RFC security policy

After fixing #3003 and the more or less uncontrolled disclosure of security information, I sat down to write the following RFC. It is not urgent (especially because it is a slightly long text) and might only be a start of a discussion. Feel free to add your comments or criticize it. At a certain point of consensus, I can create a PR out of the material.
Security Policy (draft)
Invenio reached a state where the impact of security holes and possible exploits
is not only a problem for smaller project, but for bigger installations
worldwide and therefore the organizations using them. This RFC makes
suggestions on

how to handle security bugs of a certain impact level
which developers should have which permissions regarding the information
about unpatched security bugs
how users, administrators and external developers should report certain types
of bugs or the usage of exploits
how we ensure to be an open project even when dealing with classified
information

Severity Classification
There exist several classifications from different organizations, e.g.
CVSS. These might sued the needs of
bigger organizations. For Invenio, the following simplified model might work
better.
High Severity
Description: A security hole that impacts running installations of released
versions of Invenio (e.g. no pre-releases or developer configurations) in a way
that it is possible to gain unprivileged access to data, to destroy data, to
leak user information, or to render a system unusable with a significant lower
effort than usual; all of that on layer that is reachable by endusers.
Examples: bypassing user authentication, remote code execution, XSS, SQL
injections, producing very high server load by malformed inputs.
Permissions: Only a small dedicated group of core developers is allowed to
retrieve this information. Other people should only be involved if it is crucial
for fixing the problem.
How to report: The bug or usage of certain exploits should only be reported
to a closed mailing list which is only readable by people of the given
permission level.
Disclosure: The patch nodes must contain a remark that it is a security
patch for a High Severity problem. There must not be a public disclosure on
mailing lists, forum entries, issue tracker or version control system before
a certain level of installations is patched. After it is considered safe to
release the information, it must be added to the public repositories and an
issue with a problem description and solution must be created.
Low Severity
Description: A security problem that does not affect installations directly.
This might be the case because it is not the first layer but a backbone system,
because it requires a misconfiguration or High Severity bug to be used or
because it is a theoretical bug, e.g. when using problems with certain
encryption or signature algorithms.
Exmamples: Weak file system permissions in Docker images (requires already a
certain level of system access), low quality password hashing (requires database
access), weak signature checks for code dependencies (requires MITM).
Permissions: No special permission is required to retrieve the information.
How to report: Using the
public issue tracker
Disclosure: During report or downgrade from High Severity. An issue with
bug description and solution must be created.
Undecided/Unclear Severity
Description: A security problem with unclear impact.
Exmamples: Malformed input that could increase the server load but with
unevaluated level, the slightly guess that over multiple levels a XSS attack
might be possible but without demonstration.
How to handle: Report and handle as High Severity and downgrade if needed.
FAQs
Who attacks public research?
There are many potential attackers. The author does not mention certain
scenarios because this might lead to discrimination or unfounded suspicions
against people, organizations, groups or states.
Disclosure
The author works as a Invenio developer but does not think that he must be
part of High Severity team.
Open Questions

Should the contact to the closed mailing list be encrypted? If so, how?
(e.g. shared PGP key, Schleuder)

Should there be a special invenio-security-announcement mailinglist to
prepare administrators for a critical patch? We have to assume that at the
point we release the patch we also disclose the security bug, so there might
be only a small time window between patch release and first exploit.

Should there be a Medium Severity level? If so, who has the permission to
read it? (e.g. all core developers) Differentiation to High Severity
required.

Is this method to complicated? If so, how can we simplify it while archiving
a suitable security standard.

Should this document be located at GIT top-level or as a usual part of the
documentation? If using the latter approach, we should add a pointer from
the README.rst or as as SECURITY file.

Related to #1799 and recent discussion on documentation of community processes.
Django has an excellent security policy that can be used as inspiration:
https://docs.djangoproject.com/en/1.7/internals/security/
I think the most important to document in a security policy is:

How to report security issues.
How we deal with a reported security issue (i.e. what is our workflow).

Currently we have unwritten processes but it would be good to get them down on paper. Also, I think we can wait with technical implementation details such as if we sign/encrypt messages, until the workflow is fully defined and documented.

The Django policy looks good to me. It (more or less) reflects the proposed version in a good written and "proved to work" form. We might want to use it as a baseline.

Part of documentation update.


Use 948$h to determine billTo/shipTo address

If 948 0/ $happr then use LTS Approvals for addresses, otherwise default to LTS Acquisitions.

Resolves #77

@starsplatter I still need to add a test, but feel free to run locally if you're so inclined...

looks good


Pixel ratio defaults to device pixel ratio

This seems sensible and results in one less option to pass to createVisualizer().

Ah yea, that makes sense to have as a default, thanks!


refactor so that resources are passed around strings

this prevents issues with atom length becoming limiting.  Function names can be converted to truncated names at the callsite.

completed in c9119e4

completed in c9119e4


BlotStrawberry-Vanessa

Write a short description about your art piece, such as what your artwork represents and your experience drawing it!
I was thinking about inspiration for some blot art and I came across a booster juice. It would be cool to randomly generate a strawberry. My artwork randomly generates the width, leaves, and seeds of a strawberry.

[x] I have read the steps to getting a blot
[x] I am submitting art that...

[x] is algorithmically generated (will meaningfully change each time the program is run)
[x] is your own work that is not copied from somewhere else
[x] is drawable through the editor(does not use outside tools)
[x] doesn't call Math.random() (See the documentation on randomness)
[x] is drawable on Blot itself (doesn't have lines overlap more than 5 times)

[x] Doesn't overlap lines more than 5 times
[x] Fits in the working area of 125x125mm
[x] Doesn't rely on colour to look good

If you used based your art on something else, used a tutorial, or remixed it from something else, please link it here:
Lastly, link a picture of your art piece here:

Hey there again! Currently this still falls under the bar, and I would love to see this idea be expanded! How about random fruit generated inside a blender... or a bowl of fruit? Super great start and improvement :)

Closing this PR due to inactivity! Please create a new PR when you have done more.


qq() array interpolation edge cases

Perl seems to have rather complex rules about what punctuation arrays do vs. do not interpolate. Some do not interpolate:
eval: qq/ @( @) /
' @( @) '

Others do:
eval: "WAT" =~ m/^(.*)$/; qq/ @+ /
' 3 3 '

We should work out a proper list of what does vs. doesn't, and ensure we handle them all appropriately

