Klee Wyck: Opening Sketches comparison: 1941 to 1951

First, here's a simple view of the original 1941 text of the first three sketches in Emily Carr’s Klee Wyck:
Now, here's a Google Docs comparison view of the first three sketches in Emily Carr’s Klee Wyck, setting 1941 as the "base text" and tracking changes applied in the 1951 edition:
Problems we need to read around = changes that are not really changes: formatting, spacing.
What alterations stand out to you? How did the text change between 1941 and 1951? And what do you think the significance of those changes are? Point out some alterations (you can use screen captures, and/or describe and quote from some altered passages), and comment on a particular kind of alteration you are seeing. How does this alteration change the way you read the passage, or the sketch as a whole?

I have a lot to say about this.
First and foremost, the majority of the changes I have witnessed involve spacing, spelling, and punctuation. In one paragraph, the word "school-girl" is corrected to "school girl", removing the hyphen. Another instance of changes in punctuation is on page five, where the line "but I found that a grunt of welcome was always waiting inside" was edited in the 1951 version to remove "that" from the sentence. Similarly, on the same page "Papooses tumbled round her" rephrased it to "tumbled around" in 1951. These changes are minor, but the more advanced changes come later.
The missionaries and the church have a lot of information cut for syndication, with several instances of the word "Presbyterian" and dialogue concerning the snootiness of the lesser missionary being cut, making her into a flat character compared to the other missionary. The 1951 version makes the missionaries look less antagonistic, cutting their dialog that demeans the Indians after they tell the origin of Klee Wyck, the scene with them praying in the bedroom, and how indignant they were when the Indians spoke to each other in their native language instead of English. Though a number of the lesser Missionary's dialog is cut, the insults spoken by the greater missionary are also cut.
The most notable instance of censorship, in my opinion, was how the rituals of the dead were cut from the 1951 version. I understand the argument that it could be considered gruesome or disturbing, but it was a part of their culture. In order to understand a culture, a person can't just pick and choose what aspects they want to show, and this was an example of this.
Overall, the 1951 version makes the missionaries appear more heroic, but it makes their characterizations flatter. The lesser missionary doesn't have a lot of defining traits other than her gender and having a daughter, and the greater missionary is no better. Their characterizations, along with the rituals surrounding the dead, are cuts to the story I found the most interesting.

Of the many cuts and alterations that the 1951 edition made on the original 1941 version, the deletion of this last paragraph in Ucluelet was the most disappointing to me:
"Up behind Toxis the forest climbed a steep hill and here in the woods
was one lonely grave, that of 'our only professed Christian Indian',
according to the Missionaries. The Missionaries had coffined him tight
and carried him up the new-made trail with great difficulty. They put
him into the earth among the roots of the trees, away from all his
people, away from the rain and the sun and the wind which he had loved
and which would have rushed to help his body to melt quickly into the
dust to make earth richer because this man had lived."
The total removal and censorship of the last few paragraphs in Ucluelet where Klee Wyck described the Native American tradition of handling their dead was indeed saddening overall, but I felt that the removal of this final powerful passage is what made it truly disrespectful to the novel as a whole. It is so moving and revealing - it's a truly significant passage, especially because it tells the tale of what happens when you rip a person from their cultural roots. This passage is hardly gruesome or gory at all, and yet the editors of the 1951 edition chose to cut this beautiful passage from the story entirely. They could've just edited some of the "gory" words in the passages prior to it to make it palpable for school kids, but they really just ripped the soul out of the whole sketch (and arguably the heart of the story) by taking out that section.
A small point I'd like to make on the notion of keeping thing PG for the kids, by way of cutting out "gore" or "gruesome" passages - It seems they felt fine about cutting those passages describing the Native American tradition of handling their dead, and yet they left this sentence in Tanoo:
"Do you remember what they said about those Indians being asphyxiated by
by the fumes from their engine while they slept?”
Did that one slip past the editors? Granted, I don't think that sentence is very gory, but the passages they cut at the end of Ucluelet are hardly any more gruesome than this. In fact, I actually thought they were less gruesome, but I guess that's just an opinion.
There was another pretty decent bit that was removed from the Tanoo sketch in the 1941 version that I couldn't quite wrap my head around:

I could understand how one might deem the first paragraph "sensitive," on account of the dominating tone Carr puts on the Mission house in relation to the tribe's villiage, but the rest of that passage and the next one that was cut do not seem very religiously/culturally sensitive to me. There are a lot more instances after this bit where the parts containing the missionary girl's arrogance (and also a lot of parts adding to the complexity of her character) are cut as well, and seemingly for no reason. Even sentences as innocent as "The chatter of the missionary's daughter in solemn Skedans sounded like a sheep bell tinkling outside a church," were cut, therein cutting out a huge chunk of the dynamics of her character.

There were many areas where there were only minor revisions that mostly revolved around correcting grammar and such, but where I found more interesting changes was in the large areas that were removed or altered for instance this section talking about the stupidity of the missionary girl, and some lines of the daughter were also removed.

Obviously this was in place to curb the complaints about the missionaries in general, as it may have been deemed offensive or sensitive. Overall a lot of important details were cut throughout the sketches, trying to sanitize it of anything that could be viewed as sensitive, which frankly diminishes the work through oversimplification and removal of the authors intent. It changes how the entire story is interpreted as a whole.

When comparing Emily Carr's 1941 text to her 1951 revision, I noticed some changes that stood out more than others.

This section of the text in 1951 revision, the paragraph describing the missionaries was rewritten. I am not exactly sure why, but they were described differently the second time. The 1941 text ay have been too lengthy when describing these characters in my opinion. This however, does not make much of an impact when comparing both texts.

In this image, you are able to see the multiple changes in the text. It appears to me that most of these revisions are a word being crossed out only for it to be rewritten the same way. I'm not sure if I am missing something but these changes are not even changes at all. Usually these deal with spelling errors and punctuation marks but I cannot see the difference.
To be honest, I feel as if the 1951 version did a better job at pulling out wordy messes and getting to the point. Clearly describing something without taking up too much space. After all, that is the job of a revision of a text right? Not many big changes were made, only small ones here and there. Although the biggest change I was able to find was this:

In some places, chunks of text were taken out and thrown away. They may have been too wordy or maybe just not needed to get the story across. However, this happens multiple times throughout the text. Cutting these details out may be good for some people, but bad for others. These details were obviously important in 1941 so who is to say they do not matter in 1951? This sort of thing is what really changes the story as a whole.

Looking past all of the changes made to the grammar and spacing, and spelling changes you will find a lot of things cut that were almost more critical of the missionaries. While these cuts tend to provide a much quicker explanations in some revisions I feel they are leaving out details that are taking away the character of some of them. There were several spots where the 51 version omitted things that would bring a different light to a character or several characters. For example there is an omission that describes the one missionary girl as clumsy and stupid.

Along with this there are some things describing some processes that the missionaries do that were taken out. Overall a lot of the bigger things that were taken out were things directly about missionaries and their character. This kind of thing really does change how people view them and changes a meaning as a whole.

While analyzing the Ucluelet, I realized that the passages that were removed seemed to be removed because paragraphs were too wordy. The changes made the passage easier to understand. The picture below shows a good example as a full paragraph was taken out and replaced with "had the most dignity".

In the Tanoo version, we also see an example of this. In this example, we see that "and the missionary girl's sneer" was removed. Because of this, there is less detail and information and it makes the passage more simple, with the same message.

Analyzing the Tanoo portion of the sketches, it is noticeable that a lot of the edits were of the same word being crossed out and rewritten the same. I am not sure why that is so, but it seemed to take up a significant portion of the edits.

Other edits seemed to be of shortening or deleting sentences from the paragraph, which helped to make the sections less wordy and easier to read through. These edits helped keep the story going smoothly without adding too much detail, and I think improved the flow of the work.

It is also interesting that there were 2 whole paragraphs taken out of the piece. These 2 paragraphs focused on describing the Indians and the mosquito bites on everyone, and I'm glad it was removed, as it seemed like way too much detail for the scene that is taking place.

when comparing 1941 to 1951 I'd notice that a lot of paragraphs and sentence where just taken out.

Going farther it was interesting a lot of it was the same just some words got crossed out. It was weird due to the fact words would get crossed off but be re written. As well as it had a lot of grammar correction it seemed or at least it was slightly reworded.

During my comparison of the 1941 and the 1951 texts, I noticed that most of the differences are of smaller stature in terms of them being spacing and capitalization differences.
however, there are some larger differences between the two texts with an example on the very first page of text where after I did a comparative analysis of the two documents through google, there is roughly half a paragraph removed signifying a significant difference between them.
That being so, there are not many more examples of multiple sentences being crossed out. As I had mentioned in the first sentence, the reoccurring theme of differences lies in capitalization and spacing, there are dozens of spacing differences in just the first 3.5 pages that I used comparison analysis on.
I will a screenshot or two to show some examples in space differential.

As you can see in the above images, there are 2 examples of a sentence or more being changed between the two texts while spacing is the primary difference.

While looking for the changes that were made in the 1951 edition, I came across a lot of small changes that had been made. They were usually a word here and there that had been taken out or a string of words in sentences that had been taken out. Most of the time you were still able to understand what was being said regardless if they had been altered in a small way. Also, I came across instnaces were some words in the 1941 edition that were lowercase but made to be capitalized in the 1951 revision.

However, as I was furthermore looking through the text I was able to see that a lot of paragraphs had been removed in the 1951's revision. This had seemed to occur quite often and with it happening so much it had shortened the the length of the original immensely. As I read what was removed and after remembering what we had discussed in class, it seems that the sections removed were passages that may be seen as offensive or inappropriate. Due to this being taught in classrooms it may not have been what was needed to remain in order for it to be appropriately taught to students. Here are some of the biggest edits that I came across that were removed in the 1951 revision:

While reading, I noticed that there were a lot of paragraph breaks, whether this is because of the Google Doc or the actual text I wouldn't know. Other than that though I have noticed some changes to the text. For example, on the eighth page, an entire paragraph is deleted from the story. This paragraph talked about what the missionaries were doing in the bedroom. So in the 1951 version, "The room was deathly still." is what comes immediately after instead of that paragraph, as can be seen in the screenshot below.

Another way something was deleted from the original story can be seen below. In the 1951 version, only a lesser missionary speaks while the other one is censored after what they say.

One final thing I noticed is that something does get censored majorly about halfway through the Google Doc. It seems to discuss a place that is surrounded by death, giving us some disturbing imagery of human remains as well as talking about Indians. The screenshot below is not big enough to show the entirety of what was censored, but this goes on to the next page and then the next chapter begins.

As can be seen by these screenshots, anything was not safe from being censored, whether it was a sentence or an entire page, the story from 1951 is really different from the original.

There are a vast number of changes between the two versions of text, and they range in size from omitting a hyphen or comma all the way to omitting entire paragraphs of description. The aforementioned grammatical corrections (though some can be called mere adjustments, as some words are moved to the next line without being grammatically incorrect) did not alter my reading experience, and instead providing more context into the evolution of writing conventions.

