SpFx Helloworld webpart does not show up under modern Page toolbox

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
Category

Bug

If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice.

Expected or Desired Behavior
After adding SpFx webpart to site contents, the webpart should be available in toolbox for modern UI page in SharePoint online.
Observed Behavior
Cannot find Simple hello world webpart in modern UI page toolbox, although it is available under site contents.
Steps to Reproduce
Followed all steps as explained in article
https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page
However, stuck at last step, i.e. cannot add webpart to page.

Silly question, but can you scroll down in the modern page toolbox and see it lower?

Offcourse I have tried it. I was not able to put that together in screenshot. Below is full screen grab, if that helps

OK, just double checking.  Did you get your part working on your local workbench and / or hosted workbench before uploading it to the app catalog?
If you type this into your browser (https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts) can you find your webpart listed?
If you go to your app catalog site, can you go to https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx and see your webpart in the list of available components?

Hello Patmill,
Please find my answers below:
Did you get your part working on your local workbench and / or hosted workbench before uploading it to the app catalog?
Ans: Yes it is working on local workbench.
If you type this into your browser (https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts) can you find your webpart listed?
Ans: No, I cannot find it.
If you go to your app catalog site, can you go to https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx and see your webpart in the list of available components?
Ans: No, I do not see it here as well

It started working now.
Resolution:

Go to ~appcatalog/AppCatalog/Forms/AllItems.aspx
Edit properties for the web part, I added short description & Description and saved.
Webpart started appearing under ~appcatalog/Lists/ComponentManifests/AllItems.aspx
Removed and re-added webpart from dev site.
It started showing up in page toolbox. I was able to add and see it on page as well.

Thank you for your guidance Patmill.

Glad you got it sorted out.

@Moreshwar83 Thanks for pointing out to fill 'Description' and 'Short Description'. If there is no 'Description' and 'Short description' 'Client Side WebPart' don't show up on the web part list.

If you check the schema of the web part manifest in<EMAIL_ADDRESS>you can see that the description property is required. When you try to build the project without it, or with an empty value you will get a build error. Could you share your web part manifest so that we can see your configuration?

@waldekmastykarz
Firstly, the manifest path does not seems correct in local. I found the file in the following path '.\SPFx\helloworld-webpart\node_modules@microsoft\sp-module-interfaces\lib\manifestSchemas'
IClientSideWebPartManifest.d.ts.txt
I do see, the 'description' is not optional in the file, but could be bug in mappings.
There is no mention about 'short description' field though.
P.S I have added '.txt' extension to the file as the file type is not supported by git hub comments.

@Dilli sorry, I shortened the path too much in my comment, you got it right. Where did you get the reference to 'short description' from? It doesn't seem to be mentioned anywhere.

@waldekmastykarz , Myself picked the 'short description' from app catalog. Please ignore 'short description'.

Hi @patmill  @Moreshwar83
what would i do if i cant see it in the /_api/web/GetClientSideWebParts but it is present in the sites/appcatalog/Lists/ComponentManifests/AllItems.aspx. i still cant see it when i try to add my webpart

I'm experiencing the same behavior as @paigeflourin  - worked last week (11/20), but now, the updated web part no longer appears in the web part gallery.
I did add a provisioning feature to my solution in addition to the web part - and I'm wondering if that is what is causing the web part to no longer appear.  I tried a new build without the feature block in the package-solution.json file, but that does not seem to fix it.
My solution does not appear in the /_api/web/GetClientSideWebParts output, but it is shown in ~appcatalog/Lists/ComponentManifests/AllItems.aspx and has no error messages from deployment.
Any guidance is appreciated.

I'm facing the same issue as @paigeflourin .
Moreover when I try to unsinstall the app containing the webpart, it goes to recycle bin and shows zero KBs as size.
I'm unable to delete it from solution from recycle bin and consequently unable to try updating the web part as well.
Anyone else facing this issue?

In my case, I found that when I added my own feature definition in the package-solutions file for provisioning, it was essentially overwriting the feature for the web part.  The tooling generates the feature behind the scenes but never reveals it (annoying!) so my hand-entered feature caused the conflict.
The fix was to ensure that the package-solution file has 2 features with different IDs - one for the web part, and one for the provisioning.  Once I did that, then the installation of the app put everything in the right place and the web part re-appeared in the gallery to place on a page.
Here's a sample package-solution.json to illustrate.  You'll need to generate new guids for your solution/features.
{
  "$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
  "solution": {
    "name": "Hello World",
    "id": "300ecbc4-f139-459e-bb2d-bc3b1445a12c",
    "version": "<IP_ADDRESS>",
    "features": [
      {
        "id": "3be4d3fd-963b-4a1b-9607-cddb02c4cf16",
        "title": "Hello World Web part feature",
        "description": "A feature which activates the Client-Side WebPart named Hello World",
        "version": "<IP_ADDRESS>"
      },
      {
        "title": "Hello World Provisioning",
        "description": "Adds site columns, content types, lists for Hello World items.",
        "id": "f1c4625d-e32a-4960-8166-7610cdcb24d1",
        "version": "<IP_ADDRESS>",
        "assets": {
          "elementManifests": [
            "elements.xml"
          ]
          // ,
          // "elementFiles": [
          //   "schema.xml"
          // ]
        }
      }
    ]
  },
  "paths": {
    "zippedPackage": "solution/hello-world-webpart.sppkg"
  }
}

Same problem as vickeybird here.
Webpart not showing up and after removal there where several files in the recyclebin, one of those is 0kB.
And that one can't be removed.

Ok, after an update in sharepoint (??, recyclebin look/behaves differently) things seem to be working again.
Was now able to remove the item and reinstall, now webpart shows up.

@bubbleswap  - for the error of not being able to delete from the recycle bin please open a new issue
@Leif-Frederiksen  - please see below, for instructions on gathering a correlation ID.
Thanks for all the feedback.  It actually looks like there are 2 classes of issues here:

The webpart never shows up being available anywhere.
The webpart is available on some sites but not others.

For case 1, the problem has a temporary fix.  Basically anytime an exception was thrown during deployment we would mark the package as deployed and eat the exception.  This is obviously bad and has been fixed by no longer eating the exception and marking the package as not deployed.  Also, we update error field to include the correlation ID of the deployment.  Our logging will help us determine what the root cause is, and we should be able to create a fix once we see this happen again (it has only rolled out to 75% of production, and just started on Sunday, but I don't see any instances of this yet).
For case 2, I am more interested as this is a new problem I have not seen before and am unsure of what is wrong.  We would like more information on this in order to help us diagnose what the issue is.  @Leif-Frederiksen  - please follow these steps to capture a correlation ID:

Load developer tools and start a network trace (F12)
Load a modern page
Put it in edit mode.
Click the "+" to add a webpart
View your network trace in the developer tools, you will see a request to GetClientSideWebParts
Look at the response header sprequestguid and respond here with that, as well as your tenant domain
If you know what webpart is missing, please include the details of it such as name/component id.

Thank you for helping us track down this issue,
Graham

Hi Graham,
Here is the info:
sprequestguide: b426469e-5065-5000-a684-b9581c831c38
Tenant domain: mthportal.sharepoint.com
I am uncertain about the component id. I have the following Id's
Solution: 7858eb79-bf7e-4481-8b3c-ceb6ad854d82
Webpart: 2fd7e645-afd2-44f9-b243-87d461e2cbd1
Group id of preconfigured entries: 6737645a-4443-4210-a70e-e5e2a219133a
To give you the full picture I post the content of the configuration files below - please let me know if I can provide more info.
package-solution.json:
{
    "solution": {
        "name": "MTH Ledelsessystem",
        "id": "7858eb79-bf7e-4481-8b3c-ceb6ad854d82",
        "version": "<IP_ADDRESS>",
        "iconPath": "Images/AppMTHicon.png",
        "skipFeatureDeployment": false
    },
    "paths": {
        "zippedPackage": "solution/MTH.Ledelsessystem.sppkg"
    }
}

webpartmanifest.json:
{
  "$schema"<EMAIL_ADDRESS>
  "id": "2fd7e645-afd2-44f9-b243-87d461e2cbd1",
  "alias": "LedelsessystemWebPart",
  "componentType": "WebPart",

  // The "*" signifies that the version should be taken from the package.json
  "version": "*",
  "manifestVersion": 2,

  // If true, the component can only be installed on sites where Custom Script is allowed.
  // Components that allow authors to embed arbitrary script code should set this to true.
  // https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
  "requiresCustomScript": false,

  "preconfiguredEntries": [
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "MT Højgaard: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://mthportal.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Pages",
        "toolsLibraryName": "Documents",
        "termSetName": "QMS Navigation",
        "resultSource": "578b90fb-655b-4b93-897c-f67a00c3029b"
      }
    },
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "Ajos: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://mthportal.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Sider",
        "toolsLibraryName": "Dokumenter",
        "termSetName": "QMS Navigation Ajos",
        "resultSource": "8eeb918e-c59d-4209-b7ed-e055a2821e38",
        "groupProcessLibraryName": "Pages",
        "groupToolsLibraryName": "Documents"
      }
    }
  ]
}

Also having this issue alot: @smithbrianscott  's suggestions worked though!

@Leif-Frederiksen - thank you for sending that, I can't fetch the logs until Monday, but I will take a look then.

That sounds good @mcmynn83. I'm curious as to what you can see from the logs on Monday. Have a nice weekend until then :-)
Regards
Leif

Same problem. I try sample "react-script-editor" on site with specific site collection app catalog.
NO show on modern page (also already remove all and reinstall but nothing happen).
It's show in "features" list and also in "/Lists/ComponentManifests/AllItems.aspx" .
If try in workbench it's works all fine.

There is an advisory SP128660 in Office Admin Center, which titled "Can't install or activate add-ins or modern SharePoint packages". Is this issue related to that advisory??

