rp-binary-info is not compatible with picotool for rp2350

With the latest version (2.0.0) of picotool, picotool info works with rp2040 binaries but not with rp2350.
$ picotool version
picotool v2.0.0 (Linux, GNU-11.4.0, Release)

Steps to reproduce
$ git clone https://github.com/rp-rs/rp-hal.git
$ cd rp2040-hal-examples
$ cargo build --bin binary_info_demo
$ picotool info -a -t elf target/thumbv6m-none-eabi/debug/binary_info_demo
File target/thumbv6m-none-eabi/debug/binary_info_demo:

Program Information
 name:          rp2040-hal Binary Info Example
 version:       0.1.0
 web site:      https://github.com/rp-rs/rp-hal
 description:   A GPIO blinky with extra metadata.
 binary start:  0x10000000

Fixed Pin Information
 none

Build Information
 pico_board:        pico
 build attributes:  debug

So it works with RP2040.
But doing the same RP2350 provides no info:
$ cd rp235x-hal-examples
$ cargo build --bin binary_info_demo
$ picotool info -a -t elf target/thumbv8m.main-none-eabihf/debug/binary_info_demo
File target/thumbv8m.main-none-eabihf/debug/binary_info_demo:

Program Information
 none

Fixed Pin Information
 none

Build Information
 none

Can you attach your two elf files, or can you run llvm-objdump -t | rustfilt | sort on them?

Sure.

The .boot_info input section is missing from the RP2350 example linker script. It should be packed into the .start_block output section.

Indeed, it now works as expected:
$ cargo build --bin binary_info_demo
$ picotool info -a -t elf target/thumbv8m.main-none-eabihf/debug/binary_info_demo
File target/thumbv8m.main-none-eabihf/debug/binary_info_demo:

Program Information
 name:          binary_info_demo
 version:       0.1.0
 web site:      https://github.com/rp-rs/rp-hal
 description:   A GPIO blinky with extra metadata.
 binary start:  0x10000000
 target chip:   RP2350
 image type:    ARM Secure

Fixed Pin Information
 none

Build Information
 pico_board:        pico2
 build attributes:  debug


tegra-uefi-capsules-36.3.0/bup-payload/signed/flash.idx is not found when building SWUpdate image

Hello,
I am attempting to build the scarthgap branch for L4T 36.3.0, and followed the README to enable SWUpdate on an AGX Orin devkit.
I have run into this error when building swupdate-image-tegra for the tegra-demo-distro:
The index file /yocto/tegra-demo-distro/build/tmp/work/jetson_agx_orin_devkit-oe4t-linux/tegra-uefi-capsules/36.3.0/tegra-uefi-capsules-36.3.0/bup-payload/signed/flash.idx is not found.
WARNING: /yocto/tegra-demo-distro/build/tmp/work/jetson_agx_orin_devkit-oe4t-linux/tegra-uefi-capsules/36.3.0/temp/run.do_compile.1332239:255 exit 1 from './doflash.sh'
WARNING: Backtrace (BB generated script):
	#1: tegraflash_custom_sign_bup, /yocto/tegra-demo-distro/build/tmp/work/jetson_agx_orin_devkit-oe4t-linux/tegra-uefi-capsules/36.3.0/temp/run.do_compile.1332239, line 255
	#2: do_compile, /yocto/tegra-demo-distro/build/tmp/work/jetson_agx_orin_devkit-oe4t-linux/tegra-uefi-capsules/36.3.0/temp/run.do_compile.1332239, line 161
	#3: main, /yocto/tegra-demo-distro/build/tmp/work/jetson_agx_orin_devkit-oe4t-linux/tegra-uefi-capsules/36.3.0/temp/run.do_compile.1332239, line 427

Full error log:
tegra-uefi-capsules.log.do_compile.txt
Any recommendations?
Thanks.

This looks like a bug in the tegra-uefi-capsules recipe - missing some dependencies.  I'm going to transfer this over to the meta-tegra repo, since that's where the problem is.


Why is there a version 8.0.0 in npm registry?

I've found this by accident. I was trying to install the latests embark version so I can test solidity 5.8 contracts, to no success (Help?). And I found this version lurking around.
$ npm show embark@* version
<EMAIL_ADDRESS>'8.0.0'  # this here
<EMAIL_ADDRESS>'1.2.0'
<EMAIL_ADDRESS>'2.0.0'
<EMAIL_ADDRESS>'2.0.1'
<EMAIL_ADDRESS>'2.1.0'
<EMAIL_ADDRESS>'2.1.1'
<EMAIL_ADDRESS>'2.1.2'
<EMAIL_ADDRESS>'2.1.3'
<EMAIL_ADDRESS>'2.1.4'
...

I got curious and I installed it to see what it was. It seems to be an empty package. Here is the package.json file.
$ npm i<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>updated 1 package and audited 2 packages in 0.808s
found 0 vulnerabilities

$ cat node_modules/embark/package.json
{
  "_from"<EMAIL_ADDRESS>  "_id"<EMAIL_ADDRESS>  "_inBundle": false,
  "_integrity": "sha1-wEB8no6xNTP7RDIfVEKjujPI7vE=",
  "_location": "/embark",
  "_phantomChildren": {},
  "_requested": {
    "type": "version",
    "registry": true,
    "raw"<EMAIL_ADDRESS>    "name": "embark",
    "escapedName": "embark",
    "rawSpec": "8.0.0",
    "saveSpec": null,
    "fetchSpec": "8.0.0"
  },
  "_requiredBy": [
    "#USER",
    "/"
  ],
  "_resolved": "https://registry.npmjs.org/embark/-/embark-8.0.0.tgz",
  "_shasum": "c0407c9e8eb13533fb44321f5442a3ba33c8eef1",
  "_spec"<EMAIL_ADDRESS>  "_where": "/home/meyer/Projects/notary",
  "author": "",
  "bundleDependencies": false,
  "deprecated": false,
  "description": "",
  "license": "ISC",
  "main": "index.js",
  "name": "embark",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "version": "8.0.0"
}

I would guess that it is a typo someone made at some time. ¯_(ツ)_/¯

The embark package name was is use by someone else before @iurimatias was able to have it changed to his control for the purposes of the Embark Framework. At that time, there was a version 8.0.0 that had already been published and the npm registry maintainers felt it wasn't too important to remove it. However, this is the 2nd time this week that it has caused some confusion so it's probably a good time to go back to the registry maintainers and ask them to remove it.

I have deprecated version 8.0.0, which will hopefully help to prevent confusion, and maybe that version can be removed altogether at some point.


Fix edge quoting (broken in 3.0.0)

I missed a crucial call to quote_id_if_necessary() in the to_string() path for pydot.Edge, so it's broken in 3.0.0 and leaves some values unquoted that need to be quoted.
This PR adds a fix and a test. I'd suggest an immediate bugfix release of 3.0.1.
Fixes #383

