Language Status popup commands/links stop working after an update is received and it shows outdated text (until it's closed/re-shown)

Does this issue occur when all extensions are disabled?: Yes (but you need an extension like the C/C++ extension that updates the language status info).

VS Code Version: Version: 1.89.0-insider (user setup)
Commit: ed6c6d3f28fa4cb66f6d73918365e41fb81db14c
Date: 2024-04-08T05:50:44.055Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631

Steps to Reproduce:

Hover or click on the language status icon for a language extension like C/C++.
Click a command in the language status that causes a status change like a Rescan.

Bug1: See the screenshot -- the main status bar updates its busy state correctly but the popup status UI doesn't refresh until it's made hidden/visible again, i.e. the top screenshot shows a stale "complete" state and the bottom screenshot shows a stale "updating" state. This could confuse users who expect the popup to have updated info. This is a regression from an earlier version, not sure which.

Bug2 (more severe issue): Also, after an update for the language status is received, the commands/links in the UI stop working when clicked -- this appears to have the same root cause as bug 1, because it looks like the popup UI becomes readonly after the update. From the user's perspective (who may not visibly see any update change due to the tooltips being updated), it appears that the commands/links don't work when clicked, e.g. if the status tooltip showing parsing percentage progress updates from 1% to 100% every second then the "Pause" command/link may never work for the user due to all the updates making the command readonly.

Not sure who owns this popup, @mjbvz?

Please attach a minimal repro for the problem
If this is truly two bugs, file two separate issues please

@jrieken Can you clarify what you mean by "minimal repro"? Does the VS Code team have an existing sample that uses the LanguageStatusItem? I don't see any at https://github.com/microsoft/vscode-extension-samples ? Is a repro using the C/C++ extension sufficient?
It seemed to me like 2 symptoms that share the same root cause and very similar repro steps, so it didn't seem like creating a 2nd bug was a good idea. I'd say the "bug2" is the most important issue and if bug1 isn't fixed from the bug2 fix we could open a follow up issue?

@jrieken Are you able to use the repro code below? The code attempts to approximate what our C/C++ extension does, but I'm not sure if it's 100% equivalent or not, the exact details of what our extension does can be seen at https://github.com/microsoft/vscode-cpptools/blob/main/Extension/src/LanguageServer/ui.ts .
        let languageStatusItem: vscode.LanguageStatusItem; // put this in some global location
// ...
        languageStatusItem = vscode.languages.createLanguageStatusItem(`txt id`, [
            { scheme: 'file', language: 'plaintext' }
        ]);

        languageStatusItem.busy = true;
        languageStatusItem.name = "txt name";
        languageStatusItem.text = "txt text";
        languageStatusItem.command = {
            command: "",
            title: "New window",
            tooltip: Math.random().toString()
        };
        global.setInterval(() => {
            if (languageStatusItem.command) {
                languageStatusItem.command.command = "vscode.newWindow"; // this isn't getting invoked when clicked
                languageStatusItem.command.tooltip = Math.random().toString(); // this isn't getting updated

            }
        }, 1000);

@jrieken Actually, that code sample appears to be invalid, and it should be doing something like
            if (languageStatusItem.command) {
                let newCommand  = languageStatusItem.command;
                newCommand.command = "vscode.newWindow";
                newCommand.tooltip = Math.random().toString();
                languageStatusItem.command = newCommand;
            }

but then it causes the popup to disappear on update, which doesn't happen for our C/C++ extension, so we must be doing something different to cause the command to update but not have the popup disappear, but I'm not sure what yet.

@jrieken Okay, I figured out the repro requirement -- it requires > 1 LanguageStatusItem, otherwise the popup status will disappear.
        let languageStatusItem1: vscode.LanguageStatusItem; // put this in some global location
        let languageStatusItem2: vscode.LanguageStatusItem; // put this in some global location
// ...
        languageStatusItem1 = vscode.languages.createLanguageStatusItem(`txt id1`, [
            { scheme: 'file', language: 'plaintext' }
        ]);
        languageStatusItem1.busy = true;
        languageStatusItem1.name = "txt1 name";
        languageStatusItem1.text = "txt1 text";
        languageStatusItem1.detail = "txt1 detail";
        languageStatusItem1.command = {
            command: "vscode.newWindow",
            title: "New window",
            tooltip: Math.random().toString()
        };
        languageStatusItem2 = vscode.languages.createLanguageStatusItem(`txt id2`, [
            { scheme: 'file', language: 'plaintext' }
        ]);
        languageStatusItem2.busy = true;
        languageStatusItem2.name = "txt2 name";
        languageStatusItem2.text = "txt2 text";
        languageStatusItem2.detail = "txt2 detail";
        languageStatusItem2.command = {
            command: "vscode.newWindow",
            title: "New window",
            tooltip: Math.random().toString()
        };
        global.setInterval(() => {
            if (languageStatusItem1.command) {
                let newCommand  = languageStatusItem1.command;
                newCommand.command = "vscode.newWindow";
                newCommand.tooltip = Math.random().toString();
                languageStatusItem1.command = newCommand;
            }
        }, 1000);


Change require to import

import 'bootstrap/dist/css/bootstrap.min.css';

Yes, I alse got ERROR in ./~/css-loader!./~/bootstrap/dist/css/bootstrap.css
But import return same error.

I found my problem.
I used node version 0.10.
https://github.com/webpack/css-loader/issues/144

Is this problem still persists? Sorry for the late reply here...

I later versions of node it is good - no problem.

👍


feat: add client support for detach subscription

closes #3122.
Behavior and tests verified in staging.

@jdpedrie You can try testing this in prod with the limited allow-list (keyed on subscription name.) The subscription name has to start with "testdetachsubsxyz". In addition, the project you're testing with needs to have the SUBSCRIPTION_DETACHMENT visibility label. If you can't get it working in prod, please contact me.


I just found this and wondering if I should start with V1 or V2?

Is V2 far enough along to start using it? is the Api the same?

We started v2, but it's never gonna see the light of day. In the near future, this package will be deprecated in favor of a new one: vue-data-component https://github.com/spatie/vue-data-component
v1 will still get bugfixes if necessary, but we won't be adding any more new features.


update merge annotation for rollouts apis

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

Ⅲ. Special notes for reviews

Codecov Report

Merging #173 (d065f4d) into master (76d33b8) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #173   +/-   ##
=======================================
  Coverage   43.87%   43.87%
=======================================
  Files          50       50
  Lines        5374     5374
=======================================
  Hits         2358     2358
  Misses       2618     2618
  Partials      398      398

Flag
Coverage Δ

unittests
43.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


When using the Transloco service with Angular 11.1 getting ref error, works fine in 11.0.1

I am not sure what other info I can provide as this is a large project.
but 100% if I switch back to 11.0.1 no issues and switching into the new 11.1 getting the following
using the popular package:
https://github.com/ngneat/transloco/issues/396
works fine in 11.0.1 but with 11.1 getting:

it is very odd is Transloco is loading fine with some modules and with others getting this error.
what other info can I provide?

Angular CLI: 11.1.0
Node: 10.15.0
OS: win32 x64

Angular: 11.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1101.0
@angular-devkit/build-angular      0.1100.7
@angular-devkit/core               8.3.29
@angular-devkit/schematics         8.3.29
@angular/cdk                       11.0.0
@angular/flex-layout               10.0.0-beta.32
@angular/google-maps               9.2.4
@angular/http                      7.2.16
@angular/material                  11.0.0
@angular/material-moment-adapter   11.0.0
@angular/pwa                       0.803.29
@schematics/angular                8.3.29
@schematics/update                 0.1101.0
rxjs                               6.6.2
typescript                         4.0.5

thanks,
Sean.

Closing as a duplicate of #19839 and #19852, being fixed in #19841.

Closing as a duplicate of #19839 and #19852, being fixed in #19841.


document relationship between method for determining a transit priority area and data processing

TPAs as defined in Senate Bill 743:

1/4 and/or 1/2 mile Buffer around high-frequency bus routes
Defined as half-mile buffer around the following geographies: Existing rail stations
Planned rail stations in an adopted RTP
Existing ferry terminals with bus or rail service
Planned ferry terminals with bus or rail service in an adopted RTP Intersection of at least two existing or planned bus   -  routes with headways of 15 minutes or better during both the morning and evening peak periods
Half-mile buffer around existing or planned fixed-route bus corridor with headway of 15 minutes or better during both   the -  morning and evening peak periods
Data Source: Regional Transit Database, 2016, Plan Bay Area 2017
Peak periods were defined as 6 AM to 10 AM and 3 PM to 7 PM
Bus stops had to meet the criterion for both AM and PM peaks
Average headway during the 4-hour window was used to identify achievement of 15 minute threshold
Bus stops have to be less than 0.2 miles in distance from one another (i.e., short walk to transfer)
Bus service had to originate from a single route (i.e., not combined headways of multiple routes)

copied from http://mtc.maps.arcgis.com/home/item.html?id=1188286d6b24418bbe57e573bfff00ee

apparently there are 2 laws definition the relevant distance from a transit corridor
1/4 mile here: http://www.leginfo.ca.gov/pub/11-12/bill/asm/ab_0901-0950/ab_904_bill_20120612_amended_sen_v94.html
and 1/2 mile here:
http://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201320140SB743
as such, we will need to output representations of both and/or either of these areas.

http://codes.findlaw.com/ca/public-resources-code/prc-sect-21064-3.html

mostly done as of https://github.com/MetropolitanTransportationCommission/RegionalTransitDatabase/commit/a7cf88601fc73c0eca69aa6b24f2be1a9be3f04a


Refactor/xferfcn.py

Just refactoring here.
When it s merged, I will answer issue https://github.com/python-control/python-control/issues/64.

Coverage decreased (-0.006%) to 78.218% when pulling 573191855ab74011c91769f768782309b0f66b94 on don4get:refactor/xferfcn.py into bcf538287b372e168a3e955cf2e8cbab76f8fb98 on python-control:master.

Coverage decreased (-0.006%) to 78.218% when pulling 573191855ab74011c91769f768782309b0f66b94 on don4get:refactor/xferfcn.py into bcf538287b372e168a3e955cf2e8cbab76f8fb98 on python-control:master.

Coverage decreased (-0.006%) to 78.218% when pulling 573191855ab74011c91769f768782309b0f66b94 on don4get:refactor/xferfcn.py into bcf538287b372e168a3e955cf2e8cbab76f8fb98 on python-control:master.

Coverage decreased (-0.006%) to 78.218% when pulling 573191855ab74011c91769f768782309b0f66b94 on don4get:refactor/xferfcn.py into bcf538287b372e168a3e955cf2e8cbab76f8fb98 on python-control:master.

Coverage decreased (-0.006%) to 78.218% when pulling 573191855ab74011c91769f768782309b0f66b94 on don4get:refactor/xferfcn.py into bcf538287b372e168a3e955cf2e8cbab76f8fb98 on python-control:master.


Use asynchronous request when reindexing

What did you do?
Reindexed a large index on AWS ES
What did you expect to happen?
Everything to work
What actually happened?

@Jalle19 FYI, I think the problem is not reindex itself, because it returns immediately https://www.elastic.co/guide/en/elasticsearch/client/curator/current/option_wfc.html#_link_linkend_reindex_reindex_link_2

@hungneox it definitely doesn't return immediately, at least not with the PHP SDK. We can make ES wait until the request completes, but the load balancer that sits in front of ES cannot be configured to allow for longer timeouts.

Fixed by https://github.com/digiaonline/lumen-elasticsearch/pull/72


invoices(), upcomingInvoice() and invoicesIncludingPending() return no data

Cashier Version: #.#.# 11
Laravel Version: #.#.# 7.x
PHP Version: #.#.# 7.4.5
Database Driver & Version: MySQL 8

Description:
Even though $loggedinUser is a Billable model and belongs to a user with an active (monthly) plan, calling invoicesIncludingPending(), upcomingInvoice() or invoices() on it returns no data.
            $loggedinUser = auth()->user();
            $upcomingInvoice = $loggedinUser->invoicesIncludingPending();
            $upcomingInvoice = $loggedinUser->upcomingInvoice();
            $upcomingInvoice = $loggedinUser->invoices();
            return response([
                "upcoming_invoice" => $upcomingInvoice,
            ], Response::HTTP_OK);

This is what I get back:
{
    "upcoming_invoice": [
        {}
    ]
}

Note that on the Stripe dashboard I do see an upcoming invoice 1 month from now: https://www.webpagescreenshot.info/#v2=572v2l6nG
What I am trying to do is get the amount the user will be charged at the next billing cycle (note that this may not be the same as the subscription plan's price the user is on - they may have a credit applied to their account, etc)

This is what I am trying to get done without relying on the Stripe library:
\Stripe\Stripe::setApiKey(env('STRIPE_SECRET'));
$customerId = $loggedinUser->asStripeCustomer()->id;
$upcomingInvoice = \Stripe\Invoice::upcoming(["customer" => $customerId]); // from https://stripe.com/docs/api/invoices/upcoming
return ['amount_due' => $upcomingInvoice->amount_due, 'invoice' => $upcomingInvoice];

I get all the invoices back. You're confusing the Invoice objects to be serializable to json or arrayable (which they aren't). You can't simply return them from a route or a response.

@driesvints thanks..Im not following the use-case. What is the right way to do it, if different from the code snippet?

The right way to do what?

@driesvints well I am following the documentation - what do you see wrong here?
            $loggedinUser = auth()->user();
            $upcomingInvoice = $loggedinUser->invoicesIncludingPending();
            $upcomingInvoice = $loggedinUser->upcomingInvoice();
            $upcomingInvoice = $loggedinUser->invoices();
            return response([
                "upcoming_invoice" => $upcomingInvoice,
            ], Response::HTTP_OK);

I've already explained above. Cashier's invoice object doesn't implements arrayable. You need the map the values you want to expose yourself.

Where do you see this in the docs?

@driesvints you are right, it's not exactly in the docs. I am going to try this again and report back..thanks.


Explicit build and deploy without using any triggers in BC & DC

/test arg1 arg2 arg3

This will fix wps#179 in web!


libbleu is support case sensitive or not by parameters?

I have read this libbleu code and found it is unsupported case sensitive or not sensitive. It is Inconvenient.

It's meant to be a very simple and fast BLEU implementation that operates over tensors. Case sensitivity would require knowledge of the underlying dictionary and tokenization, which would add a lot of overhead. You can use --sacrebleu for a more full featured (but slower) implementation.


[1.6] component.evidence is repeated in proto and object in jsonschema

Looks like this got missed somehow
I think it must be optional in the proto as well.
https://github.com/CycloneDX/specification/blob/master/schema/bom-1.6.proto#L136
https://github.com/CycloneDX/specification/blob/master/schema/bom-1.6.schema.json#L2079
Originally reported here

confirmed.
in ProtoBuf is it a repeated (optional) element: https://github.com/CycloneDX/specification/blob/55343ba19dee1785acf1ce9191540d5fd7b590db/schema/bom-1.6.proto#L135-L136
in JSON it is a single optional element: https://github.com/CycloneDX/specification/blob/55343ba19dee1785acf1ce9191540d5fd7b590db/schema/bom-1.6.schema.json#L1061-L1065
in XML ti is a single optional element: https://github.com/CycloneDX/specification/blob/55343ba19dee1785acf1ce9191540d5fd7b590db/schema/bom-1.6.xsd#L680-L684
i agree, there is a difference.

https://github.com/CycloneDX/specification/issues/272#issuecomment-1869972139

Actually, the defect is in the JSON and XML schemas. In this case, the protobuf is correct. Identity should be an array.

@stevespringett so we make the JSON/XML being a list?

@jkowalleck I thought only evidence.identity becomes an array, while evidence continued to be an object.

@jkowalleck I thought only evidence.identity becomes an array, while evidence continued to be an object.

i see.
proposed a PR to fix it: https://github.com/CycloneDX/specification/pull/425

fixed via https://github.com/CycloneDX/specification/pull/517

reopened.
we are currently  re-evaluating the protobuf BC detection -- #532
this leads to be opportunity to consider https://github.com/CycloneDX/specification/pull/425 a non-breaking change.
Which might lead to the opportunity to make the repeated field an optioanl field instead, as it was intended.


Fix ExportMap for a merged typescript namespace

Fixes a bug where not all of the declarations from multiple declare namespace copies would be merged together when the namespace was assigned as the export. I couldn't see any issue reported for this bug already.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.

Coverage increased (+0.8%) to 96.143% when pulling 6b81bd946074db94ca4e8adc07ea63e3d0d1a9a1 on benmunro:master into 5e143b23f3b89096e1b6a268af723f60c1ecb22f on benmosher:master.


Add Billy and Jolene to Our Team page

Billy is an accomplished photographer - maybe he'd be willing to take up that task for the individual and team shots.

Yes, already in discussion on this.
On Apr 5, 2015 8:20 AM, "Brian Nosek"<EMAIL_ADDRESS>wrote:

Billy is an accomplished photographer - maybe he'd be willing to take up
that task for the individual and team shots.
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/centerforopenscience.org/issues/337
.

Yep, already taken care of- working on adding staff and partners to the
page as well as top guidelines splash page.   Will be done /PR submitted
tomorrow or Tuesday
On Apr 5, 2015 8:23 AM, "Andrew Sallans"<EMAIL_ADDRESS>wrote:

Yes, already in discussion on this.
On Apr 5, 2015 8:20 AM, "Brian Nosek"<EMAIL_ADDRESS>wrote:

Billy is an accomplished photographer - maybe he'd be willing to take up
that task for the individual and team shots.
—
Reply to this email directly or view it on GitHub
<
https://github.com/CenterForOpenScience/centerforopenscience.org/issues/337
.

—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/centerforopenscience.org/issues/337#issuecomment-89757987
.

@erinspace can you close this one out? Thanks!

Sure thing!


Help with log format

Hi folks, I've tried modifying a few examples I've seen here to no avail.
Any help on the format for this? Thanks!
EDIT:
Actually it seems like if I grep for a single IP and output it to a new file, it works with just the standard log format, so it seems any hostnames as the client source will break this.
A. Is there any way around this?
B. If not, how might I go about telling Apache to only log IP, not name.

Are you resolve the IPs to hostnames? Are you able to change that? goaccess currently requires a valid IP

I figured that part out. Well, kinda. It wasn't set to resolve but it still was. A reboot fixed it, not sure what exactly was going on there.
I'm curious as to why hostnames won't work, is it just a matter of it being hard to account for all the different ways it could be formatted?

Originally was designed to validate those IPs and resolve them within goaccess, if you build from development, then a recent patch was added that could work in your case, please use the flag --no-ip-validation and let me know if that does the job for you.
$ git clone https://github.com/allinurl/goaccess.git
$ cd goaccess
$ autoreconf -fiv
$ ./configure --enable-utf8 --enable-geoip=legacy
$ make
# make install
# goaccess access.log --log-format=COMBINED --no-ip-validation

I'm fine without it, I'd prefer they not resolve as the user accesses the server anyway. I was just curious about reasoning. That's good to know, though, in case something changes.
Thanks for the info and the truly amazing program!


Schematic view naming

Allow custom naming of schematic view name as well as only using one value self.view to reference this name.

Adding value to schematic object called self.view that is setup in the init of the schematic creation. Changed all references to use this view variable.


An instance of NICE cannot be created

I can't create an instance of NICE in Python-3.9.12:
In [3]: NICE_explainer = NICE(optimization='sparsity')
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Input In [3], in <cell line: 1>()
----> 1 NICE_explainer = NICE(optimization='sparsity')

TypeError: __init__() missing 3 required positional arguments: 'predict_fn', 'X_train', and 'cat_feat'

Hi,
I fixed the example notebook in #5.
Best, Roman


Automatically enable the extension

if a user installs @playwright/test or if the users adds a playwright.config.ts

Folding into https://github.com/microsoft/playwright-vscode/issues/85


Track Resource Utilization of Robot

The Story
User should be able to monitor

CPU usage
Memory usage
GPU usage
Network load

of robot's components.
Parent Story

robolaunch/robolaunch#39
robolaunch/robolaunch#44

Migrated to https://github.com/robolaunch/robot-operator/milestone/9.


merge master into pipeline branch

pull in latest master code into pipeline branch

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Squash schema with prune

For the 1.0 release we plan to run squash the migrations so they are dumped to a single file. We also plan to use the --prune flag at this time to remove the individual migrations. This is to capture a single state for the 1.0 database structure. We don't expect there to be any DB rollbacks to prior versions.
For cases where a model's database structure needs to be viewed, the php artisan show:model {ModelName} command can be used instead. Relying on the migrations for this is error prone as many changes had been collecting up overtime and it would have required manually parsing the various updates to get the true sense.

When performing the schema squash will need to ensure that user is set to CURRENT_USER. See #1164


bug/fix resources

What does this implement/fix? Explain your changes.

Added new scan icon
Compressed existing resources
Replaced hardcoded Strings with placeholders
Added context to new Strings to be translated.

Any relevant logs, error output, etc?
...
Any other comments?
...
Where has this been tested?

Devices/Simulators:
Google Pixel 4
Google Pixel XL

OS Version:
Android 11
Android 10

I think everything is fine now. @ash-mega , can you take a look at it too?


Add a disclaimer

Hi, perhaps you may want to add a disclaimer to the web tool, something like "use it at your own risk"

Good idea.
I added the MIT license just now, but I think a disclaimer in the webpage itself is useful.
https://github.com/iancoleman/bip39/blob/master/LICENSE

The page itself contains a link to the license and the specific content of the license that concerns liability.
https://github.com/iancoleman/bip39/commit/1f618a7792e4b29bd06481239001e57a1aa58a37 - License details in More Info section


Accessibility Additions

Hi! Thanks for the theme - I've been adapting it for my purposes, and thought I'd share a couple of the changes I made for accessibility:
Added a skip link that is only visible to screen readers or when you tab to it
changes to baseof.html:

Skip to main content

            {{ block "header" . }}
                {{ partial "header.html" . }}
            {{ end }}

            {{ block "main" . }}{{ end }}

changes to styles.css:
a.skip-main {
    left:-999px;
    position:absolute;
    top:auto;
    width:1px;
    height:1px;
    overflow:hidden;
    z-index:-999;
}
a.skip-main:focus,
a.skip-main:active {
    left: auto;
    top: 0px;
    width: auto;
    height: auto;
    overflow:auto;
    z-index:999;
    padding: 4px 6px 4px 6px;
    color: #ffffff;
    text-decoration: underline;
    border: none;
    background: #871d6a;
}
main {
    outline:none;
}

(Look of focus and active varies based on theme; this is just what matches the changes I've made.)
Added lang to html for screen readers
changes to baseof.html:

I also made the links in the footer open in the same window, since opening links in a new window is less accessible, and made various changes to link styling (making hover/active links more visible and underlining all links so they are not just denoted by color). But those are more specific to a particular implementation of a theme.

@eladnarra
Thanks. Added these changes with link color changes according to default theme


[Bugfix] Set offer to draft if submission canceled

This fixes an issue where a submission with an offer, when cancelled, still leaves the offer state as consigned.
See this slack convo for more info.

Closing until there's a bit more definition.


Option to ignore database entries

I would like to request a feature to be able to ignore Stash database entries which already have metadata.
Currently database entries are overwritten if the metadata don't match. At least for the description this happens.
Two options would be the best:

Ignore database entries which already have metadata
Ignore database entries which have a Stash ID

Will resolve in 0.10


Add new chart tags infos

[x] Add new chart tags infos

Coverage increased (+0.0002%) to 99.602% when pulling ece62dd4b5a01f141c2253c21f51af4aeea198e8 on add_new_chart_tags_infos into 0ac22f5458fb655929c4dca8a0dd4bd658036cae on master.

Merging anyway, test failure is unrelated.


[Binance] Stop order automatically selects the wrong type

Add requirement to manually set stop order type.

your change will break currently working code
whats wrong with the current mapping?

Because order type calculation is wrong:
    if (so.getType().equals(Order.OrderType.BID)) {
      orderType = so.getLimitPrice() == null ? OrderType.TAKE_PROFIT : OrderType.TAKE_PROFIT_LIMIT;
    } else {
      orderType = so.getLimitPrice() == null ? OrderType.STOP_LOSS : OrderType.STOP_LOSS_LIMIT;
    }

The assumption that buy limit order always is take-profit limit order - is not true. The same is for sell.
If some code relies on it, it can be fixed by explicitly setting the needed type.

Ok, your right, the current implementation is just wrong.
But the way you are trying to fix it is also very hacky, you allow to much order flags and someone will by able to do a StopOrder with a MARKET + LIMIT flag monstrosity. Besides that, having a generic API that requires an exchange specific flag to work ruins the point of having a generic API. 99% of developer when they execute a 'placeStopOrder' expect a stop loss order to get placed - NOT a IllegalArgumentException or a Take Profit order.
The root of the current problem is laziness or lack of understanding that a take profit order is not a special type of stop loss order - its something opposite. Lets not continue this mistake.
Please add a new type of order to xchange-core - TakeProfitOrder - it will be very similar to StopOrder but do something opposite - this should be reflect in its javadocs. Afterwards add a
String placeTakeProfitOrder(TakeProfitOrder takeProfitOrder) throws IOException

method to TradeService and implement this feature in Binance in a proper manner by separating stop orders from take profit orders.

you allow to much order flags and someone will by able to do a StopOrder with a MARKET + LIMIT flag monstrosity

Agree, the combination of MARKET and LIMIT order doesn't make sense. Probably it causes exchange return an error, but anyway we have to reject such combination. Moreover we don't them at all, as soon
Binance expect only STOP_LOSS* and TAKE_PROFIT* flags for a stop order.

99% of developer when they execute a 'placeStopOrder' expect a stop loss order to get placed - NOT a IllegalArgumentException or a Take Profit order.

Stop order is not a synonym of stop-loss order. Stop-loss and take-profit orders are just some orders that are used to close a position. We can use a stop order to close position both by stop loss and take profit condition. It's may vary between different trading platforms, but at least it's valid in pure theory. The fact that Binance links stop order with exit condition, it's their internal interpretation of how stop order should look like, and I purpose to do not use this approach in a common interface.
How about these changes in PR:

Flags shouldn't have any of: MARKET or LIMIT
Flags should include one of: STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, and TAKE_PROFIT_LIMIT
On invalid flags combination - error should be raised and demand to set valid flag explicitly with a short explanation, why.

Flag validation in your proposition is just a way of managing a hacky solution. Our core API where possible should not allow to construct orders that do not make sense nor should it require some exchange-specific flags to work in any capacity. Adding validation does not fix bad API design.
I see your point on how you view Stop Order as a generic term that applies to both Stop loss order and Take profit order. Binances API suggests that. However on Bitmex this is a different order type: https://www.bitmex.com/api/explorer/#!/Order/Order_new
So I went to more general literature: https://www.investopedia.com/terms/s/stop-limitorder.asp
I see that a stop order has a simpel definition and the fact is it a 'stop loss' or 'take profit' is determined by the fact is your stop price higher or lower from the current price. However in the world of wildly changing prices of crypto I see that exchanges prefer that you state your intent explicitly.
Taking that into considerations my earlier proposal was also bad.
My new proposal would be to just add a new optional enum field to StopOrder:
public StopOrder extends Order {
    // ...
   public Intention intention;

   public static enum Intention {
     STOP_LOSS, TAKE_PROFIT;
   }
   // ...
}

The javadoc of this field should state that on some exchanges this field is required and if you want your code to work across many cross exchange then you should always set it.
What do you think of this approach?

Yes, it sounds reasonable.
So, using new enum for Binance, its order type will be made in that way:

STOP_LOSS: OrderType.MARKET + Intention.STOP_LOSS
STOP_LOSS_LIMIT: OrderType.LIMIT + Intention.STOP_LOSS
TAKE_PROFIT: OrderType.MARKET + Intention.TAKE_PROFIT
TAKE_PROFIT_LIMIT: OrderType.LIMIT + Intention.TAKE_PROFIT

Not exactly. In the solution I'm proposing you do not have to set any OrderFlags at all in StopOrder. The adaptation to a Binance order DTO would look like this:
switch (order.getIntention()) {
  case Intention.STOP_LOSS: return order.getLimitPrice() == null ? STOP_LOSS : STOP_LOSS_LIMIT;
  case Intention.TAKE_PROFIT: return order.getLimitPrice() == null ? TAKE_PROFIT : TAKE_PROFIT_LIMIT;


Create and publish new Patterns content on the website

Objective
We need to update the Cupcake website to reflect the patterns organization work outcome, so adopters can find what they need on the website properly.
Tasks

[ ] Lara to create new Patterns overview page content
[ ] Lara to create new Patterns guidelines for cards, lead space, in-page navigation
[ ] Jenny reviews pages
[ ] Wonile reviews and approves pages
[ ] Publish pages to the website
[ ] Update website IA

NOTE:

This is follow on work from this IA epic: https://github.com/carbon-design-system/ibm-dotcom-library-website/issues/497

Acceptance criteria

[ ] The website IA is updated and live on the website.
[ ] The patterns overview page content is updated and live on the website.
[ ] The 3 prioritized patterns pages (cards, lead space and in-page nav) are published and available to adopters.

@RobertaJHahn We completed the task goal and this Epic can be closed.


Added NodePath Hint to specify a list of acceptable Node Types

Added the ability to specify a list of valid types when exporting a NodePath (also works for CustomTypes)
This functionality was already working in VisualScript so I simply filled the gaps to make it work in GDScript, and C#.
By specifying a list of valid types the NodeSelector dialog will only allow selecting nodes of those types. Other nodes in the tree will still appear but will be disabled (grayed out.)
It has been tested to also work for NodePath Arrays in GDScript.
It is not working in C# for IEnumerable types though.
However it seems that export hints are never applied for C# IEnumerable types (it appears to be a bug and is not in the scope of this change.)
HOW IT WORKS:
In GDScript:
(Simply enumerate the type of the Nodes that can be selected)
export(NodePath, "Button", "CustomType") var nodepath
You are not forced to specfify any type. This still works:
export(NodePath) var nodepath
In C#:
[Export(PropertyHint.NodePathValidTypes,"Button,CustomType")] private Node2D nodepath;
(Notice that in C# the list of valid types must be encoded as a single String)
Some requests related to this change:

https://github.com/godotengine/godot/issues/7821 (Only the Type Restriction part)
https://github.com/godotengine/godot/issues/29912
https://godotengine.org/qa/33691/how-to-specify-exported-nodepath-type?show=33691#q33691
https://godotengine.org/qa/51552/export-custom-type-variable-on-inspector-mono-c%23?show=51552#q51552

This seems pretty useful, is it possible to use static references to the class though instead of strings?

It seems perfectly possible in GDScript.
Having a static reference to the class in C# doesn't seem trivial, because of the way Export Hints are defined in C#.
Also, because of the cross-language interoperability it may make a lot of sense to use strings (or at least to have both options).
The class may be defined in a different language, for example, and therefore not easily available as a Static Reference for the current language of the script.
I would suggest to include this implementation and possibly improve over it later to also support static references.
My reasons to suggest this are the following:

Apparently, having a static reference to the class name doesn't prevent the code from breaking if the class changes its name (Godot doesn't perform autorenaming. I'm I right?)
I don't think it brings much tipe-safety to the table since in the end it is still a NodePath we will be operating with. Therefore, lots of this functionality is still resolved at runtime.
It makes sense to have a common cross-language approach Strings based

so wait C# already has a type system are you saying we aren't going to be able to export custom node types?
what would be ideal would something like..
export(Sprite) var my_sprite
of course it would be a reference to a node not a node path but would allow you to choose existing nodes in the scene like a nodepath

C# is missing a few custom export modes so don't worry about this. At some point I'll have to implement them.

I dislike this string based implementation as in large projects it can become tedious to have to list a base type as a string and all of its inherited types, the way I am implementing it in a WIP PR that would fully resolve https://github.com/godotengine/godot-proposals/issues/1048 is passing any Script as its resource path to the scene_tree_editor and using get_base_script in the Script virtual object to find if the script's path matches any of its inherited types' paths

Hello @creikey
Some time has passed since I created this PR but as far as I can remember inherited types would be selectable without explicitly listing them.
I agree with you that the string approach is far from ideal but if you take a look at the code you will see that my main goal was:

introduce as few changes as possible
make this feature work the same across all languages
(Tested for Gdscript, C#, VisualScript)
Have this working as soon as possible (with the hope of improving it in future major releases)

@fejnartal The native type works when matching however scripts that extend from other scripts ( fairly common in bigger games ) are not recognized from the base script
e.x: adding "CustomClass" as an export hint in the nodepath assign dialog

Hi @creikey thank you for testing that and answering.
I will take a look and see if I can fix that with some minor changes.
The solution will still be based on strings I'm afraid.
My little experience in C++ and Godot Engine internals won't allow me to try a more sofisticated approach.
It would also need much more work and major changes to add stronger typesafety to all major supported languages.

Judging by the last screenshot in this article, exporting specific node types in NodePath will be possible in 4.0:

Thank you @Calinou
Yes, it seems so. And it looks great :D!
But apparently this is part of a major GDScript rewrite, so I guess this feature won't be available in C# nor VisualScript out of the box.
https://github.com/godotengine/godot-proposals/issues/828
I guess it won't hurt if I can try to add missing functionality identified by @creikey to this PullRequest since it may be a good starting point for other developments even if this proves to be insufficient or not as useful as I though it would be.

I currently don't have a proper development environment at hand. I will try to compile and test this change myself as soon as I have one.
But just in case any of you have the time and interest to try to test it yourself I have added a new check that may work for custom types' subclasses too as @creikey has suggested.
https://docs.godotengine.org/es/stable/classes/class_classdb.html#class-classdb-method-get-inheriters-from-class

The original repository has been deleted and there's another similar PR for that feature #39155, so I'll close this one.


Add markdown-lint-check GitHub action

This GitHub action checks all Markdown files in your repository for broken links. (Uses tcort/markdown-link-check)
For reference: https://github.com/gaurav-nelson/github-action-markdown-link-check

@pedrohyvo, I can't work on it at the moment. When I find some time I will help you.


docs: Add bonprix to Argo users

Checklist:

[x] My organization is added to USERS.md.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Oleg Borodai seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

You will need to sign off your commit. Please see:https://github.com/argoproj/argo/pull/4520/checks?check_run_id=1389989722

Done

Welcome!


Explore indexed.xyz for blockchain data

https://docs.indexed.xyz/examples/benthos_local_hasura
looks like you can stream the data from an S3 bucket

Related
https://docs.goldsky.com/mirror/sources/direct-indexing

Update on status: we made a team on Goldsky and are starting to plumb up a data pipeline!
We got a Jeff checking if it's easy for them to stream to GCS, which we can import into BigQuery

It would be nice to have this pipeline up with a dbt model to go from raw => what we currently export from Dune

Current status: shared access to Goldsky's service account, awaiting writes from them

Closing this out.


Incorrect folder size

code-server: 1.939-vsc1.33.1
os: Ubuntu 18.04
Issue: Size of folders under "Open Folder" is always 4096 MB
screenshot

Fixed by https://github.com/codercom/code-server/commit/446573809c686401cf65cb6bd399ba8353c572f0.


Dependencies locked...

Hi,
When I install the dependencies, it throw the following errors:
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run composer update or composer update <package name>.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- shahradelahi/easy-http is locked to version v1.3.0 and an update of this package was not requested.
- shahradelahi/easy-http v1.3.0 requires ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension.
Problem 2
- utilities-php/auth is locked to version dev-master and an update of this package was not requested.
- utilities-php/auth dev-master requires ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension.
Problem 3
- utilities-php/common is locked to version dev-master and an update of this package was not requested.
- utilities-php/common dev-master requires ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension.
Problem 4
- shahradelahi/easy-http v1.3.0 requires ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension.
- telegram-bot-php/core v1.0.2 requires shahradelahi/easy-http ~v1.3.0 -> satisfiable by shahradelahi/easy-http[v1.3.0].
- telegram-bot-php/core is locked to version v1.0.2 and an update of this package was not requested.

Hi,
It seems that you have not installed/enable the pcntl extension on your system.
For the telegram-bot-php/core package, I updated the dependencies, so you can update the project.
If this solution does not work, please provide more information about your system.


chore: add a GHA to regenerate documentation incase its forgotten

Will generate a PR on this repo if a change is merged without the docs being regenerated - should help us keep in sync.

fixes #15


Autofill search

Have recommended searches based on letters typed in search bar

Decided not to do this. Couldn't delete issue :(


Update CODEOWNERS

Description of the Change
@humb1t removal from code owners.

Benefits
No blocking questions or comments

Possible Drawbacks

Usage Examples or Tests [optional]

Alternate Designs [optional]

Yeah, this messages about repolinter was a bit tiring 😢.
Should we add you to reviewing prs? Your comments were always just on point and you gave another angle to code in review.

@i1i1 sry, forget to sign commit - please look at #891
You totally welcome to request review if you need another point of view. I just don't feel that I'm on the same page with all decisions are going on with Iroha - that's why I made a decision to retreat from maintainers.


Removing top 3 crime type statistic

I ended up removing these 3 card statistic when I was updating the new layout too in PR#50. So, i'm just going to link it to that PR


Sail command is falling under "error occurred mounting one of your file systems"

Sail Version: 1.0.1
Laravel Version: ^8.54
PHP Version: ^7.3|^8.0
OS: Windows 11

Description:
I can't run any sail commend, I always get the same error.
An error occurred mounting one of your file systems. Please run 'dmesg' for more details.
I have even tried to create a new project by running
curl -s https://laravel.build/example-app | bash
and still the same issue

Does anyone know what could be the issue ?? I do have docker installed with WSL2.
It's the first time for me that I use Sail so I didn't test it on my machine before.
the only change I made on my docker a couple of days ago was 👇  .
https://blog.codetitans.pl/post/howto-docker-over-wsl2-location/
not sure if that is why it's not working now. you guys might have a bug that will happen when the wsl2 location got changed.
also, you might need to check
https://superuser.com/questions/1682777/win-11-wsl-2-an-error-occurred-mounting-one-of-your-file-systems-dmesg-er
not sure if it's related but the first answer did mention the location.
also, docker is working fine for me, I'm using it with my visual studio .net core project and all good
any though?
thanks 🙌

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Expose http endpoint details

I’m building an infrastructure that uses service discovery to find metrics.  Now, I find it very tedious to set ports by hand so I prefer to listen on port 0 and then use service discovery to tell prometheus about it:
>>> from BaseHTTPServer import HTTPServer
>>> h = HTTPServer(("", 0), None)
>>> h.server_port
57782
>>> h.server_name
'alpha-2.local'

Currently there’s no way to achieve that using client_python.  It would be super helpful if you’d expose httpd from https://github.com/prometheus/client_python/blob/master/prometheus_client/exposition.py#L64 .
As a bonus point, this also solves the multiple processes problem from #30 in a more prometheus-like way I find: just expose multiple metrics and let prometheus figure it out.

From a manageability standpoint, I'd advise against this. You want you cluster manager to be assigning ports so that it can do healthchecking, graceful shutdown and longer term network QoS based on port numbers.

Agreed; I’m gonna claim that most of your users don’t have a cluster manager. :)  Also maybe I misunderstand, but I’m solely talking about the metrics endpoint.  Not the application service port.

I'm unsure if I should support this, you can always implement your own variant of start_http_server. These are meant as starting points for the most common use cases.

Fair enough.  I’m closing then.

This isn't completely sufficient to solve this. Consider a gauge whose role is "last time X happened", when a process died that could go backwards.

True, but wouldn’t that something to solve using max() or something similar?  Sorry, I’m still at my Prometheus beginnings. :)

True, but wouldn’t that something to solve using max() or something similar? Sorry, I’m still at my Prometheus beginnings. :)

The problem is that once the process isn't there anymore, Prometheus will stop scraping it and the value it has will go stale so the max won't see it.

That depends on the approach tho, right?
Because the way I do it, is to use consul, and register the workers’ metrics endpoints a service_id like metrics.dyndns.1, with 1 being uwsgi.get_worker_id().  Then I use relabel to get to job_id=dyndns, worker_id=1.
Therefore unless I scale down, there’s always metrics with those worker ids.
Am I missing something?

The problem is the scaling down, or if any worker gets restarted.

Hm how does restarting affect anything?  Assuming they re-register on start?

They no longer have the latest time whatever event happened, as that's all stored in memory.
The challenge is to make a unicorned app have the same semantics metric wise as a threaded one.

Ah, I get it now.  For them, the last moment it happened is “never” after start.  Still feels like something that could be figured out within Prometheus (dropping 0 or something?).
Anyhow, thanks for your time!

Still feels like something that could be figured out within Prometheus (dropping 0 or something?).

It's possible, but it's heading very much into advanced topics that something simple like this shouldn't require.

Yeah totally.  I’m just in love with Prometheus’ philosophy of keeping the client side as simple as possible so I’m exploring my options.


Feature/routes

Added recipe and user routes. Updated index.js for routes folder.

No review is needed, fixed code from the deleted branch.

Pushed to wrong branch. Will reopen a pull request for the dev branch.


SailBugfix: Filter out SIE with MIDELEG bits and provide visibility f…

…or userspace interrupt delegation
Our implementation in Miralis overlooks two points. First, we should also check if the MIDELEG bit is set. Second, the official specification allows the software to read the bits for user interrupt delegation.

So this is another case of user-level interrupt, I will close the PR as I think it will get solved by disabling user-level interrupts, but we can re-open it if that is not the case.


defaults and defining demes

This takes a stab at a few of the things we've been discussing, including requiring that a non-empty list of epochs must be given for each deme, and that attributes like selfing_rate and cloning_rate are given in a dict of defaults at the graph and deme level.
Definitely a work in progress and will need some cleaning up or rethinking perhaps.

Thanks for the comments Graham! A bit of work to do on this still - will get to it in a day or two though

Hey @apragsdale, do you mind if I pick up this PR and move it forward? I'd really like to make this match the reference implementation in the spec repo, so we can push out an alpha release of demes-python ASAP.

Hey @apragsdale, do you mind if I pick up this PR and move it forward? I'd really like to make this match the reference implementation in the spec repo, so we can push out an alpha release of demes-python ASAP.

Hey Graham- yes, go for it! I forget what sort of shape it’s in.. so I hope it’s not too bad.
On 14 Jan 2021, at 2:24, Graham Gower<EMAIL_ADDRESS>wrote:

Hey @apragsdalehttps://github.com/apragsdale, do you mind if I pick up this PR and move it forward? I'd really like to make this match the reference implementation in the spec repo, so we can push out an alpha release of demes-python ASAP.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/popsim-consortium/demes-python/pull/172#issuecomment-760014153, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIBL46VTTYNCVD2KSRXADOTSZ2S2VANCNFSM4UOB2X3A.

Hey Graham- yes, go for it! I forget what sort of shape it’s in.. so I hope it’s not too bad.
On 14 Jan 2021, at 2:24, Graham Gower<EMAIL_ADDRESS>wrote:

Hey @apragsdalehttps://github.com/apragsdale, do you mind if I pick up this PR and move it forward? I'd really like to make this match the reference implementation in the spec repo, so we can push out an alpha release of demes-python ASAP.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/popsim-consortium/demes-python/pull/172#issuecomment-760014153, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIBL46VTTYNCVD2KSRXADOTSZ2S2VANCNFSM4UOB2X3A.

Picking this back up - would be great to get a couple sets of eyes on this to make sure we're implementing it according to the specs that we've settled on.

Picking this back up - would be great to get a couple sets of eyes on this to make sure we're implementing it according to the specs that we've settled on.

I'm not really familiar enough with the existing code to give an informed review here I'm afraid @apragsdale. My take would be to get a version of this merged soon, and then add some more tests that would compare the results of the local parser here with that of the reference implementation across a range of inputs. That would give us good confidence the two are equivalent.
I think the docs build break is unrelated, probably something to do with the issue on PR builds from a while back. (So, nothing to worry about)

I'm not really familiar enough with the existing code to give an informed review here I'm afraid @apragsdale. My take would be to get a version of this merged soon, and then add some more tests that would compare the results of the local parser here with that of the reference implementation across a range of inputs. That would give us good confidence the two are equivalent.
I think the docs build break is unrelated, probably something to do with the issue on PR builds from a while back. (So, nothing to worry about)

Ok sounds good - I'll wait to see if @grahamgower notices anything obvious that needs fixing up, and then we can go forward with writing those tests to compare to the demes-spec.

Ok sounds good - I'll wait to see if @grahamgower notices anything obvious that needs fixing up, and then we can go forward with writing those tests to compare to the demes-spec.


Escape double quotes in string prompts

This fixes #382.
It checks if the answer type is string, and if it is, replaces " with \", so it can be parsed as valid JSON.

Can you add a test case for this?
You can reuse one of the tests and verify that the generated package json is correct by parsing it

I'm not home anymore, but I can do this tomorrow ;)
If I understood you correctly, the test should just verify that the
package.json is valid JSON?
Eduardo San Martin Morote<EMAIL_ADDRESS>schrieb am Mi., 8.
März 2017, 12:06:

Can you add a test case for this?
You can reuse one of the tests and verify that the generated package json
is correct by parsing it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/pull/388#issuecomment-285013064, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGmW1mhfIipGhuBJZ0PPNiHdfsHqKufrks5rjovQgaJpZM4MWozV
.

Yes, so that the double quotes are escaped correctly

Okay, I think that I should be able to do this :)
Eduardo San Martin Morote<EMAIL_ADDRESS>schrieb am Mi., 8.
März 2017, 12:12:

Yes, so that the double quotes are escaped correctly
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/pull/388#issuecomment-285014165, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGmW1u7SGg_c2hPFkMA8uBfdErK3GtGbks5rjo0jgaJpZM4MWozV
.

I just added a test to check the escaping. I tired to leave the other tests alone and add it seperately... May not be the best test, but it should do the trick 😄

LGTM 👍


virt-handler, hostdevice: Remove legacy support

What this PR does / why we need it:
The existing legacy hostdevice processing is broken [1] and untested.
A deprecation notice [2] has been sent with no objections from the
community.
Therefore, the relevant code is hereby removed.
[1] https://github.com/kubevirt/kubevirt/issues/6459
[2] https://groups.google.com/g/kubevirt-dev/c/xmZ8vx9-vME/m/w1Ywu4n3CAAJ
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
Support for legacy GPU definition is removed. Please see https://kubevirt.io/user-guide/virtual_machines/host-devices on how to define host-devices.

/cc @vladikr @rthallisey

change: Rebase

@vladikr @rthallisey, could you please update where we stand with this one?
I do not think the existing code can be used (i.e. it is dead code), or do I miss something?

The work on the dp side is making progress https://github.com/NVIDIA/kubevirt-gpu-device-plugin/pull/29

Looks good to me.
@jean-edouard @alicefr could you please have a brief look to make sure we are not missing anything?

looks good to me

Thanks!
/approve


utilization of GPU is lower

When I increased the training data to 1000 CT cases, the training of 4 12G 1080ti was normal, but the utilization of GPU would intermittently all be 0. The end result is more time consuming.
How can I adjust the code to increase the utilization of the GPU? thank you.

Hi @QianLingjun ,
Check if your data loading and preprocessing steps are optimized. Inefficient data handling can lead to bottleneck issues. Also, experiment with different batch sizes and check the GPU utilization. Sometimes, using a smaller or larger batch size can impact GPU utilization.


Handle strings in delete's limit field

Mongodb allows delete's limit parameter to be a string. I think that adding string handling in common.GetWholeNumberParam would be sufficient, although it's used for other operators like $size so the issue would require to find usages of the function and cover all of them with string tests. We should also unskip delete's ValidString test.

We should check if that's still a case with MongoDB 6 (#1083).


Error socket launch in Windows 8

In Windows 8, launching the app causes the following error with widgets_overview_app.py:

PS C:\tmp\remi-master> python .\examples\widgets_overview_app.py
remi.server      INFO     Started httpserver http://<IP_ADDRESS>:8081/
<IP_ADDRESS> - - [11/Jul/2018 15:12:19] "GET / HTTP/1.1" 200 -
remi.request     INFO     built UI (path=/)
remi.request     DEBUG    get: /
<IP_ADDRESS> - - [11/Jul/2018 15:12:19] "GET / HTTP/1.1" 200 -
cookie_to_cook: session=1531339939118
cookie_to_cook: session=1531339939118
found session id: session=1531339939118
found session id: session=1531339939118
remi.request     DEBUG    get: /res/style.css?7e7421c8fede27d23793172efe65d3d9
remi.request     DEBUG    get: /res/logo.png
<IP_ADDRESS> - - [11/Jul/2018 15:12:19] "GET /res/style.css?7e7421c8fede27d23793172efe65d3d9 HTTP/1.1" 200 -
<IP_ADDRESS> - - [11/Jul/2018 15:12:19] "GET /res/logo.png HTTP/1.1" 200 -
remi.request     ERROR    error processing GET request
Traceback (most recent call last):
File "C:\Python 3.5\lib\site-packages\remi-1.2-py3.5.egg\remi\server.py", line 813, in do_GET
self._process_all(path)
File "C:\Python 3.5\lib\site-packages\remi-1.2-py3.5.egg\remi\server.py", line 870, in _process_all
self.wfile.write(content)
File "C:\Python 3.5\lib\socket.py", line 589, in write
return self._sock.send(b)
ConnectionAbortedError: [Socket Error 10053 - An established connection was aborted by the software in your host machine.
cookie_to_cook: session=1531339939118
found session id: session=1531339939118
remi.request     DEBUG    get: /res/plus.png
<IP_ADDRESS> - - [11/Jul/2018 15:12:19] "GET /res/plus.png HTTP/1.1" 200 -
remi.server.ws   INFO     connection established: ('<IP_ADDRESS>', 36781)

For standalone app  crashes  with looping error "Socket Error 10053 - An established connection was aborted by the software in your host machine.".

@samtux does this problem happens only in standalone mode?

I see you started running widgets_overview_app.py. I can suppose that a firewall is blocking the connection. Is firewall enabled? Is python in firewall exceptions?

@dddomodossola With some of the examples that are not estandalone (widgets_overview_app.py), however the app works correctly in the browser. But for all standalone apps, it crashes showing the loader and the error loop  "Socket Error 10053 - An established connection was aborted by the software in your host machine.".

@dddomodossola  I've tried to disable the firewall before, but it still has the same errors. I don't know if this case is related with https://github.com/dddomodossola/remi/issues/217.

@dddomodossola I don't know if you know the following project to launch a standalone application https://github.com/flexxui/webruntime. I think that pywebview, gives some errors, and testing this webruntime module I have managed to launch the app correctly. The commands are very simple, you can choose for example different Browser Runtimes:
> from webruntime import FirefoxRuntime
> f = FirefoxRuntimeRuntime("C://tmp/icono.ico", title="Geocodificador de IDECA", size=(800,600), windowmode="normal")
> f.launch_app("http://<IP_ADDRESS>:8081")
> f.close()

@samtux thank you for the tip. However I think you can do the same directly opening a firefox subprocess with some parameters, this way you can avoid additional dependencies.

Personally, I like the idea of the desktop application "look and feel" without the user thinking it is a web application.  Additionally the possibility of packaging.
I really congratulate @dddomodossola on your project and see a great development alternative with the philosophy of a small library.

Thank you a lot @samtux.
Look at this for launching a firefix subprocess without the browser window https://developer.mozilla.org/en-US/Firefox/Headless_mode
;-)

Fixed in https://github.com/dddomodossola/remi/issues/217


Added: Split String

An algorithm that takes a string and a separator and returns all substrings before and after each separator
Related Issue

Issue No. #519

Proposed Changes

Added StringSplit.cpp

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[ ] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

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

Output Screenshots
|Example Input 1|

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here

Closing this pr!


feature request: snapshot pipeline data in pipelineRun for historical and repeatability purposes

Expected Behavior
When a PipelineRun is created and it expands the pipeline reference, it should include the complete copy of the pipeline yaml so that if the pipeline changes, a user can tell which actual pipeline the results came from.
Actual Behavior
No information is about the Pipeline is added in the PipelineRun
Steps to Reproduce the Problem

kubectl get "your-pipeline-run" -o yaml
will show the pipelineRun yaml with no information about the contents of the pipeline itself

Additional Info

same applied to task and taskRun

When a PipelineRun is created and it expands the pipeline reference, it should include the complete copy of the pipeline yaml so that if the pipeline changes, a user can tell which actual pipeline the results came from.

@pivotal-nader-ziada would this include also caching this Pipeline and using it in future reconcile loops? @tanner-bruce @mattmoor and @dwnusbaum were discussing this a bit in the slack chat, about wanting to make sure that changing a Pipeline midway through a run shouldn't affect runs in progress
(no worries if it makes more sense to tackle that separately)
Also @mattmoor 's suggestion about having a similar Revision model here (similar to knative/serving) could be relevant here.
Any other ideas?

you mean creating a new version of the pipeline every time its changed? might be too much versions and we then the pipelineRun needs to have the ability to select which version to use if not latest.
To clarify, yes, I would expect the PipelineRun to make a copy of the Pipeline and use that in any reconcile until this run is finished.

I think that having the ability to select the version of a Pipeline/Task to run could be useful in some cases. For example, if you have a Task that is used in a few Pipelines, and you want to update it, you will probably want to test your updates on a single Pipeline to make sure it works before you force all Pipelines to use the new version of the Task for new builds. You can always do this with a kind of poor man's versioning in the Pipeline/Task name manually (i.e. PipelineNameV2, TaskName@scm-revision), but if this is a common use case then supporting it directly could be helpful.
Even if we did have Pipeline/Task versioning, and PipelineRun held references to immutable versions of Pipelines/Tasks, I think you'd still need to copy them into the PipelineRun in some way if we expect users to be getting build info by looking at the PipelineRun directly, so the issue as-described seems like something we definitely want.

Note that corev1.ObjectReference can support ResourceVersion: https://godoc.org/k8s.io/api/core/v1#ObjectReference

you mean creating a new version of the pipeline every time its changed?

I think what we'd do is create a new version of the Pipeline when a PipelineRun is triggered, so something like:

User creates PipelineRun which uses Pipeline xyz
We create a 'Revision'/snapshot of Pipeline xyz, which the PipelineRun references
As the PipelineRun executes, it references the revision/snapshot of Pipeline xyz, meaning that if Pipeline xyz changes, those changes won't be picked up by the executing Run

if you have a Task that is used in a few Pipelines, and you want to update it, you will probably want to test your updates on a single Pipeline to make sure it works before you force all Pipelines to use the new version of the Task for new builds.

That's an interesting use case @dwnusbaum - thanks for the tip @mattmoor ! - sounds to me like we need to get an issue going to talk about the story around how a person would try out changes to their Pipeline (ideally we can get to a point where you can make changes to your Pipeline yamls and try them out in a PR or similar without effecting your actual Pipeline)

Playing into this, I just asked a question in slack:

Also, how, if at all, do we stop reconciling a PipelineRun upon completion? I may very well just be misunderstanding the general architecture, but it looks to me like the reconciler will just keep going forever - so that if you did something batty like somehow added a new Task to the Pipeline after the PipelineRun had completed, it’d end up picking up and running that new Task too. Am I missing something?

As I said, I could be misreading how this actually works at the moment, but it sure feels like adding a Task to a Pipeline after an associated PipelineRun (ok, and maybe some other actions to create/associate a TaskRun etc too, not sure) thinks it has completed could lead to it picking back up again.

but it sure feels like adding a Task to a Pipeline after an associated PipelineRun (ok, and maybe some other actions to create/associate a TaskRun etc too, not sure) thinks it has completed could lead to it picking back up again.

In the current behaviour this wouldn't happen (i dont think) b/c what triggers the reconcile to occur is:

If the PipelineRun itself changes
If any resources created by the PipelineRun change (e.g. TaskRuns)

(Created https://github.com/knative/build-pipeline/issues/299 to look into this further)


Rewrite READMEs

It rewrites READMEs with step-by-step guides on how to use ortac, both the default mode and the monolith plugin. It also elaborates on the description of the tool.
This PR builds on #81, so the first commits are not directly concerned. They are included since the installation instructions depends on #81.

Very good point! I added a new section listing some of the limitations to what specifications can be used.
There I need some extra eyes to complete that list :smile:

Thanks for this!
Can we please not merge this PR just yet, as there are still major issues that needs to be addressed before external users can try it.

Can we please not merge this PR just yet, as there are still major issues that needs to be addressed before external users can try it.

Sorry, I don't follow.
For example, there was a paper and a presentation at the OCaml Workshop 2021 advertising the Ortac repo and instructions for how to use the monolith plugin.
Rather than holding back the PR, I suggest

adding a visible warning up front in the README that the software is still experimental and under development
documenting the major issues (in the README or as issues)

Thank you @jmid for your suggestion, I added :warning: signs at the beginning of the READMEs.


header-numbering-skip-top-level: false

I assume that this setting at “false” means that h1 headers WILL be counted. If I am right, then it does not work.
Note: the 1st time I used 1.4.0 and got the dialogue box with the question if I wanted to save those settings to the note's front matter I clicked on “yes”. In that dialogue the setting was set to “true”.
So, perhaps it has something to do with a cache? If so, please advise.
If cache clearance is an issue, it should be done automatically by the plug-in, right?
Edit: I went to ~/Library/Application Support/obsidian/Cache, deleted everything in there, refreshed, deleted numbers from headers, and tried again: no change.
BTW, after removing the numbers, then refreshing Obsidian, puts the numbers back. Cache issue.

Fixed this issue in version 1.4.1


[Question] Finding a CHANGELOG.md dynamically?

I have a workflow that is triggered when new tags are created, and I don't always know the path to the CHANGELOG.md file. I'm trying to accomplish something like this:
- name: Get path for changelog
  id: changelog_path
  shell: bash
  run: |
    echo ::set-output name=path::$(ls ./**/${{ steps.app_short_name.outputs.name }}/CHANGELOG.md)
- name: Extract changelog
  if: ${{ steps.app_short_name.outputs.name && steps.check.outputs.result != 'stop' }}
  id: changelog_reader
  uses: mindsers/changelog-reader-action@v1
  with:
    version: steps.tag_version.outputs.current_version
    path: steps.changelog_path.outputs.path

Sadly this seems to fail, even though the path it's searching for returns a valid changelog. But maybe I'm going about this the wrong way. Any help is appreciated!

Got it working. My ls pattern wasn't bash friendly.
- name: Get path for changelog
  if: ${{ steps.app_short_name.outputs.name && steps.check.outputs.result != 'stop' }}
  id: changelog_path
  shell: bash
  run: |
    find . -type f -path '*${{ steps.app_short_name.outputs.name }}*/*' -name 'CHANGELOG.md'
    echo ::set-output name=PATH::$(find . -type f -path '*${{ steps.app_short_name.outputs.name }}*/*' -name 'CHANGELOG.md')
- name: Extract changelog
  if: ${{ steps.app_short_name.outputs.name && steps.check.outputs.result != 'stop' }}
  id: changelog_reader
  uses: mindsers/changelog-reader-action@v1
  with:
    version: steps.tag_version.outputs.current_version
    path: ${{ steps.changelog_path.outputs.PATH }}


Queries including a toOne relationship that is soft deleted is not being excluded on query result

Hi @olivierwilkinson !
First of all, thank you so much for this library! It is really very useful 🙌🏻
I have a quick question: I'm trying to do a query where a nested field that is soft deleted is not being excluded from the query and It is returned on the result. From what I understood on your docs, this nested field should be excluded, right? Specifically this quote of your docs

Models configured to use soft delete that are related to other models through a toOne relationship must have this relationship defined as optional. This is because the middleware will exclude soft deleted records when the relationship is included or selected. If the relationship is not optional the types for the relation will be incorrect and you may get runtime errors.

For example if you have an author relationship on the Comment model and the User model is configured to use soft delete you would need to change the relationship to be optional

If It helps, this is my schema.prisma entities related to this:
model UserAddress {
  id              String          @id @default(uuid())
  name            String
  user            User?           @relation(fields: [userId], references: [id])
  userId          String?
}

model User {
  id                                String                     @id
  email                             String?                    @unique
  name                              String?
  birthdate                         DateTime?
  createdAt                         DateTime                   @default(now())
  deletedAt                         DateTime?
  addresses                         UserAddress[]
}

And my stack is RedwoodJS as fullstack framework and I'm doing the following query:
query {
    userAddresses {
        name
        user {
            email
            deletedAt
        }
    }
}

That under the hood in the resolver it is executing this prisma query:
export const userAddresses: QueryResolvers['userAddresses'] = () => {
  return db.userAddress.findMany();
};

And as i said, it is returning a soft deleted user. But maybe i didn't understand the behaviour of toOne relationships, but from what I understood this should return something like this:
{
    "data": {
        "userAddresses": [
            {
                "name": "Test address"
                "user": {
                    "email"<EMAIL_ADDRESS>                    "deletedAt": null
                }
            },
            {
                "name": "Test address 2"
                "user": null //Being this the soft deleted user record?
            }
        ]
    }
}

Thanks in advance!

Heya 👋 ,
I'm glad you are finding the library useful! Sorry I've been slow responding to this, I've not used RedwoodJS so needed to look into it a little bit.
So for the example above it looks like the middleware is behaving as expected since the user that has been soft-deleted is excluded from the results. You are right that the null value is the soft-deleted user, if there was a user object with "deletedAt": [Date] then the middleware would have failed to exclude it. To exclude userAddresses that don't have a user I think you would need to change the Prisma query being run to do that. If you would like an example for that let me know and I can try to help there / add one to the docs 😁
Having said all that when looking into RedwoodJS I saw that they are using the Fluent API for including relations by default. I've not explicitly tested the Fluent API with the middleware so there may be some unexpected behaviour. I'll spend some time adding tests the Fluent API soon but until I've done that I'll leave this open in-case I find some issues that you should be aware of!
Thanks for trying the library, please don't hesitate to let me know if you find any other issues or confusing behaviour 🙏

Hey!
Thank you for your response, and there is no problem with the delay! I really appreciate that you took a look into RedwoodJS to give me a more detailed answer
I think I wasn't very clear in explaining the error because this is the current output:
{
    "data": {
        "userAddresses": [
            {
                "name": "Test address"
                "user": {
                    "email"<EMAIL_ADDRESS>                    "deletedAt": null
                }
            },
            {
                "name": "Test address 2"
                "user": {
                    "email"<EMAIL_ADDRESS>                    "deletedAt": null
                }
            }
        ]
    }
}

I believe this should be the expected output:
{
    "data": {
        "userAddresses": [
            {
                "name": "Test address"
                "user": {
                    "email"<EMAIL_ADDRESS>                    "deletedAt": null
                }
            },
            {
                "name": "Test address 2"
                "user": null
            }
        ]
    }
}

Am I right in saying that the current result is wrong? Because the second user is actually soft deleted, so I think there might be a bug in queries that include a toOne relationship, where soft-deleted entries are not being excluded from the query result. This error is not present in queries where a one-to-many relationship is included because the soft-deleted entities are successfully filtered out
Thanks again, and sorry for the confusion in the issue description initially

Ah! Yes then the middleware is not working as expected, most likely because the Fluent API needs some extra work to support.
Thank you for bringing this to my attention! And no worries at all about initial description 😁
I'm not sure what it will take to fix this unfortunately, but I will look into it and get back to you with an update soon 👍


Item._getUsageUpdates() should handle more cases

Originally in GitLab by @CarlosFdez
So currently, Better Rolls reimplements some of the consumption logic due to some pieces of missing functionality.

If consumeQuantity is true and consumeUsage is true, then once an item reaches 0 quantity it will continue to have uses. An item reducing to zero quantity should also set the number of uses to zero.
If consumeQuantity is true but consumeUsage is false, quantity is not consumed.

The second is less important (It is not likely to come up), but the first is necessary for any sort of quantity consumption logic that does not involve auto destroy, which is a feature that should probably be considered at some point.

I will expand on this issue to note that _getUsageUpdates also does not support consuming a set number of uses.
WIRE, for example, contains an implementation of Lay on Hands that allows the player to set the healing done using a slider and several magic items in dnd consume a varying number of uses depending on which of its abilities is used, and this currently requires a custom implementation to either duplicate this method or to piggy back it with another processing layer.

Needs to be reframed in the wake of the consumption refactor.


az network vnet subnet list-available-ips command is missing from the CLI but indicated as available in the docs

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az network vnet subnet list-available-ips

Describe the bug

The list-available-ips command is included in the latest documentation but does not appear to be actually present in the CLI. Attempting to invoke the command yields an error message stating
'list-available-ips' is misspelled or not recognized by the system.
Did you mean 'list-available-delegations' ?

Which is confirmed as missing in the --help output
$ az network vnet subnet --help

Group
    az network vnet subnet : Manage subnets in an Azure Virtual Network.
        To learn more about subnets visit https://docs.microsoft.com/azure/virtual-network/virtual-
        network-manage-subnet.

Commands:
    create                     : Create a subnet and associate an existing NSG and route table.
    delete                     : Delete a subnet.
    list                       : List the subnets in a virtual network.
    list-available-delegations : List the services available for subnet delegation.
    show                       : Show details of a subnet.
    update                     : Update a subnet.

To Reproduce

Assuming this command has not been removed, the following command should include the list-available-ips subcommand
az network vnet subnet --help

If this command is deprecated or has been removed, it should not be present in the docs.
Expected behavior

The subcommand should be available from the CLI, or should be removed from the docs.
Environment summary

Install Method: direct download of binary release
OS version: RHEL 7.9
Shell Type: bash
CLI Version:

$ az version
{
  "azure-cli": "2.36.0",
  "azure-cli-core": "2.36.0",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {}
}

Additional context

I think I figured out my own issue here. My host system is RHEL7.9 which according to the installation docs is not longer eligible to receive the latest package updates

Starting from Azure CLI 2.39.0 (released on 08/02/2022), no RPM packages will be released for RHEL 7 and CentOS 7. You may continue to use historical versions of Azure CLI on these systems, but there will be no updates or bugfixes. Consider upgrading to newer versions of RHEL or CentOS to use the latest Azure CLI.


Unify example and add wifi functionality

This brings the example more in line with others by making it more C++.
To reduce duplication and maintenance overhead I'm including wifi functionality in sockets.
It also unifies the readme and expands the wifi section.

@pan- I'll squash after you're done


More models

Hi, can you add more model from here? Thanks
https://github.com/hzwer/Practical-RIFE?tab=readme-ov-file

I have a few more models exported here: https://github.com/TNTwise/rife-ncnn-vulkan

How about 3.10 and more?


Chrome frame install script missing http protocol.

Chrome frame install script missing http protocol. This results in it not loading.
To test, view page in internet explorer 6 - you should get prompt to load chrome frame.

This is by design: http://paulirish.com/2010/the-protocol-relative-url/

also one of the first things mentioned in the h5bp faq, check out https://github.com/h5bp/html5-boilerplate/wiki/FAQs and the other docs

Ah OK, that makes sense regarding security errors. That's a good trick actually.
I was getting a javascript error with the CFInstall script when testing in IE6, which seemed to go away when I made this change, but maybe it was caused by something else. I will investigate.


This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Originally posted by @lock in https://github.com/nuxt/nuxt.js/issues/1721#issuecomment-435582723

This question is available on Nuxt community (#c8324)

I got the very same problem, but the guy the one who posted it didn't show his solution.


fix(nuxt2): support nuxt2

fix: #1832

autoimport unocss will generate the code
import 'uno.css'
export default defineNuxtPlugin(() => {})

but defineNuxtPlugin is not autoimport in pure nuxt2

I test this example, but it doesn't work properly.

You can try to run it?

I can run it. Can you provide the mini repo thanks 😀

I'm just run https://github.com/unocss/unocss/tree/main/examples/nuxt2-webpack.
let me check it carefully again.


Opt-in for a self-contained binary?

larastan sometimes fails when I have some kind of error in my code (which obviously occurs during work-in-progress), for example in a service provider, and the error notification fills up my IDE's entire viewport; which is kind of annoying sometimes.
So my suggestion is how about opting in for a self-contained binary which doesn't use/load dependencies from the project just like how it's done in https://github.com/laravel/pint/
I can work on a PR if you guys are interested.

I don't think this is going to work as well as you think:

Larastan has to boot the container to understand Laravel's magic---if you don't want / need this than just use PHPStan.


Does not work with babel-register and babel-polyfill

If I do a
node -r babel-register -r babel-polyfill node_modules/.bin/micro -p 3000 src/index.js
I still get errors about import/export statements:
micro: Error when importing ...
(function (exports, require, module, __filename, __dirname) { import ...
                                                              ^^^^^^

And yes, transpiling works (with preset-node6):
babel src --out-dir build
Any idea what might cause this?

I believe it's a poor choice to go with async-to-gen, as it does not play nice with other extensions. I contacted the author and suggested to become part of the babel solution:
https://github.com/leebyron/async-to-gen/issues/15
Please make micro so it plays well with babel! async-to-gen does not have to become part of your build distribution, so something like the previous -no-babel should be made into --no-transform (or something that makes more sense), not doing any transforms on the fly.
And why remove the babel dependency if most of the javascript programmers use it?

I believe it's a poor choice to go with async-to-gen, as it does not play nice with other extensions. I contacted the author and suggested to become part of the babel solution:
leebyron/async-to-gen#15
Please make micro so it plays well with babel! async-to-gen does not have to become part of your build distribution, so something like the previous -no-babel should be made into --no-transform (or something that makes more sense), not doing any transforms on the fly.
And why remove the babel dependency if most of the javascript programmers use it?

Maybe when Node.js 7.0 is out, which won't be too long, this problem could be solved.

@amio Seems like Lee Byron worked on a solution in async-to-gen: https://github.com/leebyron/async-to-gen/issues/15#issuecomment-245353348

Cool, thanks @timneutkens

@amio @morriz #114 was just merged which checks for async before executing async-to-gen's register. This will allow you to use node 7 with --harmony-async-await also leebyron/async-to-gen#15 was merged. This ticket can be closed 👍

Apologies if this is a dumb question, but I am still unclear how to use Micro with babel. Any tips on setting it up? I have tried several solutions and nothing seems to work. Thanks in advance!

@zachariahtimothy
@zachariahtimothy I got micro working with babel with these scripts in the package.json
"start": "node -r babel-register ./node_modules/.bin/micro src",
Below the settings, I used to deploy via now
"scripts": {
    "build": "babel -d build src",
    "start": "node -r babel-register ./node_modules/.bin/micro src",
    "now-start": "micro build"
  },


Improved translation

Changed 'padões criativos' to 'padroes criacionais' for consistency with English original.
Translated 'Prototype pattern' to 'Padrão prototype'.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Username Checker Error

This error is always occur when using the username checker
full log in the attach
error-log.txt

I will check it. If it is a bug we will fix it.

will check it out , I was busy on some works
On Fri, Oct 16, 2020, 08:34 Kiran Babu Muddam<EMAIL_ADDRESS>wrote:

I will check it. If it is a bug we will fix it.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/TIGMINT/TIGMINT/issues/13#issuecomment-709702709, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCZGB7FYTXUARSMZAQ6LF3SK6Z4NANCNFSM4SSAM5WA
.

http://localhost:3000/username/result

@shanow7  Fixed it,  pull the latest version and try again.


feat: feature flag polling for local evaluation (1/4)

Hello!
When I was looking on how to contribute to the PostHog's roadmap, I've found that one of the top items is implementing Feature Flags in Java for local evaluation. See issue: https://github.com/PostHog/posthog/issues/16419
The FeatureFlagPoller is set to fetch for new feature flags every 5 minutes. The poller also provides a forceReload method in case the consumer wants to have an up-to-date view of the feature flags.
I based most of my implementation from https://github.com/PostHog/posthog-go
I wanted to get an understanding on how to interact with PostHog's product, and Feature Flags seems a straightforward entrypoint to the portfolio.
Review order
This is the first of two PRs. I wanted to keep the scope of the change simple to facilitate the review. This PR is mainly POJOs; FeatureFlagPoller being the exception.

#55: use the poller implemented here in the PostHog client.
#56: send feature flag events to product analytics every time a consumer calls a feature flag method.
#57: get all the feature flags associated to a distinct_id

The pull-requests mentioned above should not be reviewed until the dependencies are merged.

Hey @miguelhrocha - thanks a lot for your PRs! Even though, as @marandaneto said this probably wouldn't make it in right now, I'd love to send you a posthog merch code because of the effort - this is great, love to see it :)
Send me an email please at neil @ posthog . com :)


Add Javadoc comments for our custom annotations

Each annotation defined in our repository should have a Javadoc comment. This Javadoc should explain, when such annotation should be used etc.

:pepepanic:

@PawelLipski we can close this one, right?
(y are they not closing atomagically with the pr? :thinkinggggg:)

:yes: we can close
The issues only close once all the linked PRs are merged to default branch, i.e. master for this repo.
Ideally, GitHub would have two separate settings:

the branch to which you need to merge all linked PRs for the issue to close (that would be develop for us)
the branch from which README is taken (that would be master).

Given that we need to select just one for both 1+2... I'm choosing 2. over 1. (so that only the released stuff is displayed in README)