Build output has canonical link linking to the same URL as another alternate link, leading to SEO issues

Environment
❯ npx nuxi info
Working directory: /home/projects/github-q5ddsy                                17:08:17
Nuxt project info:                                                             17:08:17

------------------------------
- Operating System: Linux
- Node Version:     v18.20.3
- Nuxt Version:     3.13.1
- CLI Version:      3.13.1
- Nitro Version:    2.9.7
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      compatibilityDate, devtools, modules, pages, routeRules, i18n
- Runtime Modules<EMAIL_ADDRESS>- Build Modules:    -
------------------------------

                                                                               17:08:17
👉 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml
👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new
👉 Read documentation: https://nuxt.com

Reproduction
Reproduction here:
https://stackblitz.com/edit/github-q5ddsy-62oh2a?file=.output%2Fpublic%2Findex.html
Summary: Using nuxt-i18n with a default language and a translated language
Describe the bug
Please check the output index.html at

either live in your browser
build the project with npx nuxt build --preset github_pages

Take a look at the auto-generated <link> elements, especially the rel="alternate" & red="canonical":
<link id="i18n-alt-en" rel="alternate" href="https://example.com/en" hreflang="en">
<link id="i18n-alt-en-US" rel="alternate" href="https://example.com/en" hreflang="en-US">
<link id="i18n-alt-de" rel="alternate" href="https://example.com" hreflang="de">
<link id="i18n-alt-de-DE" rel="alternate" href="https://example.com" hreflang="de-DE">
<link id="i18n-xd" rel="alternate" href="https://example.com" hreflang="x-default">
<link id="i18n-can" rel="canonical" href="https://example.com">

Notice, that the same URL https://example.com is being referred to, from:
<link id="i18n-xd" rel="alternate" href="https://example.com" hreflang="x-default">
<link id="i18n-can" rel="canonical" href="https://example.com">
<link id="i18n-alt-de" rel="alternate" href="https://example.com" hreflang="de">

That leads in SEO indexing/crawling, to an issue:

Bing Webmaster tools are complaining about the canonical link, referring to a link that is already marked as an alternative translation
Google Search Console is complaining about the same issue

URL that I requested indexing for: https://waldemarenns.de/
Bing Webmaster Tools:
URL cannot be indexed by Bing
The URL is not indexable as the page is an alternate version of the similar page which you have specified as canonical version using a <link rel="canonical"> tag. Bing does not index the alternate version.
Canonical URL :https://waldemarenns.de/en

Screenshot:

Google Page Speed Insights:
Document does not have a valid rel=canonicalPoints to another `hreflang` location (https://waldemarenns.de/)

Screenshot:

Take a look: https://pagespeed.web.dev/analysis/https-waldemarenns-de/30jj8518lg?form_factor=desktop
ℹ Feel free to inspect my site that is mentioned.
Additional context
Refers to #2925
Logs
No response

@WaldemarEnns Why the confused emoji? Aren't you getting the same alternate links (href) on all the locales?

Sorry for the late response, was a bit swamped with other things, I'll be investigating this issue in the coming days.

@memic84 I just wanted to express that I am struggling with the same issue 😀 Yes, I get the same results.
@BobbieGoede thanks!

@memic84
In your case I can see (based on the compiled code) that you're not using the latest release, so I can't exclude it already having been fixed.
Your issue differs from the that of @WaldemarEnns, and I can't reproduce your issue with their provided reproduction, could you open a new issue with a minimal reproduction preferably using the latest version? 🙏

@BobbieGoede Thank you for the quick check, and indeed i see that i have missed some releases from the last 2 weeks. If this still occurs, i'll open a new issue.
@WaldemarEnns Ah, didn't get the emoji :) seems after all a different issue.

@memic84
Also, make sure you have a baseUrl configured https://i18n.nuxtjs.org/docs/guide/seo#requirements, it seems to be unset currently.

@WaldemarEnns
I'm getting the impression the issue is caused by the Bing/Google crawlers being redirected to .de/en while trying to view .de/ 🤔

@memic84 In your case I can see (based on the compiled code) that you're not using the latest release, so I can't exclude it already having been fixed.
Your issue differs from the that of @WaldemarEnns, and I can't reproduce your issue with their provided reproduction, could you open a new issue with a minimal reproduction preferably using the latest version? 🙏

Just to make sure - my reproduction and issue is clear?

@WaldemarEnns I'm getting the impression the issue is caused by the Bing/Google crawlers being redirected to .de/en while trying to view .de/ 🤔

Are you sure? IMO the canonical and alternate link should both not exist at the same time and point to the same URL e.g. https://waldemarenns.de - or am I wrong?

The rules for meta tags are quite complex and the documentation is fragmented (I get lost every time I need to refresh my memory).
From what I understand the canonical link should point to the preferred (duplicate/original) URL for the current page, while alternate link should point to all alternates of the current page including the current page itself (see google video for reference at timestamp https://www.youtube.com/watch?v=8ce9jv91beQ&t=588s).
Relevant docs:

https://developers.google.com/search/docs/specialty/international/localized-versions
https://developers.google.com/search/docs/crawling-indexing/canonicalization


UnicornHD driver implementation

Implements the new display.Drawer, enforced at compile time via type assertion.
Uses physic.MegaHertz.
Includes new tests.

Make width and height internal.

Add copyright to tests.

gohci

gohci


Spot mobile gaze v2

Motivation and Context
 This PR refines training of the mobile gaze policy. It ensures the robot is penalized when the base is moving too far away from the object location.
How Has This Been Tested
 Training the mobile gaze policy
Types of changes

[Development] A pull request that add new features to the habitat-lab task and environment codebase. Development Pull Requests must be small (less that 500 lines of code change), have unit testing, very extensive documentation and examples. These are typically new tasks, environments, sensors, etc... The review process for these Pull Request is longer because these changes will be maintained by our core team of developers, so make sure your changes are easy to understand!

Checklist

[x] My code follows the code style of this project.
[ ] I have updated the documentation if required.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[x] I have added tests to cover my changes if required.

Looks good to me! I left some minor naming suggestions.
Do we have test coverage for this feature set?

Hi Michael! Thank you so much for the review! I think the most important feature set in this PR is the ability to set the robot's base orientation and the location using object transformation. I added the test there, thank you!


1.19.3

Do you mean by that, that the 1.19.2 Version also works with the 1.19.3?

Do you mean by that, that the 1.19.2 Version also works with the 1.19.3?

you could try it and see.. if it doesn't then provide a crash report or log

I have tried it. And its works!

I have tried it. And its works!

then I probably not need to add 1.19.3 version numbers on the download pages

Oh, good. I thought that a mod built for 1.19.2 wouldn't work for any other version regardless, I thought fabric didn't allow it.

Although, for software that automatically downloads mods, it won't download it because it thinks it's not compatible. (And some people might not be aware)
So, If you could update the versions somehow or just re upload it for 1.19.3, that would be nice.

oh I usually compile mods with version "1.19.x" and then update the version numbers on the download website
I've done that as this mod works fine 👍


Use set_view() in builtin view operations

Updates the builtin save_view, edit_saved_view_info, and delete_saved_view operators as follows:

save_view: when saving the current view, use ctx.ops.set_view() to update the App to reflect the fact that the current view is now saved
edit_saved_view_info: when renaming the current view, use ctx.ops.set_view() to update the App to reflect the current view's new name
delete_saved_view: when deleting the current view, reset the App to the full dataset

This is consistent with how save_workspace, edit_workspace_info, and delete_workspace work as of https://github.com/voxel51/fiftyone/pull/4902.

@imanjra note in the attached video that ctx.ops.set_view(name=name) doesn't immediately work when name is a newly created view. You must refresh the App in order for it to recognize the new view.
Interestingly, the exactly analogous steps work for ctx.ops.set_spaces(name=name) introduced in https://github.com/voxel51/fiftyone/pull/4902 does work.
Is it an easy fix to tweak the App so that new saved views can be immediately referenced?
https://github.com/user-attachments/assets/c7639f6b-8b33-4ce8-bc7a-5ffedb3f3cbd

@brimoor yah, I believe it may require slight refactor. For workspace, I think it does a trip to backend so it can get latest workspaces but for view it does it all in the frontend. I'll check it out. It should be doable.

Just to clarify, we can't merge this until/unless saved views are updated per this comment. As it currently stands, one gets the error notifications pictured in the video there.


monitor progress

HI @barisozmen thanks for sharing the code for deepaugment
I would like to try this on my dataset.
which value would you recommend to monitor on?
have you considered to implement tensorboard/  tensorboardX in the code for easy validate of the process?
thanks!

Hi @mbenami, thanks for your questions.
I would recommend monitoring reward values for each iteration of training. It's calculated by calculate_reward() function by averaging highest three non-overfitting validation accuracies in the training history. It should increase overall by each iteration (while there are lots of ups and downs), and should saturate after a while (as in below example). You might want to stop iteration when it doesn't increase for 20-30 steps.
Yes, I thought about integrating TensorBoard, but didn't have time. This is something I want to do in the future if I find enough time.


Etcd-server expandins from env variables

Hello,
Please review it. Just single function call changed. It will allow to extend etcd-server from env variables. In our environment, we are creating service for etcd and it's very useful to get etcd-server from env  variables as kubernetes set up these variables.

I signed it!

I signed it!

I signed it!

Issue? Risk level? Milestone? @dchen1107 is this a post 1.0 PR?

Thanks for this, but I am happy to say it is not needed.  We should probably UNDO support for this in the master flag.  Kubelet will already do some level of env expansion, including services, just say:
args:
- --etcd-server=$(MYETCD_SERVICE_HOST):$(MYETCD_SERVICE_PORT)

...in your yaml (or the equiv JSON).  $(...) will be expanded.  Given that, how about we undo the master support instead? :)

@thockin thank you for the explanation, as we have been using kubernetes 0.16.0 it doesn't work for us, but I just tested $(some_var) with 0.18.2 and seems it's working. Will try to upgrade our nodes.


Stereo Output Issue with Blues

I am having an issue with the channel output of numerous acts. Stereo sound generators (i.e., flop@, benjolino@, etc.) open with "2" in the bottom right output count, but will play in mono. Changing the output to "1" will send out stereo audio. Some effects acts (freeverb@ and gverb@ are ones I've tried) don't allow me to change the number to "1", so just stay mono. Wanted to share that, thanks for all the hard work!
PS- Using a Mac on Catalina, with latest Max and build of ppooll

do you use the latest release or the current source code?
in case you use the release please replace it with the current code!

Sorry, yes I've been using the latest code

@Pogslammer try this (using benjolino as example)
having "1" in the "input" boxes does mono over the "2" "output" channels

having "2" in the "input" boxes does stereo over the "2" "output" channels

hope this helps :)
maybe this "input/incoming" box should default to 2?  @klausfilip @chausch

or maybe just update ll.blues state for acts which are stereo...

Thanks so much for the response!
Yes, changing the number to "2" on the input did change the acts to stereo. It would make sense to me to default that to "2"; it's a bit counterintuitive for me to think of inputs on acts in which there is no incoming signal. Thanks again, and I apologize for having absolutely no coding ability to contribute to this amazing project!

Of course, glad it's working.  Still wrapping my head around ll.blues.  No need to apologize-- reporting issues/feedback is a contribution :)

@Pogslammer @the-steech
actually the left number box is not only input buit also defines amount of dsp voices processing.
so a patch with 1 in - out 2 should create 1 voice (plus corresponding input), doubled up to 2 outputs
2 "in" - 1 out should create 2 voices (plus corresponding inputs), mixed down to 1 output.
(you see, thinking in mc does not only apply to mutiple speakers and output channels but general poplyphony!)

iterating over the original question: some acts (like the mentioned freeverb and gverb) are hard-coded for mono or stereo behaviour. meaning that they only accept eg. mono-in/stereo-out or stereo-in/stereo-out our mono-in/out.
that's due to the used externals. there are bpatcher options for ll.blues (visible with tetris) to define mins and max for ins and outs.
in the long run all acts should support mc in ppooll. we are working on this.
reverbs in general are a tricky problem, as they very often deal with either hand-tuned delay lines or cross-channel-feedback. these are things that are difficult to expand …

even more info: an ideal ppooll acts does not use externals but exposes the full source code, allowing us to extend it in the future. something to keep in mind when creating acts …

we really need better documentation 😅

@the-steech to limit in chans you can use "@chans_in min 2 @chans_in max 2" argument for ll.blues

@Pogslammer whats the status on this – do you still have a weird behaviour or was the issue based on misinterpretation of the options?

@chausch yes, I'm pretty sure it was just misinterpreting the options on my end.

great, then i'll close this issue! thanks for the feedback!


Add option inplace to use current folder as project folder

The idea is being able to use Cookiecutter for completing parts of a projects, or for adding content to an existing project (as optional feature)

Codecov Report

Merging #1091 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #1091   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          18      18
  Lines         783     787    +4
======================================
+ Hits          783     787    +4

Impacted Files
Coverage Δ

cookiecutter/main.py
100% <ø> (ø)
:arrow_up:

cookiecutter/cli.py
100% <100%> (ø)
:arrow_up:

cookiecutter/generate.py
100% <100%> (ø)
: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 c88902e...07b0415. Read the comment docs.


Tutorials

Version
Link
Language
Author

5.x
Likes y Dislikes con el paquete Laravel Love
🇪🇸 ES
Carlos Fernandes

Feel free to post your links in comments. They will be added to the first post.

@antonkomarev Please mention that this post not updated by the latest package  updates

@MoatazAbdAlmageed that's why I've added Version column with 5.x value to the table and now we have 7.x in master branch.

Coming from v5, v8 is overwhelmingly more complex. I'm going to stick with it and I find it interesting everything that you can do now. I wish there was a simple tutorial that explained how to do very simple things like like/dislike with v8. Basically, for people who were using v5 and only needed to do simple liking/disliking, and decided to upgrade to v8 and beyond for the sake of staying up-to-date.
I can't find an upgrade guide either but maybe I'm just not looking in the right place

All upgrade guides are in one place: https://github.com/cybercog/laravel-love/blob/master/UPGRADING.md

oops.. I missed that! You should add a link to this from the documentation (if there isn't one already)
Thanks! That is very helpful

Nice catch! I've added Upgrade Guide to the documentation: https://laravel-love.readme.io/v8.0/docs/upgrade-guide


Map access in PostgreSQL do not allow index usage

Environment

Elixir version (elixir -v): doesn't matter
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): PostgreSQL 12, but applies to any PostgreSQL version
Ecto version (mix deps): 3.6.2
Database adapter and version (mix deps): postgrex 0.15.9
Operating system: macOS 11

Current behavior
Assuming that we have table like:
create table(:foos) do
  add :map, :jsonb
end

create index(:foos, [:map], using: :gin)

And query like:
from f in "foos",
  where: f.map["val"] == 1,
  select: f.id

Then the foos_map_index will not be used due to fact that Ecto will use #> operator which is not part of GIN supported operator classes. This mean that this query will be less performant than less idiomatic:
from f in "foos",
  where: fragment("? @> ?", f.map, %{val: 1}),
  select: f.id

Expected behavior
This gotcha should be either documented or we should detect situations like above and translate them to the @> operator if possible (but that still can be surprising sometimes that it doesn't work as expected).

We will document it but perhaps, as per your recent comment in the mailing list, this should be reported to PGSQL too, because if we could do the rewrite, they certainly could too. :)

I do not think that it would be so easy to do rewrite in this case. It is much easier to do in $1 = ANY(q.column) than it is to reason about the (q.column #> $1) = $2, especially as you do not know what is in $1. This mean that planner cannot be ran without knowing what is in $1, which mean that "prepared statement" is no longer "prepared".

Couldn't
(q.column #> $1) = $2

be rewritten to:
(q.column @> json_build_object($1, $2))

?
In any case, I think our biggest issue is that we support both regular json and jsonb fields, and @> is DB specific only. And we don't know the underlying DB field type when emitting the query.

@josevalim that is why I think it could be done in Ecto.Adapters.Postgres to do the rewrite to @>. However I do not know if such "magic" would be welcome in the adapters.
@> is supported by both json and jsonb, the difference is that json field cannot be indexed at all, so there is no problem there. And both #> and @> are DB specific operators, so there is not much difference there.
And, no, it couldn't as it wouldn't work for nested objects. There is no way to transform $1 = '{a,b,c}' and $2 = 1 into '{"a":{"b":{"c":1}}}'::jsonb without doing some complex parsing of $1 and $2.

I don't think it is an issue to rewrite, after all, it is the job of the adapter to match on Elixir expressions and convert them to SQL. The important is to keep the semantics.

And, no, it couldn't as it wouldn't work for nested objects. There is no way to transform $1 = '{a,b,c}' and $2 = 1 into '{"a":{"b":{"c":1}}}'::jsonb without doing some complex parsing of $1 and $2.

I don't think it is a concern, we will never have to parse $1. In our case, we always have a static list of keys, so we do have a good idea of the shape. The issue is that keys can be dynamic. So my previous example:
(q.column #> $1) = $2

The complication is rather $1 needing to work as an integer or a string.

I don't know if we have a precedent for different behaviour per server version, but fwiw pg 14 adds a subscript syntax:

SELECT ('{ "this": { "now": { "works": "in postgres 14!" }}}'::jsonb)['this']['now']['works'];

(https://www.postgresql.org/about/news/postgresql-14-beta-1-released-2213/)
and I'd expect it to be handled by indexes too which may or may not help here.

we will never have to parse $1

Yes, I was telling if we would like to push that to the PostgreSQL planner. Planner/query builder would need to parse $1 to decide how to work with that.
Of course, the arrays in JSON would be pretty hard, as q.column[1] == 1 cannot be translated to q.column @> '[1]'::jsonb as it has different behaviour. The same goes for q.column["foo"] == [1, 2]. So as long as left hand is an array or we use integer index from array then this rewrite cannot be done.
@wojtekmach I am afraid it will not work either as per documentation it will work only if the operator is applied directly on column:

However, the index could not be used for queries like the following, because though the operator ? is indexable, it is not applied directly to the indexed column jdoc:
-- Find documents in which the key "tags" contains key or array element "qui"
SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc -> 'tags' ? 'qui';

It also could be mitigated with better description how to declare indices on JSONB fields, as IIRC:
create index(:foo, ["map #> '{val}'"])

Would allow usage of index in the above case. However I do not know if the DB would be smart enough to see that map->'val' would be the same as map #> '{val}'.

@hauleth PR for the docs are always welcome!

@hauleth Ping. :)

@josevalim only one question - where it should be documented? In Ecto.Query, in Ecto.Migration, Ecto.Adapter.Postgres?


Bluesky => fediverse: some @-mention hrefs not converted

Odd, we should be wrapping Bluesky @-mention tag.hrefs in our own URLs that convert them to AS2, but at least sometimes we're not. Example: https://bsky.brid.gy/convert/ap/at://did:plc:phxtnvotfvp6322ew3rlrvyl/app.bsky.feed.post/3lclqo2v5a225 , visible on<EMAIL_ADDRESS>, note the second tag has href: https://bsky.app/profile/snarfed.org:
{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {"_misskey_quote": "https://misskey-hub.net/ns#_misskey_quote"}
  ],
  "type": "Note",
  "id": "https://bsky.brid.gy/convert/ap/at://did:plc:phxtnvotfvp6322ew3rlrvyl/app.bsky.feed.post/3lclqo2v5a225",
  "url": "https://bsky.brid.gy/r/https://bsky.app/profile/did:plc:phxtnvotfvp6322ew3rlrvyl/post/3lclqo2v5a225",
  "_misskey_quote": "https://threads.net/ap/users/17841400539003309/post/18044832881277913/",
  "attributedTo": "https://bsky.brid.gy/ap/did:plc:phxtnvotfvp6322ew3rlrvyl",
  "content": "
OMG OMG OMG we're able to bridge our threads accounts into Blue sky via federation <a class=\"mention\"<EMAIL_ADDRESS>& <a class=\"mention\"<EMAIL_ADDRESS>https://bsky.app/profile/did:plc:4ghwklnin2mvmam4ditdwv2o/post/3lclod7ptodd2
",
  "contentMap": {
    "en": "OMG OMG OMG we're able to bridge our threads accounts into Blue sky via federation @ap.brid.gy  & @snarfed.org"
  },
  "published": "2024-12-05T22:45:35.222Z",
  "quoteUrl": "https://threads.net/ap/users/17841400539003309/post/18044832881277913/",
  "tag": [
    {
      "href": "https://ap.brid.gy/ap.brid.gy",
      "name"<EMAIL_ADDRESS>      "type": "Mention"
    },
    {
      "href": "https://bsky.app/profile/snarfed.org",
      "name"<EMAIL_ADDRESS>      "type": "Mention"
    },
    {
      "href": "https://threads.net/ap/users/17841400539003309/post/18044832881277913/",
      "mediaType": "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"",
      "name": "RE: https://bsky.app/profile/did:plc:4ghwklnin2mvmam4ditdwv2o/post/3lclod7ptodd2",
      "type": "Link"
    }
  ],
  "to": ["https://www.w3.org/ns/activitystreams#Public"],
  "cc": ["https://bsky.app/profile/snarfed.org"],
}

The contentMap should contain HTML too, that's another bug.
I'll have to check whether Mastodon prefers content and if that breaks auto-translate.

Last I checked Mastodon was happy with this and allowed auto-translate on it.

Yes, the answer are 'Yes' and 'No.' respectively:

https://github.com/mastodon/mastodon/blob/8dc7f8533d1819fe812f96f0f092b3e7086dffe9/app/lib/activitypub/parser/status_parser.rb#L34-L40
https://github.com/mastodon/mastodon/blob/8dc7f8533d1819fe812f96f0f092b3e7086dffe9/app/lib/activitypub/parser/status_parser.rb#L34-L40

Which has some edge cases where it would definitely break down, but it's the safest option while they have no actual multi-language support.
I'll still file a bug because Bridgy Fed's behaviour here would break anything that does have proper post internationalisation.

Hah yes, feel free to ignore JSON comma issues in activities and objects I pasted in here, it's from me manually moving around fields a bit to put type, id, etc near the top.
quoteUrl came from Misskey, it was evidently mistakenly attributed to AS2, as https://www.w3.org/ns/activitystreams#quoteUrl , even though it doesn't actually exist there.
https://github.com/snarfed/bridgy-fed/issues/461#issuecomment-1632984323
https://misskey-hub.net/ns#_misskey_quote
https://github.com/misskey-dev/misskey/issues/8722#issuecomment-1133845284
The same question got asked in https://github.com/snarfed/bridgy-fed/issues/461#issuecomment-2094094198 back when we launched this.
So good point, you're right that quoteUrl is missing from context. It might exist in some context I could add, but I don't know what.
...having said that, to be honest, I run out of patience pretty quickly for fiddling with @context to make overly-strict JSON-LD consumers happy with unknown fields when both JSON-LD and @context are effectively optional in AP. (I know this is a controversial point.) If some fedi software blows up and chokes on any activity with any field that isn't perfectly specified in @context, I don't have a ton of motivation personally to put a lot of effort into satisfying them. Not claiming that's right of me, just describing where my head is at.

Ah right, I remember seeing that aside in their extensions page now, must have forgotten.
It would be nice if they mentioned which other "other ActivityPub programs" require it 😕


Adds ability to search for documentation in repository root and in "./docs/"

This PR introduce the ability to search, build and manage documentation when it's located in the ./docs sub directory.
Please note that it fixes an issue coming from #2 (and currently on master): if docs.Dockerfile is found into ./docs, then the build fails if requirements.txt is not next to it. But if we let mkdocs.yml at the root of the repo (on the same version), it also requires requirements.txt next to it.

First batch of review applied. WDYT @ldez : did I forget something of what we discussed?
This PR should be blocked: there is a regression for generating the menu, I'm working on this.

Broken menu fixed, it was easy:

Added a method to get the value of the docs_dir attribute from mkdocs.yml and returns the full path (parent dir of mkdocs.yml + found value of docs_dirs).
Edited the menu.go to adapt the copy of the JS (and eventual custom CSS) for menu.
And that's all: we don't have to rollback anything in https://github.com/containous/traefik/pull/4475 . This fix does not enforce anything about existing resources: structor adapts itself.

=> Validated on github.com/dduportal/traefik.

OK, latest code works very well (on my fork :) ) for all of these scenarios:

Build with current master (all branches have mkdocs.yml on the root). Even v1.1 works. Menu works for all.
Build with master having mkdocs.yml in ./docs/. Even v1.1 works. Menu works for all.
Build with a branch v15.0 tagged with v15.0.0 and v15.0.1. Even v1.1 works. Menu works for all. v1.7 is seen as v.1.6 today.


luasnip doesn't remove autocomplete placeholder marks after exiting insert mode

GIF of what happens
Basic description is that after accepting an autocompletion luasnip, somehow pressing again tab in insert mode results in the caret jumping back to the autocompletion that was accepted.
I'm using luasnip with basic nvim-cmp integration.
-- Setup Completion
-- See https://github.com/hrsh7th/nvim-cmp#basic-configuration
-- https://github.com/hrsh7th/nvim-cmp/wiki/Example-mappings#luasnip
local has_words_before = function()
  local line, col = unpack(vim.api.nvim_win_get_cursor(0))
  return col ~= 0 and vim.api.nvim_buf_get_lines(0, line - 1, line, true)[1]:sub(col, col):match("%s") == nil
end
local cmp = require'cmp'
local luasnip = require("luasnip")
cmp.setup({
  -- Enable LSP snippets
  snippet = {
    expand = function(args)
      require'luasnip'.lsp_expand(args.body)
    end
  },
  mapping = {
    ['<C-p>'] = cmp.mapping.select_prev_item(),
    ['<C-n>'] = cmp.mapping.select_next_item(),
    -- Add tab support
    ['<C-d>'] = cmp.mapping.scroll_docs(-4),
    ['<C-f>'] = cmp.mapping.scroll_docs(4),
    ['<C-Space>'] = cmp.mapping.complete(),
    ['<C-e>'] = cmp.mapping.close(),
    ['<CR>'] = cmp.mapping.confirm({
      behavior = cmp.ConfirmBehavior.Insert,
      select = true,
    }),
    ["<Tab>"] = cmp.mapping(function(fallback)
      if cmp.visible() then
        cmp.select_next_item()
      elseif luasnip.expand_or_jumpable() then
        luasnip.expand_or_jump()
      elseif has_words_before() then
        cmp.complete()
      else
        fallback()
      end
    end, { "i", "s" }),

    ["<S-Tab>"] = cmp.mapping(function(fallback)
      if cmp.visible() then
        cmp.select_prev_item()
      elseif luasnip.jumpable(-1) then
        luasnip.jump(-1)
      else
        fallback()
      end
    end, { "i", "s" }),
  },

  -- Installed sources
  sources = {
    { name = 'luasnip' },
    { name = 'nvim_lsp' },
    { name = 'buffer' },
    { name = 'path' },
  },
})

Ah, this is just the default-behaviour of luasnip, placeholders are always visited in order (including the $0, which is the one you're jumping back into) (and that does not depend on cursor-movement), so if a snippet is not jumped "through", you'll end up back in it, regardless how the cursor moved.
This can be adjusted by passing a few options to luasnip.setup: region_check_events are the auto-events, on which a check if the cursor is still inside the active snippet is performed. If it is not, the snippet will be jumped "through"/completed/left, so you won't jump back into it.
I'd recommend
luasnip.setup({
  region_check_events = "CursorHold,InsertLeave",
  -- those are for removing deleted snippets, also a common problem
  delete_check_events = "TextChanged,InsertEnter",
})

but you might want to adjust those to fire more regularly.

local luasnip = require("luasnip")
luasnip.config.setup({
    region_check_events = "CursorHold,InsertLeave",
    delete_check_events = "TextChanged,InsertEnter",
})
cmp.setup({
  enabled = function()
    -- disable completion in comments
 ...
});

this doesn't appear to change anything. Even though the author of nvim-cmp sent me back here, the gif doesn't actually trigger a luasnip automcomplete, I think the deal is just in how the <tab> integrates luasnip and nvim-cmp, but the autocomplete that causes this behavior is an nvim-cmp autocomplete.

Appending an ,InsertEnter to region_check_events should do it, if you exactly re-do the gif. I'll check later if that's also the case for me.
Its not an issue with cmp, the problem is that luasnip will always jump through all placeholders/tabstops of a snippet. It does not matter whether the Cursor is moved around, the internal state of which tabstops will be jumped to next is preserved.
Not sure what you mean with Luasnip autocomplete though, the important part is that a snippet is expanded, and luasnip takes care of that.

That seems to have done it.

Is this method still working ?
I have

but it gives the same error, If I move out of the snippets manually and work on something else then the tab brings me back to end of the snippet

Maybe append append TextChangedI to region_check_events? Or CursorMovedI, but that might be too aggressive.. (ie runs that function too often, maybe affecting performance)

For this snippet if I (instead of pressing tab inside the $$ manually leave it and then press tab anywhere else then I always come back to the end of the snippet


Fix eth_hashrate

I’m guessing ethereumjs-util changed it’s intToHex function to add a
hex prefix.

Merged by hand!


./scripts/run_console_local.sh doesn't provide a usable console with make run-local or make run-local-shift

I've been trying to get started with interacting with OLM via the Web UI and have run into issues using minikube / minishift via make run-local and make run-local-shift followed by ./scripts/run_console_local.sh to start the OKD console
Navigating to https://my_ip:8443 only shows the service catalog, nothing else, so I figured that the run_console_local.sh might help.
Once I am successful, I'm expecting that there will be a new section of the UI that I can interact with as shown in the screenshot from README.md ( below).

My actual result is a far less functional UI with an "eternal ellipses" that looks something like this:

Menu buttons are clickable but nothing else much happens on the page.
I am also seeing a bunch of errors resulting from the ./scripts/run_console_local.sh script:
[dwhatley@precision-t operator-lifecycle-manager]$ ./scripts/run_console_local.sh
Using https://<IP_ADDRESS>:8443
2018/08/29 20:40:27 cmd/main: cookies are not secure because base-address is not https!
2018/08/29 20:40:27 cmd/main: running with AUTHENTICATION DISABLED!
2018/08/29 20:40:27 cmd/main: Binding to <IP_ADDRESS>:9000...
2018/08/29 20:40:27 cmd/main: not using TLS
2018/08/29 20:40:29 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/29 20:40:29 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
[...  Perhaps docs need an update as well if this isn't a working method anymore.

Could you post the output from make run-local?

@njhale make run-local works fine, but I still haven't figured out how to get a working OLM web UI.
It's possible that the sequence of commands I'm running is incorrect (make run-local; ./scripts/run_console_local.sh), but I'm expecting to be able to look at an OLM web UI after running these steps.
make run-local
[dwhatley@precision-t operator-lifecycle-manager]$ rm -rf ~/.minikube/

[dwhatley@precision-t operator-lifecycle-manager]$ minikube config set vm-driver kvm2
These changes will take effect upon a minikube delete and then a minikube start

[dwhatley@precision-t operator-lifecycle-manager]$ make run-local
. ./scripts/build_local.sh
Starting local Kubernetes v1.11.1 cluster...
Starting VM...
Downloading Minikube ISO
 160.27 MB / 160.27 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.11.1
Downloading kubelet v1.11.1
Finished Downloading kubeadm v1.11.1
Finished Downloading kubelet v1.11.1
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Switched to context "minikube".
Sending build context to Docker daemon 93.59 MB
Step 1/36 : FROM golang:1.10 as builder
1.10: Pulling from library/golang
55cbf04beb70: Pull complete
1607093a898c: Pull complete
9a8ea045c926: Pull complete
d4eee24d4dac: Pull complete
9c35c9787a2f: Pull complete
1701d74f449a: Pull complete
ed9b85f3273c: Pull complete
Digest: sha256:b38130c9826dc4eff5375f7deeac6dc9c2b9947f194229fac34712f549d03361
Status: Downloaded newer image for golang:1.10
 ---> 5b1054129196
Step 2/36 : LABEL builder=true
 ---> Running in b396221a6117
Removing intermediate container b396221a6117
 ---> a53ebf8a1b06
Step 3/36 : WORKDIR /go/src/github.com/operator-framework/operator-lifecycle-manager
Removing intermediate container b1a7981521bd
 ---> 0610be57eed9
Step 4/36 : RUN curl -L https://github.com/stedolan/jq/releases/download/jq-1.5/jq-linux64 -o /bin/jq
 ---> Running in a035070960e4
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   599    0   599    0     0   4009      0 --:--:-- --:--:-- --:--:--  4047
100 2956k  100 2956k    0     0  2186k      0  0:00:01  0:00:01 --:--:-- 3489k
Removing intermediate container a035070960e4
 ---> 86d609ae99ca
Step 5/36 : RUN chmod +x /bin/jq
 ---> Running in 3228c1acddc3
Removing intermediate container 3228c1acddc3
 ---> cae612d39a06
Step 6/36 : COPY . .
 ---> c556ef3ea639
Step 7/36 : RUN make build-coverage
 ---> Running in 993545ef45ea
building bin/catalog with coverage
building bin/olm with coverage
building bin/servicebroker with coverage
building bin/validator with coverage
Removing intermediate container 993545ef45ea
 ---> 42cdca7725bc
Step 8/36 : RUN go test -c -o /bin/e2e ./test/e2e/...
 ---> Running in 7a9c446b0e97
Removing intermediate container 7a9c446b0e97
 ---> 685b990a80d4
Step 9/36 : FROM alpine:latest as olm
latest: Pulling from library/alpine
8e3ba11ec2a2: Pull complete
Digest: sha256:7043076348bf5040220df6ad703798fd8593a0918d06d3ce30c6c93be117e430
Status: Downloaded newer image for alpine:latest
 ---> 11cd0b38bc3c
Step 10/36 : LABEL olm=true
 ---> Running in 02fe0dd78842
Removing intermediate container 02fe0dd78842
 ---> 68b9786536a1
Step 11/36 : WORKDIR /
Removing intermediate container fc9c094f853d
 ---> ee8a73aa243c
Step 12/36 : COPY --from=builder /go/src/github.com/operator-framework/operator-lifecycle-manager/bin/olm /bin/olm
 ---> cd62576e2819
Step 13/36 : EXPOSE 8080
 ---> Running in 015c55a2d62c
Removing intermediate container 015c55a2d62c
 ---> 06a4ec941662
Step 14/36 : CMD ["/bin/olm"]
 ---> Running in 414bd4554e6d
Removing intermediate container 414bd4554e6d
 ---> df90c78feb6f
Step 15/36 : FROM alpine:latest as catalog
 ---> 11cd0b38bc3c
Step 16/36 : LABEL catalog=true
 ---> Running in 5c12a0bde24a
Removing intermediate container 5c12a0bde24a
 ---> c11ea2c0e391
Step 17/36 : WORKDIR /
Removing intermediate container 9dfa4fd61c03
 ---> 892a54b6a4a3
Step 18/36 : COPY --from=builder /go/src/github.com/operator-framework/operator-lifecycle-manager/bin/catalog /bin/catalog
 ---> 890ad022e17d
Step 19/36 : EXPOSE 8080
 ---> Running in def47e50da91
Removing intermediate container def47e50da91
 ---> eda9aa59173d
Step 20/36 : CMD ["/bin/catalog"]
 ---> Running in aee7b027fd64
Removing intermediate container aee7b027fd64
 ---> ec818db1ff5c
Step 21/36 : FROM alpine:latest as broker
 ---> 11cd0b38bc3c
Step 22/36 : LABEL broker=true
 ---> Running in 545d1354bf82
Removing intermediate container 545d1354bf82
 ---> 4e5286208311
Step 23/36 : WORKDIR /
Removing intermediate container ba85e6e79283
 ---> 0af34ee8fe5e
Step 24/36 : COPY --from=builder /go/src/github.com/operator-framework/operator-lifecycle-manager/bin/servicebroker /bin/servicebroker
 ---> 9c5a89386f52
Step 25/36 : EXPOSE 8080
 ---> Running in a1308abf24a6
Removing intermediate container a1308abf24a6
 ---> f9f817f57206
Step 26/36 : EXPOSE 8005
 ---> Running in c6f6328352e1
Removing intermediate container c6f6328352e1
 ---> b1e4661735cb
Step 27/36 : CMD ["/bin/servicebroker"]
 ---> Running in ea820a631b78
Removing intermediate container ea820a631b78
 ---> c60140bc6280
Step 28/36 : FROM golang:1.10
 ---> 5b1054129196
Step 29/36 : LABEL e2e=true
 ---> Running in 2ef3a1708933
Removing intermediate container 2ef3a1708933
 ---> bf4febe55e16
Step 30/36 : RUN mkdir -p /var/e2e
 ---> Running in ae69e07bd4a9
Removing intermediate container ae69e07bd4a9
 ---> 8c070ba9b3b1
Step 31/36 : WORKDIR /var/e2e
Removing intermediate container 94b4ab5a6e67
 ---> c29ce532f817
Step 32/36 : COPY --from=builder /bin/e2e /bin/e2e
 ---> 8161971c683d
Step 33/36 : COPY --from=builder /bin/jq /bin/jq
 ---> 42f943bd6394
Step 34/36 : COPY ./test/e2e/e2e.sh /var/e2e/e2e.sh
 ---> ef5cda53a466
Step 35/36 : COPY ./test/e2e/tap.jq /var/e2e/tap.jq
 ---> 7d90ea5b802c
Step 36/36 : CMD ["/bin/e2e"]
 ---> Running in dfd2578931d6
Removing intermediate container dfd2578931d6
 ---> 7a764dc95625
Successfully built 7a764dc95625
mkdir -p build/resources
. ./scripts/package-release.sh 1.0.0-local build/resources Documentation/install/local-values.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/08-rh-operators.configmap.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/01-alm-operator.serviceaccount.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/03-clusterserviceversion.crd.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/05-catalogsource.crd.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/06-installplan.crd.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/07-subscription.crd.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/20-aggregated-edit.clusterrole.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/21-aggregated-view.clusterrole.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/02-alm-operator.rolebinding.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/12-alm-operator.deployment.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/13-catalog-operator.deployment.yaml
wrote /tmp/tmp.6ujXW65pvE/chart/olm/templates/10-rh-operators.catalogsource.yaml
. ./scripts/install_local.sh local build/resources
namespace "local" created
serviceaccount "olm-operator-serviceaccount" replaced
clusterrolebinding.rbac.authorization.k8s.io "olm-operator-binding-local" replaced
customresourcedefinition.apiextensions.k8s.io "clusterserviceversions.operators.coreos.com" replaced
customresourcedefinition.apiextensions.k8s.io "catalogsources.operators.coreos.com" replaced
customresourcedefinition.apiextensions.k8s.io "installplans.operators.coreos.com" replaced
customresourcedefinition.apiextensions.k8s.io "subscriptions.operators.coreos.com" replaced
configmap "rh-operators" replaced
catalogsource.operators.coreos.com "rh-operators" replaced
deployment.apps "alm-operator" replaced
deployment.apps "catalog-operator" replaced
clusterrole.rbac.authorization.k8s.io "aggregate-olm-edit" replaced
clusterrole.rbac.authorization.k8s.io "aggregate-olm-view" replaced
Waiting for rollout to finish: 0 of 1 updated replicas are available...
deployment "alm-operator" successfully rolled out
deployment "catalog-operator" successfully rolled out
[dwhatley@precision-t operator-lifecycle-manager]$

./scripts/run_console_local.sh
[dwhatley@precision-t operator-lifecycle-manager]$ ./scripts/run_console_local.sh
Using https://<IP_ADDRESS>:8443
2018/08/30 14:57:10 cmd/main: cookies are not secure because base-address is not https!
2018/08/30 14:57:10 cmd/main: running with AUTHENTICATION DISABLED!
2018/08/30 14:57:10 cmd/main: Binding to <IP_ADDRESS>:9000...
2018/08/30 14:57:10 cmd/main: not using TLS
2018/08/30 14:57:13 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 14:57:13 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 14:57:17 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 14:57:17 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
[... lots more of these errors ...]

My guess is the $KUBECONFIG environment variable is incorrectly set in the terminal session that you are running ./run_console_local.

Perhaps I'm doing something wrong but after setting $KUBECONFIG to the config files created by MiniShift, I am still getting the same result.
[dwhatley@precision-t operator-lifecycle-manager]$ minikube status
minikube: Running
cluster: Running
kubectl: Correctly Configured: pointing to minikube-vm at <IP_ADDRESS>

[dwhatley@precision-t operator-lifecycle-manager]$ cat ~/.kube/config
apiVersion: v1
clusters:
- cluster:
    certificate-authority: /home/dwhatley/.minikube/ca.crt
    server: https://<IP_ADDRESS>:8443
  name: minikube
contexts:
- context:
    cluster: minikube
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    client-certificate: /home/dwhatley/.minikube/client.crt
    client-key: /home/dwhatley/.minikube/client.key

[dwhatley@precision-t operator-lifecycle-manager]$ echo $KUBECONFIG
/home/dwhatley/.kube/config

[dwhatley@precision-t operator-lifecycle-manager]$ kubectl get all --all-namespaces
NAMESPACE     NAME                                    READY     STATUS    RESTARTS   AGE
kube-system   coredns-78fcdf6894-s8ghk                1/1       Running   0          7m
kube-system   coredns-78fcdf6894-vccmr                1/1       Running   0          7m
kube-system   etcd-minikube                           1/1       Running   0          7m
kube-system   kube-addon-manager-minikube             1/1       Running   0          7m
kube-system   kube-apiserver-minikube                 1/1       Running   0          7m
kube-system   kube-controller-manager-minikube        1/1       Running   0          7m
kube-system   kube-proxy-2wzrd                        1/1       Running   0          7m
kube-system   kube-scheduler-minikube                 1/1       Running   0          7m
kube-system   kubernetes-dashboard-6f66c7fc56-7nkr8   1/1       Running   0          7m
kube-system   storage-provisioner                     1/1       Running   0          7m
local         alm-operator-6fb5bf7886-cs9w6           1/1       Running   0          4m
local         catalog-operator-69b586648-bslrt        1/1       Running   0          4m

NAMESPACE     NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
default       kubernetes             ClusterIP   <IP_ADDRESS>       <none>        443/TCP         8m
kube-system   kube-dns               ClusterIP   <IP_ADDRESS>      <none>        53/UDP,53/TCP   8m
kube-system   kubernetes-dashboard   NodePort    <IP_ADDRESS>   <none>        80:30000/TCP    7m

NAMESPACE     NAME         DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                   AGE
kube-system   kube-proxy   1         1         1         1            1           beta.kubernetes.io/arch=amd64   8m

NAMESPACE     NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
kube-system   coredns                2         2         2            2           8m
kube-system   kubernetes-dashboard   1         1         1            1           7m
local         alm-operator           1         1         1            1           4m
local         catalog-operator       1         1         1            1           4m

NAMESPACE     NAME                              DESIRED   CURRENT   READY     AGE
kube-system   coredns-78fcdf6894                2         2         2         7m
kube-system   kubernetes-dashboard-6f66c7fc56   1         1         1         7m
local         alm-operator-6fb5bf7886           1         1         1         4m
local         catalog-operator-69b586648        1         1         1         4m

NAMESPACE   NAME           AGE
local       rh-operators   4m

[dwhatley@precision-t operator-lifecycle-manager]$ ./scripts/run_console_local.sh
Using https://<IP_ADDRESS>:8443
2018/08/30 19:51:47 cmd/main: cookies are not secure because base-address is not https!
2018/08/30 19:51:47 cmd/main: running with AUTHENTICATION DISABLED!
2018/08/30 19:51:47 cmd/main: Binding to <IP_ADDRESS>:9000...
2018/08/30 19:51:47 cmd/main: not using TLS
2018/08/30 19:51:49 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 19:51:49 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 19:51:50 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
2018/08/30 19:51:51 http: proxy error: dial tcp <IP_ADDRESS>:8443: connect: connection refused
[...]

Adding --net=host to the docker run command solved my issue. Looks like there is already a PR up for this.


remove end_user_requirement field from application_plan show command

What's the context of this? has system removed that field from the results?

What's the context of this? has system removed that field from the results?
https://issues.redhat.com/browse/THREESCALE-5542


Need help to install plugin

Hi, @darrenjacoby. I am unable to install the plugin correctly on Bedrock / Sage10. First of all, I try it with Composer, but the macOS PHP version is 7.3.24 (Vagrant box has 7.4.21):
 [InvalidArgumentException]
 Package soberwp / intervention at version dev-master has a PHP requirement in compatible with your PHP version, PHP extensions and Composer version:
     - soberwp / intervention requires php ^ 7.4 | ^ 8.0 which does not match your i nstalled version 7.3.24.
     - soberwp / intervention requires tightenco / collect ^ 8 but it is not present.

Second, I try the wp-cli command. After installation I get this warning:

Warning: require(/srv/www/arte-conocimiento.com/current/web/app/plugins/intervention/dist/composer/../symfony/var-dumper/Resources/functions/dump.php): failed to open stream: No such file or directory in /srv/www/arte-conocimiento.com/current/web/app/plugins/intervention/dist/composer/autoload_real.php on line 69
Fatal error: require(): Failed opening required '/srv/www/arte-conocimiento.com/current/web/app/plugins/intervention/dist/composer/../symfony/var-dumper/Resources/functions/dump.php' (include_path='.:/usr/share/php') in /srv/www/arte-conocimiento.com/current/web/app/plugins/intervention/dist/composer/autoload_real.php on line 69

I'm not sure what the problem is. Could you suggest a diagnosis / solution? Thank you!

Hey @aitormendez,
Looks like the php requirement is not being met. The WP CLI error looks strange, I’ll test that out first thing tomorrow.

Updating macOS PHP fix the composer installation way and the plugin works fine. Big Sur comes with PHP 7.3 by default.

Hey @aitormendez, glad to hear you got it working, thanks for reporting back.


Typo in GAN chapter [version 2022-05-17]

Section 25.1 Introduction:
p832, l21~l22: "function" is repeated twice.
Section 25.2.2 Class probability estimation:
p834, l44: "we cannot evaluate" is repeated twice.

The page numbers follow the printed version.


[ISSUE #8177]optimising update topic from name serve

https://github.com/apache/rocketmq/issues/8177

Let me give you an example, if the normal ip address for dns resolution is <IP_ADDRESS>
After the dns parsing exception, the controller's address should not be updated, should continue to maintain <IP_ADDRESS>, the original return will return an empty List to update the controller address to cause the controller address is empty, this is not reasonable!

@RongtongJin @ferrirW

I'm very sorry that the previous pr https://github.com/apache/rocketmq/issues/6873 was closed by me, so please take a look at this latest pr


Add a11y test to make sure stories are loading

Currently, there isn't a check to make Storybook stories are loading. This means that all tests pass--which is unfortunately what was happening then the original pull request was made. No tests were actually being run, so all the tests passed!

Hi @interactivellama ! Can I have some more info on what's needed? I ran a Lighthouse test and it looks like accessibility is fine but performance is at a 19? But I can't find anything regarding Storybook stories. Not sure if I'm understanding correctly. Thanks!

We use axe-puppeteer in the CI tests to run aXe on all the stories in storybook. Currently if the page never loads in the headless Chrome, then the tests still pass.
In our codebase, aXe passes if no HTML is loaded into headless Chrome. We need to make our CI tests fail if no DOM is loaded.
This task would add a test to make sure that a DOM is loaded that can be tested to make sure there are no false positives.
I'm thinking that just adding a test here that checks for #root might work. Right now if #root doesn't exist then there's no test fail and the a11y test suite "passes" since there are "no a11y errors" when there is web page.
https://github.com/salesforce/design-system-react/blob/master/tests/axe-puppeteer-matcher.js#L58


[CI] Compile Uno with HiGHS

Try to compile Uno_jll.jl with HiGHS_jll.jl.
If it works, we should do the same modification in .github/julia/build_tarballs_yggdrasil.jl.

It worked :)


[ICON REQUEST]

Describe the icon you'd like to be added
TikTok logo icon
Sample icon
Attach any samples/screenshots here.
tiktok.com

@FrissBrot TikTok logo icon has been added to the library.


[Feature] kytos.core.retry decorators

Fixes #214
Description of the change
New kytos.core.retry  module providing common retry decorators for NApps
Release notes

New core kytos.core.retry module provides decorators for retries based on tenacity. The primary use case for this is using to retry certain exceptions from MongoDB and also certain requests. For MongoDB only the basic blocks are provided to simplify maintenance, for a sample on how to use check out this kytos-ng/topology PR 90 that's in flight, the retry module there has been copied to core, once this current PR lands it'll import from kytos core instead.

Appreciated your reviews


Comment on Readme: Naming conventions

please add naming conventions for:

ModuCop
EdgeFarm
.. take care of the capital letters!

Then, also add new naming conventions for:

EdgeFarm.applications
EdgeFarm.devices
EdgeFarm.data


maybe release ?

maybe do 3.60 release and then start merging things for 4.0.0 ?
@stefanpenner

3.6.0 released


feat: support build tags by copying template header over

Closes #625
Excuse the diff, my formatter got a bit trigger happy. I also moved some tests to the txtar format.

Would you be able to stop that formatter from putting args on new lines? It looks like it's optimising for 80 chars. 😁

Sure, I always use gofumpt which is quite opinionated.

Done!


ino build error

when i try to build i get this error?
ino build
Traceback (most recent call last):
File "/usr/local/bin/ino", line 6, in
main()
File "/usr/local/lib/python2.7/dist-packages/ino/runner.py", line 76, in main
args.func(args)
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line 284, in run
self.setup_flags(args)
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line 151, in setup_flags
mcu = '-mmcu=' + board['build']['mcu']
KeyError: 'mcu'

I get this error too
Platform: Arch Linux
Installed via make install from ino git
HEAD=f23ee5cb14edc30ec087d3eab7b301736da42362

From ino clean, which works
[malcolm@tulkas ard]$ ino build
Searching for Board description file (boards.txt) ... found multiple:
  - /usr/share/arduino/hardware/arduino/avr/boards.txt
  - /usr/share/arduino/hardware/arduino/sam/boards.txt
Searching for Arduino lib version file (version.txt) ... /usr/share/arduino/lib/version.txt
Detecting Arduino software version ...  1.6.0 (1.6.0)
Searching for Arduino core library ... /usr/share/arduino/hardware/arduino/avr/cores/arduino
Searching for Arduino variants directory ... /usr/share/arduino/hardware/arduino/avr/variants
Searching for Arduino standard libraries ... /usr/share/arduino/libraries
Searching for make ... /usr/bin/make
Searching for avr-gcc ... /usr/share/arduino/hardware/tools/avr/bin/avr-gcc
Searching for avr-g++ ... /usr/share/arduino/hardware/tools/avr/bin/avr-g++
Searching for avr-ar ... /usr/share/arduino/hardware/tools/avr/bin/avr-ar
Searching for avr-objcopy ... /usr/share/arduino/hardware/tools/avr/bin/avr-objcopy
Traceback (most recent call last):
  File "/usr/local/bin/ino", line 6, in <module>
    main()
  File "/usr/local/lib/python2.7/site-packages/ino/runner.py", line 76, in main
    args.func(args)
  File "/usr/local/lib/python2.7/site-packages/ino/commands/build.py", line 284, in run
    self.setup_flags(args)
  File "/usr/local/lib/python2.7/site-packages/ino/commands/build.py", line 151, in setup_flags
    mcu = '-mmcu=' + board['build']['mcu']
KeyError: 'mcu'

Do you have a  $HOME/.inorc file ? If so, try moving it away and retrying - I suspect the boards.txt it's finding has changed

I fixed this on my own environment by downgrading the Arch AUR package of arduino from 1.6 to 1.0.6

Ok ill try it..

I did not have a .inorc file so i'll try to downgrade arduino.

I downloaded arduino 1.0.6 and installed it under /usr/local/share ( thats where ino looks for it )
Then i tried to do a 'ino build' under my test project, but i got the same error.
its on a raspberry pi running rapsbian..

i have looked at the boards.txt and every board in that file all have a mcu line like this..
mega2560.build.mcu=atmega2560

Looks like this could be the same as my issue #228.  I wrote up a temporary workaround in that post; maybe that might help you.

I cannot downgrade the IDE to 1.0.6 because some specific functions won´t work well on 1.0.X
Is there any solution to this error? here it is.
pi@vfa ~/vfa $ ino build -m mega
Searching for Board description file (boards.txt) ... found multiple:

/usr/share/arduino/hardware/arduino/boards.txt
/usr/share/arduino/hardware/arduino/sam/boards.txt
/usr/share/arduino/hardware/arduino/avr/boards.txt
Searching for Arduino lib version file (version.txt) ... /usr/share/arduino/lib/version.txt
Detecting Arduino software version ...  1.6.0 (2:1.6.0)
Searching for Arduino core library ... /usr/share/arduino/hardware/arduino/avr/cores/arduino
Searching for Arduino variants directory ... /usr/share/arduino/hardware/arduino/avr/variants
Searching for Arduino standard libraries ... /usr/share/arduino/libraries
Searching for make ... /usr/share/arduino/hardware/tools/avr/bin/make
Searching for avr-gcc ... /usr/share/arduino/hardware/tools/avr/bin/avr-gcc
Searching for avr-g++ ... /usr/share/arduino/hardware/tools/avr/bin/avr-g++
Searching for avr-ar ... /usr/share/arduino/hardware/tools/avr/bin/avr-ar
Searching for avr-objcopy ... /usr/share/arduino/hardware/tools/avr/bin/avr-objcopy
Traceback (most recent call last):
File "/usr/local/bin/ino", line 6, in
main()
File "/usr/local/lib/python2.7/dist-packages/ino/runner.py", line 76, in main
args.func(args)
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line 284, in run
self.setup_flags(args)
File "/usr/local/lib/python2.7/dist-packages/ino/commands/build.py", line 151, in setup_flags
mcu = '-mmcu=' + board['build']['mcu']
KeyError: 'mcu'

I know this is a little bit of a late reply, but the problem comes from having spaces in the board file you are using.
This is a problem because the python build file (build.py) is using the exact strings as dictionary keys.
you can remove the white space in the files that ino is pointing to, or you can modify the python build file to remove white space from all of the board related strings.

Remove the space did not solve the problem on Fedora 23


Document release process

Quick notes/thoughts:

Merge 'master' of cert-manager/website into 'release-next'
PR release notes to documentation site
Update version numbers on documentation site
Ensure CI config in jetstack/testing is up to date
Fast forward release branch
Stage the new version with cmrel
Publish the new version with cmrel
Update jetstack/cert-manager-olm: https://github.com/jetstack/cert-manager-olm/pull/7
Trigger build in Red Hat portal
Merge 'release-next' into 'master'
PR to docsearch with the new version/index

/kind documentation

More important than ever I think.
Next release, me and / or @hzhou97 should shadow @meyskens and help document the process.
/assign @meyskens
/priority important-soon

Available here: https://cert-manager.io/docs/contributing/release-process/


feat: add igbinary, var_representation releases

update igbinary with release 3.2.8
update var_representation with release 0.1.4

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HAWQ-1226. fix compile error under gcc 4.8.2

When use gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC), there is a warning:
be-secure.c:323:1: warning: 'report_commerror' defined but not used [-Wunused-function]
 report_commerror(const char *err_msg)
 ^

But it will cause gcc 4.8.2 to make error if we remove this function. So let's keep it as before.

+1

@linwen @huor thanks for review.

+1

Finally found the root cause is not compiler version, but is configure option --with-openssl.
So remove report_commerror() while enable this option at the same time will cause make error.
Fix the similiar problem pls see: #1062
Thanks, @paul-guo-


A07: Settings

Description:
Allow all users/admin of the platform to modify their settings.

All of the information taken at sign up can be accessed in /settings.
Users/Admins will have the same view in settings.
Profile information and password can be changed in /settings.
Users can toggle between light and dark mode
Users can delete their account

Acceptance Criteria:
0. Ensure the database schema structure is created and migration scripts run.

@mo-jaber
Can i be assigned this?


[Feature Request]: Add Contributors Page to Display Project Contributors in the Website

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The contributors page will display the details of the contributors who have contributed to this project.
Use Case
Since this repo is part of a open source program it would be great to have a contributors page
Benefits
No response
Add ScreenShots
Ex  of my previous work -
https://github.com/user-attachments/assets/f54edaa6-ecf7-4260-8fd3-f666af1f4497
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@jeevan10017 @GAVINESHWAR Can I work on this?

@pani2004, not required now please go for another issue


[SPARK-32308][SQL] Move by-name resolution logic of unionByName from API code to analysis phase

What changes were proposed in this pull request?

Currently the by-name resolution logic of unionByName is put in API code. This patch moves the logic to analysis phase.
See https://github.com/apache/spark/pull/28996#discussion_r453460284.
Why are the changes needed?

Logically we should do resolution in analysis phase. This refactoring cleans up API method and makes consistent resolution.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit tests.

Test build #125845 has started for PR 29107 at commit 93c5ea1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30455/
Test PASSed.

Test build #125853 has started for PR 29107 at commit 8e4867a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30463/
Test PASSed.

Test build #125845 has finished for PR 29107 at commit 93c5ea1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/125845/
Test FAILed.

Thank you, @viirya .
cc @cloud-fan

Test build #125853 has finished for PR 29107 at commit 8e4867a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/125853/
Test PASSed.

Test build #126077 has started for PR 29107 at commit c23898e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30690/
Test PASSed.

Test build #126077 has finished for PR 29107 at commit c23898e.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126077/
Test FAILed.

retest this please

Test build #126093 has started for PR 29107 at commit c23898e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30705/
Test PASSed.

Test build #126093 has finished for PR 29107 at commit c23898e.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126093/
Test FAILed.

retest this please

Test build #126112 has started for PR 29107 at commit c23898e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30724/
Test PASSed.

Test build #126112 has finished for PR 29107 at commit c23898e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126112/
Test PASSed.

I just linked the JIRA to SPARK-29358 so it's easier to track the lineage.
Is there already another follow up ticket to make this work for nested structs?

I just linked the JIRA to SPARK-29358 so it's easier to track the lineage.
Is there already another follow up ticket to make this work for nested structs?

Thanks. I don't see an existing follow up ticket for nested structs.

Awesome, I just created https://issues.apache.org/jira/browse/SPARK-32376.
We've implemented a utility to do this before; I'll sync with my team and see if it's easy to port the code over and open a PR for that unless you're already planning on tackling it. Even if so, we're happy to share our test cases.

Thanks @mukulmurthy. I've not worked on it yet. Feel free to open a PR if you are ready to port the code.

Test build #126277 has started for PR 29107 at commit 1839987.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30893/
Test PASSed.

Test build #126277 has finished for PR 29107 at commit 1839987.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126277/
Test PASSed.

Test build #126294 has started for PR 29107 at commit eca8fc6.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30909/
Test PASSed.

Test build #126294 has finished for PR 29107 at commit eca8fc6.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126294/
Test FAILed.

retest this please

Test build #126311 has started for PR 29107 at commit eca8fc6.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30926/
Test PASSed.

Test build #126311 has finished for PR 29107 at commit eca8fc6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126311/
Test PASSed.

Test build #126348 has started for PR 29107 at commit 0381f5d.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30964/
Test PASSed.

Test build #126355 has started for PR 29107 at commit 2ab990e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30971/
Test PASSed.

Test build #126348 has finished for PR 29107 at commit 0381f5d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126348/
Test PASSed.

Test build #126355 has finished for PR 29107 at commit 2ab990e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126355/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31003/
Test PASSed.

Test build #126388 has started for PR 29107 at commit 2a9e1e4.

Test build #126388 has finished for PR 29107 at commit 2a9e1e4.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126388/
Test FAILed.

retest this please

Test build #126417 has started for PR 29107 at commit 2a9e1e4.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/31031/
Test PASSed.

Test build #126417 has finished for PR 29107 at commit 2a9e1e4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/126417/
Test PASSed.

thanks, merging to master!

Thanks for review.


integrate the app mamangement in the source code

Would it be possible to gather the app information in a json or yaml file that developers could manipulate using PR?
{
    "apps": {
        "alert_module": {
           "repository": "turlutut.github.com",
            "name": "toto" ,
            "description": "blablablou",
            "tags": ["tag_list"],
            "instance": "x128",
        }
    }
}

It would avoid us to message the main developers of the website to be deal with minor changes, but simply request PRs review.

Perhaps not all of the information should live within the app. Things like tags are things we'd like to control in one single place, and reorganize as we want. On the other hand, properties like name and description (and their translations) would make perfect sense to keep within the app.


Tooltip misbehaviour when using append-to and scrolling:

Describe the bug
Placing a tooltip in an element other than body using the append-to property causes strange tooltip positioning while scrolling.
To Reproduce
Please see the minimal example:
https://codesandbox.io/s/uiv-bug-342-forked-4t8ic?fontsize=14&hidenavigation=1&theme=dark
Steps to reproduce the behaviour:

Add enough content in the document body so that it can be scrolled.
Create a button with a tooltip.
Alter the append-to of the tooltip to an element which is not body, in this case a div with an ID of append_to_div.
Hover over the button to see the tooltip appear above the button.
Scroll a little bit down, so that the button is still visible, and hover over the button again - the tooltip is now much higher than the button.

Expected behavior
The tooltip element should be appended to the append_to_div div element, not body, but should still be in the correct place regardless of scroll.
Screenshots
No scroll:

With a little scroll:

Versions:

Chrome version 87.
UIV version 1.1.1

Additional context
I have examined the UIV code and can see why this happens. In the method setTooltipPosition the scrollTop of the appendTo container is used instead of the scrollTop of the document. As the container (the empty div) is empty, there is no scrolling and the subsequent calculation is off.

export function setTooltipPosition (tooltip, trigger, placement, auto, appendTo, viewport) {
  if (!isElement(tooltip) || !isElement(trigger)) {
    return
  }
  const isPopover = tooltip && tooltip.className && tooltip.className.indexOf('popover') >= 0
  let containerScrollTop
  let containerScrollLeft
  if (!isExist(appendTo) || appendTo === 'body') {
    const doc = document.documentElement
    containerScrollLeft = (window.pageXOffset || doc.scrollLeft) - (doc.clientLeft || 0)
    containerScrollTop = (window.pageYOffset || doc.scrollTop) - (doc.clientTop || 0)
  } else {
    const container = getElementBySelectorOrRef(appendTo)
    containerScrollLeft = container.scrollLeft
    containerScrollTop = container.scrollTop
  }

I have also tried altering the viewport property to 1) the same append_to_div and 2) directly on body, neither worked.
Motivation
I am trying to append the tooltip to an element which is NOT body because the tooltip code uses removeChild when the tooltip hides. Unfortunately removeChild is quite slow when the parent element (in this case body) has many element, which my project does (it has thousands of <td> elements) - and it can make the page seem quite laggy when tooltips hide. Hence, I am trying to append the tooltip to a different element, but am facing this scrolling issue.
If there is an alternate way to avoid the issue of slow removeChild on body, please let me know because then this scrolling issue won't matter too much for me.
My naive opinion would say that setTooltipPosition needs to consider the document scrolling even with a custom appendTo, but I don't know what other scenarios this would break. I appreciate this might be a difficult thing to alter.

The behaviour was confirmed. However, when you use an append-to option, the scrolling position is decided by that element, it's by design. Consider tooltips inside scrolling modal.
I unserstand you case. maybe it's able to solve by splitting the append-to and position-by behaviour? like:

Add a new prop position-by.
When none of append-to and position-by is given, it will be <body> by default.
When only append-to is given, position-by is the same as append-to.
When position-by is given, tooltips will position by the given element.

This might be able to solve you problem.
But, are you sure that when you append the tooltip to an other element rather than body, your page becomes smooth? It sounds strange. It's your case base on IE? Can you provide a minimal reproduction for that case too? Thank you.

Hi @wxsms thanks for the detailed reply.

But, are you sure that when you append the tooltip to an other element rather than body, your page becomes smooth? It sounds strange. It's your case base on IE? Can you provide a minimal reproduction for that case too? Thank you.

I've tried to make a minimal example for this situation here:
https://codesandbox.io/s/uiv-bug-342-forked-22h6o?file=/src/App.vue
This did not happen directly in codesandbox, I had to copy the code and run it directly in my browser for the issue to occur. If you open the model you might see that the opening stutters a bit. The stutter only occurs in Chrome and Edge, not Firefox, it could also be hardware dependent as well.
What happens is that:

The modal opens.
The tooltip on the button disappears as the modal opens.
As the tooltip disappears, it is removed by calling removeChild on the body.
removeChild on Chrome and Edge is quite slow, causing a recalculation of styles of all elements under the element for which removeChild was called.
Subsequently you can see a slight "stutter" as the modal moves in to position as it opens.

It might be easier to open the Chrome dev tool profiler to analyse this. You'll see in the moment of the stutter, removeFromDom is being called.
In my project I have thousands of <td>s and opening modals via buttons can seem stuttery for this reason. There are other affects elements on the UI affected by a large body element but this was the most noticeable.

Add a new prop position-by.
When none of append-to and position-by is given, it will be  by default.
When only append-to is given, position-by is the same as append-to.
When position-by is given, tooltips will position by the given element.
This might be able to solve you problem.

I'd appreciate this solution, it would be ideal if I can use position-by and append-to can both be used in a single directive, to avoid having refactoring to use tooltip directly.

Consider tooltips inside scrolling modal.

I tried to investigate this but I couldn't find a situation with scrolling modals and tooltips where the default appendTo setting didn't work perfectly already. It seems that the calculations for tooltips-in-modals are fine even with the default append-to of body (which I guess makes sense, as modals are still within body and their position is still relative to body). I attach a minimal example with a scrolling modal, the tooltip seems to behave fine:
https://codesandbox.io/s/uiv-bug-342-forked-4zqhd?file=/src/App.vue
Anyway. I appreciate the solution needs to be backwards compatible regardless, and changing the behaviour of the tooltip positioning with append-to might ruin a few people's day.

I'd appreciate this solution, it would be ideal if position-by and append-to can both be used in a single directive, to avoid refactoring to use tooltip directly.

Do you have any sugguestion to apply one more argument to the tooltip directive? As I see there can be only one argument, and is already taken by append-to.

Available in 1.2.0

Thanks @wxsms . I have tested and it works correctly.
I've submitted a pull request so this can be specified in the directive as an object value. I previously didn't realise this functionality of using an object for the directive value was available before until I saw read the popover documentation.

Thanks @wxsms . I have tested and it works correctly.
I've submitted a pull request so this can be specified in the directive as an object value. I previously didn't realise this functionality of using an object for the directive value was available before until I saw read the popover documentation.


⚠ Bofrost.lu has degraded performance

In e967f17, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1354 ms

Resolved: Bofrost.lu performance has improved in 0bd6d89 after 15 minutes.


[CP] Fix an issue that only one PlatformView can be clipped

Issue Link
https://github.com/flutter/flutter/issues/125620
Commit Hash
727b441
Target
beta
PR Link
https://github.com/flutter/engine/pull/43007
Changelog Description
Fixes an issue on iOS where only one PlatformView can be clipped.
Impacted Users
Some Flutter apps show and clip multiple PlatformViews in a single page.
Impact Description
On iOS, PlatformViews are not clipped correctly, sometimes drawn outside of parent widgets.
See below screenshot (copied from https://github.com/flutter/flutter/issues/127717), the intended behavior is that both PlatformView should be shown in circles.

Workaround
No
Risk
low
Test Coverage
yes
Validation Steps
Repro steps can be found in https://github.com/flutter/flutter/issues/127717

@zanderso could you take a look?

For a beta CP to 3.12 this seems fine to me, but I'm noticing that there was a review requested from @stuartmorgan on the original PR, and I'm wondering if he has any thoughts.

Thanks for reviewing everyone!


public docker image

please publish the images - for example this https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/docker_native_scripts/Dockerfile takes a long time to build

Hi @matti ,
The images are already published. You can retrieve them following https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/examples-gstreamer-plugin.html#examples-gstreamer-plugin-docker-download.
Hope this helps.
-ZH

they are not public and it seems like this one https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/docker_native_scripts/Dockerfile is not published

You need to follow the authentication steps first in the document: https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/examples-gstreamer-plugin.html#examples-gstreamer-plugin-docker-authenticate.
The docker file you referred is built and published as Ubuntu image:
Download the Docker Image for Ubuntu
sudo docker pull<PHONE_NUMBER>75.dkr.ecr.us-west-2.amazonaws.com/kinesis-video-producer-sdk-cpp-amazon-linux:latest

yeah, I did see the authentication - would be more convenient to have fully public images.


Building dll with cuda 10

Great repo!
Have you tried building tensorflow_cc.dll with gpu options?

There is no windows support yet as I cannot test it and I never had the need to do so.

But the tests are using CUDA10
https://github.com/PatWie/tensorflow-cmake/blob/c50be3f097a8d213f235a337eddc9af99671ef2e/.drone.yml#L19-L29


The remove-x-internal decorator does not fully remove internal paths which contain a path-level parameter

Describe the bug
Right now if an x-internal path has a path-level parameter, the path does not get fully removed.
If the path is defined on the operation level (under post), the entire path is removed, as expected.
This might be a regression, we've had such paths before, and have been using the CLI since the beta days to remove them. However, I can't be certain.
To Reproduce
openapi.yaml:
paths:
  '/products/{product_id}/clowncopterize':
    parameters:
      - $ref: '#/components/parameters/ProductID'
    post:
      summary: Clowncopterize product
      description: Clowncopterizes the given product.
      operationId: product-clowncopterize
      x-internal: true
      tags:
        - Products
      responses:
        '204':
          description: OK

Result (redocly bundle openapi.yaml):
paths:
  /products/{product_id}/clowncopterize:
    parameters:
      - $ref: '#/components/parameters/ProductID'

My example uses $ref, but the same behavior is present if the parameter is defined directly.
Repo with full example: https://github.com/bojanz/cli-bug
Expected behavior
The entire path is removed.
Redocly Version(s)
1.19.0
Node.js Version(s)
v20.12.2

Hi @bojanz! I'm not sure it's a bug as the decorator removes exactly what you've told it to remove. Technically, x-internal could be placed on any node, so it'd be quite challenging to figure out the context and clean up it appropriately.
In your case I'd recommend using a custom decorator in addition to the existing one to remove the empty path items. You'll need to create a plugin for that:
my-plugin.js:
module.exports = {
  id: 'test',
  decorators: {
    oas3: {
      'cleanup-paths': () => ({
        Paths: {
          leave: (paths) => {
            for (const pathName in paths) {
              console.log(paths[pathName]);
              // Check if we can remove the path
              if (/* the path is empty... */) {
                delete paths[pathName];
              }
            }
          },
        },
      }),
    },
  },
};

Then use it in redocly.yaml:
plugins:
  - ./my-plugin.js # <- reference the filepath to your plugin here
decorators:
  remove-x-internal: on
  test/cleanup-paths: on # <- use the decorator

Please let me know if that helps.

I totally get the argument for keeping the remove-x-internal decorator simple, since it currently doesn't care about which level it is operating on.
Perhaps it would make sense to add a separate decorator that removes paths with no operations? The two could then be combined to get the expected result.

I’d like to add one, but I don’t have the bandwidth at the moment. If you'd like, you can try adding the decorator yourself here, or contribute to our Cookbook.

This is the decorator that I ended up using:
const id = "internal";
const httpVerbs = ['get', 'head', 'post', 'put', 'patch', 'delete', 'options', 'trace'];

/** @type {import('@redocly/cli').CustomRulesConfig} */
const decorators = {
  oas3: {
    "remove-empty-path": () => ({
      Paths: {
        leave: (paths) => {
          for (const pathName in paths) {
            const foundVerbs = Object.keys(paths[pathName]).filter((k) => httpVerbs.includes(k));
            if (foundVerbs.length == 0) {
              delete paths[pathName];
            }
          }
        },
      },
    }),
  },
};

module.exports = {
  id,
  decorators,
};


multiclock: fix widget field flashing

... when switching to the "dk "clock face.
Closes https://github.com/espruino/BangleApps/issues/1690

Thanks!


Venue homepage: All submissions tap on venue homepage

Let me know if this issue belongs in a different repository.
We discussed as a team that it makes sense to show the All Submissions tab on the venue homepage when all reviewers are readers of all papers, so they have a place to easily access all papers.
Example, https://openreview.net/group?id=supaerodatascience.github.io/SupaeroSDD/2023/Workshop

We need to figure out a way to see the submission readers to decide if we want to show the "All Submissions" tab or not.


Change read_ini.sh to use associative arrays

Allows special characters to be used in section names of settings.ini.

Adds support for configuring extensions like [local-sqlite] properly.

Note that support for the search_limit parameter requires Mopidy-Local-SQLite >= 0.9.2 (run pip install --upgrade Mopidy-Local-SQLite to upgrade)

I've tried and failed to review this on github as their diff tool has made a real mess of things. I'll try to test it out tomorrow but from a quick look it seems this will now accept empty section names. Probably not the end of the world.

Most of the diffs are just as a result of leading space changes on each line (I didn't feel up to trying to match it all by hand). It may be easier to just compare the 'master' and 'head' branches of read_ini.sh on https://github.com/rudimeier/bash_ini_parser as the files are direct copies from that repository.

Rebasing this on /upstream/develop to make merging and testing easier. See https://github.com/woutervanwijk/Pi-MusicBox/pull/253


README.md should contain a better description of the goal we are trying to achieve here

I'm looking at the repo and I don't quite understand the idea:

As I understand it, the problem is that when using an SSL connection something redirects (what? Why? Is this a known issue with using something specific?) request to another domain name (subdomain) and the browser doesn't like that the certificate is issued for the apex domain, i.e., one that does not contain www. For example, example.com redirects to www.example.com.
If the first point is correct, then it means there is at least a certificate already in place containing apex. What's stopping us from issuing a certificate for multiple domain names?
In general, it would be great to describe the scenario.

@mtuktarov looks like a mix of problems. The SSL problem is described here: #6 The lack of documentation is another problem, which I can try to fix in this ticket

@mtuktarov in README, I added a link to redirect.pizza, hope this should help understand what this service is for


[BUG] Constant hours passing by as it loads "Configuring Roblox"

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[x] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
I left it open all night after it updated for me. I woke up this morning to STILL see it configuring. I closed it and tried again and it has yet to open at all. all its shows is the "configuring Roblox" loading screen.

Bloxstrap Log
N/A

Update.

I have updated

https://bloxstraplabs.com/

hm no, I went to the website, and it showed the latest was 2.7.0. thank you I'll try that

hm no, I went to the website, and it showed the latest was 2.7.0. thank you I'll try that

You probably didn't go to one of the 2 official websites.

hm no, I went to the website, and it showed the latest was 2.7.0. thank you I'll try that

Question, what website did you go to?

github, just searched bloxstrap and it showed. but I think I got it now

such a shame that you didn't show a screenshot of the page scrolled up because if you did then it would've showed this notice which would've made this report a lot funner


docs: add yosys setup instructions

SETUP.md has been updated to install yosys
After setting up as instructed, everytime when developer want to runs yosys, s/he  has to simply run the following command
bin/yosys

closes #3073

Coverage remained the same at 81.785% when pulling 938c43dc63297de5110683660485fdc202627315 on ashuvssut:docs/yosys into 673f5edf97f64d3593475e1b00db011b165e75d7 on CircuitVerse:master.

Hi @tachyons @gr455 Can you please review this PR and suggest changes if any

Thanks, Great job


[SMP-1029] Fix left nav for new use an external db topic

Fix left nav for back up and restore
For reviewers, a preview is available.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app