add a Option to turn off the new feature：start to sync when plugin is loaded

I hope I can have complete control over the sync
In fact, I don't want it to run when starting obsidian because it would slow down my startup speed

I support this request.
Frequency is set to 0 in my settings, this is explicitly labelled as manual sync. Why would I want it to sync at startup?

I do like that auto-sync on startup is possible, but agree that it should be configurable, and that sync toasts should be disabled for any auto-sync behaviors.
Toasting button-click/manual sync makes sense, because a user expects the app to react to their intent. Toasting auto-sync (including periodic auto-sync) may tend to surprise the user, so I don't think that toasts should appear then.
I open Obsidian many times a day to jot things down, and usually it's starting up from scratch, so now I see two Omnisearch toasts obscuring UI every time I open the app. You've gotta tap away the toasts just to see the note header and options, for instance.
I do think that it's reasonable to default to auto-sync on startup on new installs, so new users aren't surprised by out-of-sync vaults, as long as its configurable.

Agreed, suddenly everything is sync. That's not user firendly. Default should be "No sync on startup"!
Currently it's a bug not a feature!

+1 to this feature request! When using git as source control it prevents pulls from completing successfully because of the conflicting files (local unstaged change to timestamp and upstream "old" timestamp).
Obviously the change can be discarded, but its an extra hurdle to cross.

+1 to be able to disable this. It updates the last sync timestamp at every obsidian restart. That creates conflicts in git sync. Please can we go ahead with a hacky approach for now? This feature needs to be stopped and enabled with the option to disable it later.

hey guys, i just added this option in v1.9.4

please let me know if it suits your need

Perhaps renaming the heading to "Sync on startup" might be clearer, like how obsidian git has named it?

Perhaps renaming the heading to "Sync on startup" might be clearer, like how obsidian git has named it? "start" might not be descriptive enough for people

yeah, it is clearer to use startup 👍  i will rename it in the next release. thank you!


Docker Keep installed nodes

Hi,
I tried to run docker nodered/node-red with the --mount option to keep data. Unfortunately this is not working for additional nodes. If I also link the node_moduls directory to external, node-red doesn't work anymore.
So how can I keep the nodes that I installed in addition.

There was a template you have removed that gathers all the required information to report an issue, it also points out that questions should be asked on the Forum, Slack or Stack Overflow and not here. When you ask your question on one of those venues please include a LOT more information, e.g. platform, a the actual docker command line you used to start the container.
Secondly the right repo (for actual issues, not questions) for the nodered/node-red docker container is here: https://github.com/node-red/node-red-docker

Sorry and thank you.


Coregistration GUI - BEM only, no high-resolution scalp surface

Hi there,
I'm having a problem with the coregistration GUI. When I load in a subject, I can only see them BEM and not the high-resolution scalp surface (see image below).
Am I missing a file from my subjects_dir that the GUI is expecting?
Thanks,
Tim.

coreg looks for:
_high_res_head_fnames = (os.path.join(bem_dirname, '{subject}-head-dense.fif'),
                         os.path.join(surf_dirname, 'lh.seghead'),
                         os.path.join(surf_dirname, 'lh.smseghead'))

where bem_dirname is SUBJECTS_DIR/SUBJECT/bem. Do you have any of these files? In theory should be produced by a standard Freesurfer pipeline, but it's possible our list of files to look for is not complete.
Is your -head.fif dense? The reason we don't use this file is that sometimes it is dense and sometimes it is sparse (depending on how the user has things set up), so we can't really rely on it. If it's common enough that it is dense for people, we could try to load it and check if it's dense or sparse because they typically differ by at least an order of magnitude in vertex counts.

(and surf_dirname is SUBJECTS_DIR/SUBJECT/surf)

Is there a good place we could have put this in the docs?  I'm thinking we can populate the Notes section of mne.gui.coregistration

@jasmainak it sounds like you are just starting to use mne coreg a bit, do you have time to make a PR with this information plus whatever other pitfalls you encounter? I'm thinking we can populate the Notes section of mne.gui.coregistration

Sure! But after 18th. I have a deadline tomorrow :)

I can't think of anything offhand, we can open new issues as people experience them (or @tbardouille if you still have problems let us know and we can reopen)


Fix patching of @PXT@ in hex files

This just does the patching up to 4 times per hex line.
This bug only triggers with particular binary layouts, essentially due to "randomness" in object binary layout

Hex files have limited line length, and I think we always use 16 bytes, so you cannot have more than 2. The loop might spin 4 times when the first four bytes match, but the next two don't (patch == null). I guess let's just leave it at this.


feat: add Alert and Avatar components

Adds misc components: Alert and Avatar.

If someone is able to fix TS errors on component HTML attributes- feel free to do that!

Same thing as #17.


Future of Postal?

 It's a huge time commitment and everyone wants everything for nothing.
The question is: What can contributors do to help?
Postal is very popular tool and is vital to many developer tool kits. The last commit was on July 17th. Seems like there is an increasing number of pull requests that are not being merged.
I'm totally understanding that life happens (and that's the highest priority), but trying to figure out how contributors can help keep Postal going? Is it donating money, time, or other resources?
It would just be interesting to get a discussion going of where Postal goes from here on out. Thanks for everything that you guys do!

@jaydrogers , I think I will just fork it and merge everything myself

I'm fully aware that anyone can fork it and start merging things, but I'm afraid that might just split the community.
What aTech did here is beautiful and I don't want to see it die. Looking at their site, it looks like they have a lot of other amazing apps going on too. I don't blame them one bit if they have their hands tied up with apps that actually pay their bills. Developers need to eat too! 😀
I want to be very respectful of their efforts and generosity with this project.
What I was hoping for out of this discussion was something along the lines of:

Getting a transparent update from the aTech of where things are at and what expectations the community should have for where Postal is going (possibly @adamcooke or @catphish?)
aTech letting us know what they need to continue the project (if that is granting access to more "core contributors" or even donation goals)

If aTech is too busy to respond to this thread (which is still very understandable), then we as a community need to figure out some sort of structure how to move forward.
It's very easy to hit the fork button. It's very difficult to keep a good community together.

It would be very interesting to hear @willpower232's thoughts too because he is a major resource to this project. He helps on almost every issue and probably knows most about this product other than the founders.

Thanks for your message @jaydrogers.
We're fully planning on keeping Postal running but we just haven't had the time to commit to much ongoing development. At the moment the 300+ issues is daunting so we need to instigate a policy of not handling any support on GitHuib. I think we'll set up a public mailing list for this, update any links to point people there for support and then close any support issues with a message pointing ticket users to the mailing list.
 I imagine I'll have a bit of time to look at this before the end of the year. One thing that's missing (because we deleted it when it was open sourced because it was just reliable and incomplete) is a full and reliable test suite for testing key components. We would like to add this as a priority.
@willpower232 has been very helpful and I can't thank him enough for the help he's been to date.
Leave this with me for a bit and we'll see what we can do to help.

I'm fully aware that anyone can fork it and start merging things, but I'm afraid that might just split the community.

No, my idea is just not more than use some useful PRs and provide possibility for someone else to use it) I'm also planning to dockerize it normally with ansible

No, my idea is just not more than use some useful PRs and provide possibility for someone else to use it)

Hopefully we'll be able to get these merged soon once we've overcome the issue overload. I've already created the Google Group and I'll try and go through the issue list to find any legitimate issues which need attention vs those which are just support requests.

I'm also planning to dockerize it normally with ansible.

That'd be great! 👍

Thanks @adamcooke! We greatly appreciate your insight and I am very excited to hear that there are more things coming for Postal.
I know what you are looking to do is a ton of work, so please let us know what you need for help.

At the moment the 300+ issues is daunting so we need to instigate a policy of not handling any support on GitHuib. I think we'll set up a public mailing list for this, update any links to point people there for support and then close any support issues with a message pointing ticket users to the mailing list.

If I could just share my experience in helping open source projects, I would highly recommend using Github for support:

Github's support experience is STANDARDIZED for everyone. This makes it much easier for people to find issues and help others (especially with code sharing, screenshots, video, etc)
If it is easier for the community to support eachother, then this puts less demand on the founders
Everything for the project will continue to be in one place making it very easy for new members to onboard
People have the option to subscribe to the entire repository or to their specific issue (Github basically a mailing list already, with better features specifically for developers)
The founders don't have to maintain yet another product for mailing lists

Separating features from actual support issues can easily be done with tags. See the examples with our tags and our issue templates (click on "New Issue") on the project we worked on: https://github.com/521dimensions/amplitudejs/issues
I can help you organize and go through these 300+ issues if needed.
Moving forward
Please let us know if there is anything that we can do to help. If you have any requirements for core-contributors, I think there would be a handful of us that could help out.
Let us know what you are most comfortable with. Thanks again for all of your work!

I agree with @jaydrogers that having a separate forum / issue tracker could add some extra time to the core team, and I think it would be easier to have it all on Github. If the 300+ issues is really a problem, a good solution may be to have some community users triaging and tagging issues, so maintainers and core developers could focus on just selecting and resolving tasks.
By the way, I can offer some help with triage and tag if needed, because at work we have a Postal instance that I maintain.

Glad to see that this thread is getting a lot of people offering their help! This community is filled with a lot of great people and I am excited to see where this goes.
Over the weekend I had some further thought. Long story short, I think the first steps for Postal needs more structure to community than it does new features. I see this being broken down into two chunks:
Step 1 Goals: Organize the community

Create standards of issue labels/tags to use for organizing all action items
Create issue templates to automatically organize newly created issues
Develop requirements for people to apply as "core-contributors" to save @adamcooke and @catphish valuable time. Create this as documentation so future members can also easily participate
Develop a way to organize a roadmap (using something like Github Projects is sweet. We can even develop a way for people to "vote" on the feature within Github)
Organize, address, or close existing issues on Github

Step 2 Goals: Re-ignite the development process

Merge or address pending pull requests
After organizing a roadmap and getting community feedback, execute a small release to get Postal back on the right track

Ideally, if "Step 1" is complete, "Step 2" could be done through community members submitting PRs for the new features. The ultimate goal would be to put as much work as possible to the community.
This would allow the community to do the work of keeping "the ship" running, but still giving @catphish and @adamcooke the steering wheel to guide "the ship".
Just some quick thoughts I had. Just want to be clear that I am not telling you guys what to do, but just offering some suggestions that came to mind as I thought about it more.
Thanks again for everything that you guys do!

