Add parser for user updates and add lock to RoomUsers

I basically took these changes from the unity parsers and applied them to the flash parsers as I needed them

im a little confused as for why the callbacks are done in a new thread

ok i see, I'm not sure how i looked over that in the unity parser PR, but there should be no threading in the parsers at all

I played a bit with the parsers in the past few days and I think I now understand Firstly, it should be said that without multithreading, the game sometimes hangs a bit while functions are still running. This is not particularly bad, but it is noticeable. In addition, if you process the packets asynchronously, that threading can be kind of useful here. Don't nail me down on these statements though, am not very experienced and these are just my guesses based on my observations.why there is concurrency being used here!

Firstly, it should be said that without multithreading, the game sometimes hangs a bit while functions are still running. This is not particularly bad, but it is noticeable. In addition, if you process the packets asynchronously, that threading can be kind of useful here. Don't nail me down on these statements though, am not very experienced and these are just my guesses based on my observations.

Creating a thread is way more resource heavy than  just parsing it and calling listeners, so no, that is incorrect.
However, if the user who uses gpython decide to do something resource heavy, then yes. But then its not the job of the framework to create a thread for them, they should do it themself. Embedding the threading is not a good design pattern

Firstly, it should be said that without multithreading, the game sometimes hangs a bit while functions are still running. This is not particularly bad, but it is noticeable. In addition, if you process the packets asynchronously, that threading can be kind of useful here. Don't nail me down on these statements though, am not very experienced and these are just my guesses based on my observations.

Creating a thread is way more resource heavy than just parsing it and calling listeners, so no, that is incorrect.
However, if the user who uses gpython decide to do something resource heavy, then yes. But then its not the job of the framework to create a thread for them, they should do it themself. Embedding the threading is not a good design pattern

That's right, as I said I have less experience myself and am happy to have learned something :D I have now removed the multithreading. Only to remove callback I still have a question: How would you solve this? Because after the del statement the object is deleted and so the HEntity object should not be available in the callback anymore. Unfortunately I have no idea how to solve it.

Firstly, it should be said that without multithreading, the game sometimes hangs a bit while functions are still running. This is not particularly bad, but it is noticeable. In addition, if you process the packets asynchronously, that threading can be kind of useful here. Don't nail me down on these statements though, am not very experienced and these are just my guesses based on my observations.

Creating a thread is way more resource heavy than just parsing it and calling listeners, so no, that is incorrect.
However, if the user who uses gpython decide to do something resource heavy, then yes. But then its not the job of the framework to create a thread for them, they should do it themself. Embedding the threading is not a good design pattern

That's right, as I said I have less experience myself and am happy to have learned something :D I have now removed the multithreading. Only to remove callback I still have a question: How would you solve this? Because after the del statement the object is deleted and so the HEntity object should not be available in the callback anymore. Unfortunately I have no idea how to solve it.

the object is not deleted, only its reference in the dictionary is deleted. We can store the object in a local variable, then delete it from the dictionary, and then do the callback

Should be fixed now


Add -d, --dir option to install to / instead of

Similar to ruby-install's -r, --rubies-dir flag.

So this enables for example:
$ ruby-build truffleruby+graalvm-24.1.0 -d ~/.rubies
...
==> Installed truffleruby+graalvm-24.1.0 to /home/eregon/.rubies/truffleruby+graalvm-24.1.0

Which I find quite convenient compared to having to copy-paste the definition names after the rubies directory.

BTW, what do you think about this potential feature being lumped in with all the others, while we're going in this direction:
ruby-build truffleruby+graalvm -d ~/.rubies
#=> (installs the latest "truffleruby+graalvm" version)

BTW, what do you think about this potential feature being lumped in with all the others, while we're going in this direction:

It seems nice to have but that feels out of scope and I don't really have time to look into that. I don't really need it either.
There is also the question for CRuby if e.g. 3.3 should work, etc.

Thank you!


Fix CouplingMap test

Summary
test_coupling_map_options was failing because of different order of the couples in the list.
Converted the lists to sets for the comparison.
Details and comments
See also #877

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 72.581%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/options/options.py
1
98.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
2573

Relevant Lines:
3545

💛  - Coveralls


decode: Fix compiler issue with gcc-5

gcc 5.0 and 5.1 appear to take issue with this line and generates the
following error:
/home/nitro/tmp/nanopb/pb_decode.c: In function ‘pb_decode_noinit’:
/home/nitro/tmp/nanopb/pb_decode.c:889:60: error: conversion to ‘uint8_t {aka unsigned char}’ from ‘int’ may alter its value [-Werror=conversion]
fields_seen[iter.required_field_index >> 3] |= (uint8_t)(1 << (iter.required_field_index & 7));
^

This seems like a compiler bug, but this workaround is harmless.

Ha, diggin' out the good stuff? :)

@kylemanna Yeah, not brave enough to pick the more invasive changes right before 0.3.4 release, but this seemed safe enough :)


Future of the framework, contributions, evangelism

@kamilmysliwiec
First of all I'd like to say I really like the idea and your work so far, secondly: what are you plans for the future of the project? Here are some questions I'd love to hear your answers to.

Do you plan to move it to it's own GitHub organization (eg. nest/nest)?
Do you intend to create a website (GitHub Pages?)?
How do you want to approach contributions?
Is there any roadmap?
Are you going to make some future milestones that community could help you achieve?
What are your plans for making the framework more popular (and thus attract more contributors)?

Thanks for the answers.

Hi @galkowskit,
Many thanks! :)

It sounds ridiculous, but Nest was born by accident. Some months ago I decided to create architecture for my node.js projects. It has been becoming larger and larger and here it is. This is why I put it on my github profile. I didn't think about own organization profile yet. Maybe in the future?
I want to create simple landing page with logo and reference urls (github + documentation), probably nothing more.
I believe that they are people, which loves challanges and new technologies, just like me. If anyone want to help - I will much appreciate it :)
4 & 5. The bigger part of my ideas is already implemented in Nest (there is still some things to do of course). Now, I am interested what people want to, so I am waiting on new "issues" to help them.
I know that it can be really hard to make framework more popular. I don't have well-known organizations as a partners and I don't know famous people ;) I think that the best way to make Nest more attractive is just to write articles about 'How to [...] with Nest'. Those tutorials are the best method to show people how easy is to achieve some things with this framework.

Thanks for good questions :)

