Regression: rule not accepted anymore by schema in v5

Bug report
What is the current behavior?
Rule in the module section is not accepted anymore by the the schema. The error is:
configuration.module.rules[0].oneOf[6].resource.or[0] has an unknown property 'exclude'. These properties are valid:    object { and?, not?, or? }
If the current behavior is a bug, please provide the steps to reproduce.
{
  rules: [{ oneOf: [
    ...,
    {
      resource: {
        test: /(\.html\.js|\.js|\.mjs)$/,
        or: [{ exclude: /node_modules/ }, ...compileWithBabel],
      },
      loaders: [babelLoader]
    },
    ...
  ] }]
}

What is the expected behavior?
That it would be accepted by the schema. I am not very fluent in reading the schema, but it seems that it is not possible anymore to use any object other than one containing or, not and and withing an or, not or and.
This is the description of rule.test: "Shortcut for resource.test.". The resource rule however looks like this:
        "resource": {
          "description": "Match the resource path of the module.",
          "oneOf": [
            {
              "$ref": "#/definitions/RuleSetConditionOrConditionsAbsolute"
            }
          ]
        },

And as far as I can tell, the RuleSetConditionOrConditionsAbsolute does not contain a test property.
Alternatively, if this was a conscious change I expected it to be mentioned in https://webpack.js.org/migrate/5/ or https://github.com/webpack/changelog-v5#minor-changes
Other relevant information:
webpack version:  5
If there is another way to formulate this rule I am happy to change it.

If I change the rule to this:
        {
          resource: {
            test: /(\.html\.js|\.js|\.mjs)$/,
            or: [{ not: /node_modules/ }, ...compileWithBabel],
          },
          loaders: [babelLoader]
        },

I get this error:
- configuration.module.rules[0] should be one of these:
   ["..." | object { compiler?, dependency?, descriptionData?, enforce?, exclude?, generator?, include?, issuer?, issuerLayer?, layer?, loader?, mimetype?, oneOf?, options?, parser?, realResource?, resolve?, resource?, resourceFragment?, resourceQuery?, rules?, sideEffects?, test?, type?, use? }, ...]
   -> A rule.
   Details:
    * configuration.module.rules[0].oneOf[6].resource.or[0].not should be an array:
      [RegExp | string | object { and?, not?, or? } | function | [(recursive), ...], ...]
      -> A list of rule conditions matching an absolute path.
    * configuration.module.rules[0].oneOf[6].resource.or[0].not should be one of these:
      [RegExp | string | object { and?, not?, or? } | function | [(recursive), ...], ...]
      -> Logical NOT.

And if I change it to this:
        {
          resource: {
            test: /(\.html\.js|\.js|\.mjs)$/,
            or: [{ not: [/node_modules/] }, ...compileWithBabel],
          },
          loaders: [babelLoader]
        },

I get this error:
 - configuration.module.rules[0].oneOf[6].resource has an unknown property 'test'. These properties are valid:
   object { and?, not?, or? }

And that one feels kinda weird considering the following comments in the documentation:

Rule.test is a shortcut to Rule.resource.test. If you supply a Rule.test option, you cannot also supply a Rule.resource. See Rule.resource and Condition.test for details.

There is no test within resource. You can only use and, or and not since webpack 5.

From the documentation:

Include all modules that pass test assertion. If you supply a Rule.test option, you cannot also supply a Rule.resource. See Rule.resource and Condition.test for details.

There is also no Condition.test I think

Just to understand the new structure better, is this:
{
  test: 'a',
  exclude: 'b',
}

The same as?
{
  resource: {
    and: ['a', { not: 'b' }]
  }
}

Maybe resource is an and by it self, and it could be simplified to:
{
  resource: ['a', { not: 'b' }]
}

I don't think time should be spend on this issue. I naively thought I could quickly switch to v5, but after reading some of the motivation I realized this is not going to be that kind of upgrade.
We will re-evaluatate our configuration and plugins, quite a few things have become obsolete by new features in v5. It is gonna be quite some work to get things implemented a backwards compatible fashion, but that is fine. I understand the motivation and I think the steps taken by the webpack team are in the right direction.


When in about.html, 'Contact us' doesn't direct to the footer

I would love to fix to issue. Do assign it to me.
Thanks!


Rate limiting

Telegram has two separate rate limit conditions in place. The first is that a bot cannot send more than 30 (or so) messages per second. The second is that a bot cannot send more than 20 messages to the same group per minute. If either of these limits are hit the bot will start getting 429 errors.
It would be nice, though not absolutely imperative, to have a rate limiter in place to keep the bot from hitting these limits. The challenge is not so much the first condition, but the second.

@watzon Issue with that is that some people rather deal with the flood limits themselves then only having a "the method is maybe sending the reply in time".
So that needs to be an opt-in/out functionality imo.
Ptb offers a message queue for example.

Yeah that's the main reason I haven't added it yet. I need to think of not only the best way to do so, but how to do it in such a way that it's opt-in. A message queue isn't the worst idea.

@watzon Well the queue is just a different module. I think in python its being done with decorators, not sure your cristal has those.
There are a lot of different ways to implement rate limit dealing. Telethon for example silently expects them, checks if the wait time is under X seconds, if yes, waits those seconds out and send it then, if not, raises the error and lets the user deal with it. Also a possibility

@Poolitzer Yeah, Crystal has annotations. Not sure if that's the way I'd go with this or not. I'll have to do some brainstorming. Just retrying after a failure may be the easiest way to go about things, I guess we'll see.

@watzon It definitely is the easiest, but as I said easier, some people might not like that cause it breaks their flow

Keep in mind that Telegram increases the limits of the popular bots

True. Ideally any limiter should be both optional and configurable.


cram?

Hi, this looks very useful, will it work with cram files as input? thanks

Hi, thanks for your question. I can confirm that everything works as expected when I convert the BAM file in the example/ folder to CRAM. Let me know if you have any issues.


Install MAAS metrics fails on first task ('Set the TCP port for grafana')

Playbook fails when install_metrics = true is set in extra_vars, on the 'set the tcp port for grafana' task
Output (is long):
{"changed": false, "cmd": ["maas", "admin", "maas", "set-config", "name=promtail_port", "value=5238"], "delta": "0:00:01.369197", "end": "2022-12-06 15:22:54.386239", "msg": "non-zero return code", "rc": 2, "start": "2022-12-06 15:22:53.017042", "stderr": "usage: maas [-h] COMMAND ...\n\noptional arguments:\n  -h, --help      show this help message and exit\n\ndrill down:\n  COMMAND\n    login         Log in to a remote API, and remember its description and\n                  credentials.\n    logout        Log out of a remote API, purging any stored credentials.\n    list          List remote APIs that have been logged-in to.\n    refresh       Refresh the API descriptions of all profiles.\n    init          Initialize controller.\n    apikey        Used to manage a user's API keys. Shows existing keys unless\n                  --generate or --delete is passed.\n    configauth    Configure external authentication.\n    config-tls    Configure MAAS Region TLS.\n    createadmin   Create a MAAS administrator account.\n    changepassword\n                  Change a MAAS user's password.\n\nhttps://maas.io/\n\nargument COMMAND: invalid choice: 'admin' (choose from 'login', 'logout', 'list', 'refresh', 'init', 'apikey', 'configauth', 'config-tls', 'createadmin', 'changepassword')", "stderr_lines": ["usage: maas [-h] COMMAND ...", "", "optional arguments:", "  -h, --help      show this help message and exit", "", "drill down:", "  COMMAND", "    login         Log in to a remote API, and remember its description and", "                  credentials.", "    logout        Log out of a remote API, purging any stored credentials.", "    list          List remote APIs that have been logged-in to.", "    refresh       Refresh the API descriptions of all profiles.", "    init          Initialize controller.", "    apikey        Used to manage a user's API keys. Shows existing keys unless", "                  --generate or --delete is passed.", "    configauth    Configure external authentication.", "    config-tls    Configure MAAS Region TLS.", "    createadmin   Create a MAAS administrator account.", "    changepassword", "                  Change a MAAS user's password.", "", "https://maas.io/", "", "argument COMMAND: invalid choice: 'admin' (choose from 'login', 'logout', 'list', 'refresh', 'init', 'apikey', 'configauth', 'config-tls', 'createadmin', 'changepassword')"], "stdout": "", "stdout_lines": []}

Will be fixed as part of future work.


Incompatibility with several mods due to grave creation time

I’m the developer of Respawn Obelisks, a relatively small mod. A user of mine has reported incompatibility with this mod. My mod attempts to intercept player item drops and keep them, but not necessarily with a soul bound enchantment. I do this during the drop method of LivingEntity, whereas you create graves and handle items during onDeath of ServerPlayerEntity.
At first, I was just going to make my execution happen before yours, but I quickly found out that breaks my compatibility with another mod: Revive. Revive attempts to stop the player from dropping their items when they die, and it turns out that doesn't work with this mod either, since it tries to redirect the LivingEntity drop call(after you create a grave).
I believe the best way to fix this issue is for this mod to instead similarly prevent the player from dropping their items when they do actually drop them, which should fix problems with both of the aforementioned mods.
TLDR; Execution of YIGD's grave creation happens quite early, and breaks support with several other mods that too try to intercept item drops.
I am happy to make a PR to move execution to be on the actually dropping of the items, but I wanted to first clarify with you that that would actually be helpful.

