Bug in async awaits in es5

TypeScript Version: 4.1.0-dev.20200917

Search Terms: is:issue is:open async label:bug change
Code
async function bar () {
  return {
    a: await Promise.resolve(1),
    b: await Promise.resolve(2),
    c: await Promise.resolve(3),
    d: await Promise.resolve(4),
    e: await Promise.resolve(5),
    f: await Promise.resolve(6),
    g: await Promise.resolve(7),
    h: await Promise.resolve(8),
    // works correctly if you comment the next line
    i: await Promise.resolve(9),
  }
}

bar().then(console.log)

tsconfig.json
{
  "compilerOptions": {
    "lib": ["DOM", "ES2015"]
  }
}

Expected behavior:
{ a: 1, b: 2, c: 3, d: 4, e: 5, f: 6, g: 7, h: 8, i: 9 }

Actual behavior:
{ a: 9, b: 9, c: 9, d: 9, e: 9, f: 9, g: 9, h: 9, i: 9 }

Playground Link:
https://www.typescriptlang.org/play?target=1#code/IYZwngdgxgBAZgV2gFwJYHsIwEbAE4wAUAlDAN4BQMMeApsgnlpddcAFwzADuwqyMAAp50AW1QhaAOjoh0AGwButQgEZiAGiqtsnHnwHCxE6bIXLCAJk3bqUPb35CR4yTNpylKgMw3WMABMHA2djNzMvQgAWP1ZaYKcjV1MPcxUAVljqOATDFxN3TwsANiyYAHNc0OTCtMIAdjKACyqkgoiLAA4y1Fb88NTIgE5YgF8KcYpcPBIpZCbaCEIoTE9peXRy4iA
Related Issues:
#40047

The cause seems to be that the generated code use the same value to init all properties (case 9):
// Excluded __awaiter and __generator functions
function bar() {
    return __awaiter(this, void 0, void 0, function () {
        var _a;
        return __generator(this, function (_b) {
            switch (_b.label) {
                case 0: return [4 /*yield*/, Promise.resolve(1)];
                case 1: return [4 /*yield*/, Promise.resolve(2)];
                case 2: return [4 /*yield*/, Promise.resolve(3)];
                case 3: return [4 /*yield*/, Promise.resolve(4)];
                case 4: return [4 /*yield*/, Promise.resolve(5)];
                case 5: return [4 /*yield*/, Promise.resolve(6)];
                case 6: return [4 /*yield*/, Promise.resolve(7)];
                case 7: return [4 /*yield*/, Promise.resolve(8)];
                case 8: return [4 /*yield*/, Promise.resolve(9)];
                case 9: return [2 /*return*/, (_a = {},
                        _a.a = _b.sent(),
                        _a.b = _b.sent(),
                        _a.c = _b.sent(),
                        _a.d = _b.sent(),
                        _a.e = _b.sent(),
                        _a.f = _b.sent(),
                        _a.g = _b.sent(),
                        _a.h = _b.sent(),
                        _a.i = _b.sent(),
                        _a)];
            }
        });
    });
}
bar().then(console.log);

At first I thought that this is problem with generator transformations, but looks like version where async changes to generator and await changed to yield provides correct assignments in each case.
Also original problem is not reproducible in 3.9.7.

The nightly have the same problem.
As a reference for the typescript team, in version 3.9.7 it generates:
// Excluded __awaiter and __generator functions
function bar() {
    return __awaiter(this, void 0, void 0, function () {
        var _a;
        return __generator(this, function (_b) {
            switch (_b.label) {
                case 0:
                    _a = {};
                    return [4 /*yield*/, Promise.resolve(1)];
                case 1:
                    _a.a = _b.sent();
                    return [4 /*yield*/, Promise.resolve(2)];
                case 2:
                    _a.b = _b.sent();
                    return [4 /*yield*/, Promise.resolve(3)];
                case 3:
                    _a.c = _b.sent();
                    return [4 /*yield*/, Promise.resolve(4)];
                case 4:
                    _a.d = _b.sent();
                    return [4 /*yield*/, Promise.resolve(5)];
                case 5:
                    _a.e = _b.sent();
                    return [4 /*yield*/, Promise.resolve(6)];
                case 6:
                    _a.f = _b.sent();
                    return [4 /*yield*/, Promise.resolve(7)];
                case 7:
                    _a.g = _b.sent();
                    return [4 /*yield*/, Promise.resolve(8)];
                case 8:
                    _a.h = _b.sent();
                    return [4 /*yield*/, Promise.resolve(9)];
                case 9: return [2 /*return*/, (_a.i = _b.sent(),
                        _a)];
            }
        });
    });
}
bar().then(console.log);

Interesting enough @andrewpg found that it doesn't depend on number of await's
but on number of object keys after first await.
Example

Caused by 8231519b853b0fe594cb70b8b89fb8e5c15c2918 in #38880
/cc @elibarzilay @rbuckton

Thanks for the investigation, everyone! 🌟

Would it be possible to backport a fix for this to 4.0.x? We unfortunately had to revert our 4.0.x upgrade because this issue was causing our apps to crash, and we'd love to upgrade to 4.0.x before November :)

Yes, I think we can packport the eventual fix to TypeScript 4.0.4. @elibarzilay do you think you'd be able to prioritize this issue?

Seems like @elibarzilay is having hardware issues. @rbuckton can you take a look at this?

I'm back, kind of.  Trying to find it now.

If folks can try out the next nightly version of TypeScript to validate that the fix works for them, we'd appreciate that a toN!

@DanielRosenwasser I tried the nightly out in our repo and it seems to have fixed the issue!

@DanielRosenwasser sorry to bother, but what's the timeline for 4.0.4? We're super eager to upgrade to 4.0.x :)


Dotnet watch doesn't restart on OSX because of a corefx issue

Caused by https://github.com/dotnet/corefx/issues/7680
If it doesn't get fixed on their side, we need to workaround it.
cc @glennc

This is a tracking issue.
If it is fixed in corefx for RC2 then we can close this. If not then we will need to workaround the issue for RC2 and then back out the changes for the release after RC2.

@victorhurdugaci Please follow-up the rel check-in & our CoreFX consumption in the CI

Fixed by the latest CoreFx


fix err of go build

fix the err when build
go build
# github.com/mesh-operator/pkg/adapter/zookeeper
../../pkg/adapter/zookeeper/registry_client.go:125:22: undefined: constant

we already merge dev to master, thanks for you contribution

you have merged dev to master, and the commit also merged to master. this make the err:
# github.com/mesh-operator/pkg/adapter/zookeeper
../../pkg/adapter/zookeeper/registry_client.go:12:2: constant redeclared as imported package name
	previous declaration at ../../pkg/adapter/zookeeper/registry_client.go:5:2

you have merged dev to master, and the commit also merged to master. this make the err:
# github.com/mesh-operator/pkg/adapter/zookeeper
../../pkg/adapter/zookeeper/registry_client.go:12:2: constant redeclared as imported package name
	previous declaration at ../../pkg/adapter/zookeeper/registry_client.go:5:2

thx, already fix package repeat problem.


Update AI feature flag scope

This PR changes the scope of the AI feature flag from user to system, meaning it can't be set/overwritten via localStorage, URL or the YAML file.
Looking forward, the feature flags store should probably be broken up into three components: a config store that is project/organization specific and depends on data only available via the API, a preferences store for things that can be toggled on and off and are not intended to be hidden, and a feature flags store for things disabled by default and enabled manually. Also, there are certain things, like adminServer that don't need to be reactive or controlled during runtime that should be constants determined by environment variables.

Can we set the AI flag to default to true?

@ericpgreen2 Added.


Dyn load

[x] No static strings in the client binary
[x] Request translations using server fn
[x] Ship used translations with the HTML
[ ] Fix "interpolate_display" feature
[ ] Make it work with CSR

This is mostly working, two features are not compatible at the moment: "csr" and "interpolate_display"

Merging this, support for CSR will come later.


Supported internal allocator in {session,statement}.Execute for decrease memory usage

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Base: 59.78% // Head: 49.44% // Decreases project coverage by -10.33% :warning:

Coverage data is based on head (ebd0bec) compared to base (c253bde).
Patch coverage: 84.15% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #478       +/-   ##
===========================================
- Coverage   59.78%   49.44%   -10.34%
===========================================
  Files         242      236        -6
  Lines       26032    25667      -365
===========================================
- Hits        15562    12691     -2871
- Misses       9486    11990     +2504
- Partials      984      986        +2

Flag
Coverage Δ

1.16.x
48.42% <76.47%> (-11.13%)
:arrow_down:

1.18.x
36.16% <82.79%> (-23.44%)
:arrow_down:

1.19.x
48.24% <82.79%> (-11.40%)
:arrow_down:

connection
10.36% <0.00%> (-0.03%)
:arrow_down:

database_sql
?

discovery
8.65% <0.00%> (+0.01%)
:arrow_up:

e2e
49.44% <84.15%> (-2.68%)
:arrow_down:

integration
?

macOS-latest
?

ratelimiter
10.04% <0.00%> (-0.03%)
:arrow_down:

scripting
10.99% <8.91%> (+0.04%)
:arrow_up:

table
32.81% <84.15%> (-0.21%)
:arrow_down:

topic
27.06% <54.45%> (-0.03%)
:arrow_down:

ubuntu-latest
49.44% <84.15%> (-10.29%)
:arrow_down:

unit
?

windows-latest
?

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

Impacted Files
Coverage Δ

internal/table/keep_in_cache.go
0.00% <0.00%> (-100.00%)
:arrow_down:

table/options/options.go
13.97% <14.28%> (-42.02%)
:arrow_down:

internal/table/transaction.go
66.91% <46.66%> (-9.43%)
:arrow_down:

internal/table/data_query.go
55.55% <55.55%> (-5.99%)
:arrow_down:

internal/table/statement.go
77.27% <91.30%> (+7.57%)
:arrow_up:

internal/table/session.go
67.78% <93.18%> (-11.04%)
:arrow_down:

internal/allocator/allocator.go
64.00% <100.00%> (+6.85%)
:arrow_up:

internal/allocator/allocator_go1.18.go
71.95% <100.00%> (+4.41%)
:arrow_up:

table/table.go
61.49% <100.00%> (+0.73%)
:arrow_up:

sugar/dsn.go
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 98 more

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

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


model.all() can't return saved document  in the demo code

thx for you lib, follow querstion occurs when i get start
version info
    "soukai": "^0.3.0",
    "soukai-solid": "^0.3.0",

description
in the demo code which doc gives,save method works fine, but all method can't return the saved document while network already get the turtle data
import Soukai from "soukai";
import { SolidModel, SolidEngine } from "soukai-solid";
import SolidAuthClient from "solid-auth-client";