Here's an example of some words being moved to the next line.
In contrast to these minor corrections, the omitting of large portions of descriptive text definitely altered my reading experience, in a number of ways. The first of these is the censorship of imagery. Censorship and I haven't always got along, in fact during my junior year of highschool I wrote a speech on why we should just do away with the idea altogether. Though this was an extreme take from 16 year-old me, I don't completely disagree with it even today. Take this excerpt for example.

I've excluded the latter half, as this portion is enough to get the message across. These three paragraphs are a grim, eerie, downright disturbing description of the burial rituals conducted for the "Indian dead". I believe this is an important piece to leave in the entire text, as the imagery is staggering and wraps itself in a veil of seriousness that could otherwise be broken.
All that being said, I can definitely understand why this is censored. This next excerpt is a bit beyond me though.

It's almost as if the very concept of undergarments was deemed too scandalous and left out of the printing, which is a bit silly to me. Maybe the target demographic was changing, and in response these changes were, or vice versa.

Reading over both editions, the common error to occur seemed to be the lack or capitalization. There were several different spots where this happened in each version. Here is just one example of a failure to capitalize:

In this comparison to both of these versions, I noticed that the grammar had changed in different ways. Some of the ways are adding hyphens, commas, new capitalization. For example, on the first page first sentence you see missionaries in lower case in the older version and then in the newer version, it is capitalized. another thing is on the first page and in she wrote "a fifteen year old school girl", but changed it to " fifteen-year-old school girl.

For this assignment, I really love how Dr. Bondar was able to use a Google Doc to visually show comparisons. I think this was much better than the Variorum Viewer. The dots and highlights that were constantly on Variorum Viewer were confusing, and I think a Google Doc is better in the long run, especially in the remote environment that we are currently in. More specifically, I like how Google Docs is more specific and detailed in regards to the changes that are made. The more detail there is, the better.

In terms of noticeable changes, I would say that a big trend was the constant change in grammar between the two versions. This ranged from a variety of things such as structure in a paragraph and adding/ changing of punctuation, such as changing “Missionary’s” to "missionary's”.

Another big trend that could be noticed throughout the comparison of the two versions is the complete deletion of long part of the story to simplify into a couple of words. I personally think that this was done to try to get rid of unnecessary content that was not needed to comprehend the story and to keep the reader engaged. I think this is a strategy that was very well implemented.

In addition, there were several times where thoughts were revised, but at the same time not deleted in an effort to make the thoughts of the author more clear to the reader. An example of this is when “made my curiosity and the missionary girl’s sneer” was replaced with “made my curiosity”.

When analyzing the differences between then 1941 version and 1951 of Emily Carr's Kyee Wyck, obvious trends I found were differences in punctuation and grammar. Although, I find that to be a commonly seen trend in revised pieces of work. The most interesting finds I found between both works was the amount of large paragraphs that were eventually removed in the later 1951 edition of _Kyle Wyck. I found these most interesting because some if not most of these paragraphs were  extremely detailed and personally I thought held onto major development in the story.  In the image below is an example of a screen capture I've decided to analyze. These two paragraphs hold common meaning and develop the stories characters such as Miss Missionary and Louisa. Keeping these paragraphs in the 1951 edition would've been a great opportunity to further develop what these characters attributes are.


Traefik stops working entirely if one of the ingresses is not correctly configured.

