Decrease scrape interval for FN plugin

Description of change
Scrape interval for metrics sent to FN ARC is now 5s. This is a step to unify metrics collected in Controller's Prometheus and those sent to FN ARC.
Checklist

[ ] Tested in playground or other setup
[x] Screenshot (Grafana) from playground added to PR for 15+ minute run
[x] Tests and/or benchmarks are included

Summary by OpenAI
New Feature:

Decreased scrape interval for metrics sent to FN ARC from 10s to 5s
Changed timeout for batch/metrics-slow processor from 5s to 4s
Added constants for batch timeout, send batch size, and send batch size max
Updated CircleCI configuration to include extensions directory
Removed BuildOTelScrapeConfig function call
Unified metrics collected in Controller's Prometheus and those sent to FN ARC

🎉 A faster pace we now embrace,
Metrics flow with newfound grace.
Constants set, configs refined,
CircleCI's watchful eye aligned.
Unifying metrics, we proceed,
To fulfill our users' every need. 🚀

@kwapik Do we still need this? I made some changes in my PR last week. See if those are satisfactory.

We won't go in this direction.


[vx.dev] implements #178

[vx.dev] This PR implements #178, created by vx.dev.

[vx.dev]: This Vue component creates a chat page with a left-right layout. The left side is a contact list, and the right side is a content window that displays chat content with a specific contact. The contact list is scrollable, and each contact has an avatar, name, and last message preview. The chat content window shows the selected contact's name, last seen status, and messages. Messages sent by the user have a different background color for distinction. If no contact is selected, a placeholder message is displayed.

[vx.dev]: This Vue code generates a chat page with a left-right layout. The left side is a contact list, and the right side is a content window that displays the chat content with a specific contact. The contact list is scrollable, and each contact has an avatar, name, and last message preview. The chat window shows the selected contact's name, last seen status, and messages. Messages sent by the user have a different background color for distinction. If no contact is selected, a prompt is displayed in the chat window.


should gracefully handle rate limits

Twitter returns 429 rate limit exceeded errors. The script should rest when one of those is returned.

should just use counter - having trouble capturing 429 errors when they are returned


Review the Rebrickable data set - Danvir

The data set used is from the Rebrickable website here Rebrickable Downloads. This issue has several steps to complete
Go to the downloads page above and identify the data files - we are interested only in the relational data and not the images. There should be 12 files, each of which ends with the file extension of '.gz'. Note the date of the files.
Download each of these files manually to your local machine.
Expand each file and review the data. You should look for the following things: header, number of columns, number of rows, types of data in the different columns, which columns are missing data
The download page has a model shown in a diagram. Review this given the data you've observed. When reviewing, consider mentally connecting theme, set, inventory, parts.
In this ticket, add several paragraphs about your observations which may include additional questions.

Elements Data:
number of columns: 89089, number of rows: 4, types of data in the different columns: Element id/ part number/ color id/ design id
Elements in Lego are used to refer to a specific piece/ part of Legos, for example an element id of 4566309 refers to a black boat anchor, with the data of 2564/0/2564. Initially, I was unsure of what design idea meant, but you explained it as different variations/versions of the same part. Some design ids missing, indicating some parts never received another variation/version.
Themes:
number of columns: 461, number of rows: 3, types of data in the different columns: Theme id/ name/ parent id
Themes are used to help categorize sets. The id and name are self-explanatory, but the parent id is used if there is already a broader theme category that the theme could be included in. For example, Racers and Ferrari are two separate themes but Ferrari has the parent id of Racer as Ferrari could also be listed under Racer and Racer has no parent id as there is no such existing broader theme it could be listed under.
Color:
number of columns: 268, number of rows: 4, types of data in the different columns: color id/color name/ color on RGB/ translucent
The way color is categorized in Lego is by an id. In the case of black the data would look like 0/Black/ 05131D/false.
Parts categories:
number of columns: 69, number of rows: 2, types of data in the different columns: id/name
Part categories are used to categorize parts based on their properties, for example all bricks fall under the category of 11 no matter their size or color, so the data in this case would be 11/brick.
Parts:
number of columns: 54498, number of rows: 4, types of data in the different columns: part number/ name/ part category/ part material
Similar to elements each part has its unique data.  For example, a 1 by 2 brick has the data of 11211pr0001 /1 x 2 brick/11/plastic.
Parts relationships:
number of columns: 30989, number of rows: 3, types of data in the different columns: relationship type/child part/ parent part
Parts grouped together based on relationships and similarities but not close enough to be considered in the same category. For an example we can look at R/98653pr0003/98086pr0003, the parent part being the head of a pterodactyl and the child part being the body. Both parts of different category but hold similarities, however I was unable to determine how relationship type is chosen.
Sets:
number of columns: 22680, number of rows: 6, types of data in the different columns: set number/ name/ year/ theme/ number of parts/ URL of image
Minifigs:
number of columns: 14356, number of rows: 4, types of data in the different columns: fig number/ name/ number of parts/URL
Inventories:
number of columns: 38738, number of rows: 3, types of data in the different columns: id/version/ set number
Inventories are the versions of a Lego set.
Inventory minifigs:
number of columns: 21804, number of rows: 4, types of data in the different columns: inventory/set by Inventory / fig number/ quantity of figs
Inventory minifigs are used to determine the number of mini figures in the set.
Inventory parts:
number of columns: 1048576, number of rows: 6, types of data in the different columns: inventory/ part number/ color id/ quantity/ spare/ URL
The Inventory parts gives a detailed overview of each piece in the inventory.  A few image URLs are missing, which I find odd as no other data sheet has missing URLs.
Inventory sets:
number of columns: 4432, number of rows: 3, types of data in the different columns: inventory/set number/ quantity
Total number of versions each set has.
Reviewing model:
Reviewing the model/diagram after analyzing the data, I realize it resembles a node graph and the data is interconnected. What I mean by this is each node has data from another node, for example the set node uses data from themes, while the inventory and inventory set nodes both use data from the set node. Additionally, we can see that parts and inventory are connected through the middleman of inventory parts, which uses both inventory and parts in its data. Some other observations are that the graph is a bit outdated as the node Element does not have a data row for design idea, unlike the data charts. Finally, I noticed that some nodes had a specific id for specific data sets (consisting of Inventories, Minifigs, Sets, Parts, Parts categories, Color, Elements, themes ) while others were blank (consisting of Inventory sets, Inventory parts,  Inventory minifigs, Parts relationships) the correlation was that the one with specific ids were used as data in other nodes except for element and the ones that were blank were stand alone and not used for data.


feature request: bindable property to set CalendarWeekRule

XamForms.Controls.Calendar/Calendar.NumberOfWeek.cs

var weekNum = ciCurr.Calendar.GetWeekOfYear(start, CalendarWeekRule.FirstFourDayWeek, StartDay);

The week labels are set by default to CalendarWeekRule.FirstFourDayWeek.
I couldn't find a way to set the calenderweekrule to first full week.

Added Bindable property CalendarWeekRule in version 1.0.8


Original font is not mantained when a form is filled

What were you trying to do?
I'm using the acroform's fields to fill an existing PDF module.
The resulting module looses the original font of the module and gets Helvetica.
How did you attempt to do it?
field.setText();
What actually happened?
The resulting module looses the original font of the module and gets Helvetica.
What did you expect to happen?
The field keeps its original font.
Also I'm unable to retrieve the used font from any available API.
How can we reproduce the issue?
I use LibreOffice to create a module, assign a different font and create the PDF.
Also tried to modify the PDF with acrobat and altering the font again, with no luck.
You can see the PDF here: https://github.com/gioppoluca/sheet-export/blob/master/mappings/dnd5e/experimental/latest/5e-model.pdf
Version
1.17.1
What environment are you running pdf-lib in?
Browser
Checklist

[X] My report includes a Short, Self Contained, Correct (Compilable) Example.
[X] I have attached all PDFs, images, and other files needed to run my SSCCE.

Additional Notes
Is there an API to retrieve the original font used?

I encountered the same issue and found following solution when the font was previously embedded using pdf-lib. See also my comment here.
// Get embedded font using code from above comment
field.setText(newText);
field.updateAppearances(font);


Reduced-bloat packaging for npm & webpack

Reduced-bloat packaging for npm & webpack
react-datepicker's npm module has a main file
./dist/react-datepicker.min.js. This file is built by webpack, so it
inlines both classnames and react-tether dependencies.
The classnames and react-tether dependencies in package.json are
hence unused by consumers of react-datepicker. Right now they'd be
more appropriate in devDependencies. But this commit proposes another
solution.
I'm using react-datepicker with npm, and importing via webpack. My app
also uses classnames, and could presumably use react-tether too. But
since these react-datepicker dependencies are inlined, they cannot be
shared with the host application, despite being present in package.json.
This commit proposes that the main file for distribution via npm is
./lib/datepicker.js, compiled by Babel, but not webpack. This allows
users of react-datepicker to share the same version of classnames
and react-tether with react-datepicker.

Current coverage is 94.84%

Merging #404 into master will not affect coverage as of 43b721a

@@            master    #404   diff @@
======================================
  Files            9       9
  Stmts          194     194
  Branches        42      42
  Methods         88      88
======================================
  Hit            184     184
  Partial          2       2
  Missed           8       8

Review entire Coverage Diff as of 43b721a

Powered by Codecov. Updated on successful CI builds.

Hey @dmnd, thanks for putting this together -- this is a change I've been wanting to make for a while.  Summarizing my main feedback:

I think we should git-ignore the lib directory and have it built as part of the prepublish hook
Let's wait to make the API break (i.e. including lib instead of dist) until v1.0

Once those are addressed I think this should be good to go.

I think we should git-ignore the lib directory and have it built as part of the prepublish hook

I can understand that, but it does have one small downside:
When making a PR to a third party library I'm using, I change my application's package.json to depend on my PR instead of the published npm module. This lets me fix bugs I hit and not have to wait for other people to merge my changes, which I think makes me more likely to send fixes upstream.
As far as I understand, this workflow isn't possible if there are files in the npm module that are not part of the git repository. So while it's nice to not have built files checked into git, it does have a small advantage for consumers of the library. Unless there's some other easy way to depend on a PR that I'm unaware of.
That said, I'm happy to change this PR if you don't agree this benefit is worthwhile for your library.

We made the decision a while ago to not include built scripts in the repo =) tl;dr they're a maintenance burden and pollute PRs and diffs (more on #303)
For the case you mentioned, npm runs the prepublish hook after install, which I think is for this exact use case.  Hopefully that would work for your case of wanting to use fixes immediately and not wait for a merge and release.

Ok, removed ./lib from the repo and switched to grunt. Let me know if there's anything else blocking a merge.

Awesome -- LGTM, but I'd like @martijnrusschen to take a look before we merge

Since, we're excluding /lib in .git now, does this actually change something on how we serve files in our package? Looks like the initial description of the PR is different from the actual implementation now.

Right now this only adds to the files that we publish in the package, allowing access to the "raw" JS files without the bundled dependencies, and letting the consumer's module bundler take care of the dependencies.  For v1.0 I think we shouldn't publish our current dist build and only publish lib since module bundlers are so standard now.

SGTM

Thanks for the work here @dmnd!

No worries. Any chance I could get a release? After some investigation, depending on git repos that need a build step is pretty broken. See https://github.com/npm/npm/issues/3055


readme: split "Related Links" into projects/slides

Fixes #173.
cc @philips

