genetic recurrent myoglobinuria (MONDO:0020504) paretnage query

Definition
Parents

Genetic recurrent myoglobinuria is an inborn error of metabolism characterized by abnormal urinary excretion of myoglobin due to acute destruction of skeletal muscle fibers.

This  has parents
muscular lipidosis (MONDO:0016117)
and
disorder of phospholipids, sphingolipids and fatty acids biosynthesis with skeletal muscle predominant involvement (MONDO:0018120)
Is that correct for this disease?
I have one assignment (cox1)
It isn't obvious from the genes, or the description that  this is a "muscular lipidosis"
I can't find anything linking "cytochrome oxidase" and lipidosi (Google)

It seems that myopglobinurea is a symptom of
lipodystrophy in
https://www.omim.org/entry/605518
but is this the same disease as the MT-CO1 disorder?

@ValWood what is MT-CO1 disorder? I don't see that as a class in Mondo or OLS

The entire definition is
myoglobinuria, recurrent (MONDO:0010791)

Definition
Parents

Genetic recurrent myoglobinuria is an inborn error of metabolism characterized by abnormal urinary excretion of myoglobin due to acute destruction of skeletal muscle fibers. Epidemiology The exact prevalence remains unknown. Clinical description In the majority of cases, the disease manifests in childhood and is often triggered by exertion or infection (febrile illness). Hypertonia, muscle stiffness and muscle pain, impaired kidney function and elevated levels of serum creatine kinase are common clinical features. Etiology Mutations in the mitochondrial DNA-encoded cytochrome C oxidase genes ( MT-CO1 and MT-CO2 ) should be considered in patients with recurrent myoglobinuria. Recently, mutations in the LPIN1 gene (chromosome 2p21) have been reported to have a causative role in three patients with recurrent episodes of myoglobinuria, originating from consanguineous families. Genetic counseling The disorder may occur sporadically, or be inherited in either a recessive or dominant manner.

So I now think this is probably OK.
I  came across it  via MT-CO1  (pombe cox1).
But I think the parentage is probably fine here. Closing...


The spine of Cesium Man seems is bent

It may be due to mind, but the Cesium Man's spine looks bent.
QMV.js + CesiumMan.gltf result:

Three.js + CesiumMan.gltf result:

The skinning is wrong due to the weights sum in Cesium Man are not 1. Already fixed in https://github.com/pissang/qtek/commit/8dd12612c3cf4ebc99967c174893c4b160066b3a

@pissang  I confirmed that it has been fixed. Thanks :)


<Update?> Enum is expected.

Unable to use switch construction with this type on UpdateStream subscription.
Maybe I'm doing something wrong, I'm a beginner in Swift

Please take a look at the docs.
Also the event is an optional, because in the beginning there is no event. This means you need to do something like that (if you don't care about the new message):
switch event {
   case .newMessage?:
       print(event)
}

I tried to do as in your example. I got this error:

The compiler is unable to check that this switch is exhaustive in reasonable time

Solved, after add 'default' case. Thanks!

How to parse data ？


Don't make functions static

FStar.h holds only static function. This makes the headers unusable when only a subset of HACL* is used because it contains unused functions.

Closing. Tracked by https://github.com/mitls/hacl-star/issues/62


rename project name to project id

It took me a few retries to understand that it should be the project id and not the project name. I think this small change should make it clearer. Thanks for the great tool and article!

Great, thanks for your commit, that's perfectly reasonable.


Execution failed for task ‘:datadog_flutter_plugin:compileDebugKotlin’.

Stack trace
file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:30:22 Unresolved reference ‘PerformanceTracker’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:31:32 Unresolved reference ‘PerformanceTracker’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:80:44 Unresolved reference ‘asFlutterMap’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:102:44 Unresolved reference ‘asFlutterMap’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:135:44 Unresolved reference ‘asFlutterMap’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:165:44 Unresolved reference ‘asFlutterMap’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumEventMapper.kt:215:44 Unresolved reference ‘asFlutterMap’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:76:29 Unresolved reference ‘DatadogSdkPlugin’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:97:20 Unresolved reference ‘invalidOperation’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:131:17 Unresolved reference ‘DatadogSdkPlugin’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:172:19 Unresolved reference ‘DATADOG_FLUTTER_TAG’.
file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:200:29 Unresolved reference. None of the following candidates is applicable because of a receiver type mismatch:
@InlineOnly() fun <T, R> T.let(block: (T) -> R): R
[R|Contract description]
<
CallsInPlace(block, EXACTLY_ONCE)
>
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:200:33 Cannot infer type for this parameter. Please specify it explicitly.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:201:67 Unresolved reference ‘trackViewsManually’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:202:66 Unresolved reference ‘trackInteractions’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:203:60 Unresolved reference ‘trackErrors’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:204:69 Unresolved reference ‘trackNetworkRequests’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:205:65 Unresolved reference ‘trackNativeViews’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:207:20 Unresolved reference ‘trackCrossPlatformLongTasks’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:209:20 Unresolved reference ‘trackFlutterPerformance’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:210:60 Unresolved reference ‘dartVersion’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:231:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:252:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:262:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:278:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:299:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:321:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:343:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:356:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:369:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:382:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:393:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:403:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:416:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:438:20 Unresolved reference ‘missingParameter’.
e: file:///Users/gregspinetti/.pub-cache/hosted/pub.dev/datadog_flutter_plugin-2.9.0/android/src/main/kotlin/com/datadoghq/flutter/DatadogRumPlugin.kt:449:20 Unresolved reference ‘missingParameter’.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ‘:datadog_flutter_plugin:compileDebugKotlin’.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Reproduction steps
When executing flutter
Volume
all
Affected SDK versions
2.7.0 - 2.9.0
Latest working SDK version
2.7.0 - 2.9.0
Does the crash manifest in the latest SDK version?
Yes
Flutter Version
No response
Setup Type
No response
Device Information
No response
Other relevant information
When running flutter, is solved by running a flutter clean and pubget, it should be noted that I happened in version 2.7.0 and then I uploaded the version to 2.9.0 and happened again until I did the step mentioned at the beginning.

Hi @jtavio ,
I've seen this before and actually have no idea what causes it, but it appears it's caused by some weird disconnect between what the Flutter plugin wants and what Gradle has actually downloaded, which is why a clean rebuild solves it. It might also be caused by some Gradle cache issue...
After doing  a clean rebuild, do you ever see the problem again before performing an upgrade?

@fuzzybinary
Thanks for the answer!
correct to run a ‘flutter clean’ and then a ‘pub get’. is solved, if you need to close the bug, you could do or investigate a little more ?

Yes, I'll continue to look into it to see if it's something weird about how our SDK specifies its dependencies, but since it has a relatively simple workaround it likely won't be high priority.


Added new example Simple Browser App

This Simple Browser App demonstrates how to:

search web pages via the search bar
add a website to the favorites
open a page from the favorites
hide or show a favorites page list

This app uses two approaches. First approach is with Provider which accesses the data from the state. The next one is StateNotifier which manages state with new or edited data. For example when the user clicks on the favorite button, StateNotifier is used for adding web page to the state list. StateNotifier is also used when user wants to remove the web page from the favorites list, after which it updates the state. Before that can be done, Provider is used to check current web page and all pages in favorite list. If the page exists inside favorites list, user is able to remove the web page from the list. If web page is not located in the favorites list, user can add web page to it.
This Simple Browser App is a good example for how to use StateNotifier and Provider together. StateNotifer is used when the user clicks or writes something in the input place and Provider is used when the user wants to read some information.

Hello!
Thanks for the contribution but:
If you want to contribute examples, please host them on your personal github account and link them in "third party example".
If you want to make an official example, please make an issue first to explain why this needs to be an official one.


Evaluate LiteDB vs json file storage

For now json files are fine, but in the long run it would be nicer to be able to have something a bit more robust like LiteDB or SqlLite but the problem I can see at the moment is that currently everything is loaded into memory at the start then altered as needed and re-saved in bulk every few mins/major changes.
DBs don't really work well with this paradigm as they are meant to have data loaded on demand and updated at the entity level i.e singular flow, not entire flow store.
With this being said some of this approach could be adopted with repositories replacing the stores, but the issue then comes down to knowing if data has changed in a UI at all, then updating it on demand.
Flows would always need to be loaded into memory and could be updated in both memory and DB on the fly, but it would need some sort of way to know if the state has changed on the entity, and things like variables can updated in various places, but we do have events that can be hooked into.
Anyway it needs evaluation at some point.

Work has been done on this in a spike and is almost ready for live, its worth noting that technically there are some snags, so while yes everything will be contained within a single DB now, we have to do some ETL style work in the repository layer to take out models, convert them into JSON then convert them into BSON for storage which is inefficient, but works fine for now.
There are also some concerns with LiteDB being unmaintained as no one seems to be able to answer any questions around more advanced use cases, i.e handling advanced type serializing in specific scenarios etc.
Also another downside is that you cant simply crack open JSON files and look inside and edit anything if there are any problems or back them up, you would need to use a custom tool to open and view the LiteDB database, which is good from security at least but bad in terms of tech savvy people wanting to edit stuff.
Anyway hopefully have an update on this soon.

This has now been added via #35


Rework how compiler finds fsharp core --- Fixes: error FS0193: intern…

…al error: Exception of type 'System.Collections.Generic.KeyNotFoundException' was thrown.

"Rework how compiler finds fsharp.core"
this sounds super dangerous (and also awesome if it fixes some of the common issues).
Can you please elaborate a bit?

It won't improve your lives at all I'm afraid Steffen.  I am afraid that in order to improve your lives I will have to make the resolution changes similar to the ones I proposed over Christmas.  The goal will be to make the "magic" visible, and hopefully pluggable.
This particular change is a coreclr only change.  On the desktop the compiler needs an fsharp.core.dll for seq,lists blah blah ... if it can't find one, because none was provided on the command line, or because using msbuild to trawl framework directories as a fall back it calls GetReferencedAssemblies() and returning the one named fsharp.core.  Well that API is not on coreclr, and so instead we get the fsharp.core.dll that is co-located with the executing compiler.
Indeed this heuristic is a better one ... much more deterministic, and when we remove fsharp.core.dll from the GAC, we can switch the desktop over to this heuristic too.  Although the framework directory magic will still be required without more changes.

@KevinRansom Could you please document the effect of this change somewhere that can be referred to for future reference and testing?  For example in a markdown file of design notes about how the behaviour of the CoreCLR branch fsc.exe diverges from the master fsc.exe?
Previously, an invocation of fsc.exe had the effect of adding an implicit assembly reference as if
-r "FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

had been specified (that's what the code that's being replaced here does).   MSBuild resolution is then used to resolve to the assembly reference.  This was the intended exact behaviour of fsc.exe and fsi.exe when not given an explicit FSharp.Core reference.
I understand that the CoreCLR fsc.exe won't necessarily be able to do this because the dependency on MSBuild resolution may need to be dropped  (except perhaps on Windows for backwards compat - I'll leave that to you guys to decide).  But in any case the replacement code does something different and it's important to document the change.
thanks
don