Do you want to request a feature or report a bug?
Bug
What did you do?
I use Traefik 2.2.1 with Cert-manager 0.15
After the initial setup with helm, I deployed an Kubernetes Ingress with an reference to a certificate. (that doesn't exist yet)
kind: Ingress
apiVersion: networking.k8s.io/v1beta1
metadata:
  name: prometheus-operator-grafana-ingress
  annotations:
    traefik.ingress.kubernetes.io/router.entrypoints: websecure
    traefik.ingress.kubernetes.io/router.tls: "true"
spec:
  rules:
    - host: {{ .Values.grafana_domain }}
      http:
        paths:
          - backend:
              serviceName: prometheus-operator-grafana
              servicePort: 80
  tls:
    - hosts:
        - {{ .Values.grafana_domain }}
        secretName: ingress-prod-certs-tls

What did you expect to see?
I expected now to see that traefik fails to setup the route until cert-manager requested the certificate and wrote it to ingress-prod-certs-tls. After that I expected traefik to create a route and recover from the failed state.
What did you see instead?
Traefik stops serving all routes (also the ones that worked) if there is problem with only one ingress.
I the logs I see this error message telling me correctly that ingress-prod-certs-tls  is missing. However while it does this it stops to serve all other routes. If Cert-manager is configured to work with traefik to request certs it can't do because all ingress routes stopped working.
2020-05-12T06:43:26.813871706Z time="2020-05-12T06:43:26Z" level=error msg="Error configuring TLS: secret monitoring/ingress-prod-certs-tls does not exist" providerName=kubernetes ingress=prometheus-operator-grafana-ingress namespace=monitoring
Output of traefik version: (What version of Traefik are you using?)
Traefik 2.2.1
Helm Chart: 8.1.5

What is your environment & configuration (arguments, toml, provider, platform, ...)?
Kubernetes 1.17

sorry my fault, had problems with LB


[INTEGRATION][Airflow] Add a facet to capture job/run dependencies (a task is dependent on another task in the DAG)

In Airflow, tasks in a DAG depend on each other in a workflow.
We want to capture those dependencies.

How is that different from ParentRunFacet?

This is different from the parent run. it is the task dependency:
the task in the DAG that was the predecessor in the workflow

I believe this PR should resolve that issue: https://github.com/apache/airflow/pull/39520

https://github.com/apache/airflow/pull/39520 has been merged


Probably unnesessary if statemant on line 61

Hi,
there is following code on line 61:
if(query.length < 3);
It's not really doing something useful, probably it's part of some other code?

You're welcome to submit a PR!


I have a checkpoint but ugatit cant find it

wtf

What path did you put the checkpoint file in?

UGATIT's path : /mnt/d/UGATIT
checkpoint's path : /mnt/d/UGATIT/checkpoint
(checkpoint folder was automatically created)

Did you train U-GAT-IT ?

I got this error while training it

@1mpossibleHacker
what is the error message ?

Searching for checkpoint
couldnt find a checkpoint
load failed
(this is not exactly what it said but you understood)

load failed is not error...
Wait for training. Then it works.

dude but what about the checkpoint. please reopen it i need answers

@1mpossibleHacker
When trained, checkpoints are automatically saved for every save_freq iterations.
https://github.com/taki0112/UGATIT/blob/master/main.py#L18

it doesnt countinue after saying load failed. so i cant train

iget a trouble "Load FAILURE"  i have some models andI've put it in the folder
Why does it appear?  Do I need to change the model path?


Eddie bickham

completed mvp as well as animating the boxes

MVP

[x ]

Stretch

[ x]

What Looks Great

MVP complete! Nice work
Frequent and descriptive commits
Code is well formatted and easy to read
Great file structure

What Could Be Improved

Cleaner Nav code

What Could Be Added

More pages/Animation

Rating (1-3)


error: unrecognized subcommand 'index'

Hello, we've been trying to use dr-prg to our research but somehow after installing the program with docker and singularity separately, the index subcommand is not there.. Do you have any idea what went wrong?

Thanks for trying DrPRG!  @mbhall88 is unfortunately on holiday for a couple of weeks, and I think really only he can help. Sorry for the delay!

Hello Iqbal,
Thank you for your quick reply. It's not a problem at all, we researchers need breaks once in a while after all 😃 As alternative we're also currently trying Clockwork for Mycobacterium tuberculosis, and I'm astounded to find out that the link in the official WHO document leads to your GitHub too. I'll let you know if we have succeded on using your program. Thanks for your hard work.
Cheers!

Hi there! ok good. I just wanted to clarify one thing - DrPRG and clockwork do different things. Clockwork does decontamination of human reads, and SNP/indel calling, and optionally you can run Mykrobe also to predict resistance. But if you just want resistance prediction while waiting for Michael to return, you don't need the whole of clockwork, Mykrobe alone will do. You probably know this, but I just wanted to check
(Yes, i was amazed to find the WHO mentioning clockwork!)

Hi @ptrmtb which container are you using? i.e. how are you pulling the container and what address? And what commands are you running to use index and what is the output?


MWAA 2.4.3 support

What type of PR is this? (check all applicable)

[ ] Refactor
[X] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Dependency Update
[ ] Release

Description
Add MWAA 2.4.3 support
Add XCOM table
Add development notes
Related Tickets & Documents

Related Issue # N/A
Closes # N/A

Linting
Have you done linting by issuing ./build.sh lint command?

[X] Yes
[ ] No, I need help with linting

Testing
Have you run testing by issuing ./build.sh unit command?

[X] Yes
[ ] No, I need help with writing tests

Documentation
Have you updated the README appropriate for this PR?

[X] Yes
[ ] No, README does not need any changes for this PR

Changelog
Have you updated the CHANGELOG with the changes you are making in this PR?
Please use Added, Removed, and/or Changed subsections under the Unreleased section.

[X] Yes
[ ] No, I need help

Terms of Contribution
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hello @mathiasflorin ! Appreciate your contribution to the repo! We will get the PR review started soon! Thank you!

@mathiasflorin Let's start by fixing the build failures please. Could you please lint and push? Thank you!

Yes, I ran the lint before but I forgot to run it again after adding a minor commit with small fixes. Thanks for your review. I will rerun the unit test and lint in a few hours and push the required changes to fulfil the black format.

@crupakheti Could you please help me to resolve this pipeline error To fix this, change your publishing workflow to use an event that forks of your repository cannot trigger (such as tag or release creation, or a manually triggered workflow dispatch).

Hey @mathiasflorin, please don't worry about that error. I will need to change the publishing workflow to fix it. I have allocated time to review your PR tomorrow. Thank you!

I believe it would be beneficial for the csv.writer to use a specific delimiter to avoid confusion. According to Copilot, a pipe delimiter (|) can offer several advantages over a comma, depending on your specific needs and the nature of your data:
Less Common in Data: Commas are frequently used within data fields (e.g., in addresses, names, or descriptions), which can lead to complications even if the fields are quoted. Pipes are less likely to appear in the actual data, reducing the need for escaping or quoting.
Readability: For human readers, pipe-delimited files can sometimes be easier to read and parse visually, especially when spot-checking data.
Locale Independence: In some locales, commas are used as decimal separators (e.g., 3,1415 instead of 3.1415), which can cause confusion. Using a pipe avoids this issue.

@mathiasflorin Looks like the testing was mostly done on the local container. I will need to push some changes based on the CDK deployment error I got. Will make a push soon. Thanks!

Thank you @crupakheti . I deployed the stack only once, but I ended up using a manually created 2.4.3 MWAA environment for further testing.”

It appears there is an issue during the XCOM restore where task instance data is missing for recent entries.
[2024-08-14, 11:49:38 UTC] {logging_mixin.py:117} INFO - {'dag': 'restore_metadata', 'dag_run': 'manual__2024-08-14T10:14:30.852628+00:00', 'tasks': ['setup => success', 'restore_start => success', 'restore_slot_pool => success', 'teardown => upstream_failed', 'notify_success => upstream_failed', 'restore_variable => success', 'restore_log => failed', 'restore_active_dag => upstream_failed', 'restore_end => upstream_failed', 'restore_connection => success', 'restore_task_instance => success', 'restore_xcom => running', 'restore_task_fail => running', 'restore_trigger => success', 'restore_dag_run => success', 'restore_job => success'], 'status': 'Fail'}
[2024-08-14, 11:49:38 UTC] {standard_task_runner.py:102} ERROR - Failed to execute job 7697223 for task restore_xcom (insert or update on table "xcom" violates foreign key constraint "xcom_task_instance_fkey"
DETAIL:  Key (dag_id, task_id, run_id, map_index)=(freshness_dag, freshness_query, scheduled__2024-08-06T20:51:54.235544+00:00, -1) is not present in table "task_instance".

I will investigate whether the issue can be resolved by making the task instance table downstream of the XCOM table during export. Another option would be to implement an inner join during export to ensure only XCOM data for completed task instances is exported.

Based on the ERD diagram, it seems that dag_run and trigger should be exported before task_instance, as task_instance has foreign keys referencing these tables. Although I didn’t encounter an import error, it might be necessary to implement downstream relationships for these tables and any other exported tables with foreign keys in the future.

@mathiasflorin Thank you for your contribution! This PR has been merged to main!


Width of Bar Chart increased abnormally in case of single Value

After applying filters/Calculation if there is single data (single value) to be represented in the graph . Then the width of the particular bar chart is more than the normal behaviour.
Refer codepen URL for example.
Expected Behaviour :
Width of graph should be normal as it behaves in case of mutliple values.

This is working as intended. You can set options to change the width if you prefer a behavior other than the default

https://www.chartjs.org/docs/latest/charts/bar.html


Add OSSL_CMP_CTX_get0_validatedSrvCert()

add  OSSL_CMP_CTX_get0_validatedSrvCert()
correct OSSL_CMP_validate_msg()
change ossl_cmp_ctx_set0_validatedSrvCert() to ossl_cmp_ctx_set1_validatedSrvCert()
add respective tests as well as the -srvcertout CLI option using the new function.

[x] documentation is added or updated
[x] tests are added or updated

@t8m, your comments have been addressed.

Rebased to solve trivial merge conflict.
Also here reviewing can continue.

@beldmit still OK?

I had to fix a trivial merge conflict in util/libcrypto.num.
@beldmit and @t8m, could you please reconfirm.

This pull request is ready to merge

Merged - thanks @beldmit and @t8m


MacOS: Window resizing causes the whole UI to stretch

See the screenshot below, this seems distracting and hopefully unnecessary. MacOS 11

Uh oh. How do we think this happened @Subject38? Might you have time to test with me via TeamViewer again some time soon?

Did I split the scale into (x,y) components and forget a min()? That's my first thought but I think we would have caught it so it might be more Apple fuckery, they cannot seem to keep their API's straight.

Also if Seth has no time @eliheuer can test with me just as well. I could not find an affordable macOS virtualization service with GPU support so have not been able to determine another way to test, and the Foundation is (I am) naturally quite against the idea of purchasing an Apple computer to do local testing.

@ctrlcctrlv It is a bit hard to see what is going on in just a screenshot, so I made a YouTube video showing the bug here: https://www.youtube.com/watch?v=VzSWypCgkdQ
This is on a 2020 Apple M1 Mac Mini, macOS 11.6.5.

On Arch Linux resizing the window makes MFEKglif crash before I ever see any stretching, but this seems like another bug in itself.
This is MFEKglif v1.1.1b2-25-gc874d5a (“Metafontverse”), compiled @ 2022年08月21日(日)　16時43分57秒(午後)　協定世界時-0700.
[2022-08-21T23:51:44Z ERROR mfek_ipc::module] Module MFEKmetadata is not available. MFEK is modular software; it will still run but some features will not be available. For the best experience, please install all available MFEK modules into your PATH.
[2022-08-21T23:51:44Z INFO  MFEKglif::settings] Configuration directory is "/home/eli/.config/MFEK/glif"
[2022-08-21T23:51:44Z WARN  MFEKglif::command] Keybinds XML invalid (Invalid command string!), using default
[2022-08-21T23:51:57Z WARN  MFEKglif::user_interface] Failed to draw frame. This can happen when resizing due to VkError(ERROR_DEVICE_LOST); if happens otherwise, file an issue.

panicked at 'called `Option::unwrap()` on a `None` value', /home/eli/.cargo/registry/src/github.com-1ecc6299db9ec823/rafx-api-0.0.14/src/extra/swapchain_helper.rs:347:14

[2022-08-21T23:51:57Z INFO  MFEKglif::util] Wrote backtrace to /tmp/error_log_1661125917.txt
[1]    9222 abort (core dumped)  cargo run --release -- examples/Q_.glif

I just tested on Arch Linux and was able to resize the window without any stretching of the UI, video example here: https://www.youtube.com/watch?v=ZmyjAzNq7hs
So this is a MacOS bug, happy to help look into this, I'll see if I get the same thing on a older Intel non-M1 mac next.

I have determined the fastest way to fixing Mac issues is for me to just use someone else's Mac PC and try a bunch of things until I fix it.
Thanks for showing me the issue, it's just as weird as I thought. For sure @Subject38 and I would have noticed this. So, I can't really fix it until someone has time to dedicate to a remote session.
Because I also tried with @Subject38 to just send patches I thought might work in the past and it was a ton of useless work for both of us, in terms of patch management, copying, pasting, it not working, me getting back a video, etc.

Humorous new tag:

I updated to macOS 12.5.1 tonight and I still get the same stretching when resizing the window. So macOS 11 was not the issue.

Just tested on my local machine and I can confirm this issue exists. I feel like I might have noticed it before but didn't realise it was a big issue since after resizing all the UI elements go back to normal. I'm honestly not entirely sure what might be causing this behavior in the first place...

after resizing all the UI elements go back to normal

Oh so this isn't even that big a deal but @Subject38 there's a bigger problem
I'm glad I tried to do a full build again on @t0lva's PC because I literally was on the phone w/her for an hour trying to build and it kept erroring out and it turns out we're blocked on https://github.com/aclysma/skulpin/issues/108#issuecomment-1221852846 for new VulkanSDK versions
What VulkanSDK do you have?

(That's @t01va not @t0lva.)

(Housekeeping: I'm downgrading this bug to minor and making a new one for the VulkanSDK update issue.)

sub38@fear ~ % vulkaninfo | grep Version
WARNING: [MoltenVK] Code 0 : Unrecognized CreateInstance->pCreateInfo->pApplicationInfo->apiVersion number (0x004020c6). Assuming MoltenVK 1.1 version.
Vulkan Instance Version: 1.2.198

Looks like version 1.2.198.
I never updated after initially installing so that's likely why...

Thank you that jives perfectly w/@eliheuer's experience. I opened #323 for the SDK issue.
For the resizing...it's basically #295. Sorry I just don't think it's a big deal but of course it's still a bug so I'm leaving it open.

I just tested this on an Intel mac on macOS 11 and still get the same stretching.
I think from a UI/UX perspective it is a major issue, but I'm a UI snob I guess.

@eliheuer I agree it looks really wonky and ugly (same with the blackout effect that happens on Linux). I'll be really honest, I just don't know how to fix it. Like there are callbacks and Vulkan something or other going on here, it's all wrapped up with Skulpin's Vulkan renderer in general and I am just as likely to make it worse as make it better.
@MatthewBlanchard is usually our 3D expert but he's been a bit MIA of late so if he doesn't fix it I don't know when/if it will be, and personally I don't see it as a major problem compared to all the other ones, so that's why I've tagged it low-priority. That doesn't mean it needs to be low priority for you or anyone else including Matt, the tags just reflect my thinking as this project's maintainer. Anyone else is free to pitch in. :-)

This issue has been merged with, and supersedes, #295.

By the blackout effect, are y'all referring to the flickering/resetting effect that I receive? Screen recording to demonstrate the behavior on my system (Linux/NixOS/Wayland, using native Wayland, not XWayland). I don't see any stretching or shrinking unfortunately.

Yes, the issues are one and the same and have the same root upstream cause.

It's worth noting what I wrote at https://github.com/imgui-rs/imgui-rs/pull/582#issuecomment-1363584268. To fix #323 we will be switching in the new year to @lucasmerlin's egui_skia, OpenGL by default, with Vulkan optionally, across all GUI MFEK modules like this one.
That might fix this; in my tests so far it does. It also might not. But @jackeisnt the core GUI rendering has such large planned changes I don't think it's worth fixing this issue unless it's through the planned upgrade path. :-)

I'm very happy to hear about egui_skia and the big changes to the GUI rendering. Thanks!


simple join on mysql not working gui hang

Hi
i run just run :
select i.i_id from item i,order_line o where o.ol_i_id=i.i_id
and the GUI hand - no running query in the mysql
this run successfully  on mysql or mysql workbench .
order_line have  600k records
item have 1m records
to create tables
CREATE TABLE order_line (
ol_w_id int(11) NOT NULL,
ol_d_id int(11) NOT NULL,
ol_o_id int(11) NOT NULL,
ol_number int(11) NOT NULL,
ol_i_id int(11) DEFAULT NULL,
ol_delivery_d datetime DEFAULT NULL,
ol_amount int(11) DEFAULT NULL,
ol_supply_w_id int(11) DEFAULT NULL,
ol_quantity int(11) DEFAULT NULL,
ol_dist_info char(24) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL,
PRIMARY KEY (ol_w_id,ol_d_id,ol_o_id,ol_number),
KEY sec_i_id (ol_i_id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE item (
i_id int(6) NOT NULL,
i_im_id int(11) DEFAULT NULL,
i_name varchar(24) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL,
i_price decimal(5,2) DEFAULT NULL,
i_data varchar(50) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL,
PRIMARY KEY (i_id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Although this really is a simple JOIN, the amount of data retrieved there is huge. So, I don't think is a problem with the JOIN query itself but the amount of data returned there. To make it clear, could you try to run with a limit:
select i.i_id from item i,order_line o
where o.ol_i_id=i.i_id
limit 100

Btw, we already have an issue open for querying thousand of records: https://github.com/sqlectron/sqlectron-gui/issues/129

Since the issue is answered and we have an issue for querying thousands of records, I'll close this one.


Request: support item origin url

The origin url property stores the original url for urls that are changed by wallabag. My specific use case is to retrieve youtube urls (wallabag changes these to point to oembed xml documents).
API added in: https://github.com/wallabag/wallabag/pull/3553

Hi George,
thanks for submitting the issue. Unfortunately, I'm not actively developing the API anymore.
PRs are still welcome though. From looking at the source code from my smartphone, I think the property just needs to be added to the WallabagItem class, that should do the trick.


Reset the VF if failure occurs before the netconf is cached

This PR fixes following issue:
#212

Thanks for the PR!
/lgtm

/cc @adrianchiris

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 14 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 36.535%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/sriov/sriov.go
0
14
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
213

Relevant Lines:
583

💛  - Coveralls

I would like to know how can I run these PR tests myself if I want to? I have seen /retest in one of the PR, wasn't able find any other. Thanks.

@SchSeba kindly review and trigger tests here.

/test-all

/cc @adrianchiris @SchSeba
PTAL :)

This will not work as expected from here
https://github.com/k8snetworkplumbingwg/sriov-cni/pull/222/files#diff-30bddd0b0a3414968a5fa92d19e50ad3168e273728fd52ba867afbc442defe62R115
r, err := ipam.ExecAdd(netConf.IPAM.Type, args.StdinData)

you can't allocate the new err variable or it will not get caught by the defer function.

Fixed, there was another place with similar allocation that is also fixed. kindly check.


Adding Parent Autoclose Workflow

What does this PR do?
Adding autoclose workflow to parent repository.
Test Plan
Tested in https://github.com/Evdogs/.github/blob/main/.github/workflows/autoclose.yml
Validated in https://github.com/EVDOG4LIFE/sdk-for-go/actions/runs/10118323588
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)

@stnguyen90 - please create a Organization Owned PAT with read only access to members, and add it as an org wide secret like so:


Buffer overflow while querying Quake1 server rules

Hi, I'm experiencing a buffer overflow when I try to query some Quake1 servers while asking for server rules.
Basic query (works):
$ qstat -qs <IP_ADDRESS>:26003
ADDRESS           PLAYERS      MAP   RESPONSE TIME    NAME
<IP_ADDRESS>:26003   0/8   0/0     intro    121 / 0   QRF_COOP

Server rules query (do not work):
qstat -R -qs <IP_ADDRESS>:26003
ADDRESS           PLAYERS      MAP   RESPONSE TIME    NAME
*** buffer overflow detected ***: qstat terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7f47ea648c4e]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f47ea6e8e8c]
/lib/x86_64-linux-gnu/libc.so.6(+0x116e80)[0x7f47ea6e6e80]
qstat[0x40ceae]
qstat[0x40e97a]
qstat[0x40eb1d]
qstat[0x41f6ab]
qstat[0x402333]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f47ea5f0a40]
qstat[0x403829]
======= Memory map: ========
00400000-00445000 r-xp 00000000 fc:02 219994                             /usr/bin/qstat
00645000-00646000 r--p 00045000 fc:02 219994                             /usr/bin/qstat
00646000-0064c000 rw-p 00046000 fc:02 219994                             /usr/bin/qstat
0064c000-0065a000 rw-p 00000000 00:00 0
00a82000-00aa3000 rw-p 00000000 00:00 0                                  [heap]
7f47ea138000-7f47ea14e000 r-xp 00000000 fc:02 6030633                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f47ea14e000-7f47ea34d000 ---p 00016000 fc:02 6030633                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f47ea34d000-7f47ea34e000 rw-p 00015000 fc:02 6030633                    /lib/x86_64-linux-gnu/libgcc_s.so.1
7f47ea34f000-7f47ea5d0000 rw-p 00000000 00:00 0
7f47ea5d0000-7f47ea790000 r-xp 00000000 fc:02 6030624                    /lib/x86_64-linux-gnu/libc-2.21.so
7f47ea790000-7f47ea990000 ---p 001c0000 fc:02 6030624                    /lib/x86_64-linux-gnu/libc-2.21.so
7f47ea990000-7f47ea994000 r--p 001c0000 fc:02 6030624                    /lib/x86_64-linux-gnu/libc-2.21.so
7f47ea994000-7f47ea996000 rw-p 001c4000 fc:02 6030624                    /lib/x86_64-linux-gnu/libc-2.21.so
7f47ea996000-7f47ea99a000 rw-p 00000000 00:00 0
7f47ea9a0000-7f47ea9c4000 r-xp 00000000 fc:02 6030594                    /lib/x86_64-linux-gnu/ld-2.21.so
7f47eabbf000-7f47eabc3000 rw-p 00000000 00:00 0
7f47eabc3000-7f47eabc4000 r--p 00023000 fc:02 6030594                    /lib/x86_64-linux-gnu/ld-2.21.so
7f47eabc4000-7f47eabc5000 rw-p 00024000 fc:02 6030594                    /lib/x86_64-linux-gnu/ld-2.21.so
7f47eabc5000-7f47eabc7000 rw-p 00000000 00:00 0
7f47eabc7000-7f47eabc9000 rw-p 00000000 00:00 0
7ffe87c75000-7ffe87c96000 rw-p 00000000 00:00 0                          [stack]
7ffe87da8000-7ffe87daa000 r--p 00000000 00:00 0                          [vvar]
7ffe87daa000-7ffe87dac000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Abandon

It fails while trying an strcpy in send_rule_request_packet function in qstat.c.

You can experiment with server <IP_ADDRESS>:26003 but probably anyone from this list:

http://www.qtracker.com/server_list_details.php?game=quake

This was tested on the last revision of the master branch.

Yeah, the code has sprintf(), strcpy(), and strcat() in it.. those can probably be converted over to snprintf(), strlcopy(), and strlcat() at some point.
I'll look into it and put a PR in. :+1:
(As I get warnings when I compile about those functions on OpenBSD)

there are some older methods which could indeed lead to issues, PRs welcome

@stevenh @illwieckz  - I've made a start converting sprintf to snprintf and the other functions as well. I've not quite gotten all of them converted over yet, however I ran a while loop through that list from qtracker.com and I didn't get any crashes this time. Once I've updated the functions, I'll send a PR.

nice!!

@illwieckz @stevenh According to the struct for q_rule, the 'data' element is: unsigned char data[19];
So that's only 19 characters allocated for rules, so any rules over that length will overflow.
If that strcpy gets converted to a strlcpy, then you will only see the first 19 chars of the rules is my guess. If you wanted more, than q_packet struct would need changing I think. (With a longer data[] length)

No sure what you mean by q_rule as thats only used in one place, if you mean rules in general then they are dealt with differently.

Hi @illwieckz  - Are you able to reproduce this at all with the latest version? I attempted to do so myself and used the following one-liner:
for srv in $(qstat -qwm master.quakeservers.net:27000 | awk '{ print $2}'); do qstat -qws ${srv}; done
(You can use any of the master quakeworld servers here: https://www.quakeservers.net/quakeworld/master_servers/
I wasn't able to reproduce this at all.


Revert travis to earlier point

test to see if can unstick travis using earlier version

@marscher hmm, no luck getting travis to report its status back to github.   I tried known good configurations but it is still stuck.  You had mentioned a log someplace, but I wasn't able to located it.   I don't want to start messing with the action settings as I don't know what I am doing.


How to prevent screen capture in kivy?

How to prevent screen capture or disable screenshot in kivy that protect content in App?
Platform: Windows or Android

I don't believe we have a solution for that, and that seems outside of the projects scope.


CSS to make footnotes superscript

When using footnote notation [^1] the resulting HTML link is not superscript.
What are the CSS changes I need to make to make it superscript again?

Does not seem theme specific, perhaps a question better suited for jekyll? https://github.com/jekyll/jekyll/issues


Update Description, Tag and some other Java files affected by Tag com…

Update Description to only allow one word
Update Tag to allow multi descriptions
Adding some TODO to some files affected by Tag class. Currently I am adding empty Set into the constructor.

Codecov Report

Merging #149 into master will increase coverage by 0.20%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master     #149      +/-   ##
============================================
+ Coverage     63.78%   63.98%   +0.20%
- Complexity      403      404       +1
============================================
  Files            81       81
  Lines          1306     1305       -1
  Branches        111      112       +1
============================================
+ Hits            833      835       +2
+ Misses          435      431       -4
- Partials         38       39       +1

Impacted Files
Coverage Δ
Complexity Δ

...a/seedu/address/model/description/Description.java
17.64% <0.00%> (-17.65%)
2.00 <0.00> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

src/main/java/seedu/address/model/tag/Tag.java
80.00% <72.72%> (+17.50%)
11.00 <2.00> (+1.00)

...ava/seedu/address/logic/commands/RetagCommand.java
87.50% <100.00%> (ø)
9.00 <0.00> (ø)

...a/seedu/address/logic/parser/TagCommandParser.java
100.00% <100.00%> (ø)
5.00 <0.00> (ø)

...ain/java/seedu/address/storage/JsonAdaptedTag.java
100.00% <100.00%> (ø)
7.00 <0.00> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update db64a65...ab608a4. Read the comment docs.


Add a wiki: Unofficial Feed The Beast Wiki

Link to origin wiki: https://ftb.fandom.com
Link to destination (independent) wiki: https://ftbwiki.org
The only problem I've found with this redirection (as I've witnessed on my own, making a tampermonkey script to autoredirect me) is that both wikis have differing content; the fandom wiki has information the independent one doesn't, and vice versa.

It looks like there's a content page disparity in favor of the Fandom Wiki (29k vs. 24k). The Fandom Wiki also appears to be considered the official Wiki as well, and is the Wiki linked from https://www.feed-the-beast.com/.

Note that the FTB fandom wiki is planning to fork as well to a different website so this FTB unofficial wiki may soon be obsolete for this extension.

Re-commenting on this since it was re-submitted. Still a large content gap + Fandom wiki still seems to be considered official and linked from the official site.


[Feature Request] Translation String extension conflict

First of all, thanks for awesome this package!
Is your feature request related to a problem? Please describe.
When using  easy_localization there is conflict with String extension .tr() when just import route manager.
Even though GetX has a translation feature, my current project require a more robust solution due to requirement to support plural and gender modifiers, plus unified translation json file shared with web-frontend
Describe the solution you'd like
Move public translation utilities to another index file and keep route manager file exclusive for routing.
import 'package:get/route_manager.dart';
import 'package:get/translation_manager.dart';

Same request... I can't update the GetX package if this isn't fixed.

fixed in https://github.com/jonataslaw/getx/commit/cfacb4a33f1e9b9a5f17401fd115966180d5422a


svg duplicated in listview

the package works fine with a single SVG image, but when it comes to Listview. it duplicates some of the images

Unlikely; this is probably a bug in the code that manages the list view, which is not a part of jovial_svg.
If this were a bug in the library, at a minimum you would need to include code or enough information so that the problem can be easily reproduced.  Generally, this means providing a short stand-alone program that shows the problem.


Node Mac artifact build fix

This should fix the current problems with building the Node artifacts on Mac and with running the Node distrib tests on Mac.

With these changes, the Node artifact build is completely green. I haven't been able to verify the latest changes to the distrib tests, but they work on my machine.


BUG: Missing beautifulsoup dependency

Beautifulsoup is used as a dependency in dhlab.legacy.nb_external_files and dhlab.legacy.nbtext, which is automatically imported in the root __init__.py file. However, it's not listed as a dependency in the pyproject.toml-file, so any import to dhlab will crash in an empty environment.
Steps to reproduce
python -m .venv venv
source .venv/bin/activate  # or .venv/Scripts/activate on windows
pip install dhlab
python -c "import dhlab"

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\marie\dette_er_en_test\.venv\Lib\site-packages\dhlab\__init__.py", line 3, in <module>
    from dhlab.legacy import (
  File "C:\Users\marie\dette_er_en_test\.venv\Lib\site-packages\dhlab\legacy\nbtext.py", line 19, in <module>
    from bs4 import BeautifulSoup
ModuleNotFoundError: No module named 'bs4'

Possible fixes
I see a couple of possible fixes, and I'm happy to submit a pull request based on your preference🙂.
1. Add BeautifulSoup as a dependency
Add the following line to the pyproject.toml-file
beautifulsoup4 = "*"

2. Add BeautifulSoup as an optional dependency and use lazy imports BeautifulSoup
Add the following lines to the pyproject.toml-file
[tool.poetry.group.legacy]
optional = true

[tool.poetry.group.legacy.dependencies]
beautifulsoup4 = "*"

And move the BeautifulSoup import in dhlab/legacy/nbtext.py and dhlab/legacy/nb_external_files.py
dhlab/legacy/nb_external_files.py:
from warnings import warn

[...]

def get_urns_from_docx(document) -> List:
    """Find all URNs specified in a Word document,
    typically a ``.docx`` file."""

    try:
        from bs4 import BeautifulSoup
    except ImportError:
        raise ImportError("beautifulsoup4 is needed for `get_urns_from_docx`")

    with zipfile.ZipFile(document, 'r') as zfp:
        with zfp.open('word/document.xml') as fp:
            soup = BeautifulSoup(fp.read(), 'xml')

    return re.findall("[0-9]{13}", str(soup))

dhlab/legacy/nbtext.py:
from warnings import warn

[...]

def text_from_html_file(filename):
    """Get a flat list of tokens from a file"""
    try:
        from bs4 import BeautifulSoup
    except ImportError:
        raise ImportError("beautifulsoup4 is needed for `text_from_html_file`")

    with open(filename, encoding='utf-8') as f:
        content = f.read()
    soup = BeautifulSoup(content, 'html.parser')
    text = []
    for para in soup.find_all('p'):
        text += tokenize(para.text)
    return text

3. Add BeautifulSoup as an optional dependency and remove the from dhlab.legacy import (...) statement in __init__.py
Add the following lines to the pyproject.toml-file
[tool.poetry.group.legacy]
optional = true

[tool.poetry.group.legacy.dependencies]
beautifulsoup4 = "*"

And remove the following lines from dhlab/__init__.py
from dhlab.legacy import (
    graph_networkx_louvain,
    module_update,
    nb_external_files,
    nbpictures,
    nbtext,
    token_map,
)

Thanks for pointing this out! We recently switched to poetry. Seems to be some teething problems. Should be fixed now with 2.28.2

And thanks for the detailed post! Very helpful! Are you using dhlab for something in particular?

I made this little streamlit app to explore the collections in a fun way: https://github.com/MarieRoald/bookshelfpoetry


python_mrpt_ros: 2.13.7-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository python_mrpt_ros to 2.13.7-1:

upstream repository: https://github.com/MRPT/python_mrpt_ros.git
release repository: https://github.com/ros2-gbp/python_mrpt_ros-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.11.2
previous version for package: null

I noticed that your package uses the BSD-3 license, but the package.xml simply lists "BSD": https://github.com/MRPT/python_mrpt_ros/blob/68e313f02e2693f1424677c3ff515adaf2406cce/python_mrpt/package.xml#L10. You should probably use the full SPDX identifier ("BSD-3-Clause") there.

After consulting other people, we don't really enforce this, so I'll just merge this.


Load stats file via http

Sorry @owais—opened this too early 😅

Yeah, that makes total sense to me! I opened the PR by accident after modifying a fork as a proof-of-concept, but a dynamic loader class would be the best way to implement this properly for sure.


Rally point - poke doesn´t send email anymore

Because I had working Slack integration, I´m confident, that in version 1.1.6 was working everything as expected, after upgrade to version 1.2, we don´t getting emails anymore. Even I set debug to 3 I don´t see anywhere in php / nginx logs errors.

Just making double-sure you didn't overwrite this setting while upgrading to v1.2.0: you did set up the RALLY_SET setting in the PATHFINDER.NOTIFICATION section of the app/pathfinder.ini config file, right? 😄
There's not much else to change in this file, so it could be overlooked pretty easily (at least I did during the last upgrade >.>)

Nope, RALLY_SET has working email address set, have double check that.

Started poking around myself a bit, looks like the From: header is malformed when it is sent to the SMTP server.
I've captured some logs and the value is changed from Pathfinder<EMAIL_ADDRESS>to <Pathfinder><EMAIL_ADDRESS>somewhere while being passed around by pathfinder and the library. Currently still trying to figure out where exactly that is.

Looks like this was caused by the Fat Free Framework upgrade from 3.5.1 -> 3.6.0, committed in 03c1d53fd613e3750045510746ad6d0980b8e137. To be more precise, F3 changed their email-parsing regex which leads to it parsing the value provided by pathfinder incorrectly.
Pathfinder sets the From: address as Pathfinder<EMAIL_ADDRESS>Since F3 changed to detecting the From-"Name" in double-quotes (using the regex (?:".+?" )?(?:<.+?>|[^ ,]+)), it will recognise the Pathfinder part as a separate address, thus incorrectly adding a second set of chevrons.
This leads to further issues since the SMTP servers receives a MAIL FROM: values of <Pathfinder><EMAIL_ADDRESS>instead of the expected<EMAIL_ADDRESS>Since that is obviously an incorrect value, the SMTP servers reject the mail and notifications thus don't get sent out.
The simple fix? Adding two double-quotes around the Pathfinder string. Sounds stupid, but works, confirmed it with my instance 😄
I'll be sending a PR shortly @exodus4d

I added a new "SMTP" page to the wiki


building python benchmark workers requires python3.4 (not available on current ubuntu)

and python3.4 is not available on ubuntu 16.04LTS. That leads to ugly hacks.
See
https://github.com/jtattermusch/grpc/blob/ab0a72765588009b5dd840f7bef8d0738310ad53/tools/gce/linux_performance_worker_init.sh#L95
in https://github.com/grpc/grpc/pull/8375

This is a team-only team-internal issue; I don't see any reason for it to block the 1.1.0 release. Punting (please correct me if there's something I'm missing!).

@jtattermusch, @kpayson64: please assess a priority for this issue?

I'm not sure what the desired outcome is, if we want to test against Python3.4, then we need Python3.4 installed.  Is this issue suggesting that we test against an arbitrary python 3 version, whatever happens to be on the system?


Error: EACCES: permission denied

node -v: 11.15.0
npm -v : 6.10.1
Os: Arch Linux x86_64
Log: log.txt
I try every command with sudo and without it as well using multiple ways:
--unsafe-perms
--force & rebuild node-sass --force
Here is the supposedly install devDependencies in my pakcage.json: (Notice node-sass is installed)

"devDependencies": {
"clean-webpack-plugin": "^3.0.0",
"css-loader": "^3.1.0",
"file-loader": "^4.1.0",
"html-loader": "^0.5.5",
"html-webpack-plugin": "^3.2.0",
"mini-css-extract-plugin": "^0.8.0",
"node-sass": "^4.12.0",
"sass-loader": "^7.1.0",
"style-loader": "^0.23.1",
"webpack": "^4.37.0",
"webpack-cli": "^3.3.6",
"webpack-dev-server": "^3.7.2",
"webpack-merge": "^4.2.1"
},

But here is what npm says about it: ( Notice node-sass isn't intalled )
npm list --depth 0

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
npm audit fix(Log):log2.txt
I also try npm update node-tar with no success.

Alright just to try since permission ownership was the issue I deleted node_modules and run npm install again wich indeed fix the problem!
..............................................................................................................................................................................................


Support -o json and -o name on get

supports -o or --output json|yaml|name (default yaml)
the '---' is now at the beginning of each yaml document, not the end, to follow the standard practice
the JSON is the one from the API, no reordering
it works on get: on list and single item

Why?
Because JSON is more automatable (?) than YAML.
eg:
$ conduktor get Application -o json | jq -r '.[].metadata.name'
purchase-pipeline
tracker
support

Because single line is more readable at a glance than YAML: (the best thing will be when you can "get all" with that)
$ ./conduktor get ApplicationInstance -o name
ApplicationInstance/tracker-dev
ApplicationInstance/support-dev
ApplicationInstance/purchase-pipeline-dev

Examples:

on one item:

$ ./conduktor get Application support -o json
{
  "apiVersion": "v1",
  "kind": "Application",
  "metadata": {
    "name": "support"
  },
  "spec": {
    "title": "The support",
    "description": "The support of our company",
    "owner": "support-project"
  }
}

on a list:

./conduktor get Application -o json
[
  {
    "apiVersion": "v1",
    "kind": "Application",
    "metadata": {
      "name": "purchase-pipeline"
    },
    "spec": {
      "title": "Purchase pipeline",
      "description": "money money money",
      "owner": "admin"
    }
  },
  {
    "apiVersion": "v1",
    "kind": "Application",
    "metadata": {
      "name": "tracker"
    },
    "spec": {
      "title": "User tracking",
      "description": "Track our dear customers",
      "owner": "tracker-project"
    }
  },
  {
    "apiVersion": "v1",
    "kind": "Application",
    "metadata": {
      "name": "support"
    },
    "spec": {
      "title": "The support",
      "description": "The support of our company",
      "owner": "support-project"
    }
  }
]

default behavior unchanged, yaml (except for the '---'):

$ conduktor get Application
---
apiVersion: v1
kind: Application
metadata:
    name: purchase-pipeline
spec:
    title: Purchase pipeline
    description: money money money
    owner: admin
---
apiVersion: v1
kind: Application
metadata:
    name: tracker
spec:
    title: User tracking
    description: Track our dear customers
    owner: tracker-project
---
apiVersion: v1
kind: Application
metadata:
    name: support
spec:
    title: The support
    description: The support of our company
    owner: support-project

Could be great to add some test in test_final_exec.sh
It won't test the output but at least that the command does not crash when using -o


Update README.md of Priority encoder

README format:

Introduction: Describe the circuit in few lines
Truth table: Create a center aligned truth table for the given circuit
Schematic and Realization of Circuit: Attach an image of the schematic and realization of the given circuit. Source should be cited in case image is taken from web.

Reference:
Refer to these README files for more clarity regarding format.

Half Adder
Full Adder

Please assign this to me @Vedant-02

Assigned @theshubhamgour

Can i work upon this issue .?

Assign this issue to @Radiosnack

Assigned @Radiosnack

Did you merge my PR ?


[WIP] fastlane for Android

Work in progress

Added declaration of supported operating systems for every action
Added verifying of supported operation system when running each action
Added tests

Related issue: https://github.com/KrauseFx/fastlane/issues/169

Hello, I'm trying to automate the upload of new APK files to the google play store for the company I work for. I'm interested to contribute to your fastlane project, I was wondering if you have any pointers about how to automate the initial APK upload for newly created applications? Thank you

Coverage increased (+3.01%) to 72.19% when pulling 15e4fa36411d52d1687e32cf6c076bda7807f7d9 on feature/android into fd2c7e9dfe8bbe5669e032292cbda34b24ab95c8 on master.

Coverage increased (+3.01%) to 72.19% when pulling 15e4fa36411d52d1687e32cf6c076bda7807f7d9 on feature/android into fd2c7e9dfe8bbe5669e032292cbda34b24ab95c8 on master.

Coverage increased (+5.03%) to 74.21% when pulling bbccc8e0fe360ca0cbc9bc5fe864d51cfadf06bc on feature/android into fd2c7e9dfe8bbe5669e032292cbda34b24ab95c8 on master.

Coverage increased (+5.14%) to 74.32% when pulling 73a1d9767b34630631b8e0de82c1adc0a3dac96b on feature/android into fd2c7e9dfe8bbe5669e032292cbda34b24ab95c8 on master.

Increasing all the test coverage :+1:

Coverage increased (+5.36%) to 74.67% when pulling ac90908573be5425fa2e86bece7d26fedd64c84f on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+6.8%) to 76.11% when pulling 75c99b6db6939b42deefeed6291708321d321d24 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.55%) to 77.86% when pulling<PHONE_NUMBER>a072317306c961db649a24ca66c6f0 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.55%) to 77.86% when pulling<PHONE_NUMBER>a072317306c961db649a24ca66c6f0 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.66%) to 77.97% when pulling 653711a1cc77ea3825e95ad3d1604a5497e6ef91 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.66%) to 77.97% when pulling 3df07ce375c40485d9c8cae90a02c26b0a650ffc on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.66%) to 77.97% when pulling 63d651b5518caccb2bdb7c50694f0cddae6497b5 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.66%) to 77.97% when pulling 63d651b5518caccb2bdb7c50694f0cddae6497b5 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.66%) to 77.97% when pulling ab3ffc37f3a765cb8eb011a39826deddcb8e3020 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.71%) to 78.02% when pulling d7d0d3dc0a009920485127a874a9fb1ad5ed941a on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+5.87%) to 75.18% when pulling a80602cc17fa31115c2df1c4f4fdb402b4a9356d on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+5.87%) to 75.18% when pulling 7daa4ee87f6eb70d30c82d115e81b7405ac3a86c on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+5.87%) to 75.18% when pulling 18bf733b6d1c6c6affcca3260f6d8587be29f43b on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

