snapshot reset_simulator finishes with an error on Xcode 7.1 Final

snapshot 1.0.1, just installed using gem install snapshot

When running snapshot reset_simulators using Xcode 7.1, I get an error message at the end of the execution:
An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=157):
Incompatible device

With Xcode 7.0.1: works
$ xcode-select -p
/Applications/Xcode 7.0.1.app/Contents/Developer

$ snapshot reset_simulators
Are you sure? All your simulators will be DELETED and new ones will be created! (y/n)
y
Removing device iPhone 4s (D8ED3DA4-FF61-4C17-BB89-6F5C0F4EF2E0)
Removing device iPhone 5 (2F823D20-6647-46A5-8AEB-F01850E8E088)
[…snip…]
Removing device iPad Air 2 (66571AF6-8CEF-49EB-B5AC-DB39FA9CA72C)
Removing device iPad Pro (7F7DB67B-7B1B-45B2-A932-45DBF20A8768)
Creating ["iPhone 4s", "com.apple.CoreSimulator.SimDeviceType.iPhone-4s"] for iOS version 9.1
Creating ["iPhone 5", "com.apple.CoreSimulator.SimDeviceType.iPhone-5"] for iOS version 9.1
[…snip]
Creating ["iPad Retina", "com.apple.CoreSimulator.SimDeviceType.iPad-Retina"] for iOS version 9.0
Creating ["iPad Air", "com.apple.CoreSimulator.SimDeviceType.iPad-Air"] for iOS version 9.0
Creating ["iPad Air 2", "com.apple.CoreSimulator.SimDeviceType.iPad-Air-2"] for iOS version 9.0

With Xcode 7.1 Final: fail
$ sudo xcode-select -s /Applications/Xcode\ 7.1.app
$ snapshot reset_simulators
Are you sure? All your simulators will be DELETED and new ones will be created! (y/n)
y
Removing device iPhone 4s (1272B1C7-9840-4438-9915-5BF326CC1188)
Removing device iPhone 5 (6C8990A0-BD5F-4A9F-9D3C-D5C57BFBE34C)
[…snip…]
Removing device iPad Air 2 (66571AF6-8CEF-49EB-B5AC-DB39FA9CA72C)
Removing device iPad Pro (7F7DB67B-7B1B-45B2-A932-45DBF20A8768)
Creating ["iPhone 4s", "com.apple.CoreSimulator.SimDeviceType.iPhone-4s"] for iOS version 9.1
Creating ["iPhone 5", "com.apple.CoreSimulator.SimDeviceType.iPhone-5"] for iOS version 9.1
[…snip…]
Creating ["iPad Retina", "com.apple.CoreSimulator.SimDeviceType.iPad-Retina"] for iOS version 9.1
Creating ["iPad Air", "com.apple.CoreSimulator.SimDeviceType.iPad-Air"] for iOS version 9.1
Creating ["iPad Air 2", "com.apple.CoreSimulator.SimDeviceType.iPad-Air-2"] for iOS version 9.1
Creating ["iPad Pro", "com.apple.CoreSimulator.SimDeviceType.iPad-Pro"] for iOS version 9.1
Creating ["Apple TV 1080p", "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p"] for iOS version 9.1
An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=157):
Incompatible device

Note: I tried using snapshot reset_simulators --verbose but it doesn't seem to change the output and provide more info.

Thanks for the detailed report. Updating Xcode to reproduce this issue now :+1:


Request:  Please, please make this work with Google's Inbox too!

This extension is wonderful.  I love it so much that I actually open both Inbox and Gmail just so I can use it even though it's a hassle.  Please, please make this work with Google's Inbox too.
Thanks!
-David

I hear you on the Inbox request. :-) Thanks for the very nice words!

You deserve every word.  Why Google hasn't already put this functionality
into Gmail and Inbox is beyond me!
On Wed, Jul 12, 2017 at 1:13 AM, Greg Sadetsky<EMAIL_ADDRESS>wrote:

I hear you on the Inbox request. :-) Thanks for the very nice words!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gregsadetsky/email-dictation/issues/2#issuecomment-314648716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH6uxaGcCx2nWvvSWNanLPmRc87IGiW6ks5sNFXkgaJpZM4OVIki
.


WebGPU: add support for GPU particles

I had to reorganize the structure of the particle buffers to limit the number of dummy properties (the more dummy properties we have, the bigger the buffer is) in the WebGPU case: the STD140 layout applies for the storage buffers.
I did not manage to have shader files with a .wgsl extension to be automatically transformed to a .ts file by the gulp task, so I have created a .fx file instead for the update compute shader (gpuUpdateParticles.compute.fx).
In addition to the WebGPU support, I have also performed those changes in the GPUParticleSystem class:

support for the MULTIPLYADD blend mode
support for custom effects
fixed a bug with the cylinder emitter

On this playground (it won't work without the PR, even in WebGL2) and on my computer (GTX 1080), according to PIX the compute task is 1.35 times faster than the Stream Output stage used in WebGL2 (transform feedback buffers): 1.41ms vs 1.91ms.
Test PG: https://playground.babylonjs.com/#PU4WYI#4

Just a change in the architecture but that should not be too painful

Actually that was not so straightforward ;)

Sorry buddy


#Fn-dataprep-create-dataset-fix fix create dataset with multi files

Description

fix create dataset with multi files
modify delete dataset

Related Issue :

release test
How Has This Been Tested?

fix create dataset with multi files
1.1. menu> MANAGEMENT > Data Preparation > Dataset > Generate new dataset
1.2. Multi file Upload and Create dataset

modify delete dataset
2.1. menu> MANAGEMENT > Data Preparation > Dataset
2.2. Delete dataset

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Additional Context

run build
deploy to 4

PR move to #1619


Modified Binary Search

Pigeonhole principal is very useful and important concept. It is used for specific problems and is very useful for optimizing space complexity . For ex - Given a vector of N + 1 elements containing numbers from 1 to N, this can be solved in O(NlogN) time and O(1) space. @tarun26091999 @rudrakshi99  kindly assign this to me.

I would like to contribute to the above problem in java as I am a participant of GSSOC'21. Kindly assign this to me.


Discoball (failed)

@rlugge Can you push what you have right now so I can take a look? Want to make sure we're on the same page.


card rework

updated fourth wall dashboard to simplify presentation and allow more
cards to be visible

@collisdigital https://www.raspberrypi.org/forums/viewtopic.php?t=121195


Remove the user_id from the migration for Users.

We don't need to supply this. Let ActiveRecord manage it.

Are you sure auth0 doesn't need this to keep track of whether to create a new user or log a user into an existing one?

@kimchanyoung You are right. I'm leaving this alone.


In laravel project it can't define object

Jodit Version:  3.1.xxxxx
Project base
Laravel 5.7
list of packages:
"axios": "^0.15.3",
"bootstrap": "^4.3.1",
"cross-env": "^5.2.0",
"jodit": "^3.2.44",
"jquery": "^3.1.1",
"laravel-mix": "^4.0.15",
"lodash": "^4.17.4",
"popper.js": "^1.15.0",
"resolve-url-loader": "2.3.1",
"sass": "^1.20.1",
"sass-loader": "7.*",
"summernote": "^0.8.12",
"vue-template-compiler": "^2.6.10"
Actual behavior:
ReferenceError: Jodit is not defined[Learn More] app.js:36803:5
js http://tar.loc/js/app.js:36803
webpack_require http://tar.loc/js/app.js:20
0 http://tar.loc/js/app.js:36900
webpack_require http://tar.loc/js/app.js:20
 http://tar.loc/js/app.js:84
 http://tar.loc/js/app.js:1
After proper compilation it can't create object. Other similar editors can. And it olso works if I include js of jodit from cdn

let jodit = require('jodit');
window.Jodit = jodit.Jodit;
var editor = new Jodit('#textarea');

I've included it directly without all this overcomplicated stuff with package managers and tricky workarounds

its better if you use webpack you just add
let jodit = require('jodit');
window.Jodit = jodit.Jodit;
var editor = new Jodit('#textarea');

in your resources/app.js
and it will work but if you already managed to make it work you should close this issue


[C] Handle error TLS from DllMain

This is the change discussed here. When the C media driver is used as a DLL, the TLS slot used to handle the error state is now managed by DllMain, and the per-thread memory is correctly freed when a thread exits.

Thanks!


Basic IAM authentication, authorization

For an internal project, I implemented basic IAM authentication and authorization in moto. This includes the following:

returning an error when the request is signed with invalid credentials (either AccessKeyId does not exist, or Signature does not match the calculated one)
returning an error when the IAM principle making the request does not have the required permission

It is a very basic implementation, with a lot of incomplete areas, such as

only IAM users and assumed roles are supported as principals
currently the Resource and Condition parts of the policies are not checked at all
the service-specific error messages are only supported for IAM, S3 and EC2
since the Resource element inside IAM policies is not supported, the returned error messages does not contain this information either

To make the changes non-intrusive, I introduced an environment variable INITIAL_NO_AUTH_ACTION_COUNT. If this is set, moto will skip performing any authentication as many times as the variable's value, and only starts authenticating requests afterwards. If it is not set, it defaults to infinity, thus moto will never perform any authentication at all.
For now, please let me know if the concept (and the code) is okay, and if so, I'll create tests and add a section about it to the README.md.
Resolves #1131, resolves #1863.

Coverage decreased (-32.3%) to 60.825% when pulling 114136dedda990473caceaede02c438b1c420976 on acsbendi:master into 396cb39676efc6303129b5fe913673579f26a1a9 on spulec:master.

This is a great feature and some nice cleanup! Thank you.
I agree with this approach of using an environment variable for now. We can discuss later if we should default it on in a future major version. Can you move INITIAL_NO_AUTH_ACTION_COUNT to the settings file?
As you mention, if we can get some tests added and an update to the docs, I will be happy to merge!

@spulec Everything should be ready for this to be merged now.

Thanks again for this; it is very cool!


storage: Introduce AddExtraTableIDColumnTransformOp

What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/6827
Problem Summary:
What is changed and how it works?
This is the remaining task of https://github.com/pingcap/tiflash/pull/7493, that excluded the AddExtraTableIDColumn logic from SegmentInputStream/SegmentSourceOp.
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)

