custom cell edit mode can we have on keyboard events like pressing 'tab' key 'enter' key

I am having a requirement of table inline editing, I need to allow the user to edit row wise from one cell to other by pressing tab (and the previous cell content should be saved when user moved from one cell to another cell by pressing tab)
Is there any solution to add multiple event to
const cellEditProp = {
mode: ['click','keydown','keypress']
};
If we achieve this it will a big help to user without using mouse he can edit the table with in less time
Thanks in advance

@hctslm, thanks for advice, I know this feature will be useful, but currently I have no much time to do this, so PR is welcome :)
If I have time in the future, I'll back to support this feature 👍
Thanks

Is anyone working on this right now? I'm planning on giving it a try for a project I'm working on right now and am happy to contribute my work to the codebase if everything goes smoothly.

@samfisher908, I think there's no one work on it and this issue may start to handle after v3.0.0 release for me(current still on beta), so you can take a look for codebase and let me know if you have any question.
PR is welcome, thank you :)

Sorry @samfisher908, I didn't see your comment on this work.., #1015 is my solution to resolve this features, if you would like to PR, you just sent your PR welcome :D

duplicate #693 ?

Forgot to close it and already fixed on v3.0.0


Expression - name space conflict with Xcode 16/iOS 18

Build Information
0.15.3
Xcode Beta 16
iOS 18/macOS 15
Using Swift Package
When updating to the latest Xcode beta 16 there is a name space conflict between the SGLite struct Expression and the new Expression found in Apple's Foundation framework. Attached are screenshots of both. I will attempt to fix this and if I do I will submit a PR

To anyone who is having this issue, a temporarily fix would be adding a namespace before the Expression
Example:

Old way
Expression<String>("id")
New way
SQLite.Expression<String>("id")

This would fix this issue

Thank you JohnnyTseng, great info

@tcollins590 You could define a typealias at file level which makes it globally visible:
typealias Expression = SQLite.Expression

Or import SQLite.Expression


Fix installer

Previous installer required the use of exec, we solve this problem and allow the user to directly apply migrations.
This PR should bring the User Experience of the installation very close to what Lychee v3 was:
download the zip, extract and set up.

As usual, untested but looks good.

https://www.youtube.com/watch?v=rR4n-0KYeKQ
:laughing:


add rust docker file

fix #6

Nice! Can I bother you to write a sample Rust application that compiles correctly using your Docker image and outputs first two command line arguments to stdout (just like all other starter kits)?
Repo is here: https://github.com/icfpcontest2020/starterkit-rust/

Yes. Here is it: https://github.com/garasubo/icfpc-docker/tree/master/rust


fix(cli): init command should add FST helm chart repository

Description
This pull request changes the following:

setup FST helm repository on init command
encapsulate chart management functionalities in ChartManager class for reusability

Limitation
It only uses the latest published chart version and unable to use latest commits from master branch (so currently it fails to deploy the latest envoy-gateway fix). We need to add the capability to use chart from a local repo(assuming user has cloned full-stack-testing repo).
Related Issues

Closes #457

:tada: This PR is included in version 0.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


IPython console: add horizontal scrolling bar

This is rather a feature request or an option for those who like it.
I use quite often pandas and sometimes the columns number is too large. Printing the columns and inspecting few first rows is a common practice. Spyder wraps the columns on top of each other and thus the user sometimes find it hard to analyse quickly the data specially if the work is done in lower than 15 inch laptop screen.

For example in Pycharm the IPython windows shows the full length of all columns. It includes a horizontal scroll bar if the screen size does not  allow displaying all columns.
Therefore, is it possible to make an option for the user to show a scrolling bar in IPython console which should avoid long texts or Dataframes being wrapped around.

Thanks alot.
Regards

Spyder version: 4 beta1
Python version: 3.6
Qt version:
PyQt version:
Operating System name/version: windows

This is not something we can solve here. Please open it in this repo:
https://github.com/jupyter/qtconsole


The app will crash due to an uncaught exception in ParseUserProvider->retrieveById()

Add null return value for when the Parse user has been deleted and the session has not been closed.
Although that scenario won't happen frequently on production, during development and testing of registration of user accounts it happens a lot.
Basically, the parse query will throw an exception if the ParseObject with the given id does not exist, if that happens we return null.

Also, from memory doesn't Parse return empty arrays when an object isn't found? Furthermore, this code just catches a generic Parse Exception. What if an exception is thrown for some other reason? The above code would return null implying the user wasn't found which may not be the case, there could be a Parse Client exception


Improvement: Tool Icons & Description

If you add a "caption" and "description" to the "$:/plugins/danielo515/encryptTiddler/crypt-button", the "View Toolbar" (see Screen Shot 1) will be populated with this data under "ControlPanel" (see Screen Shot 2).
Thanks for your consideration!
Fields:

caption: {{$:/core/images/locked-padlock}} Encrypt/Decrypt
description: Encrypt or decrypt this tiddler only

Screen Shot 1

Screen Shot 2

Thanks for the detailed issue @mrmattson
Just added the suggested changes. Will be live as soon as it builds

Thanks for the detailed issue @mrmattson
Just added the suggested changes. Will be live as soon as it builds


chore(deps): update angular to v16

v14.10.1 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


No Sensors Being Created

I have switched to this integration as the default integration isnt working anymore.  I have configured the connect however even after leaving for 24 hours im not seeing any sensors being created.
Im pretty much using the default config you have posted in the readme.  Is 90 days too much?
Nothing is being logged in the logs either so i cant even look at that.

Can you confirm you still don't see them, do you have any error message ?

Sorry, my internet has been down for 3 days (seperate issue).  Just reloaded the plugin and will monitor.  I have enabled debug logging and so far the only thing i can find is this
This error originated from a custom integration.
Logger: custom_components.trakt_tv.apis.trakt
Source: custom_components/trakt_tv/apis/trakt.py:197
Integration: Trakt (documentation, issues)
First occurred: 21:27:20 (160 occurrences)
Last logged: 21:28:14
Show chuck can't be extracted due to 'NoneType' object is not subscriptable
Show californication can't be extracted due to 'NoneType' object is not subscriptable
Show utopia can't be extracted due to 'NoneType' object is not subscriptable
Show flesh-and-bone can't be extracted due to 'NoneType' object is not subscriptable
Show the-inbetweeners can't be extracted due to 'NoneType' object is not subscriptable

`
This error originated from a custom integration.
Logger: custom_components.trakt_tv.apis.trakt
Source: custom_components/trakt_tv/apis/trakt.py:58
Integration: Trakt (documentation, issues)
First occurred: 19 February 2024 at 23:52:20 (3 occurrences)
Last logged: 19 February 2024 at 23:52:21
Can't request shows/155536/progress/watched with get because it returns a 502 status code with content         api.trakt.tv | 502: Bad gateway             Bad gateway Error code 502   Visit cloudflare.com for more information.  2024-02-19 23:52:20 UTC          You  Browser  Working         London   Cloudflare   Working       api.trakt.tv  Host  Error        What happened? The web server reported a bad gateway error.   What can I do? Please try again in a few minutes.      Cloudflare Ray ID: 85826c48cd9a52b7 •  Your IP: Click to reveal  •  Performance & security by Cloudflare        . Retrying at least 9 time(s).
Can't request shows/155536/progress/watched with get because it returns a 502 status code with content         api.trakt.tv | 502: Bad gateway             Bad gateway Error code 502   Visit cloudflare.com for more information.  2024-02-19 23:52:20 UTC          You  Browser  Working         London   Cloudflare   Working       api.trakt.tv  Host  Error        What happened? The web server reported a bad gateway error.   What can I do? Please try again in a few minutes.      Cloudflare Ray ID: 85826c48e99a5316 •  Your IP: Click to reveal  •  Performance & security by Cloudflare        . Retrying at least 9 time(s).
Can't request shows/140481/progress/watched with get because it returns a 502 status code with content         api.trakt.tv | 502: Bad gateway             Bad gateway Error code 502   Visit cloudflare.com for more information.  2024-02-19 23:52:21 UTC          You  Browser  Working         London   Cloudflare   Working       api.trakt.tv  Host  Error        What happened? The web server reported a bad gateway error.   What can I do? Please try again in a few minutes.      Cloudflare Ray ID: 85826c4aca7a48ac •  Your IP: Click to reveal  •  Performance & security by Cloudflare        . Retrying at least 9 time(s).
`

An error 502 should be resolved with time, maybe try to uninstall and install again the integration. I have no other hint for the moment :/.

I'm also having these problems, the sensors don't appear, it recognizes the account but nothing from the sensors. I used the "Workaround" method to add the account.
I used the native Home Assistant sensor but as it no longer works I decided to switch to that one but it's not working for me either.

Hasn't loaded anything for me. Server has been restarted multiple times too.

Can you show me exactly what is your configuration and a screen of you dev tools typing trakt please ?

here is mine I have had no luck for about a month, no entities

Do you have logs ? What is your conf ?

Do you have logs ? What is your conf ?

default from git to make sure I was using the correct one, also tried creating a new set of key on trakt, turned on logging for it now and will let you know as soon as i have something

Can you show me exactly what is your configuration and a screen of you dev tools typing trakt please ?

So i guess i was looking in the wrong place.  I was looking at the integrations page expecting something to be populated with the sensors/devices etc...

Instead when you said look at the services page i found that it has created the sensors

So based on this my issue is fixed, although i dont know how long it took to generate this.  Might be worth updating the README around this because normally you add the integration and you configure it from there rather than having to review the states page.

Yes you have them congrats, I will work my best to make it more clear. Don't hesitate to make a pull request if you think the README need changes.


[it] removing old CODEOWNERS

