text:
bug: Cant turn on the night variant of the tokyonight theme.

Did you check docs and existing issues?

[X] I have read all the tokyonight.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of tokyonight.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0
Operating system/version
MacOS Sonoma 14.2
Describe the bug
I have setup the night variant of the theme, but when i apply that the background goes black/the background of my terminal. This issue is only for the night variant of the theme, other variants are just working fine.
Steps To Reproduce

Here is the ss of my config.
Expected Behavior
The background should be colored and not black
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})

@folke help please sir.

As you can see, the themes guibg attribute is not there in the Normal highlight group

same problem here:

it seems that tokyonight-night defaultly enabled transparent...

return {
"folke/tokyonight.nvim",
config = function()
require("tokyonight").setup({
style = "night",
styles = {
functions = {}
},
})
vim.cmd("colorscheme tokyonight")
end,
}
For now this should work

Let @folke get back so that he can provide a permanent fix

return { "folke/tokyonight.nvim", config = function() require("tokyonight").setup({ style = "night", styles = { functions = {} }, }) vim.cmd("colorscheme tokyonight") end, }
For now this should work

it doesnt work for me:

Bro just delete whatever you have written in your colroscheme config and add the above one that I shared.

Bro just delete whatever you have written in your colroscheme config and add the above one that I shared.

still no effect, let folke fix it...


text:
[ttLib.tables.O_S_2f_2] Should consistency check between OS/2 fsSelection and head macStyle be necessary?

In current version of fontTools, there is OS/2 fsSelection and head macStyle consistency check upon compile. Intuitively it makes sense because those bits (and nameID 2 in the name table as well) control the Windows style-linking mechanism together.
For the latest fonts however, I found that many bundled fonts with weight bolder than "medium," like "semi-bold," "extra-bold" or "heavy," have inconsistencies between fsSelection and macStyle. It seems like the designer did it on purpose. For example, Verdana Pro Semibold, bundled with the latest Windows 10, has the following settings:
head: macStyle = 0x0000 (Regular)
OS/2: fsSelection = 0x0120 (Bold and WWS), usWeightClass = 600 (Semi-bold)
name: (platformID 3, platEncID 1, langID 0x0409,) nameID 2: Regular
Verdana Pro Black, bundled with the latest Windows 10, has the following settings:
head: macStyle = 0x0000 (Regular)
OS/2: fsSelection = 0x0120 (Bold and WWS), usWeightClass = 900 (Heavy)
name: (platformID 3, platEncID 1, langID 0x0409,) nameID 2: Regular
Georgia Pro Black, bundled with the latest Windows 10, has the following settings:
head: macStyle = 0x0000 (Regular)
OS/2: fsSelection = 0x0120 (Bold and WWS), usWeightClass = 900 (Heavy)
name: (platformID 3, platEncID 1, langID 0x0409,) nameID 2: Regular
Hiragino Sans W6, bundled with macOS Sierra, has the following settings:
head: macStyle = 0x0000 (Regular)
OS/2: fsSelection = 0x0020 (Bold), usWeightClass = 600 (Semi-bold)
name: (platformID 3, platEncID 1, langID 0x0409,) nameID 2: Regular
Hiragino Sans W9, bundled with macOS Sierra, has the following settings:
head: macStyle = 0x0000 (Regular)
OS/2: fsSelection = 0x0020 (Bold), usWeightClass = 900 (Heavy)
name: (platformID 3, platEncID 1, langID 0x0409,) nameID 2: Regular
Even more interesting, in some cases, especially when using the 3rd party rasterizers like FreeType on Windows, head-OS/2 consistent fonts with "extra-bold" or "heavy" like weight will result in a "smear bold," but inconsistent fonts like above work normally. Although the latest OT Spec still insists that macStyle and fsSelection should be consistent, I was wondering if the necessity of that consistency check could be reevaluated.
Thanks!

UPDATE:
My friend from Microsoft told me that Windows GDI will forcibly turn off the auto bold once fsSelection is set to bold, so this might be the reason why those fonts I listed above have such inconsistencies. Set fsSelection to bold can avoid all possible auto-bolds on Windows.

Interesting. Thanks for the info.
Could anyone try on a Windows machine and confirm this is the case?
I'd be fine with removing the warning.

Auto-bolding with usWeightClass >= 700 on Windows is rather a rare case, because the font's fsSelection has to be regular or anything else other than bold, and a 3rd-party rasterizer on Windows is required. For me, I use MacType, a front-end of FreeType on Windows, and that's why I had a chance to meet and hence, observe those trivia.

From https://www.microsoft.com/typography/otspec/head.htm

Note that the macStyle bits must agree with the 'OS/2' table fsSelection bits. The fsSelection bits are used over the macStyle bits in Microsoft Windows.

We’re just following the specs. I’m fine with removing the warning but I’d strongly prefer the specs be updated especially since a major implementation might benefit from not following that statement.