@dsyme This change is not coreclr specific.  It also will be the case in the desktop compiler for Dev 15.
The reason for the change is to remove all VS assemblies from the GAC, which enables more VS xcopy scenarios.

@KevinRansom   But as I mentioned in my comment above, we were not resolving FSharp.Core from the GAC - we were finding it in Reference Assemblies.  So this doesn't have anything to do with the GAC?  So I still don't understand what the ramifications of this change are :/
In any case I do feel it is very, very important to have the change documented in a design note that describes previous and future behavior...  It feels this has a pretty decent chance of breaking someone somewhere - if not in Visual F# Tools then on Mono, or users of FSharp.Compiler.Service....


cookie popup styling

since this got recently merged, lets sync it with our design change that was few weeks ago

Data collecting
google analytics are off by default?

styling

Accept should be the "main" button
link to figma: https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=1287-18959&mode=design&t=wIR4vUyhVh1KHnUu-11

fix: the cookie banner styles are applying to the regular buttons

these buttons can be button secondary outline rounded


Pattern for multiple test cases, avoiding repetition in the yaml file

Describe the feature
I would like to be able to define the dbt_datamocktool test using placeholder values, so multiple test cases can be captured by different input/output seeds, but without requiring repetition in the yaml file
Describe alternatives you've considered
I can achieve this by copying and pasting the entire dbt_datamocktool test block, applying the specific input mapping/expected output for each seed
Example:
models:
  - name: model_name_here
     tests:
      - dbt_datamocktool.unit_test:
          tags:
            - topic_unit_test
          input_mapping:
            ref('existing_model'): ref('existing_model__input__test_case_{{ i }}')
          expected_output: ref('expect__existing_model__test_case_{{ i }}')

So, for each test case I have to copy-and-paste the entire block only to replace {{i}} with the specific test case number
Additional context
N/A
Who will this benefit?
This benefits all users with real case applications/complex logic.
By splitting the test into multiple test cases, it is easy to come up with the test data/output; as well as easily identify which specific test/logic is failing
Are you interested in contributing this feature?
I would love to contribute extending this feature. Not sure what is the best way to approach it though.
I imagine it would be possible to parameterise the underlying datamocktool macro to receive an additional and optional parameter with a list of values

Note: due to a current legacy project using dbt version 0.19.2, I am using datamocktool revision 0.1.2 (from this repo)

Update [2022-09-29]:
@mjirv I have implemented this functionality for my own project. I would be happy to raise a PR if this is deemed as a feasible contribution
It is backwards compatible as well, so should be safe to implement. Let me know if I should raise a PR

Sure thing!
The model yaml, with test applied at the table level looks like the following:
- name: domain_x__report_name
  tests:
    - custom_unit_test:
        tags:
          - domain_x_unit_test
        test_case_list: [9,12,27,28,29,30]
        input_mapping:
          ref('model_name1'): \ref('model_name1__input__test_case_@')
          ref('model_nam2'): \ref('model_name2__input__test_case_@')
        expected_output: \ref('expect__report_name__test_case_@')

The documentation provides instructions, but basically:

If not using the optional field test_case_list, the test behaves as usual
if test_case_list, it replaces the @ with each value in the iterator list

Note: I had to use the \ to escape the key, in order to treat it as a string (replacing with the @ symbol) before rendering the full Relation/Path (database.schema.identifier)

This results in a single dbt test. In case of failures, it returns the count of mismatching records.
It also logs the name of each failing test case
Lastly, I noticed there was no visibility on the unit test errors.
So I changed the process to also materialize the output of the model, using the mocked input. It gets stored as a view, making it easy to look at the underlying code by inspecting the view definition.
This has really helped debugging failing unit tests and increasing code coverage.
Would be interested to hear your thoughts on these approaches. I will raise a PR tomorrow, so you can have a closer look 👍

Nice, that all makes sense. I think providing more visibility into failures is a great idea, so thank you for adding that!
The only thing I'm not a big fan of is the string escaping, but I think that might be unavoidable. I'll give it a closer look on the PR review.

@mjirv sorry, this is my first time contributing to an open source project :)
I am getting permission denied when trying to push the branch. Do I need a contributor/writer permission to push the branch?

Good question! You need to fork it to your own account and then create a PR from that.

Hey @marcellovictorino - just a heads up that I started looking at this but didn't have time to do a complete review yet. I will aim to get it done sometime this week!

@mjirv No worries! I appreciate you must be busy as well
I am just glad to contribute back to OSS 😃
Looking forward to your review 👍


Incorrect NONBLOCKING Example?

Background
In the Quil-T proposal / de facto spec, there's these two following lines:
Re: blocking pulses:

The execution of a pulse operation on a frame blocks pulse operations on intersecting frames, i.e. frames with a qubit in common with the pulse frame.

Re: nonblocking pulses:

A pulse operation (PULSE, CAPTURE, and RAW-CAPTURE) with the NONBLOCKING modifier does not exclude pulse operations on other frames.

Then there's this example:
NONBLOCKING PULSE 0 "xy" flat(duration: 1.0, iq: 1.0)
PULSE 0 1 "ff" flat(duration: 1.0, iq: 1.0)

with the description

the two pulses could be emitted simultaneously. Nonetheless, a NONBLOCKING pulse does still exclude the usage of the pulse frame, so e.g. NONBLOCKING PULSE 0 "xy" ... ; PULSE 0 "xy" ... would require serial execution.

Problem
This is not inherently inconsistent, and can be implemented as-is. However, it adds complexity and possibly confusion for the program author, in that the behavior of the blocking PULSE is modified by the NONBLOCKING modifier on the earlier PULSE. I'll refer to these (from the cited example) as instruction [0] and [1]. I'd propose that the behavior of the blocking PULSE - that it is the only instruction executing on all common-qubit frames - should not be modified by other instructions in the program.
In this case, [0] uses only 0 "xy" but does not use or block any other frames. However, [1] still blocks 0 "xy" because it is not NONBLOCKING. In my opinion, that should mean that these two instructions cannot be scheduled concurrently.
The metaphor: [0] sits at the table, occupies a seat, but doesn't reserve any other seats. [1] sits at the table but wants to reserve a number of seats, and [0] is sitting in one of those seats. Just because [0] doesn't care doesn't mean that the two are compatible and can sit together at the table, and thus (escaping the metaphor) doesn't mean that the two should run concurrently.
Proposal
I can ship an MR to this effect depending on feedback, but I'd change the example to specifically include the concurrent pulse-and-capture pattern used in readout, and to retain this example but as a counterexample and clarify that the two would not be concurrent.
I'd also add the verbiage:

Within an instruction block, an instruction which uses a frame must start execution after all previous instructions which use or block that frame, and complete execution before all later instructions which use or block that frame.

I agree that the current behavior could be a real source of confusion. And actually, even if we kept the current behavior, I think the document could be clarified.
My memory is a bit fuzzy on why this turned out the way that it did, but I think the main reason for supporting the seemingly contradictory notion of "play a pulse which thinks that it owns some qubits, while at the same time sneaking in some other pulses" is not just for readout, but to also support certain techniques for correcting crosstalk. In this setting, you may have a program which plays some pulses to perform some gates, and you'd like to add in correction pulses (perhaps on a blocked frame, I don't know) which otherwise do not change the timing of the program.
If the original pulse is PULSE 0 1 "ff" flat(duration: 1.0, iq: 1.0) and the correction is PULSE 0 "xy" flat(duration: 1.0, iq: 1.0) then combining these to get (with existing quilt semantics)
...
NONBLOCKING PULSE 0 "xy" flat(duration: 1.0, iq: 1.0)
PULSE 0 1 "ff" flat(duration: 1.0, iq: 1.0)
...

