chore: upgrade charts

updated chart jenkins-x/lighthouse from 0.0.913 to 0.0.915
updated chart jx3/jx-build-controller from 0.0.25 to 0.0.26
updated chart jx3/jx-cli from 3.1.148 to 3.1.155
updated chart jx3/jx-preview from 0.0.143 to 0.0.144

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Color dropping in S3DIS Area5

Hello,
I want to know where is the code for Color dropping in S3DIS Area5 (used in Table 4 Page4.4.1 ).
Thanks.

https://github.com/guochengqian/openpoints/blob/cef77880fd449c8da580fea0d105a02fdf892ec3/transforms/point_transformer_gpu.py#L385


Backend container is failing to start

🐛 Summary
Backend container is failing on entry point CMD ["npx", "ts-node-dev", "src/api-dev.ts"], getting error ts-node-dev command not found. Even though all node_modules were successfully installed as mentioned in backend docker file step# 4  RUN npm ci.
To reproduce
Steps to reproduce the behavior:

cd backend && npm run build-worker
docker-compose up --build

Expected behavior
Backend container should be app and running. Should be listening on port: 3000
Any helpful log output or screenshots
Paste the results here:
ts-node-dev: not found
command failed
exited with code 127

Hmm, are you running docker-compose up --build from the root directory (and not from backend)?

@epicfaace Yes, from root directory.

I'm not sure what the problem is. We run the backend container through docker-compose regularly on CI and it works fine (see https://github.com/cisagov/crossfeed/blob/e91e0c1841da3b804198517c4b3729ffb7aa4c56/.github/workflows/backend.yml#L81), so I think it might be some problem with your setup / versions of software you are running on your computer.
Maybe you can try resetting your Docker cache and then retrying?

Reset the docker cache, still same issue. Just cloned the software few days back. Which branch is stable master or production?

Reset the docker cache, still same issue. Just cloned the software few days back. Which branch is stable master or production?

master is stable.

Okay, Will clone the fresh copy of software from master again and see if it fix the issue or not.

@epicfaace I've cleared the docker cache, npm cache as well. Also updated the docker to latest stable version.
Docker version 20.10.2, build 2291f61
npm version 7.5.2
node version v15.5.0
Followed below steps in sequence:

Cloned the fresh copy of crossfeed project.
Copied root dev.env.example file to a .env (cp dev.env.example .env)
Build the crossfeed-worker Docker image (cd backend && npm run build-worker)
Started entire environment from root using Docker Compose (docker-compose up --build)

Still getting the same above error, and warning for npm-force-resolution.
Attaching few more screenshots for reference:

Maybe you can try ssh'ing into the docker backend container, then checking the contents of the node_modules directory to see if ts-node-dev is there -- so we can see if it was properly installed in the first place.

@epicfaace I see node_modules are installed in backend container, ts-node-dev dependency exist in node_modules but on debugging I found that binaries(.bin) are missing.
As per this github issue it could be related to the package-lock.json was generated using different npm version, and I have latest npm version.
Can you please let me know this project is stable on which npm and node versions?

