Support for Canvas Devices

Anything related to future support for Canvas Devices and all relevant updates/discussions will be posted here. If you have a canvas device and would like to help test canvas support I'd appreciate it as I don't own a canvas device.

In https://github.com/jaxcksn/nanoleafMusic/commit/20e4d0ad1d52278dd812d172ae1ea921ee8fea57 on the dev branch, I replaced the Nanoleaf Aurora dependency with my own package I made specifically for this program. (It's very similar, but only with the features I need).
This should make it easier to implement Canvas support.

In https://github.com/jaxcksn/nanoleafMusic/commit/20e4d0ad1d52278dd812d172ae1ea921ee8fea57 on the dev branch, I replaced the Nanoleaf Aurora dependency with my own package I made specifically for this program. (It's very similar, but only with the features I need).
This should make it easier to implement Canvas support.

In https://github.com/jaxcksn/nanoleafMusic/commit/163282977a02278cb3ac175557d24e4044808866 I added two built release binaries for Canvas support if you would like to test. They should work in theory, but I have no way to test if it does:
For Windows: Download Here
For macOS: Download Here

In https://github.com/jaxcksn/nanoleafMusic/commit/163282977a02278cb3ac175557d24e4044808866 I added two built release binaries for Canvas support if you would like to test. They should work in theory, but I have no way to test if it does:
For Windows: Download Here
For macOS: Download Here

In 1632829 I added two built release binaries for Canvas support if you would like to test. They should work in theory, but I have no way to test if it does:
For Windows: Download Here
For macOS: Download Here

Tested - works perfectly as far as I can tell!
One thing which I don't know if it's supposed to happen is that after the first setup of my canvas panels - which showed up immediatly in the device selection - and I saved as a reconnect, and then after closing the software, it wouldn't show up again in the selection window. Is this a bug or due to it already being saved as the reconnect it doesnt put it in available connections? Reconnecting worked fine!

In 1632829 I added two built release binaries for Canvas support if you would like to test. They should work in theory, but I have no way to test if it does:
For Windows: Download Here
For macOS: Download Here

Tested - works perfectly as far as I can tell!
One thing which I don't know if it's supposed to happen is that after the first setup of my canvas panels - which showed up immediatly in the device selection - and I saved as a reconnect, and then after closing the software, it wouldn't show up again in the selection window. Is this a bug or due to it already being saved as the reconnect it doesnt put it in available connections? Reconnecting worked fine!

Edit 2: Turns out that when reconnecting, it doesnt reconnect properly. I needed to press and hold power to open device connections after pressing reconnect, even when the software said it was connected successfully, otherwise it didnt show any lighting effects. Not sure if there's a way around this, but maybe an updated popup/instructions saying to do that, or listed in troubleshooting would work.

This is definitely a bug. I'll create a issue for it and work on it when I get the chance. It'll be patched before version 1.2 is realized.
I appreciate your help!

Edit 2: Turns out that when reconnecting, it doesnt reconnect properly. I needed to press and hold power to open device connections after pressing reconnect, even when the software said it was connected successfully, otherwise it didnt show any lighting effects. Not sure if there's a way around this, but maybe an updated popup/instructions saying to do that, or listed in troubleshooting would work.

This is definitely a bug. I'll create a issue for it and work on it when I get the chance. It'll be patched before version 1.2 is realized.
I appreciate your help!

Edit 2: Turns out that when reconnecting, it doesnt reconnect properly. I needed to press and hold power to open device connections after pressing reconnect, even when the software said it was connected successfully, otherwise it didnt show any lighting effects. Not sure if there's a way around this, but maybe an updated popup/instructions saying to do that, or listed in troubleshooting would work.

This is definitely a bug. I'll create an issue for it and work on it when I get the chance. It'll be patched before version 1.2 is realized.
I appreciate your help!

Just tested on mac, the bug is not present there, reconnecting works like a dream.
The other thing I noticed on Windows in relation to the bug where it stops playing anything is that it happened pretty regularly as a song finished - it wouldnt play lights for the next song until I reloaded effects. Again, doesn't seem to happen on mac.

Edit 2: Turns out that when reconnecting, it doesnt reconnect properly. I needed to press and hold power to open device connections after pressing reconnect, even when the software said it was connected successfully, otherwise it didnt show any lighting effects. Not sure if there's a way around this, but maybe an updated popup/instructions saying to do that, or listed in troubleshooting would work.

This is definitely a bug. I'll create an issue for it and work on it when I get the chance. It'll be patched before version 1.2 is realized.
I appreciate your help!

Just tested on mac, the bug is not present there, reconnecting works like a dream.
The other thing I noticed on Windows in relation to the bug where it stops playing anything is that it happened pretty regularly as a song finished - it wouldnt play lights for the next song until I reloaded effects. Again, doesn't seem to happen on mac.


Optional Automatic Purging

Provide the ability to retain the last N builds per-repository (e.g. last 50 builds). When a new build is created the build history is pruned and older builds are deleted from the database. This will be an optional, opt-in feature, and N will be configurable.

What is the current behavior? Are all build records kept indefinitely?

What is the current behavior? Are all build records kept indefinitely?

That's currently the case yeah

Would it be possible to also say date as metric? On a system with a lot of builts - it might not reflect the history as much as saying - keep builds for X amount of days

Maybe it's a good idea to also add a special pipeline step related to this? Maybe using the "when: event:" syntax. It could be useful to clean up build artifacts, e.g. delete a docker image from the docker registry. Obviously, someone (most likely the .drone.yml author) needs to take into account that some pipeline steps might have failed, so it's possible there are no artifacts to delete.
If drone keeps track of which "build" is currently deployed in at least one environment, it would be nice to be able to exclude those builds from automatic purging.

The plan is to expose a DELETE /api/repos/{owner}/{name}/builds endpoint with a few different query parameters to control the purge behavior. ?before={number} will purge builds before the given build number, and ?retain={number} with retain the last N builds.
This will let you setup some sort of regular cron task to purge builds, or they use the global webhooks for event-driven purging.
This approach is in line with our philosophy of supporting advanced functionality through plugins and extensions, while keeping Drone core simple and focused.

purge endpoint shipped in 1.0

@bradrydzewski hi ,I am new drone user, and I have 5G sqllite database,I find all drone doc. but not find this purge endpoint,  can you tell me ,how to use it? thank you every much

该计划是公开一个DELETE /api/repos/{owner}/{name}/builds带有几个不同查询参数的端点来控制清除行为。?before={number}将清除给定构建号之前的构建，并?retain={number}保留最后的N构建。
使用此端点，您可以创建常规 cron 任务来清除构建，使用全局 Webhooks 进行事件驱动的清除，或者提出根据您的使用和保留要求进行优化的您自己的独特逻辑。
这种方法符合我们通过插件和扩展支持高级功能的理念，同时保持 Drone 核心简单和专注。

I find this doc,https://docs.drone.io/api/builds/build_stop/ ,but this is stop ,not purge log , please help me ,I dont' find the resolve method~


Invalid types with graphql 15.x

node_modules/@giraphql/core/lib/plugins/merge-plugins.d.ts:14:131 - error TS2707: Generic type 'GraphQLFieldResolver' requires between 2 and 3 type arguments.

14     wrapResolve(resolve: GraphQLFieldResolver<unknown, Types['Context'], object>, fieldConfig: GiraphQLOutputFieldConfig<Types>): GraphQLFieldResolver<unknown, Types["Context"], object, unknown>;
                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@giraphql/core/lib/plugins/merge-plugins.d.ts:15:147 - error TS2707: Generic type 'GraphQLFieldResolver' requires between 2 and 3 type arguments.

15     wrapSubscribe(subscribe: GraphQLFieldResolver<unknown, Types['Context'], object> | undefined, fieldConfig: GiraphQLOutputFieldConfig<Types>): GraphQLFieldResolver<unknown, Types["Context"], object, unknown> | undefined;
                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@giraphql/core/lib/refs/builtin-scalar.d.ts:4:11 - error TS2315: Type 'GraphQLScalarType' is not generic.

4     type: GraphQLScalarType<unknown, unknown>;
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 3 errors.

It seems like types are generated for graphql@16, if this library supports graphql@15 then typing should be properly generated for that version

Thanks for reporting this!
Unfortunately I don't know of an easy fix.  Graphql@15 should work, bit the types are incompatible.
The easiest workaround on your end would probably be to enable the skipLibCheck option in your tsconfig.  I know this isn't always a possible or desirable, so I'll spend some time investigating if there is a way to work around this on my end.   Unfortunately there often isn't a lot you can do (other than adding lots of explicit casts to any) to bridge breaking changes in types like this.
Out of curiosity, are there things keeping you from upgrading to graphql 16?

Thanks for quick response, I am aware of skipLibCheck but I am trying to avoid that. For now I have downgraded to<EMAIL_ADDRESS>version.

Out of curiosity, are there things keeping you from upgrading to graphql 16?

