toolchain-xtensa-lx106-elf won't install via pio platform install

When trying to install via "pio platform install" I get the error
Error: Could not find the package with 'toolchain-xtensa-lx106-elf @ 8.4.0+esp2020r3' requirements for your system 'windows_amd64'
I don't understand why, the platfrom.json looks correct and points to https://raw.githubusercontent.com/WallaceWilliam/xtensa-lx106-elf/master/manifest.json which contains the package that is being asked for:
        {           "system": ["windows", "windows_amd64", "windows_x86"],           "url": "https://github.com/WallaceWilliam/xtensa-lx106-elf/raw/master/xtensa-lx106-elf-win32-1.22.0-100-ge567ec7-5.2.0.tar.gz",           "version": "5.2.0+100"         }
I was able to workaround this problem by downloading xtensa-lx106-elf-win32-1.22.0-100-ge567ec7-5.2.0.tar.gz directly and placing it into $HOME.platformio\packages. But I would like to understand what is going wrong. Also thank you for all your work on this project.

As described in PlatformIO 5.0 migration guide:
PlatformIO Core 5.0 does not support unofficial package repositories declared through
packageRepositories in platform.json that was introduced in PlatformIO 3.0.
Please publish your development platforms and toolchains to the PlatformIO Trusted
Registry using pio package CLI.

Hi @bglee , how did you make it for you?
I'm in macOS and have downloaded https://github.com/WallaceWilliam/xtensa-lx106-elf/raw/master/xtensa-lx106-elf-macos-1.22.0-100-ge567ec7-5.2.0.tar.gz, then unzipped twice as<EMAIL_ADDRESS>and toolchain-xtensa-lx106-elf in /Users/snakeninny/.platformio/packages:

But I still got this error:
snakeninny@bogon packages % pio platform install custom8266

WARNING: This command is deprecated and will be removed in the next releases.
Please use `pio pkg install` instead.

Platform Manager<EMAIL_ADDRESS>is already installed
Tool Manager: Installing toolchain-xtensa-lx106-elf @ 5.2.0+100
Error: Could not find the package with 'toolchain-xtensa-lx106-elf @ 5.2.0+100' requirements for your system 'darwin_arm64'

Any ideas? Thank you!


Help me with db Traccar-Server

Hi, I am new in this and I need help with any problems with upgrade installation of traccar server. my problem is that icon of my device no show ,  and the log say the problem
 WARN: Column count does not match; SQL statement:
INSERT INTO positions (device_id, protocol, serverTime, time, valid, latitude, longitude, altitude, speed, course, address)
    VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?); [21002-194] - JdbcSQLException (... < QueryBuilder:58 < *:135 < DataManager:293 < DefaultDataHandler:27 < ...)

I dont create db and dont know how.
please can you help me. note: sorry for english idiom but I speak and write only spanish,

Traccar creates database schema automatically. I guess you did something wrong, but without any information on what you did, there is no way to tell what the problem is.

Are you sure you are using official version without modifications? It seems like you at least modified config file.

I try upgrade the version modified with google maps traccar GUI

What version?

http://traccar.litvak.su/installation.html
I have you version 3.11 and try upgrade to 3.8 of traccar.litvak.su

That's not an official Traccar project, so you should ask on the project issue tracker, not here. Also, I don't think you can easily migrate between two.


CI fails at mdbook job

Describe the Bug
With https://github.com/ElektraInitiative/PermaplanT/issues/1306 now fixed, CI fails at the mdbook job when updating the crates-io registry.
Here are some examples:
PR https://github.com/ElektraInitiative/PermaplanT/pull/1303 Pipeline
PR https://github.com/ElektraInitiative/PermaplanT/pull/1297 Pipeline
PR https://github.com/ElektraInitiative/PermaplanT/pull/1298 Pipeline
Error message
#14 [builder 7/7] RUN cargo install --git https://github.com/ElektraInitiative/mdbook-generate-summary mdbook-generate-summary --locked
#14 0.286     Updating git repository `[https://github.com/ElektraInitiative/mdbook-generate-summary`](https://github.com/ElektraInitiative/mdbook-generate-summary%60)
#14 0.899   Installing mdbook-generate-summary v0.1.1 (https://github.com/ElektraInitiative/mdbook-generate-summary#39d7f777)
#14 0.912     Updating crates.io index
#14 42.56 error: Unable to update registry `crates-io`
#14 42.56
#14 42.56 Caused by:
#14 42.56   failed to fetch `[https://github.com/rust-lang/crates.io-index`](https://github.com/rust-lang/crates.io-index%60)
#14 42.56
#14 42.56 Caused by:
#14 42.56   network failure seems to have happened
#14 42.56   if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
#14 42.56   https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli
#14 42.56
#14 42.56 Caused by:
#14 42.56   SSL error: unknown error; class=Ssl (16)
#14 ERROR: process "/bin/sh -c cargo install --git https://github.com/ElektraInitiative/mdbook-generate-summary mdbook-generate-summary --locked" did not complete successfully: exit code: 101

Steps to Reproduce the Problem
Run CI
Expected Result
CI either passes or fails on newly introduced or changed code
Actual Result
CI fails to complete mdbook job
PermaplanT version
see linked PRs
Operating System
Windows
Browser
Chrome
Versions of other relevant software/extensions
No response
Additional info/logs
No response

Thx for this beautiful issue! :heart:
We already had this issue before, unfortunately nothing showed up when the admin investigated the network.
Does restarting help?
Does it always fail on the same agent?
Can someone reproduce it locally?

@markus2330
I tried to fix it by increasing the retry count on network issues and it seems to help: PR 1332
Not sure if that's enough for the time being or @filo14 should take another look

But logs of the mdbook jobs don't seem to be preserved if successful?

Let us reopen if it fails again. Otherwise I think this solution is fine. Network problems are hard to debug.


Upload multiple files

I want to ask how can I upload multiple files?

If I'm not mistaken the MatFileUpload will only allow you to upload one image at a time.
But you can store the result in an array so the user uploads them one by one.

@ALMLAMBO @enkodellc ,
This should have been released. Can we please close this out now?


Witcher 2 doesn't start

Just tested latest d9vk master with The Witcher 2 in Wine, and strangely it fails to start with such errors:
info:  Required Vulkan extension VK_KHR_get_physical_device_properties2 not supported
info:  Required Vulkan extension VK_KHR_surface not supported
info:  Required Vulkan extension VK_KHR_win32_surface not supported
terminate called after throwing an instance of 'dxvk::DxvkError'

That's with Mesa 19.2.0 rc3, so I think those extensions should be supported. I have these installed: libvulkan1:i386, mesa-vulkan-drivers:i386.

You need an x32 vulkan loader.

I have it installed as I said: libvulkan1:i386. Something else is off.

Yeah I deleted that comment already 🐸
This isn't a D9VK bug, but rather a setup issue.
I'm not too familiar with using Vulkan on Debian/Ubuntu so I'm not sure. Definately not on my end though.

Can you install vulkanutils:i386 and see if 32-bit vkcube or vulkaninfo work?

I just tested running TW1 with d9vk which is also 32-bit. It started fine, so 32-bit Vulkan in general is OK. But something got messed up with TW2 somehow.

Are you doing this in the same prefix?

No, separate prefixes.

For a test, I can try copying one to another, and see what's going to happen

This is already interesting. I made a copy of TW1 prefix for a test, and also copied TW2 game directory in it. From that prefix, TW1 starts OK with d9vk. TW2 fails like before with same errors.

It's not x64 is it? 🐸

Nope, it shouldn't be.

Are you using winelib builds btw?

Right, can you try using a normal mingw build?
https://git.froggi.es/joshua/d9vk/-/jobs
Just to rule that out.

Let me try with 64-bit one, and then I'll try mingw build.

With 64-bit prefix + winelib build, same errors as before. Trying now 64-bit prefix + mingw build.

Same error with 64-bit + mingw build. Game is quite unlikely 64-bit though.  I'm going to try now 32-bit + mingw.

Oh, I think I know what's going on. Let me check something.

Yep, that was my misconfig. In the startup script it tried to use non existing Mesa. I managed to start it now, though it hangs on the loading screen (not the whole computer, just the game gets stuck). But that would be a separate bug if anything. Closing.


PO BOX labeled individually when tagging

PO and BOX were labeled separately as individual tokens as USPSBoxType
It comes from 'PO BOX 4900 DEPT 505 SCOTTSDALE AZ 85261-4900'
this raised an error message in the .tag method.

that's probably not the source of the error in the tag method - 'PO' & 'BOX' should be individual tokens after parsing, & the tag method concatenates consecutive tokens w/ the same label. can you drop in the output of the parse method & the error you get w/ the tag method?

Traceback (most recent call last):
File "C:/Users/yebordag/PycharmProjects/tester3/Tester3.py", line 37, in
addresstag2(testSet1)
File "C:/Users/yebordag/PycharmProjects/tester3/Tester3.py", line 29, in addresstag2
print usaddress.tag(x)
File "C:\Python27\lib\site-packages\usaddress_init_.py", line 190, in tag
raise RepeatedLabelError(address_string, parse(address_string), label)
usaddress.RepeatedLabelError:
ERROR: Unable to tag this string because more than one area of the string has the same label
ORIGINAL STRING:  PO BOX 4900 DEPT 505 SCOTTSDALE AZ 85261-4900
PARSED TOKENS:    [(u'PO', 'USPSBoxType'), (u'BOX', 'USPSBoxType'), (u'4900', 'USPSBoxID'), (u'DEPT', 'USPSBoxType'), (u'505', 'USPSBoxID'), (u'SCOTTSDALE', 'PlaceName'), (u'AZ', 'StateName'), (u'85261-4900', 'ZipCode')]
UNCERTAIN LABEL:  USPSBoxType
When this error is raised, it's likely that either (1) the string is not a valid person/corporation name or (2) some tokens were labeled incorrectly
To report an error in labeling a valid name, open an issue at https://github.com/datamade/usaddress/issues/new - it'll help us continue to improve probablepeople!
For more information, see the documentation at http://usaddress.readthedocs.org/
Process finished with exit code 1
(The entire error message)
I think I understand the error now, the parser thinks DEPT is a postbox type when it means department and that 505 is the post box number instead of the dept number.
Thanks

We have a bunch of incoming training data using departments, so this should be resolved by the next release.


Change tracker stopped during continuous replication error thrown when cookie expires

I am using cookie authentication in an ionic app using couchbase lite phonegap plugin. Replication runs fine while active_tasks shows this:
[
  {
    "progress": 100,
    "continuous": true,
    "source": "todos",
    "status": "Idle",
    "task": "repl007",
    "change_count": 1,
    "target": "http://.../todos",
    "completed_change_count": 1,
    "type": "Replication"
  },
  {
    "progress": 0,
    "continuous": true,
    "source": "http:/.../todos",
    "status": "Idle",
    "task": "repl008",
    "change_count": 0,
    "target": "todos",
    "completed_change_count": 0,
    "type": "Replication"
  }
]

