[Bug]: Unable to run init script on windows

What is the location of your example repository?
Just need to install on windows
What version of Hydrogen are you using?
2023.1.2
What version of Remix are you using?
1.12.0
Steps to Reproduce
I.
1 - Try on win10
2 - run npx @shopify/create-hydrogen@latest or any equivalent available in the doc
3 - Choose typescript and hello-world
Expected Behavior
Install dependencies and server to start
Actual Behavior
With npx @shopify/create-hydrogen@latest
C:\Users\d****\AppData\Local\npm-cache\_npx\e1eac94ad41cc36f\node_modules\yoga-layout-prebuilt\yoga-layout\build\Release\nbind.js:53
        throw ex;
        ^

[Error: ENOENT: no such file or directory, lstat 'C:\Users\d****\AppData\Local\npm-cache\_npx\e1eac94ad41cc36f\node_modules\<EMAIL_ADDRESS> {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'lstat',
  path: 'C:\\Users\\d****\\AppData\\Local\\npm-cache\\_npx\\e1eac94ad41cc36f\\node_modules\\<EMAIL_ADDRESS>}

Same issue i am facing last 2 days , please when this wil be fix it


Camera only screen

Great software.  It would be great to have a camera only screen, so that it can be put on a TV to monitor many printers without scrolling.  maybe the ability to choose how many are in the onscreen grid or auto size the video to have all printers on a single screen.

Please check the section in the readme about custom css... you can control the size of everything

I did see that, but didn't see a way to have the cameras only.  I was thinking it would be a tv that hung above the printers and would only have the cameras and id, maybe a status word (running, paused, offline), but no controls.  Strictly visual only.


start a typescript test suite [phab:D1310]

Created by evmar at 2017-02-07 01:43:28:
Add a program that runs the validator on a directory of tests.
This program is written in TypeScript so that it can reuse the
cached TypeScript standard library across tests.
Implement a tiny bit more of indexer to get the test to pass.
This indexer is still no good.  In particular, the signature for a
symbol used here is wrong, but it serves as a starting point.

zarko commented inline (context lost during migration) at 2017-02-07 18:30:26:
I would expect this to build the tests if they're not already built.

zarko commented inline (context lost during migration) at 2017-02-07 18:30:26:
Please fix.

zarko wrote at 2017-02-07 18:30:26:
The (possibly unfounded) concern I have with this approach is whether independent test cases will end up sharing more than the standard library with one another. As you've indicated, doing this sharing is important to keep latency down, especially if the test suite grows large. If we discover any weirdness down the line we might have to rethink how this works.

zarko accepted this revision at 2017-02-07 18:30:26

evmar wrote at 2017-02-07 19:09:50:
add 'build' command, mention it in docs, add newline

evmar wrote at 2017-02-07 19:13:24:

fix browse

zarko wrote at 2017-02-07 21:54:08:
Still LGTM.

evmar commented inline (context lost during migration) at 2017-02-07 21:55:27:
This change makes the autoformatter output for this code look better (I forgot to run it on the previous change).  Otherwise the code is more or less the same before or after.

evmar commented inline (context lost during migration) at 2017-02-07 21:55:27:
I'm not happy about this variable name but I'm not sure what to call vnames.
In my larger branch (that has more of the indexer implemented) I frequently ran into the problem where I have some thing, e.g. a type or whatever
let type: ts.Type = ...;
and then I make a Kythe vname for it and I don't know what to call that, so I went with kType.
It reads like a constant though.

evmar commented inline (context lost during migration) at 2017-02-07 21:55:27:
Hm, this is gonna be annoying, because yarn is not a build system and it doesn't know that you need to build before running the tests.  I could make it always build, I guess?  I suppose eventually this will need to use a real build system, and I kind of hate the JS build systems.  Do you mind if I punt this to just more documentation for now?

evmar wrote at 2017-02-07 21:55:27:
Oops, I failed to submit my comments (they're all just commentary on the code).  Sorry, still new to Phab.

zarko commented inline (context lost during migration) at 2017-02-07 21:59:30:
That's fine.

zarko closed via commit 58cdb43a646413cee7e3d52c55ebad03aa37338d at 2017-02-07 22:02:18


Fixes #20147 -- Added Request.headers

Original PR (with discussion included): https://github.com/django/django/pull/9925
I've rebased from master and squashed all the commits into one.

👋 folks, there's only one build failing with: ModuleNotFoundError: No module named 'memcache'
I haven't changed any dependency or setup.py file, do you have an idea of what might be going on?
Thanks!

There seems to be an error with jenkins not finding the right commit after the rebase. Anybody has an idea how I could fix this?

everything seems passing

You're right, when I submitted the PR originally, it was failing, it's working now 👍

@carltongibson @timgraham PR finally rebased and working. Thanks for all your support. Gonna say this once again, this community is amazing.

Hello @carltongibson @timgraham 👋 ! You think I could merge this one or should I make any other improvement?

Hi @santiagobasulto. As far as I can see the comments from @jschneier and @adamchainz remain unaddressed.
Just dropping Immutable from the naming may be enough to address @jschneier's point (???)
Overall it seems quite good to me. If you can address the points and then uncheck Patch needs improvement on the ticket, I'll have another look. (Seems like a nice feature for the amount of code.)

Great, thanks @carltongibson. I'll get on it and update soon.

Hi @santiagobasulto.
This still looks good. It would be a super addition for v2.2.  (If not we'll see if we can pick it up...)
Re @jschneier's query on immutability, from PEP 3333 (the WSGI spec):

The environ parameter is a dictionary object, containing CGI-style environment variables. This object must be a builtin Python dictionary (not a subclass, UserDict or other dictionary emulation), and the application is allowed to modify the dictionary in any way it desires.

So it's not immutable by design.
Your ImmutableCaseInsensitiveDict implements Mapping (which is read-only, vs MutableMapping) so maybe just CaseInsensitiveMapping, not worrying about actual immutability.
Request.headers is then (via your EnvironHeaders) a case-insensitive read-only accessor. (Just what we want.)
(Anybody wanting to actually mutate Request.META — Why? 🙂 — can access it directly.)
Moving EnvironHeaders as per @adamchainz's review and making the adjustments Tim suggested shouldn't leaving it far off.

Hey @carltongibson! Yes, I'll get to this immediately and push the fixes by tomorrow. Sorry, I've been quite busy lately but I don't want to keep postponing this.

Hi Santiago. Thanks for the work! I will review on Tuesday, so no panic. 🙂

@carltongibson Agree completely on the Mapping suggestion, I'll fix it now. I somehow missed one of Tim fixes. I'll update everything together.

Looking good! I love the changes

@carltongibson all done now, I'll submit the doc changes in a separate PR. I'll take some time to read the whole text and see if there are other improvements to do. Thank so much again for your patience.


Add a standalone live captions demo

Uses microphone captured speech to display Moonshine transcriptions as live captions on the console.

Thanks to @evmaki for contributions in this PR, e.g.: from here https://github.com/usefulsensors/moonshine/pull/34.

Thank you for the review Manjunath.


Different page structure between android and ios

Well the behavior is documented, but I think that is a really bad practice in terms of modularity.
As you may see the Material layout is almost the same. It just has different CSS files related to Material theme, and a bit different page structure where Navbar and Toolbar are inside of the page
http://www.idangero.us/framework7/docs/app-layout.html#basic-android-material-app-layout
For example, I have an app with the old structure where only ios style is available.
Now the migration to make the app compatible visually with android and IOS is a completely pain, since the structure changes, and implies strong modifications in includes and page structure. The ideal behavior should be only something like this:
if (getMobileOperatingSystem() === 'iOS') {
    console.log('ios');
    document.write('<link rel="stylesheet" href="{{url_for("static", filename="css/framework7.ios.min.css")}}">');
    document.write('<link rel="stylesheet" href="{{url_for("static", filename="css/framework7.ios.colors.min.css")}}">');
} else {
    console.log('android');
    document.write('<link rel="stylesheet" href="{{url_for("static", filename="css/framework7.material.min.css")}}">');
    document.write('<link rel="stylesheet" href="{{url_for("static", filename="css/framework7.material.colors.min.css")}}">');
}

Well the summary is, the page structure should be the same for both styles, in terms of cleaning, migration and future modularity, in my opinion.

Discussed many times. These OSes have pretty different structure and many things are just impossible to do with same HTML layout. Nothing painless, all you need is to just move navbar to page. Otherwise you may use "Fixed" navbar for iOS as well and have totally same layout


Highlight drop area on hover for categories and folder

Right now, there is no indication that an area is droppable. The folders or categories should be highlight on drag over so indicate that they are a dropzone.

Hi @taniarascia !
I would like to work on this.
Thanks.

I think I've done it.
#162

#162 covers categories, will just need to copy that code over to the other folders.

#164 This seems to have made drop coloring for both favorites and trash.

Closed in #162 and #164


"lefigaro" site , no video

go to www.lefigaro.fr
not any video is played with this site
we get a blank screen instead of a video screen
the error message is "animation non chargée" . in english "the application is not loaded" .
no pb with chromium
i join a FF capture

and a chromium capture

i join the link of the example
http://www.lefigaro.fr/societes/2015/04/27/20005-20150427ARTFIG00007-airbus-fete-les-10-ans-de-l-a380-et-envisage-de-nouveaux-developpements.php

Hello. There is similar issue #153 which is caused by interference with HTTPS Everywhere browser addon.
Due to differences in PPAPI and NPAPI, freshwrapper code ignores stream from browser and asks for plugin content separately. HTTPS Everywhere successfully redirects initial plugin content from http to https, but block all further http requests, and thus video doesn't load.
As far as I know, HTTPS Everywhere have an exclusion list where particular site can be added, as a workaround.

I've submitted fix for #153 in abe3d525c9bd858e8eb7aeb05fa5b53261ebcc46. I believe it's related to the issue with www.lefigaro.fr and HTTPS Everywhere addon.
Could you check again with recent version?

i get the 0.2.4 version .
i wait for the 0.3.0 one (perhaps 1 or more) for my opensuse 13.1 x86_64 then will test .
thanks

I wait for the 0.3.0 one (perhaps 1 or more week)

I like your optimism. :smiley:
I don't have regular release schedule, but they tend to happen once per one or two months. v0.2.4 was only four days ago, so it would be long wait. And long ago I thought development would be faster and decided to make v0.3.0 release after certain features implementation, with hardware video decoding acceleration amongst them. That one looks particularly hard, so most probably next release would be v0.2.5 instead.
Good luck waiting! :smiley:

Opensuse 13.1 x86_64
Freshplayerplugin 0.3.0-1.1
no more pb with video and HTTPS Everywhere
thanks

OK, great.


{Doc} Update cffi troubleshooting, extension authoring and onboarding guide

Description

Update cffi troubleshooting when there's no RPM package;
Add back vendored SDK guidance;
Add PLR process in onboarding guide.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Doc


Update dependencies and workflows

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (4c6ca0b) to head (b964a5a).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #613   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           71        71
  Lines         1896      1896
  Branches       225       225
=========================================
  Hits          1896      1896

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Different target frameworks in projects and packages

Hello, while playing with VSColorOutput I have noticed that there is targetFramework="net46" in packages.conf but in csproj files there is <TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion>
That can be fixed pretty easy the only thing you should decide framework to stick with.
The reason why I am asking abouth that change is because after clongin and compiling project - whole packages.conf files and cproj files are changed and messing things up, so it is hard to decide what should be commited and what not.

@mike-ward will it be ok to commit net452? or you wish to stick with net46?

It needs to be 4.5.2. I got nothing but grief from trolls about moving to 4.6. Guess upgrading .NET was more than they could handle.


TypeError happened on export CSV after js file compression

I was working on a function that export to CSV only selected rows. It went well until I tried to compress my js file. I used several plugins including gulp-minify, gulp-uglify, closure compiler and all got same error:
Uncaught TypeError: c.getSelected is not a function
    at Object.c.handleExportCSV [as onExport] (default.js:956)
    at onClick (default.js:981)
    at Object.y (default.js:70)
    at x (default.js:70)
    at v (default.js:71)
    at t (default.js:72)
    at c (default.js:73)
    at z (default.js:73)
    at d (default.js:72)
    at C (default.js:74)

And this is my code:
const columns = [{
          dataField: 'id',
          text: 'Category ID'
        }, {
          dataField: 'name',
          text: 'Category Name'
        }];

        const selectRow = {
          mode: 'checkbox',
          clickToSelect: true
        };

        const { ExportCSVButton } = CSVExport;

        return(
            <ToolkitProvider
              keyField="id"
              data={ this.state.categories }
              columns={ columns }
              exportCSV={ {**onlyExportSelection: true**} }>
              {
                props => (

                    <ExportCSVButton { ...props.csvProps }>Export CSV!!</ExportCSVButton>

                    <BootstrapTable
                      { ...props.baseProps }
                      selectRow={ selectRow }
                    />

                )
              }
            </ToolkitProvider>
        );

After it, I also tried setting 'exportAll: false' instead of 'onlyExportSelection: true'. Still got an error:
Uncaught TypeError: l.getData is not a function
    at l.handleExportCSV (product.bundle-min.js:1)
    at onClick (product.bundle-min.js:1)
    at Object.<anonymous> (product.bundle-min.js:1)
    at d (product.bundle-min.js:1)
    at product.bundle-min.js:1
    at C (product.bundle-min.js:1)
    at k (product.bundle-min.js:1)
    at j (product.bundle-min.js:1)
    at S (product.bundle-min.js:1)
    at R (product.bundle-min.js:1)

I wonder that is there any mistake or potential name conflict error in your source code? Could you check it out? Thank you so much!

I am also getting this issue, but I am using webpack to uglify my code. my error is very similar:
Uncaught TypeError: s.getData is not a function
    at s.handleExportCSV (main.js?cdd4c96474ec80a14813:25)
    at onClick (main.js?cdd4c96474ec80a14813:25)
    at Object.<anonymous> (main.js?cdd4c96474ec80a14813:51)
    at Object.invokeGuardedCallback (main.js?cdd4c96474ec80a14813:51)
    at Object.invokeGuardedCallbackAndCatchFirstError (main.js?cdd4c96474ec80a14813:51)
    at R (main.js?cdd4c96474ec80a14813:51)
    at w (main.js?cdd4c96474ec80a14813:51)
    at q (main.js?cdd4c96474ec80a14813:51)
    at P (main.js?cdd4c96474ec80a14813:51)
    at L (main.js?cdd4c96474ec80a14813:51)

When I build without minifying, then it succeeds, but shouldn't you want it to work with all minifyers?
I believe that there might be an actual bug. I love the table.
Thanks for the help!

I will look into it.

Any update on this issue? Thanks!

https://react-bootstrap-table.github.io/react-bootstrap-table2/blog/
Try to upgrade to newest version, I'm not very sure if I fixed it, so please help me to check and tag me if the problem still remain, thanks

@AllenFang I am still getting the error after updating to 1.3.1.
I have found that the error only occurs when I set exportAll to false. This might help you in your search to fix the issue. Thanks!

+1. Still getting this error. And it also occurs when I set onlyExportSelection to true.

@AllenFang I am running into the exact same issue as @kmb266, using 1.3.1

thanks you guy, will look into it again 👍

Update here?

@AllenFang
Getting this error while clicking export csv button.
button.js:33 Uncaught TypeError: onExport is not a function
at onClick (button.js:33)
Can you please suggest the solution for the same ? Thanks in advance.


Release notes popup

Is your feature request related to a problem? Please describe.
When a new version of the application is released, it is important to notify the user about the update. Currently, this process requires the user to manually check for updates, which can be inconvenient and may result in users not being aware of important changes or bug fixes. To address this issue, I propose implementing a release notification popup that compares the current version of the application with the version returned from the API.
Describe the solution you'd like

Upon launching the application, the system will compare the current version of the app with the version returned from the API.
If the versions differ, a release note modal will be displayed to notify the user about the new update. The release notes should highlight the changes, bug fixes, and any new features introduced in the latest version.
The release notification popup will include two options for the user: "Skip" and "Update".

If the user chooses "Skip," the popup will be closed, and they can continue using the app without updating.
If the user selects "Update," they will be redirected to the respective app store (e.g., Apple App Store or Google Play Store) to download and install the latest version of the application.

Additionally, a checkbox should be provided within the release notification popup, allowing the user to choose whether they want to skip future notifications until the next release. This option can help avoid repetitive popups for minor updates and bug fixes.
In cases where the API includes a "forceUpdate" flag, the release notification popup should only display the "Update" button. This flag indicates that the current version of the app is no longer supported, and the user must update to the latest version to continue using the application.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.


online documentation missing many config options for default modules

trying to help user format calendar output,
dateEndFormat is not listed anymore
showEnd.
etc

I see "dateEndFormat" on https://docs.magicmirror.builders/modules/calendar.html#configuration-options

your browser seems to be buggy, sam...

no.. it WAS NOT there... and then u pushed a new doc update and poof it was back ..

:-) glad to hear, so closing it now :-)


PCL Profile 259, Version=v4.5

Hello,
I 've tried to install the current version of the ZXing.Net.Mobile Package to my PCL but I got the error message: "Could not install package 'ZXing.Net.Mobile <IP_ADDRESS>'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile259', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."
My PCL Project targets the PCL Version 259 and Version 4.5 and as I saw the ZXing.Net.Mobile.Core projects targets it too.
So what might can I do?

I have the same problem..

So the problem is, ZXing.Net.Mobile doesn't actually support 259 as there's not implementation for every platform in that profile (Windows Phone 8.1 native is not supported, however Windows Phone 8.1 Silverlight is).
I guess I could just ship the Core dll for the platforms that aren't supported, however I'm not exactly sure what that would help achieve (you'd end up getting a reference to the reference PCL for ZXing.Net.Mobile which is just a bunch of stubs that throw exceptions).
I welcome more discussion on this, but for now I see no reason why artificially supporting 259 is a good idea...

So what I did, because at the moment I only use it for WP81 Silverlight, is to pull it from the repo compile the core, portable and WP8 project and added it manually to the Core and WP81 project of my concrete app.
That worked for me!

Same problem here. I would love to use this component. I added the DLL to the IOs Project as a Reference. The app compiles and displays the overlay page, but crashes when I add this line to AppDelegate.cs. global::ZXing.Net.Mobile.Forms.iOS.Platform.Init ();  I have not tested Android or Windows Phone 8.1 Silverlight.

I finally got this working in my Xamarin.Forms PCL 259 app by doing the following: I added package <IP_ADDRESS> to my Portable app, using Nuget. I then manually referenced the only DLL (ZXing.Net.Mobile.dll) in the ZXIng.Net.Mobile.Forms/Lib/Portable- directory. I then manually referenced the other 2 DLLs (ZXing.Net.Mobile.Core.dll and zxing.portable.dll)) in the ZXIng.Net.Mobile/Lib/Portable- directory. I then added package <IP_ADDRESS> as a Component in my IOs app and it worked. I can't get it to work in my Android app right now due to the Xamarin.Forms 2.2 issues and the Android support libraries, but hopefully Zing.Net.Mobile.Forms will be updated soon.

This should be fixed in master now and will be released soon.


dtype check for numeric types not working

dtype check for int and float types doesn't always catch bad values

issue fixed using numpy dtypes (np.int, np.float, etc.)


add method keepAlive && set minimal php version to 7.4 #4

Hi
I've set the php minimal version to 7.4 #4 so rewriting some methods & properties signature to be compatible.
But I can change to Php 8.3 if you prefer ;-) I don't mind.
And added the keepAlive() method to Ssh & Sftp.
I hope it suits you :-)