At first I was gonna say :+1: for some kind of trampoline page, but then again the current GitBook page serves the purpose nicely in my opinion. The only problem I had was that it was quite difficult finding this repository - or I just failed :disappointed: Had to assume it was hosted at GitHub under your username.
It could be useful if the main landing page contained a link to this repository - or lacking that - the GitBook main page (whose repository I couldn't find). Also, the npm package could also use a link to this repository, since it currently appears to have no homepage/repository defined.
I'm sorry if this doesn't add much to the current issue, but since my problem was brushed here, I thought I could comment.

@kamilmysliwiec - The server side JS ecosystem is a bit of a mess at the moment. The IBM thing and lack of forward momentum in Express has ( imo ) done irreparable there, HapiJS is great but for those that prefer code over convention, it's obviously not a popular choice & and the rest of the offerings are what they are.
You have taken a very unique approach with Nest that has a ton of potential as it matures but to do that, you are going to need help as maintaining something popular is like a second job.
If I may offer a suggestion for I know that it can be really hard to make framework more popular
Twitter & Medium would be two places to start, the buzz around Nest has already started in with the Angular folks.
As to how to do that, I'd suggest finishing out your Twitter profile and creating one for Nest ( and then using it ). I'd also suggest getting this into a GitHub Org as well. You already have a solid framework, right now what you need is docs + a bunch of people to help evangelize.
Also, though he is a super busy guy / dad / dev you may be able to sneak a bit of time with @TheLarkInn to discuss this topic. He has taken Webpack popularity / acceptance to a whole new level, I can't think of anyone better suited to ask for advice.

Totally agree, I've shared this with a bunch of angular folks and they've been very impressed.
I think an organisation would be a great idea, similar to angular's, so could have packages on npm
@nest/nest,
@nest/cli,
@nest/testing (don't know if that's entirely included in what you've done already)
with public GitHub projects for each.
I'd love to help with providing some example stuff as soon as I can for how this can be used to host an angular application, and connect to a mysql database for api routes.

@Mark-McCracken I agree, it might help in adoption as well to have an organisation name, because people will feel less like it's a "small project" (even though it might be currently). I'd love to see examples where you connect to a database, maybe even some kind of ORM (like Laravel has Eloquent).

I've managed to connect to database and get results back, need to fix some stuff around async not waiting for my results, but should be easy. Need to work out how to serve angular application on home route, but hopefully won't be hard. Only had a few hours to play with this last night, but will try to take a look next week and get an example up somewhere

I have already done an example of how to implement a chat room with Nest and Angular. Feel free to modify it as you see fit. (missing DB part)
https://github.com/Pinedo11/nestDemo-ChatClient
https://github.com/Pinedo11/nestDemo-ChatServer

Funny thing is that i had same idea, but i was not that determined, so development was slow and it was just prototype which i would in some point rewrite into well documented project. But you made a release and destroyed my dreams. Just kidding :D. I am happy to see that javascript ecosystem won't be mess anymore. I will try contribute with code, ideas and issues. Good Job.
Few ideas:

Add TypeORM
Make angular like cli tool

I believe TypeORM or Mongoose would be great addiditions. Especially if
nicely integrated.
pt., 5 maj 2017, 12:08 użytkownik Jan Lipničan<EMAIL_ADDRESS>napisał:

Funny thing is that i had same idea, but i was not that determined, so
development was slow and it was just prototype which i would in some point
rewrite into well documented project. But you made a release and destroyed
my dreams. Just kidding :D. I am happy to see that javascript ecosystem
won't be mess anymore. I will try contribute with code, ideas and issues.
Good Job.
Few ideas:

Add TypeORM https://github.com/typeorm/typeorm
Make angular like cli tool

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kamilmysliwiec/nest/issues/6#issuecomment-299428786,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCjUFAb9Hwkm4jMvEtzNSidD3A8qOZGks5r2vUygaJpZM4M1pL0
.

Locking people into a specific orm or database is a mistake, you limit your target audience.

I agree with both of the above comments.
Don't think it should lock people in to a specific ORM/database,
but being able to have an add-on package that makes this easy could be really useful and make this even more attractive

I agree with points made by @galkowskit (+1 on TypeORM), @d3viant0ne and @Mark-McCracken.
 But many other popular frameworks have a "preferred" ORM that is integrated out of the box or with a simple add-on: ASP.NET and Entity Framework, Laravel and Eloquent, Django ORM, Sails and Waterline... It makes things easier and will allow Nest to have starter templates with user auth built in, as well as allow for add-ons to be created with a standardized backend API - one big attraction of Laravel is their Official Packages such as Cashier, Envoy, Passport, Scout and Socialite and this is dependent on a standardized ORM.
In my opinion, having a standardized ORM (i.e. through 'starter templates' or otherwise) has more benefits and will open more doors to easily integrated add-ons in vein of those listed above.

Hi guys!
About integration with databases - I agree with @d3viant0ne - we should not locking people into specific solutions. On the other hand - it would be very helpful to show how to work with Nest and well-known databases, both SQL & NoSQL, and orm tools - just like typeorm. Standarized starters and best practices overviews have a lot of benefits and should makes easier to get into Nest.
Secondly, the organization profile - it is necessary and in the next few days nest will be probably moved into separated @nest profile. Maybe something like @nest prefix for packages might be useful.

Sounds good to me.
One great thing about Ionic's cli is that you can initialize projects by passing it a git repo. I think this would be an excellent idea to leverage and would allow us the ability to have starters, including one with TypeORM and the like.

Hi guys!
I finished small landing page today. What do you think? ;)
http://nestjs.com/

Looks great! A small note, the credits are barely visible on MAC with low background lit.

Love it!
Wondering if perhaps there should be a gitter.im or slack chat room for this project? might be a good place to help people or converse ideas for the framework.

100%!
I vote slack. There's a free tier right?

Slack is free with the limitation that it only saves a set amount of history.
If you are going to use Slack, use it as an invite only place to coordinate between developers as the ecosystem.
For support, my suggestion is a combination of Gitter & Stack Overflow.

Landing page is good, but the image on the right is cropped at the bottom.
For communication I'd suggest Gitter and Stack Overflow.

slack

@kamilmysliwiec here it goes my 2 cents :)
About evangelising I could help by creating a course on egghead.io, something like "Create a RESTful API in TypeScript with Nest" (any better idea?). That should give it a great boost.
Although, by that time I think some prerequisites must be accomplish. My suggestions, mostly discussed on this issue:

Find collaborators: After a point, is impossible just by one person to maintain a project. Find some first-line collaborators and coordinating with contributors is a must.
Make a transparent contribution workflow: Everyone can contribute, that's by definition, but organising all the information helps a lot. Some ideas: create labels for better issue classification, make a transparent roadmap, create a Github template for issues...
Move it to it's own Github org
Define minimum stuff to get done: Moving to @nest/... scoped packages, adding auth... Whatever you consider it must be done before starting evangelising, better get it done, otherwise it would cause confusion because of out-of-date articles, videos and so on.
Add a chat room, either Slack or Gitter: They'll avoid too poluted issues with discussions.

Not sure if I forgot anything. It could feel kind of a hassle, but it's true that when a project gets popular one spends more time just coordinating than coding 😄  (unless someone coordinates for you).
Hope this helps, tell us what do you think and what do you have in mind.

Hi @alexjoverm,
If you have some time, feel free to create a course. It would be a pleasure and really nice feeling for me, to take a look on it :1st_place_medal:

Find collaborators: You - guys - are awesome. There is a lot of people here, which incredible helps me with examples, suggestions, issues, CLI, so I think that there is nothing to look for. The team is formed itself and I am very happy with it :smiley_cat:
Make a transparent contribution workflow - must have.
Move it to it's own Github org - repository will be moved this week :smile:
Define minimum stuff to get done - today, maybe tomorrow the plan should be published
Add a chat room - maybe both Slack and Gitter?

Many thanks!

@kamilmysliwiec good to hear! Thanks for the answers
About the course, I'm currently working on one, but after that I'd be happy to do it :)
About the collaborators: Keep in mind is not the same contributors than collaborators:

Contributor: anyone who helps
Collaborator: someone that you explicitly add to the project, so they have repo access for assigning labels, merging PR, etc. So kind of "part of core team"

Probably you don't need collaborators, just keep it in mind in case you cannot manage everything :)

@alexjoverm, awesome! Can't wait :smiley:
Yep, I know the difference. Sure, not all of them could be a part of collaborators team, but I also know that additional hands to help will be needed :) Time will tell how it looks

Add a chat room - maybe both Slack and Gitter?

Gitter is a better tool for support as Google can index it's archives for web searches and it won't truncate your history.
Slack is a better tool from a usability standpoint and the fact that most of us are already in multiple slack channels already ( one less window to have open ).

Personally I think using both would send a confusing message to consumers. A lesson learned in Webpack, it's hard to change the support rules down the road. So while this level of specificity probably seems like overkill now, it's preferable to trying to apply the same down the road.

Hi guys! Do you have any ideas about the name of the package? I decided to move nest to scoped npm packages with @nestjs prefix, but now it is necessary to choose the name of the framework package. @nestjs/framework seems too long, but I don't have better idea.

@nestjs/core?
Also I'd move the testing tools under @nestjs/test

Hmm.. @nestjs/core, @nestjs/common, @nestjs/websockets, @nestjs/test, @nestjs/microservices?

Sorry, the words prefixed with @ were hidden :D

@galkowskit, @nest is not available. Also the website domain is nestjs, because nest is already used. Same here - organization profile is nestjs - same reason.

Since ~2.0.0 nest is split into several packages - @nestjs/core, @nestjs/common, @nestjs/microservices, @nestjs/testing, @nestjs/websockets. There is also CQRS module available @nestjs/cqrs.

Wow! Amazing work!!!! And great news the CQRS surprise!

@kamilmysliwiec a side question, have you considered getting some reward for all this work? You could open an OpenCollective campaign, I'm sure there would be proud backers/sponsors over the time :)

Also another good idea is to put the example into another repo. Right now it just bloats up the main repo, making it more difficult to work with.

@kamilmysliwiec well done, nest is amazing.

Hi guys! I added Gitter chat if anyone is interested :smiley_cat:

Hey, I also think this framework has a huge potential. Great work!
One small thing I'd like to say is that there should be more possiblities to support this project. Because I don't have a credit card 😉.

Thanks @ndabAP!

Hi!
It was a long road.. :smile: But I think it's the best time - nest repository is finally moved into the organization :tada: :tada: :tada:  @alexjoverm @d3viant0ne @everyone

@kamilmysliwiec is there a way we can be collaborators? can you make a video with a walkthrough of the code or a live stream on youtube where you explain all the code? It's quite difficult to follow the code without comments and I, for one, would love to contribute as much as possible but I don't have lots of time so a fast walkthrough on the architecture would be really nice so we can jump right in the code and help with further development. Am I asking a lot or would this be possible?
Great project btw! Made me switch instantly when I saw it! Keep up the good work!

@alexjoverm Any updates on the egghead course? I came from loopback looking for a better way to write my apis. I noticed that you mentioned about a course and I would be glad to pay for that.

Hey @vvdwivedi. We are investigating this topic. Hopefully, we will be able to publish something more soon :)


restful_server example not working (IDFGH-12175)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I am trying to run the restful server example to test the webserver using framework such as vue.js.
https://github.com/espressif/esp-idf/tree/master/examples/protocols/http_server/restful_server
I have configured Deploy mode to SPI flash and have followed the instructions to see how to build the firmware:

When trying to install npm packages, I am getting ton of different warnings:
PS C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo> npm install
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This module is no longer supported.
npm WARN deprecated<EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email
at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use
@babel/plugin-transform-async-generator-functions instead.
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>3.x is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Moved to 'npm install @sideway/address'
npm WARN deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>Switch to 'npm install joi'
npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated<EMAIL_ADDRESS>Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 1493 packages, and audited 1494 packages in 1m

123 packages are looking for funding
  run `npm fund` for details

82 vulnerabilities (1 low, 53 moderate, 23 high, 5 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
PS C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo>

Regardless of all the issues above, I have tried to run command npm run build but it does not seem to go through properly:
PS C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo> npm run build

><EMAIL_ADDRESS>build
> vue-cli-service build

-  Building for production...

 ERROR  Failed to compile with 2 errors                                                                                08:09:36

 error

js/app.37936d16.js from Terser
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\terser-webpack-plugin\dist\index.js:217:37
    at Array.forEach (<anonymous>)
    at TerserPlugin.optimizeFn (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\terser-webpack-plugin\dist\index.js:160:259)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:7:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1409:36
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1405:32
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at Compilation.seal (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1342:27)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compiler.js:675:18
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1261:4
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:24:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at Compilation.finish (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1253:28)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compiler.js:672:17
    at _done (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:9:1)
    at eval (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:32:22)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1185:12
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1097:9
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

 error

js/chunk-vendors.8bbb8f88.js from Terser
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\terser-webpack-plugin\dist\index.js:217:37
    at Array.forEach (<anonymous>)
    at TerserPlugin.optimizeFn (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\terser-webpack-plugin\dist\index.js:160:259)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:7:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1409:36
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1405:32
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at Compilation.seal (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1342:27)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compiler.js:675:18
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1261:4
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:24:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\Hook.js:154:20)
    at Compilation.finish (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1253:28)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compiler.js:672:17
    at _done (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:9:1)
    at eval (eval at create (C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:32:22)
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1185:12
    at C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo\node_modules\webpack\lib\Compilation.js:1097:9
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

 ERROR  Build failed with errors.
PS C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo>

After that, I have tried tu run npm audit and npm audit --force to see if it makes any difference but I still cannot seem to get it built. I would highly appreciate any help on how to get this setup and running.
Additionally, I am quite curious if running webserver using frameworks such as vue.js only possible in Station mode such as in this example? Is there any particular reason why this example does not showcase using webserver in AP mode?
For my particular application, I mostly interested in running a webserver in AP mode where the client connects to the device and connects to the webserver via the <IP_ADDRESS> or mdns. I am a little concerned if this kind of funcionality relies on having interent connection (STA mode) to download the required files and etc.

I had the same problem, apparently is something about the dependence version. I fixed like that:

I used Node Js v20.11.1 NodeJs and I changed
pacakge.json the scrip field from:

"scripts": {
    "serve": "vue-cli-service"
    "build": "vue-cli-service"
    "lint":  "vue-cli-service"
},

To:
scripts": {
    "serve": "set NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve",
    "build": "set NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service build",
    "lint": "set NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service lint"
},

Then I runner the command as readme said:

cd path_to_this_example/front/web-demo
npm install
npm run build

it install the dependence but still some errors. I didn’t fix it with audit fix or --force, just I leaved them  because in other way it don’t build.
https://stackoverflow.com/questions/69665222/node-js-17-0-1-gatsby-error-digital-envelope-routinesunsupported-err-os

Hello @krupis
Please refer to the following comment and check if it helps.
https://github.com/espressif/esp-idf/issues/10344#issuecomment-1347782776

Hello @krupis Please refer to the following comment and check if it helps. #10344 (comment)

I have installed node version 10.19.0 as suggested using the nvm with following command:
C:\Users\my_user>nvm install 10.19.0
Downloading node.js version 10.19.0 (64-bit)...
Complete
Creating C:\Users\my_user\AppData\Roaming\nvm\temp

Downloading npm version 6.13.4... Complete
Installing npm v6.13.4...

Installation complete. If you want to use this version, type

nvm use 10.19.0

Then I did:
nvm use 10.19.0 to ensure the correct node version is being used to compile the files.
I have tried to run npm run build again and it worked:
PS C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo> npm run build

><EMAIL_ADDRESS>build C:\Users\my_user\esp5\esp-idf\examples\protocols\http_server\restful_server\front\web-demo
> vue-cli-service build

|  Building for production...

 WARNING  Compiled with 3 warnings                                                                                11:32:18 AM

 warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  js/chunk-vendors.d1061d71.js (271 KiB)

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (430 KiB)
      css/chunk-vendors.f77e647c.css
      js/chunk-vendors.d1061d71.js
      js/app.1b14630b.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  File                                   Size              Gzipped

  dist\js\chunk-vendors.d1061d71.js      271.28 KiB        85.83 KiB
  dist\js\app.1b14630b.js                7.04 KiB          2.66 KiB
  dist\css\chunk-vendors.f77e647c.css    151.68 KiB        19.56 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

Thank you very much for help! Additionally, I have a few questions:

Why the web files need to be compiled? Is there any advantage?
I have previously tried to embed the index.html, styles.css and scripts.js files as following:

extern const char index_start[] asm("_binary_index_html_start");
extern const char index_end[] asm("_binary_index_html_end");
extern const char styles_start[] asm("_binary_styles_css_start");
extern const char styles_end[] asm("_binary_styles_css_end");
extern const char scripts_start[] asm("_binary_scripts_js_start");
extern const char scripts_end[] asm("_binary_scripts_js_end");

static esp_err_t web_root_hdlr(httpd_req_t* req) {
    const uint32_t len = index_end - index_start;
    TraceInf("ROOT");
    httpd_resp_set_type(req, TYPE_TXT_HTML);
    httpd_resp_send(req, index_start, len);
    return ESP_OK;
}

static esp_err_t web_styles_hdlr(httpd_req_t* req) {
    const uint32_t len = styles_end - styles_start;
    TraceInf("STYLES");
    httpd_resp_set_type(req, TYPE_TXT_CSS);
    httpd_resp_send(req, styles_start, len);
    return ESP_OK;
}

static esp_err_t web_scripts_hdlr(httpd_req_t* req) {
    const uint32_t len = scripts_end - scripts_start;
    TraceInf("SCRIPTS");
    httpd_resp_set_type(req, TYPE_TXT_JSCRIPT);
    httpd_resp_send(req, scripts_start, len);
    return ESP_OK;
}

static const httpd_uri_t web_handlers[] = {
    {.uri = "/",                .method = HTTP_GET,  .handler = web_root_hdlr,             .user_ctx = &web_context},
    { .uri = "/styles.css",             .method = HTTP_GET,  .handler = web_styles_hdlr,           .user_ctx = &web_context},
    { .uri = "/scripts.js",             .method = HTTP_GET,  .handler = web_scripts_hdlr,          .user_ctx = &web_context},
    };

static void web_register_handlers(httpd_handle_t server) {
    uint8_t cnt = ELEM_IN_ARRAY(web_handlers);
    TraceInf("Registering handlers. Total count %u", cnt);
    for (uint8_t i = 0; i < cnt; i++) {
        esp_err_t err = httpd_register_uri_handler(server, &web_handlers[i]);
        if ((err != ESP_OK) && (err != ESP_ERR_HTTPD_HANDLER_EXISTS)) {
            TraceWrn("Failed to register %u|%s handler, reason [%s]", i, web_handlers[i].uri, esp_err_to_name(err));
            break;
        }
    }
    httpd_register_err_handler(server, HTTPD_404_NOT_FOUND, http_404_error_handler);
    TraceInf("Handlers registered successfully");
}

And then in CMakeLists.txt I can do the following:
set(embed_files index.html styles.css scripts.js)
idf_component_register(EMBED_FILES ${embed_files})

How does exactly compiling web files work and why is it used here? Is it purely for convenience purposes?  Would using the above method work for framework such as Vue.js where I embed each?

Thanks for the update. Closing this issue as it seems to be resolved. Please feel free to reopen in case it still persists.

I think it would be wise to update the example README to include the dependency on the old node version as there seems to be quite a confusion. There are multiple other threads regarding the same issue and everything could be fixed by adding a single line to say that this example needs version 10.19.0

Yes indeed. I have created an MR internally for adding the note in README file.


test_remote_storage_backup_and_restore is flaky

A recent failure in main: https://github.com/neondatabase/neon/actions/runs/3563254362/jobs/5986129088
main seems failing:passing about 50:50 at the moment, each failure is unique in its flakiness.
_______________ test_remote_storage_backup_and_restore[mock_s3] ________________
[gw3] linux -- Python 3.9.2 /github/home/.cache/pypoetry/virtualenvs/neon-_pxWMzVK-py3.9/bin/python
subprocess.CalledProcessError: Command '['/tmp/neon/bin/neon_local', 'pageserver', 'start', "--pageserver-config-override=remote_storage={bucket_name='test_remote_storage_backup_and_restore',            bucket_region='us-east-1',endpoint='http://<IP_ADDRESS>:18000/'}"]' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:
test_runner/regress/test_remote_storage.py:58: in test_remote_storage_backup_and_restore
    env = neon_env_builder.init_start()
