Boxen broken under macOS Sierra

Hello guys.
Boxen seems to be broken under macOS Sierra.
Have you experimented a successful boxen install running under macOS Sierra ?
Thx

Are you able to provide the output or problem you are seeing?

I obtained this output:
julien@Carbonite:/opt/boxen$ boxen
--> Preparing to auto-update...
--> Complete! Nothing new from upstream.
Notice: Compiled catalog for pc20.home in environment production in 2.80 seconds
Notice: Package[boxen/brews/hub](provider=homebrew): Updating homebrew formulas
Error: Could not update: Execution of 'brew boxen-install boxen/brews/hub' returned 1: Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
==> Installing hub from boxen/brews
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

==> Downloading https://github.com/github/hub/archive/v2.2.1.tar.gz
Already downloaded: /opt/boxen/cache/homebrew/hub-2.2.1.tar.gz
Warning: Calling Pathname#sha1 is deprecated!
Use Pathname#sha256 instead.
/opt/boxen/homebrew/Library/Homebrew/extend/pathname.rb:320:in `verify_checksum'

==> script/build
Last 15 lines from /Users/julien/Library/Logs/Homebrew/hub/01.build:
2016-08-22 21:49:10 +0200

script/build

# _/private/tmp/hub-20160822-51203-y0p5wo/hub-2.2.1
/opt/boxen/homebrew/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64/link: -X flag requires argument of the form importpath.name=value

READ THIS: https://git.io/brew-troubleshooting

/opt/boxen/homebrew/Library/Homebrew/utils/github.rb:212:in `raise_api_error': Validation Failed (GitHub::Error)
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:174:in `open'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:219:in `issues_matching'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:252:in `issues_for_formula'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:312:in `fetch_issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:308:in `issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:353:in `dump'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:126:in `rescue in <main>'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:26:in `<main>'
Wrapped exception:
Execution of 'brew boxen-install boxen/brews/hub' returned 1: Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
==> Installing hub from boxen/brews
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

==> Downloading https://github.com/github/hub/archive/v2.2.1.tar.gz
Already downloaded: /opt/boxen/cache/homebrew/hub-2.2.1.tar.gz
Warning: Calling Pathname#sha1 is deprecated!
Use Pathname#sha256 instead.
/opt/boxen/homebrew/Library/Homebrew/extend/pathname.rb:320:in `verify_checksum'

==> script/build
Last 15 lines from /Users/julien/Library/Logs/Homebrew/hub/01.build:
2016-08-22 21:49:10 +0200

script/build

# _/private/tmp/hub-20160822-51203-y0p5wo/hub-2.2.1
/opt/boxen/homebrew/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64/link: -X flag requires argument of the form importpath.name=value

READ THIS: https://git.io/brew-troubleshooting

/opt/boxen/homebrew/Library/Homebrew/utils/github.rb:212:in `raise_api_error': Validation Failed (GitHub::Error)
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:174:in `open'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:219:in `issues_matching'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:252:in `issues_for_formula'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:312:in `fetch_issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:308:in `issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:353:in `dump'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:126:in `rescue in <main>'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:26:in `<main>'
Error: /Stage[main]/Hub/Package[boxen/brews/hub]/ensure: change from 2.2.5 to Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

2.2.1 failed: Could not update: Execution of 'brew boxen-install boxen/brews/hub' returned 1: Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
==> Installing hub from boxen/brews
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/hub.rb:6:in `<class:Hub>'
Please report this to the boxen/brews tap!

==> Downloading https://github.com/github/hub/archive/v2.2.1.tar.gz
Already downloaded: /opt/boxen/cache/homebrew/hub-2.2.1.tar.gz
Warning: Calling Pathname#sha1 is deprecated!
Use Pathname#sha256 instead.
/opt/boxen/homebrew/Library/Homebrew/extend/pathname.rb:320:in `verify_checksum'

==> script/build
Last 15 lines from /Users/julien/Library/Logs/Homebrew/hub/01.build:
2016-08-22 21:49:10 +0200

script/build

# _/private/tmp/hub-20160822-51203-y0p5wo/hub-2.2.1
/opt/boxen/homebrew/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64/link: -X flag requires argument of the form importpath.name=value

READ THIS: https://git.io/brew-troubleshooting

/opt/boxen/homebrew/Library/Homebrew/utils/github.rb:212:in `raise_api_error': Validation Failed (GitHub::Error)
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:174:in `open'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:219:in `issues_matching'
       	from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:252:in `issues_for_formula'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:312:in `fetch_issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:308:in `issues'
       	from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:353:in `dump'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:126:in `rescue in <main>'
       	from /opt/boxen/homebrew/Library/Homebrew/brew.rb:26:in `<main>'

It looks like you are running an older version of Boxen (since hub was updated to 2.2.3 and resolved many of those deprecation notices via boxen/puppet-hub#16). Can you try updating to the latest version?
However I have not seen this warning before:
# _/private/tmp/hub-20160822-51203-y0p5wo/hub-2.2.1
/opt/boxen/homebrew/Cellar/go/1.7/libexec/pkg/tool/darwin_amd64/link: -X flag requires argument of the form importpath.name=value

READ THIS: https://git.io/brew-troubleshooting

/opt/boxen/homebrew/Library/Homebrew/utils/github.rb:212:in `raise_api_error': Validation Failed (GitHub::Error)
        from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:174:in `open'
        from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:219:in `issues_matching'
        from /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:252:in `issues_for_formula'
        from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:312:in `fetch_issues'
        from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:308:in `issues'
        from /opt/boxen/homebrew/Library/Homebrew/exceptions.rb:353:in `dump'
        from /opt/boxen/homebrew/Library/Homebrew/brew.rb:126:in `rescue in <main>'
        from /opt/boxen/homebrew/Library/Homebrew/brew.rb:26:in `<main>'

Have you tried the troubleshooting link? I also run Go 1.7 locally and don't receive this on El Capitan but I'm not 100% sure this is Boxen related.
The  /opt/boxen/homebrew/Library/Homebrew/utils/github.rb:212:in 'raise_api_error': Validation Failed (GitHub::Error) suggests this is an issue with the connection to GitHub. Once you update hub can you try running boxen --debug? This will run puppet in verbose mode and give you more of an idea where things are failing and what is happening leading up to the failure.

@jacobbednarz Thank you. Bump simply puppet-hub to 1.4.3 fixed the problem.

Awesome news!


[Feature Request] Deploying from GitHub

This project is amazing; I've been using it, and it works very well. Unfortunately, having Wrangler locally on the computer and the local module creates a dependency on working offline and deploying with Wrangler to the Cloudflare Worker for every change to see updates. It would be great if there was a way to fork the project and have an automatic deploy button to Cloudflare (example: https://github.com/eidam/cf-workers-status-page#deploy-with-cloudflare-deploy-button), where the Github Action is generated automatically (with private API keys configured as Action variables) to upload the deploy to Cloudflare.

Possible one-click automatic deployment link: https://deploy.workers.cloudflare.com/?url=https://github.com/G4brym/R2-Explorer

Maybe this could work: https://github.com/cloudflare/wrangler-action

Hey @fernandodilland i've just published a new tutorial onhow to setup a new project and update using github action
https://r2explorer.dev/getting-started/setup-using-github-actions/
Let me know if you find any issues with this setup


synth_lattice: Optionally do constant comparisons in soft logic

Here we are adding a -cmp2softlogic option to synth_lattice to implement constant comparisons (arithmetic comparisons of a signal to a constant) in soft logic. Take e.g. the following:
read_verilog <<EOF
module top(input [15:0] a, output y);
	assign y = a >= 16'h7700;
endmodule
EOF
synth_lattice -family xo3 [-cmp2softlogic]