@Cyrille37 Thanks for the PR. I will take a look and let you know.

Hi @sandeshjangam
Do not hesitate to make some changes on this PR, maintainers are allowed to edit. :smile:


Stackchain/Update Alonzo auxiliary data

Please check in src/crypto/shelley/transactions.test.js whether witnesses.scripts() needs to be changed to witnesses..native_scripts().


Add Code of Conduct file

All open-source projects have code of conduct file. Can I make this file ?

Make sure you make all pr on the develop branch 👍🏻

Can you add label of NWoC?


🚀 - Allow both comma and period to insert decimalSeparator even when thousandSeparator is set to one of them.

Which package(s) are relevant/related to the feature request?
@maskito/kit
Description
Right now when I don't explicitly set a thousandSeparator (which is never entered manually (?), only shown when appropriate), I can use comma and and period to insert the decimalSeparator, no matter what it is set to.
However as soon as I set the thousandSeparator to e.g. ., I can only use , to enter the decimalSeparator.
We're running in environments where we cannot influence the keyboard layout(s) of the user, but each application user (on the same machine) can have different locale settings. Thus numpad . will always deliver a . or a ,, but the applicaiton must understand that no matter the application setting.
If this is not scope of maskito, any pointers on how to work around this would be appreciated.

This is a bit sketchy — the argument of thousand separator never being entered manually is an assumption. I can envision some old lady entering sum exactly as it is shown on her documents to pay utilities bill or something like that. I don't think we should change the current behavior. Currently we support a set of decimal separators to be treated equally when entered and it works unless it matches the thousand separator. I can only advice to use a different thousand separator. Not using dots or commas to group digits like that has been an official recommendation of International Bureau of Weights and Measures for over 70 years now, as well by ISO and many other international groups concerned with formatting. So my advice would be to just use spaces as a delimiter if you want to support multiple locales, as it is both internationally recognized format and a sane common ground for people from all over the world.