This check also fails when there is a bitmap font with a 'bhed' table but no 'head' table (they're both the same format, so it should not be a big deal to check one instead of the other!)

source: gharchive/issue

authors: Pal3love anthrotype moyogo nriley

repo: fonttools/fonttools

license: mit

license_type: permissive

license_source: bigquery


text:
Forbid empty glyph classes

makeotf forbids empty glyph classes. Given
feature test {
    sub [] a' by b;
} test;

makeotf says:
syntax error at "]" [foo.fea 2]

The feaLib parser allows them, but then chokes with an error later on:
  File "/usr/local/lib/python3.9/site-packages/fontTools/otlLib/builder.py", line 491, in buildFormat2Subtable
    ruleAsSubtable.Backtrack = [
  File "/usr/local/lib/python3.9/site-packages/fontTools/otlLib/builder.py", line 492, in <listcomp>
    st.BacktrackClassDef.classDefs[list(x)[0]]
IndexError: list index out of range

EXCEPT WHEN IT DOESN'T:
$ cat foo.fea
feature test {
    sub [a] by [];
} test;
$ fonttools feaLib -o stupid.otf foo.fea AGaramondPro-Regular.otf
$

While that's a cute way to delete a glyph, we now have sub ... by NULL so nobody should be relying on this unintended consequence, and we should follow the makeotf behaviour.

Oh, OK. So we actually have a test which not only ensures we can have empty glyph classes, but actively uses the empty glyph classes in pos rules. Right. Right.

Come to think of it, we need to allow empty glyph classes in GDEF tables, so this is a non-starter.  I'll instead forbid them at the point of use. But I'd still like to hear the rationale for allowing pos @something [].

Already in 2019 I had no collection of ever writing this code or what it was for. I won’t object if you want to change it, if it breaks something we will eventually find out.

source: gharchive/pull-request

authors: khaledhosny simoncozens


text:
On-demand DNS fetching

Yush G, [2024-02-25 08:37]
would be nice to have on demand fetching — that way we could even have like, a ratelimited reload button on the corner of each record, that people could double check that that dkim key is still the case rn

Also add a 10 sec cooldown

Olof, [2024-02-25 08:41]
should we also do re-fetching from DNS when someone uploads an already known domain/selector-pair?
(note that then, popular domains such as twitter, will be re-fetched all the time, as almost everyone has them in their inbox)
Yush G, [2024-02-25 08:48]
yeah maybe we can have a 1hr cooldown for the email uploads and a 10 sec cooldown for the refresh button?

repo: foolo/dkim-lookup

license: MIT

license_source: github-api


text:
styling/positioning issues with overlay

two problems. 1) is that when the overlay drops over another element, the overlay isn't the topmost image. I see in the docs that there is an alwaysOnTop property but I can't seem to get it set, as Angular is name mangling the property names.    I've tried alwaysontop, always-on-top, alwayson-top and always-ontop.  Gear still showing through.
 <overlay-date-picker id="lodate" class="customDatePicker" [date]="params.lodate"
                       (date-changed)="params.lodate=$event.detail.value"
                       auto-confirm="true"
                       always-on-top="true"
  ></overlay-date-picker>

The other problem is how to move the overlay over when it is on the right side.  I don't know what to do to set the right css properties in the shadow dom.

When

problem 1: Is on the icon, that is shining through, by css a z-index set?

problem 2: Do you see the same problem with other elements that also depend on polymer's IronOverlayBehaviour?

I tried setting the z-index on both the underlying components (a low
zindex) and on the overlay-date-picker (a high zindex). Same difference.

I don't have any other elements at this time that use the
Iron-Overlay-Component.

On Fri, Feb 23, 2018 at 12:01 PM, fooloomanzoo notifications@github.com
wrote:

problem 1: Is on the icon, that is shining through, by css a z-index
set?
problem 2: Do you see the same problem with other elements that also
depend on polymer's IronOverlayBehaviour
https://github.com/PolymerElements/iron-overlay-behavior?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fooloomanzoo/datetime-picker/issues/37#issuecomment-368070830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCeb_yRQRuepxUoU63a_eE6wyu1g6HSks5tXu7zgaJpZM4SQAZ1
.

the problem might be that the z-index is set on that icon-button at all, and you might have to unset it, because IronOverlayBehavior is working with that property. The other problems might be related to IronOverlayBehavior itself. One thing about the styling the ShadowDom: you won't be able to style it from outside, because that's the reason for having a ShadowDom. If I can reproduce your problem and know about how to fix it I let you know.

@jjarrell56 In the newst version I made some changes on the iron-overlay-implementation. Could you please check, if this solves your problem? If it doesn't could please post an example how to recreate this issue?

I pulled down the latest code and

Sliding the drop down to the left when picker is tight to the right side of the browser is working.
I took the z-index off the gear and the problem still remains.
I lost my custom styling. I'll go back to this.
When you have two overlay-date-pickers close together there is a bit of awkwardness as the overlay from the first drop down, will be close to the 2nd date.  I'll try some z stuff and see how it goes.

I would like to get this in your hands, i'm sure it'd be easier for you to diagnose. Simplest thing would be for you would be for me to open up my repo.  It's not a big app and for this part, it's only the client part you'd need to see.  Let me know if you'd just prefer a demo repo.  I love the work your doing.

The problem I have is that I can not reproduce the issue

I started to use the codepen, but I wasn't able to get the needed
references to paper-icon-button and I wasn't able to figure it out right
away.
I've got to take up a couple of other tasks but I will get back to this
shortly.
Thank you for your help.
On Mon, Feb 26, 2018 at 8:59 PM, fooloomanzoo notifications@github.com
wrote:

The problem I have is that I can not reproduce the issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fooloomanzoo/datetime-picker/issues/37#issuecomment-368719801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCeb7ECda7mKDjddrj3Uh8ZyNFfvdQCks5tY2GGgaJpZM4SQAZ1
.

I made a small update to fix some sizing issues. In the codepen there are now paper-icon-buttons included, so it would be nice if try to find an example where the issue occures.

I can't get to this for a couple of days, but one of my colleagues exposed
the client site at
https://stg-portal.pcamerica.com
It doesn't have any database connected to it, so the app doesn't actually
work but you can see what is happening, see pickers in top right.
Depending on how wide your browser will affect if the date time drop down
get's over a gear.
Maybe, looking at it in Chrome/Devtools can give you some insight.
I'll get back to the codepen as soon as I can.
On Wed, Feb 28, 2018 at 5:07 PM, fooloomanzoo notifications@github.com
wrote:

I made a small update to fix some sizing issues. In the codepen
https://codepen.io/fooloomanzoo/pen/RxqNOb there are now
paper-icon-buttons included, so it would be nice if try to find an
example where the issue occures.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fooloomanzoo/datetime-picker/issues/37#issuecomment-369400194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCeb6V3dEAQHwjaDBodWbnVEoTp2Q9Pks5tZc43gaJpZM4SQAZ1
.

Hi, I could solve your problem by setting for one of the outer divs the z-index to 1:

It must have something to to that these divs are separating your title-area from the content-part and so relatively seen the layers are separated. paper-icon-button has by default an z-index set and maybe that is conflicting with the given z-index from the iron-overlay-behavior. You could do it like in the screenshot, but I would give the advice to rethink the layout itself, bring toolbar and content together and don't use so many divs as containers. You could use polymer's app-header-layout also with a scrolling region for your content? app-header-layou#scrolling-region And if you are using the flexbox-layout extensively that could slow down the performance drastically, especially if don't really use it what it is good for, to fit your content in another frame. Maybe that would also solve that issue and it would be cleaner, than setting to each layer the z-index.

Thank you for the advice.  I was able able to fix the problem related to
the gear showing through.
Yes, I do use too many divs, but some of what you are seeing angular
putting in even more divs.  I have found that working with the flexbox I've
had to use divs in some contexts to actually just to it to work.
I take it that your not an advocate of flexbox, what do you suggest as an
alternative... CSS Grid?  I've continued to work with flexbox because
that's kind of what I know.  I'm open minded.  I'm a far better developer
than designer.
On Thu, Mar 1, 2018 at 3:14 PM, fooloomanzoo notifications@github.com
wrote:

Hi, I could solve your problem by setting for one of the outer divs the
z-index to 1:
[image: image]
https://user-images.githubusercontent.com/9318952/36866362-5d3071bc-1d92-11e8-9880-de45cc40a623.png
It must have something to to that these divs are separating your
title-area from the content-part and so relatively seen the layers are
separated. paper-icon-button has by default an z-index set and maybe that
is conflicting with the given z-index from the iron-overlay-behavior. You
could do it like in the screenshot, but I would give the advice to rethink
the layout itself, bring toolbar and content together and don't use so many
divs as containers. You could use polymer's app-header-layout also with a
scrolling region for your content? app-header-layou#scrolling-region
https://www.webcomponents.org/element/PolymerElements/app-layout/demo/app-header-layout/demo/scrolling-region.html
And if you are using the flexbox-layout extensively that could slow down
the performance drastically, especially if don't really use it what it is
good for, to fit your content in another frame. Maybe that would also solve
that issue and it would be cleaner, than setting to each layer the z-index.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fooloomanzoo/datetime-picker/issues/37#issuecomment-369716632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCeb8wjGJZKmi9y9P0kp7hxIuY4lguaks5taFaagaJpZM4SQAZ1
.

flexbox is very good for styling. I just meant that the amount of nodes in a website can slow down your website. On your side your could achieve the same with far less containers. You also don't use the full advantages of flexbox, for example to make it responsable to the view width or the view height. You could achieve that by flex-wrap and taking advantage of flex-base. For a header of a node, sometimes positioning it absolutely could be easier than positioning it statically if you want to make the header stay above the content field. When you are already using polymer's app-layout you could have a look at the shop app how they realize a mostly compatible grid-layout in combination with toolbars and drawers and so on.

repo: fooloomanzoo/datetime-picker


text:
Update classes

Discord updated quite a few classes, breaking some parts of this theme. This PR switches the old classes for the new classes in place using ClassUpdate.

thanks :)

authors: Saltssaumure fooooooooooooooo


text:
SFApiRequestError: Request failed with status code 500

Hi guys,
When I try to generate code, I have this error message "SFApiRequestError: Request failed with status code 500". I have a company proxy that may block the call. Is there a way to see which url is being called ?

Hi abrantes23, yes I enabled Einstein for Developers on my local VS Code, but i got this error.
Ok i'll try to use it from "Code Builder".
On my local vscode, i still have the issue event if einstein is white :

Hello!  You can enable the debug logging via the extensions settings and then you can see the specific API endpoint we are calling from the developer tools (console).

Closing this issue out now as it's been a couple of weeks without progress.  @elliot41 please reopen if you'd like to continue debugging the issue. Thanks!

@BhavsarShivam in the better late then never department please checkout my comment on https://github.com/forcedotcom/Einstein-GPT-for-Developers/issues/60.

repo: forcedotcom/Einstein-GPT-for-Developers


text:
sfdx force:source:deploy:report is throwing The org cannot be found

Summary
sfdx force:source:deploy:report sometimes fail with this error: ERROR running force:source:deploy:report:  Metadata API request failed: The org cannot be found
This started to happen after we upgrade to version 7.165 from version 7.140
Steps To Reproduce:
run sfdx force:source:deploy:report
System Information

Which shell/terminal are you using? bash

›   Warning: sfdx-cli update available from 7.165.0 to 7.166.1.
{
"cliVersion": "sfdx-cli/7.165.0",
"architecture": "linux-x64",
"nodeVersion": "node-v16.17.0",
"pluginVersions": [
"@jayree/sfdx-plugin-manifest 2.2.10 (user)",
"@jayree/sfdx-plugin-prettier 1.1.7 (user)",
"@oclif/plugin-autocomplete 1.3.0 (core)",
"@oclif/plugin-commands 2.2.0 (core)",
"@oclif/plugin-help 5.1.12 (core)",
"@oclif/plugin-not-found 2.3.1 (core)",
"@oclif/plugin-plugins 2.1.0 (core)",
"@oclif/plugin-update 3.0.0 (core)",
"@oclif/plugin-version 1.1.2 (core)",
"@oclif/plugin-warn-if-update-available 2.0.4 (core)",
"@oclif/plugin-which 2.1.0 (core)",
"alias 2.1.0 (core)",
"apex 1.2.0 (core)",
"auth 2.2.3 (core)",
"community 2.0.0 (core)",
"config 1.4.17 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.1.2 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.2.0 (core)",
"schema 2.1.1 (core)",
"signups 1.2.0 (core)",
"source 2.0.12 (core)",
"telemetry 2.0.0 (core)",
"templates 55.1.0 (core)",
"trust 2.0.3 (core)",
"user 2.1.0 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"salesforce-alm 54.8.1 (core)",
"sfdx-git-delta 5.0.7 (user)",
"sfdx-jayree 4.3.4 (user)",
"sfpowerkit 5.0.0 (user)"
],
"osVersion": "Linux 5.10.60.1-microsoft-standard-WSL2",
"shell": "bash",
"rootPath": "/usr/local/lib/node_modules/sfdx-cli"
}
Additional information

We are seeing exactly the same, there doesn't seem to be any pattern to this, it makes our deployment pipelines fail from time to time.

We also see the 'org cannot be fount error' message since a couple of weeks. We see it with the sfdx force:source:deploy command and sfdx V7.156.1.
error: ERROR running force:source:deploy:  Metadata API request failed: The org cannot be found

We are now also seeing this on other commands; we use the sfpowerkit plugin to create a pool of scratch orgs and our pipeline throws this error intermittendly:
ERROR running sfpowerkit:pool:create:  Unable to execute command .. Domain Not Found: The org cannot be found

