Indicate the required version of the package/database (it requires >= 2.0)

The format of the XML file changed enough for xdg to release a 2.0 in june of 2020.
OSs which may have a database that has not updated since then will likely install a 1.x release (say, 1.2 in Ubuntu trusty), which will fail with a hard-to-decode error
SyntaxError: (eval):1: unterminated string meets end of file
gems/mimemagic-0.3.7/lib/mimemagic/tables.rb:29:in `eval'
gems/mimemagic-0.3.7/lib/mimemagic/tables.rb:29:in `block (2 levels) in get_matches'
gems/mimemagic-0.3.7/lib/mimemagic/tables.rb:29:in `gsub!'
gems/mimemagic-0.3.7/lib/mimemagic/tables.rb:29:in `block in get_matches'

Installing the dpkg directly from the source (the download link in the README) does resolve this. But, it was not obvious that this was required.
Perhaps, this restriction needs added to the README and/or other documentation. It would also be great if the parser detected this early when possible.

:+1: Thanks, I was going to dig into what was going on with the version in Trusty this evening, this will make that much easier. I'll do something about the error message instead.

@jellybob please stop deleting versions in rubygems.org, please. I'm having problems with projects breaking unnecessarily...

We have stopped yanking versions now that none of them come with legal issues. 3.0.7 onwards are stable, and will remain in place. Also, please stop spamming unrelated issues.

@jellybob you should be aware that v2 only appears in Ubuntu 20.04 and Debian Unstable (Sid) - asking people to download a .deb and extract a file isn't really going to work for servers that have to autoscale.

@jellybob you should be aware that v2 only appears in Ubuntu 20.04 and Debian Unstable (Sid) - asking people to download a .deb and extract a file isn't really going to work for servers that have to autoscale.

I was able to install the dpkg directly on trusty after downloading the deb with wget (using dpkg -i). It's not ideal but works until we can bake it into our base image. This is also doable with a tool like chef using a remote_file and dpkg_package pair.

Also going to break on anything less than a Heroku-20 stack by the looks of it

Also going to break on anything less than a Heroku-20 stack by the looks of it

From my understanding, Heroku-20 only has shared-mime-info 1.15-1 installed as per this article, so even on the latest stack, one would probably have to use https://github.com/heroku/heroku-buildpack-apt to specifically install v2.

@kwong-yw is correct. That article accurately lists current versions. A co-worker @dzuelke pointed out that 20.04 is the current Ubuntu LTS, and the next one will not land until 2022. The mimemagic Gem will likely need to support both the v1 and v2 XML formats if it wants to use this package.

Even Focal, the current Ubuntu LTS (20.04) has v1.1.5: https://packages.ubuntu.com/focal/shared-mime-info
The next Ubuntu LTS won't land until April 2022, and there are plenty (read: millions, billions, who knows these days with the cloud and all) servers around with v1.x shared-mime-info, and for years to come - the report in #106 is from someone still running 14.04, which has been EOL for two years!
So it looks like it'll be unavoidable for the Gem to support both v1 and v2 XML formats.
I looked at the failing line:
value.gsub!(/\\(x[\dA-Fa-f]{1,2}|0\d{1,3}|\d{1,3}|.)/) { eval("\"\\#{$1}\"") }

So in some element in the v2 format, that regex doesn't match, leading the eval to fail.
Aside from the obvious question of whether evaling parts of a file from the filesystem is a good idea ;), this doesn't seem to be an unsolvable issue. I did compare the formats for a bit but couldn't straight away identify what string in the v2 file caused the failure; maybe someone else who already has a reproduce sample can provide that.

Agree. The gem was able to ignore the version difference before the change, because it could always bundle the appropriate version. Now, it will need to support multiple versions. At this point I haven't looked back in history to see how the XML handler has evolved, but perhaps there is existing code in an older revision that can help here.

Alright, found the issue.
IT IS NOT A 2.0 ISSUE. The diff between 1.15 and 2.0 is actually minimal.
It breaks with version 1.9, but not with version 1.15.
That means Ubuntu 20.04 is in the clear, and Ubuntu 18.04 for instance is affected.
I'll spare you the full diff, let's just focus on what matters:
# diff -u <(grep 'type="string"' bionic/usr/share/mime/packages/freedesktop.org.xml) <(grep 'type="string"' focal/usr/share/mime/packages/freedesktop.org.xml) | grep eval
-      <match value='eval \"exec /bin/gjs' type="string" offset="0"/>
-      <match value='eval \"exec /usr/bin/gjs' type="string" offset="0"/>
-      <match value='eval \"exec /usr/local/bin/gjs' type="string" offset="0"/>
+      <match type="string" value="eval \"exec /bin/gjs" offset="0"/>
+      <match type="string" value="eval \"exec /usr/bin/gjs" offset="0"/>
+      <match type="string" value="eval \"exec /usr/local/bin/gjs" offset="0"/>
-      <match value='eval \"exec /usr/local/bin/perl' type="string" offset="0"/>
+      <match type="string" value="eval \"exec /usr/local/bin/perl" offset="0"/>
-      <match value='eval \"exec /bin/python3' type="string" offset="0"/>
-      <match value='eval \"exec /usr/bin/python3' type="string" offset="0"/>
-      <match value='eval \"exec /usr/local/bin/python3' type="string" offset="0"/>
-      <match value='eval \"exec /bin/python' type="string" offset="0"/>
-      <match value='eval \"exec /usr/bin/python' type="string" offset="0"/>
-      <match value='eval \"exec /usr/local/bin/python' type="string" offset="0"/>
+      <match type="string" value="eval \"exec /bin/python3" offset="0"/>
+      <match type="string" value="eval \"exec /usr/bin/python3" offset="0"/>
+      <match type="string" value="eval \"exec /usr/local/bin/python3" offset="0"/>
+      <match type="string" value="eval \"exec /bin/python" offset="0"/>
+      <match type="string" value="eval \"exec /usr/bin/python" offset="0"/>
+      <match type="string" value="eval \"exec /usr/local/bin/python" offset="0"/>

The value string is evaled, and if that string is eval \"something, then, well...:
irb(main):008:0> value='eval \"exec /bin/gjs'
=> "eval \\\"exec /bin/gjs"
irb(main):009:0> value.gsub!(/\\(x[\dA-Fa-f]{1,2}|0\d{1,3}|\d{1,3}|.)/) { eval("\"\\#{$1}") }
Traceback (most recent call last):
        7: from /usr/bin/irb:23:in `<main>'
        6: from /usr/bin/irb:23:in `load'
        5: from /Library/Ruby/Gems/2.6.0/gems/irb-1.0.0/exe/irb:11:in `<top (required)>'
        4: from (irb):9
        3: from (irb):9:in `gsub!'
        2: from (irb):9:in `block in irb_binding'
        1: from (irb):9:in `eval'
SyntaxError ((eval):1: unterminated string meets end of file)

Lesson: don't parse things with eval ;)

@dzuelke thank you, that's really useful information. From the look of it this should be relatively simple to resolve, I'm not at all familiar with the guts of the parsing that's going on, but it does seem that not evaling things is going to go a long way, I think that's just a legacy of the original approach of dumping everything out to generated Ruby.

Note: it just happens to be that the string that's failing also contains the string "eval", but that is unrelated - all that it takes is any quotes in the string. Escaping might work.
This does beg the question though - why is this not happening on 1.15?
After all, the attribute value of value in this:
value="eval \"exec /bin/python3"

gets returned by the XML parser as this:
eval \"exec /bin/python3

Which should again trigger the problem.
Is the XML parsing also broken, maybe? It must be if the above string isn't triggering the problem, unless the code is (incorrectly!) accessing the raw attribute node value rather than its parsed representation.

We have been testing this in a few different environments and wanted to include our findings.
So far, we have been able to successfully parse the DB file with the following combinations of OS and shared-mime-info packages. We haven't done an exhaustive bisect or anything, but, our tests pass and our applications are booting successfully.
This was tested with v0.3.8 of mimemagic.

OS
shared-mime-info Version

macOS
2.1

Ubuntu 18 (via Docker)
shared-mime-info/now 1.9-2 amd64 [installed,local]

Ubuntu 16.04 (via AWS OpsWorks)
shared-mime-info/xenial-updates,now 1.5-2ubuntu0.2 amd64 [installed]

Ubuntu 16.04 (via Docker)
1.5-2ubuntu0.2

Yeah, follow up, I looked at this again - the way the eval actually works shouldn't even be affected by the quotes I pulled as an example.
Is this maybe a Ubuntu 14.04-only problem?
(Should still not crash there obviously).

I'm doing some testing against the specific version of the fd.o.xml mentioned in the original issue report, and it appears to be blowing up at the element <match value="\chapter" type="string" offset="0:100"/>, and only that element - commenting it out results in a successful run of the unit tests.

What's getting evaled here after the regex replacement is "\"\\c\"", which for some reason which isn't at all clear to me right now does indeed throw an unterminated string error if you call eval("\"\\c\"").

Sorry for the rapid fire comments, I'm at least partially talking to myself here.
That string is interpreted as "\c" - \c" is the literal for the control character ", which... isn't hugely useful. So yes, this is an issue with badly escaped characters. For the sake of getting this working in the one case it's known to cause problems I'm inclined to just hack something in so that \c gets rewritten to \\c before it's interpreted. Not clean, but it gets things moving again, and I don't really have the energy at this point to find a better solution.

