Test gedcom import

This is  a bug | feature request.

Prerequisites

[ ] Are you running the latest version?
[ ] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/familytree365)
[ ] Did you check the documentation?
[ ] Did you perform a cursory search?

Description

Steps to Reproduce

Expected behavior

Actual behavior

Gedcom import should work with default files such as Royal92.ged found from Google. Needs supervisor or artisan queue listen/work

It may be the frontend not configured properly now.


Annoying prompt for access to contacts

Checklist

[x] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.603
Where did you get the app from?
Google Play
Android version
I am not using a custom ROM.
Device model
Motorola G Pure
Steps to reproduce
In numerous different situations I am prompted to allow K9 access to my contacts. There doesn't seem to be a way to stop these prompts by saying "never". The only way an app will ever get access to my contacts is if it constantly prompts me, and one day it catches me off guard. Perhaps that is K9's/Thunderbird's/Mozilla's intent, but I sure hope not.
Expected behavior
No means no. Once I say no, that should mean no forever unless there is an option under "settings" that allows me to change my mind. I've looked for that option and I don't see it.
Actual behavior
I am constantly badgered by K9 to allow access to my contacts.
Logs
I don't think log are really necessary. Surely this is just an oversight.
Android 12.

We already changed the way we're asking for permissions in the beta version. See also https://blog.thunderbird.net/2023/12/thunderbird-for-android-k-9-mail-november-december-2023-progress-report/

Thanks. Good to know. Appreciate the change.


Make IMDB Reviews dataset consistent

Currently they return a map and still support transforms. Is it possible to normalize them to a similar result as the other datasets? For example, return a tuple of {{input_binary, input_type, input_shape}, {label_binary, label_type, label_shape}}?

Thanks for flagging! I'll open a PR to get of the transforms.
As for normalizing, we could truncate or pad the binaries to make them uniform in shape (as @seanmor5 suggested). That way we can provide an input_shape that describes the data exactly. Otherwise, we could make the input_shape something like {25000, nil} to indicate the length of each binary varies. Or do you have another suggestion?
We may want to return the map that IMDB.download/1 current returns in a new IMDB.to_columns/1 function for use with Explorer, similar to Squad.to_columns/1.

I see… Hrm. It would be nice to see how this dataset would be used with Axon or Explorer then before making a decision.


Darken link name if not related part of graph is hovered over

Very much needed! )
Currently, any complex graph which utilises this great plugin, quickly becomes quite a mess.

When I hover on some object, all other unrelated objects and connections are dimmed. All but links titles ) It would be awesome if all titles of all unrelated links were also dimmed. It would help to improve the visualization greatly.
When hover on some object on the graph, only the related stuff should be highlighted.

Agree with it.
It might even be better if the links were dimmed by default, and activated only when I hover the linked nodes.
(or it could be configurable)


add array support for NonZeroI* in postgres

Implements PgHasArrayType for NonZeroI16, NonZeroI32 and NonZeroI64

Need to run cargo fmt.

@JohannesIBK if you rebase it should fix the CI issue.


Update to version 34.0 of the metadata API

This is a breaking change.  Version 31.0 of the API removed create(),
update() and destroy() and replaced them with createMetadata(),
updateMetadata(), and destroyMetadata().  It also added
readMetadata() (and upsertMetadata(), which I'm not tackling here),
and made all the CRUD operations synchronous.

Reviewers: @tjwp-yesware @stevepescatore
The large diff count is due to the new WSDL files.

:+1:

When we use metaforce to describe metadata in other apps, the API version is explicitly set to '26.0' (already different to this gem), so this should not be a breaking change there. But it's worth proceeding with caution when existing apps are updated.

What I meant about the breaking change is that I changed the names of the CRUD methods called on the Savon client (and the exposed ones to match), and didn't leave the old ones in.  If you try to use this version of the gem with a pre-31.0 version of the API, the methods you need to call won't be implemented.
I'm not sure the best way to communicate that, given that this is a fork and we're not updating the gem version when we make changes.

Sorry for the confusion over the breaking change. I understood what you were breaking. I just wanted to vet that aspect of the change for other uses of metaforce since we went through a recent problem when the API version that we used with restforce was revved.
We can do whatever we want with our fork, so if you want to add a changelog or bump the version we can do that, if we're not planning to submit those changes back to the original repo.

g2g


Setup gemnasium to track dependencies

gemnasium is an easy way to track gem dependencies. They also provide a cool badge that can be inserted in the readme

Thanks for the suggestion.  I'll look into it.


luau 0.559 build failure

👋 trying to build the latest release, but run into some build issue. The error log is as below:

build issue
  /tmp/luau-20230114-3624-1edzeko/luau-0.559/CodeGen/src/EmitCommonX64.cpp:254:64: error: ‘tm’ is not a constant expression
    254 |     build.mov(rArg3, qword[rax + offsetof(global_State, tmname[tm])]);
        |                                                                ^~

full build log, https://github.com/Homebrew/homebrew-core/actions/runs/3916145999/jobs/6708193446
relates to Homebrew/homebrew-core#120570

Note, the 0.558 release build was successful, which includes clang++-10 change

This is my config setup in case it is helpful
Clang: 14.0.0
Git: 2.39.0 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 5.15.0-1030-azure x86_64 GNU/Linux
OS: Ubuntu 22.04.1 LTS (jammy)
Host glibc: 2.35
/usr/bin/gcc: 11.3.0
/usr/bin/ruby: 3.0.2
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A

A fix will be included in the next release.
-    build.mov(rArg3, qword[rax + offsetof(global_State, tmname[tm])]);
+    build.mov(rArg3, qword[rax + offsetof(global_State, tmname) + tm * sizeof(TString*)]);


Create restaurant api

[ ] Make a folder called restaurants with a javascript file in it called Restaurant
[ ] Include things for schemas with restaurants like tags owners and times


(optionally) export the stack pointer in wcc

I am trying to implement coroutines (fibers) with the WebAssembly backend, alongside Binaryen’s Asyncify, and I now need to get information about the stack pointer so that I can copy the stack around. (See: WebAssembly/binaryen#5478)
I know this is a bit of a niche use‐case for this low‐level feature, so it is completely understandable if you don’t want to support it, but if it would be possible to export the stack pointer or add an option to export it, that would solve my problem entirely, and I’d really appreciate it!
Something along these lines (src/wcc/traverse.c):
 static void add_builtins(void) {
   // Stack pointer.
   {
     const Name *name = alloc_name(SP_NAME, NULL, false);
     Type *type = &tySize;
-    /*GVarInfo *info =*/ add_global_var(type, name);
+    GVarInfo *info = add_global_var(type, name);
+    info->export = true;
   }

Thank you for working on this project, I believe it is wonderful!

Hi @zamfofex ,
I'm not familiar with Binaryen and Asyncify,
but it is good to enable asynchronous functionality in compiled code.
I think it's ok with above change and adding command line option.
Please send a pull request when you are done.


optional dependencies

This project has 16 dependencies (as of 0.0.7), and many of those have their own dependencies.  Installing responder in a virtual environment results in 32 libraries being installed.  This also makes packaging responder more time consuming for Linux distros.
I'm sure each of those has their own reason for being there, but have you considered allowing a more minimal install?  Setuptools has an extras_require argument where optional dependencies that enable extra functionality can be specified.

that comes with the territory, unforunately


bug: redis delete method accepts a list as argument

according to asyncio_redis document http://asyncio-redis.readthedocs.io/en/latest/pages/reference.html#asyncio_redis.RedisProtocol.delete, delete method accepts a list.
And, check session in request before getting redis connection and no need to get redis connection for first request

Thanks!


Image path in vue plugin

Hi!
I'm using the Vue LazyLoad-plugin as my images is hosted on an external server.
I'm trying to set an animation-gif to show when images are loading. This is set in main.js.
Vue.use(VueLazyload, {
    observer: true,
    loading: '~/assets/loading.gif'
});

The file "loading.gif" exist in the "assets"-folder, but I get a 404-error when the site is trying to use it.
Changing the variable to './assets/loading.gif' provides the "correct" url, but still gets a 404.
Any tips?

The ~ alias only works with import, require and some static element attributes like src. You can instead have your image in the /static folder, for example at /static/assets/loading.gif. Content in that folder is copied to /dist after build which means your image will be visible at /assets/loading.gif in the browser.

Thanks! This could be made clearer in the docs.


repeat table header on dynamic pages

Hi,
I'm creating a long table on a dynamic page. This sometimes results in rows being pushed to the next page. This works fine.
Is there a way to repeat the first row, which I use as a table header, on any subsequent pages?
Thanks,
DoppyNL

This feature is going to be implemented? Do you have any alternative solution to do it?

I also need this feature.
If you guys have an alternative solution please share it.


Feature/data export script

This is the script to help export JSON data.

I am currently thinking about adding the command to the NPM package scripts.
We may consider who is accessing this script and what permissions they need to have to produce this data. Perhaps we can namespace this so the data always writes to the user's home directory.

Feedback would be welcome!

The people this script is for are going to want to run the script directly. Feel free to add it as an NPM package script, but that's not how it's going to get used.
Pretty much, the bare script without any parameters should use a good default. For instance, dump all of results to /tmp/results.json. It should also say what it's going to do and prompt the user for confirmation. There should also be --help and -q (don't prompt).

The people this script is for are going to want to run the script directly. Feel free to add it as an NPM package script, but that's not how it's going to get used.
Pretty much, the bare script without any parameters should use a good default. For instance, dump all of results to /tmp/results.json. It should also say what it's going to do and prompt the user for confirmation. There should also be --help and -q (don't prompt).

Thanks. Those are some good suggestions and I will work on them right now. I may put the command in the NPM scripts package.json because it is the first place a person will normally look to understand how to use a Node JS application. I will ensure that it is easy for them to run the script directly too.

The people this script is for are going to want to run the script directly. Feel free to add it as an NPM package script, but that's not how it's going to get used.
Pretty much, the bare script without any parameters should use a good default. For instance, dump all of results to /tmp/results.json. It should also say what it's going to do and prompt the user for confirmation. There should also be --help and -q (don't prompt).