Just wanted to say thank you to @adamcooke, @catphish and @willpower232! The number of open issues have dropped by over 50% (150+ issues!) and there have been a number of PRs merged. Holy crap!
I've noticed the Github repo has been moved to a new organization as well (postalhq). It is very exciting to see these updates and know that Postal is far from dead.
Thanks for your hard work guys! Let us know if there is anything else that the rest of the community can help with.

:+1: if any of you happen to be experienced at ruby on rails with some time to kill, I think there are a fair few bugs (now labelled) without PRs to try your hand at.
I think the others are aiming to update the rails version and other dependencies at some point but there are definitely other bits worth investigating if nothing else.

@willpower232 has been great at getting the issues down to a sensible level and tagging things. We'll hopefully have a bit of time here to look at getting the more important things sorted soon.

Thanks for the update! If there is anything else that we can help as a community, please let us know.

I hate to be "that guy" to open this up again, but I am just curious to see where things are at. It was exciting to see things moving forward but it seems like momentum slowed down again (which is totally understandable).
I completely understand that this is an open-source project and life outside the computer is highest priority.
I am just looking for any sort of expectation of Postal's future or any method we as the community can help keep Postal growing. If there is anything that we can do to help, I am highly interested in volunteering (as I am sure others are too).
Any thoughts @adamcooke, @catphish, or @willpower232?

I am just looking for any sort of expectation of Postal's future or any method we as the community can help keep Postal growing.

Growing would be icing. Personally, I think it would be really good to merge a few bug fix PRs and get the dependencies up to date so Postal can keep running on updated OS versions.
Everything I host is now 100% dependent on Postal for SMTP. It would suck badly if it stopped working at some point by becoming incompatible with an internet that keeps moving forward.

I still can't make any promises for huge amounts of our time but I have, today, pushed some updates to key dependencies and also started work on some Docker images. Personally, I'm looking to get things running on Kubernetes (which I have mostly achieved) now so will hopefully document those bits soon.

I saw the commits earlier, holy crap! Thanks so much for the updates. It's very promising to see the dependencies get updated.
Is there anything that others can do to help merge some of the bug fixes?
Kubernetes is a great direction, but even getting some of the bugs fixed with a new version launched might be really helpful.
I feel like a lot of people are running their own customized versions of Postal until releases are officially launched.
I know your time is extremely valuable and just didn't know if you had a process in place for others to help review and squash bugs for you.

Sorting out some bugs would be great. The main problem is that we don't see the bugs ourselves (and we send millions of messages through our own Postal installs) so fixing them is always quite low priority.
Now I've got the app running on my machine, I may well find myself in a position to get some updates pushed out a bit more frequently.

@willpower232 will be the best resource on what bugs need to be resolved. He is extremely active on working with everyone on bugs.
Maybe @willpower232 could give you a list of priorities of bugs that can definitely be replicated?
Other ideas
Getting issue templates of what every bug needs might be helpful too. See Fastlane for example: https://github.com/fastlane/fastlane/issues/new/choose

Having stuff like this will:

Automatically organize every issue
Put emphasis on the user submitting an issue to submit as much detail as possible (to save a core-contributor as much time as possible fixing issues)

Disclaimer about me: I have no experience in Ruby coding, but I do enjoy organizing tasks and design (see one of my repos here: https://github.com/521dimensions/amplitudejs). I also have Sysadmin background (this is how I found Postal).
If you need any help getting stuff like this done, I have no issues volunteering some time as long as my changes get merged (and you find my work valuable). I don't want you to think that I would be stealing your project from you either. @willpower232 would basically be my "go-to" guy if you were not available.
Just some thoughts. Let me know what you think.

Sorting out some bugs would be great. The main problem is that we don't see the bugs ourselves (and we send millions of messages through our own Postal installs) so fixing them is always quite low priority.

Firstly, I feel I should echo this sentiment. Apart from the PRs I've made, we don't experience any issues so replicating problems is difficult when time allows.
I'm hoping to build on the Dockerfile with docker-compose to create an easily managed test environment which should help. I also don't know much Ruby but copy-paste-tweak has served me well so far!
I can see there are 30 open issues tagged bug and some of them have a PR already. Reviewing those would be handy to see if they can be solved with minor code changes and small PRs.
@jaydrogers a PR with one or more github issue templates would be lovely, I keep meaning to but don't get a chance. Basically with some standard tips for what to include would be lovely. Something along the lines of:

postal status output
netstat -lnp output
if they've restarted after changing config if relevant
how much email they're trying to send
etc

I don't have the ability to create tags but it might be worth adding topic-related tags like ui-related, has-pr, dns-related, queue-related, and so on. Then the other issues could be categorised a bit easier.
@adamcooke I'd also suggest pinning this issue and #755 to the issues page as they are probably the most useful. With all the dependencies up to date, the next major step is merging the PRs in where possible. I'm not sure how much of my initial comment is still relevant: https://github.com/postalhq/postal/issues/755#issuecomment-467020995

I don't know if a good news or not, from a Postal perspective:

Exciting news! We're delighted to announce that we've joined the
@KrystalHosting
family. Firstly, and most importantly, your service isn't changing and will continue to work as normal and our team is remaining exactly the same.

https://twitter.com/atechmedia/status/1240239030752686081?s=20

Wow, very interesting! Maybe @adamcooke could give some insight what that means for Postal?
Congrats on the sale guys, you guys definitely worked hard for it!

Krystal are also Postal users so nothing changes other than we may well have more resources to be able to work on it going forward. We've just opened the Krystal Open Source Slack channel which you're more than welcome to join to chat with me and the rest of the team here.
https://slack.k.io

Hey everyone,
my company uses Postal as well and we're eager to see it developed further or at least maintained (with relevant updates, such as the recent Rails update, and bugfixes) on a regular basis.
The thing that bothers me when reading through this thread is statements like this:

Sorting out some bugs would be great. The main problem is that we don't see the bugs ourselves (and we send millions of messages through our own Postal installs) so fixing them is always quite low priority.

Judging by its sheer number of stars and forks, Postal seems to be a very popular open source project, but at the same time it seems to be effectively unsupported by its creators – but not due to the fact that they've abandoned it but because of lack of reproducibility of issues. From what I can see, this stems mostly from Postal not being set up in a way that facilitates easy contributions (= easy to contribute for developers, easy to accept contributions for maintainers).
The biggest culprit here is (in my opinion) the lack of an automated test suite: If the project had a proper automated test suite, you wouldn't have to try to reproduce issues manually and check that a proposed fix actually fixes it – these steps are time consuming and prone to errors. Instead, you could check the tests and see if they make sense and are correct – and if everything looks good and the overall test suite passes as well (= the change didn't break any existing functionality), a contribution can be merged with (reasonable) confidence and (relatively) low effort.
Is there any reason why the project basically doesn't have a test suite? Is there anything preventing the setup of such a test suite? Would this be a contribution that would be accepted?
Apart from that, I echo the sentiment mentioned above (https://github.com/postalhq/postal/issues/917#issuecomment-585422782): Contribution guidelines, issue templates etc. could be tremendously helpful in facilitating contributions (both for contributors as well as maintainers).

Hey everyone,
my company uses Postal as well and we're eager to see it developed further or at least maintained (with relevant updates, such as the recent Rails update, and bugfixes) on a regular basis.
The thing that bothers me when reading through this thread is statements like this:

Sorting out some bugs would be great. The main problem is that we don't see the bugs ourselves (and we send millions of messages through our own Postal installs) so fixing them is always quite low priority.

Judging by its sheer number of stars and forks, Postal seems to be a very popular open source project, but at the same time it seems to be effectively unsupported by its creators – but not due to the fact that they've abandoned it but because of lack of reproducibility of issues. From what I can see, this stems mostly from Postal not being set up in a way that facilitates easy contributions (= easy to contribute for developers, easy to accept contributions for maintainers).
The biggest culprit here is (in my opinion) the lack of an automated test suite: If the project had a proper automated test suite, you wouldn't have to try to reproduce issues manually and check that a proposed fix actually fixes it – these steps are time consuming and prone to errors. Instead, you could check the tests and see if they make sense and are correct – and if everything looks good and the overall test suite passes as well (= the change didn't break any existing functionality), a contribution can be merged with (reasonable) confidence and (relatively) low effort.
Is there any reason why the project basically doesn't have a test suite? Is there anything preventing the setup of such a test suite? Would this be a contribution that would be accepted?
Apart from that, I echo the sentiment mentioned above (https://github.com/postalhq/postal/issues/917#issuecomment-585422782): Contribution guidelines, issue templates etc. could be tremendously helpful in facilitating contributions (both for contributors as well as maintainers).

Hello!
We started using Postal three years ago. It serves us very well and fills exactly our needs.
As Ubuntu 16 is sunset and I also wanted to relocate our Postal instance to another hoster, I tried to reinstall it from scratch with Ubuntu 20. It kind of works but it is a way full of papercuts as one has to dig through all those issues here and get all the pieces together to get it running.
It is very sad to see, that this project is kind of hung. @willpower232 is doing his best to help everybody around here, but I really would like to see this project actively maintained.
Is there anything we users can do, to get this up and running again? Is it a financial issue? We would sponsor it in any case as far this is possible for us and I can imagine that there are many other users that would do the same.
Please send a sign of life! Thanks!

For those not following it I want to point out that there is a sign of life in postal's slack channel 🥳

Just in case (cc: @jaydrogers @clemens),  to join the slack channel: connect/subscribe under https://slack.k.io and then join the #postal channel.

For those not on Slack, I just wanted to include that the conversation in Slack went stale as well. Hopefully the Krystal team will have time to update soon.

The number one thing that, at this point, would be hugely beneficial to the project would be to get a test suite in place - at least for the key components. Once that's sorted, we can confidently accept updates from a wider audience with less risk of things going wrong. If there is anyone in the community who can help with this, do let us know.
If anyone has any technical questions or needs any help getting started with working on the project itself, I'll always be happy to help on Slack. Just join and drop me a message. This, however, does not extend to question relating to installing or using the product - I'm afraid I don't have time to help with individual installs.
Right now, our team is busy working on other things which is why we haven't been able to do a huge amount on Postal. We do still love the product and do have the intention to spend some time on it but I don't have a solid date for that.

Right now, our team is busy working on other things which is why we haven't been able to do a huge amount on Postal. We do still love the product and do have the intention to spend some time on it but I don't have a solid date for that.

We totally understand. We're super grateful for everything that you've done for Postal. Open Source is amazing, but time is always the restriction. At the end of the day, family and friends come first.
From the lens of "what's best for Postal", unfortunately someone will need to spend a lot of time to get it updated. The security risks of running Postal in production are becoming uncomfortably high. If we put that requirement to be your time, then the problem Postal is facing is only going to get worse.
Is it possible for you to offload some responsibilities to other community members? It would be great to still have you involved at the capacity that you want to be, but also have other community members contribute and be able to update the product for you.
Forking the project would be a major setback too. It would divide the community and/or face an "uphill battle" since the new project would have to regain the traction that Postal already has.
@willpower232 has been an incredible asset for years on this project. Are you at least willing to give him the ability to merge PRs? @willpower232 is this something you're comfortable and interested in?
I am very interested in hearing both of your thoughts.

Whilst I can sort of understand ruby, I am by no means proficient enough in it to fully understand all the ramifications of a PR so I wouldn't have myself as first choice for merging PRs.
Also even if PRs are merged, the actual release process is internal to Krystal so we as a community cannot actually bring changes to what is probably the vast majority of Postal users.

Thanks for your honesty @willpower232! You're a great asset and glad to have you around.
I'm in the same boat... I don't understand much of Ruby, so I cannot be any help in that department either 😆
I could help in fixing this problem though:

the actual release process is internal to Krystal so we as a community cannot actually bring changes to what is probably the vast majority of Postal users.

We could use Github Actions to automate builds and deliver releases.
@adamcooke: What do you think? What's best for Postal moving forward?

Wait until you have more time?
Allow another Ruby developer who you are comfortable with for merging PRs and possibly adding features, tests, etc

Interested in hearing your thoughts.

Lot's of great updates are happening now! Excited to see the next chapter of Postal! 🎉


fix: add unique identifiers to tasks for accurate deletion

Summary
This pull request addresses an issue where tasks with the same text could not be accurately deleted due to the lack of unique identifiers. By assigning a unique id to each task, we ensure that tasks can be correctly identified and managed.
Changes Made

AddTaskBar Component: Modified to assign a unique id to each task using Date.now().
TaskList and TaskItem Components: Updated to handle tasks with unique ids, ensuring accurate deletion.
State Management: Updated the tasks state to be an array of objects, each containing an id and text.

Why This Change?
Previously, tasks were identified by their text value, leading to conflicts when tasks with the same text were added. This change ensures that each task has a unique identifier, allowing for accurate management and deletion of tasks.
How to Test

Add multiple tasks with the same text.
Delete tasks and verify that the correct task is removed.
Ensure that the task list updates correctly after deletion.

Related Issue
Fixes #61

Hey @pradeepkaswan :) I just saw Date.now() and If accurate and reliable timing is critical, performance.now() is the better choice 🚀

