Track Changes

Great product. I do not see an option to provide track changes editing (i.e., changes are marked with underline or something similar as they are typed in). Is this possible / has it been considered?

The editor doesn't have such a feature and we have very little request for that so it's unlikely to have it implemented by ourselves. I would suggest using the editor together with ICE.JS: https://github.com/NYTimes/ice.

That is a helpful reference. Thank you.


Sync<EMAIL_ADDRESS>

PR Details
Syncs beta<EMAIL_ADDRESS>to master
Added containerRef to the context.
Added useCarousel hook to make it easier to access.
Also added storybook - previously tested on beta but got nuked due to it being shipped with another feature that didn't go live

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Movienizer Crack 10.1 Build 594 with Keygen [Latest]

Movienizer Keygen is an impressive database management tool for movies, featuring advanced sorting, searching, backup and restore, statistics and reports. The application has good and attractive interface.
Movienizer Full Version Crack has an initiative user friendly interface and also installation process is very easy. Movienizer uses a clean window with an organizational structure in which the default movie database is loaded.
Download Now

✅▶▶ DOWNLOAD  PRO VERSION
✅▶▶ MIRROR FREE CRACK VERSION
.
.
.
✅▶▶ DOWNLOAD  PRO VERSION
✅▶▶ MIRROR FREE CRACK VERSION
.
.
.
///

Overview of Movavi Video Editor Crack
Movavi Video Editor Crack doesn’t need a formal introduction, its name is enough to showcase its features; the touch-enabled AI professional video editor is ideal for beginners and experienced users alike. From basic editing tools to advanced features, the hacked versions have it all. This means you can get lifetime access to amazing cutting, trimming, and merging features along with various advanced tools like color adjustments, transition effects, layouts, and more.


Ctrl+q comments the line instead of quitting

Description of the problem or steps to reproduce
When I tried to run the freshly installed editor I got this issue. At first, I thought I didn't know how to properly quit. Though after a few hours of coding and reading the built-in help text, I realized it's probably the default key binding. I read that F4 and F10 also do that action and they are working as usual.
Specifications
Version: 2.0.10
Commit hash: b9763856
Compiled on August 07, 2021
OS: Windows 10
Terminal: cmd.exe - WSL 2 (Ubuntu 20.04.2)

On a fresh install for me, it functions as intended. Try using the command to reset the micro settings.

Maybe this is a WSL2 specific bug. I'm having the same issue on a Debian WSL2 install, whereas I don't have this issue anywhere else, whether I'm using debian or not.

If you run > raw, what key inputs does micro report having received?

@zyedidia This is what it reports receiving on WSL2 when I press Ctrl+Q


git rm -r db/migrate/

We're trying to spin up Signon in the test env, pink stack, as part of having a working base for Replatforming.
We were facing problems with Signon not deploying because Rails refused to apply migrations, because Rails behaviour has changed between 2012 and now (surprise) and old migrations no longer apply.
The solution, it seems, is to ignore the migrations by deleting them all, as we're not going to edit every single migration for workingness eight years on. The Rails guides say that the db/schema.rb file is the canonical source of the current state of the database (what db:setup refers to), not the migrations, so the db/migrate files can be deleted at any time (once applied).
Worth noting that this problem does not occur in production, staging or integration, or indeed in GOV.UK dev environments, because we've replicated production data so the database exists when the apps deploy/run, fully populated.

Co-authored-by: Bill Franklin<EMAIL_ADDRESS>

I'm a bit worried this may be quite surprising as you'd expect an ActiveRecord project to have migrations and it's unconventional for our ActiveRecord apps to not have any. The approach we've taken in the past is to nuke just the data migrations that are coupled to application code (😡). I'll just do a quick look to see if that's practical as that seems preferable if it's not a massive job.

I had a bit of a play to see what the situation is like (branch) and even then the schema comes out different so I don't think there's anything to salvage here as production and migrations seem to have diverged.
I'm a bit concerned that if this is something that is beyond a one-off for signon we may need to have some community discussions about when is the right time to delete migrations (it seems to be something we've successfully put off for many years) as there's a level of confusion and ambiguity about when/why a migration nuking should occur. Might be worth just checking in tomorrow with #govuk-developers before merging to see if anyone has concerns/opinions.

We're trying to spin up Signon in the test env, pink stack, as part of having a working base for Replatforming.

We were facing problems with Signon not deploying because Rails refused to apply migrations, because Rails behaviour has changed between 2012 and now (surprise) and old migrations no longer apply.

So, I'm guessing this is occurring because the deployment process tries to run the migrations.

The solution, it seems, is to ignore the migrations by deleting them all, as we're not going to edit every single migration for workingness eight years on. The Rails guides say that the db/schema.rb file is the canonical source of the current state of the database (what db:setup refers to), not the migrations, so the db/migrate files can be deleted at any time (once applied).

Worth noting that this problem does not occur in production, staging or integration, or indeed in GOV.UK dev environments, because we've replicated production data so the database exists when the apps deploy/run, fully populated.

I think the more common (what I'd call proper) approach to this is run rake/rails db:setup. If you're deploying the app from scratch, that's what you should do to setup a database. I'm not particularly looking forward to this trend of deleting the migrations from the Git repositories just to work around the fact that the processes for bringing up new environments don't handle the situation properly.

* Worth noting that this problem does not occur in production, staging or integration, or indeed in GOV.UK dev environments, because we've replicated production data so the database exists when the apps deploy/run, fully populated.

Ah, I forgot to say, this isn't particularly relevant. For local development, you also run rake/rails db:setup, and that's why this issue with the migrations doesn't arise. This functionality is written in to tools like govuk-docker and govuk-guix.

Glancing through the migrations, there are instances where it looks like we are setting data as well as changing schema, Is there a risk in removing all migrations that we loose some state of data that a fresh application relies on? I realise that currently running migrations on a fresh copy breaks, so perhaps a bit of a moot point.
The other thought I had - are there any classes/code paths in for example the lib directory that we only ever call from a migration? If we are throwing away migrations, cleaning those potential things up as well would be a good idea, though of course more tedious.

I'll close this, since on further investigation we found that it's not necessary.
Rails maintains a schema_migrations table based on the filenames under the db/migrations directory. This lets it keeps track of which migrations have to be run. E.g.
10:33:46 database: signon_production
10:33:46
10:33:46  Status   Migration ID    Migration Name
10:33:46 --------------------------------------------------
10:33:46    up<PHONE_NUMBER>0458  Devise create users
10:33:46    up<PHONE_NUMBER>0534  Make users suspendable
10:33:46    up<PHONE_NUMBER>0725  Create doorkeeper tables
10:33:46    up<PHONE_NUMBER>4033  Add name to users
10:33:46    up<PHONE_NUMBER>4527  Add uid to users
10:33:46    up<PHONE_NUMBER>1921  Remove rememberable from users
10:33:46    up<PHONE_NUMBER>4354  Add admin flag to users
10:33:46    up<PHONE_NUMBER>4747  Add indices for user
10:33:46   down<PHONE_NUMBER>1259  Create permissions
10:33:46   down<PHONE_NUMBER>5328  Devise invitable add to users

We had deployed a branch with migrations removed, set up the database, and then tried deploying the app with migrations.
This didn’t work, since rails thought the migrations were new/down and tried to run them (as above), which isn’t what we wanted.
The fix was to:

deploy the release of signon without migrations
re-setup the db: govuk_setenv signon bundle exec rake db:schema:load DISABLE_DATABASE_ENVIRONMENT_CHECK=1
deploy with migrations (no migrations actually ran)

The result of db:schema:load meant that all migrations present in the db/migrations directory at the time of setting up the db are assumed to have already run (marked as up), which prevents them from being run again:
10:40:02  Status   Migration ID    Migration Name
10:40:02 --------------------------------------------------
10:40:02    up<PHONE_NUMBER>0458  Devise create users
10:40:02    up<PHONE_NUMBER>0534  Make users suspendable
10:40:02    up<PHONE_NUMBER>0725  Create doorkeeper tables
10:40:02    up<PHONE_NUMBER>4033  Add name to users
10:40:02    up<PHONE_NUMBER>4527  Add uid to users
10:40:02    up<PHONE_NUMBER>1921  Remove rememberable from users
10:40:02    up<PHONE_NUMBER>4354  Add admin flag to users
10:40:02    up<PHONE_NUMBER>4747  Add indices for user
10:40:02    up<PHONE_NUMBER>1259  Create permissions
10:40:02    up<PHONE_NUMBER>5328  Devise invitable add to users
10:40:02    up<PHONE_NUMBER>2849  Insert permissions data


How to apply custom rule to a nested property

This is the json schema being used:
{
    "$schema": "http://json-schema.org/draft-04/schema#",

    "type": "object",

    "properties": {
        "Components": {
            "type": "array",
            "items": {
                "$ref": "#/definitions/Component"
            },
            "minItems": 0
        }
    },
    "required": ["Components"],
    "additionalProperties": false,

    "definitions": {
        "Component": {
            "type": "object",

            "properties": {
                "Code": {
                    "type": "string"
                },
                "Name": {
                    "nullable": true,
                    "type": "string"
                },
                "Installer": {
                    "$ref": "#/definitions/InstallationType"
                },

            "required": ["Code", "Name", "Installer"],
            "additionalProperties": false
        },

        "InstallationType": {
            "type": "object",
            "properties": {
                "Code": {
                    "$ref": "#/definitions/InstallationTypeCode"
                },
                "EffectiveDate": {
                    "type": "string"
                },
                "EffectiveEndDate": {
                    "nullable":true,
                    "$ref": "#/definitions/EffectiveEndDate"
                }
            },

            "required": ["Code", "EffectiveDate", "EndDate"],
            "additionalProperties": false
        },

        "EffectiveEndDate": {
            "nullable": true,
            "type": "string"
        },

        "InstallationTypeCode": {
            "type": "string"
        },
    }
}

I added a custom annotator with a following method which adds  JsonInclude.Include.ALWAYS to a property in the pojo.
 @Override
    public void propertyField(JFieldVar field, JDefinedClass clazz, String propertyName, JsonNode propertyNode) {
        JsonNode nullable = propertyNode.get("nullable");
        if (nullable != null && nullable.asBoolean()) {
            field.annotate(JsonInclude.class).param("value", JsonInclude.Include.ALWAYS);
        }
    }

Now when the pojo is generated, it adds JsonInclude.Include.ALWAYS annotation to name property inside the component pojo but it didn't add that annotation to the EffectiveEndDate field in the Installer pojo.
Any thoughts/pointers will be appreciated.

I can't explain this. The $ref will cause the entire contents to be replaced at the point the $ref is used, so you should only need "nullable": true in the target of the $ref. Since you have "nullable": true there too, I can't explain why it's not showing.

I was able to fix this issue by removing $ref and directly replacing the $ref with its content and adding "nullable:true" to it.
Many thanks for your response.


fixing typos and update light-clients.md

I love Avail, I've edited a few details I spotted while reviewing documents to make them look more organized and professional!

Thanks @anil2ec4, these aren't "typos" but intentional syntax to present admonitions.

I thought it would look more organized this way. I wanted to contribute!


Router controller updates

Updated router config to export and endpoints state file which holds all known controller ctrl channels. This gets updated as new controllers are added

This will send out any known ctrl channel address to a router when it connects (if raft is not enabled it will send just the one controller's address).
Whenever a new controller is brought online the "main" controller's routers will get immediate updates. Once the raft consensus goes through it will trigger updates on each other controller's routers.

Overall looks reasonable, lots of nitpicks :)


Benchmark with ScalaMeter

build.sbt udpated

Scalameter only support Scala 2.13 which can be compatible but not recommended with Scala 3.


[crate.io] links are broken.

on crates.io which is linked from the badge both the repo and the doc links are dead.  they lead to gh 404 pages.

Thank you for the report! Now, they are fixed!


Customise the service name to support CI at Scale

What
Currently the service name is hardcoded with the jenkins service name
See https://github.com/jenkinsci/opentelemetry-plugin/blob/390ad7d1c156dff037219a018c99cd65a949e71b/src/main/java/io/jenkins/plugins/opentelemetry/opentelemetry/resource/JenkinsResourceProvider.java#L33-L38 and https://github.com/jenkinsci/opentelemetry-plugin/blob/b355859fa093dc5da00a1639d5d11d0d84427b2f/src/main/java/io/jenkins/plugins/opentelemetry/semconv/JenkinsOtelSemanticAttributes.java#L79-L87
Let's support a customise option when configuring the OpenTelemetry to set what's the service name to be used.
Why
Several Jenkins coordinators to report to the same obs11 backend might clash if they have the same Jobs for any reason.
Proposals
Given the Jenkins URL then calculate the service name
Given the Jenkins URL https://foo.domain.com then creates the service name: foo.domain.com
Pros:

Delegate the responsability to the plugin to decide the name based on the Jenkins URL.

Cons:

If JenkinsURL is too verbose (IP address, k8s namespaces...) then  it might be less user friendly.
No customisation.

Provide a global settings to override the service name
Given a Global Settings called serviceName, with default value Jenkins, then update the service name.
Pros:

User friendly
More customisation.

Cons:

Service name might not match with the Jenkins URL.

Another option ??

What about having multiple options?

Manually specified, defaulting to "jenkins" as is now
Dynamic based on URL using something like grok to extract parts you want and combine them into service name

thanks @skundrik for the feedback.
for 1) I've got something in place, see https://github.com/jenkinsci/opentelemetry-plugin/pull/97
for the 2), would you mind if I ask you to elaborate a bit more how you foresee it?
Thanks


