FFmpeg windows builds will be removed

I developed scrcpy for Linux, where the dependencies are just retrieved via apt.
But scrcpy had to work on Windows too. I'm bad at build systems, and have a very limited knowledge of Windows, so I initially just recommended to build from something which looks like a Linux environment (MSYS2). For the first public release (v1.0), I even just took the DLL installed from the MSYS environment.
But it was too cumbersome for me to create a release (I had to build from a Windows machine), so I wrote some script to cross-compile the binaries from Linux, and just downloaded prebuilt dependencies of FFmpeg and SDL (106b87a4d2459ae881ab89b987cc9347a843a4ea). This was a quick&dirty solution (which btw makes adding or upgrading dependencies very annoying). I'm not very proud of it, but at least it was good enough for solving my problem.
The FFmpeg binaries are downloaded from https://ffmpeg.zeranoe.com/builds/. This site will close soon:

ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be removed. If you're using Zeranoe FFmpeg Builds in your product, please ensure that you have a hosting strategy in place by the 18th. Thank you to everyone who supported the project along the way!

so the release script of scrcpy will just stop to work correctly.
In the short term, I could just keep the latest versions and ship them. But it becomes urgent to build the dependencies along with scrcpy. And an option to build static binaries would be awesome (#1624).
https://linuxfr.org/users/roger21/journaux/ffmpeg-pour-windows-ca-va-couper

#1484 also suffered from dll hell. IMO, it can be solved in the same time?

I even just took the DLL installed from the MSYS environment.

MSYS2/MinGW FFmpeg builds are dynamically linked. So, you have to download all the dependencies which may not be the right solution here.

The FFmpeg binaries are downloaded from https://ffmpeg.zeranoe.com/builds/. This site will close soon:

How those guys build it. Any script?

so the release script of scrcpy will just stop to work correctly.

Neevvveeerrr. With CI, possibility is endless.
One lazy solution would be to create a package for MSYS2 which already provides FFmpeg and SDL2. But the package will not be a standalone like the current releases.

Not sure if it will help much, but ffmpeg peeps already have a compilation guides: https://trac.ffmpeg.org/wiki/CompilationGuide
And https://github.com/rdp/ffmpeg-windows-build-helpers looks as the best option for cross-compiling.
But need to understand what the end goal would be, as compiling ffmpeg every as a dependency for scrcpy would be time consuming.

MSYS2/MinGW FFmpeg builds are dynamically linked. So, you have to download all the dependencies which may not be the right solution here.

Yes, that's what I did for v1.0. :smile:

How those guys build it. Any script?

I don't know.
In theory, I'd like to do something similar as we do in VLC (cf contrib/src/ffmpeg/rules.mak).

Neevvveeerrr. With CI, possibility is endless.

Yes, but I would like to be able to build the whole release from any computer (running linux) in a single script (even without docker) :)

Not sure if it will help much, but ffmpeg peeps already have a compilation guides: https://trac.ffmpeg.org/wiki/CompilationGuide
And https://github.com/rdp/ffmpeg-windows-build-helpers looks as the best option for cross-compiling.

Thank you for the links :+1:

as compiling ffmpeg every as a dependency for scrcpy would be time consuming

Only if we want/need to, otherwise it could use the dependencies provided by the system.
But it would also allow to create a minimal static build (that would be awesome to distribute the latest scrcpy release on linux).

In theory, I'd like to do something similar as we do in VLC

If that need a script to be added in scrcpy, would you add it?

Yes, but I would like to be able to build the whole release from any computer

By whole release, do you mean to compile dependencies also? Or scrcpy only?

If that need a script to be added in scrcpy, would you add it?

Yes, a script which builds ffmpeg and a script which builds SDL. :+1:
I would like to replace prebuild-deps by a directory deps with 3 subdirs:

deps/src/ffmpeg
deps/src/sdl
deps/src/adb

Each subdir would contain a script to build and install the dependency into some destination directory (or just download and verify checksum for adb). The resulting built libraries would be used by the scrcpy build system.
But that should be optional (e.g. we should be able to build scrcpy against the system ffmpeg).

By whole release, do you mean to compile dependencies also? Or scrcpy only?

Yes, dependencies included.
The release script should generate the files posted on every release:

scrcpy-server
windows 32 bits release
windows 64 bits release

If we compile the dependencies ourselves, either we just include the dll in the release, or better we build the scrcpy binaries with FFmpeg and libsdl statically linked.
And if that's the case, we could also generate:

linux 32 bits release
linux 64 bits release

This is just what I have currently in mind, maybe there are better ways.

Found something https://github.com/rdp/ffmpeg-windows-build-helpers.git. I will try it.

Found something https://github.com/rdp/ffmpeg-windows-build-helpers.git. I will try it.

Be aware that the license of this script is GPLv3.

Hi, @rom1v
Would you accept something like mxe? I built SDL2 and ffmpeg using mxe. After it, I built scrcpy against the output dlls in mxe and copied needed dll by using copydlldeps (a tool from mxe).

Would you accept something like mxe?

For now, I don't know enough to have an opinion.

MXE (M cross environment) is a GNU Makefile that compiles a cross compiler and cross compiles many free libraries such as SDL and Qt.

So compiling the cross compiler is a necessary step?

Oh, ffmpeg.org provides an alternative link to builds of FFmpeg:

http://ffmpeg.org/download.html#build-windows
https://github.com/BtbN/FFmpeg-Builds/releases

This does not change the goal to get a proper solution, but it could help in the short term :)

Would you accept something like mxe?

For now, I don't know enough to have an opinion.

For demo and testing, I can provide a PoC in a branch of my fork repo.

MXE (M cross environment) is a GNU Makefile that compiles a cross compiler and cross compiles many free libraries such as SDL and Qt.

So compiling the cross compiler is a necessary step?

From my point of view, the answer looks yes.

Hi, @rom1v
You can try this commit if you have an interest in this.
I just simply modified the win64 version.
Thanks.

@npes87184 Oh, thank you! Very interesting.
It looks great in the Makefile.
However, since it rebuilds everything (including gcc and other stuff), it takes too much time. :disappointed:

@npes87184 Oh, thank you! Very interesting.
It looks great in the Makefile.

 When it executes the copydlldeps.sh, it shows that some dlls does not find. Even though, I can run this in my windows 10, I am not sure if it affects or not.

However, since it rebuilds everything (including gcc and other stuff), it takes too much time. 😞

It also has pre-built libs here. However, I have not tested it.
BTW, if we want to do static build, we need to write down all libs that linked by ffmpeg and SDL2. A little bit annoying.

BTW, if we want to do static link ffmpeg, it also needs to care about the license.

True.
Static link is a nice-to-have solution so that Linux users could quickly test the latest version using a binary. If we are able to build the deps dynamically for Windows, it's already good.

Oh, ffmpeg.org provides an alternative link to builds of FFmpeg:

http://ffmpeg.org/download.html#build-windows
https://github.com/BtbN/FFmpeg-Builds/releases

This does not change the goal to get a proper solution, but it could help in the short term :)

I create a PR that use ffmpeg built from BtbN in #1838 .

Save and modify the system

Until this is resolved, you can prepend the ffmpeg url with https://web.archive.org/web/20200916091820/ (like https://web.archive.org/web/20200916091820/https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.3.1-win32-shared.zip) in prebuild-deps/Makefile

@deep9 Thank you for your suggestion. I tested, but their server are quite slow for downloading such archives (and I guess it's not very fair to download from them).
Instead, I added the releases on GitHub, and referenced them: 5dc3285dbf807553f86346ab16d0891cfeb32ab7

@rom1v Sure, this is more stable solution, mine was intended as a workaround :)

May I suggest using Conan? It's able to both download prebuilt binaries (if available) or build automatically from the source. I haven't used it much, but it's worked well for me so far.

Problem is it's much better integrated with CMake. Meson, not so much.

Note: it seems that meson can use the CMake find_package for compatibility.
(However, Conan is not available is official Debian repositories, so I prefer not to depend on it.)

Unsubscribe

@Menstro

Unsubscribe

To unsubscribe from a thread on github, there is a button Unsubscribe on the right column, in the "Notifications" section.

(However, Conan is not available is official Debian repositories, so I prefer not to depend on it.)

Conan can be installed using pip.
Even then, seems the official Conan repo doesn't have a ffmpeg recipe yet. Maybe once it's available, we could give it another thought.

Even then, seems the official Conan repo doesn't have a ffmpeg recipe yet. Maybe once it's available, we could give it another thought.

It's available and functional: https://github.com/conan-io/conan-center-index/pull/6707

If we need to build dependencies on windows, I suggest to try meson's wrap, which can helps to gather and build dependencies. See https://github.com/Genymobile/scrcpy/issues/1624#issuecomment-918846360.

However wrapdb has SDL2 but not ffmpeg.

A meson-ported ffmpeg hosted by gstreamer is https://gitlab.freedesktop.org/gstreamer/meson-ports/ffmpeg but it's ffmpeg 4.1.

I published a custom build specific to scrcpy (containing only the features used by scrcpy):
https://github.com/rom1v/scrcpy-deps
Here is a commit (not merged yet) to use it: https://github.com/Genymobile/scrcpy/commit/custom-ffmpeg
For comparison, here are the sizes of the dll for FFmpeg 5.1.2:

before: 89M
after: 4.7M

And now, FFmpeg 6.0 :tada:
https://github.com/rom1v/scrcpy-deps/releases/tag/6.0-scrcpy


GRSciColl - update UI to accommodate new contact model

The new contact model is now implemented: gbif/registry#379 (comment)
We need to show the new contacts on the GRSciColl pages.
Right now there are 2 fields in collections and institutions (in the API):
contacts -> old model
contactPersons -> new model
the same for the endpoints, e.g.: https://api.gbif.org/v1/grscicoll/institution/a2e50ff3-62ae-419a-8749-455342e0b455/contactPerson
The IH synch will only update the contacts under the new model.

@MortenHofft I think the portal might still be displaying the old contact, see this example:
https://www.gbif.org/grscicoll/institution/79adfa73-4a2e-4b3b-9e2c-4aa83e05d2b8
https://registry.gbif.org/institution/79adfa73-4a2e-4b3b-9e2c-4aa83e05d2b8/contact

