Question: is this possible to use environment variable with a filling template ?

Hey !
Thanks you for you awesome configuration library, it is pleasant to work with.
I wonder if when filling a template it is possible to say for instance password = env("PG_PASSWORD") ?
Let me explain why : if you want to use this config in production you mght want to use env variables for sensible informations.

https://pkl-lang.org/main/current/language-reference/index.html#resources


Feature: Upgrade container images within YAML files

Description
The arkade chart verify feature has been really useful in preventing errors with the openfaas chart and others that we maintain in the community, along with faasd's docker-compose YAML file.
A new command named arkade chart upgrade should do as per chart verify, but instead of checking if an image exists, it should use the remote registry's API to enumerate tags, parsing them with a Go version library i.e. semver and then generating a new file to STDOUT with the upgraded contents.
Imagine we had:
gateway:
  image: ghcr.io/openfaas/0.25.4

Then ran:
crane ls ghcr.io/openfaas/gateway

0.23.0
88eea5f62e1d6a1812265793eacee6213b74af80
0.23.1
b87b96ae456ef74992af2e1f9f664feec690ab57
0.23.2
dc2a7a0c6e8510058415f9430b6d4142b93c3a19
0.24.0
4604271076a96ae70b4488afdc516f62fd802dd7
0.25.0
8e711b3a0c72d05db7081f72ee6b966b486726c3
0.25.1
887c804254ffc4c1df5db77b462e21b785887335
0.25.2
bc2eeff4678407583faec982c1c7d1da915dd60c
0.25.3
c07bebbbc9c2de4ad3750184cccc23f4ecad16f1
f9245ebbb308cf6c8b86436bd25643322198e9dc
0.25.5

So in this instance, the output or change would be as follows:
gateway:
  image: ghcr.io/openfaas/0.25.5

Getting tags can be done through the standard registry v2 API:
TOKEN=$(curl -s "https://ghcr.io/token?scope=repository%3Aopenfaas%2Fprinter%3Apull&service=ghcr.io"|jq '.token'|tr -d "\"")

curl -H "Authorization: Bearer $TOKEN" https://ghcr.io/v2/openfaas/printer/tags/list

{"name":"openfaas/printer","tags":["latest","94b6fa05ac62efa1b8c143d36f73b48a38bec16c"]}

The initial call, without authentication returns a realm header explaining where to go to get the TOKEN
curl -i https://ghcr.io/v2/openfaas/printer/tags/list
HTTP/2 401
content-type: application/json
www-authenticate: Bearer realm="https://ghcr.io/token",service="ghcr.io",scope="repository:openfaas/printer:pull"

Caveats & limitations

No private image or registry support
GHCR support only, Docker Hub if it's not too much trouble
No support for SHAs, only sem-ver
Should be efficient, so if possible, there is no need to paginate all tags available for a repo like openfaas/gateway which may have  hundreds of results

Hi @alexellis,
can you assign me to this issue?