starting from the Ruby:2.4.3 image, I get the error mentioned above when running my CI/CD pipeline to run my tests. I have confirmed that version 0.3.8 is being installed and the following error occurs when I run: bundle exec rails db:create db:schema:load db:migrate --trace
Here is the complete error that I get (in case it helps someone):

rails aborted!
SyntaxError: (eval):1: unterminated string meets end of file
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:29:in eval' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:29:in block (2 levels) in get_matches'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:29:in gsub!' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:29:in block in get_matches'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:238:in block in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in upto'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:19:in map'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:19:in get_matches' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:77:in block (2 levels) in parse_database'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:238:in block in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in upto'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:75:in block in parse_database'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:238:in block in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in upto'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/nokogiri-1.10.10/lib/nokogiri/xml/node_set.rb:237:in each' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic/tables.rb:70:in parse_database'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/mimemagic-0.3.8/lib/mimemagic.rb:8:in <top (required)>' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in require'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in block in require' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:258:in load_dependency'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/activesupport-5.1.7/lib/active_support/dependencies.rb:292:in require' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/axlsx-3.0.0.pre/lib/axlsx.rb:4:in <top (required)>'
/usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:81:in require' /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:81:in block (2 levels) in require'
/usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in each' /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:76:in block in require'
/usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in each' /usr/local/lib/ruby/site_ruby/2.4.0/bundler/runtime.rb:65:in require'
/usr/local/lib/ruby/site_ruby/2.4.0/bundler.rb:114:in require' /builds/research/datateam/dovecote/annotation_configurator/config/application.rb:7:in <top (required)>'
/builds/research/datateam/dovecote/annotation_configurator/Rakefile:4:in require_relative' /builds/research/datateam/dovecote/annotation_configurator/Rakefile:4:in <top (required)>'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/rake_module.rb:29:in load' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/rake_module.rb:29:in load_rakefile'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/application.rb:703:in raw_load_rakefile' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/application.rb:104:in block in load_rakefile'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/application.rb:186:in standard_exception_handling' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/application.rb:103:in load_rakefile'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/railties-5.1.7/lib/rails/commands/rake/rake_command.rb:20:in block in perform' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/rake-12.3.3/lib/rake/application.rb:186:in standard_exception_handling'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/railties-5.1.7/lib/rails/commands/rake/rake_command.rb:18:in perform' /builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/railties-5.1.7/lib/rails/command.rb:46:in invoke'
/builds/research/datateam/dovecote/annotation_configurator/vendor/ruby/2.4.0/gems/railties-5.1.7/lib/rails/commands.rb:16:in <top (required)>' bin/rails:4:in require'
bin/rails:4:in `'

🎉🎉🎉 thanks for all the work here!

Nice job, @jellybob, I didn't have a quick reproduce case on hand.
I should note that 20.04's version doesn't have that value anymore at all.
In 18.04 and 16.04, it's double backslash escaped:
<match value="\\chapter" type="string" offset="0:100"/>

In 14.04, it's got a single backslash:
<match value="\\chapter" type="string" offset="0:100"/>

So it looks like it's indeed only the EOL Ubuntu 14.04 that's affected in the first place.

@jellybob thanks again!


what's the problom

how to fix this？

Please update to the latest version, and make sure to refresh the page after loading from json, before running. Pushed updated jsons that shouldnt require this, but in any case.


[octavia-ingress-controller]: TLS Ingress doc

The binaries affected:
IMPORTANT: Please also add the binary name in the title, e.g.
[openstack-cloud-controller-manager]: Add UDP protocol support
unless the PR affects multiple binaries.

[ ] openstack-cloud-controller-manager
[ ] cinder-csi-plugin
[ ] k8s-keystone-auth
[ ] client-keystone-auth
[x] octavia-ingress-controller
[ ] manila-csi-plugin
[ ] manila-provisioner
[ ] magnum-auto-healer
[ ] barbican-kms-plugin

What this PR does / why we need it:
Add document for creating TLS Ingress.
Which issue this PR fixes:
fixes #
Special notes for reviewers:

Release note:

NONE

/lgtm
/cc @ramineni

/approve


Typescript Definition wrong

Hi there,
IObjectOptions have margin: Margin but ITextOpts have margin: number

thx!
Greetings
crazyx13th

Thanks @crazyx13th
Fixed with Pull #647


Update to 1.6.39

update to 1.6.39
update about section

Done to get valid .pc file on Windows, so pkg-config can operate proper on libpng for Windows too

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a8mnrzjgmb/clone/recipe/meta.yaml:13: http_url: http://download.sourceforge.net/libpng/libpng-1.6.39.tar.gz is not https
ERROR: /tmp/abs_a8mnrzjgmb/clone/recipe/meta.yaml:40: missing_tests: No tests were found.
ERROR: /tmp/abs_a8mnrzjgmb/clone/recipe/meta.yaml:52: http_url: http://www.libpng.org/pub/png/libpng.html is not https
ERROR: /tmp/abs_a8mnrzjgmb/clone/recipe/meta.yaml:53: http_url: http://www.libpng.org/pub/png/libpng.html is not https
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_80kkatngkr/clone/recipe/meta.yaml:40: missing_tests: No tests were found.
ERROR: /tmp/abs_80kkatngkr/clone/recipe/meta.yaml:52: http_url: http://www.libpng.org/pub/png/libpng.html is not https
ERROR: /tmp/abs_80kkatngkr/clone/recipe/meta.yaml:53: http_url: http://www.libpng.org/pub/png/libpng.html is not https
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_302nejwnrm/clone/recipe/meta.yaml:53: http_url: http://www.libpng.org/pub/png/libpng.html is not https
ERROR: /tmp/abs_302nejwnrm/clone/recipe/meta.yaml:54: http_url: http://www.libpng.org/pub/png/libpng.html is not https
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_13l73tt_x6/clone/recipe/meta.yaml:53: http_url: http://www.libpng.org/pub/png/libpng.html is not https
ERROR: /tmp/abs_13l73tt_x6/clone/recipe/meta.yaml:54: http_url: http://www.libpng.org/pub/png/libpng.html is not https
Errors were found


Cannot run multiple bench-cases together

Configured below bench case file-
bench_cases:
- name: "insert-person"
concurrency: 2
- name: "insert-friend"
concurrency: 2
Seeing errors from dgraph [ dgraph/dgraph:v1.0.12-rc1]
2019/01/06 23:10:05 Failed to call mutate: rpc error: code = Unknown desc = Uid: [3073121] cannot be greater than lease: [10000]
2019/01/06 23:10:05 Failed to call mutate: rpc error: code = Unknown desc = Uid: [972337] cannot be greater than lease: [10000]
When the bench file is changed as below to run only single bench-case, it works fine.
bench_cases:
- name: "insert-person"
concurrency: 2

You need to allocate UIDs /assign?what=uids&num=100
https://docs.dgraph.io/deploy/#more-about-dgraph-alpha


No intellisense for required builtin node modules after installing @types/node

From @shepelevstas on April 26, 2018 5:33
Version 1.22.2
Commit 3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9
Date 2018-04-12T17:28:16.777Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32
To reproduce:
CMD
md test
cd test
md src
npm init -y
npm i @types/node
tsc --init
code . --disable-extensions

//tsconfig.json
{
	// these are default
	"compilerOptions": {
		"target": "es5",
		"module": "commonjs",
		"strict": true,
		"esModuleInterop": true
	},
	// additional
	"files": [
<EMAIL_ADDRESS>	],
	"include": [
		"src/**/*.ts"
	],
	"exclude": [
		"node_modules"
	]
}

//src/index.ts
const fs = require('fs')
var dirList = fs.| //<- **_NO INTELLISENSE_**

Or maybe I'm doing it wrong?
Copied from original issue: Microsoft/vscode#48731

From @WangPengJu on April 28, 2018 9:52
I also met this problem
https://github.com/Microsoft/vscode/issues/48883
https://github.com/Microsoft/vscode/issues/45584

See also #23711

a.ts
import fs = require("fs");
namespace G {
    export let a = 0;
}

b.ts
G.a // error

I want use namespace as global. not single module. but if use "import fs = require('fs')" in "a.ts",   "b.ts" can't use G.   if use "const fs = require("fs")", it's work.
"const fs = require("fs")" no  intellisense in vscode, webstorm have intellisense. it's confuse me.

A file can not be both a global script and a module. it is either one or the other.. import .. = require(..) only works for modules. if you are using namespaces, then you should do something like:
const fs: typeof import ("fs") = require("fs");

@weswigham do we have an issue for higher-order import types?

I don't think one's actually been opened yet, no.

We should then. we should collect such use cases.

const fs: typeof import ("fs") = require("fs");

[ts] Cannot find name 'import'.
[ts] The left-hand side of an assignment expression must be a variable or a property access.

@WangPengJu import types are only in the nightly right now, as we've yet to cut a release since adding them.

ok. i can wait @weswigham


Disable LTO in CMakeLists.txt

Forced disable of LTO by CMake.
Required if the parent project uses set(CMAKE_INTERPROCEDURAL_OPTIMIZATION ON)

I don't really know.
The PR was maked based on the information from the comment https://github.com/zlib-ng/zlib-ng/pull/1185#issuecomment-1068973228

You mention -flto, I hope you are aware that it is incompatible with zlib-ng unless compiling with Native enabled
(Because it requires all compilation units to be compiled with the same compiler flags, and that breaks -march, -mavx and similar).

cc @Dead2

@KungFuJesus As far as I know, this pull request only makes sense for cmake 3.9 or later... Currently we support older cmake versions than that...

@mtl1979, Yes, but for cmake < 3.9 this code is safe.
For cmake >= 3.9 the code protects against CMAKE_INTERPROCEDURAL_OPTIMIZATION enabled

Looks okay to me. It makes sense that we wouldn't want to allow LTO in zlib-ng if included in parent project that does allow LTO.

So, LTO does work with this project and there are shims in place to specifically disable it for things that compile with architecture specific vectorizations (to prevent IPO from say, using a block from one function in another that has possibly incompatible instructions). Does this PR suggest that's not enough?

Yes, I am also confused why this would be necessary, and what the consequences were if this were removed.

Because it requires all compilation units to be compiled with the same compiler flags, and that breaks -march, -mavx and similar

Is that so? For which compilers, is there a reference for that?

Though in my more recent experiments LTO has hurt more than helped performance on zlib-ng.

That's a different question, and probably depends on the specific toolchain / compiler version.


Add contract classes "Restrict to specific Security Level"

Add Policy to the UI for "restrict to specific Security Levels".
User can select idsc:TRUST_SECURITY_PROFILE or idsc:BASE_SECURITY_PROFILE or idsc:TRUST_PLUS_SECURITY_PROFILE

Added in 5b9c0d3


conf/conf.sh.dist missing/wrong folder structure

Dear Sir,
thank you for this great Modul. Love it so far.
You might by notice that the folder you are pointing in conf/conf.sh.dist are incorrect and need to be adjusted or the folder them self need to be edited to reflect the "standard" folder stucture.
Thanks Itow

Thank you for point out this issue! I have updated the paths in https://github.com/ZhengPeiRu21/mod-reagent-bank/commit/818916bb1c3232b63c6a0c3ca222faef49a90033. Please let me know if you continue to see any problem.


Epoch page: future slots are being refreshed

Why do we refresh slots that are still in the future? It seems to send a lot of extra API calls when we are looking at the head epoch. I think we should only try to refresh the slots after the slot time has finally passed.
For example, if we go one or two epochs in the future, we make hundreds of extra API calls for slots with future timestamps, all returning HTTP 404.

agree, I think I just couldn't find a good policy for refreshing in SWR, i.e., IIRC it tries to increase time exponentially.
a good policy would be: refresh it after current time > expected time, but I couldn't find a way to program SWR to do it declaratively.
but there is one more gotcha: let's say you refresh it once the expected slot time is reached, but the slot is not there. it could be your browser clock is not behind, so the slot actually didn't come yet; it could be that your CL node didn't receive the slot info from the network, so you need to refresh it again after a certain time.
but it could be that the slot was missed, so once you receive the next slot after that, you may not want to refresh the missed one anymore.

I'm also not satisfied with the approach of querying all slots on epoch page, that +the issues in the comment above make me think if it would be better to wait for the Erigon full CL node implementation and add a custom API for batch epoch/slot info and handle everything on node side.
I don't feel like hacking/customizing any of existing CL implementations like I did in Erigon, but if Erigon completes a full CL node implementation that should be ok to do.


Curious about your GPU specification

Hello, thanks for your great work!
While reading the paper, I became curious about your experimental setting.
I wanted to know the GPU type that you used for the experiment, but couldn't find it in the paper...
May I ask you the type of GPU that you used, and how long did it take for text completion generation (500 samples?) in your environment?
Thanks!!

Thank you for answering my question!


[stable/warp] Add Helm Chart for Warp (S3 Benchmark tool from MinIO)

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
This adds a new Chart for Warp (New S3 Benchmark tool from MinIO Team)
Which issue this PR fixes
NA
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/assign @unguiculus


Cannot pass email/pw to lgogdownloader?

It is possible to automate setting a password with passwd, and then unset the values to delete them. Is it not possible to pass values to lgogdownloader? The dev of VaporOS (SteamOS variant) and I are trying to make a zenity dialog script tool (that will become a package maybe) for users to download from GOG using this tool. The aim is to automate (in a more visual way for people) logging in, downloading, etc.
echo -ne<EMAIL_ADDRESS>| lgogdownloader --login-api

Result:
Unable to read email and password

If it is trivial, can it be made to pass this to the native command?
lgogdownloader --login-adpi username password

Seems like the reason login via pipes is failing is line 135 in downloader.cpp.
    if (!isatty(STDIN_FILENO)) {
        std::cerr << "Unable to read email and password" << std::endl;
        return 0;
    }

!isatty(STDIN_FILENO) checks whether stdin is redirected. If it is the login function is aborted and the application terminated.
Is this intended behaviour or is there a different reason why this check is made?

Looks like this check was first introduced with the commit 574a315c4444920e5fe64d429d1d3acf0dd74a84. Just removing the check won't work either because getpass(<string>) expects to get it's data from a terminal, not a pipe.
Good thing this is easy enough to work around with a short expect script. Expect will not only work with getpass but will also pass the isatty(STDIN_FILENO) check.
expect << __EOF__
eval spawn "lgogdownloader --login";
expect "Email:";
send "<email>\n";
expect "Password:";
send "<password>\n";
expect "Login successful";
interact;
__EOF__

Great idea, I was used to patch (hardcode) my own user-id & password in compiled program, but this is better.

I tired on a new build today, lgogdownloader --login and my email and password failed.

Is this specific to automated logins or does this happen when you try logging in manually as well?
A bug similar to the one you are experience seems to be documented in an existing issue: https://github.com/Sude-/lgogdownloader/issues/77

Yep, pretty much #77 is what I meant. I'll take my issue to that thread and close this. I hope this gets sorted out at some point. The lack of GOG Galaxy makes this tool extremely useful for gamers and tinkerers (I made packages for SteamOS). Thank you for the response.


Loading for infinite scroll

onScrollEnd we invoke an api, during this time app feels stuck, need a loading state onScroll end while api is getting more data. It would be great if this loading can be customizable

@snehmehta this is P1 and blocking a customer, please put as highest priority


Support for Custom Loss Functions During Fine-Tuning

I'm trying to fine-tune the TimesFM model on intermittent time-series data. The default avg_qloss loss function isn't ideal because quantile predictions vary significantly. I aim to focus the loss computation solely on the median (50th percentile).
When specifying only the median quantile, the model throws a dimension mismatch error since it's pre-trained on multiple quantiles.
tfm = timesfm.TimesFm(
    hparams=timesfm.TimesFmHparams(
        backend="gpu",
        per_core_batch_size=16,
        horizon_len=3,
        quantiles=[0.5],  # Attempting to set only the median quantile
    ),
    checkpoint=timesfm.TimesFmCheckpoint(
        huggingface_repo_id="google/timesfm-1.0-200m"
    ),
)

Error:
ScopeParamShapeError: Initializer expected to generate shape (1280, 1280) but got shape (1280, 256) instead for parameter "w" in "/horizon_ff_layer/output_layer/linear".

Is it possible to specify a custom loss function in fine tuning step that targets specific quantiles (e.g., the median) without altering the model's architecture? or alternatively, can the model be configured to ignore certain quantiles during loss computation while retaining the expected parameter shapes in below section?
@pax_fiddle.auto_config
def build_learner() -> learners.Learner:
    return pax_fiddle.Config(
        learners.Learner,
        name='learner',
        loss_fn=median_quantile_loss,  # Custom median quantile loss
#       loss_name='qloss',  # or using qloss with specified quantile
#       quantiles = [0.5]
        optimizer=optimizers.Adam(
            epsilon=1e-7,
            clip_threshold=1e2,
            learning_rate=1e-2,
            lr_schedule=pax_fiddle.Config(
                schedules.Cosine,
                initial_value=1e-3,
                final_value=1e-4,
                total_steps=40000,
            ),
            ema_decay=0.9999,
        ),
        bprop_variable_exclusion=['.*/stacked_transformer_layer/.*'],
    )

You can locally clone the package and directly modify the loss function here: https://github.com/google-research/timesfm/blob/master/src/timesfm/patched_decoder.py#L528


[Roots 3] Aubergine seeds missing model

planted aubergine seeds are missing a model, defaults to purple/black checker board pattern

Duplicate #51


[Android] Fixes needed to get EditorSyledTextView to work with screenshot tests

Changes

Workaround for isInEditMode() being always false in Paparazzi tests. isInEditMode is used in Android code to decide whether to load the native libs or not.
Use Context instead of Application in AndroidResourcesHelper (LayoutLib in Paparazzi can't cast applicationContext to Application).

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (8e127b3) 87.39% compared to head (c83334d) 87.22%.

Files
Patch %
Lines

...lement/android/wysiwyg/compose/EditorStyledText.kt
0.00%
4 Missing :warning:

...io/element/android/wysiwyg/EditorStyledTextView.kt
0.00%
0 Missing and 2 partials :warning:

...o/element/android/wysiwyg/utils/ResourcesHelper.kt
66.66%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #899      +/-   ##
============================================
- Coverage     87.39%   87.22%   -0.18%
- Complexity      415      416       +1
============================================
  Files           166      134      -32
  Lines         18987    17403    -1584
  Branches       1049      412     -637
============================================
- Hits          16593    15179    -1414
+ Misses         2093     1946     -147
+ Partials        301      278      -23

Flag
Coverage Δ

uitests
65.51% <30.00%> (-5.61%)
:arrow_down:

uitests-android
65.51% <30.00%> (-0.32%)
:arrow_down:

uitests-ios
?

unittests
86.49% <25.00%> (+1.07%)
:arrow_up:

unittests-android
44.30% <25.00%> (-0.13%)
:arrow_down:

unittests-ios
?

unittests-rust
89.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


LUA Error - Add Patron Orders

I get the following LUA error now anytime I try to add patron orders to my crafting que using version <IP_ADDRESS>.
Message: .../Modules/ReagentOptimization/ReagentOptimization.lua:439: attempt to perform arithmetic on field '?' (a nil value)
Time: Wed Oct  2 20:20:35 2024
Count: 1
Stack: .../Modules/ReagentOptimization/ReagentOptimization.lua:439: attempt to perform arithmetic on field '?' (a nil value)
[string "=[C]"]: ?
[string "@Interface/AddOns/CraftSim/Modules/ReagentOptimization/ReagentOptimization.lua"]:439: in function calculateArrayBP' [string "@Interface/AddOns/CraftSim/Modules/ReagentOptimization/ReagentOptimization.lua"]:469: in function OptimizeReagentAllocation'
[string "@Interface/AddOns/CraftSim/Classes/RecipeData.lua"]:713: in function `OptimizeReagents'
[string "@Interface/AddOns/CraftSim/Modules/CraftQueue/CraftQueue.lua"]:202: in function <...ce/AddOns/CraftSim/Modules/CraftQueue/CraftQueue.lua:201>
Locals:

This was resolved with the next update, thank you.


remove c.env == "" condition that makes all seeds run in default env

Addresses concern described in issue #5 where seeds registered for specific envs run in the common default env.
Fixes #5

I replied to the issue
https://github.com/kristijorgji/goseeder/issues/5#issuecomment-1154029974
The described behaviour is the expected one.
I forgot to document it.
common is not a real environment, but a special one that means that everything that is created as a common seed is meant to run always.
For this reason in the programmatic interface, is offered also the documented option shouldSkipCommon
For example in my real usage for test seeds, I use
err := goseeder.Execute(con, goseeder.ForEnv("test"), goseeder.ShouldSkipCommon(true))

because I have different mock data for commons as well.

I replied to the issue
https://github.com/kristijorgji/goseeder/issues/5#issuecomment-1154029974
The described behaviour is the expected one.
I forgot to document it.
common is not a real environment, but a special one that means that everything that is created as a common seed is meant to run always.
For this reason in the programmatic interface, is offered also the documented option shouldSkipCommon
For example in my real usage for test seeds, I use
err := goseeder.Execute(con, goseeder.ForEnv("test"), goseeder.ShouldSkipCommon(true))

ShouldSkipCommon(value bool) - this option has effect only if also gsenv if set, then will not run the common seeds (seeds that do not have any env specified

because I have different mock data for commons as well.


Metadata for resources

We'd like to be able to set metadata for resources in the mission model. At a minimum we need to set units. A description would also be nice. The units should be displayed when the resource is plotted in the UI, and metadata should be available through the GraphQL API. Exposing units through the API is important for being able to use resources from Aerie in other tools.

Closing in favor of https://github.com/NASA-AMMOS/aerie-ui/issues/822 and https://github.com/NASA-AMMOS/aerie/issues/1034


chore(all): Adjust dependabot settings

Description
As partly discussed in this PR.
Related Issues
Our dependabot update policy continuously tightens the constraints, updating every single patch release - making the latest versions of plus_plugins less compatible with the rest of the ecosystem.
I'll just open this PR and leave it to discussion whether any included changes make sense for plug_plugins.
Following the changes plus my understanding of the benefit:

Ignore dependabot pub updates for minor and patch releases:
If a plugin declares a dependency x of 1.0.0, it's potentially compatible with version 1.0.0 up to <2.0.0 and apps using the same dependency itself, or other packages using it (within the range >=1.0.0 <2.0.0). Updating to i.e. 1.2.4 tightens the constraints of all apps and packages using the plugin, making it less compatible with other packages, while bringing no benefit other than forcing users or other package maintainers to update their dependencies, which should not be our goal (unless there is an incompatibility with an older version, in which case the dependency should be manually updated to exclude lower versions).
Change the website dependency check from weekly to monthly. Idk if the overhead of almost weekly updating a lint dependency for the website brings a benefit.
Add dependabot gradle checks (please let me know if they were missing for a reason).

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

I totally agree here with the suggested update. Same applies to Gradle plugin updates, like currently open bump to 8.1.0 - I don't think it makes sense to push that hard with only latest.
In general, except for what you described I would suggest to bump some dependency version also in case there is some important fix (security or critical bug) introduced - I believe such cases worth it to bump minor versions as well.

Add dependabot gradle checks (please let me know if they were missing for a reason).

I believe that we just missed those parts. Namely, it was me, who worked on this Dependabot config and I could forgot a few items worth watching.

Ok cool. I also agree about the importance of manual updates if it's critical or necessary.
How to proceed with the Gradle parts (so far unchanged in this PR)?
In my understanding, they don't behave the same as pub dependencies (you could have a higher version in a package than in your app). Your feedback is important, since you're the Android expert here 😁

How to proceed with the Gradle parts (so far unchanged in this PR)?

Didn't get what you mean here

The dependabot Gradle update policies remain unchanged in this PR.
Should we add the same as for pub dependencies?

Understood now. I would suggest to also make Gradle checks monthly as we really don't need to keep that on par with Android ecosystem in plugins. As to update types I would only drop patch updates as from experience minor releases in Android libraries are usually useful with fixes/new features.
We can do it in another PR.
P.S. A bit off-topic, but I have an itch to try and replace Dependabot with Renovate for some time already as it seems to me that we will have a better experience with configs/updates in Renovate.

Good idea trying out another tool for dependency updates 👍🏽


pickAll - incorrect behavior if key name is hasOwnProperty

If elements in pickAll method has name equal to methods available in Object prototype returning value is not correct:
Examples:
R.pickAll(['a', 'hasOwnProperty'], {a: 1});
R.pickAll(['a', 'toString'], {a: 1});

Actually the result is what I would have expected as the documentation doesn't hint at all about the function picking only the "own properties" of the object. Given that, references to inherited properties, not only the ones in the Object prototype, are copied as "own properties" in the resulting object.
Or did I miss your point?

Ye, You are right.
Sorry for confusion


[ENH] - Add nebari-destroy workflow

Feature description
For users who have ci_cd enabled in their nebari-config.yaml, they can use GitHub Actions to deploy their cluster. It would also be neat if we could have a nebari-destroy workflow that destroys the cluster (triggered via a workflow_dispatch).
Value and/or benefit
This would allow users to avoid having to handle any of the cluster management on their local machine.
Anything else?
No response

This would be a great feature to have. For cost management reasons I think this is a needed feature considering how little effort something like this would be.


Alternate implementation using exiftool

Hi! I appreciate your work on this program. I had trouble getting pyexiv2 to build on my Apple Silicon Mac. I found that exiftool worked great, though, and was able to apply metadata that Photos reads. Because of the scale for this fork, a straight PR might not make sense but you may want to consider linking to my version in your readme.
And thanks, again, for your work on this! I'm able to look at some photos from my adventures from a long time ago and it's been good remembering those times.
-Alex

Thanks for letting me know, Alex. I've added a link to your fork to the end of my readme.

Awesome, thanks!


Flaky test: TestClientServerStreamRedirect

--- FAIL: TestClientServerStreamRedirect (0.00s)
    Error Trace:    raftproxy_test.go:142
    Error:      Expected nil, but got: &errors.errorString{s:"EOF"}

This one fails occasionally. If there's no fix in sight, should we disable it so it doesn't interfere with CI?
@LK4D4

Example: https://circleci.com/gh/docker/swarmkit/4979

Hit this again: https://circleci.com/gh/docker/swarmkit/5024
Should we disable the test?

It seems TestClientStreamRedirect is flaky as well:
--- FAIL: TestClientStreamRedirect (0.00s)
	Error Trace:	raftproxy_test.go:117
	Error:		Not equal: 0x8 (expected)
			        != 0xb (actual)

Spent some time tracking this down.
These tests are inherently racy and I'm going to remove them.
They end up having the proxy connect to itself, and the second invocation will error out because of a mechanism that protects against routing loops. Sounds good so far. But here's the generated code inside the proxy:
        clientStream, err := NewRouteGuideClient(conn).RecordRoute(ctx)

        if err != nil {
                return err
        }

        for {
                msg, err := stream.Recv()
                if err == io.EOF {
                        break
                }
                if err != nil {
                        return err
                }
                if err := clientStream.Send(msg); err != nil {
                        return err
                }
        }

The first line invokes the RecordRoute RPC asynchronously. This RPC will fail quicky upon detecting the routing loop. The test will only succeed if the Send happens before the client realizes that RecordRoute has failed. Otherwise, Send will return an error ("EOF"). Adding a sleep before stream.Recv makes the test fail reliably.
Since these tests are only testing a pathological error case, and it turns out that case is inherently racy and we can't really do anything about it (sending to a streaming RPC handler that has exited may error out), it's best to just remove these tests. Ideally in the future we'll add test coverage for non-pathological cases (although there is already some coverage of this in integration tests).


improve the documentation of orthogonal polynomials

gh-6540 improved the documentation of orthogonal polynomials. As a follow-up, we should

[ ] update eval_* docstrings
[ ] cross-link functions returning orthopoly1d objects, and their corresponding eval_* and *_roots.
[ ] document the orthopoly1d object itself and add clear usage guidelines (e.g. which operations
convert to power basis)
[ ] clarify the relation to newer numpy.polynomials

Alternatively, maybe we want to even deprecate np.poly1d-based polynomials in favor of np.polynomials.

Alternatively, maybe we want to even deprecate np.poly1d-based polynomials in favor of np.polynomials

Big +1 from me. If we do this then we should also extend the *_eval and *_roots functions so that they support arbitrary intervals and link that up with the window attribute of Polynomial

The poly1d-based orthopoly could be removed, it's dangerous for naive users and not useful for people who know about it...

not useful for people who know about it...

That's a good point. I might like removing orthopoly1d and replacing it with nothing over replacing it with something based on np.polynomial.


feat: add email mecanism

:tada: This PR is included in version 1.30.0 :tada:
The release is available on:

GitHub release
v1.30.0

Your semantic-release bot :package::rocket:


Make certain things configurable

Precision. Also, dial down the default precision.
Units. Should be able to define new units.
...

Can't define new units, but that's more of a stretch goal.


API support to unpack individual elements using protobuf ID and DataType

We need the reverse of the below packing operation

Currently, data can be unpacked only if we know the message type in advance.

Thanks, @ccifra for providing the initial set of capabilities in the commit on Commits on Nov 3, 2021.
I have tested the Numeric, string, and 1D Numeric unpack fields capability - It works as expected. Feel free to close this commit if you have covered sufficient data types already or mark the uncovered data types and we can use to track it here.

We have implemented this for most data types in the latest release.  I am going to leave this issue open until we can complete the data type support and create higher level wrapper APIs.
Unimplemented is repeated strings, repeated bytes and nested messages.


Use comma as "or" operator for queries

Scan the query parts for commas (u',') and treat these as (sub) AndQuerys
that need to be wrapped in an OrQuery (if there are more than one).
Supports foo, bar and foo , bar.
See #976

That means that any query holding a comma should now be escaped... I'm not sure how I feel about that.

Awesome! This looks great to me. As that thread in #976 suggested, a comma seems like the right thing to me. It's not quite true, @brunal, that every comma will need to be escaped—commas are only ORs when they appear by themselves or at the end of a term. So foo, bar is an OR query but foo,bar is not. In the shell, quotes even behave as expected, so:
$ beet ls "foo, bar"

does not invoke an OR query.
I'm inclined to merge this now. We could restrict this to only work with separated commas (foo , bar), but I'm inclined to say that this is less surprising as-is.

@sampso My original implementation only worked with separated commas, but I found myself constantly typing foo, bar during testing, so for ease of use I'd definitely try and keep it as-is (if possible).

OK, merged! We can at least see how people like this design. Thanks again! This will be awesome to have. :sparkles:

Awesome! Thanks a lot, @tomjaspers!


onnx v1.15.0

Follow up to https://github.com/conda-forge/onnx-feedstock/pull/102.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


remove field Name from NodeSpec

fixes #28351
I think field Name in NodeSpec is not used. Then I try to remove this part.
If the design is OK, I am afraid we still need to remove that from swarmkit side.
- What I did

remove field Name from NodeSpec;
changed some typos in API doc 1.24;
remove node name update part from API doc 1.25.

- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: allencloud<EMAIL_ADDRESS>

can you open a separate PR for the typo fixes in the documentation? Those may be needed to update the docs, separately from this PR

Oh yes. Did it in https://github.com/docker/docker/pull/28359

ping @aluzzardi @stevvooe
I'm not sure we want to do this. Even if the name is not used right now for nodes, it's possible we could start using it in the future. And also, it's nice for top-level to consistently use the same Annotations structure.

This change is very backwards incompatible and I cannot condone it.
The ability to name nodes was originally intended to provide operator relevant reference to node resources independent of hostname. This allows one to update and delete nodes by name, enforcing a uniqueness constraint without externalizing those constraints.
Rather than remove the field because we don't use it, let's make the field properly useful.

I recommend we close this and continue to use Annotations in NodeSpec.

I agree, thanks @aaronlehmann @stevvooe


Tutorials not loading for new, unregistered user?

I'm testing the app from the point of view of an unregistered user, and the tutorials do not seem to be loading (or if they do, it is taking a very long time - longer than ~3.5 minutes). I tried both on wifi and on my phone signal - neither worked. Is anyone else able to get it working? This testing is for 1.4.3 - I believe it was working just fine for me in 1.4.2.

This is really odd - works without issue when running a browser build (even in release mode, on webkit) but I can reproduce on iOS. Will see what I can do to investigate further

Seems like this error is causing it (ie, the fetch for the puzzle data isn't completing), which appears to be a wkwebview (or rather cordova-plugin-ios-xhr?) thing. This also happens when trying to go after the (first) Eterna essentials quest when logging in.
{
  "message": "Network Error",
  "name": "Error",
  "stack": "@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/bundle.js?[chunkHash]:2:6194\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/bundle.js?[chunkHash]:2:1256\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/plugins/@globules-io/cordova-plugin-ios-xhr/src/www/ios/xhr-polyfill.js:1187:22\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/plugins/@globules-io/cordova-plugin-ios-xhr/src/www/ios/xhr-polyfill.js:988:24\n@[native code]\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/plugins/@globules-io/cordova-plugin-ios-xhr/src/www/ios/xhr-polyfill.js:691:39\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/plugins/@globules-io/cordova-plugin-ios-xhr/src/www/ios/xhr-polyfill.js:705:25\n@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/plugins/@globules-io/cordova-plugin-ios-xhr/src/www/ios/xhr-polyfill.js:729:19\nglobal code@file:///private/var/containers/Bundle/Application/1DBB2253-DA43-4D71-803E-7B6BF6DEACCF/Eterna.app/www/index.html#/quests/eterna_essentials/1?progression=true&tags=Introduction%20to%20RNA&firstQuest=true:1:24",
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 0,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "headers": {
      "Accept": "application/json, text/plain, */*"
    },
    "baseURL": "https://eternagame.org",
    "withCredentials": true,
    "method": "get",
    "url": "/get/?type=puzzles&sort=date&puzzle_type=Progression&single=false&switch=false&notcleared=false&uid=null&tags=Introduction to RNA"
  },
  "status": null
}

Given the base URL, I have no idea why it's complaining about a null scheme. Maybe it doesn't like the spaces in the URL...? I'll try URL encoding it and seeing what happens.


Spotify playback? [Feature Request]

Issue Type

[ 0 ] Bug Report
[ 1 ] Feature Request

Description
Can we add support for Spotify playback?

Spotify does not supports that

It is not possible to play music from Spotify, as this breaks their Terms of Service. Other bots just take the names of the tracks from Spotify and look them up on YouTube. However, this is not possible without a Spotify API key, and this bot will not utilize services that require keys beyond a Discord bot token.


[WIP] Improvements to the editor

TODO:

[x] Use new tools for ordering the widgets (first of all, stop using grid)
[ ] Provide "themes" and the option to customize it. Fixes #80
[ ] Update the docs to give a useful guide to users

I also removed the Text and used a ScrolledText instead (see the reference for ScrolledText here).

I think I'm almost done with this... or that's what I hope.

Ok, by now, it works. However, I have an issue with customizing and loading themes. I will just skip this and go to the docs by now.

Most of the thing is moving good. However, it seems like just one theme is taken into account. For example, I have two themes by default (a light and dark one), but nly the light or dark theme is used, even when you select the other! What's happening here?

Ok, this works now. By the moment, only the background and foreground are painted. In the future, I want to work in syntax highlights.

Merging this, since CodeQL won't fail on this.


chore(download): lower the buffer limit for bodies downloader

Caps maximum buffered items at limit * response size = 200k non-empty bodies

Codecov Report

Merging #1178 (bfecfbc) into main (ba70b3b) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1178      +/-   ##
==========================================
- Coverage   75.29%   75.29%   -0.01%
==========================================
  Files         335      335
  Lines       36432    36432
==========================================
- Hits        27433    27431       -2
- Misses       8999     9001       +2

Flag
Coverage Δ

unit-tests
75.29% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/staged-sync/src/config.rs
71.62% <100.00%> (ø)

crates/net/network/src/session/mod.rs
69.10% <0.00%> (-1.43%)
:arrow_down:

crates/net/eth-wire/src/capability.rs
62.13% <0.00%> (-0.98%)
:arrow_down:

crates/net/network/src/session/active.rs
86.06% <0.00%> (-0.17%)
:arrow_down:

crates/stages/src/stages/bodies.rs
93.12% <0.00%> (+1.55%)
:arrow_up:

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

@mattsse agreed, ideally we would come up with a way to dynamically adjust max buffer size


feat: adding in @http directive support

Adding in @http directive support

Codecov Report

Merging #65 (c2de0b6) into main (c659fe5) will decrease coverage by 0.16%.
The diff coverage is 95.00%.

@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
- Coverage   95.60%   95.43%   -0.17%
==========================================
  Files           4        4
  Lines         273      307      +34
  Branches       73       85      +12
==========================================
+ Hits          261      293      +32
- Misses         10       12       +2
  Partials        2        2

Impacted Files
Coverage Δ

src/index.ts
100.00% <ø> (ø)

src/transformer/cdk-transformer.ts
98.09% <90.90%> (-1.91%)
:arrow_down:

src/appsync-transformer.ts
92.98% <100.00%> (+1.14%)
:arrow_up:

src/transformer/schema-transformer.ts
95.40% <100.00%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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


There was an error in evaluating the Pre-request Script:TypeError: Cannot read properties of undefined (reading 'length')

I received an error when sending after pasting in the pre-request-script from the example provided in the article.
There was an error in evaluating the Pre-request Script:TypeError: Cannot read properties of undefined (reading 'length')

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

ID: f34d51d3-4e41-897c-c2a0-088516676cea
Version Independent ID: 1bd77fa2-c81d-9746-2c18-3930f00f6c6a
Content: Tutorial - Sign and make requests to Azure Communication Services' SMS API with Postman - An Azure Communication Services tutorial
Content Source: articles/communication-services/tutorials/postman-tutorial.md
Service: azure-communication-services
Sub-service: sms
GitHub Login: @ProbablePrime
Microsoft Alias: rifox

@npalmer1452
Thanks for your feedback! We will investigate and update as appropriate.

@npalmer1452 We are still in the process of obtaining a phone number, but we are getting successful error messages stating we do not have permissions to use the phone number we tried or that the phone number was an incorrect format. This tells me my sample is successfully authenticating and thus receiving error messages.
I followed the sample step by step so I would advise you to review the document again to ensure you did not miss anything. I did not do anything outside the scope of the document, and this is my first attempt going through this specific document so I would not say I am an advanced user. Let us know if you are trying to modify the steps listed in the document in any way as this would change how we need to troubleshoot.
Let us know once you have reviewed the document and if you have further errors.


fix(tags): improve the error message when the combination of tags match no node labels

Improved the error message and call out the new tag(s) that are causing the problem
Fixes #486

Current coverage is 82.63%

Merging #565 into master will increase coverage by +0.18% as of aa370be

@@            master    #565   diff @@
======================================
  Files           36      36
  Stmts         2303    2309     +6
  Branches       331     333     +2
  Methods          0       0
======================================
+ Hit           1899    1908     +9
  Partial        115     115
+ Missed         289     286     -3

Review entire Coverage Diff as of aa370be

Powered by Codecov. Updated on successful CI builds.


[feature] expose mutable API for OneToMany

Propose a new function OneToMany::add_link(&mut self...) to allow to update a relation (so far, OneToMany is immutable and that would make it mutable).

Some summary of what I've found and explore so far about the signature of this new add_link() function. For all the below sections, assume the following already exists.
let brands = CollectionWithId::new(vec![brand1, brand2])?;
let bikes = CollectionWithId::new(vec![bike1_brand1, bike2_brand1, bike3_brand2])?;
let mut brands_to_bikes = OneToMany::new(&brands, &bikes, "brands_to_bikes");

let brand1_idx = brands.get_idx(&brand1.id).unwrap();
let brand2_idx = brands.get_idx(&brand2.id).unwrap();
let bike1_brand1_idx = brands.get_idx(&bike1_brand1.id).unwrap();
let bike2_brand1_idx = brands.get_idx(&bike2_brand1.id).unwrap();
let bike3_brand2_idx = brands.get_idx(&bike3_brand2.id).unwrap();

Only Idx
fn add_link(&mut self, from: Idx<T>, to: Idx<U>);

The problem of this signature is that nothing prevents you sending Idx objects from a third CollectionWithId. Imagine the following example.
// This is fundamentally wrong if `bike3_brand2.brand_id` contains `brand1`
brands_to_bikes.add_link(brand_2_idx, bikes3_brand2_idx);

This is a logical bug. It's a problem since the responsibility lies in the hand of the caller, not contained inside OneToMany.
Verify the link between the objects
Let's improve on the precedent proposition and try to check the relation between objects before modifying our relation. With the following function signature, we should be able to do that.
fn add_link(&mut self, from: (Idx<T>, &T), to: (Idx<U>, &U));

Note that we can't just use &T and &U because we need the Idx to update our relation. With this signature, we should be able to check that to actually points to from with the following code.
let t_id = <U as Id<T>>::id(to.1);
if t_id == from.1.id {
  // to.1 actually points to from.1, we can update the relation
} else {
  // the objects are not related, do not update the relation (or error, or panic)
}

but there is still a few problems with this design. The first one: nothing prevents us of doing the following, which is obviously wrong.
// Note the second tuple where the `Idx` doesn't match the object reference
brands_to_bikes.add_link((brand1_idx, &brand1), (bike3_brand2_idx, &bike1_brand1));

bike1_brand1 actually points to brand1 so the above if return true... but we're going to add a relation between brand1_idx and bike3_brand2_idx which is wrong.
Another problem can be expressed in the following example.
let hacker_bikes = CollectionWithId::new(vec![hb1, hb2, hb3, hb4, hb5])?;
// hb5 actually points to the correct brand
assert_eq!(hb5.brand_id, "brand1");

let hb5_idx = hacker_bikes.get_idx(&hb5.id).unwrap();

// The tuples are consistents: each `Idx` match its corresponding object
brands_to_bikes.add_link((brand1_idx, &brand1), (hb5_idx, &hb5));

But this might actually trigger a panic!() in some other part of the code. For example, if we ask for all the Bikes corresponding to brand1, the result would be: bike1_brand1_idx, bike2_brand1_idx and hb5_idx. If we use them on the collection bikes... then bikes[hb5_idx] will panic!() since bikes contains 3 elements and hb5_idx would have an index of 4. The problem here is that Idx may come from another CollectionWithId than the ones used in OneToMany::new().
Keeps track of the collections in OneToMany
One solution to avoid the previous problem is to modify entirely OneToMany's structure. Today's structure is this.
pub struct OneToMany<T, U> {
    one_to_many: BTreeMap<Idx<T>, IdxSet<U>>,
    many_to_one: BTreeMap<Idx<U>, Idx<T>>,
}

We could modify it like this.
pub struct OneToMany<'c, T, U> {
    one_collection: &'c CollectionWithId<T>,
    many_collection: &'c CollectionWithId<U>,
    one_to_many: BTreeMap<Idx<T>, IdxSet<U>>,
    many_to_one: BTreeMap<Idx<U>, Idx<T>>,
}

This is only 2 more pointers so not to bad for memory space, and you ensure you keep track of the original collections. Introducing a lifetime also makes sense since OneToMany is meaningless without the underlying CollectionWithId. However, this introduces an additional lifetime generic parameter that might make OneToMany more difficult to use. In particular, in transit_model::model::Model which, is essentially like the following (here, it has been adapted to our examples with brands and bikes).
struct Model {
  collections: Collections, // Collections contains all the `CollectionWithId`
  brands_to_bikes: OneToMany<Brand, Bike>,
}

If we introduce this lifetime, we would have to write it like this.
struct Model {
  collections: Collections, // this is owned
  brands_to_bikes: OneToMany<'collection, Brand, Bike>, // lifetimes towards the owned `collection`
}

The problem is that the code above does not compile, and self-referential pointers are a hard problem in Rust. One way forward would be something along these lines.
struct Model<'c> {
  collections: &'c mut Collections, // this is not owned anymore
  brands_to_bikes: OneToMany<'c, Brand, Bike>,
}

But that brings a new lifetime constraint in Model...
Conclusion
It seems that none of the above options are ideal.
One important thing to notice is that the main argument is to have an API that is safe to call (the API user shouldn't be able to end up in corrupted state of OneToMany). But in reality, OneToMany is already unsafe to use unless some invariants are met... Indeed, nothing bounds the relation OneToMany to the existing CollectionWithId. Take this simple example.
// Let's remove some `Bike`s
bikes.retain(|b| b.brand_id == "brand1");
// Now `bikes` doesn't contain `bike3_brand2` anymore... but `brands_to_bikes` still does
let bike_idxs = brands_to_bikes.get_corresponding_forward(idx_set![brand2_idx]);
// `bike_idxs` contains only `bike3_brand2_idx`...
let bike3_brand2_idx = bike_idxs.get(0).unwrap();
// ... but `bike3_brand2` is not in `bikes` anymore, this will panic
let b = &bikes[bike3_brand2_idx]; // PANIC

So OneToMany already need some knowledge about how to use it in order to avoid unexpected behavior. If this is already the case, maybe adding another API that is assuming the same hypothesis is OK?

That was fun but won't fix the entire problem of mutability. Not needed anymore in transit_model. Closing this PR.


Private Disk

Does your package support private disks, like S3, and how can we set it to private?

we are building the package with spatie media library that's means you can change the disk from config


Typings for uritemplate

see https://www.npmjs.com/package/uritemplate

You probably want to submit typings to https://github.com/DefinitelyTyped/DefinitelyTyped. See the description in the README (https://github.com/DefinitelyTyped/tsd#tsd):

from the community driven DefinitelyTyped repository.


fix: use correct file extension for models file

This PR fixes another typescript related bug: As the models file so far used the .d.ts file extension, its contents were ignored during transcompilation, therefore preventing the use of the library in other typescript projects. Renaming the file to models.d.ts serves as an easy fix to this problem.
While I was at it I added more types from models.ts to the export list in index.ts as missing types also seem to have caused some issues beforehand.
Finally, I incremented the version number to 1.0.2 so that we could release a patched version immediately.

@Apollon77 Could you maybe have a quick look on this PR? :)

You do changelog&tag and I publish... again?

You do changelog&tag and I publish... again?

Sounds great :) Changelog and release are created now :)

npm on it's way too.
If you need to "Ping" me directly I could also offer email, telegram, whatsapp or discord as additional communication ways beside Github issues
:-)

npm on it's way too.

Awesome, thank you :)

If you need to "Ping" me directly I could also offer email, telegram, whatsapp or discord as additional communication ways beside Github issues :-)

That's great! :) Do want to send me an email with your contact information (you can find my address on my profile)? I think using Discord or Telegram would work best for me :)


Insert links to universities on front page text

In the following text, please insert a link to each university: "The Playful Systems group at MIT Media Lab has teamed up with Tilburg University to study how our game behavior relates to how we are in real life."
The highlighted "MIT Media Lab" text should link to http://www.media.mit.edu/
The highlighted "Tilburg University" text should link to https://www.tilburguniversity.edu/
Links should open in a new tab/window.

Verified fixed


Error on translations:find

Whenever I run translations:find, I get a SQL error (w/ artisan)
https://i.imgur.com/S9CoeeS.png

@Clyv, I suspect it is related to the local/group/key columns having case insensitive collation so the index is built and validated ignoring the case of these columns. If any one of them, most likely the key column has duplicates when ignoring case then this would happen.
I searched for an issue with a fix I saw but could not find it. All I found was a link to https://dev.mysql.com/doc/refman/5.7/en/case-sensitivity.html
If you can change the collation to case sensitive on these columns I think it will fix the problem.


