Help with categories please

Third question )
I have a directory structure:

Home
Main category
-- category in the main 1
-- category in the main 2
Additional category
-- category in additional 1
-- category in additional 2
Category additional 2
-- category in additional 2-1
-- category in additional 2-2
-Link somewhere

How can I display the number of pages in a category in the site code?
i.e. there is a code:

href = # span class = badge > 21 span item in category a

And how can I put those pages that are in the category on the page in the main category?
And how else to bring random pages from some category to the main page of the site.
And as I understand it, the main page of the site I have copied as a code copied from the layout of the site. I would like these blocks to be located in the folder (content/block_slider.twig.html). So that I can change it from the admin panel of the site.
And can I add fields to fill out the product page? So that I can also add and edit from the admin panel, the product card itself looks like this
product.txt
I need to make the tabs receive information that I would fill out on the site. There will be four 6 complete blocks: Slider with images, product information for the manager, product description, and tabs (Characteristics, model (loading of two images will be here), and documentation)

I found a topic in the documentation on how to make blocks in the form of modules, but I can’t connect them.
That is, in the Home page folder, I created the _slider folder, in it I created a slider.md document. I entered the information in it in the form

name: slider
published: true
apparently: true
img slide2
div class carousel-caption
h4 about slide
p about slide more
br
a href class Button
img slide1
div class carousel-caption
h4 about slide
p about slide more
br
a href class Button
img slide3
div class carousel-caption
h4 about slide
p about slide more
br
a href class Button
In the folder with the template, I created the modules folder, in it I created the slider.md file. It contains such code
div id myCarousel class caourusel
ol
li data-target data-slide-to-0 class active
li data-target data-slide-to-1
li data-target data-slide-to-2
ol
div class carousel
div class item active
{{ content }}
div
div

And now, how can I get all this out so that it works on the main page of the site? that is, I have to get in the file (path to the file) / standard.md to get a line that would take the code from the slider module and enter it in its place. Found such a code
`
{% set image = page.media.images|first %}
{% if image %}
{{ image.cropResize(400,400).html('','','align-'~page.header.image_align) }}
{% endif %}
{{ content }}
`
but it does not work for me. What to do with it ?

I figured out the slider as well as the rest of the modules.
But there were open questions:

How to make random news fall into the slider module
How to display the number of pages in a category on a site
How to add fields to the product that I add through the admin panel
How to set up a feedback forum on the main page of the site? Since I'm reading the documentation for the plugin I did not understand what. Created a folder in the home folder,   feedback folder, placed the feedback.md in it. I inserted code into it

---
title: Form

form:
  action: '/form/modular'
  inline_errors: true
  fields:
    person.name:
      type: text
      label: name
      validate:
        required: true
    person.email:
      type: email
      label: email
      validate:
        required: true
    person.phone:
      type: text
      label: phone
      validate:
        required: true
    person.message:
      type: text
      label: message
      validate:
        required: true
  buttons:
    submit:
      type: submit
      value: Submit
  process:
    message: "Thank you from your submission {{ form.value('person.name') }}!"
    reset: true
    display: '/form/modular'

---

      <input type="text" lable="{{ person.name }}" class="form-control" placeholder="Ваше Имя">

      <input type="email" lable="{{ person.email }}" class="form-control" placeholder="Номер телефона">

      <input type="text" lable="{{ person.phone }}" class="form-control" placeholder="Email">

      <input type="text" lable="{{ person.message }}" class="form-control" data-provide="typeahead" placeholder="Ваше сообщение">

      <button class="btn btn-block btn-success" value="Выгнать" type="{{ submit }}">send</button>

But something doesn’t work (


[Bugfix] Fix export routing for quiz exercises

Motivation and Context

Fixes #3433
Fixes #3317

Problem is that export button does not work for quiz exercises. Export navigates to Create New Quiz Page. Routing definitions were correct, but I changed the order of the routes in the quizManagementRoute. (just move up the 'new' and 'export' routes) According to official documentation, the router uses a first-match wins strategy when matching routes, so more specific routes should be placed above less specific routes. After reordering, routing works again.

Also, when the user open Export Quiz Exercise page, the last segment was wrong in the breadcrumb. Export string is set with wrong translation. I also fixed this in the NavbarComponent

In addition, I re-organized the authorizations in quiz management routes.

Description

Steps for Testing

Following steps cover only export routing. Please check that all routes  related with quiz exercises are working properly in course and exam. e.g Preview, Solutions, Create, Edit, Re-Evaluate, Submissions, Delete.

Log in to Artemis as INSTRUCTOR
Navigate to Course Management
Go to Exercises for the course, to see Export Quiz Exercises button, you need to have at least one quiz exercise.
click that, it should open the correct page, not the Create New Quiz Exercise page.
look at the breadcrumbs in that page, it should be correct (see screenshot)

Test Coverage

nothings changes
Screenshots

Tested on TS2 and everything works fine. 👍🏼
Something I would suggest is to disable the export button in case there are no quizzes selected to export. See image below:

hmm, could be part of ui improvement, but I think that it is not relevant with the problem we have now. I just took noted this.


Problem Restricted training

Hello, how are you? I have a problem, I was able to prepare my data set but if I try with a high batch number, it falls due to lack of memory. Currently I have managed to train only one batch taking a time of 10 hours, which seems very strange to me since I have a RTX2080 graphics card. Here is an image that shows the consumption of the card with a batch. If you can help me or give me some advice it would be ideal.
regards

@dpramirez Can not figure out what's going wrong here. Everything seems normal here ==!

@MaybeShewill-CV  what I don't find normal is the amount of gpu memory that is occupying only training with a batch.

@dpramirez The gpu memory are allocated during graph construction process. So it's normal that all of your cpu memo are allocated during training process:)

then there is no problem that only one batch occupies?, I mean because you can generate local kittens etc.

@dpramirez I do not get your meaning of "one batch occupies" ==!

@MaybeShewill-CV I mean, using a batch of 1 doesn't produce local minima in the results.

@dpramirez You mean batch size equals 1?

@MaybeShewill-CV  yes

@dpramirez Batch size larger than 1 will cause out of gpu memory problem? If so you'd better raise an issue in TensorFlow repo. I have not met such a problem before:)


Update tutorials with signed CLA email

#648

Great success–tests passed! Thanks for the changes. All is set on your end for now, we'll get to the review shortly.

Thank you for your help!!

Justin,
This tutorial is in support of a live training for the US forest service on April 25th. Could you please check this tutorial at your earliest convenience so it can be posted before the training?
Thanks

Hung, the tutorial looks good. I corrected some formatting as I went through it (see the 3 commits above). I have three recommendations for improvement.

Show an example of the three "layers" surface, subsurface, and precip in the map. Just select a given observation (from same time period) - it doesn't need to be meaningful, except to show users the variance in the variables across space.

Section 4 and 5 perform the exact same thing. My recommendation is to combine them.

var ssSusMa =  nasa_usda_smap
  .filterDate(startDate, endDate)
  .sort('system:time_start', true)  // sort a collection in ascending order
  .select(['ssma', 'susma'])  // surface and subsurface soil moisture bands

// Compute monthly anomalies surface soil moisture.
var monthlySsSusMa =  ee.ImageCollection.fromImages(
  years.map(function(y) {
    return months.map(function(m) {
      var filtered = ssSusMa.filter(ee.Filter.calendarRange(y, y, 'year'))
                         .filter(ee.Filter.calendarRange(m, m, 'month'))
                         .mean();
      return filtered.set(
        'system:time_start', ee.Date.fromYMD(y, m, 1).millis());
    });
  }).flatten()
);

This might mean that you don't need to combine surface and subsurface collections later on - it should still chart okay. (this is untested).

Don't clip all images (see best practices). The charting function will do the clipping required for the chart. If you show layers on the map, you can clip the single image e.g. Map.addLayer(thisParticularImg.clip(region)). I removed clip in the above suggestion for combining sections 4 and 5, it can be removed from section 6 and also the aoiClip function can be removed.

You can make edits right here on GitHub - go to this URL - click on the three dot options on right of page and select "Edit" - make your changes and then commit them (very bottom of the edit page).
Let me know if you have any questions or would like to discuss anything.

Hung, the tutorial looks good. I corrected some formatting as I went through it (see the 3 commits above). I have three recommendations for improvement.

Show an example of the three "layers" surface, subsurface, and precip in the map. Just select a given observation (from same time period) - it doesn't need to be meaningful, except to show users the variance in the variables across space.
Section 4 and 5 perform the exact same thing. My recommendation is to combine them.

var ssSusMa =  nasa_usda_smap
  .filterDate(startDate, endDate)
  .sort('system:time_start', true)  // sort a collection in ascending order
  .select(['ssma', 'susma'])  // surface and subsurface soil moisture bands

// Compute monthly anomalies surface soil moisture.
var monthlySsSusMa =  ee.ImageCollection.fromImages(
  years.map(function(y) {
    return months.map(function(m) {
      var filtered = ssSusMa.filter(ee.Filter.calendarRange(y, y, 'year'))
                         .filter(ee.Filter.calendarRange(m, m, 'month'))
                         .mean();
      return filtered.set(
        'system:time_start', ee.Date.fromYMD(y, m, 1).millis());
    });
  }).flatten()
);

This might mean that you don't need to combine surface and subsurface collections later on - it should still chart okay. (this is untested).

Don't clip all images (see best practices). The charting function will do the clipping required for the chart. If you show layers on the map, you can clip the single image e.g. Map.addLayer(thisParticularImg.clip(region)). I removed clip in the above suggestion for combining sections 4 and 5, it can be removed from section 6 and also the aoiClip function can be removed.

You can make edits right here on GitHub - go to this URL - click on the three dot options on right of page and select "Edit" - make your changes and then commit them (very bottom of the edit page).
Let me know if you have any questions or would like to discuss anything.

I really appreciate your recommendation; it makes the script more cohesive!
I wonder if I can check my scripts running on GitHub instead of copying them to Code Engine, running them, and copying them back.
Hung

Justin, it looks good for me! Thanks so much for your help!

Congratulations, the tutorial has been merged. Thanks for supporting the Earth Engine developer community with this contribution!
Once the tutorial is published to the Earth Engine Developer Guide, I'll post the link here.

The tutorial is live!
https://developers.google.com/earth-engine/tutorials/community/anomalies-analysis-smo-and-pre
If you'd like to make changes to it in the future, you can sync your fork of the https://github.com/google/earthengine-community repository, edit the index.md file and submit a pull request.


haskellPackages: update stackage and hackage

This Merge
This PR is the regular merge of the haskell-updates branch into master.
This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.
haskellPackages Workflow Summary
Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.
The short version is this:

We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
The community fixes builds of Haskell packages on that branch.
We aim at at least one merge of haskell-updates into master every two weeks.
We only do the merge if the mergeable job is succeeding on hydra.
If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

This is the follow-up to #142641. Come to #haskell:nixos.org if you have any questions.

Oh, yeah that slipped in. It requires a patch from hlint, but one which
doesn't download from github nicely.
This is better than the previous state in that it at least evaluates...
On Sun, 7 Nov 2021, 12:55 am sterni, @.***> wrote:

@.**** commented on this pull request.
In pkgs/development/haskell-modules/configuration-ghc-9.2.x.nix
https://github.com/NixOS/nixpkgs/pull/144707#discussion_r744145753:

@@ -218,9 +222,7 @@ self: super: {

hlint 3.3 needs a ghc-lib-parser newer than the one from stackage
hlint = super.hlint_3_3_4.overrideScope (self: super: {

ghc-lib-parser = overrideCabal self.ghc-lib-parser_9_0_1_20210324 {

 doHaddock = false;

};
ghc-lib-parser-ex = self.ghc-lib-parser-ex_9_0_0_4;

ghc-lib-parser = self.ghc-lib-parser_9_2_1_20211101;
ghc-lib-parser-ex = self.ghc-lib-parser-ex_9_2_0_1;

From my testing this doesn't compile this way, have you actually tested
this change?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/144707#pullrequestreview-799459906,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXHY6GOJJJR5WL4LN53UKVMYNANCNFSM5HNEWCXA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Here's a recent build repo:
haskell-updates build report from hydra
evaluation 1719541 of nixpkgs commit 5102894 as of 2021-11-07 00:38 UTC
:red_circle: Branch not mergeable

No maintained job found.
mergeable jobset failed.

Build summary

Platform
Failed :x:
DependencyFailed :heavy_exclamation_mark:
TimedOut :hourglass::no_entry_sign:
Success :heavy_check_mark:

aarch64-linux :iphone:
39
35
5
7043

x86_64-darwin :apple:
74
67
9
6923

x86_64-linux :penguin:
20
24
1
7118

Maintained packages with failed dependency

[ ] cabal-install @peti

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] cabal2nix @peti

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] cachix @domenkozar

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] git-annex @peti

[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] toplevel
[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages

[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] hci @roberth
[ ] hercules-ci-agent @roberth

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.hercules-ci-cli @roberth
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.hercules-ci-cnix-expr @roberth
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.hercules-ci-cnix-store @roberth
[ ] hsdns @peti

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] language-nix @peti

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:penguin::heavy_exclamation_mark:] mergeable @cdepillabout @expipiplus1 @maralorn @sternenseemann
[ ] nix-paths @peti

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] nvfetcher @berberman

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] titlecase @peti

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] update-nix-fetchgit @expipiplus1 @sorki

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