I am aware of this, but it's actually necessary for me to have my execution time early. It turns out that if I move execution to when the player drop all their items, other things can break. For example, if I would have my graves generated when the player drops all of their inventory, trinkets will already have dropped their items, and I can't store them in my graves.
This will allow me to store items in the graves from a wide variety of mods, but yes in some instances this will happen that some other mod who also wants to change item drops is prevented from doing so.
I like to manually provide compat with these mods. In my opinion it makes it easier for both me and players using the mod with the other mods. I will for example store a snapshot of the inventory as it was before everything was dropped, and then depending on a ruleset, give some back when the grave is looted, when the player respawn, drop them on the ground, or just treat them as "vanished" or "destroyed".
I'm aware of the trinkets specific drop rules, and I'm checking them manually through my compat implementation, to make sure they are followed. If there's any edge-case however you have found that I do not follow, do let me know about it.
Finally when it comes to revive, (I haven't looked at the mod recently, so I'm not sure exactly what they do), it would make sense if they had their code injected earlier, but I'm not sure how our mods would play along in that case. It might be possible to just redirect the specific onDeath call from LivingEntity#damage, and then call the function separately, but idk maybe there's a better reason why the code is put where it is. There's also a chance I have this opinion just because I don't want to move my stuff, as that could possibly have unforeseen consequences, and I want to provide an as stable experience as possible (since if something goes wrong, players might lose all their items randomly).
I'd be interested if there's anything I should be aware of to implement compatibility on my end. Also do let me know if you have any counter-arguments you'd like to mention. I'd appreciate the feedback!

I guess I could try to move the injection point to LivingEntity#drop. I did have an issue in the past that fixed itself by moving from that injection point to ServerPlayerEntity#onDeath (which is the same injection point that DeathLog uses) from LivingEntity#drop.
I've previously used PlayerEntity#dropInventory, but I'm not even sure that's in a released version, meaning it's long ago I did that. After that (and the aforementioned issue) I've concluded that putting the code execution earlier will prevent other mods from messing things up for me.
I will try to change the injection point though, and I'll see what happens. There are quite a number of mods now that add their own inventory implementation (I provide compat for all I know, which there are 7 of, which I believe is more than universal graves does), and there's a chance some compat might break.
I'm still interested in providing compat with respawn obelisks though! There are a lot of rules that can be applied to the inventory storage mechanisms in my mod, so people could in that case likely decide on their own how they would want inventories to be handled

Should be mostly doable to implement, as long as there's something to check an obelisk was used when the player has respawned, and if yigd still takes priority with its mixins. The problem with spawning the items where the player died on respawn, instead of on death, is something that will not be as straight-forward to implement, but it's definitely possible to do. I'll let you know how it goes

Yeah I already have systems in place for respawning. Both for soulbound and other stuff. So adding/removing items from the grave shouldn't be a problem, only dropped items, but as I stated that can probably be implemented somehow anyway.

Based on my very limited testing, it seems to work well enough having the injection point at LivingEntity#drop. It might still cause issues with other mods, like mods implementing soulbound traits to items, but that remains to be seen. I'll take a better look at compatibility tomorrow though


add Pony and Elephant factors

A question at CHAOSSCon was, "What other 'big name' metrics did we come across, besides Bus Factor".
This pull-request adds the Pony Factor and Elephant Factor.

Yea, there were others too. Velocity was one.

If we added "Velocity", what definition can we give it?

CNCF has worked through this a bit:
https://www.cncf.io/blog/2017/06/05/30-highest-velocity-open-source-projects/

Thanks @germonprez  I added Velocity

Once #58  is merged, I will resolve the merge conflict.

Pull request is updated to resolve merge conflicts. It is ready for review again.


Some noob problems

Hi! Idk why but the app just won't work it gives the error and shuts down immediately
Help please(

Please follow #18 . More or less related.


abnormal gc behavior of Executor

Recently I was tuning Gearpump's performance and I found a randomly abnormal gc behavior of Excutor's jvm.
Here is the snapshot of a normal Executor Jvm's gc behaviour:

The most of gc activity is minor gc and the used heap is growing very slowly.
While here is the abnormal one:

You can see the full gc acticity is very often and it eventually will hurt the performance of Task on that Executor.
After continue digging, I found the abnormal jvm will generate a lot of akka.dispatch.AbstractNodeQueue$Node object:

Here it takes about 243MB of memory while the normal Executor jvm does not take that much.
Then I found there is already a similar issue raised in Akka:  https://github.com/akka/akka/issues/17547

@huafengw
Yes, this is a good finding. It also puzzles me for a long time. But I am not sure it is the same problem of akka#17547

There is a fix about that issue. I tried to using that fix and build a new related jar to run the application.
I ran multiple times and seems the weird gc behavior is gone.

Great! Can post the jar somewhere? I can try it locally.

It is worth to do some performance test. I think the improvement will be huge.

Please make a PR to work-around this.

Any advice on how to achieve that?

You can package the unmanaged jar directly.

@huafengw
Would you mind also paste the performance result here?

Here is the performance benchmark result on a 4-node cluster:
+--------------------+------------------------+-------------+
|                    | Throughput(messages/s) | Latency(ms) |
+--------------------+------------------------+-------------+
| Before #1816 fixed | 14,600,000             |           8 |
| After #1816 fixed  | 18,000,000             |           4 |
+--------------------+------------------------+-------------+

Now the performance is much steadier than before
Now increasing JVM’s memory will not bring much performance improvement.

Great!


Request:  tags support

Thanks for an incredible addon! It's super fast and easy to use.
I have a request though: I would be nice if we could include some custom meta tags.
Specifically, I need this to be able to zoom in on some HTML text.
I would use this:
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=1.0, minimum-scale=1.0, maximum-scale=2.0">

Hi, I'm glad to hear you like this module !
I don't think it would make sense to support any meta tag. These tags offer features that are entirely tied to browsers. Most of them wouldn't have much use with native components, except, maybe the viewport one.
However, mimicking this zooming behavior would be really tedious in react-native. To be honest, I wouldn't even know where to start, and I'm not sure this would be the highest priority right now.
Maybe we could wrap the rendered nodes inside something like react-native-view-transformer, but I don't know how texts would behave while zooming.
If you, or someone else, has more vision on this particular feature, I'd be happy to consider it, or review any PR.

The viewport meta tag works very well, at least in my device tests, for both iOS and Android. I have a RN app in production, with zero issues: https://play.google.com/store/apps/details?id=dk.krydsord.dagligkrydsen.xl - it's in Danish, but you should be able to get it or at least see the screenshots. The "zooming webview" is the crossword "player" itself.
Now, I'm making an app with song texts, primarily for an older audience, and I thought it would be nice if they could zoom in on the text by pinching (and there will also be sheet music, where it will also be important to zoom in). But on Android RN, no one has yet to make a View type that can support both zoom and scrolling in both directions. But WebView supports it out of the box, with the viewport meta tag, thus why I found your module.
That's why I'd like to somehow inject the meta tag within your module.
If you can point me in the right direction, I'd be happy to implement it and submit a PR.

Heh.. I'm pretty sure you're using display-html not this one which is render-html.
There is no webview at all in this repo 😅

I am using this one, mistakingly installed the other one earlier, but I'm on display-render now :)
I was just assuming it was using WebView. Oops! :)


It would be useful to add Dockerhub Info

Under the "use" or "release" links in the nav header, it'd be helpful to have a link to getting started with releasing Dockerhub images through the Microsoft organization (https://hub.docker.com/r/microsoft/)

Thanks Bryce. I don't actually have much information about that process, any chance you know more? Feel free to share that info internally to jwilcox.

@brycem Bryce, just reaching out again - any idea if such a resource on the docker hub side is already available?
Internally the resources pages are located here, if you'd like to submit a pull request: https://github.com/Microsoft/ospo-opensource/tree/develop/views/resources

Sorry for the delay - I've just emailed you the response I got to an internal docker DL query on the same topic.

Closing per internal thread


sven co-op support ?

Sorry for the late response.
I tried sven co-op and unfortunately it doesn't work. On Steam, sven co-op is distributed as a standalone game, not as just a mod for Half-Life. So they have their own hw.so (don't know how it differs from the original), which this hack relies on. Maybe this is a problem (not sure).
I'm not planning to support it (as I'm not interested in sven co-op), but feel free to fork and adapt it for for sven co-op.


Can't use a decorator