Failing to convert Unicode < 9 characters from the IOS emoji keyboard (chrome & safari)

Hey,
I've been having issues converting several emojis on IOS 10 from the emoji keyboard. Some of these include:

SMILING FACE WITH HALO 😇
SMILING FACE WITH SUNGLASSES 😎
CONFUSED FACE 😕

and many others.
I've confirmed the following aspects of this issue:

Emojis are able to be input and stored in unicode format.
The result of replace_unified works as expected on a desktop web browser running Mac OSX or Windows.
The result of replace_unified is completely blank on both Chrome and Safari on IOS 10 for certain emojis.

Is this a known issue, or is there a way around this? I can create a JSFiddle if that would be helpful.

If anybody finds this, mobile web browsers support unicode emojis without the need to manipulate the unicode at all. So, if you have unicode emojis just don't do anything to them and they'll show up just fine.
Closing this issue.


fix: exclusively use githubreleases version update strategy to exclude prereleases

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] ~Bumped the build number (if the version is unchanged)~
[x] ~Reset the build number to 0 (if the version changed)~
[x] Re-rendered]( https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-feedstocks ) with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This is the most elegant fix to prevent the autotick-bot from making version updates for prereleases.
See https://github.com/regro/cf-scripts/pull/2837

@conda-forge-admin please rerender