@nsbarsukov would you have an advice regarding some pre/post processor that people can employ if they still want to do this?

Thanks for your thorough thoughts - makes sense to me :D We will discuss this internally, but I'm unsure whether we can get rid of the requirement - so advice would still be greatly appreciated :)

@mduft Sorry for late response!
The only advise I can give you – use preprocessor / postprocessor and put all your complex logic inside it.
https://maskito.dev/core-concepts/processors
You can explore the following preprocessor and create something similar to it:
https://github.com/taiga-family/maskito/blob/ec8628467814cff7dfae22668370236f402d8146/projects/kit/src/lib/masks/number/processors/pseudo-character-preprocessor.ts#L5-L10


Is speech_recognition being kept up to date?

It seems many of the recognize_* methods have not kept up with the time. In particular:

recognize_bing: Connects to the old Bing speech API which has been phased out by NRC. There does not seem to be a recognize_azure() method to connect to the new Azure speech-to-text api.

recognize_ibm: Seems to also connect to a cloud service that IBM has discontinued in favour of Watson. And there does not seem to be a recognize_watson() method

This repo hasn't seen an update in 2 years, there are 202 open issues and 23 waiting pull requests.  I don't think it's maintained anymore.

On this case it can be community maintained in @abandonware org
https://rzr.github.io/rzr-presentations/docs/abandonware
Let's wait feedback from upstream if the idea is good, I'll share instructions on how to transfer repo.
Relate-to: https://github.com/abandonware/abandonware.github.io/issues/5


Make XY Grid cell block containers responsive as well

Fixes responsiveness of frame cell block containers

Excellent thanks! 👍


Windows: HMR doesn't work for a fresh Next.js project

Description
Creating a fresh Next.js with PandaCSS:

I receive a warning on compilation. It may be Windows only. There is a separate issue: #1783.
Styles don't recompile. So I have to reboot the dev server every time I change styles.

Link to Reproduction
Windows only?
Steps to reproduce

Install via https://panda-css.com/docs/installation/nextjs
pnpm dev
Go to localhost:3000
Receive the following warning:

> next dev

   ▲ Next.js 14.0.4
   - Local:        http://localhost:3000

 ✓ Ready in 4.2s
 ○ Compiling / ...
🐼 info [hrtime] Extracted in (8.99ms)
 ⚠ ./app/globals.css.webpack[javascript/auto]!=!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[2]!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[3]!./app/globals.css
Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
Invalid dependencies may lead to broken watching and caching.
As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
Globs: They are not supported. Pass absolute path to the directory as context dependencies.
The following invalid values have been reported:
 * "C:/Users/boris/Projects/panda-nextjs/app"
 * "C:/Users/boris/Projects/panda-nextjs/node_modules/.pnpm/@pandacss+dev@0.23.0_typescript<EMAIL_ADDRESS> * "C:/Users/boris/Projects/panda-nextjs/pages"
 * and more ...

Import trace for requested module:
./app/globals.css.webpack[javascript/auto]!=!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[2]!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[3]!./app/globals.css
./app/globals.css
 ⚠ ./app/globals.css.webpack[javascript/auto]!=!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[2]!./node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[11].oneOf[12].use[3]!./app/globals.css
Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
Invalid dependencies may lead to broken watching and caching.
As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
Globs: They are not supported. Pass absolute path to the directory as context dependencies.
The following invalid values have been reported:
 * "C:/Users/boris/Projects/panda-nextjs/app"
 * "C:/Users/boris/Projects/panda-nextjs/node_modules/.pnpm/@pandacss+dev@0.23.0_typescript<EMAIL_ADDRESS> * "C:/Users/boris/Projects/panda-nextjs/pages"
 * and more ...

Also, go to page.tsx:

import { css } from '@/styled-system/css'

export default function Home() {
  return (
    <main className={css({bg: 'red'})}>Hello</main>
  )
}

Change red to green.
Panda still bundles the old color red. Since green wasn't bundled, the background is now white.
To make it work, I have to pnpm dev again.

JS Framework
React (TS)
Panda CSS Version
0.23.0
Browser
N/A
Operating System

[ ] macOS
[X] Windows
[ ] Linux

Additional Information
No response

this looks specific to webpack (css-loader) on windows only.
I would love to help but without a way to minimal repro I can't do much
just to make sure this isnt a postcss issue, does the same thing also happen when using a file generated from the CLI ?
what about removing the @layer with https://www.npmjs.com/package/@csstools/postcss-cascade-layers ? maybe css-loader doesn't handle those ?

Assuming that "a file" is a styled-system/styles.css, I don't have it. It is not being generated. I followed this guide. Maybe there's some configuration option to enable?
Regarding @layer, I will update the comment as soon as I reproduce it.

Assuming that "a file" is a styled-system/styles.css, I don't have it

it is ! it's generated when running the pnpm panda or pnpm panda cssgen command

@layer: adding @csstools/postcss-cascade-layers had no effect. I also removed the .next folder and run panda codegen --clean.
styles.css: It works! I run it in a watch mode and everything's fine. No warnings.

got it, so this would be a postcss issue, that helps a lot tracking the root cause 🙏

@astahmer
I've also encountered this issue today after doing some dependency updates on my project. I've just run a bisect and from what I can see:

0.19.0 has no warnings in the terminal like in the OP.
0.21.0 has the warnings but still generates the global/reset/static files.
0.22.0 has the warnings and does not generate any of the files. Interestingly, using cssgen -w doesn't work for me.

Also running Next 14.0.4. My repo is private but happy to try and produce an MRE if needed.

I tried something to fix it here but honestly I'm blindly trying as I don't have a windows machine, it would be very helpful to have someone with one that can investigate, it's most likely somewhere near that line

For now, the error is the same. What I've done:

Cloned the repo, right after your commit
pnpm install
Went to sandbox/next-js-app
Run pnpm prepare, pnpm dev

If I had to do something else, could you please clarify? Meanwhile, I'll try to investigate the code itself.
PS S:\Projects\panda\sandbox\next-js-app> pnpm dev

><EMAIL_ADDRESS>dev S:\Projects\panda\sandbox\next-js-app
> rimraf .next && next dev

   ▲ Next.js 14.0.3
   - Local:        http://localhost:3000

 ✓ Ready in 3.6s
 ○ Compiling / ...
🐼 info [hrtime] Extracted in (13.30ms)
 ⚠ ./src/app/globals.css.webpack[javascript/auto]!=!../../node_modules/.pnpm/next@14.0.3_@babel+core@7.12.9_react-dom<EMAIL_ADDRESS>x.js??ruleSet[1].rules[12].oneOf[12].use[2]!../../node_modules/.pnpm/next@14.0.3_@babel+core@7.12.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[12].oneOf[12].use[3]!./src/app/globals.css
Invalid dependencies have been reported by plugins or loaders for this module. All reported dependencies need to be absolute paths.
Invalid dependencies may lead to broken watching and caching.
As best effort we try to convert all invalid values to absolute paths and converting globs into context dependencies, but this is deprecated behavior.
Loaders: Pass absolute paths to this.addDependency (existing files), this.addMissingDependency (not existing files), and this.addContextDependency (directories).
Plugins: Pass absolute paths to fileDependencies (existing files), missingDependencies (not existing files), and contextDependencies (directories).
Globs: They are not supported. Pass absolute path to the directory as context dependencies.
The following invalid values have been reported:
 * "S:/Projects/panda/sandbox/next-js-app/pages"
 * "S:/Projects/panda/sandbox/next-js-app/panda.config.ts"
 * "S:/Projects/panda/sandbox/next-js-app/src"

Import trace for requested module:
./src/app/globals.css.webpack[javascript/auto]!=!../../node_modules/.pnpm/next@14.0.3_@babel+core@7.12.9_react-dom<EMAIL_ADDRESS>s??ruleSet[1].rules[12].oneOf[12].use[2]!../../node_modules/.pnpm/next@14.0.3_@babel+core@7.12.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[12].oneOf[12].use[3]!./src/app/globals.css
./src/app/globals.css

Experiencing same issue on Windows with 14.0.4 nextjs. Was driving me mad, so finding this thread was a relief.
Downgraded pandacss version to 0.19.0 "solved" it for now

@chrber04, you can make it work on the latest version by running panda --watch in parallel with next dev:
{ // package.json scripts
  "dev": "concurrently \"next dev\" \"panda --watch\"",
}

You need to clean the PostCSS config:
const postcssConfig = {
  plugins: {},
}

module.exports = postcssConfig

Also, modify your globals.css:
@import '../panda/system/styles.css'; // double-check the path, it depends on your configuration

@chrber04, you can make it work on the latest version by running panda --watch in parallel with next dev:
{ // package.json scripts
  "dev": "concurrently \"next dev\" \"panda --watch\"",
}

You need to clean the PostCSS config:
const postcssConfig = {
  plugins: {},
}

module.exports = postcssConfig

Also, modify your globals.css:
@import '../panda/system/styles.css'; /* double-check the path, it depends on your configuration */

Thank you so much, that did the job for me! And bonus points it seems to compile way faster now, which might just be the newer version but thanks all the same.

sorry I should have made that clearer, this issue is specific to the @pandacss/postcss plugin so the CLI will always work just fine

And bonus points it seems to compile way faster now,

yes ! the CLI will always be better performance-wise than the postcss plugin (because we don't control precisely how many times the postcss plugin will be called, it mostly depends on the host bundler (astro/vite/next etc))

Is there any downside of not using the PostCSS plugin? Because if the CLI is faster and has the same behavior as with the plugin, I would choose the CLI.

not really, the only downside is that you lose the convenience of only running 1 process (your dev command) and instead having to run dev + pnpm panda -w

@chrber04, you can make it work on the latest version by running panda --watch in parallel with next dev:
{ // package.json scripts
  "dev": "concurrently \"next dev\" \"panda --watch\"",
}

You need to clean the PostCSS config:
const postcssConfig = {
  plugins: {},
}

module.exports = postcssConfig

Also, modify your globals.css:
@import '../panda/system/styles.css'; /* double-check the path, it depends on your configuration */

Thank you so much, that did the job for me! And bonus points it seems to compile way faster now, which might just be the newer version but thanks all the same.

Thanks for this. Seems I was setting up wrong and this does indeed work.
Added tip for anyone who takes this route and is unfamiliar with concurrently, you can pass names to the commands to clean up your terminal as such: "concurrently -n NextJS,Panda \"next dev\" \"panda --watch\""

not really, the only downside is that you lose the convenience of only running 1 process (your dev command) and instead having to run dev + pnpm panda -w

I would really love to get back on doing this 😅

as mentioned previously, doing this will at least get the 2 processes running with 1 single command:
{ // package.json scripts
  "dev": "concurrently \"next dev\" \"panda --watch\"",
}

Im actually using nx, Im using Mac and my partner uses Windows.
Up until HMR stopped working in dev.. everything was great.
here is a partial project.json of nx:
// This used to work well.
 "panda": {
      "command": "panda codegen --cwd apps/teachers-index",
      "defaultConfiguration": "production",
      "configurations": {
        "development": {},
        "test": {},
        "production": {}
      }
    },
    "dev": {
      "dependsOn": ["panda"],
      "executor": "@nx/next:server",
      "defaultConfiguration": "development",
      "configurations": {
        "development": {
          "buildTarget": "teachers-index:build:development",
          "dev": true,
          "port": 7778
        }
      }
    },

If you have ideas on how to make it easily work well on windows Im all ears

Im using nx as well and concurently works fine with it, just update your scripts in package.json like you would normally do, nx does catch on this and allow you to run them.
You can also do this in project.json if you use this, or nx.json if you have one global config.
Hope it helps.

I'll be sure to check again thank you :)

I'm running into this issue on Windows as well and did a bit of digging through the various layers of webpack to see if I could find the root cause. It looks like it's right here in NormalModule.js where it's using a regex that doesn't allow for forward slashes in absolute paths even though they're valid in Windows.
From testing by hand-altering the files in my local node_modules a simple change to testing with isAbsolute from the node:path module would do the trick. However, there's a comment from Tobias on a similar issue that makes me think a PR wouldn't be easily accepted. 😅

OK, I did some more digging, it looks like we can prevent this issue by making a couple of alterations in @pandacss/node. The gist of the changes is that we want to change out usages of pathe for node:path.
It seems counterintuitive because pathe is supposed to make things normalized for Windows, but from the webpack perspective it's creating "invalid" absolute paths. Since both backslash and forward slash work work as path separators on windows it's safe to use the webpack-friendly backslash version.
I've made the changes in my local node_modules directly and things are working properly. I'll get started on a proper PR here in a bit.

Still not working

Still not working

There was some miscommunication on the merge/release handoff. It should be relatively easy to resolve.

This was fixed?

Yes @juliomuhlbauer


current master does not compile

cd $GOPATH/src
git clone https://github.com/ReSTARTR/ec2-ls-hosts.git
cd ec2-ls-hosts/
[shine@home ec2-ls-hosts (master)]$ go get -v
ec2-ls-hosts
# ec2-ls-hosts
./main.go:63: opt.Profile undefined (type *client.Options has no field or method Profile)
./main.go:96: opt.Profile undefined (type *client.Options has no field or method Profile)
./main.go:97: opt.Profile undefined (type *client.Options has no field or method Profile)

sorry, my bad.


Create signal list custom element

As a user I want to be able to add signal liste tables to the templates to allow displaying signal lists in my generated documentations.

[ ] possibility to add signal liste tables to templates
[ ] template including signal list will be used by automated documentations


Update devtest-lab-vm-powershell.md

Added information to add new data disk.

@RogerBestMsft : Thanks for your contribution! The author, @spelluru, has been notified to review your proposed change.

@RogerBestMsft - Thank you. #sign-off
If you change "azure-docs" in the URL to "azure-docs-pr" when you make the changes, you can submit a PR against the private repo. Then, you get additional benefits like Acrolynx reporting on spelling, grammar, style, etc. You also get a staging link where you can verify how the changes look on staging.
For more information, see https://review.docs.microsoft.com/en-us/help/contribute/contribute-get-started-git-github-fundamentals?branch=master.

hi @RogerBestMsft - merging this.
As @spelluru mentioned... Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.


Templates of egress-auth and ingress-auth are out-of-date

It seems not right that egress-auth.yaml and ingress-auth were updated 2 months ago while egress.yaml was updated 9 days ago. Since we changed the way feeding config, egress-auth doesn't work right now.

@lookuptable @andraxylia

https://github.com/istio/istio/pull/504

The templates are working right now. But we may still need to keep an eye on it when we change template. Lucky we will have e2e tests covering this issue really soon.


Create Mailing List

Im thinking to import the forum emails as mailing list and use MailChimp:
https://mailchimp.com/pricing/entrepreneur/

Afterwards we can shut down the forum...

What do you want to do exactly with a mailing list?

Notify people of major updates and generally let them know what's going on and what is planned.


Update @nknize's maintainer affiliation

Description
Update @nknize's maintainer affiliation
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@nknize has been added as maintainer now.


It's an interesting project. Could you provide some examples to use it?

I'm doing something like this in an embedded environment.It's a great idea to realize a react-os.
I really want to know that react-os how to work. Would you please provide one or some examples to show how to use it?

@taoyuan Yeah, It looks promising, but I see no active development from last 2 years !

@agupta1989 This is really regrettable. Maybe the author has lost interest on it.
Do you know that there are other similar projects?

@taoyuan well, if you want to develop desktop based applications using JS stack, electron is way to go, I have not idea about any other react based library.

Hi guys
Glad to see you're interested in this project.
Im very sory but i dont have so mutch time to work on it.
@agupta1989 the idea is to make web applications that looks like operating systems inside the browser.

@uditalias ah.. got it. so you mean webtops ;) just like what qooxdoo or Sencha's ExtJS is capable of !


