typescript toolset not building on linux/arm64 as would be best on an M1

Here a recap of the situation. Docker's default target architecture matches the host. On an M1 this is arm64. The containers are built for linux so the default target platform will be linux/arm64.
While Chrome is available on Darwin arm64 it is not available for linux. For linux Chromium would be the prime candidate to replace Chrome.
Should the image switch to Chromium? How can we test that it works as expected? Did we have issues with Chromium in the past and that is why we are using Chrome?
Would it make sense to only switch for linux/arm64?
The alternative would be to continue building the typescript toolset for linux/amd64 only for which Chrome is supported. However the build takes quite a bit longer (see https://github.com/opendevstack/ods-pipeline/issues/360#issuecomment-1003030571) and may also run a bunch slower.
See also https://github.com/opendevstack/ods-pipeline/issues/360#issuecomment-1004665742 and subsequent comment.

This has already been fixed by PR #428.


LIVE-2927 reborn analytics

📝 Description
This PR contains fixes for Reborn analytics
❓ Context

Impacted projects: ledger-live-mobile
Linked resource(s):

LIVE-2927
LIVE-2928

✅ Checklist

[ ] Test coverage
[X] Atomic delivery
[X] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

@jules-grenier-ledger @nparigi-ledger could you fix the flow issues for the CI to pass :pray:


[Camera]: get focal length of camera

Use case
When a device is used with multiple back camera's. It would be handy to know the focal length of each camera.
That way a user interface can be implemented that shows the appropriate icons for each camera.
Ex:

Proposal
A new attribute to the CameraDescription class "focalLength". Used like this:
        cameras = await availableCameras();

        for (CameraDescription c in cameras) {
          print(c.focalLength);
        }

Android: camera2 supports focalLength
https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics
IOS: AvFoundation doesn't support a focallength parameter
A distinction between ultrawide, wide and telephoto lens would also be a huge step forward.
https://developer.apple.com/documentation/avfoundation/avcapturedevice/devicetype
Otherwise the videoFieldOfView parameter could be used and converted
https://developer.apple.com/documentation/avfoundation/avcapturedeviceformat/1624569-videofieldofview
func get35mmEquivalentFocalLength(format : AVCaptureDevice.Format) -> Float {
    // get reported field of view. Documentation says this is the horizontal field of view
    var fov = format.videoFieldOfView
    // convert to radians
    fov *= Float.pi/180.0
    // angle and opposite of right angle triangle are half the fov and half the width of
    // 35mm film (ie 18mm). The adjacent value of the right angle triangle is the equivalent
    // focal length. Using some right angle triangle math you can work out focal length
    let focalLen = 18 / tan(fov/2)
    return focalLen
}

Related to https://github.com/flutter/flutter/issues/78617, but this issue is related specifically to focal length.
Labeling as proposal.

C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:158: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_HIGH);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:162: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_2160P);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:166: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_1080P);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:170: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_720P);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:174: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_480P);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:178: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_QVGA);
^
C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\camera_android-0.10.4\android\src\main\java\io\flutter\plugins\camera\features\resolution\ResolutionFeature.java:182: warning: [deprecation] get(int,int) in CamcorderProfile
has been deprecated
return CamcorderProfile.get(cameraId, CamcorderProfile.QUALITY_LOW);
^
7 warnings
Note: C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\geolocator_android-4.1.7\android\src\main\java\com\baseflow\geolocator\location\FusedLocationClient.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\google_maps_flutter_android-2.4.3\android\src\main\java\io\flutter\plugins\googlemaps\Convert.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\google_mlkit_commons-0.2.0\android\src\main\java\com\google_mlkit_commons\InputImageConverter.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: C:\Users\aungy\AppData\Local\Pub\Cache\hosted\pub.dev\google_mlkit_face_detection-0.5.0\android\src\main\java\com\google_mlkit_face_detection\FaceDetector.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
e: D:\xsphere projects\fary-taxi-end-user\android\app\src\main\kotlin\com\example\fary_taxi_enduser\MainActivity.kt: (5, 7): Redeclaration: MainActivity
e: D:\xsphere projects\fary-taxi-end-user\android\app\src\main\kotlin\com\xsphere\fary_taxi_enduser\MainActivity.kt: (5, 7): Redeclaration: MainActivity
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 44s
Running Gradle task 'assembleDebug'...                             45.3s
Exception: Gradle task assembleDebug failed with exit code 1

As suggested by @stuartmorgan  this is a comparison table showing how each platform's lens information does or doesn't align with other platforms.

Lens Type
iOS
Android
Web
Windows
macOS
Linux

General Support
Available via AVCaptureDeviceType API
Lens type info can be determined using Camera2 API. LENS_FACING for front/back/external, and field of view calculated using focal length (LENS_INFO_AVAILABLE_FOCAL_LENGTHS) and sensor size (SENSOR_INFO_PHYSICAL_SIZE). CameraX does not expose this level of detail.
Lens type info not available. Web APIs (MediaDevices) allow access to cameras but without detailed hardware info on lens types.
Lens type info not available. No native API for detailed lens types, standard webcam info available via DirectShow/MediaFoundation APIs
Lens type info available via AVCaptureDevice API. If the attached camera (e.g., with telephoto or wide lens) supports detailed lens info, the API can retrieve it. However, most built-in or external webcams do not expose multiple lens types
Lens type info not available. No native API for detailed lens types, standard webcam info available via v4l2 (Video4Linux2)

Ultra-Wide
Supported
Supported
No lens type info
No lens type info
Supported
No lens type info

Telephoto
Supported
Supported
No lens type info
No lens type info
Supported
No lens type info

Wide
Supported (default)
Supported (default)
No lens type info
No lens type info
Supported (default)
No lens type info

iOS avcapturedevicetype
Android Camera 2 CameraCharacteristics
On Web, Windows, Linux, and MacOS, there is camera access but no native support to access specific lens types or hardware details.

I suggested that we stick to wide, ultra-wide and telephoto for simplicity, and because it covers most common use-cases (as discussed here


Pass GITHUB_BASE_REF and GITHUB_REF_NAME in docs tox environment

Update according to https://github.com/Qiskit/qiskit-addon-utils/pull/56

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 95.39%

Totals

Change from base Build<PHONE_NUMBER>9:
0.3%

Covered Lines:
600

Relevant Lines:
629

💛  - Coveralls


fixed:[bug]: Combobox returning NULL if not option is given #1185

What does it do?
It fixes the bug [bug]: Combobox returning NULL if no option is available #1185
Why is it needed?
Bad User experience (UX)
Related issue(s)/PR(s)
The issue "CM: Relations no longer display "No relations available" when target CT is empty #17231" is related to this.

Hey @joshuaellis can you please review this!!
This issue is causing the bug "CM: Relations no longer display "No relations available" when target CT is empty #17231" in the main repo

Hey @joshuaellis  , I'm not sure about writing test for this. but I can say that there is no such case of regression here.

To test the use case though . Go to stories docs -> stories -> combobox.stories.mdx
For any of the remove all the ComboboxOption of any component
Go to localhost:6006
You will see that there are no placeholder like 'No option available'
But after this PR , there is this placeholder message written

While rendering options in the 'strapi-design-system/src/Combobox/Combobox.tsx/' in the ComboboxInput component we are returning this
          <Viewport ref={viewportRef}>
            {children}
            {creatable ? (
              <ComboboxPrimitive.CreateItem onPointerUp={handleCreateItemClick} onClick={handleCreateItemClick} asChild>
                <OptionBox>
                  <Typography>{createMessage(internalTextValue ?? '')}</Typography>
                </OptionBox>
              </ComboboxPrimitive.CreateItem>
            ) : null}
            {!creatable && !loading ? (
              <ComboboxPrimitive.NoValueFound asChild>
                <OptionBox $hasHover={false}>
                  <Typography>{noOptionsMessage(internalTextValue ?? '')}</Typography>
                </OptionBox>
              </ComboboxPrimitive.NoValueFound>
            ) : null}
            {loading ? (
              <Flex justifyContent="center" alignItems="center" paddingTop={2} paddingBottom={2}>
                <Loader small>{loadingMessage}</Loader>
              </Flex>
            ) : null}
            <Box id={intersectionId} width="100%" height="1px" />
          </Viewport>

You can see that we are rendering

childrens
creatables (if any)
no value found
loading
So ideally ComboboxPrimitives.NoValueFound should be handling this condition


kedro-docker builds are failing

Description
The kedro-docker build that's run every night has been failing for a while now.
Context
This doesn't just seem to be a flaky build, so we should fix it to ensure the quality of the plugin.
Steps to Reproduce
See builds: https://github.com/kedro-org/kedro-plugins/actions?query=event%3Aschedule

It's failing with ModuleNotFoundError: No module named 'pyspark'. I suspect it might be the https://github.com/kedro-org/kedro-plugins/issues/290

It seems like kedro-airflow build are failing now instead of kedro-docker

Follow up issue - https://github.com/kedro-org/kedro-plugins/issues/315


[New] Validate utility network topology

Description
This PR implements Validate utility network topology in Utility Networks category.
URL to README: README
Linked Issue(s)

swift/issues/4928

How To Test

Tap on a feature, select a new attribute value, and press "Apply".
Tap "Get State" to get the current state of the utitility network.
Tap "Validate" to validate network topology and clear dirty areas.
Tap "Trace" to run a trace.
Tap "Clear" to clear the selected feature(s).

Screenshots

Thank you!


Review notes

http://tc39.github.io/ecmascript-asyncawait/#status
Stage is now 3.
http://tc39.github.io/ecmascript-asyncawait/#async-decls-exprs-static-semantics-BoundNames
"*" are recognized as markdown instead of plain text.
http://tc39.github.io/ecmascript-asyncawait/#async-arrows-static-semantics-early-errors
"AsyncArrowFunction::CoverCallExpressionAndAsyncArrowHead" needs to handle [Yield], cf. http://tc39.github.io/ecma262/#sec-arrow-function-definitions-static-semantics-early-errors
It's probably not valid to reference "AsyncConciseBody" in "AsyncArrowHead::async[no LineTerminator here]ArrowFormalParameters", because AsyncConciseBody is not part of AsyncArrowHead.
http://tc39.github.io/ecmascript-asyncawait/#async-arrows-EvaluateBody
functionObject and argumentsList not passed in "AsyncConciseBody::{AsyncFunctionBody}".
http://tc39.github.io/ecmascript-asyncawait/#async-function-prototype-properties
Typo: "prototpe"
Typo: "instrinsic"

Thanks @anba for the great review :) Some questions, if I may...

"AsyncArrowFunction::CoverCallExpressionAndAsyncArrowHead" needs to handle [Yield], cf.