This is on CLI 7.163.0:
{
  "cliVersion": "sfdx-cli/7.163.0",
  "architecture": "linux-x64",
  "nodeVersion": "node-v16.13.1",
  "pluginVersions": [
    "@jayree/sfdx-plugin-legacy 1.1.0 (user)",
    "@jayree/sfdx-plugin-manifest 2.3.0 (user)",
    "@jayree/sfdx-plugin-prettier 1.2.0 (user)",
    "@oclif/plugin-autocomplete 1.3.0 (core)",
    "@oclif/plugin-commands 2.2.0 (core)",
    "@oclif/plugin-help 2.2.3 (user)",
    "@oclif/plugin-not-found 2.3.1 (core)",
    "@oclif/plugin-plugins 2.1.0 (core)",
    "@oclif/plugin-update 3.0.0 (core)",
    "@oclif/plugin-version 1.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.4 (core)",
    "@oclif/plugin-which 2.1.0 (core)",
    "alias 2.1.0 (core)",
    "apex 1.1.0 (core)",
    "auth 2.2.3 (core)",
    "community 2.0.0 (core)",
    "config 1.4.17 (core)",
    "custom-metadata 2.0.0 (core)",
    "data 2.1.1 (core)",
    "generator 2.0.2 (core)",
    "info 2.0.1 (core)",
    "limits 2.0.1 (core)",
    "org 2.0.7 (core)",
    "schema 2.1.1 (core)",
    "signups 1.2.0 (core)",
    "source 2.0.11 (core)",
    "telemetry 2.0.0 (core)",
    "templates 55.1.0 (core)",
    "trust 2.0.3 (core)",
    "user 2.1.0 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
    "dxb 1.7.12 (user)",
    "salesforce-alm 54.7.1 (core)",
    "sfdmu 4.15.1 (user)",
    "sfdx-browserforce-plugin 2.9.1 (user)",
    "sfdx-jayree 4.3.18 (user)",
    "sfpowerkit 5.0.0 (user)",
    "texei-sfdx-plugin 1.17.0 (user)"
  ],
  "osVersion": "Linux 5.15.0-1019-azure",
  "shell": "bash",
  "rootPath": "/usr/local/lib/nodejs/lib/node_modules/sfdx-cli"
}

The same issue happens from time to time with command force:mdapi:deploy after upgrade from 7.129.0 to 7.164.2:
ERROR running force:mdapi:deploy: Metadata API request failed: The org cannot be found

Hi @mshanemc: is this something you can help with? I see this error at least daily in our CI pipeline

This error is being thrown from here:
https://github.com/forcedotcom/sfdx-core/blob/main/src/org/connection.ts#L265
When instantiating this class it tries to get the API version to use in requests from a local config value (sfdx config:set apiVersion=55.0 --global) or env var (SFDX_API_VERSION=55.0 sfdx force:org:create -).
If no config value or env var is found, it queries the org to get the max API version available and does a DNS check which is what is failing and makes it throw the "The org cannot be found" error.
Workaround: skip the DNS check by set the API version using config:set or env var mentioned as mentioned above.
We will require some logs of a deployment without setting the API version to see what URL the dns resolver is getting.
To enable debug mode just set the env var DEBUG to true, e.g.
export DEBUG=true
sfdx force:source:deploy ...

This might be related to this ongoing issue: https://status.salesforce.com/generalmessages/994

@cristiand391 thanks for the solution. We are not receiving the error anymore.
Should this be documented somewhere? Looks like SFDX_DISABLE_DNS_CHECK optimize the deployment process. There is no point in trying to DNS check every time the metadata API return InProgress while running force:source:deploy:report and the API version is already cached.
Do you think of any issue if we leave this setting true in our pipeline?

Multiple projects and environments experiencing this issue.  Can someone confirm that SFDX_DISABLE_DNS_CHECK actually exists? It's not listed in the documentation, and doesn't seem to completely fix the issue.

Same issue with force:source:deploy (sfdx-cli/7.177.1, GitHub action). Happens sporadically, no apparent pattern.

We are affected by this too. A complete waste of CI/CD pipeline runtime

We're experiencing this issue as well:
ERROR running force:source:deploy:  Metadata API request failed: The org cannot be found
Tried SFDX_DISABLE_DNS_CHECK=trueand setting the API Version and even tried older CLI Versions (7.178.0, 7.175.0, and 7.170). Nothing helped.
Different Salesforce Orgs, same error

Impacting CI/CD pipeline. Any known workaround?
ERROR running force:source:deploy: Metadata API request failed: The org cannot be found

Thank you very much @cristiand391 !!!!
Workaround works in my pipeline
npm install sfdx-cli --global
sfdx config:set apiVersion=56.0 --global
export SFDX_DISABLE_DNS_CHECK=true

Brilliant thanks @Inakihu @ @cristiand391. Resolved

Still encountering the issue on any of my connected issues. It is also incredibly frequent for me. From 10 deployments maybe around 2 even start and non can keep the connection till the end. Issue occurs with all source commands: retrieve, deploy, push, pull
I set the recommended vars and running the recommended LTS node version.

Same here.
I tried everything posted here. I tried changing the version of Salesforce CLI and Node JS to older versions, but nothing works...

I have this error

Azure Devops Pipelines with Hosted Agent (ubuntu-latest)?

Azure Devops Pipelines with Hosted Agent (ubuntu-latest)?

Yes

I'm looking at this, in the screenshot @HerrX2000 posted above I see the err is coming from the deploy library so it might be skipping the env var. Can someone post the full debug of a force:source:push?

I resolved the problem (at least, for the moment) using older versions from Node JS and Salesforce CLI, 18.12.1 and 7.155.1, and it seems that works, 3 of 3 deployments without errors. I use the SFDX_DISABLE_DNS_CHECK=true but 'm not sure if it do something.

@cristiand391 thanks for pointing out that it might be skipping the env var. Indeed my .bashrc was wrong. It set the var for the bash environment, instead of as global env var. It now works, thank you very much.
Wrong .bashrc:
SFDX_DISABLE_DNS_CHECK=true
export $SFDX_DISABLE_DNS_CHECK

Correct .bashrc line:
export SFDX_DISABLE_DNS_CHECK=true

The export is mandatory, otherwise the variable is not available within the context of sfdxx.

Following.  We are also getting the same error and unfortunately I am still getting the same after adding export SFDX_DISABLE_DNS_CHECK=true

Same result as above. 'export SFDX_DISABLE_DNS_CHECK=true' Implemented. However, unresolved.

npm install sfdx-cli --global

sfdx config:set apiVersion=56.0 --global

export SFDX_DISABLE_DNS_CHECK=true

Unfortunately, this doesn't remediate.
Code deploys, however pipelines fails.

To double check if the variable is exported correctly, you can run export | grep SFDX.
@ZanePearton @derrick-ejan-rs

Maybe this helps. My deployment now shows (node:65603) Warning: Network error occurred.  Continuing to poll.. Maybe its a symptom of how the deploy library handles short network outages. I am on WIFI, so this could be what caused the DNS check to fail for me.

To confirm that the DNS check is being skipped you set the debug env var to only show the logs from the domain resolver, you should see sf:MyDomainResolver DEBUG SFDX_DISABLE_DNS_CHECK set to true. Skipping DNS check... in the logs.
Here's an example running:
DEBUG=sf:MyDomainResolver SFDX_DISABLE_DNS_CHECK=true sfdx force:source:deploy -u easy-spaces --sourcepath es-base-objects/

@cristiand391 thanks that looks like it worked for me.

do you have any fix to Metadata API request failed: The org cannot be found"? This is a blocker for our CI pipelines

shoud we try to use export SFDX_DISABLE_DNS_CHECK=true? Is this an official workaround for this problem?

or is there any different command which works fine, like sfdx force:beta:source:push to have it stable?

@bdovh yes, I mentioned it here:
https://github.com/forcedotcom/cli/issues/1713#issuecomment-1298701282
that env var should work for all commands as the domain resolver is the same.

shoud we try to use export SFDX_DISABLE_DNS_CHECK=true? Is this an official workaround for this problem?

@bdovh  yes that is what worked for me. We are using Azure pipelines.

shoud we try to use export SFDX_DISABLE_DNS_CHECK=true? Is this an official workaround for this problem?

@bdovh yes that is what worked for me. We are using Azure pipelines.

I am using Github Action CI pipelines and it still doesn't help. Well, it randomly fails, not every time, but once per two tries

So far this has been working for me in GitHub Actions
      - name: Deploy without test classes
        shell: bash
        env:
          SFDX_DISABLE_DNS_CHECK: true
        run: >-
          sfdx force:source:deploy -x ${{env.PACKAGEXML_FILE}} -u
          ${{env.SF_USERNAME}} -w 10000 --verbose --loglevel fatal

Still experience issues with network connection during the long deployment. After adding export SFDX_DISABLE_DNS_CHECK=true in the pipeline we don have "The org cannot be found" error, but there is another one
ERROR running force:source:deploy:report:  Metadata API request failed: request to ....sandbox.my.salesforce.com/services/Soap/m/56.0 failed, reason: Client network socket disconnected before secure TLS connection was established

So far this has been working for me in GitHub Actions
      - name: Deploy without test classes
        shell: bash
        env:
          SFDX_DISABLE_DNS_CHECK: true
        run: >-
          sfdx force:source:deploy -x ${{env.PACKAGEXML_FILE}} -u
          ${{env.SF_USERNAME}} -w 10000 --verbose --loglevel fatal