With the soft logic option, this takes up
   Number of cells:                  3
     LUT4                            3

while ordinarily it would take
   Number of cells:                 14
     CCU2D                           8
     LUT4                            6

The lower usage is due to two factors:

Once the comparisons are lowered to hard carry chains they won't be optimized, but here e.g. the lower 8 bits of the signal need not be compared at all, which is optimized away in the soft logic implementation. We could, and probaly should, extend opt_expr to optimize away the lower bits of the comparison on the $ge and other cells if the constant allows that, probably conditioned on the -fine mode. That would optimize the comparison before it gets implemented with the carry chains, so it would close the usage gap here somewhat.

Optimized or not optimized, simple LUT implementation of the comparison takes up less resources anyway, by (I think) a factor of three. This is at the cost of higher delay since we are not using the carry paths.

Here we are adding a -cmp2softlogic option to synth_lattice to implement constant comparisons (arithmetic comparisons of a signal to a constant) in soft logic. Take e.g. the following:

I already implemented this in cmp2lut.v, which should already be applied to iCE40. Is there an issue with that techmap?

The issue is that cmp2lut.v only works for comparisons that fit within a single LUT; this works across multiple LUTs.

As far as I can tell, in the Lattice flow, the $lut that's generated by cmp2lut.v gets techmapped to Yosys gates and eaten up by abc and mapped to LUTs again, so it doesn't need to map onto a single physical LUT. Of course the intermediate LUT data grow exponentially in size of the signal to be compared, so that is the issue with using it for wide comparisons. We might want to supersede cmp2lut.v with something like cmp2softlogic.v, even if by default we don't enable it for comparisons wider than the architecture LUT width.

That makes sense.


⚠ Processors has degraded performance

In a041bfe, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 75 ms

Resolved: Processors performance has improved in 8b64c96.


Add more files

Take more files into Account that are being ignored by Netbeans so far:

changelog
authors
contributing

These special files are very popular in modern git repositories like github or gitlab.

Instead of hardcoding more filenames: How about providing an option panel, where the user can configure it? I think a textfield for simple regex or comma-separated list of filenames would be fine.

:+1: That would be the best solution. Unfortunately I'm unable to implement this as I haven't created any NB plugin before.

@thomas-mc-work: It is not so difficult as you might think. It is mostly swing, with some specific NetBeans APIs to persist the settings.
http://netbeans.org/kb/trails/platform.html

Hi... When can I get the final nbm file to install it... the readme is aweome but this extra files make it better.
Good idea.


Mark the visionmedia/debug build as failure

Without this, node tests break.
This is a problem, as we are making those mandatory.
This fixes it by marking the test as expected failure instead
of skipped, so that we can track when it's working again, and
re-enable it.

Will xfail cause the test suite to fail if the test stops failing?

Rebased.

Will xfail cause the test suite to fail if the test stops failing?

Yes, on purpose! That will allow us to track when things are working again.


Refactor InputBar with Tip Tap Library

Description
This PR overhauls the fundamental workings of the input bar (distinct from the code definition, which includes the generation animation and additional logic). Specifically, this update replaces the complex, legacy code in the InputBar file, which previously managed a content-editable interface, with a new implementation powered by TipTap.
Enhancements introduced in this update include:

Improved handling of mentions, including fixes for typos and issues with copy/pasting.
Maintained styling of the Input bar which is now more restrictive with larger content.
Deactivation of the submit button when no content is present.
Significantly reduces the complexity of this part of the code.

🔈 Additional changes were made during the overhaul:

The input bar now clears text when switching conversations, aligning with the context-specific nature of conversation-assistant interactions. Although this design decision is up for debate, it could lead to future implementations preserving drafts across conversation browsing.

Pending issues to address include:

Implementing file type filtering during uploads to ensure only supported files can be selected (was already broken).
Adding scroll functionality to the @mention dropdown within the input bar, matching the usability provided by the right-hand call-to-action.
[ ] Placeholder should be removed on focus
[ ] Always display the mention dropdown around

🔮 Long-term enhancements on the horizon:

The interim solution of employing tippy.js (which by the way has poor TS types coverage -- hence the any) for positioning the dropdown when typing @ will need revisiting for potential dependency removal.

Undertaking such a refactoring carries the inherent risk of regressions. The input bar is a pivotal component, serving as the initial interface for users interacting with Dust. However, this modernization significantly reduces complexity, boosting our development velocity and simplifying maintenance. It also opens the door to effortlessly integrating text formatting features like bold, italics, and code blocks (which could be leverage to influence the models).
Tests

[x] Direct mentions
[x] Sticky mentions
[x] Selected assistant
[x] Copy / paste mentions
[x] Expanding (focus + close on submit)
[x] Assistant picker
[x] File picker
[x] Mobile screen size
[x] Big payload
[x] Copy / Paste external payload (code, text)

Design
The design does not change from the former implementation.

On mobile:

Oh and as per IRL let's move everything in an input_bar folder :pray:

Awesome work 🔥
As per slack, 2 small issues identified:

typing the handle in full doesn't turn the text into a mention (eg typing @dust doesn't make a mention)
using TAB doesn't allow to turn the text into a mention (existing input bar does that)

(but other than that you have my +1 as well)

Keen to see it shipped ! :+1: for me too

Just caught a little setTimeout() not being cleaned-up while debugging the missing file bug.

@lasryaric done :)


Are polygon rings closed?

The example of interpreting a polygon in the readme has the folllowing example:
geometry: {
  geometryType: 3 (esriGeometryTypePolygon)
  coords: [256, 256, 2, 0, 0, 2, -2, 0, 0, -2, 56, 56, 2, 0, 0, 2, -2, 0, 0, -2]
  lengths: [5, 5]
}

Can you confirm that the pbf representation for polygons does not close the rings? If this is the case, can it please be documented?
However, the 5th set of coordinates is  0, -2 which would not be a closed linear ring. We would expect 0, 0 to be a closed ring.
Edit: i misunderstood the delta-encoding portion here :) But still the question remains, are the rings closed? Not closing them makes sense from a reduced amount of data transfer

Additionally, what winding do Polygons take here? I understand the protobuffer implementation is based on Mapbox's which requires an OGC winding.

@JosiahParry the rings should be closed, as in the example above.
For winding, we use the Esri convention: exterior rings are oriented clockwise, while holes are oriented counterclockwise.

I understand the protobuffer implementation is based on Mapbox's which requires an OGC winding.

Hmm, I'd say the main similarities with the Mapbox VTL encoding spec are that both specs are built on top of Google's ProtocolBuffer spec. In terms of the geometry and value encoding of the features, they are quite different. Whereas the VTL basically specifies a preprocessed tile in isolation, the Esri pbf format doesn't really make sense without considering the parameters you pass the server.
We did originally experiment with returning attribute values in a way that was more similar to Mapbox, but we found that values like doubles just end up using way more space as for many datasets, features have unique attributes. For reused string data, which I believe is the main reason they took this approach, we instead have the option of using coded domains.

Regarding being related to Mapbox:
https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/protocolbuffer-binary-format-pbf-documentation-or/m-p/464692/highlight/true#M42964

@JosiahParry sorry I was probably confusing there when I was responding to the user, but there are several types of PBF-encoded data that Esri uses. PBF-encoded payloads from FeatureServices (what this repo is) -- in the JSAPI this would be consumed via a FeatureLayer. We also support Mapbox's VT spec with Esri's VT basemaps. Those would be confused by the JSAPI as a VectorTileLayer.


Simplest Single Source GPIO on and off Example.

