WIP: Adds operator Base.:*(::ToeplitzFactorization, ::StridedVector)

For performing many Toeplitz-vector  products using the same matrix, it is efficient to reuse the factorization of the Toeplitz matrix. The README suggests that this is intended, however it's not documented how to do it. I found out (1, 2) that this works:
using ToeplitzMatrices, LinearAlgebra, Test
T = Toeplitz([0.;randn(499)], [0.;randn(999)])
x = randn(1000)
Tfac = factorize(T)
result = zeros(Float64, 500); @test mul!(result, Tfac, x, 1., 0.) == T*x

The method facilitating this is
mul!(y::StridedVector{T} where T, A::ToeplitzMatrices.ToeplitzFactorization, x::StridedVector{T} where T, α::Number, β::Number) @ ToeplitzMatrices ~/.julia/packages/ToeplitzMatrices/5gW1c/src/linearalgebra.jl:42

Besides being undocumented, it modifies the temp buffer inside the factorization A. This doesn't invalidate the factorization object (because the buffer is "temporary", I guess) but the method is not thread-safe. I think the way to make it thread-safe is to make a copy of the tmp buffer and thus not changing it. However, this obviously has an unwanted performance overhead and I don't know if thread-safety of the method (is it internal? is exporting it intented) is desired. I also didn't look at other similar methods.
I suggest possible measures including

Make this mul! method thread safe, perhaps  controlled by a parameter making it thread-safe by default but avoiding the copy when the factorization is not being reused
Add an operator Base.:*(::ToeplitzFactorization, ::StridedVector) that is thread-safe.

I implemented a suggestion for measure 1. I added comments indicating how one may approach measure 1. What do you think?
The code is not ready to merge, it has a lot of comments that should be removed and additional unit tests that illustrate my points, rather than properly testing functionality.

I don't know what's wrong with the v1.0.5, I tried starting the package from juliaup's v1.0.5 channel but that errored on instantiate already (ERROR: Unsatisfiable requirements detected for package StatsBase) ...

hopefully #91 will help


Allow empty alt attributes

Reference issue: #38
What changed in this PR:
Allows empty-string alt attributes
Fixes #38

Pull Request Test Coverage Report for Build 600

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 89.524%

Totals

Change from base Build 481:
0.003%

Covered Lines:
2158

Relevant Lines:
2288

💛  - Coveralls


[DOC] Should Neural Search Plugin be a search plugin?

What do you want to do?

[X] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Currently, in https://opensearch.org/docs/latest/, the neural search plugin has its own top level folder. I think it should be a part of the search plugins folder.

Thanks for your input! This has been fixed:


d

d

#https://github.com/ZestOfLife/PSserver/commit/0f12796a6f616a9fd5f8428fc4e4725cf5483674

#https://github.com/ZestOfLife/PSserver/commit/0f12796a6f616a9fd5f8428fc4e4725cf5483674


Slack integration

[ ] talk to George about request URL for node monitor
[ ] add functionality to be able to send a status request via slack
[ ] test daily status report feature.


Add context above TOC that indicates which guide you are in

Is your request for enhancement related to a problem? Please describe.
It is easy to lose track of whether you are currently in the developer/extender guide, the getting started, or the user guide.
Describe the solution you'd like
At the top of the table of contents, it would be nice to have an indication of which guide you are currently in. For example, "Getting Started" could display above the TOC as static text that is followed by the Zowe Overview and Release Notes sections. When a link or drop-down takes you to a page within the user guide, that text switches to say "User Guide"
Related doc pages
All (Except Homepage)
Additional context

PR https://github.com/zowe/docs-site/pull/530 created.


App performance issues while searching and loading related content

The UI seems to lock up quite often while searching and navigating to file pages -  mostly while it's trying to resolve single claims. We could batch those actions to see if that produces a better experience.

First step: @akinwale will look at tools that can provide more reporting about when/where/why lockups happen

Changes that have happened:

File page related data loads after video play starts
Search claim result data returned from search engine


HttpUrl incompatibility when using model_dump() to pass data to SqlAlchemy model

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
When using HttpUrl for field validation it should I genenrate the URL type when doing model_dump()?
When I have schema the accept HttpUrl for one of the field and when I pass the data to sqlalchemy via model_dump(), sqlalchemy throws error that it can't accept pydantic_core._pydantic_core.Url type instead of string.
SImple solution can be using .model_dump('json') but this will convert datetime like objects to string which is wrong according to schema and sqlalchemy.
So, what should be best approach for this?
Example Code
from collections.abc import AsyncGenerator
from contextlib import asynccontextmanager
from datetime import date

from fastapi import Depends, FastAPI
from pydantic import BaseModel, HttpUrl
from sqlalchemy import String
from sqlalchemy.ext.asyncio import AsyncSession, async_sessionmaker, create_async_engine
from sqlalchemy.orm import DeclarativeBase, Mapped, MappedAsDataclass, mapped_column

# --- DB
class Base(DeclarativeBase, MappedAsDataclass): ...

class User(Base):
    __tablename__ = "users"

    id: Mapped[int] = mapped_column(primary_key=True, init=False)
    first_name: Mapped[str | None] = mapped_column(String(30))
    url: Mapped[str]
    dob: Mapped[date]

engine = create_async_engine("sqlite+aiosqlite:///:memory:")
async_session_maker = async_sessionmaker(bind=engine, expire_on_commit=False)

async def get_db() -> AsyncGenerator[AsyncSession, None]:
    async with async_session_maker() as session:
        yield session

async def create_tables():
    async with engine.begin() as conn:
        await conn.run_sync(Base.metadata.drop_all)
        print("--- creating tables...")
        await conn.run_sync(Base.metadata.create_all)

# --- Schemas

class UserCreate(BaseModel):
    first_name: str | None = None
    url: HttpUrl
    dob: date

# --- FastAPI
@asynccontextmanager
async def lifespan(app: FastAPI):
    await create_tables()
    # async with async_session_maker() as db:
    #     # Perform DB operations
    yield

app = FastAPI(lifespan=lifespan)

@app.post("/users/")
async def create_user(user: UserCreate, db: AsyncSession = Depends(get_db)):
    db_product = User(**user.model_dump(mode="json"))

    db.add(db_product)
    await db.commit()
    await db.refresh(db_product)

    return db_product

Python, Pydantic & OS Version
pydantic version: 2.9.2
        pydantic-core version: 2.23.4
          pydantic-core build: profile=release pgo=false
                 install path: /home/tops/Projects/tops/fasttax/.venv/lib/python3.12/site-packages/pydantic
               python version: 3.12.5 (main, Aug 14 2024, 05:08:31) [Clang 18.1.8 ]
                     platform: Linux-5.15.0-122-generic-x86_64-with-glibc2.31
             related packages: pydantic-settings-2.5.2 typing_extensions-4.12.2 fastapi-0.115.0
                       commit: unknown

Hi @jd-solanki,
You can use a custom serializer for your url fields that converts them to strings. Ex:
from pydantic import HttpUrl, BaseModel, PlainSerializer
from datetime import datetime
from typing_extensions import Annotated

MyHttpUrl = Annotated[HttpUrl, PlainSerializer(lambda v: str(v), when_used='always')]

class TrafficEvent(BaseModel):
    id: int
    timestamp: datetime
    location: MyHttpUrl

event = TrafficEvent(id=1, timestamp='2021-01-01T00:00:00', location='http://example.com')
print(repr(event))
#> TrafficEvent(id=1, timestamp=datetime.datetime(2021, 1, 1, 0, 0), location=Url('http://example.com/'))
print(event.model_dump())
#> {'id': 1, 'timestamp': datetime.datetime(2021, 1, 1, 0, 0), 'location': 'http://example.com/'}


[GCS FT] end-to-end tests for #1341

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Add end-to-end tests for examples mentioned in the PR description of #1341.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

#1386 changes the behavior of #1341 and adds an e2e test.


TBOX-244: Documentation Validation

Wrote the following script: doc_src/validate_docs.py to validate whether all python files are included in documentation for modules and examples. Added this script to tasks.py so that it runs with invoke docs.
Additionally, added 9 missing python files to documentation, based on validation script results. Not sure if I added these properly, so let me know if any of that needs to be changed.

↪ Pull Request

✔ PR Todo

[x] Add documentation
[x] Add examples
[x] Ensure you are following the practices in the contributor guide and coding_standards

Use consistent and descriptive name conventions
Uses google-style docstrings
Uses versioned API/client methods only
Avoid global variables
Avoid giant try/catch
Don't use mutable default variables
Use a main() function in your scripts

[x] Added/updated testing for this change (ensure you are testing any changes/new code!)
[x] Update title to link to TBOX issue (i.e. start pull request title with TBOX-xx)
[x] Approval from first code-reviewer
[ ] Approval from second code-reviewer (only required if a second reviewer has left comments)
[x] Pass all checks

@wpmartin Please take a look when you get a chance. Thanks!


Add a new shared_bin log target

Recent refactor moved the HTTP request logging into a different crate, which
requires a new log target defined for the logs to be visible.

bors r+


Skip CI / skip workflow documentation clarity

What article on docs.github.com is affected?

Skip CI announcement: https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/
Skip CI documentation: https://docs.github.com/en/actions/guides/about-continuous-integration#skipping-workflow-runs
What part(s) of the article would you like to see updated?

At least to me, the announcement seemed to have misleading information.
The announcement claims the following:

If any commit message in your push ... contains the strings [skip ci], ... workflows ... will be skipped.

A push can contain several commits and the announcement says that if any commit message has the tag, then the workflows will be skipped.
However, that is not true as only the latest commit in a batch of commits was evaluated for the tag when I tested the feature.
Furthermore, the documentation of the feature is also not clear on what exactly happens when you push multiple commits as seen in the following:

Workflows ... won't be triggered if you add any any of the following strings to the commit message in a push

The documentation talks about "the commit message", which could be possibly assumed to mean the latest commit in a push of several commits, but it is ultimately unclear.
In addition, there is a typo in the documentation saying any any, that should be corrected.
Proposed solution:
The misleading text about "any commit" should be removed from the announcement.
The typo should be corrected.
The announcement and the documentation could be modified to more clearly state what actually happens when you push multiple commits.
The announcement could link to the documentation.
Additional information