(Somehow NONE of our massive test suite exercised that code path, which is pretty amazing. I think it's because most of the tests use the pydot parser to create the test data, and when dot_parser reads a quoted value in a graph, it'll include the quotes in the name. So, none of the tests that work from .dot files actually test the automatic quoting logic, as that can only be triggered using the Python API.)
That probably means we should write a bunch more tests that don't rely on the parser to create the test data.

I think a similar fix to this is needed for issue https://github.com/pydot/pydot/issues/418

@dulinriley Oh, no, this was a fix for my quoting rewrite in #363, where I just left out a quoting call.
The bad quoting logic that led to #418 happened even earlier — way back in #320, in fact, when I let a fix for attribute quoting spill over into the ID quoting and (unknowingly) broke it.
(In #363 I ended up splitting the attribute and ID quoting logic entirely, since they turned out to have more differences than similarities... but the damage was already done.)


[BUG] Incorrect error on H:MM:SS time format

Describe the bug
Error code 16 seems to be a false positive, as it is citing a rule that conflicts with the GTFS reference.
To Reproduce
I ran the validator on the attached GTFS file: Feed_Trapeze.zip
Expected behavior
I do not expect to see an error for this behavior because the GTFS reference document explicitly allows it. ("Time in the HH:MM:SS format (H:MM:SS is also accepted)."
Witnessed behavior
Notice{filename='stop_times.txt', level='ERROR', code='16', title='Invalid time', description='Invalid time: 9:38:00 in field:departure_time for entity with id:null', extra='{fieldName=departure_time, timeValue= 9:38:00}'},
Environment used

OS: macOS Catalina 10.15.6
Java version: 11.0.5
gtfs-validator version: v1.2.2

After analysis, it appears a space character is in front of the incriminated Strings.

Space   is not a valid character for a time in the HH:MM:SS format
Note that a 0 (zero) would be valid in that context
See: https://docs.oracle.com/cd/E41183_01/DR/Time_Formats.html

Example: 02:18:23


[Feature] Add New Clash Rule Provider Format

Feature Request
Description
Add a clash rule provider with domain behavior and text format.
Motivation
Domain behavior is more efficient for large numbers of rules and new text format have better matching performance and less memory usage.
Example
rule-providers:
  iran:
    type: http
    behavior: domain
    format: 'text'
    url: ""
    path: ./ruleset/iran.txt
    interval: 432000

Current  clash_rules.yaml would look like this with domain behavior and in text format:
clash_rules.txt
Suggested Solution
classical's DOMAIN-SUFFIX equivalent is +. wildcard in domain  .
Additional Information
With domain behavior , GEOIP rule should be added separately.
Additional Request
It would be great if another clash_rules file without .ir domains would be added, it would reduce file size and improve matching speed, and all .ir domains could be bypassed separately with DOMAIN-SUFFIX,ir .

I don't have spare time to work on this in the near future, but everyone feel free to open a PR.

payload:

DOMAIN-SUFFIX,

پشت هر دامین در لیست شما باید این گونه باشد (استاندارد کلش اصلی و متا)

اینی که فرستادید فرمت  yaml ، همین مرجعی که فرستادید را چک کنید دقیقا قسمت پایینش  فرمت text هست:
# comment
.blogger.com
*.*.microsoft.com
books.itunes.apple.com


Retrieve out of cache doesn't work

The retrieval out of the cache gives the following error:
/usr/local/lib/node_modules/alfred-evernote-workflow/search_content/htmlCacheLog.json:1
SyntaxError: /usr/local/lib/node_modules/alfred-evernote-workflow/search_content/htmlCacheLog.json: Unexpected number in JSON at position 46
    at parse (<anonymous>)
    at Generator.next (<anonymous>)
-
alfred-evernote-workflow 0.7.9
Alfred 4.1
darwin 19.6.0

Your environment

OS: macOS 10.15.6
Packages:
Env: Node 14.9.0; npm 6.14.8

Steps to reproduce

Save Cache
Wait for save completion
Use any search (i.e. ent)
Results lead to the error mentioned above

Expected behaviour
List of notes
Actual behaviour
Error message

Thanks for reporting a bug.
Could you send me the htmlCacheLog.json file?
I think I need to look into your htmlCacheLog.json to grasp what has happened.
-----Original Message-----
From: "Tamio<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Sent: 2020-09-01 (화) 21:30:42 (GMT+09:00)
Subject: [jopemachine/alfred-evernote-workflow] Retrieve out of cache doesn't work (#56)
The retrieval out of the cache gives the following error:
/usr/local/lib/node_modules/alfred-evernote-workflow/search_content/htmlCacheLog.json:1 SyntaxError: /usr/local/lib/node_modules/alfred-evernote-workflow/search_content/htmlCacheLog.json: Unexpected number in JSON at position 46 at parse () at Generator.next () - alfred-evernote-workflow 0.7.9 Alfred 4.1 darwin 19.6.0
Your environment
OS: macOS 10.15.6
Packages:
Env: Node 14.9.0; npm 6.14.8
Steps to reproduce
Save Cache
Wait for save completion
Use any search (i.e. ent)
Results lead to the error mentioned above
Expected behaviour
List of notes
Actual behaviour
Error message
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Could you check if this issue occurs in 0.8.0?
I've changed the way that the json file is saved in the Applescript.

Could you check if this issue still occurs in 0.8.0?
I've changed the way that the json file is saved in the Applescript.

You fixed it! Great! Thanks! 👍


Can not connect

Hello!
I can see "raspotify (raspberry pi)" under "Devices Available" but doesn´t connect, using Android.
Thanks for your help

Is it only on Android? I had the same issue when I made a mistake in the OPTIONS line in etc/default/raspotify
If you uncomment OPTIONS and don't delete / fill in username & pw then it has problems connecting (at least for me).

Thank you for your answer, I´ll follow your advice, and let  you know.
Regards

Where do I need to fill in the login data instead of putting them into the OPTIONS? Is there a workaround?


Search SDK: Factoring out base class for AnalyzerName and DataType

Also changing the way that such ExtensibleEnums are serialized. Now it is possible to use [JsonConverter(typeof(ExtensibleEnumConverter))] on the model type itself, which will allow us to use such types in generated code. This will be important for custom analyzers, which will introduce several new extensible enum types: TokenizerName, TokenFilterName, CharFilterName, and RegexFlags. It is also important for indexer support, since it has at least one extensible num type: DataSourceType.
FYI @chaosrealm @seansaleh @Yahnoosh @mhko

🎯 lgmt


Not an issue

Hi
I know I nay be stretching my luck, but maybe refresh the Themes distributed by ArkOS.
Seems to me they are "ancient" and most have fine tuning problems.
es-theme-saga-box + es-theme-sagamodern + es-theme-simply-basic + es-theme-freeplay report the game count in French (main screen) -=> Probable because ES is not in English on my system.
es-theme-saganx + es-theme-nes-box on a 1:1 screen truncates the name of all the systems system (ex: "Station" or "Sega - ...")
es-theme-switch on a 1:1 screen overlaps the systems on the main screen.
There are many nice themes nowadays fine tuned for 16:9, 4:3 and 1:1, es-theme-art-book-next-arkos is one of the possible choices.
I also like the simplicity of es-theme-replica (set to yellow) but that's a personal choice.
To test what I'm talking about, try Emulation Station in Portuguese for ex on the RGB30.

I may switch some of the other themes but not the default one which is nes-box for all devices except for the RGB30.  For the RGB30. the default is sagabox.  By default, sagabox is set to RGB30 in the theme configuration.  If it's not set to that, then you'll get oddities.  The other theme like es-theme-switch just needs to be set to 1:1 in the theme configuration and it should fix the overlap.  Any other suggested themes, I can take a look at.  I don't plan to include the es-theme-art-book-next one as pretty much every other ES based distro makes use of that theme or similar and I want to differentiate ArkOS somewhat from though it is a ES frontend.

Suggestion:
https://github.com/Vidnez/MinUArk

Another detail, why are ArkOS boot logos so different between rb353m and the rgb30?
I understand the resolutions are different, but the logo could be the same.
If you want to "want to differentiate ArkOS somewhat", a consistent boot image helps.
Keep up the good work.

I prefer to differentiate the boot logos because I find it fun to do so.  One of the benefits of this OS is if someone doesn't like the boot logo, it can be easily changed using the logo generator for rk3566 devices or by changing a jpg file for rk3326 devices.


SIGSEGV in decompiler unit test

Describe the bug
0x0000555555649170 in std::vector<TypeOp*, std::allocator<TypeOp*> >::operator[] (this=0x2a0, __n=25) at /usr/include/c++/11.1.0/bits/stl_vector.h:1046
1046		return *(this->_M_impl._M_start + __n);
(gdb) bt
#0  0x0000555555649170 in std::vector<TypeOp*, std::allocator<TypeOp*> >::operator[] (this=0x2a0, __n=25)
    at /usr/include/c++/11.1.0/bits/stl_vector.h:1046
#1  0x000055555595ac67 in CircleRangeTest::pullbackUnary (this=0x7fffffffe510, opcode=CPUI_INT_NEGATE, insize=1)
    at ../unittests/testcirclerange.cc:222
#2  0x0000555555959fd2 in CircleRangeTest::testPullbackUnary (start=240, stop=16, step=1, bytes=1,
    opcode=CPUI_INT_NEGATE, insize=1) at ../unittests/testcirclerange.cc:87
#3  0x000055555595c395 in circlerange_pullbacknegate2 () at ../unittests/testcirclerange.cc:383
#4  0x000055555595859c in UnitTest::run (testNames=std::set with 0 elements) at test.cc:37
#5  0x0000555555958ec5 in main (argc=0, argv=0x7fffffffe7f0) at test.cc:131

To Reproduce
Steps to reproduce the behavior:

.make test && ./ghidra_test_dbg

Environment (please complete the following information):

OS: arch linux
Java Version: 11.0.13
Ghidra Version:  10.2-DEV
Ghidra Origin: local

Additional context
bisect to 25801da834416d05de616b250afc55bf5ab9674e but no changes in Decompiler/
(@caheckman fyi)

I get this error if x86-64.sla is missing or otherwise out of sync with the branch.  ghidra_test_dbg doesn't rebuild processor languages it uses.  Can you try rebuilding explicitly with something like  gradle x86:sleighCompile and then rerunning ghidra_test_dbg ?

Thanks @caheckman   ... it was throwing me off why it bisected to the x86/ changes ... and completely blanked on making sure the .sla was good

@caheckman   I was running scan-build make test and it picked up a few things that looked pretty interesting, here are few to show what kinds of things it shows, it produces a report with branches to hit each.  Definitely a lot of false positives, but shows 90 potential issues.
UAF
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/architecture.cc#L767
NULL ptr deref in all the following LowLevelError
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/translate.cc#L367
Do these only matter if something was expecting a LowleverError, or badness either way?
Less obvious ones that I'm not too sure if the code flow scan-build suggests could happen or even matter (some are simple fixes either way):
is this a tmpvn memleak?
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/pcodecompile.cc#L353
thinks this can be accessed with un-initialized data
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/context.hh#L130
thinks this can be accessed with un-initialized data
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/address.hh#L301
thinks this can be accessed with un-initialized data
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/address.hh#L250
https://github.com/NationalSecurityAgency/ghidra/blob/f5994d3f2fde4bb4742df7acfe087c79383f2c70/Ghidra/Features/Decompiler/src/decompile/cpp/address.hh#L319
thinks this can be accessed with un-initialized data
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/grammar.hh#L62
thinks this can be accessed as NULL ptr
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/address.hh#L308
wants a neq zero check on num looks like
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/op.cc#L1114
thinks this can be accessed as NULL ptr
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/double.cc#L330
thinks this can get called with NULL op
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/printc.cc#L1535
thinks op2.value_real can be accessed with un-initialized data
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/semantics.hh#L51
things res.targethit can be unitilaized
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/codedata.cc#L476
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/codedata.cc#L478
things secinfo.address can be unitilaized
https://github.com/NationalSecurityAgency/ghidra/blob/3eb03b1608b24aaae1cd1d5c86a5df36270ac54d/Ghidra/Features/Decompiler/src/decompile/cpp/codedata.cc#L688


Wdio-runner: Make event names consistent with wdio-reporter

Proposed changes
Fix events name.
See https://github.com/webdriverio/v5/blob/master/packages/wdio-reporter/src/index.js#L37
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Reviewers: @webdriverio/technical-committee

Codecov Report

Merging #106 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   95.48%   95.48%
=======================================
  Files          94       94
  Lines        1862     1862
  Branches      398      398
=======================================
  Hits         1778     1778
  Misses         75       75
  Partials        9        9

Impacted Files
Coverage Δ

packages/wdio-runner/src/index.js
32.89% <ø> (ø)
:arrow_up:

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 3443038...023010f. Read the comment docs.


Cannot verify SSL certificates behind proxy

Running 0.7.4-rc0 behind a company proxy with the company's ca cert fails when aca-py tries to access the JSON-LD context schemas from an external https source.
I start aca-py with this docker-compose.yaml:
version: "3.7"
services:
  aca-py:
    container_name: alice-agent
    image: bcgovimages/aries-cloudagent:py36-1.16-1_0.7.4-rc0
    entrypoint: /bin/bash
    user: "root:root"
    command:
      [
        "-c",
        "sleep 10; update-ca-certificates; sleep 2; aca-py start --inbound-transport http <IP_ADDRESS> $ACAPY_DID_PORT --outbound-transport http --admin <IP_ADDRESS> $ACAPY_ADMIN_PORT --endpoint $ACAPY_DID_PUBLIC_URL $LEDGER_GENESIS --ledger-pool-name $LEDGER_POOL_NAME --label $ACAPY_LABEL $ACAPY_ADMIN_API_ACCESS --wallet-type indy --wallet-name ${WALLET_NAME} --wallet-key '${WALLET_ENCRYPTION_KEY}' ${ACAPY_FLAGS} --log-level $ACAPY_LOG_LEVEL $ACAPY_WEBHOOK $ACAPY_SEED $ACAPY_DEBUG_OPTION $ACAPY_DEBUG "
      ]
    environment:
      - HTTP_PROXY=http://xxxx:3128
      - HTTPS_PROXY=http://xxxx:3128
      - NO_PROXY=xxxx,<IP_ADDRESS>
      - http_proxy=http://xxxx:3128
      - https_proxy=http://xxxx:3128
      - no_proxy=xxxx,<IP_ADDRESS>
    ports:
      - "${ACAPY_DID_ADDR}:${ACAPY_DID_PORT}:${ACAPY_DID_PORT}"
      - "${ACAPY_DID_ADDR}:${ACAPY_ADMIN_PORT}:${ACAPY_ADMIN_PORT}"
    volumes:
      - ../genesis-files:/genesis-files:ro
      - ${PWD}/certs/ca_server_chain.crt:/usr/local/share/ca-certificates/ca_server_chain.crt:ro
    networks:
      - von-network

networks:
  von-network:
    name: von-network

With this container running, I can exec into it and execute a curl https://www.w3.org/2018/credentials/v1 successfully. However, when I'm trying to issue a json-ld credential with that schema I get the following error:
2022-05-13 10:24:57,739 urllib3.connectionpool DEBUG Starting new HTTPS connection (1): [www.w3.org:443](http://www.w3.org:443/)
2022-05-13 10:24:58,285 aries_cloudagent.core.dispatcher ERROR Handler error: credential_exchange_send Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 700, in urlopen
    self._prepare_proxy(conn)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 994, in _prepare_proxy
    conn.connect()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connection.py", line 424, in connect
    tls_in_tls=tls_in_tls,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket
    sock, context, tls_in_tls, server_hostname=server_hostname
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 817, in __init__
    self.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 1077, in do_handshake
    self._sslobj.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 786, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 145, in _fetch_context
    requestProfile='http://www.w3.org/ns/json-ld#context')
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 6583, in load_document
    remote_doc = options['documentLoader'](url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 110, in __call__
    return self.load_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 105, in load_document
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 432, in result

=================
    return self.__get_result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 94, in _load_sync
    return loop.run_until_complete(self._load_async(url, options))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 488, in run_until_complete
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 74, in _load_async
    document = self._load_http_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 54, in _load_http_document
    document = self.requests_loader(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 103, in loader
    cause=cause)
pyld.jsonld.JsonLdError: ('Could not retrieve a JSON-LD document from the URL.',)
Type: jsonld.LoadDocumentError
Code: loading document failed
Cause: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')
pyld.jsonld.JsonLdError: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/routes.py", line 667, in credential_exchange_send
    auto_remove=auto_remove,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 84, in prepare_send
    comment="create automated v2.0 credential exchange record",
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 230, in create_offer
    cred_proposal_message
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/formats/ld_proof/handler.py", line 406, in create_offer
    detail.credential.serialize(), document_loader
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/check.py", line 140, in get_properties_without_context
    {"documentLoader": document_loader},
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 142, in compact
    return JsonLdProcessor().compact(input_, ctx, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 721, in compact
    'jsonld.CompactError', cause=cause)
pyld.jsonld.JsonLdError: ('Could not expand input before compaction.',)
Type: jsonld.CompactError
Cause: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')

2022-05-13 10:24:58,287 aries_cloudagent.admin.server ERROR Handler error with exception: ('Could not expand input before compaction.',)
Type: jsonld.CompactError
Cause: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 700, in urlopen
    self._prepare_proxy(conn)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 994, in _prepare_proxy
    conn.connect()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connection.py", line 424, in connect
    tls_in_tls=tls_in_tls,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket
    sock, context, tls_in_tls, server_hostname=server_hostname
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 817, in __init__
    self.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 1077, in do_handshake
    self._sslobj.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 786, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 145, in _fetch_context
    requestProfile='http://www.w3.org/ns/json-ld#context')
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 6583, in load_document
    remote_doc = options['documentLoader'](url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 110, in __call__
    return self.load_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 105, in load_document
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 94, in _load_sync
    return loop.run_until_complete(self._load_async(url, options))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 488, in run_until_complete
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 74, in _load_async
    document = self._load_http_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 54, in _load_http_document
    document = self.requests_loader(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 103, in loader
    cause=cause)
pyld.jsonld.JsonLdError: ('Could not retrieve a JSON-LD document from the URL.',)
Type: jsonld.LoadDocumentError
Code: loading document failed
Cause: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')
pyld.jsonld.JsonLdError: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 159, in ready_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 196, in debug_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp_apispec/middlewares.py", line 45, in validation_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 293, in check_token
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 383, in setup_context
    return await task
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/routes.py", line 667, in credential_exchange_send
    auto_remove=auto_remove,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 84, in prepare_send
    comment="create automated v2.0 credential exchange record",
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 230, in create_offer
    cred_proposal_message
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/formats/ld_proof/handler.py", line 406, in create_offer
    detail.credential.serialize(), document_loader
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/check.py", line 140, in get_properties_without_context
    {"documentLoader": document_loader},
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 142, in compact
    return JsonLdProcessor().compact(input_, ctx, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 721, in compact
    'jsonld.CompactError', cause=cause)
pyld.jsonld.JsonLdError: ('Could not expand input before compaction.',)
Type: jsonld.CompactError
Cause: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')

2022-05-13 10:24:58,288 aiohttp.server ERROR Error handling request Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 700, in urlopen
    self._prepare_proxy(conn)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 994, in _prepare_proxy
    conn.connect()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connection.py", line 424, in connect
    tls_in_tls=tls_in_tls,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket
    sock, context, tls_in_tls, server_hostname=server_hostname
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 817, in __init__
    self.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 1077, in do_handshake
    self._sslobj.do_handshake()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/connectionpool.py", line 786, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 145, in _fetch_context
    requestProfile='http://www.w3.org/ns/json-ld#context')
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 6583, in load_document
    remote_doc = options['documentLoader'](url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 110, in __call__
    return self.load_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 105, in load_document
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 94, in _load_sync
    return loop.run_until_complete(self._load_async(url, options))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 488, in run_until_complete
    return future.result()
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 74, in _load_async
    document = self._load_http_document(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/document_loader.py", line 54, in _load_http_document
    document = self.requests_loader(url, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 103, in loader
    cause=cause)
pyld.jsonld.JsonLdError: ('Could not retrieve a JSON-LD document from the URL.',)
Type: jsonld.LoadDocumentError
Code: loading document failed
Cause: HTTPSConnectionPool(host='www.w3.org', port=443): Max retries exceeded with url: /2018/credentials/v1 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/documentloader/requests.py", line 63, in loader
    response = requests.get(url, headers=headers, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')
pyld.jsonld.JsonLdError: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 159, in ready_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 196, in debug_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp_apispec/middlewares.py", line 45, in validation_middleware
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 293, in check_token
    return await handler(request)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/admin/server.py", line 383, in setup_context
    return await task
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/routes.py", line 667, in credential_exchange_send
    auto_remove=auto_remove,
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 84, in prepare_send
    comment="create automated v2.0 credential exchange record",
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/manager.py", line 230, in create_offer
    cred_proposal_message
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/protocols/issue_credential/v2_0/formats/ld_proof/handler.py", line 406, in create_offer
    detail.credential.serialize(), document_loader
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/check.py", line 140, in get_properties_without_context
    {"documentLoader": document_loader},
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 142, in compact
    return JsonLdProcessor().compact(input_, ctx, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 721, in compact
    'jsonld.CompactError', cause=cause)
pyld.jsonld.JsonLdError: ('Could not expand input before compaction.',)
Type: jsonld.CompactError
Cause: ('Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.',)
Type: jsonld.InvalidUrl
Code: loading remote context failed
Details: {'url': 'https://www.w3.org/2018/credentials/v1', 'cause': JsonLdError('Could not retrieve a JSON-LD document from the URL.',)}  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 717, in compact
    expanded = self.expand(input_, options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 871, in expand
    inside_list=False)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 2303, in _expand
    active_ctx, element['@context'], options)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/jsonld.py", line 3049, in _process_context
    resolved = options['contextResolver'].resolve(active_ctx, local_ctx, options.get('base', ''))
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 59, in resolve
    active_ctx, ctx, base, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 108, in _resolve_remote_context
    context, remote_doc = self._fetch_context(active_ctx, url, cycles)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pyld/context_resolver.py", line 157, in _fetch_context
    code='loading remote context failed')

Any idea what's going on here? When curl is able to verify the certificate then aca-py should also, shouldn't it?

Got it to work by setting an ENV var: REQUESTS_CA_BUNDLE=/usr/local/share/ca-certificates/ca_server_chain.crt.


Integration pipeline is missing e2e test static type checks

A refactor of the SingleAddressWallet was able to be merged to master with an e2e test not being updated:
https://github.com/input-output-hk/cardano-js-sdk/blob/a177656af239eb665d59b84e3f9fcd8c27fd670f/packages/wallet/src/SingleAddressWallet.ts#L52-L56
https://github.com/input-output-hk/cardano-js-sdk/blob/a177656af239eb665d59b84e3f9fcd8c27fd670f/packages/wallet/test/e2e/SingleAddressWallet/nft.test.ts#L11-L34
At a minimum all test code needs to be built during CI, but ideally a pre-commit check would catch it earliest.

This was addressed some time back.
https://github.com/input-output-hk/cardano-js-sdk/blob/450f0a67bf3e0b867681869e22f3b2c85a475754/.github/workflows/continuous-integration-unit-tests.yaml#L33
https://github.com/input-output-hk/cardano-js-sdk/blob/450f0a67bf3e0b867681869e22f3b2c85a475754/package.json#L35


Password reset table on tenant database

It's possible to force the password reset entries to be saved on the tenant connection. In order to do so update the auth.php file and add the connection key like this:
    'passwords' => [
        'users' => [
            'provider' => 'users',
            'table' => 'password_resets',
            'expire' => 60,
            'connection' => 'tenant',
        ],
    ],

Connection is also something we can configure on the session, if using driver database.

Moved to docs repo.

Hi. What if we want to change password of user in system connection?


Local

Project
Name of the project
Changes
What was updated (new pages, weekly update, etc.)
Notes
If there are any further notes.

@alpit4 please resolve the conflicts and put the images inside the assets folder


There is no eraser option [FEAT]

eraser option is not available,if wanted to delete whole board is being deleted,not able to delete a particular one

Hi @Rohitha-pudu 👋🏻
There's already an existing issue regarding adding Eraser feature, #36
So I'm closing this issue, you can create a new issue (check existing ones before creating yours).


⚠ Bofrost.lu has degraded performance

In 0168819, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2705 ms

Resolved: Bofrost.lu performance has improved in 276184f after 33 minutes.


Using specialized schema subclasses

Resolves #1164
Motivation:
PrimitiveType contains a full mapping (and constructors!) for built-in tracked schema subtypes. By using this, the Schemas generated by the 2to3 converter will have a similar shape to the native 3.x schemas, permitting more unified structure handling for clients (permitting relying on isInstanceOf exclusively, instead of isInstanceOf as well as getType() == "xyz")
Delegating to fromTypeAndFormat to get a particular instance, then createProperty() to instantiate the particular schema resolves the issue I was running into.
If we can't actually look up the mapping, fall back to the original behaviour.

I force pushed because I found a fallback case where the base type is recognized by PrimitiveType, but the format was not. I handled this by calling with null as the format, then setFormat on the resulting schema (if it exists) otherwise continuing down the chain to new Schema() with the previous behaviour.


Web console autocompaction E2E test

Description
Add an E2E test for the common case web console workflow of setting up autocompaction that changes the partitions from dynamic to hashed.
Also fix an issue with the async test setup to properly wait for the web console to be ready.

This PR has:

[x] been self-reviewed.
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added integration tests.

Having a look into this one.. excited to run these new test locally!

Having a look into this one.. excited to run these new test locally!

Cool. If you need them, some notes for running the web console E2E tests locally: https://github.com/apache/druid/blob/master/web-console/README.md#running-end-to-end-tests

The _download_zookeeper step in script/druid is no longer needed right?

The _download_zookeeper step in script/druid is no longer needed right?
(not for this PR, just asking for reference)

Ah, yeah. I implemented this from memory of the old docs, which were updated by https://github.com/apache/druid/pull/8792 to skip the ZK download step.


ConnectionError: Couldn't reach https://huggingface.co/datasets/tatsu-lab/alpaca/resolve/main/dataset_infos.json (ConnectTimeout(MaxRetryError("HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /datasets/tatsu-lab/alpaca/resolve/main/dataset_infos.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fc4ec0d2560>, 'Connection to huggingface.co timed out. (connect timeout=100)'))")))

this is not an issue with this repo, it's an issue with your node not having access to the internet


document batch operations

Summary
Test Plan

Please consider the impact of your changes on the other developers.

#10  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Silver-Sword and the rest of your teammates on  Graphite


SQL filetype needs multipart/block support

The SQL filetype should have the same multipart delimiters as the PLSQL filetype.  That is:
   \ 'sql': { 'left': '-- ', 'leftAlt': '/*', 'rightAlt': '*/' },

Great! Would you be willing to put this into a PR?

Done.


Restore files from WSL 2 after formatting the PC

I think I can imagine the answer but I really need to ask. Is it possible to recover files that were in wsl 2 after I formatted my PC? I forgot they were there and I really need them.
Thank you!

Sorry, formatting your drive erases all contents, including WSL distros.


Adding ISEPBG

Adding ISEPBG Institute.

@km20 The first verification stage is complete: the official domain for  Institut Supérieur des Etudes Préparatoires en Biologie et Geologie La Soukra is www.isepbgsoukra.agrinet.tn, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: http://www.isepbgsoukra.agrinet.tn/images/pdfs/balag21.pdf

@philipto Thank you for your reply. The « Institut Supérieur des Etudes Préparatoires en Biologie et Geologie La Soukra » is part of Carthage University https://ucar.rnu.tn/institut-superieur-des-etudes-preparatoires-en-biologie-geologie/. The official mail addresses provided by the university of Carthage are @*.ucar.tn (where * is replaced by the institute acronym).

@km20 The first verification stage is complete: the official domain for  Institut Supérieur des Etudes Préparatoires en Biologie et Geologie La Soukra is www.isepbgsoukra.agrinet.tn, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: http://www.isepbgsoukra.agrinet.tn/images/pdfs/balag21.pdf


[SourceKit] Retrieve swiftsourcedocinfo for code completion request

Extracted from https://github.com/apple/swift/pull/62574 to test its performance impact individually.

We need swiftsourcedocinfo for cursor info and to be able to reuse the ASTContext from code completion for cursor info, we need to also retrieve the sourcedocinfo for code completion requests.

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

The stress tester did not find any significant performance regressions from always loading swiftsourcedocinfo.

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test


Installer

We need one. I choose NSIS.

Configurator and Installer became the same thing, for configure see #8 .

I disagree. #8 doesn’t solve this since the GUI still needs to be installed. Distributing a .zip is not a good experience.

Self-extracting zip, better?

And also 99% of times, people get thcrap bundled with a Touhou game.

Those people only use that thcrap for that Touhou game and no other.

Options
Windows

Self-extracting zip (this is a .exe file)
An MSIX mindless click-click-click installer
Our own .exe installer

Furthermore:
Any .exe, .msi, or .msix app could go to Windows Package Manager (winget) that adheres to these policies.
If we package as msix with this it will become and uwp app, then we could distribute to Windows Store, if we adhere to these policies.
MacOS
Somebody who uses MacOS please fill us in, but I have a suspecting feeling we are definitely not going to make it to MacOs's Store. But maybe the Linux methods would work here as well.
Linux
I think the best idea is to create .AppImage, since that basically runs everywhere, and then either provide an auto-updater for it somehow, or also maintain a Flatpack for Debian-based, and on the AUR for Arch-based. (The rest can figure it out themselves.)

Almost all of the installers on Windows except ones that install huge programs are actually self extracting archives. In fact, if you have 7-zip installed in Windows, you can just right click on the installer and it will show you to open in 7-zip. This is because for an executable in the PE file format, there is a specific last byte, after which it is all done and Windows loader will not load it into memory.
This trick was invented my Microsoft to my knowledge, there used to be a program called iexpress baked into Windows since Windows 95 and it existed in Windows 10 too. Not sure if it is in 11 though as I have switched completely to Linux. The iexpress tool allowed you to create these self extracting archives, and it used the CAB archive format. Then most common after that was WinZIP SFX and WinRAR SFX archives and later 7zip SFX. Very rarely, there are Uharc SFX too, made by WinUharc and Uharc CMD projects.
Most archive programs will try to look for the starting signature in input bytestream before throwing an error, where this is usually 2-4 dedicated bytes which will tell the file format and the format version. So all the SFX executable needs to do is to get its own file name (in C/C++ it is the 0th argument in argv array) and pass it to the archiving program. Sometimes instead of an archiving program, these link with the libraries so unarchiving code is also in the same EXE file.
Btw, the same is true with MSI installers too. MSI is just Microsoft's format which say how an installer should look like and behave. InstallShield uses multiple files though, and they are kept in different .DAT or .BIN files. InnoSetup allows both options - if SFX route, it uses LZMA compression. Else .BIN files are used as archives. NSIS, allows the package script author to decide the compression format. Most will use LZMA but other formats are available too.
However, these are for older installers or for installers for third party software. Most used softwares now go for Web Installers, which downloads the real archive in the background and install it over the network. This is also done for telemetry reasons. Installer can send over the user-agent which contains OS version and also system specifications to the server which is used to know the reach and analytics. - Youtube comment by Sri Harsha Chilakapati

MSIX Docs: https://learn.microsoft.com/en-us/windows/msix/packaging-tool/create-an-msix-overview
Alternative: https://github.com/Squirrel/Squirrel.Windows
Our Own: Alternatively, we could reuse the existing thcrap-updater, and make it into a web installer.

Even more alternatively, we could distribute via https://github.com/ScoopInstaller/Scoop


The installation of pyqt gets stuck

I use a Virtual box Ubuntu 22.04
I installed conda inside the crowddynamics folder, then I imported the second folder, where I opened the terminal, activated conda crowd36 environment to install pyqt
Here is the terminal prompt:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment:
It's getting stuck at Solving environment, could you help me please ? 🙏  I need this python simulation for my school project asap

Hello @JoujouGeek666 ,
Your problem seems to have also dependency issues as the root cause, see my recent comment in #358 . It might be that you have to use Ubuntu 16:04...


Site https://defectdojo.pythonanywhere.com/ down

Issue Template
Issue Type

[X] Bug
[ ] Enhancement

Description
Demo site on https://defectdojo.pythonanywhere.com/ is down.
If the issue is a bug, please also include the following:
Operating System
N/A
Install

[ ] setup.bash
[ ] docker

DefectDojo Version
Steps to Reproduce
Sample Scan File (if applicable)
Screenshots (optional)
Console Logs (optional)

@barbich We don't use that site anymore, where did you find the link to it? The demo site is here. Thanks

@aaronweaver link is on the defectdojo site https://www.defectdojo.org/ text in the page says "If you'd like to check out a demo of DefectDojo before installing it, you can check out our demo." with demo pointing to the wrong page.

Ah ok thx will update that one.


Jbranch

just set up some boiler plate stuff... uploaded employee model...take a look and tell me what i missed...

I think it looks good go ahead and merge it the only thing I'm not sure if we wanted to add was employee email not sure if we are collecting theirs too or only the account holders but great work


Explorer tree flicker opening fresh folder

I think I had reported this before already but now I hit this more frequently because I tend to open a logs folder from CI by dropping on the dock:

I find the explorer flicker unpleasant and I think we can do better.

This only happens when you open the folder for the very fist time

This was caused by the fix here - https://github.com/microsoft/vscode/issues/91367 - Fixed it differently so that both these issues are covered.
CC @sbatten


Update scala-collection-compat to 2.7.0

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

Files still referring to the old version number
The following files still refer to the old version number (2.2.0).
You might want to review and update them manually.
project/Dependencies.scala

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

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1

Superseded by #307.


Error parsing langchain example notebook 'langgraph_rag_agent_llama3_local.ipynb': SyntaxError

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
Any help on correcting this would be appreciated!
Error opening the notebook https://github.com/langchain-ai/langgraph/blob/main/examples/rag/langgraph_rag_agent_llama3_local.ipynb.  Opened on different Jupyter NB and lab, online JSON verifier and online Jupyter notebook (CoCalc).
Error on my ubuntu 24.04 installation:
Unreadable Notebook: /mnt/c/Users/wdonn/NLP1/langchain/rag/langgraph_rag_agent_llama3_local (2).ipynb NotJSONError("Notebook does not appear to be JSON: '\n\n\n\n\n\n\n<html\n l...")
CoCalc error:
Error parsing the ipynb file 'langgraph_rag_agent_llama3_local (2).ipynb': SyntaxError: Unexpected token < in JSON at position 6.  You must fix the ipynb file somehow before continuing.
Best wishes,
Bill
Error Message and Stack Trace (if applicable)
Unreadable Notebook: /mnt/c/Users/wdonn/NLP1/langchain/rag/langgraph_rag_agent_llama3_local (2).ipynb NotJSONError("Notebook does not appear to be JSON: '\n\n\n\n\n\n\n<html\n l...")
CoCalc error:
Error parsing the ipynb file 'langgraph_rag_agent_llama3_local (2).ipynb': SyntaxError: Unexpected token < in JSON at position 6.  You must fix the ipynb file somehow before continuing.
Description
Error in current version of file in github:
https://github.com/langchain-ai/langgraph/blob/main/examples/rag/langgraph_rag_agent_llama3_local.ipynb
System Info
Not relevant: file does not even open

OK,  apologies, kept downloading from fresh browser and it works fine.

OK, apologies, kept downloading from fresh browser and it works fine.


[STORM-2693] Heartbeats and assignments promotion for storm2.0

For large cluster support, good scheduling performance for scheduling and assignments distribution.
This is PR for 1.1.x-branch of heartbeats promotion
https://github.com/apache/storm/pull/2389
This is PR for 1.1.x-branch of assignments promotion
https://github.com/apache/storm/pull/2319

@HeartSaVioR hi, i have make PR for storm2.0, please help me to review this


This is a quick fix to attempt to resolve most of the travis failures

Most of the failures have been due to transient network failures, that are causing dependency artifact downloads to fail
Maven does not have a way to retry this without restarting the whole build, so the mvn dependency plugin is the best bet
Unfortunately, running a dependency:resolve on the project returns yet to be compiled dependencies, and causes it to fail...
There is an option to excludeGroupIds and excludeArtifactIds in the docs for this goal, but unfortunately they don't seem to work
This drafts a dummy pom in a quick and dirty way, just to download all the deps in one go, while retrying for RETRY_COUNT times if it fails

Travis failure on 2c0d07e was due to second phase not running after i moved the script to tools/travis
xerxesImpl is downloaded on that phase
Issue is already fixed is in d2faa90

Travis is still not looking very well :( will resume soon

7 successes in a row is looking better :)
Will do a couple more minor changes to force some more runs.. will rebase at the end when it feels like travis is running stable

Are you done with this @rsafonseca ? As in; should I merge?

@DaanHoogland LGTM, altough travis has been very stable today :)
Lastest commit is also useful, since the after_failure.sh script was doing nothing at all.. this will allow some insight into failures such as these:
https://travis-ci.org/apache/cloudstack/jobs/67514846
==== Marvin Init Successful ====
=== TestName: test_01_sys_vm_start | Status : FAILED ===
=== TestName: test_02_sys_template_ready | Status : EXCEPTION ===
===final results are now copied to: /tmp//MarvinLogs/test_secondary_storage_KYYYZV===
+----------------------------+---------+
|            Test            | Result  |
+============================+=========+
| test_01_sys_vm_start       | Failure |
+----------------------------+---------+
| test_02_sys_template_ready | Success |
+----------------------------+---------+

Perfect, last travis failure was just what i was referring to in the last comment, after_failure.sh printed full marvin logs, we can properly troubleshoot that issue now :)
Will look into that later or during the weekend if no one else beats me to it hehe :)

