[BUG] QLab ?? Stop function like panic !

Hi! I use Companion to control Qlab. In the new version (v2.1.0) the stop function stops all cues like "panic"
I can find the mistake ? Can anyone help me??
Thanks.. Thomas

The 'Preset' button with the red square (stop) icon is a QLab 'Panic' cue.
Operators would complain 90% of the time that cues were still running and wanted 'STOP EVERYTHING'.
If you want the actual QLab 'Stop', use the Preset button that has 'Stop' as the text.
Or change the action on the red-square button, Delete the 'Panic' action then add a 'Stop' action.

Thanks for answer. I used the preset "stop" (like a red square) with the "stop" action. it doesn't work! action "stop" stopped al cues an "panik" stopped al cues with fade time but I want to stop only one cue.

See my explanation above. You can use the preset that says 'Stop' or change the actions on the button after you copy the preset. You can also use 'Stop Selected' and enter the cue to stop.

sorry. I change this action. that's a wrong workaround?

The 'red square' preset is intentionally a 'Panic' button because most operators expect everything to stop.
The action you changed to is 'Stop' all. There is another action further down called 'Stop Selected' to stop a specific cue.


add check condition for potential invalid date with number or hyphen.

This request further improve on the date parser's ability to recognize invalid date expression strings during date range extraction.  It now filters out strings containing only 1-2 digits number that is neither year, or month of any particular year or date in any particular month of any particular year.

@ninhnguyen could you please review this change?  Thanks.


Impossible to click on Texmaker

Windows Version
Microsoft Windows [version 10.0.22631.2861]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
Texmaker 5.0.3-1build9
Repro Steps
Hello,
I'm trying to use Texmaker on WSL so i'm launching it by typing texmaker in WSL and it opens Texmaker
Expected Behavior
I was expecting to use properly Texmaker
Actual Behavior
I can't click on any button of Texmaker with my mouse but i can navigate with the keyboard.
I have no message in WSL saying there is a problem.
Diagnostic Logs
No response

I can confirm the same behavior. Unfortunately it happens sometimes. After restarting the wsl terminal a few times it works.

Hello, I "fixed" this... When it hapoens, I just press Windows and left key (or right key) then I press Windows and up key. It works for me...

Thx, I will try it. For me a solution is to close it, start Jupiter notebook , that initiates in a new browser (probably starts some graphic drivers ? ), then I close that, then, when I rerun texmaker, I can click.
Your version seems easier!

