Need Dot Net Core 8.0 support for "Microsoft.Xaml.Behaviors.Uwp.Managed" NuGet package

hello team,
we are migrating one of the modules to dot net core 8.0 as all older ones are out of support now. We have observed that "Microsoft.Xaml.Behaviors.Uwp.Managed" NuGet package does not support the Dot Net Core 8.0. Could you please help us support Dot Net Core 8.0 for this NuGet Package? We are using v2.0.1 currently stable.

@anagupt can you clarify what type of project you have?
UWP uses .NET Native, not .NET "Core". Otherwise, you'd want the WinUI package for WinUI 3 and the Windows App SDK.
Unless you're talking about the new preview of UWP support for .NET 9; that'll come in the upcoming 3.0.0 version of the package, that PR was done here: https://github.com/microsoft/XamlBehaviors/pull/256


[PowerRename] Introduce advanced counter functionality

Summary of the Pull Request

New counter functionality:

${} introduces a counter into a replace string.
supports multiple customizations: ${start=10,increment=2,padding=4}
multiple counters support: abc_${}_${increment=5}
works in combination with regular expressions

Tooltip with usage and customization descriptions
Cleanup unit tests + add unit tests for counter

PR Checklist

[x] Closes: #3814
[x] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

unit tests
renaming with different counter properties

Is it possible to have a character counter too?

@htcfreek yes, the current design is extendable to allow new properties. I'd prefer not to blow the scope for now though, so it could be done in a separate PR.

@yuyoyuppe about the word padding: this explicitly means something is added to something else. When I read "padding = 5" I interpret that to mean every number will start with "00000…". A number like "00231" only has two padding or leading zeros. Maybe "(string) length" is a better description.

I'm not sure about other PLs but for C/C++/C# it's very common to refer to the behavior you're describing as zero padding. There are a lot of relevant search results for "print zero padding" and articles like that. Both printf("%05d", 123); and Console.WriteLine(123.ToString("D5")); would output 00123. I've never seen "length" used for that. MS docs call it width though.

enumeration syntax only works if Enumerate button is enabled

Would be nice to be able to remove that button and the need for it

enumeration syntax only works if Enumerate button is enabled

Would be nice to be able to remove that button and the need for it

${start=10,increment=2,padding=4} is a valid file name, so not sure how to achieve that. Do you have any ideas to replace button with?


Kitematic crashes on first run and complains about Atom Framework

report:
Process:               Kitematic (Beta) [68237]
Path:                  /Applications/Kitematic (Beta).app/Contents/MacOS/Kitematic (Beta)
Identifier:            com.kitematic.kitematic
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Kitematic (Beta) [68237]
User ID:               502

Date/Time:             2015-04-02 15:41:05.169 +0100
OS Version:            Mac OS X 10.10.2 (14C1510)
Report Version:        11
Anonymous UUID:        3D0F422E-8473-C00D-EE9A-0D30A26AA91B

Sleep/Wake UUID:       0F295AB9-35DA-40DE-A37A-C5568A83FC83

Time Awake Since Boot: 640000 seconds
Time Since Wake:       2000 seconds

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/Atom Framework.framework/Atom Framework
  Referenced from: /Applications/Kitematic (Beta).app/Contents/MacOS/Kitematic (Beta)
  Reason: no suitable image found.  Did find:
	/Applications/Kitematic (Beta).app/Contents/MacOS/../Frameworks/Atom Framework.framework/Atom Framework: file too short

Binary Images:
    0x7fff62415000 -     0x7fff6244b837  dyld (353.2.1) <65DCCB06-339C-3E25-9702-600A28291D0E> /usr/lib/dyld

Thanks for the issue!
Interesting - first time seeing this. Does re-downloading Kitematic work?

Actually I was unable to use Kitematic because it crashes every time I try to open it.
Have you deployed a new release on its website since yesterday? If not, that happens with latest available version.

Thanks for the update :smiley:
From this thread: https://discuss.atom.io/t/dont-work-with-mac-osx-10-9-2/6019/3
It seems that atom-shell based apps only work if you unzip them using the Archive Utility. Does unzipping the app this way work?

WHAAAATTT?? Thats crazy, but... it worked! I feel dumb now, unzipping using the Archive Utility fixed it! Is it maybe related with symlinks or case sensitive?
Well, at least this issue should help someone. Thanks for the tip @jeffdm !

No reason to feel dumb! Seems like a silly bug upstream with Atom. Glad we got it working :smiley:. Sadly, it also occurs with some CLI-based unzip tools. It definitely will help others :smiley:


Create website generator

📖 Description
Basically, we'll create a mini static website generator (this could be based off Webize, but until I get back to it and clean things up - and convert it into a proper package that we can use from here - let's just create a basic thing that will serve just for this...)

Ready to merge! 🚀


blank page with php code on console

RainLoop version: 1.12.0, browser: firefox DE, firefox, OS:ubuntu 18.04 server, desktop
Expected behavior and actual behavior:
Expected: load admin / login page
Actual: blank pages with php codes in console
Steps to reproduce the problem:

install rainloop using methods described on installation pages.
Change permission described on permission pages

Logs or screenshots:
no error logs

fixed by uncommented application/x-httpd-php php on /etc/mime.types and loading php modules onto apache


Add NUCLEO-F401RE device.

Thank you for your message.
I'll try.
My plan is remove USB debugging because NUCLEO has UART-USB converter. (I/F chip)

When ready you can download the CLA form from https://github.com/ghi-electronics/TinyCLR-Ports/blob/dev/README.md#contributing
Please sign it, scan and upload it, then return to us at the specified address.

Even though the nucleo has a converter to enable serial debugging, if it can also be used for USB debugging, we want to keep that as an option for the user -- even if it isn't the default.

I apply some issues. https://github.com/matsujirushi/TinyCLR-Ports/commit/f52ba98dd6fc13d9d5d197416e0fdb594bcbb827
I have a problem.
I don't have USB PID&VID because I am not STMicro.
Please advise.

Do not worry about USB PID&USB (use that ones defined from GHI) since pa2/pa3 you defined to be used as serial you may use with any vendor uart/serial to usb converter too such are ftdrl ,pl2303 ,ch340 etc(because of external pins exist)...

I think we need to choice we can change LMODE_PIN(ENABLE usb debugging or DISABLE) or NOT.
I want to choice NOT because NUCLEO-F401RE have not USB-OTG connector and I don't have PID&VID.
Do you think that? @valoni @Arke64

For now, go ahead and use the same VID and PID. We will have some guidance soon for what values you should use going forward.
@valoni reported an issue around which debugger to use and we'll use it to track changing how the debugger is selected. The defines will probably be changed to "USE_MODE_PIN", "USE_UART_DEBUGGER", "USE_USB_DEBUGGER" instead of how it is setup now.


feat: response-contains-header & response-contains-property built-in rules

What/Why/How?
Closes #390 & #389 respectively
Check yourself

[x] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[x] All new/updated code is covered with tests

Security

[x] Security impact of change has been considered
[x] Code follows company security practices and guidelines

I updated the MR. @adamaltman, @RomanHotsiy please take a look. If the changes work for you, I'll proceed to the response-contains-property rule (I'm going to incorporate it in this MR).

@adamaltman, @RomanHotsiy
Added changes for the response-contains-property rule. Please take a look.


feat: Implemented functionality to support synchronous instrumentation

This change is

inspectit-ocelot-agent/src/main/java/rocks/inspectit/ocelot/agent/AgentMain.java line 49 at r2 (raw file):
Previously, ClaudioWaldvogel (woodywoodse) wrote…
At this point Spring is not yet intialized

good point :)

inspectit-ocelot-agent/src/main/java/rocks/inspectit/ocelot/agent/AgentMain.java line 96 at r2 (raw file):
Previously, ClaudioWaldvogel (woodywoodse) wrote…
The message says that async is disabled in pre Java 9 environments and this will have significant performance degradations

Ahhh, okay so pre Java 9 we should rather do synchronous instrumentation (what you just have implemented).
Got it, thanks!

inspectit-ocelot-core/src/main/java/rocks/inspectit/ocelot/core/instrumentation/TypeDescriptionWithClassLoader.java line 58 at r2 (raw file):
Previously, heiko-holz (Heiko Holz) wrote…
I think we resolved this in a discussion.
I had the idea that we implement the same class.staticMethod structure for the TypeDescriptionWithClassloader, so that the access to the of method is differently for loaded and for unloaded types.
e.g., by implementing nested classes with names such as ForLoadedType and ForUnloadedType and then have these two classes implement the of method

nice idea, not implemented.


Create contributors page

PR Title
This PR addresses issue #182
It creates a page to display the repository's contributors
Description
I created a new page named "contributors" with a navbar, contributors component and footer.
How you solved
I created two components—one for each contributor and another for all contributors. The contributor component hits github's Users API to get social media URLs. The contributors component encapsulates the contributor component, passes down repository contributors and displays all contributors. There's a display for mobile and one for viewports > 768px
Screenshots

Checklist

[x] I have Made this contribution as per the CONTRIBUTING guide in this repo
[x] I have tested in local Environment.
[x] I have made the fix as per issue converstaion
[x] I have starred the repository ⭐

Great @AnnieDebbie ,
Quick request,

In new page, the card container isn't centered though (we need to center it to the page and have mx-40 which brings the container to navbars margins horizontally and mx-4 in mobile screens):

And we can make border color to navbar's orange and add some radius (border-2xl will suffice)

And also we can remove the contributors section in about us page and add a link to new page there like ("check our cool contributors here ->")

Okay, got it

Great! @AnnieDebbie


Error on certificate validation on the last few days

My certificate is about to expire and and on the last few days, some instances of my application are having problems connecting to the server. They just don't connect. Even on the same device, sometimes after installing the app it works fine, other times it just doesn't connect.
Digging in I discovered that removing this library fixes the issue. Any  tip on how to fix this?
Or any ideas why this is happening?

Same issue happened to me few days ago. I had to disable CT to get my app work again.

Has anyone managed to capture a log from when this happens? I suspect it could be something like the log list being out of sync with the signature, which we have seen happen once before.