Coverage increased (+8.71%) to 78.02% when pulling 037d078a9b29c5ad6ba3171e8ecb88ac33b14fd3 on feature/android into f326f6181d479303d2ba95fe591eb12d8fe7d754 on master.

@adennen did you have any success trying to automate the initial APK upload for applications?

@shoshRose APK upload works already, yes :+1:

@KrauseFx for first APK too? can you direct me to any documentation. What about creating a new app in Google Play Console?
thank you!

@shoshRose Creating a new app is not possible due to the missing API. I haven't tried the initial APK upload yet, sorry.

@KrauseFx i'm guessing some Capybara magic will be necessary like in ios..

@shoshRose I'm getting rid of all front-end scraping with https://spaceship.airforce, we'll find a way around this :+1:

@KrauseFx looking forward to it. Please update :)


[Error]: Unique constraint failed on the fields: (session_uuid)

For the last few days, my self-hosted version of Umami keeps crashing. When I check the application logs, I see an endless stream of these errors and then the server gets overloaded and shuts down.
The Unique constraint failed on the fields part is the one that's repeated well over a thousand times in the logs.
2020-09-27T16:09:48.722408876Z app[web.1]: Ap [Error]: Unique constraint failed on the fields: (`session_uuid`)
2020-09-27T16:09:48.722437377Z app[web.1]:     at iy.request (/app/node_modules/@prisma/client/runtime/index.js:196:54)
2020-09-27T16:09:48.722442587Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
2020-09-27T16:09:48.722447212Z app[web.1]:   code: 'P2002',
2020-09-27T16:09:48.722451522Z app[web.1]:   meta: { target: [ 'session_uuid' ] }
2020-09-27T16:09:48.722455517Z app[web.1]: }
2020-09-27T16:15:52.782199022Z app[web.1]: Ap [Error]: Unique constraint failed on the fields: (`session_uuid`)
2020-09-27T16:15:52.782231631Z app[web.1]:     at iy.request (/app/node_modules/@prisma/client/runtime/index.js:196:54)
2020-09-27T16:15:52.782236995Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
2020-09-27T16:15:52.782241698Z app[web.1]:   code: 'P2002',
2020-09-27T16:15:52.782245688Z app[web.1]:   meta: { target: [ 'session_uuid' ] }
2020-09-27T16:15:52.782249653Z app[web.1]: }
2020-09-27T16:27:53.661297831Z app[web.1]: Ap [Error]: Unique constraint failed on the fields: (`session_uuid`)
2020-09-27T16:27:53.661331610Z app[web.1]:     at iy.request (/app/node_modules/@prisma/client/runtime/index.js:196:54)
2020-09-27T16:27:53.661337294Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
2020-09-27T16:27:53.661341907Z app[web.1]:   code: 'P2002',
2020-09-27T16:27:53.661355859Z app[web.1]:   meta: { target: [ 'session_uuid' ] }
2020-09-27T16:27:53.661359670Z app[web.1]: }
2020-09-27T16:29:44.665302396Z app[web.1]: Ap [Error]: Unique constraint failed on the fields: (`session_uuid`)
2020-09-27T16:29:44.665335030Z app[web.1]:     at iy.request (/app/node_modules/@prisma/client/runtime/index.js:196:54)
2020-09-27T16:29:44.665340744Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
2020-09-27T16:29:44.665345312Z app[web.1]:   code: 'P2002',
2020-09-27T16:29:44.665349624Z app[web.1]:   meta: { target: [ 'session_uuid' ] }
2020-09-27T16:29:44.665353574Z app[web.1]: }
2020-09-29T08:48:20.047069134Z app[web.1]: /app/node_modules/geolite2-redist/scripts/download-helper.js:36
2020-09-29T08:48:20.047103431Z app[web.1]: 						throw new Error(`Could not fetch checksum for ${edition.name}\n\nReceived:\n${checksum}`);
2020-09-29T08:48:20.047112278Z app[web.1]: 						^
2020-09-29T08:48:20.047116847Z app[web.1]:
2020-09-29T08:48:20.047120732Z app[web.1]: Error: Could not fetch checksum for GeoLite2-Country
2020-09-29T08:48:20.047124721Z app[web.1]:
2020-09-29T08:48:20.047128523Z app[web.1]: Received:
2020-09-29T08:48:20.047132309Z app[web.1]: <?xml version="1.0" encoding="utf-8"?>
2020-09-29T08:48:20.047136673Z app[web.1]: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2020-09-29T08:48:20.047140749Z app[web.1]:  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2020-09-29T08:48:20.047144663Z app[web.1]:
2020-09-29T08:48:20.047148526Z app[web.1]:
2020-09-29T08:48:20.047152350Z app[web.1]:     <title>503 Backend unavailable, connection timeout</title>
2020-09-29T08:48:20.047157195Z app[web.1]:
2020-09-29T08:48:20.047170626Z app[web.1]:
2020-09-29T08:48:20.047174321Z app[web.1]:
Error 503 Backend unavailable, connection timeout

