Safe selectionresult ghent

proper type checking and full tests.
Added code file that runs test. Output: test.txt
cat test.txt

Can you add the output of the test script to the commit message?

done!


Bump to 1.0.4 and rerender with 2.3.2

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


Slow quota check

Finding out why CartoDB/cartodb#1573 threw timeout errors, we found out the following issue at CDB_UserDataSize:
# explain analyze SELECT COALESCE(INT8(SUM(pg_total_relation_size('juanignaciosl.' || table_name))), 0) FROM information_schema.tables                                                                                WHERE table_catalog = current_database() AND table_schema = 'juanignaciosl'                                                                                AND table_name != 'spatial_ref_sys'                                                                                AND table_name != 'cdb_tablemetadata'                                                                                AND table_type = 'BASE TABLE'                                                                                -- exclude raster overview tables                                                                                AND table_name NOT IN (                                                                                SELECT o_table_name FROM raster_overviews                                                                                WHERE o_table_schema = 'juanignaciosl' AND o_table_catalog = current_database()                                                                                )                                                                                -- filter to raster "main" tables                                                                                AND table_name IN (                                                                                SELECT r_table_name FROM raster_overviews                                                                                WHERE r_table_name = table_name                                                                                AND o_table_schema = 'juanignaciosl' AND o_table_catalog = current_database()                                                                                );

 Aggregate  (cost=180666.03..180666.03 rows=1 width=64) (actual time=890.094..890.094 rows=1 loops=1)
   ->  Result  (cost=6730.70..180666.03 rows=1 width=64) (actual time=890.087..890.087 rows=0 loops=1)
         One-Time Filter: (((current_database())::information_schema.sql_identifier)::name = current_database())
         ->  Nested Loop Left Join  (cost=6730.70..180666.03 rows=1 width=64) (actual time=890.079..890.079 rows=0 loops=1)
               ->  Nested Loop  (cost=6730.58..180661.16 rows=1 width=68) (actual time=890.078..890.078 rows=0 loops=1)
                     ->  Seq Scan on pg_namespace nc  (cost=0.00..3.24 rows=1 width=4) (actual time=0.033..0.048 rows=1 loops=1)
                           Filter: ((NOT pg_is_other_temp_schema(oid)) AND (((nspname)::information_schema.sql_identifier)::text = 'juanignaciosl'::text))
                           Rows Removed by Filter: 53
                     ->  Bitmap Heap Scan on pg_class c  (cost=6730.58..180657.92 rows=1 width=73) (actual time=890.023..890.023 rows=0 loops=1)
                           Recheck Cond: (relnamespace = nc.oid)
                           Filter: ((relkind = ANY ('{r,v,f}'::"char"[])) AND (((relname)::information_schema.sql_identifier)::text <> 'spatial_ref_sys'::text) AND (((relname)::information_schema.sql_identifier)::text <> 'cdb_tablemetadata'::text) AND (NOT (hashed SubPlan 1)) AND (((CASE WHEN (nc.oid = pg_my_temp_schema()) THEN 'LOCAL TEMPORARY'::text WHEN (relkind = 'r'::"char") THEN 'BASE TABLE'::text WHEN (relkind = 'v'::"char") THEN 'VIEW'::text WHEN (relkind = 'f'::"char") THEN 'FOREIGN TABLE'::text ELSE NULL::text END)::information_schema.character_data)::text = 'BASE TABLE'::text) AND (pg_has_role(relowner, 'USAGE'::text) OR has_table_privilege(oid, 'SELECT, INSERT, UPDATE, DELETE, TRUNCATE, REFERENCES, TRIGGER'::text) OR has_any_column_privilege(oid, 'SELECT, INSERT, UPDATE, REFERENCES'::text)) AND (SubPlan 2))
                           Rows Removed by Filter: 741
                           ->  Bitmap Index Scan on pg_class_relname_nsp_index  (cost=0.00..6319.72 rows=806 width=0) (actual time=3.426..3.426 rows=943 loops=1)
                                 Index Cond: (relnamespace = nc.oid)
                           SubPlan 1
                             ->  Result  (cost=0.25..410.86 rows=1 width=64) (actual time=6.298..6.298 rows=0 loops=1)
                                   One-Time Filter: (current_database() = current_database())
                                   ->  Nested Loop  (cost=0.25..410.86 rows=1 width=64) (actual time=6.294..6.294 rows=0 loops=1)
                                         ->  Nested Loop  (cost=0.17..410.75 rows=1 width=68) (actual time=6.292..6.292 rows=0 loops=1)
                                               ->  Nested Loop  (cost=0.08..385.16 rows=1 width=72) (actual time=6.292..6.292 rows=0 loops=1)
                                                     Join Filter: (n.oid = c_1.relnamespace)
                                                     ->  Nested Loop  (cost=0.00..369.50 rows=2 width=12) (actual time=6.290..6.290 rows=0 loops=1)
                                                           Join Filter: (n.oid = s.connamespace)
                                                           Rows Removed by Join Filter: 85
                                                           ->  Seq Scan on pg_namespace n  (cost=0.00..3.19 rows=1 width=4) (actual time=0.007..0.013 rows=1 loops=1)
                                                                 Filter: (nspname = 'juanignaciosl'::name)
                                                                 Rows Removed by Filter: 53
                                                           ->  Seq Scan on pg_constraint s  (cost=0.00..366.00 rows=91 width=8) (actual time=2.892..6.212 rows=85 loops=1)
                                                                 Filter: (consrc ~~ '%_overview_constraint(%'::text)
                                                                 Rows Removed by Filter: 8509
                                                     ->  Index Scan using pg_class_oid_index on pg_class c_1  (cost=0.08..7.83 rows=1 width=72) (never executed)
                                                           Index Cond: (oid = s.conrelid)
                                                           Filter: ((NOT pg_is_other_temp_schema(relnamespace)) AND (s.connamespace = relnamespace) AND ((relkind)::text = ANY ('{r,v,m,f}'::text[])))
                                               ->  Index Scan using pg_attribute_relid_attnum_index on pg_attribute a  (cost=0.08..25.54 rows=15 width=8) (never executed)
                                                     Index Cond: (attrelid = c_1.oid)
                                                     Filter: (NOT attisdropped)
                                         ->  Index Scan using pg_type_oid_index on pg_type t_1  (cost=0.08..0.11 rows=1 width=4) (never executed)
                                               Index Cond: (oid = a.atttypid)
                                               Filter: (typname = 'raster'::name)
                           SubPlan 2
                             ->  Result  (cost=0.25..428.69 rows=1 width=93) (actual time=7.028..7.028 rows=0 loops=125)
                                   One-Time Filter: (current_database() = current_database())
                                   ->  Nested Loop  (cost=0.25..428.69 rows=1 width=93) (actual time=7.024..7.024 rows=0 loops=125)
                                         Join Filter: (c_2.relnamespace = n_1.oid)
                                         ->  Nested Loop  (cost=0.25..425.50 rows=1 width=101) (actual time=7.022..7.022 rows=0 loops=125)
                                               ->  Nested Loop  (cost=0.17..425.39 rows=1 width=105) (actual time=7.020..7.020 rows=0 loops=125)
                                                     ->  Nested Loop  (cost=0.08..399.81 rows=1 width=109) (actual time=7.018..7.018 rows=0 loops=125)
                                                           ->  Seq Scan on pg_constraint s_1  (cost=0.00..391.71 rows=1 width=101) (actual time=7.014..7.014 rows=0 loops=125)
                                                                 Filter: ((consrc ~~ '%_overview_constraint(%'::text) AND ((split_part(split_part(consrc, '''::name'::text, 2), ''''::text, 2))::name = ((c.relname)::information_schema.sql_identifier)::name))
                                                                 Rows Removed by Filter: 8594
                                                           ->  Index Scan using pg_class_oid_index on pg_class c_2  (cost=0.08..8.09 rows=1 width=8) (never executed)
                                                                 Index Cond: (oid = s_1.conrelid)
                                                                 Filter: ((NOT pg_is_other_temp_schema(relnamespace)) AND (s_1.connamespace = relnamespace) AND ((relkind)::text = ANY ('{r,v,m,f}'::text[])))
                                                     ->  Index Scan using pg_attribute_relid_attnum_index on pg_attribute a_1  (cost=0.08..25.54 rows=15 width=8) (never executed)
                                                           Index Cond: (attrelid = c_2.oid)
                                                           Filter: (NOT attisdropped)
                                               ->  Index Scan using pg_type_oid_index on pg_type t_2  (cost=0.08..0.11 rows=1 width=4) (never executed)
                                                     Index Cond: (oid = a_1.atttypid)
                                                     Filter: (typname = 'raster'::name)
                                         ->  Seq Scan on pg_namespace n_1  (cost=0.00..3.19 rows=1 width=4) (never executed)
                                               Filter: (nspname = 'juanignaciosl'::name)
               ->  Nested Loop  (cost=0.11..4.86 rows=1 width=4) (never executed)
                     ->  Index Scan using pg_type_oid_index on pg_type t  (cost=0.08..4.82 rows=1 width=8) (never executed)
                           Index Cond: (c.reloftype = oid)
                     ->  Index Only Scan using pg_namespace_oid_index on pg_namespace nt  (cost=0.03..0.03 rows=1 width=4) (never executed)
                           Index Cond: (oid = t.typnamespace)
                           Heap Fetches: 0
 Total runtime: 890.317 ms
(68 rows)

Querying information_schema.tables view is slow and costly. A temporal workaround is disabling quota checks, but it should be improved, since it's performed many times.

this query gives the same results but 100x
with raster_tables as (
SELECT o_table_name, r_table_name FROM raster_overviews
      WHERE o_table_schema = 'javi' AND o_table_catalog = current_database()
),
user_tables as (
    SELECT table_name
    FROM information_schema.tables
      WHERE table_catalog = current_database() AND table_schema = 'javi'
        AND table_name != 'spatial_ref_sys'
        AND table_name != 'cdb_tablemetadata'
        AND table_type = 'BASE TABLE'
),
table_cat as (
    select table_name, EXISTS(select * from raster_tables where o_table_name = table_name) as is_overview, EXISTS(select * from raster_tables where r_table_name = table_name) as is_raster from user_tables
),

sizes as (
    select COALESCE(INT8(SUM(pg_total_relation_size('"javi"."' || table_name || '"')))) s,  CASE WHEN is_overview THEN 0 WHEN is_raster then 1 else 0.5 END as mul from table_cat group by is_overview, is_raster
)
select sum(s*mul) from sizes

schema_name i used is 'javi'


Fix missing jemalloc linking

The 2.3.0 code refactor accidentally dropped linking against jemalloc, and as a result memory usage is much higher.
This restores it.

NB: This patch is cherry-picked into the 2.3.0-2 deb releases.


Issue

[INF] Ceyeio is not configured
[ERR] Using OOB Server: ceyeio is not vaild

https://github.com/zan8in/afrog/wiki/Configuration


CVE-2024-24786 - GHSA-8r3f-844c-mc37

A CVE with a moderate severity was published.
https://github.com/advisories/GHSA-8r3f-844c-mc37
The protobuf dependency needs to be updated to v1.33.0 or newer to mitigate this CVE.

fixed with https://marketplace.upbound.io/providers/crossplane-contrib/provider-keycloak/v0.14.0


Fix url and baseurl

An sccache: command not found certainly not related to this trivial PR.
@TriplEight is there anything you can do?

An sccache: command not found certainly not related to this trivial PR.
@TriplEight is there anything you can do?

fixing in https://github.com/paritytech/react-native-substrate-sign/pull/7

fixing in https://github.com/paritytech/react-native-substrate-sign/pull/7

Thanks, I relaunched the job

Thanks, I relaunched the job

I think first you want to rebase

I think first you want to rebase

lnded, for a typo I'll just merge though

lnded, for a typo I'll just merge though


Prepare to meet with OnShape

AguaClara Overview:
Water treatment plants scale with design flow rate. This means that hundreds of parameters can change with even small adjustments in flow rate. The adjustments change according to complex hydraulic equations that are currently resolved in Python. the resulting "physical parameters" that satisfy the hydraulic parameters are passed to CAD. Some CAD software draws the resulting plant. This was originally done in MathCAD and AutoCAD in place of Python and OnShape. The switch came because the old process was too difficult for students to maintain. Designing and integrating parts became prohibitively complex. However, this old system did successfully design 14 treatment plants currently built in Honduras.
Challenges with the old system:

took 10+ minutes to test a new design or any change to the design
no automated testing
To insert an elbow, for instance, you had to work within the global coordinate space - adding up many dimensions. This was error prone and time consuming.
Relied on outdated, buggy MathCAD software
Didn't take advantage of modern parametric design principles

Current approach with Fusion:

Generate a nested YAML with all physical parameters listed.
Upload the YAML to the Fusion document by cycling through the parameters of each included part.
The parts update. So we have to manually update the higher level parts to use the new version of the linked parts. This often breaks.

Issues:

Fusion parameters are far more limited than OnShape configurations. Parameters just support quantities.
Fusion has poor performance since cycling through every parameter is computationally intensive.
Fusion has strange parameters scaling performance. Parameter variables aren't placed within the timeline, causing weird effects within sketches occasionally.
Fusion doesn't easily support link sharing, meaning we had to upload the design manually to a GitHub repo and write some code within our plugin to pull it manually.
No built-in BOM or FeatureScript.

Should we use assemblies at all? Or just multi-part studios with derived parts? Can we derive parts infinitely deep?
Assembly Pros:

easy to connect parts manually
reduces feature list size, perhaps making parts more manageable
perhaps performance pros to using assemblies over large part studios?
Support in-context editing, allowing information to flow from an assembly to a part within the assembly.

Assembly Cons:

not possible to connect parts parametrically. what happens when we switch from one filter type to another? How do you dynamically "select" another part to be imported in? No "assembly configurations".

Programming Questions:

Is cycling through the YAML and uploading key-value pairs for each mentioned particular component a sound approach? I would edit the "derived part" feature to include the configuration outlined within the YAML.

Modeling Questions:

Within assemblies, what is best practice for selecting different configurations? Assemblies don't have configurations, so what is best practice for dynamically adding and removing subassemblies/ configured parts? For example, say I want to add
How do I make a "reactive component"? One that can scale according to the assembly I put it in? For instance, when I put a pipe within a tank, and I want it to "auto-scale" from one fitting to another without having to specify the length? Should I be using in-context design? Is there any way to "auto-update" contexts?
Why don't mates move with transforms in multi-part studios?
Any way to specify functions instead of variables? define a function like headloss. This would live in the feature list... But that would discourage reusability.
Tell me more about "routing"...

Can it handle the LFOM with i rows with j(i) holes in each row?
The designs you suggest showing should provide a good context for the discussion.

I met with OnShape last Friday. They had the following suggestions:

Don't write much python. Try to include all logic within featureScript. Python can be used to produce the small set of dimensions that are directly determined by hydraulic equations. We need to precisely define this set. I don't think a clear set for the plant has been developed. My proposal is we think of the minimum set that will allow scaling between 12 and 60 L/s. Then, as we need more adjustability, we can "hand over" parameters to python to control. An example is the sed tank pipe. By allowing OnShape to always use a 5 m long lance of 8" tubing, we eliminate the need to calculate any of the hydraulics. Indeed, all we need to specify is the number of sed tanks. This sparse list will be the interface, so to speak, between python and onshape. I'm starting a sparse list here.
Use master sketches for determining global placement of unit processes. These sketches can have mate connectors built in that abide sketch constraints as needed.
Build reusable features when needing special geometry. This way we can utilize FeatureScripts purpose-built design. much faster than Fusion.


qtPrepareTool qmake function fails to locate perl scripts

Describe the bug
The patched qtPrepareTool qmake function in the qt5.qtbase package fails to detect perl scripts (specifically syncqt.pl), causing a failure when trying to build qtwebengine manually.
To Reproduce
Steps to reproduce the behavior:

nix-shell -p pkg-config qt5Full ffmpeg_4 libwebp libopus xorg.libX11 gperf bison python2 mesa libglvnd nss dbus fontconfig xorg.libXcomposite xorg.libXcursor xorg.libXi xorg.libXtst libjpeg git ninja
git clone --recursive https://code.qt.io/qt/qtwebengine.git && cd qtwebengine
qmake && make

Expected behavior
The build completes successfully.
Additional context
After building gn, the build fails with the following error:
...
cd core/ && ( test -e Makefile || /nix/store/qys53np1vhsgz6qpg7vk8pn56wrjj6kf-qt-full-5.12.6/bin/qmake -o Makefile /home/michael/src/tmp/qtwebengine/src/core/core.pro ) && make -f Makefile
make[2]: Entering directory '/home/michael/src/tmp/qtwebengine/src/core'
( test -e Makefile.core_headers || /nix/store/qys53np1vhsgz6qpg7vk8pn56wrjj6kf-qt-full-5.12.6/bin/qmake -o Makefile.core_headers /home/michael/src/tmp/qtwebengine/src/core/core_headers.pro ) && make -f Makefile.core_headers
Project MESSAGE: -module QtWebEngineCore -version 6.0.0 -outdir /home/michael/src/tmp/qtwebengine -builddir /home/michael/src/tmp/qtwebengine /home/michael/src/tmp/qtwebengine
sh: -module: not found
Project ERROR: Failed to run: -module QtWebEngineCore -version 6.0.0 -outdir /home/michael/src/tmp/qtwebengine -builddir /home/michael/src/tmp/qtwebengine /home/michael/src/tmp/qtwebengine
make[2]: *** [Makefile:48: sub-core_headers-pro-make_first] Error 3
make[2]: Leaving directory '/home/michael/src/tmp/qtwebengine/src/core'
make[1]: *** [Makefile:78: sub-core-make_first] Error 2
make[1]: Leaving directory '/home/michael/src/tmp/qtwebengine/src'
make: *** [Makefile:49: sub-src-make_first] Error 2

This is because qtPrepareTool(QMAKE_SYNCQT, syncqt, , system) is failing to find syncqt.pl on the system, and returns an empty string instead. This function is patched in nixpkgs here:
https://github.com/NixOS/nixpkgs/blob/2197fed076cf8b82f8cffeb676e9a025ce33e9b7/pkgs/development/libraries/qt-5/5.12/qtbase.patch.d/0003-qtbase-mkspecs.patch#L372-L384
The original (upstream) version the function checked that syncqt.pl existed in the QT_HOST_BINS directory. The patched version checks that syncqt exists in the user's path (which it doesn't), and then appends .pl to the result.
Instead, perhaps the function should be patched to run command -v $$2.pl if the result of command -v $$2 is empty.
Metadata

system: "x86_64-linux"
host os: Linux 5.3.8+
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.3.1
channels(michael): "nixpkgs-20.03pre204216.cc6cf0a96a6"
nixpkgs: /home/michael/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Still important, just encountered this while trying to package something for Nixpkgs.
The project loads Qt's mkspecs/features/qt_module_headers.prfwhich attempts to find Qt's own syncqt.pl tool (${qtbase.dev}/bin/syncqt.pl) and errors out.
Project MESSAGE: -module UbuntuGestures -version 5.5.0 -outdir /build/source -builddir /build/source /build/source
sh: -module: not found
Project ERROR: Failed to run: -module UbuntuGestures -version 5.5.0 -outdir /build/source -builddir /build/source /build/source

error location: https://github.com/qt/qtbase/blob/5.15.0/mkspecs/features/qt_module_headers.prf#L28
The intended output of this from a CI run:
Project MESSAGE: perl -w /usr/lib/qt5/bin/syncqt.pl -module UbuntuGestures -version 5.5.0 -outdir '/build/ubuntu-ui-toolkit-1.3.2192~0ubports1+0~20201106203828.18~1.gbp62f90d' /build/ubuntu-ui-toolkit-1.3.2192~0ubports1+0~20201106203828.18~1.gbp62f90d

Possibly related: The script's interpreter is set to #!/usr/bin/env perl, which doesn't seem to work while using nix-build. Testing syncqt.pl within configurePhase gives:
/nix/store/zbdjq217kqq86d5qnn8aiqpf200m6j98-stdenv-linux/setup: /nix/store/cixibhdl3dfmj65w17ip55m16m04gkhw-qtbase-5.15.0-dev/bin/syncqt.pl: /usr/bin/env: bad interpreter: No such file or directory

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/proper-way-of-adding-qt5-patch-to-nixpkgs/11835/1

Should be fixed by #118904.


Conversion of VB.NET to C#

Now you have a great Roslyn based converter for C# to VB.NET conversion. Are there any plans to create a converter for VB.NET to C#?
Do you already have started with anything like that? Do you need support, I might could take some parts if necessary.

Please see https://github.com/icsharpcode/RefactoringEssentials/blob/master/converter.txt
It is not implemented (not even started). It is basically up for grabs as @siegfriedpammer definitely won't have time the next two quarters to do any meaningful work.

Thanks for clarification. I might have a look at the current converter and try to figure out how to start with an vb to c# converter.
If anyone have hints or notes, you're welcome.

Yes, I would start by implementing it in the same way as the C#2VB converter. As @christophwille mentioned, I am currently doing a lot other things, but I might be able to take a look at your PRs and give feedback before merging them. But, please keep in mind that I might not have the time to respond immediately.

Now we're talking! I'll see if I can find the time to help with this as well. I am very interested in converting our company's code base from VB to C# and the only thing missing to convince my boss is a reliable piece of software to do the work (at least the bulk of it). It's been over 5 years that I've wanted to do this, maybe now I'll finally be able to do it.

@kelps That's exactly my story ;)
Let's use my repository as new "master". I already started and successfully passed the first unit test. Let's discuss further on gitter.

Conversion of VB.NET to C# was implemented in 7c9fed45d961554627e3957edfdcc120d2063857 and the following commits.

Another option: https://github.com/wbennett/DotNetTranslator


mesa: 11.2.2 -> 12.0.1

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change (I don't think i'll ever make it)
[x] Tested execution of all binary files (none)
[x] Fits CONTRIBUTING.md.

There's a regression: llvm reference is retained from the main output after this PR.

So, there are more libraries that need to be moved to "$drivers/lib"? I can I check which?

For reference checking I use just grep hash-of-llvm -R ./result.

I removed the references and fixed the conflict. What's next?

It looks good. I suppose you haven't tried running a system on some of the drivers?

I staged it, but we should test a little before merging to master.

I have been using it on my system for a while: I have played a couple games with openGL 4.x requirement (that I couldn't run before) and programs with graphic acceleration and everything seems fine to me.

Great, thanks!

This PR has been accidentally (?) reverted in 9adad8612b082bcbae30c81678a04b79a44079a4, see #17738.

Fixed now in #17957


stack test failing

When using stack test the following errors are produced on my side:
PS D:\StudiumsZeug\Bachelorarbeit\duo-lang> stack test
duo-lang-<IP_ADDRESS>: unregistering (components added: test:duo-lang-test)
duo-lang> configure (lib + exe + test)
Configuring duo-lang-<IP_ADDRESS>...
duo-lang> build (lib + exe + test)
Preprocessing library for duo-lang-<IP_ADDRESS>..
Building library for duo-lang-<IP_ADDRESS>..
Preprocessing executable 'duo' for duo-lang-<IP_ADDRESS>..
Building executable 'duo' for duo-lang-<IP_ADDRESS>..
Preprocessing test suite 'duo-lang-test' for duo-lang-<IP_ADDRESS>..
Building test suite 'duo-lang-test' for duo-lang-<IP_ADDRESS>..
duo-lang> copy/register
Installing library in D:\StudiumsZeug\Bachelorarbeit\duo-lang\.stack-work\install\e0eb82b7\lib\x86_64-windows-ghc-9.0.2\duo-lang-<IP_ADDRESS>-4olvjgSRS0x4iU6ePVboWQ
Installing executable duo in D:\StudiumsZeug\Bachelorarbeit\duo-lang\.stack-work\install\e0eb82b7\bin
Registering library for duo-lang-<IP_ADDRESS>..
duo-lang> test (suite: duo-lang-test)

All examples are locally closed
  All examples are locally closed.
    Examples in examples/VexingParse.duo are locally closed
      cons2 does not contain dangling deBruijn indizes
    Examples in examples/TypeClassInstance.duo are locally closed
      eq does not contain dangling deBruijn indizes
      Reader does not contain dangling deBruijn indizes
      Show does not contain dangling deBruijn indizes
      Equals does not contain dangling deBruijn indizes
      Differ does not contain dangling deBruijn indizes
      Equals does not contain dangling deBruijn indizes
      Differ does not contain dangling deBruijn indizes
    Examples in examples/TypeClasses.duo are locally closed
      elem does not contain dangling deBruijn indizes
      Equals does not contain dangling deBruijn indizes
      Differ does not contain dangling deBruijn indizes
    Examples in examples/Tutorial.duo are locally closed
      isZSugared does not contain dangling deBruijn indizes
      isFiveZ does not contain dangling deBruijn indizes
      isZ does not contain dangling deBruijn indizes
      constFalse does not contain dangling deBruijn indizes
      constTrue does not contain dangling deBruijn indizes
      convolutedTwo does not contain dangling deBruijn indizes
      twoSugared does not contain dangling deBruijn indizes
      two does not contain dangling deBruijn indizes
      true does not contain dangling deBruijn indizes
    Examples in examples/Subsumption.duo are locally closed
      ex15sub does not contain dangling deBruijn indizes
      ex15 does not contain dangling deBruijn indizes
      ex14sub does not contain dangling deBruijn indizes
      ex14 does not contain dangling deBruijn indizes
      ex13sub does not contain dangling deBruijn indizes
      ex13 does not contain dangling deBruijn indizes
      ex12sub does not contain dangling deBruijn indizes
      ex12 does not contain dangling deBruijn indizes
      ex11sub does not contain dangling deBruijn indizes
      ex11 does not contain dangling deBruijn indizes
      ex10sub does not contain dangling deBruijn indizes
      ex10 does not contain dangling deBruijn indizes
      ex09sub does not contain dangling deBruijn indizes
      ex09 does not contain dangling deBruijn indizes
      ex08sub does not contain dangling deBruijn indizes
      ex08 does not contain dangling deBruijn indizes
      ex07sub does not contain dangling deBruijn indizes
      ex07 does not contain dangling deBruijn indizes
      ex06sub does not contain dangling deBruijn indizes
      ex06 does not contain dangling deBruijn indizes
      ex05sub does not contain dangling deBruijn indizes
      ex05 does not contain dangling deBruijn indizes
      ex04sub does not contain dangling deBruijn indizes
      ex04 does not contain dangling deBruijn indizes
      ex03sub does not contain dangling deBruijn indizes
      ex03 does not contain dangling deBruijn indizes
      ex02sub does not contain dangling deBruijn indizes
      ex02 does not contain dangling deBruijn indizes
      ex01sub does not contain dangling deBruijn indizes
      ex01 does not contain dangling deBruijn indizes
    Examples in examples/Sorting.duo are locally closed
      Could not load examples. FAILED [1]
    Examples in examples/Primitives.duo are locally closed
      yf does not contain dangling deBruijn indizes
      xf does not contain dangling deBruijn indizes
      y does not contain dangling deBruijn indizes
      x does not contain dangling deBruijn indizes
    Examples in examples/Prelude.duo are locally closed
      impossiblePrd does not contain dangling deBruijn indizes
    Examples in examples/ParserAlt.duo are locally closed
      Could not load examples. FAILED [2]
    Examples in examples/Parser.duo are locally closed
      l9 does not contain dangling deBruijn indizes
      l8 does not contain dangling deBruijn indizes
      l7 does not contain dangling deBruijn indizes
      l6 does not contain dangling deBruijn indizes
      l5 does not contain dangling deBruijn indizes
      l4 does not contain dangling deBruijn indizes
      parseComplicated does not contain dangling deBruijn indizes
      parseOneTwoFour does not contain dangling deBruijn indizes
      parseOneTwoThree does not contain dangling deBruijn indizes
      l3 does not contain dangling deBruijn indizes
      parseOnes does not contain dangling deBruijn indizes
      parseTwoOrOne does not contain dangling deBruijn indizes
      parseOneTwo does not contain dangling deBruijn indizes
      parseOne does not contain dangling deBruijn indizes
      l2 does not contain dangling deBruijn indizes
      l1 does not contain dangling deBruijn indizes
      many does not contain dangling deBruijn indizes
      many1 does not contain dangling deBruijn indizes
      alt does not contain dangling deBruijn indizes
      seq does not contain dangling deBruijn indizes
      failure does not contain dangling deBruijn indizes
      success does not contain dangling deBruijn indizes
      lit does not contain dangling deBruijn indizes
    Examples in examples/Ord.duo are locally closed
      cmp does not contain dangling deBruijn indizes
      Compare does not contain dangling deBruijn indizes
      Compare does not contain dangling deBruijn indizes
    Examples in examples/ICFP\ParsimoniousFilter.duo are locally closed
      Could not load examples. FAILED [3]
    Examples in examples/ICFP\Icfp22example.duo are locally closed
      Could not load examples. FAILED [4]
    Examples in examples/DeMorgan.duo are locally closed
      Could not load examples. FAILED [5]
    Examples in examples/Compilertests.duo are locally closed
      ex12 does not contain dangling deBruijn indizes
      ex11 does not contain dangling deBruijn indizes
      ex10 does not contain dangling deBruijn indizes
      ex9 does not contain dangling deBruijn indizes
      ex8 does not contain dangling deBruijn indizes
      ex7 does not contain dangling deBruijn indizes
      ex6 does not contain dangling deBruijn indizes
      ex5 does not contain dangling deBruijn indizes
      ex4 does not contain dangling deBruijn indizes
      ex3 does not contain dangling deBruijn indizes
      ex2 does not contain dangling deBruijn indizes
      ex1 does not contain dangling deBruijn indizes
      mltNominal does not contain dangling deBruijn indizes
      addNominal does not contain dangling deBruijn indizes
      fixS does not contain dangling deBruijn indizes
      idTwo does not contain dangling deBruijn indizes
      idPolyThree does not contain dangling deBruijn indizes
      idPoly does not contain dangling deBruijn indizes
      idNominal does not contain dangling deBruijn indizes
      id does not contain dangling deBruijn indizes
      idPolyTwo does not contain dangling deBruijn indizes
      id1 does not contain dangling deBruijn indizes
    Examples in examples/Callcc.duo are locally closed
      peirce does not contain dangling deBruijn indizes
    Examples in std/Prim\Strings.duo are locally closed
      hello3 does not contain dangling deBruijn indizes
      prepend does not contain dangling deBruijn indizes
      append does not contain dangling deBruijn indizes
      helloBoxed does not contain dangling deBruijn indizes
      hello does not contain dangling deBruijn indizes
    Examples in std/Prim\I64.duo are locally closed
      mod does not contain dangling deBruijn indizes
      div does not contain dangling deBruijn indizes
      mul does not contain dangling deBruijn indizes
      sub does not contain dangling deBruijn indizes
      add does not contain dangling deBruijn indizes
      i2 does not contain dangling deBruijn indizes
      i1 does not contain dangling deBruijn indizes
    Examples in std/Prim\F64.duo are locally closed
      divf does not contain dangling deBruijn indizes
      mulf does not contain dangling deBruijn indizes
      subf does not contain dangling deBruijn indizes
      addf does not contain dangling deBruijn indizes
      f2 does not contain dangling deBruijn indizes
      f1 does not contain dangling deBruijn indizes
    Examples in std/Data\Tensor.duo are locally closed
      Could not load examples. FAILED [6]
    Examples in std/Data\Plus.duo are locally closed
      Could not load examples. FAILED [7]
    Examples in std/Data\PeanoStructural.duo are locally closed
      nateq does not contain dangling deBruijn indizes
      mul does not contain dangling deBruijn indizes
      add does not contain dangling deBruijn indizes
    Examples in std/Data\PeanoRefinement.duo are locally closed
      nateq does not contain dangling deBruijn indizes
      mul does not contain dangling deBruijn indizes
      add does not contain dangling deBruijn indizes
    Examples in std/Data\Peano.duo are locally closed
      natgeq does not contain dangling deBruijn indizes
      natmax does not contain dangling deBruijn indizes
      nateq does not contain dangling deBruijn indizes
      mul does not contain dangling deBruijn indizes
      add does not contain dangling deBruijn indizes
    Examples in std/Data\Maybe.duo are locally closed
      fromMaybe does not contain dangling deBruijn indizes
      isNothing does not contain dangling deBruijn indizes
      isJust does not contain dangling deBruijn indizes
      maybe does not contain dangling deBruijn indizes
    Examples in std/Data\List.duo are locally closed
      scanl does not contain dangling deBruijn indizes
      sum does not contain dangling deBruijn indizes
      any does not contain dangling deBruijn indizes
      all does not contain dangling deBruijn indizes
      concatMap does not contain dangling deBruijn indizes
      concat does not contain dangling deBruijn indizes
      foldl does not contain dangling deBruijn indizes
      foldr does not contain dangling deBruijn indizes
      filter does not contain dangling deBruijn indizes
      map does not contain dangling deBruijn indizes
      reverse does not contain dangling deBruijn indizes
      append does not contain dangling deBruijn indizes
      length does not contain dangling deBruijn indizes
    Examples in std/Data\FunCofunNeg.duo are locally closed
      Could not load examples. FAILED [8]
    Examples in std/Data\BoolStructural.duo are locally closed
      impl does not contain dangling deBruijn indizes
      nor does not contain dangling deBruijn indizes
      nand does not contain dangling deBruijn indizes
      or does not contain dangling deBruijn indizes
      and does not contain dangling deBruijn indizes
      ifthenelse does not contain dangling deBruijn indizes
      not does not contain dangling deBruijn indizes
    Examples in std/Data\BoolRefinement.duo are locally closed
      impl does not contain dangling deBruijn indizes
      nor does not contain dangling deBruijn indizes
      nand does not contain dangling deBruijn indizes
      or does not contain dangling deBruijn indizes
      and does not contain dangling deBruijn indizes
      ifthenelse does not contain dangling deBruijn indizes
      not does not contain dangling deBruijn indizes
    Examples in std/Data\Bool.duo are locally closed
      impl does not contain dangling deBruijn indizes
      nor does not contain dangling deBruijn indizes
      nand does not contain dangling deBruijn indizes
      or does not contain dangling deBruijn indizes
      and does not contain dangling deBruijn indizes
      ifthenelse does not contain dangling deBruijn indizes
      not does not contain dangling deBruijn indizes
    Examples in std/Data\BinaryTree.duo are locally closed
      foldTree does not contain dangling deBruijn indizes
      filterTree does not contain dangling deBruijn indizes
      appendTree does not contain dangling deBruijn indizes
      mapTree does not contain dangling deBruijn indizes
      fromList does not contain dangling deBruijn indizes
      toList does not contain dangling deBruijn indizes
      insertTree does not contain dangling deBruijn indizes
      depth does not contain dangling deBruijn indizes
    Examples in std/Codata\With.duo are locally closed
      pair does not contain dangling deBruijn indizes
      proj2 does not contain dangling deBruijn indizes
      proj1 does not contain dangling deBruijn indizes
    Examples in std/Codata\Stream.duo are locally closed
      Could not load examples. FAILED [9]
    Examples in std/Codata\Par.duo are locally closed
      Could not load examples. FAILED [10]
    Examples in std/Codata\Function.duo are locally closed
      omega does not contain dangling deBruijn indizes
      fixLazy does not contain dangling deBruijn indizes
      fix does not contain dangling deBruijn indizes
      id2 does not contain dangling deBruijn indizes
      thrice does not contain dangling deBruijn indizes
      twice does not contain dangling deBruijn indizes
      compose does not contain dangling deBruijn indizes
      idTo does not contain dangling deBruijn indizes
      id does not contain dangling deBruijn indizes
ExampleSpec
  All the programs in the "test/Counterexamples/" folder can be parsed.
    The counterexample test/Counterexamples/CE_001.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_002.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_003.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_004.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_005.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_006.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_007.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_008.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_009.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_010.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_011.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_012.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_013.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_014.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_015.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_016.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_017.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_018.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_019.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_020.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_021.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_022.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_023.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_024.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_025.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_026.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_027.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_028.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_029.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_030.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_031.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_032.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_033.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_034.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_035.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_036.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_037.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_038.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_039.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_040.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_041.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_042.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_043.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_044.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_045.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_046.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_047.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_048.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_049.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_050.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_051.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_052.duo can be parsed
      Can be parsed
    Spec.TypeInferenceExamples[29:24]
      # PENDING: Could not parse file test/Counterexamples/CE_053.duo
Reason: Constraint Solver for type class methods not implemented yet.
    The counterexample test/Counterexamples/CE_054.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_055.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/CE_057.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056a.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056b.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056c.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056d.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056e.duo can be parsed
      Can be parsed
    The counterexample test/Counterexamples/Subsumption\CE_056f.duo can be parsed
      Can be parsed
  All the programs in the "test/Counterexamples/" folder don't typecheck.
    The counterexample test/Counterexamples/CE_001.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_002.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_003.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_004.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_005.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_006.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_007.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_008.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_009.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_010.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_011.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_012.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_013.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_014.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_015.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_016.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_017.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_018.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_019.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_020.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_021.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_022.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_023.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_024.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_025.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_026.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_027.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_028.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_029.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_030.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_031.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_032.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_033.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_034.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_035.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_036.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_037.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_038.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_039.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_040.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_041.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_042.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_043.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_044.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_045.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_046.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_047.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_048.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_049.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_050.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_051.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_052.duo doesn't typecheck.
      Doesn't typecheck
    Spec.TypeInferenceExamples[37:24]
      # PENDING: Could not typecheck file test/Counterexamples/CE_053.duo
Reason: Constraint Solver for type class methods not implemented yet.
    The counterexample test/Counterexamples/CE_054.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_055.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/CE_057.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056a.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056b.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056c.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056d.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056e.duo doesn't typecheck.
      Doesn't typecheck
    The counterexample test/Counterexamples/Subsumption\CE_056f.duo doesn't typecheck.
      Doesn't typecheck
Prettyprinted work again
  All the examples in the "examples/" folder can be parsed after prettyprinting.
    The example examples/VexingParse.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/TypeClassInstance.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/TypeClasses.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Tutorial.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Subsumption.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Sorting.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Shifts.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Primitives.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Prelude.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/ParserAlt.duo can be parsed after prettyprinting.
      Can be parsed again. FAILED [11]
    The example examples/Parser.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Ord.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/ICFP\ParsimoniousFilter.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/ICFP\Icfp22example.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/DeMorgan.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Compilertests.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example examples/Callcc.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Prim\Strings.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Prim\I64.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Prim\F64.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Void.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Unit.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Tensor.duo can be parsed after prettyprinting.
      Can be parsed again. FAILED [12]
    The example std/Data\Plus.duo can be parsed after prettyprinting.
      Can be parsed again. FAILED [13]
    The example std/Data\PeanoStructural.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\PeanoRefinement.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Peano.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\NegationP.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Maybe.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\List.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\FunCofunNeg.duo can be parsed after prettyprinting.
      Can be parsed again. FAILED [14]
    The example std/Data\Cofunction.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\BoolStructural.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\BoolRefinement.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\Bool.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Data\BinaryTree.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\With.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\VoidN.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\UnitN.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\Stream.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\Par.duo can be parsed after prettyprinting.
      Can be parsed again. FAILED [15]
    The example std/Codata\NegationN.duo can be parsed after prettyprinting.
      Can be parsed again.
    The example std/Codata\Function.duo can be parsed after prettyprinting.
      Can be parsed again.
  All the examples in the "examples/" folder can be parsed and typechecked after prettyprinting.
    The example examples/VexingParse.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/TypeClassInstance.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/TypeClasses.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Tutorial.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Subsumption.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Shifts.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Primitives.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Prelude.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Parser.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Ord.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Compilertests.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example examples/Callcc.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Prim\Strings.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Prim\I64.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Prim\F64.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Void.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Unit.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\PeanoStructural.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\PeanoRefinement.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Peano.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\NegationP.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Maybe.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\List.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Cofunction.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\BoolStructural.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\BoolRefinement.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\Bool.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Data\BinaryTree.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Codata\With.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Codata\VoidN.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Codata\UnitN.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Codata\NegationN.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
    The example std/Codata\Function.duo can be parsed and typechecked after prettyprinting.
      Can be parsed and typechecked again.
Focusing works
  Focusing an entire program still typechecks
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/VexingParse.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/VexingParse.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/TypeClassInstance.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/TypeClassInstance.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/TypeClasses.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/TypeClasses.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Tutorial.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Tutorial.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Subsumption.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Subsumption.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Shifts.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Shifts.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Primitives.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Primitives.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Prelude.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Prelude.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Parser.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Parser.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Ord.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Ord.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Compilertests.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Compilertests.duo succesfully
    CBV Focusing the program in  examples/ typechecks.
      Focused examples/Callcc.duo succesfully
    CBN Focusing the program in  examples/ typechecks.
      Focused examples/Callcc.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Prim\Strings.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Prim\Strings.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Prim\I64.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Prim\I64.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Prim\F64.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Prim\F64.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Void.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Void.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Unit.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Unit.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\PeanoStructural.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\PeanoStructural.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\PeanoRefinement.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\PeanoRefinement.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Peano.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Peano.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\NegationP.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\NegationP.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Maybe.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Maybe.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\List.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\List.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Cofunction.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Cofunction.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\BoolStructural.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\BoolStructural.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\BoolRefinement.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\BoolRefinement.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\Bool.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\Bool.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Data\BinaryTree.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Data\BinaryTree.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Codata\With.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Codata\With.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Codata\VoidN.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Codata\VoidN.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Codata\UnitN.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Codata\UnitN.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Codata\NegationN.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Codata\NegationN.duo succesfully
    CBV Focusing the program in  std/ typechecks.
      Focused std/Codata\Function.duo succesfully
    CBN Focusing the program in  std/ typechecks.
      Focused std/Codata\Function.duo succesfully

Failures:

  test\Spec\LocallyClosed.hs:48:57:
  1) All examples are locally closed, All examples are locally closed., Examples in examples/Sorting.duo are locally closed, Could not load examples.
       D:\StudiumsZeug\Bachelorarbeit\duo-lang\std\Data\Tensor.duo:10:15-10:15
       Parser error: unexpected "Ôèù leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/Sorting.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  2) All examples are locally closed, All examples are locally closed., Examples in examples/ParserAlt.duo are locally closed, Could not load examples.
       examples/ParserAlt.duo:18:39-18:39
       Parser error: unexpected '('
       expecting ')'

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/ParserAlt.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  3) All examples are locally closed, All examples are locally closed., Examples in examples/ICFP\ParsimoniousFilter.duo are locally closed, Could not load examples.
       D:\StudiumsZeug\Bachelorarbeit\duo-lang\std\Codata\Par.duo:11:15-11:15
       Parser error: unexpected "Ôàï leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/ICFP\\ParsimoniousFilter.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  4) All examples are locally closed, All examples are locally closed., Examples in examples/ICFP\Icfp22example.duo are locally closed, Could not load examples.
       D:\StudiumsZeug\Bachelorarbeit\duo-lang\std\Data\Plus.duo:11:15-11:15
       Parser error: unexpected "Ôèò leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/ICFP\\Icfp22example.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  5) All examples are locally closed, All examples are locally closed., Examples in examples/DeMorgan.duo are locally closed, Could not load examples.
       D:\StudiumsZeug\Bachelorarbeit\duo-lang\std\Data\Tensor.duo:10:15-10:15
       Parser error: unexpected "Ôèù leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in examples/DeMorgan.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  6) All examples are locally closed, All examples are locally closed., Examples in std/Data\Tensor.duo are locally closed, Could not load examples.
       std/Data\Tensor.duo:10:15-10:15
       Parser error: unexpected "Ôèù leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in std/Data\\Tensor.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  7) All examples are locally closed, All examples are locally closed., Examples in std/Data\Plus.duo are locally closed, Could not load examples.
       std/Data\Plus.duo:11:15-11:15
       Parser error: unexpected "Ôèò leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in std/Data\\Plus.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  8) All examples are locally closed, All examples are locally closed., Examples in std/Data\FunCofunNeg.duo are locally closed, Could not load examples.
       std/Data\FunCofunNeg.duo:10:24-10:24
       Parser error: unexpected ". "
       expecting "=>", ',', '_', or alphanumeric character

       std/Data\FunCofunNeg.duo:13:24-13:24
       Parser error: unexpected ". "
       expecting "=>", ',', '_', or alphanumeric character

       std/Data\FunCofunNeg.duo:19:28-19:28
       Parser error: unexpected "b."
       expecting "=>" or ','

       std/Data\FunCofunNeg.duo:28:31-28:31
       Parser error: unexpected "b."
       expecting "=>" or ','

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in std/Data\\FunCofunNeg.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  9) All examples are locally closed, All examples are locally closed., Examples in std/Codata\Stream.duo are locally closed, Could not load examples.
       D:\StudiumsZeug\Bachelorarbeit\duo-lang\std\Data\Tensor.duo:10:15-10:15
       Parser error: unexpected "Ôèù leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in std/Codata\\Stream.duo are locally closed/Could not load examples./"

  test\Spec\LocallyClosed.hs:48:57:
  10) All examples are locally closed, All examples are locally closed., Examples in std/Codata\Par.duo are locally closed, Could not load examples.
       std/Codata\Par.duo:11:15-11:15
       Parser error: unexpected "Ôàï leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/All examples are locally closed/All examples are locally closed./Examples in std/Codata\\Par.duo are locally closed/Could not load examples./"

  test\Spec\Prettyprinter.hs:40:25:
  11) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example examples/ParserAlt.duo can be parsed after prettyprinting., Can be parsed again.
       examples/ParserAlt.duo:18:39-18:39
       Parser error: unexpected '('
       expecting ')'

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example examples/ParserAlt.duo can be parsed after prettyprinting./Can be parsed again./"

  test\Spec\Prettyprinter.hs:40:25:
  12) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example std/Data\Tensor.duo can be parsed after prettyprinting., Can be parsed again.
       std/Data\Tensor.duo:10:15-10:15
       Parser error: unexpected "Ôèù leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example std/Data\\Tensor.duo can be parsed after prettyprinting./Can be parsed again./"

  test\Spec\Prettyprinter.hs:40:25:
  13) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example std/Data\Plus.duo can be parsed after prettyprinting., Can be parsed again.
       std/Data\Plus.duo:11:15-11:15
       Parser error: unexpected "Ôèò leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example std/Data\\Plus.duo can be parsed after prettyprinting./Can be parsed again./"

  test\Spec\Prettyprinter.hs:40:25:
  14) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example std/Data\FunCofunNeg.duo can be parsed after prettyprinting., Can be parsed again.
       std/Data\FunCofunNeg.duo:10:24-10:24
       Parser error: unexpected ". "
       expecting "=>", ',', '_', or alphanumeric character

       std/Data\FunCofunNeg.duo:13:24-13:24
       Parser error: unexpected ". "
       expecting "=>", ',', '_', or alphanumeric character

       std/Data\FunCofunNeg.duo:19:28-19:28
       Parser error: unexpected "b."
       expecting "=>" or ','

       std/Data\FunCofunNeg.duo:28:31-28:31
       Parser error: unexpected "b."
       expecting "=>" or ','

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example std/Data\\FunCofunNeg.duo can be parsed after prettyprinting./Can be parsed again./"

  test\Spec\Prettyprinter.hs:40:25:
  15) Prettyprinted work again, All the examples in the "examples/" folder can be parsed after prettyprinting., The example std/Codata\Par.duo can be parsed after prettyprinting., Can be parsed again.
       std/Codata\Par.duo:11:15-11:15
       Parser error: unexpected "Ôàï leftas"
       expecting "->", "leftassoc", "rightassoc", '`', punctuation, or symbol

  To rerun use: --match "/Prettyprinted work again/All the examples in the \"examples/\" folder can be parsed after prettyprinting./The example std/Codata\\Par.duo can be parsed after prettyprinting./Can be parsed again./"