Some progress:
eval: no warnings; my $str; eval($str = "qq(\@$_)") =~ m/\@\Q$_/ ? print "$str is literal\n" : print "$str INTERPOLATES\n" for map { chr $_ } 32 .. 126
qq(@ ) is literal
qq(@!) is literal
qq(@") is literal
qq(@#) is literal
qq(@$) INTERPOLATES
qq(@%) is literal
qq(@&) is literal
qq(@') INTERPOLATES
qq(@() INTERPOLATES
qq(@)) INTERPOLATES
qq(@*) is literal
qq(@+) INTERPOLATES
qq(@,) is literal
qq(@-) INTERPOLATES
<EMAIL_ADDRESS>is literal
qq(@/) is literal
qq(@0) INTERPOLATES
...
qq(@9) INTERPOLATES
qq(@:) INTERPOLATES
qq(@;) is literal
qq(@<) is literal
qq(@=) is literal
qq(@>) is literal
qq(@?) is literal
qq(@@) is literal
qq(@A) INTERPOLATES
...
qq(@Z) INTERPOLATES
qq(@[) is literal
qq(@\) INTERPOLATES
qq(@]) is literal
qq(@^) is literal
qq(@_) INTERPOLATES
qq(@`) is literal
qq(@a) INTERPOLATES
...
qq(@z) INTERPOLATES
qq(@{) INTERPOLATES
qq(@|) is literal
qq(@}) is literal
qq(@~) is literal

Oops - a bug in my program because of the parens incorrectly identified these
qq(@() INTERPOLATES
qq(@)) INTERPOLATES

They should say "is literal"


[test] Fix ClangImporter test on IBM Z

The calling convention on IBM Z requires that arguments are sign or
zero extended to regiser width, so optionally allow that.

@swift-ci Please test.

Build failed
Swift Test OS X Platform
Git Sha - 028b058bf9367e2a8a2b6f788ed96732bafc98b8

@swift-ci Please test OS X platform


feat: show a notification when a new version of the app is available

Demo

How does it work
When building the app for production, a service worker is automatically installed and executed every time the app is loaded by the browser. If a new version of the application is available, the assets (js, css, images) are downloaded in background while the user is working, and a persistent toast is eventually displayed to inform the user of the fact, providing a link to click to update the application.
If the user decides to dismiss the toast or reloads the page without clicking the link in the toast, the old version of the app will be loaded instead, and the toast is displayed again. This will continue until the user clicks the link in the toast.
Caveat
For this to work on the new staging environment, if you have already visited it in the past you'll have to close the tab and open it again to ensure that the latest service worker is installed. From that moment forward, you'll be getting the toast for new deploys.

PR Storybook available here


Some updates do not appear in the feed

For example, https://www.bungie.net/en/Explore/Detail/News/50396
(ty to Stardust for noticing some were missing)
Possible solutions:

get Bungie to reclassify the post, somehow 🙃
remove the updates category filter and scan every page instead for posts with "update" or "hotfix" in the title 🤮🤮🤮

besides how much longer this will take to load, and how spammy towards the API it probably is, it's also less reliable since there's plenty of posts with "update" that I don't want to sweep up

supply an additional JSON of misclassified posts and insert them into the feed 😮💨

I think this is the saner option, as (I'm assuming) the older posts won't change any further, and newer posts would be noticed if they were misclassified, so either they'll get fixed or me or someone else will notice.

Considering how often posts get misclassified, I am probably better off scrapping the whole feed for specific posts.


python310Packages.scooby: 0.7.0 -> 0.7.1

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build python310Packages.sfepy

Result of nixpkgs-review pr 212822 run on x86_64-linux 1

2 packages failed to build:

python310Packages.pyvista
python310Packages.sfepy

2 packages built:

python310Packages.scooby
python311Packages.scooby

mpi4py is broken.

mpi4py is broken.

And it's an x86_64-linux-specific issue...

No new failure. mpi4py was already broken for a while now.


Minecraft 1.21 support

are there any plans to update the mod at all or is it abandoned?

I did the 1.20 port and have start on a 1.21 port. I'm just very busy at the moment

@theendercore Did you also support 1.20.5? That is where all the major changes lie, which will definitely impact chime.
(Also see the ongoing discussion for Optifine/CIT Resewn on how to handle these changes, e.g. https://github.com/sp614x/optifine/issues/7658#issuecomment-2241169816)


Erlang docs not building

I moved from asdf to vfox-erlang to build erlang in my project. In asdf, I was able to build the erlang docs with the KERL_BUILD_DOCS=yes environment variable, however I haven't been able to do so with vfox, with or without the environment variable. The readme in this repo says the docs should build by default, but that hasn't been my experience. Any idea what I might be doing wrong, or if there's a bug here?

I moved from asdf to vfox-erlang to build erlang in my project. In asdf, I was able to build the erlang docs with the KERL_BUILD_DOCS=yes environment variable, however I haven't been able to do so with vfox, with or without the environment variable. The readme in this repo says the docs should build by default, but that hasn't been my experience. Any idea what I might be doing wrong, or if there's a bug here?

I released a version v1.0.1 to fix this problem. You can update vfox-erlang plugin, then reinstall Erlang/OTP and try again.
eg:
# 1、update plugin
vfox update erlang
# 2、remove the old version
vfox uninstall erlang@xxx
# 3、reinstall it
vfox install erlang@xxx

use erl to test your installation has the EEP48, for example:

@ccavolt

BTW. It is different from asdf-erlang internal implementation that uses kerl to manage versions. vfox-erlang, make is directly used for installation in Unix-like systems. You can use most environment variables mentioned in official documents to control the installation process.
for an example, speed up your installation:
export MAKEFLAGS=-j8
vfox install erlang@xxx

reference: https://github.com/erlang/otp/blob/master/HOWTO/INSTALL.md#building-3

Thanks for that tip! I've been lamenting the speed of the builds and that definitely helps!
Unfortunately, regarding the docs, that hasn't fixed the issue. I'm using a devcontainer to build erlang, so I don't have to really do much to make sure I have a clean environment. You can see how I'm building it here.

I looked at the logs for GitHub Actions, and it seems that the version of the plugin used is incorrect.

@ccavolt

Can you offer a sample devcontainer.json for me.  I want to test it.

Thanks for that tip! I've been lamenting the speed of the builds and that definitely helps!
Unfortunately, regarding the docs, that hasn't fixed the issue. I'm using a devcontainer to build erlang, so I don't have to really do much to ensure I have a clean environment. You can see how I'm building it here.

{
"name": "erlang-docs-test",
"image": "mcr.microsoft.com/devcontainers/base:ubuntu-22.04",
"features": {
"ghcr.io/ccavolt/devcontainer-features/vfox:0.4.0": {
"version": "0.5.1",
"user": "vscode",
"shell": "zsh"
},
"ghcr.io/ccavolt/devcontainer-features/vfox-erlang:0.4.1": {
"version": "26.2.5"
},
"ghcr.io/ccavolt/devcontainer-features/vfox-elixir:0.4.0": {
"version": "1.16.2",
"locale": "en_US.UTF-8",
"defaultMixCommands": "yes"
}
},
"customizations": {
"vscode": {
"extensions": [
"JakeBecker.elixir-ls",
"phoenixframework.phoenix"
]
}
}
}

I cut out a lot of things that aren't relevant to the example; let me know if you have any issues.

（QAQ~😣）Can not reproduce in my machine.
❯ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

I'm in the process of creating a reproduction...in the meantime, I updated my devcontainer feature to build the docs itself, with the following lines:
export VFOX_CACHE=/opt/vfox
cd "${VFOX_CACHE}/erlang/v-${VERSION}/erlang-${VERSION}"
make docs DOC_TARGETS=chunks

Which works in my elixir project that uses that feature. I'm able to run the erl h(lists). command and don't get any complaints from ElixirLS, so I'm not sure what's going on at the moment.

I think I messed up somewhere in here. I can't build a reproduction that doesn't build the docs now, so I'm just going to close this unless I find something more concrete later. Thanks so much for the fix and sorry for the wild goose chase afterwards! 😅


wandb ValueError

Trying to reproduce the plots for cifar10_mlp_weight_matching.py using Weights & Biases with compiling script: python src/cifar10_mlp_weight_matching.py --model-a mlp_0 --model-b mlp_1 --load-epoch 10. However, resulting in a wandb ValueError that the project doesn't contain artifact. Shown below:
wandb: ERROR Project <entity>/<project> does not contain artifact: "cifar10-mlp-weights:mlp_0"

Fixed!


[Utility][Document] Design QoS data structures

Objective
Design and implement quality of service (QoS) protobufs for Servicers in the utility module to unblock Fisherman interface design. Ensure that the protobufs capture relevant information about Servicers, focusing on the registration process and QoS metrics.
Origin Document
V1 Utility Specification - Servicer Protocol

Goals

Design QoS protobufs to capture relevant information about Servicers, such as PublicKey, StakeAmount, ServiceURL, RelayChains, GeoZone, and optional OperatorPublicKey
Ensure that the protobufs facilitate proper measurement of Network SLA (Service Level Agreement) metrics, including Availability, Latency, and Data Accuracy

Deliverable

[ ] Design and implement QoS protobufs for Staked Servicers
[ ] Ensure that the protobufs support measurement of Network SLA metrics (Availability, Latency, and Data Accuracy) for Servicers

Non-goals / Non-deliverables

Designing protobufs for other actors besides Servicers
Implementing other servicer protocol functionality

General issue deliverables

[ ] Update the appropriate CHANGELOG
[ ] Update any relevant READMEs (local and/or global)
[ ] Update any relevant global documentation & references
[ ] If applicable, update the source code tree explanation
[ ] If applicable, add or update a state, sequence or flowchart diagram using mermaid

Testing Methodology

[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @jessicadaugherty

Report cards out of scope?

Going to close this out in exchange for the process being put together in #733.


Support the ability to embed/reference custom graph views in notes and publishing graph views on the web

Please select if your request is either something new or an enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup - Dendron's Lookup Command
[x] Views - Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[x] Publish - External Site Publish
[ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe
At the moment, the user can view the graph but not use graph instances within notes. It is also not possible publish graph views on the web.
Describe the solution you'd like

Let the user reference/embed graph views (such as the local graph, filtered views, complete vault graphs, etc.) into notes in a similar way they can already embed other notes notes and text blocks defined by headers or anchors.

Support controls for what portion of the graph is embedded and how it appears on the screen (analogous to text embedding or image embedding). The user will need to be able to save filtering or query results in application to graph views.

Such capabilities would be useful, for example, in domain/parent notes or when explaining the relationships between notes to the others. Such views can serve as visual tables of contents or navigation aids. For a discussion, see Discord

Make these views publishable on the web.

Describe alternatives you've considered
It is possible to capture states of the graph as images and embed those. However, these views are not dynamic, can easily go out of dte and mislead.
Additional context
Alternative note-taking software supports this functionality (sometimes simplistically). it is an opportunity for Denrdon to show leadership.
For example, the Obsidian graph view can be published.

For some useful discussion and comparison of note-taking graphs, see this note.

I realise that there are related issues and an RFC regarding graphs...
https://github.com/dendronhq/dendron/issues/1916
RFC
https://github.com/dendronhq/dendron/discussions/615

Thank you for the suggestion. this would be a useful feature for sure. The graph view is indeed a rich design space like you mentioned. We plan on working on various graph view enhancements in the near future and we'll keep track of you suggestions here when we plan it 🙏🏼

I would love to see this as well.


Adding wrap_as_model to Block

Goals :soccer:
We recently introduced high-level functions to create models to make it easier to create models. This PR tries to introduce new functionality to each block to be converted to a model. This because otherwise we would need a high-level model-function for each block we create (like for instance #205 does for MLPBlock).
Implementation Details :construction:
This PR adds wrap_as_model to a block, which allows you to wrap a block in-between a InputBlock and prediction-tasks. This can be used for instance to convert a MLPBlock to a model by doing:
model = ml.MLPBlock([512, 256]).wrap_as_model(schema)

Another potential solution would be to add from_block to the Model class, to API would then look as follows:
model = ml.Model.from_block(ml.MLPBlock([512, 256]), schema)

Testing Details :mag:
Added a simple test to ensure wrap_as_model works as expected.

@marcromeyn  Both API solutions seems reasonable and useful for me!
Could not we have both (block.to_model() and model.from_block()) ?

@marcromeyn Both API solutions seems reasonable and useful for me! Could not we have both (block.to_model() and model.from_block()) ?

@marcromeyn I liked Gabriel's suggestion. I think to_model() sound better than wrap_as_model().

I think to_model makes sense. We do need to add some extra checks there though, since some blocks (like DLRMBlock) already contains the input-block. So then we shouldn’t add it again, and if the user provides it we need to throw an error.


feat: initial working state

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


No internet connection mode not working

Hello everyone i have follow the exact steps and works fine when my app is connected to the WiFi but the below error is triggered when i use my app with no internet connection
Failed to load resource: net::ERR_NAME_NOT_RESOLVED    https://undefined.us-east-1.amazonaws.com/
Isn't there automatically suppose to local storage the events and when is online to send it or should i make it? Cause in android and ios native language AWS automatically take care of this issues.
Thanx in advance!

Can you post some sample code on how you're instantiating the AMA.Manager. The URL you're trying to hit looks wrong.

How have you brought in the aws sdk? Is it local or remote ()?

Thanks for all the help guys. I have fixed the issue! it was a problem with the way i handle the data


RangeDailyBase warns for parameter not set

When I use Rangedailybase I always get a warning for parameter not set.
C:\Program Files (x86)\Python36-32\lib\site-packages\luigi\parameter.py:261: UserWarning: Parameter "param_name" with value "None" is not of type string.
  warnings.warn('Parameter "{}" with value "{}" is not of type string.'.format(param_name, param_value)

Looked at https://github.com/spotify/luigi/issues/1810 and tried adding email to conf
https://github.com/spotify/luigi/issues/1810#issuecomment-258284082
but it did not help...
Everything else is working fine!
I'm running luigi on windows.

The warning is not so much that param_name is not set, as much as it is a Parameter with a default of None. Parameters are being treated as if they're StringParameters and thus should have a default of ''. Since then, a new parameter type has been introduced which accepts None as a valid default value, OptionalParameter.
Regardless, this is merely a warning and shouldn't negatively impact the execution of your pipelines.
Feel free to submit a PR to default param_name to an empty string or to an OptionalParameter.

The description of param_name in https://github.com/spotify/luigi/blob/7d3bf2e06981391007d7ac923ae638ade96d8dcc/luigi/tools/range.py#L109
says that
param_name = luigi.Parameter(
        default=None,
        description="parameter name used to pass in parameterized value. Defaults to None, meaning use first positional parameter",
        positional=False)

I don't get the point of this parameter -- seems like some kind of blockage of using positional parameters or what? Would it lose its function dfaulting to empty string or optionalParameter?

Defaults to None, meaning use first positional parameter

That param_name was added in 2015, by @joeshaw
Looks to me like param_name can be updated to an OptionalParameter without the need to change any other code.


[TRI-1394] Improve the Linear integration documentation

Overview:
Update the Linear integration documentation so it is much easier to use as a reference.
We have just overhauled our GitHub documentation and would like all of the rest of our integrations to follow the same structure.
Please use the references and resources at the bottom of this post to complete this issue.
Pages to add:
Linear overview & authentication:
This page is currently this.

Page Title: Linear overview & authentication
Sidebar title: Overview & authentication
Page content: authentication with Linear, in the same format as this: https://trigger.dev/docs/integrations/apis/github

Linear Triggers & events:

Page title: Linear triggers & events
Sidebar title: Triggers & events
Page content: all the triggers and events available from our Linear integration, in the same format as this: https://trigger.dev/docs/integrations/apis/github-triggers

Linear Tasks:

Page title: Linear tasks
Sidebar title: Tasks
Page content: all the tasks available from our Linear integration, in the same format as this: https://trigger.dev/docs/integrations/apis/github-tasks. Also include one example at the bottom with clear comments. See references below for sample code.

References & resources:

Our current Linear documentation in the GitHub repo.
Example job code to use - job catalog and jobs showcase.
We use Mintlify for our docs, documentation here

TRI-1394

Hey @Rutam21 - we’re not assigning issues, we’ll accept the best PR for an issue (not necessarily the first PR either). Triaging assignments during hacktoberfest doesn’t scale.

@nujovich thank you, this is getting there. For Triggers & events and Tasks they need to be formatted in the same way that GitHub is: https://trigger.dev/docs/integrations/apis/github-triggers and https://trigger.dev/docs/integrations/apis/github-tasks
Every trigger, event and task needs to have a code example as well a link to the official Linear API documentation. You can check the GItHub integration docs pages for the correct format.

Great ! I will work on the changes through the day

@nujovich how's it going?

@nujovich how's it going?

I found it hard to complete the task documentation as there's no official link to examples :(. But I manged it. Today I will finish events & triggers :)

Awesome, thanks. I'm also going to raise the points to 500 for this one because it is a much larger change than some of the other docs changes. Thanks @nujovich, looking forward to seeing the PR come through!

Hey @nujovich, sorry about the delay for this.

If you can't find the official API documentation for a Trigger or a Task then you don't need to provide a link,  because lots of them are currently linking to the wrong place. I didn't realise how little documentation Linear had so it's ok in this case.
Could you add an example to the bottom of the Tasks page please. This should show how to use the underlying client like the GitHub integration example

Thank you!

hey @nujovich, it's the last evening for Hacktoberfest - how are you getting on?

hey @nujovich, it's the last evening for Hacktoberfest - how are you getting on?

Hi @D-K-P ! I missed the deadline. A lot going on at work. I would like to end this contribution and keep contributing, as we are having an opensource jam here in Alicante, Spain in the upcoming weeks


Errno 2] No such file or directory: '/usr/local/searxng/searx/engines/gentoo.py'

Describe the bug
Error in nginx container, Perplexica is full container installation.
To Reproduce
Going to Discover option in Perplexica, then it shows not found.
Expected behavior
Opening discover
Screenshots

Discover feature is under development and SearXNG's errors won't cause any issues


Fix soundness bug in mul instruction of RISC-V machine

Fixes: #713
Fixes a soundness bug in the mul instruction in the RISC-V machine, when instantiated on the Goldilocks field. Instead of naively decomposing the result into bytes, we now use the SplitGL machine. This machine is now part of the default processors if the field is Goldilocks.

Does this depend on the witgen PR or does witgen work here?

Does this depend on the witgen PR or does witgen work here?

It does not depend on anything!
I just merged main, please re-approve and then I'll squash.


Treat "500 Internal Server Error" and "502 Bad Gateway" the same as a 503

We still get spurious errors from our deploy jobs, and almost every time I dig into one, it ends with something like failed HEAD: 500 Internal Server Error.
This updates our auto-retry logic to treat 500 (and 502) the same as 503 (ie, up to three retries, subject to our per-request+overall rate limits).

We should maybe also include 502, although we see that a lot less frequently. :thinking:

(we also sometimes get read: connection reset by peer / unexpected EOF, but those are much harder to recover from / auto-retry)

We should maybe also include 502, although we see that a lot less frequently. 🤔

Updated.

Well, that's a new failure.  We didn't get that when the automated CI job ran three days ago. :thinking:
Error: No files were found with the provided path: .test/.coverage/coverage.*
.test/.coverage/GOCOVERDIR/. No artifacts will be uploaded.

Oh fun: https://github.com/actions/upload-artifact/releases/tag/v4.4.0
That doesn't explain why it was fine three days ago (when that release is four days ago), but that would explain it!

Oh fun: https://github.com/actions/upload-artifact/releases/tag/v4.4.0
That doesn't explain why it was fine three days ago (when that release is four days ago), but that would explain it!

Fixed (via https://github.com/docker-library/meta-scripts/commit/f5b18c803010716859916e88cba38834f2b68a7f on main)


missing Address 42001 value 0x0008

This happens because the read request comes for the address starting with 4x2002. The address numbering in the program OpenModSim starts with 1, not 0.
At the same time, in the protocol logs, addressing starts from 0, as provided in the Modbus protocol standard.

From version 1.6.0 OpenModsim support address base switch. Now you can select which address base use 0 or 1.


Need to add Button setImage and setImageFile

Began to do this, but the behavior wasn't quite as expected. Following is the code that I began writing:

    public Button setImageFile(String path){
        if(this.ctrl != null){
            try{
                ((BBjButton) ctrl).setImageFile(path);
            } catch(BBjException e){
                Environment.logError(e);
            }
        }
        return this;
    }

Implemented in v24.11


Cannot connect from some devices, connection pending

I am having problem connecting to aria2, In my laptop the connection keeps pending and eventually timeout,
But I can connect from my mobile browser

This is how it looks like in my computer, I can connect with same credentials from my mobile :/
Aria2 server is behind nginx+cloudflare

Are you sure the config in your computer equals your mobile device? I think you can try to export the config from your mobile device and import to your computer.


upgrade to netty 4.x

Update code base to consume the proper netty 4.0.x classes. This upgrades blueflood code base to use netty 4.0.40.FINAL, which is the latest 4.0.x netty up to date. There is also netty 4.1.4.FINAL but since datastax driver 3.0.0 is pulling in netty 4.0.x, I figure it's safer to use netty 4.0.x.
The main goal of this upgrade is so that datastax can use the Native epoll transport, which is supposed to perform better.

Coverage increased (+0.2%) to 75.982% when pulling 1077ca509e20812b92c431842060f1ade668b000 on shintasmith:netty into 91d390b6504bfaf538909972e2610f4b930f9451 on rackerlabs:master.

Coverage increased (+0.2%) to 75.982% when pulling fe505853a8f2a88edeeec33aa749fee4fde2fffb on shintasmith:netty into 91d390b6504bfaf538909972e2610f4b930f9451 on rackerlabs:master.

Coverage increased (+0.3%) to 76.059% when pulling ba8209b7e842a0493482b46656fa1897e444a211 on shintasmith:netty into 91d390b6504bfaf538909972e2610f4b930f9451 on rackerlabs:master.

Whats the main reason to switch from HttpRequest to FullHttpRequest?

Coverage increased (+0.3%) to 76.086% when pulling 79c5c4181b991df99a218aad356be4fbc2825203 on shintasmith:netty into 91d390b6504bfaf538909972e2610f4b930f9451 on rackerlabs:master.

@ChandraAddala I moved the max content length in HttpConfig

Looks good.

Coverage increased (+0.2%) to 76.03% when pulling 7bb13af04afc2540e72129ceaa41e62c6be727cd on shintasmith:netty into 91d390b6504bfaf538909972e2610f4b930f9451 on rackerlabs:master.


Add default border-width to hr elements

Resolves  tailwindcss/tailwindcss#979
The resulting horizontaler ruler has a height of 2 pixels.

Close duplicate PR.
Solution in #991


podman plugin does not download dependencies of roles when importing

I have a repo of an ansible role tested with molecule for some years now. Without a real change, my tests started failing on August 2023 when I import my role due to its dependencies on meta/main.yml.
I see on an early step:
Molecule default > dependency
  Starting galaxy role install process
  - staticdev.pyenv (2.10.2) is already installed, skipping.
  INFO     Dependency completed successfully.
  WARNING  Skipping, missing the requirements file.

For some reason I get the error:
  TASK [Include staticdev.python_developer] **************************************
  ERROR! the role 'staticdev.pyenv' was not found in ansible.legacy:/home/runner/work/ansible-role-python-developer/ansible-role-python-developer/staticdev.python_developer/molecule/default/roles:/home/runner/.cache/molecule/staticdev.python_developer/default/roles:/home/runner/work/ansible-role-python-developer/ansible-role-python-developer:/home/runner/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/runner/work/ansible-role-python-developer/ansible-role-python-developer:/home/runner/work/ansible-role-python-developer/ansible-role-python-developer/staticdev.python_developer/molecule/default

  The error appears to be in '/home/runner/work/ansible-role-python-developer/ansible-role-python-developer/staticdev.python_developer/meta/main.yml': line 37, column 5, but may
  be elsewhere in the file depending on the exact syntax problem.

  The offending line appears to be:

  dependencies:
    - name: staticdev.pyenv
      ^ here

The role exists on Ansible Galaxy with correct version. This error only happens on Github Actions, but not locally. I do not really understand why, but on my path locally molecule can find staticdev.pyenv and can import statically. Do I need to add anything extra to install the requirements?
I tried found a change in the docs for syntax of role-file to requirements-file, but both syntaxes give the same failure:
dependency:
  name: galaxy
  options:
    requirements-file: requirements.yml

Do you maybe have an idea @ssbarnea ?

Thanks for your answer @zhan9san! Actually I always had the dependency for my role on meta/main.yml. I noticed on last major release of molecule it stopped installing it for some reason. To continue with my role, I found a solution to not have a dependency at all, but I believe there could be a bug. It can be verified checking our my previous commit to this one https://github.com/staticdev/ansible-role-python-developer/commit/65eb677846851573b736f3f220c8da02adc42d88#diff-92c74e80f0140aa012f39f58b4259dbe74401cdc9a0b84269295f480b9961809

@staticdev
There must be some misunderstand on https://github.com/ansible/molecule/pull/3956/files.
It is said the role-path and collection-path would be removed and they should be configured in ansible.cfg, which has no effect on role-file and requirements-file described in this doc, https://ansible.readthedocs.io/projects/molecule/configuration/#dependency
Here is what I tested.
$ cat molecule/default/molecule.yml
---
dependency:
  name: galaxy
  options:
    requirements-file: requirements.yml

$ cat requirements.yml
roles:
  - name: staticdev.pyenv
    version: 2.10.2


List-of-rules window enhancements

Currently the window containing the list of rules can be closed by clicking anywhere other than the window itself. This can be improved by

Adding a clear close button
Make the rule window (div) movable

[requested by @mcr]

The window is now draggable in 119644aa07d3adc77323c4c5bf5db026375c7f0f


feat(android): Edge-to-edge Modal (navigationBarTranslucent prop)

Summary:
The future of Android is edge-to-edge and to make the React Native developer experience seamless in this regard, the ecosystem needs to transition from “opaque system bars by default” to “edge-to-edge by default.”
Currently, there's no easy way to have edge-to-edge modals, as they are implemented using Dialog instances (a separate Window) and only provide a statusBarTranslucent prop.
I tried to implement it in react-native-edge-to-edge by listening to the topShow UIManager event. But if it works well when there's a defined animation, we can see a quick jump when there's none, because there's too much delay before the event, and edge-to-edge cannot be applied quick enough to the dialog window.
react-native-edge-to-edge implem with animation (no jump)
https://github.com/user-attachments/assets/4933a102-87a5-40e4-98d9-47f8c0817592
react-native-edge-to-edge implem without animation (jump)
https://github.com/user-attachments/assets/e4675589-08fe-44fe-b9d8-0a6b3552b461

For this reason, and because listening to event feels a bit hacky, I think it will be better to go for a new prop directly on RN Modal component: navigationBarTranslucent

[!NOTE]
navigationBarTranslucent cannot be used without statusBarTranslucent, as setting both enable edge-to-edge, like AndroidX would do and it would requires extra (and unecessary, given the direction Android is taking) work to find a way to keep the status bar opaque but the navigation bar transparent that work on Android 6 to 15+

Additional infos

Colors used for the buttons navigation bar in the PR are the default Android ones (light and dark)
Compared to the Google implementation, the light scrim is applied from O_MR1 to Q (and not O to Q) as the android:windowLightNavigationBar style attribute is not available on O (it can only be applied programmatically on API 26).

Changelog:
[ANDROID] [ADDED] - Add navigationBarTranslucent prop to Modal component
Test Plan:
Run the tester app, toggle navigationBarTranslucent:
https://github.com/user-attachments/assets/286d173b-35a5-4951-9105-f9f7562d6764

Any chance this could be added to 0.74 (Expo SDK 51) and 0.76 (Expo SDK 52)?


Add Twistlock k8s operator

@jpadams If this operator works with both vanilla kubernetes and OKD/OpenShift, please add a copy of the manifests in the community-operators directory in addition to the upstream-community-operators directory.
This can be added in a follow-up PR if you wish

@jpadams It seems that the operator is passing the scorecard test, but fails CI in that it cannot cleanup resources after running. I'm not concerned with this, should be good to go
/lgtm

@SamiSousa Thanks. I added operator to community-operators as well in this same PR as our operator works on both upstream k8s and OpenShift. Does that work for you or do I need to break it out to a separate PR?

@jpadams That is perfect, thank you!

@SamiSousa What's next in the process to accept the PR? Just want to make sure I stay on top of this until you've got everything you need :)

@jpadams No more work is required on your end, this will be merged soon


Add a default keyboard shortcut to take a screenshot in a running project

The default key binding for ui_take_screenshot is F12, but it can be changed in the project settings' input map (make sure to enable Show Built-in Actions). See https://github.com/godotengine/godot-proposals/issues/6789 for detailed rationale.

This closes https://github.com/godotengine/godot-proposals/issues/6789.

Testing project: test_take_screenshot.zip
Preview
Screenshot of a project with a transparent background while paused, without any tearing despite having V-Sync disabled:

Possible solution would be to set the InputEvent as handled after taking the screenshot.

Done :slightly_smiling_face:

I'm conflicted about this for very selfish reasons, as I use F12 for my drop-down terminal yakuake on Linux. I've been using that terminal for years and F12 is its default keybinding. This change would conflict and since it's part of the project input map, it would be impossible for me to disable it in all the tests projects or games I use.

oh, another Yakuake user here, yeah F12 would conflict :(((

I'm conflicted about this for very selfish reasons, as I use F12 for my drop-down terminal yakuake on Linux. I've been using that terminal for years and F12 is its default keybinding. This change would conflict and since it's part of the project input map, it would be impossible for me to disable it in all the tests projects or games I use.

This would also conflict with the Steam screenshot key, so maybe it's better to use something like Shift + F12 instead. What do you think?

Shift + F12 sounds better to me.
That being said, the more I think about it the more I'm worried about the engine providing a builtin shortcut in all games which may conflict with user systems and favorite tools.
The current builtin input actions are those strictly necessary for expected UI interactions, and are unlikely to conflict with user hotkeys (as they're the same used by other GUI toolkits so they're not suitable for global hotkeys in the first place).
This PR would add something that departs from this and adds an always on hotkey. While the game developer can remove it on a per-project basis, most won't (that's the point of it) and thus most Godot games will support this hotkey, possibly clashing with the player's preference.
So I'm not sure whether we should actually implement this, even if I support the use case.
More opinions would be welcome :)


Voice Break and lag in voice chat

Hello ,
I have downloaded the Voice Pro - WebGL, Mobile, Desktop from the unity asset store. Now I am facing some issues

voice chat delay--- comes after 2-3 sec minimum
voice break ---not clear when multiple players join the same room(5 players I have used)
Sometimes unable to listen in Voice chat .....voice delay was intolerable.
please help me to fix my issues.....ASAP

hello.
2 known issues I know and completely related to Unity is: AudioClip.SetData
doesnt work in WebGL properly which cause issues with sound lag when played
chunk ended and begins to play new chunk which is workaround for webgl
currently. second thing is that for some reason when js code is running
under unity canvas it cause delays in receiving data from microphone from
browser(its interesting that if device has better CPU or app running with
high fps then delay is small). first thing related to Voice Pro asset and
second thing is to Microphone Pro asset.
we still investigating how we could improve both assets based on experience
from completely new product we announced for webgl
"not clear when multiple players join the same room(5 players I have used)"
-> you have to manage by own code to which room players joins by providing
same room name and be sure to be at the same region.
Best Regards
On Tue, Aug 16, 2022 at 8:18 AM karishmaibentos @.***>
wrote:

Hello ,
I have downloaded the Voice Pro - WebGL, Mobile, Desktop from the unity
asset store. Now I am facing some issues

voice chat delay--- comes after 2-3 sec minimum
voice break ---not clear when multiple players join the same room(5
players I have used)
Sometimes unable to listen in Voice chat .....voice delay was
intolerable.
please help me to fix my issues.....ASAP

—
Reply to this email directly, view it on GitHub
https://github.com/frostweep/PUN2VoiceWebGLUnity/issues/8, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACR76KHCPRJEF5XPIPFAW43VZMQBNANCNFSM56UMY7KQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

this issue isnt related to that plugin since its not Voice Pro

No its Voice pro which i have downloaded from asset store https://assetstore.unity.com/packages/tools/input-management/voice-pro-webgl-mobile-desktop-169274

this repository completely another solution and not connected to Voice Pro anyhow.


Unnecessary Bing Maps warning

A Bing Maps key warning is generated when we construct the viewer widget with the following code.  Perhaps this needs to be done a different way?
var viewer = new Cesium.Viewer('cesiumContainer', {
    selectedImageryProviderViewModel : new Cesium.ImageryProviderViewModel(
    {
        name : 'Open\u00adStreet\u00adMap',
        iconUrl : Cesium.buildModuleUrl('Widgets/Images/ImageryProviders/openStreetMap.png'),
        tooltip : 'OpenStreetMap (OSM) is a collaborative project to create a free editable map \
of the world.\nhttp://www.openstreetmap.org',
        creationFunction : function() {
            return new Cesium.OpenStreetMapImageryProvider({
                url : 'http://tile.openstreetmap.org/'
            });
        }
    })
});

Given our recent Bing map keys woes, we should probably create a much more "in-your-face" message for when the API key is set to the default, perhaps by overlaying an HTML element or ViewportQuad in the top center of the screen?

Yes, we might also even ask that they get a key before downloading Cesium like Leaflet (or default to something low-res that we host).
Let's hold for now until we think more deeply.

Now that we are rotated keys, should we just close this?

We already have an issue for that in #1262


Switching data-tiling to late materialization path (being compatible with multi-device)

Overview
This is the epic issue for tracking data-tiling evolution that is compatible with the multi-device project.
Goal

Propagate device buffer allocation requirements to host compiler.
Build a data-tiling path for GPU backends that provides decent performance by default.
Be able to do data-tiling when there are multiple devices.
Deprecate MaterializeHomogeneousEncodings pass, which switches to the late materialization path.

Tasks
Buffer Allocation Problem
https://github.com/iree-org/iree/issues/17924 has the prototype that propagates the buffer allocation requirement from codegen backends to the host compiler. The prototype uses attribute and interface to do the propagation, and it requires several components changes in IREE. To make it work with multi-devices, it requires the encoding specialization at stream level. See https://github.com/iree-org/iree/issues/17924 for more details.
Short Summary
We want to strip all target configurations, defining "layouts" representation in IR, and attach such information in encoding attributes. On the host/stream side, the EncodingLayoutAttrInterface attached to target executables implements the calculateStorageSizeInBytes method, which takes a tensor type (optionally with encodings) and returns the total storage sizes in bytes.
On the dispatch sides, the encodings attached to bindings describes the original layout. The layouts are defined by how we describe it in materialization, which has innerDimsPos, innerTileSizes, outerDimsPerm and optional swizzle. We serialize them into a dictionary attribute and attach to bindings. Thus, the encoding will have two types. One is describing the input layout. The other is the encoding for execution target. Today, they must match. There are no difference in current setup. However, we could potentionlly have update_encoding operations. In that case, we'll need to transfer the layout using this information. Below is the example that what the layout looks like in the IR.
We do not scope the update_encoding/transfer_encoding in the work, but it demonstrates that it can be supported when we have needs.
iree_encoding<... layouts = {innerDimsPos = [0, 1], innerTileSizes = [16, 1], outerDimsPerm = [0, 1]}>
iree_encoding<... layouts = {innerDimsPos = [0, 1], innerTileSizes = [-9223372036854775808, -9223372036854775808], outerDimsPerm = [0, 1]}>
iree_encoding<... layouts = {innerDimsPos = [1, 0], innerTileSizes = [16, 1], outerDimsPerm = [1, 0]}>
iree_encoding<... layouts = {innerDimsPos = [1, 0], innerTileSizes = [-9223372036854775808, -9223372036854775808], outerDimsPerm = [1, 0]}>
iree_encoding<... layouts = {innerDimsPos = [0, 1], innerTileSizes = [16, 16], outerDimsPerm = [0, 1]}>

Tasks on Codegen Sides:

[x] Introduce Codegen::LayoutAttrInterface attribute interface, which provides methods for encoding materialization in backends.
[x] Implement EncodingNopLayoutAttr to handle the discarding encodings path.
[x] Implement CPULayoutAttrInterface to handle the CPU logic.
[x] Implement VMVXLayoutAttrInterface to handle VMVX logic.
[x] Implement GPULayoutAttrInterface to handle AMDGPU logic where we're currently developing.
[ ] Remove tech debts introduced in the transition period.
[ ] After above tasks are done, we can implement a unified MaterializeEncoding pass.

Tasks on Host Sides:

[x] Introduce IREEEncoding::EncodingLayoutAttrInterface. This mainly provides interface methods for host to compute the storage buffer sizes.
[ ] Implement the interface methods for CPULayoutAttrInterface.
[ ] Implement the interface methods for VMVXLayoutAttrInterface.
[ ] Implement the interface methods for GPULayoutAttrInterface.
[ ] Implement the encoding specialization pass (which is a completed version of the prototype pass) at the Stream level. Here we scope to homogeneous computing with multi-device. I.e., a device can only have a single executable target.
[ ] Enhance the EncodingSpecialization pass to handle heterogenous computing.

With the above work, the codegen can propagate needed information to host, because host can cast the attribute to the attribute interface and get the total storage size. It also provides a path to run data-tiling on multi-device even they do not implement data-tiling. This partially unblock the deprecation of MaterializeHomogeneousEncodings pass. The remaining issue will be described in next sections.
GPU Data-Tiling Development
Currently, we are able to run data-tiling matmul on early materialization path; we have e2e tests for it. However, we are not able to run it on late materialization path. Because the set/unset encoding codegen is not supported yet.
There are two late materialization paths. One is already supported on CPU path; the other is the next evolution of data-tiling. I.e., we want to form matmul + unset_encoding + further elementwise consumer into a single dispatch. I call it data-tiling fusion path.
In this section, we firstly focus on the late materialization path. The multi_mma codegen is done for CDNA/RDNA arch, and @bjacob is currently looking at ukernel work (TBD: Provide a link). However, the set_encoding and unset_encoding codegen is not supported at this moment, even if the dispatch only have a single encoding op. @Max191 has a prototype branch that can codegen unset_encoding ops with hand-tuned configurations. Some parts (e.g., setting configs) still have some difficulties needed to be sorted out. The codegen for set_encoding ops should be similar. Note that fusion is not involved yet. They are shared effort between late materialization path and data-tiling fusion path.
The next step is looking at the fusion cases. On the late materialization path, we fuse set_encoding ops with their producers and unset_encoding ops with their consumers. They should be reasonably extended by the previous single encoding op codegen work. The only issue that I can think of is the unset_encoding + reduction case. It is not a valid case in data-tiling fusion path because we only fuse unset_encodings and further elementwise operations into matmul dispatches, but not reduction ops. We could add a flag to disable the unset_encoding + reduction fusion if it becomes tricky. The point is not to sticking to this case since it is in a transition period. We eventually need to enable the data-tiling fusion, based on priorities.
Note that the data-tiling fusion path is not supported on CPU path. We could expand the CPU work for data-tiling fusion in another section or epic issue.
So the remaining tasks are:

[ ] SetEncoding Codegen
[ ] UnSetEncoding Codegen
[ ] SetEncoding Fusion Codegen
[ ] UnsetEncoding + Elementwise Fusion Codegen
[ ] multi_mma + UnsetEncoding + Elementwise Fusion Codegen

The outcome is that we should be able to run GPU data-tiling at model level on late materialization path when unset_encoding + reduction fusion is disabled. Furthermore, we could start supporting the data-tiling fusion path on GPU. CPU needs to catch up, though.
MaterializeHomogeneousEncodings Pass Deprecation
This work depends on the other two milestones, plus its own issues. Currently, the issue is that we hurt the performance when backends do not implement data-tiling. Because we could form set_encoding ops to their own dispatch, and they are not const-evaluated for some reason (e.g., blocked by reshape ops).  It becomes a redundant copy, and we need to eliminate the case. I have not looked at this part yet, but the idea is that we could do an analaysis at CreateDispatch phase. It is hard to cancel dispatches at stream level, and it is easier to do it early on. Ben suggested me to look it at flow level, and turn them into flow.clone ops when we know that the potential targets do not implement encodings.
The other performance issue that I can think of is about hoisting ops to initializer or const-evaluating operations with encoding types. It should not be hard because we can do something like EncodingSpecialization pass, which duplicates them when needed and attaches the layout. Then we look at the layout ant lower them to a sequence of operations, and there are no longer encodings.
Tasks:

[ ] Turns a dispatch into flow.clone op if we identify that it is a redundant copy.  CAVEAT: I haven't prototyped it yet, so I do not have a concrete solution yet. It could be tricker.
[ ] Implement encoding specialization for const-eval things.

NOTE: This work technically does not depend on GPU data-tiling development. I'm just putting a bar (that is reasonable IMO) for the work.

The "Implement GPULayoutAttrInterface to handle AMDGPU logic where we're currently developing." task is done in https://github.com/iree-org/iree/pull/19392

VMVX device attribute migration is done in: https://github.com/iree-org/iree/commit/e84ea8d2079eb9782275303bc5f93d988908b314
CPU device attribute migration is done in: https://github.com/iree-org/iree/commit/415a0f6a15052dbfa1c29ec4e36876770c9b9240
I'm working on cleaning tech debts.


Add common template files for tools 1es migration

Add common tools 1es-redirect template
Add common 1es image variables

Closing in favor of https://github.com/Azure/azure-sdk-tools/pull/7920


Add "High Quality Thumbnails" For Imgur Only

Reddit itself uses pretty low quality thumbnails that they are generating, might be worth looking into the "Small Square" version of the image from Imgur for use as thumbnails. Only concern is performance. Resizing those and using larger images will result in degraded performance, so should be stress tested.

Closing due to inactivity.


Merge azavea/stac-ml-aoi-extension

Opening this to bring the content from azavea/stac-ml-aoi-extension into the stac-extensions org. I have tried to leave the original content intact and make the minimum number of changes required to fit the content into the stac-extensions/template format and get the build to pass. The intention is to open issues on this repo for any additional work needed on the extension (e.g. adding examples, additional reformatting, etc.).
A couple of notes:

@echeipesh is the owner since he made all commits to the original repo. Let me know if this should change. I'm also happy to be a co-owner or sole owner if either of those options make sense).
Did a little work to fit the content into the template format, but more probably needs to be done. I thought it would be best to do this through issues + atomic ~commits~PRs rather than as part of this merge.
Had to remove the front matter in the ADR docs to make remark happy, let me know if there's a reason that needs to be in there.

@kbgg Thanks for catching those typos, I've fixed them in 37d7387471addbb46f2fb857fc7e1690c27cfbee. I think there's a good chance we'll want to re-structure that main README anyway to be more consistent with some of the other STAC Extensions, but it's good to catch these in the review anyway.


Added number-battery

Q
A

Bug fix?
no

New sample?
yes

Related issues?

What's in this Pull Request?
Added number-battery.

I love the uniqueness of this sample! Very cool!
Thanks @tecchan1107!

I'm new to adding JSON formatting on my SharePoint list. When I copy and paste this code it will not show the battery but will not show neither the percentage symbol nor the fill bar. I have set up the field type as number. Do you know what I could be doing wrong?

Hi, @marceloariel1973
Could you please post the same information in an issue?


Should we have an 'effort' label?

Problem

Currently, some low priority issues might take only 1-2 minutes, and could be worth doing from time to time, but are easy to lose track of due to their low priority.
Description

A label indicating the effort, complexity, or time estimate for an issue might incentivize people to take on low-priority, low-effort issues more regularly.

I think the effort labels would be a valuable addition, although we might need to be deliberate about properly separating good first issues from low effort ones. Surely there can be an overlap but not all good first issues are low effort.

I think difficulty would be a more appropriate term considering it's an open source project where people of all backgrounds, experience and expertise would contribute. This could potentially tackle the issue @dhruvkb stated, as 'effort' is subjective. What is a low effort task for me isn't necessarily a low effort for other people and vice versa

@ramadanomar in that case, isn't difficulty also subjective? What's difficult for someone might by easy for someone else.

I prefer effort because it's subjective, but is a time-based subjectivity, not one based on 'expertise' like difficulty is.
Both are quite subjective however!

I am not against adding it, just not making it mandatory.

I also like the idea of a non-mandatory effort label 🙂 It would definitely be helpful for those moments when I would like a "quick win" PR that I know I could knock out easily! And for those cases as folks have mentioned where an issue might be a "good first issue", but not a particularly "low effort" one (e.g. @rwidom with the iNaturalist work 😄)

It would be interesting to try out the approach of tackling several "low effort" PRs per week. What I'm afraid of is oftentimes I start working on an issue thinking it's a "low effort" one and end up spending too much time on it :) If we add this label, it would be nice to add it somewhere in our team expectations doc to try to tackle these regularly.

Closing this issue in favour of https://github.com/WordPress/openverse/discussions/2816 as a full discussion with poll.


Clean sdk

PR Type
enhancement, configuration changes

Description

Removed DonkeyFarm from various building-related configurations and constants in the SDK.
Updated manifest files to reflect the removal of DonkeyFarm and adjusted various class_hash and original_class_hash values.
Adjusted block_number in manifest files from 19 to 17.

Changes walkthrough 📝
Relevant filesEnhancement

SelectPreviewBuilding.tsxRemove `DonkeyFarm` from building selection menu

client/src/ui/components/construction/SelectPreviewBuilding.tsx

Removed DonkeyFarm from the list of building keys.

+0/-1

config.tsxRemove `DonkeyFarm` from building images configuration

client/src/ui/config.tsx
Removed DonkeyFarm from the BUILDING_IMAGES_PATH configuration.

+0/-1

buildings.tsRemove `DonkeyFarm` from building constants

sdk/packages/eternum/src/constants/buildings.ts

Removed DonkeyFarm from various building-related constants.

+0/-4

resources.tsRemove `DonkeyFarm` from building costs configuration

sdk/packages/eternum/src/constants/resources.ts

Removed DonkeyFarm from the BUILDING_COSTS configuration.

+0/-1

structures.tsRemove `DonkeyFarm` from building type definitions

sdk/packages/eternum/src/constants/structures.ts
Removed DonkeyFarm from the BuildingType enum and related mappings.

+21/-28

buildings.cairoRemove `DonkeyFarm` from building category definitions

contracts/src/models/buildings.cairo
Removed DonkeyFarm from the BuildingCategory enum and related implementations.

+5/-9

Configuration changes

manifest.jsonUpdate manifest hashes and remove `DonkeyFarm`

contracts/manifests/dev/manifest.json
Updated various class_hash and original_class_hash values.  Adjusted block_number from 19 to 17.  Removed DonkeyFarm related entries.

+37/-61

manifest.tomlUpdate manifest hashes and remove `DonkeyFarm`

contracts/manifests/dev/manifest.toml
Updated various class_hash and original_class_hash values.  Adjusted block_number from 19 to 17.  Removed DonkeyFarm related entries.

+37/-37

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

would be careful merging this rn, because it might have some unwanted consequences if we migrate this in the deployed eternum world. where people have been constructing buildings already.
maybe we can close this for for now or put is as a draft, and merge it end of the week when we create new world ?


Upgrade to FLAME GPU 1.5

When FLAME GPU 1.5 is released, we should update this example and the associated documentation / instructions.
We should use tags to maintain easy to access tutorials for each version of FLAME GPU.

This is required to build the tutorial with GCC >= 6 / CUDA >= 9 on linux.
Ideally we should also switch to host initialisation of agents, to remove the need for XML generation.
I would also suggest moving to RST / MD for the instructions, so they do not have to be hosted on gdrive.


Documentation nav is broken

Expected Behavior
Navigation it documentation is broken
...
Current Behavior
Links go to the root, rather than the /sites/docs/ subdirectory.
For example, clicking General > XY Grid goes to:
https://get.foundation/xy-grid
But it should direct here:
https://get.foundation/sites/docs/xy-grid

Discussion going on related to this... https://github.com/foundation/foundation-sites/discussions/12565
I will pick this issue to be the "official" issue to track.

All fixed....
OMG! So it's all fixed now. But let me tell you the story of the past 12 hours....
The build has worked and had not changed for like 7 months. However, the links were broken on server hosted by Netlify. Foundation required a pretty old version of node. Netlify suggested that I update node. Well in order to do that, I needed to completely overhaul the dependencies and run a million tests to ensure that we could run on a newer version of node.
So win No. 1 today is that we have now have Foundation 6.8.0. This version now requires node 16 but will also run great under node 18 and 20. This is a pretty awesome win if you ask me.
With all of that published, I was feeling pretty good with myself and published the new build to Netlify. No dice. 😭
After probing and looking around, Pretty URLs was enabled on the site. This completely modifies your URLs to your pages. I turned off that checkmark and it was magically fixed! They must have recently launched this feature and turned it on by default.
It could have been a 30sec fix had I known. But now we have F6.8, so let's call it a good day. 😎

Aww sorry you had to go through all that but I'm super happy to get F6.8 and that I can finally update node! Thanks for your hard work! Now to test the upgrade on our different projects to see how it works...


[tcgc] remove import of UnionEnumVariant

resolve: https://github.com/Azure/typespec-azure/issues/1360

All changed packages have been documented.

:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-client-generator-core - fix ✏

remove import of UnionEnumVariant


Update the swift-format documentation

Update the swift-format documentation to reflect what the script actually does.

The script uses swift run internally with a statically specified version. There seems no need of manual installation
The version installed with the script is currently different of the one documented

@adevress Sorry for the slow response time. I think I'm going to move forward with #1318; shall we discuss how the docs should be changed?

@adevress ping.


Unit1 step 07 adding Callback function

Knowing how to Save/Load the model is great. Could we add a callback function, CallbackList, CheckpointCallback, and EvalCallback? Thanks

Hi (sorry for the big delay), thanks for the feedback. we provide for now a link towards Antonin's RL best practices and there's a step about creating your own Callbacks. We think that for the first unit that would be too much for people that's why we added it as additional resource. 🤗


generate unique type parameters (using name collision detection)

Towards #1157

Current coverage is 95.12%

Merging #1185 into master will not affect coverage as of 0913e86

@@            master   #1185   diff @@
======================================
  Files           78      78
  Stmts         9204    9204
  Branches      1746    1746
  Methods          0       0
======================================
  Hit           8755    8755
  Partial         93      93
  Missed         356     356

Review entire Coverage Diff as of 0913e86

Powered by Codecov. Updated on successful CI builds.


update to modern use of cmake (> 3.3)

Mostly we wanted to support OS releases without updating cmake, but that time is coming where its safe to put those in the past. Modern cmake usage supports some features that vastly simplify its use:

targets can have associated defines, public/private libs and includes
embedded properties like this mean that variables done have to be passed around, targets are merely linked together to bring in includes, defines, private libs
support for exporting and importing project configs and targets
remove ifdefs for older unsupported features/deprecated calls
new syntax for compiler feature support like c++11/14

Probably look at doing this for PothosCore and SoapySDR after 0.6 release. Hopefully the builder macros stay mostly the same, so plugins dont need to change, but users can take advantage of the new target properties when it makes sense to do so.

Informative: https://www.youtube.com/watch?v=bsXLMQ6WgIk

Will be part of: https://github.com/pothosware/PothosCore/tree/modernize

Im def tagging this repo before I merge this one

Certainly. This is definitely meant for 0.7 master.

I may backport my commit to override the C++ standard, but default behavior wouldn't change.


Added the ability to download the birthday wish

This PR is for #30
Here is how the birthday wish will look like when it's downloaded -

@gouravkhunger thanks for showing interest in this PR, I will try and fix this bug ASAP.

@gouravkhunger I have made some changes let me know if the bug is fixed.

Hey! Thanks for the fix.
Can you also add code to hide the button if history[0] == "/" as in the CopyLinkButton:
https://github.com/gouravkhunger/nextjs-birthday-wish/blob/7d9895b05e5df176659e6d4fefd26617899e5431/pages/[...name].js#L82
Also, move it above the create a wish button and keep it below the copy link button. Here's the hierarchy to follow on the wish page:

Copy link button (hidden when user doesn't come from the home page)
Download Image button (also hidden when user doesn't come from the home page)
Create a wish button


Public API ScalarUDFImpl.return_type returns internal error in some cases

Describe the bug
I am trying to upgrade the version of DataFusion that Comet uses. Comet currently relies on ScalarUDFImpl.return_type to get the return type of a scalar UDF. This now returns an internal error when called for DatePartFunc.
    fn return_type(&self, _arg_types: &[DataType]) -> Result<DataType> {
        internal_err!("return_type_from_exprs shoud be called instead")
    }

Should we deprecate this function if it is no longer the correct approach for determining UDF return types? It looks like return_type_from_exprs should now be used instead?
To Reproduce
No response
Expected behavior
No response
Additional context
No response

Should we deprecate this function if it is no longer the correct approach for determining UDF return types? It looks like return_type_from_exprs should now be used instead?

Short term yes
Long term -- the UDF weaved into the plan should know it's return type. It's wasteful to recalculate it over again. https://github.com/apache/datafusion/issues/12604


Log Start GC including <unknown> let customers confused,hopefully tuning it.

Enhancement
Orginal question:https://asktug.com/t/topic/873121
this is really Ugly about <unknown>.

We have solved this in version 6.x.

maybe this issue can be closed?

thanks for you reply really.
yeah,please close it.


Particular facebook video has corruption when downloading yet plays fine on the website

Checklist

[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
[09/11/21 18:11:29] [debug] System config: []
[09/11/21 18:11:29] [debug] User config: []
[09/11/21 18:11:29] [debug] Custom config: []
[09/11/21 18:11:29] [debug] Command-line args: ['--newline', '-o', 'C:\\Users\\killa\\%(title)s.%(ext)s', '--ignore-config', '--hls-prefer-native', '-v', '-f', 'bestvideo+251/bestvideo+bestaudio/best', 'https://fb.watch/7YCEsOmbTA/']
[09/11/21 18:11:29] [debug] Encodings: locale cp1252, fs mbcs, out cp1252, pref cp1252
[09/11/21 18:11:29] [debug] youtube-dl version 2021.06.06
[09/11/21 18:11:29] [debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[09/11/21 18:11:29] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[09/11/21 18:11:29] [debug] Proxy map: {}
[09/11/21 18:11:29] WARNING: Requested formats are incompatible for merge and will be merged into mkv.

Description
https://fb.watch/7YCEsOmbTA/
No matter how many times i've tried to download this video it always corrupts at 00:23 for 2 seconds and then fixes itself, this corruption does not appear when playing the video in the facebook player.

i didn't notice any corruption at 00:23
did you use the copy link in the lower right hand box below the video??
the one with the 3 dots (...)
try again with youtube-dl -f mp4 https://fb.watch/7YKpvoCGT5/

It seems that there are 2 problems:

Facebook
Source webm is corrupted. Directly played the webm (which is selected by youtube-dl) in web browser exhibits the same corruption.
youtube-dl
1080p mp4 is played in web browser but youtube-dl doesn't list this mp4.
https://video.fkix2-2.fna.fbcdn.net/v/t39.25447-2/10000000_149322427258411_7720288228458260554_n.mp4?_nc_cat=101&ccb=1-5&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX3E5MF9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ohc=92pOfJguD9YAX_6g0dI&_nc_ht=video.fkix2-2.fna&oh=b402a351feb9536b58b6141c7dad32aa&oe=61411A07

Ah thankyou so much! It's a shame that yt-dl doesn't list the mp4 as it is better quality than the webm.

I wrote:

youtube-dl
1080p mp4 is played in web browser but youtube-dl doesn't list this mp4. This mp4 is fine.

This seems to be because Facebook returns different format (webm or mp4) depending on the user-agent. (youtube-dl's default is Chrome.)
I've got the format list below several times when I passed Firefox (also needed cookies but not logged in) or Safari as user-agent to youtube-dl. Not enough times for convincing, though, because Facebook soon returns error or redirects to the login page.
[info] Available formats for<PHONE_NUMBER>44542:
format code               extension  resolution note
512725536700305a          m4a        audio only [eng] DASH audio   65k , m4a_dash container, mp4a.40.5 (48000Hz)
270241001113385v          mp4        426x240    [eng] DASH video   95k , mp4_dash container, avc1.4D401E, 24fps, video only
358688099192156v          mp4        640x360    [eng] DASH video  196k , mp4_dash container, avc1.4D401E, 24fps, video only
340943251086905v          mp4        854x480    [eng] DASH video  381k , mp4_dash container, avc1.4D401F, 24fps, video only
217019390429406v          mp4        1280x720   [eng] DASH video  863k , mp4_dash container, avc1.4D401F, 24fps, video only
897139560872375v          mp4        1600x900   [eng] DASH video 2006k , mp4_dash container, avc1.640028, 24fps, video only
2267825803352544v         mp4        1920x1080  [eng] DASH video 5166k , mp4_dash container, avc1.640028, 24fps, video only
727023981425184v          mp4        1920x1080  [eng] DASH video 8081k , mp4_dash container, avc1.640028, 24fps, video only
dash_sd_src               mp4        unknown
dash_sd_src_no_ratelimit  mp4        unknown
dash_hd_src               mp4        unknown
dash_hd_src_no_ratelimit  mp4        unknown    (best)


fix: fixes types generation with nuxt v3.7

fix issues https://github.com/huntersofbook/naive-ui-nuxt/issues/10

Thank you :heart:


Revert "(maint) Bump to ezbake 1.8.7"

This reverts commit e40393c4c6a0ad69f7f0dc7bd7dd592caacef9a8.

Test PASSed


Add BodyTagHelper  to mvc/views/tag-helpers/built-in/

https://github.com/jbagga/TagHelperComponentSample
@fiyazbinhasan  if you can write the sample code, I'll write the article and list you as author.

@Rick-Anderson the repository already contains well enough sample code. Could you please let me know what kind of samples do you need?

@fiyazbinhasan sorry I meant Document the new ITagHelperComponent in ASP.NET Core 2.0 #4033
Can you links to the repository samples you found?

@Rick-Anderson I was talking about the repo link you provided. It has an example for the built-in head tag helper component i.e. GlobalScriptTagHelperComponent. And a custom footer tag helper component, MyTagHelper.

@fiyazbinhasan  see this comment
Need a sample that shows how to include JavaScript/CSS in a Razor Page (code should be the same for MVC view).

@Rick-Anderson Please check this sample. https://github.com/fiyazbinhasan/TagHelperCompoenentSample

The primary goal of TagHelperComponents was two fold:

Enable TagHelper library authors to add TagHelpers that run on a specific set of tags without requiring a user to @addTagHelper their bits. In the default case a library author can add a BodyTagHelper that injects scripts, css, basically any pre-requisites for the library to function properly.
Enable dynamic TagHelper on specific tags by adding/removing from the component list (this is covered in the article).

Should add info about 1

@NTaylorMullen @Rick-Anderson reorganized the article a little bit. Can you take a look, please? Thanks.
https://github.com/fiyazbinhasan/TagHelperCompoenentSample

@NTaylorMullen quick review please so we can get this documented.

cc @scottaddie

@jbagga @NTaylorMullen please review this sample for use in Tag Helper component article.

The sections and flow seems good. 👍

@fiyazbinhasan Can you please submit a PR with your work? That allows us to review the doc and apply the necessary edits. Thank you very much for your great work so far.

@fiyazbinhasan Let me know if you need any help on the PR or want me to get it started.

I can make a PR by the end of this week if that's ok. @Rick-Anderson would be great if you can get it started.

@fiyazbinhasan  I'll get it started.

@Rick-Anderson @scottaddie please check out the PR https://github.com/aspnet/Docs/pull/7935

@fiyazbinhasan  merged.


Loc Automation - Updating ETA of loc job: 204

Loc Automation Updating ETA of loc job: 204

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/APEXTest/AirLocTesting, working directory: W:\rv30-s, target branch: master, target branch commit: d3970107d8c693bcc0d0f41617d7ba9c249824cd, source branch: 204, source branch commit: .

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.


keyword file belongs to a different version of the library

I've updated the porcupine's android library to v1.5 and now my ppn file seems to be invalid. How can I make it work again with this version?

if you have generated using the open source optimizer generate again using the latest version. Otherwise, send an email to Picovoice to get the latest version.

Actually we asked you to generate it. It was a service provided to Hipcam Ltd. to generate the ppn for 'Hello Hipcam'


fix: input error

Pull Request Test Coverage Report for Build 1337

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

Totals

Change from base Build 1320:
0.0%

Covered Lines:
665

Relevant Lines:
882

💛  - Coveralls


Feature/morganchen12/failable initializers

Better supporting the unhappy path of failure to produce a nil model object instead of a non-nil model object with all of its fields set to nil. This also allows for non-optional model fields.

Thinking alike here! This recent PR changed to using init(json:): https://github.com/hkellaway/Gloss/pull/30
It doesn't introduce a failable initializer, so that's definitely something to consider. Do you want to update your PR to just reflect the failable initializer?

 Not perfect yet though, still got some issues.

Should be good now.

I see you're advocating for a failable initializer over a force unwrap operator. I see virtue in both - can you let me know when you think failable initializer is the way to go?

When serializing concrete model objects from arbitrary data, it's usually a given that not all data will result in a valid model object. In this case, it makes sense to return nil from the initializer as an indicator of failure, rather than returning a non-nil model object with all of its fields set to nil. In the case where some fields are essential and must not be nil (i.e. a User model fetched from a remote database somewhere might not make sense without its unique id), a failable initializer allows us to express this requirement as a non-optional field without the use of force-unwrapping, which as you know is crashy and frowned upon.
The init? definition in the protocol doesn't forbid adopters of that protocol from defining a non-failable initializer, it just indicates that some serialization may fail.

i have been thinking about this all day; i'm liking the failable initializer for safety. this will come in the release after the latest i've prepared - will ask for a rebase then
thanks! :sparkles:

Hm, looks like the code examples in the README may need to be updated as well.

in progress

Replacing this PR with rebased version: https://github.com/hkellaway/Gloss/pull/38


chore: bdd-sbhg-import-1583241399 to 0.0.1

chore: Promote bdd-sbhg-import-1583241399 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Publish 7.5-milestone-1

Publish 7.5-milestone-1

@bot-gradle test and merge

Your PR is queued. See the queue page for details.


[Bug - next-pwa]:

Provide environment information
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>was ok)
Link to reproduction - Issues with a link to complete (but minimal) reproduction code help us address them faster

To reproduce
Run next build.
Describe the bug
Cannot find module '@swc/core'
Expected behavior
Build without error.
Screenshots (if relevant)

Additional information (if relevant)
No response

Oops. I will work on a fix soon!

Thanks for your great work @DuCanhGH!
9.0.1 is the last working version (9.1.0 is also broken).

Works nicely. Thank you.

@rollingmoai can you open a new issue with a reproduction? Thanks!

@rollingmoai I just released next-pwa 9.1.4, please let me know if it is working :)


Collapse with several collapse contents on one page

Hi,
I want to build a page with some listed documents and provide some meta information if clicked on them. My idea was to implement that via the collapse feature in the following way with NgFor:
`

    tbd

    tbd

 `

However, the problem is now that if I click on one panel-heading all collapse divs are opened and for closing vice versa. Is there a way to specify the collapse just for one single panel-heading?
Thanks!

Looks like you need to use tabs?

No tabs was wrong... however Accordion was the one I searched for... Didn't think of that. Cheers mate!

Cheers :)

How you are implementing accordion for this above example ? Can you please tell me. I am having same situation .

I have same problem.
This works for me
For example:
If you have some ngFor="let object of objects"
you can add some boolean property ("collapsed") on object model, and implement collapse like
<button type="button"
(click)="object.collapsed = !object.collapsed">

But i have a little problem with this. After clicking on different collapse buttons, after some time, page reloads. I dont know if it is problem with this implementation or what.


Make builds work with manage_closure_dependencies

Creating builds with manage_closure_dependencies: true can result in smaller build sizes.  While this doesn't seem like it should be the case, there is unused code that is unconditionally included in the builds (see #3447 for example).  Using manage_closure_dependencies improves the situation by limiting the files that are included for compilation.  However, because our olx.js file relies on types defined throughout the library, the olx.js file cannot safely be passed to the compiler when manage_closure_dependencies is set to true.
This can be demonstrated by creating a build config that only exports a single source (e.g. ol.source.Raster).  This generates compiler errors like the following:
externs/olx.js:2409: ERROR - Bad type annotation. Unknown type ol.interaction.DragBoxEndConditionType
 *     boxEndCondition: (ol.interaction.DragBoxEndConditionType|undefined)}}
                         ^

externs/olx.js:2446: ERROR - Bad type annotation. Unknown type ol.interaction.DragBoxEndConditionType
 * @type {ol.interaction.DragBoxEndConditionType|undefined}
          ^

2 error(s), 0 warning(s)

One alternative could be to distribute the externs files around the src directory (e.g. src/ol/interaction/dragboxinteraction.externs.js) and have a build tool concatenate what is needed for a custom build - but this is piling more custom logic and complexity into the build tool.
It would be nice if there were an annotation we could used to describe our externs, rather than needing to include them in separate files.  A custom annotation and build step to generate externs is another option (similar to the one above).
Anybody else have any ideas?

I don't have any alternative that would not include custom build steps. Maybe @fredj knows something?

I thought that moving the typedefs into 1 file would fix this problem, but it doesn't. It fixes the issues for typedefs, such as ol.interaction.DragBoxEndConditionType mentioned, but the compile still fails with Unknown type ol.layer.VectorTileRenderType, which is an enum not a typedef. These could be moved into one file as well, but that still wouldn't fix the problem, as there are still constructor types referred to in olx, and these have to remain in their own module/file.
I encountered the opposite problem when I first started creating custom builds. I thought it would be really clever to only include those olx externs that I actually needed, but this too fails, as the code refers to other olx types that I don't use. I suppose the basic issue is that the compiler has to know about all the type definitions, whether they're needed for a particular build or not.