does the trick. With your proposal, we'd need
...
NONBLOCKING PULSE 0 "xy" flat(duration: 1.0, iq: 1.0)
NONBLOCKING PULSE 0 1 "ff" flat(duration: 1.0, iq: 1.0)
...

which also does the trick. However, the scheduling of ... could be different in this second program, due to the lack of exclusion. But I suppose this could be dealt with via
...
FENCE 0 1
NONBLOCKING PULSE 0 "xy" flat(duration: 1.0, iq: 1.0)
NONBLOCKING PULSE 0 1 "ff" flat(duration: 1.0, iq: 1.0)
FENCE 0 1
...

or something similar.
So in short, I think what you suggest makes sense, as long as whatever NONBLOCKING tricks that have traditionally been used can be supported or done away with under the revision.


Implement panic handler

Closes #1296
This shows how we can get the full panic information out of Wasm.

[x] Implement
[x] Create feature for compatibility
[x] Call install_panic_handler automatically at the beginning of each entry point
[ ] Cleanup

Looks good! Looking forward to the wasmvm / wasmd changes.

Great, thanks for the input. Happy to avoid the unnecessary feature.


Implement timeline_manager for safekeeper background tasks

In safekeepers we have several background tasks. Previously WAL backup task was spawned by another task called wal_backup_launcher. That task received notifications via wal_backup_launcher_rx and decided to spawn or kill existing backup task associated with the timeline. This was inconvenient because each code segment that touched shared state was responsible for pushing notification into wal_backup_launcher_tx channel. This was error prone because it's easy to miss and could lead to deadlock in some cases, if notification pushing was done in the wrong order.
We also had a similar issue with is_active timeline flag. That flag was calculated based on the state and code modifying the state had to call function to update the flag. We had a few bugs related to that, when we forgot to update is_active flag in some places where it could change.
To fix these issues, this PR adds a new timeline_manager background task associated with each timeline. This task is responsible for managing all background tasks, including is_active flag which is used for pushing broker messages. It is subscribed for updates in timeline state in a loop and decides to spawn/kill background tasks when needed.
There is a new structure called TimelinesSet. It stores a set of Arc<Timeline> and allows to copy the set to iterate without holding the mutex. This is what replaced is_active flag for the broker. Now broker push task holds a reference to the TimelinesSet with active timelines and use it instead of iterating over all timelines and filtering by is_active flag.
Also added some metrics for manager iterations and active backup tasks. Ideally manager should be doing not too many iterations and we should not have a lot of backup tasks spawned at the same time.
Fixes #7751

Ok, so I've done everything I've wanted in this PR. Now I'll look into test failures and that should be it.
@arssher you can do another review iteration if you want, I'm not going to change anything but bugfixes.

I also think we'd likely benefit from generalizing task itself to have common code for cancelling and waiting for termination.

Sure, one step at a time and we'll get there.

Also, high level comment for timeline_manager.rs would be nice (partial copy of PR desciption would work).

Structurally this looks like a good direction.  Couple of general non-PR-blocking thoughts as we evolve this code:

Various functions could be pub(crate) rather than bare pub to make refactoring later easier (it's harder for linter can't detect unused pub stuff)
In places we'd like to block other code waiting for background task shutdown, the Gate helper could be a good fit.  It has the nice behavior of printing information if it blocks unexpectedly long.  I spend 5 minutes playing with that here, seems like it drops in pretty easily: https://github.com/neondatabase/neon/commits/jcsp/sk-concurrency-primitives/

Various functions could be pub(crate) rather than bare pub to make refactoring later easier (it's harder for linter can't detect unused pub stuff)

Yes, should be done later. Also it makes sense to better (re)organize safekeeper code into directories.

the Gate helper could be a good fit.

Agree, but needs more refactoring to make all tasks use the gate. Created an issue https://github.com/neondatabase/neon/issues/7831

safekeeper: use CancellationToken instead of watch channel

This change looks good, would like to commit it right after this PR.


adds support for hls.6.x

To fix https://github.com/clappr/clappr/pull/1191#event-845886043 and https://github.com/clappr/clappr/issues/1143#issuecomment-246997927

Although the build says it's broken bc of lint I can't reproduce it locally.
$ npm run lint

><EMAIL_ADDRESS>lint /Users/leandro.moreira/src/clappr
> eslint src/ test/

It is hls.js line 358 : https://github.com/clappr/clappr/blob/master/src/playbacks/hls/hls.js#L358

@kslimani if you try to run it locally it doesn't show the lint error ;(

it should be
  _fillLevels() {
    this._levels = this._hls.levels.map((level, index) => {
      return {id: index, level: level, label: `${level.bitrate/1000}Kbps`}
    })
    this.trigger(Events.PLAYBACK_LEVELS_AVAILABLE, this._levels)
  }

Locally, i have the following message
/home/kslimani/projects/clappr/src/playbacks/hls/hls.js
  358:5  error  Expected indentation of 6 spaces but found 4  indent

✖ 1 problem (1 error, 0 warnings)

Changes Unknown when pulling 6a7d55d188d6f1531c84d2028619f09d504af397 on supports_hls_6x into ** on master**.

Additionally, if i try to build Clappr with current master, hls.js playback doesn't work anymore. (but maybe you are already aware of issue ?). I am still digging where is the problem, if i findout something i will update.

@kslimani can you test this on your side? I already ran some tests (mp4, hls).

@leandromoreira yes i am gonna test and feedback.

@leandromoreira so far it is working again (testing with "npm run start" build demo page). :+1:

thank you very much @kslimani

Changes Unknown when pulling 6cc2682f1777f5bb0cb70618614cdbf634f37793 on supports_hls_6x into ** on master**.

Changes Unknown when pulling 4e1ca79e2540658f07c6e21169c0279e8f94686b on supports_hls_6x into ** on master**.

Also are we going to bump the major version of clappr for this? I think some people might be setting hlsjs options and accessing the hlsjs instance directly and this might cause problems for them?
refs: https://github.com/clappr/clappr/issues/1143#issuecomment-247985028

Changes Unknown when pulling 4e1ca79e2540658f07c6e21169c0279e8f94686b on supports_hls_6x into ** on master**.

I think some people might be setting hlsjs options and accessing the hlsjs instance directly and this might cause problems for them?

I think these people are relying on unstable abstraction :P I'm in favor of keeping the current minor version.

unstable abstraction

What abstraction are you referring to?

What abstraction are you referring to?

@shacharz I was referring to the people that use the private instance of hls (clapprInstance.core.getCurrentPlayback()._hls) as something stable

@leandromoreira what about people that used a custom XHR loader for hls.js that was passed using Clappr's config? This update broke it for them because hls.js 0.6.x has a different API for its xhr loader.

@shaharmor that's something we need to fix :) btw feel free to do a PR!

@leandromoreira I don't mind doing a PR, but we need to agree about it first :)
The 2 solutions I see:

revert to previous hls.js
release a major version and remove 0.2.64

oh so the new HLS doesn't offer XHR loader config?

@leandromoreira It does, but the API between the XHR loader and the rest of the library has changed

So it might be better to offer this new API or if possible to adapt both new and old clients.


⚠ Bofrost.lu has degraded performance

In a51fd97, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3534 ms

Resolved: Bofrost.lu performance has improved in ebe165a after 38 minutes.


Write How-To: Produce the SDR's input files

This will be: CSV files for most workflows and image files for Mothra


For other app

Maybe plugin can be made also for Cudatext? In python API.

It requires (I think almost) complete rewrite of plugin. I don't have a clue how to do it for cudatext and actually not interested in it. I suggest you to write such plugin (it required me less than day to do it) or switch to sublime text. If you have any questions regarding of inner structure of this plugin or it's code you are  welcome (please, do it by email).


don't use a VLA just to compute a buffer size

VLAs in C++ are compiler extensions, and clang 18 will complain about it.
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libelfin/+bug/2060786
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065084

I wonder why the compiler doesn't complain about similar lines of code like:
https://github.com/aclements/libelfin/blob/ca2b127a7a9ea5685873816805609b80e254b4da/dwarf/small_vector.hh#L24

In the case you pointed to, Min is not a variable but a template parameter, i.e. a compile-time constant.


Update the RTC Engine to 0.7.0.

Hi,
Sorry for jumping in unannounced, but I tried something similar to this merge while following the tutorial on my side :-)
More specifically on this commit : https://github.com/asmodehn/retrochat/commit/f53c2643187ab9424f030edfd19507b021b3fc35
It turns out that the change in dependencies (after a mix deps.update --all and a mix phx.server) triggers this on my version:
[debug] OTLP exporter failed to initialize: exception error: undefined function opentelemetry_exporter:init/1
  in function  otel_exporter:init/1 (/opt/Projects/elixir-playground/retrochat/deps/opentelemetry/src/otel_exporter.erl, line 42)
  in call from otel_batch_processor:idle/3 (/opt/Projects/elixir-playground/retrochat/deps/opentelemetry/src/otel_batch_processor.erl, line 137)
  in call from gen_statem:loop_state_callback/11 (gen_statem.erl, line 1203)
  in call from proc_lib:init_p_do_apply/3 (proc_lib.erl, line 226)

Isn't it something you observe as well on your version here ?
I m thinking there maybe some small thing missing (another dependency update, or some config setting)...
I m very new to membrane, so I have no clue where this comes from, but I am pretty sure that commit is the cause and therefore changes very similar to these here, so I thought I'd let you know.
Thank you.