Decline by default per application form

Context
Currently we do decline by default per application choice.
But there can be multiple choices per application form that expire at exactly the same time (they always do, since the decline_by_default_at for all offered choices is set when the last offer comes in). This means candidates would get multiple emails at the same time if we added email notifications.
Changes proposed in this pull request
This aggregates the application forms that need to be declined by default, which means we can start sending a single email. Rewrites the worker spec to be more system-like.
Guidance to review
Link to Trello card
Prerequisite for https://trello.com/c/DtPNK4vW
Things to check

[X] This code doesn't rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] New environment variables have been added to the Azure config

As discussed IRL, this part of the commit message would benefit from some additional explanation: ...there can be multiple choices per application form that expire at exactly the same time (they always do).

Minor feedback, otherwise LGTM 👍

@malcolmbaig updated PR / commit message!

I did wonder whether there were edge cases, e.g. when an offer is withdrawn, in which you could end up with different DBD dates on application choices for the same form but looking at the code that doesn't seem to be possible. (the service that sets the DBD operates on a form).

Indeed, it shouldn't be the case. We should think about moving the dbd date to the form, to avoid uncertainty.


python docker support

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
does this api and oauth work with python docker image?  I've deployed docker image with credential.json but when container executes the python code, it prompts to go authorize:
Please visit this URL to authorize this application: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=.....

Hi @exptaelee,
It is possible to use this library inside of a docker image. Regardless of what environment you are in, you will need to have valid credentials to use APIs.
For applications, it is generally recommended you use a service account instead, but some APIs that require access to user data do not support this.
Here is some more reading:

Using OAuth 2.0 for Web Server Applications
OAuth 2.0 for Service Accounts

@busunkim96 I am trying to get googlesheet data.  Does it also require service account?

You will need to use user credentials. Please reference the instructions at https://developers.google.com/identity/protocols/OAuth2WebServer. Thanks!

@busunkim96 I am trying to get googlesheet data. Does it also require service account?

did you figure out bro? Having same kind of requirement!


Examples panic when Nvidia driver is enabled

On Ubuntu 20.10 the examples panics with error:
thread 'main' panicked at 'Instance creation error: VkError(ERROR_LAYER_NOT_PRESENT)', examples/src/lib.rs:237:18

Backtrace:

```
🔋100% ✗ RUST_BACKTRACE=full cargo run --bin triangle
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
     Running `/home/rik/graphics/ash/target/debug/triangle`
thread 'main' panicked at 'Instance creation error: VkError(ERROR_LAYER_NOT_PRESENT)', examples/src/lib.rs:237:18
stack backtrace:
   0:     0x563708687bd0 - std::backtrace_rs::backtrace::libunwind::trace::h72c2fb8038f1bbee
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/libunwind.rs:96
   1:     0x563708687bd0 - std::backtrace_rs::backtrace::trace_unsynchronized::h1e3b084883f1e78c
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/mod.rs:66
   2:     0x563708687bd0 - std::sys_common::backtrace::_print_fmt::h3bf6a7ebf7f0394a
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:79
   3:     0x563708687bd0 - ::fmt::h2e8cb764b7fe02e7
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:58
   4:     0x5637086a812c - core::fmt::write::h7a1184eaee6a8644
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/fmt/mod.rs:1080
   5:     0x563708684b92 - std::io::Write::write_fmt::haeeb374d93a67eac
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/io/mod.rs:1516
   6:     0x563708689f5d - std::sys_common::backtrace::_print::h1d14a7f6ad632dc8
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:61
   7:     0x563708689f5d - std::sys_common::backtrace::print::h301abac8bb2e3e81
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:48
   8:     0x563708689f5d - std::panicking::default_hook::{{closure}}::hde0cb80358a6920a
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:208
   9:     0x563708689c08 - std::panicking::default_hook::h9b1a691049a0ec8f
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:227
  10:     0x56370868a641 - std::panicking::rust_panic_with_hook::h2bdec87b60580584
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:577
  11:     0x56370868a1e9 - std::panicking::begin_panic_handler::{{closure}}::h101ca09d9df5db47
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:484
  12:     0x56370868803c - std::sys_common::backtrace::__rust_end_short_backtrace::h3bb85654c20113ca
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:153
  13:     0x56370868a1a9 - rust_begin_unwind
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
  14:     0x5637086a6a01 - core::panicking::panic_fmt::h48c31e1e3d550146
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85
  15:     0x5637086a6823 - core::option::expect_none_failed::h6154dc750ae47ade
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/option.rs:1234
  16:     0x56370836f030 - core::result::Result::expect::he0952449e7c9e040
                               at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:933
  17:     0x5637083714ef - examples::ExampleBase::new::h1c81b39b07150899
                               at /home/rik/graphics/ash/examples/src/lib.rs:235
  18:     0x563708364835 - triangle::main::he0555801ca357519
                               at /home/rik/graphics/ash/examples/src/bin/triangle.rs:18
  19:     0x563708367c5b - core::ops::function::FnOnce::call_once::h4e175047d62338fd
                               at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227
  20:     0x56370836473e - std::sys_common::backtrace::__rust_begin_short_backtrace::h37bf97adc06a26dd
                               at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137
  21:     0x563708352631 - std::rt::lang_start::{{closure}}::h05da0d84ff6009df
                               at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:66
  22:     0x56370868aa67 - core::ops::function::impls:: for &F>::call_once::he179d32a5d10d957
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:259
  23:     0x56370868aa67 - std::panicking::try::do_call::hcb3d5e7be089b2b4
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381
  24:     0x56370868aa67 - std::panicking::try::h7ac93b0cd56fb701
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345
  25:     0x56370868aa67 - std::panic::catch_unwind::h7b40e396c93a4fcd
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382
  26:     0x56370868aa67 - std::rt::lang_start_internal::h142b9cc66267fea1
                               at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:51
  27:     0x563708352607 - std::rt::lang_start::hb0217ad538c3dd9c
                               at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:65
  28:     0x56370836721a - main
  29:     0x7fb018161cb2 - __libc_start_main
  30:     0x5637083490ce - _start
  31:                0x0 -
```

nvidia-smi:

Tue Dec 15 09:18:43 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.38       Driver Version: 455.38       CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce GTX 1060    Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   57C    P0    28W /  N/A |    609MiB /  6078MiB |      2%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1811      G   /usr/lib/xorg/Xorg                367MiB |
|    0   N/A  N/A      1997      G   /usr/bin/gnome-shell              103MiB |
|    0   N/A  N/A      2278      G   ...AAAAAAAAA= --shared-files        2MiB |
|    0   N/A  N/A     15782      G   ...AAAAAAAA== --shared-files      131MiB |
+-----------------------------------------------------------------------------+

vkcube works.
Let me know if more info is needed.

Looks like the example enables the VK_LAYER_KHRONOS_validation layer.
Do you have it installed ? If not you can get it from here https://vulkan.lunarg.com/sdk/home.

@filnet Thanks, that helps but after seeing the image for a moment, the program panics:

```
NFO:
GENERAL [Loader Message (0)] : Inserted device layer VK_LAYER_KHRONOS_validation (libVkLayer_khronos_validation.so)
INFO:
GENERAL [Loader Message (0)] : Failed to find vkGetDeviceProcAddr in layer libVkLayer_MESA_device_select.so
thread 'main' panicked at 'attempted to leave type platform::platform::x11::util::input::PointerState uninitialized, which is invalid', /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:658:9
stack backtrace:
0:     0x55e6dcf83bd0 - std::backtrace_rs::backtrace::libunwind::trace::h72c2fb8038f1bbee
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/libunwind.rs:96
1:     0x55e6dcf83bd0 - std::backtrace_rs::backtrace::trace_unsynchronized::h1e3b084883f1e78c
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/mod.rs:66
2:     0x55e6dcf83bd0 - std::sys_common::backtrace::_print_fmt::h3bf6a7ebf7f0394a
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:79
3:     0x55e6dcf83bd0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h2e8cb764b7fe02e7
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:58
4:     0x55e6dcfa412c - core::fmt::write::h7a1184eaee6a8644
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/fmt/mod.rs:1080
5:     0x55e6dcf80b92 - std::io::Write::write_fmt::haeeb374d93a67eac
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/io/mod.rs:1516
6:     0x55e6dcf85f5d - std::sys_common::backtrace::_print::h1d14a7f6ad632dc8
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:61
7:     0x55e6dcf85f5d - std::sys_common::backtrace::print::h301abac8bb2e3e81
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:48
8:     0x55e6dcf85f5d - std::panicking::default_hook::{{closure}}::hde0cb80358a6920a
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:208
9:     0x55e6dcf85c08 - std::panicking::default_hook::h9b1a691049a0ec8f
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:227
10:     0x55e6dcf86641 - std::panicking::rust_panic_with_hook::h2bdec87b60580584
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:577
11:     0x55e6dcf861e9 - std::panicking::begin_panic_handler::{{closure}}::h101ca09d9df5db47
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:484
12:     0x55e6dcf8403c - std::sys_common::backtrace::__rust_end_short_backtrace::h3bb85654c20113ca
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:153
13:     0x55e6dcf861a9 - rust_begin_unwind
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
14:     0x55e6dcfa2a01 - core::panicking::panic_fmt::h48c31e1e3d550146
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85
15:     0x55e6dcfa294d - core::panicking::panic::h184ede6dd822ffb4
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:50
16:     0x55e6dcd09b51 - core::mem::uninitialized::h9340e45ded11ff6c
at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:658
17:     0x55e6dcd09b51 - winit::platform::platform::x11::util::input::::query_pointer::hfa5d92a86f942bcc
at /home/rik/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.19.5/src/platform/linux/x11/util/input.rs:94
18:     0x55e6dcc5bbcd - winit::platform::platform::x11::EventsLoop::process_event::hc59f59a33a9c3e62
at /home/rik/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.19.5/src/platform/linux/x11/mod.rs:956
19:     0x55e6dcc55aaa - winit::platform::platform::x11::EventsLoop::run_forever::h3b30def978495801
at /home/rik/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.19.5/src/platform/linux/x11/mod.rs:297
20:     0x55e6dcc4d07d - winit::platform::platform::EventsLoop::run_forever::hd8d2a58eba91fd2e
at /home/rik/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.19.5/src/platform/linux/mod.rs:531
21:     0x55e6dcc4a563 - winit::EventsLoop::run_forever::h2be558bae2d8c1c6
at /home/rik/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.19.5/src/lib.rs:292
22:     0x55e6dcc53bcc - examples::ExampleBase::render_loop::hfc2ad9605f380ef0
at /home/rik/graphics/ash/examples/src/lib.rs:177
23:     0x55e6dcc62c4b - triangle::main::he0555801ca357519
at /home/rik/graphics/ash/examples/src/bin/triangle.rs:361
24:     0x55e6dcc63c5b - core::ops::function::FnOnce::call_once::h4e175047d62338fd
at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227
25:     0x55e6dcc6073e - std::sys_common::backtrace::__rust_begin_short_backtrace::h37bf97adc06a26dd
at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137
26:     0x55e6dcc4e631 - std::rt::lang_start::{{closure}}::h05da0d84ff6009df
at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:66
27:     0x55e6dcf86a67 - core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once::he179d32a5d10d957
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:259
28:     0x55e6dcf86a67 - std::panicking::try::do_call::hcb3d5e7be089b2b4
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381
29:     0x55e6dcf86a67 - std::panicking::try::h7ac93b0cd56fb701
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345
30:     0x55e6dcf86a67 - std::panic::catch_unwind::h7b40e396c93a4fcd
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382
31:     0x55e6dcf86a67 - std::rt::lang_start_internal::h142b9cc66267fea1
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:51
32:     0x55e6dcc4e607 - std::rt::lang_start::hb0217ad538c3dd9c
at /home/rik/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:65
33:     0x55e6dcc6321a - main
34:     0x7f3560415cb2 - __libc_start_main
35:     0x55e6dcc450ce - _start
36:                0x0 -
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x170000000017, type = VK_OBJECT_TYPE_DEVICE_MEMORY; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkDeviceMemory 0x170000000017[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x190000000019, type = VK_OBJECT_TYPE_DEVICE_MEMORY; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkDeviceMemory 0x190000000019[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x160000000016, type = VK_OBJECT_TYPE_BUFFER; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkBuffer 0x160000000016[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x180000000018, type = VK_OBJECT_TYPE_BUFFER; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkBuffer 0x180000000018[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x1a000000001a, type = VK_OBJECT_TYPE_SHADER_MODULE; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkShaderModule 0x1a000000001a[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x1b000000001b, type = VK_OBJECT_TYPE_SHADER_MODULE; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkShaderModule 0x1b000000001b[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x1c000000001c, type = VK_OBJECT_TYPE_PIPELINE_LAYOUT; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkPipelineLayout 0x1c000000001c[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x120000000012, type = VK_OBJECT_TYPE_RENDER_PASS; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkRenderPass 0x120000000012[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x1d000000001d, type = VK_OBJECT_TYPE_PIPELINE; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkPipeline 0x1d000000001d[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x150000000015, type = VK_OBJECT_TYPE_FRAMEBUFFER; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkFramebuffer 0x150000000015[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x140000000014, type = VK_OBJECT_TYPE_FRAMEBUFFER; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkFramebuffer 0x140000000014[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
ERROR:
VALIDATION [VUID-vkDestroyDevice-device-00378<PHONE_NUMBER>)] : Validation Error: [ VUID-vkDestroyDevice-device-00378 ] Object 0: handle = 0x55e6dee11698, type = VK_OBJECT_TYPE_DEVICE; Object 1: handle = 0x130000000013, type = VK_OBJECT_TYPE_FRAMEBUFFER; | MessageID = 0x71500fba | OBJ ERROR : For VkDevice 0x55e6dee11698[], VkFramebuffer 0x130000000013[] has not been destroyed. The Vulkan spec states: All child objects created on device must have been destroyed prior to destroying device (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-vkDestroyDevice-device-00378)
</details>

The texture example works without problems.

Looks like a winit issue.

We probably just have to update winit, I recently ran into the same error in ggez.

Yes this is a Rust 1.48 and winit issue, can confirm updating winit fixes it in other projects.
Downgrading Rust to < 1.48 is another option if you just want to get it to run and play around with it for now.
texture shouldn't work without problems though, that sounds weird, it should crash as soon as you move your cursor over it as well.

I can confirm that it works with updating winit. I have tried to make PR but I don't get the example code in a proper shape because the semantics of the winit's event loop run is changed. It now wants to own all the code which in the current structure makes it impossible to run the code which does the cleanup. That said as a Rust beginner :smile:

I can confirm that too. Examples updating winit to 0.24.0 and fixing winit namespacing references in lib.rs went just easy.
But renaming
pub events_loop: RefCell<winit::EventsLoop>,
to
pub events_loop: RefCell<winit::event_loop::EventLoop>,
leads inevitably to the folling error:
`error[E0107]: wrong number of type arguments: expected 1, found 0
--> examples\src\lib.rs:152:30
|
152 |     pub events_loop: RefCellwinit::event_loop::EventLoop,         // NEW ! pub events_loop: RefCellwinit::EventsLoop,
|                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected 1 type argument
error: aborting due to previous error; 1 warning emitted`

@majkcramer EventLoop supports custom (user) events, the type of which is passed as generic argument to EventLoop. Since these examples don't use/need that, use a void (()) type here.
I've performed the full conversion of both the examples and ash-window example here:
https://github.com/Traverse-Research/ash/compare/examples-winit-24
I'll submit a PR for this after resolving cleanup. The new event loop fn run never returns (-> !) and has all Vulkan resources moved into it. You'll see a linter warning complaining about device_wait_idle (and consequent _destroy calls not being reachable.

We probably just have to update winit, I recently ran into the same error in ggez.

Just as an FYI, I've already updated winit and rewritten the triangle example so it works with the new event loop as part of #190, just have to do the texture now

We probably just have to update winit, I recently ran into the same error in ggez.

Just as an FYI, I've already updated winit and rewritten the triangle example so it works with the new event loop as part of #190, just have to do the texture now

@hgallagher1993 Do you think you can update and submit that soon or should I submit aforementioned branch as interim solution till then? That's probably going to generate a bunch of conflicts on your side though.

@hgallagher1993 Do you think you can update and submit that soon or should I submit aforementioned branch as interim solution till then? That's probably going to generate a bunch of conflicts on your side though.

@MarijnS95 shouldn't be too long before I have a merge request, couple of days at most :+1:

@MarijnS95 shouldn't be too long before I have a merge request, couple of days at most :+1:


Update Add-SPSolution.md

Add SharePoint Server 2010 as supported.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Add-SPSolution.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Create some plugins

Some ideas for plugins that have been requested:

[ ] #506
[ ] stock management (WIP)
[ ] #505
[ ] #504

We should think about a better place to keep track of plugin ideas and plugins.

We are tracking plugin requests with the "plugin" label now, so this issue is obsolete.


30 numeric patterns added

Fixes: #555 #556 #557 #558 #559 #560 #561 #562 #563 #564 #565 #566 #567 #568 #569 #570 #571 #572 #573 #574 #575 #598 #599 #600 #601 #603 #604 #605 #606 #607

@aryashah2k Numeric Pattern 247 and 248 are same. Please clarify, I will change the code accordingly.

@aryashah2k Numeric Pattern 247 and 248 are same. Please clarify, I will change the code accordingly.

Thanks for bringing this to my notice, please change the pattern 248 to the one shown below.
I will update the image in the backend.

@aryashah2k Numeric Pattern 247 and 248 are same. Please clarify, I will change the code accordingly.

Thanks for bringing this to my notice, please change the pattern 248 to the one shown below. I will update the image in the backend.

This is already there, numeric pattern 249 (there's just slight difference in alignment of 8, I guess it is some error). Please check!

Yes, for now no changes required, will identify and rectify the pattern error and make changes accordingly. Nothing to be done from your side, your PR will get the appropriate tag counting both pattern s so no worries!


Add Fastball locations for Glitch and Relic

Adds panel and BT locations for Glitch and Relic. Together with #70 and #76 all non-livefire maps should have panel locations and BT spawns now.
Locations where decided on together with @theroylee

Panel locations on Glitch

Panel locations on Relic

I also did some playtesting yesterday with these locations hosting a public server.
The general feedback/result was:

B on Glitch being too open
-> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/
A on Relic being too easy to trap
-> No one mentioned it specifically but I found it rather easy to trap A with e-smoke, so we might reposition A later on if that becomes a major issue.

Otherwise there were no major complaints ^^

One idea that we had for B on Glitch was to put it on the support beam that sits high above the bridge, but unfortunately, that area is out of bounds. If every server had out of bounds that area might work.

B on Glitch being too open
-> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/

What about doing something like this with spawning some entities to stand on under the bridge

B on Glitch being too open
-> Not solvable sadly. To keep the symmetry in Glitch there's only one spot we can put B that isn't out of bounds :/

What about doing something like this with spawning some entities to stand on under the bridge

Wouldn't that force all players to have to download a mod for this map? I think the idea is to have any server be able to host the mode without any mod changes.

Wouldn't that force all players to have to download a mod for this map? I think the idea is to have any server be able to host the mode without any mod changes.

no. since this is getting pulled to the actual mods folder, players will already have the mod needed to do this

I'd keep the current PR regarding B as is atm to keep things clean and get all maps functional on Fastball ASAP. But we should definitely do a second PR updating the position and adding the entities as shown in the image.

Ok, I'll open a new PR when this is merged ^^


fix: Too long identifier name error

what
Fix too long identifier name without cluster recreation:
set id_length_limit = 40 for
module "aurora" {
  source  = "cloudposse/rds-cluster/aws"
  version = "1.10.0"
  ...
  id_length_limit = 40
}

will cause such recreation if final module.this.id will be between 40-60 characters
why
https://github.com/cloudposse/terraform-aws-rds-cluster/releases/tag/1.10.0 introduced random_pet, which adds 2 extra words on the top of module.this.id, and that exceed limit of 63 allowed characters for RDS names
╷
│ Error: creating RDS Cluster (company-staging-aurora-payments-ledger-service-aliases) Instance (company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1): operation error RDS: CreateDBInstance, https response error StatusCode: 400, RequestID: 1979b42f-b1df-4e00-b0ec-d3b629b3002d, api error InvalidParameterValue: Invalid database identifier:  company-staging-aurora-payments-ledger-service-aliases-promoted-piglet-1
│
│   with module.aurora_aliases.aws_rds_cluster_instance.default[0],
│   on .terraform/modules/aurora_aliases/main.tf line 261, in resource "aws_rds_cluster_instance" "default":
│  261: resource "aws_rds_cluster_instance" "default" {

This PR limit final identifier to 62-63 chars (depends on count of replica)
references
Fixing https://github.com/cloudposse/terraform-aws-rds-cluster/pull/213

@MaxymVlasov we still want to retain that random_pet because when we create_before_destroy we need to have unique names for the new instances.

@kevcube
TL;DR: id_length_limit in cloudposse/label/null calculate md5() of full_id, crop full_id and attach md5 at the end.
So you still have unique id based on pet_random, but which not violate AWS limitation
https://github.com/cloudposse/terraform-null-label/blob/5c464f42c388deb18222c2285c9e450b1fc233c7/main.tf#L161-L166

/terratest

/terratest

@kevcube tests passed

@kevcube tests passed

ok - one thing I'm wondering is how we release this, it feels like a fix, but also this will cause consumer's db instances to be recycled so maybe I release as a minor. Going to ask for backup.

It will affect only DBs with a random_pet.id length == 61 (>=62 will see the same error as in PR description)
I don't know, how many DBs have exactly this number, so yeah, second eyes could be helpful

Although I cannot merge because I was the last pusher and also only approver 🤡 whoops!

/terratest


Eloquent Model fill updated_at field only if any other field changes

Hi,
I didn't find a way to update timestamp field updated_at during Eloquent Model upsert ONLY IF a row has a field changed.
Laravel Models change the updated_at field if isDirty() = true.
You write into documentation that updated_at is added to Eloquent Models and it's true, but it always added and updated even also no field changes.
Do you have suggestions?
Thanks so much!

Hi @BusinessClick,
I've looked into this in the past but haven't found a good solution. If you are using MySQL/MariaDB, you could probably build something like this: https://stackoverflow.com/a/16588699/4848587

Thanks!


docs(vehicle_info): add docs for versioning

Description

update vehicle info docs based on https://github.com/orgs/autowarefoundation/discussions/4050
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mitsudome-r @xmfcx
If this looks good for you, I'll merge it.

@xmfcx
I'll merge this. If you have any concerns, let me know :pray:


Error: self signed certificate in certificate chain

Issue Type: Bug
When trying to "add account" getting error: 'Error: self signed certificate in certificate chain'. Issue is same with both Installer and zip file. Got admin permissions on the machine... and tried running the ".exe" as admin... no luck
Azure Data Studio version: azuredatastudio 1.3.8 (84009f65ec6297d1cc16b1b2ec8f6fba9f5be2a1, 2019-01-08T23:59:38.228Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz (4 x 2904)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.88GB (21.35GB free)

Process Argv
C:\Purna\Tools\azuredatastudio-windows\azuredatastudio.exe

Screen Reader
no

VM
0%

Extensions: none

Note that setting NODE_EXTRA_CA_CERTS to the location of a file containing your local CA certificate is probably preferable to setting NODE_TLS_REJECT_UNAUTHORIZED=0.

Closing as an upstream issue in Node.JS.  Please us the workaround list above to work around this issue.  Thanks for reporting!


Difficulty writing custom extension with preview window

I'm trying to port the last of my custom fzf.vim stuff over to fzf-lua and couldn't get preview windows to work. I read through #57 and am not sure what I'm missing, wondering if this might be a rarely hit bug or if I'm doing something wrong.
I'm trying to create a provider that will use xurls to pick out all the URLs in a file, load them into fzf, and let me pick ones to open. Everything works except for the preview window:
function openURLs(selected)
  local argstring = ''
  for k,v in ipairs(selected) do
    argstring = argstring .. ' ' .. v
  end
  os.execute("firefox --new-tab" .. argstring)
end

function getURLs()
  require('fzf-lua').grep({
    -- previewer = false,
    raw_cmd = 'xurls ' .. vim.api.nvim_buf_get_name('%'),
    search = ' ',
    search_header = "put header here later",
    preview = "echo {}",
    prompt = 'URLs in file ❯ ',
    actions = {
      ["default"] = openURLs,
    },
  })
end

Ideally I'd like to replace that preview config with something that will show the part of the buffer where the URL appears. The issue I'm having is that the preview option seems to be getting set in FZF in a way that FZF doesn't expect, or maybe is escaped. The error I get when running the above code is this:
[Fzf-lua] fzf error 2: unknown option: {}
Is this expected, and I'm just using the option wrong? I tried setting fzf_opts[--preview] as well and that didn't seem to be used at all. Also may not be ideal that I'm trying to piggyback on the grep function, but I'm not sure what the "right" way to do it is short of duplicating all the window settings and what not that fzf-luasets up and calling the nvim-fzf API directly

Apologies for commenting on a closed issue: I am trying to replicate a similar example as the above using the builtin preview as per examples in the wiki; however, when I try to populate the preview MyPreviewer:populate_preview_buf with entries as above, I get an exception in
function MyPreviewer:populate_preview_buf(entry_str)
  vim.api.nvim_buf_set_lines(self.preview_bufnr, 0, -1, false, {
  ...

that self.preview_bufnr is nil: I tried to replicate it with a clean configuration but I still get the same error.

This is an old issue, the code has been updated since, you need to use set_preview_buf, for example, see the implementation of `man_pages’:
https://github.com/ibhagwan/fzf-lua/blob/455744b9b2d2cce50350647253a69c7bed86b25f/lua/fzf-lua/previewer/builtin.lua#L889-L900