const accountUrl = "https://myaccount.inrupt.net/news/";
class News extends SolidModel {}
Soukai.loadModels({ News });
Soukai.useEngine(new SolidEngine(SolidAuthClient.fetch.bind(SolidAuthClient)));
News.at(accountUrl);

const saveData = async () => {
  // this works
  await News.create({
    title: "latest",
    content: "content news",
    author: "leeon",
  });
};

const getData = async () => {
  // network get the data
  // but this method get []
  const list = await News.at(accountUrl).all();
};

Hi there,
I see that you've closed the issue so maybe your problem is solved. But in case it is helpful, something to improve from your code is that you're not including RDF definitions in the models. I think it should work anyways, but I wouldn't recommend using such a model in a real application.
Maybe the problem was that a resource was created but given the lack of RDF definitions it doesn't have a proper shape and that causes problems when reading the model.

thank you so much for you reply,
i solve the problem after realize lacking of RDF definitions.
soukai-solid is the tool what i looking for, thank you

You're welcome, let me know how it goes :).
I've been working on some changes that I want to release soon (no time estimations though). They change some important things like the way resources are stored in the documents using a hash reference and using relative urls instead of absolute. Take a look at the dev branch or do npm install soukai@next soukai-solid@next if you want to try these out, but keep in mind it's a work in progress!

Thx for your reply.
Here is my code
import Soukai from "soukai";
import { SolidModel, SolidEngine } from "soukai-solid";
import SolidAuthClient from "solid-auth-client";
const containerUrl = "https://myaccount.inrupt.net/news/";

class Report extends SolidModel {
  public static rdfContexts = {
    schema: "https://schema.org/",
  };
  public static rdfsClasses = ["schema:Report"];
  public static fields = {
    name: FieldType.String,
    author: FieldType.String,
  };
}
Soukai.loadModels({ Report });
Soukai.useEngine(new SolidEngine(SolidAuthClient.fetch.bind(SolidAuthClient)));
Report.at(containerUrl);

const saveData = async () => {
  // save document to containerUrl works fine
  await Report.create({
    name: "latest",
    author: "leeon",
  });
};

const getData = async () => {
  // return all the document in the containerUrl
  const list = await Report.at(containerUrl).all();
};

But a new question is how to deal(update,delete,get detail ) with the document directly. Following code is my current solution
const fn = async () => {
  // get all document from the container Url
  const list = await Report.at(containerUrl).all();
    for (const iterator of list) {
      if (condition is true) {
        await iterator.delete();
        // or
        await iterator.update();
      }
    }
};

It will be great if the document provides more example

I think your code should work for the most part, here's a couple of notes:

The author field should be a FieldType.Key. If you look at the schema.org documentation of the property it declares it as a reference to another resource, not as text. So it should be a url. It's fine to continue like this if you're just learning or tinkering with it, but for a real application this is important.
The fields author and name are inferred to be schema:author and schema:name respectively, which is ok in this case. But keep it in mind in case you want to use a different name that doesn't match the schema.org documentation. You can use rdfProperty if you want to be explicit.
The delete and update are ok, although the update will only change the updatedAt field because you're not changing anything in this example.
I also assume this is an example, for a real application you wouldn't hard-code the url of the container. You should get it from the Type Index Registry or ask the user.

If you want to see some example models, take a look at these places (I'll add this to the documentation :D):

Test models in this project (you can look at test files to see how they are used).
Models in Media Kraken.
Models in Solid Focus. I haven't worked on this one for a while, so there are some things I'd do differently today. But I still use it every day and it works :).

Very  helpful suggestions, thank a lot.
Sure, it's just a demo example to show my solution. I have found  Media Kraken and Solid Focus from solid app list before,and read their source code now.
I wonder is it possible to get data from source url directly by soukai-solid other than through the container url ?
For example, I can use Model.all() get all documents contain in https:demo.solid.net/movies/.
Is it possible  to use soukai-solid directly get  movie data from https:demo.solid.net/movies/12-Angry-Men ?

I wonder is it possible to get data from source url directly by soukai-solid other than through the container url ?
For example, I can use Model.all() get all documents contain in https:demo.solid.net/movies/.
Is it possible to use soukai-solid directly get movie data from https:demo.solid.net/movies/12-Angry-Men ?

It would technically be possible, but the codebase is not prepared for that. Model for example is an abstract class, so you'd need to extend the class anyways. I think for that use-case, where you're working with data and you don't know the shape, it's better to use something like ldflex.
I'm not sure because the apps I've been working on always have a known data structure, so I haven't found the need to do that kind of generalisation.

Get that, thank you so much Orz


SQLite

It does not work when running the published app:

https://github.com/WiseLibs/better-sqlite3 seems to do some work to support Electron


Clearer comment on sweden.rq

Tiny PR to clarify the nature of one type fetched by Sweden's query. I might add small updates in other PRs as I'm cleaning a lot of Swedish gov agency content on Wikidata right now.

Thank you @PierreMesure 💯


Parentage page

Parentage page (tools/parentage/) now links to a page with code prefix descriptions, and the data submission template and bulk data file are linked.

I have reviewed and it looks good. Thank you for your work.

@jd-campbell - thanks for the review - but I don't think the branch was merged to main. Reopening.

Pinging @jd-campbell or @maxglycine - I'd like to finish this PR and merge to main if it is at an acceptable stage. We can make further changes later, but I think it's good to close issues and keep pushing ahead when possible.

I believe @jd-campbell gave you the ok last week

The thing is: a comment on the PR isn't sufficient. Review and approval is needed.  One way is to click "Files changed", then the green "Review changes" button, then the "Approve" radio button if appropriate.


Issue with k8s.io/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/

systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: activating (auto-restart) (Result: exit-code) since Wed 2020-07-29 08:46:32 EDT; 919ms ago
Docs: https://kubernetes.io/docs/
Process: 9982 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255)
Main PID: 9982 (code=exited, status=255)
Jul 29 08:46:32 node1 systemd[1]: Unit kubelet.service entered failed state.
Jul 29 08:46:32 node1 systemd[1]: kubelet.service failed.

please try reporting this on the support channels:
https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
note that the kubelet service will fail until you give it the file specified by --config (or call kubeadm init/join).
/close
/triage support
/sig cluster-lifecycle


Open rear camera in mobile devices .

can there be option to select the camera we want to select in mobile devices ?

Hi @s9k96 did you solve this?

Hi there!
Check out this document on MDN, it describes how to set the rear camera using a constraint:
https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia
You can pass this to WebcamJS along with the width and height:
Webcam.set( 'constraints', {
	width: 1280,
	height: 720,
	facingMode: { exact: "environment" }
} );

More about constraints in the docs here:
https://github.com/jhuckaby/webcamjs/blob/master/DOCS.md#custom-user-media-constraints-advanced
Note that this does not work with Adobe Flash fallback -- it only works on browsers that support native HTML5 getUserMedia.
- Joe


CM_Mail: Debug appending key/value to array

@njam please review

Looks ok, but...
You're dropping ability to pass multiple headers with the same. According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2 it is possible to send headers with the same name as single with values separated by commas. Should we support this? I vote for no.
The only misleading thing now name of the method. We should probably rename it to "setCustomHeader" as it will actually replace previoous one (not add).

Agree, I would keep the ability to set multiple headers with the same key.

I gather from this:

@tomaszdurka you are ok with the current solution (unique header name) but want a renaming of the setter
@njam you agree but would like to keep setting multiple headers with the same name

this is an interest conflict..
I vote for multiple headers with the same name, which is standard.. in order to do that, I'd refactor to encaspulate every single k/v pair into a single array (and therefore have an array of arrays). I need to refactor the "explosion" into single headers - easy :v:

@tomaszdurka @njam who wants to review?

Philipp and me are looking into this now

I would prefer to not keep array-like types with 2 values. Rather:
if (!isset($this->_customHeaders[$label])) {
  $this->_customHeaders[$label] = array();
}
$this->_customHeaders[$label][] = $value;

@ppp0 I just meant that if we agree on single-header then the name sould be set* as it's replaces previous value.

@tomaszdurka @njam I value your comment aka please review

@mariansollmann fancy reviewing please?

looks good

Why is it now called setCustomHeader(), isn't it adding a header (i.e. we can have twice a header with the same name)?

It is overwriting the header's key, though

...but only if it's the same, so not really overwriting :)


rename the contact: istio-core -> istio-steering

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

none

/assign @geeknoid


[WFCORE-532] Cache the Handle for the PathManager Callback registration so it can be removed on stopping the service.

Core - Full Integration Build 420 is now running using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e

Linux Build 1146 is now running using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e

Windows Build 842 is now running using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e

Windows Build 842 outcome was SUCCESS using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e
Summary: Tests passed: 2986, ignored: 95 Build time: 0:18:00

Linux Build 1146 outcome was SUCCESS using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e
Summary: Tests passed: 2986, ignored: 95 Build time: 0:18:22

Core - Full Integration Build 420 outcome was SUCCESS using a merge of 7a4ebbacd5b3a0effb0d86c6d7386aeb108f3b0e
Summary: Tests passed: 2856, ignored: 378 Build time: 0:48:53


Feature/role based access controll 3

resolved #14

Dynamic roles
Role controller

I have removed roles parameter in restrict to middleware. The middleware now validates user using actions.
there will be some ACTIONS related to superAdmin
such as:
const Actions= {
REMOVE_ADMIN:"REMOVE_ADMIN",
MANAGE_ROLES:"MANAGE_ROLES"
}

now the routes for super admin will use this ACTIONS. User with the required authorities can access those routes.
please review my changes.
@bellaabdelouahab

we will definitely need some code testing for this

Here comes the boring part😁. btw, can you provide all the Actions?

we will definitely need some code testing for this

yeah but testing is so boring 😁,
The createAdminUser function is not getting authorities and restrictions.
can we keep it in the authorization dir?.

we will definitely need some code testing for this

yeah but testing is so boring 😁, The createAdminUser function is not getting authorities and restrictions. can we keep it in the authorization dir?.

i dint understand you

anyway we will keep you updated on testing @muttaqin1

const createAdminUser = async () => {
  try {
    const user = await User.findOne({ email: ADMIN_EMAIL });
    if (!user) {
      await User.create({
        name: 'Admin',
        email: ADMIN_EMAIL,
        password: ADMIN_PASSWORD,
        roles: ['SUPER_ADMIN'],
      });
      Logger.info('Admin user created successfully');
    }
  } catch (err) {
    Logger.error(err);
  }
};