2020-09-29T08:48:20.047178072Z app[web.1]:
Backend unavailable, connection timeout

2020-09-29T08:48:20.047181763Z app[web.1]:
Guru Mediation:

2020-09-29T08:48:20.047185210Z app[web.1]:
Details: cache-del21738-DEL<PHONE_NUMBER><PHONE_NUMBER>

2020-09-29T08:48:20.047188835Z app[web.1]:

2020-09-29T08:48:20.047192079Z app[web.1]:
Varnish cache server

2020-09-29T08:48:20.047195648Z app[web.1]:
2020-09-29T08:48:20.047198947Z app[web.1]:
2020-09-29T08:48:20.047202387Z app[web.1]:     at IncomingMessage.<anonymous> (/app/node_modules/geolite2-redist/scripts/download-helper.js:36:13)
2020-09-29T08:48:20.047206187Z app[web.1]:     at IncomingMessage.emit (events.js:327:22)
2020-09-29T08:48:20.047209647Z app[web.1]:     at endReadableNT (_stream_readable.js:1220:12)
2020-09-29T08:48:20.047213117Z app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:84:21)
2020-09-29T08:48:20.059069441Z app[web.1]: npm ERR! code ELIFECYCLE
2020-09-29T08:48:20.059534046Z app[web.1]: npm ERR! errno 1
2020-09-29T08:48:20.061504045Z app[web.1]: npm ERR<EMAIL_ADDRESS>start: `next start`
2020-09-29T08:48:20.061770538Z app[web.1]: npm ERR! Exit status 1
2020-09-29T08:48:20.062033155Z app[web.1]: npm ERR!
2020-09-29T08:48:20.062275673Z app[web.1]: npm ERR! Failed at the<EMAIL_ADDRESS>start script.
2020-09-29T08:48:20.062513391Z app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T08:48:20.073971098Z app[web.1]:
2020-09-29T08:48:20.074331495Z app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T08:48:20.074555871Z app[web.1]: npm ERR!     /app/.npm/_logs/2020-09-29T08_48_20_067Z-debug.log