Thanks a lot!


[TACHYON-1232] Move tachyon.LocalFilesystemCluster to tachyon.underfs…

Moved LocalFilesystemCluster under logical tachyon.underfs.LocalFilesystemCluster and fixed java import/package

Can one of the admins verify this patch?

Jenkins, test this please.

@chuyqa , thanks for the patch!
It seems your commits on GitHub aren't linked to a valid Github account.
For us to properly credit your contributions, could you please set up your Github account by following the Github instructions here?


Implement background process manager

Suggestion to use a background process library like Hangfire to handle processing background jobs.
Changes to the worker:

Instead of  start to end process, the worker will be constantly running (or waiting).
Can process tasks in parallel.

E.g. Scraper loads html, adds each job and company to background queue.
Worker can process n jobs and companies at the same time.
E.g. 2. While updating jobs, new jobs can be detected and added to a queue for notifications to be processed and sent later

Jobs can be scheduled
We can view the jobs through a web interface if we enable it

when I read Hangfire, I notice there are many types of jobs, for this one, we should be using Recurring Jobs correct?


some cells are deleted by mistake

The number of live cells ckb1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqhzeqga should  be 7, indexer store returns 0

fixed by https://github.com/quake/ckb-indexer/commit/a253e1f971b9d85623588fc748194cc5eb65feb8


Provided a robust way to add extra buttons to the snippet index header.

Fixes #11275
Added a new block inside the extra_actions fragment in wagtailsnippets/snippets/index.html to simplify adding extra buttons to the snippet index header.

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks a lot @lb- ! Looking forward to contribute more! And Bhuvnesh Sharma is perfect 👍


Unable to list bucket contents

I'm attempting to list a bucket contents; however, Bucket::list doesn't handle AWS's pagination, so the results are truncated. This seems to be intentional, though as a library consumer, I would really love to not need to implement pagination myself.
However: even aware of this, Bucket::list doesn't take a marker for an argument, so there's no good way to get latter pages of data. We can use add_query, but this again feels like something that the library should handle more straightforwardly for us. Lastly, even if I use that to provide a marker thusly,
        let mut bucket = Bucket::new(bucket, region.clone(), credentials.clone());
        if let Some(mark) = marker {
            bucket.add_query("marker", &mark);
        }
        let (list_output, _) = bucket.list("", None)?;

I get nonsensical results: is_truncated is true, but next_marker is None:
        if !list_output.is_truncated {
            break;
        } else {
            println!("is_truc = {:?}, marker = {:?}", list_output.is_truncated, list_output.next_marker);
            marker = list_output.next_marker;
        }

is_truc = true, marker = None

After some more digging: rust-s3 is using list-type=2, or v2 of the list API; that version doesn't return a marker, rather, it has been renamed ContinuationToken. (I think they did this as there are cases in the v1 API where marker was None, but the response was truncated; you figured out the next marker yourself from the last listed key. Sounds like from the docs they did away with all that; if your response is truncated, you get a continuation token, end of story, which is simpler.)

@thanatos Thank you for a very detailed report, I've just pushed an update to the dev branch, bucket::list() now automatically paginates and gets you all results in a S3Result<Vec<(ListBucketResult, u32)>>, which you can unpack as:
let results = bucket.list("", None).unwrap();
for (list, code) in results {
    assert_eq!(200, code);
    println!("{:?}", list.contents.len());
}

Each ListBucketResult holds a 1000 keys at most.
This will be pushed to Cargo today as 0.8.
Thanks once again, looking forward to more feedback :)


Redirection to Amazone issue

I just downloaded file by curl and run php victor.phar

fixed by https://github.com/nella/victor/commit/7b8b467fc1709ae56867937cf889d7e9d0e135dc


Documentation

I opened up the project and while project work -- css is locked and can't expand to larger size or adjust -- looking at document all I seem to be able to find does not give me control over the css -- could you kindly point me to this

@rmasonhx12 you can now edit the CSS properties or the tailwind classes with the latest release (v3). When you setup it up either edit the CSS in the DevTools or edit the template file directly which now uses HTML.


extracted some code from CppCheckInspection to CppCheckInspectionImpl…

… / some cleanups
Some minor refactoring and cleanups in preparation of making the actual implementation testable as well as having the inspection hook separate from the actual work.

@firewave This refactor looks good to me. Anything else you wanted in this PR or are you ready for it to be merged?

No, not for now. After the XML stuff I will try to incorporate the GitHub template so there's working CI and afterwards I will do changes for more abstraction and in preparation of having unit tests.

I see you already submitted a 1.5.1. There's no date in the README.md yet and no tag for it.


Add Shreyas Minocha’s wiki

@shreyasminocha
The link: https://🧠.shreyasminocha.me = https://🧠.shreyasminocha.me/ seems to be broken. Should it instead link to https://wiki.shreyasminocha.me/ ?

Oh no, is that so? I set up a redirect to https://wiki.shreyasminocha.me, but it seems to be broken. Let me edit the link 😅

Thank you! btw nice wiki!


Where VSCode save the selected theme

is there any place where visual studio code set the current theme in file ? so i can retrieve it from there.

This is a good write-up. However, as you can see the structure is being reconsidered and it's not consider API at this point.
Does your extension want to know the theme? If so, in way is it using for? I'm asking since for example we already pass in theme marker classes into the html preview command. I.e. content presented in the html preview can find out in which theme its presented.  If that's not sufficient, pls file a feature request requesting and API for extensions to retrieve the current theme.


Fix that Syncer could miss the first update.

Golang API for etcdv2 differs from Python one, expects the current index, rather than the next.

LGTM


Item 7 - Automating Systrace with MonkeyRunner fails

FYI:Running the test on Windows 10
Your command:   gradlew :app:assembleDebug :app:assembleDebugAndroidTest   ...
I think list an incorrect task, :app:assembleDebugAndroidTest.
Should be:  gradlew :app:assembleDebug :app:assembleAndroidTest  ....

No, your suggestion is wrong - tasks are generated in every possible flavor, including the existrence of assembleDebugAndroidTest , which compiles the test app destined to work with the debug app, compiled with assembleDebug. Meanwhile assembleAndroidTest I believe is supposed to compile the test app in all flavors, not just the one you really need.


test: add harness for GioMenuSelector

Issue
N.A.
Description
Add harness on GioMenuSelector component

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Gravitee.io Automatic Deployment
A prerelease version of this package has been published! 🚀
To use it in your project run the following lines:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:tada: This PR is included in version 4.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: allow uring builder to customize flags/features

Currently, users cannot directly customize the flags and params of the uring builder, and with the rapid iteration of io_uring in the kernel, many new features will not be compatible with existing applications. So we need to provide more flexibility in the uring builder to allow customization of flags and params.

I don't think this is as useful as you might think, since many setup are not enough to just change .flags, and it doesn't make sense to change .features.

As an example, when I wanted to add the FEAT_FAST_POLL feature, there was no way I could add it to the original code.

