(chore) update to use markdown-transform

Signed-off-by: Dan Selman<EMAIL_ADDRESS>Changes

Update to use markdown-transform for Slate <> Markdown conversion
Removed markdown <> HTML conversion from plugins

Flags

Plugins are now purely for controlling Slate editor behaviour, they cannot extend markdown serialisation as that is handled by markdown-transform
Do we want to remove the List plugin altogether and just bake that into the SlateAsInputEditor?

Curious why we remove the video plugin?

I think moving the List plugin altogether and just baking that into the SlateAsInputEditor makes sense, it feels like it's an integral attribute that doesn't need to be abstracted into a plugin.

Curious why we remove the video plugin?

Because the markdown-transform would need to be extended to handle the conversion from/to Slate.


Added new feature (new classes) to parse and load pdfs using PyMuPDF from bytes buffer

Hi, here is the required info for this pull request.
Description:
I've added a new feature (new classes) to parse and load pdfs using PyMuPDF from bytes buffer. This is important when the PDF is not a file but is a bytes buffer in memory. Especially, it's useful when working and using Langchain with Spark and Databricks Autoloader.
I've also added a unit test.
Dependencies:
No new dependencies is required. Just io library which is in the native python packaging.

I've updated the code according to the comments. However, linting was giving me some errors. Also, didn't re-implement the tester as I've seen another PR discussion on it.

closing due to inactivity and merge conflicts


Any known Java ORM  for Logica

Really curious if there are known OSS Java bindings or an ORM.
The googles have not been much help.
Thanks in advance!

No, sorry, I don't think any bindings with Java exist yet.


Add vectorized iterators for std::collections

Fixes #88.

@cuviper note travis failure

Looks good except for travis failure.
I was wondering if we would want some more general "convert iterator to parallel" notion that avoids "overhead" of creating a vector, but:

that would probably have to use some sort of task queue, which is basically a vector, but probably less efficient
we can still have that if people write foo.iter().parallelize() or some such

Some data structures (e.g., btrees but prob also hashmaps) could support more efficient interaction if they gave access to more of their internals, or impl'd rayon directly. Said access might not necessarily be indexable and hence it could be a backwards incompat change to adopt it. But it seems like that would be a bridge to cross then -- and trying to ensure indexable would be a good goal for such integration anyway.

Hmm, that issue with the lifetime parameter looks annoying.  It worked with nightly, and works with beta, so I wonder what change that is that hasn't landed on stable yet?  Anyway, I think I can fix this by forking the macro into three (almost identical) variants... :/
The cd demo/... failures are even weirder -- hopefully just some spurious Travis thing.

@cuviper weird; could well be a bug, I didn't look closely at it

OK, Travis is happy now.


Use curly braces for tuple_impl! calls

Macros can be called with (), {}, and []. Using {} is slightly more idiomatic for things that expand to items (impl blocks, struct definitions, etc), and has the benefit that cargo fmt doesn't try to format them.

Ah nice!


Compilation error