You need to upgrade to the latest version in master.

You need to upgrade to the latest version in master.

I see that I'm one version behind right now. Was this a bug that got fixed? Just curious.

Yes, there are always bug fixes going straight to master. I generally develop new features in the dev branch, but master will always have that latest usable version. The version under releases is not always the latest.

Yes, there are always bug fixes going straight to master. I generally develop new features in the dev branch, but master will always have that latest usable version. The version under releases is not always the latest.

Understood! I'll make sure to keep track of master now instead of Releases. Thanks for the clarification!

Hi @mikecao , I'm still having this issue with 1.7.0. It will always crash when there are a lot of visits.
{"log":"PrismaClientKnownRequestError2: Unique constraint failed on the fields: (`session_uuid`)\n","stream":"stderr","time":"2020-11-30T05:54:01.147810834Z"}
{"log":"    at PrismaClientFetcher.request (/app/node_modules/@prisma/client/runtime/index.js:79355:15)\n","stream":"stderr","time":"2020-11-30T05:54:01.147836302Z"}
{"log":"    at runMicrotasks (\u003canonymous\u003e)\n","stream":"stderr","time":"2020-11-30T05:54:01.147841399Z"}
{"log":"    at processTicksAndRejections (internal/process/task_queues.js:97:5) {\n","stream":"stderr","time":"2020-11-30T05:54:01.147846595Z"}
{"log":"  code: 'P2002',\n","stream":"stderr","time":"2020-11-30T05:54:01.147850677Z"}
{"log":"  clientVersion: '2.12.1',\n","stream":"stderr","time":"2020-11-30T05:54:01.147854454Z"}
{"log":"  meta: { target: [ 'session_uuid' ] }\n","stream":"stderr","time":"2020-11-30T05:54:01.147858389Z"}
{"log":"}\n","stream":"stderr","time":"2020-11-30T05:54:01.14786212Z"}
{"log":"PrismaClientKnownRequestError2: Unique constraint failed on the fields: (`session_uuid`)\n","stream":"stderr","time":"2020-11-30T06:12:39.971949193Z"}
{"log":"    at PrismaClientFetcher.request (/app/node_modules/@prisma/client/runtime/index.js:79355:15)\n","stream":"stderr","time":"2020-11-30T06:12:39.971976282Z"}
{"log":"    at runMicrotasks (\u003canonymous\u003e)\n","stream":"stderr","time":"2020-11-30T06:12:39.971981362Z"}
{"log":"    at processTicksAndRejections (internal/process/task_queues.js:97:5) {\n","stream":"stderr","time":"2020-11-30T06:12:39.971986113Z"}
{"log":"  code: 'P2002',\n","stream":"stderr","time":"2020-11-30T06:12:39.971990091Z"}
{"log":"  clientVersion: '2.12.1',\n","stream":"stderr","time":"2020-11-30T06:12:39.971993859Z"}
{"log":"  meta: { target: [ 'session_uuid' ] }\n","stream":"stderr","time":"2020-11-30T06:12:39.971997794Z"}
{"log":"}\n","stream":"stderr","time":"2020-11-30T06:12:39.972016383Z"}
{"log":"PrismaClientKnownRequestError2: The provided value for the column is too long for the column's type. Column: \u003cunknown\u003e\n","stream":"stderr","time":"2020-11-30T06:51:35.667570222Z"}
{"log":"    at PrismaClientFetcher.request (/app/node_modules/@prisma/client/runtime/index.js:79355:15)\n","stream":"stderr","time":"2020-11-30T06:51:35.668759345Z"}
{"log":"    at runMicrotasks (\u003canonymous\u003e)\n","stream":"stderr","time":"2020-11-30T06:51:35.668765087Z"}
{"log":"    at processTicksAndRejections (internal/process/task_queues.js:97:5) {\n","stream":"stderr","time":"2020-11-30T06:51:35.668769494Z"}
{"log":"  code: 'P2000',\n","stream":"stderr","time":"2020-11-30T06:51:35.668773529Z"}
{"log":"  clientVersion: '2.12.1',\n","stream":"stderr","time":"2020-11-30T06:51:35.668780775Z"}
{"log":"  meta: { column_name: '\u003cunknown\u003e' }\n","stream":"stderr","time":"2020-11-30T06:51:35.668784555Z"}
{"log":"}\n","stream":"stderr","time":"2020-11-30T06:51:35.668788609Z"}
{"log":"PrismaClientKnownRequestError2: Unique constraint failed on the fields: (`session_uuid`)\n","stream":"stderr","time":"2020-11-30T07:03:29.465787166Z"}
{"log":"    at PrismaClientFetcher.request (/app/node_modules/@prisma/client/runtime/index.js:79355:15)\n","stream":"stderr","time":"2020-11-30T07:03:29.465813436Z"}
{"log":"    at runMicrotasks (\u003canonymous\u003e)\n","stream":"stderr","time":"2020-11-30T07:03:29.465818459Z"}
{"log":"    at processTicksAndRejections (internal/process/task_queues.js:97:5) {\n","stream":"stderr","time":"2020-11-30T07:03:29.465823834Z"}
{"log":"  code: 'P2002',\n","stream":"stderr","time":"2020-11-30T07:03:29.465827868Z"}
{"log":"  clientVersion: '2.12.1',\n","stream":"stderr","time":"2020-11-30T07:03:29.465831656Z"}
{"log":"  meta: { target: [ 'session_uuid' ] }\n","stream":"stderr","time":"2020-11-30T07:03:29.465835501Z"}
{"log":"}\n","stream":"stderr","time":"2020-11-30T07:03:29.465839316Z"}

