[ISSUE #1653] Refactor Code about client register.

Feature #1653

Use factory to refactor code about client register.

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1654 (f4d0803) into master (9011e97) will decrease coverage by 3.38%.
The diff coverage is 13.25%.

:exclamation: Current head f4d0803 differs from pull request most recent head ffb8d61. Consider uploading reports for the commit ffb8d61 to get more accurate results

@@             Coverage Diff              @@
##             master    #1654      +/-   ##
============================================
- Coverage     62.81%   59.42%   -3.39%
+ Complexity     2220     2216       -4
============================================
  Files           460      469       +9
  Lines          9547    10073     +526
  Branches        976     1021      +45
============================================
- Hits           5997     5986      -11
- Misses         3057     3605     +548
+ Partials        493      482      -11

Impacted Files
Coverage Δ

...enyu/admin/config/RegisterCenterConfiguration.java
100.00% <ø> (ø)

...in/disruptor/RegisterServerDisruptorPublisher.java
85.71% <ø> (ø)

.../register/AbstractShenyuClientRegisterService.java
2.08% <2.08%> (ø)

...ster/ShenyuClientRegisterSpringMVCServiceImpl.java
11.11% <11.11%> (ø)

...er/ShenyuClientRegisterSpringCloudServiceImpl.java
12.30% <12.30%> (ø)

.../register/ShenyuClientRegisterTarsServiceImpl.java
12.82% <12.82%> (ø)

.../register/ShenyuClientRegisterGrpcServiceImpl.java
13.69% <13.69%> (ø)

...register/ShenyuClientRegisterMotanServiceImpl.java
13.69% <13.69%> (ø)

.../register/ShenyuClientRegisterSofaServiceImpl.java
16.32% <16.32%> (ø)

...register/ShenyuClientRegisterDubboServiceImpl.java
18.60% <18.60%> (ø)

... and 20 more

Continue to review full report at Codecov.

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


How to document parts of my single API parameter?

This may be a feature-request or just a blindness on my side.
All my POST request have a single JSON argument in the POST body. For example, for updates, it's the desired new state of the entity like
{
    "id": 76682889,
    "email"<EMAIL_ADDRESS>    "firstname": "Mad",
    "surname": "Max",
    "zipcode": "12345"
}

This argument is obviously required, but it consists of required and optional parts, which itself should be documented. I can't see how to express it in the input JSON.
"User_UPDATE": {
  "type": "object",
  "required": ["id", "email"],    // This seems to work with swagger-codegen, but not with pretty-swag
  "properties": {
    "id": {
      "type": "integer",
      "format": "int32"
                                  // This fields has documentation, how can I express it?
    }
    ...
}

Hey thanks for reporting.
I want to keep the schema panel area clean and minimal so developer can easily and quickly copy and paste the payload. Also I don't have a good way to display if fields are required. In my opinion, adding * to key is somewhat confusing but I am open to suggestions.
We could add a short comment next to the field by adding description on that particular object.
If there is a need of thorough detail, I would suggest to put it on method level description which support markdown and more space.
Would this more or less suit your need?
"User_UPDATE": {
  "type": "object",
  "required": ["id", "email"],
  "properties": {
    "id": {
      "type": "integer",
      "format": "int32",
      "description": "required"
    }
    ...
}

In my opinion, adding * to key is somewhat confusing but I am open to suggestions.

Adding * is pretty commonplace and very compact. I saw it in an alike application and it was in red and I'd be really happy with something like this.
A short description next to the field would suffice most of the time, but you could allow longer description showing in color and with expandable eclipses or a mouse-over hint. This would be perfect:
"email": "string", // email gets validated against RFC ...

Say if we choose to add * in our schema like so:
{
    "email*": "string",          // Put * before closing quotation this is the confusing part I referred to
                                // One could ask a question "Is the key has * in name or it need to be removed ?"
    "name"*: "string"          // Put * after closing quotation
}

The step required developers to use this schema would be:

Copy schema
Paste it either to the payload panel below or their IDE
Mass find/replace to remove *.

Step 3 is what I feel like an unnecessary step
Your thought on this?
PS. I agree with you on the longer description just have to find time to work on that.

What about
{
    "email": "string"*,          // Put * after closing quotation of the TYPE as this is a required string
}

Actually, the star could be inside the quotes, too, as there's no confusion about the name. Making it red should make clear that it's not part of the type.
Can't you use a trick so it doesn't get copied? Would CSS ::after selector help?
Otherwise, what about adding a copy link which would hide the problematic parts and mark the to be copied text, so copying wouldn't require marking the whole text manually?

I agree with you on the longer description just have to find time to work on that.

I'd contribute it, but I can't figure out how it all works. If you do anything in this area, I guess, I'll be able to finish it.

I like the idea of putting * after value in quotation I should be able to add that in.
The color and handle long desc implementation is a little tricky because currently folding functionality is implemented in text based and display result using
.
If we were to convert this to html based, we need to look at getSchema function (in the generated html). It takes schema (json string) and bracket folding state and return appropriate string.

The color and handle long desc implementation is a little tricky because currently folding functionality is implemented in text based and display result using
.

My problem is the tokens containing \n, which makes ::after show the star on the next line.
As a hack, I used ::before instead. This looks a bit strange, but with the star being red and non-copyable, there's no confusion. Moreover, it makes the information nicely aligned.

Few points worth mention: ...

You're right with all of them. I like "category": {* ...} most, as the trailing star is probably most clear and easiest to spot. For copy&paste, "category": {...}* would be best, but I still hope that using ::after will be possible.
What I tried, is not worth a PR;  here you can see it all:

{{token.val}}

In getSchema, I'm missing the information about what's mandatory.

So I come up with prove of concept like you suggestion here using ::after.
And to my surprise, I just realized that * won't be copied when using ::after 🎉
I'll try to put together a solution for this and probably going to place * outside of the double quotation.
POC:

{
    "hello": {
        "key1": "val1",
        "key2": "val2"
    }
}

Turned out I like * in quotation more.
What is your opinion?

I did some changes in https://github.com/Maaartinus/livedoc, which were requested from me and which you may or mayn't like, but I have no idea how to pass the needed information around the stringly-typed schema.
I'd like to show both required as a star and some additional info for some fields. I saw, there are some comments, but I'm unsure how to do it.
Do you think you'll get to it anytime soon?

Should be able to work on this on the weekend. Very close to release. I just need to handle folding part.

I rolled out in the latest (0.1.152) and will roll out another patch that incorporate your branch soon.
Check it out and let me know.

@twskj The required star works well and the highlighting is a nice bonus. :+1:
Somehow, I can't get the comments on fields working. I saw a screenshot somewhere showing that it works, but no matter where I put description in my JSON, nothing happens. Could you show me a small example JSON?

It actually just put text in description field of object type like so:
"properties": {
    "id": {
        "type": "integer",
        "format": "int64",
        "description": "This is going to be a comment"
    },
    "name": {
        "type": "string",
        "example": "doggie"
    }
}

The generated html should contains your comment in schema
 "schema": "{\n   \"id\": \"int64\",     /* This is going to be a comment */\n   \"category\": {\n      \"id\": \"int64\",\n      \"name\": \"string\"\n   },\n   \"name\": \"string\",\n   \"photoUrls\": [\n      \"string\"\n   ],\n   \"tags\": [\n      {\n         \"id\": \"int64\",\n         \"name\": \"string\"\n      }\n   ],\n   \"status\": \"string\"     /* pet status in the store */\n}"


Add enhancement to allow RAG functionnality

What are you trying to do?
I want use a custom script on ollama server (windows) to execute Retrieval Augmented Generation (RAG) process. How can I do ?
(I have an example which is working with a python script, langchain and ollama but I can't do it behing the ollama server using api restful).
How should we solve this?
Allow Retrieval Augmented Generation (RAG)  or add an example
What is the impact of not solving this?
No response
Anything else?
No response

@g02200jeff When I need to do RAG using ollama I have always used a vector database and an embedding model (EX: nomic-embed-text:latest) on the embeddings endpoint to generate my embeddings and then search for the closest matching embedding.

Check out this: https://python.langchain.com/docs/integrations/llms/ollama/

@g02200jeff have a look at my little project, it is a RAG with ollama back-end: https://github.com/aosan/VaultChat

i am intrested too, without a way of scoring the output query against the input prompt it is really hard to determinate if the answer is any good, i would love to see ollama get more stuff like that.

I love the reliability and speed of Ollama. It would be great to add RAG support because it essentially creates an infinite context window size. This has limitations of speed and accuracy, but it's a great solution for the context window problem.

once i query the vector db for related embeddings, how do I call ollama api to use them in a query?


Dataset format

Could you please share the dataset format and how to preprocess dataset

This is the dataset_folder format

Face2Face

train

fake

000_003

00001.png
00002.png
...
00080.png

001_870

00001.png
00002.png
...
00080.png

real

000

00001.png
00002.png
...
00080.png

001

00001.png
00002.png
...
00080.png

val
test

FaceSwap
DeepFake
NeuralTextures
DFDC
DeepFakeDetection

val and test follows the same structure same as the train folder (but different data, obviously)
All other datasets also follows the same structures. [i.e, {train or test or val} --> {real or fake} --> {video_name} --> {image_name}]

Dataset Preprocessing
We first used FFmpeg to extract frames from videos. Then, we used MTCNN to detect, crop, and align faces inside the video frames. There can be some false positives, but we consider them as noise in the dataset.


Application functionality suggestions

Suggestion:

In the application settings on the Smartphone, add the "Always Horizontal" setting. This setting will make it always get a comfortable horizontal position when launching the application without changing the automatic screen position setting (this is often inconvenient)
In the Smartphone Application, add the ability to automatically connect after startup, without constant connection confirmation (at startup). For example, through the Selected Address.
Thanks

In the Smartphone Application, add the ability to automatically connect after startup, without constant connection confirmation (at startup). For example, through the Selected Address.
Thanks

This feature is already implemented. You can enable this in the device's settings in the devices tab.

But on a smartphone, when you start the program, it constantly asks you to enter the ip of the computer

In the Smartphone Application, add the ability to automatically connect after startup, without constant connection confirmation (at startup). For example, through the Selected Address.
Thanks

This feature is already implemented. You can enable this in the device's settings in the devices tab.

But on a smartphone, when you start the program, it constantly asks you to enter the ip of the computer


Active Effects on items do not work

While effects can be added to an item, they do not apply to the character, regardless of whether or not the item is equipped.

Active effects on an item are copied into the actor when the item is dropped into the sheet. Because the active effects are copied only at that moment adding active effects to the item after it was dropped doesn't do anything. The experience is not quite that smooth so I do have a desire to change this behavior down the line. I'll keep this ticket to keep track of when I eventually get to tackle this.


Model update error : Cannot unbind $this of closure using $this

Laravel Version: 8.62.0
PHP Version: 8.0.3
Database Driver & Version: mysqli

Description:
My code was working properly before, But recently it shows this error in some parts of the website. Cannot unbind $this of closure using $this. When I checked the stack trace it's showing inside Laravel Framework.

This is my code from where the Error is Occurring.
class SubscriptionService
{
    public static function upgradeToLeader(Member|Authenticatable $member, Package $package, string $preferredMeetingType = null)
    {
        $member->syncRoles($package->role);

        /*** Error is showing in the following Line ***/
        $member->update(['preferred_meeting_type' => $preferredMeetingType ?? null]);

        event(new Upgraded($member, $package));
    }
}

Stack Trace for error in SubscriptionService.php

@nunomaduro I tried upgrading to the latest version. The problem still exists.

I see. What's the code within MemberController?

@nunomaduro : This is how MemberController looks like

I understand. But on what part of your code are dispatching a job? Or using the serializable closure package? It's kind of hard of us to identify the underlying issue if we can't reproduce the issue in our side.

Got this error again from another page. Currently, it is showing through Laravel Cashier.  Providing complete stack trace below.

I also don't know the complete steps to reproduce the error.
class Member extends Authenticatable
{
    use HasApiTokens, HasFactory, HasRoles, Notifiable, Billable, SubscriptionsSync;

    protected $guarded = [];

    protected $appends = ['name'];

    protected static function booted()
    {
        static::updated(queueable(function (Member $customer) {
            try {
                if ($customer->hasStripeId()) {
                    $customer->syncStripeCustomerDetails();
                }
            } catch (\Exception $e) {
                Log::error("STRIPE_CUSTOMER_UPDATE_ERROR :: MemberId : {$this->id}, Email : {$this->email}, Error : {$e->getMessage()}");
            }
        }));

        static::addGlobalScope('approved', function (Builder $builder) {
            $builder->whereNotNull('members.approved_at');
        });
    }

}

I have updated observer in my Member Model which is queueable.


Request for new device and feature updates

I'd like to call up or do a preset function, as in the Colorlight X16 or other X-Series controllers and the iSet program.
And I checked up to X16E port with nmap and found 21 (ftp Busybox ftpd), 80 (http Jetty), and 9999 (abys) were open.

I also need the same functionality.
Novastar has all the functions implemented in its companion, but there is no colorlight.

Can you add support for Z6 processor also?


Sending cards to devices when using API.AI

Is it possible to send cards to users devices when using the SDK? It looks like I can do it within API.AI itself, but can't find any references in the SDK docs.

Hi @ds8k, we just introduced visual components in Actions on Google at IO! You can use them now under the Actions on Google response tab in APIAI, or using the RichResponse builders you can now find in this sample! Check it out!


FIX: Test names of paths when calling path.iterdir()

Messed this up in #816 (008277f4522b466aa51fb5cfa80a607760d53cd3). Changing to a more descriptive iterator variable name.

Thanks for the quick review!


Logging issue

I find an anomaly when I query the dashboard.
For some reason the log does not display all the entries that are present in the MMDVMHost log file.
As you can see, there is some missing QSO.
Is there a "span" in terms of diration or in QSO entries ?
Here is the beginning of the log file (there is an hour difference with the one displayed by the dashboard):
M: 2021-12-25 23:04:54.745 DMR Slot 1, received network voice header from F5NHJ to TG 3022
M: 2021-12-25 23:04:54.773 DMR Slot 1, received network end of voice transmission from F5NHJ to TG 3022, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2021-12-25 23:04:57.995 DMR Slot 1, received network voice header from F5NHJ to TG 3022
M: 2021-12-25 23:05:05.777 DMR Slot 1, received network end of voice transmission from F5NHJ to TG 3022, 8.0 seconds, 0% packet loss, BER: 0.0%
M: 2021-12-25 23:24:06.841 DMR Slot 1, received network late entry from IT9ABK to TG 208
M: 2021-12-25 23:24:12.481 DMR Slot 1, network watchdog has expired, 6.2 seconds, 23% packet loss, BER: 0.0%
Here is the end of the log file as I write:
[pi@f5zjh /opt/Logs/MMDVMHost]$ sudo tail MMDVM.log
M: 2021-12-26 12:30:43.690 DMR Slot 2, received network voice header from F5JFA to TG 867
M: 2021-12-26 12:30:44.040 DMR Slot 2, received network end of voice transmission from F5JFA to TG 867, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-12-26 12:34:38.577 DMR Slot 1, received network voice header from FR4KM to TG 647
M: 2021-12-26 12:34:40.615 DMR Slot 1, received network end of voice transmission from FR4KM to TG 647, 2.6 seconds, 0% packet loss, BER: 8.2%
M: 2021-12-26 12:34:46.148 DMR Slot 1, received network voice header from FR4KM to TG 647
M: 2021-12-26 12:34:48.491 DMR Slot 1, received network end of voice transmission from FR4KM to TG 647, 3.0 seconds, 0% packet loss, BER: 7.7%
M: 2021-12-26 12:35:43.581 DMR Slot 2, received network voice header from F5JFA to TG 867
M: 2021-12-26 12:35:44.030 DMR Slot 2, received network end of voice transmission from F5JFA to TG 867, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-12-26 12:38:18.959 DMR Slot 1, received network voice header from FR4KM to TG 647
M: 2021-12-26 12:38:21.024 DMR Slot 1, received network end of voice transmission from FR4KM to TG 647, 2.6 seconds, 0% packet loss, BER: 14.5%
[pi@f5zjh /opt/Logs/MMDVMHost]$
Here is is the first QSO displayed

Here is the last QSO in the last page

There is a variable in config file defining the maximum lines of the logfile to tail.
This could be the issue.


Global Summit: Platform Sessions

@peterspdx is reaching out to Copia. Start fleshing out idea + adding list of potential participants here.

Here is the google doc for adding session ideas and fleshing them out: https://docs.google.com/a/creativecommons.org/document/d/1wM-kxMhGe1HeidZN70QT7syWrmnhaqBRyfyj4GMPXaY/edit?usp=sharing
@pgstacey @peterspdx @sarahpearson @ryanmerkley please add initial thoughts here as you think of them

Ideas copied and pasted to larger GS program brainstorming doc (see Jess' note). Will keep this doc for fleshing out details in future for now


licensing and IP

collect resources on licensing (law, choosing a license, how licenses affect IP)
cc @kaythaney who offered to help

some starter resources linked here:
https://github.com/cbahlai/OSRR_course/blob/master/09_open_licensing.md
On Tue, Mar 1, 2016 at 10:48 AM, Richard Smith-Unna <
<EMAIL_ADDRESS>wrote:

collect resources on licensing (law, choosing a license, how licenses
affect IP)
cc @kaythaney https://github.com/kaythaney who offered to help
—
Reply to this email directly or view it on GitHub
https://github.com/Blahah/intro_to_open_science/issues/2.

--
@kaythaney http://twitter.com/kaythaney/
@MozillaScience http://twitter.com/mozillascience


Fix compression_ratio function

The compression_ratio function calculates len(text) / len(zlib.compress(text.encode("utf-8"))), but len(text) returns the length of string while len(zlib.compress(text.encode("utf-8"))) returns the length of bytes.
Due to this discrepancy, when recognizing languages with multibyte characters, such as Japanese, compression_ratios are underestimated and more repetitions occur than in English, according to my experience. This PR fixes the issue by calculating text length in bytes.
As far as I experimented, this change made the default compression_ratio value (= 2.4) work better and improved recognition accuracy on my Japanese dataset. For English datasets, ASCII characters consist of a single byte, so the performance change due to this PR is expected to be almost negligible.
NOTE: This PR affects recognition accuracy mainly for languages with multibyte characters, so merging it should be with caution. I confirmed that it worked well on my private Japanese dataset, but performance may be degraded on other datasets.

Can confirm that the quality increase on Japanese datasets with this is night and day.
The main branch had a problem where it will get "stuck" and start generating large amounts of blank or empty output when it encountered something difficult to understand, making it mostly useless. This fixes that problem and massively increases quality.
Thank you to jumon for this.

Thanks. Can also confirm on my Japanese dataset, The subtitles has been improved a lot, and less repetitions occurring.

Thanks for reporting this!


ReferenceError: regeneratorRuntime is not defined

I'm getting the following error when trying to run the example script.
/btc20node_modules/@ledgerhq/hw-transport-node-hid/lib/TransportNodeHid.js:1
ReferenceError: regeneratorRuntime is not defined
    at /btc20/node_modules/@ledgerhq/hw-transport-node-hid/lib/TransportNodeHid.js:86:50
    at /btc20/node_modules/@ledgerhq/hw-transport-node-hid/lib/TransportNodeHid.js:125:6
    at Object.<anonymous> (/btc20/node_modules/@ledgerhq/hw-transport-node-hid/lib/TransportNodeHid.js:202:2)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)

Hey @kyledewy. Thank you for trying chainanstractionlayer!
This is because one of the dependencies is using old version of babel. We are tracking it here: https://github.com/LedgerHQ/ledgerjs/issues/211 & https://github.com/LedgerHQ/ledgerjs/issues/218
We also have fixed this issue in the next release of chainabstractionlayer. You can install it using npm i @liquality/chainabstractionlayer@next. Or, you can do npm install babel-runtime locally in your project.
Cheers!

We've just published 0.1.21 on npm with the fix. (npm i @liquality/chainabstractionlayer)


CEAEDFOCCT.SALOME version 9.8.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@ryfu-msft
2022-04-03 18:40:08.258   Message box (Abort/Retry/Ignore):
                          C:\SALOME-9.8.0\W64\qt\bin\linguist.exe

                          An error occurred while trying to copy a file:
                          There is not enough space on the disk.

I have realized that windows warns me that the publisher of the file is unknown, perhaps this is why it fails.
I think the executable is not signed.

I have realized that windows warns me that the publisher of the file is unknown, perhaps this is why it fails.

Azure Pipelines is running out of space when installing this so it cannot continue.

@wingetbot run


[Chips] Add on the spec the possibility of having a select & Update Chip-selected

The notion of a 'select' chip is missing from ZH spark. It should be added to know that it exists.
Ref: URL (storybook)

### Tasks
- [x] Update doc Figma & ZH
- [ ] Update component: Add possibility to have 1 clear icon & the arrow for select version
- [x] Update the outline color iso container (label)

Stand by
Version selection
The use of chips on Polaris may not be optimal. We need to find a solution together and then share it

Web
Possible to have a chip that opens a drawer or a popover to select a list
Android
Same as Web
iOS
N/A
Next step:

Remove this case on the storybook and Figma specs. It is not recommended to have 2 elements to avoid a11y issues.
No action required on the chip component (ticket done)
Communicating in Gathering


flake: remove unused lists, add ansible-lint

The runtimeDeps and buildDeps were empty and can be removed.
Add ansible-lint to the devDeps.

Running ansible-lint produces a lot of findings we might want to fix up, but that will have to wait for a subsequent PR.

Thanks for the polishing :)
Today I tried the nix setup locally and the ansible installation seems to be broken (it doesn't work on main either, so it's not caused by this PR). I have the exact same issue described in https://github.com/NixOS/nixpkgs/issues/223151, which offers a few workarounds. After some fiddling with the flake.nix file, I got the linter to work and saw indeed lots of suggestions to improve the yaml. The specific workaround I used was to add export LC_ALL="C.UTF-8" to the shellHook when creating the dev shell.
Based on the above, I have two questions:

With your nix experience, do you consider the LC_ALL export workaround acceptable? To my unexperienced eye it looks like a hack, but I didn't know how to apply the other workarounds suggested in the issue tracker. It would be nice to solve this (in a clean way, if possible, and otherwise with whatever works).
With your ansible experience, would you say it's a good idea to follow all the ansible-lint advice? If so, we could tell ansible-lint to autofix everything.

Cool, thanks for trying it out :-)

With your nix experience, do you consider the LC_ALL export workaround acceptable? To my unexperienced eye it looks like a hack, but I didn't know how to apply the other workarounds suggested in the issue tracker. It would be nice to solve this (in a clean way, if possible, and otherwise with whatever works).

I'm curious what your locale output looks like. Do you see the same Ansible failure if you use Ansible 2.15+ outside of the Flake? It seems like it might be a problem you would want to solve at the system level since it could break other software that's expecting a UTF-8 enabled locale. For ref, my locale output is:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

In either case I think having an export for it in the dev shell setup would be an OK workaround. I don't think it would have any negative long term effects and is easy to undo later.

With your ansible experience, would you say it's a good idea to follow all the ansible-lint advice? If so, we could tell ansible-lint to autofix everything.

I'm generally in favour of using linters and taking their advice. It makes for a more consistent experience, lightens review burden and can catch things more experienced people consider problematic patterns. I don't think it's super pressing but if the tool can auto-fix a bunch, maybe we should give it a go :-)

Under normal circumstances, my locale output is:
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

After nix develop, the output becomes:
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

So I'd assume this is nix related. If there is anything that rings a bell, I'd love to hear. Otherwise I can push a fix with the LC_ALL export.
Re ansible lint, I'll give a go at fixing everything :)

So I'd assume this is nix related

Aha, yes I agree. That's interesting. I haven't bumped into this myself.

Otherwise I can push a fix with the LC_ALL export.
 Thanks


Mount secret to provide server.cer and key

This PR could fix https://github.com/ManageIQ/manageiq-pods/issues/755
The issue is for running Manageiq on Kubernetes using Manageiq-pods and using the remote console functionality using webMKS to take over a console for VMWare.
This PR fixed one of the issue I encountered trying to get this functionality working.
Things that need fixing to get the console working:

WebMKS had to be included into the UI-worker POD. ManageIQ-Pod currently has no functionality for that. We use a customised Dockerfile for this.
There was an issue with the httpd config that was not forwarding traffic to the remote-console pod. See https://github.com/ManageIQ/manageiq-pods/pull/756
The remote console pod needs an additional certificate. This PR mounts a secret to address this.

The creation of the certificate is still a manual step
# Generate server.cer and server.cer.key for the remote console
openssl req -x509 -newkey rsa -days 1095 -keyout server.cer.key -out server.cer -subj "/CN=server" -nodes -batch

# Store it as a kubernetes secret
oc create secret tls server-tls-secret --cert=server.cer --key=server.cer.key

If the cert is missing from the pod and try to create a remote console this error is thrown
{"@timestamp":"2021-09-27T14:43:44.098759 ","hostname":"1-remote-console-6b4cdb569d-nkk6k","pid":9,"tid":"2aadbdaed9f0","level":"err","message":"RemoteConsole proxy for VM 69 errored with No such file or directory @ rb_sysopen - certs/server.cer /var/www/miq/vmdb/lib/remote_console/client_adapter/ssl_socket.rb:23:in `initialize'\n/var/www/miq/vmdb/lib/remote_console/client_adapter/ssl_socket.rb:23:in `open'\n/var/www/miq/vmdb/lib/remote_console/client_adapter/ssl_socket.rb:23:in `setup_ssl'\n/var/www/miq/vmdb/lib/remote_console/client_adapter/ssl_socket.rb:7:in `initialize'\n/var/www/miq/vmdb/lib/remote_console/client_adapter/web_mks.rb:9:in `initialize'\n/var/www/miq/vmdb/lib/remote_console/client_adapter.rb:11:in `new'\n/var/www/miq/vmdb/lib/remote_console/client_adapter.rb:11:in `new'\n/var/www/miq/vmdb/lib/remote_console/rack_server.rb:89:in `init_proxy'\n/var/www/miq/vmdb/lib/remote_console/rack_server.rb:63:in `call'\n/opt/manageiq/manageiq-gemset/gems/puma-4.3.7/lib/puma/configuration.rb:228:in `call'\n/opt/manageiq/manageiq-gemset/gems/puma-4.3.7/lib/puma/server.rb:713:in `handle_request'\n/opt/manageiq/manageiq-gemset/gems/puma-4.3.7/lib/puma/server.rb:472:in `process_client'\n/opt/manageiq/manageiq-gemset/gems/puma-4.3.7/lib/puma/server.rb:328:in `block in run'\n/opt/manageiq/manageiq-gemset/gems/puma-4.3.7/lib/puma/thread_pool.rb:134:in `block in spawn_thread'"}

Links

https://github.com/ManageIQ/manageiq-pods/issues/755
https://github.com/ManageIQ/manageiq-pods/pull/756

@bdunne Please review

@bdunne can you see if you solved this in a different way?


chore: update versions

Closing in favor of https://github.com/denoland/deno_website2/pull/1607

Oh I didn't see this. Sorry for the duplicate.


Remove *.ts files from src during publishing to npm

I got this errors during transpiling: Error TS6059: File '.../node_modules/ng2-page-scroll/src/ng2-page-scroll-instance.ts' is not under 'rootDir' '../client/app/'. 'rootDir' is expected to contain all source files. ... for every ts file.
This happens where .ts files are in node_modules folder. It's possible to not include this souce files during publishing to npm?

Hello @inzerceubytovani, I'm not sure what your process looks like, but usually you configure the typescript compiler to only compile/transpile your own source files, so adding node_modules folder to the exclude list may solve your problem. As the libraries usually contain transpiled versions of the typescript code there's not need for you to do so.

I use exclude node_modules, but that's same problem like here: https://github.com/ocombe/ng2-translate/issues/4

And also getting this error:
..node_modules/ng2-page-scroll/ng2-page-scroll.js:1 export * from './src/ng2-page-scroll.directive'; ^ ParseError: 'import' and 'export' may appear only with 'sourceType: module'
When I try to bundle project with browserify in gulp.

Your last error sounds like an ecma script versioning problem to me. You may find es5 umd modules in the /bundles/directory. All other *.js files are es6.


Update Ant Version

Automated Linux installer is downloading Ant 1.9.7, which is no longer available in the repository. Update script to download 1.9.8 instead.

Fixed


Doesn't support option "-sharedclassloader"

It doesn't support "-sharedclassloader" but only support option "-classloader". So can not put "-sharedclassloader" to ikvmc.
Could it be supported? Or I can achieve that by other ways.

Requires a (trivial) change in the plugin, not available indeed (though it's not really required when building a single jar, hence very linked to your other issue #13 )


feat: added necessary AS compiler to AS to make a AS transformer

Why add such much code ?

Because I copied the source files from the compiler.  Eventually the compiler will be broken up into more granular modules, but until then I just copied them here to compile to AS.

It seems that assemblyscript did not upload the as version of the compiler part of the code

@willemneal  Hi. In fact, I have not officially started this grant project, because assemblyscript does not seem to export the assemblyscript version of the compiler API.

@yjhmelody That's why I copied them here. You don't need the full compiler API just the AST and transform API.  We should schedule a time to talk in more depth about this.

@willemneal transform seems to currently only support nodejs. And I think the transform API really does not need to be done in an AST visitor library

@willemneal
Do you want to implement a pure AS version of transform? Why doesn't this wait for the official build-in?
I want to implement an as version of AST visitor alone, and there is no problem. But if we want to implement transform, we need to communicate more details, which is a bit unacceptable, and I think this should be implemented by the AS official, after all, the official has provided platform-independent Transform interfaces (like writeFile/readFile), but I seem to I do not see this piece of relevant progress.
And even if it really needs to be implemented, I personally think this can be completely split into 2 libs.

@yjhmelody The more I think about it you are correct.  We should move this work and make a PR to the main repo.  I will be available early tomorrow for me.  If you can find me on discord we can sync on the next steps.  Otherwise I'll write up my ideas tomorrow morning.

@willemneal  Well, I created a new repo https://github.com/yjhmelody/as-visitor


ticdc redo module isn't compatible with anonymous changefeeds

Before asking a question, make sure you have

[X] Searched existing Stack Overflow questions
[X] Googled your question
[X] Searched open and closed GitHub issues
[X] Read the documentation

What is your question?
Creating an anonymous changefeed:
./cdc cli --pd="http://pd-monitor:2379" changefeed create \
    --sink-uri="mysql://cdc@<IP_ADDRESS>:3306/test" \
    --config x.toml \
    --start-ts=$start_ts \
    --no-confirm --sort-engine=unified

Then display the changefeed:
$ ./cdc cli --pd http://pd-monitor:2379 changefeed list
[
  {
    "id": "2aafadf6-e28c-458c-a27c-eda6af20cd03",
    "summary": {
      "state": "normal",
      "tso":<PHONE_NUMBER>46265346,
      "checkpoint": "2022-07-05 13:58:57.176",
      "error": null
    }
  }
]

We can see the changefeed is assigned with an auto generated ID.
However, redo-log reader can't parse redo-log file name generated from the ID:
[2022/07/05 13:54:29.729 +08:00] [WARN] [file.go:186] ["check selected log file fail"] [logFile=cdc:8300_y_1656060584_row_434126366617370678.log] [error="bad log name: cdc:8300 y<PHONE_NUMBER> row<PHONE_NUMBER>17370678.log: expected integer"] [errorVerbose="expected integer\nbad log name: cdc:8300 y<PHONE_NUMBER> row<PHONE_NUMBER>17370678.log\ngithub.com/pingcap/tiflow/cdc/redo/common.ParseLogFileName\n\tgithub.com/pingcap/tiflow/cdc/redo/common/util.go:119\ngithub.com/pingcap/tiflow/cdc/redo/reader.shouldOpen\n\tgithub.co
m/pingcap/tiflow/cdc/redo/reader/file.go:353\ngithub.com/pingcap/tiflow/cdc/redo/reader.openSelectedFiles\n\tgithub.com/pingcap/tiflow/cdc/redo/reader/file.go:184\ngithub.c
om/pingcap/tiflow/cdc/redo/reader.newReader\n\tgithub.com/pingcap/tiflow/cdc/redo/reader/file.go:99\ngithub.com/pingcap/tiflow/cdc/redo/reader.(*LogReader).setUpDDLReader\n
\tgithub.com/pingcap/tiflow/cdc/redo/reader/reader.go:195\ngithub.com/pingcap/tiflow/cdc/redo/reader.(*LogReader).setUpReader\n\tgithub.com/pingcap/tiflow/cdc/redo/reader/r
eader.go:143\ngithub.com/pingcap/tiflow/cdc/redo/reader.(*LogReader).ResetReader\n\tgithub.com/pingcap/tiflow/cdc/redo/reader/reader.go:134\ngithub.com/pingcap/tiflow/pkg/a
pplier.(*RedoApplier).consumeLogs\n\tgithub.com/pingcap/tiflow/pkg/applier/redo.go:101\ngithub.com/pingcap/tiflow/pkg/applier.(*RedoApplier).Apply.func1\n\tgithub.com/pingc
ap/tiflow/pkg/applier/redo.go:223\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74\nruntime.goe
xit\n\truntime/asm_amd64.s:1571"]

/label bug

/label bug-from-internal-test

/label type/bug

/type bug

/remove

/type bug

@hicqu We can use /type bug to add a bug label 😊.


Added features like Myorder , Cart , Wishlist

I have add the features that I mentioned earlier like myorder , Cart  , Wishlist at navbar without diturbing any other features

@prvn-kumar01 mention the issue using a hashtag (#) so we can understand which issue your PR is referencing, and label your PR accordingly. Thank you!

share recording of your changes

and also update the sync fork.

@prvn-kumar01 mention the issue using a hashtag (#) so we can understand which issue your PR is referencing, and label your PR accordingly. Thank you!

Make sure when any user clicks on the cart or wishlist without logging in, an alert says "Please login first." Once the user successfully logs in, they can access the wishlist and cart buttons.

share recording of your changes

and also update the sync fork.

when any user clicks on the cart or wishlist without logging in, an alert says "Please login first." Once the user successfully logs in, they can access the wishlist and cart buttons.
I added above feature
https://github.com/user-attachments/assets/5aa6e7e3-898b-4794-8dc9-50cf9c2a7f42

@prvn-kumar01, instead of the above alert message, can you please make it so that the alert closes after 2 to 3 seconds?
https://github.com/user-attachments/assets/7d0ec717-bdd3-496c-9954-bb45c5576e5c

I will try
On Sun, 6 Oct, 2024, 1:49 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01, instead of the above
alert message, can you please make it so that the alert closes after 2 to 3
seconds? Checkout the demo video below for refernce.
https://github.com/user-attachments/assets/7d0ec717-bdd3-496c-9954-bb45c5576e5c
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395344430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW36ZJZDP3P2NWWX6RMPLZ2DXADAVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2DINBTGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

https://github.com/user-attachments/assets/415f5165-4dfa-4d81-a95e-c18712ea9f39
I  make it this alert only shows only for 2 seconds

@prvn-kumar01 add alert message here and it should be full red

According to our UI red not looks good
On Sun, 6 Oct, 2024, 2:06 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01 add alert message here
and it should be full red
39531502-D0A1-4DDC-8003-48B44D028576.png (view on web)
https://github.com/user-attachments/assets/5728bca5-d7c7-496a-94e1-eb26cc87b8a8
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395349568,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW366KNBNGRMHEA4NGYWLZ2DZB3AVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2DSNJWHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Its already looks nice
On Sun, 6 Oct, 2024, 2:19 pm Praveen Kumar, @.***>
wrote:

According to our UI red not looks good
On Sun, 6 Oct, 2024, 2:06 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01 add alert message here
and it should be full red
39531502-D0A1-4DDC-8003-48B44D028576.png (view on web)
https://github.com/user-attachments/assets/5728bca5-d7c7-496a-94e1-eb26cc87b8a8
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395349568,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW366KNBNGRMHEA4NGYWLZ2DZB3AVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2DSNJWHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@prvn-kumar01 insert this in down instead of top

Ok
On Sun, 6 Oct, 2024, 2:27 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01 insert this in down
instead of top
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395355390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW363YSDSWEQLWZBOWT43Z2D3N7AVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2TKMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Bro but at top visibility is higher than lower so top is best place
On Sun, 6 Oct, 2024, 2:33 pm Praveen Kumar, @.***>
wrote:

Ok
On Sun, 6 Oct, 2024, 2:27 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01 insert this in down
instead of top
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395355390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW363YSDSWEQLWZBOWT43Z2D3N7AVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2TKMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I done my all work .
On Sun, 6 Oct 2024 at 14:35, Praveen Kumar @.***>
wrote:

Bro but at top visibility is higher than lower so top is best place
On Sun, 6 Oct, 2024, 2:33 pm Praveen Kumar, @.***>
wrote:

Ok
On Sun, 6 Oct, 2024, 2:27 pm Md Azfar Alam, @.***>
wrote:

@prvn-kumar01 https://github.com/prvn-kumar01 insert this in down
instead of top
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/pull/223#issuecomment-2395355390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUW363YSDSWEQLWZBOWT43Z2D3N7AVCNFSM6AAAAABPOCEFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGM2TKMZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@prvn-kumar01 update your PR that's i can merge

I update sync fork

How can I update my PR?

hey @prvn-kumar01 the alert message were not seen in your deployment please check that's why i can merge your PR

ok I will check it

Can I create new pull request??
To solve this problem

Can I create new pull request?? To solve this problem

@prvn-kumar01 sure closing this PR for now


Unable to reload, must rebuild project after exception.

if you use the library, add a video to a view, and later introduce an error to the code, You cannot refresh the app, the second time you refresh the app, Xcode pops up on debug navigation bar. pointing to the error, and you have to rebuild the project - not just fix it JS then refresh.

I think I’m also experiencing something like this.
Sometimes I run the app from Xcode and then it gets stuck on a white screen (before my JS code is executed).
The only way I can seem to get it to run correctly again is by restarting the react native packager/server.
Is anybody else seeing this happen, or have any ideas on where to look to find out why this happens?


[FEATURE] Added primative widget for WireGuard

This commit brings along a very simple widget for the dashboard page
which displays all tunnels configured, their description, # of peers,
listening port, and traffic stats.
Will display info boxes if:

The service is not running
No tunnels are configured

This widget is a copy-pasta from the wg status code, but slimmed down
to not show peers and all the tunnel details.
Discussions should be had around what fields people care about as it
could easily be too "busy" for a widget.
Also this can be a starting point for adding actions into the widget
such as restarting tunnels, toggling peers, etc
Implements #119

Here are some screenshots demostrating the widget in various states:
Overview:

No tunnels configured, service up:

Service down:

Tunnel down:

tunnel up:


redistest: update for new location of go.freeport

Gah, how did I miss that?  Also, Travis still passed :P

Thanks for the fix. The old import paths redirect to the right place so it still works!:
# curl -vI https://github.com/ParsePlatform/go.freeport |& grep Location
< Location: https://github.com/facebookgo/freeport
Location: https://github.com/facebookgo/freeport
# curl -vI https://github.com/facebookgo/go.freeport |& grep Location
< Location: https://github.com/facebookgo/freeport
Location: https://github.com/facebookgo/freeport


Search should link to headline with text

... and possibly show it in the search results

Links to https://www.prisma.io/docs/more/faq

https://www.prisma.io/docs/more/faq#since-prisma-20-is-released-will-prisma-1-still-be-maintained would be much better link target.
Showing "Since Prisma 2.0 is released, will Prisma 1 still be maintained?" as the search result title would also be nice.

Yay that works.
Strangely enough "Prisma 1" does not return the same search results any more, although the page still mentions it as before.


Feature suggestion/idea: Separate documentation file.

Issue:
When documenting code with JsDoc it makes the js source code cluttered with comments that doesn't add to the codes functionality and makes the code harder to read & get an overview of (but it obviously adds greatly to the documentation of the code).
Solution:
To solve this, I suggest some kind of tag, that you put in the beginning that points to a dedicated documentation file.
Examples:
In the file: myCode.js you write a tag something like this(?) somewhere close to the top:
/** @documentation { ./someFolder/docFile.jsdoc } */

or:
/**
 * @documentation { ./someFolder/docFile.jsdoc }
 */

This redirects the jsdoc documentation reader thing, so it does NOT read from myCode.js anymore, but instead reads from docFile.jsdoc.
From then on when you for example make a new function, example: (in myCode.js )
function foo( bar ) {
   return false;
}

Then you can write the documentation in the docFile.jsdoc file, something like this:
/**
 * @function {foo}        - An example function
 * @param {string} bar - A string that does nothing
 * @return {false}         - Always return false for some reason
 */

And it will work just as any normal JsDoc documentation would work, but now you have clean JavaScript code in the .js file & clean JsDoc code in the .jsdoc file.
Disclaimer:

I'm kind of new to JsDoc so there might be missused tags & such, but try to look at what I mean to do instead of how I do it.
I don't know anything of how JsDoc works under the hood, so I don't know how hard this will be to make, that's part of why I write it here so people with experience can judge the difficulty.

Searched the whole interwebz for EXACT same solution, cause of EXACT the same reasons, as OP @sebbes333.
For pure JS projects, this would be god sent.
So, for me personally: 100 thumbs up, for this suggestion.
Maybe there are easier or better possibilities already out there, like Typescripft typedefs (d.ts), some good VS Code settings and JSDoc tags combined, or something along those lines. But at least i for myself not found them yet.
If someone knows a good and easy alternative to above suggestion (without studying 100 settings for 3 months, adding 8 files and 1000 lines of text, to gracefully solve that problem by the most  complex stuff ever mentioned) for that rather easy requirement, plz enlighten us.


Cannot download video

Writes: ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type youtube-dl -U to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
But i have last version

The same here for https://www.youtube.com/watch?v=GIjTLW7soBk
$ ▶ ./youtube-dl --version
2021.12.17

same here

I am joining. I have the same
deb-usr@debian-pc:~$ /snap/bin/youtube-dl --verbose https://youtu.be/q0hyYWKXF0Q
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://youtu.be/q0hyYWKXF0Q']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.6.9 (CPython) - Linux-5.10.0-19-amd64-x86_64-with-glibc2.25
[debug] exe versions: ffmpeg 3.4.11, ffprobe 3.4.11
[debug] Proxy map: {}
[youtube] q0hyYWKXF0Q: Downloading webpage
WARNING: [youtube] Unable to decode n-parameter: download likely to be throttled (Unhandled exception in decode; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output. Traceback (most recent call last):
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/extractor/youtube.py", line 1524, in _n_descramble
raise ExtractorError('Unhandled exception in decode')
youtube_dl.utils.ExtractorError: Unhandled exception in decode; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
)
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 816, in wrapper
return func(self, *args, **kwargs)
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/YoutubeDL.py", line 837, in __extract_info
ie_result = ie.extract(url)
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/extractor/youtube.py", line 1974, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
File "/snap/youtube-dl/4806/lib/python3.6/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output

#31530

I'm having same problem

Same issue. Any estimated time when can we expect an update?

Same issue. Any estimated time when can we expect an update?

Your best bet is to follow the other issue report https://github.com/ytdl-org/youtube-dl/issues/31530

To OP, as well as to all me, toos:
Have you followed the recommended procedure on opening a NEW ISSUE in this tracker? It's a PINNED issue:

i.e. #30839
Had you done that, you'd have performed a search for existing issues with the  ERROR
ERROR: Unable to extract uploader id
and (hopefully) you'd have found ca. 110 duplicate issues with the same/similar error message, plus links to the originating issue (now a megathread), with content and info on how to hopefully remedy your predicament...
BTW, the
WARNING: [youtube] Unable to decode n-parameter: download likely to be throttled
warning has also been taken care of in git-master...


Prepping servers fails due to syntax in ansible playbook

When running the command task ansible:prepare as per the Readme, it will throw an error:
ERROR! 'notify' is not a valid attribute for a Block

The error appears to be in '/home/<repo>/ansible/playbooks/cluster-prepare.yml': line 83, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

            enabled: true
    - name: System Configuration (2)
      ^ here
task: Failed to run task "ansible:prepare": exit status 4

This is caused by this line not being indented properly:
https://github.com/onedr0p/flux-cluster-template/blob/main/ansible/playbooks/cluster-prepare.yml#L136

What is the output of ansible --version ?
❯ ansible --version
ansible [core 2.14.3]
  config file = None
  configured module search path = ['/Users/devin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/Cellar/ansible/7.3.0/libexec/lib/python3.11/site-packages/ansible
  ansible collection location = /Users/devin/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.11.2 (main, Feb 16 2023, 02:55:59) [Clang 14.0.0 (clang-14<IP_ADDRESS>)] (/opt/homebrew/Cellar/ansible/7.3.0/libexec/bin/python3.11)
  jinja version = 3.1.2
  libyaml = True

ansible 2.10.8
  config file = None
  configured module search path = ['/home/vetrius/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]```

You have a pretty old version. Do not install Ansible from the official Ubuntu apt repo, instead install it via
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-ansible-on-ubuntu-22-04
or using pip

I am guessing that fixed it, closing this issue.


feat: support TypeScript #121

Alaska Airlines Pull Request
Fixes #121
Summary:
Automatically generate d.ts files so the icons can be imported in TS projects without errors or manual typings. This will also improve autocomplete for people not using TS.
Tested in a freshly-scaffolded open-wc component and the icons can be imported without errors.
Since we specify "main": "dist/index.js" in the package.json and the d.ts files are in the same folder, the types should be picked up automatically by consuming IDEs.
Type of change:

[x] New capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix build failing on windows

build.py would fail on Windows due to a couple of changes made in #2459 that assumed FilePath::StringType is always std::string and that FilePath::CharType is always char, which is not the case on Windows. So this commit fixes that.
The error report I got from running build.py:
> python script\build.py -c D
ninja: Entering directory `out\D'
[43/316] CXX obj\atom\browser\electron_lib.atom_browser_main_parts.obj
FAILED: ninja -t msvc -e environment.x86 -- "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64_x86\cl.exe" /nologo /showIncludes /FC @obj\atom\browser\electron_lib.atom_browser_main_parts.obj.rsp /c ..\..\atom\browser\atom_browser_main_parts.cc /Foobj\atom\browser\electron_lib.atom_browser_main_parts.obj /Fdobj\electron_lib.cc.pdb
c:\users\eran.t\documents\github\electron\atom\browser\atom_browser_main_parts.cc(31) : error C2440: 'initializing' : cannot convert from 'const char [11]' to 'const base::FilePath::CharType []'
        There is no context in which this conversion is possible
c:\users\eran.t\documents\github\electron\atom\browser\atom_browser_main_parts.cc(80) : error C2664: 'void brightray::BrowserContext::Initialize(const std::string &,bool)' : cannot convert argument 1 from 'const base::FilePath::StringType' to 'const std::string &'
        Reason: cannot convert from 'const base::FilePath::StringType' to 'const std::string'
        No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called
[43/316] CXX obj\atom\browser\api\electron_lib.atom_api_session.obj
ninja: build stopped: subcommand failed.

I think we should reconsider using a CI for Windows so we can catch issues like this faster. From what I understand the reason it's currently disabled is that building on appveyor takes over 30 minutes. appveyor states in their FAQ that if you purchase a "Pro" or "Premium" plan you'll get dedicated hardware with faster CPUs, SSD drives, 1 GB network uplink. So maybe we can contact them and see if we can try running the build on the stronger machines.

Thanks!

I think we should reconsider using a CI for Windows so we can catch issues like this faster. From what I understand the reason it's currently disabled is that building on appveyor takes over 30 minutes. appveyor states in their FAQ that if you purchase a "Pro" or "Premium" plan you'll get dedicated hardware with faster CPUs, SSD drives, 1 GB network uplink. So maybe we can contact them and see if we can try running the build on the stronger machines.

We have Windows CI running on GitHub's own server, but it does not test pushes by non-GitHubbers for security reasons, so for now I can only verify Electron builds on Windows when I push.
Also considering the super-bad performance of appveyor's free plan, it still won't be usable unless their Pro plan can get more than 10x faster. And since there is no mention of machine specifications on appveyor's website, I'm not even willing to have try (faster CPUs means nothing to me).

We have Windows CI running on GitHub's own server, but it does not test pushes by non-GitHubbers for security reasons, so for now I can only verify Electron builds on Windows when I push.

Is it possible to configure the internal CI to also run on merge?
That way code that was pushed by a non GitHubber, will still go through some form of automatic testing on Windows.

Is it possible to configure the internal CI to also run on merge?

When the PR is merged by a GitHubber the CI will also run it, because the merge commit is authored by the one who click the merge button.


[BUG] NoSuchElementException for email input field during login in system with single sign-on

Bug Report
EasyRepro Version

[ ] Microsoft Dynamics 365 Online Version 8.2 (8.2.x) (DB 8.2.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0 (9.0.x) (DB 9.0.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0.2 (9.0.2) (DB 9.0.2) online
[x] Microsoft Dynamics 365 Online Version 9.1 (9.1.x) (DB 9.1.x) online

UCI or Classic Web

[ ] UCI (XrmApp)
[x] Classic Web (XrmBrowser)

Online or On Premise

[x] Online
[ ] On Premise

Browser

[x] Chrome (v73)
[ ] Firefox
[ ] IE
[ ] Edge

Describe the bug
Upon running the test identified by Microsoft.Dynamics365.UIAutomation.Sample.Web.CreateAccount.WEBTestCreateNewAccount  following call xrmBrowser.LoginPage.Login(_xrmUri, _username, _password); (here) fails with the exception below as our system will auto-sign-in even in a Chrome incognito session.
OpenQA.Selenium.NoSuchElementException
  HResult=0x80131500
  Message=no such element: Unable to locate element: {"method":"xpath","selector":"//input[@type='email']"}
  (Session info: chrome=73.0.3683.86)
  (Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Windows NT 10.0.18363 x86_64)
  Source=WebDriver
  StackTrace:
   at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(String mechanism, String value)
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElementByXPath(String xpath)
   at OpenQA.Selenium.By.<>c__DisplayClass19_0.<XPath>b__0(ISearchContext context)
   at OpenQA.Selenium.By.FindElement(ISearchContext context)
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(By by)
   at Microsoft.Dynamics365.UIAutomation.Browser.SeleniumExtensions.<>c__DisplayClass45_0.<WaitUntilAvailable>b__0(IWebDriver d) in [redacted]\EasyRepro-develop\EasyRepro-develop\Microsoft.Dynamics365.UIAutomation.Browser\Extensions\SeleniumExtensions.cs:line 591
   at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition)

Code to reproduce
See this.
Expected behavior
The code should not throw an exception and continue on line 26.
Additional context
The configuration files has been updated to fit our system.
When logging out in Dynamics 365, closing the browser, opening the browser and going to the Dynamics 365 page again. I am automatically logged in. This is also the case in Chrome incognito.
I am using Chrome 73 because we did not have newer available that was also older than 77, which is the latest Chrome.WebDriver package available in Nuget.

Hi Vivian,
If you don't have to log-in, I guest you should remove this line from your test.
xrmBrowser.LoginPage.Login(_xrmUri, _username, _password);

Hi Angel,
When commenting that line out, the browser does not load D365 page at all. It opens the browser window but it is empty and then the test fails.

@VivianVoss - In the login sequence after inputting your organization URL, do you still get asked to enter an email and then redirect to an external ADFS provider? Or does it immediately redirect with no input requirements for email?
We may need to add a scenario to more properly handle login for this if there is no initial email prompt. In past experiences, generally a user was required to input their email address before O365 would direct to an external provider for realm identity.
Thanks,
Tyler

Hi Tyler,
No, there is no email asked before. It immediately logs in and redirects to the apps page, where after a bit the test fails, because it can't find a place to put email.
BR, Vivian

@VivianVoss - We've merged a change into the develop branch via #694 . Could you try testing out this new Login method and see if it accommodates your scenario? Based on the description of events, I believe it should.
We're in a holiday code freeze at the moment, but could get this change into the core releases/v9.1 branch by January 3rd, 2020 if you can confirm this works.

Hi Tyler,
When changing the Login statement to the one you provide above, the code behaves differently, but I am left with a new exception. The exception originates from this statement. It is looking for an XPath described as id(\"crmTopBar\") but this Top Bar element (unlike in our Dynamics 8.2 on-premise installation) does not exist, resulting in a Login page failed exception message after 60 seconds of waiting as specified by the TimeSpan in the statement. I have looked through the page source on our Dynamics 9.1 online installation and confirmed that it is indeed the case that no such crmTopBar element exists.
I am thinking your change is working as expected and this issue may be a different problem. Are you aware of 9.1 online not having an element with the ID crmTopBar?

Hi Tyler, any news on this?

Hi @VivianVoss,
Why you are trying to use the Classic Web (XrmBrowser) for 9.1 online? It is mandatory for you? If you use the UCI methods, it will call a different Login method that expect a different page: see it hier
See samples
When I try to open the Classic Web in my Trial Online Version this is not really the "Classic" one. It is more like UCI (Navigation, etc).  I think many other EasyRepro Logic will not work there.

Hi all,
I have just tried the tests again but with UCI and it seems to work fine. Thanks for the help :)


[6.4.x] DROOLS-1089 - flush reentrant working memory actions when eager evalu…

…ation is enforced - test case
closes #420
(cherry picked from commit 738d191d338dab3e8baceeaf6fe31556b81fe07f)

merged into 6.4.x


Merge Lazy, Lazy1, Lazy2

I think this was just dumbness on my part. I don't know why these can't be one class.

Isn't Lazy1 required for Alternative's some and maybe?

Yes, but we could just use Lazy (f a).

Hahah, right, yes! Oops.


Insert annotations at the correct position for arrays

@avenger2597 Make sure you merge the latest changes on master branch before resolving comments.


[Consensus] Non-blocking timestamp processing

Current state
Some pieces of our code today are dedicated to postponing the vote in case the timestamp of a proposal is "slightly" ahead of the local wall clock time. In this case a node is actually waiting until its wall clock time is getting to the point of a physical clock and sends the vote only after that.
The idea behind waiting prior to voting is to be able to guarantee that "if a block with timestamp T is committed there are at least f+1 honest validators with physical clock > T at the time of execution"
This guarantee makes it possible for VM to reason about time-based contracts: there is a reasonable upper bound on the timestamps of the transactions on chain.
The problem

The waiting approach is blocking the system, increasing latencies and reducing throughput.

A carefully crafted proposals with timestamps that are slightly ahead of the physical clock are going to slow down everything.
Even in the benign case with a slight clock skew we might see cases of some validators waiting before voting for the proposals.

There is a non-trivial amount of code dedicated to waiting in these cases, that might be gone.

Proposal
We can change the guarantee from:
"if a block with timestamp T is committed there are at least f+1 honest validators with physical clock > T at the time of execution",
to:
"if a block with timestamp T is committed there are at least f+1 honest validators with physical clock > T - delta at the time of execution",
Vote processing changes: if a proposal's timestamp is within the current wall clock + delta, then allowed to vote, otherwise not allowed to vote.
Proposal generation changes: if a parent's timestamp is within the current wall clock + delta, then propose with the parent's timestamp + 1us, otherwise do not propose.

Thanks for writing this. I see one attack with this approach:

At time t0, I propose a block for round 1 with timestamp = t0 + delta
Every honest validator votes for it, because delta is the maximum margin of error validators can accept
At round 2, the leader propose a block with timestamp = t1 < t0 + delta.
No honest node validator for it because the timestamp is not strictly increasing from the previous block.

What about a completely different approach: every validator includes a timestamp in their vote. The timestamp for a block is the average of all votes corrected against f potential fake timestamps (not sure how to do the last part).

@mimoo we need the timestamps to be signed and we want them to be identical so that we'll be able to generate the QCs / LedgerInfoWithSignatures / etc.
Note that a proposal must know about its parent (because it carries a QC to the parent), so the monotonically increasing timestamp requirement can never be violated.

A carefully crafted proposals with timestamps that are slightly ahead of the physical clock are going to slow down everything.

How is this different than sending proposals towards the end of the round?

Even in the benign case with a slight clock skew we might see cases of some validators waiting before voting for the proposals.

FWIW there's really no legitimate reason for validators to be more than a few milliseconds out of sync. Anything more than that is likely H/W issues which shouldn't strike many validators at the same time.
Anyways, this proposals basically boils down to having timestamps that lag behind real time. I don't feel super strongly either way (though it seems like a bit of a bummer to lose a more accurate timestamp). One thing I will point out -- as structured it seems like if nodes are honest the timestamps will generally be accurate But in byzantine cases the timestamp could be inaccurate by up to delta.
I think that's a bit risky because people might code assuming accurate timestamps. In a hypothetical contract that allowed you to bet on interest rates, imagine the fed announces at 9am. It'd be logical to close betting at exactly 9am. However really you'd need to close at 9am - delta because if a block commits 9:01 am it's possible that the "true" time is 9:01am - delta

@mimoo we need the timestamps to be signed and we want them to be identical so that we'll be able to generate the QCs / LedgerInfoWithSignatures / etc.

Note that a proposal must know about its parent (because it carries a QC to the parent), so the monotonically increasing timestamp requirement can never be violated.

I think that's a bit risky because people might code assuming accurate timestamps. In a hypothetical contract that allowed you to bet on interest rates, imagine the fed announces at 9am. It'd be logical to close betting at exactly 9am. However really you'd need to close at 9am - delta because if a block commits 9:01 am it's possible that the "true" time is 9:01am - delta

I might miss something but I think the very same problem would happen with the current approach as well: the proposal that is sent by a byzantine validator at 9am-delta can include a timestamp of 9am. As a result the rest of the validators would first wait for 9am and then execute the proposal. It's a matter of whether you "wait and execute", or you "pretend that you waited and execute right away" :).

I might miss something but I think the very same problem would happen with the current approach as well: the proposal that is sent by a byzantine validator at 9am-delta can include a timestamp of 9am. As a result the rest of the validators would first wait for 9am and then execute the proposal. It's a matter of whether you "wait and execute", or you "pretend that you waited and execute right away" :).

Because the smart contract would say:
if (now() < 9am) { /* allow bet */ }

It's OK if a byzantine validator can delay the commit of a transaction, it's not OK if it can, at 9:01 make a transaction appear to commit at 8:59.
(nb: yes, it is possible for a byzantine validator to have two parallel chains that commit conflicting events at 8:59, then at 9:01 decide the favorable chain to commit)

it's not OK if it can, at 9:01 make a transaction appear to commit at 8:59

you mean you wish it would not be OK, because it is the case in most cryptocurrencies.

Sorry, my bad on the ordering here. The issue is you can't make a transaction appear to happen at 9:01 until 9:01. A payment channel is a good example here -- if the dispute resolution period ends at 9:01 you can't make it come early.
One way we could potentially stop the clock from falling too far behind (i.e. from somebody proposing at 9:01 a block at 8:59) is to say that if you receive a proposal containing a time T that if T + (round timeout) > local_time() you ignore the proposal / timeout. In other words -- if T is the timestamp in the proposal and tmo is the round timeout, the validator will only vote on the block if the local time when it received the proposal is in the interval [T - tmo, T + tmo].
We could chose if, on top of that, we want to add the restriction "do not vote on a block until local_time > block timestamp". IMHO with Avery's new non-blocking processor suggestion such a condition wouldn't increase the range of things a byzantine validator can do (because they can always give you the proposal at the end of the round) and would be unlikely to cause local performance issues.

A payment channel is a good example here

I think payment channels get around that by having large periods of times for you to react.

One way we could potentially stop the clock from falling too far behind

I think this is very close to @dmitri-perelman proposition if I understand correctly? Which sounds like a fair design decision. You want to allow a margin of error around your local time.

Yup, the proposal is exactly about non-blocking execution of the proposals that fall within a delta of the wall-clock time and rejection of the others.
By the way, I think some of the confusion happens because we didn't specify the way a VM is reading time for its now() function (in @bmaurer example). Imho the easiest way to get deterministic execution is to use the timestamp field of a proposal. If this is indeed the case:

We need to update the code because today consensus is not passing the timestamp to the execution.
If a block timestamp determines the time for VM execution, then "wait and execute" policy doesn't make sense at all: indeed, what's the point of waiting for 20ms if the VM input doesn't change?

By the way, I think some of the confusion happens because we didn't specify the way a VM is reading time for its now() function (in @bmaurer example). Imho the easiest way to get deterministic execution is to use the timestamp field of a proposal. If this is indeed the case:

Agree that transactions proposed as part of a block B should appear to happen at the time B.timestamp, I think as part of the work @runtian-zhou is doing we could pass this timestamp to a "clock" smart contract that would update the clock at every block.

If a block timestamp determines the time for VM execution, then "wait and execute" policy doesn't make sense at all: indeed, what's the point of waiting for 20ms if the VM input doesn't change?

We could execute right away, we just wouldn't send the vote until the timestamp had passed. The benefit of this is that a QC for a block cannot be formed until at least f+1 honest nodes believe that B.timestamp has passed. Maybe it's a fair point that this isn't of much practical benefit to the user. Let's say a payment channel expires at time T. The round ends at time TMO, T < TMO. We are the proposer for this round and want to prevent a claim on the channel from coming in before time TMO.
We could make a proposal and set timestamp = TMO+1. In the current setup we'd wait until TMO+1 to vote on the block. However the proposer could just as well have waited until TMO+1 to make the proposal.
So if we take the approach where we discard blocks where B.timestamp > (RoundStart + RoundTimeout) we get the effect of discarding any block that we would have timed out under the original strategy. While it's possible that we will vote for a block that is slightly in the future relative to our local clock, a malicious proposer had a "lock" on that round anyways. I.e. they could have just as easily delayed their proposal and achieved the later timestamp. (n.b.: this is a slightly tighter bound than LocalNow() + RoundTimeout)

Exactly!

Ok, discussed it with @aching who is the current owner of timestamp processing.
@aching doesn't particularly like this idea because it might make it harder for the lightweight clients to reason about the transactions that have been committed given the client's local time (e.g., if a client knows its physical local time it t it might want to be sure that the timestamp of the latest committed transaction is less than t and not less than t+delta).
Reassigning the issue to @aching: feel free to close it!

@aching a client should never rely on its local timestamp for this.  It can only truly know if a transaction has been committed or omitted by querying the chain and seeing a committed timestamp on chain.  The client's local time should never be used for determining if a transaction has been committed - in fact, that is not an accurate way to determine a transaction commitment and would be misleading if we implied that to be the case

First of all, thanks to @dmitri-perelman for bringing this up.

The waiting approach is blocking the system, increasing latencies and reducing throughput.
A carefully crafted proposals with timestamps that are slightly ahead of the physical clock are going to slow down everything.
Even in the benign case with a slight clock skew we might see cases of some validators waiting before voting for the proposals.

This is equivalent to a malicious proposer that sends a proposal after a delay in the round.  In the worst case, it can simply not send a proposal at all, forcing a round timeout.
Slowing everything down if unfortunately an artifact of today's implementation.  We will be discussing an improvement in our message processing that would allow parallel message checking, timeout/vote processing, during the potential wait.
Additionally, it will be fairly easy to figure out if there is a large variance of clocks between validators and suggest that they fix it - the counters are in place for this.  Validators that have clock skew beyond a specific tolerance are considered malicious.
Finally, in testnet and other cluster deployments we have not observed any actual waits in the counters since message latency (~30ms) seems to exceed any clock skew between validators.

There is a non-trivial amount of code dedicated to waiting in these cases, that might be gone.

So even if we add a fixed delta to the property, unfortunately I don't think the code simplifies.  The checks would need to include the delta but would still exist.  If we add a variable delta (e.g. round timeout), delta is now bound to the round timeout that is supposed to increase faster than any skew that occurs during the round.  A variable delta will be harder to reason about for clients.  We can consider today's system to have a delta of 0.

Proposal
We can change the guarantee from:
"if a block with timestamp T is committed there are at least f+1 honest validators with physical clock > T at the time of execution",
to:
"if a block with timestamp T is committed there are at least f+1 honest validators with physical > clock > T - delta at the time of execution",

As mentioned above if delta = 0, they are equivalent.  We expect that clients can tell if they are close to the tail of the blockchain by checking the highest blockchain time against they own clock, adding more delta just introduces more uncertainty around that.  If delta is small it doesn't matter, but if delta was large (e.g. minutes or hours), this would make it harder for clients.
In summary, at this time I would prefer to avoid adding any delta != 0 that changes the property for clients without a tangible gain.

@aching a client should never rely on its local timestamp for this. It can only truly know if a transaction has been committed or omitted by querying the chain and seeing a committed timestamp on chain. The client's local time should never be used for determining if a transaction has been committed - in fact, that is not an accurate way to determine a transaction commitment and would be misleading if we implied that to be the case

@kphfb, I think something was lost in translation.  =) I agree with everything you wrote.  About client time syncing, I was saying that a client that syncs to a ledger info that contains a committed blockchain time can reason about how close the client is to the end of the blockchain based on a clock that is synced to the global time (e.g. its local clock) without worrying about a delta.    For instance if I believe my local clock is synced to the global time and I see a commit with a clock 100 ms in the past, I am within 100 ms of the blockchain global time.  If I add a delta of 10 seconds for instance, I am within 10.1 seconds of the blockchain global time.

Discussed with @kphfb and @dmitri-perelman and it makes sense to close this for now.


Bintray shut down

One of our developers cannot compile the project due to bintray sunsetting their services

We can move the project to our own repo while this is fixed, so no rush :)

ahhh i got an email about bin tray shutting down... i’ll see what i can do

i'll be using this, woop woop

new maven url: https://github.com/deanveloper/SkullCreator/raw/mvn-repo/


failed to add sidecars.networking.istio.io CRD

Bug description
I apply custom CRDs from helm template install/kubernetes/helm/istio-init --name istio-init --namespace istio-system; however, pod for job.batch/istio-init-crd-11-1.3.0 failed to create CRD sidecars.networking.istio.io.
I am running EKS 1.14 for the control plane and EKS 1.13 for the worker nodes.
 18:41:09  ~  istio-1.3.0  manifests  kubectl -n istio-system get all
NAME                                READY   STATUS             RESTARTS   AGE
pod/istio-init-crd-10-1.3.0-9fwkb   0/1     Completed          0          9m47s
pod/istio-init-crd-11-1.3.0-btk9p   0/1     CrashLoopBackOff   5          9m47s
pod/istio-init-crd-12-1.3.0-bfp96   0/1     Completed          0          9m47s

NAME                                COMPLETIONS   DURATION   AGE
job.batch/istio-init-crd-10-1.3.0   1/1           2s         9m47s
job.batch/istio-init-crd-11-1.3.0   0/1           9m47s      9m47s
job.batch/istio-init-crd-12-1.3.0   1/1           2s         9m47s

I can apply file /etc/istio/crd-11/crd-11.yaml that pod/istio-init-crd-11-1.3.0-btk9p manually without issues; however, I don't understand why pod/istio-init-crd-11-1.3.0-btk9p exited unsuccessfully.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
The pod for adding CRD sidecars.networking.istio.io should exit successfully.
Steps to reproduce the bug
helm template install/kubernetes/helm/istio-init --name istio-init --namespace istio-system|kubectl apply -f -

Version (include the output of istioctl version --remote and kubectl version)
 18:48:08  ~  istio-1.3.0  manifests  istioctl version
2019-09-13T18:48:14.211958Z	warn	will use `--remote=false` to retrieve version info due to `no Istio pods in namespace "istio-system"`
1.3.0
 19:00:14  ~  istio-1.3.0  manifests  kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-07T09:55:27Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6-eks-5047ed", GitCommit:"5047edce664593832e9b889e447ac75ab104f527", GitTreeState:"clean", BuildDate:"2019-08-21T22:32:40Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
With helm template and kubectl apply
Environment where bug was observed (cloud vendor, OS, etc)
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

Please add logs from the job. You can pass the -p flag to get the logs from the previous container so we can see why it crashed

Can you add logs?


MarkTextAsSpoken Issues

I am trying to get my text to be marked as spoken however even in the demo it doesn't always mark it. Could this be my device (Alienware x17 R2)?  In the demo, on this device only the EN-US voice works with MarkTextAsSpoken.
Below is the code that I am using. I am using JS.
     <TextToSpeech
                    markTextAsSpoken
                    rate={".9"}
                    lang="en-GB"
                    autoPlay>

How old are you?

                </TextToSpeech>

I would say yes, it is related to the combination of OS/Browser/Lang/Locale. What browser are you using? If you notice the Languages story includes the text under the select:

(Some voices may create skewed word boundaries for the given text.)

Also, if you check the first and second FAQ from the README, you will notice that they address potential issues with markTextAsSpoken, and that for some devices (particularly Android) it is impossible to mark the word boundaries due ot a lack of support from the OS. As an example, check out this chromium issue.
Finally, I've noticed that you've assigned the rate prop as a string, when the actual type is a number. Here is an example of the text being highlighted on macOS/Chrome with your sample code (rate switched to number):

Unfortunately, your only real solution is to find a suitable voice for your given spokenText, on your supported platform(s).


Events shouldn't trigger transitioning from one state to another?

Thanks for a such great framework.
It has been my goal to use a statechart on the frontend together with ExtJS and I finally found a good one.
However I have some questions about the design choice of this framework.
Having used Sproutore's statechart I wonder why each event by default is triggering a transitioning from one state to another? If I am in a let's say "loggedin" state I should be able to "createpost", "deletepost", "searchposts" etc without having to enter a new state. Maybe I only want a transition to the "loggedout" state on "logout" event.
Or am I missing something?

This is fixed in new master branch version 2.1.0
Both the 'from' and 'to' attributes are now optional.

If 'from' is missing (or is wildcard '*') then the event can be fired from any state
If 'to' is missing, then the event doesn't cause a transition (a no-op event)


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade" workflow

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-XK8ItpxnSow5
Commit ID: 9e68b79cef4865c8fc42fce43ce9698f8670f3c1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


vim9class: "return this" required for early return from constructor (inconsistent)

Steps to reproduce
Source the following
vim9script

class C
    this._bufnr: number

    def new(this._bufnr)
        if ! bufexists(this._bufnr)
            this._bufnr = -1
            return # comment this out and things work
        endif
    enddef
endclass

var o = C.new(1234)
echo typename(o)

Observe that the typename(o) is number
Expected behaviour
Comment out the return and
typename(o) is object<C>
The following works as expected, but feels inconsistent
    def new(this._bufnr): any
        if ! bufexists(this._bufnr)
            this._bufnr = -1
            return this
        endif
    enddef

Version of Vim
9.0.1333
Environment
ubuntu
Logs and stack traces
No response

Still fails with 9.0.1754
Looking at the failure modes, to get a feel for the importance. Discovered it behaves differently script level versus :def.
Using the same class definition as above. Declare the variable with a type (no type inference) and there's an error at the script level
var v1: C
v1 = C.new(1234)
echo typename(v1)

ERROR: E1012: Type mismatch; expected object<C> but got number
But put this in a :def and there is no compile or runtime error, instead the variable is silently given an impossible value for its declared type because of the bug in the generated constructor code.
def F()
    var v2: C
    v2 = C.new(1234)
    echo typename(v2)
enddef

F()

OUTPUT: number

About the workaround, should it be legal to specify a return type for a constructor?

I have created this PR to disallow specifying a return type for the new() constructor.  Please try this out and let me know if it solve these problems and whether you see any new issues.

It solves the problem, tried a few other cases. I'll install it locally; I'm doing a bunch of vim9class debugging for the new days.


Model values of CVC and Expiry aren't set

Implemented CC, CVC and Expiry fields.
<card-number-input name="number" ng-model="data.creditcard.number" card-type="data.creditcard.type" required></card-number-input>
 <card-expiry-input name="expiration" ng-model="data.creditcard.expiration" ></card-expiry-input>
 <card-cvc-input name="cvv2" ng-model="data.creditcard.cvv2"></card-cvc-input>
 data: {{data.creditcard}}

User enters the data and model results in:
{"type":"visa","number":"4111111111111111","expiration":{"month":12,"year":2018},"cvv2":"123"}
User saves the form, but decides later to edit the information. The model hasn't changed and looks exactly as above, however, neither the CVC nor the Expiry field show the model values.
I'd like all fields to show the data entered before.
What am I missing?
Thanks...

After digging further in, it looks like the $modelvalue is set, but the $viewValue is not when the page is revisited. Any pointers on what the cause could be?

I've got this issue also trying to fix 👍

+1


Tweak config_dump format for certs

Expose errors to /config_dump instead of via tracing
Use empty ca_cert lists instead of a list with dummy object for unavailable certificates (note: can also not have the field altotheget for non-available certs, not sure which is preferred)

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

Test name
Commit
Details
Required
Rerun command

test_ztunnel
0a2e5fa92e6abade81553574fb1fdb63bf23eb86
link
true
/test test

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


Add a proper test suite

This project started as a hack to get a minimal svg tooltip working with d3.  Nothing at the time existed that targeted SVG specifically.  Once it worked well enough for my needs, I documented it and through it up on GitHub.  Without a test suite.
Not having a proper test suite created a significant burden to accepting contributions since there was no baseline level checks to ensure that a contributions passed the most basic requirements before code review.  Having a test suite would give us confidence that changes we introduce would not break existing assumptions and also raise the quality bar for contributions.
This is pretty high on my personal priority list for this project.
/cc @vdh

A test suite is exactly what I had in mind too. I've had some experience before using the Mocha framework and istanbul for code coverage.
As for testing the actual DOM changes, I'm a bit green there, potentially something using jsdom to simulate the DOM. The more heavy-duty options I've seen out there are PhantomJS or Selenium to run the code within a headless browser/renderer. I've also seen some even-heavier-duty setups that just straight up run the unit tests on the local machine's Chrome browser (of course, I doubt that option would be able to run on CI servers).

I've been pretty happy with tape and jsdom, which is what d3 itself uses.  It's a pretty feature-light test suite that likely gives us all we need.  Here's some samples from d3-selection: https://github.com/d3/d3-selection/blob/master/test/select-test.js


Error while building for musl-x86_64

Hi.
I am trying to package abseil for Void Linux. On other glibc it builds as expected but on musl it throws this error.
I don't have much experience with C++ so any advice would be appreciated it.
If you have any questions about this, please feel free to ask. Thanks for reading this.

What compiler/standard are you using?

Hello. Very sorry for that including that in the issue.
The compiler is C++ and standard is 17.

Actually, I was using -DCMAKE_CXX_STANDARD=17 based on the AUR template (I don't know anything about c++) but I removed it and rebuilt and it succeeded on musl. Closing this. Thanks for pointing in the right direction.


boot nodes seems invalid now

Recentely, my hsc node fails connecting to P2P peers.
My guess is that the 3 boot nodes defined in the code are all dead.
Could the team kindly check it?

Recentely, my hsc node fails connecting to P2P peers.
My guess is that the 3 boot nodes defined in the code are all dead.
Could the team kindly check it?

https://github.com/hoosmartchain/hsc-enode-list


Conditionally remove BernoulliLogit

This PR prepares Turing for https://github.com/JuliaStats/Distributions.jl/pull/1623.

Bump :slightly_smiling_face:
All test failures should be unrelated.

This PR ensures that merging the Distributions PR does not break Turing (at least not the latest version). As long as one uses current and older versions of Distributions, BernoulliLogit is defined in Turing. But if it already exists since it is defined in Distributions, then we do not try to redefine it.


Gradient-reversal layer

I`d like to put here question from keras-users https://groups.google.com/forum/#!topic/keras-users/QWe3xAkuBOg

I'm wondering if and how the gradient reversal layer from the paper "Domain-Adversarial Training of Neural Networks" (http://arxiv.org/abs/1505.07818) can be implemented in Keras.

The "gradient reversal layer" as described there is a layer which passes input through unchanged, but during backpropagation multiplies all gradients by a constant (negative) factor.*
According to this answer https://groups.google.com/forum/#!topic/keras-users/FcbrlLY94ms

If you want to explicitly define your gradients you would probably be better off using Torch than using Keras/Theano.

it is not possible in Keras. Am I right?

It's possible in Keras. You'll have to skip using fit/predict and instead
define your own optimization procedure.
On 1 July 2016 at 07:43, Dmytro Mishkin<EMAIL_ADDRESS>wrote:

I`d like to put here question from keras-users
https://groups.google.com/forum/#!topic/keras-users/QWe3xAkuBOg
I'm wondering if and how the gradient reversal layer from the paper
"Domain-Adversarial Training of Neural Networks" (
http://arxiv.org/abs/1505.07818) can be implemented in Keras.
The "gradient reversal layer" as described there is a layer which passes
input through unchanged, but during backpropagation multiplies all
gradients by a constant (negative) factor.*
According to this answer
https://groups.google.com/forum/#!topic/keras-users/FcbrlLY94ms
If you want to explicitly define your gradients you would probably be
better off using Torch than using Keras/Theano.
it is not possible in Keras. Am I right?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/3119, or mute the thread
https://github.com/notifications/unsubscribe/AArWb3qsaquZj62-tKHzBxvI2p9Z7NqWks5qRSeagaJpZM4JDNLD
.

@fchollet sounds much harder, than defining "gradient reversal layer"

The following code works for me, though it might only compatible with theano backend.
import theano

class ReverseGradient(theano.Op):
    """ theano operation to reverse the gradients
    Introduced in http://arxiv.org/pdf/1409.7495.pdf
    """

    view_map = {0: [0]}

    __props__ = ('hp_lambda', )

    def __init__(self, hp_lambda):
        super(ReverseGradient, self).__init__()
        self.hp_lambda = hp_lambda

    def make_node(self, x):
        assert hasattr(self, '_props'), "Your version of theano is too old to support __props__."
        x = theano.tensor.as_tensor_variable(x)
        return theano.Apply(self, [x], [x.type()])

    def perform(self, node, inputs, output_storage):
        xin, = inputs
        xout, = output_storage
        xout[0] = xin

    def grad(self, input, output_gradients):
        return [-self.hp_lambda * output_gradients[0]]

    def infer_shape(self, node, i0_shapes):
        return i0_shapes

class GradientReversalLayer(Layer):
    """ Reverse a gradient
    <feedforward> return input x
    <backward> return -lambda * delta
    """
    def __init__(self, hp_lambda, **kwargs):
        super(GradientReversalLayer, self).__init__(**kwargs)
        self.hp_lambda = hp_lambda
        self.gr_op = ReverseGradient(self.hp_lambda)

    def build(self, input_shape):
        self.trainable_weights = []

    def call(self, x, mask=None):
        return self.gr_op(x)

    def get_output_shape_for(self, input_shape):
        return input_shape

    def get_config(self):
        config = {"name": self.__class__.__name__,
                         "lambda": self.hp_lambda}
        base_config = super(GradientReversalLayer, self).get_config()
        return dict(list(base_config.items()) + list(config.items()))

@yusuke0519 Thank you very much, I will try!

@ducha-aiki Did this work for you?

@VanushVaswani yes, it does.

@ducha-aiki Thanks. Are you using it for domain adaptation?

@VanushVaswani no, for different task.

@yusuke0519 what do you pass as an argument to the layer? i.e. what is hp_lambda when the layer is placed in a keras model?