This project is too bloated to understand as a beginner. I wanted to implement a simple GPIO on-and-off example. But in this project, every class tangled with each other. There is too much abstraction for an example project. This is no beginner-friendly project.
When things go with Python, it is 3 lines of code.

Import library,
setup GPIO,
.on() or .off() function.

Very simple, and understandable. But I don't like Python. It's not a good choice for long-term development.
Can we have a beginner-friendly single-source GPIO on-and-off example in the project?

Hi, indeed this project's use case is not the "simple getting started". But we have others for that:

Single Java file with JBang: https://pi4j.com/examples/jbang/jbang_minimal_example/
A bit more as a full Maven or Gradle project: https://pi4j.com/getting-started/minimal-example-application/


After upgrade folowup checks

Please describe the problem that your request should resolve.
After upgrading all dependencies, we need to check some of them on different environments
Describe the solution you'd like

Is it already possible to achieve the same outcome in any other way? If so, how?
No, environment dependant
Additional context

[x] Check Sentry collecting data on production
[x] Check Plausible collecting data on production
[x] Check sitemap on production

Checked, verified, approved


fix topic name length on database

Since we have controlled topic name length is less than 25, so we should change the name column's length.This will fix #5491

Codecov Report

Merging #5493 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #5493   +/-   ##
=======================================
  Coverage   37.56%   37.56%
=======================================
  Files         317      317
  Lines       46824    46824
=======================================
  Hits        17591    17591
  Misses      26734    26734
  Partials     2499     2499

Impacted Files
Coverage Δ

models/topic.go
54.7% <ø> (ø)
:arrow_up:

models/migrations/v68.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix: ensure glob finds all files in folders

For some reason {folders.value.join(',')} as part of the glob doesn't work and returns less files fixes #10228
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

yeah, super odd, but it was clearly visible when logging out the matched files


[ja] Translate content/en/docs/reference/glossary/service-account.md into Japanese

Note that this issue is for Japanese Speaker
This is a Feature Request
What would you like to be added
Translate content/en/docs/reference/glossary/service-account.md into Japanese
Why is this needed
There is no Japanese translation for this page
Comments

File to translate:

https://github.com/kubernetes/website/blob/main/content/en/docs/reference/glossary/service-account.md

URL (English):

https://kubernetes.io/ja/docs/reference/glossary/?all=true#term-service-account

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

Japanese Localization document: https://kubernetes.io/ja/docs/contribute/localization/

/area localization
/language ja
/triage accepted

/assign @t-katsumura


output

code is working but not outputing in a text file

You are right --output isn't yet supported, you can output using output redirect  Command > output.txt.
I have updated README to reflect the correct help menu

perfect thanks


Where can I find the joint hierarchy in the body tracking api code?

This is useful, but it would be better if I didn't have to "reinvent the wheel " to define the joint relationships in my code, if there was an api method to get this data structure/table.

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

ID: bfd96838-87c8-c27e-f8ee-a2db651ba463
Version Independent ID: ab4d754c-e83f-7d20-cd8c-690033684406
Content: Azure Kinect body tracking joints
Content Source: articles/kinect-dk/body-joints.md
Product: kinect-dk
GitHub Login: @qm13
Microsoft Alias: quentinm

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@andersand I am unsure I understand your request. Are you referring to this information
https://docs.microsoft.com/en-us/azure/kinect-dk/body-joints

Well yes, the parent/child bone relationship map. I implemented this myself as I was unable to find such map in the library. It's not a big deal, but would be nice to include.

This is an SDK enhancement. Please open issue on https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues?q=is%3Aissue+is%3Aopen

#please-close


[Builtins] Store 'BuiltinRuntime' lazily explicitly

This allows us to be more precise regarding how BuiltinRuntimes are stored and it allows us to implement a proper NoThunks instance for BuiltinsRuntime at the cost of introducing an indirection that slightly slows things down at runtime (may be undetectable, but let's see).
This is an EXPERIMENT, do not merge.

/benchmark plutus-benchmark:nofib

/benchmark plutus-benchmark:lists

/benchmark validation

/benchmark validation

/benchmark lists

/benchmark lists

/benchmark lists

^ -3.15% on average lol.

^ -2.18%. I don't believe it.

^ -2.84%. Ok, I'll look into it. I don't trust it still.

^ +1.76% on average.

^ -2.18%. I don't believe it.

Quick!  Merge it!

I thought this wouldn't be compatible with extensible cost models in the end, but it is compatible. Still GHC-8.10 doesn't like something. I'm closing this for now and I've added an entry about this issue to #4306 in case we want to return to it in future.


Update README.md : Introducing geometry and topology in advanced math

I am creating this pull request to geometry and topology lectures/texts after all the feedback and discussion in issue #21

Closes #21


Process triggers in a separate task queue

Instead of waiting on triggers to run before resolving action execution,
queue up the task in an in-memory queue and process it asynchronously.
The results of evaluating triggers, transformer filters and subscriptions don't have an effect on the outcome of the action execution can be safely deferred, making the action execution more responsive.
Change-type: patch
Signed-off-by: Lucian Buzzo<EMAIL_ADDRESS>

@LucianBuzzo Interesting stuff, this is effectively a queue for our queue correct? One thing to consider is what happens to the tasks in the in-memory queue when the service goes down due to a deployment/outage/etc. Currently, the server wouldn't return a response until the next action was enqueued, but with these changes there is no guarantee that subsequent action requests will be safely stored in Postgres before returning a 200 to the client. My only concern is that this may result in a higher chance of things silently failing.

Sorry, I had to do it. :joy:

@joshbwlng Yep you raise a good point, though we have the same issue right now. If a server has an unexpected shutdown, and the triggers are being checked, then the information would be lost and we would lose the data.
I spoke to @ramirogm about the idea yesterday and we had a few ideas to help with resilience.

Adding an additional queue is...icky. The work isn't distributed between available nodes and there's no cap on how big the queue can grow.
You could wrap the action execution and commit logic in a transaction, allowing you to roll back the work and retry the action request if the server goes down.
Using transactions causes issues for functions that take time to complete (processing triggers for example)
We could put the processing of triggers into a separate action and execute it separately
We likely do not want to wrap things like sync in a transaction (sync processes can be very slow), so I proposed the rule that if code communicates with the outside world, it needs to run in a transformer
The actions we make available should be a very small set, like maybe 3-4 actions functions
We also need to consolidate transformers, subscriptions and triggers (maybe streams as well), into a single method for listening to system changes

The root questions for me is, how do we scale triggers? There are lots of different answers to this and I think it's worth dedicating some cycles to thinking about how we can do it.

We could put the processing of triggers into a separate action and execute it separately

@LucianBuzzo I like the idea of putting the task of checking for and enqueuing triggered actions into the graphile-worker queue. This should be able to work hand-in-hand with running sync code in a transformer as well. As this is a system-wide queue that all workers consume from, this should also be quite scalable?

@joshbwlng Yep, I think you're right. It also has the benefit of using a single system for distributing work, allowing us to focus our effort and optimizations in one area. Any improvement to how we distribute work will help both use cases.

My main concern with re-enqueuing the work is that processing the triggers requires a snapshot of the contract that was inserted, and we would need to store that as an argument in the action request. This is wasteful in terms of storage, but also potentially exposes sensitive data and is another security consideration (create contracts have a similar issue).
Perhaps one approach we could try is to have the worker flush the trigger queue after completing the action execution, but before picking up another task. This would keep action execution snappy, but also make sure the queue doesn't get out of hand.

If we had a full implementation of versioned contracts in the system, I could imagine just providing the slug and specific version of the contract instead of a complete snapshot. Right now, that's not an option.
An alternative that came to mind was encrypting the snapshot to secure that sensitive data? This doesn't address the storage issue and also increases overhead as we would need to spend cycles encrypting and decrypting the data. Upsides being we wouldn't need to worry about flushing queues and the data in the queue would be more secure.


Remove response headers

@geneh,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

While certain HTTP Headers are necessary, the web server's identifying HTTP Headers are not necessary. Their inclusion inflates each HTTP response by around 100 bytes. Granted, 100 bytes is not much when taken alone, but when taken in the context of thousands or millions of requests over the course of time, those 100 bytes add up. Furthermore, providing identifying information can pose a security risk. An attacker who knows of a vulnerability in a particular web server and ASP.NET version combination could hunt for targets making HTTP requests to many different servers and flagging those that return the particular web server/ASP.NET version numbers.


"Add Undescribed Gall" creates a name that "Add/Edit Gallformers" rejects

"Add Undescribed Gall" form makes a name without enough hyphens to be accepted by "Add Undescribed Gall"

The red field in the screenshot above was auto-generated by "Add Undescribed Gall" but it should read:
"Asphondylia s-odora-bud-rosette"
instead.

@ddennism did this get resolved via the Slack conversation?


[AIRFLOW-2678] Fix db schema unit test to remove checking fab models

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2678
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Currently airflow doesn't include any model file for FAB. If fab is enabled, this unit test will fail(complaining fab model is removed)

IMO, since all the FAB models are external, we shouldn't check those models.
Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3548 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3548      +/-   ##
==========================================
- Coverage   77.33%   77.32%   -0.01%
==========================================
  Files         204      204
  Lines       15277    15277
==========================================
- Hits        11814    11813       -1
- Misses       3463     3464       +1

Impacted Files
Coverage Δ

airflow/models.py
88.27% <0%> (-0.05%)
:arrow_down:

Continue to review full report at Codecov.

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

I run the tests manually with RBAC enabled and they passed so I assumed the merging of the models worked. But I agree that they can be removed as there are now migration scripts for them.

@seelmann , I suspect when you run the test, the RBAC tables hasn't been created. I encounter this issue both in jenkins and local test.

hey Joy @jgao54 , could you take a look? thanks.

sounds good, agree it is not necessary right now.

thanks! lgtm :)