You may have misunderstood the feature field, it is not a parameter that you need to set, but you can use this field to check if the currently used kernel supports fast poll feature.

Thanks for the heads up, have verified that I did misunderstand here.


test: add Widget tests for slide templates

Description
Add widget tests for the available slide templates. These tests should check whether the defined slide elements are visible. Also, they should test different slide configuration values (e.g. header and footer visible, custom background set, etc.).
Requirements

[ ] There is no drop in test coverage.

Hello! I would like to work on this issue.

Hey, sure, enjoy! 🤓

@bryanoli I cannot find you on any social media. Could you reach out to me on X or LinkedIn so that we can arrange the delivery of your prize?

Hey @mkobuolys. My social on LinkedIn is https://www.linkedin.com/in/bryanoli/
I cannot message you directly due to not having premium subscription.


inaccurate image

Bro it's too slow and inaccurate please make little bit faster and accurate with the prompt. I have tested 2 AI which generates Text to image with same prompt brain_fusion sometimes give inaccurate image and also please increase the height and width because it's crop's the image.

Bro it's too slow and inaccurate please make little bit faster and accurate with the prompt. I have tested 2 AI which generates Text to image with same prompt brain_fusion sometimes give inaccurate image and also please increase the height and width because it's crop's the image.
1 - Sometimes it is slow if the server is under a lot of pressure from the people who make the images
2 - The more words, the higher accuracy of the images
3 - The height and the width are both  = 764px so i cant increase that . but i will create another package to scale images soon .
if this help you . tell me to close the issue

@dj-yacine-flutter I'll wait for another package thanks

@dj-yacine-flutter okay get it


[local_auth] MainActivity.kt: (11, 48): Type mismatch: inferred type is FlutterEngine but PluginRegistry! was expected

I'm using local_auth: ^ 0.6.3 + 4 and I got this error:
error using biometric auth: PlatformException(no_fragment_activity, local_auth plugin requires activity to be a FragmentActivity., null, null)
I've tried the solutions from https://github.com/flutter/flutter/issues/33429 (see below), but none of them seem to work.
I get this new error when building the application:
MainActivity.kt: (11, 48): Type mismatch: inferred type is FlutterEngine but PluginRegistry! was expected

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugKotlin'.

Solutions tried:
package ...

import androidx.annotation.NonNull
//import io.flutter.embedding.android.FlutterActivity
import io.flutter.embedding.android.FlutterFragmentActivity
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.plugins.GeneratedPluginRegistrant

class MainActivity: FlutterFragmentActivity() {
    override fun configureFlutterEngine(@NonNull flutterEngine: FlutterEngine) {
        GeneratedPluginRegistrant.registerWith(flutterEngine)
    }
}

and also this:
package ...

import android.os.Bundle;
import io.flutter.app.FlutterFragmentActivity;
import io.flutter.plugins.GeneratedPluginRegistrant;

public class MainActivity extends FlutterFragmentActivity {
  @Override
  protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    GeneratedPluginRegistrant.registerWith(this);
  }
}

@alecsam
I tried the official local_auth plugin example on latest stable which compiled and ran properly.

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.4 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 1aafb3a8b9 (4 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (1 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86 • Android 11
      (API 30) (emulator)

• No issues found!

Can you check the plugin example and see if you've correct setup ?
If issue persists, please provide flutter doctor -v and a minimal complete reproducible code sample.

I checked it out and it worked for me too.
The difference between my code and the code in the example is MainActivity: mine is MainActivity.kt, and the one in the example is MainActivity.java.
Mine MainActivity.kt was (before I tried the exemples above):
package ...

import android.os.Bundle

import io.flutter.app.FlutterActivity
import io.flutter.plugins.GeneratedPluginRegistrant

class MainActivity: FlutterActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    GeneratedPluginRegistrant.registerWith(this)
  }
}

And MainActivity.java is:
package io.flutter.plugins.localauthexample;

import android.os.Bundle;
import io.flutter.app.FlutterFragmentActivity;
import io.flutter.plugins.GeneratedPluginRegistrant;

public class MainActivity extends FlutterFragmentActivity {
  @Override
  protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    GeneratedPluginRegistrant.registerWith(this);
  }
}

The code is the same because I used the one in the example.

$ flutter doctor -v
[√] Flutter (Channel stable, 1.22.0, on Microsoft Windows [Version 10.0.19041.630], locale en-US)
    • Flutter version 1.22.0 at D:\Flutter\flutter
    • Framework revision d408d302e2 (2 months ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0

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

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code, 64-bit edition (version 1.51.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.16.0

[√] Connected device (1 available)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

@alecsam
Check out this issue comment and see if it helps.

Thank you for your answer.
Unfortunately it doesn't work. I get the same error:
MainActivity.kt: (10, 48): Type mismatch: inferred type is FlutterEngine but PluginRegistry! was expected as https://github.com/flutter/flutter/issues/47095#issuecomment-568022889
I'm attaching an image to the source tree of the project, maybe there's something wrong here (?)

@alecsam
Check out various solutions mentioned in this issue and see if it helps.

Verified and issue replicable if on latest stable.
Steps to replicate:

Use local_auth plugin example's main.dart.
In MainActivity.kt, add below:

import android.os.Bundle
import io.flutter.app.FlutterActivity
import io.flutter.plugins.GeneratedPluginRegistrant

class MainActivity: FlutterActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        GeneratedPluginRegistrant.registerWith(this)
    }
}

Compile, which throws below error:

e: /Users/dhs/Documents/NCFlutter/test_app/android/app/src/main/kotlin/com/example/test_app/MainActivity.kt: (11, 48): Type mismatch: inferred type is MainActivity but FlutterEngine was expected

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugKotlin'.
> Compilation error. See log for more details

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 26s
Exception: Gradle task assembleDebug failed with exit code 1

The same code works with MainActivity.java but fails with MainActivity.kt.

flutter doctor -v

[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.5 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision<PHONE_NUMBER> (3 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • SM A260G (mobile)                   • 5200763ebcfa861f
      • android-arm • Android 8.1.0 (API 27)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

So do you suggest deleting MainActivity.kt and creating MainActivity.java with the code above?

Do you have any updates?

Do you have any updates?

@xster I'm still ramping up on the Android side of plugins, but it looks like this is an issue with v1 embedding that's specific to Kotlin? Does this indicate an issue with the v1 support in local_auth, or do we no longer expect this to work?

Didn't look too deeply, but the error seems a bit like there's some mix and matching of v1 and v2 Android embedding usage (not an issue with the plugin).
If your app is mainly using v1 embedding APIs (and you should upgrade :) http://flutter.dev/go/android-project-migration), then your AndroidManifest.xml shouldn't contain
<meta-data
    android:name="flutterEmbedding"
    android:value="2" />

and you should import io.flutter.app.FlutterActivity.
Otherwise, if you're using v2 embeddings, your AndroidManifest.xml should have the above tag and you should be using import io.flutter.embedding.android.FlutterActivity (or one of the sibling UI components).
Depending on whether you have the tag or not in the AndroidManifest, Flutter tools will generate the GeneratedPluginRegistrant class with the expectation that you'll call it with a PluginRegistry (if you're using v1 embeddings) or a FlutterEngine (if you're using v2 embeddings).
It's not related to Java/Kotlin.

Sounds like this is a local configuration error then, so closing.
If you can reproduce with a project that you believe meets the structure explained above, please post a link to a full sample project shouting the issue.

To be clear, it's possible that we have a bug with our tooling or engine. But we can't really tell without a reproducible project.


Keyword widgets (buttons) don't work

WARNING -  No such comm: 9fd5a99a5a4d4461bc533b0164f0087f

And nothing happens.
Need to bisect the ipywidgets / ipykernel version where this went broken. And fix.
This could be reproduced at https://mybinder.org/v2/gh/robots-from-jupyter/robotkernel/master?urlpath=lab/tree/example.ipynb

@datakurre any updates on this? We're kind of waiting for a new release that includes #144.

@sanderploegsma Unfortunately, this issue is still open.
I pushed https://pypi.org/project/robotkernel/1.7rc1/ from the current master for you. Please, open issues, if you find any.
Thank you for testing and patience :pray:


Testing data

Hi @soham97,
thanks for sharing this interesting work.
I have questions about the speech testing data for reproducing your results on the paper.

For the NISQA, can you share the list of the files you used for evaluations?
For the TTS, do you know where can I download the testing data you used from Evaluating Speech Synthesis by Training Recognizers on Synthetic Speech?
For the VMC2022, can you also share the lists of the files you used for evaluations?
For the  Noise suppression, can you also share the lists of the files (from DNS2021) you used for evaluations?

Hi @bigpon, thanks for trying out PAM! We released all the human annotation and data artifacts created for the paper here.

For NISQA, we use only simulated and live talk corpus and filter the ones will non-speech audio added from DNS. I'll share the file list in a .csv later
For the TTS testing data, you can use the LibriTTS subset from this paper "Evaluating Speech Synthesis by Training Recognizers on Synthetic Speech". The data can be downloaded from here. Please cite the original paper if you use the dataset
For the VMC2022 audio files, they can be downloaded from this Zenodo link. Additionally, this CSV file contains the audio file names along with their corresponding PAM score, MOS, MOSNet, and MOS-SSL
The DNS2021 files are from ICASSP 2021 Deep Noise Suppression Challenge. This dataset is not publicly available, so I recommend contacting the organizers or<EMAIL_ADDRESS>for data release questions. questions

Hope the above help!