test_runner/fixtures/neon_fixtures.py:623: in init_start
    self.start()
test_runner/fixtures/neon_fixtures.py:619: in start
    self.env.start()
test_runner/fixtures/neon_fixtures.py:916: in start
    self.pageserver.start()
test_runner/fixtures/neon_fixtures.py:1778: in start
    self.env.neon_cli.pageserver_start(overrides=overrides, extra_env_vars=extra_env_vars)
test_runner/fixtures/neon_fixtures.py:1583: in pageserver_start
    return self.raw_cli(start_args, extra_env_vars=extra_env_vars)
test_runner/fixtures/neon_fixtures.py:1356: in raw_cli
    raise Exception(msg) from subprocess.CalledProcessError(
E   Exception:             Run ['/tmp/neon/bin/neon_local', 'pageserver', 'start', "--pageserver-config-override=remote_storage={bucket_name='test_remote_storage_backup_and_restore',            bucket_region='us-east-1',endpoint='http://<IP_ADDRESS>:18000/'}"] failed:
E                 stdout: Starting pageserver at 'localhost:18130' in '/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo'.....
E   pageserver has not started yet, continuing to wait.....
E
E                 stderr: pageserver start failed: pageserver did not start in 10 seconds
------------------------------ Captured log setup ------------------------------
2022-11-28 09:28:41.969 INFO [neon_fixtures.py:2706] get_test_output_dir is /tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]
2022-11-28 09:28:41.970 INFO [neon_fixtures.py:2727] test_output_dir is /tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]
----------------------------- Captured stderr call -----------------------------
<IP_ADDRESS> - - [28/Nov/2022 09:28:42] "PUT /test_remote_storage_backup_and_restore HTTP/1.1" 200 -
<IP_ADDRESS> - - [28/Nov/2022 09:28:43] "PUT /test_remote_storage_backup_and_restore//tenants/7551b653fb966923d30a434dd0a0cfae/timelines/b9291f58624e0171def184733ebdb94d/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000001696070-00000000016960E9 HTTP/1.1" 400 -
------------------------------ Captured log call -------------------------------
2022-11-28 09:28:42.394 INFO [neon_fixtures.py:910] Config:
default_tenant_id = '7551b653fb966923d30a434dd0a0cfae'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:18001/']
etcd_binary_path = '/usr/local/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:18130'
listen_http_addr = 'localhost:18131'
auth_type = 'Trust'

[[safekeepers]]
id = 13
pg_port = 18132
http_port = 18133
sync = false
2022-11-28 09:28:42.395 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmp1gohwdz6 --pg-version 14 --pageserver-config-override=remote_storage={bucket_name='test_remote_storage_backup_and_restore',            bucket_region='us-east-1',endpoint='http://<IP_ADDRESS>:18000/'}"
2022-11-28 09:28:42.395 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo"
2022-11-28 09:28:43.376 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:18130' in '/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo'.
pageserver started, pid: 22183
Successfully initialized timeline b9291f58624e0171def184733ebdb94d
Stopped pageserver 1 process with pid 22183

2022-11-28 09:28:43.377 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start --pageserver-config-override=remote_storage={bucket_name='test_remote_storage_backup_and_restore',            bucket_region='us-east-1',endpoint='http://<IP_ADDRESS>:18000/'}"
2022-11-28 09:28:43.377 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo"
2022-11-28 09:28:53.442 INFO [neon_fixtures.py:1355]             Run ['/tmp/neon/bin/neon_local', 'pageserver', 'start', "--pageserver-config-override=remote_storage={bucket_name='test_remote_storage_backup_and_restore',            bucket_region='us-east-1',endpoint='http://<IP_ADDRESS>:18000/'}"] failed:
              stdout: Starting pageserver at 'localhost:18130' in '/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo'.....
pageserver has not started yet, continuing to wait.....

              stderr: pageserver start failed: pageserver did not start in 10 seconds
---------------------------- Captured log teardown -----------------------------
2022-11-28 09:28:53.816 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-28 09:28:53.816 INFO [neon_fixtures.py:2487] Stopping safekeeper 13
2022-11-28 09:28:53.816 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 13 -m immediate"
2022-11-28 09:28:53.816 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo"
2022-11-28 09:28:53.823 INFO [neon_fixtures.py:1347] Run success: safekeeper 13 is already stopped: no pid file "/tmp/test_output/test_remote_storage_backup_and_restore[mock_s3]/repo/safekeepers/sk13/safekeeper.pid" is present

2022-11-28 09:28:53.824 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

closed by https://github.com/neondatabase/neon/pull/2983


fixing link

There was an error while validating job aec6648e-5c00-409d-a233-8dcdf46712d6 Message:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
Details:Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase+ContextCommandException:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
---> System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Error clonning repository ---> LibGit2Sharp.NotFoundException: Branch 500 not found. Available branches: origin/master
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass34.<>c__DisplayClass39.b__2e(KeyValuePair2 branch)    at System.Collections.Generic.List1.ForEach(Action1 action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass34.<CloneRepository>b__2c()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetVersionAsync(String path)
at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)    --- End of inner exception stack trace ---    --- End of inner exception stack trace ---    at Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase.ThrowIfErrorsLogged()    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


fix minor issues in the readme

First off, what an amazing project! I'm doing advent of code this year in Gleam, and I struck absolute gold with gladvent. The return type enforcement for the parse function and the expectations in the gleam.toml are incredible. Somehow you've made me even more excited for the upcoming advent of code. Great work! :)
Regarding the PR, I noticed these minor issues when going through docs and thought I'd share.

Oh wow what wonderful feedback to receive! 🤗 thanks


A trivial typo of spatial SE block

Hello, I just found a tiny typo in the spatial_squeeze_excite_block function of se.py.
It should be:
se = Conv2D(1, (1, 1), activation='sigmoid', use_bias=False, kernel_initializer='he_normal')(input)
(input) should be append in the end of the above code.
I know it is trivial. hope not to confuse anyone who want to call it. Thanks.

Patched via dc1bc030c9e8790c4a1dc4ba77776119652bd6d0


[ECS] Deprecate outdated php-cs-fixer native sets as barely used

These 4 sets were copied many years ago from php-cs-fixer. They're not maintained and updated, as they don't bring any extra value.
You can use directly the test from php-cs-fixer: https://github.com/FriendsOfPHP/PHP-CS-Fixer/tree/master/src/RuleSet/Sets,
or even better, go for PSR-12 that handles the code in pretty detailed and standard way :+1:

Hello @TomasVotruba, how do you directly import a set from https://github.com/FriendsOfPHP/PHP-CS-Fixer/tree/master/src/RuleSet/Sets plz? Do you have an example? I can't find the migration path from the deprecated set.

Hi, I have no clear example. But in theory you can use the set class, parse the strings and join them with FQN class alternatives to ecs.php format.

Thanks. For the record here is what I did and it works:
$fixerFactory = new FixerFactory();
$fixerFactory->registerBuiltInFixers();
$ruleSet = new RuleSet([
    '@Symfony' => true,
    '@Symfony:risky' => true,
]);
$fixerFactory->useRuleSet($ruleSet);
$services = $ECSConfig->services();
foreach ($fixerFactory->getFixers() as $fixer) {
    $configurator = $services->set(get_class($fixer));

    if ($ruleConfiguration = $ruleSet->getRuleConfiguration($fixer->getName())) {
        $configurator->call('configure', [$ruleConfiguration]);
    }
}

The downside is that it now uses internal classes from PHP-CS-Fixer :man_shrugging:

I'll give @fancyweb's solution a try but it sounds like I'll see warnings for internal classes :)

That's not relevant in this case, as you use it on purpose :) I actually didn't know it's that simple :open_mouth:

PS: just started sponsoring you from my company account https://github.com/sctr?type=source, thanks for all the great tools you've built. My team and I use rector and ECS a lot.

Thank you :clap: :bow:

Hello,
I understand why it has been removed, however it now requires a dev dependency on friendsofphp/php-cs-fixer, which is not a good thing for any project (since it's a tool and not a real dependency).
Even the README on the repository recommends to install it in a special tool folder.
Could we find a better solution?

This might change for better developer experience soon :)
https://twitter.com/VotrubaT/status/1627613681595953152

@TomasVotruba this is amazing news!  Any idea when it will be available?

Hi, like 2 weeks ago :)

@arderyp see https://github.com/easy-coding-standard/easy-coding-standard/pull/58

thanks for the super quick response (and fix). I will test this out :)

works for me thanks again!


Add configMap, which is the config-center of volcano-vgpu

We need to Add a unified configMap for volcano-vgpu, just like hami, which consist of

global-configs: resourceName, resourceMemoryName, etc...
node-configs: device-core-scaling and device-split-count for each devices

/lgtm


Lra 558 lsa ride share add terms interface

The Terms link is added to the header.
There are Index, Show, New, and Edit Terms pages in the pull request.
Terms scopes are edited.
Current term(s): The term is current until the next term starts. In May-August there are two current terms.