Unmaintained packages with build failure
94 job(s)

[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sdp  :arrow_heading_up: 9 | 9
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.lua  :arrow_heading_up: 8 | 15
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.junit-xml  :arrow_heading_up: 7 | 9
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.thyme  :arrow_heading_up: 6 | 15
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.libBF  :arrow_heading_up: 4 | 20
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.exinst  :arrow_heading_up: 4 | 6
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.JSONb  :arrow_heading_up: 3 | 4
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.ptr-poker  :arrow_heading_up: 3 | 4
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.OrderedBits  :arrow_heading_up: 1 | 36
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.type-natural  :arrow_heading_up: 1 | 4
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.long-double  :arrow_heading_up: 1 | 2
[ ] [:iphone::x:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.easytensor  :arrow_heading_up: 1 | 1
[ ] futhark  :arrow_heading_up: 1 | 1

[:iphone::x:] [:apple::x:] [:penguin::x:] toplevel
[:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages

[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gi-gdkx11  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.jordan  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.keep-alive  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.lambdacube-core  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.loc  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.nlopt-haskell  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.opencv  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sequence-formats  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.unicode-properties  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.webapi  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.accelerate-llvm  :arrow_heading_up: 0 | 8
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.freetype2  :arrow_heading_up: 0 | 7
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.pipes-zlib  :arrow_heading_up: 0 | 6
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hmidi  :arrow_heading_up: 0 | 4
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.zip  :arrow_heading_up: 0 | 4
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.cdar-mBound  :arrow_heading_up: 0 | 2
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.ghc-bignum  :arrow_heading_up: 0 | 2
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.ide-backend-common  :arrow_heading_up: 0 | 2
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.posix-socket  :arrow_heading_up: 0 | 2
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.quic  :arrow_heading_up: 0 | 2
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.eventlog2html  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hamid  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hmatrix-morpheus  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.huckleberry  :arrow_heading_up: 0 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.lambdacube-engine  :arrow_heading_up: 0 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.picosat  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.select  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sysinfo  :arrow_heading_up: 0 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.text-trie  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.FractalArt
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.HsASA
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.LambdaDesigner
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.airship
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.astro
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.cgroup-rts-threads
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.chiphunk
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.compact-sequences
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.discount
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.diskhash
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.epub-tools
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.float128
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gerrit
[ ] [:iphone::x:] [:penguin::heavy_check_mark:] haskellPackages.gnome-keyring
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.godot-megaparsec
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gtk-traymanager
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hid
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.higher-leveldb
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.highlight
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hinotify-conduit
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hmatrix-backprop
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hq
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hs
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hsshellscript
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hssourceinfo
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.ipcvar
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.linux-framebuffer
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.mediawiki2latex
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.mercury-api
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.mortred
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.nano-cryptr
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.persistent-pagination
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.ping-wrapper
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.poker
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.posix-timer
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.postgresql-migration
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.procex
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.pthread
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sandwich-webdriver
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sfml-audio
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.shared-memory
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.tailfile-hinotify
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.text-display
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.wiringPi
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.x86-64bit
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.xmonad-utils
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.yaml-config
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.yoga
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.zot
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.zxcvbn-c

Unmaintained packages with failed dependency
68 job(s)

[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.gi-javascriptcore  :arrow_heading_up: 7 | 18
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.pretty-diff  :arrow_heading_up: 6 | 12
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.gi-webkit2  :arrow_heading_up: 5 | 14
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hslua-core  :arrow_heading_up: 5 | 12
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-prelude  :arrow_heading_up: 5 | 7
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-env-parser  :arrow_heading_up: 4 | 6
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hslua-marshalling  :arrow_heading_up: 3 | 10
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-observability  :arrow_heading_up: 3 | 5
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.jsonifier  :arrow_heading_up: 2 | 2
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp-io  :arrow_heading_up: 2 | 2
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hslua-objectorientation  :arrow_heading_up: 1 | 7
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.JSON-Combinator  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hbro  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-redis  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.opentelemetry-extra  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.orgmode-parse  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp-hashable  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.PrimitiveArray  :arrow_heading_up: 0 | 35
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hslua-packaging  :arrow_heading_up: 0 | 6
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.sized  :arrow_heading_up: 0 | 2
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hslua-classes  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.keenser  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.JSON-Combinator-Examples
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.antiope-es
[ ] cabal2nix-unstable

[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc901
[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskell.packages.ghc921
[:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.easytensor-vulkan
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.exinst-aeson
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.exinst-bytes
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.exinst-cereal
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.exinst-serialise
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.fastparser
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.gi-webkit2webextension
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hbro-contrib
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hmatrix-nlopt
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.ide-backend-server
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.jordan-openapi
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.jspath
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.lambdacube-edsl
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.lambdacube-examples
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.lpeg
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.lua-arbitrary
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-http
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.nri-test-encoding
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.opencv-extra
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.opentelemetry-lightstep
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.orgstat
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.postgresql-replicant
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.rounded
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.scan-metadata
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp-binary
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp-deepseq
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp-quickcheck
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp4bytestring
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp4text
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp4unordered
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sdp4vector
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.sequenceTools
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.shake-futhark
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.tasty-hslua
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.tasty-test-reporter
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.uber
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.unicode-names
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.xbattbar

Top 50 broken packages, sorted by number of reverse dependencies
50 job(s)
haskell98 :arrow_heading_up: 153
enumerator :arrow_heading_up: 56
derive :arrow_heading_up: 48
contiguous :arrow_heading_up: 46
MonadCatchIO-transformers :arrow_heading_up: 41
parseargs :arrow_heading_up: 41
bytesmith :arrow_heading_up: 36
data-lens :arrow_heading_up: 34
distributed-process :arrow_heading_up: 30
iteratee :arrow_heading_up: 29
jmacro :arrow_heading_up: 29
ip :arrow_heading_up: 26
either-unwrap :arrow_heading_up: 25
HList :arrow_heading_up: 23
SciBaseTypes :arrow_heading_up: 22
haskelldb :arrow_heading_up: 22
hsc3 :arrow_heading_up: 22
wxdirect :arrow_heading_up: 22
BiobaseTypes :arrow_heading_up: 21
wxc :arrow_heading_up: 21
biocore :arrow_heading_up: 20
secp256k1-haskell :arrow_heading_up: 20
wxcore :arrow_heading_up: 20
attoparsec-enumerator :arrow_heading_up: 19
bytestring-show :arrow_heading_up: 19
numhask :arrow_heading_up: 19
polysemy-plugin :arrow_heading_up: 19
wx :arrow_heading_up: 19
BiobaseENA :arrow_heading_up: 18
asn1-data :arrow_heading_up: 18
dbus-core :arrow_heading_up: 18
gtksourceview2 :arrow_heading_up: 18
BiobaseXNA :arrow_heading_up: 17
HGamer3D-Data :arrow_heading_up: 17
certificate :arrow_heading_up: 17
dbus-client :arrow_heading_up: 17
gconf :arrow_heading_up: 17
gtk-serialized-event :arrow_heading_up: 17
uuid-orphans :arrow_heading_up: 17
cuda :arrow_heading_up: 16
happstack-jmacro :arrow_heading_up: 16
manatee-core :arrow_heading_up: 16
monads-fd :arrow_heading_up: 16
murmur3 :arrow_heading_up: 16
tls-extra :arrow_heading_up: 16
ADPfusion :arrow_heading_up: 15
MaybeT :arrow_heading_up: 15
blaze-builder-enumerator :arrow_heading_up: 15
clash-prelude :arrow_heading_up: 15
hetero-dict :arrow_heading_up: 15

:arrow_heading_up:: The number of packages that depend (directly or indirectly) on this package (if any). If two numbers are shown the first (lower) number considers only packages which currently have enabled hydra jobs, i.e. are not marked broken. The second (higher) number considers all packages.
Report generated with maintainers/scripts/haskell/hydra-report.hs

Hi,
I don't understand why hledger 1.23, released in September, is not included:

LTS stackage has version 1.21
hackage has version 1.23

I don't understand why hledger 1.23, released in September, is not included:

By default, if a package is in Stackage we use that version. If there is a newer version on Hackage it is also included with a version suffix.
hledger 1.23 can be found under haskellPackages.hledger_1_23.

Oh, yeah that slipped in. It requires a patch from hlint, but one which doesn't download from github nicely. This is better than the previous state in that it at least evaluates...

That was fixed in a1f0dff4a71aa4367dae205d058b03a8cf786442.

futhark now (really) requires aeson <IP_ADDRESS>, may need to restrict its version for now.


compatibility with the web

Hi
Is this package compatible with the flutter web? How can I use it?
I have this error:
Error: Unsupported operation: Platform._operatingSystem
    at Object.throw_ [as throw] (http://localhost:56933/dart_sdk.js:5334:11)
    at Function._operatingSystem (http://localhost:56933/dart_sdk.js:56144:17)
    at Function.get operatingSystem [as operatingSystem] (http://localhost:56933/dart_sdk.js:56190:27)
    at get _operatingSystem (http://localhost:56933/dart_sdk.js:56103:27)
    at Function.desc.get [as _operatingSystem] (http://localhost:56933/dart_sdk.js:5839:17)
    at get isLinux (http://localhost:56933/dart_sdk.js:56115:26)
    at Function.desc.get [as isLinux] (http://localhost:56933/dart_sdk.js:5839:17)
    at flutter_secure_storage.FlutterSecureStorage.new.[_selectOptions] (http://localhost:56933/packages/flutter_secure_storage/flutter_secure_storage.dart.lib.js:175:33)
    at flutter_secure_storage.FlutterSecureStorage.new.read (http://localhost:56933/packages/flutter_secure_storage/flutter_secure_storage.dart

There currently is no web support. Please check out https://github.com/mogol/flutter_secure_storage/issues/96 for more info.


Additions to Programmatic Modification

Just wanted to get some thoughts put somewhere so I don't forget.  I have been going through everything trying to see the flow and I have two thoughts on the Programmatic Modification:

Maybe someone can make a script that does all the excel cleaning through programmatic modification using R? To show the power of a script running it?  Like a ta da moment.  Maybe for next bootcamp?

Programmatic modification is something that takes a lot of time to learn. Maybe incorporate strategies of how to achieve this over time. Like when you have a problem, approach it as chance to learn R with YOUR material instead of a tutorial. It may take more time, but you are getting two things done at once; learning to code AND cleaning your data. Or if you never solve the problem, start a list of what you couldn’t do. Learn when you have more time.

Thanks again @naupaka for the base! Looks great.

Also, version control is left out completely in this course, since Organization 2 disbanded.  Could we fit a small introduction in here?  Just a thought.

Hi @iamciera - just added a first pass effort on the script to do the cleaning as described in the instructors file. Take a look - not sure the best way to pull off the header/footer business in a clean way.

Also just added a paragraph regarding your second point to the end of the lesson file.


make text view work with documents from other domains

The text view (seed-synopsis-text) does not yet work with texts from other domains due to xss. When trying, java script of the document presented in the iframe is not evaluated.
see sandbox attribute of <iframe> element, https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe?retiredLocale=de#sandbox
Test: run usage example like Jiob Frontend locally, which fetches texts from remote.

mentioned in commit e4fb185655a1bf502a2d62425044a613a98b865b

mentioned in commit 4ba48df1fe5887d1ba7ef0aa911166407da9aa55

mentioned in commit 31d3203bf2023f209b5c1af874fd910211d22623

added 2h of time spent

This was implemented in release 0.7.0.

mentioned in commit 71ceef29eb985acece325e69b2b12b58a2da33eb

added 4d of time spent


[SPARK-9581][SQL] Add unit test for JSON UDT

This brings #7416 up-to-date by @drubbo.

cc @yhuai / @davies for review.

Merged build triggered.

Merged build started.

Test build #39621 has started for   PR 7917 at commit 7035308.

Test build #39621 has finished for   PR 7917 at commit 7035308.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39660 has started for   PR 7917 at commit 93e3954.

Test build #39660 has finished for   PR 7917 at commit 93e3954.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #1321 has started for   PR 7917 at commit 93e3954.

Test build #1321 has finished for   PR 7917 at commit 93e3954.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1347 has started for   PR 7917 at commit 93e3954.

Test build #1347 has finished for   PR 7917 at commit 93e3954.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Alright I'm merging this.


Update writer integration

Update Writer LLM integration
Changes the parameters and base URL to be in line with Writer's current API.
Based on the documentation on this page: https://dev.writer.com/reference/completions-1

thanks for the fix @heathexer!


Auth0 integration

Need to check integration with codingcoach auth0 configuration, also, I need to check the iOS version


Story Line Implementation

Description
Task: Story Line Implementation of UI
Feature: Overall Game Features
This is a collaboration task undertaken by Team 6 and Team 1. Team 6 is providing Story Line aspects for Team 1 to implement. Other aspects may be worked on together. Create the integration of Stage 2 story into the game seamlessly and provide a backstory for the next animal.
Dependencies

[ ] Story Line [Stage 2] - UI for the Story Boards (#369)

Milestones
List of steps that need to be completed for this task.

[ ] Story UI (Sep. 23)
[ ] Create screens to display story (Sep. 25)
[ ] Test ensure sizing formatting (Sep. 26)
[ ] Dialogue for each screen (Sep. 29)
[ ] Testing for screens (Sep. 30)

Documentation
Story Line [Stage 2]
Member

Jaimee Taylor (@jtayl647)

I changed the ticket was a typo


Lineage

Functionality for saving Entities and Relationships relating to Horizontal Lineage in bufferGraph.

Just a FYI, JavaDoc is now run on every build. Whilst we don't check that all methods are documented (we could!), it is important that the javadoc copiler doesn't find errors. The latest PR build seems to be failing on the javadoc in the lineage modules. You can run mvn javadoc:javadoc just to run this stage.


fix: improve build file naming convention and caching

In revision: https://github.com/vbenjs/vue-vben-admin/commit/a6086f4cc8f33fea7431f3d39eb73dda20c325bd
Using entryFileNames: 'index.js' in Vite is generally not recommended due to several issues:

Caching Problems: Without a unique identifier, browsers may load stale versions from cache.
Name Conflicts: Multiple entry points will overwrite each other, causing conflicts.
Debugging Difficulty: Identical filenames make debugging harder as they don't reflect their origin or purpose.

Also using entryFileNames: 'index.js'  is not aligned to the  Docker file
CMD sed -i "s|__vg_base_url|$VG_BASE_URL|g" /usr/share/nginx/html/dist/assets/entry/index-*.js

https://github.com/vbenjs/vue-vben-admin/blob/8d3981f599f073b226c822a8d28af9aecf00a667/Dockerfile#L23C2-L23C99
Reference issue: https://github.com/vbenjs/vue-vben-admin/issues/3905
General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

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

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[x] My code follows the style guidelines of this project
[x] Is the code format correct
[x] Is the git submission information standard?
[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

cc @xachary


merge 'main-lachie' into 'main'

#25  👈 (View in Graphite)
main-lachie

This stack of pull requests is managed by Graphite. Learn more about stacking.


 It's a collaboration meeting week, and S3DF is down, so I can't work on this right now. I can hand it off to you next week.

What do you mean by "hand off"?
I'm mainly going to be adding tests to make sure the task is giving results as expected.  The most detailed tests will still be in the descwl_coadd package.

This is ready for a review. I had originally intended to set these up and merge, and for you to add further tests on top of these on another branch. I think that might still be for the best here.

Arun is this ready for review?

Yes, Erin, this PR is ready for a review.

Arun our reviews are complete

Thanks Ern and Matt. I'll address the review comments next week when I'm back from vacation.

Shall we merge this and then I can add more tests in a separate PR?

Should we wait for Matt to approve or at least dismiss the change request? I could bypass the branch protection and merge, but I'd rather not.

Let's wait for Matt who is back from vacation tomorrow


added a real test case

Fixes #3 by adding a long-awaited test case showcasing the true power behind lerp

   Expected: 59
       got: 59.00000000000001

Feels bad man

I think you can make the test pass by casting the number to an Int32, see: https://crystal-lang.org/docs/syntax_and_semantics/as.html
Can you please update the README to include your test case that exposes lerp's powerlevel? I'd appreciate that very much :smile:

LGTM :+1:


WriteBlittable Android issues

note that this gave invalid IL errors in the past.
now it seems to only give NRE

note that we could use NativeArray and call .GetPtr() to avoid 'fixed' every time

You also forget that in the past that Blittable on ARMv7 architecture (older devices or low-end phones) also caused fatal application errors unless that has been fixed via IL2CPP or whatnot. That's what my original fix was for - to prevent ARMv7 devices which are still common in the market, or devices running 32bit ARMv7 applications on their native 64bit ARM64/AArch64 platform. The latter is like the WOW64 Windows subsystem - without it, you would not be able to run 32bit applications.

also note that we could try 'fixed byte*' and then simply copy N bytes instead of 'T*'

reopening so we can try to reproduce and try several fixes.
cooper: https://github.com/Derek-R-S/Light-Reflective-Mirror/blob/main/UnityProject/Assets/Mirror/Runtime/Transport/LRM/LRMTools.cs#L111

works fine with android emulator ARM, Unity 2021.2.7, IL2CPP

more details.
reported by ADIIO in Discord.

hardware: " Xiaomi redmi note 8, android 9 (pie)"
il2cpp.
player settings -> API compatibility level: net standard 2.0

works fine for jesus and fakebyte.
adiio can still repro in his own build over LAN:

:
AndroidPlayer(ADB@<IP_ADDRESS>:34999) NullReferenceException: Object reference not set to an instance of an object
  at Mirror.NetworkWriter.WriteBlittable[T] (T value) [0x0002d] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkWriter.cs:117
  at Mirror.NetworkWriterExtensions.WriteDouble (Mirror.NetworkWriter writer, System.Double value) [0x00000] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkWriter.cs:205
  at Mirror.GeneratedNetworkCode._Write_Mirror.NetworkPingMessage (Mirror.NetworkWriter writer, Mirror.NetworkPingMessage value) <0xcb10ade0 + 0x00063> in <c7b337358a1146978f4ad6a53807b44d>:0
  at (wrapper delegate-invoke) System.Action`2[Mirror.NetworkWriter,Mirror.NetworkPingMessage].invoke_void_T1_T2(Mirror.NetworkWriter,Mirror.NetworkPingMessage)
  at Mirror.NetworkWriter.Write[T] (T value) [0x0002e] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkWriter.cs:155
  at Mirror.MessagePacking.Pack[T] (T message, Mirror.NetworkWriter writer) [0x0000f] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\MessagePacking.cs:43
  at Mirror.NetworkConnection.Send[T] (T message, System.Int32 channelId) [0x00008] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkConnection.cs:133
  at Mirror.NetworkClient.Send[T] (T message, System.Int32 channelId) [0x0001b] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkClient.cs:433
  at Mirror.NetworkTime.UpdateClient () [0x00028] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkTime.cs:96
  at Mirror.NetworkClient.NetworkLateUpdate () [0x0004c] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkClient.cs:1365
  at Mirror.NetworkLoop.NetworkLateUpdate () [0x00018] in D:\Mirror-android_blittable_repro\Assets\Mirror\Runtime\NetworkLoop.cs:205

ARMv7 is 32bit, yes.

Congrats, you got the Blittable Address Alignment error on ARMv7 CPUs. This is one reason I wrote a patch to make the readers/writers not use Blittable on Android build targets - I am not sure about iOS but ARMv7 iOS devices are literally unsupported now iirc.

for future reference, this is a simply repro as suggested by @FakeByte

    unsafe void TryUnaligned()
    {
        byte[] buffer = new byte[30];
        for (int i = 0; i < 18; ++i) {
            // 0 is aligned, 1 is aligned, etc.
            fixed (byte* ptr = &buffer[i])
            {
                double* double_ptr = (double*)ptr;
                *double_ptr = Math.PI;
            }
        }
        Debug.Log("repro unaligned: " + BitConverter.ToString(buffer));
    }

FakeByte
:
You get the memory address of buffer[position] which might not be correctly aligned and will cause issues on some CPU's
[
11:27 PM
]
FakeByte
:
I know on dektop platforms unaligned access are slower but will work, but especially older arm platforms dont like that

fixed in https://github.com/vis2k/Mirror/commit/b54d0869014a7783b41baa1c7413478220ae9b7e


pull down changes to badger-finance

merging this one - looks like repo will direct PR to the main public repo.


3rd party alert management

Title
Description
For customers who are not using Prometheus, Prometheus conversion tools seem to be an option.  Similiar to the ORM compatibility page, CockroachLabs does not own the other tools.  Should these tools be listed as known to work based on customer feedback and may be listed as alpha support?
Outline
Sysdig can read Prometheus exporters. https://sysdig.atlassian.net/wiki/plugins/servlet/mobile?contentId=64946336#content/view/64946336
Stackdriver can scrape metrics stored in Prometheus text format from one or multiple components   https://github.com/GoogleCloudPlatform/k8s-stackdriver/tree/master/prometheus-to-sd
Expected Audience
DevOps and Operations

Supports #2120


[core] Added IGNORE_CUSTOM_CACHE_TIMEOUT option

Explaining my usecase. For some reason I enabled custom_timeout in my config, but forgot to disable it back. Meanwhile some users already generated feed urls with _cache_timeout parameters. So if I disable custom_timeout back, those feed urls become invalid, which is not good.
So, I added option to ignore _cache_timeout param in url.

Thanks for the PR :+1:

So if I disable custom_timeout back, those feed urls become invalid, which is not good.

I agree, this is a server-side issue.

So, I added option to ignore _cache_timeout param in url.

This doesn't feel right to me and is confusing to new users. Users might also question if the parameter is even applied in their specific situation, which adds a layer of uncertainty.
An alternative to this is replying with the "301 Moved Permanently" header. Feed readers and browsers will automatically follow the location provided in the header. Here is some code for reference:
header('Location: index.php?action=...', true, 301);

Would that work for you?

Almost. Maybe I should have explained myself better.
You can remove ignore_custom_timeout entirely and just assume, that custom_timeout = false implies ignore_custom_timeout = true. That way, you only need to replace this line:
https://github.com/RSS-Bridge/rss-bridge/blob/78c69b08f0f544e0eb0caa16ae94771eabd33764/index.php#L129
by this:
unset($params['_cache_timeout']);
header('Location: ' . parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH) . '?' . http_build_query($params), true, 301);
die();

So, if custom_timeout = true, everything works fine.
If custom_timeout = false, everyone gets redirected.

Merged. Thanks for keeping it updated! :+1:


[DO NOT MERGE] Fix llm dropdown display condition

DO NOT MERGE.
We can make a release from this branch and recommend the pre-release version (nightly channel version).
Test plan

For all account types {enterprise, free, pro}
open a project
open Cody
the dropdown shows expected entries

This fix has been released in:
https://plugins.jetbrains.com/plugin/9682-sourcegraph-cody--code-search/versions/nightly/492106
(and the corresponding release version aka stable channel)


replace the modal close icon

replace the modal close icon with one that looks nicer, and aligns properly. Likely SVG.
Before:

closing this as has been addressed by above PR


Close POAM V17-CM-6: X-Content-Type-Options Header Missing

In order to demonstrate that our system has an acceptable level of risk, we need to close this identified potential risk as resolved or invalid.
Document for drafting operational requirements
Acceptance Criteria:

[x] Where possible, we have OWASP ZAP scans that show this is fixed.
[x] For the rest that depend on upstream PRs, we've documented an operational requirement
[x] Rationale has been approved by our AO.
[x] Sent rationale to 3PAO.
[x] 3PAO has verified our rationale.

More Information

See POAM for details.
NIST Special Publication 800-53 (Rev. 4) CM-6

This has been remediated for sites behind secureproxy, but has not been remediated for other sites (concourse, metrics, etc)

Updated acceptance criteria, since we can close OWASP ZAP items by providing updated scans.

Outstanding issues related to this:
https://github.com/18F/cg-product/issues/472
https://github.com/18F/cg-product/issues/469

Updated acceptance criteria again to reflect our approach to this one. Drafted rationale here, sent to AO for approval (https://github.com/18F/Infrastructure/issues/745).

There's no more active work on this one to do for now.


Added CONTRIBUTING.md

This PR fixes #32

This PR fixes #32

Contributing.md file already exists. @suhanipaliwal

But this issue was assigned to me so I have already worked on it.


added obs and obs6 locations and access instructions for JASMIN and DKRZ in documentation

Description
CEDA/JASMIN and DKRZ instructions how to use OBS and OBS6 CMORized data

Closes #1072
Link to documentation:

Before you get started

[ ] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[ ] 🛠 This pull request has a descriptive title
[ ] 🛠 Documentation is available
[ ] 🛠 Tests run successfully
[ ] 🛠 All checks below this pull request were successful

@valeriupredoi Release v2.5 is approaching quickly (the feature freeze will be on 2022-02-21). Since this pull request is marked for v2.5, could you briefly comment if you further intend to include this in the new release and/or if you are facing any problems with it? Thanks!!

@schlunma thanks for policing us :police_officer: :grin: I am currently waiting on this https://github.com/ESMValGroup/ESMValTool/pull/2385#issuecomment-953747102 - no rush, we can postpone to 2.6 if need be :+1:

Sorry my late reply and lack of action @valeriupredoi! I am still a bit concerned about two things:

giving the impression that we would widely distribute the cmorizer Tier3 data
managing the way we would give access to OBS data at DKRZ without giving every interested person the access to our computing resources. If we allow users to our computing project, we could restrict that in a way that people would not use our computing time but they could still fill up all our storage quota... The alternative would be to have a script that gives reading permissions for a bunch of files (a dataset) to a given DKRZ user.

Well, I'm tempted to postpone this PR to v2.6. First of all, it would give us time to advertise the new cmorizer interface. This includes a command esmvaltool data info DATASET that directly outputs info on the data source, how to get the data, register and sign the data terms of use. By asking people to take a look at that, we could more safely decline responsibility if Tier3 datasets for which we gave access were to be misused. Second, it would give us time to see how we would manage the data access opening at DKRZ. Nevertheless, if you really want to have that in the documentation for Jasmin in v2.5, please go ahead and I can take a look 👍

sorry for the late reply @remi-kazeroni - a storm and weekend stood inbetween us :grin: I fully agree with you on this one, and I have just changed the milestone to 2.6. Additional to your solid case in the comment, I would argue we need the @ESMValGroup/userengagementteam to have some readily available info on how we deal with OBS data - this question, together with how to install the tool and obtain CMIP model data, is a very frequent one and it'd be good to have this sort of info in their tutorial/User engagement documentation etc (if they don't already) so we should do this in lock-step with them (yeah this is a popular term in the current European geopolitical environment :grin: )

As mention in https://github.com/ESMValGroup/ESMValTool/issues/1072#issuecomment-1190100222, this will be moved to the next milestone.

what you reckon @remi-kazeroni - shall we move this one click further to 2.8?

what you reckon @remi-kazeroni - shall we move this one click further to 2.8?

Yes, let's move it to the next milestone. This requires more discussion and action. The upcoming workshop should be a good place for that.

gonna have to move this to M2.10 but @remi-kazeroni @rswamina and meself we should have a sit down talk about this stuff, perhaps at the Sweden workshop?

gonna have to move this to M2.10 but @remi-kazeroni @rswamina and meself we should have a sit down talk about this stuff, perhaps at the Sweden workshop?

Did you? :smile:

well well well, what do we have us here? Old stuff! @zklaus - in principle this ca go in, but we need to add the DKRZ info, so do you think the CEDA bit will suffice for now?

Yeah. Some documentation is better than no documentation.

cheers @zklaus - I have now resurrected this from orphan-land :grin:

release boys @zklaus and @bouweandela - merge this one pls, and that's it for M2.10 PRs :beer:


fix display config on row click in filters

Notes for Reviewers
This PR fixes #
To display on row click and edit icon click the correct config of particular filter

Signed commits

[x] Yes, I signed my commits.

Thanks, guys.


Try using webrequest onbeforerequest for redirect for seamless user experience

This extension seems to redirect after the shorts page has loaded(partially) which creates a black screen and delays the video load by quite some time.
https://github.com/tom-james-watson/old-reddit-redirect/blob/master/background.js
Try using https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/onBeforeRequest

This event is triggered when a request is about to be made, and before headers are available. This is a good place to listen if you want to cancel or redirect the request.

I used declarativeNetRequestAPI as a trial since it replaced webRequestAPI with declarativeNetRequestAPI in Manifest v3. (Firefox is not supported).
As a result, redirects in Chrome are now very fast.
Thanks for the great suggestion👍 c1cfc6c0356681e19c773294d9cd6aae1a17b985


Unicode issue in paths

If the path passed to
https://github.com/OneDrive/onedrive-sdk-python/blob/master/src/onedrivesdk/extensions/drive_request_builder_helper.py#L40
contains a unicode character it blows up with a unicode error. Is it valid to have unicode characters in paths in onedrive? if so, this should be updated.

This PR(#137) may address and provide a quick fix for this issue considering unicode character is not allowed in paths.

@DataSapient I recommend you have this behavior implemented in your PR:

Include it in the docs
By default remove unicode characters
Raise a warning when it removes unicode characters, by default
Have an option on whether to remove unicode or not
If they manually say they want to remove unicode not raise a warning
That should keep everyone happy.

Thank you for reaching out and for your patience. This SDK is being officially deprecated. See #209 for more information


modal still showing when set  to false when from prev screen , when nav back showing modal

Environment

Platforms

Versions

Android:
iOS:
react-native-modal:
react-native:
react:

Description

Reproducible Demo

Same issue here !


Jacoco doesn't accept Provider type when using version catalog to reference versions

Expected Behavior
Given that libs.versions.jacoco returns Provider<String>, jacoco was expected to accept the given type.
apply plugin: 'jacoco'

jacoco {
    toolVersion = libs.versions.jacoco
}

Current Behavior
Build error: Could not find org.jacoco:org.jacoco.agent:provider(?).
Need to apply .get() in order to return the version declared in version catalog.
apply plugin: 'jacoco'

jacoco {
    toolVersion = libs.versions.jacoco.get()
}

Context

Accepting Provider type will result in improved build performance, as it'll only re-execute tasks where jacoco is used.

We plan to change toolVersion into a lazy property in 9.0.


change voice fail by command

I use command to convert wav files，sounds is change，but not change to chino's voice, did I miss anything?  this is command:
cd F:\sd-webui\DDSP\DDSP-SVC; ./runtime/Scripts/activate.bat; ./runtime/python.exe main.py -i F:\sd-webui\DDSP\test\test.wav -m exp/model_chino.pt -o F:\sd-webui\DDSP\test\chino.wav -k 0 -id 1 -e true -eak 0
output:
`
2023-04-17 10:05:36 | INFO | fairseq.tasks.text_to_speech | Please install tensorboardX: pip install tensorboardX
[DDSP Model] Combtooth Subtractive Synthesiser
[Loading] exp/model_chino.pt
Pitch extractor type: crepe
Extracting the pitch curve of the input audio...
Extracting the volume envelope of the input audio...
[Encoder Model] HuBERT Soft
[Loading] pretrain/hubert/hubert-soft-0d54a1f4.pt
Enhancer type: nsf-hifigan
| Load HifiGAN:  pretrain/nsf_hifigan/model
Removing weight norm...
Speaker ID: 1
Cut the input audio into 2 slices
100%
`
this command fail too,
cd F:\sd-webui\DDSP\DDSP-SVC; ./runtime/Scripts/activate.bat; ./runtime/python.exe main.py -i F:\sd-webui\DDSP\test\test.wav -m exp/model_chino.pt -o F:\sd-webui\DDSP\test\chino.wav -k 0 -id 1 -e false
output:
`
2023-04-17 10:07:58 | INFO | fairseq.tasks.text_to_speech | Please install tensorboardX: pip install tensorboardX
[DDSP Model] Combtooth Subtractive Synthesiser
[Loading] exp/model_chino.pt
Pitch extractor type: crepe
Extracting the pitch curve of the input audio...
Extracting the volume envelope of the input audio...
[Encoder Model] HuBERT Soft
[Loading] pretrain/hubert/hubert-soft-0d54a1f4.pt
Enhancer type: none (using raw output of ddsp)
Speaker ID: 1
Cut the input audio into 2 slices
100%
`

What type of input did you use? If the input is a male voice and the target is a female voice, it is best to use the -k parameter to raise the key

thanks, I got the point.


Restructure: Create conda-env-update buildpack

Background
See RFC 0001 that outlines the proposed restructure of python family of buildpacks. In order to conform to the RFC, a new conda-env-update buildpack should be created that is responsible for updating/creating a conda environment based on the environment file in app source code.
Proposal

Create a new repository named conda-env-update at github.com/paketo-community/conda-env-update
Transfer this issue to conda-env-update.
Create a buildpack using packit that runs the logic of "conda env update" or "conda env create" by requiring conda.
Buildpack API should be as follows:

provides: conda-environment
requires: conda during build

Write an RFC describing the behavior of this buildpack.

Extra notes:
Please update the README and GoDoc to be consistent with buildpacks in this language family
Please use buildpack API 0.4 in the buildpack.toml

Picking this up.

Still in flight. Latest work is here: https://github.com/andymoe/conda-env-update/tree/packit-restructure

The linked PR is blocked by https://github.com/paketo-community/miniconda/issues/96


[Snyk] Security upgrade merge from 1.2.1 to 2.1.1

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

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

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

758/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.3
Prototype Pollution SNYK-JS-MERGE-1042987
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: merge
    The new version differs by 27 commits.

56ca75b build: v2.1.1
7b0ddc2 fix: prototype pollution
8686d85 build: bump version
80151be build
0acaaf3 build: update dev dependencies
f571887 Merge pull request #38 from 418sec/master
869927f Merge pull request #1 from alromh87/master
c2f8454 Fix Prototype Pollution
bf8b1ff build: include typings
ece8885 Merge pull request #32 from yeikos/develop
43ffa43 build: include only needed files
7bf0fc8 fix: export default function (typings)
159e724 build: bump version
21f4105 fix: default typings
36d4b9c build: new npm scripts
eabfd6f build: CommonJS support
bf85170 test: add merge script
75ba781 build: add editor config
2d2b54a build: update ignored files
b36036a docs: remove license copyright
1385593 build: update main script and description
2b22e6b docs: update readme
7cc6574 build: package-lock.json
29e46a8 build: ts and webpack config

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

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

Pull Request Test Coverage Report for Build 594743351

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

Totals

Change from base Build 350934710:
0.0%

Covered Lines:
99

Relevant Lines:
104

💛  - Coveralls


[BUG] Errors when importing SOK and Data loader

I am not able to import Merlin Dataloader + SOK in TensorFlow. Either order (first SOK -> Dataloader OR Dataloder -> SOK) throws an error (see thread).
Importing sok and then data loader
import os

import tensorflow as tf
import sparse_operation_kit as sok

os.environ["TF_GPU_ALLOCATOR"]="cuda_malloc_async"  # fraction of free memory

BATCH_SIZE = 64000
os.environ["CUDA_VISIBLE_DEVICES"] = ",".join(map(str, range(1)))
sok.Init(global_batch_size=BATCH_SIZE)

import nvtabular as nvt
from nvtabular.loader.tensorflow import KerasSequenceLoader, KerasSequenceValidater
from nvtabular.framework_utils.tensorflow import layers

File /usr/local/lib/python3.8/dist-packages/tensorflow/python/framework/config.py:874, in set_logical_device_configuration(device, logical_devices)
    810 """Set the logical device configuration for a `tf.config.PhysicalDevice`.
    811
    812 A visible `tf.config.PhysicalDevice` will by default have a single
   (...)
    872   RuntimeError: Runtime is already initialized.
    873 """
--> 874 context.context().set_logical_device_configuration(device, logical_devices)

File /usr/local/lib/python3.8/dist-packages/tensorflow/python/eager/context.py:1601, in Context.set_logical_device_configuration(self, dev, virtual_devices)
   1600 if self._context_handle is not None:
-> 1601   raise RuntimeError(
   1602       "Virtual devices cannot be modified after being initialized")
   1604 self._virtual_device_map[dev] = virtual_devices

RuntimeError: Virtual devices cannot be modified after being initialized

During handling of the above exception, another exception occurred:

TypeError                                 Traceback (most recent call last)
Input In [1], in <cell line: 13>()
     10 sok.Init(global_batch_size=BATCH_SIZE)
     12 import nvtabular as nvt
---> 13 from nvtabular.loader.tensorflow import KerasSequenceLoader, KerasSequenceValidater
     14 from nvtabular.framework_utils.tensorflow import layers

File /nvtabular/nvtabular/loader/tensorflow.py:28, in <module>
     25 from nvtabular.loader.backend import DataLoader
     26 from nvtabular.loader.tf_utils import configure_tensorflow, get_dataset_schema_from_feature_columns
---> 28 from_dlpack = configure_tensorflow()
     29 LOG = logging.getLogger("nvtabular")
     30 # tf import must happen after config to restrict memory use

File /nvtabular/nvtabular/loader/tf_utils.py:64, in configure_tensorflow(memory_allocation, device)
     58         tf.config.experimental.set_virtual_device_configuration(
     59             tf_devices[device],
     60             [tf.config.experimental.VirtualDeviceConfiguration(memory_limit=memory_allocation)],
     61         )
     62     except RuntimeError as e:
     63         # Virtual devices must be set before GPUs have been initialized
---> 64         warnings.warn(e)
     66 # versions using TF earlier than 2.3.0 need to use extension
     67 # library for dlpack support to avoid memory leak issue
     68 __TF_DLPACK_STABLE_VERSION = "2.3.0"

TypeError: expected string or bytes-like object

Importing Dataloader and then SOK
import os

import tensorflow as tf
import sparse_operation_kit as sok

os.environ["TF_GPU_ALLOCATOR"]="cuda_malloc_async"  # fraction of free memory

import nvtabular as nvt
from nvtabular.loader.tensorflow import KerasSequenceLoader, KerasSequenceValidater
from nvtabular.framework_utils.tensorflow import layers

BATCH_SIZE = 64000
os.environ["CUDA_VISIBLE_DEVICES"] = ",".join(map(str, range(1)))
sok.Init(global_batch_size=BATCH_SIZE)

---------------------------------------------------------------------------
AbortedError                              Traceback (most recent call last)
Input In [1], in <cell line: 15>()
     13 BATCH_SIZE = 64000
     14 os.environ["CUDA_VISIBLE_DEVICES"] = ",".join(map(str, range(1)))
---> 15 sok.Init(global_batch_size=BATCH_SIZE)

File /usr/local/lib/python3.8/dist-packages/SparseOperationKit-1.1.2-py3.8-linux-x86_64.egg/sparse_operation_kit/core/initialize.py:237, in Init(**kwargs)
    234         return _horovod_init(**kwargs)
    235 else:
    236     # horovod not imported
--> 237     return _one_device_init(**kwargs)

File /usr/local/lib/python3.8/dist-packages/SparseOperationKit-1.1.2-py3.8-linux-x86_64.egg/sparse_operation_kit/core/initialize.py:198, in Init.<locals>._one_device_init(**kwargs)
    196 global_seed = kwargs.get("seed", None) or kit_lib.gen_random_seed()
    197 visible_devices = _get_visible_devices()
--> 198 status = kit_lib.plugin_init(local_rank, 1, unique_id, global_seed, visible_devices,
    199                              global_batch_size=kwargs["global_batch_size"])
    200 return status

File <string>:1455, in plugin_init(global_replica_id, num_replicas_in_sync, nccl_unique_id, global_seed, visible_devices, global_batch_size, name)

File /usr/local/lib/python3.8/dist-packages/tensorflow/python/framework/ops.py:7107, in raise_from_not_ok_status(e, name)
   7105 def raise_from_not_ok_status(e, name):
   7106   e.message += (" name: " + name if name is not None else "")
-> 7107   raise core._status_to_exception(e) from None

AbortedError: /workspace/build-env/sparse_operation_kit/kit_cc/kit_cc_infra/src/resources/cpu_resource.cc:47 Intra-process barrier blocking threads time out. [Op:PluginInit]

The HugeCTR team proposed that it could be related to having multiple GPUs and not using MirrorStrategies. They shared an example:
import os

import tensorflow as tf
import sparse_operation_kit as sok

os.environ["TF_GPU_ALLOCATOR"]="cuda_malloc_async"  # fraction of free memory

import nvtabular as nvt
from nvtabular.loader.tensorflow import KerasSequenceLoader, KerasSequenceValidater
from nvtabular.framework_utils.tensorflow import layers

BATCH_SIZE = 64000
os.environ["CUDA_VISIBLE_DEVICES"] = ",".join(map(str, range(1)))
strategy = tf.distribute.MirroredStrategy()
with strategy.scope():
    sok.Init(global_batch_size=BATCH_SIZE)

@bschifferer , please triage this bug

I dont know if this bug is still valid - it is from April 6th. I havent worked on SOK + dataloader since then. But if we want to provide both, then this is important

@bschifferer ,  is this a P0 or P1 ?


Upgrade protobuf to 0.11

This is a relatively small change.

protobuf version spec was set to ~> 0.11 in mix.exs
regenerated files using 0.11 compiler

Hey, is there anything I can do to get this merged? Thanks. :)

Hi, this would be really good to have. Anything we could help to move this forward?  @ethanvaughn

@davelooi Why do you need the upgrade, does anything break when using this library with protobuf 0.11?

Actually, it's not broken. Managed to figure out what was blocking my upgrade. Thanks for responding.


[FEATURE REQUEST] - Don't download cache if it exists

By editing Buildkite's git-clean-flags we can exclude cache files or directories from being removed during checkout. If this is so, this plugin could check if the cache files/folders already exist and skip restoring it.
This could be done with a key like skip_restore_existing or something.

Yup! Great idea.
I will prepare after other pending bug.

I've evaluated possible use cases and, I'm not sure If checking existing directories are reliable or not. For example, you may change cache folders on next builds which leads to incorrect match. However, It is still possible to do so. I'll handle this on v2.5.0. Feel free to send your PR if you have any proposal.

Not stale

Not stale


tour (shepherd.js)

Problem/Need:
To help not-confident users (or people who wouldn't mind a reminder).
Suggestions:

[ ] automatically ask user if they want a tour or something, based on a date stored locally (localStorage?) - maybe ask if it's been a month since the last visit
[ ] add test to prevent regressions in the tour
[ ] add ability for the test to set the date (in localStorage?) so that it can reliably test this feature

References:
https://codepen.io/hchiam/pen/xxGXMLv
https://github.com/hchiam/code-inspiration/blob/master/src/helpers/tour.js
https://shepherdjs.dev

Going for a more elegant option: #87


[transaction-coordinator] Implementation of transaction coordinator client.

Motivation
Implement transaction coordinator client.
Modifications
Add transaction coordinator client.
Add transaction meta store handler to handle meta store request and response.
Verifying this change
Unit test added.


fix parallel runs w/ vtkmofo

[x] Fix parallel runs with vtkmofo w/ FV
[ ] Convert to use the new vtk format:

[ ] FV
[ ] FD

@porteri I think this is resolved now, correct? I'm going to close, but please re-open if I'm mistaken.


Merging Linux simulator update from dbwz8/simDbg

Trailing semi-colon is wrong. Original was correct

Got it, I'll fix that.


Remove ustring::operator int()

As pointed out by Thiago Ize and John Haddon (but unfortunately not
heard by me until literally years later), this is error prone because
there are times when a ustring is converted to an int/bool in unexpected
situations. It even led to verifiable errors in OSL that I only
discovered after commenting out this operator to see what would happen.
Neither std::string nor std::string_view have this operator, bolstering
Thiago & John's arguments.
So we are removing it from OIIO 2.0. Hopefully this won't break too many
people's apps that happen to make use of ustring. The fix is simple, just
change:
if (myustring)

to
if (! myustring.empty())

Because this is a back-compatibility break, this change will only be merged into master, NOT backported to any current release branches.

LGTM!


Mccalluc/more css modules

More CSS modules. I'm hoping that by using modules, it will be easier to split off components in the future... but if the extra complexity of the code feels burdensome to you, that's also useful to know.

Note: not necessary for next release

@keller-mark : Have you had a chance to look at this?

Hmm, I don't see how scss nesting would change things... it's just the top-level class that gets renamed dynamically. (Though there are other things I'm uncertain about.)


Unit 1.32 Release

We are about launching Unit 1.32 and this requires some changes in our Docs as well. This Task-List is to keep track of the changes need and link the resulting PRs.
Release 1.32.0

[ ] Adding a News Item to News / 2024 / Unit 1.32.0 Released.
[ ] Adding an News Item to News - Unit 1.32.0 Released / Version 1.32.0 adds support for the WebAssembly Component Model / WASI 0.2 APIs, access Unit variables from NJS Scripting, conditional access logging and more! Details

NJS Updates
Release Related

[ ] Bump NJS Version to 0.8.2 in Scripting . We have to be clear in the messag that 0.8.2 is the only version that will be supported by 1.32.0.

General Issues

[ ] On Scripting we are referencing to njs. We should be more clear an spell it out as NGINX JavaScript Engine "njs".

WASM Updates

[ ] Adding a new News Entry for a WASM Blog Post

We should be more clear an spell it out as NGINX JavaScript Engine "njs".

I've never seen the word 'engine' used around njs before. "NGINX JavaScript (njs)" is enough.

marked all the items that are in the draft already.
Missing some sections of the release news, the webassembly blog post, and the NJS examples that I can't figure out on my own.


Making TinyXML2 as static library in Visual Studio 2019

Hi,
I am using tinyxml1 in Visial Studio 2010 and have not problems till now. I want to create new tinyxml2 as a static library file in Visual Studio 2019. I am getting lot of linkage errors when using in application. Can someone suggest a best way of creating 2019 tiny xml as static library so that i can reuse in multiple places in my legacy project.
Thanks,
Sai

Or just include the tinyxml2.cpp/h files in a library somewhere. It really is only the 2 source files.


Fix ">" instead of ">" on "concepts" documentation page

On https://slack.dev/bolt-python/concepts at line 12 of "Example with AWS Lambda" there is ">" displayed, instead of ">" symbol. To fix this you have to remove ";" after it
Category (place an x in each of the [ ])

[ ] slack_bolt.App and/or its core components
[ ] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Adapters in slack_bolt.adapter
[x] Others

Hi @Globart1337, thanks for taking the time to report this issue. This may be due to the Jekyll rendering system. If anyone knows the way to properly resolve it, sharing the knowledge and/or sending a pull request fixing it would be appreciated.

@seratch what file is used to generate the page? I can try to fix it, if I know where it`s located

@Globart1337 The markdown files under docs directory are used for generating the website contents. If you are not familiar with GitHub Pages, please refer to their documents first.

Resolved by  #690


docs: remove references to signal-specific start functions

Continuation of https://github.com/signalfx/splunk-otel-js/pull/570/

Codecov Report
Base: 81.44% // Head: 81.52% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (8727b1d) compared to base (ddc63a8).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #577      +/-   ##
==========================================
+ Coverage   81.44%   81.52%   +0.08%
==========================================
  Files          28       28
  Lines        1110     1115       +5
  Branches      246      246
==========================================
+ Hits          904      909       +5
  Misses        206      206

Impacted Files
Coverage Δ

src/start.ts
100.00% <ø> (ø)

src/index.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Links to referenced documents don't work

Various links to documents referenced within the page take the form of assetid:///6cbee1b5-f6f6-443f-8fa9-31cc5c05a0ee which are not resolvable.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dcb3f5fb-6a88-cb57-78c0-963c78a394ca
Version Independent ID: 55d980df-e89d-615c-d1d3-d4ac2c0589fa
Content: Steps for Configuring the Test Lab
Content Source: WindowsServerDocs/remote/remote-access/directaccess/tlg-multisite/Steps-for-Configuring-the-Test-Lab-4.md
Product: windows-server
Technology: remote
GitHub Login: @eross-msft
Microsoft Alias: lizross

Hmm. Those assetid:/// links look like remnants from the old pre-GitHub Microsoft Docs platform. We should replace them with the current document filename links (note the Step 1 — 14 pages in the TOC list to the left of the page).

By the way, thank you for pointing out that issue. 👍🏻


Create dotnet-desktop.yml

This is an action, what builds here in github the develop branch.

Working :)


[BACKLOG-4393] Added bundle

Added bundle pentaho/pentaho-notification-webservice-bundle to feature
pentaho-data-profiling-ce-base

@brosander please review


Changed 3 line to allow for manual input of the scaling factor

I changed a few lines in RendererInterface and PNGRenderer, so it's now possible to override the default scale factor of 4, if desired, by stating it as a second parameter. That is all.
$renderer->render($code, 15);

Thank you for your PR. As other implementations of RendererInterface might not need a scale factor, I'd rather keep the interface as simple as possible and set the options in the constructor.
Please feel free to reopen if you want discuss this further.


Getting started with python plug-ins for GIMP

@kmwangi-ken
Do we have any updates?
If you still need more time, we can close this PR for now. You can still work on those changes, submit as a new PR, and ping me there.

@srishilesh, there are updates.  To be submitted soon

Hi @kmwangi-ken
Your article appears to have many sentences that are taken verbatim from third-party sources. We can't publish any content that is not original or properly cited/referenced. There are many free online tools where you can check this (such as quetext.com, and if you're uncertain about the definitions around plagiarism, this is a good resource to reference.
We're really looking for unique/original content.
Getting started with python plug-ins for GIMP Copyleaks Report.pdf

@kmwangi-ken
Do we have any updates?
Let me know if you need help creating a new PR


for arabic

for arabic case what changes need to be done ?

yourSegment.buttonTitles = "سعادة,مرحبا,يبتسم"
and you are good to go.

let me know if are still facing issues


Find better alternative for website search feature

Since switching to the new theme based on bokeh we are now relying on Google Custom Search Engine to search our website. This has benefits over the inbuilt Sphinx search, which ignores anything but the first keyword you give it, but it's also supported by ads which is kind of awful. If we can find a better alternative we should use it.

Low priority, tentatively assigning to 1.8.1.

Removing milestone, unlikely to happen anytime soon.

Closing, it works fine and I don't know of decent alternatives.


Timeline crashes in between condition and choice on End Branch event

The problem
Describe the bug
When I run timeline with specific event sequence. The timeline crashes with Invalid access to property or key 'current_event_idx' on a base object of type 'Nil'.
To Reproduce
Steps to reproduce the behavior:

create timeline

if false:
- choice

click on "Play timeline"

Expected behavior
Timeline runs and ends without error.
Screenshots

System (please complete the following information):

OS: Windows
Godot Version: 4.3
Dialogic Version: 2.0 Alpha 14

Solutions
Workaround
Add comment after condition where timeline crashes
if false:
# comment or text event
- choice

Possible fixes
No idea.

@Jowan-Spooner @Tetragramat
I was unable to reproduce this bug in the current main branch of Dialogic on Godot 4.3.

New project on Godot 4.3 with fresh download of Dialogic from https://github.com/dialogic-godot/dialogic/archive/refs/tags/2.0-alpha-14.zip
Reproduction:
https://github.com/user-attachments/assets/4bf3e70c-8f01-47b9-9a0d-7a7ddfb6600f

I think this should be fixed on main now. Feel free to test the main branch and let me know!

Hello i have a similar problem:

it crashes when i just enter a simple if with choice under it


Get rid of ColorManager

I read on one of the platform mailing lists that it's not needed, which is news to me.  Should take a glance at the platform implementations.

Turns out to still useful just as a widget-focused dedup.


WMS ID #11455 - Learn how to use RAFT Replication to build resilient distributed databases

Add here your WMS ID #11455 - Raft Replication workshop
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[X] All filenames are lower case (including folders, images, files, etc.)
[X] Filenames are descriptive
[X] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[X] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[X] Image references in markdown contain an alternate text

Hello Team,
I have made the requested changes and please find below the response inline:
•	In file and image names please replace all _ with - and make sure all characters are lowercase as per naming guidelines ----> Done
•	The help email in your manifest.json files needs to be<EMAIL_ADDRESS>to match your WMS stakeholder ---->Done
•	Per self QA guidelines, labs should not reference Always Free or Free Tier. Please remove these references from the intro and other md files -----> Removed from intro.md file but the md file for the "Get Started" section is coming from the common labs "https://oracle-livelabs.github.io/common/labs/cloud-login/cloud-login.md". We did not change any file from common labs.
Thanks.
Please let me know the next steps.

Hi @deekshasehgal
For the removing the free tier references from the other md files I'm referring to removing references such as in the prerequisites section of prepare-setup and initialize-environment such as below
This lab assumes you have:

An Oracle Free Tier or Paid Cloud account

The other changes look good. Thanks!

Hello @ZRTalke
I have made the requested changes in rest of the files too, before you approved the request. You must have seen the updates.
Removed "Free-tier and Paid Tenants"  from the files prepare-setup.md, initialize-environment.md and topology.md .
Thanks.


Upgrade dbt-presto to 0.15.2

Hi,
I've split this PR in 3 commits:

Simplify presto local environment
dbt docker container
Upgraded dbt-presto to 0.15.2

Simplify presto local environment
Changed the local presto environment to only test dbt against the memory connector. Since we can CREATE|DELETE|SELECT|DROP tables using the memory connector we can avoid having to deal with hadoop, hive and hive-metastore (and all its deployment complexities).
dbt docker container
Created a simple dbt docker container to test dbt-presto, this way we can isolate the dbt and python environments and re-create them easily. You can test this by running:
cd docker
./dbt/build.sh
./init.bash
./run_tests.bash
./remove.bash

Upgraded dbt-presto to 0.15.2
Changes in connections.py:

upgraded code to closely match the postgres connections.py
added authentication: username is now required and if method is ldap|kerberos then dbt-presto uses the user/password to authenticate to presto

Changes  in adapters.sql:

updated presto__reset_csv_table and presto__load_csv_rows
changed rename_relation to use from_relation.type: TABLE or VIEW

Let me know if there's any code change needed.

Thanks!
I've addressed your feedback.

I just finished some end-to-end testing of the changes proposed in this PR. Everything is looking good. I'm especially appreciative of the simplified approach to local testing via memory connector, which makes my life a lot easier :)
The only error I ran into related to switching model materializations between table and view. I think this is actually a bug in the default materializations, so I opened that here: https://github.com/fishtown-analytics/dbt/issues/2161.
It's related to the conversation in #9 and this change in the PR:

changed rename_relation to use from_relation.type: TABLE or VIEW

Given that the current version of dbt-presto runs alter table always, which doesn't ever work for views, the change in this PR is a definite improvement.

Doesn't this line: https://github.com/fishtown-analytics/dbt-presto/pull/10/commits/12a4d1ccf911c24dbc18ec6348f328374a5d6f98#diff-0db5a416656f30501e74db601031fa2eR89 addresses the view materializations?
I've ran our entire dbt pipeline with this version as a test and it ran fine.

That's right! Thanks to that line change, models materialized as views run just fine. They really don't in the current version of the plugin.
There is an error if I materialize a model as a view, run it, and then switch the materialization to table and re-run. I think that error is due to a line in the default materializations, not anything you've implemented in this PR.

@jtcohen6 can this be merged and dbt-presto on PyPi updated please? :)