Delete unused entrypoint-celery.sh

worker and beat have their own entrypoint

Always approve dead-code removal :D


Fix Handbrake build on Darwin by turning off GUI support

Motivation for this change

Fix cairo build on macOS by disabling Xlib support.
Fix ffmpeg-full build on macOS by making sure that the nvenc option is not used.
Fix handbrake build by adding a dependency on lzma (for all platforms) and adding some Darwin-specific libraries and patches.
Fix mp4v2 build by building against the C++03 standard. The package has some code that is not valid under the newer standards.
Add video-transcoding, a set of scripts for transcoding, inspecting, and converting videos.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @codyopel @fuuzetsu @Anton-Latukha @wmertens

I’ve force-updated the branch so that it’s based on the latest nixpkgs master branch. I removed all of the commits except for the Handbrake one, since @vcunat was kind enough to cherry-pick some of the other commits earlier and, as @matthewbauer points out, the cairo changes don’t actually seem to be necessary. (I’ll open a new PR later to add the video-transcoding scripts that this PR used to include.) I also added some notes to the Handbrake default.nix file and added some commentary to the commit message; I didn’t change any of the code itself.
I want to apologize to all of you for this PR turning into such a mess—I should have broken it up into several separate, orthogonal PRs. I will definitely keep that in mind next time 🙂 Thank you everyone for the kind feedback and suggestions on this!

@GrahamcOfBorg build handbrake

@bdesham can you please look into the aarch64-linux failure if you get a chance?

I see

cp: cannot create regular file './internal_defaults.json': File exists

which does not seem related to this PR. It's probably some race in the build system, as on aarch64.nixos.community it was fixed by --cores 1.  Perhaps it will be better to disable parallel building?  It doesn't take too long.

@vcunat Is there anything I can do to move this PR along? I don’t have write access and I’m not sure which parallel-building setting you’re referring to.

I meant: aaf3881a.  (Easier done than explained.)

Thanks @vcunat!


"straight forward" should be replaced with "straightforward"

In the following sentence
"Porting to .NET Core (or .NET Standard) from .NET Framework for many projects is relatively straight forward"
"straight forward" should be replaced with "straightforward"

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

ID: 577db847-e424-a9dc-ee2d-f2c6ddb54600
Version Independent ID: 5fa219d8-0c9c-c758-c1ee-17cefd75ca24
Content: Port from .NET Framework to .NET Core - .NET Core
Content Source: docs/core/porting/index.md
Product: dotnet-core
GitHub Login: @cartermp
Microsoft Alias: phcart

Fixed in https://github.com/dotnet/docs/pull/21475


Make addProcess() parallel

Following Crosby's patch, this commit makes launching health-check processes faster when many health-checks occur simultaneously.
It helps avoiding health-check timeouts that Paypal ran into. (FIELD-2190)
In addition, this commit adds a lock to protect accessing to 'processes' map of the container.
Signed-off-by: Xinfeng Liu<EMAIL_ADDRESS>

Need wait for travis CI fix https://github.com/docker/containerd/pull/11 to be merged first.


Add a Billing Contact email field to Public Cloud provisioning form

Some teams working in public cloud would like to have a copy of their quaterly billing report sent to a specific email. Right now only Product Owners listed on the project form receive the quaterly billing reports and have to foward the reports to the team's Financial Advisors or Expense Authority manually. It would be helpful to have a copy of the report sent to another email address of their choise.
Definition of Done:

[ ] A new field "Billing Contact" added to the provisioning form for public cloud requests that collects a valid government email (not IDIR, as it can be a shared team mailbox that is not associated with an IDIR).

This functionality is no longer relevant as we will be managing billing contacts via the user management feature (tracked in a different ticket).


AnimationGroup: Add masking support

I create the PR as a draft, for discussion (is it the right design? what about the class / function names? ...)
The aim is to be able to create a mask for an animation group and not play animations for targets that are not in the mask.
The mask (AnimationGroupMask) is simply a set of target names. It's a set of strings instead of TransformNode / Bone / ... so that a single mask can be used for several animation groups.
By way of illustration, in the Avatar PoC, I can remove the custom functions RemoveIdentityTransformationsFromAnimationGroup and RemoveTargetsFromAnimationGroup and replace them with something like :
const animationGroupMask = new BABYLON.AnimationGroupMask([<list of bone names used by the facial animation>]);

this._facialAnimationGroup.mask = animationGroupMask;
this._facialAnimationGroup.removeUnmaskedAnimations();

There's no hurry to review the PR, so don't bother if you're on vacation!

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14119/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14119/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14119/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14119/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14119/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14119/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14119/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14119/merge#BCU1XR#0

Any update on this? are you waiting for feedback from @PatrickRyanMS ?

Tagging @bghgary for the Set usage ?

Tagging @bghgary for the Set usage ?

Looks like we already use Set in a number of places in the code. I just tested using it with Chakra and it works. The only method I see that is missing is size.
+		add	function add() { [native code] }	Object, (Function)
+		clear	function clear() { [native code] }	Object, (Function)
+		delete	function delete() { [native code] }	Object, (Function)
+		entries	function entries() { [native code] }	Object, (Function)
+		forEach	function forEach() { [native code] }	Object, (Function)
+		has	function has() { [native code] }	Object, (Function)
+		keys	function values() { [native code] }	Object, (Function)
+		values	function values() { [native code] }	Object, (Function)


Enhancements in EC2 and Added Support for AMIs

This PR does the following:

Currently the auto_scaling_groups.py code does not use the UNWIND approach, instead it uses loops to populate the AWS resources. This PR rectifies that. Additionally, some more attributes of AutoScalingGroups are populated.