Great, it works fine by adding set_preview_buf, thank you! However I have noticed that the previewer disappears while scrolling through the entries and needs to be explicitly invoked back (say via F4): is this maybe related to actions.resume in some way or should it work fine (and maybe I am making a mistake somewhere)?

Great, it works fine by adding set_preview_buf, thank you! However I have noticed that the previewer disappears while scrolling through the entries and needs to be explicitly invoked back (say via F4): is this maybe related to actions.resume in some way or should it work fine (and maybe I am making a mistake somewhere)?

I don’t see how resume is related, you mean it disappears when you scroll entries or when you try to scroll the preview window? Neither should happen, link or post your code and I’ll take a look, the easiest way is just to copy the man_pages preview code (or any other previewer) and adjust it to your needs.

I am using the same code from the wiki, namely
local builtin = require("fzf-lua.previewer.builtin")
local MyPreviewer = builtin.base:extend()

function MyPreviewer:new(o, opts, fzf_win)
	MyPreviewer.super.new(self, o, opts, fzf_win)
	setmetatable(self, MyPreviewer)
	return self
end

function MyPreviewer:populate_preview_buf(entry_str)
	local tmpbuf = self:get_tmp_buffer()
	vim.api.nvim_buf_set_lines(tmpbuf, 0, -1, false, {
		string.format("SELECTED FILE: %s", entry_str),
	})
	self:set_preview_buf(tmpbuf)
	self.win:update_scrollbar()