let me try that one

shoud we try to use export SFDX_DISABLE_DNS_CHECK=true? Is this an official workaround for this problem?

@bdovh yes that is what worked for me. We are using Azure pipelines.

I am using Github Action CI pipelines and it still doesn't help. Well, it randomly fails, not every time, but once per two tries

This is what Salesforce support has confirmed as official workaround.

FYI: sfdx v7.180.0 (latest-rc) includes a fix for this, see rel notes:
https://github.com/forcedotcom/cli/tree/main/releasenotes/sfdx#71800-dec-8-2022-stable-rc
ERROR running force:source:deploy:report: Metadata API request failed: request to ....sandbox.my.salesforce.com/services/Soap/m/56.0 failed, reason: Client network socket disconnected before secure TLS connection was established

@steals that's a different network error, if you can please open a new GH issue and provide a debug log of the CLI.

Hi @cristiand391
I know it is a stretch question, but based on a lot of the comments above, it seems also to happen for force:source:deploy and not just force:source:deploy:report.
Do you know if the fix will also apply to force:source:deploy?

@nickytorstensson the fix was done on the sfdx-core library: https://github.com/forcedotcom/sfdx-core/pull/712
The fix should apply to all commands that interact with an org as those are done using sfdx-core.
As I mentioned in the comment below, the fix is included in the current release candidate, not in latest stable (the one most people use).
See: https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli_rc.htm
If you are still getting the The org cannot be found err  with sfdx >= v7.180.0, please let us know.

sfdx 7.180.0 is now stable/GA with fixes for this issue. If you had been holding off installing during the RC period, you can now upgrade!

@nickytorstensson the fix was done on the sfdx-core library: forcedotcom/sfdx-core#712
The fix should apply to all commands that interact with an org as the connections to it are done using sfdx-core.
As I mentioned in the comment below, the fix is included in the current release candidate, not in latest stable (the one most people use). See: https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli_rc.htm
If you are still getting the The org cannot be found err with sfdx >= v7.180.0, please let us know.

I have a question, does it fix also the sfdx force:source:push command?

@bdovh yes, it should.

is 7.180 GA?
Why when I try to execute the script
node --version
npm install sfdx-cli --global
export SFDX_DISABLE_DNS_CHECK=true
echo "Version of SFDX CLI is: $(sfdx --version)"
it installs the version
Version of SFDX CLI is: sfdx-cli/7.179.0 linux-x64 node-v16.18.1

@bdovh yes, you can see the latest tag points to 7.180.0:
➜  sf-plugin-api git:(cd/cleanup) ✗ npm show sfdx-cli dist-tags
{
  latest: '7.180.0',
  'latest-rc': '7.181.1',
  dev: '7.177.0-dev.4',
  'dev-rc': '7.177.0-dev.4'
}

authors: HerrX2000 Inakihu JFloresGarcia RodEsp TonyWhiteSMS Yurii-Zakharov ZanePearton bdovh cristiand391 cromwellryan derrick-ejan-rs jdgirald joernflath jverelst khushaldave maristei nickytorstensson slaght srinivasan-kr steals stoevie

repo: forcedotcom/cli


text:
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined

Getting this error when retriving components using VS code  sfdx force:source:retrieve --manifest
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined
Here us Package.XML ==>

*
ApexClass

*
ApexComponent

*
ApexPage

*
ApexTestSuite

*
ApexTrigger

*
AuraDefinitionBundle

*
LightningComponentBundle

*
StaticResource

48.0

CLI version ==>
sfdx-cli/7.57.1-dbf54fc584 win32-x64 node-v10.15.3

@grdixit65 it looks like one of the metadata types you are using is failing can you please pinpoint the type that you are unable to retrieve and we can get the team that owns it to fix the issue. thank you for reporting

@clairebianchi it is "AuraDefinitionBundle" causing issue.

Hi, for me it is happening when I tried with  in package.xml
What I was trying:
Creare a blank project in VS code with SF extension and authorize a developer instance and then retrieving the components based on package.xml. I tried with class, trigger, TestSuite, Aura comp etc but only when I add lwc component with * (to retrieve all lwc in my org) I get that error.
Version is 47.0 in package.xml.
Let me know if you need any more details.

Hi,
I am facing same issue and it occurs when "LightningComponentBundle" is present in manifest.
can this be please addressed at the earliest?
version 49.0

I'm experiencing the same issue. It seems to have started when the dev org I'm working from updated to Winter 2021 (version 50.0). Tried changing the version on my package.xml file, but that didn't fix it. Only worked after removing the "LightningComponentBundle" section. Ok for now, as I'm working on apex, but I rely on VS Code for working with LWCs, as well, so the sooner this can get fixed the better.

Same issue here, addding "LightningComponentBundle" to package.xml throws this error.
Cannot read property 'fileName' of undefined

This is a duplicate of #496 so I'll close it out in favor of that one, which was reported first.  The fix will be in the next patch release.

Actually this one was first, sorry.  Doesn't matter...it'll be fixed asap.

Also having the same issue
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined
sfdx-cli 7.82.0 (core)

Also having the same issue
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined
sfdx-cli 7.82.0 (core)

Same error for me using on Window OS.
sfdx-cli/7.83.0

Same error for me using on Window OS.
sfdx-cli/7.83.0

I'm experiencing this issue too

I'm experiencing this issue too

I am experiencing this issue.
I needed to remove

*
AuraDefinitionBundle

From my package.xml for it to work.
Error I am receiving when running it while in there is:
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined

*** Internal Diagnostic ***
TypeError: Cannot read property 'fileName' of undefined
at Function.getMetadataFileNameFromBundleFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:42:48)
at Function.getPathFromBundleTypeFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:36:43)
at AuraDefinitionBundleMetadataType.getDefaultAggregateMetadataPath (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\metadataTypeImpl\bundleMetadataType.js:31:52)
at SourceWorkspaceAdapter.processMdapiFileProperty (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceWorkspaceAdapter.js:286:59)
at C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:166:22
at Array.forEach ()
at MdapiPullApi._syncDownSource (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:158:31)
at SourceRetrieve.retrieveFromManifest (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:177:64)
at async SourceRetrieve.retrieve (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:57:27)
at async SourceRetrieveCommand.execute (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieveCommand.js:32:16)
at async SourceRetrieveCommand.execLegacyCommand (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:149:29)
at async SourceRetrieveCommand.run (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\commands\force\source\retrieve.js:32:16)
at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules@salesforce\command\lib\sfdxCommand.js:93:40)
at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules@oclif\config\lib\config.js:173:24)
at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\main.js:27:9)
at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\command.js:43:20)
Outer stack:
at Function.wrap (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\node_modules@salesforce\core\lib\sfdxError.js:171:27)
at SourceRetrieveCommand.catch (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:248:46)
at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules@salesforce\command\lib\sfdxCommand.js:97:13)
at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules@oclif\config\lib\config.js:173:24)
at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\main.js:27:9)
at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\command.js:43:20)
at async Object.run (C:\Program Files\Salesforce CLI\client\dist\cli.js:32:20)

sfdx:SourceRetrieveCommand ERROR [
sfdx:SourceRetrieveCommand   '\u001b[1mERROR running force:source:retrieve: \u001b[22m',
sfdx:SourceRetrieveCommand   "\u001b[31mCannot read property 'fileName' of undefined\u001b[39m",
sfdx:SourceRetrieveCommand   '\u001b[31m\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m*** Internal Diagnostic \u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m\u001b[39m\n' +
sfdx:SourceRetrieveCommand     "\u001b[31mTypeError: Cannot read property 'fileName' of undefined\u001b[39m\n" +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.getMetadataFileNameFromBundleFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:42:48)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.getPathFromBundleTypeFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:36:43)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at AuraDefinitionBundleMetadataType.getDefaultAggregateMetadataPath (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\metadataTypeImpl\bundleMetadataType.js:31:52)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceWorkspaceAdapter.processMdapiFileProperty (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceWorkspaceAdapter.js:286:59)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:166:22\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Array.forEach ()\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at MdapiPullApi._syncDownSource (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:158:31)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceRetrieve.retrieveFromManifest (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:177:64)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieve.retrieve (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:57:27)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.execute (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieveCommand.js:32:16)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.execLegacyCommand (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:149:29)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.run (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\commands\force\source\retrieve.js:32:16)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\command\lib\sfdxCommand.js:93:40)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\config\lib\config.js:173:24)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\main.js:27:9)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\command.js:43:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31mOuter stack:\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.wrap (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\node_modules\@salesforce\core\lib\sfdxError.js:171:27)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceRetrieveCommand.catch (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:248:46)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\command\lib\sfdxCommand.js:97:13)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\config\lib\config.js:173:24)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\main.js:27:9)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\command.js:43:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Object.run (C:\Program Files\Salesforce CLI\client\dist\cli.js:32:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m***\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m\u001b[39m'
sfdx:SourceRetrieveCommand ] +50s

I am experiencing this issue.
I needed to remove

*
AuraDefinitionBundle

From my package.xml for it to work.
Error I am receiving when running it while in there is:
ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined

*** Internal Diagnostic ***
TypeError: Cannot read property 'fileName' of undefined
at Function.getMetadataFileNameFromBundleFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:42:48)
at Function.getPathFromBundleTypeFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:36:43)
at AuraDefinitionBundleMetadataType.getDefaultAggregateMetadataPath (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\metadataTypeImpl\bundleMetadataType.js:31:52)
at SourceWorkspaceAdapter.processMdapiFileProperty (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceWorkspaceAdapter.js:286:59)
at C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:166:22
at Array.forEach ()
at MdapiPullApi._syncDownSource (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:158:31)
at SourceRetrieve.retrieveFromManifest (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:177:64)
at async SourceRetrieve.retrieve (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:57:27)
at async SourceRetrieveCommand.execute (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieveCommand.js:32:16)
at async SourceRetrieveCommand.execLegacyCommand (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:149:29)
at async SourceRetrieveCommand.run (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\commands\force\source\retrieve.js:32:16)
at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules@salesforce\command\lib\sfdxCommand.js:93:40)
at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules@oclif\config\lib\config.js:173:24)
at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\main.js:27:9)
at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\command.js:43:20)
Outer stack:
at Function.wrap (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\node_modules@salesforce\core\lib\sfdxError.js:171:27)
at SourceRetrieveCommand.catch (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:248:46)
at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules@salesforce\command\lib\sfdxCommand.js:97:13)
at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules@oclif\config\lib\config.js:173:24)
at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\main.js:27:9)
at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules@oclif\command\lib\command.js:43:20)
at async Object.run (C:\Program Files\Salesforce CLI\client\dist\cli.js:32:20)

