Add 3D model Elasticsearch model

Description

We will need to add a 3D model model (model2?) to our list of Elasticsearch syncable models in elasticsearch_models.py. This commit may prove as a useful reference: https://github.com/WordPress/openverse-api/commit/cf21b73b4cb7609aea74f6a6e0080695aa2fd8d2
The ES models represent the fields that we will want to search against. This may not be all of the fields available for the media type, we'll need to check against images & audio to see what feels we should include/exclude.
Alternatives

Additional context

Implementation

[ ] 🙋 I would be interested in implementing this feature.

Closing as 3d models are indefinitely on hold and no work should be done on them until we re-plan this project.


Travis CI: add MacOS target and create scripts files

Commit d478cd97bf6fb7616d0b5eda92fef54c3b4191b4 fixes #216.

SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch
I choose option 1.

hmm, I thought to implement osx builds after cmake magic is merged.
or you are not going to add osx to cmake?

I already added support for MacOS in the CMake configuration, but we should make sure that it works.
Once this pull request is merged, I will rebase #518, in order to trigger the builds, so that we can know whether they succeed or not.

Merged. Many thanks for your hard work

You're welcome.


Update JSONata to 1.7.0

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Chore

Proposed changes

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

This resolves #2324 (the en translation anyway).  This PR updates JSONata to version 1.7.0 and updates the translation and formatter to support the new  and enhanced functions.

Hi, thanks for this. I'll take a proper look at it  on Monday of I don't get a chance before hand.
In future, if you're going to work on an issue, please add a comment to the issue, or mention in #dev in slack that you are looking at it to avoid duplicate effort. For this issue, I have a local branch with half of the work done; the issue was mostly a reminder for me to come back and finish it.
But I'm happy to review your changes and merge if they are good.

Whoops sorry about that!  Saw the issue this morning and figured I'd take a crack at it.  I will check on slack and leave an issue comment next time before starting work 👍

Coverage remained the same at 77.536% when pulling c590247afa3b7db842c646386c231a040079fc22 on pdong:chore/update-to-jsonata-1.7 into 29f1651a18cdd2c178dba65ea7a500ceaca7cf4c on node-red:master.

Thanks!


Control with custom dynamic font has a y size of infinity after Win + D

Godot version
3.3.4.stable
System information
Windows 10
Issue description
On a project with 2D stretch mode, using show desktop (Windows + D) and then go back makes controls containing text with a dynamic font stretch their y size to infinity.
Before:

After Win + D and restoring:

Inside the inspector (at rect_size):

I specifically said Windows + D instead of minimizing and restoring, and this only happens on 2D stretch mode.
Steps to reproduce
Import a custom font like Arial to a project. Create a scene with Control root node and a Label inside. Use a custom DynamicFont for that Label with Arial as the font data. Change project stretch mode to 2D. Run that scene and press Windows + D 2 times.
Minimal reproduction project
InftyOnShowDesktop.zip

Shoot, there is a workaround. Can anybody explain why this happens?

Well, that's still a bug for when font oversampling is enabled, no?

It still is for 3.3.4.stable.

Related to https://github.com/godotengine/godot/issues/47957.
Can you try reproducing this in 3.4rc3? It may have been fixed by https://github.com/godotengine/godot/pull/51973.

This is unrelated to the issue itself, but remember that Microsoft fonts' licenses don't allow you to redistribute the font files. Consider using open source metrics-compatible fonts instead, such as Arimo.

Thanks for reminding me! For one second I thought Arial was free to use.

I can now confirm this issue is not reproducible in 3.4rc3.

Thanks for testing :slightly_smiling_face: Closing as resolved then.


[xc7] Support RAMB36E1

Tasks:

[x] Ensure that RAMB36E1 can be placed and routed
[ ] Add simulation model for RAMB18E1 and RAMB36E1
[ ] Create test benches to verify pre- and post-place and routed designs using RAMB18E1 and RAMB36E1
[ ] Verify RAMB18E1 and RAMB36E1 operation in hardware

Support not required for:

RAMB36E1 1-bit cascades
ECC support

Existing BRAM36 tests appear to work on hardware.  I'm working on fasm2v support next, followed by RAMB sim models so we can add testbenches.

Clarification on BRAM36 support, I suspect that only the widest modes are working (e.g. 36 and 72 bit wide), for the same reason that https://github.com/SymbiFlow/symbiflow-arch-defs/commit/9c65a49cd5c6b88d7606a8cb817dbee448050013#diff-2bb469162bf2c7f8904db77a1acc2582 was required.  Once fasm2v support is in, I'll add the following tests:

[ ] RAMB18 width = 2
[ ] RAMB18 width = 4
[ ] RAMB18 width = 9
[ ] RAMB36 width = 2
[ ] RAMB36 width = 4
[ ] RAMB36 width = 9
[ ] RAMB36 width = 18


Creating ModuleLoaderData sturcture for Build/Sign/ModuleLoader workf…