Was this completed in #832?
(I can't close it as Derek is configured locally)


7.x: usage in typealias

Hi, this morning I tried migrating R.Swift to 7.x
In my projects, I mostly use R.swift with the following typaliases:
typealias L = R.string.localizable
typealias I = R.image
typealias C = R.color
typealias F = R.font

But unfortunately, these are not working anymore, the error is: Cannot find type 'R' in scope.
I suspect this is because R.generated file is no longer part of the sources.
Is there a way around this, maybe by modifying the buildtool? Or will I be forced to find-replace all usages of the type aliases?

In version 7, R is no longer a type, but a value instance of type _R
You should be able to use variables instead:
let L = R.string.localizable
let I = R.image
let C = R.color
let F = R.font

Wow, that was fast, and way easier than expected.
Thanks Tom!


Fixed Usage of Azure Model

This PR makes sure that the selected Model is used in Azure OpenAI environments

Indeed - didn't saw that. The other PRs are more efficient than mine.
I'm closing it.


fix(object_store,gcp): test copy_if_not_exist

Which issue does this PR close?
Closes #3235.
Rationale for this change
The copy_if_not_exist function was not tested, and didn't pass the test when enabled. It needed to return an AlreadyExists error if the destination already existed.
What changes are included in this PR?

copy_if_not_exist returns AlreadyExists error when appropriate
GCP now tests copy_if_not_exists in integration tests
GCS copy commands send a Content-Length header now.

Are there any user-facing changes?

I have run the integration tests for the gcs feature against my own GCS account and they all pass. ✅


Rename gaps() to gaps_trimmed() and add a gaps_untrimmed()

Since the documentation wasn't that clear it may be worth explaining the trimming effect and adding an untrimmed method so that all behavior is obvious and available.

And actually while at it it might be worth doing the same for overlapping() too

actually I'm going to hold off on overlapping_trimmed() for a while since it would also make overlapping_mut more ambiguous

fixed in 6480e22


Fix grid prop defs (docs)

Grid already supports responsive rows / cols (prop defs were inaccurate)

I am not seeing any issues with types when using Grid. What issue does this solve exactly?

Check the docs on the website, neither does or columns is listed as
responsive
On Tue, Aug 15, 2023 at 6:07 AM Vlad Moroz @.***> wrote:

I am not seeing any issues with types when using Grid. What issue does
this solve exactly?
—
Reply to this email directly, view it on GitHub
https://github.com/radix-ui/themes/pull/23#issuecomment-1678908827, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOMNKBPJLITVMDGVD5XLCTXVNYALANCNFSM6AAAAAA3QUATOY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, documentation is separate in https://github.com/radix-ui/website. Thanks for the note, we'll update it

@vladmoroz I believe the way the website works is that it picks up the propDefs of the individual component and then renders that in a table.
https://github.com/radix-ui/website/blob/ee246a5e0451744e2f127a006726c70e4727be4b/components/ThemesPropsTable.tsx#L37
So doesn't it need to be changed here first, and then have the updated module installed for the website to be picked up?

It does, but the docs use the value of the prop defs (which already have an explicit responsive: true value for columns and rows props) and not their type signature, which is what this PR adjusts—this would have no effect on the docs anyway.
Since this package itself defines these props correctly, it's something we need to fix in the website code


[ISSUE-48][FEATURE][FOLLOW UP] add unit test for validating rss objects

What changes were proposed in this pull request?
For issue #48
I add some unit test about validating rss objects in webhook components.

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Codecov Report

Merging #248 (3f2990f) into master (7eb069e) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #248      +/-   ##
============================================
- Coverage     59.29%   59.22%   -0.07%
+ Complexity     1346     1344       -2
============================================
  Files           162      162
  Lines          8789     8789
  Branches        828      828
============================================
- Hits           5211     5205       -6
- Misses         3311     3315       +4
- Partials        267      269       +2

Impacted Files
Coverage Δ

...rg/apache/uniffle/storage/common/LocalStorage.java
42.75% <0.00%> (-2.07%)
:arrow_down:

...org/apache/uniffle/server/ShuffleFlushManager.java
76.66% <0.00%> (-1.67%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Bump deployment db dir

https://www.pivotaltracker.com/n/projects/2124891/stories/156796254

I see this followed https://github.com/aeternity/epoch/pull/975


pull request for e2e test at 01/25/2017 21:26:07

:white_check_mark: Validation status: passed
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.


Catalog returns null items

I am working on a specific scenario. So with external help, I have created a custom profile with additional fields. We extracted the additional fields from the XML in the JSON. Creating new metadata works fine but the index page does not work now.
All I get is this

and I do have metadata, as seen below.

If anyone has any idea or pointers what could be causing this, please let me know. I have tried with ElasticSearch, 6.4, 7.5, 7.11, none of them show the metadata. It all started after I extracted the additional two fields from the XML in the JSON. Here's a download link for my catalog. Maybe another pair of eyes can see what I am missing.

are you certain your geoportal looks at this particular index? especially since you mention you have tried multiple versions of elastic. please include the output of: http://localhost:9200/_cat/indices and http://localhost:9200/_cat/aliases

It did work with 7.5 as well as 7.11 before the addition of the two new fields in the JSON. Before I create a new metadata entry, I have 31 entries.

And did you 'add the new fields in JSON' through the geoportal or through this elastic client?


Help: Full path to source file is displayed in docs and I can't change it.

Hi all,
I've been fiddling with this for the last 3 hours and I give up :(
When using the most basic call from MacOsX Terminal to run jsdoc I ALWAYS get the full path of my source file within the generated documentation.
Example:
./jsdoc ../project/js/jsfile.js

In the generated index file I can see a h1 with "index" and below it a h2 with the full path to the js file:
/Users/username/projects/path/projectname/js/jsfile.js

After reading up I thought it would be relative to where I run jsdoc from.
But all this has the same exact result:
cd /Users/username/projects/path/projectname
../jsdocs-master/jsdoc js/jsfile.js

as well as
cd /Users/username/projects/path/projectname/js
../../jsdocs-master/jsdoc jsfile.js

The problem is, that this path is also used with the line number references. And it's really not nice that my internal path is displayed...
The output I would want is projectname/js/jsfile.js or at least just jsfile.js, but I can not for the life of me get this to work.
I hope someone can tell me what I'm doing wrong.
regards,
Jan

hi I am using the latest from git+https://github.com/jsdoc3/jsdoc.git"
As you can see at http://depoio.github.io/node-telegram-bot/Bot.html , it stills display full path.

Same issue encounted on 3.3.2, it stills display full path. And with more than one source js file it will do right.

@shernshiou @dickeylth This may be an issue with the template you're using. If you can reproduce this issue with JSDoc's default template, please file a new bug. Otherwise, file a bug against the template you're using.


Altered Naming Convention for Duplicates

In my experience the current naming convention of "Copy of {AutoName}" is very inconvenient, primarily when sorting the Path/Auto names alphabetically as duplicating an auto will send it to a random place in the stack instead of right next to the Path/Auto being duplicated. I believe the changes I've proposed would address this.

I concur that something that appends a suffix would be preferred over something the prepends a prefix, as it would result in less scrolling when creating new paths or autos by duplicating something that exists and then modifying it.

Just checking in on the status of this as it still has failing tests and needs to be formatted.
You can format by running dart format . in the root of the project directory.

It looks like the tests are failing because the actual naming logic is not working as expected. For example, when duplicating Example Path (1) it expects to see Example Path (2) but doesn't. I'm assuming its creating Example Path (1) (1)


Add docs-verifier

First release of the docs-verifier (the extended action of markdown-links-verifier).

Is this doing anything other than checking links yet?

@gewarren Yup. Basic redirection verification.
https://github.com/MSDocsBuild/build-verifier/blob/d535b55271cc491d5cce733f2447e12ff21db0fa/src/RedirectionVerifier/RedirectionsVerifier.cs
The algorithm is to be enhanced in a future version.

🎉 Error: No redirection is found for 'docs/csharp/misc/cs0003.md'.

This is cool @Youssef1313
I'll open a PR that removes the item in the TOC and adds a redirect. then, once that's merged, we can close and reopen this as a test.

I think the build is stuck. Closing & reopening.

@Youssef1313 - We've created a new repo in the dotnet organization to house GitHub Actions that are specific to docs. We'll be locking down our docs repos to restrict the use of actions that aren't defined in the dotnet organization. Would you mind moving your build-verifier action to this repo? Also, it might be better to name it docs-verifier or link-verifier to differentiate it from the action that checks for build warnings.

Sure. Doing that in https://github.com/dotnet/docs-actions/pull/3.


Add mini app for the SPDE method

Contribution
The purpose of this PR is to provide MFEM with support for Gaussian random field generation. Random field models are necessary for uncertain quantification and risk-averse optimization, both of which are important application areas for key MFEM stakeholders. The specific type of Gaussian random field focused on in this miniapp, Matern random fields, are generated by solving the following stochastic fractional partial differential equation, $$(1-\Delta)^\alpha u = \mathcal{W},$$ where $\mathcal{W}$ denotes white Gaussian noise and $\alpha>0$ is a regularity parameter.
Rather than demonstrate random field generation in an MFEM example, we chose to prepare a miniapp that contains the new random field generation class SPDESolver. The main component of this PR is this new class, which can be interfaced in downstream UQ and OUU applications. The main use case that is highlighted in this miniapp is the sampling of random truss structure geometries using uncertainties that mimic those encountered in additive manufacturing processes.
PR builds on ex33/ex33p and implements subsets of the following two papers:
[1] Khristenko, U., Constantinescu, A., Tallec, P. L., Oden, J. T., &
Wohlmuth, B. (2020). A Statistical Framework for Generating
Microstructures of Two-Phase Random Materials: Application to Fatigue
Analysis. In Multiscale Modeling & Simulation (Vol. 18, Issue 1,
pp. 21–43). Society for Industrial & Applied Mathematics (SIAM).
https://doi.org/10.1137/19m1259286
[2] Khristenko, U., Constantinescu, A., Tallec, P. L., & Wohlmuth, B. (2021).
Statistically equivalent surrogate material models and the impact of
random imperfections on elasto-plastic response (Version 2). arXiv.
https://doi.org/10.48550/ARXIV.2112.06655
--> For more info, consult the miniapps/materials/README.md
Running the miniapp
cd mfem
mkdir build && cd build
cmake -DMFEM_USE_LAPACK=ON -DMFEM_USE_MPI=ON .. && make -j12
cd miniapps/materials
ls # should contain visualize.py and README.md

# particles
mpirun -np 4 generate_random_field -o 1 -r 3 -rp 3 -nu 2 \
       -l1 0.015 -l2 0.015 -l3 0.015 -s 0.01 \
       -t 0.08 -n 5 -pl2 3 -top 0 -rs
# Octet-Truss
mpirun -np 4 generate_random_field -o 1 -r 3 -rp 3 -nu 2 \
       -l1 0.08 -l2 0.08 -l3 0.08 -s 0.01 \
       -t 0.08 -top 1 -rs

Expected result

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3065
@TobiasDuswald
@tzanio
@bslazarov + @mlstowell + @psocratis
10/26/22
6/13/23
⌛due 11/16/22

PR Checklist

[x] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

[ ] Clarify what to do with redundant rational approximation
[ ] Makefile
[ ] Copyright on top
[ ] Format
[ ] Header to Header / Source (optional)

From PR meeting 08/23/22:

Avoid duplication of ex33.hpp file
No preference if the header should be in miniapps/materials or examples.
Keep only header (not hpp and cpp) to simplify include

-> Resolved in d0ed2eb, 733aaa6, 3962108

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@mlstowell, @psocratis and @bslazarov, can you please review when you get a chance?

@psocratis and @bslazarov -- can you please review when you get a chance?

@TobiasDuswald, please update copyright of new files to 2023, e.g. replace
miniapps/spde/CMakeLists.txt:1:# Copyright (c) 2010-2022, Lawrence Livermore National Security, LLC. Produced

with
miniapps/spde/CMakeLists.txt:1:# Copyright (c) 2010-2023, Lawrence Livermore National Security, LLC. Produced

Is there anything still left to do on this PR before merging @TobiasDuswald ?

I've included all the feedback previously discussed with @brendankeith , @psocratis , and @bslazarov . From my side, it's ready to go 👍 If any of the more senior developers want to change something, please let me know. But I consider myself done here. ✌

I've included all the feedback previously discussed with @brendankeith , @psocratis , and @bslazarov . From my side, it's ready to go 👍 If any of the more senior developers want to change something, please let me know. But I consider myself done here. ✌

Great stuff!! @tzanio, can this be merged before the review for the OUU project next month?

Nice!
Can you please update CHANGELOG?

Also, can you double check all items here:

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

Merged in next for testing...

Error from tonight's autotest (build-test-basic script):
spde_solver.cpp(15): catastrophic error: cannot open source file "examples/ex33.hpp"
  #include "examples/ex33.hpp"
                              ^
compilation aborted for spde_solver.cpp (code 4)
make[1]: *** [spde_solver.o] Error 4
make[1]: *** Waiting for unfinished jobs....
make: *** [miniapps/spde] Error 2
make: *** Waiting for unfinished jobs....
spde_solver.cpp(15): catastrophic error: cannot open source file "examples/ex33.hpp"
  #include "examples/ex33.hpp"
                              ^

The failure is probably seen just in the out-of-source build with GNU make. Probably, it is best to just use a relative path "../../examples/ex33.hpp" instead of relying on the top MFEM source dir being set on the command line with -I.

Thanks for letting me know @tzanio & @v-dobrev. I followed your suggestion and changed to the relative path with https://github.com/mfem/mfem/pull/3065/commits/41ef47f9dc83c194ce54347026aa9b54ea735cd2 . hope that will fix the issue :)

Re-merged in next for testing...

Re-merged in next for testing ...

Can you merge master here and resolve the conflicts?

@psocratis Does this have to be re-merged into next following 180b85e?

@psocratis, waiting on your review

@psocratis, waiting on your review

@tzanio, I haven't formally reviewed this since I was also a contributor to this PR. In any case I think it's ready to go

@tzanio, this should be ready now. I added it to Doxygen. I also took the opportunity to add  the DPG miniapp as well and fixed a wrong path for the BlockSolvers miniapp.

@tzanio, does this need to be re-merged in next?

Re-merged in next for testing...

Re-merged in next for testing...

Re-merged in next for testing...


Feature request: Connect via unix socket rather than UDP

I'm currently running chrony with the cmdport set to 0 so that no UDP cmd socket is open. /run/chrony/chronyd.sock still exists and is what chronyc etc use to connect to chronyd.
Right now, the exporter only supports UDP, but it looks like there's some code in the facebook repo that looks to use the same golang lib to connect over unixgram:  https://github.com/facebook/time/blob/512b3b30ab2387f45954a90a25645535a4ee1e54/cmd/ntpcheck/checker/chrony.go#L38
I had a very quick go at trying to get this to work, but the exporter just seems to hang when trying to fetch stats. I'm not sure if there's something else needed to get unix socket support, or if I've missed something obvious, but this would be a nice-to-have.

I think you're looking for https://github.com/SuperQ/chrony_exporter/pull/35. Waiting on some changes from the author.

Oh - apologies, I completely missed this. Will watch that (y)


Fixed populate of empty associations. This avoids to execute a smembers

This avoids to execute a smembers command in redis

already fixed in PR #67


optimization: use client hints for SSR

https://developers.google.com/web/updates/2015/09/automating-resource-selection-with-client-hints
We can use these new hint headers to get the actual constraints and use those values on the server instead of making an educated guess then doing a re-render on the client. Any user who enables these hints on their page would be able to benefit from the optimization, otherwise the current method still applies.
Would be a good PR!

@contra Came here looking for this. Is this on the radar?

@oyeanuj Yep - after we take care of #162 which will finalize the SSR API we can do this one.

This doesn't seem to have gotten any more browser support since 2020 - no FF or Safari support. For that reason going to backburner this until it gets more adoption.
Also given the spec, this would only work w/ deviceWidth / width queries - which satisfies a lot of use cases but not all.


Seeing duplicate messages in user defined source

Duplicate message -  AAAAAJexQqI=-52-input-0  -  419895504

we occasionally see around 10 per second.

Hey @yhl25 , how do we reproduce this issue?

I think this was fixed in - https://github.com/numaproj/numaflow/pull/1613

Have we observed this again? Or are we good for 1.3 on this to close

@kohlisid No we haven't. It should be good to close. cc: @yhl25

@yhl25 why was this reopened?

We do not see this anymore except when there is ack failures due to topic rebalancing.


Recola training data

hey,
Two questions about the training data, hope you can help. Thanks in advance.

the Recola dataset that I downloaded doesn't include the same amount data that you have. Did you try to include additional data that collected by yourself?

In your code, you have:
train = [25, 15, 16 ,17 ,18 ,21 ,23 ,37 ,39 ,41 ,46 ,50 ,51 ,55 ,56, 60], # 25
valid = [14, 19, 24, 26, 28, 30, 34 ,40, 42, 43, 44, 45, 52, 64, 65],
test  = [54, 53, 13, 20, 22, 32, 38, 47, 48, 49, 57, 58, 59, 62, 63] # 54, 53
What I got are:
Train = [ 16,21,23,25,37,39,41,46,56]
Valid = [19,26,28,30,34,42,45,64,65]
Test=[13,20,32,38,47,49,53,59,63]
Did I miss anything here?

Annotated data - are you using the annotation from the Recola database? Or the annotation has been post-processed by you?
In your code, you have:
def get_samples(subject_id):
arousal_label_path = root_dir / 'Ratings_affective_behaviour_CCC_centred/arousal/{}.csv'.format(subject_id)
valence_label_path = root_dir / 'Ratings_affective_behaviour_CCC_centred/valence/{}.csv'.format(subject_id)
arousal = np.loadtxt(str(arousal_label_path), delimiter=',')[:, 1][1:]  #this only reads the annotation from the 1st external annotator.

but what I got is something like /recola/AVEC_2016/ratings_individual/arousal/dev_1.csv, the format in the csv file is something as below:
time | FM1 | FM2 | FM3 | FF1 | FF2 | FF3
0 | 0 | 0 | 0 | 0 | 0 | 0
arousal = np.loadtxt(str(arousal_label_path), delimiter=',')[:, 1][1:]  #this only reads the annotation from the 1st external annotator.

Hi, you got the database by email to<EMAIL_ADDRESS>I applied the database and filled all the information needed. But why I got any response from the email ?
Thank for your kindly response if you have any idea.

I too haven't received any confirmation from the Recola Database team. How much time do they take to process a request ?

You may use the AVEC18-GES dataset to try these networks.

You may use the AVEC18-GES dataset to try these networks.

How can I get that?
I cannot fill the request since the lab I'm in doesn't have an webpage for introduction.

Can we use IEMOCAP dataset??

You may use the AVEC18-GES dataset to try these networks.

what about using IEMOCAP dataset??
any suggestion..

I too haven't received any confirmation from the Recola Database team. How much time do they take to process a request ?

hey, bro, did you get the reply from the recola dataset team later? How much time did it take


Update the link to the YouTube video in your README.md file

I'm trying to get started.
This link to the video is not working.
Did you perhaps change it?

Download the template as .zip file
Extract the ASP.NET Core folder
Run TemplateRenamer.exe in the project directory and provide the name of your project
Start the solution file with Visual Studio 2019

Thanks!


Feat(secrets): modify with optional secretversion

Adjusted the getsecret method with optional parameter of secret version, if not supply will get the latest secret version enable, else get the specific version

Inspire from old but gold POC azure keyvault
Thanks @bentaylorwork kudos

Thanks @curlybytes and sorry that it took me so long.
Yes it took some inspiration from bentaylorwork/azurekeyvault :)

@odinuv Thanks for the updates and unit test, I'm not really good at TDD at all XD
I can now use directly the library instead of relying on my Fork


"Dirty flag" in Scene is not set correctly when modifying MixedRealityToolkit configuration profiles

Describe the bug
When opening an example scene from MRTK v2.0.0 in Unity 2018.3.14f1 and changing the configuration of the MixedRealityToolkit, the scene is not marked as dirty from the custom Inspector UI (https://docs.unity3d.com/ScriptReference/EditorUtility.SetDirty.html).
Without further changes in the scene, Unity does not realize the changes in the scene, and therefore does not ask the user to save the changes. If the user reloads the scene, the changes have to be done again.
To reproduce
Steps to reproduce the behavior:

Open an MRTK v2 Eye Tracking Demo scene in Unity 2018.3 (Reproducible with Assets/MixedRealityToolkit.Examples/Demos/EyeTracking/Scenes/mrtk_eyes_05_Visualizer.unity)
Configure a Mixed Reality Toolkit Configuration Profile
Select a configuration profile
See the fact that Unity does not set a "*" flag indicating that changes have been made.
Switching to a different scene will not prompt the user to save changes.
Only workaround is changing something else in the scene unrelated to the profile to set the dirty flag.

Expected behavior
The dirty flag should be set correctly to indicate a change has been made after configuring the profile.
Your Setup

Unity Version 2018.3.11f1
MRTK Version v2.0

Target Platform

HoloLens 2

Testing in stabilization branch now. Modifying the active profile for a MRTK monobehavior does mark the scene as dirty.
Changing properties in the profile will not mark the scene dirty. This is expected because any changes will update the associated profile scriptable object which is not a per-scene change.


staking: move AbandonOrphanedCoinstakes to BlockDisconnect

The AbandonOrphanedCoinstakes function has less impact when run in BlockDisconnect, instead of during staking or walletload.

Let's go with this solution.


Minor release: v1.1

@LachlanStuart do we want everything that's in master to be added to the release?

@intsco Yes

@LachlanStuart please check that all the new features you worked on.

@intsco Looks good to me


Request - Item Stack

Not sure if it would be too hacky or if it has potential to mess with memory usage, but is it possible to add an option to place a stack of an item on the stand? For example, multiple arrows which show up as just one of its type, but the tooltip displays the total count and allows placing and retrieving all at once. Thank you regardless, great mod and it's adding some really amazing opportunities for design/decoration around our base.

Yes, that would be possible. It would require everyone to have the mod because people without the mod would take whole stack while only getting one item.


Unable to push image to custom registry (retrying issue)

I have same issue as @vikas027 at #22188, but as there is recomendation to put it into new issue, I'm writing here.
That's interesting that the problem appears only for big images (>100Mb), and small images works fine.
Environment
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

I setup Docker Registry by following these steps - https://docs.docker.com/registry/deploying/
Next applied TLS and Native basic auth.
Steps to reproduce

docker login docker-registry → enter login/password → Login Succeeded
Pull existing image from Docker Hub:

docker pull nginx
Using default tag: latest
latest: Pulling from library/nginx

Digest: sha256:dedbce721065b2bcfae35d2b0690857bb6c3b4b7dd48bfe7fc7b53693731beff
Status: Downloaded newer image for nginx:latest

Create new tag to push to custom registry:

docker tag nginx docker-registry/nginx-test

After that I see this tag in result of docker images command.
Docker is strating to push the image:
docker push docker-registry/nginx-test
The push refers to a repository [docker-registry/nginx-test]
bc1394447d64: Layer already exists
6591c6f92a7b: Layer already exists
f96222d75c55: Pushing [============>                                      ] 31.63 MB/123 MB

But at the end of process I see error:
error parsing HTTP 400 response body: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01//EN\"\"http://www.w3.org/TR/html4/strict.dtd\">\r\n<TITLE>Bad Request</TITLE>\r\n<META HTTP-EQUIV=\"Content-Type\" Content=\"text/html; charset=us-ascii\">\r\n
Bad Request - Invalid Verb
\r\n

HTTP Error 400. The request verb is invalid.
\r\n\r\n"

If I try to repeat same steps with another images, for example mongo, I see another message:
docker push docker-registry/mongo-test
The push refers to a repository [docker-registry/mongo-test]
f1e35a8075b1: Layer already exists
a474b557cf91: Layer already exists
c70a3fc3236e: Pushing [===============================>                   ]   133 MB/214.4 MB
af170437ae05: Layer already exists
a03828149464: Layer already exists
70c36fdd993b: Layer already exists
eafeecfceabd: Layer already exists
38e11f990b2e: Layer already exists
f96222d75c55: Retrying in 2 seconds

Logs
Docker daemon logs
Oct 29 09:11:26 docker-host systemd[1]: Started Docker Application Container Engine.
Oct 29 09:11:26 docker-host dockerd[1024]: time="2016-10-29T09:11:26.900627200+05:00" level=info msg="API listen on [::]:2376"

So nothing new after dockerd starts.
 The registry never does that. So clearly there is something between your docker engine and your registry (eg: an http proxy), and that something does not support one of the methods (probably PATCH).
Can you elaborate on exactly how you set this up? Using nginx? or HA?

@dmp42 There is IIS ARR + CloudFront in between. You think this is cause of issue?
What about "Retrying in X seconds"?

Docker does retry when it encounters certain failures, but in this case, it's not going to help.
Your proxy (IIS and/or CloudFlare) simply does not allow certain http verbs, and it must. (message is pretty clear: The request verb is invalid)
It's easy to confirm: just try the same operation directly against your registry server, bypassing your proxies.
Bottom-line: you need to reconfigure IIS/CF and (IIRC) allow at least the following: GET, POST, PUT, HEAD, PATCH.
If it still doesn't work, we can look into your daemon logs in debug mode.

@dmp42 I understood the problem. There was http proxy enabled at CloudFlare, which doesn't allow to upload more than 100Mb for free accounts. Therefore it returns HTTP 400 and image pushing fails.
I disabled HTTP proxy and now it works good.
Thank you for your assistance 👍

Happy you got it to work!


[Feature Request] Provide python wheels

It would be great if wheels were provided for the Python package, at least the ones for linux (https://github.com/pypa/manylinux), as compilation of the package takes quite a while.

Yeah, that would be cool.  Someone should submit a PR :)

Why wheels are not compiled for latest version?
https://pypi.org/simple/dlib/#files

Because dlib needs to compile itself relative to what hardware is available on you machine. E.g. CUDA, AVX, SSE, NEON, or some BLAS that is available. Those old binaries used a slow lowest common denominator setting and people complain and get confused about why they run slower.

On Jul 10, 2019, at 1:20 AM, SmartManoj<EMAIL_ADDRESS>wrote:
Why wheels are not compiled for latest version?
https://pypi.org/simple/dlib/#files
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@davisking Are we sure that doing python setup.py install automatically uses the best available on the current computer? (i.e. AVX, SSE, NEON if available, etc.)
Or is there there a risk that python setup.py install will run a low-spec version whereas a faster version would be available?
TL;DR do we have to do things manually, in addition to python setup.py install, to be sure we are using the local machine's features?

You should never have to specify this stuff.  The python cmake build checks for what is available and enables everything by default.  If you don't see the other things being enabled it's because the tests for their existence on your computer are coming back false.  The tests should be robust since they build little test programs with those features and run them.  If the programs can build and run then the features are enabled.  If they don't then they aren't enabled.


add support for most requested priority

What this PR does / why we need it:
It is supported priority in the default scheduler.
Added it to kube-batch for better compatibility, readability and easier transition from the default scheduler.
This PR also refactors existing code in pkg/scheduler/plugins/nodeorder/nodeorder.go.
Release note:
Added support for the "most requested" priority.

/ok-to-test

/lgtm
/approve


Polymer

Begin updating polymer.

@kasperpeulen @devoncarew @lukechurch
We're going to merge Kasper's polymer changes in order to go ahead with polymer integration in embedding. We will fix any existing mobile bugs with polymer as we move along.

Merging.

lgtm to merge :)


Updating HPX to V1.1

Thanks for the PR!
I noticed that we weren't picking up the installed CMake files, so I started using vcpkg_fixup_cmake_targets() and found a few more tweaks that were needed.
I've pushed the modified version to your branch -- it looks good enough to me that I'll merge it in a few days if I don't hear back from you, but if you can give me a thumbs up or down I can merge sooner / fix it :)


Question: Can AsyncSignal.fromFuture revert to the "initial value"

I was expecting ".refresh()" just to call the future again, and ".reload()" to start from scratch (so reset to the initial data and set isCompleted to false), but this is not the case.
Am I just not seeing the function to do this, or is it not possible?

Working on fixing this here:
https://github.com/rodydavis/signals.dart/pull/78

Fixed on 2.0.0, reset will revert to the initial value

The 'reloading' state isn't firing in my code, or your 'flutter_async' example (version 2.0.0)


Make it possible to pick 1-6 weeks as an duration option in the Duration stream field

The current options are set here:
https://github.com/OpenTechFund/opentech.fund/blob/97ec20965197be7915a001882205fcb02183e9fd/opentech/apply/funds/blocks.py#L106-L121

For statistics we want to have a single duration value in common for all submissions.
Would like to avoid messing with current submission data if possible.

Idea: Have two duration fields, one for weeks and one for months (the current one) and then add a duration property to submissions that checks both week and month options and retrieves the right value?

@Parbhat Any ideas how to best accommodate this feature request?

@frjo The idea in the issue description sounds good. We can create two dictionaries one for months DURATION_MONTH_OPTIONS and other for weeks DURATION_WEEK_OPTIONS. And DURATION_OPTIONS will be the combination of these two dictionaries. So, the user can then select a choice based on these two.

@Parbhat It would be ok to display both weeks and month in the same list to the applicant. (But OTF would prefer to have to separate fields or some kind of option on the duration field to pick week or month.)
The keys are now 1-24 that represent month. What should we use for keys for week do you think, if we present them together.
0.25|1 week
0.5|2 weeks
etc.

@frjo If the requirement is to pick one from weeks or months means applicant will be shown only weeks or months and not both. Then we can add an option in duration block which will let admin choose from week and month. Depending on that we will create choices for applicant. So, the week dictionary can also use 1 key which will represent 1 week.

@Parbhat But when retrieving the values we need to know if the key represents weeks or month.

@frjo After we have a new field which will let admin user pick the duration is for weeks/months. Then we can update this method with a conditional. If the duration_type (new field) value in weeks, we will check key in DURATION_WEEKS_OPTIONS dictionary.
https://github.com/OpenTechFund/opentech.fund/blob/97ec20965197be7915a001882205fcb02183e9fd/opentech/apply/funds/blocks.py#L129-L130

OTF says it works well and is approved (Slack).


Update to rand 0.7

The primary change is due to rand's new error handling. With rand 0.7, the rand::Error type now contains either a boxed Error (when std is available) or a NonZeroU32 (in no_std cases). As a result, I've introduced a new PassThroughExhaustedError type. When std is available, the implementation creates a rand::Error by boxing a PassThroughExhaustedError, while in no_std cases, it uses an error code representing the error.
Fixes #168.

I'm not sure why CI failed. The log indicates linker errors of some sort. The errors only occur for the nightly compiler using gcc. Maybe it's a bug in the latest nightly?

CI failed because of borked Rust nightly, it has been fixed starting with yesterday nightly.

Thanks @jturner314 this looks great (but may need a small rebase of the changelog), and I'm eager to see it merged!

Oh, thanks for the heads up. I've rebased the PR off the latest master.

Thanks! Merging this now but I'll leave it unreleased as there may be more breaking changes we'll want to do for 0.10.

@Centril  @ZackPierce Do you have an ETA or a burndown chart for a potential 0.10.0 release I could refer to?

@Centril @ZackPierce Is there an ETA / something like a roadmap or burndown chart I could refer to to try to plan for a 0.10.0 release?

@huitseeker Not as of now. I'm personally quite swamped with language team and compiler engineering work. If you want to go over the list of issues and PRs and create an issue for things to work through in 0.10.0 that would be quite helpful.

@Centril Just an idea: cloud the proptest repo carry a tag for an (unpublished, and probably never-to-be-published) version 0.9.6?
This would, without disturbing your 0.10.0 plans, let us use this trick:
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#working-with-an-unpublished-minor-version
.. to depend on a proptest that imports a rand v > 0.7.
At the moment, projects that define generators have to stick to rand 0.6.5 or take a git dependency.


add const to lookup

Looks reasonable.

Auto-merge toggled on

Silly question: do you think there will be any noticeable increase in compile speed when all of additions of const are included?

I doubt it.


refine: Allow specifying the model config when loading a local model.

problem: PaddleClas loads the config based on model_type  during initialization. However, the value of model_type is always set to custom while loading a local model, which results in the default configuration being loaded every time. PaddleClas 初始化时根据 model_type 来加载 config，而使用本地模型时 model_type 在 _check_input_model 中恒为 "custom"，导致使用本地模型一直使用默认配置而无法使用正确的配置文件。
fix: Allow specifying the model config when loading a local model.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.杨璐 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


scroll

How can I scroll down/up in the list ?

No vertical scrollbar:

Clean cache and try again.


make graphite do fewer recursive chowns when starting

Motivation for this change
The carbonCache service is currently incapable of starting once there are more than 500,000 metrics in the database. This happens because every time before carbonCache starts, a recursive chown is run on the graphite data directory. Since each metric is a distinct file, this chown hits a lot of files. On our production environment, it has recently gotten so slow that systemd times whenever we start carbonCache.
Looking through the service definition, it appears that the recursive chown was only used as convenient way to change ownership of a few directories and files immediately after they are created. This PR makes the ownership changes more explicit. Instead of recursing over the entire data directory, it now targets only the files that were just created. There is still some recursive chowning but none that ends up doing a recursive traversal of whisper (the directory containing all the metrics).
Things done

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

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Updated the db-created logic.

One problem preventing me merging this (in looking for easy things to merge,) is the commit messages don't follow the commit format: https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#submitting-changes

Squashed & fixed the commit message. Thanks!

Thanks for fixing that!


Bug Fix in downloading media files

@huikaihoo Thanks for this. I manually made these changes to my project and it fixed an error I was getting trying to use strapi-upload-google-storage.

I don't know who maintains this repository, but I can confirm that this fix dramatically speeds up build times after the first build. I don't think caching was working at all before. I would recommend merging this in.

HI @huikaihoo, Thank you for contributing ! I'm closing this PR as we just merged a PR that refactor the plugin.


[VK Video] "Unknown error" when downloading playlist's JSON metadata

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2023.01.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[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 issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Ukraine, but not limited to.
Provide a description that is worded well enough to be understood
While trying to download video's playlist, e.g. https://vk.com/video/playlist/-179915138_101 , an error appears.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--skip-download', 'https://vk.com/video/playlist/-179915138_101']
[debug] Encodings: locale cp65001, fs utf-8, pref cp65001, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.01.06 [6becd25] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg n5.1.2-9-g807afa59cc-20221210 (setts), ffprobe n5.1.2-9-g807afa59cc-20221210
[debug] Optional libraries: Cryptodome-3.16.0, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1760 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.01.06, Current version: 2023.01.06
yt-dlp is up to date (2023.01.06)
[vk:uservideos] Extracting URL: https://vk.com/video/playlist/-179915138_101
[vk:uservideos] -179915138_101: Downloading webpage
[download] Downloading playlist: Становление богом
[vk:uservideos] -179915138: Downloading JSON metadata
ERROR: Unknown error
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1502, in wrapper
  File "yt_dlp\utils.py", line 3053, in <lambda>
  File "yt_dlp\utils.py", line 2823, in __getitem__
  File "yt_dlp\extractor\vk.py", line 563, in _entries
  File "yt_dlp\extractor\vk.py", line 82, in _download_payload
yt_dlp.utils.ExtractorError: Unknown error

[vk:uservideos] Playlist Становление богом: Downloading 1 items of 0
[download] Finished downloading playlist: Становление богом

Unknown error is what the site returns. Possibly the load_videos_silent payload API used in #2248 is no longer working.

This looks like it will be fixed by #6122


Only last added button is working on latest nova version (v2.4.0)

When I add more than one button, only the last added button will work. Clicking on other buttons have no effect. There is no error in console nor an xhr request will be fired.

Can you provide some code to examine

Sure.
           Button::make('Approve', 'inquiry-approve')
                ->style('primary-outline')
                ->confirm('Are you sure?')
                ->visible($this->status == 'pending'),

            Button::make('Decline', 'inquiry-decline')
                ->style('danger-outline')
                ->confirm('Are you sure?')
                ->visible($this->status == 'pending'),

"Approve" button is not working, "Decline" is. If I remove "Decline", "Approve" works.

More details: if I remove the "confirm", both buttons are working.
Seems like if two buttons with confirmation are on same page, only last is opening the modal.

Confirming that this issue exists on Laravel Nova v2.5.
Only the last button of the last row can be clicked when using confirm().

Confirming that this issue exists on Nova 2.6.1
Button::make('Quick Pay')->confirm('Are you sure?', view('partials.quickpay')->render())
the confirm dialog does not show, except for the last row in the index list.

People are welcome to contribute a solution. I'll review

Tried to find a solution, but my Vue-skills are not good enough ;-)