Thanks. Those are some good suggestions and I will work on them right now. I may put the command in the NPM scripts package.json because it is the first place a person will normally look to understand how to use a Node JS application. I will ensure that it is easy for them to run the script directly too.

Done! I changed my mind on the NPM package.json because we do not have NPM or Yarn installed on Classy instances to run it from the package.json scripts section.

@rtholmes
We have the **/bin folder in .gitignore, so this file was placed in the helper-scripts directory. If it does not result in an issue, we can remove the **/bin line from the .gitignore and move the helper-scripts into the bin/ folder.

This is the script to help export JSON data.

I am currently thinking about adding the command to the NPM package scripts.
We may consider who is accessing this script and what permissions they need to have to produce this data. Perhaps we can namespace this so the data always writes to the user's home directory.

Feedback would be welcome!

The feedback has been implemented.
This script will run on any Classy instance as long as the database is named db in Docker Compose.


Add Elixir 1.15 in GitHub Actions workflows

📖 Description and reason
Elixir 1.15 🚀
🦀 Dispatch
#dispatch/elixir

🦀 Requesting reviewers for this pull request:

@garno (reviewer for the elixir stack)

🦀 Mentionning users for this pull request:

@EtienneStPierre (learner for the elixir stack)
@jocech99 (learner for the elixir stack)
@marcantoineg (learner for the elixir stack)


#hash was removed

reference https://github.com/rails/rails/commit/a2be6ce3eb94516a57c07c98f3cb19502b05cff1#diff-93f829a51b98ce021e5a83382ab9310a
reverts https://github.com/rspec/rspec-rails/commit/8f533e0690426482a3f90c187371f65bff00b181
fixes https://github.com/rspec/rspec-rails/pull/2076 again

Seems like a safe bet for the WIP branch whilst in beta

Thanks!


Docker repo is corrupted?

$ docker pull rustembedded/cross
Using default tag: latest
Error response from daemon: manifest for rustembedded/cross:latest not found: manifest unknown: manifest unknown

$ cross build --target=arm-unknown-linux-gnueabihf
Unable to find image 'cross-armhf:lastest' locally
docker: Error response from daemon: pull access denied for cross-armhf, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

FROM rustembedded/cross:arm-unknown-linux-gnueabihf

ENV DEBIAN_FRONTEND=noninteractive
ENV PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/arm-linux-gnueabihf/pkgconfig
ENV PKG_CONFIG_ALLOW_CROSS=1

RUN apt-get update && apt-get install -y --no-install-recommends apt-utils

RUN dpkg --add-architecture armhf && \
    apt-get update && \
    apt-get install --assume-yes libpthread-stubs0-dev:armhf && \
    apt-get install --assume-yes libudev-dev:armhf && \
    apt-get install --assume-yes libudev1:armhf

RUN curl https://sh.rustup.rs -sSf | sh -s -- -y

# Add .cargo/bin to PATH
ENV PATH="/root/.cargo/bin:${PATH}"

# Check cargo is visible
RUN cargo --help

RUN rustup target add arm-unknown-linux-gnueabihf

cross 0.2.1
https://hub.docker.com/r/rustembedded/cross

What are you trying to achieve?
rustembedded/cross does not contain a latest tag, which is why you get manifest for rustembedded/cross:latest not found: manifest unknown: manifest unknown
cross build --target=arm-unknown-linux-gnueabihf pulls rustembedded/cross:arm-unknown-linux-gnueabihf-x.y.z not cross-armhf:lastest. Do you have a image override in your Cross.toml that is configured wrongly? Also note that it seems the tag is misspelt. lastest vs latest.
please provide your Cross.toml file and cross -V output for further help.

it works. it was a temporary problem with the repo in the docker hub.


cannot open any web-vscode after deleted a repository

I work in web-vscode just now. Here is what I do

git add 10k files by mistake.
It takes so long to Undo changes
so I deleted the repository and open a new one.
then I cannot open any repository by web-vscode

I get this while i open the new repository
Cannot open repository. GraphqlResponseError: Request failed due to following response errors:
- API rate limit exceeded for user ID xxxxxxxx

Version: 1.95.0
Commit: 912bb683695358a54ae0c670461738984cbb5b95
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Embedder: github.dev
Extension version: 0.42.0

I deleted the repository in Remote resource Manager.
Everything works.


How to change shortcuts

Do you know how to change default shortcuts??

This might be what you are looking for.
BTW this repo is just for listing Hyper plugins, and not Hyper itself.


Add missing span for run_method_on_single_plugin in Plugin Manager

I want to merge this change because adding a missing span for run_method_on_single_plugin in Plugin Manager.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-2150 Activate span for single plugin call


How to send message

Is there an example to send a message with C version of qrtone ?

The MXChip is sending a message here:
https://github.com/Ifsttar/qrtone/blob/v0.3.0/examples/MXChipChat/MXChipChat.ino#L207
Qrtone can send any bytes, so you can use the structure you want. For "chat" part in the web page on https://ifsttar.github.io/qrtone/ it use simple format like this:

address
size(bytes)
description

0
1
Identifier of the field type (0x0 username 0x1 message)

1
1
Field size (0-255)

2
n
Field content

So if user name MXChip says off it will produce
int8_t msg[] = {0, 6,'M', 'X', 'C', 'h', 'i', 'p', 1, 3, 'o', 'f', 'f'};

This message have to be encoded by qrtone using this function call:
audio_to_play = qrtone_set_payload_ext(qrtone, msg, sizeof(msg), QRTONE_ECC_Q, 1);

qrtone qrtone instance
msg message pointer
sizeof(msg) length of message
QRTONE_ECC_QThe higher the quality of the ecc will be, the more it will be able to reconstruct an altered message, however by increasing the duration of the audio signal.
crc 0x1 to add CRC bytes (message content check)

This function will return the total number of audio samples.
In order to generate and retrieve the samples you have to call this function
qrtone_get_samples(qrtone, scaled_output_buffer, scaled_output_buffer_size,  power);

scaled_output_buffer is a float array of any size. Each consecutive call to this function will generate the next samples so you don't have to cache the full length of the message.
As the return value is a float value you have to set the expected peak value using the power argument.


Protection against possible directory traversal and remote inclusion.

You are right. I added code like you suggested. (really the same code). I think the possible problem is covered.

Looks good, thanks for getting that!
Tagged as 1.3.0

Your welcome. I think in a few days I can write a couple of lines about this feature in the documentation.


Speed up xr_vectorize

dea_spatialtools.xr_vectorize is seemingly orders of magnitude slower than dea_spatialtools.subpixel_contours, despite both kind of doing the same thing. I suspect this is the call to gdal/rasterio, which we can probably replace with skimage.measure.label.

Do they return the same type of objects though?

No, but I have postprocessing code on the subpixel_contours to get them in the same format, and it's not the bottleneck as far as I can tell


What is your error on ?

Sorry, I didn't have time to look at this until now, but ready to assist in debugging.
I just need some recreation steps, where are you seeing the error, what is your hunch? We didn't go through as debugging in the course since you sort of breezed through it so far, but what I get most students to do is write out the following.

What is the situation?/What are you trying to do?
What is breaking/error message?
What is your question?
What is your best guess?

Answering those 4 questions will put you in a good place to get an answer, whether from me or from Slack or Stack Overflow. With that being said, I see the error message and have begun debugging and can provide some detailed steps to get unstuck, just need to know what you know first.

Also feel free to provide screenshots as well, those are always helpful.

Per the checkpoint, the code provided should be able to make a song play when you click on the play button that appears when you hover over a song number.

When i click on the play button, the error in the console reads "TypeError: Cannot read property 'audioUrl' of undefined". This refers to the following code:

var setSong = function(song){
     		if (currentBuzzObject) {
     			currentBuzzObject.stop();
     			currentSong.playing = null;
     		}

     		currentBuzzObject = new buzz.sound(song.audioUrl, {
     			formats: ['mp3'],
     			preload: true
     		});

     		currentSong = song;
     	};

I've copied the code line by line from the checkpoint and this error has always been there. I'm wondering if this is an actual bug in the code provided by Bloc (especially since my app was working as it should prior to starting this checkpoint (7).
Regarding the issue itself, song.audioUrl is coming back as undefined. This should be referring to the Fixtures.js file which contains all of the album information. Since the error is specially stating that audioUrl cannot be read, I'm wondering if the proper element (or anything for that matter) is being passed into the song parameter for the setSong function? It nothing was, it would make sense why this is coming back as undefined.

4). My guess is that nothing is being passed into the function so song (the parameter for the function) isn't referring to anything so audioUrl which is the method being called on the parameter is invalid therefore returning as undefined. From what I mentioned earlier, this seems like a bug in the code Bloc has provided (unless I suck at copying and pasting, lol).
Let me know what you find. Very interested in the resolution for this one.

This is the portion of the checkpoint where the error begins

Sorry to string you along here, but you missed the last part. What is the error message? Without the error message I spend more time trying to figure out your app, rather than trying to figure out your error. You will always have errors in code and it will be valuable to learn how to seek help by providing the most information.
Whether it's to me, Stack Overflow, or someone random on Slack. Always provide the literal error message
=>typeError: Cannot read property 'audioUrl' of undefined

The other part missing is your best guess or question. What is undefined?
Answer the question above first, but your error is here => https://github.com/rapid99/bloc-jams-angular/blob/master/app/templates/album.html#L13