Some additional useful attributes missing from EC2 Instances and Subnets get populated too! Corresponding changes have been made in the documentation. (I specifically didn't add the UNWIND approach here because I wasn't quite sure of the code structure here and I didn't want to break things 🙈)

The documentation for Auto Scaling Groups was missing all this while. Added it!

And the one major update in this PR is - Added support for Amazon Machine Images (AMIs) - images.py in the ec2 folder.

@achantavy All suggested changes as per your review are done here. Anymore changes required? :)


Update case-study-using-the-stabilization-plane-to-reduce-holographic…

…-turbulence.md

Docs Build status updates of commit 33cc80a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/case-study-using-the-stabilization-plane-to-reduce-holographic-turbulence.md
:white_check_mark:Succeeded
View

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.


Update classifier.py

this would allow it to classify all the images in a given directory, rather than selecting a single image each time

Hi @gupta-keshav! Thanks for the PR!
classifier.py is a helper script for visualising face recognition result on a single image. I thinks it's bad UX to process all images from directory because that's potentially a lot of images which will open a lot of windows for user. classifier.py was written to quickly check result on a single image, not a batch of images.
Could you please explain me your concrete use-case in more detail so I can get a better sense why you would need this change?

Hey @ldulcic ,
It is common to test on multiple images rather one image as it is not possible to estimate how well the model performs from just a single image, moreover if not renamed images names are usually quite long and it quickly becomes cumbersome to test multiple of them. Multiple Windows can be handled by just removing the previous window before displaying the current one. If classifier.py is intended for single images maybe It is possible to add classifier_batch.py for multiple images.

Hey @gupta-keshav,
I think another script is a better solution. I just pushed util/tag_images.py script in develop branch.
You can run it like this:
python -m util.tag_images --input-folder path/to/input --output-folder path/to/output

Does this cover your use case?

Yes, Thank You!


Error when installing kubeai

Install kubeai according to the steps prompted by the official website documentation. When proceeding to helm installation, the error message cannot be installed as shown in the figure below. How to solve it?

Thanks for sharing the details. I am not able to reproduce this, but some other user was. I plan to put in a fix anyway, but could you share:

Helm version
Kubectl version
K8s distro and version

This has been fixed in the latest helm release.
@flightefore can you please run help repo update and try again?  I would like to confirm that it's fixed now.
Make sure you use the helm chart version 0.4.2.


[Mapping issue] Why is 4214962 in condition occurrence?

Describe the problem

One of the most common codes (15% in a sample I took) in the condition occurrence table is "Blood pressure finding" 4214962 https://athena.ohdsi.org/search-terms/terms/4214962. Should this information instead be in the measurement table, ideally with the value?

Affected databases
cdm_gold_202301
Tag for awareness
@ajoedicke @daniprietoalhambra

That would be ideal
On 13 Feb 2024, at 15:22, edward-burn @.***> wrote:

Describe the problem

One of the most common codes (15% in a sample I took) in the condition occurrence table is "Blood pressure finding" 4214962 https://athena.ohdsi.org/search-terms/terms/4214962. Should this information instead be in the measurement table, ideally with the value?

Affected databases
cdm_gold_202301
Tag for awareness
@ajoedickehttps://github.com/ajoedicke @daniprietoalhambrahttps://github.com/daniprietoalhambra
—
Reply to this email directly, view it on GitHubhttps://github.com/oxford-pharmacoepi/cdm-etl-gold/issues/23, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJXXJRU6OSP3R447OZBP4A3YTNZIXAVCNFSM6AAAAABDGTDB5CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTENBUGA3TGMY.
You are receiving this because you were mentioned.Message ID: @.***>

@edward-burn
I use public_100k as an example.
These conditon_occurrence records were mapped from the following Read Codes.
And the mapping is provided by Athena.

condition_concept_id
condition_source_value (in public_100k)
count (in public_100k)

4214962
246..11
55146

4214962
246..12
3657

4214962
246Z.00
189

4214962
246..00
510087


[feature]:  Automatically Comment on Issue Raise

Is there an existing feature request for this?

[X] I have searched the existing issues

Detailed Description
I propose implementing a feature that automatically comments on an issue when it is raised. This comment will serve as an acknowledgment to the contributor for bringing the issue to our attention and provide any necessary guidance or next steps.
Use Cases and Benefits
No response
Priority/Impact
Medium

Hello @thevijayshankersharma, hopefully I can help you with this. According to my understanding, an auto-comment should be generated when an issue is raised with all the guidelines and necessary details, so that the contributor can know about the issue.
You can use Github Actions auto comment for this. I can handle this. Please assign this issue to me under GSOC '24.
@aryasoni98


Enable some privilege

By default, this workflow was not able to fetch code from the message, you just need to set something in the system settings -> Privacy & Security, give Full Disk Access and Accessibility. Then, it should be able to work. Thank you! This is a wonderful project.

Thanks for reporting! I will update the documentation accordingly and see if there is a way to check.
Any chance you can share a screenshot of the Settings screen?

Sure, these are my settings. Hope these help.

I have added this check in the latest release. Thanks for reporting it!


rasterio

mtpy-v2 and aurora seem to be installing different versions of rasterio on python 3.8.
Rasterio 1.3.11 was released about 10h ago from this message.  Last good 3.8 mtpy build was ~20h ago.
On mtpy:
Collecting rasterio (from mtpy-v2->aurora==0.4.1)
  Downloading rasterio-1.3.10-cp312-cp312-manylinux2014_x86_64.whl.metadata (14 kB)