I added three more commits to the PR. Please review.

@anantaUM Please review this PR as soon as possible on Monday. Since I changed column names in the terms table, all my other branches are broken right now on my localhost because they use old names.


Bump dependencies

This follows #282.
Bump dependencies to reduce depending on multiple versions of crates and move forwards in general.
The following lines disappear from the output of cargo tree -d:
nalgebra v0.29.0
└── hotham-simulator v0.2.0 (C:\Users\morot\source\repos\hotham\hotham-simulator)

nalgebra v0.31.0
├── hotham v0.2.0 (C:\Users\morot\source\repos\hotham\hotham) (*)
├── parry3d v0.9.0
│   └── rapier3d v0.14.0 (*)
└── rapier3d v0.14.0 (*)

num-rational v0.3.2
└── image v0.23.14 (*)

num-rational v0.4.1
├── nalgebra v0.29.0 (*)
└── nalgebra v0.31.0 (*)

simba v0.6.0
└── nalgebra v0.29.0 (*)

simba v0.7.1
├── nalgebra v0.31.0 (*)
├── parry3d v0.9.0 (*)
└── rapier3d v0.14.0 (*)

This leaves us with duplicated versions of cfg-if and raw-window-handle (not introduced here).

Nice work @rasmusgo - we should investigate some sort of automated dependency check similar to what https://github.com/Ralith/openxrs does.


Fix flaky TestArchiverAbortEarlyOnError

What is the purpose of this change? What does it change?
The test function TestArchiverAbortEarlyOnError fails from time to time.
This PR fixes the race condition in the test, see the commit message for the full description.
For reproducing the test error use the following command:
go test -count=1000 -parallel=1 -cpu=1 -run TestArchiverAbortEarlyOnError ./internal/archiver/
Was the change discussed in an issue or in the forum before?
The test failure showed up in #2285.
Checklist

[x] I have read the Contribution Guidelines
[ ] I have added tests for all changes in this PR
[ ] I have added documentation for the changes (in the manual)
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[x] I have run gofmt on the code in all commits
[x] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

Awesome, thanks!


downloading issues

when i download any course it saying that downloaded 0 out of 1 item

If it shows 1 item then it means you have lecture start - lecture end option enabled in settings. Please deactivate the feature and you should be able to download all files.


Inconsistent syntax for unique indexes

When defining an index on a column, you can chain index and unique calls.
When defining an index on the table level (e.g., to span it over multiple columns), you can not chain the two functions. This leaves the question whether you need to do
table.index([ 'foo', 'bar' ]);
table.unique([ 'foo', 'bar' ]);

or only
table.unique([ 'foo', 'bar' ]);

?
The documentation unfortunately is not very clear here.

table.unique() isn't currently documented at all (https://github.com/tgriesser/knex/issues/988). I would think just table.unique() though, and that also using table.index() would be at best wasteful, unless you wanted to create a second index of a different type† (assuming the database engine allows that), or worse maybe overwrite your unique index because of the automatic naming? That does seem like an unfortunate API inconsistency though. Could probably be solved by making column.unique() take the same arguments as column.index() and giving table.index|unique chained index|unique methods. That makes me wonder what Knex does under the hood with column.unique().index() though -- create one or two indexes.
†According to Postgres 9.5 docs:

Currently, only B-tree indexes can be declared unique.


Black Screen

How can I change the black  background color in multires rendering?
Is it possible to  render new multires panorama tiles  without removing older tiles?

It is not possible to change the multires background color.
I'm not sure what you're asking with your second question.


ci: run coverage for the free-threaded build

This is loosely related to #4635.
From what I've worked out experimenting with those PRs, I realise that we can run coverage on the merge commit in CI. The nice thing about this is that we can add all jobs (not just build) to coverage.
Most importantly for current work, this enables code coverage for the freethreaded job. cc @ngoldbaum

Thanks David! It'll be nice to have coverage reports on PRs for Py_GIL_DISABLED blocks.

Over on #4588 I'm seeing the coverage tests failing with a git error: fatal: refusing to fetch into branch 'refs/heads/main' checked out at '/home/runner/work/pyo3/pyo3'. I don't immediately see what's wrong...


[Subtask] Support distributions expression

Describe the subtask
We can get distributions expression code from https://github.com/apache/gravitino/pull/5646/commits/c3d8271ee3992a1d09590440af85faf4cdb48ef3
Parent issue
#5198

Can I work on this issue?


Port CipherEquivalence.v

Progress on #566
New, parallel version of CipherEquivalence.v with the Circuit structure. Along the way, I separated out multistep and a couple of proofs about it into its own file, added a new tactic destruct_inner_pair_let, and added some helper lemmas about lists.

Did the CipherEquivalence proofs copy over to the CipherEquivalenceNew or did you have to completely rewrite?

Mostly they did, except the cipher_loop_equiv proof now has a helper proof that describes the single-step behavior (it wasn't strictly necessary, but I think it's nice to have). So the previously super long and complicated proof became two medium-length and simpler proofs.


TX details: rename "block" to "height"

As per https://app.clickup.com/t/861mx1rme

No, the screenshot was wrong, we shouldn't do this.


ngeohash.js is missing in action

First of all, I'm not using browserify for my project, I did however install it and ran npm install afterwards, as mentioned in the docs. However, I cannot seem to find ngeohash.js after running that. Am I doing something wrong?

Fixed in 5aa6e88
I just updated the script and README now the file can be generated from npm run browserify


Reverse proxy with sub folder support

I use docker to deploy with this image: fjudith/draw.io
and this is my nginx conf:
    location = /draw {
        proxy_pass http://domain:8083/;
    }

But I did not found any where to config this sub folder in draw.io, this caused the static resources not found problem

hello my image plublis the app at the root

upstream http_drawio {
  ip_hash;
  server <IP_ADDRESS>:8080
}

...

  location /draw {
    rewrite ^([^.]*[^/])$ $1/ permanent;
  }
  location ~ ^/draw/(.*)$ {
    proxy_buffering off;
    proxy_redirect off;
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $remote_addr;

    proxy_pass http://http_drawio/$1;
  }

...


Correction for raw affiliation Western University Western University

Correction needed for raw affiliation Western University Western University
raw_affiliation_name: Western University Western University
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4360593204;W4388727027;W4385885009;W4386928715;W4385553950
contact: 21d5b6a7619834d6dca6c6c162bd89c5:6f3d6248c28de1d3 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Scale estimates