This function is only getting the role but  not getting the authorities and restrictions.
const createAdminUser = async () => {
  try {
    const user = await User.findOne({ email: ADMIN_EMAIL });
    if (!user) {
      await User.create({
        name: 'Admin',
        email: ADMIN_EMAIL,
        password: ADMIN_PASSWORD,
        roles: ['SUPER_ADMIN'],
//authorities: [], missing!
//restrictions:[] missing!
      });
      Logger.info('Admin user created successfully');
    }
  } catch (err) {
    Logger.error(err);
  }
};


*kgo.Record pooling support

This PR resolves https://github.com/twmb/franz-go/issues/823 by allowing to reuse consumed records via kgo.(*Record).Reuse method.

so , i don't understand - records already get from pool or this is not planned?


Fixes #792.

Fixes #792. Originally, when on iOS theme, an IconButton with a null Icon and an action that popped the current context was placed in the location of a normal back button even in the main conversation list. This caused clicking in that area to pop the main context and exit to a black screen.
I have changed the logic to not include an IconButton in this case and instead include a new Container() with no action when tapped.
I know there are a lot of format changes so I'll point out that the lines with the actual code changes are 421-435 (originally 441-456).

Next time, mind letting me know the major lines that changed? Hard to decipher with all the linting changes lol. Approved nontheless

Included the line numbers in the last line of the pr comment lol. I'll put them up at the beginning next time.

Next time, mind letting me know the major lines that changed? Hard to decipher with all the linting changes lol. Approved nontheless

Included the line numbers in the last line of the pr comment lol. I'll put them up at the beginning next time.

That's my fault. I was doing 10 things at once and didn't read correctly


Autolinking doesn't work

Hello again,
after reading the logs, I realised that the plugin doesn't even load. Silly me just assumed it loaded because the site creation worked fine. The plugin shows in the preferences, but is greyed out and "There was a problem loading this plugin" shows as description, nothing else.
Info I didn't provide on reddit:

I'm running ArchLinux
the plugin file is located in ~/.local/share/zim/plugins, no subfolder

Log from starting Zim the normal way
zim.log
Log from starting Zim through the terminal with debug option
zim_debug_terminal_output.txt

Oh, I didn't even think about if the folder is still the same on other distros (I use Ubuntu). If you click "open plugins folder" (on the plugins screen), does it still take you to that folder or somewhere else?

Yes, it takes me to that folder. I have another plugin there (zim-clip) that works. The only difference is that zim-clip is in a subfolder.

Ok. It might be due to a syntax error, then? If you use VS Code it should tell you if something is wrong. If not, the only other thing I can think of is a dependency error (which is odd because it shouldn't have any that are not included with zim itself) Maybe send me your modified version so I can take a look at it and test it on mine.

autolink.zip
Here is my Version.
As far as I can tell, there is no syntax error. I use Kate, which has syntax highlighting, but I tried with VS Code and got no error.
One thing I discovered: when I try to open other plugin files from the file manager, I get the option to run them. This does not happen with autolink.py

One thing I discovered: when I try to open other plugin files from the file manager, I get the option to run them. This does not happen with autolink.py
well that is especially strange. VS Code did flag a few errors, but they were all caused by some sort of weird tab issue. So far it won't even appear in the list, but I'll keep fiddling around with it and see if I can get it to work.

Apparently I forgot to actually put it in the folder, smh. Once I put it in there it showed up right away, actually. Here's your version, with strange tabs removed, and some other things such as closing the files after it's done with them and some debug messages should you have issues again.
autolink.zip
If you still have issues after this, I think it's gotta be a dependency problem.

It works! Thanks a lot, this makes writing so much easier.

 It sure does :)


Agent returns an error while spark HS installing

Description
Ambari-agent returns an error while Spark History Server deploying. This error related to output decoding. Traceback:
stderr:
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/stacks/BGTP/1.0/services/SPARK/package/scripts/spark_client.py", line 55, in <module>
    SparkClient().execute()
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 352, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/stacks/BGTP/1.0/services/SPARK/package/scripts/spark_client.py", line 34, in install
    self.install_packages(env)
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 853, in install_packages
    retry_count=agent_stack_retry_count)
  File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in __init__
    self.env.run()
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py", line 30, in action_install
    self._pkg_manager.install_package(package_name, self.__create_context())
  File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line 35, in wrapper
    return function_to_decorate(self, name, *args[2:], **kwargs)
  File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line 282, in install_package
    shell.repository_manager_executor(cmd, self.properties, context, env=self.properties.install_cmd_env)
  File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 744, in repository_manager_executor
    should_stop_retries = __handle_retries(cmd, repo_properties, context, call_result, is_first_time, is_last_time)
  File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 689, in __handle_retries
    __update_repo_metadata_after_bad_try(cmd, context, repo_properties, call_result.code, call_result.out)
  File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 715, in __update_repo_metadata_after_bad_try
    _logger.info("Execution of '%s' failed and returned %d. %s" % (string_cmd_from_args_list(cmd), code, out))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1875: ordinal not in range(128)

Tasks

[ ] Fix ambari-agent bug
[ ] Upgrade version into <IP_ADDRESS>.0

Python's default encoding is ASCII which throws UnicodeDecodeError when trying to decode a stream/array of bytes to Unicode. Setting the default encoding to UTF-8 will fix the conversion from bytes to UTF-8 encoded string.
It can be done in two ways:
First - Set environment variable
In file /etc/environment set next env variables:
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8

And apply changes using source /etc/environment
In another way it can be configured in file /etc/ambari-agent/conf/ambari-agent.ini by adding next strings:
[environment]
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8

Second - Set another encoding in py file
Add next code in py file:
reload(sys)
sys.setdefaultencoding('utf8')

To fix this bug was used first method. Issue closed without any merge requests.


MT5 Connect

Hello,
I am unable to connect to MT5 Client using the following code:
MtApi5Client mtClient = new MtApi5Client();
mtClient.BeginConnect(8228);
Is there something missing? Is there any way to get connection error message?
Using the ApiService I am able to connect and get quotes:
MTApiService.MtClient client = new MTApiService.MtClient(8228);
client.Connect();
List<MTApiService.MtQuote> ff = client.GetQuotes();
Thank you.

Do you have the same problems with the Test Client? (MtApi5TestClient.exe)

same question here
@KptKuck have yuo solved it?

MtApi5Client has async function BeginConnect.
For correct using the API you need to subscribe on event ConnectionStateChanged to get state of connection.
When you receive state Mt5ConnectionState.Connected then you can use other functions like GetQuotes.

Can you solve that? I'm having the same problem


enable ni filter entry and filter meta

This PR enables to define a NI filter in addition to the IN filter.
In addition the filter meta will be added to the filter card underneath the title.
        {
            "title": "Retailer",
            "field": "retailer",
            "filter": {
                "meta": "Exclude from layer filter",
                "type": "ni",
                "ni": [
                    "ALDI",
                    "Lidl",
                    "Tesco"
                ]
            }
        },

Good spot. I rename input to content and make sure that content is always an array prior to the unshift.
I also merged the main into this branch.


Revisit decision to inherit system isolate property when spawning isolates

To resolve issues related to generating macro code with --pause-isolates-on-start provided, it was decided that isolates spawned by the kernel service to perform the macro code generation should inherit the system isolate property from the kernel service isolate. This prevents the macro generation isolate from pausing on start or exit, resolving https://github.com/dart-lang/sdk/issues/54729.
However, inheriting the system isolate property may not be the right thing to do in all situations, so we should revisit this decision once the macro generation debugging story is better defined or if it impacts debugging for user programs once the dartdev CLI isolate starts running from an AOT snapshot. This should be revisited to determine if:

Inheriting the system isolate property is actually what we want to do in general
Isolate.spawn* APIs should instead include a parameter to specify an isolate as a system isolate

Closing this issue for now as it turns out there's situations where we do want isolates spawned from system isolates to not be system isolates, so this CL won't be landing.

I think it is worth considering if we want to simplify our life and split kernel-service into a separate process. Could we get to the point where we only run vm-service in the same process and nothing else?

That'd definitely be ideal, and I think that's something @a-siva wants to explore.

As a temporary fix, we're going to inherit the system isolate flag on isolate spawn except for the case where the main isolate is a system isolate due to the --mark-main-isolate-as-system-isolate flag is passed to the standalone VM.
This flag is only used in the context of test runners that don't want the main isolate to be debuggable as they're not running user code. However, the test runners do spawn isolates running user code that should be debuggable from the main isolate, so inheriting the system isolate property isn't the right thing to do.

The change https://github.com/dart-lang/sdk/commit/d9797db9ea6349afb34d369dd7c43d1c8b6e5376 broke "Collect Report" button on the analysis server diagnostic page when analysis server is spawned via dartdev (dart language-server). Analyzer isolate are now being treated as system isolates which breaks code like this: https://github.com/dart-lang/sdk/blob/c9a8bbd8d6024e419b5e5f26b5131285eb19cc93/pkg/analysis_server/lib/src/status/diagnostics.dart#L529-L530.
I am somewhat puzzled as to why we did not simply change behavior of isolates spawned from kernel-service rather the other way around? I am thinking about changing condition to:
// Treat children isolates spawned by kernel-service and vm-service as
// system isolates as well.
const bool is_parent_vm_service =
        strcmp(parent_isolate_->name(), "vm-service") == 0;
const bool is_parent_kernel_service =
        strcmp(parent_isolate_->name(), "kernel-service") == 0;
api_flags.is_system_isolate =
        api_flags.is_system_isolate && (is_parent_kernel_service || is_parent_vm_service);

Any opinions on this @bkonyi ?

Since embedders can mark isolates as system isolates the idea was that isolates spawned by system isolates should inherit this property to avoid situations where system isolates spawn workers that unexpectedly show up in DevTools. This was the most generic solution, but realistically the only system isolates are the VM service, kernel service, DartDev, and the main isolate when --mark-main-isolate-as-system-isolate is provided.
Your proposal LGTM. If it ends up causing unexpected behavior in some other embedder in the future, we can always modify our API to allow for embedders to specify the default inheritance behavior.

On second thought, shouldn't the analysis server also collect diagnostic information related to the system isolates? That's probably a better fix that won't make a non-debuggable isolate visible to DevTools and won't allow for flags like --pause-isolates-on-{start,exit} to actually pause the spawned isolate.
I was also talking with @a-siva about this earlier and he brought up a good point about this logic in the analysis server not working in product builds due to the lack of a VM service, which is how DartDev is going to be run in the near future.

Anyway I recognize that some of these points are moot in AOT world, but I am just trying to highlight that there is nothing VM internal about LSP server spawned by IDE.

Sure, they aren't VM internal, but they're internal to the Dart SDK and the implementation details aren't relevant for the vast majority of our users. It's still possible to view and profile these isolates through DevTools with VM Developer Mode enabled or Observatory.

This is orthogonal. We have a stable version to fix and we can't wait for AOT switch to happen (nor can we backmerge that into stable).

In that case, the simplest fix is to collect isolate statistics for all isolates in the process, including system isolates, which will also give a fuller picture into what's going on in the process than only looking at non-system isolates will.

I was catching up on the discussion here, I think initially the service isolate and kernel isolate were the only ones marked as system isolate (internal to the VM functionality).
I believe the package:test bootstrapping logic exposed a bug when started with the flag --pause-isolates-on-{start,exit} and similarly the dartdev isolate exposed a race condition again with the --pause-isolates-on-{start,exit} between the service isolate starting up and the dartdev isolate.
I am wondering if marking these isolates as system isolates to fix the above bug is not the right fix, maybe we need a mechanism for the isolate to declare itself as to whether it wants to participate in vm-service functionality ?

I am wondering if marking these isolates as system isolates to fix the above bug is not the right fix, maybe we need a mechanism for the isolate to declare itself as to whether it wants to participate in vm-service functionality ?

That's kind of what the concept of "system isolates" was meant for... :-)

I am wondering if marking these isolates as system isolates to fix the above bug is not the right fix, maybe we need a mechanism for the isolate to declare itself as to whether it wants to participate in vm-service functionality ?

That's kind of what the concept of "system isolates" was meant for... :-)

Then why do isolates inherit that property from the parent ?

Then why do isolates inherit that property from the parent ?

The only reason the property is inherited at all right now was to support the kernel isolate spawning isolates for macro execution. The macro isolates were pausing on start in scenarios where --pause-isolates-on-start was provided, so we decided to make isolates inherit the system isolate property from their parent isolate under the assumption that isolates spawned by system isolates should also likely be system isolates.

Then why do isolates inherit that property from the parent ?

The only reason the property is inherited at all right now was to support the kernel isolate spawning isolates for macro execution. The macro isolates were pausing on start in scenarios where --pause-isolates-on-start was provided, so we decided to make isolates inherit the system isolate property from their parent isolate under the assumption that isolates spawned by system isolates should also likely be system isolates.

This comes back to my question about whether we need a mechanism for an isolate to declare itself as not wanting to participate in vm-service functionality instead of making such assumptions ?

This comes back to my question about whether we need a mechanism for an isolate to declare itself as not wanting to participate in vm-service functionality instead of making such assumptions ?

Sure, providing a way to specify whether or not a spawned isolate is a system isolate would allow for this.


[Bug] - Fixed Broken 404 Links

Signed-off-by: Adithya Krishna<EMAIL_ADDRESS>What I did

Fixed many 404 links across the website.
Fixes #408

Notes to Reviewers
In this page, https://ux.redhat.com/about/how-we-build/ the patternkit and patternbuilder redirects to a 404 page having links of RH Internal network I guess, could you please let me know if it was intentional, or should it be updated to https://www.drupal.org/project/patternkit and https://www.drupal.org/project/patternbuilder respectively

No problem :)
Thanks so much, @bennypowers for approving and merging this 🚀


Send notification when room is under attack

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

5
0
0
5

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

semperrabbit
✔

dragoonreas
✔

ViezeVingertjes
✔

ButAds
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


Engineering/Atmos gameplay improvements.

This will be a master list of all potential engineering/atmos improvements.
If something is not listed please comment and it could be added.
If there is no issue, it hasn't been made yet.
TO-DO:

[ ] Devices

[ ]  #15708 - RCD Rework & Improvements
[ ]  #4203 - Atmos Devices

[ ] Engines

[ ] Tesla
[ ] SuperMatter Crystal & events (crystal cascade event/solar flare event)

[ ] Atmos

[ ] Rooms should only fill with distro if at unsafe levels (flood prevention)
[ ] #20293 - spacing is too slow

[ ] Refactoring

[ ] #13068

[ ] Bugs

[ ] #20313 - TEG bugs
[ ] #20788 - Meta mapping atmos issues
[ ] #10333 Stacking pipes/devices (check for anchored pipes)
[ ] #20365
[ ] #20548
[ ] #15653
[ ] #10163 (needs replicating)
[ ] #20548

[ ] Requests

[ ] #20953 - Radiation Collector improvements
[ ] #20952 - Admin alerts
[ ] Standard/Guidelines for how atmos devices should be mapped
[ ] Pipe layers (1-5 or 1-3)
[ ] #20549

super matter? crystal cascade event?

super matter? crystal cascade event?

SM was already on the list but I added your event

Here's a problem with current spacing mechanics #20293
If gas miners are ever to be removed, it will be only amplified. Even with gas miners present, a few such vents are able to waste more air than is being produced.
A more generic problem with mapping atmospherics: #20788
There should be standards/guidelines for how atmospheric devices should be mapped to prevent such situations.

Added

Pipe stacking needs to be fixed still, I think

Pipe stacking needs to be fixed still, I think

I'm not familiar with pipe stacking. Is it just stacking (anchored) pipes on top of each other?
Adding layers and checking for anchored pipes should fixed that.

theres a pr for that open

theres a pr for that open

Which one?

#19665 :trollface:

Yup that's what I was thinking of


Docfix: Update incident creation example

Example was failing because no sender was specified, update to show how to set a default sender.
Update example showing how to add details to the page
Strip trailing whitespace

Closes #78
Signed-off-by: Joe Block<EMAIL_ADDRESS>

Done


Creation of about and contact pages

Created about and contact pages , with the given information under JWOC 2024, Please verify this

Can you make it so the about and the contact pages have their own separate pages, instead of them all being in the home page. @thesri

Accha okay can I just get some more time for this? I thought it should be on the landing page only .

Yes you finish it by tomorrow. I can increase the difficulty tag based on the work done.

Okay sure thanks

created about and contact pages seperately under JWOC 2024  please verify.

Great Job!! @thesri Merged!!

@thesri This is really great!! Increased the difficulty to medium.

@thesri This is really great!! Increased the difficulty to medium.

Thankyou


Square Android Popup in version 3.0

I have been using the https://github.com/01org/appframework/tree/3.0beta version of the framework. All works well except that when I test on an android device I get default square android themed popup , instead of the none os theme i see on the desktop. I went as far as comment out the android specific popup css in the af.ui.css file but I still see the os themed popup. is there a way to fix this? I know that this is a beta but all seem to work well except this.
in my code I have $.afui.useOSThemes=false; but this seem to not make a difference.

Can you put a demo up and let me know the device?  I'll look into it ASAP

Here goes: http://deleovon.com/fix/ . If you test on chrome it works at it should. it you test in android browser is shows

I just tested your page and I see the correct popup.  Which "Android browser" were you testing in?

Your problem is you are setting $.afui.useOSThemes=false; in the $.afui.ready function.  That gets set AFTER $.afui has launched.  Move it before and it will work.

thanks. its now fixed.


Rename default name to crosslingo

To achieve it I should rename the module "app"

Implemented in scope of #111


Stopped working in Obsidian Mobile

Before Submitting: Double-check that you are running the latest version of the plugin. The bug might have already been fixed 😄

Describe the bug
The plugin used to work great on Obsidian Mobile, but in one of the latest versions the right pane was removed, there is now only a left one (showing file explorer & search by default).
The calendar view seems to always bind itself to the right, and is thus not accessible on Obsidian Mobile anymore, unless I'm missing something.
Steps to reproduce

Open Obsidian Mobile with the calendar plugin turned on.
Open the left pane -- it is not there.
I believe there's no way to open the right pane anymore.