On Aurora:
Collecting rasterio (from mtpy-v2==2.0.9)
  Downloading rasterio-1.3.11.tar.gz (413 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [3 lines of output]
 <string>:22: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
      WARNING:root:Failed to get options via gdal-config: [Errno 2] No such file or directory: 'gdal-config'
      ERROR: A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.
      [end of output]

@kujaku11 FYI: you may need to pin rasterio <1.3.11 for now.

Hmm, maybe a glitch associated with the new rasterio.  It went away after a couple days.


fix: prevent blueprint migrations which inserted playout-gateway subdevices on a fresh install from failing

Even though the typings state it shouldn't be undefined, settings.devices is undefined here on a fresh install until at least one subdevice has been added to the playout-gateway. Before this fix, it would have to be added manually via the settings page before any blueprint migrations which also tried to insert devices could run successfully.
It's possible that there is a better place for this fix, but after a couple hours of searching I couldn't find the root cause.

Codecov Report
Base: 68.34% // Head: 88.78% // Increases project coverage by +20.44% :tada:

Coverage data is based on head (04825f2) compared to base (4cad186).
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff               @@
##           release46     #792       +/-   ##
==============================================
+ Coverage      68.34%   88.78%   +20.44%
==============================================
  Files            277       10      -267
  Lines          33895     2355    -31540
  Branches        4537      304     -4233
==============================================
- Hits           23166     2091    -21075
+ Misses         10281      263    -10018
+ Partials         448        1      -447

Impacted Files
Coverage Δ

meteor/server/api/blueprints/migrationContext.ts

...teor/server/api/ingest/mosDevice/mosIntegration.ts

packages/job-worker/src/ingest/mosDevice/diff.ts

meteor/lib/logging.ts

meteor/lib/api/client.ts

packages/job-worker/src/ingest/cleanup.ts

meteor/server/api/integration/mediaWorkFlows.ts

meteor/lib/database.ts

packages/job-worker/src/ingest/rundownInput.ts

meteor/lib/collections/IngestDataCache.ts

... and 257 more

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

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


Export acclogp! and getlogp?

Just noticed in https://github.com/SciML/DiffEqBayes.jl/pull/158 that we don't export acclogp! and getlogp. Maybe we should do that, now that @logpdf was removed?

Sounds good to me.


Chromium's font rendering color inaccurate

Font rendering in Chromium has a problem: the color is inaccurate. While it's not serious for a web browser, it's serious for a code editor. I was so frustrated when writing a syntax theme. Can GitHub do something to tweak Chromium's font color to what it should be?
To show everybody the problem, I made a comparison between 3 browsers. First, take a look at 13px font in Chrome (same effect as Atom). Left is black, right is rgb(0,128,0) green:

It's a little darker. What's the correct color? Let's take a look at Firefox and Safari's:
Firefox:

Safari:

Chromium has a -webkit-font-smoothing css property, set to "subpixel-antialiased" by default. If changed to "antialiased", it becomes too bright:

My conclusion is: whatever smoothing strategy I choose, it's inaccurate. Either too dark or too bright. It will become more serious if the font is even smaller.
Let's look at an extreme case (8px using default smoothing. not practical, just to show the problem):

In Chrome it became completely black.
Firefox:

Safari:

Before my test, I thought it's a Webkit problem, but now I tend to think it's a Chromium problem, because Safari is OK.
Update:
Seems it's caused by anti-aliasing. If you set -webkit-font-smoothing to none, then the color is correct, but the font looks ugly. Maybe Webkit has some internal parameters that control the anti-aliasing, but Chromium did not tune it to its best? That's why Safari's font color is OK? I don't know.
Update:
If React editor is enabled (default in v0.117), then it will be too bright rather than too dark.

This has been solved, right? cc @simurai @as-cii

I can still reproduce this:

It looks like they use different subpixel-aliasing (orange on the left, blue on the right). Like the vertical line of b and d is blue in Atom, but green in Safari. And Atom uses a darker orange.
I don't think we can do much about it. And that Chromium issue seems stale. Maybe just be aware when porting an existing theme to Atom to compare screenshots, and adjust if needed.

I don't think we can do much about it. And that Chromium issue seems stale. Maybe just be aware when porting an existing theme to Atom to compare screenshots, and adjust if needed.

I think they archived the issue because there was no activity after a year. Honestly I agree that there isn't much we can do about it: subpixel anti-aliasing is problematic in so many ways but we have to rely on Chromium for it to work, or simply disable it everywhere (which would cause other text display issues).
Still, I feel like we may close this as it's not really related to Atom but to Electron/Chromium. Thoughts? :thought_balloon:

I agree with closing this as it isn't something we have control over ... or at least obtaining control would be far too costly at this stage. Since this bug boils down to "we don't render the same as native rendering", the only way to truly fix it (in all its variations) is to start using native rendering ... and I don't believe we are likely going to stop using Chromium for our rendering engine any time soon?


Update values.py

Adding a fingerprint i am currently using for the 2022 Bolt EV / Bolt EUV for testing purposes.

your edited will be commented out.
this is un-runnable PR.


confused rgb/bgr?

Hi thanks for the great work!
I am quite confused about this code segment in the Transformer_explainability.ipynb notebook:
# create heatmap from mask on image
def show_cam_on_image(img, mask):
    heatmap = cv2.applyColorMap(np.uint8(255 * mask), cv2.COLORMAP_JET)
    heatmap = np.float32(heatmap) / 255
    cam = heatmap + np.float32(img)
    cam = cam / np.max(cam)
    return cam

def generate_visualization(original_image, class_index=None):
    transformer_attribution = attribution_generator.generate_LRP(original_image.unsqueeze(0).cuda(), method="transformer_attribution", index=class_index).detach()
    transformer_attribution = transformer_attribution.reshape(1, 1, 14, 14)
    transformer_attribution = torch.nn.functional.interpolate(transformer_attribution, scale_factor=16, mode='bilinear')
    transformer_attribution = transformer_attribution.reshape(224, 224).cuda().data.cpu().numpy()
    transformer_attribution = (transformer_attribution - transformer_attribution.min()) / (transformer_attribution.max() - transformer_attribution.min())
    image_transformer_attribution = original_image.permute(1, 2, 0).data.cpu().numpy() # chw -> hwc (rgb)
    image_transformer_attribution = (image_transformer_attribution - image_transformer_attribution.min()) / (image_transformer_attribution.max() - image_transformer_attribution.min())
    vis = show_cam_on_image(image_transformer_attribution, transformer_attribution)
    vis =  np.uint8(255 * vis)
    vis = cv2.cvtColor(np.array(vis), cv2.COLOR_RGB2BGR)
    return vis

image = Image.open('samples/catdog.png')
dog_cat_image = transform(image)

fig, axs = plt.subplots(1, 3)
axs[0].imshow(image);
axs[0].axis('off');

output = model(dog_cat_image.unsqueeze(0).cuda())
print_top_classes(output)

# cat - the predicted class
cat = generate_visualization(dog_cat_image)

# dog
# generate visualization for class 243: 'bull mastiff'
dog = generate_visualization(dog_cat_image, class_index=243)

axs[1].imshow(cat);
axs[1].axis('off');
axs[2].imshow(dog);
axs[2].axis('off');

as you can see, the image_transformer_attribution is loaded through PIL and transformed by pytorch, so it is in the RGB order.
however, the heatmap is constructed through cv2, so I assume it is in the BGR order? So why we can directly add them together i.e., cam = heatmap + np.float32(img) when they are not in the same color space?
Please correct me if my understanding is wrong here. Thanks!

Hi @Tsingularity, thanks for your interest!
I apologize for the delay in response.
This code was adapted from this great repo.
If I recall correctly, it also contains full documentation of all the details.

Thanks for the reply and reference.
But could you please check the notebook code above and my question in detail? I am not saying the attention code is incorrect. It just seems the visualization part is a little bit buggy in terms of 'BGR / RGB'.
Thanks!

I was actually referring to this code it’s exactly the code that applies the heatmap to the image that you copied here.
Does this help your confusion?

Thanks for pointing the reference code.
But I am afraid that's where the bug comes from? I mean as u can see in the original code, it is using 'BGR' by default (for both img and mask).
However, in ur notebook code above, the input image image_transformer_attribution is in RGB, but the mask heatmap = cv2.applyColorMap(np.uint8(255 * mask), cv2.COLORMAP_JET) is in BGR. And u directly add them together while they are actually in different color space:cam = heatmap + np.float32(img). That's the reason why I think it doesn't make sense here.
But I could be wrong anyway. Feel free to correct me if there's something incorrect in my understanding.
Thanks!

I understand your point, I'm really no expert in these BGR/RGB games, when I try applying the code with the RGB conversion (L. 40 in the reference code), I get identical heatmaps.
It is possible that this is working due to this conversion in the notebook code (in generate_visualization):
vis =  np.uint8(255 * vis)
vis = cv2.cvtColor(np.array(vis), cv2.COLOR_RGB2BGR)

If you wish to use the RGB conversion from L. 40, you can simply remove the above 2 lines like this:
def show_cam_on_image(img: np.ndarray,
                      mask: np.ndarray,
                      colormap: int = cv2.COLORMAP_JET) -> np.ndarray:
    """ This function overlays the cam mask on the image as an heatmap.
    By default the heatmap is in BGR format.
    :param img: The base image in RGB or BGR format.
    :param mask: The cam mask.
    :param use_rgb: Whether to use an RGB or BGR heatmap, this should be set to True if 'img' is in RGB format.
    :param colormap: The OpenCV colormap to be used.
    :returns: The default image with the cam overlay.
    """
    heatmap = cv2.applyColorMap(np.uint8(255 * mask), colormap)
    heatmap = cv2.cvtColor(heatmap, cv2.COLOR_BGR2RGB)
    heatmap = np.float32(heatmap) / 255

    if np.max(img) > 1:
        raise Exception(
            "The input image should np.float32 in the range [0, 1]")

    cam = heatmap + img
    cam = cam / np.max(cam)
    return np.uint8(255 * cam)

def generate_visualization(original_image, class_index=None):
    transformer_attribution = attribution_generator.generate_LRP(original_image.unsqueeze(0).cuda(), method="transformer_attribution", index=class_index).detach()
    transformer_attribution = transformer_attribution.reshape(1, 1, 14, 14)
    transformer_attribution = torch.nn.functional.interpolate(transformer_attribution, scale_factor=16, mode='bilinear')
    transformer_attribution = transformer_attribution.reshape(224, 224).cuda().data.cpu().numpy()
    transformer_attribution = (transformer_attribution - transformer_attribution.min()) / (transformer_attribution.max() - transformer_attribution.min())
    image_transformer_attribution = original_image.permute(1, 2, 0).data.cpu().numpy()
    image_transformer_attribution = (image_transformer_attribution - image_transformer_attribution.min()) / (image_transformer_attribution.max() - image_transformer_attribution.min())
    vis = show_cam_on_image2(image_transformer_attribution, transformer_attribution)
    return vis

Here are the heatmaps in both cases:
original:

with RGB conversion:

Since the heatmaps are identical in both cases, I guess this does not make much of a difference, but thanks for pointing this out!

thanks for looking into this issue and re-running the visualization code.
I also just wrote a correct version on my end and got the same results as u showed above. It's interesting to see this issue (seemingly) doesn't affect the final image output at all.
Since the code is in notebook and I find it hard to make a pull request inside jupyter notebooks, I'll just leave the modification work to u :)
Thanks for the help again!


add a github action workflow for the publishing of the jupyter Book

I have added a workflow called CI_deploy_book.yml to the update_doc branch. This is based on the example from jupyter-book. The action still needs to be tested though.
As the action fully builds the jupyter-book, I think it's best to remove the folder ./jupyter_book/_build/ from the repo and add it to the gitignore as it is generated content that's no longer required.

This workflow is active.


Add support for Apple iOS maker notes

Add a parser for makernotes written by Apple iOS devices.  I originally added this to extract the burst UUID values that iOS devices write to collect burst images together.
Note: Until this PR lands you can use this code to add apple makernote parsing right now.

This PR is now broken and won't work correctly with goexif now due to changes in #60.


Warn about conflicting packages

Describe the bug
When having multiple packages in packages that have conflicting commands (or libraries) it isn't clear which one of the packages is used.
One example is:
languages.c.enable = true;
packages = [ pkgs.clang_14 ];

languages.c.enable adds pkgs.clang, so the resulting packages is:
[ pkgs.clang pkgs.clang_14 ]

When using clang you'd be using the pkgs.clang one and not the one from pkgs.clang_14.
There are a number of things that devenv could be doing:

Prioritize packages that were added last
Error when 2 packages have conflicting binaries
Warn when 2 packages have conflicting binaries

To Reproduce
{ pkgs, ... }:
{
  packages = [ pkgs.clang pkgs.clang_14 ];
}

The resulting clang command is the one from clang not the one from clang_14.
Version
0.5

The last one should prevail, need to look into why that's not happening (maybe we're reversing the list at some point?)