Do I need to handle yield specially? I don't see why it is necessary to include the verbage that ES6 has. Specifically, the action taken is same if yield is present or not present, so why not just say... apply the cover grammar with no tokens left over, and apply the yield semantics to the supplemental grammar?

It's probably not valid to reference "AsyncConciseBody" in "AsyncArrowHead::async[no LineTerminator here]ArrowFormalParameters", because AsyncConciseBody is not part of AsyncArrowHead.

Yeah you're probably right, good catch! I'm not sure how to fix this though - I can't make it a static semantics for AsyncArrowFunction :: CoverCallExpressionAndAsyncArrowHead => AsyncConciseBody since  ArrowFormalParameters is from the supplemental grammar. I'd hate to make the grammar less well factored to avoid this issue... Thoughts?
Fixed all the other issues you noted!

Yeah you're probably right, good catch! I'm not sure how to fix this though - I can't make it a static semantics for AsyncArrowFunction :: CoverCallExpressionAndAsyncArrowHead => AsyncConciseBody since ArrowFormalParameters is from the supplemental grammar. I'd hate to make the grammar less well factored to avoid this issue... Thoughts?

It should be possible to move all early error checks from AsyncArrowHead to AsyncArrowFunction.
-> https://gist.github.com/anba/ec84fa8d9ed13ee30511

Do I need to handle yield specially? I don't see why it is necessary to include the verbage that ES6 has. Specifically, the action taken is same if yield is present or not present, so why not just say... apply the cover grammar with no tokens left over, and apply the yield semantics to the supplemental grammar?

Now I wonder whether or not [Yield] is actually needed in AsyncArrowHead. Do you know an example where [Yield] is required (when the early errors checks are already applied to CoverCallExpressionAndAsyncArrowHead per the gist from above)?

It should be possible to move all early error checks from AsyncArrowHead to AsyncArrowFunction.
-> https://gist.github.com/anba/ec84fa8d9ed13ee30511

I see, I was thinking yesterday this wouldn't work because in some contexts CoverCallExpressionAndAsyncArrowHead is allowed to contain yield but attaching these semantics to AsyncArrowFunction seems fine I agree.

Now I wonder whether or not [Yield] is actually needed in AsyncArrowHead. Do you know an example where [Yield] is required (when the early errors checks are already applied to CoverCallExpressionAndAsyncArrowHead per the gist from above)?

I believe that it is needed because an async arrow not nested in a generator should allow yield-as-identifier so the static semantics would not cause an error in that case. Only when the parameter is present (ie. when the async arrow is in a generator body) should those static semantics create an error. Probably I'm missing something though.

@anba want to give that gist as a PR? I can pull it in too but it's easier to track your contributions if you send a PR :)

@anba want to give that gist as a PR? I can pull it in too but it's easier to track your contributions if you send a PR :)

Just created PR #69

I believe that it is needed because an async arrow not nested in a generator should allow yield-as-identifier so the static semantics would not cause an error in that case. Only when the parameter is present (ie. when the async arrow is in a generator body) should those static semantics create an error. Probably I'm missing something though.

Here's my reasoning why [Yield] is not required for AsyncArrowHead:
When the yield token is present in CoverCallExpressionAndAsyncArrowHead[Yield], one of the following productions gets parsed:

IdentifierReference
Throws a SyntaxError because of 12.1.1:

IdentifierReference[Yield] : Identifier

It is a Syntax Error if this production has a [Yield] parameter and StringValue of Identifier is "yield".

BindingIdentifier
Throws a SyntaxError because of 12.1.1:

BindingIdentifier[Yield] : Identifier

It is a Syntax Error if this production has a [Yield] parameter and StringValue of Identifier is "yield".

YieldExpression
Throws a SyntaxError because of:

AsyncArrowFunction

It is a Syntax Error if CoverCallExpressionAndAsyncArrowHead Contains YieldExpression is true.

That means yield is already rejected when parsing the initial CoverCallExpressionAndAsyncArrowHead[Yield] and therefore it should not be necessary to propagate [Yield] to AsyncArrowHead.

Alright, I agree with you!

This should all be addressed now. Thanks @anba!!!

Removing [Yield] in AsyncArrowHead is still an open issue. I'll try to create a PR for this later today.

@anba I think it's fixed, unless I misunderstand what you mean. See d3a5143.

Ah, I didn't see that commit. Sorry for the confusion!
(You forgot to update CoveredAsyncArrowHead. :wink: )