I am using apollo server, dependency tree currently requires graphql@15
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ │ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ │ └──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped invalid: "^14.2.1 || ^15.0.0" from node_modules/apollo-server-core/node_modules/apollo-graphql
│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>

Can you try the latest version of GiraphQL with the latest version of graphql@15 (15.7.2).  I manually fixed places that were incompatible with the 15.7.2, I think some earlier version of 15 have additional incompatibilities.  It's not a great long term solution, but should be good enough until more of the graphql eco-system has been updated to support graphql@16

I tried with
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
Still gives same typing error
node_modules/@giraphql/core/lib/plugins/merge-plugins.d.ts:14:131 - error TS2707: Generic type 'GraphQLFieldResolver' requires between 2 and 3 type arguments.

14     wrapResolve(resolve: GraphQLFieldResolver<unknown, Types['Context'], object>, fieldConfig: GiraphQLOutputFieldConfig<Types>): GraphQLFieldResolver<unknown, Types["Context"], object, unknown>;
                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@giraphql/core/lib/plugins/merge-plugins.d.ts:15:147 - error TS2707: Generic type 'GraphQLFieldResolver' requires between 2 and 3 type arguments.

15     wrapSubscribe(subscribe: GraphQLFieldResolver<unknown, Types['Context'], object> | undefined, fieldConfig: GiraphQLOutputFieldConfig<Types>): GraphQLFieldResolver<unknown, Types["Context"], object, unknown> | undefined;
                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/@giraphql/core/lib/refs/builtin-scalar.d.ts:4:11 - error TS2315: Type 'GraphQLScalarType' is not generic.

4     type: GraphQLScalarType<unknown, unknown>;
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 3 errors.

I don't see any change for offending file refs/builtin-scalar.ts in https://github.com/hayes/giraphql/commit/c6aa73276d596585a5d15115f91579a60385cd25, I don't think this can be fixed without breaking support for graphql@16.
If you want you can close this issue, I'll update to latest version when apollo-server supports graphql@16

I have reported this issue to apollo-server repository https://github.com/apollographql/apollo-server/issues/5941, hopefully it will be resolved soon

Closing this issue as<EMAIL_ADDRESS>now supports graphql@16

Closing this issue as<EMAIL_ADDRESS>now supports graphql@16


Add more test users with grant data and use new images

This PR includes changes introduced in PR(https://github.com/OA-PASS/pass-docker/pull/61), update so new images should include all changes from master
Testing
First and foremost, all recent changes in master must still work:

Deposit services must work!

This PR adds three new test users with grants attached. New usernames to be used to login to PASS:

nih-user
ed-user
usaid-user

I have tested locally. Deposit service seemed to work, as described in PR (https://github.com/OA-PASS/pass-docker/pull/55).
I was able to login using all three of the added users and  see appropriate grants for each.


[Don't Merge, Service roll out 2/20/2018] Swagger For new rdbms API change for new biz model

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] This is a redo of previously signed-off pull request https://github.com/Azure/azure-rest-api-specs/pull/2207. The main change is we will still release the API as preview. Structure the folder following the guidance @ https://github.com/Azure/azure-rest-api-specs/wiki/December-2017-Refactoring#stable-and-preview.
Also, we took out the VirturalNetworkRules which still in private preview.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

This commit was treated and no generation was made for Azure/azure-sdk-for-python

Did a commit to Azure/azure-sdk-for-go:
https://github.com/Azure/azure-sdk-for-go/commit/0a2273a40869a88a792b82357a8a7b409b5a8898

Automation for azure-sdk-for-python

Did a commit to Azure/azure-sdk-for-go:
https://github.com/Azure/azure-sdk-for-go/commit/fe01c725182660b5a6bff865fb7a72d301e6e745

This commit was treated and no generation was made for Azure/azure-sdk-for-go

This commit was treated and no generation was made for Azure/azure-sdk-for-go

Automation for azure-sdk-for-go

@marstr I've corrected all errors in the job you mentioned. https://travis-ci.org/Azure/azure-rest-api-specs/jobs/338866706.

@johanste  @NiklasGustafsson  - have folks from azure api review board seen this? Please review if not already.

@ravbhatnagar says:
@johanste @NiklasGustafsson - have folks from azure api review board seen this? Please review if not already.

I reached out to @johanste offline to get advice on how to proceed here.

Looks good.

Once the 20th rolls around, I'll remove the DoNotMerge label, and ping @QingqingYuan about whether or not the service team is ready for this to be merged.

I got word from @QingqingYuan that this has been delayed until the 28th.

I just got word from @QingqingYuan that the service is now available.


Migrate all the Log.(x) instructions to use Timber.(x)

Haha, Google! "Use Timber, not Log". So funny, much humour.
Timber is Log, but automatically switches off for release builds, so all the if (BuildConfig.DEBUG) can be removed.
It should also shrink the APK size a fraction too.

Also migrate all the System.out.println(...); and if (BuildConfig.DEBUG) e.printStackTrace(); to use Timber.e(TAG, e.printMessage()); as appropriate

Task Update Feb 2,

Replaced all Log.x, System.out.println() and If (BuildConfig.Debug) e.printStacktrace() to use Timber.x.


Upgrade to Laravel 5.8.x

@cretueusebiu thanks for this repo...it's much needed!
Can we upgrade to Laravel 5.8.x?

I hope I can release a new version this week with everything up to date.

Great thanks @cretueusebiu. I hope to keep using this repo, appreciate you keeping it up to date.
By the way, this is off-topic, but would it be possible to have a laravel + nuxt example with social login/authentication using socialite (for one of google, facebook, linkedin, twitter as an example)?

2.0 has been released!

Awesome, thanks! Look forward to trying it out


Spring Petclinic organization

Brian Dussault, the Director of the Spring engineering team, asked me to move the angularjs branch to another repository, outside of the spring-projects organisation that will be reserved to Pivotal employees.
I've created a brand new GitHub organisation called spring-petclinic. You will find the spring-petclinic-angular1.
The  spring-petclinic organisation has been created to host Spring Petclinic forks. Spring community members could have direct commit rights on it.
We may imagine other projects for React, Angular 2, Spring Cloud and so on. @nilshartmann, @mszarlinski you may take the lead on it.
Feel free to join this organisation by asking trough this issue.

Ok, I would like to push forward with AngularJS and Spring Cloud version. My goal is to polish AngularJS branch and setup a distributed version on top of it ✌On the other hand, I'm not familiar with ReactJS and I wonder how to reconcile that branch with upcoming Spring Cloud version.

@mszarlinski I've invited you to the spring-petclinic organisation. Once accepted, I could give you permission to the spring-petclinc-angular1 project. You may work with feature branch and pull request or with direct commit, as you prefer.
For ReactJS, I was thinking about  @nilshartmann who already have a private repo.

Hi,
even my React branch/fork is still heavy work in progress with a lot of improvements I'd be more than happy to share the code in this new organization.
Regards,
Nils

Nils, I've just invited you to the spring-petclinic organisation. I've proposed too to David Syer.

Hi Antoine, thanks for the invitation. Should I add a "spring-petclinic-reactjs" project with my reactjs branch?

Yes you cloud. I think it will have a better visibility and you may be help by the community.

I've added the new repository. Thanks again for your invitation!

Hello @arey is that still a thing? I found this link to this PR on your blog, didn't see any other mention in the READMEs as to how to join (is there an official way to ask, or someone specific to contact?).
I forked the Spring PetClinic to make it use htmx, see: agrison/spring-petclinic-htmx and would be interested to know if it could be included there?
Some may also eventually want to participate and improve it.

It's still a thing, and the HTMX version sounds interesting. Antoine might not see your comment unless you try and ping him directly (he's the org owner and therefore the only person who can invite you AFAIK).

Thank you for your answer @dsyer, much appreciated.
I will send him an email directly then.

@agrison I've just answered to your email. Thanks for your contribution :)
@dsyer do you want I add you as owner of the org? For safety, I think it would be more appropriate to have two members in this role.

Sure, thanks.


Updates to address issues 64, 65 (chapter 9)

cc @osman-koyuncu-qualcomm @atishp04

Apart from the above nit: lgtm.


xscreensaver: Enable perl modules needed for RSS image fetch (#57629)

(cherry picked from commit<PHONE_NUMBER>6056fb3a01ee6e9a9c3ee476a928e1)

Ouch wrong branch?


MB-4626 don't prefill move type and disable next btn if unselected

Description
On the Select Move type page, no option should be selected when the page loads. Currently, if a shipment has been created, the type of move will be pre-selected when the user goes to the select page. The user should also not be able to select "next" if no type has been selected.
Acceptance criteria:
GIVEN I am a SM with a at least one shipment already on my move
WHEN I am on the Shipment Selection screen
THEN I should not see any of the shipment types pre-selected
AND THEN I should not be able to click on the NEXT button until I have selected a shipment type
NEXT button will remain grayed out until a shipment type has been selected
No radio is selected upon arrival on the page
Setup
Run the app and log in as either hhg unsubmitted or nts user type in local sign in. You can also create a move with any shipment option manually.
On the review page, select "add another shipment". Verify that no move type is pre-selected when you are routed to the select move type page, and the next button is disabled. Select a shipment - verify that the next button is enabled and you are able to go through and add another shipment. Test with multiple/different shipment types.
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Messages

:book:
:link: MB-4626

  Generated by :no_entry_sign: dangerJS against 76794cbe62ea88a36d39d7bf03991e549cb3dca9


Add result collector for chain activator

Collect result of each requested activator (eg. for logging, profiler etc).

I close this issue. After rethinking this idea would complicate the feature handling.


Channel ordered monitor

Add function argument for monitor creation to allow grouping of parameters according to channels rather than instrument. Specifically, group according to parameter.instrument instead of parameter.root_insturment. Default behavior is the current behavior with sorting by root_instrument.
Code has been tested on qcodes version 0.30.0 on one system.
Potentially it could be nice to be able to pass in a manual sorting by allowing direct input of the parameter dictionary rather than going through _get_metadata.

bors merge


fix #626 Microsoft.Azure.Functions.Worker.Extensions.OpenApi throws System.IO.FileNotFoundException

This addresses the #626 so the behavior of Microsoft.Azure.Functions.Worker.Extensions.OpenApi matches Microsoft.Azure.WebJobs.Extensions.OpenApi.
After the change I could confirm the migrated project can safely skip attempting to load unused types.

@justinyoo I see you were the latest active MS staff in here. Any chance you could look at this? This project is failing for .NET 8 projects.

Unfortunately, the project's limited recent development has led to challenges, including compatibility issues with the latest Azure Functions worker/isolated packages and Asp.Net integration. This situation is particularly challenging as we rely on this project for our Serverless APIs.
Moreover, it's disappointing to observe that Microsoft is advocating for Azure Functions in Serverless API development. This underscores the importance of reassessing our current strategy, especially considering the reported difficulties in the smooth integration of various Microsoft services.


Handling of missing data in tables

As mentioned here.

Thanks for creating this issue. This is partially supported right now, e.g. see https://github.com/Deltares/Ribasim/blob/ed4fbefdc23d0c62ca84939a7f9e6b055f5a1f0b/core/src/utils.jl#L198, where we ignore NaN values when updating the forcing.
Both GeoPackage and Arrow have a general concept of missing data, separate from NaN which only exists for floats, and therefore is not an option for optional string fields like control_state. In julia NULL is normally encoded as missing, so a float that can be missing is Union{Float64, Missing}. So probably we should use that for everything that is allowed to be missing, unless there are other downsides compared to using NaN.

@visr I guess this issue is solved now?

I don't think so. It's gotten better with your implementation of defaults in the julia core, but we still need testing and a clear story on how we handle optional data across ribasim-python and the core.

I think this can be closed now. Occasionally we adjust this a bit like in #1493. One thing worth adding is that we should always use NULL / missing rather that NaN in out input data.


As a developer, I want to be able to query augmented L2_HR_PIXC and PIXCVec metadata (cycle, pass, scene ID) in CMR UAT POCUMULUS so that I can get list of L2 products

PR opened on cmr-graphql per @frankinspace's suggestion
https://github.com/nasa/cmr-graphql/pull/36

PR merged; blocked until 1/25 when CMR pushes changes to UAT

Swodlr PR ready for CMR UAT deployment; https://github.com/podaac/swodlr/pull/42

Closed with merge of #42


Solarweave Explorer Integration

Key Features
This pull request implements Solarweave in a completely unobtrusive way. It has automatic fallback compatibility to the original implementation. Therefore, no actual cache from Solarweave needs to be present for the Explorer to work. However, it will try to query Solarweave first.
Please note that when retrieving blocks by slot and blockhash will not work unless an existing Solarweave Cache is implemented.
Search by blockhash and slot
You can now search for blocks using slots:

You can also search for blocks by using blockhashes:

The new block page
The new block page showcases an overview of the block as well as all the transactions in the block.

If an invalid block is inputted. It will simply just display this page.

Custom Solarweave Cluster Info
If you wanted to retrieve data from a custom Solarweave Database you can use the updated Cluster Info page as seen here.

Full fallback compatibility
There is automatic fallback compatibility for the original block explorer. This means that even if there is no Solarweave cache. The Explorer will still work as intended. Just remember that block pages will not work if there is no Solarweave cache.
Other notes

Block History does not use Solarweave. Please see updates on: https://github.com/ArweaveTeam/arweave/issues/268 if considering using Arweave for Block History in the future.

Awesome, I'd love to dig through this but could you please open a PR on the monorepo https://github.com/solana-labs/solana instead? This repo is just a mirror

@jstarry, just created this pull request! Cheers!
https://github.com/solana-labs/solana/pull/12750


Datesearch: test broken

Recent log:
./api_datesearch_test.py
**********************************************************************
File "./api_datesearch_test.py", line 66, in __main__.test_bad_datesearch
Failed example:
    test_bad_datesearch()
Exception raised:
    Traceback (most recent call last):
      File "/opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/doctest.py", line 1337, in __run
        compileflags, 1), test.globs)
      File "<doctest __main__.test_bad_datesearch[0]>", line 1, in <module>
        test_bad_datesearch()
      File "./api_datesearch_test.py", line 82, in test_bad_datesearch
        assert r.text == str(msg)
    AssertionError
**********************************************************************
File "./api_datesearch_test.py", line 52, in __main__.test_simple_datesearch
Failed example:
    test_simple_datesearch()
Exception raised:
    Traceback (most recent call last):
      File "/opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/doctest.py", line 1337, in __run
        compileflags, 1), test.globs)
      File "<doctest __main__.test_simple_datesearch[0]>", line 1, in <module>
        test_simple_datesearch()
      File "./api_datesearch_test.py", line 58, in test_simple_datesearch
        assert len(pdf) == 407, len(pdf)
    AssertionError: 996

Note that with recent change (see #541 ), the parameter window for datesearch (only) is restricted to maximum 3 hours.

Yes, simple test fails because it is now in days, not minutes - it is easy to fix. The second one is trickier - now the API does not provide an error message, but just crops the window to 3 hours if it is larger than that. Is it correct behaviour, or we should return the error in this case instead?..

Fixed in https://github.com/astrolabsoftware/fink-science-portal/pull/557


SecGeoLookupDb not working if we perform a "nginx -s reload"

Database is not open. Use: SecGeoLookupDb directive." after reload
Describe the Bug
When using mmdb to block countries from accessing the website, everything works fine until the nginx server is reloaded. After reload, it is not able to work.
It is linked to this issue in modsecurity: Issue 2041
As a consequence, I would require to restart the container whenever I update the configuration file to block certain countries.

The workaround mentioned in this issue, is to only compile the modsecurity engine without "libgeoip-dev" and without the flag:"--with-geoip"

Since the legacy GeoIP-dev library does not really server any purpose, would it be okiee to remove it from the image?

Apologies for bumping this, is this something the team would be willing to consider? @fzipi

Everything that keeps things working, of course. Sorry for the delay.

Alright thank you, I will raise a PR for it!

This should be solved in https://github.com/coreruleset/modsecurity-crs-docker/releases/tag/release%2F20241003.


Support supplying flags like Prune in the app updater when requesting a sync from ArgoCD

Checklist

[x] I've searched the issue queue to verify this is not a duplicate feature request.
[ ] I've pasted the output of kargo version, if applicable.
[ ] I've pasted logs, if applicable.

Proposed Feature

ArgoCD can pass extra options to sync, e.g. Prune https://github.com/argoproj/argo-cd/blob/32cc6638f78e15652c24eb2cd6403e6e7ec26ab0/server/application/application.go#L1971. Kargo doesn't set Prune, yet sets SyncOptions https://github.com/akuity/kargo/blob/cc293f0bd128943e097d9ae76ea69469b7a1c462/internal/directives/argocd_updater.go#L511-L528. It be nice to allow specifying Prune with update requests.
Motivation

Parity with ArgoCD sync.
Suggested Implementation

Surface Prune checkbox in UI if not already, then pass the flag to the sync field in the operation.

flags like Prune

Prune seems like a sensible option to expose. If there are others you feel would be especially useful, please enumerate.
I don't want to blindly expose all options, as my gut says not all of them make sense in the context of Kargo.
Prune, at least, is absolutely doable.

There also can be Replace, Force, Dry Run. Regarding Replace, there's this proposal https://github.com/argoproj/argo-cd/issues/20730, that would be discussed soon.

Rather than exposing any of these as options in the argocd-update step, I'm wondering if these are just things that should be copied over from the Application's sync policy when we create the sync operation.
Is there any reason that the options used by argocd-update should differ from what's in the sync policy?

I'm wondering if these are just things that should be copied over from the Application's sync policy when we create the sync operation.

Actually, I already assumed we were doing that, so we should make that change. I believe Argo CD auto-sync will pick up the applications preferences when creating the operation, so we can copy that logic.

Actually, I already assumed we were doing that, so we should make that change.

I thought there were, perhaps, things we ought to be copying but weren't but I just double-checked and we are already copying all sync options.
So @andrii-korotkov-verkada, if you have specific sync options set on the App, Kargo will already use them.

Sync flags might be good to support in the argocd-update step too, in case there is a use case to override the Application's default sync settings.

I believe because sync options are just generic string, we just need to support a string field and pass it on. There would be no upkeep of supporting more and more options.

I agree, especially if it's this straightforward.
Thanks @jessesuen.


lack of example for re-development

hi, i found out the lapin from the rabbitmq/examples , and in that repo, the lapin's example is too old for current version(^0.28), but using current repo, i just found out something very simple which lack

fanout model
direct routing
topic

and both without something like "queue_bind", "exchange" which can't be ignore
and in future's example, the code is in "0.27" which not compact with current stage
thanks

Hi,
More examples would totally be welcome!
I can help if needed

All examples are using latest version of lapin now


libc_bitflags doesn't group constants in documentation

Looking through the documentation generated from the sys/termios library for example (see #527) you can see that all the constants are listed in one big lump instead of grouped like how they are in the source. Additionally, when looking at these bitflags in the docs, they don't have any of their constants listed under them. You actually have to read the source to figure out what constants are part of sys::termios::InputFlags for example.

This was resolved with the merge of #801.


Return lockfile version and generator

This is a breaking change: it changes the return type.
Closes https://github.com/robertohuertasm/yarn-lock-parser/issues/19

@selfisekai  thanks for this. I have to review how these changes impact the project where I'm using the library. Will come back to you once I have a clearer picture.


Add necessary usethis commands for the things we cannot set correctly in advance

In the skeleton's README, we could write a sequence of usethis or other (e.g., custom-made) commands, that help to set up the aspects of the package we do not know in advance. E.g., commands that add necessary badges, type of license, etc. There are functions that do the most of the job to set up Travis CI and Appveyor (this means that not only plain text files are created by those functions), etc.
I think the skeleton should contain only those elements of the package that work out of the box (E.g., GitHub Actions workflows, some examples of vignettes, and functions). And all the infrastructure should work in the skeleton: CI, code coverage, pkgdown builds, etc.

Sounds good to me!

I agree for the badges, but I'm not convinced the skeleton should actually work on CI: the errors we get now are useful since they point to required changes e.g. in the DESCRIPTION file. Putting something like "SKELETON" there would make CI builds run, but that would then mean an additional risk of not changing all the things that need to be customized.

We decided for now to stay with the skeleton package rather than moving over to usethis - with the exception of usethis commands that do not need further changes for us.
The skeleton should stay with not filled in fields leading to the builds fail in order to make sure the fields will be correctly set for derived packages.


/-/{healthy,ready}/ respond to HEAD

Some frameworks issue HEAD requests to determine health.
This resolves prometheus/prometheus#11159
Signed-off-by: Nicolas Dumazet<EMAIL_ADDRESS>

Interesting, thanks! I don't have much experience with HEAD requests in the wild, but https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD says, "A response to a HEAD method should not have a body.". Maybe just return the OK status code for HEAD and no message? (that then obviates the need for the message printer handler refactoring as well).

Thanks Julius, I agree with you and I've updated the PR accordingly.

:+1: Thanks!


Add support for 2 command queues in UNet Shallow demo

Summary
Add support for 2 command queues in a UNet Shallow test script to improve end-to-end performance.

Complete in 173515aa773cec51dd20f2e5de80e0bfafe7d9cf


Installation fails due to conflicting idna version

Hi, users are unable to run derrick due to dependency conflict with idna package.
As shown in the following full dependency graph of derrick, derrick requires idna>=2.6，while requests==2.20.0 requires idna>=2.5,<2.8.
According to pip’s “first found wins” installation strategy, idna==2.8 is the actually installed version.
However, idna==2.8 does not satisfy idna>=2.5,<2.8.
Dependency tree---------
derrick-master
| +-chardet(version range:==3.0.4)
| +-docopt(version range:>=0.6.2)
| +-idna(version range:>=2.6)
| +-jinja2(version range:>=2.10.1)
| | +-MarkupSafe(version range:>=0.23)
| +-MarkupSafe(version range:>=1.0)
| +-nose(version range:>=1.3)
| +-pkginfo(version range:>=1.4.1)
| +-prompt-toolkit(version range:==1.0.15)
| | +-six(version range:>=1.9.0)
| | +-wcwidth(version range:*)
| +-pychalk(version range:==1.1.0)
| | +-six(version range:*)
| +-Pygments(version range:>=2.2.0)
| | +-coverage(version range:*)
| | +-nose(version range:*)
| | +-pyflakes(version range:*)
| | +-pylint(version range:*)
| | +-tox(version range:*)
| +-requests(version range:==2.20.0)
| | +-certifi(version range:>=2017.4.17)
| | +-chardet(version range:<3.1.0,>=3.0.2)
| | +-idna(version range:>=2.5,<2.8)
| | +-urllib3(version range:>=1.21.1,<1.25)
| +-requests-toolbelt(version range:==0.8.0)
| | +-requests(version range:>=2.0.1,<3.0.0)
| | | +-certifi(version range:>=2017.4.17)
| | | +-chardet(version range:<3.1.0,>=3.0.2)
| | | +-idna(version range:>=2.5,<2.8)
| | | +-urllib3(version range:>=1.21.1,<1.25)
| +-setuptools-git(version range:==1.2)
| +-simplejson(version range:>=3.11.1)
| +-six(version range:>=1.11.0)
| +-tqdm(version range:>=4.9.12)
| +-urllib3(version range:>=1.23)
| +-wcwidth(version range:>=0.1.7)
| +-whaaaaat(version range:>=0.5.2)
| | +-prompt-toolkit(version range:>=1.0.14)
| | | +-six(version range:>=1.9.0)
| | | +-wcwidth(version range:*)
| | +-pygments(version range:>=2.2.0)
| | | +-coverage(version range:*)
| | | +-nose(version range:*)
| | | +-pyflakes(version range:*)
| | | +-pylint(version range:*)
| | | +-tox(version range:*)
| | +-regex(version range:>=2016.11.21)

Thanks for your help.
Best,
Neolith

Solution

Fix your direct dependency to be idna>=2.5,<2.8.

I have checked this revision will not affect your downstream projects now.

Upgrade requests to 2.22.0，to remove this conflict.

Delete your direct dependency idna and use the idna transitively introduced by requests.

Which solution do you prefer, 1, 2 or 3?
@ringtail Please let me know your choice. I can submit a PR to solve this issue.

@NeolithEra I would like to choose 1 or 2. Could you submit a PR? Thanks a lot ! ☺

#42

Bug Fixed


Live tab in app during transition period

3 different states in BCC Media app during transmission period.
Functional live in live tab
Directory to connect app/ app store in live tab
Disable live tab
Versions released during transition period (jan- after easter) should be able to handle all 3 states behind feature flag
After Easter, only accommodate state 3

force-bcc-live (state 2)
remove-live-tab (state 3)


Default value of false for boolean does not work

Newest version: Result of my parsed arguments is {cache=mysql, duration=0, fillCache=false, writeRequestsPerSecond=0, readRequestsPerSecond=0, readThreadCount=5, size=4096, verbose=false, writeThreadCount=0}
Calling .isVerose() or isFillCache() returns true.
Cannot debug it because there are no sources for the .internal classes.

I'm also seeing this behavior in version 0.8.9. FWIW here is the code that returns true, regardless of what I set 'defaultValue' to:
@Option(shortName = "nu", longName = "no-ui", defaultValue = "false")
boolean suppressUi();

As per #3 I believe that this is the intended implementation. I would be inclined to agree that supporting boolean arguments that default to false would be useful, but it is not a bug.
The linked issue offers a work-around.


#1 Initial Release of the all new Liberty coin.

The wallet still has the theme we used for Rupaya at this point.

Many improvements and bugfixes.

Masternode tiers is still a work in progress and is not activated on the network.


Search not work properly with auto guess encoding

Does this issue occur when all extensions are disabled?: Yes

Version: 1.56.2 (user setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:

Set "files.autoGuessEncoding": true
The encoding of source file is "GB 2312"
When I open the source file, search works fine
Otherwise, I can't search Chinese text

Search doesn't support this setting. You will need to set files.encoding


Origin/submit questionnairs

Questionnaire submission issue fixed

Fix to questionnaire submission looks good.

Successfully fixed issue in which users were unable to submit questionnaire after questionnaires were made available at all times. Looks good.


Caching

Coverage increased (+0.3%) to 91.378% when pulling fc1bcd38657aa4b5f5648d35f86a14afc8d58550 on caching into 3089bb4c8bac8c92b3c1a0dc42228bce0affdae2 on master.

Coverage increased (+0.9%) to 91.984% when pulling 98dca47cb86ee15f435b9a7df3777a6b82e8a954 on caching into 3089bb4c8bac8c92b3c1a0dc42228bce0affdae2 on master.


Typos in the installation instruction:

Small typo: cd ,,/mmhuman3d should be cd ../mmhuman3d.
Thanks for the great work!

Thank you for the correction. Fixed.


Support contact points with multiple receivers

Newer versions of Grafana support a one-to-may mapping of contact points to receivers. However, the operator only supports one receiver per contact point.
Implementing this will probably break CRD compatibility, so we'll have to consider this carefully.

How about adding a new CRD GrafanaContactPointV2 to keep compatible

Hi @theSuess , I think I find a work around for this requirement, just declare multiple GrafanaContactPoint object with the same spec.name, like:
---
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaContactPoint
metadata:
  name: grafanacontactpoint-sample-part2
spec:
  name: grafanacontactpoint-sample
  type: "email"
  instanceSelector:
    matchLabels:
      app.kubernetes.io/instance: grafana
  settings:
    addresses: bar<EMAIL_ADDRESS>---
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaContactPoint
metadata:
  name: grafanacontactpoint-sample-part3
spec:
  name: grafanacontactpoint-sample
  type: "email"
  instanceSelector:
    matchLabels:
      app.kubernetes.io/instance: grafana
  settings:
    addresses<EMAIL_ADDRESS>

It's not very elegant, but works at the moment.


fix: FreeType build

Closes https://github.com/crazywhalecc/static-php-cli/issues/269.
See for the rationale: https://gitlab.freedesktop.org/freetype/freetype/-/issues/1158
Also let the SourceForge download page choose an appropriate mirror instead of hardcoding it.

Seems that we cannot dynamically obtain the latest version from the GitHub mirror repository.


Making Pub/Sub unit tests use mock credentials.

See some representative failures:

https://ci.appveyor.com/project/GoogleCloudPlatform/google-cloud-python/build/1.0.2609.pubsub-sys-test-hygiene
https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/4367


update description, remove inuit-clearfix

Updated module description
Capitalized the dropdown options for consistency
Removed inuit-clearfix import

@Menkhaus-ge do we need to keep the commented out line 70 in demo/index.html?

There is some inconsistency with the names of our states: level 3 is called "Temporary States" (plural), and level 12 is called "Modal State" (singular). That may be intentional though-- are there multiple possibilities for what might be a temporary state?

Looks like dropdown and shadows both need to be dark-themed

@Menkhaus-ge did you intentionally keep the commented out line 70 in demo/index.html or should I get rid of it?


Added Loading Animation

Title and Issue number

Title : Add loading animation for creating and joining rooms
Issue No. : #37
Code Stack :  React, CSS
Close #37

Description
I've added loading animations for both creating and joining rooms. Initially, I included an artificial loading time for testing purposes, as seen in the provided screen recordings. However, I've updated the functionality so that the loading animation only appears during actual loading processes.
Video/Screenshots (mandatory)

https://github.com/sd012gfhkhhvh/Slate.AI/assets/142984776/a52b70fe-c449-4cec-b8d8-c9fdb991e18b
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

Working under JWOC

@sd012gfhkhhvh consider this kind request , Could we change the tag from "Medium" to "Hard" on the  pull request? It was a bit more challenging than expected.

@sd012gfhkhhvh consider this kind request , Could we change the tag from "Medium" to "Hard" on the pull request? It was a bit more challenging than expected.

kindly make pr to the dev branch.

@sd012gfhkhhvh consider this kind request , Could we change the tag from "Medium" to "Hard" on the pull request? It was a bit more challenging than expected.

You have created a custom loader in raw css which might feel challenging, you could have used some external libraries for ease. But for your effort of making a custom loader I will think of upgrading the level

@sd012gfhkhhvh have a look

@ramith-kulal ping me up with your full name, githubId,college name etc on discord to keep track of contributors in phase-2


Backport 23221 to 7.52.x

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=auto

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=auto

@kacper-murzyn per our conversation earlier today let me just close this PR and not backport these changes to 7.52, because I am still struggling with some CI failures on the original PR that I'm backporting and I'm no longer confident in being able to sort them out without changing the agent install script. I'll just release these changes in 7.53 instead.


Medicine Publishing: dependent styles

Via https://forums.zotero.org/discussion/91529/request-for-assistance-for-referencing-style-for-diagnostic-histopathology#latest
Parent style has been created via: https://github.com/citation-style-language/styles/pull/5866
Add the following journals:
Anaesthesia and Intensive Care Medicine
Diagnostic Histopathology
Medicine
Obstetrics, Gynaecology and Reproductive Medicine
Orthopaedics and Trauma
Paediatrics and Child Health
Surgery

@adam3smith @bwiernik
Would you be able to review this PR at some stage? Thanks :)


Crash on search a char using f when target char isn't found

To reproduce
Create a file with the following content
this is a test
this is a test
this is a test

Then create a multi cursor on the three lines and press f (to search for a char in line) and then press a char that doesn't exists in the line like x. This leads to a whole hang of vim 8.1 and no way to recover from.

@Faham thanks for reporting this bug. It also happen on neovim.
The way to workaround this is to press CTRL-C.
If you really want this to be properly fixed, any pull request is welcome.
Thanks,
Antoine


Handle optional parameters

To make the Lambda more configurable allow passing in of additional optional parameters
This will support different configurations, for example validation metadata in different source bucket, validating against different schemas etc

Closing for now


Typescript

Hi,
Love this starter project, absolutely nails all the essentials in a modern SPA.
I am however a bit of a Typescript fan so would love to use TS on both the client and server. I dont suppose you know anyone that has had a go at converting this to use Typescript have you before I start?
Cheers,
Mike

I have just started learning TypeScript myself and loving it so far!
However I don't know anyone who's done that yet...

Ye I have been using it since the very first beta, it catches so many errors that are easy to make in JS. Use it on most of my web projects.
Unfortunately im not a webpack expert tho so always find it hard when I have to dig too deep into webpack.
It should just be a matter of using ts-loader then feeding the results into babel.. I think... http://stackoverflow.com/questions/38320220/how-to-setup-typescript-babel-webpack
Im going to have a go at it later this week, hopefully it should just be a matter of converting one file at a time (renaming *.js to *.ts) and working through the typing issues that come up, gonna go for MAX strictness tho to avoid those pesky nulls...
{
    "compilerOptions": {
        "outDir": "built",
        "target": "es5",
        "module": "commonjs",
        "moduleResolution": "node",
        "jsx": "react",
        "declaration": false,
        "removeComments": true,
        "experimentalDecorators": true,
        "sourceMap": true,
        "noImplicitAny": true,
        "noImplicitThis": true,
        "strictNullChecks": true,
        "noImplicitReturns": true,
        "noFallthroughCasesInSwitch": true
    },
    "exclude": [
        "node_modules",
        "built"
    ]
}


EKS in-place upgrades without data loss or data transfer using Karpenter

Description
What problem are you trying to solve?
I currently have several stateful applications and databases running on EC2 instances using local Instance storage with fast NVMe SSDs (i3en, i4g) to store 100s of TBs of data. When we need to handle upgrades, we can simply upgrade the processes and packages inside the node and consider it up-to date.
I am considering moving these workloads into EKS and manage the nodes with Karpenter.
One of the requirements we have is to keep EKS up to date with latests EKS versions. The default upgrade mechanism on EKS creates new nodes instead of upgrading them in-place and reusing the nodes.
This requirement will force our EKS clusters to be upgraded multiple times a year, which is a disruptive and sensitive operation for stateful applications when we have to move 100s of TB on each upgrade for each cluster, moving that much data is a slow process that can take days to avoid impacting the performance of the cluster.
We are evaluating options to mitigate node rotation by having nodes upgraded in-place without losing the data in the ephemeral storage of the node. Unfortunately, EBS is not an option for this setup.
Is there any way to handle in-place node upgrades with Karpenter?
How important is this feature to you?
Not having this handled by karpenter, would require us to implement hacky ways to achieve in-place upgrades, that can cause inconsistency across nodes, which we prefer to avoid but I am keen to hear your approaches if it solves the problem.

Would it be possible to close this issue as a duplicate of https://github.com/kubernetes-sigs/karpenter/issues/1123. Would be useful to have this write up in that issue


MAINT: sparse.linalg: Remove unnecessary operations

Reference issue

What does this implement/fix?

Removed the unnecessary condition statement related with the numpy.matrix type in utils.py because b is a ndarray after calling make_system, and the reshape operation  is also unnecessary.
Additional information

thanks @zhaog6

Seems like a useful simplification to me.

Yes, the make_system make b an ndarray type (hence the if condition is not necessary) and shape of x is a tuple (N,) (hence the reshape operating is also not necessary).
Thanks for your review!


ruff: 0.0.277 -> 0.0.278

Diff: https://github.com/astral-sh/ruff/compare/v0.0.277...v0.0.278
Changelog: https://github.com/astral-sh/ruff/releases/tag/v0.0.278
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[x] 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.

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

27 packages built:

baserow
baserow.dist
dmarc-metrics-exporter
dmarc-metrics-exporter.dist
emacsPackages.lsp-bridge
paperless-ngx
python310Packages.dirty-equals
python310Packages.dirty-equals.dist
python310Packages.pytest-examples
python310Packages.pytest-examples.dist
python310Packages.python-lsp-ruff
python310Packages.python-lsp-ruff.dist
python310Packages.watchfiles
python310Packages.watchfiles.dist
python311Packages.dirty-equals
python311Packages.dirty-equals.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.watchfiles
python311Packages.watchfiles.dist
ruff
ruff-lsp
ruff-lsp.dist
strictdoc
strictdoc.dist

resulting binary works fine, lgtm


React challenge 12 fails test

The code in the attached image fails test, even if indent is added before Fruits and Vegetable components to match solution code

Get should be lowercase: document.getElementById

:+1:

But the Fruits and Vegetables components should be on the same indentation level as the  tag, right? Or does it not matter?

Nope! tThe indentation doesn't matter at all. All of the JSX will be compiled down so it can be indented in any arbitrary way.


word cuts when displayed

Hi,
Thank you for your nice package! When trying the example of the README, I get the following result

As you can see, the text is cut in the boxes and the diagram is not interactive.
Is there a way to address this?
Thank you

Hi @rveltz,
I have faced this problem before but I'm not pretty sure on how to solve it properly. This package basically puts together functionality from Kroki through Kroki.jl.
It would be interesting to investigate whether this is a problem with DocumenterDiagrams or an upstream issue.
Thanks for pointing it out!
If you are sticking to generating diagrams using mermaid, I would consider using DocumenterMermaid, as they might provide interactivity features.


What are the supported browsers for echarts?

This is something that came up to my mind recently, but what are the supported browsers for echarts?
Ovilia mentioned that this is something that could be added inside the Tutorial section of the docs
P.S. I edited this, because I realized that on the mailing list, it was Ovilia who replied 😅

@Jivanvl if you don't mind, could you post here what the supported browsers are? That way anyone in the community can easily contribute the change? :)


Alex can make indicator bars appear first

by holding down the button, hitting correct to skip the question without allowing buzz ins, opening a new question, and releasing the button

This is likely fixed, but I'm bad at coding so I'll keep the issue open for now and keep an eye on it


Cache too large

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.713
Where did you get the app from?
Google Play
Android version
14
Device model
Pixel 8 Pro
Steps to reproduce
After a minimal amount of usage, I check the size of the cache, using the long press on the app icon & tap storage. The cache is always 1.72 GB or above, even though I clear it every day.

Expected behavior
I expect a smaller cache
Actual behavior
Since the latest update, cache is 1.72 GB or more
Logs
k9mail-logs.txt

This is not a general problem. My K-9 Mail installation is several years old and the cache size is below 50MB. I never manually clear the cache.
Unfortunately, there's no easy way to check what is causing your cache size to blow up like it does. Can you please do some experiments to try to narrow it down?
I'm guessing it's the WebView component that is caching a lot of data. To test this, clear the cache, open the app and sync your accounts, but don't open any messages for viewing. Then check the cache size.
If the cache size is small, open a message for viewing, then check the cache size again. Repeat, and write down the cache size after each opened message. If there's a message that causes a significant increase, we'd like a (redacted) copy of that message so we can try to reproduce the problem on our test devices.

I cleared the cache. I synced my accounts. Cache went up to 1.72 GB without even opening any messages.
Thanks
On December 30, 2023 8:56:39 AM CST, cketti @.***> wrote:

This is not a general problem. My K-9 Mail installation is several years old and the cache size is below 50MB. I never manually clear the cache.
Unfortunately, there's no easy way to check what is causing your cache size to blow up like it does. Can you please do some experiments to try to narrow it down?
I'm guessing it's the WebView component that is caching a lot of data. To test this, clear the cache, open the app and sync your accounts, but don't open any messages for viewing. Then check the cache size.
If the cache size is small, open a message for viewing, then check the cache size again. Repeat, and write down the cache size after each opened message. If there's a message that causes a significant increase, we'd like a (redacted) copy of that message so we can try to reproduce the problem on our test devices.
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/7464#issuecomment-1872543077
You are receiving this because you authored the thread.
Message ID: @.***>

Hello,
I was just wondering how you are using v6.713 when the version on Google Play and here on Github are both v6.603? I am using this version on Android 14 and my cache is 122MB.
Could you have downloaded a per-releasve version or something?

It's beta. The latest update did this to the cache.
On January 2, 2024 11:41:22 AM CST, jsinfate @.***> wrote:

Hello,
I was just wondering how you are using v6.713 when the version on Google Play and here on Github are both v6.603? I am using this version on Android 14 and my cache is 122MB.
Could you have downloaded a per-releasve version or something?
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/7464#issuecomment-1874339927
You are receiving this because you authored the thread.
Message ID: @.***>

@PandaGuitar: Can you please clear the cache from the Storage screen, then exit the screen and open it again? Does the cache size actually shrink after "clear cache" was used?

When I clear it, it says 0 B. When I close & reopen, it says 2.73 GB, even without opening the app to read messages.
On January 3, 2024 8:37:50 AM CST, cketti @.***> wrote:

@PandaGuitar: Can you please clear the cache from the Storage screen, then exit the screen and open it again? Does the cache size actually shrink after "clear cache" was used?
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/7464#issuecomment-1875473377
You are receiving this because you were mentioned.
Message ID: @.***>

So at least part of the problem seems to be a bug in Android. Try force stopping the app, then clearing the cache.

Same thing happens
On January 3, 2024 9:07:52 AM CST, cketti @.***> wrote:

So at least part of the problem seems to be a bug in Android. Try force stopping the app, then clearing the cache.
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/7464#issuecomment-1875520693
You are receiving this because you were mentioned.
Message ID: @.***>

That makes it rather hard to find out what caused the cache to grow that large in the first place. I suggest you open a bug in Android's issue tracker for the cache not actually being deleted. https://issuetracker.google.com

OK thanks!
On January 3, 2024 9:24:49 AM CST, cketti @.***> wrote:

That makes it rather hard to find out what caused the cache to grow that large in the first place. I suggest you open a bug in Android's issue tracker for the cache not actually being deleted. https://issuetracker.google.com
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/7464#issuecomment-1875545587
You are receiving this because you were mentioned.
Message ID: @.***>

I'm closing this issue because there's not much we can do without more information.
Please do post here once your Android version allows you to clear the cache so we can narrow down which part of K-9 Mail is responsible for growing the cache. I'll then re-open the issue.


does not support Arabic

you make a great addon it just need a little improvement
i hope yo will help me
Error report from the popup
utf8 canot decode  0xc8
What is your operating system
win10

Hey do you have a copy of the file by any chance?
It's seems more like a general unicode error tbh.
I assume your are running the plugin from anki?

hey
I hope the html and image have been sent.
bad network connection
thank you again
في السبت، ٢٨ مارس، ٢٠٢٠ ٢٣:٣١ c-okelly<EMAIL_ADDRESS>كتب:

Hey do you have a copy of the file by any chance?
It's seems more like a general unicode error tbh.
I assume your are running the plugin from anki?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c-okelly/org_to_anki/issues/64#issuecomment-605515661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOZ4YSRSJRNBRGO5ZOLI2TTRJZNCHANCNFSM4LVOAAGQ
.

hey
I am sure the plugin work properly with English but
with arabic show this message.
I use liberoffice
the html show correct view in the  internet browser
I tried alot alot of way to be sure the problem not related to RTL LTR
thank you very much
p.s.
I am a med student so I donot know alot about programming. ..etc
arabic .html
https://drive.google.com/file/d/10cK5rIBvabHDqEiRPF1dIeOmFURYWtxr/view?usp=drivesdk
٢٠٢٠٠٣٣٠_٢٢٢١١٨.jpg
https://drive.google.com/file/d/1j6PE51tX5ylfwLONvBaJHhOfiCve0-h5/view?usp=drivesdk
في السبت، ٢٨ مارس، ٢٠٢٠ ٢٣:٣١ c-okelly<EMAIL_ADDRESS>كتب:

Hey do you have a copy of the file by any chance?
It's seems more like a general unicode error tbh.
I assume your are running the plugin from anki?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c-okelly/org_to_anki/issues/64#issuecomment-605515661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOZ4YSRSJRNBRGO5ZOLI2TTRJZNCHANCNFSM4LVOAAGQ
.

Sorry I missed the reply here.
Could you please provide me with access to the google drive file?
Thanks

I'm not able to replicate the problem. I have a sample deck linked below:
https://docs.google.com/document/d/e/2PACX-1vRh7ZbjjJmvaAcCnn6M2btOPBoOZdn4lWoCr6vJNHDuS7CZrZDkJfst8o7FRxl8xtD2sQPLLYm4fuX5/pub
Could you please provide a link the the deck that is causing you the error?


Fix test_remote_io.py due to mutating public s3 bucket

Please read through our contribution guide prior to
creating your pull request.

Note that there is a section on requirements related to adding a new DataPipe.

Fixes #984
Changes

Add a private function to TestDataPipeRemoteIO in test_remote_io.py to get s3 objects count label through aws cli
add awscli in requirements

Hi @NivekT, @ejguan, have you seen a version conflict similar to the one we are getting in 3.11 conda? I wonder if you have any quick fix

Hi @NivekT, @ejguan, have you seen a version conflict similar to the one we are getting in 3.11 conda? I wonder if you have any quick fix

You ignore it. Not related

@ShiboXing Can you please do a rebase onto main branch and force push? Otherwise, I think this PR is ready.

@ejguan, rebased and force-pushed!


Add Docker

I added a Dockerfile, so people can build and run Blackbird inside of a container. I also updated the README, with some basic instructions.

Thanks @alexgandy

lets get this merged :)


[OneExplorer] Directory move/deletion is not reflected automatically

What?
Directory move/deletion is not detected by file system watcher which ONE Explorer is using.
It's found out that removing directory within the workspace is not detected, both on ssh-remote or local envs.
From #1213

Fix?
  private fileWatcher = vscode.workspace.createFileSystemWatcher(
      `**/*.{cfg,pb,tflite,onnx,circle,tvn,tv2w,tv2o,tv2m,log,json}`);

Currently, ONE Explorer's file watcher watches files with certain extensions, not directory.
By changing the glob pattern to **/*, the problem resolves.

Concerns?
Will it slow down our extension?
About watching all the files within the workspace:
Anyways file system change occurs only on file save, until the user hits the save key, file system watchers won't work. It'll be okay...
If there's any file which is periodically changing in the workspace, ONE Explorer will have such a burden of refreshing periodically. Currently, it re-build all the tree, not the changed one.
By saving the tree and re-build the subtree of only the changed ones, the problem will be solved.

Done


Fix unique line coverage counting

We count the #unique line coverage of the new fuzz targets by subtracting the lines covered by existing targets.
However, the current code does not exclude unhit lines in existing targets.
This PR fixes that by only subtracting lines with a non-zero hit count.
This PR also:

Adds a new helper function to assisting debug this or similar issues in the future.
Fixes a minor typo in function pattern when matching covreport, which misses the first char in function name.

Launching another full experiment with the latest code:
JOB: https://pantheon.corp.google.com/kubernetes/job/us-central1/llm-experiment-large/default/weekly-manual-mar-6
REPORT: https://llm-exp.oss-fuzz.com/Result-reports/scheduled/2024-03-06-weekly-all/sort.html
BUCKET: https://pantheon.corp.google.com/storage/browser/oss-fuzz-gcb-experiment-run-logs/Result-reports/scheduled/2024-03-06-weekly-all
BUCKET GS: gs://oss-fuzz-gcb-experiment-run-logs/Result-reports/scheduled/2024-03-06-weekly-all


Uncaught TypeError: Cannot read property 'Changes' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 1.1.0
System: Mac OS X 10.11.1
Thrown From: omnisharp-atom package, v0.25.10
Stack Trace
Uncaught TypeError: Cannot read property 'Changes' of null
At /Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:77

TypeError: Cannot read property 'Changes' of null
  at Object.applyChanges (/Users/Dopare/.atom/packages/omnisharp-atom/lib/omnisharp-atom/services/apply-changes.js:4:17)
  at AnonymousObserver._onNext (/Users/Dopare/.atom/packages/omnisharp-atom/lib/omnisharp-atom/features/code-format.js:46:73)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1787:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AnonymousObserver.tryCatcher (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:63:31)
  at InnerObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:4585:41)
  at InnerObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at InnerObserver.tryCatcher (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:63:31)
  at AutoDetachObserverPrototype.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:5793:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AnonymousObserver._onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/contexts.js:49:30)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1787:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AnonymousObserver.tryCatcher (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:63:31)
  at AutoDetachObserverPrototype.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:5793:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at FirstObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.aggregates.js:945:19)
  at FirstObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at Subject.Rx.Subject.addProperties.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:5908:19)
  at AnonymousObserver._onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/clients/client-base.js:263:72)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1787:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AnonymousObserver.tryCatcher (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:63:31)
  at AutoDetachObserverPrototype.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:5793:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AnonymousObserver._onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.time.js:863:13)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1787:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:1721:31)
  at AsyncSubject.Rx.AsyncSubject.addProperties.onCompleted (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/rx/dist/rx.js:5995:17)
  at StdioDriver.handlePacketResponse (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:203:26)
  at StdioDriver.handlePacket (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:189:18)
  at StdioDriver.handleData (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:184:18)
  at Interface.<anonymous> (/Users/Dopare/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:126:54)
  at emitOne (events.js:77:13)
  at Interface.emit (events.js:169:7)
  at Interface._onLine (readline.js:209:10)
  at Interface.<anonymous> (readline.js:339:12)
  at Array.forEach (native)
  at Interface._normalWrite (readline.js:338:11)
  at Socket.ondata (readline.js:85:10)
  at emitOne (events.js:77:13)
  at Socket.emit (events.js:169:7)
  at readableAddChunk (_stream_readable.js:146:16)
  at Socket.Readable.push (_stream_readable.js:110:10)
  at Pipe.onread (net.js:520:20)

Commands
     -0:07.4.0 core:move-left (atom-text-editor.editor.omnisharp-editor.is-focused)
  2x -0:07.1.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:06.3.0 snippets:next-tab-stop (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:06.3.0 snippets:expand (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:06.3.0 editor:indent (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:05.5.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:04.9.0 core:save (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:02.3.0 core:backspace (atom-text-editor.editor.omnisharp-editor.is-focused)
     -0:02.1.0 omnisharp-atom:code-format-on-curly-brace (atom-text-editor.editor.omnisharp-editor.is-focused)

Config
{
  "core": {},
  "omnisharp-atom": {}
}

Installed Packages
# User
atom-yeoman, v0.3.15
json-schema, v0.1.15
linter, v1.10.0
omnisharp-atom, v0.25.10

# Dev
No dev packages

I am also getting this error while editing a c# file.

Same here. Basically I get this error while writing ' ; ' at end of line or expression.
It would be nice to know how to fix it

I also get this error, and there's no IntelliSense either.

This should be fixed the latest version, let me know if you see a problem again.


fix: type definition of pageref in Entry

This pull request renames the field pageRef under the Entry interface to pageref to keep it consistent with other occurrences in the codebase as well as the W3C specification (although it is still a draft).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


UK Postal address issue with postcodes

Running into an issue where if an incorrect county is used, ie a council instead of the correct county. For example
58 Gloucester Crescent Hindley Wigan WN2 4DQ
Wigan is the council, instead of Wigan it should be Greater Manchester but in real terms there's nothing wrong with Wigan. This incorrectly results in the postcode being labelled as house, which makes a complete mess of the addresses. Result:
Array (     [0] => Array         (             [label] => house_number             [value] => 58         )     [1] => Array         (             [label] => road             [value] => gloucester crescent hindley         )     [2] => Array         (             [label] => city             [value] => wigan         )     [3] => Array         (             [label] => house             [value] => wn2 4dq         ) )
Though 58 Gloucester Crescent Hindley WN2 4DQ
Correctly results in:
Array (     [0] => Array         (             [label] => house_number             [value] => 58         )     [1] => Array         (             [label] => road             [value] => gloucester crescent         )     [2] => Array         (             [label] => city             [value] => hindley         )     [3] => Array         (             [label] => postcode             [value] => wn2 4dq         ) )
Will add more examples shortly.

Found a nice work around, adding United Kingdom to the end of the strings resolves the issue

Hm, so Wigan exists in OSM, but would be mapped to city under libpostal's current mapping rules for the UK. The UK of course has more exceptions than any other country in our configs :-).
Under the current rules, admin_level=8 is mapped to city in the UK unless there is a "designation" tag that is one of {non_metropolitan_county, non_metropolitan_district, unitary_authority}, in which case it's mapped to state_district, and there are exceptions for individual cities. For Wigan, the designation is "metropolitan_district".
I wasn't really sure how to map metropolitan_district because looking at the 30 instances of this tag in OSM, it is used for Birmingham, Manchester, Liverpool, Sheffield, Leeds, and Newcastle as well (maybe a few others), which would have the adverse affect of making those cities state_district as well as the actual metropolitan boroughs.
What I can do is map designation=metropolitan_district to state_district by default and just make exceptions for the cases that are really city boundaries.
There are a couple of other things I'm doing for v1.1 around allowing more verbose UK place names (locality + postal town combos being one of the big ones). Can add this in to the release as well.

There might be another issue here on the parser/feature extraction side. The reason the postcode is parsed correctly when you add country name is that in our machine learning model there's a different feature (variable) that fires if a postcode is seen in the context of a valid admin area (11216 could be a house number in California, but if it's seen next to a token like "Brooklyn" or "NY" it's definitely a postcode). If a known postcode is seen without supporting context, the model will be essentially operating without the most important variable in predicting the postcode label.
For most countries that use digit-only postcodes, this is really helpful in disambiguating between house numbers and postcodes, but for the UK and Canada, postcodes are so distinctive that they shouldn't need any other supporting context.
Reminder to self that it might also be helpful is to add a feature which could fire for any postcodes that are unambiguous whether they have context or not, which could only help in the UK/Canada without hurting performance anywhere else.

Yeah there's definitely an issue around this. Wigan is a city, so is Hindley but Hindley falls within the Wigan Borough which is probably the best way to describe it. With them both being cities(towns) shouldn't they map identically?
I would have expected 58 Gloucester Crescent Wigan WN2 4DQ to be the same as 58 Gloucester Crescent Hindley WN2 4DQ, but the Wigan version is parsing the post code into house. While this Hindley one is correct.

Looking at the training data the only examples of that particular postcode seem to come from our GeoPlanet data. In GeoPlanet, that postal code is associated with Hindley (so Hindley is a valid context), and Hindley is parented by "Wigan Metropolitan Borough", as a state_district. "Metropolitan Borough" is not one of the boundary name suffixes we use to normalize names, which I can add to the list, but in general that means that "Wigan" by itself wouldn't be valid context for that postcode under the current model.
With the proposed changes to feature extraction, none of that would really be an issue in 1.1.

That makes sense, I thought that would be the case but I did the following and it parsed fine which made me think otherwise.
58 Gloucester Crescent London WN2 4DQ
Anyhow agreed, sounds like you understand what needs to be done for 1.1 and I can work around for now. Let me know if you need anything UK related.
Thanks!

There are other features in the model that can help other than the postcode context such as structural features (previous word=London and previous tag=city may also be a reliable indicator that the next word is a postcode if there's no other strong evidence from the word itself, and a large city like London might have a higher weight for that than smaller cities, enough to overpower the intercept/bias feature).
You can see the features used by libpostal at each word using the .print_features command in the address_parser client. It's kind of like logging for the parser model and can be helpful in debugging postcode issues (particularly the "postcode have context" and "postcode no context" features).
May very well need some UK geography/address help in the future. Used to live there and have been to many of these places but the addresses are still among the more edge-case-y in the world.

Not sure if its helps but I'll keep adding examples to this ticket of other UK issues related to postcode which I think 1.1 will fix will allow you to run through some currently bad examples to help with testing.
Seen this today Unit 105, Screenworks, 22 Highbury Grove, London, N5 2EF, United Kingdom, both London and 2EF parsed into City, 'N5' becomes postcode.

Couldn't find that particular postcode in the training data. In GeoPlanet there's "N5 2EA", "N5 2EG", and "N5 2EH".
I should also say that in 1.1 there's another form of token normalization which, in addition to the normalizations we already do (normalizing all digits to "D"), will normalize all letters in a numeric token to "X" so tokens like "NX 2XX" can share statistical strength without necessarily needing to see every postcode in training.

@thatdatabaseguy how is 1.1 coming? I have an internal application I can use it on, whats its current state is it stable enough to use?

Not yet. OSM has grown large enough that the 1.1 training data can no longer be built on a single machine in-memory, so in the process of moving it to a Spark implementation. I'm also working on multiple things other than libpostal at the moment, so no ETA. Libpostal 1.0 can parse just about anything in the UK if you can afford a few minor mistakes (GeoPlanet contains almost 2 million UK postcodes, so the 2 examples above simply happen to be postcodes that were neither in GeoPlanet nor OSM). If not, use a regex to extract/remove the postal code, and then use libpostal on the remainder of the address.


Move indirect call substitution to printer

An alternative to #43543 to estimate the performance implications of performing the substitution in the printer.

@typescript-bot perf test


CLI command is not standard nomenclature and needs clarity

[
Below is the standard nomenclature for cli commands:
az purview account add-root-collection-admin --account-name [Purview Account Name] --resource-group [Resource Group Name] --object-id [User Object Id]
Customers and SEs are not able to follow the cli command as provided due to lack of clarity.
]

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

ID: 1bb9ad75-5aa1-af3d-9f59-073015190950
Version Independent ID: 467433dd-ade8-5109-eaa5-a2198146b769
Content: Understand access and permissions - Azure Purview
Content Source: articles/purview/catalog-permissions.md
Service: purview
GitHub Login: @viseshag
Microsoft Alias: viseshag

@tifischer Thank you for sharing valuable feedback. We are actively validating it. We will share updates soon.

@tifischer  - As always, thank you! I've updated the command and added some information.

You should see the update by this afternoon, or tomorrow at the latest.

#please-close


Release v2.5 is ES6, was that supposed to be built?

Release v2.5 is ES6, was that supposed to be built?

I've attached the browser scripts in the 2.5.0 github release. The browser files are normally available through npm in the dist folder or the project can be imported for use with browserify.


markdown superscript and subscript

Describe the bug
The superscript and subscript don't seem to work.
For example:
x2  should produce x2
x2 should produce x2
Thank you,

It's already working in latest VS Code Insiders


Roll Flutter Engine from 5f6469f47e42 to 472f39fa128c (4 revisions)

https://github.com/flutter/engine/compare/5f6469f47e42...472f39fa128c
2023-03-02<EMAIL_ADDRESS>[web] Remember which variant of CanvasKit is being used (flutter/engine#40027)
2023-03-02<EMAIL_ADDRESS>Fix includes of SkBitmap/SkImage (flutter/engine#40026)
2023-03-02<EMAIL_ADDRESS>Revert "add lint check for python files (#39736)" (flutter/engine#39930)
2023-03-02<EMAIL_ADDRESS>Roll Skia from 5ce859c0a3e1 to a0ab1e734490 (3 revisions) (flutter/engine#40024)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


KON-6: Allow kwargs for create/update function and additional tweaks

Jira: KON-6
Closes #9

SgBaseModel now supports _extra_fields where any arbitrary fields that is not specified by the subclasses model will be store in _extra_fields.
Example:
data = {"id": 1, "name": "Projek", "sg_foobar": True}
project = SgProject.from_dict(data)
project._extra_fields  # {"sg_foobar": True}

To include the _extra_fields when converting the model to dict, make sure to pass in include_extra_fields=True as kwargs.
project.to_dict(include_extra_fields=True)


Remove Offload Listener code

For the time being this has been disabled.
The original implementer has stated that we should not bring this back life using it's current code but remove it and re-do it using different scaffolding for a REST API interface.

Dependencies supporting this code are being flagged with vulnerabilities, from Github notifications:
python-multipart vulnerable to Content-Type Header ReDoS

High severity

fastapi, python-multipart, starlette

CVE-2024-24762

gunicorn is also being flagged with a vulnerability:
https://github.com/gluent/goe/security/dependabot/5


Add version conflicts to entity updates

Depends on https://github.com/getodk/central/issues/509

Represent conflicts in the database somehow (on entities or entity_defs table?)
Detect the conflict (base version noted in submission does not match latest version on the server)
Save that there was a conflict
Expose conflicts on the API

Should be able to compute

how many entities are in conflict in a given entity list
which entity is in conflict
(probably) which entity def introduced the conflict

API changes should enable the following frontend PRs:
#500
#502
#503
#504

My current thinking is that we could implement this as two columns:

entity_defs."conflictStatus". One of 'hard', 'soft', or null. This reflects whether the entity def conflicts with prior entity defs, not later ones. The value would never change.
entities."resolvedAt". When were conflicts on the entity last marked as resolved? When counting conflicts, we would only include entity defs created after this timestamp.

API changes

Frontend needs conflict counts in multiple places. For #505 and #507, Frontend also needs the diffs of the conflicting entity versions relative to their base version ("author's view"). The current diffs endpoint compares entity versions sequentially ("Central's view"), which Frontend still needs. But Frontend now also needs a way to diff conflicting entity versions relative to their base version.
In addition, Frontend needs to know for each conflicting entity version whether it is a soft conflict or a hard conflict. In the case of a hard conflict, it needs to know which properties conflict. (I guess a soft conflict is just the case where the list of conflicting properties is empty.)

I'm copying this note from @lognaturel to here because its relevant to how we think about conflicts:

My recollection was that we weren't going to do three way merging and would instead do last-received-wins with detection of

"simultaneous updates": the last received updating submission's base version is not identical to the server's current version and there is no overlap between the properties updated by this submission and properties changed by any updates made since the last received submission's base version
"conflict": the last received updating submission's base version is not identical to the server's current version and there is overlap between the properties updated by this submission and properties changed by any updates made since the last received submission's base version

IIRC, we mostly reached this conclusion based on the assumption that updates from submissions would generally be diffs already. That is, if a property isn't changed by a form, it wouldn't generally be sent. That assumption would be incorrect if users decide to build forms that are more for data management than worfklow management so we would track frequency of conflicts and reconsider more sophisticated merging if they happened a lot.

There's ongoing discussion in slack but I'll summarize it all here in this issue once we get to a decision.


Add Tencent.QQ

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/AzurePipelines run

/azp run

/Azp Run

The link given in this PR is used to download the latest version of Tencent QQ, and I can not find a link to download the specified version. So every time an official upgrade of it, the installation fails due to the inability to pass the hash check.