Hmmm I think I met this issue last week when the webpart show up on first time deployment but after that every app upgrading will cause it to disappear from the Web Parts toolbox.
Later then I found out that there is an issue with the "includeClientSideAssets" in the package-solution.json
I CREATED ANOTHER PROJECT with that "includeClientSideAssets" set to false and using the CDN URL instead and things are working now even after upgrading the app.
But I do recall that once it has disappeared then even set the "includeClientSideAssets" to false and re-deploy won't make it show up again.
Now I'm facing the issue with the app keep saying " The App is installing..." and just hang there forever without any errors.

I was also facing this issue  , the only workaround i found was to delete the app packages from the site collections and from the app catalog and then redeploy everything. Is is working now as expected in all sites except one

Hi @mcmynn83  - did you get a look at the logs?

I had the same issue. Increasing the version number in package-solution.json and deploying again to the app catalog then upgrading and/or re-installing multiple times would never work. Removing from the app catalog and recycle bin 2nd stage did the trick.
I did notice something else, if I added another web part using the yeoman generator, only the new web part would show up if I upgraded the solution without removing from the app catalog. However, as soon as I increased the version number and upgraded again, my recently added web part would also disappear.
Hope this helps.

I noticed on my tenant that */CLIENTSIDEASSETS was not added to to public CDN origins event thou CDN was enabled. Added that manually, removed app from AppCatalog and from sites and the webpart showed up. (this happened on Classic SP)

Hi @mcmynn83 - any success with looking into the logs?
Regards
Leif

I logged this case as a Severity B premier support ticket. MS CS team told me that their engineer will contact me tomorrow at 9am (HKT)
BTW, I am using Azure CDN, but I still experience the issue. I don't think that it is a SharePoint CDN config issue.

That sounds great @tsekityam  - looking forward to hearing what they find :-)

I am experiencing this today on multiple tenants.  Thanks for the research on this all.  I will try the suggested workaround of completely reinstalling from app catalog.

@telmocruz the same is with me now, the deletion from second recycle bin 'fixed' it for site collections created directly from SP Admin. But the recycling bin trick is not working for a site collection generated by O365 group. Was the one that didn't work for you also a site from O365 group?

Sorry about going silent here.  @Leif-Frederiksen - I looked at your logs and it looks like there is an issue.  Still investigating a fix.  Will keep the thread updated.

Just to update the thread and give a little more context... I can't tell you why everybodies is failing, or if it is the same reason.  However, the reason @Leif-Frederiksen is not see the webparts is that when he installed the app package the feature did not end up activated.  I'm currently trying to determine why that happened.  If anybody else is seeing this problem if you could send me correlation ids both for your call to add an app (when you install the spfx feature on the site), as well as the correlation ID for a call to getting webparts which doesn't show your webparts that would be super helpful.  Lastly, I would also need the URL of the site collection.  Thanks!

The cause of the problem has been identified and we will be rolling out a fix for it shortly.  Unfortunately the problem is in the generator which means packages have been created that cause this problem and will continue to cause problems.  In order to fix the problem after the fix is applied you will have to do the following:

Uninstall the app from a site collection
The app will have to be deleted from the app catalog
The new version of the app (built with the new generator) will have to be uploaded to the app catalog
Then the app will have to be added back to the site collection.

This process will work on todays solutions as well, however, it will have to be re-done after the fix is rolled out.
Sorry for the trouble has caused and thank you for helping us diagnose the issue.

I had an issue where the manifest in /Lists/ComponentManifests/AllItems.aspx was stuck at v.0.0.1 while my latest wp was 1.4.0. Seems uploading a new version does not always overwrite the component manifest list. Deleting the manifest entry, editing the props of the app made it all work again.
cc @patmill

@wobba - Could you open a new thread for that issue?  Also, if possible could you send the SPRequestGuid (from the response headers) for when you upload your new solution that doesn't actually trigger an update to your component manifests?

Hi,
I'll try to reproduce it later and log an issue if I'm able to. This was a
customers tenant so I had to make it work pretty quickly.
-mikaek
ons. 14. feb. 2018 kl. 19:09 skrev GrahaMc<EMAIL_ADDRESS>
@wobba https://github.com/wobba - Could you open a new thread for that
issue? Also, if possible could you send the SPRequestGuid (from the
response headers) for when you upload your new solution that doesn't
actually trigger an update to your component manifests?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/775#issuecomment-365694794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADHoLVBHWeMAeHncNI_JE4LDqcF5Fm4ks5tUyFHgaJpZM4OyQo6
.

Excellent thanks, and sorry that it's causing you problems.

Just quick update. We are looking to get the fix out as part of the upcoming SPFx Yeoman package v1.4.1 release. ETA for this release is hours / days... so coming soon. Will close the issue, when fix is out.

@VesaJuvonen so this means you have been able to repro the issue and figured out the problem? Could you elaborate on the actual issue causing this?

This is now fixed. We have a solid repro and have fixed the underlying issue as part of the v1.4.1 release. This was related to false behavior in Yeoman template solution packaging, which caused feature ID to get updated on a newer version of the package. ´
Unfortunately fixing this from existing environments will require some extra work and you should be upgrading to v1.4.1 as soon as possible. Here's a direct quote from the 1.4.1 release notes.
Fixed issue in the generator that prevented activation of new versions of SPFx packages.
Symptoms - You deploy a new version of SharePoint Framework packages and you no longer see your web parts in web part picker.
Issue reported here: https://github.com/SharePoint/sp-dev-docs/issues/775
Fix - To be able to fully successfully fix this issue, you will need to perform following steps in your SharePoint Online tenants.

Remove all instances of existing SharePoint Framework solutions from site level
Remove SharePoint Framework solution from app catalog
Upload new SharePoint Framework solution built with 1.4.1 version to your app catalog
Install SharePoint Framework solutions back to sites.

Notice that this issue is not happening for tenant-scoped SharePoint Framework solutions and it's not happening for SharePoint add-ins.

You might potentially take advantage of the SharePoint ALM APIs or SharePoint PnP PowerShell cmdlets for add-ins to automate this needed process.

Thank you. My issue was different then as I'm using tenant scoped parts. I
will update to 1.4.1 for my two parts, bump their version number in
package.json and manifest, rebuild and update the part on sites they are
used to verify if the show up or not.
-Mikael
tor. 15. feb. 2018 kl. 21:09 skrev Vesa Juvonen<EMAIL_ADDRESS>
This is now fixed. We have a solid repro and have fixed the underlying
issue as part of the v1.4.1 release. This was related to false behavior in
Yeoman template solution packaging, which caused feature ID to get updated
on a newer version of the package. ´
Unfortunately fixing this from existing environments will require some
extra work and you should be upgrading to v1.4.1 as soon as possible.
Here's a direct quote from the 1.4.1 release notes
https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-for-SPFx-Package-Version-1.4.1
.
Fixed issue in the generator that prevented activation of new versions of
SPFx packages.
Symptoms - You deploy a new version of SharePoint Framework packages
and you no longer see your web parts in web part picker.
Issue reported here: #775
https://github.com/SharePoint/sp-dev-docs/issues/775
Fix - To be able to fully successfully fix this issue, you will need to
perform following steps in your SharePoint Online tenants.

Remove all instances of existing SharePoint Framework solutions
from site level
Remove SharePoint Framework solution from app catalog
Upload new SharePoint Framework solution built with 1.4.1 version
to your app catalog
Install SharePoint Framework solutions back to sites.

Notice that this issue is not happening for tenant-scoped SharePoint
Framework solutions and it's not happening for SharePoint add-ins.
You might potentially take advantage of the SharePoint ALM APIs
https://docs.microsoft.com/en-us/sharepoint/dev/apis/alm-api-for-spfx-add-ins
or SharePoint PnP PowerShell cmdlets for add-ins
https://docs.microsoft.com/en-us/sharepoint/dev/apis/alm-api-for-spfx-add-ins#sharepoint-pnp-powershell-cmdlets-to-programmatically-add-and-deploy-sharepoint-apps
to automate this needed process.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SharePoint/sp-dev-docs/issues/775#issuecomment-366046517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADHoKDyx0pfIQcl1E7meTNY5qWfLLaiks5tVI7qgaJpZM4OyQo6
.

@wobba - Please submit a new issue if needed, so that we can track that with repro steps and web part configuration setup. Thx. Otherwise, it's impossible for us to track the tasks in VSO - as all of these issues are automatically synced for internal processing for our team.

I'm still having issues although I ran these steps:

To be able to fully successfully fix this issue, you will need to perform following steps in your SharePoint Online tenants.
Remove all instances of existing SharePoint Framework solutions from site level
Remove SharePoint Framework solution from app catalog
Upload new SharePoint Framework solution built with 1.4.1 version to your app catalog
Install SharePoint Framework solutions back to sites.

The webpart still isn't selectable in the toolbox...

This one got me now as well. My SPFx 1.4.1 tenant scoped webpart had includeClientSideAssets set to true and same as @poikjo, I had the Office 365 CDN enabled on the tenant but did not have the */CLIENTSIDEASSETS origin added.
So the solution was to add the origin and the webpart started to appear in the "add new webpart" dialog.
(You can also turn off the Office 365 CDN in which case the web part should appear as well. The JS files will then be served from the app catalog)

Yep - few things to notice here.

@Laskewitz - If you are using the standard URL in the write-manifests.json as "cdnBasePath": "<!-- PATH TO CDN -->"- and you use asset packaging - then it does not matter if the CDN is enabled or not... If CDN is enabled, we'll load the web part from CDN, if not, we load it directly from app catalog... without any changes needed by the developers.
@vman  - This is indeed something to notice. If you used CDN before CLIENTASSETS origin being there, you'll need to add that origin there manually or reactivate CDN

Not seeing any actual new issues here, so not reopening... if there are similar issues, please do open a new issue with sufficient details.

Hi,
I'm experiencing similar issue here.
I have a site collection with about 20-25 subsites.
I've installed the app at site collection catalog.
I'm using the 1.4.1 version.
For most of the subsites the webparts are available, but for some of them I can't see them.
Same app & same site collection.
Any idea or suggestion?
Thanks!

I can confirm this issue is still lingering.  To resolve the issue prior, I updated my solution to use 1.4.1.  Then upon deployment seemed to be fine.  Now performing some changes and redeployed the web part is no longer visible to add to the page onto the page.