Randomized with seed<PHONE_NUMBER>

Finished in 0.2214 seconds
467 examples, 15 failures, 2 pending

duo-lang> Test suite duo-lang-test failed
Completed 2 action(s).
Test suite failure for package duo-lang-<IP_ADDRESS>
    duo-lang-test:  exited with: ExitFailure 1
Logs printed to console

https://serokell.io/blog/haskell-with-utf8
This is the underlying issue. We are not explicitly setting the utf-8 locale when reading and writing to disk.


There are inconsistent titles of the SAS URL field on the 'Shared Access Signature' and 'Enter Connection Info' dialog

Storage Explorer Version: 1.19.0-dev
Build Number: 20210401.2
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to Reproduce

Select one blob container then right click it.
Click 'Get Shared Access Signature...' -> Click the 'Create' button on the 'Shared Access Signature' dialog.
Observe the title of the SAS URL field on the dialog.
Open the connect dialog -> Select 'Blob container -> Shared access signature URL (SAS)' -> Click the 'Next' button.
Observe the title of the SAS URL field on the 'Enter Connection Info' dialog.
Check whether the two titles are consistent.

Expected Experience
Show a consistent 'SAS URL'.
Actual Experience
Show inconsistent titles.

Show 'URI' on the 'Shared Access Signature' dialog.
Show 'SAS URL' on the 'Enter Connection Info' dialog.

