feat: a subset of $R$ can act on submodules of $R$ module

If $M$ is an $R$-module, $N$ a submodule and $S$ a subset of $R$. Then we can define $S \cdot N$ to be the smallest submodule containing all $s \cdot n$ where $s \in S$ and $n \in N$

I think in locale Pointwise this is even a MulAction.

I think in locale Pointwise this is even a MulAction.

proving mul_smul is longer than I expected, I think it's better to do it in another PR

I think in locale Pointwise this is even a MulAction.

It is a distributive multicative action! Thanks for pointing this out.

It is a distributive multicative action! Thanks for pointing this out.

Thanks for confirming! If Set R were a Semiring I think we can also show it's a Module, but it's not (distributivity doesn't hold).

! If Set R were a Semiring

It is when using the SetSemiring alias

I think we might already have a Module (Ideal R) (Submodule R M) instance; is this new instance the same a that one composed with Ideal.span?

It is when using the SetSemiring alias

That's using union as addition, not pointwise addition inherited from addition on R.

I think we might already have a Module (Ideal R) (Submodule R M) instance; is this new instance the same a that one composed with Ideal.span?

I think yes (and loogle found Submodule.moduleSubmodule).

It is when using the SetSemiring alias

That's using union as addition, not pointwise addition inherited from addition on R.

I think we might already have a Module (Ideal R) (Submodule R M) instance; is this new instance the same a that one composed with Ideal.span?

I think yes (and loogle found Submodule.moduleSubmodule). (Should we restrict to CommSemiring?)

Should I re-implement this in terms of span composing with soul then?

I suspect this has the same problem as you remarked about for the case of non-commutative rings R

Do you actually care about the non-commutative case?

Do you actually care about the non-commutative case?

No,not really

Do you actually care about the non-commutative case?

No,not really. But we should have it work for noncomm cases in case other people care about them right?

Only if we think the generalization is reasonable; for instance you say that

Submodule.pointwiseDistribMulActionwants[SMulCommClass α R M], so when we write down r • N, we need a type class SMulCommClass R R M, but Ris assumed to be semiring here not necessarily commutative, so we can't writer • N`?

One option is of course to redefine r • N as the smallest submodule with the property you describe, but then it is no longer the case that it is equal to r • (N : Set M). Arguably, the value in that definition in the first place is that it coincides.
Maybe it's obvious to you that this generalization is the right one, but in cases where it's not its often best to leave the generalization for someone who does care about it, so that they can ensure the generalization goes in the right directions.

Note: I have pushed an update to the lean toolchain because this PR was on a buggy version of the toolchain. WARNING: checking out old commits of this PR using v4.2.0-rc2 or v4.2.0-rc3 can cause lake clean to delete your mathlib folder! If you need to do so, make sure to delete lakefile.olean manually before running any lake commands.

LGTM modulo the minor comment above
maintainer merge


Initializing Terraform Provider printed

Describe what happened
An init message is printed into stdout when using pulumi-aws:
Previewing update (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/anton-pulumi-corp/bucket-sets/dev/previews/edd87a15-9430-4bac-976f-7da66ca493f5

     Type                 Name             Plan     Info
     pulumi:pulumi:Stack  bucket-sets-dev           1 message

Diagnostics:
  pulumi:pulumi:Stack (bucket-sets-dev):
    2024/10/16 11:16:28 Initializing Terraform AWS Provider...

Resources:
    2 unchanged

Updating (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/anton-pulumi-corp/bucket-sets/dev/updates/4

     Type                 Name             Status     Info
     pulumi:pulumi:Stack  bucket-sets-dev             1 message

Diagnostics:
  pulumi:pulumi:Stack (bucket-sets-dev):
    2024/10/16 11:16:32 Initializing Terraform AWS Provider...

Sample program
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";

// Create an AWS resource (S3 Bucket)
const role = new aws.iam.Role("test-role", {
    assumeRolePolicy: aws.iam.assumeRolePolicyForPrincipal({ Service: "lambda.amazonaws.com" }),
    managedPolicyArns: ["arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy"]
})

Log output
N/A
Affected Resource(s)
No response
Output of pulumi about
N/A
Additional context
CLI
Version      3.130.0
Go Version   go1.22.6
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  aws     6.56.0
resource  awsx    2.16.1
resource  docker  4.5.6
resource  docker  3.6.1
language  nodejs  unknown

Host
OS       darwin
Version  14.6.1
Arch     arm64

This project is written in nodejs: executable='/Users/anton/bin/node' version='v18.18.2'

Current Stack: anton-pulumi-corp/bucket-sets/dev

TYPE                  URN
pulumi:pulumi:Stack   urn:pulumi:dev::bucket-sets::pulumi:pulumi:Stack::bucket-sets-dev
pulumi:providers:aws  urn:pulumi:dev::bucket-sets::pulumi:providers:aws::default_6_56_0
aws:iam/role:Role     urn:pulumi:dev::bucket-sets::aws:iam/role:Role::test-role

Found no pending operations associated with dev

Backend
Name           pulumi.com
URL            https://app.pulumi.com/anton-pulumi-corp
User           anton-pulumi-corp
Organizations  anton-pulumi-corp, moolumi, demo, pulumi
Token type     personal

Dependencies:
NAME            VERSION
@pulumi/pulumi  3.136.1
@types/node     18.19.55
typescript      5.6.3
@pulumi/aws     6.56.0
@pulumi/awsx    2.16.1

Pulumi locates its logs in /var/folders/gd/3ncjb1lj5ljgk8xl5ssn_gvc0000gn/T/com.apple.shortcuts.mac-helper// by default

Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Looks like here is a recent change that inserted a log.Printf that is now showing through Pulumi:
https://github.com/hashicorp/terraform-provider-aws/commit/7a4449abc8925c0b58cd0aca0558102f96331119#diff-58d6a027753b50994deb7e11e4a99dde423f35844986019bd9cea5e0c94aba22R37


test: add libp2p-websocket-star tests

Adds tests for libp2p-websocket-star
Ref libp2p/js-libp2p-websocket-star#3

Ok, I've gone through and give a big CR (with refactoring in place) to websocket-star. Overall there is a ton of work there and I'm really happy to see it coming together, thank you @mkg20001 👏🏽👏🏽👏🏽👏🏽!
The CR+Refactor can be found in:

https://github.com/libp2p/js-libp2p-websocket-star/pull/16
https://github.com/libp2p/js-libp2p-websocket-star-rendezvous/pull/1

To release and integrate websocket-star with confidence, recommending our users to try it out, I still want to see some issues solved and/or improved. I've opened issues in both repos so that it is clear what is missing, lists can be found in:

https://github.com/libp2p/js-libp2p-websocket-star-rendezvous/issues
https://github.com/libp2p/js-libp2p-websocket-star/issues

@mkg20001 is this something you would like to finish? I can continue helping by providing CR and coding time, just not sure how much time I can allocate that soon :)
Thanks!

@mkg20001 is this something you would like to finish? I can continue helping by providing CR and coding time, just not sure how much time I can allocate that soon :)

Yes but I'm also working on https://github.com/ZeroNetJS/zeronet-js/ and my last year in school just began so I won't be working on this project that much

I didn't know about zeronet-js with libp2p! That's rad! :D

Actually, this is more than rad! it is super-duper rad! Wanna show it working today at the IPFS All Hands?

After thinking about that for a while and talking with my parents I decided it would be a good idea. I'm usually a bit shy and this would be the first every meeting/conference/etc where I would participate. But I would like to participate. How can I join? How does that work?

@dryajov @VictorBjelkholm can I get your review here as well?

Rebased all changes against current master and released stable versions of the libp2p-websocket-star* modules.
Merge?

Can you provide a configuration you've tested this with in js-ipfs?
In my tests to implement this I found some odd issues with the multi addresses.
Using a test server,
config: {
  Addresses: {
    Swarm: [
      '/dns4/ws-star-signal-2.servep2p.com/wss/p2p-websocket-star/'
    ]
  }
}

My logs output:

Swarm listening on /dns4/ws-star-signal-2.servep2p.com/wss/p2p-websocket-star/ipfs/QmcdoJPn4CStGjJd58XQE3GfLZQHSshMovhoGMNFoHd9px/ipfs/QmcdoJPn4CStGjJd58XQE3GfLZQHSshMovhoGMNFoHd9px

And it does not successfully connect with any peers over websocket star.
When I add this to src/core/runtime/libp2p-browser.js
peerInfo.multiaddrs.clear()
peerInfo.multiaddrs.add(multiaddr('/dns4/ws-star-signal-1.servep2p.com/wss/p2p-websocket-star/'))
const wsstar = new WSStar({id: peerInfo.id})

It will do peer discovery, bitswam and pubsub correctly.

Try it with https://github.com/mkg20001/js-ipfs/tree/feat-websocketstar or apply this patch and see if it works

The only annoying thing is that now it is not possible to configure the libp2p transport with the WebSocketStar from the configuration like:
  const ipfs = new Ipfs({
    libp2p: {
      modules: {
        transport: [new WebSocketStar({id: peerInfo.id})],
        discovery: [new WebSocketStar({id: peerInfo.id})]
      }
    }
  })

because in that scenario the peerInfo is not available yet. Not sure if it is critical to have that though.

You can use it without peer id and use this signalling server instead: /dns/ws-star-signal-4.servep2p.com/wss/p2p-websocket-star/. note that it's not as secure as the other servers (no crypto challenge)

Let's focus on figuring out #130 to get that PeerId on the transport. Until then let's move with the not as secure, also not yet audited version.

@mkg20001 thanks for pushing this :) I've made some comments. I am happy to finish this one tomorrow early morning if you don't have time until then. Thank you!

I see a number of configurations posted as not working above,  is there a conclusion of a configuration that works ? Could it be posted here.


Can't see dates only time (jQuery 3 only)

As I started transitioning to jQuery 3 I noticed that the date pickers stopped working.
When I click on a datepicker I see this:

If I click on the time icon, I can swap to time, it transitions correctly, and I see the time fine (except I think the icon is supposed to be at the bottom?):

If I click back everything is still short like it was on the first picture. If I swap to jQuery 2.2.4 it works just fine so I have no idea what to do about this situation. I thought it could be related to this #1657 but I tried applying these changes and it did nothing.
Help please!

Hi,
As mentioned in #1765 you can temporarily add
div.datepicker > div { display: block; }
until the issue is fixed.

Hi @poulpo !
Thank you so much, this piece of code has seemed to fix the issue for the time being!


[docs] Set default value for filterOptions

By default, options are filtered through fuzzy match. This is confusing when the docs don't have any default, setting the expectation that the options provided should not be filtered based on the value.

[x] I have followed (at least) the PR section of the contributing guide.

Please run yarn docs:api and commit

