Any plans to add support for tenants?

want a pull request?

I'm looking at using this module and also need tenant support. @erichexter do you already have something written? I didn't see a fork.

I extended some existing code using the octo client. But will need the
tenant support eventually.

@erichexter  I need to add tenant support as well. For us the primary purpose will be to bulk add tenants and tags. What functionality are you looking for? Perhaps we can work on this together to get everything we need. I haven't really used this module before so I'm just starting to look over it so I can follow the existing patterns.

@Dalmirog I'd like to take a whack at adding tenant features to the module. Would that be ok with you? I was looking through the pester tests. Can you give me some advice on how you have your test environment configured to make these work? Are you using the octopus azure image? Would be cool to get the entire test environment wrapped in an ARM template.

@mud5150  I basically want to create tenants and add them to a project/environement as part of our onboarding process. While we dont have a usecase for tags yet. I see us using it in the near future.

@erichexter Sounds good. I forked it to my account so feel free to keep an eye on it. Looking through the module now. Hopefully I'll have something to show tomorrow.

Hi @erichexter . I've added support for this in 0.6.0. Please reach out in the Gitter channel if you have questions about the usage and I'll jump in to give you a hand.

great, thanks for the follow up.


Devp/v1.0.0

Basic but functional gem push action. This is just the action ported over from the github-scanner test setup. A base to start building on.
See fac/dev-platform#62

No gem push run: https://github.com/fac/github-scanner/actions/runs/748558038
New gem version run: https://github.com/fac/github-scanner/actions/runs/748617904

✅
I still think two things though:

The repo/action name and action should be changed, rubygems makes me think it's for rubygems.org. I think it should be ruby-gem-push-action
The repo/action should spell out github-package-repository everywhere.

i.e. here rubygems-push-action -> ruby-gem-push-action
Up to you if you want to change it.

I tried to cover this yesterday with this thread: https://freeagent.slack.com/archives/C011DUEFZV1/p1618411388042400 where I suggested the same things and got ignored! Also said in standup that would follow up with a renaming round.


Documentation: Drop section on adding RHEL compute nodes

https://docs.okd.io/latest/machine_management/adding-rhel-compute.html
OKD latest does not support RHEL compute nodes. Maybe in the future, Fedora compute nodes could be supported, but I don't think that's on the roadmap at the moment. We should probably just remove this section of the docs.

There is no "support" in OKD, but these playbooks could be used to add CentOS / Fedora nodes to the cluster.
I think the section should stay, but in OKD version "RHEL" needs to be replaced with "CentOS/Fedora".
However these require OpenShift repos to install kubelet / crio etc. and these are not available - so its probably easier to drop this section then mislead the users

Hi, just to double check, with OKD, currently it is not possible to add CentOS nodes as compute nodes to an OKD cluster, is it? Or is it just a documentation issue?
Which repos would be needed to add to CentOS so the ansible script could work?

Its possible, but not trivial. We don't publish kubelet and crio repos - these should be provided by CentOS PaaS team. Once you have them you'd use openshift-ansible master / release-4.4 branch playbooks

similarly https://docs.okd.io/latest/updating/updating-cluster-rhel-compute.html would also be affected


Distributed: delta-sync doesn't take in consideration schema/clusters changes

Right now if any change happen to clusters/schema, they are not realigned to the node that ask for a delta-sync.

My idea is to:

after the delta-sync, ask for metadata like 1) database structure, 2) schema records, 3) indexes and 4) sequences
parse database structure, and foreach new cluster, create it. For each dropped cluster, drop it
overwrite the schema locally

For 2.2 I'd prefer to avoid supporting this because after a deeper analysis, it requires more time to develop and test it properly. So in v2.2 if any cluster or indexes has been added or removed, the delta-synch falls back on full replica. It's already in develop branch. I'm going to leave this open to be developed in v3.0

I am not confused, just a little disappointed this can't make 2.2. LOL! :smile:
Scott

I know, me too :-)

Closed long time ago.

Do your changes mean this issue will be resolved in 3.0 now?
Scott


QuickPick no longer sets activeItems to an empty array when no items are visible

At some point the QuickPick has stopped clearing the activeItems when you type a value that doesn't have any matches (and no items are set to alwaysShow). In GitLens we've used that behavior to offer additional behavior or options (e.g. via an added alwaysShow item), but now that is no longer possible.
Even worse though, is that if the user types a filter that matches 0 items and then presses Enter or OK, then it will behave like they accepted an item that is not visible -- which is certainly not their intent.
Here is a repo to reproduce the issue: https://github.com/eamodio/vscode-simple/tree/bug/quickpick-activeitems
/cc @TylerLeonhardt

/duplicate https://github.com/microsoft/vscode/issues/209074

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Lightspeed receiver failing when no device is connected

ratbag raw: hidpp write: 11 01 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp read:  10 01 8f 00 18 09 00
ratbag debug:     HID++ error from the device (1): ERR_UNSUPPORTED (09)

Duplicate of #785.


vmware-on-ocp.py doesnt properly append hostname prefix to vars for nfs and haproxy

vmware-on-ocp.py doesnt properly append hostname prefix to vars for nfs and haproxy

closed by #416


getVersionNumber does not work on Android 7.0

The getVersionNumber does not work on Android 7.0 (SDK 24) in the Mate 9 and Moto 7.
Seen on the Google Play report.

Probably related to #110


Add schema selection for Postgresql

It would be nice to have a dropdown list similar to database names for the schemas in Postgresql so I can write queries without putting schemata in front of my table names all time. Though it should be also possible to set no schemata selection to make sure you can work with multiple schemas in one query. Schema names should be put in quotes.

Actually you can change active schema in PG using database navigator (select schema->context menu->Set Active).
But database combo in main toolbar shows database list (not schemas). I agree, this is quite useless in case of PostgreSQL.
I'll fix this in the next version.


Login errors display and new user creation redirects to /explore

I added in some error handling for the create user form as well (sorry - already had that on the branch, so it was easiest to push it to make other changes).


D-STAR support

https://github.com/n7tae/new-xlxd
Note that D-STAR uses an old version of the AMBE vocoder, which md380emu cannot do. Other emulators have awful audio quality, so a hardware vocoder is needed. Shelving for now.


Table names should be quoted

If I have a basic diagram with a table in a schema mermaid seems to error on the period <schema>.<table> - e.g.
erDiagram
  metadata.ModelMetadata {
    BIGINT pkid PK
    VARCHAR-64 name
    VARCHAR-32 version
    DATETIME insert_timestamp
  }

In GitHub gives:

If I instead manually change it to:
erDiagram
  "metadata.ModelMetadata" {
    BIGINT pkid PK
    VARCHAR-64 name
    VARCHAR-32 version
    DATETIME insert_timestamp
  }

...it renders fine:
erDiagram
  "metadata.ModelMetadata" {
    BIGINT pkid PK
    VARCHAR-64 name
    VARCHAR-32 version
    DATETIME insert_timestamp
  }

I'll see if I can put in a PR to fix it. Might be able to make time in the next few weeks...

Might be able to make time in the next few weeks...

I took a look and the change was very simple:

https://github.com/endremborza/sqlmermaid/pull/3


Fixed Tailwind typo in main.html