Additional Context
This issue also reproduces for one file share/table/queue.

We will change to URL.

@JasonYeMSFT Show 'URI' in the tooltip of the 'Copy' button

I have updated that one and the strings in the connect dialog to say "URL" instead of "URI".


Remove colNames from RRDD

The unit tests pass, but I messed up the commit message a bit -- You might want to try and fix that if possible !

Hahahaha, coolNames is totally appropriate!

This was largely replicated in https://github.com/cafreeman/SparkR-pkg/commit/0387db26357fc4b4774589b704bd4cec72f20cce, so I'm gonna go ahead and close this.


Connection Error with PhoenixHTML 3.3.0

When using phoenix_html version 3.3.0, the app fails to render the connection it exist on:
https://github.com/liveviewnative/liveview-client-swiftui/blob/main/Sources/LiveViewNative/Coordinators/LiveViewCoordinator.swift#L235
The culprit being that new version of PhoenixHTML renders  as <div data-phx-main ...> instead of expected <div data-phx-main="true" ...>, which is what PhoenixHTML 3.2.0 renders.
Not sure if there is a reason for the exact match or if this can be loosen to just matching the attribute existence?

I think HTML spec treats the existence of the attribute as truthy so they'd be the same value but yes we are doing an exact match and should loosen that.

@carson-katri I think changing that LOC cited above to:
doc.select("div[data-phx-main]")