I'd argue that we would remove PA3oBAgjnkU as its content became highly out-of-date. There's however the Apprendra meetup (https://www.youtube.com/watch?v=wTfCOUDNV_M / https://docs.google.com/presentation/d/1ly9wQKQIlI7rlb0JNU1_P-rPDHU4xdRCCM3rxOdjcgc/edit#slide=id.g110c4ca1b8_1_1) that we can add.

LGTM

LGTM


inafut.com NSFW

Domain
https://www.niihen.com/2021/11/yamitsuki-pheromone.html
Link
https://www.inafut.com/p/ads.html?download=YUhSMGNITTZMeTkzZDNjdWJXbHljbTl5WldRdWRHOHZabWxzWlhNdk1VeFFUMEpKUlVzdlcwNWxhMjlRYjJsZFgxbGhiV2wwYzNWcmFWOVFhR1Z5YjIxdmJtVmZWR2hsWDBGdWFXMWhkR2x2Ymw4dFh6QXlYMXMzTWpCUVhWdHVaV3R2Y0c5cExtTmhjbVZkTG0xd05GOXNhVzVyY3c9PQ==
Version
0.0.0
What browsers are you seeing the problem on?
Firefox, Chrome
What OS are you seeing the problem on?
Windows
(Optional) Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

inafut seems to be a non existing site anymore?


Packet Processing error when initiating Dragon Battle/Placing end crystal

Describe the bug
When placing an end crystal *ONLY in the end, it will crash the user and send an error to the console
To Reproduce
Teleport to end world, ensure dragon is ALREADY dead, and place an end crystal anywhere
Screenshots or Videos
Video of the Crash can be found here
Error in console: https://paste.dedimc.io/ewolaqifus.css
Plugins
[REDACTED]
Version
Purpur 1085, 1.16.5
Java 11
Is bug present on Paper, Spigot, CraftBukkit, or Vanilla
Be sure you test the upstream projects for this bug and include if it is present or not here, include /version output for each upstream project you tested.
TESTED PAPER 651, WORKS PERFECTLY FINE, NO BUG
TESTED TUINITY b12d0cc (255) WORKS PERFECTLY FINE, NO BUG
Additional context
Add any other context about the problem here you think will help resolve the problem.

My issue turned out to be MC-104897 which is now fixed (in 1.17). I tested my world in vanilla 1.17-pre1 and the dragon did respawn properly, so I expect this will also work in Purpur when the full release comes.


Lack of maintainment

Hi,
as some of you might already concluded, I won't further maintain this package any more, because I don't have the time, I no longer use K8S privately and I am no longer a Gandi customer. I plan to set this repository to read-only and I will include a link in the readme to a repo of someone who is willing to maintain a fork.
What do you think and is there someone who is able to maintain the package to whom I can link in the readme? I also suggest that you update the cert-manager documentation (PR) to refer to the update-to-date repo.
Cheers!

We're actively working on a fork of this that might be a bit more opinionated. We use Gandi to do challenges in our multi-tenant environment, and thus will add features around that use-case.
If there's any interest, it can be found here: https://github.com/molnett/cert-manager-webhook-gandi


How to configure dependencyFilter in .madgerc

Configuration files (e.g. .appnamerc) may be in either json or ini format.

Looks like rc doesn't support JS functions. See rc document.

This doesn't appear to work via package.json configuration either. If this is intentional, the documentation could make this clearer by stating certain options are meant for use in the madge() JavaScript API rather than the CLI.

I noticed this as well while trying to merge this PR

#282

I think we might need a new way to apply dependencyFilter.
Further discussion about this will happen in #282, while trying to solve this issue with the same PR.


add profession column to profiles

@tyranja I've made those changes. Am not sure if anything else is required...

To do before merge:

[ ] limitation 80 chars ?
[ ] add it in the profile form ( Anja? )
[ ] add it to the profile show view under the title  ( Anja? )


More debugger functionality (deadlock detection, single-stepping, complex breakpoints conditions, etc)

Two high-level comments on the changes in examples:

We don't check in .yalc files; probably got added by mistake?  In any case, please remove.
The ykt example failed in several of the test runs.  I tried re-executing them, but it might be expedient to drop the changes to ykt.js from this PR and try it in a PR just by itself.

Re-execution of the failing jobs yielded the same failures in ykt test scenarios.  Definitely try removing the changes to ykt.js to rule that out as the cause.


type aliasing maybe types leads to unsafe code

Repro
type Maybe<A> = ?A;
declare function g<A>(f: () => Maybe<A>): Maybe<A>;
declare function f(): Maybe<number>;

(g(f): Maybe<string>); // <= no error but should
(g(f): Maybe<{}>); // <= no error but should
(g(f): Maybe<Array<boolean>>); // <= no error but should

Either changing the Maybe deifnition to
type Maybe<A> = null | void | A;

or changing the g definition to
declare function g<A>(f: () => ?A): Maybe<A>;

raises the expected errors

But, type Maybe<A> = A is also broken

Seems to be fixed


Connecting to the server = timed out

Good evening. I have this weird problem that whenever I try to connect to my server I get timed out, and if I don't, I spawn in an absolutely empty world, and THEN get timed out after a few seconds. And the only thing I have to connect it to is RFTools exchanging its dim info.
http://pastebin.com/cibLtbGZ
If the full log is needed, I can upload it to somewhere.

I see nothing in this log indicating rftools at all. So I doubt this has something to do with rftools. If you find any further information that indicates that it is rftools then feel free to reopen this

I'm not sure how this is realted, but on my server when i update buildcraft and its add-ons to more current release my server timeouts anyone who tries to join, oddly enough when I remove rftools the timeouts stop. Not sure why it causes rftools to make them happen, but removing it fixes it so that has to mean something, either its directly causing it or doing some asm reflexive magic messing with buildcraft stuff, will upload logs when I get the chance


Browser validations break save on persisted objects with images

Let's say we have a model with an image
class Player < ActiveRecord::Base
  mount_uploader :image, ImageUploader

  validates :name, presence: true
  validates :image, presence: true
end

Saving a new object or editing the image is fine

but when you try to save a persisted model without editing the image, you get a validation error on the file upload field

Refers to #2339 #2373

Merged #2373.

btw this is still an issue with browser validations activated (default behaviour)
This should be reopened

Fixed now, thanks!

:+1: Thanks!

thanks and sorry for not submitting a PR myself


iterate on jax.hessian docs

Follow up on #2705.

@hawkinsp heads up I pushed a couple successive commits here, might need to refresh to see the latest.


Disabling telemetry has no effect

Bug description
I have set the environment variables and confirmed they are present in the container (see below) yet the logs show prisma continuously attempting to phone home:
docker-compose.yml:
    environment:
      ...
      DISABLE_PRISMA_TELEMETRY: true
      CHECKPOINT_DISABLE: 1
      ...

in the container:
/ # env | grep -E DISABLE
DISABLE_PRISMA_TELEMETRY=true
CHECKPOINT_DISABLE=1
/ #

logs:
...
2024-02-09 13:10:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:11:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:12:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:13:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:14:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:15:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:16:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:17:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:18:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.
2024-02-09 13:19:28 [Telemetry] Warning: Telemetry call failed with akka.stream.StreamTcpException: Connection failed.

How to reproduce
Run Prisma with environment variables set as specified to disable telemetry and check stdout or docker logs.
Expected behavior
No communication whatsoever with any host except in response to workload requests
Prisma information

// not relevant (empty)

// none

Environment & setup

OS: NA/Docker prismagraphql/prisma:1.34.10
Database: MariaDB
Node.js version: N/A

Prisma Version
prisma CLI is irrelevant - this is a server issue.

Hi @Mugane, thanks for opening this issue.
Unfortunately, Prisma 1 is no longer supported.
This repository hosts the source code for Prisma 5 (npm, docs).
I would recommend evaluating our version migration guide, starting with Prisma 1 to Prisma 2. Thanks!


Building a snap with snapcraft.yaml

I have been trying to create a snap for 2 weeks now, but it still doesn't work
Today I managed to finally make the app run and load HTML in the webview, but the Blazor won't load.
All I see is the HTML / CSS loader spinner that spins indefinitely
Do you know how to make it work?
Below are the snapcraft.yaml and the console output
name: openhabittracker
version: '1.0.0'
grade: devel
summary: Take notes, plan tasks, track habits
description: |
  - Free and Ad-Free
  - Open Source
  - Privacy Focused: All user data is stored locally on your device
  - Available on Windows, Linux, Android, iOS, macOS, and as a web app
  - Localized to English, German, Spanish, Slovenian

  Key Features:

  - Markdown support for notes
  - Use categories and priorities to organize your notes, tasks, and habits
  - Advanced Search, Filter, and Sort
  - Data Export/Import: JSON, YAML, TSV, Markdown
  - Import your notes from Google Keep
  - Available in 26 themes with Dark and Light modes

base: core22

confinement: devmode

layout:
  /usr/lib/$SNAPCRAFT_ARCH_TRIPLET/webkit2gtk-4.0:
    bind: $SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/webkit2gtk-4.0
#  /usr/lib/$SNAPCRAFT_ARCH_TRIPLET/webkit2gtk-4.1:
#    bind: $SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/webkit2gtk-4.1

parts:
  openhabittracker:
    plugin: dotnet
    dotnet-build-configuration: Release
    dotnet-self-contained-runtime-identifier: linux-x64
    source: .
    override-build: |
     dotnet build OpenHabitTracker.Blazor.Photino/OpenHabitTracker.Blazor.Photino.csproj -c Release
     dotnet publish OpenHabitTracker.Blazor.Photino/OpenHabitTracker.Blazor.Photino.csproj -r linux-x64 -c Release -p:PublishSingleFile=true --self-contained true -f net8.0 -o $SNAPCRAFT_PART_INSTALL
     chmod 0755 $SNAPCRAFT_PART_INSTALL/OpenHT
    build-packages:
      #- libwebkit2gtk-4.1-dev
      - dotnet-sdk-8.0
    stage-packages:
      #- libwebkit2gtk-4.1-0
      - libwebkit2gtk-4.0-37
      - libnotify4
      - libicu70
      - libglu1-mesa
      - freeglut3
      - libwebkit2gtk-4.0-dev
      - webkit2gtk-driver
      - libcanberra-gtk3-module
      - libcanberra-gtk-module
      - libgl1-mesa-dri
      - mesa-vulkan-drivers
      - libgbm1
      - libglx-mesa0

apps:
  openhabittracker:
    command: OpenHT
    plugs:
      - opengl
      - hardware-observe
    environment:
      LIBGL_DRIVERS_PATH: $SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/dri
      LD_LIBRARY_PATH: $LD_LIBRARY_PATH:$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/dri

console:
urban@urban-VirtualBox:~/Jinjinov/OpenHabitTracker$ snap run openhabittracker
Photino.NET: "Photino".SetTitle(Photino.Blazor App)
Photino.NET: "Photino.Blazor App".SetUseOsDefaultSize(False)
Photino.NET: "Photino.Blazor App".SetUseOsDefaultLocation(False)
Photino.NET: "Photino.Blazor App".SetWidth(1000)
Photino.NET: "Photino.Blazor App".SetHeight(900)
Photino.NET: "Photino.Blazor App".SetLeft(0)
Photino.NET: "Photino.Blazor App".SetTop(100)
Photino.NET: "Photino.Blazor App".SetTitle(OpenHabitTracker)
Photino.NET: "OpenHabitTracker".SetUseOsDefaultSize(False)
Photino.NET: "OpenHabitTracker".SetSize(1680, 1050)
Photino.NET: "OpenHabitTracker".SetUseOsDefaultLocation(False)
Photino.NET: "OpenHabitTracker".SetTop(0)
Photino.NET: "OpenHabitTracker".SetLeft(450)
Photino.NET: "OpenHabitTracker".Load(/)
Photino.NET: "OpenHabitTracker" ** File "/" could not be found.

VMware: No 3D enabled (0, Success).
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["BeginInvokeJS",2,"Blazor._internal.attachWebRendererInterop","[3,{\u0022__dotNetObject\u0022:1},{},{}]",3,0])
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["AttachToDocument",0,"app"])
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["BeginInvokeJS",3,"import","[\u0022./_content/OpenHabitTracker.Blazor/jsInterop.js\u0022]",1,0])
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["RenderBatch",1,"AAAAAAEAAAABAAAAAAAAAAAAAAD/////AQAAAAEAAAABAAAAAAAAAAUAAAD/////AgAAAAEAAAABAAAAAAAAAAgAAAD/////AwAAAAEAAAABAAAAAAAAAAsAAAD/////BAAAAAMAAAABAAAAAAAAAA0AAAD/////AQAAAAEAAAAnAAAA/////wEAAAACAAAAKAAAAP////8FAAAAAQAAAAEAAAAAAAAAKQAAAP////8GAAAAAQAAAAEAAAAAAAAALwAAAP////8HAAAAAQAAAAEAAAAAAAAANQAAAP////8IAAAAAAAAABgAAAAwAAAASAAAAGAAAACYAAAAsAAAAMgAAAA7AAAABAAAAAUAAAABAAAAAAAAAAAAAAADAAAAAAAAAP////8AAAAAAAAAAAMAAAABAAAA/////wAAAAAAAAAAAwAAAAIAAAD/////AAAAAAAAAAADAAAAAwAAAP////8AAAAAAAAAAAQAAAADAAAAAgAAAAAAAAAAAAAAAwAAAAQAAAD/////AAAAAAAAAAADAAAABQAAAP////8AAAAAAAAAAAQAAAADAAAAAwAAAAAAAAAAAAAAAwAAAAYAAAD/////AAAAAAAAAAADAAAABwAAAP////8AAAAAAAAAAAQAAAACAAAABAAAAAAAAAAAAAAAAwAAAAgAAAD/////AAAAAAAAAAABAAAAGgAAAAkAAAAAAAAAAAAAAAMAAAAKAAAACwAAAAAAAAAAAAAAAQAAABgAAAAJAAAAAAAAAAAAAAADAAAACgAAAAwAAAAAAAAAAAAAAAEAAAAWAAAACQAAAAAAAAAAAAAAAwAAAAoAAAANAAAAAAAAAAAAAAABAAAABQAAAA4AAAAAAAAAAAAAAAMAAAAKAAAADwAAAAAAAAAAAAAAAwAAABAAAAD/////AQAAAAAAAAAIAAAAEQAAAAAAAAAAAAAAAAAAAAIAAAASAAAAAAAAAAAAAAAAAAAACAAAABMAAAAAAAAAAAAAAAAAAAAEAAAABAAAAAUAAAAAAAAAAAAAAAMAAAAKAAAAFAAAAAAAAAAAAAAAAwAAABUAAAAWAAAAAAAAAAAAAAADAAAABwAAAP////8AAAAAAAAAAAgAAAAXAAAAAAAAAAAAAAAAAAAABAAAAAQAAAAGAAAAAAAAAAAAAAADAAAACgAAABgAAAAAAAAAAAAAAAMAAAAVAAAAGQAAAAAAAAAAAAAAAwAAAAcAAAD/////AAAAAAAAAAAIAAAAGgAAAAAAAAAAAAAAAAAAAAQAAAAEAAAABwAAAAAAAAAAAAAAAwAAAAoAAAAbAAAAAAAAAAAAAAADAAAAFQAAABwAAAAAAAAAAAAAAAMAAAAHAAAA/////wAAAAAAAAAACAAAAB0AAAAAAAAAAAAAAAAAAAAIAAAAHgAAAAAAAAAAAAAAAAAAAAEAAAAGAAAAHwAAAAAAAAAAAAAAAwAAABUAAAAgAAAAAAAAAAAAAAADAAAACgAAACEAAAAAAAAAAAAAAAUAAAADAAAAAAAAAAAAAAAAAAAACAAAACIAAAAAAAAAAAAAAAAAAAACAAAAIwAAAAAAAAAAAAAAAAAAAAEAAAAGAAAAHwAAAAAAAAAAAAAAAwAAABUAAAAkAAAAAAAAAAAAAAADAAAACgAAACUAAAAAAAAAAAAAAAUAAAADAAAAAAAAAAAAAAAAAAAACAAAACYAAAAAAAAAAAAAAAAAAAACAAAAJwAAAAAAAAAAAAAAAAAAAAEAAAAGAAAAHwAAAAAAAAAAAAAAAwAAABUAAAAoAAAAAAAAAAAAAAADAAAACgAAACkAAAAAAAAAAAAAAAUAAAADAAAAAAAAAAAAAAAAAAAACAAAACoAAAAAAAAAAAAAAAAAAAACAAAAKwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0FwcEFzc2VtYmx5FEFkZGl0aW9uYWxBc3NlbWJsaWVzBUZvdW5kCE5vdEZvdW5kCVJvdXRlRGF0YQ1EZWZhdWx0TGF5b3V0BkxheW91dAxDaGlsZENvbnRlbnQEQm9keQNkaXYFY2xhc3NAY29udGFpbmVyLWZsdWlkIGQtZmxleCBmbGV4LWNvbHVtbiB2aC0xMDAgbWgtMTAwIG92ZXJmbG93LWhpZGRlbhFyb3cgZmxleC1zaHJpbmstMS9jb2wgYmctYm9keS1zZWNvbmRhcnkgZC1mbGV4IGFsaWduLWl0ZW1zLWNlbnRlcgZidXR0b24SbmF2LWxpbmsgcHgtMSBweS0yB29uY2xpY2sbPGkgY2xhc3M9ImJpIGJpLWxpc3QiPjwvaT4gBE1lbnUPCgoKICAgICAgICAgICAgF25hdi1saW5rIHB4LTEgcHktMiBtcy0yBGhyZWYFbm90ZXMNCiAgICAgICAgICAgIBduYXYtbGluayBweC0xIHB5LTIgbXMtMgV0YXNrcw0KICAgICAgICAgICAgF25hdi1saW5rIHB4LTEgcHktMiBtcy0yBmhhYml0cwIKCosBPGRpdiBpZD0iYmxhem9yLWVycm9yLXVpIj4KICAgIEFuIHVuaGFuZGxlZCBlcnJvciBoYXMgb2NjdXJyZWQuCiAgICA8YSBocmVmIGNsYXNzPSJyZWxvYWQiPlJlbG9hZDwvYT4KICAgIDxhIGNsYXNzPSJkaXNtaXNzIj7wn5eZPC9hPjwvZGl2PgFhBW5vdGVzF25hdi1saW5rIHB4LTEgcHktMiBtcy0yIDxpIGNsYXNzPSJiaSBiaS1jYXJkLXRleHQiPjwvaT4gBU5vdGVzBXRhc2tzF25hdi1saW5rIHB4LTEgcHktMiBtcy0yJTxpIGNsYXNzPSJiaSBiaS1jYXJkLWNoZWNrbGlzdCI\u002BPC9pPiAFVGFza3MGaGFiaXRzF25hdi1saW5rIHB4LTEgcHktMiBtcy0yIDxpIGNsYXNzPSJiaSBiaS1jYXJkLWxpc3QiPjwvaT4gBkhhYml0c6wFAAC4BQAAzQUAANMFAADcBQAA5gUAAPQFAAD7BQAACAYAAA0GAAARBgAAFwYAAFgGAABqBgAAmgYAAKEGAAC0BgAAvAYAANgGAADdBgAA7QYAAAUHAAAKBwAAEAcAAB4HAAA2BwAAPAcAAEoHAABiBwAAaQcAAGwHAAD5BwAA\u002BwcAAAEIAAAZCAAAOggAAEAIAABGCAAAXggAAIQIAACKCAAAkQgAAKkIAADKCAAA4AAAAAQBAACkBQAAqAUAANEIAAA="])
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["AttachToDocument",8,"head::after"])
Photino.NET: "OpenHabitTracker".SendWebMessage(__bwv:["RenderBatch",2,"CAAAAAIAAAABAAAAAAAAAAAAAAD/////AQAAAAEAAAACAAAA/////wkAAAABAAAAAQAAAAAAAAAEAAAA/////wkAAAAAAAAACgAAAAEAAAABAAAAAAAAAAYAAAD/////CgAAAAAAAAALAAAAAAAAAAsAAAAAAAAADAAAAAAAAAAMAAAAAAAAAAkAAAAAAAAAKAAAAEAAAABIAAAAYAAAAGgAAABwAAAAeAAAAIAAAAAIAAAABAAAAAIAAAAJAAAAAAAAAAAAAAADAAAAAAAAAP////8AAAAAAAAAAAQAAAACAAAACgAAAAAAAAAAAAAAAwAAAAAAAAD/////AAAAAAAAAAAEAAAAAgAAAAsAAAAAAAAAAAAAAAMAAAABAAAA/////wAAAAAAAAAABAAAAAIAAAAMAAAAAAAAAAAAAAADAAAAAQAAAP////8AAAAAAAAAAAAAAAAAAAAACVNlY3Rpb25JZAdjb250ZW50XAEAAGYBAACIAAAAsAAAAFQBAABYAQAAbgEAAA=="])
urban@urban-VirtualBox:~/Jinjinov/OpenHabitTracker$