I updated to v2.8.0 today. Same thing is still happening.

I have same issue in 2.8.0

and still the same issue in 2.9.2 - could you please fix this?

@nilsE it’s open source. You can fix it too

Any updates on this? I tried to find a solution but couldnt. My js skills are not good as well :(

@dillingham Please review the pull request, thanks :)

What's the current state of this issue? It seems I have the same problem on an app I'm building.


Convert ProgressBar, ProgressiveImage to styled-components - BISTArk

Converted the given components from SCSS to Styled components i have left the scss files as it is and commented out the import statements (So that it will be easy to revert back.

Sorry I'm opening this PR before being assigned the task.Hopefully, this will be assigned to me. :)

@BISTArk Could you also check for lint errors?

are there any more changes that i need to do? or is this ready to merge?


added Users class test

It might be better to split up the overall checks into smaller individual checks so we could know exactly what goes wrong, but I don't really see a problem with this.


Project description and readings for Rodrigo

Strong lensing happens when a massive foreground lens galaxy is aligned with a background source. But galaxies and groups in the environment (ENV) of the lens and projected along our line of sight (LOS) produce a second-order, weak lensing effect. This effect is described by a quantity called "external convergence" (kappa_ext, kappa). See McCully et al 2017 and Birrer et al 2017 for some theory.
Previous studies (Greene et al 2013, Rusu et al 2017, Birrer et al 2019) have shown that information available in astronomical survey catalogs for a sky region -- such as the observed objects' positions, brightnesses in each color filter, sizes, shapes, and approximate redshifts (~distances from us) -- can constrain kappa in that region reasonably well. So we know that there's information in the catalogs that tells us about kappa.
Where we can do better is in the modeling. Most studies so far have relied on manually calculating some summary statistics of the catalog, such as the number of galaxies in a region, and mapping it to kappa. As you can probably guess, this is a simplified model that potentially discards valuable information in the catalogs. Machine learning models can process all of the information.
The ultimate goal of this project is model the probability distribution over kappa, given the astronomical catalog entries of objects within ~2 arcminutes of a sky position. Models I'm thinking of are some various conditional density estimators (Dalmasso et al 2019), deep sets (Zaheer et al 2017), variational Bayes (Gal et al 2016 and lots of other papers), and graph nets (Battaglia et al 2018). We can start with getting point estimates of kappa rather than a full distribution, to see which features our model is picking up.
One important implementation detail is that the number of objects in our input X is variable, i.e. we are taking variable numbers of rows with a fixed set of columns from a catalog. Our output Y, for now, is one scalar, kappa.
You now have enough information to go do some literature review and write the introduction in your notes! I made an Overleaf template for your notes (view link here; log in with your Stanford email to edit).

@mueland might help your literature review!


fix(ui): Fix line breaks in vulnerability descriptions

Please see the commit for details.
@mnonnenmacher this is an easy & quick first fix for showing the vulnerability descriptions.

A small suggestion while modifying the component: IMO it would make sense for the references to be visible when you open the details, as it already takes a lot of spaces and I don't think there's any reason to have to click twice to see everything.


pthread_cond_wait return value incorrect

Describe the bug
The pthread_cond_wait always returns ETIMEDOUT
I try to use pthread_cond_wait and find that its return value is always ETIMEDOUT, even the thread is wakened normally.
To Reproduce
https://github.com/zephyrproject-rtos/zephyr/blob/c3715da5d95c10527e65624d47954987037f50c5/tests/posix/common/src/pthread.c#L100
we can easily check the return value here.
And I think this test case also needs to check the return value.
I guess we should reset the thread's ret_val in pthread_cond_signal and pthread_cond_broadcast, just like the pthread_mutex doing.
https://github.com/zephyrproject-rtos/zephyr/blob/c3715da5d95c10527e65624d47954987037f50c5/lib/posix/pthread_mutex.c#L148
Expected behavior
The thread calling pthread_cond_wait should return 0 (its wait time is K_FOREVER, so it should not return ETIMEDOUT.
Impact
We will fail to port some code because of the incorrect return value.

@povergoing - thanks for providing all of the detail and the RC.


Release/sprint 22 deploy

Salesforce Abandoned Cart integration
Paid Blog Template - New Header Fragment
Moving to prod
Fix #PM-568
Fix #PM-556
Test URLs:
Before: https://main--24petwatch--hlxsites.hlx.page/lost-pet-protection/lps-quote
After: https://feature-pm-568-abandon-cart--24petwatch--hlxsites.hlx.page/lost-pet-protection/lps-quote

Looks good to me.


New rules, breaking changes

Changes

Breaking change: @above is no longer min-inclusive
Breaking change: @below is no longer max-inclusive
Breaking change: @between is no longer min/max-inclusive
Introduced new rules: @from-width, @to-width, @between-from and @between-to
Breakpoint values in config can now be written in ints as well as in strings (valid values: 700, '700px', '700')

Reasoning
According to common terminology, "above", "below", "between" should not be inclusive. Also, media queries are usually used in pairs so that one of the queries excludes the break point. Added rules are named after the ones in the Rupture library.
Note
Please bump the version to 1.x.x as some of the changes are breaking.

Thanks!


Merge pull request #8 from Franch1co/main

Merge pull request #7 from Franch1co/develop

It's ok.


Reducing the minimum deployment target for iOS

Hey,
I noticed that you set the minimum target dependency for this at iOS 11.0. Does this pod really require iOS 11? If not, can you reset the target to something lower and push it to cocoapods? Thanks!

Thanks for your question!
This pod is based on Swift 4 and the default target dependency is iOS 11.0 in Xcode. I dismissed this problem.
I will reset to 8.0 and re-push it.


Removed extraneous json descriptions from internal types

Internal types do not require description but several still had them.
@bgrant0607 @nikhiljindal

Over to @bgrant0607.

Thanks. LGTM

Reassign to @lavalamp for another LGTM

LGTM

LGTM
Sure-- can we take the json tags out, too? :) :) In a follow-up.