Then I get another cookie through curl, so the cookie on the mobile side expires. No error is thrown while polling but the active_tasks shows this:
[
  {
    "progress": 100,
    "continuous": true,
    "source": "todos",
    "status": "Idle",
    "task": "repl007",
    "change_count": 1,
    "target": "http://...todos",
    "completed_change_count": 1,
    "type": "Replication"
  },
  {
    "progress": 0,
    "continuous": true,
    **"error": [
      400,
      "java.lang.Exception: Change tracker stopped during continuous replication"
    ],**
    "source": "http://.../todos",
    "status": "Idle",
    "task": "repl008",
    "target": "todos",
    "type": "Replication"
  }
]

The call to _changes  never returns an error and always returns 200.
I am trying to handle cookie expiration using the rest api.

@swaheed2,

The call to _changes never returns an error and always returns 200.

/_changes REST API returns changes in the database. It does not return any status of the replicator.

Note to Self:

Replicator stops by cookie expiration, so /_active_tasks should return "status": "stopped".

@swaheed2,
_active_tasks REST API returns only Active replicators. It means the stopped (inactive) replicators are not in the response results. To detect replicator's error status, please call /_active_tasks with feed parameter with lonpoll or continuous.


Can't generate more than 11 images

Hi, I found this issue but that didn't help me. I guess it has been updated since then, but anyway, I'm trying to generate more than 11 images, beneath 11 is fine, but when I go above I get the following:
Quick note: I have edited the name of each image so it ends with #1 #2 #3 etc. (i.e Rare Orange Eyes #1.png) - do I have to do anything else, in the code for example?
start creating NFTs.
-----------------
creating NFT 1 of 50
- rarity: undefined
D:\NFT\Generative OpenSource\generative-art-opensource-main\index.js:133
    let num = Math.floor(Math.random() * layer.elementIdsForRarity[_rarity].length);
                                                                            ^

TypeError: Cannot read properties of undefined (reading 'length')
    at D:\NFT\Generative OpenSource\generative-art-opensource-main\index.js:133:77
    at Array.forEach (<anonymous>)
    at createDna (D:\NFT\Generative OpenSource\generative-art-opensource-main\index.js:132:11)
    at startCreating (D:\NFT\Generative OpenSource\generative-art-opensource-main\index.js:200:18)
    at Object.<anonymous> (D:\NFT\Generative OpenSource\generative-art-opensource-main\index.js:249:1)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)

Thanks!

Same problems here , any solution ?

make sure to change the original number to match the editionSize num
const editionSize = 100
// ...
let rarityWeights = [
  addRarity('super_rare', 1, 1),
  addRarity('rare', 2, 5),
  addRarity('original', 5, 100)
];


Add memory bounded algorithms

https://laconicml.com/simplified-memory-bounded-a-star/
https://en.wikipedia.org/wiki/SMA*#Implementation


select multiple not working with object as ng:options

When using an Object as source for ng:options in a <select multiple> tag, it's not possible to select more than one element.
Test at http://jsfiddle.net/marcenuc/7eJjm/

Vojta please fix this.

I've tested commit fa4aa702409cd59fb14c4c15619885ae7c7bb81c and it works for me.


Gnomad fixes

Fixes for field names in gnomad and clinvar

Hi Brad,
This PR fixes all problems mentioned in the linked issue. If there's no further objection there, feel free to merge.
Cheers
M

Matthias -- thanks so much for debugging and fixing all the issues here. Much appreciated.


Utilize formatted message from AzureEventSourceListener in LogEvent

closes #44028
@lmolkova - If this fix makes sense, there are other files where we should make this fix.

I think the desire in the original code is to defer formatting the message until/unless it's absolutely needed. In particular, you want to avoid (expensive) formatting if the log level would otherwise filter the event entirely.
I would propose an alternative where we add a second (overloaded) constructor to AzureEventSourceListener that takes a simpler Action<EventWrittenArgs>. Callers that don't need the formatted message can use that constructor.
See this: https://github.com/pharring/azure-sdk-for-net/compare/dev/pharring/EventSourceEventFormattingPerf...pharring:azure-sdk-for-net:dev/pharring/AddAzureEventSourceListenerConstructorOverload?expand=1

Yes, you are missing something. In this PR, message formatting (likely a string allocation) still happens unconditionally inside AzureEventSourceListener in order to evaluate the arguments to call the LogEvent callback, passing the fully-evaluated formattedMessage to LogEvent. If the log level is set high/low enough that the event will be filtered, then the fully formatted message is never used -- meaning it was a wasted allocation.

Does the EventSource not avoid the eager formatting when it calls IsEnabled before calling WriteEvent?

Does the EventSource not avoid the eager formatting when it calls IsEnabled before calling WriteEvent?

Yes, it does. However, this listener subscribes to events at "Verbose" level (meaning everything) and the AzureEventSourceListener uses calls EnableEvents without passing a keyword mask -- also meaning "all events".


docs: add link to demos in README

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: determine the appropriate default configuration

We need to determine the appropriate default configuration for the raft cluster.

I want to take this issue.

thanks!

#185


Issue with replacing the logo image

Bug Description
I am attempting to replace the logo image with a custom image but the dev server does not seem to reflect these changes.
I followed the instructions provided in the wiki:
https://github.com/slatedocs/slate/wiki/Changing-the-Logo-and-adding-Images
Even though my folder no longer contains the original slate image, I'm still seeing this image
Browser (please complete the following information):

OS: Ubuntu 20.04
Browser: Chrome
Version: 88

Please also note that I'm using the slatedocs/slate docker image (Image Id: d7e22a13d4ed)
Many thanks for the help!

I believe this issue is related to caching performed by middleman. I was able to resolve by deleting the image on the dev site and re-serving the docs.


Is this remote webdriver supported?

I know that Selenium stealth does not support remote webdriver. BUT, is <IP_ADDRESS> really "remote"? Is there any hope of making this work:
driver = webdriver.Remote(
   command_executor='http://<IP_ADDRESS>:4444/wd/hub',
   options=webdriver.ChromeOptions()
)

stealth(driver,
        languages=["en-US", "en"],
        vendor="Google Inc.",
        platform="Win32",
        webgl_vendor="Intel Inc.",
        renderer="Intel Iris OpenGL Engine",
        fix_hairline=True,
        )

Currently I get the same error, whether the Selenium Grid was local "<IP_ADDRESS>" or otherwise:
root@dc3cb4f8e581:/home/pi/tl# python3 tl-both
Traceback (most recent call last):
  File "tl-both", line 36, in <module>
    stealth(driver,
  File "/usr/local/lib/python3.8/dist-packages/selenium_stealth/__init__.py", line 41, in stealth
    raise ValueError("driver must is selenium.webdriver.Chrome, currently this lib only support Chrome")
ValueError: driver must is selenium.webdriver.Chrome, currently this lib only support Chrome

My goal is to see what's happening on screen sometimes. If you have any other suggestions to do that please do. Thank you.

I created a fork of this package and it's now supported https://github.com/markmelnic/stealthenium

Was literally just looking for this @markmelnic

@cdekort Literally released 18 mins ago, give it a star )


Ramme Doesn't Close properly (Ubuntu/Linux)

I've installed Ramme (ver 3.2.3) on my Ubuntu 16.10.
The application doesn't close properly when I close the window (or even if I close using the menu option Window > Close option). I noticed this when I closed the window while a video with sound was playing. Although the window disappeared, the sound kept looping in background. I had to then kill the 'ramme' process from System Monitor to stop the sound and close the application.
I hope you will also release the fix for the layout and shortcut issues.
thanks for the wonderful app

39fdb07f5fd72e5798eec0205c01173654266386 and 89bc86807623460049c1faf7c6a653066640fd6e
Will be in next release. Closing issue for now.


When using disposable, typescript should never report the variable as unused

🔍 Search Terms
"using", "dispose", "asyncDispose", "is declared but its value is never read"
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
TypeScript reports variables declared via using as unused if they aren't used explicitly, but I would argue that they are used implicitly and shouldn't be reported as unused in any case.
📃 Motivating Example
TypeScript Playground link
💻 Use Cases

What do you want to use this for?
What shortcomings exist with current approaches?
What workarounds are you using in the meantime?

Sometimes I just want the using for creating a mutex lock, and I don't need to interact with the variable in any way.
Workaround is to prefix the variable with _

I would argue that it should be reported as unused. I believe in the majority of cases you actually want to use the resource for something, and not only treat it as an automatic scope. For those cases prefixing with an underscore is a good workaround.
Instead a proposal should be made to TC39 to support using declarations that don't bind any variable.

I agree; I think it looks wrong enough that the _ prefix, if it was really intended to be unused by explicit code, is really valuable.

https://github.com/tc39/proposal-discard-binding
I guess I have to wait for this.


feat: Making contact generation optional based on shape types

This change is

Review status: 0 of 15 files reviewed at latest revision, 1 unresolved discussion.

src/collide/narrow.rs, line 22 at r1 (raw file):
Previously, torkleyy (Thomas Schaller) wrote…
Maybe let Y default to () so you don't have to specify it.

Done.

Comments from Reviewable

Review status: 0 of 15 files reviewed at latest revision, 2 unresolved discussions.

src/collide/narrow.rs, line 22 at r2 (raw file):
Previously, Xaeroxe (Jacob Kiesel) wrote…
Add Y to documentation please

Done.

Comments from Reviewable


DNM Upmerge 171120

In progress
pending: re-apply the reverted downstream commits.

Some checks failed. Please fix and resubmit.
Nits issues
Please remove blank lines at end of 'boot/cypress/platforms/retarget_io_pdl/cy_retarget_io_pdl.h'

Please remove blank lines at start of 'boot/zephyr/include/arm_cleanup.h'

