Adds the abort reason to signal.reason on cancel

Related to https://github.com/getify/CAF/issues/18
Sweet! This worked out quite well. Good idea, and thanks to your friend as well.
I've added the reason onto the signal in the most basic way here, so let me know if you'd like it done differently.
I can think of one potential error if you call abort twice with different reasons, the 1st reason will be overwritten and it will be wrong in the finally block.
cancelToken.abort('reason1');
cancelToken.abort('reason2');

I don't see any other tests for bad usage of the library though, so let me know if you want me to protect against this or not.

I noticed that the function you had me fix up was called in a different order than the cancelToken.abort(reason)'s rejection/controller.abort, which got me thinking about the ordering of triggered events. Playing around a little more with using the AbortController's abort I came across a few other issues (although not really related to the reason fix here).
var useRawAbortController = true;
QUnit.only( "abort event ordering", async function test(assert){

	function *main(signal, ms) {
		signal.addEventListener('abort', (e) => console.log('--- in abort listener', e))
		signal.pr.catch(e => console.log('--- in signal pr catch', e));
		try {
			for (let i = 0; i < 5; i++) {
				assert.step(`step: ${i}`);
				yield CAF.delay(ms,signal);
			}
		}
		catch (err) {
			console.log('--- in catch ', e)
		}
		finally {
			console.log('--- in finally');
			if (signal.aborted) {
				assert.step("step: in canceled finally");
				assert.ok('reason' in signal, 'signal reason missing');
			}
			else {
				assert.step("step: uhoh signal should be aborted");
			}
		}
	}

	var ac;
	if (useRawAbortController) {
		ac = new AbortController();
	}
	else {
		ac = new CAF.cancelToken();
	}
	main = CAF(main);

	var rExpected = [
		"step: 0",
		"step: 1",
		"step: 2",
		"step: in canceled finally"
	];

	setTimeout(function t(){
		ac.abort();
		ac.abort();
	},50);

	// rActual;
	try {
		await main(useRawAbortController? ac : ac.signal,20);
	}
	catch (err) {
	}

	assert.expect( 6 ); // note: 3 assertions + 4 `step(..)` calls
	assert.verifySteps( rExpected, "ignore canceled after 3 iterations" );
} );

If you drop in this code with useRawAbortController = true it will print:
--- in abort listener { type: 'abort', bubbles: false, cancelable: false }
--- in abort listener { type: 'abort', bubbles: false, cancelable: false }
--- in finally
--- in signal pr catch { type: 'abort', bubbles: false, cancelable: false }

when useRawAbortController = false it prints:
--- in finally
--- in signal pr catch undefined
--- in abort listener { type: 'abort', bubbles: false, cancelable: false }
--- in abort listener { type: 'abort', bubbles: false, cancelable: false }

The order can probably be fixed by internally triggering the abort controller's abort and making sure everything goes through the same code paths instead of having two places that can reject the signal.pr, however a quick test of that broke a lot of tests.
The duplication of the abort listener event is from the once(this.signal, "abort", rej) you had me fix up is actually called twice because of the event ordering on the task queue.
The other difference is that there's a different error thrown into the signal.pr.catch. I'm not entirely sure which one is the desired behaviour. (This is actually the AbortError that I was expecting to get thrown into the catch clause originally.) All the tests pass though, so it's probably not that big of a deal.

Let me know if you want me to create separate issues, or attempt to fix them here as well

BTW, standard AbortSignal instances have an aborted boolean that's set to true once the signal is aborted.
So that's probably the best property to check in the finally clause to determine if the function was canceled. Then this extended reason property we've added can provide additional context to why the cancellation occurred (in case there are multiple reasons for cancellation and they necessitate different clean-up operations).

Great thanks!


MacOS Monterey 12.2: The IP address configured for the host-only network is not within the allowed ranges.

When using "# vagrant up" command I came across an annoying message which I don't want others to encounter:
########################################################
==> server2: Clearing any previously set network interfaces...
The IP address configured for the host-only network is not within the
allowed ranges. Please update the address used to be within the allowed
ranges and run the command again.
Address: <IP_ADDRESS>
Ranges: <IP_ADDRESS>/21
Valid ranges can be modified in the /etc/vbox/networks.conf file. For
more information including valid format see:
https://www.virtualbox.org/manual/ch06.html#network_hostonly
######################################################
So, the way to tackle this problem in my case was to:
--> Create the directory: /etc/vbox/
--> Create the networks.conf file under it and put the above ip network address range inside:
"* <IP_ADDRESS>/24"
Save and quit and then run "# vagrant up" again to see it taking off.
Hope it was helpful.
Follow this link to understand it as well: https://www.sitepoint.com/community/t/homestead-vagrant-ip-address-not-within-allowed-ranges/377751

issues solved


Expose Retry-After value into the exception

Is your feature request related to a problem? Please describe.
Notion exposes a Retry-After after when reaching the rate limit. But the library hides it, forcing the developer to guess as to when to retry.
Describe the solution you'd like
Ideally, the NotionApiException should expose the value, probably as a Timespan?.
Describe alternatives you've considered
We could also consider adding a RateLimitNotionApiException : NotionApiException exception class for this use case.
Additional context
The doc

Related #253

This has been released as part of 4.2.0


v 4+ Add Screwpine  (Pandanus spp.) to species json

Add 'Pandanus spp.' to species.json
https://en.wikipedia.org/wiki/Pandanus#:~:text=Pandanus is a genus of,screw palm%2C and screw pine.

Added in Version 4.1.4 Build 81


[Task]

Description
support config ui theme in System Configuration, remove the theme-button

remove the theme button here.

Task List
No response

I want to help

Still available?

@forcejie welcome, has assgined to you.

@forcejie hi, the config button has done here https://github.com/dromara/hertzbeat/pull/1636
And we need to trigger the actual switching of the page color theme after choosing to switch the theme. Can you help us to work with @TJxiaobao to solve it?
https://github.com/dromara/hertzbeat/pull/1636


Replace utils module

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Having a utils module is considered a code smell in most cases, including this one. It did way too much different stuff and even required circular imports in some places. This PR distributes the code formerly contained in the utils module in a logically coherent manner into new and existing modules. It also includes minor fixups that were necessary to pass all tests; the most notable one being the clear separation of web directory creation, frontend package installation and frontend setup. This fixup should increase testability in general, as the frontend setup called the frontend package installation function in the previous code, which made it way harder to mock said installation.
Type of change
Refactoring
Changes To Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully ran tests with your changes locally?

Seems like from __future__ import annotations was never needed in route.py until now. I think this should fix the workflow errors, but I haven't been able to set rtx up to test with 3.7 or 3.8 yet, so only a rerun will tell for sure.

Forgot to lint the docstrings 🤦♂. Sorry for the delay, should work now.

Thanks for fixing the build! We're cutting a release tonight, I'll merge this in afterwards.

Talked with @ElijahAhianyo offline - looks like this is because we need to update pcweb and pynecone at the same time. I ran the integration test manually and it passed, so I'll merge this in.


Fix requiring files with ES2015 imports in node

The file d3-hierarchy/src/hierarchy/index has ES2015 imports, which means it doesn't play well when importing into NodeJS. We can alternatively get the Node constructor from hierarchy's prototype.

This PR is required for my use case of the flextree-v4 plugin as well (an angular client in a meteor project).


Fix typo on powershell snippet

tldr

@DenisBalan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jborsecnik  Oops, thanks for catching and fixing this! #sign-off


Short solution needed: "How to convert an image to black and white" (python-pillow)

Please help us write most modern and shortest code solution for this issue:
How to convert an image to black and white (technology: python-pillow)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to convert an image to black and white


Remove version: Sogou.SogouInput version <IP_ADDRESS>02

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://ime.sogoucdn.com/sogou_pinyin_<IP_ADDRESS>02.exe
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 910)


SBP: Deposits #3

Is there any possibility that currency_id in send_payment_tx() will match with CurrencyId::Native?
If that is the case then the deposit will be executed as T::NativeCurrency::deposit(who, amount)? in the orml_currencies pallet. It will end up executing deposit_creating() in pallet_balances which might fail if the amount is lower than the ED (existential deposit).
How would you handle this situation? You might end up with some new balance in the Vault but not new native assets minted on chain.

Closing this because the structure of the depositing changed and this does not apply anymore.


Update community.yml

add ,

Hey there,
Is this a duplicate of your pr #287?

Yep, This looks like a duplicate.

sorry,my mistake

@varghesejose2020 Can I close this PR?

@varghesejose2020 Can I close this PR?

@AllanRegush  yes Proceed


sendToBridge Bug ?

I'm going to implement an example of a drop-down refresh, but invoking sendToBridge on onRefresh does not respond to JS onMessage, and I'm sure that sendToBridge is valid on the onBridgeMessage call

hi @ifzm, nothing's jumping out.  Is it something I can download/clone locally to debug?

So sorry. Careful examination revealed that it was my own problem )


Add Masonry Grid Layout for Uploaded Images with Expandable View

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Currently, when users upload images, there is no masonry layout or a way to handle displaying more than three images in a compact and user-friendly manner.
Issue Number: 7
What is the new behavior?
This PR introduces a new feature that allows users to view their uploaded images in a masonry grid layout. When users upload more than three images, the first three images are displayed in a compact masonry grid. If there are more than three images, a +N overlay appears on the third image, indicating the number of additional images. When the user clicks on the +N overlay, the grid expands to show all images.
The update leverages native CSS for the masonry layout, ensuring that the layout is handled efficiently by the browser without the need for additional JavaScript for positioning. This improves both performance and user experience.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@steppy452 @amcdnl Please review this PR when you get a chance.

Hi @amcdnl @steppy452, Thank you for your feedback. I've fixed the issues you pointed out. Please review the changes and let me know your thoughts.

@steppy452, thanks for the review. I addressed your comment and Implemented the maxImageLength variable, let me know what you think.


Option not found

Metric name as 'Requests' is not exist.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ddc18273-8bbe-951d-d6a4-acc903772614
Version Independent ID: 29d66337-5772-6187-b64b-02607a682fe3
Content: Autoscale Azure resources based on performance data or a schedule
Content Source: articles/monitoring-and-diagnostics/monitor-tutorial-autoscale-performance-schedule.md
Service: azure-monitor
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

@uamrit Thanks for the feedback. We are actively investigating and will get back to you soon.

@uamrit To help provide the best answer possible, can you please elaborate by what you mean when you say, "Metric name as 'Requests' is not exist."

@uamrit is this still an issue. Looking forward to your response.

@uamrit We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Feature [#38]: Add support for delete api

Summary

Added delete_api method to the ApiService, enabling users to remove APIs programmatically.
Integrated a new Route to support the delete_api method for seamless API deletion.
Introduced supporting models required for the delete_api functionality.

Checklist

[x] I have run cargo test and all tests pass.
[x] I have run cargo fmt and the code is formatted.
[x] I have run cargo clippy in pedantic mode and refactored.
[x] I have included documentation for any new structs or methods.
[x] I have updated tests for any code I addded/changed/deleted.
[x] I have updated the CHANGELOG to include my changes.

Related Issues

From a glance this looks great. I'll merge and release after work tonight. Thanks for the contribution!

I got another chance to look back at this today.
The Delete API endpoint accepts a request body, not a query parameter - I fixed that for you.
But that begs the question, did you not test this before opening your PR?


🔧 Update pre-commit hooks

Update hooks, fix issues, and also pin dependencies for mypy more strictly (to reduce potential for differences between local and remote runs of mypy)

Thanks for fixing this. 👍 I'm pretty sure that wasn't so easy.


Bug with styled types

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Steps to Reproduce 🕹
When we use Custom props for styled function when get the error:
interface StyledButtonProps {
  type: string;
}
const StyledButton = styled(
  ({ type, ...other }: StyledButtonProps & ButtonProps) => <Button {...other} />
)({
  color: props => (props.type === "test" ? "red" : "green"),
  display: "block"
});

My sandbox https://codesandbox.io/s/hopeful-tesla-e9fut

Tech
Version

Material-UI
v4.9.2

React
16.12.0

Browser
Chrome 80

TypeScript
3.7.5

etc.

Use the generic types of styled like so:
import { DefaultTheme } from '@material-ui/core/styles/defaultTheme';

interface StyledButtonProps {
  type: string;
}
const StyledButton = styled(
  ({ type, ...other }: StyledButtonProps & ButtonProps) => <Button {...other} />
)<DefaultTheme, StyledButtonProps>({
  color: props => (props.type === "test" ? "red" : "green"),
  display: "block"
});

@michelalbers Thanks a lot. Could you please add these examples to the documentation?

@oliviertassinari @mbrookes what the stage for this issue? I think it's a significant case for adding to documentation? or better ts types handling?

Adding @eps1lon who is 100% more skilled in this area than me. (I suspect that this should be ∞, give or take, but I'm not a big proponent of percentages > 100! 😆)

Maybe we should change type of styled to something like that?
type ExtractProps<T> = T extends React.ElementType<infer P> ? P : {};

export type ComponentCreator<Component extends React.ElementType> = <
  Theme = DefaultTheme,
  Props extends {} = ExtractProps<Component>
>(

An update, we have now made enough progress with the new @material-ui/styled-engine package in v5 to move toward a progressive removal of the @material-ui/styles package (based on JSS). The current plan:

In v5.0.beta.0, this package will come standalone, in complete isolation from the rest.
In v5.0.0, this package will be soft deprecated, not promoted in the docs, nor very actively supported.
During v5, work on making the migration easier to the new style API (sx prop + styled() API). We might for instance, invest in the documentation for using react-jss that has more or less the same API. We could also invest in an adapter to restore the previous API but with emotion, not JSS.
In v6.0.0, this package will be discontinued (withStyles/makeStyles API).

This was made possible by the awesome work of @mnajdova.


Add documentation to event_handlers

Current coverage is 100% (diff: 100%)

Merging #368 into 1.0.0 will not change coverage

@@           1.0.0   #368   diff @@
===================================
  Files         23     23
  Lines       1536   1536
  Methods        0      0
  Messages       0      0
  Branches     183    183
===================================
  Hits        1536   1536
  Misses         0      0
  Partials       0      0

Powered by Codecov. Last update 3bdd354...c78d2a0

@kavdev should be g2g now 👍


Upgrade Cosmos SDK

@philipstanislaus it appears CircleCI has failed because it can’t find gometalinter; can you take a look at this again so all the CircleCI tests pass?

@escobyte can you review this PR?

Codecov Report

Merging #36 into master will increase coverage by 9.56%.
The diff coverage is 55.55%.

@@            Coverage Diff            @@
##           master     #36      +/-   ##
=========================================
+ Coverage   54.33%   63.9%   +9.56%
=========================================
  Files          14      14
  Lines         657     676      +19
=========================================
+ Hits          357     432      +75
+ Misses        275     212      -63
- Partials       25      32       +7

Impacted Files
Coverage Δ

app/genesis.go
7.47% <0%> (-0.69%)
:arrow_down:

x/clp/keeper.go
81.41% <100%> (ø)
:arrow_up:

app/app.go
75.21% <87.5%> (+63.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 62ade06...b200a96. Read the comment docs.

Exactly @musnit :) Thanks for the review!


Cookies error

When I try to download course after inputing my udemy username and password it give me error see screenshot attached.

I face the same error.

yes, same here

I am also facing same issue, can you please provide steps ,how you (@penCsharpener ) resolve it

try the procedure here: https://hive.blog/udemy/@dillagr/udemy-trick-you-must-try-workaround

@dillagr thanks for the solution i really appreciate.

it seems the problem is solved with -k switch closing the issue.


[GHSA-hh32-7344-cg2f] Authorization bypass in Spring Security

Updates

Affected products

Comments

CVE-2022-22978 is caused by RegexRequestMatcher.class (https://spring.io/security/cve-2022-22978)
RegexRequestMatcher.class is located in spring-security-web-5.3.4.RELEASE.jar but grype only outputs spring-security-core as a path. (https://github.com/spring-projects/spring-security/blob/main/web/src/main/java/org/springframework/security/web/util/matcher/RegexRequestMatcher.java)

Great find. Thank you much!


[bug] keychain prompt on MacOS

Describe the bug
I develop tauri app on MacOS and every time the app restart in dev mode it opens a dialog and asking for password:

Important info:

It happens on dev mode only, not in production build which I install and open.
I authenticate with twitter.com which uses indexedDB / secure storage
It happens from the second run in dev mode (after the first restart). in the first time it doesn't happen
I can reproduce it in 2 different MacOS computers.
It doesn't happen in regular tauri app, so most probably it's from the use of twitter.com
It's very hard to develop with it as I need to enter my password every reload.

Reproduction
Create tauri app, navigate to twitter and log in. restart the app and navigate to twitter again.
Expected behavior
After the first time you click "Save always" it shouldn't prompt again in dev mode.
Full tauri info output
[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.19.0
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: git+https://github.com/Glitch752/tauri/?branch=feat/multiwebview#e51ea29913f995f03d1f7d3332013c4d1321cb7b (2.0.0-alpha.20)
    - tauri-build [RUST]: no manifest (2.0.0-alpha.13, 2.0.0-alpha.13, 2.0.0-alpha.13)
    - wry [RUST]: 0.35.1
    - tao [RUST]: 0.24.0
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 1.5.9

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

Stack trace
No response
Additional context
I tried to change settings in keychain app, and allow everything, it didn't helped.
I tried also to delete the keys in keychain and restart the app and it didn't helped.
An option to disable secure storage in webkit can help. but I can't find such option

Related issue: #7930


Fetch user information after oauth registration

get the oauth identity after registration https://github.com/rogerthat-platform/rogerthat-backend/blob/31645b770ee70c023a542e52915f3780e69db5f5/src/rogerthat/pages/register_mobile.py#L979
and use the provided information to pre-fill the userprofile with email (@<oauth_domain>), qualified identifier (real email address to be shown in UI), and name
Also extend RegistrationResultTO with this same info

Only implement RegistrationResultTO with extra info


When editing page, textarea for inscription may be nowhere near the photo of the text.

On the edit page the field containing the current inscription text (if any) is displayed below whatever photos of the bench there are. The photo of the inscription is always the top photo. If there is even one photo other than the inscription text, is is impossible to have both the photo of the inscription and the field for the inscription text simultaneously visible in the same browser window on a monitor with a vertical resolution of 1200 pixels. (Many monitors have vertical resolution less than 1200 pixels.)
Moving the inscription text field so it's underneath the photo of the inscription, as it is on the add page, would make editing inscription text easier.

Good plan! I'm planning on moving this project to Gitlab this weekend, so a pull request before then would be useful.


<EMAIL_ADDRESS>started wrapping datetime with quotes in yaml

Describe the bug
We use Netlify CMS with the unpkg link set to version ^2.0.0, and since yesterday copy changes failed our build. I discovered Netlify CMS started wrapping datetime values in doublequotes. Our parses then parsed them as strings instead. Using the Netlify CMS version 2.10.40 fixed the issue for us. We're using the github backend and have no format set on the datetime field.
To Reproduce
Using 2.10.41 save a markdown page with datetime widget. The yaml has added quotes around the field.
Expected behavior
The datetime value should be saved without quotes.
Applicable Versions:

Netlify CMS version: 2.10.41
Git provider: GitHub
OS: Mac OS 10.14.6
Browser version: Firefox 74.0.1

Node.JS version:

CMS configuration
backend:
  name: github
  repo: org/our-repo
  branch: master # Branch to update (optional; defaults to master)
media_folder: 'resources/public/uploads'
public_folder: '/uploads'
publish_mode: editorial_workflow
logo_url: '/images/logo.svg'
collections:
  - name: 'blog'
    label: 'Blog'
    folder: 'content/blog'
    preview_path: blog/{{slug}}
    create: true
    editor:
      preview: false
    fields:
      - { label: "Type", name: "type", widget: "hidden", default: "blog" }
      - { label: "Title", name: "title", widget: "string" }
      - { label: "Publish Date", name: "date", widget: "datetime" }
      - label: "Author"
        name: "author"
        widget: "relation"
        collection: "author"
        searchFields: ["title", "role"]
        valueField: "title"
        displayFields: ["title", "role"]
      - { label: "Featured Image", name: "image", widget: "image", required: false }
      - { label: "Body", name: "body", widget: "markdown" }

Also found this issue from 2018 with similar problem #1271

Duplicate of https://github.com/netlify/netlify-cms/issues/3567, thanks for reporting


Issue while running prepdocs.py script

SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1002)
0%|                                                                                | 0/1 [00:01<?, ?it/s]
Traceback (most recent call last):
File "C:\Users\vk\git\sample-app-aoai-chatGPT-main\scripts\prepdocs.py", line 233, in
create_and_populate_index(

File "C:\Users\vk\git\sample-app-aoai-chatGPT-main\scripts\prepdocs.py", line 137, in create_and_populate_index

@sarah-widder Can you please help me for above mentioned issue .

@sarah-widder Hi , Can you please suggest for above mentioned issue . Its coming while running prepdocs.py

Are you behind a corporate firewall? You might need to add your corporate CA cert to your Python CA file.

@Neil-Schneider yes i am under corporate firewall and app is working fine in my local machine. Its just that after deploying it to azure chat is not working and m getting above error in logs.
I have already created vnet and confirmed that in my app service resource, also enabled access to this web app from selected networks..


Add ability to look up volumes by unambiguous partial name

Fixes #3891
Add the ability to look up volumes based on partial names, so long as the name given is not ambiguous. This is piped into volume remove and volume inspect so we can use those with short names. It is not piped into --volume and --mount for podman run - a full name will still be required there, as we create volumes that don't exist (IE, changing the behavior would break Docker compatibility).

Removing WIP. Should be ready.
This does come with a breaking change to the Varlink volume remove API - we've added a return. CC @jwhonce

@baude PTAL. Note the Varlink changes in particular - anything we need to do to account for this?
@rhatdan @giuseppe @vrothberg @TomSweeneyRedHat Reviews would be appreciated

this LGTM

@rhatdan @baude @vrothberg @giuseppe @TomSweeneyRedHat Tests green, anyone want to merge?

/lgtm


How to let users create subdomains

Hi,
Can you please let me know how to let users create subdomains by providing email address and subdomain name, that way I feel subdomain sites creation will be easy for main site owner and he can manage them easily from admin page if required.
I believe you are already doing this using demo plugin, can you please share code if its possible.

Hi @mazharoddin
I created a plugin to receive the request and then create the demo, please check the screenshot of the code:

Thank you...

I could able to let users create subdomains by providing slug and name by using your plugin code, thanks for sharing it.


Docs fixes after v1.0.0 release

Nice job on the v1.0.0 release!
This PR contains some small fixes to the docs.

Thanks!!


Implements syscall 56

Fixes #368.

Games now reach #369

I'll be honest Ultima, I'm still surprised at how my fest of returning all those syscalls as 0s let me get that far lmao. *Of course, it isn't proper behavior, but it let us see what future syscalls we had to implement.

All of those might not be required in the beginning. For example, if you change the output of is_in_sandbox to 1 it will go to a different syscall.

All of those might not be required in the beginning. For example, if you change the output of is_in_sandbox to 1 it will go to a different syscall.

I might do that and make issues for all of them in case anybody wants to implement the syscalls.

Also, glad you're deciding to take a more verbose approach to logging now. Seeing as Syscalls kinda said nothing a week ago.

Also, why are you defining your own "no such file or directory" error when we have an error code for that already? (Enoent)

The errno is for returning to the PS4.


NOALBS not working properly for me

I don't understand anything about coding so I have no idea what is happening.
All I know everything else is working, video stream, scene switching on http://t2t2.github.io
But the is not connecting. I've edited my info in the config.json but it feels like it's not updating it?
Since it keeps trying to join the #715209 channel instead of my Perceivingmind channel.
Nginx is also running.
And I get this error message:
[5/4/2021] [10:56:53 PM] [OBS] » i  info      Connecting & authenticating
[5/4/2021] [10:56:53 PM] [CHT] » i  info      Connecting to twitch
[5/4/2021] [10:56:53 PM] [OBS] » ×  error     Failed to authenticate
[5/4/2021] [10:56:53 PM] [OBS] » ×  error     Can't connect or lost connnection
[5/4/2021] [10:56:53 PM] [OBS] » i  info      Trying to reconnect in 5 seconds
[5/4/2021] [10:56:54 PM] [CHT] » √  success   Successfully Connected
[5/4/2021] [10:56:54 PM] [CHT] » √  success   Authenticating and joining channel   715209
Anyone that can help me? What am I doing wrong?

Euh. nevermind I guess?
I did something. saved it, opened a folder and now it's working. :'D
Guess I learned something today.


Build canary packages in Linux anaconda-pkg-build container

This unlocks canary builds on linux-{aarch64, ppc64le, s390x} via the multi-arch anaconda-pkg-build container.
Tested here https://github.com/conda/conda/pull/13636

Description

I'm sorry, but this is moving us backwards again on using Anaconda-internal tooling and systems to build things for the OSS conda project, which is what the canary builds are for. Maybe we'll have a publicly maintained docker image in the future to reconsider this.