FORMS-2981 Localisation of different default error messages

Description

Related Issue
FORMS-2981

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

I have written tested locally and commented the localisation cypress test case, until we receive the translated strings from the localisation team.


spyder is unable to show the variable you are trying to view because the module azureml was not found

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Hi there,
I couldn't see the contents of a variable in Variable explorer.
Giving below error:

Though I could see azureml in files

I followed the below link to create a new environment for azureml - (modular approach)
https://github.com/spyder-ide/spyder/wiki/Working-with-packages-and-environments-in-Spyder
What steps reproduce the problem?

Create a new environment
Activate new environment
install azureml-sdk
install spyder-kernel
Deactivate new environment
Goto (base) anaconda environment
launch spyder
change IPython Interpreter to point to the Python.exe file in new environment
restart kernel
from azureml.core module import Workspace class
Try to veiw content of Worskspace class in variable explorer by double clicking

What is the expected output? What do you see instead?
The content of Workspace class

Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 4.1.5
Python version: 3.8.5
Qt version: 5.9.7
PyQt version:  5.9.2
Operating System name/version: Windows 10

Dependencies

PASTE DEPENDENCIES HERE

I could see the contents of the variable if I install spyder separately in the new environment (Naïve approach)

Hey @JamiVaraPrasad, thanks for reporting. The only to follow this approach
https://github.com/spyder-ide/spyder/wiki/Working-with-packages-and-environments-in-Spyder
and view your objects is (as you already found) to install azureml-sdk in the same environment as Spyder is installed. This is basically what our message is telling you:

This is a Python limitation and for now there's nothing we can do about it, sorry.


Consider always scaning current project/module src directory for endpoints

Currently, source files from current project (or current module of a multi-module project) is scanned for endpoints, only if there is no configuration for the exposed packages from dependencies (or other modules). If the user configure the maven/gradle plugin to scan and include a single external endpoint from some dependency, then they should always list the a high-level package from the sources of the current project/module as well which is not convenient.
Configuring the for exposed packages from other modules or from dependencies should not affect the parser behavior for scanning the sources in the current project (or current module of a multi-module project), as most of the times, the use case is to use some external utility endpoints, and not to hide the endpoints of the current project/module.
We should consider always scanning the current project/module's sources, plus the additional exposed packages from the dependencies or other modules.

Sounds like a good idea. However note that the actual scanning happens for the compiled files in the target/build directories, not for the source.

Sounds like a good idea. However note that the actual scanning happens for the compiled files in the target/build directories, not for the source.

Thanks for the input. Updated the wording in the title and description.


Restructure package

After finishing beta3, code will need to be refactored and packages restructured. This issue will reference the other issues pertaining to this.

Beta 4 is finished. Tests were reduced down to one class. I want to finish beta 5 before adding more comprehensive tests.


Add Web We Want overview

Docs Build status updates of commit 9f3278b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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 e2e25ba:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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 119f6f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 150449c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit dda0449:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 283ac87:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/web-we-want/index.md
:warning:Warning
View
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md

Line 27, Column 132: [Warning-file-not-found] Invalid file link: '../devtools-guide-chromium/experimental-features/'.
Line 27, Column 169: [Warning-file-not-found] Invalid file link: '../devtools-guide-chromium/3d-view/'.

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 62df7bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit b59ab43:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 74b29d3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 6503437:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 65cf656:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit ec5b78d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/web-we-want/index.md
:white_check_mark:Succeeded
View

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

#sign-off and merged.


Header component#47

Finished the styling for Header Component #47.

I think those all are or should be in scope and should be easy to update.

So far so good! I'm going to dive a little deeper tomorrow on resolutions and fonts, but I don't expect I'll find much else to nitpick over. 2 questions:
The logo changes from blue to orange on the About page in the prototype. Is that within scope?
The hamburger icon looks slightly different than the one in the prototype. Would you consider that within scope, or prefer dealing with it later?

Update the icon to now update to based on view port.

Updated the Icon and removed mentions of mentor night from the project. @MoribundMedium


[Coverity CID :188890]Insecure data handling in /drivers/watchdog/wdt_qmsi.c

Static code scan issues seen in File: /drivers/watchdog/wdt_qmsi.c
Category: Insecure data handling
Function: get_timeout
Component: Drivers
CID: 188890
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

@nashif Hi. Do you think that it is a good idea to fix that defect by writing a new function sat_subtract and perform a saturating subtract?
As I understand the issue is count - 1 and its ability to underflow if count=0.
Please check my code idea prototype for that fix:
extern int sat_subtract(u32_t a, u32_t b);
inline sat_subtract(u32_t a,  u32_t b)
{
return ((a > b) ? (a - b) : 0);
}
static u32_t get_timeout(u32_t  timeout)
{
u32_t count = 0U;
return sat_subtract(count,1U);
}


ESM and CSS loading

In the ESM (EcmaScript Modules) version, css files are being imported like:
import './actionbar.css';

I have looked into the ECMA-262, TC39 proposals etc. but nowhere I could find that importing CSS files or other assets is allowed this way. Do any browsers support importing CSS files that way? Do I miss anything obvious? To me the ESM version is not ESM ;).

CSS files are handled by webpack, the typical bundler when chossing ESM. This has nothing to neither with ECMA nor with the browsers. For more information about webpack and loading CSS: https://webpack.js.org/guides/asset-management/#loading-css

To me it is a mistake to introduce non-standard features to esm modules. How about if I want to use the unbundled version directly in the browser together with http2? As it is now, it is impossible...

Sorry for the disappointment. I think the ESM Version is thought to be bundled with webpack in this project, I'm quite sure that bundled/optimizied/tree-shaked code is still faster than HTTP2 with multiplexing etc... But hey, there is still an AMD Version that you can use.

@czb I agree.
I explicitly tried to avoid any webpack assumptions in the esm distribution, that's why the esm distribution can be loaded by other loaders.
But I could not figure out what to do with the CSS imports. Our CSS is grouped neatly with the corresponding feature. i.e. we don't have a large CSS file which is a "take it all or leave it all", but rather we have written the CSS next to the JS, so each JS file can indicate that it wants certain CSS.
You are correct, the source code cannot be loaded in its current shape via a <script type="module> tag without a minimal preprocessing to strip the CSS imports. But, I wonder, what is the alternative? What would you recommend? My plan is to wait for the committee to figure out what they're gonna do about CSS loading and adopt that once that is finalised.

Personally, I load css dynamically:
export function injectFile(href: string) {
    return new Promise<void>((resolve, reject) => {
        const link = document.createElement('link')
        link.setAttribute("rel", "stylesheet")
        link.setAttribute("type", "text/css")
        link.onload = () => resolve()
        link.onerror = () => reject()
        link.setAttribute("href", href)
        document.head.appendChild(link)
    })
}

@czb Yes, that is what I also do in the AMD loader I wrote 5 years ago :). But I don't want to do that in each and every JS file where I use some CSS. I also want the ability to be able to collect all used CSS into a single style-sheet at packaging time, so that's why I left .css imports in JS files.

I could not find any signs of css imports discussions which probably means they will not arrive in a near future.
To me, any solution is better than extending javascript by non standard features that are not even at stage 1.

@czb I am not familiar with the maze of github repositories used by whatwg or w3c nor their politics.
I don't expect that ECMA-262 (which standardises ECMAScript) would concern itself with importing CSS in a web browser.
Do you happen to know where we can ask someone about the state of affairs for importing CSS ?

I happen to be part of the group proposing HTML Modules - the ability to import HTML files into JavaScript modules or via <script type=module. CSS Modules are on our radar, but not proposed yet.
I can tell you that the semantics would likely be oriented around a CSS module exporting a Constructible Stylesheet: https://wicg.github.io/construct-stylesheets/index.html
ie:
import stylesheet from './styles.css';

stylesheet instanceof CSSStyleSheet; // true

// attach to global
document.moreStyleSheets.push(stylesheet);

// or to a ShadowRoot
class MyElement extends HTMLElement {
  constructor() {
    this.attachShadow({mode: 'open'}).moreStyleSheets.push(stylesheet);
  }
}

If you wanted to be future-facing to such a spec, the most proper thing to do would be to create a JS modules that has no side-effects and returns a style sheet object from a JS module, ie:
styles.css.js:
// create a container and scope to hold a style sheet:
const container = document.createElement('div');
const shadowRoot = container.attachShadow({mode: 'open'});

// create a <style> element to add css text to
let styleElement = document.createElement('style');

// add the styles
styleElement.textContent = `
  .monaco-editor .accessibilityHelpWidget {
	padding: 10px;
	vertical-align: middle;
	overflow: scroll;
  }
`;
// add the <style> to the document so it creates a style sheet
shadowRoot.appendChild(styleElement);

export default let stylesheet = styleElement.sheet;

However, because this has no side-effects, this would require rewriting the importing code. Which is kind of ugly without the moreStyleSheets property of the Constructable StyleSheets proposal.
So for now, because I don't think you're using Shadow DOM yet, I think the best option is to build .css files into JS modules, that attach the CSS to the main document:
export default styleElement = document.createElement('style');
styleElement.textContent = `
.monaco-editor .accessibilityHelpWidget {
	padding: 10px;
	vertical-align: middle;
	overflow: scroll;
}
document.head.appendChild(styleElement);
`;

Then your import sites can remain the same as the are now.