sfdx:SourceRetrieveCommand ERROR [
sfdx:SourceRetrieveCommand   '\u001b[1mERROR running force:source:retrieve: \u001b[22m',
sfdx:SourceRetrieveCommand   "\u001b[31mCannot read property 'fileName' of undefined\u001b[39m",
sfdx:SourceRetrieveCommand   '\u001b[31m\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m*** Internal Diagnostic \u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m\u001b[39m\n' +
sfdx:SourceRetrieveCommand     "\u001b[31mTypeError: Cannot read property 'fileName' of undefined\u001b[39m\n" +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.getMetadataFileNameFromBundleFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:42:48)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.getPathFromBundleTypeFileProperties (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\bundlePathHelper.js:36:43)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at AuraDefinitionBundleMetadataType.getDefaultAggregateMetadataPath (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\metadataTypeImpl\bundleMetadataType.js:31:52)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceWorkspaceAdapter.processMdapiFileProperty (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceWorkspaceAdapter.js:286:59)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:166:22\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Array.forEach ()\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at MdapiPullApi._syncDownSource (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePullApi.js:158:31)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceRetrieve.retrieveFromManifest (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:177:64)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieve.retrieve (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieve.js:57:27)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.execute (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceRetrieveCommand.js:32:16)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.execLegacyCommand (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:149:29)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand.run (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\commands\force\source\retrieve.js:32:16)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\command\lib\sfdxCommand.js:93:40)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\config\lib\config.js:173:24)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\main.js:27:9)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\command.js:43:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31mOuter stack:\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at Function.wrap (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\node_modules\@salesforce\core\lib\sfdxError.js:171:27)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at SourceRetrieveCommand.catch (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:248:46)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\command\lib\sfdxCommand.js:97:13)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\config\lib\config.js:173:24)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\main.js:27:9)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\command.js:43:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m    at async Object.run (C:\Program Files\Salesforce CLI\client\dist\cli.js:32:20)\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m***\u001b[39m\n' +
sfdx:SourceRetrieveCommand     '\u001b[31m\u001b[39m'
sfdx:SourceRetrieveCommand ] +50s

Sorry how is this Closed or Fixed
The issue is still there.
the bad code is still there.
Fixing it means deploying it to the stable branch before Closing the Bug.

Also getting this error. Fresh install of sfcli and sf extensions pack in vscode.

Freshly installed VSCode and Salesforce Extensions pack.
Getting this error when trying to retrieve from manifest:
11:27:14.245 sfdx force:source:retrieve --manifest c:\Users\myUsername\VScode code\Partial\manifest\package.xml ERROR running force:source:retrieve:  Cannot read property 'fileName' of undefined
This is the error I get when trying to retrieve using Org Browser:
11:31:31.753 sfdx force:source:retrieve --json --loglevel fatal -m LightningComponentBundle:training {   "status": 1,   "name": "TypeError",   "message": "Cannot read property 'fileName' of undefined",   "exitCode": 1,   "commandName": "SourceRetrieveCommand",   "stack": "TypeError: Cannot read property 'fileName' of undefined\n    at Function.getMetadataFileNameFromBundleFileProperties (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\bundlePathHelper.js:42:48)\n    at Function.getPathFromBundleTypeFileProperties (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\bundlePathHelper.js:36:43)\n    at LightningComponentBundleMetadataType.getDefaultAggregateMetadataPath (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\metadataTypeImpl\\bundleMetadataType.js:31:52)\n    at SourceWorkspaceAdapter.processMdapiFileProperty (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourceWorkspaceAdapter.js:286:59)\n    at C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourcePullApi.js:166:22\n    at Array.forEach (<anonymous>)\n    at MdapiPullApi._syncDownSource (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourcePullApi.js:158:31)\n    at SourceRetrieve.retrieveFromManifest (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourceRetrieve.js:177:64)\n    at async SourceRetrieve.retrieve (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourceRetrieve.js:65:27)\n    at async SourceRetrieveCommand.execute (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourceRetrieveCommand.js:32:16)\n    at async SourceRetrieveCommand.execLegacyCommand (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\ToolbeltCommand.js:149:29)\n    at async SourceRetrieveCommand.run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\commands\\force\\source\\retrieve.js:32:16)\n    at async SourceRetrieveCommand._run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@salesforce\\command\\lib\\sfdxCommand.js:93:40)\n    at async Config.runCommand (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\config\\lib\\config.js:173:24)\n    at async Main.run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\command\\lib\\main.js:27:9)\n    at async Main._run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\command\\lib\\command.js:43:20)\nOuter stack:\n    at Function.wrap (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\node_modules\\@salesforce\\core\\lib\\sfdxError.js:171:27)\n    at SourceRetrieveCommand.catch (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\salesforce-alm\\dist\\ToolbeltCommand.js:248:46)\n    at async SourceRetrieveCommand._run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@salesforce\\command\\lib\\sfdxCommand.js:97:13)\n    at async Config.runCommand (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\config\\lib\\config.js:173:24)\n    at async Main.run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\command\\lib\\main.js:27:9)\n    at async Main._run (C:\\Program Files\\Salesforce CLI\\client\\node_modules\\@oclif\\command\\lib\\command.js:43:20)\n    at async Object.run (C:\\Program Files\\Salesforce CLI\\client\\dist\\cli.js:32:20)",   "warnings": [] }

Can you try the retrieve from vscode after enabling an experimental setting?
Experimental: Deploy Retrieve  is the setting
id salesforcedx-vscode-core.experimental.deployRetrieve

@z4chry @nbparrell Hi, I'm having the hardest time reproducing this issue on windows. I'm running
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.7 (core)
config 1.2.4 (core)
generator 1.1.5 (core)
salesforcedx 50.16.1 (core)
├─ limits 1.0.3 (core)
├─ schema 1.0.3 (core)
├─ user 1.0.11 (core)
├─ apex 0.1.4 (core)
├─ custom-metadata 1.0.11 (core)
├─ templates 50.4.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
└─ salesforce-alm 50.16.1 (core)
sfdx-cli 7.86.3 (core)
telemetry 1.0.1 (core)

with 3 different package.xml,
LWC only,
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
     <types>
        <members>*</members>
        <name>LightningComponentBundle</name>
    </types>
    <version>51.0</version>
</Package>

Aura only,
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>AuraDefinitionBundle</name>
    </types>
    <version>51.0</version>
</Package>

Aura + LWC
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>AuraDefinitionBundle</name>
    </types>
    <types>
        <members>*</members>
        <name> LightningComponentBundle</name>
    </types>
    <version>51.0</version>
</Package>

I'm able to sfdx force:source:retrieve -x package.xml without any errors, I'm able to sfdx force:source:retrieve -m LightningComponentBundle and sfdx force:source:retrieve -m AuraDefinitionBundle without errors. I'm even running $ sfdx force:source:retrieve -m LightningComponentBundle:lib "lib" is my bundle name without errors
@nbparrell while your fix above is no longer valid for that file, we are now normalizing all of the paths, and then path.sep should properly match, no matter where the path came from, or where it's going to.
If you see anything that I'm doing differently or that I'm missing please let me know!

@WillieRuemmele
So when going through and debugging, the issue I was seeing was that the file being retrieved was using '/' for it's path and not being normalized to '' which as you have said would eliminate the need for a different path.sep. As for what you are doing different I am not sure. I have very limited knowledge regarding this extension, I had some free time to trouble shoot and fix my issue so that I could set up the environment on my computer. I am also not sure how the paths are initially being generated when pulling down from the org which is what I would assume is causing the issue, though I can't be sure since again I am not particularly familiar with the over all process.
Where are you normalizing the paths so that you would only need to use the path.sep ''. Is there a chance that certain naming conventions used when naming the bundles might interfere with the normalization process? Again shooting in the dark a bit but that would be the rabbit hole I would go down just to double check.