@mithunm93
Hi, thanks for opening the PR. However, I think setting a string value as default value for filterOptions, which supports only function type, will create more confusion for users.
In addition, the way of creating custom filter options is already documented quite clearly here, so I'd say we do not need the change of this PR.

I think setting a string value as default value for filterOptions, which supports only function type, will create more confusion for users.

I second that. Besides, the default values in the docs are taken from JSDocs comments and types must match.

I'd say we do not need the change of this PR.

I'm closing the PR.


Rename package to 'zenodo-get' to match pypi?

Is it possible/reasonable to rename this conda package zenodo-get to match the PyPI package name?

Even the doc at https://gitlab.com/dvolgyes/zenodo_get asked the user to pip3 install zenodo_get. I think it is better to ask the upstream to decide which one they want to stick to first and be internally consistent.
I'm not sure how to rename a conda-forge feedstock, and may be the easiest way is just to create a new feedstock and discontinue this one if we really want to rename.

I think this might be a PyPI quirk that the package is properly called zenodo_get but PyPI allows and encourages the use of zenodo-get? Either way this is an upstream issue. Thanks.


still doesnt work

it still doesnt work despite xxcodianxx already voicing his concerns about this game breaking issue

pretty normal

pretty normal

1/10 project, dev was mean to me


fix: collection description/info not refresh after search

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #5516
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

@JustLuuuu it's fixed 🥹
https://deploy-preview-5518--koda-canary.netlify.app/

pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 33.82 USD/KSM ~ 0.591 $KSM
🧗 EZiu1PjV2j2JHKxY6mHnFwwCRCoV27uHKQSkKXATSh1srJT
🔗 0x464a4899965d7c96df938dad11d1c6eee0b664e383d9b75209a0448e5a6cbc54
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


OpenCL error codes, then junk output -- possibly a build issue?

Hi folks,
Having trouble getting a working OpenCL build. First run in a new working directory gets upset that there's no opencl_profile_devices.dat:
axfelix@shoebox:~/Desktop$ tesseract test.png out pdf
Tesseract Open Source OCR Engine v3.05.00dev with Leptonica
[DS] Profile file not available (tesseract_opencl_profile_devices.dat); performing profiling.
[DS] Device: "GeForce GTX TITAN X" (OpenCL) evaluation...
[OD] write binary[kernel-GeForce_GTX_TITAN_X.bin] succesfully
[DS] Device: "GeForce GTX TITAN X" (OpenCL) evaluated
[DS]          composeRGBPixel: 0.022978 (w=1.2)
[DS]            HistogramRect: 0.012700 (w=2.4)
[DS]       ThresholdRectToPix: 0.010093 (w=4.5)
[DS]        getLineMasksMorph: 0.004402 (w=5.0)
[DS]                    Score: 0.125484
[DS] Device: "(null)" (Native) evaluation...
[DS] Device: "(null)" (Native) evaluated
[DS]          composeRGBPixel: 0.018301 (w=1.2)
[DS]            HistogramRect: 0.060059 (w=2.4)
[DS]       ThresholdRectToPix: 0.016802 (w=4.5)
[DS]        getLineMasksMorph: 0.110437 (w=5.0)
[DS]                    Score: 0.793896
[DS] Scores written to file (tesseract_opencl_profile_devices.dat).
[DS] Device[1] 1:GeForce GTX TITAN X score is 0.125484
[DS] Device[2] 0:(null) score is 0.793896
[DS] Selected Device[1]: "GeForce GTX TITAN X" (OpenCL)
OpenCL error code is -38 at   when clSetKernelArg imageBuffer .
OpenCL error code is -38 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -38 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -38 at   when clSetKernelArg histogramBuffer .
OpenCL error code is -52 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannels .
OpenCL error code is -52 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannelsReduction .
OpenCL error code is -38 at   when clSetKernelArg imageBuffer .
OpenCL error code is -38 at   when clSetKernelArg thresholdsBuffer .
OpenCL error code is -38 at   when clSetKernelArg hiValuesBuffer .
OpenCL error code is -38 at   when clSetKernelArg pixThBuffer .
OpenCL error code is -52 at   when clEnqueueNDRangeKernel kernel_ThresholdRectToPix .
Setting return value to -1
OpenCL error code is -38 at   when clSetKernelArg imageBuffer .
OpenCL error code is -38 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -38 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -38 at   when clSetKernelArg histogramBuffer .
OpenCL error code is -52 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannels .
OpenCL error code is -52 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannelsReduction .
After that, it works (while throwing issues like Error in boxClipToRectangle: box outside rectangle
Error in pixScanForForeground: invalid box) but the output is basically junk. Did I screw something up when compiling?

I'm seeing something very similar. First time I run Tesseract after deleting tesseract_opencl_profile_devices.dat, I get the following:
START**
-bash-4.2$ tesseract ESub.png ESubPng
Tesseract Open Source OCR Engine v3.04.00 with Leptonica
[DS] Profile file not available (tesseract_opencl_profile_devices.dat); performing profiling.
[DS] Device: "Tesla K40c" (OpenCL) evaluation...
OpenCL error code is -44 at   when clCreateKernel .
OpenCL error code is -48 at   when clSetKernelArg .
OpenCL error code is -48 at   when clSetKernelArg .
OpenCL error code is -48 at   when clSetKernelArg .
OpenCL error code is -48 at   when clSetKernelArg .
OpenCL error code is -48 at   when clSetKernelArg .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectAllChannels .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectAllChannelsReduction .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg numPixels .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg histogramBuffer .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannels .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannelsReduction .
OpenCL error code is -44 at   when clCreateKernel kernel_ThresholdRectToPix .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg height .
OpenCL error code is -48 at   when clSetKernelArg width .
OpenCL error code is -48 at   when clSetKernelArg wpl .
OpenCL error code is -48 at   when clSetKernelArg thresholdsBuffer .
OpenCL error code is -48 at   when clSetKernelArg hiValuesBuffer .
OpenCL error code is -48 at   when clSetKernelArg pixThBuffer .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_ThresholdRectToPix .
[DS] Device: "Tesla K40c" (OpenCL) evaluated
[DS]          composeRGBPixel: 0.022510 (w=1.2)
[DS]            HistogramRect: 0.006130 (w=2.4)
[DS]       ThresholdRectToPix: 0.005528 (w=4.5)
[DS]        getLineMasksMorph: 0.007509 (w=5.0)
[DS]                    Score: 0.104147
[DS] Device: "(null)" (Native) evaluation...
[DS] Device: "(null)" (Native) evaluated
[DS]          composeRGBPixel: 0.029208 (w=1.2)
[DS]            HistogramRect: 0.108206 (w=2.4)
[DS]       ThresholdRectToPix: 0.032306 (w=4.5)
[DS]        getLineMasksMorph: 0.200906 (w=5.0)
[DS]                    Score: 1.444651
[DS] Scores written to file (tesseract_opencl_profile_devices.dat).
[DS] Device[1] 1:Tesla K40c score is 0.104147
[DS] Device[2] 0:(null) score is 1.444651
[DS] Selected Device[1]: "Tesla K40c" (OpenCL)
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectOneChannel .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectOneChannelReduction .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg numPixels .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg histogramBuffer .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannels .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannelsReduction .
OpenCL error code is -44 at   when clCreateKernel kernel_ThresholdRectToPix_OneChan .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg height .
OpenCL error code is -48 at   when clSetKernelArg width .
OpenCL error code is -48 at   when clSetKernelArg wpl .
OpenCL error code is -48 at   when clSetKernelArg thresholdsBuffer .
OpenCL error code is -48 at   when clSetKernelArg hiValuesBuffer .
OpenCL error code is -48 at   when clSetKernelArg pixThBuffer .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_ThresholdRectToPix .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectOneChannel .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectOneChannelReduction .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg numPixels .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .
OpenCL error code is -48 at   when clSetKernelArg tmpHistogramBuffer .
OpenCL error code is -48 at   when clSetKernelArg histogramBuffer .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannels .
OpenCL error code is -48 at   when clEnqueueNDRangeKernel kernel_HistogramRectAllChannelsReduction .
-bash-4.2$
STOP**********
Running after that I get:
START**********
-bash-4.2$ tesseract ESub.png ESubPng
Tesseract Open Source OCR Engine v3.04.00 with Leptonica
[DS] Profile read from file (tesseract_opencl_profile_devices.dat).
[DS] Device[1] 1:Tesla K40c score is 0.104147
[DS] Device[2] 0:(null) score is 1.444651
[DS] Selected Device[1]: "Tesla K40c" (OpenCL)
-bash-4.2$
STOP***********
This creates the txt file, but it's just junk, maybe a few random characters. For a long time I was also seeing the 'Error in boxClipToRectangle: box outside rectangle' sort of errors that axfelix was seeing.
If I run it with the CPU device like this:
TESSERACT_OPENCL_DEVICE=2 tesseract ESub.png ESubPng
...it works perfectly. Great OCR output.
I have done everything I can imagine, including rebuilding Tesseract several times, using jpg, png and tif input files and rebuilding Leptonica. The nvidia drivers are the latest and OpenCL is the latest.
Any ideas?

Still working on the problem. Here's some information that will hopefully make it easier for someone to solve before I spend another day tracking it down.
I have two test cases using the same source file. Doesn't matter if the source is png or tif, same bad results. Tesseract correctly identifies that I have a Tesla K40c as device 1. The CPU is device 2. The call I'm making is either:
TESSERACT_OPENCL_DEVICE=1 tesseract ESub.png Esub -l enm //GPU
or
TESSERACT_OPENCL_DEVICE=2 tesseract ESub.png Esub -l enm //CPU
In the file baseapi.cpp in function TessBaseAPI::ProcessPage() I put in code to save the image before and after the call to GetThresholdedImage() like so:
pixWrite("tessinputBEFORE.tif", pix, IFF_TIFF_G4);
Pix* page_pix = GetThresholdedImage();
pixWrite("tessinputAFTER.tif", page_pix, IFF_TIFF_G4);

In the CPU version both before and after images look correct, showing the same text and formatting.
In the GPU OpenCL version 'before' is fine, but the 'after' version is seriously sheared when the source image has non-binary dimensions.  It looks like the pitch is being miscalculated. The source image was 1721 x 1238 pixels. In this case the OCR failed completely of course.
On an educated hunch I resized the the same image to 2048 x 1024. Now the shearing is gone, The characters in the image are somewhat recognizable. There is still a problem, the letters are all munged, almost like letters are being overlaid on top of each other or something. I will send the two bad output images if you tell me where.

Here you go...
Original source image 1721 x 1238:

Result when source image resized to 2048 x 1024 results:

Sheared OpenCL output with odd-sized source image.