Whoops, will do it! Sorry :(


Add log-level option to conmon and crio.conf

conmon now has a --log-level flag that changes
the verbosity of the logs based on the value it
is set to. From logrus, panic(0), fatal(1), error(2) tells
conmon to print all pexit and nexit logs (this
is the default). warn(3) adds the nwarn logs, info(4)
adds the ninfo logs, and finally debug(5) adds the ndebug
logs as well.
Adds a log_level field in the crio.conf that can have the
following options: panic, fatal, error, warn, info, and debug.
Changes default from info to error.
Signed-off-by: umohnani8<EMAIL_ADDRESS>

@mrunalp @runcom PTAL

/test all

Squash PRs and then fix travis and LGTM

/test all

/test e2e_rhel

/test e2e_rhel

tests pass. @mrunalp @runcom PTAL

LGTM


Add napari plugin

Checklist

[X] I've given this PR a concise, self-descriptive, and meaningful title
[X] I've linked relevant issues in the PR body
[X] I've applied the relevant labels to this PR
[ ] I've added relevant tests for my contribution
[ ] I've updated the documentation and/or added correct docstrings
[ ] I've assigned a reviewer
[X] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Description
The goal of this PR is to replace the FSLeyes plugin with a plugin for napari.
TODO

Determine how the installation should be done by the users
Update documentation
Add docstrings to the plugin code
Nice to have: add tooltips to buttons

How to test:

~Follow the steps to install ADS~
~Once ADS is installed, follow the instructions starting from step 5 of https://github.com/axondeepseg/napari-plugin/blob/main/README.md~

New instructions:
git clone https://github.com/axondeepseg/axondeepseg.git ads_napari
cd ads_napari
git checkout sia/add_napari_plugin
conda env create -n ads_napari
conda activate ads_napari
pip install -e . plugins/
napari

Linked issues
Resolves #681, resolves #404

@Stoyan-I-A I've made a few minor changes which now substantially simplify the installation procedure.
To install from this branch, all one needs to do is follow the basic ADS installation procedure, with one minor change during the pip install step.
git clone https://github.com/axondeepseg/axondeepseg.git ads_napari
cd ads_napari
git checkout sia/add_napari_plugin
conda env create -n ads_napari
conda activate ads_napari
pip install -e . plugins/

And then run napari as usual.
Would you mind testing it out on your end to see if it works as seamlessly as it does for me?

The tests are failing due to timeouts from long conda resolve times, but it doesn't appear to be due to my changess a the "passing" green checkmarks for 39329c0 just before my commits only checked the readthedocs build for some reason, whereas mine are running all the tests. I also found locally during my testing that it was taking quite a while to resolve the envs, which I am guessing are from the replacement of fsleyes to napari in the conda reqs. I recall we had a similar issue when we introduce fsleyes in the environment file, and after playing around for a long time, ended up needing to "fix" certain other dependency versions in order to need less conflict resolutions between dependencie.

I think to resolve the very long package resolution time, we may need to resort in implementeding mamba instructions per #680. I just tried locally and the installation of this branch took lest than a minute with mamba, the only caveat being that I had to install mambaforge which overrides the default conda in the terminal path, which would be annoying (very) for user with already existing environments in their conda install. The need for a way around this is partly why I stalled #680, so we may need to explore alternative install instsructios (eg see what other packages in the lab are doing and if we can leverage some of their work)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1175

Relevant Lines:
1316

💛  - Coveralls

@Stoyan-I-A Cool! I didn't think of testing it with the pip install instead - great idea! And now the tests pass.
I'll test it locally too now for me to make sure it runs the same.

@mathieuboudreau I have tested your install instructions and they worked on my side.

I've made changed the state of this branch to active on ReadTheDocs, so now the documentation will build for each push to this branch. You can now preview the documentation for this branch here: https://axondeepseg.readthedocs.io/en/sia-add_napari_plugin/

This documentation section, https://axondeepseg.readthedocs.io/en/sia-add_napari_plugin/documentation.html?highlight=fsleyes#graphical-user-interface-gui, needs to be updated. I can write something up. One thing we'll need to do, either in this PR or open an issue for, is create a YouTube tutorial for the napari plugin like we did for our FSLeyes one: https://www.youtube.com/watch?v=ImElcp9_k6Y

I've updated most of the documentation for napari.
The only section I didn't change is the manual segmentation one, https://axondeepseg.readthedocs.io/en/sia-add_napari_plugin/documentation.html?highlight=fsleyes#manual-correction-of-segmentation-masks, because I don't quite know how to use the manual segmentation tools in napari yet, and also his detailed GDoc will also need to be changed: https://docs.google.com/document/d/1S8i96cJyWZogsMw4RrlQYwglcOWd3HrM5bpTOJE4RBQ/edit?usp=sharing

Actually, not changed, but we need to create a new GDoc for the napari instructions (we'll want to keep the old doc so that older versions of the documentation still point to the FSLeyes GDoc)

@Stoyan-I-A I've added docstrings in the plugin for all the classes/methods, but could use your help in ensuring that the information is correct since you wrote the code.

For the tooltips, if you think it will take some time to implement, I'd say let's open issues for them so that we can release this update quicker.
Besides that, from your initial to-do list, I think we're only really missing instructions for the manual segmentation, and then could un-draft this PR for review.

Thank you @mathieuboudreau for adding the changes. I will look at them in the next few days.

I changed some of the docstrings. I mostly removed some text because I found it was either redundant OR that it was too long and could become a risk if the code is modified in the future and the dev forgets to update the docstring

I changed some of the docstrings. I mostly removed some text because I found it was either redundant OR that it was too long and could become a risk if the code is modified in the future and the dev forgets to update the docstring

Thank @Stoyan-I-A ! Yes I felt that too, I cleaned a lot of them up beforehand so sorry I missed some of the verbose ones!

@Stoyan-I-A I've written the section on manual segmentation using the Napari plugin in the documentation, and also recorded a short video tutorial. I've opened an issue for the tooltips feature you mentionne (#731).
I think the PR is now ready for review. Although you can't approve his PR (you created it), if you could review the parts I've added and give written approval, I'll review your plugin code and approve this PR (I only expect minor suggestions, from my earlier pass, and generally using it).

Thank you @mathieuboudreau. I will look at it in the upcoming days.

I checked the updated documentation. About the video: we have a youtube channel for AxonDeepSeg (https://www.youtube.com/@axondeepseg8899). Would it be possible to move the video over there? It is currently uploaded on the neuropoly youtube channel.
The rest looks good to me. And thank you for creating a new video tutorial!

About the video: we have a youtube channel for AxonDeepSeg (https://www.youtube.com/@axondeepseg8899). Would it be possible to move the video over there? It is currently uploaded on the neuropoly youtube channel.

If I recall, we (the lab, internally) made the decision a year or two ago to stop using the individual "software project" Youtube videos, and centralize all new uploaded to the NeuroPoly Youtube channel. So I think the current SOP is still to upload to the common Neuropoly channel, we just never deleted the old software-specific ones.


Installation Instructions Fail to Run

Describe the bug
Following the README's installation instructions (from source), I receive the following error at npm start:
deploy@personal-prd-www01:/var/www/gallery/pigallery2-master$ npm start

><EMAIL_ADDRESS>start /var/www/gallery/pigallery2-master
> node ./backend/index

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '/var/www/gallery/pigallery2-master/backend/index'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `node ./backend/index`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/deploy/.npm/_logs/2019-06-25T21_19_24_245Z-debug.log

I attempted sudo npm i -g typescript and node-ts, but neither helped.
I even attempted to globally install gulp (as the build-release script fails without it - you might want to consider adding this to your instructions, as well).  This script fails as well:
deploy@personal-prd-www01:/var/www/io/thevaughans/gallery/pigallery2-master$ npm run build-release

><EMAIL_ADDRESS>build-release /var/www/io/thevaughans/gallery/pigallery2-master
> gulp build-release

[21:21:47] Failed to load external module ts-node/register
[21:21:47] Error: Cannot find module 'ts-node/register' from '/var/www/io/thevaughans/gallery/pigallery2-master'
[21:21:47] Failed to load external module typescript-node/register
[21:21:47] Error: Cannot find module 'typescript-node/register' from '/var/www/io/thevaughans/gallery/pigallery2-master'
[21:21:47] Failed to load external module typescript-register
[21:21:47] Error: Cannot find module 'typescript-register' from '/var/www/io/thevaughans/gallery/pigallery2-master'
[21:21:47] Failed to load external module typescript-require
[21:21:47] Error: Cannot find module 'typescript-require' from '/var/www/io/thevaughans/gallery/pigallery2-master'
[21:21:47] Failed to load external module @babel/register
[21:21:47] Error: Cannot find module '@babel/register' from '/var/www/io/thevaughans/gallery/pigallery2-master'
[21:21:47] Local gulp not found in /var/www/io/thevaughans/gallery/pigallery2-master
[21:21:47] Try running: npm install gulp

Is there a dependency or step I'm missing to support TypeScript properly?  I do not normally use TS with my Node.js work.
Enviroment (please complete the following information):

OS: Ubuntu 16.04.6 LTS
Node: v10.16.0
NPM: 6.9.0

Used app version: Compiled from source

Hi,
you should need to install anything globally (not even gulp). If you run the npm scripts, it will use the locally installed packages.
You first error means that the .ts files files are not compiled to .js (it cannot find index.js).
(And most likely you are also missing the angular build too, but you would have that error at a later point)
there are 2 way of building the app:

npm install

it installs and builds everything. It is the default way of doing it. (This is how the heroku demo is deployed)

It install all dev. dependencies too. If you would like to avoid that, you can:

run npm install and then npm run build-release.

You can do it on a separate computer. It will create a release folder (and probably also zips that folder too)

You can observe that  in the release folder,  you have only .js files and the new package.jsondoes not contain the dev. dependencies anymore.

you can copy that folder and deploy the app (on you deployed machine you should also run the npm install )
This is how the releases are created. It is a more efficient way of deploying the app.

I hope it helps.
Best,
Patrik

Hey Patrik,
While building a more verbose response, I think I found the issue.  The npm install function is currently being killed internally.
Here are my exact steps, to the point of install.  You can see the not-so-helpful killed statement buried in the installer's status on the left at the very end:
deploy@personal-prd-www01:/var/www/gallery$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial
deploy@personal-prd-www01:/var/www/gallery$ node -v
v10.16.0
deploy@personal-prd-www01:/var/www/gallery$ npm -v
6.9.0
deploy@personal-prd-www01:/var/www/gallery$ wget https://github.com/bpatrik/pigallery2/archive/master.zip
--2019-06-26 17:48:38--  https://github.com/bpatrik/pigallery2/archive/master.zip
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/bpatrik/pigallery2/zip/master [following]
--2019-06-26 17:48:38--  https://codeload.github.com/bpatrik/pigallery2/zip/master
Resolving codeload.github.com (codeload.github.com)... <IP_ADDRESS>
Connecting to codeload.github.com (codeload.github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 27354910 (26M) [application/zip]
Saving to: ‘master.zip’

master.zip                             100%[=========================================================================>]  26.09M   136MB/s    in 0.2s

2019-06-26 17:48:39 (136 MB/s) - ‘master.zip’ saved [27354910/27354910]

deploy@personal-prd-www01:/var/www/gallery$ unzip master.zip
Archive:  master.zip
1bf538f818e11b50e2a08614c0fe826944c69312
   creating: pigallery2-master/
  inflating: pigallery2-master/.editorconfig
   creating: pigallery2-master/.github/
   creating: pigallery2-master/.github/ISSUE_TEMPLATE/

### ... redacted for brevity ###

  inflating: pigallery2-master/test/e2e/tsconfig.e2e.json
  inflating: pigallery2-master/tsconfig.json
  inflating: pigallery2-master/tslint.json
deploy@personal-prd-www01:/var/www/gallery$ cd pigallery2-master/
deploy@personal-prd-www01:/var/www/gallery/pigallery2-master$ npm install
Killed   ..........] / extract:gulp-json-modify: sill extract<EMAIL_ADDRESS>extracted to /var/www/gallery/pigallery2-master/node_modules/.staging/gulp-json-modify-df7

Running with a higher verbosity results in the following:
deploy@personal-prd-www01:/var/www/gallery/pigallery2-master$ npm --verbose install
npm info it worked if it ends with ok
npm verb cli [ '/usr/bin/node', '/usr/bin/npm', '--verbose', 'install' ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb npm-session c99e761ce609c79f
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm timing stage:loadCurrentTree Completed in 34ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 2082ms
npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 2823ms
npm timing stage:loadIdealTree Completed in 5863ms
npm timing stage:generateActionsToTake Completed in 1346ms
npm verb correctMkdir /home/deploy/.npm/_locks correctMkdir not in flight; initializing
npm verb lock using /home/deploy/.npm/_locks/staging-1b5c9c2eeadf1728.lock for /var/www/gallery/pigallery2-master/node_modules/.staging
npm timing audit submit Completed in 1734ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 1741ms
npm timing audit body Completed in 33ms
Killed   ..........] - extract:gulp-json-modify: sill extract<EMAIL_ADDRESS>extracted to /var/www/gallery/pigallery2-master/node_modules/.staging/gulp-json-modify-df7

I'm not sure if that helps.  This seems to be a custom script failing without error, maybe?  Hard to say.

Sorry for the double post - but I think I found the issue.  I think my VM is running out of memory, as the script failure is happening in different points.
This seems to be a poor error message on NPM's part and not any issue with your code.  Thanks for the help!  I'll go ahead and close this one.

In this case I can recommend you using option 2 and doing the npm install and npm run build-release in a separate machine. Afterwards the npm install with the release version should use less memory.


Python 3.12 is not supported.

the imp module has been replaced with  importlib in Python 3.12.

@soimort It is possible to make this repository maintained It possible I'd like to get it to maintaine it :-)


v6.1.2-1.0.0: Optimizations failure - Unexpected token: operator (>)

Hi Pierre,
thank you for your work and effort in making nested fields available in Kibana.
Unfortunately it fails when optimizing JavaScript/caching browser bundles.
Do you have an idea what's happening?
I found some resources saying that babel do not run correctly or do not run the time it is intended to be run.
bin/kibana-plugin install file://<path-to>/nested-fields-support-6.1.2-1.0.0.zip
Attempting to transfer from file://<path-to>/nested-fields-support-6.1.2-1.0.0.zip
Transferring 43344901 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Optimizing and caching browser bundles...
Plugin installation was unsuccessful due to error "Optimizations failure.
   5183 modules

    ERROR in commons.bundle.js from UglifyJs
    Unexpected token: operator (>) [commons.bundle.js:251028,47]
"

I am running ElasticSearch and kibana both in version 6.1.2:
bin/kibana --version
6.1.2

bin/elasticsearch --version
Version: 6.1.2, Build: 5b1fea5/2018-01-10T02:35:59.208Z, JVM: 1.8.0_131

Any help is appreciated! :-)

Unfortunately an error appears "SourceFormat is undefined".

Tried with latest release 6.1.2-1.0.2

I see the issue...

Released... please verify that 1.0.3 works for you. If so, please close this issue.
Thanks!

Very good 👍 Thank you!


How Dose Mods Work?

What is your question?
the title says it

It's to play mods without downloading 200mb or using source.

??

if you import your mod (or any downloadable mod and their unzipped folder) it allows you to play that mod
Example: https://gamebanana.com/mods/365489
download and unzip the file then put it in the mods folder.
also a tutorial: https://www.youtube.com/watch?v=4Ql4CqFauSY

I think you're new onto this mods thing.
Mods are obviously fnf mods that can be installed with Psych Engine 0.5 or higher, to do this you must have a mod that has only the files from the mods folder and not containing an executable and "assets".
Paste the folder that contains all the files and then put it onto your psych engine "mods" folder. Done.

it didn't work

skill issue

For softcoded mods, you need to place the mod folder into mods/ and it should just load in, make sure though that you go into the mods section within the game itself and click 'enable all' on the mod you want to use as there might be assets in there that change other things besides just new songs


With global illumination off unlit areas are monochrome for DM

Foundry 0.7.8
D&D 5th 1.2.0
Perfect Vision 1.2.13
I am finding that when Global Illumination is off, and no token is selected, unlit areas of the map are monochrome. This is with Improved DM vision on or off,

When Global Illumination is turned on the map displays correctly

I still can't reproduce it. Are all other modules disabled? Errors in the console?

I found the culprit. It's MidiQOL for some reason. Not sure how that affects vision though?

I managed to reproduce it when I enabled Midi QOL's Players control owned hidden tokens. Do you have this option enabled?

Great that's it! Thanks for tracking that down

I now know what the problem is. I'm going to report it to the Midi QOL devs. This bug could break other modules as well.


Nuxt 3 video.js support

Environment
nuxt 3 fresh project where videos stored in assets/video/**.mp4
Reproduction
install video.js and follow this setup https://stackoverflow.com/questions/73961731/import-video-js-into-nuxt-js-application-not-working
Describe the bug
I'm not able to find how to use link in video src that comes from props and use like dynamically.
Additional context
I want a way that I can use nuxt 3 assets folder file dynamically to play a video from video js.
I used some thins like this:
`const videosImport = import.meta.glob("@/assets//.mp4");

sources: [{
src: videosImport["/assets/video/publish.mp4"],
type: "video/mp4",
}]
`
After that also I'm getting the error like video file is not readable by the module
Logs
No response

See https://vitejs.dev/guide/features.html#glob-import.
We can track improving this in Nuxt in https://github.com/nuxt/nuxt/issues/14766.


feat: Assist passthrough

Closes #12  and closes #11
I was able to test the VUI portion, but due to some ongoing alpha issues, was not able to test the GUI portion.
Adds the ability to directly pass a request to Home Assistant via their Assist API. This allows the plugin to retain feature parity without additional dev work in the plugin.
Also removes the dist/build folders and adds a basic Python .gitignore file.
Tested locally in containers and working on testing on my Mark 2 dev kit.
Fixes a bug when using ovos-bus-client where the device list was being passed to the Message as a list, not a dict.

Replaced by #20


Removes some gate folks, adds @deepthiskumar

Needs redeploy with these changes

!ci-build-me

!approved-for-mainnet

!ci-build-me


Hazard: Perilous Flash Flood

This hazard has a item "Filth Fever": I'm wondering if this item is wrong (maybe from an other hazard ?).
The hazard is from the gamemastery guide, but I did not find any filth fever in this hazard (page 80 f.).

Repulsive refuse, the third bullet point.
"Additionally, creatures who come into contact with the flood waters are exposed to filth fever (DC 20 Fortitude, Bestiary 258)"


gowin_pack hangs on OSER10 - ELVDS_OBUF combo on Tang Nano 9K

Hi, I'm recently trying to have HDMI output on Gowin Tang Nano 9K using project apicula, but I encountered the problem of gowin_pack hangs and falling into PDB, saying something like this:
Info: [ 82567,  82568) |
Info: [ 82568,  82569) |

8 warnings, 0 errors

Info: Program finished normally.
SPINE5 SPINE13 not found in tile 1 47
> /oss-cad-suite/lib/python3.11/site-packages/Apycula-0.10.1.dev5+g153fc97-py3.11.egg/apycula/gowin_pack.py(1236)route()
-> continue
(Pdb)

I wonder what the problem might be? This issue https://github.com/YosysHQ/nextpnr/issues/1147 feels quite similar.
The verilog code, cst and makefile are at https://gist.github.com/regymm/93aa01486ad10a185976f2e665151e66
Note that in verilog code line 43/44, I've tried multiple clock configurations, including clkpix/clk_250, clkpix/clk_TMDS, but all have the same problem.
Btw, I'm kinda curious if there's any existing HDMI demo using the open-source toolchain? I should be able to use 25M/250M and manually write a TMDS decoder as in the fpga4fun example, but it won't pass timing (in Gowin IDE, the Fmax is around ~180M and HDMI won't display).

I don’t think that we will be able to surpass Gowin IDE - it is like a standard with which we compare our developments.
But to the point: OSER10 ELVDS works in the new router architecture - Himbaechel, in just two hours I will add the example oser10-elvds-tangnano9k to the standard apicula distribution.
https://github.com/YosysHQ/apicula/assets/6075465/cd6e633e-8bcb-4ca4-addc-5afcd78c75a9
Try your design with the apicula master branch and the nextpnr master branch (you can see how to install it in https://github.com/YosysHQ/apicula/issues/220#issuecomment-1876682997).
If your design still can’t compile, then let me know and we’ll figure it out.

Oh I didn't mean apicula's performance, in Gowin IDE my 250 MHz encoder logic can only run at 180 MHz, which is not even close. So maybe Gowin just expects us to use OSER10.
Can I ask how to install apicula master branch? The makefile seems to require the Gowin IDE and fuzzing. Do I need to do this (instead of using a pre-built library, etc)?
I tried using nextpnr master branch with himbaechel, and apicula of version pip install apycula, and the design still has the same problem.

If you already have a master nextpnr, then you will most likely be able to assemble your own design.
Try calling the desired router:
nextpnr-himbaechel --json $< --write $@ --device GW1NR-LV9QN88PC6/I5 --vopt family=GW1N-9C --vopt cst=$(filter-out $<,$^)

And in the .CST file, specify each pin from the differential pair separately:
IO_LOC "tmds_d_p" 71;
IO_PORT "tmds_d_p" PULL_MODE=NONE DRIVE=8;
IO_LOC "tmds_d_n" 70;
IO_PORT "tmds_d_n" PULL_MODE=NONE DRIVE=8;

(yes, I know about Gowin syntax, but I’m very bad at writing parsers - I’m much worse at it than researching the insides of a chip. Maybe I’ll improve it in the future.)

Oh I should have used nextpnr-himbaechel. Now HDMI is working. Thanks for your quick help!

Cool! If you'd like to contribute a working HDMI example it'd be much appreciated.

Of course! The code is based on fpga4fun's example, at https://github.com/FPGAOL-CE/user-examples/tree/main/hdmi . I'm using this dockerized toolchain https://github.com/FPGAOL-CE/osstoolchain-docker-things/blob/master/gowin/Dockerfile.gowin-gocd . HDMI clocks are done by generate 25M and 250M clk from PLL, then divide the 250M by 2 using a register. That's the closest I can get to without CLKDIV. Since the 125M drives only the OSER10, this untimed part is not likely to fail.


make command works with root permissions only

Can someone look into the issue? I am using Fedora 33 and had  created a Unix group called docker and add users to it, so ideally it should not ask say permission denied.
$ make
docker run --rm -v "/home/vagrant/i-probably-didnt-backdoor-this:/app" -w /app -u "1000:1000" \
	rust@sha256:8463cc29a3187a10fc8bf5200619aadf78091b997b0c3941345332a931c40a64 \
	cargo build --release --locked --target=x86_64-unknown-linux-musl
error: Permission denied (os error 13) at path "/app/targetzF01pS"
make: *** [Makefile:2: build] Error 101

I might be completely wrong here. Just thought of reporting this anyway :+1:

hi!
it seems the docker part of it is working fine, could you check if your /home/vagrant/i-probably-didnt-backdoor-this folder is writable by uid 1000? /app/targetzF01pS sounds weird but I'm assuming this is cargo trying to create the /app/target/ folder and failing due to permission problems on /app/.


More than one Mount point

Do you think it's possible to add more than one instance in a single app?
For example
/blog
/wiki
?

Hi! Currently definetly no, if you want it to be 2 different blogs.  It would require some changes in the database schema.
Would you like to have to different set of users for these blog?

no same users


Mapbox distance indicator in bottom right seems to be off when zoomed out very far

Spotted by @nickhough :

Seems to be showing 50km when the actual distance of that line would actually be much much larger than that
I'm not sure why, or how to fix it, and it's not super high priority because the scale is probably mostly useful at a very zoomed-in view, but wanted to document this anyway

@danielcolinjames it seems that is a known issue: https://github.com/alex3165/react-mapbox-gl/issues/720, apparently switching to mapboxgl.ScaleControl might fix this

there's also a z-index thing happening:


Pthread_t change broke musl

Using latest libc causes issues on musl because of this:
error[E0308]: mismatched types
   --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/jobserver-0.1.13/src/lib.rs:665:40
    |
665 |                     libc::pthread_kill(self.thread.as_pthread_t(), libc::SIGUSR1);
    |                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected *-ptr, found u64
    |
    = note: expected type `*mut imp::libc::c_void`
               found type `u64`

It's because pthread_t type in libc changed to correct one but libstd still use wrong one.

Even with https://github.com/rust-lang/rust/pull/61428 merged stable and beta will remain broken.
To handle it gracefully libc would have to detect pthread_t type exported by libstd and use the same.

I don't think this is a libc bug. Neither libc nor libstd promise that libstd::RawPthread and libc::pthread_t are type aliases to the exact same type. IIUC, this is actually intended to not be the case by design.
That is, the bug here is in the user code that assume that passing a libstd::RawPthread to a libc API taking a libc::pthread_t is portable code. It is not. The portable way of interfacing a libstd::RawPthread with a libc::pthread_t is, AFAICT, to use mem::transmute.

Having said that, it is unclear to me how to fix this, or whether it is worth fixing. How much user code is impacted by this ?

At least everything that depends on jobserver won't build: https://crates.io/crates/jobserver/reverse_dependencies
Cargo is one of listed crates so this is very likely to break building of Cargo for musl toolchain unless there is workaround applied to jobserver.

IIRC a workaround to jobserver was already applied ?

I don't know if that was the "proper" workaround, AFAICT the proper workaround is just using a mem::transmute here, although for the time being at least using a raw_pthread as _ should work as well since an usize can be cast into a *mut c_void.

IIRC a workaround to jobserver was already applied ?

Not for this issue:
https://github.com/alexcrichton/jobserver-rs/blob/15b93a7caac18dd9aedd686e7c8381cef3fd450c/src/lib.rs#L667

Indeed, I might have confused jobserver with some other project. See https://github.com/alexcrichton/jobserver-rs/pull/14

@mati865 so a new version of jobserver has been released with a fix, could you let me know whether that solves this issue ?

It works, thanks.


Add Aff/Neg badge to speech in speech manager if applicable

Would be nice to have red aff badge, or blue neg badge if the speech is tied to a side

These changes are in the speechEnhance branch. will merge soon


Rest API to Revoke OAuth 2.0 Access Token by Administrator

Describe the improvement
WSO2 IS doesn't have a Rest API exposed to revoke an OAuth 2.0 access token by an administrator.
Additional context
In general all the end-user related operations, where end-users are acting on their data, should have a corresponding Rest API for administrators to do the same on behalf of users.
E.g. session termination (having), account linking (don't have), enrolling 2nd factor devices (don't have), etc.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!

Account linking is going to be provided with https://github.com/wso2-enterprise/iam-product-management/issues/328


Request LICENSE

Are you planning to add a License?

Good idea
2.0 inc, and licence will be added.
Thx u for pull request.


Allow assert_no_accessibility_violations to accept block

There might be cases where you wish to see if a page raises any
violations. Simply visiting a page with violations will fail, but it
could be nice to declare that in the test itself.
One possible use-case could be visiting a page that requires no
user interactions. A controller level test might cover the markup, but
the system level test would be created for testing accessibility
violations.

One possible use-case could be visiting a page that requires no user interactions.

The Usage section of the README mentions that accessibility violations are audited after calls to visit.
Would calling assert_no_accessibility_violations after the visit call have the same outcome?
class MySystemTest < ApplicationSystemTestCase
  test "Page raises no accessibility violations" do
    visit root_path

    assert_no_accessibility_violations
  end
end

What about this particular motivating use case makes it better to call with a block?

@seanpdoyle you're right, we don't need a block. This is making me realize what I'm actually looking for is a way to improve the assertion itself. The following tests will raise the same error if the page has any violations.
class MySystemTest < ApplicationSystemTestCase
 test "Page raises no accessibility violations" do
   visit page_with_violation

   assert_no_accessibility_violations
 end

 test "Page also raises no accessibility violations" do
   visit page_with_violation
 end
end

Instead of raising the following
Found 1 accessibility violation:

1) heading-order: Heading levels should only increase by one (moderate)
    https://dequeuniversity.com/rules/axe/4.5/heading-order?application=axeAPI
    The following 1 node violate this rule:

        Selector: h4
        HTML:
Let’s sign in to your account

        Fix any of the following:
        - Heading order invalid

Invocation: axe.run({:exclude=>[]}, {}, callback);

I would expect a call to assert_no_accessibility_violations to return something like "Expected page to have no accessibility violations but found 1".

@stevepolitodesign what you're describing sounds a lot like axe-core-rspec, the underlying package that powers capybara_accessibility_audit. That gem provides a be_axe_clean matcher to manually invoke.
This gem's aspirations are a little different. By limiting the programming interface and keeping the gem's surface area extremely minimal, capybara_accessibility_audit forces suites to address violations.
If each test were required to invoke a Minitest assertion or Spec matcher, it'd be easy to omit or forget the call.
There's the configuration escape-hatches to exclude violations, but that's largely an interface for applications to gradually adopt the gem.
Once those violations are addressed, those configurations should be removed. That flexibility shouldn't be re-introduced.

@stevepolitodesign what you're describing sounds a lot like axe-core-rspec, the underlying package that powers capybara_accessibility_audit. That gem provides a be_axe_clean matcher to manually invoke.

Thank you for pointing this out. That's essentially what I'm looking for. I'm comfortable closing this pull request now that I have a better understanding of this gem's aspirations, and its underlying dependencies.
I do wonder if it's worth updating the README to highlight my original use case, and how one could solve for that with axe-core-rspec or this minitest alternative


Add custom definitions for EditableMesh

closes #1191
Pending discussion item: Do we want to replace number with VertexId or FaceId (or equivalent) where applicable? (Original discussion).

LGTM, love it! beat me to the punch


[improvement](fe and broker) support specify broker to getSplits, check isSplitable, file scan for HMS Multi-catalog

Proposed changes
Merge #24830, #25453, #27122 into Branch-2.0

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

run buildall


Estimate requested features during last sprint call

cphate color picker: have the list of all the neurons in the color picker, we can select a single neuron, once the color for this is changed the change is reflected in the cluster spheres that contain this neuron.
color pickers: add 5 most recent used colors.

cphate color picker (8h)
most recent color pickers (8h)


AttributeError: 'SpatialTransformer' object has no attribute 'is_placeholder'

I was trying to implement Spatial Transformer Layer in my Code but I am getting this error. Is there any solution for it ?
`
def locnet():
b = np.zeros((2, 3), dtype='float32')
b[0, 0] = 1
b[1, 1] = 1
W = np.zeros((64, 6), dtype='float32')
weights = [W, b.flatten()]
locnet = Sequential()
    locnet.add(Conv2D(16, (7, 7), padding='valid', input_shape=(128, 64, 1)))
    locnet.add(MaxPooling2D(pool_size=(2, 2)))
    locnet.add(Conv2D(32, (5, 5), padding='valid'))
    locnet.add(MaxPooling2D(pool_size=(2, 2)))
    locnet.add(Conv2D(64, (3, 3), padding='valid'))
    locnet.add(MaxPooling2D(pool_size=(2, 2)))

    locnet.add(Flatten())
    locnet.add(Dense(128))
    locnet.add(Activation('elu'))
    locnet.add(Dense(64))
    locnet.add(Activation('elu'))
    locnet.add(Dense(6, weights=weights))

    return locnet

def train(run_name, start_epoch, stop_epoch, img_w):
    # Input Parameters
    img_h = 64
    words_per_epoch = 8000
    val_split = 0.2
    val_words = int(words_per_epoch * (val_split))

    # Network parameters
    conv_filters = 16
    kernel_size = (3, 3)
    pool_size = 2
    time_dense_size = 32
    rnn_size = 512
    minibatch_size = 32

    if K.image_data_format() == 'channels_first':
        input_shape = (1, img_w, img_h)
    else:
        input_shape = (img_w, img_h, 1)

    fdir = os.path.dirname(get_file('wordlists.tgz',
                                    origin='http://www.mythic-ai.com/datasets/wordlists.tgz', untar=True))

    img_gen = TextImageGenerator(monogram_file=os.path.join( 'bangla_wordlist_mono_clean.txt'),
                                 bigram_file=os.path.join(fdir, 'wordlist_bi_clean.txt'),
                                 minibatch_size=minibatch_size,
                                 img_w=img_w,
                                 img_h=img_h,
                                 downsample_factor=(pool_size ** 2),
                                 val_split=words_per_epoch - val_words
                                 )
    act = 'relu'
    input_data = Input(name='the_input', shape=input_shape, dtype='float32')
    input_data=(SpatialTransformer(localization_net=locnet(),
                                 output_size=(128, 64)))(input_data)
    inner = Conv2D(conv_filters, kernel_size, padding='same',
                   activation=act, kernel_initializer='he_normal',
                   name='conv1')(input_data)
    inner = MaxPooling2D(pool_size=(pool_size, pool_size), name='max1')(inner)

    inner = Conv2D(conv_filters, kernel_size, padding='same',
                   activation=act, kernel_initializer='he_normal',
                   name='conv2')(inner)
    inner = MaxPooling2D(pool_size=(pool_size, pool_size), name='max2')(inner)

    conv_to_rnn_dims = (img_w // (pool_size ** 2), (img_h // (pool_size ** 2)) * conv_filters)
    inner = Reshape(target_shape=conv_to_rnn_dims, name='reshape')(inner)

    # cuts down input size going into RNN:
    inner = Dense(time_dense_size, activation=act, name='dense1')(inner)

    # Two layers of bidirectional GRUs
    # GRU seems to work as well, if not better than LSTM:
    gru_1 = GRU(rnn_size, return_sequences=True, kernel_initializer='he_normal', name='gru1')(inner)
    gru_1b = GRU(rnn_size, return_sequences=True, go_backwards=True, kernel_initializer='he_normal', name='gru1_b')(inner)
    gru1_merged = add([gru_1, gru_1b])
    gru_2 = GRU(rnn_size, return_sequences=True, kernel_initializer='he_normal', name='gru2')(gru1_merged)
    gru_2b = GRU(rnn_size, return_sequences=True, go_backwards=True, kernel_initializer='he_normal', name='gru2_b')(gru1_merged)

    # transforms RNN output to character activations:
    inner = Dense(img_gen.get_output_size(), kernel_initializer='he_normal',
                  name='dense2')(concatenate([gru_2, gru_2b]))
    y_pred = Activation('softmax', name='softmax')(inner)
    # Model(inputs=input_data, outputs=y_pred).summary()

    labels = Input(name='the_labels', shape=[img_gen.absolute_max_string_len], dtype='float32')
    input_length = Input(name='input_length', shape=[1], dtype='int64')
    label_length = Input(name='label_length', shape=[1], dtype='int64')
    # Keras doesn't currently support loss funcs with extra parameters
    # so CTC loss is implemented in a lambda layer
    loss_out = Lambda(ctc_lambda_func, output_shape=(1,), name='ctc')([y_pred, labels, input_length, label_length])

    # clipnorm seems to speeds up convergence
    sgd = SGD(lr=0.02, decay=1e-6, momentum=0.9, nesterov=True, clipnorm=5)

    model = Model(inputs=[input_data, labels, input_length, label_length], outputs=loss_out)

    # the loss calc occurs elsewhere, so use a dummy lambda func for the loss
    model.compile(loss={'ctc': lambda y_true, y_pred: y_pred}, optimizer=sgd)`

Could you post your error output and your tensorflow & keras versions so I can take a look at your problem?

Thank you very much for your early reply
Keras Version: 2.0.2
Tensorflow Version: 1.3.0
Error:
Traceback (most recent call last):   File "bangla_image_ocr.py", line 604, in <module>     train(run_name, 0, 40, 128)   File "bangla_image_ocr.py", line 580, in train     model = Model(inputs=[input_data, labels, input_length, label_length], outputs=loss_out)   File "/home/codehead/anaconda2/lib/python2.7/site-packages/keras/legacy/interfaces.py", line 88, in wrapper     return func(*args, **kwargs)   File "/home/codehead/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 1566, in __init__     if layer.is_placeholder: AttributeError: 'SpatialTransformer' object has no attribute 'is_placeholder'

Thank you, I'd try to reproduce the error using newer versions of tf and keras to see if the problem is caused by compatibility issues.

@hello2all May I know which versions did you use for this ?

If I recall correctly, tensorflow 1.0 and keras 2.0

Thanks ! Please let me know if you have found any solution for this problem .

@codeheadshopon There is a compatibility issue with the newest version of Keras. However, there is an easy fix to it: in spatia_transformer.py, delete line 37
self.constraints = self.locnet.constraints
After deleting the line, my model was able to successfully compile with no error.
This is tested with:
Tensorflow 1.3.0
Keras 2.0.8

Didn't work with me.
I updated my keras version to 2.0.8
But still getting the same error.

In the newer versions of Keras, there has been an update on the method to build customized layer. Since I can not re-create the exact error you have been experiencing, I encourage you to look into the Keras documentation and modify the layer initialization accordingly.
I hope this is helpful for you.


add get_insider_transaction_reported

add get_insider_transaction_reported to fetch information here

That class already has a data object, use that. And expose function via Ticker class.

That class already has a data object, use that. And expose function via Ticker class.

Sure, could you take a look on the latest commit? thanks

I looked and saw you ignored my review.
https://github.com/ranaroussi/yfinance/blob/88525abcbd9c1ab32b893d678a6c4fa8686bdf8e/yfinance/scrapers/holders.py#L10C1-L10C1

Looking good. But please add unit test(s) to tests/ticker.py. Purpose is to fail if someone in future breaks your code.
Then to conform to #1084 if you don't mind:

rebase to dev branch (plenty of guides online, or GPT4) and change target to dev
git squash

What's the status of this PR?

Added ut and changed target branch to dev, ready for review

Where's the test?

@ValueRaider Close, please. Implemented at #1772


Execute block - Incorrect merkle trees

Description
We got some scenario can be caused block execution failed by Incorrect merkle trees. For details please refer attached logs:

All nodes are forked, and then one of nodes got Incorrect merkle tree.
All nodes forked.zip
On of node rollback successful, but then continue to execute later block got incorrect merkle tree.
Incorrect MerkleTree.zip
Run lot of vote operation(100 txs), and then node would be timeout first, then would be got Incorrect merkle tree.
Vote-IncorrectMerkleTree.zip

out of date.


[2588] Applications open style fix

Context
Same as before. The new and edit applications open pages are slightly out of line with the prototype
Changes proposed in this pull request

Change the value of the applications_open_from label from "Other" to "On a specific date"

[x] Make sure all information from the Trello card is in here

[x] Attach to Trello card

[x] Rebased master

[x] Cleaned commit history

[x] Tested by running locally

 Applications open: Second option should say "On a specific date"


Make the UI responsive for all devices

Summary
OpenDevin must be responsive for all screen sizes
Motivation
When the screen sizes reduce the tabs like browser, code editor do out of viewport.
Technical Design
Use of media query to adjust the alignment according to screen sizes.

Raised a PR to help tackle this https://github.com/OpenDevin/OpenDevin/pull/677

I'm going to close this as will not do for now because there doesn't seem to be plans to tackle this for a while. We can open a new issue if it's something that a lot of people want.


Cannot query db from psql shell on dev

dev has postgres and a galaxy postgres user, and typing \l in the shell reveals that a db named galaxy does exist but I can't see the relations or tables for it.  It would be a good addition to the scripts to set this up properly.

This just requires the connection string to be stored in .pgpass in the user's home directory.

Closed with #79


Changed How the PortWatcher plots data to avoid plotting data for por…

…ts that have 0 data points stored in their loggers

Codecov Report
Attention: Patch coverage is 82.05128% with 7 lines in your changes missing coverage. Please review.

Project coverage is 90.17%. Comparing base (28c7bbe) to head (1236ab2).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

src/brom_drake/PortWatcher/PortWatcher.py
76.66%
7 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #13       +/-   ##
===========================================
+ Coverage   79.15%   90.17%   +11.01%
===========================================
  Files          41       51       +10
  Lines        1166     1333      +167
===========================================
+ Hits          923     1202      +279
+ Misses        243      131      -112

Flag
Coverage Δ

?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


What does the error "missing required parameter name" mean

Hello,
I am attempting to use the vSphere driver for chef-provisioning.  When I run chef-client, the first VM spins up and converges the recipe without issue.  As soon as it gets to the second VM the chef run dies with the error:
    ====================================================================
Error executing action `converge` on resource 'machine[chef-2]'
    ====================================================================

RuntimeError
------------
missing required parameter name

Resource Declaration:
---------------------
# In /home/chef/.chef/local-mode-cache/cache/cookbooks/my_cookbook/recipes/provision.rb

 46:   machine "chef-#{num}" do
 47:     recipe 'my_cookbook::default'
 48:     attribute %w[foo bar] = baz
 48:   end
 49: end

My provisioning recipe (outside of my vSphere configuration) is simply:
num_servers = 3

1.upto(num_servers) do |num|
  machine "chef-#{num}" do
    recipe 'my_cookbook::default'
    attribute %w[foo bar] = baz
  end
end

This is confusing because the error has the machine name in it, and there is literally no difference between machine one and machine ten.
Changing the above lines to the following allows the VM to spin up without issue:
#1.upto(num_cassandra_servers) do |num|
  machine "chef-2" do
    recipe 'my_cookbook::default'
    attribute %[foo bar] = baz
  end
#end

The same cookbook runs fine in test kitchen minus the provisioning bit.
Any help is greatly appreciated.
Thanks!
EDIT:
To add further to my confusion, if I create each machine individually by editing the machine name, e.g. replace "chef-#{num}" with "chef-1", "chef-2", "chef-3", the modify the recipe to use the loop, running chef again on the already running vms completes without issue.

Hi,
I've seen a couple of similar reports, and I believe the issue may be specific to the vsphere driver. I don't presently have access to vmware infra to repro, but could I trouble you to submit this issue on that project (https://github.com/CenturyLinkCloud/chef-provisioning-vsphere) as well?

Moving to https://github.com/CenturyLinkCloud/chef-provisioning-vsphere/issues/18

Thanks for moving! I just pushed v0.7.1 that fixes this.


Carplay not working with 3.7.0 b2 release

Carplay gives a black screen on the car display and nothing shows up

Created https://github.com/pwn20wndstuff/Undecimus/issues/1583


Chrome doesn't play on Windows

I dunno why, but following (slightly adapted) code, doesn't work on windows with chrome..
Player just stays black, loads, sometimes shows a still picture after long time, RAM consumption goes up drastically.. But no errors.
wasm files are delivered correctly, are not transpiled and have a correct mime encoding delivered by nginx.
import React, { useEffect, useRef, useState } from 'react';
import videojs from 'video.js';
import {
   registerIVSTech,
} from 'amazon-ivs-player';

import wasmWorkerPath from 'amazon-ivs-player/dist/assets/amazon-ivs-wasmworker.min.js'
import wasmBinaryPath from 'amazon-ivs-player/dist/assets/amazon-ivs-wasmworker.min.wasm'

const createAbsolutePath = (assetPath) => new URL(assetPath, document.URL).toString();

export default function AmazonIvsPlayer({ props }) {

  const streamSource = "https://d6hwdeiig07o4.cloudfront.net/ivs/956482054022/cTo5UpKS07do/2020-07-13T22-54-42.188Z/OgRXMLtq8M11/media/hls/master.m3u8"

  let player = null;

   useEffect(() => {
     console.log("absolute path", createAbsolutePath(wasmWorkerPath))

     registerIVSTech(videojs, {
         wasmWorker: createAbsolutePath(wasmWorkerPath),
         wasmBinary: createAbsolutePath(wasmBinaryPath),
     });
     // registerIVSQualityPlugin(videojs)

     player = videojs('amazon-ivs-videojs', {
         techOrder: ["AmazonIVS"],
         controlBar: {
           fullscreenToggle: false,
           pictureInPictureToggle: false
         },
         autoplay: false,
         logLevel: "debug",
         src: streamSource
     }, () => {
        console.log('Player is ready to use!', player);
         player.src(streamSource)
     })

     console.log('Player is ready to use!', player);
     // player.enableIVSQualityPlugin();
   }, [streamSource])

  return (
     <div className="amazon-container text-center">
      <video id="amazon-ivs-videojs" className="video-js vjs-theme-city" controls/>
    </div>
  )
}

All other browsers work completely fine, Safari, FF,... Also chrome on OSX works fine.. Just windows :(

Thanks for the report. Few questions:

What version of Windows & what version of Chrome?
Does this CodePen work for you on Windows Chrome?

https://codepen.io/amazon-ivs/pen/bdc01e977102051eae5fb85482f88276

Do you have any extensions installed or browser flags enabled that could be affecting playback?

Omfg... We found out why there was this strange behaviour..
We were using sentry-react... After removing it, the player works flawelessly... omg, I spent so many hours...
Maybe you should add this to your readme or know issues page.. May help to save someones work time...

@h0jeZvgoxFepBQ2C Glad that you managed to resolve your issue, and thanks for reporting it. People searching for similar issues should see this, so I don't believe we need to further document it.


Authentication Error: When trying to write the data more than 5 yrs into netcdf file

Downscale version: Conventions:  CF-1.7 CMIP-6.2
activity_id:   ScenarioMIP
contact<EMAIL_ADDRESS>data_specs_version: 01.00.30
Python version: Python 3.9
Operating System: Ubuntu

Description
ClientAuthenticationError: Operation returned an invalid status 'Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.'
ErrorCode:AuthenticationFailed
Ran into a deserialization error. Ignoring since this is failsafe deserialization
Traceback (most recent call last):
File "/home/user/my_project_dir/anaconda3/lib/python3.9/site-packages/msrest/serialization.py", line 1509, in failsafe_deserialize
What I Did
I am calculating month Tamax mean and then writing it into netcdff file as I need the downscale data to be fed as input in a model
subset = all_datasets.sel(
lon=slice(25, 45),
lat=slice(-10, 10),
)
mtasmax = subset.resample(time="M").mean()
delayed_obj = mtasmax.sel( time=slice("2025-01-01", "2030-12-31")).to_netcdf('rgrp_yr2_2025_2030.nc',
compute=False)
if I run for 10 years or 5 years or if the notebook is running for quie some time it shows this Client authentication error
can some please in regards to this?
If there was a crash, please include the traceback here.
![image](https://user-images.githubusercontent.com/60099425/192335221-73a2190b-6e68-44c4-9e89-9c1cf0a1d1d4.png)

Thanks for the question and interest in the dataset! Sorry to hear you're having this issue.
This seems to me to be a Microsoft Planetary Computer authentication issue - @TomAugspurger - if you're around - any advice on how to handle this issue?
@devosse1 you might be able to get help by filing an issue or asking for advice from the
https://github.com/microsoft/PlanetaryComputer team & users, by filing an issue or visiting their discussions page

Discussing this at https://github.com/microsoft/PlanetaryComputer/issues/109. I think this can be closed.

sure


Copying and pasting multi-line cell values will paste one line on each cell on DMN Editor's Boxed Expression Editor

During the https://github.com/kiegroup/kie-tools/pull/1850 review, I found some bad behavior when coping and pasting a cell with multiline content.
Case 1.
Only the first line is actually copied and pasted
https://github.com/kiegroup/kie-issues/assets/16005046/bc1ca457-e13d-48cb-b89a-402ab9fabc61
Case 2.
A multiline cell is copied and pasted into multiple cells
https://github.com/kiegroup/kie-issues/assets/16005046/2bb3b9a1-8945-4daa-8e77-338037920930
Please check for CUT and PASTE combination as well

@yesamer Hmmm.... interesting! Just tested on a famous spreadsheet editor and looks like for multi-line content they use a string delimiter, like so:
-------
|  a  |
|  b  |
|  c  |
-------
|  d  |
|  e  |
|  f  |
-------

is pasted as
"a
b
c"
"d
e
f"

so we could do something similar.


data: remove yoyoekta.json

Changes proposed
Deleted yoyoekta.json file after shifting to forms.

Did you mean to close the pull request?


Enable diagnostics via build constraint to prevent from running in tests

Overview
This makes sure diagnostics aren't enabled during go test or unless the release build constraint is enabled. This replaces existing logic that disabled diagnostics by use of config flags.
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

Good point about client tests. There are integration tests in the client repos that we should disable diagnostics for. I will ticket them.


LDAP revocation & wallet

Steering: Proposal Summary
Used to propose a change or addition to Steering.
This is for the Steering work START approval step. Discuss the proposed work or change.
Section 4.1.10 Credential Revocation seems to mix issuer and wallet requirements. Suggest to sharpen the focus and clarify the wallet requirements.
Steering: Publication Summary
Used to present completed work to Steering for approval to publish.
Discuss the work that was completed in reference to the above proposal.  Include any differences from the proposal and why.
use [GitHub Preview](https://htmlpreview.github.io/) to show final state of documents along with pull requests (if needed).

Detailed Description:
observation 1
Section 4.1.10 Credential Revocation says,

Digital Wallet Providers SHALL implement the OCI Directory Service (LDAP)-based mechanism for determining if a Verifiable Credential has been revoked (vc-status-2021-ldap).

This is not precise, as the issuer needs to run LDAP servers, the wallet just needs to be able to call them.
Suggest to reword to sth like,

wallet providers shall implement API calls to the LDAP server of the issuer and check the revocation status

observation 2
I'd also remove the intro sentence, as that's hypothetical and not relevant for audits or implementers. They only need to know what applies NOW.

OCI can potentially support multiple methods for communicating when a Credential has been revoked.

observation 3
Further, the para ends with,

Credential Issuer and Digital Identity providers SHALL implement LDAPS, which is LDAP secured by communication over Transport Layer Security (TLS) protocol.

The CI criteria do not belong in the wallet conformance document.

Triage:

[x] Is Issue appropriate for OCI Architecture
[x]  Assign Size
[x]  Assign Priority
[x]  Assign Label (if needed)
[x]  OCI affected Artifacts Identified
[ ]  Assign Triage - Artifact Version Target (v x.x.x Milestone)
[ ]  Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
[ ]  Create sub-project (if needed)

Affected Parties (help determine Sunrise/Sunset):

[ ] Trading Partners
[x]  Issuers
[x]  Wallet Solutions
[ ]  PI Verification Solutions

Affected OCI Artifact

[ ] Schema Document
[ ] Identity Schema
[ ] ATP Schema
[ ] Issuer Conformance Criteria
[x] Wallet Conformance Criteria
[ ] VRS Solution Conformance Criteria
[ ] Wallet API Specification
[ ] Governance Document
[ ] Conformance Program
[ ] OCI Website
[ ] Internal Process

Change Category (Guides Steering Review)
- Steering/Industry Review

[ ] Business-Level (May affect business operations)
[ ] OCI Governance, Policy or website feature

- Steering/Industry Notification

[ ] Technical-Level (Does not affect business operations)
[ ] OCI Internal Process or Infrastructure

Communication

[ ] Website
[ ]  Newsletter
[ ]  email:
[ ]  Other:

consider impact on issuer criteria @britpayson

relates to https://github.com/Open-Credentialing-Initiative/Digital-Wallet-Conformance-Criteria/issues/76

hold until decision on PR #75

PR &  ticket closed, as merged into https://github.com/Open-Credentialing-Initiative/Digital-Wallet-Conformance-Criteria/issues/76


Error: addImage does not support files of type 'UNKNOWN'

Thank you for submitting an issue to jsPDF. Please read carefully.
Are you using the latest version of jsPDF?
"jspdf": "^1.4.0",
Have you tried using jspdf.debug.js?
Steps to reproduce
I'm doing this in a React stateful component.
  import { background01 } from './../data/forms/n-400/n-400-images/background01.jpg';     makeJsPdf = (q, answer) => {     let doc = new jsPDF();     doc.setFontSize(14);     let imgData = 'data:image/jpeg;base64,background01';     console.log(typeof imgData);     doc.addImage(imgData, 'JPEG', 0, 0, 400, 400);     doc.text(35, 40, answer);     doc.save("first.pdf");   }
It works fine without the image.
Ideally a link too. Try fork this http://jsbin.com/rilace/edit?html,js,output
I tried importing the image code into this jsbin and it didn't respond.
the console logged this error:
"error"
"Script error. (line 0)"
What I saw
Link to error as screenshot
What I expected
I expected the text to be on top of the image like the demo on https://parall.ax/products/jspdf

I learned that I shouldn't try to use the image but use dataURI.
I converted my image to a dataURI using this website:
https://websemantics.uk/tools/image-to-data-uri-converter/

Thank you bro, really really thank you!


Size of node should adapt to content

Example:
# Theorem
## Branch 1
### Step 1
#### $x^2 + y^2$
### Step 2 with a very long long long long long long long long long long
### Step 3
## Branch 2
### Step 1
### Step 2
### Step 3
## Branch 3
### Step 1
### Step 2
### Step 3

Definitely, we need a better layouting algorithm. I created an issue to track progress: https://github.com/dundalek/markmap/issues/11

This is now supported in the new version 0.4.0. It adapts width to the content. By default it truncates long labels and you get result like this:

But you can also turn off truncation in settings and you will get this:


Why are we passing chunksize=0 to AutoForwardDiff rather than using default?

We're explicitly passing in chunksize=0 to AutoForwardDiff everywhere in the codebase; is there a reason for this? Maybe @devmotion @sunxd3 @yebai knows?

Ah, perfect! That was the piece of code I was looking for; thanks!
But exactly, so we should be using chunksize=nothing for default since that's what ADTypes.jl uses (if you do AutoForwardDiff(), then it results in nothing).

There is an argument about always being explicit, but yeah, I think nothing is good (setting chunksize to 0 does feels a bit strange looking from the outside)

But chunksize=0 is more confusing that chunksize=nothing, no?

IIRC that was not touched when moving to ADTypes, so probably a very old design choice. Just using the ADTypes default value for this purpose seems easier.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.13 to before v5.15.24",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f73f7f4da581875f9b1f2fb8ebd1ab15ed634488",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7f54894aa7517d2b6c797a499b9f491e9db9083"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "f73f7f4da581875f9b1f2fb8ebd1ab15ed634488",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "b7f54894aa7517d2b6c797a499b9f491e9db9083",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.24 by commit b7f54894aa7517d2b6c797a499b9f491e9db9083, it was introduced in version v5.13 by commit f73f7f4da581875f9b1f2fb8ebd1ab15ed634488. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000442


Shape of output value of concat is list in GPU

cuda.empty([1]) makes a GPUArray with list shape. It causes a type invalid error.
https://github.com/pfnet/chainer/blob/master/chainer/functions/concat.py#L69

This problem is already fixed in the newest version of pycuda.
https://github.com/inducer/pycuda/commit/53bcda2f825b3fc681907769318c33ed04c3b943#diff-c6f20a28105688a11d8983cd1fce702cL195

Me too...
$ time ./train_zoom_autoencoder.py -g 0
rmsqerr_adj:<PHONE_NUMBER>03
Traceback (most recent call last):
File "./train_zoom_autoencoder.py", line 288, in
loss.backward()
File "build/bdist.linux-x86_64/egg/chainer/variable.py", line 197, in backward
File "build/bdist.linux-x86_64/egg/chainer/variable.py", line 116, in grad
ValueError: Shape of data and grad mismatch: [2, 4, 1024, 1024] != (2, 4, 1024, 1024)
This error is occured in two cases. The first case is when the user manually
sets the Variable.grad incorrectly. The second case is when some Function
implementation has a bug. If you do not manually set the Variable.grad in your
script, please report this error to the issue tracker with the stack trace,
the information of your environment, and your script:
https://github.com/pfnet/chainer/issues/new.
real    0m15.683s
user    0m15.095s
sys     0m5.572s

I was able to fix the above error, by downloading the latest master repository of pycuda from
https://github.com/inducer/pycuda
and by manually installing it.

:+1:


Unable to load DLL 'gdiplus'

Type of issue
Bug
Current Behavior
Exception:
Unable to load DLL 'gdiplus': The specified module or one of its dependencies could not be found
(Exception from HRESULT: 0x8007007E)","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":"   at System.DrawingCore.GDIPlus.GdiplusStartup(UInt64& token, GdiplusStartupInput& input, GdiplusStartupOutput& output)\n   at System.DrawingCore.GDIPlus..cctor()","RemoteStackTraceString":null,"RemoteStackIndex":0,"ExceptionMethod":null,"HResult":-2146233052,"Source":"ZKWeb.System.Drawing","WatsonBuckets":null
I have these files in my server:
ZKWeb.System.Drawing.dll
System.Drawing.dll
System.Drawing.Primitives.dll
Environment

Version used:  QRCoder1.3.2
Compiled from source or NuGet package?:  NuGet package
Payload/Encoded text:  weixin：//wxpay/s/An4baqw
Environment: .NETCore, Centos
My Code:

QRCodeGenerator qrGenerator = new QRCodeGenerator();
QRCodeData qrCodeData = qrGenerator.CreateQrCode(uResult.code_url, QRCodeGenerator.ECCLevel.Q);
Base64QRCode qrCode = new Base64QRCode(qrCodeData);
string qrCodeImageAsBase64 = qrCode.GetGraphic(20);

Hi @xland ,
this is a known issue. To avoid this error and to have more "standard" code I removed ZKWeb's drawing classes and replaced them with the official System.Drawing in this commit https://github.com/codebude/QRCoder/commit/0b347a5963a2510896db0a015aae0e0c99dbade8
Unfortunately this commit will be become part of the next release, so it isn't covered by the current Nuget package. Thus you have two options:

Compile the library yourself from source
Add https://www.myget.org/F/qrcoder/api/v3/index.json as source to your Nuget Package Manager and take the QRCoder package from this stream. (This stream contains the latest build. Everytime a commit into this repository is done, this stream will get an update.)

Hi @xland ,
nice to hear that the solution worked. So I'll close this issue. Feel free to come back if you have more questions.

Hi,
I faced this issue although update QRCoder to 1.3.3.
Can you help me to resolve it?
Im using netcore 2.1.
Here is exception:
"Unable to load DLL 'libgdiplus': The specified module could not be found."
This my code - very simple as your example:
var activeLink = EmailConfig.ActiveURl + registerId.ToString();
QRCodeGenerator qrGenerator = new QRCodeGenerator();
QRCodeData qrCodeData = qrGenerator.CreateQrCode(activeLink, QRCodeGenerator.ECCLevel.Q);
Base64QRCode qrCode = new Base64QRCode(qrCodeData);
string qrCodeImageAsBase64 = qrCode.GetGraphic(20);
return qrCodeImageAsBase64;
additional picture:

Hi @DucBui93 ,
have you installed the latest libgdi on the system you want to use the QRCoder? Please do the following steps:
apt-get install libgdiplus
cd /usr/lib
ln -s libgdiplus.so gdiplus.dll

Let me know if it helped.

Hi @DucBui93 ,
have you installed the latest libgdi on the system you want to use the QRCoder? Please do the following steps:
apt-get install libgdiplus
cd /usr/lib
ln -s libgdiplus.so gdiplus.dll

Let me know if it helped.

Thanks,
After install libgdi in my mac.

opps, it's appear again in 1.3.5, and i had installed libgdiplus to linux system.


Chat - Pin icon flashes after switching back to online

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/14608
Action Performed:
1.Go offline
2.Pin a chat
3.Unpin a chat
4.Pin a chat again
5.Go online
Expected Result:
Chat ends up in the correct state of "pinned" without any blinking
Actual Result:
Pin icon flashes after switching back to online
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/215926287-a53d8a94-21df-41fc-9cc0-ec557d59cc73.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
View all open jobs on GitHub

I think this is to some extent expected because all the actions made offline are queued to be done when user comes back online. Hence if user will toggle the settings there and back while offline and comes back online, the requests will be sequentially made to the server resulting in this flickering behaviour. it does not look great, but I think this is not strictly a bug.

Gotcha, thanks for that context @mountiny - do you think we should close this for now then to focus on other items?

@greg-schroeder Now I have noticed the issue is mentioning a PR https://github.com/Expensify/App/pull/14608 where this was noticed. It might not be related but it might be worth:

check if engineer can repro locally on main
reverting that change in the mentioned PR locally
check if you can repro after the change

That would confirm this was caused by that PR.
If not, then I would probably close this.

@greg-schroeder can you also add Engineering so it picks someone internal, thanks!

Yep sorry, missed before this is coming form latest deploy https://github.com/Expensify/App/issues/14709#issuecomment-1412670582 so we should investigate if this is not a deploy blocker actually cc @thienlnam

Sure, I assigned Engineering to help with https://github.com/Expensify/App/issues/14720#issuecomment-1412828802

I am closing this because it is expected behavior as Vit points out. We've discussed this several times, and we have always opted to just let the network queue play out naturally when someone comes back online.


Does not work for Ruby Component

Describe the bug
The extension provides no details at all when visiting https://rubygems.org/gems/logstash-input-tcp/versions/6.0.9-java.
Desktop (please complete the following information):

OS: OSX
Browser Chrome
Extension Version 2.2.0

Raised on behalf of Bryan

This appears to be working as expected - no bug here.

The issue is how the PURL is being constructed. Current PURL being submitted for evaluation is<EMAIL_ADDRESS>- but this should be pkg:gem/logstash-input-tcp@6.0.9?platform=java

See https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst


🔥 Drop support for Python3.7

Thanks for the interest! I currently don't have a particular need to drop support for Python 3.7 so I'll pass on this one for now. ☕


PDO::getAttribute(PDO::ATTR_SERVER_VERSION) fails on connection from connection pool

Driver version or file name
extension version 4.3.0 (per php -i)
SQL Server version
SQL2016
Client operating system
CentOS Linux release 7.4.1708 (Core)
PHP version
PHP 7.1.15
Microsoft ODBC Driver version
<IP_ADDRESS> (per yum info msodbcsql)
Problem description
When using connection pooling requesting the Server Version attribute (PDO::ATTR_SERVER_VERSION) the request fails on the second request in the same process.
The reason that I ran into this quite specific problem is that the framework used (Laravel) uses Doctrine/DBAL which checks this attribute (see https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Driver/PDOConnection.php#L71). The code below is thus simplified.
Expected behavior and actual behavior
Expected behaviour was to receive a value for the attribute.
Actual behaviour is the code works fine for a non-connection-pool-connection (Pooling=no in odbcinst.ini) but a warning is thrown by PDO::getAttribute() when the connection would be from the connection pool:
PHP Warning:  PDO::getAttribute(): SQLSTATE[IM001]: Driver does not support this function: driver does not support that attribute in /path/to/test.php on line 6
Repro code
/etc/odbcinst.ini:
[ODBC]
Pooling=Yes

[ODBC Driver 13 for SQL Server]
Description=Microsoft ODBC Driver 13 for SQL Server
Driver=/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.1.so.9.2
UsageCount=1
CPTimeout=120

test.php:
<?php

for ($i = 0; $i < 4; $i++) {
    $pdo = new PDO('sqlsrv:Server=HOSTNAMEGOESHERE;Database=EXISTINGDATABASEGOESHERE', 'user', 'password');
    var_dump($pdo->getAttribute(PDO::ATTR_SERVER_VERSION));
    echo "----------------------------------\n";
}

?>

Expected result:
string(10) "13.00.4001"
----------------------------------
string(10) "13.00.4001"
----------------------------------
string(10) "13.00.4001"
----------------------------------
string(10) "13.00.4001"
----------------------------------

Actual result:
string(10) "13.00.4001"
----------------------------------
string(10) "13.00.4001"
----------------------------------
PHP Warning:  PDO::getAttribute(): SQLSTATE[IM001]: Driver does not support this function: driver does not support that attribute in test.php on line 6
bool(false)
----------------------------------
PHP Warning:  PDO::getAttribute(): SQLSTATE[IM001]: Driver does not support this function: driver does not support that attribute in test.php on line 6
bool(false)
----------------------------------

Hi @mathieuk
The problem lies in unixodbc. I can reproduce the same problem in both Ubuntu 16.04 and CentOS 7 with ODBC 17.1.
However, I did test that with unixODBC 2.3.6  the problem goes away.

This indeed seems fixed with a more up to date unixODBC. Thanks for looking into this!

Great! I'm going to close this issue, @mathieuk
Please feel free to reopen in case you have more questions.

Dear @yitam , does it unixODBC driver be applied to the server?
Thanks in advance!

@marcellopato I'm not sure I understand what you're asking about unixODBC. ODBC driver depends on the driver manager unixODBC and by installing ODBC 17 will update unixODBC as well.

@yitam Hi and thanks for the answer. I meant if the unixODBC should be installed on the dev and production server.
I do dev on a mac. The MSSQL is running on an aws server witch I don´t know yet if is Linux or Windows.
I hope I made myself more clear this time and thanks again for your help!


Reduce number of management network commands issued during env creation

We need to reduce number of "subutai management_network -Z list" commands issued by SS during environment creation to optimize the speed and reduce traffic.

Number of execution of this command reduced by taking the command out of a loop


Move mixins to global space

This PR is awesome.
It will lead to better integration of resource-loader and all my plugins. We'll get proper mixins declaration in d.ts files!
This is initial demo - I expose only DisplayObject. More stuff will be exposed later when we discuss this one.
Many mixins will be exposed for canvas packages.

I'll need to test this locally, will let you know tomorrow :)

Good one!


ISSUE-9: Move internalOptions.facade to public api (fix #9)

Links
#9
What is this?

Ability to override default Node.js FileSystem API's.

Hm, strange that tests for options.filter is failed. Well, will be fixed soon.

Coverage increased (+0.07%) to 98.154% when pulling 099aaad0e7114e1c7dad315bbe4ac76b5dc0a3ed on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

@mrmlnc - Great work, as always!  Thanks for always including tests, comments, and documentation with all of your PRs.  I really appreciate that.
I like your approach to this, but I'd suggest a couple minor changes...
First, rather than merging the options.facade and internalOptions.facade in three places (lib/sync/index.js, lib/async/index.js, and lib/steam/index.js), I think it would be better to do it inside the normalizeOptions.js function.  That function accepts the options and internalOptions objects, does whatever logic is necessary to merge the two, and returns a merged and normalized object.
Secondly, I think it would be simpler to have the fs methods directly on options.facade, rather than having separate options.facade.sync and options.facade.async properties.  Any given readdir-enhanced method is only sync or async, so it wouldn't ever make sense to pass both sync and async facades.  It'll be up to the user to know whether they're calling a synchronous or asynchronous method and pass the correct facade for it.
What do you think?  These are pretty minor changes, and now I realize that I probably could have done them in the time it took to write all of this. 😀

Also, I've invited you to be a contributor on this project, since you consistently do such good work on it. 👍

Yeap, I'll think about it very soon.

Well, push alternative way :)

Coverage decreased (-28.3%) to 69.811% when pulling ce47f9e4389094f36fa4036c1a53cf28058e8faf on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

Coverage increased (+0.05%) to 98.131% when pulling cf9100e1916a70428a9e654653b9a6c39d2e26b1 on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

Coverage increased (+0.05%) to 98.131% when pulling e0944e5a8b4cd0e12cd57d26b028ee0541357baa on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

Coverage increased (+0.05%) to 98.131% when pulling e0944e5a8b4cd0e12cd57d26b028ee0541357baa on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

Coverage increased (+0.05%) to 98.131% when pulling e0944e5a8b4cd0e12cd57d26b028ee0541357baa on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

Coverage increased (+0.05%) to 98.131% when pulling e0944e5a8b4cd0e12cd57d26b028ee0541357baa on mrmlnc:ISSUE-9_public_facades into 6dce763f742f45457cbff042d581226f5caeeaca on BigstickCarpet:master.

@BigstickCarpet ping :smiley:

@mrmlnc - Sorry.  I've had zero spare time for the past couple of weeks.  But I'm off next week for the holidays, so I'm planning to catch-up on stuff like this.  Sorry for the delay :(

Ok, @mrmlnc, I finally got some free time to merge this PR.  Thanks again for the great work!  I'll make the changes that I mentioned above and then publish a new version to NPM.  Shouldn't take more than a couple hours.


Large Objects ownership

Steps to reproduce

deploy postgresql charm (14/stable) in a K8S cluster
deploy your application charm (MAAS, WIP, uses postgresql_client interface)
integrate MAAS and postgresql-k8s (through a cross-model integration)
use MAAS for a while, wait for it to create some Large Objects in the DB
remove the MAAS application
deploy MAAS again
integrate MAAS and postgresql again (it requests the same DB name)

Expected behavior
The new deployment inherits the existing database with ownership of all existing Large Objects.
Actual behavior

When the application is removed the first time, postgresql drops its user. As result, all existing LO are inherited by the DB owner (operator) as seen in table pg_catalog.pg_largeobject_metadata. When the application is deployed again, postgresql creates a new user and grants all rights to it, but the LO objects remain owned by the operator user.
Versions

Operating system: Ubuntu 22.04.3 LTS

Juju CLI: 3.3.1-genericlinux-amd64

Juju agent: 3.3.1

Charm revision: 14.9
Copy of https://github.com/canonical/postgresql-operator/issues/348.

Revision 202 contains the fix.