It seems like this test sometimes fails because the SSVM takes a while to startup.. the test/integration/smoke/test_secondary_storage.py:159 asserts that "Starting" != "Running" and just exits there.
This needs to allow some time for the SSVM to start if state="Starting" instead of immediately throwing an AssertionError.
File hasn't been touched for over a year, so i guess this is a pretty old issue on travis, also explains why it's intermittent.

Mentioned issue fixed in https://github.com/apache/cloudstack/pull/493/
:D

Ever since i first saw this failure I wondered... why is this considered a success?!?
=== TestName: test_02_sys_template_ready | Status : EXCEPTION ===
+----------------------------+---------+
| test_02_sys_template_ready | Success |
+----------------------------+---------+
Fixed in the latest commit.

It seems latest fix uncovered tests that were failing but actually reporting success!

I'd say this now downloads around 99% of project dependencies before build starts
Mostly just maven-remote-resources-plugin stuff is still downloaded, plus very few others that somehow are not picked-up by the script runs... hopefully 99% will be enough to have travis never fail with download error/timeouts.. will launch some load on travis to see :)

LGTM waiting for travis to agree


[AVM Module Issue]: Unable to create role assignment at the secret level

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
(Optional) Module Version
0.7.1
(Optional) Correlation Id
No response
Description
Problem
Creating a role assignment at the secret level currently fails. The problem seems to be that the scope in the azurerm_role_assignment is referring to the azurerm_key_vault_secret resource as a whole, instead of pointing to its id.
Example:
Invoking the module with the following configuration:
module "key_vault" {
  source              = "Azure/avm-res-keyvault-vault/azurerm"
  version             = "0.7.1"
  name                = "my-key-vault"
  location            = "westeurope"
  resource_group_name = "my-rg"
  tenant_id           = "<some-tenant-id>"
  enable_telemetry    = false