With the latest version of Babel, along with preset-stage-0, using a decorator results in a console error:
Uncaught TypeError: Cannot call a class as a function
    at r (index.js:1)
    at o (index.js:1)
    at Object.defineProperty.value (index.js:6)
    at __webpack_require__ (bootstrap 29dc0c7…:19)
    at Object.defineProperty.value (index.js:15)
    at __webpack_require__ (bootstrap 29dc0c7…:19)
    at Object.defineProperty.value (index.js:6)
    at __webpack_require__ (bootstrap 29dc0c7…:19)
    at Object.<anonymous> (client.js:19)
    at __webpack_require__ (bootstrap 29dc0c7…:19)

Manually wrapping my component without using a decorator seems to work.
I use @withApollo and other decorators fine in the same codebase. I wonder if you should use mridgway/hoist-non-react-statics? You can see it used here by Apollo.

Did you try using it as an HOC ?
export default placesLoader(MyComponent, {
  libraries: ["places", "geometry"],
  key: GOOGLE_MAPS_API_KEY,
})

Did you try using it as an HOC ?

Yes, and it seems to work. Although Babili mangle seems to get stuck on this package, I wonder if it's related to this issue.

Documentation was outdated. But I remove the decorator line in it.


Cannot display 0 after select 0 with options: [0, 1, 2]

now, I have to translate options from a list of number to a list of string, such as: ['0', '1', '2'].
Is it a bug or I missed something?
version<EMAIL_ADDRESS>

Hmm, there actually seems to be a bug when you select number 0 in a single-select.
Thanks for catching this! I should fix this soon.

@shentao thanks 👍

I think I got it fixed. The updated release should be available ~Wednesday.

@shentao Hey shentao, May I ask about the v-modal feature again?
Or is there something I can help? I can try to submit a  PR for that. :)

This is something that requires some breaking changes, but I guess I will have it this week :)

@shentao Thank you so much :)

Finally published and available in v1.1.3!

@shentao Cool~! 👍


Make custom schema persitent

I like to save my custom schema within the extension, so that I do not have to replace the default schema every time.

The extension actually only wraps https://skohub.io/editor/, so we should persist schema URLs here.

I like to save my custom schema within the extension, so that I do not have to replace the default schema every time.

After giving this another thought with @dobladov, this will actually be a setting in the extension after all.


Added VB Variant Example

Summary
Added a VB variant example for rule id ca2215.
Fixes #Issue_Number 22039.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mikehowell sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@mikehowell Tip: From "Files changed" tab, you could use "Add suggestion to batch" button to apply all suggested changes in a single commit.

Thanks for the info @Youssef1313 . I'm new to contributing to open source projects so this information really helps. Thanks also for your contributions to this PR too.

@mikehowell Thank you for adding the VB example!


Background: Change the background of application from coloured to image from unsplash

Use this image as background

Not doing this task since current theme does not match with this background


Error in MatSelect.prototype._onFadeInDone

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Mat select should close without any errors in the console.
What is the current behavior?
When closing a mat select, with or without selecting anything, an error is thrown in the console:
ERROR TypeError: Cannot read property 'nativeElement' of undefined
at MatSelect._onFadeInDone
At a cursory glance, it looks like this function is only supposed to be called when opened, not closed.
What are the steps to reproduce?
https://angular-xeppx5.stackblitz.io
Angular 5.0.0 project with Material 2.0.0-beta.12
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.0.0, Material 2.0.0-beta.12, TypeScript 2.5.3, tested with Chrome 61.0.3163.100 and FireFox 56.0.2.

This is something that is fixed in master and will be in the next release.


404 Not Found add_or_update_user/<user_id>

hi
when I request to  rest api on gamification engine   a url 404 Not Found
in my gamification engine, auth is off
for example : http://<IP_ADDRESS>:6543/add_or_update_user/2 and method: post and python version is 3.7.3
respones:
`

404 Not Found

404 Not Found
The resource could not be found.

/add_or_update_user/2

« FIXME: Debug Toolbar

`
How to solve this problem?

fixed in develop


stm32/spi: new_blocking_txonly_nosck hangs on v3+

All SPI operations on an SPI created with new_blocking_txonly_nosck hang on chips with SPIv3+.
It hangs in spin_until_rx_ready.
The only difference vs new_blocking_txonly is we don't configure any pin as SCK. Seems strange the SPI would care, intuitively I'd say SCK should be only an output so the SPI shouldn't care if it goes "nowhere". Perhaps it needs to be "looped back" somehow. Hopefully it's only for the RX part, so we can fix it by actually not doing any RX at all.

fixed in #3028