Thank you for the explanation @justinfagnani
I'm going to think about this for a while, I was hoping to end up in a situation with the /esm/ folder in our distribution where its contents are both future-proof and consumable today via loaders such as webpack or rollup.
I don't believe webpack nor rollup would understand the creation of <style> elements code pattern and be able to extract the CSS to a separate CSS file.
I also don't think browsers will really like this creation of hundreds of <style> elements (speed-wise). Even if the pattern would change to create a single <style> element and keep appending to it, things might not be as good as extracting the CSS to a single file... I think browsers prioritise downloading CSS over other resources like images...

So I modified the gulpfile to build .css into .css.js and this gets things closer to working, but there was an exception about require not being defined:
languageFeatures.js:192 ReferenceError: require is not defined
    at editorSimpleWorker.js:522
    at new Promise_ctor (winjs.base.js:1822)
    at EditorSimpleWorkerImpl.BaseEditorSimpleWorker.loadForeignModule (editorSimpleWorker.js:521)
    at webWorker.js:57
    at ShallowCancelThenPromise.CompletePromise_then [as then] (winjs.base.js:1743)
    at MonacoWebWorkerImpl._getForeignProxy (webWorker.js:56)
    at MonacoWebWorkerImpl.getProxy (webWorker.js:87)
    at WorkerManager._getClient (workerManager.js:76)
    at WorkerManager.getLanguageServiceWorker (workerManager.js:105)
    at DiagnostcsAdapter.worker [as _worker] (tsMode.js:47)

Any updates on this? Is it just that we're waiting on ECMA for new CSS loading spec? If so, it would be great to have a ESM spec compliant version using one of the solutions @justinfagnani put forward for the time being!

I'd love to be able to run the following in the browser (just prototyping myself) - and have it load the editor:
<!doctype html>
<html>
  <meta charset="utf-8">
<body>
  <div id="container">
</body>
<script type="module">

  import monaco from '//dev.jspm.io/monaco-editor/esm/vs/editor/editor.main.js';
  console.log(monaco);

</script>
</html>

Currently it does not load and I see a large number of these errors in the console
Failed to load module script: The server responded with a non-JavaScript MIME type of "text/css". Strict MIME type checking is enforced for module scripts per HTML spec.

Here's an example plnkr I was hoping to be able to hack on using the monaco editor in the browser https://plnkr.co/edit/0fMrMAjNeH2PVGAh206m?p=preview to prototype something...

@alexandrudima @kqadem Any news?

Hello, is there any update on distributing a browser/spec-friendly ESM build?
I think the suggestions given above are all quite reasonable:

Distribute your css as .css.js stylesheet modules
Distributing a js module and a bundled stylesheet

Browser-friendly ES modules with minimal side-effects per module are an incredibly useful tool for publishing future-proof packages. As of now, I can't really ship a browser-runnable package without forcing the user into webpack or parcel.
Alternatively, Rollup support would also make this transformation much easier.

I can't believe we are still not on standard here.
Is there any effort being made to resolve this yet?
In this day and age staxmanade example is the reasonable choice.

I forgot about Monaco not being standards compliant here after being away from two years, and hit this roadblock again when trying to load code directly into a browser.
Again, can the ESM distribution be renamed to "webpack" or something? It's just misleading at this point. If the library really is distributed as modules then typing  import('https://unpkg.com/monaco-editor@0.20.0/esm/vs/editor/editor.all.js?module'); in devtools should work without errors. Monaco currently has dozens of errors.
Then, can the CSS just be built and distributed a different way? Many libraries that use standard modules these days publish CSS inside of JS modules, sometimes via a build step. Vexflow and CodeMirror 6 are two I've seen recently. Everything made with LitElement works this way. The benefit is that the CSS is part of the library's module graph and you don't need any bundler to get the right files loaded.

For anyone else struggling with this: yes. This library is not exported as a valid ESM module.
If you need to use it on a real-life project (specially if you rely on popular abstractions like create-react-app or next-js), it needs to be transpiled and loaded with a separate webpack rule.
Here's a few things that worked on my current stack, but each toolchain will have it's entry points to allow webpack tweaks (or the eject button, which leaves you with plain webpack) :)

webpack plugin for monaco editor to write less configs :scroll:
react monaco editor to skip writing the react bindings ---> but still uses monaco-editor --> so it inherits the same ESM issues :0
I use next-js, luckily they expose a lot of entry points to play with webpack config. Depending on your choice of styling (css/css-modules/sass/css-in-js) you'll need to set a special loader rule for the monaco styles and ttf fonts! Here's a hint on how it could look, but it depends on your css flavor

// pseudo-code from the docs here:
// https://github.com/react-monaco-editor/react-monaco-editor#using-with-webpack
// Specify separate paths
const path = require('path');
const APP_DIR = path.resolve(__dirname, './src');
const MONACO_DIR = path.resolve(__dirname, './node_modules/monaco-editor');

// pass webpack module.rules
{
  test: /\.css$/,
  include: APP_DIR,
  use: [{
    loader: 'style-loader', // or whatever you use
  }, {
    loader: 'css-loader', // or whatever you use
    options: {
      modules: true,
      namedExport: true,
    },
  }],
}, {
  test: /\.css$/,
  include: MONACO_DIR,
  use: ['style-loader', 'css-loader'],
},
, {
  test: /\.ttf$/,
  include: MONACO_DIR,
  use: ['file-loader'],
}

next-transpile-modules will transpile the nasty code!!! Could also be written on webpack or as a prebuild step I guess? But it needs to be transpiled at some point otherwise it will just not work :)
if using ssr we get a node-ish env on the first render... so don't forget to make it a dynamic import to avoid missing browser globals!

import dynamic from 'next/dynamic'

const MonacoEditor = dynamic(import('react-monaco-editor'), { ssr: false })

<MonacoEditor ... />

web workers need to be handled by nextjs as static content to be available on the final bundle :robot:

Hope this list of hints helps others trying to consume it on their projects... but also highlights how much effort/knowledge/fiddling is needed to actually use the library :)

Reiterating what @justinfagnani has said above; calling this esm is misleading at best. At worst a casual adopter will install the library and attempt to import it natively only to find that this does not work, wasting time. If a bundler like webpack is necessary this obviates the benefits of language-level, dependency-free imports. Monaco is awesome, and I hope that this can be addressed with more urgency. Thanks!

To save time for y'all:
Unfortunately, the ESM folder does NOT contain an ESM distribution
The ESM folder gives you the impression that it contains an ESM implementation of Monaco. After importing it using import-maps, it turns out that it tries to use ESM loading of CSS, which is disallowed in ESM and does not work in browsers.
Most ESM distributions allows both ESM loading and legacy loading (using transpiration tools). This one, however, depends on legacy tools and does not work with ESM.

Thanks all; I got here after trying to get some node.js-based mocha tests that tried to test monarch syntax highlighting in an ESM project. I can't see a way around this, other than webpack-ing up my tests and letting the transpiler do its magic; which is a layer of complexity I was avoiding til now (and annoyingly the mocha<->webpack stuff's all broken too).

@oldrich-s You are right, moreover, that import './actionbar.css'  is one of those custom hacky patches that reach consensus among devs-on-the-edge, to inject text as a stylesheet on the fly, so nothing about it anything ressembling a 'module' XD
meanwhile at ECMALabs, 2 years later, they have come up with this thing, and hit a roadblock there:
import "https://example.com/module";
import "https://example.com/module" assert { type: "css" };
[https://whatpr.org/html/4898/webappapis.html#integration-with-the-javascript-module-system]
Oh well, can we blame people though for just wanting to move forward while standards are being discussed XD
If you face this issue:

Personally I would take that import and put it where it on another css, since you are not getting any 'css scoping' benefit anyway, and this is actually compliant since ages ago:
import "./deezstyles.css";

.my-already-cascading-styleshits {
}

Or... you could also instantiate some DOM wrappers and stick them a shadowDOM so then you can assign it an instance of a CSSStytleSheet with your CSSRule, which effectively isolates your css classname and it doesnt pollute the global scope.
Really man, the human mind is amazing XD

There should be an official solution, but I've found some luck using Skypack which bundles npm packages to ESM on-demand.
import * as monaco from<EMAIL_ADDRESS>
This is also very fast to load because it bundles the entry-point and eliminates the waterfall effect.
There's a limitation with resolving assets within CSS though, and fails to load codicon.ttf.
Not the best solution but I worked around this using a service worker:
self.addEventListener('activate', event => {
	event.waitUntil(clients.claim());
});

self.addEventListener('fetch', (event) => {
	if (event.request.url.endsWith('codicon.ttf')) {
		event.respondWith(
<EMAIL_ADDRESS>		);
	}
});

For anyone else struggling with this: yes. This library is not exported as a valid ESM module.
If you need to use it on a real-life project (specially if you rely on popular abstractions like create-react-app or next-js), it needs to be transpiled and loaded with a separate webpack rule.
Here's a few things that worked on my current stack, but each toolchain will have it's entry points to allow webpack tweaks (or the eject button, which leaves you with plain webpack) :)

webpack plugin for monaco editor to write less configs 📜
react monaco editor to skip writing the react bindings ---> but still uses monaco-editor --> so it inherits the same ESM issues :0
I use next-js, luckily they expose a lot of entry points to play with webpack config. Depending on your choice of styling (css/css-modules/sass/css-in-js) you'll need to set a special loader rule for the monaco styles and ttf fonts! Here's a hint on how it could look, but it depends on your css flavor

