404 not found /admin123

I state ... I'm not an expert!!! I installed the script on a host that does not have cpanel. It is working on the php version 7. The installation is successful, not specified or a specific folder and resides in the directory path "/". The home page opens, but you can not access the administration panel.
http://site.domain/admin123 return 404 :(  Error
Can it work equally on the PHP 7 version?
Do I have to edit the .htaccess file?
I can not reproduce the error log file due to failure to access the settings. Where can I find this information?

@DEATHJ0KER Yes it works with PHP 7.
You need to use the enclosed htaccess file.
What about cPanel ? Learn manual configuration of Apache instead and you'll be good for every situation.
Check docs on www.ph7cms.com to rename the admin panel.

@

Of course, you are the genius, for me it's all difficult. I tried to install it with a click through Softaculous and only in the byethost hosts everything works correctly. Manually installing it on host Altervista, without CPanel, I set everything manually, at least what you can do. In their opinion it might work, but they can not tell me where the problem is born. They tell me that with such a large file as it is .htaccess, it is difficult for me to help. It works correctly when first installed, but does not open the control panel. I do not know what to do to solve...
The site where it works is www.virtualxdating.epizy.com/admin123
The site where it not works is www.virtualxdating.altervista.org/admin123
Inviato da Posta per Windows 10
Da: Polyna-Maude R.-Summerside
Inviato: venerdì 3 agosto 2018 01:17
A: pH7Software/pH7-Social-Dating-CMS
Cc: Valentino Decaroli; Mention
Oggetto: Re: [pH7Software/pH7-Social-Dating-CMS] 404 not found /admin123(#255)
@DEATHJ0KER Yes it works with PHP 7.
You need to use the enclosed htaccess file.
What about cPanel ? Learn manual configuration of Apache instead and you'll be good for every situation.
Check docs on www.ph7cms.com to rename the admin panel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@DEATHJ0KER Have you did like I told you in the other issue and checked with your hosting provider if they use modsecurity ?

I can give you the login details of the host where it was installed... Surely you understand the problem at first glance.

Host Login to https://www.altervista.org
username: virtualxdating
password: Nobody999

I am not going to do YOUR job.
Start by asking your hosting provider if they use modsecurity. Don't abuse of the help people give you and do your share by helping yourself.
I'm not going to contact your provider. You don't understand that YOU HAVE TO WORK ?
Go out and read the docs plus ask about modsecurity like already said.
You're asking like someone who pay some thousand $ to buy MatLab. First call tech support to understand how to do install because can't use a shell prompt.
Afterward complain he can't do nice "drawing" but just bought a scientific calculus software without having even finished high school math.
Maybe there's some basic skills that you should work on.

Okay I close the question here. Traced scripts for 20 years, if you're not curious to solve this problem, leave it to do this as a job. I always helped everyone when they had problems with my scripts and eventually installed them without problems anywhere. That profile was created to solve the problem, as I said, your script can be installed using just one click in a single free host service. You have nothing to teach cats, they are able to climb on their own... It would be a nice idea to solve this mountain of problems LOL³ Thank you for your time.

Hi @DEATHJ0KER
Really sorry, just so it right now. Have you tried to uncomment https://github.com/pH7Software/pH7-Social-Dating-CMS/blob/master/.htaccess#L23 line (in the root .htaccess file).
Finally, are you sure the mod_rewrite is correctly configured? https://ph7cms.com/doc/en/how-to-install-rewrite-module
Do you have 404 error else where when with your website or is it only with /admin123 URL?
Thanks!

The problem is only on /admin123 | mod_rewrite work well
I opened a ticket to the host. The host has some limitations and requires the intervention of paid technical support regarding the installation of scripts. Not all scripts are allowed to install, the service has limitations. This is why it does not access the /admin123 administration page. I installed PH7 CMS successfully through free InfinityFree hosting with installation wizard. It works perfectly, does not present any problem. Free host recommended to easily install the script ---> InfinityFree https://infinityfree.net
I do not use this script for profit, I have deactivated all the payment formulas of the service to be used freely.
P.S. Now I'm having trouble parking my domain on the host... Problems are being created in the hosts in the form of a promotion to their paid services. I like the free network!
Thank you for your precious time and for making available a script of such importance.
If I like this script? Very very much.
Thanks again.

What a shame! Indeed, please don't use free hosting companies. You can find very good ones (if you don't have much traffic) for just a few bucks per month (less than a coffee!)
I usually recommend WebFaction or others here https://ph7cms.com/doc/en/hosting
For the domain name, I usually recommend NameCheap or Name.com (they are awesome, and you can park/redirect your domain easily). I have no clue for yours... since your web host is free, I guess you can't if your domain is free. Otherwise, see with your domain registrar provider.
 If you could leave a nice review on Sourceforge (or just Star the Github repo, that would be AWESOME! 😃).
Good luck!

Treat instant messaging based on clients, therefore I do a lot of tests and I use many different hosts to practice with cms.
Of course, my domain is registered on NameCheap. When I have to park it in a free host it usually takes no more than 40 minutes. I had the dns aimed for over 4 days on InfinityFree host and even today he told me to set their DNS LOL³ :D
Check to see if my sourceforge review reflects the quality of your script.
Review by vxdscripts
I wish you a good job!!!

You Rock @DEATHJ0KER! 🎉

Hi @DEATHJ0KER
Please try to go to YOUR-WEBSITE.com/admin123/setting/analyticsapi and remove the code there, then save it. Please also try to clear the cache, Admin Panel -> Tool -> Caches -> Caches Manager

Solved tnx u are awesome 💯 :

Happy to hear that! 😊 Enjoy!


Add support for user-defined stream names

Use case: Hatchery (relevant for other projects as well).
For long-running tasks, Azure Function app might need to be restarted multiple times. In this scenario the stream graph is alive in the Fabric, however Azure Functions has to be "re-invoked". Current behavior is that every time when Azure Function restart a new stream graph is generated.
Proposal: Introduce stream graph builder methods with user-defined stream names to enable the users to control whether the stream graph has to be re-generated or not.

Initial implementation done by @Zingasoft in 86c605f0bcd9c5473b2a89afbb114010a74f7de7


Bread Crumb Component Updates and Additions

This PR will add the ability to include the Current page text into the breadcrumbs. By default if you do not include the current attribute in the component, it will work as it did before.
Additionally, in the component, it would not default to a direction, so if you were to render the following code:
<x-breadcrumbs
    :breadcrumbs="[
        '/' => 'Home',
        '/dashboard' => 'Dashboard',
        '/dashboard/users' => 'Users'
    ]"
/>

You would end up with something that looks like the following:

Not the desired output.
So, in this PR ltr will be default and if you want to use rtl you would have to specify that by including the dir attribute in the component and setting it to rtl
📼 Quick Video.
I've also created a quick video to show you what the breadcrumbs look like in this PR. I then swap over to the original (old) breadcrumbs component that is currently in the repo. You'll see the differences and updates in this video.
https://www.loom.com/share/73273290a6ee4daa938692bd382a0b0a
Testing
I've made sure to thoroughly test the component and make sure it is rendering correctly both in light and dark mode.
Documentation
I've also updated the documentation to include these updates.
Please let me know if you would like me to make any further changes or need clarification on anything.
Thanks!

Hi Tony, what's the reason you don't have dir on the <html> tag? That's what we do in the Panel Builder so it applies to all elements. I am not a fan of introducing a new attribute for this.

Also, the "current" behaviour can already be achieved, by appending the label of the current page onto the :breadcrumbs, but without a key (so the key is numeric). That's also what we do in the panel builder.

I believe my comments will help you out, so I'm going to close this. But if you have further clarification, just reply here and we can reopen.

@danharrin Great, thanks for the clarification.
So, say that someone is not using the Panel builder, do you recommend adding the dir to the body tag of the page, or where do you recommend adding that? It would be nice if the breadcrumbs component defaulted to dir='ltr' as opposed to showing both carets (left and right), making the component look broken by default.
Let me know :)
Thanks!

If we added dir='ltr' to the component, it would override the body setting, right?

But we'd need to :dir="null" in the admin panel, or pass in the RTL setting again? Otherwise it would override our <html> setting?

I understand its not desired but is there another way to do this in CSS?

We want ltr:hidden to apply even when the dir attribute is not present


Update admin README for new docker instructions [OSF-7842]

Purpose
Update instructions for getting the admin up and running locally
Changes

README updates to work with new django configuration

Side effects
None
Ticket
https://openscience.atlassian.net/browse/OSF-7842

@erinspace I was mid review when this was merged. invoke shell should probably changed to docker-compose run --rm web invoke shell for consistency and you have a typo on line 3 enviornment


Lag when using Maps app

Hi emotionbug, Once the module is installed, the map applications have a delay when used. It takes a long time to update the location even without using the fake GPS. Are there ways to fix it?
I tell you an example, I establish a point a and point b in the Maps application and the update does not go in real time, it has a delay of 4 or more seconds.

I'm having the same issue

Map apps just straight up can not find GPS signal with this module enabled. The intended application for spoofing works but as a side effect, waze and Google maps break even when GPS mocking app is off. Only workaround is to disable this module and restart to switch between mocking and normal driving.
OnePlus 11
Android 14
LineageOS 21 - Salami


show spinner centered of the screen

I would like to show centered loading spinner position, is there way to show separate and centered of the screen.
thank you.

I don't see why not, have you tried changing the CSS to center it?

I just played with this (3 years later). It does not seem to be achievable without hacking into Leaflet.
Leaflet puts each element extending L.Control into one of four containers: topleft, topright, bottomleft and bottomright which is determined by optional position property of a L.Control. This containers are set to position: absolute and stitched to the egdes of leaflet-control-container which has position relative and same dimensions as full map.
In order to position LoadingControl to the center of a map, it needs to be placed directly into leaflet-control-container and not into child containers. This is currently not possible.