@Cyan005 Check my post http://www.techmikael.com/2018/02/alternative-way-to-solve-issue-where.html or the release notes at https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-for-SPFx-Package-Version-1.4.1#other-relevant-fixes on how to resolve this.

I have been struggling with this issue where deploying the react-script-editor (https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor) and it is not showing in the toolbox of Site Pages in modern team site and communication site. I cloned the repo 2 weeks ago which means I have the newest 1.4.1 spfx as I see it referenced in package.json.
I followed the many suggestions in this thread I can say I removed from Site Collection and Tenant App Catalog countless times and redeployed manually and via PnP Powershell.
I have tested even across 2 different tenants which are more cleaner than my primary dev tenant.
My general approach is

Create private CDN such as \sites\CDN\siteassets\ and PnP PowerShell to set the CDN origin
Deploy to tenant App Catalog. SkipFeatureDeployment is TRUE so that it is deployed to all sites
Go to either a modern team site, communication site, or classic site to attempt to find and add the Modern Script Editor web part.
Issue: I only can see this web part in toolbox for 3-5 classic sites among 3 different tenants.
I am able to to see add/publish 1 other SPFX sample web parts from this repo.

I am particularly interested in using the react-script-editor webpart. And I only changed the cdnbasePath and skipfeaturedeployment settings in the .json. No other code changes. gulp --ship and gulp package-solution -ship
Appreciate any advice.