[fix] [broker] Fix broker deadlock to add timeout on blocking call during bk-client creation

Fixes https://github.com/apache/pulsar/issues/22840

Main Issue: #22840
Motivation
This PR addresses the third issue discussed in #22840
Currently, Bk-client has multiple blocking calls with metadata-store and doesn't have a timeout. introducing timeout and retry helps the bk-client break the deadlock and complete the execution path.
"metadata-store-10-1" #25 prio=5 os_prio=0 cpu=7574.38ms elapsed=703.54s tid=0x00007fafdd884ed0 nid=0x37eb waiting for monitor entry  [0x00007fae8f9d3000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(java.base@11.0.19/ConcurrentHashMap.java:1723)
        - waiting to lock <0x00001000f4a02bc0> (a java.util.concurrent.ConcurrentHashMap$ReservationNode)
        at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.asyncOpen(ManagedLedgerFactoryImpl.java:365)
        at org.apache.pulsar.broker.service.BrokerService.lambda$createPersistentTopic$66(BrokerService.java:1533)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$644/0x00007facb91c8040.accept(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@11.0.19/CompletableFuture.java:753)
        at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@11.0.19/CompletableFuture.java:731)
        at java.util.concurrent.CompletableFuture.thenAccept(java.base@11.0.19/CompletableFuture.java:2108)
        at org.apache.pulsar.broker.service.BrokerService.createPersistentTopic(BrokerService.java:1514)
        at org.apache.pulsar.broker.service.BrokerService.lambda$checkOwnershipAndCreatePersistentTopic$60(BrokerService.java:1472)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$634/0x00007facb91c6968.accept(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@11.0.19/CompletableFuture.java:753)
        at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@11.0.19/CompletableFuture.java:731)
        at java.util.concurrent.CompletableFuture.thenAccept(java.base@11.0.19/CompletableFuture.java:2108)
        at org.apache.pulsar.broker.service.BrokerService.checkOwnershipAndCreatePersistentTopic(BrokerService.java:1470)
        at org.apache.pulsar.broker.service.BrokerService.lambda$loadOrCreatePersistentTopic$57(BrokerService.java:1437)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$492/0x00007facc317a960.run(Unknown Source)
        at java.util.concurrent.CompletableFuture$UniRun.tryFire(java.base@11.0.19/CompletableFuture.java:783)
        at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.19/CompletableFuture.java:506)
        at java.util.concurrent.CompletableFuture.complete(java.base@11.0.19/CompletableFuture.java:2073)
        at org.apache.pulsar.metadata.coordination.impl.LockManagerImpl.lambda$acquireLock$1(LockManagerImpl.java:105)
        at org.apache.pulsar.metadata.coordination.impl.LockManagerImpl$$Lambda$613/0x00007facbf1d9d08.run(Unknown Source)
        at java.util.concurrent.CompletableFuture$UniRun.tryFire(java.base@11.0.19/CompletableFuture.java:783)
        at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.19/CompletableFuture.java:506)
        at java.util.concurrent.CompletableFuture.complete(java.base@11.0.19/CompletableFuture.java:2073)
        at org.apache.pulsar.metadata.coordination.impl.ResourceLockImpl.lambda$acquire$2(ResourceLockImpl.java:128)
        at org.apache.pulsar.metadata.coordination.impl.ResourceLockImpl$$Lambda$611/0x00007facbdc40040.run(Unknown Source)
        at java.util.concurrent.CompletableFuture$UniRun.tryFire(java.base@11.0.19/CompletableFuture.java:783)
        at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.19/CompletableFuture.java:506)
        at java.util.concurrent.CompletableFuture.complete(java.base@11.0.19/CompletableFuture.java:2073)
        at org.apache.pulsar.metadata.coordination.impl.ResourceLockImpl.lambda$acquireWithNoRevalidation$6(ResourceLockImpl.java:167)
        at org.apache.pulsar.metadata.coordination.impl.ResourceLockImpl$$Lambda$609/0x00007facbdc42908.accept(Unknown Source)
        at java.util.concurrent.CompletableFuture$UniAccept.tryFire(java.base@11.0.19/CompletableFuture.java:714)
        at java.util.concurrent.CompletableFuture.postComplete(java.base@11.0.19/CompletableFuture.java:506)
        at java.util.concurrent.CompletableFuture.complete(java.base@11.0.19/CompletableFuture.java:2073)
        at org.apache.pulsar.metadata.impl.ZKMetadataStore.handlePutResult(ZKMetadataStore.java:225)
        at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$7(ZKMetadataStore.java:182)
        at org.apache.pulsar.metadata.impl.ZKMetadataStore$$Lambda$160/0x00007fae8db950b0.run(Unknown Source)
        at java.util.concurrent.Executors$RunnableAdapter.call(java.base@11.0.19/Executors.java:515)
        at java.util.concurrent.FutureTask.run(java.base@11.0.19/FutureTask.java:264)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(java.base@11.0.19/ScheduledThreadPoolExecutor.java:304)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.19/ThreadPoolExecutor.java:1128)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.19/ThreadPoolExecutor.java:628)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(java.base@11.0.19/Thread.java:829)