Thanks for the suggestion, @pivanov ! I have updated the timing function to use performance.now() for better accuracy. The changes have been pushed.


wrapper.emitted() does not work as expected with @vue/composition-api v1.1.0

wrapper.emitted() issue
When updated the deps to  @vue/composition-api v1.1.0, wrapper.emitted() method stopped working properly
Instead of emit object property, I started receiving hook:created, hook:mounted etc.

Can you research on this?

Which previous version of @vue/composition-api did you use? Could you provide a repo that demonstrates this case?

Sorry, my bad 😄
In my tests, I have checked wrapper.emitted() result to equal the expected stuff. The reason why my tests failed is that the commit above introduced the additional values included to wrapper.emitted() result:

I have adjusted the test:
expect(wrapper.emitted().submit).toEqual(...);

All worked properly
I am closing the issue 👍🏻


Make webnative includable via a file path

NB: Feature requests will only be considered if they solve a pain
Summary
This in package.json doesn't work:
{
  "dependencies": {
    "webnative": "../webnative"
  }
}

Problem
When importing webnative like that, files index.cjs.js, index.umd.js and index.es5.js aren't in the right place after a npm run build.
This is not a problem with the npm version, since npm publish is run inside the dist directory. (See the justfile scripts).
Impact
It's a little more difficult to develop for webnative.
Solution
Two options:

Inform the user that they have to run just build-and-clean and include webnative via ../webnative/dist, but I think this is unexpected and a little confusing
Change the package.json to refer to the index.*.js files as dist/index.*.js files and run npm publish from the root path (this breaks some users. E.g. in fission-suite/drive we'd need to change the build script to refer to a webnative/dist/index.cjs.js instead).

I assume we were publishing from within dist to not include any unwanted files. If we do option 2, we should include an .npmignore file.
:v:

You shouldn't need to need to refer to dist, I think. Normally build tools refer to the main, module and browser fields in package.json, depending on the context. But yes, you still need to run yarn build to build webnative first.
Also the correct syntax is:
{
  "dependencies": {
    "webnative": "file:../webnative"
  }
}

Yeah right. The value for that in package.json at the moment is this:
https://github.com/fission-suite/webnative/blob/7a23b8329f660c1582d88116d33f04dfec41c639/package.json#L11
But there's no index.cjs.js at that path after a yarn build.
It works via npm, because the package.json file gets copied into dist. Then the path works out. Also the npm publish is run inside the dist folder instead of at the project root.

Oh I see, yeah, that should be dist 👍
And then we add the other stuff to the NPM ignore list.
We should indeed not copy the package.json into dist.


Can we just use key 'SPACE' to use Peek? not combination shortcut key

Description of the new feature / enhancement
I hope the shortcut key for Peek can be set as a non-combination shortcut key, directly using key 'SPACE' to launch it, just like MacOS does.
Scenario when this would be used?
When we open the file explorer and use peek to preview files.
Supporting information
No response

/dup #26143


Add Net-A-Porter to list of companies using Fela

Description
We have been using Fela on our latest projects at Net-A-Porter. It's a relatively large application, so we are pretty happy with the results so far!
Changes
If one of the following checks doesn't make sense due to the type of PR, just check them.

[x] Documentation has been added/updated

Yey! Cool, thank you :)


python310Packages.neo4j: 5.9.0 -> 5.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.neo4j is: Neo4j Bolt Driver for Python
meta.homepage for python310Packages.neo4j is: https://github.com/neo4j/neo4j-python-driver
meta.changelog for python310Packages.neo4j is: https://github.com/neo4j/neo4j-python-driver/releases/tag/5.10.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.10.0 with grep in /nix/store/2cip9v47zsczs29d3340kg0i911fk1s8-python3.10-neo4j-5.10.0
found 5.10.0 in filename of file in /nix/store/2cip9v47zsczs29d3340kg0i911fk1s8-python3.10-neo4j-5.10.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
crackmapexec
python310Packages.langchain
python310Packages.neo4j
python311Packages.neo4j

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2cip9v47zsczs29d3340kg0i911fk1s8-python3.10-neo4j-5.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.neo4j https://github.com/r-ryantm/nixpkgs/archive/274f7b59e1a7f7235d6bf235552307dbeb5b7c3b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2cip9v47zsczs29d3340kg0i911fk1s8-python3.10-neo4j-5.10.0
ls -la /nix/store/2cip9v47zsczs29d3340kg0i911fk1s8-python3.10-neo4j-5.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

crackmapexec
python310Packages.langchain
python310Packages.neo4j
python311Packages.neo4j

Maintainer pings
cc @fabaff for testing.

Duplicate of #240746


When i run .\scripts\code-web.bat，some static resources cannot be found。

Which step went wrong？

help！！！ Do you have a handsome guy to help me solve this problem?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


AssetStrategy does not work with action_send intent handled by Gmail

On my Nexus 5 running KitKat 4.4.2.
The issues revolves around Gmail expecting a size, but the size returned is -1. Gmail seems to be treating it as an unsigned int/long, so I get the error that it can't attach files of 25MB. Adding the following to AssetStrategy seemed to get around that problem:
	@Override
	public long getLength(Uri uri) {
		AssetFileDescriptor afd;
		try {
			afd = appContext.getAssets().openFd(getFilename(uri));
		} catch (IOException e) {
			Logger.ex(e);
			return super.getLength(uri);
		}

		long size = afd.getLength();

		try {
			afd.close();
		} catch (IOException e) {
			Logger.ex(e);
		}

		if (size == 0) {
			return super.getLength(uri);
		} else {
			return size;
		}
	}

	// extracted for use elsewhere
	private String getFilename(Uri uri) {
		boolean isFirst=true;
		StringBuilder fullPathBuilder=new StringBuilder();

		if (path != null) {
		  fullPathBuilder.append(path);
		}

		List<String> segments=new ArrayList<String>(uri.getPathSegments());

		segments.remove(0); // get rid of first segment

		for (String segment : segments) {
		  if (isFirst) {
			isFirst=false;
			fullPathBuilder.append(segment);
		  }
		  else if (!"..".equals(segment)) {
			fullPathBuilder.append('/');
			fullPathBuilder.append(segment);
		  }
		}

		return fullPathBuilder.toString();
	}

Now I am seeing the following error over a dozen times as soon as I select Gmail from the list:
10-22 16:17:52.329  30392-31461/com.tophatter E/TransferOutThread﹕ Exception transferring file
    java.io.IOException: write failed: EPIPE (Broken pipe)
            at libcore.io.IoBridge.write(IoBridge.java:455)
            at java.io.FileOutputStream.write(FileOutputStream.java:187)
            at com.commonsware.cwac.provider.AbstractPipeStrategy$TransferOutThread.run(AbstractPipeStrategy.java:131)
     Caused by: libcore.io.ErrnoException: write failed: EPIPE (Broken pipe)
            at libcore.io.Posix.writeBytes(Native Method)
            at libcore.io.Posix.write(Posix.java:202)
            at libcore.io.BlockGuardOs.write(BlockGuardOs.java:197)
            at libcore.io.IoBridge.write(IoBridge.java:450)
            at java.io.FileOutputStream.write(FileOutputStream.java:187)
            at com.commonsware.cwac.provider.AbstractPipeStrategy$TransferOutThread.run(AbstractPipeStrategy.java:131)

Do you have any thoughts on the matter?

getLength() support was added for raw resources and assets in v0.2.3.


[Feature]: AsciiDoc like callouts support

What problem does this feature solve?
https://docs.asciidoctor.org/asciidoc/latest/verbatim/callouts/#callout-syntax
Currently, react-syntax-highlighter's APIs are not exposed fully.
What does the proposed API look like?

I was thinking to use shiki transformers, but it seems transformers will not be applied on plain text code blocks which I'd like to support at the same time.

I'll try to add a custom shiki transformer first.


Domains with subdomain (local and remote)