There are two kinds of errors here:

PrismaClientKnownRequestError2: Unique constraint failed on the fields: (session_uuid)
PrismaClientKnownRequestError2: The provided value for the column is too long for the column's type. Column: \u003cunknown\u003e


Using realm in my app, I can publish my app on the iOS AppStore, but when I upload the app to the Mac AppStore it reports an error.

What happened?
After I upload the App to TestFight, it generates an error :
ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '' for key 'com.apple.application-identifier' in 'NowDO.app/Contents/Frameworks/realm.framework/Versions/A/Resources/librealm_dart.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier .
Repro steps
After I upload the App to TestFight, it generates an error
Version
1.0.0
What Atlas Services are you using?
Atlas Device Sync
What type of application is this?
Flutter Application
Client OS and version
MacOS
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response

Hi @whaleHan,
This must be an issue related with XCode project settings.
It is a common issue and you can find many references searching in Google.
If you have set your profile and certificates correctly and you don't have any red issues in Signing & Capabilities options, the deployment should be successful. We don't have any issue with the deployment. Do you have some expired certificates?
Did you try to clean and build again?
Go to XCode menu -> Product>Clean Build Folder,
then Priduct->Build and Product->Archive again.
When you build make sure you have selected "Any iOS devices".
If this doesn't help, please share your XCode Runner Settings if it is possible?

Hi,
we have investigated and found an issue related to your problem. We will be fixing it.
Cheers

Hi we have merged the fix for this and it will be part of our next release very soon.
Thanks for reporting.

@whaleHan We have just released the fix for this in<EMAIL_ADDRESS>

@blagoev I still get this error on version 1.0.2

@blagoev
This problem is still present on version 1.0.2

@blagoev
I'm also still getting this error on version 1.0.2

Having an empty value incom.apple.application-identifier in liberal_dart.dylib seems to be what's causing the issue. I'm not entirely sure that this key should be here at all.
According to the provisioning profile, the bundle contains a key value that is not allowed: '' for the key 'com.apple.application-identifier' in '<redacted>.app/Contents/Frameworks/librealm_dart.dylib'

Thanks for the report. We will investigate more.

A quick question: Did anyone try doing flutter clean after upgrading the realm dependency?

I usually run flutter clean before I run flutter build macos --release.
To add more context I started out with realm 0.8.0+rc and this issue was not present in that version. Attached is a screenshot of the signing dialog showing that the entitlements are not present for librealm_dart.dylib.
I upgraded to 0.9.0+rc to see if the entitlements were present and they were not.
I then updated to 0.10.0+rc to check the same thing and the entitlements first started showing up in this version.
It seems like something changed between 0.9.0+rc and 0.10.0+rc with regards to the signing.

We have released the fix for this in 1.0.3. You can try it out. We will be investigating the issue with newer versions of xcode.