Hello @asmodehn !
I am sorry for a late reply. We really appreciate that you let us know, that such a problem occurs!
I believe that we haven't faced that problem in our case, but surely we will try to inspect what might be causing it for you.
In you case, does it anyhow affect the main application's functionality, that is - displaying the video of all the peers in the room?
Cheers,

Hi @varsill
I believe I noticed it because my config somehow ended up with a debug log enabled.
Once I had the video display the debug log becomes a bit impractical...
I ll keep investigating when I get some time, but I was able to see my video, so I m guessing it doesnt have any impact.
I see one video, but no duplication of my own video (from me joining in multiple tabs) as I naively expected at first.
I ll keep playing with the code, to see if I need to duplicate the stream or what ;-)
In any case, thanks a lot for the work in the tutorials, it is definitely helpful for newcomers in the multimedia streaming world !
I ll refrain from hijacking the PR now :-)
Cheers!

Hello @asmodehn !
I really thank you for your kind words! I am glad you find our tutorials helpful ;)
Cheers!


Support proposed @machine rule

There has been a lot of interest in the ability to pre-define the allowed 'transitions' from one state to another, all in one place. This is not yet part of the spec, but I propose a syntax for it in the explainer -- and I think it would be another good feature to test.
(for now, the do() functional syntax might be simplest to support in relation to existing syntax)

An initial implementation was added in 4575f7602a5a8d5245fa2ab6ea5275f39d5df1f4. The codepen demo has been updated accordingly.
Right now the @machine definitions break CSS parsing of the other polyfill features, so @machine blocks should come at the end of stylesheets (or at least after all other styles related to CSS Toggles).
For anyone trying this out locally, keep in mind you'll need the toggle-machines.js script before using index.js. I'll start looking into packaging the code correctly so we can continue using a single entry point.

All bugs have been fixed in 808b84791661e8429ebd921c181a235625c300df, and we no longer need the extra file. Just make sure index.js is included with type="module".


When is the lz4 compression format supported?

Afkak doesn't currently support LZ4 compression, but it should be straightforward to add. Here's an outline of what it would take.
First, mark the codec supported:
https://github.com/ciena/afkak/blob/b7e0a716881ff776e15843465586a4cbd942cb6c/afkak/common.py#L37-L39
Add an extra for the required dependency here:
https://github.com/ciena/afkak/blob/b7e0a716881ff776e15843465586a4cbd942cb6c/setup.py#L29-L32
Add encoding support here:
https://github.com/ciena/afkak/blob/b7e0a716881ff776e15843465586a4cbd942cb6c/afkak/kafkacodec.py#L929-L936
Add decoding support here:
https://github.com/ciena/afkak/blob/b7e0a716881ff776e15843465586a4cbd942cb6c/afkak/kafkacodec.py#L266-L282
And most importantly, add unit and integration tests that exercise this code path.


Added link for CDC

Added a hyperlink to CDC's cloud connectivity page

@duongau
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Editor markdown preview not support Chinese？

Editor preview has display problem of Chinese Characters.
Editor preview not support Chinese。
eg：
举例。

Please send me an example of the problem or a chinese markdown file to make a test...

Fixed in 2.2.1 version.

thank you

In 2.2.2 version I've fixed it also in Explorer Preview Panel.


Startproject tutorial : Removed files explained after django-admin startproject mysite.

Trac ticket number
No ticket number. Tutorial docs improvement as mentioned in Djangocon Europe 2024 docs improvement
Branch description
The explanation of different files created after django-admin startproject mysite is here redundant, as they will be explained later when the user needs to configure/ interact with each of them.
Before:

After removing the explanations:

Checklist

[X] This PR targets the main branch.
[X] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[] I have checked the "Has patch" ticket flag in the Trac system. Does not apply here
[] I have added or updated relevant tests. Does not apply here
[X] I have added or updated relevant docs, including release notes if applicable.
[X] I have attached screenshots in both light and dark modes for any UI changes.

It seems weird to say, "Let's look at these files" and then offer no explanation. I think it's a helpful overview.

That is fair. How about this ?

It is also more in agreeance with the later startapp files directory explanation ;)

Well, I don't agree with this and other changes proposed by @evildmp, removing large amounts of explanatory material from the tutorial (https://github.com/django/django/pull/18253, https://github.com/django/django/pull/18246, https://github.com/django/django/pull/18239). Perhaps my opinion is in the minority, but I would like to see some consensus on the Django forum before moving forward with all these removals. I came to Django as an experienced programmer and I found many of these incidental explanations helpful, even if not strictly necessary. It seems Daniele wants to target the tutorial more at beginner programmers.

Dear Tim,
please consider my edited comment above, I have tried to answer "why" of the edit, as I understood it ! I will try to post them as new comments in the future

Well, I don't agree with this and other changes proposed by @evildmp, removing large amounts of explanatory material from the tutorial (#18253, #18246, #18239). Perhaps my opinion is in the minority, but I would like to see some consensus on the Django forum before moving forward with all these removals.