Gitlint issues
Commit 6610e880d8:
1: UC2 Signed-off-by: must have a full name
Commit 907476d701:
4: UC4 Line exceeds max length (74>72): "might cause linking collision as this header belongs to FIH_ENABLE_DELAY"
6: UC4 Line exceeds max length (73>72): "This header is already included by "bootutil/fault_injection_hardening.h""
Commit fce873364e:
5: UC4 Line exceeds max length (73>72): "fault injection like clock or power glitching, EM pulse, laser beam, etc."
Commit 1dcc73b0b8:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Add ifdefs in crypto abstract function for ec256 to enable compilation when mbedtls used as backend"
1: UC5 Title exceeds max length (99>72): "Add ifdefs in crypto abstract function for ec256 to enable compilation when mbedtls used as backend"
1: UC6 Body has no content, should at least have 1 line.
Commit 8ebe53537b:
5: UC4 Line exceeds max length (74>72): "when running through recommonmark==0.6.0 because it is unable to parse the"
Commit 6ea44be64f:
1: UC5 Title exceeds max length (78>72): "cypress: update user documentation with disclaimer and additional instructions"
3: UC4 Line exceeds max length (127>72): "This change adds Disclaimer section to Cypress related documentation and adds details about custom hardware configuration flow."
Commit ff026122e1:
3: UC4 Line exceeds max length (244>72): "Entering deep sleep on CM0 without valid application on CM4 caused pyocd error while programming. This fix disables entering deep sleep mode on CM0 if no valid applications found for boot. Waiting for uart complete tx reworked. Code refactoring"
Commit 8097d86b2f:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Compile with MBEDTLS_CIPHER_MODE_CTR set."
1: UC6 Body has no content, should at least have 1 line.
Commit 4f4833d465:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Abstracting mcuboot crypto functions for cleaner porting and less of an ifdef hell."
1: UC5 Title exceeds max length (83>72): "Abstracting mcuboot crypto functions for cleaner porting and less of an ifdef hell."
10: UC4 Line exceeds max length (81>72): "- No need to free contexts because Zephyr sets MBEDTLS_PLATFORM_NO_STD_FUNCTIONS."
Commit f62ea0c464:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "bootutil should not import assert.h"
Commit 453231ca12:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Remove unused headers."
1: UC6 Body has no content, should at least have 1 line.
Commit 30feaf648d:
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "hal_flash is unused, remove the import."
Commit 8672c8e98a:
1: UC2 Signed-off-by: must have a full name
Commit 42b32394d6:
3: UC4 Line exceeds max length (86>72): "Fix imgtool does not take into account value of confirm flag, when signing .hex images"
Commit fdff3e1ea0:
4: UC4 Line exceeds max length (73>72): "of Zephyr are confused. It might be might be understood as one-pair image"
Commit 9ed399cd6d:
1: UC5 Title exceeds max length (93>72): "zephyr: Turn off cache for Cortex M7 before chain-loading. The new image will fail otherwise."
1: UC6 Body has no content, should at least have 1 line.
pylint issues
************* Module imgtool.image
scripts/imgtool/image.py:222:55: C0303: Trailing whitespace (trailing-whitespace)
scripts/imgtool/image.py:253:4: R0201: Method could be a function (no-self-use)
scripts/imgtool/image.py:491:4: R0201: Method could be a function (no-self-use)