The announcement is the first result on search engines to me when searching with github actions skip ci, so I feel it is important to correct the information that it gives.
The documentation was harder to find. Especially since the announcement does not link to it and it did not seem to be anywhere in search engine results outside of GitHub. I only found it by searching Github docs with skip ci.
PS. github support directed me here.

Hello @Rochet2, thanks for reaching out about this.
I've reviewed this with the team and we want to be clear on what it is you want changed and why. Would you mind opening a new issue specifically for the documentation change you're proposing so that we can be certain that we evaluate it properly? Let me know if you have any questions.
Thanks for helping make the GitHub documentation better!


Closes #229 Rely on updated libpak/sherpa for bool. parsing

More context at https://github.com/paketo-buildpacks/libpak/pull/220

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

hello! I have successfully rebased on main, and locally built and run the tests; it all worked!


Transform when dragging Mondrian graph nodes is not working correctly

Go to comment tab of GtMondrianBasicExamples and drag on the nodes of the example graphs. Note that the node "runs away" from the cursor position and is offset by some amount as dragging proceeds.
GToolkit 0.8.439, Windows

Thanks!

Thanks!

Thank you for the issue :)
It should work as expected now

Thank you for the issue :)
It should work as expected now


Use barrier type props

This depends on
https://github.com/binary-com/binary-utils/pull/1

It's failing because method required in binary-utils is not there yet


Prefer distribution/lib/Standard files when runEngineDistribution

Pull Request Description
Prefer distribution/lib/Standard/* files over the files in built-distribution/enso-engine-*/enso-0.0.0-dev/lib/Standard/. This solves the common error when one debugs thru files and edits them just to find out they are rewritten by next build.
Important Notes
The support for locating alternativeFile is only enabled for developers. E.g. have to run with -ea enabled and Enso version is 0.0.0-dev. Both of these conditions are satisfied when one uses:
sbt:enso> runEngineDistribution --run test/Base_Tests --debug

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Java,
[ ] Debugging was manually tested

JVM tests are hitting the assert introduced by this PR...

That is unexpected. Clearly, CI jobs are setting ENSO_VERSION (https://github.com/enso-org/enso/actions/runs/12124001092/job/33800730744?pr=11736#step:7:132) to something else than 0.0.0-dev.

Do I assume correctly that this also works for enso --inspect --run ...?

Yes, when the enso launcher is started with -ea (for example via sbt's runEngineDistribution), then even Chrome Dev tools show the sources from distribution/lib:

Wow I didn't use runEngineDistribution much, but that makes me want to reconsider! This should cut the iteration time tremendously!


Magento 2.2 Compatibility

Does not support composer installation due to incompatibility with magento/framework version constraints: https://github.com/meanbee/magento2-csspreload/blob/master/composer.json#L16
Support for magento/framework version 101.* would resolve this, e.g:
    "magento/framework": "100.1.*|101.*",

2.2 comes with a large number of changes and while the feature set of this extension is unlikely to be affected, we should still test it to make sure nothing breaks. If all is well, then I have no objections to updating the version requirements.


why virtualenv method is not provided as an alternative?

$ python -m venv venv
$ python --version
Python 3.8.6
$ source venv/bin/activate
(venv)$ pip install azure-cli
Successfully installed PyJWT-1.7.1 adal-1.2.5 antlr4-python3-runtime-4.7.2 applicationinsights-0.11.9 argcomplete-1.12.2 azure-appconfiguration-1.1.1 azure-batch-10.0.0 azure-cli-2.17.1 azure-cli-core-2.17.1 azure-cli-telemetry-1.0.6 azure-common-1.1.26 azure-core-1.9.0 azure-cosmos-3.2.0 azure-datalake-store-0.0.51 azure-functions-devops-build-0.0.22 azure-graphrbac-0.60.0 azure-keyvault-1.1.0 azure-keyvault-administration-4.0.0b2 azure-loganalytics-0.1.0 azure-mgmt-advisor-2.0.1 azure-mgmt-apimanagement-0.2.0 azure-mgmt-appconfiguration-0.6.0 azure-mgmt-applicationinsights-0.1.1 azure-mgmt-authorization-0.61.0 azure-mgmt-batch-9.0.0 azure-mgmt-batchai-2.0.0 azure-mgmt-billing-1.0.0 azure-mgmt-botservice-0.2.0 azure-mgmt-cdn-5.2.0 azure-mgmt-cognitiveservices-6.3.0 azure-mgmt-compute-18.0.0 azure-mgmt-consumption-2.0.0 azure-mgmt-containerinstance-1.5.0 azure-mgmt-containerregistry-3.0.0rc16 azure-mgmt-containerservice-9.4.0 azure-mgmt-core-1.2.1 azure-mgmt-cosmosdb-1.0.0 azure-mgmt-databoxedge-0.2.0 azure-mgmt-datalake-analytics-0.2.1 azure-mgmt-datalake-nspkg-3.0.1 azure-mgmt-datalake-store-0.5.0 azure-mgmt-datamigration-0.1.0 azure-mgmt-deploymentmanager-0.2.0 azure-mgmt-devtestlabs-4.0.0 azure-mgmt-dns-2.1.0 azure-mgmt-eventgrid-3.0.0rc7 azure-mgmt-eventhub-4.1.0 azure-mgmt-hdinsight-2.0.0 azure-mgmt-imagebuilder-0.4.0 azure-mgmt-iotcentral-3.0.0 azure-mgmt-iothub-0.12.0 azure-mgmt-iothubprovisioningservices-0.2.0 azure-mgmt-keyvault-8.0.0 azure-mgmt-kusto-0.3.0 azure-mgmt-loganalytics-0.7.0 azure-mgmt-managedservices-1.0.0 azure-mgmt-managementgroups-0.2.0 azure-mgmt-maps-0.1.0 azure-mgmt-marketplaceordering-0.2.1 azure-mgmt-media-2.2.0 azure-mgmt-monitor-0.11.0 azure-mgmt-msi-0.2.0 azure-mgmt-netapp-0.14.0 azure-mgmt-network-17.0.0 azure-mgmt-nspkg-3.0.2 azure-mgmt-policyinsights-0.5.0 azure-mgmt-privatedns-0.1.0 azure-mgmt-rdbms-3.1.0rc1 azure-mgmt-recoveryservices-0.4.0 azure-mgmt-recoveryservicesbackup-0.6.0 azure-mgmt-redhatopenshift-0.1.0 azure-mgmt-redis-7.0.0rc2 azure-mgmt-relay-0.1.0 azure-mgmt-reservations-0.6.0 azure-mgmt-resource-10.3.0 azure-mgmt-search-2.1.0 azure-mgmt-security-0.6.0 azure-mgmt-servicebus-0.6.0 azure-mgmt-servicefabric-0.5.0 azure-mgmt-signalr-0.4.0 azure-mgmt-sql-0.21.0 azure-mgmt-sqlvirtualmachine-0.5.0 azure-mgmt-storage-16.0.0 azure-mgmt-synapse-0.5.0 azure-mgmt-trafficmanager-0.51.0 azure-mgmt-web-0.48.0 azure-multiapi-storage-0.5.2 azure-nspkg-3.0.2 azure-storage-common-1.4.2 azure-synapse-accesscontrol-0.2.0 azure-synapse-artifacts-0.3.0 azure-synapse-spark-0.2.0 bcrypt-3.2.0 certifi-2020.12.5 chardet-4.0.0 colorama-0.4.4 cryptography-2.9.2 fabric-2.5.0 humanfriendly-8.2 idna-2.10 invoke-1.5.0 isodate-0.6.0 javaproperties-0.5.1 jmespath-0.10.0 jsmin-2.2.2 jsondiff-1.2.0 knack-0.7.2 mock-4.0.3 msal-1.0.0 msal-extensions-0.1.3 msrest-0.6.19 msrestazure-0.6.4 oauthlib-3.1.0 paramiko-2.7.2 pkginfo-1.6.1 portalocker-1.7.1 psutil-5.8.0 pygments-2.7.3 pynacl-1.4.0 pyopenssl-19.1.0 python-dateutil-2.8.1 pytz-2019.1 requests-2.25.1 requests-oauthlib-1.3.0 scp-0.13.3 sshtunnel-0.1.5 tabulate-0.8.7 urllib3-1.26.2 vsts-0.1.25 vsts-cd-manager-1.0.2 websocket-client-0.56.0 xmltodict-0.12.0
as it can be seen, no need to have a homebrew.
or
poetry init
and add azure-cli when asked

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

ID: d09ed623-c83f-6bae-639e-a5f9a31fe3bb
Version Independent ID: c5d0d722-aacd-47a3-3fcf-982c02c4d0e9
Content: Install the Azure CLI for macOS
Content Source: docs-ref-conceptual/install-azure-cli-macos.md
Service: azure-cli
GitHub Login: @dbradish-microsoft
Microsoft Alias: dbradish

@kunthar
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

@kunthar
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

hi @fengzhou-msft could you pls help to have a look? thanks

hi @fengzhou-msft could you pls help to have a look? thanks

@kunthar We will plan a new doc for installing azure-cli with pip in virtualenv for all platforms.

@kunthar We will plan a new doc for installing azure-cli with pip in virtualenv for all platforms.

@yungezz - Thank you for providing your insights.
@kunthar - I hope @yungezz has answered your question.
At this moment, Since there is no doc update required for this particular doc, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@yungezz - Thank you for providing your insights.
@kunthar - I hope @yungezz has answered your question.
At this moment, Since there is no doc update required for this particular doc, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


CD doesn't update the deployment image?

I updated the image but noticed that the shiny deployment doesn't switch to the new image. Even when I manually restarted the deployment it didn't switch (still using the old sha).
How would I do this manually (until such a time as we integrate it into the CD) ?

Hey if okay this should always be done with a P.R. so can always get a +1 from someone as is a live service before gets merged.
The CD atm only deploys for Shiny when is a stable tag release that has been published.

@zachomedia @justbert

Ok sure thing; will make sure to always go through a PR.
I think issue #2 is still affected until the server is updated. @menmark . I'm off my machine now, but tomorrow morning I should just tag this as release then he should be good to go?
-------- Original Message --------
On Apr 28, 2020, 11:18 PM, William H <<EMAIL_ADDRESS>wrote:
Hey if okay this should always be done with a P.R. so can always get a +1 from someone as is a live service before gets merged.
The CD atm only deploys for Shiny when is a stable tag release that has been published.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.￼
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "[https://github.com](https://github.com/StatCan/shiny/issues/3#issuecomment-620968339", "url": "[https://github.com](https://github.com/StatCan/shiny/issues/3#issuecomment-620968339", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

@blairdrummond Can you check now? I've created and published a release of the repo which triggered a deployment

Working now!


Regarding the citation of paper data?

Hello, author. First of all, thank you for your work, which is very inspiring to us. However, we found that the effect of your work on the Synapse dataset is consistent with that in HiFormer. In other words, can we directly cite the data of other papers that have run the Synapse dataset? I am a beginner and I don't quite understand this aspect. Looking forward to your answer! Translate this content into English.

Thanks for being interested in our work. Could you elaborate on your question a bit more ? I guess you were trying to say if it's fine to cite the performance from the other papers (e.g., HiFormer, TransUNet, SwinUNet) on Synapse dataset. As long as you are following the same experimental protocol as those papers (or simply building upon their code), it is totally reasonable. We cited their empirical results directly since we followed the same experimental protocols. If pre-trained weights are released by the authors (e.g., our AgileFormer, nnFormer, etc), you are definitely welcome to test them yourself. Hope this will answer your question.

OK, thanks for your reply. We have two more questions for you. Question 1: Can you explain specifically what the same experimental protocol refers to? Is it the same experimental configuration? For example, are the settings for lr, weight_decay, batch_size, etc.? Question 2: You said that you can directly quote the experimental results of the SwinUNet paper on Synapse. In other words, you do not need to retrain SwinUNet on Synapse. But I have seen that the author team of SwinUNet did not open source their pre-trained weights on github. So how did you get the segmentation result map of SwinUNet on the Synapse data set? This question has troubled us for a long time, and we look forward to your answer.

To your first question, What I meant by the same experimental protocol was mainly the training/testing split and preprocessing, whereas hyperparameters (lr, weight_decay, num of epochs, batch size, etc) can vary from model to model (i.e., what we typically refer to as hyperparameter tuning). To your second question, yes. We retrained the SwinUNet to reproduce their results (79.13) for visualization. You can contact me at my email<EMAIL_ADDRESS>if you want some results for visualization. I also shared the visualization code in this repo.

Thank you very much for your reply.However, your model hyperparameters, such as lr, batch_size, etc., are not consistent with swinunet's hyperparameters. , how can you possibly reproduce the segmentation results consistent with swinunet? (Even if the same machine, the same hyperparameter configuration, is retrained and tested twice, the segmentation results of the two times cannot be the same, right?) Or, the segmentation result you reproduce is not 79.13, but you will log in locally The segmentation results of swinunet are visualized. That is, the segmentation score corresponding to the swinunet segmentation result map in your paper is not 79.13?

I don't mean any harm. I never understood how to directly quote data from other papers, but I couldn't get the corresponding segmentation result map. The data in the paper cannot be reproduced locally. We also thought of this approach, but we want to confirm whether this approach is reasonable.

I want to make it very clear. What I meant by reproducing SwinUnet’s results was done by its code and certainly what they identified as the optimal hyperparameters, instead of the configurations in our settings. Indeed, we can reproduce SwinUnet’s results as the authors have the random seed fixed (I tried this on different machines, the results were the same). You’ll expect to produce the same results even on different machines, though minor deviations may be possible due to numerical issues of your system. For the other hyperparameters, it can definitely vary from model to model: even when you change a small portion of the model, your “optimal” hyperparameters should be reset. With that said, I think the most convincing way is to open source the segmentation results, which I will do shortly. But I cannot guarantee for other models.


New CLI including REPL

-c/--compile to compile specified .civet files to .civet.tsx or .civet.jsx files (according to --js flag)
-o/--output lets you override the output directory/extension/filename
Without -c, runs files directly (like coffee)
- to run or compile stdin; -o - to output to stdout
civet <input >output still works
civet alone runs simple REPL with cute prompt: 🐱>

I also made the main compile function turn on coffeeCompat by default (when no other civet directive) for filenames ending with .coffee. This currently messes up line numbers by 1 though... Ideally we'd have a way to send information to the parser, but I don't know how.
Builds on #96
TODO: require registration, so requires work (this is generally missing in Civet I think)
TODO: civet foo.civet in ESM mode?

Rebased and added a commit that does "civet coffeeCompat";#{src}


Add usage instructions

Nice package!
I thought it would be helpful to have some usage instructions.
Since you posted this on your blog, I just linked the article and copied the relevant instructions.

No problem!
I just saw you already have a quickstart.rst in the docs folder.
Probably makes sense to just use that in the Readme, since it is quite comprehensive.
Sorry for that😅

No worries. It's all an iterative process and there wasn't anything to show how it works when visiting the repo. Now there is!


Monthly cycle?

Would it be possible to schedule a reminder on the first day of the month?
At the moment, as a workaround, one could use active day 1 pause 30 days, but it's not ideal.

I would do it the same way as for the weekdays: have a list of days of the month to select on when the reminder should trigger. This would solve the use case.
Will plan it for the next release.


nixos/systemd: don't require network-online.target for multi-user.target

Previously we required network-online.target for multi-user.target. This has made a lot of people very angry and has been widely regarded as a bad move (or at least, very nonstandard):
https://github.com/NixOS/nixpkgs/commit/15d761a525a025de0680b62e8ab79a9d183f313d#commitcomment-128564097
This was done because of fragile tests and services declaring dependencies on multi-user.target when they meant network-online.target.
Let's rip off the bandaid and fix our tests.
I have not yet run any tests locally, and this is probably going to break a bunch of stuff. We should get some hydra resources and gather a list of the broken tests.
cc @NixOS/systemd
Previous related PRs/attempts in vain to execute this change:

https://github.com/NixOS/nixpkgs/pull/86273
https://github.com/NixOS/nixpkgs/pull/86484

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Tests I managed to run and failed prior to something starting to compile firefox and me realizing this is absolutely a hydra-requiring task:

/nix/store/0604s4qllgbidl8lk1s1landm0wx8dad-vm-test-run-qemu-vm-restrictnetwork.drv
/nix/store/06b20phngwjph1hx34fvzj0q73lgiq7a-vm-test-run-rss2email.drv
/nix/store/06phq00lx028ca6zxfl47r2iva6qp6ww-vm-test-run-systemd-networkd-dhcpserver.drv
/nix/store/07pz2q32lhy0dqdcs63pgwqx805g4cy0-vm-test-run-paperless.drv
/nix/store/094cnijjhv78yjcz4ia9wbrxidjr1nq8-vm-test-run-zrepl.drv

Tests that seem to just be flaky/unrelated broken?

/nix/store/1l9ws129lraf63k1mvvb8pk1cnimh0vy-vm-test-run-pgjwt.drv
/nix/store/1x1bnhnjlr00gv10vv6nlwvjrj89mm68-vm-test-run-ec2-nixops-userdata.drv
/nix/store/23z9h56svc6y7a3npn0lnd8rxx0gn94z-vm-test-run-pipewire-0.3.80.drv
/nix/store/23z9h56svc6y7a3npn0lnd8rxx0gn94z-vm-test-run-pipewire-0.3.80.drv

Firefox shouldn't have to be built if you use a revision where it's built

Firefox shouldn't have to be built if you use a revision where it's built, rebase onto nixos-unstable to not require hydra to build anything else than the tests.

Yes, but the tests themselves are also very annoying and resource intensive to build hahaha.

Summary of discussion on Matrix with uep, Raito and others regarding this: our first goal is to get a Hydra run of all the tests with this PR applied. Then we can start fixing ones we know of and apply this change by default to all tests for the 23.11 release.
In 24.05 we may be able to roll this out to all systems, and it will plausibly cause some breakage. Another suggestion was to apply it to all systems right after branch-off; this seems also plausible.

https://hydra.nixos.org/jobset/nixos/pr-258680-systemd_network-online.target

rebased against nixos-unstable so hydra can be more useful. should have done that earlier.

It was quite close from the start, if I looked right.

Pipewire tests are known broken in the VM currently.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-does-multi-user-target-depend-on-network-online-target/33565/11

Rebased to master for the 24.05 cycle. Going to let Hydra have another go at it, and see if there are new issues.

@ofborg eval

Is it planned to make multi-user.target depend on network.target instead?

alright, I think I have found any of the ones I might find.

Is it planned to make multi-user.target depend on network.target instead?

I don't think any other distributions do this.

Is it planned to make multi-user.target depend on network.target instead?

I don't think any other distributions do this.

I think otherwise services like NetworkManager might not get pulled up correctly on boot.

Note the distinction between this unit and network.target. This unit is an active unit (i.e. pulled in by the consumer rather than the provider of this functionality) and pulls in a service which possibly adds substantial delays to further execution. In contrast, network.target is a passive unit (i.e. pulled in by the provider of the functionality, rather than the consumer) that usually does not delay execution much. Usually, network.target is part of the boot of most systems, while network-online.target is not, except when at least one unit requires it. Also see Running Services After the Network Is Up for more information.

This is what systemd documentation says about it.

The alternative would of course be to depend on network management services like NetworkManager directly. But I think those services should at least be triggered when multi-user.target is reached.

Is it planned to make multi-user.target depend on network.target instead?

I don't think any other distributions do this.

I think otherwise services like NetworkManager might not get pulled up correctly on boot.

I believe this is incorrect. On my arch system the following is the case:
systemd-networkd is wants=network.target, wantedby=multi-user.target; network.target is after=systemd-networkd.service.
Thus we don't need any wacky stuff above and beyond upstream.

@jzbor indeed, @lf- has it right.

In contrast, network.target is a passive unit (i.e. pulled in by the provider of the functionality

The "provider" is e.g. systemd-networkd.service, so that is the service that should be pulling network.target in. systemd-networkd.service gets pulled in by the administrator by enabling it, which makes it wanted by multi-user.target.

Yes I am sorry, I have misread the paragraph. Nevertheless I am not quite sure if an additional dependency of mutli-user.target on systemd-networkd.service or NetworkManager.service would be needed to avoid breaking existing setups. I only speak regarding NetworkManager as this is what I am using/what I tested, but as far as I can tell it does not have any connections to the multi-user.target target, at least not on my machine (NixOS unstable):
[jzbor@x1-carbon] ~ systemctl show NetworkManager.service | grep -i want
Wants=network.target
WantedBy=network.target

Although maybe this is just the case for NetworkManager, as I have not tested networkd.
This seems to also be the way Arch does it.
I am sure you guys have a lot more knowledge about the systemd stuff, so if you think this is irrelevant or does not apply just keep on going with this great PR. Just thought I would bring this to your attention. :)

Needs one more rebase.

Needs one more rebase.

Noted and done. Thank you.

Had a last look and noticed you were starting network-online.target manually on tests that wait for it. Is that in lieu of a proper network configuration, or why did that become necessary?

Had a last look and noticed you were starting network-online.target manually on tests that wait for it. Is that in lieu of a proper network configuration, or why did that become necessary?

That's because the test scripts depend on the network getting started, and "wait for unit" does not mean Wants=, but only After=, as I understand it, so they would get stuck. Starting it explicitly is a command line way of saying "my script is Wants=network-online.target After=network-online.target".

I disabled the Hydra jobset now.

Committing to reverting, since we did not have much of any test coverage of network-manager (!!!!!) and thus didn't catch the regression https://github.com/NixOS/nixpkgs/issues/71151
This is evidence that we need to do another revision of this.


[WIP] Skip SSL Validation option

Pull Request Test Coverage Report for Build 150

0 of 29 (0.0%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 2.304%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/config/config.go
0
1
0.0%

pkg/osb/config.go
0
2
0.0%

pkg/sm/config.go
0
2
0.0%

pkg/sm/client.go
0
11
0.0%

pkg/sbproxy/sbproxy.go
0
13
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/osb/config.go
1
0.0%

Totals

Change from base Build 144:
-0.07%

Covered Lines:
17

Relevant Lines:
738

💛  - Coveralls


We only need to check for mangledGenericTypeNameSym once

Incorporated the feedback

@forki,  looks like there are conflicts.

Hmmm I got that wrong.

@dsyme, you have requested changes, can you work with @forki to resolve whether you still need them?
Thanks
Kevin

Already fixed it according to the feedback. Please review again


Enhancement Request: Climate Temperature, Glass Surface Heating & Seat Heaters

Background
After extensive debugging, I've managed to customize the start_climatisation service call for my Audi, allowing for hard-coded control over temperature settings, glass surface heating, and individual seat heaters. This discovery enables a more personalized climate control experience directly from the code.
Current Implementation
Currently, adjustments are made by directly modifying the service call within the audi_services.py file, specifically on line 547. The original line of code is:
data = '{"action":{"type": "startClimatisation","settings": {"targetTemperature": 2941,"climatisationWithoutHVpower": true,"heaterSource": "electric","climaterElementSettings": {"isClimatisationAtUnlock": false, "isMirrorHeatingEnabled": true,}}}}'

Proposed Enhancement
I have successfully modified the code to enable front seat heaters as well, showcasing the potential for variable control:
data = '{"action":{"type": "startClimatisation", "settings": {"targetTemperature": 2941, "climatisationWithoutHVpower": true, "heaterSource": "electric", "climaterElementSettings": {"isClimatisationAtUnlock": false, "isMirrorHeatingEnabled": true, "zoneSettings": {"zoneSetting": [{"value": {"isEnabled": true, "position": "frontLeft"}}, {"value": {"isEnabled": true, "position": "frontRight"}}, {"value": {"isEnabled": false, "position": "rearLeft"}}, {"value": {"isEnabled": false, "position": "rearRight"}}]}}}}}'

Details on Controllable Features

Temperature: The temperature value is in deca-kelvin. The formula for converting from Fahrenheit to the target temperature is as follows:
selected_target_temperature_f = 70
selected_target_temperature_c = int((selected_target_temperature_f - 32) * (5/9))
target_temperature = selected_target_temperature_c * 10 + 2731

This formula calculates "2941" for a 70°F target.

Glass Surface Heating: Controlled by the boolean isMirrorHeatingEnabled.

Seat Heaters ("Auto Seat Comfort"): The seat heaters are managed via boolean values under zoneSettings for each seat. My vehicle lacks rear seat heaters, so defaults for those do not affect functionality.

Enhancement Request
Would it be possible to pass variables for temperature, glass surface heating, and seat comfort settings along with the VIN and action in the start_climatisation service call? Ideally, the service would use default values if none are provided. The variables could include:

temperature_f and/or temperature_c
glass_surface_heating
seat_comfort_front_left
seat_comfort_front_right
seat_comfort_rear_left
seat_comfort_rear_right

This enhancement would greatly increase the usability and flexibility of the Audi services integration, allowing users to control these settings directly from the Home Assistant front end.

Would this be something you could create a PR for?

My knowledge is pretty limited past this point. Not sure where to start to pull the values from the front end service call. I can give it a shot, but it will take me a lot of time and testing. I'll work on it, but wanted to put my findings out there if someone else can get to it first.

Would this be something you could create a PR for?

I think I've done it. Won't be able to test on my vehicle until tomorrow. Will report back after testing.

Would this be something you could create a PR for?

Tested, working, and submitted pull request. Apologies for the absolute nightmare of commits. I've never used the github process before. Let me know if you need me to submit a different way or change anything.

Will be implemented with #306


Hash win/loss record mapping on NFT.id & NFT.getType()

Issue To Be Solved
In the current implementation of RockPaperScissorsGame, win/loss records are indexed on NFT.id. However, since the contract has been generalized to accept any NFT, this indexing scheme can lead to collisions between NFTs that assign ids arbitrarily (e.g. on total supply). This removes the uniqueness guarantees implied by win/loss records of a given NFT
Suggest A Solution
As mentioned in #33, a possible solution is to index on a combination of the NFT's id & Type. Hashing the two values would give us a single unique value on which to index. This means that the current RockPaperScissorsGame.winLossRecords would have a Type of {String: GamingMetadataViews.BasicWinLoss} where the String index is the hashed value of the NFT's id & Type.
The encoding scheme would look something like:
pub fun encodeNFTIndex(nftID: UInt64, nftType: Type): String {
    let nftIDToBytes = nftID.toBigEndianBytes()
    let nftTypeToBytes = nftType.identifier.utf8
    let hashArray = nftIDToBytes.concat(nftTypeToBytes)
    return String.encodeHex(HashAlgorithm.SHA3_256.hash(hashArray))
}

Inserting & looking up the NFT's win/loss record would require the id & Type of the NFT in question, and the two arguments  would be used to derive the index with the above encoding method.

@sisyphusSmiling can we close this one?

Disregarding this approach in favor of indexing win/loss on UUID


Update DataToolUtils.java

在传入的message为null的情况下，会有报空指针的风险，加判空检查。

Codecov Report

Merging #82 into develop will decrease coverage by 0.13%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop      #82      +/-   ##
=============================================
- Coverage      49.63%   49.49%   -0.14%
+ Complexity      1246     1242       -4
=============================================
  Files            159      159
  Lines           8275     8277       +2
  Branches        1034     1034
=============================================
- Hits            4107     4097      -10
- Misses          3742     3749       +7
- Partials         426      431       +5

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/com/webank/weid/util/DataToolUtils.java
66.18% <0%> (-0.24%)
123 <1> (ø)

.../weid/protocol/response/ResolveEventLogResult.java
57.14% <0%> (-28.58%)
3% <0%> (-1%)

...rvice/impl/engine/fiscov2/WeIdServiceEngineV2.java
73.95% <0%> (-3.73%)
33% <0%> (-3%)

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 e4696ae...85e863e. Read the comment docs.

Thanks @IdioticMadman


Bump and cli dependency

Resolves #10 Bump and-cli from 2.0.0-beta.2 to 2.7.1
Bumps and-cli to latest version and updates references to renamed functions. Additionally, fixed an issue with the dotnet --version example command flag that conflicts with the base --version flag from commander.

[x] Related GitHub issue(s) linked in PR description
[x] Destination branch merged, built and tested with your changes
[x] Code formatted and follows best practices and patterns
[x] Code builds cleanly (no additional warnings or errors)
[x] Manually tested
[x] Automated tests are passing
[-] No decreases in automated test coverage
[x] Documentation updated (readme, docs, comments, etc.)
[-] Localization: No hard-coded error messages in code files (minimally in string constants)

@all-contributors add @jstevenson for review


Remove benchmarks from test suite

Remove benchmark measurements and printouts (that nobody probably ever reads) from the test suite, now we have a benchmark suite where they should belong.

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

Merging [#1986][cc-pull] into [master][cc-base-branch] will decrease coverage by <.01%

@@             master      #1986   diff @@
==========================================
  Files           303        303
  Lines         53992      53967    -25
  Methods           0          0
  Messages          0          0
  Branches       5576       5572     -4
==========================================
- Hits          47123      47098    -25
  Misses         5950       5950
  Partials        919        919

Powered by Codecov. Last updated by [b8eed30...43c1b87][cc-compare]
[cc-base-branch]: https://codecov.io/gh/numba/numba/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/numba/numba/compare/b8eed30b6cc561631dfcc021c52c77230287654a...43c1b87014711bf9c510b4c0204148083a546ecf?src=pr
[cc-pull]: https://codecov.io/gh/numba/numba/pull/1986?src=pr


Send email on integration tests fail

We would want these integration tests to run periodically as well, and only send the email on the periodic job.

Note that only the integration tests should be periodic, not the lint jobs.

@claudiubelu The PR has been updated. The workflow now runs periodically. The lint job has been excluded from running periodically and the email is only sent for integration testing in case of failure.

LGTM!
The CI failures are unrelated, and they have already been fixed (see https://github.com/finos/legend-juju-bundle/pull/33).


[BUG]

Version Information
PHP Version:
Package Version (l5-api):
Describe the bug
I am getting an error when trying to setup docker.
configure: error: Package requirements (oniguruma) were not met:
No package 'oniguruma' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables ONIG_CFLAGS
and ONIG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
To Reproduce
When I run docker-compose up
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Hey @Eolykab
Would I be correct to say you are writing to compile PHP 7.4 image ?

Yes correct

Hey @Eolykab , I will update the boilerplate to make PHP 7.4 default (for some reason I thought this was already the case)
Meanwhile, to fix this I think all you need to do is add this to the list of packages being installed at the top of the Dockerfile of the "php-fpm" and "workspace "containers (inside env/docker)
    libonig-dev \

Works like a charm. Thanks

tagged as v2.0.3


terraform, aws: add 2i2c:hub-name tags to buckets

Check if existing buckets can be updated with tags via terraform, if it is, then that is a requirement for this issue to be done.
EDIT: buckets tag can get updated with tags easily, anything in terraform can!

Try to mix in the tag 2i2c:hub-name into other tags applied to buckets in some way.
How isn't obvious, because the user_buckets variable isn't directly tied to a hub - maybe we need to be more explicit about it though and listing that? I'm not sure - its part of this issue to figure out what is a reasonable path forward to still tag each bucket with 2i2c:hub-name=one-hub-name

Definition of done

[x] It's determined if we can update existing buckets with tags
We can!
[ ] Terraform files are adjusted so that new hubs don't risk not getting the 2i2c:hub-name tag set on their new buckets

We moved this back to 'up next' because it is unclear what the target of this is. I see those tags are already applied for openscapes.

The target is to ensure its easy to retroactively enable cost attribution in our AWS clusters, by in the context of buckets getting them attributed to a specific hub automatically.

Its not straightforward to get this done though, so maybe having this explicitly set is the way to go.
I'll go for a close now since I no longer think getting it done automatic is the way to go, which this issue was written assuming it was.


fix: dockerfile

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: Extend fiveg_rfsim interface

This PR extends the fiveg_rfsim interface according to the TE126 - Orchestrating network configuration between the Core and the RAN specification.
This interface is only used internally between the DUs (Distributed Unit) and the UEs (User equipment) to orchestrate network configuration for the Charmed Aether SD-Core.

@tonyandrewmeyer  Could you please review ? Many thanks.


dont want systemd if started with custom home

what do you think about specified via environment variable?

Doesn't seem to work for me.
% HOME=/home/md/hello keybase status
Username:      modalduality

I don't understand what you mean by "it doesn't work" --- does the repro not work, or the fix doesn't work?

Right, my point is that this fails:
HOME=/tmp/foo XDG_RUNTIME_DIR= keybase status

for the same reason that this fails:
keybase --home=/tmp/foo status

And therefore, we should disable systemd when we see HOME for the same reason we disable it when we see --home

@heronhaye I pushed another attempt ^?

Isn't $HOME always set? so it's difficult to tell a non-standard home. Can probably ask the system if $HOME is real home dir for current user (the one that's also in /etc/passwd)

Oh, @zapu, good point...

(not sure what we're doing here, will leave this PR open for now)

closing for now


ARROW-1993: [Python] Add function for determining implied Arrow schema from pandas.DataFrame

cc @fjetter and @crepererum: This might be interesting for you. This is a first iteration of extracting Arrow schemas from Pandas DataFrames without doing the full conversion. It still does the conversion on object columns but I would add a follow-up PR that exposes some of the type guessing functions from C++ here so that we can call them instead of the full conversion.

@keechongtan could you rebase this? I can try to take a closer look soon

@wesm rebased.

Hi @keechongtan, thanks for posting the PR! I haven't taken a detailed look at your code yet, but there seem to be some problems (perhaps due to rebasing?):

the flake8 step fails on Travis-CI
the _ndarray_to_array and from_pandas functions seem duplicated
Cython compilation fails (both on AppVeyor and Travis-CI)

@pitrou @wesm I made this PR up to date.
I intend to refactor the pandas_compat module afterwards, because it's pretty hard to follow what happens there.

I will have a look


[Hub Generated] Review request for Microsoft.AzureStack to add version stable/2016-01-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run unifiedPipeline

This PR is adding missing api version 2016-01-01 for swagger completeness.

This PR is adding missing api version 2016-01-01 for swagger completeness.

I have updated the PR checklist accordingly

@varunkumta we are taking care of s360 alerts but not by changes to an existing API version, but by adding a missing one for swagger completeness - that's why I initially had it marked as "new API version" .
Here's a link to the s360 issues we are addressing with this PR
https://vnext.s360.msftcloudes.com/blades/unifiedplatform?blade=AssignedTo:All~KPI:6dc4e485-2d1b-449c-a224-30b183391437~SLA:1~Forums:All~_loc:UnifiedPlatform&def=&peopleBasedNodes=avishwan_team;maximpop_team&tile=S360_ServiceId:9537bbc3-8945-4a80-a398-9e894170cc28~_loc:__key__UnifiedPlatform__6dc4e485-2d1b-449c-a224-30b183391437&global=4:9537bbc3-8945-4a80-a398-9e894170cc28
Cc: @markcowl for awareness

@varunkumta we are taking care of s360 alerts but not by changes to an existing API version, but by adding a missing one for swagger completeness - that's why I initially had it marked as "new API version" .
Here's a link to the s360 issues we are addressing with this PR
https://vnext.s360.msftcloudes.com/blades/unifiedplatform?blade=AssignedTo:All~KPI:6dc4e485-2d1b-449c-a224-30b183391437~SLA:1~Forums:All~_loc:UnifiedPlatform&def=&peopleBasedNodes=avishwan_team;maximpop_team&tile=S360_ServiceId:9537bbc3-8945-4a80-a398-9e894170cc28~_loc:__key__UnifiedPlatform__6dc4e485-2d1b-449c-a224-30b183391437&global=4:9537bbc3-8945-4a80-a398-9e894170cc28
Cc: @markcowl for awareness

yes, pretty sure here existing means 'publicly available' not 'documented in swagger' - as I see a lot of traffic in ARM for your RP and this apiversion

@varunkumta we are taking care of s360 alerts but not by changes to an existing API version, but by adding a missing one for swagger completeness - that's why I initially had it marked as "new API version" .
Here's a link to the s360 issues we are addressing with this PR
https://vnext.s360.msftcloudes.com/blades/unifiedplatform?blade=AssignedTo:All~KPI:6dc4e485-2d1b-449c-a224-30b183391437~SLA:1~Forums:All~_loc:UnifiedPlatform&def=&peopleBasedNodes=avishwan_team;maximpop_team&tile=S360_ServiceId:9537bbc3-8945-4a80-a398-9e894170cc28~_loc:__key__UnifiedPlatform__6dc4e485-2d1b-449c-a224-30b183391437&global=4:9537bbc3-8945-4a80-a398-9e894170cc28
Cc: @markcowl for awareness

yes, pretty sure here existing means 'already publicly available' not 'existing in swagger' - as I see a lot of traffic in ARM for your RP and this apiversion

Sounds good. Thanks for the review!

@ionuttulai We cna merge when the ci jobs have passed

@ionuttulai We cna merge when the ci jobs have passed

The pipeline has been running for almost 24 hours now. Is that expected, or is there a way to re-queue it?

@ionuttulai We cna merge when the ci jobs have passed

@markcowl It looks like the pipeline ran successfully but the results were not reported back to the PR.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=730156&view=results

@markcowl is there anything we can do to re-run the pipeline for the mandatory checks? It looks like it ran successfully but the results never made it back to the PR.

@ionuttulai Yes, we are looking at why the notifications did not make it back here

/azp run

/azp run

very latest (passing) run is here: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=736836&view=results


Add CSVNLinesSequenceRecordReader

Refer to this link for build results (access rights to CI server needed):
/job/datavec_PR/13/


It seems that cleanup removes /usr/local/etc/my.cnf.d

This still happens:
https://github.com/Homebrew/brew/issues/2792
Discussion was closed over a year ago, but it's still happening.

brew cleanup now runs brew prune which cleans out empty directories. https://github.com/Homebrew/brew/issues/2792#issuecomment-340260207 should solve the issue.

From the issue template:

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you do not read fill out the issue template repeatedly you will be blocked from ever submitting issues to Homebrew again.

It only removes that directory if it's empty. If it's empty and you created it manually: put a file in there. If it's empty and you didn't create it manually: reinstall the relevant formula.

Regarding the issue template:
I would have happily commented on the original issue but comments were locked on a bug that didn't get fixed. Plus, I didn't think the requested information was necessary since it it literally a duplicate.
On to the issue:
I know it removed the directory if it's empty.  I know the comment contains the fix.  That's not fixing the issue however.  brew prune, or brew cleanup if you prefer, causes a default, non-custom, working system to no longer work.  Providing the "documentation" to fixing it in github issue comments is hardly a fix.
The BUG is that brew prune breaks a properly installed (with no customizations) application and the fix is a hack only for those that have experienced the bug and come here to search for a fix.
On top of that, there is not necessarily a need to have a file in that directory, nor is it recommended to put one there upon installation.
Again, brew prune shouldn't break an application that is property installed without modification.
I don't believe I'm being unreasonable, but perhaps I am.  I don't frequent the GitHub repo for this project to track issues.  Is this not considered a bug?  Is this sort of thing common in dealing with various formulas?  I just don't understand why this is ignored as it seems like a fairly obvious problem.

I would have happily commented on the original issue but comments were locked on a bug that didn't get fixed.

It did.

I didn't think the requested information was necessary since it it literally a duplicate.

We always need the information.

Is this not considered a bug?

Correct. It's intentional that brew cleanup removes empty directories from HOMEBREW_PREFIX.

It did.

How is it that a brew command breaks a default install, and the "fix" is a comment on a github issue?  At the VERY least that should be in docs on the homebrew site.  What you have is not a fix at all.  Googling error messages and hoping someone else had the same issue is not a fix.

It's intentional that brew cleanup removes empty directories from HOMEBREW_PREFIX.

I get that.  The problem is that is has a side effect that it breaks a properly installed package with no indication that it was the problem.  The only saving grace is that homebrew is popular enough that people have posted this issue already and google deemed it search-result-worthy, but homebrew didn't "fix" anything!
What could a fix be?  Maybe have the package installer put a dummy file in that directory?  Have a warning on cleanup/purge that certain package are likely to break after running?

How is it that a brew command breaks a default install, and the "fix" is a comment on a github issue?

It's not. The fix was the formula was modified and, more recently, the bottle was rebuilt.

Maybe have the package installer put a dummy file in that directory?

It does.

If it's empty and you didn't create it manually: reinstall the relevant formula.

@cjf Did you do this?

I ended up recreating the directory and putting a dummy file in it myself.


add ex center calculator using edges and bring all calculator of triangle under one tab

…angle under one tab
fix #1397

Info about Issue or bug

fix #[issue number that will be closed through this PR]
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

Original
Updated

original screenshot
updated screenshot

Original

**

**

Updated

### first i add excenter using equation of edges

and bring all other calculator related to triangle in tringle calculator tab


Is presence=optional inferred when using sinceVersion?

In the context of adding a new field, the Message Versioning documentation (https://github.com/real-logic/simple-binary-encoding/wiki/Message-Versioning) states:

The new field should have its sinceVersion attribute set to be the version number that has been used for the new schema and its presence=optional attribute set.

I understand that newly added fields can only be optional.  I was therefore thinking that if sinceVersion was set on a field, then by definition that field must be optional.  I was wondering whether it was therefore a hard requirement to add "presence=optional" to the schema given that this can be inferred?

It is a hard requirement however it is not easy to enforce with the XSD 1.0. I think it is better to be explicit than have "magic" behaviour applied implicitly.

Thanks for the clarification.


TS: issues with private class properties with ref vs shallowRef for typed arrays

Vue version
3.5.11
Link to minimal reproduction
https://play.vuejs.org/#eNqNU99r2zAQ/leEnlJIHcrYS+YGutCHDbaVrm9RGKpzTtTJktDJWULw/76THP9YYWnBYPu+T3ff3X068Tvnsn0NfM7zAJXTMsBCGMbyJ8Cw3Cm9YfO91DXcCo47qbX9c+e9PArOZv8lbgDcmJXPRrnpFwuvXGAIoXZMS7OlMwEFJ1RVzvrAhqSltxUTPJul36hV8E8978S+HZdaIrJmxIwBYrHZjOXX122yGMuoyHDSQzll554eoRwydDWEKaxB0jnqm92OjuTn4qv1YrJaX/UFZWLakoWjg07has0mKCtogxJZ2EHUkC+uukL93KhKRF6lj4NsR7fgUxoYHSrVNntBa2h/p7gNwQtbOaXB/3BBUVLB5ywhEUu6v6ZYKTXCtAOKHRS/WyD4eoi/4CHGBH/wgOD3NJceC9JvIbTw/c/vcKDvHqzsptbEvgA+AlpdR5Et7XNtNqR7xEtyv6R1KbN9wvtDAINdV1FoZDaJn7a2vND7IPdD9jGdE6ahMXbGoAnCITmjSH7qfHUSPrKdV3vyb/d+8NbNGQZPwvq1GxtUQfvdycAUPdixzynqZ62K8+ufBBFPWjqLx+v49iW5aP5o3w2UyiStmKdBpAs6HxzZS6fWoQj4Tuc+Ay2GXNssJq9d+WsPPq6IOqA5Zzc3vPkLvgN7ng==
Steps to reproduce
Essentially the same issue as reported here: https://github.com/vuejs/language-tools/issues/4970 and was marked as upstream.
What is expected?
When using ref, if the given type is an array type of instances of a class with private properties, its type remains the same across it's usages.
What is actually happening?
When using ref with an array type, the iterable class type is unwrapped and it's private properties are lost, generating errors when that class type is expected, since they now do not match.
System Info
No response
Any additional comments?
No response

Closing as a duplicate of #2981. As a workaround, see: https://github.com/vuejs/core/issues/2981#issuecomment-1831724017

From what I understand, the limitation on unwrapping private fields is still present: Playground

From what I understand, the limitation on unwrapping private fields is still present: Playground

That might be so, but my question remains: why is unwrapping done when using array syntax and not when using single instance syntax? I.e.: why does ref<MyClass> map to type Ref<MyClass, whilst ref<MyClass[] maps to type Ref<{ ...unwrapped_MyClass }[]> instead of Ref<MyClass[]>?
The unwrapping seems to be the hardest, and not the easiest solution. If no unwrapping was done, I can't see how there would be any issue...

I.e.: why does ref<MyClass> map to type Ref<MyClass>

I’m not entirely sure I understand your question. Both cases involve unwrapping, as shown in the Playground example above:
class Foo {
  private foo = 1
}

const t1 = ref<Foo[]>([new Foo])
//     ^ Ref<{}[]>
const t2 = ref<Foo>(new Foo)
//     ^ Ref<{}>, not Ref<Foo>

The reason for unwrapping and the available workaround are explained in more detail in #2981. You might find it helpful to check that out.

I.e.: why does ref<MyClass> map to type Ref<MyClass>

I’m not entirely sure I understand your question. Both cases involve unwrapping, as shown in the Playground example above:
class Foo {
  private foo = 1
}

const t1 = ref<Foo[]>([new Foo])
//     ^ Ref<{}[]>
const t2 = ref<Foo>(new Foo)
//     ^ Ref<{}>, not Ref<Foo>

The reason for unwrapping and the available workaround are explained in more detail in #2981. You might find it helpful to check that out.

From what I understand, unwrapping is then used to provide the <template> section with "raw" types from the setup/definition section such that, for example, Ref<number> becomes number. I understand how this is done for the sake of being able to use the unwrapped syntax in the SFC's <template>.
What I don't understand is why unwrapping does not stop when it reaches a well-defined class type. I mean, in such cases, typing is definitive an clear, and no further unwrapping is required. Ref<MyClass> or Ref<MyClass[]> will never become anything else.
When initializing through the use of the ref( object ) method, I understand why it must attempt to deeply analyze the given object, when that object is of an arbitrary type, which can only be understood by analyzing it. However, when that object is from a well defined type or class, I don't understand the need to try and "destructure" said object into its constituents.
The type is already there. You're only trying to create a new unecessary (and sometimes wrong, as is the case) type.


fix: update CryptoJS and run npm audit fix

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea - #446
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #446 🦕

Updates CryptoJS's package.json version to ^4.2.0, resolving the CVE with it.
Relatedly, for development, there are several CVEs in the second-order dependencies of the dev tools. This runs npm audit fix to update those as well.

Thanks for this fix, @zackdotcomputer! Please resolve merge conflicts with a new commit and we'll get this merged.

@wangela No problem. I've merged the root repo's main into this branch and resolved the conflicts.


We will rename master to main on Thursday - May 20th

On May 20th we're going to rename the default branch in this repository to main. For more details, see our earlier announcement.

done


Add SQS queue name parameter to mosaic script

Fixed by https://github.com/azavea/raster-foundry-tiler/pull/9


build: turn on buildkit for everyone

seems like there are still problems?

@nicks just a weird test compatibility problem that I was confused by: I thought the output of a failed docker build was different between old engine and buildkit. What's actually happening is that in buildkit the output seems to differ between darwin and linux, whereas before it didn't. Should be good now.


feat: add World Chain to the Superchain Registry

Adding a New Chain
This PR adds World Chain to the registry.
Checklist

[x] I have declared the chain at the appropriate Superchain Level.
[x] I have run just validate <chain-id> locally to ensure all local validation checks pass.
[x] I have run just codegen to ensure that the chainlist and other generated files are up-to-date and include my chain.

https://github.com/ethereum-lists/chains/pull/5867

Alchemy has let me know that they're going to activate Granite on this chain this week. We should hold off on the merging this PR until we have the granite activation time in here. Functionally I think the order of operations is to:

Activate granite
Update the configuration file
Regenerate the registry artifacts with the just command
Update this branch with the latest
Validate the tests are passing
Merge

Public RPC URLs are correct now. Validation succeeds.


Fix compilation with swift legacy version.

It was impossible to compile the project after settings the build
settings SWIFT_VERSION=2.3.
There was one ambiguity on the dispatch_sync function calls. I simply
added an intermediate struct to be able to call it explicitely.
There was one conflict with the Objective-C selector atomic when we
wanted to make CKModifyRecordsOperation adopting the
CKModifyRecordsOperationType protocol.
I renamed it as atomicRecord.

Hi @yageek - sorry, what is your intent with this PR?

Okay - so, these changes are already on the swift/2.3 branch. If you need to submit now with Xcode 8, you can use that branch.
It will be released (probably today) as v3.4.0


Add de_dot function to log4j

Currently, we have problems with dots in keys coming from our JIRA application.  While the de_dot filter does exist, it has a performance penalty as outlined in Elastic's press release.  Below is an example of some MDC keys that are giving us issues.
{
                      "message" => "x.x.x.x o623x525x1 avs.soap [12/Feb/2016:10:23:32 +0100] \"POST http://z.z.z.z/rpc/soap/jirasoapservice-v2/login?in0=avs.soap&in1=**masked** HTTP/1.0\" 500 19587 0.0160 - \"Axis/1.4\" -",
                     "@version" => "1",
                   "@timestamp" => "2016-02-12T09:23:32.444Z",
                    "timestamp" =><PHONE_NUMBER>794,
                         "path" => "com.atlassian.jira.web.filters.accesslog.AccessLogFilter",
                     "priority" => "INFO",
                  "logger_name" => "com.atlassian.jira.web.filters.accesslog.AccessLogFilter",
                       "thread" => "http-apr-8180-exec-25",
                        "class" => "?",
                         "file" => "?:?",
                       "method" => "?",
             "jira.request.url" => "/rpc/soap/jirasoapservice-v2",
    "jira.request.assession.id" => "-",
          "jira.request.ipaddr" => "x.x.x.x",
              "jira.request.id" => "623x525x1",
                "jira.username" => "anonymous",
                         "host" => "y.y.y.y:50416"
}

Potential patch coming soon.

This plugin is deprecated for security reasons. More details, including a recommended alternative, available here: https://www.elastic.co/guide/en/logstash/current/plugins-inputs-log4j.html#_deprecation_notice


Add syntax highlighting for enum classes

Current highlighting of the included test file:

After this PR:

(Note that this branch includes the commit from #140, so I suggest you merge that one first.)

Hey @Wilfred, any chance you could resolve the merge conflict?

@PranayAgarwal of course! Done :)


Execute AWS Jenkins job for data sync complete

The data_sync_complete Jenkins job will have never been triggered in
integration since it has moved to AWS.

If this is working, the logic around the
trigger_data_sync_complete(_aws) jobs should be revisited as it is quite
messy (at least added to backlog/techdebt

solo: @schmie

This is the job that repoints URLs to environment specific ones, right, as well as some other stuff? :disappointed: :scream:

Not exactly - this trigger the job you're thinking of, which is defined in integration. Some of the repointing stuff also happens as part of the data sync process; but triggering the Data_Sync_Complete job on integration is necessary to do other post-processing, such as republishing tasks.

This has been finished on another branch by Ben. Closing.


Warning message "There is no application set to open the URL about:blank."

Every time I click on a conversation I get a warning message that reads "There is no application set to open the URL about:blank. Search the App Store for an application that can open this document, or choose an existing application on your computer."
This is the same kind of message id get if I was trying to open a file that didnt have an app to open it. I am just trying to click a new conversation, i'm not opening a file. It doesnt matter who's conversation I click on.
I have tried uninstalling the app, restarting the app, and logging out then in to the app with no success.
I get 2 of these messages every time I click a conversation and 3 on loading the app the first time.
See the warning message here:

dupe #126


Show add workspace modal in list header

Move the "add workspace" button into the list view header:

NOTE: This requires the following PR to be merged and published:
https://github.com/openshift/dynamic-plugin-sdk/pull/178
This will also cause conflicts with https://github.com/openshift/hac-infra/pull/25
It is assumed that https://github.com/openshift/hac-infra/pull/25 will be merged first.  To prepare for that, there are commented-out lines of code that will restore functionality where the user is taken to the details page after they create a workspace.

/hold

NOTE: ^^ tests will fail until #25 is merged.  #25 contains the code to update the dependencies.

/unhold


[LLC] Body-complex

Generate paging helper methods only when method group contains paging method.
Refactor code
Generate SDK for body-complex.json
Write test for it

Do you need to add the autorest call to generate the test code to generate file?

OK


Build should reap from aframe src

npm install
WARNING in ./~/aframe/dist/aframe.js
Critical dependencies:
1:479-486 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
@ ./~/aframe/dist/aframe.js 1:479-486

Sorry for delay in responding. We currently ship the dist because when projects using Browserify try to build A-Frame, they'd need to include all of our transforms and stuff.


Glamor's FontFace rule and Downshift seem to trigger a re-render of some sort

I'm making a custom dropdown with Downshift and Glamorous / Glamor. It's working really well, but I've ran into an issue which only seems to manifest itself when I'm using glamorous components (const DropdownList = glamorous.div(...)) as elements inside the downshift and I have fontFace rules to include a custom font.
The issue is that whenever you first load the page (haven't interacted with it) and then click the dropdown. My whole page seems to do a sort of flash. It looks like the fonts are being replaced or something. When I remove the FontFace rule everything seems fine and there is no flashing going on.
I've prepared a repo which has the same problem (see below). In this repo it's a bit harder to see because only the dropdown is using a custom font, so only that flashes when you first click it.
There's two possible workarounds for this;

Include the font-face rules in plain css (not through glamor)
Don't use glamorous components as children of Downshift (although i'm not sure if this fixes the problem entirely).

Repro:
https://github.com/thomhos/downshift-glamor-issue
Relevant versions:
"downshift": "^1.0.1",
"glamor": "^2.20.40",
"glamorous": "^4.4.0",
"react": "^15.6.1",

A bit more info. I don't think this is related to downshift. It also seems to happen when I switch routes, but it's harder to see because the flash almost happens the same time as the content is re-rendered. I do notice that each time when the flash happens, the network inspector shows my fonts are loaded again. Clicking through my app, the fonts are loaded 8 times by now.
It doesn't seem to be related to downshift, I suspect the style block is being re-rendered which triggers that flash of fonts.


apps/ble: Use store/config instead of store/ram

store/ram was deprecated
Now application are configured to use store/config and
BLE_STORE_CONFIG_PERSIST set to 0.

This https://github.com/apache/mynewt-nimble/pull/889 needs to be merged first to make CI work


Find usages in file

Allows to limit the find usages call to the current file. This will allow editors to implement a mark occurrences feature (highlighting all occurrences of the symbol under the caret)

Nice. Thanks!


bug: Date picker in webview for Android is not totally localized for french

Version
6.9.26
Platform(s)

[X] Android
[ ] iOS
[ ] Web

Current behavior
The date picker in the webview is not fully localized in french.

Expected behavior
Please localize also "Set" and "Clear". Ideally the date  picker would be the material one for the android implementation.
Reproduction
https://github.com/alainkr/cagiku
Steps to reproduce
Build the android app
launch
click on "show datepicker webview"
compare with
click on "show datepicker browser"
Other information
No response
Capacitor doctor
$ npx cap doctor
Capacitor Doctor
Latest Dependencies:
@capacitor/cli: 6.2.0
@capacitor/core: 6.2.0
@capacitor/android: 6.2.0
@capacitor/ios: 6.2.0
Installed Dependencies:
@capacitor/ios: not installed
@capacitor/core: 6.2.0
@capacitor/cli: 6.2.0
@capacitor/android: 6.2.0
[success] Android looking great! 👌
Before submitting

[X] I have read and followed the bug report guidelines.
[X] I have attached links to possibly related issues and discussions.
[X] I understand that incomplete issues (e.g. without reproduction) are closed.

Fastest way to fix this issue

[ ] I want to get this fix ASAP and found the issue with Algora we recommend ($50 to $500)

It looks like the date picker is an older version. Is there a way to configure inappbrowser to the Material datepicker.
I've seen https://stackoverflow.com/questions/77989551/why-does-datepicker-in-flutter-inappwebview-look-old  but could apply it.


Objects as maps: unknown props in values are unchecked

/* @flow */

type T = {};
type TMap = {[key: string]: T;};

// with explicit type cast everything is ok..
var x1: TMap = {prop: {}};
(x1.prop: T).unknownProp; // error: property unknownProp Property not found in object type

// conversely...

// dot notation
var x2: TMap = {prop: {}};
(x2.prop).unknownProp; // no errors!

// bracket notation
var x3: TMap = {prop: {}};
(x3['prop']).unknownProp; // no errors!

I also tried this:
/* @flow */

var x: {[key: string]: number;} = {abc: 1};
(x['abc']).prop; // no errors!
(x['abc']: number).prop; // error: property prop Property not found in Number

Is it a bug? Without an explicit type cast Flow does not infer x['abc'] to be a number.

I am able to repro this. It looks like the issue here is assigning an object literal to an object-as-map.
Here's some more code:
/* @flow */

function ex1() {
  var x: {[key: string]: number;} = {};
  x.abc = 1;
  var y: string = x.abc; // number incompatible with string
}

function ex2() {
  var x: {[key: string]: number;} = { abc: 1 };
  var y: string = x.abc; // no error
}

Similar question: should accessing a map member evaluate to a maybe expression?
The following code should typecheck but it doesn't:
let obj: {[key: string]: number} = {};
obj['a'] = 5;
let b: number = obj['b']; // b should actually be a ?number
let c = b * 10;


Update install guide with new numpy versions

Added that to the task list https://github.com/cupy/cupy/wiki/Actions-Needed-for-Dependency-Update

Update docs/requirements.txt to use the latest versions.

bumped docs requirements

Jenkins, test this please.

Jenkins CI test (for commit<PHONE_NUMBER>1db0fee3dc4413550081ae81d96561, target branch master) succeeded!

Please ignore the backport bot error

@asi1024 Failed to backport automatically.

Not cleanly cherry-picked

Jenkins CI test (for commit<PHONE_NUMBER>1db0fee3dc4413550081ae81d96561, target branch master) succeeded!


Make connection quality not too optimistic.

With score normalization, the quality indicator showed good under conditions which should have normally showed some badness.
So, a few things in this PR

Do not normalize scores
Pick the weakest link as the representative score (moving away from averaging)
For down track direction, when reporting delta stats, take the number of packets sent actually. If there are holes in the feed (upstream packet loss), down tracks should not be penalised for that loss.

State of things in connection quality feature

Audio uses rtcscore-go (with a change to accommodate RED codec). This follows the E-model.
Camera uses rtcscore-go. No change here. NOTE: THe rtscore here is purely based on bits per pixel per frame (bpppf). This has the following existing issues (no change, these were already there)

Does not take packet loss into account.
Expected frame rate is not available. So, measured frame rate is used as expected frame rate also. If expected frame rate were available, the score could be reduced for lower frame rates.

Screen share tracks: No change. This uses the very old simple loss based thresholding for scoring. As the bit rate varies a lot based on content and rtcscore video algorithm used for camera relies on bits per pixel per frame, this could produce a very low value (large width/height encoded in a small number of bits because of static content) and hence a low score. So, the old loss based thresholding is used.

Things to watch for

Connection quality - how closely does it match user experience?
Scores will not be 5.0 anymore, but that does not mean connection is not excellent.

Needs more work. The default video score will return 3.8 (under excellent conditions) because of the rtc score model for video.


Can not set mappings between popup and status after recent breaking change

Description
Neogit reports that there are duplicate mappings, since instead of overriding them it tries to merge with the defaults which is bad imo. So for example i would like to have both x and X keys open two different popups, but since x is already taken by default in the status mappings map, i get this error.  Please allow us to completely override the default mappings, we might want to even disable certain ones, instead of merging them with the defaults.
E5108: Error executing lua: .../packages/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: vim/shared.lua:0: key found in more than one map: x
stack traceback:
[C]: in function 'error'
.../packages/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
.../packages/start/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
.../packages/start/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
.../packages/start/plenary.nvim/lua/plenary/async/async.lua:108: in function 'run'
.../share/nvim/site/pack/packages/opt/neogit/lua/neogit.lua:103: in function 'open'
/home/asmodeus/.config/nvim/lua/plugin/neogit.lua:9: in function 'open_vcs_element'
/home/asmodeus/.config/nvim/lua/user/actions.lua:1049: in function 'open_vercontrol_view'
/home/asmodeus/.config/nvim/lua/user/command.lua:1959: in function </home/asmodeus/.config/nvim/lua/user/command.
lua:1958>
Neovim version
0.9.4
Operating system and version
ubuntu
Steps to reproduce
        mappings = {
            finder = {
                ["<cr>"] = "Select",
                ["<esc>"] = "Close",
                ["<c-j>"] = "Next",
                ["<c-p>"] = "Previous",
                ["<tab>"] = "MultiselectToggleNext",
                ["<s-tab>"] = "MultiselectTogglePrevious",
            },
            popup = {
                ["?"] = "HelpPopup",
                ["i"] = "IgnorePopup",
                ["b"] = "BranchPopup",
                ["p"] = "PushPopup",
                ["f"] = "FetchPopup",
                ["r"] = "RebasePopup",
                ["l"] = "LogPopup",
                ["z"] = "StashPopup",
                ["D"] = "DiffPopup",
                ["P"] = "PullPopup",
                ["c"] = "CommitPopup",
                ["C"] = "CherryPickPopup",
                ["x"] = "RevertPopup",
                ["X"] = "ResetPopup",
                ["m"] = "MergePopup",
                ["M"] = "RemotePopup",
            },
            status = {
                ["<c-r>"] = "RefreshBuffer",
                ["<c-v>"] = "VSplitOpen",
                ["<c-x>"] = "SplitOpen",
                ["<c-t>"] = "TabOpen",
                ["<esc>"] = close_git_view,
                ["<enter>"] = "GoToFile",
                ["<tab>"] = "Toggle",
                ["n"] = "InitRepo",
                ["s"] = "Stage",
                ["S"] = "StageUnstaged",
                ["u"] = "Unstage",
                ["U"] = "UnstageStaged",
                ["d"] = "DiffAtFile",
                ["R"] = "Discard",
                ["I"] = "InitRepo",
                ["L"] = "CommandHistory",
                ["}"] = "GoToNextHunkHeader",
                ["{"] = "GoToPreviousHunkHeader",
            },
        },

Expected behavior
No errors
Actual behavior
Error is observed opening the git status.
Minimal config
See above.

Cool, I knew I'd see stuff like this. The end goal is to make things more flexible for everyone, but the path to getting there is... bumpy.
Anyways, thanks for the reproduction config. I'll try and sort this out asap.

Not working on master/latest changes, tried that before posting this issue - @star-szr

Maybe a config switch to disable all built-in keybindings would help?
oil.nvim example:
use_default_keymaps = true,

I... I love the simplicity. Done. https://github.com/NeogitOrg/neogit/pull/926

Though I do think using false should work for this use case too. I haven’t had a chance to dig into the code but I’m imagining we could remove all mappings set to false from the defaults before merging.

Easy, too. Great ideas :)

Hi, I'm sorry..
Did that work for anybody??

Really hope so. Is stuff broken for you?

Yeah, suddenly i'm getting the following:

But, now that i look at it closer maybe it is not related to this issue here.
Something about Vim(sign):E155: Unknown sign: NeogitOpen:section

Looks unrelated. I'll close this, and do you wanna open a new issue with your config?

Actually, im still getting the OP error.
My use_default_keymaps was set to false, but when I set it to true the error is there and renders Neogit unusable.


Horizontal REPL / Vertical Split

Hello Zach, I bought Nightcode from AppStore, how do I split the REPL side by side with the editor vertically??
Thanks

You can edit nightcode.edn and save it to ~/Library/Containers/info.oakleaf.nightcode/Data/nightcode.edn. That's the special home directory for the MAS version of Nightcode.

Let me know if that doesn't work...I haven't tried it =)

Hi Zach, thanks. I have tried it, it doesn't work. :((

OK I'll take a look soon.

Sorry for the delay. I just tested it and it does indeed work. Please make sure that you put the file in the right place, and that you edited it so it says :panel :horizontal.

Thanks, it does work. :+1:


Copy Selected Header/Headers

Hi,
Can you add new item "Copy Selected Header/Headers" to the menu ? When you will choose this item, only the name of column selected header will be copy and separated by commas -> next you can paste this string to the your new query (etc. after select).
Picture:

Thanks!

Yeah, this is a very old feature request. Time has come.


Inconsistent logical volume files

Describe the bug
Version: 2.08
Deployed 1 master, 3 volume servers and 1 filer with defaultReplication=001 and a scheduled script that fixes replication every 20 minute. One day a volume server was accidentally down for more than 20 minutes. During the downtime, some files were uploaded via filer. Later when the down volume server came back, the files uploaded during the downtime cannot be downloaded with filer randomly, reporting 404 error.
All filer operations are using HTTP API.
System Setup
A minimal reproduction can be done by following steps:

Start one master server with weed master -defaultReplication=001.
Start 3 volume servers with weed volume -max=1 -dir=/tmp/weed{0,1,2} -port={8080,8081,8082}.
Start 1 filer with weed filer.

Wait for several minutes for the cluster to be steady and upload a file. Running volume.list with weed shell should see 3 volume servers with 2 of them having a logical volume each. And the file count should not change for a while.
 Run volume.fix.replication with weed shell. Now the shell should see 2 running volume servers with the logical volume before. Now upload another file with different file name.
Restart the killed volume server. Now the cluster is in a inconsistent state that the logical volumes have different file counts. Restart the other two volume servers and try to get the second file uploaded with filer. Now you should see 404 Not Found error.
Expected behavior
The uploaded file should be retrieved without errors because the file does exist on the other two volume servers.

What's worse, if the other two volume servers are permanently down afterward, the second uploaded file would be LOST.

there is a plan to fix missing files on read.

I think fix.replication will start after and random delete Volume 1 from Servers 8080-8082.
When deleting a volume, it can look at modified_at_second

Added more logic to pickOneReplicaToDelete by compact revision, modified time, and file size.


34 fix release pipeline bug

figure out why the manylinux wheels cannot be uploaded to PyPI

made "twine upload" check for both the python version and the manylinux build env tags when uploading
-> let's see if "twine upload" just failed because it got ambigious file names


report_error refactoring

This refactor will help me a lot to change get_matches_with to return Result.
Also it is good for same code deletions.
Only I'm not sure with module and enum name, so waiting for your suggestions before merge ;)

Looks like a good start! I'd re-name the error enum to something like ClapError (or similar??) though because ArgNames confused me at first. And there are also errors that may not be related to args, or down the road there could be.  Then we can also implement std::error::Error

there is a big problem with Error trait. I tried to do it, but for now reports using huge bunch of App code, it is unattainable from Display trait, which is must-have if you implement Error

I have some ideas how to solve this in non rust ideology, but it is non goal for us, I think

Resolved

Very nice!


Setup REST Backend

[x] Clone and run Spring PetClinic REST
[x] Authenticate as admin/admin
[x] Use Swagger to get test data through API

git clone ...
cd ...
mvn spring-boot:run
http://localhost:9966/petclinic/swagger-ui.html


Fix up #172

Fixes two tests that are failing after the merge of #172, and implements the bit of polish discussed in https://github.com/babel/babylon/pull/163#pullrequestreview-4321611.

Current coverage is 94.52% (diff: 100%)

No coverage report found for master at 3525c00.

Powered by Codecov. Last update 3525c00...3c9d7fe


remove ImageCore as a dep

If we add maxabsfinite to utils, we can depend on ImageCore only in tests (no need for full blown Images)

If we add maxabsfinite to utils, we can depend on ImageCore only in tests (no need for full blown Images)
Yeah, I thought about that too. I'll give it a go


pd/client: report approximate_keys instead of approximate_rows

What have you changed? (mandatory)
This PR will report the approximate number of keys in write cf instead of rows in the region during the heartbeat.
It's prepared for controlling the region by both the number of keys in write cf and size of the region.
What are the type of the changes? (mandatory)

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested? (mandatory)
unit tests
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
no
Does this PR affect tidb-ansible update? (mandatory)
no
Refer to a related PR or issue link (optional)
https://github.com/pingcap/tikv/pull/3159
@overvenus @huachaohuang PTAL

LGTM. Please update the PR comment.

PTAL @huachaohuang


bump-formula-pr: even more precise tag replacement

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

If in a formula tag matches version, then bump-formula-pr with --version argument fails:
% brew bump-formula-pr --version 2022-07-22  --debug exploitdb
...
==> replace /2022-07-12(?=")/ with "2022-07-22"
==> replace "d84f857e94f91c71fcb93041483f661d29023c1e" with "46346f8944f5d01e09a8ed3d78e34cf759697b47"
==> replace "version \"2022-07-12\"" with "version \"2022-07-22\""
Error: inreplace failed
/opt/homebrew/Library/Taps/homebrew/homebrew-core/Formula/exploitdb.rb:
  expected replacement of "version \"2022-07-12\"" with "version \"2022-07-22\""
/opt/homebrew/Library/Homebrew/utils/inreplace.rb:89:in `inreplace_pairs'
/opt/homebrew/Library/Homebrew/dev-cmd/bump-formula-pr.rb:311:in `bump_formula_pr'
/opt/homebrew/Library/Homebrew/brew.rb:93:in `<main>'

Version got replaced by the first replacement pair (for the tag), and it failed to be replaced on the third one (for version).
Closes https://github.com/Homebrew/brew/issues/13596

Review period will end on 2022-07-25 at 13:28:24 UTC.

Review period ended.


Added Breadth First Search Algoirthm

Breadth First Search Algorithm is Added in this Commit.

@yash-gulatii, I would like to know more about the use and work of this algorithm

It is a Tree Traversal Algorithm used to Print all the elements present in a Tree Data Structure.


add arrow indication

Hey @rawlinxx 👋
I've rebased your PR on last master and merged it (7a5954a) ✅
Thanks a lot for contributing to this project! 🙏