I've had this happen on an internal app.  The weird thing is that it's very repeatably on specific windows (while other windows in the same app remain responsive).  The whole window frame is completely non-responsive to mouse (can't even drag the window), but keyboard input still works, and pressing Win+Up seems to recover it.  I can't see anything significantly different between windows that work and windows that lock up, but it's extremely consistent so there's presumably something.


Is triton inference server same with TRTIS?

I could not find document about the difference between trtis and triton.
Is there any difference? or not?
If there is a doc, sorry for didn't find it carefully.
please reply that link.

Hi, I guess so, TRTIS was for TensorRT Inference Server but they changed to Triton to avoid confusion since it not only supports TensorRT but many backends. (can't find the exact link about that)

The description was on the master branch README for some time. That readme is now updated but you can still see the TRTIS -> Triton description on the 20.03.1 README. https://github.com/NVIDIA/triton-inference-server/tree/r20.03.1#roadmap


How to test out PX4 firmware modified code without Pixhawk board?

Is there a way to test out PX4 firmware modified code using Gazebo? I would like to see the performance of the quadcopter. I know there is a mavros gazebo simulator. But how can I verified that the code that I modified on Px4 Firmware is working correctly?
Thank you

How about you start with http://dev.px4.io and look through the SITL / Simulation section?


Fix msc old -> new transfer fakaps showing wrongly in sis

010947593

in oodi has been in old msc from 2013 to 2020, then transferred to new msc with studyright until end of 2021
in sis shows only old msc with studyright until 2020
these are both in same studyright element array in oodi, so probably oodi fakap?

looks like ok now regarding new msc programme


Review SpringCloudStreamMicrometerCommonTags in the context of Spring Boot's common tags feature

Addressing the following SCDF request: Issue#12933, Spring Boot has implemented a Common Tags feature that allows to declaratively add Common Tags using just application properties.
Review the current SpringCloudStreamMicrometerCommonTags to see if we can simplify it using the new boot feature.

I can confirm that setting the common tags explicitly:
management.metrics.tags.stream.name=${spring.cloud.dataflow.stream.name:unknown}
management.metrics.tags.application.name=${spring.cloud.dataflow.stream.app.label:unknown}
management.metrics.tags.application.type=${spring.cloud.dataflow.stream.app.type:unknown}
management.metrics.tags.instance.index=${spring.cloud.stream.instanceIndex:0}
management.metrics.tags.application.guid=${spring.cloud.application.guid:unknown}

and having the web actuator endpoints exposed:
management.endpoints.web.exposure.include=health,info,bindings

Removes the needs of stream-applications-micrometer-common dependency


Missing ruby version requirement

Seems like this gem requires Ruby 2.0+, but you don't specify it in the gemspec so it installs into 1.9
Attempting to run simple ruby file with only require 'rbattlenet' results into error
/var/lib/gems/1.9.1/gems/rbattlenet-1.1.0/lib/rbattlenet.rb:1:in `require_relative': /var/lib/gems/1.9.1/gems/rbattlenet-1.1.0/lib/rbattlenet/rbattlenet.rb:37: syntax error, unexpected tLABEL, expecting ')' (SyntaxError)
  def self.authenticate(api_key:)
                                ^
/var/lib/gems/1.9.1/gems/rbattlenet-1.1.0/lib/rbattlenet/rbattlenet.rb:46: syntax error, unexpected tLABEL, expecting ')'
  def self.set_region(region:, locale:)
                             ^
/var/lib/gems/1.9.1/gems/rbattlenet-1.1.0/lib/rbattlenet/rbattlenet.rb:50: syntax error, unexpected keyword_end, expecting $end
        from /var/lib/gems/1.9.1/gems/rbattlenet-1.1.0/lib/rbattlenet.rb:1:in `<top (required)>'
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `require'
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:60:in `rescue in require'
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:35:in `require'
        from test.rb:1:in `<main>'

@jammer thanks for letting me know, i'll have a look into it tomorrow

@jammer this issue should now be resolved, let me know if it crops up again


LaTeX cover design

https://latexdraw.com/stylish-latex-cover-page/

https://latexdraw.com/tikz-cover-pages-gallery/


Error Saving Query - Unable to get property 'html' of undefined or null reference

Can you clarify why I am receiving this error?
I get a different error when using Chrome:

Added a null check to the lines that used an html property. Root cause is probably mismatch in what is returned from different versions of tfs.
Please verify that this fixes for you

Thanks @ostreifel .  I don't see the HTML error on my end but checking in with my colleague to make sure he isn't experiencing it.  Will follow up if this error persists.


InvalidCastException

1;  class Sequential : Evaluate(Value data) ,
2  class DataFrameTrainPredict: Evaluate(object testData)
Sequential .Evaluate invokes DataFrameTrainPredict.Evaluate,and in DataFrameTrainPredict.Evaluate there are "DataFrame data = (DataFrame)testData;" , so  it is a InvalidCastException when Value  is  Cast into DataFrame.

I have checked in the fix. Could you please take latest and try again.

You have  changed "Sequential . Evaluate(Value data)" into "Sequential .Evaluate(DataFrame data)" , Have you considered about "ImgGenTrainPredict.Evaluate(object testData)"?  In "ImgGenTrainPredict.Evaluate(object testData)" ,there is "Value data = (Value)testData;" ,and "ImgGenTrainPredict.Evaluate" may also be invoked by "Sequential . Evaluate"

I am working on standardizing the dataframe. There is another ImageDataFrame which is inherited from the XYFrame class but its not completed yet. If we need to predict with images please wait this week for me to complete the code and test it out. I will setup some examples for you on how to use it.

Thank you


Can't link to changelog

https://warehouse.python.org/project/Sphinx/
Can't give direct link to the changelog.

Duplicate of #932.


Cross compile & publish gem workflow

What
I'm interested in getting a published gem setup on rubygems. I'm curious about what blockers exist.
I've done some preliminary work to get a github action workflow setup. This PR builds & packages the x86_64-linux & aarch64-linux native gems and has a step to publish them to rubygems.
There are 2 jobs in the workflow:

native_gem: which builds and uploads the gem artifacts
publish_gem: which downloads the artifacts from the previous job and publishes them to rubygems.

It will run & list the built artifacts every time but only push on the release trigger.

Publishing
There are a few options for how to trigger publishing the gem. I have it defaulted to run only when there is a new release with a version tag.
if: contains(github.ref, 'refs/tags/v') && github.event_name == "release"

Dependencies
I used the cross-gem action to build the native gem. It's targeted at build rust native extensions but it works on regular C extensions too.
I used the Publish to Rubygems action to manage pushing the gem artifacts to rubygems. This will require you to set RUBYGEMS_API_KEY in this repositories Settings > Secrets > Actions. You can get a key from rubygems in Settings > API KEYS > New API Key.
Questions
I see you have existing releases with the packaged gems already bundled. I wasn't sure on how you built those artifacts but thought an automated action would be nice & simple. It'd be best if you could hook up the workflow you use to build those artifacts into the publish_gem job.
Would an approach using the Fetch Github Release Asset action be more desirable? You could publish releases the same way you do now with prebuilt gems for all architectures and have the action download the native gems and automatically push them to Rubygems.
If that avenue is more interesting I could put up a PR with a workflow (I've been testing them here: https://github.com/DerekStride/test-rb-ts-bindings).

Hello Derek,
I was intending to do publish the gem whenever the project moves under the tree-sitter org.
I already asked @maxbrunsfeld, and he was excited to do it, but unfortunately all I got back was radio silence.
Regardless, I don't think we should be waiting anymore. Let's do it.

Yes I think it's better to do it this way

Closing this PR in favour of #22 which introduces the publish gem workflow.


Add Optional target prop to Link component

Hi 👋🏼 ,
It's me again. ^-^
I'm in a situation where I want to redirect the user to another page in another tab.
To do so, It would mean to set target='_blank' in the rendered styled a tag.
So, I propose to either add an optional target prop (containing a string value) to the Link component and send it in the underlying styled a tag:
<Link target="_blank" href="https://example.com"> Some link opening in the same tab / window </Link>

Or use a boolean prop to switch between _self and _blank:
<Link newTab={true} href="https://example.com"> Some link opening in a new tab / window </Link>

with a logic in the component like:
newTab ? '_blank' : '_self'

What do you think?

Hi 👋🏻 Thanks for the suggestion!
We have purposely chosen not to expose the ability to open links in another tab in the Primer Link component because this behavior can lead to a disruptive and often inaccessible experience. We have been advised that it's preferable to allow the user to make the decision of how they want links to behave, as such we avoid encoding target="_blank" and other similar techniques for opening links a new browser tab/window.
I'm going to close this issue for now, but feel free to write back.

Hi,
Oh ok, that makes sense. 🤔
Thank you. ^-^


media attribute contents are missing in the AST

I might be overlooking something but it seems that media attribute contents of style tags are missing in the AST.
<!DOCTYPE html>

	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Document</title>

I would expect the media contents (min-width: 500px) to be present in the AST.
They are there as part of raws.codeBefore but this is a raw string.
To add support for Document and postcss-html in postcss-preset-env we need to be able to distinguish unconditional from conditional style tags.
Is this something that can be added?
This might need to be part of the PostCSS API, so we don't need to have syntax plugin specific code in postcss-preset-env.

AST
[
  <ref *2> Root {
    raws: {
      semicolon: false,
      after: '\n',
      codeBefore: '<!DOCTYPE html>\n' +
        '\n' +
        '\n' +
        '\t<meta charset="UTF-8">\n' +
        '\t<meta http-equiv="X-UA-Compatible" content="IE=edge">\n' +
        '\t<meta name="viewport" content="width=device-width, initial-scale=1.0">\n' +
        '\t<title>Document</title>\n' +
        '\t\n\t\n\n\n\n\n'
    },
    type: 'root',
    nodes: [ [Rule] ],
    source: {
      input: [Input],
      start: [Object],
      inline: false,
      lang: 'css',
      syntax: [Object]
    },
    lastEach: 1,
    indexes: {},
    document: <ref *1> Document {
      raws: {},
      type: 'document',
      nodes: [Array],
      source: [Object],
      proxyCache: [Circular *1],
      [Symbol(isClean)]: true,
      [Symbol(my)]: true
    },
    proxyCache: [Circular *3],
    [Symbol(isClean)]: false,
    [Symbol(my)]: true
  }
]

Thank you for posting the report.
Hmm... I think it might be difficult to include the media attribute in the node with the current design.
Perhaps we need to separate the attribute information from raws.codeBefore and make stringify work well even if the attribute is edited.

make stringify work well even if the attribute is edited.

We do not have an immediate need to edit the contents.
We do have to know if the style tag is conditional or not.
There currently already exists an inline flag which is true for
 but false for


ASP.NET Core MVC versus Razor pages

Microsoft said: If you choose this tutorial over the Razor Pages version, please leave a note explaining why.
Why?
The Model-View-Controller (MVC) pattern helps make your web APIs and web apps testable.
Seems like a simple decision.

Thanks for the feedback @robertparis. Just want to mention in passing that we've had a topic pertaining to testing RP apps (unit + integration) since early December. It's generally just as easy to set up and test using either dev scenario.
With the new testing package (in 2.1 preview now), things will be even a bit better for 2.1. That work is under review on https://github.com/aspnet/Docs/pull/4832 in case you wanted to take an advance look.
Note that when 2.1 is released, we'll cut the integration testing section from the RP testing topic. The updated integration testing topic (on that PR) focuses on RP; and the integration testing approaches are almost same between MVC and RP. We should 🤞 only need the one integration topic going forward.

Dup of #3889


Word cloud generation can lead to time-out

Search on newspaper title causes time-out when trying to generate wordcloud (too many hits, takes too much time).

We have a hard time limit of 300 seconds for every task that is executed by Celery (a.o. word cloud generation). If we make this 600 seconds this issue will probably be "solved". Would be nice to have a separate error message for this however.


Calendar (google?) for the course

@sciclic had a great idea about posting a calendar of deadlines (originally appearing in this comment). Should consider having this. Perhaps also for class meetings and office hours.

Embed a calendar on a webpage like this: https://ubc-mds.github.io/calendar/ -- Team Sonja?

I created a calendar on Google and exported it into zip format, with proposed deadlines for all submissions: (1) Lecture worksheets (6 total), (2) Mini Project Milestones (3 total), and (3) Team Troubleshooting Assignments (3 total). Please let me know what you think! I kept all deadlines to Fridays (11:59pm I suppose?) and only had to add an extra one on a Monday so that they could all fit, but I think Team Troubleshooting Assignments should be designed to only last 1 hour so that should still meet the 6hr/week I believe.
Please find it here: STAT545A.ical.zip, I think it should automatically download!

Actually, I also included class meetings, but no office hours yet since that hasn't been discussed!

This looks great!

There are 4 Team Troubleshooting assignments listed (not 3), meaning we can delete that Monday deadline. This leaves 2 hours per week on non-worksheet projects. I made this change.
I also added a schedule for the videos to be launched
I added STAT 545B classes

STAT545.ics.zip

Looks great! I think it's ready to go on the website.


Can't set environment variables in terminal

Currently, there is no way of setting the environment variables in the terminal. Which causes you to not be able to run commands such as pwd.  It would be nice to be able to set environment variables before a command. Maybe by returning inside the fetchCommand? Something like:
const wasmTerminal = new WasmTerminal({
    fetchCommand: (commandName) => {
        if (commandName === 'cd') {
            const callbackCommand = async (args) => {

                return {
                    bin: '' // Either the normal WASM binary or a string to output
                    env: [
                        ['$PWD', args[0]]
                    ]
                }
            }

            return callbackCommand
        }
    },
    wasmFs,
});

In the documentation there is an option for fetchCommandFromWAPM but it's only for that function available. (Also the envEntries are not being used https://github.com/wasmerio/wasmer-js/blob/master/packages/wasm-terminal/lib/functions/fetch-command-wapm.ts#L73)

Hello @FranklinWaller !
Thank you for the issue!
I'm glad you brought this up. We made it so you can pass Enviornment variables to @wasmer/wasi, but we hadn't considered it for the shell, because we thought of it is an all-in-one.
Perhaps it would be good to add a new "hook", such as "fetchEnvironmentVariables", that returns an object of the current environment variables to be spread across what we are currently doing? cc @syrusakbary
And considering commands like pwd, a proper file system strategy has been something we've been working towards, with issues like #91 and #95 , this will definitely be something we should handle as well!
Thank you again, glad you brought this up, we'll keep this open as a feature request 😄

With the new @wasmer/sdk package, you can do this using the env argument. For example,
const instance = await pkg.entrypoint.run({
    env: { RUST_LOG: "debug" },
    ...
});


Can we have an incremental id (for internal relations) too?

The package handles UUID greatly but using UUID for everything doesn't make sense.
For example, we can use UUID as external key to requested resource and an incremental id to handle internal requests (and relations). But by disabling $incrementing, we're unable to have both.
So my question is how is it possible to have an incremental id alongside an optimized UUID and actually use them?

You can always add an auto incremented column for internal use, eg. for relations.


Delete .DS_Store

This is a minor cleanup - noticed this file that shouldn't be there.
It is excluded by .gitignore: https://github.com/envoyproxy/envoy/blob/730df5c6cc0d36f417b35b3065f434bf32e95d38/.gitignore#L41
Probably was committed before the exclusion.
.DS_Store is MacOS's internal file serving ada db with folder view options.
This is normally excluded from git.
Signed-off-by: Sergii Tkachenko<EMAIL_ADDRESS>
Commit Message: Delete .DS_Store
Additional Description: .DS_Store is MacOS's internal file serving ada db with folder view options. This is normally excluded from git.
Risk Level: none

Thanks!


[bug] js code was injected multiple times into webview

Describe the bug

tauri command

#[tauri::command]
async fn create_window_finance_yahoo<R: Runtime>(handle: AppHandle<R>) {
    let new_window = tauri::WindowBuilder::new(
        &handle,
        "finance_yahoo", // the unique window label
        tauri::WindowUrl::App("https://finance.yahoo.com/".into()), // the url to load
    )
    .build()
    .unwrap();
}

inject js in my plugin

pub fn plugin_with_options<R: Runtime>(options: Options) -> TauriPlugin<R> {
    let mut plugin_builder = Builder::new("sentry").invoke_handler(generate_handler![
        event,
        breadcrumb,
        create_window_finance_yahoo,
        create_window,
        inject_js_file,
        remove_js_file
    ]);

    if options.javascript.inject {
        println!("plugin_with_options to inject ../dist/inject.min.js");

        plugin_builder = plugin_builder.js_init_script(
            include_str!("../dist/inject.min.js")
                .replace("__DEBUG__", &format!("{}", options.javascript.debug)),
        );
    }

    plugin_builder.build()
}

when the "finance_yahoo" window opened, and check the dev-tool's console:

Reproduction
No response
Expected behavior
inject js into webview only once with multiple iframes.
Platform and versions
❯ cargo tauri info

[✔] Environment
    - OS: Mac OS 12.6.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.73.0-nightly (1065d876c 2023-07-09)
    ✔ Cargo: 1.73.0-nightly (45782b6b8 2023-07-05)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: nightly-x86_64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 16.17.0
    - pnpm: 7.29.1
    - yarn: 1.22.19
    - npm: 8.15.0

[-] Packages
    - tauri [RUST]: 1.4.1
    - tauri-build [RUST]: 1.4.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: ../dist

Stack trace
No response
Additional context
No response

Currently js_init_script seems to trigger a user-script injection at each subframe (such as loading iframe in the page), so if you only need to call it once, you could probably call eval to run the script once after the window is created.


Signals

I am making my own provider and controller (subclassing wsgidav's) to add three features:

realms and users/groups/profiles from database: currently prototype with tinydb. I want to be able to do CRUD operations in real time. Not sure if possible. I'll keep you updated.
signals: for creating notifications, auditing, etc.
rest api: first only for db so in a future a web panel interacting with wsgi to create realms and users/groups/profiles, panel user auth/permission and show notifications, collection history.... A webdav client to operate on files/folders.

This is kind of ambitious, as I am trying to replace Pydio 8 (I don't like the cells/golang movement), let's see where this ends (anybody interested?)
On signals: I think signals should be added at wsgidav level so all the project may benefit of this pattern.
I am using signalslot library and looks enough for this https://pypi.org/project/signalslot/
The idea is adding emitters on all filesystem operations. There are several uses for this: collection/file history. Notifications (email, telegram, web) like "User fuu updated /folder1/file2 2 hours ago".
I am also using signals as callbacks to check "write" permissions. This way I can make a Realm/repository readonly for certain user/group/profile. For "customer portals" for example.
Note: I am using miracle acl library to check for access but this can be keep out from wsgidav project and let dev choose.
To end up, thanks Martin for your software and release 3 works like a charm and looks like a great improvement for devs.

Do you want me to propose a pull request or just upload my code to study usage?
Thanks
Note: I added wsgidav reload on change to include new realms created on database. Also at the same time I am serving a flask app for API, in another thread. Using gevent.pywsgi
#~ from cheroot import wsgi
import gevent
import gevent.monkey
gevent.monkey.patch_all()
from gevent.pywsgi import WSGIServer
from werkzeug.serving import run_with_reloader

import api
import providers
import controllers
import davapp
import logging

logger = logging.getLogger("wsgidav")
logger.addHandler(logging.FileHandler('hello.log'))
logger.propagate = True
logger.setLevel(logging.DEBUG)

from tinydb import TinyDB

realms = TinyDB("db/realms.json")
#~ realms.insert({'name':'principal','uri':'/','path':'/home/gollum/Proyectos/Limbo/limbo/local'})
#~ realms.insert({'name':'second','uri':'/2','path':'/home/gollum/Proyectos/Limbo/limbo/local2'})

users = TinyDB("db/users.json")
#~ users.insert({'username': 'user1', 'password': 'afsasdf','group':'group1',"roles": ['admin',],'realm':'/'})
#~ users.insert({'username': 'user2', 'password': 'asfasf','group':'group2',"roles": ['admin',],'realm':'/'})
#~ users.insert({'username': 'user3', 'password': 'asdfasdf','group':'group2',"roles": ['admin',],'realm':'/2'})

config = {
    "host": "<IP_ADDRESS>",
    "port": 8080,
    "error_printer": {
        "catch_all": True,  # False,
    },
    "verbose": 4,
    "http_authenticator": {
        "accept_basic": False,
        "accept_digest": True,
        "default_to_digest": True,
        },
    "domain_controller": controllers.DomainLimboController(),
    "users_db": users,
    "realms_db": realms,
    }

config['provider_mapping'] = {}
app = davapp.LimboDAVApp(config)

server_args = {
    "bind_addr": (config["host"], config["port"]),
    "wsgi_app": app,
    }

import _thread as thread

def api_thread():
    api_server = WSGIServer((config["host"], config["port"] + 1), api.api)
    api_greenlet = gevent.spawn(api_server.serve_forever())

@run_with_reloader
def serve():
    thread.start_new_thread(api_thread,)
    dav_server = WSGIServer((config["host"], config["port"]), app)
    dav_greenlet = gevent.spawn(dav_server.serve_forever())

serve()

WSGIDAV BROWSER

API

THUNAR gvfs

DJANGO web

client

Do you want me to propose a pull request or just upload my code to study usage?

If you have a fork with a feature branch, we can discuss there. If you want to share your code separately that's fine as well.
I am not sure if I understand enough what parts of it could be part of WsgiDAV (core, demo apps, docs), and what is unrelated built on top of it.

Sorry I am off for a while. I will try to be back in august with some code.

No problem. Please keep in mind that the current way of adding behavior to WsgiDAV is by overriding and deriving.
I generally try to follow There should be one-- and preferably only one --obvious way to do it.
I'd like to understand better why another approach (signals) is required or beneficial to solve the use case, so I am curious with whatever you come up with ;-)


Multiclass segmentation example not working.

I'm running into problems with the multiclass example. It is failing during the model fit generator:
# train model
history = model.fit_generator(
    train_dataloader,
    steps_per_epoch=len(train_dataloader),
    epochs=EPOCHS,
    callbacks=callbacks,
    validation_data=valid_dataloader,
    validation_steps=len(valid_dataloader),
)

---------------------------------------------------------------------------
error                                     Traceback (most recent call last)
<ipython-input-16-859d1e145522> in <module>
      6     callbacks=callbacks,
      7     validation_data=valid_dataloader,
----> 8     validation_steps=len(valid_dataloader),
      9 )

/opt/conda/lib/python3.7/site-packages/keras/legacy/interfaces.py in wrapper(*args, **kwargs)
     89                 warnings.warn('Update your `' + object_name + '` call to the ' +
     90                               'Keras 2 API: ' + signature, stacklevel=2)
---> 91             return func(*args, **kwargs)
     92         wrapper._original_function = func
     93         return wrapper

/opt/conda/lib/python3.7/site-packages/keras/engine/training.py in fit_generator(self, generator, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, validation_freq, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch)
   1730             use_multiprocessing=use_multiprocessing,
   1731             shuffle=shuffle,
-> 1732             initial_epoch=initial_epoch)
   1733
   1734     @interfaces.legacy_generator_methods_support

/opt/conda/lib/python3.7/site-packages/keras/engine/training_generator.py in fit_generator(model, generator, steps_per_epoch, epochs, verbose, callbacks, validation_data, validation_steps, validation_freq, class_weight, max_queue_size, workers, use_multiprocessing, shuffle, initial_epoch)
    183             batch_index = 0
    184             while steps_done < steps_per_epoch:
--> 185                 generator_output = next(output_generator)
    186
    187                 if not hasattr(generator_output, '__len__'):

/opt/conda/lib/python3.7/site-packages/keras/utils/data_utils.py in get(self)
    623         except Exception:
    624             self.stop()
--> 625             six.reraise(*sys.exc_info())
    626
    627

/opt/conda/lib/python3.7/site-packages/six.py in reraise(tp, value, tb)
    701             if value.__traceback__ is not tb:
    702                 raise value.with_traceback(tb)
--> 703             raise value
    704         finally:
    705             value = None

/opt/conda/lib/python3.7/site-packages/keras/utils/data_utils.py in get(self)
    608                 try:
    609                     future = self.queue.get(block=True)
--> 610                     inputs = future.get(timeout=30)
    611                 except mp.TimeoutError:
    612                     idx = future.idx

/opt/conda/lib/python3.7/multiprocessing/pool.py in get(self, timeout)
    655             return self._value
    656         else:
--> 657             raise self._value
    658
    659     def _set(self, i, obj):

/opt/conda/lib/python3.7/multiprocessing/pool.py in worker(inqueue, outqueue, initializer, initargs, maxtasks, wrap_exception)
    119         job, i, func, args, kwds = task
    120         try:
--> 121             result = (True, func(*args, **kwds))
    122         except Exception as e:
    123             if wrap_exception and func is not _helper_reraises_exception:

/opt/conda/lib/python3.7/site-packages/keras/utils/data_utils.py in get_index(uid, i)
    404         The value at index `i`.
    405     """
--> 406     return _SHARED_SEQUENCES[uid][i]
    407
    408

<ipython-input-5-f15eaa6c897e> in __getitem__(self, i)
    115         data = []
    116         for j in range(start, stop):
--> 117             data.append(self.dataset[j])
    118
    119         # transpose list of lists

<ipython-input-5-f15eaa6c897e> in __getitem__(self, i)
     63         # read data
     64         image = cv2.imread(self.images_fps[i])
---> 65         image = cv2.cvtColor(image, cv2.COLOR_BGR2RGB)
     66         mask = cv2.imread(self.masks_fps[i], 0)
     67

error: OpenCV(4.2.0) /io/opencv/modules/imgproc/src/color.cpp:182: error: (-215:Assertion failed) !_src.empty() in function 'cvtColor'

Any idea what could be wrong?

Well based on the error it looks like something might be wrong with your image files. See here.

Looks like it is not able to find your files. (Check your path, image extension etc)

I'm running on a google cloud ai notebook, and the example seems to be downloading the sample images correctly... Any ideas? The images are being displayed in the other parts of the code, it's only when it starts doing the training, and not at the beginning, it happens in the middle of the training.

Are you over-indexing?

Not sure what solved the issue, I re downloaded the image sand this time it works. I'm closing the issue


fix integration tests not deselecting dropdown

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>Unblocks a bunch of current PRs. Noticed that they all failed with the same integration test error.

fair


failed: Error during WebSocket handshake: Unexpected response code: 403

my config
var express = require('express');
var proxy = require('http-proxy-middleware');

var wsProxy = proxy('/', {
	target: 'http://preview-hgpos.behuntergatherer.com',
	changeOrigin: true, // for vhosted sites, changes host header to match to target's host
	ws: true, // enable websocket proxy
	logLevel: 'debug'
})

var app = express()
app.use('/', express.static(__dirname))
app.use(wsProxy) // add the proxy to express

var server = app.listen(8070)
server.on('upgrade', wsProxy.upgrade) // optional: upgrade externally

my terminal
 Proxy created: /  ->  http://preview-hgpos.behuntergatherer.com
[HPM] Subscribed to http-proxy events:  [ 'error', 'close' ]
[DEMO] Server: listening on port 3000
[DEMO] Opening: http://localhost:3000
[HPM] GET /websocket/webSocketIMServer -> http://preview-hgpos.behuntergatherer.com
[HPM] Upgrading to WebSocket

browser console error
WebSocket connection to 'ws://localhost:8070/websocket/webSocketIMServer' failed: Error during WebSocket handshake: Unexpected response code: 403

I need help, Thx!

I am facing another websocket error:
On the console:
kernel.js:461 WebSocket connection to 'wss://mondaytest.datacabinet.systems/jupyterproxy/8888/api/kernels/322058d6-4375-4c4d-97a2-2177d51eb225/channels?session_id=7AEECF5B67EE41B78140847CC99DB1F9' failed: Error during WebSocket handshake: Invalid status line
On the cloud:
[HPM] Upgrading to WebSocket
[HPM] Upgrading to WebSocket
[HPM] Upgrading to WebSocket
[HPM] Error occurred while trying to proxy request /jupyterproxy/8888/api/kernels/322058d6-4375-4c4d-97a2-2177d51eb225/channels?session_id=A6BE4AAC52144BFDA9BF8586893A4A0E from mondaytest.datacabinet.systems to http://localhost:8890 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)10:10:05 PM INFO ip:<IP_ADDRESS> cloud:AWS
{"ResponseMetadata":{"RequestId":"dbc6757d-70e8-11e8-b764-e1cfd7ce25b4"}}

我的问题已经解决，因为后端框架websocket限制了其他域请求，后端把限制去掉就可以连接了

To translate the last comment: “My problem has been solved because the backend framework restricts websocket requests from other domains, and the backend can be connected by removing the restrictions.”

@gauseen @aral could you be more specific on how to remove the backend framework? i have the same handshake issue while using http-proxy-middleware. Thank you!!

@kellywang1234 I’m sorry, I don’t remember what this was about. Perhaps the original poster does (CC @gauseen).
I wonder, based on the last comment, if it was a CORS issue.


Release

Hi @tpetchel why am I having Unauthorized error. I'm following this documentation: https://docs.microsoft.com/en-us/learn/modules/create-multi-stage-pipeline/4-promote-dev


Sidebar categories linking to a doc or category index page

🚀 Feature
Category in docs are only container for subitems (topics). But some help system enable category to be introductory topic to subitems (ie containing text that introduce the subitems or refers to subitems  ie see also links to subtopic1, sub..)
Have you read the Contributing Guidelines on issues?
Yes
Motivation
Interested to use the Docusaurus Help System but before investing in it wan't to know the roadmap
Pitch
It's pretty useful. If you can read the introductory topic, you sometimes don't have to click/navigate to subtopics. It'a a better system than having a first topic (~overview) refering to following topics in a same level appearance > introductory topic has to be a level upper the subtopics..
Example of documentation with introductory topics :
https://www.gatsbyjs.org/docs/deploying-and-hosting/
https://www.innovasys.com/help/hs2019.1/authoringcontent.html
https://markdownmonster.west-wind.com/docs/
Hope my explaination is not too hard to understand..
Thanks to the docusaurus team for their work
Regards, Xavier

+1 to this feature request. I have a case right now where I'm migrating docs over to docusaurus and we've set all nav items to be expanded by default.
themeConfig: {
    sidebarCollapsible: false,
}

Currently if you try clicking on the category item in the nav, nothing happens and it would be helpful to be able to add an optional link to a doc page on the category:
Example where introDoc.md is the doc when you click on the nav item.
{
        type: "category",
        label: "Introduction",
        rootItem: introDoc,
        items: [subdoc1, subdoc2]
}

Some users want this behavior but some other users prefer that the category are just labels and not clickable. If we were to add support for this, we might need to change how the pure categories look, such that they don't look clickable.

@yangshun Is this still a starter issue to be worked on if yes I could maybe give it a shot.

Hey, didn't notice this issue, that also seems related to a more recent one: https://github.com/facebook/docusaurus/issues/3051
@sladyn98 there's ongoing work to be merged on the docs plugin + a few other important refactors I'd like to do.
This won't be time lost to have such a POC of this feature, and would help collect feedback, but just be aware that you might not be able to rebase it easily, and might need to re-open a brand new pull request 🤪

Raw thoughts but here's a possible api:
{
        type: "categoryDoc",
        label: "Introduction",
        id: "introDocId",
        items: [subdoc1, subdoc2]
}

Would render the introDocId doc.
{
        type: "categoryDoc",
        label: "Introduction",
        id: undefined, // on purpose
        items: [subdoc1, subdoc2]
}

Would render an automatically generated table of content of all the inner-tree of this category (we could later see how to make this view more useful by adding additional data to it, maybe a small doc summary or something)

Is there any update on this feature?
Is there any proposed solution for now?
Currently I have a duplicate entry in my sidebar representing the category file. This of course looks a little bit ugly.

This is quite often requested (https://github.com/facebook/docusaurus/issues/3686) so we'll try to find a solution, but it will come after i18n support.
In the meantime, if someone wants to design the API surface and write an exhaustive RFC, so that it is flexible and suit all the use-cases reported, that would help.
The design of this feature is not so straightforward as we are not sure yet how it should behave regarding category collapsing.

Just wanted to add that this is how the kubernetes.io docs work which to me are great. Would love to have this be available (if not default) behavior in docusaurus!

I would definitely like to see this as well. I have encountered the requested functionality several times just today on different sites. In addition to the kubernetes.io docs mentioned by @chrisdostert:

GitHub docs
DITA docs

I like the sidebar behavior of the GitHub docs best (although the k8s docs operate similarly). It hides the sub-articles of the other categories that are not related to doc currently in view. I do not find this behavior confusing or annoying. It makes the sidebar easier to grok.

Thanks for showing some examples. We'll try to find an API that allows all these slightly different UX so that you can choose the one you want.

I like the sidebar behavior of the GitHub docs best (although the k8s docs operate similarly). It hides the sub-articles of the other categories that are not related to doc currently in view. I do not find this behavior confusing or annoying. It makes the sidebar easier to grok.

At the same time it's confusing if the item you click on immediately change position. I guess it's an acceptable tradeoff, but we should probably not enforce this specific UX.

FYI there's an existing PR, and also suggested an API here, curious to have your feedback on it: https://github.com/facebook/docusaurus/pull/3898#issuecomment-742638270

Thanks @slorber.
What I had in mind (which is in line with the examples provided by @ctlajoie, is to have a space to write an overview page for the category that would be linked to when clicking on the category itself.
The PR you linked to seems to be solving a different (if related) problem of how to minimize clicks in a world where you are forced to create an intro page as a subpage.
As a workaround it's a pretty clean one, but not exactly the request here.

@omry , you could create the overview md page, and make the category link to it?
module.exports = {
    docs: [
    {
      type: 'category',
      label: 'Docusaurus',
      link: {type: "doc", id: 'docusaurus-category-overview-doc'}
      items: ['introduction', 'design-principles', 'contributing'],
    },
    // ...
  },
};

Do you see a good reason for this category overview page to not be a regular doc?

I think it should be a regular doc in the sense that I should be able to author it like any other doc.
This is mostly about the user experience: As a user I don't think of the content of the high level overview of a category as something at the same level as the items of the category.
Can you show me an example of what your above overview page looks like?
I have been adding an item to the list as an alternative for an index page. e.g:

Hi, i want to open doc when user click on a category in the sidebar. Looks like it's not supported yet.
Thus i try to create workaround for it by using  first index of category item docs and modify sidebar component with sizzling.
You can see it on my repo https://github.com/nascode/example-docusaurus-v2-sidebar-category-doc

that looks very helpful @nascode , thank you!

@omry what I understand is you want "tutorials" to link to the overview, instead of "Tutorials intro"

But isn't that exactly what I'm proposing to you?
module.exports = {
    docs: [
    {
      type: 'category',
      label: 'Tutorials',
      link: {type: "doc", id: 'tutorials-intro'}
      items: ['basic-tutorial', 'structured-config-tutorial'],
    },
    // ...
  },
};

Can you show me an example of what your above overview page looks like?

Exactly the same as your current intro page, it's just the sidebar that will be different

I tried to modify my sidebar to this and was not successful (I kept getting parsing errors from the sidebar).
Here is my sidebar, Can you help me get on the right track?

@omry the code above is not implemented yet, it's just a possible API design we could use to implement this feature.

Oh, I thought you meant that this was already supported somehow.
I think we are on the same page on the functionality aspects but let me repeat it to be sure:
What I would like is for the Tutorial category, when clicked would do two things:

change the content of the right pane to that of the page "Tutorials intro".
Expand the categories list (to contain the items Basic Tutorial and Structured Configs Tutorial).

This should also work when linking to https://hydra.cc/docs/tutorials/ (currently it results in 404).
Your proposed API design seems sensible to me.
In terms of API design for this, the dict describing the tutorials category above looks good to me.
I am assuming you are aware that currently the top level doc is a dict and not a list for some people (all?) as evident by my sidebar linked above and your suggestion is either a mistake or some other change that is planned:
my sidebar:
module.exports = {
    docs: {
       ...
    }

Your proposal:
module.exports = {
    docs: [
       ...
    ]
}

What I think would be the desired effect is to simply be able to link a category to a markdown file itself
See example https://www.gatsbyjs.com/docs/recipes/
The following comment would not enable that as you would autogenerate some content, but it would be nice if we could define ourselves what to write on the intro/overview page of the cateogry
https://github.com/facebook/docusaurus/issues/2643#issuecomment-661058279
As mentioned by @hsiaoer , it would be helpful to be able to add an optional link to a doc page on the category:
Example where introDoc.md is the doc when you click on the nav item.
{         type: "category",         label: "Introduction",         rootItem: introDoc,         items: [subdoc1, subdoc2] }

@omry yes we agree

This should also work when linking to https://hydra.cc/docs/tutorials/ (currently it results in 404).

You can already use slug: /docs/tutorials on your existing category intro doc for that

I am assuming you are aware that currently the top level doc is a dict and not a list for some people

As documented, there are 2 syntaxes (shorthand/dictionary, expanded/list) but they are equivalent, it's just a shortcut we created. Also you'll have to use the expanded form if you want more options like the one we are discussing here, as the shorthand is just categoryName  -> subItems and can't pass more config

@TomPeirs

What I think would be the desired effect is to simply be able to link a category to a markdown file itself
See example https://www.gatsbyjs.com/docs/recipes/

Yes, this is exactly what my API description above would solve

The following #2643 would not enable that as you would autogenerate some content, but it would be nice if we could define ourselves what to write on the intro/overview page of the category

I don't understand, it's what I suggest  to do: we assign a docId to a category instead of generating automatically the category page when we write such config:

It's your responsibility to write an intro/category doc with id: tutorials-intro here, we won't auto-generate it.
This is very similar to what you suggest, except we didn't  use the same name/api surface (rootItem: "id" replaced by link: {type: "doc", id: "id"}} for extensibility)

Thanks @slorber

You can already use slug: /docs/tutorials on your existing category intro doc for that

Can you point to an example?
This will still be needed once you support sidebar category doc?

The example is just what I gave you, just try this frontmatter and see how
it impacts your doc url
https://v2.docusaurus.io/docs/docs-introduction/
The presence of a doc in a sidebar (either as a regular doc or a caterory
doc) does not affect its url in anyway. Only the slug/id/filename do.
You are free to choose the exact url you want for all your docs using the
slug frontmatter
Le ven. 18 déc. 2020 à 04:31, Omry Yadan<EMAIL_ADDRESS>a
écrit :

Thanks @slorber https://github.com/slorber
You can already use slug: /docs/tutorials on your existing category intro
doc for that

Can you point to an example?
This will still be needed once you support sidebar category doc?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/2643#issuecomment-747846079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PUXZH75YONEJI56WQLSVLEI7ANCNFSM4MOIT2IA
.

Came across this Hashnode doc homepage: https://support.hashnode.com/
I think this kind of UI can be nice for the auto-generated category index:

If there are nested items on a 3rd level we could add a (count) text and if there are too many level2 items we could add some kind of accordion

Styill actual!!

What‘s the progress? Still waiting for it.

This feature is one of the top priorities in my todo-list.
I expect it to be implemented in October.

@slorber Is there a working (but not yet released/merged) version of this feature that we could source ourselves at the danger of incompatibility with future changes? (just as a temporary solution until it's been merged.

There is no easy way to implement this in userland that I can think of.
You can try to assign extra data in the customProps attribute of sidebar items, and provide your own rendering logic using those custom props.
https://docusaurus.io/docs/sidebar#passing-custom-props

Gitbook makes the README.md file within a folder the category index page, which I think we can adopt for auto-generated sidebars as a default value

When editing content heavy websites, I think it would be useful to link automatically to foldr-name.md
This makes the editing process in IDEs such as vs-code much nicer by having folder1.md, folder2.md etc. open side by side rather than 10 tabs with README.md

This makes the editing process in IDEs such as vs-code much nicer by having folder1.md, folder2.md etc. open side by side rather than 10 tabs with README.md

Maybe in the end we shouldn't adopt any default value and just use front matter like category_index: true to turn a page into the index page?

Working POC: https://deploy-preview-5830--docusaurus-2.netlify.app/tests/docs/sidebar/category/tests/
There are some edge-cases not covered yet, and no tests, but it works.
The link:

is a generated category index page (rough styling)
contains categories linking to actual docs using index.md, readme.md or <categoryName>.md convention

The goal for me is to make it easy for you to provide custom styling of the generated category index page, for which you could use the sidebar customProps attributes to provide custom stylings like colors etc... We'll try to do that on the Docusaurus website as an example and to make our site beautiful.
Note a UX edge case that must be considered: some sub-categories of the generated category index won't always have links (ie they'll be like current categories, appearing in white here):

My two cents

should we render lists or cards

Cards. The list is too plain to be attractive & meaningful

should we show the full tree render the direct subitems of the category

Only the direct children. Deeper children can be accessed in other ways

should we render collapsed categories

If we ended up rendering the whole tree, we should render collapsed categories. The default collapsed state is very arbitrary and shouldn't interfere with the statically rendered page.
On how the category link should appear in the sidebar, I prefer

Only highlight text on hover if the category is a link
Clicking on the triangle toggles the category without redirecting
Clicking on the text toggles the category & redirects

Cards. The list is too plain to be attractive & meaningful

Agree

Only the direct children. Deeper children can be accessed in other ways

Agree

Links to test:
deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/getting-started
deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/guides
deploy-preview-5830--docusaurus-2.netlify.app/tests/docs/category/tests
This is not the most beautiful design but is a good first version, what should we change?
What should the cards and layout look like?
Any SVG icons to recommend instead of emojis?

I have these two types of design to offer:

https://docs.luxalgo.com/ (ignore the box shadow part, just the spacing / size etc.)
https://docs.luxalgo.com/lux-algo-premium-indicators/lux-algo#features

I personally would prefer smaller font size & larger padding. Maybe we can also render some description and/or the pages' routes?

I would use this feature. I currently have a page where I have an intro blurb + cards (with title+description) for a section. I just have it as the first item, but I would prefer it as link on the category itself.
Ideally, auto-gen is great, but personally I probably would want to be able to point a category to my own md file for each category where desired, so I can add some text above or whatever, and easily be able to access the data of docs in that category to make my own cards.
ex. https://deephaven.io/core/docs/tutorials/overview/
I was inspired by the gatsby docs:
https://www.gatsbyjs.com/docs/how-to/performance/

https://deephaven.io/core/docs/tutorials/overview/ is the final result I would like, and what I've got currently. I would like it as the category link, rather then the first item under the category, and an easier way to get the data for the cards.
Something to consider with cards, is maybe including the description from the front-matter as well on the card.

@dsmmcken it looks quite complicated to achieve what you want here because your cards are not really following a "normalized structure".
This top part could be achieved by adding some category metadata:

The bottom part is more complex.

The first card leads to a doc, others are liking to headings/anchors... At some point, Docusaurus should be able to understand what it needs to create a card for.
What we'll do automatically (show cards for subcategory items, not headings) might not make sense in all use-cases.

But in the end, we should enable you to build your own index rendering logic and replace our own default logic.
With swizzle, you could be able to build your own rendering logic and create a sidebar category with a custom proprietary syntax, such as:
module.exports = {
  mySidebar: [
    {
      type: "category",
      label: "Tutorials",
      items: ["..."],
      link: { type: "generated-index" },
      customProps: {
        title: "Deephaven Tutorial",
        description: "Learn how Deephaven works",
        subtitle:
          "The goal of this tutorial is to help you create a mental model for how Deephaven works and to introduce you to its capabilities and workflows.",
        intro:
          "You will build analytics and applications with both updating (streaming) and static (batch) data sets, become familiar with the Deephaven IDE experience, apply your Python functions to your data, build a dashboard, create a notebook, and build and launch a stand-alone application. With a bit more time, you’ll then develop a Python client application that uses the API to receive data from your server application.",
        cards: [
          {
            title: "0. Quick Start",
            description:
              "Set up Deephaven in your Docker environment with pre-built images.",
            url: "/core/docs/tutorials/quickstart/"
          },
          {
            title: "1. Ingest static data",
            description:
              "Import CSVs from URLs. Read an example CSV and Parquet file..",
            url: "/core/docs/tutorials/tutorial/#1-ingest-static-data"
          }
          // ... other cards here
        ]
      }
    }
  ]
};

Does it make sense?
Not sure it would be significantly simpler than linking to a custom doc though (or using a index.md or README.md which we'll support).

If you have any feedback to share, on what you see here, now is a good time:

Category linking to doc: https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/api/plugins/
Category linking to automatically generated index: https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/guides

I'm in the process of making this robust, tested and documented, so let me know if you have any UX feedback

That looks pretty good. I think linking to a page, or auto generated will work for most people.
Something I find awkward is not being able to collapse an opened category. If I open a category in the middle and it's giant, then I want a doc in the category after, it is difficult to have to scroll way past it. Should you still be able to collapse a category if it's active, by clicking it? Maybe the icon can performs that action? I don't know, but that bit feels off.
My page having weird links to headings is actually just a temporary solution, we intend them to be separate pages (our code snippets are auto extracted, tested, run, and then automatically inject their output back into the page, but we haven't create the ability to have snippets depend on other pages yet).
If possible, it would be nice if you could also fetch the card data only somehow, where I could have an index page, but then still render cards on it as well.
some-category-doc.md
---
etc
---

my custom intro or whatever markup here

<MyCustomCardComponent cards={some-magic-way-to-have-card-data-here} />

Kinda like how you can add a  component to a page.

Something I find awkward is not being able to collapse an opened category.

Yep, it's actually blocked by an upstream dep: https://github.com/facebookincubator/infima/issues/188 (it's also developed by us anyways, so not so much trouble, just that the fix isn't in place yet)

If possible, it would be nice if you could also fetch the card data only somehow, where I could have an index page, but then still render cards on it as well.

+1. And I do have an idea of how to implement this, let's see if we want to add that in this PR or raise a subsequent PR because this one is getting big

Hi @slorber  and @Josh-Cena
Thank you for working on this interesting feature.
My input would be to make the cards render similar to an admonition, as I find contrast-wise they seem to adhere more to W3C accessibility standards to me.
The hover effect and the cursor handling is nice, but the border shadow hurts my head a little.

My input would be to make the cards render similar to an admonition, as I find contrast-wise they seem to adhere more to W3C accessibility standards to me.

I guess you are talking about the same problem as the box shadow. See https://github.com/facebookincubator/infima/issues/187. I don't think the current design is problematic but certainly we can sharpen the shadow when not hovered.

My input would be to make the cards render similar to an admonition, as I find contrast-wise they seem to adhere more to W3C accessibility standards to me.

I guess you are talking about the same problem as the box shadow. See facebookincubator/infima#187. I don't think the current design is problematic but certainly we can sharpen the shadow when not hovered.

Indeed, that would work.

@Josh-Cena @slorber
One more thing to consider for Card Icons.
The sidebar object can take the following : doc, ref, link, category.
In the netlify preview we can see the icons for a doc and a category, and I was wondering if you considered also Link?
Perhaps we could add a little bit more spacing between the Title and the Icon of a card?
Would there be a possibility to add a customization option to assign those icons/svgs for the card icons?

Perhaps we could add a little bit more spacing between the Title and the Icon of a card?

I personally think the spacing is good...

Would there be a possibility to add a customization option to assign those icons/svgs for the card icons?

If you have differing design ideas you can likely re-implement your own index page through swizzling. (And we will try to make it as convenient as possible.) We would likely not add options for every detail.

In the netlify preview we can see the icons for a doc and a category, and I was wondering if you considered also Link?

Indeed, links, unsurprisingly, have the icon 🔗.

Perhaps we could add a little bit more spacing between the Title and the Icon of a card?

I personally think the spacing is good...

Would there be a possibility to add a customization option to assign those icons/svgs for the card icons?

If you have differing design ideas you can likely re-implement your own index page through swizzling. (And we will try to make it as convenient as possible.) We would likely not add options for every detail.

In the netlify preview we can see the icons for a doc and a category, and I was wondering if you considered also Link?

Indeed, links, unsurprisingly, have the icon 🔗.

Oke thank you ;-) seems that everything is considered.

Yes, we'll allow collapsing a category
External links have a different icon, this can be seen here: https://deploy-preview-5830--docusaurus-2.netlify.app/tests/docs/category/tests/

If possible, it would be nice if you could also fetch the card data only somehow, where I could have an index page, but then still render cards on it as well.

I don't understand what this means sorry 😅

Perhaps we could add a little bit more spacing between the Title and the Icon of a card?
Would there be a possibility to add a customization option to assign those icons/svgs for the card icons?

We'll likely improve the design and add customization options later. Here I'm mostly focusing on the initial MVP with the UX and a good extensible public API that we can improve later.
Note that these theme components are well encapsulated and easy to customize with a swizzle.

Thanks for your feedback, which is mostly about design and "shortcut" options, we can improve all that incrementally from the current state later in subsequent PRs, and in the meantime using swizzle is likely a good enough workaround until we figure out the most wanted customization apis.

If possible, it would be nice if you could also fetch the card data only somehow, where I could have an index page, but then still render cards on it as well.

@slorber By that he means, you have a normal doc page as index page, but inject the category items in it as JSON so it can be rendered somewhere in the middle of the page, kind of like the TOCInline where we have a global toc export to do this.
My idea would be to inject this in MDXProvider

Oh I see, something like this?

It's already technically possible atm using hooks in the MDX doc, but probably not with the most intuitive API. We can figure out later how to add MDX shortcodes for that.

PR and UX ready for a final review!
Unless there's any pushback, this is going to be merged tomorrow!
https://github.com/facebook/docusaurus/pull/5830

Test URLs:

https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/getting-started
https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/guides
https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/markdown-features/
https://deploy-preview-5830--docusaurus-2.netlify.app/tests/docs/category/tests

Docs:

Category links (doc, generated-index)
Category index.md convention
docCategoryGeneratedIndexComponent option

Please share your last feedback asap

Is it easy to change/remove the icons, or would I have to swizzle the component for that?

Is it easy to change/remove the icons, or would I have to swizzle the component for that?

@slorber Is it possible to popularize the idea of CSS ::before pseudoelements for these icons?

I’ve been following the progress of this for a while now, and I love how this is forming. Really great work!
Request:
Can you close the Table of Contents panel when tapping the Category item (that has a page) on the mobile version? Currently, that panel stays open which makes it seem like nothing has occurred.

Is it easy to change/remove the icons, or would I have to swizzle the component for that?

@slorber Is it possible to popularize the idea of CSS ::before pseudoelements for these icons?

For now you can swizzle the DocCard component
We don't have yet a good way to manage theme icons, we'll try to normalize how we handle icons in themes as part of https://github.com/facebook/docusaurus/issues/5865 and make sure that overriding an icon is consistent for all the existing use-cases of the theme.
If you have a better icon/design we can also improve our current design. Feel free to override DocCard in userland for now, show us the result, and eventually if the design is better we can make it the default later.

Can you close the Table of Contents panel when tapping the Category item (that has a page) on the mobile version? Currently, that panel stays open which makes it seem like nothing has occurred.

Yes, also noticed that ;) this has been fixed

This has been published in canary (0.0.0-4241) and scheduled for a release next week
Please give it a try and tell us if it works fine ;)

Hey guys 😄
I've been struggling to find the option to enable this?
I didn't want to bother reading through all these comments, therefore I am asking :)
I also couldn't find anything related to it in your docs

@SivertGullbergHansen

https://docusaurus.io/docs/sidebar/items#category-link
https://docusaurus.io/docs/sidebar/autogenerated#category-item-metadata

If you can read the introductory topic, you sometimes don't have to click/navigate to subtopics. It'a a better system than having a first topic (~overview) refering to following topics in a same level appearance > introductory topic has to be a level upper the subtopics.. Example of documentation with introductory topics : https://www.gatsbyjs.org/docs/deploying-and-hosting/

Interestingly, Gatsby actually moved away from this style. My guess would be that it's because readers might miss that they can click on the category sidebar to read info. Readers might sometimes expand the category using the arrow instead, thereby missing crucial introductory info. This can also happen if the reader opens a category subpage from an external link, in which case it's unlikely they'll know to click the category in the sidebar since it's also expanded.
I'd argue that a better approach would be to make any clicks to the category redirect the reader to the intro subpage. That way, it's still a quick experience (same # of clicks), but makes the intro information explicit. I've created https://github.com/facebook/docusaurus/issues/8833 to add support for this :)


Falco exporter does not work if we have Syscall + K8S plugin

I actually have inside my cluster 2 releases of falco :

1 that deploy a daemonset of falco on every node
1 other that deploy a unique replicaset of falco-k8saudit-eks plugin to analyze my EKS Cloudwatch logs

I've deployed falco-exporter to export some prometheus metrics to Grafana but this falco-exporter only export the data from the base falco or only from the k8s plugin falco so I always miss some informations.

The fact that we have a "double" falco install seems to fail inside falco-exporter

Expected behaviour
Deploy 1 daemonset of falco et 1 replicaset of falco k8s audit plugin.
Port forward the falco exporter pod which is on the same node as the falco k8saudit one.
See that you only have the k8saudit values or the base falco values.

Get the value of the base falco AND the k8saudit falco inside the falco-exporter on the same node to no miss data

Environment

Falco version:

System info: 3.6.2

Cloud provider or hardware configuration: AWS
OS: Ubuntu 22.04

Installation method: Kubernetes (Helm)

Additional context

Hi @afreyermuth98 falco-exporter can't handle multiple sources at once. It will connect to the available unix:///run/falco/falco.sock socket. In the node where there are two instances of falco only one of the unix sockets will be available since they later instance will overwrite the existing unix socket.
To make it work in your scenario, you will need to change the path where the falco unix socket is exposed and deploy a new instance for each k8s.
Anyway i think the best approach would be to deploy falco-exporter as a sidecar.

You'll have as much falco-exporter as falco deployments. In your scenario you will have:

falco with syscalls deployed as a deamonset + falco-exporter as daemonset configured to attach to the UNIX sockets exposed by the falco falco pods of the daemonset;
falco with k8saudit deployed as a deployment + falco-exports as deployment contifured to attach to the UNIX sockets exposed by the falco pod of the deployment. Rempember that the falco pod and falco-exporter pod need to be run on the same node.

The best approach would be to deploy falco-exporter as a sidecar. Unfortunately the current charts does not support this configuration.

Yes I agree with you !
@alacuku Unfortunately, it seems that we cannot deploy falco-exporter as a deployment :'(

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Version => 0.4.1

w00t.  lgtm.

One is perhaps a little too enthused? Now that the Travis of Integration Continuous has finished, can we proudly confirm our progress.


Polyfills

Super happy to see this at Stage 3! 🎉
I noticed there's a polyfill under development at es-shims/RegExp.escape and available via NPM, and I've also made my own lightweight one: lionel-rowe/regexp-escape-polyfill. I'll probably add it to JSR and/or NPM at some point, but for now it's just a GitHub repo.
Benchmarks/comparison:

Name
Time (avg)
Iter/s
Bundle size (minified)
Details

lionel-rowe/regexp-escape-polyfill
1.269 µs
787,546.7
793 B
Modern JS/ESM only, with TS support; aims for full compatibility with the spec (verified via test262) but may differ on implementation details.

es-shims/RegExp.escape
12.837 µs
77,899.8
84.2 kB
Aims for ES3 compliance; written with CJS modules; more closely follows the implementation details of the algorithm in the spec.

Anyway, feel free to add this info to the README etc.

https://github.com/zloirock/core-js#regexp-escaping

Thanks @zloirock ! Added that to the table

I don't know about perf, but the bundle size for core-js/actual/regexp/escape definetly not 88kB -) https://bundlejs.com/?q=core-js%2Factual%2Fregexp%2Fescape&treeshake=[*]

I don't know about perf, but the bundle size for core-js(-pure)/actual/regexp/escape definitely not 88kB -)
https://bundlejs.com/?q=core-js-pure%2Factual%2Fregexp%2Fescape&treeshake=[*]
https://bundlejs.com/?q=core-js%2Factual%2Fregexp%2Fescape&treeshake=[*]

Gotta admit I was a little perplexed at how high the numbers looked for es-shims/RegExp.escape and zloirock/core-js. Methodology I'm using is fetching the ESM version via esm.sh then bundling and minifying with esbuild (which in theory should tree shake correctly for ESM bundling). No gzip. Still, 12.8 kB is a long way off of 88 kB, so I guess either esbuild isn't tree shaking properly, esm.sh is adding a massive amount of cruft, or there's a bug in my code.

(Computing bundle size numbers absent a complete application is always going to be inaccurate due to optimizations and deduplication, and displaying them makes it really easy for people to draw inaccurate conclusions in both directions.)
Thanks! I'll add es-shims and core-js to the readme; when you've published yours to npm, I'd love a PR to add it as well.


fix: handle deprecations in third-party libraries

Summary of Changes
Migrate our code, so it no longer uses deprecated API elements of third-party libraries.

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

v0.29.0
GitHub release

Your semantic-release bot :package::rocket:


Project Template Cleanup: Issue #478

Fix for issue #478.
Also remove unnecessary 2017 project templates.

PTAL


style guide: avoid non-optional Options

This suggestion was not discussed anywhere else first, this PR is meant to be the place for objections/discussion/corrections/support.

Great change :)


Create a hierarchical policy service

We want to be able to apply policies to a data type rather than adding the same policies to potentially 1000's of resources of the same data type.
The initial idea would be to have 2 tables:

The first would be a mapping of type to policies (resource level policy, record level policy)
The second would be a mapping of resource to policies (resource level policy, record level policy)

To find the policies for a resource, you would first get the relevant (resource/record level) policy for that resource, then work your way up the resource parentage chain and then you would get the relevant policy for the type. This way the child resource policies have precedence over the parents, and the parents have precedence over the data type.

merged into develop


fix: skip rewriting auth header

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update "TorrentGalaxy" separator

Update "TorrentGalaxy" separator

For this provider it does not matter, they treat "+" and "%20" properly.

For this provider it does not matter, they treat "+" and "%20" properly.


mermaid.init() on hidden items is not displaying labels

When mermaid.init() was called and the hidden items (they were placed in a collapsible body and hide on default) did not display the label correctly, see the picture bellow (very appreciate for any solutions or bug fix):

Hi,
which browser are you using? Looks like this not from command-line.
are you using the latest mermaid? what's your html and css looks like?
It's likely browser/css issue. i cannot reproduce it. so asking.
Thanks!

Hi,
which browser are you using? Looks like this not from command-line.
are you using the latest mermaid? what's your html and css looks like?
It's likely browser/css issue. i cannot reproduce it. so asking.
Thanks!

Thanks. I can see it now, with the above sample html and a

not working with bootstrap 3 tabs also
same efffect

I managed to get this working for a mermaid flow diagram not of the first tab.
The code is here:

Mermaid starts on load anyway, so I set start on load to false. I turned on logging so that I could see what it was doing.
I then set up a click event on the tab that contained the mermaid drawing. So when the tab was clicked then I set mermaid back to start on load true. I then found that I had to call mermaid.init() to finish off the drawing - it now works fine.
My plan if I have a mermaid drawing on more than 1 tab is to change the class of the div to something other than mermaid and then change it to mermaid as the first action when clicking on the tab.


Analysis: sort modes by brightness

tm512 — Today at 10:23 AM

maybe there's some way to calculate how bright a particular mode is, then sorting them by brightness? so like with the major scale as input, you'd get lydian, major, then mixolydian, rather than major, dorian, phrygian

Use the computed bright percentage and implement a tie-breaker for sorting equally-bright-but-distinct modes.

Time estimate: 2 hours


Revert "prevent accidental calls to io.exit when asserts are active."

Reverts flutter/flutter#46210
Breaks test on postsubmit:
01:10 +30 ~2 -1: test/analyze-sample-code_test.dart: analyze-sample-code [E]
  Expected: [
              'known_broken_documentation.dart:30:9: new Opacity(',
              '>>> Unnecessary new keyword (unnecessary_new)',
              'known_broken_documentation.dart:62:9: new Opacity(',
              '>>> Unnecessary new keyword (unnecessary_new)',
              '',
              'Found 1 sample code errors.',
              ''
            ]
    Actual: [
              'Unhandled exception:',
              'Cannot analyze dartdocs; unexpected error output:',
              '[17 issues found. (ran in 14.1s), Unhandled exception:, \'package:flutter_tools/src/base/io.dart\': Failed assertion: line 108 pos 5: \'_exitFunction != io.exit || io.Platform.environment[\'FLUTTER_TEST\'] != null\': io.exit was called with assertions active. If this is an integration test, ensure that the environment variable FLUTTER_TEST is set to a non-null String., #0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:42:39), #1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:38:5), #2      exit (package:flutter_tools/src/base/io.dart:108:5), #3      _exit.<anonymous closure> (package:flutter_tools/runner.dart:262:7), #4      _rootRun (dart:async/zone.dart:1122:38), #5      _CustomZone.run (dart:async/zone.dart:1023:19), #6      _CustomZone.runGuarded (dart:async/zone.dart:925:7), #7      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23), #8      _rootRun (dart:async/zone.dart:1126:13), #9      _CustomZone.run (dart:async/zone.dart:1023:19), #10     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:949:23), #11     Timer._createTimer.<anonymous closure> (dart:async-patch/timer_patch.dart:23:15), #12     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:384:19), #13     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418:5), #14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)]',
              '#0      SampleChecker._runAnalyzer (file:///tmp/flutter%20sdk/dev/bots/analyze-sample-code.dart:579:7)',
              '#1      SampleChecker._analyze (file:///tmp/flutter%20sdk/dev/bots/analyze-sample-code.dart:598:33)',
              '#2      SampleChecker.checkSamples (file:///tmp/flutter%20sdk/dev/bots/analyze-sample-code.dart:251:16)',
              '#3      main (file:///tmp/flutter%20sdk/dev/bots/analyze-sample-code.dart:114:7)',
              '#4      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:305:32)',
              '#5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)',
              ''
            ]
     Which: was 'Unhandled exception:' instead of 'known_broken_documentation.dart:30:9: new Opacity(' at location [0]
  package:test_api                         expect
  test/analyze-sample-code_test.dart 19:5  main.<fn>
01:10 +30 ~2 -1: Some tests failed.
▌21:07:41▐ ELAPSED TIME: 1min 39.078s for ../../bin/cache/dart-sdk/bin/pub run test -rcompact -j3 --no-color in dev/bots
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ERROR: Last command exited with 1 (expected: zero).
Command: ../../bin/cache/dart-sdk/bin/pub run test -rcompact -j3 --no-color
Relative working directory: dev/bots
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TBR @zanderso

lgtm


istio.io tasks/traffic-management/request-routing/test.sh test fails on the main branch

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
Trying to move the istio.io tests from the release-1.8 branch to main and the test now fails. The tail end of the log (https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio.io/8562/doc.test.profile_default_istio.io/1334602913711919104/artifacts/tests-setup-profile-default-255/TestDocs/tasks/traffic-management/request-routing/test.sh/test.sh/_test_context/test.sh_output.txt):
serviceaccount/bookinfo-productpage created
deployment.apps/productpage-v1 created
gateway.networking.istio.io/bookinfo-gateway created
virtualservice.networking.istio.io/bookinfo created
destinationrule.networking.istio.io/productpage created
destinationrule.networking.istio.io/reviews created
destinationrule.networking.istio.io/ratings created
destinationrule.networking.istio.io/details created
Waiting for deployment "productpage-v1" rollout to finish: 0 of 1 updated replicas are available...
deployment "productpage-v1" successfully rolled out
deployment "details-v1" successfully rolled out
deployment "ratings-v1" successfully rolled out
deployment "reviews-v1" successfully rolled out
Waiting for deployment "reviews-v2" rollout to finish: 0 of 1 updated replicas are available...
deployment "reviews-v2" successfully rolled out
deployment "reviews-v3" successfully rolled out
virtualservice.networking.istio.io/productpage created
virtualservice.networking.istio.io/reviews created
virtualservice.networking.istio.io/ratings created
virtualservice.networking.istio.io/details created
Duration: 0 seconds
Duration: 0 seconds
Duration: 0 seconds
Duration: 0 seconds
virtualservice.networking.istio.io/reviews configured
Duration: 0 seconds
VERIFY FAILED get_bookinfo_productpage_jason (timeout after 120s):
received:
"  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   237  100   207  100    30  29571   4285 --:--:-- --:--:-- --:--:-- 33857
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>Redirecting...</title>

Redirecting...

You should be redirected automatically to target URL: .  If not click the link.  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>Redirecting...</title>

Redirecting...

You should be redirected automatically to target URL: .  If not click the link.
100   207  100   207    0     0  34500      0 --:--:-- --:--:-- --:--:-- 34500
<!DOCTYPE html>

    <title>Simple Bookstore App</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">

<link rel="stylesheet" href="static/bootstrap/css/bootstrap.min.css">

<link rel="stylesheet" href="static/bootstrap/css/bootstrap-theme.min.css">

      BookInfo Sample

    <button type="button" class="btn btn-default navbar-btn navbar-right" data-toggle="modal" href="#login-modal">Sign
      in</button>

        <button type="button" class="close" data-dismiss="modal">×</button>

Please sign in

        <form method="post" action='login' name="login_form">

<input type="text" class="form-control" name="username" id="username" placeholder="User Name">

<input type="password" class="form-control" name="passwd" placeholder="Password">

            <button type="submit" class="btn btn-primary">Sign in</button>
            <button type="button" class="btn btn-default" data-dismiss="modal">Cancel</button>

        </form>

The Comedy of Errors

Summary: Wikipedia Summary: The Comedy of Errors is one of William Shakespeare's early plays. It is his shortest and one of his most farcical comedies, with a major part of the humour coming from slapstick and mistaken identity, in addition to puns and word play.

Book Details

Type:
paperback

Pages:
200

Publisher:
PublisherA

Language:
English

ISBN-10:
1234567890

ISBN-13:
123-1234567890

Book Reviews

An extremely entertaining play by Shakespeare. The slapstick humour is refreshing!

        Reviewer1

Absolutely fun and entertaining. The play lacks thematic depth when compared to other plays by Shakespeare.

        Reviewer2

"
expected:
"glyphicon glyphicon-star"

[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Tests should pass
Steps to reproduce the bug
Run the istio.io test or try and follow the instructions on the content/en/docs/tasks/traffic-management/request-routing/index.md page.
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
main branch
How was Istio installed?
test framework
Environment where the bug was observed (cloud vendor, OS, etc)
ci pipeline
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

I did try this page manually and I do see the stars when logged in as jason, and don't when not logged in, which matches the page. It seems that something in the test might not be actually logging in as jason resulting in the failure.  @frankbu, do you have any insight on the login in as jason and maybe why it's failing?

This issue was fixed in a commit in https://github.com/istio/istio.io/pull/8562 provided by @howardjohn.

This issue was fixed in a commit in https://github.com/istio/istio.io/pull/8562 provided by @howardjohn.


remove link from missing docs

Hi. Not sure if the docs will be added in, but noticed that the link pointed to a directory that no longer exists in the repo. Thanks.

          1 Warning

:warning:
Please assign someone to your PR

  Generated by :no_entry_sign: Danger

Hey @hidace , yea...we've not done a great job of documenting things here.
For now, we have the main README, and some components have their own READMEs, such as this one.
Thanks for the cleanup!


KnownIssues page on helix.dot.net

From @akoeplinger
I just noticed that the data on
https://helix.dot.net/BuildAnalysis/KnownIssues
doesn't match the table in the github issue, e.g. 89054 and 82894 both show 1 for the month hit count but on github they show 3 and 4 respectively (it seems most of the hit counts don't match actually)

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description
Fixed Landing Page Known issues not showing the correct number of impacted builds

Thanks for reporting this :)
Unfortunately we need completely different information for each site so we have different queries and there was a problem with the one on helix.dot.net, fixing this

PR: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/36220

fixed, closing


Firestore schedule export, move const variables outside of function execution

Move consts, except databaseName, outside of function execution.

LGTM


Dummy submission signature

This adds a dummy signature step to the profile submission so we can see how users react, whether the language is confusing, etc.
Unfortunately the UX of submission signing will probably need to change before this goes live for real. I'm not sure whether it's possible to generate short IPFS hashes locally (the ipfs-only-hash project, which ought to handle it, doesn't seem to deal with the mhlen argument we need to generate custom short hashes that'll fit in a felt). If it isn't possible, we may need to rework the UX so we can generate the string to sign after the photo and video have been uploaded.
Another potential tech-driven UX constraint is that I'm not sure how annoying it'll be to verify the signature of a long string in Cairo. If that ends up being hard to pull off, we may have to settle for just signing the bare profile CID, which means we'll have to find a way to indicate to the user what the heck they're signing.

Replaced by https://github.com/zorro-project/zorro/pull/123


Refactor and optimize varous df modules and bugfixes

Refactor modules rsjk and gdf, mdf, rsdf, ft_ao, aft;
Fix bug for large kmesh;
Fix memory usage issue in pbc.df.incore;
Add new vhf driver nr_direct_ex_drv;
Fix r_direct;
Fix bug in GDF when using Cartesian basis;
Fix issue #1154 for mdf;
Tune guess_omega;
Improve lattice Ls;
Tune k2gamma.kpts_to_kmesh;
Improve function to decontract basis;

@hongzhouye @fishjojo  Code is updated according to Hongzhou's tests and suggestions. The accuracy for different density fitting methods reaches the desired precision now. Hopefully this PR is ready to merge

Codecov Report

Merging #1168 (08a093e) into master (9e0c29c) will decrease coverage by 0.06%.
The diff coverage is 87.69%.

@@            Coverage Diff             @@
##           master    #1168      +/-   ##
==========================================
- Coverage   83.44%   83.38%   -0.07%
==========================================
  Files         691      706      +15
  Lines      132000   137443    +5443
  Branches    13575    14603    +1028
==========================================
+ Hits       110150   114607    +4457
- Misses      19087    19958     +871
- Partials     2763     2878     +115

Impacted Files
Coverage Δ

pyscf/agf2/aux_space.py
36.69% <ø> (ø)

pyscf/ci/cisd.py
88.36% <0.00%> (+0.13%)
:arrow_up:

pyscf/df/df.py
97.93% <ø> (ø)

pyscf/gto/ecp.py
78.94% <ø> (ø)

pyscf/lib/linalg_helper.py
54.44% <ø> (ø)

pyscf/pbc/df/ft_ao.py
89.68% <ø> (-10.32%)
:arrow_down:

pyscf/pbc/df/gdf_builder.py
87.44% <ø> (ø)

pyscf/pbc/df/incore.py
92.07% <ø> (+6.50%)
:arrow_up:

pyscf/pbc/df/mdf.py
92.44% <ø> (+1.93%)
:arrow_up:

pyscf/pbc/df/mdf_ao2mo.py
89.47% <ø> (+0.18%)
:arrow_up:

... and 196 more


TextField/TextArea without fixed width cause native crash in JBR 21

After #521, when TextField and TextArea don't have a fixed width, they cause a native crash in the JBR (at least when running in an IJ plugin)

Will be solved in #554 — can't know for sure what the issue was, but it seemed to stem from a very poor implementation of BTF2 in #521, and possibly something random-looking like, dunno, the lunar phase.

(I would push the fix buuuut they've temporarily removed my permissions from this repo, so I can't push)

Fixed in a6012516b1eb94f3d8459c240405030f067ad1fa


address the non-equi constraints, add output for the test case

I thought about the multi map for a while and I changed it back to basic map due to 2 reasons (1) as RexLiteral is immutable too, a constant '10' is different from a constant '10'. Thus there will be two values of '10'. (2) We only need a single literal value. Storing multiple values in a multi-map is not that useful.

Merged into julianhyde/master. Shortly will be merged into apache/master if tests pass. Thanks for the patch!

By the way, the best way to submit a patch is to fork your own copy of the apache repo (don't fork mine) and submit a pull request to apache. If I've made some changes in my repo you can still cherry-pick or merge them into your repo, and you can still send the pull request to apache.


RadzenDatagridColumn filter cannot be cleared after setting FilterValue

Describe the bug
I'm setting an initial value on a RadzenDatagridColumn<T>.FilterValue as so:
foreach (var (key, filterValue) in GridFilters)
{
    if (filterValue is null) continue;
    var column = _dataGrid.ColumnsCollection.FirstOrDefault(c => c.Title == key);
    if (column is null) continue;
    column.FilterValue = filterValue;
}
await _dataGrid.Reload();

After setting the FilterValue you can't clear the filter as the GetFilterValue() always fallbacks to the initial FilterValue which is not modified:
public object GetFilterValue()
{
    return filterValue ?? FilterValue;
}

You can circumvent the issue by using the SetFilterValueAsync.
Expected behavior
The FilterValue should update when the component is updated or the property should be modified or removed.
Desktop (please complete the following information):

Version 5.6.9

This demo is using exactly the same approach and the value can be cleared:
https://blazor.radzen.com/datagrid-filter-api?theme=material3

I'm sorry but it's not. It's using the the method SetFilterValue. If you change it to the property FilterValue it can't be cleared.

FilterValue should not be used since this is what will be restored when you execute StateHasChanged().

The warning is added directly by Blazor framework and Visual Studio when you build the project - it's not something specific to Radzen.Blazor compoents. Public parameters should not be set using code.


[MM-20766] Fix binding functions and references to reenable scroll

Summary
moving through search suggestions was not scrolling once you got to the last one visible but there were more suggestions. Also improve refs from string to object refs.
Ticket Link
MM-20766

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4433.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Umm .. I am totally not qualified to review client side stuff. I will excuse myself.

will destroy this test server because the infra that is running will be depracated. if you need a test server just add the tag again, thanks.
att, mattermost cloud services.

Test server destroyed

/update-branch


Fix Visual Studio squigglies/code-completion in GlobalObjects.cpp

Visual Studio gets horribly confused for some reason, and bugs out the file

@swift-ci please smoke test and merge

https://connect.microsoft.com/VisualStudio/feedback/details/3128781


English Language

Would be great, if you could use English-Language for all the descriptions.
(https://translate.google.de/translate?hl=&sl=zh-CN&tl=en&u=https%3A%2F%2Fgithub.com%2Fxuyuanzhou%2Freact-native-yz-vlcplayer)
Thanks for your hard work.

+1

+1


Implement shared CI build

Implements:

Shared CI build
Correct compiler

Building the tests gave me endless grief or Mac and Windows. I decided to link the test against the library. I am sure there is some reason for not doing this, but I do not know the reason and this works.


Not getting order updates on test websocket

So basically the title.
I place an order on wss://api.hyperliquid-testnet.xyz/ws and there is no update when subscribed to orderUpdates. While i see the order is in the list via browser.
Nor there is nothing with frontendOpenOrders/openOrders post request on the same testnet uri. Seems like it's getting orders only from actual only?
The same results i get with your sdk. No updates on order, no info about orders.
I see site is asking for info from different link which is: https://api-ui.hyperliquid-testnet.xyz/info. But it's not possible to query the address - 403 forbidden.

It sounds like you are claiming that you are getting the same results with the sdk as the API, so closing as this is not an SDK issue. Feel free to join the discord and ask questions to figure out how to use the API. The subscriptions work, my best guess is that you are subscribing to the wrong address. There is no need to use the api-ui version of the endpoints, but you also shouldn't get 403 errors


Environment implementation

Tasks:

[x] #178
[x] #179
[x] #180
[x] #181
[x] #162
[x] #295
[x] #286
[x] #292
[x] #285
[x] #270
[x] #328
[x] #293
[x] #235
[x] #61
[x] #265
[x] #281
[x] #284

Closing, all tasks completed


Delta encode edict ids

This also includes #2529, and you can see the third commit shows the size reductions, which are really nice. Will remove #2529 prior to merging.

much savings, much wow!


[Storage] Support Version level Worm (VLW)

Description

Object level immutable policy is based on versioned blob. WORM: write once read multiple times. There has been CLW(container level worm), design this feature to allow user to operate on object level.
User can create / migrate container by enable VLW on the container, then user can set different immutable policy and enable legalhold on each blobs in this container.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


added and implemented retweet_text() and updated requirements.txt

see docstring for information about what it does
added mechanicalsoup to requirements.txt because retweet_text uses mechanicalsoup
some context for why I made this:
was working on a twitter bot at a hackathon and we wanted to get retweet text of a retweet, the api at that point had the capability to get the url of the retweet but we wanted to get the text of the original tweet that was being retweeted.

This seems like its out of the scope of the library, which can already do this (although it takes two requests).

This can actually already be accomplished with a single existing request using API.get_status.
Using the status ID from the link, this will return a Status/Tweet object.
The retweeted_status attribute (if it exists) of this Status object is actually another Status object.
This means you can simply do something like api.get_status(status_id).retweeted_status.text.
An additional dependency for a single utility method that re-implements existing functionality is excessive. Not only that, but the additions in this PR are outside the scope of this library and don't fit within its spirit or theme. The purpose of Tweepy is to provide an interface to Twitter's API, not methods to scrape the site itself.


HWY-171: Include list of votes' hashes that need endorsing in WireVote.

https://casperlabs.atlassian.net/browse/HWY-171

bors r+