  secrets       = {
    app-id-secret = {
      name         = "app_id_secret"
      content_type = "id"
      role_assignments = {
         app-id-secret-reader = {
          role_definition_id_or_name = "Key Vault Secrets User"
          principal_id               = "<principal-id>"
        }
      }
   }
}

Throws the following error:

Hi @JoaoFHS this is fixed in the latest commit bit I haven't released!
Apologies...
https://github.com/Azure/terraform-azurerm-avm-res-keyvault-vault/blob/bb6f4574b883e26c834d951e832bd62f35e9f60f/modules/secret/main.tf#L15-L15


Drop dynamic wrapper injection code generation

Part of https://github.com/knative/pkg/issues/2739
This removes the codegen logic that generates informers and clients that use the dynamic.Client underneath. These aren't being used anywhere.

/assign @pierDipi


Building image fails at ADD ServiceMonitor.exe /

When running docker build -t aspnet-site --build-arg site_root=/ .
build fails at step 4:
Step 4/8 : ADD ServiceMonitor.exe /
ADD failed: GetFileAttributesEx \?\C:\Windows\TEMP\docker-builder514299249\ServiceMonitor.exe: The system cannot find the file specified.
Windows Server 2016 Version 1607 Build 14393.447
Docker Version 17.09.0-ce-win33 (13620)
Any ideas?

ServiceMonitor.exe is now downloaded.  See https://github.com/Microsoft/aspnet-docker/pull/88.  @veaceslc - please try the latest Dockerfiles.  Closing but feel free to log a new issue if you have issues with the latest Dockerfiles.


Cannot install on Cygwin; pysass.cpp doesn't compile

Attempting to install libsass-python on Cygwin fails to run; it instead displays errors:
In file included from /usr/include/python3.4m/Python.h:8:0,
                 from pysass.cpp:2:
/usr/include/python3.4m/pyconfig.h:1440:0: warning: "__BSD_VISIBLE" redefined
 #define __BSD_VISIBLE 1
 ^
In file included from /usr/include/sys/config.h:5:0,
                 from /usr/include/_ansi.h:16,
                 from /usr/include/string.h:10,
                 from pysass.cpp:1:
/usr/include/sys/features.h:250:0: note: this is the location of the previous definition
 #define __BSD_VISIBLE  0
 ^
In file included from /usr/include/python3.4m/pyport.h:335:0,
                 from /usr/include/python3.4m/Python.h:50,
                 from pysass.cpp:2:
/usr/include/sys/time.h:104:34: error: ‘u_int’ has not been declared
 bintime_mul(struct bintime *_bt, u_int _x)
                                  ^
pysass.cpp: In function ‘Sass_Import** _call_py_importer_f(const char*, Sass_Importer_Entry, Sass_Compiler*)’:
pysass.cpp:464:55: error: ‘strdup’ was not declared in this scope
         if (source_str) source_str = strdup(source_str);
                                                       ^
pysass.cpp:465:64: error: ‘strdup’ was not declared in this scope
         if (sourcemap_str) sourcemap_str = strdup(sourcemap_str);
                                                                ^
pysass.cpp: In function ‘PyObject* PySass_compile_string(PyObject*, PyObject*)’:
pysass.cpp:530:51: error: ‘strdup’ was not declared in this scope
     context = sass_make_data_context(strdup(string));
                                                   ^
error: command 'gcc' failed with exit status 1

It appears that Cygwin's gcc doesn't define strdup from strings.h when in -std=c++0x mode. Using -std=gnu++0x this all compiles fine. Using the same version of gcc (5.4.0) on Ubunutu works fine.

https://github.com/chaosdeathfish/libsass-python/commit/1f82fce931f0e6a215b3881401a8f1b250de54ff fixes this issue

I think I can change this to not rely on strdup at all.  sass itself provides an implementation that should probably be used (since they call delete[] on the result anyway).
If I make a branch, can you try it out for me?

Sure, I'll be happy to give it a go! Fixing it properly does seem preferable to my rather hacky fix.

Can you try this branch for me? https://github.com/dahlia/libsass-python/pull/196

Unfortunately that doesn't seem to work, due to strdup use within libsass itself:
libsass/src/sass_functions.cpp: In function ‘Sass_Function* sass_make_function(const char*, Sass_Function_Fn, void*)’:
libsass/src/sass_functions.cpp:21:37: error: ‘strdup’ was not declared in this scope
     cb->signature = strdup(signature);
                                     ^
error: command 'gcc' failed with exit status 1

Strange!  I'm going to merge it either way, then we can probably ask upstream for some help here.  Worst case we'll apply your patch which seems fine to me :)