should be OK


Searching Trees Algorithm Codes

Description
Searching Trees Algorithm Codes
Fixes #(58)
issue_no must refer to the issue related to this PR, visit here
Type of change
Choosing one or more options from the following as per the nature of your Pull request.
NOTE: Check boxes using [x]

[ ] Bug fix (non-breaking change which fixes an issue)
[ x] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Checklist:

[ x] I have named my files and folder, according to this project's guidelines.
[x ] My code follows the style guidelines of this project.
[ x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[ x] I have commented on my code, particularly in hard-to-understand areas.
[ x] I have created a helpful and easy to understand README.md, with problem description and my name.
[ x] I have included a requirements.txt file (if external libraries are required.)
[ x] My changes do not produce any warnings.
[x ] I have starred this repository.
[x ] I have added a working sample/screenshot of the script.

[x] I have checked for trailing spaces in file names and none have them.

Add your name along with github profile link to readme as re issue PR

In contributers.md, right?

I have already added a Readme.md in the folder that has my name and github profile link.

Contributors.md must not be altered whereas this file must include your name and github link.

I have added my name and profile link.


enable-fips should just warn/exit

QuicTLS is not providing a FIPS-enabled module that has been verified. We should not build the FIPS module.
It might be nice to run the FIPS tests against the openSSL module however.

Once you replace the modules you would have one that is FIPS.
Agreed on the desirability of FIPS tests with OpenSSL module

Once you replace the modules you would have one that is FIPS.

Do you mean copy over the files from OpenSSL after they do FIPS config?  Cute hack.

Yeah, that's already what we do with 3.1 and 3.0

With #96 'build the fips container' is gone. The fips-stuff tag points to the commit that did it, in case we ever need to bring it back.  Closing.


Unable to specify custom zksolc compiler

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
forge 0.0.2 (f505a536 2024-06-26T15:14:31.411368000Z)
Operating System
macOS (Apple Silicon)
Describe the bug
When trying to compile using custom zksolc compiler via using the flag forge build --zksync --zk-solc-path ./path-to-zksolc-compiler flag getting the following error Broken pipe (os error 32).
Also when trying to specify the zksolc compiler in foundry.toml like zksolc='./path-to-compiler', for example when specifying the v1.5.1 compiler executable path and running forge build --zksync v1.4.1 is being downloaded automatically in ~./zksync/ and is being used instead of the zksolc compiler specified.

Hi!
The zksync.solc configuration option (--zk-solc-path) is meant to specify a custom version of solc that zksolc will use, therefore please do not use it to specify a zksolc compiler, which should instead (as you pointed out also) be specified in zksync.zksolc.
We are investigating the issue in regards to v1.5.1 being ignored.

Using [profile.default.zksync] in foundry.toml it worked fine for me. Thank you.


[network] filter ip's from DNS resolver according to protocol

NetworkAddress allows us to advertise a dns name but restrict a dialer
to only connect over IPv4 or IPv6. This diff actually enforces this
distinction in our tcp dialing logic, so we will never accidentally
connect over IPv4 if the address only allows IPv6 (and vice versa).
For example, dialing "/dns4/example.com/tcp/8080" will now only ever
connect over IPv4 and likewise for "/dns6/example.com/tcp/8080".
Of course, if the address advertiser doesn't care (or supports both
protocols), we continue to support "/dns/example.com/tcp/8080", which
does no filtering and will use whatever resolved SocketAddr that works
first.
Closes: #1200