Your code is not working with our system because we have a subdomain before localhost
Our URL: http://<subdomain>.localhost:4201/
Can you change the line in index.js: 20 to the following please:
urlReplacer = (url) => url.replace(/http:\/\/.*localhost:\d+/, absPath);
Finally our goal is a nightly test run in an Azure pipeline. The URL will be:
https://<subdomain>.<domain>/
Is this possible with your package?

TIL *.localhost is resolved to localhost.
I found .*localhost to be too permissive because it'd match whateverlocalhost, so instead of .* I used (.+\.)? (requires a dot between subdomain and localhost if subdomain is specified).
Available in version 0.3.0

Thank you for your fast response. Finally the tool generated json coverage data within the tmp folder if I use localhosturl with my local running service. A generation on the remote server is still not possible because of the  url matching.
The output is generated code with a lot of webpack content. C8 can not understand the content:

{
  "result": [
    {
      "url": "<path>/<filename>.js",
      "scriptId": "15",
      "source": "\"use strict\";\n(self[\"webpackChunktts_ui_angular_flow\"] = self[\"webpackChunktts_ui_angular_flow\"] || []).push([[\"projects_tts-ui-angular-flow-candidates_src_public-api_ts\"],{\n\n/***/ 80663:\n/*!***********************************************************************************!*\\\n  !*** ./projects/tts-ui-angular-flow-candidates/src/lib/constants/empty-filter.ts ***!\n  \\***********************************************************************************/\n/***/ ((__unused_webpack_module, __webpack_exports__, __webpack_require__) => {\n\n__webpack_require__.r(__webpack_exports__);\n/* harmony export */ __webpack_require__.d(__webpack_exports__, {\n/* harmony export */   emptyFilter: () => (/* binding */ emptyFilter)\n/* harmony export */ });\n/* harmony import */ var _flow_shared__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! @flow/shared */ 6606);\n\nconst emptyFilter = {\n  appliedFromFilter: '',\n  appliedUntilFilter: '',\n  channelIdFilter: _flow_shared__WEBPACK_IMPORTED_MODULE_0__.AdditionalFilterOption.All,\n  cityFilter: '',\n  communicationStatusIdFilter:
[...]

The output of C8 is empty (nothing covered). Have you an idea how to link/resolve the data?
Current config:
  projects: [
    {
      name: 'chromium',
      use: {
        ...devices['Desktop Chrome'],
        coverageDir: './coverage/tmp',
        coverageSrc: './projects',
        coverageSourceMapHandler: 'localhosturl'
      }
    },


Cannot find 'swaggerFileName' during generate

I'm running version 3.1.3 of swagger-maven-plugin and I'm trying to set the filename using the swaggerFileName parameter. I get the following error message when running maven install:
 [ERROR] Failed to execute goal com.github.kongchen:swagger-maven-plugin:3.1.3:generate (default) on project GridPackage-app: Unable to parse configuration of mojo com.github.kongchen:swagger-maven-plugin:3.1.3:generate for parameter swaggerFileName: Cannot find 'swaggerFileName' in class com.github.kongchen.swagger.docgen.mavenplugin.ApiSource -> [Help 1]

@danjo830 Try removing the swaggerFileName node from your pom. The readme.md is currently reflecting the state of 3.1.4-SNAPSHOT, and swaggerFileName was added in 3.1.4-SNAPSHOT.

Thanks, it works without the property in the pom. I didn't realize there was a newer version available.

Where can I get the 3.1.4-SNAPSHOT? I need a possibility to modify the output file name to sore the result for different api sources in seperate files.

I need this feature too and the 3.1.4-SNAPSHOT is not available via the mentioned repo.
Can someone push the snapshot to repo?

@kongchen is the only one with the permissions to push snapshots and releases. I only have commit access.
@kongchen would you please update the snapshot ? Thanks!

Yes, please do it. I am waiting for this new attribute to be available. Thanks in advance!

@kongchen can you please provide snapshot or may be new release. thx

any update on this? I'm still getting this error. Have we added support for "swaggerFileName" ? I'm using version 3.1.2

Any update on this issue?

Sorry my bad, I found 3.1.4 in Maven Central.


Intermittently AWS EC2 agents fail to register with Buildkite

Upon inspection of the services and logs, it appears that calls to the instance metadata service have failed (empty response), causing cloud-final.service to fail and leave the instance running but it's not connected to Buildkite. We have had other similar issues where obtaining the metadata randomly (and again rarely) fails after the agent has registered and it's running a build (during the pre-command script).
According to AWS docs (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-throttling), there is throttling at an instance level, but I fail too see how we would be hitting any limits. We only make a small number of calls to the metadata service per instance.
May be worth increasing the timeouts and retries in the agent?

@liam-bailey, I'm pretty sure this is https://github.com/buildkite/elastic-ci-stack-for-aws/issues/572 and not strictly a problem with the agent itself.

Yup, agree, think it's that issue. Going to close this one out.


Cabal derivations with editedCabalFile field are broken by new hackage metadata revisions

The problem
Here's my compiler output:
setupCompileFlags: -package-db=/tmp/nix-build-haskell-intervals-0.7.1.drv-0/package.conf.d -j1
[1 of 1] Compiling Main             ( Setup.lhs, /tmp/nix-build-haskell-prelude-extras-0.4.drv-0/Main.o )
[1 of 1] Compiling Main             ( Setup.hs, /tmp/nix-build-haskell-parallel-<IP_ADDRESS>.drv-0/Main.o )
Linking Setup ...
Linking Setup ...
[1 of 1] Compiling Main             ( Setup.lhs, /tmp/nix-build-haskell-intervals-0.7.1.drv-0/Main.o )

trying http://hackage.haskell.org/package/lens-4.7/lens.cabal
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14484    0 14484    0     0  75285      0 --:--:-- --:--:-- --:--:-- 97864
output path ‘/nix/store/jajagqi8sq7rgz2qdlijkgln0mvzc1y6-lens.cabal’ should have sha256 hash ‘0xaprn01zc22h6lgipdifb0r5s7dkc3rpffhrmpj4j6kkixx74d9’, instead has ‘1cbw7p9daamg5c8y98lwgi25dqxxkgj1jgd2m8h81p2lq743dx5v’
building path(s) ‘/nix/store/rmbi6iadjz398lva4ic7hv7vdwbf71is-gtk2hs-buildtools-<IP_ADDRESS>’
cannot build derivation ‘/nix/store/swbs9vxibspsbaic2nkxxg3rfmjiv39k-haskell-lens-4.7.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/gcji0idq19pc2jp76lgfnjxrdfyqk2n7-profunctors-4.4.1.tar.gz’
building path(s) ‘/nix/store/6v97xx2pgv7h0rj905hgp58havhgilmw-reflection-<IP_ADDRESS>.tar.gz’
building path(s) ‘/nix/store/3r3r60cgybrhphcfnqfiv2f9lcm4q9ca-semigroupoids-4.3.tar.gz’
cannot build derivation ‘/nix/store/fsdcmcbgvsq7adb0x9jw6iwg2v6s0pni-ghc-7.8.4.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/wcv6y6sn6ghv8pz1y25pfxd7abg19n38-haskell-diagrams-builder-<IP_ADDRESS>.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/6wkq86x8wm2zv26zdqkb6rjwhk35s70b-diagrams-builder.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/ni48c7va6kwj37gz7dcbzr6aibm0jj1f-myEnv.drv’: 1 dependencies couldn't be built

Note the mention: trying http://hackage.haskell.org/package/lens-4.7/lens.cabal
which according to the output resulted in SHA: 1cbw7p9daamg5c8y98lwgi25dqxxkgj1jgd2m8h81p2lq743dx5v
but should have given:
‘0xaprn01zc22h6lgipdifb0r5s7dkc3rpffhrmpj4j6kkixx74d9’
Some supplementary analysis results
Here we see that the actual value has been properly calculated:
> $ nix-prefetch-url http://hackage.haskell.org/package/lens-4.7/lens.cabal
...
1cbw7p9daamg5c8y98lwgi25dqxxkgj1jgd2m8h81p2lq743dx5v

And that it maps to the fifth metadata revision:
> $ nix-prefetch-url http://hackage.haskell.org/package/lens-4.7/revision/5.cabal;
...
1cbw7p9daamg5c8y98lwgi25dqxxkgj1jgd2m8h81p2lq743dx5v

Which you can explore here: http://hackage.haskell.org/package/lens-4.7/revisions/.
Now, performing some supplementary queries, we can see that the
expected SHA maps to the first metadata revision.
> $ nix-prefetch-url http://hackage.haskell.org/package/lens-4.7/revision/1.cabal;
...
0xaprn01zc22h6lgipdifb0r5s7dkc3rpffhrmpj4j6kkixx74d9

Here's the package expressions:
  "lens" = callPackage
    ({ mkDerivation, array, base, bifunctors, bytestring, comonad
     , containers, contravariant, deepseq, directory, distributive
     , doctest, exceptions, filepath, free, generic-deriving, ghc-prim
     , hashable, hlint, HUnit, mtl, nats, parallel, primitive
     , profunctors, QuickCheck, reflection, semigroupoids, semigroups
     , simple-reflect, split, tagged, template-haskell, test-framework
     , test-framework-hunit, test-framework-quickcheck2
     , test-framework-th, text, transformers, transformers-compat
     , unordered-containers, vector, void
     }:
     mkDerivation {
       pname = "lens";
       version = "4.7";
       sha256 = "1z2ydc90m0cq76yamdaws4677lpi476f9z25xrz8r7y5kxh2aq4s";
       editedCabalFile = "a991d37b9cd348226fcdd0b99b079bede892c172b1ddf8a88142b01f80cd5775";
       buildDepends = [
         array base bifunctors bytestring comonad containers contravariant
         distributive exceptions filepath free ghc-prim hashable mtl
         parallel primitive profunctors reflection semigroupoids semigroups
         split tagged template-haskell text transformers transformers-compat
         unordered-containers vector void
       ];
       testDepends = [
         base bytestring containers deepseq directory doctest filepath
         generic-deriving hlint HUnit mtl nats parallel QuickCheck
         semigroups simple-reflect split test-framework test-framework-hunit
         test-framework-quickcheck2 test-framework-th text transformers
         unordered-containers vector
       ];
       homepage = "http://github.com/ekmett/lens/";
       description = "Lenses, Folds and Traversals";
       license = stdenv.lib.licenses.bsd3;
     }) {};

Whose editedCabal file I can match with:
> $ curl http://hackage.haskell.org/package/lens-4.7/revision/1.cabal | sha256sum
...
a991d37b9cd348226fcdd0b99b079bede892c172b1ddf8a88142b01f80cd5775

My understanding
I had a cabal nix expression that I could build at some point in time, but now
some time later (such as this case), the package maintainer decides to
update the package's metadata for some reason. Now, I cannot build
my nix expression.
I seem to me that it defeats the purpose of nix / having repeatable
builds.
It seem reasonable to think that we should use the full url to the
specific cabal file revision at the point of generating the expression
(e.g.: http://hackage.haskell.org/package/lens-4.7/revision/1.cabal)
instead of the url to the current revision of the file
(e.g.: http://hackage.haskell.org/package/lens-4.7/lens.cabal).
That would imply adding a revision field alongside or within editedCabalFile
field.
Now I understand that retrieving the revision would have to be automated
if not already as part of hackage2nix.
Meanwhile
Is there any quick fix in the meantime so that I can get my build running
again?
Update
As a quick fix suggested in 5920#issuecomment-71218347, I used the following command to
find a new value for the editedCabalFile:
curl http://hackage.haskell.org/package/lens-4.7/revision/5.cabal | sha256sum
...
bbf436c8c154dc8020aaa23d19e49bbde356447c9ca2e4112baf2ad5d23d7cb1

Found the code snipped that would have to be adapted:
              ${let newCabalFile = fetchurl {
                      url = "http://hackage.haskell.org/package/${self.fname}/${self.pname}.cabal";
                      sha256 = self.editedCabalFile;
                    };
                in
                  optionalString (self.editedCabalFile or "" != "") ''
                    echo "Replace Cabal file with edited version ${newCabalFile}."
                    cp ${newCabalFile} ${self.pname}.cabal
                  ''
              }${optionalString self.jailbreak "${jailbreakCabal}/bin/jailbreak-cabal ${self.pname}.cabal"}

in https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/cabal/default.nix#L249

Also found my answer for the meanwhile sections as part of:
5920#issuecomment-71218347

I had a quick glance at hackage2nix / cabal2nix source code and it seems it is pretty much ready
for this.
fetchOrFromDB would have to take into account the optional revision already present in Source
(sourceRevision) to generate the url.
Derivation returned by cabal2nix also already have the revision field.
Now, there would be generatePackageSet's following snippet to adapt so that
it tries to find the latest revision and then always fetches it by revision:
descr = hackage Map.! name Map.! pkgversion

and then, update Derivation.revision with it.
And at the very end, ensure the revision field gets printed in:
return $ nest 2 $ hang (string attr <+> equals <+> text "callPackage") 2 (parens (pPrint drv)) <+> (braces overrides <> semi)

This is a duplicate of https://github.com/NixOS/nixpkgs/issues/6914.

Arhgg, I was looking at the wrong cabal builder on git hub repo... Good job for the fix.
Now however this old haskellPackages, surrounding tools and individual packages of
are become really irrelevant and a serious pitfall to people trying to understand what's
occurring with their haskellngPackages / haskellngPackages builds. This is even more
the case, now that   nixpkgs/pkgs/build-support/cabal/default.nix has been proven
broken and still contains broken code.
I think it has become the time to do one of 2 things:

Completely remove all this old broken stuff.
In all these broken files, add a big noticeable comment specifying
that this is deprecated and possibly broken, specify what is the
proper alternative file that does the job now (specifying the distinction between
haskellng and haskellOld and add a reference to the procedure
how to migrate from one to this other maybe adding some
convincing points as to why migrate such as this issue). A link to
such reference would do:
http://lists.science.uu.nl/pipermail/nix-dev/2015-January/015591.html, a
wiki entry would be even better.

Please see https://github.com/NixOS/nixpkgs/pull/7465.

Thanks.


V2 Addon conversion prep: convert to single-package monorepo.

Context, Plan, etc: https://gist.github.com/NullVoxPopuli/eafc7dad6547de5e730098498b829e1f

updated

ok, let's give this a go and see how it works out.


Undefined name InfiniteType

InfiniteType doesn't exist:
https://github.com/sdiehl/numpile/blob/73c0dad97ebce73c0c370b890d8188cffc3b43d4/numpile.py#L370
@sdiehl - Should this be change to raise TypeError?
Or something else?

Yes, it should be a custom instance of Exception.


[Feat]: Adding a sliding feature with 3 pictures in the home page complementing the text and background color

I would like to add a feature of sliding multiple images that would complement the text written on it and also the background
that would enhance the look of the page.

@vivekvardhan2810  if u find this feature useful kindly assign it to me under hacktoberfest and GSSOC.

@shreyabajaj12 pls complete the issue assigned you before.

@shreyabajaj12 for now we don't require this, we will look into this later, so i am closing this issue.


German translation

@rhtyd @svenvogel
Add new translations for German-based on en.json

@svenvogel Can you help me?

@svenvogel @utchoang @onitake I'm happy to merge this as soon as we've consensus.

@onitake yes but this are additions and we are orientate us on the old one. i dont see so much incorrect wording or clunky things. if the api would more speaking and the english one more a reference it would be easier.

@rhtyd Agree. we will go through the file 😄 ---- faaaast

@svenvogel @onitake @utchoang is this ready for merging?

@rhtyd No. We need @onitake  to confirm comments of @svenvogel for the update German translation file.

@onitake some news?
@utchoang @rhtyd let’s wait one more days. If there come no feedback we go with the best we know and change the rest later. Sound this ok?

Ping @onitake @svenvogel @utchoang

@svenvogel Do you think you need to change something more?

@utchoang after changes i think we should go with this PR and fine tune things later if we find some inaccuracy. CC @rhtyd

Okay @svenvogel I'll merge this PR based on your feedback


Move the add peer button to top

Move the Add Peer button to the top, otherwise it is a game of whackamole when peers are being added and removed while trying to click the button

That's done as part of the redesign


discussion: recommended way to authenticate requests

Hola! Mad props to your mad science! 🙌 . Thank you for this. So clean, well structured. I've read the WP GraphQL docs on authenticating requests. I wondered if you have a recommendation or pattern you'd suggest to authentication from the front-end to the WP backend? Hope this doesn't come off as lazy AF but rather a request for expert insights, not re-inventing the wheel for a newbie. Thanks for the consideration.

Great question!
This repo just uses the WP REST API which supports basic auth — https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/
The requests on this app actually don't even require authentication since they are read only. Surprisingly even most big content sites using Wordpress don't protect their WP REST endpoint for reading content.
A few examples of this are Wired magazine or TechCrunch. If you go to either site and append /wp-json/wp/v2/posts to the URL, you will get all of their posts back as JSON. You can even configure your next-wp site to literally just pull content from one of these publications.

We opted to not use GraphQL in this project. We didn't see it as a huge need for a simple headless site. If we were to use WP more as an application backend, it would probably be great to add support for GraphQL to it so that it has greater flexibility

I also failed to mention this in the previous comment, but since we're generating the pages statically, content only pulls from WP when the site builds. The load on the WP backend is pretty light since we're not always hitting it to serve content

Make sure as well to disable the WordPress front end and make sure that your Wordpress is non indexable. Your endpoint will be added via ENV and then the posts/authors/categories all will be statically generated.

Thank you @youngbloodcyb and @brijr! Epic release, so helpful. Sorry for dropping off the face of the earth after your thoughtful comments and guidance. Much appreciated!


avoid missing metrics

many of the metrics, for example http_requests_total, are not showing up until the first request is received, this goes against prometheus best practices https://prometheus.io/docs/practices/instrumentation/#avoid-missing-metrics

Hey @alfaro28, you are raising a valid point. I've run into this problem myself a few times. What I'm doing atm is just writing a custom metrics closure like in metrics.py that also initializes all my metrics. I think I could bring that into the package itself by adding an optional parameter to the metric functions that accepts the FastAPI app. Then every metric function could decide on it's own if and how it wants to init stuff.
But this solution will never cover all corner cases without custom "metric functions" (I really should find a better name for these functions that take a few settings and return a function that actually performs stuff like incrementing metrics). The reason is that only after the first request it is known if the status codes are grouped or ungrouped for example. So in the case of the default instrumentation you can actually not initialize anything, because everything is configurable.
I guess this is a big disadvantage of the approach in this package. The gathering and preprocessing of information (what is the handler? what is the status? etc) is completely separated from the actual instrumentation.

I managed to workaround this issue by manually sending a request when initializing my app, I guess is not such a big deal but I just wanted to bring it up

@alfaro28 if you want to be 100 % exact your solution still does not cover the recommendation completely:

Time series that are not present until something happens are difficult to deal with

In Prometheus you must make a distinction between a metric and time series. A metrc is something like requests_total. In this example you have one (1) metric. And it can contain multiple time series:
requests_total{handler="/". status="302"}
requests_total{handler="/". status="400"}
requests_total{handler="/foo{item_id}". status="500"}

So you would have to initialize ALL possible combinations, because technically every new value leads to a new separate time series. Though in real life it is often enough to approximate it like you did by just initializing a subset of all time series.
Transferred to this project this means that we can also only cover a subset. For example all time series only containing the metric name.

I'm experiencing an issue that might be related to this. Whenever I add a new metric into the instrumentator, I lose some of the "default" metrics that come with this package (that is, the ones I see when I'm not registering any custom metric).
This is the difference. Any ideas why?

@lucasalvarezlacasa how are you adding the metric? Can you share some code?


Overlays are closed differently based on their type

Some of the overlays such as the ones for commenting and adding hotspots can be closed by clicking around the window or ESC, but the ones with the X on the top right corner can not be closed with the ESC key.

Added esc key shortcut support for the popups - 88d18d146fb507ffb5ead0ee5b3b0d9f8df18344.


Improve user experience for Chinese phone numbers

SMS providers (Twilio/Nexmo/MB) do not allow sending SMS to Chinese phone numbers due to regulations. As such our verifications success rate is 0% from China. We should provide a message to users that are using China as the phone number country code letting them know in advanced that it's not supported and preventing continuation.

Should block for all our unsupported regions: CU,SY,KP,IR,SD,CN (list may be longer now) but China is the most pressing since we see an average amount of traffic coming from there (compared to all other countries)


⚠ pnpm has degraded performance

In 1bfd828, pnpm (https://icetrust_dashboard.nightwatchcybersecurity.com/data/output/pnpm.json) experienced degraded performance:

HTTP code: 200
Response time: 20 ms

Resolved: pnpm performance has improved in d94f201.


keystone store service cert

这个 PR 实现什么功能/修复什么问题:
keystone 支持保存cert

是否需要 backport 到之前的 release 分支:
release/3.2.0
/area region keystone
/cc @yousong @zexi @swordqiu

/hold
还需要绑定endpoint和cert关系

/hold cancel

Codecov Report

Merging #5879 into master will increase coverage by 0.00%.
The diff coverage is 5.55%.

@@           Coverage Diff            @@
##           master    #5879    +/-   ##
========================================
  Coverage    6.95%    6.95%
========================================
  Files         641      643     +2
  Lines      109916   110042   +126
========================================
+ Hits         7642     7651     +9
- Misses     101688   101805   +117
  Partials      586      586

Flag
Coverage Δ

#aFlag
6.95% <5.55%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/validators/validators_cert.go
0.00% <0.00%> (ø)

pkg/compute/models/loadbalancercertificates.go
4.76% <0.00%> (+0.70%)
:arrow_up:

pkg/keystone/models/endpoints.go
3.47% <0.00%> (-0.44%)
:arrow_down:

pkg/mcclient/options/servicecertificates.go
0.00% <0.00%> (ø)

pkg/keystone/models/servicecertificates.go
14.51% <14.51%> (ø)

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 d9575b2...d9bec7c. Read the comment docs.

/lgtm

/lgtm


DAPI-88 Improvements/Changes in Interventions-CommunityApi request and responses as a result of E2E Integration

What does this pull request do?
After completing the end to end integration between Interventions and Delius UI (via community-api and delius-api) a number of improvements and changes were identified in order to have a working integration. These comprise:

Provide offsets with dates and times so that appointments and referrals can be exchanged correctly with Delius
Provide integration context (applicable config) in all requests
Use UUIDs over long text to identify reference data (i.e. service category)

What is the intent behind these changes?
To achieve a working integration between new Interventions Service and the existing Case Management System Delius.

This PR is being withdrawn as Delius-api is being changed to provide dates and times as OffSetDateTimes. This means there will be no ambiguity about what they represent and is in line with MoJ standards. Once done, this PR will be redone.


Not creating another domain.

Hello,
I am currently having the issue where it will not detect a new domain name. It's only reading the very first line of proxydomains. Any suggestions to resolve this?
if nshield_proxy is 1 and dryrun is 0:
	print "Setting up nShield proxy for domains found in /etc/nshield/proxydomains\n"
        # Generates nginx proxy_pass from /etc/nshield/proxydomains and checks if already present in nginx conf
        with open("/etc/nshield/proxydomains") as f:
                content = f.readlines()
                content1 = content[0].split(' ')
                ip = content1[1].strip('\n')
                domain = content1[0]
                if domain not in os.popen("cat /etc/nginx/sites-enabled/dynamic-vhost.conf").read():
                    print "I Will generate proxy configuration for site "+domain+" on IP: "+ip
                    os.popen("""echo 'server {
        listen 80;

        root /var/www/html;
        index index.html index.htm index.nginx-debian.html;

        server_name """+domain+""";

        location / {
    proxy_pass       http://"""+ip+""";
    proxy_set_header Host      $host;
    proxy_set_header X-Real-IP $remote_addr;
}
}
' >> /etc/nginx/sites-enabled/dynamic-vhost.conf""")
                    os.popen('service nginx restart')
                else:
                    print "Domain already configured"

        print "Now you can test that your site is reachable via nShield proxy by changing the domain DNS or via your PC hosts file or directly DNS A record"

Kind Regards,
Jack K-B

Hello Jack,
I fixed the code and now the proxydomain configuration is working with multiple domains
commit link
Sami

Hello Sami,
That's perfect, thank you very much for resolving this issue for me!
Kind Regards,
Jack K-B

Hello,
I'm sorry for re-opening this issue but upon executing the 'python nshield-main.py' command, I'm receiving this error http://prntscr.com/gz44pn - The file does exist and I've checked it's in the correct path.
Kind Regards,
Jack K-B

Hello,
The error is most likely from the variable not a str, now i have added the str() conversion

Hello,
That's perfect thank you. I've just executed git pull and it's now showing the error http://prntscr.com/h2bv4k
Kind Regards,
Jack K-B

Hello,
Could you remove the /home/nShield/ folder  and run again:
cd /home/ && git clone https://github.com/fnzv/nShield.git && bash nShield/install.sh
?
From my ubuntu 16 image works without issues

Hello,
Thank you for replying. I've done as you said and it ran without issues upon default settings. As soon as I turned the variable 'nshield_proxy' to '1'. It's showing the same error as the above.
The machine that I'm receiving this error on is 'Ubuntu 16.04.3 LTS'.
Kind Regards,
Jack K-B.

Hello,
Sorry for the late reply, here is the fix: commit 5af9a02eb63a00f18ec25cc98de4b8f5ff0ef611


400 Bad Request when file has around 100 lines of code

Is there a way to configure the max lines/tokens or other configuration to fix the 400 I am getting on medium size files? I have tried increasing/decreasing the max lines and max tokens in the extension settings but that did not work. This happens with different model choices. I have restarted vscode between changes.
Issue Description
When the source file or java unit test file grows to 120 lines or so of code, my 200 OK become 400 Bad Request
fauxpilot-copilot_proxy-1  | INFO:     2023-06-13 19:50:41,149 :: <IP_ADDRESS>:55171 - "POST /v1/engines/codegen/completions HTTP/1.1" 200 OK
fauxpilot-copilot_proxy-1  | 1
fauxpilot-copilot_proxy-1  | INFO:     2023-06-13 19:51:02,653 :: <IP_ADDRESS>:55176 - "POST /v1/engines/codegen/completions HTTP/1.1" 400 Bad Request

Expected Result
200 Ok with response
How to Reproduce

When src or test file grows to 150 lines
See error: "POST /v1/engines/codegen/completions HTTP/1.1" 400 Bad Request

Update: It is not the lines of code. I am now getting it with a small hello world python app. It starts out working and then soon after a few lines of code I start getting the 400 bad request. It happens with any of the multi-lang models from hugging face.

It turns out the model I am using has a max token limit of 2048 and my code around line 100 was exceeding that limit.


Adjust imports in aqc plugin to avoid discovery overhead

Summary
This commit tweaks the imports for the aqc plugin to make the optimizer
and other aqc method imports occur at run time only. Previously these
were done at the module level, which is normally best practice for many
reasons, but in this specific case doing plugin discovery causes the
module to be loaded (and the plugin class instaniated) even if the
plugin is not specified by the user. The imports for aqc are fairly
heavy as both the algorithms tree and scipy can be slow to load. To
avoid the overhead on discovery these imports are moved to runtime so we
only load them if the aqc plugin is used and these imports are needed.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.008%) to 82.849%

Files with Coverage Reduction
New Missed Lines
%

qiskit/extensions/quantum_initializer/uc.py
2
88.65%

qiskit/pulse/library/waveform.py
3
89.36%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
50142

Relevant Lines:
60522

💛  - Coveralls


[Accordion Menu] text over opne/close icon

think about adding in:
.accordion-title {
padding-right: 2.5rem;
}
How to reproduce this bug:
add long text in .accordion-title
What should happen:
text dont cover +/- button
What happened instead:
text cover +/- button
Browser(s) and Device(s) tested on:
FF, chrome, opera
Foundation Version(s) you are using:
6.4.2

I think this needs to be handled on a case by case basis. The exact side of the margin will depend on how large the icon is. We'll think of better ways to implement this in F7.


Removed warning when building in release mode

Related with the comment https://github.com/ros2/rviz/pull/1049#issuecomment-1708186981

This looks good to me with green CI, thanks for iterating!

Oh, we should also run a job using https://ci.ros2.org/job/ci_packaging_linux/ , just to confirm that the problem is fixed when building in Release mode.

This looks good to me with green CI, thanks for iterating!

Oh, we should also run a job using https://ci.ros2.org/job/ci_packaging_linux/ , just to confirm that the problem is fixed when building in Release mode.

@clalancette should I run up-to this package ? or I should run the same job ?

@clalancette should I run up-to this package ? or I should run the same job ?

I think up-to is sufficient; there really isn't much above this (only rviz2 itself), and it doesn't have any particular tests for this.

@clalancette can you check that I launched the build properly ?

That job looks good to me.  Here is full regular CI to make sure there are no other problems:

Linux
Linux-aarch64
Windows

All right, this is looking good.  Going ahead and merging, thanks for the fix @ahcorde !

@clalancette is this warning also relevant in humble and iron ?

@clalancette is this warning also relevant in humble and iron ?

Yeah, we'll have similar warnings when running the packaging jobs for them.  Also, this should further increase the performance.  So I think we should backport it.

https://github.com/Mergifyio backport humble iron


Fix test suite and update project to work with Swift 2.1 / Xcode 7.2

Currently blocked by "FBSnapshotTestCase" not building on 7.2 — "Use of private header from outside its module" for all imports of private headers in implementation (!) files.

Fixed by 1a2c4fb034da78e8d13f204792038c77fb4ff26b


Error getting Manifest

Hi,
I cannot play any streams, always getting the same "Error getting Manifest" and then "Could not open / parse mpdURL"
General infomration
rpi3 running on debian stretch OSMC, Kodi 18
Debug log
https://gist.github.com/laclaro/2d10327b82e97b8ef3f9ea5688f2405c
Best,
Henning

Installing the fork of CastagnaIT Version v0.14.6 worked for me. Since this very repo by asciidisco as well as the one by CastagnaIT have recent changes, I don't know which one is the most advanced. Please join your efforts!
Best,
Henning

Leaving this open to be found by people.


fix(frontend): #182

The issue: #182
During startup, enable text field, but disable submit
The current behavior of the application prevents users from typing their prompts while waiting for the initialization process to complete. This hampers the ideal user experience, especially in cases where the initialization phase takes some time.
So the fix ensures that users can type their prompts while the application is initializing, allowing them to be ready to submit their input once the initialization process is complete.

I think that's a lint issue

@maruf-rahman007 looks like you need to fix the lint issues

Looks like this is fixed now. Thanks!


Operational Metrics for SuperSet

Problem
I have installed SuperSet for some of our querying and visualizing needs. However, sometimes queries take longer than expected time to execute. Once the application is installed and running in a production, it is very vital to get operational insights for the application's performance. This kind of metrics is missing in SuperSet.
I am leveraging Apache SuperSet to enable stakeholders / users to query data from various pre-configured data sources.
As a product owner, I would like to get insights on:

Query metrics such as query/count, query/success/count, query/failed/count, query/interrupted/count, query/timeout/count, user, execution_time etc.
Number of queries ran over time (e.g. how many queries ran in the past hour / day etc)

Describe the solution you'd like
There should be a way to expose the operational metrics for a metrics server to use as a part of the API specification available here. So potentially an API endpoint like /api/v1/metrics that can have all the operational metrics in TSDB format.
Having this type of insights via Apache SuperSet seems to be missing.
Additional context
Please let me know if there is any way community is deriving these insights at the moment from Apache SuperSet?

Superset currently has a log event emitter, where user events are published. By default these events are sent to the metadata db in the logs table


Move Configuration files to the top level

At the moment the configuration files are scattered throughout the project. We should consolidate and simplify. This includes the jekyll configs, gruntfiles, gemfiles, and NPM json. The GAE config could probably stay where it is, but it might be nice to pull it up and have it copied over as part of the build.
cc @wibblymat FYI.

Closed by #1060


CLI: Remove unneeded translation functions

Could someone double-check me on my logic?
I don't think translations get processed in the context of WP CLI (meaning docs or function messages get returned translated) but I could be wrong.
Proposed changes:

Removes translation functions from CLI commands.
Updates parameter docs for $args params.

Yoast-SEO seems to use translations, but most others don't: https://github.com/search?q=WP_CLI%3A%3Asuccess&type=code

The text seems to be translated (except the special-chars 🫣)...

So the questions might be more like: do we want that? even more because it seems to be the only translated text!?!

Interesting! Good to know

So the questions might be more like: do we want that? even more because it seems to be the only translated text!?!

Up to you, I don't have a strong opinion

I just wanted to write the same... I have no strong feelings on that one and am happy to remove them!

you already remove the one from the description, so let's be consistent!


@Query annotation to support query limiting

This will allow you to limit the results returned from a DynamoDB query that has a sort and range key, techincally also a Scan.  I developed this to reduce cost b ased on the new OnDemand pricing.
Example:
@Query(limit = "10")
List<Blah> findFirst10ByStatusAndDateTimeBeforeOrderByDateTimeDesc(String Status, String DateTime);

The previous behavior would actually return every single result and then clip it.  With this limit parameter dynamo only returns the request amount of results.  This is mainly for HashAndRange.  It still requires First10 and the Query annotation to work otherwise the Spring-DynamoDB will just do queries limited to 10 results until it gets them all.

Thank you so much.
Merged via #239


Query Editor: Clear Property field when the asset changes

What happened:
When we have property selected in the editor and we change the asset, property name becomes the ID instead of just being cleared. This means that if we submit this query, we will get "failed to fetch query data: ResourceNotFoundException: Property not found"
What you expected to happen:
Property Id should be cleared when asset ID is selected.
How to reproduce it (as minimally and precisely as possible):
https://github.com/grafana/iot-sitewise-datasource/assets/16140639/cf870238-b358-4276-8dfd-2950cc6ddc98
Screenshots

Anything else we need to know?:
We can select multiple assets, so the property shouldn't be cleared unless its asset is removed.
Environment:

Grafana version:
Plugin version:
OS Grafana is installed on:
User OS & Browser:
Others:

@idastambuk I'm from the AWS SiteWise team. I'll take this issue! Thank you! :)


[TASK] Add kubectl port-froward to integration tests

Related to:
Incident: INC-1234
Overview:
According to the incident discussion, the kubectl port-froward is expected in some workloads.
Hence, we should ensure that it's working as part of our integration tests.
### Tasks
- [ ] Test kubectl port-froward for all components

Hello, I would like to work on this issue

do you mean by ensuring that it's working as part of our integration tests that it should be a part of file "test/integration/scenarios/chart-full-setup/Taskfile.yaml" ?

@mabdelgowa It should be part of testsuite-core.yaml which is a venom test.

@aabouzaid plz check the edited version of venom checks

@mabdelgowa Great :raised_hands:
Could you please create a PR for it?

@aabouzaid
Done


Static contacts script does not produce hydrogen bonds

Tried to compute water-mediated interactions from 1U19 crystal structure (input file attached):
$python static_contacts.py --topology 1U19_A_pdb.txt --output 1U19_test.txt --all-interactions
But, it appears like no hydrogen bond or water-mediated interactions are being computed:
$cat 1U19_test.txt | cut -f2 | sort | uniq
Columns: frame, interaction_type, atom_1, atom_2[, atom_3[, atom_4]]
pc
ps
sb
total_frames:1 interaction_types:sb,pc,ps,ts,vdw,hb,lhb
ts
vdw
1U19_A_pdb.txt

Adding hydrogens to the pdb files computes hbss, hbsb and hbbb interactions but no wb or wb2 interactions

For static structures, would it be possible to compute hbonds based on distance only, not distance and angle?

@ajvenkat When I added a --solv HOH argument then the wb and wb2 contacts were picked up. We'll have to look into setting the defaults for solvent in static computations.

Thanks, Anthony!


Latest changes broke docker-compose compatibility

Just rebuilt my containers and realized I can't log into the time machine any more. Seemingly, the latest change to add users removed the AFP_LOGIN, AFP_PASSWORD and AFP_NAME attributes. Still investigating, will update this issue once I know for sure. Going back to old version in the meantime.

That's right!

That's right!
https://github.com/odarriba/docker-timemachine/blob/dc9cd2add4186b5bf799b50bab62761b80b8243f/entrypoint.sh
I haven't thought about that possible use-case.
I will restore the functionality in the next days.
Thanks!!

Hello @RobTS !
I have just added that forgotten functionality, and it should be building in docker hub right now.
Can yo try again when compiled?
Thanks!

Hey, thanks for the help. Just got around to trying it, unfortunately, it's still failing. This time not with an auth, but a connection problem. Docker logs state the following:

Config matches the one of my public homeserver repo, it may help you find the issue: https://github.com/RobTS/homeserver_template

Hi again!
Sorry for the delay. I have test it right now and changed the service launching structure to avoid these errors.
According to my tests, it should work right now. Can you confirm it?
Regards!

I suppose this is working right now, So I'm closing the issue. Please, If it doesn't, just comment here and reopen the issue.
Regards!


Improve Market Hash Fragment

Some apps like Telegram encodes URL, that is why hash part of url will be like #buylisting%7C3126012155444962045%7C730%7C2%7C19106738906 but not like #buylisting|3126012155444962045|730|2|19106738906. Function MarketCheckHash accepts only | symbol, but not %7C.
if ( window.location.hash.length > 4 && window.location.hash.substr(0,4) == "#buy" )
{
	var rgListing = window.location.hash.substr(4).split('|');
	BuyMarketListing( rgListing[0], rgListing[1], rgListing[2], rgListing[3], rgListing[4] );
}

It will be great, if this extension will fixing hash part of URL before function MarketCheckHash was called.

Thanks for the suggestion, but I'd prefer that we don't mutate some core functions on the page for now.


[Lint] rename variable in graphx/translate.go

Go prefers mixed caps to underscores.
http://golang.org/doc/effective_go.html#mixed-caps
Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

R: @angoenka

No worries! It's a reasonable mistake to make.
@herohde Please merge!


The startupapicheck image isn't published to quay.io, so the standard Helm install fails.

While testing v1.14.0-alpha.0 in https://github.com/cert-manager/cert-manager/issues/6591, I found that the new startupapicheck isn't published to quay.io, so the standard Helm install fails.
$ helm upgrade test cert-manager --repo https://v1-14-0-alpha-0.jetstack-charts.pages.dev  --namespace cert-manager --create-namespace --install --set installCRDs=true --devel --wait
Release "test" does not exist. Installing it now.
Error: failed post-install: 1 error occurred:
        * timed out waiting for the condition

$ kubectl -n cert-manager describe pod/test-cert-manager-startupapicheck-gg5rv
...

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  79s                default-scheduler  Successfully assigned cert-manager/test-cert-manager-startupapicheck-gg5rv to kind-control-plane
  Normal   Pulling    41s (x3 over 79s)  kubelet            Pulling image "quay.io/jetstack/cert-manager-startupapicheck:v1.14.0-alpha.0"
  Warning  Failed     40s (x3 over 78s)  kubelet            Failed to pull image "quay.io/jetstack/cert-manager-startupapicheck:v1.14.0-alpha.0": rpc error: code = Unknown desc = failed to pull and unpack image "quay.io/jetstack/cert-manager-startupapicheck:v1.14.0-alpha.0": failed to resolve reference "quay.io/jetstack/cert-manager-startupapicheck:v1.14.0-alpha.0": unexpected status from HEAD request to https://quay.io/v2/jetstack/cert-manager-startupapicheck/manifests/v1.14.0-alpha.0: 401 UNAUTHORIZED
  Warning  Failed     40s (x3 over 78s)  kubelet            Error: ErrImagePull
  Normal   BackOff    0s (x5 over 77s)   kubelet            Back-off pulling image "quay.io/jetstack/cert-manager-startupapicheck:v1.14.0-alpha.0"
  Warning  Failed     0s (x5 over 77s)   kubelet            Error: ImagePullBackOff

Workaround is to disable the startupapicheck:
$ helm upgrade test cert-manager --repo https://v1-14-0-alpha-0.jetstack-charts.pages.dev  --namespace cert-manager --create-namespace --install --set installCRDs=true --devel --wait --set startupapicheck.enabled=false
Release "test" does not exist. Installing it now.
NAME: test
LAST DEPLOYED: Thu Jan  4 11:11:33 2024
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
cert-manager v1.14.0-alpha.0 has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.io/docs/configuration/

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.io/docs/usage/ingress/

I'll add this as a known issue in the release notes.
/kind bug
Originally posted by @wallrj in https://github.com/jetstack/jetstack-charts/pull/219#pullrequestreview-1803970844

I think startupapicheck needs adding here. It was added as a dependency of the make target in https://github.com/cert-manager/cert-manager/pull/6549 but the rules should also have been updated to add the startupapicheck image to the cert-manager-server file, here:
https://github.com/cert-manager/cert-manager/blob/612e2209685215eea3aead682471d53fe5563330/make/release.mk#L84-L103


refactor Tags

ref: https://github.com/gpanders/ztags/pull/3
It's more reasonable to pass allocator to init.
Remove GitHub related changes.

@gpanders PTAL
I have reverted allocator changes.
In current implementation, it's not that easy to adopt allocator directly, I plan to open a new PR to address this.

Thanks!


Test nc_test4/tst_bug324 is run by Makefile.am but not CMakeLists.txt

There is a test that is not being run by the cmake build. When I add it everything works fine. I will put this in my PR I'm about to put up on valgrind removal.

Never mind, it is run, but only with HDF4. I will close this issue.

OK, sorry for the confusion, but now I've figured out what the heck I am trying to do here.
The issue is that tst_bug324.c is run as a HDF4 test, but, in fact, has nothing to do with HDF4. It should just be run as a regular test. I noticed this when I separated out the HDF4 tests into their own directory.
That PR is still to come, but meanwhile, in my current PR I have moved tst_bug324 from being a HDF4 test to just a regular C test.

Ed-
I suspect this test refers to this issue:
https://github.com/Unidata/netcdf-c/issues/324
which appears, as you note, to be independent of hdf4.
But be aware that we had a couple of failures where is failed if hdf4 was enabled,
even if the test was not specifically an hdf4 test.

OK, good to know. It has been unassociated with HDF4 in the autotools build for some time, not sure when. Seems to be working OK.
In HPC NetCDF the HDF4 tests have all been moved to another dir, and tst_bug324.c left in nc_test4. Is it OK if I continue with this, and disassociate tst_bug324 from HDF4?

Ok with me.


Permissions example

Build a simple SaaS app which proxies shape requests through an API and only allows certain shapes to certain roles.

Duplicate of https://github.com/electric-sql/electric/issues/1455


Add url and baseUrl to error messages in parseUrl

Add the url and baseUrl to the error messages inside parseUrl. This should help debug where these errors originated.

@jdeal could you take a look at this one whenever possible? This should help debug an error that's spiked in Sentry since 8 days ago. Thanks in advance!

Thanks @jdeal!


Replace deprecated Chunk.modules usage

What kind of change does this PR introduce?
Replaces deprecated usage of Chunk.modules.
Did you add tests for your changes?
No interface or functional changes.
If relevant, link to documentation update:
No documentation update.
Summary
Using output: libraryTarget: "amd" causes a deprecation warning. This appears to cause build failures in some circumstances. This change replaces the deprecated property use with an undeprecated method cal which contains the exact same functinality.
Does this PR introduce a breaking change?
No.
Other information

Thanks


Add instructions on how to submit expense reimbursements

Typo - should be $25 or more, not $50 or more for receipt.

@talsafran technically I think this should go into the employee wiki, not the handbook but just a nitpick, nothing essential. The handbook should be the backbone of our policies, whereas the granular "here's how you do x and y" can go into the employee wiki.

No that's totally valid.
On Wed, Feb 24, 2016 at 11:57 PM, Charley Wang<EMAIL_ADDRESS>wrote:

@talsafran https://github.com/talsafran technically I think this should
go into the employee wiki, not the handbook but just a nitpick, nothing
essential. The handbook should be the backbone of our policies, whereas the
granular "here's how you do x and y" can go into the employee wiki.
—
Reply to this email directly or view it on GitHub
https://github.com/josephine/handbook/pull/39#issuecomment-188659122.

--
cto // co-founder
josephine.com // @talsafran http://twitter.com/talsafran

I can git revert that commit :)
On Thu, Feb 25, 2016 at 10:59 AM, Tal Safran<EMAIL_ADDRESS>wrote:

No that's totally valid.
On Wed, Feb 24, 2016 at 11:57 PM, Charley Wang<EMAIL_ADDRESS>wrote:

@talsafran https://github.com/talsafran technically I think this
should go into the employee wiki, not the handbook but just a nitpick,
nothing essential. The handbook should be the backbone of our policies,
whereas the granular "here's how you do x and y" can go into the employee
wiki.
—
Reply to this email directly or view it on GitHub
https://github.com/josephine/handbook/pull/39#issuecomment-188659122.

--
cto // co-founder
josephine.com // @talsafran http://twitter.com/talsafran

--
cto // co-founder
josephine.com // @talsafran http://twitter.com/talsafran


poudriere.conf.sample: fix typo

Sorry, that second commit has nothing to do with this PR..

Cherry picked just 47c168784afb6caf9ce606a81cf815b18c4754c7 in


When using local IP of my macbook where meteor is running  not able to connect to iPhone (ws://local IP:4000/websocket)

Meteor is running on my macbook, I am trying to connect from my iPhone to meteor using local IP of my macbook. I am unable to connect.
+ (instancetype)defaultAccount {
  A0SimpleKeychain *keychain = [self keychain];
  if (!keychain) return nil;
  NSData *data = [keychain dataForKey:METAccountKeychainItemName];
  if (!data) return nil;
  return [NSKeyedUnarchiver unarchiveObjectWithData:data];
}

getting data is nil, self.networkReachabilityManager.reachabilityStatus  getting  Null

Can i connect using IP or not, because when I am using url able to connect,
If i am using  "ws://localhost:4000/websocket"then able to run in simulator,
Please can i know why Local IP is not working, and it will work or not?

Use the .local address that you can find in OS X Settings > Share/Sharing : Computers on your local network can access your computer at.


windows mingw64 compile fail

My step：
git clone https://github.com/google/glog.git
cd glog

cmake -S . -B build -G "Unix Makefiles"
cmake --build build

An error occurred:
[  3%] Building CXX object CMakeFiles/glog_internal.dir/src/demangle.cc.obj
In file included from C:/Users/xxx/Documents/glog/src/demangle.cc:44:
C:/Users/xxx/Documents/glog/src/utilities.h:61:12: fatal error: port.h: No such file or directory
   61 | #  include "port.h"
      |            ^~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/glog_internal.dir/build.make:76: CMakeFiles/glog_internal.dir/src/demangle.cc.obj] Error 1
make[1]: *** [CMakeFiles/Makefile2:861: CMakeFiles/glog_internal.dir/all] Error 2
make: *** [Makefile:166: all] Error 2

Everything is normal when compiling on Ubuntu.
Is there any special operation required for compiling on the Windows platform?
I use MSYS2 MINGW64、windows 11 、 Latest code(#54b2c17172dc39892de41ed2b3e72902e19ce0c0)
Hope to receive some guidance, thank you in advance

Could you please provide the full output of cmake --build build --verbose?

This is the complete output
$ cmake --build build --verbose
Change Dir: '/c/Users/xxx/Documents/glog/build'

Run Build Command(s): /usr/bin/cmake.exe -E env VERBOSE=1 /usr/bin/make.exe -f Makefile
/usr/bin/cmake.exe -S/c/Users/xxx/Documents/glog -B/c/Users/xxx/Documents/glog/build --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake.exe -E cmake_progress_start /c/Users/xxx/Documents/glog/build/CMakeFiles /c/Users/xxx/Documents/glog/build//CMakeFiles/progress.marks
/usr/bin/make  -f CMakeFiles/Makefile2 all
make[1]: Entering directory '/c/Users/xxx/Documents/glog/build'
/usr/bin/make  -f CMakeFiles/glog_internal.dir/build.make CMakeFiles/glog_internal.dir/depend
make[2]: Entering directory '/c/Users/xxx/Documents/glog/build'
cd /c/Users/xxx/Documents/glog/build && /usr/bin/cmake.exe -E cmake_depends "Unix Makefiles" /c/Users/xxx/Documents/glog /c/Users/xxx/Documents/glog /c/Users/xxx/Documents/glog/build /c/Users/xxx/Documents/glog/build /c/Users/xxx/Documents/glog/build/CMakeFiles/glog_internal.dir/DependInfo.cmake "--color="
make[2]: Leaving directory '/c/Users/xxx/Documents/glog/build'
/usr/bin/make  -f CMakeFiles/glog_internal.dir/build.make CMakeFiles/glog_internal.dir/build
make[2]: Entering directory '/c/Users/xxx/Documents/glog/build'
[  3%] Building CXX object CMakeFiles/glog_internal.dir/src/demangle.cc.obj
/mingw64/bin/CC.exe -DGFLAGS_IS_A_DLL=0 -DGLOG_NO_SYMBOLIZE_DETECTION -DGLOG_USE_GFLAGS -DGLOG_USE_GLOG_EXPORT -DGOOGLE_GLOG_IS_A_DLL -I/c/Users/xxx/Documents/glog/src -I/c/Users/xxx/Documents/glog/build -I/usr/local/include -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT CMakeFiles/glog_internal.dir/src/demangle.cc.obj -MF CMakeFiles/glog_internal.dir/src/demangle.cc.obj.d -o CMakeFiles/glog_internal.dir/src/demangle.cc.obj -c /c/Users/xxx/Documents/glog/src/demangle.cc
In file included from C:/Users/xxx/Documents/glog/src/demangle.cc:44:
C:/Users/xxx/Documents/glog/src/utilities.h:61:12: fatal error: port.h: No such file or directory
   61 | #  include "port.h"
      |            ^~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/glog_internal.dir/build.make:76: CMakeFiles/glog_internal.dir/src/demangle.cc.obj] Error 1
make[2]: Leaving directory '/c/Users/xxx/Documents/glog/build'
make[1]: *** [CMakeFiles/Makefile2:861: CMakeFiles/glog_internal.dir/all] Error 2
make[1]: Leaving directory '/c/Users/xxx/Documents/glog/build'
make: *** [Makefile:166: all] Error 2

You need to run CMake in the MINGW64 / MSYS2 shell not MSYS / MSYS2.

Thanks for your guidance, it helps a lot.
I am indeed using MINGW64/MSYS2. It should be caused by not installing the software package mingw-w64-x86_64-cmake. Because I did not encounter this problem when compiling other projects normally, I did not take it into consideration.
All in all, thank you very much


Fixing argument handling in the JSRT C# sample

The argument parsing is expecting at least one argument, but the check is validating against zero.

@liminzhu Can you take a look?

Good catch @kfarnung . Could you fix the occurrences in other samples as well?

@liminzhu I believe that's all of them.

@kfarnung  thanks!


Added hovering effect to logot button

Related Issuse

User friendly hovering effect on logout button.

Closes: #197
Describe the changes you've made
I have added hovering effect to logot button.
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

Original
Updated

original screenshot

updated screenshot |

@iamabhi222 I have made the changes .Please review.


Ticker / stock tooltip

Overview
Current Behavior
Currently, there is varying usage of Ticker and Stock with no explanation. This is confusing for the user, a beginner trader.
Desired Behavior
I would like there to be a tooltip somewhere in the app that explains the difference between the two.
Use Cases
I considered using only one of the terms, but this not only complicates things, it also misses out on a great opportunity for the user to learn.
Technical Scope
We already have a tooltip component. Just decide where it goes, and what it says

*I would also like to include a re-color or animation for all tooptips