I believe the modern script editor web part is configured to require a site to have noscript disabled (the add/customize page permission is allowed) for security reasons. By default, self-service sites (sites that are created outside of tenant admin) do not allow this.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Roy Kim (MVP<EMAIL_ADDRESS>Sent: Saturday, April 14, 2018 6:12:20 PM
To: SharePoint/sp-dev-docs
Cc: Pat Miller (SHAREPOINT); Mention
Subject: Re: [SharePoint/sp-dev-docs] SpFx Helloworld webpart does not show up under modern Page toolbox (#775)
I have been struggling with this issue where deploying the react-script-editor (https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor) and it is not showing in the toolbox of Site Pages in modern team site and communication site. I cloned the repo 2 weeks ago which means I have the newest 1.4.1 spfx as I see it referenced in package.json.
I followed the many suggestions in this thread I can say I removed from Site Collection and Tenant App Catalog countless times and redeployed manually and via PnP Powershell.
I have tested even across 2 different tenants which are more cleaner than my primary dev tenant.
My general approach is

Create private CDN such as \sites\CDN\siteassets\ and PnP PowerShell to set the CDN origin
Deploy to tenant App Catalog. SkipFeatureDeployment is TRUE so that it is deployed to all sites
Go to either a modern team site, communication site, or classic site to attempt to find and add the Modern Script Editor web part.
Issue: I only can see this web part in toolbox for 3-5 classic sites among 3 different tenants.
I am able to to see add/publish 1 other SPFX sample web parts from this repo.

I am particularly interested in using the react-script-editor webpart. And I only changed the cdnbasePath and skipfeaturedeployment settings in the .json. No other code changes. gulp --ship and gulp package-solution -ship
Appreciate any advice.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/775#issuecomment-381372718, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADl-SXoDk30ioxGmQ5SN_WBku1J0sUb4ks5top50gaJpZM4OyQo6.

Thanks @patmill . I just used some powershell to disable powershell. Thought it be something simple that I missed. Much appreciated for the guidance!!

@RoyKimYYZ as @patmill said, default settings are to require a script enabled site. At the bottom of https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor the readme has notes how to deploy to noscript sites or tenant wide.

@wobba Thanks for pointing that out. I guess I didn't read it more carefully and should have played around the requiresCustomScript setting. By this web part "not being allowed", I just thought it would error out in App Catalog or when Adding App to the site. Nevertheless, I'm still learning the nitty gritty details of the multi-step process of install,deploy,activate multiplied by various config setting options. Appreciate your hard work and guidance!

Anybody having issues emptying the recycle bin to remove the app do this:
After removing the app in the classic mode (which is the only mode you can remove an app in), change back to modern mode (there should be a link below the side navigation) and open the recycle bin in the modern mode. this mode allows to delete the package from the recycle bin.

in my case, I have several webparts in the same project (e.g. 4 webparts in total):

In the workbench, all webparts are displayed properly in the toolbox to be added into the page.
In the modern page, only the first 2 created webparts are displayed in the toolbox, and the latest 2 webparts were NOT displayed in the toolbox.

Troubleshooting: I ensured that Description and Short Description have values in the App Properties, but the latest 2 webparts were not found anywhere (also checked in https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts and  https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx )
Solution:
I need to delete the app in the Site Contents and re-added the app back. My highlight is that we have a retention policy enabled in the tenant, and we must change the version of the app at Visual Studio Code (config\package-solution.json) so that we can re-add the same app (with a newer version) back to the Site Contents of the site.

I've also encountered this problem + found a solution that worked for me:

I am also experiencing this issue. Any update would be great. When I first created the solution, I was able to add the new webpart to a modern page. I made some changes, updated the package in the AppCatalog and tried adding to a new site I was working on and now it won't show up at all.
It does NOT appear when I go to "_api/web/GetClientSideWebParts" on the site I am working on.
It does appear when I go to "/Lists/ComponentManifests/Allitems.aspx".

My solution (for an SPFx solution NOT deployed to the entire tenant in one go):
Step 1: (preferrably) remove the apps on the site collections where you installed them. Do it like this: from site contents, remove. As a site collection admin (or global admin), go to the recycle bin. There is an error indeed when attempting to remove it there. However, change the url: _layouts/15/RecycleBin.aspx to _layouts/15/AdminRecycleBin.aspx. There, remove the app. Also, go to the second stage recycle bin (_layouts/15/AdminRecycleBin.aspx?View=2) and remove it there. Now the app is completely removed from your site collection.
Step 2: remove the spfx app from the app catalog. Repeat the steps with the admin recycle bin to make sure this item is also completely gone from the app catalog site collection.
Step 3: re-add your spfx package to the app catalog. I did not have to alter any ids to get it to work.
Step 4: re-add your app to the site collection where you want to add your web part.
Step 5: find your web part in the toolbox ! You can now also check the following endpoints to see your web part listed:
_api/web/GetClientSideWebParts
/Lists/ComponentManifests/Allitems.aspx

#1253 Related issue

I am still having this issue after I followed the tutorial. Using SPFX 1.9.1

I think there is something broken in my E3 developer tenant. When I go into the admin center and go to the apps section in settings and then go to the catalog creation page in my E3 tenant I can create another appcatalog. In my E5 tenant when I go the the app section and go the the appcatalog link I am redirected to my appcatalog


[Macros] Provide member macros with information about "missing" conformances

Provide member macros with similar information about conformances to what extension macros receive, allowing member macros to document which conformances they care about (e.g., Decodable) and then receiving the list of conformances that aren't already available for the type in question. For example, a macro such as
@attached(member, conformances: Decodable, Encodable, names: named(init(from:), encode(to:)))
macro Codable() = ...

Expanded on a type that is not already Decodable/Encodable would be provided with Decodable and Encodable (via the new missingConformancesTo: argument to the macro implementation) when the type itself does not conform to those types.
Member macros still cannot produce conformances, so this is likely to be used in conjunction with extension macros most of the time. The extension macro declares the conformance, and can also declare any members that shouldn't be part of the primary type definition---such as initializers that shouldn't suppress the memberwise initializer. On the other hand, the member macro will need to define any members that must be in the primary definition, such as required initializers, members that must be overridable by subclasses, and stored properties.
Codable synthesis is an example that benefits from member macros with conformances, because for classes it wants to introduce a required initializer for decoding and an overridable encode operation, and these must be members of the nominal type itself. Specifically, the Codable macro above is likely to have two attached member roles:
@attached(member, conformances: Decodable, Encodable, names: named(init(from:), encode(to:)))
@attached(extension, conformances: Decodable, Encodable, names: named(init(from:), encode(to:)))
macro Codable() = ...

where the "extension" role is responsible for defining the conformance (always), and the "member" creates the appropriate members for classes (init vs. required init).
The desire for this feature is tracked by rdar://112532829.

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

@swift-ci please smoke test macOS

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please build toolchain macOS

apple/swift-syntax#2004
@swift-ci please smoke test

apple/swift-syntax#2004
@swift-ci please build toolchain macOS

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please build toolchain macOS

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test

Windows failure is unrelated; kicking this off again.

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test Windows

https://github.com/apple/swift-syntax/pull/2004
@swift-ci please smoke test


Analysis Task: Subroutine References NPE

Describe the bug
ERROR Analysis Task: Subroutine References -  (AnalysisTaskWrapper) java.lang.NullPointerException
To Reproduce
Steps to reproduce the behavior:

test binaries:  https://github.com/polaco1782/linux-static-binaries
Headless Analyzer
may AnalysisTaskWrapper NPE errors in the log

Screenshots

Environment (please complete the following information):

OS: Debian GNU/Linux 10
Java Version: openjdk 11.0.11
Ghidra Version: 9.2.4
Ghidra Origin: official ghidra-sre.org distro

If I remember correctly this has been fixed. Please try the latest Ghidra release.


Mark JS API as stable

To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

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


Error at startup

Updated from 1.1.72 -> 1.1.74, received this error

Hello, thanks for the report. Migration issues like these are hard to diagnose without a save file. Could you provide me yours? If it's small enough, you can drop it here on Github.

the save file is 500MB, so here's the Google Drive link instead:
https://drive.google.com/file/d/1vNQcpDL5tDf7sbL1SazV-tkU6BkPA18K/view?usp=sharing

Thanks. The file seems set to private, I sent a silly request for access.

sorry, fixed. try again.

Thank you, worked. That's one chonky file! I'll look into the issue.

In an attempt to make it more manageable to open up (since I'm sure you'll be doing that a few times), I took the same one and trimmed/deleted many surfaces
https://drive.google.com/file/d/1vX1ReB3fzqGuHj32kjxKrekhWmmHQMnO/view?usp=sharing

Thank you, that's very kind.

Thanks to your save file (and patience), I was able to figure it out. It's related to migrating something that is already 'invalid' due to mod changes, which is something I didn't really test before release.
Although, there do seem to be some migration gremlins still, as most your plans are invalidated, which I'm not sure is working correctly. I'll have to look into that. But this one will be fixed with a release soon.


Fix coding style in Exit Before Enter example page

I think it is a better practice to use ternary operators in conditional rendering.

The current code is more clear to me, especially for illustrating the use of exit before enter.


New version: DuckStudio.GitHubLabelsManager version 1.5

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #195056

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

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

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

[!IMPORTANT]
Should be reviewed by @DuckDuckStudio

Microsoft Reviewers: Open in CodeFlow

Hi @Luna-Grace,@fjwxzde,@DuckDuckStudio,
Do you approve of these changes?
(Automated response - build 930.)


Create initial commit

After install, it should create an initial commit

closed with https://github.com/BearStudio/create-start-ui/commit/294d6ffa8cd9c5455042feead39d88d0b37f2635


Use idris-jvm in the repl?

Is it possible to use idris-jvm in the repl with an IDE? I'd like to do interactive development with other jvm libs in my emacs repl.

Currently in Idris REPL, we can only execute native code but we can still use the REPL with JVM types and functions. I am working on compiling Blodwen to JVM so once it is ready, we should be able to execute JVM code as well with that.

When I am in the Atom editor and I CTRL-ALT-R to type check then it sas
didn't load (my path)/src/main/idris/Main.idr

Can't find import IdrisJvm/FFI

How to fix this so I can do interactive editing?

You need to have an ipkg file like this:
module helloworld

pkgs = idrisjvmffi

modules = Main

Ahh thanks, what I had to do was open that folder with the ipkg in the root of the project, before I was opening a parent folder and drilling down to the sub-folder which contained the ipjkg which was wrong.

Now that we have Idris 2 on the JVM, compiler and REPL can run on the JVM. Here is a small example.
module Main

import System.FFI

namespace LocalDateTime
    data LocalDateTime : Type where [external]

    %foreign "jvm:now(java/lang/Object java/time/LocalDateTime),java/time/LocalDateTime"
    prim_now : PrimIO LocalDateTime

    %foreign jvm' "java/time/LocalDateTime" ".toString" "java/time/LocalDateTime" "String"
    prim_toString : LocalDateTime -> PrimIO String

    export
    now : IO LocalDateTime
    now = primIO prim_now

    export
    toString : LocalDateTime -> IO String
    toString = primIO . prim_toString

main : IO ()
main = do
    currentDateTime <- LocalDateTime.now
    printLn !(toString currentDateTime)

$ rlwrap idris2 Main.idr
     ____    __     _         ___
    /  _/___/ /____(_)____   |__ \
    / // __  / ___/ / ___/   __/ /     Version 0.5.1-98e399195
  _/ // /_/ / /  / (__  )   / __/      https://www.idris-lang.org
 /___/\__,_/_/  /_/____/   /____/      Type :? for help

Welcome to Idris 2.  Enjoy yourself!
Main> :exec main
"2022-01-02T22:27:09.945"
Main>


included passed values in the range - fixed

Added the ability to check the dates being passed in the range. Currently, if I have a range of 3/18/2015 - 4/12/2015 and 3/18/2015 is the date being passed to check, it will return false even though it is in the date range.

My two cents: "between" makes me think it's a closed range, and I'd be surprised by something named that including the ends.

Also see discussion in #2164

@talymo well, we can not just change the behavior of the function, it will break existing code. I'm closing this in favor of #2164. Hopefully in the next version there will be a way to specify whether you want ends included or not.


Use CircleCI to publish release version

ac543c7
This requires:
GitHub user token

Create a account
Grant it a push access to Khan/KaTeX
Create a GitHub access token with public_repo permission
Add it to CircleCI environment variable settings (CircleCI docs) as GH_TOKEN

and
NPM token

Create a NPM token
Add it to CircleCI environment variable settings (CircleCI docs) as NPM_TOKEN

@ylemkimon in https://github.com/Khan/KaTeX/pull/1531 we were able to use a repository deploy token.  Why is a user token necessary in this situation?

@kevinbarabash The deploy key does not give access to the GitHub API, as it’s HTTP. I think we can leave the creating the GitHub release, as release notes have to be added.
Also, I have some concerns about this PR, as uploading tokens can be dangerous and 2FA cannot be enabled, in part due to recent incident in eslint-scope.

@ylemkimon sounds good. Thanks for thinking about the security implications of these changes.


Updating glottocodes

@FredericBlum, here is the actualized list of languages with their respective Glottocodes for the dataset. I also updated the Glottolog and Concepticon version for the CLDF conversion.

Great, I'll merge now :) thanks for the review, @LinguList.


add histogram to track how many datapoints per metric we try to rollup raw to 5Min

We would like to know how many points we are fetching/reading when we are trying to rollup raw points from metrics_full to 5Min granularity. This would be useful in generating the right kind of load for performance testing.

Coverage increased (+0.03%) to 74.997% when pulling 6add88875a1659d90d38f5f8dd1afae7179c35f4 on shintasmith:rollup_meter into 6cacb4f4e835c835b7cfd78cbb464c697a7f5205 on rackerlabs:master.

@ChandraAddala , I have updated the code so that it will only update the histogram for query against metrics_full ColumnFamily

Coverage increased (+0.04%) to 75.015% when pulling aff85afd650d8de2bcf2718bf4aafc4f1363bc2a on shintasmith:rollup_meter into 6cacb4f4e835c835b7cfd78cbb464c697a7f5205 on rackerlabs:master.


Story Submission link in About page goes to old story page

https://frontline-stories.netlify.app/contact/

that's what it currently is, do you


[Fix] More comprehensive acquisition of Flink-K8s Ingress public endpoints

What changes were proposed in this pull request
Issue Number: close #2553

Brief change log

Verifying this change

This change is already covered by existing tests, such as (please describe tests).

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (no)

@Al-assad @wolfboys PTAL

@Al-assad @wolfboys PTAL

Hi Bin, Please modify this section：

@Al-assad PTAL1111111111111111111

@Al-assad PTAL

I'm sorry that I'm not familiar with Scala syntax, which caused me to overlook many details. Thank you for your patient guidance @Al-assad

LGTM, Finally 😛


Fix broken analytics.js quickstart link

New link: https://segment.com/docs/sources/website/analytics.js/quickstart/

Thanks!


ExEx WAL doesn't account for genesis block

Describe the feature
An empty node with an ExEx doesn't start when syncing from genesis and crashes with the Error: failed to parse file name: 0.tmp error. It happens because we don't write the genesis notification to WAL.
Additional context
No response

Closing in favor of https://github.com/paradigmxyz/reth/issues/11801


Allow adjusting time window

At the moment the logs are fetched from the last 15 minutes. Would be good to specify the time window somehow so we can investigate old issues.

I've added the ability to specify the time window in the event payload and the log inspector uses it now.
@robinMcA is going to work out how to specify the time window


kafka4s-connect

Adds a new kafka4s-connect subproject with utils for writing Kafka Connect sources and sinks in Scala. Draft because I still need to add docs. I will also backport this to https://github.com/Banno/kafka4s/tree/series/2.x, either in this or a future PR (should not require any code changes).

@zcox closing this because I assume it is stale. Please feel free to reopen if you feel that I've done so in error.

@Kazark 👍 wow, forgot all about this. It could still be done, but probably should be redone.


Anand dev heatmap yolo: current branch with changes

Changelog

Policy: YoloSAMPointNavResNetPolicy

Created YOLOPerception class
init : initializes YOLO and MobileSAM models and
predict: give object and receptacle segmentation masks as outputs. Also added some filters to reduce number of loop executions containing call to the SAM predict function.

Modified forward function of the GazeResNetEncoder
init: removed head_rgb from the visual encoder visual keys. Also initializes the YOLO_perception class
forward: It first checks if the "yolo_segmentation_sensor" is in observations (which is always the case as the collect_env_res from trainer calls predict function of YOLOPerception and stores that output) and then modifies that data according to the current skill (here GAZE: object_segmentation and start_recep_segmentation)

Modified GazePointNavResNetNet
init: removed head_rgb, yolo_object_sensor, yolo_start_receptacle_sensor and yolo_segmentation_sensor from fuse_keys

Trainer: YOLOSAMTrainer
_init_train: Called the YOLOPerception predict function to return masks and store it as reading of the yolo_segmentation_Sensor for the first_rollout. Also remove extra observation keys: head_rgb etc.
_collect_environment_result: Make call to the YOLOPerception predict function and then clean the batch observation to store for the rollout_storage.
train: added some extra print statements for debugging and clear cache memory.

Sensors: sensor
yolo_object_sensor: returns target object  category id as per new mapping of classes
yolo_start_receptacle_sensor: returns start receptacle id
yolo_goal_receptacle_sensor: returns goal receptacle id
yolo_segmentation_sensor: returns dummy tensor of same size as output for YOLOPerception predict function.

Single agent access Manager: single_agent_access_manager
_create_storage: removes extra keys from stoage from observation space-head_rgb, yolo_start_receptacle_sensor, yolo_object_sensor
load_state_dict: Fixed the previous error of lr_lambda resume state

Config: config.py
Created customRLConfig with following changes

Agent: Created a new single agent access manager class.

config file for experiments: YOLOSAM_gaze_rl_skill

DDPPO config: Created new customDDPPOconfig with addition of a new boolean key train_detector.

Is there a reason that you dont set inference mode (as done for visual features) when executing yolo_sam inference in the trainer init ? But I guess you do it in subsequent steps

Not needed to set that as it is called using Ultralytics library predict function

Okay got it
Btw, you should be very careful with hardcoding resolution as here

Also, what is the reason for doing this ?

backbone visual encoder should correspond to what is set in the config
Also I would strongly suggest you to clean up your policy class implementation. Remove all the unnecessary unused classes/functions/if-else conditions such as this, this, this
Basically, since we are trying to debug issues I would suggets you to remove thigns from implementation which you know should not be used. You can add them back later for future experiments

Please remove this condition as it may cause an issue. Can you please re check the logs and confirm that this condition was not execution. For the current experiments, you should raise an error message whenever the encoder tries to perfrom SAM inference as we dont want that

Why is all this hardcoded ? The class name is also the same as the default habitat single_agent_access_manager. Again, this can cause issues later as you wont remember that you hardcoded all these things and even the class name is same as the default habitat class

What is this line for ?

Net Parameter Distribution
Parameters
YOLO                                          164660809 (164M)  (Not trainable)
SAM                                            10130092 (10M)       (Not trainable)
Visual Encoder                           3034092 (3M)
Visual Features                          1044992 (1M)
State Encoder                             5402624 (5M)
start_receptacles_embedding   672
Previous action embedding       192

Total Parameters : 9485655
Critic                 513
Net                    9482572
Action Dist        2570

YOLO and SAM parameters are not listed in total params because YOLOPerception class does not inherit nn.Module (it inherits PerceptionModule same as done by DETIC). I tried to change this but it gives an error says self.train() cannot be boolean.
All the other parameters are trainable and listed with Total Params.

So earlier masks was a CPU numpy array ? And now you are explicitly moving it to the GPU ?

Also the same "task killed" error shows up in the other yolo_detector only experiments without SAM right ?

Also, it is not clear to me how does this fix the GPU OOM error in the detector+SAM experiments ? Can you please clarify ?


Retrieve patch filepath for Nopol

Pull Request Test Coverage Report for Build 1979

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 54.846%

Totals

Change from base Build 1978:
0.03%

Covered Lines:
2920

Relevant Lines:
5324

💛  - Coveralls


Dashboard authentication doesn't work

Describe the bug
In the chrysalis pt 2 version of Hornet, the dashboard authentication doesn't work.
To Reproduce

Run hornet tools pwdhash
Change Hornet config
Restart Hornet
Try to access dashboard

Expected behavior
The username and password don't get accepted. The credentials field simply reopens.
Environment information:

Browser: Firefox(Windows and macOS), Safari (macOS)
HORNET version: a153e10

Fixed with #827

Fixed with #827


Support new .NET 3.1.10  SDKs: SDK 3.1.404 and SDK 3.1.110

MSFT also shipped new .NET 3.1 SDKs along with .NET 5:

[x] SDK 3.1.404
[x] SDK 3.1.110

Done for v0.4


Release tag names

Hi,
Would it be possible to change the format of the release tag names (for the docker image), to a more human readable format?
I would suggest,
[pgxl_version_number]-[docker-image-version],
for example,
postgres-xl-docker:10.1-0.5.1
That would increase the readability in the helm chart. See: https://github.com/LamaAni/PGXL-HELM
image value.

The tags were actually cleaned up slightly in the last release. :) When a new version gets released, it's tagged according to the tag in the upstream Postgres-XL repo. Since the build images themselves aren't part of the official Postgres-XL project, a build change, even to fix a bug, won't result in a version bump upstream, of course. So, the base tag is done to match the upstream, so it's clear which upstream code is actually being packaged, and then anything past that is incremented using Git tag (i.e. using git describe) command, so it's deterministic. So, for the release XL_10_R1_1-313-g31dfe47342, since that was a version released by this project rather than an intermediary build, that name actually came from Postgres-XL—if you check out Postgres-XL XL_10_STABLE branch, you'll see that that commit is called XL_10_R1_1-313-g31dfe47342.
I agree the tags are a bit complex, but I personally see most of this as being upstream's responsibility or decision, not ours. And regarding the potential for having two commits chained—the first being upstream code, and the second any intermediary build not yet released—I think the additional complexity is justified by the deterministic builds and making it absolutely clear what is being built.
e.g. using this method, even if someone requests some earlier upstream code, for some reason—say a regression has been discovered on latest 'stable', building a fix is very easy, even though the numbering would come part-way through a current release. It also enables easy updates of the build packaging itself, even if upstream hasn't changed (such as happened for the XL9_5_STABLE branch).

Hi
I understand the reasoning, and it is logical. But it would make things very hard. And example can be given in airflow. When I talk about airflow 1.10.4, with image build 1.10.4 everyone know what I am talking about.
Thanks for considering,
You can close this.

Yes, completely understood—and that is indeed how we manage versions of pretty much everything else. :) But for pretty much everything else, the packaging is tied to the underlying code, whereas in this case, we are 'just' repackaging the upstream, without being able to affect the upstream versioning. e.g. with 10.1.2 , what would that mean for this project? That it's Postgres-XL 10.1.2 ? What if we need to update or fix an image issue? Should that be 10.1.3 ? And if Postgres-XL update some commits with some fixes on the stable branch? 10.1.4 ? And if we need to revert to a previous version of Postgres-XL code, or even just build it for something someone is analysing, but use the latest image stuff without known bugs? 10.1.5 doesn't make sense for that. Or if we want to go back to 9.4.3 , but fix with the latest image stuff? Well, the version of upstream Postgres-XL hasn't changed… Hence why, despite the long rather unwieldy version numbers, my current thinking is that this system is the best for declarative versioning, allowing us to update or build a variety of upstream Postgres-XL versions in parallel (e.g. we're currently packaging v9 and v10), without having to maintain some lookup chart of versions, or wait for a new Postgres-XL version every time we want to update the build packaging.