Thanks for the response, I don't expect you to be an expert in how our tools work ;). Are you still seeing this issue on the cli versions I posted above? I'm quite confused on the activity on this issue because I'm not able to reproduce it, but obviously plenty of people are.

So one thing that I should mention, though I am not sure if it is a potential issue, is that I am storing my org on a seperate hard drive from the cli. So my project is on my D: drive where as the cli and visual studio code is on the C: drive.
I am currently on version 50.16.0 though I have not removed the changes or made any updates to that code so I am not seeing that issue. One issue I am seeing now is that when I try to retrieve from the manifest after the initial retrieval I am getting this error:

ERROR running force:source:retrieve:  Unexpected file found in package directory: D:\MedicalAlertSF\ConnectAmericaPartial\force-app\main\default\aura\AccountChangesPage\AccountChangesPage.auradoc\AccountChangesPage.auradoc
*** Internal Diagnostic ***

UnexpectedFileFound: Unexpected file found in package directory: D:\MedicalAlertSF\ConnectAmericaPartial\force-app\main\default\aura\AccountChangesPage\AccountChangesPage.auradoc\AccountChangesPage.auradoc
    at Workspace.isValidSourcePath (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:171:35)
    at Workspace.handleArtifact (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:154:18)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:144:36)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:146:17)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:146:17)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:146:17)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:146:17)
    at async Workspace.walk (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:146:17)
    at async Workspace.walkDirectories (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:131:13)
    at async Workspace.initializeStateFull (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:99:9)
    at async Workspace.init (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\workspace.js:46:17)
    at async Function.create (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\kit\lib\creatable.js:31:9)
    at async SourcePathStatusManager.init (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourcePathStatusManager.js:161:26)
    at async Function.create (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\kit\lib\creatable.js:31:9)
    at async SourceWorkspaceAdapter.init (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\lib\source\sourceWorkspaceAdapter.js:60:21)
    at async Function.create (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\kit\lib\creatable.js:31:9)
Outer stack:
    at Function.wrap (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\node_modules\@salesforce\core\lib\sfdxError.js:171:27)
    at SourceRetrieveCommand.catch (C:\Program Files\Salesforce CLI\client\node_modules\salesforce-alm\dist\ToolbeltCommand.js:248:46)
    at async SourceRetrieveCommand._run (C:\Program Files\Salesforce CLI\client\node_modules\@salesforce\command\lib\sfdxCommand.js:97:13)
    at async Config.runCommand (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\config\lib\config.js:173:24)
    at async Main.run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\main.js:27:9)
    at async Main._run (C:\Program Files\Salesforce CLI\client\node_modules\@oclif\command\lib\command.js:43:20)
    at async Object.run (C:\Program Files\Salesforce CLI\client\dist\cli.js:32:20)
******

I too have this issue and have cli installed on C: and Workspace on D: (New Laptop build WIN10 Pro)
I am not following the convo closely so sorry if out of touch.
I fixed it by replacing the code with '/' as per @nbparrell comment.
or maybe it is fixed in the code and I am just seeing my changes are now the same as the new DL codebase.
personally I am having issue with a whole other set of problems (Many problems, solve one anothe pops up.
BTW the std install is not the latest version, and hence an update is required, but this procedure needs to be communicated to the masses.
I think the std download needs to be made from stable version.

BTW the std install is not the latest version, and hence an update is required, but this procedure needs to be communicated to the masses.
I think the std download needs to be made from stable version.

That would explain why it wasn't working yesterday after a fresh install of the plugins and vscode and was working fine today. Haven't had any issues with retrieving the Aura Bundles today.

Can you try the retrieve from vscode after enabling an experimental setting?
Experimental: Deploy Retrieve is the setting
id salesforcedx-vscode-core.experimental.deployRetrieve

@shetzel @WillieRuemmele Setting Experimental: Deploy Retrieve to true did fix the errors I was experiencing on sfdx-cli/7.83.0-eba9c6a927 win32-x64 node-v12.18.3. Alternatively, when I downgrade to sfdx-cli/7.81.0-7b953c80d1 win32-x64 node-v12.18.3 I didn't experience any errors.
All projects and program installations are located on the same drive.

I updated VS Code this morning and I can now retrieve Aura and LWC components

Encounter this error on sfdx force:source:pull, sfdx-cli/7.83.0-eba9c6a927 win32-x64 node-v12.18.3.  Have also enabled Experimental: Deploy Retrieve, to no effect.  Any updates?

Hi team , @mshanemc
I am using Illuminated Cloud 2 on Win.x64, and facing the same issue while try to retrieve metadata for SFDX project via OAuthen connection . Tools version are below
SFDX plugin --core
salesforcedx 48.10.1 (48.10.1)
sfdx-cli 7.106.3 (core):
package.xml

*
LightningComponentBundle

45.0

Error message
Retrieve Failed-Failed to retrieve metadata.-Status: FAILED - Message: TypeError - Cannot read property 'fileName' of undefined
Any update for this issue, please advice, thank a lot.
Cheers,
Kate

Hi @kateluu-comdev
you can checkout the soon-to-be-announced beta source plugin by installing it with sfdx plugins:install @salesforce/plugin-source , and uninstalling it with sfdx plugins:uninstall @salesforce/plugin-source that should resolve these metadata-specific issues you're seeing.
Let me know how it goes 👍

sfdx plugins:install @salesforce/plugin-source

Hi WillieRuemmele,
Thank for the suggestion , did apply the install and uninstall as propose, then got something new as below
Error Message
```
Failed to obtain the org list from the Salesforce CLI:
• status = 1
• message = Unexpected argument: --skipconnectionstatus
See more help with --help
**Log details**
when run the sfdx force:org:list --skipconnectionstatus --json

{
"status": 1,
"name": "Error",
"message": "Unexpected argument: --skipconnectionstatus\nSee more help with --help",
"exitCode": 1,
"commandName": "OrgListCommand",
"stack": "Error: Unexpected argument: --skipconnectionstatus\nSee more help with --help\n
at validateArgs (~\sfdx\node_modules\@oclif\parser
\lib\validate.js:10:19)\n    at Object.validate (~\sfdx\
node_modules\@oclif\parser\lib\validate.js:55:5)\n    at Object.parse (~
\AppData\Local\sfdx\node_modules\@oclif\parser\lib\index.js:28:7)\n    at OrgListC
ommand.parse (~\sfdx\node_modules\@oclif\command\lib\
command.js:86:41)\n    at OrgListCommand.init (~\sfdx\nod
e_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:196:44)
n    at async OrgListCommand.run (~\sfdx\node_modules\s
alesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:80:13)\n    at async
Config.runCommand (~\sfdx\client\7.106.3-4b5d171\node
modules\@oclif\config\lib\config.js:173:24)\n    at async Main.run (~\
AppData\Local\sfdx\client\7.106.3-4b5d171\node_modules\@oclif\command\lib\main.js:
27:9)\n    at async Main._run (~\sfdx\client\7.106.3-4b5
d171\node_modules\@oclif\command\lib\command.js:43:20)\n    at async Object.run (~\sfdx\client\7.106.3-4b5d171\dist\cli.js:114:21)\nOuter st
ack:\n    at Function.wrap (~\sfdx\node_modules\salesfor
ce-alm\node_modules\@salesforce\core\lib\sfdxError.js:151:27)\n    at OrgListCommand.c
atch (~\sfdx\node_modules\salesforce-alm\dist\Toolbelt
Command.js:246:46)\n    at async OrgListCommand._run (~\sf
dx\node_modules\salesforce-alm\node_modules\@salesforce\command\lib\sfdxCommand.js:8
5:13)\n    at async Config.runCommand (~\sfdx\client\7.1
06.3-4b5d171\node_modules\@oclif\config\lib\config.js:173:24)\n    at async Main.run (
~\sfdx\client\7.106.3-4b5d171\node_modules\@oclif\com
mand\lib\main.js:27:9)\n    at async Main._run (~\sfdx\
client\7.106.3-4b5d171\node_modules\@oclif\command\lib\command.js:43:20)\n    at asyn
c Object.run (~\sfdx\client\7.106.3-4b5d171\dist\cli.j
s:114:21)",
"warnings": []
}

Hi All,
Getting error after the Salesforce CLi got update to this version
sfdx-cli/7.113.0 win32-x64 node-v14.17.4
ERROR running force:source:deploy:  Cannot read property 'id' of undefined
Any help will be much appreciated, I tried to downgrade to the lower version, but it complains about "System cannot find the path specified"

Hi @hemrag07 while this error message is the same, that is a new bug. Could you please file a new information with all of the information


text:
Clarification on formioService

1)What is the purpose of adding an attribute called SERVICE in formio tag?
'<formio src="test.json" `service="?">'
2)Is there any working example using attribute SERVICE in formio tag?
3)Is it possible to invoke a custom function while loading a form ?,Without disturbing formioService
I.e.,  i want to preprocess the json and  also want to perform some preaction.
4)Is it Possible to extend the FormioService? In order to customize the action on the event
5)Wizard not rendered while giving json in API (src) format .

@anupriyaideas2it The idea of the service parameter is that you can extend the FormioService class, and then pass that into the directive so that it uses your extended class vs. the core service. This allows you to do some more flexible things to inject your custom logic within the Service functions. I think that answers 1-4.
5 sounds like a bug, and I will look into it.
Thanks,
Travis.


text:
Add support for DELIMITER syntax

Can you add support for syntax?
DELIMITER $$