Reopening since maybe we should try to get it working instead of just disabling it. There's two people that have confirmed it's working for them (in G0 the author of https://github.com/embassy-rs/embassy/pull/1345, then another in G4). So i'm very confused why it's always hanging in tests for me...


Fix debugger setup

I asked this in the discord but got no reply, so pushing this branch here to get some visibility.
I needed to make the changes in this PR to get the app to run with the VSCode debugger. I don't know if this is due to my environment (windows, node 18.18), or if the debugger setup is just broken.
If someone can verify these changes also work on a mac/linux environment we  can decide to merge this (or not).

👍


Use simpler csproj format

This project is fairly simple right now, but the older style csproj format that it is using can cause issues as a project grows especially concerning merge conflicts. As long as required development on VS 2017 is okay, this new format is much cleaner and simpler than the older project files.

@twsouthwick,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Wait, you can use the core csproj for full framework projects? Why isn't this default?

Because it doesn't work for all project types. Simple console style apps, though, work as expected. Others (like WebApps, WPF, etc), have issues at the moment (although the team is working to enable it for all). It is default, however, if you go through the ".NET Core -> Console App" menu and then change it to a whatever target framework (ie .NET 4.6) you want.

Thanks! That makes sense. (I mean, except for the creating a netfx app via ".NET Core" 😉) Having looked at some of the msbuild .props and .targets now, I can see why it's taking time!

Sure this looks way simpler for a little tool like this.


The sample code is wrong when using in query parameters with a list of values

Describe the bug
The generated code in curl, Python, etc. is not well generated when we have query parameters with a list of values.
The query parameters in the sample code have the list of values separated by commas (",") and should be exploded instead, i.e., repeat the query parameter for each value separated by an "&".
This behavior is defined by the explode OpenAPI property (that defaults to true), which seems to be being ignored.
Even when we force explode to true, it is ignored.
See this example in the OpenAPI spec (you can download it with the Export button at https://developers.probely.com/api/reference/probely-developer-documentation):

See more about the explodeproperty at https://swagger.io/docs/specification/serialization/#query
Expected behavior
In the endpoint https://developers.probely.com/api/reference/api-users-list, when adding values for query parameters exclude and exclude_target like this:

The generated curl should be:
curl -L -X GET 'https://api.probely.com/api-users/?exclude=field1&exclude=field2&exclude_target=t1&exclude_target=t2' \
-H 'Accept: application/json' \
-H 'Authorization: JWT <YOUR_API_TOKEN>'

Current behavior
Currently, the generated curl is wrong with the values of the query params exclude and exclude_targetseparated by commas (","):
curl -L -X GET 'https://api.probely.com/api-users/?exclude=field1,field2&exclude_target=t1,t2' \
-H 'Accept: application/json' \
-H 'Authorization: JWT <YOUR_API_TOKEN>'

Possible solution
Consider the explode property of the OpenAPI to generate the sample code.
If explode is not defined or is true the query parameters in the sample code should be repeated for each value that is inserted and separated by "&".
If explode is false the values of the query parameter in the sample code should be separated by a comma (",")
Steps to reproduce

Go to https://developers.probely.com/api/reference/api-users-list
At the right hand side, in the REQUEST section, click on Show optional parameters
Add "field 1" and "field2" to the exclude query parameter
Add "t1" and "t2" to the exclude_targetquery parameter
Check the generated sample code in curl that is generated with query parameters separated by commas

Screenshots

Context
This provides a bad user experience for people trying to get the sample code to use the API endpoint since it will not work, and it's difficult to understand why.
Your Environment

Version used: docusaurus: 2.4.3, docusaurus-plugin-openapi-docs: 2.1.0

Related to #750


Clone the options var.

I was running into an issue when running this behind a webserver as a microservice. Basically the first request would generate the pdf as expected however subsequent requests were returning the same PDF.  After some debugging I found that the HTML files are being written correctly but options isn't getting updated.
Here is the options on the first pass:
{
    allowLocalFilesAccess: true,
    printDelay: 5000,
    settings: { javascriptEnabled: true },
    html: '\n    \n    \n
blah
\n    \n\n',
    footer: 'Date Generated: 08-Sep-2016 12:17:36 (GMT -0500)'
}

And on the second:
{ allowLocalFilesAccess: true,
  printDelay: 5000,
  settings: { javascriptEnabled: true },
  footer: 'Date Generated: 08-Sep-2016 12:20:28 (GMT -0500)',
  viewportSize: {},
  paperSize: {},
  waitForJSVarName: 'PHANTOM_HTML_TO_PDF_READY',
  htmlFile: '/tmp/2337a2d0-75e8-11e6-9a97-dbf70888544fhtml.html',
  footerFile: '/tmp/2337a2d0-75e8-11e6-9a97-dbf70888544ffooter.html',
  url: 'file:///%2Ftmp%2F2337a2d0-75e8-11e6-9a97-dbf70888544fhtml.html',
  output: '/tmp/2337a2d0-75e8-11e6-9a97-dbf70888544f.pdf',
  html: '\n    \n    \n
blah2
\n    \n\n' }

Notice that the url is already set to the previous HTML document. And based on this code:
opt.url = opt.url || "file:///" + encodeURIComponent(opt.htmlFile);

It would reuse the same url over and over again.
My change just uses lodash to do a deep clone of the the options passed in so that any modifications that are done are not passed on to subsequent request.

Great, thanks.

Released in 0.4.6


Mod stops the live game output option from working

When enabled the mod stops the live game output option from working. it doesn't update live until the game is closed, is there any way to fix this?

If you are using the vanilla launcher, this issue can be fixed by replacing the contents of the Console appender with <LegacyXMLLayout /> in the mod's config file. Alternatively, you can use an alternate launcher that does not have this issue to begin with, such as MultiMC. I can't release a new version of the mod with this fix included by default however, as the legacy XML layout breaks the logging of non-vanilla launchers (Such as MultiMC).
Specifically, to fix the issue, look for the lines <Console name="SysOut" target="SYSTEM_OUT"> and </Console> in the mod's config file. Then, replace everything in-between those lines with just <LegacyXMLLayout />.


Implemented: functionality to reorder pending jobs from the updates page(#2dmggua)

Related Issues

Closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[ ] I read and followed contribution rules

Closing as will be handled in #172


Build manylinux binary wheels of releases

Currently only source distributions are deployed to PyPi.

Make it possible to build manylinux binary wheels via Travis-CI builds
Publish those to PyPi

This will make binary wheels available for most linux distributions, so they do not have to build from source to get native code extensions when installing via pip.
See manylinux branch for a WIP.

Wheels automatically built for OSX and Linux as of 1.4.0


Chore rename TTopnFilterContext to TTopnFilterDesc

Proposed changes
rename TTopnFilterContext to TTopnFilterDesc
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


feat: allow to pick providers via the cli

allows to specify --provider=aws or --provider=google.
Follow up: I think we have to take out cloud-provider client initialization out of the New.. constructors. Since they are both registered statically you'll always have to have a valid Google and AWS client, which usually won't be the case.
/cc @ideahitme

👍


Move the Donate Link

Description
Donate link
Ask
The Donate link shouldn't be the first thing a user sees.
To Do
Move the donate link to the end of the menu.
Reword the sentence
Here's the new order: About, Chapters, Materials, Donate
Additional Info
The donate link shouldn't be the first thing a user sees. They need to know about GDI before they are asked to date.

@staceyturnage not entirely sure we want to move forward with this and move the donate button to the end. Would be good to get some direct examples and/or studies that prove that we need to move to the end of the nav links.
@corinnepw what are your thoughts on the importance of where the donate link is in the main nav? I feel like you have the best perspective on how easily people are able to find out that information.

Here's are a few nonprofit technology group that has "support" at the end
of their menu!
http://www.nten.org
http://www.techsoup.org
Code.org has their donate button at the bottom of the page
http://code.org
Stacey
On Wed, Feb 11, 2015 at 8:57 PM, Julia Elman<EMAIL_ADDRESS>wrote:

@staceyturnage https://github.com/staceyturnage not entirely sure we
want to move forward with this and move the donate button to the end. Would
be good to get some direct examples and/or studies that prove that we
need to move to the end of the nav links.
@corinnepw https://github.com/corinnepw what are your thoughts on the
importance of where the donate link is in the main nav? I feel like you
have the best perspective on how easily people are able to find out that
information.
—
Reply to this email directly or view it on GitHub
https://github.com/girldevelopit/gdi-new-site/issues/196#issuecomment-74009447
.

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup | @gdihouston
| @staceyyturnage

@staceyturnage I think case studies/research from reputable sources on the placement of the donate button versus examples of NPO sites are more informative. See some below.
@juliaelman basically all of the research I've done over the past couple months has been to include it prominently on the main nav and to even make it a different color to help it stand out.
I believe @Cara-Jo may have some thoughts on this as well
The most upvoted answer on this UX Stack Exchange forum has some great info about making the donate button prominent and included in the main nav.
Here's an excerpt: Donate button is THE element to be featured throughout a non-profit's website. It should be easily visible everywhere. You shouldn't worry about being "too pushy" because donations fuel non-profits.
If you put it into a menu or the footer, you're going to destroy collections because it won't be visible to the majority of visitors.

I believe it should remain where it is, and after some user testing down the line, we should figure out whether or not we want to change the color to make it stand out more.

It was a simply a suggestion it can remain where it is.
As a potential donor I would want to know about the organization before I
was asked to donate, just my opinion.
Stacey
On Wed, Feb 11, 2015 at 10:40 PM, Corinne<EMAIL_ADDRESS>wrote:

@staceyturnage https://github.com/staceyturnage I think case
studies/research from reputable sources on the placement of the donate
button versus examples of NPO sites are more informative. See some below.
@juliaelman https://github.com/juliaelman basically all of the research
I've done over the past couple months has been to include it prominently on
the main nav and to even make it a different color to help it stand out.
I believe @Cara-Jo https://github.com/Cara-Jo may have some thoughts on
this as well
The most upvoted answer on this UX Stack Exchange
http://ux.stackexchange.com/questions/16088/ideal-location-for-a-donate-button
forum has some great info about making the donate button prominent and
included in the main nav.
Here's an excerpt:
Donate button is THE element to be featured throughout a non-profit's
website. It should be easily visible everywhere. You shouldn't worry about
being "too pushy" because donations fuel non-profits. If you put it into a
menu or the footer, you're going to destroy collections because it won't be
visible to the majority of visitors.

I believe it should remain where it is, and after some user testing down
the line, we should figure out whether or not we want to change the color
to make it stand out more.
—
Reply to this email directly or view it on GitHub
https://github.com/girldevelopit/gdi-new-site/issues/196#issuecomment-74016716
.

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup | @gdihouston
| @staceyyturnage

This makes for a good discussion, @staceyturnage, and I'm glad you brought it up. It's good that we're all posting examples to help decide this direction. I checked out other organizations similar to ours and noticed a pattern in very loud DONATE buttons, which can be fitting for groups that aren't backed by giant companies or even the government.
Let's get through launch and keep tabs on immediate feedback and maybe we'll have a good idea of what does and doesn't work in the near future :+1:
Thanks, lady!

I'm not asking for it to be removed from the page I'm simply asking can it
be repositioned. I have no problem with it being prominently displayed but
the first thing a potential donor sees I don't know if that's a good thing.
As I mentioned before I'm coming from a user's prospective and what better
way to see that is to look @ other nonprofit's websites (end result of the
development process).
Or here's a thought maybe it shouldn't say "donate" maybe it should say
"support us" but again whatever is decided is fine with me.
Stacey
On Wed, Feb 11, 2015 at 10:43 PM, Stacey Turnage<EMAIL_ADDRESS>wrote:

It was a simply a suggestion it can remain where it is.
As a potential donor I would want to know about the organization before I
was asked to donate, just my opinion.
Stacey
On Wed, Feb 11, 2015 at 10:40 PM, Corinne<EMAIL_ADDRESS>wrote:

@staceyturnage https://github.com/staceyturnage I think case
studies/research from reputable sources on the placement of the donate
button versus examples of NPO sites are more informative. See some below.
@juliaelman https://github.com/juliaelman basically all of the
research I've done over the past couple months has been to include it
prominently on the main nav and to even make it a different color to help
it stand out.
I believe @Cara-Jo https://github.com/Cara-Jo may have some thoughts
on this as well
The most upvoted answer on this UX Stack Exchange
http://ux.stackexchange.com/questions/16088/ideal-location-for-a-donate-button
forum has some great info about making the donate button prominent and
included in the main nav.
Here's an excerpt:
Donate button is THE element to be featured throughout a non-profit's
website. It should be easily visible everywhere. You shouldn't worry about
being "too pushy" because donations fuel non-profits. If you put it into a
menu or the footer, you're going to destroy collections because it won't be
visible to the majority of visitors.

I believe it should remain where it is, and after some user testing down
the line, we should figure out whether or not we want to change the color
to make it stand out more.
—
Reply to this email directly or view it on GitHub
https://github.com/girldevelopit/gdi-new-site/issues/196#issuecomment-74016716
.

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup |
@gdihouston | @staceyyturnage

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup | @gdihouston
| @staceyyturnage

---------- Forwarded message ----------
From: Stacey Turnage<EMAIL_ADDRESS>Date: Wed, Feb 11, 2015 at 10:50 PM
Subject: Re: [gdi-new-site] Move the Donate Link (#196)
To: girldevelopit/gdi-new-site <
<EMAIL_ADDRESS>
I'm not asking for it to be removed from the page I'm simply asking can it
be repositioned. I have no problem with it being prominently displayed but
the first thing a potential donor sees I don't know if that's a good thing.
As I mentioned before I'm coming from a user's prospective and what better
way to see that is to look @ other nonprofit's websites (end result of the
development process).
Or here's a thought maybe it shouldn't say "donate" maybe it should say
"support us" but again whatever is decided is fine with me.
Stacey
On Wed, Feb 11, 2015 at 10:43 PM, Stacey Turnage<EMAIL_ADDRESS>wrote:

It was a simply a suggestion it can remain where it is.
As a potential donor I would want to know about the organization before I
was asked to donate, just my opinion.
Stacey
On Wed, Feb 11, 2015 at 10:40 PM, Corinne<EMAIL_ADDRESS>wrote:

@staceyturnage https://github.com/staceyturnage I think case
studies/research from reputable sources on the placement of the donate
button versus examples of NPO sites are more informative. See some below.
@juliaelman https://github.com/juliaelman basically all of the
research I've done over the past couple months has been to include it
prominently on the main nav and to even make it a different color to help
it stand out.
I believe @Cara-Jo https://github.com/Cara-Jo may have some thoughts
on this as well
The most upvoted answer on this UX Stack Exchange
http://ux.stackexchange.com/questions/16088/ideal-location-for-a-donate-button
forum has some great info about making the donate button prominent and
included in the main nav.
Here's an excerpt:
Donate button is THE element to be featured throughout a non-profit's
website. It should be easily visible everywhere. You shouldn't worry about
being "too pushy" because donations fuel non-profits. If you put it into a
menu or the footer, you're going to destroy collections because it won't be
visible to the majority of visitors.

I believe it should remain where it is, and after some user testing down
the line, we should figure out whether or not we want to change the color
to make it stand out more.
—
Reply to this email directly or view it on GitHub
https://github.com/girldevelopit/gdi-new-site/issues/196#issuecomment-74016716
.

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup |
@gdihouston | @staceyyturnage

--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup | @gdihouston
| @staceyyturnage
--
STACEY TURNAGE | Founder | Girl Develop It Houston |
<EMAIL_ADDRESS>| girldevelopit.com | Houston Meetup | @gdihouston
| @staceyyturnage

@staceyturnage thank you for your thoughtful feedback and for initially posting this issue! While I see your point of view as the user, I also see @corinnepw point and the articles of evidence she provided to support this decision.
I am going to close this issue, but the website team will definitely keep their ears to the ground to hear what our users think post launch. It might help putting specific analytics on the button to see how many click throughs we get when the link is in one place vs. the other? We could use something like Optimizely to do the testing! \o/ But then... that would be on another issue.
@staceyturnage thank you again for your continued insight and feedback on this project! It is very much appreciated!!!!


gradle properties update

Just a bump to the dev branch for version.

The app is vastly faster all of a sudden, it's true.

Thank you -- glad to know that at least in this one instance, I'm not crazy. :)

And, yeah, like vastly :)  What's up with that?!

Non-debug versions of Java client/ML?

I don't think so; there is no debug Java Client API version.  And actually, middle tier and marklogic times didn't speed up at all.  It's all in the browser tier.  (And believe me I've been looking at query times in web developer tools plenty).  Streaming parse in the browser would explain it; could that have changed?

That's interesting and surprising.
I will take some time to figure out which commit(s) seem to have done it... my first guess is that one of the dependencies may have been running slowly for some reason, because the timing of this sudden improvement doesn't correspond with any memory I should have of changing the browser app in a way that would have this effect -- e.g. I didn't suddenly write code that would change the way responses are oarsed. But shortly before release, the dependencies were updated and locked down at higher versions than we had been previously using, hence my only-slightly-educated guess.

On second thought, I did monkey with the httpInterceptor while we were pursuing CSRF....

late to the party on this but why is it changed to a snapshot version? what does that mean?

This is closed as subsumed in #587.


Support for Java multiline comments

please add the multi line comments for java:
multiLineComment:  ['/*', '*', '*/']

This has been merged to master


Remove AggregateExpr::create_accumulator

Is your feature request related to a problem or challenge?
AggregateExpr currently provides both the ScalarValue based Accumulator and the new GroupsAccumulator interface. With an additional groups_accumulator_supported to indicate if GroupsAccumulator is supported.
This is unfortunate as it forces us to keep two accumulator implementations for each expression, which is not only wasteful but introduces the possibility of inconsistency between the two implementations
Describe the solution you'd like
Change AggregateExpr::create_accumulator to return GroupsAccumulator, and remove groups_accumulator_supported and create_groups_accumulator. Implementations that currently only have an Accumulator based implementation can return a GroupsAccumulatorAdapter, which is ultimately what GroupedHashAggregateStream will do anyway
Describe alternatives you've considered
No response
Additional context
This blocks https://github.com/apache/arrow-datafusion/issues/6842

I think updating AggregateExpr which is largely an internal implementation detail of DataFusion, to better communicate what is supported and what is not makes a lot of sense to me.
I think there are two accumulators now because Accumulator has an API to do retractable updates (incremental updates)
Accumulator is part of the public API so I don't think it can / should be removed

The only thing that might be tricky with this proposal is making sure the right implementation is provided for accumulators that can do retractable updates (like sum and count)


Play tracks uniquely

Is there a test for this feature? I am seeing this:
-            requestMatcherTypes: [.URL])
 +            turntableConfiguration: TurntableConfiguration(requestMatcherTypes: [.URL]))

But could we test when the configuration allows to not play tracks uniquely?

Good catch! Test included :white_check_mark:

Great :sparkles:

:truck:


chore: Update instructions on how to get SDK version

The issue template seems to be referencing https://github.com/golang/dep which is deprecated. Also the command was missing a closing double quotes ".
This PR updates the issue template to use go list -m <module>

[x] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[x] Tests are included and/or updated for code changes.
[x] Updates to module CHANGELOG.md are included.
[x] MIT license headers are included in each file.

/check-enforcer override


fix: Disable SERVICE_MANAGER_ADDR & ETH_RPC as mandatory

Changes proposed
Fixes a config processing bug where cert verification can be disabled but the application will crash since the service manager and eth rpc params are still required even-though they shouldn't be.

How/where does the proxy crash? If we are using the latest version of eigenda_client (which I think we are?), those fields are actually mandatory, even if we don't do cert checking.


[Paid Services - Documentation] MP API Tutorials

Tracing history via MP forums

MicroProfile Tutorial Bid Proposal
Funding MicroProfile Tutorial with 2023 Budget

[microprofile-wg] MicroProfile tutorial update

[
Creating the Official MicroProfile Tutorial - Tarun Telang.pdf
Proposal for Creating MicroProfile Tutorial _ Werner Keil.pdf](https://github.com/eclipse/microprofile-marketing/files/13638308/Proposal.for.Creating.MicroProfile.Tutorial._.Werner.Keil.pdf)

Attended MP Marketing Call, 11th December 2022 - 11:30 pm -12:00 pm IST, as per request from Reza and Clark
Attached is the Presentation summarizing my Outline Proposal -
Outline for the Official MicroProfile Tutorial.pdf
I would be joining the upcoming MP Community call to get the above Outline further reviewed.
As recommended in the MP Marketing Call, I would be following format as per Jakarta EE Tutorial - https://jakartaee.github.io/jakartaee-documentation/jakartaee-tutorial/current/index.html
Awaiting contract from Eclipse Foundation to start the work, might need to reconsider the timeline as MPWG is going on holidays. I will update this ticket after signing the contract and will also share queries for the MP Marketing.

Dear @ttelang,
Thank you for your generosity attending today's meeting and introducing yourself while enable many Q&A.
This ticket is now assigned to you and you can use it. 👍  this community collaborated with another wonderful MicroProfiler on a similar written project  2019- Technical White Paper Pro Bono by Lars RÖWEKAMP! #3 that has about 86 comments. Therefore, ASK AWAY!
Below is the core summary, in addition to your notes above, of today's feedback provived by MicroProfilers:

. MP goes into End of the Year Vacation from Dec 16th to January 7th.

The milestones listed in Creating.the.Official.MicroProfile.Tutorial.-.Tarun.Telang must be postpone to enable MP feedback.

During the MP Holiday period, The Tutorial contract agreement needs to be signed directly with the EF team. Reza will connect you via the MPWG forum with the respective EF members.  Those conversations with the EF are expected to be private.  You are most welcomed to use this ticket to communicate when the agreements are signed and you are a GO to initiate your Research, if any, during the Holiday period.

MPWG Charter should help you navigate your contributions and collaboration with the MP Community. As mentioned today, MP's Openness is 1 of the 7 pilars that ought to be protected while adding value applicable to the ecosystem.

Requests @ttelang,

Can you please provide your email? Why?

As of follow up, I created a google drive space for you in the MP community folder under MP>Content

Tarun Teland - Folder
no contains the Outline & Proposal
Yet, you can use it to drop any other documentation as you see fit.  The access is Public View, restricted Edit.

We need your email to give you Editor's access to own the folder and manage it.

@aeiras - thanks for creating the Google Drive space. For granting edit permissions, my email id is<EMAIL_ADDRESS>

Still awaiting the contract, shared my mailing address to Dennis who is drafting the contract.
Could not join MP Community call as its schedule was 1 am (IST) as per my local time.
Reze has introduced me to Kito to provide me pointers regarding leveraging Jakarta EE Tutorial.

I have shared following queries to Kito via email. While, I am awaiting response, others may also respond here in case any further inputs.
I see there are two formats used for Jakarte EE tutorials:
(1) https://eclipse-ee4j.github.io/jakartaee-tutorial/ (Old one)
(2) https://jakartaee.github.io/jakartaee-documentation/jakartaee-tutorial/current/index.html (New one)

Is the second one (2) the right format for creating the new Microprofile tutorial ?

I am referring the following repositories and planning to create MicroProfile tutorial on similar lines:

https://github.com/jakartaee/jakartaee-tutorial
https://github.com/eclipse-ee4j/jakartaee-examples
https://github.com/jakartaee/jakartaee-documentation-ui/

From the above repos, I understand that I need to use the following tools to generate the MicroProfile tutorials:

AsciiDoc (https://asciidoc.org/)
Antora (https://antora.org/)

Is my understanding correct, kindly correct me or share any further details if I am missing out something.
Is there any recommended diagramming tool for creating architecture diagrams?
Is there any style guide for architecture diagrams that I should follow?

@aeiras - thanks for creating the Google Drive space. For granting edit permissions, my email id is<EMAIL_ADDRESS>
Dear Tarun,
Thank you for getting back to me so quickly. Your editor access has been sent this AM. Welcome to MPWG, contributing via Google Drive as well. :)

I am glad the extra resources provided via this ticket are valuable to your initial MP research.
You are already helping improve things in MP with the ticket you submitted. Amazing OSS form, Tarum. You got this! :)

As we start the MP Holiday brake on the 8th of January, I wish you a beautiful Holiday and a happy end of 2023!

Following Items have been discussed so far:

I will be preparing the MicroProfile Tutorial as per the format -
https://jakartaee.github.io/jakartaee-documentation/jakartaee-tutorial/current/index.html

The content would be written as per Jakarta EE Tutorial Style Guide

Diagrams will be created using draw.io as per the guidelines at this page - [Jakarta EE Tutorial - Creating Diagrams]- https://github.com/jakartaee/jakartaee-tutorial/blob/main/CONTRIBUTING.md#creating-diagrams.

I am planning to store the assets of the MicroProfile Tutorials in the following repositories:

S.N
Repo
Purpose

1.
https://github.com/eclipse/microprofile-tutorial
Content of the MicroProfile Tutorial

2.
https://github.com/eclipse/microprofile-documentation
Builds documentation site using the Antora Playbook.

3.
https://github.com/eclipse/microprofile-documentation-ui
HTML and CSS assets used for the look and feel of the documentation site.

4.
https://github.com/eclipse/microprofile-examples
Example source code used inside the Tutorial content

I need to finalize whether 1&4 should be merged or kept separately.

I would be referring How Antora Works to get started with how Antora orchestrator pulls up the content from different repos and generates the UI with content, search, etc.

Thanks Kito for confirming the format and tools via email and sharing the style guides about writing content and creating diagrams.

The tutorial will be based will be based on the currently available latest version of MicroProfile 6.1. Let me know in case, anyone has any other opinion or views on this.

Today (Jan 23, 2024), I attended MP Open API Technical Call today, presented the outline draft document - https://drive.google.com/file/d/1sSy5FyeQM_QYBPWK761XrBAtUtUQx6ye/view?usp=sharing for feedback on the MicroProfile OpenAPI Specification chapter.
Below were some inputs I received:

Link for the recent API changes for MicroProfile OpenAPI post MicroProfile 5.0
https://download.eclipse.org/microprofile/microprofile-open-api-3.1/microprofile-openapi-spec-3.1.html#api_changes_31
For various technical issues or feedbacks, I would be sharing the drafts / outlines in this group - https://groups.google.com/g/microprofile

@ttelang Thank you for joining the MP Technical call yesterday and providing an informative update! As promised on the call, when you are ready to get feedback, please email to the following 2 addresses<EMAIL_ADDRESS><EMAIL_ADDRESS>

This EF issue was created to get the dedicated microprofile-tutorial repo.

Thanks @Emily-Jiang for sharing about MicroProfile google group and working group mailing lists. I have subscribed to these and started a conversation regarding seeking feedback about the MicroProfile API Tutorial. I will engage with these forums for further inputs regularly.

Please find below my revised plan for completing the MicroProfile APIs Tutorial:

Milestone
Deliverables
Date

Design
Final Content Outline and Structure
Done

Milestone 1
Draft Completion for Chapters 1
6th Feb 2024

Draft Completion for Chapters 2
8th Feb 2024

Draft Completion for Chapters 3
10th Feb 2024

Milestone 2
Draft Completion for Chapters 4
12th Feb 2024

Draft Completion for Chapters 5
14th Feb 2024

Draft Completion for Chapters 6
16th Feb 2024

Milestone 3
Draft Completion for Chapters 7
18th Feb 2024

Draft Completion for Chapters 8
20th Feb 2024

Draft Completion for Chapters 9
22th Feb 2024

Draft Completion for Chapters 10
24th Feb 2024

Draft Completion for Chapter 11
26th Feb 2024

Milestone 4
Finalized Tutorial
29th Feb 2024

Best Regards,
Tarun

I am working on this repo - https://github.com/ttelang/microprofile-tutorials. After the new repo within the eclipse organization is created, I would move the content there.

This EF issue was raised to get the dedicated microprofile-tutorial repo created.

Created another issue to chase up as I might have created the previous issue under a wrong team.

I am worried about using the MicroProfile starter as the basis for the tutorial. It creates a mess regarding the variability of JDK/MicroProfile Version/Spec support. Some implementations, like Quarkus, focus on its own starter and not the MicroProfile starter because it is more feature-specific to Quarkus.
Maybe a more appropriate approach is for each runtime to provide a CLI, pom.xml, or instructions for project creation. During the development of the tutorial, I suspect each implementation would have to tweak the instructions as we learn more.

I am worried about using the MicroProfile starter as the basis for the tutorial. It creates a mess regarding the variability of JDK/MicroProfile Version/Spec support. Some implementations, like Quarkus, focus on its own starter and not the MicroProfile starter because it is more feature-specific to Quarkus.
Maybe a more appropriate approach is for each runtime to provide a CLI, pom.xml, or instructions for project creation. During the development of the tutorial, I suspect each implementation would have to tweak the instructions as we learn more.

I attended MP Starter call on 12th Feb 2024. MP6.1 supports is not yet there.
Below is what I am planning to cover.
Introducing readers about generating a new project structure using MicroProfile Starter. Will also add a note like something like below:
IMPORTANT: At the time of writing this tutorial, the latest MicroProfile released version was 6.1. We will not be using MicroProfile Starter to generate the project structure as it does not currently support this version.

@ttelang the github repo https://github.com/eclipse/microprofile-tutorial has been created. You can create PRs to move your materials there.

Below is the list of chapters that are Ready for Review

Chapter 1: Introduction to MicroProfile
Chapter 2: Getting Started with MicroProfile

I will update the above list as soon as more Chapters gets ready for review.

@ttelang the github repo https://github.com/eclipse/microprofile-tutorial has been created. You can create PRs to move your materials there.

@Emily-Jiang - Thanks for getting this repo created. I will start creating PRs in next couple of days for migrating the tutorial content.
We would need 3 more repos as for the MicroProfile API tutorial as mentioned in the table here - https://github.com/eclipse/microprofile-marketing/issues/847#issuecomment-1864488393

@ttelang the github repo https://github.com/eclipse/microprofile-tutorial has been created. You can create PRs to move your materials there.

@Emily-Jiang - Thanks for getting this repo created. I will start creating PRs in next couple of days for migrating the tutorial content.
We would need 3 more repos as for the MicroProfile API tutorial as mentioned in the table here - #847 (comment)

@ttelang we discussed this at the last Technical call. We agreed to just have one repo microprofile-tutorial. You can add multiple modules in that repo.

@ttelang I have the MP Tutorial repo set up for you with Apache License and it is ready for you to create PRs.

@ttelang I have the MP Tutorial repo set up for you with Apache License and it is ready for you to create PRs.

Hi @Emily-Jiang , I have created the following PRs for your review:
#4 - Preface (Front Matter)
#5 - Chapter 1: Introduction to MicroProfile

I am worried about using the MicroProfile starter as the basis for the tutorial. It creates a mess regarding the variability of JDK/MicroProfile Version/Spec support. Some implementations, like Quarkus, focus on its own starter and not the MicroProfile starter because it is more feature-specific to Quarkus.
Maybe a more appropriate approach is for each runtime to provide a CLI, pom.xml, or instructions for project creation. During the development of the tutorial, I suspect each implementation would have to tweak the instructions as we learn more.

The tutorial will take a neutral approach avoid emphasizing any single MicroProfile implementation.

Examples within the tutorial will be centered around MicroProfile specifications
We would be sharing only about the minimal pom.xml containing only the MicroProfile dependency for the specifications covered in the corresponding chapter.
If required, Instructions for using popular implementations (Open Liberty, WildFly, Payara etc.) would be covered in a separate section.
The complete code listing will be provided in separate repository for e.g. eclipse/microprofile-examples

Collaborating with the MicroProfile community, we can seek links to more in-depth guides provided by the implementations themselves.

Created this video tutorial for presenting the content of first three chapters of MicroProfile Tutorial (Milestone 1) - https://youtu.be/O6ERkg5DHZ8

@ttelang Do you have an update? It's been a while and we haven't seen updates on the Google Docs that we review. Are you waiting on an action item from us?

@ttelang  please provide a status update to this issue. Thanks!

@ttelang We'd like to get an update before the steering committee call on Tuesday.
Thanks!

@ttelang Ping. Any updates?


Update package shell quote

Closes https://github.com/advisories/GHSA-g4rg-993r-mgx7

Codecov Report

Merging #89 (5ce62d4) into master (8e72b7c) will increase coverage by 3.48%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
+ Coverage   92.66%   96.15%   +3.48%
==========================================
  Files          23       22       -1
  Lines         477     1923    +1446
==========================================
+ Hits          442     1849    +1407
- Misses         35       74      +39

Flag
Coverage Δ

ubuntu-latest-12
?

ubuntu-latest-14
?

ubuntu-latest-18
96.15% <ø> (?)

windows-latest-12
?

windows-latest-14
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/spawn-posix.js
96.87% <0.00%> (-3.13%)
:arrow_down:

bin/common/parse-cli-args.js
92.82% <0.00%> (-0.43%)
:arrow_down:

lib/spawn.js
100.00% <0.00%> (ø)

bin/run-p/help.js
100.00% <0.00%> (ø)

bin/run-s/help.js
100.00% <0.00%> (ø)

bin/run-p/index.js
100.00% <0.00%> (ø)

bin/run-s/index.js
100.00% <0.00%> (ø)

lib/match-tasks.js
100.00% <0.00%> (ø)

bin/common/version.js
100.00% <0.00%> (ø)

bin/common/bootstrap.js
100.00% <0.00%> (ø)

... and 13 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Strange permission problem on Windows

Cannot access user directories, requires admin privilege. No idea why...
It anyway works with the privilege.

Filed https://github.com/kripken/emscripten/issues/5268


refactor: Update for new service key names and overrides for hyphen to underscore

Dependent on edgexfoundry/go-mod-core-contracts#613
Dependent on edgexfoundry/go-mod-bootstrap#216
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
Service key constants have the edgex- prefix
Issue Number:  #3460 & #3393
What is the new behavior?
Service key constants no longer have the edgex- prefix
Hyphen in Overrides are converted to underscore
Does this PR introduce a breaking change?

[x] Yes
[ ] No

BREAKING CHANGE: Service key names used in configuration have changed.
New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #3462 (98bad9c) into master (5b6776f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3462   +/-   ##
=======================================
  Coverage   40.62%   40.62%
=======================================
  Files         202      202
  Lines       16488    16488
=======================================
  Hits         6699     6699
  Misses       9313     9313
  Partials      476      476

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 7e9ba5b...98bad9c. Read the comment docs.

The prefix in SECURITY.md should be modfied.
Please also modify the config API example in system-agent.yaml, core-data.yaml, and core-metadata.yaml under /openapi/v2/ folder.

@cloudxxx8 , I addressed the YAML files. Remember that the container and host names will still start with edgex- prefix
The SECURITY.md is way outdated and needs many more changes than the scope of this PR. I have created a new issue to address updating it:
https://github.com/edgexfoundry/edgex-go/issues/3476


OSSM-351 Provide an option to istio-must-gather to scrape only selected SMCP

This change should go here instead: https://github.com/openshift/openshift-docs/blob/master/modules/ossm-about-collecting-ossm-data.adoc
It will get pulled in automatically when we do a community release.

This change should go here instead: https://github.com/openshift/openshift-docs/blob/master/modules/ossm-about-collecting-ossm-data.adoc
It will get pulled in automatically when we do a community release.

Oh, so we now source some stuff from the official docs? I thought it was the other way around (but manually).

Yeah, our workflow is weirdly different than vast majority of other projects/teams, even within Red Hat. We do product first, then we backport to community. So, product is our upstream :)

That's how it was requested of us :) I'm just happy to combine efforts so we're not constantly duplicating each other.

Yeah, I'm not talking specifically about docs repo.

Everything in topics and modules is pulled in from product documentation. We have the ability to add patches for Maistra specific content, but ideally all of the docs that engineering and the docs team write are both added directly to the openshift repo and pulled in.


Comments glitches

[x]  1. The reply should firstly appear just in place where it was posted. In another words, it should replace the Form it was created with. It should work this way in all modes (threaded, flat). Then after page reloading it may be placed in necessary position in accordance with current display mode.
https://una.io/page/view-discussion?id=4605

[ ]  2. Try to find solution to show the structured Comment + Sub comments on View Comment page.

Currently the realized mechanism is used on View Comment page only. But theoretically it can be used for all comments lists. But it should be tested first.


escapeForwardSlash="false" is not applied for properties when includeAllProperties="true"

NLog version: 4.7.7.-4.7.9.
Platform: .Net 4.7
Current NLog config
	<layout xsi:type="JsonLayout" escapeForwardSlash="false">
		<attribute name="level" layout="${level:upperCase=true}"/>
		<attribute name="mpath" layout="${event-properties:mpath}"/>
	        <attribute name="props" encode="false" escapeForwardSlash="false">
			<layout xsi:type='JsonLayout' includeAllProperties="true" escapeForwardSlash="false"  />
		</attribute>
	</layout>

What is the current result?
mpath property is passed explicitly via Dictionary and it contains forward slash

mpath property in "props" nested layout has values with "/" escaped
mpath property defined explicitly via attribute properly doesn't have "/" escaped
 {
  "level" : "DEBUG", "mpath": "/api/test.ashx" },
  "props": { "module": "test", "mpath": "\/api\/test.ashx" }
}

Created  #4403 to resolve this missing feature.

Resolved by #4403

NLog v4.7.10 has been released.

thanks a lot for the quick update and NuGet release!


2084 Bug | Roles Data doesn't refresh

This PR fixes an elusive bug: switching safes was not reloading the new safe's roles. IOW, the previous safe's roles would be visible in the new safe's roles page.
Ideally I should've branched off develop and used that as this PR's base, but, alas, I branched off roles-0.2.0/streams instead. Means this fix will make it to develop only when streams does. Not the most terrible thing to have happened in the world, since this was never an urgent bug in the first place.
Also snuck in a tiny update I made to the "today" indicator on the DecentDatePicker component

It's possible to switch Safes without invoking the HomePage component at all (via the search bar). Does this work in that case?
Tested this, the roles don't persist into the next safe

There is another place in the app where resetSafeState() is called. Should this Zustand reset go there, too?
I don't think so. Regardless, all paths to switch safes that I tested didn't persist a previous safe's roles. Also this bug was hard to reproduce in the first place, so while I did test alternate paths, most testing was focused on the reliable edge case where roles were not getting cleared out

@DarksightKellar what is the mechanism that allows the Zustand stores to reset themselves when a Safe is changed through the search bar, if we're not explicitly doing that?

@adamgall I think this useEffect in useKeyValuePairs is the answer:

it's got a daoAddress dependency (and chain id)
getHatsTreeId itself may return null or undefined, so if the context safe has no such events, the "reset" happens, here (which is something I believe you anticipated when building this part out, hence this code):

I don't like relying on this side effect to "clear out" the state. Would prefer that happens more explicitly.

I don't like relying on this side effect to "clear out" the state. Would prefer that happens more explicitly.