Settings:
[profiles.default]
dt_enable_read_thread = false
enable_pipeline = true
enforce_enable_pipeline = true

Query 1 (no partition):
set @@session.tidb_opt_enable_late_materialization = 'off';

/*PLACEHOLDER*/ /*q1*/select   ol_number,
         sum(ol_quantity) as sum_qty,
         sum(ol_amount) as sum_amount,
         avg(ol_quantity) as avg_qty,
         avg(ol_amount) as avg_amount,
         count(*) as count_order
from	 order_line
where	 ol_delivery_d > '2007-01-02 00:00:00.000000'
group by ol_number order by ol_number;

Query 2 (partitioned):
create table t1(id int, age int, key(id)) partition by range(id) (
  partition p0 values less than (100),
  partition p1 values less than (200),
  partition p2 values less than (300),
  partition p3 values less than (400));

insert into t1 values (1, 10);
insert into t1 values (10, 10);

alter table t1 set tiflash replica 1;

set @@session.tidb_isolation_read_engines='tiflash';
set @@session.tidb_partition_prune_mode = 'dynamic';

analyze table t1;

select * from information_schema.tiflash_replica;

select count(*) from t1 where id < 150;

[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/rebuild

/run-all-tests

/run-all-tests

/merge


[BUG] manifest.json target platform firefox-mv2 compilation error

What happened?
// package.json
{
  "scripts": {
    "dev": "plasmo dev --target=firefox-mv2",
    "build": "plasmo build",
    "package": "plasmo package"
  },
}

output:

Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Firefox
Relevant log output
No response
(OPTIONAL) Contact Details
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

@erniu Thanks for filing the issue! Just created a PR to fix this will release a patch soon :)

The fix should be up in 0.64.4


doc: Fix wrong example commands

Description
Fix issue in doc
Fixes #892
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have run pre-commit for code linting and typing (pre-commit run)
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes (tox -e testenv)

@carl-baillargeon / @mtache / @titom73
extra suggestion from the issue reporter would be to move tags example out of "getting started" -> thoughts?


digest: async mode switch to sw for small packets

hw v2 does not support msg->in_bytes = 0, refer
drv/hisi_sec.c: digest_bd2_type_check
if (type == HASH_SINGLE_BLOCK) {
WD_ERR("hardware v2 not supports 0 size in block hash!\n");
return -WD_EINVAL;
}
But Nginx does send packets with in_bytes=0, sync mode is OK since it switches to sw, while async mode will fail.
Fixed by switching to sw for small packets in async mode too, Though only in_bytes=0 matters.

lgtm


(Non Fosdem 2022 related) As a Host/Coordinator I wish to tell the bot a speaker is not here for a QA without needing to do it in penta

Is your feature request related to a problem? Please describe.
The Bot is very aggressive fast, if someone is missing (which is great) but as a Host/Coordinator I want to mute it if I know a speaker cant show up. Otherwise it is very chatty/spammy.
Describe the solution you'd like
A reaction action on the bot messages to mute it would be great.
Describe alternatives you've considered
Apparently this gets synced via penta, but penta is sadly quite slow to work with, and also I would like a more matrix native way as the coordinators and hosts likely will mostly be in matrix while the conference runs.

Additionally, this would be nice if someone wants to use the bot with another backend. I didn't check how much penta is tied into the bot though.


Pull elements of SpansService apart for better organization and dependency management

Goal
Pull apart the SpansService interface  and implementations into constituent components. This is a bit messy, but there's no easy step by step way of breaking them down, so the idea is to do it roughly first then clean up the concerns in subsequent PRs.
There's no new logic, just stuff being moved around. Tests all pass after modifications

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

master

PR #312

PR #313   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 31, 12:18 PM: @bidetofevil started a stack merge that includes this pull request via Graphite.


Regent: Support for intXd with X > 3