I wonder if just changing to always using -std=gnu++0x will fix this without breaking other compilers. I'll try that next!

Does this patch work? https://github.com/dahlia/libsass-python/pull/197

That builds fine - I'll test it in more detail when I have a moment!

The unit tests run fine, I'll hopefully have time to run it against some actual data later today but everything is looking good so far.

Hmm, I guess my main concern would be with osx.  I'll see if I can find someone to test on osx.

Had a friend at work try osx, seems good I'll merge this PR :D

Note that this is now part of a real release: 0.13.0

strdup() is not a part of a C or C++ standard, so technically speaking Cygwin is right.


The Get Started and Release Notes panel all open if Storage Explorer is a new installation

Storage Explorer Version: 1.31.0-dev
Build Number: 20230616.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.4 (Apple M1 Pro)
Architecture: x64
How Found: From running test cases
Regression From: Previous release (1.30.0)
Steps to Reproduce

Uninstall Storage Explorer.
Delete all Storage Explorer data from %AppData%.
Launch the install executable from the current build.
Check whether the Get Started opens and Release Notes doesn't open.

Expected Experience

The Get Started opens.
The Release Notes doesn't open.

Actual Experience

The Get Started opens.
The Release Notes opens.

Verified this issue on the build main 20230627.1. Fixed.