Description
Fixes a typo in the main.html file regarding TailwindCSS. This doesn't seem to have any layout changes for now.
(this is my first PR and I just happened to come across the typo).
Fixes # (issue)
Typo in main.html: "felx-row" to "flex-row"
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:
Please put an x in the boxes that apply. You can also fill these out after creating the PR.

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x ] I have tested this code locally, and it is working as intended

Screenshots
No visible changes to the layout.

dyslexia still persists

Thanks for your contribution


Make both the Linux and Darwin servo_home variables available from Jinja

Opening this so I don't forget about this; see #324 for details.

See also #209


Add OSTN02 link to OS website

inc. brief explanation.

@dhardiman we should get slack notifications...didn't just now :( - and I did press that gorgeous green button.


Adapt Selenium Automation scripts with latest UI

Ongoing issue that needs to stay open. So that scripts match evolving UI.

TBD figure out github actions yaml to keep moving this issue over from sprint to sprint

notifications make it so script cannot activate and find the elements to click on.

2FA disabled still giving errors. try to make script to auto buy 1 free base 1 free polygon nft on rairprotocol.xyz twice per week.

Selenium script works for core workflow. Whenever modification is required will reopen


Do not allow mixture of forward and backslashes in install path match

If this idea is correct. Just an idea review.
Also, I was not sure about the \\\\ pattern part, in which environments does it match, and if its ok also like \\install\\index.php . If not, a \\{1,2} pattern would be fine I think. Well, initially I was thinking about to use only a \\, but this syntax was throwing errors in my local tests (I don't understand why), while on online testers it was fine.

What are you trying to fix here ? Is it security related ?

It's not a fix, more a tighter syntax of the regexp at most.
So we have either a /path/to/php or \\path\\to\\php , and not a /path\\like/this\\php match or \\path/like/this\\php etc.
I don't know if this is an useful commit, just wanted to share this little idea. It can be discarded and if it was also wrong on top, I can spank myself.

Ah! No I think that allowing only one version of the directory separator (no able to mix them) is ok.
And I was not aware of the \1 trick. Good thing!
@brendo do you agree ?

One thing though: Symphony mostly uses / as the regexp delimiter (instead of %). Could you change this ?

Also the dot (.) before php should be escaped (. instead of only . which matches any characters)

And I was not aware of the \1 trick. Good thing!

Yes, I've also learned this recently, so I wanted to share. The \N e.g. \1 syntax is a backreference to a previous capturing (match), in N order of the () appearence in the expression, holding the actual matched value.

Also the dot (.) before php should be escaped (. instead of only . which matches any characters)

A good point. Will do.

One thing though: Symphony mostly uses / as the regexp delimiter (instead of %). Could you change this ?

Ok, can do. Maybe all these changes will have meaning when @brendo will want to incorporate them.
And then I should probably create a single commit for all this (a rebase I guess?).
I was also puzzled about the reason for \\\\, does it match a \\ starting path? Or just a backslash path \like\this\php.

(a rebase I guess?).

git commit -a --amend
git push origin branch --force

It's easier to amend your last commit in your case (rebase + squash would also work but it's more error prone)

I was also puzzled about the reason for \\,

This is common in lots of programming language: you escape the string literal AND the regexp char.
'\'  == one \ in the string. \ is an escape char (for \n\t\r)
and then \ is also special in regexp so it needs another one (actually 2) the match one single \ char.
C#, Java, Javascript kind of have the same behavior :)
As for regexp^, I would recommand this resource https://regex101.com/#pcre
That's how I've test your regexp :)

Is this ok to merge (it looks like it?). Has this been tested on a Windows box?

Ok, can do. Maybe all these changes will have meaning when @brendo will want to incorporate them.

In this scenario where the expression has a million slashes already, I'm fine with using a different delimiter for readability.

Ok. But not it is not ready, still missing the fix for the litteral dot in index.php

Ok. But not it is not ready, still missing the fix for the litteral dot in index.php

Will ship everything mentioned by tomorrow.

Has this been tested on a Windows box?

I haven't. But if Windows does not have a \\path/likethis than it should be ok.

Ok, I've made the forced update with the updated syntax, also made the commit comment easier, but did not manage to test it under Windows in this run, only undex Linux. Will return to the win test in the evening, which is in couple of hours here.
Thanks @nitriques and @brendo for your suggestions and tips!

This breaks local WAMP and XAMPP installs. Just wont run the XSLT processes
due to invalid URI reference..
On 13 January 2015 at 12:05, Juraj Kapsz<EMAIL_ADDRESS>wrote:

Ok, I've made the forced update with the updated syntax, also made the
commit comment easier, but did not manage to test it under Windows in this
run, only undex Linux. Will return to the win test in the evening, which is
in couple of hours here.
Thanks @nitriques https://github.com/nitriques and @brendo
https://github.com/brendo for your suggestions and tips!
—
Reply to this email directly or view it on GitHub
https://github.com/symphonycms/symphony-2/pull/2301#issuecomment-69734972
.

Wouldn't it make more sense to just get rid of that entire regex/path checking and simply set a flag inside /install/index.php before bundle.php is included? oO

Wouldn't it make more sense to just get rid of that entire regex/path checking and simply set a flag inside /install/index.php before bundle.php is included? oO

Maybe, but I think it's easier to break than check the file path...

Maybe, but I think it's easier to break than check the file path...

How?

How?

I had some setup where variables declared globally where not readable by other functions...

I had some setup where variables declared globally where not readable by other functions...

How does this affect the situation we have here? This is not a function.
The change I suggest is simply set $bInsideInstaller in /install/index.php before bundle.php is included, and check if $bInsideInstaller is set inside bundle.php.
What's happening right now is that $bInsideInstaller is set inside bundle.php based on the file path and a cumbersome regex.

$bInsideInstaller may not be readable from bundle.php
But this happend to me only once...

$bInsideInstaller may not be readable from bundle.php

This seems pretty weird.

Yeah it was. @brendo ever encounter similar situation ?

 It appears that on a Windows environment you can have a mixed path.

It appears that on a Windows environment you can have a mixed path

Yeah but it's not "right". And on linux, it breaks.
I would like to test the change proposed by @jensscherbl

Yeah but it's not "right". And on linux, it breaks.

On linux, it doesn't have mixed paths... Mixed paths exist because we define (Unix) paths for certain things (workspace, templates, etc.) and get other paths, like the document root, from the system (where Windows returns backslash paths). So if you concatenate DOCROOT and /workspace/pages, you get a mixed paths on Windows. Good thing is, Windows can handle this fine, so no problem here.

2.6.x ? why not 2.6.0 ?

2.6.x ?

Sorry, my fault. 2.7.0 would be more appropriate, since 2.6.x should be hotfixes only.

why not 2.6.0

Because every change made should be well tested and could potentially create new issues that need to be fixed before a release, or even worse, remain unnoticed.
If we want to get 2.6.0 out soon, we shouldn't introduce new changes that aren't really fixing anything and are only nice to have at this point.
Same for other, pre-2.6.0 issues popping up recently. You have to decide when it's time to stop adding stuff and start stabilizing a release.

Ok though that your proposed change was a bug fix ;)
But I understand your reasoning and I agree with it.


[Feat]: Add styles.yml File for Raising Enhancement Requests Separately