"pulsar-io-4-32" #166 prio=5 os_prio=0 cpu=429.42ms elapsed=701.77s tid=0x00007facc80314b0 nid=0x3881 waiting on condition  [0x00007facc73f4000]
   java.lang.Thread.State: WAITING (parking)
        at<EMAIL_ADDRESS>Method)
        - parking to wait for  <0x00001000f838ac60> (a java.util.concurrent.CompletableFuture$Signaller)
        at java.util.concurrent.locks.LockSupport.park(java.base@11.0.19/LockSupport.java:194)
        at java.util.concurrent.CompletableFuture$Signaller.block(java.base@11.0.19/CompletableFuture.java:1796)
        at java.util.concurrent.ForkJoinPool.managedBlock(java.base@11.0.19/ForkJoinPool.java:3128)
        at java.util.concurrent.CompletableFuture.waitingGet(java.base@11.0.19/CompletableFuture.java:1823)
        at java.util.concurrent.CompletableFuture.get(java.base@11.0.19/CompletableFuture.java:1998)
        at org.apache.pulsar.bookie.rackawareness.BookieRackAffinityMapping.setConf(BookieRackAffinityMapping.java:121)
        - locked <0x00001000f8389698> (a org.apache.pulsar.bookie.rackawareness.BookieRackAffinityMapping)
        at org.apache.bookkeeper.client.RackawareEnsemblePlacementPolicyImpl.initialize(RackawareEnsemblePlacementPolicyImpl.java:265)
        at org.apache.pulsar.bookie.rackawareness.IsolatedBookieEnsemblePlacementPolicy.initialize(IsolatedBookieEnsemblePlacementPolicy.java:105)
        at org.apache.pulsar.bookie.rackawareness.IsolatedBookieEnsemblePlacementPolicy.initialize(IsolatedBookieEnsemblePlacementPolicy.java:51)
        at org.apache.bookkeeper.client.BookKeeper.initializeEnsemblePlacementPolicy(BookKeeper.java:581)
        at org.apache.bookkeeper.client.BookKeeper.<init>(BookKeeper.java:505)
        at org.apache.bookkeeper.client.BookKeeper$Builder.build(BookKeeper.java:306)
        at org.apache.pulsar.broker.BookKeeperClientFactoryImpl.create(BookKeeperClientFactoryImpl.java:87)
        at org.apache.pulsar.broker.ManagedLedgerClientFactory.lambda$initialize$0(ManagedLedgerClientFactory.java:95)
        at org.apache.pulsar.broker.ManagedLedgerClientFactory$$Lambda$1006/0x00007facb41b1440.apply(Unknown Source)
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(java.base@11.0.19/ConcurrentHashMap.java:1705)
        - locked <0x00001000f3c03a28> (a java.util.concurrent.ConcurrentHashMap$ReservationNode)
        at org.apache.pulsar.broker.ManagedLedgerClientFactory.lambda$initialize$1(ManagedLedgerClientFactory.java:93)
        at org.apache.pulsar.broker.ManagedLedgerClientFactory$$Lambda$202/0x00007fae1e73e9b0.get(Unknown Source)
        at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.lambda$asyncOpen$6(ManagedLedgerFactoryImpl.java:369)
        at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl$$Lambda$660/0x00007facb91ecd60.apply(Unknown Source)
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(java.base@11.0.19/ConcurrentHashMap.java:1705)
        - locked <0x00001000f4a02bc0> (a java.util.concurrent.ConcurrentHashMap$ReservationNode)
        at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.asyncOpen(ManagedLedgerFactoryImpl.java:365)
        at org.apache.pulsar.broker.service.BrokerService.lambda$createPersistentTopic$66(BrokerService.java:1533)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$644/0x00007facb91c8040.accept(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@11.0.19/CompletableFuture.java:753)
        at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@11.0.19/CompletableFuture.java:731)
        at java.util.concurrent.CompletableFuture.thenAccept(java.base@11.0.19/CompletableFuture.java:2108)
        at org.apache.pulsar.broker.service.BrokerService.createPersistentTopic(BrokerService.java:1514)
        at org.apache.pulsar.broker.service.BrokerService.lambda$checkOwnershipAndCreatePersistentTopic$60(BrokerService.java:1472)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$634/0x00007facb91c6968.accept(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniAcceptNow(java.base@11.0.19/CompletableFuture.java:753)
        at java.util.concurrent.CompletableFuture.uniAcceptStage(java.base@11.0.19/CompletableFuture.java:731)
        at java.util.concurrent.CompletableFuture.thenAccept(java.base@11.0.19/CompletableFuture.java:2108)
        at org.apache.pulsar.broker.service.BrokerService.checkOwnershipAndCreatePersistentTopic(BrokerService.java:1470)
        at org.apache.pulsar.broker.service.BrokerService.lambda$loadOrCreatePersistentTopic$57(BrokerService.java:1437)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$492/0x00007facc317a960.run(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniRunNow(java.base@11.0.19/CompletableFuture.java:815)
        at java.util.concurrent.CompletableFuture.uniRunStage(java.base@11.0.19/CompletableFuture.java:799)
        at java.util.concurrent.CompletableFuture.thenRun(java.base@11.0.19/CompletableFuture.java:2121)
        at org.apache.pulsar.broker.service.BrokerService.loadOrCreatePersistentTopic(BrokerService.java:1433)
        at org.apache.pulsar.broker.service.BrokerService.lambda$getTopic$31(BrokerService.java:1014)
        at org.apache.pulsar.broker.service.BrokerService$$Lambda$476/0x00007facc3057108.apply(Unknown Source)
        at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap$Section.put(ConcurrentOpenHashMap.java:404)
        at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap.computeIfAbsent(ConcurrentOpenHashMap.java:238)
        at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:1013)
        at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:978)
        at org.apache.pulsar.broker.service.BrokerService.lambda$getOrCreateTopic$29(BrokerService.java:973)

This PR has unit-test which fails with single thread and it can be fixed by providing multiple threads into callback processing.
Modifications
Allow metadata-store to use multiple callback threads to avoid deadlock situation in broker.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

I don't think adding the timeout here would be very helpful.
If there is a deadlock, there would be still be a deadlock with the timeout. Just it would be unblocked after 30 seconds, until it happens again.
Though it would be making debugging this issue pretty much impossible. (Since you would be looking at: why is the system slow? and you wouldn't be able to capture the stack traces that would lead to fix the root cause of the deadlock).


Use HttpClientFactory when fetching feeds

Make HTTP requests using IHttpClientFactory in ASP.NET Core | Microsoft Learn

This should help with recent DNS issues: https://sentry.io/share/issue/cf367201fb444074b3c274ed78aab67c/


More explanation needed for Flow Frequency

For the flow frequency the documentation is not clear. If I user a manual trigger like HTTP Request trigger, can I fire it off as many runs as the pricing tier allows me? Or will there be a delay of 15min between the actual running of a flow when the flow is kicked off by manual trigger like the HTTP request?

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

ID: 1947fd4e-170f-6392-e309-5fd05082ffb8
Version Independent ID: 79ccd9e1-0998-bc4e-004c-ffbe57291196
Content: Billing and metering questions - Microsoft Flow
Content Source: flow-docs/billing-questions.md
Service: flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@nicojdejong You can fire it as many times as the pricing tier allows. Thanks for using Microsoft Flow.
-Deon


Ability to jump "through" one model to another on M:N relationships

Problem
Once again this idea is inspired by Ruby on Rails. ;) ActiveRecord (the ORM library that ships with Rails) has the concept of a "has many through" relationship. That is, one record has many associated records through another record inbetween.
For example, let's say you have a Car which gets regular Service. The record of that car getting a service is handled by the Maintenance model, which records which car, which service, the date it was performed, and maybe the employee who performed the job. We could model this in schema.prisma like so (thanks to @pantharshit00 on Slack for working up the schema):
model Car {
  id          Int        @default(autoincrement()) @id
  make        String
  model       String
  year        Int
  maintenance Maintenance[]
}

model Service {
  id          Int        @default(autoincrement()) @id
  name        String
  maintenance Maintenance[]
}

model Employee {
  id              Int        @default(autoincrement()) @id
  name            String
  maintenanceDone Maintenance[]
}

model Maintenance {
  id          Int      @default(autoincrement()) @id
  car         Car      @relation(fields: [carId], references: [id])
  service     Service  @relation(fields: [serviceId], references: [id])
  employee    Employee @relation(fields: [employeeId], references: [id])
  carId       Int
  serviceId   Int
  employeeId  Int
  performedAt DateTime @default(now())
}

Getting the Maintenance records on a Car is pretty easy:
prisma.car.findOne({ where: { id: 123 } }).maintenance()

But what if I wanted the Service records associated with the car? Right now it would be something like:
prisma.car.findMany({
    include: {
      maintenance: {
        select: {
          service: true,
        },
      },
    },
  })

But what if you could simplify that syntax with the idea of the "has many through" relationship relationship: A Car has many Service records through Maintenance records.
It would be amazing if you could get to those records using the same, simple syntax:
prisma.car.findOne({ where: { id: 123 } }).service()

Solution
Perhaps an extra parameter can be passed to @relation somehow denoting that the records are reached through another? You give it the name of another field you've already defined on the model, like maintenance:
model Car {
  id          Int        @default(autoincrement()) @id
  make        String
  model String
  year Int
  maintenance Maintenance[]
  service Service[] @relation(through: maintenance)
}

Since we already have the definition of how a Service relates to a Maintenance in the Maintenance model there's no need to repeat the other relation arguments.
Additional context
Here's some Rails documentation on has-many-through: https://guides.rubyonrails.org/association_basics.html#the-has-many-through-association
What do you think? Is it crazy enough to work?

@cannikin Checkout this: https://www.prisma.io/docs/concepts/components/prisma-schema/relations#many-to-many-relations

@arefaslani Thanks for the link! That's the standard many-to-many syntax, which is fine. For example, a BlogPost has many Comments, which works just fine: const comments = db.blogPost.findOne({ where: { id: 1234 } }).comments()
This introduces third (or more) levels of relationships, all accessible from the parent model, where maybe a Comment has one Author. What if I want to get all the comment authors via the BlogPost? That's where has-many-through comes into play. Prisma would have to add some kind of syntax to let me just do something like: const authors = db.blogPost.findOne({ where: { id: 1234 } }).commentAuthors()

@cannikin Yeah I encountered the same problem you described... I think it's a must have feature.

Simplified version in accordance with rails has_many through document.
schema
model Physician {
  id           Int           @id @default(autoincrement())
  name         String
  appointments Appointment[]
}

model Patient {
  id           Int           @id @default(autoincrement())
  name         String
  appointments Appointment[]
}

model Appointment {
  id           Int       @id @default(autoincrement())
  physician    Physician @relation(fields: [physician_id], references: [id])
  physician_id Int
  patient      Patient   @relation(fields: [patient_id], references: [id])
  patient_id   Int

  appointment_date DateTime @default(now())
}

insert records to all tables
  const patient_1 = await prisma.appointment.create({
    data: {
      patient: {
        create: { name: "patient_1" },
      },
      physician: {
        create: { name: "physician_1" },
      },
    },
  });
  await prisma.appointment.create({
    data: {
      patient: {
        create: { name: "patient_2" },
      },
      physician: {
        connect: { id: patient_1.id },
      },
    },
  });

To get patients served by a specific physician (=physician_1),
  const physician = await prisma.physician.findFirst({
    where: { name: "physician_1" },
    include: { appointments: true },
  });

  const patients = await prisma.patient.findMany({
    where: {
      id: {
        in: physician.appointments.map((appointment) => appointment.patient_id),
      },
    },
  });

  console.log(patients);     => [ { id: 1, name: 'patient_1' }, { id: 2, name: 'patient_2' } ]

I want to above as follows without removing intermediate model from schema. Rails can do.
const physician = await prisma.physician.findFirst({
    where: { name: "physician_1" },
    include: { ??? },
  });

console.log(physician.patients);

we want has many through as well!

Bumping, has_many: through in rails is really nice. I noticed https://github.com/prisma/prisma/issues/7351 is similar to this ticket, but the attached PR is all-or-nothing for disabling fks. I want a specific has_many: through rails like syntax in Prisma for join table querying. It's kind of a pain querying without it.

Do not know if this helps but the Laravel framework also has the similar concept of has many through relationships https://laravel.com/docs/8.x/eloquent-relationships#has-many-through. Would be great to have the same feature in Prisma.

Any update on this? I'm also interested on this feature. Any ways we can help further? https://github.com/prisma/prisma/issues/4910

Just to keep thread alive.. This would be an awesome feature to have.
Also, really like the proposal approach.