Legion and Regent now have support for a variable number of index space dimensions, and this support has been ported to the C interface.
What remains is to use this feature to extend Regent's int2d/3d to more dimensions. This should be straightforward, as most operations on int2d/3d are already handled uniformly, by mapping over the structs' fields.
Mainly, someone needs to run through the code looking for uses of hardcoded numbers for the maximum number of dimensions, and replace them with the appropriate compile-time constant (e.g. this assertion https://github.com/StanfordLegion/legion/blob/8474f232dd50f68b26c77009e757f098766a73ad/language/src/regent/std.t#L1891 and this for-loop https://github.com/StanfordLegion/legion/blob/8474f232dd50f68b26c77009e757f098766a73ad/language/src/regent/std.t#L2123).
Also see #466.

Closing, this has been supported for a while.


EventHandle and option to disable EventHandler chaining.

This PR introduces EventHandle for easier events management.
Problem:
Event management with limited lifetime of objects - can be cumbersome, especially as there is no easy way to detach events unless you have all the references to arguments that this event was created with.
Also, anonymous functions as a callback on event that needs to be removed after - is a "no no!" with a current implementation.
So when you need to subscribe to an event in a script, and manage that subscription, you need to add very similar lines to 3 places: initialize, destroy and swap. And when you have many events, it looks like copy-pasted code all around with small modifications.
Another major problem is that current EventHandler implementation returns this when creating an event using on and once, which historically was called "chaining", but it is not chaining as it does not offer any logic of chaining events, their order of execution and rules of execution.
So implementing EventHandle requires breaking change, which PlayCanvas avoids. As chaining has not been seen used in practice, this PR implements it in a breaking manner, to mitigate issues if someone (extremely unlikely) used chaining, this implementation makes a on and once method for backwards compatibility. So this code will still work:
app.on('evtOne', () => {
    // one
}).on('evtTwo', () => {
    // two
});

Notes:
Engine does not have a single use of "chaining" in its codebase or examples.
I've tested this PR on dozens of existing projects (old and new, small and big), and have not found a single use of "chaining".
This also been discussed on forums and on github: https://github.com/playcanvas/engine/pull/5341 https://github.com/playcanvas/engine/issues/4910
During tests, engine uses somewhere references for event handle (old object) after it has been removed.
Solution:
Proposed implementation changes the behavior of on and once on EventHandler, by returning EventHandle. Which developer can use to detach event by simply calling handle.off().
New APIs:
// pc.EventHandler
let evt = obj.on('event', () => { }); // returns EventHandle

// pc.EventHandle
evt.removed; // true if this event has been removed
evt.off(); // function to simply remove an event

Examples:
ScriptType remove event when script is destroyed or swapped:
Script.prototype.initialize = function () {
    this.evt = this.app.on('event', this._onEvent, this);

    this.once('destroy', () => {
        this.evt.off();
    });
};

Script.prototype.swap = function(old) {
    old.evt.off();
    this.evt = this.app.on('event', this._onEvent, this);
};

Script.prototype._onEvent = function() {
    // event
};

ScriptType with many events:
Script.prototype.initialize = function () {
    this.bindEvents();
    this.once('destroy', this.detachEvents); // make sure we detach events on destroy
};

// bind all events
Script.prototype.bindEvents = function() {
    this.detachEvents();
    if (!this.events) this.events = [];
    this.events.push(this.app.on('eventA', this._onEvent, this));
    this.events.push(this.app.on('eventB', this._onEvent, this));
    this.events.push(this.app.on('eventC', this._onEvent, this));
    this.events.push(this.app.on('eventD', this._onEvent, this));
};

// detach all linked events
Script.prototype.detachEvents = function() {
    if (!this.events?.length) return;
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events.length = 0;
};

Script.prototype.swap = function(old) {
    old.detachEvents(); // detach events from old script instance
    this.bindEvents();
};

Script.prototype._onEvent = function() {
    // event
};

I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

            const handles = this._callbacks[name];
            if (handles) {
                for (let i = 0; i < handles.length; i++) {
                    handles[i].destroy();
                }
                this._callbacks[name] = [];
            }

Shouldn't this._callbacks[name] = []; be just handler.length = 0;? Is there any kind of reference comparison magic somewhere else, which demands this?
Why do we produce Array GC?
Here too:
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events = [];

            const handles = this._callbacks[name];
            if (handles) {
                for (let i = 0; i < handles.length; i++) {
                    handles[i].destroy();
                }
                this._callbacks[name] = [];
            }

Shouldn't this._callbacks[name] = []; be just handler.length = 0;? Is there any kind of reference comparison magic somewhere else, which demands this?
Why do we produce Array GC?
Here too:
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events = [];

Focus of this PR is to with minimal logic changes implement EventHandle. If there is an optimisation of EventHandler methods - good option for another PR.

Focus of this PR is to with minimal logic changes implement EventHandle. If there is an optimisation of EventHandler methods - good option for another PR.

Good point, what about the code that specifically you added?
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events = [];

 * @example
 * // store an array of event handles
 * let events = [ ];
 *
 * events.push(objA.on('testA', () => { }));
 * events.push(objB.on('testB', () => { }));
 *
 * // when needed, remove all events
 * events.forEach((evt) => {
 *     evt.off();
 * });
 * events = [ ];

Usually we handle it like this in the engine:
    destroy() {
        const meshInstances = this.meshInstances;
        for (let i = 0; i < meshInstances.length; i++) {
            meshInstances[i].destroy();
        }
        this.meshInstances.length = 0;
    }

Because why create extra GC for operations that don't require it? We use temporary variables everywhere aswell to not call Vec3#clone for example, so the examples could reflect that, because other devs will take it as... example.

Focus of this PR is to with minimal logic changes implement EventHandle. If there is an optimisation of EventHandler methods - good option for another PR.

Good point, what about the code that specifically you added?
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events = [];

What would be an alternative way of unsubscribing from a list of events?

 * @example
 * // store an array of event handles
 * let events = [ ];
 *
 * events.push(objA.on('testA', () => { }));
 * events.push(objB.on('testB', () => { }));
 *
 * // when needed, remove all events
 * events.forEach((evt) => {
 *     evt.off();
 * });
 * events = [ ];

Usually we handle it like this in the engine:
    destroy() {
        const meshInstances = this.meshInstances;
        for (let i = 0; i < meshInstances.length; i++) {
            meshInstances[i].destroy();
        }
        this.meshInstances.length = 0;
    }

Because why create extra GC for operations that don't require it? We use temporary variables everywhere aswell to not call Vec3#clone for example, so the examples could reflect that, because other devs will take it as... example.

I've updated the example to use .length = 0. Good point.
Events are "detached" and long-lived objects. The usual pattern of working with them is to have them for a long time, and sometimes remove them. Associated memory with each event is small. So re-using event handles is not considered here. Vectors and similar math objects can be created on each frame, so this can lead to a significant GC stall, and we do encourage re-using them, as they can be re-used. EventHandle - cannot be re-used, like many other things within the engine.

Updated this PR with a recent EventHandler refactor (https://github.com/playcanvas/engine/pull/5501).

Events are "detached" and long-lived objects. The usual pattern of working with them is to have them for a long time, and sometimes remove them. Associated memory with each event is small. So re-using event handles is not considered here.

Right, so why give them an off method? It's not like we will on them again? off'ing them is destroy'ing them, so destroy is all that should be required.
My main motivation to get rid of the off method is to simplify the API here. I dislike to have different return values based on some setting like pc.EventHandler.chaining = false; if it's not 100% necessary.
I think we could simply return always and only the EventHandle, BUT the EventHandle has extra deprecation methods to generate warning's for on/off/once method's.
So for the rare case that someone wrote something like:
this._registry
  .off("load", this._onLoad)
  .off("error", this._onError);

They can continue using that code until we decide it had enough deprecation time.

Right, so why give them an off method? It's not like we will on them again? off'ing them is destroy'ing them, so destroy is all that should be required.

That is the current naming convention when working with events. We "off" them.
Happy to hear if PlayCanvas developers are happy to have two different names for the same logical operation.
const evt = app.on('event', onEvent);

app.off('event', onEvent);
evt.off(); // alternative

// or

app.off('event', onEvent);
evt.destroy(); // alternative

I dislike to have different return values based on some setting like pc.EventHandler.chaining = false; if it's not 100% necessary.

I absolutely agree here. But, the engine has a promise to the users that it does not break public APIs, and ensures backwards compatibility. Even with this case, where I personally never seen chaining used in dozens of projects I've worked on.

I think we could simply return always and only the EventHandle, BUT the EventHandle has extra deprecation methods to generate warning's for on/off/once method's.

It will be impossible to have the same behavior, as currently the returned value from EventHandler.on - is the EventHandler itself. So the user can access any properties/methods of EventHandler (and objects that inherit it, e.g. Entity).
Also, off still returns EventHandler, so provided example:

this._registry
  .off("load", this._onLoad)
  .off("error", this._onError);

Will work with this PR.

I absolutely agree here. But, the engine has a promise to the users that it does not break public APIs, and ensures backwards compatibility. Even with this case, where I personally never seen chaining used in dozens of projects I've worked on.

Okay, lets be real here: breaking things is an established procedure, that's why we note it in releases:

The Plane#constructor change alone affected me and at least two others (who happened to speak up in the PR). Who knows how many others.
While this PR is basically obfuscating API by trying to bend over backwards for something that affects... no one?
In my personal fork I ripped the Event chaining out quite some time ago, never experienced any problems in projects I play around with.

@willeastcott, @slimbuck, @mvaligursky what you guys think, should we go with breaking change by returning EventHandle from on and once by default? With very-very little chance that someone wrote with chaining. So we provide a global flag that they can use to switch to the old-way?
That would be definitely amazing, it just goes against a rule of "never break a public API".
I went conservative with this PR, but am happy to go with breaking (unlikely affecting anyone) change.

To be honest, @Maksims, I never knew you could chain these calls and I never have in all the years I've been working with PlayCanvas. I don't recall ever seeing anyone else do that in their code (which doesn't mean they don't do it!).
In this particular instance, where I believe very, very few projects will be affected, I'd rather go with a clean API and a mini-breakage. 😄 What do you think @mvaligursky?

@Maksims - I agree with @willeastcott , that's a main reason to break existing API. I'd say go for it as well, considering this will benefit many users with some inconvenience to almost none.
Extra points are given if there's a way to have Debug.deprecated message to warn the user something no longer works. Or at least I prefer to have an exception in code to happen if we cannot detect it - pointing the user to the change, instead of silently hiding it behind a different behaviour.

EventHandle could have on/off/once/fire methods which simply point out their deprecation and do nothing else.

So we provide a global flag that they can use to switch to the old-way?

This still needs input, I would rather completely drop static chaining = true; which just makes the types crazy (return values based on variables... which no one uses).
I don't want to write code like !(ret instanceof pc.EventHandler) because pc.EventHandle is not exported, just to fix types for a case that I want 100%.

I've updated PR with returning EventHandle by default.
Also (@mvaligursky) added on and once methods to EventHandle, so it is technically backwards compatible with such workflow, except it will warn with Debug.deprecated.

I'm also very happy about the outcome, I would just like to point out the last thing that I'm still not happy with: EventHandle#destroy
I have a function that I'm using in dozens of places:
/**
 * Call each element's destroy method and empty array afterwards.
 * @param {{destroy: Function}[]} arr
 */
export function destroyArray(arr) {
    const n = arr.length;
    for (let i = 0; i < n; i++) {
        arr[i].destroy();
    }
    arr.length = 0;
}

When I call that on an array, I expect that no resource is leaked any longer. But current EventHandle#destroy is leaking the event, because Event#destroy is only marking the EventHandle as deleted. Marking something as deleted is not deleting it, it's simple as that.
You can check every destroy method we have in the engine: https://github.com/search?q=repo%3Aplaycanvas%2Fengine destroy() {&type=code
They all clean up their events in their destroy method and I would like to keep that intuition.
Instead of something like this:
// detach all linked events
Script.prototype.detachEvents = function() {
    if (!this.events?.length) return;
    for(let i = 0; i < this.events.length; i++) {
        this.events[i].off();
    }
    this.events.length = 0;
};

I just write everywhere:
// detach all linked events
Script.prototype.detachEvents = function() {
    if (!this.events?.length) return;
    destroyArray(this.events);
};

Collapsing 4 lines into 1...
So my last change proposal is:

And the four lines of callbacks[i].destroy(); turn into callbacks[i]._removed = true;
In C++ there is a concept of "friend classes", but in JS it's simply @internal (public to "friend classes").
    /**
     * True if event has been removed.
     * @type {boolean}
     * @internal
     */
    _removed = false;

And then you can drop the getter:
    /**
     * True if event has been removed.
     * @type {boolean}
     */
    get removed() {
        return this._removed;
    }

Last but not least:
These changes don't break anything, the unit tests work etc, it's a semantic fix to ensure that destroying means destroying and not marking something as destroyed, while leaking resources.

I have a function that I'm using in dozens of places:

I've updated that function for you:
export function destroyArray(arr) {
    const n = arr.length;
    for (let i = 0; i < n; i++) {
        if (arr[i] instanceof pc.EventHandle) {
            arr[i].off();
        } else {
            arr[i].destroy();
        }
    }
    arr.length = 0;
}

The initial intent was to clean up references within the destroy method, but currently, the engine has places where such references are used after the callback has been removed.
Updated this PR and removed destroy method altogether.

@Maksims Thank you a lot, it looks very good!
Can we just please have a simple destroy method? :sweat_smile:
This is a common pattern:
https://github.com/playcanvas/engine/blob/864b4bdd8ed090b3dc53b1024e7a29838e06b40d/src/framework/asset/asset-localized.js#L217-L221
We could apply that here aswell:
    destroy() {
        this.off();
    }

Yes, I could update destroyArray, but the point is that it shouldn't know any internals - it shall just work following a simple idiom. And the type {destroy: Function}[] is also wrong now.
Anyway, if you add that or not, I'm very happy about the state :+1: Good job! :100:

I just synched with @Maksims and he says he's happy to merge this in its current state. So merging... 😄  Such a great contribution. Thank you all!

Just a heads up. This PR breaks the current playcanvas tween add on when you tween like I have in the code snippet below since the event handlers no longer return this but they return the new EventHandle.
    const params = {
      opacity: 0.5,
      scale: 0,
      yPosition: 0,
    };

    textEntity.entity.setPosition(position);
    textEntity.entity.setLocalScale(0, 0, 0);

    textEntity.entity
      .tween(params)
      .to({ opacity: 1, scale: 1.25 }, (0.1 / 0.24) * duration, CubicOut)
      .chain(
        textEntity.entity
          .tween(params)
          .to({ scale: 1 }, (0.06 / 0.24) * duration, CubicOut)
          .on('update', () => {
            textEntity.entity.setLocalScale(params.scale, params.scale, params.scale);
          }),
        textEntity.entity
          .tween(params)
          .to({ yPosition: 0.5 }, (0.02 / 0.24) * duration)
          .on('update', () => textEntity.entity.setPosition(
            position.x,
            position.y + params.yPosition,
            position.z,
          )),
        textEntity.entity
          .tween(params)
          .to({ yPosition: 0.75, opacity: 0 }, (0.06 / 0.24) * duration)
          .on('update', () => {
            textEntity.entity.element.opacity = params.opacity;
            outlineColor.a = params.opacity;
            textEntity.entity.element.outlineColor = outlineColor;
            textEntity.entity.element.shadowColor = outlineColor;
            textEntity.entity.setPosition(
              position.x,
              position.y + params.yPosition,
              position.z,
            );
          })
          .on('complete', () => {
            textEntity.active = false;
            textEntity.entity.enabled = false;
          }),
      )
      .on('update', () => {
        textEntity.entity.element.opacity = params.opacity;
        outlineColor.a = params.opacity;
        textEntity.entity.element.outlineColor = outlineColor;
        textEntity.entity.element.shadowColor = outlineColor;
        textEntity.entity.setLocalScale(params.scale, params.scale, params.scale);
      })
      .start();

@Maksims - any thoughts on the comment above?

I wanted to look into this all day too, but working on something else... quick ad-hoc solution should be a prototype patch and return this again

@Maksims - any thoughts on the comment above?

Small patch of chain method to use scope of EventHandle - will do the trick.

We are also mixing "illegal" ES5 patterns with ES6 in playcanvas-tween:
https://github.com/playcanvas/playcanvas-tween/blob/3e0eb3b40b5d1155efa1a27d2e1d33590f9cabe3/tween.js#L1
We are not coming around the fact that we have to have some breakage in old ways of doing things, because it's simply not possible any longer - ES6 is here since 2015 and we didn't catch up too much in PC libraries (tween / spine lib).
The upside is that we can get a somewhat simpler typing experience too by following standard ES6 ways (compared to namespace merging in e.g. playcanvas-tween). E.g. instead of pc.SineOut we could introduce a default pcTween.SineOut for ES5 users?
And ES6 users could use whatever, like import { SineOut } from 'playcanvas-tween';
If we already need to update two things, we can just overlap it so developers only need to update once and are "good to go" again.

With a second glance at a tween library recommended ways of doing things, and it heavily relies on chaining. This is the case where not forcing breaking change, but having it behind the flag would help.
Updating the tween library with its own methods like .update(callback) and .complete(callback) - will help, but will require a migration by its users.

We are also mixing "illegal" ES5 patterns with ES6 in playcanvas-tween:

This is outside of this PR's scope, please open a separate issue or propose a PR in a related repo.


Upgrade 1.5.2 and improve debugging

This PR includes

Upgrade Confluent.Kafka 1.5.2
Adding Following Libkafka properties with default values.
Add Log to identify if users use SingleFunctionExecutor or MultipleFunctionExecutor
Redirect Libkafka Log to the ILogger

Setting
librdkafka property
default
Trigger or Output

LibkafkaDebug
debug
null
Both

MetadataMaxAgeMs
metadata.max.age.ms
180000
Both

SocketKeepaliveEnable
socket.keepalive.enable
true
Both

Upgrade Confluent Kafka for avoiding limitation for Azure about the log-lived TCP Connection
The reason of the default settings, refer to this issue
Add Log to detect which FunctionExecutor do they use?
For the log of FunctionExecutor, I'd like to know if a user uses Single or Multiple Function Executor for diagnosing an issue.
If there is a better place, please let me know.
Redirect the Log of Libkafka native library
Currently, the Libkafka message is showed up standard output, that means there is no way to fetch it from Application Insights or other logging system.
Debug option enables librdkafka logging. https://github.com/edenhill/librdkafka
Fix
https://github.com/Azure/azure-functions-kafka-extension/issues/185
https://github.com/Azure/azure-functions-kafka-extension/issues/187

I upgrade the Confluent.Kafka library to 1.5.2
Also, I add topic.metadata.refresh.interval.ms configuration support for EventHubs.
https://github.com/edenhill/librdkafka/issues/3109

I update this PR according to the https://github.com/Azure/azure-functions-kafka-extension/issues/187


Home page

Number of Volunteers: 1
One volunteer should be in charge of updating the content on the home page.

The homepage should include the following:

[ ] Introductory video / Welcome note from Program Chairs
[ ] Video/Slides from Infrastructure Chairs describing how to navigate the website
[ ] Overall Schedule of the conference

@hao-fang: Please add if I missed something.

We may want to embed the read-only #announcement RocketChat channel on the Home Page.
I'm not sure if it will look good though. An alternative is to make a new page of #announcement.

[ ] Do something like ICLR did with a blurb of all elements of the conference: https://iclr.cc/virtual/index.html

@raosudha89 can you keep track of these two issues as well?

[ ] #86
[ ] #87

[ ] Find the right way to embed two videos into the homepage

Details:
I was trying to embed to two videos in this page using the code below:

Welcome message from General Chair and Program Chairs

Message from Virtual Infrastructure Chairs about the new virtual conference format

However, when I use the same id for the div and a different ids under presentationId, it does not display two videos for some reason.
The reason I was thinking using different div id is because here is an example from ICLR page where they embed two slideslive videos and they do that using two different div ids: https://github.com/ICLR/iclr.github.io/blob/master/templates/pages/expo.html
But to do this, I need to know where is the id 'presentation-embed' defined. I am unable to find that.

@hao-fang is a volunteer still needed for this?

@vladdy
@raosudha89 is currently on this so I'll let her explain. My understanding is that this is basically done at least for the "Basic Website" task. We can improve the layout as a "Website Enhancements" if we have time #169 .

I think it looks nice enough now with #198


Wagtail 1.8.1

This PR upgrades our Wagtail version from 1.7 to 1.8.1. See Wagtail release notes for 1.8 and 1.8.1.
Selected changes

Ability to restrict page privacy to public, private with password, private to logged-in users, and private only to users in certain groups.
New "bulk delete" permission available to grant ability to delete entire page trees (not applicable to us as deletion is disabled through the UI).
New StaticBlock option for inserting static content into a StreamField editor; this has been asked for several times as a way to provide editors with more detailed instructions about entering content.
ChoiceBlock now accepts a callable as an option for choices, which should allow us to reduce migrations generated when editing lists in ref.py.

(see release notes for full list)
Screenshots
New page privacy dialog

Notes

As a side effect of this upgrade, our dependency on the requests library has been increased from 2.7.0 to 2.12.4.

Checklist

[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Passes all existing automated tests
[X] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[X] Reviewers requested with the Assignee tool :arrow_right:

ChoiceBlock now accepts a callable as an option for choices, which should allow us to reduce migrations generated when editing lists in ref.py.

Nice! Does this mean we'll be able to clean up any of the code we did to work around this for the resource snippets?

This looks to my memory like the least amount of code changes we've had to make for a Wagtail upgrade.

Thanks to a familiar name: http://docs.wagtail.io/en/v1.8.1/releases/1.8.1.html

@Scotchester possibly, and I think there's some additional cleanup that could be done to the filterable list code that also pulls in content from ref.py. I'm not including that cleanup in this PR to keep its scope limited to the upgrade.


License

We need to choose a license...

Any update on this? I was just about to file the same issue.

This is a hot topic about Mull we are actively looking into now. Is there anything that is blocking you from trying Mull without a license at the moment?

@mbrukman, this is a hot topic about Mull we are actively looking into now. Is there anything that is blocking you from trying Mull without a license at the moment?

The lack of a license implies "copyrighted with all rights reserved" which legally prevents anyone from doing anything with this repo. This issue has been open for almost a year (since Dec 2016).
Here's what GitHub says regarding this situation:

You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license.

Downloading a copy of the project's source code == "reproduce" and sharing with a colleague or incorporating into another project == "distribute". Default copyright laws prevent both of those actions.

The lack of a license implies "copyrighted with all rights reserved" which legally prevents anyone from doing anything with this repo. This issue has been open for almost a year (since Dec 2016).

We are very much aware of this. The reason of why there is still no license is very simple: we are much better in mutation testing at this point than in understanding the license topic well enough to pick up the right license. We have been actively developing Mull in our spare time since mid of 2016 and our focus was on development side of things. It is only now that we are getting Mull to a usable v1 and it is only now that people are starting to take Mull seriously. Additionally we are talking to people who expressed interest in commercial use of Mull and that adds some complexity to the license question which we have to carefully consider.
I can only repeat that we are actively looking into this and apologise for inconvenience that the absence of license might cause if you want to give Mull a try. We are trying to find the right license as soon as possible.


Automate app packaging

@Chunosov
Please describe steps of manual packaging from original sources
Then we will try to automate and add to CI (travis)

Added redist script in #10

Redists scripts are there. Making the app buildable properly via CK is a big story which will be covered by other, more specific tasks (the first one of them is #25). So, closing this ticket.


Support multiple methods in compound/macro tasks.

As mentioned on discord, just noting here that "Methods" in "Compound Tasks" as mentioned on page 5 in this description of HTNs are missing from the implementation :) https://www.gameaipro.com/GameAIPro/GameAIPro_Chapter12_Exploring_HTN_Planners_through_Example.pdf

Adding a note that it was after this issue was posted that I added issue templates. No need to change it as it works just fine. (Trying to pre-empt any white-knighting)


Issue with k8s.io/docs/tasks/tls/managing-tls-in-a-cluster/

This is a...

[ ] Feature Request
[ X] Bug Report

Problem:

Step zero points to a package directory filled with various packages, but does not declare which to install. Can these same steps be done via openssl, which often is installed already? Perhaps it should use a more common tool to generate a .csr file.

2)The page does not represent what I see when following the steps.
Step 3 has functions later on the page, that should be explained as part of the step. If there is more than just kubectl certificate approve it should be explained.  Tried that step but it replies Approved, but not Issued as the page would indicate.

In step 4 the proposed jsonpath='{.status.certificate}' does not exist. If the intention is to generate a key perhaps the command should be: kubectl get csr my-svc.my-namespace -o jsonpath='{.spec.request}' | base64 -d > server.crt

Proposed Solution:
The page seems like what someone thinks the steps would be instead of what someone who doesn't already know the process would need to know to complete the step.
Page to Update:
http://kubernetes.io/...
https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/

From kubectl cluster-info dump:
"KernelVersion": "4.4.0-1039-aws",
"OSImage": "Ubuntu 16.04.3 LTS",
"ContainerRuntimeVersion": "docker://1.12.6",
"KubeletVersion": "v1.8.2",
"KubeProxyVersion": "v1.8.2",
"OperatingSystem": "linux",
"Architecture": "amd64"

The information on the page does not cover enough of what it takes to manage TLS certificates in a cluster. Someone with intro knowledge of kubernetes and lots of Linux admin ability would remain unable to use this information to replace a compromised key.

Closing this is okay.
Creating certificates that contains SANS is not so straightforward when using openssl.
Ref: https://kubernetes.io/docs/concepts/cluster-administration/certificates/#openssl


--includeOptional varying behaviours

For install --includeOptional "not the recommended components" but for download ("layout") --includeOptional "includes the recommended...components". Is this correct, if so the difference in behaviours should be emphasised in this very clear and useful doc.

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

ID: 5e97b834-fa82-6aa0-5913-4d5a8ed23366
Version Independent ID: e988e3ea-8565-ca88-6ade-ab67425a51ae
Content: Use command-line parameters to install Visual Studio
Content Source: docs/install/use-command-line-parameters-to-install-visual-studio.md
Product: visual-studio-dev15
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@andykn Thanks for your feedback; we appreciate it! We'll investigate and report back.
(@tydunkel - let's discuss this.)


refactor ForgeEnergyIntegration to translate to IStrict* Mekanism classes

Should fix #4645
Previously the forge integration was passing to RF methods, which now get stripped if RF isn't there.
@aidancbrady just to be sure, the IStrictEnergyAcceptor and kin accept Mekanism J, yes?

Correct, thanks!


Adding image size in data loader in README

#Resolves #150
This issue resolves the value error pointed out in Issue 150.
The Data loader loads images that are not in the powers of 2, which is a requirement for the image processing to work. So a parameter needs to be passed in the data loader.

Hi @Shivansh20128,
Thanks for opening this PR. I checked the error and it seems the code in the README.md needs to have an argument mentioning the size of the image as a power of 2 for the INEQR embedding to work. We cannot directly change the load_mnist_dataset function since that function is used to download images of all sizes. So I suggest doing something like this:
# Load MNIST dataset
train_dataset, test_dataset = load_mnist_dataset(image_size=2)

Feel free to make these changes to the README.md. Let me know if you would need any help here!


[Question] Incompatible Graphic Card

I have a Intel HD Graphics 4000 and it don't work for windows but for other devices it work, so if I use this, what happens to game? just a crash or it can break my pc?

If you are using Linux the game will run. On Windows it shouldn't run because of the Intel drivers and your video card. That's it.

The Intel HD 4000 does not support Vulkan.

It support Vulkan on Linux via Mesa drivers.

Even with Mesa Vulkan support on anything older than Broadwell is incomplete and broken.


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2024-01-30T16:38:54+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
8321b4114219a35ca1ff18212bafd598ffafc30a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

https://github.com/istio/api/pull/3072


Contact Julian Helmchen

Julian Helmchen (Freie Universität Berlin, Friedrich-Meinecke-Institut)
he has the project to make a big corpus of German GT with Transkribus

Although... (screenshot from the slide shown @ Transkribus User Conference 2022)


Reformat feature.name and reintorudce data and plot() for CompoundFeatures

See #417 for the conversation on feature names.
Averaged data and averaged graphs decided to be added in the dev meeting on 22.02.2024

Please use https://github.com/FZJ-INM1-BDA/siibra-configurations/tree/use_v04_feature_ids for configuration to test.

note: waiting on me (@xgui3783 ) to create a preview viewer/api instance

additional regression not covered by tests
some features now have duplicated ids
sample code:
import siibra

siibra.cache.clear()

region = siibra.get_region("cortical layer", "1 left")

f, = siibra.features.get(region, "cell density profile")
print(len([_ for _ in f]), len({_.id for _ in f})) # prints 5 3

@AhmetNSimsek are the new commits meant to address https://github.com/FZJ-INM1-BDA/siibra-python/pull/568#issuecomment-1966356183 ?

@AhmetNSimsek are the new commits meant to address #568 (comment) ?

Indeed! I forgot to ping you, sorry.

Codecov Report
Attention: Patch coverage is 33.87097% with 41 lines in your changes are missing coverage. Please review.

Project coverage is 49.35%. Comparing base (5a0e6b3) to head (b8b3bff).
Report is 477 commits behind head on main.

Files
Patch %
Lines

siibra/features/feature.py
42.30%
15 Missing :warning:

...bra/features/connectivity/regional_connectivity.py
23.07%
10 Missing :warning:

siibra/features/tabular/cortical_profile.py
33.33%
8 Missing :warning:

...a/features/tabular/regional_timeseries_activity.py
30.00%
7 Missing :warning:

...a/features/connectivity/functional_connectivity.py
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #568       +/-   ##
===========================================
+ Coverage   36.81%   49.35%   +12.53%
===========================================
  Files          61       74       +13
  Lines        5421     6980     +1559
===========================================
+ Hits         1996     3445     +1449
- Misses       3425     3535      +110

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


Added doc tests for up_to and down_to panic cases

Fixes #11.
I've kept the original tests intact, for now. Meanwhile, the doc-tests can serve our documentation needs.

@killercup The build target with clippy-preview is failing. Do you think we should try with clippy instead of clippy-preview?


⚠ Bofrost.lu has degraded performance

In 4db2152, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1052 ms

Resolved: Bofrost.lu performance has improved in 7f6120a after 8 minutes.


Update check fails.

[4:18 PM] Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
[4:18 PM] Error checking updates on 'https://github.com/apocc/pw-mods/blob/master/repo.json'.
Unity Mod Manager 0.23.5b

Thanks for pointing that out. It should be fixed with v1.1.1.


Reference Issue #6297

If you close the rescan while it is in progress, will it continue where it left off when you start it again?

@Roasbeef I left it running for several days and it didn't finish syncing. What do you think I should do?


Harmonic Synthesis, Alpha

This PR represents the ALPHA RELEASE of the vision doc:

The tenets have been replaced with a list of desired experiences.
There are no combined narratives yet, but the roadmap is (I believe) complete and readable, and the User's manual of the future describes the plans in a form that can hopefully give you a good feeling for its impact. There are also clearly enumerated deliverables, each describing the intended impact as well as design notes.
The submitted stories have been moved to an appendix.

What comes next

[ ] Continue updating roadmap, design notes, and other details
[ ] Author combined status quo, shiny future narratives
[ ] Evaluate impact of proposal on the various projects
[ ] Review plans with appropriate teams
[ ] Select owners for the various initiatives and get things going

How to give feedback
I welcome feedback, but I also don't want this to become a "mega RFC thread for everything ever". Therefore, I request the following:

Please leave structured reviews, not random comments.
Feel free to respond to points on other people's reviews, but keep the back and forth to a minimum.

I plan to schedule 1:1 time with major stakeholders to go over particular points of interest, so what I'm looking for here is more of a 'heads up, this is an area to dig more into' than a 'let's figure it out in this thread'. If you like, you can take something to Zulip for more conversation (#wg-async-foundatons stream).

If you think I've made factual inaccuracies, or overlooked concerns, I would particularly like to know that. My goal is to turn every major point into a FAQ or an alternative or something like that, so that this document really captures the conversation we have here and elsewhere.

This is minor, but could your "Rendered" link go directly to https://nikomatsakis.github.io/wg-async-foundations/vision/harmonic.html ? Had to dig a bit through the menu to find it.

OK! I've updated the OP to reflect this, but this PR now represents the "alpha release" of the vision doc:
This PR represents the ALPHA RELEASE of the vision doc:

The tenets have been replaced with a list of desired experiences.
There are no combined narratives yet, but the roadmap is (I believe) complete and readable, and the User's manual of the future describes the plans in a form that can hopefully give you a good feeling for its impact. There are also clearly enumerated deliverables, each describing the intended impact as well as design notes.
The submitted stories have been moved to an appendix.

Reading through this as a relative outsider, I think there is a strong vision for the end goal and the roadmap/deliverables seem pretty exhaustive, but what I'm missing is a description of how the deliverables will satisfy the goals in the vision. IOW, even if everything in the roadmap gets ticked off, I can't figure out if we will have arrived at the shiny future or not.

Thanks @nrc. In the "User's Guide", there were links to specific deliverables that implement each point, I wonder if part of what was missing was that the "concrete designs" aren't really known yet. We have things in mind but it's somewhat intentionally vague, and instead meant to describe the intended experience, so that we have space to work out the best path as we go. (To be included, though, I felt like I had to have "reasonably strong" confidence that the idea can be done.)

Hi all! I've been talking with @tmandry and these are the next steps we have in mind:

To start, we're going to merge this PR, since it's basically the right starting point (that will require a somewhat annoying rebase...).
Next, we're going to upgrade the status quo and shiny future stories to have narratives based on a few chosen projects that illustrate the major problems that we see. I have a branch laying out some of that work, but I'm going to open it as a follow-up PR.
We're actively discussing who to setup as owners of each area and we'll be following up on that.

Thanks @nrc. In the "User's Guide", there were links to specific deliverables that implement each point, I wonder if part of what was missing was that the "concrete designs" aren't really known yet. We have things in mind but it's somewhat intentionally vague, and instead meant to describe the intended experience, so that we have space to work out the best path as we go. (To be included, though, I felt like I had to have "reasonably strong" confidence that the idea can be done.)

Yeah, the links from the user guide were pretty useful, I guess I was looking for maybe a document or section that was just that mapping for quick reference (rather than being embedded in the user guide) and with some explanation of how the deliverable satisfies the goals in 2.2 and 2.6, where it is less obvious (especially 2.2, the mapping to 2.6 is a bit clearer IMO and one also has to be able to map the concrete goals of 2.6 to the abstract goals of 2.2).


Add React lazy and loaders to the website

Hey hii
Can i work on it?

Hello @rohitrokz29
I have assigned you the issue you may start working on it

I have added React lazy Loading. Is there any other Loader needed to be added ?

Send a pull request, after reviewing the pull request, I will tell you what things can be added or changed.

I have sent a pull request. Please check .


Can not make compression work with static files

Please help. Compression does not work. There is no Content-Encoding in responses
var express = require('express');
var compression  = require('compression');
var app = express();

app.set('port', (process.env.PORT || 5000));
app.use(compression());
app.use(express.static(__dirname + '/public'));

app.listen(app.get('port'), function() {
  console.log("Node app is running at localhost:" + app.get('port'));
});

Hi! Your code above works perfectly for me, but since you didn't provide a static file to use, I cannot help much further.
Compression depends on three main things you didn't provide:

What are the request headers you are sending to the server?
What is the type of the file you are serving?
What is the size of the file?

Thank you for response. Here is curl of request
curl "http://my-server.com.angular.js" -H "Pragma: no-cache" -H "Accept-Encoding: gzip, deflate, sdch" -H "Accept-Language: ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4" -H "User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36" -H "Accept: /" -H "Referer: http://my-server.com/" -H "Connection: keep-alive" -H "Cache-Control: no-cache" --compressed
And response:
Accept-Ranges:bytes
Cache-Control:public, max-age=0
Connection:keep-alive
Content-Type:application/javascript
Date:Mon, 25 May 2015 21:32:56 GMT
Etag:W/"e90aa-1077232132"
Last-Modified:Mon, 25 May 2015 21:09:53 GMT
Server:Cowboy
Transfer-Encoding:chunked
Vary:Accept-Encoding
Via:1.1 vegur
X-Powered-By:Express

Thank you. How big is the file (in bytes). By default we will not compress a file if it under 1kb. I can also see by your response you have a proxy between you and the server. This is the problem pretty much 100% of the time. Can you make the request directly to the server without going through the proxy?

The size of file is 958KB. It does not work even if run node index.js on my computer

Unfortunately everything works perfectly for me with the code you sent. This means that I will just have to await a PR from you that fixes the issue, unfortunately. I will await a PR with the fix :)

I'm going to close this for now due to lack of reproduction. If you are able to figure out the issue and it turns out to be a bug in this module, a PR would be very welcome :) Here is the console session from when I tried to reproduce the issue with the information provided:
$ cat app.js
var express = require('express');
var compression  = require('compression');
var app = express();

app.set('port', (process.env.PORT || 5000));
app.use(compression());
app.use(express.static(__dirname + '/public'));

app.listen(app.get('port'), function() {
  console.log("Node app is running at localhost:" + app.get('port'));
});

$ node -v
v0.10.33

$ npm i compression express
<EMAIL_ADDRESS>node_modules\compression
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules\express
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
$ mkdir public

$ node -pe 'console.log("/* " + new Buffer(958 * 1024) + " */")' > public/example.js

$ ls -lh public/
total 480k
-rw-r--r--    1 user     group     958k May 25 17:59 example.js

$ node app.js &
[1] 14108
Node app is running at localhost:5000

$ curl -XGET -I -H'Accept-Encoding: gzip, deflate, sdch' http://localhost:5000/example.js
HTTP/1.1 200 OK
X-Powered-By: Express
Accept-Ranges: bytes
Date: Mon, 25 May 2015 22:03:32 GMT
Cache-Control: public, max-age=0
Last-Modified: Mon, 25 May 2015 21:59:33 GMT
ETag: W/"ef815-3318529146"
Content-Type: application/javascript
Vary: Accept-Encoding
Content-Encoding: gzip
Connection: keep-alive
Transfer-Encoding: chunked

Please try to follow my console session above yourself to see if it reproduces for you. If following the above still shows Content-Encoding: gzip in the response like mine does, then it didn't reproduce the issue. If there are adjustments you can make that reproduce it, please feel free to follow up with the full instructions to reproduce, in the format as above so I can reproduce.

ok, thank you. I'll try

I've had the same problem as well. Your test script worked for me, however. The difference seems to be using -XGET in the curl command. According to this page:
http://stackoverflow.com/questions/8498371/curl-get-and-xget
the difference is that -XGET forces curl to use a GET request. By default it is doing a HEAD request, which I guess doesn't get gzipped.
So it looks like compression is turned on, it just doesn't appear to be thanks to curl.  Could you include instructions for using curl properly to verify gzip in the readme?


Fix external links

Fixes #3371
Some links to github PRs might still be timing out, e.g.:
[Step 1/1] docs/releases/v1.1.6.html
[05:03:41][Step 1/1]   request exceeded our ExternalTimeout --- docs/releases/v1.1.6.html --> https://github.com/cockroachdb/cockroach/pull/22893

@benesch, any tips on how to increase that timeout threshold?

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4a0edabb9c0f3d6e03c101718de11df6fcd7f40a/

You can bump the ExternalTimeout in .htmltest.yml. I'm skeptical that will help, though; 30s should be plenty. Perhaps we're bumping up against a GitHub rate limit.


gRPC service call in istio behave inconsistent

Describe the bug
Sometime happening
Service to service call in istio mesh giving Unimplemented, at the same time ingress call is working fine. After sometime, (may be due to restart target service) its working fine. This happening vice-versa as well (service to service call working fine but ingress giving Unimplemented exception).
Expected behavior
It should work at all cases all time
Steps to reproduce the bug
Inconsistent
Version
istio 1.04
Kubernetes v1.12 & v1.13
Installation
Helm
Environment
GKE and Baremetal(RKE)

Im seeing a similar result, i can call my application service directly via grpc and it works but through the ingressgateway im getting Unimplemented and i do not see the request making it to the service. I do not see any logs in my applications istio-proxy logs when calling through the ingressgateway
Ingress gateway log
[2019-03-22T14:02:48.079Z] "POST /summaft.infrastructure.v1.SFTService/GetClientHTTP/2" 200 - 0 0 0 - "<IP_ADDRESS>" "grpc-node/1.17.0 grpc-c/7.0.0 (osx; chttp2; gizmo)" "ace2ff26-b6dc-4d0d-a5d0-fcdbd2f6b9ea" "<IP_ADDRESS>:81" "-" - - <IP_ADDRESS>:80 <IP_ADDRESS>:54169

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: sft
  namespace: sft
spec:
  hosts:
  - '*'
  gateways:
  - istio-autogenerated-k8s-ingress
  http:
  - match:
    - uri:
        prefix: /
    route:
    - destination:
        port:
          number: 8064
        host: sft

Hello Istio! What is the answer for this. How is this being addressed and what do you suggest for debugging errors of this type?

One possibility is to set an DestinationRule and set turn off timeouts. This might be an underlying reason but I am not sure. Still investigating.

Thanks for the report. It doesn't seem like there is enough info here for us to take any action and there hasn't been any activity.
If you are still experience this problem feel free to open an issue with more information. Thanks!


Issues with downloading score image from editor

There are 2 issues currently with downloading score image:

Score image is only rendered fully if the image opacity slider is set to full. IMO, the score image should be given fully no matter what level the slider is, as it is irrelevant to the editor.

Files are downloaded as PNG files, which is weird because the backend uses jpg files. Perhaps look into changing that?

Fixed in 53c480db8289601bf1257a3b89c8e3917523931b


Render 'stats' REST API data in Hub web pages

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/241
Originally created by @aaronsteers on 2022-04-20 21:24:51

View 7 previous comments from the original issue on GitLab


Not compatible with sketch 39.1

@fuggfuggfugg :) I'm sure your already on it !

Thanks for reporting. However I cannot replicate.

Yep, my bad, It's working just fine! Keep up the good work


cannot import name 'NotePayload' from 'mipac.types'

Describe the bug
With Mipac 0.1.0 there is a new error occuring, when starting the bot.
I tested it with ceilingfox's unaltered code, only the new MIPAC version in a venv
Code snippets
from mipa.ext import commands, tasks
from mipa.router import Router
from mipac.models import Note
from mipac.util import check_multi_arg
[...]
if __name__ == "__main__":
    bot = MyBot()
    asyncio.run(bot.start(url, token))

Code run with the former version 0.0.2 just fine
Error
Traceback (most recent call last):
  File "/home/ente/git/Misskey-Bot-CeilingFox/cfbot.py", line 4, in <module>
    from mipa.ext import commands, tasks
  File "/home/ente/git/Misskey-Bot-CeilingFox/venv/lib/python3.10/site-packages/mipa/__init__.py", line 10, in <module>
    from .client import Client
  File "/home/ente/git/Misskey-Bot-CeilingFox/venv/lib/python3.10/site-packages/mipa/client.py", line 18, in <module>
    from mipa.state import ConnectionState
  File "/home/ente/git/Misskey-Bot-CeilingFox/venv/lib/python3.10/site-packages/mipa/state.py", line 9, in <module>
    from mipac.types import ChatPayload, NotePayload, UserPayload
ImportError: cannot import name 'NotePayload' from 'mipac.types' (/home/ente/git/Misskey-Bot-CeilingFox/venv/lib/python3.10/site-packages/mipac/types/__init__.py)

To Reproduce
Update Mipac and try to start the bot
Expected behavior
Bot starts
Correct behavior
Please describe the behavior you think should be desired.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment used:

OS: Linux, Windows and WSL
Python: 3.10 in a venv via PyCharm
MiPAC: Mipa 0.0.2 ; Mipac 0.1.0

Is this a pip install using git?

Ah, I understand. This is a problem on the MiPA side; there was a major type name change on the MiPAC side, but I forgot to change the MiPA. Sorry about that. Please wait a while for the fix.

I think I fixed it. Please uninstall mipa and execute the following command.
pip install git+https://github.com/yupix/MiPA.git


Add cargo features for optional crates

Some crates, like clap or tabled, are only relevant to a small number of users. We should only include these features if the library's user actually needs them. Therefore, we should use Cargo features to conditionally compile those crates and theirintegration.
Fixes #204
Also I removed the cargo build CI workflow, because we don't produce any binaries here. Just running cargo check should be enough right? We only want to make sure it compiles.

Codecov Report
Patch coverage: 21.73% and project coverage change: +0.07 :tada:

Comparison is base (9f84635) 48.00% compared to head (c2caa23) 48.08%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #208      +/-   ##
==========================================
+ Coverage   48.00%   48.08%   +0.07%
==========================================
  Files          30       30
  Lines       10904    10913       +9
==========================================
+ Hits         5235     5248      +13
+ Misses       5669     5665       -4

Flag
Coverage Δ

unittests
48.08% <21.73%> (+0.07%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

kittycad/src/types.rs
3.91% <2.70%> (-0.03%)
:arrow_down:

openapitor/src/lib.rs
84.93% <100.00%> (+0.28%)
:arrow_up:

openapitor/src/types/mod.rs
90.08% <100.00%> (+0.02%)
:arrow_up:

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


dist.nuget.org download links overlap the border

nuget.exe download links on dist.nuget.org go outside of the box in Firefox

This page should be updated to a format that supports a long list of versions for each of these components since we will continue to add to this list.

was fixed


Add Koalas support for properties and methods not explicitly defined in woodwork.

We can use this extend functionality to allow methods and properties not explicitly written for our Woodwork DataTables to be used for DataTables with Koalas dataframes as the underlying data type.
https://koalas.readthedocs.io/en/latest/reference/extensions.html

Closing. Duplicate of #493


fix application properties for embedded csp

Rationale
This PR provides a way to define two different headers enforce and report for content security policy delivered through embedded tomcat.
Related Pull Requests

https://github.com/LabKey/server/pull/626

Changes

new application.properties - csp.enforce and csp.report

@ankurjuneja @labkey-matthewb It looks like this change broke the existing CSP we're using with standalone Tomcat on TeamCity.

@ankurjuneja @labkey-matthewb It looks like this change broke the existing CSP we're using with standalone Tomcat on TeamCity.

Nevermind. It didn't.


Added fade up animate on scroll effect

Animation can increase user experience... That's why I add this animation..
@devansh016 Preview :-

Sorry for the fast preview... Hope that you can understand what is changed!

@yashchaudhari008 should we include this? Will this be distracting for user or will align with our minimal news goal?

@yashchaudhari008 should we include this? Will this be distracting for user or will align with our minimal news goal?

Animation breaks at end of page.
Thanks for considering me @devansh016 , I personally think animations are great.
But in this case, I think animation should be more subtle.
I also notice that if we fast scroll, cards are loads in bulk (means 4-5 cards follow same animation) making app look kinda laggy.

Thanks for the contribution. I have approved this PR for hacktoberfest but will not be merging this Pull Request. @Muhammed-Rahif

@yashchaudhari008 should we include this? Will this be distracting for user or will align with our minimal news goal?

Animation breaks at end of page.
Thanks for considering me @devansh016 , I personally think animations are great.
But in this case, I think animation should be more subtle.
I also notice that if we fast scroll, cards are loads in bulk (means 4-5 cards follow same animation) making app look kinda laggy.

Yeah... I noticed that... 👍
I will be back with another feature or something else... If there is one to work on, please mention...
And thank you very much to accepting for hacktoberfest...❤😊


5.0.8 release

hi @timmolter if you have some time to cut the next release this week that would be awesome!

ok, I'll do it this week some time. Thanks for the reminder...

done


Also sync Virtual IPs with a VHID group to backup host, closes #3034

I ran the following tests (after the third commit):
Create:
- CARP: works
- VIP without VHID: works
- VIP with VHID: works:

Modify:
- CARP: works
- VIP without VHID: works
- VIP with VHID: works

Delete:
- VIP with VHID: works


MQTT problem in 0.1.5

There is s problem in 0.1.5.
The cam doesn't send mqtt messages because of an error in mqttv4 daemon.

Confirm that this is resolved in 0.1.6, thanks!

Closed due to being fixed in v0.1.6


Error: Code=CrossTenantDeploymentNotPermitted

Are there additional permissions that need to be setup to deploy resources across two subscriptions?
I am using the user account setup by the company I work for, which I use for deploying into our corporate development subscriptions. In my personal directory, I've setup my corporate user as User Type 'Guest' and the Source shows up as 'External Azure Active Directory'. The user has been assigned 'Contributor' role on the second (personal) subscription (Visual Studio Enterprise). When I attempt to deploy, logged in as the corporate user, in the corporate subscription context, I get the following error that says the deployment cannot deploy to my personal subscription: "New-AzResourceGroupDeployment : 07:52:35 - Error: Code=CrossTenantDeploymentNotPermitted; Message=The template deployment tries to deploy resources to
subscription 'd5ae...'. However, the current tenant '9d3f...' is not authorized to deploy resources to
that subscription."

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

ID: 5a327806-354a-df02-bfef-91a912750d1a
Version Independent ID: 4aae591f-bacf-d40b-b939-a11ca7c8d9db
Content: Deploy Azure resources to multiple subscription and resource groups
Content Source: articles/azure-resource-manager/resource-manager-cross-resource-group-deployment.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@brianstringfellow, Thanks for the question! We are taking a look into this and will get back to you soon.

If I understand your issue correctly, the "user/Identity" with contributor role, maps to the tenant ID = "9d3f..." Curious to know if granting the "user" owner role (instead of Contributor) and see if that resolves your issue.
If issue persists, please raise a support ticket with our technical support team using these steps. If you don't have a support plan, send mail to<EMAIL_ADDRESS>include your subscription ID and a link to this thread (for context) and we will gladly connect you with our technical support team.
We will now close this thread but look forward to your update on our support channel.


Wallet

Story
hi there
Firsst of all after all of your efforts discuraging a user to interact with you i finaly made it after 5 hours .
Your wallet is the most discouraging thing to interact in crypto .
Whyyyyyy??????
Why i have to pay to interact with you protocol ??
Why i have to open  a temporary wallet and then get to the . near wallet why?????
Why users use other things then your wallet to ineract ??
Why i have to pas fbi to get into discord ???
Why i have  to have 4 near for 2fa ?????
You supposed to be the better and cheaper version of ethereum and yoy ask for money before even i made atrrade whyyyyyyyyyyyyyyyyyyyyyyyy?????????????????????
As a USER who PRECONDITIONS, I want to DO_THING so I can ACCOMPLISH_GOAL.
Acceptance Criteria

[ ] AC1
[ ] AC2
[ ] Mobile ok
[ ] Tested

Unhappy Path
Assets

Mockup:

NOTES

This is great UX feedback and duly noted, you can learn more about the concept of gas here: https://docs.near.org/docs/concepts/gas.  For DApps you connect to they might require minimum storage staking to use the DApp that's up to the DApp authors. https://docs.near.org/docs/concepts/storage-staking

Closing for now and made a note about improving our ux copy to clarify


fix install deps

Hi
Thanks for the package!
After I installed the package, it broke down, when I did:
from danlp.datasets import DDT
ddt = DDT()
ddt_ne = ddt.load_as_simple_ner(predefined_splits= True)

As far as I can see, this is due to the fact, 'pandas' and 'conllu' are both used in the code but NOT included as install requirements in setup.py.
I suggest, you include both.
I understand, why you do not include stuff like 'torch', 'flair' and so on to keep the package lightweight, but I think the above dependencies should.

Hi
Thanks for the package!
After I installed the package, it broke down, when I did:
from danlp.datasets import DDT
ddt = DDT()
ddt_ne = ddt.load_as_simple_ner(predefined_splits= True)

As far as I can see, this is due to the fact, 'pandas' and 'conllu' are both used in the code but NOT included as install requirements in setup.py.
I suggest, you include both.
I understand, why you do not include stuff like 'torch', 'flair' and so on to keep the package lightweight, but I think the above dependencies should.

Thanks for the suggestion and the PR. It makes sense yes.
We will also include the other dependencies as option.

Hi
Thanks for the package!
After I installed the package, it broke down, when I did:
from danlp.datasets import DDT
ddt = DDT()
ddt_ne = ddt.load_as_simple_ner(predefined_splits= True)

As far as I can see, this is due to the fact, 'pandas' and 'conllu' are both used in the code but NOT included as install requirements in setup.py.
I suggest, you include both.
I understand, why you do not include stuff like 'torch', 'flair' and so on to keep the package lightweight, but I think the above dependencies should.

Thanks for the suggestion and the PR. It makes sense yes.
We will also include the other dependencies as option.


Chore/notify-HO

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Please also include any acceptance criteria if you have any.
Preliminary work for hooking up this repository + beyond!

When pushes to master happen, triggers an action which sends the SHA to this workflow https://github.com/UKHomeOffice/digital-form-builder-1/actions?query=workflow%3A"Fork+sync+by+dispatch+(from+xgovformbuilder)"
The workflow on UKHO repo will then echo the sha.

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce
the testing if necessary.
Before PR's can be merged they will need to be tested by QA and approved where
applicable. To flag the change to QA assign @XGovFormBuilder/qa as one of the reviewers.

[x] sha is getting echo'd

Checklist:

[x] My changes do not introduce any new linting errors
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation and versioning
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have rebased onto master and there are no code conflicts
[x] I have checked deployments are working in all environments
[x] I have updated the architecture diagrams as per Contribute.md

reopening to get rid of some noise..

reopening to get rid of some noise..


Request to create a new repository for Ratify website

We finished the Ratify website framework development as described in #692 . In order to maintain the source code and content in a central place, I hope we can create a new repository under deislabs org for the Ratify website project. Then migrate the code and content from https://github.com/ShravaniAK/Ratify-Website to this new repository.

LGTM

Close this issue as the repository has been created https://github.com/deislabs/ratify-web


Introduction to fetch() needs update

https://developers.google.com/web/updates/2015/03/introduction-to-fetch says:

With the current fetch() implementation it's not possible to make requests for resources on a different origin from the window global scope.

but this is no longer current and needs updating.

Are we maintaining 2 year old blog posts @PaulKinlan?


File box

I'm submitting a...
[ ] Bug Fix
[ ] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[ ] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[ ] Tests for the changes have been added

Description
please describe the changes that you are making
for features, please describe how to use the new feature
please include a reference to an existing issue, if applicable
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Related issue: https://github.com/wechaty/wechaty/issues/1914

In wechaty-puppet-mock will use FileBox from 'file-box', so we should import FileBox from wechaty-puppet?

Yes. As discussed with @windmemory, we should import FileBox from wechaty-puppet in everywhere, including the wechaty-puppet-mock.

So this PR will be test green after wechaty-puppet-mock PR merged? Right?

No, it cannot.
Because the unit test needs to instantiate a puppet for testing purposes.

But now it can not pass the CI test, could you give me some advices for this case?

Cloud you please make sure you can pass the unit tests in your local environment by running npm test?
After that, I believe you can pass the CI.

It can't, but the log of failed test show that:
Error: Cannot find module 'file-box'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/Users/suchang/Desktop/PROJECT/Test/testPadplus/wechaty/node_modules/wechaty-puppet-mock/src/puppet-mock.ts:21:1)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/Users/suchang/Desktop/PROJECT/Test/testPadplus/wechaty/node_modules/wechaty-puppet-mock/src/index.ts:1:1)

So I think this error maybe due to the FileBox in wechaty-puppet-mock is from file-box?

Yes. So I'd like to suggest that you can keep the dependencies of the file-box for now. I will remove it by later.


Fixed resources header and added Sort & Filter

Description
Fixes #641

Added Sort and Filter feature for the Resources page for sorting and filtering the available Docs
Adjusted Sort and Filter according to the Dark Theme
Updated handleSearch function to be compatible with the Sort & Filter featured
Fixed the header in Resources page

Video
https://github.com/mdazfar2/HelpOps-Hub/assets/115717746/5d838341-5a38-46ac-b375-a2eb8863cbdd
Screenshots

@mdazfar2 Please review and merge this PR

@Asymtode712 fix this navbar as well when we open any specific topics-

@mdazfar2 Sure just a sec

@mdazfar2 Done!

@Asymtode712, do one more thing: change this to the top and write it this way so the user can understand the use of this icon. According to your convenience, try to add and write from your side.

@mdazfar2 Ok as you wish!!

@mdazfar2 Is this looking fine to you:
https://github.com/mdazfar2/HelpOps-Hub/assets/115717746/b4cd5c0a-13e4-450a-907b-f0037767986e

@Asymtode712 nice update it and also add hover on the icon of more info

@mdazfar2 Done!


[BUG] Celo Terminal does not update

Environment
Operating System: macOS 12.0.1
Celo Terminal Version: 1.11.5
Describe the bug
Trying to update Celo Terminal, clicking on the "v1.11.5 → v1.11.13" button at the bottom of the left menu, leads to nothing after 30mins+ of waiting. Refreshing the page with cmd+r removes the loading bar under the clicked button and suggests the app wasn't really updating.
To Reproduce

open app
Click on "v1.11.5 → v1.11.13" button at the bottom of the left menu
See the progress bar animation, wait
Nothing happens (app update expected?)

Expected behavior
App should update after clicking that button? How should we update otherwise? Thank you

When you click "update" button, it starts downloading the new version. Depending on your internet connection, it can take some time to do so.
It seems like update is working for others, so it might be some sort of a local issue with internet connection.
As for other ways to update, you can just download new version from either github or directly from celoterminal.com and install that by replacing the old version and it should all work fine.


fix: amend rollout correction email wording

TIS21-6650

Thanks @DorisWongNHS - nope, I was going to leave it 😁


Update composer.json

I'm not sure why there are strict qualifications on the minor version updates, guzzle is at 5.2 at the moment and it seems silly to prevent updates because of a minor version change.  Relax from the tilde range selector to the caret range selector to allow minor upgrades.

Your're right, and that's the intended behaviour. The caret is the best option here (although In case of php '~7.0' it shouldn't make a difference, as no patch level is given). Thanks!


fix(frontend): solve console warning

Resolves #609
What does this PR do?
Solve console warnings
How should this be tested?

Make run
Check there is no warning

Please @tetogomez @JeanVegaD take a look a some of these changes, I'm make the console solving recommendation. Most of the error are on the useEffect.

@leisterfrancisco take a look at the conflict

@leisterfrancisco take a look at the conflict

@JustinCast thanks, working on


Package Name On PyPI

As we get closer to completing our goals for Release version 1.0.0 (see #148), we need to come to a consensus as to what exactly the PyPI name for this library should be.
So far, on Discord, we have discussed the possibility of using a variety of names, including:
manimlib 1, 2
manim-com, manimc 1, 2, 3, 4
manimcm,manim-cm, manim_cm 1
2 (poll)
manim 1 (poll), 2
This ties in with #6 and #165.
@eulertour has filed a PEP 541 request here to try and get the name manim. It has been 4 weeks since and we have not heard back. PEP 541 gives the admins 6 weeks to contact the owner of the repo, so I suppose we should look back in about 2 weeks time.
In the event that we are not successful in getting the name manim, what other name would be ideal? It would be very easy to use the name manimlib for this repository, and rename Grant's package to manim-3b1b or something similar. As of now, we also have access to the name manimcm, so that too can be used with not much effort.

Did you mean to close this?

Yeah, it's a duplicate of https://github.com/ManimCommunity/manim/issues/163. At least, I think it is.


apple thread_info api addition

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 4b0b7fd1e657e576cec4d3a2dc3f14eb0f3cee7a has been approved by Amanieu

:hourglass: Testing commit 4b0b7fd1e657e576cec4d3a2dc3f14eb0f3cee7a with merge 13c8ceb1ed9077295edf68747bb282a6bee5f31c...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 13c8ceb1ed9077295edf68747bb282a6bee5f31c to master...


Pass custom environmental variables into Kong ingress controller

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
So, I need to pass extra env variable to my custom plugin.
In docker compose I just do this:
- DATABASE_HOST=myhost
- DATABASE_PASSWORD=123
- DATABASE_USER=root
- DATABASE_NAME=kong
- "KONG_NGINX_MAIN_ENV=DATABASE_HOST; env DATABASE_PASSWORD; env DATABASE_USER; env DATABASE_NAME"

This is working fine, however I don't know how to do the same with the Kong ingress controller, according to the chart value description:

Specify Kong configuration
This chart takes all entries defined under .env and transforms them into into KONG_*
environment variables for Kong containers.
Their names here should match the names used in https://github.com/Kong/kong/blob/master/kong.conf.default
See https://docs.konghq.com/latest/configuration also for additional details

  env:
    log_level: info
    my_custom_var: hello

So if I put my custom variable there it will be transformed into KONG_MY_CUSTOM_VAR
So how can I do it? I cannot find where the Kong chart exposes additional environmental variables for the proxy pod
Possible solutions
Just rename the variables this way:
- KONG_DATABASE_HOST=myhost
- KONG_DATABASE_PASSWORD=123
- "KONG_NGINX_MAIN_ENV=KONG_DATABASE_HOST; env KONG_DATABASE_PASSWORD"

Or override Kong deployment:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ingress-kong
  namespace: kong
spec:
  template:
    spec:
      containers:
      - name: proxy
        env:
        - name: DATABASE_HOST
          value: myhost

Is there a better way to do this?
Thanks

Using the .env settings will as you suggest result in the env var being prefixed with KONG_, this was a deliberate choice in the helper script:
https://github.com/Kong/charts/blob/main/charts/kong/templates/_helpers.tpl#L752
{{/*
    ====== USER-SET ENVIRONMENT VARIABLES ======
*/}}
{{- $userEnv := dict -}}
{{- range $key, $val := .Values.env }}
  {{- $upper := upper $key -}}
  {{- $var := printf "KONG_%s" $upper -}}
  {{- $_ := set $userEnv $var $val -}}
{{- end -}}

It would be possible however to add additional functionality to support your use case, let me know if you want to follow up on this as a feature request?
As for a workaround for this issue in the meantime unfortunately helm itself doesn't have a means to inject env vars into containers so your options are limited to post-processing workarounds (e.g. manually adding the ENV vars you want to your pods, or adding a initContainer to do it) or to clone this repo and locally modify the chart and deploy using your own modified version until such a time that there's a supported feature.
Let me know your thoughts, if that is helpful, and any other questions you may have?

So, is it not possible to pass env variables to a custom plugin via Helm chart? It seems a common use case, or maybe is there something I am missing?
In this case we could do something similar to the Bitnami chart: https://github.com/bitnami/charts/tree/master/bitnami/postgresql#postgresql-parameters
have the possibility to pass extra env variables to a pod via: extraEnv
extraEnv:
 MY_CUSTOM_VARIABLE: hello // either as map or array of objects

And then merge it together with the other variables, I see there is this function:
{{- $extraEnv := dict -}}
{{- range $key, $val := .Values.extraEnv }} // Maybe a check to see whether the value is actually being set
  ...
{{- end -}}

{{/*
      ====== MERGE AND RENDER ENV BLOCK ======
*/}}

{{- $completeEnv := mergeOverwrite $customEnv $userEnv -}}
{{- template "kong.renderEnv" $completeEnv -}}

{{- end -}}

Not sure how mergeOverwrite works, but that is the idea
What do you think?

Yeah unfortunately so far we just didn't have this.
Your suggestion looks good I talked it over with my fellow maintainers and we would accept that kind of patch. :+1:

Hello,
I have the same requirement.
@shaneutt if you guys are accepting PR, I will be glad to try and make something as we need to feature ASAP.
Please let me know, thanks

Hello,
I have the same requirement.
@shaneutt if you guys are accepting a PR, I will be glad to try and work something out as we need this feature.
Please let me know, thanks.

Yep sounds good thanks, I would recommend coordinating with @MatteoInfi prior to starting but then go for it.

I honestly do not have much time and I am not really expert with helm templating, if you can do it is better.
Thanks

Gotcha, I will see what I can do next week

Related to this https://github.com/Kong/charts/pull/568


Add libgcc

Fix missing dependency on libgcc
Description
Adds missing run-time dependency for Python cryptography package.
Related Issue
Fixes #321
Motivation and Context
Currently the cryptography package will bring in libgcc as a dependency when built, resulting in the following error on first run:
ImportError: Error loading shared library libgcc_s.so.1: No such file or directory

How Has This Been Tested?
$ docker build -t gimme-aws-creds .
...
$ docker run --rm -ti gimme-aws-creds
No gimme-aws-creds configuration file found, starting first-time configuration...
...

i.e. attempting to run succeeds instead of the traceback shown in #321.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

The CLA-signing page is broken but consider it signed by my opening this PR.

Works, thank you!

Hi, any chance this could be merged?

Worked fine on my system too. Please merge it.

I don't believe I have the perms anymore. @bwynsm should be able to help.


Merge master to live with latest release notes

Docs Build status updates of commit d200d1e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/how-to-guides/create-qsharp-project.md
:white_check_mark:Succeeded
View

articles/install-guide/pyinstall.md
:white_check_mark:Succeeded
View

articles/install-guide/qjupyter.md
:white_check_mark:Succeeded
View

articles/install-guide/update.md
:white_check_mark:Succeeded
View

articles/intro-to-katas.md
:white_check_mark:Succeeded
View

articles/machines/qc-trace-simulator/index.md
:white_check_mark:Succeeded
View

articles/quickstart.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[BEAM-11415] Setup and bugfixes for Go ValidatesRunner framework.

These issues were found and fixed while working on the ValidatesRunner framework, but are not directly related, so they're good candidates for a setup commit. The fixes:

Fixed an issue in graphx/xlang.go where the output PCollection of a composite containing an external transform wasn't being renamed properly, resulting in an error due to the composite containing a non-existent output. This was only caught when testing the Flink Runner, tests still passed with the Python Portable Runner.

Added a check to cross-compiling code to detect if the pipeline is being executed through go test, so an appropriate cross-compilation can be done for tests. This enables running pipelines from tests with portable runners.

Added a new helper function to ptest for convenience.

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

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

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

GitHub Actions Tests Status (on master branch)

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

R: @lostluck