@bors-libra r=gregnazario

:pushpin: Commit e2ad876 has been approved by gregnazario

:hourglass: Testing commit e2ad87633a2efe0b2aa47e56c5f8f1bf972fad6b with merge 5d88f2daef05d014110da9cd3fd00f4d327f5ac5...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit e2ad87633a2efe0b2aa47e56c5f8f1bf972fad6b with merge 798382ce5dcdbafb3e09013757330ea0cc209fef...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: gregnazario
Pushing 798382ce5dcdbafb3e09013757330ea0cc209fef to master...


Fix typo in test documentation.

Problem
Typo in testing documentation.
Solution
Fix typo.

Codecov Report

Merging #391 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #391   +/-   ##
========================================
  Coverage    94.56%   94.56%
========================================
  Files          218      218
  Lines         3204     3204
  Branches       255      255
========================================
  Hits          3030     3030
  Misses         174      174

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 ec5da43...5e85a2b. Read the comment docs.

@edwelker  this has been merged in 947e1da5eaf37f916f42985cab4602fc9910ff53


Problems when training

Hi,
thanks for sharing the code!
When I try to train using
python3 ./main/dist_train_sat.py --config 'experiments/sat/train/sat_res50_davis17.yaml
I get an attribute error at
model = model_builder.build(task, task_cfg.model)
in dist_train.py
When I replace that line by
model = model_builder.build(task, task_cfg['segmenter'])
then I get
AttributeError: 'NoneType' object has no attribute 'eval'
at
self.tracker.eval()
in distributed_sat_trainer.py  (the tracker is None).