Expected behavior
When on mobile, of when there is no right pane (if it's possible to detect it), bind to the left pane instead of the left one.
Environment (please specify)
OS
Android
Obsidian Version (e.g. v0.10.6)
Obsidian Mobile 1.3.0
Theme (if applicable):
If the bug is visual, please provide the name of the Community Theme you're using.

have the same problem

I actually discovered that a right swap from the middle of the document opens the right pane.
I'd still rather have the option to put it in the left pane, but at least it is usable.

I am having the same issue...even when I right swipe and get the right pane there, no calendar visible.

I don't have an Android device on hand but you might be interested in checking a similar issue someone had on iPadOs. The issue can most likely be resolved in the same way, see this comment for help.
If the aforementioned helps then this issue can be closed as it's not a bug @esm7 🙂

Thanks, that works for me.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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


Certificate date issue on main site

Good day.
The certificate on the site does not return valid.
FF: Firefox Developer Edition detected an issue and did not continue to www.googleplaymusicdesktopplayer.com. The website is either misconfigured or your computer clock is set to the wrong time.
Chrome  NET::ERR_CERT_DATE_INVALID
@MarshallOfSound
Kind Regards

Fixed


Popup to tab

show mnemonic on a new chrome tab instead popup, make it easier for user to save the copied mnemonic into another application (notepad...), the popup will disappear once lost focus.
I don't think this has any security implication, however unlike the other pull request, but this maybe opinioned

Superseded by #436.
Thanks for your time and contribution.


Flux Generator does not work with Mekanism universal cables

When connecting Mekanism universal cable the generator acts as if nothing is connected.

I don't know what's going on with Mek cables, but it's on there side.
You can use a power cube as a buffer, or if you have Tesla installed you can use Tesla Generator module instead of Flux Generator and the cables work with it.
See #132 and aidancbrady/Mekanism#4188.


If right button title is not present, use image size to determine the width

I wanted to use an image without text for the right button, but needed to update the slk_appropriateRightButtonWidth function to support this.

Fixes #122

@dzenbot Any support for this?

Thanks.

I would appreciate if this will be merged with the master branch


Add a Gitter chat badge to README.md

DarkEnergyScienceCollaboration/Twinkles now has a Chat Room on Gitter
@SimonKrughoff has just created a chat room. You can visit it here: https://gitter.im/DarkEnergyScienceCollaboration/Twinkles.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

We can use this room to chat about Twinkles if people want.


TouchableOpacity in renderItem is clicked while on scroll

Describe the bug
I have TouchableOpacity component in renderItem. While trying to scroll down the list, item(on which my thumb stands on first touch trying to scroll) is automatically clicked.
Following warning is reproduced right after:
Sending 'onAnimatedValueUpdate' with no listeners registered.

To Reproduce
TouchableOpacity component in renderItems. Enough Items to enable scrolling down.
Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

Platform: IOS, Android
React Native or Expo version: 0.61.5
Reanimated version: 1.7.0
React Native Gesture Handler version: 1.5.6

found the cause, it happens when I use onPressOut(due to the current ongoing issue with onPress) within renderItem component.

Thanks for the followup. Closing as underlying issue is #120


Expand tilde in read_edf()

Fixes #22.

I just tried to write a test using a symlinked file or directory (to make sure .resolve() works), but apparently .resolve() is not necessary, as it works either way (at least on linux) :shrug:
Another thought: we should probably use .expanduser() in Edf.write() as well

I just tried to write a test using a symlinked file or directory (to make sure .resolve() works), but apparently .resolve() is not necessary, as it works either way (at least on linux) 🤷

No idea what this actually does, it probably doesn't hurt to leave it in. But it's up to you, let me know if you want me to remove it.
I'll add it to Edf.write(), sure.

(I didn't mean to put my last comment in a review. I meant to write a normal comment, but the UI from within VS Code is... not ideal.)

Thanks @cbrnr!


resume builder added #576

Description
Helps to create your resume and gets you print it.
Fixes:  #576

Added a new js project.

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

Checklist:

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

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

please consider this under GSSoC'22 contribution.

Did you totally make this on your own? If not add the resources you used in a readme file. Also, if you have raised this issue in any other repo then please close this PR

I did took js logic reference from a video and understood it, rest all is coded by me.

Did you totally make this on your own? If not add the resources you used in a readme file. Also, if you have raised this issue in any other repo then please close this PR

I did took js logic reference from a video and understood it, rest all is coded by me.

Add the video link in the readme file

Did you totally make this on your own? If not add the resources you used in a readme file. Also, if you have raised this issue in any other repo then please close this PR

I did took js logic reference from a video and understood it, rest all is coded by me.

Add the video link in the readme file

Added 👍 Please check once.


New version: ClimateERA v0.3.5

Registering package: ClimateERA
Repository: https://github.com/natgeo-wong/ClimateERA.jl
Created by: @natgeo-wong
Version: v0.3.5
Commit: fb0a2d480526378d8e90f5e0ab49a11e4d87e6a7
Reviewed by: @natgeo-wong
Reference: https://github.com/natgeo-wong/ClimateERA.jl/commit/fb0a2d480526378d8e90f5e0ab49a11e4d87e6a7#commitcomment-37315090
Release notes:

Fixed bug for saving of .jld2 files for parameter information that initially pointed to the wrong directory.

Block merger.


Why max out desired number when exceeding the targetvalue by only 1?

My targetvalue is set at 6.  If I bump up to 7 messages in queue, I get this
  "sqs-helloworld-length" (target value):  7 / 6
Min replicas:                              1
Max replicas:                              10
Deployment pods:                           10 current / 10 desired

That's not good if I set my max to 100. I might at all 100 pods for one single message increase.
If I do one lower than the targetvalue, I get this.
  "sqs-helloworld-length" (target value):  5 / 6
Min replicas:                              1
Max replicas:                              10
Deployment pods:                           5 current / 5 desired

Could someone explain why it's behaving this way?

The behavior is controlled by HPA, but this doesn't seem normal to me. HPA is responsible for the scaling, the adapter here is just reports the current value and HPA should decide whether to increase or decrease the number of replicas.
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/


PowerShell Graph Rest API sample of Uploading a large file to SharePoint

PowerShell script showing how to upload a large file to SharePoint using MS Graph Rest API.
Run script with App Registration or user
Updated a spelling mistake from my previous script.

Hey @pmatthews05, thank you, this is a really nice same and use of Graph + Azure CLI!! 👏😊 This should be live shortly 😊


refactor: be more permissive in function inputs

Do not require the caller to pass owned strings, since a reference
will suffice.

I'm still new to Rust, so I hope this is somewhat idiomatic and definitely useful, but I'm very open to feedback!

Actually I also new to rust. I checked rust docs about AsRef<T>, it seems an appropriate usage here. Feel free to make the changes.

Sounds good @jukanntenn, I've updated all uses of &Vec<String>


Planets missing in Electron

The little planets orbiting the rings in the Orbit logo don't appear in Electron. They appear when run in Chrome.
Need to investigate why.
@theobat FYI

This is NOT an Electron bug. The planets go missing only when the theme !== 'Purple' so I think this is to due with the hue-rotation and/or the planets' color format. Need to investigate more.

Found the planets!

Nice!


bbdesign not working in python 3.8.5

bbdesing is not working on Python 3.8.5
This is the error if I try to run the example in the docstring
----> 1 doe.bbdesign(3)

~/virtual_enviroments/hamopt/lib/python3.8/site-packages/pyDOE/doe_box_behnken.py in bbdesign(n, center)
     64
     65     # First, compute a factorial DOE with 2 parameters
---> 66     H_fact = ff2n(2)
     67     # Now we populate the real DOE with this DOE
     68

~/virtual_enviroments/hamopt/lib/python3.8/site-packages/pyDOE/doe_factorial.py in ff2n(n)
    113
    114     """
--> 115     return 2*fullfact([2]*n) - 1
    116
    117 ################################################################################

~/virtual_enviroments/hamopt/lib/python3.8/site-packages/pyDOE/doe_factorial.py in fullfact(levels)
     76         for j in range(levels[i]):
     77             lvl += [j]*level_repeat
---> 78         rng = lvl*range_repeat
     79         level_repeat *= levels[i]
     80         H[:, i] = rng

TypeError: can't multiply sequence by non-int of type 'numpy.float64'

Same Issue. You can test here: https://colab.research.google.com/drive/1paIe2xzREicgILvJSsE7PLlcRXbLNMJu#scrollTo=5rI7gtaEeDdp

with python 3, you have to install pydoe2 instead of pydoe
from pyDOE2 import fullfact, ff2n, fracfact, fold, pbdesign, bbdesign, ccdesign, lhs
bbdesign(3)

Hello @francoisbres thx for your help.
Yes. It's works using :
`
!pip install pyDOE2
from pyDOE2 import fullfact, ff2n, fracfact, fold, pbdesign, bbdesign, ccdesign, lhs
bbdesign(3)
Colab exemple:  https://colab.research.google.com/drive/1paIe2xzREicgILvJSsE7PLlcRXbLNMJu?usp=sharing
Best,
Manuel


[Question]: Changing the host / baseURL

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
How can I change the host to our internal gpt proxy server? I don't see this option in the class.
What am I missing?

Thanks Dosu, but I am using Typescript and I can't find in the docs.

Thanks @dosu-bot., but I am using Typescript (Node.js) and I can't find it in the docs.

Please open an issue on the TS package @Danielg212
Looking at the source code, I'm guessing the base_url is part of the client options object from openai
https://github.com/run-llama/LlamaIndexTS/blob/b64716d3f7e41e0b8db7421b7150cafd13026843/packages/core/src/llm/openai.ts#L13

os.environ['OPENAI_API_KEY'] = "sk-xxxxxx"
os.environ['OPENAI_API_BASE'] = "https://xxxxxx/v1"


Refactor FlutterView / FlutterWindow

In preparation for multi window we need to refactor the FlutterView/FlutterWindow classes in dart:ui:

Remove FlutterWindow class
Move its logic into FlutterView and make that class non-abstract
expose a viewId (instead of a window id like FlutterWindow does today) on the FlutterView that uniquely identifies the view

The goal is to center the engine around views, it will have no idea about windows.

Interestingly, FlutterWindow._windowId is currently typed Object. Should this (or better: the new viewID) just be an int?


Installation on NixOS

Problem
In trying to install the VSCode extension on NixOS, I encounter the following error when I try to open a Rust file.
Logs

OS: linux (6.6.45)
VSCode: 1.92.1
Error message
error: failed to run custom build command for `alsa-sys v0.3.1`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_DEV_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `/home/alice/.cargo-target/plugin-nightly-2024-05-20/debug/build/alsa-sys-473ce205f9ab4211/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=ALSA_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=ALSA_STATIC
  cargo:rerun-if-env-changed=ALSA_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=ALSA_STATIC
  cargo:rerun-if-env-changed=ALSA_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at /home/alice/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18:

  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags alsa

  The system library `alsa` required by crate `alsa-sys` was not found.
  The file `alsa.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `alsa.pc`.

  stack backtrace:
     0: rust_begin_unwind
               at /rustc/d84b9037541f45dc2c52a41d723265af211c0497/library/std/src/panicking.rs:652:5
     1: core::panicking::panic_fmt
               at /rustc/d84b9037541f45dc2c52a41d723265af211c0497/library/core/src/panicking.rs:72:14
     2: core::panicking::panic_display
     3: build_script_build::main
     4: core::ops::function::FnOnce::call_once
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Full log: https://paste.rs/o9I5g

The issue seems to be related to pkgconfig. I don't know the details, but I usually compile rust programs in a Nix shell that has the following configuration:
{ pkgs ? import <nixpkgs> {} }:
  let
    overrides = (builtins.fromTOML (builtins.readFile ./rust-toolchain.toml));
    libPath = with pkgs; lib.makeLibraryPath [
      # load external libraries that you need in your rust project here
    ];
in
  pkgs.mkShell rec {
    buildInputs = with pkgs; [
      clang
      # Replace llvmPackages with llvmPackages_X, where X is the latest LLVM version (at the time of writing, 16)
      llvmPackages.bintools
      rustup
      pkg-config
      openssl
      openssl.dev
      # NB: only for `whenfs`, should probably isolate it as a dependency.
      fuse3
    ];
    RUSTC_VERSION = overrides.toolchain.channel;
    # https://github.com/rust-lang/rust-bindgen#environment-variables
    LIBCLANG_PATH = pkgs.lib.makeLibraryPath [ pkgs.llvmPackages_latest.libclang.lib ];
    shellHook = ''
      export PATH=$PATH:''${CARGO_HOME:-~/.cargo}/bin
      export PATH=$PATH:''${RUSTUP_HOME:-~/.rustup}/toolchains/$RUSTC_VERSION-x86_64-unknown-linux-gnu/bin/
      export PKG_CONFIG_PATH = "${pkgs.openssl.dev}/lib/pkgconfig";
      '';
    # Add precompiled library to rustc search path
    RUSTFLAGS = (builtins.map (a: ''-L ${a}/lib'') [
      # add libraries here (e.g. pkgs.libvmi)
    ]);
    LD_LIBRARY_PATH = libPath;
    # Add glibc, clang, glib, and other headers to bindgen search path
    BINDGEN_EXTRA_CLANG_ARGS =
    # Includes normal include path
    (builtins.map (a: ''-I"${a}/include"'') [
      # add dev libraries here (e.g. pkgs.libvmi.dev)
      pkgs.glibc.dev
    ])
    # Includes with special directory paths
    ++ [
      ''-I"${pkgs.llvmPackages_latest.libclang.lib}/lib/clang/${pkgs.llvmPackages_latest.libclang.version}/include"''
      ''-I"${pkgs.glib.dev}/include/glib-2.0"''
      ''-I${pkgs.glib.out}/lib/glib-2.0/include/''
    ];
  }

I would guess that my version of VSCode (installed via home-manager) does not know how to set PKG_CONFIG_PATH appropriately. Is there a simple way to work around this that I can do on my  side, or does my issue require some condition in the argus extension itself?

I ran into a similar problem when setting up a shell environment for a project that uses Bevy. The fix that I found there was that pkg-config needs to be a nativeBuildInput, you can see that in my argus flake https://github.com/cognitive-engineering-lab/argus/blob/9ba45fa9c6105030f2e7f89ba45e3fc029b3990b/flake.nix#L77 you'll also need alsa-lib and udev in your buildInputs, see here https://github.com/cognitive-engineering-lab/argus/blob/9ba45fa9c6105030f2e7f89ba45e3fc029b3990b/flake.nix#L107-L109
I believe that this should solve your issue. For argus to work properly on Nix the rust toolchain needs to be managed by rustup—long frustrating reason why—but it seems you are doing that. Let me know if this works for you.

Side note, I'm a little confused why alsa is needed if you're just installing the extension from the VS Code marketplace. This is usually only necessary when building from source 🤔

Great, thank you! Documenting the process here for other users.

Create a "shell.nix" file in a directory with the following contents (my configuration above with @gavinleroy additions):

{ pkgs ? import <nixpkgs> {} }:
  let
    libPath = with pkgs; lib.makeLibraryPath [
      # load external libraries that you need in your rust project here
    ];
in
  pkgs.mkShell rec {
    nativeBuildInputs = with pkgs; [ pkg-config ];

    buildInputs = with pkgs; [
      clang
      llvmPackages.bintools
      rustup
      pkg-config
      openssl
      openssl.dev
      # for argus
      alsa-lib.dev
      udev.dev
    ];
    RUSTC_VERSION = "nightly";
    # https://github.com/rust-lang/rust-bindgen#environment-variables
    LIBCLANG_PATH = pkgs.lib.makeLibraryPath [ pkgs.llvmPackages_latest.libclang.lib ];
    shellHook = ''
      export PATH=$PATH:''${CARGO_HOME:-~/.cargo}/bin
      export PATH=$PATH:''${RUSTUP_HOME:-~/.rustup}/toolchains/$RUSTC_VERSION-x86_64-unknown-linux-gnu/bin/
      export PKG_CONFIG_PATH = "${pkgs.openssl.dev}/lib/pkgconfig";
      '';
    # Add precompiled library to rustc search path
    RUSTFLAGS = (builtins.map (a: ''-L ${a}/lib'') [
      # add libraries here (e.g. pkgs.libvmi)
    ]);
    LD_LIBRARY_PATH = libPath;
    # Add glibc, clang, glib, and other headers to bindgen search path
    BINDGEN_EXTRA_CLANG_ARGS =
    # Includes normal include path
    (builtins.map (a: ''-I"${a}/include"'') [
      # add dev libraries here (e.g. pkgs.libvmi.dev)
      pkgs.glibc.dev
    ])
    # Includes with special directory paths
    ++ [
      ''-I"${pkgs.llvmPackages_latest.libclang.lib}/lib/clang/${pkgs.llvmPackages_latest.libclang.version}/include"''
      ''-I"${pkgs.glib.dev}/include/glib-2.0"''
      ''-I${pkgs.glib.out}/lib/glib-2.0/include/''
    ];
  }

Run nix-shell
Open VSCode from that shell by running the command code.

Argus now runs in that Nix shell, and no longer throws the error.

Thanks for reporting back! I will note here that this fix is necessary only for participants of the online study at Brown. (The error shown on Zulip is from building a test crate and not installing Argus itself.)
For others using Argus in the wild it's sufficient to have rustup available on the path.

For the second example, I had to also include the package libmysqlclient.dev to the end of buildInputs in the shell.nix. Leaving it here in case it's useful to someone else. Furthermore, the spaces between the = in the PKG_CONFIG_PATH line must be removed. The final shell.nix which I used to correctly install Argus was the following:
{ pkgs ? import <nixpkgs> {} }:
  let
    libPath = with pkgs; lib.makeLibraryPath [
      # load external libraries that you need in your rust project here
    ];
in
  pkgs.mkShell rec {
    nativeBuildInputs = with pkgs; [ pkg-config ];

    buildInputs = with pkgs; [
      clang
      llvmPackages.bintools
      rustup
      pkg-config
      openssl
      openssl.dev
      # for argus
      alsa-lib.dev
      udev.dev
      libmysqlclient.dev
    ];
    RUSTC_VERSION = "nightly";
    # https://github.com/rust-lang/rust-bindgen#environment-variables
    LIBCLANG_PATH = pkgs.lib.makeLibraryPath [ pkgs.llvmPackages_latest.libclang.lib ];
    shellHook = ''
      export PATH=$PATH:''${CARGO_HOME:-~/.cargo}/bin
      export PATH=$PATH:''${RUSTUP_HOME:-~/.rustup}/toolchains/$RUSTC_VERSION-x86_64-unknown-linux-gnu/bin/
      export PKG_CONFIG_PATH="${pkgs.openssl.dev}/lib/pkgconfig";
      '';
    # Add precompiled library to rustc search path
    RUSTFLAGS = (builtins.map (a: ''-L ${a}/lib'') [
      # add libraries here (e.g. pkgs.libvmi)
    ]);
    LD_LIBRARY_PATH = libPath;
    # Add glibc, clang, glib, and other headers to bindgen search path
    BINDGEN_EXTRA_CLANG_ARGS =
    # Includes normal include path
    (builtins.map (a: ''-I"${a}/include"'') [
      # add dev libraries here (e.g. pkgs.libvmi.dev)
      pkgs.glibc.dev
    ])
    # Includes with special directory paths
    ++ [
      ''-I"${pkgs.llvmPackages_latest.libclang.lib}/lib/clang/${pkgs.llvmPackages_latest.libclang.version}/include"''
      ''-I"${pkgs.glib.dev}/include/glib-2.0"''
      ''-I${pkgs.glib.out}/lib/glib-2.0/include/''
    ];
  }


Failing tests for discussion #3780

Unit tests to reproduce errors from discussion #3780.

Thanks, merged and fixed.


APS-2900 - add mac install instructions

I gave it a test but @timng-bcgov maybe you can double check?

Aidan found it works


ci: uncomments gh-pages deploy step

Description
Uncomments the deploy step.

:tada: This PR is included in version 7.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[VAX-1006] Possible race condition in process.subscribe()

We sometimes are encountering an issue in the subscribe call. The subscription notifier doesn't have the subscription id after the client.subscribe() is finished. While debugging we noticed that when this happens it's because the subscription data message is received before client.subscribe() finishes. So when trying to read the promise from the subscription notifiers it's undefined.
The subscribe function
https://github.com/electric-sql/electric/blob/553a817770691e7afa3ac07562f443650ef87843/clients/typescript/src/satellite/process.ts#L374
This is what triggers the websocket communication that can end up deleting the subscriptionId before finishing.
https://github.com/electric-sql/electric/blob/553a817770691e7afa3ac07562f443650ef87843/clients/typescript/src/satellite/process.ts#L415
Here is where we get the undefined exception.
https://github.com/electric-sql/electric/blob/553a817770691e7afa3ac07562f443650ef87843/clients/typescript/src/satellite/process.ts#L431
Here is where the subscription is being removed.
https://github.com/electric-sql/electric/blob/553a817770691e7afa3ac07562f443650ef87843/clients/typescript/src/satellite/process.ts#L451
Would it make sense to check after client.subscribe() if the subscription exists? Or is that something that shouldn't happen?
When everything works fine, during client.subscribe() WebSocket only receives SatSubsResp. And after that the rest of the subscription messages are received (SatSubsDataBegin, ..., SatSubsDataEnd). When it fails this messages are received while the client.subscribe() is running.
VAX-1006

We're working on some improvements to the protocol and will look into this after.
https://github.com/electric-sql/electric/pull/423

I'm currently investigating a very similarly looking problem, though I traced it down to different locations in the client code from the original report here. Instead of an undefined exception, I'm getting this:
encountered a subscription error: Received subscribe response for unknown subscription bfca735d-5037-4685-b547-74a4946118f1
connectivity state changed disconnected
client disconnected from server
Uncaught:
i [Error]: Received subscribe response for unknown subscription bfca735d-5037-4685-b547-74a4946118f1
    at q.internalError (file:///app/node_modules/.pnpm/file+clients+typescript_react-dom@18.2.0_react@18.2.0/node_modules/electric-sql/dist/satellite/shapes/cache.js:1:3515)
    at q.subscriptionResponse (file:///app/node_modules/.pnpm/file+clients+typescript_react-dom@18.2.0_react@18.2.0/node_modules/electric-sql/dist/satellite/shapes/cache.js:1:682)
    at Re.handleSubscription (file:///app/node_modules/.pnpm/file+clients+typescript_react-dom@18.2.0_react@18.2.0/node_modules/electric-sql/dist/satellite/client.js:1:11025)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async oe.subscribe (file:///app/node_modules/.pnpm/file+clients+typescript_react-dom@18.2.0_react@18.2.0/node_modules/electric-sql/dist/satellite/process.js:3:2997)
    at async Module.$ (file:///app/dist/client.js:1:1125)
    at async REPL7:1:33 {
  code: 26
}

I can reliably reproduce this when running the E2E test suite in https://github.com/electric-sql/electric/pull/500.
Here's the sequences of protocol messages that leads to the exception:
[rpc] send: #SatSubsReq{id: bfca735d-5037-4685-b547-74a4946118f1, shapes: [{"$type":"Electric.Satellite.SatShapeReq","requestId":"fe977dcd-c79c-431a-b9da-2aa923c6dfce","shapeDefinition":{"$type":"Electric.Satellite.SatShapeDef","selects":[{"$type":"Electric.Satellite.SatShapeDef.Select","tablename":"items"}]}}]}
[proto] send: #SatRpcRequest{method: subscribe, requestId: 3}
[proto] recv: #SatRpcResponse{method: subscribe, requestId: 3}
[proto] recv: #SatSubsDataBegin{id: bfca735d-5037-4685-b547-74a4946118f1, lsn: MjU1MTEyODA=}
[proto] recv: #SatShapeDataBegin{id: fe977dcd-c79c-431a-b9da-2aa923c6dfce}
[proto] recv: #SatOpLog{ops: []}
[proto] recv: #SatShapeDataEnd{}
[proto] recv: #SatSubsDataEnd{}
actually changed notifier
[rpc] recv: #SatSubsResp{id: bfca735d-5037-4685-b547-74a4946118f1}

For comparison, here's what the working sequence looks like:
[rpc] send: #SatSubsReq{id: b1f3087c-6eac-43c9-92b7-83d622abf678, shapes: [{"$type":"Electric.Satellite.SatShapeReq","requestId":"737a6fa4-1b48-4c01-855b-a4d4c187da3f","shapeDefinition":{"$type":"Electric.Satellite.SatShapeDef","selects":[{"$type":"Electric.Satellite.SatShapeDef.Select","tablename":"items"}]}}]}
[proto] send: #SatRpcRequest{method: subscribe, requestId: 3}
[proto] recv: #SatRpcResponse{method: subscribe, requestId: 3}
[rpc] recv: #SatSubsResp{id: b1f3087c-6eac-43c9-92b7-83d622abf678}
[proto] recv: #SatSubsDataBegin{id: b1f3087c-6eac-43c9-92b7-83d622abf678, lsn: MjU1MTEwNjQ=}
[proto] recv: #SatShapeDataBegin{id: 737a6fa4-1b48-4c01-855b-a4d4c187da3f}
[proto] recv: #SatOpLog{ops: []}
[proto] recv: #SatShapeDataEnd{}
[proto] recv: #SatSubsDataEnd{}
actually changed notifier

The difference between the two being in the ordering of the SatSubsResp message, everything else remains the same.
I was looking into how my server-side changes could cause this when I remembered this issue that had already been reported by @js2702. So it looks like my changes aren't the root cause but have somehow made it more likely for the race to occur.

A bit more info on the error I'm seeing: the exception is raised in SubscriptionDataCache.subscriptionResponse(), and the subscription itself gets deleted in SubscriptionDataCache.reset() when the SatSubsDataEnd message is processed, so that there's no cache entry for it by the time SatSubsResp arrives.

After studying the server log I'm inclined to conclude that it's a client-side error. I couldn't see any difference in processing the SatSubsReq between two clients on the server, yet each client logs that fact that it received the response at different points.
cc @balegas @kevin-dp

@alco that's definitely a client-side issue. The issue there is the difference where the event loop gets resolved. RPC message decode returns a promise resolution, but that releases the event loop, and sometimes, if the message from the server arrives in the subsequent frames, the event loop enters in message processing instead of in resolving await call - and the message gets processed ahead of handling of RPC response

@icehaunter I'm at a loss as to why my changes to how PG connections are pooled on the server could affect this client-side issue such that I see 1 to 3 E2E tests fail with this error every time I run the E2E workflow from https://github.com/electric-sql/electric/pull/500 on CI. It hasn't succeeded once here on GH, I've only been able to see the full E2E test suite pass on my machine.

@alco When @js2702 and I reported this issue it was only happening on a Linux machine, on macOS it was working correctly.
We stopped seeing this issue when we implemented the new overhauled RPC communication on the Dart client, though. We also managed to avoid the issue temporarily by adding the equivalent of asyncSleep(0) for Dart, when receiving websocket messages on the client, although that's more a hack than a proper fix, hence why we opened the issue.


Integration with scalelite

Hi guy,
I think it is a really good project.
I need to test it.
Just a suggestion, in your script you download all the file and you recreate the structure you need to create the video file. Why don't just search the file on the BBB instance ( only if you have 1 BBB instance ) or on the scaling tool "scalelite".
In the case of scalelite, all the files of all the BBB instances are re-exported in a NFS server.
So you could adapt your script to just get the files from the directory and do the same.
In a second way, you just need to find a way to start your script each time a new record is ready to be "converted".
To help you in the integration of Greenlight, go here https://github.com/EugeneWHZ/greenlight/commit/e0ced1815b7279342c9eef5d71cb8b78e8a24470
Regards,
Aurelien.

Hi @aguerson ,
Thank you for taking a look at my project. It is very much still in its infancy, so your feedback is appreciated.
You are correct that the current code recreates the structure needed to create the video file. That is currently so because I don't have a BBB server running yet, so everything was done client-side.
Once I have a server up and running, the files will be taken from the BBB directories directly.
I hope I understood your question correctly, if not, please let me know.
I'll take a look into Scalelite, thanks for the suggestion and the link to help with the integration in Greenlight. My idea was not to run the script once a recording is ready to be converted, but rather only once the user wants it through Greenlight's interface to save resources. What do you think?
Regards,
Daniel

but rather only once the user wants it through Greenlight's interface to save resources. What do you think?

Yes you are right.
I need to test your code to give you me feedback. I am using https://github.com/jibon57/bbb-recorder since a while, and I hope your approach is fastest.
See you soon,
Regards,
Aurelien.

Hi,
I tested your script today and I confirm It is compatible with Scalelite and Greenlight.
Thanks and congratulations,
Thierry

Hi @pielonet, that's great to hear, thank you!


correct command for using specified openssl with cmake

Pull Request Checklist
Hi there, I'm trying to integrate the Azure SDK into apache doris, and during the process, I found that I need to specify a particular version of OpenSSL. At this point, I discovered that the related commands in the documentation were incorrect, so I'm attempting to correct the documentation through this PR.
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

Thank you very much for catching my typo, the change looks good.
Let me know if you're done with verifying the fixes so I can merge the changes in.

Thank you very much for catching my typo, the change looks good.
Let me know if you're done with verifying the fixes so I can merge the changes in.

Hi @LarryOsterman , sorry for my late response. I have already passed the verification, everything is fine now, and it’s ready to be merged.


Add and improve Japanese translations

Thank your for this awesome app!
I added Japanese translation to App/Localizable.xcstrings and BatFiKit/Sources/L10n/Localizable.xcstrings.
I changed some Japanese translation to comply Apple's glossary.

Thank you very much! :)


Tweaks export/import bug.

Describe the bug
If you select the standard tweaks then export it & import it, everything is same except Change Windows Terminal default is automatically selected.
Expected behavior
Exported config should be the same as per user choice.
Screenshots
Export:

Import:

Hello, @Garou7! Thanks for the report!
I just tested this and I wasn't able to replicate the issue you showed in your first screenshot, I used a config with WPFTweaksPowershell7Tele as the only feature enabled, and Change Windows Terminal default: PowerShell 5 -> PowerShell 7 is appropriately checked alongside Disable PowerShell 7 tele, as PowerShell 7 telemetry can't be disabled if PowerShell 7 is not installed:

Can you upload your configuration file here so I can take a look at it and see if you have WPFTweaksPowershell7Tele enabled?

@Cryostrixx I think i found the culprit Disable Powershell 7 Telemetry, if you select ANY checkbox in tweaks with Disable Powershell 7 Telemetry & ignore the Change Windows Terminal default then import & export it will automatically select the Change Windows Terminal default even tho you didnt choose it.
Another example:
Export:

Import:

@Cryostrixx I think i found the culprit Disable Powershell 7 Telemetry, if you select ANY checkbox in tweaks with Disable Powershell 7 Telemetry & ignore the Change Windows Terminal default then import & export it will automatically select the Change Windows Terminal default even tho you didnt choose it.
Another example:
Export:
Import:

I understand where you are coming from but this is intended behavior, PowerShell 7 telemetry is specific to PowerShell 7, here's my config:
{
  "WPFFeature": [
    "WPFFeatureEnableLegacyRecovery",
    "WPFFeaturesdotnet",
    "WPFFeatureslegacymedia",
    "WPFFeatureDisableSearchSuggestions"
  ],
  "WPFInstall": [],
  "WPFTweaks": [
    "WPFTweaksRestorePoint",
    "WPFTweaksAH",
    "WPFTweaksDebloatAdobe",
    "WPFTweaksHome",
    "WPFTweaksHiber",
    "WPFTweaksPowershell7Tele",
    "WPFTweaksDisableLMS1",
    "WPFTweaksBlockAdobeNet",
    "WPFTweaksLaptopHibernation",
    "WPFTweaksEdgeDebloat",
    "WPFTweaksDVR",
    "WPFTweaksRemoveHomeGallery",
    "WPFTweaksStorage",
    "WPFTweaksRightClickMenu",
    "WPFTweaksServices",
    "WPFTweaksTele",
    "WPFTweaksEndTaskOnTaskbar",
    "WPFTweaksLoc",
    "WPFTweaksDiskCleanup",
    "WPFTweaksWifi",
    "WPFTweaksRemoveCopilot",
    "WPFTweaksConsumerFeatures",
    "WPFTweaksRemoveOnedrive",
    "WPFTweaksRemoveEdge",
    "WPFTweaksDeleteTempFiles"
  ],
  "Install": []
}

I don't have WPFTweaksPowerShell7 in my config but I do have WPFTweaksPowerShell7Tele, one feature cannot be enabled without the other, if you don't have PowerShell 7 its telemetry cannot be disabled, so the option to replace PowerShell 5 with PowerShell 7 is checked, as the tooltip for Change Windows Terminal default: PowerShell 5 -> PowerShell 7 says: This will edit the config file of the Windows Terminal replacing PowerShell 5 with PowerShell 7 and installing PS7 if necessary.
You can test this for yourself by downloading this config: winutil-test.json, it only has Disable PowerShell 7 Telemetry enabled, import it and you'll see that Change Windows Terminal default: PowerShell 5 -> PowerShell 7 is checked as a dependency for Disable PowerShell 7 Telemetry.

@Garou7 Update: I just checked the code for WPFTweaksPowerShell7Tele and I don't see anything that would enable WPFTweaksPowerShell7.
I'll dig through the code and see if I can determine what is causing this issue.

@Garou7 I looked through all the code, and I couldn't find anything that enables Change Windows Terminal default: PowerShell 5 -> PowerShell 7 when Disable PowerShell 7 Telemetry is enabled, for now, what I'd suggest you do is manually uncheck Change Windows Terminal Default: PowerShell 5 -> PowerShell 7 each time you import your config. It isn't ideal but it'll only take a few seconds to do each time, in the meantime, you should provide a few things in this issue:

Your operating system version (you can get to this by opening your start menu, typing winver.exe, and hitting Enter).
Your Windows Terminal version, you can get this by opening Windows Terminal, typing wt --version, and hitting Enter.
Your Windows PowerShell version information, you can get this by opening PowerShell, typing $PSVersionTable, and hitting Enter.
Your WinUtil version, you can access this by clicking the settings cog on the top right, and clicking on About.
The tweaks and features you use with WinUtil, for this the easiest way to share that is to upload your WinUtil configuration file here.

Copy and paste all of this information and send it in the comments, it will make it as easy as possible for contributors to replicate your environment as closely as possible and perform further testing.

@Garou7 That's a known issue i think, another contributor would have to confirm that for me, I'll test the issue you reported initially with the information you provided when I get back to my device that has WinUtil on it.

Where I can find the WinUtil configuration file?

@Garou7 Oh, I didn't see that part, sorry! If you have a WinUtil configuration file it should be in your Documents folder: C:\Users\<your-username-here>\Documents, if it isn't in your Documents folder the other common path to save config files is in C:\Users\<your-username-here>\Desktop.
If you don't know where it is stored you can navigate to the C:\ drive in File Explorer and search for the name of your config file, Right-click, and select Open file location.


post with unicode data and the post body will be truncated!!!

when i use requests post data with unicode, and the content-length will be wrong, and the post data will be truncated, test with requests 2.10.0
test code

# -*- coding: utf-8 -*
import json
import requests
# use utf-8
import sys
reload(sys)
sys.setdefaultencoding('utf-8')

data = json.dumps({'test': u"测试"}, ensure_ascii=False)
print data
resp = requests.post('https://github.com/kennethreitz/requests/issues', data=data, verify=False)

fiddler snapshot

reason

data = json.dumps({'test': u"测试"}, ensure_ascii=False)
the unicode length: len(data) = 14
the utf-8 chars length len(data.encode('utf-8')) = 18
encode with utf-8 but the content-length not change, so, the post body is truncated data
data.encode('utf-8')[:len(data)] = {"test": "测

is it a bug? need help

Why are you passing ensure_ascii=False?

Anyway, that's kind of neither here nor there. There are several solutions to your problem:

Don't use ensure_ascii=False. There's no requirement to do it: JSON allows unicode escape characters.
Alternatively, don't pass Requests a unicode string in data. This kind of works in Python 2, but I wish it didn't: it makes no sense. Encode it yourself using utf-8.
Just defer all of this decision making and use requests.post(url, json={'test': u"测试"}).


New package version creation fails on required custom metadata fields

Summary
When creating new version of previously managed-released package with required fields on custom metadata, the CLI errors that the fields cannot be changed - even when they are not changed.
Steps To Reproduce:
I don't have a repos that can easily demonstrate this since it requires a previously managed-released package, but the steps are:

In a version before 7.11 create and release a managed package version.  The package should contain fields on custom metadata types that include <required>true</required> tags.
Update CLI to 7.11 (this may not be related, but it's what I did to reach this point)
Try to create new package version using force:package:version:create, without changing the metadata for the required fields on the custom metadata.

Expected result
Package version creation should succeed.
Actual result
Seeing the following error for every required field on every custom metadata type.
Value__c: Cannot modify managed object: entity=CustomFieldDefinition, component=<anId>, state=MANAGED_RELEASED, Field: OptionsFlag OptionBit: OptionsFlagRequired Previous Value: true New Value: null\n
System Information
{
"cliVersion": "sfdx-cli/7.110.0",
"architecture": "win32-x64",
"nodeVersion": "node-v14.17.3",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.2.2 (core)",
"@oclif/plugin-not-found 1.2.4 (core)",
"@oclif/plugin-plugins 1.10.0 (core)",
"@oclif/plugin-update 1.4.0-3 (core)",
"@oclif/plugin-warn-if-update-available 1.7.0 (core)",
"@oclif/plugin-which 1.0.3 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"@salesforce/sfdx-trust 3.6.0 (core)",
"alias 1.1.10 (core)",
"apex 0.2.2 (core)",
"auth 1.7.1 (core)",
"config 1.2.13 (core)",
"custom-metadata 1.0.12 (core)",
"data 0.5.2 (core)",
"generator 1.1.7 (core)",
"limits 1.2.1 (core)",
"org 1.6.7 (core)",
"salesforce-alm 52.1.0 (core)",
"schema 1.0.8 (core)",
"sfdx-cli 7.110.0 (core)",
"telemetry 1.2.2 (core)",
"templates 52.1.0 (core)",
"user 1.3.1 (core)"
],
"osVersion": "Windows_NT 10.0.19044"
}
Additional information
It's interesting to me that the error message indicates the 'new value' is 'null\n' - yet in the XML the tag for required has a 'true' value, just like before.
The version creation routine does not report any problems on required fields on custom objects.  Just custom metadata types.

I downgraded to 7.88.1 and I'm receiving the same error.  So I am not sure this has much to do with the local CLI version.

I'm seeing this same metadata error when running the command  sfdx force:source:push  . Nothing about our metadata has changed since the last time we were successfully able to push.

I'm glad I'm not alone.  This error started happening today suddenly.
force-app/main/default/objects/CbAppSetting__mdt/fields/Value__c.field-meta.xml      Cannot modify managed object: entity=CustomFieldDefinition, component=00N3F00000Oqnr7, state=MANAGED_RELEASED, Field: OptionsFlag OptionBit: OptionsFlagRequired Previous Value: true New Value: null (6:13)

For those of you having issues with simple pushes, try building your SOs with the noancestors option.  I've had no issues pushing using this method.  It won't help if you need to cut a new package version... but it might get you unstuck.

For info this has been raised on the partner chatter, and this is a response that was posted there.

It looks like there is a bug that was just logged for this.
I'm going to reach out to the engineering team to get guidance on when an expected fix will go out. I'll report back here on this thread when I have more information.

Creating 2gp package version gave same error for me, even though there were no changes to the custom metadata.
sfdx-cli/7.110.0 win32-x64 node-v14.17.3

Got this issue yesterday. Was not able to get rid of ancestor.
But now seems like this bug was fixed.

There's a post along these lines on the Partner Chatter thread I mentioned above.

As far as I know, this issue should have been solved now. I asked <...> to check and he confirmed that the issue has been solved for them. FYI

Removing api version from sfdx-project.json and thereby upping the version of the temporary scratch org from 51 to 52 during the build fixed it for me.
sfdx force:package:version:create -n <ver> -a "Ver <ver>" -t <ver> -x -c -e "<ver desc>" -p <package>  -f .\config\project-scratch-def.json -w 300

Is anyone still seeing this error?


Wrong example for filtering users by authentication methods

The example shows that you can filter user registration details by methodsRegistered which is a collection, so the query in example will never work
/reports/userRegistrationDetails?$filter=methodsRegistered eq 'email'

The correct example should be with any
/reports/userRegistrationDetails?$filter=methodsRegistered/any(x:x eq 'email')

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

ID: 21801e97-c4a8-f381-c80a-1f2fd1da7de6
Version Independent ID: e79dd7b7-4e27-06c6-744d-5b3b8aac39df
Content: List userRegistrationDetails - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/authenticationmethodsroot-list-userregistrationdetails.md
Product: identity-and-access-reports
Technology: microsoft-graph
GitHub Login: @kvenkit
Microsoft Alias: MSGraphDocsVteam

Thank you @MartinM85 for pointing out this error. I've raised a PR to fix the example.


Unsatisfiable requirements detected for package

Hi, I am looking forward to using MarSwitching.jl for developing a forecast model. However, during my installation, the error was thrown.
ERROR: Unsatisfiable requirements detected for package MarSwitching [b2b8a7f1]:  MarSwitching [b2b8a7f1] log:  ├─possible versions are: 0.1.1 or uninstalled  ├─restricted to versions * by an explicit requirement, leaving only versions: 0.1.1  └─restricted by compatibility requirements with NLopt [76087f3c] to versions: uninstalled — no versions left    └─NLopt [76087f3c] log:      ├─possible versions are: 0.5.0-1.0.0 or uninstalled      ├─restricted to versions * by an explicit requirement, leaving only versions: 0.5.0-1.0.0      └─restricted by compatibility requirements with QuantEcon [fcd29c91] to versions: 0.5.0-0.6.5        └─QuantEcon [fcd29c91] log:          ├─possible versions are: 0.14.3-0.16.5 or uninstalled          └─restricted to versions * by an explicit requirement, leaving only versions: 0.14.3-0.16.5
And the version of local packages are
"VegaLite"                 => v"3.2.3"
"Query"                    => v"1.0.0"
"UpdateJulia"              => v"0.4.2"
"NLopt"                    => v"0.6.5"
"LaTeXStrings"             => v"1.3.0"
"MixedModels"              => v"4.22.1"
"StructuralEquationModels" => v"0.2.1"
"IJulia"                   => v"1.24.2"
"Plots"                    => v"1.39.0"
"Metal"                    => v"0.5.1"
"Pluto"                    => v"0.19.30"
"DataFrames"               => v"1.3.6"
"UnicodePlots"             => v"3.6.0"
"QuantEcon"                => v"0.16.5"
Will  the later version meeting the satisfaction of latest packages?
Thanks!

Thanks for opening this issue!
I see the QuantEcon.jl requires NLopt.jl to be between 0.5.0 and 0.6.5. I reproduced your error and after downgrading package requirements for NLopt to ">= 0.6.5" it should work.
I will soon release new version to the Julia's general registry with other improvements. Meanwhile you may use: ] add MarSwitching#main This will install the github version of the package with the changes. Tell me if it works.

Hi! Thank you for your quick reply.
However, I have tried several times. It seems the conflicting packages are MarSwitching and QuantEcon. The following codes could install the package properly.
julia ] rm QuantEcon resolve add MarSwitching
And, after MarSwitching installed,  the QuantEcon is not able to be installed anymore.
Considering the popular usage of QuantEcon, I am looking forward to the update of MarSwitching.
Thanks for your contribution and share it~

Yes, the general registry version of MarSwitching.jl has old compatibilities. I just changed dependency requirements in github version and will release this version to the general registry soon.
In the meantime you may try installing the github version and see if it still conflicts with QuantEcon:
] add MarSwitching#main
Tell me if this one works.

Yes, the general registry version of MarSwitching.jl has old compatibilities. I just changed dependency requirements in github version and will release this version to the general registry soon.
In the meantime you may try installing the github version and see if it still conflicts with QuantEcon:
] add MarSwitching#main
Tell me if this one works.

Sorry for delay reply, and this works. Thank you for your contribution!


Skipped test in downloaded report is missing list of nodes

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Download a CIS Scan report (make sure a test is skipped in the scan report)

Expected Result:
The skipped test should have the nodes column populated with apt nodes.
Actual Result:
The skipped test is missing the list of applicable "nodes" column
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master head - commit id: 656781c34
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Kubernetes version (use kubectl version):

1.15

Docker version (use docker version):

(paste the output here)

This isn't a bug. The test wasn't run on the nodes.