Cloud announcment rewrite

I think I spent more time thinking about what we should write than actually writing. I settled on a simple tutorial that's basically the same thing as running fluvio. The point behind doing it here is that it highlights the core value proposition of fluvio cloud - Building a streaming data app without the hassle of devops.
Our first version of this just had too much "About Fluvio" and not enough "about fluvio cloud". We don't have enough features yet to have something like the EKS AWS announcment but we will eventually. So, in our case, it's a bit more terminal stuff than graphics of the website.
It's not quite the same but this is what the post looks like rendered.

My original reasoning behind the announcement was dual purpose. Announce the cloud but also tell users what Fluvio is. We don't have the AWS brand, hence a Cloud centric message is not all that helpful if people don't know what it does.

My original reasoning behind the announcement was dual purpose. Announce the cloud but also tell users what Fluvio is. We don't have the AWS brand, hence a Cloud centric message is not all that helpful if people don't know what it does.

Yeah, I get it. It'll take time to build the audience. If I were to come across the last post I wouldn't have read it. It was too markety and not enough "how do I build stuff". I'll admit that I'm only part of the main demographic here. Engineers know how to read and how to navigate docs, we just want to get them reading and using fluvio. Let's not distract them with a ton of stuff.
Also, there's a post Why we build fluvio but it looks unpublished?


The connection to the server localhost:8080 was refused - did you specify the right host or port?

Tutorials: https://developers.sap.com/tutorials/btp-app-kyma-prepare-dev-environment.html
In Step 4: Log in to your Kyma cluster
After downloading the .yaml file from KubeconfigURL, manual copy may not work properly as defined in the tutorial (MacOS). Because, its difficult to find .KUBE folder in mac & in many case it is not visible at all even with ls -A command in terminal. Any further commands like "kubectl create namespace risk-management" will throw following error message.
"The connection to the server localhost:8080 was refused - did you specify the right host or port?"
To over come this -> Easy way is to set the environment with EXPORT KUBECONFIG=<Downloaded .yaml file path>.
This means, right after downloading the .yaml, in the VS Code terminal write ----> EXPORT KUBECONFIG=.
For ex, it should look like this -  EXPORT KUBECONFIG=/Users/abc/Downloads/config.yaml
I feel, this is much easier to set the environment & this should work irrespective of OS. However, I'm submitting this for your review. Please check and add this hint too, it may help someone else who is puzzled with 8080 refusal error.
Reference Blog / Tutorial : https://developers.sap.com/tutorials/btp-kyma-extension.html#d1e76efd-61f4-420c-a9db-12c4615ed635

@smahati please respond to the user's feedback.  Thank you.

Hello,
Sorry for the delay, unfortunately the Kyma tutorials have been retired please take a look at the new tutorial "Incident Management" for the latest tutorials.
Best regards,
Mahati


When saving Pharo methods in Coder we should convert line breaks to CR

This was addressed in #1257


Disable printing -e in count.sh

Wouldn't this also be fixed by changing #! /bin/sh to #! /bin/bash?

I suppose so, yes.


updated versions, properties, docker images

Renamed to MenuRepository as both dynamodb and cosmosdb have to have the same MenuRepository in order to be used at runtime based on profile. MenuRepository is used in cqrs and cqrs-events projects
I've also updated the configuration to load the properties based on the profile

/azp run

/azp run

/azp run

/azp run

/azp run


Show all 'Application suitable' statuses as the same colour

We need to ensure that all application suitable statuses are the same colour for now, as they are semantically the same for users.

should we expand this commit message little to explain in more detail why we think it's wrong to rely to a colour change to distinguish between:

accepted with placement request
accepted without placement request

My understanding is that using colour is unreliable for accessibility reasons and we recommend relying on the separate call to action in the "actions" column e.g:

"View placement requests"
"Create placement request"

@edavey this is actually a defect left from #1759 unrelated to APS-651 but all the more reason to leave a more comprehensive commit message. Thanks for the prompt


Start implementing muted users

Related: #4655
Tested by opening the app, and running the following commands in my terminal:
curl -sSX POST https://chat.zulip.org/api/v1/users/me/muted_users/19335 -u wesleyac@zulip.com:MY_API_KEY
curl -sSX DELETE https://chat.zulip.org/api/v1/users/me/muted_users/19335 -u wesleyac@zulip.com:MY_API_KEY

And using the debug console to verify that the correct data got added to the redux state.