Is your feature request related to a problem? Please describe.
style.yml (Custom ISSUE_TEMPLATE):

The styles.yml file, on the other hand, serves as a custom ISSUE_TEMPLATE for issues related to coding style, code formatting, and linting rules within your GitHub repository. This template helps contributors or users report code style-related concerns or seek guidance on adhering to the project's coding standards.
The contents of styles.yml might include specific questions or prompts related to coding style, requesting users to provide examples of code snippets that need formatting adjustments or explanation. Additionally, you might include instructions on how to check code against the project's style guidelines and best practices.

Describe the solution you'd like
Just Follow Above Issue
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hi @amanjaiman1 . Please Review on this Issue as soon as Possible. Thank You !

Hi @amanjaiman1 . Please Review on this Issue as soon as Possible. Thank You !

@amanjaiman1 . Please Review on this Issue?


Bootstrap CSS not rendering

Challenge Waypoint: Call out Optional Actions with Button Info has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
If I don't manually paste in the link to the Bootstrap stylesheet, the Bootstrap CSS isnt rendered on the phone. Directions said it would load in background?
My code:
<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css">

CatPhotoApp

Click here for cat photos.

  <button class="btn btn-block btn-primary">Like</button>

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">
    <input type="radio" name="indoor-outdoor"> Indoor
    <input type="radio" name="indoor-outdoor"> Outdoor
    <input type="checkbox" name="personality"> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Crazy
    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

I'm not able to reproduce this issue. Do you have any browser extension that might be blocking resources or are you getting any errors in the console when you don't include it in the editor?

Thanks for checking. I'm guessing its my browser or network. I will check from different location. I can get through each Waypoint without an error, so I can still do the lessons. Feel free to close, I will followup if I can reproduce elsewhere.

Okay, will do, hope you have better luck elsewhere! :smile:


Move hosting from github.io

We should stop using github.io and building the site in pipelines and using gh-pages branch.
Tasks

[x] Set up new solution for hosting (like AltinnPedia)
[x] Use GitHub Actions for build
[x] Delete gh-pages branch
[x] Update README
[x] Delete project in DevOps
[x] Switch DNS for docs.altinn.studio

Fixed by #931


Improve create new project walkthrough step. Closes #267

🎯 Aim
Improves create new project walkthrough step with SPFx component types.
📷 Result

✅ What was done

[X] Updated create-new-project.md file

🔗 Related issue
Closes: #267

Awesome 👏👏👏.
Thank you very much 🤩😍. You Rock
I will review it ASAP


Line graph a little off

Expected behavior
As the other graphs, when I have a container defined like this

The result is as expected. The graph is in the graph container.

See the horizontal bar at the bottom of the chart.
Current behavior
With the line graph, the graph is a little off with Microsoft Edge

With Firefox is huge

Reproducible sample
https://codepen.io/erossini/pen/jOxRXLN
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
3.7.1
Browser name and version
Microsoft Edge 106.0.1370.47 (Official build) (64-bit) / Firefox 105.0.3 (64-bit)
Link to your project
https://github.com/erossini/BlazorChartjs

Are you sure it is not within your blazor wrapper since if I put an element beneath the chart it does not render over it. Otherwise please provide a reproducable sample.

@LeeLenaleee if you insert a p in the div container, it is OK. If you add the p underneath, you have the issue. I updated the codepen


Add the miqversions executable to .gitignore

I'm not sure if this is the right way to test changes, but I built the executable locally in my development directory using go build
This gave me a dirty git status.

No idea tbh, I forget already.


feat(setup/productionize): s/scaling/productionize

Also adds a note on log/metric config

Should alleviate some of the concerns with https://github.com/spinnaker/spinnaker.github.io/pull/817


insmod failing in Petalinux 2018.1