@lavalamp Removing json tags didn't work last time we tried. That's #3933. However, at this point I think the best solution is to nuke api/types.go entirely.


fix to pass test under node 6.0.0

fix the test case to enable koa test pass in node 6.0

closing as duplicate of #723

@juliangruber  this is a PR to the master branch, #723 is a PR to the v2.x branch, they are obviously not duplicate.

[Current coverage][cc-pull] is 100%

Merging [#721][cc-pull] into [master][cc-base-branch] will increase coverage by +n/a%

@@           master       #721   diff @@
========================================
  Files           4          4
  Lines         336        413    +77
  Methods         0         81    +81
  Branches       96        101     +5
========================================
+ Hits          336        413    +77
  Misses          0          0
  Partials        0          0

4 files (not in diff) in lib were modified. more

Hits +77

Powered by Codecov. Last updated by [4809f08...92a8400][cc-compare]
[cc-base-branch]: https://codecov.io/gh/koajs/koa/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/koajs/koa/compare/4809f083acfa50f5fec53e655192c06fc1a6713b...92a84008f2bd48765bd97be02533f6c99a887241
[cc-pull]: https://codecov.io/gh/koajs/koa/pull/721?src=pr


Creating Dashboard for mean Latency

Hi everyone,
I am currently trying to create a Grafana Dashbooard with some of the Hystrix Prometheus metrics. One of them is a Graf that should show the mean latency over time.
Therefore I am using the following query:
avg(hystrix_command_latency_total_seconds_sum{command_group=~"$commandGroup", command_name=~"$commandName"} ) by (command_name, command_group)
Unfortunately it feels like the used metric just sums up all latencies over time, because my graph looks like this:

I tried to divide the metric hystrix_command_latency_total_seconds_sum by hystrix_command_latency_total_seconds_count, but this gives me very unrealistic low results.
Does anyone know how to properly create a query for a mean latency over time?
Thanks in advance!

Both metrics are always increasing, meaning the sum up the time and the counts from the start of the application. You already described this in your question.
To calculate a moving average of the request time, you'll first need to apply rate(metric{...}[5m]) first. Then calculate the ratio. In the example above this would look like this:
rate(hystrix_command_latency_total_seconds_sum[5m])
/
rate(hystrix_command_latency_total_seconds_count[5m])

When you later want to sum up metrics from several instanaces, first use rate() on your metrics, then sum(). See this excellent post "Rate then sum, never sum then rate" by one of the maintainers for details.
Please be aware that averages can be misleading, percentiles and histograms give you more insight on what's happening in your system. prometheus-hystrix already provides histograms. Read more about histograms in the blog post How does a Prometheus Histogram work?,

@ahus1 That was exactly what I am looking for, thank you very much!
And thanks as well for the articles, the histograms look really helpful.


Documenting how to use LLM gate and test_assist.metta

Hello All,
I think it will be good to create examples using LLM gate, test_assist.metta and other hyperon tools, to show how to build an agentic LLM. Will that be useful? Any thoughts?
Cheers!

Hi. Examples are available in the corresponding repo:
https://github.com/zarqa-ai/metta-motto
See examples, tutorial, tests folders there. Also, a tutorial will be available on metta-lang.dev in a week or so.
As for other hyperon tools, they will also be covered by tutorials and documentation, when they are ready.

Hi. Examples are available in the corresponding repo: https://github.com/zarqa-ai/metta-motto See examples, tutorial, tests folders there. Also, a tutorial will be available on metta-lang.dev in a week or so. As for other hyperon tools, they will also be covered by tutorials and documentation, when they are ready.

Hello @Necr0x0Der ,
That explains what I couldn't find any of this, the examples are in a different repo. Thanks for sharing this and letting me know about the new tutorail coming up on metta-lang.dev. Much appreciated.
Cheers!


Revise to pull csvs from utility_datasets repo.

This is mostly revising these lines in globals.R and the std_city_names() function in standarizers.R...

Changed approach, no longer relevant. Closing.


Resource management (opinions please!)

Curious what peoples thoughts are regarding managing things like DNS records, alarms, etc.
One option is individual CLI commands, this would be a little easier to implement, but awkward since the team can't review/audit them, commit them to source control, and requires listing a bunch of resources to see the state of the world.
$ up dns ls
$ up dns add apex.sh blog.apex.sh A <IP_ADDRESS>,<IP_ADDRESS>,....
$ up dns add apex.sh ping.apex.sh CNAME ping.netlify.com

The more "correct" approach these days would be more like Terraform infra-as-code style, where the config in your repo is the source of truth, though it may be less familiar/intuitive to some people.
For DNS looking something like the following (for apex.sh zone):
{
  "domain": "apex.sh",
  "dns": {
    "blog.apex.sh": {
      "type": "A",
      "value": [
        "<IP_ADDRESS>",
        "<IP_ADDRESS>"
      ]
    }
  },
  "ping.apex.sh": {
    "type": "CNAME",
    "value": "ping.netlify.com"
  }
}

Changes would be previewed via up plan which shows what will be updated/created/deleted etc and applied with up apply or similar. Note this is not a replacement for Terraform or CloudFormation, just need to provide enough for people to get apps bootstrapped.
Pros of CRUD style:

Familiarity due to matching Heroku and friends
?

Pros of Terraform style:

Single source of truth / overview of app just from reading app.json
Preview changes before applying them
Easily reviewable via GitHub
?

Any opinions?

What needs implementing for now:

[x] IAM role(s)
[x] DNS (explicit)
[ ] DNS (implicit)
[x] API Gateway
[x] ACM
[x] parameterize tmpl
[x] outputs
[x] create stack
[ ] update stack
[x] delete stack
[x] plan
[x] apply
[x] event streaming
[x] CLI integration
[ ] styling / ux

Why not both? CLI commands read/update central config.

Some day maybe, I think I'll start with the config stuff for now, that's more the best practice the past few years.  Secret env vars are probably the one exception I can think of, having those in config is obviously not good haha.

Then yeah, I'd roll with config file first. Not only easier, but supplementing with a CLI later (as opposed to vice versa) is more additive / not breaking.

Thoughts on something like TFE? It's super nice to have the changes planned/applied by a third party and reviewed by the team. We've had significantly fewer outages after moving stuff from "normal" Terraform to Terraform Enterprise.

@stephenmathieson nice! Longer term that definitely makes sense, even running up from the the CLI is gimmicky beyond super small companies, but people like gimmicks haha, sadly, at least it's low barrier to entry I suppose.
Just using CloudFormation for now, little frustrating that it's slow but TF isn't very embeddable right now so it'll do!

needs a bit of polish but pretty much done


Restore old call to action with new letter

This removes the town hall locator widget and restores the old call to action which will submit to Mothership and then forward it on to a specified Action Network petition, contact reps in Congress, and submit an FCC complaint.
Cleaned up a bunch of stuff and removed the CSS delayed JavaScript load, still lots more cleanup remaining.
TODO: This still needs to be updated to point to a new Action Network petition, needs updated subject line and copy for comment that will be sent to Congress and FCC, and needs a little design work and post-action share button on the thanks modal.

@holmesworcester @gaudette75 This should be ready to merge after updating the form to point to a fresh Action Network petition.

Sharing modal should say:
"Thanks! Now, can you share?"
"We need as many people as possible to take action this week!"

Also, if "share on twitter" launches the twitter tool signup (it should ideally) it should say "join twitter brigade"


Add Device Support Information to Feedback Intent #2494

Description
Added Support Info to email when the user wants to share feedback.
Fixes #2494 Collection of device's essential information when user want to share feedback
What changes did you make and why?
When a user wants to share some feedback, the current scenario does not include the device name, model number, etc. so I added it the email template.
Tests performed
Tested betaDebug on Xiamo Mi A1 with API level 28.
Screenshots showing what changed

Codecov Report

Merging #2499 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2499      +/-   ##
=========================================
- Coverage     5.8%    5.8%   -0.01%
=========================================
  Files         257     257
  Lines       12261   12271      +10
  Branches     1101    1101
=========================================
  Hits          712     712
- Misses      11490   11500      +10
  Partials       59      59

Impacted Files
Coverage Δ

...n/java/fr/free/nrw/commons/CommonsApplication.java
42.3% <ø> (ø)
:arrow_up:

...free/nrw/commons/theme/NavigationBaseActivity.java
21.93% <0%> (-1.52%)
: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 114a932...0f54b6e. Read the comment docs.

@maskaravivek Changes made, also moved app version from title to body :)

For the last line I guess you meant "App version"?
Please make only the first letter of each line capitalized, for instance
"Network type" instead of "Network Type"
Please make the title "-- Technical information --" instead of
"--Technical-Info--"
Thanks! :-)

On Fri, Feb 22, 2019 at 4:26 PM Madhur Gupta<EMAIL_ADDRESS>wrote:

@maskaravivek https://github.com/maskaravivek Changes made, also moved
app version from title to body :)
[image: screenshot_20190222-125228]
https://user-images.githubusercontent.com/30932899/53226470-1dda6f80-36a1-11e9-9c7a-9d89e8b51a9f.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/pull/2499#issuecomment-466300789,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBhm4F69d04ZA-ozPprB_SjkKnxu3ks5vP5uigaJpZM4bHDdq
.

@nicolas-raoul
Changes made

Works well. Merging it. :)


React step 5

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

https://carbon-tutorial-tianjunzhao.mybluemix.net/#/
This is my  mybluemix.net URL

You did not start with a checkout of step 5 per instructions: https://www.carbondesignsystem.com/tutorial/react-step-5#branch
This is causing your layout to be incorrect. Please try again

No updates in 60 days. Closing.


API search by country

Is there an example of how to query the API to find stations by a given country name/code?

below an example for using cURL command in a CLI for the current application.
Replace the "78" (Greece) with the T_GO_TERRITORY_REF.TERRITORY_ID of your choice.
curl 'https://oscar.wmo.int/surface//rest/api/search/stationSearch' -H 'Content-Type: application/json;charset=UTF-8' --data-binary '{"operation":"AND","nrt":"false","quickSearch":false,"wmoRaOrCountryId":"C-78"}'
Country IDs can be retrieved with the call:
https://oscar.wmo.int/surface/rest/api/referenceData/list/TerritoryRef/1
For the next Release of the productive application (R1.2.3 - no M2M) currently on DEPL environment and to be deployed end of February, there will be a more user-friendly API available. You will be able to get a list of stations in a country with the following call:
oscardepl.wmo.int/surface/rest/api/search/station?territoryName=GRC
The notation used for the TerritoryName (GRC in this case) is the WMO_306_CD available in the code registry.
This call will be also available for the productive M2M release but not earlier than the end of May.


[R24.08] [Simple Data Exchanger] Release Checks

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info
Please provide information on what you want to be included in the Eclipse Tractus-X release.
If you are not owner of this issue, please provide the information as comment to the issue.
Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.
Version to be included in Eclipse Tractus-X release:
*** Version: 2.4.2
*** Helm Chart Version 0.1.11
Leading product repository: repository link
Compliance Verifications
This issue tracks all checks, that need to be performed for a product release in Eclipse Tractus-X.
General Checks

[ ] Tractus-X Release Guidelines(TRGs) fulfilled https://github.com/eclipse-tractusx/managed-simple-data-exchanger/issues/51
https://github.com/eclipse-tractusx/.github/blob/main/.github/ISSUE_TEMPLATE/qg-checklist.md

Make sure to open and fill in a separate documentation issue in your product repository using the Quality Gate Checklist issue template

[!NOTE]
Note: most criteria for documentation and security are now covered in TRGs

Security Checks
Test Results

[x] E2E Integration Test passed
[ ] User Journey approved
User Journey should be checked only fro Data Providing and without PCF

Helpful Links

Eclipse Tractus-X openAPI specs on SwaggerHub

Hi,
as discussed in today's open meeting and referring to today's email, please remove the check topics for Interoperability, Data Sovereignty and Threat Modeling in your description

QG Review 23-July

Leading product repository Link is missing
TRG Check needs to be done
User Journey needs to be approved
E2E test is pending

@ther3sa  If I understood correctly the TRG which we should follow for 24.08 are those ones: https://github.com/eclipse-tractusx/.github/blob/main/.github/ISSUE_TEMPLATE/qg-checklist.md

Planned E2E Tests for release 24.08 on Catena-X INT environment have been performed successfully. Thank You!

Could you set the check for the e2e test and could you give me an update on how far you are with the TRGs and the user journey?

I have a question. Does this issue only affect the Managed simples data exchanger SDE? Is there an additional issue for the frontend and the backend? :)
See table https://github.com/eclipse-tractusx/sig-release/issues/821

@almadigabor  could you give me an update on how far you are with the TRGs? :)

I have a question. Does this issue only affect the Managed simples data exchanger SDE? Is there an additional issue for the frontend and the backend? :) See table #821

Hello Theresa, it is for all of them. The issue is for the entire SDE.
In regards with the TRG it is in progress more than half is done

I have a question. Does this issue only affect the Managed simples data exchanger SDE? Is there an additional issue for the frontend and the backend? :) See table #821

Hello Theresa, it is for all of them. The issue is for the entire SDE.
In regards with the TRG it is in progress more than half is done

okay thank you for your update :)

Hey @ther3sa! Working on it, hopefully I'll be done a couple of hours. Who's doing TRG 9.01 UI/UX styleguide checks? I'm not really familiar with the topic.

Hey @ther3sa! Working on it, hopefully I'll be done a couple of hours. Who's doing TRG 9.01 UI/UX styleguide checks? I'm not really familiar with the topic.

thanks for the update :)
@stephanbcbauer do you know who can do the TRG 9.1 UI/UX style guide check?

@ther3sa  when is the last day for the QG approvals?

@ther3sa when is the last day for the QG approvals?

Today is the last day for QG approval

@ther3sa when is the last day for the QG approvals?

Today is the last day for QG approval
We will finish it today. for all three products until EoB

Okay thank you for your update :)

I approve the QG with the following versions:
Helm Chart Version: 0.1.12
App Version: 2.4.3

@almadigabor I received an email, but I can no longer see your comment.
Are the TRGs ready? Could you check the box then?
Is the TRG 9.01 UI consistency/styleguide for UI not needed here either?

Needed to recheck something, so I deleted the comment. I approve the QG now with the following versions:
Helm Chart Version: 0.1.12
App Version: 2.4.3

Could you check the TRG in the description. After that I can give my approval :)

Congrats:

Quality Gate fully approved with all necessary pre-requisites fulfilled!

Thanks for all your efforts :)


[Gekidou] Permalink UI (excluding non-happy path)

Summary
This PR changes the UI of the permalink view excluding the UI related to the non-happy path. The non-happy path is being worked on #6294 I believe.
Ticket Link
https://mattermost.atlassian.net/browse/MM-42107
NONE

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/23070
https://circleci.com/gh/mattermost/mattermost-mobile/23069

Artifact links:
https://output.circle-artifacts.com/output/job/d5230525-c51c-49ae-b664-c6929aff7588/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa
https://output.circle-artifacts.com/output/job/92e909c4-bb77-44f3-884e-a38c500a5399/artifacts/0/tmp/artifacts/Mattermost_Beta.apk

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/23081
https://circleci.com/gh/mattermost/mattermost-mobile/23080

Artifact links:
https://output.circle-artifacts.com/output/job/e301fa1c-832d-4825-bc02-536b9f039fc6/artifacts/0/tmp/artifacts/Mattermost_Beta.apk
https://output.circle-artifacts.com/output/job/63e4bf4b-ac47-4f51-a5c6-834c796bac5b/artifacts/0/tmp/artifacts/Mattermost_Beta.ipa


Fix OldDot -> NewDot workspace validation

Details
So here's what we were doing before:

The WorkspaceSidebar component was dependent upon two optional props, allPolicies and policy. The order in which these props would be provided via Onyx is not guaranteed.
To check if we've linked to a valid policy, we were waiting for allPolicies to load, then checking to see if the individual policy was still not loaded. If it was not, we'd assume it was invalid. So we were making the false assumption that both the allPolicies and policy props would be loaded at the same time.
To fix this, we really need to know whether the policy was found in Onyx or not, but unfortunately there's no way to tell the difference between a default value for an Onyx prop, and an Onyx prop just never showing up. So instead, we wait for allPolicies to load, and check if the linked policy (taken from the URL) is included in the list of policies. If not, we assume the policy is invalid.

Fixed Issues
Fixes bug discussed in this PR and in slack here.
Tests / QA Steps

Log into NewDot.
If you don't already have a workspace, click on the global create menu and create one.
Close the NewDot tab.
Open OldDot in another tab, log in with the same account, and go to /admin_policies
Click on the workspace.
Verify that NewDot opens in a new tab and displays the workspace without any issue.
Log out of NewDot, and close the tab again.
Back in OldDot, click on the workspace again.
Verify that NewDot opens in a new tab and displays the workspace without any issue.
Log out of NewDot, and close the tab again.
Open a second OldDot/admin_policies page in another tab or window.
Delete the workspace in the second OldDot tab.
Back in the first OldDot/admin_policies page, click on the workspace again.
Verify that NewDot opens in a new tab, displays the workspace for a moment, then navigates home and displays an Invalid Workspace error.

Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Potential alternate solution might be to make the policy prop required, and if it's null then we know that it wasn't found in Onyx. But I'm not sure if withOnyx works with required props or not (some changes I made in relation to the betas prop in other files to suppress errors makes me think no, withOnyx doesn't really work with required props).

Broke for me on these steps:

Open OldDot in another tab, log in with the same account, and go to /admin_policies
Click on the workspace.

Got a white screen and lots of errors in the JS console going to include them all just in case it's useful and I can't reproduce again.

JS console logs.txt
Refreshing the page doesn't bring me back to a usable website. I'm just stuck. So something that we put in storage is preventing the app from running. Gonna try to clear storage and see if it happens again.

Think it's maybe related to trying to load a report behind the workspace settings page not too sure but one error looks related to ReportActionCompose

Cleared storage
Logged out of New Dot
Accessed workspace via Old Dot policies page
Still seeing this guy

Anyone opposed to just returning a loading spinner in the sidebar until the policy is available for now?
I like the idea to show an error if the policy truly doesn't exist (bad link in old dot or somewhere else definitely seems possible), but unsure if it's a mainline flow. Seems way more important to have everything load OK the first time when we hand off from OldDot to NewDot.

Anyone opposed to just returning a loading spinner in the sidebar until the policy is available for now?

So for invalid workspaces we would just show an infinite loading spinner? If we can't find another solution that's fine. But the root problem is really that we can't tell the difference between these two scenarios:

Policy not loaded from Onyx yet
Policy not found in Onyx

But the root problem is really that we can't tell the difference between these two scenarios

I hear that and this is definitely a point of confusion for this flow. But I'd counter that the problem we are experiencing is:

We are setting policies one by one into Onyx, but the code acts like they are all set at once. So, if you have more than one the transition only works if you tap the one that Onyx sets first.

The problem isn't that we fail to show an error message when a policyID is invalid. That might be a good problem to solve eventually, but it's not blocking us from shipping this.
Anyways, here's what the spinner fix looks like:
https://user-images.githubusercontent.com/32969087/134456406-2c0cd743-2de8-41d9-b53b-1c8da35b1899.mp4

Closing this out in preference of https://github.com/Expensify/App/pull/5439/files.


Complete safechecker

[x] Finish proofs about universes and move them to their rightful place
[x] Generalize context conversion to (contravariant) context cumulativity. This lays the ground-work for moving to contravariant subtyping in the future as well.
[x] Finish checking of inductive type declarations.

It needs a rebase but otherwise: the safechecker is sound, admit-free, does not rely on additional axioms and finally does real subtle checks on inductive declarations :) safe_checker_test.v still passes so we have enough to check HoTT devs already (and it's not absurdly slow).

This also add a PCUICWfReduction file with proofs that red* o subterm and red+ + subterm are wellfounded, so as to write recursive definitions easily that combine taking head-normal-forms and recursing on subterms or strict reducts on the initial argument.

To note: I think the checker is pretty much complete as well as sound, except for cumulative inductive types. We approximate the check of cumulativity using syntactic equality whereas Coq is smarter and uses a special purpose reduction/comparison function. That's next.

I pushed the fix of the error message. Given the size of the huge cleanup/refactoring I'm planning to start now I'll merge this and do the cleaning in a separate PR that will be easier to review. It will be mainly about moving lemmas to their right place.


Mockdata: Add a sql script that inserts mock storage locations

Description
Currently there are no mock storage locations in DAMAP to show of this part of the frontend. The mock data can not be added into the DB by default, since  institutions would need to remove it before deploying, which is a hazzle.
Proposed solution
Write a sql script, that adds the test data directly into the deployed postgresql container.

We decided to not include the script in the project, since in its basic form its already contained in CUSTOMISING.md.


tensorflow model to MLIR

I want convert tensorflow model to MLIR .
I saved tensorflow model using model.save() as saved_model.pb.
How can lower the convert model to MLIR (affine/std dialect)?
What are the steps to do so?
Thank You

I suggest to post your question in https://groups.google.com/a/tensorflow.org/g/mlir


Feature: Display Coin Value

I keep my coin at an exchange because I like to see what they are worth. Could something be integrated into the wallet to get the current price from Polo, and then display to the user what the value would be in BTC and USD?

This is an interesting feature and definetly possible... but this would "tie" PascalCoin to a certain "data provider"...
Perhaps PascalCoin could create a plug-in system for this and then calculate average price from all data provided from plug-ins.
This way at least it would not be "tied" to a certain provider. But user can decide themselfes which ones to "tie" to dependent on which plugins they installed for this !


Added Maths Quiz app

Title and Issue number
Maths quiz app with number of questions choice #2379
Close #2379
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

https://github.com/pranjay-poddar/Dev-Geeks/assets/133862694/4e31813f-3c9b-4d58-93b8-c1baff190374

@MohitGupta121 please merge this

@pranjay-poddar Can you please merge this?

@pranjay-poddar @MohitGupta121 pls merge this


added auth diagrams

btw you can display the markdown preview in the Files changed tab like so:

Gonna merge, if you notice anything wrong with these diagrams later then PR to fix would be appreciated 🙏


[BUG] Fox5Image.toPIL() appears to produce incorrect colors

The bug
When using Fox5Image.toPIL() to convert a Fox5 image to a PIL image, the resultant image appears to have incorrect colors

Original Test Image as in Fox Editor

Resulting image that was saved from the PIL object produced by Fox5Image.toPIL() - It appears that only the green channel from the image and arbitrary transparency is saved.

Proposed solution
It appears that the issue is on this line here.
https://github.com/FelixWolf/libfurc/blob/58410b1d9332db81b4a342a52a43a2ae36989a6a/libfurc/fox5.py#L67
When the line is substituted as follows
data += bytes((self.data[pixel+1], self.data[pixel+2], self.data[pixel+3], self.data[pixel+0]))

the colors should be saved correctly.
Test code
Below is the code snippet I used to save the above images from a fox file, for reference - in case there's something in my code that may have caused the issue instead.
from libfurc import fox5

def getImage(fox,id):
    return fox.body["ImageList"][id]

fox = fox5.load("exportTest.fox")
img = getImage(fox,0)
img = img.toPIL()
img.save("testcard.png")
#img.show()

Thanks you for the report!
Looks like I was trying to the ARGB pixel as if I were going to encode it(thus encoding it as BARG).
This has been fixed as of 6b14c1b.


[TEST: Suggested formatting improvements]: for README.md for better readability

This PR suggests formatting improvements for the file.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/what-are-tabs.md
85
3
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Bounds for L-BFGS-B for PyTorch or Jax

Does PyTorch or Jax backend support bounds?

Yes, the bounds are related to the scipy minimize algorithm used, not to the backend.


fix: add delay before talking to roku web server

also replace old request and request-promise with axios

got it, fixed


Dev to main sync

Developer Name: @MayurLund
PR Number(s):-

#414

Issue Ticket Number:-

#387

Backend changes

[ ] Yes
[x] No

Frontend Changes

[x] Yes
[ ] No

Database changes

[ ] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

[ ] Yes
[x] No

Deployment notes(Any special instructions for the deployment)

[ ] Yes
[x] No

Tested in staging

[ ] Yes
[x] No

Video
I have attached the videos for reference


Bug: text node broken after removing selection as entering a composition symbol like korean.

Lexical version: 0.7.5 (latest)
This bug only happens in Chrome, Safari and not in FF.
Steps To Reproduce

Select more than two text nodes (above one should be fully wrapped)
Enter any symbol affecting composition event like Korean symbol.
selection will be removed but symbol doesn't appear and can't write any word at the focusing text node

https://user-images.githubusercontent.com/74358372/210831408-eef66347-c4aa-4baa-846d-5240e8895517.mov
The current behavior
When the selected text nodes are replaced, the new node has empty TextContent and can't be modified. (until newline)
The expected behavior
When the selected text nodes are replaced, the new one will have contents I typed and work correctly.

I found a temporary solution about this bug, but I'm not sure it doesn't have any side effects.

I found a temporary solution #3679  about this bug, but I'm not sure it doesn't have any side effects.


Pixhawk Pro safety switch pressed state changes randomly

When no safety switch is connected the pressed state changes randomly. As a workaround I've disabled the GPIO handling and forced the state to false.

@AndreasAntener
GPIO_BTN_SAFETY is defined twice, once in board_config.h (Pixracer style, because it has no IO processor) and once in IO driver. I would try commenting this line and this line.

@AndreasAntener @davids5
Changing this line by
#define GPIO_BTN_SAFETY (GPIO_INPUT|GPIO_CNF_INPULLDWN|GPIO_MODE_INPUT|GPIO_PORTB|GPIO_PIN5)
solves the issue. David, is that a good way of dealing with it or should we implement a hardware pull-down resistor?

@klopezal - I have a PR inbound.
We need to look for this same class of mistake in the board_config that are a byproduct of the copy from fmuV4.
I found one more it is in the incoming PR

@AndreasAntener @davids5
See https://github.com/PX4/Firmware/pull/6808

@davids5 Thanks! I don't fully understand the fix though.
For my understanding: GPIO_BTN_SAFETY is still referenced in px4io.h. Wouldn't that also require changing? Also I'm a bit confused since GPIO_BTN_SAFETY_FMU now only exists for v4pro.

There are two issues.
The first is that an unconnected signal had the same name as the button input. By changing its name that disables the fmu from treating that input as the safety switch.
The second issue is that the actual safety switch connection to the PX4 IO is missing a pull down. The proper fix is to add the pull-down on the Hardware. An alternate workaround is to use a modified bootloader and firmware build that both enables  pull down  on that gpio.
In this case because the signal is at the edge of the board and the pins are large I would recommend soldering through hole component on it and connecting it to ground. It needs to be 1.5 k
On March 13, 2017 2:23:11 PM HST, Andreas Daniel Antener<EMAIL_ADDRESS>wrote:

@davids5 Thanks! I don't fully understand the fix though.
For my understanding: GPIO_BTN_SAFETY is still referenced in
px4io.h. Wouldn't that also require changing? Also I'm a bit confused
since GPIO_BTN_SAFETY_FMU now only exists for v4pro.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/PX4/Firmware/issues/6799#issuecomment-286284617

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

The first is that an unconnected signal had the same name as the button input. By changing its name that disables the fmu from treating that input as the safety switch.

Fixed In FW


Certification printing / saving as PDF not formatted correctly

Describe the bug
Certifications are not correctly formatting when downloading / printing.
To Reproduce
Steps to reproduce the behavior:
View a certification. For example: https://www.freecodecamp.org/certification/mainlycoding/javascript-algorithms-and-data-structures
Then right click save as PDF or print. You will see the formatting jumbled, despite efforts to manually resize. The signature, for example, is way too big.
Screenshots
Here's the twitter thread with some screenshots: https://twitter.com/Lebron29ayy/status/1549522926751318017/photo/1
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser: latest Chrome and Firefox tested – it doesn't work in either

Sounds like the fix for this might require some research into <link media="print" />. That is just my initial suggestion

An issue with the help wanted label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

Can you assign this to me so that I can look into it?


forseti server config/error in creating inventory with folder ID

I'm getting an error when I add the root_resource_id in forseti config as below(added an example folder ID),
root_resource_id: folders/12345378162
The following is the error that I was getting
Exception in thread Thread-77:
Traceback (most recent call last):
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/base/resources.py", line 326, in try_accept
self.accept(visitor, stack)
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/base/resources.py", line 359, in accept
visitor.visit(self)
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/crawler.py", line 118, in visit
resource.get_org_policy(self.get_client())
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/base/resources.py", line 112, in wrapper
result = f(*args, **kwargs)
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/base/resources.py", line 891, in get_org_policy
for org_policy in org_policies_iter:
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/services/inventory/base/gcp.py", line 2156, in iter_crm_organization_org_policies
for org_policy in self.crm.get_org_org_policies(org_id):
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/common/gcp_api/cloud_resource_manager.py", line 482, in get_org_org_policies
paged_results, 'policies')
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/common/gcp_api/api_helpers.py", line 87, in flatten_list_results
for page in paged_results:
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/common/gcp_api/repository_mixins.py", line 258, in list_org_policies
verb_arguments=arguments):
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/common/gcp_api/_base_repository.py", line 493, in execute_search_query
request = self._build_request(verb, verb_arguments)
File "/home/forseti/.local/lib/python3.6/site-packages/forseti_security-2.25.0-py3.6.egg/google/cloud/forseti/common/gcp_api/_base_repository.py", line 378, in _build_request
return method(**method_args)
File "/home/forseti/.local/lib/python3.6/site-packages/googleapiclient/discovery.py", line 782, in method
% (name, pvalue, regex)
TypeError: Parameter "resource" value "organizations/folders/12345378162 " does not match the pattern "^organizations/[^/]+$"
During handling of the above exception, another exception occurred:

This issue is resolved after adding GCS object creator permissions to Forseti project's gcp-sa-cloudasset default service account which is require for asset export to DB. There is no mention about this in Forseti documentation. Please add it.