Describe your changes
Related issue number or link (ex: resolves #issue-number)
Checklist before opening this PR (put x in the checkboxes)

[ ] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[ ] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@fsbaraglia
Is this PR to update dev-it with the main branch ?


Add Chebyshev type and change Ultrapsherical{m}(d)->Ultraspherical(m,d)

The following is slow
u=Fun(exp)
for k=1:100
Derivative()*u
end
because Derivative has to be recompiled for each Ultraspherical{m} space.  The templating was mostly to have special routines for Ultraspherical{0}===Chebyshev.  So I think adding a Chebyshev type and removing the templating is good

Now implemented.


Can you please Turn off version detection？

If turn off version detection，It's no need to update plugin, which still can be used.

You can disable version checking by config.yml check.update to false!
https://github.com/fuyutsuki/Texter/blob/fecd04e3910519360b3cea610e2f05406dffac59/resources/config.yml#L7

Thanks<(￣︶￣)>


10.1.2 Release Hash Incorrect

Describe the bug
The 10.1.2 release has the hash listed as 64860a83d53aca19001d0026e5daf7db05218942dcbbf1ef0b1638242a09b8f6
To Reproduce
Download the 10.1.2 release zip file, and the SHA-256 hash is ac96fbdde7f754e0eb9ed51db020e77208cdb12cf58c08657a2ab87cb2694940.
Expected behavior
I'd expect the hash in the release notes to match the hash of the zip file.
Screenshots
n/a
Attachments
n/a
Environment (please complete the following information):
n/a
Additional context
I downloaded this twice just to double check it wasn't a corrupt file on my end, and obtained the same hash twice.

Fixed.  Copied incorrect hash.  Thanks for pointing this out.


[WEB] Adding hiring banner to latest dox

Questions:

Do I need to add this to v11 and v10 dox too? v10 dox already has a warning alert about the Clarity version not being supported
Is the expectation that the view jobs redirects you to http://vmware.design/career.html? If not, let me know and I can update it.

Signed-off-by: Jeeyun Lim<EMAIL_ADDRESS>

Hi @jeeyun
Thanks for doing this! We don't want this in the documentation. The home page should be sufficient for now...

I think the VMware Design jobs page is good for now. But could we add the Sofia dev positions to that page?
Could you contact whoever manages that Careers page to get those added?

So we don't want it anywhere except on landing page? And yes, will contact the appropriate parties for adding the positions.

Yup, only on the landing page for now


[Feature Request] Please offer an entry to change the width of el-menu-collapse.

Existing Component
是
Component Name
el-menu
Description
I want the set the menu--collapse 36px width with expand/collapse transition. But now el-menu--collapse is fixed in 64px which means the width transition less than 64px wouldn't work.
Could you offer an entry to change the width of menu--collapse ?
Or other methods could solve my problem
Here is my CSS:
  // 让el-menu展开流畅的关键样式
  .el-menu:not(.el-menu--collapse) {
    width: 200px;
  }
  .el-menu {
    width: 36px;
   }

Duplicate of #7490


[Login page] Components wiggle down screen when an error is shown

~Attempt to log in via a local user with junk credentials, the error message is shown at the top and all components underneath wiggle down screen~ This requires more of a redesign of the whole page
This problem is made worse when there's a status message. For example log out (url is /auth/login?logged-out) and green status text is shown, on log in attempt this is removed which causes a wiggle... then the error message causes a re-wiggle.
In summary, log in screen needs de-wiggling.

#4740 resolves the wiggle on log in

@richard-cox 4740 doesn't look like the right issue - is there another issue for this? or a PR that fixes it?

@nwmac Sorry, have updated the comment, meant #4722. That solves the wiggle when there's an existing error message and user tries to log in.

Verified on v2.7-head 216bb7f
I tried a few different scenarios and if there's an existing message (error or otherwise) on the login screen, if another appears it simply replaces the existing one with no wiggling.


environment id support added

@in4s update utils to v1.0.1, please

@in4s update utils to v1.0.1, please

Do you mean updating this library locally on my PC or elsewhere?

@in4s update utils to v1.0.1, please

Do you mean updating this library locally on my PC or elsewhere? @sklmx if you mean changing this line: "qase/php-client-utils": "^1.0" I thought it is not necessary since it should use the latest patch version anyway.

This only works for a fresh install, you can still only update qase-phpunit which uses features from version 1.0.1. Also, the version in composer.lock is still fixed to 1.0.0.


No occurrence for Hemimysis anomala shown

The small maps in the paper show that Hemimysis anomala should have at least 2 occurrences (one near Antwerp and one near Ostend). Our map shows no occurrences of this species. When I go to CartoDB, I see only one record, with coordinates 49.29339 2.30738 which, according to google maps, is in France (near Beauvais).

This might be an error in the dataset. @pboets to check this out. Also, the small maps in the paper were not based on the cleaned data...

Then isn't it strange that the cleaned data results in a position in France?

There is indeed one occurrence left in the Query.  And there is a mistake in the data.
Coordinate should be 51.21846944,4.36027500 I think.
I'l ask Frederic to change this in NBN

There is something strange, the correct coordinates were to find  in the
verbatimCoordinates section. It's the only record where this happened, I
guess something during the import in Recorder.
There were more in France before, we might of missed this one...
On Fri, Jul 17, 2015 at 2:59 PM, Bart Aelterman<EMAIL_ADDRESS>wrote:

Then isn't it strange that the cleaned data results in a position in
France?
—
Reply to this email directly or view it on GitHub
https://github.com/LifeWatchINBO/alien-macroinv-website/issues/2#issuecomment-122267039
.

--
Belgian Biodiversity Platform
Dimitri Brosens
Biodiversity Research Liaison Officer
Research Institute for Nature and Forest
Kliniekstraat 25
1070 Brussels
ORCID: 0000-0002-0846-9116
www.inbo.be
www.biodiversity.be
www.beescommunity.be
WATCH OUR BELGIAN BIODIVERSITY PLATFORM MOVIES ON:
http://vimeo.com/114955090 (data publication activities)
http://vimeo.com/114955160 (science-policy activities)
http://vimeo.com/114955193 (our general mission)
http://www.biodiversity.be/

One record for this in source dataset. Should be resolved once we sync CartoDB with the cleaned data.

Looks good on http://trias-project.github.io/alien-macroinvertebrates/ closing issue


How to add a new board of FPGA device (alinx_ax7010)

I am trying to add a new FPGA device. Here is the question I encountered and as a handbook as well.
out.log
gang@ubuntu:~/CFU-Playground/proj/proj_zynq7010$ make bitstream USE_VIVADO=1 IGNORE_TIMING=1 TARGET=xilinx_zynq_xc7z010 > out.log
INFO:SoC:        __   _ __      _  __
INFO:SoC:       / /  (_) /____ | |/_/
INFO:SoC:      / /__/ / __/ -_)>  <
INFO:SoC:     /____/_/\__/\__/_/|_|
INFO:SoC:  Build your hardware, easily!
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Creating SoC... (2022-02-28 09:28:22)
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:FPGA device : xc7z010clg400-1.
INFO:SoC:System clock: 100.000MHz.
INFO:SoCBusHandler:Creating Bus Handler...
INFO:SoCBusHandler:32-bit wishbone Bus, 4.0GiB Address Space.
INFO:SoCBusHandler:Adding reserved Bus Regions...
INFO:SoCBusHandler:Bus Handler created.
INFO:SoCCSRHandler:Creating CSR Handler...
INFO:SoCCSRHandler:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
INFO:SoCCSRHandler:Adding reserved CSRs...
INFO:SoCCSRHandler:CSR Handler created.
[out.log](https://github.com/google/CFU-Playground/files/8155475/out.log)

INFO:SoCIRQHandler:Creating IRQ Handler...
INFO:SoCIRQHandler:IRQ Handler (up to 32 Locations).
INFO:SoCIRQHandler:Adding reserved IRQs...
INFO:SoCIRQHandler:IRQ Handler created.
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Initial SoC:
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:32-bit wishbone Bus, 4.0GiB Address Space.
INFO:SoC:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
INFO:SoC:IRQ Handler (up to 32 Locations).
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoCBusHandler:io0 Region added at Origin: 0x80000000, Size: 0x80000000, Mode: RW, Cached: False Linker: False.
INFO:SoC:CPU overriding rom mapping from 0x0 to 0x0.
INFO:SoC:CPU overriding sram mapping from 0x1000000 to 0x10000000.
INFO:SoC:CPU overriding main_ram mapping from 0x40000000 to 0x40000000.
INFO:SoCBusHandler:cpu_bus0 added as Bus Master.
INFO:SoCBusHandler:cpu_bus1 added as Bus Master.
INFO:SoCBusHandler:rom Region added at Origin: 0x00000000, Size: 0x00020000, Mode: R, Cached: True Linker: False.
INFO:SoCBusHandler:rom added as Bus Slave.
INFO:SoC:RAM rom added Origin: 0x00000000, Size: 0x00020000, Mode: R, Cached: True Linker: False.
INFO:SoCBusHandler:sram Region added at Origin: 0x10000000, Size: 0x00002000, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:sram added as Bus Slave.
INFO:SoC:RAM sram added Origin: 0x10000000, Size: 0x00002000, Mode: RW, Cached: True Linker: False.
INFO:SoCIRQHandler:uart IRQ allocated at Location 0.
INFO:SoCIRQHandler:timer0 IRQ allocated at Location 1.
INFO:S7PLL:Creating S7PLL, speedgrade -1.
INFO:S7PLL:Registering Single Ended ClkIn of 100.00MHz.
INFO:S7PLL:Creating ClkOut0 sys of 100.00MHz (+-10000.00ppm).
INFO:S7PLL:Config:
divclk_divide : 1
clkout0_freq  : 100.00MHz
clkout0_divide: 16
clkout0_phase : 0.00°
vco           : 1600.00MHz
clkfbout_mult : 16
INFO:SoCBusHandler:csr Region added at Origin: 0xf0000000, Size: 0x00010000, Mode: RW, Cached: False Linker: False.
INFO:SoCBusHandler:csr added as Bus Slave.
INFO:SoCCSRHandler:bridge added as CSR Master.
INFO:SoCBusHandler:Interconnect: InterconnectShared (2 <-> 3).
INFO:SoCCSRHandler:ctrl CSR allocated at Location 0.
INFO:SoCCSRHandler:identifier_mem CSR allocated at Location 1.
INFO:SoCCSRHandler:leds CSR allocated at Location 2.
INFO:SoCCSRHandler:timer0 CSR allocated at Location 3.
INFO:SoCCSRHandler:uart CSR allocated at Location 4.
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Finalized SoC:
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:32-bit wishbone Bus, 4.0GiB Address Space.
IO Regions: (1)
io0                 : Origin: 0x80000000, Size: 0x80000000, Mode: RW, Cached: False Linker: False
Bus Regions: (3)
rom                 : Origin: 0x00000000, Size: 0x00020000, Mode: R, Cached: True Linker: False
sram                : Origin: 0x10000000, Size: 0x00002000, Mode: RW, Cached: True Linker: False
csr                 : Origin: 0xf0000000, Size: 0x00010000, Mode: RW, Cached: False Linker: False
Bus Masters: (2)
- cpu_bus0
- cpu_bus1
Bus Slaves: (3)
- rom
- sram
- csr
INFO:SoC:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
CSR Locations: (5)
- ctrl           : 0
- identifier_mem : 1
- leds           : 2
- timer0         : 3
- uart           : 4
INFO:SoC:IRQ Handler (up to 32 Locations).
IRQ Locations: (2)
- uart   : 0
- timer0 : 1
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Initializing ROM rom with contents (Size: 0x5108).
INFO:SoC:Auto-Resizing ROM rom from 0x20000 to 0x5108.

ERROR: [DRC UCIO-1] Unconstrained Logical Port: 2 out of 7 logical ports have no user assigned specific location constraint (LOC). This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all pin locations. This design will fail to generate a bitstream unless all logical ports have a user specified site LOC constraint defined.  To allow bitstream creation with unspecified pin locations (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks UCIO-1].  NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run.  Problem ports: serial_rx, and serial_tx.
ERROR: [Vivado 12-1345] Error(s) found during DRC. Bitgen not run.
Traceback (most recent call last):
  File "./common_soc.py", line 57, in <module>
    main()
  File "./common_soc.py", line 53, in main
    workflow.run()
  File "/home/ggang/CFU-Playground/soc/board_specific_workflows/general.py", line 121, in run
    soc_builder = self.build_soc(soc)
  File "/home/ggang/CFU-Playground/soc/board_specific_workflows/general.py", line 98, in build_soc
    soc_builder.build(run=self.args.build, **kwargs)
  File "/home/ggang/CFU-Playground/third_party/python/litex/litex/soc/integration/builder.py", line 330, in build
    vns = self.soc.build(build_dir=self.gateware_dir, **kwargs)
  File "/home/ggang/CFU-Playground/third_party/python/litex/litex/soc/integration/soc.py", line 1139, in build
    return self.platform.build(self, *args, **kwargs)
  File "/home/ggang/CFU-Playground/third_party/python/litex/litex/build/xilinx/platform.py", line 55, in build
    return self.toolchain.build(self, *args, **kwargs)
  File "/home/ggang/CFU-Playground/third_party/python/litex/litex/build/xilinx/vivado.py", line 372, in build
    _run_script(script)
  File "/home/ggang/CFU-Playground/third_party/python/litex/litex/build/xilinx/vivado.py", line 101, in _run_script
    raise OSError("Error occured during Vivado's script execution.")
OSError: Error occured during Vivado's script execution.
make[1]: *** [/home/ggang/CFU-Playground/soc/common_soc.mk:115: build/xilinx_zynq_xc7z010.proj_zynq7010/gateware/xilinx_zynq_xc7z010.bit] Error 1
make: *** [../proj.mk:287: bitstream] Error 2

Hi @ggangliu , thanks for trying this!    I recently got a Digilent Arty Z7 board with a z7010 myself.
Did you add the board platform/target files for "xilinx_zynq_xc7z010" yourself?   Is that an eval board from Xilinx?   I don't see it in https://github.com/litex-hub/litex-boards/tree/master/litex_boards/platforms .

Hi @ggangliu , thanks for trying this! I recently got a Digilent Arty Z7 board with a z7010 myself.
Did you add the board platform/target files for "xilinx_zynq_xc7z010" yourself? Is that an eval board from Xilinx? I don't see it in https://github.com/litex-hub/litex-boards/tree/master/litex_boards/platforms .

Thanks for reply. Yes I have added the board platform/target files for it in local Repo. It is from Xilinx, I saw the device ID is the same with digilent_zybo_z7.py. So even I can program "digilent_zybo_z7.bit" file into my board. So I almost copy and modify my board based on digilent_zybo_z7 board.  I will submit after I build it successful at least.
Is there anywhere need to be changed also unless litex-boards? By the way, it seems that usb_uart is necessary to be added.  I cannot comment out " self.add_extension(_usb_uart_pmod_io)" line.

@ggangliu does the basic LiteX build work with your board files?   Either using the "PS" ARM cores, or using a soft CPU built on the FPGA fabric?

@ggangliu , the issue you have with the tty connection (serial_tx, serial_rx) is probably similar to what I see on my Arty Z7.   On my Arty, the USB cable connects to an FTDI chip that then connects to the PS, not to the PL (FPGA).
On other boards, with plain FPGAs,  there usually dedicated FPGA I/Os for serial_rx / serial_tx that connect to the FTDI chip and then USB.
One solution is to set up your own UART/USB conversion by buying a small board like this https://www.amazon.com/gp/product/B00IJXZQ7C/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 (there are MANY alternatives on Amazon / Alibaba / electronics supply places).    You will then need to pick the FPGA IOs to use, add them to your LiteX platform file, and then set up the serial port in the target file.   And of course wire the converter board to your Zynq board (just 3 wires are needed).

@tcal-x Really thanks. I already have a UART/USB conversion, I can try it soon. It is really glad to know this. Thanks again.

@ggangliu , the issue you have with the tty connection (serial_tx, serial_rx) is probably similar to what I see on my Arty Z7. On my Arty, the USB cable connects to an FTDI chip that then connects to the PS, not to the PL (FPGA).
On other boards, with plain FPGAs, there usually dedicated FPGA I/Os for serial_rx / serial_tx that connect to the FTDI chip and then USB. That's what LiteX is expecting, but in our case, those pins aren't declared in the FPGA platform file.
One solution is to set up your own UART/USB conversion by buying a small board like this https://www.amazon.com/gp/product/B00IJXZQ7C/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 (there are MANY alternatives on Amazon / Alibaba / electronics supply places). You will then need to pick the FPGA IOs to use, add them to your LiteX platform file, and then set up the serial port in the target file. And of course wire the converter board to your Zynq board (just 3 wires are needed). Zybo does something similar using its PMOD connector: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/platforms/digilent_zybo_z7.py#L69-L77

I have tested, it is really like what you said. I use FPGA pins as Serial ports, building is successfully. And LEDs is flashing.

I have tested, it is really like what you said. I use FPGA pins as Serial ports, building is successfully. And LEDs is flashing.

That's great!   Have you been able to connect over your new USB/serial to interact with the LiteX BIOS?

I have tested, it is really like what you said. I use FPGA pins as Serial ports, building is successfully. And LEDs is flashing.

That's great! Have you been able to connect over your new USB/serial to interact with the LiteX BIOS?

P.S. @ggangliu I have NOT tried this yet -- I've only gotten as far as you have -- getting the LED Chaser blinking.  See https://github.com/litex-hub/litex-boards/issues/358 .

I have tested, it is really like what you said. I use FPGA pins as Serial ports, building is successfully. And LEDs is flashing.

That's great! Have you been able to connect over your new USB/serial to interact with the LiteX BIOS?

P.S. @ggangliu I have NOT tried this yet -- I've only gotten as far as you have -- getting the LED Chaser blinking. See litex-hub/litex-boards#358 .

Yes, I have tried it, but it output some unreadable code, I guess that the baud rate (only tried 115200) was not matched with BIOS. I'm gotta to check the source of BIOS.

Hi @ggangliu , those are great findings.    I never would have thought to try 1/2 speed baud rate!   I hope I can find time to see what the status is with my build on Arty Z7.
To clarify the JTAG discussion --- I thought you were able to program PL before (to get the blinking LED).   Are you saying that you need to make a change to program the PL correctly?
Ah, the device value should probably be overridden in the board target file, not in the central xilinx/programmer.py file.   Here is how it works with the target file for Arty Z7:
prog.load_bitstream(os.path.join(builder.gateware_dir, soc.build_name + ".bit"), device=1)

https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/digilent_arty_z7.py#L131

Hi @ggangliu , those are great findings. I never would have thought to try 1/2 speed baud rate! I hope I can find time to see what the status is with my build on Arty Z7.
To clarify the JTAG discussion --- I thought you were able to program PL before (to get the blinking LED). Are you saying that you need to make a change to program the PL correctly?
Ah, the device value should probably be overridden in the board target file, not in the central xilinx/programmer.py file. Here is how it works with the target file for Arty Z7:
prog.load_bitstream(os.path.join(builder.gateware_dir, soc.build_name + ".bit"), device=1)

https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/digilent_arty_z7.py#L131

Really thanks @tcal-x. The first time success, I was using Vivado GUI to program, so I can select specific device. Last day I tried to use command line "make prog". Appreciate again.

Hi @tcal-x,
A new question,  I was running this command "make load TTY=/dev/ttyUSB0 TARGET=xilinx_zynq_xc7z010", it encountered below issue. Could you please give me any suggestion? Thanks.
  CXX schema_utils.cc	schema_utils.o
  CXX tflite.cc	tflite.o
  CXX tflite_unit_tests.cc	tflite_unit_tests.o
  AS  crt0-vexriscv.S	crt0-vexriscv.o
  LD       software.elf
/home/ggang/Downloads/riscv64-unknown-elf-gcc-10.1.0-2020.08.2-x86_64-linux-ubuntu14/bin/../lib/gcc/riscv64-unknown-elf/10.1.0/../../../../riscv64-unknown-elf/bin/ld:/home/ggang/CFU-Playground/proj/proj_zynq7010/build/ld/linker.ld:20: warning: memory region `main_ram' not declared
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:163: software.elf] Error 1
make[1]: Leaving directory '/home/ggang/CFU-Playground/proj/proj_zynq7010/build'
make: *** [../proj.mk:214: /home/ggang/CFU-Playground/proj/proj_zynq7010/build/software.bin] Error 2

What I have done

I have checked vexriscv core.py file, it looks no proplem

./third_party/python/litex/litex/soc/cores/cpu/vexriscv/core.py     def mem_map(self):
        return {
            "rom":            0x00000000,
            "sram":           0x10000000,
            "main_ram":       0x40000000,
            "csr":            0xf0000000,
            "vexriscv_debug": 0xf00f0000,
        }

regions.ld shows like below, it seems be generated automatically. And no "main_ram" section definition.

MEMORY {
        rom : ORIGIN = 0x00000000, LENGTH = 0x00020000
        sram : ORIGIN = 0x10000000, LENGTH = 0x00002000
        csr : ORIGIN = 0xf0000000, LENGTH = 0x00010000
}

linker.ld in build/ld folder like below, all sections are using "main_ram" as target area.

INCLUDE output_format.ld
ENTRY(_start)

__DYNAMIC = 0;

INCLUDE regions.ld

SECTIONS
{
        .text :
        {
                _ftext = .;
                *(.text.start)
                *(.text .stub .text.* .gnu.linkonce.t.*)
                _etext = .;
        } > main_ram

Hi @ggangliu , yes, that is a real issue.   I see the same thing with my Arty Z7 board -- no main_ram region.
But we can fix that by adding a new RAM!   We could either split the existing rom region -- but then I think we'd need to change the origin of the main_ram region to be 0x10000 (with the original rom using 0x00000 - 0x10000).   There's a precedent with what they have done with Fomu, which now splits the psram into two regions:  https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/kosagi_fomu.py#L93-L106
But, we could try adding a new region for main_ram made out of unused BRAMs.  You can add a RAM on the Wishbone bus using this:
self.add_ram("main_ram", 0x40000000, 0x10000)

I haven't tried this yet, but hopefully later today.

@ggangliu , I was able to add the new memory region, but I couldn't really test it since I couldn't get the tty / uart to work with the PMOD adapter.

putty and litex_term are able to connect via PMOD adapter with sudo command, but sometime it works on /dev/ttyUSB0, sometime it is /dev/ttyUSB1, it is not stable. And default baud rate is 1843200. Some UARTs tool don't support this baud rate.

@ggangliu , I was able to add the new memory region, but I couldn't really test it since I couldn't get the tty / uart to work with the PMOD adapter.

putty and litex_term are able to connect via PMOD adapter with sudo command, but sometime it works on /dev/ttyUSB0, sometime it is /dev/ttyUSB1, it is not stable. And default baud rate is 1843200. Some UARTs tool don't support this baud rate.

Hi @ggangliu , yes, that is a real issue. I see the same thing with my Arty Z7 board -- no main_ram region.
But we can fix that by adding a new RAM! We could either split the existing rom region -- but then I think we'd need to change the origin of the main_ram region to be 0x10000 (with the original rom using 0x00000 - 0x10000). There's a precedent with what they have done with Fomu, which now splits the psram into two regions: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/kosagi_fomu.py#L93-L106
But, we could try adding a new region for main_ram made out of unused BRAMs. You can add a RAM on the Wishbone bus using this:
self.add_ram("main_ram", 0x40000000, 0x10000)

I haven't tried this yet, but hopefully later today.

Thanks tcal-x, this method is able to add any custom section, it is very flexible.
Through analyzing source code, I found there is a simpler way to enable it that we only need to add parameter(integrated_main_ram_size = 0x4000) in board target file, like below code.
        # SoCCore ----------------------------------------------------------------------------------
        SoCCore.__init__(self, platform, sys_clk_freq,
            ident          = "LiteX SoC on ECP5 Evaluation Board",
            integrated_main_ram_size = 0x4000,
            **kwargs)

And also found a reference here. https://github.com/litex-hub/litex-boards/blob/08a79fa3ac68d1ddff0ba58432e86351efbbf100/litex_boards/targets/lattice_ecp5_vip.py#L104-L105

Hi @tcal-x ,  How can I execute "make load" with demo.bin? Right now I don't how to build demo.bin. I have to start with demo program because my board has no sufficient memory to store tensorflow image.

@ggangliu did you figure out how to use the DDR of the board as main_ram?


fix: make sha command working

There was missing shift in sha command.  Added.
I've also updated .github/actions to use $github.repository_owner repository  to make testbuild possible for MR authors.

Thank you for the contribution!


Building chromium for v3.0.*

Adding new built binaries for puppeteer 3.0.x releases

@fartbagxp did you add libgbm-dev dependency while compiling as authors stated in puppeteer 3.0.1 release:

The docs now include the libgbm-dev dependency that's needed for Linux builds (#5667, #5693)

Linked issues:

https://github.com/puppeteer/puppeteer/pull/5667
https://github.com/puppeteer/puppeteer/pull/5693

I'm asking because those issues are connected especially with lambda environment :)

As far as i tested (via lambda layer) it works fine :)

Hmm, @bestplay9384 - didn't notice that one.
I just ran https://github.com/alixaxel/chrome-aws-lambda/blob/master/_/ansible/plays/chromium.yml using ansible, should the Install Packages include libgbm-dev?
What else is missing - since chromium.yml hasn't been updated since Oct 2019?
I can try to rebuild it with everything else turned on.

It doesn't seem like libgbm1 is available, so I'll use libgbm1-dev and update the configurations before rebuilding. I noticed that the AMI in inventory.ini is running off of a 2019 version of Amazon Linux 2 but it's probably not an issue.
I'm adding the hashes of the new files, just in case anybody wanted to verify.

File
Type of Hash
Hash

chromium.br
md5
6e1eeb438f88880d41b70e8a33db29db

chromium.br
sha1
49c57d369423c27189aec03b4487fb5da75e198b

chromium.br
sha256
aaebb14231f2c80e5afd15586c1d94b6780f7ed1dcbe2b044c86592207e231d6

swiftshader.tar.br
md5
5570df5549a9faaebb3b2a3d4cbd4e84

swiftshader.tar.br
sha1
e44214200c893af265c24a2dabc738981813bcbf

swiftshader.tar.br
sha256
b42101c710e59a68d89e38b8006262f7ad0409793ae979214e5ea6ea35241d31

Thank you for this @fartbagxp! :bow:


Mana goes negative on queue

basically could be a few things:

[ ] the calculation for the time you'll have enough mana is off
[ ] the calculation for checking mana costs for queued items is off (unlikely cause <@259506763374526466> didn't use an item)
[ ] the calculation for subtracting the mana is off (subtracting too much)

I haven't seen this in a long time so I am going to close it


Latest version is throwing errors on web

While trying to upgrade from v2.1.1, I ran into a few issues.

v4.0.0 does not appear to have the dist files updated with the latest changes to memory limiting
The project development appears to have been deviated to 3 separate repos (Dador, JustAMan, jellyfin), where the jelyifin fork looking to be the latest. @jellyfin or @JustAMan Any chance we can look to merge your wonderful updates back to the original repo?
A simple web example is no longer working on the latest version. I've created a very simple test example webpage to showcase the player, as the original example in the readme no longer exists. However it seems that a simple web example is no longer working. More details here. Anyone else seeing the same thing?

Created a PR with the same simple web example against this original repo, but still does not appear to be working properly.
https://github.com/Dador/JavascriptSubtitlesOctopus/pull/71

@TFSThiagoBR98 Noticed that the original examples folder was removed in https://github.com/Dador/JavascriptSubtitlesOctopus/commit/37d81c3e19d777c545d090e49a05dd0a303c6849. Was this ever migrated somewhere else?

@nickfujita I was planning on making upstreaming PRs, but then real life happened... I still hope to do them, though. Meanwhile anyone is free to do that if they want to :)


Internal AppTP support

Task/Issue URL: https://app.asana.com/0/414235014887631/1204167883757917/f
Tech Design URL:
CC: @SlayterDev
Description:
See Asana task for context

Steps to test this PR:

See Asana task for testing steps, specifically this subtask

Copy Testing:

[ ] Use of correct apostrophes in new copy, ie ’ rather than '

Orientation Testing:

[ ] Portrait
[ ] Landscape

Device Testing:

[ ] iPhone SE (1st Gen)
[ ] iPhone 8
[ ] iPhone X
[ ] iPhone 14 Pro
[ ] iPad

OS Testing:

[ ] iOS 14
[ ] iOS 15
[ ] iOS 16

Theme Testing:

[ ] Light theme
[ ] Dark theme

Internal references:
Software Engineering Expectations
Technical Design Template

Also, I'm unable to test AppTp on device as app is not building in 14.3 due to the Kingfisher issue, and all my devices have been updated to 16.4.x.  I understand you were working on the KF updates?  Got a branch I could integrate temporarily to test functionality on device?

@afterxleep That's right, the Kingfisher change is still open here: https://github.com/duckduckgo/iOS/pull/1614
I'll be trying to get that merged in the next day or so, after which I'll pull develop back into this branch and you should be good to go. I'll ping you once that's ready. Thanks!

@afterxleep This should be good to go now. Let me know if you run into trouble building for your device in Xcode 14.3!


:no_entry: No longer need pyaml for deployments

This PR needs to be merged before #284 Note, it merges into branch feature/yarnify as opposed to master

:rocket: deployment of connecting-to-services-pr-285 in nhsuk-dev succeeded (http://connecting-to-services-pr-285.dev.beta.nhschoices.net)


ACI gets stuck in 'Pending' if multiple volume mounts with identical mounthPath are used

When creating an ACI and specifying multiple volumeMounts with the same mountPath, the service accepts the request and the ACI goes straight into 'Pending' forever. Not forever, because after about half an hour, it goes into something like 'backOff'. The REST service should validate this and return a BadRequest.
PowerShell to reproduce (you can use absolutely any docker image, the ACI will not reach 'Pulling' state):
Invoke-WebRequest `
    -UseBasicParsing `
    -Method PUT `
    -ContentType "application/json" `
    -Headers  @{
    Authorization = "Bearer $authToken"
} `
    -Uri "https://management.azure.com/subscriptions/$subscription/resourceGroups/$resourceGroup/providers/Microsoft.ContainerInstance/containerGroups/$containerGroupName?api-version=2018-10-01" `
    -Body (@{
        id         = "/subscriptions/$subscription/resourceGroups/$resourceGroup/providers/Microsoft.ContainerInstance/containerGroups/$containerGroupName"
        location   = "west europe"
        name       = "$containerGroupName"
        properties = @{
            osType                   = "Linux"
            containers               = @(
                @{
                    name       = "$containerName"
                    properties = @{
                        image        = "$ContainerRegistryServer/$ImageName"
                        resources    = @{
                            requests = @{
                                cpu        = 1
                                memoryInGB = 0.3
                            }
                        }
                        volumeMounts = @(
                                @{
                                    name      = "mount1"
                                    mountPath = "/mnt/"
                                    readOnly  = $true
                                },
                                @{
                                    name      = "mount2"
                                    mountPath = "/mnt/"
                                    readOnly  = $true
                                }
                            )
                    }
                }
            )
            volumes                  = @(
                @{
                    name   = "mount1"
                    secret = @{
                        parameters = "eAA=" # just the string 'x' as base64
                    }
                },
                @{
                    name   = "mount2"
                    secret = @{
                        parameters = "eAA=" # just the string 'x' as base64
                    }
                }
            )
            restartPolicy            = "Never"
            imageRegistryCredentials = @(
                @{
                    server   = $ContainerRegistryServer
                    username = $spCreds.username
                    password = $spCreds.password
                }
            )
        }
    } | ConvertTo-Json -Depth 99)

Thanks for reporting! ACK the issue. There is a validation missing from the REST api. We plan to get this fixed by Dec 7th.

Adding to this: If - by accident - you are setting a mount path that is not absolute, e.g. "mymount" instead of "/mymount" the deployment is pending for half an hour and then fails. It should be checked that mount path has to be absolute.


Fixes for swapped URLs to cloudinary adapters

URLs to ghost-storage-cloudinary and ```ghost-cloudinary-store```` were swapped

Thanks!


[WIP] Sub menu

This is my attempt at implementing Sub menus in the context menu for #68
Here's the list of things to do:

[x] Update gitignore to ignore IDEA files (Webstorm is my IDE of choice)
[x] Update package.json  to show the correct minimum version for node (node 16 wasn't working for me, and was getting a error. Upgrading to node 18 worked.
[x] Update the types
[x] Update the docs
[x] Add an example page

[x] Add some text for the example page

[ ] Implement the sub menu in the code

[x] Make a submenu appear on hover
[ ] Update the Click Outside logic to not hide the context menu when trying to click on the sub menu
[x] Make the submenu disappear when other menu items are being hovered over
[x] Add chevron to show that the submenu exist, and add styling for it

[ ] Refactor the code to be a better API

Let me know if you have any thoughts 😊

Thanks for finishing it ✨


feat(UI): Add config for refreshTickInSeconds

Closes https://github.com/shaka-project/shaka-player/issues/6376

@MarianoFacundoArch Please add your name and email to https://github.com/shaka-project/shaka-player/blob/main/AUTHORS and https://github.com/shaka-project/shaka-player/blob/main/CONTRIBUTORS. Thanks!

Hi! Thanks! It is done in two commits; please let me know when it is merged. I am willing to continue collaborating! :D
https://github.com/shaka-project/shaka-player/pull/6391
https://github.com/shaka-project/shaka-player/pull/6392

@avelad Name added to this PR as requested; how do we proceed and get it merged?
Thanks!

@avelad Name added to this PR as requested; how do we proceed and get it merged? Thanks!

We need a review from @joeyparrish or @theodab before merge it. Thanks!

When shall this be released? In which version?

If we don't do a new branch for v4.8, this would be out in v5.0, which we will be more cautious about.  There are other things we want to break this year, like moving to TypeScript, so it's possible that v5.0 will be delayed for a while.  If we create a v4.8.x branch without the breaking changes in it, your change would be in that branch and would be out sooner.

We will be releasing v4.8.0 soon.

Got it. Thank you @joeyparrish !


chore(package.json) Upgrade rollup to 0.56.3

Coverage remained the same at 100.0% when pulling 28081a1e25549beb24f6fa42b4c0c1812ec0804f on upgrade-rollup into d0005fa9f4b7e36f50683ff6259858ec7797b142 on master.

Coverage remained the same at 100.0% when pulling 28081a1e25549beb24f6fa42b4c0c1812ec0804f on upgrade-rollup into d0005fa9f4b7e36f50683ff6259858ec7797b142 on master.


Temp fix for unimplemented API calls

For those API calls that haven't been implemented yet, we could use a custom exception to highlight that a pull-request would be appreciated.
See @aaronpowell's gist for the PullRequestRequiredException idea:
https://gist.github.com/aaronpowell/2708280

FYI - It's on NuGet - https://www.nuget.org/packages/PullRequestRequiredException/

Cool, thanks @aaronpowell :+1: (450 package downloads, nice! :sunglasses:)


KAFKA-13917: Avoid calling lookupCoordinator() in tight loop

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mimaison would you please review this short change if you get some time?

@hachikuji would you please review this small PR?

Failed tests are unrelated:
    Build / JDK 11 and Scala 2.13 / org.apache.kafka.controller.QuorumControllerTest.testConfigurationOperations()
    Build / JDK 17 and Scala 2.13 / kafka.admin.TopicCommandIntegrationTest.testDescribeAtMinIsrPartitions(String).quorum=kraft
    Build / JDK 17 and Scala 2.13 / kafka.controller.ControllerIntegrationTest.testPartitionReassignmentToBrokerWithOfflineLogDir()

Do we need to backport this? Also cc @guozhangwang @dajac since this code has gone through a few iterations.

+1 to backport this change to 3.2. Let me know if necessary. Thanks.


Refactor: Linter test for only class-sided default values

Fixes #360

looks good, maybe we could even try to assert for constant values in those default values. This does not provide a way to find default values not named default*, but that could be quite hard tom implement.

Yep, I thought about that as well and was not sure how that would behave. Would a default value like 10 @ 10 be recognized as a constant? It would be bad if not. Additionally, look at defaultTextMorph for example. It returns a default morph which clearly is no constant. However, on could argue that this should not be classified as a default value.
To sum it up, I think looking for constants would maybe raise more problems than looking for default... already does.
But we could actually use looking for contants to detect methods that should be default methods. (Would be a different linter test then)


Short-circuit HList / Coproduct implicit recursion via a macro-backed type class

Closed https://github.com/milessabin/shapeless/pull/459 by mistake, reopening it here.

Still need some work.

We could have a look at it during the Scala eXchange hack day if you're around.

Is this redundant now?

It's not really redundant. It's something that short-circuits standard (recursive) derivation for case classes / ADTs, when using TypeClass.
I don't have much time for it right now, I think that can wait... (I can close and re-open it later if you'd like.)

I'll punt this to 2.3.1 ...

Do you think you'll have any time for this for 2.3.2?

I'd be willing to have a look at it, yes (some type class derivation slowness bite me quite hard very recently...). I'll update the PR in a few days.

Updated the PR.
I may try to make this mechanism more general in a second time (like https://github.com/milessabin/shapeless/pull/459 was at some point). So that it can handle default values or require extra auxiliary type class instances for each field / constructor - if you're fine with it.

I haven't tried to benchmark that in its current state (although there's no reason it doesn't make things better).

Note that it uses Console.err.println to explicitly report which field or constructor is making the derivation fail (which helps a great deal to debug derivations). c.error or c.warning are silenced here.

This seems to break the orphan tests, for reasons that are unclear to me... I don't much about their internals. Aren't they supposed to be deprecated somehow (by export-hook, or LowPriority here)? If that's the case, I'd rather wait for shapeless 2.4. I'm not sure there's a real problem in Derived here (and in any case, that can be more thoroughly tested in the mean time).

Am I dreaming, or has this PR (and some others) mysteriously come back from the dead?

I'm going to close this for now. I don't want to add new macros to shapeless at this point and I think that -Yinduction-heuristics is the better way forward.


Update samples.cc for comments on is_partitionable

With the recent release [1], a query without any Distributed Union is also considered partitionable. Modify the comment a bit to avoid inconsistency with the documentation.
[1] https://cloud.google.com/spanner/docs/release-notes#December_19_2023

This change is

/gcbrun


Add Info output when consumer is started

Right now we do nothing, so its difficult to know if the consumer has started or not. Would be nice to post a simple INFO log message when a consumer is started and connected.
Same when ending cleanly.

Fixed in https://github.com/signalwire/signalwire-ruby/commit/a38c3c0589e190e35a2ebdaccb76ce03b96d8844


Enhance performance of AbstractPatternJsonProvider

This PR addresses multiple performance issues of the AbstractJsonPatternParser.

PatternLayoutBase creates a new StringBuilder for every event it must serialize causing garbage and unnecessary pressure on the GC. This PR tries to reuse a StringBuilder per thread.
Filtering of empty fields is retrieving values multiple times from the event. This may become become expensive when the value is computed by a PatternLayout. This PR uses Jackson's FilteringJsonGenerator instead.
Make use of the most appropriate JsonGenerator#write() method instead of using writeObject() for "simple" value types. Using writeObject() delegates to the underlying ObjectCodec which is slower and produces lot more garbage.
Refactor the code to make it easier to read and understand.

Benchmarks show that these changes make the AbstractPatternJsonProvider 4 times faster than LLE 6.6 and more importantly, it does not produce garbage anymore.

Do the existing unit tests provide sufficient test coverage to ensure these changes did not change the generated JSON?

The seems to have good coverage already... Do you have additional scenarios in mind?

They seem to have good coverage already... Do you have additional scenarios in mind?

No.  I haven't looked at them.  I just wanted to confirm.  I trust your judgement.

I'm done with this PR.
@philsttr Are you ok with it?


Duplicate rows in input

Does not catch the error of getting input dataframe with duplicate gene/feature names till filter_features rule.

hm unsure if I want to implement an exception handling (e.g., removing duplicates) or just put it in the docs...


Rename node.js classroom page and update link to v3

Description of the change: Rename node.js classroom page and update link to v3
Reason for the change: Issue #2744
Link to original source:
@ksigler7

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @PyroclasticMayhem,
Thanks for the updates! We're not really looking for this type of change right now. However, if you're participating in Hacktoberfest, please check out our issues: https://github.com/sendgrid/docs/issues - We have a bunch of pretty easy changes in there that we are looking for.
Thanks!
SendGrid Docs team

@PyroclasticMayhem, please ignore my other comment, I mixed this up with another one, and I see now that this is based on one of our open issues.
Thanks so much for the update and sorry for the confusion!

Hello @PyroclasticMayhem,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


revert: Regen on new cluster"

This reverts #876

Do you have any suggestions on how to detect that a cluster is new in some other way?
/cc ankitm123 tomhobson


⚠ Bofrost.be has degraded performance

In cd58a21, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2494 ms

Resolved: Bofrost.be performance has improved in e4f7477.


Add SwiftGen for assets

This PR adds SwiftGen for assets and therefore lays the foundation for #30.
As there are currently multiple ways assets are used within the code, I didn't actually change the asset access mechanism yet – it's probably better if the core team does it.
To go on, I suggest a few things:

Also use SwiftGen for storyboards:

ib:
  inputs: .../Folder
  outputs:
    - templateName: scenes-swift4
      output: .../Resources/Generated/Storyboards.swift

Also use SwiftGen for localizations, combined with BartyCrouch, as shown in this project template.
Use a custom template for SwiftGen assets like this one. It would be best, if all image assets could be accessed using ~Images.folderName.folderName.imageName and all color assets using ~Colors.folderName.folderName.imageName

@fredpi Thank you very much for this PR. I just wanted to let you know that I am now looking into this PR which includes testing it locally and trying to figure out if there is anything else that needs to be done.
The only concern I have at the moment - without having looked at it - is that there are currently 13+ iOS developers working on this project + several developers from the open source community. If this changes the workflow significantly we may have to document that and make everyone aware about the changes. That being said I am now starting the review and I am pretty curious what I will find once I open the box. :)

@inf2381 I believe our CI is not being executed for PRs coming from other repos. It this done intentionally?

@fredpi I now had a look at the PR. I think that we have to also adjust the circleci config.yml file so that swiftgen is installed before actually building the app. We also have to consider our internal CI landscape. I will ask around if this might cause any issues and report back to you.

@ChristianKienle Would love to see SwiftGen in this project as well, prevents many bugs and errors!

@fredpi Why not build-script step that automatically runs SwiftGen on each build?

@Jeehut Do you mean a run-script phase in Xcode? I have added it, maybe you overlooked it ;)
Or do you mean something else?