I don't know if this is related but I think the portal might still display the old contacts (reported by one of our users):
https://www.gbif.org/grscicoll/institution/442fa096-b2bf-4ecc-b513-ae0958eeec25
https://registry.gbif.org/institution/442fa096-b2bf-4ecc-b513-ae0958eeec25/contact

Yes that is the same issue: that the API has been changed and so the website shows stale content. This was the same issue that we recently addressed when rewriting the registry-console.

closed by https://github.com/gbif/portal16/commit/93ad21aa2481beb40b68e046240d13eb993b2a4a


Add app.alert - Like RedAlert

:boom: BOOM :boom:
We can do alerts like RedAlert style.
app.alert(title: "Hey There", message: "Want a sandwich?") do |choice|
  case choice
  when "OK"
    mp "Here's your sandwich"
  when "Cancel"
    mp "Fine!"
  end
end

<3


Remote Storage Failed

Debug Data:

UserID => 99
{"status":"failure","errorCode":"3007","errorMessage":"Card storage feature is not enabled for this<EMAIL_ADDRESS>

I think the error message says what you need to fix in here: Card storage feature is not enabled for this merchant. That means you should log in to your iyzico merchant account and enable the Card storage feature.


dispatch 可以返回future的类型吗

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

如果当前组件有对应的effect的处理函数，dispatch返回对应effect的函数返回结果。


Update Licesne file [Final Doc]

Final Doc slides
Update License

[x] Update License file.

Originally posted by @tusharagg1 in #130

Related Commits:

Update LICENSE


Module Generation

It would be great to have a yeoman style module generation. Like pepperoni generate module:Login would create a folder in modules with defaults. Isn't it ?

Yes, that's quite a nice idea. If you have time you could prototype something and we can see how it would work!

Sure ! I think yeoman is not the only option here, will come up in a few days.

Rather than yeoman we can also use plopjs and gluegun, they all can do the job but plop.js seems more lightweight and easy to implement.
I'll come up with experimental branch in few days.

It's here https://github.com/sercanov/pepperoni-app-kit/tree/feat/generator
What do you think ?

Hey @sercanov, do you mind opening a PR? Would be easier to review and keep track of it. Based on my initial glance it looks nice. I think what we also want in the future is to be able to add extra "features" to a sample app, such as Auth0 (removed due to many people not liking it) and other optional things.

Hey @krivachy sure, opening right away.
Hey actually there are a lot of to do and plenty of possibilities. It may evolve a whole selective generator in the end.


Containerization

It would be interesting to have a container image of the app. This way I would be able to launch a container on a remote desktop and ping the host address.
Something like Docker.

I can provide a dockerized version, if you are interested.

Yes, you may create PR with docker :)

Hello guys! Thank you for your interest!
@davebulaval Yes, we thought about this possibility and expected to implement it in the future versions. But now our current focus is on supporting as many data types as possible in Label Studio.
@JStumpp We are interested in it. If you do PR, we will certainly implement this functionality in the project.

@JStumpp I cannot help much but I can at least valide the build of the container and if the functionnality work.

@davebulaval no problem, I am on it. Should be ready tomorrow.

The dockerization is ready, see the pull request https://github.com/heartexlabs/label-studio/pull/31
Give it a try:
docker run -p 8200:8200 -t -i amaigmbh/label-studio -c config.json -l ../examples/chatbot_analysis/config.xml -i ../examples/chatbot_analysis/tasks.json -o output

or mount a folder with your custom configuration files
docker run -p 8200:8200 -t -i -v C:\docker\custom:/app/examples/audio_regions amaigmbh/label-studio

First one work well. Second I have a invalid mode error.

@davebulaval can you post the exact error? Are you running on windows and did you create the path C:\docker\custom with files from an example?

@JStumpp @davebulaval First one works well, yes. But I can't reproduce with this instruction the second one.
docker run -p 8200:8200 -t -i -v C:\docker\custom:/app/examples/audio_regions amaigmbh/label-studio

Could u expand the instruction? When I started LS using an example from the local path, Docker did not find the config outside directory. And the LS starts with default config audio_regions
My version (my environment is macOS):
docker run -p 8200:8200 -t -i -v /Users/shevchenkonik/named_entity:/app/examples/named_entity amaigmbh/label-studio


The documentation is outdated

Hello, it is not possible to reproduce the steps in this documentation because the azure interface has all been modified.

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

ID: ecbbb69a-f2dd-ed42-d887-14a72494000f
Version Independent ID: 7e5c254a-fd12-0fc6-fc7d-61f4ef009226
Content: Consume multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework
Content Source: docs/spfx/use-aadhttpclient-enterpriseapi-multitenant.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

It has been 2+ years to this issue and the documentation is still not updated, is there any update on this?


udsoncan-1.17.1 no longer available

There is a new version of 'udsoncan' (1.18.1) available. Has this new version any influence on the function of the overall software? The reason for my question is, that my Raspi CAN-configuration (vitodens 300-W-B3HG)  is running well with the can-utils commands but not with the open3E commands.

I have now tested the open3E software with both 'udsoncan' versions: no difference in the failure behaviour on my Raspi CAN-configuration. So the reason for not running on my system seems to have (unfortunately) other reasons. Sorry for the trouble caused.

Hi, thank you for your interest in the project :-) Yes udsoncan will be updated in the requirements soon.
Here some facts for the current development state of E3 gas boilers: We are currently working on decoding datapoints for gas devices. First scans using doip are done. If you want to test, then try connecting the service access point and connect through doip, e.g. python3 Open3Eclient.py -d <IP_ADDRESS> -r 256 -v. Datapoint 256 should be readable. Sadly at this time the mechanism for accessing uds over can is not fully understood as it is done for heat pumps. If you want to contribute, please try a can diagnostic scan using https://github.com/CaringCaribou/caringcaribou. There you should try cc.py uds discovery and then cc.py uds services.


Bad email address in authentication form should display validation errors

On the /signin page, if I enter an invalid email address like "test@test" it will crash the app.

Its actually not crashing the app, and the backend is throwing the error correctly.
fcc:middlewares:error-reporter Email is not a valid email address. +5s
{ Error: Email is not a valid email address.
...
...
{ type: 'errors',
     message: 'Email is not a valid email address.',
     redirectTo: '/email-signup',
     status: 400 } }

I think this needs, investigation to check why the error message isn't displayed as a flash message.

What if you were to give the input part of it the type of "email". Doesn't HTML5 come with a way to ensure that the input is a valid email?

I think its already the case.

So then wouldn't that be enough of an alert? Or am I missing something

Yes, the issue is its not triggered for some reason. Here is view if you are interested in debugging
https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/server/views/account/email-signin.jade
Reach out to Contributors Chat room for any assistance in contributing.
Thanks.

Was this issue resolved? The flash message seems to be working fine for me.

Hi @Radlerz1 thanks for reporting. Yes indeed.
Just to clarify for future reference:

The native HTML validation is fine, turns out I completely missed the fact the test@test is actually a valid email just like test@localhost
We were not getting the server side validation messages, for a reasons unknown to me. But this has now been resolved in some recent changes merged within the last day.

Closing.


Dynamic imports shouldn't be transpiled in CommonJS

Bug Report
When using a dynamic import() in a TS codemod, it gets transpiled to a require() (wrapped in a Promise):