feat: create/run sample app containers after image built completed (#90)

This PR adds an additional step to the pullApplication action - it creates a pod with the 2 containers.
It doesn't get started yet, i'm going to work on it on a follow-up PR but it can be start manually from the pod/container page of desktop.
EVentually you should see the green check on create application

and a new pod similar to

If you start it you would probably see it fail because the modelservice is slow at loading the model and the sample app when trying to connect to the model service it fails.
So what you can do is

start the pod
the model service container should appear green
check the logs and wait until you see it is completely loaded and running (e.g there should be http://localhost:7860 url message)
start the sample app container
now you can open it on the browser

video demo -> https://drive.google.com/file/d/16hWByy2J17s88o_O6WyFcCwPAVczH3E8/view

When testing on my machine (Fedora Linux), the image is correctly built and the container is started, but the container stops after a few seconds.
I cannot debug the container started by the AI Studio, but here is what I get when I run the container from the CLI (do I need to add some options to the run command?):
podman run -it chatbot-example  bash
Loaded as API: http://<IP_ADDRESS>:7860/ ✔
Traceback (most recent call last):
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_exceptions.py", line 10, in map_exceptions
    yield
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_backends/sync.py", line 206, in connect_tcp
    sock = socket.create_connection(
  File "/usr/lib64/python3.9/socket.py", line 844, in create_connection
    raise err
  File "/usr/lib64/python3.9/socket.py", line 832, in create_connection
    sock.connect(sa)
socket.timeout: timed out

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_transports/default.py", line 67, in map_httpcore_exceptions
    yield
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_transports/default.py", line 231, in handle_request
    resp = self._pool.handle_request(req)
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 268, in handle_request
    raise exc
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 251, in handle_request
    response = connection.handle_request(request)
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_sync/connection.py", line 99, in handle_request
    raise exc
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_sync/connection.py", line 76, in handle_request
    stream = self._connect(request)
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_sync/connection.py", line 124, in _connect
    stream = self._network_backend.connect_tcp(**kwargs)
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_backends/sync.py", line 213, in connect_tcp
    sock.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1)
  File "/usr/lib64/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/opt/app-root/lib64/python3.9/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
    raise to_exc(exc) from exc
httpcore.ConnectTimeout: timed out

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/chatbot/chat_ui.py", line 22, in <module>
    chat = Chat(model_endpoint)
  File "/chatbot/chat_ui.py", line 9, in __init__
    self.client = Client(self.endpoint)
  File "/opt/app-root/lib64/python3.9/site-packages/gradio_client/client.py", line 133, in __init__
    self.config = self._get_config()
  File "/opt/app-root/lib64/python3.9/site-packages/gradio_client/client.py", line 720, in _get_config
    r = httpx.get(
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_api.py", line 196, in get
    return request(
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_api.py", line 104, in request
    return client.request(
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_client.py", line 828, in request
    return self.send(request, auth=auth, follow_redirects=follow_redirects)
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_client.py", line 915, in send
    response = self._send_handling_auth(
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_client.py", line 943, in _send_handling_auth
    response = self._send_handling_redirects(
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_client.py", line 980, in _send_handling_redirects
    response = self._send_single_request(request)
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_client.py", line 1016, in _send_single_request
    response = transport.handle_request(request)
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_transports/default.py", line 231, in handle_request
    resp = self._pool.handle_request(req)
  File "/usr/lib64/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/opt/app-root/lib64/python3.9/site-packages/httpx/_transports/default.py", line 84, in map_httpcore_exceptions
    raise mapped_exc(message) from exc
httpx.ConnectTimeout: timed out

@feloy yes it's in draft for that reason 😆
It only works for the model services app so far. It takes a while as its slow to load the model (atleast on windows) but you can see it succeed on the logs and then open it on the browser. I was waiting for Jeff as i need to ask him how i should connect the sample app to the model. I use my personal ip to connect to it but i'm sure there should be some other way.

I need to write some tests but you can start playing with it and see if you face some issue.
I only tested on Windows so far. It extremely slow at starting the model_service. Like 4 min this morning :/
So if you start the pod, be patient and don't give up 😆
You can check the video above to see how it works

Works great on Linux Fedora. The model starts instantly on my system (not fast enough for the app to get connected the first time, a retry on the connection to the model would be helpful)

Works great on Linux Fedora. The model starts instantly on my system (not fast enough for the app to get connected the first time, a retry on the connection to the model would be helpful)

Oh nice, so windows is the only turtle here 😆 Yes in a following PR i think we need to listen to the port to see when the model service is ready and then connect the sample app 👍

I created a PR: https://github.com/axel7083/locallm/pull/4

@feloy @axel7083 @jeffmaury i've splitted the commits so the first one is just a refactoring of the existing code (instead of having a hube pullApplication i split it into smaller pieces), the second is about new stuff and then all the tests.
If you want you can look at them separately. Just FYI.

I'll wait another hour so someone else have the time to give it a look and i'll merge as this is the base for moving forward.


Fixing parsing a diff when a file is added w/o content

Hi there! I was trying to use the GitDiff library when I came across this bug-- when an empty file is added w/o any content* the patch doesn't have from and to fields with the expected values.
Not sure if including file_a and file_b on the headers is the best solution here but it's the one I could find :)
Please let me know if this works out.
Also-- I noticed some files are not mix format-compliant**.  Would be happy to fix that as well (maybe on the same PR?)
Best!
Bruno
*like this:
touch file.txt
git add file.txt
git commit -m "adding empty file"

** try:
mix format --check-formatted lib/git_diff.ex

** (Mix) mix format failed due to --check-formatted.
The following files are not formatted:

  * lib/git_diff.ex

Sorry for the delayed response, life has been busy and this obviously isn't something changing often or that I'm keeping a close eye on.
You're mostly there with it but there are a couple changes I'm requesting before I accept.


[fix][ci][branch-2.10] Fix the release tools

Modification

Upgrade python to python3
Remove the cpp-related command

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in the forked repository
PR in forked repository:

The failure is imported by https://github.com/apache/pulsar/pull/19674.

/pulsarbot rerun-failure-checks


Dependencies

What exactly are the dependencies of this widget? And would you please include a list in the readme.

jQuery
jQuery UI

Core
Widget
Mouse
Sortable

Am I missing something from the above list?

+1
I'm trying to integrate this plugin into a webapp that doesn't already have jquery UI as a dependency and need to know what the minimal jquery UI configuration is.

@Mottie you are missing nothing.

jQuery
jQuery UI

Core
Widget
Mouse
Sortable

These are the dependencies.


Autotile - always revert to the first setup when closing godot

Operating system or device, Godot version, GPU Model and driver (if graphics related):
9738ebcda047fd9b4ddf71a0da5d682ade1a2666
Issue description:
When closing godot and open it again, the setup such icon, bitmask, etc revert to the previous setup.
Step to reproduce
I'm not quite sure this always happen, but you can clone my repo and try to change the setup -> close -> open again, no changes happen
Update
Try to figure out a little bit, so I found the solution, but still, this is a bug. We need to export the tileset scene to .tres after making changes. That will save all changes
Link to minimal example project:
https://github.com/damarindra/GameOff2017

I have this problem too. I am using v3.0 stable on Arch

closed, resource is not saved automatically when saving scene. You need to save manually by click the save icon on inspector


update to 20200226

Checklist

[X] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

note that these recent releases of git-annex would break datalad prior yet to be released 0.12.3, due to breakage of API (removal of --include-dotfiles in  7.20191218-128-g3cd375723 AKA 8.20200226~73

Maybe add constraints on git-annex version to  datalad-feedstock?
I wonder why —include-dotfiles could not be made a no-op for backwards compatibility...

Maybe add constraints on git-annex version to datalad-feedstock?

we might, e.g. could have been <=8 (or whatever syntax is), and in the next update I will do <=9.
I wish there was "Breaks" relationship in conda to be declared in git-annex pkg like we do in debian

I wonder why —include-dotfiles could not be made a no-op for backwards compatibility...

well, I wondered too, and even whined a (just a tiny) bit to joey ;)  moreover, there might be side-effects in adjusted branches (ref: https://github.com/datalad/datalad/pull/4214#issuecomment-592536329)


Optimize performance

We have checked the operation, but we apologize if there are any problems.
If you have any questions, please ask.

Looked through everything and it all looks good. Thanks for the contribution!

Oh, I completely forgot to reduce the weight of the selector. I will be sending out another PR soon.


AsyncDataCacheTest.ttl is flaky

Bug description
[Expected behavior] and [actual behavior].5: [ RUN      ] AsyncDataCacheTest.ttl
5: I20231227 07:32:14.231534 28752 SsdFile.cpp:774] [SSDCA] Starting shard 0 without checkpoint
5: I20231227 07:32:14.231607 28752 SsdFile.cpp:774] [SSDCA] Starting shard 1 without checkpoint
5: I20231227 07:32:14.231676 28752 SsdFile.cpp:774] [SSDCA] Starting shard 2 without checkpoint
5: I20231227 07:32:14.231743 28752 SsdFile.cpp:774] [SSDCA] Starting shard 3 without checkpoint
5: I20231227 07:32:14.304281 31243 AsyncDataCache.cpp:534] [SSDCA] Limiting SSD save batch to 588 entries
5: I20231227 07:32:14.304381 31243 AsyncDataCache.cpp:534] [SSDCA] Limiting SSD save batch to 627 entries
5: I20231227 07:32:14.304404 31243 AsyncDataCache.cpp:534] [SSDCA] Limiting SSD save batch to 564 entries
5: I20231227 07:32:14.314743 31243 SsdFile.cpp:661] [SSDCA] Checkpointing shard 0, force: 0 bytesAfterCheckpoint: 1.72MB checkpointIntervalBytes: 1.60MB
5: I20231227 07:32:14.324473 31243 SsdCache.cpp:128] [SSDCA] Wrote 6MB, 0.0658458 MB/s
5: I20231227 07:32:14.339534 31264 AsyncDataCache.cpp:579] [CACHE] Removed 509 AsyncDataCache entries.
5: I20231227 07:32:14.342849 31264 AsyncDataCache.cpp:579] [CACHE] Removed 499 AsyncDataCache entries.
5: I20231227 07:32:14.346889 31264 AsyncDataCache.cpp:579] [CACHE] Removed 545 AsyncDataCache entries.
5: I20231227 07:32:14.348112 31263 AsyncDataCache.cpp:579] [CACHE] Removed 0 AsyncDataCache entries.
5: I20231227 07:32:14.348253 31263 AsyncDataCache.cpp:579] [CACHE] Removed 0 AsyncDataCache entries.
5: I20231227 07:32:14.348361 31263 AsyncDataCache.cpp:579] [CACHE] Removed 0 AsyncDataCache entries.
5: I20231227 07:32:14.349735 31264 AsyncDataCache.cpp:579] [CACHE] Removed 493 AsyncDataCache entries.
5: I20231227 07:32:14.349841 31263 AsyncDataCache.cpp:579] [CACHE] Removed 0 AsyncDataCache entries.
5: I20231227 07:32:14.350323 31263 SsdFile.cpp:586] [SSDCA] Removed 172 entries from /tmp/velox_test_4ioSnI/cache0. And erased 1 regions with 50% entries removed.
5: I20231227 07:32:14.350550 31263 SsdFile.cpp:586] [SSDCA] Removed 157 entries from /tmp/velox_test_4ioSnI/cache1. And erased 1 regions with 50% entries removed.
5: I20231227 07:32:14.350858 31263 SsdFile.cpp:586] [SSDCA] Removed 149 entries from /tmp/velox_test_4ioSnI/cache2. And erased 1 regions with 50% entries removed.
5: I20231227 07:32:14.350876 31264 CacheTTLController.cpp:68] Failed applying cache TTL of 98 seconds. Entries from 66 files are to be removed, while 0 files are retained
5: I20231227 07:32:14.351198 31263 SsdFile.cpp:586] [SSDCA] Removed 150 entries from /tmp/velox_test_4ioSnI/cache3. And erased 1 regions with 50% entries removed.
5: I20231227 07:32:14.351220 31263 CacheTTLController.cpp:68] Succeeded applying cache TTL of 98 seconds. Entries from 66 files are to be removed, while 0 files are retained
5: ../../velox/common/caching/tests/AsyncDataCacheTest.cpp:1146: Failure
5: Expected equality of these values:
5:   statsTtl.ssdStats->entriesAgedOut
5:     Which is: 628
5:   statsT1.ssdStats->entriesCached
5:     Which is: 172
5: W20231227 07:32:14.360149 28752 File.cpp:129] close failure in LocalReadFile destructor: -1, Bad file descriptor
5: W20231227 07:32:14.360194 28752 File.cpp:129] close failure in LocalReadFile destructor: -1, Bad file descriptor
5: W20231227 07:32:14.360208 28752 File.cpp:129] close failure in LocalReadFile destructor: -1, Bad file descriptor
5: W20231227 07:32:14.360221 28752 File.cpp:129] close failure in LocalReadFile destructor: -1, Bad file descriptor
5: I20231227 07:32:14.367921 28752 TempDirectoryPath.cpp:31] TempDirectoryPath:: removing all files from/tmp/velox_test_4ioSnI
5: [  FAILED  ] AsyncDataCacheTest.ttl (136 ms)
5: [----------] 10 tests from AsyncDataCacheTest (29659 ms total)
System information
This happens on circle ci Linux build run: https://circleci.com/api/v1.1/project/github/facebookincubator/velox/285728/output/107/0?file=true&allocation-id=658bcac2aced6d10c464c307-0-build%2FABCDEFGH
Relevant logs
https://circleci.com/api/v1.1/project/github/facebookincubator/velox/285728/output/107/0?file=true&allocation-id=658bcac2aced6d10c464c307-0-build%2FABCDEFGH

I am seeing this frequently in CI.
Another instance https://app.circleci.com/pipelines/github/facebookincubator/velox/43282/workflows/8aff73f0-8afe-43a6-8631-f380f7c34be4/jobs/300634

I still see this happening on PRs:
https://app.circleci.com/pipelines/github/facebookincubator/velox/44881/workflows/4abb28a5-0823-4f07-a7a4-1a660f6b9ffc/jobs/312596
5: [  FAILED  ] 1 test, listed below:
5: [  FAILED  ] AsyncDataCacheTest.ttl
5:
5:  1 FAILED TEST
5:   YOU HAVE 1 DISABLED TEST
5:
258/289 Test   #5: velox_cache_test .......................................................***Failed   57.65 sec

@gggrace14 Ge, would you prioritize fixing this?

Yes, will fix asap.
For the test AsyncDataCacheTest.ttl, the flaky part comes from a race condition of getting the stats for checking and the actually running of ttl in multi-threads. I already tried a semaphore to serialize the two, but the race condition still exists. Will debug and try a different way.


Not possible to control visibility of Action bar when tab-view is used

Issue
When a tab-view is being used, it is currently not possible to control the visibility of the action-bar as all possible(documented) options to control the visibility is through the Page. And a tab-view doesn't seem to play along with a page.
What I want to achieve:
The ability to hide the Action bar when the user scrolls down the page inside a tab view. A good example for this is the youtube app.

Hi @asaph26,
I reviewed your scenario, however I was unable to reproduce such an issue. I am attaching a link to the repo, where I uploaded a  sample project. Could you review my code and to verify, whether you still have the same issue.
https://github.com/tsonevn/NGHideActionBar.git
If you still expire the same problem you could send me sample project which could be debugged locally.
I hope this helps

Hi @tsonevn
Thanks for the quick reply. This helps a lot. I didn't try it this way. I was more focussed on getting it to work with TS.
Are there any plans to make a page and a tab-view play well together? Is it possible to include routing in a nativescript ng app while also using a tab-view?
I am closing the issue. Thanks again for the quick reply.

Hi @asaph26 ,
You could use page-router-outlet to navigate between the pages. You could review this  article from the documentation. I am also attaching sample project, where has been demonstrated how to use navigation in your NativeScirpt Angular2 project .