p.s. If Postgres-XL tagged their commits more nicely—the ones in the source code repository are very much inconsistent, and typically updated sporadically—then the versioning of the images under this method would be far clearer anyway. e.g. if Postgres-XL chose to tag their latest commit in the v10 stable branch as 10.3.0 today, then in fact this would result in us also changing our main image releases to simply 10.3.0 . I've also relaxed the versioning here to allow non-annotated tags, since Postgres-XL annotated v9 stable branch, but not v10—but really, the tagging there is far from what I would ultimately hope for, without wanting to sound overly critical.

Hi
Thanks for the detailed response. I guess the current tagging system will have to do. The change is for the better.

No worries. If you feel like it, and wish to request of upstream Postgres-XL project that it tag their 'stable' branch releases more sensibly and consistently, not only would I also be very pleased, but also that would trickle into this project, and make the tags here more like you describe 'automatically'—thus simplifying the Helm charts, also.
Sadly, I've pretty much given up on contacting the mailing list myself, because since their migration to a new mailing list host a year or two ago, the end-to-end encryption-through-transport guarantees have been broken, meaning I can no longer reply to people or email there. I reported it a couple of times, once at length including headers, and it apparently seemed to be a problem with the mailing list host they migrated to—but ultimately nothing got fixed, and years later, at least as of a few months ago, all my emails were still getting rejected (since I use a mailing host which enables requests of end-to-end encryption-through-transport guarantees). I confess that after the first few times, I stopped posting and all but forgot about it.


Aside scroll fix

steps to fix.

encapsulate top of countries (i.e. search bar, buttons) in a div
give position sticky and top to said div
check for issues
optional, give return to start labels to parameters and countries title

remember to include webkit vendor prefixes on css

In order to make my idea of having the titles be fixed while scrolling two things have to be done. The first is to have the Customize title out of the div containing stuff, such that it isn't on the parent div of the countrieswrapper. The second is specifying the top positions for both elements, which can break stuff eventually because of hardcoding values.

Afterwards, programming the titles as a way to get to the top, with https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView for instance

Odd artifact when scrolling, the div seems less big than it should, probably a rounding issue due to 0.1 rem.

only vendor prefix I think exists is position: -webkit-sticky; putting it here when github stops bugging out.

last thing to look at is the wide margin/padding the spacer has and the pixel issue with the scroll-to-top.

Final issues before pull request:
Accessibility issues:

Using the keyboard to scroll (Shift-Tab mostly) doesn't show the actual button, so JS scroll event has to be implemented to always show the object.
The headers can't be selected through Tab (maybe with button role? or button element).
ARIA roles?


Event PDF Generation

Completed with this PR. @aero31aero @rogeredthat

This PR was using pdfkit. The module is highly advanced and would require a separate api to interact with things like markup. Closing because its infeasible.


Remove patches/dev branch from clicommandlineparser

Split from https://github.com/dotnet/source-build/issues/405

This repo is still on a dev branch (not much different from patches IMO from a maintainability perspective):
https://github.com/dotnet/source-build/blob/275e6615655bc36401aadcc67320db6231f8d3ca/repos/clicommandlineparser.proj#L8-L9
/cc @crummel @tmat @dleeapho

CliCommandLineParser was moved back onto the prodcon branch with https://github.com/dotnet/source-build/commit/6b2e3210a40df7aebe18fc561bf27eae97e262a8.


Add some 404 tests

Add some 404 test, what check some bug what exists in npm version.

Oh no, tests test nothing!

I haven't written tests for all the failure cases yet, but would be glad to accept PRs!  We need tests for 201 and 304 reponses too.  Glad to offer help if you have any trouble with Chai/Nock.


Type versioning

Demonstrate how version an entity type definition and write a translation from old to new.
Bonus: Add bitemp to be able to query on old or new versions as they were known previously.

Made good progress on this eaxmple today.  Setting to fix as I'm now in progress.  The example I'm working on first is a minimal data migration project, where the delta between the models is very small.

In PR

Versions example look good.
@jmakeig Please let me know if I can ship this task or you want to take a look and ship yourself since its your recipe.

Shipping this task!


MAINT: misc. updates for better Py3 compatibility

Changes:

assertEquals -> assertEqual
assert_raises_regexp -> six.assertRaisesRegex
remove 'U' mode from gradient code tests
make skbio.draw RuntimeWarning tests more lenient to order of warnings (these were failing for me with a fresh conda install)

Should be good to merge when tests pass.


Custom translation with SqlFunctionExpression puts the function name between quotation marks

public static class DB {
	public static decimal? Nvl(decimal? a, decimal? b) {
		throw new Exception();
	}
}

modelBuilder
.HasDbFunction(typeof(DB).GetMethod(nameof(DB.Nvl)))
.HasTranslation((exps) => new SqlFunctionExpression("nvl", typeof(decimal?), exps));

ctx.TestTable.Select(z => DB.Nvl(1, 2)).First();

This gets translated to:
SELECT "nvl"(1.0, 2.0)
FROM "TEST_TABLE" "z"
FETCH FIRST 1 ROWS ONLY

Which throws an exception:
Oracle.DataAccess.Client.OracleException : ORA-00904: "nvl": invalid identifier
The problem is that "nvl" is between quotation marks. Why is this happening and how can I get rid of the quotation marks?
The documentation for HasTranslation points to https://go.microsoft.com/fwlink/?linkid=852477 but this link just redirects to https://docs.microsoft.com/en-us/ef/core/modeling/ instead of anything specific to function translation.
I am able to work around this by creating my own FunctionExpression class instead of using SqlFunctionExpression, but I think this should be unnecessary.
EF Core version: 2.2
Database provider: Microsoft.EntityFrameworkCore.Oracle
Target framework: .NET Framework 4.7
Operating system: Windows 10
IDE: Visual Studio 2017 15.8.6

I just noticed that quotes cause the identifier to be case sensitive. The following works correctly despite quotes:
SELECT "NVL"(1.0, 2.0)
FROM "TEST_TABLE" "z"
FETCH FIRST 1 ROWS ONLY

So it's not even an Oracle issue, it's just a me issue. Sorry.

It seems that SqlFunctionExpression has be changed in core 3 and it does not have a ctor that takes a string in the first parameter anymore. I can't seem to find anywhere online explaining what's the correct usage now. Any help?


[UI] Application page "fail" during configuration binding

Describe the bug
If I switch to the application page while a configuration is binding, the page will fail with "Expected resource to be defined".
A refresh of the page is enough to "fix" it.
To Reproduce

Create an app
Create a configuration binding with the app, and switch to the applications page without waiting for the creation to complete
See the error after waiting a few seconds

Hi @scures, I tried with @mmartin24 and the issue is there also in the epinio-dev branch.
He's going to post a video about it :+1:

@scures , @enrichman , here you go. This is the error on latest epinio-dev
https://user-images.githubusercontent.com/37271841/197735377-18ecef07-fce4-4c9e-87b4-8c19d1f0739d.mov

Not fixed yet in epinio-ui:v1.5.1-0.0.3

To be checked when https://github.com/epinio/ui/issues/183 is merged

This seems fixed now in epinio-dev:
https://user-images.githubusercontent.com/37271841/218978687-49877215-59b4-496b-9454-924efe2f0f05.mov


Removed custom User-Agent headers in requests for NHentai

Checklist:

[X] Updated source's version for individual source changes
[X] Updated all sources' versions for template changes
[X] Set appropriate nsfw value
[X] Did not change id even if a source's name or language were changed
[ ] Tested the modifications by running it on the simulator or a test device

https://discord.com/channels/927984899472883723/932317480590901358/1084913625858322502
https://discord.com/channels/927984899472883723/932317480590901358/1081649776665317406


Add byte array to Query

Currently Query::arg exists in order to add a String to a Query, this works really well with something like serde_json. However, it would be really convenient to also be able to add a Vec<u8> or similar directly to a Query in order to store a binary blob using something like bincode to serialize the data.

Blocking on skytable/skytable#157

Way to go, this has been implemented!


Adding POJOs mapping AWS Price List API JSON object

Adding AWS pricing supplier with Pricing Canonical Data Model
Adding multi cloud pricing service and integrating into existing multi cloud service plus configuring Guice modules plus pom dependencies

Hello Daniel,
please review my PR containing pricing functionality (pricing discovery + persistence + querying) and processing of first cloud service provider - AWS.
Thanks,
ŁSz

@LSZ-PL please check the merge conflicts

@LSZ-PL I solved the merge conflict, however this PR does not compile...


banChatMember definition not correct

packages:
"node-telegram-bot-api": "^0.61.0",
"@types/node-telegram-bot-api": "^0.61.6",
I'm using banChatMember like this bot.banChatMember(chatId, parseInt(m, 10), ban) but it gives me some weird error like TypeError: Cannot create property 'chat_id' on number '1689496709' where it's mixing up the ban date and the chatId.
Looking at the function definition on main package:
    * @param  {Number|String} chatId   Unique identifier for the target chat or username of the target channel (in the format `@channelusername`)
    * @param  {Number} userId  Unique identifier of the target user
    * @param  {Object} [options] Additional Telegram query options
    * @return {Promise} True on success.
    * @see https://core.telegram.org/bots/api#banchatmember
    */
  banChatMember(chatId, userId, form = {}) {
    form.chat_id = chatId;
    form.user_id = userId;
    return this._request('banChatMember', { form });
  }

but on typescript, gives me this signature:
method) TelegramBot.banChatMember(chatId: NodeTelegramBot.ChatId, userId: number, untilDate?: number | undefined, revokeMessages?: boolean | undefined): Promise<boolean>

which one is not correct? If I remove the ban timer and just call with 2 arguments it works fine

The correct is: banChatMember(chatId, userId)
or if you need to pass the optional params: banChatMember(chatId, userId, { untilDate: XXXXX, ... })


Ensure this plugin doesn't break sourcemaps for the rest of the app.

Sourcemaps still don't work for the transformed components, but at least it doesn't
spoils the sourcemaps for the rest of the bundle.

Fixed in https://github.com/metafy-gg/vite-plugin-svelte-svg/commit/7f60563a4375ecbe6c9b111cd8bdac4cdd5d9b1c

@trmcnvn I checked the latest main and it does work for us. Can you publish a new version to the registry? Thanks!

2.0.2 is already published.


[Android][Windows] Running the examples error

error when run:
./gradlew :Examples:Movies:android:app:installDebug

and it's works:
gradlew :Examples:Movies:android:app:installDebug

#2693

Should be fixed now - https://github.com/facebook/react-native/blob/master/docs/LinuxWindowsSupport.md


Support SRVW=-1 for Sparse

To fix no solution found when Sparse + SRVW=-1

the solution can be found after this PR, from CI the related failed is gone.
http://math-ci.amd.com/blue/organizations/jenkins/gfx94x%2Fprecheckin%2FhipBLASLt/detail/PR-518/1/pipeline


Could not find package symfony/symfony-demo with stability stable.

hello,
when I run this command line:
composer create-project symfony/symfony-demo symfony-demo
I receive this error:
[InvalidArgumentException]
Could not find package symfony/symfony-demo with stability stable.
I have php 7.1.7, the same error in php 7.0.21
Could you update it to the latest PHP?

Hm, I wonder is it due to config.platform.php locked version or "php": ">=5.5.9" in require section?

The package is simply not registered on packagist.org. :)

I was pretty sure it's registered. Any reasons do not register it? composer create-project is a good alternative way to install it I think

@bocharsky-bw moreover, the Symfony Installer is being deprecated, so the recommended way to install this project will be through composer create ..., so it must work!
@fabpot could you please register the Symfony Demo as a package on Packagist.org? Thanks!

@javiereguiluz Done

Thanks!  Closing as fixed because:

The packages exists at https://packagist.org/packages/symfony/symfony-demo
The command composer create-project symfony/symfony-demo symfony-demo works now. If you see any problem, execute composer clear-cache because the package is very recent.


Proposed solution for issue #16

Below the fold images are sometimes being loaded.
After some digging I found that elements acting as the container MUST be visible when lazy image initializes. If the container has an animation on it and starts off hidden, it will not work and all images will load in container. This initial hidden state seems to screw up the calculations as the container element is not technically visible at the time lazy image is executed. This edge case causes the remaining to be a negative version of height.  Simply checking if remaining and height cancel each other out seemed to fix the edge case.
Demo of updated code working with originally hidden containers ( which previously did not work ):
http://peter.build/doing/app/#/app/events/now/

In regards to the Unit Tests, these were not passing for me with the initial code base.  I tried two versions of node ( v0.10 & v0.12 ) with the actual master branch and the grunt unit fails.  This PR only changes on line and uses two existing variables with a basic math operator.
I did look at the unit tests and it seemed the only way to get them to pass was to add { 'nolazy': true } in the afkl-lazy-image-options.  Seems without it the HTML never rendered and there are three tests that failed because the HTML rendered as an empty string.

The test fails because there are conditions not met :) But thanks for the insights into your problem. Your solution now gives errors for items where both are equal (logo left top, or image inside scrollable container). I think the option to check if image container is visible or not is better. Only jqlite has no .is(:visible). So i will check for innerWidth, that can only be set if parent is blocklevel (breaking change, since normally i also could put it in span) AND has a width.
{code}
var _elementOffsetWidth = function () {
if (element.offset) {
return element.offset().width;
}
return element[0].getBoundingClientRect().width;
};
{code}
then
{code}
var _onViewChange = function () {
// Config vars
var remaining, shouldLoad, windowBottom;
var height = _containerInnerHeight();
var scroll = _containerScrollTop();
var visible = _elementOffsetWidth() === 0 ? false : true; // element must be block level, check for visiblity is then possible

var elOffset = $container[0] === $window ? _elementOffset() : _elementOffsetContainer();
windowBottom = $container[0] === $window ? height + scroll : height;

remaining = elOffset - windowBottom;

// Is our top of our image container in bottom of our viewport?
//console.log($container[0].className, _elementOffset(), _elementPosition(), height, scroll, remaining, elOffset);
shouldLoad = remaining <= offset;

// Append image first time when it comes into our view, after that only resizing can have influence
if (shouldLoad && !loaded && visible) {

    _placeImage();

}

};
{code}
and for these three tests i will add
{code}
it('We only have one image', function() {
var el = angular.element('');
$compile(el)(scope);
scope.$digest();
window.setTimeout(function() {
    expect(el.html()).toBe('<img alt="" class="afkl-lazy-image" src="img/foo.png">');
}, 300);

});
{code}
See if this also works for you then i will release new major.

See if this dev version checked in now is solving your case as well?

@SquadraCorse Unfortunately, no, this fix does not work and has the same issue as the original.  All images load.  You can see the issue again on that same link.  Your code changes are found in this file:
http://peter.build/doing/app/assets/js/angular.js
If you search for var _onViewChange you'll see your changes made.
I know you are WAY more familiar with your own project that I am, but maybe explaining why I updated what I did would be helpful.  Even if it breaks other experiences, you might be able to figure out root case.
It seems like any time the remaining was the negative version of height this issue shows itself.  I am not 100% sure if getting the width of the element will make a difference as my quick checks said it was visible, event though I knew for a fact it was not.  I am not sure if makes a difference, but the animation I have is not a toggle of show/ hidden.  There is a 500ms animation that loads an element.  This animated element, FYI, is not the afkl-image-container.  There is a div.transition element for each page that shows up as a child within afkl-image-container which is what eventually contains the afkl-lazy-image.
I am OK just using my forked version of the project, as I might just be a weird edge case that no one else has.  But my solution of checking if remaining and height cancel each other out seems correct for my usage.  Especially since height should never be zero, and remaining, as far as I could tell, was never negative.  So I could not think of a situation where height and remaining could ever add up to zero unless this weird edge case happened.  But, this is your baby, so I know you'll know like 10 reasons off the top of your head.

@SquadraCorse Also, I would be curious if you tested ng-show rather than ng-if on http://afklm.github.io/ng-lazy-image/sample-hide-show.html.
As you know, ng-if does not actually render the element into the DOM.  This is not the same as ng-show which does render the element into the DOM, but adds a hidden class.  ng-show is more realistic to what I was having issues with.  It makes sense why ng-if still works as it seems like it would be running afkl-lazy-image on an element that is both visible and in the DOM.

For now, forking is maybe the best way. I did see you start with
.transition {
    display: none;
    height: 100%;
}
,,,

and then do your transititon. If i have time today i will make a different test (you are right about ng-if), i also saw it gave a width so my visible assumption doesn't work so i will remove it. I will also look at you change again and see why my own usecases didn't work anymore. Is transition in visibilty an option for you :) ?

So now I am totally lost as to the cause.  I duplicated the circumstances I had using your existing demo.
I put it up on plnkr for live editing:  http://plnkr.co/edit/oKBvtdfLHzoYIK2qEpja?p=preview
However, I was never able to get it able to break the way mine is without that fix.


TypeError: chunk.isInitial is not a function

There is this error:
var shouldExtract = !!(options.allChunks || chunk.isInitial());
TypeError: chunk.isInitial is not a function

I have no idea what is it.
My webpack.config.js file:
var ExtractTextPlugin = require('extract-text-webpack-plugin');

module.exports = {
    entry: './app/client.js',
    output: {
        filename: 'bundle.js',
        path: 'public/js'
    },
    module: {
        loaders: [
            {
                test: /\.jsx?$/,
                exclude: /node_modules/,
                loader: 'babel-loader',
                query: {
                    presets: ['react', 'es2015', 'stage-1']
                }
            },
            {
                test: /\.css/,
                loader: ExtractTextPlugin.extract('css')
            }
        ]
    },
    plugins: [
        new ExtractTextPlugin('styles.css')
    ]
};

There's not enough information to debug. Which version of webpack/extract-text-webpack-plugin are you using? If you have webpack 1 and are using extract-text-webpack-plugin 2, that error could happen. In that case you'll have to use extract-text-webpack-plugin 1 or upgrade webpack to 2.

I use last versions of 'extract-text-webpack-plugin' and webpack (2.2.1)

Ok, still not enough info. Maybe someone else has a better idea.

I don't know what else... It's  just about a simple functionality - build 'bundle.css' from all css-files from project. What kind of information do you need?

I would need a project to run. chunk.isInitial() is something provided by webpack itself. If chunk is missing, there is something fatally wrong.

Maybe these lines?
 at C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\index.js:259:55
    at C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3025:16
    at eachOfArrayLike (C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:940:9)
    at eachOf (C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:990:5)
    at Object.eachLimit (C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3089:3)
    at ExtractTextPlugin.<anonymous> (C:\site.dev\site-spa\react\node_modules\extract-text-webpack-plugin\index.js:257:10)
    at Compilation.applyPluginsAsync (C:\site.dev\site-spa\react\node_modules\tapable\lib\Tapable.js:71:13)
    at Compilation.seal (C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:525:7)
    at Compiler.<anonymous> (C:\site.dev\site-spa\react\node_modules\webpack\lib\Compiler.js:397:15)
    at C:\site.dev\site-spa\react\node_modules\tapable\lib\Tapable.js:103:11
    at Compilation.<anonymous> (C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:445:10)
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:417:12
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:332:10
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:52:16
    at done (C:\site.dev\site-spa\react\node_modules\async\lib\async.js:246:17)
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:44:16
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:332:10
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:52:16
    at done (C:\site.dev\site-spa\react\node_modules\async\lib\async.js:246:17)
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:44:16
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:332:10
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:52:16
    at done (C:\site.dev\site-spa\react\node_modules\async\lib\async.js:246:17)
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:44:16
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:332:10
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:52:16
    at done (C:\site.dev\site-spa\react\node_modules\async\lib\async.js:246:17)
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:44:16
    at C:\site.dev\site-spa\react\node_modules\webpack\lib\Compilation.js:332:10
    at C:\site.dev\site-spa\react\node_modules\async\lib\async.js:52:16

Sorry, that doesn't help.
I'm closing this issue until someone can provide a proper project to examine as instructed in the issue template.

Unable to provide a project, but I'd just like to mention that this is happening to me also.
Package versions:
"webpack": "^1.14.0"
"extract-text-webpack-plugin": "^2.1.0"

Properties from config file:
module: {
  rules: [
    {
      test: /\.css$/,
      use: ExtractTextPlugin.extract({
        fallback: "style-loader",
        use: "css-loader"
      })
    }
  ]
},
plugins: [
  new ExtractTextPlugin("styles.css")
]

@Rob-- Can you either upgrade to webpack 2 or downgrade the plugin to 1 series? I don't think the 2.x version of the plugin is supposed to work with webpack 1. That could be forced through a peer dependency.

@bebraw I'm a complete idiot, for some reason I thought I was using Webpack 2.0 even though I saw my Webpack version was clearly not 2.0. It's working perfectly now, sorry for wasting your time!

@Rob-- No probs. We may still want to set that peer dep to avoid these kind of issues. 👍

occurs for me as well - same exact issue same exact config.
webpack : 2.2.1
extract-text-webpack-plugin : 2.1.0

@jony89 There's still not enough info to help. 😢

@bebraw what do you need?
latest webpack, latest package of this module. add the following config to webpack :
        rules: [
            {
                test: /\.css$/,
                loader: ExtractTextPlugin.extract({
                   fallback: 'style-loader',
                   use: [
                     {
                       loader: 'css-loader',
                       options : { autoprefixer: false, sourceMap: true, importLoaders: 1 }
                     },
                     'postcss-loader'
                   ]
                 })
            }
        ],

and :
    plugins: [
        new ExtractTextPlugin('index.css'),
    ]

Then run the project with that webpack config and you will get :

node_modules\extract-text-webpack-plugin\index.js:267
var shouldExtract = !!(options.allChunks || chunk.isInitial());
^
TypeError: chunk.isInitial is not a function
at C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\index.js:267:55
at C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3025:16
at eachOfArrayLike (C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:940:9)
at eachOf (C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:990:5)
at Object.eachLimit (C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3089:3)
at ExtractTextPlugin. (C:\chikichak\app\client\chikichak-mobile\node_modules\extract-text-webpack-plugin\index.js:265:10)
at Compilation.applyPluginsAsync (C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\tapable\lib\Tapable.js:71:13)
at Compilation.seal (C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\webpack\lib\Compilation.js:525:7)
at Compiler. (C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\webpack\lib\Compiler.js:397:15)
at C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\tapable\lib\Tapable.js:103:11
at Compilation. (C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\webpack\lib\Compilation.js:445:10)
at C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\webpack\lib\Compilation.js:417:12
at C:\chikichak\app\client\chikichak-mobile\node_modules\gulp-webpack\node_modules\webpack\lib\Compilation.js:332:10
at C:\chikichak\app\client\chikichak-mobile\node_modules\async\lib\async.js:52:16
at done (C:\chikichak\app\client\chikichak-mobile\node_modules\async\lib\async.js:246:17

@jony89 I would need a standalone project. Any chance you could open a separate issue with that?

k

see #461

@jony89 Ok. Hopefully someone can debug based on that. Thanks.

@jony89 There is no { autoprefixer: false } in css-loader, which version of css-loader do you use and does it work without setting sourceMap. Please also try without postcss-loader and provide your postcss.config.js aswell. Don't take it personal but I won't download any kind of .zip or other files as long as I cannot take a first glance at them before I execute that on my system 😛 (#461)

so how do you expect me to provide a stand alone project?
create one by your own, it is pretty easy. postcss is not needed to reproduce the issue. (I just tried to create standalone as fast as possible) this will trigger the same issue :
        rules: [
            {
                test: /\.css$/,
                loader: ExtractTextPlugin.extract({
                   fallback: 'style-loader',
                   use: [
                     {
                       loader: 'css-loader'
                     }
                   ]
                 })
            }
        ],

It start to look like you guys don't really want to try and fix that. I'm trying to help here.

@jony89 you could make a new repo and upload an example project there?

god bless u all.
https://github.com/jony89/simple-webpack-extract-plugin

@jony89 node_modules/.bin/webpack --config webpack.dev.config.js against that completes without a problem for me (Node 6). There's still some info missing (Node version for one). Missing something subtle.

This is a little old now, but I just ran into this same error when I moved to a machine running node 7.0.0, after installing nvm and switching to 7.10.0 the error was resolved. webpack2.2 / extract 2.1

Same problem. All current stable versions: webpack 2.5.1 / extract-text-webpack-plugin 2.1.0. Just upgraded to node 7.10.0, still have the problem.
TypeError: extractedChunk.isInitial is not a function

some of the conversation moved to the issue, so i write my temp solution here as well
tnx, temporary solution is to give webpack-stream your own webpack version:
webpackStream(config, require('webpack'))

see https://github.com/shama/webpack-stream/issues/125
this is the issue : #461
hope it helps for others.

I thought I thoroughly checked all the versions, but it turned out I had a different webpack version running in node_modules of a higher level folder. So webpack was globally 2.5.1 but require('webpack') was an older version. Working fine now that I've got that sorted out. You can close this again

Hello I am getting this error as well.
$ webpack -v
3.0.0
$ node -v
v7.7.1

 optimizeUnhandled rejection TypeError: chunk.isInitial is not a function
    at C:\project\node_modules\extract-text-webpack-plugin\index.js:267:55
    at C:\project\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3047:16
    at eachOfArrayLike (C:\project\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1039:9)
    at eachOf (C:\project\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:1087:5)
    at Object.eachLimit (C:\project\node_modules\extract-text-webpack-plugin\node_modules\async\dist\async.js:3109:3)
    at ExtractTextPlugin.<anonymous> (C:\project\node_modules\extract-text-webpack-plugin\index.js:265:10)
    at Compilation.applyPluginsAsync (C:\project\node_modules\tapable\lib\Tapable.js:71:13)
    at Compilation.seal (C:\project\node_modules\webpack\lib\Compilation.js:525:7)
    at Compiler.<anonymous> (C:\project\node_modules\webpack\lib\Compiler.js:397:15)
    at C:\project\node_modules\tapable\lib\Tapable.js:103:11
    at C:\project\node_modules\html-webpack-plugin\index.js:60:9
    at tryCatcher (C:\project\node_modules\html-webpack-plugin\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\project\node_modules\html-webpack-plugin\node_modules\bluebird\js\release\promise.js:512:31)
    at Promise._settlePromise (C:\project\node_modules\html-webpack-plugin\node_modules\bluebird\js\release\promise.js:569:18)
    at Promise._settlePromise0 (C:\project\node_modules\html-webpack-plugin\node_modules\bluebird\js\release\promise.js:614:10)
    at Promise._settlePromises (C:\project\node_modules\html-webpack-plugin\node_modules\bluebird\js\release\promise.js:693:18)

@elliotwesoff look at this html-webpack-plugin comment, it fixed my 'undefined' error (mainly back to<EMAIL_ADDRESS>or use npm@5)

Hey @ghostd , I still get the same error after doing cd node_modules/html-webpack-plugin && npm install webpack extract-text-webpack-plugin

same issue here. jony89 comment helped me in my case, even though i'm using gulp-webpack, not webpack-stream as he states.
I got my setup on github, so you can clone and play around if you want to ...
Just to let you know:
gulp-webpack 1.5.0
webpack 2.6.1
extract-text-webpack-plugin 2.1.2
sass-loader (which is using E-T-W-P) 6.0.6
Basically, to make it work, try and provide to your webpack-stream or as in my case gulp-webpack webpack as a second param after your config ... that's what makes it work in my case as well :)

Can't believe this issue still closed:
node: 8.1.4
webpack: 3.1.0
extract-text-webpack-plugin: 3.0

Hi! Can You review this article? You even don't need to know russian. Just execute commands and create files. I get topic error, when I execute npm run build.
TypeError: chunk.sortModules is not a function.
What has forgotten the article author to do?

Hi guys, I ran into this problem myself. After reading it I tried to downgrade the plugin to 2.1.0 and it works for me. So far I can say that 3.x didn't work with webpack 2.2.0.
Hope this will help somebody here ;-)

Thanks @marcopeg, I had the same issue.  For me I was able to instead fix this issue by upgrading from webpack 2 to webpack 3.

node: 8.4.0
webpack: 3.0.0, 3.1.0, 3.5.5
extract-text-webpack-plugin: 3.0
the same problem...

I am install local version webpack-dev-server and it solved the problem.

I solved this issue by upgrading webpack-stream.
webpack 3.5.6
webpack-stream 4.0.0
extract-text-webpack-plugin 3.0.0

Im having this situation with webpack 1.13.2 and extract-text-webpack-plugin 3.0.1 :/

for webpack 3
npm install --save-dev extract-text-webpack-plugin
for webpack 2
npm install --save-dev<EMAIL_ADDRESS>for webpack 1
npm install --save-dev<EMAIL_ADDRESS>

@navasiloy your suggestion made the trick for my case. thanks.

I'm closing this issue until someone can provide a proper project to examine as instructed in the issue template.

@webpack You definitely need another admin for this repository.

@andrew-aladev please provide minimum reproducible test repo

I was able to reproduce it with empty string as an extension for webpacker. I am going to provide more detailed info later.

@andrew-aladev just ping me when repo is ready :+1:

My chunks was created in webpack/lib/Compilation.js in addChunk. But my version of webpack is 1.15.0. So we have misconfigured webpack here.
It is an npm issue. It shouldn't be possible for me to install latest extract-text-webpack-plugin with webpack 1x.

latest extract-text-webpack-plugin is not compatibility with webpack@1

The problem was about webpacker. It was using the wrong version of webpack. It's so easy to receive the same problem with npm.


Toggle buttons

There is a Bootstrap feature we haven't covered: https://getbootstrap.com/docs/5.3/forms/checks-radios/#toggle-buttons
There is a pull request #879 from @mmonteagudo that proposes an implementation.
There are still questions to resolve:

How does this coexist with Switches, which we implemented using the widely-used HxSwitch component (derived from HxCheckbox)? Should the toggle-button be another derivative of HxCheckbox, or are checkbox/switch/toggle-button variants of the basic HxCheckbox component that should be selectable via a Variant=CheckboxVariant.Regular|Switch|ToggleButton parameter? The enum-based variant would likely allow us to configure HxCheckboxList to handle rendering with a single parameter.

How do we handle the optional button group?

There are also Button plugin on/off buttons with similar behavior. Should we consider these as a separate feature that doesn't affect our check/radio boxes implementation, or is there potential overlap (e.g., HxCheckboxVariant.ButtonPlugin)?

@hakenr it actually is there, but the implementation or use is somehow awkward as it requires use of pure Blazor InputCheckbox  with HxButtonGroup.
https://havit.blazor.eu/components/HxButtonGroup#checkboxes-and-radios

Yes, the intention here is to add the feature in the very handy CheckboxList and RadiobuttonList components for ease of use. I'm already using it in our application.


dep: update libxslt to v1.1.36

What problem is this PR intended to solve?
libxslt just release v1.1.36. Full change log is at https://gitlab.gnome.org/GNOME/libxslt/-/releases/v1.1.36. This was a lockstep release with libxml 2.10.0 (see https://github.com/sparklemotion/nokogiri/pull/2625) and contains performance improvements and bugfixes.
Have you included adequate test coverage?
Existing coverage should be adequate.
Does this change affect the behavior of either the C or the Java implementations?
Potentially could change behavior in the CRuby implementation, but tests should provide coverage. We've been regularly running CI against upstream master.

I'm investigating the windows failures which seem to be related to the change in xslt/exslt exports:
linking shared-object nokogiri/nokogiri.so
/usr/bin/x86_64-w64-mingw32-ld: nokogiri.o: in function `Init_nokogiri':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/nokogiri.c:151: undefined reference to `__imp_xsltEngineVersion'
/usr/bin/x86_64-w64-mingw32-ld: /home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/nokogiri.c:201: undefined reference to `__imp_exsltRegisterAll'
/usr/bin/x86_64-w64-mingw32-ld: /home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/nokogiri.c:203: undefined reference to `__imp_xsltExtModuleFunctionLookup'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `dealloc':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:17: undefined reference to `__imp_xsltFreeStylesheet'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `transform':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:259: undefined reference to `__imp_xsltSetGenericErrorFunc'
/usr/bin/x86_64-w64-mingw32-ld: /home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:262: undefined reference to `__imp_xsltApplyStylesheet'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `serialize':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:102: undefined reference to `__imp_xsltSaveResultToString'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `registr':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:344: undefined reference to `__imp_xsltRegisterExtModule'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `initFunc':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:307: undefined reference to `__imp_xsltRegisterExtFunction'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `method_caller':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:286: undefined reference to `__imp_xsltXPathGetTransformContext'
/usr/bin/x86_64-w64-mingw32-ld: /home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:288: undefined reference to `__imp_xsltGetExtData'
/usr/bin/x86_64-w64-mingw32-ld: xslt_stylesheet.o: in function `parse_stylesheet_doc':
/home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:68: undefined reference to `__imp_xsltSetGenericErrorFunc'
/usr/bin/x86_64-w64-mingw32-ld: /home/flavorjones/code/oss/nokogiri/tmp/x64-mingw32/nokogiri/2.6.0/../../../../ext/nokogiri/xslt_stylesheet.c:71: undefined reference to `__imp_xsltParseStylesheetDoc'
collect2: error: ld returned 1 exit status

See https://gitlab.gnome.org/GNOME/libxslt/-/issues/73 for upstream issue with symbol exports. Pushed a workaround to this PR


If fetcher returns null the revalidation is ignored

This was my fetcher function:
  async function readUser() {
    return localStorage.user ?? null;
  }

If I'd go to the console and run localStorage.removeItem('user'), revalidation of any kind (whether via calling revalidate or focus revalidation) wouldn't work, until I switched it to:
  async function readUser() {
    return localStorage.user ?? false;
  }

Hey Guillermo,
Thanks A LOT for this exhaustive issue reports. I will be looking into them to see if they are related to this lib or https://github.com/ConsoleTVs/swrev.
I think I'll need some testing to be able to do all this, apologies!
Furthermore, I'm really happy to see you testing this tool. I'll keep an eye on all that's been posted around here for the upcoming release and see if I am able to correctly fix the use cases provided.
I know it might be frustrating to see many issues around. My intention was to build a foundation to be used across frameworks Like Svelte or Vue (You guys already have a great swr library for react). Strangely, I seem to be getting less issues on the Vue adapter (https://github.com/ConsoleTVs/vswr). Perhaps less people using it, no idea.
I am not an expect on Svelte, so I might need some help in some areas. Will investigate, thanks again!