Identity/Emails issues
6dfba7fd0736f0e6bf92e921e498108b3caa653e: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
a022053a4173084880bc48bdd4bbcf9607274ead: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
a08d7f5d00f3f1a0231938569e6e7cfaedc88858: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
7adcc8e1103eb2ef1102bdc43cc91b0e87fdd0b8: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
d3c55689113c3688f6d3d655bb7091a86ebe69d6: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
49a9acbab9cb713dd6e239b8d84c7b1423b2edf2: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
ee7909cc72bcc475e4d0f378c12049378d766d4d: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
5bafddc597203ba3368777db52b1ffaf6d6d65b9: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
905d64c9749c9a2071d1fe4d7276ec3f616c2166: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
bc1a7347531106b2a20b832394e749830576aad2: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
cfe3a1f501cd5d14f7e680ee76d8010ee09de7f7: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
8ef73b07e7bde81101449a69786416da023cbd9b: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
c5617751123c426bfc315e4c70f644c699288979: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
aeae31691f588c3951aca332bc8811dee30c5899: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
b0b2797347a47e3819cd0fe0997a2af63d3d2601: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
e02d22a4ab8ade69c4a77d3a2739c9ab6e496ee3: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
d133ca23423b86e668c9f640afa1d0b1598ecf27: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
d4f41ec02a11e4098e0a6eddb8e06aec5b5d6a45: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
51163770a42616c4c707917b9fedf8c7cd130274: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
0cb278157ed9573611b3ceae20e0b0574607fc0d: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
c6afb6e3b8767baece3f1438a5b0a9f7e1362382: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
552b8680cec7e651c3da8b0c42eb8ea5a4dc801e: author email (Ioannis Glaropoulos<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
6610e880d825630c43dda57ab22f693a938fd525: author email (TTornblom<EMAIL_ADDRESS>does not follow the syntax: First Last .
8672c8e98a173415e838b91bab967b8e5619975a: author email (dmiv<EMAIL_ADDRESS>does not follow the syntax: First Last .
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

Comments:
FYI @mbolivar-nordic  @hakonfam @sigvartmh @nvlsianpu @carlescufi

64617d8 was pushed, so we are able to also revert 80eb854, which was not caught by ncs-compare, although a relevant patch was merged upstream.
026a4e5, 75fd8f2, 01dd7b3, ac05701, 22373ec are standard git-reverts, so the corresponding reverted commits must be reapplied as is.
06d7123 is a manual revert I did, to be able to achieve a conflict-free upmerge. Without it, I would have to revert, again, the commit by Sebastian B, that introduces PM (along with several other dependencies); this way we minimize the effort in next up-merges. However, the reverts done in  06d7123  must be re-applied.

If that's what it takes, that's what has to be done.

@mbolivar-nordic I am not sure I fully-agree; I think we "could" try to be a bit smarter here. The optimization problem is
minimize the number of reverted commits
subject to: linear history, conflict-free merges, etc.

If we are able to push a "noup" commit that makes us revert less stuff in the next upmerge, we could exploit in case-by-case basis. But I don't have a super strong opinion. I also see the value of a standardized procedure.
So I followed the recommendation and reverted all commits that conflict (along with their dependencies).

@hakonfam , @nvlsianpu all patches starting from ac05235 need to be re-applied, unless you think they are not needed any more. In that case please, add a comment for each one that is left behind.

I mean, ac05235,  4c5ff85, a8cc987 and onwards.

https://github.com/nrfconnect/sdk-mcuboot/pull/130/commits/9f3d9db74473f94a38e62e43e8253ab25a006d2a should be left behind.
https://github.com/nrfconnect/sdk-mcuboot/pull/130/commits/f48de7a5237886a994984528b1cb1fb595620e1b removes need for it.

9f3d9db should be left behind.
f48de7a removes need for it.
same 3ab66d8 - , can be removed, all flash drivers supports unaligned reads since a while.

This should be fixed now.

We can just skip the conflicting patch during the cherry-pick and we get a zero-diff rebase, which I have posted here:
https://github.com/mbolivar-nordic/sdk-mcuboot/tree/upmerge-130-rebase
This has an empty diff with the current tip of this PR, 4b41ab6.
I think we could make an exception and allow this PR to be merged if we make it very clear in the commit log for the conflicting patch that it is a 'temphack' which should be skipped when rebasing. That won't cause difficulties when it is time to rebase for the next NCS release.


Calendar ToString/FromStr chain yields different object

If I have the following code, just creating a calendar, stringifying it, and then parsing the result, the resulting Calendar object ends up being different than the one we started with:
  #[test]
  fn emit_parse_icalendar() {
    let mut calendar = Calendar::new();
    calendar.append_property(Property::new("FOOBAR", "foobaz"));

    let emitted = dbg!(calendar.to_string());
    let parsed = dbg!(Calendar::from_str(&emitted).unwrap());

    assert_eq!(parsed, calendar)
  }

---- emit_parse_icalendar stdout ----
 calendar.to_string() = "BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:ICALENDAR-RS\r\nCALSCALE:GREGORIAN\r\nFOOBAR:foobaz\r\nEND:VCALENDAR\r\n"
 Calendar::from_str(&emitted).unwrap() = Calendar {
    properties: [],
    components: [],
}
thread 'emit_parse_icalendar' panicked at 'assertion failed: `(left == right)`
  left: `Calendar { properties: [], components: [] }`,
 right: `Calendar { properties: [Property { key: "FOOBAR", val: "foobaz", params: {} }], components: [] }`'
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Basically, all properties are missing. Is that expected?

oh boy. seems there is a use-case I hadn't tested. Might only be a missing loop in the serialization code. Do you wanna take a look?

oh boy. seems there is a use-case I hadn't tested. Might only be a missing loop in the serialization code. Do you wanna take a look?

As per my understanding (didn't look too closely), it's about this logic in the read_calendar function that I can't make sense of:
pub fn read_calendar(input: &str) -> Result<Calendar<'_>, String> {
    components(input)
        .finish()
        .map(|(_, mut components)| {
            let root_is_calendar = components
                .get(0)
                .map(|first_root| first_root.name == "VCALENDAR")
                .unwrap_or(false);

            if root_is_calendar {
                let root = components.swap_remove(0);
                Calendar {
                    properties: root.properties,
                    components: root.components,
                }
            } else {
                Calendar {
                    components,
                    properties: Vec::new(),
                }
            }
        })
        .map_err(|e: VerboseError<&str>| format!("error: {}", convert_error(input, e.clone())))
}

What is so special about this root calendar? I suspected it has something to do with what the underlying standard says (which I am utterly unfamiliar with), but it does not make much sense to me at this point.

I had also tried adding a component to the calendar, but then wanted to check with you first when that didn't change anything. The focus on components seems...odd to me, though I could understand if the standard said that a calendar without components is meaningless/invalid (I'd still question whether it's that crate's job to correct that, and certainly whether that should happen silently on the load path [as opposed to verbosefully when saving]).

The issue was not in that function, that one only looks complicated because I'm trying to handle the case that I get a Calendar without the root "tag".
The actual issue was that during parsing I assumed that calendars would not have properties, because the properties at calendar-level are usually only stuff like VERSION and so on.
In #62 I'm keeping all the properties when creating a Calendar from parsed input. This however led into a bit of a rabbit-hole, since suddenly I was adding these basic properties twice (once from the parsed calendar and once during serialization). So I had to refactor and (softly) break the API contract a little bit and now I add these during instantiation of the Calendar.

The issue was not in that function, that one only looks complicated because I'm trying to handle the case that I get a Calendar without the root "tag". The actual issue was that during parsing I assumed that calendars would not have properties, because the properties at calendar-level are usually only stuff like VERSION and so on.
In #62 I'm keeping all the properties when creating a Calendar from parsed input. This however led into a bit of a rabbit-hole, since suddenly I was adding these basic properties twice (once from the parsed calendar and once during serialization). So I had to refactor and (softly) break the API contract a little bit and now I add these during instantiation of the Calendar.

Very cool; thanks for looking into a fix. Will have tested it out some more by tomorrow the latest.

No hurry, it’s Xmas time anyway


[SPARK-25963] Optimize generate followed by window

What changes were proposed in this pull request?
I've added an optimizer rule to add Repartition operator when we have a Generate operator followed by a Window function
How was this patch tested?
I've added a plan unittest

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@uzadude where is this relevant? You will end up with two shuffles if you do this.

The whole idea is that we'll get one shuffle and it will be before the explode as the window's partition is contained in the repartition.
I'll show the physical plan.

this is the original query. we can see the explode followed by the shuffle:
import org.apache.spark.sql.functions._
import org.apache.spark.sql.expressions._

val N = 1 << 12

spark.sql("set spark.sql.autoBroadcastJoinThreshold=0")

val tokens = spark.range(0, N, 1, 2).selectExpr(
  "floor(id/4) as key", "'asd/asd/asd/asd/asd/asd' as url")
  .selectExpr("*", "explode(split(url, '/')) as token")

val w = Window.partitionBy("key", "token")
val res = tokens.withColumn("cnt", count("token").over(w))

res.explain(true)

== Optimized Logical Plan ==
Window [count(token#11) windowspecdefinition(key#6L, token#11, specifiedwindowframe(RowFrame, unboundedpreceding$(), unboundedfollowing$())) AS cnt#17L], [key#6L, token#11]
+- Generate explode([asd,asd,asd,asd,asd,asd]), false, [token#11]
   +- Project [FLOOR((cast(id#4L as double) / 4.0)) AS key#6L, asd/asd/asd/asd/asd/asd AS url#7]
      +- Range (0, 4096, step=1, splits=Some(2))

== Physical Plan ==
Window [count(token#11) windowspecdefinition(key#6L, token#11, specifiedwindowframe(RowFrame, unboundedpreceding$(), unboundedfollowing$())) AS cnt#17L], [key#6L, token#11]
+- *(2) Sort [key#6L ASC NULLS FIRST, token#11 ASC NULLS FIRST], false, 0
   +- Exchange hashpartitioning(key#6L, token#11, 1)
      +- Generate explode([asd,asd,asd,asd,asd,asd]), [key#6L, url#7], false, [token#11]
         +- *(1) Project [FLOOR((cast(id#4L as double) / 4.0)) AS key#6L, asd/asd/asd/asd/asd/asd AS url#7]
            +- *(1) Range (0, 4096, step=1, splits=2)

and if we add the repartition before the generate:
val tokens = spark.range(0, N, 1, 2).selectExpr(
  "floor(id/4) as key", "'asd/asd/asd/asd/asd/asd' as url")
  .repartition(col("key"))
  .selectExpr("*", "explode(split(url, '/')) as token")

val w = Window.partitionBy("key", "token")
val res = tokens.withColumn("cnt", count("token").over(w))

res.explain(true)

== Optimized Logical Plan ==
Window [count(token#11) windowspecdefinition(key#6L, token#11, specifiedwindowframe(RowFrame, unboundedpreceding$(), unboundedfollowing$())) AS cnt#17L], [key#6L, token#11]
+- Generate explode([asd,asd,asd,asd,asd,asd]), false, [token#11]
   +- RepartitionByExpression [key#6L], 1
      +- Project [FLOOR((cast(id#4L as double) / 4.0)) AS key#6L, asd/asd/asd/asd/asd/asd AS url#7]
         +- Range (0, 4096, step=1, splits=Some(2))

== Physical Plan ==
Window [count(token#11) windowspecdefinition(key#6L, token#11, specifiedwindowframe(RowFrame, unboundedpreceding$(), unboundedfollowing$())) AS cnt#17L], [key#6L, token#11]
+- *(2) Sort [key#6L ASC NULLS FIRST, token#11 ASC NULLS FIRST], false, 0
   +- Generate explode([asd,asd,asd,asd,asd,asd]), [key#6L, url#7], false, [token#11]
      +- Exchange hashpartitioning(key#6L, 1)
         +- *(1) Project [FLOOR((cast(id#4L as double) / 4.0)) AS key#6L, asd/asd/asd/asd/asd/asd AS url#7]
            +- *(1) Range (0, 4096, step=1, splits=2)

we get the same result just with the explode after the shuffle, and only one shuffle

Can one of the admins verify this patch?


Functions don't properly work with other window because of failing RegExp check

Hello, I have been using the library in a pretty complex setup to build a library that will be distributed and I have started to try it out in our system and found a problem that prevents the usage of the library altogether.
When the library is compiled through a webpack, somewhere in the code, the following will occur (which I think is in no-case, the reduction):
          return r instanceof RegExp
            ? e.replace(r, t)
            : r.reduce(function (e, r) {
                return e.replace(r, t)
              }, e)

I have tracked the issue to the specific line - this code will work normally as a primary dependency, but if this built library is then used in other contexts, for example, running through a Node VM as an executable or used in different spawned window, it will fail. The reason for it is:
console.log(r instanceof RegExp) // false
console.log(r.constructor.name) // "RegExp"

Basically, what is happening is explained here:
https://medium.com/@samjwright/why-is-instanceof-my-object-returning-false-in-typescript-fec74df5c2a8
The fix is very simple, check for RegExp instance in another way.
Happy to open PR that fixes this should you be interested. I am of course aware that this is a highly exotic scenario, but it does fail this way (not everyone runs the code through NodeVM), so I think it should be fixed anyway.
Thank you very much!

Thanks for the flag! I've actually been working on a small rewrite this week of the library that would coincidentally fix this issue. I just pushed my work so far up to GitHub, but I'm going to wait for a chunk of time to release/deprecate everything according to the updates. So I should have a fix for you available either tonight or tomorrow.

This has been fixed with<EMAIL_ADDRESS>Please update and let me know if you still see any issues.


chore(starknet_integration_tests): in mempool_p2p_flow_test check alive instead of timeout

Stack:

#2723 ⬅
#2719

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


The link to the sample program seems to be broken

The following url is not found.
https://github.com/Microsoft/azure-spring-boot/tree/master/azure-spring-boot-samples/azure-active-directory-b2c-oidc-spring-boot-sample/src/main/resources/templates

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

ID: f81d7cec-7853-fe76-8178-dc1fc6886f1b
Version Independent ID: 61b1f5e0-f5cb-83c2-04ef-e8202dea9b33
Content: Use the Spring Boot Starter for Azure Active Directory B2C
Content Source: articles/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-active-directory-b2c-oidc.md
Service: active-directory-b2c
GitHub Login: @panli
Microsoft Alias: edburns

@m-moris thanks for the feedback! I've updated the topics with the correct URLs, so the links will work starting next week. The correct URLs are:

https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/spring/azure-spring-boot-samples/azure-spring-boot-sample-active-directory-b2c-oidc/src/main/resources/application.yml

https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/spring/azure-spring-boot-samples/azure-spring-boot-sample-active-directory-b2c-oidc/src/main/resources/templates


the position of the menu when the dropdown is right-aligned opened.

https://sveltestrap.js.org/?path=/story/components--dropdown
It seems to me that the Alighment EXAMPLE in this URL has an unintended behavior.
I believe the right edge of the menu should be aligned with the right edge of the button, is that correct?
This issue also occurs with Direction EXAMPLE.
I think a possible cause is that the dropdown div is too wide. So setting fit-content to width in the dropdown class should solve the issue.
If this is the right solution, we would be happy to create a PullRequest and help you fix it!

Hi @mugi111 ,
Thanks for the heads up.   Changing the dropdown class might work but that is not something we can fix in this library as people may use external Bootstrap files from CDN, etc.
I think we can add class or changes to Dropdown component, but you can also workaround by adding this to your code where you use Dropdown:
<Dropdown class="d-inline-block" ...>

Can you confirm that behaves as you expect?

@bestguy
Thank you for your quick reply.
You're right, you right.
I'm sorry I talked without understanding.
I confirmed behaves as I expect by that method.

It's no problem, we might want to default to that class in the component.  I'll look at change this weekend, thanks for the heads up.

@bestguy
You're welcome.
I'm wishing for continued success of this great project.
I'm supporting this you and this project!


disallow detached args to remove(), lock(), and refresh()

This makes HR follow the behavior defined by the JPA spec, instead of legacy Hibernate behavior.
See discussion in #344.

This is good to go, it seems to me.

Rebased and merged https://github.com/hibernate/hibernate-reactive/pull/346
Thanks!


WordBazzar Vote Options design and loading steps

Closes #966
Closes #967
Closes #969

margins look quite big here

margins look quite big here

@AtanasKrondev can you resolve the conflicts so we can merge this PR? Thanks!

@AtanasKrondev can you resolve the conflicts so we can merge this PR? Thanks!

@AtanasKrondev can you resolve the conflicts so we can merge this PR? Thanks!

Currently resolving and will merge it afterwards.

@AtanasKrondev can you resolve the conflicts so we can merge this PR? Thanks!

Currently resolving and will merge it afterwards.


[Feature] scripts like huggingface autotrain

Describe the feature
Hugging Face autotrain
My idea is a script that uses the same dataset and schedule, but runs different experiments on the backbone.
A naive implementation would be:
config.py
_base_ = [
    '../_base_/datasets/sample_dataset.py',
    '../_base_/schedules/sample_schedule.py',
    '../_base_/default_runtime.py'
]

script.py
backbones = ['./_base_/models/swin-s.py', './_base_/models/efficientnet-b0.py', './_base_/models/convnext-s.py']
_base_cp = copy.deepcopy(_base_)
for backbone in backbones:
    _base_cp.append(backbone)
then load config and train.

Will you implement it?

[ ] I would like to implement this feature and create a PR!

backbones = ['./base/models/swin-s.py', './base/models/efficientnet-b0.py', './base/models/convnext-s.py']
_base_cp = copy.deepcopy(base)

where is the backbone choice placed? in the config or the command?

in config

_base_ = xxxx

models = ['./_base_/models/swin-s.py', './_base_/models/efficientnet-b0.py', './_base_/models/convnext-s.py']

python batch_train.py batch_cfg.py

in CLI

_base_ = xxxx

python batch_train.py base_cfg.py --models ./_base_/models/swin-s.py ./_base_/models/efficientnet-b0.py ./_base_/models/convnext-s.py .....

Option 1 looks good 👍

It kind of functions like our development tools. which used like:

python .dev_scripts/benchmark_regression/3-benchmark_train.py --models xx xx(can be matched by re)
Then you will see which job you would run

python .dev_scripts/benchmark_regression/3-benchmark_train.py --models xx xx --run to run

python .dev_scripts/benchmark_regression/3-benchmark_train.py --models xx xx --summary to see the summary result

Maybe models can be set both in the config and CLI. But how to show what tasks we are about to run? I think it is necessary to show that. I'll try to investigate this kind of feature elsewhere.


SNOWFLAKE STORED PROCEDURE GRANTS/PERMISSION ARE GETTING REMOVED WHENEVER STORED PROCEDURE IS GETTING UPDATED

Provider Version
chanzuckerberg/snowflake v0.33.1
Terraform Version
terraform/0.14.8
Describe the bug
We are deploying stored procedure using "snowflake_procedure" resource and the permission/grants is provided through "snowflake_procedure_grant" resource. Any time we make a change to procedure and deploy the permissions/grants are getting removed as the procedure is dropped and recreated(new version). However the grants are not getting applied.  So as a work around we apply the change one more time and now the terraform generates the plan to apply the procedure grants
Expected behavior
When procedure undergoes change the grants mentioned should be reapplied.
Code samples and commands
Please add code examples and commands that were run to cause the problem.
Additional context
Add any other context about the problem here.

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


AccountCreation

When the program is started, the user is met with a login/register page, and can choose to login if they have an account, and to register if they do not. The login page should ask for the users username and password before granting them access to their account. The register page will ask for the users name, a unique username, email, and password. Once the user has registered they are sent to the login page.


Double addition of items on ToChoiceBox addData:

ToChoiceBox addData: message add two items instead of one.

do you have an example that exhibit this issue ?

fixed :).
thanks, there was also an issue regarding item removing


This is our first travis file

Lets enable travis CI for our porject

rejected, a problem in travis.yml


how to modify the contents of a Tensor?

what is the candle equivalent of this?
t[2, :] *= 2;

This is actually not possible and on purpose, only variables are mutable, tensors by default are not. The goal is to favor a functional approach and avoid all sort of mutability. Do you have some specific use cases where this would be especially useful? (you may want to look at the yolo examples as the python implementation of these had some in place ops on slices that were converted to some cat etc operations).

Thanks for pointing me to the yolo examples. I looked through some of the other examples and couldn't really figure out how this was translated from Python.

Closing this as done but feel free to reopen or create a new issue if you have further questions.


Fix plugin databse tables

This should fix any plugin dbtable name issue.
Plugins meta is set right after all the models have been are discovered
On Django 1.6- we must patch a get_models as there is no suitable hook/signal
On Django 1.7 we can use AppConfig.ready that is called in the final phases of the project setup and after the model discovery

Coverage decreased (-0.08%) to 87.881% when pulling 5f99c454ed39179c337035367471ac26bfc96b9f on yakky:feature/plugin_discover into a000f0bf5d43c10d393e15c89fab6e84da4c4132 on divio:develop.

Coverage decreased (-0.08%) to 87.881% when pulling 5f99c454ed39179c337035367471ac26bfc96b9f on yakky:feature/plugin_discover into a000f0bf5d43c10d393e15c89fab6e84da4c4132 on divio:develop.

Coverage decreased (-0.08%) to 87.881% when pulling 5f99c454ed39179c337035367471ac26bfc96b9f on yakky:feature/plugin_discover into a000f0bf5d43c10d393e15c89fab6e84da4c4132 on divio:develop.

Coverage decreased (-0.08%) to 87.881% when pulling 5f99c454ed39179c337035367471ac26bfc96b9f on yakky:feature/plugin_discover into a000f0bf5d43c10d393e15c89fab6e84da4c4132 on divio:develop.


Load from docker image

Is there any way to load a package from a docker image?
The main reason I'm asking is that the tests for the shipyard don't always go through all the steps of being built into an image before being merged into main. For some packages it's difficult to figure out if changes made will build into a proper docker image during the PR process. It might be better to have them built into docker images and then tested (from the image) as part of the normal build process. And then just add the docker push once merged into main. This would facilitate more thorough testing.
Another option would be to add in something like a docker save followed by untaring to a clean directory into the shipyard main.ps1 or utils.ps1 files. Then that directory could be passed as an argument into the Test-PwrPackageInstall method.

I was thinking the same thing through the VS debacle. I added the local folder package specifically for testing, but you're right in that we need to upgrade that to docker tag or tar support.


Validate Phone Number is 8 - 16 digits

Fixes #157, #183
Also, closing #153, as it is redundant. (If the person gives you a wrong email, there's no point in complaining about the format, because it'll bounce either way).

Codecov Report

Merging #199 (33247bc) into master (81301eb) will decrease coverage by 0.51%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #199      +/-   ##
============================================
- Coverage     51.64%   51.13%   -0.52%
- Complexity      605      684      +79
============================================
  Files           125      128       +3
  Lines          2612     2955     +343
  Branches        336      419      +83
============================================
+ Hits           1349     1511     +162
- Misses         1181     1346     +165
- Partials         82       98      +16

Impacted Files
Coverage Δ

...c/main/java/seedu/edrecord/model/person/Phone.java
80.00% <ø> (ø)

...ava/seedu/edrecord/model/assignment/Weightage.java
60.00% <0.00%> (-9.24%)
:arrow_down:

...edu/edrecord/storage/module/JsonAdaptedModule.java
76.31% <0.00%> (-5.27%)
:arrow_down:

...va/seedu/edrecord/model/assignment/Assignment.java
71.42% <0.00%> (-5.05%)
:arrow_down:

.../main/java/seedu/edrecord/model/module/Module.java
77.52% <0.00%> (-4.14%)
:arrow_down:

...drecord/model/assignment/UniqueAssignmentList.java
23.80% <0.00%> (-0.11%)
:arrow_down:

...c/main/java/seedu/edrecord/ui/StatusBarFooter.java
0.00% <0.00%> (ø)

.../java/seedu/edrecord/logic/commands/CdCommand.java
0.00% <0.00%> (ø)

...ava/seedu/edrecord/logic/commands/MoveCommand.java
0.00% <0.00%> (ø)

...a/seedu/edrecord/logic/commands/RemoveCommand.java
0.00% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


Error: '!_debugLocked': is not true

package:flutter/src/widgets/navigator.dart': Failed assertion: line 4657 pos 12: '!_debugLocked': is not true.
The relevant error-causing widget was
SplashScreen
lib/root_app.dart:30

I could have given more important details, but I am super new to flutter.
I am using it like
SplashScreen.navigate(
        name: 'assets/riv/logo.riv',
        next: (context) => GraphQLWidgetScreen(),
        until: () => Future.delayed(
          Duration(
            seconds: 2,
          ),
        ),
        startAnimation: 'start',
      ),

Tho this works great on flutter web but throwing error on ios emulator. I havent checked in android.

That basically what the example app is doing and it doesn't throw this error, look like it fail pushing your widget to the current navigator for some reason. Difficult to know why, can you give a try to the example app see if you reproduce too ?

Can reproduce now,
until: () => Future.delayed(
          Duration(
            seconds: 2,
          ),
        ),

Throwing error
but not with
until: () => Future.delayed(
          Duration(
            seconds: 5,
          ),
        ),

I've just fixed this :) just do flutter pub upgrade and it should work, thanks for the report!


function: regexp_match and regexp_matches

Is your feature request related to a problem? Please describe.
I need a function that can extract the hashtags from a tweet. In postgres, it's regexp_match and regexp_matches .
postgres=# select regexp_matches('Hello #risingwave #singularity', '#\w+', 'g');
 regexp_matches
----------------
 {#risingwave}
 {#singularity}
(2 rows)

Describe the solution you'd like
https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-POSIX-REGEXP

regexp_match(target Varchar, pattern Varchar);
regexp_matches(target Varchar, pattern Varchar);
regexp_matches(target Varchar, pattern Varchar, flag Varchar);

Rust regexp library: https://docs.rs/regex/latest/regex/
Describe alternatives you've considered
N/A
Additional context
Add any other context or screenshots about the feature request here.

regexp_matches can be implemented after https://github.com/singularity-data/risingwave/pull/4030

Flags are not yet implemented. It's just ignored, which might be confusing. We'd better at least report an error @TennyZhuang
dev=> select regexp_match('abc01234xyz', 'ABC', 'i');
 ?column?
----------

(1 row)

I feel it won't be an issue as long as we keep the code and the doc consistent. What do you say?

@xxchan I feel it won't be an issue as long as we keep the code and the doc consistent. What do you say?

Yes, indeed. But just in case, I've just added an argument check #4546


Unify user experience when using all Azure Spring starters

When users use different Azure Spring starters, they expect to have a unified experience configuring azure sdk properties, creating credentials, and Spring-related functions.

[x] The consistent user experience when configuring properties (#23421)
[x] The consistent user experience when providing credentials (#21472)

[x] Since Azure SDKs should support TokenCredential, we need to provide this capability in our starters:

[x] Support TokenCredential in all storage/database area starters (#21486)
[x] Support TokenCredential in all messaging area starters (#22704)
[x] Support TokenCredential in all security area starters (#22705)
[x] Support TokenCredential in all app config starters (#22706)

[x] Different authentication methods are supported in different Azure SDKs other than TokenCredential, we should support all authentication methods an Azure SDK supports in our starters:

[x] Support other authentication methods in all storage/database area starters (#22707)
[x] Support other authentication methods in all messaging area starters (#22708)
[x] Support other authentication methods in all security area starters (#22709)
[x] Support other authentication methods in all app config area starters (#22710)

[x] When Spring Boot Actuator is used and health endpoint is enabled in Spring Boot projects, health indicators are expected to indicate components' health status. We should support this in all our starters. (#21974)

[x]  Support in messaging components (#21976)
[x]  Support in storage/database components (#21977)
[x]  Support in security components (#21979)
[x]  Support in app config components (#21982)

Closing this in favor of https://github.com/Azure/azure-sdk-for-java/issues/23402.


Fatal error while login

Hi,
I am trying to login with creditionals but it's give error.
Fatal error: Uncaught InstagramScraper\Exception\InstagramAuthException: Something went wrong. Please report issue. in /home/xxxx/public_html/vendor/xxx/instagram-php-scraper/src/InstagramScraper/Instagram.php:1220 Stack trace: #0 /home/aem37it2ujqa/public_html/stories-download.php(21): InstagramScraper\Instagram->login() #1 {main} thrown in /home/xxx/xxx/xxx/raiym/instagram-php-scraper/src/InstagramScraper/Instagram.php on line 1220
It's working before week ago. Now it's showing error after updating files week before back.
Can anybody help me out?

Please help me out. It's very urgent

i have a same issue

Before updating, login is working fine and getStories function was not working

Any solution to this problem?

Any solution?
Without login all works fine, but with  login credentials gets the same error.

Is there any update on this? It still doesn't work.

Why my Instagram account always says suspicious login attempt?


Add end2end example for SD3

Note for reviewers, other_impls.py is an external script not written by me, so feel free to ignore it.


[BEAM-5411] Simplify BeamUnnest

This simplifies BeamUnnest by moving most of the logic out into the conversion rule. This decouples the operation from our Calc implementation. This has the added benefit of failing on unsupported operations at planning time rather than execution time.

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

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

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

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

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

Java

Python

---

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

Run Java Precommit

and other logic updates

The @Nullable changes aren't functional, they only provide a hint to findbugs. It appears findbugs doesn't run on tests or this would have been in my previous PR. Passing null through each field is tested here: https://github.com/apache/beam/pull/6383/files#diff-999a08cfdaf0dc102fa5f86c9419fe22R48

The rest of this shouldn't be a functional change, it is just refactoring logic. There are existing tests for this path including here: https://github.com/apache/beam/blob/master/sdks/java/extensions/sql/src/test/java/org/apache/beam/sdk/extensions/sql/BeamSqlDslArrayTest.java#L214


Map link on https://justingosses.com/geology doesn't work, need to investigate

Describe the bug
Map link on https://justingosses.com/geology doesn't work, need to investigate

Fixed in https://github.com/JustinGOSSES/justingosses-website/pull/133


test: add unit tests for library orientation

Resolves #83
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[X] Extensive Unit Testing
[X] Documentation update

Checklist
Please carefully read these items and tick them off if the statements are true
or do not apply.

[X] I have performed a self-review of my own code
[X] My code follows the existing coding style, lints and generates no new
warnings
[X] I have added type annotations to all function/method signatures, and I
have added type annotations for any local variables that are non-trivial,
potentially ambiguous or might otherwise benefit from explicit typing.
[X] I have commented my code in hard-to-understand areas
[X] I have added ["Google-style docstrings"] to all new modules, classes,
methods/functions or updated previously existing ones
[X] I have added tests that prove my fix is effective or that my feature
works
[X] New and existing unit tests pass locally with my changes and I have not
reduced the code coverage relative to the previous state
[X] I have updated any sections of the app's documentation that are affected
by the proposed changes

Codecov Report

Merging #91 (a66f470) into dev (295fba7) will decrease coverage by 1.31%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##               dev      #91      +/-   ##
===========================================
- Coverage   100.00%   98.68%   -1.32%
===========================================
  Files           10       11       +1
  Lines          611      837     +226
===========================================
+ Hits           611      826     +215
- Misses           0       11      +11

Impacted Files
Coverage Δ

htsinfer/get_read_orientation.py
95.13% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Good stuff - thanks a lot @rohank63!


Update tt-avdata.adoc

An initial draft of the ToR for discussion and consideration.

replace by: https://github.com/wmo-im/sc-imt/pull/20


Dupe Botania

https://www.youtube.com/watch?v=KMrFx-ziGQw

I can't replicate this bug, but I can't understand the language in the video too.
Can you explain it a bit more?
Can you replicate this bug with only Botania installed?

This bug AE2 or Botania. Use Talisman with Botania. and use PatternTerm with AE2. and replicate this bug.

The video is not available anymore and I don't remember how the dupe works


Adding docker

There is about 1 week of logs that can be seen here however there are many unnecessary commits there (about 30-something) which are not exactly informative to track, so this is just a cleaned-up version of that pull request all in one commit.

This is not necessary, because all commits get squashed for the merge of the PR ;)


Phone validation multiple countries

Is it possible to allow multiple countries into phone validator?
These works individually :

new FormControl(null, Validators.compose([Validators.required, CustomValidators.phone('US')])),
new FormControl(null, Validators.compose([Validators.required, CustomValidators.phone('CA')])),

But when trying to do both ,"ERROR TypeError: Cannot read property '9' of undefined"
new FormControl(null, Validators.compose([Validators.required, CustomValidators.phone(['US','CA'])])),
Curious to know if there is multiple country support . If so how do we do?. Thank you

Added this feature, see my pull request.
You can use it like CustomValidators.phone('EN', 'US')


Binding: Expose blpapi::Session::createIdentity

This will provide greater flexibility for the JS layer when dealing with identity objects.

Closed by #49


removeLayer method throws an error

Here it the code-fragment for 'removeLayer':
 removeLayer: function (layer) {
    var id = L.Util.stamp(layer);
    var _layer = this._getLayer(id);
    if (_layer) {
      delete this.layers[this.layers.indexOf(_layer)]; // `this.layers` should be replaced with `this._layers`
    }
    this._update();
    return this;
  }

Instead of this.layers should be this._layers i guess.

You're totally right about that. Would someone mind opening a pull request with the fix?

I can do later

calling delete on the array index is not sufficient, as later it is possible to iterate over the array and delete leaves the value at that index 'undefined'.  Instead, you must splice the item from the array to leave it continuously defined.
I had included a fix in my pull request #46 (an unrelated feature request)

Please, accept the PR to fix the issue caused by using delete on array.

Possible to merge this pull request and release a new version to npm?


[Gen 2] Request to support sorting relation items

Describe the feature you'd like to request
Say there is a Team has a one-to-many relationship to Member. My goal is to get team members sorted by createdAt field.
Below is the official example to define relationships, but there is no instruction how to sort the team members like await team.members({sortDirection: 'DESC'})
const schema = a.schema({
  Member: a.model({
    name: a.string().required(),
    // 1. Create a reference field
    teamId: a.id(),
    // 2. Create a belongsTo relationship with the reference field
    team: a.belongsTo('Team', 'teamId'),
  })
  .authorization(allow => [allow.publicApiKey()]),

  Team: a.model({
    mantra: a.string().required(),
    // 3. Create a hasMany relationship with the reference field
    //    from the `Member`s model.
    members: a.hasMany('Member', 'teamId'),
  })
  .authorization(allow => [allow.publicApiKey()]),
});

const { data: members } = await team.members();

Describe the solution you'd like
Support sortKey config here members: a.hasMany('Member', 'teamId', {sortKeys: ['createdAt']}),
Describe alternatives you've considered
Add .secondaryIndexes(index => [index('teamId').sortKeys(['createdAt']).queryField('listByDate')]) to Member model, and get members by client.models.Message.listByDate({roomId}, {sortDirection: 'DESC}) instead of await team.members(),
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

Hey @hangoocn, Thanks for raising this. We are marking this as a feature request for the team to evaluate further.

Having the ability to add a sort key to relationships like .hasMany would be great. I'm having the same use-case where i want to have all results for the .hasMany relationship sorted by createdAt.


Paradise Lost Crashes when loaded with Create's fabric port

What were you doing when the crash occured? How can we replicate it?

install Fabric API 0.51.1 (latest)
install Create 0.4.1+534 (latest) from here
install Paradise Lost 1.6.8 (latest)
launch game with Fabric Loader 0.13.3

Did it crash the client or server?
Client
Mod Version
Beta 1.6.8
Fabric API Version
0.51.1
Crash Report
https://pastebin.com/ut7Vy5dC

Other mods
Mods are as listed in Replication Steps, but can also be downloaded here.
Additional Information
No response

I also left this as an issue on the Create mod's GitHub, as I am unsure whether it is caused by this mod or theirs.

Having similar issue on 1.6.9 of Paradise Lost

Hm, seems to be crashing due to shaders. Perhaps there is a conflict in regards to how we apply them?
@gudenau would be more knowledgeable about this

According to the Create devs, this is likely caused by the boreal wisteria leaf shader.

Is this related/the same thing as https://github.com/devs-immortal/Paradise-Lost/issues/665? Which can confirm, I have attempted using both releases of Create with both releases of Paradise Lost for 1.18.2, no combination of them will work.

Considering the only way for that registry to be locked is by getting the render layers, I would say that create is doing something funky.
Our render layers are registered about as early as possible.
Related code from Satin:
public final class BlockRenderLayerRegistry {
    public static final BlockRenderLayerRegistry INSTANCE = new BlockRenderLayerRegistry();
    private final Set<RenderLayer> renderLayers = new ObjectArraySet<>();   // ArraySet for faster iteration
    private volatile boolean registryLocked = false;

    private BlockRenderLayerRegistry(){}

    public void registerRenderLayer(RenderLayer layer) {
        if(registryLocked){
            throw new IllegalStateException(String.format(
                "RenderLayer %s was added too late.",
                    layer
            ));
        }

        renderLayers.add(layer);
    }

    public Set<RenderLayer> getLayers() {
        registryLocked = true;
        return renderLayers;
    }
}

Needs confirmation if this still occurs in 0.2.0

will be fixed in next Create release

Just tested it today, I'm glad to say the incompatibility is fixed.


Write mdbook

For reference on how to set up mdbook in the repro, you can take a look at what we did for Emergence (the design folder).
We also have a CI workflow for this, including deployment to GitHub Pages and verifying that all pages are included in the SUMMARY.md (otherwise they won't show up in the book).

Oh heck yeah, thanks! Exactly what I needed 😄


Failed to create service: services "pvc-xxx-ctrl-svc" already exists when creating pvc in OKD 3.11

Description
After a default installation of OKD 3.11 I proceeded with the installation of OpenEBS following the installation through kubectl method.
When creating a sample pvc:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: demo-vol1-claim
spec:
  storageClassName: openebs-jiva-default
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5G

The provisioner fails with the following errors logged:
I0723 17:16:27.625604       1 volume.go:73] OpenEBS volume provisioner namespace openebs
I0723 17:16:27.630157       1 leaderelection.go:187] attempting to acquire leader lease  openebs/openebs.io-provisioner-iscsi...
I0723 17:16:27.637989       1 leaderelection.go:196] successfully acquired lease openebs/openebs.io-provisioner-iscsi
I0723 17:16:27.638405       1 controller.go:636] Starting provisioner controller openebs.io/provisioner-iscsi_openebs-provisioner-584ffbf7d6-mw5mt_3e43e8e8-cd08-11ea-9e9c-0a580a82002d!
I0723 17:16:27.638420       1 event.go:221] Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"openebs", Name:"openebs.io-provisioner-iscsi", UID:"3e44d495-cd08-11ea-b5fe-065dd8f6cd0a", APIVersion:"v1", ResourceVersion:"134939", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' openebs-provisioner-584ffbf7d6-mw5mt_3e43e8e8-cd08-11ea-9e9c-0a580a82002d became leader
I0723 17:16:27.738816       1 controller.go:685] Started provisioner controller openebs.io/provisioner-iscsi_openebs-provisioner-584ffbf7d6-mw5mt_3e43e8e8-cd08-11ea-9e9c-0a580a82002d!
W0723 17:26:09.657643       1 reflector.go:270] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:673: watch of *v1.StorageClass ended with: The resourceVersion for the provided watch is too old.
I0723 17:30:38.875813       1 controller.go:991] provision "openebs/demo-vol1-claim" class "openebs-jiva-default": started
I0723 17:30:38.878528       1 event.go:221] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"openebs", Name:"demo-vol1-claim", UID:"39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a", APIVersion:"v1", ResourceVersion:"138782", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "openebs/demo-vol1-claim"
E0723 17:30:38.920868       1 volume.go:171] HTTP Status error from maya-apiserver: Not Found
I0723 17:30:38.921180       1 volume.go:105] CAS Volume Spec Created:
{"metadata":{"name":"pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a","namespace":"openebs","creationTimestamp":null,"labels":{"openebs.io/namespace":"openebs","openebs.io/persistentvolumeclaim":"demo-vol1-claim","openebs.io/storageclass":"openebs-jiva-default"}},"spec":{"capacity":"5G","iqn":"","targetPortal":"","targetIP":"","targetPort":"","replicas":"","casType":"","fsType":"","lun":0},"cloneSpec":{},"status":{"Phase":"","Message":"","Reason":""}}
I0723 17:30:39.053650       1 volume.go:132] volume Successfully Created:
{"apiVersion":"v1alpha1","kind":"CASVolume","metadata":{"annotations":{"openebs.io/storageclass-version":"134400"},"labels":{"openebs.io/cas-template-name":"jiva-volume-create-default-1.12.0","openebs.io/persistent-volume-claim":"demo-vol1-claim","openebs.io/version":"1.12.0"},"name":"pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a"},"spec":{"accessMode":"","capacity":"5G","casType":"jiva","fsType":"","iqn":"iqn.2016-09.com.openebs.jiva:pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a","lun":0,"replicas":"3","targetIP":"\u003cno value\u003e","targetPort":"3260","targetPortal":"<IP_ADDRESS>:3260"},"status":{"Message":"","Phase":"","Reason":""}}
E0723 17:30:39.174036       1 volume.go:171] HTTP Status error from maya-apiserver: Not Found
E0723 17:30:39.174259       1 cas_provision.go:123] Failed to read volume: Not Found
W0723 17:30:39.174395       1 controller.go:750] Retrying syncing claim "openebs/demo-vol1-claim" because failures 0 < threshold 15
E0723 17:30:39.174451       1 controller.go:765] error syncing claim "openebs/demo-vol1-claim": failed to provision volume with StorageClass "openebs-jiva-default": Not Found
I0723 17:30:39.174511       1 event.go:221] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"openebs", Name:"demo-vol1-claim", UID:"39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a", APIVersion:"v1", ResourceVersion:"138782", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "openebs-jiva-default": Not Found
W0723 17:30:45.665431       1 reflector.go:270] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:670: watch of *v1.PersistentVolume ended with: The resourceVersion for the provided watch is too old.
I0723 17:30:54.174828       1 controller.go:991] provision "openebs/demo-vol1-claim" class "openebs-jiva-default": started
I0723 17:30:54.178365       1 event.go:221] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"openebs", Name:"demo-vol1-claim", UID:"39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a", APIVersion:"v1", ResourceVersion:"138782", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "openebs/demo-vol1-claim"
E0723 17:30:54.231598       1 volume.go:171] HTTP Status error from maya-apiserver: Not Found
I0723 17:30:54.231738       1 volume.go:105] CAS Volume Spec Created:
{"metadata":{"name":"pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a","namespace":"openebs","creationTimestamp":null,"labels":{"openebs.io/namespace":"openebs","openebs.io/persistentvolumeclaim":"demo-vol1-claim","openebs.io/storageclass":"openebs-jiva-default"}},"spec":{"capacity":"5G","iqn":"","targetPortal":"","targetIP":"","targetPort":"","replicas":"","casType":"","fsType":"","lun":0},"cloneSpec":{},"status":{"Phase":"","Message":"","Reason":""}}
E0723 17:30:54.284492       1 volume.go:128] Internal Server Error: failed to create volume 'pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a': response: failed to create volume:

It seems like the main issue here is with maya:
E0723 17:30:38.920868       1 volume.go:171] HTTP Status error from maya-apiserver: Not Found

Checking maya logs I see:
I0723 17:30:38.923176       1 volume_endpoint_v1alpha1.go:135] received volume create request
I0723 17:30:39.053981       1 volume_endpoint_v1alpha1.go:165] volume 'pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a' created successfully
I0723 17:30:39.055239       1 volume_endpoint_v1alpha1.go:78] received cas volume request: http method {GET}
I0723 17:30:39.055271       1 volume_endpoint_v1alpha1.go:171] received volume read request: pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
W0723 17:30:39.170614       1 task.go:433] notfound error at runtask {readlistrep}: error {replica pod(s) not found}
W0723 17:30:39.172629       1 runner.go:166] nothing to rollback: no rollback tasks were found
2020/07/23 17:30:39.174793 [ERR] http: Request GET /latest/volumes/pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
failed to read volume: volume {pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a} not found in namespace {openebs}
I0723 17:30:54.181013       1 volume_endpoint_v1alpha1.go:78] received cas volume request: http method {GET}
I0723 17:30:54.181071       1 volume_endpoint_v1alpha1.go:171] received volume read request: pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
W0723 17:30:54.231838       1 task.go:433] notfound error at runtask {readlistrep}: error {replica pod(s) not found}
W0723 17:30:54.232374       1 runner.go:166] nothing to rollback: no rollback tasks were found
2020/07/23 17:30:54.232420 [ERR] http: Request GET /latest/volumes/pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
failed to read volume: volume {pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a} not found in namespace {openebs}
I0723 17:30:54.233786       1 volume_endpoint_v1alpha1.go:78] received cas volume request: http method {POST}
I0723 17:30:54.233816       1 volume_endpoint_v1alpha1.go:135] received volume create request
W0723 17:30:54.284826       1 runner.go:166] nothing to rollback: no rollback tasks were found
2020/07/23 17:30:54.285123 [ERR] http: Request POST /latest/volumes/
failed to create volume:
casvolume {cloneSpec: {}
metadata:
  creationTimestamp: null
  labels:
    openebs.io/namespace: openebs
    openebs.io/persistentvolumeclaim: demo-vol1-claim
    openebs.io/storageclass: openebs-jiva-default
  name: pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
  namespace: openebs
spec:
  accessMode: ""
  capacity: 5G
  casType: ""
  fsType: ""
  iqn: ""
  lun: 0
  replicas: ""
  targetIP: ""
  targetPort: ""
  targetPortal: ""
status:
  Message: ""
  Phase: ""
  Reason: ""
}: failed to execute volume engine: failed to execute runtask {jiva-volume-create-puttargetservice-default-1.12.0}:
template values {CAST:
  castName: jiva-volume-create-default-1.12.0
  kubeVersion: v1.11.0
  version: 1.12.0
Config:
  AuxResourceLimits:
    enabled: ""
    value: none
  AuxResourceRequests:
    enabled: ""
    value: none
  ControllerImage:
    enabled: ""
    value: openebs/jiva:1.12.0
  DeployInOpenEBSNamespace:
    enabled: "true"
    value: ""
  EvictionTolerations:
    enabled: ""
    value: |-
      t1:
        effect: NoExecute
        key: node.alpha.kubernetes.io/notReady
        operator: Exists
      t2:
        effect: NoExecute
        key: node.alpha.kubernetes.io/unreachable
        operator: Exists
      t3:
        effect: NoExecute
        key: node.kubernetes.io/not-ready
        operator: Exists
      t4:
        effect: NoExecute
        key: node.kubernetes.io/unreachable
        operator: Exists
      t5:
        effect: NoExecute
        key: node.kubernetes.io/out-of-disk
        operator: Exists
      t6:
        effect: NoExecute
        key: node.kubernetes.io/memory-pressure
        operator: Exists
      t7:
        effect: NoExecute
        key: node.kubernetes.io/disk-pressure
        operator: Exists
      t8:
        effect: NoExecute
        key: node.kubernetes.io/network-unavailable
        operator: Exists
      t9:
        effect: NoExecute
        key: node.kubernetes.io/unschedulable
        operator: Exists
      t10:
        effect: NoExecute
        key: node.cloudprovider.kubernetes.io/uninitialized
        operator: Exists
  FSType:
    enabled: ""
    value: ext4
  Lun:
    enabled: ""
    value: "0"
  NodeAffinityPreferredSchedIgnoredExec:
    enabled: ""
    value: |-
      t1:
        key: some-node-label-key
        operator: In
        values:
        - some-node-label-value
  NodeAffinityRequiredSchedIgnoredExec:
    enabled: ""
    value: |-
      t1:
        key: beta.kubernetes.io/os
        operator: In
        values:
        - linux
  OpenEBSNamespace:
    enabled: ""
    value: openebs
  ReplicaAntiAffinityTopoKey:
    enabled: ""
    value: kubernetes.io/hostname
  ReplicaCount:
    enabled: ""
    value: "3"
  ReplicaImage:
    enabled: ""
    value: openebs/jiva:1.12.0
  ReplicaNodeSelector:
    enabled: ""
    value: none
  ReplicaResourceLimits:
    enabled: ""
    value: none
  ReplicaResourceRequests:
    enabled: ""
    value: none
  ReplicaTolerations:
    enabled: ""
    value: none
  StoragePool:
    enabled: ""
    value: default
  TargetNodeSelector:
    enabled: ""
    value: none
  TargetResourceLimits:
    enabled: ""
    value: none
  TargetResourceRequests:
    enabled: ""
    value: none
  TargetTolerations:
    enabled: ""
    value: none
  VolumeMonitor:
    enabled: "true"
    value: ""
  VolumeMonitorImage:
    enabled: ""
    value: openebs/m-exporter:1.12.0
JsonResult: --redacted--
ListItems: {}
TaskResult:
  creategetpvc:
    replicaAntiAffinity: none
    targetAffinity: none
    verifyErr: null
  creategetsc:
    storageClassVersion: "134400"
    verifyErr: null
  createputsvc:
    jivapodsns: openebs
    verifyErr: null
  stsTargetAffinity: none
Volume:
  capacity: 5G
  isCloneEnable: "false"
  isRestoreVol: "false"
  owner: pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
  pvc: demo-vol1-claim
  runNamespace: openebs
  snapshotName: ""
  sourceVolume: ""
  sourceVolumeTargetIP: ""
  storageclass: openebs-jiva-default
}: failed to execute task:
task executor {MetaExec: {}
Runtask:
  metadata:
    creationTimestamp: "2020-07-23T17:16:27Z"
    generation: 1
    labels:
      version: 1.12.0
    name: jiva-volume-create-puttargetservice-default-1.12.0
    namespace: openebs
    resourceVersion: "134878"
    selfLink: /apis/openebs.io/v1alpha1/namespaces/openebs/runtasks/jiva-volume-create-puttargetservice-default-1.12.0
    uid: 3e1351b5-cd08-11ea-b5fe-065dd8f6cd0a
  spec:
    meta: |
      {{- $deployInOpenEBSNamespace := .Config.DeployInOpenEBSNamespace.enabled | default "true" | lower -}}
      id: createputsvc
      {{- if eq $deployInOpenEBSNamespace "true" }}
      runNamespace: {{ .Config.OpenEBSNamespace.value | trim | saveAs "createputsvc.jivapodsns" .TaskResult }}
      {{ else }}
      runNamespace: {{ .Volume.runNamespace | trim | saveAs "createputsvc.jivapodsns" .TaskResult }}
      {{ end }}
      apiVersion: v1
      kind: Service
      action: put
    post: |
      {{- jsonpath .JsonResult "{.metadata.name}" | trim | saveAs "createputsvc.objectName" .TaskResult | noop -}}
      {{- jsonpath .JsonResult "{.spec.clusterIP}" | trim | saveAs "createputsvc.clusterIP" .TaskResult | noop -}}
    task: |-
      apiVersion: v1
      Kind: Service
      metadata:
        annotations:
          openebs.io/storage-class-ref: |
            name: {{ .Volume.storageclass }}
            resourceVersion: {{ .TaskResult.creategetsc.storageClassVersion }}
        labels:
          openebs.io/storage-engine-type: jiva
          openebs.io/cas-type: jiva
          openebs.io/controller-service: jiva-controller-svc
          openebs.io/persistent-volume: {{ .Volume.owner }}
          openebs.io/persistent-volume-claim: {{ .Volume.pvc }}
          pvc: {{ .Volume.pvc }}
          openebs.io/version: {{ .CAST.version }}
          openebs.io/cas-template-name: {{ .CAST.castName }}
        name: {{ .Volume.owner }}-ctrl-svc
      spec:
        ports:
        - name: iscsi
          port: 3260
          protocol: TCP
          targetPort: 3260
        - name: api
          port: 9501
          protocol: TCP
          targetPort: 9501
        - name: exporter
          port: 9500
          protocol: TCP
          targetPort: 9500
        selector:
          openebs.io/controller: jiva-controller
          openebs.io/persistent-volume: {{ .Volume.owner }}
Values:
  CAST:
    castName: jiva-volume-create-default-1.12.0
    kubeVersion: v1.11.0
    version: 1.12.0
  Config:
    AuxResourceLimits:
      enabled: ""
      value: none
    AuxResourceRequests:
      enabled: ""
      value: none
    ControllerImage:
      enabled: ""
      value: openebs/jiva:1.12.0
    DeployInOpenEBSNamespace:
      enabled: "true"
      value: ""
    EvictionTolerations:
      enabled: ""
      value: |-
        t1:
          effect: NoExecute
          key: node.alpha.kubernetes.io/notReady
          operator: Exists
        t2:
          effect: NoExecute
          key: node.alpha.kubernetes.io/unreachable
          operator: Exists
        t3:
          effect: NoExecute
          key: node.kubernetes.io/not-ready
          operator: Exists
        t4:
          effect: NoExecute
          key: node.kubernetes.io/unreachable
          operator: Exists
        t5:
          effect: NoExecute
          key: node.kubernetes.io/out-of-disk
          operator: Exists
        t6:
          effect: NoExecute
          key: node.kubernetes.io/memory-pressure
          operator: Exists
        t7:
          effect: NoExecute
          key: node.kubernetes.io/disk-pressure
          operator: Exists
        t8:
          effect: NoExecute
          key: node.kubernetes.io/network-unavailable
          operator: Exists
        t9:
          effect: NoExecute
          key: node.kubernetes.io/unschedulable
          operator: Exists
        t10:
          effect: NoExecute
          key: node.cloudprovider.kubernetes.io/uninitialized
          operator: Exists
    FSType:
      enabled: ""
      value: ext4
    Lun:
      enabled: ""
      value: "0"
    NodeAffinityPreferredSchedIgnoredExec:
      enabled: ""
      value: |-
        t1:
          key: some-node-label-key
          operator: In
          values:
          - some-node-label-value
    NodeAffinityRequiredSchedIgnoredExec:
      enabled: ""
      value: |-
        t1:
          key: beta.kubernetes.io/os
          operator: In
          values:
          - linux
    OpenEBSNamespace:
      enabled: ""
      value: openebs
    ReplicaAntiAffinityTopoKey:
      enabled: ""
      value: kubernetes.io/hostname
    ReplicaCount:
      enabled: ""
      value: "3"
    ReplicaImage:
      enabled: ""
      value: openebs/jiva:1.12.0
    ReplicaNodeSelector:
      enabled: ""
      value: none
    ReplicaResourceLimits:
      enabled: ""
      value: none
    ReplicaResourceRequests:
      enabled: ""
      value: none
    ReplicaTolerations:
      enabled: ""
      value: none
    StoragePool:
      enabled: ""
      value: default
    TargetNodeSelector:
      enabled: ""
      value: none
    TargetResourceLimits:
      enabled: ""
      value: none
    TargetResourceRequests:
      enabled: ""
      value: none
    TargetTolerations:
      enabled: ""
      value: none
    VolumeMonitor:
      enabled: "true"
      value: ""
    VolumeMonitorImage:
      enabled: ""
      value: openebs/m-exporter:1.12.0
  JsonResult: --redacted--
  ListItems: {}
  TaskResult:
    creategetpvc:
      replicaAntiAffinity: none
      targetAffinity: none
      verifyErr: null
    creategetsc:
      storageClassVersion: "134400"
      verifyErr: null
    createputsvc:
      jivapodsns: openebs
      verifyErr: null
    stsTargetAffinity: none
  Volume:
    capacity: 5G
    isCloneEnable: "false"
    isRestoreVol: "false"
    owner: pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a
    pvc: demo-vol1-claim
    runNamespace: openebs
    snapshotName: ""
    sourceVolume: ""
    sourceVolumeTargetIP: ""
    storageclass: openebs-jiva-default
}: failed to create service: services "pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a-ctrl-svc" already exists

The final part of the log:
failed to create service: services "pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a-ctrl-svc" already exists

Is what I don't fully get as it doesn't make sense since the service was created by the operator, or at least that is what I understand.
Expected Behavior

I would expect the pvc to be created successfully

Current Behavior

pvc remains in the following Pending state:

oc get pvc
NAME              STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS           AGE
demo-vol1-claim   Pending                                       openebs-jiva-default   12m

Your Environment

kubectl get nodes:

NAME                                       STATUS    ROLES           AGE       VERSION
ip-10-0-0-132.eu-west-1.compute.internal   Ready     compute         2d        v1.11.0+d4cacc0
ip-10-0-0-151.eu-west-1.compute.internal   Ready     infra,master    2d        v1.11.0+d4cacc0
ip-10-0-0-163.eu-west-1.compute.internal   Ready     compute,infra   2d        v1.11.0+d4cacc0

kubectl get pods --all-namespaces:

kubectl get pods --all-namespaces
NAMESPACE                           NAME                                                             READY     STATUS             RESTARTS   AGE
default                             docker-registry-3-xllch                                          1/1       Running            0          1d
default                             registry-console-1-csmvw                                         1/1       Running            0          1d
default                             router-5-g94qv                                                   1/1       Running            0          1d
default                             router-5-vf2p6                                                   1/1       Running            0          1d
kube-service-catalog                apiserver-d6hw8                                                  1/1       Running            1          1d
kube-service-catalog                controller-manager-s8mlp                                         1/1       Running            4          1d
kube-system                         master-api-ip-10-0-0-151.eu-west-1.compute.internal              1/1       Running            11         2d
kube-system                         master-controllers-ip-10-0-0-151.eu-west-1.compute.internal      1/1       Running            12         2d
kube-system                         master-etcd-ip-10-0-0-151.eu-west-1.compute.internal             1/1       Running            8          2d
openebs                             maya-apiserver-bddd7bc5f-xv9jw                                   1/1       Running            0          27m
openebs                             openebs-admission-server-5646df6c6-mdgdn                         1/1       Running            0          27m
openebs                             openebs-localpv-provisioner-dbbddc59b-f6gpz                      1/1       Running            0          27m
openebs                             openebs-ndm-operator-685c7bfdd7-7hkfg                            1/1       Running            0          27m
openebs                             openebs-provisioner-584ffbf7d6-mw5mt                             1/1       Running            0          27m
openebs                             openebs-snapshot-operator-68d4477c6-jz6rl                        2/2       Running            0          27m
openebs                             percona                                                          0/1       Pending            0          13m
openebs                             pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a-ctrl-685ff74db9-m484b   2/2       Running            0          13m
openshift-console                   console-6d9fc6c997-ndlwt                                         1/1       Running            0          1d
openshift-infra                     bootstrap-autoapprover-0                                         1/1       Running            0          1d
openshift-monitoring                alertmanager-main-0                                              3/3       Running            0          1d
openshift-monitoring                alertmanager-main-1                                              3/3       Running            0          2h
openshift-monitoring                alertmanager-main-2                                              3/3       Running            0          2h
openshift-monitoring                cluster-monitoring-operator-8578656f6f-4228q                     1/1       Running            0          1d
openshift-monitoring                grafana-dbfd84995-bjn8z                                          2/2       Running            0          1d
openshift-monitoring                kube-state-metrics-c4f86b5f8-6k7db                               3/3       Running            0          1d
openshift-monitoring                node-exporter-9rb5k                                              2/2       Running            2          1d
openshift-monitoring                node-exporter-ljk24                                              2/2       Running            2          1d
openshift-monitoring                node-exporter-tz5wq                                              2/2       Running            2          1d
openshift-monitoring                prometheus-k8s-0                                                 4/4       Running            1          1d
openshift-monitoring                prometheus-k8s-1                                                 4/4       Running            1          2h
openshift-monitoring                prometheus-operator-6644b8cd54-xwcj4                             1/1       Running            0          1d
openshift-node                      sync-47zlv                                                       1/1       Running            1          1d
openshift-node                      sync-dftjd                                                       1/1       Running            1          1d
openshift-node                      sync-vbkfp                                                       1/1       Running            1          1d
openshift-sdn                       ovs-jtqsm                                                        1/1       Running            4          2d
openshift-sdn                       ovs-l574b                                                        1/1       Running            3          2d
openshift-sdn                       ovs-zqzh6                                                        1/1       Running            4          2d
openshift-sdn                       sdn-9rf9v                                                        1/1       Running            4          2d
openshift-sdn                       sdn-bnfdj                                                        1/1       Running            5          2d
openshift-sdn                       sdn-z4qf6                                                        1/1       Running            4          2d
openshift-template-service-broker   apiserver-5zbts                                                  1/1       Running            1          1d

kubectl get services:

NAME                                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
admission-server-svc                                ClusterIP   <IP_ADDRESS>    <none>        443/TCP                      28m
maya-apiserver-service                              ClusterIP   <IP_ADDRESS>   <none>        5656/TCP                     28m
pvc-39a3db4a-cd0a-11ea-b5fe-065dd8f6cd0a-ctrl-svc   ClusterIP   <IP_ADDRESS>    <none>        3260/TCP,9501/TCP,9500/TCP   13m

kubectl get sc:

NAME                        PROVISIONER                                                AGE
openebs-device              openebs.io/local                                           29m
openebs-hostpath            openebs.io/local                                           29m
openebs-jiva-default        openebs.io/provisioner-iscsi                               29m
openebs-snapshot-promoter   volumesnapshot.external-storage.k8s.io/snapshot-promoter   29m

kubectl get pv:

No resources found

kubectl get pvc:

NAME              STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS           AGE
demo-vol1-claim   Pending                                       openebs-jiva-default   14m

OS (from /etc/os-release):

cat /etc/*release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.8 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.8"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.8 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.8:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.8
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.8"
Red Hat Enterprise Linux Server release 7.8 (Maipo)
Red Hat Enterprise Linux Server release 7.8 (Maipo)

Kernel (from uname -a):

Linux ip-10-0-0-151.eu-west-1.compute.internal 3.10.0-1127.13.1.el7.x86_64 #1 SMP Fri Jun 12 14:34:17 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux

Install tools: openebs installed using the kubectl procedure described in the official documentation.

@HenryGP for openshift based cluster follow the steps mentioned  https://docs.openebs.io/docs/next/kb.html#OpenEBS-install-openshift-4.1