@pvoigtlaender  It seems that model = model_builder.build(task, taks_cfg.model) is in dist_train.py while we train sat with dist_train_sat.py?

Gotcha!
Thx, it's working now :)


Do unbuffered output from launch scripts

Docker logs won't show the whole thing due to buffering... So yeah, do unbuffered output!

So this isn't necessary since I switched everything to use the logging module in #26 and it does flush() by default.


Implemented Task APIs

[x] cloases #14
[ ] cloases #15
[ ] cloases #16
[ ] cloases #17
[ ] cloases #18
[ ] cloases #19
[ ] cloases #20

Codecov Report

Merging #43 (1e7d934) into main (bc7a649) will increase coverage by 3.79%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
+ Coverage   73.22%   77.02%   +3.79%
==========================================
  Files           5        6       +1
  Lines         254      296      +42
==========================================
+ Hits          186      228      +42
  Misses         58       58
  Partials       10       10

Impacted Files
Coverage Δ

todoist/projects.go
94.82% <ø> (ø)

todoist/client.go
65.95% <100.00%> (ø)

todoist/sections.go
96.36% <100.00%> (-0.07%)
:arrow_down:

todoist/tasks.go
100.00% <100.00%> (ø)

todoist/utils.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Revert "Adding Batch package"

Reverts GoogleCloudPlatform/google-cloud-php#414