CREATE PROCEDURE proc()
BEGIN
   /* */
END$$

DELIMITER ;

I need to write sql queries with this syntax and inconvenient to switch to Mysql Workbench every time.

Is there any solution to this yet?

forked and implemented by topic starter
https://marketplace.visualstudio.com/items?itemName=poreklo.vscode-mysql

@poreklo is there any way to get your feature merged into this project?

@poreklo is there any way to get your feature merged into this project?
Easy :-) It's only preprocess function https://github.com/poreklo/vscode-mysql/blob/d7d47e3da3966e01119890174d2bcf6140e09dcb/src/common/utility.ts#L32

repo: formulahendry/vscode-mysql


text:
add functions to upload/download certificates

Using the monitor API endpoints
/api/v2/monitor/system/certificate/download
/api/v2/monitor/vpn-certificate/local/import
Required to implement: https://github.com/fortinetdev/terraform-provider-fortios/pull/168

Hi @poroping ,
Thank you for contributing to Terraform FortiOS provider. /api/v2/monitor/system/certificate/download and /api/v2/monitor/vpn-certificate/local/import are monitor APIs. Monitor APIs are stateless, and we do not provide resources for stateless APIs. It will violate Terraform's purpose https://www.terraform.io/docs/language/state/purpose.html, and may make user confusing.
For monitor APIs, we have a solution of using generic resource: https://registry.terraform.io/providers/fortinetdev/fortios/latest/docs/resources/fortios_json_generic_api. We encourage user using this generic resource to handle monitor APIs to keep Terraform FortiOS provider's consistence.
Again, thank you for your contribution and great idea. You are very welcome to share your great thought and point out our problem. Please let me know if you have any questions.
Thanks,
Xing

authors: lix-fortinet poroping

repo: fortinetdev/forti-sdk-go


text:
Index builder does not recognize valid manifest entries

The index build currently warns for unknown entries in manifests like, categories, keywords, homepage and install. Those entries are valid as defined in the manifest reference in the fpm repository but not correctly recognized by the index builder.

I created a pydantic model of the fpm manifest a while ago in awvwgk/pyfpm, which allows to easily verify the correctness of a package manifest and extract the data in Python. Using this or a similar model would make it easy for the registry handle the package verification.

repo: fortran-lang/fpm-registry


text:
Add a feature to directly import a cURL request

Tell us about the task you want to perform and are unable to do so because the feature is not available
Currently the only way to make a request in APIDash is by using http request format.
Describe the solution/feature you'd like us to add
We can add a feature where it is possible to make a request using the cURL format

@ashitaprasad @animator I am working on this!

Ohh cool! Will close this


text:
Improving the UI further

Removed card and added separator in between list items.
Changed the search icon to with specified size and padding.

Before

After

Similar things can be done with other screens.

@heysadboy Please see the material guidelines https://material.io/guidelines/components/cards.html#cards-usage. You should not use cards here according to the guidelines

@mananwason Thanks for reviewing. I'll look it up.

@mananwason Hi. I realized instead of cards, the list items can just be separated by divider. It would be great if I could work on other similar issues.

I made the changes in pull request https://github.com/fossasia/open-event-android/pull/992

Can i work on this?

@sanketkumar1996 @heysadboy is already working on it.
You can pick up any other unassigned issue.

@the-dagger Hi. Solving this issue here. https://github.com/fossasia/open-event-android/pull/1017

authors: heysadboy mananwason saketkumar95 the-dagger

repo: fossasia/open-event-android


text:
Correct API request url

Corrects API endpoint for request in README file.

@niranjan94 Please review. Thanks!

@mariobehling Please review. Thanks :smile:

repo: fossasia/query-server


text:
ResponsiveMenu broke dropdown menu after return to original breakpoint

What should happen?
I have Responsive menu: accordion on mobile and dropdown on desktop. At first initializing dropdown works fine. After changing viewport size to mobile menu converts to accordion and it works fine as well. But when i return to desktop/dropdown version - dropdown initialize seems to be failed. When i hover on item that has dropdown - it opens, and when i move mouse out of the item it should disappear.
What happens instead?
Instead i've got console error, and submenu keep showing
Uncaught TypeError: Cannot read property 'autoclose' of null
foundation.dropdownMenu.js:150
Possible Solution

...
Test Case and/or Steps to Reproduce (for bugs)

Test Case: codePen
Foundation Docs for ResponsiveMenu has same issue - https://foundation.zurb.com/sites/docs/responsive-navigation.html#drilldown-dropdown-menu
Your Environment

Foundation version(s) used: 6.5.1
Browser(s) name and version(s): Chrome, FireFox, Edge
Device, Operating System and version: Windows 10
Link to your project:

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title and template are correctly filled.

Hi Alexey! Your codepen actually works, since it's currently linked to Foundation 6.5.0's javascript.
(But there's still a console-error though.)
Maybe it should be linked to 6.5.1 for demonstration purposes.
I'm struggling with the exact same issue. Do you know if there's a patch for this? Thanks, Andrej

Thank for correction. Replace with actual version.
For now, i've just cutted out autclose property, and the next closingTime property, since i'm not using it.
But still looking for the proper solution.

Thanks! I will try that too …

Same issue. "hasSub is not defined" in foundation.dropdownMenu.js
Alexey, could you please provide your temp solution?

Please test https://codepen.io/DanielRuf/pen/jJVjmz

See https://github.com/zurb/foundation-sites/pull/11715

Works for me! Thank you so much Daniel.
Alex.

Just adding that I am seeing the same issue in 6.5.3 while trying to upgrade some packaged.  Daniel's PR fixes the issue.  Will have to wait on it.  Thanks Daniel.

Hi @thejonroberts
You can use https://github.com/zurb/foundation-sites/pull/11715.patch or https://github.com/zurb/foundation-sites/pull/11715.diff with patch-package or patch to fix it in your projects.
There is currently no activity around Foundation Sites so the PR will not be merged so soon.

I appreciate the heads up, Daniel.  I was considering using a fork, but ultimately decided to just disable the hover open behavior to work around this problem.
In case anyone else is looking for that solution, you can set data-disable-hover=true, data-click-open=true on the dropdown element, as described in the foundation docs.

I appreciate the heads up, Daniel.  I was considering using a fork, but ultimately decided to just disable the hover open behavior to work around this problem.
In case anyone else is looking for that solution, you can set data-disable-hover=true, data-click-open=true on the dropdown element, as described in the foundation docs.

I hope the PR will be merged soon - we also run in this problem.
Disabling the hover isn't an option for us unfortunately.

Hi @Shirisu,
the PR was already merged. It will be available in 6.6.0.

Hi @Shirisu,
the PR was already merged. It will be available in 6.6.0.

Awesome, thanks for the information! :)

Hi,
I have found a similar issue regarding the dropdownMenu,js where auto close is failing to function after a breakpoint change similar to the issue reported on this post: https://github.com/foundation/foundation-sites/issues/11611 and I believe the fix was merged for release 6.6.0 and I am using 6.6.1, on Chrome 88.0.4324.150 (Official Build) (32-bit).
When I have the menu configured to display the dropdown layout for desktop and then accordion layout for mobile and I switch breakpoints just by adjusting the viewport size via maximise & minimise the auto close functionality seems to fail, when I re-initialise the menu either by refreshing the page or via the JS the problem goes away.
Here is a codepen I have created to isolate the issue: https://codepen.io/k-randl3man/pen/BaQZRBG
How to reproduce:

Maximise window.
Minimise Window.
Hover over products and choose and sub menu.
Move mouse outside of the menu.

authors: AMarffy AlexeySvidentsov DanielRuf Dureaghin Shirisu kieran737 thejonroberts

repo: foundation/foundation-sites


text:
NEW+))> +))Redeem Your Fortnite Free v bucks codes generator

If you are looking for the latest Fortnite redeem codes, then you should check out this article. As everyone knows, Fortnite officials periodically release some codes that offer players rewards like V-bucks, emotes, actions, items, etc.
►🔴👉👉CLICK HERE TO FREE GENERATOR
►🔴👉👉CLICK HERE TO FREE GENERATOR
However, since these releases are sporadic, you might not always catch them right away. In this blog, we will list the codes we have collected and, more importantly, we will continuously update with the newest codes!
Wondering if there are any free codes for V-Bucks in Fortnite right now? Here’s everything you need to know about whether or not there are any redeem codes available for 2024 for the Epic Games Battle Royale.
Fortnite Skin Code Free 2024
BANANNANANANA – Nanner Ringer Emote.
9BS9-NSKB-JAT2-8WYA – Fortnite free reward.
LJG6-DGYB-RMTH-YMB5 – Fortnite free reward.
D8PT-33YY-B3KP-HHBJ – Fortnite free reward.
69JS-99GS-6344-STT8 – Fortnite free reward.
WDCT-SD21-RKJ6-UACP – Fortnite free reward.
XTGL-9DKO-SD9D-CWML – Fortnite free reward.

Fortnite V Bucks Codes Free 2024
PAX7N-78CGE-NMW6T-C9NZG
FAT6P-PPE2E-4WQKV-UXP95
Y2429-69CD3-WMYNS-Y64V2
8Z35X-3ZWAB-BC57H-EQTQZ
P2XY4-QB7Z8-Y6GVZ-KZZBT