I swear I've seen this particular image corruption before, when I was working on the pdf output module. I wish I could remember what it was.

Anything else that can be done to help debug? I have a vested interest in getting a working OpenCL build before the end of January...

I speculate we had a Leptonica bug, fixed it, but the fix never got propagated to the OpenCL-ified mini-fork of Leptonica that sits inside Tesseract. I think the way to go is look inside the thresholding call and keep comparing the CPU vs GPU to help isolate where things go different. It's also helpful to look at all data in the pix struct before/after/cpu/gpu to understand better what went wrong.
struct Pix
{
l_uint32             w;           /* width in pixels                   /
l_uint32             h;           / height in pixels                  /
l_uint32             d;           / depth in bits (bpp)               /
l_uint32             spp;         / number of samples per pixel       /
l_uint32             wpl;         / 32-bit words/line                 /
l_uint32             refcount;    / reference count (1 if no clones)  /
l_int32              xres;        / image res (ppi) in x direction    /
/ (use 0 if unknown)                /
l_int32              yres;        / image res (ppi) in y direction    /
/ (use 0 if unknown)                /
l_int32              informat;    / input file format, IFF_*          /
l_int32              special;     / special instructions for I/O, etc */
char                text;        / text string associated with pix   */
struct PixColormap  colormap;    / colormap (may be null)            */
l_uint32            data;        / the image data                    */
};
P.S. What's up with this? Debuggnig cruft?
https://github.com/tesseract-ocr/tesseract/blob/c53add706e7853c8ea9986a87aebb465f29173bd/api/baseapi.cpp#L1230

Yeah, that sure looks like a debug path. New theory is OpenCL turns on some some debugging, which activates faulty debugging code that messes everything up.

Separate experiment, swap:
pixWrite("tessinputAFTER.tif", page_pix, IFF_TIFF_G4);
with
pixWrite("tessinputAFTER.png", page_pix, IFF_PNG);
just to make sure we're not having trouble with writing out your debug image.
I can imagine weird problems if the depth is not 1 bit per pixel and we try
to write out g4 tiff.

And finally, find the place where the image is first read into Tesseeract and turned into a Pix. See if we already have corruption at that point.

I can't debug this myself. I still get a segfault on my computer when trying to use OpenCL as per issue #53 . Will be travelling for the rest of the month. Good luck and sorry.

Please check master branch or commits f46dfdc29da2bbacf6635752d9f28133ad4e10fe and 5db760215fa05f8dd722f66bc6a3ac438a5cd8d4.

PR #475 fixes an error with OpenCL which results in these error message:
Tesseract Open Source OCR Engine v3.05.00dev with Leptonica
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectAllChannels .
OpenCL error code is -44 at   when clCreateKernel kernel_HistogramRectAllChannelsReduction .
OpenCL error code is -48 at   when clSetKernelArg imageBuffer .

Maybe it is related to this issue, too.


Add a Slope criteria to see if a technical indicator or series is moving up/down

Should have a value for how steep the slope should be for the criteria to trigger.

Currently this is being emulated by using a Above/Below criteria with a technical indicator and a cloned one of Shift(ti, 1).


[Feature Request] Typed API Client

Is your feature request related to a problem? Please describe.
I'm using the REST API to execute fetches for room data (metadata, permissions, etc.). Currently, I'm using axios to dispatch requests which is fine but it would be nice to have a typed client similar to this:
const liveblocks = new Liveblocks({ secret: SECRET_KEY! });
Describe the solution you'd like
It would be great if we could either expose additional methods on the existing Liveblocks class or create a dedicated typed REST client.
interface LiveBlocks {
  ... existing liveblocks methos
  getRoom(id: string): Promise<Room>
  getRooms(): Promise<Array<Room>>
  etc..
}

This is absolutely something we want to offer in our @liveblocks/node API, it just hasn't been implemented yet. I'll take this to the team 👍

Hi @nvie . I would love to use the @liveblocks/node api. Also I would love to contribute to the same. Is there somewhere I can access the same?

What would it take to at least expose OpenAPI definitions on the RestAPI? Generators are excellent these days so that way we could generate clients in whatever language we like and get full type safety.
It's one of the few surprising aspects of liveblocks so far, that there's a REST API but no client or even OpenAPI definitions available

Hello everyone, we just added all our REST APIs as fully typed methods to Liveblocks client. See docs.


docs: update image tags to proper paths

Specifies the correct image tag for running sxm-player via docker. Closes #3. Fixed version of #8

Since this is the repo that back Docker Hub, the README should be for any Docker Hub URLs. Any Github related docs for the image can be inside of the main sxm-player repo.

Good point - updated.


add taginfo file to let OSMers know which tags we use

Taginfo is a very useful project to learn about tags in OSM, and you can use it to know what the tags are used to.
this PR add a taginfo file for our project, so it can be displayed in the pages for the tags we use.
The documentation for the file format can be found here : https://wiki.openstreetmap.org/wiki/Taginfo/Projects
I didn't add all the tags we use in here, because this does not have to replace our documentation, it is mainly a way to advertise our project and how to map in OSM to use it ;)

it might also bo nice to say that we read all the name:* tags but there does not seem to be a way to tell this, so it's fine for the moment
I created a PR to reference this: https://github.com/taginfo/taginfo-projects/pull/58

thanks :+1:


Add episode 05 (Functions).

number 5: functions  and..
I forgot to commit a change from your comment in number 04, so adding it here (novice mistake to make me empathize more with our novice students :-D)

thanks for your suggestions @mkcor
I believe I answered  all of your comments. Can you have a last look and if you agree with all feel free to merge

@mkcor , I fixed the conflict :-)

@mkcor , I fixed the conflict :-)

Ok, great! Feel free to merge, but I would be careful when using the term 'parameter;' in this episode, it appears under two different meanings, and the difference isn't made explicit.


CSS in comments is not ignored by Polymer.

      /*paper-submenu::shadow paper-item::shadow iron-icon {
        position: absolute;
        top: 4px;
      }*/

Just an example, the above CSS continued to be perpetuated to the element despite comments.

/sub

In #2473 a testcase was added to test the reported bug, however CI reports it is working correctly. Additional replication steps would be needed to narrow down a bug, or this issue could be closed via the PR?

I just tested this and either the problem is fixed or, there was some other underlying cause, but definitely closeable from my perspective.


Can't update - pyee version requirements differ between ChangeDetection and Playwright

I self-host and have a PIP based install (I updated the PIP install instructions on your Wiki last year) - this normally runs without issue and updates are fine.
This time however I see ChangeDetection and Playwright having different version requirements for the same package: pyee
ChangeDetection  = pyee 12.0.0
Playwright = pyee < 12.0.0 but > 11.0.0
playwright 1.47.0 requires pyee==12.0.0, but you have pyee 11.1.1 which is incompatible.
pyppeteer-ng 2.0.0rc5 requires pyee<12.0.0,>=11.0.0, but you have pyee 12.0.0 which is incompatible
Installing 12.0.0 before updating CD, results in it being dropped back to down 11.1.1 due to Playwright's requirements.

hmm it's because of pyppeteer-ng mainly, need to test that package with an updated pyee :/


Consider mechanism for dynamic selection of source DB and view

For example, one might call session.getAddressBookCollection() and then read values from the same view in each DB.
One possibility may be to not handle this in the driver at all: just assume the developer will have a scoped bean they can use to push/pop the next-up DB to process, and then not account for differences in view names. That would avoid the question of how to handle cases of opening a DB as a specific user in a non-API-specific way.

I'll start this by implementing methods to query a view explicitly by name, leaving aside the question of different DBs for now. That can fall under the umbrella of https://github.com/OpenNTF/org.openntf.xsp.jakartaee/issues/332.


Improve typography

Hello,
I have two suggestions on how to improve the typography of the digits: groups of three and monospace numbers.
One of my favorite OTP apps on iOS https://www.hde.co.jp/otp/en/ puts the digits into groups of three, which makes it a bit easier to read and type them out. I'd like to see this in your Authenticator as well.
Monospace numbers would make the codes line up better in some of the fonts. This is just a cosmetic thing my OCD would like to have ;) https://dev.fitbit.com/build/guides/user-interface/css/#monospace-numbers Fitbit details how to access monospace numbers.

Hi,
Great idea, and thank you for the link to the monospace resource. I'll be implementing the grouping and monospace (for supported fonts) in the next version!

Both of these are now available in the latest update.


Date parsing with timezone information

My CLOCK are generated this way:
  CLOCK: [2020-09-09 Wed 09:04 CEST]--[2020-09-09 Wed 09:04 CEST] =>  0:00

Context
Notice the timezone information. I need to be able to parse this timezone information to have non-naive datetimes.
Indeed, I'm travelling as I work, and use these clock information generated in local times all over the world.
They need to be converted then to my customers timezone.
About non-naive datetime
Anyway, it seems quite desirable to handle only non-naive datetime anyway.
Note also that I don't think I've done anything special to change the time format of emacs.
Analysis of code
First, orgparse don't recognize this because of the timezone information that is not expected.
I'm able to fix that, but then, what to do with the timezone information ?
python's datetime is a really big mess and does not know how to solve this alone:

datetime.datetime.strptime

still creates naive datetime using "%Z"... this is a bug/quirk (see: stackoverflow nice summary)
could create non-naive datetime using "%z" for some python 3.2+ only.
anyway "%Z" and "%z" do not know how to handle more than a very few timezone specifier

see patch to update doc about %Z not handling much
see python issue about %Z not handling much

Otherwise you must create yourself a tzinfo object...
So, the only way to do this correctly is:

Either keep the full "%Y-%m-%d %H:%M %Z" string unparsed (at least it is complete info) and give it to OrgDateClock so that we can do some proper parsing of this info (but then, how do you check duration and I didn't check if you had other code expecting that OrgDateClock were holding actual datetime object).
Either depend on some other external python package to create a full fledged datetime object.

How do you view this problem and are you interested to support full non-naive time parsing ?
I'm able to send you a PR, but won't do it without your approval, as it may imply some decisions about adding a dependency to orgparse.

Hi!
Oh, interesting, I think it's the first time I've seen the timezone in org-mode dates!

Note also that I don't think I've done anything special to change the time format of emacs.

Are you sure? I did a quick web search and also grepped org-mode sources, and it doesn't look like there is native timezone support.

How do you view this problem and are you interested to support full non-naive time parsing ?

That said org-mode is extensible and I think it's would be an interesting problem to solve within orgparse too, so would be happy to help!

python's datetime is a really big mess and does not know how to solve this alone:

Yep! I've had to parse tz info with strptime several times, and every time I ended up with some hacks like splitting timezone info substring and manually parsing it separately.. or something similarly horrible.

I'm able to send you a PR, but won't do it without your approval, as it may imply some decisions about adding a dependency to orgparse.

Appreciate checking in advance :)