Release support for 1.8 on PyPI

Describe the Feature
It looks like dbt 1.8 support was merged to master but is not yet available as a release
Describe alternatives you've considered
Install from git commit
Who will this benefit?
Everyone!
Anything else?
No response

Hi @jnoynaert
I will get it out today. I wanted to include a fix for materialized view which was merged yesterday.
Thanks

dbt-oracle==1.8.0 is released on PyPI


feature(scroll-list): scroll to selection

Didn't finish the review, more is coming.

Please add a description!


Prognose counted as real

The problem
Hi, after installation, the daily Prognose is counted as real PV input. See the new, long, dark brown line. It reflects in the energy graph above as a huge 20kWh PV power usage. I expect Solcast to just add the dotted line to the diagram.
What version of Solcast Integration has the issue?
v4.1.7
What version of Home Assistant are you using?
Newest
Diagnostics information
No response
Logs debug/info/error output
No log data

Additional information
No response

https://github.com/BJReplay/ha-solcast-solar/issues/50

Did you attach an image? I see nothing here.
By my best guess this is not an integration issue, but a set up issue @ralfsteck, which is why I reference #50. Strange forecast as production issue.
It will be configuration.
If you have upgraded from a very old, likely Oziee version, which oddly did not care about this kind of misconfiguration then this could cause even though "I did nothing but upgrade".