Yes, the plugin would likely need to put the loading element somewhere outside of the typical Leaflet control elements if we wanted to do this.
I'm not convinced centering the spinner is a good idea design-wise and generally prefer to stick with the standard Leaflet controls configuration, so I'm not going to work on this. If someone wanted to work on a pull request I might consider merging it.


fix(Android): Workaround for chromium bugs 1023678 and 1050635.

Summary
There is a bug in the WebView that causes a spurious call to onReceivedError
whenever you download a file.
This commit is a workaround for that bug. The idea here is to try and detect
these spurious errors and drop them before they cause problems.
This commit should be reverted once those chromium bugs are fixed.
https://bugs.chromium.org/p/chromium/issues/detail?id=1048335
https://bugs.chromium.org/p/chromium/issues/detail?id=1023678
This workaround addresses issue #1050

Test Plan

Download a file through the webview on an android device with an up-to-date chromium installed.
Here is a screenshot from our app:

Without this fix, this happens when I click download:

With this fix, the error doesn't happen.
Compatibility

OS
Implemented

iOS
❌

Android
✅

Checklist

[X] I have tested this on a device and a simulator

@jamonholmgren @Titozzz @safaiyeh
Could you guys please review this PR?
Thanks.

Approved @trcoffman

Hi @safaiyeh, first of all, thanks for you time and work.
About this PR, what is missing to be merged?
Can I do something to help?
Thanks

Just need to merge master into it!

Thank you @trcoffman

@safaiyeh I've merged master into the branch, can you please merge this?

import WebView from 'react-native-webview';
exprot default class.........{
render(){
return (<WebView source={require('./index.html')} ........./>)
}
.....}
Error:crypto.getRandomValues() not supported????????

import WebView from 'react-native-webview';
exprot default class.........{
render(){
return (<WebView source={require('./index.html')} ........./>)
}
.....}
Error:crypto.getRandomValues() not supported????????why ?

That has nothing to do with this PR... or even this package in general. That's an error in your own codebase. React-native by default doesn't support crypto.getRandomValues(). You are gonna need this polyfill package for that: https://www.npmjs.com/package/react-native-get-random-values.
This isn't the appropriate place to talk about your issue though, this is a pull-request not an issue.

on version 9.4.0 this problem is back ?

on version 9.4.0 this problem is back ?

Same problem here on this version


[Improvement][dolphinscheduler-service] After the remove method removes the Server address, the refreshMasterList method needs to be executed.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
After the remove method removes the Server address, the refreshMasterList method needs to be executed.
org.apache.dolphinscheduler.service.queue.MasterPriorityQueue#remove
public void remove(Server server) {
this.queue.remove(server);
}
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

您好，您的邮件以收到，谢谢！未及时回复，请见谅。我会尽快处理。


The optional file "depent.txt" is not working

Hi,
In the context of some learn-ocaml exercises, I need to preload some external code (".ml" and ".cma" files). I tried to use the optional file "depend.txt" as described in the manual (http://ocaml-sf.org/learn-ocaml/tutorials/step-8.html). However, this seems to fail to work. I cannot manage to make the external code available to the student's code.
Here is the description of one failed experiment. I'm trying to gain access to some module "Q" that exports the symbol "q".
- Definition of module Q
> cat my-learn-ocaml-repository/exercises/lib/q.ml
   let q = 123 ;;
   let w = 456 ;;

> cat my-learn-ocaml-repository/exercises/lib/q.mli
   val q: int

- Checking the module Q
> ocamlc -c q.mli q.ml
> ocaml q.cmo
        OCaml version 4.05.0
# Q.q;;
- : int = 123
# Q.w;;
Error: Unbound value Q.w

- The file "depend.txt"
> cat my-learn-ocaml-repository/exercises/demo/depend.txt
../lib/q.mli
../lib/q.ml

- Rebuilding the repository and launching the learn-ocaml server
> touch my-learn-ocaml-repository/exercises/demo/test.ml
> learn-ocaml build  --repo my-learn-ocaml-repository
Learnocaml v.0.12 running.
Updating app at ./www
demo                         [OK]
> learn-ocaml serve
Learnocaml server v.0.12 starting on port 8080
Found the following teacher tokens:
  - X-1JJ-OZA-V41-XXX

- Using the exercise "demo" in the web browser
   Q.q;;
Unbound module Q

Thank you,
- Artur Miguel Dias

@lsylvestre Can you help us with this one?

Hi,
thank you for your interest in this feature.
As far as I know, it is not yet possible to preload external code and to make it available to the student's code.
The optional file depend.txt just allow to make external code available to test.ml, in the grading environment.
For instance, by replacing the content of my-learn-ocaml-repository/exercises/demo/test.ml with :
Test_lib.set_result @@
  [ Report.info ~message:("Q.q = " ^ string_of_int Q.q) ] ;;

the result in the web browser is :

You answer was very useful to me. I quickly understood that the exercises run in a restricted environment with access to a limited set of libraries and with no reach to the file system. This is a consequence of the translated OCaml code running on the browser, on the client side of the learn-ocaml application.
Probably, it should be possible to create a customized version of learn-ocaml with extra ocaml libraries available. Nevertheless, we tried to find a solution within the confines of the user manual.
Our code had a single dependence: the Yojson library. Our final, best solution was to get rid of this dependency and to write by hand a new small JSon parser, a neat piece of code with only 150 lines. After all, the json format is LL(1) parsable...
A different attempt that also worked, however with less flexibility, was to preprocess all the JSon examples beforehand, so that the json parser was not required at runtime.
One funny failed attempt that is worth mentioning was to try and expand inline the entire code of the Yojson library, which amounts to 14 thousand lines of OCaml code. Extra two thousand lines of code from the module Stream was also required. The final single file "depend.txt" ran perfectly on the regular OCaml interpreter, but the client side of learn-ocaml couldn't cope with it due to sheer size (we got the error "INTERNAL ERROR: error in prelude").
Thank you!

Thank you for your feedback on your experiments.
I was just testing another solution that you may find helpful:
You can customise the Learn-OCaml interpreter by declaring compiled files in : https://github.com/ocaml-sf/learn-ocaml/blob/master/src/grader/dune#L86
For instance, by declaring %{ocaml-config:standard_library}/stream.cmi, and then recompiling Learn-OCaml,
Stream can be used in all the exercises.
On my opam installation, %{ocaml-config:standard_library} is ~/.opam/<switch-name>/lib/ocaml,
and Yojson is in ~/.opam/<switch-name>/lib/Yojson.
Therefore, by declaring something like %{ocaml-config:standard_library}/../Yojson/yojson.cmi,
I can use Yojson on the client side :

Have a good day!

This is great! Thank you for the very clear examples.

I guess we can close this issue, right?

Yes, I agree.


Firebase Crashlytics Gradle Plugins become unresolved after migrating to versions.properties

[x] I have read the guidelines for submitting issues

🐛 Describe the bug

Really not sure if this is firebase-crashlytics-gradle issue or refreshVersions, before adding the refreshVersions, we were able to use any gradle API from firebase-crashlytics-gradle.
⚠ Current behavior

✅ Expected behavior

The refreshVersions able to coexist with firebase-crashlytics-gradle
💣 Steps to reproduce

Not sure what/which information to provide here, but here's my config:
// versions.properties
version.firebase-crashlytics-gradle=2.7.1

// app/build.gradle.kts
plugins {
    // ... omitted
    id("com.google.firebase.crashlytics")
}

// buildSrc/settings.gradle.kts
pluginManagement {
    plugins {
        id("de.fayard.refreshVersions") version "0.11.0"
    }
}

plugins {
    id("de.fayard.refreshVersions")
}

// settings.gradle.kts
plugins {
    id("de.fayard.refreshVersions") version "0.11.0"
}

📱 Tech info

Build Scan URL:

You need to use the no-BoM variant.
Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.
We have a plan to improve our dependency notations so that the default is the working one.

You need to use the no-BoM variant.
Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.
We have a plan to improve our dependency notations so that the default is the working one.

Ahhh, noted, yes, we're currently using BoM for Firebase, well noted then, will use the no-BoM for a workaround for this, will gives you updates 🙏

You need to use the no-BoM variant.
Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.
We have a plan to improve our dependency notations so that the default is the working one.

Ahhh, noted, yes, we're currently using BoM for Firebase, well noted then, will use the no-BoM a workaround for this, will gives you updates 🙏

This is so unfortunate, after using the no-BoM variant, the firebase plugin still fails to resolve 🙏

You have a clash between your dependencies and the ones from refreshVersions.
The Firebase object from refreshVersions is used and uses camelCase, not snake_case.

@jmfayard Can we make buildSrcLibs avoid clashes like that one?

You need to use the no-BoM variant.
Unfortunately, the issue is that the Firebase BoM used to include the Gradle plugin, but no longer does.
We have a plan to improve our dependency notations so that the default is the working one.

Does this issue already opened, or should I create a feature request for this one?

You have a clash between your dependencies and the ones from refreshVersions.
The Firebase object from refreshVersions is used and uses camelCase, not snake_case.

We've removed clashed dependencies from our buildSrc, unfortunately the firebase crashlytics plugins still failed to resolved :sob:

Next version of refreshVersions will improve bundled Firebase dependency notations. Hopefully, it helps.
In the meantime, just stick to plain hardcoded dependency notations and use the version placeholder (the underscore _).

Next version of refreshVersions will improve bundled Firebase dependency notations. Hopefully, it helps.
In the meantime, just stick to plain hardcoded dependency notations and use the version placeholder (the underscore _).

Removing our previous buildSrc/Dependencies.kt and use hardcoded notation & version placeholder, unfortunately failed to resolve as well :(

refreshVersions 0.20.0 is out with updated dependency notations. If it still doesn't work on your end, please link us a minimal reproducing project.

android-agentapp.zip here's our private internal project, we also remove everything from credentials and our entire codebase, except the build.gradle(.kts) and a few scripting files

android-agentapp.zip here's our private internal project, we also remove everything from credentials and our entire codebase, except the build.gradle(.kts) and a few scripting files

we also update to v0.22.0, there's a little problems for this code (so we commented out for a while):
// implementation(Square.Retrofit2.retrofit) {
    //     exclude(group = "com.squareup.okhttp3")
    //     because("version 3.x pulled from retrofit")
    // }

please let us know if need anything 🙏  thank you ❤

It's 0.20.0, not 0.22.0, did are you sure you set the correct version?

The issue is that firebaseCrashlytics { … } doesn't exist, because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working. It's unrelated to refreshVersions itself.

The issue is that firebaseCrashlytics { … } doesn't exist, because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working. It's unrelated to refreshVersions itself.

looks like this is issue on firebase gradle plugins unsupported to GKD (Gradle Kotlin DSL) itself, cmiiw?

BTW, posting big screenshots isn't very helpful to us. Giving the relevant part of the error messages, and any relevant small snippet is much less overwhelming for us, and we can sometimes reply when on mobile, which is hardly doable with these gigantic screenshots.

BTW, posting big screenshots isn't very helpful to us. Giving the relevant part of the error messages, and any relevant small snippet is much less overwhelming for us, and we can sometimes reply when on mobile, which is hardly doable with these gigantic screenshots.

well noted, my apologize for the screenshot, I should've resize it before commenting :pray: :D

because it's not optimized for Kotlin DSL, and I think you migrated from Groovy DSL which can go through runtime hacks to get that working

Thanks again for confirming this 🙏

It supports it, but you cannot configure it the way you're doing. Just search for "firebase crashlytics kotlin dsl" on Google and you'll get the info you need to do what you want.

It supports it, but you cannot configure it the way you're doing. Just search for "firebase crashlytics kotlin dsl" on Google and you'll get the info you need to do what you want.

found it!
for future readers, see workaround using this:
// app/build.gradle.kts

plugins {
  //...
  id("com.google.firebase.crashlytics")
}

android {
  buildTypes {
    getByName("release") {
      (this as ExtensionAware).configure<CrashlyticsExtension> {
        mappingFileUploadEnabled = true
        nativeSymbolUploadEnabled = true
        // etc.
       }
    }
  }
}

or
// app/build.gradle.kts
import com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension

android {
  buildTypes{
        getByName("release") {
            configure<CrashlyticsExtension> {
                mappingFileUploadEnabled = false          // to disable mapping file uploads (default=true if minifying)
                nativeSymbolUploadEnabled = true         // to enable NDK symbol file uploading (default=false)
                unstrippedNativeLibsDir = "path/to/libs" // optional override to change the default unstripped native library path, only used in NDK builds
            }
        }
    }
}

ref:

https://github.com/firebase/firebase-android-sdk/issues/1622#issuecomment-639584044
https://github.com/firebase/firebase-android-sdk/issues/2665#issuecomment-849897741


Better names for the *_indexer accessors

Tiled client Node object satisfy the Python Mapping interface; they are "dict-like". This is nice because all the things you can do with dicts
d["my_data"]
len(d)
d.items()
# etc.

work on Node just the same.
The Mapping interface supports look up by name like d["my_data"] but not look up by position like d[0]. For Node, we want position-based access too; we want to support the Python Sequence interface.
What are our options for doing this?
Accessors with log names (current approach)
A Node is a Mapping and it has accessors that satisfy the Sequence interface.
c.values_indexer[...]
c.keys_indexer[...]
c.items_indexer[...]

Pro:

Explicit switching between named-based lookup and positional lookup
Unambiguous

Con:

Way too verbose to just get the first/last item

Single Dispatch
c[0]  # int -> Sequence-like access
c[:5]  # slice -> Sequence-like access
c["image"]  # str -> Mapping-like access

Pro:

No new names to learn as the user

Cons:

This kind of overloading can be confusing.
Databroker has a strong commitment to interpreting integer keys as scan_id. Breaking that would be a huge problem for Databroker. For this reason, this is a nonstarter.

Overload .values, .keys, .items
Continue to support .values(), .keys(), .items(). Also support .values[], .keys[], .items[].
Pro:

No new names to learn

Cons:

Overloading interface methods like this with __getitem__ is very strange. (I can't think of a single time I've seen this done.)

Give .values_indexer (the most common one) a shorter alias
Ideas for ideas include:
.s  # not obvious, but nice and short! meant to invoke "slice" or "sequence"
.slice
.seq  # for "sequence..."
.iloc  # familiar if you know pandas, but inscrutable otherwise
.val  # good name, but not obvious how to use it, or which is which between "val" and "values"

I really want a very short way to type "Get me the first one," so I currently lean toward .s.
Make .values(), .keys(), .items() return iterators that are indexable.
c.values()[0]  # first
c.values()[:5]  # first 5
# ditto for keys, items

h/t @kleinhenz for this suggestion, which is very much in the spirit of slicerator and PIMS. I can't believe I didn't think of it!

Make .values(), .keys(), .items() return iterators that are indexable

This is my favorite.  Looks a bit funny, but at also means if you don x = c.values() it will still "do the right thing"

In short, I agree with c.values()[...].
I went digging and it turns out this has been a contentious topic previously w.r.t. dictionaries.
Python 2 used the notion dic.items()[0], but this changed in 3.X when these dictionary methods starting returning views (i.e. references/pointers of sort).  So there is precedent for this.
I'm not sure how the implementaiton would look since these are currently producing generators,  but I'm sure there's a plan.
https://github.com/bluesky/tiled/blob/54b26842d1926b451ac6ecd45dd94208bde40f24/tiled/client/node.py#L374-L401
There is some discussion (and plenty of sass) over the efficiency concerns here. But since this isn't a class in the standard library, and we need to meet users where they are, it's probably best to use this for inspiration on implementation.
One notion that came from this discussion that I do like---and find more elegant than c[-1]---is .first(), .last(),  .head(), and .tail() as simple slicing methods. But depending on the outcomes, those could just be short aliases.

Great find!
For a generic iterator, positional lookup raises performance concerns. (To get the Nth item you may need to iterate through the first N.) In our case, our implementation happens to support random access, and for that reason I think the efficiency concerns do not apply.
I agree that .first(), .last(), .head(), and .tail() would be very nice. Yes, we can implement them as aliases.


Problem with your package

Hi Yakov,
I tried your package in my local server and I have no problem...but I tried to use it in UmbracoCloud environment (where debug="false" is only temporary disabled) and when the debug mode is OFF, the website give me an YSOD problem without details
Can you helpme?

Hi
Can you show me the error? It can help me to understand this issue
On Wed, Mar 21, 2018, 6:03 PM Adriano Fabri<EMAIL_ADDRESS>wrote:

Hi Yakov,
I tried your package in my local server and I have no problem...but I
tried to use it in UmbracoCloud environment (where debug="false" is only
temporary disabled) and when the debug mode is OFF, the website give me an
YSOD problem without details
Can you helpme?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yawkale/missingcode-umbraco-html-minifier/issues/1,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJspEp4cwApNMJuxw42TGStPnpXYezefks5tgnnVgaJpZM4S0gN2
.

Sorry for slow response, I have no environment on Umbraco Cloud, I'll use reproduce this issue


[Easy][LandingPage] FAQ section on main page

Is this request related to a problem? Please describe.
Many people ask the same questions, need a FAQ for fast redirect and for average person to quickly understand.
Describe the solution you'd like

Add a FAQ page + Add it to navbar and footer
The FAQ page should display each question and answer directly. No need for accordion.

The questions for now would be:
0. Why is PearAI called PearAI?

Pear programming... Pair programming... PearAI Pair programming!

What separates PearAI from Github Copilot?> PearAI will provide better quality responses, and also has a better UX. These are the 2 key factors in accelerating your coding workflow. For both of these factors, you can try the free trial, and you'll be able to see the proof for yourself.
Why should I switch to PearAI?

PearAI is a fork of VSCode, and possess all of its functionalities, but also adds more to it by integrating AI functionalities to speed up your coding workflow. Current users have expressed that their coding workflow accelerated by at least 3-4x.

Why can't I just use ChatGPT/Claude/etc. directly instead?

You can, and we used to as well. However, the convenience of the chat being integrated into the editor, along with easy access features within the chats such as including other files, applying changes directly, removing the need to copy paste code, prompting with code context, adding other websites or docs links in chat directly, all of this and more, means that you have a much more seamless coding experience, resulting in significant overall faster development. Try it yourself!

Is PearAI an extension or an app? PearAI is an app and requires you to download it.

PearAI is an app and requires you to download (hyperlink download) it. Being a VSCode extension severely limits the modifications we can do. In order to provide the best UX possible, we need full control of code changes within the app.

How can I contribute to PearAI?

See the contributors' section. (hyperlink to the new Contributing page)

@Fryingpannn i guess issue already done


TUIO for Displax

Thank you for the response to my last issue and for making this awesome simulator!
I am making an application for a Displax screen (interactive touch screen).
I was able in making a connection between the simulator and the screen itself, but now I'm trying to attach a certain touch to showing a square on that spot. So with the Displax screen you get these physical circled objects which you can use for object recognition by placing them on the screen.
What we want to achieve is spawning one of the virtual numbered squares that you see in the simulator on the same spot where you place that physical circled object.
I can't seem to find how to or where in the code I could inject this.
Thanks in advance Greg!

hey again Justin, when we used TUIO for our interactive touch tables the ids to identify various objects came from the touch screen surface hardware itself. We used MultiTaction display hardware that we configured to recognise markers printed on the physical items used on the table.
The TUIO objects sent over the network embed an integer id which the simulator should recognise if they're between 0-7 or 1-8 (can't quite remember the exact range) and show squares for. I assume that these are the type of objects you need to recognise so perhaps double check that the ids your table is sending are in the range 0-7 (or 1-8!). Do you need to recognise a larger range of objects? If so, you should be able to easily extend the range in the simulator by duplicating the existing squares and changing their ids. If you need to recognise arbitrary object ids coming in then the simulator will have to be modified to spawn prefabs for each unique touch/marker for the object ids you want to support (and show the right number in the square etc). For our test rigs I never had to test more than a couple of objects so I didn't need to extend it further and support any object ids that appeared. It's probably more to do with getting using Unity to spawn and configure stuff than it is a TUIO problem, so if you're comfortable using Unity you should be ok.
I haven't looked at the simulator for a while (so it's probably quite out of date with the latest Unity) but feel free to ask some questions and I'll do my best to answer them :)

Great thanks a lot, Greg!
I'll go digging again but this really helps it will probably be something within the range then as you suggest because the IDs are high digits. I will check out MultiTaction too.
I will let you know if I succeed!
Thanks again Greg, you're awesome!

No worries. Maybe check out TUIOListener for a command line TUIO debugger/helper. It might help you quickly debug/confirm what object numbers are in use from your table objects.

Hi Greg,
So I checked with TUIOListener and I looked into the code but did not manage to make a change. So the TUIO simulator still perceives the disc as 3 individual cursors/touches. The discs that I use have an ID that range from 401 to 408.

This is what I tried:

Altering the spawnObjectCount in Surface.cs from 8 to 410;
Altering the Range in SurfaceObject.cs from (0,7) to (0,410)
In scene Inspector adding 410 sprites and 410 colors while in game mode
In scene Inspector setting a specific object to a specific ID (401)
Connecting to Displax Connect which is able to identify the disc and its ID

I think I am missing something or did something wrong, could you help me point out what?
Thanks in advance Greg!!

Here is a picture of my Unity scene and where you can see in the bottom left corner that it recognizes 3 touches but no object.

Found the solution:
In de displaxApplication, you have to make a normal Tag and not a Tag+ which I made.

hey Justin, nice one tracking it down. I would not have been able much with the displaxApplication configuration!


Create Open publish

Docs Build status updates of commit 6b4f888:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Open publish
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Some readers require PSHB

It would be nice if a reader, upon registration, could specify that it only supports PSHB feeds and then only get shown if the feed contains rel="hub" so that users don't get confused when they try the button and it doesn't work.

Hum. What feed/reader do you have in mind This should work for any reader, whether it supports PuSH or not!

I understand that's the current intent, but it would be nice if readers (such as gnu social, or my indie reader) that only work with PuSH could still be used with this on compatible feeds.

That's a good point... and "feature" discovery is indeed something that needs to be addressed... Let's keep the issue open until we find a good solution for this :)


Add literal combinator to print strings verbatim.

The motivation for the literal combinator is to be able to print
multiline string literals in for example source code. Scala multiline
string literals contain newlines that should never be flattened or get
indentation.

Codecov Report

Merging #77 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
+ Coverage   98.12%   98.18%   +0.05%
==========================================
  Files           6        6
  Lines         267      275       +8
  Branches       38       39       +1
==========================================
+ Hits          262      270       +8
  Misses          5        5

Impacted Files
Coverage Δ

core/src/main/scala/org/typelevel/paiges/Doc.scala
98.06% <100%> (+0.06%)
:arrow_up:

...re/src/main/scala/org/typelevel/paiges/Chunk.scala
97.56% <100%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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

It seems the mima checks don't run, https://travis-ci.org/typelevel/paiges/jobs/284720590#L1044
[info] paiges-core: previous-artifact not set, not analyzing binary compatibility

Not sure if this is intentional or not judging https://github.com/typelevel/paiges/blob/bc2b920b3a070444c66fc720772b33a3fdf7acf5/build.sbt#L105

Why do you want nesting to be ignored?
I’m concerned that breaks composability in that after the first newline positions become absolute.

I want to ignore nesting in order to accurately print Scala multiline string literals.
{
  """
""" // newline inside string literal should ignore indent
}

If that newline is printed with two space indent then the program gets new semantics.
After more thinking, I'm not happy with the approach in this PR as literal doesn't abort grouping as I'd like it to do.
// with current literal
foo("""
""")
// how I want it
foo(
  """
"""
)

I think I want three different kinds of newlines

line, in its current form
line that unconditionally aborts grouping (eliminates the flat part of the union), but respects nesting/indentation.
line like 2. AND ignores nesting

Example
{   // line #1, flattens to space if grouping succeeds
  """
""" // line #3 inside string literal, should never get indent and should never flatten
  1 // line #2 separating the string literal statement from `1`, keeps indent but can never flatten
}

I'm not sure what's the best way to model this in the current implementation, whether we need custom flatten/grouped/nesting combinators or adapt the existing ones.

Closing since I'm not convinced Literal is necessary if we manage to generalize Line.

I went ahead and implemented lineNoFlat and lineNoFlatNoIndent and I'm experimenting  with them in https://github.com/olafurpg/scala-syntax. Early results look promising, I was able to fix the idempotency issues I had with multiline string literals. I need more time to validate if lineNoFlat/lineNoFlatNoIndent are necessary, introducing them is a big breaking change since there is currently an assumption that every Doc has a flat representation.


[docs] Random Unsplash photo URL is no longer functional

Steps to reproduce
Link to live example: (required)
Steps:

Link attache in 2nd step. i started recently working on react Js. Sorry for if i am Wrong. here is mention Issue to replicate (React Templates) -> (Sign-in side) -> Preview -> "Open below link".
https://mui.com/material-ui/getting-started/templates/sign-in-side/
when you open no Image will rendering. As Showing in preview.

Current behavior
No Image is rendering Or may remove from your server.
Expected behavior
Image will be show when preview
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: Sign-in side

I agree, yeah! Regarding the sign-in side, specifically, @zanivan tackled this already; just waiting to resolve the tests there so we can merge the fix. Maybe it'd also be good to fix the blog in the meantime, too. This issue is also actually a dupe of https://github.com/mui/material-ui/issues/42649 😃 So, closing this one in favor of the first.


ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: INVALID_ADDR

Bug Report
What happened:
After trying to update our cluster with ceph-ansible it fails with INVALID_ADDR
failed: [foo04.ceph-sh.xxx.de] (item={u'service': u'ceph-mon', u'zone': u'public'}) =>
{"changed": false, "item": {"service": "ceph-mon", "zone": "public"},
"msg": "ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: INVALID_ADDR: aa.bb.186.0/24, xx.yy.9.0/24, xx.yy.231.160/27, xx.yy.231.130/27 Permanent and Non-Permanent(immediate) operation"}         >
failed: [bar-01-mon.ceph-2.yyy.de] (item={u'service': u'ceph', u'zone': u'public'}) =>
{"changed": false, "item": {"service": "ceph", "zone": "public"},
"msg": "ERROR: Exception caught: org.fedoraproject.FirewallD1.Exception: INVALID_ADDR: aa.bb.186.0/24, xx.yy.9.0/24, xx.yy.231.160/27, xx.yy.231.130/27 Permanent and Non-Permanent(immediate) operation"}

How to reproduce it (minimal and precise):
Try to use multiple public networks like described http://docs.ceph.com/docs/luminous/rados/configuration/network-config-ref/
(Share your group_vars files, inventory - will share later have to pseudo. some lines)
Environment:

OS (e.g. from /etc/os-release):

NAME="Red Hat Enterprise Linux Server"
VERSION="7.6 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME=Storage
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.6"

Kernel (e.g. uname -a):
Linux bar-01-mon.ceph-2.yyy.de 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux

Ansible version (e.g. ansible-playbook --version):

ansible-playbook <IP_ADDRESS>
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible-playbook
  python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

ceph-ansible version (e.g. git head or tag or stable branch):
3.2.4-1.el7cp
Ceph version (e.g. ceph -v):

ceph version 12.2.8-89.el7cp (2f66ab2fa63b2879913db6d6cf314572a83fd1f0) luminous (stable)

Try to use multiple public networks like described http://docs.ceph.com/docs/luminous/rados/configuration/network-config-ref/

We currently don't support multiple networks for public and cluster network in ceph-ansible.
I suppose you specify something like public_network: <IP_ADDRESS>/24,<IP_ADDRESS>/24 but the public_network (and cluster_network) are supposed to be an unique value.
You issue comes from the firewalld module because we're using the public_network variable as value for the firewalld source parameter. This field doesn't support multiple networks.
https://github.com/ceph/ceph-ansible/blob/stable-3.2/roles/ceph-infra/tasks/configure_firewall.yml#L26
https://docs.ansible.com/ansible/latest/modules/firewalld_module.html#parameters

That's exactly what I expected, problem is only that until a few weeks ago everything just worked and not supporting multiple networks causes way more problems.

I'm using check_firewall maybe I have to use configure_firewall.
It's a bit irritating when configuration options are renamed or deprecated without any real notice.

Yes, you need to use configure_firewall.
https://github.com/ceph/ceph-ansible/blob/stable-3.2/RELEASE-NOTE.md#removed-features


How do I get two shapes to move together?

Hello! I want a rectangle with a triangle on top. In the example with the creepy guy not all of the parts have a mouseX, mouseY part to them but yet the entire thing moves with the mouse. I can't get the two shapes to stick together. Thank you!

AHHH I figured it out! I'm so happy.


Does not run on Mac because multiprocessing runs with spawn on mac

This code is tested on linux and on WSL linux on Windows which run multi-processing as fork.  It does not run on a mac which runs as spawn.  The program uses queues in global variables.

The code now forces multiprocessing to use Fork instead of Spawn.
Found a couple data sets with "future" dates when read on the Apple M1 so tossing future packets for now.


Var name typo processing URL table alias

I just noticed this while looking into other stuff. It must be of some consequence. Maybe it will help with loading the contents of URL table aliases at first startup?

Done. Good catch! Thanks Phil!


Fix broken links on main

  Exhaustive list of all broken anchors found:
  - Broken anchor on source page path = /docs/api/resources/toc/abuse_reports_toc/:
     -> linking to #api-abuse-reports (resolved as: /docs/api/resources/toc/abuse_reports_toc/#api-abuse-reports)
     -> linking to #api-abuse-reports-create (resolved as: /docs/api/resources/toc/abuse_reports_toc/#api-abuse-reports-create)
     -> linking to #api-abuse-reports-get (resolved as: /docs/api/resources/toc/abuse_reports_toc/#api-abuse-reports-get)
  - Broken anchor on source page path = /docs/api/resources/toc/agent_ingresses_toc/:
     -> linking to #api-agent-ingresses (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses)
     -> linking to #api-agent-ingresses-create (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses-create)
     -> linking to #api-agent-ingresses-delete (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses-delete)
     -> linking to #api-agent-ingresses-get (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses-get)
     -> linking to #api-agent-ingresses-list (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses-list)
     -> linking to #api-agent-ingresses-update (resolved as: /docs/api/resources/toc/agent_ingresses_toc/#api-agent-ingresses-update)
  - Broken anchor on source page path = /docs/api/resources/toc/api_keys_toc/:
     -> linking to #api-api-keys (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys)
     -> linking to #api-api-keys-create (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys-create)
     -> linking to #api-api-keys-delete (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys-delete)
     -> linking to #api-api-keys-get (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys-get)
     -> linking to #api-api-keys-list (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys-list)
     -> linking to #api-api-keys-update (resolved as: /docs/api/resources/toc/api_keys_toc/#api-api-keys-update)
  - Broken anchor on source page path = /docs/api/resources/toc/application_sessions_toc/:
     -> linking to #api-application-sessions (resolved as: /docs/api/resources/toc/application_sessions_toc/#api-application-sessions)
     -> linking to #api-application-sessions-get (resolved as: /docs/api/resources/toc/application_sessions_toc/#api-application-sessions-get)
     -> linking to #api-application-sessions-delete (resolved as: /docs/api/resources/toc/application_sessions_toc/#api-application-sessions-delete)
     -> linking to #api-application-sessions-list (resolved as: /docs/api/resources/toc/application_sessions_toc/#api-application-sessions-list)
  - Broken anchor on source page path = /docs/api/resources/toc/application_users_toc/:
     -> linking to #api-application-users (resolved as: /docs/api/resources/toc/application_users_toc/#api-application-users)
     -> linking to #api-application-users-get (resolved as: /docs/api/resources/toc/application_users_toc/#api-application-users-get)
     -> linking to #api-application-users-delete (resolved as: /docs/api/resources/toc/application_users_toc/#api-application-users-delete)
     -> linking to #api-application-users-list (resolved as: /docs/api/resources/toc/application_users_toc/#api-application-users-list)
  - Broken anchor on source page path = /docs/api/resources/toc/bot_users_toc/:
     -> linking to #api-bot-users (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users)
     -> linking to #api-bot-users-create (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users-create)
     -> linking to #api-bot-users-delete (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users-delete)
     -> linking to #api-bot-users-get (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users-get)
     -> linking to #api-bot-users-list (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users-list)
     -> linking to #api-bot-users-update (resolved as: /docs/api/resources/toc/bot_users_toc/#api-bot-users-update)
  - Broken anchor on source page path = /docs/api/resources/toc/certificate_authorities_toc/:
     -> linking to #api-certificate-authorities (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities)
     -> linking to #api-certificate-authorities-create (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities-create)
     -> linking to #api-certificate-authorities-delete (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities-delete)
     -> linking to #api-certificate-authorities-get (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities-get)
     -> linking to #api-certificate-authorities-list (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities-list)
     -> linking to #api-certificate-authorities-update (resolved as: /docs/api/resources/toc/certificate_authorities_toc/#api-certificate-authorities-update)
  - Broken anchor on source page path = /docs/api/resources/toc/credentials_toc/:
     -> linking to #api-credentials (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials)
     -> linking to #api-credentials-create (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials-create)
     -> linking to #api-credentials-delete (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials-delete)
     -> linking to #api-credentials-get (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials-get)
     -> linking to #api-credentials-list (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials-list)
     -> linking to #api-credentials-update (resolved as: /docs/api/resources/toc/credentials_toc/#api-credentials-update)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_backend_module_toc/:
     -> linking to #api-edge-route-backend-module (resolved as: /docs/api/resources/toc/edge_route_backend_module_toc/#api-edge-route-backend-module)
     -> linking to #api-edge-route-backend-module-replace (resolved as: /docs/api/resources/toc/edge_route_backend_module_toc/#api-edge-route-backend-module-replace)
     -> linking to #api-edge-route-backend-module-get (resolved as: /docs/api/resources/toc/edge_route_backend_module_toc/#api-edge-route-backend-module-get)
     -> linking to #api-edge-route-backend-module-delete (resolved as: /docs/api/resources/toc/edge_route_backend_module_toc/#api-edge-route-backend-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_circuit_breaker_module_toc/:
     -> linking to #api-edge-route-circuit-breaker-module (resolved as: /docs/api/resources/toc/edge_route_circuit_breaker_module_toc/#api-edge-route-circuit-breaker-module)
     -> linking to #api-edge-route-circuit-breaker-module-replace (resolved as: /docs/api/resources/toc/edge_route_circuit_breaker_module_toc/#api-edge-route-circuit-breaker-module-replace)
     -> linking to #api-edge-route-circuit-breaker-module-get (resolved as: /docs/api/resources/toc/edge_route_circuit_breaker_module_toc/#api-edge-route-circuit-breaker-module-get)
     -> linking to #api-edge-route-circuit-breaker-module-delete (resolved as: /docs/api/resources/toc/edge_route_circuit_breaker_module_toc/#api-edge-route-circuit-breaker-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_compression_module_toc/:
     -> linking to #api-edge-route-compression-module (resolved as: /docs/api/resources/toc/edge_route_compression_module_toc/#api-edge-route-compression-module)
     -> linking to #api-edge-route-compression-module-replace (resolved as: /docs/api/resources/toc/edge_route_compression_module_toc/#api-edge-route-compression-module-replace)
     -> linking to #api-edge-route-compression-module-get (resolved as: /docs/api/resources/toc/edge_route_compression_module_toc/#api-edge-route-compression-module-get)
     -> linking to #api-edge-route-compression-module-delete (resolved as: /docs/api/resources/toc/edge_route_compression_module_toc/#api-edge-route-compression-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_ip_restriction_module_toc/:
     -> linking to #api-edge-route-ip-restriction-module (resolved as: /docs/api/resources/toc/edge_route_ip_restriction_module_toc/#api-edge-route-ip-restriction-module)
     -> linking to #api-edge-route-ip-restriction-module-replace (resolved as: /docs/api/resources/toc/edge_route_ip_restriction_module_toc/#api-edge-route-ip-restriction-module-replace)
     -> linking to #api-edge-route-ip-restriction-module-get (resolved as: /docs/api/resources/toc/edge_route_ip_restriction_module_toc/#api-edge-route-ip-restriction-module-get)
     -> linking to #api-edge-route-ip-restriction-module-delete (resolved as: /docs/api/resources/toc/edge_route_ip_restriction_module_toc/#api-edge-route-ip-restriction-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_o_auth_module_toc/:
     -> linking to #api-edge-route-o-auth-module (resolved as: /docs/api/resources/toc/edge_route_o_auth_module_toc/#api-edge-route-o-auth-module)
     -> linking to #api-edge-route-o-auth-module-replace (resolved as: /docs/api/resources/toc/edge_route_o_auth_module_toc/#api-edge-route-o-auth-module-replace)
     -> linking to #api-edge-route-o-auth-module-get (resolved as: /docs/api/resources/toc/edge_route_o_auth_module_toc/#api-edge-route-o-auth-module-get)
     -> linking to #api-edge-route-o-auth-module-delete (resolved as: /docs/api/resources/toc/edge_route_o_auth_module_toc/#api-edge-route-o-auth-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_oidc_module_toc/:
     -> linking to #api-edge-route-oidc-module (resolved as: /docs/api/resources/toc/edge_route_oidc_module_toc/#api-edge-route-oidc-module)
     -> linking to #api-edge-route-oidc-module-replace (resolved as: /docs/api/resources/toc/edge_route_oidc_module_toc/#api-edge-route-oidc-module-replace)
     -> linking to #api-edge-route-oidc-module-get (resolved as: /docs/api/resources/toc/edge_route_oidc_module_toc/#api-edge-route-oidc-module-get)
     -> linking to #api-edge-route-oidc-module-delete (resolved as: /docs/api/resources/toc/edge_route_oidc_module_toc/#api-edge-route-oidc-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_policy_module_toc/:
     -> linking to #api-edge-route-policy-module (resolved as: /docs/api/resources/toc/edge_route_policy_module_toc/#api-edge-route-policy-module)
     -> linking to #api-edge-route-policy-module-replace (resolved as: /docs/api/resources/toc/edge_route_policy_module_toc/#api-edge-route-policy-module-replace)
     -> linking to #api-edge-route-policy-module-get (resolved as: /docs/api/resources/toc/edge_route_policy_module_toc/#api-edge-route-policy-module-get)
     -> linking to #api-edge-route-policy-module-delete (resolved as: /docs/api/resources/toc/edge_route_policy_module_toc/#api-edge-route-policy-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_request_headers_module_toc/:
     -> linking to #api-edge-route-request-headers-module (resolved as: /docs/api/resources/toc/edge_route_request_headers_module_toc/#api-edge-route-request-headers-module)
     -> linking to #api-edge-route-request-headers-module-replace (resolved as: /docs/api/resources/toc/edge_route_request_headers_module_toc/#api-edge-route-request-headers-module-replace)
     -> linking to #api-edge-route-request-headers-module-get (resolved as: /docs/api/resources/toc/edge_route_request_headers_module_toc/#api-edge-route-request-headers-module-get)
     -> linking to #api-edge-route-request-headers-module-delete (resolved as: /docs/api/resources/toc/edge_route_request_headers_module_toc/#api-edge-route-request-headers-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_response_headers_module_toc/:
     -> linking to #api-edge-route-response-headers-module (resolved as: /docs/api/resources/toc/edge_route_response_headers_module_toc/#api-edge-route-response-headers-module)
     -> linking to #api-edge-route-response-headers-module-replace (resolved as: /docs/api/resources/toc/edge_route_response_headers_module_toc/#api-edge-route-response-headers-module-replace)
     -> linking to #api-edge-route-response-headers-module-get (resolved as: /docs/api/resources/toc/edge_route_response_headers_module_toc/#api-edge-route-response-headers-module-get)
     -> linking to #api-edge-route-response-headers-module-delete (resolved as: /docs/api/resources/toc/edge_route_response_headers_module_toc/#api-edge-route-response-headers-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_saml_module_toc/:
     -> linking to #api-edge-route-saml-module (resolved as: /docs/api/resources/toc/edge_route_saml_module_toc/#api-edge-route-saml-module)
     -> linking to #api-edge-route-saml-module-replace (resolved as: /docs/api/resources/toc/edge_route_saml_module_toc/#api-edge-route-saml-module-replace)
     -> linking to #api-edge-route-saml-module-get (resolved as: /docs/api/resources/toc/edge_route_saml_module_toc/#api-edge-route-saml-module-get)
     -> linking to #api-edge-route-saml-module-delete (resolved as: /docs/api/resources/toc/edge_route_saml_module_toc/#api-edge-route-saml-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_user_agent_filter_module_toc/:
     -> linking to #api-edge-route-user-agent-filter-module (resolved as: /docs/api/resources/toc/edge_route_user_agent_filter_module_toc/#api-edge-route-user-agent-filter-module)
     -> linking to #api-edge-route-user-agent-filter-module-replace (resolved as: /docs/api/resources/toc/edge_route_user_agent_filter_module_toc/#api-edge-route-user-agent-filter-module-replace)
     -> linking to #api-edge-route-user-agent-filter-module-get (resolved as: /docs/api/resources/toc/edge_route_user_agent_filter_module_toc/#api-edge-route-user-agent-filter-module-get)
     -> linking to #api-edge-route-user-agent-filter-module-delete (resolved as: /docs/api/resources/toc/edge_route_user_agent_filter_module_toc/#api-edge-route-user-agent-filter-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_webhook_verification_module_toc/:
     -> linking to #api-edge-route-webhook-verification-module (resolved as: /docs/api/resources/toc/edge_route_webhook_verification_module_toc/#api-edge-route-webhook-verification-module)
     -> linking to #api-edge-route-webhook-verification-module-replace (resolved as: /docs/api/resources/toc/edge_route_webhook_verification_module_toc/#api-edge-route-webhook-verification-module-replace)
     -> linking to #api-edge-route-webhook-verification-module-get (resolved as: /docs/api/resources/toc/edge_route_webhook_verification_module_toc/#api-edge-route-webhook-verification-module-get)
     -> linking to #api-edge-route-webhook-verification-module-delete (resolved as: /docs/api/resources/toc/edge_route_webhook_verification_module_toc/#api-edge-route-webhook-verification-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edge_route_websocket_tcp_converter_module_toc/:
     -> linking to #api-edge-route-websocket-tcp-converter-module (resolved as: /docs/api/resources/toc/edge_route_websocket_tcp_converter_module_toc/#api-edge-route-websocket-tcp-converter-module)
     -> linking to #api-edge-route-websocket-tcp-converter-module-replace (resolved as: /docs/api/resources/toc/edge_route_websocket_tcp_converter_module_toc/#api-edge-route-websocket-tcp-converter-module-replace)
     -> linking to #api-edge-route-websocket-tcp-converter-module-get (resolved as: /docs/api/resources/toc/edge_route_websocket_tcp_converter_module_toc/#api-edge-route-websocket-tcp-converter-module-get)
     -> linking to #api-edge-route-websocket-tcp-converter-module-delete (resolved as: /docs/api/resources/toc/edge_route_websocket_tcp_converter_module_toc/#api-edge-route-websocket-tcp-converter-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edges_https_routes_toc/:
     -> linking to #api-edges-https-routes (resolved as: /docs/api/resources/toc/edges_https_routes_toc/#api-edges-https-routes)
     -> linking to #api-edges-https-routes-create (resolved as: /docs/api/resources/toc/edges_https_routes_toc/#api-edges-https-routes-create)
     -> linking to #api-edges-https-routes-get (resolved as: /docs/api/resources/toc/edges_https_routes_toc/#api-edges-https-routes-get)
     -> linking to #api-edges-https-routes-update (resolved as: /docs/api/resources/toc/edges_https_routes_toc/#api-edges-https-routes-update)
     -> linking to #api-edges-https-routes-delete (resolved as: /docs/api/resources/toc/edges_https_routes_toc/#api-edges-https-routes-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edges_https_toc/:
     -> linking to #api-edges-https (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https)
     -> linking to #api-edges-https-create (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https-create)
     -> linking to #api-edges-https-get (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https-get)
     -> linking to #api-edges-https-list (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https-list)
     -> linking to #api-edges-https-update (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https-update)
     -> linking to #api-edges-https-delete (resolved as: /docs/api/resources/toc/edges_https_toc/#api-edges-https-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edges_tcp_toc/:
     -> linking to #api-edges-tcp (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp)
     -> linking to #api-edges-tcp-create (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp-create)
     -> linking to #api-edges-tcp-get (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp-get)
     -> linking to #api-edges-tcp-list (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp-list)
     -> linking to #api-edges-tcp-update (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp-update)
     -> linking to #api-edges-tcp-delete (resolved as: /docs/api/resources/toc/edges_tcp_toc/#api-edges-tcp-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/edges_tls_toc/:
     -> linking to #api-edges-tls (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls)
     -> linking to #api-edges-tls-create (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls-create)
     -> linking to #api-edges-tls-get (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls-get)
     -> linking to #api-edges-tls-list (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls-list)
     -> linking to #api-edges-tls-update (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls-update)
     -> linking to #api-edges-tls-delete (resolved as: /docs/api/resources/toc/edges_tls_toc/#api-edges-tls-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/endpoints_toc/:
     -> linking to #api-endpoints (resolved as: /docs/api/resources/toc/endpoints_toc/#api-endpoints)
     -> linking to #api-endpoints-list (resolved as: /docs/api/resources/toc/endpoints_toc/#api-endpoints-list)
     -> linking to #api-endpoints-get (resolved as: /docs/api/resources/toc/endpoints_toc/#api-endpoints-get)
  - Broken anchor on source page path = /docs/api/resources/toc/event_destinations_toc/:
     -> linking to #api-event-destinations (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations)
     -> linking to #api-event-destinations-create (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations-create)
     -> linking to #api-event-destinations-delete (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations-delete)
     -> linking to #api-event-destinations-get (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations-get)
     -> linking to #api-event-destinations-list (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations-list)
     -> linking to #api-event-destinations-update (resolved as: /docs/api/resources/toc/event_destinations_toc/#api-event-destinations-update)
  - Broken anchor on source page path = /docs/api/resources/toc/event_sources_toc/:
     -> linking to #api-event-sources (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources)
     -> linking to #api-event-sources-create (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources-create)
     -> linking to #api-event-sources-delete (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources-delete)
     -> linking to #api-event-sources-get (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources-get)
     -> linking to #api-event-sources-list (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources-list)
     -> linking to #api-event-sources-update (resolved as: /docs/api/resources/toc/event_sources_toc/#api-event-sources-update)
  - Broken anchor on source page path = /docs/api/resources/toc/event_subscriptions_toc/:
     -> linking to #api-event-subscriptions (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions)
     -> linking to #api-event-subscriptions-create (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions-create)
     -> linking to #api-event-subscriptions-delete (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions-delete)
     -> linking to #api-event-subscriptions-get (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions-get)
     -> linking to #api-event-subscriptions-list (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions-list)
     -> linking to #api-event-subscriptions-update (resolved as: /docs/api/resources/toc/event_subscriptions_toc/#api-event-subscriptions-update)
  - Broken anchor on source page path = /docs/api/resources/toc/failover_backends_toc/:
     -> linking to #api-failover-backends (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends)
     -> linking to #api-failover-backends-create (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends-create)
     -> linking to #api-failover-backends-delete (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends-delete)
     -> linking to #api-failover-backends-get (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends-get)
     -> linking to #api-failover-backends-list (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends-list)
     -> linking to #api-failover-backends-update (resolved as: /docs/api/resources/toc/failover_backends_toc/#api-failover-backends-update)
  - Broken anchor on source page path = /docs/api/resources/toc/http_response_backends_toc/:
     -> linking to #api-http-response-backends (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends)
     -> linking to #api-http-response-backends-create (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends-create)
     -> linking to #api-http-response-backends-delete (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends-delete)
     -> linking to #api-http-response-backends-get (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends-get)
     -> linking to #api-http-response-backends-list (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends-list)
     -> linking to #api-http-response-backends-update (resolved as: /docs/api/resources/toc/http_response_backends_toc/#api-http-response-backends-update)
  - Broken anchor on source page path = /docs/api/resources/toc/https_edge_mutual_tls_module_toc/:
     -> linking to #api-https-edge-mutual-tls-module (resolved as: /docs/api/resources/toc/https_edge_mutual_tls_module_toc/#api-https-edge-mutual-tls-module)
     -> linking to #api-https-edge-mutual-tls-module-replace (resolved as: /docs/api/resources/toc/https_edge_mutual_tls_module_toc/#api-https-edge-mutual-tls-module-replace)
     -> linking to #api-https-edge-mutual-tls-module-get (resolved as: /docs/api/resources/toc/https_edge_mutual_tls_module_toc/#api-https-edge-mutual-tls-module-get)
     -> linking to #api-https-edge-mutual-tls-module-delete (resolved as: /docs/api/resources/toc/https_edge_mutual_tls_module_toc/#api-https-edge-mutual-tls-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/https_edge_tls_termination_module_toc/:
     -> linking to #api-https-edge-tls-termination-module (resolved as: /docs/api/resources/toc/https_edge_tls_termination_module_toc/#api-https-edge-tls-termination-module)
     -> linking to #api-https-edge-tls-termination-module-replace (resolved as: /docs/api/resources/toc/https_edge_tls_termination_module_toc/#api-https-edge-tls-termination-module-replace)
     -> linking to #api-https-edge-tls-termination-module-get (resolved as: /docs/api/resources/toc/https_edge_tls_termination_module_toc/#api-https-edge-tls-termination-module-get)
     -> linking to #api-https-edge-tls-termination-module-delete (resolved as: /docs/api/resources/toc/https_edge_tls_termination_module_toc/#api-https-edge-tls-termination-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/ip_policies_toc/:
     -> linking to #api-ip-policies (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies)
     -> linking to #api-ip-policies-create (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies-create)
     -> linking to #api-ip-policies-delete (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies-delete)
     -> linking to #api-ip-policies-get (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies-get)
     -> linking to #api-ip-policies-list (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies-list)
     -> linking to #api-ip-policies-update (resolved as: /docs/api/resources/toc/ip_policies_toc/#api-ip-policies-update)
  - Broken anchor on source page path = /docs/api/resources/toc/ip_policy_rules_toc/:
     -> linking to #api-ip-policy-rules (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules)
     -> linking to #api-ip-policy-rules-create (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules-create)
     -> linking to #api-ip-policy-rules-delete (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules-delete)
     -> linking to #api-ip-policy-rules-get (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules-get)
     -> linking to #api-ip-policy-rules-list (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules-list)
     -> linking to #api-ip-policy-rules-update (resolved as: /docs/api/resources/toc/ip_policy_rules_toc/#api-ip-policy-rules-update)
  - Broken anchor on source page path = /docs/api/resources/toc/ip_restrictions_toc/:
     -> linking to #api-ip-restrictions (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions)
     -> linking to #api-ip-restrictions-create (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions-create)
     -> linking to #api-ip-restrictions-delete (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions-delete)
     -> linking to #api-ip-restrictions-get (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions-get)
     -> linking to #api-ip-restrictions-list (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions-list)
     -> linking to #api-ip-restrictions-update (resolved as: /docs/api/resources/toc/ip_restrictions_toc/#api-ip-restrictions-update)
  - Broken anchor on source page path = /docs/api/resources/toc/reserved_addrs_toc/:
     -> linking to #api-reserved-addrs (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs)
     -> linking to #api-reserved-addrs-create (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs-create)
     -> linking to #api-reserved-addrs-delete (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs-delete)
     -> linking to #api-reserved-addrs-get (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs-get)
     -> linking to #api-reserved-addrs-list (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs-list)
     -> linking to #api-reserved-addrs-update (resolved as: /docs/api/resources/toc/reserved_addrs_toc/#api-reserved-addrs-update)
  - Broken anchor on source page path = /docs/api/resources/toc/reserved_domains_toc/:
     -> linking to #api-reserved-domains (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains)
     -> linking to #api-reserved-domains-create (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-create)
     -> linking to #api-reserved-domains-delete (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-delete)
     -> linking to #api-reserved-domains-get (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-get)
     -> linking to #api-reserved-domains-list (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-list)
     -> linking to #api-reserved-domains-update (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-update)
     -> linking to #api-reserved-domains-delete-certificate-management-policy (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-delete-certificate-management-policy)
     -> linking to #api-reserved-domains-delete-certificate (resolved as: /docs/api/resources/toc/reserved_domains_toc/#api-reserved-domains-delete-certificate)
  - Broken anchor on source page path = /docs/api/resources/toc/ssh_certificate_authorities_toc/:
     -> linking to #api-ssh-certificate-authorities (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities)
     -> linking to #api-ssh-certificate-authorities-create (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities-create)
     -> linking to #api-ssh-certificate-authorities-delete (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities-delete)
     -> linking to #api-ssh-certificate-authorities-get (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities-get)
     -> linking to #api-ssh-certificate-authorities-list (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities-list)
     -> linking to #api-ssh-certificate-authorities-update (resolved as: /docs/api/resources/toc/ssh_certificate_authorities_toc/#api-ssh-certificate-authorities-update)
  - Broken anchor on source page path = /docs/api/resources/toc/ssh_credentials_toc/:
     -> linking to #api-ssh-credentials (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials)
     -> linking to #api-ssh-credentials-create (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials-create)
     -> linking to #api-ssh-credentials-delete (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials-delete)
     -> linking to #api-ssh-credentials-get (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials-get)
     -> linking to #api-ssh-credentials-list (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials-list)
     -> linking to #api-ssh-credentials-update (resolved as: /docs/api/resources/toc/ssh_credentials_toc/#api-ssh-credentials-update)
  - Broken anchor on source page path = /docs/api/resources/toc/ssh_host_certificates_toc/:
     -> linking to #api-ssh-host-certificates (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates)
     -> linking to #api-ssh-host-certificates-create (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates-create)
     -> linking to #api-ssh-host-certificates-delete (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates-delete)
     -> linking to #api-ssh-host-certificates-get (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates-get)
     -> linking to #api-ssh-host-certificates-list (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates-list)
     -> linking to #api-ssh-host-certificates-update (resolved as: /docs/api/resources/toc/ssh_host_certificates_toc/#api-ssh-host-certificates-update)
  - Broken anchor on source page path = /docs/api/resources/toc/ssh_user_certificates_toc/:
     -> linking to #api-ssh-user-certificates (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates)
     -> linking to #api-ssh-user-certificates-create (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates-create)
     -> linking to #api-ssh-user-certificates-delete (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates-delete)
     -> linking to #api-ssh-user-certificates-get (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates-get)
     -> linking to #api-ssh-user-certificates-list (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates-list)
     -> linking to #api-ssh-user-certificates-update (resolved as: /docs/api/resources/toc/ssh_user_certificates_toc/#api-ssh-user-certificates-update)
  - Broken anchor on source page path = /docs/api/resources/toc/static_backends_toc/:
     -> linking to #api-static-backends (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends)
     -> linking to #api-static-backends-create (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends-create)
     -> linking to #api-static-backends-delete (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends-delete)
     -> linking to #api-static-backends-get (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends-get)
     -> linking to #api-static-backends-list (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends-list)
     -> linking to #api-static-backends-update (resolved as: /docs/api/resources/toc/static_backends_toc/#api-static-backends-update)
  - Broken anchor on source page path = /docs/api/resources/toc/tcp_edge_backend_module_toc/:
     -> linking to #api-tcp-edge-backend-module (resolved as: /docs/api/resources/toc/tcp_edge_backend_module_toc/#api-tcp-edge-backend-module)
     -> linking to #api-tcp-edge-backend-module-replace (resolved as: /docs/api/resources/toc/tcp_edge_backend_module_toc/#api-tcp-edge-backend-module-replace)
     -> linking to #api-tcp-edge-backend-module-get (resolved as: /docs/api/resources/toc/tcp_edge_backend_module_toc/#api-tcp-edge-backend-module-get)
     -> linking to #api-tcp-edge-backend-module-delete (resolved as: /docs/api/resources/toc/tcp_edge_backend_module_toc/#api-tcp-edge-backend-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tcp_edge_ip_restriction_module_toc/:
     -> linking to #api-tcp-edge-ip-restriction-module (resolved as: /docs/api/resources/toc/tcp_edge_ip_restriction_module_toc/#api-tcp-edge-ip-restriction-module)
     -> linking to #api-tcp-edge-ip-restriction-module-replace (resolved as: /docs/api/resources/toc/tcp_edge_ip_restriction_module_toc/#api-tcp-edge-ip-restriction-module-replace)
     -> linking to #api-tcp-edge-ip-restriction-module-get (resolved as: /docs/api/resources/toc/tcp_edge_ip_restriction_module_toc/#api-tcp-edge-ip-restriction-module-get)
     -> linking to #api-tcp-edge-ip-restriction-module-delete (resolved as: /docs/api/resources/toc/tcp_edge_ip_restriction_module_toc/#api-tcp-edge-ip-restriction-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tcp_edge_policy_module_toc/:
     -> linking to #api-tcp-edge-policy-module (resolved as: /docs/api/resources/toc/tcp_edge_policy_module_toc/#api-tcp-edge-policy-module)
     -> linking to #api-tcp-edge-policy-module-replace (resolved as: /docs/api/resources/toc/tcp_edge_policy_module_toc/#api-tcp-edge-policy-module-replace)
     -> linking to #api-tcp-edge-policy-module-get (resolved as: /docs/api/resources/toc/tcp_edge_policy_module_toc/#api-tcp-edge-policy-module-get)
     -> linking to #api-tcp-edge-policy-module-delete (resolved as: /docs/api/resources/toc/tcp_edge_policy_module_toc/#api-tcp-edge-policy-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_certificates_toc/:
     -> linking to #api-tls-certificates (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates)
     -> linking to #api-tls-certificates-create (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates-create)
     -> linking to #api-tls-certificates-delete (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates-delete)
     -> linking to #api-tls-certificates-get (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates-get)
     -> linking to #api-tls-certificates-list (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates-list)
     -> linking to #api-tls-certificates-update (resolved as: /docs/api/resources/toc/tls_certificates_toc/#api-tls-certificates-update)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_edge_backend_module_toc/:
     -> linking to #api-tls-edge-backend-module (resolved as: /docs/api/resources/toc/tls_edge_backend_module_toc/#api-tls-edge-backend-module)
     -> linking to #api-tls-edge-backend-module-replace (resolved as: /docs/api/resources/toc/tls_edge_backend_module_toc/#api-tls-edge-backend-module-replace)
     -> linking to #api-tls-edge-backend-module-get (resolved as: /docs/api/resources/toc/tls_edge_backend_module_toc/#api-tls-edge-backend-module-get)
     -> linking to #api-tls-edge-backend-module-delete (resolved as: /docs/api/resources/toc/tls_edge_backend_module_toc/#api-tls-edge-backend-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_edge_ip_restriction_module_toc/:
     -> linking to #api-tls-edge-ip-restriction-module (resolved as: /docs/api/resources/toc/tls_edge_ip_restriction_module_toc/#api-tls-edge-ip-restriction-module)
     -> linking to #api-tls-edge-ip-restriction-module-replace (resolved as: /docs/api/resources/toc/tls_edge_ip_restriction_module_toc/#api-tls-edge-ip-restriction-module-replace)
     -> linking to #api-tls-edge-ip-restriction-module-get (resolved as: /docs/api/resources/toc/tls_edge_ip_restriction_module_toc/#api-tls-edge-ip-restriction-module-get)
     -> linking to #api-tls-edge-ip-restriction-module-delete (resolved as: /docs/api/resources/toc/tls_edge_ip_restriction_module_toc/#api-tls-edge-ip-restriction-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_edge_mutual_tls_module_toc/:
     -> linking to #api-tls-edge-mutual-tls-module (resolved as: /docs/api/resources/toc/tls_edge_mutual_tls_module_toc/#api-tls-edge-mutual-tls-module)
     -> linking to #api-tls-edge-mutual-tls-module-replace (resolved as: /docs/api/resources/toc/tls_edge_mutual_tls_module_toc/#api-tls-edge-mutual-tls-module-replace)
     -> linking to #api-tls-edge-mutual-tls-module-get (resolved as: /docs/api/resources/toc/tls_edge_mutual_tls_module_toc/#api-tls-edge-mutual-tls-module-get)
     -> linking to #api-tls-edge-mutual-tls-module-delete (resolved as: /docs/api/resources/toc/tls_edge_mutual_tls_module_toc/#api-tls-edge-mutual-tls-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_edge_policy_module_toc/:
     -> linking to #api-tls-edge-policy-module (resolved as: /docs/api/resources/toc/tls_edge_policy_module_toc/#api-tls-edge-policy-module)
     -> linking to #api-tls-edge-policy-module-replace (resolved as: /docs/api/resources/toc/tls_edge_policy_module_toc/#api-tls-edge-policy-module-replace)
     -> linking to #api-tls-edge-policy-module-get (resolved as: /docs/api/resources/toc/tls_edge_policy_module_toc/#api-tls-edge-policy-module-get)
     -> linking to #api-tls-edge-policy-module-delete (resolved as: /docs/api/resources/toc/tls_edge_policy_module_toc/#api-tls-edge-policy-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tls_edge_tls_termination_module_toc/:
     -> linking to #api-tls-edge-tls-termination-module (resolved as: /docs/api/resources/toc/tls_edge_tls_termination_module_toc/#api-tls-edge-tls-termination-module)
     -> linking to #api-tls-edge-tls-termination-module-replace (resolved as: /docs/api/resources/toc/tls_edge_tls_termination_module_toc/#api-tls-edge-tls-termination-module-replace)
     -> linking to #api-tls-edge-tls-termination-module-get (resolved as: /docs/api/resources/toc/tls_edge_tls_termination_module_toc/#api-tls-edge-tls-termination-module-get)
     -> linking to #api-tls-edge-tls-termination-module-delete (resolved as: /docs/api/resources/toc/tls_edge_tls_termination_module_toc/#api-tls-edge-tls-termination-module-delete)
  - Broken anchor on source page path = /docs/api/resources/toc/tunnel_group_backends_toc/:
     -> linking to #api-tunnel-group-backends (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends)
     -> linking to #api-tunnel-group-backends-create (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends-create)
     -> linking to #api-tunnel-group-backends-delete (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends-delete)
     -> linking to #api-tunnel-group-backends-get (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends-get)
     -> linking to #api-tunnel-group-backends-list (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends-list)
     -> linking to #api-tunnel-group-backends-update (resolved as: /docs/api/resources/toc/tunnel_group_backends_toc/#api-tunnel-group-backends-update)
  - Broken anchor on source page path = /docs/api/resources/toc/tunnel_sessions_toc/:
     -> linking to #api-tunnel-sessions (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions)
     -> linking to #api-tunnel-sessions-list (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions-list)
     -> linking to #api-tunnel-sessions-get (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions-get)
     -> linking to #api-tunnel-sessions-restart (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions-restart)
     -> linking to #api-tunnel-sessions-stop (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions-stop)
     -> linking to #api-tunnel-sessions-update (resolved as: /docs/api/resources/toc/tunnel_sessions_toc/#api-tunnel-sessions-update)
  - Broken anchor on source page path = /docs/api/resources/toc/tunnels_toc/:
     -> linking to #api-tunnels (resolved as: /docs/api/resources/toc/tunnels_toc/#api-tunnels)
     -> linking to #api-tunnels-list (resolved as: /docs/api/resources/toc/tunnels_toc/#api-tunnels-list)
     -> linking to #api-tunnels-get (resolved as: /docs/api/resources/toc/tunnels_toc/#api-tunnels-get)
  - Broken anchor on source page path = /docs/api/resources/toc/weighted_backends_toc/:
     -> linking to #api-weighted-backends (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends)
     -> linking to #api-weighted-backends-create (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends-create)
     -> linking to #api-weighted-backends-delete (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends-delete)
     -> linking to #api-weighted-backends-get (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends-get)
     -> linking to #api-weighted-backends-list (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends-list)
     -> linking to #api-weighted-backends-update (resolved as: /docs/api/resources/toc/weighted_backends_toc/#api-weighted-backends-update)
  - Broken anchor on source page path = /docs/integrations/azure-logs-ingestion/event-destination/:
     -> linking to #event-destination (resolved as: /docs/integrations/azure-logs-ingestion/event-destination/#event-destination)
  - Broken anchor on source page path = /docs/k8s/crds/:
     -> linking to #ngrokapicommon (resolved as: /docs/k8s/crds/#ngrokapicommon)
  - Broken anchor on source page path = /docs/k8s/developer-guide/internal-crds/:
     -> linking to #ngrokapicommon (resolved as: /docs/k8s/developer-guide/internal-crds/#ngrokapicommon)

so we don't actually use those tos files anywhere from what i can tell.
i think these are the only ones to fix:
- Broken anchor on source page path = /docs/integrations/azure-logs-ingestion/event-destination/:
     -> linking to #event-destination (resolved as: /docs/integrations/azure-logs-ingestion/event-destination/#event-destination)
  - Broken anchor on source page path = /docs/k8s/crds/:
     -> linking to #ngrokapicommon (resolved as: /docs/k8s/crds/#ngrokapicommon)
  - Broken anchor on source page path = /docs/k8s/developer-guide/internal-crds/:
     -> linking to #ngrokapicommon (resolved as: /docs/k8s/developer-guide/internal-crds/#ngrokapicommon)


Export Session in init

How would this feature be useful?
Currently, if you'd like to annotate nox callbacks, for e.g. type checking, code completion or docstring lookup, you have to import Session from nox.sessions:
import nox
from nox.sessions import Session

@nox.session
def foo(session: Session):
    ...

Re-exporting Session in __init__ would 'jibe' with nox's global object approach and would perhaps make typing in nox more accessible.
Describe the solution you'd like
For the Session class to be imported/re-exported in nox.__init__ so as to not require a separate import.
Describe alternatives you've considered
Importing Session from nox.sessions, as above.

Go for it!
On Thu, Sep 3, 2020 at 11:29 AM layday<EMAIL_ADDRESS>wrote:

How would this feature be useful?
Currently, if you'd like to annotate nox callbacks, for e.g. type
checking, code completion or docstring lookup, you have to import Session
from nox.sessions:
import noxfrom nox.sessions import Session
@nox.sessiondef foo(session: Session):
...
Re-exporting Session in init would 'jibe' with nox's global object
approach and would perhaps make typing in nox more accessible.
Describe the solution you'd like
For the Session class to be imported/re-exported in nox.init so as to
not require a separate import.
Describe alternatives you've considered
Importing Session from nox.sessions, as above.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theacodes/nox/issues/343, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5I47GEB7P5GHB3R6NUPTSD6Y5XANCNFSM4QU4267A
.


Update the generated variable names to conform OE guidelines

This PR updates generated variable names to conform the developer guidelines of OE. The detail includes

No longer use double underscores

__oe_ecalls_table -> oe_ecalls_table (which will be referenced by the OE runtime)
__foo_ocall_function_table -> _foo_ocall_function_table  (only used in the local file)

Add underscore to the local variables
Remove underscore from the struct members

Refer to https://github.com/openenclave/openenclave/issues/3210 for more detail.
Signed-off-by: Ming-Wei Shih<EMAIL_ADDRESS>

Thanks for doing this. Are these the only non-conformant variables, or would there be more?

This should cover all the cases in the oeeger8r-generated code.

Would the user have to make any changes in their code due to the renamed variables?

User shouldn't be affected by these changes.


Fix bio callback backward compatibility

This is an alternative fix for #5488

[x] documentation is added or updated
[x] tests are added or updated

So if this fixes the issue that I reported/attempted to fix in #5488 then I am totally fine with it.
Do you think that it would make sense to extend the testcase to
RSA_print(bio, EVP_PKEY_get1_RSA(key), 0);
or do you think that it won't cover more ground/code than it already does?

Yes, it fixes your issue, and allows BIO_puts to return the correct value.
Additionally it avoids passing pointers to undefined values for BIO_CB_READ
and BIO_CB_WRITE for which now is about the last time we can clean up that kind
of error before 1.1.1 get released.

Do you think that it would make sense to extend the testcase to
RSA_print(bio, EVP_PKEY_get1_RSA(key), 0);

No I think RSA_print uses the same functions, BIO_write and BIO_puts.
But it might be useful to add test cases for BIO_read and BIO_gets,
and various BIO_ctrl code, and for using the new callback as well.
But I think that can be done when an issue is raised with these functions.

Ping, @openssl/omc
could one of you apprive this for the upcoming code-freeze?

Merged, thanks!