It's good to look at existing datasets to help us estimate the scale.
Here's The European Library with 109M records: http://www.theeuropeanlibrary.org/tel4/access/data/opendata
According to this, Flickr receives on the order of 10M photos per day:
https://www.flickr.com/photos/franckmichel/6855169886
LoC: 16M books
CC: 1.1B works
Spotify catalog: ~30M songs (http://www.nytimes.com/interactive/2015/06/30/business/media/music-streaming-guide.html)
Feel free to add any other large-scale datasets here
For fun, here's the IA petabox storage system: https://archive.org/web/petabox.php

The social network numbers are definitely orders of magnitude more than openly licensed, but good to compare with (some sources are better than others().
Instagram: 58,000,000 per day
Facebook: 300 million per day. (Source: Gizmodo)
Tumblr: 53.3 million

imo the CC archive is probably a decent target for now

Yeah, the "realistic long-term" scale I'm thinking of is "low tens of billions" based on these figures

So invariably we'll need to shard; let's do that from the beginning.

~2M Getty images on hand right now

Would be good to revisit this on a per-namespace basis, making mental note


Question: Upload backups to EMC ECS ?

Does bbr-pcf-pipeline support uploading backups to EMC ECS ?

I am using EMC ECS and I am repeatedly getting errors trying to backup to ECS.
Trying to push Ops Manager backup zip file:
om-backup-artifact
3.42 MB / 3.42 MB [===================================] 100.00 % 18.79 KB/s 3m6serror running command: RequestError: send request failed
caused by: Put https:/pcf-cflab02-cg-backups/installation.zip: Proxy Error

If you take a look at output above, it's missing EMC ECS endpoint (i.e.,  s3ecs.XXXXX.localnet:9020"
Trying to push ERT backup:
ert-backup-bucket
5.00 MB / 113.51 MB [=>--------------------------------] 4.40 % 24.98 KB/s 3m24serror running command: RequestError: send request failed
caused by: Post https:/pcf-cflab02-cg-backups/ert-backup.tar?uploads=: Proxy Error

In both cases BBR pipeline is not picking up ((storage-endpoint)) variable.
Snippent from pipeline.yml:

- name: om-backup-artifact
  type: s3
  source:
    bucket: ((backup-artifact-bucket))
    region_name: ((storage-region))
    endpoint: ((storage-endpoint))
    access_key_id: ((storage-access-key-id))
    secret_access_key: ((storage-secret-access-key))
    versioned_file: installation.zip
    use_v2_signing: ((storage-use-v2-signing))

Snippet from secrets.yml file:
skip-ssl-validation: true
pivnet-api-token: "XXXXXXXXX"
bbr-version: 1.2.3
opsman-url: https://opsmanager.cflab02-cg.iXXXXXXX.localnet
opsman-username: OpsMan
opsman-password: "XXXXXXXXX"
backup-artifact-bucket: pcf-cflab02-cg-backups
storage-region: ""
storage-endpoint: "s3ecs.XXXXX.localnet:9020"
storage-access-key-id: pcf-nonprod-01
storage-use-v2-signing: true
storage-secret-access-key: "XXXXXXXXXXXXXXXX"
concourse-worker-tag: BBR
private: true
disable_ssl: true

Any ideas ?
Thank so much.

Answering my own question: yes it does. You have to do couple of things:

Make sure you have enabled versioning on your bucket. This is a must
If you're using proxy in your environment, make sure to list your S3 in FQDN format in your /etc/environment file
As it currently stands, Concourse mangles no_proxy statement.  This is a bug. Concourse folks are envisioning a fix for it in 3.15.x release. As a workaround, remove all proxy-related entries in your worker environment file and source your /etc/environment file for your proxy entries. Consequently, in your SystemD file, pass proxy settings such as this --http-proxy=${http_proxy} --https-proxy=${https_proxy} --no-proxy=${no_proxy} and so forth. This should take are of it.

Cheers,
Alex


Add forced update

On startup do a check to an url loaded from config.js
If the response is anything but status === 400, it is ok (200 or 404 are ok).
If not compatible show a specialized screen.

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


Option to view zones

Hi, it will be nice to have an option in UI to see the zones after you made them.

You mean to see the area ? Like display the line draw ?

I think @hadesownage is asking for an option in the admin menu to show the zone like you do when creating. See below.

I agree this would be super helpful viewing already created zones.

I just added the feature. Please, make sure to read the warning in the readme (changelog section), there is a small breaking change (you have to rename a db property).


Write a regression test verifying picklability of Unpack

See #44. dwf/picklable_itertools@825eb0f solved this (I think), but we might as well add a test to make sure this doesn't happen again, just in case.
This could be eventual CCW fodder.

Closed by #110.


Combination of nargs='+' and type=float fails when reading from config file

I love the work you've done with this package, it has spared me from so many parsing-induced headaches.
I did, however, run into a slight problem with the nargs-option (using ConfigArgParse 0.9.3). If I have a file foo.py and I add an argument with parser.add('--bar', type=float, nargs='+'), then the following works as expected:
./foo.py --bar 1.0 2.0 3.0

However, having bar = 1.0 2.0 3.0 in the config file conf.ini does not work:
./foo.py --conf conf.ini
foo.py: error: argument --bar: invalid float value: '1.0 2.0 3.0'

As far as I understand it from reading the source code, the problem arises because config file values are passed to argparse as a single string, so the config file setting above would actually be equivalent to
./foo.py --bar "1.0 2.0 3.0"
foo.py: error: argument --bar: invalid float value: '1.0 2.0 3.0'

This of course fails since that string is not a valid float.

I expecting the same issue,
would be nice to specify
bar =[ 1.0,2.0, 3.0]

and allow  nargs="+" or nargs=3 and an error would generated if the list is longer

coalesced into #30


Missing pause option on queued state

Added missing 'pause' option to context menu when a torrent is in uploading queued state. Fixes #799.
I'm not completely sure if this is the correct solution. My current thought is that the pause option is missing when: the torrent is finished and not uploading (state is UploadingQueued). When the torrent is uploading then the state is also uploading, so this bug doesn't happen.

Hey, thanks! I'll run through the code as well and see if behaves correctly :)


github history: restore any commit

Ability to restore any existing commit.

This is awesome!
I think having this for all projects would be awesome. What if we used git in the browser?  Then if they do log into github and want to host there, we can literally just push their git repo.
Here's a decent git implementation in JS. I doubt it's very big:
https://github.com/isomorphic-git/isomorphic-git
This might also be a good workaround to users or MakeCode bugs accidently deleting work and not being able to undo.


✨[Feature Request]: Add a new page for disabled person

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The disabled person tab redirects to home page.
I would like create a new page for that button.
Features I would like to add to the page:
listing hospitals and their accessibility options, what insurance options are available (if the hospital allows cashless payment) , redirect to doctor and appointment pages.
I would also like to rename disabled person tab to differently abled people.
Use Case
This feature would be helpful to disabled people.
Benefits
No response
Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04 and @varshith257 please assign this issue to me


UI: Add a scroll view in covid tracker section

Description:

Make the borderd section scrollable.

The underlined section :

PR Instruction:

Issue will be assigned on a first come first serve basis.
If you are thinking to make a pr then at first be sure to get assigned.
before pushing your PR please make sure to fetch upstream.
your pr should be pushed on the develop branch only.
try to complete your assigned task within 3 to 5 days and if you need more time then please let me know. As the program has limited time only so please try to complete as fast as you can.
With your PR try to send a screenshot or screen recording of your work

@sitamadex11 I have open a PR kindly review it


Create an updated schema diagram for MongoDB

Create an updated schema diagram that accurately reflects the organization and features of the DS MongoDB collections

Created BL-391 out of this issue.


BUG: new content not deployed to the website for months

Describe the bug
New content seen in merged pull requests are not making it to the website at https://bitcoin-only.com
PR https://github.com/bitcoin-only/bitcoin-only/pull/705
webpage https://bitcoin-only.com/hardware
PR https://github.com/bitcoin-only/bitcoin-only/pull/706
webpage https://bitcoin-only.com/dev-tools
PR https://github.com/bitcoin-only/bitcoin-only/pull/751
webpage https://bitcoin-only.com/spend-bitcoin

To Reproduce
View one of the Pull Requests.
View the corresponding website page.

Expected behavior
Content appears on the website.

Screenshots
e.g.
PR https://github.com/bitcoin-only/bitcoin-only/pull/705

webpage https://bitcoin-only.com/hardware

hmm ok will check


Handling multi-line input across connection types

This plugin was originally aimed at interactive usage. Which means it expects a connection input/output approach that is different than an editor:
https://github.com/Jycraft/jycraft/blob/master/src-common/jycraft/plugin/servers/PySFListener.java#L125
Meaning, it tries to keep reading, across messages, until it thinks you are "finished". This works well for telnet and for the interactive interpreter in the browser. But it's a pain when we want to send over a single chunk of code to execute.
We have added JSON support to the web socket version. Should we refactor this to let the browser tell the server when it is sending a full "file"?

I think it would be like adding another case in the switch
switch (messageType) {
            case login:
            // code
                break;
            case interactive:
                //code
                break;
            case file:
                //code
                break;
            case logout:
               //code
                break;
            default:
                break;
        }

though if you think of a more elegant solution I would love to hear hahaha, since all of this stuff is new to me I'm still a bit lost on what to do or how to do ir properly.
in these days i will do some rework on the implementation I made to fix some issues ben pointed and I will look into the file case you are mentioning

#21 should cover this

#22  did actually cover this, you can send a python script's path over the websocket to test a live execution or you can load them from a directory named python-plugins on the server's root directory, this is a working example of that.


[feat] Allow Restore on Installed Service

Currently it is required to wipe out a service in order to restore a backup.  If there's a problem with the backup, data is gone.

Essentially rolling back to a prior state. This is conceptually the same as uninstalling and restoring from backup, but with the up front guarantee that it will work. Needs strong messaging to prevent loss of newer data.

it would be great if the integrity of the backup could be verified before requiring the user to delete their datadir.
It seems like a better system would be: allow the user to restore over existing data, but warn them before they do this that it will replace their existing data. Then, run the restore to make sure it doesn't error out. If it errors, don't delete the datadir at all.


[sql-parse] Fixing parsing LIMIT exceptions

This PR fixes an issue when trying to extract the LIMIT from a query and the LIMIT value is either missing or ill-defined which previously would raise a series of exceptions (IndexError, TypeError, etc.) which would result in an Internal Server Error (500) being thrown.
Note if no valid LIMIT can be extracted we simply return None and allow the underlying database engine to flag the issue during parsing.
to: @graceguo-supercat @michellethomas @mistercrunch @timifasubaa

Codecov Report

Merging #6963 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #6963      +/-   ##
==========================================
- Coverage   64.76%   64.76%   -0.01%
==========================================
  Files         421      421
  Lines       20386    20384       -2
  Branches     2249     2249
==========================================
- Hits        13204    13202       -2
  Misses       7049     7049
  Partials      133      133

Impacted Files
Coverage Δ

superset/sql_parse.py
99.13% <100%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41041f2...a4cd78f. Read the comment docs.

LGTM


ames: forward iff we're a galaxy

Resolves #492.

Where is the best place to add a helper function to determine which identity type (comet, moon, planet, star, galaxy) we are, given c3_d *who_d? We need such a function to set the new "forwarding enabled" flag sat_u.for_o in the u3_ames struct.

So far we've just done u3do("clan:title", u3k(ship)).  Wouldn't be hard to add a clan function (especially if we need to call it before the loom is set up), not sure where it fits, maybe vortex.c?

Thanks @philipcmonk. How's this look now?


failed calling webhook "webhook.cert-manager.io":

Describe the bug
helm upgrade --install --namespace actions-runner-system --create-namespace \
             --wait actions-runner-controller actions-runner-controller/actions-runner-controller

Error: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": dial tcp <IP_ADDRESS>:443: connect: connection refused

Checks

[x] My actions-runner-controller version (v0.x.y) does support the feature
[ ] I'm using an unreleased version of the controller I built from HEAD of the default branch

Environment (please complete the following information):

Helm Chart Version 0.12.8

Retrying seemed to work.


thank you!

thanks for this and for your fork of scdl.
please consider enabling issues in your scdl repo so i can report.

Done


error

$ python cookie_crimes.py
Traceback (most recent call last):
File "cookie_crimes.py", line 139, in
forbidden_process = summon_forbidden_protocol()
File "cookie_crimes.py", line 100, in summon_forbidden_protocol
stdout=subprocess.DEVNULL,
AttributeError: 'module' object has no attribute 'DEVNULL'

You are are likely using python 2. DEVNULL does not exist for the python 2 version of subprocess.


Add LwIP-based Network and Service Tests to Continuous Integration Matrix

Currently, LwIP-based network and service tests are not included in the continuous integration matrix, leaving a substantial amount of exposure in continuous integration.

https://github.com/openweave/openweave-core/pull/155

Currently, three tests are failing under LwIP:

FAIL: happy/tests/standalone/pairing/test_weave_ble_01.py
FAIL: happy/tests/standalone/time/test_weave_time_local.sh
FAIL: happy/tests/standalone/time/test_weave_time_auto.sh

@jenniexie, any updates or insights on this?

Hi Grant, I haven't worked on this yet, I should be able to get some time for this one this week.
I will confirm with you for the actions I plan to do tomorrow.

I am seeing 4 test cases are failing on my setup:
FAIL: happy/tests/standalone/wdmNext/test_weave_wdm_next_mutual_subscribe_48.py
FAIL: happy/tests/standalone/wdmNext/test_weave_wdm_next_mutual_subscribe_61.py
FAIL: happy/tests/standalone/time/test_weave_time_local.sh
FAIL: happy/tests/standalone/time/test_weave_time_auto.sh
And I am not seeing test_weave_ble_01.py in my test result list, maybe it is disabled for LWIP case, I will on these ones and try to fix them.

Resolved.


Add Hbase Plugin

Title: Hbase Plugin Contribution
Link: https://github.com/VictorZeng/pinpoint/tree/hbase-plugin/plugins/hbase
Target: pinpoint-hbase-plugin
Supported Version: hbase version 1.0.0+.
Description: trace hbase client and show hbase topology in the web ui.
ServiceTypes:

(8800, "HBASE_CLIENT")
(8801, "HBASE_CLIENT_ADMIN")
(8802, "HBASE_CLIENT_TABLE")
(8803, "HBASE_ASYNC_CLIENT")

Annotations:

(320, "hbase.client.params", VIEW_IN_RECORD_SET)

Configurations:

profiler.hbase.client.enable=true
profiler.hbase.client.admin.enable=true
profiler.hbase.client.table.enable=true
profiler.hbase.client.params.enable=true

@Xylus still Merging is blocked.

Codecov Report

Merging #4782 into master will increase coverage by 0.06%.
The diff coverage is 62.92%.

@@            Coverage Diff             @@
##           master    #4782      +/-   ##
==========================================
+ Coverage   40.45%   40.52%   +0.06%
==========================================
  Files        2570     2580      +10
  Lines       78297    78475     +178
  Branches    10643    10661      +18
==========================================
+ Hits        31678    31801     +123
- Misses      43735    43774      +39
- Partials     2884     2900      +16

Impacted Files
Coverage Δ

...rp/pinpoint/plugin/hbase/HbasePluginConstants.java
0% <0%> (ø)

...rcorp/pinpoint/plugin/hbase/HbasePluginConfig.java
100% <100%> (ø)

...oint/plugin/hbase/HbasePluginMetadataProvider.java
100% <100%> (ø)

...m/navercorp/pinpoint/plugin/hbase/HbasePlugin.java
34% <34%> (ø)

...hbase/interceptor/HbaseTableMethodInterceptor.java
50% <50%> (ø)

.../hbase/interceptor/HbaseClientMainInterceptor.java
68.18% <68.18%> (ø)

...base/interceptor/HbaseClientMethodInterceptor.java
73.33% <73.33%> (ø)

...hbase/interceptor/HbaseAdminMethodInterceptor.java
75% <75%> (ø)

...interceptor/HbaseClientConstructorInterceptor.java
83.33% <83.33%> (ø)

...n/hbase/interceptor/HbaseClientRunInterceptor.java
85.71% <85.71%> (ø)

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c7e604f...d26eb4b. Read the comment docs.


Make the typing explicit

Description
Because TDiscovered is fully abstract it is not possible to correct serialize it with pydantic v2. This PR makes it more concrete so we can handle it explicitly.
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 67e6a37511621e02c77ff1c7b6fd340cc23a9f3a


Datagrid with expandable rows not rendering correctly (Angular 9)

I have updated to the latest Angular 9 and clr@next packages 3.0.0-next.8
The datagrid with expandable rows fails to render correctly but functionaly it works as expected.

Hello, @ImranAhmed thanks for reporting it. Can you provide a working example of this issue? So we could test and investigate.
Thanks in advance.

Hi, I managed to fix it.
I had a static reference to the old css file at<EMAIL_ADDRESS>I had to point this to latest @next version and it worked. Thanks.


Popup not Repositioning when Trigger Changes Position Due to Transition of Another Element

Bug Report
Steps
In the code sandbox, do the following steps to reproduce the issue:

Scroll down
Click the "Collapse" button

Expected Result
The open popup should follow the trigger when the other column is hidden which causes the trigger's position to change
Actual Result
The open popup does not follow the trigger's new position and stays where it was before collapsing
Version
3.0.0-beta
Testcase
https://codesandbox.io/p/sandbox/semantic-ui-example-mrdt8f

I see the issue as well. An interesting observation for me is that the tooltip will relocate properly after scrolling.

I see the issue as well. An interesting observation for me is that the tooltip will relocate properly after scrolling.

I noticed that too. However, I'd want to not have the user to do that.


Added support for testsuite

@snowleopard @angerman
Validation result after this push:
SUMMARY for test run started at Mon May 14 00:32:42 2018 IST
0:20:37 spent to go through
6359 total tests, which gave rise to
23523 test cases, of which
17231 were skipped
  42 had missing libraries
6098 expected passes
  94 expected failures

   0 caused framework failures
   0 caused framework warnings
   1 unexpected passes
  55 unexpected failures
   2 unexpected stat failures

@chitrak7 Thanks! I've added some comments.

@alpmestan I do not exactly know that, Can you give me pointers on where to look.  More importantly, why does testsuite decide to skip a test.

@snowleopard Can you please see why recursive rule failure is coming?

@alpmestan I do not exactly know that, Can you give me pointers on where to look. More importantly, why does testsuite decide to skip a test.

You should see some information about this in the testsuite driver initialization part of the output (early on, when you look at the full log).

@alpmestan I believe skipped tests are because of using "fast" option with testsuite.

@chitrak7 OK. If you ever get a chance to, it would be terrific to add a way to run the equivalent of ./validate --slow. If not, I'll do it. But not in this PR of course. Thanks for the reply and taking a look at what was going on :+1:

@chitrak7 Please resolve merge conflicts.

Can you please see why recursive rule failure is coming?

@chitrak7 The recursive rule failure is unrelated to your PR. I think the reason is #599.

@chitrak7 Something is wrong, looks like you've duplicated the recent commits instead of rebasing.

@snowleopard I have reset my repository and made necessary changes. It is currently failing due to "llvm" issue. I will resend it once that PR Lands.

Should the title of this PR be "Add support for nofib testsuite" ? We already support hadrian test.

No, support for nofib was the goal of #599, not this PR. This PR is about supporting the execution of more tests, and about building things that are required by some of them which were not built previously. It still skips a whole bunch of tests but maybe @chitrak7 could provide an overview of the state of things with/without the commits from his branch? In terms of # of tests being run, # of broken test expectations.

I just noticed that this PR also add a new file src/Rules/Nofib.hs...

Right, my commits somehow did not get merged properly apparently. But you cann tell they've already been merged because they refer to the PR number.

Hi @snowleopard @angerman, I have pushed the work done with validation implementation.

@chitrak7 Thanks! Let's come back to this PR once we fix Hadrian.

OK, I think we can merge this -- there are a few minor issues but we can fix them later.
@alpmestan Do you have any further comments?

Merged. Many thanks @chitrak7, and everyone else for the review!


Feature request: databases with non default options

Recently we get an application upgrade (app + databases) from a software house, then we immediately get worst performance.
Of course they tell us "it's your SQL Server, your network" and so on... until I see the tag "(AutoClose )" in the database list of Azure Data Studio.
In a perfect world, DBADash would show me a warning when it sees the AutoClose option on, because it is a mess.
Is it possible to get warnings for AutoClose and other database options when they are different from default value?
Thanks

Ok, it works as you described.
But when I'm on the Home page, I see all my instances and the column "Database State" is green for all the rows.
If I click on "view" I can see that "Auto Cose" is red but I would never have clicked if the background is green.
Am I missing something? Or maybe I'm using a non default DBADash configuration?

The Database State check is looking for databases where the state is Recovery Pending, Suspect or Emergency.  The Summary is for things that you would want to include as part of your daily checks so these states are important to highlight alongside missing backups, failing jobs etc.
Auto Close or Auto Shrink is more of a potential misconfiguration.  I don't think this should typically be part of the daily checks - more as part of a configuration review.  I can see why you would want this to be more visible though given the issue with it changing during deployment.
As a workaround, you could create an agent job to fail if there are databases in the DBA Dash repository DB with auto close (which is picked up on the Summary page).  Something like this in an agent job.
IF EXISTS(
	SELECT 1
	FROM dbo.Databases D
	JOIN dbo.Instances I ON I.InstanceID = D.InstanceID
	WHERE D.is_auto_close_on=1
	AND D.IsActive=1
	AND I.IsActive=1
)
BEGIN
	RAISERROR('Auto Close is enabled on one or more databases',11,1)
END

Or a custom check could be used.

I added a custom check, using the code  below:
USE [DBADashDB]
GO
CREATE OR ALTER PROC [dbo].[DBADash_CustomCheck]
AS
-- Table variable used to ensure the output is in the required format
DECLARE @CustomChecks TABLE(
Test NVARCHAR(128) NOT NULL,
Context NVARCHAR(128) NOT NULL,
Status TINYINT NOT NULL,
Info NVARCHAR(MAX) NULL,
PRIMARY KEY(Test,Context),
CHECK (Status IN(1,2,3,4))
)
/*
Run your own tests and insert the results into @CustomChecks table.
Test = Name of your custom test
Context = Context where the test applies to.  e.g. application name, job name, database name, server name etc.
Status =   1=Critical (Red), 2=Warning (Yellow), 3= N/A (Grey), 4=OK (Green)
Info = Any additional information you would like to include
*/
INSERT INTO @CustomChecks(Test,Context,Status,Info)
SELECT 'Database AutoClose check','Database',2,'Warning on database ' + D.name + ' on server ' + I.ServerName
FROM dbo.Databases D
JOIN dbo.Instances I ON I.InstanceID = D.InstanceID
WHERE D.is_auto_close_on=1
AND D.IsActive=1
AND I.IsActive=1;
-- return data in required format
SELECT Test,
Context,
Status,
Info
FROM @CustomChecks
The SELECT statement returns 1 row, but Summary dashboard doesn't show me an alert, in this case a warning.

The custom check was designed to be deployed to the monitored instances rather than the repository database.  You can still do the check against the repository database if the associated instance is being monitored.  The stored proc needs to be deployed to whatever database the service is connecting to (typically master unless you specified an initial catalog for the source connection).  The check will be associated with the instance that hosts the repository database.

Ok, I created the stored procedure in the master database of a monitored instance and it works as expected.
Thanks... now is a perfect world :)


USE AND WORKING SOFTWARE

PLZ SHOW THE STEPS

PLZ SHOW STEPS

Read the README.md file.

Please tell me how to working on this software
On Wed 14 Nov, 2018, 1:19 PM Adones Pitogo<EMAIL_ADDRESS>wrote:

Closed #22 https://github.com/adonespitogo/AdoBot/issues/22.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adonespitogo/AdoBot/issues/22#event-1965125347, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aq8VXYUkjVwkHo5RnPXNdIXiBjQ_psUZks5uu8rsgaJpZM4YdKEp
.


WIP: bump c-ares library to v1.32.2

Commit Message: Bump c-ares library to v1.32.2
Additional Description: Last attempt at version upgrade failed few ARM tests, relating to IPv6-localhost
Risk Level:
Testing:
Docs Changes:
Release Notes:
Fixes #33138
Fix #35222
Please don't review yet. PR created to run tests

c-ares 1.32.3 is now available


[FEATURE] Way to utilize magic vars generically?

Description of the requested feature
The magic vars is basically a json structure with no standard keys, for instance the EWW_NET and EWW_DISK gives few similar objects of different interfaces and different partitions, but they can't be used without hardcoding particularly to the system-specific thing... Maybe a shell script interfereing in between or few more extension to s-expr be helpful, like looping through key-value or just key or just value, mapping to particular key of each in an array, take max/min (useful for EWW_NET), take sum maybe etc.
Proposed configuration syntax
Unsure, lets discuss?
Additional context
-

There were for loops already-before the s-expr, not sure how they work out now that the syntax changed.

@legendofmiracles there weren't 🤔
Generally, while I understand the desire for more abstraction, the only real "solution" here would be to add a jq like engine into eww - which feels like it would drastically increase the complexity of eww again. Not for the implementation side necessarily (although probably), but also usage-side. Currently, I see relatively little need for this, as in 99% of cases one is making a widget for themselves, hard-coded to one system. Do you have any concrete examples where that higher level of abstraction would drastically increase the quality of a configuration?

True, we can potentially poll for lsblk or ip link show to get required interfaces for these 2 magic var, this might be a topic for future if more variables with more complexity comes in.
I'd just like to pass the var or its indexing to a shell script and receive output instead of increasing complexity of yuck/s-expr to have imperative language capability while their main purpose is just to declare the fields & tree of data. I guess this can work if we can pass s-expr instead of only literal values in the command of defpoll...
I'd rate this as low-priority issue.

I might consider a pipe function or something in simplexprs, that would allow passing values through a shell pipeline. If that existed, you could make use of jq directly, by running sth like pipe(EWW_DISK, "jq 'whatever'"). Would this work for your usecases?

If we can awk or sed probably most of the text based manipulations can be done easily as well.
+1, perfect idea!

@legendofmiracles there weren't 🤔
Generally, while I understand the desire for more abstraction, the only real "solution" here would be to add a jq like engine into eww - which feels like it would drastically increase the complexity of eww again. Not for the implementation side necessarily (although probably), but also usage-side. Currently, I see relatively little need for this, as in 99% of cases one is making a widget for themselves, hard-coded to one system. Do you have any concrete examples where that higher level of abstraction would drastically increase the quality of a configuration?

Actually there is already a rust version of jq called jql. It would be be pretty easy to add to eww as the project is one library with a 143 lines bin.rs.

My current workaround is the parameterise the machine-specific parts, and use the :visible property with an expression: https://gitlab.com/jokeyrhyme/dotfiles/-/blob/main/config/eww/eww.yuck
e.g.
(defwidget battery [id]
  (box :class "battery" :orientation "h" :space-evenly false :halign "end" :tooltip "battery ${id}" :visible {!!EWW_BATTERY[id].capacity}
    "🐇${EWW_BATTERY[id].capacity}%"))

(defwidget sidestuff []
  (box :class "sidestuff" :orientation "h" :space-evenly false :halign "end"
    ...
	(battery :id "BAT0")
	(battery :id "BAT1")
    ...))

So, even if not all of my machines have a BAT0 or BAT1, my config includes both, and hides whatever is not available

After yeeeeeeears of waiting, I now added a jq function via the jaq crate in #695!
I still think a generic pipe function would be an interesting idea, but having built-in jq-style processing definitely seeeeeeems quite reasonable. I'm wondering if how feasible it might be to simply use a jq implementation as a general replacement for simplexpr... 🤔


Merging from staging branch

Email recipient and domain whitelisting
Fixed issue causing logs to be mixed up across PRs
Test coverage
Linting
Documentation
Build improvements and dependency updates

Thank you for your contribution and Welcome to our Open Source Community!
To make sure your pull request is successful, we need all our contributors to be identifiable, but we couldn't parse the GitHub details of the following people : Nikolay Ganev
Luckily, resolving the issue is straightforward and you can resolve it by following the instructions below.

Alternatively, use the slightly more complex git reset --soft and git rebase to checkout your changes, rewrite the commit history locally and (force) push changes to the downstream branch.
If you have any issues with the steps above, please email<EMAIL_ADDRESS>so we can help you resolve before reviewing and accepting your pull request.
Thanks once again for the contribution and understanding.
cc @finos-admin

CLA bot is complaining about the git signature of a former FINOS collaborator, Nikolay Ganev. We have his ICLA on file, so it's ok to merge this PR.

Thanks @mcleo-d ! Proceeding with the merge and testing!


I can't implement this function

hi, how can I implement the link function in dataview as shown in the picture?

Hmm, I don't have support for external links? I will add for the next release.

You use elink in the query itself:
TABLE elink(url) AS link, ...

Thank you so much!

You can do that - elink can take two arguments, the second of which is the display text. So do
elink(url, "Link")

I suddenly feel very happy today, thank you very much for your guidance