@Jinjinov I am not familiar with creating Snap packages tbh. Perhaps the publishing guide can help you figure it out?
https://github.com/tryphotino/photino.Samples/tree/master/Photino.PublishPhotino/PublishPhotino#universal-packaging-with-flatpak

I successfully published a Snap: https://snapcraft.io/openhabittracker
I used extensions: [gnome] that adds all needed libraries instead of manually adding them myself.
The config is much shorter now:
name: openhabittracker
title: OpenHabitTracker
icon: net.openhabittracker.OpenHabitTracker.svg
website: https://openhabittracker.net
source-code: https://github.com/Jinjinov/OpenHabitTracker
issues: https://github.com/Jinjinov/OpenHabitTracker/issues
license: GPL-3.0
version: '1.0.0'
grade: stable #devel
summary: Take notes, plan tasks, track habits
description: |
  - Free and Ad-Free
  - Open Source
  - Privacy Focused: All user data is stored locally on your device
  - Available on Windows, Linux, Android, iOS, macOS, and as a web app
  - Localized to English, German, Spanish, Slovenian

  Key Features:

  - Markdown support for notes
  - Use categories and priorities to organize your notes, tasks, and habits
  - Advanced Search, Filter, and Sort
  - Data Export/Import: JSON, YAML, TSV, Markdown
  - Import your notes from Google Keep
  - Available in 26 themes with Dark and Light modes

base: core22

confinement: strict #devmode

parts:
  openhabittracker:
    plugin: dotnet
    dotnet-build-configuration: Release
    dotnet-self-contained-runtime-identifier: linux-x64
    source: .
    override-build: |
     dotnet publish OpenHabitTracker.Blazor.Photino/OpenHabitTracker.Blazor.Photino.csproj -r linux-x64 -c Release -p:PublishSingleFile=true --self-contained true -f net8.0 -o $SNAPCRAFT_PART_INSTALL
     chmod 0755 $SNAPCRAFT_PART_INSTALL/OpenHT
    build-packages:
      - dotnet-sdk-8.0

apps:
  openhabittracker:
    extensions: [gnome]
    command: OpenHT
    plugs:
      - hardware-observe
      - home
      - removable-media
      - network


[Lesson Page] Render Challenge Diff

Use react-diff-viewer to render the submission diff on each challenge
Closes #111

Why there is no Storybook with <ReactDiffViewer />?
Did you forget to include it?

Do we have to add StoryBook for 3rd-party components?

It's not about 3rd-party components but to have an idea on how it's look. 🙂
You know your code and it's look & feel. As reviewer sometimes it's difficult to have an idea just with the code.
That why we have StoryBook with page folder or even a screenshot of your work would be fine for me.


Add formatting option to dashboard tables so that text can be turned into a hyperlink

An expression could be used to create the link text and the link could open another dashboard with parameters or an external resource.

Delivered


Merge prTesting_201902030848 branch to master branch

OPS Build status updates of commit f6f0605:
:clock10: Preparing: average preparing time is 48 sec(s)

OPS Build status updates of commit f6f0605:
:clock10: Incremental building: average incremental building time is 15 sec(s)

OPS Build status updates of commit f6f0605:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: support Chunk.groupsIterable and ChunkGroup.getParents

This PR aims to address issue #3896 by exclusively using u32 in JsChunkGroup::parents and JsChunk::groups, thereby reducing overhead.

!canary

!canary

!canary

need chunkGroup.name


Cannot remove notes from slack

When a note is placed on slack for some reason it cannot be deleted.

The notes could be deleted after I reloaded the page

This seems to have been fixed. Closing


What Errors are termed Critical when DeploymentMode set to production

[Enter feedback here]
https://docs.microsoft.com/en-us/azure/active-directory-b2c/troubleshoot-with-application-insights Document says
Use the following configuration to send only critical error messages to your Application Insights.
Set the DeploymentMode attribute of the TrustFrameworkPolicy to Production.
it will be good to have examples on what Errors are deemed critical.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bdca08d8-4a1d-f11c-9e3e-6627ea0f18bc
Version Independent ID: 6bb42537-50b2-2af1-fdf7-86b76ed9afe6
Content: Troubleshoot custom policies with Application Insights - Azure AD B2C
Content Source: articles/active-directory-b2c/troubleshoot-with-application-insights.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@tusharkadev
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@JamesTran-MSFT any update?

