Show circular dependency errors don't show in VSCode

It looks like "dependency cycle" errors from the compiler don't show in VSCode.
It would be great to have these appear in the Problems tab, if possible.

There's an issue for this in the rescript-compiler repo: this is not picked up as the error message is not printed indented.

Thanks @cristianoc, I'll close this issue then.

Related: https://github.com/rescript-lang/rescript-compiler/issues/5229


Typo in the menu in Russian

Description
There is a typo in the "База данных" (Database) menu option in Russian language. Should be "Новое соединение из JDBC URL" instead of "Новое соездинение из JDBC URL".

DBeaver Version
Community Edition <IP_ADDRESS>211202223
Operating System
Windows 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Thank you for bug report.


plusTime does not evaluate data access in amount

The plusTime operator does not evaluate data access values in the amount node. Additionally, in our tests, Jackson parsed the value 0 as a DoubleNode, causing the evaluatePlusTime method to throw an exception since it expected an IntNode for amount.
Consider adding support for evaluating data access in the plusTime amount as well as checking if the node is a numerical type instead of forcing it to be an IntNode:
internal fun evaluatePlusTime(dateOperand: JsonNode, amount: JsonNode, unit: JsonNode, data: JsonNode): JsonDateTime {
	var numericalNode = amount
	if (numericalNode is ObjectNode) {
		numericalNode = evaluate(amount, data)
	}

	val longAmount = if (numericalNode.isNumber) {
		numericalNode.longValue()
	} else {
		throw RuntimeException("\"amount\" argument (#2) of \"plusTime\" must be a number")
	}

	if (!isTimeUnit(unit)) {
		throw RuntimeException("\"unit\" argument (#3) of \"plusTime\" must be a string 'day' or 'hour'")
	}

	val timeUnit = TimeUnit.fromName(unit.textValue())
	val dateTimeStr = evaluate(dateOperand, data)
	if (dateTimeStr !is TextNode) {
		throw RuntimeException("date argument of \"plusTime\" must be a string")
	}
	return JsonDateTime.fromIso8601(dateTimeStr.asText()).plusTime(longAmount, timeUnit)
}

OK, will look into the 0 as DoubleNode-problem right away.
As for making the amount operand a CL expression: what's the use case for this? Do you have to implement a concrete business rule that really requires that?
I'm happy to add things like that, but in the short term it's in our own interest to keep the language as small as we can get away with, so we can test it as well as we can, and provide things like a sound type system as soon as possible.

@M-Wong I have trouble reproducing the “0 as DoubleNode”-problem. Can you share a test/code that exposes it?

@dslmeinte Regarding the "0 as DoubleNode"-issue: Sorry to have raised this with you, turns out that was an issue on our side. We load our certlogic json from a server with additional information. Part of that is deserialized into data classes, while the logic is kept as a string, since it's anyway just passed down to Jackson and the certlogic class. However, our deserializer (Moshi) automatically converted integers to doubles even when kept as strings, hence Jackson would receive 0.0 instead of the original 0. We managed to fix this by configuring Moshi differently.
Regarding the amount operator: We configure certain offsets and validity time ranges inside the value sets that we reference from the plusTime operator, since we also use those values in other places of the app.
Example:
"plusTime": [
  {
    "var": "payload.t.0.sc"
  },
  {
    "var": "external.valueSets.acceptance-criteria.rat-test-validity"
  },
  "hour"
]

The field external.valueSets.acceptance-criteria.rat-test-validity also comes from the server and is used for certlogic as well as other logic within the application. To make sure we use the same values everywhere, we used the var data access syntax in the plusTime operator.

@M-Wong Regarding “0 as DoubleNode”: OK, thanks for clearing that up. I'll add a unit test to check whether Jackson has the expected behaviour nevertheless.
Regarding the evaluatable amount operand: the value sets are governed by an official EU body, so it's not possible to add value sets. Even if that were possible, it's not possible to add extra fields like this.
You could add additional external parameters (to the external object) to pass in extra data you think you need in your validation rules, but that's not regulated so would be an obstacle to other Member States being able to validate against your validation rules.
In this case, I would say: just put in the number of hours explicitly, as an integer value. Parametrizing rules like this anyway makes them less immutable than they're supposed to be. I'm assuming rat-test-validity is something like 72 hours?

@dslmeinte True, i guess our acceptance-criteria dictionary is misplaced in the valueSets property, it should be placed directly within external. Yes, rat-test-validity is 72 hours, and we also parametrized other validity values to reduce mistakes when reusing the same values. But I agree that this reduces the compatibility with other states and their validation rules. So in that case you can close this issue if an evaluatable amount is not desireable at this moment.

Glad to find ourselves on the same page! Will close the issue.
Thanks for investing time in CertLogic! :)


Allow actor items to refer to items from the foundry database

The items added to an actor's inventory should be able to refer to an item from the foundry database for its base name, short description and reference.
Using features from Foundry v11 we need to extend the allowed item types to insert our own that replicates DnD5e items. From that sheet we then pick the name and short description to show in the inventory. (Unless customized.)

[x] Add custom item type to the system
[ ] Add sheet for the item type based on the DnD5e item sheets
[x] Make actor item retrieve referenced item's name and short description

Current issues remaining:
The custom item sheet needs to be expanded,
and it doesn't save properly.


Slices: Wrong type for custom types

Setup:

"prismic-javascript": "^1.1.5",
Two custom types (home_page and tip). tip is used in a slice of home_page
Master language is de-ch and a 2nd language fr-ch

If I query the master language the custom types in slice.items is correct ("type": "tip",)
JS:
  const client = await Prismic.api(`https://${repositoryName}.prismic.io/api/v2`, { accessToken })
  const response = await client.query("", {lang: "de-ch"})

Result
{
  "id": "XKXobhAAAJmVNCNu",
  "type": "home_page",
  "lang": "de-ch",
  "data": {
     ...
    "body": [
      {
        "slice_type": "content",
        "items": [
          {
            "tip": {
              "id": "XKbxCxMAACIAP_bb",
              "type": "tip",
              "lang": "de-ch"
            }
          }
        ]
      }
    ]
  }
}

But when I query a non-master language I get "type": "home_page", as type for the custom type
JS:
  const client = await Prismic.api(`https://${repositoryName}.prismic.io/api/v2`, { accessToken })
  const response = await client.query("", {lang: "fr-ch"})

Result
    {
      "id": "XKXzwxAAAByKNFXn",
      "type": "home_page",
      "lang": "fr-ch",
      "data": {
       ...
        "body": [
          {
            "slice_type": "content",
            "slice_label": null,
            "items": [
              {
                "tip": {
                  "type": "home_page",
                  "lang": "fr-ch",
                 }
              }
            ]}
        ]
      }
    },

Any idea why?
Thanks!

Actually it looks like its a general problem of the API. I did a dummy repo to test.
While the master language returns the right (chi) type for results.[type="paren"]. data.child.type the 2nd language does not.

master language: https://content-type-test.prismic.io/api/v2/documents/search?ref=XKd5ThMAAPwpQlHb#format=json
2nd Language: https://content-type-test.prismic.io/api/v2/documents/search?ref=XKd5ThMAAPwpQlHb&lang=de-ch#format=json

The issue was identified and it's related to the translation from one
locale to another.
We already released a fix to prevent that from happening again and another
fix will be released on Monday for already corrupted links.
Sorry for the inconvenience.
Le ven. 5 avr. 2019 à 18:07, Marcel Eyer<EMAIL_ADDRESS>a
écrit :

Actually it looks like its a general problem of the API. I did a dummy
repo to test.
While the master language returns the right (chi) type for
results.[type="paren"]. data.child.type the 2nd language does not.

master language:
https://content-type-test.prismic.io/api/v2/documents/search?ref=XKd5ThMAAPwpQlHb#format=json
2nd Language:
https://content-type-test.prismic.io/api/v2/documents/search?ref=XKd5ThMAAPwpQlHb&lang=de-ch#format=json

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prismicio/prismic-javascript/issues/86#issuecomment-480332412,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFtiX2stpsYKroUdTVgBafbrK426i6eEks5vd3TagaJpZM4ce7M1
.

Thanks for the answer! Looking forward for the fix!

@arnaudlewis it works with a new created repo! Thanks!