// pseudo-code from the docs here:
// https://github.com/react-monaco-editor/react-monaco-editor#using-with-webpack
// Specify separate paths
const path = require('path');
const APP_DIR = path.resolve(__dirname, './src');
const MONACO_DIR = path.resolve(__dirname, './node_modules/monaco-editor');

// pass webpack module.rules
{
  test: /\.css$/,
  include: APP_DIR,
  use: [{
    loader: 'style-loader', // or whatever you use
  }, {
    loader: 'css-loader', // or whatever you use
    options: {
      modules: true,
      namedExport: true,
    },
  }],
}, {
  test: /\.css$/,
  include: MONACO_DIR,
  use: ['style-loader', 'css-loader'],
},
, {
  test: /\.ttf$/,
  include: MONACO_DIR,
  use: ['file-loader'],
}

next-transpile-modules will transpile the nasty code!!! Could also be written on webpack or as a prebuild step I guess? But it needs to be transpiled at some point otherwise it will just not work :)
if using ssr we get a node-ish env on the first render... so don't forget to make it a dynamic import to avoid missing browser globals!

import dynamic from 'next/dynamic'

const MonacoEditor = dynamic(import('react-monaco-editor'), { ssr: false })

<MonacoEditor ... />

web workers need to be handled by nextjs as static content to be available on the final bundle 🤖

Hope this list of hints helps others trying to consume it on their projects... but also highlights how much effort/knowledge/fiddling is needed to actually use the library :)

This is such a great write up but didn't work for me on Nextjs 10.

https://web.dev/css-module-scripts/ indicates a possible way forward:
import sheet from './styles.css' assert { type: 'css' };
document.adoptedStyleSheets = [sheet];
shadowRoot.adoptedStyleSheets = [sheet];

or the async variant
const cssModule = await import('./style.css', {
  assert: { type: 'css' }
});
document.adoptedStyleSheets = [cssModule.default];

@alexdima does this mean you will change the imports to standard ones?
and will then the esm folder contain a version wich could directly be loaded from browser?

@alexdima
do you work on this? is it possible to help with something?

@evtk thnx, but not working :(
`const path = require("path");
const MONACO_DIR = path.join(__dirname, "..", "node_modules/monaco-editor");
module.exports = {
module: {
rules: [
{
test: /.css$/,
include: MONACO_DIR,
use: ["style-loader", {
"loader": "css-loader",
"options": {
"url": false,
},
}],
},
],
},
};`
      "architect": {         "build": {           "builder": "@angular-builders/custom-webpack:browser",           "options": {             "customWebpackConfig": {               "path": "./custom-webpack.config.js",               "mergeRules": {                 "externals": "replace"               }             },

@Maksclub It does work, just had this same issue with 14.2.2 as well.
Just make sure the MONACO_DIR path is correct corresponding your project structure.
my case was removing the ..
const MONACO_DIR = path.join(__dirname, "..", "node_modules/monaco-editor");

For those of you ending up here finding a solution to have Monaco Editor ESM style work with Angular 14, this might help:

Use @angular-builders/custom-webpack to be able to manipulate webpack config
Setup like below in your custom-webpack.config.js

const webpack = require("webpack");
const path = require("path");
const MONACO_DIR = path.join(__dirname, "..", "node_modules/monaco-editor");

module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/,
        include: MONACO_DIR,
        use: ["style-loader", {
          "loader": "css-loader",
          "options": {
            "url": false,
          },
        }],
      },
    ],
  },
};

Thanks for this. It's painful to need a custom webpack config, but it worked like a charm. However, I now have a bunch of nonsensical warnings in my Angular build, e.g.:
Warning: /...../node_modules/monaco-editor/esm/vs/editor/standalone/browser/iPadShowKeyboard/iPadShowKeyboard.css depends on '!../../../../../../../style-loader/dist/runtime/styleDomAPI.js'. CommonJS or AMD dependencies can cause optimization bailouts.
The irony of it complaining about these being "CommonJS or AMD dependencies" is not lost on me. I don't see how to disable the warnings though, given that they are coming from style-loader itself. They are just warnings, but if anyone knows how to get rid of them, please post.

Maybe this helps someone, I created an ESM bundle of Monaco here. There are a couple of examples of using it in the test directory.

@codeStryke without diving too much into that bundle: would it be possible to use Monaco without all the needed webpack config? I would love to remove all that custom config and the need for the custom builder for our Angular app.

@evtk You can also use "prebuild" and then import as ES module.
Just use this
https://github.com/bultas/monaco-component

I managed to build an ESM library out of the monaco-editor which includes a default configuration for YAML (only). It is pretty tailor made (added specific exports in the module), but thought it was worth posting here to help others.
https://github.com/evtk/monaco-editor-yaml-esm
For those coming here, looking for an answer how to use the Monaco Editor with Angular. Besides that webpack based solution I posted earlier on, you can also use this package or your own fork of it. It removes the need to use custom angular builders, which i wanted to get rid of.
Instead of installing the monaco-editor use the bundle I created and make sure to add the following glob to your angular.json assets config:
              {
                "glob": "**/*",
                "input": "node_modules/monaco-editor-yaml-esm/dist/assets",
                "output": "assets"
              }

@poucet Web Dev Server can accept arbitrary rollup plugins to serve these kinds of things, but the problem is that I'm not sure how monaco expects those CSS imports to be handled, hence why monaco should remove them from their distribution bundle. Here is an example of using WDS + a random CSS rollup plugin I found (not sure if this is how monaco expects it to be used):
https://stackblitz.com/edit/node-tfl4jq?file=types.d.ts
But, doing this compilation at serve time is probably not what you want because it can cause server latency. To make TS not crash, you should include a declare module '*.css' {} so TSC can compile, and then use a build tool like rollup / esbuild / webpack to process the bundle and handle those CSS files in the way monaco expects and then serve that resultant bundle.

As Import Attributes are now at stage 3 (again), would it be possible to switch monaco to use valid ES6 Code?
https://github.com/tc39/proposal-import-attributes

related to #4175

Another option for Angular, if you don't want to use the custom webpack builder listed above, is to do something like this somewhere in the build or postinstall:
npx replace "^import '.*\.css';$" "" --recursive ./node_modules/monaco-editor/esm/*

And then add this to your global styles list in angular.json:
node_modules/monaco-editor/min/vs/editor/editor.main.css

This works better for my particular use case, where I am publishing a reusable monaco-editor component. I've added the npx script to the component library's postinstall, and I no longer have to force users of the component/library to use the custom webpack builder. It's a bit ugly, but so are the .css imports being removed!

@neodescis did ever find a solution for those warnings?
I mean, not a big deal, but since we know that they're redundant, it would be better to get rid of them.

@neodescis did you ever find a solution for those warnings? I mean, not a big deal, but since we know that they're redundant, it would be better to get rid of them.

If you use the solution I posted just above, instead of the custom webpack builder, you shouldn't see any warnings.

I'm not sure if it can work for my requirement: I need to have the smallest bundle possible.
I'm already using monaco-editor-webpack-plugin to remove stuff that I don't need.
Although maybe I can use both of them, need to try.

@neodescis in the end I did what you did, just by using patch-package instead of an npx replace command.
Managed to shave off about 100 KB out of 3 MB. The .js bundle is smaller, the .css file slightly bigger.


deploying to github pages as subdirectory

I have a small project with create-react-app, which I wanted to host on github pages. It would be:
stopachka.github.io/my-project

The help in our tutorial was awesome. However, when loading the project, assets are not correctly found.
In the generated index.html, we have ->
<script type="text/javascript" src="/static/js/main.ce66e420.js"></script>

This will direct github-pages too
https://stopachka.github.io/static/js/main.ce66e420.js

which return a 400. It should instead direct to ->
stopachka.github.io/my-project/static/js/main.ce66e420.js

Ideas:

Make it so the source path does not have the / prepended to it.
Find simple way to tell github-pages to do the right thing, or to prepend /my-project/ to the source path through some option
If this is something that we don't want to support out of the box, we can tell users to eject, and write some quick instructions in the docs

I think the tutorial linked to mentions the fix in the first sentence 😉 .

Open your package.json and add a homepage field:

 "homepage": "http://myusername.github.io/my-app",

If you do this, Create React App will know to use /my-app as root URL.

Clarified in the doc: 6aabe7e881f45fd52e8481bbe2463ea3fce8c1ba.
The most recent version also explains this behavior after build:

Ah, nice, thanks for the clarification @gaearon -- initially thought it was just meant as a flag to output the instructions. Super nice touch :)


Add script to remove file generated from cook

Create a cleanCook.py script.
The script should remove the Saved folder and the cooked folder from the host.
Also the current cleanCook script should be rename as a post postCook

Needs also of branch feature/cleanCookFiles


Modify the as param condition

Hi!
I have something to suggest while using it, so I am registering an issue.
Can I change the condition of as parameter to falsy values other than undefined?
https://github.com/scottrippey/next-router-mock/blob/f212a96d1ad82f743676d044800a0185b3dcd841/src/MemoryRouter.tsx#L145-L147
I wish change
if (!as) {
      asRoute = undefined;
      asPath = getRouteAsPath(newRoute.pathname, newRoute.query, newRoute.hash);

What do you think? Have a good day 🙂

The goal of this lib is to reproduce Next's behavior as closely as possible.  If Next supports falsey values, then that sounds fine.  However, I know that "" empty string should be considered a valid URL, so I'd probably only want to consider as === undefined || as === null .
I'd be fine if you created a PR with this change!

@scottrippey thanks, I created


Navigation drawer take space from bottom

hello developer,
I have tried to use your library for one of my project and run fines in other devices but in Motorola devices NavigationDrawer take space from bottom.
Please let me know how would i remove this space.

Same issue here.

@JeffersonSchmitt
I had loaded whole module in my app instead of gradle line. and set up menu as i needed.


how to compute margin from BN statistics?

Hi,
I still can't understand how to compute margin from BN statistics after reading the code. Can you explain a little bit (why you compute cdf?)

Hi
I assume that the features after BN is Gaussian distribution, and calculates the margin based on expectation values of Gaussian distribution.
You can find more details on Appendix A of my paper (https://arxiv.org/pdf/1904.01866.pdf)
I hope it helps you understand the formular.


Skip nsx* related packages from trackupstream

Those are coming via rpm-packaging

Some background on this: rpm-packaging derived packages will automatically get a changelog entry added if the tarball changes upon osc disabledrun (which is what openstack-trackupstream does). That will not happen if the spec template changes, yielding a different renderspec result.
Maybe we should fix that problem in a more generic manner. Otherwise we'd have to remove a whole lot of packages from openstack-trackupstream (most Monasca packages for instance).

I'm not fully satisfied with this, but at least it will keep these two packages from causing trouble for now. I'll try to remember looking into creating a more permanent fix at some stage...

@JanZerebecki what is the proper fix for you?

I found out that there are packages (openstack-nova, openstack-glance, ...) that could be automatically updated from rpm-packaging, but are not, because they lack the renderspec _service entry. This avoids only the problem but still ingests upstream changes, though then we don't get he benefit of rpm-packaging changes.
There are more packages that use renderspec, e.g. python-os-vif.
For deciding what we should do, I think it mostly doesn't matter how often they are update via a change in rpm-packaging. Unless we do not want to fully automate it.

so they get some changelog entry from the trackupstream of the tarball

This also applies to the nsx packages, so the monasca ones are not different in that regard.
An idea for a fix: A complication in automating this properly with changelog generation from commits in rpm-packaging is that most commits in there won't affect most packages. So we should avoid uselessly changing packages with only changelog entries. To do that we would need to, for each new commit in the rpm-packaging branch and for each package try to apply renderspec. If that made a change add the commit headline to the entry in the changes file and record the commit id in a file in the package source. Otherwise discard the change. Maybe this needs to cache somewhere which rpm-packaging commit we already discarded for a package. If the file recording the last commit id is not there or is not in HEAD it just applies HEAD, adds thus in the changes file, and records the commit id. It should be possible to do this in https://github.com/openSUSE/obs-service-renderspec .

@JanZerebecki so we're not using the openstack service packages from rpm-packaging yet (mostly because they're incomplete upstream and because we have local modifications that never merged upstream). so thats why the openstack* packages don't have a service entry for tracking upstream.
In the current setup we basically don't want to automatically ingest changes from rpm-packaging upstream due to the .changes entry. we can cache the git hashes and figure out which git logs from <oldchanges..newchanges> can be added to the .changes entry. Patches accepted :-) Meanwhile I think this removes nsx* like all the other oslo* packages from trackupstream and we'll just have to remember udpating them manually whenever an upstream review changes. Certainly not ideal but this way it is at least consistent.

From the intersection of this job and DC9 the following packages have the same problem as the nsx ones: openstack-horizon-plugin-neutron-vpnaas-ui, openstack-horizon-plugin-monasca-ui, openstack-monasca-agent, openstack-monasca-api, openstack-monasca-log-api, openstack-monasca-notification, openstack-monasca-persister, openstack-neutron-vsphere, python-monasca-common, python-monasca-statsd.
Why not treat them the same way?

@JanZerebecki so the situation with monasca packages I already explained in https://github.com/SUSE-Cloud/automation/pull/2871#issuecomment-430572397 - and the commetn still applies.
the same is true for all the horizon plugin packages that you mentioned, they track stable/* tarballs and hence they must remain part of the trackupstream job. The purpose of this change was to remove packages that are not tracking git branches upstream from the openstack-trackupstream jenkins job.

I added now the monasca-statsd package to the list, but I would prefer to not overload this work with unrelated cleanups otherwise we'll have hours of discussion on git commit messages  ;)

The purpose of this change was to remove packages that are not tracking git branches upstream from the openstack-trackupstream jenkins job.

Ah! That is what I missed, they don't have a URL in the spec Source.
As you noted that would be useful information in the commit message.

@JanZerebecki Information is in the commit message now.


Develop

v0.0.1の実装をしたヨー

Pull Request Test Coverage Report for Build 20

11 of 335 (3.28%) changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-8.1%) to 14.943%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/game.go
0
28
0.0%

lib/titlescene.go
7
42
16.67%

lib/scenemanager.go
4
47
8.51%

lib/gamescene.go
0
64
0.0%

lib/input.go
0
64
0.0%

lib/gamepad.go
0
90
0.0%

Files with Coverage Reduction
New Missed Lines
%

lib/game.go
1
0.0%

Totals

Change from base Build 15:
-8.1%

Covered Lines:
91

Relevant Lines:
609

💛  - Coveralls


Remapping keys

Would be nice to be able to remap keys.
I use dvorak, and the the movement keys htns instead of hjkl.

Would like to see this as well now, especially considering the keybinding q (to close dijo) was removed recently. Instead of pressing 1 key, I now have to press 4 (shift + : + q + enter). Would be nice to see this configurable as well :smile:

Should be possible once a config file feature is implemented.

Environment variable would also work.

This is available as of v0.2.7, remains undocumented however. The following is a sample config for dvorak:
[look]
true_chr = "·"
false_chr = "·"
future_chr = "·"
grid_size = 2

[colors]
reached = "cyan"
todo = "magenta"
inactive = "light black"

[keybinds]
week_mode = "v"
global_week_mode = "V"

[keybinds.grid]
up = "n"
down = "t"
left = "h"
right = "s"

[keybinds.cursor]
up = "N"
down = "T"
left = "H"
right = "S"

Does not work on
❯ dijo --version
dijo 0.2.7

❯ cat ~/.config/dijo/config.toml
[look]
true_chr = "·"
false_chr = "·"
future_chr = "·"

[colors]
reached = "cyan"
todo = "magenta"
inactive = "light black"

[keybinds]
week_mode = "v"
global_week_mode = "V"

[keybinds.grid]
up = "r"
down = "t"
left = "d"
right = "n"

[keybinds.cursor]
up = "R"
down = "T"
left = "D"
right = "N"

looking at the code this is not implemented?


Wrong size of mask in RTMDet-Ins post-processing

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
In _bbox_mask_post_process function, when the argument rescale is True, the mask_logits will be interpolated to the original image size, but the width and height in scale_factor are reversed when calculating the original image size. If keep_ratio in Resize tranform is False, the width and height scale factor in scale_factor is difference, and it will make mask size wrong.
https://github.com/open-mmlab/mmdetection/blob/ee2e5423571d57d7f4156bade5a2cd6470fdffae/mmdet/models/dense_heads/rtmdet_ins_head.py#L498-L507
Reproduction

What command or script did you run?

python tools/test.py configs/rtmdet/rtmdet-ins_tiny_8xb32-300e_coco.py \
    https://download.openmmlab.com/mmdetection/v3.0/rtmdet/rtmdet-ins_tiny_8xb32-300e_coco/rtmdet-ins_tiny_8xb32-300e_coco_20221130_151727-ec670f7e.pth \
    --cfg-options test_dataloader.dataset.pipeline.1.keep_ratio=False

Did you make any modifications on the code or config? Did you understand what you have modified?

There are no modifications on the code or config.

What dataset did you use?

coco
Environment
not important
Error traceback
If applicable, paste the error trackback here.
none

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!
https://github.com/open-mmlab/mmdetection/pull/11231

@RangiLyu Hi, can you take a look at this issue, the same error is fixed in mmdeploy https://github.com/open-mmlab/mmdeploy/pull/2581


Investigate question generation from wiki-like texts

The Dual-LSTM Encoder model is pretty good as a retrieval-based model as compared to our Sequence-to-Sequence generation-based model.
We want to create a training set for our retrieval-based model. We can extract questions from a sentence, for instance:
Sentence: "The crownlands is one of the nine constituent regions of the Seven Kingdoms of Westeros."
Questions can be...
"What is the crownlands?"
"What is one of the nine constituent regions of the Seven Kingdoms of Westeros.?"
If we can make this possible, we can create a good training set for a retrieval-based Dual-LSTM Encoder model.
More details for the Dual-LSTM encoder can be found here.

Any resources so i can help ?

http://www.iro.umontreal.ca/~felipe/TALN2010/Xml/Papers/taln/taln2010_submission_172.pdf
http://www.cs.cmu.edu/~ark/mheilman/questions/papers/heilman-question-generation-dissertation.pdf
Check these out.

#21
#20
I have added the question generation from wiki-sites.


update version to 1.2.2-SNAPSHOT

Description
update version to 1.2.2-SNAPSHOT

Codecov Report

Merging #610 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #610   +/-   ##
=========================================
  Coverage     52.42%   52.42%
  Complexity      691      691
=========================================
  Files           177      177
  Lines          3111     3111
  Branches        233      233
=========================================
  Hits           1631     1631
  Misses         1356     1356
  Partials        124      124

Continue to review full report at Codecov.

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


Iframes do not respect preload or other plugin infrastructure

Operation System: macOS High Sierra
Beaker Version: 7011
This is functional via electron 2.0.0-beta-1
session.setPreloads()

Having beaker api and extensions be able to perform on the webview and the webview's iframes would make the browser much more extensible and usable.
If there are other ways that would work that would also be awesome!
Context (I mean by this that the preloads.js  doesn't run in iframes for Beaker)

Ah excellent, I missed that new feature in Electron. I'll be sure to add this when we take the dive into v2.

Word on the street is that this isn't going to be easy to implement in Electron. The recent Electron feature doesn't add support for iframes or workers. This may be a long way off.

Thank you @pfrazee its interesting because previous PRs said it was, but I saw the referred to comments.
Thank you

What's the status of this?  Iframes are a big problem for realistic content rendering of web content.

Quick note on this: Electron should have the support I need. I think I can implement this but I'm unsure about how to handle permissions. I think if the site asks for write permissions while in an iframe, I'll have to auto-deny.

@pfrazee is there any way to use the sandbox attribute? I'm not sure if it would be frowned upon to add browser specific values, but it might be beneficial for parent frames to restrict some of the Beaker specific APIs
There's also the experimental allow-storage-access-by-user-activation value, but I believe that's only available in Safari and Firefox at the moment. You might be able to see how they handle any prompts for write access though.
https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API

@andrewburgess Thanks for the tips, I'll take a look. BTW was that you that submitted datcool to r/beakerbrowser?

Yep, it's me!

Awesome, great site. I'm going to flair you for it

There might be a good case for supporting DatArchive and other Beaker APIs in same-origin (and non-sandboxed) iframes only. Going this route, I think the current permissions system would work alright without much changes.

Good point!
On Thu, Jun 20, 2019 at 8:57 AM Brecht Savelkoul<EMAIL_ADDRESS>wrote:

There might be a good case for supporting DatArchive and other Beaker
APIs in same-origin (and non-sandboxed) iframes only. Going this route, I
think the current permissions system would work alright without much
changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/863?email_source=notifications&email_token=AAJWCUYNFFJAY7DGPHQFVPLP3OED5A5CNFSM4ETM3BOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYFPVFQ#issuecomment-504035990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJWCU42O25TDE26LUX4MF3P3OED5ANCNFSM4ETM3BOA
.


Add pypi package publishing in CI/CD

This PR adds automatic pypi package publishing in CI/CD.
I still need to:

When to execute export
Set export repo to pypi not test.pypi

But first, I need to know if this approach is OK?

https://test.pypi.org/project/tiledb-vector-search/ is the published version on test.pypi under my credentials

The pipeline now finally passes with a small check:
https://github.com/dudoslav/TileDB-Vector-Search/actions/runs/7459145166


[QPG6100] Size optimizations

Problem
Further size optimization required to fit flash/RAM
Summary of Changes

Limit CHIP event queue
SDK submodule updated with size optimizations.

Could you add some notes on how this was tested?
how do we see that the qpg resource usage decreased?
how can we validate that qpg functionality did not regress?
The latter is tricky because our ToT seems somewhat unstable, however some best-effort would be great. We are trying to start enforcing testability on PRs to try get more stability into our head branch.

Could you add some notes on how this was tested?
how do we see that the qpg resource usage decreased?
Numbers before this PR
chip-qpg6100-lighting-example build:

Flash          | 506464/524288 - 96.60 %
Flash+NVM      | 522848/524288 - 99.73 %
Ram            | 59284/98272 - 60.33 %
Stack          | 512/98272 - 0.52 %
Heap           | 38476/98272 - 39.15 %
Ram+Heap+Stack | 98272/98272 - 100.00 %

Numbers after:

Flash          | 494836/524288 - 94.38 %
Flash+NVM      | 511220/524288 - 97.51 %
Ram            | 59272/98272 - 60.31 %
Stack          | 512/98272 - 0.52 %
Heap           | 38488/98272 - 39.16 %
Ram+Heap+Stack | 98272/98272 - 100.00 %

how can we validate that qpg functionality did not regress?
The latter is tricky because our ToT seems somewhat unstable, however some best-effort would be great. We are trying to start enforcing testability on PRs to try get more stability into our head branch.

We are using chip-device-ctrl to check the correct behavior of our example app.
As things are in flux in the tree, this is also an ongoing activity.
This PR was already put forward to alleviate mentioned PR #6943


Updated SignUp and Login Page

Title of the Pull Request
Successfully updated SignUp and Login Page

Related Issue
Closes: #202
Description
So, I have changed the UI of signup and login page to make it look more appealing, as the website is related to canvas editing, so I thought of some cool background it make it look rich!
Screenshots 📷

Type of change
What sort of changes have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[ ] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

@vishanurag  Sir, I have successfully made signup and login page.
Please review it and merge


luci asterisk 500 Internal Server Error

lede version: "LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685)"
Device: linksys wrt1200ac v1
After installing asterisk 13 and associated luci support I get the following error when i try to go to dialplan under the services->asterisk -> dialplan tabs
(However there are no errors under asterisk -> call routing).
Attached are some screen shots

_Sorry, the server encountered an unexpected error.
/usr/lib/lua/luci/dispatcher.lua:460: Failed to execute cbi dispatcher target for entry '/admin/services/asterisk/dialplans'.
The called action terminated with an exception:
/usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/map'.
A runtime error occured: /usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/tsection'.
A runtime error occured: /usr/lib/lua/luci/template.lua:97: Failed to execute template 'cbi/ucisection'.
A runtime error occured: [string "/usr/lib/lua/luci/view/cbi/ucisection.htm"]:15: attempt to call field 'json_encode' (a nil value)
stack traceback:
[C]: in function 'assert'
/usr/lib/lua/luci/dispatcher.lua:460: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:141: in function_

Should this be reopened? This package is still available and the problem still exists.


Tagged deprecated classes with @deprecate and a short explanation

I also got rid of the Groovy test classes

Merge completed manually on the following commit: b77694c


[Feature] Generate code for contract instance in such way that you can pass multiple addresses for events

Component
contract
Describe the feature you would like
It would be nice to have method like event_filter_with_address::<Event>(address: impl Into<ValueOrArray<Address>>). For example, you want to subscribe to all DEXs like uniswap.
/// Event filters.
#[automatically_derived]
impl<
    T: alloy_contract::private::Transport + ::core::clone::Clone,
    P: alloy_contract::private::Provider<T, N>,
    N: alloy_contract::private::Network,
> RouterInstance<T, P, N> {
    /// Creates a new event filter using this contract instance's provider and address.
    ///
    /// Note that the type can be any event, not just those defined in this contract.
    /// Prefer using the other methods for building type-safe event filters.
    pub fn event_filter<E: alloy_sol_types::SolEvent>(
        &self,
    ) -> alloy_contract::Event<T, &P, E, N> {
        alloy_contract::Event::new_sol(&self.provider, &self.address)
    }
    ///Creates a new event filter for the [`CreateProgram`] event.
    pub fn CreateProgram_filter(
        &self,
    ) -> alloy_contract::Event<T, &P, CreateProgram, N> {
        self.event_filter::<CreateProgram>()
    }
}

https://github.com/alloy-rs/alloy/blob/c6c91cc197c79c456433c79d60f81c8c5aa13001/crates/contract/src/event.rs#L32-L45
Additional context
No response

migrated this, as contract codegen is performed in core.  I am not convinced that we actually want an constructor _with_whatever here instead of a builder-style method

In that case if we want to do this it should be builder methods on alloy contract event that just delegate to the underlying filter?

that sounds right to me


Provide an existing gerrit.config

In case of migration it would be really useful to have an ability to provide a single gerrit.config file instead of/with providing parameters separately.
E.g.
docker run \
  --name gerrit \
  -e GERRIT_CONFIG_FILE=path/to/gerrit.config \ # with all existing configuartions
  -e WEBURL=http://my-gerrit.example.com \ # e.g. if we want different url
  -d openfrontier/gerrit

This is an interesting idea. Let me think about it.
Basicly, I can add a cp path/to/gerrit.config ${GERRIT_HOME}/review_site/etc in the gerrit-entrypoint.sh somewhere before setting other parameters according to the environment variables. This is not a big deal.
On the user's hand, you should mount this file into the container by using docker run -v or ConfigMap in k8s, but on the other hand, is it even better to mount  gerrit.config file on the ${GERRIT_HOME}/review_site/etc/gerrit.config directly? I've never done this before, just an idea worth considering.

For now I came up with something like:
https://github.com/dmitvitalii/docker-gerrit/pull/1/files
and going to test it soon.

I added some commends in your commit. Would you please check it there?


simple example does not finish because job-executor is not active

The simple application example runs into an endless loop while waiting for the processinstance to be ended because the final service task is async and there seems to be a problem with the job executor activation (though the default value is "true").
We should have a working example and a test that proves it works

Fixed already


Android: FLOATING POINT TEXTURE EXTENSION IS REQUIRED BUT NOT SUPPORTED.

It appears that loading data gives the following error:
RUNTIMEERROR: THE FLOATING POINT TEXTURE EXTENSION IS REQUIRED BUT NOT SUPPORTED.
I have a Samsung Galaxy S7. I've tried multiple browsers aswell but it keeps failing. The same javascript has no errors on pc browser.

Hello @wkoeter,
It looks like your phone might not have support for one of the WebGL extneions we use.  Go to http://webglreport.com/ and see if OES_texture_float is in the list of supported extensions.

Thanks for the fast reply. Indeed my Galaxy S7 seems to not support that extension. Is there a work around you might recommend? Or is it a dead end regarding my phone? Thanks in advance.

Currently, it's a dead end, but this was a recent change in Cesium and it's extremely unfortunate that the S7 does not support this extension.  I think we need to revisit this requirement since the S7 is such a popular phone.
I assume you tried Chrome?
CC @bagnell @pjcozzi

@mramato
Okey that is unfortunate indeed.
Yes i've tried Chrome, Chrome Beta, Opera and Firefox.

IIRC this is a very widely supported extension (not sure why the S7 would not have it) and there were no good alternatives to not using it.  We could consider a sub-optimal fallback if there's enough users expected to not have support for this for quite some time to come.

IIRC this is a very widely supported extension

According to https://community.arm.com/thread/9251, no Mali gpus support OES_texture_float, considering how popular Malu chipset is, I'm not sure we can claim it's widely supported enough to allow Cesium to be broken on it.  The Samsung Galaxy line alone (all of which are Mali I believe) is about 20% of the mobile market.  What's particularly bad is that this was a breaking change in a recent version of Cesium, so it used to work fine.  I understand there are some major technical hurdles here, but this is a huge reduction in Cesium device compatibility.

We've been looking into building on top of Cesium's VR capabilities (which is already limited to android devices) and this issue is really biting us since we invested in Samsung Galaxy + Gear setup for testing purposes

(which is already limited to android devices)

What makes you say this?  We've had Cesium running on Occulus devices in the past and there's no reason it can't work with other set ups as well (Vive, iphone, etc..).  I'll admit that it might need some work to update to the latest WebVR spec and definitely needs more testing, but the landscape isn't as bleak as you're painting it.  We would be happy to look at pull requests to improve Cesium's current implementation.
That all being said, I'm firmly in the "Has to work on Galaxy" camp, and VR compatibility is an unrelated issue I'd be happy to discuss on the forum (where more people can chime in what their thoughts).

@mramato should've kept it at +1 for Galaxy support :+1: My misspoken bleakness comes from ignorance as i'm just getting my feet wet with VR support. Will be in touch in the forums

Reported on the forum: https://groups.google.com/d/msg/cesium-dev/Lsj-KsgR__U/3YYz5s4mAQAJ

@bagnell and I discussed offline about adding an ugly but isolated ubyte RGBA fallback.  I marked this as next release since we may be able to get this to this in time.
There should also be a Chrome issue that @mramato may have the link too.

There's a workaround for this in #4700.  We would appreciate if anyone is able to test the branch in that pull request and leave your feedback here.  If all goes well, we plan to ship this in Cesium 1.28 tomorrow.


Implement notebook status

Fixes #20.  Relies on https://github.com/jupyter/jupyter-js-services/pull/62.
Adds notebook icons with kernel status indicator and kernel name title.

@dwillmer, ready to go.

:+1:


Test environments

Before merging @riccardo-forina so that we can evaluate the GH Environments on workflows:
Settings -> Environments -> New environment -> Name: "test" ->Check "Required reviewers" -> add e.g. me and you -> Environment secrets -> Add secret and add TEST_USERNAME and TEST_PASSWORD
This way we have a "manual approval" for running the CI and we don't risk leaking secrets, we have still to check how this works on forks, but it can be a smaller detail...

ok, I need to apply the environment in the reusable-workflow, @riccardo-forina ping me when the environment is available plz :-)


support for IPInfusion OcNOS

This PR adds support for IPInfusion OcNOS network operating system.
Since this platform is a non core scrapligo platform, I have added a community driver for it - https://github.com/hellt/scrapligo-ocnos
Currently, only boxen install works, packaging is not done.

now boxen package also works

booom! lgtm -- ready to merge?

Let's do this!
Any refinements would be easier to carry our based on this working MVP


Add "includes" method

Add a new .includes(value: T | predicate: T => boolean) method that determines whether the set includes the given value or a value identified by the predicate function.
Returns true if the value is found in the collection or the predicate function returns an item from the collection. Returns false otherwise.
Example
Set.of([1, 2, 3, 4, 5]).includes(2)
// true

Set.of([1, 2, 3, 4, 5]).includes(value => {
  return value > 3
})
// true

Set.of([1, 2, 3, 4, 5]).includes(value => {
  return value === 0
})
// false

Can i take this issue?

@binkpitch Hey, yeah sure.

@binkpitch please notice there's already pull request #5. You can also approach another issue: #4 or #1

@marcuspoehls Got it.

@marcuspoehls I notice that #4 and #1 has already been assigned but has been inactive. Can I take both issues?

@binkpitch Yeah sure. Both of the other two issues are inactive for 10 days. I appreciate if you want to submit pull requests for one or both 👍


flir_boson_usb: 1.2.1-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository flir_boson_usb to 1.2.1-1:

upstream repository: https://github.com/astuff/flir_boson_usb.git
release repository: https://github.com/astuff/flir_boson_usb-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: 1.2.0-0

flir_boson_usb
* Merge pull request #3 <https://github.com/astuff/flir_boson_usb/issues/3> from valgur/patch-1
* Fix minor issues detected by catkin_lint
* Fixing installation of nodelet_plugins.xml.
* Contributors: Joe Driscoll, Joshua Whitley, Martin Valgur, Sam Rustan

Holding for sync


Add make target for bringing up CouchDB for devs

Description
Currently, we have some code in repository to use a CouchDB database, but no supporting code to aid developers in using this.
Tasks

[x] create a docker-compose.yaml that can bring up the CouchDB instance alongside the docker developer container
[x] create a Makefile target to bring up docker compose-based stack for development.

DoD

[ ] There is a single make target to bring up the application with CouchDB, documented in the README

Already completed


debian pkgs not uploaded to istio-artifacts on gcs in postsubmit

Say the istio/istio master is at 1c498e7712badd8f3e885fbe3b77e4d2d3621843 (01/08/2018).
Visiting https://storage.googleapis.com/istio-artifacts/auth/1c498e7712badd8f3e885fbe3b77e4d2d3621843/artifacts/debs gives you "key does not exist" error instead of downloading the deb file. This is also true for pilot and proxy (although proxy uses its own sha as it is not part of istio/istio).
These debs are required to install istio on the VM that expends the service mesh. This problem was uncovered when I was trying to activate tests on the VM expansion feature (https://github.com/istio/istio/pull/2444). Maybe the debs upload steps were missed during the migration off bazel, as I don't see upload commands in either
https://github.com/istio/istio/blob/master/prow/istio-postsubmit.sh
or
https://github.com/istio/istio/blob/master/bin/push

is this still and issue ? if so can you solve it ?
(or do you have specific questions / need help with ? maybe @mattdelco can help you too)

I think it's still an issue (the push of debs by bin/push [and now "make push" was mostly deleted during the shift to a single monolithic dep) but it should be addressed as part of https://github.com/istio/istio/pull/2444 .

Is it still a problem ? Can you update and close ?

https://github.com/istio/istio/pull/2444 should have fixed it. Closing it now.


Fix malformed check to avoid 65-bit top overflow

Hopefully addresses https://github.com/riscv/riscv-cheri/issues/149, but I'd like to do some more checking before this gets merged!

Does this also mean we can no longer observe BASE > TOP for all tagged capabilities?

Does this also mean we can no longer observe BASE > TOP for all tagged capabilities?

Depends what you mean... This means that in 65-bits, BASE <= TOP, tagged or untagged. For tagged capabilities, that was (hopefully!) already true, even in a 64-bit space, with the exception of 2^64 itself. Note though that there isn't a CGetTop (GCTop?), so software would have to do base + length itself, with length saturating at uint_max.

Depends what you mean... This means that in 65-bits, BASE <= TOP, tagged or untagged. For tagged capabilities, that was (hopefully!) already true, even in a 64-bit space, with the exception of 2^64 itself. Note though that there isn't a CGetTop (GCTop?), so software would have to do base + length itself, with length saturating at uint_max.

Yes I mean in 65-bit space. I vaguely remember seeing cases in the cheri-compressed-cap library where use of the high bits would infer a top < base due to wrapping, so we couldn't assert that the decompressed top > decompressed base in all cases.

@arichardson Yes, that's exactly the problem this is to fix.

As with https://github.com/riscv/riscv-cheri/pull/116#issuecomment-2047932173 I've proved that the decoded bounds from encoded capabilities always have base <= top. It finds the problem before this fix and proves the property after this fix. Same caveats apply, including that I've had to change the SMT backend.
This should be good to merge.

... Now with better whitespace.


Baseline img width is not helpful

Problem
baseline styles sets img { width: 100%; }, but that is forcing us to override that line with img { width: inherit; }
Solution
Don't globally set img {width: 100%; }

Closed as per discussion in #14


Some problems about demo.py

snap_image always returns an error

cam.create_frame_filter works well in my 64-bit python, but in 32-bit python it causes the error:

Traceback (most recent call last):
File "E:/Program Files/JetBrains/PyProject/demo2.py", line 30, in
cam.add_frame_filter_to_device(h)
File "E:\Program Files\Python\Python36-32\lib\site-packages\py_ic_imaging_control-1.0-py3.6.egg\pyicic\IC_Camera.py", line 336, in add_frame_filter_to_device
OSError: exception: access violation writing 0x5C16F9CC

i don't understand what's the meaning of "cam.register_frame_ready_callback"

Any idea about how to  solve these problems?

What error is returned from snap_image?
A callback function is a function that is passed to the driver and automatically called when the driver is ready to call it, in this case when the frame is ready. The default callback function when called will set some flags that wait_til_frame_ready will wait to be set, which then allows access to the frame.

Thank you for your reply.
Here is the error:
Traceback (most recent call last):
File "E:/Program Files/JetBrains/PyProject/demo2.py", line 59, in
cam.snap_image(1000)
File "E:\Program Files\Python\Python36-32\lib\site-packages\py_ic_imaging_control-1.0-py3.6.egg\pyicic\IC_Camera.py", line 427, in snap_image
pyicic.IC_Exception.IC_Exception: 0
Why the function ‘handle_frame(handle_ptr, p_data, frame_num, data)’ is not used in the demo.py?
It also seems that the live mode in python has a much longer ‘exposure time’ and lower FPS than that in the official software of IC Capture.
I don’t learn C++. Maybe I need some time to understand the official examples.

@morefigs
I was able to save images a few times, but suddenly I go the same error
Traceback (most recent call last):
File "C:/Users/z003kpue/PycharmProjects/untitled2/py-ic-imaging-control-master/demo.py", line 49, in
cam.snap_image(1000)
File "C:\Users\z003kpue\PycharmProjects\untitled2\py-ic-imaging-control-master\pyicic\IC_Camera.py", line 427, in snap_image
raise IC_Exception(err)
pyicic.IC_Exception.IC_Exception: 0
Any idea why this occured, I removed the device ,reinstalled the drivers as well, but nothing changed.

I don't actually have one of these cameras anymore so it's hard for me to test.

Closed as stale. This was my first issue opened on GitHub. Thanks for this repo which helped me finish my internship six years ago.


docs: Update openid signing.md

This is a fix for https://github.com/sigstore/docs/issues/163

Summary

Remove duplicate and obsolete info from file.
Release Note

NONE
Documentation
Documentation

Docs only fix

@olivekl please review

@olivekl please review

Happy to review --- I'll loop back to take a look tomorrow.
By the way, it'd be great to add some more detail and context to the PR messages, esp. for any reviewers who might not be following the repo as closely. For example, in this case: what sections are obsolete and why, and whether you intend to do additional work on these instructions as part of a multi-PR progression, or whether the instructions will be in their final state after the deletions, that kind of thing. Likewise in the associated issues! That'll make it a lot easier for folks to review on the fly.


chore(ec2): rename EC2 any port check

Description
Rename check ec2_securitygroup_allow_ingress_from_internet_to_any_port to ec2_securitygroup_allow_ingress_from_internet_to_all_ports for a more accurate naming.
Thanks @jchrisfarris for the idea!
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'm going to put the no merge tag since we have to discuss what to do if we change a check ID since we have to include something different in the output, if not we are going to introduce breaking changes for the outputs.

I'm going to put the no merge tag since we have to discuss what to do if we change a check ID since we have to include something different in the output, if not we are going to introduce breaking changes for the outputs.

I think it would not be a breaking change since this is not the first alias and Prowler will work with the older check ID.

You can break customer's automation if we change the check_id to a new one. The alias should store the new name but the original name needs to be left there.

Closing this PR since it is not longer needed


Failure when running in Ubuntu 20.04 container

I'm running jurplel/install-qt-action@v4 within an ubuntu:20.04 container running on the ubuntu-latest build runner:
runs-on: ubuntu-latest
container: ubuntu:20.04

My Qt installation step is:
- name: Install Qt
  uses: jurplel/install-qt-action@v4
  with:
    version: '5.15.2'
    arch: 'gcc_64'
    archives: qtbase qtsvg qttools qtx11extras
    cache: true

This setup isn't working, and from the logs it appears that install-qt-action is trying to use Python 3.11.9 which expects a glibc version which isn't available on the system as well as printing a message about "zstd" being missing.
Here's the relevant portion of the output messages (with debugging enabled):
Setting up gstreamer1.0-gl:amd64 (1.16.3-0ubuntu1.3) ...
Setting up libglvnd-dev:amd64 (1.3.2-1~ubuntu<IP_ADDRESS>) ...
Setting up libgl1-mesa-dev:amd64 (21.2.6-0ubuntu0.1~20.04.2) ...
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.7) ...
Processing triggers for libc-bin (2.31-0ubuntu9.16) ...
Setting up libpulse-dev:amd64 (1:13.99.1-1ubuntu3.13) ...
##[debug]Resolved Keys:
##[debug]["install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-/__w/lmms/Qt-==0.20.*-==3.1.*-qtbase-qtsvg-qttools-qtx11extras"]
##[debug]Checking zstd --quiet --version
##[debug]Unable to locate executable file: zstd. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
##[debug]
##[debug]zstd version: null
##[debug]Resource Url: https://acghubeus1.actions.githubusercontent.com/pwcaf1VPrxS7fgOXBPcMD3dvo9HUjny8wRXGhIgjwlGHKIWSGp/_apis/artifactcache/cache?keys=install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-%2F__w%2Flmms%2FQt-%3D%3D0.20.*-%3D%3D3.1.*-qtbase-qtsvg-qttools-qtx11extras&version=3ab230e51801c7664d085e3f50065160a9156cc97720996ecd93bd08f6532c84
##[debug]Resource Url: https://acghubeus1.actions.githubusercontent.com/pwcaf1VPrxS7fgOXBPcMD3dvo9HUjny8wRXGhIgjwlGHKIWSGp/_apis/artifactcache/caches?key=install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-%2F__w%2Flmms%2FQt-%3D%3D0.20.*-%3D%3D3.1.*-qtbase-qtsvg-qttools-qtx11extras
##[debug]Failed to delete archive: Error: ENOENT: no such file or directory, unlink ''
Automatic cache miss, will cache this run
/__t/Python/3.11.9/x64/bin/python3 -m pip install setuptools wheel py7zr==0.20.*
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /__t/Python/3.11.9/x64/bin/python3)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
Error: Error: The process '/__t/Python/3.11.9/x64/bin/python3' failed with exit code 1
##[debug]Node Action run completed with exit code 1
##[debug]Finished: run
##[debug]Finishing: Install Qt

Please let me know if you know how to fix this. Thanks!

Interesting. I tried the following workflow and got a different error.
name: CI

on:
  push:
  pull_request:
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest
    container: ubuntu:20.04
    steps:
        - name: Install Qt
          uses: jurplel/install-qt-action@v4
          with:
            version: '5.15.2'
            arch: 'gcc_64'
            archives: qtbase qtsvg qttools qtx11extras
            cache: true

Output:
> Run jurplel/install-qt-action@v4
> Run actions/setup-python@v5
/usr/bin/docker exec  9b4f8e62bac0867a047bc7228e7c8aef70f8dec050d8926f02ccfd850ea1f4d7 sh -c "cat /etc/*release | grep ^ID"
> Installed versions
> Run jurplel/install-qt-action/action@v4
/usr/bin/docker exec  9b4f8e62bac0867a047bc7228e7c8aef70f8dec050d8926f02ccfd850ea1f4d7 sh -c "cat /etc/*release | grep ^ID"
Error: Error: Unable to locate executable file: sudo. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

It seems that both of us failed when installing dependencies:
https://github.com/jurplel/install-qt-action/blob/f03f05556819ceb3781ee2f455ec44c339d683c0/action/src/main.ts#L284-L331
For now I have no idea why it happened.

I tried installing zstd and now my error message is this:
Setting up libglib2.0-dev:amd64 (2.64.6-1~ubuntu20.04.7) ...
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.7) ...
Processing triggers for libglib2.0-0:i386 (2.64.6-1~ubuntu20.04.7) ...
Processing triggers for libc-bin (2.31-0ubuntu9.16) ...
Setting up libpulse-dev:amd64 (1:13.99.1-1ubuntu3.13) ...
##[debug]Resolved Keys:
##[debug]["install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-/__w/lmms/Qt-==0.20.*-==3.1.*-qtbase-qtsvg-qttools-qtx11extras"]
##[debug]Checking zstd --quiet --version
##[debug]*** zstd command line interface 64-bits v1.4.4, by Yann Collet ***
##[debug]zstd version: null
##[debug]Resource Url: https://acghubeus1.actions.githubusercontent.com/pwcaf1VPrxS7fgOXBPcMD3dvo9HUjny8wRXGhIgjwlGHKIWSGp/_apis/artifactcache/cache?keys=install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-%2F__w%2Flmms%2FQt-%3D%3D0.20.*-%3D%3D3.1.*-qtbase-qtsvg-qttools-qtx11extras&version=74fa578b216ee68fbe23bcedf63b12defa5faf7ce10d9a959c44eb2f55a66d5f
##[debug]Resource Url: https://acghubeus1.actions.githubusercontent.com/pwcaf1VPrxS7fgOXBPcMD3dvo9HUjny8wRXGhIgjwlGHKIWSGp/_apis/artifactcache/caches?key=install-qt-action-linux-6.5.0-1021-azure-desktop-gcc_64-5.15.2-%2F__w%2Flmms%2FQt-%3D%3D0.20.*-%3D%3D3.1.*-qtbase-qtsvg-qttools-qtx11extras
##[debug]Failed to delete archive: Error: ENOENT: no such file or directory, unlink ''
Automatic cache miss, will cache this run
/__t/Python/3.11.9/x64/bin/python3 -m pip install setuptools wheel py7zr==0.20.*
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /__t/Python/3.11.9/x64/bin/python3)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
/__t/Python/3.11.9/x64/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /__t/Python/3.11.9/x64/lib/libpython3.11.so.1.0)
Error: Error: The process '/__t/Python/3.11.9/x64/bin/python3' failed with exit code 1
##[debug]Node Action run completed with exit code 1
##[debug]Finished: run
##[debug]Finishing: Install Qt

Note that it finds zstd now, but it fails to parse the version when it runs zstd --quiet --version.
When I run zstd --quiet --version on Ubuntu 22.04, I get:

1.4.8

But on Ubuntu 20.04, it is:

*** zstd command line interface 64-bits v1.4.4, by Yann Collet ***

This could probably be fixed with better parsing.

Looks like you need to install sudo. It's not pre-installed on ubuntu:20.04.

Hmm, using sudo in a Docker container looks a bit weird. I think the action itself should detect if it's running as a root first.

I've installed sudo but didn't make it work:
Get:107 http://archive.ubuntu.com/ubuntu focal/main amd64 libnpth0 amd64 1.6-1 [7736 B]
...
Get:156 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libgstreamer-plugins-base1.0-0 amd64 1.16.3-0ubuntu1.3 [740 kB]
Setting up libwayland-server0:amd64 (1.18.0-1ubuntu0.1) ...
...
Setting up tzdata (2024a-0ubuntu0.20.04) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Configuring tzdata
------------------
Please select the geographic area in which you live. Subsequent configuration
questions will narrow this down by presenting a list of cities, representing
the time zones in which they are located.
  1. Africa      4. Australia  7. Atlantic  10. Pacific  13. Etc
  2. America     5. Arctic     8. Europe    11. SystemV
  3. Antarctica  6. Asia       9. Indian    12. US

<stopped here>

Why are our execution results not the same...? Maybe you have installed other packages before installing Qt?

Yes, I install some other dependencies prior to installing Qt.
I'm working on the "linux" job of this build.yml: https://github.com/messmerd/lmms/blob/linux-vcpkg/.github/workflows/build.yml
This is the bulk of the dependencies I install beforehand: https://github.com/messmerd/lmms/blob/linux-vcpkg/.github/workflows/deps-ubuntu-gcc-20.04.txt
And I ran into the tzdata issue too. It's difficult to install non-interactively. I used this:
sudo ln -fs /usr/share/zoneinfo/UTC /etc/localtime
sudo DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends software-properties-common

I tried using setup-python: false and it fixed the issue.

I tried using setup-python: false and it fixed the issue.

Good to hear that.
However the problem is still not found, so I may test it again later.


Investigate credit foreign key error while updating.

Edit: 16 attainments found with module_group_id='hy-SM-125118355' but no modules are found with that group_id. According to the date and student number the module missing might be Luonnontieteiden kandidaatti (00345).
Errors happen when trying to insert a credit into table but no course with course_id found.

Fix'd in Sisu, now can be found from importer db

Fix'd in Sisu, now can be found from importer db


fix(InstallCRDs): reverse CRD install status when necessary

When operator controller fails e.g. OOM but not installed CRDs successfully, this error will happen.
more details see #291

lgtm


RPC Method logging in plugin

Sister PR: https://github.com/runtimeverification/blockchain-k-plugin/pull/108

Subsumed #837


Does not seem to work in FF and Safari on a Mac

I used benchmark on this StackOverflow post but it does not work on Firefox and Safari. The times are shown as undefined on both browsers for each test case.

fixing asap, thanks for reminding this known problem

Seems fixed. Added screenshots for FF and Safari on the SO post .


Primary key required when generating from existing tables

I generated a full scaffold starting from an existing table.
This table has a primary key with autoincrement.
The generated views (and model) require the id upon saving or updating.

@sbolognini Can you explain it in little bit more details? we are not able to get it.
Your primary key in the existing table has a different name than id? that's what you mean?

@sbolognini Issue is fixed and the primary key is no longer required field when using fromTable option.
Thanks for catching it out. Also, do not forget to list your project under #631 list (if you want). :)


Database Initialisation

Hello,
I have addapted the previous PokeGame to 1.0 I have few troubles bedore pull request (if you want it ^^). The module works, but I didn't understand very well the database initialisation : when i run the bot after au full clean, my Table isn't created in NadekoBot.db. If i add it wtih sql-request no problems :/. I have added my DbSet , complete de onmodelcreating and ensure_data in the NadekoContext. What am I missing ?

You need to add a migration. Go into Nadekobot/src/Nadekobot (next to project json) with cmd and type dotnet ef migrations add pokegame, then start the bot. Assuming you setup all models correctly, migration will apply automatically when you start the bot and it will work

Sorry for bothering you, but i have an error when i run dotnet ef migration add pokegame so i cloned your dev, and I ran dotnet ef migration list it's return me the same error :/

oh, you need to readd old OnConfiguring method and then run the command, then readd it again. I think it's commented out in NadekoContext.cs

Thank you ! It works !
Are you interrested to get the Pokegame module in the "official" Nadeko ?

depending on how it's done

That's true


Bug/217

General information
Associated issues: #217
Checklist
Author:

[ ] One or more reviewers have been assigned.
[ ] Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix.
[ ] The associated GitHub issues are included (above).
[ ] Notes have been included (below).

Reviewers:

[ ] All automated checks are passing (green check next to latest commit).
[ ] At least one reviewer has signed off on the pull request.  Reviewers have two business days to review the pull request, after which the author may merge in the pull request unilaterally.

Notes
Makes the cluster toggle expand/collapse button more reliable.

Fixes bug where the button would be hidden if you hover over an edge that goes outside the cluster.
Fixes bug where if you expanded a cluster by clicking on the bubble the icon for the button would not update properly.
Makes the hover detection more precise. It now detects if you are hovering over the bubble itself, not the parent node or child nodes or edges in the cluster.
Briefly tested on chrome, safari and firefox on my machine.

Can you guys give this a try and let me know if it works as expected for you. Thanks.

Note: I tried this out on Safari on Mac.


Fix "to parquet" output: Bugfix code to write output to parquet file format

Abstar is not producing parquet outputs even when specifying parquet as the desired output in the command line. This issue is to fix the code to write output to parquet correctly.

Closing as this was completed by #4.


Decode EAN

@axxel
Hi,
Is there any way to identify the EAN code on the left?

The question is ill posed, because it implies that there is an EAN(13) code on the left but there is none. ;). The first bar of the start marker is missing. You could add it back in to make it a valid symbol again but the library will not detect this ill-formed symbol.

The question is ill posed, because it implies that there is an EAN(13) code on the left but there is none. ;). The first bar of the start marker is missing. You could add it back in to make it a valid symbol again but the library will not detect this ill-formed symbol.

@axxel Hi,
I use the decoding in this link. The EAN code on the left can be parsed, and the start character on the left actually exists.

I was talking about the first character of the text but the first bar of the start maker which are the first 2 black bars that usually are bit longer than the rest. This marker is required by the standard and is used for detecting the code. Apparently there are other readers which can handle this situation but zxing-cpp cannot. Sorry.
The line that rejects this barcode is this. You are welcome to try modify the code such that it works for you.

@axxel
If I directly comment out this statement, I can recognize the left EAN code in the image but the starting position of the postion obtained is wrong. And Will it affect the recognition of other codes?
How can I modify the appropriate code?  Thank you very much for your help and guidance.

And Will it affect the recognition of other code type?

It will pretty much break the library the linear barcode detection. Modifying the END_PATTERN is not really an option as is already the smallest meaningfully detectable pattern. There is no easy fix for your issue, I'm afraid.

If I directly comment out this statement (return 0), What are the possible costs?  Is the same as this:

It will pretty much break the library the linear barcode detection.

Both of your links point to the same line of code. I guess you meant something different?


Mixed IP and SNI in same Web App

It doesn’t seem to be documented, but consider a scenario where you have a Web App with an SNI SSL binding, and you’ve configured your DNS entry for that hostname as a CNAME for your-site.azurewebsites.net. No problems there. Now you add an additional IP SSL binding to the same Web App with a different hostname and certificate, and you map the DNS entry for that A record to the IP address that is newly assigned.
The undocumented part: you must go back and update the CNAME for your SNI SSL binding to sni.your-site.azurewebsites.net (adding the “sni” prefix). Otherwise, clients using the hostname of the SNI SSL binding will randomly get served the wrong certificate and fail.

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

ID: 8dfb8f30-3236-ad55-eabf-6940a7e16329
Version Independent ID: 8f4385a4-9ac2-38da-d243-ed3c00b0fd36
Content: Bind an existing custom SSL certificate to Azure Web Apps
Content Source: articles/app-service/app-service-web-tutorial-custom-ssl.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: cephalin

@npiasecki
Thanks for the feedback! We are currently investigating and will update you shortly.

@npiasecki This might be more advanced than what the document is trying to achieve. We have requested the doc author to review your feedback and make any necessary changes. Thank you for the feedback.

@npiasecki Thanks for your feedback, and yes it's true that it's a bit of an advanced scenario. I'm tracking the feedback internally at https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1225308. #please-close.

Thanks, I'm not saying it has to be on that page, but could be appropriate for a reference section. If I hadn't found it on some random Microsoft guy's blog, I'd be in for days of run-around with support.