The issue with this is that import() are the only way for CJS files to import an ESM file. So we need to be able to keep the dynamic import in the transpiled code (because using require in those cases will crash as they aren't compatible with ESM).
Also import() is fully supported by Node, even in CJS:  see https://nodejs.org/api/esm.html#import-expressions.

Dynamic import() is supported in both CommonJS and ES modules. In CommonJS modules it can be used to load ES modules.

🔎 Search Terms
esm, ecma script module, ecmascript module, common js, commonjs, cjs, dynamic import, import()
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about esm

⏯ Playground Link
Playground link with relevant code
💻 Code
import a from './a'

console.log(a)

const b = async () => {
    const a = await import('./a.mjs');
}

🙁 Actual behavior
import() is transpiled as Promise.resolve().then(() => __importStar(require('./a.mjs')))
🙂 Expected behavior
import() should transpiled as import() as dynamic imports are supported in CJS (and are the only way to import ESM from CJS)
And this, we should generate this:
"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
const a_1 = __importDefault(require("./a"));
console.log(a_1.default);
const b = async () => {
    const a = await import('./a.mjs');
};

You need to use module: "node16" (alternatively, nodenext) to use dynamic import in CJS.

Duplicate of https://github.com/microsoft/TypeScript/issues/52775

I don't think I can:
node16 & nodenext are using top level ESM:

node16:

nodenext:

Edit: in the REPL, if I switch to module: node16, and then switch back to module: commonjs, it seems to output the proper code (see in TypeScript Play)
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const a_1 = require("./a");
console.log(a_1.default);
const b = async () => {
    const a = await import('./a.mjs');
};

This may be an issue in the REPL itself (as moduleResolution isn't exposed there)
I'll close this issue. Thanks for your reply 🙇


Forecast/feature

Added the beginning of the 5-Day Forecast weather card.

Everything looks good. The app is functioning properly. Going to merge with the main branch.


Lumen AliasLoader not found

Although you don't officially support lumen I just though I would point out that Lumen does not support Illuminate\Foundation\AliasLoader so it might be worth doing a check and only making it call registerAliases() if it is a detected Laravel install and making Lumen users setup the alias themselves.

see https://github.com/yajra/laravel-datatables/issues/317 , i give the answer:
if you set class_alias in your bootstrap/app.php, you don't need registerAliases() in the DatatablesServiceProvider,so you can comment this line

 $this->registerAliases();

@jasonz1987 Thats great but I am not a fan of changing files in my vendor folder I would be really nice if there was some sort of check. I ended up just putting the code in a try catch block then I could use the same fork for laravel and lumen

Fixed on v6.1.0. Kindly check and verify. Thanks!


Performance regression testing

What's the new feature?
Introducing a mechanism for regression testing of algorithm performance (in terms of speed).
What value does this add?
This would support assessment of how performance either improves or regresses on development of new or existing features or software architecture.
Is there an alternative you've considered?
No response
Additional context
This was a recommendation made during Sprint 15 Review.

Could be quite a large ticket. Depends on how thorough we want to be.

If running during GitHub workflows, save timing data to a Git Gist.

Split this into issue #725


🚀 Feature: Export types

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
I’m testing console-fail-test  in one of our projects within our monorepo.
Our Vitest env is configured using a single vitest.config file pointing to a setupTest.ts file inside each monorepo project, so I can’t change the shared vitest config, because it will affect all projects.
Note that my setupTest.ts is a TS file, so when I’m importing console-fail-test TS is complaining about missing declaration types for this package:
As a workaround I had to add a couple of TS and Eslint ignores to bypass this issue:
// setupTest.ts

// @ts-expect-error console-fail-test is not exporting types
import { cft } from "console-fail-test";

// eslint-disable-next-line @typescript-eslint/no-unsafe-call
cft();

Additional Info
No response

Ah, I would have thought this would have already been done by #209. Definitely a bug that should be fixed. Thanks for filing!

@all-contributors please add @joel-daros for ideas.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙

@JoshuaKGoldberg I was inspecting this issue and it looks like there is something related to the package release action.
The build process is generating the types correctly in the lib folder, but there is something weird happening when the Github pipeline is trying to generate the release and upload it to npm. I think you’re using your JoshuaKGoldberg/release-it-action script for this, which I’m not familiar with.
I don’t know if there is anything related but, the code published in the npm isn’t actually the code built in lib folder but the source code.

Interesting! I also see the published package doesn't have provenance noted, the way more recent create-typescript-app projects do. I wonder if I'd manually published, forgot to create the .d.ts files at the time, and forgotten about it since?
Let me refresh the tooling now, publish a new patch version, and see where that goes...

Ok looks like the 0.4.0 publish from #574 fixed things!
https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgYwGbwL51VCI4BEyEAdgM4QA2ApgLSoCGwltM1ZMBA3AFA9owAFAEouQA
import { cft } from "console-fail-test";

cft(); // This is typed now, hooray!

Thanks for the issue @joel-daros, I'm a bit relieved that this is working!

I really appreciate the fixes @JoshuaKGoldberg , but I think we still have an issue that is preventing the types from working correctly.
There are no errors in the TS playground, but when the package is installed locally in a real project, it still complains about missing types for console-fail-test.
I think the way you’re exposing the "exports" types in package.json is the culprit:
	"exports": {
		".": {
			"types": {
				"import": "./lib/index.d.mts",
				"require": "./lib/index.d.ts"
			},
			"import": "./lib/index.mjs",
			"require": "./lib/index.js"
		}
	},

I made some changes in my local env and looks like the changes bellow solve the issue:
	"exports": {
		".": {
      "import": {
        "types": "./lib/index.d.ts",
        "default": "./lib/index.js"
      },
      "require": {
        "types": "./lib/index.d.cts",
        "default": "./lib/index.cjs"
      }
    }
},

I’ll be happy to submit a PR with these changes if you agree that’s right way to solve it.

@arethetypeswrong/cli agrees:
$ npx -y @arethetypeswrong/cli -P
^[
console-fail-test v0.4.0

Build tools:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
⚠ A require call resolved to an ESM JavaScript file, which is an error in Node and some bundlers. CommonJS consumers will need to use a dynamic import. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/CJSResolvesToESM.md

💀 Import failed to resolve to type declarations or JavaScript files. https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/NoResolution.md

┌───────────────────┬──────────────────────────────┐
│                   │ "console-fail-test"          │
├───────────────────┼──────────────────────────────┤
│ node10            │ 🟢                           │
├───────────────────┼──────────────────────────────┤
│ node16 (from CJS) │ ⚠ ESM (dynamic import only) │
├───────────────────┼──────────────────────────────┤
│ node16 (from ESM) │ 💀 Resolution failed         │
├───────────────────┼──────────────────────────────┤
│ bundler           │ 💀 Resolution failed         │
└───────────────────┴──────────────────────────────┘

...and you're right @joel-daros - I was only checking the one module resolution mode on the playground. A PR would be lovely, yes please!


Mad Joker card is different

Describe the Issue
I've been using this, and it is quite good, but there is a difference in the calculator and my game: My Mad Joker is a different card to yours.
Mine is: "+10 Mult if played hand contains a Two Pair"
Your one is: "+20 Mult if played hand contains a 4 of a Kind."
Describe the solution you'd like
I would like this to be put into your calculator so it can be used in the calculator properly.
Describe alternatives you've considered
You might still be able to add it in as another Joker card instead of replacing your own version.
Additional context
I do not know whether this is version specific, but for context I am playing version 1.0.1 - FULL on PS5
Added 2 Screenshots for proof that I do have those cards (Mad_Joker_1 is to show the card, Mad_Joker_2 is if you need it for assets etc.)

Is this still an issue after #68 ?

no


Add mapping_set_id to JSON response

Do it the same way as in #34.
Make sure that the other field is already in JSON format.
Need to change this in the mapping_set:
{
      "object_source": "http://purl.obolibrary.org/obo/hp",
      "uuid": "0025bf7bc8d551c4b4f2c34d6e89d58f",
      "subject_source": "http://purl.obolibrary.org/obo/mp",
      "other": "PMID:32585259",
      "mapping_date": "2022-02-01",
      "comment": "KidsFirst; see ticket https://github.com/mgijax/mammalian-phenotype-ontology/issues/3497",
      ...
      "mappings": {
        "href": "http://localhost:8008/mapping_sets/0025bf7bc8d551c4b4f2c34d6e89d58f/mappings"
      }
    }

A possible solution, in case the field other has something:

If the content in other is JSON, add the key sssom_api:mapping_set_id
If not, add the content in other to the key other_sssom, and add the key sssom_api:mapping_set_id

After some meetings, it was decided not to change the SSSOM model. The solution is to have endpoints only for the UI; we can add any field important for the UI and one that is SSSOM conform.


[discussion] lazy load spreadsheet feature(s) for speed and memory footprint?

As much as I have seen I think that the entire Excel file props are loaded into memory to read and write. To optimize performance, I suggest selectively loading and manipulating data in memory rather than the entire dataset. This could boost efficiency, especially for larger files and scenarios where only specific data is modified. I think most of the workloads are based on using a limited feature set anyway.
I'd appreciate a good discussion on this proposal.

@schungx you raise a very valid point, but this library is not implemented in that way. The spreadsheet is decoded into memory props which is then manipulated as needed. And on write, the props stored are written to file.

True.  I am not knowledgeable enough about the Excel file format to know how it is done, except that it is XML-based and zipped (probably compressed).  With that, it may not be possible to stream it without reconstructing the whole thing in memory first, because essential data structures may reside at the very end...

Perhaps flags to control what info should be loaded.  That would give more flexibility.

It implements lazy_read(path) in case a large file is to be edited.
This implementation allows the user to specify when to deserialize on a per-sheet basis.
// Read raw data (not deserialized)
let path = std::path::Path::new("./tests/test_files/aaa.xlsx");
let mut book = umya_spreadsheet::reader::xlsx::lazy_read(path).unwrap();

// Deserialize the first sheet
let mut sheet = book.get_sheet_mut(&0).unwrap();

A first stepping stone could be, for example, the following renovations

reading of Excel files is done by lazy_read(path).
The system automatically deserializes each portion when needed.
a method to deserialize all parts is also provided.

@MathNya, i felt lazy_read(path) is lacking sufficient documentation for exact use case. I was using book.get_sheet(&0). unwrap() and getting error.
Also, once the sheet is loaded that would mean things like table, protection etc are also loaded into memory props. I was meaning for that to be loaded lazily.
I am open for discussion on this issue. Thanks for responding

Or some form of a builder API:
let excel_reader = ExcelReaderBuilder::new().with_values().with_formulas().with_pictures().build();

// The following reads the Excel file Book.xlsx, but only with values, formulas and pictures.
// Other stuff like formatting, drawings, etc. are skipped (i.e. default values).
// It would be like the sheet is copied and "Paste-Special" onto a blank new sheet with only values and formulas.
let file = excel_reader.read("Book.xlsx").unwrap();

@agentjill
You are right.
lazy_read(path) is a bit quirky.
I have felt the need to improve the documentation.

Also, once the sheet is loaded that would mean things like table, protection etc are also loaded into memory props. I was meaning for that to be loaded lazily.

It is wonderful.
I agree with the lazy load subdivision.

[You can] use the parallel programming, Luke!
worksheets are almost independent
pub fn read_reader<R: io::Read + io::Seek>(
reader: R,
with_sheet_read: bool,
) -> Result<Spreadsheet, XlsxError> {
...
for (_, type_value, rel_target) in &workbook_rel { // can it be parallel?
...
}

@mjhmjhgkmj
Very nice idea.
The sections you mentioned can be processed in parallel.
(Perhaps there are other areas where parallel processing is possible.)


Dart Pad Isn't Showing My Github Profile

Hey @Menula-De-Silva, thanks for opening an issue!
DartPad dropped support for GitHub authentication to reduce the maintenance cost of the site and help focus on the core "playground" experience of DartPad.

Hmm ... Ok


wasmtime: 21.0.1 -> 22.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bytecodealliance/wasmtime/releases.
meta.description for wasmtime is: Standalone JIT-style runtime for WebAssembly, using Cranelift
meta.homepage for wasmtime is: https://wasmtime.dev/
meta.changelog for wasmtime is: https://github.com/bytecodealliance/wasmtime/blob/v22.0.0/RELEASES.md
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 22.0.0 with grep in /nix/store/q9hab7ipnybjk7i8n4n6820xa8i93jwg-wasmtime-22.0.0
found 22.0.0 in filename of file in /nix/store/q9hab7ipnybjk7i8n4n6820xa8i93jwg-wasmtime-22.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wasmtime

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q9hab7ipnybjk7i8n4n6820xa8i93jwg-wasmtime-22.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wasmtime https://github.com/r-ryantm/nixpkgs/archive/e47dcab3a433b26ce2c72d76dfb8fa696ff9d978.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e47dcab3a433b26ce2c72d76dfb8fa696ff9d978#wasmtime

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q9hab7ipnybjk7i8n4n6820xa8i93jwg-wasmtime-22.0.0
ls -la /nix/store/q9hab7ipnybjk7i8n4n6820xa8i93jwg-wasmtime-22.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

wasmtime
wasmtime.dev

Maintainer pings
cc @ereslibre @matthewbauer for testing.

Result of nixpkgs-review pr 321327 run on x86_64-linux 1

2 packages built:

wasmtime
wasmtime.dev

Result of nixpkgs-review pr 321327 run on x86_64-linux 1

2 packages built:

wasmtime
wasmtime.dev


Add a FORTRAN formatter

An amazing implementation of FORTRAN editing.
A FORTRAN formatter would be very helpful  enhancement (at least for the free format FORTRAN code file structure, FORTRAN 90 and up) .
Format document and format selected like in the c/c++ extension.

Formatting source code is a very opinionated thing and each one has his own code style. Also I don't have the time to implement a formatting algorithm. But PR are welcome 👍

Full formatting, like in many Visual Studio implementations, is indeed complex and in many cases a matter of personal preference. I actually ment only post indenting of a code that was originally written without indentation or a non consistant indentation.
Also syntax highlighting does not support some of he modern keywords and constructs like bind, value, reference, enum (and consequently enumerator).
Indentation while typing does not support type declaration, select case statement, and enum.
I fixed some of the syntax highlighting privately on my vc code installation and the auto indentation as well. however, I failed to indent the internal case whithin a select case statment more than the select case.
I never used github before (besided complaining ... and openning issues)
Should I open a pull request for those modifications? (I will have to learn how, but there is a first time for everything)

@yonadav I suggest you read this: https://guides.github.com/activities/forking/
It's pretty simple!

@yonadav would you like to open an issue for the auto indentation issues that you are having with the new Fortran keywords you mentioned about here?

@yonadav are you still willing to share your fixes?
I can guide you through the process of how to contribute to the project if you want to.

Adding this here just to keep this for future reference:
emacs has a F90 formatter that uses the following eviroment variables to format the file...

Associate indent
// Indentation applied to ASSOCIATE blocks

Continuation indent
// Indentation applied to continuation lines

Critical indent
// Indentation applied to BLOCK and CRITICAL blocks

Do indent
// Indentation applied to DO blocks

If indent
// Indentation applied to  IF, SELECT CASE, WHERE and FORALL blocks

Program indent
// Indentation applied to  PROGRAM, MODULE, SUBROUTINE, FUNCTION blocks

Type indent
// Indentation applied to  TYPE, ENUM, INTERFACE and BLOCK DATA blocks

In our case, the number of spaces in each indentation can be set based on VSCode editor.tabSize configuration for example.

Thanks for create this useful extension!
I agree with @yonadav . The only reason I am still using Emacs for Fortran is because it has a nice formatter. It would be nice if you could just add an option for us to use Emacs indentation directly by importing executable Emacs path. (Like atom-beautify)

@han190 This feature here is desirable for everyone, but we are short in developers right now :-1: . Your idea is simpler, probably easier to implement, it could be a nice first step :+1: . Thank you!

Guys, there is an alternative/crappy fix if you are really annoyed by the indentation.  Go ahead and copy the file from here:
https://github.com/Glavin001/atom-beautify/blob/master/src/beautifiers/fortran-beautifier/emacs-fortran-formating-script.lisp
Save it under any directory you like, for example, /Users/usrname/.emacs-batch-f90-indent.lisp. Then as introduced by the file, open a terminal from VS-code and type
emacs -batch -l ~/.emacs-batch-f90-indent.lisp -f f90-batch-indent-region *.f90
or you can alias the command with some shortcut and save it to bash file. I know it is crappy but at least I don't have to switch between VS-code and Emacs when editing Fortran files.

A decent solution that has worked for me in the past, especially with large projects, is fprettify https://github.com/pseewald/fprettify. Although it focuses mostly on formatting whitespaces.

Check out https://sourceforge.net/projects/findent/ . That is a very fast fortran indenting program, also converts from fixed format to free format and vice-versa and understands fortran 66 until fortran 2008.


Temperature module reporting negative numbers at high temps.

This issue seems to hard to reproduce, but seems to be caused from high temps. I think it's around >78C that my temp goes negative.
My temp module is only slightly modified, but here's the script:
[module/temperature]
type = internal/temperature
thermal-zone = 0
warn-temperature = 65

format = <label>
format-underline = ${colors.accent-color}
format-warn = <label-warn>
format-warn-underline = ${colors.red}

format-padding = 1
format-warn-padidng = 1

label = %temperature%
label-warn = %temperature%

ramp-0 = 
ramp-1 = 
ramp-2 = 
ramp-foreground = #55

Also I took a screenshot of it happening:
http://i.imgur.com/JGoI6mP.png

I had sometimes 92 °C here. There is no problem.
You could check this:
cat /sys/class/thermal/thermal_zone0/temp
What is the output?

You could use this command to check the values that the polybar temperature module reads:
$ cat /sys/class/thermal/thermal_zone*/temp | awk '{ printf "%.0f°C\n", $1/1000 }'

Waited till I went negative again and got this as an output:
zack@shippage:~$ cat /sys/class/thermal/thermal_zone*/temp | awk '{ printf "%.0f°C\n", $1/1000 }'
-50°C
41°C
83°C

This means the value is already a wrong at your system.
A workaround could be to use another sensor. What kind of sensor is your thermal_zone0?
Btw. There is a typo mistake at you config. It should be padding:
format-warn-padidng = 1

Thanks for spotting that, my config is still a work in progress. I'm not sure how to check what my sensor is. If it's a hardware problem, I'm running a Macbook Pro early 2016. If it's a software issue, then I'm running stock Ubuntu 16.10, and I haven't touched anything to do with the thermal zone that I know of.

Yes, at this point the problem is not at polybar. The value is already wrong.
This means we can't help you a lot here.
But you could try a newer kernel version. Maybe there is something broken in your version.


Collisions Issues when change scenes

Godot version:
3.1 beta 6
OS/device including version:
Windows 7
issue description:
in a platform game when i change between scenes there are issues regarding collisions between player and platform
Steps to reproduce:
using  "change_scene()" or PackedScene with "change_scene_to()" seems to trigger these issues.
it happens to me in Godot 3.1 since Beta 3
sorry for my english

Could you provide a project that reproduces those issues?

Seems like a duplicate of #24694 actually.
Please comment if you think it's not.

yes i think the problem is very similar

Seems like a duplicate of #24694 actually.
Please comment if you think it's not.

yes i think the issue is very similar to this


[wishlist] Helper script for recovering wrongly entered SSIDs

I think it would be nice to have a script that helps with wrongly entered SSIDs (or maybe also passwords). The idea is to sniff the WLAN for connection attempts and print them to the console. That way we could find out what a particular device is configured for.

Although I don't think this is a terrible idea, the latest commit of Tuya convert includes a 'thirdparty.bin' provided by @digiblur which now enables WiFi Manager by default. Successive failures to connect due to incorrect password or SSID will now re-spawn the ' sonoff-xxxx ' AP again! Just make sure you flash ####thirdparty.bin and not another version of Sonoff-Tasmota.
There is also talk that perhaps a WifiMan sonoff bin will be pre-compiled by Tasmota in the future!
[-=SrZ=-]

@SirRedZ Hmm, have the security implications of that change been thought through? This means an attacker can disconnect the WLAN router, spawn an own one with the same SSID and then take over all IoT devices in that network.

Your point is well understood - I guess users would have control to add web admin password to also protect against this. It is so common for people to lock themselves out, in some cases making the module garbage for many users without additional skills and resources. I would say this project is aimed at the greater masses, and as such this is the lesser of the evils. Since the Wifi manager option is reset upon a sonoff updated flash, and web admin password offers another layer of protection, my opinion is the risk is somewhat mitigated.
Also, both binary files are included in the project, so people have choices to be made!
Interestingly enough, this entire project is about DEFEATING PROTECTIONS so it's certainly an oxy-moron indeed! @schildbach
Have an awesome day!
[-=SrZ=-]

In a home automation scenario, hopefully the home owner has physical control of the router thus not allowing it to be powered off or disconnected while the rest of the smart switches in the home remain powered on.

@sirredz the wifi manager is not reset after a new bin is written. It's only reset if the user resets to defaults after the new bin is written.

My mistake - I was thinking that but didn't specify it. I often reset 5, so I kind of forgot to mention that step. Good call-out!
[-=SrZ=-]

Nice idea @schildbach, if you submit a PR we can see how it works. Otherwise I believe #277 should cover this. Thanks for sharing your ideas!

Just wanted to document the steps I took to recover from a wrong SSID (using Ubuntu 18.04, on an Intel Wifi):

sudo apt install aircrack-ng wireshark
sudo airmon-ng check kill
sudo airmon-ng start  (e.g. wlp58s0 or wlan0)
sudo wireshark
select your wifi device from the list
plug in the misconfigured device and immediately watch SSIDs, you should see your misconfigured SSID pretty soon


Forms and buttons

Thanks to some work that @Samsinite did, I was able to back fill some new shiny controls for us!

Once this has been merged and released we will need to run npm run deploy-documentation to update the documentation.


[BUG] Message vs. ScriptBlockText for Powershell rules

Describe the bug
We seem to have a mix of fields between Message and ScriptBlockText for the Powershell rules in ESCU.
If my own testing is correct, the Message field is only extracted when the Powershell Windows Event Logs are ingested in Classic Mode (renderXml=false), while ScriptBlockText is only when the XML version is (renderXml=true).
If I'm correct, this might lead some of these detections to fail depending on how the Powershell logs are ingested as a result.
As a reference, the following Powershell related Detections use Message (the others use ScriptBlockText):

Allow Inbound Traffic In Firewall Rule
Detect Copy of ShadowCopy with Script Block Logging
Domain Group Discovery with Adsisearcher
Elevated Group Discovery with PowerView
Powershell Windows Defender Exclusion Commands
Windows Get-AdComputer Unconstrained Delegation Discovery
Windows PowerView Constrained Delegation Discovery
Windows PowerView Unconstrained Delegation Discovery

Expected behavior
Do we want to standardize on ScriptBlockText? And possibly document that a requirement for these detections to work is to use the XML format for those Windows Event Logs? E.g.: renderXml = true?  Or support both versions?
And/or work with the Windows Add-on team to add an explicit extraction for ScriptBlockText to the TA?
App Version:

ESCU: latest

Additional context
Add any other context about the problem here.

Not sure where your list came from, as some of those have already been using ScriptBlockText but for the one that was still based on multi-line logs, we've got an MR internally to update this and should have it merged soon.


[CT-2832] [Spike] Can the hook for latest model version unsuffixed view/clone leverage our clone macro/materialization?

spike split out of https://github.com/dbt-labs/dbt-core/issues/7442
We have documented/recommended some code for an opt-in post-hook, that creates an extra view pointing to the "latest" object: https://docs.getdbt.com/docs/collaborate/govern/model-versions#configuring-database-location-with-alias
Definition of done:

Spike on whether we can clean up this code by leveraging the clone macro / materialization that we developed for v1.6

If we can get to cleaner code that's supported across DWHs, it's then just a UX question of whether this is enabled/disabled via yaml config (option 2) or post-hook (option 3)

@aranke That's great news! I think the next step here is actually moving forward with:

#7442

By (roughly):

executing that macro within the model run/build step
iff it's a versioned model
returning the appropriate information about the created/updated object to the cache

If that sounds right to you, I think we can close this spike and move forward with #7442 (schedule for the next sprint). Does that sound right to you?


Pipeline Event Plugin

Repository URL
https://github.com/johnniang/pipeline-event-plugin
New Repository Name
pipeline-event-plugin
Description
The Pipeline Event Plugin built for Jenkins is mainly to solve the interaction problem between the third-party system and Jenkins.
GitHub users to have commit permission
@LinuxSuRen
@JohnNiang
Jenkins project users to have release permission
surenpi
johnniang
Issue tracker
GitHub issues

/hosting re-check

/hosting re-check

/hosting host

I want to rename this plugin suddenly, so I'm going to close this issue for a while.


Automatic update of AWSSDK.Core to <IP_ADDRESS>

NuKeeper has generated a patch update of AWSSDK.Core to <IP_ADDRESS> from <IP_ADDRESS>
AWSSDK.Core <IP_ADDRESS> was published at 2021-01-30T02:27:39Z, 3 days ago
2 project updates:
Updated src/Generator/Generator.csproj to AWSSDK.Core <IP_ADDRESS> from <IP_ADDRESS>
Updated src/Core/Core.csproj to AWSSDK.Core <IP_ADDRESS> from <IP_ADDRESS>
AWSSDK.Core <IP_ADDRESS> on NuGet.org
This is an automated update. Merge only if it passes tests
NuKeeper: https://github.com/NuKeeperDotNet/NuKeeper

Not all lockfiles were updated.


Add gist:description

We have many places where we'd like to add a user description field on various instance data and there doesn't seem to be a good existing choice for this. It seems general enough that it could be a candidate to go into gist.

I usually use skos:definition for instance descriptions.  Most of the time there is no need for anything else.  Would that not work for the cases you have in mind?

I usually use skos:definition for instance descriptions.  Most of the time there is no need for anything else.  Would that not work for the cases you have in mind?

Definition and description are not equivalent. I can describe someone as medium height, brown hair, blue eyes, etc. but that is not a definition. The description is likely relevant only to instances, rather than classes and properties.And it's best thought of as a datatype property, I think: even though it's only text, it is data rather than metadata.
rdfs:comment is too vague, which is the reason we removed it from our standard set of annotations. I like the idea of adding gist:description.

Definition and description are not equivalent. I can describe someone as medium height, brown hair, blue eyes, etc. but that is not a definition. The description is likely relevant only to instances, rather than classes and properties.And it's best thought of as a datatype property, I think: even though it's only text, it is data rather than metadata.
rdfs:comment is too vague, which is the reason we removed it from our standard set of annotations. I like the idea of adding gist:description.

A description and a definition are not semantically the same thing. So skos:definition would work if you don't mind using terms for things other than what they were meant for. Which seems to go against the general premise of semantic modeling. OTOH, I know we don't recommend a proliferation of datatype properties. So I am interested in hearing what other people think about wrt if it makes sense to make the distinction, and if it belongs in gist.
It isn't that I "need a solution" as I know there are many other options including rdfs:comment or we can add it to our own ontology. Heck, I could even use gist:containedText, but that wasn't what that was meant for either.

A description and a definition are not semantically the same thing. So skos:definition would work if you don't mind using terms for things other than what they were meant for. Which seems to go against the general premise of semantic modeling. OTOH, I know we don't recommend a proliferation of datatype properties. So I am interested in hearing what other people think about wrt if it makes sense to make the distinction, and if it belongs in gist.
It isn't that I "need a solution" as I know there are many other options including rdfs:comment or we can add it to our own ontology. Heck, I could even use gist:containedText, but that wasn't what that was meant for either.

@Jamie-SA containedText was manufactured to go with a Text object, although the domain is not stated. Semantically it doesn't work anyway: we don't say the description "blue eyes, brown hair" is contained by the person being described.
I agree with not overloading terms.

@Jamie-SA containedText was manufactured to go with a Text object, although the domain is not stated. Semantically it doesn't work anyway: we don't say the description "blue eyes, brown hair" is contained by the person being described.
I agree with not overloading terms.

@rjyounes that was my point.

@rjyounes that was my point.

Definition is indeed different from description. skos:scopeNote can be used for descriptions. If we want something more specific than that, we could create a gist annotation property and have it be a subproperty of skos:scopeNote.  I don't yet see a good reason to use a datatype property.

Definition is indeed different from description. skos:scopeNote can be used for descriptions. If we want something more specific than that, we could create a gist annotation property and have it be a subproperty of skos:scopeNote.  I don't yet see a good reason to use a datatype property.

I think you are mixing domains. The definition of skos:scopeNote is "A note that helps to clarify the meaning and/or the use of a concept." The description of John as "medium height, blond hair, blue eyes" does not clarify the meaning or use of John, nor is John a concept.

I think you are mixing domains. The definition of skos:scopeNote is "A note that helps to clarify the meaning and/or the use of a concept." The description of John as "medium height, blond hair, blue eyes" does not clarify the meaning or use of John, nor is John a concept.

The description of John as "medium height, blond hair, blue eyes" does not clarify the meaning or use of John, nor is John a concept.

Objection sustained.

The description of John as "medium height, blond hair, blue eyes" does not clarify the meaning or use of John, nor is John a concept.

Objection sustained.

@rjyounes says:

[the description] is best thought of as a datatype property, I think: even though it's only text, it is data rather than metadata.

I am not compelled by that argument for making gist:description a datatype property.
A property for description is similar to skos:definition in that it provides important semantic information.  So it makes sense for it to be an annotation property, a sibling of skos:definition and thus a subproperty of skos:note. They might even be kissing cousins.

@rjyounes says:

[the description] is best thought of as a datatype property, I think: even though it's only text, it is data rather than metadata.

I am not compelled by that argument for making gist:description a datatype property.
A property for description is similar to skos:definition in that it provides important semantic information.  So it makes sense for it to be an annotation property, a sibling of skos:definition and thus a subproperty of skos:note. They might even be kissing cousins.

Compare the function and content of a datatype vs annotation property in the following example:
:_UnitedNations a gist:Organization ;
   gist:name "United Nations" ;
   gist:description "The United Nations is an intergovernmental organization that aims to maintain international peace and security, develop friendly relations among nations, achieve international cooperation, and be a centre for harmonizing the actions of nations." ;
   skos:note "Do we really want to define this in gist?" ;
.

IMO the description is data - in the same way that gist:name is - while the annotation is metadata.
Along these lines, I've been thinking about gist:name vs skos:prefLabel, and I've concluded that individuals that have real names in the real world should in general not have prefLabels, but rather names (though I don't rule out the possibility that labels would be appropriate in some contexts). Consider the lengthy discussion about how to format prefLabels in #227; you wouldn't have this discussion about the United Nations, because the name is an actual fact that has been assigned to the individual in the outside world, not something we assign. Instead of altLabel, one could define a hierarchy of name properties, such as abbreviation, acronym, legalName, genericName, givenName, familyName, etc. to provide other names like "UN," and so on. These tell you the semantics of the names and how they are used, as opposed to altLabel. I'm not proposing that all of these would be defined in gist itself - though abbreviation and acronym are universally useful, and legalName may be generally useful in an enterprise context.

Compare the function and content of a datatype vs annotation property in the following example:
:_UnitedNations a gist:Organization ;
   gist:name "United Nations" ;
   gist:description "The United Nations is an intergovernmental organization that aims to maintain international peace and security, develop friendly relations among nations, achieve international cooperation, and be a centre for harmonizing the actions of nations." ;
   skos:note "Do we really want to define this in gist?" ;
.

IMO the description is data - in the same way that gist:name is - while the annotation is metadata.
Along these lines, I've been thinking about gist:name vs skos:prefLabel, and I've concluded that individuals that have real names in the real world should in general not have prefLabels, but rather names (though I don't rule out the possibility that labels would be appropriate in some contexts). Consider the lengthy discussion about how to format prefLabels in #227; you wouldn't have this discussion about the United Nations, because the name is an actual fact that has been assigned to the individual in the outside world, not something we assign. Instead of altLabel, one could define a hierarchy of name properties, such as abbreviation, acronym, legalName, genericName, givenName, familyName, etc. to provide other names like "UN," and so on. These tell you the semantics of the names and how they are used, as opposed to altLabel. I'm not proposing that all of these would be defined in gist itself - though abbreviation and acronym are universally useful, and legalName may be generally useful in an enterprise context.

Along these lines, I've been thinking about gist:name vs skos:prefLabel

@rjyounes This is important and should be a separate issue.

Along these lines, I've been thinking about gist:name vs skos:prefLabel

@rjyounes This is important and should be a separate issue.

skos:note "Do we really want to define this in gist?"

This should be a skos:editorialNote. As you point out, it has nothing to do with the meaning of an IRI.

skos:editorialNote "A note for an editor, translator or maintainer of the vocabulary."

However all of the following have a LOT to do with the meaning of an IRI

skos:definition: "A statement or formal explanation of the meaning of a concept."
skos:scopeNote:  "A note that helps to clarify the meaning and/or the use of a concept."
gist:description:  Further elaborates the meaning of a URI beyond what may be in skos:definition

Having gist:description as an annotation is consistent with common usage. Textual information about the meaning of IRIs typically goes in annotations. That is what rdfs:comment is for.

skos:note "Do we really want to define this in gist?"

This should be a skos:editorialNote. As you point out, it has nothing to do with the meaning of an IRI.

skos:editorialNote "A note for an editor, translator or maintainer of the vocabulary."

However all of the following have a LOT to do with the meaning of an IRI

skos:definition: "A statement or formal explanation of the meaning of a concept."
skos:scopeNote:  "A note that helps to clarify the meaning and/or the use of a concept."
gist:description:  Further elaborates the meaning of a URI beyond what may be in skos:definition

Having gist:description as an annotation is consistent with common usage. Textual information about the meaning of IRIs typically goes in annotations. That is what rdfs:comment is for.

I'm not suggesting that the skos properties be datatype properties. I do not see how the description of a person, organization, or other RWO can be considered meaning or use. It's exactly the same argument I made above for why skos:definition shouldn't be used instead of a description property. I maintain that the skos predicates are metadata about concepts - which is what ontology terms are - while a description is suitable for instances.

I'm not suggesting that the skos properties be datatype properties. I do not see how the description of a person, organization, or other RWO can be considered meaning or use. It's exactly the same argument I made above for why skos:definition shouldn't be used instead of a description property. I maintain that the skos predicates are metadata about concepts - which is what ontology terms are - while a description is suitable for instances.

Moved the name discussion to new issue #427.

Moved the name discussion to new issue #427.

How does your proposed definition of gist:definition distinguish it from skos:scopeNote?

Good question. Strictly speaking, it does not. So we could decide to just use scopeNote instead of a new property.   I don't see any proposed definitions for gist:description?  What do you propose? What distinguishes it from scopeNote?

How does your proposed definition of gist:definition distinguish it from skos:scopeNote?

Good question. Strictly speaking, it does not. So we could decide to just use scopeNote instead of a new property.   I don't see any proposed definitions for gist:description?  What do you propose? What distinguishes it from scopeNote?

I do not see how the description of a person or other RWO can be considered an indication of its "meaning and/or use".

What does foo:23456HJYf mean? You have no idea. But suppose I say:
foo:23456HJYf a gist:_Organization ;
    skos:prefLabel "Office of Compliance"^^xsd:string
  .

You now have an idea of what foo:23456HJYf is intended to mean. But you might not know anything about that office.  So it still might not mean much of anything to you.  This extra triple would help you:
foo:23456HJYf
    gist:description l "A US federal organization that advances workplace rights, safety, health, and accessibility in the Legislative Branch."^^xsd:string
  .

Now you have a fairly good grasp of what foo:23456HJYf means.  We could use scopeNote  to disambiguate it from other organizations with the same name.

I do not see how the description of a person or other RWO can be considered an indication of its "meaning and/or use".

What does foo:23456HJYf mean? You have no idea. But suppose I say:
foo:23456HJYf a gist:_Organization ;
    skos:prefLabel "Office of Compliance"^^xsd:string
  .

You now have an idea of what foo:23456HJYf is intended to mean. But you might not know anything about that office.  So it still might not mean much of anything to you.  This extra triple would help you:
foo:23456HJYf
    gist:description l "A US federal organization that advances workplace rights, safety, health, and accessibility in the Legislative Branch."^^xsd:string
  .

Now you have a fairly good grasp of what foo:23456HJYf means.  We could use scopeNote  to disambiguate it from other organizations with the same name.

PUNCH LINE: Sometimes the distinction between definition and description is not so clear cut. Sometimes it makes sense to use skos:definition for an instance, but due to likely confusion, I would recommend against it.
DETAILS: On the distinction between 'description' and 'definition'.  Every definition is a description, and one should never suppose that a description is a definition.  A lot of the time, there is no point in creating a skos:definition for instances which correspond to proper nouns in English.  But what would you call an entry in Miriam-Webster dictionary for Ithaca?

city in south central New York on Cayuga Lake population 30,014

If you were the author of the dictionary, I dare say you'd call it a definition.  It is intended to be a definitive characterization of what is meant by "Ithaca NY" -- so I would not find it jarring if someone used that phrase in a skos:definition. I might not do it that way, but it is not obviously wrong, semantically nor from a common sense perspective.

PUNCH LINE: Sometimes the distinction between definition and description is not so clear cut. Sometimes it makes sense to use skos:definition for an instance, but due to likely confusion, I would recommend against it.
DETAILS: On the distinction between 'description' and 'definition'.  Every definition is a description, and one should never suppose that a description is a definition.  A lot of the time, there is no point in creating a skos:definition for instances which correspond to proper nouns in English.  But what would you call an entry in Miriam-Webster dictionary for Ithaca?

city in south central New York on Cayuga Lake population 30,014

If you were the author of the dictionary, I dare say you'd call it a definition.  It is intended to be a definitive characterization of what is meant by "Ithaca NY" -- so I would not find it jarring if someone used that phrase in a skos:definition. I might not do it that way, but it is not obviously wrong, semantically nor from a common sense perspective.

Whatever Merriam-Webster thinks they're doing, I'm not buying it. Consider the MW entry for "George Washington":
1732–1799 American general; 1st president of the U.S. (1789–97)
I cannot be convinced that that's a definition. Does it mean that if he hadn't been a general or the first US president or lived one year longer he wouldn't have been the same person?
The Ithaca case works too: if there are now 35K residents of Ithaca, is it a different city? By comparison, the definition of "thousand" really is, as MW states, "a number equal to 10 times 100." Any number that doesn't satisfy the definition is not a thousand.
Further, there can be more than one city that matches the description "city in south central New York on Cayuga Lake population 30,014," which again suggests it's not a definition.
A definition is strict, in the sense that the thing so defined cannot change and remain the same thing. A description is malleable, in the sense that if the thing departs from its description it can still be the same thing, though the description needs to be updated.
I refer you to M-W's definition of "definition" (emphasis mine):
(1a) a statement of the _meaning_ of a word or word group or a sign or symbol
(1b) a statement expressing the _essential nature_ of something

Whatever Merriam-Webster thinks they're doing, I'm not buying it. Consider the MW entry for "George Washington":
1732–1799 American general; 1st president of the U.S. (1789–97)
I cannot be convinced that that's a definition. Does it mean that if he hadn't been a general or the first US president or lived one year longer he wouldn't have been the same person?
The Ithaca case works too: if there are now 35K residents of Ithaca, is it a different city? By comparison, the definition of "thousand" really is, as MW states, "a number equal to 10 times 100." Any number that doesn't satisfy the definition is not a thousand.
Further, there can be more than one city that matches the description "city in south central New York on Cayuga Lake population 30,014," which again suggests it's not a definition.
A definition is strict, in the sense that the thing so defined cannot change and remain the same thing. A description is malleable, in the sense that if the thing departs from its description it can still be the same thing, though the description needs to be updated.
I refer you to M-W's definition of "definition" (emphasis mine):
(1a) a statement of the _meaning_ of a word or word group or a sign or symbol
(1b) a statement expressing the _essential nature_ of something

Given a strict definition of the word 'definition' then I agree with your latest remarks, and none of what you say seems to contradict the PUNCH LINE of what I said above which is about common broader usage of the term, 'definition' as well as common use of skos:definition.
So I don't see much daylight between a decision you would make about this or one that I would make in an ontology creation exercise.   We should strive to make our skos:definitions in gist more strict.  Most of the current entries do not even come close to your exacting standards.

Given a strict definition of the word 'definition' then I agree with your latest remarks, and none of what you say seems to contradict the PUNCH LINE of what I said above which is about common broader usage of the term, 'definition' as well as common use of skos:definition.
So I don't see much daylight between a decision you would make about this or one that I would make in an ontology creation exercise.   We should strive to make our skos:definitions in gist more strict.  Most of the current entries do not even come close to your exacting standards.

Comment from Michael at triage meeting: everything needs a skos:prefLabel since UIs and other applications look for it.
This seems right.

Comment from Michael at triage meeting: everything needs a skos:prefLabel since UIs and other applications look for it.
This seems right.

I missed the meeting today so I don't have the context. I am trying to figure out how MU's comment applies to this issue?

I missed the meeting today so I don't have the context. I am trying to figure out how MU's comment applies to this issue?

DECISION: gist:description to be defined as a datatype property.


Lockfile issue

There are some problems with lockfile, easy to solve thou.
libs/cherrypy/lib/sessions.py
is using self.lock = lockfile.LockFile(path)
same goes for zerobin/paste.py
lock = lockfile.LockFile(counter_file)
In my case, running dir on lockfile returns this:
['AlreadyLocked', 'Error', 'FileLock', 'LinkFileLock', 'LockBase', 'LockError', 'LockFailed', 'LockTimeout', 'MkdirFileLock', 'NotLocked', 'NotMyLock', 'SQLiteFileLock', 'UnlockError', '__all__', '__builtins__', '__doc__', '__file__', '__name__', '__package__', 'division', 'errno', 'os', 'socket', 'sys', 'thread', 'threading', 'time', 'urllib']

push

+1

Btw, the latest lockfile release states:

This package is deprecated. It is highly preferred that instead of using this code base that instead fasteners or oslo.concurrency is used instead.

Why did you reopen it ?

@ashok-arora mistake I guess :-)


PigeonHole Sort| SortingAlgorithms | C++

Title - PigeonHole Sort in C++
what will change -
Type of Issue -

[x] Adding New Code

Programming Language

[x] C++

Ask for issue assignment before making Pull Request.

Add your file in the proper folder

Clean Code and Documentation for better readability

Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding.

I would like to work on this issue. Kindly assign me.

[x] Issue assigned to @tusharsbauskar

I'll take this up since no-one has volunteered.

Can I be assigned this issue?


How to run eval_vfid.py code?

Hi, I'm eager to evaluate FID, but I'm not sure how to run the eval_vfid.py.
Because there is no flintstones_data which should be imported.
Also I tried using eval_vfid.py in StoryViz, but there is another issue: no file named "img-%s-%s.png' % (item, k)". In my result folder, there is no file like "img-%s-%s.png' % (item, k)".
Would you tell me how to run eval_vfid.py file?

I modifed flintstones_data → vlcgan.pororo_data. Because there is no flintstones_data in github.
I made fake images for test datset with command: python train_vlcgan.py --cfg ./cfg/pororo_s1_vlc_eval.yml --data_dir ./data/ --dataset pororo --checkpoint_file ./output/pororo_martt_bs12_stageI_r1.0/Model/netG_epoch_150.pth
I run the numpy_to_img to make images from the npy file. Since there is no numpy_to_img function in VLCStoryGAN, so I used function from StoryViz.
I used the concat output. Because the data I’d like to evaluate is story data.
Finally, I run the evaluation code: python eval_vfid.py --img_ref_dir ./data/ --img_gen_dir ./output/pororo_martt_bs12_stageI_r1.0/Eval/images4eval/ --mode test


Cannot read properties of undefined (reading 'clickfalse')

I'm having a problem with an app I'm building and have isolated it down to the following code snippet.
Basically, the steps to recreate are:

Create a new project
Init npm
Install linkedom and preact
Create an index.js file with the code below
Run node index.js
Receive the error Cannot read properties of undefined (reading 'clickfalse')

I can confirm the code works fine in Chrome. i.e. running .click() on the element.
What is the code?
import { parseHTML } from 'linkedom';
import { h, render } from 'preact';

function handleClick () {
  console.log('i gotted clicked')
}
const app = h('button', { onClick: handleClick }, 'Hello World!');

const {
  window, document
} = parseHTML(`
  <!doctype html>
  <html lang="en">
    <head>
      <title>Hello SSR</title>
    </head>
    <body>
    </body>
  </html>
`);

globalThis.document = document;
globalThis.window = window;

render(app, document.body);

const button = document.body.querySelector('button')
console.log(button.click())

What is the error?
TypeError: Cannot read properties of undefined (reading 'clickfalse')
    at GlobalEvent.I (file:///home/mark/Synced/Projects/preact/node_modules/preact/dist/preact.mjs:1:4267)
    at GlobalEvent.dispatch (file:///home/mark/Synced/Projects/preact/node_modules/linkedom/esm/interface/event-target.js:7:14)
    at GlobalEvent.invokeListeners (file:///home/mark/Synced/Projects/preact/node_modules/linkedom/esm/interface/event-target.js:28:20)
    at Array.some (<anonymous>)
    at HTMLButtonElement.dispatchEvent (file:///home/mark/Synced/Projects/preact/node_modules/linkedom/esm/interface/event-target.js:80:17)
    at HTMLButtonElement.click (file:///home/mark/Synced/Projects/preact/node_modules/linkedom/esm/html/element.js:58:18)
    at file:///home/mark/Synced/Projects/preact/index.js:28:20
    at ModuleJob.run (node:internal/modules/esm/module_job:185:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:281:24)

I am not sure what you are trying to do but LinkeDOM is not a replacement for a browser ... it's more about SSR. Clicking is not really about SSR though ... if you find a solution happy to read the MR but I won't work on this for the time being.

I'm using it as a replacement for JSDOM for testing my preact user interface.
Could you point me in the direction of where to look at solving the above message? Is there a line you think that's causing it to throw?
Appreciate it's not a priority and thanks for all the work you've done on the project anyway.

this project goal is also not to replace JSDOM ... for browser-like things, JSDOM is the way to go.
If it's tests you are after, you are better off with JSDOM or real browsers (headless or not).
That being said, I have no idea, neither time, to check that error, sorry, and not a single file points at this project, it's all preact errors.

Thanks @WebReflection for the help anyway. I've submitted a PR that fixes the issue I have, although if it breaks other things then I get you don't want to spend any time on it.

@markwylde I've fixed it slightly differently, improved readability for the future, and added a little test. This should be fine now, thanks for investigating 👋


Adding Licence.txt and Readme pointer

Putting the same license + readme pointer that we use for our other repos (e.g. https://github.com/Azure/azure-webjobs-sdk)

looks good. :shipit:


Port lotus eth changes

Summary of changes

Changes introduced in this pull request:

ported some of the changes from Lotus to Forest that seemed relevant for NV18 or performance.
moved is_valid_for_sending to a different crate to be used in the message pool. I am not 100% sure it's where it should belong, but at least I didn't get circular dependencies issues.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Nice. Could you link the corresponding PR/commit in Lotus that you have used?

Nice. Could you link the corresponding PR/commit in Lotus that you have used?

Most of them come from this giga PR https://github.com/filecoin-project/lotus/commit/cdf3812e4081d35692b5ab81c573ab82d0df69cf
There is also this that caught my attention https://github.com/filecoin-project/lotus/commit/a9a65e05d8564d0b5bfe35416f50d0ea7b5fad51

What about supporting Ethereum API RPC endpoints? Do we want to support this in the near future?

What about support of equivalent resolve_to_deterministic_address/resolve_to_deterministic_address_at_finality functions?
Do you think it's not needed right now?

What about supporting Ethereum API RPC endpoints? Do we want to support this in the near future?

No clue how high supporting Ethereum is on our priorities list. This PR certainly is not intended to do so - only do some basic validations. @lemmih ?

What about support of equivalent resolve_to_deterministic_address/resolve_to_deterministic_address_at_finality functions?
Do you think it's not needed right now?

I only grabbed a few changes I encountered and tried to apply them when investigating stateroot mismatches, so they don't sit in my local stash. There are certainly more to port from this 15k LoC PR; this would require a more extended investigation.


Kptfile should be formatted based on openapi schema, not lexicographically

Kptfile should be formatted based on openapi schema, and not lexicographically. This will give us better control of formatting and make sure we can add new fields easier.

relevant to #1381

We have done significant work to preserve ordering/formatting of resources during fn eval|render, so not sure if this is still valid. I will close this issue for now and let's reopen it in context of new requirements related to formatting (if any)


Prettier commit messages

Hey,
can you pls make better commit messages, that contains more informations about a change?
I don't like this:

Could you please pay me for my work ? thanks

Diegos code is well documented. Therefore it's additional work.
It's something else if somebody contributes to another repository.


psh: allow sysexec to spawn programs with default map

Description

A change to both sysexec (psh) command and proc_syspageSpawnName() which allows to run syspage programs with the default memory map (dmap) set in plo using the app command.
JIRA: RTOS-74

Motivation and Context

It is a pain to keep typing the default map to sysexec  command for an application when it is given in the app command, so this needs be changed.
Types of changes

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

How Has This Been Tested?

[ ] Already covered by automatic testing.
[ ] New test added: (add PR link here).
[x] Tested by hand on: (imxrt1064).

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing linter checks and tests passed.
[ ] My changes generate no new compilation warnings for any of the targets.

Special treatment

[x] This PR needs additional PRs to work (list the PRs, preferably in merge-order).
https://github.com/phoenix-rtos/phoenix-rtos-kernel/pull/222
https://github.com/phoenix-rtos/phoenix-rtos-doc/pull/12
[x] I will merge this PR by myself when appropriate.

@niewim19 I'd like you to check if my changes work with whitelists, additionally please take a look at documentation update.
And also @jsarzy as the changes made by me with this commit may affect the tests execution.

About whitelist compatibility:
sysexec whitelist utility is only a stringwise comparison and it does not check the entered command for any logical coherence. If the old command call (with map specified) is held in place then projects that use whitelist will not even need change (however it will be nice to shorten necessary commands)
Taking examples from corresponding doc PR:
Allowing: sysexec -m dtcm progname arg1 arg2 with various args will need a whitelist entry as follows:
sysexec -m dtcm programname *
Allowing: sysexec progname arg1 arg2 with varoius args will need a whitelist entry as follows:
sysexec programname *
As -m parameter must be after sysexec and before programname then whitelist entries mentioned above are mutually exclusive (one does not allow other and vice versa). So it is good.
Looks good to me from whitelist utility standpoint.

The changes breaks the test runner but fix is one-liner - I will test it today.


Modifiers?

It would be awesome if you were able to manually define some modifiers, that, as it says, modifies the data before outputting.
Something like
{{ users|implode:',' }}

Would make something like jens1o, test, mickey when you pass an array with
[
    'jens1o',
    'test',
    'mickey'
]

Regards!
Jens

Are you talking about custom modifiers or predefined?

Both actually, so it is flexible. Otherwise, if you're open to add new modifiers in the future, that could be an option, too.

I think it can complicate rendy a lot, anyways this can be achived with some module which process all modifiers and then calls rendy. Do you know any modules which can do such things?

No, unfortunately not. But I'd need such an module, too.

Closed due to a long time of inactivity 🏝

Still a feature request I'd look forward to. :/

@jens1o what is your use case?

I don't understand what you're saying. The readme says that it is compatible with handlebars, and now you're passing me to use the original one instead?

Could you please show me the place, where handlebars used with modifiers in the way you use it?

Just landed support of modifiers in v4.1.0🎉. It was hard but I did my best to preserve speed and simplicity of Rendy.
Is it works for you?


Works only for single word

Hi,
Is this model only works for single handwritten word?
When the image has a collection of multiple words (a sentence) then this model gives poor/no result. But when the image has only one word like (Cat), this model works perfectly. Is my observation is correct or am I missing something here?
Thanks.

Hi,
yes, that's correct. The reason is not the number of words, but the size of the input image.
The input image is downsized to 128x32px, so if it contains a long sentence you won't be able to read the text on it anymore.
However, groups of short words should work fine, e.g. "I go home".
For more information see section 2 of this article: https://towardsdatascience.com/27648fb18519

If my image size is fixed to 128x32 for each input, I guess then multiple
words will be read properly.
Will this approach work?
On Wed, 19 Sep 2018, 15:15 Harald Scheidl<EMAIL_ADDRESS>wrote:

Hi,
yes, that's correct. The reason is not the number of words, but the size
of the input image.
The input image is downsized to 128x32px, so if it contains a long
sentence you won't be able to read the text on it anymore.
However, groups of short words should work fine, e.g. "I go home".
For more information see section 2 of this article:
https://towardsdatascience.com/27648fb18519
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/githubharald/SimpleHTR/issues/9#issuecomment-422732001,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXV_7k6qcts36T4vixRDiSs0vQRHtmdgks5uchIogaJpZM4WvvTj
.

There is no need to resize your input to 128x32, this is done automatically (also taking care that no distortion happens). You just have to take care that in your image, when downsized, the text is still large enough to be recognized.
I recommend either approach 2.1 or 2.2 of the linked article.

Thank you so much for the guidance
On Wed, 19 Sep 2018, 15:38 Harald Scheidl<EMAIL_ADDRESS>wrote:

There is no need to resize your input to 128x32, this is done
automatically (also taking care that no distortion happens). You just have
to take care that in your image, when downsized, the text is still large
enough to be recognized.
I recommend either approach 2.1 or 2.2 of the linked article.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/githubharald/SimpleHTR/issues/9#issuecomment-422740093,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXV_7mhdqmfPSV09Mn93dC9bj3hrBfvkks5uchetgaJpZM4WvvTj
.

You are right, using word segmentation I am getting correct results.

Left: downsize it and feed complete image to model.
Right: apply word-segmentation (only one word shown). Feed each word
individually to the model.

As you can see, the images of the segmented words contain much bigger
text, which can easily be recognized by the model.
[image: downsize_imgs]
https://user-images.githubusercontent.com/15148095/45747427-1dc3d880-bc06-11e8-857b-905ade59a9f9.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/githubharald/SimpleHTR/issues/9#issuecomment-422744697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXV_7td5E4bT6jB1v6vaZwrvnUV5AIugks5uchrdgaJpZM4WvvTj
.

Is the writing style for you alhpnum images the same as for your "normal" text?
Just to be sure that the bad results are not just because the writing looks entirely different.
If it's not the writing style: maybe the model learned some language properties, such that certain character combinations are more likely than others, e.g. "na" is more likely than "nx" in the IAM dataset which the model was trained on. But this is just an assumption, I didn't do any experiments to check if this is really the case.

How can I train your network for some other language like Hindi??


Obsolete property specified in demo_analysis_Spectra.m?

In demo_analysis_Spectra.m

H= grid_plot(spec, mnt, opt_grid_spec,'XUnit', spec.xUnit, 'YUnit', spec.yUnit);
the spcification of units should be obsolete (default of grid_plot)? Please check and remove if that's true.

CLAIM

it was obsolete, verified, will commit the fix soon.


Waves tx json serialization

Description
Added Waves transfer transaction json serialization
Testing instructions
unit test
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[X] Prefix PR title with [WIP] if necessary.
[X] Add tests to cover changes as needed.
[X] Update documentation as needed.

Can you add json class for gson to android library?

can you link an example of how it should be?


ClamWin.ClamWin version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual copying of Clamwin tags needed.


Implement hotreloading for macOS and Windows and other bugfixes

Implements hot reloading for macOS and windows
Closes #45
Closes #73

Thank you for the PR! Unfortunately I do not accept feature implementations as per CONTRIBUTING.md sorry.

I will extract the bug fixes and typo corrections into a new PR without the hotreloading part

Why did you deny this PR but allowed #81 to be merged, which is clearly also a feature implementation?


double scrollbar and weird scrolling behaviour

i'm not sure what i've done but there are now 2 vertical scrollbars showing (in Edge) and really weird scrolling issues happening too where the content is disappearing and there's almost infinite scroll (in Chrome/Brave)
i'm not certain when this started but i feel like it was right around when i added a TailwindUI component to the Footer.astro component

Interestingly, Firefox (on Windows, at least) is fine. Let’s see what the Chrome issue is.


[DSC] SampleConfigurations enhancements

Provide a description of requested docs changes

Add repo link in the header comment:

dotnet/aspnetcore/configuration.dsc.yaml

Resource Microsoft.VisualStudio.DSC/VSComponents requires repo to be cloned

Update winget package:

PowerShell/PowerShell/configuration.dsc.yaml

Resource Microsoft.WinGet.DSC/WinGetPackage is referencing a package id that was removed from winget-pkgs repo.

@AmelBawa-msft regarding the ASP.NET Core configuration: do you mean this repo has to be cloned? If so, why? For the ${WinGetConfigRoot}\..\.vsconfig?

I believe for this YAML we need to add a header comment referencing the ASP.Net Core repo. Correct, it's just a hint for the user to clone the ASP.Net Core repo before running the DSC configuration YAML (after placing it in aspnetcore/.configurations/configuration.dsc.yaml). The ${WinGetConfigRoot} will be replaced at runtime by the config file absolute path.
CC: @ryfu-msft

Okay, thanks for the clarification! I've updated the PR 😃.


Cleanup of the NUOPC wrapper

Description

This cleans up much of the error handling within the MAPL_NUOPCWrapperMod.F90 by introducing some new error handling macros for NUOPC. The formatting of the file has been updated, and some extraneous code has been removed. Finally, the some minor bugs introduced in newer versions of MAPL that occur during finalization have been resolved.
Related Issue

In addition to cleaning up the NUOPC wrapper this also fixes #503.
Motivation and Context

How Has This Been Tested?

Types of changes

[x] 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)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[ ] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

@bena-nasa   Can you review this PR?     (Some of the PR's are getting stale and I want to clear them out.)


Update to node 10 in .travis.yml

I have upgraded to node 10 in my system recently and I cannot get onchange to run without changing versions.  Please consider this pull request to fix the issue.  Thank you.

I only submitted what the greenkeeper bot suggested. Feel free to disregard
if there is more. It was late at night for me and I didn't go through your
code any deeper than that.
Jim Strother, Web Developer
On Fri, Jun 29, 2018, 23:25 Blake Embrey<EMAIL_ADDRESS>wrote:

Why would changing Travis fix the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Qard/onchange/pull/64#issuecomment-401516231, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APROiZMgkv6uQJIhlCQ8C4v9seSRFUAsks5uBv3IgaJpZM4U9z5-
.

Travis CI is a continuous integration environment. All it does is run tests. This doesn't change any code, so if there's an issue with node.js 10 it won't be fixed by running tests on it (which appear to be passing).


Category

Added User-defined Expense Categories

Expense Categories are now required to be defined by the user before being able to be used with an expense

Codecov Report

Merging #108 (9ea0306) into master (3b23000) will increase coverage by 0.82%.
The diff coverage is 68.25%.

@@             Coverage Diff              @@
##             master     #108      +/-   ##
============================================
+ Coverage     60.36%   61.18%   +0.82%
- Complexity      434      475      +41
============================================
  Files            87       94       +7
  Lines          1602     1721     +119
  Branches        171      189      +18
============================================
+ Hits            967     1053      +86
- Misses          592      615      +23
- Partials         43       53      +10

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

.../java/seedu/address/logic/commands/AddCommand.java
85.71% <0.00%> (-14.29%)
:arrow_down:

...ava/seedu/address/logic/commands/ClearCommand.java
100.00% <ø> (ø)

...java/seedu/address/logic/commands/EditCommand.java
93.75% <0.00%> (-3.03%)
:arrow_down:

...java/seedu/address/logic/commands/ExitCommand.java
100.00% <ø> (ø)

...java/seedu/address/logic/commands/HelpCommand.java
15.62% <0.00%> (-1.05%)
:arrow_down:

...java/seedu/address/logic/commands/ListCommand.java
25.00% <ø> (ø)

...eedu/address/logic/parser/ExpenseExpertParser.java
69.56% <0.00%> (-6.63%)
:arrow_down:

.../java/seedu/address/model/expense/Description.java
80.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
69.33% <50.00%> (-2.31%)
:arrow_down:

... and 11 more

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 3b23000...9ea0306. Read the comment docs.


Use local file name instead of host name

local file name can be used instead of host name:

Just to display file name in the settings window
To store settings on per file basis
file path can be used as a host name - all files in the same directory can have the same settings

is done in a different way


not enough shared memory increasing track_activity_query_size to 64K

I have tried to increase the max query size to cope with long, DWH-style queries:
track_activity_query_size = 65536
but I get, on cluster restart:
waiting for server to start....:  not enough shared memory for data structure "Ash Entry Query Buffer" (65536000 bytes requested)
on two different machines that should have plenty of memory available; e.g. one is a Linux Red Hat system with 32G memory, 20G of which is free.
I'm not familiar at all with PG development, but could it be because in ash_shmem_startup() there are 3 shared memory requests sized after pgstat_track_activity_query_size ("Ash Entry Query Buffer", "Ash Entry Top Level Query Buffer", "Proc Query Buffer"), and only 2 corresponding in ash_entry_memsize() - probably missing "Proc Query Buffer"?
Postgres 13.2 with latest pg_sentinel v1.0.0.

Thanks for reaching out.
The "Proc Query Buffer" part is done in proc_entry_memsize() which is in get_parsedinfo.c.
Will have a look.

Solved in commit 7fe711f

Many thanks!


DaoMaster.DevOpenHelper class def not found build for android tablet only

Hi, I got an issue where DaoMaster.DevOpenHelper not found : classnotfounddef. i have search entire git test with the pro guard and i test with update the gradle and etc. i still got crashing issue on that part when i build into my tablet but it is ok for my phone. any idea how to solve it? Please response to me and  i had tried all of possible solution that i found on online and on this git. thank you

This is the EventBus project. You maybe are looking for the greenDAO project?
-ut


Refactor Code

Clear code and eliminate repeat

Thanks for the suggestion! The code repetition isn't pretty, but it's better behaved for purposes of documentation that a define_method would be.


On some android devices front camera is too dark to scan

Expected Behaviour
We are wanting to scan QR codes using the front camera of an android tablet & have been conducting device testing using our cordova tablet app which was previously deployed on iPads, using the phonegap-plugin-barcodescanner plugin.
Actual Behaviour
On some android devices when the scanner opens the picture is too dark to scan QR codes, whereas on other android devices it is possible to scan the QR codes successfully in low light conditions
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 7.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Kodak Tablet 7
Cordova CLI version and cordova platform version
cordova --6.1.1

Plugin version
6.0.8
Sample Code that illustrates the problem
Initialising with front camera active

@GilbertLiddell have you considered add the showTorchButton: true option so the user can turn on the flash if things are too dark?

@macdonst he is talking about front camera, that one usually doesn't have flash.
I don't think we can do something to improve this issue, some devices have better cameras and can scan on worse conditions, and probably screen brightness might also be affecting the recognition

@jcesarmobile ooof, oh yeah, speed reading too many issues today. There is nothing we can do about this issue. That device has a 2MP front camera which is not very good.


search bar padding improvements

before:

after :

I'm not sure if this is the right way, but it works

@SunsetTechuila ❤