Hey @mattmook , I do not happen to have a log, but the behavior of failing to verify the signatures was like consistently inconsistent. At some it would fail to verify and then would work again. I am not sure if it has something to do with the last days of the month and an issue is going on with Date validations, but we have not seen it happen afterwards.
Just for future reference and in order to help you debug it more effectively, what would you like from us to capture? Just the raw loglist response?

When creating the certificateTransparencyInterceptor you can provide a logger, an instance of CTLogger - it might be worth recording any instances when log is called with an instance of VerificationResult.Failure.

Yeap, we are already using that and it was outputting something along the lines of:
SSLHandshakeException: Certificate transparency failed: LogServerSignatureResult.Invalid.SignatureFailed I can get the exact log next time it happens 😄

I'm not sure if related or not, but I recently added this library and things were working fine. Starting today, cert transparency is failing:
Failure: Unable to load log servers with SignatureVerificationFailed(signatureResult=Invalid signature)

Any updates on this issue?
Are others still experiencing this?

Haven't experienced it since the last days of January. Will wait to check it on February as well!

We had this logged in production today as well. Unfortunately we do not have any logs to share apart from:
javax.net.ssl.SSLPeerUnverifiedException: Certificate transparency failed at com.babylon.certificatetransparency.internal.verifier.CertificateTransparencyInterceptor.intercept(CertificateTransparencyInterceptor.kt:59)

Yeah, we actually disabled this library since we cannot afford to have these issues happen randomly. Our security team understands but would really like this to be solved / looked into.
I wrote about how we are remotely toggled this library in another issue: https://github.com/babylonhealth/certificate-transparency-android/issues/28#issuecomment-582993663

@mattmook based on this comment: https://github.com/babylonhealth/certificate-transparency-android/issues/28#issuecomment-582653499 could we please have an update that uses the correct casing for the Signature name SHA256withRSA https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#Signature and prepare a new release?
Also since more people mentioned issues with the last days of a month, I really tend to believe something shady is going on there.

There are some interesting findings I mentioned here: https://github.com/babylonhealth/certificate-transparency-android/issues/28#issuecomment-625865487


Adding the IA-DEVS definition paper to the README.md for reference

Adding a link to the paper defining the formalism IA-DEVS that is going to be implemented by this simulation engine.


Address some vulnerabilities reported for ORT using resolutions in .ort.yml

This PR is in the context of scanning ORT with ORT. Sonatype NexusIQ which we use currently as advisor issues a number of vulnerabilities for ORT. In this PR I try to address some of them by resolutions in .ort.yml that (according to my analysis and understanding) should not affect ORT in the way it is using the affected components.
There are other vulnerabilities though which probably cannot be handled by such resolutions in general, since they may depend on the concrete context or environment in which ORT is used.

Looks like funTest-non-analyzer got stuck again... we probably need to have a look at what's going on there separately.


Changed logging to directly print to file instead of using microlog.

Since we already route all vehicle logging through the VehicleLogger object, using microlog4j does not really help us in any way.  This PR removes the microlog4j dependency, and instead directly logs to a logfile directory.
This also changes logging to use a proper android directory request, so logs will now be put into:
/sdcard/Documents/platypus
It also slightly changes formatting to put the full date at the top of each logfile, instead of printing it on every line.  The timestamps used in the log are relative to the start of the log, which makes the logs much shorter.

Looks good to merge as long as the new format is acceptable to everyone. Sample log excerpt below:
17111	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17112	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9811792095061782,0,-0.1930993496437295,0],"zone":"17North"}}
17114	I	{"sensor":{"channel":3,"type":"ES2","data":[0,22.8]}}
17147	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17148	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9812431002194185,0,-0.19277442328219851,0],"zone":"17North"}}
17165	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17240	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9813379855657316,0,-0.19229081643643844,0],"zone":"17North"}}
17270	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17340	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9812663229550732,0,-0.1926561793305107,0],"zone":"17North"}}
17370	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17440	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.981353313787868,0,-0.19221257377593767,0],"zone":"17North"}}
17471	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17540	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.981424817945558,0,-0.19184714415525803,0],"zone":"17North"}}
17573	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17640	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9815426390897778,0,-0.19124342511227443,0],"zone":"17North"}}
17671	I	{"sensor":{"channel":2,"type":"ATLAS_PH","data":[4.099]}}
17771	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17771	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9815426390897778,0,-0.19124342511227443,0],"zone":"17North"}}
17870	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17871	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9815659009318505,0,-0.19112399673469743,0],"zone":"17North"}}
17908	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
17940	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9815659009318505,0,-0.19112399673469743,0],"zone":"17North"}}
17970	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
18016	I	{"sensor":{"channel":1,"type":"ATLAS_DO","data":[9.82]}}
18039	I	{"pose":{"p":[476608.34,4671214.4,172.35],"q":[0.9816203213919358,0,-0.19084429420444468,0],"zone":"17North"}}
18070	I	{"cmd":{"m0":{"v":0},"m1":{"v":0}}}
18098	I	{"sensor":{"channel":4,"type":"BATTERY","data":[16.231,0,0]}}

Thanks for testing @christomaszewski ⛵


Build does not complete - variables not set in docker-compose.yml?

I am trying to get this to run on my local development machine (Intel MacBook Pro, Docker Desktop), but although the cookiecutter completes correctly, the docker-compose build --no-cache fails with the following error message:
=> [auth] library/node:pull token for registry-1.docker.io                                                                                0.0s
failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF

Checking the docker-compose.yml file, I see a lot of Variable not set mentions - see attached file which I had to rename to .txt).
Any ideas how I can debug this?
docker-compose.txt

I'm not immediately sure of what the problem may be. Did you make any edits to the file (even as much as opening, saving, and closing) because there seem to be some tab/space errors? I have had Docker scream because of mixed tabs and spaces for formatting.
Also, is yours a recent version of Docker?
The variable not set will just pull from your .env on build. E.g. ${TRAEFIK_TAG?Variable not set} will pull TRAEFIK_TAG. The error message you'd get if it was a problem and the variable was not set would be Variable not set. You'll see in other places that the alternative isn't a message but a default value.