It uses Node 15 (see https://github.com/cisagov/crossfeed/blob/master/backend/Dockerfile#L2). npm / node versions shouldn't make a difference, though, since it's using Docker, which ensures the right version of npm / node is installed.

@epicfaace Yes, it is using node 15.8 and npm 7.51 that's why there were issues. I changed the backend docker image from node:current-buster to node:12, now all containers are up. But now facing the issues related to database, see the screenshot below:

Okay, that's great!


Taker can take offer with same id twice

Not sure how I managed to do this, but it seems the maker's offer is not always removed correctly.
Saw this in the taker logs, which means that we tried to take the same offer twice:
2021-10-14 20:24:47 ERROR Message handler failed: error returned from database: UNIQUE constraint failed: cfds.order_uuid: UNIQUE constraint failed: cfds.order_uuid
2021-10-14 20:24:58  INFO POST /api/calculate/margin text/plain:

The maker should not allow this.

This is related to https://github.com/comit-network/hermes/issues/323 - because we don't remove/replace the offer upon auto-reject upon retry the taker will try to create another cfd with the same order.
Note: Yes, the taker creates a cfd before sending the take request to the maker to keep track of the state.

I can still reproduce this on master (4ffbebda189320d48fd53399aa0a61d7b30bcbbe). It occurred after attempting to send and order request to the maker whilst the maker hadn't yet replied to my original order request.

@da-kami : this is assigned to you and in progress . If you are not working on this, please unasign yourself.

fixed with #532


Add isActive test with a custom parse/stringify function

For issue #2118
queryIsActive compare Object{foo: Object{1: 'bar'}} with Object{foo: Object{4: 'bar'}} wrong.

Thanks for the PR, @unh! Would you mind rebasing on current master? The tests should pass now.


Remove Spencer Dollahite, #1300

Removes Spencer Dollahite, Resolves #1300

Oh! I just closed that issue. 😃
Closing this PR.


Fix errors in StandardAnchorTags tool

I noticed that the standard anchor tags tool didn't open a PR when we merged some PRs in our meeting yesterday, when it should have.
There were a couple bugs in the StandardAnchorTags tool. The main one is that I had edited the README.MD file by hand, and changed the text the tool searches for to replace the TOC.  I fixed that by adding an HTML comment in the README so it's more resilient for edits.
After that fix, this uncovered a second issue where one header had repeated spaces. Fix that as well.
Finally, fix an error exposed by the new action added in #249 (Thanks @Youssef1313). I'll add comments on that PR momentarily.
Once this is merged, the tool should re-run and update the section numbers in the draft-v6 branch best on the PRs we merged yesterday in our meeting. This run failed yesterday when we merged the PR that added nameof expressions. We should have had a new PR that updated the TOC and affected sections.

Currently the comment for this PR ends with "Once this is merged, the tool should" - what should it do? Enquiring minds are eager to know!
(I haven't really got a sense of the PR yet.)

Sorry about that @jskeet I was interrupted while creating the PR and didn't get the description updated. That should be fixed now.


v5.6 is still broken. Downgrading to v5.3 is still the best solution. [Downgrade instructions included]

Script version
v5.6
Describe the bug

Next/previous buttons no longer show up on the video screen.
"AutoPlay" toggle no longer shows up on the video screen
Holding down left mouse on the video doesn't fast forward the video
There was something else but I can't remember what it was...

Desktop (please complete the following information):

OS: Windows 10 v10.0.19045.4291
Browser: Chrome

Additional context
RAT has not worked since v5.3
Temporary fix
Downgrade to v5.3

Go to the v5.3 commit
Click the Raw button
TamperMonkey should open up asking if you want to downgrade.
Say yes.
Restart your browser and go to YouTube.
If you get a popup asking if you want to update, click the red skip button b/c 5.6 is broken.
When 5.7 comes out, you should get another notification asking if you want to update.

Still getting double audio on v 5.3.
Workaround: Press spacebar and it should pause the first audio.

TheRealJoelmatic removed the messages with fixes. 3.8 worked. 5.3 it's broken. Double Audio.

53 is broken for me, double audio. 5.6 works, but I get error message on YouTube for some videos, "Video not available.
Playback on other websites has been deactivated by the video owner. Watch on YouTube".

@csptt-alt
@Peryite89
@Mendax1989
Everything I say is from a Windows OS standpoint using Chrome browser and I do not speak for other operating systems or other browsers.

Still getting double audio on v 5.3.

I've been using 5.3 since 5.4 came out and introduced the double audio bug.
I've used 5.3 through 5.4, 5.5, and 5.6 because all of these are broken and 5.3 isn't.
I can't figure out how certain others and saying 5.3 doesn't work for them when I've had zero issues with it for 2 weeks now.
If you have double audio, it is impossible you're on a version lower than v5.4 because that specific bug was introduced by 5.4.
Double audio is confirmation you're not downgraded.
Check TamperMonkey.
The script's version number should be displayed next to the script:

Go into the script itself, and there's a line up top that tells you the current version:

If that's not 5.3, you need to re-downgrade.
Other things that can help:

Ensure you click "Skip" if the update popup happens.
You can manually set the version from 5.3 to 5.6 so you won't get the update notification for 5.6.
Change the // @version      5.3 to // @version      5.6, click "File", then click save.
Alternatively, you can change the line const updateCheck = true to const updateCheck = false.
Make sure to save the script after editing.

@slzero-X
Yeah, I reported a few of the people doing it but they're creating new accounts.
Something like Daddy Ghost and Grand Daddy Ghost were posting earlier and those accounts are now deleted.

Youtube engineers putting in that hard work.

5.3 doesn't work anymore due to youtube improving its system to detect ads, 5.6 is broken but at least it skips ads

5.3 doesn't work anymore due to youtube improving its system to detect ads, 5.6 is broken but at least it skips ads

False. It's working perfectly fine. Have been using it since 5.4 came out without issue.

5.3 is not working for me, youtube detects it and just puts up the "ad blockers violate youtube's terms of service" screen. Is there a reason why it works for you but does not function for me?

5.3 is not working for me, youtube detects it and just puts up the "ad blockers violate youtube's terms of service" screen. Is there a reason why it works for you but does not function for me?

i just refresh the page a few times and it eventually works. lately it’s been detecting midroll ads too but those have only taken a single refresh each. at this point its more about the principle for me, i’d rather be inconvenienced by semi-working adblock than be inconvenienced by youtube’s atrocious ad system.


Missing "derive" feature for serde dependency?

Hey Jérémie, I was just trying to update the Elixir mjml_nif lib to use mrml v1.2.2 and came across this error when compiling the crate:
Compiling mrml v1.2.2
error[E0433]: failed to resolve: could not find `Serialize` in `serde`
  --> /home/paul/.asdf/installs/rust/1.51.0/registry/src/github.com-1ecc6299db9ec823/mrml-1.2.2/src/mj_accordion/children.rs:16:44
   |
16 | #[cfg_attr(feature = "json", derive(serde::Serialize, serde::Deserialize))]
   |                                            ^^^^^^^^^ could not find `Serialize` in `serde`

error[E0433]: failed to resolve: could not find `Deserialize` in `serde`
  --> /home/paul/.asdf/installs/rust/1.51.0/registry/src/github.com-1ecc6299db9ec823/mrml-1.2.2/src/mj_accordion/children.rs:16:62
   |
16 | #[cfg_attr(feature = "json", derive(serde::Serialize, serde::Deserialize))]
   |                                                              ^^^^^^^^^^^ could not find `Deserialize` in `serde`

The dependencies in my Cargo.toml looked like this when compiling failed:
[dependencies]
rustler = "0.22.0-rc.1"
mrml = "1.2.2"

When I put an additonal explicit serde dependency with reference to its derive feature, like the following, compiling succeeds:
[dependencies]
rustler = "0.22.0-rc.1"
serde = { version = "1.0", features = ["derive"] }
mrml = "1.2.2"

(This also fetches an additional serde_derive v1.0.126)
I'm not too familiar with serde and the usage of macros, but might there be a missing features = ["derive"] for the serde dependency (or an explicit serde_derive dependency) in the mrml-core Cargo.toml?
Or did I miss sth. that changed from mrml v1.0.0 to v1.2.2 in terms of setup/installation?

@paulgoetze thanks for this issue, I completely forgot to update the installation steps. You do need to install serde = { version = "1.0", features = ["derive"] }.
I should probably hide the part requiring serve behind a feature 🤔

Thanks a lot @jdrouet - the latter works perfectly in my use case.
Also you get the Quickest-Maintainer-Reply-Award (weekend edition) :trophy: :wink:

Thank you very much! I'll keep it on my desk!


Endowment calculation

The contracts are calculating the endowment (the amount that must be sent to cover all costs when scheduling a transaction) like so:
    function computeEndowment(
        uint _payment,
        uint _donation,
        uint _callGas,
        uint _callValue,
        uint _gasPrice,
        uint _gasOverhead
    )
        public pure returns (uint)
    {
        return _payment
                .add(_donation.mul(2))
                .add(_callGas.mul(_gasPrice))
                .add(_gasOverhead.mul(_gasPrice))
                .add(_callValue);
    }

As far as I can tell I believe we do not need to multiply the donation by 2 and this may be something left over from legacy code. If this is so I can add this easy fix to #94 since I found a bug in the endowment calculation anyway. However, I thought I would discuss here first in case I missed something.

closing, outdated


Gardenlet is missing read permissions for events in the seed cluster

How to categorize this issue?

/area ops-productivity performance quality
/kind bug
/priority 3
What happened:
Gardenlet was failing for quite some time in newly created seed cluster with error like
{"level":"info","msg":"Waiting until the nginx-ingress-controller service is ready...","seed":"foo","time":"2021-09-08T11:55:13Z"}
{"level":"error","msg":"error retry failed with context deadline exceeded, last error: nginx-ingress-controller service is not ready: `.status.loadBalancer.ingress[]` has no elements yet, i.e. external load balancer has not been created occurred while waiting for load balancer to be ready","seed":"foo","time":"2021-09-08T11:55:18Z"}
E0908 11:55:18.308357       1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:241: Failed to watch *v1.Event: failed to list *v1.Event: events is forbidden: User "system:serviceaccount:garden:gardenlet" cannot list resource "events" in API group "" at the cluster scope

While it has no controller actively watching events, during the bootstrapping of the seed, if the managed ingress is not disabled, a LB will be created and waited its public IP to be provisioned here https://github.com/gardener/gardener/blob/ec9152a73f63642f40907ed079bd2d0c6ff732a3/pkg/operation/seed/seed.go#L1000 In case of failure, events will be looked for errors here https://github.com/gardener/gardener/blob/ec9152a73f63642f40907ed079bd2d0c6ff732a3/pkg/utils/kubernetes/kubernetes.go#L200. But gardenlet is not allowed to read events, it has only create, patch and update permissions in the garden namespace currently https://github.com/gardener/gardener/blob/ec9152a73f63642f40907ed079bd2d0c6ff732a3/charts/gardener/gardenlet/charts/runtime/templates/role-garden-gardenlet.yaml#L15-L22.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Deploy a fresh installation of gardenlet with managed ingress enabled into a cluster that cannot successfully provision new LB services (e.g. scaled down CCM or restricted quota).
Anything else we need to know?:
Thanks to @timebertt for the findings!
Environment:

Gardener version: v1.30.1
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

Additionally, the gardenlet should be configured not to watch events on the seed cluster at all.

+1
IIRC, this is also necessary because otherwise the following error occurs:
error 'non-exact field matches are not supported by the cache' occurred while fetching more details

/assign


docs: improve readme documentation

Please move the .gitignore change to a separate PR if you really need it. I see no principal objections, but this should nod be hidden in "docs update"

I let @puzrin merge it if he is okay with the changes.


Improve Wizard UI

Highlights:

Cache input box values so that users don't have to re-type a value if they hit back during a wizard (only cached within the single wizard)
Add a "back" button to warning dialogs if they're shown during a wizard
More reliably detect if a step actually prompted using onDidFinishPrompt. This fixes bugs where the step didn't prompt and then the next step's back button doesn't work

Related: https://github.com/microsoft/vscode-azureappservice/issues/1226


Upgrade Jetty to version 11.0.16

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test camel-atmosphere-websocket camel-cometd camel-jetty-common camel-jetty camel-salesforce camel-thymeleaf camel-undertow


more updates for the next release

@MikeTschudi I made a change to the downloadUtils to address the issue with duplicates never being downloaded. queryFeatures from the layer seems to auto filter the duplicates so just made a new set of features and pushed in the duplicates after the initial query. Feel free to change if you know a better way but wanted to point it out.


Untestable function in MeMoModel

          ![image](https://github.com/Porthmeus/MeMoMe/assets/7808379/5e42179a-dbc3-4ded-a5b4-b82e04338f5a)

Code like this is impossible to test, we should discuss how we handle this?
Internal error codes? Return error strings Haskell Style?
Also we should add a few broken models i.e. at least one
Originally posted by @Unaimend in https://github.com/Porthmeus/MeMoMe/issues/89#issuecomment-1975123370

Not quite sure what you mean here and should be discussed.

https://stackoverflow.com/a/56300627 Might a possible solution


Address Sonar issues causing PR status check failures

Codecov Report

Merging #15169 (6aa3724) into main (cc536be) will decrease coverage by 0%.
The diff coverage is 68%.

@@          Coverage Diff           @@
##            main   #15169   +/-   ##
======================================
- Coverage     65%      65%   -1%
======================================
  Files        561      561
  Lines      26542    26543    +1
  Branches    3806     3806
======================================
  Hits       17278    17278
- Misses      8561     8562    +1
  Partials     703      703

Impacted Files
Coverage Δ

src/client/common/process/proc.ts
14% <14%> (-1%)
:arrow_down:

src/client/activation/common/downloader.ts
68% <85%> (ø)

src/client/common/crypto.ts
76% <100%> (ø)

src/client/common/platform/fileSystem.ts
80% <100%> (ø)

Codecov Report

Merging #15169 (6aa3724) into main (cc536be) will decrease coverage by 0%.
The diff coverage is 68%.

@@          Coverage Diff           @@
##            main   #15169   +/-   ##
======================================
- Coverage     65%      65%   -1%
======================================
  Files        561      561
  Lines      26542    26543    +1
  Branches    3806     3806
======================================
  Hits       17278    17278
- Misses      8561     8562    +1
  Partials     703      703

Impacted Files
Coverage Δ

src/client/common/process/proc.ts
14% <14%> (-1%)
:arrow_down:

src/client/activation/common/downloader.ts
68% <85%> (ø)

src/client/common/crypto.ts
76% <100%> (ø)

src/client/common/platform/fileSystem.ts
80% <100%> (ø)


EKS-A Nutanix Provider Action Items

These are some of the action items that came up from bugbash. These items are roughly in the order by priority

[ ] Support auto-generating SSH keys when sshAuthorizedKeys field is not set or is empty
[ ] Rename Nutanix credentials env vars from NUTANIX_USER to EKSA_NUTANIX_USERNAME and NUTANIX_PASSWORD to EKSA_NUTANIX_PASSWORD to be consistent with other EKS Anywhere providers
[ ] Add preflight to validate connection to NutanixDatacenterConfig's endpoint:port using something similar to this https://github.com/aws/eks-anywhere/blob/2a03ef2bb651cfc70c1cfea12a032103263d7817/pkg/executables/govc.go#L598-L604
[ ] Add preflight to validate Nutanix credentials before validating subnets and images
[ ] Add preflight to validate NutanixDatacenterConfig.endpoint is a valid endpoint
[ ] Add preflight to validate NutanixDatacenterConfig.port is a valid port
[ ] Add preflight to validate NutanixDatacenterConfig.additionalTrustBundle, if provided, is a valid PEM encoded cert
[ ] Add preflight to validate NutanixMachineConfig's memorySize, systemDiskSize, vcpuSockets and vcpusPerSocket
[ ] Separate out validation errors for cluster/subnet/image instead of wrapping them https://github.com/aws/eks-anywhere/blob/main/pkg/providers/nutanix/validator.go#L45-L55
[ ] In the NutanixDatacenterConfig object, include the additionalTrustBundle by default in the generated cluster config
[ ] In the NutanixDatacenterConfig object, change the default port to something else since 0 is not a valid port. Maybe set it to the default Prism Central port 9440?
[ ] In the NutanixMachineConfig object, don't include uuid: null by default in the generated cluster config

Added the pre-flight checks in https://github.com/aws/eks-anywhere/pull/4215

for  item

[ ] In the NutanixDatacenterConfig object, change the default port to something else since 0 is not a valid port. Maybe set it to the default Prism Central port 9440?
ref: https://github.com/aws/eks-anywhere/pull/4197

Pending tasks from above list:
-[]  Support auto-generating SSH keys when sshAuthorizedKeys field is not set or is empty
-[] Rename Nutanix credentials env vars from NUTANIX_USER to EKSA_NUTANIX_USERNAME and NUTANIX_PASSWORD to EKSA_NUTANIX_PASSWORD to be consistent with other EKS Anywhere providers
-[]  In the NutanixDatacenterConfig object, include the additionalTrustBundle by default in the generated cluster config

ssh key gen https://github.com/aws/eks-anywhere/pull/4297
passing additionalTrustBundle to capx https://github.com/aws/eks-anywhere/pull/4321
Rename Nutanix credentials env vars from NUTANIX_USER to EKSA_NUTANIX_USERNAME and NUTANIX_PASSWORD to EKSA_NUTANIX_PASSWORD to be consistent with other EKS Anywhere providers https://github.com/aws/eks-anywhere/pull/4303


Fixing formatting of task list

Changes Unknown when pulling 4117fc88965887b78801c1457341714e37de6df8 on rawkode:bugfix/fixing-task-list into ** on GT8Online:master**.


[#2241] feat(server): Introduce option to mark server unhealthy once any storage corrupted

What changes were proposed in this pull request?
Introduce option to mark server unhealthy once any storage corrupted.
Why are the changes needed?
For: #2241
This feature is to reduce the impact while the local directories are corrupted.
Does this PR introduce any user-facing change?
Yes.
rss.server.health.markUnhealthyOnceStorageCorruption is introduced, the default value is false that will not activate this feature by default.
How was this patch tested?
Existing unit tests.

Codecov Report
Attention: Patch coverage is 57.14286% with 6 lines in your changes missing coverage. Please review.

Project coverage is 52.94%. Comparing base (10c02cd) to head (b8599f5).
Report is 6 commits behind head on master.

Files with missing lines
Patch %
Lines

...org/apache/uniffle/server/LocalStorageChecker.java
33.33%
5 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2245      +/-   ##
============================================
+ Coverage     52.15%   52.94%   +0.79%
+ Complexity     3517     3338     -179
============================================
  Files           550      501      -49
  Lines         31672    27099    -4573
  Branches       2707     2544     -163
============================================
- Hits          16518    14348    -2170
+ Misses        14098    11819    -2279
+ Partials       1056      932     -124

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Computed fields allways appears whether checkbox is checked or is not

Hi,
I have the following problem:
I have a computed field like this:

Which its megafilter column is:

And whether the checkbox is checked or not, the column is allways visible...
I need that on checked be visible and on unchecked not visible..
Is there anything I'm not doing well, it's a bug or computed fields are allways rendered ( if so, then could be implement a feature that acts like normal attribute ?)
Thanks in advance

You cant use a computed attributed like that, MegaFilter needs to know the name of the field in order to work properly, you can change your code to this:
Text::make('Theme', 'theme')->displayUsing(function(){
  return '.....'
})

Thanks for answering so fast.
I just make what you say but now the values are just "-":

is themes a relationship? maybe it should be $this->resource->themes->first()->name ? your themes is probably an empty array

Yes themes is a relationship. It is not empty because all events have at least one theme and before I  made the change, the values were displayed well.
Also I just make the change for $this->resource->themes->first()->name but the result is still the same

If you simply do this doesnt work?
Text::make('Theme', 'theme')->displayUsing(function(){
  return 'Test Hello world'
})

you see the Test Hello world or still -- ?

or you could also try ->resolveUsing()  instead of ->displayUsing()

If you simply do this doesnt work?
Text::make('Theme', 'theme')->displayUsing(function(){
  return 'Test Hello world'
})

you see the Test Hello world or still -- ?

Exactly:

or you could also try ->resolveUsing() instead of ->displayUsing()

Same result --> '--'

Are you using the use HasMegaFilterTrait; ?
I have a similar setup and its working for me:

Yes, I'm using it:

I use it like this:

Mmmh, I put it like you but still the same result...
Maybe I have to update the package? My current version is:
digital-creative/nova-mega-filter": "^0.2.3

Maybe that's it, the latest version is v0.2.6

I already update it to v0.2.6 but I have the same problem... :(
I don't know if some package could be interacting with megafilter
Also, I see that the resolveCallback is never been executed. I proved to put a dd("Hello World") inside callback but it is never shown on request

I think the problem might not be with this package in your case, this is my test:

<?php

declare(strict_types = 1);

namespace App\Nova;

use App\Models\Client as ClientModel;
use DigitalCreative\MegaFilter\Column;
use DigitalCreative\MegaFilter\HasMegaFilterTrait;
use DigitalCreative\MegaFilter\MegaFilter;
use Illuminate\Http\Request;
use Laravel\Nova\Fields\Text;

class Client extends Resource
{
    use HasMegaFilterTrait;

    /**
     * The model the resource corresponds to.
     *
     * @var string
     */
    public static $model = ClientModel::class;

    /**
     * Get the fields displayed by the resource.
     *
     * @param Request $request
     *
     * @return array
     */
    public function fields(Request $request)
    {
        return [

            Text::make('Test', 'test')
                ->resolveUsing(static function () {
                    return 'Hello world';
                }),

        ];
    }

    /**
     * Get the cards available for the request.
     *
     * @param Request $request
     *
     * @return array
     */
    public function cards(Request $request)
    {
        return [
            MegaFilter::make([
                'columns' => [
                    Column::make('Test', 'test'),
                ],
            ]),

        ];
    }

}

Okey, thank you @milewski . Then, I'll have to keep investigating, but I don't know where to start..

Confirmed, I 've updated Laravel and Nova to last versions and now is working as expected.
Thanks for your help @milewski.


Add script for updating proposal tests and daily job for automatic updates

I see your concerns, however having all tests in one place simplifies the integration with other runtimes (otherwise all of them would have to build proposals' tests by themselves which pretty much will be a duplicated effort across the community), and I think wasi-threads might actually be one of the complex ones to integrate with right now given there's no wasi-sdk available that supports it yet.
I see a few other options we might consider:

make sure all proposals implement build.sh file that's self-contained (i.e. already downloads all dependencies like compiler, sdk etc) and builds tests, but that means we most likely repeat the same job in the CI multiple times for each proposal (e.g. if multiple proposals/tests use the same compiler we download it multiple times). There's also a chance that the specific version of toolchain requested by build.sh might not run on the image we use for CI. But maybe those are not such a big problems
we expect proposals to publish *wasm files along with the source code; that simplifies the process for wasi-testsuite, but also will require from maintainers to build CI action to update tests (which maybe is not an unreasonable expectation?)

@yamt I think (?) we both agree we'd like to have amalgamated branch with all proposal's tests. If that's the case, I'd suggest going ahead with this PR so we have something working; we can later update it with different approaches to generate .wasm files. Please let me know if you have strong objections.

@yamt I think (?) we both agree we'd like to have amalgamated branch with all proposal's tests. If that's the case, I'd suggest going ahead with this PR so we have something working; we can later update it with different approaches to generate .wasm files. Please let me know if you have strong objections.

i'm not sure if i agree with having a single "amalgamated branch".
or having a branch to serve binaries at all.
but this patch is ok for me, at least as a temporary solution.


Downloading UNSW Echo360 videos still doesn't work

This was discussed in #38, and "fixed" in #42.
However, #42 only fixes the front-end and not the back-end, so although the correct unit codes now appear in the interface, the download still fails.
I've written a fix for this in #47 (having not seen #42 and just assuming that it somehow didn't get fixed), but perhaps a better approach would be to have just one function for getUnitCode and call that from both places. [I don't know JavaScript well enough to know how to do that]

Closing issue as this was fixed in #47


[BUG] Scratchpad cannot be toggled to full screen directly

Pyprland version
2.4.1
Describe the bug
When using scratchpads, I cannot make them full screen directly using the full-screen shortcut.
To Reproduce
Steps to reproduce the behavior:

Open a scratchpad.
Focus on the scratchpad.
Press the full-screen shortcut.

Expected behavior
When a scratchpad is opened and in focus, pressing the full-screen shortcut should:

Make the scratchpad full screen.
Return it to its normal floating state and position when the full-screen shortcut is pressed again.

Actual behavior
Pressing the full-screen shortcut while a scratchpad is opened and in focus does nothing.
Workaround (That I'm using now)

Open the scratchpad and ensure it is in focus.
Use the shortcut to toggle the floating state off.
Press the full-screen shortcut.
This allows the scratchpad to go full screen.

Try setting pinned = false

It works! Thanks for the solution!


Check for formatting during the compile lifecycle phase

If there are non-complying files, check fails the build after all of the previous phases are completed, which often involves running several tests. In order to save time, it would be useful to move this to the compile lifecycle phase.
What do you think?

wdyt @malaporte?

Looking at the maven build lifecycle, it might make more sense semantically to use process-sources (which happens before compile).

We were thinking the same thing on our project, we want the build to fail earlier.
Maybe just an update to the readme explaining how to override the default phase might be good enough. That way it won't change any existing behaviour for those relying on the current default.
For me I'm happy with validate phase because I am not worried about checking generated sources, but maybe it's a different preference for different people/projects.
Something like:

The default phase for the check goal is compile however you can override this to any phase you like when configuring the execution. for example to override so that the check will take place in the validate phase:
<execution>
    <phase>validate</phase>
    <goals>
        <goal>check</goal>
    </goals>
</execution>

I prefer not changing the default phase, but adding documentation for how to change that in your own pom as @camac suggests. Would you like to make another PR with a docs update @camac ?

I prefer not changing the default phase, but adding documentation for how to change that in your own pom as @camac suggests. Would you like to make another PR with a docs update @camac ?

@klaraward Yep no problem I will submit one tomorrow 👍

@klaraward I have created PR #131 with the README update. Let me know if anything needs changing!

Going with #131 and closing this.


MIGRATIONS-970 - Replayer logs req/res/res triples as JSON

Signed-off-by: Mikayla Thompson<EMAIL_ADDRESS>Description
New Feature: as the replayer replays, it also outputs "triples" to file. Triples are objects with the original request, the original (source cluster) response, and the shadow cluster response.
This is a reopened version of #113 . That branch was affected by the manually signed commits of #110 , so the relevant commits were cherry picked onto this branch and update with comments from that PR. Sorry for the messy history.
Issues Resolved
MIGRATIONS-970
Testing
Lots of manual testing, but no unit tests.
Check List

[ ] New functionality includes testing

[ ] All tests pass, including unit test, integration test and doctest

[X] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #117 (e11628f) into main (cfe33bf) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   91.51%   91.51%
=======================================
  Files          25       25
  Lines        1155     1155
  Branches      122      122
=======================================
  Hits         1057     1057
  Misses         83       83
  Partials       15       15

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


[BUG] Font rendering on ubuntu is bad

In general, fonts for Insomnia in Ubuntu 17.10 render really badly - hinting is probably wrong as the smaller the font, the less readable they are.

Insomnia Version:

Version 5.15.0
Shell 1.7.13
Node 7.9.0
V8 5.8.283.38
Architecture x64

Operating System: Ubuntu 17.10 / Unity 7

I'm attaching a number of partial screenshots:

Some of the other electron apps I'm using (eg VSCode) do not show this problem and indeed render fonts just like any other native app.
Seems to be all fonts, not just the interface fonts I've highlighted - embiggening the text editor font mitigates the problem in there, but by no means fixes it.

I don't think your screenshots are high enough quality for me to tell what's wrong with the font. Maybe a screenshot that shows side-by-side with another app with better font rendering?

You need to open the image to remove github's zooming as the blur masks the issue. This is on a 1920x1080 screen. In 4K the problem is less apparent.
You can see both JSON render very similarly, same font but insomnia's sizing is a little lower. That's fine.
The issue comes on the interface elements, like the tabs, the POST button, the URL. Rendering is pretty bad there and makes the labels hard to read. It is quite possible it's the font being used, since the comparing screenshot is vscode which also uses electron. vscode is using the default system font, in my case this is Ubuntu.

Oh ya, I think I see it now. The JSON looks much smoother.
This is likely an issue with the default interface font. Do you know what font-face visual studio is using?

Hmm, ya I should probably just copy what VSCode uses for it's default fonts. Right now Insomnia includes the Open Sans font from Google Fonts (only the .woff2 format) which might not behave well with Ubuntu.

:+1: do gimme a shout if you need a hand with testing it out

Sure, thanks 😄

@gschier I just got updated to 5.16.1, did this fix make it in there? I see no real change on font rendering.

Ya it's in there. I guess that wasn't the correct fix, then 😿

Since yesterday I now have a "retina" install of Ubuntu running in VMWare so I can test it out 👍

Can you do me a favor and check which font-family is actually showing for you? In Ubuntu 18.04 it's Liberation Mono but I don't have a 17.10 to test with.

It is liberation mono local as per your screegrab, and it is just fine  on the editor and the response preview, timeline etc.
The place where weird font rendering remains is on the UI elements such as folder names, tabs etc. which is also liberation local. This is really puzzling though because the same font at the same size on a plain html loaded in chrome renders much better

I'm messing about with the dev tools and styles see if I can hit the spot

Oh right, got confused again as to which font was messed up. Let me know if you can figure out a font that works for you 😄

Ubuntu works better, but still renders with the hinting all messed up. How old is the version of electron you're using in here?

Nice, I can change it to the Ubuntu font for now and see what happens. Changing the UI font size is actually pretty tricky because all of the padding/margin/etc is tied to it (scaled using rem). I'd consider it though. Note that you can also change the zoom level using ctrl +/-

Understood, and thank you for your help :+1: I use insomnia constantly so good fonts are important to avoid eye strain

I'm having similar problem on Ubuntu 18.04 with Insomnia version 5.16.1.
I've checked the font family in dev tools and it is using: Courier New.
Is there any way I can change the font myself?

Going to close this now that there is the ability to select a custom font. Hopefully the user will be able to chose one with more weight.


Support mean as synonym for avg

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
This came up in https://github.com/datafusion-contrib/datafusion-python/issues/56
Describe the solution you'd like
Support "mean" as well as "avg"
Describe alternatives you've considered
None
Additional context
None

If anyone is interested in picking this up, it looks like it is probably a one liner (plus tests).
We need to add an additional mapping here in datafusion/expr/src/aggregate_function.rs
impl FromStr for AggregateFunction {
    type Err = DataFusionError;
    fn from_str(name: &str) -> Result<AggregateFunction> {
        Ok(match name {
            "min" => AggregateFunction::Min,
            "max" => AggregateFunction::Max,
            "count" => AggregateFunction::Count,
            "avg" => AggregateFunction::Avg,

I'm interested in this. May i try it?


PR: Change deprecated funtion QInputDialog.getInteger for QInputDialog.getInt

Fixes #3519
This also was causing error in maximum lines in console and history deep

This looks good to me, thanks @rlaverde!

@ccordoba12 this means that this no longer works with qt4 ?

Don't worry, this function was introduced in Qt 4.5 :-)

ah ok

@ccordoba12 You're welcome :)

:+1:


License & APK

Just stumbled upon your app's repo and, using the packageId from the build.gradle also found it's listed at PlayStore. But what I could not find out is the license used – and how people without access to Google's walled garden could use your app. Did you already choose a F/LOSS license (see e.g. SPDX and check those approved by OSI/FSF if still unsure)? And would you consider providing a signed release build e.g. attached to your releases?

@zacharee any chance?

Sorry, my notifications are all messed up on GitHub. I've added the MIT license.
I'm probably not going to be providing builds here on GitHub, since the Play version is paid and I also have it available as a Patreon benefit.

Sorry, my notifications are all messed up on GitHub.

:see_no_evil: I know exactly what you mean. Happened to me more than once, too.

I've added the MIT license.

Wonderful, thanks!

I'm probably not going to be providing builds here on GitHub, since the Play version is paid and I also have it available as a Patreon benefit.

Oh, I wasn't aware of that. Maybe you could consider a "lite" variant (preferably also without Crashlytics/Firebase then, for the benefit of the F/LOSS folks)? Consider it a "promo action" then, drawing interest. In those big halls with millions of (often fake) apps, some good app got lost. But in the little gardens of F-Droid (my repo has about 1k apps, F-Droid's own about 4k) it would be discovered by some of those who'd otherwise have missed it. And some of them might consider "going pro" (provided they have a means to; most of us do not even have a Google account, for reasons).
That said, third variant: With your app under a free license, would you be opposed to a listing at F-Droid? F-Droid would build your app from source (while my repo just takes the APKs provided by the resp. devs) and either signs them with a key especially generated for it by F-Droid itself – or takes a corresponding APK signed by you if the build was "reproducible" (i.e. their APK is binary-identical to yours).

I'm not sure if it's worth it for me to create a separate build config to exclude the GMS Wearable and Crashlytics libraries or disable certain features. This is mostly a hobby/personal project that I've made public.
I get not wanting to use GMS on a device (and CellReader should be fully functional aside from the Wearable companion part without GMS), but the main reason it's on the Play Store is because I don't know of any other stores that let you post paid apps aside from the Amazon store which is pretty much unusable from a developer standpoint.

Understood. Yes, Amazon Store would not be better at all (though PlayStore can be a pain in the … behind as well). F-Droid as well as my repo only can show donation links; as we do not have any user accounts, we cannot track payment either. Of course you could have some license key to be entered into the app once obtained OTR (bank transfer, Patreon, whatever). But yes, that would be extra work to implement.
Well, we should get rid of money altogether and … yeah, dream on :see_no_evil:
OK, I won't press – I totally understand your point. I fully accept if you close the issue and chapter – though I still hope we find a way, and you maybe keep this issue to ponder about :wink: Whichever it will be: thanks for your support, and all the best for you personally and your project here!


Rebuild

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

fixes #346 on LTR branch (3.28.9)

@conda-forge-admin, please rerender


Don't show imagestreams error on experimental mode

Signed-off-by: John Collier<EMAIL_ADDRESS>What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind cleanup
What does does this PR do / why we need it:
When a user enters an invalid component name to odo create when experimental mode is enabled on OpenShift, they see this error:
 ✗  imagestreams.image.openshift.io "dsfdsfd" not found

This happens because on OpenShift (with odo's experimental mode enabled), if no valid devfile component with the given name is found, we drop down to checking for s2i/imagestream components instead, rather than erroring out.
This error can be confusing if the user doesn't know what imagestreams are / was only intending to create from a devfile component. So instead, I modified the error message that's returned when an image stream can't be found to display the following when experimental mode is enabled:
 ✗  component "dsfdsfd" not found

This PR does not affect odo without experimental mode enabled, so the regular imagestreams error message is shown.
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/3128
How to test changes / Special notes to the reviewer:

Log in to an OpenShift cluster and enable odo's experimental mode
Run odo create <some-fake-component>
Error message should say component "<some-fake-component>" not found

@kadel Any concerns with this approach? I'm open to alternatives 😄
It's a little hacky, but I wanted to avoid breaking s2i-support when experimental mode is enabled and still maintain a somewhat meaningful error message for both s2i and devfile components

$ odo create fakecomp
Experimental mode is enabled, use at your own risk

Validation
 ✗  Checking devfile compatibility [19888ns]
 ✗  Creating a devfile component from registry:  [13492ns]

Please run `odo catalog list components` for a list of supported devfile component types
 ✗  component "fakecomp" not found

@johnmcollier should we start the validation stage for a component that's not found in the devfile registry? Shouldn't we handle it similarly for devfile component as well? Maybe even print only the last part, i.e.,:
$ odo create fakecomp
Experimental mode is enabled, use at your own risk

 ✗  component "fakecomp" not found

By no means am I suggesting to address it in this PR. We can discuss this in a separate issue. The code you've added looks good to me! But, if it makes sense, I would open a separate issue to discuss the validation part.
/lgtm

/approve


Underline and Strikethrough don't render on Whitespace when Render Whitespace is true

The Underline and Strikethrough text decoration does not render on whitespace when the setting Render Whitespace is enabled
Render Whitespace: none

Render Whitespace: all

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Wrapping slider in  tag doesn't work as expected on mobile

CodeSandBox example

CodeSandBox link: https://codesandbox.io/s/react-slick-playground-up7mf
Example from the above link: https://up7mf.csb.app/

Issue
If I wrap the entire Slider component in an a tag I can swipe/switch slides and click on any slide and go to the URL specified. This works fine on desktop. On mobile, however, it works, but only on the first slide. Once you swipe to another slide and tap, you are not taken to the link specified. On second tap, however, it does take you to the URL specified.
I would expect to be taken to the URL specified on all slides on the first tap, not just one the first slide.
Steps to reproduce the issue
Below are steps to reproduce the issue:

Go to https://up7mf.csb.app/ on a mobile device (or emulate a mobile device in your browser dev tools)
Tap on the first slide. Notice it takes you to Google.
Go back to https://up7mf.csb.app/
Swipe forward or backward (doesn't matter)
Tap on the new slide you are now on.
Notice you are not taken to Google this time.
Tap again.
Notice you are taken to Google now.

Possible fix
This is the line of code that swallows the click event: https://github.com/akiran/react-slick/blob/ef32fce2bc9b4152d1006b661ed95512138be458/src/inner-slider.js#L413
This line marks the slide as not clickable:
https://github.com/akiran/react-slick/blob/ef32fce2bc9b4152d1006b661ed95512138be458/src/inner-slider.js#L453
I believe the swipeMove method that contains the line above should not get fired if the user has not actually moved but just performed a tap. Alternatively, if this method should be fired on tap, the slide should be marked as clickable again in a callback after this.setState on this line: https://github.com/akiran/react-slick/blob/ef32fce2bc9b4152d1006b661ed95512138be458/src/inner-slider.js#L455
Conclusion
I can work on a PR if this gets acknowledged as a bug. Thanks.

@bolatovumar Yes, was able to reproduce the issue.
Please send a PR with fix.


SDK version in cookiecutters should be pinned

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/279
Originally created by @edgarrmondragon on 2021-11-23 18:09:13

In relation to https://gitlab.com/meltano/sdk/-/issues/278 and the Slack conversation, the cookiecutter starters should have a pinned version of the SDK. That would mean a few things:

Taps and targets explicitly declare the latest SDK version they support.
To get features from a newer SDK release, package developers need to update the SDK version in pyproject.toml.
End-users will always get the package bundled with an SDK version the developer knows to work.

View 4 previous comments from the original issue on GitLab


Source Code Question

When I initialized the Pipefile, pipenv helped me create the directory of virtualenv, e.g. creator CPython3Posix(dest=/Users/icbd/.local/share/virtualenvs/未命名文件夹-AsmMYtXt
I was curious about how the name of this directory was generated, so I found the source code implementation.
https://github.com/pypa/pipenv/blob/32e18cd9aa9bf3ab7851c528275ceda61e2383e9/pipenv/project.py#L539-L546
Does the processing of base64.urlsafe_b64encode have any special considerations? It seems that using hex() would be enough.
Thanks

What would be the advantage of hex over base64.urlsafe_b64encode?

@icbd did you know you can specify the name of your virtualenv with an environment variable override as well?

1. Problem Summary:
The issue questions the use of base64.urlsafe_b64encode in generating a unique hash for the virtual environment directory name. The user believes using hex() might be sufficient and seeks clarification on the rationale behind the chosen method.
2. Comment Analysis:

Another user inquires about the advantages of using hex() over base64.urlsafe_b64encode, highlighting the need to consider the benefits of the existing approach.
The maintainer points out the possibility of specifying a custom virtual environment name via an environment variable, suggesting an alternative solution for the user's potential concern.

3. Proposed Resolution:
While the user's suggestion of using hex() to generate the hash is valid, base64.urlsafe_b64encode offers specific advantages in this context:

Conciseness: Base64 encoding produces a shorter hash string compared to a hexadecimal representation for the same data. This results in shorter virtual environment directory names, improving readability and usability.
URL Safety: The "urlsafe" variant of Base64 ensures that the generated hash is safe to use in file paths, avoiding characters that might be problematic for file systems.
Collision Resistance: The hash is derived from the Pipfile location, providing reasonable collision resistance.  Changing the hash generation algorithm should not increase the risk of collisions.

Therefore, continuing to use base64.urlsafe_b64encode remains a suitable approach for generating the virtual environment hash.
4. Code Snippet:
No code changes are necessary based on the current analysis.
5. Additional Steps:

Documentation:  Add a comment in the pipenv/project.py file explaining the rationale for using base64.urlsafe_b64encode for generating the virtual environment hash.
Future Considerations:  If the need arises for significantly shorter directory names, explore using a stronger hashing algorithm (e.g., SHA256) with a shorter output truncation.
Address User Concern:  While the maintainer has highlighted the option of using a custom virtual environment name, it would be beneficial to directly address the user's question about the choice of base64.urlsafe_b64encode in the issue thread, pointing to the documentation for further details.

By addressing the user's concerns and providing clear documentation, we can enhance understanding and maintain the benefits of the existing approach.


Unsuccessful upgrade from 1.1.54318 to 1.1.54342 because of DateTime exception

We tried to do the rolling upgrade of Clickhouse from 1.1.54318 to 1.1.54342 stable and faced the following exception:
Code: 378. DB::Exception: Received from <host>. DB::Exception: Data type DateTime cannot have arguments: while receiving packet from <host>:<port>, <host>.

It happens when some node with old version (1.1.54318) sends distributed query to another node with new version (1.1.54342). Simplest query example on old node is:
SELECT toStartOfHour(timeslot)
FROM <some_distributed_table>
WHERE date = '2018-01-01'
LIMIT 1

timeslot is DateTime type, date is Date type.
We thought, that maybe problem is related to this changelog:

Improved support for timezones. The DateTime data type can be annotated with the timezone that is used for parsing and formatting in text formats. Example: DateTime('Europe/Moscow'). When timezones are specified in functions for DateTime arguments, the return type will track the timezone, and the value will be displayed as expected.

And it seems that code should handle such problem correctly: https://github.com/yandex/ClickHouse/blob/60477a9aaac73f283d0428b1f357de339512dcf3/dbms/src/DataStreams/NativeBlockOutputStream.cpp#L158
We do the rolling upgrade as usual and it means that we can have different versions of Clickhouse server during the upgrade. Our cluster is big and we can't tolerate query exceptions for long period of time, we need at least 1+ hour to do the full upgrade. Is there anything we can do to avoid this exception and continue with upgrade?

#define DBMS_MIN_REVISION_WITH_TIME_ZONE_PARAMETER_IN_DATETIME_DATA_TYPE 54311

That is slightly incorrect and compatibility isn't working for 1.1.54318.

To avoid this issue, you can postpone upgrade until the next version will be released.
Another possibility is to backport this patch a074b77 and rebuild ClickHouse.

@alexey-milovidov, when do you plan to cut the next stable release? I wonder if we should just wait for that and avoid extra restart round.

Unfortunately we have tagged a release candidate just before the fix was committed. In case there are no critical problems with it the next release candidate will not appear until after a ~week.

@alexey-milovidov thanks, we're going to backport the patch and try again.


browser reload to trigger after the last asset has been written

Depends on #112

https://github.com/lomirus/live-server/issues/18


fixed some bugs

Hey maintainer ,i made some changes in the project .
added css propery " overflow-wrap: break-word; " in Coverimage.css .if give title of blog to many char string without space it overflows out of container.
added maxLength ="75" in author input field , string of >80 char will overflow the footer .(noone would have such long name thought  :D ).
added lot divs in configCover.js to align input and label in a single line ,u can remove it and wrap  input tag inside label alternatively.(text will also be clickable then ).

The changes you made have disturbed the layout. Please fix this.

okay , feel free to close the PR as you sorted it out yourself


Setup ABAP GIT

Hello All,
My organization wants to implement ABAP GIT but i am not able to find the below , can someone help me with the exact answers , thanks in advance
training for the developers
security issues,
version management

Training: see http://docs.abapgit.org it describes the features of abapGit, but it is up to you how you want to use it. Also see http://docs.abapgit.org/other-articles-and-presentations.html for different scenarios
Security: feel free to review the code, as all other open source projects there might be issues. Strength in open source comes in numbers, right now there are 75 people from different organizations watching all code changes.
Version Management: The code for abapGit is stored in this repository, where you can always fetch the latest version. Every now and then I increase the version number and update https://github.com/larshp/abapGit/blob/master/changelog.txt
You decide when/how/if you want to upgrade your local versoin.

Hello Lars ,
Thanks for the quick response , Do you have any slides which you take for customer demos on how , why
If you can share the details it would be of great help please .
Thanks in advance .
Regards
Sri

abapGit is not a commercial product, so there are no customers, only users and community 😄
All my stuff is shared at http://docs.abapgit.org/other-articles-and-presentations.html
My slides are usually only images, and not very much text. But also see
https://blogs.sap.com/2017/05/07/abap-using-git-for-safety-and-transparency/
and
https://blogs.sap.com/2017/11/19/getting-started-open-sourcing-abap-code/
which describes the most important parts of abapGit from my point of view.

Thanks Lars Appreciate your quick response :)
Regards
Sri

feel free to jump onto the slack channel, https://abapgit-slackinviter.herokuapp.com/ if you like to discuss approaches/processes

guess this can be closed


[KOGITO-4199] Remove auto-creation of third party CRs

Signed-off-by: Ricardo Zanini<EMAIL_ADDRESS>See: https://issues.redhat.com/browse/KOGITO-4199
In this PR we remove Infinispan, Kafka and Keycloak auto-creation from our code base. Now, users MUST create these resources first.
@sutaakar I haven't tried yet on OCP, I'll run my tests tomorrow. Also, I believe we need a counterpart from BDD? Is it expecting the operator to create the resources for the tests?
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[x] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test

So going forward the kogitoInfra is just an abstraction which will used to bind our kogito resources with the pre defined/created infra resources?

There is an option to instruct KogitoCLI to install Data index when new project is created: kogito new-project ksuta-test2 --install-data-index. This command will fail as there are applied default KogitoInfra objects.
IMHO we should remove this option, maybe also installation of other supporting services when new project is created used using KogitoCLI?

I will adjust BDD tests, should be relatively easy. There are already tests using externally provided infra, so we just need to remove or adjust the rest of tests.

Also nightly images are missing with latest changes. I am promoting them right now.

Also nightly images are missing with latest changes. I am promoting them right now.

deployed

@sutaakar, I think we are good to start testing it now. wdyt?

And about the OLM integration with other operators? shouldn't that part be removed as well?

And about the OLM integration with other operators? shouldn't that part be removed as well?

That was removed ages ago :smile:

@ricardozanini Tests are adjusted, ready on https://github.com/ricardozanini/kogito-cloud-operator/pull/14

Failures are related to codedov upload.

BDD tests can be started once https://github.com/kiegroup/kogito-operator/pull/791 is merged

/jenkins test

/jenkins test ?

/jenkins test

I think we have an issue here, the PR was opened with the name of the old repo and from what I saw the plugin expects it to be with the name of the new repo.
stderr: remote: Repository not found.
fatal: repository 'https://github.com/ricardozanini/kogito-operator/' not found

I guess we all need to rename our fork repositories to kogito-operator.
and we need to update the different Jenkinsfiles to get that name instead of kogito-cloud-operator

please rebase to get the latest Jenkinsfile update to correct renaming

/jenkins test

@ricardozanini The BDD test changes disappeared from the PR

/jenkins test

/jenkins test

/jenkins test

https://github.com/ricardozanini/kogito-operator/pull/16 should fix the test error

/jenkins test

/jenkins test


403 error

2024-10-02 10:28:46 | ERROR    | 214 - Memfi | ❗ Unknown error while getting Access Token: 403, message='Forbidden', url=URL('https://api-gw-tg.memefi.club/graphql')

This issue has been preview on the Pull Requests. To resolve, Contact the official General support page to initiate a chat with our live agent using the chat button via support


Akaike information criterion

Greetings,
I would like to express my appreciation for the tool you have provided for parameter estimation using simulation-based inference. Currently, I am attempting to compute the Akaike Information Criterion (AIC) to compare various models. I am using the SNLE algorithm with the NSF density estimator and multi-round inference to identify the best-fitting model for my 20 data points.
As suggested in #693, I am using the following formula to obtain the unnormalized log probability:
    ll=posterior.potential(theta=best_params, x=x_0)

However, I have encountered three issues regarding this approach:

The values of ll differ significantly between multiple runs even when using the same prior and simulator.
My understanding is that the potential is $p(x_0|\theta_i, M_j, \phi_k)p(\theta_i|M_j)$, where $\theta_i$ represents the parameters of model $M_j$ with the maximum-a-posteriori estimate, and $\phi_k$ are the parameters of the autoregressive flow. Typically, model comparison is based on model evidence, which is the marginal likelihood over the parameter space. Unfortunately, I am unsure of how to obtain this value (given that I have to integrate over two parameters)
If I am correct, if the priors of the models are different they don’t cancel out from the potentials when computing the AIC

Hi there, thanks for creating this issue.
Indeed, the AIC (and related tools) are not implemented in this toolbox.

This variability stems from different initial weights of the neural network and from the train/test split being random. One way to deal with this is to average multiple runs of SNLE. You can use the NeuralPosteriorEnsemble  for this:

posteriors = ... # A list containing multiple `posterior` objects, each obtained with, e.g., SNLE.
ensemble_posterior = NeuralPosteriorEnsemble(posteriors)

Computing the model evidence is not implemented in sbi.  I did not rigorously test the following code, but something like this should do it for two parameters:

# Build grid over which to integrate.
resolution = 100
theta1 = torch.linspace(lower1, upper1, resolution)
theta2 = torch.linspace(lower2, upper2, resolution)
X, Y = torch.meshgrid(theta1, theta2)
xy = torch.stack([X, Y])
xy = torch.reshape(xy, (2, resolution**2)).T

# Evaluate p(theta, x) on grid
joint_evaluations = torch.exp(posterior.potential(xy, x=x_o))

# Quadrature
dx1 = (upper1 - lower1) / (resolution-1)
dx2 = (upper2 - lower2) / (resolution-1)
evidence = torch.sum(joint_evaluations) * dx1 * dx2

Indeed, the priors do not cancel out.

Hope this helps!
Michael

Thank you for your response. I have followed your suggestion and I am currently estimating three different priors, which I will combine using the NeuralPosteriorEnsemble method. This is a computationally intensive process as I am using the SNLE algorithm, amortized on two runs, as well as an MCMC sampler to estimate the posterior distribution.
Regarding the computation of the model evidence, you suggested integrating over the prior parameter space. But I don't see why:
$p(x_0|M_j, \phi_k) = \int_{\theta}^{}p(x_0|\theta, M_j, \phi_k)p(\theta_i|M_j)d\theta$
Lastly, do you have any suggestions for tools to compare different models based on their explanatory power, while also penalizing models with a large number of parameters?

the potential computed by the SNLE class is equal to $log(p(x_0|\theta, M, \phi)p(\theta|M))$
In the code snippet you provided you applied the exp to get $p(x_0|\theta, M, \phi)p(\theta|M)$
and then you summed over different values of $\Theta$
approximating the integral $\int_{\Theta}^{}p(x_0|\theta, M, \phi_k)p(\theta|M)d\theta$
I don't see why this quantity is equal to the model's evidence defined as $p(x_0|M)$
Thank you very much for your time

Hi @hdahmou, no, iid sampling should work with NLE ensembles as well. Could you please create a separate issue with a minimal failing example? Thanks!

Starting from $\int_{\Theta} p(x_o | \theta, \mathcal{M}, \phi_k) p(\theta | \mathcal{M}) d\theta$: The term inside the integral is the joint distribution of parameters and observation:
$\int_{\Theta} p(x_o | \theta, \mathcal{M}, \phi_k) p(\theta | \mathcal{M}) d\theta  = \int_{\Theta} p(x_o, \theta | \mathcal{M}, \phi_k) d\theta$
Marginalizing this quantity (i.e., integrating out $\theta$) gives $p(x_o| \mathcal{M}, \phi_k)$:
$\int_{\Theta} p(x_o, \theta | \mathcal{M}, \phi_k) d\theta = p(x_o| \mathcal{M}, \phi_k)$
which is exactly the model evidence (as predicted by the model with parameters $\phi_k$).

I apologize for reopening this issue.
Given that when using SNLE I have access to $p(x_o|\theta, M, \phi)p(\theta|M)$
In a single-round inference scenario, the prior distribution $p(\theta|M)$ is the same as the one used to train the density estimator (to which we have access). Additionally, since the neural network parameters $\phi$ were not specifically fitted to $x_o$ during the single-round training process, $x_o$ and $\phi$ are independent, and we can simplify the potential to $p(x_o|\theta, M, \phi)$ to $p(x_o|\theta, M)$ making it possible to compute the model's likelihood.
I'm pretty sure there's gotta be at least one mistake in my reasoning that I haven't caught yet.

Could you phrase your question more explicitly? I don’t understand what it is exactly that you are asking.

I apologize for the confusion,
What I was asking for was feedback on estimating the model's likelihood using the potential function from the sequential neural likelihood method.
Specifically, I am wondering if it is possible to estimate the likelihood via the unnormalized log-prob $\log{p(x_o|\theta, M, \phi)p(\theta|M)}$ where $x_o$ are iid observations, $M$ a simulation model, $\theta$ the vector of optimal parameters of $M$ that fit $x_o$ and $\phi$ the vector of parameters of the autoregressive flow used to estimate $\theta$
My reasoning is the following:
If $\phi$ are estimated via one single round (amortized inference) then the prior $p(\theta|M)$ is the same as the one that was initially provided, for which we have access to the log_prob
Additionally, since the neural network parameters were not specifically fitted to $x_o$ during the single-round training process $\phi$ and $x_o$ are independent, therefore:  $\log{p(x_o|\theta, M, \phi)} = \log{p(x_o|\theta, M)}$
Finally $\log{p(x_o|\theta, M)} = \log{p(x_o|\theta, M, \phi)p(\theta|M)} - \log{p(\theta|M)}$ where the two elements on the right are known quantities.
I would appreciate any feedback you have on this approach.

Thank you for your fast response
I am more interested in $p(x_o|\theta, M)$, the likelihood to observe $x_o$ given a model $M$ and a vector of parameters $\theta$ independently of the weights $\phi$ of the normalizing flow.
By examining this likelihood, I can evaluate and compare different models independently of the weights of the likelihood estimator.

Alright, thanks!
If you have access to the parameters $\theta$ then this is a perfectly viable strategy.
The reason that all common approaches for model comparison use the marginal likelihood $p(x_o | M)$ is that the true parameters $\theta$ are not usually known.
So, in short: if the true parameters $\theta$ are known, then you can use $p(x_o | \theta, M)$ to compare models.

You are right, the posterior can be multi-modal therefore the maximum a posteriori (MAP) estimation algorithm may not be able to identify the global maximum parameter vector $\theta$, plus the posterior distribution obtained through this approach is only an approximation to the true posterior distribution, which renders this method invalid.

I checked Papamakarios 2018. Based on what I understood, given enough data (and a sufficiently flexible model) $q_\phi(x|\theta)$ tends to $p(x|\theta)$, $q_\phi$ being a parametrized conditional neural density estimator.
Wouldn't it make sense to normalize the potential $p(x_0|\theta, M)p(\theta, M)$ (output of potential method) by $p(\theta, M)$ to get an approximation of the likelihood function $p(x | \theta, M)$? (and then use the Watanabe-Akaike Information Criterion)

I am not familiar with the Watanabe-Akaike Information Criterion, so I can't really help here. But yes, if you normalize the output of the .potential method by $p(\theta | M)$, you will get $q(x | \theta)$.

I appreciate your response. Based on my situation, it seems like the most viable option for me would be to utilize $\frac{q_\phi(x | \theta)}{p(\theta | M)}$ as an estimate for $p(x | \theta, M)$:
x = prior.sample()
l = np.exp(posterior.potential(x))/np.exp(prior.log_prob(x))


iOS Fullscreen with Controls Crash

@ashnfb @cobarx
Current behavior
The following change crashes our current implementation on iOS:
https://github.com/react-native-community/react-native-video/pull/1441/files#diff-42e8804735be64e84d6dd1fb103210a1R566
We display the video in full screen as soon as it is loaded.
After updating this implementation crashes.
A fix is not urgent for us, as we do not need the controls in non fullscreen mode on iOS.
As a workaround we just disable the controls on iOS, which resolves the issue.
Reproduction steps
<Video           source={this.props.source}           resizeMode='contain'           paused={false}           repeat={false}           controls={true}           onLoad={() => this.player && this.player.presentFullscreenPlayer()}           ref={this.handleRef}           style={fullscreen}         />
Additional info: We render the video in a react navigation dialog.
Expected behavior
It does not crash.
Platform

iOS

Exception thrown while executing UI block: Application tried to present modally an active controller <XXX.ReactNativeViewController: 0x7ff09b6182c0>.

__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke
    RCTUIManager.m:1112
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke.461
__RCTExecuteOnMainQueue_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
UIApplicationMain
main
start
0x0

@jonas-arkulpa can you try this fix in my master branch before I do a pull request
https://github.com/nfb-onf/react-native-video
cc @cobarx @fubar

@ashnfb Thx for the really fast response.
I tried your fix with positive and negative results. :)
With the change our implementation does not crash if the controls prop is set true.
Atm onEnd and onFullscreenPlayerWillDismiss do not get called.
With active controls another issue we've since the update is partly fixed.
The player does start in expanded fullscreen by default (I have no clue how this functionality is properly called). Also the state of the button is wrong: First press just toggles the button state and the second shrinks the video. Not sure why the control prop changes this behaviour. I think this existed before and might be better handled in a different issue.
controls=true:

controls=false:

The grey background is the video. Tested on an iPhone X.

@jonas-arkulpa @cobarx
Try my master branch again -->  https://github.com/nfb-onf/react-native-video, it includes fixes for the onXXX methods.  I did not look at the controls issue.
iOS 11+ has much better methods for method-based entry into fullscreen mode.  The code in the repo is much more complex than it needs to be because of legacy iOS support.

@kaybutter Do you have the time to test this the following weeks?

@jonas-arkulpa Yup. Should find some time next week :)

Sorry, haven't had time to look at this yet. Will try my best to get to it quickly.

@ashnfb Sorry that it took so long. I've tried using your branch. I noticed that the video refuses the play in Fullscreen now, if I set controls to true :(

@ashnfb any update on this? I have an issue with fullscreen via presentFullscreenPlayer and dismissFullscreenPlayer with controls set to true || false.  This may be related.   Im gonna report on another issue with attached links to example repos. thanks.

We have this issue too when setting fullscreen via presentFullscreenPlayer():
Simulator/Device (iOS)

Tested with local .mp4, remote .mp4 and remote .m3u8.

with controls set to true the simulator throws the following error:

Error setting property 'fullscreen' of RCTVideo with tag #3: Exception thrown while executing UI block: Application tried to present modally an active controller <UIViewController: 0x7fabe8c0fea0>.

with controls set to false the simulator does not throw and error but the video loses frame playback and gets stuck, forcing faster playback/catchup when you programmatically dismiss full screen mode via dismissFullscreenPlayer().

I've setup a test repo to reproduce and debug : https://github.com/4AllDigital/RNV-iOS
I'm happy to do any work/testing on this, but Im not an Objective-C developer and it seems that the issue is on that side, possibly around https://github.com/react-native-community/react-native-video/blob/master/ios/Video/RCTVideo.m#L1257, but I'd be guessing.

Hi @joemewes, I've been away for 2 months, and haven't been looking into react-native-video for some time.  I will try and have a look in the next few weeks at this issue if I can find the time; I recall it being pretty ugly to fix because of legacy iOS APIs.  Apologies that I can't help more immediately.

@ashnfb no worries. That's great and no stress about timings. I still think open-source projects and maintainers amazing! lol.

Hello all, this is also happening for us, but on an iPad 7th gen running iOS 13.1. We tried rolling back to 3.1.0 but it's happening there too.
Our (stripped-back) implementation:
<Video
  ref={(ref) => (videoElementRef.current = ref)}
  source={{ uri: source }}
  onReadyForDisplay={() => {
    videoElementRef.current.presentFullscreenPlayer();
  }}
  allowsExternalPlayback={false}
/>

+1 here.

Any update on this change? I am getting the same error. I am trying to make the video automatically go full screen if the user switches to landscape during playback.

I have this issue too, with react-native-video version 5.0.2.
I can fullscreen player on iOS by clicking native control, but I get error if I'm calling presentFullscreenPlayer().

i have the same error on IOS,
but when i set control={false},it works for me
when can fix the issues?

source={{ uri: source }}

hello can you specify your source ?

same issue with react-native-video<EMAIL_ADDRESS>

I have the same issue in the TVOS app, any update?

to fullscreen work fine you need set absoluteFill (top:0, bottom:0, left:0, right:0) in Video component

to fullscreen work fine you need set absoluteFill (top:0, bottom:0, left:0, right:0) in Video component

yes, I did it already. I'm facing the same issue which was mentioned by @joemewes in his earlier comment https://github.com/react-native-video/react-native-video/issues/1568#issuecomment-549289189

I've observed one thing here which allows playing video on fullscreen mode, I hope it will help others
use onFullscreenPlayerDidDismiss event with video like following
<Video
    source={{
        uri: this.state.screener.screener_urls[0],
        headers: buildHeader()
      }}
     ref={(ref) => {
         this.player = ref
      }}
     repeat={false}
     poster={this.state.screener.films[0].thumburls}
     onEnd={() => { console.log('onEnd') }}
     onFullscreenPlayerDidDismiss={() => { console.log('onFullscreenPlayerDidDismiss') }}
     onProgress={(evt) => {  }}
     onBuffer={this.onBuffer}
     onError={this.videoError}
     style={{
        position: 'absolute',
        top: 0,
        left: 0,
        bottom: 0,
        right: 0,
     }}
/>

As you can see here I'm not doing anything here with this event but fullscreen working perfectly once I mentioned this event

It's annoying but for now I'm just handling it like:
<Video
  controls={Platform.OS === 'android' || !fullScreen}
   // ...other props
>

where fullScreen is a boolean state variable.
Works for me on version 5.1.1, but since the fullscreen prop doesn't seem to work on either platform, I also need to manage the toggling of fullscreen with videoPlayer.current.presentFullscreenPlayer();

I've observed one thing here which allows playing video on fullscreen mode, I hope it will help others
use onFullscreenPlayerDidDismiss event with video like following
<Video
    source={{
        uri: "your_video_url",
        headers: buildHeader()
      }}
     ref={(ref) => {
         this.player = ref
      }}
     repeat={false}
     onEnd={() => { console.log('onEnd') }}
     onFullscreenPlayerDidDismiss={() => { console.log('onFullscreenPlayerDidDismiss') }}
     onProgress={(evt) => {  }}
     onBuffer={this.onBuffer}
     onError={this.videoError}
     style={{
        position: 'absolute',
        top: 0,
        left: 0,
        bottom: 0,
        right: 0,
     }}
/>

As you can see here I'm not doing anything here with this event but fullscreen working perfectly once I mentioned this event

I can't even see the log information here using the same code. It seems onFullscreenPlayerDidDismiss() on my ios simulator device does not work at all.

Does anyone have a solution for this? I am using and PR to have fullscreen for Android so I can't rollback to 3.1.0.


set id for sheet for custom styling

could you allow us to set an id for the sheet container?
Right now this assumes that only one sheet would exist on the page, however i am using multiple (and want to have them different widths on desktop) but custom styling is always applied to the classes.
Something like  <Sheet id="custom-sheet"></Sheet> should be enough
Edit: Seems like setting an id for sheet.container actually works, however typescript is unable to identify the props. Maybe you could update the PropTypes with React.ButtonHTMLAttributes and Framer-Motion Props?

Good catch! 🙌🏻  I will add React.HTMLAttributes<HTMLDivElement> to the sheet props type declaration which should fix this. This will be available in the next release which will be v1.3.1.


Training code

Hi,
Will you provide the training code to replicate the results from the paper and generate the frozen Tensorflow graph model?
Thanks

The training code is under preparation for both geodesc and contextdesc (a follow-up work of geodesc). Since the projects are industry-driven, it may take some time to resolve the patent issue and I cannot provide any guarantee for this release.

Sorry for taking forever to resolve the license issue. The training code is now publicly available, together with two follow-up works published in CVPR19 and CVPR20. Please visit TFMatch for details.


Update scalatest to 3.2.0

Updates org.scalatest:scalatest from 3.1.2 to 3.2.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: test-library-update, semver-minor

Codecov Report

Merging #1491 into master will decrease coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1491      +/-   ##
==========================================
- Coverage   85.88%   85.66%   -0.23%
==========================================
  Files          58       58
  Lines        2197     2197
  Branches      107      107
==========================================
- Hits         1887     1882       -5
- Misses        310      315       +5

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
94.59% <0.00%> (-2.71%)
:arrow_down:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.32% <0.00%> (-1.68%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.05% <0.00%> (-0.28%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
93.97% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e7f2c12...7b51ca7. Read the comment docs.


API rate limits

I searched a lot to find rate limits of Instagram private API but there was nothing, (i.e how many requests  per minute are allowed to call and how many accounts we can login by an IP.)
Do you have any reference to prevent flood and reduce risk of account removal by Instagram?

@paradox70 These limits are constantly changing, so I use one IPv6 per account

Thanks for your reply and awesome library.
I want to find out:
1- The maximum number of accounts I can login by an IP.
2- The rate limit of uploading medias to ig by an account.
I will find these by testing, If I have free time.

1 - I'm using 10 accounts for 1 IPv6 proxy
2 - publish from 4 to 16 posts to the feed and 24-48 stories per day

Thanks, You saved my time.


[FR] Add support for autocomplete of tags and links

Like it is available in general in Obsidian
https://user-images.githubusercontent.com/80559262/172063051-2a64bbd4-0adc-4a54-b134-50b2ad56c6ea.mp4

Sure! It will be added to the roadmap

using as a reference kanban plugin. The idea is using a react portal
https://github.com/mgmeyers/obsidian-kanban/blob/main/src/components/Editor/autocomplete.ts

Thanks to the astounding work of Kanban plugin, this feature have a solid base
First steps of my adaptation to dbfolder:
https://user-images.githubusercontent.com/11924043/187089029-9472ddfa-ec4a-445c-beb8-7f913e99f33f.mov

Will be added with the next version!
https://user-images.githubusercontent.com/11924043/187145417-fc7caf13-7590-4d69-946f-64e51546772b.mov


fail fast if another instance already using IP address

When bosh unknowingly selects an IP address for a create_vm that is already in use, the bosh director will call out to create_vm and just block. bosh cancel-task won't stop it. You just have to wait and stew.
Could we update create_vm to first quickly double check with AWS that the selected IP address is not already in use and fail fast? Then the operator can update their cloud-config's reserved list and start again.

Hmm, there is some specific logic + comments that suggest that an IP address that's already in use could mean that we need to wait for it to be released.
https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/blob/master/src/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb#L140-L146

That being the case, is it possible or out of the question for bosh cancel-task to more quickly cancel the create_vm call to the CPI?

@drnic We've seen issues of AWS SDK retrying by itself by not releasing the IP address in time. I don't know if this is specifically what is happening in your environment. Unfortunately we weren't able to reproduce but would be happy to do more investigation around that if necessary.
I don't know details about cancel-task. @dpb587 Any ideas?

In @drnic's case it seems the environment is shared with non-bosh-managed instances and they have difficulty keeping the cloud-config's network reserved section in sync with real world settings.
There's currently no way to propagate a task cancellation message to the externally-executed CPI. In theory, director could propagate a linux signal like INT to an executed CPI process to hint it should exit ASAP, but that might result in a lot of extra complexity for CPIs and director. I'm not sure that would be worth it.
Historically, outside of BOSH, I've seen delays of IPs being freed in from a terminated VM in the network side of EC2, like @cdutra suggests. Assuming that IP propagation delay is still an issue in modern AWS infrastructure, an alternative to constant, long retries would be for the CPI to follow up the failure by querying all instances to filter for the claimed IP address. Since terminated instances don't have IPs (the IP propagation delay is separate, iirc), there should be no instances returned; if there are instances found (and in started state?) the CPI could fail the create_vm quickly knowing there's no future change likely.

I'll close this ticket as I don't think there are any cpi specific fixes to the bigger issues. thanks for the discussion.


"forever" option is useless in node 0.12.*

because it's creates new agents every request, for example:
var request = Request.forever({
  maxSockets: 2
});

var r1 = request("http://google.com", function() {});
var r2 = request("http://google.com", function() {});

console.log(r1.agent === r2.agent); //prints false, but should be true

Problem is here https://github.com/request/request/blob/master/request.js#L486 .
This can be fixed by replacing this line by something like this:
self.agentClass = self.httpModule.Agent;
self.agentOptions.keepAlive = true;

Such behaviour makes sockets not reusable, because creates new pool(agent) every http request.

Generally speaking the forever should not be used in anything higher than node 0.10 (as stated in the docs), see https://github.com/request/request/pull/1671 for details. Your fix proposal looks good :+1:


chainsync StopSyncProcessError cause handlers to block on readyForNextBlockChan

On RollBackward and RollForward handlers, the readyForNextBlockChan is filled when a StopSyncProcessError is catched from the callback, 2 messages are sent to the readyForNextBlockChan. This can cause leaks as the handler could block forever.
Calling 2 subsequent Sync that stops the loop on the first received message , the callback handler of the second call is blocked/never called.
Example code to reproduce:
func main() {
	ctx := context.Background()
	address := "bart.bardels.me:6001"
	conn, err := (&net.Dialer{Timeout: time.Second}).DialContext(ctx, "tcp", address)
	if err != nil {
		panic(err)
	}

	o, _ := ouroboros.New(
		ouroboros.WithConnection(conn),
		ouroboros.WithNetwork(ouroboros.NetworkByName("mainnet")),
		ouroboros.WithNodeToNode(true),
		ouroboros.WithKeepAlive(true),
		ouroboros.WithChainSyncConfig(chainsync.NewConfig(
			chainsync.WithBlockTimeout(30*time.Second),
			chainsync.WithRollBackwardFunc(func(p common.Point, t chainsync.Tip) error {
				fmt.Printf("chainsync.RollBackwardFunc: point: %+v -- tip: %+v\n", p, t)
				return chainsync.StopSyncProcessError
			}),
			chainsync.WithRollForwardFunc(func(n uint, x interface{}, t chainsync.Tip) error {
				fmt.Printf("chainsync.RollForwardFunc: uint: %v -- x: %T -- tip: %+v\n", n, x, t)
				return chainsync.StopSyncProcessError
			}),
		)),
	)
	o.ChainSync().Client.Start()

	sp := common.NewPoint(
		92277900,
		func() []byte {
			b, _ := hex.DecodeString("6bf0ed7fd582d78433e1b1863da8d545fdb465d115dc353ccdbd0120f8509c90")
			return b
		}(),
	)

	err = o.ChainSync().Client.Sync([]common.Point{sp})
	if err != nil {
		o.Close()
		panic(err)
	}
	err = o.ChainSync().Client.Sync([]common.Point{sp})
	if err != nil {
		o.Close()
		panic(err)
	}
	select {}
}

The message is not printed on the second Sync call.
here and here the readyForNextBlockChan is filled and the handlers are filling it again just before to return, my guess is that after signaling the syncLoop to giveup the handlers should return nil.

Thank you @safanaj for the bug report and suggested fix


Support encoding ECDSA address in kbech32

Handled setting version bit correctly
Also handled missing bits padding

@tmrlvi would you like to review this addition?


Added OpenHV

This adds @OpenHV.

Thanks for the proposed addition. I would have one question about how different OpenHV is from OpenRA. Is it basically OpenRA just with different graphics or are there different game mechanics as well? How much different is the codebase between OpenHV and OpenRA by now?
My concern is that if I start adding mods, I might end up with many new entries, which also would need to be maintained somehow.

Thanks for the proposed addition. I would have one question about how different OpenHV is from OpenRA. Is it basically OpenRA just with different graphics or are there different game mechanics as well? How much different is the codebase between OpenHV and OpenRA by now?
My concern is that if I start adding mods, I might end up with many new entries, which also would need to be maintained somehow.

OpenHV is using a large chunk of the OpenRA engine and SDK with some custom logic maintained in the mod. The main difference is that OpenHV is a true Open Source game. The game assets are not proprietary.

Thanks for the explanation.


Domain Substitution: appspot.com URL in a GN file

ungoogled-chromium version: b80a0ec5dc7cad643f4c2c82bf2727a205621eac
Configuration and/or platform(s): all
Problem description
An appspot.com URL can be found in a GN file, however GN files are not processed by domain substitution:
strings out/Release/chrome | grep appspot
https://chromium-i18n.appspot.com/ssl-aggregate-address/

grep -r I18N_ADDRESS_VALIDATION_DATA_URL
third_party/libaddressinput/BUILD.gn:  defines = [ "I18N_ADDRESS_VALIDATION_DATA_URL=\"https://chromium-i18n.appspot.com/ssl-aggregate-address/\"" ]
chrome/browser/autofill/address_normalizer_factory.cc:                  I18N_ADDRESS_VALIDATION_DATA_URL,
chrome/browser/autofill/android/personal_data_manager_android.cc:                            I18N_ADDRESS_VALIDATION_DATA_URL,
chrome/browser/payments/chrome_payment_request_delegate.cc:          I18N_ADDRESS_VALIDATION_DATA_URL,

Is there any harm to adding *.gn and *.gni files to domain substitution?


Update operator-connect-configure.md

Fixed typo with remove the on-prem line URI PowerShell command.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


x1221 As ARA (Harriet) I would like to record the main peak size in addition to the concentration on the Visium QC concentration operation

New measurements:

Minimum size
Maximum size
Main peak size

Each measurement value should be a positive integer.

@khelwood @sabrine33 this is working fine but Harriet said that recording the Min size and max size is tricky. Not on STAN but depending on how the sample is, i.e. just whether a peak is beyond threshold. shes now asking to change it to main peak size and average size for the library. Or should we release what we have done and then change it?

@KatyTudor Probably best to change it before the release. If we release it and then change it, we'll have an anomalous group that has different measurements recorded to anything else.
Can you spell out the new requirements please?

@khelwood @sabrine33 can we change it to average size and peak size for the library concentration (so only two columns), and  remove the min and max size.
for cDNA concentration to remove min and max and just have average size

@KatyTudor Hopefully that change is up on UAT now

@khelwood @sabrine33 thanks for making the changes so quickly thats working great. I assume when release the view will have the new columns on?

@KatyTudor You mean the visium_concentration_view? You want the new size measurements as columns in that? or somewhere else?

@KatyTudor OK the UAT view has been updated.


Fix ios crash

update readme to fix ios issue with Flipper
Remove and gitignore .xcode.env.local becaue it was causing build errors.
Bump to latest 0.71.x react-native package to address build error, no template named 'unary_function' in namespace 'std'

Guh. I don't understand why those lint errors are a problem now.


Jenny's demo notebook

@jennyyzxu, I cleaned this up a bit and pushed a live version to the website so you can see what it looks like: https://promptlytechnologies.com/imfp/docs/demo.html. In your project folder, do git pull to get the changes I made.
Notice that some of your lines of code are too long, and some of your plots too wide, so they go off the right edge of the screen. See if you can fix that. Once we get that resolved, I will merge these changes to the main branch.


Illuminate\Contracts\Container\BindingResolutionException

I'm getting this error message after I add the provider to app.php:
[Illuminate\Contracts\Container\BindingResolutionException]
  Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\Manager

on a fresh installation of Laravel 5.3.

Ah... forgot to add the ScoutServiceProvider.


Axis log wrong side --- FIX

Fixing #414
Test out:
# side 4 logged, side 2 not logged
gs <- gsplot() %>%
  points(1:3, c(1,10,100)) %>%
  points(3:5, c(10,100,1000), col="blue", side=4, log='y') %>%
  axis(side=4)
gs

# side 3 logged, side 1 not logged
gs <- gsplot() %>%
  points(c(1,10,100), 1:3, side=1) %>%
  points(c(10,100,1000), 3:5, col="blue", side=3, log='x') %>%
  axis(side=3)
gs

# side 3 logged, side 1 not logged
gs <- gsplot() %>%
    points(c(1,10,100), 1:3, side=1) %>%
    points(c(10,100,1000), 3:5, col="blue", side=3) %>%
    axis(side=3) %>%
    view(side=3, log='x')
gs

# side 1 logged, side 3 not logged
gs <- gsplot() %>%
    points(c(1,10,100), 1:3, side=1) %>%
    points(c(10,100,1000), 3:5, col="blue", side=3) %>%
    axis(side=3) %>%
    view(side=1, log='x')
gs

That last example where we are trying to log side=1 but not side=3 is still wrong.
gs <- gsplot() %>%
    points(c(1,10,100), 1:3, side=1, log='x') %>%
    points(c(10,100,1000), 3:5, col="blue", side=3) %>%
    axis(side=3)
gs

par culprits for losing labels: mfrow & mfg. When these two were reset together, the labels disappeared. One reset and the other not, did not result in disappearing labels.
We don't really know why....:crystal_ball:

Funky


No excess properties error on function return type

TypeScript Version:  Nightly, 3.7.5
Search Terms: excess property, computed property
Code
const a = <T>(shape: T | (() => T)): T => {
    return shape instanceof Function ? shape() : shape;
}

//Case 1
a<{ x: string }>(() => ({ x: '', o: '' })); // I expect this to fail

//Case 2
a<{ x: string }>({ x: '', o: '' }); // Fails as expected

Expected behavior:
I expect Case 1 to show error similar to Case 2 because returned object contains more properties than described in generic type.
Actual behavior:
Case 1 is a valid typescript
Playground Link: Playground Link

Duplicate of #12632 which requires #241


Remove project specific community health files

Description
Removes the code of conduct and security files since they are now covered by organisation-wide files.
See https://github.com/erlef/.github/pull/1 & https://github.com/erlef/.github/pull/2

[x] I have read and understood the contributing guidelines

Good stuff.