@tusharkadev
Thank you for the follow up on this!
Adding the author @msmimart to share any updates on this request.


Bug: allocating coarrays at the team level

Avg response time

Defect/Bug Report

OpenCoarrays Version: 2.0.0
Fortran Compiler: GNU Fortran (GCC) 9.0.0 20180506 (experimental)
C compiler used for building lib: gcc (GCC) 9.0.0 20180506 (experimental)
Installation method: install.sh
Output of uname -a: Linux 3.13.0-147-generic #196-Ubuntu SMP Wed May 2 15:51:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
MPI library being used: MPICH 3.2.1
Machine architecture and number of physical cores: laptop computer, 4 cores
Version of CMake: 3.4.0

Observed Behavior
When trying to allocate an allocatable coarray on the images of a specific team only, that allocate statement does not only synchronize with the (same) allocate statement on the images of that team, but instead does (try to) synchronize with (any) allocate statement(s) on the images of any other team as well. This may prevent from independent code execution on the images of a specific team in the presence of an allocatable coarray.
See the following code example: There are two allocate statements (the second one being out commented) in the code execution parts of the subteams. Each allocate statement does allocate another coarray in other teams each. With only the first allocate statement active in the code, program execution does hang (assuming that the allocate statement does try to synchronize with allocate statements outside that team, which do not exist). On the other side, with both allocate statements being active, runtime execution does complete successfully, even if the both allocate statements do allocate two distinct coarrays on the teams.
program Main
! please compile and run with 15 coarray images
  !
  use,intrinsic :: ISO_FORTRAN_ENV, only: team_type
  implicit none
  !
  integer, codimension[:], save, allocatable :: intAllocatableCoarray1
  integer, codimension[:], save, allocatable :: intAllocatableCoarray2
  !
  integer :: intTeamNumber
  type (team_type) :: MainTeam
  type (team_type) :: SubTeam
  !
!
!************************************************
! MainTeam **************************************
!************************************************
!
! split the 15 images of the initial team into 3 child teams consisting of 5 images each:
  if (this_image() <= 5) then
    intTeamNumber = 1
  else if (this_image() >= 6 .and. this_image() <= 10) then
    intTeamNumber = 2
  else if (this_image() >= 11) then
    intTeamNumber = 3
  end if
  !
form team (intTeamNumber, MainTeam) ! this creates the 3 child teams in MainTeam
!
change team (MainTeam)
!
!************************************************
! SubTeam ***************************************
!************************************************
!
! split the 5 images of the MainTeam's child teams into two distinct teams resp.:
  if (this_image() < 3) then
    intTeamNumber = 1
  else
    intTeamNumber = 2
  end if
!
form team (intTeamNumber, SubTeam) ! this generates 6 teams (2 new sub teams in the 3 main teams resp.)
                                   ! within the change team (MainTeam) construct
change team (SubTeam)
!
SubTeam_select: select case (team_number())
!
case (1) SubTeam_select
  ! codes for child team 1 of SubTeam:
  allocate (intAllocatableCoarray1[*])
  !
  write(*,*) 'image number: ', this_image(), ' of team number: ', team_number(), &
             ' in SubTeam, of MainTeam''s child team number:'
  !
!*******************
case (2) SubTeam_select
  ! codes for child team 2 of SubTeam:
!  allocate (intAllocatableCoarray2[*]) ! without this allocate statement runtime execution will hang
  !
  write(*,*) 'image number: ', this_image(), ' of team number: ', team_number(), &
             ' in SubTeam, of MainTeam''s child team number:'
!
end select SubTeam_select
!
end team !(SubTeam)
!
!*************
!*************
!*************
!
end team !(MainTeam)
!
end program Main

Expected Behavior
Program execution should not hang when allocating a coarray on a specific team only.

Let me further comment on this to give some idea about the importance of correct working of the ALLOCATE statement at the team level:
The desired runtime behavior of the ALLOCATE statement with a coarray object at the team level is described in the standards text, chapter <IP_ADDRESS>, paragraph 4: “...execution...is delayed until all other images in the current team have executed the same statement the same number of times in this team.”
And here is what the standard can't possibly say explicitly about the already very desirable real-world runtime behavior of the ALLOCATE statement in conjunction with remote atomics (through atomic subroutines) using the current implementations (ifort and gfortran):
Remote data transfer through atomic subroutines can be very irritable: Especially after a failure we can observe severe side effects that do corrupt the remote data transfer channels through atomic subroutines among the involved coarray images, so that no further remote data transfer will succeed. Nevertheless, we can use atomic subroutines (and SYNC MEMORY) to develop (with low effort) quite sophisticated (customized or user-defined) synchronization procedures that are able to detect such faulty remote data transfer channels between coarray images (using a timer).
Recovering from such is the goal and is exactly where the ALLOCATE statement comes into play: I did (more or less) extensive testing the ALLOCATE statement with corrupted remote data transfer channels using the current implementations (ifort 18/19beta, and recent gfortran/OpenCoarrays/MPICH -they have virtually the same runtime behavior on my computer-).
From my current testing I would say that the ALLOCATE statement is the one synchronization method that does allow to recover safely from corrupted data transfer channels through atomic subroutines. In this context, the ALLOCATE statement is not just for memory management but rather for restoring of (corrupted) remote data transfer channels by reallocating them after a failure.
I could imagine that correct implementation of ALLOCATE at the team level means a major effort for the implementer but hopefully did give an idea about it's importance as well.
Cheers
PS: I will soon upload a working example program that demonstrates such recovery through ALLOCATE to a new GitHub repository as well.

Hi Michael, I just wanted to let you know that I have seen this issue, but cannot attend to it for a few days. Please remind me later next week if you haven't heard from anyone by then.
Thanks!

Hi Zaak,
thanks for the note, and I will do so. That issue is on top of my list. (To
me, any other issue is currently secondary). I will even continue trying to
convince others about it's importance.
cheers
2018-05-17 3:14 GMT+02:00 zbeekman<EMAIL_ADDRESS>
Hi Michael, I just wanted to let you know that I have seen this issue, but
cannot attend to it for a few days. Please remind me later next week if you
haven't heard from anyone by then.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/533#issuecomment-389713622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUQ_MXLq1ZltN3pck8tA07-tUrI8Jz8ks5tzM8EgaJpZM4T7w16
.