Ahh, you're totally right of course, I overlooked it. Looks good, thank you! 👍

@fredpi I now had a look at the PR. I think that we have to also adjust the circleci config.yml file so that swiftgen is installed before actually building the app. We also have to consider our internal CI landscape. I will ask around if this might cause any issues and report back to you.
I have also assigned @inf2381 (aka Mr. CI) to make him aware about what is happening.

@ChristianKienle Thanks for the suggestion, but I think that would be rather counterproductive:
Every developer that adds news assets should build afterwards (automatically causing SwiftGen to update the Assets.swift file), then commit both the new assets and the updated Assets.swift file. The CI, in contrast, should not manipulate files before / while building.
Of course, this setup will yield a warning within the CI (that SwiftGen isn't installed), but I guess that won't be a problem with the current CI configuration that doesn't fail immediately on warnings.

@fredpi I now had a look at the PR. I think that we have to also adjust the circleci config.yml file so that swiftgen is installed before actually building the app. We also have to consider our internal CI landscape. I will ask around if this might cause any issues and report back to you.
I have also assigned @inf2381 (aka Mr. CI) to make him aware about what is happening.

@ChristianKienle Thanks for the suggestion, but I think that would be rather counterproductive:
Every developer that adds news assets should build afterwards (automatically causing SwiftGen to update the Assets.swift file), then commit both the new assets and the updated Assets.swift file. The CI, in contrast, should not manipulate files before / while building.
Of course, this setup will yield a warning within the CI (that SwiftGen isn't installed), but I guess that won't be a problem with the current CI configuration that doesn't fail immediately on warnings.

Gosh you are right. The CI does not need it. :D I really need more sleep lol.
Okay so then the CI is not a concern. Then this PR is fine with me.
So the plan is, if this gets merged to then actually start using Assets.swift in our code base - right?

@ChristianKienle Would love to see SwiftGen in this project as well, prevents many bugs and errors! Also I wonder why we are not using GitHub Actions for this regarding CI? @inf2381

We are using CircleCI because it was the first CI platform to have the Xcode beta version we needed back then...

@ChristianKienle Thank you for the fast review and responses. The Beta explanation makes sense! 👍 Looking forward for this getting merged. I think as a subsequent PR @fredpi might want to migrate at least the more trivial uses of dynamic strings to SwiftGen.
@ChristianKienle What is your opinion on also using BartyCrouch for fixing multiple potential issues with translations? After this is merged, @fredpi or I could continue with that as he has pointed out in his first post in this thread.

@ChristianKienle Thanks for the review! 👍
I've made some changes to this PR:

SwiftGen is now also used for Storyboards – rendering the custom AppStoryboard type useless. While adding SwiftGen for storyboards I found a lost storyboard file (Main.storyboard) that isn't used anymore, so I removed it.
A custom template is now used for the asset generation – allowing for faster access and enabling namespacing by default (resulting in code like Colors.SemanticColors.medium or Assets.EnSettings.iconsBluetooth). Also, all colors and images of a catalog can be accessed easily, e. g. using Colors.allColors.
I have added custom SwiftLint rules that enforce the use of SwiftGen. Currently, they are still commented out.

As from my side, this can be merged now.
The next step would be to migrate the existing use to SwiftGen (+ enable the new SwiftLint rules). This can be done step by step, starting with storyboards, then colors and finally images. The latter may be a bit more time-intensive because the namespace must be looked up for each image.
Also, SwiftGen & BartyCrouch work quite well together for localizations, so those could also be implemented as @Jeehut suggested.

@fredpi Thank you very much for the changes. I will review this PR again - shortly.
@Jeehut & @fredpi To be honest I have never used BartyCrouch. Before I can make any qualified comment I would have to look at it which I will do. Not sure if I will be able to check it out today though...

@ChristianKienle BartyCrouch works like magic without the need that anyone learns something new, it actually just fixes gaps in Xcode and makes things work as expected. For example, when you write NSLocalizedString("new_key", comment: "") in code, it will automatically add the key to the Localizable.strings files for all languages. Also, whenever any new labels or buttons are added or removed from Storyboard files, it automatically syncs the translations of those Storyboards to add/delete the keys. Once we configured it, you won't need to do anything specific, just install it on your machine and you're good to go.
But having that said, it should for sure be a separate PR because SwiftGen is already useful without BartyCrouch, so we can move the BartyCrouch discussion to it's own PR.
@fredpi Instead of SwifLint custom rules (which I don't like because they are not easy to test and also don't support autocorrection), could we use AnyLint which I have already basically configured in https://github.com/corona-warn-app/cwa-app-ios/pull/104?
I have also already prepared AnyLint checks for using SwiftGen in another projects, here they are:
    // MARK: DynamicColorReference
    try Lint.checkFileContents(
        checkInfo: "DynamicColorReference: Don't use dynamic color references – use SwiftGen & Color instead.",
        regex: #"UIColor\(\s*named:\s*\""#,
        matchingExamples: [#"UIColor(named: "primary")"#],
        nonMatchingExamples: ["Colors.primary.color"],
        includeFilters: [swiftFiles],
        excludeFilters: [generatedSwiftFiles]
    )

    // MARK: DynamicStoryboardReference
    try Lint.checkFileContents(
        checkInfo: "DynamicStoryboardReference: Don't use dynamic storyboard references – use SwiftGen & StoryboardScene instead.",
        regex: #"UIStoryboard\(\s*name:\s*\""#,
        matchingExamples: [#"UIStoryboard(name: "LoginViewController")"#],
        nonMatchingExamples: ["StoryboardScene.Login.loginViewController.instantiate()"],
        includeFilters: [swiftFiles],
        excludeFilters: [generatedSwiftFiles]
    )

    // MARK: DynamicStringReference
    try Lint.checkFileContents(
        checkInfo: "DynamicStringReference@warning: Don't use dynamic localization string references via code strings – use SwiftGen & L10n instead.",
        regex: #"NSLocalizedString\s*\("#,
        matchingExamples: [#"NSLocalizedString(@"Test", comment: "");"#, #"NSLocalizedString("Test", comment: nil)"#],
        includeFilters: [swiftFiles],
        excludeFilters: [generatedSwiftFiles]
    )

Hi guys,
Thanks for your discussion here. SwiftGen is not a new concept, as the idea is very similar to the Android R file. Is there some one who can tell me what's the benefit it can bring in to the project? If it's possible, personally, I prefer the following way to organize the assets:
 enum BluetoothState {
  case on
  case off
  private var imageName: String {
   switch self {
   case on: return "Illu_Bluetooth_Off"
   case off: return "Illu_Bluetooth_On"
   }
  }
  var image: UIImage { UIImage(named: imageName) }
 }

I think this is more logic.

@haosap SwiftGen is a generalized approach to fixing any resource loading problem which is by default done by manually referincing dynamic strings in iOS development. Unfortunately, the default method is very prone to errors like typos, referencing no longer available or renamed files. Because Xcode neither has a built-in check for the existence of the files and also doesn't provide autocompletion, errors are quite common, especially if the project is open source and many different people work on it.
In the end, yes, Android Studio for example has a similar concept built-in, and yes it's possible to set up a different solution like a custom one (that you suggested) or R.swift. But as SwiftGen is by far the most used solution here and many iOS developers know it, it's IMHO the best solution to tackle the problem of error-prone autocompletion-free nature of loading resources in iOS development without creating unnecessary obstacles for new contributors.

@ChristianKienle I have just rebased to fix conflicts. The tests pass so I think there's nothing holding back this PR from getting merged.
Just one last addition to this PR: I have added SwiftGen for strings. I didn't do it until now because I thought it would be better if it would be in a PR together with BartyCrouch, but for me it seems like the general expectation is that this PR already adds SwiftGen for strings. Unfortunately, the keys for the strings use an underscore pattern (main_screen_some_string) instead of a combination of points and underscores (~ main_screen.some_string) that would cause SwiftGen to better structure the strings (resulting in code like L10n.MainScreen.someString instead of L10n.mainScreenSomeString).
@Jeehut Yes, using AnyLint would be better, but maybe this PR should still implement SwiftLint rules and AnyLint migration should be discussed in #104.
@haosap Actually a pattern like Images.BluetoothState.on is possible with SwiftGen using namespacing (taking into account the group structure in the assets catalog Images.xcassets). However, as the asset catalogs are currently configured not to use namespacing themselves, the last name must be unique (Images.BluetoothState.bluetoothStateOn). That could be changed but one must be extremely cautious to properly update all the names referenced via storyboards – I wouldn't do it now that we don't have much time for it. Also, I'm wondering why there are multiple images assets catalogs; is this for performance reasons? I guess it would be easier to just have Images.xcassets and Colors.xcassets.

From @haosap:

Hi,
Could you please give me some example? What kind of MANY bugs will bring in this project besides Typo, without using the SwifGen?
Thanks.

@haosap Firstly, I don't know why you edited my comment instead of clicking "Quote reply". I assume you are searching for a thread-like answer method like in other tools like Slack, which will be coming to GitHub soom (I think this summer): https://help.github.com/en/github/building-a-strong-community/about-team-discussions
Apart from that, let me answer your question. Firstly, the way you ask your question seems to already include a logical issue: Your question implies that only one bug type ("Typo") can not leas to "many bugs", which is untrue. There can be thousand typos in the repo which would be thousand bugs but all of them consisting of one bug type.
Having that said, I will also quote myself because I already mentioned 3 bug types that are prevented by using SwiftGen:

Unfortunately, the default method is very prone to errors like typos, referencing no longer available or renamed files.

So not only typos are fixed, but also if one of the resources is removed (e.g. an image, a string or a color) then the project won't build anymore which makes clear that there's an issue. Without SwiftGen, it will continue to build, leaving to a user-error. Or if one of the resources was renamed (this usually happens in the last steps before a release where things are refactored to make things more consistent after a fast-progress period) then the same thing happens, SwiftGen again helps.
In practice, we have prevented around 2-3 bugs shipping per 2-week sprints to users in teams of 3 developers. Here, we are many more developers and of course someone could check that all resources are still available before making a release – or we just use SwiftGen.

@ChristianKienle I rebased to fix conflicts and to adapt to the new asset catalog structure.
In an additional commit, I renamed Assets.xcassets to Images.xcassets and ena-colors.xcassets to Colors.xcassets. If you're not okay with that change, I can withdraw it. But it enables code like Images.someImageInTheAssetsCatalog (instead of Assets.someImageInTheAssetsCatalog) and Colors.someColorInTheEnaColorCatalog (instead of EnaColors.someImageInTheAssetsCatalog). Such an effect may also be achieved by modifying the SwiftGen-xcassets.stencil - just let me know what to do.

@ChristianKienle As my asset catalog renaming caused a bunch of conflicts, I now switched to the different approach (modifying the SwiftGen template), that only renames the asset catalogs in the Assets.swift file.
Also, as rebasing got trickier every time, I squashed the previous changes into one commit.


SBOM workflow using "npm sbom"

Which problem is this PR solving?
This replaces https://github.com/open-telemetry/opentelemetry-js/pull/4479
This workflow is using the npm sbom command to generate multiple SBOM files: one for each package and one for the whole repository (opentelemetry-js.spdx). All files are combined in a single zip file. The workflow is triggered when a release is published.
NOTE: The npm sbom command makes it possible to exclude dev dependencies (--omit dev configuration). However, there seems to be a bug where sometimes dependencies are not captured (see https://github.com/npm/cli/issues/7204 for more details). Once the npm issue is resolved, the --omit dev configuration should be added to the commands in this workflow).
An example output from this workflow is available here.

@martinkuba I guess you don't need final review until this is adjusted somehow to add this asset to the relevant GitHub Release?

@trentm @pichlermarc Trent is correct that we would need an extra step in the workflow to add the artifact to a release. This brings up a question whether it should be attached to the API and experimental releases as well. And if yes, should we have different workflows for the core SDK, the API, and experimental packages? I think the answer is probably yes, and I can split this into three different workflows (or conditional steps). What do you think?

Is it misleading that it references an<EMAIL_ADDRESS>package? There actually is (perhaps by accident?) such a package published to npm: npmjs.com/package/opentelemetry?activeTab=versions (That package is not malicious, BTW. It just contains a small package.json and useless one-line "index.js".)

I tried with "private": true and did not make a difference. The version 0.1.0 is in the top-level package.json, so it is technically correct. Per the documentation of the field, the important part is that the value is unique for each file, which it is since it gets a unique UUID appended. In any case, the npm sbom does not have a way to customize it.

I have made the following updates

added .json file extension to the generated SBOM files
removed the SBOM file for the whole repository
SBOM files are generated conditionally for core packages, experimental packages, or API based on the release tag
the SBOM zip file is added to the release automatically as an artifact


Codecov Integration (#22)

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@6540027). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #23   +/-   ##
==========================================
  Coverage           ?   87.59%
==========================================
  Files              ?        4
  Lines              ?      411
  Branches           ?        0
==========================================
  Hits               ?      360
  Misses             ?       51
  Partials           ?        0

Continue to review full report at Codecov.

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


Incorrect is-a relation: purine nucleobase biosynthetic process is-a pigment biosynthetic process

GO:0009113 purine nucleobase biosynthetic process
is-a
GO:0046148 pigment biosynthetic process
The above is-a relation might be incorrect as purine compounds cannot be classed as true pigments.

Thanks for pointing this out.


use Fast Downward version 0.3.1

The new up-fast-downward version uses the Fast Downward 23.06 release.

Codecov Report
Patch and project coverage have no change.

Comparison is base (6caa639) 85.03% compared to head (802d1f2) 85.03%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #491   +/-   ##
=======================================
  Coverage   85.03%   85.03%
=======================================
  Files         198      198
  Lines       26053    26053
=======================================
  Hits        22153    22153
  Misses       3900     3900

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


[c++] Fix typos in unit-test case and impl

CI fail introduced on #2884.
std::strcmp returns 0 on match so the intended use is !std::strcmp("foo", "foo") to get a truthy value.

This is passing in my sandbox & failing here so once again I'm squinting at caching ... 👀 🤔

There is some memory corruption going on -- prints reveal metadata value "soma" is reading back as "soma+239" or somesuch ... problem does not repro in Mac sandbox; does repro in Ubuntu sandbox; debugging ...

There was an incorrect use of the core get_metadata API which sometimes passed CI, but only by accident. Fixed in https://github.com/single-cell-data/TileDB-SOMA/pull/2888/commits/1f01f6ec97745d50045da15a47007ee67d9333f4.


Manage labels with .github/settings.yml

🚀 Feature Request
Is your feature request related to a problem? Please describe.

A .github/settings.yml file to manage project labels :D

Describe the solution you'd like

Something like this

$ dig WWW.EXAMPLE.COM http://WWW.EXAMPLE.COM +nostats +nocomments +nocmd
> ;WWW.EXAMPLE.COM http://WWW.EXAMPLE.COM.                     IN      A
> WWW.EXAMPLE.COM http://WWW.EXAMPLE.COM.              3592
IN      CNAME   YOUR-USERNAME.github.io.
> YOUR-USERNAME.github.io.      43192   IN      CNAME   *
GITHUB-PAGES-SERVER *.
> * GITHUB-PAGES-SERVER *.         22      IN      A       <IP_ADDRESS>
Em qua., 14 de abr. de 2021 11:11 AM, Jose Gracia Berenguer <
@.***> escreveu:

🚀 Feature Request Is your feature request related to a problem?
Please describe.

A .github/settings.yml file to manage project labels :D

Describe the solution you'd like

Something like this
https://github.com/npm/create-oss/blob/master/.github/settings.yml

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Josee9988/project-template/issues/17, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARKDXS44NLFDNWXFCMU7U23TIWPBNANCNFSM425PK4GQ
.

@Leeeooo19888 hey, could you please stop commenting and creating nonsense posts and comments?


Provide a method to disable syncer which takes checkpoints

Syncer takes checkpoints of LCFS frequently to keep LCFS crash consistent.  This may trigger I/Os and loss of access to LCFS for short intervals.  If somebody does not want LCFS to be crash consistent, they may disable syncer completely.

this can be done by doing the following:
lcfsctl /lcfs syncer 0


Document the composing text feature

The composing feature of Flutter's text editing doesn't seem to be explained anywhere in the docs.  The docs linked above simply state:
The range of text that is still being composed.

What this feature does is to support the IME feature that allows replacing the text currently being edited with some replacement.  This is used, for example, by non-phonetic writing systems:

And even by Gboard to do suggestions (note the underline in the field and suggestions in the keyboard):

We should explain this in the docs!

I'll extract it from https://github.com/flutter/flutter/pull/80910/files

@LongCatIsLooong Yes perfect if that was in TextEditingValue.composing!  I forgot you had added that.

@justinmc @LongCatIsLooong was this ever added to the docs? I don't see any PR reference or doc reference in this thread. Instead, it looks like the issue was automatically closed.
As for the linked Dart doc, I think that quite a bit more elaboration would be useful. The description in the Dart doc only refers to a few specific non-arabic languages as an example of using a composing region. However, if I interact with the IME in English, I get all sorts of deltas sent back to me that make changes to the composing region. There appears to be a much broader set of use-cases for a composing region than what is alluded to in that Dart doc.

The docs went from one sentence to the several paragraphs that you see there now.  If there's more that we can add to make it more useful I definitely want to do that though.
Are you using Gboard on Android when you see composing changes in English?  It does that for suggestions, which is briefly mentioned in the docs.
What kind of details are you looking for?  Maybe I could add an example of typing English and another example of typing Chinese when composing is used and give the composing ranges over time.

I'm using the standard OS keyboard (as far as I know). I've mostly run in an emulator, so I dunno if that keyboard might be replaced with a Gboard by default?
I think the confusion around a composing region speaks to the need for an overall document that helps describe the various relationships in IME communication.
For example, there are various references to "committing" the composing region. Is a "commit" something that happens between Flutter and the OS? or is that something that happens in the OS even without Flutter? Or are there 2 stages of commits? And what does it mean to commit it? The answer to this question probably has a related impact on IME content and IME selection. Also, understanding this communication goes beyond what a composing region is, and into the relationship between the concept of a composing region and how Flutter coordinates with the OS.
Given that Flutter has designed its own IME API that re-routes OS signals in a particular way, it would be good for Flutter to thoroughly explain its IME API. In other words, a developer can't build an understanding of Flutter's IME abstraction by studying Android or iOS, because Flutter merged Android and iOS capabilities into one, and possibly reworked names and relationships along the way. This difficulty will only increase as various desktop IME considerations come in. I think Flutter should thoroughly describe how a developer is expected to utilize and interact with Flutter's IME APIs.
This may be of tangential interest to @sfshaza2 and @InMatrix


Status

Enhanced the mayaserver status with hardstuff details

The code has built successfully in my machine

The errors in 451 and 452 are solved in my case by commiting code two or more times

I got the real stuff port and up but...Can't able to slice port number from struct

The above screen shot is the output with real stuff


Fix links

1. [L0710] http://s10.postimg.org/yxy033a6h/Project_Ran_Main_Background.png Failed to open TCP connection to s10.postimg.org:80 (getaddrinfo: nodename nor servname provided, or not known)
2. [L1194] 404 http://thomasokken.com/free42/download/free42.tgz
3. [L1695] 301 http://images.contentful.com/emmiduwd41v7/1TmcZsJy7Si4qCYm24aAse/158d511e7e58461d64cf902fb5a26d32/santa-app-final.png  → https://images.ctfassets.net/emmiduwd41v7/1TmcZsJy7Si4qCYm24aAse/158d511e7e58461d64cf902fb5a26d32/santa-app-final.png

@dkhamsing  I don't know what is wrong with the URLs below, because I can open them in a browser and the ones work fine. As well as in a local running of awesome_bot.
1. [L0286] 404 https://camo.githubusercontent.com/9c5aa602321121d160837fbe8c0af605196810b4/687474703a2f2f73382e706f7374696d672e6f72672f346c377575746f30352f4f72626974375f47616d652e676966
2. [L0710] 404 https://camo.githubusercontent.com/7ebcddf23366d36c0283af08a7032fc0f1cf5a6f/687474703a2f2f7331302e706f7374696d672e6f72672f7978793033336136682f50726f6a6563745f52616e5f4d61696e5f4261636b67726f756e642e706e67

Thx!
Sent with GitHawk


Details about lane post processor

I was looking at the code in cc_lane_post_processor.cc and I was trying to figure out if and how apollo projects pixels into 3d world coordinates. I found the CCLanePostProcessor::ProcessWithoutCC function. At around line 571 a variable value is set to the value of the pixel. I don't understand what the value of this variable represents. I thought lane_map is like a binary map, 0 means no lane, 1 means lane, but the variable value takes different values. Can anyone explain the values in lane_map?
Edit: Some more questions. I managed to do what I originally wanted, that is to project lane lines to world coordinates and see them from top down. I just took the code from the function I mentioned above. Now I want to understand how this transformation from camera pixel to world coordinate works. I found that the following 3 lines do the magic. Can anyone explain me what each of them do?
Eigen::Matrix<double, 3, 1> img_point(        x * roi_width / lane_map.cols,        y * roi_height / lane_map.rows + roi_start, 1.0);
Eigen::Matrix<double, 3, 1> xy_p = trans_mat_ * img_point; (trans_mat_ comes from camera extrinsic parameters, i understand this line is where the actual projection is done)
xy_point << xy_p(0) / xy_p(2), xy_p(1) / xy_p(2);
xy_point has the final coordinates

I am closing it since there is no further question after last answer.


Add autofixer for order rule

I really want this feature :-)
see #711

Coverage increased (+0.05%) to 96.02% when pulling 31def147baacb9c8170424097828c1df6f87a9e2 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage decreased (-0.006%) to 95.959% when pulling c25bdcba6bba1292066f5925224b89d3c52befc1 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage decreased (-0.006%) to 95.959% when pulling c25bdcba6bba1292066f5925224b89d3c52befc1 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage decreased (-0.006%) to 95.959% when pulling c25bdcba6bba1292066f5925224b89d3c52befc1 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage decreased (-0.006%) to 95.959% when pulling c25bdcba6bba1292066f5925224b89d3c52befc1 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage increased (+0.2%) to 96.131% when pulling 2209e83fffb84586fd02bcb742a1a173c14bc91a on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage increased (+0.2%) to 96.131% when pulling 2209e83fffb84586fd02bcb742a1a173c14bc91a on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage increased (+0.2%) to 96.131% when pulling 2209e83fffb84586fd02bcb742a1a173c14bc91a on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Hi, i dont have ideas how to fix appveyor build. Could you give me some a hint?
Another point: travis builds seems to unstable. Here is failed build and after fix coverage success build

@ljharb, currently autofixer just fix errors reported by original rule. Code
var async = require('async');
var a = 1;
var fs = require('fs');

transforms to
var fs = require('fs');
var async = require('async');
var a = 1;

due to rule requires 'fs' to occurs before 'async'.
In my opinion fixer should fix errors reported by rule.
Should i modify rule to avoid this behavior?

What about:
var b = require('b');
require('a')(b);

?
In other words, I think this rule is only safely fixable in a subset of the circumstances that the rule warns on - eslint core's policy (which I think everyone should follow) is that autofixes must always be "safe", and not change the meaning of the code, even if that means not autofixing some things.

:see_no_evil: Currently autofixer brokes the code above. Im going to update autofixer to avoid unsafe fixes.

Specifically: I think that to start, autofixing can only be said to be safe only within a chunk of requires and/or imports, where the requires are purely assignments - and any code that's not a variable-assigned-require or an import-with-a-binding has to be considered a boundary across which autofixing can't cross.
For example, side-effecting requires/imports (like just import 'foo'; or require('foo');, eg polyfills/shims/etc), are likely in place intentionally, which means that every require/import that happens before it must remain before it, and everything after it must remain after it.

Hi. Currently reorder fixes is very safe and only strict var-assignement-require and imports can be reordered and autofixes would not applied to the following code
var foo = require('./foo').bar.bar.bar;
var fs = require('fs');

Im not sure about this. Maybe such reorderings should be allowed

Coverage increased (+0.2%) to 96.117% when pulling 316d818cfe733b3be49e86fd22b426f039ff9ca6 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage increased (+0.2%) to 96.118% when pulling 82a66c4f47aa781aa5db53d781327180bfd47b17 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

Coverage increased (+0.2%) to 96.118% when pulling 82a66c4f47aa781aa5db53d781327180bfd47b17 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

@tihonove using fs would make it safe; but if you imported something with side effects it wouldn't be :-/

Ok, are there anything i can do to complete pr?

Coverage increased (+0.2%) to 96.145% when pulling 9af8223dbc0264ba1970faeea762c80733825bb8 on tihonove:master into dd281306089ba15394aeb2b85241509286442e34 on benmosher:master.

We'll need to get the tests passing before it can be merged tho.

I dont have ideas how to fix appveyor build. Could you give me a hint? Seems it fails after all test successfully passed

I believe the appveyor build might be broken on master; @benmosher, can you confirm?

Would be great to see this merged..

@benmosher any chance of merging and releasing this?

Sync and rebase pr

@tihonove after your rebase there is one test failure..

ah I see. :(

@tihonove - master build is now passing again
@benmosher - any chance you can take a look at merging this?

Coverage increased (+0.1%) to 96.18% when pulling 09703d0b3d2351b9b6889c7dd1fa68d10776497c on tihonove:master into 98acd6afd04dcb6920b81330114e146dc8532ea4 on benmosher:master.

It sure would be great to have this merged 🙏

@benmosher anything we can do to make this review easy? It could be really nice to get this in a  release :)

will merge once linux builds pass 👍

macOS build seems to be struggling. Are those really necessary btw (as this lib doesn't involve any "macos" specific code?)

@MoOx I agree that it shouldn't matter but the tests are there for the times when it mysteriously does. 😅 LGTM now, though 👍

See #1086 - this PR caused a performance regression. It’d be great if anyone interested in keeping this autofixer in the plugin could look into that issue.

You're my hero, @tihonove!  I just needed to apply an import/order rule to 395 files; this saved me a full day of hair pulling.


Fix publishing to fifo sns->sqs subscription

This closes #4737

Accidentally left an unused import in there. Removed in b309487ed484970c01c2a6c355ddf8da22ca2274 and will need approval again

Looks like some other tests are still failing with these changes

Should be good now :pray:

Codecov Report

Merging #4738 (6b53179) into master (ee6b2bf) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4738   +/-   ##
=======================================
  Coverage   95.32%   95.32%
=======================================
  Files         563      563
  Lines       60944    60953    +9
=======================================
+ Hits        58092    58101    +9
  Misses       2852     2852

Flag
Coverage Δ

servertests
47.45% <63.63%> (+<0.01%)
:arrow_up:

test_responses
32.06% <27.27%> (-0.01%)
:arrow_down:

unittests
95.23% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/sns/models.py
96.66% <100.00%> (+0.05%)
:arrow_up:

moto/sns/responses.py
98.03% <100.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Model names are plural, leads to error

Laravel Version: 5.3.26
Voyager Version: 0.10.0
PHP Version:
Database Driver & Version:

Description:
When creating a database table, the 'create model' button will create a model using plural (e.g. App\Videos). When one then uses the bread feature, it pre-fills the 'Model Name' with singular version (e.g App\Video). This results in an error. It can be solved by going into your code and change the model to the singular version manually.
Better would be that the 'create model' is immediately creating a singular version model (e.g. App\video)

The problem is only with the database table being incorrect right?
Cause in this case I'm gonna make the system add the ´table´ property to the model to ensure that the correct table is being used.

Well, not really.
If your table name is videos, I would assume the model is App\Video and not App\Videos. Just to be consistent with a table users and a model App\User. While the table is often plural, the model is often singular.
In the current version of Voyager, when the table name is videos, a model App\Videos is created (instead of App\Video). The problem is then that in the bread function the App\Video is proposed to the user. This leads to an error obviously.
So not really a bug, but I think it should be changed for consistency with the rest of Laravel. The only thing that needs to happen is that the model should be singular.

Okay. I will soon come up with a fix for this and let you know.

Just to add to this issue, since the one I've opened was mark as duplicated. What I was experiencing what not a pluralization issue, but a casing issue. With composite words, the model creation uses snake case, while everywhere else uses camel case.

What was the table-name you created @vpakg?

Hey @marktopper , the table created was uploaded_files. It generated a model named Uploaded_files but the auto-filled information shows by default App\UploadedFile.
For a more detailed explanation, please view #386
Thanks!

Just been looking into this as I've encountered this as well.
I noticed on this line that you're taking the name straight from the form the user submits. If people use a plural e.g. teams/products, the model created is Teams/Products respectively, when it's the singular we need.
Laravel has a helper function for str_singluar and str_plural, all depends on how you want to approach this.

This has been resolved by #579.  Closing


Is it possible to use Arel without ActiveRecord?

I'd like to write a rack app that uses arel and is backed by a mysql database. Is it possible to do this without using activerecord? I noticed you can set the Arel::Table.engine, but I wasn't sure what to set this to.

To something that implements the Active Record API that Arel needs. Also, please don't ask questions in the issue tracker. Use the Rails Core mailing list

Ok, thanks.


GITLAB - Fix terraform.ApplyUsersTerraform(globalFlags.DryRun, directory)

This function doesn't work for gitlab user setup. We need to add the parameters to make it work on gitlab.
Atlantis is the key: https://github.com/kubefirst/gitops-template/blob/main/terraform/vault/secrets.tf#L35

Relates to this not be fixed: https://github.com/kubefirst/kubefirst/issues/514

Not relevant anymore.


Integrate with Angular 6

I am currently using electron-forge with my angular 6 project. I'm stuck at
Preparing to Package Application for arch: x64
Can you please tell me how do i integrate this with angular 6?

This project is specifically for React and many changes will need to be made in order for it to work with Angular. Please have a look at the tutorial in Medium as linked in the Readme file. The philosophy should be the same and by changing the Babel setting while including the correct Angular rather than React modules you should have it working.


Unable to re-authenticate into Azure Storage Explorer

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.23.0
Regression From
1.23.0
Architecture
x64
Storage Explorer Build Number
20220223.14
Platform
Windows
OS Version
Windows 10
Bug Description
I am not able to re-authenticate into Azure Storage Explorer.
Error Message:
{
"message": ""{\n  \"message\": \"\\\"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-10-28T05:01:37.4148697Z and was inactive for 90.00:00:00.\\\\r\\\\nTrace ID: 466f5fea-a54c-4ee4-a522-8cf7aa361700\\\\r\\\\nCorrelation ID: abed3f7c-c7f7-45c8-a34c-3a3f1f7b77e2\\\\r\\\\nTimestamp: 2022-03-14 10:15:22Z\\\"\"\n}""
}
Steps to Reproduce

Launch Storage Explorer
Re-authenticate

Actual Experience
{
"message": ""{\n  \"message\": \"\\\"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-10-28T05:01:37.4148697Z and was inactive for 90.00:00:00.\\\\r\\\\nTrace ID: 466f5fea-a54c-4ee4-a522-8cf7aa361700\\\\r\\\\nCorrelation ID: abed3f7c-c7f7-45c8-a34c-3a3f1f7b77e2\\\\r\\\\nTimestamp: 2022-03-14 10:15:22Z\\\"\"\n}""
}
Expected Experience
No response
Additional Context
No response

@kean365 typically this just means you need to reauthenticate. Have you tried that?

Yes I tried, I am getting the same error.
Thanks-
Kiran
On Mon, Mar 14, 2022 at 10:48 PM Matthew Rayermann @.***>
wrote:

@kean365 https://github.com/kean365 typically this just means you need
to reauthenticate. Have you tried that?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/5524#issuecomment-1067084027,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4YRXKPOO4RACX4FBCBFATU75YFJANCNFSM5QVCDALQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Regards,
Kiran

Can you try:

Go to Help > Reset
Select only "Authentication"
Click "Reset"
Restart Storage Explorer
Sign in again

Closing due to lack of response. If you are continuing to run into this problem, we recommend opening an Azure support ticket. You can also open a new issue here.