topic [nfc]: Fix internal references to "subject"; add TODO-server for others

The bulk of the places we mention "subject" are direct references to
either the property of that name on Message or somewhere else in
the server API.  Most of those, and in particular Message#subject,
are still that way in the current API.
  In particular, for any given piece of API, I
won't want to make a conversion before we've at least settled on the
API change so that we can convert to what we know is the future API.
However, there are a handful of places where we say "subject" to
mean "topic" and it's entirely internal to the mobile app.  So
here we go ahead and fix those.

And in the handful of places where the API change has already happened on the server and we didn't already have a TODO-server comment for it, add one now. Including in messages' edit history, where the server-side change hasn't yet landed but is expected to soon: zulip/zulip#21309.

Thanks! Merged.


move to containers/image v5, buildah v1.11.4

Move to github.com/containers/image v5 and buildah v1.11.4. Builds which specify a base image using a digest or tag which points to a manifest list should not produce errors when pulling the base image, otherwise there should be no visible changes to behavior.
Includes a proposed update to update-deps.sh which more or less does what make vendor does in the buildah source tree.

/lgtm

@adambkaplan ptal

@bparees ptal

/retest

@nalind is there a BZ associated with the "build fails if FROM uses a mainfiest list"? I assume there is a buildah-related issue out there tracking this fix.

I'm not sure we were tracking a problem in builds - one of the main motivations was https://github.com/cri-o/cri-o/issues/2157, along with other issues elsewhere tracking the Digest of source image's manifest would not match destination reference error at run-time.  It actually looks like we still have a bit of work when using a base that we specify using a digest.

Additional work in https://github.com/containers/buildah/pull/1960 should be relevant.


[Feature] luarocks compatibility layer

Bootstrap a luarocks installation.
Provide a compatibility layer for unimplemented APIs that delegates to luarocks.
Transform installed luarocks packages to rocks packages.
We'll need to find a way to tell luarocks which dependencies are installed.

@mrcjkb do we think it's safe to close this one now?


Basic Menu component

First iteration of the Menu component

horizontal menu
Menu.Item supports active and onClick
isConformant test passes for both Menu and Menu.Item components

Proposal for first implementation:
<Menu> always ul
<Menu.Item> always li > a

<Menu items={[ ... ]} /> always items with li > a
<Menu.Item as='div'> always li > div

Proposal for first implementation:

Implemented with following limitations:

<Menu as='div'> renders as div (but does not make much sense at the moment as Menu.Item always renders as li
I had to disable isConformant tests for Menu.Item which fail because both props.className and props.as are applied to the nested <a> element, not to the <li>

I had to disable isConformant tests for Menu.Item which fail because both props.className and props.as are applied to the nested  element, not to the

For consistency, what about applying them to the li instead?

This looks good for the first iteration, merge at will 👍


more general mask support

the general case of attention is (using annotations from jaxtyping)
q: Float["lq d"]
k: Float["lkv d"]
v: Float["lkv o"]
mask: Bool["lq lkv"]

returns: Float["lq o"]

but it looks like right now this library only supports a 1 dimensional mask?

@GallagherCommaJack at the moment, it only supports key masking
generalized 2d masking would defeat the purpose of flash attention, as you incur the quadratic cost


Amazon In App Purchase fails with Amazon App Tester: IabResult: 6, Current UserId doesn't match purchase UserId

Hi!
D/pbchess (23911): Purchase finished: IabResult: 6, Current UserId doesn't match purchase UserId (response: 6:Error), purchase: PurchaseInfo(type:inapp): {"orderId":null,"packageName":null,"productId":license,"purchaseTime":0,"purchaseState":0,"developerPayload":null,"token":q1YqVrJSyslMTs0rTlXSUUoB8gxNjCxMzC1MLS0MzM2BYqUgFcYePuYRBQWuvhlF_u4ueaVFlrqlOWWF-blFwelmhZX-Lt65iRnmZjleobZALSVKVoa1AA}
queryInventory() also shows that item is not purchased. But:

I can see this purchase in Amazon App Tester
If I try to purchase this item again, I get: "IabResult: 7, Item is already purchased"

Libs used:
openiab-<IP_ADDRESS>.jar, in-app-purchasing-2.0.1.jar (also tried with the latest in-app-purchasing-2.0.61.jar - the same result)

Hi.
I'm pretty sure this issue is only relevant to App Tester.
Most likely you change Amazon User option under 1. User Account Settings tab.
Real Amazon Store shouldn't return items purchased by another user.

Roman, I used user #1 in App Tester and didn't change this setting. I see in the logs that purchase UserId is empty while current UserId is my App Tester user #1.

Well, this is weird.
Can't you use Delete All option under 3. Manage Transactions tab and try to reproduce this?

I've deleted all purchases and tried again several times. Is is reproduced constantly every time I make purchase.

Hmm... Just re-tested it with my HTC Sensation XE. Purchase works well... But on my Cube Talk 9x tablet this problem is stable reproducible.

As I said, I'm pretty sure App Tester is to blame for this.
If you use OpenIAB in your application, I recommend  trying to reproduce it with Amazon live testing.

So, It is not quite clear whether it is App Tester problem or Open IAB library problem. Anyway, thanks for help. I'll use live testing.

Please reopen this issue if you find anything.


can i show every time when activity call?

now its showing only one time but i need to show it every time when activity call. is it possible?

The usageId is a unique String. So you can create a unique ID programatically every time, for example:
String usageId = new Date().toString();

@pratikcouragedigital , It is possible by the way which @cuiti  has shown. However, I added a method showAlways(boolean) into SpotlightView.Builder for ease. When you pass true, it will show every time you open that same screen.


GroupMap for desktop

Changes

divide sidenav in map and stores #567

zoom into stores on storeview
remove storemap

add invitations to group menu
made font-size of toolbars a little smaller on mobile
added users to groupMap, only really makes sense after merging #569

ToDos

[ ] Replace user and store icons with nicer ones
[ ] Think of a better layout for groupMap
[ ] figure out if there should be an overview button

For a screenshot see #567

Codecov Report

Merging #572 into master will decrease coverage by 0.39%.
The diff coverage is 78.48%.

@@            Coverage Diff            @@
##           master     #572     +/-   ##
=========================================
- Coverage   98.59%   98.19%   -0.4%
=========================================
  Files         246      250      +4
  Lines        3920     3999     +79
=========================================
+ Hits         3865     3927     +62
- Misses         55       72     +17

Impacted Files
Coverage Δ

client/app/components/group/group.js
100% <ø> (ø)
:arrow_up:

...nt/app/components/group/groupDetail/groupDetail.js
100% <ø> (ø)
:arrow_up:

...nt/app/components/group/_groupMap/groupMap.spec.js
100% <100%> (ø)

...p/components/group/_groupMap/groupMap.component.js
100% <100%> (ø)

...onents/group/groupDetail/groupDetail.controller.js
100% <100%> (ø)
:arrow_up:

client/app/components/group/_groupMap/groupMap.js
100% <100%> (ø)

client/app/services/group/currentGroup.service.js
80% <33.33%> (-20%)
:arrow_down:

...p/components/group/store/storeDetail.controller.js
75% <50%> (-25%)
:arrow_down:

.../components/group/_groupMap/groupMap.controller.js
58.82% <58.82%> (ø)

... and 3 more

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 ea162d3...8539144. Read the comment docs.


Footer

Footer being an integral part of any website is missing. Add a footer with contact and other info about the website

@bharathmb7 a small footer has been added by another contributor, so I advise you to sync your fork of the repository so you can work on the updated design.


Some small changes

This introduces a config property to hide the rect around a legend item.
It also changes the distance calculation of the title. (@hwbllmnn This might break layout when using multiple legends, right?)

This PR also makes some smaller changes to the (build-)folder structure.

The layout should be fine, the actual rendered height is determined in order to break into another column.


Projection Testing

Axon provides fixtures when it comes to Saga and Aggregate testing. When it comes to projection testing developers are left on their own. It might be useful to provide a functionality in axon-test module for testing projections.
Here is a proposal:
ProjectionFixture fixture = ProjectionFixture.registerHandlingComponent(new MyProjection()) // here we can have scanning of @EventHandlers and @QueryHandlers
                                             .registerResource(new MyRepository()); // or mock

fixture.given(events)
       .whenQuery(query) // whenScatterGatherQuery, whenSubscriptionQuery
       .expectResult(queryResult);

...

fixture.given(events)
       .andSubscriptionQuery(query)
       .when(event)
       .expectEmittedUpdate(anUpdate);

Perhaps related, but would this fixture be able to test Error cases? Like having the errorhandler kick in or pushing TEP in error and retry mode?

big +1 I was looking to test queries but not possible

Yes, it is a bit frustrating to try to use the @QueryHandler/QueryGatway without testing support from the framework

yes, I will agree, to have a possibility to test an event handling with some kind of Fixture will be helpful

Definitely +1

+1.

+1

+1

Added this issue to release 5.0.0 as we intend to validate the feasibility of this in the new APIs.


Stop and Seek should be immediate actions.

WaitBy blocks the calling thread for a specified duration in milliseconds.
This has the unfortunate consequence that if a midi event for instance has a delta time of 5 seconds, that the play thread is blocked for 5 seconds.
A Stop or Seek command will then be effectuated after those 5 seconds.
This can be solved by making IMidiPlayerTimeManager.WaitBy abortable or by having a different way of waiting the appropriate amount of time dictated by the delta time.

Also this behaviour prevents regular playback progress updates, as during the wait no progress can be reported back.

Furthermore, seeking should not trigger the public EventReceived of MidiPlayer.
The goal is to seek to a position, not to replay the entire midi file upto the position.
Subscribers of MidiPlayer.EventReceived should not be triggered by this.
This may be implemented by giving the MidiEventLooper.EventReceived event an argument that tells the MidiPlayer that the event  is a normal play event or if it is the result of the seeking process.


influxd restore panic

Bug report
System info:
InfluxDB 1.5.1, Ubuntu 16.04
Steps to reproduce:

Trying to restore a full backup made on another machine (size around 31 GB)
influxd restore -db telegraf -newdb restore_telegraf -portable -host '<IP_ADDRESS>:8089' -rp autogen /root/IDB_Backups/telegraf/

Expected behavior:
Restoring data to InfluxDB
Actual behavior:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x96fac6]
goroutine 1 [running]:
github.com/influxdata/influxdb/cmd/influxd/restore.(*Command).updateMetaPortable(0xc4201f4000, 0x0, 0xf0)
/go/src/github.com/influxdata/influxdb/cmd/influxd/restore/restore.go:316 +0x86
github.com/influxdata/influxdb/cmd/influxd/restore.(*Command).runOnlinePortable(0xc4201f4000, 0xc4200100c0, 0x8)
/go/src/github.com/influxdata/influxdb/cmd/influxd/restore/restore.go:104 +0x2f
github.com/influxdata/influxdb/cmd/influxd/restore.(*Command).Run(0xc4201f4000, 0xc4200100c0, 0x8, 0x8, 0xc42007a200, 0xc42007a2a0)
/go/src/github.com/influxdata/influxdb/cmd/influxd/restore/restore.go:78 +0x209
main.(*Main).Run(0xc42005bf40, 0xc4200100b0, 0x8, 0x8, 0x5acc8de7, 0x3579b4ee)
/go/src/github.com/influxdata/influxdb/cmd/influxd/main.go:115 +0xf04
main.main()
/go/src/github.com/influxdata/influxdb/cmd/influxd/main.go:45 +0x16a
Additional info:
When I opened the bug I thought the cause of the error is, that the InfluxDB service is not running, but I started it, can connect to the DB, but still get this error.
netstat -plunt shows:
tcp        0      0 <IP_ADDRESS>:8089          <IP_ADDRESS>:*               LISTEN      10341/influxd
Can you give hints how to debug this ?

The Backup was created on a machine with InfluxDB 1.5.1, ubuntu 16.04 without the -portable option. So if I understand correctly, I have a backup in legacy format.
So if I remove -portable then I get normal error messages:
influxd restore -datadir /var/lib/influxdb/data -db telegraf -newdb restore_telegraf -host '<IP_ADDRESS>:8089' -rp autogen /root/IDB_Backups/telegraf/
2018/04/10 12:58:47 Restoring offline from backup /root/IDB_Backups/telegraf/restore_telegraf.*
restore: no backup files for /root/IDB_Backups/telegraf/restore_telegraf.* in /root/IDB_Backups/telegraf/

But still I cannot restore the backup due to a new error message. Do I need to rename all the files to restore_telegraf.* ??

So to see what happens if I renamed all the files (except meta.00) with the prefix restore_ so the files have the same name as my new DB I want to create. Afterwards the restore ran smoothly, but still my DB was not visible, so I ran systemctl restart influxdb an get:
influxd[15276]: run: open server: open tsdb store: mkdir /var/lib/influxdb/data/restore_telegraf/_series: permission denied
After chown -R influxdb:influxdb /var/lib/influxdb/data/restore_telegraf/ the service started and opened the shards (I can see in syslog). But in the influx client I cannot the the DB if I type:
> show databases
name: databases
name
----
_internal
telegraf
graphite

I'm lost at the moment ?

@bolek2000 is there a .manifest file in /root/IDB_Backups/telegraf/?

Troubleshooting notes:
Looks like cmd.manifestMeta can be nil here and referenced here.

No .manifest existing. The backup was created per database with -database option. It seems that I can only use the old legacy restore procedure (with data loss) described in the docs. -online also doensn't work. The only thing I didn't explicitly do is restoring only the metastore. But I guess the old meta.00 file will only know the old databases, not the new one I want to create, isn't it ?

So this works for me to use the restored data (with data loss), but I am restoring on a test instance. The backup files have the original names from backup:
# systemctl stop influxdb
# influxd restore -metadir /var/lib/influxdb/meta /root/IDB_Backups/telegraf/
Using metastore snapshot: telegraf/meta.00
# influxd restore -datadir /var/lib/influxdb/data -db telegraf -newdb telegraf -host '<IP_ADDRESS>:8089' -rp autogen /root/IDB_Backups/telegraf/
2018/04/10 14:38:25 Restoring offline from backup /root/IDB_Backups/telegraf/telegraf.*
# chown -R influxdb:influxdb /var/lib/influxdb
# systemctl start influxdb

So I am leaving the panic message for you to fix. Thanks so far....

@bolek2000   This bug is fixed and will go out on the next release: #9634   but there is a workaround for 1.5.1:
This issue occurs because you did not use -portable when you create the backup, and so the 'legacy' file format was generated.  You can still use the new features in restore!  Instead of   -portable,   try  -online,   which behaves the same as -portable but consumes the old legacy format including the meta.00 and related backup files.
Even after the bugfix, we will avoid the panic but instead the restore would have printed an error message and exited without restoring anything.  Your final solution then will be to use -online  if you have generated the legacy backup format.


Adding new gun games

+1 C64

All good to be merged.
In summary :
New games added to the gungames.xml with precalibration (for Wii) and mamenames.xml (Action Max and HD version of ALG)


Reforging table giving a different reforge than expected

Hello, for some reason when I use the reforging table I get a different (sometimes similar) reforge than anticipated

What version are you using

Closing for lack of information.


Tagged commit for 0.2.14 does not match artifacts

I'm not sure if there's anything we can do here (now that it's happened), but our release tooling tagged https://github.com/astral-sh/uv/commit/f07308823e877690a00141441b07fd0f7dfe9805 instead of https://github.com/astral-sh/uv/commit/e0ad649c7449b7f54c0053e409ac6e7bf18a6f68 during the re-run of the failed 0.2.14 release.
The artifacts were all built for the proper commit, but the git tag points to an incorrect source.
See #4432 for details on the original problem.

We're releasing 0.2.15 now to minimize the effect of this.


Docker security

Think about dockers' security. Retrieved from.To issue make notes.

trivy
Targets (what Trivy can scan):

Container Image
Filesystem
Git Repository (remote)
Virtual Machine Image
Kubernetes
AWS

Scanners (what Trivy can find there):

OS packages and software dependencies in use (SBOM)
Known vulnerabilities (CVEs)
IaC issues and misconfigurations
Sensitive information and secrets
Software licenses

grype

Scan the contents of a container image or filesystem to find known vulnerabilities.
Find vulnerabilities for major operating system packages:

Alpine
Amazon Linux
BusyBox
CentOS
Debian
Distroless
Oracle Linux
Red Hat (RHEL)
Ubuntu

Find vulnerabilities for language-specific packages:

Ruby (Gems)
Java (JAR, WAR, EAR, JPI, HPI)
JavaScript (NPM, Yarn)
Python (Egg, Wheel, Poetry, requirements.txt/setup.py files)
Dotnet (deps.json)
Golang (go.mod)
PHP (Composer)
Rust (Cargo)
Supports Docker, OCI and Singularity image formats.

Grype's using database

Alpine Linux SecDB: https://secdb.alpinelinux.org/
Amazon Linux ALAS: https://alas.aws.amazon.com/AL2/alas.rss
RedHat RHSAs: https://www.redhat.com/security/data/oval/
Debian Linux CVE Tracker: https://security-tracker.debian.org/tracker/data/json
Github GHSAs: https://github.com/advisories
National Vulnerability Database (NVD): https://nvd.nist.gov/vuln/data-feeds
Oracle Linux OVAL: https://linux.oracle.com/security/oval/
RedHat Linux Security Data: https://access.redhat.com/hydra/rest/securitydata/
Suse Linux OVAL: https://ftp.suse.com/pub/projects/security/oval/
Ubuntu Linux Security: https://people.canonical.com/~ubuntu-security/

@safdtgx
lynis
docker-bench-security
docker-bench-test
dockle


[End of 2024] [Grants] Curation Workflow Tracking

NCI funds new grants throughout the year. We typically curate and add these two the CCKP twice per years, or wait until there is a big batch to add since this process is not trivial.
Ideally by the end of Q4 2024, we need to add the following 11 grants to our repertoire of infrastructure, curation, and listing on the CCKP:

MetNet (U01 CA284085, U01 CA283749, U01 CA289564, U01 CA293470)
TEC (R37 CA279722, R01 CA290115, R01 CA279948, R01 CA281216, R01 CA292382)
PS-ON (U01 CA290442, U01 CA293853)

Information on all of these grants is available in https://reporter.nih.gov/ and can be searched by the grant numbers listed above. Notably, none of these are U54 grants, so there is no need to curate sub-projects (typically done with the ProjectView manifest) for these grants.
Historically, we tracked the grant curation process in Jira, with the following steps (please take a look at the last round of grant curation for additional context and historical roles). We have an opportunity to re-visit this process to 1) consider opportunities for streamlined grant metadata extraction and infrastructure setup automation 2) formalize an updated grant curation SOP in the context of our latest infrastructure and required steps. I understand that @Bankso and @aditya-nath-sage may have some ideas here.

[x] Curate list of grants to add (above)
[ ] Populate GrantView manifest with grants to be added and identify new terms to be added to the data model
[ ] Assign themes to new MC2 grants, ideally based on existing themes
[ ] Update data model with new terms: new themes, grant numbers, etc
[ ] Make further updates to GrantView manifest, as needed (following data model updates)
[ ] Create Synapse projects for new MC2 grants with default wiki info and resource sub-folders
[ ] GrantView manifest validated and uploaded + syncing scripts updated as needed
[ ] Sync newly ingressed grant data to Portal - Grants Merged table
[ ] Validate updated grant information on portal
[ ] Push and confirm theme graphs on CCKP homepage have been updated (there is an action for Github for this that Verena or Ashley have controlled in the past)
[ ] Ensure scopes are updated for new grants: DCA, UNION tables, etc.
[ ] Ensure pubmed crawler is successfully picking up resources for new grants

By the end of this round, I am hoping we can develop an updated SOP for grant curation.

Have been unable to work on grants curation this sprint


feat(component): Visibility support

Problem to solve
Often a component needs to stay on the tree, but just be invisible for a while.
The suggested method (?) is to remove them from the tree. Adding and removing them has several problems:

It's an async operation, and a remove followed by an immediate add again can cause issues
Lifecycle events are fired, when all you want to do is not render the component

Proposal
Mixin A change (and visibilty flag) that adds visibility to components while still on the tree.
More information
With suggestions from maintainers on how this could best be implemented, I'd be willing to contribute it.

Hmm, how were you planning to do this with a mixin? I'm imagining that it would use renderTree, but it wouldn't be able to cancel out the renderTree from the component?

I hadn't really looked in to it yet. Just seemed to be a good first suggestion :)
Do you know if there is any reason it wasn't implemented?

Well due to the reason that I don't think it is possible to do it with a mixin. 😅
But you can try!

Forget I said mixin 🤣
Sounds like it should be an addition to a base class at a lower level?

Well, this seems to work just fine.
Any reservations before I continue and do further testing, update docs etc?
mixin Visible on Component {
  bool visible = true;

  @override
  void renderTree(Canvas canvas) {
    if (visible) {
      super.renderTree(canvas);
    }
  }
}

Right, it will work in the cases where the component that you use the mixin on hasn't overridden renderTree (then it will call both the mixin and the local override, no matter the value of visible is), but I think that is such a rare use-case that it can be accepted, just make sure to add a note in the docs about it.
I would name the mixin Visibility and the variable isVisible, other than that it looks good!

Ah yes, I see what you mean.  As well as maybe being rare - in that case the author can manually add a check for isVisible to their custom renderTree method, since they are authoring the component.
Agree with your suggestions 👍

The name 'Visibility' is defined in the libraries
- 'package:flame/src/components/mixins/visibility.dart (via package:flame/components.dart)'
- 'package:flutter/src/widgets/visibility.dart'.

Try using 'as prefix' for one of the import directives, or hiding the name from all but one of the imports

@spydon do you prefer:

Change the name of my mixin (e.g. HasVisibility) ?
Add documentation to tell the developer to hide the other imports (i.e. hide flutter's widget visibility package) ?

Ah, I don't think many try to import widget imports in their components, but let's go with HasVisibility anyways.

I don't mind changing it back to Visibility if that is preferred. I prefer it myself :grin:


Can't debug Clang build on Windows anymore

Tested versions
v4.4.dev.custom_build [cf038deb1]
System information
Godot v4.4.dev (cf038deb1) - Windows 10.0.19045 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>36) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 threads)
Issue description
Can't debug clang build on Windows compiled with scons use_mingw=yes use_llvm=yes dev_build=yes. Will not allow debug anymore with lldb-dap.
This is caused by https://github.com/godotengine/godot/pull/100207 cc @bruvzg
I guess if platform=windows but use_llvm=yes we should still use -gdwarf-4 or something like this ? Or am I missing a package ?
Steps to reproduce
N/A
Minimal reproduction project (MRP)
N/A

I guess if use_llvm=yes we should still use -gdwarf-4 or something like this ?

No, it was changed to dwarf-5 for libbacktrace, it does not matter which compiler was used.
clang should default to dwarf-5 since llvm-14, it's possible you are using old version of lldb.

I use https://packages.msys2.org/groups/mingw-w64-clang-x86_64-toolchain which provided lldb version 19.1.4-1
I tried with https://github.com/mstorsjo/llvm-mingw and that was the same.
Using drawrf-4 it make it work again, what should I do then ?

It may be because of lldb-dap https://github.com/mfussenegger/nvim-dap/issues/186#issuecomment-852382434

Tested various configs:

drawf-4 symbols produces by gcc:

Doesn't work with libbacktrace.

drawf-5 symbols produces by gcc:

Work in gdb:

Kinda work in lldb, but seems to have some issues, it's spamming a lot of Failed to extract range list table at offset error and does not show source lines (function names are shown).
Work with libbacktrace.

drawf-5 symbols produced by clang:

Doesn't work in gdb.
Work in the same half-broken way in lldb.
Doesn't work with libbacktrace.

drawf-4 symbols produced by clang:

Work in gdb.
Work in lldb, no error spam lines are show correctly:

Work with libbacktrace.

So we should switch clang builds back to drawf-4.

Thank you for your tests!

Kinda work in lldb, but seems to have some issues, it's spamming a lot of Failed to extract range list table at offset error and does not show source lines (function names are shown).

Sounds like this from the GCC 11 release notes:

To take full advantage of DWARF version 5 GCC needs to be built against binutils version 2.35.2 or higher. When GCC is built against earlier versions of binutils GCC will still emit DWARF version 5 for most debuginfo data, but will generate version 4 debug line tables (even when explicitly given -gdwarf-5).

There must be a mismatch between the debuginfo data and the debug line tables versions.
Looking at libbacktrace's dwarf.c is seems to have code to support earlier dwarf versions than 5. Maybe we could revert back to dwarf-4 for all platforms and just find how to use libbacktrace to process dwarf-4 data explicitly?


Actually/pdoc 19

@hkenney r?

FYI this branches off PR #35

Just noting: We'll need to rebase this when #35 is in


Improve MTL map

change to rate per 100000
use 7-day rolling average (see https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.rolling.html), maybe add it to data_mtl.csv for both per 100k and new cases
use a discrete color scale for the 7-day average per 100k of each borough (based on the ranges here maybe: https://globalhealth.harvard.edu/key-metrics-for-covid-suppression-researchers-and-public-health-experts-unite-to-bring-clarity-to-key-metrics-guiding-coronavirus-response/) (@jeremymoreau: do you know how to do such a discrete color scale in dash?)
if possible, could add some more information to the tooltip on hover (such as, cases per 100k, new cases)

There are actually two ways for the 7-day incidence/average.

7-day rolling average is the average of cases per day
7-day incidence is the sum of cases in the last 7 days

It is basically the same (factor 7 difference) and there seems to be no consistent use of either. I am inclined to use the 7-day incidence.
I played around with pandas for a bit and I think I managed to create a dataframe with a multiindex so that for each borough there can be several metrics (total cases, new cases and 7-day rolling sum/avg) all calculated from the cases.csv.

I was just testing out something similar actually, although just reformatting the data provided in all the source data_mtl_municipal.csv into a more usable format. I didn't calculate 7-day incidence though, so maybe your solution is better (since I could only include data since Santé Montréal started reporting 14-day incidence). It does add all the information on mortality as well however, so that might be interesting to integrate?
See the function here: https://github.com/jeremymoreau/covid19mtl/blob/49-improve-mtl-map/app/mapdata.py
And example output df:  https://github.com/jeremymoreau/covid19mtl/blob/49-improve-mtl-map/app/data/processed/data_mtl_map.csv
I agree that reporting case incidence is the main thing of interest. All the other data, could be shown in the hover tooltip (or we could add some buttons to switch between case incidence, mortality incidence, etc. if we're feeling fancy).
I also really like the idea of adding a discrete colourmap using the guidelines you posted above. It should be fairly easy to create a custom colourmap based on the suggested values with Plotly: https://plotly.com/python/discrete-color/

I agree that the mortality could be interesting for the hover tooltip among the other data. Although I am not sure how valuable mortality is per borough. The test positivity rate would be interesting too but those numbers I have so far only seen in the Montreal situation PDF document.
For the mortality I would suggest to go through all past files and use the Nombre de décès column (since their CSV shows < 5 for new deaths). That allows to calculate the actual new deaths per day.
Interesting to see how you created the MultiIndex. I struggled with that but found a way that works I think. I am using the total cases per day per bourough and calculate the new cases, 7-day incidence and 7-day incidence per 100k. I transposed the current cases.csv. It might be more of a personal preference but I find it easier to see the changes in the diff when only new rows are added.
The code is here: https://github.com/jeremymoreau/covid19mtl/blob/49-mtl-boroughs/refreshdata.py#L444-L481
The resulting CSV is here: https://github.com/jeremymoreau/covid19mtl/blob/49-mtl-boroughs/app/data/processed/data_mtl_boroughs.csv

The plotly express choropleth_mapbox does not have a colorscale argument. I think that's what's required to create a mapping from value to color. Does anyone know how to create the same map with plotly Choroplethmapbox directly?

I think this is actually doable with plotly express, we just need to add a column to the pandas df with categorical risk levels (i.e. green, yellow, orange, red) based on the cases per 100k, as per the reference you posted above. Then add a discrete colourscale like this:
px.choropleth_mapbox(
    cases_per1000_long, geojson=mtl_geojson,
    locations='borough',
    featureidkey='properties.borough',
    animation_frame='date', animation_group='borough',
    mapbox_style='carto-positron',
    zoom=9, center={'lat': 45.55, 'lon': -73.75},
    labels=labels['montreal_map_colourbar_labels'],

    # Replace color='cases_per_1000' with the following
    color='risk_level',  # Add risk_level column to pandas df: <1, 1-9, 10-24, >=25 per 100k
    # took the colours from: https://globalepidemics.org/key-metrics-for-covid-suppression/
    color_discrete_map={'green': '#7ea47c', 'yellow': '#ecd93b', 'orange': '#dfae5a', 'red': '#c83a44' },
)

I can work on this if you'd like since I'm fairly familiar with Plotly.

Ah, that's it! Thanks! I also found this article where the same approach is used.
I'll give it a shot, should be able to pull it off with that hint.
About the risk level. Right now I used the 7-day rolling sum (not average) which would allow to do the categorization a bit more fine-grained. This (7-day rolling sum per 100k) is also what Sante Montreal uses. I've known it from Germany (see this map, click on the legend icon to see the legend with the ranges) but essentially whatever is most used here we should use. Do you have any opinion on it?

Also for resampling I came across pandas resample method which I will try and see if it makes it easier to reduce the dataset.

I'm fine with either the 7-day rolling average or rolling sum, whichever you think is best. The link you shared (https://globalhealth.harvard.edu/key-metrics-for-covid-suppression-researchers-and-public-health-experts-unite-to-bring-clarity-to-key-metrics-guiding-coronavirus-response/) bases its risk level categories on daily new cases per 100k (and they report 7-day moving averages on their map) though, so if you are going to use the 7-day rolling sum I guess you will need to multiply the brackets by 7? I'd be in favour of using the same (or equivalent) brackets.

I'm fine with either the 7-day rolling average or rolling sum, whichever you think is best. The link you shared (https://globalhealth.harvard.edu/key-metrics-for-covid-suppression-researchers-and-public-health-experts-unite-to-bring-clarity-to-key-metrics-guiding-coronavirus-response/) bases its risk level categories on daily new cases per 100k (and they report 7-day moving averages on their map) though, so if you are going to use the 7-day rolling sum I guess you will need to multiply the brackets by 7? I'd be in favour of using the same (or equivalent) brackets.

Writing this down for future reference. I managed to downsample by converting the date to a DateIndex via df.resample('7d'). It starts on the first date (here 2020-03-29). Any date that has no data will result in an NaN row. There's only a few. I tried to fill those rows with the last known date as follows:
df.asfreq('7d', method='ffill') but if there is a large gap (such as in the summer) there will be duplicate rows. Also the index should be copied to a column before to know the actual date afterwards (the index will get the expected date value). The duplicates can be dealt with withdf[~df.index.duplicated(keep='first')]. For now I won't do it since it seems not worth it.

Writing this down for future reference. I managed to downsample by converting the date to a DateIndex via df.resample('7d'). It starts on the first date (here 2020-03-29). Any date that has no data will result in an NaN row. There's only a few. I tried to fill those rows with the last known date as follows:
df.asfreq('7d', method='ffill') but if there is a large gap (such as in the summer) there will be duplicate rows. Also the index should be copied to a column before to know the actual date afterwards (the index will get the expected date value). The duplicates can be dealt with withdf[~df.index.duplicated(keep='first')]. For now I won't do it since it seems not worth it.

Sometimes, due to adjustments in case numbers, the 7-day incidence is negative. I would just set those to 7.

Sometimes, due to adjustments in case numbers, the 7-day incidence is negative. I would just set those to 7.

I'm pretty close but I'm facing an issue where some of the boroughs remain uncoloured. Would you be able to have a look? It's branch https://github.com/jeremymoreau/covid19mtl/tree/49-mtl-boroughs
Another thing I haven't figured out yet is how to keep the legend always with all possible labels/values. It seems to change based on the current frame.

I'm pretty close but I'm facing an issue where some of the boroughs remain uncoloured. Would you be able to have a look? It's branch https://github.com/jeremymoreau/covid19mtl/tree/49-mtl-boroughs
Another thing I haven't figured out yet is how to keep the legend always with all possible labels/values. It seems to change based on the current frame.

Fixed in 2883a6d2f1c1d0caaee80fc6a9ef5a0ae5d15d60. Kinda tricky, but had to add all the categories to each date (even if there were no boroughs with that category on a given date). Found solution here: https://medium.com/@mahshadn/animated-choropleth-map-with-discrete-colors-using-python-and-plotly-styling-5e208e5b6bf8
Empty categories look like this:

Map looks awesome btw!! Thanks for making this, it's way better than before:

I added a couple more colours within the "orange" and "red" risk level categories to make a gradient (I think this is what you had in mind from the beginning right?).
Things we still need to fix:

Setting the last frame as default is broken for some reason, not sure why (commented it out for now).
Page loading times are bad, I downsampled the map shapefile a lot (94 kb →  14kb), but it's still slow. I think the ideal would be to "lazy-load" the map (and other figures) after page load, but I'm not sure how to do that. If we could load the map last without blocking the rest of the page from rendering it would help a lot.

Perhaps useful for reference (haven't looked into it much yet though):

https://dash.plotly.com/dash-core-components/loading
https://dash.plotly.com/loading-states

Fixed in 2883a6d2f1c1d0caaee80fc6a9ef5a0ae5d15d60. Kinda tricky, but had to add all the categories to each date (even if there were no boroughs with that category on a given date). Found solution here: https://medium.com/@mahshadn/animated-choropleth-map-with-discrete-colors-using-python-and-plotly-styling-5e208e5b6bf8
Empty categories look like this:

Map looks awesome btw!! Thanks for making this, it's way better than before:

I added a couple more colours within the "orange" and "red" risk level categories to make a gradient (I think this is what you had in mind from the beginning right?).
Things we still need to fix:

Setting the last frame as default is broken for some reason, not sure why (commented it out for now).
Page loading times are bad, I downsampled the map shapefile a lot (94 kb →  14kb), but it's still slow. I think the ideal would be to "lazy-load" the map (and other figures) after page load, but I'm not sure how to do that. If we could load the map last without blocking the rest of the page from rendering it would help a lot.

Perhaps useful for reference (haven't looked into it much yet though):

https://dash.plotly.com/dash-core-components/loading
https://dash.plotly.com/loading-states

Awesome! Good catch. Thanks a lot.

I added a couple more colours within the "orange" and "red" risk level categories to make a gradient (I think this is what you had in mind from the beginning right?).

Yes, thanks! I did change the order though to go from light to dark (worse) and reordered the legend in the opposite way.
I also changed the hover data to show new cases/total cases/7-day incidence/7-day incidence per 100k. Right now this is not done with a hover template. I'd prefer to have : as a separator like it was but haven't tried to supply a custom hover template with all the data yet. It might be accessible through the customdata variable.

Setting the last frame as default is broken for some reason, not sure why (commented it out for now).

I think it's because z is something else now. I tried passing something else into update_traces and got an error which showed the possible values, one of them is:
visible
            Determines whether or not this trace is visible. If
            "legendonly", the trace is not drawn, but can appear as
            a legend item (provided that the legend itself is
            visible).

I haven't figured out yet how specify the selector argument (update_traces(visible=True, selector=?).

Page loading times are bad, I downsampled the map shapefile a lot (94 kb → 14kb), but it's still slow. I think the ideal would be to "lazy-load" the map (and other figures) after page load, but I'm not sure how to do that. If we could load the map last without blocking the rest of the page from rendering it would help a lot.

Hm. With showing a frame for every week the df increased from ~400 to 1188 rows. So one way would be to change the frequency. However, I haven't measured it, but app start seems slow, page load the same/similar (to me). At least with debug=False.
I did notice that most Dash examples make use of these callbacks (@app.callback). Is this not required here? Could that be a factor?

Awesome! Good catch. Thanks a lot.

I added a couple more colours within the "orange" and "red" risk level categories to make a gradient (I think this is what you had in mind from the beginning right?).

Yes, thanks! I did change the order though to go from light to dark (worse) and reordered the legend in the opposite way.
I also changed the hover data to show new cases/total cases/7-day incidence/7-day incidence per 100k. Right now this is not done with a hover template. I'd prefer to have : as a separator like it was but haven't tried to supply a custom hover template with all the data yet. It might be accessible through the customdata variable.

Setting the last frame as default is broken for some reason, not sure why (commented it out for now).

I think it's because z is something else now. I tried passing something else into update_traces and got an error which showed the possible values, one of them is:
visible
            Determines whether or not this trace is visible. If
            "legendonly", the trace is not drawn, but can appear as
            a legend item (provided that the legend itself is
            visible).

I haven't figured out yet how specify the selector argument (update_traces(visible=True, selector=?).

Page loading times are bad, I downsampled the map shapefile a lot (94 kb → 14kb), but it's still slow. I think the ideal would be to "lazy-load" the map (and other figures) after page load, but I'm not sure how to do that. If we could load the map last without blocking the rest of the page from rendering it would help a lot.

Hm. With showing a frame for every week the df increased from ~400 to 1188 rows. So one way would be to change the frequency. However, I haven't measured it, but app start seems slow, page load the same/similar (to me). At least with debug=False.
I did notice that most Dash examples make use of these callbacks (@app.callback). Is this not required here? Could that be a factor?

Ah, is it possible that with the callback it would be possible to react to the slider (as input) and therefore only provide one animation frame at a time?!

Ah, is it possible that with the callback it would be possible to react to the slider (as input) and therefore only provide one animation frame at a time?!

Sounds good!
For the hovertemplate I had something like this with the previous map:
# Update hoverlabel for all frames
mtlmap_fig.update_traces({
    'hovertemplate': labels['montreal_map_hovertemplate']
})
for frame in mtlmap_fig.frames:
    frame['data'][0]['hovertemplate'] = labels['montreal_map_hovertemplate']

# labels dict from app_en.py
labels = {
'montreal_map_hovertemplate': '
Borough/City: %{location}
Cases per 1000 population: %{z}',
}

Although, you're right z has changed vs. with the continuous colourscale, so some things will need to be different (for the hovertemplate and setting the default frame). I could post the question about setting the default frame on the Plotly forum once this is live. This is where I got that solution previously: https://community.plotly.com/t/defining-default-starting-frame-with-plotly-express-animation/38636
I also tried it again today and it is faster than it was when I tested it last, not sure why. The Dash callbacks are used to interactively change things on the page after it loads (e.g. change what data would be displayed on the map when you click a button), but we aren't using any of them currently since all the figures are "static". https://dash.plotly.com/basic-callbacks
I think we can merge this for now (before the new data update tmr), then work on fixing the smaller things later? I really like this new map!

Sounds good!
For the hovertemplate I had something like this with the previous map:
# Update hoverlabel for all frames
mtlmap_fig.update_traces({
    'hovertemplate': labels['montreal_map_hovertemplate']
})
for frame in mtlmap_fig.frames:
    frame['data'][0]['hovertemplate'] = labels['montreal_map_hovertemplate']

# labels dict from app_en.py
labels = {
'montreal_map_hovertemplate': '
Borough/City: %{location}
Cases per 1000 population: %{z}',
}

Although, you're right z has changed vs. with the continuous colourscale, so some things will need to be different (for the hovertemplate and setting the default frame). I could post the question about setting the default frame on the Plotly forum once this is live. This is where I got that solution previously: https://community.plotly.com/t/defining-default-starting-frame-with-plotly-express-animation/38636
I also tried it again today and it is faster than it was when I tested it last, not sure why. The Dash callbacks are used to interactively change things on the page after it loads (e.g. change what data would be displayed on the map when you click a button), but we aren't using any of them currently since all the figures are "static". https://dash.plotly.com/basic-callbacks
I think we can merge this for now (before the new data update tmr), then work on fixing the smaller things later? I really like this new map!

I actually found your post during my research for a solution to this problem. Yes, please post this question there once it is live.
You might have tried it when the df was badly unstacked and had over 5000 rows. I got it down to 1188 rows although that will increase over time with every week.
Once thing that is happening though is that there is some sort of flickering when you slide through the dates. Might be due to the increased number of frames?
I have to add some label translations and then it's good to go. Thanks for your help!

I actually found your post during my research for a solution to this problem. Yes, please post this question there once it is live.
You might have tried it when the df was badly unstacked and had over 5000 rows. I got it down to 1188 rows although that will increase over time with every week.
Once thing that is happening though is that there is some sort of flickering when you slide through the dates. Might be due to the increased number of frames?
I have to add some label translations and then it's good to go. Thanks for your help!

Unfortunately, setting the hovertemplate as it was done also does not work. It works for the first frame (using update_traces) but not for the remaining frames. So it is still commented out.

Unfortunately, setting the hovertemplate as it was done also does not work. It works for the first frame (using update_traces) but not for the remaining frames. So it is still commented out.

Ok, I will post the question tomorrow. I can ask about the hovertemplate at the same time.
I'm not sure how we can fix the flicker in the legend (seems to only happen when moving the slider quickly, not when pressing play or clicking a specific point on the slider). Maybe there is a way to not update the legend when changing frames (since it's always the same)? I did however fix the map "resize flicker" by moving the legend on top of the map (also gives the map more space, especially on mobile). Seems like Plotly just refreshes a bit slowly between frames.

Ok, I will post the question tomorrow. I can ask about the hovertemplate at the same time.
I'm not sure how we can fix the flicker in the legend (seems to only happen when moving the slider quickly, not when pressing play or clicking a specific point on the slider). Maybe there is a way to not update the legend when changing frames (since it's always the same)? I did however fix the map "resize flicker" by moving the legend on top of the map (also gives the map more space, especially on mobile). Seems like Plotly just refreshes a bit slowly between frames.


docs: updated readme

Summary of changes:

Updated README to be inline with other charms. This REAME will be pulled into Charmhub.

@beliaev-maksim New PR for README.


Factory uses bytes4 to track instanceTypes, this is unjustifiably restrictive

The Factory contract wants to track types of contracts. It does this using a bytes4 type. It seems this is inspired from the ERC-165 standard.
The baseline choice should be using a full 32 byte hash. The bytes4 costs more gas to store, retrieve and compare (EVM stores a whole word, Solidity handles truncation) also it has less collision resistance.
As an author of ERC-165 I think bytes4 is a bad choice here.
Recommendation: use a full word hash
References: Definition https://github.com/erasureprotocol/erasure-protocol/blob/4a3d98ce023a264a9f3c7ba62ef77a9207bba5fe/contracts/modules/Factory.sol#L20

Change would require redeployment of registries, added for v2


Remove redundant variables

Remove some redundant variables.

@thangchung : Please review it. Since I wonder about the enrichClient whether it plays a real role in each method without using it in other places.

@toanvo Hi anh Toan. Yeah, that's the redundant codes that I used for writing the log but forgot to remove it. Thank you anh.


[ACR] az acr create, az acr update: add metadata-search argument

Related command

az acr create, az acr update
Description

Added a new parameter "metadata-search" to the az acr create/update commands to support enablement of the metadata-search feature.
Added unit tests to the new changes.
Update the default acr mgmt client python SDK to the latest one so that "metadata-search" property is available in the model file.
Update the test recordings after the SDK upgrade.

Testing Guide

Added two unit tests. You could test by running this on your azdev environment.

azdev test test_acr_create_with_metadata_search_disabled --live --discover
azdev test test_acr_create_with_metadata_search_enabled --live --discover

History Notes

[ACR] az acr create, az acr update: add metadata-search argument

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

ACR

The CI failure: test_acr_agentpool seems not to be related to our module. I was able to rerun the commands in the test manually and everything passes through. It's more likely to be an issue with the test framework .

The CI failure: test_acr_agentpool seems not to be related to our module. I was able to rerun the commands in the test manually and everything passes through. It's more likely to be an issue with the test framework . @yonzhan Does the CI error look familiar to you? Thanks!

Hi @raymondluo1,
Since you upgraded the API version, and these tests all used the original version.
Therefore, the test results show that the version information is inconsistent.

Hi @wangzelin007 , thanks for the detailed explanation. It seems that not only our service's unit tests got impacted. For services that are using the ACR sdk in  unit tests, they are impacted as well. I will try to record those components's unit tests as well and include them in my PR.

@zhoxing-ms @wangzelin007 what's the general recommendation for Switch params? I added a new param to our cli, which is used to enable/disable a feature. The post request would parse it as an Enum as either Enabled/Disabled. For now, I make it as:
--metadata-search Enabled/Disabled. Is it a good practice? Another pattern I saw is using it like a boolean flag, such as: --metadata-search-enabled.

Please fix conflicting files

@yonzhan Sorry for the late update, I was oncall last week. The merge conflict has been fixed.

@raymondluo1 Could you please resolve these CI issues?

@zhoxing-ms  I changed the params name as suggested, but I am getting this error from the CLI about param name too long:
FAIL - HIGH severity: option_length_too_long
Parameter: acr create, metadata_search_enabled - The lengths of all options ['--metadata-search-enabled'] are longer than threshold 22. Argument metadata_search_enabled must have a short abbreviation.

Please add a short alias for --metadata-search-enabled or configure the file linter_exclusions.yml

@raymondluo1 Please resolve these CI issues first, thanks

@raymondluo1 Could you please resolve these CI issues and conflicts?

@zhoxing-ms I have a couple of questions about some weird behavior I am seeing while fixing the tests.

The failing test ERROR: 'test_acr_artifact_streaming' exists twice in the 'acr' module. Please rename one or both and re-run --discover. However, I checked the module and I didn't see another test_acr_artifact_streaming. I changed the test name and the test could pass now. But I am wondering why would it say that the test exists twice in the 'acr' module?
There are some test failures from other service team. I was trying to use the bump version pipeline, but it's not working correctly? Could you help me check what's wrong? https://dev.azure.com/azclitools/internal/_build/results?buildId=125694&view=results

@zhoxing-ms I have a couple of questions about some weird behavior I am seeing while fixing the tests.

The failing test ERROR: 'test_acr_artifact_streaming' exists twice in the 'acr' module. Please rename one or both and re-run --discover. However, I checked the module and I didn't see another test_acr_artifact_streaming. I changed the test name and the test could pass now. But I am wondering why would it say that the test exists twice in the 'acr' module?
There are some test failures from other service team. I was trying to use the bump version pipeline, but it's not working correctly? Could you help me check what's wrong? https://dev.azure.com/azclitools/internal/_build/results?buildId=125694&view=results

The test appears to have the same name as the test file (test_acr_artifact_streaming.py)
The error is related to authentication, we're working on it and will back to you later.

@

@zhoxing-ms I have a couple of questions about some weird behavior I am seeing while fixing the tests.

The failing test ERROR: 'test_acr_artifact_streaming' exists twice in the 'acr' module. Please rename one or both and re-run --discover. However, I checked the module and I didn't see another test_acr_artifact_streaming. I changed the test name and the test could pass now. But I am wondering why would it say that the test exists twice in the 'acr' module?
There are some test failures from other service team. I was trying to use the bump version pipeline, but it's not working correctly? Could you help me check what's wrong? https://dev.azure.com/azclitools/internal/_build/results?buildId=125694&view=results

The test appears to have the same name as the test file (test_acr_artifact_streaming.py)
The error is related to authentication, we're working on it and will back to you later.

Hi, thanks for pointing out the test name issue. For the pipeline, do you know when would it be fixed? Thanks!

@

@zhoxing-ms I have a couple of questions about some weird behavior I am seeing while fixing the tests.

The failing test ERROR: 'test_acr_artifact_streaming' exists twice in the 'acr' module. Please rename one or both and re-run --discover. However, I checked the module and I didn't see another test_acr_artifact_streaming. I changed the test name and the test could pass now. But I am wondering why would it say that the test exists twice in the 'acr' module?
There are some test failures from other service team. I was trying to use the bump version pipeline, but it's not working correctly? Could you help me check what's wrong? https://dev.azure.com/azclitools/internal/_build/results?buildId=125694&view=results

The test appears to have the same name as the test file (test_acr_artifact_streaming.py)
The error is related to authentication, we're working on it and will back to you later.

Hi, thanks for pointing out the test name issue. For the pipeline, do you know when would it be fixed? Thanks!

Hi @raymondluo1,
you can ping @evelyn-ys for the details of bump version pipeline.

The regression test pipeline will be fixed next week.

@yanzhudd @zhoxing-ms I am starting to see some error from the test framework for the test test_acr_artifact_streaming .I am getting similar failure as this Open Issue:L https://github.com/Azure/azure-cli/issues/28283
E               vcr.errors.CannotOverwriteExistingCassetteException: Can't overwrite existing cassette ('d:\repos\azure-cli\src\azure-cli\azure\cli\command_modules\acr\tests\latest\recordings\test_acr_artifact_streaming.yaml') in your current record mode ('once').
E               No match for the request (<Request (POST) https://cliregoxvpwrdu2hd2qx.azurecr.io/oauth2/exchange>) was found.
E               Found 10 similar requests with 1 different matcher(s) :
E
E               1 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               2 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               3 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               4 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               5 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               6 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               7 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               8 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               9 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
E
E               10 - (<Request (POST) https://clireg000002.azurecr.io/oauth2/exchange>).
E               Matchers succeeded : ['method', 'scheme', 'port', 'path', '_custom_request_query_matcher']
E               Matchers failed :
E               host - assertion failure :
E               cliregoxvpwrdu2hd2qx.azurecr.io != clireg000002.azurecr.io
env\lib\site-packages\vcr\stubs_init_.py:263: CannotOverwriteExistingCassetteException

@evelyn-ys The CLI pipeline is not functioning correctly. I tried both method a and method b. For method a, the PR generated doesn't contain the new recording generated. For method b, the PR creation failed. https://dev.azure.com/azclitools/internal/_build/results?buildId=129341&view=results
This is the PR generated by the CLI pipeline, which doesn't contain the new recordings at all.
https://github.com/Azure/azure-cli/pull/28332

@raymondluo1 If the regression pipeline doesn't generate new recordings for some failed tests, then it means our pipeline was not able to rerun the tests successfully. It could be permission issue or using some fixed resources in the failed tests. You need to rerun these tests manually

@evelyn-ys @yanzhudd  This test test_acr_deployment_function_app failed even in the dev branch when I ran it locally. How could I address the issue? It doesn't belong to our service.

@raymondluo1 Could you please resolve these CI issues and conflicts?

Since the pipeline was broken, I manually resolved all the CI issues. The cred scan failed due to failure to download the credscan package.

@evelyn-ys @zhoxing-ms @yanzhudd  I saw that the all the Azure.azure-cli pipeline runs are failing because of the failure to install the cred scan, do you know when would this be fixed? Thanks.

@evelyn-ys @zhoxing-ms @yanzhudd I saw that the all the Azure.azure-cli pipeline runs are failing because of the failure to install the cred scan, do you know when would this be fixed? Thanks.

We have sent an email to Microsoft Security Code Analysis Support for help, thank you for your reminder.

/azp run

[heart]         Raymond Luo reacted to your message:

From: Xing Zhou @.>
Sent: Tuesday, February 27, 2024 9:10:37 AM
To: Azure/azure-cli @.>
Cc: Raymond Luo @.>; Mention @.>
Subject: Re: [Azure/azure-cli] [ACR] az acr create/update: Add new argument --allow-metadata-search to enable the metadata-search feature for the registry (PR #28082)
Merged #28082https://github.com/Azure/azure-cli/pull/28082 into dev.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/pull/28082#event-11933125878, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZC7DDEBOC4B5XQJHOTUIK3YVWPI3AVCNFSM6AAAAABA7FRPCWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEZTGMJSGU4DOOA.
You are receiving this because you were mentioned.Message ID: @.***>


how to override control button style?

You can set control-btn to false, use prev() and next() methods on slide instance(get ref from slide component) to customize your control button.

I mean i want to use stock button and change some style like gradient bg.
Now i can change it inside my component style using !important tag


Remove FormObject.cs and FormObjectCollection.cs

PR Summary
Update: reverted in https://github.com/PowerShell/PowerShell/pull/19387
Remove dead code:

FormObject.cs
FormObjectCollaction.cs

PR Context
Discussed with @iSazonov in #19359

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@iSazonov and @CarloToso, FormObject and FormObjectCollaction are public types, and thus it's possible to call Invoke-WebRequest -Body with a FormObject instance, isn't it? This change looks like a regression.

@daxian-dbw Thanks for pointer this! I missed that fact. @CarloToso Please revert of the commit.
Although this class is useless I guess since there is an option for IDIctionary afterwards.
Maybe we should think about removing this class and mark it now as obsolete? @daxian-dbw What do you think?

@CarloToso Please revert the commit.

I don't have a strong opinion. I guess we should just keep it as is, since there is no real reason to remove it.


[Feature request] Unsaved buffers support

1. Request
It would be nice, if users can run command, if they have unsaved buffer in current view.
2. Justification
More than 20 times in a day, I wrote text in unsaved buffers via next methods:

I create new file or new window,
I use GitHub Issue Sublime Text package,
I use GhostText Sublime Text package.

I run AutoHotkey scripts for my unsaved buffers.
3. Settings
Part of my Run App.sublime-commands file:
{
    "caption": "Run Apps: SublimeLinterCheck",
    "command": "runapp",
    "args":{
      "app": "D:\\AutoHotkey\\SublimeLinterCheck.exe"
    }
},

4. Steps to reproduce
I open any unsaved buffer → Ctrl+Shift+P (⌘⇧p for Mac) → Run Apps: SublimeLinterCheck.
5. Expected behavior
Successful run my D:\AutoHotkey\SublimeLinterCheck.exe file.
6. Actual behavior
command: runapp {"app": "D:\\AutoHotkey\\SublimeLinterCheck.exe"}
error: Save the buffer to a local file firstly

Thanks.

You're right. Currently, "run app" doesn't accept buffered text as a "target". There are only three types of target now: directory, file and project.  The fourth target type can be added, "buffer" for example. Code can be added here: https://github.com/liuhewei/run-app-sublime/blob/master/runapp.py#L23
Actually, I'm not using SublimeText now. So I can't handle the request. Sorry for that.


get_test_data_path (and similar) should not be in resources.py

Test code should be entirely separate from non-test code.

There are also a couple of other functions that fit the same bill.

Warnings about this were added in 655f979e43be8d6be2fd1f231ca23643f498350c

Fixed in #215

In 0.3.0.


CORS issue when accessing model-viewer.js  script.

Description
From early morning today, the model viewer section uploaded on our website stopped displaying 3D models. I checked the console for debugging the issue. Turned its a CORS restriction issue. While browsing through the internet on your github forum I have seen that this has happened twice before.

Browser Affected

[x ] Chrome
[x ] Edge
[x ] Firefox
[ ] Helios
[ x] IE
[ ] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

Hi, This issue originally mentioned in post is fixed but now there is a new issue. The poster image is exceeding out of the model viewer frame towards the right side.

@najafsikander Can you post a glitch that repros your issue? In v0.8 we implemented seamless poster transitions, so the toBlob() method with idealAspect=true will give you a screenshot that will work as a poster for any aspect ratio canvas.

@najafsikander in the URL in your screenshot, it looks like you are trying to request<EMAIL_ADDRESS>but we have not released a v1.0.0 yet. That might be related. Try changing that part of the URL to<EMAIL_ADDRESS>

I believe what was left of this issue was closed in #973.


Unable to "nimble install" on osx

Hi,
Is the nimble install method still working?
I am getting the below on osx 10.15:
davids-Mac-Pro-2:mosh dk$ nimble install   Verifying dependencies for<EMAIL_ADDRESS>    Info:  Dependency on<EMAIL_ADDRESS>already satisfied   Verifying dependencies for<EMAIL_ADDRESS>Installing<EMAIL_ADDRESS>  Building mosh/mosh using c backend /Users/dk/mosh/src/convert.nim(1, 11) Warning: imported and not used: 'strformat' [UnusedImport] stack trace: (most recent call last) cligen.nim(370, 25)      dispatchGen cligen.nim(197, 35)      parseHelps /Users/dk/mosh/src/mosh.nim(20, 13) template/generic instantiation of dispatchfrom here /Users/dk/.nimble/pkgs2/cligen-1.5.19-bfe4f99a16ace2164fe40d40866e4951bed51820/cligen.nim(825, 14) template/generic instantiation ofdispatchCffrom here /Users/dk/.nimble/pkgs2/cligen-1.5.19-bfe4f99a16ace2164fe40d40866e4951bed51820/cligen.nim(812, 14) template/generic instantiation ofdispatchGen` from here
/Users/dk/.nimble/pkgs2/cligen-1.5.19-bfe4f99a16ace2164fe40d40866e4951bed51820/cligen.nim(197, 35) Error: cannot get child of node kind: nnkEmpty
Tip: 4 messages have been suppressed, use --verbose to show them.
nimble.nim(229)          buildFromDir
Error:  Build failed for the package: mosh

davids-Mac-Pro-2:mosh dk$
`

I can reproduce here and am generally inclined to fix this given its completely breaking ha. Give me a moment as its been a while since I touched nim.

Okay can you try now with nim version 2.0.0?
Should work.
I've also renamed the executable to bend because mosh is, as I've just learned, an already established UNIX tool.


not a issue but an idea (again)

can you add click sounds to the replay engine?

use zeo's clickbot


online image convert crash

Fatal error: Allowed memory size of 201326592 bytes exhausted (tried to allocate 134217736 bytes) in /web/littlev/littlevgl.com/tools/img_conv_core.php on line 451

How big is the image you're trying to convert? We've received several reports lately about the web converter running out of memory.

about 500K jpeg file, I have resolve it by use local tool . thanks sir

Great! We probably need to improve the script as the memory limit seems to be an issue for a lot of people.
It seems to be the same issue as https://github.com/littlevgl/lv_utils/issues/31, so let's continue the discussion there.


Exception

Hi
I use couchbase lite v 1.2.1 and forestdb i start my replicatin but i do not touch couchbse broadcast receiver ...
06-23 03:17:27.279 10940-11009/com.xxx.kkkkkkkk E/Surface: getSlotFromBufferLocked: unknown buffer: 0xb99959c0
06-23 03:17:27.308 10940-10940/com.elt.passsystem E/ActivityThread: Activity com.xx.kkkkkkkkkk.activity.synchronization.DocumentActivity has leaked IntentReceiver com.couchbase.lite.android.AndroidNetworkReachabilityManager$ConnectivityBroadcastReceiver@2440ae9 that was originally registered here. Are you missing a call to unregisterReceiver()?
  android.app.IntentReceiverLeaked: Activity com.xxx.kkkkkk.activity.synchronization.DocumentActivity has leaked IntentReceiver com.couchbase.lite.android.AndroidNetworkReachabilityManager$ConnectivityBroadcastReceiver@2440ae9 that was originally registered here. Are you missing a call to unregisterReceiver()?
      at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:918)
      at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:719)
      at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1172)
      at android.app.ContextImpl.registerReceiver(ContextImpl.java:1152)
      at android.app.ContextImpl.registerReceiver(ContextImpl.java:1146)
      at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:554)
      at com.couchbase.lite.android.AndroidNetworkReachabilityManager.startListening(AndroidNetworkReachabilityManager.java:29)
      at com.couchbase.lite.NetworkReachabilityManager.addNetworkReachabilityListener(NetworkReachabilityManager.java:26)
      at com.couchbase.lite.replicator.ReplicationInternal.startNetworkReachabilityManager(ReplicationInternal.java:329)
      at com.couchbase.lite.replicator.ReplicationInternal.start(ReplicationInternal.java:264)
      at com.couchbase.lite.replicator.ReplicationInternal$13.doIt(ReplicationInternal.java:1227)
      at com.couchbase.lite.replicator.ReplicationInternal$13.doIt(ReplicationInternal.java:1223)
      at com.github.oxo42.stateless4j.StateConfiguration$3.doIt(StateConfiguration.java:135)
      at com.github.oxo42.stateless4j.StateConfiguration$3.doIt(StateConfiguration.java:133)
      at com.github.oxo42.stateless4j.StateRepresentation.executeEntryActions(StateRepresentation.java:118)
      at com.github.oxo42.stateless4j.StateRepresentation.enter(StateRepresentation.java:97)
      at com.github.oxo42.stateless4j.StateMachine.publicFire(StateMachine.java:199)
      at com.github.oxo42.stateless4j.StateMachine.fire(StateMachine.java:126)
      at com.couchbase.lite.replicator.ReplicationInternal$1.run(ReplicationInternal.java:209)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
      at java.util.concurrent.FutureTask.run(FutureTask.java:237)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
      at java.lang.Thread.run(Thread.java:818)

Hi @lukasw44,
It seems ConnectivityBroadcastReceiver is not unregistered in couchbase lite code. We will look into it.

I think i have got that error when i try login using the same user on two devices so maybe thats may be problem.

Is there any problem with reproduce this bug ?


Request for example .env file

Issue Type

[ ] Bug (https://github.com/Kaniwani/kw-frontend/blob/master/.github/CONTRIBUTING.md#bug-reports)
[x] Feature (https://github.com/Kaniwani/kw-frontend/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description
I'd like to spin up a local instance of WaniKani for development but am in need of an example .env file. The README says to contact Duncan on Slack for this (which I did), but given this project isn't as active anymore I'm not sure that the Slack is still in use. Could an example .env file be posted in this repo for future reference?

Hey, sorry I didn't see your slack message.
Can you try with the following .env - which will run your local against prod.
If you setup a local backend just replace DEV_DOMAIN= with your localhost.
DEV_DOMAIN=https://www.kaniwani.com
RAVEN_DSN=
SENTRY_AUTH_TOKEN=
SENTRY_ORG=
SENTRY_PROJECT=

Works perfectly, thank you!


Cannot read property of 'id' undefined

The error occurs when try to register the command as slash command, the command works perfect with prefix message content.
Error:
https://devmirza.is-fucking-in.space/b21e3c58-2944-4fb6-8eff-5fde4261436d

Not from this package, also links seems a scam xD

LMAO it's not a scam

it's a sharex upload server where my screen shots are stored

Not from this package, also links seems a scam xD

Yes it's from the package the error says it all i update the markdown i accidently make it code block plus i dont use any thing in my command that uses 'id'


Feature request: Hex code entry field for any of the appearance settings

Nothing too pressing but I use your widget and has become my go-to app of a few for any new phone and widget always placed on home screen. Thank you for creating it and keeping it updated and working so nicely!
If anything, I tend to be almost OCD like in my color choices for all appearance settings in apps and display on phones and no different across all my devices. I use three particular colors and can only get the exact ones via hex codes and not by the dial rotater used in this app. I've seen a couple apps simply just add a text field that automatically places dial to that exact color match. Either way, would just really love to see this feature to make things even more perfect than they already are with it in current state.
Thanks for considering adding this at some.point in future.
Regards,
V. Justice

I'm adding this now, see https://github.com/plusonelabs/calendar-widget/issues/292#issuecomment-524551358

Released in Beta version 3.0, please try: https://play.google.com/apps/testing/org.andstatus.todoagenda
Note: Due to lots of internal changes existing widgets should be recreated. Sorry for inconvenience.

Thank you for adding this to your latest version, I really appreciate you!


[Research Epic] User and market research on roles

Overview
Before we want to continue implementing additional roles in the interface or begin research on how to tackle this topic holistically in terms of open role (often modules) development, curation of available roles and on how to expose these roles in the interface, we should start with conducting user research and analysing other existing solutions, our user feedback and past work on this topic.
Requirements

[ ] qualitative interviews with individuals and organizations
[ ] analysing user feedback & requests
[ ] analysis of role management in other financial and non-financial applications
[ ] analyze historic user research on this topic
[ ] summarize results

Timeline
discussion with @KristinaMayman required
Designs
Links
Original problem statement: https://github.com/safe-global/safe-pm/issues/85
Working document: https://www.notion.so/gnosis-safe/Role-Management-894a91099a43479582c53d45277a144e
Kick-off results: https://www.notion.so/gnosis-safe/18-05-Kickoff-fe9a134610cc406398af59a6c5856865

@johannesmoormann I suggest not to put non-frontend tasks in this project. I don't see anything in the description that would require coding in this repo.

@katspaugh will discuss moving it to the design repo.


Status line?

Would anyone like a status line? It would basically be a footer holding information such as git status.
I'm thinking the more I add, the more this theme needs options. Right now it's forcing everything upon the user, mainly cuz I made it for myself initially. ✌

Local test of the status line. Just shows the git branch for now. Like it? Should I upload it into the theme? Suggestions on what more to put there? 👋

I think it looks great, however I see all the useful info already on the pure theme for zsh.
Current branch is already a duplicate, and I was going to suggest all things that are already visible in the theme like dirty working directory / unpulled unpushed / command execution time.
Maybe some properties that apply to the current instance instead of the current folder, like:

node version
online status

What were you thinking of adding?

Thanks for the feedback! I agree that the most useful information is already provided by zsh.
I was thinking there would be some cases where it's not always visible and useful to have duplicates, while it also enables actions.
Tried adding cwd where clicking on it takes you to the directory on finder.
What do you think? 👋

Just pushed the status line to this theme. Feel free to try it.
Status line is most likely here to stay but the content is very much open to change. It's also a possibility to fork Pure and remove its git features once the status line one is fully featured itself


add remaining metadata

@loosebazooka @patflynn @briandealwis

Ping @loosebazooka @patflynn @briandealwis

Codecov Report

Merging #447 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #447   +/-   ##
=======================================
  Coverage   66.28%   66.28%
=======================================
  Files          67       67
  Lines        1815     1815
  Branches      281      281
=======================================
  Hits         1203     1203
  Misses        489      489
  Partials      123      123

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 8193135...fbc1f42. Read the comment docs.

@elharo should we not review this?

Branches got mixed up. Current version is at https://github.com/GoogleCloudPlatform/appengine-plugins-core/pull/449


[BEAM-9541] Push all docker images from RC instead of hard-coding them.

This greatly simplifies the script. It also spares us from having to hard-code yet another list of supported Flink versions, which I'm trying to avoid. There is the minor downside that listing images requires them to be present locally from build_release_candidate.sh, so we can't clean them up in between builds. However, I don't think that was ever really necessary except to save disk space.
R: @emilymye
cc: @chamikaramj

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM! I think my same concern is if someone accidently cleans up a docker image, or if someone has locally tested a new version of $LANG that is tagged at a specific release RC, but both seem very unlikely. I would feel more confident if there was a list of images to at least compare against, but that does also involve hardcoding the image names/versions again.

LGTM! I think my same concern is if someone accidently cleans up a docker image, or if someone has locally tested a new version of $LANG that is tagged at a specific release RC, but both seem very unlikely. I would feel more confident if there was a list of images to at least compare against, but that does also involve hardcoding the image names/versions again.

LGTM! I think my same concern is if someone accidently cleans up a docker image, or if someone has locally tested a new version of $LANG that is tagged at a specific release RC, but both seem very unlikely. I would feel more confident if there was a list of images to at least compare against, but that does also involve hardcoding the image names/versions again.

Another solution I considered is using docker search to list the images that have been uploaded to Docker Hub. Unfortunately the docker search tool does not offer the functionality to do this (it can find repos, but not list tags, for example). We could alternatively curl and parse a json blob from docker hub's API endpoint, but that seems like overkill here.

LGTM! I think my same concern is if someone accidently cleans up a docker image, or if someone has locally tested a new version of $LANG that is tagged at a specific release RC, but both seem very unlikely. I would feel more confident if there was a list of images to at least compare against, but that does also involve hardcoding the image names/versions again.

Another solution I considered is using docker search to list the images that have been uploaded to Docker Hub. Unfortunately the docker search tool does not offer the functionality to do this (it can find repos, but not list tags, for example). We could alternatively curl and parse a json blob from docker hub's API endpoint, but that seems like overkill here.


Sm8150: Add support for Galaxy TabS6 (gts6l)

Main

Add support for Galaxy TabS6

Support

Sd card works on Windows
Touch works on Windows
There is still more that needs to be fixed

Matters needing attention

Please note that the UFS Gpt of Samsung devices needs to be fixed. If it is not fixed, please do not manually online the disk.

I am very sorry for giving up on future support and maintenance.
However, due to the extremely "intelligent" nature of Windows auto repair mode, it forced all of my luns online. I only fixed SDA, but the other luns were not, resulting in all other luns being destroyed, the device not being able to start or even respond at all. At the same time, I do not have strong technical skills to repair my UFS, and I do not want to purchase another Samsung device, and I do not even have the ability to purchase it anymore.
Samsung is a great manufacturer and has added many IC chips. Due to this issue, tabS6 cannot use USB and requires a lot of additional repairs to achieve this. The following image can illustrate this point very well.

If anyone wants to maintain Samsung devices, be sure to fix all luns, not just SDA Otherwise, when you encounter Windows auto repair, you will encounter problems unless you have extremely fast speed and restart the device before entering auto repair mode.

@qaz6750 a52 moment

R.I.P.


xcbuild: add SDKROOT by default to the wrappers

This fixes #30269 and lets us do things like xcrun -find cc, for example.
cc @matthewbauer
Motivation for this change
#30269
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
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

I'll probably also upgrade xcbuild later. There are no new official releases but the current one has a nasty bug where it runs build steps out of order and master has a fix for that, so I'm just going to build that unless you object.

Looks good! Keep track of some of the darwin.* stuff after this is merged because they can sometimes break from changes like these.

Thanks!


V2 Telemetry Stats: Use OpenCensus

Consider using OpenCensus library for exporting prometheus metrics.
At present Wasm metrics pipeline connects directly to the Envoy Pipeline.
Envoy is not dynamically configurable, which creates problems for configurable metrics. Changing distribution buckets is also not supported.
If Stats uses opencensus to export metrics (like stackdriver filters) it will solve these problems.
There are two options.

Update stats code to directly use OC library. This may be difficult thru real Wasm.
Update Host implementation to select destination of metrics, Either send it thru the Envoy pipeline or send it out thru OpenCensus. OC requires a singleton object in C++, so this may be easier. The metrics will have to be exported on a different port, however istio-agent can scrape it locally to ensure a stable external location.

The ideal long term solution is that the EnvoyPipeline supports OC, and (2) is better aligned with that.

@jplevyak @bianpengyuan One option is changing stats filter and another to add alternate destination in the Wasm Filter impl.

The other option, register necessary OC library function using FFI. Also this will require envoy expose istio standard metrics on a different port other than 15090.
Is the only motivation to support configurable buckets?

Config buckets, crazy metrics filtering and tag extraction.
I updated the description with port change info, it can be remapped by the istio-agent.


[Bug]: Problem in search for small screen

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
As you seen in the video. The result of search is not displaying properly in mobile screen.  It's look too much annoying and not even readable format. Need to fix this
Expected behavior
This result also supposed to be look like normal other lists.
Just like this -

Add ScreenShots
Currently it display the results in this way.
https://github.com/user-attachments/assets/bbe7e27e-fa61-41a1-9e12-899f66fdffc9
@Soujanya2004  Please assign it to me. I want to fix this problem.
On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Suvadip-sana this will be implemented in #236

@Soujanya2004
Yes but in your code base the search results display in seperate ejs file not in same index.ejs file.
That's why I raised seperate ISSUE

@Suvadip-sana yeh ryt, i forgot


usrsctp send buffer does not clear itself

We're working on a webRTC data channels library that uses usrsctp, but in our test application, we keep hitting the default send buffer (256kB) and it doesn't seem like it's clearing on its own. Is there a specific flag or an attribute that we could be missing out in the implementation or is this a bug?
Related: https://github.com/chadnickbok/librtcdcpp/issues/28

I'm not aware of any issues related to this. Using the test programs I can transfer 100 MB. Running the server using programs/tsctp -E 9899 and running the client programs/tsctp -E 9999 -U 9899 -n 100000  <IP_ADDRESS>.

I guess that program works well. Here's the pcapng file anyway: https://ufile.io/btfvt

I'll have a look at the file. Currently downloading...

I can't see any problem in the tracefile. Is it a tracefile captured when you had a problem with your application? That is what I would need...

Hi Michael,
I had a brief look into tracefile as well and I believe I can see there a number of issues related to a_rwnd calculation on side with port 5001:

It seems to me that endpoint with port 5001 calculates a_rwnd incorrectly. If you have a look at frame #21 and #25 you can see two SACK chunks. First acknowledges TSN 182463615, second - 182463617. That means that TSNs 182463616 and 182463617 arrived, both data chunk had length of 1024 bytes. In case when both chunks got buffered a_rwnd should decreased by 1024*2 bytes, shouldn't it? In trace file reported a_rwnd got decreased by 2560 bytes.

Endpoint with port 5001 had abruptly shrunk a_rwnd several times. You can find all occurrences of such behaviour by this filter (sctp.sack_a_rwnd==1).  The behaviour is seen in frames #38606 and #38607. SCTP just reported a_rwnd of 23552 bytes and cumulative TSN 182489167. Next SACK reports a_rwnd as 1 byte (which is strange enough by it self) and cumulative TSN as 182489169. As in example above TSNs 182489168 and 182489169 were 1024 bytes, so a_rwnd should be decreased by 2048 bytes, not by 23551. I think such behaviour can confuse sender, not sure if it will lead to EWOULDBLOCK.

There is also seems to be an issue with the way GAPs are handled by the same endpoint (port 5001). As far as I can see all of the DATA chunks are sent via stream #0  in order (I have not seen any chunk with ordered delivery bit set to 1), which means that if any DATA chunks got lost, TSNs received after that cannot be delivery to upper layer until missed chunks are re-transmitted (correct me if I'm wrong). If frames #3049, #3051 you can see SACK chunks that reported TSN 182465567 as last received in sequence. SACK from #3049 also reports that it received TSN 182465579 and decreased a_rwnd, which means that this TSN has been buffered. Next SACK at #3051 reports that cumulative TSN is still 182465567 and TSNs 182465579-182465580 are received as well. Since tsn 182465580 should have been buffered as well, that should lead to smaller value of a_rwnd reported in SACK chunk, however this didn't happen. A_rwnd reported in SACK #3049 and #3051 are the same - 131072 bytes.

P.S. I don't know what SCTP implementation was used on the side with port 5001, maybe it was not usrsctp, but I just decided to let you know that there are some suspicious places in the trace file.

Thank you all for looking into this and sorry for the late response.
@tuexen, I thought you wanted me to run those two examples. I'll attach another trace once I figure out how to make the webRTC library talk to the sctp client/server. (I'll need to dismantle the DTLS layer)
Also, I have a feeling the SACK responses are not being redirected to the SCTP layer from DTLS layer after a while. I have a feeling there's a race condition in my implementation and it may not be the usrsctp library after all. I'll keep you all updated.

If SACKs are been filtered out by DTLS we would see a lot of retransmissions in your tracefile, which I didn't see (there are some, but not a lot) and it is quite likely would to ungraceful association termination, which I didn't see either. That makes me think that SCTP on your end were receiving SACKs.

@zinovya the trace file above was just between two example tsctp programs bundled in usrsctp library. I thought @tuexen wanted me to do that first.

@zinovya There is a known issue with the a_rwnd. See https://github.com/sctplab/usrsctp/issues/137. However, when the stack receives n bytes payload it has to buffer, it should decrement its a_rwnd by n + o, where o is some overhead. However, this is not working right now. I'll fix it soon.
usrsctp was used at both sides.
@PowerInside I wanted to see a tracefile showing the problem it figure out if you are also running in this problem. If you have some logging facility, you can integrate some logging of sent and received SCTP packets before/after DTLS handling without changing DTLS using usrsctp_dumppacket(). See ekr_loop for an example how it is used.

Here's the log file where I enabled usrsctp_dumppacket() before and after DTLS handling: https://drive.google.com/a/hamon.in/file/d/0B8arEHFxidkpTUVvcFktV0ZMZk0/view?usp=sharing
From line 32, you can notice that the usrsctp_conninput() function does not return for some reason. Line 24 and 26 seem to be the last call that worked.


Convert underscore to hyphens in generic attributes names

Just a draft idea to address https://github.com/zostera/django-bootstrap5/issues/267 to see if there is any interesting in solving the issue
The change replace _ to - in generic tag attributes
So i can do something like {% bootstrap_button data_bs_toggle="collapse" data_bs_target="#update-group-9" button_type="reset" content="Cancel" %}
Generic attributes (like data_bs_toggle) are passed to render_tag without any changes while templatetag arguments (like button_type) are not, so it's safe to make this change without interfering django-bootstrap5 behaviour

Just a draft idea to address https://github.com/zostera/django-bootstrap5/issues/267 to see if there is any interesting in solving the issue

Yes, please merge these changes.

@dyve is this something you'd be interested to merge? If so I will complete this with tests to make it actually mergeable

The idea of converting data_ tot data- is interesting. For anything  not starting with data_, it becomes a possible risk I think.

the idea behind this PR is to allow integrating htmx attributes (hx-*) which is currently not possible to support

Ok, Let's see it.

@dyve this is a first draft. I included tests to check that no existing attribute is altered

Cam here to open an issue about this. Being able to add arbitrary attributes is almost a necessity these days, and it in the template seems less hacky than setting it on the python side.

I'm interested in this solution as well. Right now I use a custom template tag and overwrite the django_bootstrap5 render_tag() function with the code changes from this PR. It works, but I would appreciate a native solution.

This looks pretty useful! With the data_ prefix, it should be mostly safe.
A possible addition is to support custom prefixes through a setting. That offers options to:

(default) BOOTSTRAP5["hyphen-attributes-prefixes"] = ["data"], converts all data_* to data-*
BOOTSTRAP5["hyphen-attributes-prefixes"] = ["data", "hx"], same as 1., and converts hx_* to hx-*
BOOTSTRAP5["hyphen-attributes-prefixes"] = []  No conversion.

It should be straightforward to maintain, and leaves an option for users wanting custom prefixes.

https://github.com/zostera/django-bootstrap5/pull/524#issuecomment-2485984608
I’ll try to push an update for this in the coming weeks.

I'm actually trying to figure it out right now, watch this space.

See #737

@yakky I continued this (with a parameter added) in #737. I'll make sure you get the credits if we merge this. If there is a better way on GitHub to continue work on a branch in someone else's repo, please let me know.


Valero/OADP support for Keycloak's EDB

Resolves https://github.ibm.com/IBMPrivateCloud/roadmap/issues/60711#issuecomment-74907167
cc @giacomoch

Do we also want to make the same changes for IM's edb deployment or do they share this config?

It's my understanding that we are waiting on new EDB version with bug fix before including this change for IM so disregard this question for now.

Do we also want to make the same changes for IM's edb deployment or do they share this config?

My understand is that

Yes, we will use those annotations into IM's EDB deployment for B&R process when we switch to velero add-on after a new EDB release containing the fix.
Can those annotations for IM's EDB deployment exist out of the box, like what we did for Keycloak's EDB deployment?

The questions arises because those annotations might be conflicted with what CPD team will add into IM's EDB deployment.
However, CS/ODLM allow annotations and label overwritten, meaning even those velero annotation exists on IM's EDB deployment initially, CPD team could overwrite it by updating CS CR.

those annotations might be conflicted with what CPD team will add into IM's EDB deployment.

It would depend on how cpd adds these annotations. If they also include them in the operand config, in my (brief) testing, you could have (roughly, it's been a minute since I looked at it):k8s.enterprisedb.io/addons: '["velero","external-backup-adapter"]' and as long as you give the hooks specified under the external-backup-adapter configuration different names than the typical velero ones (ie anything other than post.hook.backup.velero.io/command, pre.hook.backup.velero.io/command) they should not conflict.
But if CPD is overwriting the annotation field k8s.enterprisedb.io/addons after the cluster object is created then they will likely remove Bedrock's velero addon.

Note sure that it matters, but do note that the Cluster in the CR should not be changed for any of the IM and Zen work as we dont share the Cluster.
I imagine the above complication arises given both Zen and IM use the same Cluster CR. Just want to make sure the Keycloak one is not changed :)

correct, this would not affect keycloak


How to call the Script

I have no idea how this works. Where do i have to put my Code and how to I call the Function? What happens then? Creates this Code a real KML File?
Can somebody help me?

put this on your gem file
gem ruby_kml
then bundle install and thats all