@tmatsuo do you know when the Batch stuff is getting merged back in?


sun.* source code not included in src.zip

From @don-vip on October 6, 2017 20:43
I have downloaded this binary:
https://github.com/AdoptOpenJDK/openjdk8-releases/releases/download/jdk8u144-b01/OpenJDK8_x64_Win_jdk8u144-b01.exe
Once installed, it appears sun.* source code is not included in src.zip.
As at least the class I'm interested in (src/share/classes/sun/util/locale/provider/NumberFormatProviderImpl.java) is licensed under GPLv2, coud you please include in src.zip all the source code we can find in OpenJDK repositories?
Copied from original issue: AdoptOpenJDK/openjdk8-releases#9

From @gdams on October 7, 2017 12:0
@neomatrix369 any ideas about this?

From @neomatrix369 on October 7, 2017 21:10
@gdams No idea why this would be the case, we are archiving the image folder as it is produced by the OpenJDK build process, see src.zip in https://ci.adoptopenjdk.net/job/openjdk8_build_x86-64_windows/ws/openjdk/build/windows-x86_64-normal-server-release/images/jdk8u162-b01/.
We do not amend the image, at all (apart from removing some demo folders to reduce the footprint of the original archive file).

From @neomatrix369 on October 7, 2017 21:13
@don-vip Can you please point us to OpenJDK Windows builds (produced anywhere else) in which the src.zip does contain the file you are looking for?
I'll also ask the OpenJDK team about this after doing some looking around.