Ok, fixed all of those comments, and also went ahead and pushed the initial version of hiding messages from muted users in the MessageList. Should be ready for another look :)

Ah, a few of my fixes here are in the wrong commit. I'll fix that in a moment.

Ok, fixed up the commit history.
Also, here are screenshots of what the UI looks like.

@gnprice should be ready for another review :)

OK, so of these commits:
2d77cfeeb initialDataTypes: Add MutedUsers.
01b763872 Redux: Add muted_users reducer.
2298150bc directSelectors: add getMutedUsers.
82d92ab4d backgroundData: Add muted_users.
ff1773692 css: Rename widget class to special-message.
d445419eb webview: Add initial support for hiding muted messages.
5cc0ee049 webview: Allow revealing messages from muted users.
dff038514 caughtUpReducer: Fix bug that overwrote CaughtUp state.
aad5b966c webview: Coalesce consecutive muted messages.
2c2dfbcf5 webview: Add note about alternative to getMessageNode.
f78745bde PmConversationList [nfc]: Convert to functional component.
e9298d3d3 PmConversationList: Hide PMs from muted users.
0267617b1 contentHtmlFromPieceDescriptors: Switch to object for args.
13e530e46 messageAsHtml: Translate muted-user text.
I'm merging versions of these:
2d77cfeeb initialDataTypes: Add MutedUsers.
01b763872 Redux: Add muted_users reducer.
2298150bc directSelectors: add getMutedUsers.
82d92ab4d backgroundData: Add muted_users.
ff1773692 css: Rename widget class to special-message.
2c2dfbcf5 webview: Add note about alternative to getMessageNode.
0267617b1 contentHtmlFromPieceDescriptors: Switch to object for args.
The merged commits are:
10a07b9a9 api: Add types for muted users; add muted_users to requested data.
14ee13e1a muted users: Add data to Redux state.
c438b54b9 muted users tests [nfc]: Compact object literals to 1 line, vs. 4.
efb301b56 muted users tests [nfc]: Inline small actual/expected expressions.
b67e440c3 muted users tests [nfc]: Factor out boring arbitrary base state.
c8ed0b08f muted users tests: Use eg.otherUser and eg.thirdUser.
c7c58c894 example data [nfc]: Describe the "action fragments" idea more clearly.
0a66a1af0 example data [nfc]: Describe when to define example actions here.
f0c01d079 msglist: Add muted_users to backgroundData.
aeb56ec23 msglist css [nfc]: Rename widget class to special-message.
954a67fb5 webview js [nfc]: Add note about alternative to getMessageNode.
713f1c6f7 msglist html [nfc]: Use an args object for contentHtmlFromPieceDescriptors.
Do take a look. The main changes are:

I squashed the directSelectors commit into the Redux commit, and moved a few of the changes from the Redux commit ahead into the API commit -- specifically the parts that are basically more of the API binding, so that all the API-binding changes are in one commit.

That means the API commit now includes the changes to src/api/eventTypes.js, and also the corresponding bits to turn that event into a Redux action, because those bits are (thankfully) just boilerplate.

I added [nfc] to summary lines where appropriate.

Hmm, I guess that isn't in our style guide! It is documented in our glossary. I should go add it to the style guide (which I think we hadn't started yet when I wrote that entry.)

I revised some summary lines mostly to make the prefixes broader, like changing "contentHtmlFromPieceDescriptors" to "msglist html", and putting the specific function name in the later part of the summary line.

This looks like it may not really be explained anywhere in any detail; it probably should be! But as the Zulip-wide Git style guide says briefly, that prefix is generally "the name of the subsystem". So "the message list" or "the HTML generation for the message list" is a good match for the "subsystem" level of generality we're going for there. Sometimes I'll do a quick git log src/foo/ to see how we've referred to a given subsystem in past commits.

I wrote some additional commits to tighten up the new test file along the lines I had in mind up at https://github.com/zulip/zulip-mobile/pull/4678#discussion_r616363607 . These are split out into commits more finely than I probably would otherwise do, to help make visible the different things I'm doing there. In net the file gets 22 lines shorter, and the two very simple tests become one line each.

I also added there a couple of changes to exampleData.js that hopefully make clear some things that really weren't written down there before -- so thank you for running into those :slightly_smiling_face:

And merged those commits -- thanks again @WesleyAC!
Because this thread has gotten unwieldy for GitHub (with parts of it hidden to keep their page-load numbers good, etc.), let's pick up the rest on a new PR. I've pushed a rebased version to my repo as a branch dev-muted-users -- the commits are:
9cb90e820 caughtUp: Fix bug that overwrote CaughtUp state.
84aa24f32 webview: Add initial support for hiding muted messages.
c83092f8b webview: Allow revealing messages from muted users.
b738acea0 webview: Coalesce consecutive muted messages.
1391b41ca PmConversationList [nfc]: Convert to functional component.
16fbb4735 PmConversationList: Hide PMs from muted users.
89b8f95cc messageAsHtml: Translate muted-user text.

One thing I noticed on the caughtUp commit, just before I was going to merge with it included:
-        caughtUp = { older: action.foundOldest, newer: action.foundNewest };
+        caughtUp = {
+          // $FlowIssue[unnecessary-optional-chain]
+          older: state[key]?.older || action.foundOldest,
+          // $FlowIssue[unnecessary-optional-chain]
+          newer: state[key]?.newer || action.foundNewest,
+        };

What happens if state[key] is indeed absent?
I believe we'll end up with the right result -- false or true for each value, depending on the data in action -- but it's a bit subtle. In particular if we had the two sides of the || in the other order, which looks pretty innocuous, I believe it'd go wrong and stick an undefined in there when foundFooest was false.
So it'd be good to make the fallback logic here more explicit. I think the logic at the end of legacyInferCaughtUp above is pretty effective for this:
  const { older: prevOlder, newer: prevNewer } = prevCaughtUp || DEFAULT_CAUGHTUP;

  return {
    older: prevOlder || caughtUpOlder,
    newer: prevNewer || caughtUpNewer,
  };

Where the jsdoc on DEFAULT_CAUGHTUP is:
/** The value implicitly represented by a missing entry in CaughtUpState. */


file format

I read with the utmost interest your description of Sitrano and I am eager to try it, but I don't have Matlab... just the runtime.
Anyway that you can compile the thing in a format that can be run with the runtime?
Thanks,
Nimus

Hi Nimus, thanks for your message. I will have a look at this and try to compile it asap!

Hi Leonardo,
Thank you so much, it will be deeply appreciated.
Nimus
On Wed, Jul 19, 2023 at 12:10 AM Leonardo Fierro @.***>
wrote:

Hi Nimus, thanks for your message. I will have a look at this and try to
compile it asap!
—
Reply to this email directly, view it on GitHub
https://github.com/himynameisfuego/SiTraNo/issues/3#issuecomment-1641539090,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA43VSLZSERHP3NPL7XTEHDXQ6B63ANCNFSM6AAAAAA2PKC32Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

HI Leonardo,
Any chances of the compilation coming before you become too busy with the new academic year?

HI Leonardo, Any chances of the compilation coming before you become too busy with the new academic year?

Sorry I haven't had any time for this, I am trying to complete my disseration by early October. So I would expect the compiled version to be out by mid October

Yeah!
Best of luck with your dissertation BTW!

Hi Leonardo,
I got the Juce version to get me started but it is not as complete as yours. Are we still on track to get a compiled version sometime soon?

Hi Leonardo, I got the Juce version to get me started but it is not as complete as yours. Are we still on track to get a compiled version sometime soon?

@nimusd I have produced a compiled version. I will polish a couple of things and add it to the 1.1 release files by the end of today!