In terms of supporting this, I think you'll need to modify these bits:

https://github.com/karlicoss/orgparse/blob/9184c9a78053962de14057e69fc9221c74ba003f/orgparse/date.py#L137-L140 to parse the timezone information via the regex
https://github.com/karlicoss/orgparse/blob/9184c9a78053962de14057e69fc9221c74ba003f/orgparse/date.py#L339 _daterange_from_groupdict to extract the parsed timezone string from the regex match dictionary
https://github.com/karlicoss/orgparse/blob/9184c9a78053962de14057e69fc9221c74ba003f/orgparse/date.py#L194 _to_date to pass it further and construct the datetime object

Regarding extra dependency -- in theory, I wouldn't mind if it's not a required dependency, e.g. say you want to use library named tzparser:
try:
    import tzparser # (or whatever you want to use)
    tz = tzparser.parse(tzstr)
except ImportError:
    warnings.warn("Please install tzparser to parse timezone information")
    tz = None

Now regarding including this in orgparse -- I think considering it's not standard org-mode (but again, correct me if I'm wrong!), not sure how I feel about it. However, I think it would be possible to solve it for you without forking the library by monkey patching your code:
import orgparse.date
orgparse.date.TIMESTAMP_RE = ....
orgparse.date.OrgDate._daterange_from_groupdict = ...
orgparse.date.OrgDate._to_date = ...

# rest of your code that uses orgparse

That way the rest of library will be using the modified version of code, and hopefully handle timezone info. Do you think that could work for you?

Are you sure? I did a quick web search and also grepped org-mode sources, and it doesn't look like there is native timezone support.

Closing this since still not sure if it's actually standard org-mode, but feel free to reopen if it's a common usecase for some sort of org-mode plugin which you think we could support


ROS buildfarm does not compile F2C properly

Issue to discuss the progress about PR https://github.com/Fields2Cover/Fields2Cover/pull/133 and https://github.com/Fields2Cover/Fields2Cover/pull/134

Error returned by: https://build.ros2.org/job/Rbin_uN64__fields2cover__ubuntu_noble_amd64__binary/68/consoleFull#console-section-16
08:29:21 CMake Error at CMakeLists.txt:129 (find_package):
08:29:21   Could not find a package configuration file provided by "ortools" with any
08:29:21   of the following names:
08:29:21
08:29:21     ortoolsConfig.cmake
08:29:21     ortools-config.cmake
08:29:21
08:29:21   Add the installation prefix of "ortools" to CMAKE_PREFIX_PATH or set
08:29:21   "ortools_DIR" to a directory containing one of the above files.  If
08:29:21   "ortools" provides a separate development package or SDK, be sure it has
08:29:21   been installed.

The essence of the 1st build failure is replicated by the following script which effective comes from the  debhelper dh_auto_configure.
#!/bin/bash

mkdir -p build
cd build
DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX=/opt/ros/rolling -DCMAKE_PREFIX_PATH=/opt/ros/rolling -DBUILD_TESTING=OFF ..

The important setting being -DFETCHCONTENT_FULLY_DISCONNECTED=ON which fully disables the use of FetchContent during debian packaging.   The apparent reason why - https://salsa.debian.org/debian/debhelper/-/commit/5debbd6171dd2a091dde9ed499d8bb118ed2e1a8

cmake: set FETCHCONTENT_FULLY_DISCONNECTED to true
According to the documentation[1], FETCHCONTENT_FULLY_DISCONNECTED tells
the FetchContent module that no internet connection is available, and no
attempt at downloading dependencies at configure time is made, thus
speeding up builds.
Debian package builds are already made offline, and I don't expect this
to create any issue for users; it is thus enabled regardless of the
dh-compat level.

which leads to
https://cmake.org/cmake/help/latest/module/FetchContent.html#variable:FETCHCONTENT_FULLY_DISCONNECTED
which clarifies its intended use suggesting that this topic has been raised before.

Note The FETCHCONTENT_FULLY_DISCONNECTED variable is not an appropriate way to prevent any network access on the first run in a build directory. Doing so can break projects, lead to misleading error messages, and hide subtle population failures. This variable is specifically intended to only be turned on after the first time CMake has been run. If you want to prevent network access even on the first run, use a dependency provider and populate the dependency from local content instead.

The ros2 helper ament_vendor() gets away with it because it uses cmake's ExternalProject which does not respect FETCHCONTENT_FULLY_DISCONNECTED=ON.  However ament_vendor does use UPDATE_DISCONNECTED TRUE.  UPDATE_DISCONNECTED TRUE skips the update step.  It does not prevent the initial download step.
See https://github.com/ament/ament_cmake/blob/79cc237f8eb819edf4c1c624b56451e0a05a45f8/ament_cmake_vendor_package/cmake/ament_vendor.cmake#L290
And https://cmake.org/cmake/help/latest/module/ExternalProject.html#update-step-options

rosbag2 mcap_vendor gets away with it by overriding the debian rules by appending
-DFETCHCONTENT_FULLY_DISCONNECTED=OFF
See https://github.com/ros2-gbp/rosbag2-release/pull/10/files

This is the file that I think needs to change and then the appropriate bloom commands run.
https://github.com/Fields2Cover/fields2cover-release/blob/debian/rolling/fields2cover/debian/rules.em
https://wiki.ros.org/bloom/Tutorials/ReleaseThirdParty#Custom_Build_Commands

Note tweak to debian build option to correct repository here https://github.com/ros2-gbp/fields2cover-release/commit/33742dfb56d0ac606037c74742356833568d093f