From @don-vip on October 7, 2017 21:38
? There is not. I'm asking to include the missing files. If they were already included, I wouldn't have created the ticket :)

@neomatrix369 Worth asking upstream OpenJDK folks why this isn't included (for jdk8u).   I can't see any reason not to include it if it's GPLv2 with Classpath and not a closed Sun/Oracle class.

From @neomatrix369 on October 7, 2017 21:45
@don-vip Thanks for clarifying.
It would mean changing the build script, have a look at http://jdk.java.net/java-se-ri/8 and then the http://download.java.net/openjdk/jdk8u40/ri/openjdk-8u40-src-b25-10_feb_2015.zip, which does not contain the file you are talking about either.
@gdams @karianna what do you think about the request? Our build script will fork away from the standard OpenJDK one if we implement this, is this desirable for the medium/long run?

@tellison Good point, we could provide the link to the tag in Github in the download.

From @tellison on October 9, 2017 9:34
FYI it has been true 'forever' that src.zip does not contain all the library source code.  That zip file is produced to assist development tools display relevant source code.  IMHO it should contain less source than it already does.
Now that we are all connected, better still we should simply include coordinates to the git repo sources that produced the build so that dev tools can reach on-line the entire code from which the binaries are produced if they so choose.

So this was actually a 'bug' with OpenJDK itself.  Severin has submitted a RFR to add these sources for 8.  We may see this come in for 8u202

Thanks a lot! Link for reference.

I'll close this as our nightly builds will pick this up in due course.

How can I get the fix?

I downloaded JDK8u202 b03 from Oracle and src.zip is still 20Mb. I don't understand why, as JDK-8073327 is supposedly fixed in 8u202 b01
AdoptOpenJDK 8u nightly refers to 8u192. I thought "nightly" meant master on jdk8u mercurial repository?


Enhancement: Provide a way to notify resource if defined

It should be possible for a resource to notify a resource if and only the resource to be notified exists.  (Put differently, it should be possible to make a run not fail at runtime with an uncaught exception if the notified resource has not been defined at compile time.)
An example would be a cleanup recipe that removes a conf.d file, and notifies the daemon that might use the conf.d file to reload.  If the daemon is no longer being managed by Chef, it's not fatal that the daemon's service is no longer declared.

The easiest way to handle this would be to use find_resource to declare the target if it hasn't been already.

A DSL enhancement would be preferable, e.g.:
resource 'foo' do
   notifies :action, 'some[resource]', :if_exists, :immediately
end

DSL changes are the biggest hammer we have, and generally only used for something either very common or that doesn't increase the API surface. Given that this hasn't come up enough for someone to ask for it, I don't think that's a good fix.
recipe = self
ruby_block 'whatever' do
  block do
    recipe.find_resource(:service, 'name') do
      action :nothing
      provider :noop
    end
end

That should be all you need in your recipe :)

Let's ask the community; this is not a decision you get to make by yourself.

I'm not finding the example compelling either:
service "thing" do
  action :nothing
end

file "/etc/thing.d/thing.conf" do
  action :remove
  notifies :stop, 'service[thing]', :before
end

either wrap it in a resource to avoid 3694 errors, or rename the service resource.

@lamont-granquist What if the service is defined elsewhere?   Doesn't your example redefine its behavior as a side effect?

@mfischer-zd The example I gave uses find_resource to only define it if it isn't already defined.

it doesn't really hurt to define the service twice.  even with resource cloning and 3694 errors that simple of a resource clone is unlikely to cause issues other than spitting out the WARN that everyone ignores.  and its easy to work around:
service "thing-being-removed" do
  service_name "thing"
  action :nothing
end

file "/etc/thing.d/thing.conf" do
  action :remove
  notifies :stop, 'service[thing-being-removed]', :before
end

or whatever naming tactic you like to avoid the 3694 collision.
plus wrap that in a custom resource or use_inline_resources-style LWRP and the sub-resource collection makes the name unique (resources only have to be uniquely named within their own resource collection to avoid 3694 issues).

I agree that this is a viable workaround, @lamont-granquist, but I still fail to see how this is a better user experience than adding a simple :if_exists argument.
Let's solicit user and customer feedback before making a decision.  Thanks.

@mfischer-zd let me offer you some other ways to raise the visibility of this request so that it can have broader discussion within the community and the product team within Chef.

Write it up as a public RFC.
Share the request on the Chef feedback site - this is reviewed by Chef Software, Inc.'s product management team.
Mention this ticket (and/or your RFC, and/or you post on the feedback site) and solicit input on the discussion forum.

Hi,
as @nathenharvey suggests, there are better venues for providing feature requests to Chef. It's extremely unlikely, given our backlog, that this will be prioritised through this channel, and so I'm going to close out this ticket.
I strongly encourage you to raise this via feedback.chef.io and interact with our product team there.
Thanks,
-Thom


test: remove redundant test suite

Overview
This file just starts running the test suit and shuts it down therefore we can remove it.
Checklist

[ ] Required CI checks are passing

Strange but I think the CLITestSuite is actually used by x/blobstream/client/query_test.go

you're right! me and

yeah this was my bad, I just saw the file that wasn't doing anything and assumed it wasn't needed


Fixed the example how to use PEP 257 docstrings to be compatible with PEP 257.

The example showed a single line docstring in three distinct lines instead of
one. This commit changed that, to be an actual multi-line docstring.

To my knowledge, we don't actually use that style. Unless there is consensus to change it, I guess we need a note about the discrepancy with the PEP.

PEP 257 states that “The summary line may be on the same line as the opening quotes or on the next line.”, and both options produce equivalent output (as per https://www.python.org/dev/peps/pep-0257/#handling-docstring-indentation). Thus, I believe there isn't a discrepancy.

Sounds good.

All right, fair enough. I obviously missed that part of the PEP.
Just for reference: pep257/pydocstyle will per default issue a warning when not fitting such a docstring in a single line:
D200 	One-line docstring should fit on one line with quotes