After upgrading to Vivado 2018.1 and Petalinux 2018.1 I built a new project with 2 PL to PS only DMAs. I downloaded your latest driver code from the repository and rebuilt the kernel module along with the rest of Petalinux. Once the device was booted the only action I took was to run...
insmod /lib/modules/4.14.0-xilinx-v2018.1/extra/xilinx-axidma.ko
...this immediately resulted in a segmentation fault and the dmesg output looks as follows...
mmc0: new high speed SDHC card at address 0007 mmcblk0: mmc0:0007 SD04G 3.71 GiB   mmcblk0: p1 udevd[750]: starting version 3.2.2 udevd[751]: starting eudev-3.2.2 FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready macb e000b000.ethernet eth0: link up (1000/Full) IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready xilinx_axidma: loading out-of-tree module taints kernel. Unable to handle kernel NULL pointer dereference at virtual address 00000000 pgd = dbae8000 [00000000] *pgd=1c2b8831, *pte=00000000, *ppte=00000000 Internal error: Oops - BUG: 17 [#1] PREEMPT SMP ARM Modules linked in: xilinx_axidma(O+) uio_pdrv_genirq CPU: 1 PID: 1196 Comm: insmod Tainted: G           O    4.14.0-xilinx-v2018.1 #3 Hardware name: Xilinx Zynq Platform task: dc27ecc0 task.stack: dc0bc000 PC is at axidma_of_parse_dma_nodes+0x1fc/0x488 [xilinx_axidma] LR is at of_find_property+0x40/0x4c pc : [<bf00a40c>]    lr : [<c04f761c>]    psr: 600d0013 sp : dc0bdcd0  ip : 00000000  fp : dc7dc624 r10: dacef114  r9 : dacef100  r8 : dc7dceb0 r7 : 00000014  r6 : 00000000  r5 : 00000001  r4 : dad9fcc0 r3 : 00000000  r2 : 00000000  r1 : 600d0013  r0 : 00000000 Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none Control: 18c5387d  Table: 1bae804a  DAC: 00000051 Process insmod (pid: 1196, stack limit = 0xdc0bc210) Stack: (0xdc0bdcd0 to 0xdc0be000) dcc0:                                     dc0bdce8 00000001 00000001 00000001 dce0: bf00d018 00000000 dc7dc624 00000001 00000001 00000000 00000002 00000002 dd00: 00000002 c04f822c 00000000 dc172200 bf00d018 bf00c6f0 00000000 dc7dceb0 dd20: c7a3b964 c7a3b964 c7a3b960 00000001 00000009 dad9fcc0 00000002 bf00d018 dd40: 00000000 00000014 dc172200 00000002 c01768d0 bf009f1c dc172200 dad9fcc0 dd60: 0000002d dad9fcc0 dc172200 bf00d018 00000000 bf00d018 00000000 bf008074 dd80: bf008028 dc172210 bf00d018 c03b15fc dc172210 c0a55cd4 c0a55cd8 c03b0140 dda0: dc172210 dc172244 bf00d018 c0a18bb0 00000000 00000001 dacef264 c03b0280 ddc0: 00000000 bf00d018 c03b0204 c03ae990 dc072f58 dc177f34 bf00d018 dbb2e680 dde0: 00000000 c03af7b8 bf00b52e bf00b52f 00000000 bf00d018 dc0bdf40 dac87f00 de00: bf010000 c03b0a04 ffffe000 dc0bdf40 dac87f00 c0101a54 00000000 00000001 de20: 00000000 a00d0013 00000000 bf00d0c8 c0a3abc4 c0a3abc4 dad9f240 dac4501c de40: 014000c0 c01cd348 dcb36e60 00000000 c0a3ad00 c0a3ad00 0001acf3 a00d0013 de60: bf00d080 dc0bdf40 dac87f00 00000001 dacef240 dacef264 c01768d0 c017a818 de80: bf00d080 dac87f00 bf00d080 dc0bdf40 bf00d0c8 c0179ca8 bf00d08c 00007fff dea0: bf00d080 c0176a18 e09bc000 c0176940 c0a0e68c bf011000 e09bc000 bf00d22c dec0: ffffffff 000b9150 014002c0 00000009 00000000 c01c1fd0 dac87f00 00000000 dee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 df00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000080ec df20: 000c128c 00000000 e09c40ec 000b9150 ffffe000 00000051 00000000 c0179ec8 df40: e09bec49 e09bc000 000080ec e09c3afc e09c3970 e09c2414 00006000 00006500 df60: 00000000 00000000 00000000 000027a4 00000023 00000024 0000001b 0000001f df80: 00000011 00000000 000080ec bef90e83 bef90e7c 00000080 c01071e4 dc0bc000 dfa0: 00000000 c0107020 000080ec bef90e83 000b91a0 000080ec 000b9150 00000049 dfc0: 000080ec bef90e83 bef90e7c 00000080 000001b9 000b66c0 bef90d84 00000000 dfe0: bef90bc0 bef90bb0 00020ebc b6e75e50 600d0010 000b91a0 00000000 00000000 [<bf00a40c>] (axidma_of_parse_dma_nodes [xilinx_axidma]) from [<bf009f1c>] (axidma_dma_init+0xac/0x1bc [xilinx_axidma]) [<bf009f1c>] (axidma_dma_init [xilinx_axidma]) from [<bf008074>] (axidma_probe+0x4c/0xc4 [xilinx_axidma]) [<bf008074>] (axidma_probe [xilinx_axidma]) from [<c03b15fc>] (platform_drv_probe+0x50/0x9c) [<c03b15fc>] (platform_drv_probe) from [<c03b0140>] (driver_probe_device+0x1ec/0x2b0) [<c03b0140>] (driver_probe_device) from [<c03b0280>] (__driver_attach+0x7c/0xa8) [<c03b0280>] (__driver_attach) from [<c03ae990>] (bus_for_each_dev+0x7c/0x8c) [<c03ae990>] (bus_for_each_dev) from [<c03af7b8>] (bus_add_driver+0x16c/0x1d4) [<c03af7b8>] (bus_add_driver) from [<c03b0a04>] (driver_register+0xa0/0xe0) [<c03b0a04>] (driver_register) from [<c0101a54>] (do_one_initcall+0xfc/0x11c) [<c0101a54>] (do_one_initcall) from [<c017a818>] (do_init_module+0x54/0x1c4) [<c017a818>] (do_init_module) from [<c0179ca8>] (load_module+0x1d98/0x1e9c) [<c0179ca8>] (load_module) from [<c0179ec8>] (SyS_init_module+0x11c/0x12c) [<c0179ec8>] (SyS_init_module) from [<c0107020>] (ret_fast_syscall+0x0/0x48) Code: e1a00006 eb53b475 e3500000 1a000006 (e5963000)  ---[ end trace 588ea7ea39cf59c0 ]--- root@avnet-digilent-zedboard-2018_1:~# insmod /lib/modules/4.14.0-xilinx-v2018.1/extra/xilinx-axidma.ko ^C root@avnet-digilent-zedboard-2018_1:~#  root@avnet-digilent-zedboard-2018_1:~# ^C    root@avnet-digilent-zedboard-2018_1:~#  root@avnet-digilent-zedboard-2018_1:~#  root@avnet-digilent-zedboard-2018_1:~#  root@avnet-digilent-zedboard-2018_1:~#  root@avnet-digilent-zedboard-2018_1:~# packet_write_wait: Connection to <IP_ADDRESS> port 22: Broken pipe brandon@brandon-zynq:~/petaproject-2018-1$ petalinux-build --project req-tester[INFO] building project [INFO] sourcing bitbake
As I mentioned in a previous post I know that xilinx upgraded their dma driver for a few reasons, like support of 64MB transfers, but I thought that if I just maintained the 8MB max that things would be ok.
Maybe this is a compatibility issue with the new driver? or maybe this is a deeper issue? I know the circumstances are very different but could it possibly be related to the fault seen in #45 ?

Found the issue. Turns out that it was a mal-formatted device tree which caused the code to index a non-existent child node in the device tree dma entry. Specifically the axi dma character driver entry had looked like this...
axidma_chrdev: axidma_chrdev@0 {
	    compatible = "xlnx,axidma-chrdev";
	    dmas = <&e_dma_hier_axi_e_dma 0 &u_dma_hier_axi_u_dma 1>; //bad line
	    dma-names = "eth_rx_img_ch", "usb_rx_img_ch";
	};

when it should have looked like this...
axidma_chrdev: axidma_chrdev@0 {
	    compatible = "xlnx,axidma-chrdev";
	    dmas = <&e_dma_hier_axi_e_dma 0 &u_dma_hier_axi_u_dma 0>; //corrected
	    dma-names = "eth_rx_img_ch", "usb_rx_img_ch";
	};

@bperez77 If I can make a recommendation to help others realize they've made this mistake and to prevent segmentation faults due to NULL pointer deference I would modify the axidma_of.c to validate that the child node exists before trying to use it. Maybe issue a kernel print that says it failed to find the specified child node and to check the device tree for errors?
  // Go to the child node that we're parsing
    dma_chan_node = of_get_next_child(dma_node, NULL);
    if (channel == 1) {
        dma_chan_node = of_get_next_child(dma_node, dma_chan_node);
    }

//ADD NEW CODE HERE TO CHECK IF DMA_CHAN_NODE IS NULL!!!

    // Read out the channel's unique device id, and put it in the structure
    if (of_find_property(dma_chan_node, "xlnx,device-id", NULL) == NULL) {
        axidma_node_err(dma_chan_node, "DMA channel is missing the "
                        "'xlnx,device-id' property.\n");
        return -EINVAL;
    }

@bperez77 Hi it seems like you are using two dma in your design
would you please give more infomation about your design?
now i'm facing Unable to get slave channel 0: rx_channel. problem
I have modified my devicetree like this

but insmod xxx.ko still failed


Improve errors infra and handle api rate limit

Description
Improve errors infrastructure so all error types will have "Is" function so they can be compare easily and optimized,
Handle API Rate limit error so this is the error that will back instead of the generic error (like "Failed to refresh token")
Must

[x] Tests
[x] Documentation (if applicable)

Let's also add example to examples and README on how to handle the new error.


Tables with resources have no edge borders

Setup

Rancher version: v2.6-96bce6e0882099a15c0ded35c069a786d9aadbde-head
Browser type & version: Chrome/Firefox/Safari

Describe the bug

Tables with resources have no edge borders
To Reproduce

Log in to Rancher as an admin
Result
the table with list of clusters have no edge borders
Same issue with

"Continues Delivery" (Menu -> Continues Delivery -> any page)
"Cluster Management" (Menu -> Cluster Management -> Clusters or Cloud Credentials) but drivers table looks good
Navigate through your local cluster (Workloads, Apps, Service Discovery, Storage etc)

Expected Result

Tables should look whole
Screenshots

Test Environment:
same as when the issue was logged

Testing:
Navigated through multiple pages and confirmed that the original issue with tables missing borders is fixed


capemgr_loader causes kernel panic in  4.1.18-bone-rt-r20

I am trying to load capes using uEnv.txt. The BB-BONE-LOGIBONE cape is based on this https://github.com/QuickJack/logi-kernel/blob/master/beaglebone-black/logibone_ra2/BB-BONE-LOGIBONE-00A3.dts. I am using am33xx-boneblack-oberlay.dtb.
(1) cape_enable=bone_capemgr.enable_partno=BB-BONE-LOGIBONE:00A3 => Both capes are loading/working fine
(2) cape_enable=BB-UART1,bone_capemgr.enable_partno=BB-BONE-LOGIBONE:00A3  => Both capes are loading/working fine
(3) cape_enable=BB-UART1,BB-UART2 and loading BB-BONE-LOGIBONE by using "echo BB-BONE-LOGIBONE:00A3 > /sys/devices/platform/bone_capemgr/slots" is working fine
(4) cape_enable=BB-UART1,BB-UART2,bone_capemgr.enable_partno=BB-BONE-LOGIBONE:00A3 => kernel panic:

[    4.119697] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,0A5A,1713BBBK2912                                                                             '
[    4.127011] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-bla                                                                             ck - #slots=4
[    4.143802] mmc0: host does not support reading read-only switch, assuming wr                                                                             ite-enable
[    4.154742] mmc0: new high speed SDHC card at address aaaa
[    4.161004] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[    4.167063]  mmcblk0: p1 p2
[    4.190372] bone_capemgr bone_capemgr: slot #0: No cape found
[    4.250337] bone_capemgr bone_capemgr: slot #1: No cape found
[    4.310333] bone_capemgr bone_capemgr: slot #2: No cape found
[    4.340147] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 3
[    4.347345] bone_capemgr bone_capemgr: slot #3: No cape found
[    4.353153] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' VER '                                                                             N/A' PR '0'
[    4.361304] bone_capemgr bone_capemgr: slot #4: override
[    4.366648] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[    4.373668] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Ove                                                                             rride Manuf,BB-UART1'
[    4.382806] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART2' VER '                                                                             N/A' PR '0'
[    4.390958] bone_capemgr bone_capemgr: slot #5: override
[    4.396300] bone_capemgr bone_capemgr: Using override eeprom data at slot 5
[    4.403319] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Ove                                                                             rride Manuf,BB-UART2'
[    4.412447] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-BONE-LOGIBON                                                                             E' VER '00A3#=>kernel' PR '0'
[    4.422170] bone_capemgr bone_capemgr: slot #6: override
[    4.427512] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[    4.434532] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A3,Ove                                                                             rride Manuf,BB-BONE-LOGIBONE'
[    4.444709] bone_capemgr bone_capemgr: initialized OK.
[   39.710779] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltag                                                                             e latency[950000<->1325000]:-22
[   39.721319] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltag                                                                             e latency[950000<->1325000]:-22
[   39.731378] cpufreq: __cpufreq_add_dev: CPU0: Running at unlisted freq: 55000                                                                             0 KHz
[   55.651843] capemgr-loader- invoked oom-killer: gfp_mask=0x2800d0, order=0, o                                                                             om_score_adj=0
[   55.660258] capemgr-loader- cpuset=/ mems_allowed=0
[   57.487946] CPU: 0 PID: 65 Comm: capemgr-loader- Not tainted 4.1.17-bone-rt-r                                                                             19 #1
[   57.495628] Hardware name: Generic AM33XX (Flattened Device Tree)
[   57.501835] [] (unwind_backtrace) from [] (show_stack+0x1                                                                             1/0x14)
[   57.509639] [] (show_stack) from [] (dump_header+0x4d/0x1                                                                             4c)
[   57.517111] [] (dump_header) from [] (__out_of_memory+0x2                                                                             79/0x284)
[   57.525096] [] (__out_of_memory) from [] (out_of_memory+0                                                                             x4d/0x54)
[   57.533081] [] (out_of_memory) from [] (__alloc_pages_nod                                                                             emask+0x5ad/0x65c)
[   57.541851] [] (__alloc_pages_nodemask) from [] (new_slab                                                                             +0x1e5/0x248)
[   57.550166] [] (new_slab) from [] (__slab_alloc.constprop                                                                             .9+0x157/0x1a8)
[   57.558669] [] (__slab_alloc.constprop.9) from [] (kmem_c                                                                             ache_alloc+0x87/0xd0)
[   57.567697] [] (kmem_cache_alloc) from [] (__d_alloc+0x1f                                                                             /0xd8)
[   57.575415] [] (__d_alloc) from [] (d_alloc+0x11/0x30)
[   57.582360] [] (d_alloc) from [] (lookup_dcache+0x53/0x70                                                                             )
[   57.589625] [] (lookup_dcache) from [] (__lookup_hash+0x1                                                                             7/0x2c)
[   57.597430] [] (__lookup_hash) from [] (lookup_slow+0x2b/                                                                             0x6c)
[   57.605063] [] (lookup_slow) from [] (link_path_walk+0x1d                                                                             5/0x570)
[   57.612956] [] (link_path_walk) from [] (path_openat+0x3b                                                                             /0x3e0)
[   57.620763] [] (path_openat) from [] (do_filp_open+0x23/0                                                                             x60)
[   57.628296] [] (do_filp_open) from [] (file_open_name+0xb                                                                             b/0xf0)
[   57.636101] [] (file_open_name) from [] (filp_open+0x21/0                                                                             x34)
[   57.643660] [] (filp_open) from [] (_request_firmware+0x1                                                                             93/0x56c)
[   57.651649] [] (_request_firmware) from [] (request_firmw                                                                             are_direct+0x21/0x2c)
[   57.660691] [] (request_firmware_direct) from [] (capemgr                                                                             _load_slot+0x87/0x440)
[   57.669791] [] (capemgr_load_slot) from [] (capemgr_loade                                                                             r+0x89/0x2f8)
[   57.678127] [] (capemgr_loader) from [] (kthread+0x8b/0xa                                                                             0)
[   57.685500] [] (kthread) from [] (ret_from_fork+0x11/0x30                                                                             )
[   57.692772] Mem-Info:
[   57.695076] active_anon:0 inactive_anon:0 isolated_anon:0
[   57.695076]  active_file:0 inactive_file:0 isolated_file:0
[   57.695076]  unevictable:0 dirty:0 writeback:0 unstable:0
[   57.695076]  slab_reclaimable:1193 slab_unreclaimable:793
[   57.695076]  mapped:0 shmem:0 pagetables:1 bounce:0
[   57.695076]  free:124291 free_pcp:157 free_cma:6078
[   57.726649] Normal free:497164kB min:2848kB low:3560kB high:4272kB active_ano                                                                             n:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolat                                                                             ed(anon):0kB isolated(file):0kB present:524288kB managed:507108kB mlocked:0kB di                                                                             rty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:4772kB slab_unreclai                                                                             mable:3172kB kernel_stack:352kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:                                                                             628kB local_pcp:628kB free_cma:24312kB writeback_tmp:0kB pages_scanned:0 all_unr                                                                             eclaimable? yes
[   57.770029] lowmem_reserve[]: 0 0 0
[   57.773575] Normal: 9*4kB (UEMR) 9*8kB (UERC) 8*16kB (UEMRC) 11*32kB (UEMRC)                                                                              9*64kB (UEMRC) 7*128kB (UERC) 8*256kB (UEMR) 7*512kB (UEMRC) 6*1024kB (UERC) 6*2                                                                             048kB (UEMRC) 3*4096kB (UEC) 56*8192kB (UEC) = 497164kB
[   57.792729] 0 total pagecache pages
[   57.796239] 0 pages in swap cache
[   57.799568] Swap cache stats: add 0, delete 0, find 0/0
[   57.804830] Free swap  = 0kB
[   57.807721] Total swap = 0kB
[   57.810627] 131072 pages RAM
[   57.813518] 0 pages HighMem/MovableOnly
[   57.817369]<PHONE_NUMBER> pages reserved
[   57.821061] 6144 pages cma reserved
[   57.824565] [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oo                                                                             m_score_adj name
[   57.833180] Kernel panic - not syncing: Out of memory and no killable process                                                                             es...
[   57.833180]
[   57.842274] CPU: 0 PID: 65 Comm: capemgr-loader- Not tainted 4.1.17-bone-rt-r                                                                             19 #1
[   57.849875] Hardware name: Generic AM33XX (Flattened Device Tree)
[   57.856014] [] (unwind_backtrace) from [] (show_stack+0x1                                                                             1/0x14)
[   57.863806] [] (show_stack) from [] (panic+0x6d/0x180)
[   57.870724] [] (panic) from [] (oom_zonelist_trylock+0x1/                                                                             0x80)
[   57.878344] [] (oom_zonelist_trylock) from [] (contig_pag                                                                             e_data+0xb10/0xb5c)
[   57.887182] ---[ end Kernel panic - not syncing: Out of memory and no killabl                                                                             e processes...
[   57.887182]
[   80.720349] random: nonblocking pool is initialized

Ich have to say, that I am not using the EEPROM on the Logibone. It has never been programmed. I am loading everything manually.

It is enough to add "cape_enable=bone_capemgr.enable_partno=UART1,UART2,UART3" to uEnv.txt. This will produce the above kernel panic. There's also an excessive delay when the capes are initialized during boot.
This bug is not related to the Logibone in any way!

I don't see that oom issue yet:
debian@beaglebone:~$ uname -r
4.1.18-ti-rt-r49
debian@beaglebone:~$ cat /proc/cmdline
console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=UUID=1ea435af-d6f7-4713-9c46-758c7e0d2c75 ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
debian@beaglebone:~$ dmesg | grep bone
[    0.000000] Kernel command line: console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=UUID=1ea435af-d6f7-4713-9c46-758c7e0d2c75 ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
[    3.848068] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,,BBG115096703'
[    3.848101] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4
[    3.902769] bone_capemgr bone_capemgr: slot #0: No cape found
[    3.962745] bone_capemgr bone_capemgr: slot #1: No cape found
[    4.022741] bone_capemgr bone_capemgr: slot #2: No cape found
[    4.082742] bone_capemgr bone_capemgr: slot #3: No cape found
[    4.088541] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' VER 'N/A' PR '0'
[    4.088556] bone_capemgr bone_capemgr: slot #4: override
[    4.088573] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[    4.088590] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-UART1'
[    4.088716] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART2' VER 'N/A' PR '0'
[    4.088730] bone_capemgr bone_capemgr: slot #5: override
[    4.088742] bone_capemgr bone_capemgr: Using override eeprom data at slot 5
[    4.088757] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-UART2'
[    4.088862] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART3' VER 'N/A' PR '0'
[    4.088876] bone_capemgr bone_capemgr: slot #6: override
[    4.088888] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[    4.088904] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,BB-UART3'
[    4.089554] bone_capemgr bone_capemgr: initialized OK.
[    4.105042] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-UART1-00A0.dtbo' loaded; overlay id #0
[    4.109409] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-UART2-00A0.dtbo' loaded; overlay id #1
[    4.109566] bone_capemgr bone_capemgr: slot #6: dtbo 'BB-UART3-00A0.dtbo' loaded; overlay id #2
[   13.388091] LUN: removable file: /var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

You are using a different kernel. Did you also use am335x-boneblack-overlay.dtb in uEnv.txt?
I will post the exact output when using UART1, UART2 & UART3 on monday.

it's the exact same overlay patchset, no i used: am335x-bonegreen-overlay.dtb
But that's exactly the same as am335x-boneblack-overlay.dtb

There's on difference. I have connected the Logibone and did not program the EEPROM which is at address 0x57. According to http://papermint-designs.com/community/node/331 this is equivalent to Slot 3.
The relevant dmesg output is:

[    4.340147] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 3
[    4.347345] bone_capemgr bone_capemgr: slot #3: No cape found

I checked it with a blank BeagleBone Black and the problem is still there. It might have something to do with the fact, that I cannot update the overlays from https://github.com/RobertCNelson/bb.org-overlays using install.sh. The problem is "E: Unable to locate package bb-customizations". Obviously this package does not exisit in my active repositories.

Yeah i can factor out bb-customizations, that's just to bring the initramfs hook, dtbo..
Not sure if # is ignored, but the dtb= should be removed..
[    0.000000] Kernel command line:
console=ttyS0,115200
bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3#=>kernel panic!!!
root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait dtb=

btw, did you change the config?  still not sure why oom is getting triggered...
Regards,

Using "console=ttyS0,115200 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait dtb=am335x-boneblack-overlay.dtb" the problem still exists.
Yes, I changed uEnv.txt. I added:

fdtfile=am335x-boneblack-overlay.dtb
dtb=am335x-boneblack-overlay.dtb

Is this https://eewiki.net/display/linuxonarm/BeagleBone+Black information about uEnv.txt still up to date?

It is, but you don't need to pass "dtb=am335x-boneblack-overlay.dtb" on the boot arg's.. just set it in /boot/uEnv.txt as:
dtb=am335x-boneblack-overlay.dtb

Regards,

@QuickJack still no oom's..
https://paste.debian.net/413304/
root@beaglebone:~# uname -r
4.1.18-bone-rt-r20

root@beaglebone:~# cat /boot/uEnv.txt | grep -v '#' | grep dtb
dtb=am335x-boneblack-overlay.dtb

root@beaglebone:~# cat /proc/cmdline
console=tty0 console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable

root@beaglebone:~# dmesg | grep bone
[    0.000000] Linux version 4.1.18-bone-rt-r20 (root@b4-jetson-tk1-2gb) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 Mon Feb 29 20:15:46 UTC 2016
[    0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable
[    3.083699] usb usb1: Manufacturer: Linux 4.1.18-bone-rt-r20 musb-hcd
[    3.207605] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,,BBG115096609'
[    3.207628] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4
[    3.262501] bone_capemgr bone_capemgr: slot #0: No cape found
[    3.322491] bone_capemgr bone_capemgr: slot #1: No cape found
[    3.382489] bone_capemgr bone_capemgr: slot #2: No cape found
[    3.442488] bone_capemgr bone_capemgr: slot #3: No cape found
[    3.448274] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' VER 'N/A' PR '0'
[    3.448285] bone_capemgr bone_capemgr: slot #4: override
[    3.448299] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[    3.448313] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-UART1'
[    3.448391] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART2' VER 'N/A' PR '0'
[    3.448401] bone_capemgr bone_capemgr: slot #5: override
[    3.448410] bone_capemgr bone_capemgr: Using override eeprom data at slot 5
[    3.448423] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-UART2'
[    3.448491] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART3' VER 'N/A' PR '0'
[    3.448501] bone_capemgr bone_capemgr: slot #6: override
[    3.448510] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[    3.448522] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,BB-UART3'
[    3.448832] bone_capemgr bone_capemgr: initialized OK.
[    3.467368] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-UART1-00A0.dtbo' loaded; overlay id #0
[    3.468098] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-UART2-00A0.dtbo' loaded; overlay id #1
[    3.470023] bone_capemgr bone_capemgr: slot #6: dtbo 'BB-UART3-00A0.dtbo' loaded; overlay id #2
[    8.998590] LUN: removable file: /var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img

Please dump config.gz to pastebin...
zcat /proc/config.gz

Regards,

I did not change my kernel config. Here is the link to the pastebin of my kernel config: http://pastebin.com/MErh66xA

I tested  https://rcn-ee.com/rootfs/2016-02-11/microsd/bone-ubuntu-14.04.3-console-armhf-2016-02-11-2gb.img.xz which uses the TI kernel by default. It indeed works to activate UART1, UART2  & UART3. However, I noticed that a lot of things have changed:
(1) There are 2 different uEnv.txt files: /uEnv.txt and /boot/uEnv.txt
(2) After running install_kernel.sh from the bb-kernel the system won't boot. Those two kernel variants are obviously incompatible in some way.
(3) There is only one partition. The boot partion seems to be removed
(4) I cannot find UBboot. During boot a 2013 version of UBoot is loaded. I guess this is loaded from the eMMC. I cannot use the eMMC because it shares the GPMC pins.
(5) I used to load the kernel image from /boot/zImage. The new SDCard uses /boot/vmlinuz-
I think there's a lot of confusion about which UBoot image is loaded from which location. Also the format of uEnv.txt is constantly changing. There are even multiple different versions of uEnv.txt within a single partition.

(1) There are 2 different uEnv.txt files: /uEnv.txt and /boot/uEnv.txt

"/uEnv.txt" is just a shim for old versions of u-boot stuck in eMMC (retains compatibly all the way back to, Angstrom's 2013.06.20)
Since you are utilizing the eMMC for something else, just zero out the eMMC so you don't have to deal with that version of u-boot..
(2) After running install_kernel.sh from the bb-kernel the system won't boot. Those two kernel variants are obviously incompatible in some way.

Remove "/uEnv.txt" then "install_kernel.sh" will work, as it's falling in the first if statement here:
https://github.com/RobertCNelson/stable-kernel/blob/master/tools/install_kernel.sh#L146-L166
when it really needs to enter the 2nd, if..
(3) There is only one partition. The boot partion seems to be removed
(4) I cannot find UBboot. During boot a 2013 version of UBoot is loaded. I guess this is loaded from the eMMC. I cannot use the eMMC because it shares the GPMC pins.

Correct, it makes things a lot more reliable, MLO/u-boot.img are dd'ed into the 1MB hole at the start of the drive
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSDcard
(5) I used to load the kernel image from /boot/zImage. The new SDCard uses /boot/vmlinuz-

I think there's a lot of confusion about which UBoot image is loaded from which location. Also the format of uEnv.txt is constantly changing. There are even multiple different versions of uEnv.txt within a single partition.

Here is the full right up of what's going on:
http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
Haven't really made any changes to ^ since summer of 2014, just tweak/fix/addon's, but the same syntax in /boot/uEnv.txt

Many thanks for your comments. I will take a look into it asap.
I manually added the kernel to the new SDCard by moving the zImage to /boot/vmlinuz-4.1.18-bone-rt-r20 and adding the dtb files to /boot/dtbs/4.1.18-bone-rt-r20. I commented out the loadxrd line in /uEnv.txt. I also uncommented the dtb=am335x-boneblack-overly line and activated the UARTs in /boot/uEnv.txt. Here is my bootlog:

U-Boot 2013.04-dirty (May 06 2013 - 16:12:47)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:    not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  1  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
1180 bytes read in 10 ms (115.2 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
1227 bytes read in 64 ms (18.6 KiB/s)
debug: [/boot/vmlinuz-4.1.18-bone-rt-r20] ...
6907304 bytes read in 1213 ms (5.4 MiB/s)
## Error: "loadxrd" not defined
debug: [/boot/dtbs/4.1.18-bone-rt-r20/am335x-boneblack-overlay.dtb] ...
54299 bytes read in 107 ms (495.1 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] ...
debug: [bootz 0x82000000 0x88080000: 0x88000000] ...
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Using Device Tree in place at 88000000, end 8801041a

Starting kernel ...

[    3.008480] omap_voltage_late_init: Voltage driver support not added
[    3.015517] cpu cpu0: cpu0 clock notifier not ready, retry
[    3.130614] bone_capemgr bone_capemgr: slot #0: No cape found
[    3.190609] bone_capemgr bone_capemgr: slot #1: No cape found
[    3.250605] bone_capemgr bone_capemgr: slot #2: No cape found
[    3.280427] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 3
[    3.287637] bone_capemgr bone_capemgr: slot #3: No cape found
[   71.693351] Kernel panic - not syncing: Out of memory and no killable processes...
[   71.693351]
[   71.702479] CPU: 0 PID: 65 Comm: capemgr-loader- Not tainted 4.1.18-bone-rt-r20 #1
[   71.710093] Hardware name: Generic AM33XX (Flattened Device Tree)
[   71.716240] [] (unwind_backtrace) from [] (show_stack+0x11/0x14)
[   71.724045] [] (show_stack) from [] (panic+0x6d/0x18c)
[   71.730972] [] (panic) from [] (oom_zonelist_trylock+0x1/0x80)
[   71.738605] [] (oom_zonelist_trylock) from [] (contig_page_data+0xb10/0xb5c)
[   71.747458] ---[ end Kernel panic - not syncing: Out of memory and no killable processes...
[   71.747458]
[   80.480636] random: nonblocking pool is initialized
[  102.095167] musb-hdrc mus

After all these tests I think that the problem seems to be kernel related

Oh, there is one other thing we should test. ;)
Hold the boot button, before power up, to force the much newer version of u-boot on the microSD to load vs, the old version in eMMC...
Regards,

After pressing the boot button the result is as follows:

U-Boot 2016.01-00001-g795bd53 (Jan 25 2016 - 20:02:29 -0600), Build: jenkins-github_Bootloader-Builder-325

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:    not set. Validating first E-fuse MAC
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
1180 bytes read in 10 ms (115.2 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
1227 bytes read in 67 ms (17.6 KiB/s)
debug: [/boot/vmlinuz-4.1.18-bone-rt-r20] ...
6907304 bytes read in 452 ms (14.6 MiB/s)
## Error: "loadxrd" not defined
debug: [/boot/dtbs/4.1.18-bone-rt-r20/am335x-boneblack-overlay.dtb] ...
54299 bytes read in 105 ms (504.9 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] ...
debug: [bootz 0x82000000 0x88080000: 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x6965a8 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Using Device Tree in place at 88000000, end 8801041a

Starting kernel ...

[    2.877502] omap_voltage_late_init: Voltage driver support not added
[    2.884376] cpu cpu0: cpu0 clock notifier not ready, retry
[    2.992437] bone_capemgr bone_capemgr: slot #0: No cape found
[    3.052434] bone_capemgr bone_capemgr: slot #1: No cape found
[    3.112433] bone_capemgr bone_capemgr: slot #2: No cape found
[    3.142173] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 3
[    3.149360] bone_capemgr bone_capemgr: slot #3: No cape found
[   32.568162] Kernel panic - not syncing: Out of memory and no killable processes...
[   32.568162]
[   32.577273] CPU: 0 PID: 65 Comm: capemgr-loader- Not tainted 4.1.18-bone-rt-r20 #1
[   32.584877] Hardware name: Generic AM33XX (Flattened Device Tree)
[   32.591006] [] (unwind_backtrace) from [] (show_stack+0x11/0x14)
[   32.598793] [] (show_stack) from [] (panic+0x6d/0x18c)
[   32.605706] [] (panic) from [] (oom_zonelist_trylock+0x1/0x80)
[   32.613322] [] (oom_zonelist_trylock) from [] (contig_page_data+0xb10/0xb5c)
[   32.622161] ---[ end Kernel panic - not syncing: Out of memory and no killable processes...
[   32.622161]
[   80.552439] random: nonblocking pool is initialized

I did another test which proves that the bb-kernel has a problem. I copied /boot/vmlinuz-4.1.17-ti-rt-r47 from the above mentioned image to my SDCard to /boot/uboot/zImage. In order to save some time I did not update .dtb files or modules. The system boots fine.
After activating UARTs 1..3 there is no problem at all:

uname -r
4.1.17-ti-rt-r47

dmesg|grep bone
[    0.000000] Kernel command line: console=ttyS0,115200 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait dtb=am335x-boneblack-overlay.dtb

dmesg|grep bone
o=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait dtb=am335x-boneblack-overlay.dtb[    0.000000] Kernel command line: console=ttyS0,115200 bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait dtb=am335x-boneblack-overlay.dtb
[    5.065287] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,0A5A,1713BBBK2912'
[    5.072590] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4
[    5.135655] bone_capemgr bone_capemgr: slot #0: No cape found
[    5.195653] bone_capemgr bone_capemgr: slot #1: No cape found
[    5.255651] bone_capemgr bone_capemgr: slot #2: No cape found
[    5.285671] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 3
[    5.292856] bone_capemgr bone_capemgr: slot #3: No cape found
[    5.298676] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' VER 'N/A' PR '0'
[    5.306826] bone_capemgr bone_capemgr: slot #4: override
[    5.312181] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[    5.319198] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-UART1'
[    5.328404] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART2' VER 'N/A' PR '0'
[    5.336554] bone_capemgr bone_capemgr: slot #5: override
[    5.341906] bone_capemgr bone_capemgr: Using override eeprom data at slot 5
[    5.348922] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-UART2'
[    5.358106] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART3' VER 'N/A' PR '0'
[    5.366254] bone_capemgr bone_capemgr: slot #6: override
[    5.371605] bone_capemgr bone_capemgr: Using override eeprom data at slot 6
[    5.378621] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,BB-UART3'
[    5.388608] bone_capemgr bone_capemgr: initialized OK.
[    6.529811] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-UART1-00A0.dtbo' loaded; overlay id #2
[    6.529994] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-UART2-00A0.dtbo' loaded; overlay id #1
[    6.530110] bone_capemgr bone_capemgr: slot #6: dtbo 'BB-UART3-00A0.dtbo' loaded; overlay id #0
[   22.161460] bone_capemgr bone_capemgr: part_number 'BB-BONE-LOGIBONE', version '00A3'
[   22.161497] bone_capemgr bone_capemgr: slot #7: override
[   22.161516] bone_capemgr bone_capemgr: Using override eeprom data at slot 7
[   22.161535] bone_capemgr bone_capemgr: slot #7: 'Override Board Name,00A3,Override Manuf,BB-BONE-LOGIBONE'
[   22.203851] bone_capemgr bone_capemgr: slot #7: dtbo 'BB-BONE-LOGIBONE-00A3.dtbo' loaded; overlay id #3

Can you reproduce the problem with capemgr?
I have tested  4.1.18-ti-rt-r52.1 which uses the Linux DMA Engine API. After recompiling the Logibone driver it is working fine. Unfortunately, the CPU load increased from 17% to 23% when running my application. This means that this kernel is a step back compared to the bb-kernel.

Meanwhile I have switched to the latest rootfs and the problem disappeared. I am using a 4.1.x bone-rt kernel. There seems to be a problem with my old rootfs and/or partitioning scheme. It does not play nicely with capemgr.
I am closing this issue as it involves a combination of a new kernel and an old rootfs/ partitioning scheme which is difficult to reproduce.


SQL block does not support magic comment

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
I write sql code block like this
insert into BOOK(
    ID, NAME, EDITION, PRICE, STORE_ID
) values(?, ?, ?, ?, ?)
/* batch-0: [100, SQL in Action, 1, 59.9, 2] */
/* highlight-next-line */
/* batch-1: [7, LINQ in Action, 3, 49.9, 2] */

I used /* highlight-next-line */ to highlight the last line, but it is actually not highlighted
This magic comment works normally for all languages except sql.
Reproducible demo
No response
Steps to reproduce
Just write a code block

Language is SQL
Use highlight-next-line

Expected behavior
The next lien should be highlighted
Actual behavior
The next line is not highlighted
This bug only appears when language is SQL
Your environment
OS: Mac-M1
Docusaurus: 3.6.3
Node version: 22.2.0
Self-service

[ ] I'd be willing to fix this bug myself.

Looks like we don't support multi-line comments for SQL, only single-line -- syntax.
This works:
```sql
insert into BOOK(
    ID, NAME, EDITION, PRICE, STORE_ID
) values(?, ?, ?, ?, ?)
/* batch-0: [100, SQL in Action, 1, 59.9, 2] */
-- highlight-next-line
/* batch-1: [7, LINQ in Action, 3, 49.9, 2] */
```

I think it should be pretty easy to add SQL multi-line comments, if anyone from the community want to contribute that in packages/docusaurus-theme-common/src/utils/codeBlockUtils.ts

I want to contribute to this is it still open ?

You can submit a PR directly

i made the changes but how i test those by viewing them to confirm

https://github.com/facebook/docusaurus/blob/main/CONTRIBUTING.md#development

i am not sure how to view it even after changes it looks it is not taking effect
here is what i tried
added a new comment pattern
sql:{start:'/*',end:'*/'},
created a seprate case for sql inside getAllMagicCommentDirectiveStyles function
 case 'sql':
      return getCommentPattern(['sql','lua'], magicCommentDirectives);

We can't help you without seeing a PR including all your code and how it renders in the Netlify preview sorry. Please submit a draft PR and we'll review your attempt.