Hi @arnaudlewis
There is still similar bug with i18n and custom types. Looks like its related to the Single Type custom type:
master language: https://broken-content.prismic.io/api/v1/documents/search?ref=XKsVyRMAAEqPUjE1#format=json
oah: {
  type: "Link.document"
  value: {
  document: {
    id: "XKsRthMAAO6UUh79"
    type: "child"
    tags: [ ]
    lang: "en-us"
    slug: "child-title-en"
}

2nd language (document object is missing): https://broken-content.prismic.io/api/v1/documents/search?ref=XKsVyRMAAEqPUjE1&lang=de-ch#format=json
{
oah: {
  type: "Link.document"
  value: "=&=033XKsR0hMAAO6UUh96%%parent-single%%"
  }
}

Or do I something wrong?

The fix is coming today to resolve this issue.
I'll keepyou posted ;)
Le lun. 8 avr. 2019 à 11:46, Marcel Eyer<EMAIL_ADDRESS>a
écrit :

Hi @arnaudlewis https://github.com/arnaudlewis
There is still similar bug with i18n and custom types. Looks like its
related to the Single Type custom type:
master language:
https://broken-content.prismic.io/api/v1/documents/search?ref=XKsVyRMAAEqPUjE1#format=json
oah: {
type: "Link.document"
value: {
document: {
id: "XKsRthMAAO6UUh79"
type: "child"
tags: [ ]
lang: "en-us"
slug: "child-title-en"
}
2nd language (document object is missing):
https://broken-content.prismic.io/api/v1/documents/search?ref=XKsVyRMAAEqPUjE1&lang=de-ch#format=json
{
oah: {
type: "Link.document"
value: "=&=033XKsR0hMAAO6UUh96%%parent-single%%"
}
}
Or do I something wrong?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prismicio/prismic-javascript/issues/86#issuecomment-480762458,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFtiXxAtOdSnMwnPRHJGkx_gEeIJkerGks5vew_sgaJpZM4ce7M1
.

The fix was released.


Wrong type argument

Currently try to work with sayid (still in spacemacs), but whenever I try to initiate a trace, I'm getting this error: sayid-write-resp-val-to-buf: Wrong type argument: listp, 19
Debugger entered--Lisp error: (wrong-type-argument listp 19)
  sayid-put-text-props(((0 19 (("start" 0) ("start-col" 0))) (19 39 (("start" 19) ("start-col" 0)))) #<buffer *sayid-traced*>)
  sayid-write-resp-val-to-buf(("Traced namespaces:\n\n\nTraced functions:\n" ((0 19 (("start" 0) ("start-col" 0))) (19 39 (("start" 19) ("start-col" 0))))) #<buffer *sayid-traced*>)
  sayid-setup-buf(("Traced namespaces:\n\n\nTraced functions:\n" ((0 19 (("start" 0) ("start-col" 0))) (19 39 (("start" 19) ("start-col" 0))))) t nil)
  sayid-req-insert-content(("op" "sayid-show-traced" "ns" nil))
  sayid-show-traced()
  sayid-remove-trace-fn()
  call-interactively(sayid-remove-trace-fn nil nil)
  command-execute(sayid-remove-trace-fn

In this case I was trying to remove a trace from this function:
(defn transitive [s]
    (let [val-map (apply hash-map (flatten (vec s)))
          find-relations (fn find-relations [key]
                           (let [result (get val-map key)]
                           (if result
                             (lazy-seq (cons result (find-relations result))))))]
      (reduce (fn [coll item]
                (map (fn [x]
                       [item x]) (find-relations item)))
              #{} (keys val-map))))

I get similar errors when enabling a trace or creating an inner trace. Creating an inner trace does cause the trace to appear on the sayid-traced buffer. Just enabling a trace does not making it appear in the traced buffer. In either case, the results do not appear in the sayid workspace when I run the method.

Is this something that worked before and doesn't now?
Are you using the latest version (0.0.14) of sayid in clojure and emacs? The emacs package is now (as of yesterday) on MELPA.
If you have the right versions, running sayid-version in elisp should give you this:
clj=0.0.14 el=0.0.14
Let me know whether that's it.

Hmmm.... tracing individual functions (C-c s t e' or sayid-trace-fn-enable`) isn't working for me, although I don't get an error. I always trace by ns, so I must've broken this and not caught it.
Your error may be unrelated though.

Ok I'll trace by ns. I am using the melpa version I believe. I got this: clj= el=0.0.14 when I ran sayid-version. Which is a bit weird, do I have clojure not set up right in my setup?

ok, yeah you're using v0.0.11 or earlier of the sayid clj lib, which is not going to work with v0.0.14 of the emacs client (which you are using). You need to bump up to sayid v0.0.14 wherever you include it -- profiles.clj or project.clj I'd expect.

I see. A little deja-vu since last time I made this kind of error. A better error message for a mismatched version would be great. Thanks for helping me with this!

Ha, true. I actually did add the other message you requested, but didn't get to comment/closing the ticket yet.
https://github.com/bpiel/sayid/issues/11

I might have looked at the previous error to get a hint at the issue :)

Added an issue for the bug I noted above
https://github.com/bpiel/sayid/issues/23


PWA name not being rendered

Although the name is available on the manifest, it is not being correctly extracted from the manifest or incorrectly being rendered on the UI.

Fixed by #40


[Question] How can i generate Messages.class?

Describe the bug
I can't find this anywhere and to compile I need this.
The only thing i could do is extract from the jar and copy it to the projec

Run the build task before syncing your ide


⚠ Bofrost.be has degraded performance

In 3808539, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1323 ms

Resolved: Bofrost.be performance has improved in 42a8498 after 6 minutes.


missing 'score' attribute breaks nose's "-p" at verbosity level 2

Using nose 1.1.2 and django-nose 0.1.3, printing the list of plugins at verbosity level 2 throws the following exception:
$ ./manage.py test -p --verbosity 2
Plugin django setup
Traceback (most recent call last):
  File "./manage-dev", line 11, in <module>
    execute_manager(settings)
  File "/home/abeld/WORK/myproject/env/src/django/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/home/abeld/WORK/myproject/env/src/django/django/core/management/__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/abeld/WORK/myproject/env/src/django/django/core/management/base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/home/abeld/WORK/myproject/env/src/django/django/core/management/base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/south/management/commands/test.py", line 8, in handle
    super(Command, self).handle(*args, **kwargs)
  File "/home/abeld/WORK/myproject/env/src/django/django/core/management/commands/test.py", line 37, in handle
    failures = test_runner.run_tests(test_labels)
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/django_nose/runner.py", line 85, in run_tests
    result = self.run_suite(nose_argv)
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/django_nose/runner.py", line 49, in run_suite
    addplugins=plugins_to_add)
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/nose/core.py", line 118, in __init__
    **extra_args)
  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
    self.parseArgs(argv)
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/nose/core.py", line 147, in parseArgs
    self.showPlugins()
  File "/home/abeld/WORK/myproject/env/local/lib/python2.7/site-packages/nose/core.py", line 219, in showPlugins
    print "  score: %s" % p.score
AttributeError: 'DjangoSetUpPlugin' object has no attribute 'score'

Based on http://readthedocs.org/docs/nose/en/latest/plugins/interface.html saying "must have the attributes enabled, name and score", I assume it is django-nose's fault for not having that attribute.

Not that I know of; it's the expected behavior. But if you say "Closes #43." in the commit message, that bug will be automatically closed when the pull request is.


chore: initialize RC app

Description
Initializes the basic project along with brief documentation.

Fixes #1

 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 !


Add support for punctuation

Monkeytyper has a mode that adds randomized punctuation to words in a test, such as a period/comma/colon/semicolon at the end of a word (periods making the next word capitalized), a dash between words, or surrounding the word with a delimiter, such as parentheses or quotes.
Would be nice to emulate this, to simulate english prose with all its punctuation without resorting to full book exerpts.

Actually, looking through the codebase, I think this might be something I can pound out over the next while. Ill start working on a PR.


Enable SSL for requests in create_cve_json script

Closes #771.

Should we setup separate CI tests for shell and python scripts that go into the tools folder?

Should we setup separate CI tests for shell and python scripts that go into the tools folder?

That's a good idea, let's open an issue for that


Final Full-stack project Kanban setup

Hi reviewer,
In this full-stack capstone project, we are 5 collaborators. We successfully created the Kanban board according to the project requirement. link.
These are the collaborators:
@TaiwoEnoch
@Tracy-miranja
@danutibe07
@AbdusSattar-70
@Lengushuru Charles

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Highlights

met all project requirements as far as I could see, good job 👍

Optional suggestions

[OPTIONAL] Consider adding labels to your issues, it makes it easier to filter by different types and gives another added level of differentiation among tasks (front-end vs back-end etc.)
[OPTIONAL] Ensure that you are adding realistic weight to your tasks.

Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Hope all is well, and that my comments were helpful. 😸
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Support for tiled web maps

A layer component for Tiled Web Maps would be the next big wish, with the option to supply a array of hostnames
https://openlayers.org/en/latest/examples/xyz.html

Could you please elaborate on the array of hostnames?

in the XYZ Source you have the option to supply URI templates, which are basically the subdomains you can use in the URI
google use mt0 mt1 etc in the XYZ sources
see:
https://openlayers.org/en/latest/apidoc/module-ol_source_XYZ-XYZ.html

Ok. In the current state I simply defined the URL template as element property. So anything that is supported by OpenLayers will work.
<ol-map zoom="7" lat="46.7985" lon="8.2318">
    <ol-layer-xyz url="http://c.tiles.wmflabs.org/hillshading/{z}/{x}/{y}.png"></ol-layer-xyz>
</ol-map>

There is but a single URL parameter. Would that be sufficient?

you would need to have a parameter which supports multiple values for the subdomain to make it work for e.g. google maps

Sure, I can expose the urls array too as input.
What I was referring to is this part of the docs:

A {?-?} template pattern, for example subdomain{a-f}.domain.com, may be used instead of defining each one separately in the urls option.

I suppose that it caters for more typical use cases where the subdomain follows this pattern.

hmm, this part of the docs are a bit vague but I see what you mean


feat: implement custom titlebar matching editor style

If possible, maybe we should draw the "minimize", "maximise", and "close" icons like a normal windows APP with title.

something like this

Normal window:

Maximised window:

Full titlebar:

@dzhou121 few things:

[ ] do we want lapce logo in titlebar? current position is ok? same for colour? which platforms will have logo? for example VSCode has logo on Windows, but not on macOS due to window controls on left side

[ ] do we want title? what should title have? should title be same as "os" title (currently it's workspace/folder name)

[ ] do we want window controls on windows to match perfectly? standard Windows window controls have big padding between each other. they also look a bit blurred(?)

Example of draggable lapce:
https://user-images.githubusercontent.com/50457605/176743017-73656470-f7fa-4fda-9246-50dc7e57a162.mp4

do we want lapce logo in titlebar? current position is ok? same for colour? which platforms will have logo? for example VSCode has logo on Windows, but not on macOS due to window controls on left side

Lapce logo only for Windows.

do we want title? what should title have? should title be same as "os" title (currently it's workspace/folder name)

Probably yes for Windows only.

do we want window controls on windows to match perfectly? standard Windows window controls have big padding between each other. they also look a bit blurred(?)

Yes please if that's not too much of trouble.

The only thing left is to add dynamic title to show workspace name but I haven't figured that out yet. PR can be merged and I'll push fix for title later.
Also, restoring window currently doesn't work from window control, it works on double click on titlebar though.

Thanks!
I'm perfectly happy with it for not showing project name, because it's already at the very left.
The restore thing might be a Druid thing. I can look into that.


Pastanaga theme / manage views

Coverage decreased (-1.07%) to 58.748% when pulling a97df4d58b0281b193b5c7065d1ee5720234b7f3 on pastanaga into baec5a633f0e72218ef68b7654f16dfd337bab3f on master.


El Capitan support

Is there any way I could get this running on El Capitan? It worked perfectly on Sierra but it was too slow and unstable.

Did you try? Did you get a specific error? It should work since the DB is essentially the same.

Yes, I have tried.
First of all, the application is only for macOS 10.12 and above, so it won't, even with the script
When I attempted to change the minimum macOS version in the Info.plist. I got it to run through the script.
However, here is what I get:

most of that’s just part of the script trying to collect crash logs that aren’t there.
The major bit is the Killed: 9. That’s because the app includes symbols/code which only works for >10.12. I’ll try and compile for 10.11 tonight and let you know.

Were you able to get this working on 10.11 by compiling it?

I'm completely lost on how to try to compile this. How would I compile it for El Capitan?

MessageProxy.zip
Let me know if it works. This is a weird dev build since I'm in the middle of a big feature but I've just disabled it so it should be okay. Haven't tested it.

Thank you so much! This worked perfectly. I really appreciated it.

Can you replace the version I attached with a fresh copy downloaded from here? If you don't you won't get auto-updates in the future and that's not great.


Oryx tutorial

Hi
I liked the lambda architecture of Oryx.
I am interested in building a model on Kafka and Spark, but I am new to maven.
Could anyone help me out with getting started with the example wordcount, as I am struggling with errors.
The readme in dev tab is not very clear.
Any tutorial or a few starting steps would help.
I have spark 2.2 installed and kafka 2.12 installed.
I have cloned the git repo and tried with mvn package. It build the jars. But stuck at deploying app/example with oryx-run.sh, throws some errors with spark-submit.

The docs on the oryx.io site should still be correct. Yes, it's going to require some familiarity with Maven, Hadoop, Kafka, Spark, etc to use. You haven't said here what isn't clear nor the problem you're facing, so I'd have to close this.

ok, I made some progress
Now stuck on this:
2019-04-09 16:39:57,966 INFO yarn.Client: Submitting application application_1554852387362_0003 to ResourceManager
2019-04-09 16:39:57,994 INFO impl.YarnClientImpl: Submitted application application_1554852387362_0003
2019-04-09 16:39:57,996 INFO cluster.SchedulerExtensionServices: Starting Yarn extension services with app application_1554852387362_0003 and attemptId None
2019-04-09 16:39:59,001 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:39:59,004 INFO yarn.Client:
client token: N/A
diagnostics: [Tue Apr 09 16:39:57 -0700 2019] Application is added to the scheduler and is not yet activated. Skipping AM assignment as cluster resource is empty.  Details : AM Partition = <DEFAULT_PARTITION>; AM Resource Request = <memory:1024, vCores:1>; Queue Resource Limit for AM = <memory:0, vCores:0>; User AM Resource Limit of the queue = <memory:0, vCores:0>; Queue AM Resource Usage = <memory:0, vCores:0>;
ApplicationMaster host: N/A
ApplicationMaster RPC port: -1
queue: default
start time:<PHONE_NUMBER>978
final status: UNDEFINED
tracking URL: http://eucasnps-03.internal.synopsys.com:8088/proxy/application_1554852387362_0003/
user: hadoop
2019-04-09 16:40:00,006 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:01,008 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:02,010 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:03,011 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:04,013 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:05,015 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:06,017 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:07,019 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:08,020 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:09,022 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:10,024 INFO yarn.Client: Application report for application_1554852387362_0003 (state: ACCEPTED)

This indicates you have some problem with your YARN cluster. It is saying
there are no resources available to you. This is not related to the Oryx
project.
On Tue, Apr 9, 2019 at 6:43 PM Riya Punjabi<EMAIL_ADDRESS>wrote:

ok, I made some progress
Now stuck on this:
2019-04-09 16:39:57,966 INFO yarn.Client: Submitting application
application_1554852387362_0003 to ResourceManager
2019-04-09 16:39:57,994 INFO impl.YarnClientImpl: Submitted application
application_1554852387362_0003
2019-04-09 16:39:57,996 INFO cluster.SchedulerExtensionServices: Starting
Yarn extension services with app application_1554852387362_0003 and
attemptId None
2019-04-09 16:39:59,001 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:39:59,004 INFO yarn.Client:
client token: N/A
diagnostics: [Tue Apr 09 16:39:57 -0700 2019] Application is added to the
scheduler and is not yet activated. Skipping AM assignment as cluster
resource is empty. Details : AM Partition = <DEFAULT_PARTITION>; AM
Resource Request = <memory:1024, vCores:1>; Queue Resource Limit for AM =
<memory:0, vCores:0>; User AM Resource Limit of the queue = <memory:0,
vCores:0>; Queue AM Resource Usage = <memory:0, vCores:0>;
ApplicationMaster host: N/A
ApplicationMaster RPC port: -1
queue: default
start time:<PHONE_NUMBER>978
final status: UNDEFINED
tracking URL:
http://eucasnps-03.internal.synopsys.com:8088/proxy/application_1554852387362_0003/
user: hadoop
2019-04-09 16:40:00,006 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:01,008 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:02,010 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:03,011 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:04,013 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:05,015 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:06,017 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:07,019 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:08,020 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:09,022 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
2019-04-09 16:40:10,024 INFO yarn.Client: Application report for
application_1554852387362_0003 (state: ACCEPTED)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/OryxProject/oryx/issues/358#issuecomment-481479939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyM-rxxguZtUw5XsG3tu8-3Ph1mo7lRks5vfSWkgaJpZM4clJoS
.


Result for all search returning "None"

all methods return none as output.

im facing this issue too.

Same issue. Logging indicates:
2024-07-23 05:17:02 DEBUG Encoding detection: utf_8 is most likely the one.
Encoding is set, per guidelines.
def googleNews(keys: list, num_of_articles: int) -> dict:
google_news = GoogleNews()
google_news.set_lang('en')
google_news.set_period('1d')
google_news.set_encode('utf_8)')
...

google_news.results() should output the results.


[Typo] Delete DiscardingOuputFormat

I don't know if we have any users using this output format.
But I would like to get rid of the wrongly named DiscardingOuputFormat.

+1 good to merge

+1


pytest assertion rewriting does not seem to work with meson editable install

It could well be partially linked to some of the discussion in https://github.com/mesonbuild/meson-python/issues/642 but I thought a separate issue may be worth it.
Description of the issue
The pytest assertion rewriting that shows additional debug information when an assert fails does not show up when using meson editable install. It does work fine when using normal (non-editable) meson install. Although not crucial I would argue that this can be actually quite useful in CI logs.
It could also well be a Pytest issue but I thought I had to start somewhere and chose meson-python.
More background about Pytest assertion rewriting, see Pytest doc that links to a somewhat old blog post but I am guessing is probably still relevant?
This was originally seen in scikit-learn (see https://github.com/scikit-learn/scikit-learn/issues/29253#issuecomment-2173549242 if you are really curious where it would have actually been quite useful to see intermediary values in the AssertionError in https://github.com/scikit-learn/scikit-learn/issues/29253#issuecomment-2167610891). I put together a reproducer below with numpy hoping this makes it a bit easier to look at. I guess a smaller reproducer could be put together if deemed useful, but it would take a bit of time (I tried with https://github.com/dnicolodi/python-siphash24 and I am not able to reproduce the issue).
Get the reproducer from my numpy branch
git clone https://github.com/lesteve/numpy
git checkout meson-editable-pytest-assertion-rewrite

I added a simple test in numpy/tests/test_mine.py
import numpy as np

def test():
    arr = np.arange(100)
    assert arr.sum() < 100

When running with pytest you pytest assertion rewriting shows the value or arr.sum() (see below).
Normal (non-editable) install
pip install --verbose --no-build-isolation .

Note the assertion rewriting i.e. you get the value of arr.sum()
Partial output:
E       assert np.int64(4950) < 100
E        +  where np.int64(4950) = <built-in method sum of numpy.ndarray object at 0x7b77efd7a370>()

Full output
 ❯ pytest --pyargs numpy.tests.test_mine
========================== test session starts ===========================
platform linux -- Python 3.11.7, pytest-8.2.2, pluggy-1.5.0
rootdir: /home/lesteve
plugins: hypothesis-6.103.2
collected 1 item

micromamba/envs/numpy-dev/lib/python3.11/site-packages/numpy/tests/test_mine.py F [100%]

================================ FAILURES ================================
__________________________________ test __________________________________

    def test():
        arr = np.arange(100)
>       assert arr.sum() < 100
E       assert np.int64(4950) < 100
E        +  where np.int64(4950) = <built-in method sum of numpy.ndarray object at 0x7b77efd7a370>()
E        +    where <built-in method sum of numpy.ndarray object at 0x7b77efd7a370> = array([ 0,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 12, 13, 14, 15, 16,\n       17, 18, 19, 20, 21, 22, 23, 24, 25, ...72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84,\n       85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99]).sum

micromamba/envs/numpy-dev/lib/python3.11/site-packages/numpy/tests/test_mine.py:6: AssertionError
======================== short test summary info =========================
FAILED micromamba/envs/numpy-dev/lib/python3.11/site-packages/numpy/tests/test_mine.py::test - assert np.int64(4950) < 100
=========================== 1 failed in 0.82s ============================

Editable install
pip install --verbose --no-build-isolation --editable . --config-settings editable-verbose=true

You don't get the value of arr.sum()
 pytest --pyargs numpy.tests.test_mine
========================== test session starts ===========================
platform linux -- Python 3.11.7, pytest-8.2.2, pluggy-1.5.0
rootdir: /home/lesteve
plugins: hypothesis-6.103.2
collecting ... + /home/lesteve/micromamba/envs/numpy-dev/bin/ninja
[1/1] Generating numpy/generate-version with a custom command
Saving version to numpy/version.py
collected 1 item

dev/numpy/numpy/tests/test_mine.py F                               [100%]

================================ FAILURES ================================
__________________________________ test __________________________________

    def test():
        arr = np.arange(100)
>       assert arr.sum() < 100
E       AssertionError

dev/numpy/numpy/tests/test_mine.py:6: AssertionError
======================== short test summary info =========================
FAILED dev/numpy/numpy/tests/test_mine.py::test - AssertionError
=========================== 1 failed in 1.02s ============================

I don't think anyone active in maintaining meson-python has the time to dig into this. The pytest maintainer are much better positioned to understand where things go wrong. Once we know what the problem is, we can look into fixing it.
I'm very surprised that pytest works for simple packages but not for more complex ones. The editable package loading code does not care whether the package contains an extension module or not. Thus the issue should be reproducible with a pure Python package too.

OK thanks a lot for your insights! I'll try to come up with a simpler reproducer and open an issue in Pytest to see whether they have some intuition where the problem lies.


feat(headless): add headless-numeric-filter & headless-date-filter controllers

PR is a bit big because there is a lot of repetition between date & number, but implementation is very similar
I'd like feedback on this before I go ahead with testing + samples (in upcoming PRs)
Design doc: https://docs.google.com/document/d/1SsCHuHO6Xvb2AklJ6Q9_snN0RKPqqsfyXCRQCubC3lI/edit?ts=60d0ca6c
https://coveord.atlassian.net/browse/KIT-780

Would a commonly shared range filter be useful?


What is the best way is to determine, if the syntax that I would like to add is not conflicting with any other existing extension.

I am working on an extension and I would like to know if my syntax won't be conflicting with any other extension.
What is the best way to achieve that?

There is no easy way outside of the project itself as you figured out in #538.
We would have to ship the tests as a separate NuGet package in order to support that scenario.

If you have concrete examples of syntax in mind, you could ask for feedback on the https://talk.commonmark.org/ forum

Thank you for your responses I will look into the proposed solution.
Would the following spec configuration in SpectFileGen result in enabling ALL extensions?
new Spec("Forms", "FormsSpecs.md", "advanced+pipetables+gfm-pipetables+footnotes+attributes+emphasisextras+hardlinebreak+gridtables+customcontainers+definitionlists+emojis+abbreviations+listextras+mathematics+bootstrap+figures+medialinks+smartypants+autoidentifiers+tasklists+diagrams+nohtml+yaml+autolinks+jiralinks+globalization+forms"),


test31

qwer

Could not find source branch for new issue branch

Could not create PR (Request failed due to following response errors:

Variable $headSha of type GitObjectID! was provided invalid value)


The device profile link is broken

The Device Profile link is broken:
https://learn.microsoft.com/en-us/resources/samples/active-directory-dotnet-deviceprofile/?v=17.23h

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a0ab71a0-a2df-fa37-83fa-080dece952f6
Version Independent ID: f74b7d51-aede-ed93-437e-601654d8fa7e
Content: Get started with the REST APIs for Azure DevOps Services and Team Foundation Server - Azure DevOps Services REST API
Content Source: index.md
Service: azure-devops
Sub-service: azure-devops-ecosystem
GitHub Login: @elbatk
Microsoft Alias: elbatk

Duplicate of #434


Add Skip() and Reset() methods to LittleEndian::Reader

Problem
Reader has no methods for Skip() or Reset(), which may lead users to do potentially unsafe buffer size calculations, such as in #4748.
This is a follow-up to a comment in #4765.
Summary of Changes

add Skip() method to advance the Reader forward a number of octets
add Reset() method to return the Reader to the start pointer it was initialized with

Do we have a usage for this?
I am a bit weary for 'reset' because when getting such a buffer it  may not be clear to what it resets.
Skip seems to not be useful unless the buffer is already initialzed/it has already been written to.
I would like to understand use cases and if we could instead use existing functionality (e.g. one can allways use operator= to reset to a given buffer, but then it has to have knowledge of buffer and size).

Do we have a usage for this?
I am a bit weary for 'reset' because when getting such a buffer it may not be clear to what it resets.
Skip seems to not be useful unless the buffer is already initialzed/it has already been written to.
I would like to understand use cases and if we could instead use existing functionality (e.g. one can allways use operator= to reset to a given buffer, but then it has to have knowledge of buffer and size).

Realized this is for reader ... so skip seems to make sense if data is not required. Maybe SkipBytes is a clearer name.
Still not convinced about reset.

Do we have a usage for this?
I am a bit weary for 'reset' because when getting such a buffer it may not be clear to what it resets.
Skip seems to not be useful unless the buffer is already initialzed/it has already been written to.
I would like to understand use cases and if we could instead use existing functionality (e.g. one can allways use operator= to reset to a given buffer, but then it has to have knowledge of buffer and size).

Realized this is for reader ... so skip seems to make sense if data is not required. Maybe SkipBytes is a clearer name.
Still not convinced about reset.

The use case for this came from #4765 specifically because I wrote some code in TestBdxTransferSession.cpp that would inspect the contents of a PacketBuffer containing a StatusReport message. I needed to read the header and data in the PacketBuffer but not modify the Start pointer so that the message could then be passed to the "peer" node in the test.
In non-test code, this may not be a use case. I assume that it almost all cases, the header of a message will be consumed and then the data will be inspected and there will likely not be a need to reset the Start pointer and consume the header again. But it will make the test code safer and there may be other use cases for being able to reset/skip a Reader.
Would it be more clear to change Reset() to Rewind() or BackToStart()?

Fwiw, we should probably add the uses together with the methods; then it will be clearer why they are useful.

Fwiw, we should probably add the uses together with the methods; then it will be clearer why they are useful.

Just pushed a commit that includes the use case for Skip(). There's currently no pending use case for Reset() that I know of in BDX. Maybe @tcarmelveilleux or @mspang know of a use since they suggested it?

Maybe SkipBytes is a clearer name.

Writer already has Skip.

Writer temporarily had Reset() for use by the PacketBufferWriter subclass, but I removed it again because copy assignment worked just as well, i.e. compilers are smart enough that writer = Writer(…) just resets the LHS.

Writer already has Skip.

True, though it's unused (even in tests), so not sure why it's there...

Do we have a use case for Reset? I'd avoid adding it, and the corresponding extra code, until we decide we really need it.

@bzbarsky-apple @andreilitvin The amount of extra code is minimal. The ability to rewind to start of a buffer to re-read it rather than create a new reader over the same buffer (which will involve more instructions) is a symmetry that has yet to be taken advantage of, but mostly because a lot of cases of manual buffer management still exist.
If you have a reader, a Reset() is a common method. It exists in our internal buffer reader APIs and is trivial.
Trevor wrote the tests and it's an inlined header method so if it's never used, it costs nothing.

Trevor wrote the tests and it's an inlined header method so if it's never used, it costs nothing.

There's a nonzero cost per constructor invocation because of the extra state that needs to get stored, no?  That's why there's a codesize increase even though nothing is using the reset method....
If it were truly zero-cost-unless-used I would be a lot happier with it.

Maybe the right thing to do is to drop the new mBufLen member and have Reset do mAvailable += OctetsRead(); before resetting mReadPtr?  I think that would make this actually zero-cost.

Do we have a use case for Reset? I'd avoid adding it, and the corresponding extra code, until we decide we really need it.

@bzbarsky-apple @andreilitvin The amount of extra code is minimal. The ability to rewind to start of a buffer to re-read it rather than create a new reader over the same buffer (which will involve more instructions) is a symmetry that has yet to be taken advantage of, but mostly because a lot of cases of manual buffer management still exist.
If you have a reader, a Reset() is a common method. It exists in our internal buffer reader APIs and is trivial.
Trevor wrote the tests and it's an inlined header method so if it's never used, it costs nothing.

@tcarmelveilleux I would argue that reset in this context can cause more confusion. Consider this code:

void ProcessData(Reader reader) {
   int data = reader.Read8();
   if (data == 0xFF) {  // if starting with 0xFF, data is 16-bit
      reader.Reset();
      data = reader.Read16();
   }
   return data;
}

It "feels" ok (read something, need to re-read so reset and read again). But it is undefined behaviour because Reader buffer and length are not specified (function may read in the middle of a buffer).
I agree that Reset is very convenient if you create a buffer, do stuff and just need to go totally back.
How about having an equivalent of Tell() and Seek() ?
so you can:
auto pos = reader.Tell();

 if (data == 0xFF) {  // if starting with 0xFF, data is 16-bit
    reader.Seek(pos);
    data = reader.Read16();
 }

this also allows for 0 cost in constructors.
In the current implementation Tell/Seek could be simultated with operator=.

Do we have a use case for Reset? I'd avoid adding it, and the corresponding extra code, until we decide we really need it.

@bzbarsky-apple @andreilitvin The amount of extra code is minimal. The ability to rewind to start of a buffer to re-read it rather than create a new reader over the same buffer (which will involve more instructions) is a symmetry that has yet to be taken advantage of, but mostly because a lot of cases of manual buffer management still exist.
If you have a reader, a Reset() is a common method. It exists in our internal buffer reader APIs and is trivial.
Trevor wrote the tests and it's an inlined header method so if it's never used, it costs nothing.

@tcarmelveilleux I would argue that reset in this context can cause more confusion. Consider this code:
int ProcessData(Reader reader) {
   int data = reader.Read8();
   if (data == 0xFF) {  // if starting with 0xFF, data is 16-bit
      reader.Reset();
      data = reader.Read16();
   }
   return data;
}

It "feels" ok (read something, need to re-read so reset and read again). But it is undefined behaviour because Reader buffer and length are not specified (function may read in the middle of a buffer).
I agree that Reset is very convenient if you create a buffer, do stuff and just need to go totally back.
How about having an equivalent of Tell() and Seek() ?
so you can:
auto pos = reader.Tell();
int data = reader.Read8();
if (data == 0xFF) {  // if starting with 0xFF, data is 16-bit
   reader.Seek(pos);
   data = reader.Read16();
}

this also allows for 0 cost in constructors.
In the current implementation Tell/Seek could be simultated with operator=.

There is more conversation than code. It means we have to simplify. Let's keep Skip() and remove Reset() for now.

There is more conversation than code. It means we have to simplify. Let's keep Skip() and remove Reset() for now.

Agreed. We can revisit this if a use case arises for Reset/Seek


IPAM controllers get stuck in processing subnet which starts with IP address like 0.X.X.X

Bug Report
Type: bug report
What happened
Create a new subnet which starts with IP address like 0.0.0.X, e.g.,
apiVersion: networking.alibaba.com/v1
kind: Subnet
metadata:
  name: testsn
spec:
  network: init
  range:
    cidr: <IP_ADDRESS>/24
    gateway: ""
    version: "4"
    start: "<IP_ADDRESS>"
    end: "<IP_ADDRESS>"

Its status (usage) never gets updated.
By checking metrics of manager, we found that IPAM controllers seems get stuck in processing certain item.
# HELP workqueue_unfinished_work_seconds How many seconds of work has been done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.
# TYPE workqueue_unfinished_work_seconds gauge
workqueue_unfinished_work_seconds{name="GlobalService"} 0
workqueue_unfinished_work_seconds{name="IPAM"} 80509.583495458
workqueue_unfinished_work_seconds{name="IPInstance"} 0
workqueue_unfinished_work_seconds{name="NetworkStatus"} 80509.584626613
workqueue_unfinished_work_seconds{name="Node"} 0
workqueue_unfinished_work_seconds{name="Pod"} 79452.589502282
workqueue_unfinished_work_seconds{name="Quota"} 0
workqueue_unfinished_work_seconds{name="RemoteCluster"} 0
workqueue_unfinished_work_seconds{name="RemoteClusterStatus"} 0
workqueue_unfinished_work_seconds{name="RemoteClusterUUID"} 0
workqueue_unfinished_work_seconds{name="SubnetStatus"} 80509.584568096

What you expected to happen
Usage of newly created subnet can be synced successfully.
How to reproduce it (as minimally and precisely as possible)
Anything else we need to know?
Environment

hybridnet version:
v0.7.5
OS (e.g. cat /etc/os-release):
Kernel (e.g. uname -a):
Kubernetes version:
Install tools:
Others:

try to fix referred package by https://github.com/containernetworking/plugins/pull/782


Fix some temporary string instances; reduce static global objects.

Static global objects: reduce to avoid initialization sequence
issues. For strings, std::string can typically be replaced with
std::string_view or const char*
const string parameters to function calls should never be passed
by value only by reference to avoid a bunch of copies.

Signed-off-by: Henner Zeller<EMAIL_ADDRESS>

Codecov Report

Merging #1857 (93ff788) into master (0e63dcf) will decrease coverage by 0.00%.
The diff coverage is 23.07%.

@@            Coverage Diff             @@
##           master    #1857      +/-   ##
==========================================
- Coverage   13.44%   13.44%   -0.01%
==========================================
  Files         203      203
  Lines       95087    95082       -5
==========================================
- Hits        12789    12785       -4
+ Misses      82298    82297       -1

Impacted Files
Coverage Δ

src/Cache/PPCache.cpp
2.52% <0.00%> (-0.40%)
:arrow_down:

src/SourceCompile/PreprocessFile.h
48.33% <50.00%> (ø)

src/SourceCompile/PreprocessFile.cpp
47.85% <62.50%> (-0.23%)
:arrow_down:

Continue to review full report at Codecov.

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


Aragorn error 500 Workflow A.9

https://github.com/NCATSTranslator/minihackathons/blob/main/2021-12_demo/workflowA/A.9_EGFR_advanced.json

{
  "callback": "http://<IP_ADDRESS>:8000/ars/api/messages/2f3f4aaa-c15a-4a8b-affb-3002684e20b3",
  "description": "",
  "logs": [
    {
      "code": null,
      "level": "ERROR",
      "message": "Exception 'logs'",
      "timestamp": "2021-08-12 15:57:38.659031"
    },
    {
      "code": "InvalidTRAPI",
      "level": "ERROR",
      "message": "TRAPI validator reported an error: Additional properties are not allowed ('negated' was unexpected)\n\nFailed validating 'additionalProperties' in schema[0]['items']:\n    {'additionalProperties': False,\n     'description': 'Generic query constraint for a query node or query '\n                    'edge',\n     'properties': {'id': {'allOf': [{'$ref': '#/components/schemas/CURIE'}],\n                           'description': 'CURIE of the concept being '\n                                          'constrained. For properties '\n                                          'defined by the Biolink model '\n                                          'this SHOULD be a biolink CURIE. '\n                                          'otherwise, if possible, from '\n                                          'the EDAM ontology. If a '\n                                          'suitable CURIE does not exist, '\n                                          'enter a descriptive phrase here '\n                                          'and submit the new type for '\n                                          'consideration by the '\n                                          'appropriate authority.',\n                           'example': 'EDAM:data_0844'},\n                    'name': {'description': 'Human-readable name or label '\n                                            'for the constraint concept. '\n                                            'If appropriate, it SHOULD be '\n                                            'the term name of the CURIE '\n                                            \"used as the 'id'. This is \"\n                                            'redundant but required for '\n                                            'human readability.',\n                             'example': 'molecular mass',\n                             'type': 'string'},\n                    'not': {'default': False, 'type': 'boolean'},\n                    'operator': {'description': 'Relationship between the '\n                                                'database value and the '\n                                                'constraint value for the '\n                                                'specified id. The '\n                                                'operators ==, >, and < '\n                                                'mean is exactly equal to, '\n                                                'is greater than, and is '\n                                                'less than, respectively. '\n                                                \"The 'matches' operator \"\n                                                'indicates that the value '\n                                                'is a regular expression '\n                                                'to be evaluated. If value '\n                                                'is a list type, then at '\n                                                'least one evaluation must '\n                                                'be true (equivalent to '\n                                                'OR). This means that the '\n                                                '== operator with a list '\n                                                \"acts like a SQL 'IN' \"\n                                                \"clause. The 'not' \"\n                                                'property negates the '\n                                                'operator such that not '\n                                                \"and == means 'not equal \"\n                                                \"to' (or 'not in' for a \"\n                                                'list), and not > means '\n                                                '<=, and not < means >=, '\n                                                'and not matches means '\n                                                \"does not match. The '==' \"\n                                                'operator SHOULD NOT be '\n                                                'used in a manner that '\n                                                'describes an \"is a\" '\n                                                'subclass relationship for '\n                                                'the parent QNode.',\n                                 'enum': ['==', '>', '<', 'matches'],\n                                 'type': 'string'},\n                    'unit_id': {'description': 'CURIE of the units of the '\n                                               'value or list of values in '\n                                               \"the 'value' property. The \"\n                                               'Units of Measurement '\n                                               'Ontology (UO) should be '\n                                               'used if possible. The '\n                                               'unit_id MUST be provided '\n                                               'for (lists of) numerical '\n                                               'values that correspond to '\n                                               'a quantity that has units.',\n                                'example': 'UO:0000222'},\n                    'unit_name': {'description': 'Term name that is '\n                                                 'associated with the '\n                                                 'CURIE of the units of '\n                                                 'the value or list of '\n                                                 \"values in the 'value' \"\n                                                 'property. The Units of '\n                                                 'Measurement Ontology '\n                                                 '(UO) SHOULD be used if '\n                                                 'possible. This property '\n                                                 'SHOULD be provided if a '\n                                                 'unit_id is provided. '\n                                                 'This is redundant but '\n                                                 'recommended for human '\n                                                 'readability.',\n                                  'example': 'kilodalton'},\n                    'value': {'description': 'Value of the attribute. May '\n                                             'be any data type, including '\n                                             'a list. If the value is a '\n                                             'list and there are multiple '\n                                             'items, at least one '\n                                             'comparison must be true '\n                                             '(equivalent to OR). If '\n                                             \"'value' is of data type \"\n                                             \"'object', the keys of the \"\n                                             'object MAY be treated as a '\n                                             \"list. A 'list' data type \"\n                                             \"paired with the '>' or '<' \"\n                                             'operators will encode '\n                                             'extraneous comparisons, but '\n                                             'this is permitted as it is '\n                                             'in SQL and other languages.',\n                              'example': 57.0}},\n     'required': ['name', 'id', 'operator', 'value'],\n     'type': 'object'}\n\nOn instance[0]:\n    {'id': 'biolink:highest_FDA_approval_status',\n     'name': 'highest FDA approval status',\n     'negated': False,\n     'operator': '==',\n     'unit_id': None,\n     'unit_name': None,\n     'value': 'regular approval'}",
      "timestamp": "2021-08-12T15:58:21.417514"
    }
  ],
  "message": {
    "knowledge_graph": null,
    "query_graph": {
      "edges": {
        "e0": {
          "constraints": null,
          "object": "n1",
          "predicates": [
            "biolink:decreases_abundance_of",
            "biolink:decreases_activity_of",
            "biolink:decreases_expression_of",
            "biolink:decreases_synthesis_of",
            "biolink:increases_degradation_of",
            "biolink:disrupts",
            "biolink:entity_negatively_regulates_entity"
          ],
          "relation": null,
          "subject": "n0"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:SmallMolecule"
          ],
          "constraints": [
            {
              "id": "biolink:highest_FDA_approval_status",
              "name": "highest FDA approval status",
              "negated": false,
              "operator": "==",
              "unit_id": null,
              "unit_name": null,
              "value": "regular approval"
            }
          ],
          "ids": null,
          "is_set": false,
          "name": "Small Molecule"
        },
        "n1": {
          "categories": null,
          "constraints": null,
          "ids": [
            "NCBIGene:1956"
          ],
          "is_set": false,
          "name": "EGFR"
        }
      }
    },
    "results": null
  },
  "status": null,
  "validation_result": {
    "message": "TRAPI validator reported an error: Additional properties are not allowed ('negated' was unexpected)\n\nFailed validating 'additionalProperties' in schema[0]['items']:\n    {'additionalProperties': False,\n     'description': 'Generic query constraint for a query node or query '\n                    'edge',\n     'properties': {'id': {'allOf': [{'$ref': '#/components/schemas/CURIE'}],\n                           'description': 'CURIE of the concept being '\n                                          'constrained. For properties '\n                                          'defined by the Biolink model '\n                                          'this SHOULD be a biolink CURIE. '\n                                          'otherwise, if possible, from '\n                                          'the EDAM ontology. If a '\n                                          'suitable CURIE does not exist, '\n                                          'enter a descriptive phrase here '\n                                          'and submit the new type for '\n                                          'consideration by the '\n                                          'appropriate authority.',\n                           'example': 'EDAM:data_0844'},\n                    'name': {'description': 'Human-readable name or label '\n                                            'for the constraint concept. '\n                                            'If appropriate, it SHOULD be '\n                                            'the term name of the CURIE '\n                                            \"used as the 'id'. This is \"\n                                            'redundant but required for '\n                                            'human readability.',\n                             'example': 'molecular mass',\n                             'type': 'string'},\n                    'not': {'default': False, 'type': 'boolean'},\n                    'operator': {'description': 'Relationship between the '\n                                                'database value and the '\n                                                'constraint value for the '\n                                                'specified id. The '\n                                                'operators ==, >, and < '\n                                                'mean is exactly equal to, '\n                                                'is greater than, and is '\n                                                'less than, respectively. '\n                                                \"The 'matches' operator \"\n                                                'indicates that the value '\n                                                'is a regular expression '\n                                                'to be evaluated. If value '\n                                                'is a list type, then at '\n                                                'least one evaluation must '\n                                                'be true (equivalent to '\n                                                'OR). This means that the '\n                                                '== operator with a list '\n                                                \"acts like a SQL 'IN' \"\n                                                \"clause. The 'not' \"\n                                                'property negates the '\n                                                'operator such that not '\n                                                \"and == means 'not equal \"\n                                                \"to' (or 'not in' for a \"\n                                                'list), and not > means '\n                                                '<=, and not < means >=, '\n                                                'and not matches means '\n                                                \"does not match. The '==' \"\n                                                'operator SHOULD NOT be '\n                                                'used in a manner that '\n                                                'describes an \"is a\" '\n                                                'subclass relationship for '\n                                                'the parent QNode.',\n                                 'enum': ['==', '>', '<', 'matches'],\n                                 'type': 'string'},\n                    'unit_id': {'description': 'CURIE of the units of the '\n                                               'value or list of values in '\n                                               \"the 'value' property. The \"\n                                               'Units of Measurement '\n                                               'Ontology (UO) should be '\n                                               'used if possible. The '\n                                               'unit_id MUST be provided '\n                                               'for (lists of) numerical '\n                                               'values that correspond to '\n                                               'a quantity that has units.',\n                                'example': 'UO:0000222'},\n                    'unit_name': {'description': 'Term name that is '\n                                                 'associated with the '\n                                                 'CURIE of the units of '\n                                                 'the value or list of '\n                                                 \"values in the 'value' \"\n                                                 'property. The Units of '\n                                                 'Measurement Ontology '\n                                                 '(UO) SHOULD be used if '\n                                                 'possible. This property '\n                                                 'SHOULD be provided if a '\n                                                 'unit_id is provided. '\n                                                 'This is redundant but '\n                                                 'recommended for human '\n                                                 'readability.',\n                                  'example': 'kilodalton'},\n                    'value': {'description': 'Value of the attribute. May '\n                                             'be any data type, including '\n                                             'a list. If the value is a '\n                                             'list and there are multiple '\n                                             'items, at least one '\n                                             'comparison must be true '\n                                             '(equivalent to OR). If '\n                                             \"'value' is of data type \"\n                                             \"'object', the keys of the \"\n                                             'object MAY be treated as a '\n                                             \"list. A 'list' data type \"\n                                             \"paired with the '>' or '<' \"\n                                             'operators will encode '\n                                             'extraneous comparisons, but '\n                                             'this is permitted as it is '\n                                             'in SQL and other languages.',\n                              'example': 57.0}},\n     'required': ['name', 'id', 'operator', 'value'],\n     'type': 'object'}\n\nOn instance[0]:\n    {'id': 'biolink:highest_FDA_approval_status',\n     'name': 'highest FDA approval status',\n     'negated': False,\n     'operator': '==',\n     'unit_id': None,\n     'unit_name': None,\n     'value': 'regular approval'} --- ",
    "size": "4 kB",
    "status": "FAIL",
    "version": "1.1.1"
  },
  "araxui_provider": "ARS",
  "araxui_response": "2f3f4aaa-c15a-4a8b-affb-3002684e20b3"
}

https://arax.ncats.io/?source=ARS&id=c9c02a08-5574-45e2-836c-cf16f95fa964
{
  "callback": "http://localhost:8000/ars/api/messages/290dd07d-71e2-42d4-a404-8fb041151ac4",
  "description": "",
  "logs": [
    {
      "code": null,
      "level": "ERROR",
      "message": "Exception 'logs'",
      "timestamp": "2021-09-01 23:27:38.171649"
    },
    {
      "code": "InvalidTRAPI",
      "level": "ERROR",
      "message": "TRAPI validator reported an error: Additional properties are not allowed ('negated' was unexpected)\n\nFailed validating 'additionalProperties' in schema[0]['items']:\n    {'additionalProperties': False,\n     'description': 'Generic query constraint for a query node or query '\n                    'edge',\n     'properties': {'id': {'allOf': [{'$ref': '#/components/schemas/CURIE'}],\n                           'description': 'CURIE of the concept being '\n                                          'constrained. For properties '\n                                          'defined by the Biolink model '\n                                          'this SHOULD be a biolink CURIE. '\n                                          'otherwise, if possible, from '\n                                          'the EDAM ontology. If a '\n                                          'suitable CURIE does not exist, '\n                                          'enter a descriptive phrase here '\n                                          'and submit the new type for '\n                                          'consideration by the '\n                                          'appropriate authority.',\n                           'example': 'EDAM:data_0844'},\n                    'name': {'description': 'Human-readable name or label '\n                                            'for the constraint concept. '\n                                            'If appropriate, it SHOULD be '\n                                            'the term name of the CURIE '\n                                            \"used as the 'id'. This is \"\n                                            'redundant but required for '\n                                            'human readability.',\n                             'example': 'molecular mass',\n                             'type': 'string'},\n                    'not': {'default': False, 'type': 'boolean'},\n                    'operator': {'description': 'Relationship between the '\n                                                'database value and the '\n                                                'constraint value for the '\n                                                'specified id. The '\n                                                'operators ==, >, and < '\n                                                'mean is exactly equal to, '\n                                                'is greater than, and is '\n                                                'less than, respectively. '\n                                                \"The 'matches' operator \"\n                                                'indicates that the value '\n                                                'is a regular expression '\n                                                'to be evaluated. If value '\n                                                'is a list type, then at '\n                                                'least one evaluation must '\n                                                'be true (equivalent to '\n                                                'OR). This means that the '\n                                                '== operator with a list '\n                                                \"acts like a SQL 'IN' \"\n                                                \"clause. The 'not' \"\n                                                'property negates the '\n                                                'operator such that not '\n                                                \"and == means 'not equal \"\n                                                \"to' (or 'not in' for a \"\n                                                'list), and not > means '\n                                                '<=, and not < means >=, '\n                                                'and not matches means '\n                                                \"does not match. The '==' \"\n                                                'operator SHOULD NOT be '\n                                                'used in a manner that '\n                                                'describes an \"is a\" '\n                                                'subclass relationship for '\n                                                'the parent QNode.',\n                                 'enum': ['==', '>', '<', 'matches'],\n                                 'type': 'string'},\n                    'unit_id': {'description': 'CURIE of the units of the '\n                                               'value or list of values in '\n                                               \"the 'value' property. The \"\n                                               'Units of Measurement '\n                                               'Ontology (UO) should be '\n                                               'used if possible. The '\n                                               'unit_id MUST be provided '\n                                               'for (lists of) numerical '\n                                               'values that correspond to '\n                                               'a quantity that has units.',\n                                'example': 'UO:0000222'},\n                    'unit_name': {'description': 'Term name that is '\n                                                 'associated with the '\n                                                 'CURIE of the units of '\n                                                 'the value or list of '\n                                                 \"values in the 'value' \"\n                                                 'property. The Units of '\n                                                 'Measurement Ontology '\n                                                 '(UO) SHOULD be used if '\n                                                 'possible. This property '\n                                                 'SHOULD be provided if a '\n                                                 'unit_id is provided. '\n                                                 'This is redundant but '\n                                                 'recommended for human '\n                                                 'readability.',\n                                  'example': 'kilodalton'},\n                    'value': {'description': 'Value of the attribute. May '\n                                             'be any data type, including '\n                                             'a list. If the value is a '\n                                             'list and there are multiple '\n                                             'items, at least one '\n                                             'comparison must be true '\n                                             '(equivalent to OR). If '\n                                             \"'value' is of data type \"\n                                             \"'object', the keys of the \"\n                                             'object MAY be treated as a '\n                                             \"list. A 'list' data type \"\n                                             \"paired with the '>' or '<' \"\n                                             'operators will encode '\n                                             'extraneous comparisons, but '\n                                             'this is permitted as it is '\n                                             'in SQL and other languages.',\n                              'example': 57.0}},\n     'required': ['name', 'id', 'operator', 'value'],\n     'type': 'object'}\n\nOn instance[0]:\n    {'id': 'biolink:highest_FDA_approval_status',\n     'name': 'highest FDA approval status',\n     'negated': False,\n     'operator': '==',\n     'unit_id': None,\n     'unit_name': None,\n     'value': 'regular approval'}",
      "timestamp": "2021-09-02T12:15:08.350362"
    }
  ],
  "message": {
    "knowledge_graph": null,
    "query_graph": {
      "edges": {
        "e0": {
          "constraints": null,
          "object": "n1",
          "predicates": [
            "biolink:decreases_abundance_of",
            "biolink:decreases_activity_of",
            "biolink:decreases_expression_of",
            "biolink:decreases_synthesis_of",
            "biolink:increases_degradation_of",
            "biolink:disrupts",
            "biolink:entity_negatively_regulates_entity"
          ],
          "relation": null,
          "subject": "n0"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:SmallMolecule"
          ],
          "constraints": [
            {
              "id": "biolink:highest_FDA_approval_status",
              "name": "highest FDA approval status",
              "negated": false,
              "operator": "==",
              "unit_id": null,
              "unit_name": null,
              "value": "regular approval"
            }
          ],
          "ids": null,
          "is_set": false,
          "name": "Small Molecule"
        },
        "n1": {
          "categories": null,
          "constraints": null,
          "ids": [
            "NCBIGene:1956"
          ],
          "is_set": false,
          "name": "EGFR"
        }
      }
    },
    "results": null
  },
  "status": null,
  "validation_result": {
    "message": "TRAPI validator reported an error: Additional properties are not allowed ('negated' was unexpected)\n\nFailed validating 'additionalProperties' in schema[0]['items']:\n    {'additionalProperties': False,\n     'description': 'Generic query constraint for a query node or query '\n                    'edge',\n     'properties': {'id': {'allOf': [{'$ref': '#/components/schemas/CURIE'}],\n                           'description': 'CURIE of the concept being '\n                                          'constrained. For properties '\n                                          'defined by the Biolink model '\n                                          'this SHOULD be a biolink CURIE. '\n                                          'otherwise, if possible, from '\n                                          'the EDAM ontology. If a '\n                                          'suitable CURIE does not exist, '\n                                          'enter a descriptive phrase here '\n                                          'and submit the new type for '\n                                          'consideration by the '\n                                          'appropriate authority.',\n                           'example': 'EDAM:data_0844'},\n                    'name': {'description': 'Human-readable name or label '\n                                            'for the constraint concept. '\n                                            'If appropriate, it SHOULD be '\n                                            'the term name of the CURIE '\n                                            \"used as the 'id'. This is \"\n                                            'redundant but required for '\n                                            'human readability.',\n                             'example': 'molecular mass',\n                             'type': 'string'},\n                    'not': {'default': False, 'type': 'boolean'},\n                    'operator': {'description': 'Relationship between the '\n                                                'database value and the '\n                                                'constraint value for the '\n                                                'specified id. The '\n                                                'operators ==, >, and < '\n                                                'mean is exactly equal to, '\n                                                'is greater than, and is '\n                                                'less than, respectively. '\n                                                \"The 'matches' operator \"\n                                                'indicates that the value '\n                                                'is a regular expression '\n                                                'to be evaluated. If value '\n                                                'is a list type, then at '\n                                                'least one evaluation must '\n                                                'be true (equivalent to '\n                                                'OR). This means that the '\n                                                '== operator with a list '\n                                                \"acts like a SQL 'IN' \"\n                                                \"clause. The 'not' \"\n                                                'property negates the '\n                                                'operator such that not '\n                                                \"and == means 'not equal \"\n                                                \"to' (or 'not in' for a \"\n                                                'list), and not > means '\n                                                '<=, and not < means >=, '\n                                                'and not matches means '\n                                                \"does not match. The '==' \"\n                                                'operator SHOULD NOT be '\n                                                'used in a manner that '\n                                                'describes an \"is a\" '\n                                                'subclass relationship for '\n                                                'the parent QNode.',\n                                 'enum': ['==', '>', '<', 'matches'],\n                                 'type': 'string'},\n                    'unit_id': {'description': 'CURIE of the units of the '\n                                               'value or list of values in '\n                                               \"the 'value' property. The \"\n                                               'Units of Measurement '\n                                               'Ontology (UO) should be '\n                                               'used if possible. The '\n                                               'unit_id MUST be provided '\n                                               'for (lists of) numerical '\n                                               'values that correspond to '\n                                               'a quantity that has units.',\n                                'example': 'UO:0000222'},\n                    'unit_name': {'description': 'Term name that is '\n                                                 'associated with the '\n                                                 'CURIE of the units of '\n                                                 'the value or list of '\n                                                 \"values in the 'value' \"\n                                                 'property. The Units of '\n                                                 'Measurement Ontology '\n                                                 '(UO) SHOULD be used if '\n                                                 'possible. This property '\n                                                 'SHOULD be provided if a '\n                                                 'unit_id is provided. '\n                                                 'This is redundant but '\n                                                 'recommended for human '\n                                                 'readability.',\n                                  'example': 'kilodalton'},\n                    'value': {'description': 'Value of the attribute. May '\n                                             'be any data type, including '\n                                             'a list. If the value is a '\n                                             'list and there are multiple '\n                                             'items, at least one '\n                                             'comparison must be true '\n                                             '(equivalent to OR). If '\n                                             \"'value' is of data type \"\n                                             \"'object', the keys of the \"\n                                             'object MAY be treated as a '\n                                             \"list. A 'list' data type \"\n                                             \"paired with the '>' or '<' \"\n                                             'operators will encode '\n                                             'extraneous comparisons, but '\n                                             'this is permitted as it is '\n                                             'in SQL and other languages.',\n                              'example': 57.0}},\n     'required': ['name', 'id', 'operator', 'value'],\n     'type': 'object'}\n\nOn instance[0]:\n    {'id': 'biolink:highest_FDA_approval_status',\n     'name': 'highest FDA approval status',\n     'negated': False,\n     'operator': '==',\n     'unit_id': None,\n     'unit_name': None,\n     'value': 'regular approval'} --- ",
    "size": "4 kB",
    "status": "FAIL",
    "version": "1.1.1"
  },
  "araxui_provider": "ARS",
  "araxui_response": "290dd07d-71e2-42d4-a404-8fb041151ac4"
}

Strider deploying Sep 9 should fix this.

https://arax.ncats.io/?source=ARS&id=eaef59d1-ad7c-423c-b67d-ec02ca227cd4


Update Add-PnPFileToProvisioningTemplate.md

Added the web parameter to this cmdlet. I found it in the March update of the module.

OPS Build status updates of commit 353e5be:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: OPS Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

OPS Build status updates of commit 353e5be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

OPS Build status updates of commit 3435479:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

OPS Build status updates of commit ed9a0bb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFileToProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

Looking on the actual code of this cmdlet, can't see the web parameter - https://github.com/SharePoint/PnP-PowerShell/blob/dev/Commands/Provisioning/Site/AddFileToProvisioningTemplate.cs. Also all PnP PowerShell documentation changes should be applied on the original source code as we auto-generate the PnP PowerShell documentation from the code. This means that we cannot accept changes directly on the PnP cmdlet docs.

@VesaJuvonen, thanks for checking this. And sorry for creating a PR in the wrong place. I think you already mentioned this to me before but I forgot, my bad :)


Feature optional injections

From: https://github.com/odesk/phystrix/pull/9
In order to simplify CommandFactory setup, where requestLog and requestCache are not used, make these dependencies optional

:+1:

:+1:

noice! My eyes are still burning though.