end

-- Disable line numbering and word wrap
function MyPreviewer:gen_winopts()
	local new_winopts = {
		wrap = false,
		number = false,
	}
	return vim.tbl_extend("force", self.winopts, new_winopts)
end

(plus the addition of set_preview_buf as suggested).  I see the behaviour shown in the screenshot below
https://user-images.githubusercontent.com/15387611/211368167-ff54c0f0-870f-4f29-aad5-20641132c75f.mov
P. S. If you prefer I can open a new issue to avoid polluting this one (unless it's trivial).

@gennaro-tedesco, this might be related to #604, seems I introduced a bug with this commit: https://github.com/ibhagwan/fzf-lua/commit/2ef7fe0d00234e1744010d9c1afe1c4492a242af

@gennaro-tedesco, can you try with the latest commit (https://github.com/ibhagwan/fzf-lua/commit/e337b533c32fbc2533309bb94ee146b98da271fe), if it still doesn't work open a new issue and we'll handle it there.

I'm again referring to this issue as all-things-inbuilt-previewer :). I want to pass an external option to
function MyPreviewer:populate_preview_buf(entry_str)

(think of it as a user configuration) but I don't understand where in the constructor such option must be initialised (I presume this is more or a lua object oriented question than plugin specific). I have tried defining the class method as
function MyPreviewer:populate_preview_buf(entry_str, config)

and then invoking it as
fzf.files({
    ...
    previewer = session_previewer(user_config),
    ...

but  this gives an exception of win option being nil. I suppose one may also pass the external parameters as option to the fzf picker altogether, but I haven't found a way :/.

You can pass the user config as any other fzf-lua option and then access the the options under self.opts, for example if you run fzf_lua.files({ cwd = … }), you can find the value with self.opts.cwd.


Add basic release automation

This release flow aims for the following features:

npm version && npm publish works locally
Action dispatch runs the same scripts as the local workflow
Automatic build and changelog generation
Github release support

@voxpelli if you want to factor something like this into the re-uesable workflow, let me know, or give me an idea how you want it done and I can do that.

I need to fix the lifecycle hooks on this before tests pass.

Ok fixed up those tests.


remove ci trigger for main and release branches [buildNum:2<IP_ADDRESS>]

Motivation behind this:
Whenever we release a new addon we first start by running bump-version.yml, which bumps the package_version.txt by a commit to main / release branch from imodeljs-admin. This causes two pipeline runs to trigger, one as a result of the trigger which I am removing in this PR and one triggered by the bump-verson.yml pipeline.
The pipeline run as a result of the trigger is useless and wastes build time.
We could potentially special case the scenario where we're releasing a new addon and only skip the trigger for that scenario(when imodeljs-admin pushes to the branch, Scenario A), but I don't see a benefit in the other scenario that this pipeline would trigger and thats when a PR merges to main/release branch (Scenario B). I could see value in running CI/ the trigger in scenario B if we didn't already have the github policy to require that our PRs were up to date with main. @aruniverse could you confirm this policy is in place for the imodel-native repo?
The value that it would bring without the github policy is that it would confirm that whatever is in main + the PR that merged runs nicely together(no errors). With the github policy PRs are always running with whatever is already in main so it adds no value.
Please correct me if I am wrong regarding scenarios A / B or if there is some other valuable reason to have these triggers.

Is this pr still needed?

I would assume we're still wasting build time on a merge to main with this. But, looking at the imodel-native-internal pipeline, it deosn't seem to have an issue.

I took a look at imodel-native
And it does seem pointless to have some of these pipelines run 'Individual CI for main'
I also wonder if even imodeljs-admin's commit causing a pipeline run is not that useful. It doesn't seem to be a release build, do we need to run non release builds off of main when with Dan's changes we're guaranteed to run a release build for every change into main?


Added a skip statement for an invalid test for the template manager

A stub of a test with incomplete implementation was being run again. A skip statement was added to it to prevent testing until properly implemented

It's a code failure, not a test failure. I can't replicate locally and I've got latest.


Some icons are broken on iPadOS

Maybe these are cached from before some fontawesome update? Don't know though.

Yes, seems to be the cache, the Version tag should probably be appended to the font url. I'd still like to not serve the whole fa bundle in the future.

play/pause also seems to be broken at least partly (reproduce with „play“, „skip“, „skip“ on not yet started stream)

I just tried this again. Seems like this is fixed again. :tada:

This was a caching issue after updating fontawesome.


droid_backends

import torch
import torch.nn.functional as F
import droid_backends
anyone know what is the droid_backends?

It's from the setup.py file: https://github.com/youmi-zym/GO-SLAM/blob/e954a850bf52aced47bb40d7637e840edf0a73ce/setup.py#L8
the setup.py file creates a setuptools.Extension for the c++ and CUDA files in the 'src/lib' subdirectory: https://github.com/youmi-zym/GO-SLAM/tree/e954a850bf52aced47bb40d7637e840edf0a73ce/src/lib
Read more here: https://pytorch.org/docs/stable/cpp_extension.html#torch.utils.cpp_extension.CUDAExtension

It's from the setup.py file:
https://github.com/youmi-zym/GO-SLAM/blob/e954a850bf52aced47bb40d7637e840edf0a73ce/setup.py#L7-L31
the setup.py file creates a setuptools.Extension for the c++ and CUDA files in the 'src/lib' subdirectory: https://github.com/youmi-zym/GO-SLAM/tree/e954a850bf52aced47bb40d7637e840edf0a73ce/src/lib
Read more here: https://pytorch.org/docs/stable/cpp_extension.html#torch.utils.cpp_extension.CUDAExtension
thank you !!!!!!!!!!!!!!!!!!!


Timestampable onFlush should skip any objects not in MANAGED state

If you update and delete an entity that has a timestamp field to be changed on update, the onFlush listener will try to set the changed timestamp and recalculate a change set but due ot the object being scheduled for deletion it is no longer managed and the UOW will throw an exception.
This is easily fixed by checking if the object state is managed before doing any changes.

its related to recent change in Timestampable listener :(

yes probably will need to revert it back :(

prolly yes :+1:


integrate plugin with markdown preview

I'm not sure how to ask this. It seems that the latest vscode version supports this integration:
https://code.visualstudio.com/updates/v1_15#_support-for-markdown-preview-plugins
In those release notes another mermaid plugin is showing this integration.
Would it make sense to add this integration here also?
Thanks!

definitely, this is a must! I was short on time for this one... :)