+1, this would be a great feature to have. I'm coming to Prisma from Elixir-land and so far a through association is the only thing I'm missing (I am very thankful for Prisma's succinctness and its SQL migrations).
The @relation(through: intermediaryRecord) way of declaring the relationship on the schema is the clearest version of this to my mind, e.g. service Service[] @relation(through: maintenance) from @cannikin 's post.
Like in Rubyland, Elixir's Ecto schema syntax also has :through declarations for both has_many and has_one relationships, which are very helpful when writing concise queries for such data.
From the docs:
  use Ecto.Schema

  schema "posts" do
    # In the has_many :through example below, the `:comments`
    # in the list [:comments, :author] refers to the
    # `has_many :comments` in the Post own schema and the
    # `:author` refers to the `belongs_to :author` of the
    # Comment's schema (the module below).
    # (see the description below for more details)
    has_many :comments_authors, through: [:comments, :author]

    # Specify the association with custom source
    has_many :tags, {"posts_tags", Tag}
  end

  schema "comments" do
    belongs_to :author, Author
    belongs_to :post, Post
    has_one :post_permalink, through: [:post, :permalink]
  end

I have a Post from the schema above that has_many Comments, and those Comments belong_to Authors
A single post has_many :comments_authors through comments

The two ways to take advantage of this when querying are:

Via a query preload: field, e.g. preload: [:comments_authors], which in this case would return my Post, its  CommentsAuthors, and their Comments as if doing a comprehensive join under the hood.
Via querying only a record's associated CommentsAuthors, e.g. authors = Repo.all assoc(post, :comments_authors) would return only a post's CommentsAuthors.

Just to throw another idea in there to keep this alive. It's a little bit more verbose than prior suggestions, but keeps the data schema very opaque.
model User {
  id               Int               @id @default(autoincrement())
  groupMemberships GroupMembership[]
  groups           Group[]           @through(field: 'groupMemberships', references: 'group')
}

model Group {
  id Int @id @default(autoincrement())
}

model GroupMembership {
  id      Int   @id @default(autoincrement())
  user    User  @relation(fields: [userId], references: [id])
  userId  Int
  group   Group @relation(fields: [groupId], references: [id])
  groupId Int
}

const user = await client.user.findUnique({
   where: { id: 1 },
   include: { groups: true }
})

i’d also love this!! has anyone found any workarounds?

+1 super keen on this

Also finding myself wanting a "has-one-through" relationship!

+1!

Would love this feature as well!

+1 Keeping this alive :)