ubuntu20.04 ros2(humble)
git clone -b 0.7.0 --single-branch https://github.com/autowarefoundation/tvm_vendor.git
colcon build --symlink-install --packages-select tvm_vendor
Starting >>> tvm_vendor
--- stderr: tvm_vendor
error: patch failed: cmake/config.cmake:115
error: cmake/config.cmake: patch does not apply
make[2]: *** [CMakeFiles/tvm-build.dir/build.make:126: tvm-build-prefix/src/tvm-build-stamp/tvm-build-patch] Error 1
make[1]: *** [CMakeFiles/Makefile2:137: CMakeFiles/tvm-build.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
Failed   <<< tvm_vendor [0.73s, exited with code 2]

Hi I am having same problem?
Could you share me how you solved the problem?


Fix sh syntax

removed the dollar sign when assigning a value to an environment variable to make it work
wrapped query parameter value in quotes to make it work

@WilliamMauclet : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@WilliamMauclet which shell are you using? I've found that the dollar sign needs to be there.


Why does SimCLR use class_loss in training_step?

https://github.com/vturrisi/solo-learn/blob/main/solo/methods/simclr.py#L124
Forgetting why this loss is being added to the nce loss in the training_step, I thought it was only calculated for the validation step or in supcon method.

Hi! Thanks for using solo-learn. Please, search through the issues before posting. The question has already been answered multiple times:
https://github.com/vturrisi/solo-learn/issues/174
https://github.com/vturrisi/solo-learn/issues/91
https://github.com/vturrisi/solo-learn/issues/128


remove fallback timeslot not possible

current workaround is: remove registration of 21:00 timeslot and register again

What is the issue? Normally there should be an "x" in them dropdown control to clear the fallback.

it is visible, but once you click on it, it will revert to the last chosen time.
tested on edge and ios

Hm, okay that seems to be a server issue then. Do you see any errors in the browser console?

no issues


Add NDC Columns Drug

Hello @elmo , what's this?

Hello @elmo , what's this?

I assume it's due to a kind of mistake. Let me close.

I assume it's due to a kind of mistake. Let me close.


Vacuum Chest should not attract items when not activated

Issue Description:
Vacuum chests have a redstone setting.  This makes this redstone setting fairly useless.
What happens:
Vacuum chests pull in items even when disabled/set to never active.
What you expected to happen:
Vacuum chests stop attracting items when disabled.
Steps to reproduce:

Set vacuum chest to "Never active"
Throw item on the ground
Watch item get pulled towards vacuum chest

Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-<IP_ADDRESS>_beta
EnderCore: 1.10.2-<IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>5

Your most recent log file where the issue was present:
N/A

Hmm, on closer inspection it does seem to work this way already, not sure why it didn't work for me earlier.
Closing.

Possibly client-server desync. The Vacuum Chest is one of the few blocks that does the same work on the client and server. Most machines just do it on the server and send the "render as on"/"render as off" data to the client. Which means that our complete Redstone code is designed to run server-side and may not be as robust for the Chest as would be nice...

(read that tag as "most probably it is a bug, but is is so minor and only cosmetic that it's not worth to fix it"

Fair enough, if I figured out what was happening exactly earlier I wouldn't even have reported it in the first place, so works for me


Chore merge-main@7f35bc5

[x] https://github.com/twbs/bootstrap/commit/55fb59c074f7c7f3e19a802f6567a5ffbafad5d9
[x] https://github.com/twbs/bootstrap/commit/298cb9194b61db3c36f96ec5cd36d0072b533d5c
[x] https://github.com/twbs/bootstrap/commit/21fa2cfc122938ba34fcf94770fe2d6d2dfd7842
[x] https://github.com/twbs/bootstrap/commit/e77ae50311366b07225d15b19e330a3871123437
[x] https://github.com/twbs/bootstrap/commit/a8142497c79f33bebd13a8b00d8104b324ce5cf7
[x] https://github.com/twbs/bootstrap/commit/b7cce49dbc7d9dd6be1dd49e6764dd6f23f6d758
[x] https://github.com/twbs/bootstrap/commit/fcc2c809767525a32357fc4877a6dbbac6ba1370
[x] https://github.com/twbs/bootstrap/commit/699402bee5d02659acaab69208549f26f9b3313d
[x] https://github.com/twbs/bootstrap/commit/dd93551914424e577176a6377e1614742aa1018c
[x] https://github.com/twbs/bootstrap/commit/d4e87d28cdc1b5d053b4c08da737321ab4de2ff7
[x] https://github.com/twbs/bootstrap/commit/7e5a8016ba557641ee93b38aed4482a1360b64af
[x] https://github.com/twbs/bootstrap/commit/645f95584551409660fcd9b990fc24caa0327df5

https://github.com/twbs/bootstrap/commit/3ef6a435be5fe13f8b46c3a949aa0ddc5c3e6ef1: Nothing to do in Boosted

[x] https://github.com/twbs/bootstrap/commit/28f150d7204788114e2b36555f5e07eb8bdfdbab
[x] https://github.com/twbs/bootstrap/commit/88da704eedc5149b70dcec7845453456a6e26761
[x] https://github.com/twbs/bootstrap/commit/ec0e1c220e2f9b1f4591b4c7f12a622822f14014
[x] https://github.com/twbs/bootstrap/commit/3673933fe74b4323267b0b0a7871a393ce2ff5cb
[x] https://github.com/twbs/bootstrap/commit/6e904341c9a4a07ea0232850a2dcd4ddc7dfa00a
[x] https://github.com/twbs/bootstrap/commit/d21a51a2eaa73d98005dc79a59c5c0b1c5f54d15
[x] https://github.com/twbs/bootstrap/commit/5bdd5e02a46101b96e83431b18c39979e337c033
[x] https://github.com/twbs/bootstrap/commit/05c6e7dd66c10af8b2f8345b48c26de12f769335
[x] https://github.com/twbs/bootstrap/commit/63145c8bc6bb26f7651fbd6cfe626068704cdf76
[x] https://github.com/twbs/bootstrap/commit/c73480c63660d0643434e07c9a522758c21a272d
[x] https://github.com/twbs/bootstrap/commit/ea7ff1eab9e66bf51152c6b5b73580cefd423b43
[x] https://github.com/twbs/bootstrap/commit/e72a090aee2c518dc76fb9d6d9fae732343c1432
[x] https://github.com/twbs/bootstrap/commit/58ac9a9a5cf6072188d8a928a6f3206ffb855219
[x] https://github.com/twbs/bootstrap/commit/ce655ee6f2fb8ad774846e4afe7daeb9fc8686e7

:warning: This one had edge cases in Boosted so check in details all those cases

[x] https://github.com/twbs/bootstrap/commit/d16088d5d1ec2de56a301fbb8e1a227ae7eb5ece
[x] https://github.com/twbs/bootstrap/commit/e567d511d4c94617510ef592ab804ec273e93480
[x] https://github.com/twbs/bootstrap/commit/1936e0c5eaa7f8f2d89ec1ac863aa73130fb69b1
[x] https://github.com/twbs/bootstrap/commit/7c966f584889c6dfb0f1a70dd1757b2d237a68a0
[x] https://github.com/twbs/bootstrap/commit/acf6ea74a74328bcaa9f1c354f27e602cfbb8968

:boom: Breaking changes reverted in another commit after

[x] https://github.com/twbs/bootstrap/commit/70cb00c349f38025fb8aa5850a71b14bf7f0efd7
[x] https://github.com/twbs/bootstrap/commit/8fe82c7176a577190f2d69f9cbdd990b7f3c8493
[x] https://github.com/twbs/bootstrap/commit/a9a89debc7535a1c5857ced28c1002a2f682889f

[ ] Let's do it in another PR but make the same modifications in Boosted for our custom content

[x] https://github.com/twbs/bootstrap/commit/33827d24a4f6a4c8446584d7740c338e35b41b91
[x] https://github.com/twbs/bootstrap/commit/91f6a01c69f8530ad11fd75e7532ebba6a9ef3a8
[x] https://github.com/twbs/bootstrap/commit/11751c613fdb040f8db5a155d7aafaeabd387499
[x] https://github.com/twbs/bootstrap/commit/8182fd94308f83f2432aa61bf43268fc40740a92
[x] https://github.com/twbs/bootstrap/commit/71582eabff54b6ff98aa471350258da70a14c802
[x] https://github.com/twbs/bootstrap/commit/a4841afa26fb066a53c6a70e87d906e3e309a903
[x] https://github.com/twbs/bootstrap/commit/b165f35f7808b59f4e09ec518caa441e30830fbb
[x] https://github.com/twbs/bootstrap/commit/88bd287b27c8097ca02347038dbb0b321b71d169
[x] https://github.com/twbs/bootstrap/commit/0e5cd69c02ae07b0ddb1656ef9b7eac5f9aca2e7
[x] https://github.com/twbs/bootstrap/commit/fbf64406dfe414acca102c3a0ce2a151c768373c
[x] https://github.com/twbs/bootstrap/commit/9e73b6a13c1cd4cc27d1456319a3d63630e91e2f
[x] https://github.com/twbs/bootstrap/commit/0eb808015fc84effc69300a0a7e6884eb924abc9
[x] https://github.com/twbs/bootstrap/commit/7f35bc5b65dccf6c953321e47342c4ed0b7c4b2b

Tracked issues with StackBlitz in https://github.com/twbs/bootstrap/pull/36088.

[ ] After the feedback (and merge?) of this PR, we need to not to forget checking Boosted custom parts of the documentation and execution in StackBlitz (same listing work than in the PR)


Fix: Wrap special characters in double quotes for correct CSV formatting

Description: Fix wrap special characters in double quotes for correct CSV formatting

LGTM


publish-snapshot script is publishing the first jar it finds next to a pom.

We have Snapshot publications that are including extra jars.  These jars are incorrectly being picked up by the publish-snapshot.sh script and published with mvn deploy-file.  As a result it is pushed to Sonatype as the latest publication, but is not the correct jar.
For example
org/opensearch/gradle/build-tools/1.1.0-SNAPSHOT/ publishes two jars:
build-tools-1.1.0-SNAPSHOT-test-fixtures.jar and build-tools-1.1.0-SNAPSHOT.jar
The script is picking up build-tools-1.1.0-SNAPSHOT-test-fixtures.jar and pushing under sonatype as:
 /org/opensearch/gradle/build-tools/1.1.0-SNAPSHOT/build-tools-1.1.0-20210910.002130-165.jar
When the dependency is used, the incorrect jar is fetched.  Specifically for plugins & build-tools, this results in the following error.
* Where:
Build file '/Users/handalm/workspace/job-scheduler/build.gradle' line: 48

* What went wrong:
A problem occurred evaluating root project 'opensearch-job-scheduler'.
> Plugin with id 'opensearch.opensearchplugin' not found.

Note - this is NOT an issue for release builds that are pushed with the stage-maven-release.sh script.  That script using a separate nexus staging plugin that pushes all artifacts that are in the folder.  Unfortunately we cannot use that to push snapshots.

Should we be rewriting this as a publish step in build-workflow?

I have mixed feelings on that.
I'd rather that instead of us pushing pre-built snapshot artifacts with this script that we update the build-workflow to conditionally push in component build scripts.  Ex. Pass a publish flag to build.sh where artifacts may conditionally invoke a gradle script to push to the snapshot repo & the necessary credentials are provided by CI.   For example the core repo has a ./gradlew publishNebulaPublicationsToSnapshotsRepo where this is possible.  We would want this toggle-able so we don't break local builds.
I think we should keep the staging functionality with the external script stage-maven-release.sh that stages pre-built artifacts.  This is because we need to promote them at a much later stage and not at build time.

Generally python > bash because we can write tests.
Care to write up a separate issue about what you think we should do longest term?

Generally python > bash because we can write tests.
Care to write up a separate issue about what you think we should do longest term?

Hi @mch2 have you looked at this comment from @dblock ?
Thanks.

@mch2 Can you add acceptance criteria so that we could move on.

This issue has been resolved the best it can with #1188.  I will update #1182 with an idea to remove this script entirely.


what is manual and auto versions

It has code for auto and manual version per language, kindly explain what they are how they are different in
https://github.com/elastic/observability-examples/blob/main/Elastiflix/README.md

Hi @nagkumar I've just opened #21 that should help clarify this, can I let you review and comment on the PR if anything isn't clear enough ? Thanks !


Backport: Rancher enforces arbitrary limit on autoscaling nodes in GKE clusters

https://github.com/rancher/rancher/issues/20355

https://github.com/rancher/rancher/pull/21030

Replication:
Version: v2.2.4
As pictured I cannot make GKE node pool autoscaling max greater than 5 for each min and max (template prevents this). (Below in picture I tried to plug in a number greater than 5 in each field)

Validation:
Version: release-v2.2 (essentially v2.2.5 rc) (6/21/19)
Failed.
I still cannot set min to greater than 5 and max to greater than 5.
I think this just isn't in release-v2.2 yet? I just pulled it 6/21/19 12:50PM pacific.

Waiting on new build.

Use https://releases.rancher.com/ui/2.2.78/index.html for testing and re-test this.

Version: v2.2-head with ui-index of https://releases.rancher.com/ui/2.2.78/index.html
This is now working correctly. See my comment above for reproduction notes https://github.com/rancher/rancher/issues/20936#issuecomment-504553068

The ui allows the min to be greater than 5 and the max to be greater than 5.
I brought up a cluster with this configuration and confirmed settings in GCP web UI.

Further, I ensured I can have a min setting of 1 and a max setting of 1 as well. This works without any issues as well.

I also did various checks with weird settings like a min of 3 and a max of 1. The UI does not allow this, as expected (it will forcibly set max to at least equal the min at minimum). Additionally, if you do not set the initial node pool amount to be the minimum value or greater then the UI will mention this and prevent creating the cluster, as expected. The UI also does not allow entering any zeros or other chars, as expected. Last, there appears to be no limit set. I can have autoscaling set to min 1 and max 1048576 without any issues.
HTTP/API appear correct. I could not identify any issues except for one small issue (for which I will open a separate bug). When you first try to change the numbers the UI seems to enforce the old 5/5 for min/max fields. But then try again and then it works. You basically just have to plug in your number you want twice (if greater than 5). It's a strange behavior but doesn't seem to hurt anything. This issue is tracked here:


ClusterPool Inventory RFE followup

Add "Alternatives" and "Future" sections per code review.
HIVE-1367

/assign @akhil-rane


Reactjs 2.5 was released to Nuget but no tagging?

https://www.nuget.org/packages/React.Web.Mvc4/
It appears it is 2.5?

Sorry about that, looks like I forgot to push the changes to the repo. The only change in 2.5 is adding support for ASP.NET Core 1.0. This change is not relevant for React.Web.Mvc4, so don't worry too much :)
At the moment, I use the exact same version number for every package, so sometimes the version number is incremented even if there's no changes in that particular package. I might change it in the future.

release-2.5.0 has been tagged in the repo for a while, closing this issue. Thanks!


make possible to netsetgo to connect to existent bridges

Currently lxc allows the newly created container to connect to an already created bridge, like lxcbr0 (lxc bridge) or virbr0 (created by libvirt).
instead of creating a new bridge and set all the iptables rules, netsetgo could have a new option to create the veth pair and connect to an existent bridge.
@teddyking do you think this is a nice idea? If yes, I can try to work on it !

@marcosps I think that's a great idea! And PRs would be very welcome.

Closing old bugs :)


Logs emitted by LoggerProvider are missing the resource attributes

What happened?
Steps to Reproduce
Run the setup code attached
Expected Result
A log record emitted with the resource attributes
Actual Result
A log record without the resource attributes, e.g.:
{
  timestamp:<PHONE_NUMBER>772000,
  traceId: undefined,
  spanId: undefined,
  traceFlags: undefined,
  severityText: undefined,
  severityNumber: undefined,
  body: undefined,
  attributes: {}
}

Additional Details
See code below.
This happens in both span context and where there's no active span recording.
OpenTelemetry Setup Code
const { Resource } = require('@opentelemetry/resources');
const { LoggerProvider, SimpleLogRecordProcessor, ConsoleLogRecordExporter } = require('@opentelemetry/sdk-logs');
const logsAPI = require('@opentelemetry/api-logs');

const resource = Resource.default().merge({ 'some-thing-about': 'the-resource' })
const loggerProvider = new LoggerProvider({ resource });
loggerProvider.addLogRecordProcessor(new SimpleLogRecordProcessor(new ConsoleLogRecordExporter()));

logsAPI.logs.setGlobalLoggerProvider(loggerProvider).getLogger().emit({ message: 'Hello, world!' });

package.json
{
  "name": "my-opentelemetry-project",
  "version": "1.0.0",
  "description": "A project using OpenTelemetry for logging",
  "main": "logging.js",
  "scripts": {
    "start": "node logging.js"
  },
  "dependencies": {
    "@opentelemetry/resources": "1.17.1",
    "@opentelemetry/sdk-logs": "0.50.0",
    "@opentelemetry/api-logs": "0.50.0"
  }
}

Relevant log output
{
  timestamp:<PHONE_NUMBER>772000,
  traceId: undefined,
  spanId: undefined,
  traceFlags: undefined,
  severityText: undefined,
  severityNumber: undefined,
  body: undefined,
  attributes: {}
}

They're simply not added to the output of the console exporter, right?

From what I can see they're in the exported data but not logged via the console exporter.

From what I can see they're in the exported data but not logged via the console exporter.

I see, my apologies for missing that.
Should it be classified as a ConsoleExporter bug in that case, or is it by design?

From what I can see they're in the exported data but not logged via the console exporter.

I see, my apologies for missing that. Should it be classified as a ConsoleExporter bug in that case, or is it by design?

No worries, this was by design. Though I can see that it's confusing when it's not there. I've run into that multiple times when trying to troubleshoot apps running in k8s that I couldn't see the resources in the console exporter when I enabled it.
For that reason I added logging the resource to the ConsoleSpanExporter (#4605 classified as a feature).
I'll re-classify this issue as a feature. If you want you can open a PR to make the same change for the console log exporter. :slightly_smiling_face:


"QR Code is invalid" erro when scanning OOB proof-request

When scanning an out-of-band proof-request, the BC Wallet displays a QR code is invalid error and appears to not complete the processing of the payload. However, after dismissing the camera screen, the proof-request is correctly displayed in the wallet and it can be responded to correctly (assuming the holder possesses the correct credentials to fulfill it).
c.c.: @Jsyro
Example out-of-band proof-request payload:
{
   "@id":"c893661e-dadc-4aff-869e-ea4ccb4757e3",
   "@type":"https://didcomm.org/out-of-band/1.1/invitation",
   "goal_code":"request-proof",
   "label":"vc-authn Out-of-Band present-proof authorization request",
   "requests~attach":[
      {
         "@id":"request-0",
         "mime-type":"application/json",
         "data":{
            "json":{
               "@id":"c893661e-dadc-4aff-869e-ea4ccb4757e3",
               "@type":"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation",
               "request_presentations~attach":[
                  {
                     "@id":"libindy-request-presentation-0",
                     "mime-type":"application/json",
                     "data":{
                        "base64":"eyJub25jZSI6ICI3NzQ4MjkyNzUxNjUwNjk2NTE1NDk0ODYiLCAibmFtZSI6ICJwcm9vZl9yZXF1ZXN0ZWQiLCAidmVyc2lvbiI6ICIwLjAuMSIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsicmVxX2F0dHJfMCI6IHsicmVzdHJpY3Rpb25zIjogW10sICJuYW1lIjogImZpcnN0X25hbWUifSwgInJlcV9hdHRyXzEiOiB7InJlc3RyaWN0aW9ucyI6IFtdLCAibmFtZSI6ICJsYXN0X25hbWUifX0sICJyZXF1ZXN0ZWRfcHJlZGljYXRlcyI6IHt9fQ=="
                     }
                  }
               ],
               "comment":"None",
               "~service":"None"
            }
         }
      }
   ],
   "services":[
      "did:sov:EXrhGcG9VYSV2QA8m66B3P"
   ]
}

Correct proof-request screen after error:

@esune , @Jsyro, can you provide steps on how to reproduce these error? It can be from a fresh tenant in traction

@amanji, Is this still relevant? I know you made some changes to the mobile app after our original discussions.

@cvarjao you should be able to reproduce by running vc-authn (from the 2.0-development branch) and setting USE_OOB_PRESENT_PROOF to True.

Wondering id @nodlesh can help here. Creating an OOB proof-request correctly is not particularly straightforward, so that is why I suggested using vc-authn as it would be just a configuration change. If he can't help, I'll see what I can put together.

Relates to #1147

I believe this issue can be closed. I have given a full explanation in a comment in #1147 on current results of this case, https://github.com/bcgov/bc-wallet-mobile/issues/1147#issuecomment-1832065321

I tested again with VC-AuthN (currently using ACA-Py 0.10.3) and the issue seems to have indeed been resolved: I was able to scan the QR code with an OOB proof-request and respond successfully. Thanks!

Wondering if this is still an issue, or has become an issue again?
I'm testing out with VCAuthn. This is locally with ngrok and at the lab… so not sure if there's possible interference from that setup, however as shown below this setup is working for connectionless, so I doubt it.
If I set VCAuthN to the OOB mode I get an invalid QR code when scanning with the wallet.
Steps to reproduce each case are:
1. Pull vcauthn repo
2. Set the USE_OOB_PRESENT_PROOF value to desired for test case
3. Start up
4. Start up the demo app and login
Scan QR code with freshly opened BC Wallet
Connectionless (USE_OOB_PRESENT_PROOF false)

The QR code resolves to something like https://a33f-207-81-220-83.ngrok-free.app/url/pres_exch/4fe9a2d7-f57f-482f-b82c-5bdb1ec93481
The payload this redirects to is

{
    "@id": "874b772e-acca-4e9c-88c6-f6962166c873",
    "@type": "did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation",
    "request_presentations~attach": [
        {
            "@id": "libindy-request-presentation-0",
            "mime-type": "application/json",
            "data": {
                "base64": "eyJub25jZSI6ICI4ODU1NjQ2MjU3NzI5MTgzOTkyODk3NTMiLCAibmFtZSI6ICJwcm9vZl9yZXF1ZXN0ZWQiLCAidmVyc2lvbiI6ICIwLjAuMSIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsicmVxX2F0dHJfMCI6IHsibmFtZXMiOiBbImdpdmVuX25hbWVzIiwgImZhbWlseV9uYW1lIiwgImNvdW50cnkiXSwgInJlc3RyaWN0aW9ucyI6IFt7InNjaGVtYV9uYW1lIjogIlBlcnNvbiIsICJpc3N1ZXJfZGlkIjogIkw2QVNqbUREYkRIN3lQTDF0MnlGajkifSwgeyJzY2hlbWFfbmFtZSI6ICJQZXJzb24iLCAiaXNzdWVyX2RpZCI6ICJRRXF1QUhrTTM1dzRYVlQzS3U1eWF0In0sIHsic2NoZW1hX25hbWUiOiAiUGVyc29uIiwgImlzc3Vlcl9kaWQiOiAiTTZkaHVGajVVd2JoV2tTTG12WVNQYyJ9XSwgIm5vbl9yZXZva2VkIjogeyJmcm9tIjogMTcwODAyMzg4MywgInRvIjogMTcwODAyMzg4M319fSwgInJlcXVlc3RlZF9wcmVkaWNhdGVzIjoge319"
            }
        }
    ],
    "comment": null,
    "~service": {
        "recipientKeys": [
            "6PmHCm4rJWVE1y9u7MxRiro7j6zzo9XWuKYDAChyivbS"
        ],
        "routingKeys": null,
        "serviceEndpoint": "https://d6e1-207-81-220-83.ngrok-free.app"
    }
}

Out of band (USE_OOB_PRESENT_PROOF false)

Payload from redirect from https://b6c4-207-81-220-83.ngrok-free.app/url/pres_exch/e0e48509-8174-46f7-995c-32d8ad6033cd

{
    "@id": "ee52a798-22ff-4f95-ae36-333ada28aa2b",
    "@type": "https://didcomm.org/out-of-band/1.1/invitation",
    "goal_code": "request-proof",
    "label": "vc-authn Out-of-Band present-proof authorization request",
    "requests~attach": [
        {
            "@id": "request-0",
            "mime-type": "application/json",
            "data": {
                "json": {
                    "@id": "ee52a798-22ff-4f95-ae36-333ada28aa2b",
                    "@type": "did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation",
                    "request_presentations~attach": [
                        {
                            "@id": "libindy-request-presentation-0",
                            "mime-type": "application/json",
                            "data": {
                                "base64": "eyJub25jZSI6ICIzODYyNDkyMjc1MzEyMjk4Mjc5MDQ5MTkiLCAibmFtZSI6ICJwcm9vZl9yZXF1ZXN0ZWQiLCAidmVyc2lvbiI6ICIwLjAuMSIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsicmVxX2F0dHJfMCI6IHsibmFtZXMiOiBbImdpdmVuX25hbWVzIiwgImZhbWlseV9uYW1lIiwgImNvdW50cnkiXSwgInJlc3RyaWN0aW9ucyI6IFt7InNjaGVtYV9uYW1lIjogIlBlcnNvbiIsICJpc3N1ZXJfZGlkIjogIkw2QVNqbUREYkRIN3lQTDF0MnlGajkifSwgeyJzY2hlbWFfbmFtZSI6ICJQZXJzb24iLCAiaXNzdWVyX2RpZCI6ICJRRXF1QUhrTTM1dzRYVlQzS3U1eWF0In0sIHsic2NoZW1hX25hbWUiOiAiUGVyc29uIiwgImlzc3Vlcl9kaWQiOiAiTTZkaHVGajVVd2JoV2tTTG12WVNQYyJ9XSwgIm5vbl9yZXZva2VkIjogeyJmcm9tIjogMTcwODAyNDIzMiwgInRvIjogMTcwODAyNDIzMn19fSwgInJlcXVlc3RlZF9wcmVkaWNhdGVzIjoge319"
                            }
                        }
                    ],
                    "comment": null,
                    "~service": null
                }
            }
        }
    ],
    "services": [
        "6PmHCm4rJWVE1y9u7MxRiro7j6zzo9XWuKYDAChyivbS"
    ]
}

I tested from home and am getting the same error - BC Wallet version 1.0.15 Build (1531)

@loneil How can I reproduce this? I need to get the QR code to scan so I can see the logs.

@loneil Can I gen the QR code so that I can try and reproduce with logging on?

That's a bit tricky, since this is running VCAuthN on my local, though it IS using ngrok so I could share a QR code with you maybe.
(I could show you how to start up VCAuthN locally as well maybe)
The other option is if there's a running VCAuthN env we could flip over the OOB flag. @esune do you know?

Probably the easiest would be to run VC-AuthN locally in demo mode. Instructions are in the repo readme, you'd have to change this line to true before running it to generate an OOB proof-request.

@jleach @cvarjao can we reopen this as it seems like it broke again?
@nodlesh do you still see errors related to this / #1147 in the test harness?

@esune, this is probably an Credo (former AFJ) issue, can you reproduce with just Credo?

@cvarjao I have only tested with BC Wallet since I do not have a Credo agent I can use. Is there boilerplate I could use to run tests/ Otherwise I'll have to get some time to familiarize with the framework and set-up an agent/exchange to test.

@esune The OOB Proof Attachment BC Wallet regression tests for both Android and IOS are passing consistently.

@nodlesh is this for connection-less OOB proof requests? Conenction-based proofs might work differently.
I might try gathering some info with remote logging.

I finally managed to run a test with OOB and remote logging (thanks @jleach, that was super easy!).
BC Wallet scans the QR code and tells me it is in invalid URL - things don't work.
Remote logging doesn't show much, just a message about a received message once the QR code is scanned:

The payload returned by VC-AuthN can be seen here:

The first payload uses a connection-less proof-request, and it works fine
The second payload is using an OOB proof-request, and doesn't work

I'll try and take a look at AATH to see if I can figure out any differences in the payloads (@nodlesh if you have pointers to where to look or how to extract it let me know), but as-is I am a bit stuck in the investigation.

@esune  Is it not the Goal Code that is the difference? Goal Codes are not used in AATH yet.

@esune Is it not the Goal Code that is the difference? Goal Codes are not used in AATH yet.

connection-less does not use goal codes at all. The OOB connection-less does, however I can't see how that would trigger the "invalid URL" bit (but I couldn't figure out what's going on under the hood in the wallet).

@cvarjao here is the vcauthn oob connectionless payload that is being rejected:
{
  "@id": "2700f47e-0430-4f45-b34e-5c4057c6265a",
  "@type": "https://didcomm.org/out-of-band/1.1/invitation",
  "goal_code": "request-proof",
  "label": "vc-authn Out-of-Band present-proof authorization request",
  "requests~attach": [
    {
      "@id": "request-0",
      "mime-type": "application/json",
      "data": {
        "json": {
          "@id": "2700f47e-0430-4f45-b34e-5c4057c6265a",
          "@type": "did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation",
          "request_presentations~attach": [
            {
              "@id": "libindy-request-presentation-0",
              "mime-type": "application/json",
              "data": {
                "base64": "eyJub25jZSI6ICIyMDg2Mjk2OTc3ODY1OTA2MDk5MTAwNjMiLCAibmFtZSI6ICJwcm9vZl9yZXF1ZXN0ZWQiLCAidmVyc2lvbiI6ICIwLjAuMSIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsicmVxX2F0dHJfMCI6IHsibmFtZXMiOiBbImdpdmVuX25hbWVzIiwgImZhbWlseV9uYW1lIiwgImNvdW50cnkiXSwgInJlc3RyaWN0aW9ucyI6IFt7InNjaGVtYV9uYW1lIjogIlBlcnNvbiIsICJpc3N1ZXJfZGlkIjogIkw2QVNqbUREYkRIN3lQTDF0MnlGajkifSwgeyJzY2hlbWFfbmFtZSI6ICJQZXJzb24iLCAiaXNzdWVyX2RpZCI6ICJRRXF1QUhrTTM1dzRYVlQzS3U1eWF0In0sIHsic2NoZW1hX25hbWUiOiAiUGVyc29uIiwgImlzc3Vlcl9kaWQiOiAiTTZkaHVGajVVd2JoV2tTTG12WVNQYyJ9XSwgIm5vbl9yZXZva2VkIjogeyJmcm9tIjogMTcxODA0MTcwMywgInRvIjogMTcxODA0MTcwM319fSwgInJlcXVlc3RlZF9wcmVkaWNhdGVzIjoge319"
              }
            }
          ],
          "comment": null,
          "~service": null
        }
      }
    }
  ],
  "services": [
    {
      "recipient_keys": [
        "2gMSwKkZe1oA8H7jFCHSsGGeCoSH489N6PTc2Qtg8jKJ"
      ],
      "routing_keys": [],
      "service_endpoint": "https://0c25-75-156-98-192.ngrok-free.app",
      "id": "did:vc-authn-oidc:123456789zyxwvutsr#did-communication",
      "type": "did-communication",
      "priority": 0
    }
  ]
}

The error it rejects with is No message class found for message type "https://didcomm.org/out-of-band/1.1/invitation"
I searched both orgs (hyperledger and openwallet-foundation) and couldn't find the string "class found for" in any repo

@loneil are we good to close this issue with the fix we found yesterday?

I think we could close it as I believe there's no changes needed on the Wallet side going forward for this and we will make some changes in VCAuth-N (issue to come on that repo)

Relevant issue (and linked PR fix in there) https://github.com/bcgov/vc-authn-oidc/issues/545


Update collate

Pull Request Test Coverage Report for Build 443

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.789%

Totals

Change from base Build 437:
0.0%

Covered Lines:
2689

Relevant Lines:
3248

💛  - Coveralls


Alpha 7 not opening

2023-10-07T14:00:05 | comicapi.comicarchive | WARNING | Failed to load talker: rar
2023-10-07T14:00:05 | comicapi.comicarchive | WARNING | Failed to load talker: sevenzip
2023-10-07T14:00:05 | comictalker | ERROR | Failed to load talker: comicvine
Traceback (most recent call last):
File "comictalker_init_.py", line 28, in get_talkers
File "importlib_metadata_init_.py", line 209, in load
File "importlib_init_.py", line 127, in import_module
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in _find_and_load_unlocked
File "", line 228, in _call_with_frames_removed
File "", line 1030, in gcd_import
File "", line 1007, in find_and_load
File "", line 984, in find_and_load_unlocked
ModuleNotFoundError: No module named 'comictalker.talkers'
2023-10-07T14:00:05 | comictalker | ERROR | Failed to load talker: metron
Traceback (most recent call last):
File "comictalker_init.py", line 28, in get_talkers
File "importlib_metadata_init.py", line 209, in load
File "importlib_init.py", line 127, in import_module
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in _find_and_load_unlocked
File "", line 228, in _call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'metron_talker'
-->
Tested on 2 different systems (Windows 10 and 11)

Fixed in 1.6.0-alpha.8


MCMC hyperparameter marginalization

Rather than only relying on point-estimates for the hyperparameters, we should include the ability to average the acquisition scores over several draws from the log likelihood + log prior. This should not be too hard to accomplish given the support to sum acquisitions, and the MCMC support built in GPflow. What I had in mind:

Include an option for BayesianOptimizer to indicate the number of draws (n)
Copy the acquisition n times and sum them all together. This sum acquisition will then be optimized to select new sampling decisions
Each iteration, request all models of one of original acquisition object. Call sample on each model to obtain n draws. Then visit each acquisition of the sum and call set_state() on the models.

These steps only require limited changes in BayesianOptimizer. Two issues currently prevent implementation

When copying an acquisition object (and its underlying models) the order of sorted_params can change. This means calling set_state() with a free state vector obtained from another copy can have the wrong order. GPflow/GPflow#417 would solve this if merged
Right now, ei + ei + ei results in a tree structure, it would simpler if it results in some form of AggregateAcquisition which concatenates the scores and applies tf.reduce_sum. This would reduce the size of the tree and the TensorFlow graph, and is more efficient (I guess). This would require some additional code: I'm playing around with this right now and it seems to be straightforward.

Both issues were addressed, started working on this.

#31 implements the MCMC hyperparameter marginalization.


1.24 broke/removed markdown support for base64 data URIs in CompletionItem & Hover

VSCode Version: 1.24
OS Version: Windows 10 Pro 64-bit

It would seem that the most recent update broke a feature that I was (ab)using to render images in CompletionItemProvider and HoverProvider: The base64 encoded image is no longer displayed:

In previous version, it worked like this:

This functionality can be tested with vscode-fontawesome-autocomplete

Install the extension
Create a new .html file
Start typing fa and browse the auto-completion items. Expand the documentation by clicking the blue i button if necessary.

Looks like your data uri contains spaces. I don't know why this worked previously but it likely should not have. Try either percent encoding it or base64 encoding it
Other extensions using data-uri images (such as color info) seem to work fine in the latest release

@mjbvz Thanks for the quick response, base64 encoding the image data indeed fixed the issue.
Off-topic note:
I guess the markdown rendering engine was updated? Not really an issue but it seems that tables no longer render properly if the heading row cells only consist of spaces. Apparently adding a   to the first header cell fixes that.


WIP : Minor fixes for record readers, transforms needed

What changes were proposed in this pull request?

TransformProcessRecordReader calls its member RecordReader's initialize(...) method from within its own. This appears to be necessary for using TPRR with, e.g., a CsvRecordReader.
Added an "ignore unknown tokens" option to StringListToCategoricalSetTransform. I'm using this transform to convert a text field into binary BOWs and we want to have the option to ignore tokens that aren't in our vocabulary or replace them with "UNK."

For the latter point, one alternative would be to leave the existing transform unchanged and move this sort of functionality into a dedicated "BOW" transform.
How was this patch tested?
Manual tests. Shouldn't be hard to add unit tests -- I'll try to get around to that in the coming days.
Please review
https://github.com/deeplearning4j/deeplearning4j/blob/master/CONTRIBUTING.md before opening a pull request.

@emsixteeen you probably want to be working off this branch!

Most of these have been fixed by other branches so I'm closing it.


Ingest null value for INT and LONG type column in Druid

I am ingesting some data from JSON to Druid. The input data has null value for some of the INT and LONG fields. I want to store them as null, instead of storing them as 0. I am not able to figure out how to do that. Can anyone guide me through?
There is a similar question on stackoverflow - Apache Druid can store null value for number. The answers say it can be done, but it's not clear how it can be done.
Thanks,

Solution -
druid.generic.useDefaultValueForNull=false is actually a system property and has to be added in following config file that will not convert null to 0. By default druid.generic.useDefaultValueForNull=true, and that is why the issue.
druid/conf/druid/cluster/_common/common.runtime.properties
I must say, documentation is little bit vague though.


[ZEPPELIN-559] Cassandra interpreter v2

What is this PR for?

Update the Cassandra interpreter to V2 to support new schema commands to describe Cassandra 3.x features:

User Defined Functions
User Defined Aggregates
Materialized Views

Add support for single line comment using double slashes (//)
Add DESCRIBE TYPES
The Java driver version is bumpted to 3.0.0-rc1
The contextual HELP menu is also updated and a ChangeLog section is added.

What type of PR is it?
[Improvement]
Todos

[x] - Add new PR to update official Cassandra interpreter with new features
[ ] - Code review by the community (warning, Scala inside)

Is there a relevant Jira issue?
ZEPPELIN-559
ZEPPELIN-575 for doc
How should this be tested?

Download and install locally Cassandra 3.1.1
Start Cassandra
Clone this pull request locally with:

git fetch origin pull/600/head:CassandraInterpreterV2
git checkout CassandraInterpreterV2

Build this version of Zeppelin with mvn clean package -DskipTests
Start Zeppelin and update the property cassandra.hosts of the Cassandra interpreter (set it to localhost or <IP_ADDRESS> depending on your configuration)
In a paragraph, execute all the CQL statements given in this CassandraInterpreterV2TestData.cql by copy-pasting them
Start a new %cassandra paragraph and execute DESCRIBE FUNCTION test.maxOf;. You should be able to see:

Start a new %cassandra paragraph and execute DESCRIBE AGGREGATE test.group_by;. You should be able to see:

Start a new %cassandra paragraph and execute DESCRIBE MATERIALIZED VIEW test.user_by_country;. You should be able to see:

Start a new %cassandra paragraph and execute SELECT id,val1,val2,maxOf(val1,val2) FROM test.test_max;. You should be able to see:

Start a new %cassandra paragraph and execute SELECT group_by(category,sales_count) FROM test.items;. You should be able to see:

Start a new %cassandra paragraph and execute SELECT * FROM test.user_by_country WHERE country='FR';. You should be able to see:

Questions:

Does the licenses files need update? --> No
Is there breaking changes for older versions? --> No
Does this needs documentation? --> Yes

@doanduyhai thanks for the contribution, I know you gave some details in the JIRA issue, but could you update this PR description with our PR template? (https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#creating-a-pull-request)

Just checked the full process, Cassandra interpreter v2 and new CQL scripts, all is ok

@doanduyhai Great improvement! Somehow last commit didn't trigger CI. Could you trigger CI for last commit?

@corneadoug @Leemoonsoo
Code review has been done by @brianwawok and I pushed some refactoring.
The build succeeded but Travis marked it as failed because : The log length has exceeded the limit of 4 Megabytes (this usually means that test suite is raising the same exception over and over)
Looks like this is a very common issue with Travis, it is reported here: https://github.com/travis-ci/travis-ci/issues/3865

@Leemoonsoo @corneadoug Finally successful build

Those headers :)
I don't usually review interpreters, but I will test it out :)

Thanks @doanduyhai  for big improvement!
LGTM

LGTM. Any more comments or discussion on this PR?

Merge if there're no more discussions

Tested, very nice interpreter thank you @doanduyhai !
A small amendment: to test this, make sure UDF sandbox is enabled in conf/cassandra.yaml
enable_user_defined_functions: true
Let's merge it


Typescript support

This is a great utility, thanks for publishing it. I was wondering if you have any intentions to add types for Typescript?

Also, seem to be getting this error after following your readme

I am on NextJS 1.14.1

In your tsconfig.json file, change the compilerOptions.moduleResolution to Bundler.

I am on NextJS 1.14.1

I'm sorry, which version are you using? I developed the package on the latest version of NextJS, and the feature I used was introduced in 14.2.0 (or 14.1.1-canary.9).
I'm going to start working on a solution to make it compatible, but I highly recommend you update because you are missing out on tons of improvements and bug fixes. For most users, the update process is simply changing the version of the dependency. You can read the changelogs here: https://nextjs.org/blog/next-14-2


keymap  may cause content loss

My lua config for vscode-neovim:
local keymap = vim.api.nvim_set_keymap
local opts = { silent = true, noremap = true }

keymap('i', '<C-l>', '<Right>', opts)
keymap('i', '<C-h>', '<Left>', opts)
keymap('i', '<C-j>', '<Cmd>call VSCodeNotify("deleteWordLeft")<Cr>', opts)
keymap('i', '<C-k>', '<Cmd>call VSCodeNotify("deleteWordRight")<Cr>', opts)

When I type in insert mode and ESC exits, the content is lost, only occurs at the first insertion after the up and down movement, the error is as follows:

does setting affinity help? https://github.com/vscode-neovim/vscode-neovim/issues/1051

and ESC

if it's after ESC I would guess it's related to vscode-neovim's attempt to track insert-mode "redo".
https://github.com/vscode-neovim/vscode-neovim/issues/1139


torcs: add musicplayer.patch

Unbreaks build of torcs.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Where is this patch from? The preference is to not maintain patch files in nixpkgs like this, but fetch them from elsewhere if possible.

@aanderse I have written this patch myself to fix the build on NixOS. I am not aware of any other distros that have to do the same.

The original triggers "invalid conversion from char to whatever"? If so that seems like an upstream problem and not specific to the nixpkgs toolchain, or am I missing something?

The patch is also available on Salsa:
https://salsa.debian.org/games-team/torcs/raw/32bbe77c68b4de07b28c34497f3c0ad666ee618d/debian/patches/gcc7.patch
I added it to #59316 and built it locally. I'll merge that other PR soon.


[Feature request] don't restrict Git to HTTP/1.1 in Checkout task until after the checkout is complete

My organization has discovered that if we run the exact same commands as are executed by the Microsoft-provided checkout task (which is implemented within the agent runner rather than in the pipeline-tasks repo) but we omit the line git config http.version HTTP/1.1, the performance of our checkout is dramatically faster. By combining this with the changes mentioned in #3352, we've seen an 80-90% reduction in our checkout times.
Based on the comments in the codebase and the feedback we've gotten from engaging our Microsoft support contacts, we've been told that this HTTP/1.1 restriction is in place because IIS can reject large pushes to Azure git repos when HTTP/2 is being used. However, since the checkout job only fetches/checks out and does not do any pushes, it would be ideal if at least the invocation of git config http.version HTTP/1.1 could be moved to after the initial checkout is complete, so that any subsequent pushes can be protected from failing, but the initial checkout can benefit from the massive speed benefits of not being locked to the older standard.
Alternately, since according to the documentation that's linked in the comment mentioned above it seems like the header limit is user-defined, a better solution would be for the IIS instance underlying Azure Git repos to be configured correctly such that git can be properly supported over HTTP/2, as it seems likely that similar performance improvements would be seen for other git operations besides fetching.

This is not stale, it's an active enhancement request.

This is not stale, it's still an active enhancement request.

@sphanley thanks for reporting! @MaximMalygin could you please take a look?
Is it possible/would it make sense to adjust configuration on ADO side?
We could probably invoke git config http.version HTTP/1. after checkout, but not sure if it's fully supported now.

Probably we should tested it, because i'm not sure if it works correctly for all repositories

Hi @sphanley, thank you for your contribution.
After my tests it seems that we will not have significant change with different options on http.version parameter. Due to git client uses smart protocol, the performance is closer to HTTP/2
Regarding your second suggestion to implement feature flag for checkout command parameters - if there is not any tag the checkout speed will same, if there is, it is necessary to download it as well.
Closing this, feel free to ask any other questions or let us know if it's still relevant for you.


unable to signup

when i try to sign up it shows a strange error in console
MongooseError: Operation users.findOne() buffering timed out after 10000ms
my mongo db is working correctly i dont know why this error comes

Usually when this happens it means your MongoDB has not been set up correctly


Tests : proving client tests

Added tests for proving client.
Updated the implementation and types for sharp client as per the specs provided in this doc here : SHARP prover specs
Fixed the fact calculation logic in get_fact_info function.

coverage: 59.789% (+3.4%) from 56.401%
when pulling cc98db1b0bc958c8d0fa6464d0ee2de6e8ae6d35 on test/proving-client-tests
into 7e771e709c2fba2b7da96bcf2e249ee27c1ca249 on main.

Requesting review @EvolveArt 🙏


Use llmv_asm! macro for inline assembly

\ fixes #204
the asm! macro will soon be deprecated.
This changes all of the asm! calls to llvm_asm!
To my knowledge doing a direct replacement should be fine.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @korken89 (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.


docs: leverage proto docs update

Description
Updates related to https://github.com/umee-network/umee/pull/1369

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

buf CI error fixed in https://github.com/umee-network/umee/pull/1397


Accessing the local mlbgame database directly

How can i directly access the database instead of using the python module?

I'm not quite sure exactly what you are asking, but the local game data is stored in mlbgame/gameday-data and the remote data from mlb.com can be accessed here: http://gd2.mlb.com/components/game/mlb/. The data is not stored in a database, but rather as compressed XML files, and the data provided by mlb.com are XML files.


Mark dirs with a slash in Composer config

as in here https://getcomposer.org/doc/04-schema.md#psr-4

Thanks!

You're welcome.


Support automatically running tests on file save

Now that there is Support for continuous (autorun) tests, it would be nice to have it enabled for Python.
Previous requests I've found, closed before the extension API was available:

https://github.com/microsoft/vscode-python/issues/5769
https://github.com/microsoft/vscode-python/issues/18305

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.

I didn't solicit votes since on the day I opened the issue you removed the "needs community feedback" label and added the "needs PR" and "partner ask" ones.
This is a classic workflow for Test Driven Development and it is available in competing IDEs. Hence my ask to consider reopening this issue. Thanks.


[WIP] Update cluster version to v1.16

Checklist

[ ] Chart Version bumped

https://github.com/chatwork/charts/pull/188


Allow webpack config customizations

Maybe this is out of the scope of jspsych-builder (and maybe I'm among the few that prefer markdown to raw HTML), but... I think having the ability to leverage mdx, since we can use React  would be awesome. 😅
I'm not too sure if this starts approaching the maintenance/usage level of an SSG (e.g., next.js), but having the ability to specify instructions/whatnot in mdx would certainly be preferable to writing HTML as strings or at all (imo).
(If this does increase the management load to something akin to an SSG, feel free to close this. 😅)
Maybe this makes more sense as a "open up projects to customizing Webpack through a top-level webpack.config.js" or equivalent? (I wager this would minimize workload on your end while enabling users to "do what they want".)

and maybe I'm among the few that prefer markdown to raw HTML

At least you're not alone; I've been using Marked for this. Didn't know mdx yet, looks interesting!

Maybe this makes more sense as a "open up projects to customizing Webpack through a top-level webpack.config.js" or equivalent? (I wager this would minimize workload on your end while enabling users to "do what they want".)

Right, that would be quite social :smile: I think we can default-export a function from webpack.config.js that takes the predefined webpack config and returns a modified version of that. Which would need some words of caution, since the config may change in a then breaking way even in minor releases... WDYT?

The approach seems reasonable, too. Maybe this also gives a way to resolve #19, too?
Also, I included MDX support on a local copy of jspsych-builder and it seems to work so far. I may submit a ReactPlugin to demonstrate how to integrate React components into jsPsych.
Definitely agreed on words of caution. Also seems reasonable to throw in a "minimal/no support" for custom webpack.config.js since that could balloon time commitment. 😅

Maybe this also gives a way to resolve #19, too?

Not too sure if it does, since the port is only a config option of the dev server, not the compiler (AFAIK). Anyway, I'd say the port use case is frequent enough to be supported stably!

👋 so... I managed to get this working, but it required setting jspsych-builder to be a commonjs module.
# package.json
- "type": "module",

# tsconfig.json
- "module": "esnext",
+ "module": "commonjs",

Seemingly, nothing changes. (I'm able to start the dev server, use MDX, and the like.)
I'll open a PR shortly with these changes so you can take a look. 🙂


CJS/UMD bundles don't export placements and other enums

Today I came across a weird issue after importing {placements} from '@popperjs/core' for use in the prop types of a component I built. It worked fine in my Storybook development environment, but when running our tests (using Jest), I got an error (TypeError: Cannot read property 'filter' of undefined). Turns out that in Jest, the CJS build is used, and it's missing some exports that exist in the ESM build (like placements). I assume they're being tree-shaken too aggressively?
It would be great if this could be fixed so that all builds have the same exports.

I had the same problem, but it was closed https://github.com/popperjs/popper-core/issues/1259

I don't plan to expose all the internal enums from the UMD and CJS builds since they are not tree-shakeable and would negatively affect the bundle size.
I just pushed a commit to build enums.js for CJS and UMD so that you can manually import them though. Please let me know how does it look.

We ran into this issue and spent time tracking it down. Same thing. Works in an ESM environment, but not in a CommonJS environment (like Jest).
I don't agree with "they are not tree-shakeable and would negatively impact the bundle size". The enums are in the dist/cjs/popper.js file:
var top = 'top';
var bottom = 'bottom';
var right = 'right';
var left = 'left';
var auto = 'auto';
var basePlacements = [top, bottom, right, left];
var start = 'start';
var end = 'end';
var clippingParents = 'clippingParents';
var viewport = 'viewport';
var popper = 'popper';
var reference = 'reference';
var variationPlacements = /*#__PURE__*/basePlacements.reduce(function (acc, placement) {
  return acc.concat([placement + "-" + start, placement + "-" + end]);
}, []);
var placements = /*#__PURE__*/[].concat(basePlacements, [auto]).reduce(function (acc, placement) {
  return acc.concat([placement, placement + "-" + start, placement + "-" + end]);
}, []); // modifiers that need to read the DOM

var beforeRead = 'beforeRead';
var read = 'read';
var afterRead = 'afterRead'; // pure-logic modifiers

var beforeMain = 'beforeMain';
var main = 'main';
var afterMain = 'afterMain'; // modifier with the purpose to write to the DOM (or write into a framework state)

var beforeWrite = 'beforeWrite';
var write = 'write';
var afterWrite = 'afterWrite';
var modifierPhases = [beforeRead, read, afterRead, beforeMain, main, afterMain, beforeWrite, write, afterWrite];

Perhaps @FezVrasta means dead code elimination? The only thing missing is the following at the bottom of the file:
exports.placements = placements


About the location of the whatsapp session file

Hi...
Would you mind asking where's the whatsapp session file reside as I can't it after scanning the QR code running inside the docker.
I've called docker exec -it <docker> sh to go inside docker daemon but I just can't find the corresponding file.
Would anyone could help guide me through?
Thank you so much

Where did you find it?

Nope really.... I found out seems if SessionFile is set the next time the docker restart no need to scan the QR code again.
However, turn out I believe I still need to know the location of the session file and backup in case any problems on the docker that need to be reinstalled
So, would anybody help this thro? Thanks

See whatsapp config in matterbridge.toml.sample, specifically
# First time that you login you will need to scan QR code, then credentials willl be saved in a session file
# If you won't set SessionFile then you will need to scan QR code on every restart
# optional (by default the session is stored only in memory, till restarting matterbridge)
SessionFile="session-48111222333.gob"

So assuming you are setting the session filename, it will be relative to the current working directory inside docker. Can we see your Dockerfile or docker-compose file?

seems solved... yup... in the root directory once it scan... great~


[flash_ctrl] Split hardware / software interface reads.

Fix issue identified in #14011
In the original design, the life cycle interface and software interface
shared the read data path. This works fine except in RMA entry.
Upon RMA entry, since the datapath is shared, the life cycle interface
clears out all the read FIFO contents so that it can take over the
FIFO.  However, this means any data deposited in the FIFO that software
was intending to read is now no longer valid.
Practically speaking, this is not a problem. As we really do not care if
a host can successfully read when RMA entry begins.  However, this
behavior creates a situation where it is difficult for DV to predict
hardware behavior around RMA entry without probing internal signals.
By splitting the read path (very little overhead), we allow the software
data already depositted to stay alive while the RMA wipe begins.
Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

@eshapira please have a look. This changes touches the fix that was made previously for an init_busy failure.
I ran it against the same test and didn't see issues, but maybe you'll want to double check.

@eshapira please have a look. This changes touches the fix that was made previously for an init_busy failure. I ran it against the same test and didn't see issues, but maybe you'll want to double check.

@tjaychen Sorry it took me some time, LGTM.


Device should be booted only when we change the permission status

In Detox when we set the device permission the simulator is booted again but it happens every time suppose when start the app and the location permission is not given , Now if we want to check an instance where we do not want to give location permission , to handle this we have to pass location permission as 'No'. Now already the permission status is 'No' and we are also passing as 'No' then in that case the device should not be booted.

This is a AppleSimulatorUtils issue, but don't open an issue, as I will respond here: There is no convenient way to read these permissions.
I recently made changes to applesimutils to only reboot the device when absolutely necessary. This should improve your test times. Please update your applesimutils and try.


MTV-1354 | Ignore namespaces when choosing the v2v pod on the nodes

Issue: When a user has a plans across many namespaces the v2v anti-affinity does not look for the other pods in different namespaces when using the anti-affinity.
Fix: This PR disables the namespace selector so it looks across whole cluster for the pods and distributes the pods evenly.

This change improves the efficiency of the migrations with many different namespaces. It's done by distributing the migration pods evenly across all nodes in the cluster.
Here is an example before and after the change where you can see the network throughput doubled from 200 MBps to 400 MBps


WSGIRequest object has no attribute kbsite

This is pull of latest code.  Probably has to do with all the default / multisite changes going on recently.
Can't get to certain views.  And Kegbot core crashes when trying to start.
Here is a screenshot of the sentry error:
https://skitch.com/raytiley/gum84/kegbot-crash
Thanks
-ray

Made the changes docman suggested in irc, but now it crashes when I do a pour.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 284, in run
self.finish_response()
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 324, in finish_response
self.write(data)
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 403, in write
self.send_headers()
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 467, in send_headers
self.send_preamble()
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 385, in send_preamble
'Date: %s\r\n' % http_date()
File "/usr/lib/python2.7/socket.py", line 324, in write
self.flush()
File "/usr/lib/python2.7/socket.py", line 303, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe
Exception happened during processing of request from ('<IP_ADDRESS>', 44111)
Traceback (most recent call last):
File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request
self.finish_request(request, client_address)
File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/local/lib/python2.7/dist-packages/Django-1.3.1-py2.7.egg/django/core/servers/basehttp.py", line 570, in init
BaseHTTPRequestHandler.init(self, *args, **kwargs)
File "/usr/lib/python2.7/SocketServer.py", line 641, in init
self.finish()
File "/usr/lib/python2.7/SocketServer.py", line 694, in finish
self.wfile.flush()
File "/usr/lib/python2.7/socket.py", line 303, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe
2011-12-22 13:35:51,463 INFO     (flowmanager) Starting flow: <Flow 0x4ef3a258: tap=kegboard.flow0 ticks=0 username='' max_idle=0:00:10>
2011-12-22 13:36:12,134 INFO     (flowmanager) Flow has become too idle, ending: <Flow 0x4ef3a258: tap=kegboard.flow0 ticks=1742 username='' max_idle=0:00:10>
2011-12-22 13:36:12,135 INFO     (flowmanager) Stopping flow: <Flow 0x4ef3a258: tap=kegboard.flow0 ticks=1742 username='' max_idle=0:00:10>
2011-12-22 13:36:12,143 INFO     (drink-manager) Flow completed: flow_id=0x4ef3a258
2011-12-22 13:36:13,160 ERROR    (service-thread) Uncaught exception in thread service-thread. Stack trace:
2011-12-22 13:36:13,193 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/util.py", line 113, in run
2011-12-22 13:36:13,194 ERROR    (service-thread)     self.ThreadMain()
2011-12-22 13:36:13,194 ERROR    (service-thread)
2011-12-22 13:36:13,195 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/kb_threads.py", line 124, in ThreadMain
2011-12-22 13:36:13,195 ERROR    (service-thread)     self._Step(timeout=0.5)
2011-12-22 13:36:13,196 ERROR    (service-thread)
2011-12-22 13:36:13,196 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/kb_threads.py", line 129, in _Step
2011-12-22 13:36:13,197 ERROR    (service-thread)     self._ProcessEvent(event)
2011-12-22 13:36:13,198 ERROR    (service-thread)
2011-12-22 13:36:13,205 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/kb_threads.py", line 156, in _ProcessEvent
2011-12-22 13:36:13,206 ERROR    (service-thread)     cb(event)
2011-12-22 13:36:13,206 ERROR    (service-thread)
2011-12-22 13:36:13,207 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/manager.py", line 462, in HandleFlowUpdateEvent
2011-12-22 13:36:13,207 ERROR    (service-thread)     self._HandleFlowEnded(event)
2011-12-22 13:36:13,208 ERROR    (service-thread)
2011-12-22 13:36:13,210 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/manager.py", line 491, in _HandleFlowEnded
2011-12-22 13:36:13,210 ERROR    (service-thread)     spilled=spilled)
2011-12-22 13:36:13,212 ERROR    (service-thread)
2011-12-22 13:36:13,213 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/core/backend.py", line 302, in RecordDrink
2011-12-22 13:36:13,214 ERROR    (service-thread)     duration=duration, auth_token=auth_token, spilled=spilled)
2011-12-22 13:36:13,215 ERROR    (service-thread)
2011-12-22 13:36:13,215 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/web/api/krest.py", line 251, in RecordDrink
2011-12-22 13:36:13,216 ERROR    (service-thread)     return self.DoPOST(endpoint, models_pb2.Drink(), post_data=post_data)
2011-12-22 13:36:13,217 ERROR    (service-thread)
2011-12-22 13:36:13,218 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/web/api/krest.py", line 173, in DoPOST
2011-12-22 13:36:13,219 ERROR    (service-thread)     return self._FetchResponse(endpoint, out_msg, params=params, post_data=post_data)
2011-12-22 13:36:13,220 ERROR    (service-thread)
2011-12-22 13:36:13,221 ERROR    (service-thread)     File "/usr/local/lib/python2.7/dist-packages/kegbot-0.8.3-py2.7.egg/pykeg/web/api/krest.py", line 195, in _FetchResponse
2011-12-22 13:36:13,222 ERROR    (service-thread)     response_data = urlopen(url, data=encoded_post_data, timeout=FLAGS.krest_timeout).read()
2011-12-22 13:36:13,223 ERROR    (service-thread)
2011-12-22 13:36:13,224 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
2011-12-22 13:36:13,224 ERROR    (service-thread)     return _opener.open(url, data, timeout)
2011-12-22 13:36:13,225 ERROR    (service-thread)
2011-12-22 13:36:13,226 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 394, in open
2011-12-22 13:36:13,227 ERROR    (service-thread)     response = self._open(req, data)
2011-12-22 13:36:13,228 ERROR    (service-thread)
2011-12-22 13:36:13,229 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 412, in _open
2011-12-22 13:36:13,230 ERROR    (service-thread)     '_open', req)
2011-12-22 13:36:13,231 ERROR    (service-thread)
2011-12-22 13:36:13,232 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 372, in _call_chain
2011-12-22 13:36:13,233 ERROR    (service-thread)     result = func(*args)
2011-12-22 13:36:13,233 ERROR    (service-thread)
2011-12-22 13:36:13,234 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 1201, in http_open
2011-12-22 13:36:13,235 ERROR    (service-thread)     return self.do_open(httplib.HTTPConnection, req)
2011-12-22 13:36:13,236 ERROR    (service-thread)
2011-12-22 13:36:13,236 ERROR    (service-thread)     File "/usr/lib/python2.7/urllib2.py", line 1174, in do_open
2011-12-22 13:36:13,237 ERROR    (service-thread)     r = h.getresponse(buffering=True)
2011-12-22 13:36:13,237 ERROR    (service-thread)
2011-12-22 13:36:13,238 ERROR    (service-thread)     File "/usr/lib/python2.7/httplib.py", line 1027, in getresponse
2011-12-22 13:36:13,242 ERROR    (service-thread)     response.begin()
2011-12-22 13:36:13,243 ERROR    (service-thread)
2011-12-22 13:36:13,244 ERROR    (service-thread)     File "/usr/lib/python2.7/httplib.py", line 407, in begin
2011-12-22 13:36:13,244 ERROR    (service-thread)     version, status, reason = self._read_status()
2011-12-22 13:36:13,248 ERROR    (service-thread)
2011-12-22 13:36:13,248 ERROR    (service-thread)     File "/usr/lib/python2.7/httplib.py", line 365, in _read_status
2011-12-22 13:36:13,249 ERROR    (service-thread)     line = self.fp.readline()
2011-12-22 13:36:13,249 ERROR    (service-thread)
2011-12-22 13:36:13,250 ERROR    (service-thread)     File "/usr/lib/python2.7/socket.py", line 447, in readline
2011-12-22 13:36:13,250 ERROR    (service-thread)     data = self._sock.recv(self._rbufsize)
2011-12-22 13:36:13,251 ERROR    (service-thread)
2011-12-22 13:36:13,251 ERROR    (service-thread) Error was: <class 'socket.timeout'>: timed out
2011-12-22 13:36:13,252 ERROR    (service-thread) Exiting thread.
2011-12-22 13:36:14,052 ERROR    (watchdog-thread) Thread service-thread died unexpectedly
2011-12-22 13:36:14,100 INFO     (net-thread) got quit event, quitting
2011-12-22 13:36:14,100 INFO     (eventhub-thread) got quit event, quitting
2011-12-22 13:36:14,101 INFO     (watchdog-thread) got quit event, quitting
2011-12-22 13:36:14,102 INFO     (heartbeat-thread) got quit event, quitting
2011-12-22 13:36:14,102 INFO     (alarmmanager-thread) got quit event, quitting
2011-12-22 13:36:14,436 INFO     (kegnet) Stopping server
2011-12-22 13:36:15,091 ERROR    (main) Watchdog thread exited, quitting
2011-12-22 13:36:16,093 INFO     (main) Stopping any remaining threads
2011-12-22 13:36:16,093 INFO     (main) Stopping all service threads.
2011-12-22 13:36:16,094 INFO     (main) All service threads stopped.
2011-12-22 13:36:16,095 INFO     (main) Kegbot stopped.


WP-6538 Dart 2 and DDC compatibility changes.

Description
Changes to make this package compatible with Dart 2 and the Dart Dev Compiler.
Testing

[ ] CI passes (on both the stable and the dev channels)

Code Review
@Workiva/app-frameworks
@robbecker-wf

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on HipChat: InfoSec Forum.

+10 compiled example and test directory with DDC Dart 1. Compiled example directory with Dart 2 DDC.
(test directory did not compile with Dart 2 DDC - needs a newer dart2 compatible async package ... but then it wouldn't be backwards compatible)

QA +1

[ ] Testing instruction
[ ] Dev +1's
[ ] Dev/QA +10 with detail of what was tested

performed and documented by Rob

[ ] Security review (if required)
[ ] Unit tests created/updated
[ ] All unit tests pass
[ ] Rosie has run and reports properly the release the ticket will be included in

Merging into master.

@Workiva/release-management-pp


Move copyright in migrated java-util to proper druid.io form

👍

Looks like I missed copyright update in common.parsers package :(. Thanks @drcrallen :)


UPGRADE PROMPT_PREFIX | CITATIONS NON-EXISTING FILES

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Ask a question

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

azd version?

run azd version and copy paste here.
1.0.2

Versions

Mention any other details that might be useful

Hello,
I'm having some difficulty defining prompt_prefix functions.
I would like to use 100% and only the "power" of gpt to have it answer the queries by referring only to the sources of the indexed documents.
Even changing the prompt_prefix, we noticed that it answers questions that have nothing to do with the documents and also in the citation, it cites files that do not exist, I already went to the azure service in cognitive search and in the Indexes tab this document that he created and appears also in the container, this file he created is not there.

I've read some documentation on prompt engineering, but I believe it's in the wording for the prompt_prefix.
Could you support me to say what is the correct set of words to avoid these false positives

Thanks! We'll be in touch soon.

This is probably related to #388
As of today, OpenAI has removed the model for text-davinci-003, which is used for cognitive search queries.
You can switch to gpt-35-turbo, but the queries are significantly worse.
I have stumbled across a similar problem today.
There are files in my citations, that aren't existing on my blob-storage or in cognitive search.
I assume it is due to the changes OpenAI/Microsoft is currenctly doing, since text-davinci-003 has been removed.

I do not think so.
I see that changing the expressions in the prompt_prefix improves the result.
But, it still answers things that are not related to the document and cites non-existing files.
I believe that is the set of words used.

I said it is probably related, and not the cause.
As stated in #389  it seems, the prompt in combination with gpt-35-turbo might not be the best.
Which would mean, the reason you have these non-existent file references is caused by a combination of switching to gpt-35-turbo and using the initial prompt.
And that means, your problem is related to OpenAI deprecating davinci-003, as of today.

Closing this in favor of the more recent issue with current prompt: https://github.com/Azure-Samples/azure-search-openai-demo/issues/564


write a property test checking that supertypes are always greater than their subtype.

labelled as "good first issue" but you should probably know something about https://hexdocs.pm/stream_data/StreamData.html first


feat(static pages): use new subanavigation component

Description
use new sub navigation ui based on browser width and input links
Why
sub navigation ui is breaking if browser width is less
Issue
NA
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

FYI - Zero linter issues in this PR :)

This PR is dependent on this new component https://github.com/eclipse-tractusx/portal-shared-components/pull/78

This is dependent on https://github.com/eclipse-tractusx/portal-frontend/pull/374

@manojava-gk the pr and the changeLog is refering to a new "sub navigation ui"
I would have expected that its rather an update of the "sub navigation menu" component. Isnt it?
Also could you please mention the respective section where the component was updated (mention it for the ChangeLogs and in the PR description please)


Java compiler constant analysis seems to be broken on 8u301

After upgrading JDK from 8u291 to 8u301, some tests start failing: https://ge.gradle.org/s/upnw3rem6jm4i/tests/overview
There might be some internal change in JDK compiler.
Steps to reproduce:

Install JDK 8u301.
./gradlew -PtestJavaVersion=8 -PtestJavaVendor=oracle :language-java:eIT --tests CrossTaskConstantChangesIncrementalJavaCompilationUsingJarIntegrationTest

@asodja You did some changes in this area in the past. Do you have the bandwidth to take a look?

Checked and it seems this JDK does not track milliseconds of the files last modified timestamp so Gradle doesn't detect files as changed if there is a fast change. Will investigate with @wolfs and @blindpirate further.

There was a change in the JDK 8u301. File.lastModified() returns (https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8177809) timestamp with milliseconds but previously it did not. Unfortunately, this is inconsistent with Files.readAttributes(symlink, BasicFileAttributes.class) that is used in DirectorySnapshotter.
Due to that this code breaks:
https://github.com/gradle/gradle/blob/5ec3f672ed600a86280be490395d70b7bc634862/subprojects/core/src/main/java/org/gradle/api/internal/changedetection/state/CachingFileHasher.java#L86
since we use File.lastModified() for a marker file and Files.readAttributes(symlink, BasicFileAttributes.class) for snapshotted files, to detect if we can use cached value or not. And since these two methods return inconsistent timestamps we detect this incorrectly: in that case we take cached value even though we shouldn't.

Thank you for taking care of this, Anze!


Vulkan: StandardMaterial3D with any transparency does not cast shadows

Godot version
v4.0.alpha8.official [917fd6574]
System information
Mac OSX 12.4, M1 Pro
Issue description
I'm unable to get a material to render a shadow when I set any transparency other than "Disabled":

This seems related to https://github.com/godotengine/godot/issues/50344 but that seems fixed.
Steps to reproduce

Create a scene with a directional light and flat terrain that accepts shadows
Create a Mesh3D with a quad, give it a StandardMaterial3D and a texture with alpha in it.
Position it so you can see the shadow casted on the flat terrain.
Now set the material "Transparency" to anything other than "Disabled"

==! The shadow disappears.
Minimal reproduction project
shadow_test.zip

On GD4 Alpha13 Win10/64, I can get a shadow using depth prepass mode or alphascissors. Not with Alpha hash or alpha.

Also ProximityFade (part of the transparency pipeline) has no shadow, only self-shadows. No PF on the right. The rock looks weird because of #63675.

Also ProximityFade (part of the transparency pipeline) has no shadow, only self-shadows.

Alpha blending is used for materials with proximity fade enabled, so this is expected.

@Calinou Can this be added to the gd4 roadmap and material tracker https://github.com/godotengine/godot/issues/56333?

I can't reproduce the original issue anymore on 4.0.alpha13 (Linux, NVIDIA 515.57):

Please continue the discussion about the proximity fade issue in https://github.com/godotengine/godot/issues/63675.

The other proximity fade issue (#63675) is about z-ordering, and this issue is about shadows on different transparency modes, but this still leaves the fact that proximity fade doesn't have shadows at all, even though it can properly be used to fade with modes that have shadows such as alpha scissor.


Entering Long Mode: Mention physical address bits in the table describing a page table entry

In the paging section we describe the page table entry format this way:

An entry in the P4, P3, P2, and P1 tables consists of the page aligned 52-bit physical address of the frame or the next page table and the following bits that can be OR-ed in:

It is followed by a table with the various field descriptions. This table doesn't mention bits 12 to 51, because the preceding sentence already said that these bits contain a physical address. This approach seems to cause some confusion, e.g. on why we can just OR the address with some bits without overwriting important parts of it.
In the blog comments, Frank Afriat recommended that it “would be clearer to add in the Paging section the meaning of bits 12-31 containing the physical address of the next P or the physical address”. I agree with that (but it should be “bits 12 - 51”).
So I think we should do the following:

Describe bits 12-51 in the table.
Explain that the address is always page aligned, so that we don't need to store bits 0-11.
Explain that the address is 2MiB/1GiB aligned for huge pages.
Maybe remove the “the following bits that can be OR-ed in” formulation in the preceding sentence and use something simpler (e.g. “a page table entry has the following format”) instead.

I agree that the formulation is clunky. The entry is a bit field, with particular bits and bit ranges being reserved for different pieces of information. The fact that we can build the entry using shifts and bitwise or is an implementation detail, and doesn't serve well as an explanation.

Hi, Phil-opp
I have a problem when trying to compile and run your source code.
The situation is..
I tried to read(or write) the memory range 1M~955M on the computer, and the result was successful.
But when I tried to read(or write) the memory range 956M~1023M on the computer, the result was always crash...
I would like to ask if the page table or something needs to be modified?

@blackdogbro Hi, this is an old, outdated issue about a formulation in the "Entering Long Mode" post. Could you create a new issue for your problem?
About your issue: The crash could have various causes. Do you have your code online somewhere so that I can take a look?


Sandbox support

Added sandbox support in simmilar fashion as lokielse/omnipay-unionpay

hopefully this request will be approve


discussion data normalizations: loops vs. dipoles

cc @prisae, @dougoldenburg

Just comparing e-dipole-e-dipole, m-dipole-m-dipole, and m-loop-m-dipole:
https://nbviewer.jupyter.org/github/empymod/empymod-examples/blob/master/7b_Dipoles_and_Loops.ipynb
Some of that might be useful for this issue.


Custom navigation block - getInfo > index not correct

I am trying to add a custom navigation block with index / total items count indicator.
I'm using slider.getInfo();.
This returns info.index. However this is not always the correct index. For example, if my slider contains 2 items this will return info.index = 2 after initiating the slider.
My startIndex is 0.
Using version 2.8.8.

You could use displayIndex instead. Refer to here


Specifying desired height sensor

Per control.cpp#L452-L470, what is the motivation for adding the _control_status.flags.XX as logical ors inside the if/else statements for baro/gps? Are we trying to limit the height sensor fusion to one sensor only or fuse all that are available?
If the prior, seems to make sense to add add a param check for VDIST_SENSOR_EV (which exists in the enum already) to the first if statement and remove the _control_status.flags checks for baro/gps. If the later is the case, what purpose does the _params.vdist_sensor_type serve?

The original intention was to provide a structure to allow fusion of multiple height sources, but the height offsets were problematic unless additional states were added


Add FourierTransform

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes
See #292. But there was some change in constructors and mods indexation.
Related Issue
#292.
Closing issues
Closes #292.

Codecov Report

Merging #306 (5dd11b0) into master (2e2c006) will decrease coverage by 32.92%.
The diff coverage is 28.57%.

@@             Coverage Diff             @@
##           master     #306       +/-   ##
===========================================
- Coverage   87.63%   54.71%   -32.93%
===========================================
  Files          95       96        +1
  Lines        4683     4732       +49
===========================================
- Hits         4104     2589     -1515
- Misses        579     2143     +1564

Impacted Files
Coverage Δ

etna/transforms/fourier.py
27.08% <27.08%> (ø)

etna/transforms/__init__.py
100.00% <100.00%> (ø)

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-92.00%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.72% <0.00%> (-75.00%)
:arrow_down:

etna/transforms/statistics.py
27.50% <0.00%> (-71.67%)
:arrow_down:

etna/transforms/filter.py
28.57% <0.00%> (-71.43%)
:arrow_down:

... and 57 more

Continue to review full report at Codecov.

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


Icon Path or AllIcons Field
JavaScriptPsiIcons.Icons.FileTypes.TSX
What does it look like?

What Plugin?
(Integrated into) WebStorm
How to get to it?
Step One: Open WebStorm Project
Step Two: Create a .tsx file

Got it thanks, will wait a little bit and batch up all icon requests and complete them then. Thanks for reporting.


Improvements to kubernetes-basics/expose-intro.html

I was looking at issue 2907 and I thought this was something I could help with. I'm interested in contributing to the docs as I can. I couldn't do anything with the interactive part as that content seems auto-generated by katacoda. I assume I have to login at their site and do edits there once given the right access. Happy to do that too. In the meantime, take a look at these changes to the static part and see them running here:
http://<IP_ADDRESS>:9080/docs/tutorials/kubernetes-basics/expose-intro/

NOTE: Please check the “Allow edits from maintainers” box below to allow
reviewers fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

This change is

The travis-ci build may need to be restarted. This was opened a few days ago in the middle of their DB issue.

@mkorejo Might as well fix the merge conflict. That should kick off a new travis-ci build. If it happens again, I'll try to restart it via the travis-ci.org site.

@chenopis not following. I can't mark the conflict resolved as a I don't have the access. The changes in the PR are basically an overhaul of the page so there will always be a conflict that has to be merged manually by a contributor, if I understand correctly.
Am I doing this right or am I missing something? Thanks.

@mkorejo TL;DR: You many not have write privileges to master but you can pull from that into your branch and resolve the conflicts there.
If you're using the git command line or a git client, you'll need to pull master into your mkorejo:patch-2907 branch. It will give you a warning that there is a conflict, you can then go in and find which lines are in conflict and manually fix them. Then mark the conflict as resolved, do a commit, and then push the changes back up to your branch in GitHub.

@jaredbhatti This ready to be merged now?

@jaredbhatti @chenopis still looking for a tech review? thanks for shuffling this along.


Performance problem

We have a problem where Episerver edit mode takes forever to load.
I have been in contact with Episerver support and they have looked into the memory dumps.
Got this from the support:

My colleague took a look into some of the dumps now and reports that the issue appears to be in DbLocalizationProvider / EPiServer.DatabaseLocalizationProvider.GetAllStrings

We using the following packages:
<package id="DbLocalizationProvider.AdminUI.EPiServer" version="5.8.0" targetFramework="net471" />
<package id="DbLocalizationProvider.EPiServer" version="5.8.0" targetFramework="net471" />
<package id="DbLocalizationProvider.MigrationTool" version="5.8.0" targetFramework="net471" />
<package id="LocalizationProvider" version="5.7.7" targetFramework="net471" />
<package id="LocalizationProvider.Abstractions" version="5.7.7" targetFramework="net471" />
<package id="LocalizationProvider.AspNet" version="5.7.7" targetFramework="net471" />

Hi,
Do you have LegacyMode enabled? I mean do you have migrated resources in XPath format?
Which Episerver version are you at?

Hi,
Yes, EnableLegacyMode is enabled.
We are running these version:
  <package id="EPiServer.AddOns.Helpers" version="<IP_ADDRESS>" targetFramework="net471" />
  <package id="EPiServer.CMS" version="11.14.0" targetFramework="net471" />
  <package id="EPiServer.CMS.AspNet" version="11.14.0" targetFramework="net471" />
  <package id="EPiServer.CMS.Core" version="11.14.0" targetFramework="net471" />
  <package id="EPiServer.CMS.TinyMce" version="2.9.0" targetFramework="net471" />
  <package id="EPiServer.CMS.UI" version="11.23.3" targetFramework="net471" />
  <package id="EPiServer.CMS.UI.Core" version="11.23.3" targetFramework="net471" />
  <package id="EPiServer.Commerce.Core" version="13.14.1" targetFramework="net471" />
  <package id="EPiServer.Commerce.UI" version="13.14.1" targetFramework="net471" />
  <package id="EPiServer.Commerce.UI.CustomerService" version="13.14.1" targetFramework="net471" />
  <package id="EPiServer.Commerce.UI.ManagerIntegration" version="13.14.1" targetFramework="net471" />
  <package id="EPiServer.Framework" version="11.14.0" targetFramework="net471" />
  <package id="EPiServer.Framework.AspNet" version="11.14.0" targetFramework="net471" />
  <package id="EPiServer.Marketing.KPI" version="2.5.2" targetFramework="net471" />
  <package id="EPiServer.Marketing.KPI.Commerce" version="2.4.2" targetFramework="net471" />
  <package id="EPiServer.Marketing.Messaging" version="1.3.0" targetFramework="net471" />
  <package id="EPiServer.Marketing.Testing" version="2.5.11" targetFramework="net471" />
  <package id="EPiServer.Search" version="9.0.3" targetFramework="net471" />
  <package id="EPiServer.ServiceLocation.StructureMap" version="2.0.3" targetFramework="net471" />

But do you have XPath style resource keys?

Yes we have

This is known issue. I'm taking a look at it within v6 context. Release is pretty close already!


Implement Base IMostro Interface and Core Types

Description
Create the foundational interface structure for the Mostro Tools library following the specified IMostro interface, including all required types and basic event handling.
Testing Requirements

Basic class instantiation
Event emitter functionality
Connection handling
Type validation

Acceptance Criteria

[ ] Base class implements IMostro interface
[ ] All type definitions match protocol specifications
[ ] Event system properly initialized
[ ] Connection handling implemented
[ ] Tests passing
[ ] Documentation complete

References

Reference interface in web client
Mostro protocol documentation

@grunch Can you give me permission to assign so I can assign myself what I'm doing?


Emacs mailing list.

Hi:
Recently it has been commented in the emacs devel mailing list the interest to add tree-sitter support in vanilla.
https://lists.gnu.org/archive/html/emacs-devel/2021-06/msg00174.html
https://lists.gnu.org/archive/html/emacs-devel/2021-06/threads.html
This module is a very good starting point for that and it was mentioned that a very good first step is that this packages become part of the official Elpa repo.
It would be very nice if the developers of the emacs-tree-sitter package join to the developer team and help with the integration too  cause you already have the experience. The integration with vanilla can improve the user experience, simplify the installation "out of the box" experience while on the other hand we can provide a better support and functionalities to make it more efficient.
WDYT?

@ubolonton you were ping'd here https://lists.gnu.org/archive/html/emacs-devel/2021-06/msg00177.html

Let's keep the discussion on https://github.com/ubolonton/emacs-tree-sitter/discussions/127


Backend Migration

Checklist:

[x] I have updated the necessary documentation
[ ] I have signed off all my commits as required by DCO
[x] My build is green

Backend Migration (Work in progress)
https://github.com/procore-oss/backstage-plugin-announcements/issues/141
Tasks:

[x] Init entry plugin.tsx file

@gaelgoth made some progress on the collator in https://github.com/procore-oss/backstage-plugin-announcements/pull/197. Hoping to have it ready to publish by the end of the weekend.

Great stuff! I added changeset