Still not working. Now the main issue is "/usr/bin/ld: _deps/ortools-src/lib/libortools.so.9.9.3963: error adding symbols: file in wrong format" (https://build.ros2.org/job/Ibin_ujv8_uJv8__fields2cover__ubuntu_jammy_arm64__binary/85/consoleFull#console-section-16)

Still not working. Now the main issue is "/usr/bin/ld: _deps/ortools-src/lib/libortools.so.9.9.3963: error adding symbols: file in wrong format" (https://build.ros2.org/job/Ibin_ujv8_uJv8__fields2cover__ubuntu_jammy_arm64__binary/85/consoleFull#console-section-16)

This is because its an arm64 build variant.  The built release tarball being downloaded or ortools is for amd64.

Here is an attempt at supporting a arm64 variant - https://github.com/Fields2Cover/Fields2Cover/pull/141
I don't have one so only the build farm will let me know it if works.

https://build.ros2.org/job/Rbin_uJ64__fields2cover__ubuntu_jammy_amd64__binary/ is the build care about the most.  So YAY!
Rbin_uJ64 == Rolling Binary ubuntu jammy AMD64

Unfortunately, for jammy the last version compiled was v1.2.1. For v2, check https://build.ros2.org/job/Rbin_uN64__fields2cover__ubuntu_noble_amd64__binary/
08:13:22 -- or-tools -- Downloading and installing from release tarball
08:13:22 CMake Error at CMakeLists.txt:129 (find_package):
08:13:22   Could not find a package configuration file provided by "ortools" with any
08:13:22   of the following names:
08:13:22
08:13:22     ortoolsConfig.cmake
08:13:22     ortools-config.cmake
08:13:22
08:13:22   Add the installation prefix of "ortools" to CMAKE_PREFIX_PATH or set
08:13:22   "ortools_DIR" to a directory containing one of the above files.  If
08:13:22   "ortools" provides a separate development package or SDK, be sure it has
08:13:22   been installed.
08:13:22
08:13:22
08:13:22 -- Configuring incomplete, errors occurred!
08:13:22 	cd .obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
08:13:22 dh_auto_configure: error: cd .obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTING:BOOL=OFF -DCMAKE_INSTALL_PREFIX=/opt/ros/rolling -DCMAKE_PREFIX_PATH=/opt/ros/rolling -DBUILD_TESTING=OFF .. returned exit code 1
08:13:22 make[1]: *** [debian/rules:36: override_dh_auto_configure] Error 2

I have seen that DFETCHCONTENT_FULLY_DISCONNECTED=ON on the error message above. rules.em was modified to disable it, tho

Unfortunately, for jammy the last version compiled was v1.2.1. For v2, check
Ah, spoke too soon.  Saw a green and mis-read the date.

I have never done a bloom release myself either.
I was hoping/guessing that a change to debian/rolling/fields2cover would be enough to cover all rolling branches.
...
I see you just made some changes - https://github.com/ros2-gbp/fields2cover-release#fields2cover-rolling---200-12.
Here's hoping.

I've just released your PR to support arm. Lets see if that solves the problem.  Green again for amd on everything, and for  arm only on rolling (due to being the only one released yesterday). I hope we can have everything green for amd and arm on the next release!!! Missing rhel6 tho, but maybe is being to ambitious.
https://build.ros2.org/job/Rbin_uN64__fields2cover__ubuntu_noble_amd64__binary/
https://build.ros2.org/job/Rbin_unv8_uNv8__fields2cover__ubuntu_noble_arm64__binary/
https://build.ros2.org/job/Jbin_uN64__fields2cover__ubuntu_noble_amd64__binary/
https://build.ros2.org/job/Ibin_uJ64__fields2cover__ubuntu_jammy_amd64__binary/
https://build.ros2.org/job/Hbin_uJ64__fields2cover__ubuntu_jammy_amd64__binary/
Thank you again @aosmw, I cannot stress you enough how good you are :clap:

Great!!!
rhel6 is surely too old.  Got a link?

https://build.ros2.org/job/Rbin_rhel_el964__fields2cover__rhel_9_x86_64__binary/186/consoleFull#console-section-14

https://rhel.pkgs.org/9/epel-x86_64/geos-devel-3.10.1-1.el9.x86_64.rpm.html provides /usr/include/geos_c.h

Thank you, I will try this

As all the ROS versions are working now (except for rhel), I think we can safely close this issue. Thank you for your awesome work @aosmw!! I still can't believe it's working now


FIxed FOrm errors and eye icon

Related Issue
Closes #1241

Description
This pull request addresses two issues in the Login component:

Corrected the placement of onClick={login} in the login form. Previously, the onClick event was erroneously placed on the form tag, causing validation to trigger on any form element change. I've moved the onClick event to the login button to ensure it triggers only when the login button is clicked.

Added a password visibility toggle feature to the password input field. I've implemented an eye icon that toggles between showing and hiding the password text when clicked. The icon changes color and the password visibility changes accordingly.

This fixes the issue of validation errors appearing without submitting the form and enhances the user experience by providing a password visibility toggle feature.
Changes Made

Moved onClick={login} from the form tag to the login button to trigger login only on button click.
Added a password visibility toggle feature to the password input field using the eye icon.
Styled the eye icon to change color based on password visibility.

Screenshots (if applicable)
https://github.com/rohansx/informatician/assets/85815172/21773706-818d-4e5c-b4c0-01d8148205df
Please review and merge this pull request to improve the behavior and user experience of the login form.
Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

@Nishitbaria ,please review and merge my pull request


D415 does not work with PCI-e USB expansion port

Required Info

Camera Model
D415

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
5.4.0-80-generic

Platform
PC

SDK Version
2.48.0

Language
realsense-viewer

Segment
Others

Issue Description
I am using Intel D415 cameras and the realsense-viewer is able to work perfectly fine when it is plugged into the USB 3.2 port that comes with the computer. However, I want to plug this into the PCI-e to USB 3 expansion port for a multi-camera setup. When I plug one camera into it, I encountered errors. I unplugged and re-plugged it many times and sometimes, I only get the RGB stream to show up on the viewer, other times only the depth stream shows up, and sometimes none of the streams show up. I was wondering if there was a way to stream both RGB and depth footage consistently with the PCI-e expansion port.
The following error occurs when I connect the camera into the PCI-e expansion port, successfully turn on the RGB stream, and then try to turn on the stereo stream:
Backend in rs2_open_multiple(sensor:0x555b95d45810, profiles:0x555b970b3590, count:1): set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Connection timed out
Here is the link for the expansion card that I am using:
https://www.amazon.ca/gp/product/B0836QPCJ9/ref=ox_sc_saved_title_1?smid=A1BM86NEBPKXB0&psc=1

Hi @ritviksingh9  There was a past case in https://github.com/IntelRealSense/librealsense/issues/6899 regarding the camera not working correctly in a pci-e expansion port but working normally when plugged in directly.  In that particular case, it was thought to be due to the USB controllers that the pci-e expansion was using compared to the USB controllers that the computer's USB port used.
The RealSense user in that case, who was also using Ubuntu, developed a bash script as a workaround to rebind the USB drivers before enabling the camera stream.
https://github.com/IntelRealSense/librealsense/issues/6899#issuecomment-671984909

Okay thanks, will check out!

Hi @ritviksingh9  Do you require further assistance with this case, please?  Thanks!

Unfortunately, the fix did not work. The website also suggested to reset the USB ports but when we tried that the PCI-e expansion card still did not work.

So to confirm, rebinding the USB drivers does not solve the problem no matter which method is used to do so, please?

Yep. When we unbind and then bind the USB drivers it does not solve the problem of the Realsense not being recognized.

When the PCI-e card was installed into the PC, can you confirm that it was connected up to the power supply unit (PSU) inside the PC?  The power lead supplies the PCI-e board with 5V that enables the board to be to provide ports with sufficient power when USB devices with a high power draw (such as a RealSense camera) are attached.  If the board was simply plugged into the PCI-e slot without the power cable attached then it might only be able to handle low power draw devices such as mouse and keyboard.
The image below is taken from the Amazon product listing for the board that you kindly provided at the beginning of this case.

Yes, we made sure to connect the SATA power cable from the PCI-e board to the PSU.

If you are using a PCI-e board for the sake of keeping cables tidy, I wonder if you could achieve the same with a mobile USB 3 hub that has a very short USB cable connecting it to the computer  You can find examples of them on Amazon by searching for mobile usb hub

Hi @ritviksingh9  Do you have an update about this case that you can provide, please?  Thanks!


Audacitorch install prevents import of torchaudio

I've trained a model that acts on MFCCs I get using torchaudio.  When I installed audacitorch to wrap my model (in Colab), it prevents me from importing torchaudio with the message OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory.  It looks like installing audacitorch uninstalls and re-installs torch - might that have something to do with it?

Here's the full error: `/usr/lib/python3.7/ctypes/init.py in init(self, name, mode, handle, use_errno, use_last_error)
362
363         if handle is None:
--> 364             self._handle = _dlopen(self._name, mode)
365         else:
366             self._handle = handle
OSError: libtorch_cuda_cpp.so: cannot open shared object file: No such file or directory`

Hi! What version of audacitorch are you trying to use? You will probably need to use torchaudio==0.9.0, since audacitorch uses torch 1.9.1

Yes thanks that worked!

happy to help:)


Implement solution for build your own story book

Apart from the code, there should be a brief description for this PR as well telling what this PR does and what problem does it solve.


Selenium stuff

Add the ability to "hijack a session" by clicking on a fancy button, use selenium to setup the session cookies and launch it.
Unsure if its better to use the remote java server or a specific driver and embed those into the binary, or download on first run... or download to memory?

Basic selenium support added with commit 8e65f029b34a6d3cb75eb89a06149912dae1804d


url router test utility

Here is a proposal for making testing routes easier. What do you think?

Looks like a really useful idea. One thing I was wondering (sorry if this is obvious form the implementation, I still have to take a closer look) is if it would be feasible to implement basically the same API, but only using directly HTTPServerResponse, by employing some UFCS. Instead of just URLRouter, it would also make sense to allow any HTTPServerRequest(Delegate/Function/Handler) as the target.

I'm not sure I understand... where do you expect to send a HTTPServerRequest? As I know a server request is represented as an object not as a Delegate/Function/Handler.
I will try to remove the test server class and use a HTTPServerResponse. I know that I am using this way of testing inside a project and for some reason I was not able to use the HTTPServerResponse. I will try again and post here more details :)

ping @s-ludwig

Sorry for losing track of this. I just got reminded of it due to recent forum thread.
So since URLRouter itself inherits from HTTPServerRequestHandler, it would be a simple generalization to let request(...) take a HTTPServerRequestHandler, as well as any of the other handler types.


Modal sizes

How can I set the modal sizes? sm, md, lg and xl?
Please assist.

@pavangayakwad It doesn't have size. But you can use width/height utility classes like w-96 or h-96
Please let me know if you have any questions.

Thanks for your quick reply.
It seems the sizes are not really affecting even when I set something like

or

.
The w-{} have limited sizes so I was exploring other large size options.

@pavangayakwad
Try adding a max-w-full as well

This worked like a charm!
Updating the documentation with details should help who are looking for these tweaks! This is approach is far far better idea than giving limited sm, md, lg, xl kind of settings.
Indeed a great work from you guy!!! keep it going! 👍 and Thank you very much @saadeghi for taking time and responding.


Use 2 ppxes for jsx again

Turned out using a single ppx + using a CLI flag isn't ideal because of the way flags are handled + paths that contain spaces.

cc @bobzhang


About the Preprocessing of input images.

This project used different preprocessing method with the Pytorch pretrained models. The pretrained models use RGB values normalized to [0, 1]. While in pytorch-fcn, images are BGR values and not normalized to [0, 1], only center normalized. So how did it works?
See this on pytorch discuss:
All pretrained torchvision models have the same preprocessing, which is to normalize using the following mean/std values: https://github.com/pytorch/examples/blob/master/imagenet/main.py#L92-L93164 (input is RGB format)
[ref: https://discuss.pytorch.org/t/how-to-preprocess-input-for-pre-trained-networks/683/2]

I use VGG16 model pretrained using caffe, and distributed at Caffe-Zoo. And that's why I use different preprocessing.
This is common, and the original author of FCN also used that model.


Switch to go mod

I propose to use go modules instead of dep. What do you think?
Benefits:

go mod is a nearest future
work outside GOPATH

#28


Create Copy a specific element based on its language attribute

Added rule based on Pau's issue. Added generic example and attribution.

Approved for merge.


Contribute to http-interop

PSR-17 is an upcoming proposal that will standardize HTTP Message factories. The work of defining the actual interfaces is happening right now in @http-interop http-factory repository.
Can we work together to make http-interop/http-factory the standard moving forward?

I know that I have expressed doubt about HTTPlug in the past and I do still have reservations. That said, the foundational work around having a set of standard PSR-7 factories is extremely important for the adoption of PSR-7 and benefits the entire PHP ecosystem.
Here's to looking forward instead of back! 🍻

We sure had some discussions which have shocked me because I know we want to achieve the same goal. I also share your concern about the importance of the PSR-7 factories.
I'm happy that you reached out and asked this question. And of course, let's work together 🍻

Hi Woody,
Thanks for reaching out, I really look forward to work on this. I've already gone through the current interfaces. If I saw correctly, the inheritance has been removed, which is great IMO.
As far as I can see Diactoros is the only implementation, so I would like to support this project by the following:

Create an unofficial Guzzle implementation if I can't find any (sane one)
Create a bridge between our factories, so eventually we can deprecate our vendor factories (Diactoros and Guzzle) and use "official" ones without breaking BC in our packages
Once this proposal reaches standard phase, deprecate this factory package and recommend PSR-17

At least this is the roadmap I can see regarding PHP HTTP packages.
As for actual contribution: I will look at the interfaces more closely. @dbu and I will have a workshop @ Web Summer Camp where we can advocate PSR-17. Apart from that, I think the most useful contribution at this stage is to use the interfaces and find any possible problems. Given the similarities between our interfaces and the proposed PSR-17 ones, I wouldn't count on too many. In fact, I would like to see this the fastest standard to be accepted.
About personal things: this is not the FIG. Although you (and me, everyone) got used to the political and personal issues affecting work within the FIG, I really think this is NOT the way professional work should happen. As long as the personal or any other issues does not affect the ongoing work (as I expressed on the thread you asked Paul to step down), I don't really care what other conflicts/disagreements we have.

when we started with the message factory interfaces (and the client interface, as well) we all agreed that both things would best fit into a PSR as they are meant to be a general standard. and a general standard by a standardization group is much better than a standard by an ad-hoc group. i agree with @sagikazarmark and hope to eventually deprecate the php-http/message-factory interfaces and point people to PSR-17.

Now that PSR-17 has been ratified, would you be open to a pull request that has each of the interfaces here extending the PSR interfaces? I think this would require a major version bump, since there are a few differences that would provide BC breaks (i.e. difference in signature of Psr\Http\Message\UriFactoryInterface::createUri() and additional required methods in Psr\Http\Message\StreamFactoryInterface).
If you're open to it, I can put together a PR.
(Background: I just ran into a problem trying to use UriFactoryDiscovery::find() with a method that expects a Psr\Http\Message\UriFactoryInterface object. Unfortunately, I can't use the discovery method because non of the classes in Http\Message\UriFactory implement the PSR interface.)

@ramsey you might be interested in http-interop/http-factory-discovery.

@shadowhand Oh, nice! I wasn't aware of the http-interop project. Thanks!

@ramsey it's where the PSR-17 interfaces were prototyped. We're keeping it around to provide utility packages for PSR-15/17.

I think instead of implementing the interface this package should be deprecated instead together with the implementations (where it makes sense).
I would assume (or kinda hope) that the PSR-17 implementations will move next to the PSR-7 implementations (Guzzle, Diactoros and Nyholm PSR-7 being the three major ones).
PSR-18 is also going to be accepted soon being a big change for the PHP-HTTP ecosystem, so if it brings breaking changes (we hope it won't) then switching to PSR-17 in the same step will probably happen as well.


Install B9S Using Seedminer

This is a valid method for installing B9S on a user's 3ds that I think should be included in the guide. It allows for single system dsiware injection.
Gbatemp:
https://gbatemp.net/threads/seedminer-single-system-dsiware-injection.495685/
Github:
https://github.com/zoogie/seedminer

I think you should simply link to jisagi's guide (https://jisagi.github.io/SeedminerGuide/) instead of completely remaking a guide.


Use macros in the README examples

Use the matrix! and assert_matrix_eq! macros in the README examples.
Resolves #130

Great, thanks!


_yosys fails to parse Yosys version from fomu-toolchain

I have been yosys and nextpnr-ice40 from v1.5.6 of the fomu-toolchain, downloaded from https://github.com/im-tomu/fomu-toolchain/releases/tag/v1.5.6
The version number reported by the fomu-toolchain build of yosys is not compatible with the version number parser in _yosys.py. Here is the traceback from calling platform.build():
Traceback (most recent call last):
  File "./video.py", line 203, in <module>
    buildAndRunTest(DEMOS[args.demo], RESOLUTIONS[args.resolution], args.seed, args.optimize, args.program)
  File "./video.py", line 176, in buildAndRunTest
    platform.build(demo(resolution),
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/build/plat.py", line 90, in build
    plan = self.prepare(elaboratable, name, **kwargs)
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/build/plat.py", line 163, in prepare
    return self.toolchain_prepare(fragment, name, **kwargs)
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/build/plat.py", line 437, in toolchain_prepare
    render(content_tpl, origin=content_tpl))
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/build/plat.py", line 419, in render
    return compiled.render({
  File "/home/osboxes/ib/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/home/osboxes/ib/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/home/osboxes/ib/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 2, in top-level template code
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/build/plat.py", line 314, in emit_debug_verilog
    return verilog._convert_rtlil_text(rtlil_text,
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/back/verilog.py", line 10, in _convert_rtlil_text
    yosys = find_yosys(lambda ver: ver >= (0, 9))
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/_yosys.py", line 211, in find_yosys
    if proxy.available() and requirement(proxy.version()):
  File "/home/osboxes/ib/lib/python3.8/site-packages/nmigen/_yosys.py", line 154, in version
    return (int(match[1]), int(match[2]), int(match[3] or 0))
TypeError: 'NoneType' object is not subscriptable

The above message is due to match being None, since the regex match failed.
Here is the yosys version string from the fomu build of yosys:
$ yosys -V
Yosys 7f5c73d58fd732a96e480083896cd73c722849ba (Fomu build) (git sha1 66613d5, gcc 7.4.0-1ubuntu1~18.04.1 -fPIC -Os)

Here are a couple of possible solutions:

nMigen could reject unversioned yosys binaries and fallback to nmigen-yosys, if available.
nMigen could accept unversioned yosys binaries, but with a warning
request fomu-toolchain to build yosys binaries so that they report a version number that is parsable by nMigen
nMigen could be left incompatible with fomu-toolchain

Of these, think 1 is best. I'm happy to try making a PR for either 1 or 2.

It is not possible to do option 2, since the output of nMigen has to be customized for the Yosys version it works with (RTLIL is not stable); so option 1 seems sensible.

Will do.

I would be fine with (3) but I think we should do (1) in parallel, since this is probably not the last time we encounter such Yosys builds.


open notebook in hue home just jump to new notebook

when I want to open a saved notebook on home page, it will jump to open a new notebook not my saved one, only if you  open the saved notebook from left sidebar documents, then you can open your saved notebook, I think it's a bug?

hi! do you have more info for us? which version? or from master? what browser are you experiencing this in?

I encountered the same problem，the version of hue is 4.0.1，and used hue4 web view

my solution is: hue.mako 995 line
if (window.location.getParameter('notebook') !== '') {
changed as
 if (page.current.indexOf("notebook=")>=0) {

Thanks! Actually it's a bug just when the notebook app has not been loaded yet, I opened https://issues.cloudera.org/browse/HUE-7138 to keep track of it


Plan for jump feature?

Not currently.
If need be, it's pretty straightforward to extend with jumping, while instantly getting into game-specific behaviour and feel, as well as adding further complexity to the movement code. This conflicts with this project's goal to be a simple, stable, off-the-shelf starting point.


Update the source information

Type: Missing
Summary:
Update the source information
Details:
With the rise in supply chain attacks and OSS dependencies being used as a attack vector, Microsoft is working with our ecosystem partners, such as the Linux Foundation's OpenSSF, to enable OSS consumers to track packages back to their public sources.
Resolution:
This PR was created to add this value, ensuring future releases will include this provenance information.
Published NPM packages with repository information:
* smart-mixin
Affected definitions:

smart-mixin 2.0.0

Other packages by this author point to this GitHub user account. Approved.


Memory Growing Issue

just install sample project. Run on an emulator. Open Memory Monitor. Scroll up and down with several times. Memory is growing. Sometimes GC start, but cannot release more memory. Always call GC.
Any idea on this issue?
Thanks

I checked by sample project.
By scrolling up and down multiple times, memory usage grows and once GC starts, some memory gets released. Memory usage will be grown if no other application needs any memory. But once the memory usage is grown to the limit, memory is released and not increase any more.
I believe this is normal behaviour.


west: warn that using runner args on multiple domains is experimental

The introduction of sysbuild and west build / flash / debug / etc.
support raises questions regarding how to handle user specified runner
arguments.
Some arguments may be acceptable for all domains, whereas others are
only valid for a single or few domains in a multi domain build.
Therefore, consider the usages of runner specific options experimental
when applied to multiple domains.
The following warning is printed to the user when using runner specific
arguments on multiple domains:
WARNING: Specifying runner options for multiple domains is experimental.
If problems are experienced, please specify a single domain using '--domain <domain>'

Signed-off-by: Torsten Rasmussen<EMAIL_ADDRESS>

I have a memory that we agreed to limit sysbuild's scope to only what it knew it could support, not just allowing everything (even with a warning like this).

I remember we briefly touched upon the subject, but I don't recall that we ever reached a conclusion at the time.
@mbolivar-nordic I see the warning as a temporary solution until we have discussed and designed properly how we want sysbuild and west runners to handle more complex scenarios.
For a start, let's look at --dev-id and some use-cases:

A simple sample, like blinky + MCUboot for a single code SoC, nrf52840.
In this case, allowing west flash --dev-id 1234 will make it possible for a user to flash a specific board when multiple boards are connected, instead of:
west flash --domain mcuboot --dev-id 1234 + west flash --domain blinky --dev-id 1234
Secondly, doing two operations bear the risk of the user flashing in wrong order (mcuboot default will mass erase).
So allowing --dev-id in this case make life easier.

A dual core sample, for example bluetooth app + HCI RPMsg + mcuboot, dual core Soc like nRF5340.
In this case, both cores can be accessed through the same debugger chip which means west flash --dev-id 1234 will make it possible for a user to flash a specific board with such dual core SoC, again instead of:
west flash --domain mcuboot --dev-id 1234 + west flash --domain blinky --dev-id 1234 + west flash --domain hci_rpmsg --dev-id 1234
Now in this case three commands to handle for the user.
So allowing --dev-id in this case also is still making life easier.

Advanced multi board sample, for example Bluetooth LE audio gateway on board 1, Bluetooth LE audio headset on board 2.
Imagine this sample turned into sysbuild infrastructure: nRF5340 Audio
Notice how that  application has it's own buildprog.py for building both a gateway and a headset,
In this case, building for two dev-kits are easy.
Flashing them can be a little bit trickier.
Two dev-kits will be having different debugger chips.
This means west flash --dev-id 1234 becomes meaningless.
User will have to decide what goes where, for example:
west flash --domain gateway --dev-id 1234 + west flash --domain headset --dev-id 4321

Should we block users in use-case 1) and 2) from using --dev-id in a multi-domain because it will not work in use-case 3) ?
I believe use-case 1) and 2) might be majority of users, and use-case 3) a special case.
I therefore believe that for now we should inform the user that multi-domain and extra runner args are experimental, and then continue the discussion on how to proceed forward with good user-experience and how to handle all those new use-cases that will emerge.
Instead of directly block arguments that may make life easier for majority of users.
The warning is a temporary solution, because I believe this topic is very important and requires more thoughts and discussions.
Until then, the support of runner args is experimental, because we might decide to block some / all runner args.
We might want to invent a new scheme for allowing users to direct a given runner arg to a single / multiple domains.
Informing this is experimental allows us to change this support as we like.

OK, I am fine with that. You have convinced me. Thanks.

I don't recall the discussion in detail, but @tejlmand's explanation also convinced me.


Missing resolve param behavior

Update resolve function param to destructuring.

Thanks for PR, Please make shure you use commitizen next time 😉

Another thing is I found that when I add resolver mutation to Mongoose type composed object
UserTC.addResolver({
  name: 'createUserByCustomData',
  kind: 'mutation',
  args: {
    email: 'String',
    password: 'String',
  },
  type: UserTC,
  resolve: ({ _, args, context, info }) => {
    console.log(args); // args is inside object param
    return {
      email: 'Unimplement yet',
    };
  },
});

but if add it directly in GQC
helloMutate: {
    type: 'String',
    resolve: (_, args) => {
      console.log(args); // args is receive in second param
      return 'hello';
    },
  },

@zapkub
First of all, thanks for PR.
Commitizen messages will be very cool, but anyway we can Squash and merge your changes with changing commit message. Due commit messages Travis with semantic releasing decides publish new version or not:

docs(Mutations): Missing resolve param behavior just run tests, no new version
feat(Mutation): Something run tests and publish new package with minor version 0.X.0
fix(Mutation): Something run tests and publish new package with patch version 0.0.X
You may watch free courses about automatically publishing modules (if it's interesting to you): https://egghead.io/lessons/javascript-how-to-write-a-javascript-library-automating-releases-with-semantic-release

What about
resolve: ({ _, args, context, info }) => {
// vs
resolve: (_, args) => {

Yep, this is some tricky unobvious part. Try to explain.
When you works with regular GraphQLFieldConfig resolve method without any wrappers:
TC.setField('helloMutate', { // starting of graphql fieldConfig
  type: 'String',
  description: 'My mutation',
  resolve: (_, args) => {
    console.log(args); // args is receive in second param
    return 'hello';
  },
});

But when you work with graphql-compose Resolvers and relations a standard graphql resolver is wrapped and its arguments passed as one object (named resolveParams or rp). Also to this object added parsed projection from queryAST and other useful object which may be required.
Eg graphql-compose-mongoose

adds query to rp for debugging
you may provide rp.rawQuery which used by filterHelper in resolvers with filtering, eg findMany
add rp.beforeRecordMutate: Promise to do additional checks/work with doc before changing/removing

So graphql-compose's  resolveParams (rp) provides an ability to pass/read data to/from the underlying implementation.
Maybe it should be standardized, and I should wrap standard GraphQL resolver in fieldConfigs. But for now, I see that it brings runtime performance degradation.

PS. Somewhere at 14-15 April, I will be in BKK. And we can meet w/ beer in some shopping center, while my wife will be shopping. @katopz already on https://twitter.com/katopz/status/838019621709987840


Can't be installed from BRAT

BRAT
oscarspalk/obsidian-git-sync
The release is not complete and cannot be download. main.js is missing from the Release.

Release 1.0.4 should contain all files for a functional plugin.


Retrieve intent extra through CropImageActivity

Hi.
It's more of an enhancement than an issue.

An exemple :
I have a recyclerview listing my friends. When I select a friend, it opens the image picker/cropper like this:
CropImage.activity()
                .setGuidelines(CropImageView.Guidelines.ON)
                .start(this)
The problem is that, in onActivityResult, I don't know which friend was selected.
Currently, the only way I found to correct this, is to have a global variable "Friend", that I assign before starting the CropImageActivity, and I use it in onActivityResult.
It works, but it's not the best way to do it. I think it would be better if I could do it like that:
Intent cropIntent = CropImage.activity().getIntent(this);
cropIntent.putExtra("friend", friend);
onActivityResult:
Friend selectedFriend = resultIntent.getParcelableExtra("friend");
Don't you think it would be a good idea?

added in 2.5.1

Is it possible to propagate extras for the PickImageChooserIntent as well?

@ArthurHub  can you explain how can i use this library in fragment and send extra data by example?


"dependencies" error

The dependencies code needs some "relaxing". Even --no-strict-dependency had NO EFFECT on these.
{
 "dependencies": []
}

Should be fine, indicating no dependencies known at present. But it doesn't work.
Similarly, only the name attribute of an entry should be required. The version information should be optional.
     "issues_url": "",
     "dependencies": [
        { "name": "puppetlabs/stdlib" }
     ]
    }

Similarly, if the "version_requirement" tag is specified, its contents could/might be empty.

  "issues_url": "",
  "dependencies": [
    { "name": "puppetlabs/stdlib", "version_requirement": "" }
  ]
}

also doesn't work.
Work-around: add a "0" to the version_requirement

@electrical whatcha think?

So I've gone ahead and reverted #9 and released 0.0.6 to rubygems. Hopefully that will fix things. I think the feature is cool but there are a number of problems that came out of it which weren't getting fixed.


hide elements

Add all the stuffz here
is it possible to give hide this elements?

this would give a cleaner experience

You can use these flags:
chrome://flags/#disable-thorium-icons to disable colors.
chrome://flags/#chrome-labs Set to "Disabled"
chrome://flags/#hide-sidepanel-button
Note that the Extensions icon can't be removed.

thx


Support mini_portile ~> 2

This PR inlines the cmake support from mini_portile2 2.2.0rc so that this gem will be compatible with the latest release version of mini_portile.
My use-case is using  image_compressor_pack in a Rails project alongside nokogiri, which has a dependency conflict with the 2.2.0rc version of mini_portile.
It's a bit of a hack so feel free to close, just thought I'd share what worked for me.
Thanks for the gem!

Thank you for taking the time to contribute patches ❤


Set up branch

Changes:

Install React

Hi @vflorin1995,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have implemented the wrong workflow. According to gitflow you should merge to the develop branch, not the main branch.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Getting error "Error: helm-charts chart not found in repo https://nerdswords.github.io/helm-charts"

Executed "helm repo add nerdswords https://nerdswords.github.io/helm-charts"
then executing " helm dependency update ."
getting error :- Error: helm-charts chart not found in repo https://nerdswords.github.io/helm-charts
Can anyone please help

@tarvez05 did you manage to solve this problem?

Closing due to staleness, feel free to re-open in case you need any further help.


Documentation refers to incorrect UI options in Docker Container logging

The page https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#troubleshooting mentions that

To log the stdout and stderr from your container, you need to enable Docker Container logging under App Service Logs.

There is no "Docker Container" option under App Service Logs. It is not clear what is needed to enable logging for Docker containers.

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

ID: ef9002ed-c817-c615-fe32-05ad4cc78b61
Version Independent ID: 72295255-8d90-a2c6-0995-0e1208fcdcab
Content: Introduction to App Service on Linux - Azure
Content Source: articles/app-service/containers/app-service-linux-intro.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

@haschdl Thanks for the feedback! We are currently investigating and will update you shortly.

@haschdl Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

The option to enable is "Application Logging" under App Service Logs

@msangapu-msft can you confirm? Will "Application logging" turn on the Docker container logs?

Hi team, sorry for the delay. Yes the "Application Logging" will enable Docker Container logs. I will update the doc today.

Changes were merged to master: https://github.com/MicrosoftDocs/azure-docs-pr/pull/97318
#please-close


Play positive feedback sound as the written feedback text appears

User Story
As a UX designer,
I want to play this positive feedback sound when the animation for the written feedback text to display plays,
So that we are giving enough positive feedback and encouragement through SFX to keep engagement in the task going.
Video reference from FTM Unity-- it's played when the graphical shine goes from right to left which is after the feedback phrase "Superb!" is spoken
Acceptance Criteria
Given that we have answered a question correctly,
When the written feedback text begins to appear,
Then I should hear this sound effect and the spoken language audio of that feedback.

@burrage Hiii Ben, Here actually the positive feedback sound is added but it plays after the Feedback text animation (can be observed in the below video which i have attached), so we had a doubt that should it play when the text animation starts? . Please give your valuable feedback on this.
Thank you.
https://github.com/curiouslearning/FeedTheMonsterJS/assets/99384703/02896d71-a59f-45e7-9f53-ad4222c0f709

@Ashish1998 Could I see it playing when the text animation starts please? I want to make sure the experience feels like it isn't taking a long time between questions and that might shorten the time (?) while still giving the right amount of sound feedback (it's feeling better!)
Thanks!


API(s) to support modification

Spec out one or more API(s) to support the addition of an overlay, and to update the relevant image manifest/config and root index after an overlay is modified (https://github.com/sylabs/singularity/issues/1480). Also see discussion in https://github.com/sylabs/oci-tools/pull/46.

Assuming we are following the flow for Singularity detailed in https://github.com/sylabs/singularity/issues/1480 we need to be able to perform 2 modification operations for minimal functionality, with an additional 'seal' operation if we wish to allow images with overlays to be finalized and / or pushed to an OCI registry as an OCI image with r/o tar layers.
1. Add EXTFS Overlay
We must be able to add an extfs overlay, of configurable size, to the SIF file. The overlay will be added to the image config as an additional layer with an extfs mediaType. The image config, manifest, and RootIndex will be updated so that all hashes are consistent at the time of insertion of the extfs overlay layer.
To avoid re-writing the entirity of the SIF file, we would need to enforce that all existing image layers are located at the start of the SIF file. Large images can have many and large layers, so we don't want to re-write the whole SIF if at all possible.
For an image with N layers - Before:

descriptor id
type
content

1
OCI.Blob
SquashFS layer

...
OCI.Blob
SquashFS layer

N
OCI.Blob
SquashFS layer

N+1
OCI.Blob
Image Config

N+2
OCI.Blob
Image Manifest

N+3
OCI.RootIndex
Image Index

After the addition of an extfs overlay:

descriptor id
type
content
state

1
OCI.Blob
SquashFS layer
Unmodified

...
OCI.Blob
SquashFS layer
Unmodified

N
OCI.Blob
SquashFS layer
Unmodified

N+1
OCI.Blob
EXTFS overlay layer
New

N+2
OCI.Blob
Image Config
Updated

N+3
OCI.Blob
Image Manifest
Updated

N+4
OCI.RootIndex
Image Index
Updated

2. Update Metadata
As the EXTFS overlay layer is modified, the image config, manifest, and RootIndex will become inconsistent w.r.t. the hash for the extfs overlay layer. Due to concurrency issues, the risk of batch jobs being killed etc. in the SingularityCE use case it is probably not practical to update the image config, manifest, root index after each use of the overlay in r/w mode. However, before we share the image in a registry, we need the hashes to be correct.
We must have an operation that updates the image metadata, rewriting image config, manifest, rootindex appropriately.
Before metadata is updated:

descriptor id
type
content

1
OCI.Blob
SquashFS layer

...
OCI.Blob
SquashFS layer

N
OCI.Blob
SquashFS layer

N+1
OCI.Blob
EXTFS overlay layer

N+2
OCI.Blob
Image Config

N+3
OCI.Blob
Image Manifest

N+4
OCI.RootIndex
Image Index

After metadata is updated:

descriptor id
type
content
state

1
OCI.Blob
SquashFS layer
Unmodified

...
OCI.Blob
SquashFS layer
Unmodified

N
OCI.Blob
SquashFS layer
Unmodified

N+1
OCI.Blob
EXTFS overlay layer
Unmodified

N+2
OCI.Blob
Image Config
Updated

N+3
OCI.Blob
Image Manifest
Updated

N+4
OCI.RootIndex
Image Index
Updated

3. 'Seal' Overlay
When a user has finished modifying an image via an overlay, we may wish to allow them be able to 'seal' the image. This will convert the EXTFS overlay layer into a SquashFS layer.
Sealing an overlay - into a r/o layer - is also a prerequisite for being able to subsequently push the image in tar layer format, compatibile with other runtimes.
Before image is sealed:

descriptor id
type
content

1
OCI.Blob
SquashFS layer

...
OCI.Blob
SquashFS layer

N
OCI.Blob
SquashFS layer

N+1
OCI.Blob
EXTFS overlay layer

N+2
OCI.Blob
Image Config

N+3
OCI.Blob
Image Manifest

N+4
OCI.RootIndex
Image Index

descriptor id
type
content
state

1
OCI.Blob
SquashFS layer
Unmodified

...
OCI.Blob
SquashFS layer
Unmodified

N
OCI.Blob
SquashFS layer
Unmodified

N+1
OCI.Blob
SquashFS layer
New - conversion of extfs layer

N+2
OCI.Blob
Image Config
Updated

N+3
OCI.Blob
Image Manifest
Updated

N+4
OCI.RootIndex
Image Index
Updated

1. Add EXTFS Overlay
We must be able to add an extfs overlay, of configurable size, to the SIF file. The overlay will be added to the image config as an additional layer with an extfs mediaType. The image config, manifest, and RootIndex will be updated so that all hashes are consistent at the time of insertion of the extfs overlay layer.
To avoid re-writing the entirity of the SIF file, we would need to enforce that all existing image layers are located at the start of the SIF file. Large images can have many and large layers, so we don't want to re-write the whole SIF if at all possible.
For an image with N layers - Before:
descriptor id	type	content
1	OCI.Blob	SquashFS layer
...	OCI.Blob	SquashFS layer
N	OCI.Blob	SquashFS layer
N+1	OCI.Blob	Image Config
N+2	OCI.Blob	Image Manifest
N+3	OCI.RootIndex	Image Index
After the addition of an extfs overlay:
descriptor id	type	content	state
1	OCI.Blob	SquashFS layer	Unmodified
...	OCI.Blob	SquashFS layer	Unmodified
N	OCI.Blob	SquashFS layer	Unmodified
N+1	OCI.Blob	EXTFS overlay layer	New
N+2	OCI.Blob	Image Config	Updated
N+3	OCI.Blob	Image Manifest	Updated
N+4	OCI.RootIndex	Image Index	Updated

I think there are a couple of steps here. At a minimum:

Construct an updated v1.Image with the EXTFS layer and updated image config/manifest. mutate.AppendLayers can be used for this purpose. You would need to construct a v1.Layer containing the EXTFS filesystem, which is probably best done in the SingularityCE code base?
Replace the original v1.Image with the updated v1.Image. Here, we probably need an API in github.com/sylabs/oci-tools/pkg/sif. Perhaps something like:

func Update(path string, ii v1.ImageIndex, opts ...UpdateOpt) error

Update would expect an OCI-SIF at path and replace its rootIndex with ii. The logic for this could be something like:

Generate a list of all OCIBlob digests referenced by ii, and digest of new rootIndex.
Remove all SIF descriptors not in the list of references (including rootIndex if it's been updated.)
For each descriptor in the list of references, check if the blob is already in the SIF. If not, add it to the SIF.

2. Update Metadata
As the EXTFS overlay layer is modified, the image config, manifest, and RootIndex will become inconsistent w.r.t. the hash for the extfs overlay layer. Due to concurrency issues, the risk of batch jobs being killed etc. in the SingularityCE use case it is probably not practical to update the image config, manifest, root index after each use of the overlay in r/w mode. However, before we share the image in a registry, we need the hashes to be correct.
We must have an operation that updates the image metadata, rewriting image config, manifest, rootindex appropriately.
Before metadata is updated:
descriptor id	type	content
1	OCI.Blob	SquashFS layer
...	OCI.Blob	SquashFS layer
N	OCI.Blob	SquashFS layer
N+1	OCI.Blob	EXTFS overlay layer
N+2	OCI.Blob	Image Config
N+3	OCI.Blob	Image Manifest
N+4	OCI.RootIndex	Image Index
After metadata is updated:
descriptor id	type	content	state
1	OCI.Blob	SquashFS layer	Unmodified
...	OCI.Blob	SquashFS layer	Unmodified
N	OCI.Blob	SquashFS layer	Unmodified
N+1	OCI.Blob	EXTFS overlay layer	Unmodified
N+2	OCI.Blob	Image Config	Updated
N+3	OCI.Blob	Image Manifest	Updated
N+4	OCI.RootIndex	Image Index	Updated

This should be fairly do-able. Again, you'll need to construct an updated v1.Image, this time that contains an updated EXTFS v1.Layer. This should just be a matter of calculating the layer digest, constructing a v1.Layer similarly to the previous step, and then using mutate.SetLayer to replace the old layer.
From there, if you call Update as described above, I think it might just work?

3. 'Seal' Overlay
When a user has finished modifying an image via an overlay, we may wish to allow them be able to 'seal' the image. This will convert the EXTFS overlay layer into a SquashFS layer.
Sealing an overlay - into a r/o layer - is also a prerequisite for being able to subsequently push the image in tar layer format, compatibile with other runtimes.
Before image is sealed:
descriptor id	type	content
1	OCI.Blob	SquashFS layer
...	OCI.Blob	SquashFS layer
N	OCI.Blob	SquashFS layer
N+1	OCI.Blob	EXTFS overlay layer
N+2	OCI.Blob	Image Config
N+3	OCI.Blob	Image Manifest
N+4	OCI.RootIndex	Image Index
descriptor id	type	content	state
1	OCI.Blob	SquashFS layer	Unmodified
...	OCI.Blob	SquashFS layer	Unmodified
N	OCI.Blob	SquashFS layer	Unmodified
N+1	OCI.Blob	SquashFS layer	New - conversion of extfs layer
N+2	OCI.Blob	Image Config	Updated
N+3	OCI.Blob	Image Manifest	Updated
N+4	OCI.RootIndex	Image Index	Updated

This will again follow a similar flow I think. The tricky part here will be the EXTFS->SquashFS conversion, and I'm not sure if this belongs in this repo or in SingularityCE. I'd lean towards CE for now, as EXTFS seems fairly specific to that at the moment?
Once you have a v1.Layer containing the result of the conversion... it should be a matter of mutate.SetLayer and then Update again?


Add 21 char max len validation to Entrypoint domain

Coverage remained the same at 26.207% when pulling 62b1cd68b24cc7ac1b28b8ae381f5981ad7087f9 on entrypoint_domain_max_len into 79c5de1a143ad948d8fbece76a846ce762b2c393 on master.


Add-on stopped working in Firefox 67.0.2 (64-bit)

This is a Bug Report
Description
What ever folder I select Firefox still propose to save bookmarks in "Other Bookmarks".
Steps to reproduce the problem

Install/Update Firefox to 67.0.2
Install Default Bookmark Folder Add-on
Set "Select where new bookmarks will be added:" option to any Folder except "Other Bookmarks"
Try to save any bookmark

Expected behavior
Any time I try to add bookmark I'd like to see folder that is selected in add-on but not default "Other Bookmarks".
Specifications

Version of the add-on: 2.10

Firefox edition: Firefox (regular edition)
Firefox version: 67.0.2 (64-bit)
Firefox language: English

Platform/OS: Windows 10 1803build

I also noticed that while the computer is on, and I close Firefox, when starting Firefox again, the default bookmark folder that I selected was lost. Hope this helps.
BTW: I now have Firefox Quantum 67.0.4 (64-bit) which produces this issue.

Thank you for reporting this issue @iG8R and for providing the details. 👍
I have been trying to reproduce the problem with an almost exact setup, and I was unfortunately unsuccessful.
I do have a few questions that could help me:

If you try to set other options, such as toggles (like Add new bookmarks to the top of the selected folder) or folder selection for the quick bookmark icon, are they retained or not?
If you set an option and refresh the page, is the selection retained?

On a different approach, I do not know if you are familiar with Firefox profiles? They are where Firefox stores your bookmarks, passwords and other user data.
If you can create a new profile, and test the add-on to see if the problem still exists, that would be very helpful and would rule out a number of possible issues (see #66) or a corrupted profile (which can sometimes happen). This link explains how to use the Profile Manager to create and remove Firefox profiles. Please let me know if you need any help in this regard.
Thanks for your help! 🙂

First of all I'd want to thank you @teddy-gustiaux for the excellent addon.
Recently I updated Firefox to 67.0.4 (64-bit) version and Default Bookmark Folder started working correctly again.
Regarding you question earlier when I had 67.0.2 version:

Yes, all toggles and folder selection are retained but addon still didn't work correctly.
Yes, all options have been retained after refreshing page but, again, addon didn't work correctly.
The same was with the new profile also - the issue didn't disappear.

Thank you.

Thanks a lot! I am glad to hear things are back to normal with 67.0.4- although at this point I am not sure what made the add-on fail with the previous minor version. I am going to close this issue, but feel free to open a new one if you are experiencing any other problems. 🙂


Updated transpiler test_mappers to utiliz Path.QASMS (#4724)

Summary
Fixes #4724
Details and comments
QiskitTestCase._get_resource_path('qasm') appends qasm to Path.TEST.  This assumes that qasm is located directly beneath wherever Path.TEST points. This might change in the future and then all test utilizing utility function assertResult will break. The update instead uses Path.QASMS which points directly to the location of the qasm folder and then uses QiskitTestCase._get_resource_path properly to locate the exact qasm file sought after. This also allowed the removal of import os sins it was no longer in use.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Johan Nicander seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


PSService - Service stuck at starting

hi JF! first of all - great program!! one of the best contributions I ever found.
I have been trying to accomplish something for a while now using your program and reached a new stage of closeness to completion - I think I need a hand now.
What I need the service to do is, from a domain-joined server, connect to (map as drive) a non-domain file share (with user and pass), and then start an app.
What I had before: either the service started correctly, or the goal (connect the share and start the app) was met. I need both because this will go into prod once working.
A bit more explained:
If I added a line stop-process -force -id $pid for the service to kill itself, the share would be connected and the app started, but the SCM console would shout: "service failed to start". If I commented out that line, then the service would run ok, but the connection to the file share would not be established and the webapp would start and show that error message: "could not reach the file share".
Thinking about what happened there I introduced a change: the actual work (connecting to the file share and starting the app) which was part of the service is now a different program, and what the service does is only run it:
start-process -filepath powershell.exe -argumentlist "-file D:\Atlassian\JIRA\bin\start-jira.ps1"
At first I thought this was actually working, because the SCM console did not complain and the app was started OK with the connection to the file share. However, the service stays at "Starting" forever.
I will try the solution in this link, basically wrap it all in a method and make the service start a new thread calling that method. However, do you have any ideas, have you had to do something similar?
Thanks, cheers!!
Dimas

Hi again! The link I pasted solved my issue - closing this now, I hope it'll be useful for someone else. FYI it created more PS instances in the host running it.


Use without Carthage or Cocoapods -> error: Type 'Permission' has no member 'locationWhenInUse'

how can I solve that?
I copied all files as well as .xcconfig to project's root dir... Till update to Swift 3.0 everything was working

I just started seeing this as well after switching from Carthage to CocoaPods (But for notifications not locationWhenInUse).

@dillidon You have to set the .xcconfig file as a configuration file in your project configurations. You might want to use Carthage though, it will make it so much easier :)
@jessetipton There is no need of using PermissionConfiguration.xcconfig with CocoaPods.
See the instructions here.


Stable Windows Version of Ungoogled Chromium (V 67)

I've noticed that this is the latest version of the stable branch of Ungoogled Chromium. Is it still safe to use this? I do like the old style of the browser more, and if it's safe to use, I'd like to use this instead. Thanks in advance.

Yeah the newer Windows versions should be promoted, even though they have a few bugs. It's not recommended to stick to an old version of Chromium.