I think the above proposals/ideas aren't perfect. In one of my Laravel project i've a media table. which stores all the files. product (different types of) images, videos, users avatars, store banner & logo etc. When I give a file to that, the model (before saving) automatically (ofcourse i've configured it) parses all the necessary (to project needs) meta data. like mime type, extension, file size, where the actual file is stored (system can store various types of files in different servers). When querying, this also construct appropriate full url of the file too.

Is this still open?


Improved docs

Also added Iterator() and MinMax() methods
Plus various nil protections and Mapper / Reducer now panic if no Converter / Accumulator is supplied

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (8fa4fa4) compared to base (703f2a3).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##              main        #7    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           11        11
  Lines          819      1020   +201
==========================================
+ Hits           819      1020   +201

Impacted Files
Coverage Δ

accumulator.go
100.00% <100.00%> (ø)

comparator.go
100.00% <100.00%> (ø)

consumer.go
100.00% <100.00%> (ø)

converter.go
100.00% <100.00%> (ø)

mapper.go
100.00% <100.00%> (ø)

predicate.go
100.00% <100.00%> (ø)

reducer.go
100.00% <100.00%> (ø)

stream.go
100.00% <100.00%> (ø)

streamable.go
100.00% <100.00%> (ø)

streamable_slice.go
100.00% <100.00%> (ø)

... and 1 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


⚠ GitLab Server has degraded performance

In 3017d94, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6863 ms

Resolved: GitLab Server performance has improved in cc608bc.


multiple crontab entries after --update-crontab

Hi i would like to ask if this is the intended behavior of whenever, because it is a bit confusing for me:
When i run whenever from inside a soft link directory without setting the identifier flag -i , it gets multiple crontab entries if the symlink changes :(   /app/current -> app/releases/**
config/deploy.rb
"cd '/app/current' && RAILS_ENV=production bundle exec whenever --update-crontab --set 'path=/app/current/'"

Since the app/current dir  is a symlink then the  crontab file get the default values after each deployment
 # Begin Whenever generated tasks for: /app/releases/1
 # Begin Whenever generated tasks for: /app/releases/2
 # Begin Whenever generated tasks for: /app/releases/3
...etc

cd /app/current
pwd   : /app/current
pwd -P : /app/releases/**

lib/whenever.rb
Dir.pwd :/app/releases/**

what is the point to generate different cron jobs for the same schedule that always exists in the same full path directory /app/current/config/schedule.rb ?
in order to have the intended behavior i have to manually set the idintifier to a static string
"whenever -i '/app/current' --update-crontab --set 'path=/app/current/'"

Whenever cannot know that your schedule is at that symlinked path. It could also be at many others. You'll have to set a static identifier.


[Azure.Core] Update testing to use the same patterns in all strings

having a convention for all of these strings. Something along the lines of
Model/ModelWire.json
Model/ModelJson.json
Model/ExpectedWire.json
Model/ExpectedJson.json
From this convention the ModelTests base class could simply load all of those files and do all comparisons.

https://github.com/Azure/azure-sdk-for-net/pull/38169#discussion_r1308065364


ListEventGroup API response is slow, when no CEL filter or keyword search results are found

Describe the bug
When the ListEventGroup API cannot find results, the response time increases significantly, taking up to 54 seconds. However, when results are found, the API responds almost instantly (within milliseconds).
We made only one call from Origin Reports Adaptor (screenshot below) but we noticed 3 request to Kingdom log(screenshot below) for the same single request which returns the same result within 600 ms.
Kingdom Log:

Origin Reports Adaptor Log

Steps to reproduce

Login to Origin Platform
Go to Campaign group page
Search for Event Groups without any filters and the EGs not found in UI
Click on “Search“ button to call listeventgroup API

Component(s) affected
Kingdom, Reporting Server
Version
Halo 5.11
Environment
Origin Stage & PROD Environment
Additional context
attached log screenshot above.

We made some performance enhancements to ListEventGroups in v0.5.13 as part of fixing a previous simulator issue. See #1923. Feel free to reopen if you still see the same problem after upgrading past that version.
As an aside, all issues filed here should be in the context of Halo software only. This means that the "Step to reproduce" should only cover parts of Halo. For the purposes of filing issues here, assume that the Origin UI doesn't exist.


Add section 3-impact HTML and CSS code

Add section 3-impact HTML and CSS code
close #26
Checklists
General Checks

[ ] the branch is up to date with main/master
[ ] the code works when pulled and run locally
[ ] All CI checks pass
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[ ] PR it is assigned to the owner
[ ] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[ ] the markdown source is formatted
[ ] spelling and grammar is correct in all text
[ ] The markdown looks correct when you preview the file
[ ] all links and images work

HTML

[ ] the code is well-formatted
[ ] the HTML code passes validation
[ ] there are no inline styles (example: style='color: red;')
[ ] there are no <style> tags with CSS, all styles are hrefs
[ ] there is no inline JavaScript (example: onclick='doSomething()')
[ ] there are no <script> tags with JS, all JS is in an separate file
[ ] ids are used for JavaScript only, not for CSS
[ ] semantic tags are used
[ ] spelling and grammar is correct in all site content

CSS

[ ] the code is well-formatted
[ ] passes all the linting checks

I tried to fix "lint checks" problems. When I sent the 1st PR, the details looks like this.

I fixed some of the problems, and now the details looks like this.

How to fix these problems now? I don't understand the  clue. I need help. 😢

Problem solved. Read the clue in details and be patient. 😄

Your PR passes the lint check @AlinaTaoRao great 👍

@sannesofie
Thanks. After I fixed problems in HTML and CSS one by one.


Added no prorate and billing cycle anchor setters for subscription swapping.

This is a little update that allows you to set prorate and billing_cycle_anchor when swapping a subscription plan.
Usage is:
$user->subscription()->noProrate()->billingCycleAnchor("now")->swap($stripe_plan);
I proposed this need way back in 2014 on this pull request: https://github.com/laravel/cashier/pull/88
It looks like it was implemented elsewhere: https://github.com/laravel/cashier/pull/210
But subsequently dropped in Cashier 6.0 (along with noProrate()) unless I'm massively overlooking something.

I think you could send this to 6.0 branch.

@taylorotwell OK great. I've done this here: https://github.com/laravel/cashier/pull/285


'bundle outdated --group' not working as expected

Hello, I'm encountering some strange behavior with the bundle outdated command, and first and foremost I would like to know if this really is a bug or an expected behavior.

Having an outdated rubocop gem in my Gemfile:
gem 'rubocop', groups: [:development, :test]

The command you ran
bundle outdated --group test
What you expected to happen
the gem rubocop is listed as outdated.
What actually happened
the gem rubocop was not listed as outdated.

So, here is my assumption:
When I write
gem 'rubocop', groups: [:development, :test]

or
group :development, :test do
  gem 'rubocop'
end

I expect that bundler will consider that the gem is in two separate groups, as if it were declared like this:
gem 'rubocop', :group => :development
gem 'rubocop', :group => :test

I searched the github docs and the bundler.io docs and it did not became clear to me if my assumption is correct.
Some more examples

Having an outdated rubocop gem in my Gemfile:

gem 'rubocop', groups: [:development, :test]

when I run:
bundle outdated
the gem is correctly listed

Having an outdated rubocop gem in my Gemfile:

gem 'rubocop', groups: [:development, :test]

when I run:
bundle outdated --group development
the gem is correctly listed

Having an outdated rubocop gem in my Gemfile:

gem 'rubocop', groups: [:development, :test]

when I run:
bundle outdated --group test
the gem is not listed

I also created an automated test(https://github.com/emilianoLeite/bundler/commit/e6e8d4b034390150fe26dcd3ff9cfc4b0e34da55) to confirm this behavior.
The output of said automated test is as follows:
bundler|fix-outdated-group ⇒ rspec spec/commands/outdated_spec.rb:74
Could not find 'automatiek' (~> 0.1.0) among 31 total gem(s)
Checked in 'GEM_PATH=/Users/codus/.rvm/gems/ruby-2.3.3@bundle:/Users/codus/.rvm/gems/ruby-2.3.3@global', execute `gem env` for more information (Gem::MissingSpecError)
Could not find 'mustache' (= 0.99.6) among 31 total gem(s)
Checked in 'GEM_PATH=/Users/codus/.rvm/gems/ruby-2.3.3@bundle:/Users/codus/.rvm/gems/ruby-2.3.3@global', execute `gem env` for more information (Gem::MissingSpecError)
Could not find 'rdiscount' (~> 2.2) among 31 total gem(s)
Checked in 'GEM_PATH=/Users/codus/.rvm/gems/ruby-2.3.3@bundle:/Users/codus/.rvm/gems/ruby-2.3.3@global', execute `gem env` for more information (Gem::MissingSpecError)
Could not find 'ronn' (~> 0.7.3) among 31 total gem(s)
Checked in 'GEM_PATH=/Users/codus/.rvm/gems/ruby-2.3.3@bundle:/Users/codus/.rvm/gems/ruby-2.3.3@global', execute `gem env` for more information (Gem::MissingSpecError)
Install the ronn gem to build the help pages
man:build ran for   0.000000   0.000000   0.000000 (  0.000103)
Run options:
  include {:locations=>{"./spec/commands/outdated_spec.rb"=>[74]}}
  exclude {:bundler=>"=< 2.0", :rubygems_master=>true, :git=>"=< 2.11.0", :rubygems=>"=< 2.6.11", :ruby=>"=< 2.3.3", :realworld=>true, :sudo=>true}

bundle outdated
  with --group option
    not outdated gems
    returns a sorted list of outdated gems from one group => 'default'
    returns a sorted list of outdated gems from one group => 'development'
$ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby -rrubygems -S gem --backtrace generate_index
Generating Marshal quick index gemspecs for 61 gems
.............................................................
Complete
Generated Marshal quick index gemspecs: 0.061s
Generating specs index
Generated specs index: 0.003s
Generating latest specs index
Generated latest specs index: 0.001s
Generating prerelease specs index
Generated prerelease specs index: 0.002s
Compressing indices
Compressed indices: 0.002s
# $? => 0

$ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
  -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
  -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
  /Users/codus/Projects/bundler/exe/bundle install --retry 0 --no-color
Fetching /Users/codus/Projects/bundler/tmp/libs/zebra
Fetching /Users/codus/Projects/bundler/tmp/libs/foo
Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
Resolving dependencies...
Fetching activesupport 2.3.5
Fetching duradura 7.0
Fetching terranova 8
Fetching weakling 0.0.3
Installing weakling 0.0.3
Installing terranova 8
Installing activesupport 2.3.5
Installing duradura 7.0
Bundle complete! 6 Gemfile dependencies, 7 gems now installed.
Bundled gems are installed into `./.bundle`
# $? => 0

$ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
  -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
  -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
  /Users/codus/Projects/bundler/exe/bundle install --retry 0 --no-color
Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
Resolving dependencies...
Bundle complete! 4 Gemfile dependencies, 5 gems now installed.
Bundled gems are installed into `./.bundle`
Removing foo (a427292f2204)
Removing zebra (b875e4b9f775)
# $? => 0

$ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby -rrubygems -S gem --backtrace generate_index
Generating Marshal quick index gemspecs for 64 gems
................................................................
Complete
Generated Marshal quick index gemspecs: 0.106s
Generating specs index
Generated specs index: 0.004s
Generating latest specs index
Generated latest specs index: 0.002s
Generating prerelease specs index
Generated prerelease specs index: 0.000s
Compressing indices
Compressed indices: 0.002s
# $? => 0

$ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
  -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
  -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
  /Users/codus/Projects/bundler/exe/bundle outdated --group test --no-color
Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
Resolving dependencies...

Outdated gems included in the bundle:
# $? => 1
    returns a sorted list of outdated gems from one group => 'test' (FAILED - 1)

Retried examples: 0

Failures:

  1) bundle outdated with --group option returns a sorted list of outdated gems from one group => 'test'
     Failure/Error: expect(gem_list.size).to eq gems_list_size

       expected: 2
            got: 0

       (compared using ==)

       Commands:
       $ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby -rrubygems -S gem --backtrace generate_index
       Generating Marshal quick index gemspecs for 61 gems
       .............................................................
       Complete
       Generated Marshal quick index gemspecs: 0.061s
       Generating specs index
       Generated specs index: 0.003s
       Generating latest specs index
       Generated latest specs index: 0.001s
       Generating prerelease specs index
       Generated prerelease specs index: 0.002s
       Compressing indices
       Compressed indices: 0.002s
       # $? => 0

       $ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
         -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
         -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
         /Users/codus/Projects/bundler/exe/bundle install --retry 0 --no-color
       Fetching /Users/codus/Projects/bundler/tmp/libs/zebra
       Fetching /Users/codus/Projects/bundler/tmp/libs/foo
       Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
       Resolving dependencies...
       Fetching activesupport 2.3.5
       Fetching duradura 7.0
       Fetching terranova 8
       Fetching weakling 0.0.3
       Installing weakling 0.0.3
       Installing terranova 8
       Installing activesupport 2.3.5
       Installing duradura 7.0
       Bundle complete! 6 Gemfile dependencies, 7 gems now installed.
       Bundled gems are installed into `./.bundle`
       # $? => 0

       $ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
         -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
         -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
         /Users/codus/Projects/bundler/exe/bundle install --retry 0 --no-color
       Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
       Resolving dependencies...
       Bundle complete! 4 Gemfile dependencies, 5 gems now installed.
       Bundled gems are installed into `./.bundle`
       Removing foo (a427292f2204)
       Removing zebra (b875e4b9f775)
       # $? => 0

       $ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby -rrubygems -S gem --backtrace generate_index
       Generating Marshal quick index gemspecs for 64 gems
       ................................................................
       Complete
       Generated Marshal quick index gemspecs: 0.106s
       Generating specs index
       Generated specs index: 0.004s
       Generating latest specs index
       Generated latest specs index: 0.002s
       Generating prerelease specs index
       Generated prerelease specs index: 0.000s
       Compressing indices
       Compressed indices: 0.002s
       # $? => 0

       $ /Users/codus/.rvm/rubies/ruby-2.3.3/bin/ruby \
         -I/Users/codus/Projects/bundler/lib:/Users/codus/Projects/bundler/spec -rsupport/hax \
         -r/Users/codus/Projects/bundler/spec/support/artifice/fail \
         /Users/codus/Projects/bundler/exe/bundle outdated --group test --no-color
       Fetching source index from file:/Users/codus/Projects/bundler/tmp/gems/remote2/
       Resolving dependencies...

       Outdated gems included in the bundle:
       # $? => 1
     # ./spec/commands/outdated_spec.rb:98:in `test_group_option'
     # ./spec/commands/outdated_spec.rb:140:in `block (3 levels) in <top (required)>'

Finished in 18.62 seconds (files took 0.70388 seconds to load)
4 examples, 1 failure

Failed examples:

rspec ./spec/commands/outdated_spec.rb:139 # bundle outdated with --group option returns a sorted list of outdated gems from one group => 'test'

So, again: is this a bug or an expected behavior?
If it is a bug, I would be happy to try to fix it 😄 .
Cheers.

https://github.com/bundler/bundler/pull/6116 should fix this!


Add homu webhook

as requested in https://github.com/servo/rust-bindgen/pull/3

@bors-servo r+

I think travis build might fail since llvm apt sources went down not so long ago

I'm looking into the apt thing now.

Merging manually following lars' instructions.


[feature] Add new interaction analysis API

Purpose
This adds functionality to analyze metabolic interactions in already existing outputs from the grow workflow. Functionality is added in the new micom.interaction module and the extended visualizations that go along with those.
Interactions are calculated between a focal taxon (taxon of interest) and all interaction partners by default, but one can also specify arbitrary sets of focal taxa, including all taxa giving all n x n interactions.
Focal interactions
Can be calculated with the interactions command as interactions(results, taxa=[focal taxa]).
All interactions would be obtained with interactions(results, taxa=None). This is relatively slow as all it scales with $|samples|\cdot|metabolites|\cdot|taxa|^2$. If more than one focal taxon is specified it will be parallelized across focal taxa.
For each metabolite M with focal taxon A and interaction partner B this will classify interactions into the following three groups:
provided:    A -> M -> B
received:    A <- M <- B
co-consumed: A <- M -> B

Summaries
The resulting interactions can further be summarized into overall interaction fluxes using the summarize_interactions functions which collapses each focal:partner:group interaction in each sample onto the total flux, total mass flux, total carbon flux, total nitrogen flux, and number of interactions.
Scores
This includes a general framework to calculate and visualize interaction scores. For now I added the MES.
Visualizations
There are new visualizations for focal interactions and the MES score.
@vrmarcelino: Let me know if those make sense. Range of the MES looks similar to the paper.
example visualizations
TODO

[ ] add tests
[ ] add docs

Hi @cdiener
Thanks for adding this feature!
Yes the formula is correct and the values are in the range of what we found.
Let me know if you want me to rub some tests.

Hi @cdiener Thanks for adding this feature! Yes the formula is correct and the values are in the range of what we found. Let me know if you want me to rub some tests.

Awesome, yes it would be great if you could run some tests. You should be able to install this branch in a new python or conda env with
pip install git+https://github.com/micom-dev/micom.git@feature/interaction

Also for the visualizations I currently remove MES scores of 0 so I can show them on a log-scale and to not have too many metabolites with zero scores. Do you think that makes sense or should I include them?

Test done, and it works!
I've re-run the grow workflow for one sample, and calculated MES with MES_res = scores.MES(res) using the new feature.
The MES results are calculated correctly (same MES scores obtained using my scripts with the newly grown community).
I expected some stochasticity with the grow workflow, but the MES results are extremely similar to what we obtained before for that sample, which is reassuring!

Yes I think it makes sense to remove the metabolites with zero scores for the visualisation, but if there is an option to download the .csv file I would leave all MESs in there (as it might be interesting if MES=0 in disease but  >> 1 in health for example).
Thanks for implementing this!

@vrmarcelino Thanks so much for the detailed validation. I would also expect some slight variation due to tolerance cutoffs and solver versions but overall super encouraging agreement. Happy it works.


Some Suggestions

Ability to change shader quality for lower-end PCs.
The ability to add more than one shader and let it choose randomly which one to render.
Port to 1.19.1. (not that important)

EDIT:

An option to save the set rendering quality for certain shaders. For example, if you set a certain shader that's performance intensive to render in lower quality, it will save that option for that specific shader.

Feel free to add any you wish.

His response:
Ok I will address them in order:

Sure, I will add that, probably as a slider
That is an interesting idea, will look into it
Will port as soon as it is feature complete (settings screen, textures)

I probably won't add the number 4. it would get messy considering that shaders are loaded from resource packs, much easier for the end used to just adjust the quality slider


Bug report on 设置MySQL数据源

Contribution guidelines

[X] I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

[X] ... the problem doesn't occur with the server or web themes
[ ] ... the documentation does not mention anything about my problem
[ ] ... there are no open or closed issues that are related to my problem

Description
设置MySQL数据源，“高级-数据库”字段必须带一个？结尾才可以正常设置成功，否则就设置失败，提示“unkown database xxxx”
Expected behaviour
可以正常设置数据库
Actual behaviour
设置MySQL数据源，“高级-数据库”字段必须带一个？结尾才可以正常设置成功，否则就设置失败，提示“unkown database xxxx”
Steps to reproduce
数据源-选择MySQL数据库
Package versions

Java: JDK11

Configuration
系统配置

System information

Operating system: windows
Browser: Microsoft Edge 111

Message that will be displayed on users' first issue

@ldbinac 感谢提供相关信息，我们来复现并修复它


Test: light update in activity bar

[ ] win @michelkaporin
[ ] mac @ramya-rao-a
[ ] linux @alexandrudima

Complexity: 3
To improve our update story we have added a new activity in the bottom of the activity bar. Verify:

clicking on the new icon you are presented with a menu and all actions in that menu make sense and work
once there is an update we show a notification badge in the activity bar and the update action nicely reflects the state (same as the update action in the top app menu)
you are no longer spamed by the message service once there is an update

Please note that this is currently only enabled for insiders as we plan to collect more feedback before we push this out to stable.
Please assign all issues regarding this test plan item to me and @joaomoreno

:+1: The menu entries make sense to me. Also no more annoying popups :heart:


[RN][CI] Add Github Action to add a commit with #run-e2e-tests

Summary:
#41308 introduce the possibility to run e2e tests if a commit contains #run-e2e-tests in the commit message.
This PR builds on top of that, and let users to run e2e tests by adding a comment with with #run-e2e-tests
Changelog:
[Internal] - Allow to run e2e tests from comments
Test Plan:
Not sure it can be tested until the PR is merged... ¯_(ツ)_/¯

#run-e2e-tests


client-js of vue3 [Feature]

Search before asking

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

Description
client-js support vue3.x
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

If you want to submit new feature support, welcome. If not, there is nothing we could track here.
The official issue tracker is for bugs or new features (someone has decided to do)


Repeated errors in the absence of an internet connection

When travelling with my laptop, when without an internet connection I am consistently plagued with the following error while I work on Purescript in atom:

Error: getaddrinfo ENOENT undefined:15118 at Object.exports._errnoException (util.js:856:11) at errnoException (dns.js:31:15) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)

What makes you think this is to do with ide-purescript?
The only network connection this package makes is to localhost, it's possible that that is behaving badly on your system, it's also possible (as far as the stack trace you show) that something else in Atom is causing the issue - there are plenty of things that do make internet connections.

A fair and obvious question, I should have justified better up-front.
Here's what I've discovered:

Under conditions in which the error occurs, I can reliably reproduce it by activating auto-completion (e.g. using ctrl-space) while editing a purescript source file (but not a javascript file for example)
I have not reproduced the error with the ide-purescript package disabled
If there is no internet connection when I start atom I get no errors (a useful work-around at least)
In fact, if there is internet when I start atom but I have not yet opened a purescript source file, I then lose internet and then auto-complete in a purescript file, there is no error i.e.
If there is internet when I first open a purescript file and I then lose internet, auto-completion generates the error
While I lack internet connection (in the presence or absence of errors) I get no auto-completion suggestions in purescript (if the package is disabled I get what I assume are the built-in provider's auto-completion suggestions)
When starting atom with no internet (with a purescript file open) I get the notification that psc-ide-server has been started, then once I connect internet I have to switch tabs to another purescript file, at which point I get a notification that it has connected to an existing psc-ide-server instance, then after a few seconds I get auto-completion suggestions again.

Thanks. What OS are you running? I feel like there's some issue around dns lookup for localhost, that may be slightly system specific.
I've tried and can't reproduce this on my machine :(
Can you try this with https://github.com/kRITZCREEK/pscid ? I imagine this is the same but may eliminate some possibilities. If this behaves the same, can you also try with pscid and manually started psc-ide-server --debug

I'm running Windows 10.
I'm not sure what you mean by "try this" with pscid & I've never used the tool before. If I just run pscid it  fails to start psc-ide-server. If I run psc-ide-server manually then pscid it starts fine and I can build without internet, but then that is also true with ide-purescript; as far as I'm aware it is just auto-completion that errors.
I've not done any atom plugin development, but as I can readily reproduce it I'd be happy to give some debugging a stab given some pointers if you'd like.

The reason I ask is auto-completion makes a connection to psc-ide, just as rebuild does (if you have 'fast rebuild' set, which is now default) (and pscid - BTW I mean to try the file watcher, not the b to build).  Can you try the 'ide-purescript:search' command (^O /)  when autocomplete is erroring and see if it is the same or different?
If only autocomplete is an issue but not search, tooltips, fast build - then it is unlikely to be to do with this package, and instead something to do with autocomplete+ or some other provider.
As for debugging if you open up the developer tools in Atom and manage to break on the exception in question, you may be able to find something interesting.

Ah right. Yes pscid crashes with the same exception on file save and ide-purescript also errors on save with fast-build enabled. Although ide-purescript:search & tooltips don't function in the absence of internet they also do not produce an error pop-up.
It looks to me like this is probably https://github.com/nodejs/node/issues/2237 where sadly the conclusion appears to have been:

I hate windows. why doesn't it just work like unix?

However, it looks like the solution is to install a loopback interface as described here for example. Having done so I seem to have full functionality without error =)
Thanks for your help!


How to update the trust policy for authRole set by UpdateRolesWithIDPFunction?

Amplify CLI Version
12.0.3
Question
Hi there,
To use the attributes for access control with the identity pool, I need to include sts:TagSession in the authRole's trust policy. However the trust policy seems to be modified by a Lambda called UpdateRolesWithIDPFunction after the override of the project level IAM roles is performed. Is there a way to modified the trust policy set by UpdateRolesWithIDPFunction?
My goal is to use principal tags in my S3 bucket policy, as the following:
export function override(
  resources: AmplifyS3ResourceTemplate,
  amplifyProjectInfo: AmplifyProjectInfo
) {
  resources.s3AuthPrivatePolicy.policyDocument.Statement = [
    {
      Effect: "Allow",
      Action: ["s3:PutObject", "s3:GetObject"],
      Resource: [
        {
          "Fn::Join": [
            "",
            [
              "arn:aws:s3:::",
              { Ref: "S3Bucket" },
              "/private/${aws:PrincipalTag/user_id}/*",
            ],
          ],
        },
      ],
    },
  ];
}

I have also configured the principal tags mapping as the following:
export function override(
  resources: AmplifyAuthCognitoStackTemplate,
  amplifyProjectInfo: AmplifyProjectInfo
) {
  resources.addCfnResource(
    {
      type: "AWS::Cognito::IdentityPoolPrincipalTag",
      properties: {
        IdentityPoolId: {
          Ref: "IdentityPool",
        },
        IdentityProviderName: {
          "Fn::Sub": [
            "cognito-idp.${region}.amazonaws.com/${client}",
            {
              region: {
                Ref: "AWS::Region",
              },
              client: {
                Ref: "UserPool",
              },
            },
          ],
        },
        PrincipalTags: {
          app_id: "aud",
          user_id: "sub",
        },
        UseDefaults: false,
      },
    },
    "MyIdentityPoolPrincipalTags"
  );
}

However, I need to manually change the authRole trust policy in the AWS console. Is there a way to automate this?
Thanks!

Hey @sibyl229 :wave: thanks for raising this and apologies for the delay! Are you currently using a project override to modify the authRole policy? This can be created with amplify override project and the authRole should be accessible on resources.authRole

Hi @josefaidt thanks for the reply! I am currently using the project override to override the policy of the authRole. That works fine and wasn't the issue. The issue I have is about the trust relationship policy, and what was set in the override seems to be subsequently replaced by the Lambda called UpdateRolesWithIDPFunction. Any thoughts about that? Thanks!

Thanks @josefaidt ! That makes sense! It might take a while before I try the suggestion. Please feel free to close the issue.


fix(graphic): fix graphic draw bound

fix bound box bug
fix OcclusionSystem not use bug
fix graphic draw bound

CI ray.test failed, something wrong with new changes of Ray


Cleaned up poisson_2d test output.

Actually wait before you merge...I've added a bit more stuff.

@adimako - Please have a look at this to see if you're okay with the changes I made.  I'm trying to organize the test directory and remove files generated by tests.

In that case I believe that the file will not be removed.  There may be another way to handle this, but usual with the class structure the teardown method will remove the files, I just don't have time to refactor this right now.

Hold on a while before you merge...

I checked if moving the delete staments before tests but it is not possible to cover all the cases, not without digging into WT and check at which point files are written. @cekees @alistairbntl is there a way to run a script after test_wavetools that cleans up these files?

Like I said, I think the best approach is to refactor the tests using the class structure in files like proteus/tests/matrix_constructors/test_laplace_TH_2D.py.  I'd be happy to do this at some point, but right now I need to stay focused on something else I'm working on.

Since the tests pass I'm okay with merging as is and creating an issue to refactor and clean it up when somebody has the time.

@alistairbntl go for it

+1.


Library Reference to Library Deploys Twice

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (550c548 2023-02-13T00:04:26.346778Z)
What command(s) is the bug in?
forge script script/Counter.s.sol --rpc-url "$ETH_RPC_URL" --broadcast --sender $ETH_FROM
Operating System
macOS (Apple Silicon)
Describe the bug
Including a reproducible minimal version here: https://github.com/hexonaut/library-issue-example
Read the README in that repo to reproduce. You will see 3 libraries being deployed, but only 2 exist.

We just noticed we're facing the same issue
## Setting up (1) EVMs.
==========================
Simulated On-chain Traces:

  [3777561] → new BorrowLogic@0x3db487975aB1728DB5787b798866c2021B24ec52
    └─ ← 17250 bytes of code

  [1486768] → new BridgeLogic@0xA25d9f14CFA40d3227ED9a48B124667dDFfCFdDD
    └─ ← 6641 bytes of code

  [1582148] → new ConfiguratorLogic@0xfE76366A986B72c3f2923e05E6ba07b7de5401e4
    └─ ← 7095 bytes of code

  [953491] → new EModeLogic@0xAa84D489F71d2A8D71e992143a2dE8B3AA54AAA9
    └─ ← 4171 bytes of code

  [3777561] → new BorrowLogic@0x70Bf6EC6Fca41a7d08dCBB9909985AC0A4510B5E
    └─ ← 17250 bytes of code

  [2011793] → new FlashLoanLogic@0xd1B3E25fD7C8AE7CADDC6F71b461b79CD4ddcFa3
    └─ ← 9072 bytes of code

  [2830299] → new LiquidationLogic@0x1d69c48A35DdD241E72a31dB0E637676d89Fc553
    └─ ← 12866 bytes of code

  [1650301] → new PoolLogic@0x398808Db36da6BA4e30d4Fb88d72c3473921bC6e
    └─ ← 7399 bytes of code

  [2588365] → new SupplyLogic@0x8be473dCfA93132658821E67CbEB684ec8Ea2E74
    └─ ← 11744 bytes of code

  [3870204] → new Pool@0xb04280b09F47cFd81906817505F24ceFE1BA86D2
    └─ ← 17673 bytes of code

For some reason BorrowLogic is deployed twice.
Is there a known workaround.

Fxed with https://github.com/foundry-rs/foundry/pull/5164

The error still exists。

The error still exists。
forge version : forge 0.2.0 (fcae63a 2023-10-08T00:31:37.838144000Z)

The error still exists.
forge version :  forge 0.2.0 (fcae63a 2023-10-08T00:31:37.838144000Z)
source code:
import "./libraries/HeaderBLSVerifier.sol";
import "./libraries/SyncCommitteeRootToPoseidonVerifier.sol";
import "./libraries/SimpleSerialize.sol";

three contract deployed, Two of them are library:


Fix 32-bits warnings

Fix #458

Nice fix but keep in mind that this can broke again at any point.


Add lightning bolt icon (#513)

@pfarejowicz Thanks for the input, I'll chat with my designer and make sure this is the asset they intended.

@pfarejowicz I talked with my designer, and this asset did come from PDS, but apparently something got a little messed up in the compression process. Hopefully this version should be better.

@pfarejowicz I talked with my designer, and this asset did come from PDS, but apparently something got a little messed up in the compression process. Hopefully this version should be better.

@noragrossman can we double check again that the actual SVG file came from the PDS team? It looks better now and renders correctly

but it looks like its not optimized which would have been done by them


Update Ember CLI and other dependencies

@trentmwillis I've bumped ember-cli-mocha version to the latest v0.14.4.
Also changed yes n piping to echo "n" - yes n did not work on my local Mac and seems caused Travis to hang. I suspect root cause could be dist: trusty added to .travis.yml file when I upgraded ember-cli using addon blueprint.

Looks good to me! Thanks a bunch for working on this 😄

FYI, this is now released as<EMAIL_ADDRESS>

@trentmwillis Awesome! Thank you!


Authfix

Fixing the unit authorization problem, so that the creator of a unit is now attached to the unit itself. Also fixed some view issues on the user and unit sides.

I wonder if the access denied is because I did not start with a fresh user. This mostly works but the view of the unit seems to be missing its occupants and there are two random non-link hover thingies at the bottom whose purpose is unclear:

The occupants table should show the name of the occupants who are users. But this may not be the best method to indicate who is in the unit, as not all occupants may be users and so the table will be missing some things. Also users who haven't filled in a name won't display properly. I'll figure this out later.

Huh. One of the recent commits broke the unit-user_building assignment.


feat: add EmbarkStudios/cargo-deny

EmbarkStudios/cargo-deny: Cargo plugin for linting your dependencies
Check List

[x] Read CONTRIBUTING.md

[x] Read OSS Contribution Guide

[x] All commits are signed

This repository enables Require signed commits, so all commits must be signed

[x] Avoid force push
[x] Do only one thing in one Pull Request

Thank you!

Oops, I missed the fail. Will update.

Done 👍

v4.176.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.176.0


Update new event with document ID returned from Firebase

What it Does

Closes #47
Fixed the crash which happened due to missing id.

How I Tested

Create a new maintenance event.
Delete immediately when you create the event.
Now, its getting deleted. Issue is fixed.

Notes

Inserting the id before I append the event into array.

Screenshot
https://github.com/mikaelacaron/Basic-Car-Maintenance/assets/54598657/164d01e9-cc20-4b92-a5a3-783fb2f5df68

Also note for future PRs a better branch name would be 47-bugfix-add-event-crash mainly without the # in front


[Bug]:   Timer only increments by 10

Version

[X] I'm using version 1.7.0

Known issues

[X] I've checked Known issues

Existing issues

[X] I've checked Existing issues

What operating system are you using?
Linux
Operating System Version
Ubuntu
Reproduction steps
1.Go to Big Break Timer
2.Use arrows mouse to increase adjust the slider
3. Slider increments by units of 10
Expected Behavior
I have used Stretchly on Windows.
The timer should increment by units of 1.
Actual Behavior
Increments by 10.
Relevant log output
No response
Preferences
No response
Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is currently calculated as (settings.get('breakInterval') + 1)*10 . Refactor to value other will be a big, coz this is calculated currently in many places. This should not be hard to change, but change in that many places will be hard to test.

Also topic should be updated to minutes timer.

@i-zanis what slider do you mean?
I guess you mean for Long Breaks.
The value there depends on what is your value in Mini Breaks as it is basically: Show Long Breaks after X Mini Breaks.
So if the Mini Break is every 10 minutes then Long Break can be every 20, 30, 40... minutes.
General in UI, I had to make choice between allowing everything and lowering complexity of the UI, therefore UI does not allow everything. For special case, config file can be used to change the values.

@hovancik I does not agree. User should be able to set long break to any minute, Workrave do this and no one complains about it. I could do this, of course after tray icon time indicator.

How would it work then?
Right now, I can only write as I described, so Long after X Mini.
Let's say user puts long break every 12 minutes, Mini every 10 as is by default. How are breaks working?

I think they use seperate timers. I know you do not want to seperate timers, still this seems like simplest solution. Alternatively this option could be provided where no mini are enabled, coz short breaks are not that useful, and then no problem with Micro breaks interaction.

Currently I have no mini enabled.
Most people that use applications such as these as very detail-oriented.
Not being able to adjust such a detail is a deal breaker. There is no other
option other than uninstall.
The fanciness of a UI cannot overcome health concerns along with strict
deadlines.
The feature does a lot and is easy to implement.
On Fri, Jun 4, 2021, 11:28 Michał Urbanek @.***> wrote:

I think they use seperate timers. I know you do not want to seperate
timers, still this seems like simplest solution. Alternatively this option
could be provided where no mini are enabled, coz short breaks are not that
useful, and then no problem with Micro breaks interaction.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hovancik/stretchly/issues/967#issuecomment-854598491,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANK7JQ2GO6P4AIMWZP6YFZDTRCTERANCNFSM453YRXDA
.

@i-zanis please consider what I wrote:

The value there depends on what is your value in Mini Breaks as it is basically: Show Long Breaks after X Mini Breaks.
So if the Mini Break is every 10 minutes then Long Break can be every 20, 30, 40... minutes.

General in UI, I had to make choice between allowing everything and lowering complexity of the UI, therefore UI does not allow everything. For special case, config file can be used to change the values.

Your conclusions should be:

Ah, so let's say I want Long Break to be interval of 60, 90, 120 minutes, then I need my Mini Break interval to be 30 minutes.  Let's say I want it to be 10, 15, 20 minutes, then my Mini Breaks need to be 5 minutes. Let's say I want 20, 30, 40, then I setup Mini for 10.
If my dream value is not in UI, I can set it up via editing config file.

Stretchly is opinionated, and the aim is not to solve every possible usecase. I would not be able to do that even if I were working on Stretchly fulltime. There are many apps in this space and everyone is free to choose according to their needs.

@senpl

I think they use seperate timers. I know you do not want to seperate timers, still this seems like simplest solution.

I guess they use separate timer but my question is how the breaks looks like?

Let's say user puts long break every 12 minutes, Mini every 10 as is by default. How are breaks working?

I start app at 5 am. What happens?
5:10 Mini Break -> 5:12 Long Break?
5:10 Mini Break -> 5:22 Long Break?
When is then the next Mini Break? What happens when timers occur on the same time? What Break to show? What does "same time" mean? When they are in the exactly same time or maybe a minute difference?
What if Long Break is halfway and timer for Mini comes? and vice versa. How is next break calculated?
This is very arbitrary  and different people will want different things: don't show long when break last Mini was X minutes before, or show it anyway. Don't cancel running break when some other is halfway, ignore it. Or don't ignore it, but only if it was Long. Etc etc.
Therefore I designed a system that there are mini breaks and then long break after X of mini breaks. You can still pretty much put any interval for Longs Breaks even if you don't use mini breaks.


Creating Husarion project fails when at enable_module

I am following your tutorial  to create a new Husarion project on Ubuntu. I have installed Visual Studio Code and  hFramework is successfully compiled.
This is the command I am running and its output
cmake .. -DBOARD_TYPE=core2 -DPORT=stm32 -DHFRAMEWORK_PATH=/home/saurav/hFramework -GNinja
CMake Deprecation Warning at /home/saurav/hFramework/hFrameworkPort.cmake:3 (cmake_policy):
The OLD behavior for policy CMP0011 will be removed from a future version
of CMake.
The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances.  Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
/home/saurav/hFramework/hFramework.cmake:18 (include)
CMakeLists.txt:4 (include)
-- Using hFramework from workspace
This is module path:
CMake Error at /home/saurav/hFramework/hFramework.cmake:40 (string):
string sub-command STRIP requires two arguments.
Call Stack (most recent call first):
CMakeLists.txt:8 (enable_module)
-- Using module from workspace:
-- Configuring incomplete, errors occurred!
See also "/home/saurav/leo_firmware/CMakeFiles/CMakeOutput.log".
Looking inside the enable_module macro,
COMMAND "${HFRAMEWORK_PATH}/../hcommon/hdev-findmodule" ${name}
it is looking for hdev-findmodule file which I believe is not installed.
Could you please help.
Thanks

Hello sausthapit,
I need some clarification, first you wrote that "hFramework is successfully compiled" then you are unable to build hFramework, did you change anything during the process?
On the other hand, when you install VSCode with Husarion extension, you are getting hFramework built and ready to use.
You can proceed to creating Husarion project step.
Regards,
Łukasz

Hi Lukasz,
Thanks for replying, I installed the extension and also compiled from the source on github. While I was compiling my firmware, I was using the wrong hFrameworkPath. Once I used the path to the Husarion extension, there was no more error.
Regards,
Saurav


Do not allow overwritting of primitive types

Q
A

Bug fix?
yes

Breaking change?
no

New feature?
no

Deprecations?
no

Spec compliancy?
yes

Tests added/pass?
yes

Fixed tickets

License
MIT

I noticed that flow does not allow overwriting of primitive types. http://astexplorer.net/#/AVDxqdz5yq
This also adds this behaviour to babylon.
/cc @samwgoldman @gabelevi @jeffmo

Current coverage is 97.27% (diff: 100%)

Merging #314 into master will increase coverage by <.01%

@@             master       #314   diff @@
==========================================
  Files            21         21
  Lines          4001       4006     +5
  Methods         485        489     +4
  Messages          0          0
  Branches       1179       1177     -2
==========================================
+ Hits           3892       3897     +5
  Misses           49         49
  Partials         60         60

Powered by Codecov. Last update 1150c0d...d26657f


Incorrect use of quotes in f-string

Hello,
I noticed an issue in the following line of code:
https://github.com/TrimVis/butlarr/blob/a13dfa592da928c8547dcaa8393dbce75c01bad0/butlarr/config/services.py#L10
The problem arises from the use of double quotes for both the string and the dictionary key.
Running it in Docker causes the container to constantly restart.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Oh yes, I forgot that in earlier python versions this issue with nested quotes exists, I will push a hotfix immediately :)

Should be fixed with: https://github.com/TrimVis/butlarr/releases/tag/1.2.1

I will leave this issue open for a couple days in case you encounter any further errors :)


Handle multiple order in NFTDetail

currently just showing the order which index is zero, need to use proper order when there are multiple orders

discussed and know how to implement
https://github.com/orgs/kaguraswap/discussions/124

Let's make new issues

implement order list component
add order list in NFTPage
add order list in TopPage


Can you add an option for uploading multiple files?

Example:
<input type="file" multiple>
Thank you.

Thanks for creating this library first of all.
Is there a way to pass this through props? If not, how do we add this?

+1 here
this is necessary functionality

1
Also need this feature.


Add tests for uniprops and add a fudged test for a MoarVM bug

https://github.com/MoarVM/MoarVM/issues/448

Done.

Thanks a lot!


Create  component

Description
Headings are used for showing content hierarchy and are important for improving the reading experience for our users.
Visual style

Parameters
We should be able to render all of these styles with the combinations of parameters in the table.

Parameter
Values
Default

Size
Display, Size 1, Size 2, Size 3
probably nothing? if we need something, choose Heading 2 as it will be most common

Element
h1, h2, h3, h4, h5, h6, div, (anything else?)
same 🔝

Weight [optional]
bold, medium
bold

Predefined combinations of headings
This is a list of main headings that should be used in our designs. Of course that it's possible to make more combination with different parameters but it's recommended to use these pre-defined headings.

Type
Pre-defined parameters

Heading Display
Size: Display

Heading Level 1
Size: Size 1Element: h1

Heading Level 2
Size: Size 2Weight: medium

Heading Level 3
Size: Size 3Weight: medium

_If some parameter is not pre-defined, just use the default value for that parameter.
Design tokens
For all configurations:
font-family: $fontFamily
line-height: $lineHeightHeading
color: $colorHeading

Based on selected configuration:

Parameter:Value
property: $token

Size:Display
font-size: $fontSizeHeadingDisplay

Size:Size 1
font-size: $fontSizeHeadingLarge

Size:Size 2
font-size: $fontSizeHeadingMedium

Size:Size 3
font-size: $fontSizeHeadingSmall

Weight:bold
font-weight: $fontWeightBold

Weight:medium
font-weight: $fontWeightMedium

Important! Parameter “size” is independent of semantic markup. It is possible to call component with the configuration like <Heading Size="Size 1" Element="div">Heading example</Heading>.
Some inspiration from other’s React components for heading component:
https://pricelinelabs.github.io/design-system/Heading
http://grommet.io/dxc/docs/heading (check Examples button on the right top)
https://cloudflare.github.io/cf-ui/#cf-component-heading
http://design-system.pluralsight.com/components/text/ (scroll down a little)
https://seek-oss.github.io/seek-style-guide/text (play with params and switch to headline)
https://backpack.github.io/components/web/text (switching to headline only with params)

I checked Storybook and pre-defined states are not yet there. The definition is in the description above (Display, Level 1, Level 2, Level 3). If anything, write me and I try to explain more.


add esc as default key to quit window

Hello, would be lovely to use escape to close the window

Agreed! Added as of 4d9f12d!


Updated Contribution.md

I have Updated the Contribution.md File with proper steps on how to clone the repo to create a PR.

thanks for committing @anshulkansal04 , don't forget to star the repository


After updated to version 0.4.0 the task crashed

##[error]File not found: 'D:\a_tasks\GitDownloader_56033f91-aeb8-4316-b19a-bcb721f4705b\0.4.0\ps_modules\VstsTaskSdk\VstsTaskSdk.psd1'

+1 We're also having this issue

+1 Same issue here.

+1 Same issue here.

I am also having that issue. Is it possible to roll back for a little bit?

It also shows it pulled from the marketplace.  I uninstalled it and now I can't get it back.
https://marketplace.visualstudio.com/items?itemName=fakhrulhilal-maktum.GitDownloader

Please update again to latest version 0.4.7. I'll close this issue if no one report this error within 3 days.

it's working again. Thanks


Update /login (pre-approval) copy

We've updated the copy to simplify the experience for the user, and added a "More Information" tab to provide additional detail, if desired.
Acceptance Criteria

[x] The App Name is displayed
[x] If the app is requesting an access key (limited), user is displayed "This does not allow the app to transfer any tokens"
[x] If the app is requesting a full access key, user is displayed "This provides access to your entire NEAR balance. Proceed with caution!"
[x] "More Information" button leads to a separate page with the following details

[x] Contract ID

[x] contractId

[ ] Methods

[ ] List of method names

[ ] Transaction Allowance

[ ] Gas Fee Allowance: X NEAR

Assets
Designs

Main Screen (limited access)
Main Screen (full access)
More Information Screen

Read and write to the NEAR blockchain

that's not true though. App is only getting permission to call specific contract.

@vgrichina could you please check if shell login info is accurate, I can change it as well if necessary:
https://wallet.nearprotocol.com/login/?title=NEAR+Shell&public_key=5RibhyW1b5j1GqBQDZhV5uZHsgvx2FLkbNKok48j8o4S

@marcinbodnar that's probably question to @kcole16 as well. The items there are accurate, but don't cover all. Like e.g. you can also access every contract which isn't obvious. And "Deploy Contracts" really only applies to your account for example.
However layout-wise such fixes are needed:

Does not allow:
column needs to be removed as it's empty

Contract:
needs to be removed as it's empty too

@vgrichina ok, I will handle fixes. So what would the final text sounds for these two situations @kcole16 ?

@vgrichina @marcinbodnar Updated from

Read and write to the NEAR blockchain

to

Read and write to this app's smart contract on the NEAR blockchain

@marcinbodnar For the near-shell case, let's add

Call functions on any smart contract

@kcole16 there are really more things than that though. Like e.g. you can also stake. Or unstake. Or add/remove keys. Basically everything that is available as actions in tx.

@vgrichina Fair, I should've gone through the commands! Think this covers it (all of the actions)
@marcinbodnar Let's add

Stake and unstake NEAR tokens

Create and delete access keys

Closing as issue is outdated


In ReadExecutor, verify a statement execution returns a ResultSet

Currently, the boolean value returned from Statement#execute in ReadExecutor is ignored. It should be checked, and if false, it means there is no result set being returned, which we should handle appropriately rather than just calling getResultSet().

even SELECT NULL LIMIT 0; returns a ResultSet (empty). I couldn't figure out a way to get Statement#execute return false for a SELECT. And I don't think someone can sneak in an update into a Read[A] that gets reflected as having no ResultSet
However just to handle all corner cases I would suggest to return an empty result stream.
I'll give this a try


Cannot find name 'useAsyncGql' in a .tsx file

Description:

Unable to find the function useAsyncGql in a .tsx file.
Using vite for bundling and Nuxt 3.
Tried copying the example, also tried exporting the function from the library but it was not available

Error:

tsconfig.json:

versions:

nuxt-graphql-client: ^0.1.12
nuxt: 3.0.0-rc.4
typescript: ^4.7.4

I think the culprit with my issue was pnpm it's causing some issues when trying to use it for Nuxt 3 and this library it somehow was not able to install the node modules properly even if I added shamefully-hoist. I deleted my node modules and .nuxt reverted back to yarn install and my problem was solved I was helped by my colleague.


[zdf] extract episode info if available

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information

Some of the videos on ZDF.de are organized in seasons, other are not. This PR aims to extract series, episode, season_number, episode_number when available.
Example:
python3 -m youtube_dl --output "%(series)s S%(season_number)02dE%(episode_number)02d - %(episode)s.%(ext)s" --get-filename https://www.zdf.de/serien/tabula-rasa/tabula-rasa-118.html

The JSON document I'm extracting is pretty messed up in some cases. I'm closing the PR and reopen it when I found a solution.


add WarningsFilter to filter Zed warnings and write to stderr

With the nuke-driver branch, the warnings channel is gone and warnings are written directly into the resulting Zed output.
We should implement a simple WarningsFilter that wraps a zio.Reader that would filter out these warnings and write them to stderr for zq and zed query.
We might want to create type warning = error

This is obsolete because the warnings channel is gone.


Couldn't run the code

Firstly, thanks for building such a great documentation on using ML Kit.
However, I have tried to build the code by myself and unfortunately the crop activity won't show up. It keeps back to the main screen after taking photo.
I am new to android environment and need some hints on how to successfully build your app.
The errors (in my case) are found in BaseDialogMain.kt and MainActivity.kt
Thanks!

Sorry for late reply. Kindly post the error.log so, it's easy for me to check


enhancement request: Removing Tag Values from the User Asset Group does not save

Is there an existing issue for this?

[X] I have searched the existing issues

Enhancement description
Save of Tag value removal is not functioning under User Asset Groups.
Jira - CUS-57
🧑💻 Implementation
No response
Anything else?
No response

@astra1 Can you please look into this?

@rammvenk will do