You are absolutely right, I defined it as Prognose in the PV entry and it works.
Viele Grüße von Unterwegs
Von: Steve Saunders @.>
An: BJReplay/ha-solcast-solar @.>
Kopie: ralfsteck @.>; Mention @.**>
*Datum: *14.09.2024 14:33:04
*Betreff: *Re: [BJReplay/ha-solcast-solar] Prognose counted as real (Issue #172)

Did you attach an image? I see nothing here.
By my best guess this is not an integration issue, but a set up issue @ralfsteck[https://github.com/ralfsteck], which is why I reference #50[https://github.com/BJReplay/ha-solcast-solar/issues/50]. Strange forecast as production issue.
It will be configuration.
If you have upgraded from a very old, likely Oziee version, which oddly did not care about this kind of misconfiguration then this could cause even though "I did nothing but upgrade".
—
Reply to this email directly, view it on GitHub[https://github.com/BJReplay/ha-solcast-solar/issues/172#issuecomment-2350974425], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AEUQHM2PRX5FBWDEKHKJPE3ZWQT53AVCNFSM6AAAAABOGY3FJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHE3TINBSGU].
You are receiving this because you were mentioned.
[Verfolgungsbild][https://github.com/notifications/beacon/AEUQHMYSYRYTJRRW6Q3L7BTZWQT53A5CNFSM6AAAAABOGY3FJGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUMEEC5S.gif]

Good to hear.
Freut mich zu hören, dass es funktioniert.