@adamgall Hmm I think you've gotten too hung up on the "clear out state" semantic. Hear me out:
useKeyValuePairs is the way to load up a safe's hat tree, regardless. We don't know before checking it if a safe has a tree or not, so getHatsTreeId(safeEvents... could return null or undefined if the context safe doesn't in fact have a (declared) tree. In that case setHatsTreeId will (and should) be called with null or undefined. This is a feature and not a happy accident -- It's not a "clearing out state" side effect, it's a "setting the tree for this safe we have just switched to" intentional effect.
I don't see any need to, somewhere else, do:

listen for safe changes
try to get the new safe's tree
if safe has got no tree, specifically reset the tree store
OR specifically set the tree store if the safe happens to have one.

Actually a better argument would be to rename useKeyValuePairs to something along the lines of useLoadSafeHatsTree, because that is all it is doing. It just so happens to be using the KeyValuePairs contract internally.

@DarksightKellar - to replicate is it as simple as jumping between safe's role pages quickly?

@adamgall / @DarksightKellar - roles jumping between safes issue still appears for me
https://decentdao.slack.com/archives/C06QZTUTKRC/p1722952950606279?thread_ts=1722949970.035939&cid=C06QZTUTKRC


sms.db malformed

Hi,
I have exported sms.db but am unable to use it with sqlite3:
Error: database disk image is malformed
Any idea what could be the issue and how I could troubleshoot?
Thank you.

It seems my database is really corrupted. May not have to do with itunes backup.

@sebay
Any resolution on this? I've run into the same issue.


[test] All log is 404 in argo

http://testing-argo.kubeflow.org/workflows/kubeflow-test-infra/kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4?tab=workflow&nodeId=kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172&sidePanel=logs%3Akubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172%3Amain
The log of element in argo DAG is 404 although the element is succeeded
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172\" not found","r
eason":"NotFound","details":{"name":"kubeflow-tf-operator-presubmit-tfjob-e2e-492-b317aef-225-99c4-3605379172","kind":"pods"},"code":404}

/assign @jlewi

Duplicate of argoproj/argo#777
The work around is to access the logs directly via stackdriver as described here.
@gaocegege @ScorpioCPH You should both have access to stackdriver.

Thanks for your comment!


Fix #3347 and #3348

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR, however we have a fix for the related issues in our pipeline so closing this


Package request: llvm/clang 17/18/19

There are all tools available below llvm 17. However llvm 17 is partially and 18/19 completely missing. Those would be very useful for modern c++23 development.
Even fedora will upgraded to llvm 18 soon.
Add a :+1: reaction to issues you find important.

#296284 is already underway for 18, not sure what you mean by 17 is "partially missing"

@eclairevoyant There are no llvm Packages for llvm 17 only the clang-tools.

No? #258614 was merged months ago.

@eclairevoyant oh I see, I was confused because I cant find them on nix search. I did not notice that the they are not named llvmPackages_17 (they are named only llvmPackages).
Maybe the latest version should have also a package with version name, so it can be locked (which is not possible at the moment).

Oh nice. Sorry for wasting your time.


Auto Closing Brackets

Could you introduce a quick thing that would work similar to auto closing html brackets but with ejs tags?

This should be working already:
https://github.com/Digitalbrainstem/ejs-grammar/blob/2175126dc68b75a2ea28950c2d5031e194bab0f6/language-configuration.json#L27

I think this actually stems from #35. If you can convince the formatter that all previous EJS tags have closed, you then get auto-closing behavior.


Make "title" for the back button clickable as well

ATM , e.g. on https://gui-beta-dandiarchive-org.netlify.app/#/dandiset/000003, we have <-- Dandiset Dashboard where only smaller <-- is clickable and Dandiset Dashboard is just text. IMHO it would be a better UX if the entire <-- Dandiset Dashboard would be a clickable element leading to the dashboard

In this example, Dandiset Dashboard is the title for the current page. I don't think that text should be a link that takes you somewhere else.
Similarly, upon clicking the back arrow, the title reads Public Dandisets. I certainly wouldn't expect that title to be a hyperlink to somewhere else either.

<-- is a weird icon for taking one back to public dandisets.
i think that icon should be changed, but then there is duplication (we already have public dandisets on that page). so ideally it is back but takes you back to where you came from, which at the moment it doesn't. it takes you to public not the specific page of public dandisets you were looking at.
overall it's a misleading UI i think.


lib: thrft: TFDServer.cpp: close not declared

Compile error
lib/thrift/src/thrift/server/TFDServer.cpp:29:19: error: '::close' has not been declared; did you mean 'fclose'?

Looks like we need to include <posix/unistd.h>

Need CONFIG_POSIX_API as well


Support for ~= (PEP440 Compatible Version) specifiers

Describe the issue briefly here.
Environment Versions

Ubuntu 17.04
Python version: 2.7.13
pip version: 9.0.1
pip-tools version: 1.9.0

Steps to replicate

requirements.in contents:

fs==2.0.3

(this is the latest version at the time of writing)
2. $ pip-compile -o requiremets.txt requirements.in
Expected result
requirements.txt is built successfully and contains fs==2.0.3
Actual result
  File "/home/john/.virtualenvs/quote-of-the-day/local/lib/python2.7/site-packages/pkg_resources.py", line 2518, in scan_list
    raise ValueError("Expected "+item_name+" in",line,"at",line[p:])
ValueError: ('Expected version spec in', u'appdirs~=1.4.0', 'at', u'~=1.4.0')

Full output: https://gist.github.com/e-kolpakov/48f3f976b905d2958cd2ce4d39f1c5b2
If you allow some speculation, looks like PEP440 Compatible Version specs are not fully supported by pip-compile or underlying library.

Uhm, sorry for the noise, looks like it was caused by outdated setuptools version: pip install -U setuptools solved the problem.
Might be good to include this into troubleshooting or even actual error message thrown there.


Drop "type" attribute for JavaScript in HTML5

In HTML5 the attribute type="text/javascript"  is no longer needed/optional (it was needed until version 5 of HTML). I believe this level of verbosity is not needed and thus should be dropped.
FWIW it also gives a warning in the W3 validator
https://www.w3.org/TR/html5/document-metadata.html#processing-link-type

You can bodge it away with something like this in the twig-file(s):
{{ assets.css()|replace({ 'type="text/css" ': ''}) }}
{{ assets.js()|replace({ 'type="text/javascript" ': ''}) }}
{{ assets.js('bottom')|replace({ 'type="text/javascript" ': ''}) }}
For instance in the /[THEME]/templates/partials/base.html.twig


Support for Rules

I saw recent versions of Gherkin support the Rule thing along with the ability to add tags. It would be great if tickspec can support this.

Thanks for the suggestion. I believe that it would be nice to stay up to date. Do you know how other implementations handle the rules? Do they manifest in the testing framework in the same way as tags on scenarios?
Anyway, open to anyone to pick this up to add this functionality.

Specflow does support it
https://docs.specflow.org/projects/specflow/en/latest/Gherkin/Gherkin-Reference.html


Firebase Auth Problem

Please fill in the following fields:
Unity editor version: latest
Firebase Unity SDK version: latest
Additional SDKs you are using (Facebook, AdMob, etc.): Email and password
Platform you are using the Unity editor on (Mac, Windows, or Linux): windows
Platform you are targeting (iOS, Android, and/or desktop): android
Please describe the issue here:
UnityEngine.Debug:LogWarning(Object)
Firebase.Platform.FirebaseLogger:LogMessage(PlatformLogLevel, String) (at Z:/tmp/tmp.ZuzGwZSFEs/firebase/app/client/unity/src/Unity/FirebaseLogger.cs:16)
Firebase.FirebaseApp:LogMessage(LogLevel, String) (at Z:/tmp/tmp.AKg9cuw0I4/firebase/app/client/unity/proxy/FirebaseApp.cs:93)
Firebase.AppUtilPINVOKE:FirebaseApp_ReleaseReferenceInternal()
Firebase.FirebaseApp:ReleaseReferenceInternal(FirebaseApp) (at Z:/tmp/tmp.AKg9cuw0I4/firebase/app/client/unity/proxy/FirebaseApp.cs:1000)
Firebase.FirebaseApp:RemoveReference() (at Z:/tmp/tmp.AKg9cuw0I4/firebase/app/client/unity/proxy/FirebaseApp.cs:296)
Firebase.FirebaseApp:Dispose() (at Z:/tmp/tmp.AKg9cuw0I4/firebase/app/client/unity/proxy/FirebaseApp.cs:51)
Firebase.FirebaseApp:Finalize() (at Z:/tmp/tmp.AKg9cuw0I4/firebase/app/client/unity/proxy/FirebaseApp.cs:47)

Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?

I really need help here plss tell me how to solve this issue

Hi @johnnyboiii3020
The warning in your original title (Auth object 0x47ab7fe0 should be deleted before the App) is normal.
This is due to that C# GC can finalize any object in any order and from any thread.
Second thought, we probably should make it as a debug log.
About the stack trace in your edited post, is it a crash or just for the warning log?
Please let us know.  Thank you.

Hi @johnnyboiii3020 , please let us know if this is still an issue.
--Patrick


Update log4s to 1.9.0

Updates org.log4s:log4s from 1.6.1 to 1.9.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.log4s", artifactId = "log4s" } ]

labels: library-update, semver-minor

Superseded by #124.


support config cache

Closure will make laravel config:cache cause error
change default config section 'calculations' behavior to support 'php artisan config:cache'

Thank you for this. I thought about it for a while, and decided that a cleaner way would be to create a separate (user-selectable) calculations class. I'm adding that now.


memory reachable through globals is not a leak

Blocked on https://github.com/rust-lang/rust/pull/70762
Fixes https://github.com/rust-lang/miri/issues/940

@bors r+

:pushpin: Commit 7841f445932096adcf07944b707af73fc73830f1 has been approved by RalfJung

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 325682ad56d23369059ea93d5a8d44e5782e41cf to master...


Add a "update dependencies" entry for PR checklist

Summary
To ease dependencies updates, a new entry in the checklist for pull requests asks for people making PRs to also run the update-dependencies make target (see this comment in another PR)
This should help for the releases process, as we will not have to do this manually for each released package.
I'm not 100% sure about the wording, so feel free to make this more user-friendly :)

This was my suggestion, but after discussing we decided not to do this. Instead we should shorten the checklist!