Hi Zaak,
sorry for being somewhat delayed with my reminder to that issue.
As I've already told, it's an important issue for me and surely for others as well. I could imagine that the implementation of ALLOCATE / DEALLOCATE at the team level will be a major effort for the developer(s). Is there anything I could possibly do to help with this? Please let me know if any help is needed. (I can't make promises yet but would surely try to help if I only can).
Best Regards
Michael

Hi @MichaelSiehl,
I was one of the people that originally helped with teams and will be able to look into this issue next week. I'll be able to report on the amount of time/effort that I expect it will take to fix this issue. I can see its an important issue for you, thanks for your patience and reporting the issue.
Cheers, Soren

Hi Soren,
great! Thanks for that info.
Just some further background information:
I've got the plan to develop a coarray-based framework (as Open Source) for
general purpose parallel programming myself. I started with F08 but have
reached (and exceeded) the limits of Fortran 2008 coarrays (using it for
MPMD-style programming).
With current OpenCoarrays (I'm still using 2.0.0), and it's impressive
support for Fortran 2018 coarray teams, opportunities have already improved
greatly.
My current status: Due to a customized synchronization procedure, I can
easily detect (and avoid) many kinds of parallel runtime failures, ranging
from data races to hardware failures (by using a timer as well as an
'enumerated synchronization technique' within the customized
synchronization procedures; it requires also a certain programming
technique for the development of parallel algorithms). I can also produce
corrupted atomic data transfer channels between coarray images, to use
these for testing purposes.
(Just from my testing, the atomic data transfer channels themselves do not
seem to be corrupted but the timing between them. As a result, no further
data transfer between coarray images through the corrupted atomic (derived
type) coarray (component) may occur).
From my current testing, using ifort 18 and 19 beta (these do not support
F18 teams), as well as gfortran/OpenCoarrays, the ALLOCATE statement is the
one synchronization method that allows to safely recover from such
corrupted atomic data transfer channels (coarrays). That is what could make
ALLOCATE at the team level a really powerful feature.
(Another working option, that we can use meanwhile, is to switch to another
(derived type) atomic coarray (component) after such runtime failures with
corrupted atomic data transfer channels. On the other hand, a CHANGE TEAM
or END TEAM is not a cure for it. But also, and fortunately, there were no
side effects between coarray images in distinct teams at the same team
level, even not if they did execute on the same processor core -as far as I
can assume yet-.)
Cheers, Michael
https://github.com/MichaelSiehl?tab=repositories
2018-06-29 0:00 GMT+02:00 Soren Rasmussen<EMAIL_ADDRESS>
Hi @MichaelSiehl https://github.com/MichaelSiehl,
I was one of the people that originally helped with teams and will be able
to look into this issue next week. I'll be able to report on the amount of
time/effort that I expect it will take to fix this issue. I can see its an
important issue for you, thanks for your patience and reporting the issue.
Cheers, Soren
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/533#issuecomment-401186542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUQ_CdvQIHhCUuECFJYfkEFM91eUFmDks5uBVIQgaJpZM4T7w16
.

The deadlock occurs only when failed image support is enabled. Failed images have been disabled by default since OpenCoarrays 2.4.0.
The reason is that the gfortran front end emits a call to _gfortran_caf_sync_all() as part of the coarray allocation process. In OpenCoarrays, this routine includes the following barrier:
#ifdef WITH_FAILED_IMAGES
    ierr = MPI_Barrier(alive_comm); chk_err(ierr);
#else
    ierr = MPI_Barrier(CAF_COMM_WORLD); chk_err(ierr);
#endif

"alive_comm" is effectively MPI_COMM_WORLD, whereas CAF_COMM_WORLD is the communicator for the current team of images... so if failed images support is enabled, and a coarray allocation occurs in only a subset of sibling teams, then those teams will deadlock.
I'm working on enhancing failed images in OpenCoarrays to support a larger subset of the Fortran 2018 standard; that work will include a fix for this issue as well.

@nathanweeks Thanks very much for this information. I will check this soon using OC 2.4.0. (My current installation does still use OC 2.3.1.)

@nathanweeks It really works, great! I can confirm that OpenCoarrays 2.4.0 (with default usage) does allocate coarrays at the team level independently from any allocation on another team (no deadlock occurs). I think we can close this issue now.
Thanks very much. Great job!

@nathanweeks and @MichaelSiehl Thanks for resolving this!


lisk-cli dapps -a

Currently its harder to work on several dapps at the same time because if you answer no on the question about clearing the blockchain.db it doesn't go further.

After recent patches, lisk-cli is more or less operational again. I think this issue should be closed and more detailed ones added (i.e. psql database drop/re-create, answering the genesisblock.json override with "no" leads to "[TypeError: Invalid hex string]", ...)
So can this be closed?


Improve Type Constant Design

Problem
The TLC object is needed to discern if a type has a constant value. This increases cross-dependencies and prevents meaningful unification of Constants.
Describe the solution you'd like
Make Type Constants into Either<Term,Constant> instead of just Term.
Additional context
This could potentially greatly reduce the TLC object's God Object status in current design.

#56 all green with new system.


Create Autoresponder

docathon#219

Hey you might want to remove me from this as I no longer work at SendGrid.
Thanks!
Leor

On Nov 9, 2015, at 12:10 PM, Eric Schallock<EMAIL_ADDRESS>wrote:
Merged #888 https://github.com/sendgrid/docs/pull/888.
—
Reply to this email directly or view it on GitHub https://github.com/sendgrid/docs/pull/888#event-459213097.


Fix mario sample code

see: repl
I guess it's caused by setTimeout's type signature change.

Good catch, thank you!


supporting posting issues as JIRA and YouTrack backlog issues

May require setting up database ??

@epicallan , I think am stuck from some point, even after installing the jira integration apps in my github acc, my issues are not reflected in jira, all i see are the repositories and that's not what we want.


Feature/enhanced type support

Replaces visitor pattern / Extends type coverage
Better support for complex nested types
Attempts reference resolution directly before falling back to source maps
Normalize path separators to support cross platform
Replace usage of rm with rimraf in package scripts to support windows

Hi @WHenderson
Sorry for the delay.
I took the initiative of reordering the commits, in order to add the new examples before the visitor's refactoring.
I also added a commit with some tests on the new examples.
Turns out the new examples were already working without the refactoring (except for the Intersection but this was a bug in Typedoc itself, fixed here : https://github.com/TypeStrong/typedoc/pull/1910)
Ideally I'd like to have some examples that highlight the need for the refactoring.
Could you add some, maybe based on failing cases you would have on a project of yourself?
Thanks in advance.

Hi @WHenderson
Sorry for the delay.
I took the initiative of reordering the commits, in order to add the new examples before the visitor's refactoring. I also added a commit with some tests on the new examples.
Turns out the new examples were already working without the refactoring (except for the Intersection but this was a bug in Typedoc itself, fixed here : TypeStrong/typedoc#1910)
Ideally I'd like to have some examples that highlight the need for the refactoring. Could you add some, maybe based on failing cases you would have on a project of yourself?
Thanks in advance.

A large number of the types weren't correctly linking up in my main mono-repo, so I debugged through the generation steps and came up with this fix. As you can tell from the order of commits, I didn't use TDD and am surprised that all the types correctly linked even without the changes.
If I find some time I'll see if I can create a test case that justifies the fix. Right now I'm just trying to get my repo to the stage I can make it public (sorting documentation and licensing).
Thanks for taking the time though and also for creating this extension in the first place!

Hi @WHenderson
I published a new release v0.2.0 for typedoc v0.23 compatibility.
This new version doesn't rely on source maps anymore.
I picked up some of your commits on the main branch (windows compatibility, new examples and new tests).
Please let me know if the new version works for you.
Thanks.


Latency doesn't shown when quiet-text: true

Describe the bug
When I enable normalize with quiet-text: true and enable latency, latency doens't shown.

To Reproduce
collectors:
  - name: ns-col-ipv4
    afpacket-sniffer:
       port: 53
       device: ens192
       chan-buffer-size: 65535
     transforms:
       latency:
         measure-latency: true
         unanswered-queries: true
         queries-timeout: 2
       normalize:
         qname-lowercase: false
         quiet-text: true
loggers:
  - name: ns-log
     logfile:
        file-path: /var/log/dns/ns4-queries.log
        mode: text
        flush-interval: 1
        max-size: 100000000
        max-files: 0

routes:
    - from: [ ns-col-ipv4 ]
      to: [ ns-log ]

Additional context
Version: 0.39.0

Thank to report this bug.
The fix will be available in next release.

completed via #450


Include latest hugo 0.37.1 in Ubuntu 18.04 LTS repos

I have been testing the alpha of Ubuntu 18.04 in a VM and I noticed that the version of Hugo currently in the repos are 0.26.
Since Ubuntu 18.04 is a LTS and there have been really nice features added to Hugo lately, (like the page image resources handling) should we try to get hugo 0.34 in to the ubuntu repos before release?

Most likely it has to go through debian testing before entering the ubuntu repo https://tracker.debian.org/pkg/hugo

Thank you for the heads up!

I would love for this to happen, but this seems to be a hard task ...

Me too, it would be great to get the latest Hugo into Ubuntu 18.04 LTS especially because of all the important new features.  My apologies for falling behind.
According to https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule for Ubuntu 18.04 LTS, the Debian Import Freeze will happen on 2018-03-01, though indeed, for a LTS release, the Debian import might be from testing instead of unstable, so Hugo and any new dependencies had better enter "unstable" before 2018-02-21.  Deadline for dependency upload probably around 2018-02-14.
I'd better get on it.

All thanks to Dr. Tobias Quathamer (@toddy15) who prepared, packaged and uploaded hugo 0.35-1 to Debian on 2018-02-12:

https://tracker.debian.org/pkg/hugo

which has been imported into Ubuntu "Bionic":

https://packages.ubuntu.com/bionic/hugo (0.35-1 in [universe])

@toddy15, thank you for doing all the actual work when I was unable to.
Sidenote: hugo 0.36.1 cannot be uploaded to Debian yet because the new dependency golang-github-muesli-smartcrop-dev is still awaiting manual approval: https://ftp-master.debian.org/new.html

There are some serious issues with Hugo < 0.36.1 that, if this is some long term Debian thing, I would prefer if it would be removed rather than added.
Ideally you should wait for 0.37 (Monday).

There are some serious issues with Hugo < 0.36.1 that, if this is some long term Debian thing, I would prefer if it would be removed rather than added.
Ideally you should wait for 0.37 (Monday).

Thanks for the heads up!
Since the supposed deadline isn't until March 1, I think we still have a chance to get Hugo 0.37 into Ubuntu 18.04 LTS, perhaps using some kind of manual sync request if needed be.
I am starting to learn about that process here:

https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
https://wiki.ubuntu.com/DebianImportFreeze/Implementation

I will follow up on it to ensure the best version of Hugo ends up in Ubuntu 18.04 LTS.

Special thanks to @toddy15, @mwhudson and other friends at Ubuntu for filing sync requests on Launchpad, triaging them, and doing the actual sync into Ubuntu 18.04 LTS (bionic).
Here is a quick checklist to keep track of sync requests of related packages.
Packages that are absolutely needed for hugo (>= 0.37) to enter bionic-release
[ ] Bug #1753179 “FFe: Sync golang-github-alecthomas-chroma 0.3.0-1 ...” : Bugs : golang-github-alecthomas-chroma package : Ubuntu
[ ] Bug #1753180 “FFe: Sync hugo 0.37.1-1 (universe, coming soon) fr...” : Bugs : hugo package : Ubuntu
[ ] Bug #1753838 “Sync golang-github-chaseadamsio-goorgeous 2.0.0+gi...” : Bugs : golang-github-chaseadamsio-goorgeous package : Ubuntu to allow golang-blackfriday (1.5.1-1) to migrate from bionic-proposed to bionic-release.
Other dependencies or related packages
[x] Bug #1753748 “Sync golang-golang-x-sys 0.0~git20180224.f6cff07-1...” : Bugs : golang-golang-x-sys package : Debian which fixes compilation with gccgo-8
[ ] Bug #1753767 “FFe: Sync golang-fsnotify 1.4.7-1 (universe) from ...” : Bugs : golang-fsnotify package : Ubuntu with fewer deadlocks and race conditions
[ ] Bug #1753829 “FFe: Sync golang-github-revel-revel 0.12.0+dfsg-4 ...” : Bugs : golang-github-revel-revel package : Ubuntu because of my removal of old transitional package names from golang-fsnotify (1.4.7-1)

I will release 0.37.1 with 1 bug fix tomorrow. It's not the most critical bug in the world, but is a regression and hard for the end users to understand; I have been holding off a little waiting for more  ... which did not come, which I guess is a good thing.

I am happy to report that, thanks to the help of many people, especially @toddy15, @mwhudson, @tsimonq2 and @ginggs, Hugo 0.37.1-1 has finally landed in Ubuntu 18.04 LTS (bionic) (due to be released on 2018-04-26), see https://packages.ubuntu.com/bionic/hugo
(I was helping a friend with installing the Lubuntu flavour of Ubuntu 18.04 LTS daily snapshot, and sudo apt install hugo indeed fetched 0.37.1-1!  Hurray!)


⚠ File access has degraded performance

In cbfdc74, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 12520 ms

Resolved: File access performance has improved in ae46ce8 after 11 minutes.


(in-package :foo) not honored

If I execute the in-package function from the REPL the output suggests that the function successfully ran, however the package change never happens.
Also, it would be nice, once this is working, to change the REPL prompt to the new package name.

I'm running into this as well, is there a workaround?

Possibly important: Running (in-package ...) in the repl does not appear to change the value of *package* (which isn't surprising, but I thought it was worth pointing out).
I've found a solution for my needs though: To change the active package in the REPL, you can click on the name of the currently active package (the text that says "cl-user" in the attached screenshot).

This will open a dropdown at the top of VSCode allowing you to select a new package:

Find the package you want and click it, and the REPL prompt will move into that package.
Unless I missed it, I don't see this functionality documented in the readme, I figured it out by looking at the extension source. As someone attempting to learn CL, not knowing I could do this was a bit of a roadblock for me.


Upgrade Linux Kernel for flatcar-3510 from 5.15.113 to 5.15.115

Subject says it all.

We need to first release the next Stable with Kernel 5.15.113, https://github.com/flatcar/scripts/pull/840, not this one.
Added on-hold.

See instead https://github.com/flatcar/scripts/pull/904


fix(building-rollup): resolve json5 security vulnerability

What I did

Updated the @babel/core library in building-rollup package to resolve the recent json5 security vulnerability.

This updated @babel/core from 17.19.6 to 17.20.12. Changes to that library are minor and can be reviewed in their commit history.
Ran tests successfully in packages/building-rollup.

thx 🤗


Pushing invoice to a bad server returns "Invoice not found"

Per @itowlson:

If I push to a bad server, I appear to get an "Invoice was not found" error from the Bindle client lib, which seems misleading.  Is this expected / a known issue?  Or am I doing something wrong?

This is the error I get:
$ hippo bindle . -s http://fake.example.com/v1
Error: Error pushing bindle to server: Error creating request

So I'll move this issue over to Hippo-CLI

The misleading message occurs when the client is constructed with http2_prior_knowledge set to false.  The Bindle CLI never does that; I changed the Hippo CLI to do it on one of the branches, because I thought it might be needed to work with the load balancer on the test server, but I can change it back if we are happy with prior knowledge being assumed by default.

Oh! Okay. That makes sense why I could not reproduce. I will keep working on this one.

Semi-closing the loop on this one:

With a nonexistent server all is well
With a server that reliably returns 404 for unknown URLs, this will always produce Invoice was not found (because the client tries to post to .../_i and that doesn't exist.  404 is is unwrapped to an "invoice was not found" message at https://github.com/deislabs/bindle/blob/219d98dd3dd88e34635523506fe927758ad38c49/src/client/mod.rs#L549
WIth a server that reliably returns 404 for HTTP/1 but does not handle HTTP/2 without negotiation, you will get the generic "Error creating request" if you go straight to HTTP/2 because you can't talk to the server at all, but "Invoice was not found" if you negotiate because then it gets as far as the 404.  I guess example.com falls into this category.

So I think the fundamental issue is that the generic status unwrap code always assumes it's an invoice that was not found rather than the general invoice endpoint (or whatever other endpoint).

Alright, that all makes a lot of sense. So the root of the error is that a POST operation's 404 failure is being translated to the error message for a GET operation's error.


fix(deps): update config-no-service

This PR contains the following updates:

Package
Type
Update
Change

@grpc/grpc-js (source)
dependencies
minor
1.8.21 -> 1.9.8

@grpc/grpc-js (source)
dependencies
patch
1.9.0 -> 1.9.8

@grpc/proto-loader (source)
dependencies
patch
0.7.8 -> 0.7.10

@opentelemetry/auto-instrumentations-node (source)
dependencies
minor
0.38.0 -> 0.39.4

@opentelemetry/auto-instrumentations-node (source)
dependencies
patch
0.39.1 -> 0.39.4

@opentelemetry/auto-instrumentations-web (source)
dependencies
patch
0.33.1 -> 0.33.2

@opentelemetry/resource-detector-alibaba-cloud (source)
dependencies
patch
0.28.0 -> 0.28.2

@opentelemetry/resource-detector-alibaba-cloud (source)
dependencies
patch
0.28.1 -> 0.28.2

@opentelemetry/resource-detector-aws (source)
dependencies
patch
1.3.0 -> 1.3.2

@opentelemetry/resource-detector-aws (source)
dependencies
patch
1.3.1 -> 1.3.2

@opentelemetry/resource-detector-container (source)
dependencies
patch
0.3.0 -> 0.3.2

@opentelemetry/resource-detector-container (source)
dependencies
patch
0.3.1 -> 0.3.2

@opentelemetry/resource-detector-gcp (source)
dependencies
patch
0.29.0 -> 0.29.2

@opentelemetry/resource-detector-gcp (source)
dependencies
patch
0.29.1 -> 0.29.2

@types/node (source)
devDependencies
minor
20.5.0 -> 20.8.9

@types/styled-components (source)
devDependencies
patch
5.1.26 -> 5.1.29

@types/uuid (source)
devDependencies
patch
9.0.2 -> 9.0.6

Grpc.AspNetCore
nuget
minor
2.57.0 -> 2.58.0

Grpc.AspNetCore.HealthChecks
nuget
minor
2.57.0 -> 2.58.0

brotli

minor
==1.0.9 -> ==1.1.0

charset-normalizer

minor
==3.1.0 -> ==3.3.1

click (changelog)

patch
==8.1.6 -> ==8.1.7

configargparse

minor
==1.5.5 -> ==1.7

confluentinc/cp-kafka
final
patch
7.5.0 -> 7.5.1

cypress
devDependencies
minor
10.4.0 -> 10.11.0

eslint (source)
devDependencies
minor
8.47.0 -> 8.52.0

floki

minor
~> 0.34.3 -> ~> 0.35.0

gettext

minor
~> 0.22 -> ~> 0.23

gevent

minor
==23.7.0 -> ==23.9.1

geventhttpclient

patch
==2.0.9 -> ==2.0.11

github.com/IBM/sarama
require
patch
v1.41.1 -> v1.41.3

github.com/google/uuid
require
minor
v1.3.1 -> v1.4.0

go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
require
minor
v0.42.0 -> v0.45.0

go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
require
minor
v0.43.0 -> v0.45.0

go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
require
minor
v0.43.0 -> v0.45.0

go.opentelemetry.io/contrib/instrumentation/runtime
require
minor
v0.42.0 -> v0.45.0

go.opentelemetry.io/contrib/instrumentation/runtime
require
minor
v0.43.0 -> v0.45.0

golang
stage
minor
1.19.4-alpine -> 1.21.3-alpine

golang
stage
minor
1.19.2-alpine -> 1.21.3-alpine

google.golang.org/grpc
require
minor
v1.56.1 -> v1.59.0

google.golang.org/grpc
require
minor
v1.57.0 -> v1.59.0

google.golang.org/protobuf
require
minor
v1.30.0 -> v1.31.0

googleapis-common-protos

minor
==1.59.1 -> ==1.61.0

grafana/grafana

minor
10.1.2 -> 10.2.0

grpcio (source)

minor
==1.56.2 -> ==1.59.0

grpcio-health-checking

minor
==1.56.2 -> ==1.59.0

kubeshop/tracetest

minor
v0.13.10 -> v0.14.4

locust

minor
==2.15.1 -> ==2.18.0

log
dependencies
patch
0.4.19 -> 0.4.20

markdownlint-cli
devDependencies
minor
0.35.0 -> 0.37.0

monolog/monolog
require
minor
3.4.0 -> 3.5.0

msgpack (changelog)

patch
==1.0.5 -> ==1.0.7

net-smtp

minor
0.3.3 -> 0.4.0

open-telemetry/opentelemetry-logger-monolog (source)
require
patch
0.0.4 -> 0.0.5

openapi-typescript (source)
devDependencies
minor
6.5.0 -> 6.7.0

opentelemetry
dependencies
minor
0.19 -> 0.20

opentelemetry-api

minor
==1.19.0 -> ==1.20.0

opentelemetry-exporter-otlp (changelog)

minor
0.24.2 -> 0.26.1

opentelemetry-exporter-otlp-proto-grpc

minor
==1.19.0 -> ==1.20.0

opentelemetry-http
dependencies
minor
0.8.0 -> 0.9.0

opentelemetry-instrumentation-all (changelog)

minor
0.39.1 -> 0.51.1

opentelemetry-otlp (source)
dependencies
minor
0.12.0 -> 0.13.0

opentelemetry-proto

minor
==1.19.0 -> ==1.20.0

opentelemetry-sdk

minor
==1.19.0 -> ==1.20.0

opentelemetry-sdk (changelog)

minor
1.2.1 -> 1.3.0

opentelemetry-semantic-conventions (source)
dependencies
minor
0.11.0 -> 0.12.0

opentelemetry_api
dependencies
minor
0.19 -> 0.20

otel/opentelemetry-collector-contrib

minor
0.86.0 -> 0.88.0

phoenix

minor
~> 1.6.16 -> ~> 1.7.0

phoenix_live_view

minor
~> 0.17.5 -> ~> 0.20.0

pino (source)
dependencies
minor
8.14.2 -> 8.16.1

prost
dependencies
minor
0.11 -> 0.12

prost-types
dependencies
minor
0.11 -> 0.12

protobuf

minor
==4.23.4 -> ==4.24.4

psutil

patch
==5.9.5 -> ==5.9.6

puma (source, changelog)

minor
6.3.0 -> 6.4.0

python
final
minor
3.11-slim-bullseye -> 3.12-slim-bullseye

pyzmq (source)

patch
==25.1.0 -> ==25.1.1

quay.io/prometheus/prometheus

patch
v2.47.0 -> v2.47.2

reqwest-middleware
dependencies
patch
0.2.2 -> 0.2.4

reqwest-tracing
dependencies
patch
0.4.5 -> 0.4.6

ruby (source)

minor
3.1.4 -> 3.2.2

ruby
final
minor
3.1.4-slim -> 3.2.2-slim

rust
stage
minor
1.69 -> 1.73

sharp (changelog)
dependencies
patch
0.32.5 -> 0.32.6

sinatra (source, changelog)

minor
3.0.6 -> 3.1.0

styled-components (source)
dependencies
minor
6.0.7 -> 6.1.0

tokio (source)
dependencies
minor
1.28 -> 1.33

tonic
dependencies
minor
0.9 -> 0.10

tonic-build
build-dependencies
minor
0.9 -> 0.10

tonic-health
dependencies
minor
0.9.2 -> 0.10.2

tracing-opentelemetry
dependencies
minor
0.19.0 -> 0.21.0

ts-proto
dependencies
minor
1.156.6 -> 1.162.2

typescript (source)
devDependencies
minor
5.1.6 -> 5.2.2

typing-extensions (changelog)

minor
==4.7.1 -> ==4.8.0

urllib3 (changelog)

patch
==2.0.4 -> ==2.0.7

uuid
dependencies
patch
9.0.0 -> 9.0.1

uuid
dependencies
minor
1.3.2 -> 1.5.0

zope-interface

minor
==6.0 -> ==6.1

googleJavaFormat
dependencies
minor
1.7 -> 1.18.1

org.apache.logging.log4j:log4j-core (source)
dependencies
patch
2.21.0 -> 2.21.1

com.google.api.grpc:proto-google-common-protos
dependencies
minor
2.22.1 -> 2.27.0

com.google.api.grpc:proto-google-common-protos
dependencies
minor
2.26.0 -> 2.27.0

com.github.ben-manes.versions
plugin
minor
0.47.0 -> 0.49.0

Release Notes

grpc/grpc-node (@grpc/grpc-js)
v1.9.8
Compare Source
v1.9.7: @grpc/grpc-js 1.9.7
Compare Source

Fix a bug that could cause a client to not update name resolution after multiple failed connection attempts (#2602)

v1.9.6: @grpc/grpc-js 1.9.6
Compare Source

Include more information in most "No connection established" errors (#2598)
Remove the index tracer, and add more information to other trace logs (#2599)

v1.9.5: @grpc/grpc-js 1.9.5
Compare Source

Fix a type inconsistency in server-call.ts (#2589 contributed by @rsnullptr)
Close ports if the server is shut down while the bind operation is ongoing (#2590)

v1.9.4: @grpc/grpc-js 1.9.4
Compare Source

Fix a bug that could cause a client to sometimes incorrectly hold the process open when no longer in use (#2586)

v1.9.3: @grpc/grpc-js 1.9.3
Compare Source

Make a few improvements to DNS resolving timing (#2571)

Experimental changes:

Added grpc.experimental.BackoffTimeout#getEndTime

v1.9.2: @grpc/grpc-js 1.9.2
Compare Source

Handle error when sending keepalive pings (#2563)
Fix a bug that could cause invalid connection states when DNS updates contained the same address the client was already connected to (#2559 contributed by @gusumuzhe, backported in #2564)

v1.9.1: @grpc/grpc-js 1.9.1
Compare Source

Improve formatting of channelz logs (#2535)
Avoid sending initial request after the deadline passes in some cases (#2536)
Fix possible null reference in pick_first load balancing policy (#2539)
Allow empty method config names in service configs (#2550)
Defer actions in write callbacks on the client to potentially work around a Node bug (#2552)

v1.9.0: @grpc/grpc-js 1.9.0
Compare Source

Implement channel idle timeout and the channel option grpc.client_idle_timeout_ms (#2471)
Implement gRFC A62: pick_first: sticky TRANSIENT_FAILURE and address order randomization (#2511)
Fix premature leaving of context due to improper Http2ServerCallStream handling (#2501 contributed by @CedricKassen)
Add channel option grpc-node.tls_enable_trace to enable Node TLS tracing (#2507)
Cancel deadline timer on server when call is cancelled (#2508)

Experimental changes:

Added grpc.experimental.createResolver

open-telemetry/opentelemetry-js-contrib (@opentelemetry/auto-instrumentations-node)
v0.39.4
Compare Source
v0.39.3
Compare Source
v0.39.2
Compare Source
v0.39.1
Compare Source
v0.39.0
Compare Source

grpc/grpc-dotnet (Grpc.AspNetCore)
v2.58.0
What's Changed

Start 2.58 development cycle. by @jtattermusch in https://github.com/grpc/grpc-dotnet/pull/2267
Update ServiceBinderBase.AddMethod annotations to allow null handler by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2270
Add request and channel to call debugging by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2271
Support disabling load balancing with SocketsHttpHandler.Properties by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2274
Remove netstandard1.5 from some projects by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2279
Add debugger display to Status by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2281
Fix detecting inherited WinHttpHandler by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2288
Dispose socket after connection failure by @JamesNK in https://github.com/grpc/grpc-dotnet/pull/2287
Bump GrpcToolsPackageVersion to 2.58.0 by @apolcyn in https://github.com/grpc/grpc-dotnet/pull/2290
Bump version to pre1 on 2.58 branch by @apolcyn in https://github.com/grpc/grpc-dotnet/pull/2291
Update v2.58.x branch to 2.58.0 by @apolcyn in https://github.com/grpc/grpc-dotnet/pull/2299

Full Changelog: https://github.com/grpc/grpc-dotnet/compare/v2.57.0...v2.58.0

google/brotli (brotli)
v1.1.0
Compare Source
Added

decoder: BrotliDecoderAttachDictionary
decoder: BrotliDecoderOnFinish callback behind BROTLI_REPORTING
decoder: BrotliDecoderSetMetadataCallbacks
encoder: BrotliEncoderPrepareDictionary,
BrotliEncoderDestroyPreparedDictionary,
BrotliEncoderAttachPreparedDictionary
decoder: BrotliEncoderOnFinish callback behind BROTLI_REPORTING
common: BrotliSharedDictionaryCreateInstance,
BrotliSharedDictionaryDestroyInstance,
BrotliSharedDictionaryAttach
CLI: --dictionary option
java: encoder wrapper: Parameters.mode
java: Brotli{Input|Output}Stream.attachDictionary
java: wrapper: partial byte array input
typescript: decoder (transpiled from Java)

Removed

build: BROTLI_BUILD_PORTABLE option

Fixed

java: JNI decoder failed sometimes on power of 2 payloads

Improved

java / js: smaller decoder footprint
decoder: faster decoding
encoder: faster encoding
encoder: smaller stack frames

Ousret/charset_normalizer (charset-normalizer)
v3.3.1
Compare Source
Changed

Optional mypyc compilation upgraded to version 1.6.1 for Python >= 3.8
Improved the general detection reliability based on reports from the community

v3.3.0
Compare Source
Added

Allow to execute the CLI (e.g. normalizer) through python -m charset_normalizer.cli or python -m charset_normalizer
Support for 9 forgotten encoding that are supported by Python but unlisted in encoding.aliases as they have no alias (#323)

Removed

(internal) Redundant utils.is_ascii function and unused function is_private_use_only
(internal) charset_normalizer.assets is moved inside charset_normalizer.constant

Changed

(internal) Unicode code blocks in constants are updated using the latest v15.0.0 definition to improve detection
Optional mypyc compilation upgraded to version 1.5.1 for Python >= 3.8

Fixed

Unable to properly sort CharsetMatch when both chaos/noise and coherence were close due to an unreachable condition in __lt__ (#350)

v3.2.0
Compare Source
Changed

Typehint for function from_path no longer enforce PathLike as its first argument
Minor improvement over the global detection reliability

Added

Introduce function is_binary that relies on main capabilities, and optimized to detect binaries
Propagate enable_fallback argument throughout from_bytes, from_path, and from_fp that allow a deeper control over the detection (default True)
Explicit support for Python 3.12

Fixed

Edge case detection failure where a file would contain 'very-long' camel cased word (Issue #289)

bw2/ConfigArgParse (configargparse)
v1.7
Compare Source

cypress-io/cypress (cypress)
v10.11.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-11-0
v10.10.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-10-0
v10.9.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-9-0
v10.8.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-8-0
v10.7.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-7-0
v10.6.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-6-0
v10.5.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#10-5-0

eslint/eslint (eslint)
v8.52.0
Compare Source
Features

70648ee feat: report-unused-disable-directive to report unused eslint-enable (#17611) (Yosuke Ota)

Bug Fixes

5de9637 fix: Ensure shared references in rule configs are separated (#17666) (Nicholas C. Zakas)
dcfe573 fix: add preceding semicolon in suggestions of no-object-constructor (#17649) (Francesco Trotta)

Documentation

476d58a docs: Add note about invalid CLI flags when using flat config. (#17664) (Nicholas C. Zakas)
660ed3a docs: Plugin flat config migration guide (#17640) (Nicholas C. Zakas)
a58aa20 docs: fix examples for several rules (#17645) (Milos Djermanovic)
179929b docs: Remove trailing newline from the code of Playground links (#17641) (Francesco Trotta)
f8e5c30 docs: Update README (GitHub Actions Bot)
b7ef2f3 docs: Enable pretty code formatter output (#17635) (Nicholas C. Zakas)
0bcb9a8 docs: Fix syntax errors in rule examples (#17633) (Francesco Trotta)
61b9083 docs: Make no-continue example code work (#17643) (Zhongyuan Zhou)
9fafe45 docs: upgrade to 11ty 2.0 (#17632) (Percy Ma)
ff8e4bf docs: Update README (GitHub Actions Bot)
fab249a docs: Update README (GitHub Actions Bot)
392305b docs: Update no-irregular-whitespace and fix examples (#17626) (Francesco Trotta)
6b8acfb docs: Add real whitespace to no-trailing-spaces examples (#17630) (Francesco Trotta)
1000187 docs: Fix examples in unicode-bom (#17631) (Francesco Trotta)
000290c docs: Update README (GitHub Actions Bot)

Chores

6d1f0c2 chore: upgrade<EMAIL_ADDRESS>(#17671) (Milos Djermanovic)
d63d4fe chore: package.json update for @eslint/js release (ESLint Jenkins)
f30cefe test: fix FlatESLint tests for caching (#17658) (Milos Djermanovic)
ef650cb test: update tests for no-promise-executor-return (#17661) (Milos Djermanovic)

v8.51.0
Compare Source
Features

0a9c433 feat: Add --no-warn-ignored CLI option for flat config (#17569) (Domantas Petrauskas)
977e67e feat: logical-assignment-operators to report expressions with 3 operands (#17600) (Yosuke Ota)

Bug Fixes

f976b2f fix: make rule severity case-sensitive in flat config (#17619) (Milos Djermanovic)
0edfe36 fix: Ensure crash error messages are not duplicated (#17584) (Nicholas C. Zakas)
dd79abc fix: eslint-disable to be able to parse quoted rule names (#17612) (Yosuke Ota)
d2f6801 fix: Ensure correct code path for && followed by ?? (#17618) (Nicholas C. Zakas)

Documentation

ee5be81 docs: default to sourceType: "module" in rule examples (#17615) (Francesco Trotta)
1aa26df docs: Add more examples for multiline-ternary (#17610) (George Ashiotis)
47d0b44 docs: Update README (GitHub Actions Bot)
dbf831e docs: use generated og image (#17601) (Percy Ma)
1866da5 docs: Update README (GitHub Actions Bot)

Chores

1ef39ea chore: upgrade<EMAIL_ADDRESS>(#17624) (Milos Djermanovic)
f8c7403 chore: package.json update for @eslint/js release (ESLint Jenkins)
2665552 test: fix flat config linter tests to use Linter in flat config mode (#17616) (Milos Djermanovic)
7b77bcc chore: Refactor CodePathState (#17510) (Nicholas C. Zakas)
bc77c9a chore: Document and refactor ForkContext (#17566) (Nicholas C. Zakas)
24e1f14 chore: Refactor and document CodePath (#17558) (Nicholas C. Zakas)

v8.50.0
Compare Source
Features

27d5a9e feat: add suggestions to array-callback-return (#17590) (Tanuj Kanti)
f9082ff feat: flat-rule-tester make sure default config always matches (#17585) (fnx)
83914ad feat: Implement SourceCode#applyInlineConfig() (#17351) (Nicholas C. Zakas)
22a5582 feat: add rule no-object-constructor, deprecate no-new-object (#17576) (Francesco Trotta)
85a3d9e feat: allowVoid option in array-callback-return (#17564) (Tanuj Kanti)

Bug Fixes

cc4d26b fix: Ensure deprecated context.parserServices warns (#17593) (Nicholas C. Zakas)
1ea4cfb fix: Ensure all RuleTester tests all deprecated context methods (#17587) (Nicholas C. Zakas)
aa1b657 fix: wrong suggestion and message in no-misleading-character-class (#17571) (Yosuke Ota)

Documentation

1800537 docs: Fix and standardize JSX code examples (#17591) (Francesco Trotta)
48a44a7 docs: Add correct/incorrect tags to prefer-arrow-callback (#17589) (Francesco Trotta)
20893d4 docs: fix incorrect tag's place (#17575) (Tanuj Kanti)
bd7a71f docs: Update README (GitHub Actions Bot)

Chores

f8a8a2d chore: upgrade<EMAIL_ADDRESS>(#17599) (Milos Djermanovic)
38ada6d chore: package.json update for @eslint/js release (ESLint Jenkins)

v8.49.0
Compare Source
Features

da09f4e feat: Implement onUnreachableCodePathStart/End (#17511) (Nicholas C. Zakas)
32b2327 feat: Emit deprecation warnings in RuleTester (#17527) (Nicholas C. Zakas)
acb7df3 feat: add new enforce option to lines-between-class-members (#17462) (Nitin Kumar)

Documentation

ecfb54f docs: Update README (GitHub Actions Bot)
de86b3b docs: update no-promise-executor-return examples (#17529) (Nitin Kumar)
032c4b1 docs: add typescript template (#17500) (James)
cd7da5c docs: Update README (GitHub Actions Bot)

Chores

b7621c3 chore: remove browser test from npm test (#17550) (Milos Djermanovic)
cac45d0 chore: upgrade<EMAIL_ADDRESS>(#17549) (Milos Djermanovic)
cd39508 chore: package.json update for @eslint/js release (ESLint Jenkins)
203a971 ci: bump actions/checkout from 3 to 4 (#17530) (dependabot[bot])
a40fa50 chore: use eslint-plugin-jsdoc's flat config (#17516) (Milos Djermanovic)
926a286 test: replace Karma with Webdriver.IO (#17126) (Christian Bromann)
f591d2c chore: Upgrade config-array (#17512) (Nicholas C. Zakas)

v8.48.0
Compare Source
Features

1fbb3b0 feat: correct update direction in for-direction (#17483) (Francesco Trotta)
d73fbf2 feat: rule tester do not create empty valid or invalid test suites (#17475) (fnx)
ee2f718 feat: Allow void in rule no-promise-executor-return (#17282) (nopeless)

Bug Fixes

7234f6a fix: update RuleTester JSDoc and deprecations (#17496) (Jonas Berlin)

Documentation

7a51d77 docs: no-param-reassign mention strict mode (#17494) (Stephen Hardy)
9cd7ac2 docs: add fetch script to package.json conventions (#17459) (Nitin Kumar)
cab21e6 docs: advice for inline disabling of rules (#17458) (Ashish Yadav)
056499d docs: fix example of flat config from plugin (#17482) (Francesco Trotta)
9e9edf9 docs: update documentation URL in error message (#17465) (Nitin Kumar)

Chores

8dd3cec chore: upgrade<EMAIL_ADDRESS>(#17501) (Milos Djermanovic)
6d0496e chore: package.json update for @eslint/js release (ESLint Jenkins)
9d4216d chore: Refactor and document CodePathSegment (#17474) (Nicholas C. Zakas)

gwik/geventhttpclient (geventhttpclient)
v2.0.11
Compare Source
What's Changed

Support Python 3.12 by @cyberw in https://github.com/geventhttpclient/geventhttpclient/pull/182

Full Changelog: https://github.com/geventhttpclient/geventhttpclient/compare/2.0.10...2.0.11
v2.0.10
Compare Source
What's Changed

Disable unit tests for no ssl module + fixes for build by @cyberw in https://github.com/geventhttpclient/geventhttpclient/pull/181
(no code changes)

Full Changelog: https://github.com/geventhttpclient/geventhttpclient/compare/2.0.9...2.0.10

IBM/sarama (github.com/IBM/sarama)
v1.41.3: Version 1.41.3 (2023-10-17)
Compare Source

What's Changed
:bug: Fixes

fix: pre-compile regex for parsing kafka version by @qshuai in https://github.com/IBM/sarama/pull/2663
fix(client): ignore empty Metadata responses when refreshing by @HaoSunUber in https://github.com/IBM/sarama/pull/2672

:package: Dependency updates

chore(deps): bump the golang-org-x group with 2 updates by @dependabot in https://github.com/IBM/sarama/pull/2661
chore(deps): bump golang.org/x/net from 0.16.0 to 0.17.0 by @dependabot in https://github.com/IBM/sarama/pull/2671

:memo: Documentation

fix(docs): correct topic name in rebalancing strategy example by @maksadbek in https://github.com/IBM/sarama/pull/2657

New Contributors

@maksadbek made their first contribution in https://github.com/IBM/sarama/pull/2657
@qshuai made their first contribution in https://github.com/IBM/sarama/pull/2663

Full Changelog: https://github.com/IBM/sarama/compare/v1.41.2...v1.41.3
v1.41.2: Version 1.41.2 (2023-09-12)
Compare Source

What's Changed
:tada: New Features / Improvements

perf: Alloc records in batch by @ronanh in https://github.com/IBM/sarama/pull/2646

:bug: Fixes

fix(consumer): guard against nil client by @dnwe in https://github.com/IBM/sarama/pull/2636
fix(consumer): don't retry session if ctx canceled by @dnwe in https://github.com/IBM/sarama/pull/2642
fix: use least loaded broker to refresh metadata by @HaoSunUber in https://github.com/IBM/sarama/pull/2645

:package: Dependency updates

chore(deps): bump the golang-org-x group with 1 update by @dependabot in https://github.com/IBM/sarama/pull/2641

New Contributors

@HaoSunUber made their first contribution in https://github.com/IBM/sarama/pull/2645

Full Changelog: https://github.com/IBM/sarama/compare/v1.41.1...v1.41.2

google/uuid (github.com/google/uuid)
v1.4.0
Compare Source
Features

UUIDs slice type with Strings() convenience method (#133) (cd5fbbd)

Fixes

Clarify that Parse's job is to parse but not necessarily validate strings. (Documents current behavior)

grpc/grpc-go (google.golang.org/grpc)
v1.59.0: Release 1.59.0
Compare Source
Behavior Changes

balancer: grpc will switch to case-sensitive balancer names soon; log a warning if a capital letter is encountered in an LB policy name (#6647)
server: allow applications to send arbitrary data in the grpc-status-details-bin trailer (#6662)
client: validate grpc-status-details-bin trailer and pass through the trailer to the application directly (#6662)

New Features

tap (experimental): Add Header metadata to tap handler (#6652)

Special Thanks: @pstibrany

grpc: channel idleness enabled by default with an idle_timeout of 30m (#6585)

Documentation

examples: add an example of flow control behavior (#6648)

Bug Fixes

xds: fix hash policy header to skip "-bin" headers and read content-type header as expected (#6609)

v1.58.3: Release 1.58.3
Compare Source
Security

server: prohibit more than MaxConcurrentStreams handlers from running at once (CVE-2023-44487)
In addition to this change, applications should ensure they do not leave running tasks behind related to the RPC before returning from method handlers, or should enforce appropriate limits on any such work.

v1.58.2: Release 1.58.2
Compare Source
Bug Fixes

balancer/weighted_round_robin: fix ticker leak on update
A new ticker is created every time there is an update of addresses or configuration, but was not properly stopped.  This change stops the ticker when it is no longer needed.

v1.58.1: Release 1.58.1
Compare Source
Bug Fixes

grpc: fix a bug that was decrementing active RPC count too early for streaming RPCs; leading to channel moving to IDLE ev

Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: src/featureflagservice/mix.lock
Command failed: mix deps.update floki gettext phoenix phoenix_live_view
/bin/sh: mix: command not found

File name: src/productcatalogservice/go.sum
Command failed: go get -d -t ./...
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc v0.39.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.16.0
go: downloading go.opentelemetry.io/otel/sdk/metric v0.39.0
go: downloading go.opentelemetry.io/otel/sdk v1.16.0
go: downloading golang.org/x/net v0.15.0
go: downloading golang.org/x/sys v0.12.0
go: downloading google.golang.org/genproto v0.0.0-20230822172742-b8732ec3820d
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.16.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlpmetric v0.39.0
go: downloading go.opentelemetry.io/proto/otlp v0.20.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/internal/retry v1.16.0
go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.16.0
go: downloading go.opentelemetry.io v0.1.0
go: downloading go.opentelemetry.io/otel/exporters/otlp v0.20.1
go: github.com/opentelemetry/opentelemetry-demo/src/productcatalogservice imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc imports
	go.opentelemetry.io/otel/exporters/otlp/internal: cannot find module providing package go.opentelemetry.io/otel/exporters/otlp/internal
go: github.com/opentelemetry/opentelemetry-demo/src/productcatalogservice imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc imports
	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/internal/oconf imports
	go.opentelemetry.io/otel/exporters/otlp/internal/envconfig: cannot find module providing package go.opentelemetry.io/otel/exporters/otlp/internal/envconfig
go: module github.com/golang/protobuf is deprecated: Use the "google.golang.org/protobuf" module instead.

File name: src/shippingservice/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/shippingservice/Cargo.toml --workspace
/bin/sh: cargo: command not found

File name: src/emailservice/Gemfile.lock

/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:283:in `find_spec_for_exe': Could not find 'bundler' (2.3.7) required by your /private/var/folders/sb/c6sv5dy16rjdlflwkf5q2kfr0000gn/T/renovate/repos/github/secustor/opentelemetry-demo/src/emailservice/Gemfile.lock. (Gem::GemNotFoundException)
To update to the latest version installed on your system, run `bundle update --bundler`.
To install the missing version, run `gem install bundler:2.3.7`
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems.rb:302:in `activate_bin_path'
	from /usr/bin/bundler:23:in `<main>'


preUpdate event is dispatched when only refmany collection is updated

Fixes #861, closes #862

Merged manually in https://github.com/doctrine/mongodb-odm/commit/c055530e236b12ef29a22937e9ebc3d14ef0959a


Error in planet temperature estimate

in equations.py, lines 173-174 read
if T_p is None:
T_p = T_s * ((1-A)/epsilon)**(1/4) * sqrt(R_s/(2*a))
the factor 1/4 evaluates to 0 rather than 0.25

Hey, the file begins with from __future__ import division and so it should equal 0.25. Was this evaluating incorrectly?


⚠ Bofrost.hr has degraded performance

In cb15bcd, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 2882 ms

Resolved: Bofrost.hr performance has improved in 9161fbb after 6 minutes.


Added packed layernorm_forward

This is the implementation of using packed data types for layernorm and has an associated speedup of around 50% for this kernel in the dev files, waiting for the PR for making the data types in that kernel into floatX to merge before merging the test kernels for this.

https://github.com/karpathy/llm.c/pull/319 this one adds the floatX to the dev cuda kernel for this

I am very embarrassed I swear running this yesterday I was getting numbers that were closer to 600GB/s for both kernel 6 and kernel 9 throughput and around 900GB/s for kernel 8 throughput and now when I run those kernels its  around 950GB/s and 1050GB/s for the 8. If that really is the case and you'd rather keep the simplicity and not have the packing then there is also the option of going for kernel 9 that is now the same speed as kernel 6 that will give the same performance as before but split it into two simpler kernels?


Support for Portfolio page

Could you expound on what exactly the requirements for a "portfolio page" would be?

A different page that showcases author's work or projects that is not specific to github repositories. May also serve as CV.

Why to add support for portfolio that's not specific to github repositories right into this?
You always can add a page and make it however you want such as Portfolio or CV.
https://github.com/github/personal-website#adding-pages

@flamendless If I understand you correctly, it sounds like you want a more generic presentation of any kind of work-related content. I think the purpose there is so broad and unique to each person that this repository could not be useful for those purposes.
This repo's purpose is to do the heavy lifting of wiring up a Jekyll website to showcase your work (assuming much of it is on GitHub) without requiring you to go and gather each project's content. Beyond that, you're very welcome to hack your fork to display any type of content you like. Just write the HTML into the existing files 👍🏼


Does not keep the screen awake on Android when accessed via chrome

Hosting the app locally, accessing it on an android device via chrome over LAN (e.g. <IP_ADDRESS>:port)
The future returns the updated enabled/disabled value, but the screen still turns off.
If I go to the nosleep demo page on the same phone / browser (https://richtr.github.io/NoSleep.js/example) the screen stays on.

@odkken thank you for bringing this up.
Unfortunately, I don't have the experience in debugging mobile web apps from Chrome, so I might be hamstrung in trying to investigate this further.
If you can provide an example app that reproduces this, that would also help.
Lastly, I do take pill requests to resolve this issue. So if you have a lead on a possible fix, I'll be happy to review it.

Sure, the provided example app is all I'm running.  If you just launch it with

flutter run -d web-server --web-hostname <IP_ADDRESS> --web-port 12345

then access that from your phone's browser, you should be able to reproduce

I am working on it on the side, so if I figure it out I'll update.  Just wanted to raise awareness if anyone is more knowledgeable than I am.

Huh, this seems to be an android-specific issue.  I tried it on an iphone and it works fine.

Here is a very simple working widget to provide the functionality:
class WakeLockWidget extends StatefulWidget {
const WakeLockWidget({super.key});
@override
_WakeLockWidgetState createState() => _WakeLockWidgetState();
}
class _WakeLockWidgetState extends State {
bool _isSupported = false;
var _wakeLock;
@override
void initState() {
super.initState();
_checkSupport();
}
_checkSupport() {
final navigatorObj = js.JsObject.fromBrowserObject(js.context['navigator']);
if (navigatorObj.hasProperty('wakeLock')) {
setState(() => _isSupported = true);
}
}
enable() {
if (!_isSupported) return;
final navigatorObj = js.JsObject.fromBrowserObject(js.context['navigator']);
final promise = navigatorObj['wakeLock'].callMethod('request', ['screen']);

// Handle the promise resolution
js.JsObject.fromBrowserObject(promise).callMethod('then', [
  (val) {
    setState(() {
      _wakeLock = val;
    });
  }
]);

}
disable() {
if (!_isSupported || _wakeLock == null) return;
final wakeLockObj = js.JsObject.fromBrowserObject(_wakeLock);
if (wakeLockObj.hasProperty('release')) wakeLockObj.callMethod('release');

}
@override
Widget build(BuildContext context) {
return Column(
children: [
ElevatedButton(onPressed: enable, child: Text('Enable WakeLock')),
ElevatedButton(onPressed: disable, child: Text('Disable WakeLock')),
],
);
}
}
I will leave this here rather than submitting a pull request, as I am not familiar with flutter package development, and I think this would need to be added to the original wakelock package (the web implementation specifically).

I can confirm there is some kind of issue with web, I tried on mobile both chrome and safari. nosleep.js testpage works fine.

@diegotori any update on including/fixing this? I'd love to remove the hack, as it breaks cross-platform compatibility while js is included directly.

It works in the latest Flutter version for me now. Thank you for making/maintaining the package!

Hi @ocinon,
can you please specify in which Flutter Version it started working for you?
Did you do any other fixes/workarounds or ist just "started working"?
I´m still having this issue on an Android device with Chrome..

@yannis216 I haven't tested it in a while and can't tell you which version it was. The two things that I did were update Flutter and call the init function once the user presses a button on the page, as otherwise, it doesn't work (actually, it could be that I'm calling init during each build call).


Remove version: StefansTools.SKTimeStamp version 1.3.7

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/stefanstools/files/SKTimeStamp/SKTimeStamp64-1.3.7.msi/download
Status Code: 200
(Automated message - build 897)

Close with reason: Package still available.;


setMinWordLength gives an exception

Hey, nice library.
I loaded some text into it and settings frequencyAnalyzer.setMinWordLength(2); for words such as "ok" and "gg", but this gives me an exception:
java.lang.IllegalArgumentException: Width (0) and height (14) cannot be <= 0
	at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1016)
	at java.awt.image.BufferedImage.<init>(BufferedImage.java:340)
	at wordcloud.Word.<init>(Word.java:39)
	at wordcloud.WordCloud.buildWord(WordCloud.java:260)
	at wordcloud.WordCloud.buildwords(WordCloud.java:247)
	at wordcloud.WordCloud.build(WordCloud.java:107)
	at CloudCreator.main(CloudCreator.java:56)

where line 56 is wordCloud.build(wordFrequencies);

Might be related to the empty string issue #14

sorry about that! I'll look into this :) Thanks for creating the issue.

fixed.


Date modified and Modified fields are updated immediately on success

@kthorat-prog @markquintontulloch typically these should be set on the backend

@oblodgett The response of the service is the updated row data. So, I think it is already set on the backend.


[WIP] Use z2taper and deprecate legacy

Summary
Before merge this PR, https://github.com/Qiskit/qiskit-terra/pull/5537 and update qiskit-tutorials are necessary.
Details and comments
TODO

[ ] WIP
[ ] Update qiskit-tutorials

I think in Aqua we can stay with the code, that will all be deprecated here, still using legacy operators. Evidently the moved/refactored application modules will use the opflow now in Terra. I think that this PR can just be closed? (Tutorials will all need be updated so they used the moved/refactored code from terra and the new repos and no longer use any Aqua code, but in any case that work will be done elsewhere to be PR'd to the qiskit tutorials repo)

I think in Aqua we can stay with the code, that will all be deprecated here, still using legacy operators. Evidently the moved/refactored application modules will use the opflow now in Terra. I think that this PR can just be closed? (Tutorials will all need be updated so they used the moved/refactored code from terra and the new repos and no longer use any Aqua code, but in any case that work will be done elsewhere to be PR'd to the qiskit tutorials repo)


Body Padding Issue if offCanvas is Open

Hi , how can i remove Body Padding Issue if offCanvas is Open?

What do you mean by body padding issue? Is it visible in our docs page?
https://tailwind-elements.com/docs/standard/navigation/offcanvas/

Closing due to inactivity.


Tidal energy pilot

Pilot is using HDF5 files with grid data with xyt coordinates.

vocabularies of values needs to be determine
dashboard shall access the data in efficient way to visualise, tiling is interesting - to be confirmed if needed

Thank you, so there are many opportunities to develop


You might find Ripcord (Qt Discord client) interesting

I just saw this project, and remembered another Qt Discord client I used a few years back called Ripcord. Just thought you might find it interesting for reference.
It is closed-source iirc, but the Qt GUI library it uses is FOSS: https://github.com/randrew/phantomstyle

Interesting, thanks!