The literal error message from the console when I click on the play button that appears when you hover the mouse over the song number is "TypeError: Cannot read property 'audioUrl' of undefined" (I'm at the office now but can get the full on error message when I get home.
My best guess as to what is going on here is that the parameter for the function in question isn't getting filled in properly so the audioUrl (which is the method being called on the 'song' parameter) doesn't refer to the audioUrl element within the Fixtures.js file.
We do meet today though so we can always look at this this afternoon.

Any thoughts on this one @bdougie ?
TypeError: Cannot read property 'audioUrl' of undefined
I have the same issue.

@senoff I provide info above, context is key, which I don't have any for your case. The problem was song was undefined, I am sure you have a similar object that is undefined. Find what is undefined and define and you should be able to get past your current error.

Thanks.  I was able to use the solution you providing to find my issue in the album.html file.


the point clouds file

Thanks for your pretty code Detailed 2D-3D Joint Representation for Human-Object Interaction.
I do not have a GPU and I can not get point clouds with my PC and it is not possible for me to run step 4 of  "Data generation" phase. My possibilities are limited.
I want point clouds of humans and objects. Were you able to generate  the point clouds with low space?

Hi, thanks for using our code.
The point clouds take up too much space thus difficult for us to share them on google driver, as well as the extracted 3D features, so we provide the self-extracting manuscripts for the users.
Is it possible for you to use some online GPU services like the google cloud platform? Now we are also working on constructing a lite version of DJ-RN relying on limited resources, but it may take a while to make it work.

Hi
Thank you very much for your code.
I already used the online google colab that were very slow. Of course, I did not use them for this purpose. I will definitely use it. Is it possible for you to put some of these cloud points in Google drive, for example, the volume of one tenth of them?

With your help, I was able to move forward to step 4 of 'Data Generation' phase. For me the step 4 of 'Data Generation' (Run SMPLify-X on the dataset with the filtered pose) is very time consuming. Maybe if I have the .pkl files and meshes files of SMPLify results, I will can perform step 5 (Assign the SMPLify-X results to the training and testing data) myself. The meshes and .pkl files are smaller in size. Is it possible for you to put these in Google Drive?

Sorry for the late reply! The required files take ~100G space in our local server, which is still too large for us to upload them to the Google Drive.

Sorry to bother you. Even pkl and mesh files take up a lot of space? For me, the pkl and mesh files of each image takes up about 1 MB space, which is 27 GB for 27,000 training images. Is it not possible for you to send  a smaller volume of them? If possible, send only the mesh and pkl files that are smaller.

We didn't contain the image files when calculating. And since different image contains different number of samples, many images actually cost more than 1MB, which is too large for us to upload them to the Google Drive.

You are absolutely right. In any case, I do not have 100 G of space on my computer to run myself.
Excuse me, I have a question, For the "3D Human-Object Interaction Volume Generation and Visualization" step just need to have the files of vertex_path_GT.txt,vertex_path_Neg.txt and vertex_path_Test.txt ? That is, all of the above steps(Data generation step) are done to produce a file that comes with all the point clouds of the overall images and use it in the "3D Human-Object Interaction Volume Generation and Visualization" step. If yes, so, is it possible to send me the files of vertex_path_GT.txt, vertex_path_Neg.txt and vertex_path_Test.txt?
If it is possible for you please help me

@mahsa1363 can you please share with me vertex_path_GT.txt ?

@mahsa1363 can you please share with me vertex_path_GT.txt ?

@Foruck how can we exactly reproduce the results in your CVPR paper without having access to vertex_path_GT.txt, vertex_path_Neg.txt, and vertex_path_Test.txt files?

@Foruck how can we exactly reproduce the results in your CVPR paper without having access to vertex_path_GT.txt, vertex_path_Neg.txt, and vertex_path_Test.txt files?


Crash when opening a recipe in NEI

After updating to Mekanism 8, every time I click on any item's icon in NEI, client crashes. Doesn't matter what kind of item, I tested a few - vanilla iron pickaxe, reactorcraft's uranium fuel pellet and others.
Everything was fine with Mekanism 7
http://pastebin.com/3VGExtj2
Thanks in advance for your help

This looks like outdated minetweaker.


[RMP] Improve the speed of training models with Merlin Models

Problem:
Merlin models needs to differentiate itself relative to other RecSys library solutions.  One of those areas of differentiation needs to be performance on the GPU.  If our libraries don't follow best practices and achieve fast performance that we can measure on GPU then our potential customers have no reason to use the library.
Goal:

Provide performant retrieval and ranking models in production
Follow best practices by our colleagues for GPU optimization

Constraints

Merlin models is built on top of Tensorflow

Possible Optimizations
Retrieval models

[ ] Performance optimization

[ ] https://github.com/NVIDIA-Merlin/models/issues/340
[ ] https://github.com/NVIDIA-Merlin/models/issues/339
[x] https://github.com/NVIDIA-Merlin/models/issues/338
[x] https://github.com/NVIDIA-Merlin/models/issues/336

Ranking models

[ ] ???

@gabrielspmoreira @marcromeyn Where are we at with the perf regressions we were seeing?  Can we close this?

Check this bug is done https://github.com/NVIDIA-Merlin/models/issues/339 and this issue should be closed. This is an ongoing effort. The profiling portion will be spun off as a separate RMP ticket

@EvenOldridge @viswa-nvidia  As we discussed in the Grooming meeting today, I have tested the pending runtime issue of retrieval models training (https://github.com/NVIDIA-Merlin/models/issues/339) with the current implementation (for both V1 and V2) and it doesn't occur anymore. So that bug was closed.
I also extracted the profiling tasks of retrieval model pipelines to a new RMP #340 , which also addresses ranking model pipelines, as profiling tasks will require an external support (Valerie).
So I am closing this RMP, as it already delivers value with the finished perf improvements on retrieval models.


[Bug] Default button text invisible on hover in dark mode

default on hover text will be invisible in dark mode

Thanks for reporting this issue !


Direct Line sending more ConversationUpdate activities than it used to

Hello bot developers! This isn't a real issue -- it's an announcement from the Bot Framework team.
Today we rolled out a change where Direct Line will send more ConversationUpdate messages than it used to.
Old behavior: Direct Line sends a ConversationUpdate activity when the conversation is started
New behavior: Direct Line sends a ConversationUpdate activity when the conversation is started and when each user joins.
If you're using Direct Line 1.1 and you're seeing a ConversationUpdate activity after every message the sends, you're probably not populating the From property in your messages. You can fix this issue by choose an ID and sending that in the From field. You can read more about this issue here: https://docs.botframework.com/en-us/technical-faq/#why-does-my-direct-line-conversation-start-over-after-every-message. This issue does not exist in Direct Line 3.0.
Please let us know if you encounter any problems.

hi issue 2071 https://github.com/Microsoft/BotBuilder/issues/2071
does it get affected by your latest update. Can you pls take a look at my issue. My project don't work now. it's urgent .thanks.

Hi @zhou-xinghai, I took a look at the other issue but at the moment we're not seeing this with other bots. Let's discuss on the other GitHub issue and try to determine the cause there.


docs: fixed trim links

Just noticed these links were not working :)

I am in the process of updating the documentation for v0.31.0 and some names like these have changed. The API reference is outdated, not the guides. 🙃


Add Dissipation Operators for DienerDorbandSchnetterTiglio2007

Is the only dissipation operator available the one of MattssonSvärdNordström2004?
I am trying to construct a dissipation operator from DienerDorbandSchnetterTiglio2007 but I get a MethodError.

MWE:
d = derivative_operator(DienerDorbandSchnetterTiglio2007(), 1, 2, -5,5,11)
di = dissipation_operator(d)
# d.coefficients -> Mattsson, Nordström (2004)

dissipation_operator(DienerDorbandSchnetterTiglio2007(), 2, -5,5,11, d.coefficients.left_weights, d.coefficients.right_weights)
ERROR: MethodError: no method matching dissipation_coefficients(::DienerDorbandSchnetterTiglio2007, ::Int64, ::StepRangeLen{…}, ::SVector{…}, ::SVector{…}, ::FastMode)

Closest candidates are:
  dissipation_coefficients(::MattssonSvärdNordström2004, ::Int64, ::Any, ::Any, ::Any, ::Any)
   @ SummationByPartsOperators ~/.julia/packages/SummationByPartsOperators/VWtwV/src/SBP_coefficients/MattssonSvärdNordström2004.jl:29
  dissipation_coefficients(::MattssonSvärdNordström2004, ::Int64, ::Any, ::Any, ::Any)
   @ SummationByPartsOperators ~/.julia/packages/SummationByPartsOperators/VWtwV/src/SBP_coefficients/MattssonSvärdNordström2004.jl:29

Stacktrace:
 [1] dissipation_operator(source_of_coefficients::DienerDorbandSchnetterTiglio2007, order::Int64, xmin::Int64, xmax::Int64, N::Int64, left_weights::SVector{…}, right_weights::SVector{…}, strength::Int64, mode::FastMode, parallel::Nothing)
   @ SummationByPartsOperators ~/.julia/packages/SummationByPartsOperators/VWtwV/src/dissipation_operators.jl:231
 [2] dissipation_operator(source_of_coefficients::DienerDorbandSchnetterTiglio2007, order::Int64, xmin::Int64, xmax::Int64, N::Int64, left_weights::SVector{…}, right_weights::SVector{…})
   @ SummationByPartsOperators ~/.julia/packages/SummationByPartsOperators/VWtwV/src/dissipation_operators.jl:224
 [3] top-level scope
   @ REPL[26]:1
 [4] top-level scope
   @ ~/.julia/juliaup/julia-1.10.0+0.x64.linux.gnu/share/julia/stdlib/v1.10/REPL/src/REPL.jl:1428
Some type information was truncated.  Use `show(err)` to see complete types.

in the paper of Diener et al they provide dissipation coefficients up to 8th order (D_{8-4}), up to now only up to 2nd order dissipation operators are supported?

Currently, dissipation operators are only implemented for

MattssonSvärdNordström2004 (see SummationByPartsOperators.dissipation_coefficients)
PeriodicDerivativeOperators (taking basically the interior parts of the operators of MattssonSvärdNordström2004)
FourierDerivativeOperators

Adding the dissipation operators of DienerDorbandSchnetterTiglio2007 would be a nice contribution and I would be happy to review a PR. Let me know if you need help with this.

in the paper of Diener et al they provide dissipation coefficients up to 8th order (D_{8-4}), up to now only up to 2nd order dissipation operators are supported?

I'm not sure I understand this part correctly. Do you refer to the order of accuracy or the order of the derivatives that are approximated by the dissipation operators? The ones of Mattsson et al. use higher-order undivided difference approximations of a $2p$th derivative for SBP operators with interior order of accuracy $2p$. That's why they keep the order of accuracy of the SBP operators for which they are designed.


Figure out how to get rid of entityManager.entities

There's gotta be some way to put an indexer on entityManager so I can do entityManager["index"].

This isn't possible.


remove http-related nginx config

Continuing with #864 remove remaining HTTP related config.

Pull Request Test Coverage Report for Build fc6e17f123eb82bc510d170bc055e2a806c1b251-PR-866

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.937%

Totals

Change from base Build 0c50ac677dd412ccc23880a81c1ecf4d2e1fd3ba:
0.0%

Covered Lines:
992

Relevant Lines:
1439

💛  - Coveralls

@conectado Mind if I push up a commit to this PR? I think I want to add some docs/config changes.

@conectado Mind if I push up a commit to this PR? I think I want to add some docs/config changes.

@jamilbk  go ahead!


cmd/go: -buildmode=c-archive should work on windows

We'd like a way to use go as a library language on Windows. Since there is already issue #11058 that addresses the need for the c-shared build mode for generating DLLs, I am adding this request for getting static library support.

Submitted a patch at https://go-review.googlesource.com/#/c/18057/

I've added 32-bit support to this code, however it no longer builds at all when I set GOARCH=386.

Any ideas?

I can see rt0_windows_amd64.s changed in CL 18057. For 386 support, I suspect you want to make similar changes to rt0_windows_386.s ay the very least. No?
Alex

I'm sorry, I should have been more clear. I have not pushed the 32-bit changes into the CL. I can do that, if you like. I made numerous changes, including rt0_windows_386.s. I admit that it is hard to diagnose a problem blind. I was thinking I just made some obvious beginner's mistake and perhaps you would might have seen something like this before.

It's just a guess, but perhaps you are getting no buildable Go source files in <path> because you have set GOARCH such that you are cross-compiling, but you did not explicitly set CGO_ENABLED=1.

That was it exactly. The 32-bit Windows API does not support some of the runtime features I wrote for initialization. I will have to rewrite parts of that code.

I am encountering very strange errors. Basically, hundreds of errors that look like:
'blah' referenced in section '.text' of 'blah' defined in discarded section '.text' of 'blah.../libkernel.a
I've tried to look through why this may be happening, but I'm afraid that I haven't come up with anything. Any ideas?

If implementing 32-bit is a problem, do not do it. Lets implement windows-amd64, and we'll worry about windows-386 later.
Alex

Okay. I will disable the build commands for 32-bit, but I feel like I should leave the code in. The problem happens during the final link of the library. The support code should be correct, including the runtime and relocation bits. There's just something about the link command that needs to be figured out. Does that sound okay?

32-bit is also important to me.  I'd like to help.  I'm seeing those same link errors when I enable it with your patch.
Many errors like the following:
_free' referenced in section `.text' of C:/Program Files/mingw-w64/i686-5.1.0-p
osix-dwarf-rt_v4-rev0/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.1.0/../../../../
i686-w64-mingw32/lib/../lib/dllcrt2.o: defined in discarded section `.text' of C
:/Program Files/mingw-w64/i686-5.1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../lib/g
cc/i686-w64-mingw32/5.1.0/../../../../i686-w64-mingw32/lib/../lib/libmsvcrt.a(dk
tbs01101.o)
`__initterm' referenced in section `.text' of C:/Program Files/mingw-w64/i686-5.
1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.1.0/../../.
./../i686-w64-mingw32/lib/../lib/dllcrt2.o: defined in discarded section `.text'
 of C:/Program Files/mingw-w64/i686-5.1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../
lib/gcc/i686-w64-mingw32/5.1.0/../../../../i686-w64-mingw32/lib/../lib/libmsvcrt
.a(dktbs00350.o)
`__amsg_exit' referenced in section `.text' of C:/Program Files/mingw-w64/i686-5
.1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.1.0/../../
../../i686-w64-mingw32/lib/../lib/dllcrt2.o: defined in discarded section `.text
' of C:/Program Files/mingw-w64/i686-5.1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/..
/lib/gcc/i686-w64-mingw32/5.1.0/../../../../i686-w64-mingw32/lib/../lib/libmsvcr
t.a(dktbs00145.o)
`__initterm' referenced in section `.text' of C:/Program Files/mingw-w64/i686-5.
1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../lib/gcc/i686-w64-mingw32/5.1.0/../../.
./../i686-w64-mingw32/lib/../lib/dllcrt2.o: defined in discarded section `.text'
 of C:/Program Files/mingw-w64/i686-5.1.0-posix-dwarf-rt_v4-rev0/mingw32/bin/../
lib/gcc/i686-w64-mingw32/5.1.0/../../../../i686-w64-mingw32/lib/../lib/libmsvcrt
.a(dktbs00350.o)
```

Can anyone shed some light on what might be causing the 32-bit link errors so others can look into it? From searching I found hints that it might be the order the libs are linked in.. but I had no luck changing the linking order of the libs to resolve the errors.

32-bit Windows uses a leading underscore on symbols.  64-bit WIndows does not.  It may be related to that.  Or it may not, it's just a guess.

before those errors I do see the following
Cannot export bad_proc_msg: symbol not found
Cannot export gosave: symbol not found
Cannot export masks: symbol not found
Cannot export setg_gcc: symbol not found
Cannot export shifts: symbol not found
Error: 0-bit reloc in dll

32-bit is also important to me. I'd like to help.

64-bit version does not work at this moment as far as I am concerned. We need testcarchive to PASS for us to even consider CL for inclusion. No point discussing 32-bit - it is only distracting everyone. If you want to help, help testcarchive to PASS.
Alex

testcarchive is only failing because the test is set up as a .bash file, which won't work on Windows.
I'll work on a test.bat now

@alexbrainman The c-archive tests were rewritten by @ianlancetaylor and now they don't even compile on Windows. So... I'm really not sure how to make the tests pass at this point. I started rewriting the test.bash file in Go, but now that the signal handlers exist there's kind of no point.

If it was rewritten in Go should it just be a "go run" file?
What do you suggest we do about the test files?

Sorry about that.  Signal handling is pretty hard to get right for c-archive and c-shared, so we needed the tests.  I didn't really think about the effect on Windows.  It's fine with me if you want to put in a main_windows.c.
Probably test.bash should be replaced by a archive_test.go file that is run using go test, like the one in misc/cgo/testshared.

I still prefer we use Go to write tests (in $GOROOT/src/cmd/dist/test.go or what Ian suggested). We can write test to do whatever is required for different OSes. But I will let you do what you want.
Alex

I have added a main_windows.c, which contains the contents of main.c before @ianlancetaylor committed the signal handling changes. I updated test.bat to use that file instead of the other one.
Note that I am willing to rewrite the tests in Go, but I would like to get this patch accepted first. The c-archive tests pass for me on 32 and 64-bit.

I can also verify that c-archive now works for me on both 32 and 64 bit Windows

I removed the InitOnce based synchronization for the runtime init. This allows the patch to compile on older versions of mingw.

Just an update. The only problems left appear to be link errors with the 32-bit mode where cgo is inexplicably linking in -mwindows mode instead of -mconsole. This is causing an undefined reference to WinMain(). I am investigating this issue, but it doesn't appear related to my patch other than that cgo may not have worked properly at all on Windows 32-bit, and now we would like it to.
Anyone who is looking to help get this patch done sooner could investigate TestCgoExternalThreadPanic, TestCgoCrashHandler, TestCgoTraceback, etc.
I am looking into these failures too, but more eyes are better.

I have verified the cause of the problem:
If I create a file:
//test.c
int main(int argc, char **argv) {
return _main(argc, argv);
}
and I include it in the build of the failing tests, the build completes normally.
This verifies that it is the underscore problem.
I have tried to adjust the code in pe.go which prepends the underscore to avoid doing that for main(), but it doesn't seem to have any effect.
@ianlancetaylor , @alexbrainman I am not sure where main() is defined for a cgo-enabled program on 32-bit windows. If someone could point me to that location, the fix appears to be trivial.

main (or main for amd64) is defined in runtime/rt0_windows$GOARCH.s

@minux, thank you. This bug has been fixed. The failing tests now pass. Please re-evaluate the patch for inclusion.

@alexbrainman  I have addresses the issues you raised in the patch. Please re-evaluate it. Thanks!

@alexbrainman I have addresses the issues you raised in the patch.

Thank you for letting me know. But you don't need to comment about it on this issue. I can see all your new changes on Gerrit. Anyone who posts on your CL (and all nominated reviewers and CC) will get email every time you comment there or upload new patch.
Alex

@minux, @ianlancetaylor: There is some question about the right thing to do here:
// os1_windows.go
// Used by the C library build mode. On Linux this function would allocate a
// stack, but that's not necessary for Windows.
//go:nosplit
func newosproc0(mp *m, stk unsafe.Pointer) {
newosproc(mp, stk)
}
Some similar implementations of this function use //go:nosplit, others use  //go:nowritebarrier
Neither @alexbrainman nor I know what the right thing to do here is. Can you please advise?

On Unix systems, newosproc0 is called at process startup time, with no stack guards installed.  I assume the same is true in your Windows implementation.  Therefore, it must be //go:nosplit.  This is not optional.  Also, it must only call //go:nosplit functions.  This is unlike newosproc, which does not need to be //go:nosplit.  But if you are going to have newosproc0 call newosproc, as implied above, then newosproc must also be //go:nosplit.
Similarly, newosproc0 is called before the GC is installed, and therefore any write barriers will fail, so //go:nowritebarrierrec is a good choice (nowritebarrierrec is better than nowritebarrier, as it means that not only must this function have no write barriers, every function it calls must have no write barriers).  This is a warning option that does not affect code generation, so it's OK if it's not there.  But since you are writing new code, you should add it.  newosproc is normally //go:nowritebarrier because it is called from newm, where the comment explains why no write barriers are permitted.

@alexbrainman or anyone else:
I rebased onto origin/master and I am getting a new error when I run all, but only on 64-bit architectures:
ok      cmd/fix 0.125s
--- FAIL: TestShadowingLogic (0.77s)
        go_test.go:244: running testgo [list -f ({{.ImportPath}}) ({{.ConflictDir}}) ./testdata/shadow/root1/src/math]
        go_test.go:259: standard output:
        go_test.go:260: (_/C_/Users/Christopher_Nelson/t/src/cmd/go/testdata/shadow/root1/src/math) (C:\Users\Christopher Nelson\t\src\math)

        go_test.go:1884: shadowed math is not shadowed; looking for (_/C_/Users/Christopher Nelson/t/src/cmd/go/testdata/shadow/root1/src/math) (C:\Users\Christopher Nelson\t\src\math)
        go_test.go:244: running testgo [list -f ({{.ImportPath}}) ({{.ConflictDir}}) ./testdata/shadow/root1/src/foo]
        go_test.go:259: standard output:
        go_test.go:260: (foo) ()

        go_test.go:244: running testgo [list -f ({{.ImportPath}}) ({{.ConflictDir}}) ./testdata/shadow/root2/src/foo]
        go_test.go:259: standard output:
        go_test.go:260: (_/C_/Users/Christopher_Nelson/t/src/cmd/go/testdata/shadow/root2/src/foo) (C:\Users\Christopher Nelson\t\src\cmd\go\testdata\shadow\root1\src\foo)

        go_test.go:1897: shadowed foo is not shadowed; looking for (_/C_/Users/Christopher Nelson/t/src/cmd/go/testdata/shadow/root2/src/foo) (C:\Users\Christopher Nelson\t\src\cmd\go\testdata\shadow\root1\src\foo)
        go_test.go:244: running testgo [install ./testdata/shadow/root2/src/foo]
        go_test.go:263: standard error:
        go_test.go:264: go install: no install location for C:\Users\Christopher Nelson\t\src\cmd\go\testdata\shadow\root2\src\foo: hidden by C:\Users\Christopher Nelson\t\src\cmd\go\testdata\shadow\root1\src\foo

        go_test.go:283: testgo failed as expected: exit status 1
FAIL
FAIL    cmd/go  92.031s

Any guidance, would be appreciated.

I doubt the cmd/go test failure has anything to do with your patch.  It should probably be a separate issue.


fix re-use data between postcss listeners (#103)

fix re-use data between postcss listeners
format code with prettier

relate issues: #103, #101

@cuth please check and review this pr

https://github.com/cuth/postcss-pxtorem/issues/110
bug ?

yes


Check for uniqueness among local_identifier within a label

The Information Model says, for local_identifier in all containers,
The local_identifier attribute provides a character string which uniquely identifies the containing object within the label.
I finally encountered a label that had multiply defined local_identifiers with the same value.

This may actually not be an issue with newer version of the IM that use the schema ID type

The IM now uses xs:ID to define local_identifiers, which will handle this use case:
    <xs:simpleType name="ASCII_Local_Identifier">
      <xs:restriction base="xs:ID">
        <xs:minLength value="1"/>
        <xs:maxLength value="255"/>
        <xs:pattern value='\p{IsBasicLatin}*'/>
      </xs:restriction>
    </xs:simpleType>


Chore: update files affected by make github/init

what

Update files affected by make github/init.

why

This updates important files relating to GitHub Actions: CODEOWNERS, workflow files, release-drafter configuration.

references

https://github.com/cloudposse/build-harness/blob/5c5abeceb39cde6d75a2ee754947afeb880d7658/modules/github/Makefile.init

/test all


max per block and max total imbalance should be presented in ether (wei)

currently imbalance recorder operates with twei / token currency.
it would be more "readable" if values presented in ether (wei).
so change the whole logic to ether - keep imbalance in twei. set max in twei etc...

question:
spyros
if token value drops big - lets say 30% and ether doesn't
will we enlarge our reserve?
will lower our max imbalance?

This goes the same for eth/token rise or drop, regardless if we use  twei or wei.
We will update the twei numbers more often than the wei, so being able to set them in wei, makes it easier.

It will be a security threat to have that.


Order exercises by increasing difficulty

At the moment, the exercises are kinda haphazardly ordered. Ideally, we'd list the exercises in progressive difficulty order, as that proveds the best experience for the user.
In the Rust track, they went about this problem by looking at the concepts that are required. This might be a bit infeasable for this track, as there are so many exercises.
I suggest we first start by categorizing the exercises in three categories:

Easy
Moderate
Difficult

We can then look at the individual categories to determine the ordering within that category. What do you think about this approach?

I wonder if that could be something we can add to the config...

Well, the config file is JSON, so that means no comments.

This makes a lot of sense.
I'm only about 1/3rd in the F# track and experience this. Some exercises require understanding of a lot of concepts if you want to solve them elegantly (partial active patterns, options, list functions, piping,...), while the follow-up exercise is a walk in the park again. I'll see if I can find the time to pick out the ones I found especially tricky.
I found the ones that have a non-functional API (I'm looking at you Clock & Bank Account!) add complexity that isn't necessary to grasp F# FP basics. When working in the real world/C# interop those things become very relevant but these topics aren't that relevant if you want a taste of idiomatic F#.
I'd push those exercises further down the track.
Especially Bank Account, that one even had me pulling out MailBoxProcessor :smile:

@jovaneyck Thanks a lot in advance already! There are some exercises with a non-functional API. Do you think we should be converting them to proper functional exercises?

@ErikSchierboom I feel like I should try to complete all the exercises before I can really rank them, but I do think that the ones with a non-functional API are worth converting.

@rmunn Sure, that totally makes sense! I'll rework the non-functional exercises.

@jovaneyck PR #152 was just merged, which converts the six remaining OO exercises to functional ones :)

@ErikSchierboom I do prefer the approach of tagging each exercise with a list of topics that need to be understood beforehand, and from there grouping the topics themselves by difficulty to determine the order of exercises. With difficulty being based on personal opinion there will be more room for subjectivity and the influence of each person's programming background.
I can start tagging each exercise as I do it, plus the finished ones. I was thinking of turning this into a little fsharp program, maybe something along these lines:
type Topic    = Topic of string
type Exercise = { title : string; topics : Topic list }
let Exercises = [ ("bob", ["PatternMatching", "Conditionals"]) // ...
                ] |> List.map (fun title topics -> { title = title; topics = List.map Topic topics})

Once all the data is in then it will be easy to write a sorting function and adjust the algorithm as needed.

Great idea! I'll try to work on my list of tags as well.

@ErikSchierboom  How about using the fsharp language reference?
Also, I assume we will be using the example solutions in the xfsharp repo?

@choiaa The F# language reference is a very convenient help. I do think that we should also have a way of marking the difficulty of an exercise. One exercise that uses pattern-matching might be a lot more difficult than another.
The example solutions are just that: examples. There are probably far better solutions to many of the problem than what I came up with. I think we can use the examples as a guide to see what concepts will probably be used to solve them, but they shouldn't be the definitive guide.

@ErikSchierboom You're right, I did notice the difference in difficulty even for a single topic. Do you suggest adding a single Difficulty field to the Exercise record or adding three different fields as so?
Easy : Topic list
Medium : Topic list
Advanced : Topic list

Also, where in the repo do you recommend placing this sorting program? Maybe it can be turned into an exercise with a test suite of its own?

I think the first option (single field) is better, because even though one exercise might have three advanced topics and the other just one, the latter might still be more difficult.
As for where to put this code, maybe we should create a tools or helpers directory and then put the program in a sub-directory within that directory. We can then modify the build script to allow us to run the application.
To make it an exercise would require it to be added to the x-common repository. If you think you can create a suitable exercise from it, you should create an issue in that repository.

These are all the header topics from the F# language reference page:

Functions
Values
Literals
Type Inference
Primitive Types
Unit Type
Strings
Tuples
Lists
Options
Sequences
Arrays
Generics
Records
Discriminated Unions
Enumerations
Reference Cells
Type Abbreviations
Classes
Structures
Inheritance
Interfaces
Abstract Classes
Members
Type Extensions
Parameters and Arguments
Operator Overloading
Flexible Types
Delegates
Object Expressions
Copy and Update Record Expressions
Casting and Conversions
Access Control
Conditional Expressions: if...then...else
Match Expressions
Pattern Matching
Active Patterns
Loops: for...to Expression
Loops: for...in Expression
Loops: while...do Expression
Assertions
Exception Handling
Attributes
Resource Management: The use Keyword
Namespaces
Modules
Import Declarations: The open Keyword
Signatures
Units of Measure
XML Documentation
Lazy Computations
Computation Expressions
Asynchronous Workflows
Query Expressions
Code Quotations
Compiler Directives

Not all of them are useful in the context of grading our exercises. Perhaps we should omit the ones we think won't apply to our examples? For example, I don't think we need Compiler Directives as a topic.
Furthermore, some topics are missing, such as Recursion.

As a long-term solution you could implement a system where the user can rate a finished problem with easy/appropriate/hard and change the order of the problems based on that feedback. Codewars uses a similar system to grade their new Kata entries. Implementing a solution like this would introduce a couple of other problems tho, mainly how you rank the feedback of your users and how to make the system effective without changing around too much all the time.

As a long-term solution you could implement a system where the user can rate a finished problem with easy/appropriate/hard and change the order of the problems based on that feedback.

Yeah, I think it would help a lot to get feedback from people about difficulty.

Also this would mean implementing it for the whole site, not only the F# problem track, which might be undesirable.

No, very desirable, I think!
A couple of somewhat related discussions:

https://github.com/exercism/discussions/issues/60
https://github.com/exercism/exercism.io/issues/1081

There's been so much to do on Exercism for so long, but I think that the time is probably ripe for something like this now.

There has been quite some progress lately on this issue. See this issue in particular. I think the next step for us will be to specify the topics for all exercises. After that, we can try to assign difficulties and then finally we can try to come up with a better order for the exercises.
Once the new format has been approved, I'll start with the groundwork. Hopefully, you'll be able to help assigning the topics.

RESERVED

RESERVED (exercises 1-10)

RESERVED (exercises 11-20)

RESERVED (exercises 21-30)

RESERVED (exercises 31-40)

RESERVED (exercises 41-50)

RESERVED (exercises 51-60)

RESERVED (exercises 61-70)

RESERVED (exercises 71-80)

RESERVED (exercises 81-90)

RESERVED (exercises 91-100)

RESERVED (exercises 100-102)

This has been closed by this PR.


plotEpistack plot stacks in the wrong order

It plot the stacks from bottom to top. It would be more intuitive to plot them from top to bottom.

Tentatively fixed in:
https://github.com/GenEpi-GenPhySE/epistack/pull/2#issue-695097116


docs: add adr ddos, waf and rate-limiting [skip ci]

Overview
add adr ddos, waf and rate-limiting
Checklist
My PR contains...

[x] No code changes (changes to documentation, CI, metadata, etc.)
[ ] Bug fixes (non-breaking change which fixes an issue)
[ ] Improvements (misc. changes to existing features)
[ ] Features (non-breaking change which adds functionality)

My changes...

[ ] are breaking changes
[x] are not breaking changes
[ ] If yes to above: I have updated the documentation accordingly

Documentation

[x] My changes do not require a change to the project documentation
[ ] My changes require a change to the project documentation
[ ] If yes to above: I have updated the documentation accordingly

Tests

[x] My changes can not or do not need to be tested
[ ] My changes can and should be tested by unit and/or integration tests
[ ] If yes to above: I have added tests to cover my changes
[ ] If yes to above: I have taken care to cover edge cases in my tests

This is quite an old PR - @womfoo do we need this? Can we finish it up or close it out as not needed. This one could be moved to an infra repo for safe keeping until a future date?

closing makes more sense in infra repo


feat: configurable max condition evaluation cost

Configurable max evaluation cost for conditions over hard-coded value.
Description
The DefaultMaxConditionEvaluationCost is hard-coded at 100. This is the minimum allowable value in order to prevent API compatibility problems with Conditions. This PR allows the max condition evaluation cost to be set by environment variable, CLI parameter, or within the openfga configuration file (as already defined). As the run configuration is not available outside of server startup, this value is exposed via an exported function in the config package. This function ensures that the returned value is the greater of DefaultMaxConditionEvaluationCost and the configured max condition evaluation cost.
References

Review Checklist

[X] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[X] The correct base branch is being used, if not main
[X] I have added tests to validate that the change in functionality is working as expected

@cmmoran thanks for the pull request. Did you run into specific issues with the default value? If so, can you share more about your use case?

@cmmoran thanks for the follow up changes. Left 2 last comments - LGTM otherwise. Thanks!

All PR requests have been addressed. Is there anything else I can do to facilitate this PR?

@cmmoran thanks for the follow up changes. Left 2 last comments - LGTM otherwise. Thanks!

Let me know if there's anything else I can do to facilitate this PR.


Manually lock the database

Output of restic version

restic 0.12.0 compiled with go1.15.7 on darwin/amd64
What should restic do differently? Which functionality do you think we should add?

Here's an idea.  How about "restic lock" - all it would do is lock the database from any operation.  Say you're about to sync to another cloudspace, and you don't want any clients automatically backing up to it in the meantime.  Run restic lock, transfer, then unlock on the target endpoint.
What are you trying to do? What problem would this solve?

Could come in handy to be able to stop incoming backups (etc) purposefully before maintenance, syncing operations, etc.  Especially if you have a large number of clients and a wide, randomized backup window.
Did restic help you today? Did it make you happy in any way?

Always! :)

Closing this as duplicate of #2166. In case you have no scripts that automatically run unlock, you could create a copy of the lock file create by check or prune and place that in the lock folder when you want to block operations on the repository.


CARDS-2263: Store HERACLES S3 data export task performance metrics in the JCR

This Pull Request introduces 3 new performance metrics, all related to HERACLES S3 data exports, namely:

S3ExportedForms counts the number of Forms successfully pushed to the configured S3 bucket
S3ExportedSubjects counts the number of Subjects successfully pushed to the configured S3 bucket
S3ExportFailures counts the number of S3 export tasks that have terminated in error

Additionally, an ErrorTracking service is made available so that whenever ErrorTracking.logError is called, an nt:file node in the JCR under /LoggedEvents is created which holds the contents of the logged error. The SlackNotificationsTask is modified so that any logged errors under /LoggedEvents are sent in the periodic Slack alerts update along with the performance metrics recorded under /Metrics. As of the current implementation, all logged errors under /LoggedEvents will be sent to Slack, therefore once the errors have been resolved, these node under /LoggedEvents should be manually deleted so that alerts of these (now resolved) errors are no longer sent to Slack.
As the errors collected by ErrorTracking.logError can potentially be long, I needed to switch from using basic text objects on the Slack API to using attachment objects. This automatically adds a Show more / Show less button for messages that would be too long to be sent to Slack using basic text objects. This, however, slightly changes the appearance of the message of all our Slack alert messages.
For example, a nightly performance metric update message from Cards4PREMs would now look like this,

instead of this,

Testing Instructions

Build this (CARDS-2263) branch including a Docker image with mvn clean install -Pdocker.
cd compose-cluster
python3 generate_compose_yaml.py --dev_docker_image --oak_filesystem --composum --cards_project cards4heracles --slack_notifications --s3_test_container.
You will be prompted to enter a Slack webhook URL. Either create your own Slack channel and app with an incoming webhook or DM me to be added to the #cards-alerts-dev Slack channel and I will provide you with an incoming webhook.
Edit docker-compose.yml and add the environment variable NIGHTLY_SLACK_NOTIFICATIONS_SCHEDULE=0 * * ? * * to the cardsinitial container.
docker-compose build && docker-compose up -d
Every minute, a performance metric update containing Number Of Forms Exported to S3 bucket, Number Of Subjects Exported to S3 bucket, and Number Of Failed S3 export jobs should be sent to Slack.
Visit http://localhost:8080 and login as admin:admin
Create a Demographics Form and a test Patient Subject.
Visit http://localhost:8080/Subjects.s3push?dateLowerBound={TODAY}&dateUpperBound={TOMORROW}. For example, if today is July 12th 2023, you would visit http://localhost:8080/Subjects.s3push?dateLowerBound=2023-07-12&dateUpperBound=2023-07-13.
The next update in Slack should show Number Of Failed S3 export jobs incremented by 1 followed by a stack trace showing a NoSuchBucket error.
Visit http://localhost:8080/bin/browser.html and delete the nt:file node under /LoggedEvents
Visit http://localhost:9001 and login as minioadmin:minioadmin
Click on Create bucket and create a new bucket called uhn.
Visit the Subjects.s3push URL once again (eg. http://localhost:8080/Subjects.s3push?dateLowerBound=2023-07-12&dateUpperBound=2023-07-13)
The next Slack update should increment both Number Of Forms Exported to S3 bucket and Number Of Subjects Exported to S3 bucket by 1.
Create a new Baseline Health Information Form for the same test patient and visit the S3 push URL (eg. http://localhost:8080/Subjects.s3push?dateLowerBound=2023-07-12&dateUpperBound=2023-07-13) once again.
The next Slack update should increment Number Of Forms Exported to S3 bucket by 2 and Number Of Subjects Exported to S3 bucket by 1.
Visit http://localhost:8080/bin/browser.html and delete everything under /Metrics.
The next Slack update should show ERROR: Could not gather any performance statistics.
docker-compose down && docker-compose rm && docker volume prune -f && ./cleanup.sh

@IntegralProgrammer  Is this PR now ready for re-test?

@IntegralProgrammer Is this PR now ready for re-test?

Not yet.

Tested 3 times with the with path system/sling code present as was originally in this PR and for all 3 times, expected data was sent to Slack.
Tested 3 times with the with path system/sling code removed as was introduced in the changes made by @sdumitriu and for all 3 times, the text ERROR: Could not gather any performance statistics was sent to Slack.

I figured out why it doesn't work.
set principal ACL  only works for principals under /users/system/sling, since the principal-based ACLs are not quite standard, but an Oak extension to the default ACL defined by the JCR specification, which isn't enabled by default. Sling enables it, and configures it to only be valid for sling system users.
Either use ... with path when creating the system user, use set acl instead of set principal acl to set rights, or configure the principal ACL implementation to support all system users.
I'll fix it.

I am not getting this error:

If you look at slack the error is:

Also after creating S3 bucket, there is no export happening.
The only thing that worked as expected is :


Add ability to ignore in format string

%% would represent ignoring a part of the string.
For example if the filename is: 01. Artist1- Song1
The format string could be: %tract%. %% to just extra 01 and ignore everything else

Please try the beta and let me know how it goes: https://github.com/NickvisionApps/Tagger/releases/tag/2023.8.3-beta1 :)

@DeWir3 ^

I tried this in 2023.8.3 now and it worked great. Thank you for this as well!
I would recommend adding a small info bubble with the available values as well :)


Links: Xamarin Community Toolkit (2021-01)

Monthly links cleanup.  cc / @davidbritch

Docs Build status updates of commit a97577c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/views/expander.md
:white_check_mark:Succeeded
View

docs/views/mediaelement.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a97577c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/views/expander.md
:white_check_mark:Succeeded
View

docs/views/mediaelement.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


oops

my last commit was bad and i didnt realize
sorry @koenbok i know you trusted me

😳
On Mon, Aug 29, 2016 at 8:01 PM George Kedenburg III <
<EMAIL_ADDRESS>wrote:

my last commit was bad and i didnt realize
sorry @koenbok https://github.com/koenbok i know you trusted me
You can view, comment on, or merge this pull request online at:
https://github.com/koenbok/Framer/pull/410
Commit Summary

oops

File Changes

M framer/Screen.coffee
https://github.com/koenbok/Framer/pull/410/files#diff-0 (4)

Patch Links:

https://github.com/koenbok/Framer/pull/410.patch
https://github.com/koenbok/Framer/pull/410.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/koenbok/Framer/pull/410, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACbYv5Serc1v9HkwcwgE9TLYZAMweIyks5qk50egaJpZM4JwGbh
.

Merged it in, are there no tests for this?


Support user-defined types

For example, if there is a custom scalar type:
scalar Date

Then hypothesis-graphql doesn't know how to generate data for it, but it would be nice to have a way to generate it via custom strategies provided by the user. Something like this:
from hypothesis_graphql import strategies as gql_st
from hypothesis import strategies as st

@given(case=gql_st.query(schema, custom_types={"Date": st.dates().map(str)}
def test_something(case):
    ...

Implementation notes:

Add custom_types argument to the hypothesis_graphql._strategies.queries.query function. Its type is Dict[str, SearchStrategy];
Pass it down to the hypothesis_graphql._strategies.primitives.scalar function;
At the end of the function, add a check if the scalar name is in the custom_types dictionary. Then use a strategy from this there;
If type is nullable, then combine that strategy with st.none() and return it to the caller

@sweco-sedalh as you liked the original comment, I am letting you know that this feature is available in 0.7.0 :)


GEODE-2729: Remove global variables

Remove CacheImpl::getInstance calls
Converted PdxTypeRegistry clear to non-static method
Adding Type Registry to cpp code as a public object.
Convert static PoolManager method calls into instance method calls
Remove PoolFactory/PoolManager global connectionPool singleton
Allows multiple PoolFactories per Cache
Remove default pool logic from Cache into PoolManager
Add mutli-cache integration test

All c++ and .NET tests (unit and integration) passed on Windows, Linux, MacOS, and Solaris X86.

Please fix up commit messages

This was merged without auto-close comment.


[Snyk] Security upgrade com.amazonaws:aws-java-sdk-s3 from 1.12.223 to 1.12.423

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
:sparkles: Snyk has automatically assigned this pull request, set who gets assigned.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

uasdm-fargate-erossync/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

616/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Denial of Service (DoS) SNYK-JAVA-COMFASTERXMLJACKSONCORE-3038426
com.amazonaws:aws-java-sdk-s3:  1.12.223 -> 1.12.423
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
👩💻 Set who automatically gets assigned
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Out of date


Release notes don't seem to update properly

I use Atom on two different machines and I'm seeing anomalies when looking at the release notes. On one of my machines the release notes are always blank with only a button showing to view previous release notes. On the other machine the release notes are old. Here is a current screenshot but keep in mind this isn't the only time the release notes have been outdated compared to the release I was using.
Currently using Atom 0.136 on Windows 8.1 (on two different systems).

Hi all,
Problem is not solved:
Here's what do I see by clicking on : Help -> Release Notes

And here's what my (Win 7) control Panel says:
win_version

I suppose the versions should be the same....

+1
I have this same issue. I'm running version 0.172.0 on Windows 8.1, and the release notes only go up to 0.147.0.

For people still having this issue, can you run the following from the Console tab of the dev tools?
localStorage.getItem('release-notes:version')

I'm running 0.172 but the output of localStorage.getItem('release-notes:version') says "0.149.0"

Great, thanks, that seems to be the issue, for some reason the event that emits the version being downloaded either isn't firing or it is firing with the wrong information.

When I execute localStorage.getItem('release-notes:version') the output says "0.147.0"

running localStorage.setItem('release-notes:version', "0.177.0") and then viewing the release notes updated them. We'll see what happens with the next update.

Just pushed a fix to master for this but because this is auto updater related it will probably take 2 releases to correct itself and show the right version and notes.

Updated to 179, release notes is still stuck on 157 for me

for me as well

he said it might take 2 releases. If it really bothers you run
localStorage.setItem('release-notes:version', "0.179.0") in the console.

I just updated from 177 to 179 and the release notes updated fine. Thanks for the fix!

fixed. Thx :+1:

Seems like we have consensus, great :-)

I'm seeing the problem once again. See screenshot:

hello,
similar situation here:

version in help menu: 0.187.0
release notes: 0.165.0

and auto update does not work
best regards,
ziga

Well isn't this just fantastic :frowning:.
/cc @kevinsawicki

Additional info:

I had older version before (0.17x.x)
(re)installation of version 0.187.0 (current) didn't help.

After following the suggestion and executing localStorage.setItem('release-notes:version', "0.187.0") the numbers were adjusted and release notes show as they should.
Hopefully it will update next time :8ball:
Noticed one thing (hopefully not related) - solarized light syntax theme lost its current line highlight.
Best regards!

I have the same issue.
Version 0.188.0 but release notes displaying 0.184.0 as the last one.
Changing the localStorage version did the trick to update them

Worked for me on the last update. From 0.188.0 to 0.189.0

This has been working for me nicely on 3 machines for a while now.

Closing once again.  If anyone can still reproduce this on 0.192.0 please comment here.

So I was impatient and downloaded the Atom installer instead of waiting for the 193 update today and since then Atom thinks it has to update and restart all the time.

Did it 3 times already, still happening.

A combination of manually changing the version field in local storage and the update actually being available on the update servers seems to have fixed it. Still a problem someone should look into..

@kevinsawicki @50Wliu want me to create a new issue for this or?

want me to create a new issue for this or?

Sure, sounds good.

https://github.com/atom/atom/issues/6482

This is happening for me now between versions 1.1.0 and 1.2.0 (OSX el capitan)

Looks like a regression has popped up with release notes not updating automatically again.

Can confirm

same here, 1.2.1 El Capitan

Win 10 confirmed issue is back also.

Yep, this problem has returned :(

I also have this issue.

can someone lock this issue please.

Please do not lock this issue, please reopen it.

We're really sorry about this issue. The plan is to remove the release notes package and have all the update logic in the about page similar to chrome. See https://github.com/atom/atom/issues/9164 for more details.


Some Puppeteer commands not available in existing installations despite being documented

Note: This update is being raised through Claude Desktop at the request of a user who has performed extensive testing.
Additional findings for this issue:

Attempted Solutions:

Cleared all npm/npx caches
Force-reinstalled the server with --force flag
Specified exact version (@0.5.1) in configuration
Completely uninstalled and reinstalled Claude Desktop
Verified correct configuration and server startup

Version Information:
Available versions: 0.1.0, 0.2.0, 0.3.0, 0.5.0, 0.5.1
All versions exhibit the same behavior - puppeteer_hover and puppeteer_select commands are not accessible.

Server Behavior:

Server connects successfully (verified in logs)
Basic commands (navigate, click, fill, screenshot, evaluate) work correctly
No error messages when connecting server
Server starts cleanly with version 0.5.1 explicitly specified

Environment:

macOS
Node.js v23.3.0
Fresh installation of Claude Desktop
Clean npm/npx caches

This suggests the issue might be:

A documentation mismatch between README and implementation
Commands in development but documented early
A potential limitation in how Claude Desktop interfaces with the Puppeteer server

Would be helpful to know:

Are these commands actually implemented in any version?
If implemented, are there specific requirements to enable them?
Should the README be updated to reflect current capabilities?

Seems this is a duplicate of https://github.com/modelcontextprotocol/servers/issues/207.


PBR spotlight falloff

implements spotlight falloff as defined at pbr-book.org. It's juuust slightly dirty in that it's smuggling the falloff angle (ok. the cos of the falloff angle) in by way of the existing panda3d spotlight exponent property, which... wasn't supported by simplePBR anyway.

Also see Moguri/panda3d-gltf#85 for how the glTF converter converts the outer distance into an exponent.  If you're going to use a linear falloff instead of an exponent, it should probably use the inverse of that calculation.
That said, is there a good reason not to just apply the exponent the way Panda does it here?

The awkward answer is "the systems I'm using Panda3d to prototype for all use inner-angle"
Longer answer: before switching to simplePBR, I'd done similar not-entirely-right work to set an exponent to approximate inner-angle. Later I accidentally discovered a side-effect where, in the regular pipeline, setting the scale of a spotlight had an influence on the inner angle  scale = 1/math.cos(math.radians(self.state.inner_angle)), though setting exponent was still super wonky.  Later, while poking around to see if there was any chance of making area lights work, I found the place where I could make simplePBR do PBR-spec inner-angle, so that's what I did here.
Is there a way to add uniforms to a light instance? If so, I can dispense with the dirty hack and make pbr-inner-angle cleanly opt-in.  (and maybe even figure out how to do area lights)

Closing due to inactivity


Add optional UUID comparison block to insertOrUpdate

Addresses issue #12

Closing this PR as this is no longer an issue after updating UniqueIdentifiable to use an associated type for the uniqueIDValue UniqueIDType.


feature request: custom attribute mapping

It would be nice with a way to customize the attribute mapping, so for example instead of
phoneNumbers: {  "value" : "+4511279865",  "type" : "mobile",  "primary" : false }
it could be mapped to
mobile: "+4511279865"

this feature will be available to certain degree with the release of 2.0.0 at https://scim-for-keycloak.de
The version 2.0.0 is still in development though.


Unable to create a new ignite app

What's going on?
I'm unable to create a new ignite app no matter what template I use.
Steps to reproduce:

ignite new surf --debug
template: Bower
Expo: yes (also tried without, gives me another error)

Errors trace:
  Error: Command failed with exit code 2: ignite add ignite-bowser --debug

  - error.js:56 makeError
    [global]/[gluegun]/[execa]/lib/error.js:56:11

  - index.js:114 handlePromise
    [global]/[gluegun]/[execa]/index.js:114:26

  - task_queues.js:97 processTicksAndRejections
    internal/process/task_queues.js:97:5

      There were errors while generating the project. Run with --debug to see verbose output.

an error occured while installing ignite-bowser boilerplate.
Error: Command failed with exit code 2: ignite add ignite-bowser --debug
    at makeError (/Users/Carl/.config/yarn/global/node_modules/gluegun/node_modules/execa/lib/error.js:56:11)
    at handlePromise (/Users/Carl/.config/yarn/global/node_modules/gluegun/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  command: 'ignite add ignite-bowser --debug',
  exitCode: 2,
  signal: undefined,
  signalDescription: undefined,
  stdout: '\u001b[90m09:40:41\u001b[39m \u001b[35m[ignite]\u001b[39m running add command\n' +
    '\u001b[90m09:40:41\u001b[39m \u001b[35m[ignite]\u001b[39m installing /Users/Carl/Code/side-project/surf/surf/node_modules/ignite-bowser from source npm\n' +
    '\u001b[90m09:40:42\u001b[39m \u001b[35m[ignite]\u001b[39m ignite-bowser 5.0.3 on npm.\n' +
    '\u001b[90m09:40:42\u001b[39m \u001b[35m[ignite]\u001b[39m yarn add ignite-bowser --dev\n' +
    '\u001b[31m----------\u001b[39m\n' +
    '\u001b[31mCommand failed: yarn add ignite-bowser --dev\u001b[39m\n' +
    '\u001b[31m(node:90269) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.\u001b[39m\n' +
    '\u001b[31mwarning<EMAIL_ADDRESS>This should have been a major version bump\u001b[39m\n' +
    '\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
    '\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
    '\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > webpack > watchpack ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
    '\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
    '\u001b[31mwarning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
    '\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
    '\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()\u001b[39m\n' +
    '\u001b[31mwarning solidarity > gluegun > enquirer ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
    '\u001b[31mwarning solidarity > gluegun > prompt-autocompletion > prompt-choices ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
    '\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
    '\u001b[31mwarning "reactotron-react-native ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>+
    '\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "@react-native-community/masked-view@>= 0.1.0".\u001b[39m\n' +
    '\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "react-native-gesture-handler@>= 1.0.0".\u001b[39m\n' +
    '\u001b[31mwarning "@storybook/addon-storyshots ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
    '\u001b[31mwarning "@storybook/addon-storyshots > @storybook/core > @storybook/router > @reach/router ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
    '\u001b[31mwarning "@storybook/react-native > @emotion/native ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>+
    '\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
    '\u001b[31mwarning "@storybook/react-native-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
    '\u001b[31mwarning "@storybook/react-native-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
    '\u001b[31mwarning "jest > jest-cli > jest-config > jest-environment-jsdom ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
    '\u001b[31merror Command failed with exit code 1.\u001b[39m\n' +
    '\u001b[31m\u001b[39m\n' +
    '\u001b[31m----------\u001b[39m',
  stderr: '- adding \u001b[36mignite-bowser\u001b[39m\n' +
    '✖ \u001b[31mignite-bowser\u001b[39m was not able to be installed. Is it a valid NPM module?',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
error installing boilerplate

ignite doctor results:
System
  platform           darwin
  arch               x64
  cpu                4 cores        Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  directory          side-project   /Users/Carl/Code/side-project

JavaScript
  node               12.16.3      /usr/local/bin/node
  npm                6.14.4       /usr/local/bin/npm
  yarn               1.3.2        /usr/local/bin/yarn

Ignite
  ignite-cli         3.5.1        /Users/Carl/.npm-packages/bin/ignite
  ignite src         build        /Users/Carl/.config/yarn/global/node_modules/ignite-cli/build
  generators         {}

Android
  java               9.0.4        /usr/bin/java
  android home       -            undefined

iOS
  xcode              10.0
  Error: Command failed: pod --version
  /Users/Carl/.rbenv/versions/2.3.4/bin/ruby: invalid option -:  (-h will show valid options) (RuntimeError)

  - child_process.js:303 ChildProcess.exithandler
    child_process.js:303:12

  - events.js:310 ChildProcess.emit
    events.js:310:20

  - child_process.js:1021 maybeClose
    internal/child_process.js:1021:16

  - child_process.js:286 Process.ChildProcess._handle.onexit
    internal/child_process.js:286:5

/Users/Carl/.config/yarn/global/node_modules/gluegun/build/index.js:13
    throw up;
    ^

Error: Command failed: pod --version
/Users/Carl/.rbenv/versions/2.3.4/bin/ruby: invalid option -:  (-h will show valid options) (RuntimeError)

    at ChildProcess.exithandler (child_process.js:303:12)
    at ChildProcess.emit (events.js:310:20)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'pod --version',
  stderr: '/Users/Carl/.rbenv/versions/2.3.4/bin/ruby: invalid option -:  (-h will show valid options) (RuntimeError)\n'
}

I've had the same error before running sudo gem install cocoapods which give the error in ignite doctor

Facing same issue.

Same here

Looks like the error is can't find ignite-bowser. Occasionally we see this issue when people have custom .npmrc that prevent NPM/yarn from looking at the global NPM registry. You also have an error where the pod command isn't found. If you use a ruby switcher like chruby make sure you've selected a version where cocoapods is available.

Having the exact same issue
✔ Which boilerplate would you like to use? · ignite-bowser
✔ using the Infinite Red Bowser boilerplate
✔ Would you like to use Expo on this project?
    Why Expo? Expo (https://expo.io) is the fastest way to get started.
    However, Expo support is experimental at this time. If unsure, select No and we'll install the traditional route.
    Additionally, using Expo means you won't be able to add any custom native modules.

   (y/N) · true

We'll initiate your app using Expo. Please note that you won't be able
to use native modules unless you "eject".
More info here: https://docs.expo.io/versions/latest/expokit/eject/
✔ initialized Expo app  in 197.13s
  There were errors while generating the project. Run with --debug to see verbose output.

an error occured while installing ignite-bowser boilerplate.
Error: Command failed with exit code 2: ignite add ignite-bowser
at makeError (/Users/dhritimanbanerjee/.config/yarn/global/node_modules/gluegun/node_modules/execa/lib/error.js:56:11)
at handlePromise (/Users/dhritimanbanerjee/.config/yarn/global/node_modules/gluegun/node_modules/execa/index.js:114:26)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
command: 'ignite add ignite-bowser ',
exitCode: 2,
signal: undefined,
signalDescription: undefined,
stdout: '\u001b[31m----------\u001b[39m\n' +
'\u001b[31mCommand failed: yarn add ignite-bowser --dev\u001b[39m\n' +
'\u001b[31mwarning<EMAIL_ADDRESS>This should have been a major version bump\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
'\u001b[31mwarning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
'\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
'\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > enquirer ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > prompt-autocompletion > prompt-choices ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > enquirer > prompt-question > prompt-choices ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "@react-native-community/masked-view@>= 0.1.0".\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "react-native-gesture-handler@>= 1.0.0".\u001b[39m\n' +
'\u001b[31mwarning "@storybook/addon-storyshots ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
'\u001b[31mwarning "@storybook/react-native-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>+
'\u001b[31merror Command failed with exit code 1.\u001b[39m\n' +
'\u001b[31m\u001b[39m\n' +
'\u001b[31m----------\u001b[39m',
stderr: '- adding \u001b[36mignite-bowser\u001b[39m\n' +
'✖ \u001b[31mignite-bowser\u001b[39m was not able to be installed. Is it a valid NPM module?',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
error installing boilerplate

Having the exact same issue. NOTE: it does seem that the app got generated, in spite of the errors
✔ Which boilerplate would you like to use? · ignite-bowser
✔ using the Infinite Red Bowser boilerplate
✔ Would you like to use Expo on this project?
    Why Expo? Expo (https://expo.io) is the fastest way to get started.
    However, Expo support is experimental at this time. If unsure, select No and we'll install the traditional route.
    Additionally, using Expo means you won't be able to add any custom native modules.

   (y/N) · true

We'll initiate your app using Expo. Please note that you won't be able
to use native modules unless you "eject".
More info here: https://docs.expo.io/versions/latest/expokit/eject/
✔ initialized Expo app in 197.13s
  There were errors while generating the project. Run with --debug to see verbose output.

an error occured while installing ignite-bowser boilerplate.
Error: Command failed with exit code 2: ignite add ignite-bowser
at makeError (/Users/dhritimanbanerjee/.config/yarn/global/node_modules/gluegun/node_modules/execa/lib/error.js:56:11)
at handlePromise (/Users/dhritimanbanerjee/.config/yarn/global/node_modules/gluegun/node_modules/execa/index.js:114:26)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
command: 'ignite add ignite-bowser ',
exitCode: 2,
signal: undefined,
signalDescription: undefined,
stdout: '\u001b[31m----------\u001b[39m\n' +
'\u001b[31mCommand failed: yarn add ignite-bowser --dev\u001b[39m\n' +
'\u001b[31mwarning<EMAIL_ADDRESS>This should have been a major version bump\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > webpack > watchpack > watchpack-chokidar2 ><EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
'\u001b[31mwarning @storybook/addon-storyshots > @storybook/core > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper ><EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1\u001b[39m\n' +
'\u001b[31mwarning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
'\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142\u001b[39m\n' +
'\u001b[31mwarning jest-expo > jest > jest-cli > jest-config > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > enquirer ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > prompt-autocompletion > prompt-choices ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning solidarity > gluegun > enquirer > prompt-question > prompt-choices ><EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "@react-native-community/masked-view@>= 0.1.0".\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency "react-native-gesture-handler@>= 1.0.0".\u001b[39m\n' +
'\u001b[31mwarning "@storybook/addon-storyshots ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
'\u001b[31mwarning "@storybook/react-native-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>+
'\u001b[31mwarning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^8.0.0".\u001b[39m\n' +
'\u001b[31mwarning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>+
'\u001b[31merror Command failed with exit code 1.\u001b[39m\n' +
'\u001b[31m\u001b[39m\n' +
'\u001b[31m----------\u001b[39m',
stderr: '- adding \u001b[36mignite-bowser\u001b[39m\n' +
'✖ \u001b[31mignite-bowser\u001b[39m was not able to be installed. Is it a valid NPM module?',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
error installing boilerplate

Same issue here

Hey @bitbreakr
Do you still have the issue 😉


citra.json: Fix extract_dir

Should fix Could not find 'nightly-mingw'! (error 16) for Citra 1975-20230820.

[x] I have read the Contributing Guide.

@Calinou Please merge this PR instead #1024 since it tackles both Citra manifests.

Sorry for the delay. This needs a rebase before it can be merged.

@sgt's #1024 should be rebased instead.