…low (#301)
This PR add the creation of the ModuleLoaderData structure. This struct contains all the data needed for processing the wholw flow of Build/Sign/Module loader per specific Module/KernelMapping.
The flow ass following:

when starting processing the Reconcile request( either in Module controller
or in ManagedCluster controller) all the needed data from Module and KernelMapping
is merged into a newly created ModuleLoaderData struct
all the following layers are working only with this structure, no need to look
at Module or KernelMapping again.
This does not affect the flow of DevicePlugin

Upstream cherry-pick 244d756a30e633dd6e96164ae388f08828faf1ae

/assign @ybettan

/lgtm


Under/overflow bins in data

In the defaults, now the under/overflow bins are merged into the first/last visible bins for the MC histogram.
However, there is no corresponding option for data at the moment, therefore the under/overflow bins are not plotted, leading to a discrepancy in the data/MC ratio, as displayed in the following plot where the first bin contains the underflow bin in MC but not in data:

A new feature is requested to handle under/overflow bins in data to be coherent with the way we handle them in MC.

The issue is being addressed in https://github.com/PocketCoffea/PocketCoffea/pull/115: now the under/over-flow bins of the data histogram are properly added to the first and last bin, respectively.


pull request for e2e test at 11/10/2016 15:56:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Issues with the Benchmark

Hi!
As I understand the benchmark example program should also work for a VDMA engine looped back, correct? I have a design which contains only a VDMA engine with TX and RX looped back. The module loads ok, and both channels seem to be seen:
[    7.697740] axidma: axidma_dma.c: axidma_dma_init: 718: DMA: Found 0 transmit channels and 0 receive channels. [    7.707679] axidma: axidma_dma.c: axidma_dma_init: 720: VDMA: Found 1 transmit channels and 1 receive channels.
When I run the benchmark code as below:
sudo ./axidma_benchmark -v -t 0 -r 1 -f 10x10x3 -g 10x10x3 -n 3
I get a segmentation fault.
In dmesg I see:
[  170.988718] axidma: axidma_dma.c: axidma_start_transfer: 301: VDMA receive transaction timed out.
Any suggestions as to where I can look for the problem?
Thanks!!

On reviewing some of the other issues, is it possible this is related to not having the number of buffers set to 1 in the IP core?

I am guessing, like you @bperez77, I just have the wrong settings in my IP core.

@Westwood68 Do you happen to remember/have the settings for the AXI VDMA IP you used to get the VDMA test to work in the kernel? I'm trying to get it up an running now, but I can't seem to find the right configuration.<

@Westwood68, could you let us know what settings you used to get the VDMA working correctly? Thanks!

Yeah this one was tricky, I still haven't figured out the proper settings on the IP core to get it to work. It may also be an issue inside the driver with how multiple VDMA buffers are set up, but I would still expect it to work for a single buffer case.
IIRC from that original thread, he didn't remember what the original settings were.

Hi @bperez77, the program does indeed crash when the single test transfer is performed (single_transfer_test). Since making some changes to the IP core, I am now getting a null pointer exception, so I guess it might actually not be related to the driver at all.
It might also be that there is some significance to the fact that I am using a 64-bit platform (ZynqMP) instead of the 7-series Zynq. I actually really hope that the problem is in the user space program and not in the driver, as I have very little experience developing kernel modules.

I guess this is the same problem as described in issue #52.
I am not sure if I will get further than they did, but if I do, I will post my findings here.

I have added some kprint statements to the module to see exactly where in the DMA transfer things go sideways... See below, where I added also the lines of code where the print statements happened:
`[  124.105520] Running axidma_rw_transfer.464, axidma_chrdev.c
[  124.105523] Getting tx channel.[n473, axidma_dma.c]
[  124.105526] Getting rx channel.[n482, axidma_dma.c]
[  124.105528] Setting up SG table, tx.[n493, axidma_dma.c]
[  124.105532] Setting up SG table, rx.[n502, axidma_dma.c]
[  124.105534] Adding SG frame info, tx.[n524, axidma_dma.c]
[  124.105537] Adding SG frame info, rx.[n542, axidma_dma.c]
[  124.105539] Prepping transfer, tx.[n550, axidma_dma.c]
[  124.105550] Prepping transfer, rx.[n557, axidma_dma.c]
[  124.105556] Starting transfer, tx:[n566, axidma_dma.c]
[  124.105559] Flush all pending xfers:[n294, axidma_dma.c]
[  124.105567] All pending xfers cmplt:[n298, axidma_dma.c]
[  124.105570] Starting transfer, rx:[n573, axidma_dma.c]
[  124.105572] Flush all pending xfers:[n294, axidma_dma.c]
[  124.105579] All pending xfers cmplt:[n298, axidma_dma.c]
[  124.105637] Transfers started:[n580, axidma_dma.c]
[  124.105641] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[  124.113663] pgd = ffffffc878423000
[  124.117036] [00000000] *pgd=00000008785b6003
[  124.121110] , *pud=00000008785b6003
[  124.121114] , *pmd=0000000000000000
[  124.121121] Internal error: Oops: 86000006 [#1] SMP
[  124.125965] Modules linked in: xilinx_axidma(O)
[  124.130479] CPU: 2 PID: 3707 Comm: axidma_benchmar Tainted: G    B      O    4.9.0-xilinx-v2017.4 #1
[  124.139594] Hardware name: Mercury XU5 (DT)
[  124.143759] task: ffffffc87a91ce80 task.stack: ffffffc877f3c000
[  124.149664] PC is at 0x0
[  124.152177] LR is at 0x0
[  124.154695] pc : [<0000000000000000>] lr : [<0000000000000000>] pstate: 40000145
[  124.162075] sp : ffffffc877f3fd60
[  124.165371] x29:<PHONE_NUMBER>00012c x28: ffffffc877f3c000
[  124.170665] x27: ffffff8008962000 x26:<PHONE_NUMBER>00001d
[  124.175959] x25:<PHONE_NUMBER>000123 x24:<PHONE_NUMBER>000015
[  124.181254] x23: 0000007fe08b1b50 x22: 0000007fe08b1b50
[  124.186549] x21: ffffffc87aaab600 x20: ffffff8000963630
[  124.191844] x19: ffffffc877f3fdb8 x18:<PHONE_NUMBER>000001
[  124.197139] x17: 0000007fae4c5290 x16: ffffff800819e2c0
[  124.202439] x15:<PHONE_NUMBER>010000 x14:<PHONE_NUMBER>000000
[  124.207733] x13:<PHONE_NUMBER>000004 x12:<PHONE_NUMBER>000195
[  124.213028] x11:<PHONE_NUMBER>000002 x10:<PHONE_NUMBER>000195
[  124.218323] x9 :<PHONE_NUMBER>000001 x8 : ffffff8008d55648
[  124.223618] x7 :<PHONE_NUMBER>000000 x6 :<PHONE_NUMBER>891196
[  124.228913] x5 : ffffffc87ff9eba8 x4 :<PHONE_NUMBER>000001
[  124.234207] x3 :<PHONE_NUMBER>000007 x2 :<PHONE_NUMBER>000006
[  124.239502] x1 :<PHONE_NUMBER>000007 x0 :<PHONE_NUMBER>000000
[  124.246275] Process axidma_benchmar (pid: 3707, stack limit = 0xffffffc877f3c020)
[  124.253748] Stack: (0xffffffc877f3fd60 to 0xffffffc877f40000)
[  124.259472] fd60: ffffffc877f3fe00 ffffff800819dc14 ffffffc87a4f4200 ffffffc87a5a0558
[  124.267290] fd80: ffffffc87a4f4200 0000007fe08b1b50 0000007fe08b1b50<PHONE_NUMBER>000015
[  124.275102] fda0: ffffffc877f3fe10 ffffff8008081298<PHONE_NUMBER>00004f<PHONE_NUMBER>000001
[  124.282914] fdc0: 0000007fae3fe000<PHONE_NUMBER>007530<PHONE_NUMBER>000064<PHONE_NUMBER>000003
[  124.290726] fde0: 0000007fae3f6000<PHONE_NUMBER>007530<PHONE_NUMBER>000064<PHONE_NUMBER>000003
[  124.298538] fe00: ffffffc877f3fe80 ffffff800819e304 ffffffc87a4f4200<PHONE_NUMBER>000003
[  124.306350] fe20: ffffffc87a4f4200<PHONE_NUMBER>485706 0000007fe08b1b50<PHONE_NUMBER>4018a8
[  124.314162] fe40: ffffffc877f3fe80 ffffff800818c68c ffffffc87a4bbb00 ffffffc87a4bbb00
[  124.321975] fe60:<PHONE_NUMBER>1ad010<PHONE_NUMBER>000030 ffffffc877f3fe80 ffffff800819e2e4
[  124.329786] fe80:<PHONE_NUMBER>000000 ffffff8008082ef0<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[  124.337599] fea0: ffffffffffffffff 0000007fae4c529c<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[  124.345411] fec0:<PHONE_NUMBER>000003<PHONE_NUMBER>485706 0000007fe08b1b50<PHONE_NUMBER>000003
[  124.353223] fee0: 0000007fe08b1c98<PHONE_NUMBER>000001 0000007fe08b1b94<PHONE_NUMBER>007530
[  124.361035] ff00:<PHONE_NUMBER>00001d ffffff80ffffffc8<PHONE_NUMBER>010101 0000007fe08b1c00
[  124.368847] ff20:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000 0000007fae58d000
[  124.376659] ff40: 0000007fae560090 0000007fae4c5290<PHONE_NUMBER>000a03<PHONE_NUMBER>402768
[  124.384471] ff60:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[  124.392283] ff80:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[  124.400095] ffa0:<PHONE_NUMBER>000000 0000007fe08b1af0 0000007fae54ef1c 0000007fe08b1af0
[  124.407907] ffc0: 0000007fae4c529c<PHONE_NUMBER>000000<PHONE_NUMBER>000003<PHONE_NUMBER>00001d
[  124.415719] ffe0:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[  124.423529] Call trace:
[  124.425954] Exception stack(0xffffffc877f3fb90 to 0xffffffc877f3fcc0)
[  124.432379] fb80:                                   ffffffc877f3fdb8<PHONE_NUMBER>000000
[  124.440197] fba0: ffffffc877f3fd60<PHONE_NUMBER>000000 ffffffc877f3fbc0 00000000ffffffc8
[  124.448009] fbc0: ffffffc87aaab600<PHONE_NUMBER>000244 ffffff8000964180<PHONE_NUMBER>000002
[  124.455821] fbe0:<PHONE_NUMBER>000000<PHONE_NUMBER>000002<PHONE_NUMBER>000000 ffffffc87ff9ec00
[  124.463633] fc00:<PHONE_NUMBER>00012c<PHONE_NUMBER>000000 ffffffc877f3fdb8 ffffff8000963630
[  124.471445] fc20: ffffffc87aaab600 0000007fe08b1b50<PHONE_NUMBER>000000<PHONE_NUMBER>000007
[  124.479257] fc40:<PHONE_NUMBER>000006<PHONE_NUMBER>000007<PHONE_NUMBER>000001 ffffffc87ff9eba8
[  124.487069] fc60:<PHONE_NUMBER>891196<PHONE_NUMBER>000000 ffffff8008d55648<PHONE_NUMBER>000001
[  124.494882] fc80:<PHONE_NUMBER>000195<PHONE_NUMBER>000002<PHONE_NUMBER>000195<PHONE_NUMBER>000004
[  124.502694] fca0:<PHONE_NUMBER>000000<PHONE_NUMBER>010000 ffffff800819e2c0 0000007fae4c5290
[  124.510504] [<          (null)>]           (null)
[  124.515187] Code: bad PC value
[  124.518247] ---[ end trace 725126ff463380d9 ]---`
I sort of expected to find something like a failure to use the "copy to/from user" function or similar, but this is not the case. In fact it seems like the kernel actually completes the full DMA transfer function before getting the null pointer exception at the line where we return 0.
Any ideas where I could keep looking for the problem? I have tried a lot of combinations of settings for the VDMA engine, nothing seems to be helping much, aside from the fact that now I get a null pointer exception instead of a timeout condition...
Thanks!

I have been rigorously pursuing the solution to this issue in parallel and come to the same conclusion.  The DMA transfer function is completing correctly and the null pointer exception is occurring  at the very point that the axidma_rw_transfer(dev, &inout_trans) in the ioctl case statement for AXIDMA_DMA_READWRITE in axidma_chrdev.c.
I speculate that a conflict is occurring with the  asynchronous signal being issued for transmit DMA completion.  Because the axidma-benchmark application is blocking on the receive completion anyway, this signal is not needed for correct operation.
I did a quick test today on the Zedboard by commenting out the "send_sig_info( ... )" line in the axi_dma_callback function and confirmed that the axidma-benchmark for VDMA still worked fine.
I will have access again beginning on 9/24 to the ZynqMP ZCU102 board to test this out.  If you can see if this makes a difference before then, please advise.  If this turns out to be the problem, the fix should be implemented elsewhere in the driver so as not to impact cases where the signal is necessary.

Looking deeper into the axidma_callback( ... ) signal handler for the VDMA Tx transaction done signal, there is an assert( ... ) function being called.  An assertion is not considered async-signal-safe.  This could be the root of the problem but won't know for sure until testing on the ZynqMP.

Hi @EKjeldsen, I am glad I am not the only one having this problem. I tried your suggestion of commenting out the send_sig_info function call in the dma callback. I added some printk statements to follow the timing. Interestingly, it does indeed seem to be crashing during the second time we enter the callback (presumably for the RX thread), since I see the entrance printk, and not the exit printk. Below are my added printk statements from a run of the transfer test so you can observe the sequencing:

[ 1315.592026]  Getting tx channel.[n475, axidma_rw_transfer]
[ 1315.597390] Getting rx channel.[n484, axidma_rw_transfer]
[ 1315.602771] Setting up SG table, tx.[n495, axidma_rw_transfer]
[ 1315.608588] Setting up SG table, rx.[n504, axidma_rw_transfer]
[ 1315.614402] Adding SG frame info, tx.[n526, axidma_rw_transfer]
[ 1315.620305] Adding SG frame info, rx.[n544, axidma_rw_transfer]
[ 1315.626210] Prepping transfer, tx.[n552, axidma_rw_transfer]
[ 1315.631858] Prepping transfer, rx.[n559, axidma_rw_transfer]
[ 1315.637496] Starting transfer, tx:[n568, axidma_rw_transfer]
[ 1315.643143] Flush all pending xfers:[n296, axidma_start_transfer]
[ 1315.649215] All pending xfers cmplt:[n300, axidma_start_transfer]
[ 1315.655286] Starting transfer, rx:[n575, axidma_rw_transfer]
[ 1315.660927] Flush all pending xfers:[n296, axidma_start_transfer]
[ 1315.667008] All pending xfers cmplt:[n300, axidma_start_transfer]
[ 1315.673116] Entered axi-dma callback.:[n151, axidma_dma_callback]
[ 1315.679160] NOT performing the send_sig_info...:[n160, axidma_dma_callback]
[ 1315.686278] Entered axi-dma callback.:[n151, axidma_dma_callback]
[ 1315.692362] Transfers started:[n582, axidma_rw_transfer]
[ 1315.697651] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 1315.705726] pgd = ffffffc87a7cd000
[ 1315.709095] [00000000] *pgd=0000000877d3d003

I will let you know if I discover anything else today while I am working on it.

Follow up: I was running very small transfers to test the engine. Out of curiosity I ran some normal, frame sized transfers using the following command:

sudo ./axidma_benchmark -v -f 1080x1920x3 -g 1080x1920x3 -n 3

Behavior here was quite a bit different. The program seems to freeze after a different kernel error, before the DMA transfers are even set up...

[   66.925888] Entered axidma_ioctl fctn.
[   66.925893] Getting device pointer from the file.
[   66.925897] Entered axidma_ioctl fctn.
[   66.925898] Getting device pointer from the file.
[   66.925911] Entered axidma_ioctl fctn.
[   66.925912] Getting device pointer from the file.
[   66.926301] Unable to handle kernel paging request at virtual address ffffffc000100000
[   66.934158] pgd = ffffffc87b981000
[   66.937542] [ffffffc000100000] *pgd=0000000000000000
[   66.942297] , *pud=0000000000000000