Our tutorial is like a beloved old friend that has succumbed to some middle-aged bloating. It has become rather flabby in places (these aren't even the most problematic examples - look at https://docs.djangoproject.com/en/5.0/intro/tutorial05/, in which the poor user must plod through multiple paragraphs of verbiage before they get to do anything).
There is an endless number valuable-to-a-few people things that could be added to it (and we can see that a lot have gone in already).
We need to make the tutorial crisp, lean, and punchy, so that every part of it is a contribution to the user's learning experience, not digressions into things that are described or explained elsewhere, and that the vast majority of users derive no value from.
These digressions really serve the authors' (wholly understandable, and also hard to resist) need to teach and explain much more than they serve the learners' needs.
Nothing is lost by moving such material out of the tutorial into a more appropriate place and linking to it. In fact, it's of advantage to people who are interested in it, because now they will find it in context, and given the space it needs - not shoehorned into an awkward aside in the tutorial.
By the way these issues were created in a workshop at DjangoCon Europe (by participants in the workshop, after discussion of what the tutorial does well and not so well; discussed also with @nessita, @carltongibson, @felixxm, @thibaudcolas and others in multiple conversations, perhaps they'd like to provide some input too).

It seems Daniele wants to target the tutorial more at beginner programmers.

Not in the least. It doesn't matter how experienced your are or how advanced your skills, when you are in a learning situation acquiring a new skill, you learn more effectively if you are not being interrupted by unnecessary digressions and distractions.

I don't want to waste time in dialog if the decision is already made, but I think these asides and explanations do provide value. They briefly show off aspect of Django that the reader can return to in more depth later. They teach philosophy and the "why" behind what we are doing.
If the Django community has decided we don't want these things anymore, then yes, we could excise quite a lot of material from the tutorial so the user can get through it much more quickly and come away with less knowledge. I think that would be a loss. When I was a new Django user, I was in no rush to get through the tutorial, and I remember enjoying its detailed explanations.
I appreciate all the work you're doing to try to improve the tutorial, but I don't agree with your characterization that it suffers from middle-aged bloat when most of these explanations have been there since the beginning (with some revisions at Django's PAIs have changed). Cheers!

There have been numerous discussions about simplifying the tutorial over a number of years now. There's widespread criticism within the wider ecosystem that it's too complicated: joking phrases such as "the notorious polls tutorial" are often used.
Bringing it into line with the Diataxis approach has been an agreed goal for a number of years now. These changes are in line with that.
We can (of course) open a thread on the forum and summon opinions again to reiterate all these conversations one more time, but it just seems like another unnecessary trip into the long grass.

@esskaey There is no need to include images to show what the changes will look like - that's easy enough for readers to infer via https://github.com/django/django/pull/18242/files. In fact including the images makes it harder to follow your pull request, so I suggest removing them.
I think it's right to remove that material from the tutorial - but that's only half the job. There are at least four more questions to be considered:

What should we say about the folder structure, now that we have excised that additional explanation?  I think we should say
something - for example: "As we proceed through the tutorial we will encounter some of these files more closely and work with them - their purpose and function will become clearer then."

Should the information we have removed be included somewhere in the documentation, if not here?

If so, where? (Perhaps there is already a page somewhere that explains the output of startproject - I can't easily check right now, but I suspect that there isn't. You could start looking at https://docs.djangoproject.com/en/5.0/ref/django-admin/#startproject, but my feeling is that a new page under https://docs.djangoproject.com/en/5.0/topics/ titled something like "Django project layouts and conventions" might be called for.)

Should we link to this material from the tutorial? (In my opinion, definitely.)

Tim wrote:

I think these asides and explanations do provide value. They briefly show off aspect of Django that the reader can return to in more depth later. They teach philosophy and the "why" behind what we are doing.

I think this material does more than provide value, I think it is essential to the completeness and success of the documentation. The "why" of Django is often scattered in the documentation though, rather than being collected and organised more deliberately.
If you were giving me my first flying lesson in a turbine-powered aircraft after years of flying piston-engined planes, at a certain point in that lesson I might be surprised, say by the slow spool-up time of the engines. And to understand what is happening and how to think about it, I would ask for some explanation. But the time for the explanation - the philosophy of flying a turbo-prop) would not be in the middle of that first flight (when it would be distracting, and I wouldn't be able to pay it proper attention) but when we are safely back on the ground for the debriefing.
I feel it's the same with the documentation. I would like to develop the explanatory power of our documentation in the /topics section, where we can organise material about why and philosophy and so on in more satisfactory ways.
The tutorial and the flying lesson are for learning - acquiring familiarity, having safe encounters with the machinery and work and techniques - in a controlled environment. The explanation guides (and the post-flight debriefing) are for acquiring deeper knowledge and understanding.

@esskaey There is no need to include images to show what the changes will look like - that's easy enough for readers to infer via https://github.com/django/django/pull/18242/files. In fact including the images makes it harder to follow your pull request, so I suggest removing them.

I thought it saves one time, by not having to check out and generate the docs. Not adding images is only easier for me :)
I have tried to address the questions from your comment.

Hello!
I've been following the conversation in this PR, and pondering about the best course of action. After some consideration, I agree with @evildmp and @carltongibson about the benefits of sticking to the Diátaxis principles and focusing the content of the tutorial to what the user needs to learn at a given step. My rationale is as follows:

Feedback heard in DjangoCon Europe about the presence of distracting and confusing content in the tutorial, specifically in tutorial 1.
Many Trac tickets have been closed with the rationale that tutorials should provide only the minimum necessary explanation.
My own history of learning. When I read these two comments from @timgraham I thought "I must be an alien" because I've had the opposite experience:

I came to Django as an experienced programmer and I found many of these incidental explanations helpful, even if not strictly necessary. [...]
When I was a new Django user, I was in no rush to get through the tutorial, and I remember enjoying its detailed explanations.

Following the flying lessons analogy, I can share my own real anecdote which illustrates why, even for experienced users, sticking to the basic when learning a new thing is important:
I've been driving manual stick cars for over 20 years now, so you could say I'm an experienced driver. I've navigated through all sorts of streets, routes, and countries—handling everything from old clunky cars that made parking on slopes a real challenge to newer models with cameras and alarms for added assistance. When I recently switched to driving an automatic car, it was a whole new experience. I had to focus on the bare minimum to keep the car running smoothly and avoid any mishaps, especially since I was so used to think about RPMs and smooth gear transitions. My right hand would constantly (incorrectly) reach for the stick and my left foot would attempt to press on a missing clutch. When the salesperson was explaining how to use the car, they started mentioning the radio, windshield wipers, and how to connect my phone to the car's screen, and I was just like, "NO, STOP, SHUT UP! I can barely keep this thing moving straight!".
When I first drove this car, it was a sunny day, so any explanation about windshield wipers was completely unnecessary and distracting! Of course that at some I definitely had to learn how to use them, but the first drive was not the right time for it. Same for the radio, the GPS, the "sport mode", and what not.
Answering some spot on questions from Daniele:

What should we say about the folder structure? "As we proceed through the tutorial we will encounter some of these files more closely and work with them - their purpose and function will become clearer then."

That proposal sounds sensible.

Should the information we have removed be included somewhere in the documentation, if not here?

Yes, please. We should find a place for these for this PR and the other PRs that are removing unnecessary explanations.

If so, where?

I think we could grow the ref to include the result of invoking startproject.

my feeling is that a new page under https://docs.djangoproject.com/en/5.0/topics/ titled something like "Django project layouts and conventions" might be called for.

This also sounds like a good option but I think it will require more traction/time to get this done.

Should we link to this material from the tutorial? (In my opinion, definitely.)

I agree.

Can we change the verb in the title of the PR, from 'remove' to 'move'?

Can we change the verb in the title of the PR, from 'remove' to 'move'?

Sure, we should follow the existing commit message pattern which is using "Relocated", see 73e8e811416dcb5007ad9cc9d1632aaca95bf302 and 82c71f0168b1c132e499505609d285c6016ed4f2


fix(SNP-1286): rules member ordering

Changes

Changed member-ordering

Changed arguments-ordering.
Added last order for :
- body
- child
- children

Added parameters-ordering

@Sadhorsephile
Can you participate in the review too?


chore: pass port and rpcport arg to bitcoin testcontainer

Adaptations to https://github.com/theborakompanioni/bitcoin-spring-boot-starter/pull/126
Please merge at will!
BitcoindContainerAutoConfigurationTest should run through successfully :pray:
We can discuss further changes in your PR.

Great stuff, thanks! I like consolidating the network and chain properties as a Chain enum.

:+1:
Probably should rename network property to chain as Bitcoin Core has no config "network".. just to try staying consistent.. but that can be done in upcoming PRs.

Can you explain why you needed to take out the lines in the unit tests for 'context.start()'?

Not exactly sure. But apparently, it is not needed (anymore?). There are potentially many lines of code that are redundant. Better to remove them, if they are not useful - what are your thoughts?


Add binary that copies stdin to stdout, stripping escape sequences

I wanted this for testing, and thought others might also find it useful.
It adds a binary that copies standard input to standard output, stripping escape sequences.

Thanks for the PR, but I don't think this is something I want to maintain in this crate.


Fonts don't seem to work in the browser (preloadRemoteFonts)

Describe the bug
I am using typst.ts to generate PDFs in the browser. It works, but I can't figure out how to change fonts. Using preloadRemoteFonts causes the browser to actually fetch the woff files, but the rendered PDF doesn't use them.
It is very likely that I'm holding the typst.ts API wrong.
Reproducer:
I tried reproducing this in a single file, but I cannot get a single-file thing to work at all; visiting https://myriad-dreamin.github.io/typst.ts/preview.html gives me a JS console error: Uncaught (in promise) LinkError: import object field '__wbg_call_3bfa248576352471' is not a Function.
I only managed to reproduce it with a build tool, I chose vite. The reproducer is in https://github.com/WojciechP/typst-fonts-reproducer.
The relevant bit of code:
import { createTypstCompiler } from<EMAIL_ADDRESS>import wasmURL from "@myriaddreamin/typst-ts-web-compiler/pkg/typst_ts_web_compiler_bg.wasm?url";
import { preloadRemoteFonts } from<EMAIL_ADDRESS>
const cc = createTypstCompiler();
await cc.init({
  getModule: () => {
    return { module_or_path: wasmURL };
  },
  beforeBuild: [
    preloadRemoteFonts([
      "https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2",
      "https://fonts.gstatic.com/s/arimo/v29/P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcABrHdwcoaaQw.woff",
    ]),
  ],
});
const lines = [
  "Some text using the default font \\",
  '#set text(font: "Roboto")',
  "Some text using Roboto font",
];
const source = lines.join("\n");

cc.addSource("/main.typ", source);

document.querySelector("#source")!.textContent = source;

const result = await cc.compile({
  format: "pdf",
  mainFilePath: "/main.typ",
  diagnostics: "full",
});
console.log(result.diagnostics);
if (result.result) {
  const blob = new Blob([result.result!], { type: "application/pdf" });
  const link = document.querySelector<HTMLAnchorElement>("#pdf")!;
  link.href = window.URL.createObjectURL(blob);
  link.textContent = "Download PDF";
  link.download = "main.pdf";
}

I would expect the two lines in the resulting PDF to render differently, but they don't. There are no diagnostics returned.
My understanding is that Typst has a font fallback, so when it cannot find a font it uses whatever's available. Passing fallback: false to set text causes the second line to disappear entirely.
Expected behavior
The second line should use Roboto.
Desktop (please complete the following information):
OSX, Firefox 132.0.1
Package/Software version (using command typst-ts-cli --VV full and paste down the output):
I am not using the CLI at all, I am only importing the typst-ts in TypeScript. The relevant bit of my package.json:
 "devDependencies": {
    "typescript": "~5.6.2",
    "vite": "^5.4.10"
  },
  "dependencies": {
    "@myriaddreamin/typst-ts-web-compiler": "^0.5.0-rc9",
<EMAIL_ADDRESS>"^0.5.0-rc9"
  }

Any help or suggestions on how to troubleshoot further would help. Alternatively, any demo that uses multiple fonts would probably help too, but I couldn't find one. Thank you in advance!

visiting https://myriad-dreamin.github.io/typst.ts/preview.html gives me a JS console error: Uncaught (in promise) LinkError: import object field '__wbg_call_3bfa248576352471' is not a Function.

Yeah, I see it is broken. I'll try to fix it.

 preloadRemoteFonts([
      "https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2",
      "https://fonts.gstatic.com/s/arimo/v29/P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcABrHdwcoaaQw.woff",
    ]),

Probably a same issue as https://github.com/Myriad-Dreamin/typst.ts/issues/600#issuecomment-2499978278.

Hello hat618 your woff2 font seems not being identified by typst correctly. I know it by downloading fonts and check it offline:
typst fonts --font-path Downloads

And "Roboto" font is not in the identified list of fonts.
To confirm it, I used the roboto fonts on Google Fonts from the gist and everything works as expected:
$typst.setCompilerInitOptions({
  beforeBuild: [
    preloadRemoteFonts([
      'http://fonts.gstatic.com/s/roboto/v15/7MygqTe2zs9YkP0adA9QQQ.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/T1xnudodhcgwXCmZQ490TPesZW2xOQ-xsNqO47m55DA.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/dtpHsbgPEm2lVWciJZ0P-A.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/iE8HhaRzdhPxC93dOdA056CWcynf_cDxXwCLxiixG1c.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/W5F8_SL0XFawnjxHGsZjJA.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/hcKoSgxdnKlbH5dlTwKbow.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/Uxzkqj-MIMWle-XP2pDNAA.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/daIfzbEw-lbjMyv4rMUUTqCWcynf_cDxXwCLxiixG1c.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/bdHGHleUa-ndQCOrdpfxfw.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/owYYXKukxFDFjr0ZO8NXh6CWcynf_cDxXwCLxiixG1c.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/H1vB34nOKWXqzKotq25pcg.ttf',
      'http://fonts.gstatic.com/s/roboto/v15/b9PWBSMHrT2zM5FgUdtu0aCWcynf_cDxXwCLxiixG1c.ttf',
    ]),
  ],
});

Thank you for a speedy answer! Indeed using the .toff fonts from the linked gists instead of the .woff files solves the issue. Feel free to mark this as duplicate of https://github.com/Myriad-Dreamin/typst.ts/issues/600, I don't know why I hadn't found it myself.

Duplicate of #600


Shadcn Plumbing

Description
Create a super basic control in P.B using Shadcn/ui + Radix. The control should be one of the controls that makes up the BC control. If it is easy, put this into Storybook, otherwise make a new task to do the Storybook work.

Note the instructions for installing shadcn say you can choose between default and New York. Alex said to go with default for now.

Tailwind has some nice suggestions for supporting dark mode https://tailwindcss.com/docs/dark-mode#supporting-system-preference-and-manual-selection

Shadcn set up in platform-bible-react at https://github.com/paranext/paranext-core/tree/shadcn-pbreact


Fix typos

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

Collapsed
https://github.com/github/docs/blob/main/content/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller.md
https://github.com/github/docs/blob/main/content/actions/migrating-to-github-actions/automated-migrations/automating-migration-with-github-actions-importer.md
https://github.com/github/docs/blob/main/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md
https://github.com/github/docs/blob/main/content/apps/github-marketplace/listing-an-app-on-github-marketplace/deleting-your-app-listing-from-github-marketplace.md
https://github.com/github/docs/blob/main/content/apps/oauth-apps/using-oauth-apps/connecting-with-third-party-applications.md
https://github.com/github/docs/blob/main/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
https://github.com/github/docs/blob/main/content/code-security/dependabot/working-with-dependabot/managing-dependabot-on-self-hosted-runners.md
https://github.com/github/docs/blob/main/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
https://github.com/github/docs/blob/main/data/reusables/actions/creating-a-runner-group-for-an-organization.md
What part(s) of the article would you like to see updated?
There are some duplicated words to be deleted, e.g. for, and, to.
Also, in content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md, a additional → an additional.
Additional information
There are such typos in non-markdown files, I'm not sure whether to fix them but I'm willing to commit changes if necessary.

@omvjro Apologies on behalf of our bot! Thank you so much for opening this issue! I'll get this triaged for review ✨

Closing this issue as https://github.com/github/docs/issues/32977 appears to have been opened in its place 💛


Remove import to fix lint error

Details
Fix lint error:
andrew ➜ (main) App npm run lint

><EMAIL_ADDRESS>lint /Users/andrew/Expensidev/App
> eslint . --max-warnings=0

Error while parsing /Users/andrew/Expensidev/App/src/libs/actions/Report.js
Line 29, column 13: Line 29: Identifier 'OptionsListUtils' has already been declared

  27 | import Growl from '../Growl';
  28 | import * as Localize from '../Localize';
> 29 | import * as OptionsListUtils from '../OptionsListUtils';
     |             ^
  30 |
  31 | let currentUserEmail;
  32 | let currentUserAccountID;
`parseForESLint` from parser `/Users/andrew/Expensidev/App/node_modules/babel-eslint/lib/index.js` is invalid and will just be ignored

/Users/andrew/Expensidev/App/src/libs/actions/Report.js
  29:13  error  Parsing error: Identifier 'OptionsListUtils' has already been declared

  1 Remove import to fix lint error
  27 | import Growl from '../Growl';
  28 | import * as Localize from '../Localize';
> 29 | import * as OptionsListUtils from '../OptionsListUtils';
     |             ^
  30 |
  31 | let currentUserEmail;
  32 | let currentUserAccountID;

✖ 1 problem (1 error, 0 warnings)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `eslint . --max-warnings=0`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/andrew/.npm/_logs/2022-01-25T23_23_36_924Z-debug.log

Tests

Run npm lint or check the lint action

CPing this to staging to un-block deploys. It's not an emergency, but there's also no need to wait.

@roryabraham looks like this was merged without passing tests. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

🚀 Cherry-picked to staging by @roryabraham in version: 1.1.33-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @roryabraham in version: 1.1.33-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


launchCamera function crashes app on Android 4.2.2

Description
I have a function that calls ImagePicker.launchCamera(...) and it works fine in later versions of Android but breaks 4.2.2 (Jellybean)
Solution
Does anyone have any solution to this issue?
Additional Information

React Native version: 0.42.3
Development Operating System: Mac

FIX: I commented out lines 281-287 in ImagePickerModule.java that were specific to versions lower than KIT KAT because I do permissions checks on my own anyway.
if (Build.VERSION.SDK_INT <= Build.VERSION_CODES.KITKAT) {
     List<ResolveInfo> resInfoList = reactContext.getPackageManager().queryIntentActivities(cameraIntent, PackageManager.MATCH_DEFAULT_ONLY);
     for (ResolveInfo resolveInfo : resInfoList) {
       String packageName = resolveInfo.activityInfo.packageName;
       reactContext.grantUriPermission(packageName, cameraCaptureURI, Intent.FLAG_GRANT_WRITE_URI_PERMISSION | Intent.FLAG_GRANT_READ_URI_PERMISSION);
     }
   }


Label format selectable

Besides the pseudo-ops it would be good to also allow choosing custom label formats in a way like:
Local label: <prefix>label<postfix>
Global lable:<prefix>label<postfix>
Where prefix/postfix can be choosen. For example, lyxass uses "." prefix for locals and "::" postfix for globals

The on-screen display always shows them plainly.  There's currently no support for locals in the main app -- they're "local or global" until the (theoretically assembler-specific) label localizer gets its hands on them.  There's a TO DO item to improve that, since I'd like to see things like non-unique loop labels on-screen, but that's a bit down the road.

Ok, get it.  Your To-do list is very long ... Anyway just an idea while using your tool.


Performance issue with ProfileService

Found new performance issue (this time reproducing even on x86 desktop!)
Noticeable scrolling freezes starting with this commit https://github.com/Windows-XAML/Template10/commit/ac0235227e82f58cf2705f91db22589dd09abf2d
I actually tested commits from stable nuget package release to latest commit and found exactly when and where new extreme UI freezes (noticeable even on x86 desktop) originated.
To reproduce issue you can navigate from main page to another page, then back to main page (using back button), then to another page again. When you scroll page after some navigations, you should notice very noticeable freezes.
Performance degradation reproduced after some page navigations.
This weird behavior is starting exactly with this commit (https://github.com/Windows-XAML/Template10/commit/ac0235227e82f58cf2705f91db22589dd09abf2d)

Honestly, I don't understand what is the root cause of this issue. Looking at the commit itself, I can not tell it does anything wrong. It merely add new class. Also, when I deleted this class from branch which is branched from latest commit it doesn't help. But when I compile code from previous commit, there is no extreme performance degradation after some page navigations. When I compile code from this commit and newer - there are dire freezes after some page navigations. Code seems to be broken on exactly this commit. But there is no sane reason. Looks like some overlooked fundamental problem like increased memory consumption and frequent garbage collections (I haven't profiled memory consumption so I can't tell), but this commit doesn't introduce anything whic can cause increased memory consumption. It actually doesn't changed anything important. But I clearly and reliably reproduced broken app behavior exactly on this commit. To track this I compiled and tested my app with every commit from stable release and found when issue started to appear. It looks crazy and unreasonable. I'm very confused.

Also, I noticed longer app startup time with this commit. Sometimes it crash on standard splash screen (silently close after long wait). Something is fundamentally wrong.

@Windows-XAML/community can it be because I'm not updated Shell.xaml/Shell.xaml.cs in my app and otherwise use obsolete one from earlier Template10 "Hamburger" project template (from which I originally started my app)? I noticed some changes in Shell.xaml and Shell.xaml.cs in newer versions.

@Opiumtm I don't know even. this: https://github.com/Windows-XAML/Template10/issues/1044 Is killing me... I could not found the root cause....

Leave a comment

@JerryNixon ????


[Feature] number of tests per day per country in the dataset

I was wondering if there is an idea of incorporating number of tests done per day per country in the current dataset.
I am not sure how it could be integrated in the current line-list files but adding a column 'num_tests' could be an idea.
alternatively a separate line-list with:  date, num_tests, positives could handle it.
Thank you,
Million

we could create a folder for test and statistics, would the work?

cool, that works!


Allow uses to specify order of files to display in an entry

Is your feature request related to a problem? Please describe.
A user should be greeted with the "main" descriptor file and the "main" parameter file on a page, rather than which one is alphabetically first, if the Dockstore-publisher so wishes.
For example: This GATK workflow imports a WDL. The WDL it imports is shown first when a user goes to the workflow page. If the user is expecting this WDL to get imported into Terra, they will be disappointed, as it clicking the import button will import the "main" WDL even though the imported WDL is what is shown first. (I'm not against always importing the "main" WDL even when an imported WDL is what is currently selected, but ideally a user shouldn't be importing a WDL they unknowingly may not have even seen.)

Another example: I'd like to have this Terra JSON show up before the local one, as I anticipate someone going to the Dockstore page for this workflow is more likely to want to go to Terra next rather than testing locally.

Describe the solution you'd like
For test parameter files, .dockstore.yml should allow specifying which one is the primary one, or it respected the order I wrote them in. The above example with JSONs actually has a .dockstore.yml that specifies the Terra one first, but because L comes before T, the local one still comes first.

For descriptor files, the implementation will likely vary based on how the workflow was registered, but at a minimum we should consider not having imported WDLs at the top.
Describe alternatives you've considered
Renaming my JSONs, not importing WDLs
┆Issue is synchronized with this Jira Story
┆fixVersions: Dockstore 1.14
┆friendlyId: DOCK-2018
┆sprint: Backlog
┆taskType: Story

Going to prioritize https://github.com/dockstore/dockstore/issues/4004 instead


Error at buid

Hi, at first thank you very much for your realy nice RedMobile feature. I love it.
Im running on a Win10 Machine and i what to set up a custom modul for my phone.
Im not a programmer so the Github world is sometimes realy hard for me, but most oft the time i can handle it after some time, but here i think i need your help..!
Can you please helpt me how to get it work.
things i have done:

Created a new folder in windows
cd into that folder
git clone https://github.com/okhiroyuki/redmobile-modules-generator.git
cd into that gernerated folder
npm i
npm i node-red-contrib-telegrambot
npm run build

now i get a error msg.

In the package.json file the telegrambot is listed.
Before i start the build the noe_modules folder is there, but at that time the error comes, the folder is also gone??
I dont know what do do now...

No sry

I am having the same issue, this is a paid app and paid feature but still it doesn't works.

yes it's annoying - @okhiroyuki why won't you help?

I have on and off come back to trying to figure this one out as you guys.. but i managed to get past the above error today because i figured out that there was a folder missing. When i created this folder "node_modules" in the generator folder and when i did the npm i. it populates that folder with all the modules incl the once you install ontop. then i got past this error and the code creates the folder "dist" itself when running.. however it can not exist that folder when you run because it will spit out a error if the folder is there that it cant create it.
It looks like he is just compressing what is in that folder with Gzip format  level 9 ... wish means you should be able to dump what is in the node_modules folder in with 7zip with zip archive format and complevel 9  should be deflate method. Am going to test if that works.
But i am getting the cmd window upp but it spit out some new errors when trying to do stuff in it that i cant catch... but it looks like it is failing on the compression file creation i have noticed when i saw how he compresses the file together and wondering if that the above is a semi workaround to get it working ... but going to test if that works.

I appreciate the work you're doing on this. Did you have any luck moving
this forward beyond what you wrote here?
Thanks
On Sun, Jan 22, 2023 at 7:52 AM Marlark @.***> wrote:

I have on and off come back to trying to figure this one out as you guys..
but i managed to get past the above error today because i figured out that
there was a folder missing. When i created this folder "node_modules" in
the generator folder and when i did the npm i. it populates that folder
with all the modules incl the once you install ontop. then i got past this
error and the code creates the folder "dist" itself when running.. however
it can not exist that folder when you run because it will spit out a error
if the folder is there that it cant create it.
It looks like he is just compressing what is in that folder with Gzip
format level 9 ... wish means you should be able to dump what is in the
node_modules folder in with 7zip with zip archive format and complevel 9
should be deflate method. Am going to test if that works.
But i am getting the cmd window upp but it spit out some new errors when
trying to do stuff in it that i cant catch... but it looks like it is
failing on the compression file creation i have noticed when i saw how he
compresses the file together and wondering if that the above is a semi
workaround to get it working ... but going to test if that works.
—
Reply to this email directly, view it on GitHub
https://github.com/okhiroyuki/redmobile-modules-generator/issues/4#issuecomment-1399510979,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APHXJJQLR7YUSE6RWF2T5SLWTVCRZANCNFSM5HX4QXEA
.
You are receiving this because you commented.Message ID:
@.***>

@sniicker
Have you tried the latest code and cannot create it successfully?

I have confirmed that the latest code builds fine on Windows 10.
a122835cf2e28117044d0ef74be4763faf53c6f9
Note that there was a case where the build failed if the dist folder was present, so a response has been put in place.


It would be better to expose UIFont properties instead of names and sizes

In the OnboardingViewController class, I propose removing the font name and size properties and instead adding UIFont properties.  Exposing a UIFont property will allow the use of Apple's San Francisco system font.  In WWDC 2015 Session #804 near the 30 minute mark, Apple recommends not accessing these system fonts by name, because doing so essentially returns an unoptimized version of the font.

Yeah I totally agree - that's been bugging me for a while. I'm thinking we could expose it as a property and would probably want to deprecate the size/name properties, and in the near future remove them altogether.
Did you want to open a pull request?

Ok. I've never opened a pull request before. I think this would be a good first one.

@rpstro02 Awesome - let me know if you need any assistance!

This should now be moot as I've exposed the labels themselves as properties. Let me know if you have future issues.


Missing commas in CodeFormatter.sublime-settings

Error trying to parse settings: Unexpected character, expected a comma or closing bracket in Packages/CodeFormatter/CodeFormatter.sublime-settings:88:9
Error trying to parse settings: Unexpected character, expected a comma or closing bracket in Packages/CodeFormatter/CodeFormatter.sublime-settings:179:9

this was fixed  #198


Add end-to-end tests for keyboard shortcuts for the new DMN Editor

The tests should target the DMN Editor envelope and cover the following shortcuts

[ ] cancel action (Escape)
[ ] create group (G)
[ ] copy node (Ctrl/Cmd + C)
[ ] cut node (Ctrl/Cmd + X
[ ] delete node (Delete/Backspace)
[ ] focus on selection (B)
[ ] hide from DRD (X)
[ ] horizontal navigation (Hold Shift)
[ ] move (Up/Down/Left/Right/Shift + Up/Shift + Down/Shift + Left/Shift + Right)
[ ] pan (Hold Alt)
[ ] paste node (Ctrl/Cmd + V)
[ ] redo (Ctrl/Cmd + Shift + Z)
[ ] reset position to origin (Space)
[ ] select/deselect all (A)
[ ] toggle hierarchy highlight (H)
[ ] toggle properties panel (I)
[ ] undo (Ctrl/Cmd + Z)
[ ] zoom (Hold Ctrl)

@ljmotta hi, thank you for the issue, do we target this tests for web-browsers, e.e. playwright tests, or do we target them for VS Code for example?

As using the DMN Editor envelope as target we would need to test on the browser. But we could extended those tests for the VS Code as well when we start creating tests for the extension.


render 'Contain' with null

below this is main query with null return, render with 'number' parameter without problem.
number":null,"user":{"username":"test"}
below this is contain query with null, since render parameter is 'user.username', so datatable cant get '.username' and popup an error.
number":null,"user":{"user":null}
any solutions? thanks

I think the only solution to this problem is to use a custom render callback which can then ignore null objects.

I honestly think just using a custom rendered is fine. Im my use cases mainly I'm generating a link to a belongsTo relationship anyways so during the link generation I'm checking for null.


Statsd Logs not showing up with docker compose

How to reproduce the bug
Add the following lines to superset_config.py
from superset.stats_logger import StatsdStatsLogger
STATS_LOGGER = StatsdStatsLogger(host='localhost', port=8125, prefix='superset')

and the extra param to gunicorn cmd in run-server.sh
--statsd-host localhost:8125
I am also running a development server FLASK_ENV and SUPERSET_ENV set to development
BUT when i  build and run superset from scratch Superset 0.0.0-dev then the statd logger seems to show up locally, it however fails to show up in my docker compose
Expected results
stats_logger should start logging major events like query timings
Actual results
statsd logger does not show up.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

browser type and version: Chrome Version 108.0.5359.94
superset version: 1.51.2
python version: Python 3.9.15
node.js version: v18.11.0
any feature flags active: FLASK_ENV, SUPERSET_ENV = development

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stack traces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
stats_logger shows up when running locally but does not with docker-compose

Maybe @nytai or @john-bodley can help with this one?

This seems like it might warrant being moved to Q&A, if it is a configuration concern and not a bug, per se.


Fix validating length of numbers

Validating the length of numbers was broken in a few places, as noted in #136, here are some fixes.
Basically the bug happens because length is measured and compared using .length, which is not a method on Number, so I'm checking the typeof on values passed into BetweenLengthValidationRule, MaximumLengthValidationRule and MinimumLengthValidationRule. If it's a Number, convert it to a String.
Simples.
This is my first PR, so if I've done something per convention please let me know.
:heart:

Thanks @Zensavona - first please make sure you signed the CLA for contributions.  After that could you please squash these in to a single commit since they are all so small?
Thanks a ton!

Signed the CLA and squashed those commits @PWKad.
I wasn't sure how to-the-letter you guys are about submission guidelines so I thought best to err on the side of more commits.

I'll get this merged in tonight.  Thanks!

@EisenbergEffect CLA check

@PWKad CLA Confirmed.

@Zensavona I'm merging this in but getting a few gulp lint issues for == instead of === - when I make the switch there is a failing test.  Going to add a commit to fix this up hopefully.


render LastError on agent gui even when not JSON

What does this PR do?

Fix display of go check errors in agent GUI, to match the agent status command
Motivation

Go checks that reported errors only displayed Error: UNKNOWN ERROR in the agent GUI. This happened because Python checks report errors as a JSON string, but Go checks don't.
https://datadoghq.atlassian.net/browse/WINA-521
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Create an error in a go check, for example, configure the win32_event_log check to monitor an event log that doesn't exist.
Then ensure that agent status command line, agent GUI collector status page, and the dashboard infra page, show the check error.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Meilisearch timing out and crashing on GVC

Hey,
I am currently using an instance of the search on Google Virtual Computer.
I have not had any issues before, but since deleting one index, I now cannot use the search at all, even simply uploading one row of data crashes the engine
this is my delete request
private static async void DeleteIndexes()
{
using (var httpClient = new HttpClient())
{
httpClient.DefaultRequestHeaders.Add("X-Meili-API-Key", "XXXXXX");
using (var request = new HttpRequestMessage(new HttpMethod("DELETE"), "https://xxxxxxxx/indexes/mattressmannew"))
            {
                var response = await httpClient.SendAsync(request);
                var RESULT = response.Content.ReadAsStringAsync().Result;

                Console.WriteLine(RESULT);
            }
        }

    }

whether I try to search, return index info, anything at all, it now crashes
I can't seem to see why

Hi! What version of MeiliSearch are you using? Were you still indexing the documents when you deleted the index?

hey :) latest version.
I'm deleting an entire index
then requesting documents from another
that process seemed to kill meilisearch to the point where any search request or interaction at all results in a 502

I have now tried the process again and i can confirm it is the deletion of the indexes that crashes the entire system
i have deleted an index because it was not updating, and now the entire Meilisearch is down

Hi! What version of MeiliSearch are you using? Were you still indexing the documents when you deleted the index?

hey :) latest version.
I'm deleting an entire index
then requesting documents from another
that process seemed to kill meilisearch to the point where any search request or interaction at all results in a 504
I have now tried the process again and i can confirm it is the deletion of the indexes that crashes the entire system
i have deleted an index because it was not updating, and now the entire Meilisearch is down

Hello @ALittleMoreDevTeam, and everyone following the issue!
The first RC of MeiliSearch v0.21.0 is out.
We did our best to fix indexation and crash issues. We succeeded to improve it, but not to totally fix them.
You can test this new release by downloading the binaries available in this release.
Or you can use it with docker:
docker run -p 7700:7700 getmeili/meilisearch:v0.21.0rc0 ./meilisearch

We will still improve this after the release of the v0.21.0. We would rather release a non-completely optimized version rather than delay it and, at the same time, delay the release of new features. Be sure we are doing our best to always improve these indexation issues.
As a reminder:

despite the improvements, we always recommend pushing your documents to MeiliSearch by batch and not one by one. The maximum payload size of MeiliSearch is 100Mb and can be optionally increased. It means most of the dataset can be pushed with one call to the API.
If you still have a memory crash, it means the RAM of your machine might not be adapted to your dataset size. We recommend increasing the RAM of your machine.

Thanks for your patience and your help with this! ❤

Hello everyone reading this issue.
I close this issue due to the lack of feedback since it was happening with an old version of Meilisearch.
However, for anyone having issues in general with indexation performance, like this issue, please, refer to this discussion. Your feedback will be really appreciated 🙂


API server access tests are skipped

What happened
Started kube-hunter in active mode with RBAC rules enabled for pod creation.
kube-hunter did not report about successful pod creation.
Expected behavior
kube-hunter reports about successful pod creation

It worked when added ClusterRole for listing namespaces.
The logic behind the hunter is to list namespaces and try to create a pod inside every namespace found.
When there is no access to list namespaces, the hunter will not try to create a pod.
The desired behavior is to create a pod inside the service account namespace when no namespaces discovered.


Added code for Even array solution of Codeforces

I have added Even array solution of Code forces under the Code forces folder in C. @Amit-45 Please review this PR. This will fix issue  #738 .

@Amit-45 Please review this PR. This will close issue #738 .

@Sathwika-02 delete the other file


Can we run gpt-fast from Windows Command Prompt or Powershell?

For this code:
export MODEL_REPO=meta-llama/Llama-2-7b-chat-hf
./scripts/prepare.sh $MODEL_REPO

I could change to:
set MODEL_REPO=meta-llama/Llama-2-7b-chat-hf
But I'm not sure how to proceed further.  Is there a way to run gpt-fast from Windows Command Prompt or Powershell?

I don't think this repo supports powershell - I would suggest using WSL if you want to run this repo on Windows.

@Chillee thanks, but i'm having problems trying to run WSL2 with GPU:
https://github.com/microsoft/WSL/issues/10869

I don't have any plans to support powershell in this repo.


python311Packages.dramatiq: 1.15.0 -> 1.16.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.dramatiq is: Background Processing for Python 3
meta.homepage for python311Packages.dramatiq is: https://github.com/Bogdanp/dramatiq
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.0 with grep in /nix/store/b2x75al3qk3cbngvgbaq8igrsr9x1zrq-python3.11-dramatiq-1.16.0
found 1.16.0 in filename of file in /nix/store/b2x75al3qk3cbngvgbaq8igrsr9x1zrq-python3.11-dramatiq-1.16.0

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
fit-trackee
python311Packages.dramatiq
python311Packages.flask-dramatiq
python311Packages.periodiq
python312Packages.dramatiq
python312Packages.flask-dramatiq
python312Packages.periodiq

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b2x75al3qk3cbngvgbaq8igrsr9x1zrq-python3.11-dramatiq-1.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.dramatiq https://github.com/r-ryantm/nixpkgs/archive/8d268ba60fc4d5bf569d79e7161369321b5fc455.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8d268ba60fc4d5bf569d79e7161369321b5fc455#python311Packages.dramatiq

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b2x75al3qk3cbngvgbaq8igrsr9x1zrq-python3.11-dramatiq-1.16.0
ls -la /nix/store/b2x75al3qk3cbngvgbaq8igrsr9x1zrq-python3.11-dramatiq-1.16.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages marked as broken and skipped:

python312Packages.dramatiq
python312Packages.flask-dramatiq
python312Packages.periodiq

1 package failed to build:

fit-trackee

3 packages built:

python311Packages.dramatiq
python311Packages.flask-dramatiq
python311Packages.periodiq

Maintainer pings
cc @traxys for testing.

fit-trackee breakage seems unrelated


New version: shirowanisan.COEIROINK version 2.3.4

Pull request has been created with komac v2.0.4 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335141 2024-02-10 08:39:30.645 [CORE] DeliveryOptimization error: 0x80190190, extended error: 0x00000000 2024-02-10 08:39:30.685 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FF8B891A465: (caller: 00007FF8B891AD01) Exception(1) tid(1b74) 80190190 Bad request (400).

(Automated response - build 720.)

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


feature: Gse Agent 包管理

Codecov Report

:exclamation: No coverage uploaded for pull request base (V2.2.12-rc@463306a). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             V2.2.12-rc     #696   +/-   ##
=============================================
  Coverage              ?   35.79%
=============================================
  Files                 ?      239
  Lines                 ?    17957
  Branches              ?        0
=============================================
  Hits                  ?     6428
  Misses                ?    11529
  Partials              ?        0

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 463306a...3484c02. Read the comment docs.

并不需要合入 正在删除相关逻辑中


Octokit::TooManyRequests in Communication::Website::Page::Home#sync_with_git_without_delay

Error in Osuny
Octokit::TooManyRequests in Communication::Website::Page::Home#sync_with_git_without_delay
GET https://api.github.com/repos/osunyorg/bordeauxmontaigne-to-bild-or-not-to-bild: 403 - API rate limit exceeded for user ID 90196448. If you reach out to GitHub Support for help, please include the request ID C57A:324FAD:2B95B4B4:2BC1E4A4:6613AD02. // See: https://docs.github.com/rest/overview/rate-limits-for-the-rest-api
View on Bugsnag
Stacktrace
app/services/git/providers/github.rb:119 - default_branch
app/services/git/providers/github.rb:123 - branch_sha
app/services/git/providers/github.rb:150 - tree
app/services/git/providers/github.rb:137 - tree_items_by_path
app/services/git/providers/github.rb:131 - tree_item_at_path
app/services/git/providers/github.rb:89 - git_sha
app/services/git/repository.rb:41 - git_sha
app/services/git/analyzer.rb:68 - exists_on_git?
app/services/git/analyzer.rb:11 - should_create?
app/services/git/repository.rb:73 - block in sync_git_files
app/services/git/repository.rb:71 - each
app/services/git/repository.rb:71 - sync_git_files
app/services/git/repository.rb:25 - sync!
app/models/concerns/with_git.rb:37 - sync_with_git
bin/bundle:113 - load
bin/bundle:113 - <main>

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website#clean_and_rebuild_without_delay

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::Agenda::Event#sync_with_git_without_delay

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::IndirectObject::SyncWithGitJob@elephant

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::UpdateThemeVersionJob@mice


add acknowledgement  to EESEN

The work of TLG is proposed as early as in 2015 by Yajie Miao, whose death in 2016 was really a pity. Please give an acknowledgement  and respect to him.
paper: EESEN: End-to-End Speech Recognition using Deep RNN Models and WFST-based Decoding
github: https://github.com/srvk/eesen

Thanks, please see https://github.com/wenet-e2e/wenet/pull/418.