Thank you for your answer, turukawa.
I did not make any updates to the files, and just ran one command after the other. I am aware that there seem to be / are issues with Docker on Mac - mainly because of the abstraction OSX does (https://markshust.com/2018/12/30/docker-mac-filesystem-volume-mount-approach-performance/). However, I am definitely not an expert.
For the record, I am running the most recent version of Docker Desktop.
I'll check out the Docker issue, maybe that will fix it. Other than that, I'll probably just install Linux somewhere. Is it possible to run this stack inside one Docker container?

From the looks of things with that issue, you need to downgrade to a version previous to the issue occurring.
It's possible to run FastAPI from a single image. Check out the source Inboard images. However, at that point you're going to need to decide how to deploy any other components you may need (database, frontend, etc).

Yup, downgrading to Docker Desktop 4.14.0  from last year worked. Thank you for your help.


Remove stale untagged images

Stale untagged images aren't removed.

Problem is: The Github Token doesn't have permission to delete packages, nor is there a way to grant it. Personal Access Tokens on the other side aren't available on organization level, but user only. (Except creating a dedicated bot user) There's no way to solve this at the moment.


feat(api): add app-specific directory APIs, closes #5263

I'd appreciate some feedback on the approach taken here as it's my first time working with the Tauri codebase.
In particular, should there be tests? I can't find tests anywhere for similar API features such as the existing appDir method.
Also, are you happy with the way I have refactored appDir and logDir to internally call appConfigDir and appLogDir to avoid duplicated code?
I also wondered if there's an equivalent to @since for the Rust documentation comments?

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
closes #5263

Another thing we need to think about is localdata vs data because of windows :/

yeah we could also add appLocalDataDir

Thanks for the review @amrbashir, I'll make those changes later. I was actually going to ask about deprecation notices too but forgot, so thanks for mentioning that.
I'll look at appLocalDataDir too.

I think I've addressed all the issues discussed, and also fixed the lint error. Would you mind taking another look @amrbashir ?


design

Week 2 of the sprint i need to come up with a new design and animation for the calculating page (maybe one that falls off downward?)
Need to find inspiration, look around for other people`s sites and look around on internet

Hier wat links voor inspiratie:
dashboard

https://dribbble.com/search/dashboard
https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct
https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct

landingspagina

https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/
https://nl.pinterest.com/pin/790944753334543946/

animatie

https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct
https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct
https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct
https://www.behance.net/search/projects/dashboard?tracking_source=typeahead_search_direct

verander color palette


feat: bump embedchain version to 0.0.58 in examples

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #633
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (does not change functionality, e.g. code style improvements, linting)
[ ] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[ ] Unit Test
[ ] Test Script (please provide)

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

Seems like this is already merged as part of https://github.com/embedchain/embedchain/pull/639
My bad though. I should have looked at your PR first 😓 Will take care from next time.


Support for a App.config settings

I'm trying to couple commandline Options class with ConfigurationManager.AppSettings to make configuration persistent. For now (with stable version 1.9.x) I ended with such piece of code:

public Options (string[] args) {

	// TODO: redesign without reflections
	var pis = this.GetType().GetProperties().Where(prop => prop.IsDefined(typeof(OptionAttribute), false));
	foreach (var pi in pis) {
		var optAttr = pi.GetCustomAttributes(typeof(OptionAttribute), false).FirstOrDefault() as OptionAttribute;
		if (optAttr == null)
			continue;
		optAttr.DefaultValue = optAttr.DefaultValue ?? ConfigurationManager.AppSettings[optAttr.LongName];
	}

	// here we use CommandLine to initialize this class
	using (var parser = new CommandLine.Parser(settings => { settings.HelpWriter = Console.Error; settings.IgnoreUnknownArguments = false; }))
...

Maybe you can propose better way to enumerate properties?

@apla, code can help, but can you first describe exactly what you're trying to doing?
When talking about Options class and persistence, do you want serialize an instance in your settings or "externalize" attributes metadata?
I want to add that, if I'm not wrong, that @nemec already done a configuration component coupled with this project. You can check its repo or ask him.

Hi @apla, are you asking for a way to load settings from App.config and override some of them with command line parameters? Do you also need to save command line overrides back to the App.config?
For the first one, I wrote a library called SmartConf that does just that -- set the "order" of your data sources and they will all be merged into on config. Additionally, I wrote sources for AppSettings and CommandLine (see here, the readme for CommandLine is in the CommandLine folder).
If you need to save the data back, unfortunately I haven't implemented that yet for AppSettings. You could load settings from a regular XML file (XmlFileConfigurationSource) instead, which does support saving.

I want to split project development to two phases. When I write code and test it I change configuration via command line, and when my requirements are satisfied, I want to store that config via persistence layer (for example, App.config). Then I can distribute my project along with working configuration. Also, using that configuration allows me to pin into windows 8.x taskbar, because all cli parameters is lost when I pin program to taskbar.
I don't need to change configuration programmatically, App.config shall provide defaults.
For example, I'm writing borderless fullscreen browser. I want to configure starting url to http://instance-a.site.com/ and use cefsharp for that browser. Another client wants to use old site with ActiveX, so I need to configure url as http://instance-b.site.com and define WebBrowser version as IE 8.  When I'm ready, I just send zip archives with working configuration using only one binary.
Do I need to provide one configuration class for App.config and another one for commandline? Or I can use one Config class like this?

private sealed class Options {
	[Option ("url", MetaValue = "URL", HelpText = "Url to show on multiscreen")]
	public string Url { get; set; }

	[Option ('e', "engine", DefaultValue ="chrome", HelpText = "Browser engine to use: ie or chrome")]
	public string Engine { get; set; }

...

var manager = new ConfigurationManager<Config>(
    new AppSettingsConfigurationSource<Config>(),
    new CommandLineConfigurationSource<Config>(args)
);
var config = manager.Out;

Yes, you should use the same class for both. Your sample code looks
correct.

As you seen, @apla, @nemec helped you... I want to add that we're happy you choose this library and that your way of using it for automating tests is very cool.

Fine, I was looking for same solution as @apla too!

@dlev, as said @nemec it own a project that can help in such direction or at least can be used to get inspiration.
This is what I'm planning for post-2.0-stable:
class Options {
  // normal options here ...omissis...

  [Option(Default=Fallback.AppConfig("section/value").Or(8080))]
  public int Port { get; set; }
}

In few words you'll get a Fallback object with fluent syntax able to indicate and alternate source or fallback itself to fixed default.
I'm thinking to something similar from year (you can search old issues for confirmation) and I think it accommodates also @apla needs.
If you want writing something custom, you'll supply a Func delegate, I want to keep the library free from public interfaces or base classes.
The bad news is that you need to wait until 2.0 reaches stable version. Before doing it I want to add a new test project that uses FsCheck (yes the new t.p. will be in F).
Thanks everyone for joining wonderful discussion. :+1:

Well, this is a very elegant notation:
.Or(8080)

But it is good to know that autogenerated Settings.Designer.cs can contain a default value itself (if Property GenerateDefaultValueInCode for this Setting is set to True):
        [global::System.Configuration.ApplicationScopedSettingAttribute()]
        [global::System.Diagnostics.DebuggerNonUserCodeAttribute()]
        [global::System.Configuration.DefaultSettingValueAttribute("8080")]
        public int Port {
            get {
                return ((int)(this["Port"]));
            }
        }

Unfortunately it is not allowed to simplify the notation just to use:
  [Option(Default = Properties.Settings.Default.Port)]
  public int Port { get; set; }

Yes, but this is not what I'm proposing. When Default = "Fallback", the parser will look for a property {PropertyName}Fallback that returns a Fallback type used to fluently build such default data customizations.
@diev, maybe you've looked during my process of editing...?
R. Giacomo


Sequelize Breaking Changes

Model.Instance and instance.Model are removed
Breaking Changes

A "bit" late to the part :) But thanks for the info! I cannot see that we use these properties anywhere in the code ATM.


Unicode in type-at-pos is broken

Flow version: 0.105.0
const d: {'фу-бар': number} = {}

Expected behavior
{ 'фу-бар': number }

Actual behavior
{ "\u0444\u0443-\u0431\u0430\u0440": number }

Link to Try-Flow or Github repo:

Color is off in errors too

I was looking into a related issue recently. this is because Flow reports locations in UTF8 but JS counts in Unicode code units. I started adding an encoding flag, so that you can choose; the CLI would default to UTF8, and flow_parser.js and flow.js would default to UCS2/UTF16.

actually this could be a separate place that uses the wrong encoding, but I think the fixes will be similar.


EndlessScroll - Current page value

Why in EndlessRecyclerOnTopScrollListener initial current page value is set to 0 and in EndlessRecyclerOnScrollListener is set to 1?
https://github.com/mikepenz/FastAdapter/blob/develop/library-extensions/src/main/java/com/mikepenz/fastadapter_extensions/scroll/EndlessRecyclerOnTopScrollListener.java#L13
https://github.com/mikepenz/FastAdapter/blob/develop/library-extensions/src/main/java/com/mikepenz/fastadapter_extensions/scroll/EndlessRecyclerOnScrollListener.java#L19
Can't find any reason for that.

This will be fixed with v3


[FEAT] Add ability to access doc.microsoft.com from context menu on right click of a namespace or a type

Add ability to access doc.microsoft.com from context menu on right click of a namespace or a type
and display in a readonly window like the in-memory creation of goto-definition
e.g. IHostingEnvironment
https://docs.microsoft.com/en-us/aspnet/core/api/Microsoft.AspNetCore.Hosting
Directory
https://docs.microsoft.com/en-us/dotnet/core/api/System.IO
and so on.

Thanks for the request. That's a great idea!


getRPercentCooldownMod(), getFlatCritChanceMod()

Do those two methods return a double no greater than 1.00 or a double no greater than 100?
In other words, if someone has +5% critical chance runes, does the method getFlatCritChanceMod() return 0.05 or 5?

In your example 0.05 would be returned.
By the way, if you could just test simple stuff like this yourself in the future instead of opening an issue that'd be great =D. I'm just going to go in and test it myself the same way you would anyway.


Dependency version update (pytheas 1.25).

NetflixOSS » karyon » karyon-pull-requests #2 SUCCESS
This pull request looks good


Ensure new accounts are immediately available

Description
This fixes a bug with the inline account creation where the accounts wouldn't be available in the same CLI command session. This created an adverse experience when doing things like apply datacenter and creating an inline account – the account wouldn't be available right away causing the application to fail.
Closes https://github.com/architect-team/arcctl/issues/125
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
# Clear settings
$ rm -rf ~/.config/arcctl

# Apply a datacenter without previously existing accounts. Create them inline.
$ arcctl apply dc ./__tests__/datacenters/local.yml

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

I have never hit this. Why does this fix this?

I have never hit this. Why does this fix this?

The current implementation uses a class getter to allow providerStore to be referenced like a property, but in reality every time something references this.providerStore it will create a new class instance. This way we only create one instance of the store.


Fix example link in juniper_rocket README

It appears that the official repo was combined back into the main juniper repo, but the link didn't get updated.

Awesome, thanks!


Local Edge functions: event loop error after a few minutes

Describe the bug
It seems that after my edge function has been running locally for some time (perhaps a few minutes) I start to get these messages in the logs:
wall clock duration warning. isolate: df3c6dc8-dcc9-4348-a278-e0e1ff102fc3
wall clock duration warning. isolate: 93b745a9-cdb0-49a0-ae88-514a87391cd6
wall clock duration warning. isolate: ce00ba14-d7f7-4e27-8b6e-92191f485a81
wall clock duration warning. isolate: 39ebddfd-8b3e-4af6-a966-178f821877b6

And then eventually I see this:
event loop error: TypeError: Cannot convert undefined or null to object
    at slice (<anonymous>)
    at new DOMException (ext:deno_web/01_dom_exception.js:126:14)
    at [[[signalAbort]]] (ext:deno_web/03_abort_signal.js:83:14)
    at AbortController.abort (ext:deno_web/03_abort_signal.js:172:30)
    at file:///home/deno/main/index.ts:147:31
    at Object.action (ext:deno_web/02_timers.js:151:11)
    at handleTimerMacrotask (ext:deno_web/02_timers.js:65:10)
    at eventLoopTick (ext:core/01_core.js:189:21)

After that error happens, all my requests fail with this:
Error in worker connection: connection closed before message completed
request failed (uri: "/my-function" reason: hyper::Error(Canceled, "connection was not ready"))

The function is as simple as this:
Deno.serve(async (req) => {
  return new Response(
    JSON.stringify({ publicToken: "123" }),
    {
      headers: { "Content-Type": "application/json" },
    }
  );
});

To Reproduce
Steps to reproduce the behavior:

Create a new function with the above code
run supabase functions serve
Call the function at least once (not sure if this is actually necessary)
Wait a few minutes... You should eventually see the above event loop error
Try to call the function again.  You will get "connection was not ready" error

Expected behavior
Local functions should not randomly crash after only a few minutes :)
Desktop (please complete the following information):

OS: OSX
Version of CLI: 1.110.1

Additional context
At least one other person has reported experiencing this problem in the supabase discord (The above report is using their description).

Transferring because it sounds like an issue with edge runtime container.

I can also verify that I'm experiencing the same issue.

Seeing the same issue also

I'm also seeing this issue, can't update supabase beyond 1.106.1 or edge fns break every few minutes.

yep. same

I'm also experiencing this issue with CLI version 1.110.1

I had this is issue too on my M2 mac until i upgraded Docker Desktop (it was very much out of date) as well as supabase. Now running without a single crash on supabase 1.112.2 and Docker Desktop 4.25.1 (128006). Still seeing the wall clock duration warning though, but no crashes.

I had this is issue too on my M2 mac until i upgraded Docker Desktop (it was very much out of date) as well as supabase. Now running without a single crash on supabase 1.112.2 and Docker Desktop 4.25.1 (128006). Still seeing the wall clock duration warning though, but no crashes.

My Docker Desktop version is 4.19.0 (106363

Thanks @hyldmo. Updating Docker Desktop and my supabase CLI resolved the crashing issue.

Any comments on whether the wall clock duration reached. isolate:<PHONE_NUMBER>0253939329 logs are a problem? It kind of seems like the connection isn't being closed out or something, but the response it getting returned from the endpoint. Is there something else we should be doing to tell supabase that the request is complete?

same

same issue here, i don't get an error, but all cloud functions become very slow or irresponsive after a couple requests. Seems like the workers don't exit execution. If i restart the runtime it works again for a couple of request

I as well am getting related issues.
I get wall clock log msgs like these:
wall clock duration reached. isolate: d66d7171-0472-48db-a589-a52454d89a26
isolate memory usage sender dropped
wall clock duration warning. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
wall clock duration reached. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
isolate memory usage sender dropped

I also am having an issue where I cannot use the existsSync() and Deno.readDirSync() functions.
When running these, I get the following error:
runtime has escaped from the event loop unexpectedly: event loop error: TypeError: Deno.statSync is not a function
    at existsSync (https://deno.land/std@0.220.0/fs/exists.ts:121:23)
    at EnvService.dirDoesNotExist (file:///home/deno/functions/instructor-ui/services/env-service.ts:100:13)
    at EnvService.validateInitEnvFile (file:///home/deno/functions/instructor-ui/services/env-service.ts:65:14)
    at EnvService.loadEnv (file:///home/deno/functions/instructor-ui/services/env-service.ts:22:48)
    at file:///home/deno/functions/instructor-ui/index.ts:5:12
failed to send request to user worker: connection error: Connection reset by peer (os error 104)
user worker failed to respond: connection error: Connection reset by peer (os error 104)
InvalidWorkerResponse: user worker failed to respond
    at async Promise.allSettled (index 1)
    at async UserWorker.fetch (ext:sb_user_workers/user_workers.js:79:21)
    at async Server.<anonymous> (file:///home/deno/main/index.ts:146:12)
    at async #respond (https://deno.land/std@0.182.0/http/server.ts:220:18) {
  name: "InvalidWorkerResponse"
}

I have tried to search for any open or closed issues on this to see if I can get some more info but have come up dry.

hello @CalvinWilkinson 😁
This runtime provides a limited File API compared to Deno, and that's a relatively recent change. From a security perspective, allowing file access can be problematic.
As for the error message... that's something that needs to be documented for self-hosted users 🙄
wall clock duration reached. isolate: d66d7171-0472-48db-a589-a52454d89a26
isolate memory usage sender dropped
wall clock duration warning. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
wall clock duration reached. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
isolate memory usage sender dropped

Do you mind if I ask what version of the runtime you're getting this message from? I remember this is something I've already fixed.
failed to send request to user worker: connection error: Connection reset by peer (os error 104)
user worker failed to respond: connection error: Connection reset by peer (os error 104)
InvalidWorkerResponse: user worker failed to respond
    at async Promise.allSettled (index 1)
    at async UserWorker.fetch (ext:sb_user_workers/user_workers.js:79:21)
    at async Server.<anonymous> (file:///home/deno/main/index.ts:146:12)
    at async #respond (https://deno.land/std@0.182.0/http/server.ts:220:18) {
  name: "InvalidWorkerResponse"
}

This error message is a trivial runtime message caused by a script error, so you don't have to care about it, but now that I think about it, it's a bit verbose for a user 😅

hello @CalvinWilkinson 😁
This runtime provides a limited File API compared to Deno 1, and that's a relatively recent change. From a security perspective, allowing file access can be problematic.
As for the error message... that's something that needs to be documented for self-hosted users 🙄
wall clock duration reached. isolate: d66d7171-0472-48db-a589-a52454d89a26
isolate memory usage sender dropped
wall clock duration warning. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
wall clock duration reached. isolate: 476ff220-04b9-41ee-a5dc-7db65464616a
isolate memory usage sender dropped

Do you mind if I ask what version of the runtime you're getting this message from? I remember this is something I've already fixed.
failed to send request to user worker: connection error: Connection reset by peer (os error 104)
user worker failed to respond: connection error: Connection reset by peer (os error 104)
InvalidWorkerResponse: user worker failed to respond
    at async Promise.allSettled (index 1)
    at async UserWorker.fetch (ext:sb_user_workers/user_workers.js:79:21)
    at async Server.<anonymous> (file:///home/deno/main/index.ts:146:12)
    at async #respond (https://deno.land/std@0.182.0/http/server.ts:220:18) {
  name: "InvalidWorkerResponse"
}

This error message is a trivial runtime message caused by a script error, so you don't have to care about it, but now that I think about it, it's a bit verbose for a user 😅
Footnotes

https://supabase.com/docs/guides/functions/debugging#limitations ↩

That is good to know.  Thanks for the update!!
As for the runtime, here is what I have:

Deno - v1.41.3
Supabase - 1.145.4

I hope that is what you need.  If you need anything else. let me know.

Your version of Deno is different from the version of Deno that edge-runtime is using internally.
I assume the version of Deno you are mentioning is a standalone.
The actual version of edge-runtime included in the 1.145.4 you mentioned is v1.36.1^1 The version of Deno it is using is v1.40.3^3.
It's pretty complicated, isn't it?😅 I think this needs to be documented at some point.
And it looks to me like you're using a version prior to the one that fixed the bug (that should be fixed at edge-runtime v1.38.0 and above).
You can upgrade the CLI version to beta to bring edge-runtime up to date^4.

Your version of Deno is different from the version of Deno that edge-runtime is using internally. I assume the version of Deno you are mentioning is a standalone.
The actual version of edge-runtime included in the 1.145.4 you mentioned is v1.36.112 The version of Deno it is using is v1.40.33.
It's pretty complicated, isn't it?😅 I think this needs to be documented at some point. And it looks to me like you're using a version prior to the one that fixed the bug (that should be fixed at edge-runtime v1.38.0 and above).
You can upgrade the CLI version to beta to bring edge-runtime up to date4.
Footnotes

https://github.com/supabase/cli/blob/v1.145.4/internal/utils/misc.go#L37 ↩
https://github.com/supabase/edge-runtime/releases/tag/v1.36.1 ↩
https://github.com/supabase/edge-runtime/blob/v1.36.1/crates/cli/.env.build ↩
https://github.com/supabase/cli/releases ↩

That makes sense to me!!
Indeed I am running a separately installed version of deno due to other projects.
Thanks for the update!!

I am also running into the same Issue using transformers.js
import { layer_norm, pipeline } from "npm:@huggingface/transformers";

export async function createEmbeddings(content: string): Promise<number[]> {
    const pipe = await pipeline(
        "feature-extraction",
        "nomic-ai/nomic-embed-text-v1.5",
        {
            // quantized: false
        }
    );
    const tensors = await pipe(content, { pooling: "mean" });
    const matryoshka_dim = 512;
    const embeddings = layer_norm(tensors, [tensors.dims[1]])
        .slice(null, [0, matryoshka_dim])
        .normalize(2, -1);
    return embeddings.tolist() as number[];
}

Deno.serve(async (req) => {
 ....

     for (const row of rows) {
        const { id, [contentColumn]: content } = row;

        if (!content) {
            console.error(`No content available in column '${contentColumn}'`);
            continue;
        }

        const output = await createEmbeddings(content);
        const embedding = JSON.stringify(output);

        const { error } = await supabase
            .from(table)
            .update({
                [embeddingColumn]: embedding,
            })
            .eq("id", id);

        if (error) {
            console.error(
                `Failed to save embedding on '${table}' table with id ${id}`,
                error
            );
            continue;
        }
    }
 })


IBC Governance Action Support

Closes #2173

We are letting this slip from Testnet 64, and will return after shipping.


Parents of indented tasks do not show collapse icon in Reading Mode (when folding is enabled)

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Given the following Markdown...
* [ ] My task
	* [ ] sdf
	* [ ] sdf
* [ ] My other task
	* [ ] sdf
	* [ ] sdf
	* [ ] sdf

... When Folding is enabled, both "My task" and "My other task" should show folding collapse arrow icons.
Current behaviour
Whilst this does happen in Editing mode, the arrows do not show in Reading mode.
Text renders in Reading mode as  My task
Steps to reproduce
Try some indented task lists...

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version
1.0.0
Tasks Plugin Version
1.18.1
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Thanks for a clear explanation.
If anyone works on this, there is a similar request to allow the group headings in task results blocks to be foldable: https://github.com/obsidian-tasks-group/obsidian-tasks/discussions/1012. The knowledge for fixing one would help in the implementing of the other.

Can you make the plugin ignore alternate checkboxes as a partial workaround? I use usual ones for tasks and alternate for writing. Currently all types are considered as valid task checkboxes

What is needed to address this is to find out what CSS is added to parent list items when folding is enabled.
The only thing I can think of, as the cause of this, is that Tasks is not retaining that style information.
Once I know what CSS to look for, it should be feasible to preserve it.
I previously asked about this on Obsidian Discord, unsuccessfully.

@claremacrae I've had a look at the CSS and Obsidian adds the is-collapsed class to folded-away sublists - this then seems to render the chevron for un-folding for regular list items (which then only have class=is-collapsed), but Tasks seems to override checkbox items with its own markup, and doesn't render the chevron when is-collapsed is part of the classes. (Side note- when collapsing a sublist of a checkbox in edit mode, then in reading mode there is no indication at all of the hidden information.)
(In edit mode it's the same is-collapsed class, but it is added to a
 tag that's enclosing both the label of the line and the checkbox, which in edit mode seems to be rendered on its own.)

Thank you @st-- - what is the CSS for showing the chevron but not actually collapsing? In other words, how to make sub-lists collapsible but not collapsed?
(I read this request as about showing the chevrons, but not collapsing the sections???)

So for the regular list items, Obsidian adds an extra <svg> that renders the chevron:

and this then gets rotated under the is-collapsed class:

whereas the sub-list gets hidden away:

Does that help / point in the right direction?

I've tried figuring out what is processing the button-click to actually add the is-collapsed class, but I've got no idea:(

Yes I think that does help a lot. Thank you.

Maybe realted https://github.com/obsidian-tasks-group/obsidian-tasks/issues/208
I can confirm the current behaviour is that

There has been a discussion in Discord of what's involved in implementing folder, in plugins - it starts at this message.

Most likely a markdown post processor for reading view and a code mirror editor extension for live preview
In the editor you can make your extension check if it is in Live Preview mode and render differently/disable itself
for reading view a post processor is the easiest, recommended and supported way to interact with DOM elements
Anything else (like if you're hacking the contents of the DOM directly) won't work well because internally there are optimizations to unload DOM elements out of view
And yeah for fold it'd be a codemirror extension that generates widgets and replacement ranges, and you have to register them because if you don't register them it won't run?
a set of functions doing what
I don't understand what you mean by just making it a set of functions

My conclusion is that it is too much work to ever be feasible in this plugin.
So, in view of this size of the backlog for this project, and the demotivating effect of a very long backlog on volunteer energy levels, and the difficulty of this request, I'm marking this one as 'not planned'. This doesn't mean 'won't fix' - it means not likely to be done in the foreseeable future.


Spelling Fixes

Additional Spelling fixes @Court72

@sloanster
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[Additional Parameter Request] Codeunit 5804 Item Cost Management - OnBeforeUpdateUnitCostSKU

Hi Team,
In codeunit 5804 we need possibility to have additional checks in the procedure UpdateUnitCostSKU. Standard publisher would suit us if it had additional standard parameter CalledFromAdjustment: Boolean as pass by reference . OnBeforeUpdateUnitCostSKU would be perfect solution:

[IntegrationEvent(false, false)]
local procedure OnBeforeUpdateUnitCostSKU(Item: Record Item; var SKU: Record "Stockkeeping Unit"; LastDirectCost: Decimal; NewStdCost: Decimal; MatchSKU: Boolean; CalledByFieldNo: Integer; var UnitCostUpdated: Boolean; var CalledFromAdjustment: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Playing with jobs

looks like you are converging, looks nice if the templates work out this way

I don't think templates are the right thing to use here.  I'm trying to understand how this works. I'm stuck on how to conditionally perform step sequences... DevOps docs are not very clear, to me at least...

wishful thinking on my part, what were approaching for looked sensible :-)

I think I'm on to something.... 🙉

we are counting on you 🙀

Then, all is lost. We still need to build docker images for our tpl sets so we can test everything. I don't really know where to start there.... 💩

pointing and clicking on the path to destruction 🚯


Fix step 4

I've added some notes to step 4 so its a bit easier to accomplish.
In addition I noticed the compute name was different between the compute.json and the run_config.py file so I aligned that name.

Thanks @Ethan-Arrowood. Let me review that later this week.


Simplify Dockerfile and begin transition to standardize on conda environments

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

I like having all of the versions strictly pinned down personally. It does make things slightly more difficult when/if we add or update dependencies but I think the juice is worth the squeeze there.
Might you add the freeze command you used so we can reference it later? My assumption given the detail of the conda files is you generated them from a previously solved environment. I think having that process documented somewhere is critical for other devs to know so if they need to update a dep they can roughly ...

Create environment from this existing file
Modify that environment for their needs
Run your "freeze command", guessing contribution guide is best place for this?
And then last take that and update the conda .yml file with those changes for their PR

Makes sense.
You're right, it was a bit of a bootstrapped process, but, I think going forward it will just consist of updating the created yaml file.


Relax vitest peerDependency

close #5

@chaance would you please take a look on this? Thanks!

Did the author forget about it?

The author is busy. Happy to merge but I have a few other changes lined up before I cut a new release.


Added CopyOnSelect as a Global Setting

Summary of the Pull Request
Introduces the "copyOnSelect" setting to "globals" as a boolean type. When set to true, a selection is immediately copied to your clipboard upon creation. When set to false, the selection persists and awaits further action.

PR Checklist

[x] Closes #524
[x] CLA signed
[x] Tests ~added/passed~ not necessary
[x] Requires documentation to be updated
[x] I am a core contributor

Detailed Description of the Pull Request / Additional comments
Standard "added a new global setting" changes
TermControl's PointerReleased event is updated to support a mouse button release event. Just hooked up the copy function right there.

Validation Steps Performed

copyOnSelect = true

make selection
right click to paste (selection persists)
Works! ✔

copyOnSelect = true

make selection
right click to paste
left click on a cell
right click to paste
same data should be pasted twice
Works! ✔

copyOnSelect = true

click on a cell (no selection)
drag to another cell (selection visible)
drag back to first cell (selection should persist, but should only cover one cell)
Works! ✔

copyOnSelect = false

make selection
selection persists
right click to copy (selection disappears)
right click to paste
Works! ✔

Should the selection disappear? That's not how it works on other terminals.

Should the selection disappear? That's not how it works on other terminals.

Yeah. I originally had it disappear to provide feedback that you copied it. I'm going to change it to:

selection persists after copy
right-click immediately pastes (doesn't do a redundant copy)
click/tap (no drag) should...

not create a new selection
@DHowett-MSFT should it erase old selection?

Question: should setting be renamed to copyMode = {Windows, Unix}? 👍 or 👎 and put your thoughts below!

I think I personally prefer copyOnSelect. It's much more literally what I want - I wouldn't necessarily know that unix means "copy on select". Is there other possible values of copyMode you're thinking of other than Windows vs Unix?

I think I personally prefer copyOnSelect. It's much more literally what I want - I wouldn't necessarily know that unix means "copy on select". Is there other possible values of copyMode you're thinking of other than Windows vs Unix?

IIRC, MacOS's Terminal has a drop-down on right-click. But that's also weird because there'd be different functionality through that drop down menu like "search with Google", I think. I don't remember what the other drop-down options are.

Question: should setting be renamed to copyMode = {Windows, Unix}?

A copyMode of "unix" is pretty ambiguous, IMO it could just as easily refer to line ending conversion as it could to the select/click behaviour. Also, AFAIK (grumpy old man tone) copy-on-select derives more from X and its ancestors than it does Unix.

Alright, decided on the following model for the settings:

copyOnSelect: bool --> when enabled, this makes it so that...

when you make a selection, it gets copied
a single cell selection is not supported (unless you select more than a cell then drag the mouse back to get a single cell)
right-click always pastes

pauseOnSelect: bool (#980) --> when enabled, this makes it so that...

output is paused when a selection is displayed/active

pointer bindings (#1553) --> we'll have a bunch of actions supported. A few include...

right-click (as an example) being bound to...

paste: always paste
smartCopyPaste: copy, if selection active. Paste otherwise.
menu: context menu as shown above

The only tricky part I see here is copyOnSelect's 3rd function potentially interfering with pointer bindings. For now, I say we keep it as is. When pointer bindings comes along, we can make it so that smartCopyPaste specifically clears the selection. Thus kinda breaking this up into 2 things (not a big fan but I feel that that's the best way to approach this issue).

copyOnSelect = false
make selection
selection persists
right click to copy (selection disappears)

Does pressing enter to copy instead of right click work here? I have over a decade of muscle memory pressing enter at this step, and it's currently causing me to make a lot of mistakes in the new terminal.

@zadjii-msft CopyOnSelect tests got added. Note that an "active selection" is considered copy-able. Handling a single cell selection is really weird but I thing the refactor and the test should make it clear what kind of behavior is now expected when using this new mode.

@msftbot make sure @DHowett-MSFT  signs off

I'm running the version in the store. (0.3.2171.0) With this version, click-drag, double-click and triple-click all select and copy to clipboard. Right click removes selection, but does NOT paste. A second right click DOES paste. This is odd.
On other terminal apps on windows and Linux, middle button is paste and right button is menu. Is there an option to get that functionality?
What does middle button do currently?
I don't see a "CopyOnSelect" option in settings.

Our release process can't possibly be that fast.

As of 0.3.2171.0: selection just selects, right-click copies and deselects, and then right-click pastes.
As of [next version]: copyOnSelect is added, but the preexisting behavior stays the same if it is set to false.

I didn't expect it to be in the store release yet, just being clear that I'm not yet testing the current change. :)
I would like to see more Linux-y feel with right button select modes, middle button paste mode, and right button menu. It's been requested before on other posts. I was just wondering if there's a plan for adding that. Thanks for the updates!

Thanks! We haven't yet looked at middle-paste, but we've talked about "mouse bindings" (as a post-1.0 feature)!

Question: I'm using 0.4.2382.0 but I am still having big issues when using WSL with windows terminal. Should I see the copyOnSelect toggle somewhere in the settings? Why don't I see it there?
I am just trying to fix the annoying bug of copying something in my clipboard [from e.g. the notepad or the browser] and then pasting it in my WSL instance within windows terminal. It this PR fixing this issue?

fix the annoying bug of copying something

@alecive what you have described is not a bug (???) so we can't tell if this pull request, which adds an option that makes it so text you select gets copied to the clipboard automatically, fixes it.
(fwiw: add copyOnSelect to your profiles.json as a boolean, either in the globals section or not (if you don't have one))

Awesome!!!!


Timepicker ignores timezone on 'getDate'

I have an input which I have transformed using datetimepicker(), and it looks just fine. All of the inputs are present, things adjust themselves accordingly when I make selections. However, when I go to fetch the Date() object using $('#myDiv').datetimepicker('getDate'), the date selected is always in my local time. I have tried enabling and disabling all of the timezone options described in the documentation but to no avail.
          $('#dateTime').datetimepicker({
		minDate: 0,
		showTimezone: true,
		timeFormat: 'hh:mm z',
	});
	$('#sendDateTime').datetimepicker('setDate', (new Date()));

    function getTimeStringFromField(dateTimePicker)
{
	var schedule = dateTimePicker.datetimepicker('getDate');
	var scheduleString = schedule.toJSON();
	return scheduleString;
}

Hi,
Yes Even I am facing the same issue with the TImezones, It does not Do any timezone conversion when selecting the zone dropdown. Could you please help me out on how I could make it work with this time picker. As of now I am planning to implement some other time picker js for my project


[Icon Request]: Adding official Cucumber  icon for its feature file

Housekeeping

[X] I'm sure this issue is not a duplicate

Icon Type

[X] File Icon
[ ] Folder Icon

Icon Type

[X] Extension
[ ] Filename
[ ] Language ID

Original Icon
The official Cucumber icon.

Icon Information
This official Cucumber icon can be found at
https://github.com/cucumber/html-formatter/blob/main/javascript/logo.svg
More Information:
The existing icon in vscode-icons, which is embedded below, for Cucumber feature files is not  the official icon of Cucumber.

So I am creating this issue along with a PR to update the existing icon for Cucumber feature.

When I create a .feature file in VSCode I get the fallback file icon of text lines. I have installed vitest-cucumber to streamline testing. Am I missing something?


Don't remove other conditions when adding ConfigChangesPendingRestart

Adding a condition of type ConfigChangesPendingRestart is currently removing any other statuses. This fixes that and does some code cleanup.

The change LGTM given Russ' answer to my question. I recommend getting sign-off from Ryan, Dongbo, and Johnny.


Add the Lie-theoretic exponential map

As discussed in https://github.com/JuliaNLSolvers/Manifolds.jl/pull/68#discussion_r361746072

The first decision here seems to be what to call it. Options I can think of are:

gexp
expg
group_exp
exp_group

I prefer expg by analogy to expm in some languages being the matrix exponential, but I'm not thrilled with any of them.
The second decision is where to implement it. For AdditionOperator, it will coincide with the Riemannian exponential, and we can just forward it.
For MultiplicationOperator, it should default to calling exp for Matrix/Number inputs and otherwise be unimplemented. This would cover most textbook groups with a multiplication operation.
Analogously, I prefer logg (though glog sounds great, and now I remember I have some glög left over in the fridge).

We can of course call it glögg (even gløgg is close by), I have ö on my keyboard directly, no problem.
While expm is short and one knows it's the matrix Exponential, I would vote for group_exp for readability. Another possibility is to use the exp(::LieGroup{M}, ::Any...) signature maybe, where LieGroup <: GroupManifold or we do it with GroupManifold? And where I got to names, should we maybe call GroupManifold LieManifold ? For me, Lie just sounds mor familiar.

Sure, we can have glögg as an alias for Lie logarithm 😄 . As primary names, group_exp and group_log sound fine (although I also like lie_exp and lie_log).

I also like lie_exp, but maybe then we should really go for LieManifold for consistency?

Right, it would be inconsistent to sometimes use Lie and sometimes group. Both options, Lie and group, are fine for me.

I am fine with a decision pro-group, but my personal favour would be Lie.

I prefer group. Since all of our manifolds are differentiable manifolds, "Lie group" is redundant. Moreover, we can consistently use "group" everywhere without it sounding weird (e.g. SemidirectProductGroup but not SemidirectProductLie). We could maybe make it "liegroup" in some places, but then we have issues with consistency, and the names include a redundant word.
We already abbreviate some decorator names. e.g. MetricManifold is really PseudoRiemannianMetricManifold, but we shorten for convenience and document what it means.
I'm fine with group_exp and group_log.


Bounty: Style up pages and add pagination to token info and transaction pages (100k VIA)

Style up pages

Home (Account Balances)
Mint
Token

Add pagination

Token Address

Add pagination

Config

Please leave proposal in comments along with VOI Address to deliver rewards upon accepted submission. Account of address provided must have balance.

1837548
https://arc200.algodrop.net/#/token/6779767/address/7EISH72TGOIOMBHON3G5LE3HIZYORQL5R3KLKPI22YRGLW44JUW4UDNFGA

100k VIA sent to 7EISH72TGOIOMBHON3G5LE3HIZYORQL5R3KLKPI22YRGLW44JUW4UDNFGA


Memory error

Hey, I wanted to use it on windows from console and this is what I got:
Reading tiles from '.\belly'...
Processed 34 tiles.
Processing main image...
Traceback (most recent call last):
File ".\mosaic.py", line 221, in
mosaic(sys.argv[1], sys.argv[2])
File ".\mosaic.py", line 214, in mosaic
image_data = TargetImage(img_path).get_data()
File ".\mosaic.py", line 66, in get_data
large_img = img.resize((w, h), Image.ANTIALIAS)
File "C:\Python27\lib\site-packages\PIL\Image.py", line 1645, in resize
return self._new(self.im.resize(size, resample))
MemoryError
I don't know what is the reason, just saying.
Best,
Dawid

got the same MemoryError here

This error is being thrown by the PIL library which this project uses - and apparently it can happen if you pass in a negative height or width value to the resize function. Please add the following line of code before line 66:
print w,h

and let me know what values are displayed. Also, if you can attach the image you are trying to use to this issue I will try to reproduce the problem at this end.


Add feature to activate flag by a cookie

This is motivated by wanting to trigger server side flag through conditions set though a 3rd party a/b testing service.

The right way to do this is to use waffle.set_flag and set the flag based on the other cookie.


[TODO] Hook up Checks API reporting using octomachinery

@webknjaz, 💚 the idea to use the Checks API.
Please let me know where I can help.
Maybe https://github.com/stoe/xo-action could help with some inspiration. It's a JS linter, also using the Checks API.
⚠ My Python skills are limited ⚠
¯_(ツ)_/¯

@stoe I'm working on a framework in Python 3.7+ which is loosely similar to Probot.
You may want to take a look at https://tutorial.octomachinery.dev for a walkthrough.
It supports both GitHub Apps and Actions from scratch but needs waffling and more docs.
The example in README should give you the initial feel of how to use it: https://github.com/sanitizers/octomachinery
In the meantime, I've created this issue as a note for myself once I have time or somebody will be able to pick it up :)

Please let me know where I can help.

You can run subprocesses via https://docs.python.org/3/library/asyncio-subprocess.html#asyncio.create_subprocess_shell (easy way).
Or you could import run from https://github.com/ansible/ansible-lint/blob/master/lib/ansiblelint/main.py#L51 and call it, but it'd probably require patching sys.argv (hard way)
To use it in async world use loop.run_in_executor https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor with https://pymotw.com/3/asyncio/executors.html

Meanwhile, it's possible to convert the ansible-lint output to warnings and errors using workflow commands: https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-a-warning-message. This would work even with a shell script that we have now, as a temporary solution.

Closing because ansible-lint already outputs using github annotations.


Update monitors.md

We keep getting questions about when Test Analytics Monitoring and Alerts will be back. The docs is misleading it says it coming back soon. But Test Analytics confirmed they do not have a concrete timeline
Reference Ticket
https://secure.helpscout.net/conversation/2288060702/53565/

Hello! I had another look -- @mbelton-buildkite , Monitors and Alerts are unlikely to return in their current format. Should we remove the entire sub-section of our TA docs called 'Monitoring' for now?

Monitors and Alerts are unlikely to return in their current format. Should we remove the entire sub-section of our TA docs called 'Monitoring' for now?

I think so, yes. Based on that note, they haven't been available for ~10 months. Let's remove it to give you a clean slate when launching their new form when you're ready.
@meiqimichelle, are there any customers or comms we need to manage? Or could we update this PR to remove the page and be done?


Bug/questionnaires skip logic errors for admin panel

Closes #1489
Closes #1538

StreamBlock & StructBlock validation errors were handled generically before
But in newer versions, wagtail has introduced a specific mechanism to standardize the StreamBlock and StructBlock validation errors
Used the new mechanism for StreamBlock and StructBlock validation errors
Raise validation error when skip logic is added and multi-step isn't enabled.

@istride issues are resolved, could you take a look?

@istride All the issues are fixed, could you take a look?


RC 3: Link to backups broken

The download links to backups are broken. They point to /bl-content/backup instead of /bl-content/workspaces/backup.

Fixed!


Example for proper way to remote load pages

So I have 1 host and one remote both running on nextjs. I wish to be able to remote load a set of pages(for example /pokemon/[number], with both the pokemon as index and numer as pid page) from the remote to the host, including the use of getServersideProps or getInitialProps so that I can achieve SSR on the remote loaded page.
Currently I've managed this somewhat with
import RemotePage from 'remote/Page'

const Page = RemotePage
Page.getInitialProps = RemotePage.getInitialProps;

export default Page

as it's own page component in the host app. However with this setup I'd need to expose every page individually and import them into page files with the correct path in the host container to duplicate the remote container's routing.
Is there a better way to share multiple pages?
How am I supposed to reuse routes from a remote next app?
And how do I make sure the serverside functions are ran on imported pages? (Another example of this I didn't make work is here
Could you add an example of federated loaded pages in the nextjs-mf example repo?

Hello, I have the same doubt. Is there a way to mount an entire remote app with Next with their own routes?
Example: if I have two apps, main and store, the main application has two pages "/" and "/store" and then I want to mount the entire store app in /store with their own sub-routes. Is this possible? something like single-spa.

Not really a good way to inject routes in next. We have router shims that can but its not great and haven't tried to patch it server side.
You can use a [...slug] route and manually call the low level federation API to pull the remote you want.
Generally the best way is mirroring the pages across apps or have a slug route with some logic

Follow-up to best practices for remote loading pages.
What is the best way to remote load pages using functions like getServersideProps, getStaticPaths etc?
Currently I'm using a method used in multiple examples (like the Universe project)
import dynamic from 'next/dynamic';
import { NextPage, NextPageContext } from 'next';
const page = import('fjellovergang/fjellovergang')
const Fjellovergang = dynamic(() => import('fjellovergang/fjellovergang')) as NextPage;
Fjellovergang.getInitialProps = async (ctx: NextPageContext) => {
// capture the getInitialProps function from the page
const getInitialProps = ((await page).default as NextPage)?.getInitialProps;
if (getInitialProps) {
// if the function exists, call the function on server-side and client-side
return getInitialProps(ctx);
}
return {};
};
export default Fjellovergang
However this only supports getInitialProps. I'm uncertain what the best way to utilise the other page-functions is?

It supports any and all data fetching options. Not just get initial props.

I prefer explicit page exports, but you can also create a catchAll slug route that dynamically loads one of the pages depending on what the slug value is.


fix: restore errors namespace in declaration file

Restores the errors namespace in the declaration file.
I accidentally removed it in the last PR that generated the declaration file.

This is fairly straightforward and just a declaration file fix so I'm going to merge and release.


Event Registry - Sources Part 1

First part of sources for the Registry feature request: https://github.com/knative/eventing/issues/929
Important

This still doesn't address the changes of CloudEvents source and subject attributes. There is still some debate of what should be put in each. This PR just sets the framework necessary to easily set those attributes in a subsequent PR.
Changes to Sources CRD to include description and schema attributes are not there yet.

Proposed Changes

Creating EventTypes in the following source controllers, from which we know (at least some of) the events they can produce:

GitHub
AWS SQS
GCPPubSub
Kafka

Only creating the EventTypes for Broker sinks.
Created a common EventType "reconciler" helper to avoid duplicating code across the source controllers.
Adding dependency of the eventing repo  (and updating pkg)

Release Note

On installing a source CO (GitHub, AWS SQS, GCPPubSub, or Kafka), its EventTypes will be added to the Registry.

/cc @vaikas-google @grantr @Harwayne @akashrv @n3wscott @duglin
Here is the sources part of the Registry stuff I've been experimenting with. Comments and feedback are highly appreciated.

@Abd4llA this is the sources part of the Registry proposal. Also WIP, but it'd be great to have your input.
Thanks!

/cc @vaikas-google @grantr @Harwayne @akashrv @n3wscott @duglin
Here is the sources part of the Registry stuff I've been experimenting with. Comments and feedback are highly appreciated.

Which file has the github types? I couldn't find it when I searched

Which file has the github types? I couldn't find it when I searched

You mean this one? https://github.com/knative/eventing-sources/blob/a81e4bf176fdde1549c7a6e339b3baf185e7e1b6/pkg/apis/sources/v1alpha1/githubsource_types.go
I'm not changing any of the type CRDs as of now. Just using them as is for an initial cut.
With the GitHubSpec fields I'm creating the EventTypes CRs in the GitHub source controller.

Problem here: https://github.com/knative/test-infra/issues/638
/retest

@vaikas-google @grantr @Harwayne @n3wscott
This is ready to start reviewing. Please look at the PR description, this still doesn't include the change to source and subject, as it seems we are still not in full agreement.

/retest

/test pull-knative-eventing-sources-integration-tests

The problem seems to be that the e2e script pulls the eventing nightly build:
readonly KNATIVE_BASE_YAML_SOURCE=https://storage.googleapis.com/knative-nightly/@/latest
<EMAIL_ADDRESS>As we've just merged the registry change in eventing, it will be in the next nightly build, and therefore tests should start passing (hopefully)
Will wait until tomorrow and rerun them.

/test pull-knative-eventing-sources-integration-tests

@vaikas-google @Harwayne @grantr @n3wscott friendly call for reviews :)

Got through everything!

Thanks a lot @grantr . Your review was very helpful! Will let you know when is ready for a second pass

Tested gcppubsub, kafka, and github... Seems to be working fine.
Cannot easily test aws sqs.
NAME                                          TYPE                                     SOURCE                                                          SCHEMA   BROKER    DESCRIPTION   READY   REASON
dev.knative.kafka.event-cjvcr                 dev.knative.kafka.event                  topic2                                                                   default                 True
dev.knative.kafka.event-tdt48                 dev.knative.kafka.event                  knative-demo-topic                                                       default                 True
dev.knative.source.github.pullrequest-pkb8c   dev.knative.source.github.pull_request   nachocano/eventing                                                       default                 True
dev.knative.source.github.push-vmbl2          dev.knative.source.github.push           nachocano/eventing                                                       default                 True
google.pubsub.topic.publish-hrxhh             google.pubsub.topic.publish              //pubsub.googleapis.com/knative-project-228222/topics/testing            default                 True

@grantr @vaikas-google @n3wscott
this is ready for a second pass. There are a couple of separate follow up issues that I can take care later on, but the basic functionality herein seems to be working (see kubectl get eventtypes output above). The main one is a refactoring of the eventtype reconciler proposed by Grant, which makes a lot of sense. I guess I didn't get it right away.
The next PR should contain the changes to source and subject.

/approve

Made a small refactor to make it easier for the bigger one later on. Added the eventtype package again, inside reconciler, with its own resources dir.

@grantr @vaikas-google @n3wscott friendly ping to lgtm (or keep on adding comments) so that I can continue with the follow ups.

I already approved, sorry. should've said explicitly, letting @grantr @n3wscott take a look since they had some suggestiongs.

Just the one change left from me (remove Raw) then

Done!

/lgtm


Fix AttributeError: MixtralModel object has no attribute org_vocab_size.

Mixtral cannot start because of this error:
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1695, in __getattr__
    raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
AttributeError: 'MixtralModel' object has no attribute 'org_vocab_size'. Did you mean: 'vocab_size'?

Related PR: #2831

You are right, this is indeed broken at the moment!
There seems to be some divergence on how things are working for Mistral vs. Mixtral (Mixtral has self.vocab_size = config.vocab_size whereas Mistral has self.vocab_size = config.vocab_size + lora_vocab and self.org_vocab_size = config.vocab_size) -- any thoughts about this @Yard1 ?

For this, Mistral has the correct logic and Mixtral should follow it exactly.

Let me try to update that @Pernekhan do you mind if I push to your PR to update it?

Unfortunately I couldn't push to this PR, so made a new one including your commit @Pernekhan :)
https://github.com/vllm-project/vllm/pull/2880


css styling of hacktober section

hi there,
i wanted to update the css styling of the hacktober section like in the issue i raised #226, #225 but the merge pull request wasn't successful, so i'm trying it again. #249 is a closed pull request, before I realised the branch I was working on was really behind and tried merging my main branch with the current version and adjust some changes, to keep everything that was already there. Not sure if it's the correct way of doing and apologies if it causes any issues!
This is what it looks like on my local machine:

This issue has already been resolved,
Please, try to find a new issue to work on.


Add this repo as a Homebrew Formulae

In the same way that your main argc utility is part of brew, it would be handy to package up this repo so a simple brew install argc-completions would do the work of installing its dependencies and adding a few lines to someone's rc file. This would go a long way towards simplifying users' environment building automations they may have.
Thanks for this repo!

Not now.


chore: durability updates for TSM snapshots

Closes # https://github.com/influxdata/idpe/issues/13699
We're adding an occasional backup of TSM files.  The purpose is to allow us to satisfy our backup requirements without needing to keep the OOB backups forever (as we do today).  This will allow us to make commitments on how quickly deleted data is purged from our systems - today we cannot make any such commitment.
This PR adds some minor description of the new TSM backup.  More or less detail could be provided - I tried to mimic the level of detail in the other sections.

[ ] Signed the InfluxData CLA
(if necessary)
[ ] Rebased/mergeable

LGTM.
I don't think this is worth elaborating on in the documentation, but I'll provide some more detail here and you can include it if you think its appropriate.  Regarding the 100 days:  We are required to have 90 days of backups, which I'm interpreting to mean we must always have a backup available to protect data 90d old.
So with weekly backups kept for 100d, the oldest backup at any time will be 93-100d old.  That's because when a backup reaches 100d old and we delete it, the next oldest backup is 93d old (giving us 3d of buffer before violating our commitments).
All we want to commit to is 90d protection, as stated in our TOS.  That is accomplished by keeping weekly backups for 100d.
I think this documentation is fine as it is, because this doc is explaining what we do, not necessarily what we commit to.

Thank you, @Joe-Blount, I agree this is good for our docs site context.
This add'l context like this maybe appropriate for our Sales Enablement on Disaster Recovery brochure @lwandzura, @bpalani?
cc @noramullen1 @garylfowler @gunnaraasen - re Monthly Cloud updates


feat: port Order.Filter.Ultrafilter

Did you use start_port.sh?

I did, but I think the script failed at some point so not everything was done automatically (it was some awk error, I'll investigate a bit more this evening). Did that create a problem in any way?


@koa-shopify-auth doesn't start authentication

Bug summary
Write a short description of the bug here ↓
The app works perfectly on a local development environment via ngrok - but throws a 404 errors, graphQL unexpected token < in JSON at position 0, and never authenticates when deployed to an aliased domain via ZEIT Now.
Expected behavior
The app should run and authenticate identically on a domain name as it does locally.
Actual behavior
If deployed to ZEIT, the authentication URL would look like this.
https://shopify.viaglamour.com/auth?shop=via-staging2.myshopify.com
Opening this URL throws a 404 error. The @shopify/koa-shopify-auth is meant to recognize the /auth and begin the process of authentication but never does.
If I set the app's URL (and all the whitelisted URLS) back to my ngrok environment.
https://c6108518.ngrok.io/auth?shop=via-staging2.myshopify.com
The authentication screen is triggered and the app runs successfully!
Demo: https://gyazo.com/78e3a16fef817e73551895670eebaa5a
Steps to reproduce the problem

Deploy the app to ZEIT.
Change local environment variables (like TUNNEL_URL) to the deployed ZEIT domain.
Attempt to authenticate via the URL

Hi @keiraarts! Are you using the 'build' command at any point to deploy? We haven't built out that command for the tutorial, and I'm pretty sure it doesn't pick up the custom server on build.
The guide doesn't cover deploying at the moment, but I have a feeling that the issue you're having is because npm run build builds the front end of the app.
Because this has a custom server, you'll need to modify the build command.
I found this on the next forums:
https://spectrum.chat/next-js/general/custom-server-in-production~81cd6879-9d7f-41b8-be3f-f69d86214d33
You'll probably want to write a small script that includes 'NODE_ENV=production node server.js
I'm going to add a feature-request tag to this as we've had a couple people asking about building for production :)

Hiya Katie!
I am using the build command, though I'm starting to doubt my deployments haha.
Are there any repositories available that show a deployed demo app (that authenticates) at Shopify?
I'd love to reverse-engineer something to find my mistake.

Hey @keira! There aren't at the moment that I know of.
I'm going to try to work on something as a demo, but I can't promise how quickly I can get it out. I do think the spectrum forums and issues on zeit/next.js can help in the meantime though. You need to make sure you create a build, and that when you deploy (I believe Zeit uses the start command) you're running a production version of the node server. I will ping you for sure when I have something ready, but I understand you want to get this app out there.
It looks like this might help too: https://github.com/Shopify/shopify-demo-app-node-react/issues/9

I got progress @katiedavis!
The /auth is now being recognized after setting the production server. I also had to change the now.json configuration to include the environment variables.
"build": {
"env": {
"SHOPIFY_API_KEY": "--",
"SHOPIFY_API_SECRET_KEY": "--"
}
}
There's one last issue. I know I'm asking a lot - but maybe you've seen it before!
When visiting /auth on a production environment (and using the full domain on the app setup) the console throws this error.
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://via-staging2.myshopify.com') does not match the recipient window's origin ('https://shopify.viaglamour.com').
I can recreate the error on a local environment if the origin URL != the URL in app setup.
But in a production environment the console ALWAYS throws this error regardless if the app setup's, environment variables, or now.json configuration matches the requested URL. It's happening on my own project and a cloned version of this tutorial.
GIF Demo: https://gyazo.com/cc337c362806f70c7eb5368f0a8a7f12
If you have any suggestions (like before!) it might help me get this app finished!
Otherwise I'm eagerly awaiting a deployed demo to pick apart.
Thanks for your generous help Katie!

Consider the issue closed! @katiedavis
This entire time I was deploying with Zeit's now that is serverless.
My Koa server was never going to work to authenticate there.
I changed my deployment to Heroku and the issue is resolved.
The fun of learning development! Thanks again for pushing me in the right direction.


Rely on email.Address.String() to properly format To, From, etc.

Let golang's builtin routines take care of proper encoding and quotation of display name and adresses.

This seems reasonable to me. I think the original code was written before this was built in to the stdlib (even though that was years ago at this point!).
Thanks for sending this in.


Use pre-processors (like sass/scss, stylus, etc) with VueJs sfc in storybooks (extending webpack with loaders)

Issue details
I would like to use pre-processors (mainly scss) with VueJs Single File Components.
Extending the Button.vue (of the Kitchen Sink)
<style lang="scss">
  .button {
    border: 3px solid;
    padding: 10px 20px;
    background-color: white;
    outline: none;

    &.--rounded {
      border-radius: 5px;
    }
  }
</style>

Doing the following steps, causes stories to be empty.
Steps to reproduce
1. Install  sass-loader & node-sass:
According the vue-loader documentation, you need to install the npm packages sass-loader & node-sass:
npm install sass-loader node-sass --save-dev

2. Extend the webpack.config.js by Including the ‘loader’ in the ‘module’:
Using the Full control mode + default
const path = require('path');
const webpack = require('webpack');

module.exports = (storybookBaseConfig, configType, defaultConfig) => {
  // configType has a value of 'DEVELOPMENT' or 'PRODUCTION'
  // You can change the configuration based on that.
  // 'PRODUCTION' is used when building the static version of storybook.

// ------------------------------------ ADDED START ------------------------------------
  // Extend it as described in the vue-loader documentation
  defaultConfig.module.rules.push({
    test: /\.vue$/,
    include: path.resolve(__dirname, '../src'),
    loader: 'vue-loader',
    options: {
      loaders: {
        scss: 'vue-style-loader!css-loader!sass-loader', // <style lang="scss">
        sass: 'vue-style-loader!css-loader!sass-loader?indentedSyntax' // <style lang="sass">
      }
    }
  });
// ------------------------------------ ADDED END ------------------------------------

  // Make whatever fine-grained changes you need
  defaultConfig.plugins.push(
    new webpack.optimize.CommonsChunkPlugin({
      name: "vendor",
      chunks: ['preview'],
      minChunks: function (module) {
        // this assumes your vendor imports exist in the node_modules directory
        return module.context && module.context.indexOf("node_modules") !== -1;
      },
    })
  );
  // config.resolve.extensions.push('.vue');

  // Return the altered config
  return defaultConfig;
};

3. Running the Storybook:
npm run storybook

><EMAIL_ADDRESS>storybook C:\vue-kitchen-sink
> start-storybook -p 9009 -s public

info @storybook/vue v3.4.0-alpha.8
info
info => Loading static files from: C:\vue-kitchen-sink\public .
=> Loading custom .babelrc
=> Loading custom addons config.
=> Loading custom webpack config (full-control mode).
webpack built f69a7575bbf3851ad9f1 in 7347ms
info Storybook started on => http://localhost:9009/
info

No errors. But stories are empty.
Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/vue 3.1.13
@storybook/vue ^3.4.0-alpha.8

Affected platforms

Affected on everywhere platform
Webpack config might be the issue i guess

Screenshots / Screencast / Code Snippets (Optional)
Below I'll just post the code of the files that are involved.
Basically there are no major changes, except the block in the webpack.config.js.
Everything is based on the vue-kitchen-sink provided by the storybook package, which worked as expected before the changes had been made.
Button.vue
<template>
  <div>
    <button class="button" :style="{color: color, borderColor: color}" @click="handleClick" :class="{'button--rounded': rounded}"><slot></slot>!</button>
  </div>
</template>

<script>
  export default {
    props: {
      rounded: Boolean,
      handleClick: {
        default: () => () => null
      },
      color: {
        default: '#42b983'
      }
    }
  }
</script>

<style lang="scss">
  .button {
    border: 3px solid;
    padding: 10px 20px;
    background-color: white;
    outline: none;

    &.--rounded {
      border-radius: 5px;
    }
  }
</style>

package.json
{
  "name": "vue-example",
  "version": "3.4.0-alpha.8",
  "private": true,
  "scripts": {
    "build": "cross-env NODE_ENV=production webpack --progress --hide-modules",
    "build-storybook": "build-storybook -s public",
    "dev": "cross-env NODE_ENV=development webpack-dev-server --open --hot",
    "storybook": "start-storybook -p 9009 -s public"
  },
  "dependencies": {
    "vue": "^2.5.13",
    "vuex": "^3.0.0"
  },
  "devDependencies": {
    "@storybook/addon-actions": "^3.4.0-alpha.8",
    "@storybook/addon-centered": "^3.4.0-alpha.8",
    "@storybook/addon-knobs": "^3.4.0-alpha.8",
    "@storybook/addon-links": "^3.4.0-alpha.8",
    "@storybook/addon-notes": "^3.4.0-alpha.8",
    "@storybook/addon-storyshots": "^3.4.0-alpha.8",
    "@storybook/addon-viewport": "^3.4.0-alpha.8",
    "@storybook/addons": "^3.4.0-alpha.8",
    "@storybook/vue": "^3.4.0-alpha.8",
    "babel-core": "^6.26.0",
    "babel-loader": "^7.1.2",
    "babel-preset-env": "^1.6.0",
    "babel-preset-vue": "^2.0.1",
    "cross-env": "^5.1.3",
    "css-loader": "^0.28.9",
    "file-loader": "^1.1.6",
    "node-sass": "^4.7.2",
    "sass-loader": "^6.0.6",
    "style-loader": "^0.20.1",
    "vue-hot-reload-api": "^2.2.4",
    "vue-loader": "^13.7.1",
    "vue-style-loader": "^3.1.2",
    "vue-template-compiler": "^2.5.13",
    "webpack": "^3.11.0",
    "webpack-dev-server": "^2.11.1"
  }
}

webpack.config.js
const path = require('path');
const webpack = require('webpack');

module.exports = (storybookBaseConfig, configType, defaultConfig) => {
  // configType has a value of 'DEVELOPMENT' or 'PRODUCTION'
  // You can change the configuration based on that.
  // 'PRODUCTION' is used when building the static version of storybook.

  defaultConfig.module.rules.push({
    test: /\.vue$/,
    include: path.resolve(__dirname, '../src'),
    loader: 'vue-loader',
    options: {
      loaders: {
        scss: 'vue-style-loader!css-loader!sass-loader', // <style lang="scss">
        sass: 'vue-style-loader!css-loader!sass-loader?indentedSyntax' // <style lang="sass">
      }
    }
  });

  // Make whatever fine-grained changes you need
  defaultConfig.plugins.push(
    new webpack.optimize.CommonsChunkPlugin({
      name: "vendor",
      chunks: ['preview'],
      minChunks: function (module) {
        // this assumes your vendor imports exist in the node_modules directory
        return module.context && module.context.indexOf("node_modules") !== -1;
      },
    })
  );
  // config.resolve.extensions.push('.vue');

  // Return the altered config
  return defaultConfig;
};

Please specify which version of Storybook and optionally any affected addons that you're running
3.1.13

Which package is that? You need to use the same version for main storybook package and addons

I suspect that this is actually a configuration issue. We're using vue, scss, and storybooks at work and it works fine.
Vue loader will handle all calling the loader automatically for you. All you should have to do is install sass-loader and node-sass.

It's definitely a configuration issue, no doubt, but just installing sass-loader and node-sass seems not to be enough.
Are you using scss in your vue components at work? (within style-tag in the FooComponent.vue)
My steps to test scss in vue components:
git clone https://github.com/storybooks/storybook.git .
cd examples/vue-kitchen-sink/
npm install sass-loader node-sass --save-dev
npm install
npm run storybook

editing ./src/stories/Button.vue
1. Changing style to something sassy:
<style>
  .button {
    border: 3px solid;
    padding: 10px 20px;
    background-color: white;
    outline: none;

    &.--rounded {
      border-radius: 5px;
    }
  }
</style>

2. Apply the changes to the template:
<template>
  <button
    class="button"
    :style="{color: color, borderColor: color}"
    @click="handleClick"
    :class="{'button--rounded': rounded}" <!-- change to button-rounded -->
  >
    <slot></slot>!
  </button>
</template>

Previewing the Rounded Button in the storybook shows the class has been added to the button, but the nested styles, fx. button--rounded, are not provided.
That's why I tried to override the webpack config in my first example above, according the vue-loader documentation, which leads to empty stories. ¯_(ツ)_/¯
If styles in vue sfc works for you, i would appreciate a snippet of your config(s) and package.json, if that is possible.

Embarrassing!
@zephraph it's absolutely true, that you only have to install sass-loader and node-sass...
I was using ampersand-syntax the wrong way, which I didn't notice. 👎
Don't do: &.--rounded { it is just &--rounded { without a dot. Really sorry for this fail.

still have the same issue in 4.0.0 or 4.0.4 for storybook/vue


Please edit the topic to Hacktoberfest

Currently, it is marked as not participating in hacktoberfest because the topic currently does not have the 'k' of Hacktober.
Please do it as soon as possible so the PR's get counted.
And also mark hacktoberfest-accepted with the k in it.
Thanks in advance

Yes, can you add topics "hactoberfest", "hactoberfest-2020" in the topic otherwise this repo won't be particpating.

@PriyavKaneria @umangag07
Thanks for the info!
I have made the required changes. Feel free to dm me if there's some issue. :)