[   66.942307] Internal error: Oops: 9600004f [#1] SMP
[   66.947151] Modules linked in: xilinx_axidma(O)
[   66.951666] CPU: 3 PID: 3370 Comm: axidma_benchmar Tainted: G    B      O    4.9.0-xilinx-v2017.4 #1
[   66.960781] Hardware name: Mercury XU5 (DT)
[   66.964946] task: ffffffc87875a700 task.stack: ffffffc87afc4000
[   66.970855] PC is at __memset+0x1ac/0x1d0
[   66.974844] LR is at __dma_alloc+0xf8/0x2a0
[   66.979007] pc : [] lr : [] pstate: 40000145
[   66.986385] sp : ffffffc87afc7c30
[   66.989682] x29: ffffffc87afc7c30 x28:<PHONE_NUMBER>000008
[   66.994975] x27: 0000007f7d0d2000 x26:<PHONE_NUMBER>5ef000
[   67.000270] x25: ffffff8008cc34e0 x24: ffffff8008d457f8
[   67.005565] x23:<PHONE_NUMBER>000000 x22: ffffffc87b0aa010
[   67.010860] x21: ffffffc878619a98 x20: ffffffc000100000
[   67.016155] x19:<PHONE_NUMBER>5ef000 x18:<PHONE_NUMBER>000a03
[   67.021449] x17: 0000007f7d81b060 x16: ffffff8008087d10
[   67.026750] x15:<PHONE_NUMBER>000040 x14:<PHONE_NUMBER>000001
[   67.032044] x13:<PHONE_NUMBER>000038 x12: ffffff8008d3e890
[   67.037339] x11: ffffff8008d3e890 x10: ffffffbf00018820
[   67.042634] x9 :<PHONE_NUMBER>000000 x8 : ffffffc000100000
[   67.047929] x7 :<PHONE_NUMBER>000000 x6 :<PHONE_NUMBER>00003f
[   67.053223] x5 :<PHONE_NUMBER>000040 x4 :<PHONE_NUMBER>000000
[   67.058518] x3 :<PHONE_NUMBER>000004 x2 :<PHONE_NUMBER>5eefc0
[   67.063813] x1 :<PHONE_NUMBER>000000 x0 : ffffffc000100000

[   67.070586] Process axidma_benchmar (pid: 3370, stack limit = 0xffffffc87afc4020)
[   67.078059] Stack: (0xffffffc87afc7c30 to 0xffffffc87afc8000)
[   67.083782] 7c20:                                   ffffffc87afc7c80 ffffff8000960220
[   67.091601] 7c40: ffffffc878619a80 ffffffc87a5f4d10 ffffffc87b0aa010 ffffffc87ace5200
[   67.099413] 7c60: ffffffc878619a98 ffffff8008d457f8 ffffff8008cc34e0<PHONE_NUMBER>000000
[   67.107225] 7c80: ffffffc87afc7cf0 ffffff8008164104 ffffffc878610a80 ffffffc87aef9500
[   67.115037] 7ca0:<PHONE_NUMBER>000000 ffffffc87a1ae000 ffffffc87a5f4d10<PHONE_NUMBER>0000fb
[   67.122849] 7cc0:<PHONE_NUMBER>0005ef ffffffc87a4d19a0<PHONE_NUMBER>000000 ffffffc87a1ae000
[   67.130661] 7ce0:<PHONE_NUMBER>000000<PHONE_NUMBER>5ef000 ffffffc87afc7d70 ffffff8008164580
[   67.138473] 7d00:<PHONE_NUMBER>5ef000 0000007f7d0d2000<PHONE_NUMBER>000003<PHONE_NUMBER>000001
[   67.146285] 7d20: ffffffc87a1ae000 ffffffc87aef9500<PHONE_NUMBER>0000fb<PHONE_NUMBER>0005ef
[   67.154097] 7d40: ffffff8008962000 ffffffc87afc4000 ffffffc878610a70<PHONE_NUMBER>000000
[   67.161910] 7d60:<PHONE_NUMBER>5ef000 fffffffffffffff4 ffffffc87afc7de0 ffffff800814d244
[   67.169721] 7d80: ffffffc87aef9568 ffffffc87a1ae000<PHONE_NUMBER>000000<PHONE_NUMBER>5eec00
[   67.177534] 7da0:<PHONE_NUMBER>000003<PHONE_NUMBER>000001<PHONE_NUMBER>000000 ffffff8008983000
[   67.185346] 7dc0: ffffffc87afc7de0 ffffff800814d1f8 ffffffc87afc7e38 ffffffc87afc7e38
[   67.193158] 7de0: ffffffc87afc7e40 ffffff80081621e8<PHONE_NUMBER>5eec00 ffffffc87a1ae000
[   67.200970] 7e00:<PHONE_NUMBER>000000<PHONE_NUMBER>000003<PHONE_NUMBER>000000<PHONE_NUMBER>000001
[   67.208782] 7e20:<PHONE_NUMBER>5eec00<PHONE_NUMBER>005702 ffffffc87afc7e40<PHONE_NUMBER>000000
[   67.216594] 7e40: ffffffc87afc7eb0 ffffff8008087d28<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[   67.224406] 7e60: ffffffffffffffff 0000007f7d783cdc<PHONE_NUMBER>000000<PHONE_NUMBER>000015
[   67.232218] 7e80:<PHONE_NUMBER>000123<PHONE_NUMBER>0000de<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[   67.240030] 7ea0: ffffffffffffffff 0000007f7d78029c<PHONE_NUMBER>000000 ffffff8008082ef0
[   67.247842] 7ec0:<PHONE_NUMBER>000000<PHONE_NUMBER>5eec00<PHONE_NUMBER>000003<PHONE_NUMBER>000001
[   67.255654] 7ee0:<PHONE_NUMBER>000003<PHONE_NUMBER>000000 0000007fe8156218<PHONE_NUMBER>000000
[   67.263466] 7f00:<PHONE_NUMBER>0000de<PHONE_NUMBER>000000<PHONE_NUMBER>010101<PHONE_NUMBER>000000
[   67.271278] 7f20:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000 0000007f7d848cc0
[   67.279091] 7f40: 0000007f7d783cc8 0000007f7d81b060<PHONE_NUMBER>000a03<PHONE_NUMBER>402768
[   67.286902] 7f60:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[   67.294715] 7f80:<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>000000
[   67.302527] 7fa0:<PHONE_NUMBER>000000 0000007fe8156370 0000007f7d8099f0 0000007fe8156370
[   67.310339] 7fc0: 0000007f7d783cdc<PHONE_NUMBER>000000<PHONE_NUMBER>000000<PHONE_NUMBER>0000de
[   67.318151] 7fe0:<PHONE_NUMBER>000000<PHONE_NUMBER>000000 fffffffff7ffffff fffefbfffd9bffff
[   67.325960] Call trace:
[   67.328386] Exception stack(0xffffffc87afc7a60 to 0xffffffc87afc7b90)
[   67.334811] 7a60:<PHONE_NUMBER>5ef000<PHONE_NUMBER>000000 ffffffc87afc7c30 ffffff80083de32c
[   67.342629] 7a80:<PHONE_NUMBER>000100<PHONE_NUMBER>0006ef<PHONE_NUMBER>000800 ffffff8008188210
[   67.350441] 7aa0: ffffffc87afc4000<PHONE_NUMBER>000800<PHONE_NUMBER>000100 ffffffbf00003820
[   67.358253] 7ac0: ffffffc87afc7ba0 ffffff8008188440<PHONE_NUMBER>000100 ffffff8008d658f8
[   67.366065] 7ae0:<PHONE_NUMBER>000100<PHONE_NUMBER>010000<PHONE_NUMBER>0005ef ffffff8008cd0bb0
[   67.373877] 7b00: ffffffc000100000<PHONE_NUMBER>000000<PHONE_NUMBER>5eefc0<PHONE_NUMBER>000004
[   67.381689] 7b20:<PHONE_NUMBER>000000<PHONE_NUMBER>000040<PHONE_NUMBER>00003f<PHONE_NUMBER>000000
[   67.389501] 7b40: ffffffc000100000<PHONE_NUMBER>000000 ffffffbf00018820 ffffff8008d3e890
[   67.397313] 7b60: ffffff8008d3e890<PHONE_NUMBER>000038<PHONE_NUMBER>000001<PHONE_NUMBER>000040
[   67.405124] 7b80: ffffff8008087d10 0000007f7d81b060
[   67.409981] [] __memset+0x1ac/0x1d0
[   67.415026] [] axidma_mmap+0xf8/0x388 [xilinx_axidma]
[   67.421613] [] mmap_region+0x38c/0x5a8
[   67.426906] [] do_mmap+0x260/0x398
[   67.431855] [] vm_mmap_pgoff+0x94/0xb8
[   67.437150] [] SyS_mmap_pgoff+0xb0/0x228
[   67.442619] [] sys_mmap+0x18/0x28
[   67.447478] [] el0_svc_naked+0x24/0x28
[   67.452774] Code: 91010108 54ffff4a 8b040108 cb050042 (d50b7428)
[   67.458889] ---[ end trace 7b9aad28c11933be ]---

By the way, @EKjeldsen, does the "vdmatest" kernel module from Xilinx work in your system? That kernel module also does not work in my system. Typical Xilinx.

@bperez77 : I have noticed in the character device driver, you have case statements for dma read, vdma read, dma write, vdma write, but then only a dma read and write (bidirectional),  are the additional frame housekeeping tasks performed in the respective vdma functions not necessary for the bidirectional case?

@brianvg - thank you for updating your findings.  We will be looking further into this today and will post updates as well.

Found something interesting late today of interest.  To rule out multiple buffer issues, I verified operation using a single frame buffer.  On the Zedboard, Brandon's axidma_benchmark and Xilinx's vdmatest ran fine.  On the ZCU102, vdmatest ran fine but axidma_benchmark encountered the NULL pointer exception.
However, I noticed that the value of "xlnx,num-fstores" for the VDMA IP core in the pl.dtsi file generated for the ZCU102 was double what it should be.  In my original 3 frame buffer case, "xlnx,num-fstores" equals 0x6 vs, 0x3.  In the 1 frame buffer case, "xlnx,num-fstores" equals 0x2 vs. 0x1.
In the case of the Zedboard, there was no discrepancy between the setting in the VDMA IP and the Petalinux generated value fox "xlnx,num-fstores".
Tomorrow we will test a version on the ZCU102 that corrects the "xlnx,num-fstores" to equal 0x1.
Seems to be yet another bug in Petalinux (we are using 2017.4).

Hi @EKjeldsen, I just ran a test with the corrected entry for the frame buffer. I do not observe any changes in behavior, still seeing the segmentation fault. Nice catch though! Not sure how Petalinux is getting that wrong...

We are still pursuing this effort, but haven’t posted anything lately because of dead ends.  Our use case is the opposite direction, PL -> PS, for video source processing by the PS, but also what would seem to be a typical application.  There is a very perplexing problem!  One architecture difference with respect to the Zynq-7000 Zedbaord is the presence of an SMMU.   I think I’ve finally convinced myself that the SMMU can be bypassed as this driver provides the necessary address translation.  But I would appreciate your take on that.   Yesterday I discovered that a switch to set the size of dma_addr_t to 64 bits was not being configured in Petalinux.  I added a user_xx.cfg file containing the following entry: CONFIG_ARCH_DMA_ADDR_T_64BIT=y.   I then verified that sizeof(dma_addr_t) was 8 bytes.  Unfortunately the NULL pointer exception remained.
Today I’m going to look further into the possibility of a pointer arithmetic error.  Also, a point of divergence to consider that his driver uses an interleaved DMA call for VDMA vs. scatter-gather call for regular DMA.  Maybe something is being set incorrectly in that call when 64-bit bit addressing is used?
From: brianvg<EMAIL_ADDRESS>Sent: Tuesday, October 02, 2018 1:27 AM
To: bperez77/xilinx_axidma<EMAIL_ADDRESS>Cc: Kjeldsen, Erik H<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [bperez77/xilinx_axidma] Issues with the Benchmark (#68)
Hi @EKjeldsenhttps://github.com/EKjeldsen ! Any new progress on the issue? I was exploring the possibility of leveraging V4L2, which is what many ZynqMP users end up doing to get video streams from user space working, but unfortunately, the framework does not seem to allow sending video into the PL for any use other than sending it to a display port/hdmi interface. This seems to rule out the very plausible use case of using the framework for a video coprocessor (sending the data down to the PL, and then retrieving it after processing). @bperez77https://github.com/bperez77's work really does seem to be the only show in town for creating a data path for this sort of a use case. It is typical of Xilinx's startling lack of imagination that they would not prioritize this as a typical use case and offer some measure of support. (please excuse the rant...)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/bperez77/xilinx_axidma/issues/68#issuecomment-426153056, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aenrph4DiBuhVnVpO6LvC3uuE0dIl1Aiks5ugvkKgaJpZM4WnKrY.

Hi @EKjeldsen I may be mistaken, but my read of the SMMU is that it is disabled by default and even when enabled only has an effect when the relevant PL masters are set up correctly to use it. I have tried enabling it in the device tree, but I don't see any effect. Enabling the SMMU would in theory allow us to use virtual addresses for mapping memory locations from user space into the DMA engine. I guess one would need to map the VDMA to a VIO device type. It all looks very cool, and would save the memory copy that is otherwise necessary. See here and . Also, I guess you need to add the smmu use statements to the device tree, after you figure out the stream ID of your AXI DMA interfaces. It is all explained on the wiki, but it sounds a bit iffy to be honest. It is not clear to me how you can guarantee contiguous memory address allocation for large buffers from user space.
All this is fairly academic. I am nearly 100% certain that the problem is not related to address translation at the hardware level, since the Xilinx VDMA self test completes successfully.

Sorry @brianvg @EKjeldsen, I've been pretty busy lately and haven't been active. So from the above thread it seems like there's two separate issues:

The callback function is causing a NULL pointer exception wit the AXI DMA RW transfer.
The driver is not correctly handling transfers that involve more than 1 frame buffers.

I don't think that the SMMU should have any influence on the correct operation of the driver, it is able to perfrom all the translations to physical addresses required by the IP.
I'll have some time to work on this this weekend. Can one of you guys send me the configuration for your VDMA IP (a screenshot should be sufficient)? I still haven't gotten to the phase where I get a successful VDMA transfer. For both the VDMA test driver and my benchmark program, the transfer times out. I'm also working off a Zybo board, so I won't be able to directly replicate what you guys have on the ZynqMP board.
P.S. Yeah @brianvg I understand your frustration. It's three years on from when I created this driver and Xilinx still doesn't have a driver that's usable directly from userspace programs. I imagine Xilinx has done it this way because they want to pigeonhole everyone into their SDSoC framework.

@bperez77 I agree that it is all about moving people to SDSOC. Very annoying because they should not care what path people use to develop. Xilinx is ostensibly a hardware company. There are so many ways to do design input! Not everyone wants to pretend C++ is a good method to design programmable logic.
I am not at all certain that my configurations are correct, but I have attached screenshots.

Best Regards,
Brian

BTW, this is just my latest configuration. I have played around a lot over time...

Here are our current VDMA setup screenshots. Thank you for looking at this further Brandon.  Since you don't have any ZynqMP platform available, you could make suggestions for @brianvg and us to try on our hardware to further isolate the problem.
I have noticed that you declare a static pointer to the character device - "axidma_dev" to store this pointer on the stack.  Is is possible that is getting corrupted?  The other critical argument in the ioctl is the "axidma_inout_transaction" structure which is also stored on the stack.  Could this be somehow be going out of scope?

To come back to some of your guys' original connection. When the two way/read write transfer occurs, the callback will be invoked twice. For the TX/write transfer, the callback is invoked with wait equal to false, so it will try to send a signal. However, if no signal is registered, then it shouldn't trigger a signal. For the RX/read transfer, the callback function should be invoked with wait equal to false. In this case, it will instead complete the completion structure, which should unblock the kernel thread waiting on the RX transfer.
@EKjeldsen those are valid points about both of those structures. For the loopback test, even though those values are stored on the stack, they are gauranteed to remain in scope because the main kernel thread that invokes DMA transfer function will wait for the callback function to indicate that it can continue. So, the values will remain valid because the thread will be put to sleep while waiting. It's not clear from the code, but this is what should be happening.
If had to guess, it seems that the macro VALID_NOTIFY_SIGNAL isn't behaving correctly, and when send_sig_info is being invoked, the cb_data->process field isn't properly initialized, leading to the segmentation fault. Since commenting out send_sig_info seems to fix the issue, this should be the culprit.
I'm investigating more now.

I'm still not able to get the VDMA IP working correctly with a loopback test. I tried both of your configurations against Xilinx's VDMA test driver, but both still timeout for me as well.
Since I can't make more progress on this route, can you guys take your existing stack backtraces and determine the source line numbers as desribed in this StackOverflow post?

when I run my benchmark on PetaLinux , I get :+1:
./axidma_benchmark: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
prob is more a petalinux issue.

@maikonadams  how to add the driver's files to PetaLinux?
There is a compilation problem while it is being used with Petalinux 20118.2.
I copy the drivers   files
axi_dma.c
axidma.h
axidma_chrdev.c
axidma_dma.c
axidma_of.c
to the /project-spec/meta-user/recipes-modules/axidma/files
modify the driver.mk to makefile .but can't add the include file and the lib file.  and  compile   error occors.


OpenWeatherMap API error & crashing

Hello. I've been using the app for quite awhile now but have recently been having some problems.
It feels like these problems started happening around version 1.7.1. I use OpenWeatherMap for this app and several others and have my own private API key. When I initially open the app I get a pop-up asking me for my key, which is already there.

When I click save, the app will crash every time and I have to manually clear it from active apps or it will crash when I try to open it again. If I do not touch save, but touch the screen anywhere else, the pop-up will disappear; however, the app will not automatically update. I have to select the ellipsis and touch refresh. If I pull down to refresh, about half of the time nothing happens. The other half of the time, the app will crash.
I couldn't find anywhere to collect logs for you. If there is, please let me know.
OS: Android 14 - GrapheneOS
Device: Pixel 7 pro
App version: <IP_ADDRESS>
APK source: GitHub

@exstntlmsnthrp I LL take a look at it thanks for reporting

@farfromrefug Brilliant! I downloaded as soon as I saw it available and I don't have any problems now. And it remembers my API key.
Did you refactor the build or something? It looks better! Thanks.
The weather alerts are now working again too.
Cheers.

@exstntlmsnthrp thanks. Yes i changed a lot for things! BTW you should look at the Open-Meteo provider. It is a free forever provider which is getting real good!


adding parameter manual BGP adv

Terraform liniting failed, please format code.
Also, please restore the version constraint in versions.tf. These Azure RM resources were introduces in 3.15.0. As such, this constraint needs to be set: https://learn.microsoft.com/nl-nl/azure/developer/terraform/provider-version-history-azurerm#3150-july-21-2022

Implemented change in latest version 1.0.1.


cut command (ctrl+x) deletes whole line even if nothing selected

Godot version
v3.5.beta2.official [7a4f9dfb1]
System information
Mac OSX (Intel 2019)
Issue description
When in the script editor, press Ctrl+x (Cmd+x on mac).
The whole current line will be deleted. This often leads to annoyances if you are working in Emacs as Ctrl+x is such a common keybinding.
I often find myself accidentally deleting one line and then trying to run the game.
Steps to reproduce
When in the script editor, press Ctrl+x (Cmd+x on mac).
Minimal reproduction project
No response

Many editors have behaviors like this, i.e. copy/cut the whole line when nothing is selected. e.g. VSCode and JetBrains IDEs.

Perhaps then a way to disable this behaviour?
For me I rarely type anything in the script editor (rather using it as a separate screen), so this just causes an annoyance.

Cut can be useful, so the answer to cripple the script editor in some way (by moving the default cut key) doesn't sound great to me.

I think there is also an important difference in godot from most editors.
Since in godot you spend 90% of your time in other UI, whereas in VSCode you spent 90% of the time in the editor.

Another problem here is that when I accidentally cut something, I can press Ctrl + z to undo, but the lines are then selected. This causes other development flow issues.
For me these are not huge issues but something I see every day at least a few times and breaks my immersion as I struggle to get Godot to do what I feel it should be doing.

Sure, the following explanations are just my opinion, no offense meant.

The whole current line will be deleted. This often leads to annoyances if you are working in Emacs as Ctrl+x is such a common keybinding

This is only true for people who are used to Emacs. For people who use VSCode or similar software, they would expect the behavior how it is currently implemented.
I am guessing here, but I think there are more users that are used to VSCode or similar as compared to Emacs.

I often find myself accidentally deleting one line and then trying to run the game.

This feels more like a user error and while changing it may be beneficial to you, it certainly would cripple the experience for others.

perhaps adding a second shortcut for cut line (defaulting to ctr+x) when nothing is selected would fix this issue.

I don't think adding a second keybinding for cut is a good way.

In godot you spend 90% of your time in other UI (inspector) whereas in VSCode you spent 90% of the time in the text editor.

This is just not true and heavily depends on the user. For me I would say that the percentages could be switched because I spend most of my time in Godot writing code.

Another problem here is that when I accidentally cut something, I can press Ctrl + z to undo, but the lines are then selected. This causes other development flow issues.

I agree with this, but I don't think this has anything to do with the original issue and it should probably be made an issue of its own.
Conclusion
I certainly would be glad if Godot would work for everyone and the problem could be solved for you, but I think the current implementation is superior to your suggestion for the majority of the users.

I think the current implementation is superior to your suggestion for the majority of the users.

Thanks for the in depth reply. OK it makes sense that a lot of people want to keep their flow as similar to VSCode as possible.
What about adding a single toggle somewhere in the editor settings which enabled or disabled this feature?

I have made a pull request that solves this by adding a Project Settings checkbox that can disable this behaviour (it's on by default so no changes for most people).

Another problem here is that when I accidentally cut something, I can press Ctrl + z to undo, but the lines are then selected

If this is still an issue, make a separate bug report. You may tag me when doing so.

Resolved by #90743


(bug) Allow Bolt to use Puppet 6.19.z releases

Previously we had pinned Bolt to depend on Puppet >= 6.18.0 <=6.19.0
because when Puppet released 6.19.0 we picked it up before we had made
Bolt-side changes necessary to be compatible with the new Puppet
version. We restricted the Puppet gem to not pick up new versions so
that we could actively make similar updates in the future without
needing to do so immediately. However, this meant that some gems which
depend on Bolt and Puppet ended up resolving to an old version of Bolt,
which broke their use of the gem. This change means we'll pick up Z
releases of Puppet, but can still make any changes in Bolt we need to
before picking up the Y release.
!bug

Allow Puppet 6.19.1 as a dependency
This let's Bolt use Puppet 6.19.1 as a dependency.

CLA signed by all contributors.


fix build error due to missing declaration

../lib/usr/app/cli/cli.h: In function 'get_root':
../lib/core/log/cne_log.h:344:13: error: implicit declaration of function 'unlikely' [-Werror=implicit-function-declaration]
344 |         if (unlikely(!(exp)))

Please add a signed off line to the commit message as I can not commit it without that line. Thanks.

Error is possible to trigger here with: option('enable_asserts', type: 'boolean', value: true,


Remove unused RouteGuideClient and move RemoteTestClient to tests

Reference discussion: https://github.com/grpc/grpc/pull/4108#discussion-diff-44494393

cc @jcanizales

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM


example not working

I'm trying basic usage example
https://github.com/carpedm20/fbchat/blob/master/examples/basic_usage.py#L4
$ pip install fbchat
...
Successfully uninstalled fbchat-1.9.6
$ python3
Python 3.6.9 (default, Nov  7 2019, 10:44:02)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import fbchat
>>> session = fbchat.Session.login("<email>", "<password>")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
AttributeError: module 'fbchat' has no attribute 'Session'

Please see the examples on the v1 branch, or on ReadTheDocs.
The examples on the master branch is for the new, still unreleased version 😉


Last updated time missing

Last updated time is missing

@Rajath-BeeLab I can't reproduce.

@Rajath-BeeLab : I cant reproduce this. Tested it on all available devices with device mode in Chrome DevTools

Can't reproduce it.

It works in chrome. I could reproduce in safari desktop view itself..

it happening in iOS or apple device. All browsers in iOS

yes.. I can confirm issue exist on chrome of iOS too..

I’m using iPhone and couldn’t see last updated time. I dint have android device in hand to check. So I think this is issue arise only in iPhone or iOS devices

Also strange one.. When i try working in local on same safari browser, it works.
But when i open prod version it isn't..
Both below snaps are from safari on MacOS
Prod version:

local version:

I checked this and found the cause
We are checking date is valid or not by using new Date() safari returns NaN in this case while chrome parses is Without any issues. . We might need to use library like momentJS to fix this issue.

@Rajesh-Narayanappa87 your local might not have the latest changes.

Gotcha fam! Patched 🍃


Bug found when change the orientation of device

hi, I open the slide menu in horizontal then rotate the screen. When I open the slide menu again, I found that there maybe something wrong at the top of the menu. By the way, rotating the screen will force the menu to close without calling the function will close nor did close? How can I do to monitor it?

I have that same problem when I send the application to background with the drawer open and then resume it.

@victorlsn I try to solve this problem by add the codes under.
override func viewWillTransition(to size: CGSize, with coordinator: UIViewControllerTransitionCoordinator) {
super.viewWillTransition(to: size, with: coordinator)
slideMenuController()?.closeLeft()
}

Thanks!


Is there an option to only increment date part (year and month)?

I was wondering if I can configure release-it via command line in a way that release-it-calver-plugin only increases the date parts of the version.
For example, I have a master branch and a release branch.
Both year and month should be updated on master branch - every day (scheduled pipeline executing release-it) and or every time a pipeline runs (e.g. merge request pipeline executing release-it). The minor/patch versions however should be increased only when master is merged into release branch and thus a release with tag is created.
The main reason is that there are months in which no release is done and thus if this option is not available, the year and month would be wrong for our test and staging environments when year and/or month changed. However, if I run release-it on those environments the minor/patch counter would be wrong.
So my question is if there is a configuration option to do so?

You could try:
{
  "format": "<your format>",
  "increment": "calendar",
  "fallbackIncrement": "calendar"
}


remove usage of EventSource in favour of Event & Emitter

Event was a stepping stone towards the new event mechanism we now use. In favour for clarity and a compact codebase we should remove usages and implementation of EventSource et al. Staring with @bpasero

:+1:

Yeah!


config-linux.md: fix info

Signed-off-by: zhouhao<EMAIL_ADDRESS>

The changes in 5a47021 all look good to me.

LGTM

LGTM


How do I custom import path for prisma client ?

Discussed in https://github.com/omar-dulaimi/prisma-trpc-generator/discussions/18

Originally posted by kittipojsr July 20, 2022
By default prisma-trpc-generator use import type { Prisma } from '@prisma/client'; for prisma client. But I need to use custom path from prisma client generator schema output.

Released in https://github.com/omar-dulaimi/prisma-trpc-generator/releases/tag/0.4.0


Facebook Template in Conversations

Hi all,
I'm using conversations with DoctrineCache inside a symfony 3 application (Botman dev-master). I observe the following behavior inside my conversation class:

Using the ask() method with a question object
Using isInteractiveMessageReply to detect, if the user interacted with the message
Inside isInteractiveMessageReply reply with a facebook template

Once the facebook template is sent, I receive again the webhook call from facebook with the answer of 1. If I change my message from facebook template to "normal" text, I won't receive the answer of 1. again (as expected)
Any ideas?
Thank you.

I built the FB templates. Could you show me your code so I can try to reproduce the issue?

I just rewrote the complete conversation class and the issue is solved. Seems that I didn't build the facebook template correctly. However, it was visible in the messenger.

ok strange, but great it works now.


[ZT] Point to up-to-date Kubernetes example

Seems that this tutorial was copied from the Github example linked earlier.

@abelinkinbio Should we point to https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/deployment-guides/kubernetes/ instead?

Let's link to both


RTX 30xx compatibility

I have used pytorch 1.7.x stable release and 1.8.x nightly build with both Cuda 11.0 and 11.1 and keep running into a error when trying to use pre-trained efficientnet-l2. My python version is 3.8.6, and my GPU is RTX3090
I am using the pytorch segmentation models https://github.com/qubvel/segmentation_models.pytorch package, which uses this package to load the pre-trained efficientnet-l2 network.
The network loads fine but when I start training on the first iteration I get this error:

I believe this has to do with the gpu architecture's Cuda capability sm_86.
As I stated earlier neither updating pytorch to the nightly build nor updating Cuda from 11.0 to 11.1 got rid of the error.
Heres my current nvidia-smi output:

and nvcc--version output:

Interestingly efficientnet-pytorch https://github.com/lukemelas/EfficientNet-PyTorch works fine, although that package does not have a pre-trained efficientnet-l2.
I haven't tried to run with the other effecientnets from this package so I do not know if this is an issue with just the l2 net, but based on where there error is thrown:
\AppData\Local\Programs\Python\Python38\lib\site-packages\timm\models\layers\activations.py", line 39, in forward
return swish_jit_fwd(x)
I would assume that this applies to all of them.

@Jmzahn this isn't an issue with the code here but with PyTorch or the CUDA/cuDNN install.
My efficientnets use torchscript for swish activations for more speed. That requires the cuda/cudnn tooling to be setup properly and apparently there is an issue with whatever combo you have. Lukemelas doesn't have jit'd activations, only the memory efficient aspect.
You can disable the jit activations by passing no_jit=True in the create_model() fn. Also, you might be behind a bit relative to my latest commits, I added support for the native SiLU (proper name for swish) activation for PyTorch >= 1.7 which should avoid the jit activation, if you'd picked up that commit I wouldn't be seeing swish_jit_fwd but I'd see a native PyTorch SiLU op.
I should point out that the PyTorch 1.7 CUDA 11 release is using a problematic version of cuDNN (8.0.3 on Linux) that has quite a few regressions. Maybe it's using cuDNN 8.0.4 on the windows build? I've been only using the NGC PyTorch containers as they use the proper 8.0.4 ver of cuDNN.
Aside from all that, the L2 model is an absolute monster. Seems quite likely you'll hit OOM error next for a segmentation model, I can barely run them in validation on a Titan RTX at a reasonable batch size.

Thank you for your input, I had no clue what was causing the errors so this helped a ton.
I am guessing the Semantic models package is behind on which version of your package is installed as a dependency.
For reference for other people I believe the windows build is using cuDNN 8.0.4.
It does seem like I will run into OOM errors if I tried to train with the L2 model, so the B series of efficientnets will have to do.


[CLOUD-1915] - Include serviceaccount object into templates

Signed-off-by: Filippe Spolti<EMAIL_ADDRESS>

Outdated.


List Widget - add option to format front matter output as array

Feature request
Is your feature request related to a problem? Please describe.
Its not much of a problem, just a preference.
The list widget currently produces this format in the front matter.
mylist:
  - foo
  - bar

I would prefer to have an option to tell the widget to output it like this
mylist: [foo, bar]

Jigsaw (the SSG I use) Jekyll and Hugo (two of the most popular SSGs) support this format. I assume front matter generally works the same across other SSGs.
Describe the solution you'd like
Add a format option for list widget.
Example: format: "array"
- {label: "Tags", name: "tags", widget: "list", format: "array", required: false}

Describe alternatives you've considered
N/A
Additional context
N/A

I'd like this too. At the same time, it seems Hugo doesn't have a problem with this, so I guess it's not such high priority.

Any SSG that uses YAML front matter should allow that syntax. At first I thought it was SSG-specific but it's in the default YAML syntax.

Is no one checking this issue?

Both are valid yaml, why the preference?
Sent with GitHawk

Last time I checked NetlifyCMS doesn't produce .md files with arrays formatted like this.

It's preferrable for me when a post I'm creating has a long list of tags.
When I'm working on the md file in a code editor and there's a lot of them, the vertical list format takes up a lot of screen space before I can scroll down to the content.

Closing as stale and/or outdated.


Lost new untracked files

Hello there.
For the second time I experience very strange issue which leads to total lose of unstaged files :((((
I had some changes and few new files. I did:

git add
git commit

After running all the hooks I can see that all my new files are lost.
Thanks in advance for any help

Here is log from console:
cast-call-client on  integrate-tailwindcss [$✘!?] via ⬢ v12.14.1
➜ gst                                                                                21:12:54
On branch integrate-tailwindcss
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .eslintrc
	modified:   package-lock.json
	modified:   packages/client/.flowconfig
	deleted:    packages/client/.storybook/addons.js
	deleted:    packages/client/.storybook/config.js
	deleted:    packages/client/flow-typed/npm/styled-components_v3.x.x.js
	modified:   packages/client/package-lock.json
	modified:   packages/client/package.json
	modified:   packages/client/src/app.jsx
	deleted:    packages/client/src/assets/castcalls-logo.png
	deleted:    packages/client/src/assets/logo_black.png
	modified:   packages/client/src/components/Header.jsx
	modified:   packages/client/src/components/portfolio/PortfolioGrid.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTile.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTileWithPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/portfolio-tile/PortfolioTileInfo.stories.jsx
	modified:   packages/client/src/components/subscriptions/stories/InvolvementCard.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/SubscriptionGrid.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/components/SubscriptionPortfolioTile.stories.jsx
	modified:   packages/client/src/index.jsx
	modified:   packages/client/src/pages/landing/LandingPage.jsx
	modified:   packages/client/src/router/MainRouter.jsx
	modified:   packages/client/src/style-config.js

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	packages/client/.storybook/main.js
	packages/client/.storybook/preview.js
	packages/client/flow-typed/npm/classnames_v2.x.x.js
	packages/client/postcss.config.js
	packages/client/src/assets/Logos/
	packages/client/src/cc-kit/
	packages/client/src/components/Header.stories.jsx
	packages/client/src/tailwind-out.css
	packages/client/src/tailwind.config.js
	packages/client/src/tailwind.css
	packages/client/src/utils/MediaMatcher.js
	packages/tests/package-lock.json

no changes added to commit (use "git add" and/or "git commit -a")

cast-call-client on  integrate-tailwindcss [$✘!?] via ⬢ v12.14.1
➜ ga packages/client/package.json                                                                           21:12:55

cast-call-client on  integrate-tailwindcss [$✘!+?] via ⬢ v12.14.1
➜ gst                                                                                21:13:18
On branch integrate-tailwindcss
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	modified:   packages/client/package.json

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .eslintrc
	modified:   package-lock.json
	modified:   packages/client/.flowconfig
	deleted:    packages/client/.storybook/addons.js
	deleted:    packages/client/.storybook/config.js
	deleted:    packages/client/flow-typed/npm/styled-components_v3.x.x.js
	modified:   packages/client/package-lock.json
	modified:   packages/client/src/app.jsx
	deleted:    packages/client/src/assets/castcalls-logo.png
	deleted:    packages/client/src/assets/logo_black.png
	modified:   packages/client/src/components/Header.jsx
	modified:   packages/client/src/components/portfolio/PortfolioGrid.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTile.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTileWithPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/portfolio-tile/PortfolioTileInfo.stories.jsx
	modified:   packages/client/src/components/subscriptions/stories/InvolvementCard.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/SubscriptionGrid.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/components/SubscriptionPortfolioTile.stories.jsx
	modified:   packages/client/src/index.jsx
	modified:   packages/client/src/pages/landing/LandingPage.jsx
	modified:   packages/client/src/router/MainRouter.jsx
	modified:   packages/client/src/style-config.js

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	packages/client/.storybook/main.js
	packages/client/.storybook/preview.js
	packages/client/flow-typed/npm/classnames_v2.x.x.js
	packages/client/postcss.config.js
	packages/client/src/assets/Logos/
	packages/client/src/cc-kit/
	packages/client/src/components/Header.stories.jsx
	packages/client/src/tailwind-out.css
	packages/client/src/tailwind.config.js
	packages/client/src/tailwind.css
	packages/client/src/utils/MediaMatcher.js
	packages/tests/package-lock.json

cast-call-client on  integrate-tailwindcss [$✘!+?] via ⬢ v12.14.1
➜ gc -m 'integrate-tailwindcss'                                                                             21:13:19
husky > pre-commit (node v12.14.1)
  ✔ Preparing...
  ✔ Running tasks...
  ✔ Applying modifications...
  ✔ Cleaning up...
[integrate-tailwindcss 2c1a81f] integrate-tailwindcss
 1 file changed, 15 insertions(+), 4 deletions(-)

cast-call-client on  integrate-tailwindcss [$✘!] via ⬢ v12.14.1 took 2s
➜ gst                                                                                21:13:25
On branch integrate-tailwindcss
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .eslintrc
	modified:   package-lock.json
integrate-tailwindcss
	modified:   packages/client/.flowconfig
	deleted:    packages/client/.storybook/addons.js
	deleted:    packages/client/.storybook/config.js
	deleted:    packages/client/flow-typed/npm/styled-components_v3.x.x.js
	modified:   packages/client/package-lock.json
	modified:   packages/client/src/app.jsx
	deleted:    packages/client/src/assets/castcalls-logo.png
	deleted:    packages/client/src/assets/logo_black.png
	modified:   packages/client/src/components/Header.jsx
	modified:   packages/client/src/components/portfolio/PortfolioGrid.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTile.stories.jsx
	modified:   packages/client/src/components/portfolio/PortfolioTileWithPreview.stories.jsx
	modified:   packages/client/src/components/portfolio/portfolio-tile/PortfolioTileInfo.stories.jsx
	modified:   packages/client/src/components/subscriptions/stories/InvolvementCard.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/SubscriptionGrid.stories.jsx
	modified:   packages/client/src/components/subscriptions/subscription-grid/components/SubscriptionPortfolioTile.stories.jsx
	modified:   packages/client/src/index.jsx
	modified:   packages/client/src/pages/landing/LandingPage.jsx
	modified:   packages/client/src/router/MainRouter.jsx
	modified:   packages/client/src/style-config.js

no changes added to commit (use "git add" and/or "git commit -a")

Environment

OS: macOs Catalina 10.15.1
Node.js: 12.14.1
lint-staged: 10.0.0

FYI I also experienced a similar issue to this (not sure if it's the same thing as this is marked as fixed) with lint-staged 10.5.3, though I was luckily able to retrieve my files utilizing the tip from @MikeYermolayev above.

FYI I also experienced a similar issue to this (not sure if it's the same thing as this is marked as fixed) with lint-staged 10.5.3, though I was luckily able to retrieve my files utilizing the tip from @MikeYermolayev above.

Same here. I keep losing all the files including the existing one that have been modified. I keep those files open in VScode and then saving them again to restore. However this happens only in one repo and other repos are working fine. Everything is same like the version/OS/folder structure etc except that any changes made in the file in this repo are getting deleted. However it keeps some of the files, for e.g it keeps pacakge.json file but all my typescript files are keep getting deleted. As you can see at the end it says 1 deletion where in fact I have not deleted any files.
Here is the debug log
git version 2.32.0
lint-staged version  : ^12.3.3
husky > pre-commit (node v16.13.2)
  lint-staged:bin Running<EMAIL_ADDRESS>+0ms
  lint-staged:bin Options parsed from command-line: {
  allowEmpty: false,
  concurrent: true,
  configPath: undefined,
  cwd: undefined,
  debug: true,
  maxArgLength: 65536,
  quiet: false,
  relative: false,
  shell: false,
  stash: true,
  verbose: false
} +1ms
  lint-staged:validateOptions Validating options... +0ms
  lint-staged:validateOptions Validated options! +1ms
  lint-staged Unset GIT_LITERAL_PATHSPECS (was `undefined`) +0ms
  lint-staged:runAll Running all linter scripts... +0ms
  lint-staged:runAll Using working directory `/mnt/c/Repos/services` +1ms
  lint-staged:resolveGitRepo Resolving git repo from `/mnt/c/Repos/services` +0ms
  lint-staged:resolveGitRepo Unset GIT_DIR (was `undefined`) +0ms
  lint-staged:resolveGitRepo Unset GIT_WORK_TREE (was `undefined`) +1ms
  lint-staged:execGit Running git command [ 'rev-parse', '--show-prefix' ] +0ms
  lint-staged:resolveGitRepo Resolved git directory to be `/mnt/c/Repos/services` +24ms
  lint-staged:resolveGitRepo Resolved git config directory to be `/mnt/c/Repos/services/.git` +1ms
  lint-staged:execGit Running git command [ 'log', '-1' ] +25ms
  lint-staged:execGit Running git command [ 'diff', '--staged', '--diff-filter=ACMR', '--name-only', '-z' ] +23ms
  lint-staged:runAll Loaded list of staged files in git:
  lint-staged:runAll [
  lint-staged:runAll   '/mnt/c/Repos/services/package.json',
  lint-staged:runAll   '/mnt/c/Repos/services/src/shared/shared.module.ts'
  lint-staged:runAll ] +69ms
  lint-staged:getConfigGroups Grouping configuration files... +0ms
  lint-staged:getConfigGroups Grouping staged files by their directories... +0ms
  lint-staged:getConfigGroups Grouped staged files into 2 directories: +0ms
  lint-staged:getConfigGroups {
  lint-staged:getConfigGroups   '/mnt/c/Repos/services': [ '/mnt/c/Repos/services/package.json' ],
  lint-staged:getConfigGroups   '/mnt/c/Repos/services/src/shared': [ '/mnt/c/Repos/services/src/shared/shared.module.ts' ]
  lint-staged:getConfigGroups } +2ms
  lint-staged:getConfigGroups Searching config files... +1ms
  lint-staged:loadConfig Searching for configuration from `/mnt/c/Repos/services`... +0ms
  lint-staged:loadConfig Successfully loaded config from `/mnt/c/Repos/services/package.json`:
  lint-staged:loadConfig {
  lint-staged:loadConfig   './**/*.ts': [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ]
  lint-staged:loadConfig } +2ms
  lint-staged:getConfigGroups Found new config "/mnt/c/Repos/services/package.json" from "/mnt/c/Repos/services"! +4ms
  lint-staged:validateConfig Validating config from `/mnt/c/Repos/services/package.json`... +0ms
  lint-staged:validateConfig Validated config from `/mnt/c/Repos/services/package.json`: +0ms
  lint-staged:validateConfig {
  lint-staged:validateConfig   './**/*.ts': [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ]
  lint-staged:validateConfig } +1ms
  lint-staged:loadConfig Searching for configuration from `/mnt/c/Repos/services`... +3ms
  lint-staged:loadConfig Searching for configuration from `/mnt/c/Repos/services/src/shared`... +1ms
  lint-staged:loadConfig Successfully loaded config from `/mnt/c/Repos/services/package.json`:
  lint-staged:loadConfig {
  lint-staged:loadConfig   './**/*.ts': [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ]
  lint-staged:loadConfig } +2ms
  lint-staged:getConfigGroups Found existing config "/mnt/c/Repos/services/package.json" from "/mnt/c/Repos/services"! +6ms
  lint-staged:loadConfig Successfully loaded config from `/mnt/c/Repos/services/package.json`:
  lint-staged:loadConfig {
  lint-staged:loadConfig   './**/*.ts': [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ]
  lint-staged:loadConfig } +6ms
  lint-staged:getConfigGroups Found existing config "/mnt/c/Repos/services/package.json" from "/mnt/c/Repos/services/src/shared"! +6ms
  lint-staged:getConfigGroups Grouped staged files into 1 groups! +1ms
  lint-staged:chunkFiles Resolved an argument string length of 96 characters from 2 files +0ms
  lint-staged:chunkFiles Creating 1 chunks for maxArgLength of 65536 +1ms
  lint-staged:generateTasks Generating linter tasks +0ms
  lint-staged:generateTasks Generated task:
  lint-staged:generateTasks {
  lint-staged:generateTasks   pattern: './**/*.ts',
  lint-staged:generateTasks   commands: [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ],
  lint-staged:generateTasks   fileList: [ '/mnt/c/Repos/services/src/shared/shared.module.ts' ]
  lint-staged:generateTasks } +1ms
  lint-staged:makeCmdTasks Creating listr tasks for commands [ 'npx --no-install eslint -c ./.eslintrc.js', 'npm run compile' ] +0ms
  lint-staged:resolveTaskFn cmd: npx +0ms
  lint-staged:resolveTaskFn args: [ '--no-install', 'eslint', '-c', './.eslintrc.js' ] +0ms
  lint-staged:resolveTaskFn execaOptions: {
  cwd: '/mnt/c/Repos/services',
  preferLocal: true,
  reject: false,
  shell: false
} +0ms
  lint-staged:resolveTaskFn cmd: npm +2ms
  lint-staged:resolveTaskFn args: [ 'run', 'compile' ] +0ms
  lint-staged:resolveTaskFn execaOptions: {
  cwd: '/mnt/c/Repos/services',
  preferLocal: true,
  reject: false,
  shell: false
} +1ms
  lint-staged:chunkFiles Resolved an argument string length of 55 characters from 1 files +9ms
  lint-staged:chunkFiles Creating 1 chunks for maxArgLength of 65536 +0ms
[STARTED] Preparing lint-staged...
  lint-staged:GitWorkflow Backing up original state... +0ms
  lint-staged:GitWorkflow Getting partially staged files... +0ms
  lint-staged:execGit Running git command [ 'status', '-z' ] +58ms
  lint-staged:GitWorkflow Found partially staged files: [] +39ms
  lint-staged:GitWorkflow Backing up merge state... +1ms
  lint-staged:file Reading file `/mnt/c/Repos/services/.git/MERGE_HEAD` +0ms
  lint-staged:file Reading file `/mnt/c/Repos/services/.git/MERGE_MODE` +0ms
  lint-staged:file Reading file `/mnt/c/Repos/services/.git/MERGE_MSG` +0ms
  lint-staged:file File `/mnt/c/Repos/services/.git/MERGE_HEAD` doesn't exist, ignoring... +1ms
  lint-staged:file File `/mnt/c/Repos/services/.git/MERGE_MODE` doesn't exist, ignoring... +0ms
  lint-staged:file File `/mnt/c/Repos/services/.git/MERGE_MSG` doesn't exist, ignoring... +1ms
  lint-staged:GitWorkflow Done backing up merge state! +3ms
  lint-staged:GitWorkflow Getting deleted files... +1ms
  lint-staged:execGit Running git command [ 'ls-files', '--deleted' ] +43ms
  lint-staged:GitWorkflow Found deleted files: [] +22ms
  lint-staged:execGit Running git command [ 'stash', 'create' ] +22ms
  lint-staged:execGit Running git command [
  'stash',
  'store',
  '--quiet',
  '--message',
  'lint-staged automatic backup',
  '865dcc3e01539c2e4075d865e62bdcc2b693fb01'
] +77ms
  lint-staged:GitWorkflow Done backing up original state! +121ms
[SUCCESS] Preparing lint-staged...
[STARTED] Running tasks for staged files...
[STARTED] package.json — 2 files
[STARTED] ./**/*.ts — 1 file
[STARTED] npx --no-install eslint -c ./.eslintrc.js
[SUCCESS] npx --no-install eslint -c ./.eslintrc.js
[STARTED] npm run compile
[SUCCESS] npm run compile
[SUCCESS] ./**/*.ts — 1 file
[SUCCESS] package.json — 2 files
[SUCCESS] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
  lint-staged:GitWorkflow Adding task modifications to index... +24s
  lint-staged:execGit Running git command [
  'add',
  '--',
  '/mnt/c/Repos/services/src/shared/shared.module.ts'
] +24s
  lint-staged:GitWorkflow Done adding task modifications to index! +35ms
  lint-staged:execGit Running git command [ 'diff', '--name-only', '--cached' ] +34ms
[SUCCESS] Applying modifications from tasks...
[STARTED] Cleaning up temporary files...
  lint-staged:GitWorkflow Dropping backup stash... +21ms
  lint-staged:execGit Running git command [ 'stash', 'list' ] +21ms
  lint-staged:execGit Running git command [ 'stash', 'drop', '--quiet', 'refs/stash@{0}' ] +28ms
  lint-staged:GitWorkflow Done dropping backup stash! +82ms
[SUCCESS] Cleaning up temporary files...
  lint-staged Tasks were executed successfully! +24s
[feature/package_upgrades 0aee73e] Added missing file
 1 file changed, 1 insertion(+), 1 deletion(-)


Fix namings

[x] Folders.
[x] Files be Pascal

Files in a12e57b

Folder Names still have to be talked about

Yea - warnings.


[Defaults]: Audio/Subtitle Languages

Link to File
pmm: languages
Version Number
1.18.0-develop25 (Docker)
What branch are you on?
nightly
Describe the Bug
Several issues and errors regarding this.

https://metamanager.wiki/en/latest/defaults/overlays/languages.html has the wrong ISO country code for S
It seems odd and arbitrary to make all but six languages false by default. Under what circumstances would a user want to see that the video contains Portuguese audio but not Swedish audio? The only way to fix this is to manually add something like the following:

        template_variables:
          use_ko: true # Korean
          use_zh: true # Chinese
          use_da: true # Danish
          use_ru: true # Russian
          use_it: true # Italian
          use_hi: true # Hindi
          use_te: true # Telugu
          use_fa: true # Farsi
          use_th: true # Thai
          use_nl: true # Dutch
          use_no: true # Norwegian
          use_is: true # Icelandic
          use_sv: true # Swedish
          use_tr: true # Turkish
          use_pl: true # Polish
          use_cs: true # Czech
          use_uk: true # Ukrainian
          use_hu: true # Hungarian
          use_ar: true # Arabic
          use_bg: true # Bulgarian
          use_bn: true # Bengali
          use_bs: true # Bosnian
          use_ca: true # Catalan
          use_cy: true # Welsh
          use_el: true # Greek
          use_et: true # Estonian
          use_eu: true # Basque
          use_fi: true # Finnish
          use_fl: true # Filipino
          use_gl: true # Galician
          use_he: true # Hebrew
          use_hr: true # Croatian
          use_id: true # Indonesian
          use_ka: true # Georgian
          use_kk: true # Kazakh
          use_kn: true # Kannada
          use_la: true # Latin
          use_lt: true # Lithuanian
          use_lv: true # Latvian
          use_mk: true # Macedonian
          use_ml: true # Malayalam
          use_mr: true # Marathi
          use_ms: true # Malay
          use_nb: true # Norwegian Nokmåuse
          use_nn: true # Norwegian Nynorsk
          use_pa: true # Punjabi
          use_ro: true # Romanian
          use_sk: true # Slovak
          use_si: true # Slovenian
          use_sq: true # Albanian
          use_sr: true # Serbian
          use_sw: true # Swahili
          use_ta: true # Tamil
          use_ur: true # Urdu

I don't get why there are two types of Norwegian listed but not many other languages like Armenian. Why are not all ISO-639 available?
Persian comes up as Farsi even though there's no Persian in the documentation.

i think we fixed this in nightly
we didnt want to overwhelm people with them all being true off bat so thats why theres only 6
you can also just make a list of those you want to use under the languages template variable
we started with a list of country flags and are trying to match them with languages some get left out some we may not have had flags for im happy to add any if you can tell me its code and what flag it should have
is the pesian language not farsi?

Can this infromation be added to wiki and example? We should enable all languages - weight is already there to apply, This 6 language supreme pack doesn't make sense, quite opposite is preferred - disable the most frequent languages and show unique language labels.

its already been added its just only on the nightly wiki as that feature is only in nightly

May I suggest changing the country flag for catalan and use Andorra (ad) instead of Spain (es)?
The reason is that catalan is the official language in Andorra, and it is the only country with catalan as main/single official language.


Debug Console does not scroll

Issue Type: Bug
I've written a simple python file that generates generates output in a loop, the debug console is filling with text and when it's full, instead of showing the last line of text, it doesn't scroll down. My launch.json file looks like this:
        {
            "name": "PI - Gyro Testing - Wired",
            "type": "python",
            "request": "attach",
            "port": 5678,
            "host": "<IP_ADDRESS>",
            "preLaunchTask": "Launch Remote PI Wired Testing Container",
            "pathMappings": [
                {
                    "localRoot": "c:\\Users\\omart\\Project",
                    "remoteRoot": "/src/repos/"
                }
            ],
            "internalConsoleOptions": "openOnSessionStart",
            "postDebugTask": "Kill Remote PI Testing Container",
            "justMyCode": false,
        }

and the code I run looks like this :
from gyrosensor import GyroSensor
from ev3dev2.sensor import INPUT_4
import time
import logging

logging.basicConfig(level=logging.INFO, format='%(asctime)s:%(levelname)s:%(threadName)s:%(message)s')
log = logging.getLogger(__name__)

sensor6 = GyroSensor(INPUT_4, 6)
print('sensor created...')
while True:
    time.sleep(5)
    print('5 sec passed...')

The class implements a thread that loops and sends things to the logger, which prints it on the debug console. But then it won't scroll automatically and I'm pretty certain it did before...
 Let me know if you can still see it with todays vscode insiders

Excellent, it works now!! :) thanks for fixing this.

Thanks for letting us know


Add connection templates

Description
As secribed in the issue #218 , ConnectionTemplateProvider now supports EthernetNetwork, FcNetwork, NetworkSet and FCoENetwork
Rubocop seems to be happy, manipulation with resources works fine - tested with OneView Synergy edition.
Check List

[x] New functionality includes testing.

[x] All tests pass ($ rake test).

[x] New functionality has been documented in the README if applicable.

[x] New functionality has been thoroughly documented in examples (please include helpful comments).

[x] Changes documented in the CHANGELOG.

Thank you. Will adjust.

@fgbulsoni I've made some changes. I've created extra method load_connection_templates where I'm calling load_template_from_resource. I've done so because we're loading these templates in two actions: create_or_update and reset. Tests are passing.
Tomorrow morning I'm gonna test them against the Synergy.
Will send an update once it's tested.

Functionality tests:
FC networks
code
oneview_fc_network 'Fibre Channel A' do
  client oneview_sdk_client
  data(
    fabricType: 'FabricAttach',
    autoLoginRedistribution: true
  )
end

oneview_connection_template 'Update connection template: Fibre Channel A' do
   client oneview_sdk_client
   associated_fc_network 'Fibre Channel A'
   data(
     bandwidth: {
       maximumBandwidth: 1000 * 8,
       typicalBandwidth: 1000 * 8
     }
   )
end

Result:

Network sets
code:
oneview_network_set 'network_set' do
  client oneview_sdk_client
  ethernet_network_list ['network_1', 'network_2']
end

oneview_connection_template 'Update connection template: network_set' do
   client oneview_sdk_client
   associated_network_set 'network_set'
   data(
     bandwidth: {
       maximumBandwidth: 1000 * 10,
       typicalBandwidth: 1000 * 10
     }
   )
end

Result:

overall, I'm happy with the functionality :)

@jsmartt Please review again since I made some changes to the PR. Once we have another approval I'll also give mine.

@jsmartt There you go, updated according to comments. Please review again whenever you have the time.
:octocat: :taco:

@jsmartt @tmiotto Hopefully now we've covered all fronts in this PR. Please let me know if there's anything else that catches your attention or if this is good to go.

Is this ready to be merged?

Is this ready to be merged?

It is, I was just waiting for Travis to finish. Merging atm the moment.

Thank you very much! You're my superheroes :rocket:


Add TokenId to redeemInstructionsHashIsAllowed for Redeem Contracts

Adding tokenId to redeemInstructionsHashIsAllowed in order to set redeem permissions to be token specific rather than across the collection

looks good!


Queuedrop

this might already be enough to fix the i2c issue
please test when possible

@TanDro i think merging this and closing #93 might be premature without actually making sure that it works as advertised

@jhalmen you are totally right


then should be chainable even with no return

If a promise resolves and then onfulfilled returns nothing, then it shold behave as if onfulfilled does not exist i.e. return Promise::resolve( promise1 value )
Likewise if a promise rejects and onrejected returns nothing, then it needs to act as if onrejected is not a function so pass through the rejection
Finally if a non promise is returned from either onfulfilled or onrejected, then it needs converting to Promise::resolve( returned value )

This is now resolved


P0 turns into P1 after using uBit.audio.setPin(uBit.io.P1)

See https://github.com/microbit-foundation/micropython-microbit-v2/issues/69#issuecomment-855948709
Reproduction in C++ using CODAL v0.2.28:
#include "MicroBit.h"

MicroBit uBit;

int main() {
    uBit.init();

    uBit.serial.printf("== start ==\r\n");
    uBit.serial.printf("P0.name=%d\r\n", uBit.io.P0.name);
    uBit.serial.printf("P1.name=%d\r\n", uBit.io.P1.name);
    uBit.serial.printf("P2.name=%d\r\n", uBit.io.P2.name);

    uBit.audio.setPin(uBit.io.P1);

    uBit.serial.printf("== end ==\r\n");
    uBit.serial.printf("P0.name=%d\r\n", uBit.io.P0.name);
    uBit.serial.printf("P1.name=%d\r\n", uBit.io.P1.name);
    uBit.serial.printf("P2.name=%d\r\n", uBit.io.P2.name);

    for(;;);
}

Output:
== start ==
P0.name=2
P1.name=3
P2.name=4
== end ==
P0.name=3
P1.name=3
P2.name=4

From then on, P0 behaves like P1 because its .name field has been overwritten with "3".

Thanks @dpgeorge . I can see why: MicroBitAudio::pin is a NRF52Pin & reference.
@finneyj Should I simply change the internal MicroBitAudio::pin to a pointer?

Yes please @martinwork - absolutely the thing to do.
Apologies @dpgeorge.

Created PR https://github.com/lancaster-university/codal-microbit-v2/pull/116.

Thanks for the quick turn around!  Can confirm the bug is fixed.

Thanks for confirming @dpgeorge


view source link at top of page points to wrong url

This fixed and closed but not deployed.
On Wed, 21 Jan 2015 16:15 Pete LePage<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1108.


Package spark-xml in a python wheel so that it can be used with Delta Live Tables

It is not possible to install jar packages with Delta Live Tables, but the jars can be shipped with python wheels like it is done for other Spark projects.

It is a JVM library; I don't think a .whl helps?


Benchmark: Quantile Compression

I've integrated quantile compression into Turbobench Compression Benchmark
using the ffi c-interface for 32/64 bits integers.
Executables for windows and linux can be downloaded from releases.
I've made also a quick test with 32-bits lz77 offsets:

turbobench -ezstd,9/qcomp32,8 silesia_o.u32

      C Size  ratio%     C MB/s     D MB/s    Name            File
    30556963    55.6      91           260    qcomp32 8       silesia_o.u32
    33077995    60.1       7          1048    zstd 15         silesia_o.u32
    33242362    60.4      61          1040    zstd 9          silesia_o.u32

More benchmarks are now available.

Summary: at the chosen compression levels, Quantile Compression compresses much faster and gets better compression ratio in most facets, but notably gets a worse ratio on decimal floats and interleaved or shifting distributions. Quantile compression also decompresses much more slowly. I have been aware of these weaknesses and expect to address the compression ratio issues and part of the decompression speed issue in a future format (though I do not plan to compete on the highest decompression speeds).
@powturbo Is there an explanation of each dataset used here? Also, I don't see version information - would appreciate if you could point me to that or add it.
Closing the issue as there is no action required.

I hope you'll continue to improve your excellent quantile compression. I see a lot of potential in improving the decompression speed.

lz77 offsets are the output of lz77 compression algos like zstd. This is in general a smooth increasing distribution. Large integers are more common.
The other datasets are described in the paper
Large-Alphabet Semi-Static Entropy Coding Via Asymmetric Numeral Systems

I prefer to use real datasets used in academia in order to facilitate a comparison.


Update libgit2 submodule.

This updates the libgit2 submodule to latest master.
As several public struct members as well as some functions' parameters/return values have changed fundamental types (e.g from git_off_t which is an int64_t to git_object_size_t which is an uint64_t) I bumped the minor versions of both libgit2-sys and git2-rs (meaning it's equivalent to a major version bump for 0.x versions). As I'm not familiar with the version increment policy, let me know if that's wrong.

I guess I'll have to get a VM with Windows up and running tomorrow to figure out why the Windows build fails.

The change from enum to uint32_t for flags in some structs is what tripped me up. On Windows with msvc, where git_enum! uses i32, the raw enum values must be cast to u32 for rustc to be satisfied.
The libgit2 pull request which introduces this change mentions the ergonomic downsides for C++ that results from using an uint32_t, which may be worth mentioning.
As the usage of raw flags is hidden behind methods in the Rust API, the numeric casts don't affect users of git2-rs unless they are using raw values directly.

Everything looks great to me here thanks!
For the enum changes, could the type definitions for each type be switched to u32 all platforms too? That should remove the need ideally for the as cast when using the named constant values.

I tried to do that (by using pub enum git_merge_flag_t: u32 in the git_enum! definition for all the affected structs) but it led to errors on Windows for the systest suite related to the structs.

Sorry for the delayed response, but could you gist what the errors look like in that case?

This is the output I get when I set the git_enum! type to u32 explicitly for these three enums.
RUNNING ALL TESTS
bad git_merge_flag_t signed: rust: 0 (0x0) != c 1 (0x1)
bad git_merge_file_flag_t signed: rust: 0 (0x0) != c 1 (0x1)
bad git_stash_apply_flags signed: rust: 0 (0x0) != c 1 (0x1)

The tests that fail all seem to be generated as such, with just the enum name changed:
#[inline(never)]
#[allow(non_snake_case)]
fn sign_git_stash_apply_flags() {
  extern {
    #[allow(non_snake_case)]
    fn __test_signed_git_stash_apply_flags() -> u32;
  }
  unsafe {
    same(((!(0 as git_stash_apply_flags)) < (0 as git_stash_apply_flags)) as u32,
      __test_signed_git_stash_apply_flags(), "git_stash_apply_flags signed");
  }
}

I don't understand what information the systests are generated from, but that a test that covers signedness fails when the type is set to unsigned at least makes some sense based on the name alone. (If it makes sense to someone who understands the tests more deeply is unclear to me.)

Ah ok no worries! I think that the definitions may be a bit odd at the C layer, but that's ok. Let's go ahead with this and we can improve it later if necessary!


Cursor appears at the end of a label when updating it's text

Hi,
I'm using the library with STM32 board and an ILI9341 display. Everything works fine except updating label's text dynamically - I'm having an unexpected vertical line (cursor?) at the end of the label. There is no vertical line when the label is first created. I'm using simple code for tests:
static lv_obj_t * glabel;
void lv_tutorial_objects(void)
{
    lv_obj_t * scr = lv_page_create(NULL, NULL);
    lv_disp_load_scr(scr);

    glabel = lv_label_create(scr, NULL); /*First parameters (scr) is the parent*/
    lv_label_set_text(glabel, "Object usage demo");  /*Set the text*/
    lv_obj_set_x(glabel, 50);                        /*Set the x coordinate*/
}
void lv_tutorial_task(void)
{
    static int i = 0;
    lv_label_set_text_fmt(glabel, "i = %d", i++);  /*Set the text*/
}

So when I call lv_tutorial_task periodically the label's text changes, but a vertical line appears at the end (at length position of the initial "Object usage demo" text)

I couldn't find a way to disable it. Thank you

Just figured it out that it is my SPI DMA flush_cb implementation issue. Without using DMA the label is updated correctly


Proposed App File Structure

So, I've learned a lot building this app. Along with that, I've gained a deeper appreciation for code organization. I think what's going on now has a few pain points and I'd like to spec out something different. Currently there's a react branch that has exposed a few things I hadn't noticed about how this app is organized.
Models
The concept and rules behind challenges are slightly messy and I think this can be better. #168 was the beginning of this, but it needs to be even better so someone else can pick this up and maintain it. I'm not sure if we need a whole new database schema, but the code that represents it needs to be better.
What exposed how messy this became was when I tried to model some React components after the actual data models. The attempt was to create a one-to-one mapping from model class to a container component that loaded the model from the api. This got gross (and confusing) pretty fast. I think using a new file structure could combat some of these issues.
A new file structure you say?
I recently read this blog post, which lead to this stack overflow article, which lead to this repo. The main take away I got was to move away from the controllers/ models/ views/ structure. Instead I want to move to a feature specific structure. For instance, for our performances feature, we'd have a folder structure that looks like this
/performances
├── index.js
├── performances-controller.js
├── performances-controller.test.js
├── performacnes-model.js
├── performances-model.test.js

A few things to note:

Each method and controller is accompanied with it's own test file
No views (because React)

Then, we'd combine each feature into a structure that would look something like this
.
├── client
│   ├── public
│   │   ├── index.html
│   ├── rest of react app
├── db
│   ├── index.js
│   ├── queries
│   │   ├── index.js # I'm not sure if I'm thrilled with that here
│   ├── schema.sql
├── config
│   ├── index.js
│   ├── routes.rb
│   ├── ... other necessary files
├── jobs
│   ├── index.js
│   ├── send challenge email
│   ├── ... other necessary files
├── server
│   ├── ...features (performances, challenges, results, users, etc)
│   ├── server.js # hooks everything up together (like app.js is doing now)

Those are my current thoughts
I'm currently talking to myself, so of course I agree with me.
cc/ @btmills - Would you mind giving this a 👀 if you have the time/want?
cc/ @tarebyte - I know the rails dev in you wouldn't like this, but I'd love an opposing opinion if you have the time

My current side project has a similar organization scheme focused more around feature instead of function. Particularly at work, organizing by function (reducers/, components/) worked fine up to a point, but now components/ particularly has become unwieldy. We're trying an experiment to organize new code by feature, and I think it's going well so far. I don't have enough data to tell you whether this scheme is going to work, but it's what I'm trying.

Self: ended up with a solution that improves what is currently on master. Closing


Dont run unscaled processes

I use dokku-app-predeploy-tasks to run any processes with a scale of zero pre deploy, but this plugin treats zero scale as an error when I think it should just not run the process (ditto for processes absent in the SCALE file).
This also means if I want to temporarily stop my worker processes I can scale to zero:
dokku scale web=1 worker=0

Support for this has been added to master. I'm closing this out.


Cosmetic: Change relative imports to absolute imports

Most of the code base uses absolute imports, but we used relative imports in a few places. The case for using relative imports is that it theoretically makes it easier to pluck the code and stick it somewhere else. Sure, but there's no way we're moving this code somewhere else, so I'd rather the imports were clearer and more explicit.
Given that, I changed all the relative imports to absolute imports.
Minor r?

Actually, I think if travis is cool with this, I'll just merge it. It's pretty straight-forward. Bad imports will fail immediately.

Travis is green--merging!


Door sensor konke

Hello,
To start thank you for your work I use the plugin from the start it's perfect :)
Here I have aqara and konke door sensor, the AQARA sensor creates a 'DOOR CONTACT' device the konke sensor creates a 'CONTACT' device I changed the sensor to 'DOOR CONTACT' but the open / close direction and reverse is it possible to correct for the konke sensors the creation of a device 'DOOR CONTACT' and have the right direction opening / closing?
Thank you
Additional information
Zigbee2MQTT version: last dev (git pull today 02/07/2020)
Python version: Python 3.7.3
Domoticz version: 2020.2
Plugin version: last (git pull today 02/07/2020)

Aqara sensors were the first supported by the plugin and to me, quite logical was to use DoorSensor instead of Contact, but later I receive feedback that others prefer just regular contact as these sensors could be placed on windows for example. That's why all later door sensors use Contact.
You can basically achieve desired behavior by switching to Door Lock Inverted type

Okay I can understand that some people wanted the contact mode no worries but the logic would like that when the window is closed and the sensor in contact with the magnet declares to close in domoticz outside the it declares open normally window to close in domoticz that should put close don't you think?

I'm not sure I got your point, could you please attach some screens maybe

Here is a picture the state in domoticz should be opened not close
[url=http://www.noelshack.com/2020-27-4-1593715631-capture.png][img]http://image.noelshack.com/minis/2020/27/4/1593715631-capture.png[/img][/url]
[url=http://www.noelshack.com/2020-27-4-1593715631-img-0180.jpg][img]http://image.noelshack.com/minis/2020/27/4/1593715631-img-0180.png[/img][/url]

Please consider switching to the next version of the plugin #458.
Reopen this issue in case of any issues.


@on-per-page-change event getting called twice

Issue Type (delete the irrelevant ones)

[x] Bug

Specs
What version are you using?
^2.18.1
What browser?
Chrome
Expected Behavior
What did you expect to happen?
Getting called only once when I change the Per page dowpdown
Actual Behavior
What actually happened?
Method gets called twice
Steps to Reproduce the Problem
Please detail your steps here
1.Using

jsfiddle
If you provide a jsfiddle reproducing the issue, it'll be addressed much faster.
you can use this as base
`<vue-good-table
mode="remote"
@on-search="onSearch"
@on-page-change="onPageChange"
@on-sort-change="onSortChange"
@on-column-filter="onColumnFilter"
@on-per-page-change="onPerPageChange"
:totalRows="totalRecords"
:isLoading.sync="isLoading"
ref="my-table"
:columns="columns"
:rows="rows"
:line-numbers="true"
:search-options="searchOptions"
:sort-options="sortOptions"
:pagination-options="paginationOptions"
:select-options="selectOptions"
@on-selected-rows-change="selectionChanged"
styleClass="vgt-table striped bordered"
>

Add

  <template slot="table-row" slot-scope="props">

      <router-link :to="{ name: 'Profile', params: { empId: props.row.id } }" class="ti-pencil" tag="a"></router-link>

      {{props.formattedRow[props.column.field]}}

  </template>
</vue-good-table>`

2.21.9 should fix this.


Cloud authentication state should be cleared if API key is changed

We should keep track of the API key used when saving cloud auth state and clear the session token if a new API key is used to avoid confusing error states.

Moved to internal tracker: https://filestack.atlassian.net/browse/FS-3353


Use CancellationToken where it should

┆Issue is synchronized with this Asana task

➤ Einar Ingebrigtsen commented:
I pulled this in - couldn't see anything fundamentally flawed here and also we're doing the holistic code-review, hoping we're catching the big issues from that.


docs(output): Update behaviour for output.library and commonjs2

https://github.com/webpack/webpack/pull/11817#issuecomment-731119689

@pustovalov Thanks for your contribution.


Setup SFC doesn't compile development with development flag "_file" when component is process for devtools to show setup function

Version
3.2.29
Reproduction link
github.com/antfu/vitesse
Steps to reproduce
Pull the repo, or just follow the getting started steps with pnpm. While I provided the vitesse starting repo, you could use the vite repo as well. See the below for details from both project starts paths.
On Viteese:
If you just do a build with the the standard flow, then do a "pnpm preview" you will see the devtools and your layout will be Anonymous Component and the Page will be Anonymous Component.
On Vite:
Change the the dev script to the following: '"dev": "vite build --watch --mode 'development'"
Open up your chrome devtools and note that the Vue devtools should be present as you changed the mode to "development" When reviewing the component structure of the devtools, none router based components show up as Anonymous Component
What is expected?
The component file name should be visible through the devtools component tree as well as the setup properties.
What is actually happening?
The component is showing up as "Anonymous Component" and the setup method properties are not visible for the component.

Router components are processing fine through the dev tools tree. I submitted an issue on the devtools and the Guillaume Chau gave me the following message.
"Looks like it's an issue with the component compiler. The devtools uses a development-only property __file added to component definitions when the component is processed."
I figured since the core team is in control of the render function and processing, this was the place to submit the issue. Let me know if I need to place the issue to the vite team.
Here is the issue on the vue/devtools board. https://github.com/vuejs/devtools/issues/1564#
You will see a screenshot of the issue and some background as I was trying to figure out how to consistently reproduce.

This is an issue with vite's plugin, which only adds this property if the dev-server is running:
https://github.com/vitejs/vite/blob/5306234aad7e7432fb55c6033a63c6cf74493c3f/packages/plugin-vue/src/main.ts?_pjax=%23js-repo-pjax-container%2C div[itemtype%3D"http%3A%2F%2Fschema.org%2FSoftwareSourceCode"] main%2C [data-pjax-container]#L105-L108

Thanks @LinusBorg I submitted this to the Vite team and will keep an eye out on #5218


Split out 400 to 403 metric transformation

The previous build failed to deploy. It looks like MetricTransformations can only contain one transformation. Which begs the question, "why make it an array?".

:+1: