Allow specifying workspace-specific EnvironmentVariableCollection mutators

For example:
export interface EnvironmentVariableMutator {
	readonly type: EnvironmentVariableMutatorType;
	readonly value: string;
	readonly workspace: Workspace | undefined;
}

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	replace(variable: string, value: string, workspace?: Workspace): void;
	append(variable: string, value: string, workspace?: Workspace): void;
	prepend(variable: string, value: string, workspace?: Workspace): void;
}

Context: https://github.com/microsoft/vscode-python/issues/20492#issuecomment-1380579731

Feedback from API sync:
As we anticipate we might need shell scoping as well in the future, use something similar to
workspace.getConfiguration(section?: string, scope?: ConfigurationScope): WorkspaceConfiguration;

instead.
Updated proposal:
export interface EnvironmentVariableMutator {
	readonly type: EnvironmentVariableMutatorType;
	readonly value: string;
	readonly scope: EnvironmentVariableScope | undefined;
}

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	replace(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	append(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	prepend(variable: string, value: string, scope?: EnvironmentVariableScope): void;
}

export type EnvironmentVariableScope = { workspace?: Workspace };

One issue with this is that readonly scope: EnvironmentVariableScope | undefined; carries optional properties.

One issue with this is that readonly scope: EnvironmentVariableScope | undefined; carries optional properties. Hence an alternative could be:

The required would need to be removed when we added a second one anyway, we can just treat {} and { workspaceFolder: undefined } the same as undefined

Sorry what do you mean by the "second one"? Mostly I was trying to follow Extension-API-guidelines:

For readonly properties on interfaces that VS Code exposes to extensions: Use | undefined as this makes it clear the property exists but has the value undefined.

But I guess we don't have to strictly follow it?

@karrtikr by a second one I mean a second scope, we don't want the user to explicitly enumerate all the scopes to set it which Required<> would do.

Updated proposal:
export interface EnvironmentVariableMutator {
	readonly type: EnvironmentVariableMutatorType;
	readonly value: string;
	readonly scope: EnvironmentVariableScope | undefined;
}

export interface EnvironmentVariableCollection extends Iterable<[variable: string, mutator: EnvironmentVariableMutator]> {
	replace(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	append(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	prepend(variable: string, value: string, scope?: EnvironmentVariableScope): void;
	get(variable: string, scope?: EnvironmentVariableScope): EnvironmentVariableMutator | undefined;
	delete(variable: string, scope?: EnvironmentVariableScope): void;
	clear(scope?: EnvironmentVariableScope): void;
}

export type EnvironmentVariableScope = {
	/**
	* The workspace folder to which this collection applies to. If unspecified, collection applies to all workspace folders.
	*/
	workspaceFolder?: WorkspaceFolder;
};

Closing in favor of https://github.com/microsoft/vscode/issues/182069 as these issues were only open to finalize proposed API.

Moving this out of June as it's a feature request.

Updated proposal
export interface ExtensionContext {
	/**
	 * Gets the extension's environment variable collection for this workspace, enabling changes
	 * to be applied to terminal environment variables.
	 *
	 * @param scope The scope to which the environment variable collection applies to.
	 */
	readonly environmentVariableCollection: EnvironmentVariableCollection & { getScopedEnvironmentVariableCollection(scope: EnvironmentVariableScope): EnvironmentVariableCollection };
}

export type EnvironmentVariableScope = {
	/**
	* Any specific workspace folder to get collection for. If unspecified, collection applicable to all workspace folders is returned.
	*/
	workspaceFolder?: WorkspaceFolder;
};

@karrtikr I was expecting this so it's easier to understand for an API user:
export interface ExtensionContext {
	readonly environmentVariableCollection: EnvironmentVariableCollection;
	getScopedEnvironmentVariableCollection(scope: EnvironmentVariableScope): EnvironmentVariableCollection;
}

That's what I had initially had https://github.com/microsoft/vscode/issues/182069#issuecomment-1544072299, you're the one who recommended that perhaps we should put it inside EnvironmentVariableCollection itself: https://github.com/microsoft/vscode/issues/182069#issuecomment-1544291171 👀

API sync also seemed to be in agreement with that, but maybe we should check again.

@karrtikr my mistake, I forgot some of the conversations as this has gone through a few iterations 😅

Based on discussion in API sync, we should probably deprecate existing environmentVariableCollection API and merge it with the scoped one (similar to workspace.getConfiguration())
export interface ExtensionContext {
	/**
	 * Gets the extension's environment variable collection for this workspace, enabling changes
	 * to be applied to terminal environment variables.
	 *
	 * @deprecated Use {@link getEnvironmentVariableCollection} instead.
	 */
	readonly environmentVariableCollection: EnvironmentVariableCollection;
	/**
	 * Gets the extension's environment variable collection for this workspace, enabling changes
	 * to be applied to terminal environment variables.
	 *
	 * @param scope The scope to which the environment variable collection applies to.
	 */
	getEnvironmentVariableCollection(scope?: EnvironmentVariableScope): EnvironmentVariableCollection;
}

export type EnvironmentVariableScope = {
	/**
	* Any specific workspace folder to get collection for. If unspecified, collection applicable to all workspace folders is returned.
	*/
	workspaceFolder?: WorkspaceFolder;
};

Assigning myself too so it's easier for me to track 🙂

@meganrogge @Tyriar When viewing contributions, is it possible to open the preview of the markdown directly instead of the .md file?

as opposed to

I can open preview using:

@karrtikr since this is an advanced feature I think the raw markdown is more flexible as the user can navigate and copy section of it better. So I don't think this is a necessary change personally

Feedback before finalization:

Add an interface GlobalEnviornmentVariableCollection implements EnvironmentVariableCollection
Add getScoped to the GlobalEnviornmentVariableCollection
Clarify how scoped interacts with the non-scoped collection
Don't deprecate

Updated proposal:
export interface ExtensionContext {
    /**
     * Gets the extension's global environment variable collection for this workspace, enabling changes to be
     * applied to terminal environment variables.
     */
    readonly environmentVariableCollection: GlobalEnvironmentVariableCollection;
}

interface GlobalEnvironmentVariableCollection extends EnvironmentVariableCollection {
    /**
     * Gets scope-specific environment variable collection for the extension. This enables alterations to
     * terminal environment variables solely within the designated scope.
     *
     * Each object obtained through this method is isolated and does not impact objects for other scopes,
     * including the global scope.
     *
     * @param scope The scope to which the environment variable collection applies to.
     */
    getScoped(scope: EnvironmentVariableScope): EnvironmentVariableCollection;
}

export type EnvironmentVariableScope = {
    /**
     * Any specific workspace folder to get collection for. If unspecified, collection applicable to all workspace folders is returned.
     */
    workspaceFolder?: WorkspaceFolder;
};

Each object obtained through this method is isolated and does not impact objects for other scopes, including the global collection.

Should we also call out how it's applied in addition to (and after) the global collection?
Looks good otherwise 👍

Sure, I have modified the docstrings to append it. I plan to have the implementation ready but only merge and adopt it in Python extension next week to avoid multiple iterations.


WIP: Implement API error handling

Context
We currently configured error handling in _app using React ErrorBoundry and the integration of Sentry which handles
Problem or idea
Solution or next step

🗒 Closing for https://github.com/AlexsLemonade/refinebio-web/issues/220 (duplicate), thank you.


updating ycsb version to 0.17

Confirmed with OCS QE team ( consumers/users of Ripsaw ) that they're not using YCSB yet so this change won't affect them

Might need a rebase to get the testing

rebased, and will trigger tests

/rerun all

Results for SNAFU CI Test

Test
Result
Runtime

cluster_loader
FAIL
00:00:00

fio_wrapper
PASS
00:06:56

fs_drift_wrapper
PASS
00:07:20

hammerdb
FAIL
00:13:53

iperf
PASS
00:05:45

pgbench-wrapper
PASS
00:07:15

smallfile_wrapper
PASS
00:06:34

sysbench
PASS
00:05:34

uperf-wrapper
PASS
00:07:01

ycsb-wrapper
PASS
00:13:33

Nothing to do with YCSB. Should be safe to merge.

Needed to revert to rebase/merge.


Scrolling to hash links is broken on Chrome

Describe the bug
Clicking a link like https://kit.svelte.dev/docs/configuration#version should take you to that part of the page. It works in Firefox...

...but not Chrome:

Reproduction
Go to https://kit.svelte.dev/docs/configuration#version in Chrome
Logs
No response
System Info
System:
    OS: macOS 12.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 69.61 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 98.0.4758.109
    Firefox: 97.0.1
    Safari: 15.1
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.30
    @sveltejs/adapter-static: next => 1.0.0-next.28
    @sveltejs/kit: next => 1.0.0-next.291
    svelte: ^3.46.0 => 3.46.4

Severity
annoyance
Additional Information
No response

Testing fix now

You're never going to believe it, but it was introduced in #4155 somehow.

Makes sense, because it scrolls to the correct position temporary and then returns to 0

It's probably something to do with that clientHeight/Width bind, some Chrome edge-case/bug, but no idea how to fix it, maybe there is some other way to do that banner without that bind

Most of the more complicated stuff with the banner is no longer necessary with the shorter message on mobile that doesn't need to wrap. The whole thing should be able to be replaced with an HTML- and CSS-only banner that swaps out messages with media queries.

#4219 it looks like it works.

https://kit-svelte-dev-aigplkaoi-svelte.vercel.app/docs/configuration#version

Actually now it works on some loads and not on others, hmmm, looks like some racing condition

I think I actually figured the root cause of the issue

Closed #4219 it was just hiding the issue, need to investigate deeper.

Before this block of code, the page is correctly scrolled: https://github.com/sveltejs/kit/blob/cdc32a9f4f17d69be6ca1cae58bf3961155545a2/packages/kit/src/runtime/client/client.js#L330-L334
After, it's reset. So it's something to do with the hydration. Trying to create a minimal repro.

I think the browser tries to scroll, but the max scroll(full page height) changes slightly when hydrated(maybe just 1 pixel) and that causes it, but how to solve it is beyond me.

Ok I've managed to at least make a simpler repro: https://stackblitz.com/edit/sveltejs-kit-template-default-pm2sdq?file=src%2Froutes%2Ffails.svelte&terminal=dev
Visit https://sveltejs-kit-template-default-pm2sdq--3000.local.webcontainer.io/ and try going to works and fails. There's something about the combination of {@html ...} and bind:clientHeight that causes the scroll to be reset on hydration.

Just wanted to tell you guys, you are doing great job, I recently tried svelte (kit) and felt like am home 🚀 ( no  jsx, simplicity, chrome lighthouse is very happy ..etc)
I want to help with this but am still a noob,  am learning a lot reading what you're doing guys. Keep it up.
And good luck with this scrolling bug 😊

Ok, so the bug isn't visible in the Svelte REPL for obvious reasons, but I think I have a basic understanding of why it's happening:

On line 32, in the l (cLaim) method, the children of the <main> are being detached. The HTML isn't put back until line 42 in the m (Mount) method. Between claim and mount, the addition of the resize listener is somehow causing Chrome to reset the scroll (presumably Firefox waits until work is complete before assessing whether it needs to). I'm not sure why innerHTML = html doesn't happen during claim. Will raise an issue on the Svelte repo.
So we have lots of fixes to choose from:

move the banner with the bind:clientHeight to below the HTML block
reimplement it so it doesn't need bind:clientHeight
add resize observer bindings to Svelte so it doesn't need to use the resize listener hack
populate {@html ...} tags during claim instead of mount

@Rich-Harris I'm on my phone now, but one solution I can think of is to save scroll position to const before calling new Root
and after it just do
scrollTo(pos.x, pos.y)
I don't it's good to just for it for the docs site because that bug could be happening on some other sites we don't know about.
That's just one of the most simplest solutions but your solutions are definitely better.

Opened https://github.com/sveltejs/svelte/issues/7341

@Rich-Harris It's happening again for me on the docs site, for ex. link https://kit.svelte.dev/docs/routing#advanced-routing-fallthrough-routes you posted in https://github.com/sveltejs/kit/issues/4291#issue-1165916525
Interestingly enough, it happens most of the loads, but not always.

Interestingly enough, it happens most of the loads, but not always.

Same here! Crazy! 😄

@Rich-Harris any idea why this could be happening? because I have none, one workaround I can think of is to check if hash is present and scrollTop is 0, If both are true then we do document.getElementById(location.hash.slice(1)).scrollIntoView() or something like that in client.js but I understand it's bad design.

Hash links are working fine for me in Chrome Version 99.0.4844.84 on a Mac. Am I supposed to do something in particular to reproduce the issue?
https://kit.svelte.dev/docs/configuration#version

Hash links are working fine for me in Chrome Version 99.0.4844.84 on a Mac. Am I supposed to do something in particular to reproduce the issue?
https://kit.svelte.dev/docs/configuration#version

This one is failing for me on the same version of chrome (M1 as well) as you @cliftonlabrum
https://kit.svelte.dev/docs/routing#advanced-routing-fallthrough-routes

It is working fine for me...
Version 1.37.109 Chromium: 100.0.4896.60 (Official Build) (64-bit)

Didn't work for me(Will attach the right version tomorrow)

Can not reproduce the behavior when clicking a link from another page (external or internal), i.e. the links in the Github comments above.
However, when middle-mouse-clicking, ctrl-clicking, or pasting the URL into a new tab, the scroll offset doesn't apply just as described in the issue. The same happens when I modify a link in this issue by adding target="_blank".
I'm not sure if that's supposed to work like that, due to some browser limitations or something, so I'm not sure that helps.
Version 1.37.111 Chromium: 100.0.4896.79 (Official Build) (64-bit)

Used to be broken in Safari as well. But seems to work from version 324

Faced this bug while I was learning sveltekit.
Click on this link (https://kit.svelte.dev/docs/types#generated-types), it doesnt scroll to that position on Chrome. But sometimes it does, very finicky.

I might have happened on a related issue - I'm finding that Chrome 102.0.5005.63 doesn't scroll to hash when the page is doing an inertial scroll from scrolling with a mouse. Hash links work only when the page has completely stopped moving from inertial scrolling.

Can't reproduce this anymore, therefore closing this. The PR that would fix the underlying issue is https://github.com/sveltejs/svelte/pull/7426

Please reopen, middleclicking the link does not scroll to the hash in recen chromium based browsers.

Having the same problem as well when I paste the hask link in Chrome (Chromium).
On the other hand hash links scroll works programaticaly (when generating  table of content links in navigation of my SvelteKit application).

This works now! Thank you :-)


Meeting Topics

Add a page that filters by Meeting Topics. The post tag "topic" will show up on that page, but no others.

Implemented as follows:
meetings.html includes all posts tagged 'meeting'

Switched from tag to category. Category is now "meetings"

Closing. Implemenetd

Implemenetd


No License

AmpharosInTBOI currently doesn't have a license. Under US law, this means that the mod cannot be copied, modified, or distributed. Technically this includes us. I'm sure this is not the intention, so we should probably add some sort of license for clarification. MIT, BSD, WTFPL, CC, and Unlicense seem like good options, though I think MIT is the best in this case.

For reference, here is the entirety of the MIT license.
Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Done and pushed to main


Create a self hosted version of the back-end

Fellow engineer here, I would be happy to help, but it appears this repo is a bit light on documentation on how to run the back-end. Would you be open to getting some support on building this? Perhaps a good first step would be to add a docker-compose file that allows a dev to run this locally.
To keep the plugin under your control, I would suggest to add the option to point it to a self hosted back-end possibly, so people can choose to roll their own backend, offloading the costs for you.

Hey, no need to worry, here is it done: https://github.com/Gabisonfire/torrentio-scraper-sh

Thanks @kubo6472, I'll close this issue.


Docs for sozo account

We added the sozo account command in https://github.com/dojoengine/dojo/pull/1601 but the book isn't updated to include the documentation for it.
Add the documentation for it similar to other commands that we have for sozo.
Ref: https://github.com/dojoengine/dojo/blob/main/bin/sozo/src/commands/account.rs
λ sozo account
Manage accounts

Usage: sozo account [OPTIONS] <COMMAND>

Commands:
  new     Create a new account configuration without actually deploying.
  deploy  Deploy account contract with a DeployAccount transaction.
  fetch   Fetch account config from an already deployed account contract.
  help    Print this message or the help of the given subcommand(s)

Options:
  -v, --verbose...  Increase logging verbosity
  -q, --quiet...    Decrease logging verbosity
  -h, --help        Print help (see more with '--help')
  -V, --version     Print version

Can you assign this to me please?

@jancris100 done! feel free to reach out to me on discord if you have any questions.

Done!

Hi @kariy can you close this task please ? The task is done !


fixed bug in allen temporal relations when two intervals start/end ea…

…ch other

Since tested by Jawad, I merge.


Please add a small video demonstration

It's hard to visualize how your package will look and investing time in adding it first to see how it looks is a huge barrier for entry for most people who hear about this project for the first time.

how can i help with documenting this request? @TheSGJ

Posting here, thought it may serve as quick glance of how it'll look like in Next.js app:
<NextTopLoader showSpinner={true} height={2} color="#1745fb" />

https://github.com/user-attachments/assets/7a996096-3e3b-4b37-917d-db88b30990dc


Engine crashes due to 'Could not make the context current, EGL Error: EGL_BAD_ACCESS (12290)'

Testing the counter app in samsung sm-t110 tablet running android 4.2.2 only shows a blank screen when building with the master channel, in stable channel it works correctly. Tested in release and debug mode.
Output from the terminal:
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(124)] Could not make the context current
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(53)] EGL Error: EGL_BAD_ACCESS (12290)
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(124)] Could not make the context current
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(53)] EGL Error: EGL_BAD_ACCESS (12290)
E/flutter ( 6043): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(44)] Could not make the context current to setup the gr context.
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(124)] Could not make the context current
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(53)] EGL Error: EGL_BAD_ACCESS (12290)
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(124)] Could not make the context current
E/flutter ( 6043): [ERROR:flutter/shell/platform/android/android_context_gl.cc(53)] EGL Error: EGL_BAD_ACCESS (12290)
E/flutter ( 6043): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(236)] Could not make the context current to acquire the frame.

Flutter doctor:
[√] Flutter (Channel master, 1.20.0-3.0.pre.193, on Microsoft Windows [versÃ£o 10.0.18362.900], locale pt-BR)
    • Flutter version 1.20.0-3.0.pre.193 at E:\git\flutter
    • Framework revision 61a04b1551 (3 hours ago), 2020-07-09 15:52:19 +0800
    • Engine revision 0ec6f6c3f2
    • Dart version 2.9.0 (build 2.9.0-21.0.dev 06cb010247)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\angelo\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[!] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

Same as https://github.com/flutter/flutter/issues/51534, where author commented that it doesn't happen with 1.17.x

/cc @jason-simmons

I tried running some apps using the current Flutter master on a Nexus 7 with Android 4.1.2.  I wasn't able to reproduce this.

We need to get a hold of a "Samsung Galaxy Tab 3 Lite" to reproduce this.

I have run git bisect and found that the crash starts at this commit: (https://github.com/flutter/flutter/commit/82187e6b84cc92b18a575e79e082944a20762f6b)
In this revision this error is shown in the debug console:
 orig_eglMakeCurrent:597 error 3002 (EGL_BAD_ACCESS)
In the previous revision the errors EGL Error: EGL_BAD_ACCESS (12290) and Could not make the context current to acquire the frame are still present in the debug console, but the app runs correctly.

Maybe https://github.com/flutter/engine/pull/18670 is related? /cc @blasten

https://github.com/flutter/engine/pull/18670  added additional FML_CHECKs, which might be the change in behavior. I’m still unsure why the app should continue to run even if that error is present.
@chinmaygarde do you plan to order this device?

Still happening on Flutter Stable 2.0.3 and Samsung Galaxy Tab 3 Kids Android 4.1.2.

my android emulator was working prior to upgrading to 2.0.4
[✓] Connected device (4 available)
• AOSP on IA Emulator (mobile) • emulator-5554                        • android-x86    • Android 9 (API 28) (emulator)

Are there any updates on how to fix this issue? I am running into this issue as well since this week when testing the app in release mode. I am on Flutter Channel stable, 2.2.1. and testing on a Samsung Galaxy S3.

Still or also exists in flutter 2.5.3 but only on my Android 4.2.2 test device:
[✓] Flutter (Channel stable, 2.5.3, on Arch Linux 5.15.4-arch1-1, locale de_DE.UTF-8)
    • Flutter version 2.5.3 at /home/marcel/devtools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (vor 6 Wochen), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /home/marcel/Android/Sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 2020.3)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 62.0.1
    • Dart plugin version 203.8452
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Connected device (1 available)
    • GT I8200N (mobile) • 479028a6c2e6b100 • android-arm • Android 4.2.2 (API 17)

We will likely be forced to drop support for API 16-18 (https://github.com/flutter/flutter/issues/109709) so this may soon become no longer applicable.

Since the minimum api support is now 19 and this issue was reported on 16, this issue has become obsolete / stale and isn't valid anymore, so closing as such.


fix: MD036/no-emphasis-as-heading

Fixes #
Docs for Toolkit PR #
What changes to the docs does this PR provide?

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

[ ] Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
[ ] For new pages, used the provided template
[ ] For new features, added an entry in the Table of Contents
[ ] Ran against a spell and grammar checker
[ ] Contains NO breaking changes

Other information

Docs Build status updates of commit 446104a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/controls/TextToolbar.md
:warning:Warning
View
Details

docs/controls/StaggeredPanel.md
:bulb:Suggestion
View
Details

docs/controls/layout/StaggeredLayout.md
:bulb:Suggestion
View
Details

docs/controls/wpf-winforms/WebView.md
:bulb:Suggestion
View
Details

.markdownlint.json
:white_check_mark:Succeeded

docs/animations/ConnectedAnimations.md
:white_check_mark:Succeeded
View

docs/animations/Expressions.md
:white_check_mark:Succeeded
View

docs/controls/LayoutTransformControl.md
:white_check_mark:Succeeded
View

docs/extensions/IconMarkupExtensions.md
:white_check_mark:Succeeded
View

docs/extensions/NullableBoolMarkup.md
:white_check_mark:Succeeded
View

docs/extensions/OnDeviceMarkup.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/Twitter.md
:white_check_mark:Succeeded
View

docs/controls/TextToolbar.md

Line 29, Column 1: [Warning-alt-text-bad-value] Alt text 'TextToolbar' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text.

docs/controls/StaggeredPanel.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

docs/controls/layout/StaggeredLayout.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

docs/controls/wpf-winforms/WebView.md

Line 547, Column 60: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2. Otherwise, remove the view parameter.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a071563:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/controls/TextToolbar.md
:warning:Warning
View
Details

docs/controls/StaggeredPanel.md
:bulb:Suggestion
View
Details

docs/controls/layout/StaggeredLayout.md
:bulb:Suggestion
View
Details

.markdownlint.json
:white_check_mark:Succeeded

docs/animations/ConnectedAnimations.md
:white_check_mark:Succeeded
View

docs/animations/Expressions.md
:white_check_mark:Succeeded
View

docs/controls/LayoutTransformControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView.md
:white_check_mark:Succeeded
View

docs/extensions/IconMarkupExtensions.md
:white_check_mark:Succeeded
View

docs/extensions/NullableBoolMarkup.md
:white_check_mark:Succeeded
View

docs/extensions/OnDeviceMarkup.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/Twitter.md
:white_check_mark:Succeeded
View

docs/controls/TextToolbar.md

Line 29, Column 1: [Warning-alt-text-bad-value] Alt text 'TextToolbar' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text.

docs/controls/StaggeredPanel.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

docs/controls/layout/StaggeredLayout.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 672804b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/controls/TextToolbar.md
:warning:Warning
View
Details

docs/controls/StaggeredPanel.md
:bulb:Suggestion
View
Details

docs/controls/layout/StaggeredLayout.md
:bulb:Suggestion
View
Details

.markdownlint.json
:white_check_mark:Succeeded

docs/animations/ConnectedAnimations.md
:white_check_mark:Succeeded
View

docs/animations/Expressions.md
:white_check_mark:Succeeded
View

docs/controls/LayoutTransformControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView.md
:white_check_mark:Succeeded
View

docs/extensions/NullableBoolMarkup.md
:white_check_mark:Succeeded
View

docs/extensions/OnDeviceMarkup.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/Twitter.md
:white_check_mark:Succeeded
View

docs/controls/TextToolbar.md

Line 29, Column 1: [Warning-alt-text-bad-value] Alt text 'TextToolbar' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text.

docs/controls/StaggeredPanel.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

docs/controls/layout/StaggeredLayout.md

Line 4, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Arranges child elements into a staggered grid pattern.' is duplicated in 'controls/StaggeredPanel.md(4,14)', 'controls/layout/StaggeredLayout.md(4,14)'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Describe how to handle duplicate hook names

See issue #1.

@rrrene @jnbt Can you lend me your :eyes:  please? :)
I'll rebase and merge it later. Thanks!

:sparkling_heart: I like it


Segfault with using external plugin in SRT

Creating an issue, that I have reproduced with the SharkRT fork (not yet with main, but its pretty close).
Repro steps :
Build setup
git clone git@github.com:nod-ai/SRT.git
cd SRT
git checkout mahesh_plugin_error
// build IREE as normal

// Build the plugin
git clone git@github.com:MaheshRavishankar/mlir-toy-bazel.git
cd mlir-toy-bazel
git submodule update --init
git checkout mahesh_plugin_error
CC=clang CXX=clang++ cmake -B build -DCMAKE_BUILD_TYPE=Debug -G Ninja
cmake --build build

Input :
$ cat input.mlir
func.func @mmt4d() -> tensor<4x2048x8x4xf32>
{
  %arg0 = util.unfoldable_constant dense<1.0> : tensor<4x2048x8x1xf32>
  %arg1 = util.unfoldable_constant dense<0.4> : tensor<2048x2048x4x1xf32>
  %cst = arith.constant 0.000000e+00 : f32
  %0 = tensor.empty() : tensor<4x2048x8x4xf32>
  %1 = linalg.fill ins(%cst : f32) outs(%0 : tensor<4x2048x8x4xf32>) -> tensor<4x2048x8x4xf32>
  %2 = linalg.mmt4d ins(%arg0, %arg1 : tensor<4x2048x8x1xf32>, tensor<2048x2048x4x1xf32>)
    outs(%1: tensor<4x2048x8x4xf32>) -> tensor<4x2048x8x4xf32>
  return %2: tensor<4x2048x8x4xf32>
}

$ iree-compile --iree-llvmcpu-enable-microkernels --iree-hal-target-backends=llvm-cpu -o output.vmfb input.mlir
$ iree-run-module --device=local-sync --executable_plugin=mlir-toy-bazel/build/examples/matmul/system_plugin.so --function=mmt4d --module=output.vmfb

stack trace

The segfault is happening on parameter dereference within the system plugin.

Hope this helps
; Symbol: no symbol info
; Source: unknown
7FFFF7FAD61E: 85 C0                      testl  %eax, %eax
7FFFF7FAD620: 75 7B                      jne    0x7ffff7fad69d
7FFFF7FAD622: 49 83 C7 04                addq   $0x4, %r15
7FFFF7FAD626: 49 83 C6 08                addq   $0x8, %r14
7FFFF7FAD62A: 49 81 FF 00 20 00 00       cmpq   $0x2000, %r15  ; imm = 0x2000
7FFFF7FAD631: 0F 85 79 FF FF FF          jne    0x7ffff7fad5b0
7FFFF7FAD637: 48 8B 8D 68 FF FF FF       movq   -0x98(%rbp), %rcx
7FFFF7FAD63E: 48 FF C1                   incq   %rcx
7FFFF7FAD641: 49 81 C4 00 20 00 00       addq   $0x2000, %r12  ; imm = 0x2000
7FFFF7FAD648: 48 83 F9 20                cmpq   $0x20, %rcx
7FFFF7FAD64C: 0F 85 DE FE FF FF          jne    0x7ffff7fad530
7FFFF7FAD652: 48 8B 8D 78 FF FF FF       movq   -0x88(%rbp), %rcx
7FFFF7FAD659: 48 FF C1                   incq   %rcx
7FFFF7FAD65C: 48 81 45 B8 00 40 00 00    addq   $0x4000, -0x48(%rbp)  ; imm = 0x4000
7FFFF7FAD664: 48 83 F9 04                cmpq   $0x4, %rcx
7FFFF7FAD668: 0F 85 A2 FE FF FF          jne    0x7ffff7fad510
7FFFF7FAD66E: 48 8B 4D C0                movq   -0x40(%rbp), %rcx
7FFFF7FAD672: 48 03 4D 88                addq   -0x78(%rbp), %rcx
7FFFF7FAD676: 48 8B 45 C8                movq   -0x38(%rbp), %rax
7FFFF7FAD67A: 48 03 45 80                addq   -0x80(%rbp), %rax
7FFFF7FAD67E: 48 89 45 C8                movq   %rax, -0x38(%rbp)
7FFFF7FAD682: 48 89 C8                   movq   %rcx, %rax
7FFFF7FAD685: 48 89 4D C0                movq   %rcx, -0x40(%rbp)
7FFFF7FAD689: 48 81 F9 00 08 00 00       cmpq   $0x800, %rcx  ; imm = 0x800
7FFFF7FAD690: 0F 8C 6A FE FF FF          jl     0x7ffff7fad500
7FFFF7FAD696: E9 35 FE FF FF             jmp    0x7ffff7fad4d0
7FFFF7FAD69B: 31 C0                      xorl   %eax, %eax
7FFFF7FAD69D: 48 8D 65 D8                leaq   -0x28(%rbp), %rsp
7FFFF7FAD6A1: 5B                         popq   %rbx
7FFFF7FAD6A2: 41 5C                      popq   %r12
7FFFF7FAD6A4: 41 5D                      popq   %r13
7FFFF7FAD6A6: 41 5E                      popq   %r14
7FFFF7FAD6A8: 41 5F                      popq   %r15

unfortunately doesn't make sense to me (unless your screenshot was taken in a different run, as the address is not nearby what you posted)
I'd try disabling link-embedded to see if it isolates to that, but am not sure what it'd imply if it was isolated to that.

unfortunately doesn't make sense to me (unless your screenshot was taken in a different run, as the address is not nearby what you posted)
I'd try disabling link-embedded to see if it isolates to that, but am not sure what it'd imply if it was isolated to that.

I am not sure I follow. I took the stack trace and just posted what it pointed to in the third entry there. I am happy to get on GVC to discuss more. The high bandwidth might help understand more of what you are looking for.

the fault address here:
is not the code address here:
7FFFF7FAD61E: 85 C0                      testl  %eax, %eax
and since that's not a memory op I have no idea where the fault address would be coming from

Ok, yeah, this is kind of the issue I am having... I understand what you are saying, but that address makes no sense to me. Thats why I have a hunch that something in the way the system_plugin set up here https://github.com/MaheshRavishankar/mlir-toy-bazel/blob/main/examples/matmul/system_plugin.c is the issue.


Make MergeRight, MergeLeft and MergeRecord homomorphic

Type

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description

Related

Related Issue #
Closes # https://github.com/Effect-TS/effect/issues/3823

Thanks @KhraksMamtsov


How to use this plugin to generate a pod for iOS project to use

Hi, body, as title said, I want to generate a cocoapods for iOS project as our project use cocoapods as module manager, I'v read the README.md, but can't find how to use it to generate a pod, Any step for me to achieve that?
FYI:Comes from here: https://kotlinlang.slack.com/archives/C3SGXARS6/p1603028341199400?thread_ts=1602236811.143200&cid=C3SGXARS6

Hi @wuseal,
this plugin cannot create a Pod. It can create an XCFramework and a matching Package.swift file.
For integration of Kotlin Multiplatform projects with Cocoapods please take a look at the Cocoapods Plugin: https://kotlinlang.org/docs/reference/native/cocoapods.html

Hi @wuseal,
this plugin cannot create a Pod. It can create an XCFramework and a matching Package.swift file.
For integration of Kotlin Multiplatform projects with Cocoapods please take a look at the Cocoapods Plugin: https://kotlinlang.org/docs/reference/native/cocoapods.html

@ge-org Thank you for quick reply, Yeah, I'v used cocoapods plugin, this is my demo:
https://github.com/wuseal/Idle
I created a release version pod by using your plugin now, I tested it and works fine.
Now  I have another question:
How to create XCFramework within DEBUG and RELEASE together and link it in podspec here: https://github.com/wuseal/Idle/blob/2e241d5c285d396b0a49d7dd3a748ff94bca7f86/Idle.podspec#L11

@ge-org Thank you for quick reply, Yeah, I'v used cocoapods plugin, this is my demo:
https://github.com/wuseal/Idle
I created a release version pod by using your plugin now, I tested it and works fine.
Now  I have another question:
How to create XCFramework within DEBUG and RELEASE together and link it in podspec here: https://github.com/wuseal/Idle/blob/2e241d5c285d396b0a49d7dd3a748ff94bca7f86/Idle.podspec#L11

Hi @wuseal,
sorry for the late reply. There's no way to include a debug and a release build in the same xcframework at the moment. You could create two pods instead.


Onboard iaas server group

Latest iaasalpha SDK release removes the methods for managing server groups but doesn't provide any replacements. We must wait for new endpoints to be added before this PR can be continued to work on


Emscription 3.1.56

This PR resolves https://github.com/woodser/monero-ts/issues/144

Thanks.
Running the sample code, I get this error:
Error [ReferenceError]: asyncifyStubs is not defined
    at LibraryUtils.deserializeError (/Users/woodser/git/monero-ts/dist/src/main/ts/common/LibraryUtils.js:253:106)
    at LibraryUtils.invokeWorker (/Users/woodser/git/monero-ts/dist/src/main/ts/common/LibraryUtils.js:242:26)
    at async MoneroWalletFullProxy.openWalletData (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:1843:5)
    at async MoneroWalletFull.openWalletData (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:1602:25)
    at async MoneroWalletFull.openWallet (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:144:20)
    at async TestUtils.getWalletFull (/Users/woodser/git/monero-ts/dist/src/test/utils/TestUtils.js:232:32)
    at async Context.<anonymous> (/Users/woodser/git/monero-ts/dist/src/test/TestSampleCode.js:32:20)
Worker error: ReferenceError: asyncifyStubs is not defined
    at /Users/woodser/git/monero-ts/dist/dist/monero_wallet_full.js:8:19712
    at Function.loadFullModule (/Users/woodser/git/monero-ts/src/main/ts/common/LibraryUtils.ts:109:70)
    at openWalletData (/Users/woodser/git/monero-ts/src/main/ts/wallet/MoneroWalletFull.ts:1616:37)
    at Function.openWallet (/Users/woodser/git/monero-ts/src/main/ts/wallet/MoneroWalletFull.ts:144:43)
    at apply (/Users/woodser/git/monero-ts/src/main/ts/common/MoneroWebWorker.ts:421:58)
    at self.onmessage (/Users/woodser/git/monero-ts/src/main/ts/common/MoneroWebWorker.ts:49:68)
    1) "before all" hook for "Sample code demonstration"

Which has a related issue which was recently fixed and closed, so it's in the next release of emscripten: https://github.com/emscripten-core/emscripten/issues/21104#event-12329214343

Please remove the ./dist assets from the PR. Those can be updated and committed later.

Please remove the ./dist assets from the PR. Those can be updated and committed later.

Done

is this PR mergeable for now?

For now I'd rather wait to confirm it works in the next release than changing these values in the current release.

Thanks.
Running the sample code, I get this error:
Error [ReferenceError]: asyncifyStubs is not defined
    at LibraryUtils.deserializeError (/Users/woodser/git/monero-ts/dist/src/main/ts/common/LibraryUtils.js:253:106)
    at LibraryUtils.invokeWorker (/Users/woodser/git/monero-ts/dist/src/main/ts/common/LibraryUtils.js:242:26)
    at async MoneroWalletFullProxy.openWalletData (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:1843:5)
    at async MoneroWalletFull.openWalletData (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:1602:25)
    at async MoneroWalletFull.openWallet (/Users/woodser/git/monero-ts/dist/src/main/ts/wallet/MoneroWalletFull.js:144:20)
    at async TestUtils.getWalletFull (/Users/woodser/git/monero-ts/dist/src/test/utils/TestUtils.js:232:32)
    at async Context.<anonymous> (/Users/woodser/git/monero-ts/dist/src/test/TestSampleCode.js:32:20)
Worker error: ReferenceError: asyncifyStubs is not defined
    at /Users/woodser/git/monero-ts/dist/dist/monero_wallet_full.js:8:19712
    at Function.loadFullModule (/Users/woodser/git/monero-ts/src/main/ts/common/LibraryUtils.ts:109:70)
    at openWalletData (/Users/woodser/git/monero-ts/src/main/ts/wallet/MoneroWalletFull.ts:1616:37)
    at Function.openWallet (/Users/woodser/git/monero-ts/src/main/ts/wallet/MoneroWalletFull.ts:144:43)
    at apply (/Users/woodser/git/monero-ts/src/main/ts/common/MoneroWebWorker.ts:421:58)
    at self.onmessage (/Users/woodser/git/monero-ts/src/main/ts/common/MoneroWebWorker.ts:49:68)
    1) "before all" hook for "Sample code demonstration"

Which has a related issue which was recently fixed and closed, so hopefully it's in the next release of emscripten: emscripten-core/emscripten#21104 (comment)

3.1.57 is out, however there still seem to be some issues. It can build the distributable fine.
This is output from running npm test on the head of this pr branch.
https://gist.github.com/NorrinRadd/d7168dfff5c5293526dd38e12dd388b3
3.1.57 will complain about no thread support if run on the master branch.
3.1.10 will run tests fine on the master branch.

I'm getting errors running with emscripten 3.1.57:
/Users/woodser/git/monero-ts/build/boost/include/boost/config/requires_threads.hpp:47:5: error: "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)"
   47 | #   error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)"
      |     ^
In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/crypto/crypto.cpp:37:
In file included from /Users/woodser/git/monero-ts/build/boost/include/boost/thread/mutex.hpp:12:
/Users/woodser/git/monero-ts/build/boost/include/boost/thread/detail/platform.hpp:71:9: error: "Sorry, no boost threads are available for this platform."
   71 | #       error "Sorry, no boost threads are available for this platform."
      |         ^
In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/crypto/crypto.cpp:37:
/Users/woodser/git/monero-ts/build/boost/include/boost/thread/mutex.hpp:18:2: error: "Boost threads unavailable on this platform"
   18 | #error "Boost threads unavailable on this platform"
      |  ^

Be sure to delete all the build folders before building, and you should see the same error with ./bin/build_all.sh:
rm -rf ./build && rm -rf ./external/monero-cpp/external/boost-sdk && rm -rf ./external/monero-cpp/external/openssl-sdk

I'm getting errors running with emscripten 3.1.57:
/Users/woodser/git/monero-ts/build/boost/include/boost/config/requires_threads.hpp:47:5: error: "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)"
   47 | #   error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)"
      |     ^
In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/crypto/crypto.cpp:37:
In file included from /Users/woodser/git/monero-ts/build/boost/include/boost/thread/mutex.hpp:12:
/Users/woodser/git/monero-ts/build/boost/include/boost/thread/detail/platform.hpp:71:9: error: "Sorry, no boost threads are available for this platform."
   71 | #       error "Sorry, no boost threads are available for this platform."
      |         ^
In file included from /Users/woodser/git/monero-ts/external/monero-cpp/external/monero-project/src/crypto/crypto.cpp:37:
/Users/woodser/git/monero-ts/build/boost/include/boost/thread/mutex.hpp:18:2: error: "Boost threads unavailable on this platform"
   18 | #error "Boost threads unavailable on this platform"
      |  ^

Be sure to delete all the build folders before building, and you should see the same error with ./bin/build_all.sh:
rm -rf ./build && rm -rf ./external/monero-cpp/external/boost-sdk && rm -rf ./external/monero-cpp/external/openssl-sdk

that is what i get if I run on the master branch.  I just ran that rm command and built again on this pr branch and it finished building fine. the new output of npm test is here: https://gist.github.com/NorrinRadd/0cb2b5d81aac0ac23ca751a448f7e385

Excellent, it's building for me too, so I must have done something wrong last time.
So two issues I'm seeing:

Running npm run test -- --grep "TEST MONERO UTILITIES" gives the error "TypeError: _LibraryUtils.default.getWasmModule(...)._free is not a function", which hopefully you can recreate.

Running "Sample code demonstration" in the browser gives error: "ReferenceError: SharedArrayBuffer is not defined". We want to keep the final output single threaded now to avoid these new requirements, until after the emscripten upgrade.

So two issues I'm seeing:
1. Running `npm run test -- --grep "TEST MONERO UTILITIES"` gives the error "TypeError: _LibraryUtils.default.getWasmModule(...)._free is not a function", which hopefully you can recreate.

I just pushed a fix for this.

2. Running "Sample code demonstration" in the browser gives error: "ReferenceError: SharedArrayBuffer is not defined". We want to keep the final output single threaded now to avoid these new requirements, until after the emscripten upgrade. I'm hoping this can merely be an emscripten linker flag until we turn it on.

I cannot reproduce this. When I press the Sample Code button, nothing happens.

@woodser  ^

npm run test -- --grep "TEST MONERO UTILITIES" is fixed with the malloc and free exports.
Running npm run test -- --grep "Sample code demonstration" fails with error "memory access out of bounds" in node.js and "SharedArrayBuffer is not defined" in the browser.
I think the first step is to ensure this test passes for you before any of these changes (i.e. based on master and with emscripten 3.1.10), so you have a successful baseline.
After that test is passing, you should be able to observe the errors by applying the changes in this PR and updating to the latest emscripten.


Full naming support for route tables rather than just the prefix

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
While using this module, route tables are created called, nat-route and internet-route. There is a support for adding a prefix using var.label_prefix but what I would like is to make this entire name configurable rather than just the prefix
New or Affected Resource(s)
Route table display names
Potential Terraform Configuration

# Copy-paste any Terraform configurations for how the requested feature may be used.

References

Resolved in https://github.com/oracle-terraform-modules/terraform-oci-vcn/pull/137


Print: Entry, ":0:shortcut", Does Not Exist

Hi,
i get the same error that has been mentioned here before:
https://github.com/warpling/Macmoji/pull/26#issuecomment-251603791
Macmoji-master % ./scripts/macmoji install
./scripts/macmoji: line 8: realpath: command not found
Installing Macmoji text replacements...
Print: Entry, ":0:shortcut", Does Not Exist

Hi @Tealk, I've removed the install script since I wasn't able to find a way to get it working again with the changes in the last new macOS versions. Sorry about this. Hope you were able to install it okay with the drag/drop method :)


Getting warning with NS 6.5.1

Am getting the following warning when building - ok?
CONSOLE WARN file: node_modules/@nativescript/core/ui/tab-view/tab-view.ios.js:17:0: Objective-C class name "UITabBarControllerImpl" is already in use - using "UITabBarControllerImpl1" instead.
CONSOLE WARN file: node_modules/@nativescript/core/ui/tab-view/tab-view.ios.js:78:0: Objective-C class name "UITabBarControllerDelegateImpl" is already in use - using "UITabBarControllerDelegateImpl1" instead.
CONSOLE WARN file: node_modules/@nativescript/core/ui/tab-view/tab-view.ios.js:116:0: Objective-C class name "UINavigationControllerDelegateImpl" is already in use - using "UINavigationControllerDelegateImpl1" instead.

This seems like a runtime warning. Can you share what kind of project are you using and how do you reproduce it. These logs signal that most probably the tab-view module is being loaded for the second time. This could happen due to various reasons (e.g. workers, HMR, ...)


[AppConfiguration] Implemented ETag-by-page feature

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Data.AppConfiguration


pull request for e2e test at 01/29/2017 00:15:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


What are the miner fees?

What are the miner fees in loaf wallet? Is there any option to configure it or see it in the wallet? I installed the wallet but I don't have ltc - how can i check the miner fees?

If you try to send coins, you will see an option for fees. There is an economy fee, and an express fee. At the moment, due to lack of congestion in the Litecoin Network, both should let your transactions get confirmed in the next block.


Improve display message shown

Codecov Report
Base: 70.56% // Head: 70.58% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (8ec969f) compared to base (83f2fd8).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #74      +/-   ##
============================================
+ Coverage     70.56%   70.58%   +0.02%
  Complexity      382      382
============================================
  Files            70       70
  Lines          1206     1207       +1
  Branches        117      117
============================================
+ Hits            851      852       +1
  Misses          319      319
  Partials         36       36

Impacted Files
Coverage Δ

src/main/java/gim/logic/commands/AddCommand.java
100.00% <ø> (ø)

...rc/main/java/gim/logic/commands/DeleteCommand.java
100.00% <ø> (ø)

src/main/java/gim/logic/commands/ExitCommand.java
100.00% <ø> (ø)

src/main/java/gim/logic/commands/HelpCommand.java
100.00% <ø> (ø)

src/main/java/gim/logic/commands/ListCommand.java
100.00% <ø> (ø)

src/main/java/gim/model/exercise/Exercise.java
95.34% <100.00%> (+0.11%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Enhancement: Implement way to handle gzipped tar files in the tar extractor

Tar extraction cannot handle gzipped tar files. It should be possible to handle this however, it is somewhat diffcult as the content-type is application/gzip special casing might be needed for files of extension .tar.gz or .tgz to have a magic contentType returned.
This is not a huge priority but I've seen a few  issues where the downloaded file is .tar.gz and the current .tar implementation does not handle it well.

Duplicate of #1


Persistant damage applied to both selected token and target

Hi, I have an issue that appeared when using the "Apply persistant damage" button that adds the damage to both selected token and target.
Tested with :

System 4.6.3
Persistant damage 0.11.2
Target damage 1.5.3
Option to hide standard damage button ON
No other module activated

After a reboot I am not able to reproduce the issue, so it's all good I presume

Fixed in 1.5.4


gdrcopy is not working properly

Hello guys,
I build from source gdrcopy using master branch on my Clara AGX which have dGPU RTX 6000
Linux kernel version is 4.9.201
I tried sanity, copybw and copylat tools but it doesn't work properly.
Kindly see my logs below.

gdrcopy kernel module

nvidia@nvidia-tegra:~/devel/gdrcopy$ lsmod | grep -i "gdrdrv"
gdrdrv                 17384  0
nvidia              34654122  221 gdrdrv,nvidia_modeset,nvidia_uvm
nvidia@nvidia-tegra:~/devel/gdrcopy$ cat /proc/modules | grep -i "gdrdrv"
gdrdrv 17384 0 - Live 0x0000000000000000 (PO)
nvidia 34654122 221 gdrdrv,nvidia_uvm,nvidia_modeset, Live 0x0000000000000000 (PO)
nvidia@nvidia-tegra:~/devel/gdrcopy$

dGPU RTX 6000 kernel module version

nvidia@nvidia-tegra:~/devel/gdrcopy$ sudo modinfo nvidia | grep -i "version"
version:        460.73.01
srcversion:     125B3A69C5589D51F81E2B6
vermagic:       4.9.201-tegra SMP preempt mod_unload modversions aarch64
nvidia@nvidia-tegra:~/devel/gdrcopy$

running tools

nvidia@nvidia-tegra:~$ sudo sanity
Running suite(s): Sanity
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
Assertion "(read(read_fd, &cont, sizeof(int))) == (sizeof(int))" failed at sanity.cpp:865
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?
gdr_open error: Is gdrdrv driver installed and loaded?

Thanks

I found my the root cause. the driver gdrdrv doesn't create gdrdrv device.
I used insmod.sh script and after that all works fine.
FYI, I used modprobe command line instead of insmod.sh script.
I think gdrdrv driver should create the device when loading. I will try to add device creation and submit a PR when I have time


Zoom with mousewheel

Just had the idea to enable the mousewheel for zooming the image insteat or in addition to the slider. What do you thing is this a good idea or would it confuse the users?

Closing due to inactivity.

I was able to get this working, at least in Chrome.
function BindMouseWheelScrollEvents() {
    $('#divID').bind('mousewheel', function (e) {
            e.preventDefault();

                    var $slider = $(".cropit-image-zoom-input");
                    var currVal = parseFloat($slider.val());
                    var increment = (e.originalEvent.wheelDelta > 0) ? 0.1 : (0.1 * -1);
                    var newVal = currVal + increment;

                    $slider.val(newVal);
                    slider.trigger("change"); // This triggers the CropIt code for slider/range changes.
            });
        }`


Improve remark on UDP/TCP for high availability

A lot of people (including myself) seem to struggle with setting up high availability. I think it makes sense to improve the remarks on UDP/TCP for high availability.

@pascal-hofmann you need to sign off your last 3 commits to pass DCO check. Just run:
git filter-branch -f --commit-filter 'git commit-tree -S "$@"' HEAD~3..HEAD
git push --force

@pascal-hofmann you need to sign off your last 3 commits to pass DCO check. Just run:
git filter-branch --msg-filter 'cat - && echo && echo "Signed-off-by: Pascal Hofmann<EMAIL_ADDRESS>" "$@";' HEAD~3..HEAD
git push --force

Thanks for the detailed instructions and sorry for the delay. It was a busy week for me… :)

Thanks!


Can't remove entries in Relations to Other Signs

The trash can shows, but clicking it has no effect.

Same goes for relations to Foreign Signs. I solved this problem the classic way: I got all frustrated for not being able to find the problem for over 60 minutes, and when I got back from lunch I saw it in 5 minutes :).

Haha! Long live lunch.


New app. Golf View

This app aims to fill the same functionality as golf specific smartwatches. It uses OpenStreetMap to fetch course geometry and measure real time distance to golf holes.

Wow, this looks awesome! I'm not a golf player but I love the idea of dragging all the course info off openstreetmap. There must be other sports that could do stuff like this too


How to synchronize different tasks to one git branch?

@wangzyon , please ask such questions on our gitter channel: https://gitter.im/opencv-cvat/public.


Berserk Coloured Source

https://berserkcolored.com/
I was hoping it could be created into a source

I second this, looks amazing!

Upvote!!


Edit handler heading override

Pulled out from https://github.com/wagtail/wagtail/pull/5868 as requested to ensure this is added to release notes:
Adds the ability to override a FieldPanel's heading by providing it explicitly in the constructor. (Previously this would be overridden as soon as a field was bound by the form field's label)
Adds a test for this new function

Merged in 526649008da4c58a5c9afed263932a8791a6e9ab - thanks @jacobtoppm!


Added Scatter data and aannotation data + more control over title and…

Added Scatter data for points with precise size and colour control and colour axis and annotation data to tag specific points + more control over title and legend.

Will check the tests soon

I made another push to the repo today. Can you check if its ok?

Regarding tests: you should be able to run them in your IDE, and see which one pass and which one not, it would be really nice to refactor them so they will pass, and add few of them to unit test also your part. If you need more info about it: let me know.

Graph Axis with colour range should be optional IMO

Point Annotation is OK

For some reason I still can't get the Scatter Data, can you add some example .gh file in repo so I could try it?

Regarding SVG: I'd say that if it is not that much reliable, then it is better to not add it at all. Later people will brag about that we should fix this or that.

Really nice icons! It 100% match existing ones.

If you have the graph axis optional how do you see the C values of the of the scatter data? Imagine its like a building plan that shows x and y but the colour parameter Values (not colour itself) is the Z dimension number, so you have to read what the colour corresponds to from the colour axis. Do you have another way to read it in mind? Btw I fixed axes now and you can add different gradients and they will show. See the example.gh
I still don't know how to run the tests : ) I'm not really  a programmer but rather an architect that learned in high school. Is there a menu option or something I can use? But to be honest I'm doing PhD now and have to submit pretty soon so not sure I will have time before July to do the tests. For now just want to make sure everything works so I can make the data graphs for the paper with the added bonus of contributing here :)
I pushed a definition so that you can see how I used it.
And can we please keep the svg in code but never mention anywhere on messages or interface that exists. Only two of us and people that read this can use it knowing it is not perfect so they will not complain as it does not depend on us but the OxyPlot back end. I think its quite good to get the data in vector format and the text doesn't matter so much sometimes or you can easily change it in illustrator.
Thanks for the icons actually I used the original ones and modified them inside VS so that they fit perfectly with the rest of the theme.

Hi!

Regarding optional colour range: I get that, but it looks a bit strange if you'd like to have simple axises, because you have only X,Y values, and still it shows you a color range for nothing. I believe it should either detect if someone is using this additional data and then apply this range next to axises, or just add separate compoenent, so if someone will need axises+range then he will use it, and if not then he will use it axises only.
Regarding tests ok
Regarding svg: I try to avoid hidden features ;)

Recently I'm constantly working on another project, that's why I'm not here all the time, but will try to keep in touch :)

because you have only X,Y values, and still it shows you a color range for nothing
I don't understand what you mean. Are you seeing the colour axis even if you don't use the Scatter Data component? Can you show me an example gh file or image so that I know what you mean?

or just add separate compoenent, so if someone will need axises+range then he will use it
I think that's why I made the scatter data component to display that range. Maybe if the component name is Gradient Data it will make more sense? Next to axis you mean on the x or y axis? If so I'm not sure oxyplot supports having dual values on one axis?

Regarding svg: I try to avoid hidden features ;)
That's ok.

I have tested it during last week and it works as expected but maybe the terminology and component name should be changed. I have updated the branch just now.

Hi, will check it out probably next week, and will let you know ;)

Hello, did you have any time recently to have a look at the latest updates? I fixed some of the annoyances and I think is usable with no problems.

Hey, great, I will probably have some time next week. Will let you know ;)


Re-investigate Parboiled 2

Can we move off the old parboiled parser to the newer, maintained one?
Questions:

What does it look like to call into generated Scala code from Kotlin?
What would a Maven build look like for code generation vs SBT?

Parboiled 2 is Scala only, and needs the Scala compiler in the build.


Add first currency as default

Hello,
As we are not using USD as default currency we want to be able to select the first currency from the ChoiceSet as default as we'd like to avoid changing it every time we create a contract.
With this modification we can used the FIELD_CHOICES and the first element of the list will be proposed as default.
For configuration without FIELD_CHOICES no changed as USD is still the first choice.

    CHOICES = [
        (CURRENCY_USD, 'USD'),
        ('eur', 'EUR'),
        ('chf', 'CHF'),
    ]

Change will be available in version 2.2.8.


Failed to execute 'removeChild' on 'Node' React issue after 5.0 update due to innerHTML being wrapped

There is an issue now with React and using ReactDOM.createPortal(children, rootElemRef.current) where rootElemRef is an actual reference in addOverlay and the children are whatever you would put inside an overlay- (basic idea for wrapper taken from here)
viewer.addOverlay({
        element: rootElemRef.current,
        ...props
      })

When removed the React throws Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node. This is due to the fact that innerHML now gets wrapped in div, link to commit
This could be bypassed by using rootElemRef.current.children[0] but then again it's not an elegant solution as it is better to manipulate the actual ref as well as having an issue of detecting when the child is actually there since addOverlay isn't triggering a rerender.
I know React isn't the scope of this project but still mentioning this incase someone has the same issue or has a better solution or an idea.

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer

Interesting! Thank you for filing this. I'm not sure what the best solution is... Hopefully people have ideas.
You might also file a note on https://github.com/stephenwf/use-open-seadragon/issues.
Of course one option would be to build your overlay without React, but then you don't get the advantage of React. Btw, I'm not familiar with createPortal... Does it allow for rerenders, or is it just a one-shot thing?

The createPortal is basically the same as the usual render it just portals it to the defined container. I think it is needed here because overlays need to be rendered inside a dedicated osd div.
I think the error is basically the same as if someone would run a React app and then go to Chrome Inspector Tool and drag html divs around and then run some state changes - React isn't aware of external tree changes.
I'm gonna test out some solutions and if I find something that isn't to hacky I'll definitely post it.

Hmm, yes the setting of the innerHTML seems to be causing the issue there.
I think if the overlay needs a wrapper there could be 2 elements on the Overlay class.
So this:
this.element.innerHTML = "
" + this.element.innerHTML + "
";

Could be:
this.wrapperElement = document.createElement('div');
this.wrapperElement.appendChild(this.element);

And then you could apply the CSS transforms to the outer element. It would be essentially the same thing, but the contents of the passed in element are unchanged.
Although it is React that is throwing this error, I think it could be replicated:
const overlay = document.createElement('div');
const something = document.createElement('p');

overlay.appendChild(something);

// Pass `overlay` to the Overlay class in OSD.

// Later...
overlay.removeChild(something); // throws

something.innerHTML = '...'; // Does not apply the changes

If the overlay is passed in explicitly, I feel like the DOM elements should remain stable.

Interesting. That does seem like a cleaner way of wrapping it... I don't remember why we went with the innerHTML approach.
Is anyone up for giving it a try in the OSD code?
@BeebBenjamin (author of  #2546), any thoughts?

I didn't actually want to add this feature oringally.  I thought we should originally leave it and let people handle the HTML in the overlay.  But it was suggested that users would want to be able to flip the content of the overlay independently of the overlay.  This is because flipping the overlay causes any text to be reversed.  So I came up with an inelegant solution that worked for the suite of tests we have.  We could do any of the following:

Tear out the flipping of the content.
Find a better way of wrapping.
Add some additional tests for some of the well known packages that depend on OSD to see if changes break stuff such as this React package.

These are just suggestions and I don't mind taking on the fix since my PR caused this.

We could do any of the following:

Tear out the flipping of the content.
Find a better way of wrapping.
Add some additional tests for some of the well known packages that depend on OSD to see if changes break stuff such as this React package.

I'd vote for option 2.
I think what @stephenwf proposed above makes sense. I would guess the root of the problem is that the wrapping is done by setting this.element.innerHTML = "
" + this.element.innerHTML + "
"; - the problem is, all references to the original DOM elements (and bound data, event handlers, etc) are lost since they are re-created from new HTML text. Appending the existing DOM element to the new wrapper via wrapper.appendChild(existingNode) will help a lot. And it would be ideal to set all of the properties (like style) on the wrapper so that OSD is only changing elements that it controls.

Adding a wrapper and appending the element to it just disables the flipping of the content.  This is why I wished to rather extend the element, which is what I was attempting to do.  If there's a way to modify the existing node (wrap it in a div) without removing the references?

Would the following work:
 this.element = options.element;
        this.elementContent = this.element.firstChild;
        this.elementWrapper = document.createElement('div');
        this.elementContent.parentNode.insertBefore(this.elementWrapper, this.elementContent);
        this.elementWrapper.appendChild(this.elementContent);

More like something like this (the previous example broke tests):
this.element = options.element;
    this.elementContent = this.element.firstChild;
    this.elementWrapper = document.createElement('div');
    this.element.insertBefore(this.elementWrapper, this.elementContent);
    if (this.elementContent){
        this.elementWrapper.appendChild(this.elementContent);
    }

I want to write a unit test (but not in React) to see if the above fixes it, and if not helps me to.  What would be your expected outcome to restoring functionality? @stephenwf @oblak1  I need a sequence of operations you wish to do with the overlay to see what helps preserve this functionality.

@BeebBenjamin Thank you for continuing to be involved with this patch. I remember that you were reluctant to go with the wrapping and I insisted on it. If at any point you want to wash your hands of it, I totally understand!
I forget if we already covered this, but why don't we do it like this?
this.element = document.createElement('div');
this.element.appendChild(options.element);

I remember that you were reluctant to go with the wrapping and I insisted on it. If at any point you want to wash your hands of it, I totally understand!

😅

this.element = document.createElement('div');
this.element.appendChild(options.element);

This breaks the tests, producing the following error:
TypeError: Cannot read properties of null (reading 'getBounds')
Where as the following:
   this.element = options.element;
   this.elementContent = this.element.firstChild;
   this.elementWrapper = document.createElement('div');
   this.element.insertBefore(this.elementWrapper, this.elementContent);
   if (this.elementContent){
       this.elementWrapper.appendChild(this.elementContent);
   }

Doesn't, probably because we're making this.element something else.  I think maybe leaving this.element as is might be the better way to not introduce more side effects, even if the way we wrap it is more roundabout.

I also, still need some test conditions for React to see if this fixes the issue with removing Children and reusing the references later.  No point doing this, if it's still broken according to the issue.

I want to write a unit test (but not in React) to see if the above fixes it, and if not helps me to. What would be your expected outcome to restoring functionality? @stephenwf @oblak1 I need a sequence of operations you wish to do with the overlay to see what helps preserve this functionality.

I'm not sure if this will help, but the general idea is to reference the element using addOverlay. Once we have a reference to the element, we should be able to manipulate its style and basic HTML attributes.
This reference (whether it's the element itself or a child of a wrapper element, depending on how it's done in OSD) will serve as the portal container in React and its children are whatever we want to put inside overlay. It's important that this portal container doesn't have any children on its own, as React won't expect them when calling removeChild.

This breaks the tests, producing the following error:
TypeError: Cannot read properties of null (reading 'getBounds')

I see! This is because we are using this.element to test against. We can certainly fix that by explicitly having the element we were given and the wrapper element be stored in separate variables and use each as appropriate.

Where as the following:
this.element = options.element;
this.elementContent = this.element.firstChild;
this.elementWrapper = document.createElement('div');
this.element.insertBefore(this.elementWrapper, this.elementContent);
if (this.elementContent){
this.elementWrapper.appendChild(this.elementContent);
}
Doesn't, probably because we're making this.element something else. I think maybe leaving this.element as is might be the better way to not introduce more side effects, even if the way we wrap it is more roundabout.

My concern with this is what if options.element has more than one child? I suppose we could loop through all of the children. I don't know... taking the element apart and plucking at its pieces seems like it might be hard to get right in all scenarios.

Okay, I've made some progress. I have a unit test which passes before the PR and breaks after the PR.  So I will know when I fix this.  My proposal above does the same as adding a div to the innerHTML, so I won't take that any further. I am now working on the suggested strategy.

I can get the demos to look the same, but the unit tests are failing.  So still working through the fix.

I believe this is now fixed by #2582 . Thank you @BeebBenjamin !


Random error

Hi,
I am facing a random error in my tests, with django 1.8.12, coverage 4.0.3 and django_coverage_plugin 1.3 (and seemingly only on my CI server using ubuntu precise 32bit, not our developer machines using ubuntu >= 14.04 64bit):
django_coverage_plugin/plugin.py", line 170, in line_number_range
    assert frame.f_code.co_name == 'render'
AssertionError

(Side note, as it is an AssertionError exception, the test reports it as a failure, not an error)
It seems to be called from django/template/engine.py, line 168 (https://github.com/django/django/blob/1.8.12/django/template/engine.py#L168):
    def get_template(self, template_name, dirs=_dirs_undefined):
        """
        Returns a compiled Template object for the given template name,
        handling template inheritance recursively.
        """
        # ... removed for brevity
        if not hasattr(template, 'render'):  # <<-- fails here
            # template needs to be compiled
            template = Template(template, origin, template_name, engine=self)

This call comes from a fairly standard return render_to_string(template_name, context.flatten()) in a template tag.
I've managed to get a shell at the point of failure, and frame.f_code.co_name is indeed 'get_template'.

It is random in the sense that it appears maybe 10% of the time.

@NotSqrt hmm, strange.  Are you using any concurrency libraries, like gevent, greenlets, or eventlets?

I get this error when running tests with https://github.com/kmmbvnr/django-jenkins, on LiveServerTestCase tests calling selenium, so not directly concurrency libs, but definitely threads and subprocesses.

OK, I'm not sure how well this will work, but let's try this experiment.  In one of your tests, (anywhere, just some place that we can get the output, and we know that it's running in the same process as the occasional failures), add this code:  "import pprint, sys; pprint.pprint(sys.modules)".  If you need to, also add a failure like "1/0" to get the test runner to show you the output.  Then we can see what libraries might be involved.

Here is a list of the libraries extracted from import pprint, sys; pprint.pprint(sys.modules) in the function that raises the exception:
BaseHTTPServer
ConfigParser
Cookie
FixTk
HTMLParser
OpenSSL
PIL
Queue
SocketServer
StringIO
UserDict
UserList
_LWPCookieJar
_MozillaCookieJar
__builtin__
__future__
_abcoll
_ast
_bisect
_cffi_backend
_codecs
_collections
_csv
_ctypes
_curses
_cython_0_21_1
_cython_0_22
_elementtree
_functools
_hashlib
_heapq
_io
_json
_locale
_multiprocessing
_openssl
_random
_socket
_sre
_ssl
_strptime
_struct
_virtualenv_distutils
_warnings
_weakref
_weakrefset
abc
amqp
anyjson
appconf
argonauts
argparse
array
ast
asynchat
asyncore
atexit
backports
base64
billiard
binascii
bisect
bitarray
blessings
bootstrap3
braces
bz2
cPickle
cStringIO
calendar
celery
certifi
cffi
cgi
classytags
cmath
codecs
collections
colorsys
colour_runner
compat
concurrent
configurations
contextlib
cookielib
copy
copy_reg
coverage
crypt
cryptography
cssselect
cssutils
csv
ctypes
curses
datetime
dateutil
decimal
defusedxml
difflib
dis
distutils
django
django_countries
django_coverage_plugin
django_extensions
django_filters
django_jenkins
django_redis
django_statsd
email
encodings
encutils
enum
errno
exceptions
fcntl
fnmatch
formtools
fractions
ftplib
ftputil
funcsigs
functools
future_builtins
gc
genericpath
getopt
getpass
gettext
glob
googleapiclient
grp
gzip
hashlib
heapq
hijack
hiredis
hmac
html5lib
htmlentitydefs
httpagentparser
httplib
httplib2
imghdr
imp
importlib
inspect
io
ipaddress
ipware
itertools
jinja2
json
jwt
keyword
kombu
leaflet
linecache
locale
logging
logilab
lxml
markupbase
markupsafe
marshal
math
microsofttranslator
mimetools
mimetypes
mmap
mock
model_utils
msgpack
multiprocessing
multiupload
netrc
new
ntpath
numbers
numexpr
numpy
oauth2client
oauthlib
opcode
openid
operator
optparse
os
pandas
parler
pbr
pdfrw
pickle
pipeline
pkg_resources
pkgutil
platform
plistlib
polib
polymorphic
posix
posixpath
pprint
pptx
premailer
psutil
psycopg2
pty
pwd
pyasn1
pyexpat
pyftpdlib
pygments
pytz
quopri
random
re
redis
reportlab
requests
requests_oauthlib
resource
rest_framework
rest_framework_filters
rfc822
rosetta
scipy
sekizai
select
selenium
sendfile
sh
shlex
shutil
signal
simplejson
site
sitecustomize
six
smtplib
social
socket
sockjs
spwd
sre_compile
sre_constants
sre_parse
ssl
stat
statici18n
statsd
string
stringprep
strop
struct
subprocess
supervisor
swampdragon
sys
sysconfig
tarfile
tempfile
termios
textwrap
thread
threading
time
timeit
timezone_field
token
tokenize
traceback
tty
types
ujson
unicodedata
unittest
uritemplate
urllib
urllib2
urlparse
uu
uuid
warnings
watson
weakref
wsgiref
xlsxwriter
xml
zipfile
zipimport
zlib

I don't see any smoking guns there. Selenium is notorious for unpredictability, but I don't see how it could produce assertions like that one.

I tried to inspect the stack when entering the line_number_range method:
  File "/usr/lib/python2.7/threading.py", line 524, in __bootstrap
    self.__bootstrap_inner()
  File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
    self.run()
  File "virtualenv/local/lib/python2.7/site-packages/django/test/testcases.py", line 1190, in run
    self.httpd.serve_forever()
  File "/usr/lib/python2.7/SocketServer.py", line 227, in serve_forever
    self._handle_request_noblock()
  File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "virtualenv/local/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 102, in __init__
    super(WSGIRequestHandler, self).__init__(*args, **kwargs)
  File "/usr/lib/python2.7/SocketServer.py", line 638, in __init__
    self.handle()
  File "virtualenv/local/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 182, in handle
    handler.run(self.server.get_app())
  File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
    self.result = application(self.environ, self.start_response)
  File "virtualenv/local/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 63, in __call__
    return self.application(environ, start_response)
  File "virtualenv/local/lib/python2.7/site-packages/django/test/testcases.py", line 1107, in __call__
    return self.application(environ, start_response)
  File "virtualenv/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 189, in __call__
    response = self.get_response(request)
  File "virtualenv/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 164, in get_response
    response = response.render()
  File "virtualenv/local/lib/python2.7/site-packages/django/template/response.py", line 158, in render
    self.content = self.rendered_content
  File "virtualenv/local/lib/python2.7/site-packages/django/template/response.py", line 135, in rendered_content
    content = template.render(context, self._request)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/backends/django.py", line 74, in render
    return self.template.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/base.py", line 210, in render
    return self._render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/test/utils.py", line 96, in instrumented_test_render
    return self.nodelist.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/base.py", line 905, in render
    bit = self.render_node(node, context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/debug.py", line 79, in render_node
    return node.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 135, in render
    return compiled_parent._render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/test/utils.py", line 96, in instrumented_test_render
    return self.nodelist.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/base.py", line 905, in render
    bit = self.render_node(node, context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/debug.py", line 79, in render_node
    return node.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/classytags/core.py", line 146, in render
    return self.render_tag(context, **kwargs)
  File "virtualenv/local/lib/python2.7/site-packages/sekizai/templatetags/sekizai_tags.py", line 83, in render_tag
    rendered_contents = nodelist.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/base.py", line 905, in render
    bit = self.render_node(node, context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/debug.py", line 79, in render_node
    return node.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/defaulttags.py", line 329, in render
    return nodelist.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/base.py", line 905, in render
    bit = self.render_node(node, context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/debug.py", line 79, in render_node
    return node.render(context)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 151, in render
    template = context.template.engine.get_template(template)
  File "virtualenv/local/lib/python2.7/site-packages/django/template/engine.py", line 170, in get_template
    if not hasattr(template, 'render'):

It is clearly in the LiveServerThread, not the main thread.
It is not always the same template that makes it fail.
In line_number_range, the template instance is in frame.f_locals['template'], but it has no loaded source, so it can't be used in position_for_node.
Do you want me to look in a specific direction ?
I was unable to simplify and reproduce the bug in a clean django project.

@NotSqrt, I noticed that StringIO shares the same memory between the celery worker processes. It generated some corrupted contents in my project. Would it be the root cause for your case?

@hz It's hard to tell..


create_cmdline feature

Looking for something along the lines of create_cmdline from SiliconCompiler.  This would be helpful to reduce repeated boilerplate code in testbenches.

Implemented in #210.  Set cmdline=True when creating SbDut; extra arguments can be created with the optional extra_args argument.


Add 3.9.1 release

The upstream repo already has a `meson.build' so we should be using that rather than overwriting our own. You might find the mesonwrap tools helpful, they have functionality to review your code automatically for common problems:
https://github.com/mesonbuild/mesonwrap/

The upstream repo already has a `meson.build' so we should be using that rather than overwriting our own.

I see. I have used branch 3.7.0 as base for this template but I should have checked more.

You might find the mesonwrap tools helpful, they have functionality to review your code automatically for common problems:

I have tested this PR with the mesonwrap tool and all checks pass. Thanks for pointing it out :)


bump rasterio to 1.0.24 in doc building environment

This is hopefully a fix for #3182 but I wasn't sure how to really test this on read the docs (RTD) itself.
There may be a few things going on:

Local testing showed removing the "auto_gallery" dir would cause the failing gallery examples to actually be recognized as failing (i.e. bust the cache)
https://github.com/conda-forge/rasterio-feedstock/issues/118 and some examining of the conda list output on RTD for led me to think this was a deeper problem. Local testing with a bumped version of rasterio resulted in conda-forge being the channel source (rather than pip?), it also fixed the failing builds which relied on rasterio.

Examining the output of conda list in the CI build shows most of the packages are coming from conda-forge now, including rasterio. This should mean the docs will build successfully on RTD.

Great, let's try it! Thanks @DocOtak


No screenshot on npmjs.com

Idk if it's something that needs fixing. Maybe it's not worth packaging effectively useless stuff inside the npm package to save space.

ftr, this is the url: https://www.npmjs.com/package/webxdc-dev
i do not know, how these sites are used in practise, but, as a first impression, to me it does not look good, i would fix that.
as a pragmatic approach, we could probably just replace ./screenshot.png in the README by https://raw.githubusercontent.com/webxdc/webxdc-dev/main/screenshot.png


[feature] x-editable

What do you think of adding support for x-editable type input fields?

Seems like it could be an interesting project but I'm not sure I have the bandwidth to take it on right now. You're the first person to request it (though I assume you wouldn't be the only one to make use of it).
Would you be interested in contributing toward this feature?

Might be a good reason to learn typescript. That's my major barrier right now.

On Jul 2, 2015, at 8:42 PM, Brian Vaughn<EMAIL_ADDRESS>wrote:
Seems like it could be an interesting project but I'm not sure I have the bandwidth to take it on right now. You're the first person to request it (though I assume you wouldn't be the only one to make use of it).
Would you be interested in contributing toward this feature?
—
Reply to this email directly or view it on GitHub.

I can't say enough nice things about it. :)
I work at Google so I use the Closure compiler a lot during my day job. I've also used CoffeeScript a fair amount in the past. TypeScript is much more enjoyable than either.
If you do decide to give it a try, I recommend checking out the 30-day demo for WebStorm too. It's fantastic.

hi,i am getting error in line63 when i try in IE8,i have included the es5.js as well.
below line in form-for.js gives error
Object.defineProperty(FormForConfiguration.prototype, "autoGenerateLabels", {
Please help
Thanks

I was a fan of coffeescript until babel and es6. Haven't had time to work with typescript... Still not convinced all the tooling is there yet and I feel like there is a small barrier to entry for contributions still. I suspect though that in a year or two we will all be writing it.
Already a open source license user of idea under my Apache committer membership. Love it!
What I'm really looking for is something very much like your project but with just bootstrap support. I don't want special elements for declaring forms. Just standard html. I see why you went that route but I'd rather not put barriers to entry up for people by making them learn new elements. Just annotate basic form elements with angular and bootstrap specific markup.
Sorry, getting off topic now. If you'd like to close this issue no worries. Thanks for your fast response and helpful attitude!

On Jul 2, 2015, at 9:29 PM, Brian Vaughn<EMAIL_ADDRESS>wrote:
I can't say enough nice things about it. :)
I work at Google so I use the Closure compiler a lot during my day job. I've also used CoffeeScript a fair amount in the past. TypeScript is much more enjoyable than either.
If you do decide to give it a try, I recommend checking out the 30-day demo for WebStorm too. It's fantastic.
—
Reply to this email directly or view it on GitHub.

I think the tooling is sufficient to make it a very compelling choice. Far superior to vanilla JS and far more elegant and compact (subjectively) than Closure.
Hm. Interesting concept. formFor could be refactored to allow for decorating regular input elements while also offering the more full-featured, label-and-field combo directives... but I don't know if it would be worth the effort.
You may also be interested in a side project of mine that's kind of fizzled out at the moment - Forms JS. If you have any interest in joining, I haven't given up on it yet. The other contributors didn't really have the time though and I'm not sure I want to tackle another library solo.
I'm going to close this for now but...it's a nice though, and if other people see it and like the idea, maybe I'll consider it. :)


Create db if not existing

Would be nice that app.metrics influxdb reporter will create database if it was not created

I think in many cases an application wouldn't have such permission. For those that decide it's OK, it could be done just as easily outside App Metrics on app startup. Thoughts?

Agree with you, in most cases there is not root rights to influxdb instance. But on other hand, there is so easy to implement it, so maybe in future would be nice to have this feature as useful addition.

I'll think about it again once a stable 2.0 release goes out. I guess I can think about it like getting started with EF which creates db tables on startup to make the dev experience a little better ;)

Please add this feature.
Heapster and Telegraf do it. Same behavior is expected.
It does not need any additional permissions (InfluxDB does not have any public endpoints, and used in local net only).

Already done


Spelling mistake, tweaking description and links to docs

Spelling mistake, tweaking description and links to docs

👍