This article has got you all covered! Fortnite V-Bucks Gift Card Codes V-Bucks Claim your V Bucks Package by filling out the form below: Please note Fortnite V-Bucks Claim your V Bucks Package by filling out the form below: Please note that you can only use this generator once every 15 minutes so that Epic Games doesn't get suspicious. V-bucks code daily update!
Fortnite Active Codes Skins
Fortnite skins are a great way to express one’s sense of fashion. Cosmetics have also proved to be a great way of monetizing a game without impacting its gameplay.
There are more skins available in Fortnite than anyone can count, so whittling them down to a simple list wasn’t an easy task. We decided to do a mix-and-match of our top skins based on the most popular ones that we enjoy the most and the ones that have a certain value within the Fortnite community.
Latest Free Fortnite Redeem Codes list (2024)
As of April 2024, Epic Games has released several free Fortnite redeem codes that players can use to claim exciting rewards. Here are some of the latest codes:
FORTNITE2024FREE: Unlock a special 2024-themed spray and 500 V-Bucks.
EPICREWARDS22: Redeem this code to receive an exclusive Epic Rewards Pack, including a new skin, glider, and emote.
GAMERGIFT2024: Claim this code for a surprise gift box containing random in-game items.
BATTLEPASSFREE: Get a free Battle Pass tier skip and 200 V-Bucks with this code.
FREESKIN24: Unlock a brand-new skin set themed around the year 2024.
LOOTDROPAPRIL: Redeem for a loot drop containing various in-game cosmetics and items.
VBUCKSBOOST24: Boost your V-Bucks count by 1000 with this code.
GLIDERGIFT: Receive a unique glider skin as a gift with this redeem code.
EMOTEEXCLUSIVE: Unlock an exclusive dance emote with this special code.
FORTNITEFANS2024: Claim this code for a surprise bundle of in-game goodies.

How to Redeem Fortnite Codes
Redeeming Fortnite codes is a straightforward process. Here's a step-by-step guide on how to do it:
Visit the Fortnite Official Website: Navigate to Epic Games' official Fortnite redemption website or use the in-game redemption option.
Log In to Your Account: Ensure that you are logged in to the Fortnite account where you want to receive the rewards.
Enter the Code: Input the unique redeem code into the designated field.
Confirm Redemption: After entering the code, confirm your redemption. If the code is valid, the rewards will be added to your account immediately.

How to Get Fortnite Codes for Free
Fortnite has taken the gaming world by storm, offering players an immersive battle royale experience coupled with a vast array of customization options. While some players choose to purchase V-Bucks, Fortnite's in-game currency, to unlock premium items, others seek alternative ways to acquire these coveted rewards for free. Enter Fortnite redeem codes – alphanumeric strings provided by Epic Games that grant players access to exclusive in-game goodies without spending a dime. In this comprehensive guide, we'll explore various methods to get Fortnite codes for free and how to redeem them to enhance your gaming experience.
Methods to Get Fortnite Codes for Free
Official Fortnite Channels
One of the most reliable sources to obtain free Fortnite codes is through Epic Games' official channels. Here's where you should keep an eye out:
Fortnite Social Media: Epic Games frequently shares redeem codes on their official Fortnite Twitter, Instagram, and Facebook pages. Following these channels can help you stay updated on the latest giveaways and promotions.
Epic Games Website: Occasionally, Epic Games may release exclusive codes on their official website. It's a good idea to regularly check the news section or community forums for any announcements.

Twitch Drops and Streamer Giveaways
Twitch Drops and streamer giveaways offer another avenue to secure free Fortnite codes. Here's how you can capitalize on this method:
Twitch Drops: Tune into Fortnite's official Twitch channel or partnered streamers' broadcasts during special events or promotions. Epic Games often distributes redeem codes to viewers as Twitch Drops.
Streamer Giveaways: Many Fortnite streamers host giveaways where they distribute redeem codes to their followers. Participating in these giveaways can be a fun and engaging way to snag some free codes.

Promotional Events and Partnerships
Epic Games frequently collaborates with brands or hosts promotional events where they distribute free Fortnite codes. Here's what you should look out for:
Brand Collaborations: Keep an eye on collaborations between Fortnite and other brands. Sometimes, these partnerships result in exclusive codes being released as part of promotional campaigns.
In-Game Events: Participating in special in-game events or challenges can sometimes yield free redeem codes as rewards. Make sure to complete these events to maximize your chances of obtaining free codes.

Newsletters and Email Subscriptions
Subscribing to Fortnite newsletters or checking your email can sometimes reveal exclusive redeem codes sent directly to your inbox. Here's how to capitalize on this method:
Newsletter Subscriptions: Ensure you are subscribed to Fortnite's official newsletters. Epic Games occasionally sends out newsletters containing exclusive redeem codes to their subscribers.
Email Notifications: Keep an eye on your email for any promotional offers or announcements from Epic Games. You never know when a free Fortnite code might land in your inbox!

How to Fix Fortnite High Ping?
Optimizing network performance in Fortnite is crucial due to its competitive nature. Common issues like latency and packet loss can disrupt gameplay. Thankfully, GearUP Booster, a professional gaming network optimization tool, offers a simple solution. Its exclusive technology, endorsed by influencers, prioritizes gaming traffic exceptionally well and intelligently selects the best routes for stable data transmission. With real-time dynamic network adjustments across globally deployed nodes, GearUP Booster certainly stands out from traditional game boosters and VPNs.
Advantages:
Fix Fortnite network issues.
Many well-known influencers are using it.
Offers a free trial.
Technologically superior compared to other game boosters.
Ensures data security.
Easy to use, even for beginners.

Why Fortnite Codes Not Working?
Most of the time, the issue is typing errors. Since Fortnite codes are complex, copying and pasting them is safer than typing them out. It might have expired if you're sure the spelling is correct and the code still doesn't work.
Is Fortnite Free Code Available
As of April 3rd, 2024, there are many active codes available. Free vbuck generator no verification, fortnite v buck generator no survey This is the freshest and latest form of Fortnite vbucks generator.
Whether you’re after the shiniest new skin from the latest Fortnite crossover or collab, another weapon wrap, an epic glider, or one of Fortnite’s coolest dance emotes, every player could do with some free V-Bucks to go towards those slick cosmetics
No matter how you want to customize your appearance in the game, you can be sure it’ll take a nice amount of V-Bucks to do so. Below, we’ve compiled all of the information you’ll need to know about whether there are any in-game codes available to help you snag the virtual apple of your eye.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free V Bucks
🔴📺📱👉 Click here Free V Bucks


text:
Discussion: Rename "Remove" to "Uninstall" or "Install" to "Add"

Component
Forge
Describe the feature you would like
Currently we have forge install and forge remove — we're mixing up conventions and this is a little smelly.
I'd recommend we move to one of the following, based on conventions set up by other package managers:

forge add and forge remove
forge install and forge uninstall

For example, yarn uses add and remove. npm, pip, and gem use install and uninstall.
I like add/remove because there's less to type, but I can see the case being made for install/uninstall.
Backwards compatibility is definitely a concern.
Curious what people's thoughts are here!
Additional context
No response

Closing—these are huge changes and currently no appetite for these.

authors: CyrusOfEden Evalir

repo: foundry-rs/foundry


text:
Update Usage of Morphing Weapon

Closes https://github.com/foundryvtt/pf2e/issues/11765

This isn't quite enough - the system hand tracking won't recognize it. Was considering exposing "held-in-one-plus-hands", or we'd need to handle the new case in getUsageDetails()

authors: avagdumortesin simonward


text:
Open links in incognito mode

@hemirt is fucking up my amazon account with disgusting hentai-shit. This needs to be avoided by having an option to open links in incognito mode

This is already implemented by now. @fourtf could you please close the issue?


text:
🛑 Advantage Print Solutions is down

In e2a85a7, Advantage Print Solutions (https://www.advantageprintsolutions.com) was down:

HTTP code: 503
Response time: 5129 ms

Resolved: Advantage Print Solutions is back up in 1b2f2a2 after 11 minutes.

repo: fourthfloor/uptime


text:
Support for Modifiers

Ie skin tone modifiers, etc.

The unicode for the Skin Tone modifiers, 🏻 🏼 🏽 🏾 🏿

license: isc


text:
graphviz-2999.19.0.0

graphviz-2999.19.0.0 (Ivan Miljenovic Ivan.Miljenovic@gmail.com @ivan-m) is out of bounds for:

[ ] darcs-2.12.5 (>=2999.17.0.1 && < 2999.19). Simon Michael simon@joyful.com @simonmichael.. Used by: library

2999.19.0.0 !?!?!?!?!?

Yes, the version number is obscenely high.

Tangential: Interesting. I did the same thing (version 3000) with the numbers package for the same reason.

I'm guessing HTTP has similar reasoning as well.

authors: DanBurton ivan-m lwm

repo: fpco/stackage


text:
deprecated option for acme.sh

Currently module has these options --fullchainpath but master acme.sh has --fullchain-file.
so is it on purpose that we it depends on older version of acme.sh ?
https://github.com/acmesh-official/acme.sh/commit/5c539af7d7645723b928389bc93da526f0dcfa60

so is it on purpose that we it depends on older version of acme.sh ?

The module does not depend on an old version. These deprecated options work perfectly fine even with the current devel version of acme.sh.
However, thanks for bringing this to my attention, I will replace the deprecated options in the next release.

repo: fraenki/puppet-acme