NameError on Ruby 3.1 breaks error matching

Subject of the issue
The introduction of error highlight behavior in Ruby 3.1 for NameError causes the raise_error(message) and raise_error.with_message(message) matchers to fail on NameErrors.
This has a wide impact on the ecosystem, causing CI to fail for a number of repos when using Ruby 3.1.0.  That includes rspec-expectations own CI run.  Getting some sort of solution out for this quickly will make it much easier to add Ruby 3.1 as an option in the ecosystem.
It should be noted that the original message is preserved by syntax highlighting and can be accessed via the original_message method.  A somewhat hacky solution may be to introduce a method like
def actual_error_message
  return nil unless @actual_error

  @actual_error.respond_to?(:original_message) ? @actual_error.original_message : @actual_error.message
end

and replace the use of @actual_error.message in RaiseError with this method call.
Your environment

Ruby version: Ruby 3.1.0
rspec-expectations version:  3.10.1

Steps to reproduce
Failing cases can be found in the rspec-expectations test suite.  The simplest to reproduce is:

Create a single spec file with the following content:

RSpec.describe "expect { ... }.to raise_error(message)" do
  it "passes if a NameError is raised with the expected message" do
    expect { raise NameError.new('blah') }.to raise_error('blah')
  end
end

Run this spec file under rspec with Ruby 3.0.  It passes.
Switch to Ruby 3.1.0
Run the spec again, and it fails

Expected behavior
NameErrors initialized with the expected message should pass the matcher (raise_error(message), raise_error.with_message(message)).
Actual behavior
NameErrors initialized with the expected message fail the matcher (raise_error(message), raise_error.with_message(message)).

That sounds like a major compatibility issue. I regret we didn't build against ruby-head before.

Ruby 3.1
CI to fail ... rspec-expectations own CI run

But how, we don't have 3.1 in our build matrix, do we?
Is this the raise_error to blame?
Can you please send a PR with a failing example? If it's failing our build, a PR to add Ruby 3.1 to the build matrix is sufficient.
We'll surely do what we can to make RSpec compatible with Ruby 3.1. However, please consider that we are volunteers, and presently we have quite a lot on our plate. If you could invest time into the fix, this is very much appreciated.

@pirj Of course.  Your efforts are appreciated.  And I'm happy to help.
I've got a failing build against my fork of the repo and am working on a fix.  I'm running into a few other build failures, mostly against older Rubies (e.g. 2.1) running on Windows because of a failure to load something called ansicon.
I should have a PR up today, although it may not be green against these older Rubies.

First of all, my bad. We do, indeed, test against ruby-head. It's just that we allow failures of this build job. We should have made the build mandatory and prepared for Ruby 3.1 release in advance. This is our miss.
Please disregard CI failures on older builds, it's an evergoing struggle - things break here and there without any changes on our side. Do not bother fixing anything that you have not broken.
What I suggest doing:

keep ruby-head build as is, as it track the ongoing development of Ruby 3.2
add Ruby 3.1 to the matrix (without allow_failure)
research raise_error failure and attempt to fix it on Ruby 3.1

We'll provide guidance and feedback as needed. And thanks for volunteering to fixing this issue. I hope it's the only one on the road to compatibility with Ruby 3.1.

So this turned out to be more complicated that I thought, so I'm going to break it into two separate issues:

NameError on Ruby 3.1 breaks error matching.
Rails 3.1 in CI

This issue will track #1.  I'll open #2 in a separate issue.
I got confused, and while I was seeing the NameError issue locally I DID NOT see it in rspec-expectations CI.  I'm virtually certain I saw it in a CI run for at least one other repo, but I need to track that down.
I can reliably reproduce the issue locally in this environment - MacBook Pro w/Monterey (12.1) running Rubies installed with rbenv.  To reproduce:

Check out the rspec-expectations repo
Install Ruby 3.1.0 using rbenv and select it as the active Ruby
Run bundle
Run bundle exec rspec spec/rspec/matchers/built_in/raise_error_spec.rb
Specs fail because of the additional text in the error message

By setting a RUBYOPT value I can make the specs green

Now run RUBYOPT="--disable-error_highlight" bundle exec rspec spec/rspec/matchers/built_in/raise_error_spec.rb
Specs will pass

I'm not sure why error highlighting isn't being enabled in the CI environment for rspec-expectations, but this is definitely an observable failure locally.
I have a fix for it that doesn't require the user to set the RUBYOPT value.  That PR is in draft and I'm doing some rebasing and tweaking.  Will link here when it's ready.

Here's the PR with the changes that fix the raise_error_spec.rb run referenced in my previous comment - https://github.com/rspec/rspec-expectations/pull/1339

As a note, I just ran into this when I tried to add Ruby 3.1 to the factory_bot CI matrix.  In CI we're seeing a failure that's due to this issue.

Closed in #1339


warning: possible EventEmitter memory leak detected

I am using factor-bundle with watchify and gulp.
var gulp = require('gulp');
var gutil = require('gulp-util');
var source = require('vinyl-source-stream');
var browserify = require('browserify');
var reactify = require('reactify');
var watchify = require('watchify');
var factor = require('factor-bundle');
var uglify = require('gulp-uglify');
var fs = require('fs');
var concat = require('concat-stream');
var file = require('gulp-file');

gulp.task('watch', bundle)

function bundle () {

  // react components
  var files = [
    '/path/to/file1.jsx',
    '/path/to/file2.jsx',
    '/path/to/file3.jsx'
  ];

  var bundler = watchify(browserify(watchify.args))

  bundler.add(files);
  bundler.add('./lib/api.js', {expose: 'api'});
  bundler.require('./lib/api.js', {expose: 'api'});
  bundler.transform('reactify');
  bundler.on('update', rebundle);

  function rebundle() {
    bundler.plugin('factor-bundle', {
        outputs: [
          write('/path/to/file1.js'),
          write('/path/to/file2.js'),
          write('/path/to/file3.js'),
          ]
    });
    bundler.bundle()
        .on('error', gutil.log.bind(gutil, 'Browserify Error'))
        .pipe(write('shared.js'));
  };

  return rebundle();
}

function write (name) {
    return concat(function (content) {
        // create new vinyl file from content and use the basename of the
        // filepath in scope as its basename.
        return file(name, content, { src: true })
        // uglify content
        .pipe(uglify())
        // write content to build directory
        .pipe(gulp.dest('./public/bundles/'))
    });
}

It works fine but after five or ten rebundles I start seeing the following warning:
Trace
    at Browserify.addListener (events.js:179:15)
    at f (/Users/benoit/git/figure/web/node_modules/factor-bundle/index.js:55:7)
    at Browserify.plugin (/Users/benoit/git/figure/web/node_modules/browserify/index.js:345:9)
    at Browserify.bundle (/Users/benoit/git/figure/web/gulpfile.js:46:13)
    at Browserify.emit (events.js:107:17)
    at null._onTimeout (/Users/benoit/git/figure/web/node_modules/watchify/index.js:126:15)
    at Timer.listOnTimeout (timers.js:110:15)
(node) warning: possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at ConcatStream.addListener (events.js:179:15)
    at ConcatStream.once (events.js:204:8)
    at Labeled.Readable.pipe (/Users/benoit/git/figure/web/node_modules/factor-bundle/node_modules/labeled-stream-splicer/node_modules/stream-splicer/node_modules/readable-stream/lib/_stream_readable.js:612:8)
    at /Users/benoit/git/figure/web/node_modules/factor-bundle/index.js:73:43
    at Array.reduce (native)
    at Transform._flush (/Users/benoit/git/figure/web/node_modules/factor-bundle/index.js:65:35)
    at Transform.<anonymous> (/Users/benoit/git/figure/web/node_modules/factor-bundle/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:135:12)
    at Transform.g (events.js:199:16)
    at Transform.emit (events.js:129:20)
    at finishMaybe (/Users/benoit/git/figure/web/node_modules/factor-bundle/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:371:12)
    at endWritable (/Users/benoit/git/figure/web/node_modules/factor-bundle/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:378:3)
    at Transform.Writable.end (/Users/benoit/git/figure/web/node_modules/factor-bundle/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:356:5)
(node) warning: possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit.

+1

Yeah, this is for real. Every time the plugin is called the addHooks event listener is attached to Browserify. As you can see in this illustration
 [ [Function: collect],
  [Function: reset],
  [Function],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks],
  [Function: addHooks] ]

Just add: bundler.on('reset', function () { gutil.log(bundler.listeners('reset')); });, to see the results yourself. I'm guessing this probably leads to the excessive listeners on ConcatStream.

@benoitguigal to fix this do this to your rebundle function:
  var outputs;
  bundler.plugin('factor-bundle', {
    outputs: outputs
  });
  function rebundle() {
    outputs = files.map(function (file) {
      var name = path.basename(file, '.jsx');
      return write("./" + name + '.js');
    });

    bundler.bundle()
    .on('error', gutil.log.bind(gutil, 'Browserify Error'))
    .pipe(write('shared.js'));
  }

And please give me that bounty on SO :smiley:

This seems like a real bug, looking into it. addHooks should only be added once, you can see it's the saem logic as in watchify: https://github.com/substack/watchify/blob/e20c9a39fad48f411b2dc48a1d784a947bb8fb9e/index.js#L59-L60

So my SO solution doesn't work right. Luckily I have another solution in the interim until a PR is made.
Functions have a name property in ECMA6 which Node 12 also has.
So try this: Go here and change
b.on('reset', addHooks);
to
b.once('reset', addHooks);

Thanks Freyert, I will give it a try :-)

Cheeeers, has fixed for me

BTW @benoitguigal  and @neilcarpenter nice sites/projects.

Haha thanks!! :) And yeah, ditto to @benoitguigal

+1, is there still no PR for this?

+1

this seems to be an issue still with 2.5.0 on Mac OSX
browserify ./client/src/app/*.js -p  [ factor-bundle  -o 'uglifyjs -cm > ./client/dist/js/`basename $FILE`' ] -o ./client/dist/js/common.js

This is still a problem I have whenever I attempt to run grunt-karma
Running "karma:ci" (karma) task
(node) warning: possible EventEmitter memory leak detected. 11 bundled listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at Browserify.addListener (events.js:179:15)
    at Browserify.once (events.js:204:8)
    at deferredBundle (/Users/user/Documents/feed/node_modules/karma-bro/lib/bro.js:183:11)
    at Browserify.w.bundleFile (/Users/user/Documents/feed/node_modules/karma-bro/lib/bro.js:243:7)
    at /Users/user/Documents/feed/node_modules/karma-bro/lib/bro.js:269:9
    at nextPreprocessor (/Users/user/Documents/feed/node_modules/karma/lib/preprocessor.js:48:28)
    at /Users/user/Documents/feed/node_modules/karma/lib/preprocessor.js:86:7
    at evalmachine.<anonymous>:334:14
    at /Users/user/Documents/feed/node_modules/karma/node_modules/graceful-fs/graceful-fs.js:102:5
    at FSReqWrap.oncomplete (evalmachine.<anonymous>:95:15)
Injecting Rewireify into modules

I defined my browserify + watchify task exacly as here and got this problem as well.
(node) warning: possible EventEmitter memory leak detected. 11 reset listeners added. Use emitter.setMaxListeners() to increase limit.

Why this has not been fixed yet?

I used this ugly workaround, since I was not able to extract the plugin outside rebundle function
**
 * fixes possible EventEmitter memory leak detected: https://github.com/substack/factor-bundle/issues/64
 * @param {Browserify.BrowserifyObject} bundler
 */
function fixFactorBundleMemoryLeak(bundler) {
  var listeners = bundler.listeners("reset").filter(l => l.name === "addHooks");
  for (var i = 0; i < listeners.length - 1; i++) { //remove "reset"" listeners except last
    bundler.removeListener('reset', listeners[i]);
  }
}


useStorage for userLogin form values not long work correctly

Hi, there is a problem with usage of localStorage for store the userLogin form values (email and password) in the Login.vue (https://github.com/faisalfjri/breeze-vue-api/blob/master/src/pages/auth/Login.vue) page.
Since version https://github.com/vueuse/vueuse/releases/tag/v9.3.1 of vueuse the usage of localStorage with useStorage not long work correctly.
Problem
The localStorage not sync correctly against userLogin form values in the Login page . The localStorage is synced only one time on first typing in one of the TextInput component.
Any suggestion?

Hi guys, any news?

hi @alvarofvr, commit #62e1c12 for your problem, I've updated dependencies and fixed login

hi @alvarofvr, commit #62e1c12 for your problem, I've updated dependencies and fixed login

Hi @faisalfjri thank you so much, can you explain the resolution, i'm new in Vue / Pinia and i need some words.


Add username to gyro add example in README

As of #28 the add command seems to require a username before the repository name as otherwise it throws an error saying it expected a '/'. This PR adds the username to the README example.

Oh thank you for that catch! I missed that when I made users part of the packaging system.
One correction though: hejsil => Hejsil
Thanks!

@mattnite Thanks for merging :)


Question  about running mod

Hello,
Thanks for library, i used attiny85 and programmer avrisp i succesfully burned chip (with no bootloader) and 8Mhz internal clock but after installation i cant run original PAL game, my system is SCPH-101 with PM-41 (2) board it is also NTSC-U console
Question is :

Can we still run original games after chip?
Will PAL games work after the chip on NTSC console?
Is burning fuses on attiny really necessary before uploading code via arduino IDE? (I didnt do this part)

Hello,
Overall the answer is yes to all three questions, for the fuses if you
install the Arduino bootloader, and then you burn the program again the
fuses remain.
But normally on SCP-101, you have to run the bios patch, which is not
really possible on ATtiny85.
Sorry
Le dim. 10 sept. 2023 à 20:28, Armin Salčin @.***> a
écrit :

Hello,
Thanks for library, i used attiny85 and programmer avrisp i succesfully
burned chip (with no bootloader) and 8Mhz internal clock but after
installation i cant run original PAL game, my system is SCPH-101 with PM-41
(2) board.
Question is :

Can we still run original games after chip?
Will PAL games work after the chip on NTSC console?
Is burning fuses on attiny really necessary before uploading code
via arduino IDE? (I didnt do this part)

—
Reply to this email directly, view it on GitHub
https://github.com/kalymos/PsNee/issues/45, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDOKBGPTBKV42F3TD3FTMDXZYBEBANCNFSM6AAAAAA4SK4F4Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for the quick answer, i got confused by the bios patch here It says only if you have PAL SCP-101 to do bios patch, I will try with Arduino pro mini definitely to move out of probably mistakes with burning fuses.


Feature/attendances

Checklist for your PR

[ ] please start with a draft PR and mark it as ready for review when you are confident that your implementation works as expected.
[ ] add a changelog entry in CHANGELOG.md with a link to this PR.
[ ] make sure that all tests pass and add new test functions if your code is not covered by existing tests. Please use mock tests when network requests are required.
[ ] let someone review & approve your code, make changes where necessary.

Hints

name your branches accordingly: use the prefixes bugfix/, feature/, or release/ and then a short title for your PR in kebab-case (lowercase words separated with dashes), e.g. feature/my-awesome-feature.
Please make sure that pre-commit hooks are enabled on your system to avoid common mistakes before you make a commit.
feel free to delete this template and replace it with your own description of the PR.

Codecov Report
Patch coverage: 88.00% and project coverage change: +0.66 :tada:

Comparison is base (3cd11f6) 86.71% compared to head (d3c32bd) 87.37%.

: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
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
+ Coverage   86.71%   87.37%   +0.66%
==========================================
  Files           7        7
  Lines         843      895      +52
==========================================
+ Hits          731      782      +51
- Misses        112      113       +1

Impacted Files
Coverage Δ

src/personio_py/models.py
90.49% <85.00%> (+0.61%)
:arrow_up:

src/personio_py/client.py
81.81% <88.88%> (+2.35%)
:arrow_up:

src/personio_py/version.py
100.00% <100.00%> (ø)

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

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


Dont re-encode heic to heif

Is your feature request related to a problem? Please describe.
Heif is the container, heic is the image format, effectively .heic is heif
Describe the solution you'd like
When someone switches them, just apply the file extention change when saving / sharing. No need to re-encode. This would do a couple time and battery savings, efficiency is epic
Describe alternatives you've considered
Using jpeg xl

This is impossible using current implementation

Nope, only if i use convertion between files


Query Builder method count_all_results() could fail if an GROUP BY condition is used.

Query Builder method count_all_results() could fail if an ORDER BY condition is used. The number of results is the number of first group instead of the number of the the result after grouping.

My CI version is 3.0.2, and as has been fixed in new release, I closed this issue.


Multi-allelic sites

Hello,
I have tried using Echtvar to annotate with some genome-wide scores such as CADD or regBase. These have a score for all possible variants in the genome, so for each position there is one REF and 3 ALT alleles. If the 3 ALT alleles are collapsed in one VCF record in the annotation file, then Echtvar will only annotate variants from query file if it matches the first of the 3 alleles.
Example of collapsed variant:
22      16055959        .       G       A,C,T   .       .       REG=0.11765,0.0974135,0.134254;
In this case, Echtvar would only annotate G>A variants. G>C or G>T will get missing value.

yes, you'll have to decompose the VCF first.
I'll make this an error so you don't build without knowing.
Thanks for continuing to report these usability issues.

exactly, all VCFs seen by echtvar should be decomposed and normalized. I will update the README with this and add checks.

I'll open this till I commit the fix.


Fix rendering issue of namespace/name in gep-713

namespace/name currently just renders to "/"

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Does this PR introduce a user-facing change?:
NONE

Thanks!
/ok-to-test
/lgtm
/approve


Missing OpenVINO's and EdgeX's license and copyright

This repo is missing OpenVINO's and EdgeX's licenses and the appropriate copyright notice.
The dockerfile also needs to include OpenVINO's license.

Could we added the openvino's licensing folder to edgex-openvino-object-detection folder?
https://github.com/openvinotoolkit/openvino/blob/master/licensing/third-party-programs.txt

YOLO model's license: https://docs.openvino.ai/latest/omz_models_model_yolo_v2_tiny_tf.html#legal-information

Added by #9 and 595c879ac70c924b3042fef0e49ccc543c2aa431.


chore: parameterize status reporting environment variable

What type of PR is this?
Add status reporting enable parameter to the template referenced by app-interface saas file
What this PR does / why we need it?
Conditionally enable status reporting in different ocm environments.
Which Jira/Github issue(s) this PR fixes?
Fixes #
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make go-test command locally to run all the unit tests and mock tests locally.
[ ] Included documentation changes with PR

/test operator-e2e

/retest

/retest

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.01%. Comparing base (cb114d2) to head (9a13712).
Report is 5 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #625       +/-   ##
===========================================
- Coverage   72.53%   60.01%   -12.53%
===========================================
  Files          51       62       +11
  Lines        3350     4049      +699
===========================================
  Hits         2430     2430
- Misses        773     1472      +699
  Partials      147      147

see 11 files with indirect coverage changes


Implement rules

Pull Request Test Coverage Report for Build 69

40 of 41 (97.56%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 96.552%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/rules.jl
21
22
95.45%

Totals

Change from base Build 59:
0.7%

Covered Lines:
84

Relevant Lines:
87

💛  - Coveralls

Codecov Report

Merging #7 into master will increase coverage by 0.71%.
The diff coverage is 97.61%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
+ Coverage   95.83%   96.55%   +0.71%
==========================================
  Files           4        5       +1
  Lines          48       87      +39
==========================================
+ Hits           46       84      +38
- Misses          2        3       +1

Impacted Files
Coverage Δ

src/SymReduce.jl
100% <100%> (ø)
:arrow_up:

src/patterns/Patterns.jl
100% <100%> (ø)
:arrow_up:

src/patterns/unify.jl
100% <100%> (ø)
:arrow_up:

src/rules.jl
95.65% <95.65%> (ø)

src/patterns/types.jl
88.88% <0%> (+1.38%)
: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 449361d...b2e1956. Read the comment docs.


Will littfs support compression in the future？

Interesting you ask this because I was looking into this quite recently.
In the general case, I don't think so. Compression requires significant (for a microcontroller) RAM, and this is sort of a dead end for littlefs. Though if you happen to come across any constant-RAM compression algorithms let me know.
Compression lets you trade off some RAM and processing power for lower disk usage, but for littlefs we usually want the tradeoff to go the other way. Flash storage is cheap, so if you can use more storage to decrease RAM consumption/performance, you can get a smaller/cheaper MCU.

That being said, I think it would be really interesting to look at pre-compressed littlefs images, That is, allowing you to compress littlefs offline, such as at compile-time, and then mount/decompress littlefs at run-time.
I think this would be very useful for read-only images such as those used in bootloaders, and focusing on decompression would be a much easier problem.

@geky Take a look at lz4 compression, it has a constant RAM compression, and high performance for microcontrollers. Mbed has an example in their mbed cloud project:
https://github.com/PelionIoT/mbed-cloud-client/blob/master/update-client-hub/delta-tool-internal/source/lz4.c

Another possible implementation for compression could be on the route of heatshrink, which was developed with low/constant memory consumption in mind; n particular for low-end MCUs. Compression somewhat depends on how much RAM you allocate for it, but with even low settings the used LZS implementation works quite well.
Remains the question: Which parts of LFS could best be compressed. While there's the possibility to compress simple images like squashfs does, there's also the possibility to allow for compression of attributes/metadata or inline file contents. Both with metadata and inline file contents things should be accessible with the usual API.
Also given you mentioned low RAM consumption: You thus likely should avoid compressing the actual directory structure; especially as this might cause quite a bit of additional processing required to find information when (compressed) directories have to be scanned repeatedly for information.

Circling back on this a bit, there are some upcoming changes to the file structure that I think make compression quite a bit easier to implement, so it would be interesting to revisit this in the future.

@geky Take a look at lz4 compression, it has a constant RAM compression

Another possible implementation for compression could be on the route of heatshrink

Thanks @felipeLeast, @BenBE. I made a mistake in thinking there were no constant-RAM compression algorithms. Though my understanding is there is a performance cliff where having a too small amount of RAM ends up compressing poorly. That combined with needing to match encoder/decoder dictionaries creates some annoying questions around how much RAM you need for portability.
I think the most complicated part will be how the compression configuration (which algo, dict size, etc) is stored. Simply storing the configuration per-file and failing to read when an algo/RAM is not available is one option.

Also given you mentioned low RAM consumption: You thus likely should avoid compressing the actual directory structure; especially as this might cause quite a bit of additional processing required to find information when (compressed) directories have to be scanned repeatedly for information.

Hmmm, I've only been thinking of compressing file data, which is a much simpler problem. Compressing metadata would be quite a bit more complicated, though not impossible... Especially since metadata is all append-only logs... 🤔
This paragraph could probably be an entire research project.

Remains the question: Which parts of LFS could best be compressed. While there's the possibility to compress simple images like squashfs does, there's also the possibility to allow for compression of attributes/metadata or inline file contents. Both with metadata and inline file contents things should be accessible with the usual API.

Inline data is an interesting question, and will probably take some experimentation. But if you revert to uncompressed on failed compression I don't see a reason to not try compressing inline data. We usually think of inlined data as "small", but if you have a >=1 MiB block size, your inlined data is probably not "small".
For attributes it's a bit more questionable. My gut says the portability issues would not be worth the compression gains, especially since attributes are usually quite small, but my gut has been wrong before...

Interesting things to think about.


Allow dash inside jvmRoute

From<EMAIL_ADDRESS>on December 30, 2010 10:26:36
What steps will reproduce the problem?

Set jvm route in server.xml with dash (e.g. MYSERVER-T1, MYSERVER-T2)
Start two nodes
Go to app through apache httpd mod_jk cluster with stickysessions
Observe session-id assigned and it contains jvmRoute
Kill server in use
Reload page
Observe session-id changed completely, not only jvmRoute part

What is the expected output? What do you see instead?

Session failover - restoration of session on another node.

What version of the product are you using? On what operating system?

1.3.6

Please provide any additional information below.

Patch for this problem provided.
It is for jvmRoute to contain not only \w symbols
but dash also. Regular expression for jvmRoute changed to [a-zA-Z0-9-].

Attachment: memcached-session-manager-1.3.6-jvmRoute-dash.patch
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=69

From martin.grotzke on December 30, 2010 05:13:06
This is a duplicate of  issue #62 , see these commits:
https://github.com/magro/memcached-session-manager/commit/ee75536d
https://github.com/magro/memcached-session-manager/commit/49725e61

This is not yet released, you'd need to build the current master (I could also provide built jars).
Status: Duplicate
Mergedinto: 62

From martin.grotzke on January 27, 2011 14:36:22
(No comment was entered for this change.)
Labels: Milestone-1.4.0


KAFKA-9709: add a confirm when kafka-server-stop.sh find multiple kafka instances to kill

add a confirm when kafka-server-stop.sh find multiple kafka instances, avoid mistakenly kill all instance of this machine.

Thanks for the PR, @iamgd67.  This probably requires a KIP because it changes existing behavior.  Existing automation that relies on this script would break if the functionality is added as currently implemented in this PR, for example.  A KIP is the place to address this in an open proposal and discussion.

thans your review, @rondagostino . what about add a timeout like 5 seconds, if no user interaction, do kill all just as before.

@iamgd67 This is the type of discussion that would occur for a KIP.  Creating one is the way to go.

@rondagostino , create kip https://issues.apache.org/jira/browse/KAFKA-9709 and list some  workaround there, don't know will the PR and KIP auto connect to each other.

@iamgd67 Take a look at the instructions here.  You would add a link to this issue in the KIP document that you publish.


Output added to resourceGroup module.

Overview/Summary
Added outputs to make depends-on support better for sub modules deploying into the created resource group.
This PR fixes/adds/changes/removes
Support for using an output to make dependencies in bicep file.
Breaking Changes
None
Testing Evidence
Only adds output to module, so tested it with a simple main bicep file.
Inputs:

Outputs:

As part of this Pull Request I have

[X] Checked for duplicate Pull Requests
[ ] Associated it with relevant ADO items
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Performed testing and provided evidence.
[X] Updated relevant and associated documentation.

Thanks @KiZach,
Out of interest how does this help as you cannot use the name or ID from an output of one module to pass into another module today as it creates a circular dependency as per:

Just want to understand before we look to merge this PR
Thanks
Jack

Hi @jtracey93
You are right, did some more tests and found why it was working on another Bicep project.
I used the CARML module https://github.com/Azure/ResourceModules/tree/main/arm/Microsoft.Resources/resourceGroups in another project, this has the outputs. And on this project the RG name was used as a param not scope to 'sub' modules for extracting the 'applicationname' that was part of the resource group name.
So I think this PR can be closed.


Add support for storage area onChanged event listeners

Aside from the onChanged events on the storage namespace, each storage
area (sync, local and managed) have their own onChanged event. This
event is tied to the area and as such, it has a different callback
function signature that only provides an object mapping with the
relevant StorageChange(s).
References:
https://developer.chrome.com/apps/storage#type-StorageArea
https://chromium.googlesource.com/chromium/src/+/master/extensions/common/api/storage.json#152

Realized just now that this seems to be Chrome specific thing and does not work with Firefox extensions for example. Is this something that's still relevant for this project? Otherwise this PR can be closed

Noticed just now that this seems to be a Chrome specific thing and does not work with Firefox extensions. Is this something that's still relevant for this project? Otherwise this PR can be closed

While we don't have any decent way to categorize these differences I don't see a reason we can't implement Chrome or Firefox only APIs.

Can someone look at this PR? Looking for the support this code would provide.

Can someone look at this PR? Looking for the support this code would provide.

rebasing but this likely requires a lot more attention


Add grid or flexbox to make it responsive

You can use "styles as props" via any component in Evergreen - so if you choose to make something display="grid" or display="flex", you can + should be able to do so.
Check out https://github.com/segmentio/ui-box  (which is what most of Evergreen is built on top of) for examples of how to set these styles. Let us know if you have any other questions!


UISlider inside Content view controller doesn't move smoothly

I'm facing a problem that I have a UISlider inside a UIScrollview in a UIViewController that is content view controller. It contains a UISlider, the uislider works normally on simulater. On physical device it doesn't work smoothly, I have to drag it from the very accurate center point which is quite annoying. When I try to view that UIViewController without using SidebarNavigation it works just fine as expected..
Any suggestion ?
-Update-
A repo that does reproduce the problem:
https://github.com/aproram/Xamarin-SideBarNavigation-UISlider-Issue-Demo

Nothing that I can think of. Have you tried disabling the slide functionality of the menu?

@jdehlin
SidebarController.DisablePanGesture is not accessible while using SidebarNavigation as a xamarin component..
May you tell me how to disable the slide functionality some other way?

Use the latest nuget version.


Latest repeatedly builds stale code

Details

Project URL: https://github.com/pypa/setuptools
Build URL (if applicable):
Read the Docs username (if applicable): jaraco

Per pypa/setuptools#604, I'm migrating the project to RTD as PyPI is dropping support for doc hosting. I've gotten access to the setuptools project, which was formerly configured for Mercurial (Bitbucket), which may be implicated in this issue.
After moving from Mercurial to Git, the project failed to build because it was missing dependencies, so I pushed this commit and reconfigured the project in RTD to use for docs/requirements.txt. The build failed, so I retried a couple of times manually building latest.
Excepted (erm, Expected) Result
As seen in the UI, latest should build the VCS default branch. In this case, it's a git repo and 'master' is configured as the default branch in Github. Therefore, it should build the aforementioned commit, which is in master.

Actual Result
Instead, the build failed:

I retried several times, but repeatedly got the same error.

it seems that after waiting a few minutes and triggering another latest build, it now got the latest commit:

So while I thought maybe it was an issue with having been a Mercurial project, because I saw default here:

Apparently the issue is only a lag between when commits are pushed and when they can be pulled. Is that by design?

It's happening again, now with https://github.com/pypa/setuptools/commit/8fea56035d22fc46e8237fa8f6b1b548fd0105d5. I'll keep repeatedly building until I get a different response and see if I can assess how long the stale builds continue.

Oh, this is interesting. It seems one build went back to a commit even older than the one that finally built before:

And again

How weird.

More than 6 minutes and RTD is still building pypa/setuptools@f12843c13

15 minutes and it's still building one of two older commits. I'm going to take a break from this effort for now.

Hours later, problem still exists.

I set the branch to the default, master, and that triggered a build, which grabbed the latest tip:

I'll take a look into this, it seems I might need to go in an clean out the old project commit history.

It seems the last build did in fact complete successfully without having to alter the out of date versions:
http://readthedocs.org/projects/setuptools/builds/4068321/
Does this seem resolved?

Yes, sort-of. It seems that setting the branch manually seems to have worked around the issue.

I suspect this is a matter of stale version/commit info. If it stops working, I can wipe the existing version and commit info from the project.

I'll remove the branch override and see if the issue re-emerges, in which case it's worth trying a wipe to see if the project can be restored to a state that behaves as expected.

Server Error

seems same as #2255

@jaraco I think this is related to #3913

Closing as a duplicate, and due to lack of activity.


Causes error if user model is different name from 'Users'

I'm trying to use CookieTokenAuth in some CakePHP3 project, where user data table is not users.
In Current implementation, though, users model is hard-coded, and specifying userModel doesn't work well.
// AuthTokensTable.php
public function initialize(array $config)
{
    $this->addBehavior('Timestamp');

    $this->belongsTo('Users');
}

// CookieTokenAuthenticate.php
$tokenEntity = $authTokens->findBySeries($series)->contain('Users')->first();

It caused the error, Error: [Cake\Database\Exception] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'project_name.users' doesn't exist.

The last line of CookieTokenAuthenticate#getUserFromCookieData is return $this->_findUser($user->username);, the property name 'username` is also hard coded.

Thanks for the issue report. I am quite busy right now, but I will have a look at this next week.

Thank you for your patience.
I have had a look at this issue. You seem to be using version 0.2.1 or older. I had not yet released a new version, though in the master branch custom configurations were supported already. I have now released this enhancement as version 0.3.0.
Testing, the resulting configuration with Members as the user model and nick as the username field works fine in version 0.3.0:
	$this->loadComponent('Auth', [
            'authenticate' => [
                'Beskhue/CookieTokenAuth.CookieToken' => [
                    'fields' => ['username' => 'nick'],
                    'userModel' => 'Members'
                ],
                'Form' => [
                    'fields' => ['username' => 'nick'],
                    'userModel' => 'Members'
                ],
            ]
	   ]);


update endpoint for support archives

Description
closes #5218
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

@matborowczyk  Do we still need the zip-building logic when using the new endpoint? Based on what Wouter told me, we might not need to care anymore and just trigger a download.

Can you also delete the old code related to generating the Zip and remove the JSZip dependencies? :D

Processing this pull request

Merged into branches master, iso6 in 745128759a549498a978008a70c36ecdba25a627


Clarify the explanation for while

The previous description (until some condition is met) makes it sound like the while body will loop until the while condition is true.

Makes sense! Thanks for the clarification @ellotheth


Create new DAOs for workflow, filesets, subscriptions

Real src code changes are:

a couple of DAOs added, so far used only by unit tests
another one just renamed

All the rest is unittests created for all WMSpec requests, such that we can test how workflow tasks, filesets and subscriptions get created on the agent side.
There is quite a few things still being printed, since I'll have to come back to all these tests later this week (once I push changes to StepChain). I'll then clean them up.

Needless to say, these tests are going to be a PITA to maintain. Hopefully we won't touch them again in the next 5 years or so (and will keep only StepChain/TaskChain + T0 specs)

@ticoann I already ran these tests on my oracle dev instance and everything looks fine.
Can you please review and merge it. I'll then rebase my stepchain branch and get over that long standing issue :-)


Question: Difficulty of support for SQL Operations Studio

Just wondering what it would take to allow this to support SQL Operations Studio via direct vsix installation.

I'm unaware of the SQL Operations Studio extensibility model. I have a feeling this won't work out of the box; it would be better to contact the SQL Operations Studio instead.


add host.os.type and system.diskio.io.time

Adds host.os.type field and system.diskio.io.time.  With the Host View I am thinking to switch to using host.os.type and we are currently using system.diskio.io.time.
https://www.elastic.co/guide/en/ecs/current/ecs-os.html#field-os-type
https://www.elastic.co/guide/en/beats/metricbeat/current/exported-fields-system.html#_diskio_4

Just for visibility, there is this PR in draft https://github.com/elastic/kibana/pull/140788
I wonder if maybe now would be a good time to invest into synthtrace for us instead? Specially in light of https://github.com/elastic/kibana/issues/139924

Happy to try that tool out but this is a pretty quick and easy change if someone would still like to use Slingshot.

@matschaffer Thanks for your comments.  Opened up this issue as you got me thinking about whether latency is calculated correctly.  https://github.com/elastic/kibana/issues/141982


[fix] add svelte field when packaging

Several heuristics in Kit/vite-plugin-svelte to tell Vite to mark Svelte packages rely on the "svelte" property. Vite/Rollup/Webpack plugin can all deal with it.
Fixes #1959
@dominikg @bluwy  I didn't quite follow through your discussion over at vite-plugin-svelte, but I think this change is needed for Svelte packages to properly get detected, right?
Before submitting the PR, please make sure you do the following

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

yes, thats right. the svelte field is relied upon. We should also make sure that exports contains
"./package.json":"./package.json", this is important for both rollup-plugin-svelte and vite-plugin-svelte to be able to read the svelte field.

yes, thats right. the svelte field is relied upon. We should also make sure that exports contains
"./package.json":"./package.json", this is important for both rollup-plugin-svelte and vite-plugin-svelte to be able to read the svelte field.

This is already the case 👍

actually the "svelte" field is only needed packages that export ".svelte" components. Utilities that come without any components, eg just some fancy store or context utility can still ship without a "svelte" field.
So maybe a warning to add it would be better, or somehow find out if any .svelte is exported?
Or is it implied that package is always used for ui, as utilities generally would not need to go through preprocess + compile ?

Yeah @dominikg's comment are spot on. The svelte field is used to workaround Vite's prebundling process, and is only needed if they export Svelte components. I don't think Kit reads the svelte field anymore though, the logic has been moved to vite-plugin-svelte.


jest-environment-miniflare doesn't seem to setup async_hooks

We have a project where we can do end-to-end tests with Miniflare and it works beautifully! Durable objects are doing their input gating, requests to other durable objects happen in order and in parallel.
When we run the same tests in the miniflare jest environment we get notices that we're not awaiting Promises (due to console.log calls in subsequent code). This is correct, but as we understand it is also the expected way to use Durable objects. Is there some way, from jest, to await the stack of network and storage calls before describing our expected outcomes?

Hey sorry, I just saw this! That's so helpful! I'll give this a whirl, but I'll pre-emptively close this to keep your queue quiet.


Restored the native profile for camel-quarkus-pdf integration tests

This test is running on my machine, so the first aim of this PR is to check whether the issue is present on CI.

ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/494/


feat: Add example Python stack for Step Functions

What does this PR do?
Add an example Python stack that creates and instruments a State Machine.

Motivation

Testing Guidelines
Deployed the stack, and the traces showed up in Datadog app.

Additional Notes

Types of Changes

[ ] Bug fix
[x] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

[x] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

/merge


how to add refrence assembly with new project-style

Hi @NaBian
after this commit
https://github.com/HandyOrg/HandyControl/commit/5861666e1bb43ed1c301a5f3867520ac9a4ffb86
i cant add this refrence for .Net Framework 4.5 and 4.0
i write this code in HandyControl_Net_GE45.csproj and HandyControl_Net_GE40.csproj
<Reference Include="System.Web.Extensions" />
but build fail with many errors that cant find assembly
before this commit everything worked fine
https://github.com/ghost1372/HandyControls/blob/8f671e85840586f338d75b9734b89de0536aefb2/src/Net_GE45/HandyControl_Net_GE45/HandyControl_Net_GE45.csproj#L158
If possible, help me add this reference
thanks

you may forget to reference system.web:
<ItemGroup>
    <Reference Include="System.Web" />
    <Reference Include="System.Web.Extensions" />
 </ItemGroup>

@NaBian  I added it but it didn't work
A strange error is displayed when writing using

It also looks like the .NET40 demo can't be compiled and failed with error

System.Web is not a part of net core, you can try to find alternatives

yes i know i checked env with ! (if is not core) anyway
i used NET40 || NET45 || NET462 || NET47 || NET48 instead of !NETCOREAPP3_0 and problem solved for now😀


ARROW-6509: [C++][Gandiva] Re-enable Gandiva JNI tests and fix Travis CI failure

@pitrou

Can you describe what was the issue?

Seems like the mimalloc allocator interacts badly with the JVM in some way.

@pprudhvi can you add the stack from the coredump (for the mimalloc case) in the jira ?


Pawel/add timezone timeformat

Description of the change

Adding timezone and time_format to project resource.
Updating project by name, timezone and time_format in place (no new resource on change)
Preserve backward compatibility - skip default timezone and time_format on read.

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Maintenance
[ ] New release

Checklists
Development

[x] Lint rules pass locally
[x] The code changed/added as part of this pull request has been covered with tests
[x] All tests related to the changed code pass in development

Code review

[ ] This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers assigned
[ ] Issue from task tracker has a link to this pull request
[ ] Changes have been reviewed by at least one other engineer

I only found one odd edge case, importing a project that was not created by Terraform resets the timezone/time format configuration to the default values. If fixing this would require other hacky solutions, I'd rather keep it as is.

Yes, as I stated before, there is no perfect solution to this. When we will try to import the project with default timezone and we want to set that timezone explicitly in the tf file then we will get :
  # rollbar_project.terraform_example will be updated in-place
  ~ resource "rollbar_project" "terraform_example" {
        id            = "644248"
        name          = "terraform_example"
      + time_format   = "12h"
      + timezone      = "US/Pacific"
        # (5 unchanged attributes hidden)
    }

as the tfstate file has these 2 variables set to null.
so we have 2 scenarios here:

read it as it is - it will fix the import, but after the upgrade to a new tf version just running terraform apply will try to update all the projects (even without additional changes from a user)
skip reading default values - problem with terraform import for default values in time_format and timezone vars, but terraform apply will not try to make any changes even after the upgrade to new tf version.

Which way is better ? Depends on a customer and situations. I cannot say that 2) is better than 1) all the time because it does not change the existing state of the terraform. Also, if we go with 1) a customer may choose not to upgrade now. But what will be in the future when a customer wants to get the next version ? Eventually, they will see some surprises.
We need to decide here, I am really fine with either way.

closing this for now


digest: Remove unnecessary scroll bar for private messages.

Testing Plan:
GIFs or Screenshots:

Thanks for fixing, merged, thanks @punchagan!


Successful installation/setup, unsuccessful login

After puppet have run, I go to the web page and login. It seems to accept my username/password, but I get:
HTTP ERROR 404

Problem accessing /j_acegi_security_check. Reason:

Not Found

Looking at a host where I installed Jenkins manually, I see that it have the ~jenkins/war directory (especially war/WEB-INF/security/SecurityFilters.groovy) while the puppet installed one doesn't have that war directory..

Try google.  Eg, https://stackoverflow.com/questions/9684320/jenkins-j-acegi-security-check#21078846
This sort of configuration issue is beyond the scope of the puppet module.


Deno support

Support running unsort on the deno runtime: https://deno.com/blog/dnt-oak

Solved in https://github.com/jwanner83/unsort/releases/tag/1.0.0-rc2


[WIP] Speaker ID - Updates on VoxCeleb speaker recognition recipe

So this PR is based on earlier discussion with many great people on current problems on scoring and computing metric stats for speechbrain, along with minor fix on buggy stuff when running. This PR aims for opening such discussion and related contributions by fixing some obvious ones.
Two problems are handled here first:

Score normalization. Well actually the implementation of speechbrain for that is not wrong. The problem lies in the algorithm themselves. There are three algorithms: z-norm, t-norm and s-norm. The latter two acquires test mean/std statistics, which may not be legitimate for voxceleb’s 1-to-1 trial list. But based on my testing, score normalization itself at least has trivial impact on the EER(%) performance and undramatic impact on DCF. Also, z-norm is valid to be applied here because it only aggregates enrollment statistics. But just to be safe, the default score normalization methods in param file is set to be 'none'.

Embedding normalization. This is accordingly more problematic because we aggregates mean/var statistics across the batch. This is essentially not legitimate because we are not supposed to aggregate diff. statistics across the utterance for 1-to-1 trial lists. This can be solved by either wiping out the normalization step in the code or set the batch size to 1 when doing the inference. I removed such embedding normalization step in the scripts.

The performance are shown here, along with the old statistics:

Model
Version
EER, minDCF

ECAPA-TDNN, cosine
Old
0.69%, 0.08258

ECAPA-TDNN, cosine
Updated
0.90%, 0.11045

TDNN, PLDA
Old
3.2%, -

TDNN, PLDA
Updated
3.23%, 0.34713

@mravanelli @anautsch There are also things which I would like to confirm:

I did not find any score normalization step in PLDA scoring, including base code. Is that correct?
Feature mean/std normalization. I assume this one is same as cepstral mean subtraction and variance normalization (CMVN) which is quite familiar to most speech processing folks. Is that correct or there are some batch-wise operations? (Although I do not think this is problematic for now)

We can update the statistics after approving and fixing all changed noted here, including README and hugging face READMEs. We then can move on to further discussion on optimization, as well as other speaker verification examples.

Thank you for this PR @underdogliu! I would encourage all the speaker recognition experts that would like to give a contribution to help with this PR. We would like the speaker recognition community to be happy with the baselines we propose, but we need your help to make sure this is the case.

Hi, starting from this branch, someone got this error in Avignon. That's weird, isn't Cyclic scheduler hooked properly?

I can try to replicate. Weird, everything was working in the past..
On Fri, Jun 24, 2022 at 2:58 AM Parcollet Titouan @.***>
wrote:

Hi, starting from this branch, someone got this error in Avignon. That's
weird, isn't Cyclic scheduler hooked properly?
[image: Capture d’écran 2022-06-24 à 08 57 50]
https://user-images.githubusercontent.com/11910731/175480422-7df0521c-5e18-43d3-aeb4-cb1482e00f4b.png
—
Reply to this email directly, view it on GitHub
https://github.com/speechbrain/speechbrain/pull/1439#issuecomment-1165265309,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA2ZVQMWEY3JYZQ4LCBS53VQVMB5ANCNFSM5YWJSBMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I solved the issue by just registering the Scheduler. Indeed, it is not registered (no decorator) in the code.

Could you please push this change?
On Fri, Jun 24, 2022 at 8:59 AM Parcollet Titouan @.***>
wrote:

I solved the issue by just registering the Scheduler. Indeed, it is not
registered (no decorator) in the code.
—
Reply to this email directly, view it on GitHub
https://github.com/speechbrain/speechbrain/pull/1439#issuecomment-1165550673,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA2ZVWLFUVPC4TT6SCZKDTVQWWKXANCNFSM5YWJSBMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for this PR @underdogliu!

As for the s-norm, it looks like it relies on a cohort-based on the training data only. I might miss something, but it looks correct to me, no?
In the current version, I left it activated, but we can rediscuss it off-line (and revise that in another PR). Meanwhile, I think we can merge it to make sure at least this fix is part of the upcoming release.


Local Navigation No Background When Sticky

When local nav becomes sticky, there is no background or background does not sticky with local nav.
Maybe corrected with @twhite313 update to local nav in header block. https://github.com/Esri/esri-eds/issues/341
http://localhost:3000/en-us/about/about-esri/overview

Also, variation on it  from Field Ops
https://main--esri-eds--esri.aem.live/en-us/capabilities/field-operations/overview

Looks to be resolved with recent updates.


mgmt, update test on elasticsan

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - elasticsan - mgmt - tests

/azp run java - elasticsan - mgmt - tests


C95241: replacing italic asterisks by underlines

Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
Description: Nested asterisks broke format in localized pages
@Rick-Anderson

Thanks @Rick-Anderson


Change file path patterns to support 1-level symlinks by default

While trying to use knapsack to run RSpec that is symlink-ed to a different directory, me and my team spent a fair amount of time trying to figure out why Knapsack wouldn't load our knapsack reports correctly.
After digging into the knapsack code, we found out that by default, the file path pattern provided by default does not follow symlinks.
I would like to propose that we support follow at least 1-level symlinks by default

:ok_hand: Thanks!


Refactored NetlistResources Controller

Problem Description

Fixes #226.
Solution
Replaces DAO usage with OpenDCS implementations.
how you tested the change
Unit testing of data mapping included.
Where the following done:

[ ] Tests. Check all that apply:

[x] Unit tests created or modified that run during ant test.
[ ] Integration tests created or modified that run during integration testing
(Formerly called regression tests.)
[ ] Test procedure descriptions for manual testing

[ ] Was relevant documentation updated?
[ ] Were relevant config element (e.g. XML data) updated as appropriate

If you aren't sure leave unchecked and we will help guide you to want needs changing where.

References getAll will need a new OpenDCS DAI method to support filtering by transport medium type


On-demand sampling CPU profiling

Initially proposed by @anuraaga and @imasahiro. We could integrate with a library like spf4j or something better and expose the UI in DocService to let a user toggle the profiler or browse the report.

https://github.com/flamegrapher/flamegrapher


Searching for numbers will throw an exception

Numbers might actually be found in some translations but generally searching for numbers is probably a user mistake and they meant to do a lookup. Regardless it shouldn't throw an exception.

Fixed by #11


Own dataset test.

Hi, thanks for your source code. Could you tell me how can I generate my own dataset？Use colmap or some others？Thank you！

yeah, you can calibrate the image with the COLMAP or other tools, after calibration you have the extrinsic and intrinsic and near-far , then you can convert it to the blender, llff or dtu format. This repo provides guidance from COLMAP to LLFF format.

Thanks very much. I'll close this issue.


New package: FixedPointNumerics v0.1.0

Registering package: FixedPointNumerics
Repository: https://github.com/tobyfarley/FixedPointNumerics.jl
Created by: @tobyfarley
Version: v0.1.0
Commit: b56ef1081848ebe328e83cc6c92dcbae6ac31a15
Reviewed by: @tobyfarley
Reference: https://github.com/tobyfarley/FixedPointNumerics.jl/commit/b56ef1081848ebe328e83cc6c92dcbae6ac31a15#commitcomment-148328337
Description: Type package for Julia that uses integers to store fixed point numbers

Closing in favor of https://github.com/JuliaRegistries/General/pull/118091
Please do not try to release new versions while the initial registration is pending.


Option to exclude folders

An option to exclude (multiple) folders would be nice, like "C:/Users". Not having an option like that would mean that it scans the same SharePoint for multiple users. Maybe the same option can be added to include multiple folders / drives instead of just one.

Merged into #26


Evaluate whether pysimdjson could be used in Rally

There are largely two areas where handling large chunks of JSON impacts performance in Rally:

Parsing the JSON source
Creating Python (dict) Objects from JSON

The simjson project seems to take advantage of modern SIMD vector instructions to achieve much higher performance than other libraries.
The pysimjson project beings those benefits to Python via bindings with prebuilt binary wheels for a lot of platforms. Additionally, it provides JSON pointers via at(), or proxies for objects and lists to reduce the creation of Python objects. We've been hitting these issues at various points e.g. in https://github.com/elastic/rally/pull/941 and https://github.com/elastic/rally/pull/935 (i.e. especially after using an async-io based load generator).
Given the benchmark results this could be a very useful library to use. Both projects use Apache 2.0 license.

I'm watching this issue - if you find any missing functionality or issues in pysimdjson that would block this, let me know and they'll be resolved.

While I don't have anything super useful to add here in terms of replacements, I would just like to throw my anecdotal hat into this ring with respect to the elastic/logs track I was trying to run against our new NVMe backed hot data tier on on-prem hardware within an ECE cluster.  The results I was getting scaling from targeting 1 shard to 2 shards and beyond didn't improve the overall indexing throughput.  I specifically increased the corpus size to around 60 days of data to ensure I had plenty of events to index.  My goal was to understand the behaviour the new cluster with respect to hot spotting, shard and replica counts.  Unfortunately, Elastic Rally initially gave me the wrong idea.
It wasn't until I ran multiple copies of Elastic Rally with identical settings concurrently from the same host was I able to actually start approach any of the hardware limits in the cluster.  In the end, I had to run 12x Elastic Rally instances on the elastic\logs track to bottleneck the CPU on the hot data tier.  I executed all 12 instances from a single server (backed by NVMe, 128 GB of RAM, 32c/64t, 10 Gb network).  This resulted in the actual indexing rate rising from 60-70,000 doc/s to 550-600,000 docs/s.  The reality was that the server sending the logs wasn't a limiting factor, nor was the hot data tier nodes, but Elastic Rally in quickly providing the documents fast enough to index.
My suspicion was that, similar to the Golang stdlb for encoding/json, that the performance is not super optimised in Python.  This issue seems to validate that theory, I just wanted to provide a real world example of where Elastic Rally performance is producing results that could be easily misconstrued by naive users such as myself.

@berglh Thanks for the report! It's true that you should always check that the client is not the bottleneck. Until we fix https://github.com/elastic/rally/issues/1399, would you mind running https://github.com/benfred/py-spy on one of the Rally processes? It will tell us what exactly is being slow.

@pquentin I'm not sure if you were after the flame graph specifically or a different format. Can run again with the other output if required. I went ahead and cleared out or cluster password from the SVG. I didn't see anything specifically JSON related in the hotspots, but there's a lot going on as I captured the parent and subprocesses of the elastic/logs track. esrally_profile

I opened https://github.com/elastic/rally/issues/1566 so that this issue stays focused on pysimdjson.


replace chalk with colorette

colorette is a lighter version of chalk.
It reduces the bundle size

I'm not interested in moving to colerette, but I'm willing to move to https://github.com/sindresorhus/yoctocolors

@sindresorhus nice!
I'll change it .


OK button no longer works

Hi,
Current master code, OK button no longer works on KiCAD 6.0.2
thanks

I'm not able to reproduce.
Does KiBuzzard.log have any useful insights?

ctrl + v can use it.


Add Peabody Transcripts to Fixit+

User Story
We've received Peabody transcripts from UGA and need to add them to Fixit+.
Additional Information
Zip file: https://app.zenhub.com/files/116399818/10e81ce4-1de8-4ae9-8ab6-760297f765b0/download
Done Looks Like
The transcripts are added and ready for correction in a new collection called Peabody.

Hey @jasoncorum, do we know that vtt files work? That's the thing I missed with this is we need to see that vtt displays alright.

VTT should display fine as the application actually converts JSON to VTT as part of our import process.
Additional note:
These are going in to FixIt+ with a collection name of: Peabody Collection - UGA.

Iceboxing because this got pushed back and we don't have the records ready for ingest.


Redirect http://build.servo.org/ to HTTPS

This is untested, but matches what https://ssl-config.mozilla.org/ suggests. (This could be a good time to apply other suggestions from there too.)

This change is

Looks good, please merge! ^^ #913 was ignored, so I closed it in a moment of weakness. xD
https://www.hardenize.com/report/build.servo.org/1564587122#summary

r? @jdm

iirc last time I made this change I broke our buildbot CI completely. This will need to wait until I see convincing evidence that that won't happen again.

In particular, I believe that there are some python-based HTTP requests for servo.org that see a 301 response and raise an exception.


feat(chart): add imagePullSecrets values for deployments

Adds the possibility to add a imagePullSecrets value for the images. Since we use Kargo in an on-premise Kubernetes which can't access the internet, we need to access a private registry. The easiest way to do that is with imagePullSecrets: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
Used this values file locally to check that the functionality works:
image:
  repository: my.private.registry/kargo-image
  pullSecrets:
    - name: regcred

api:
  oidc:
    enabled: true
    dex:
      enabled: true
      image:
        pullSecrets:
          - name: regcred
  adminAccount:
    password: admin
    tokenSigningKey: iwishtowashmyirishwristwatch

With this command:
helm template kargo . --namespace kargo --create-namespace  -f test.values.yaml > test.yaml

Best regards. Thanks for your work.

@MPritsch great feature! Thank you for this!


[Feature Request] Catch errors thrown in transform

README says that transform should not throw errors. This makes it less convenient to use for two reasons:

If the code can throw errors, we need to ensure that they are caught and transformed to ctx.addIssue calls with fatal: true
There is often no meaningful value to return in case the error happens, so for zod to infer the output type correctly, some hacks are needed

For example, I wrote this utility helper in my applicaiton to handle this problem:
export const zodCatch =
  <Input, Result>(fn: (input: Input) => Result) =>
  (input: Input, ctx: RefinementCtx) => {
    try {
      return fn(input);
    } catch (error) {
      if (error instanceof Error) {
        ctx.addIssue({
          fatal: true,
          code: ZodIssueCode.custom,
          message: error.message,
          params: {
            ...error,
            name: error.name,
          },
        });
      } else {
        ctx.addIssue({
          fatal: true,
          code: ZodIssueCode.custom,
          message: String(error),
        });
      }

      // Hack for zod to infer type correctly
      // this value won't be used because we added fatal issues to ctx
      return undefined as any as Result;
    }
  };

I use it like this:
const schema = z.string().transform( zodCatch((v) => JSON.parse(v)) );
const parsed = schema.parse("invalid json");

Although this helper solves the problem for me, it would be nice if something like this could be included in zod itself. If catching all errors is too much (it would likely be a breaking change), maybe it can only catch instances of a specific error class. That would still be beneficial because it would eliminate the need for a return type hack.

I agree that transform should have the option to emit errors. Right now I have to basically run the same quote twice, first in a refinement and then again in the transform. E.g. to get a DecimalJs value:
z.string()
  .refine(value => {
    try { new DecimalJs(value) } catch { return false; }
    return true;
  })
  .transform(value => new DecimalJs(value));

It would be ideal if the transform function would be allowed to throw exceptions, and either use the exception message as error, or optionally to pass a secondary argument to the transform function which then will be used as value.

Right now I have to basically run the same quote twice, first in a refinement and then again in the transform

@DASPRiD in the latest versions of zod you don't have to do this twice. Instead, transform provides the ctx argument:
z.string()
  .transform((value, ctx) => {
    try {
      return new DecimalJs(value);
    } catch (error) {
      ctx.addIssue({
        fatal: true,
        code: ZodIssueCode.custom,
        message: error.message,
        params: { ...error, name: error.name }
      })
    }

    // This is a hack to get proper type inference
    return undefined as unknown as DecimalJs;
  });

Nevertheless, having native support for throws in transform would make the syntax much simpler.

// This is a hack to get proper type inference
return undefined as unknown as DecimalJs;

I see we can now return z.NEVER to avoid the casting hack.


few ideas

HI,
great tool, I was looking for something like that, running it on windows and Linux too.
What would you think about following few ideas (I am sure you though about them too)

option to choose font (for all and whole entries - global)
spell check with choice of language

Great tool, with a dark mode it would be perfect, love the simplicity of it... thanks!  Dark mode please!

The ability to add images would also be appreciated (apologies, I am no coder)

Sorry, I am busy with other projects, and I'm not adding new features to this old project right now. 😢  I'm glad you like it though, and yes those are all great features! I may get around to adding them later when I have time for this.


cert-manager v1.10.0 always tries to access clusterissuers at cluster scope

Describe the bug:
Starting in v1.10.0, cert-manager tries to list clusterissuers at the cluster scope, even though we spceifically only enable controllers for namespace scoped resources.
Expected behaviour:
When the clusterissuers controller isn't enabled, don't try to access cluster scoped clusterissuers.
Steps to reproduce the bug:
For cases where clusterissuers are not needed, with v1.9.1 you can start the following controllers. No ClusterRole is needed.
--controllers=issuers,certificates-metrics,orders,challenges,certificaterequests-approver,certificaterequests-issuer-acme,certificaterequests-issuer-selfsigned,certificates-trigger,certificates-issuing,certificates-key-manager,certificates-request-manager,certificates-readiness,certificates-revision-manager"

Starting in v0.10.0, the same configuration will log:
k8s.io/client-go@v0.25.2/tools/cache/reflector.go:169: failed to list *v1.ClusterIssuer: clusterissuers.cert-manager.io is forbidden: User "system:serviceaccount:default:cert-manager" cannot list resource "clusterissuers" in API group "cert-manager.io" at the cluster scope

The purpose of enumerating controllers is that we can turn off those we don't need and we should not need a ClusterRole. I know I could provide it a new ClusterRole for this, but this access attempt is not expected.

Anything else we need to know?:
Environment details::

Kubernetes version: v1.25.3
Cloud-provider/provisioner: Any
cert-manager version: v1.10.0
Install method: e.g. static manifests

/kind bug

Running into the same problem during deployment. Is there a workaround for this ?

/remove-lifecycle-stale

Running into the same problem during deployment. Is there a workaround for this ?

Try disabling certificaterequests-issuer-selfsigned and clusterissuers controllers.


Java 11 version

@notsureifkevin, @pwittrock, the new release/java11 branch will host a version of Spring Petclinic Microservices based on OpenJDK 11.
I've upgraded the maven-docker-plugin from 0.4.13 to 1.2.0 (still have a GCR warning during the build).
We could
I've also used a new prefix (I will report it to develop) in order to publish Docker image to Docker Hub in an a neutral organization.
@mszarlinski I've created the springcommunity organization into Docker Hub. Please could you confirm your DockerHub login is springcommunity

I have logged to DockerHub, thank you @arey


status is not being updated in Indigo

Hey Joe,
Thanks for writing this plug-in! I have three ratgdo devices installed. All of them work with the plug-in. I can open and close them.
I exposed these in the HomeKitLink Siri plug-in as well and can open and close them in the Home app.
However, I'm noticing that the custom states in indigo aren't being updated for the light, availability, obstruction, and door. Are these still in the works?

That means you don't have the trigger properly configured, so updates from the ratgdo to the plugin (via MQTT) aren't received.

Also, some of those are only sent out (by the ratgdo) at startup or if the status changes.

I had created the trigger.
I turned up debugging on the ratgdo plugin. Here's the log:
ratgdo.log
The message that appears to be being sent is wrong:
2023-12-26 21:54:04.992	ratgdo GDO Controller Debug	message_handler: MQTT message ##systemstate## from \uc0\u9881 \u65039 MQTT Connector\
This is unexpected. I believe It should be ##ratgdo## and not ##systemstate##. I verified in the MQTT Connector that was automatically created that the message type is ##ratgdo##
Also I looked in the plug-in, and light, obstruction, and availability aren't supported.

I'll need to see the trigger definition.
What did you use to create that log file?  It looks like it was formatted in RTF, which messed it up.  Please use a plain text editor (like BBEdit) and repost.

I found the issue. I needed to go edit the MQTT Connector device and add "ratgdo/#" as a subscribed topic. Now things are working, including the updating of the light, availability, and obstruction. I didn't see that explicitly spelled out in the README. I may have missed it.
I can create an action to turn the light on or off by sending the appropriate MQTT command, so that will take care of that.
I believe you can close this issue.

I updated the README to include the required subscription.  Thanks for catching that.


Different default shot numbers for qiskit Sampler and BraketLocalBackend.

What is the expected enhancement?
The default shot number for qiskit’s Sampler is 0, whereas that for BraketLocalBackend is 1000, see the code example below. This could cause some confusion. Ideally, the default shot values should be the same.
from qiskit import QuantumCircuit
from qiskit_braket_provider import BraketLocalBackend
from qiskit.primitives import Sampler

circuit = QuantumCircuit(1)
circuit.h(0)
circuit.measure_all()

# Run with qiskit backend
Sampler().run(circuit).result().quasi_dists[0]

# Qiskit local backend return probability calculated
# from state vector, which has no shot noise and the
# result is fixed for different runs
# {0: 0.5, 1: 0.5}

# Run with braket backend
BraketLocalBackend().run(circuit).result().results[0].data.counts

# Braket local backend return sampled probability with shot noise
# and the result vary from run to run
# {'1': 537, '0': 487}

I'm actually surprised that the sampler accepts 0 shots, and returns probabilities as the counts. In any case, the Braket provider doesn't have a native sampler, but just a classic Qiskit backend, which is a different interface. However, it might be worth considering writing native primitives in this package.


Not working

trade-helper not working, please fix it

+1 i like ur trade helper bro please fix it

It would be rly cool if you can fix this issue or at lest give us a chance on fixing it ourselfs. Thank you very much!

I would love to get this updated, since Geforce Now currently supports getting the copied content and pasting it into the host, you don't need steam at all.
That would probably make it easier even for awakened poe trade to integrate with GFN players, but for this tool it'll already work great if it's fixed :)

I would love to get this updated, since Geforce Now currently supports getting the copied content and pasting it into the host, you don't need steam at all.
That would probably make it easier even for awakened poe trade to integrate with GFN players, but for this tool it'll already work great if it's fixed :)
If you could do it, a lot of people would be grateful to you


[Bug]: Sign In Button does not work in Mobile

The Sign In button is not working/not directing to any link after being clicked in a mobile phone.

we are working on it


Add support for billing mapping

It would be nice to enable the option to have some way of mapping matrix users to a billing system as well. This way one could sustainably host this for others and have a SIP Trunk for it.

Ideas on billing flow:

Using a widget to charge prepaid amounts (Downside: No transfer, Benefit: easy to verify user)
External page to charge amounts and then linking via email verification alike flow. (Benefit: same flow can be used to transfer users. Downside: Needs to manage accounts)
Bot sends link (Downside: Bad UX and no transfer)


Button missing from Google Calendar

OS version:
Browser version:
Extension version:

Relevant integration (if any):
Google Calendar
🐛 Describe the bug
The button is not visible in Calendar events
Expected behaviour

Steps to reproduce

Steps to reproduce the behaviour:

Go to ...
...

Other details or context
Case

case reference

case reference

The Google Calendar has changed the names of styles and structure so the extension cannot find the close button
In the code of the track-extension/src/content/google-calendar.js file:
const notTogglPseudoClass = ':not(.toggl)';
const popupDialogSelector = 'div[data-chips-dialog="true"]';
const detailContainerSelector = 'div[data-is-create="false"]';
const rootLevelSelectors = [
${popupDialogSelector},
${detailContainerSelector}${notTogglPseudoClass}
].join(',');
...
const closeButton = $('[aria-label]:last-child', elem);
The selector that ends up returning in the case of the modal is not the one to close but the one with the three vertical dots
As a first step, replace "[aria-label]:last-child" with "[aria-label]:first-child"
In addition to the "target =
closeButton.parentElement.nextElementSibling.lastElementChild
.lastElementChild;" is no longer viable and would have to be rethought

Report

Report

case reference

case reference

case reference

case reference

Case reference

Case reference

Case reference

Case reference

case reference

case reference

Case reference

Case

Case reference

Case reference

Thanks @AdrianBou.
Your comment helped us fix the problem faster! 🙌
PR open #2150 👌


Problem merging library's Manifest: "android:allowBackup"

In my app, I need "android:allowBackup" to be false, but it seems that it has been set to true in the library's AndroidManifest.
This is similar to the issue reported here: https://github.com/voghDev/PdfViewPager/issues/11
While there is a workaround for this, it might be worthwhile to make the change to remove it as well. It is set to true by default, which is probably why it shows up in the generated AndroidManifest, even though you have not explicitly set it as such.
I would be happy to provide with a PR if that works for you.
Thanks for the library, btw! Extremely useful and handy!

Ok, I'll have a look at this attribute in the samples and the library project.
Thanks for reporting

In the meanwhile, have you tried to ignore android:allowBackup the same way android:icon is ignored in #11? Never tried something similar tbh

Yeah, that's basically the workaround I mentioned. It's not critical, just annoying :)

@voghDev: Did you plan to create a release that includes this fix?
I'm eager to update to avoid those merge rules.
Thanks for your awesome lib!

Hi Andreas,
I thought it was released already. I'll have a look and release it together with another changes.
Thanks!

Hi again, I've released 1.0.2 that fixes these manifest conflicts. If you want to have a look at the code it is located in the vertical_viewpager branch. There is a full list of changes in CHANGELOG.md
Let me know if this solves manifest conflicts

The Manifest changes work as expected.
Thank you very much for taking the time to create a new release!

You're welcome mate :) I'm glad they do

Can you please update the README to this version 1.0.2? I had the same problem, because I installed the 1.0.1 version and had to to search for this issue to find out it has already been resolved.

@janvde I mean, the README clearly states that latest is 1.0.2...

It doesn't under the 'installation' header.

Well 1.0.2 was quite of an experimental branch, I'm not sure if making it the official one. If this version helped you fixing an issue, then it would be ok to add it in the README, I guess.
Thanks for the feedback

Uploaded a version 1.0.3 that is similar to 1.0.2 but without the experimental features (vertical ViewPager). This issue should not give more headaches :-)

Hi,
there is an updated version of the vertical_viewpager branch
You can try it using
implementation 'es.voghdev.pdfviewpager:library:1.1.3'
Let me know if it's useful for you


#3006: Calculated columns: changing return type triggers column reordering

To reproduce:

Open any CSV in native DG
Add a calculated test column which simply returns 1
Reorder columns such that the test column is on the right of the Structure column
Open the dev console
Update the formula such that it returns 2 as follows:

table = grok.shell.tableByName('SPGI_10_rows')
testCol = table.getCol('test')
await testCol.applyFormula('2', 'int')

The column now shows 2 in all rows and has not moved
Update the formula such that it returns a as follows:

await testCol.applyFormula('a', 'string')

The column has moved to the bottom of the table: this should not happen

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16521

Olesia Pavlenko commented in Jira:

PowerPack > v.1.1.14


Protcol APIView: stylistic improvements

-> narrow down the exception type of try/catch
https://github.com/Azure/azure-sdk-tools/blob/main/packages/python-packages/protocol-stub-generator/protocol/protocol_models.py#L1383
-> Instances like the below  can be refactored to leverage enumerate:
for op_groups in range(0, len(yaml_data["operationGroups"])):

Closing as LLC View will be replaced with Swagger view.


Forman can drop signals in extreme conditions

Hello,
While reading the article at
http://www.sitepoint.com/the-self-pipe-trick-explained/ I realized
that the signal handling code shown there and of the same type in your
application is broken.  As you have a single nonblocking pipe in your
application you can drop signals entirely (and not just fold multiple
signals of the same type into one).  The simplest fix is to use a pipe
for each individual type of signal or to just use pselect or similar.
I'm pretty sure that there is a way to use a single pipe but it seems
complicated and very difficult to implement correctly.
Thank you,
Steven Stewart-Gallus

Thanks for the note. Please submit a PR if you have an idea how to fix it!


Add misc.visitor.py

Fixes https://github.com/fonttools/fonttools/issues/1959

Thanks @anthrotype. This is currently a sketch... I expect to reiterate on it, and then put things in their proper places.

Okay I think this is useful-enough to be merged now.
The Snippets/scale-upem.py added here already handles variable fonts as well.

I've added a fairly functional print-json.py snippet as well. Python is able to parse back the json and I'm able to do things like:
j['glyf']['glyphs']['uni0040']['coordinates'][3][0]

which is the equivalent of:
font['glyf'].glyphs['uni0040'].coodinates[3][0]

I've added a fairly functional print-json.py snippet as well. Python is able to parse back the json and I'm able to do things like:

Doesn't work for CFF... We need to add ensureDecompiled there.

Okay. Tests also added with 100% coverage.

This is great!
Could you add the scaler as a module to https://github.com/fonttools/fonttools/tree/main/Lib/fontTools like we do for pyftsubset and merge?
I plan on using this to diff fonts which have different upms.

Thanks for the review Cosimo. I'll address them soon.

Could you add the scaler as a module

Done. Need better API, etc. But you can use it already.

@anthrotype PTAL.


Can i use this in .vue files without using the vue-filepond package?

Summary
The following script doesn't bind to the input element
const inputElement = document.querySelector('input');
const pond = FilePond.create(inputElement);
According to the DOCS the input element will be replaced with ...
But It doesn't get replaced.
How to reproduce
Using a .vue create the code below:
`

`
...
Expected behaviour
The input element should be replaced with ...
...
Additional information
...

Environment
Version

OS
MacOS / Windows / iOS / Linux / ...

Device
iPhone SE / Galaxy Note 9 / ...

Browser
Safari 11.1.1 / Edge 15 / ...

Sorry i am not sure why my code isn't being see here, i did surround them with backticks

I would advice against this as you’d have to add most of the code that is in the Vue adapter yourself. Why not use the adapter?
Will close this issue as it’s related to Vue implementation details and not a FilePond bug/problem.


Zoom is installed in C:\Windows\System32\config\systemprofile\AppData\Roaming\Zoom

Brief description of your issue
The package Zoom.Zoom is installed in the above mentioned path, which makes it unavailable for the users. It also doesn't create a registry neither is it listed with a Winget list.
Steps to reproduce
The software, like many other packages, is installed from MDM, using a script that uses Winget.exe install -e --id Zoom.Zoom
As it is installed in this folder, it is not accessible for users, neither appears in the Winget list, in the list of apps installed or in the windows registry.
Expected behavior
To be installed in some folder accessible for the users
Actual behavior
It is being installed in the above mentioned folder and cannot be used by users.
WinGet-2022-10-20-06-47-40.413.log
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19043.2130
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

This looks like it's an error with the Zoom installer itself being called in a system context from MDM, as winget just calls the installer. It does seem like in your context that it is writing to the registry keys, but since the user scope was selected, those registry changes would only show for the MDM user.
2022-10-20 06:47:42.623 [CLI ] Starting installer selection.
2022-10-20 06:47:42.623 [CLI ] Installer [X86,exe,User,] is current best choice
2022-10-20 06:47:42.623 [CLI ] Installer [X86,exe,User,] is better than [X86,msi,Machine,] due to: Scope
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is better than [X86,exe,User,] due to: Machine Architecture
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is current best choice
2022-10-20 06:47:42.623 [CLI ] Installer [X64,exe,User,] is better than [X64,msi,Machine,] due to: Scope
2022-10-20 06:47:42.623 [CLI ] Installer [Arm64,exe,User,] not applicable: Machine is not compatible with Arm64
2022-10-20 06:47:42.623 [CLI ] Installer [Arm64,msi,Machine,] not applicable: Machine is not compatible with Arm64
2022-10-20 06:47:42.623 [CLI ] Completed installer selection.
2022-10-20 06:47:42.623 [CLI ] Selected installer Architecture: 2
2022-10-20 06:47:42.624 [CLI ] Selected installer URL: https://cdn.zoom.us/prod/<IP_ADDRESS>81/x64/ZoomInstallerFull.exe
2022-10-20 06:47:42.624 [CLI ] Selected installer InstallerType: exe
2022-10-20 06:47:42.624 [CLI ] Selected installer Scope: User
2022-10-20 06:47:42.624 [CLI ] Selected installer Language:
2022-10-20 06:47:42.630 [CLI ] Generated temp download path: C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\f7cba2e790a7d41658ea0f430ac775f08d9872add59168fd72f12262bc9f9786
2022-10-20 06:47:42.630 [CORE] Downloading to path: C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\f7cba2e790a7d41658ea0f430ac775f08d9872add59168fd72f12262bc9f9786
2022-10-20 06:47:42.631 [CORE] DeliveryOptimization downloading from url: https://cdn.zoom.us/prod/<IP_ADDRESS>81/x64/ZoomInstallerFull.exe
|
2022-10-20 06:47:47.754 [CLI ] Starting: 'C:\Windows\TEMP\WinGet\defaultState\Zoom.Zoom.5.12.9281\ZoomInstallerFull.exe' with arguments '/silent'
|
2022-10-20 06:49:19.522 [CLI ] During package install, 1 changes to ARP were observed, 1 matches were found for the package, and 1 packages were in both
2022-10-20 06:49:19.522 [CLI ] The entry determined to be associated with the package is 'Zoom', with publisher 'Zoom Video Communications, Inc.'

@SamaelAmbrona did you try run with:
--scope=machine
You can read more here:
https://github.com/microsoft/winget-cli/issues/1772
https://learn.microsoft.com/en-us/windows/package-manager/winget/settings#scope

you can read in the log:
2022-10-20 06:47:42.624 [CLI ] Selected installer Scope: User


Filter out opted out regions in config check

This PR updates the "AWS Config Enabled in all regions" query to filter out regions that are opted out. Opted out regions can not be accessed in any way so missing config resources in those regions should not be reported as an error.

Thanks @yorinasub17 for using Steampipe 👍 . Great to see your contribution here 👍.
You are absolutely right about the control reporting an error state, however, instead of filtering out the regions which have not been opted in, could we skip them in state and add a reason for opted-out regions?
You could refer https://github.com/turbot/steampipe-mod-aws-compliance/blob/main/query/securityhub/securityhub_enabled.sql for more information.

however, instead of filtering out the regions which have not been opted in, could we skip them in state and add a reason for opted-out regions?

Sounds good! Updated in 547faad and checked that it works as intended (account ID masked):
%~> aws-vault exec logs -- steampipe check control.cis_v140_3_5 --workspace-chdir .

+ 3.5 Ensure AWS Config is enabled in all regions ........................................................................................ 1 / 22 [==========]
  |
  ALARM: ap-northeast-3 IncludeGlobalResourceTypes disabled, AllSupported disabled, Recording disabled and LastStatus is not SUCC… ap-northeast-3<PHONE_NUMBER>00
  OK   : sa-east-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ sa-east-1<PHONE_NUMBER>00
  OK   : eu-west-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ eu-west-1<PHONE_NUMBER>00
  OK   : ap-south-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .......... ap-south-1<PHONE_NUMBER>00
  OK   : us-west-2 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ us-west-2<PHONE_NUMBER>00
  OK   : us-east-1 IncludeGlobalResourceTypes enabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............. us-east-1<PHONE_NUMBER>00
  OK   : ap-southeast-2 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .. ap-southeast-2<PHONE_NUMBER>00
  OK   : ap-northeast-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .. ap-northeast-1<PHONE_NUMBER>00
  OK   : us-east-2 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ us-east-2<PHONE_NUMBER>00
  OK   : ap-southeast-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .. ap-southeast-1<PHONE_NUMBER>00
  OK   : ap-northeast-2 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .. ap-northeast-2<PHONE_NUMBER>00
  OK   : eu-north-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. .......... eu-north-1<PHONE_NUMBER>00
  OK   : us-west-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ us-west-1<PHONE_NUMBER>00
  OK   : eu-west-3 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ eu-west-3<PHONE_NUMBER>00
  OK   : ca-central-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ...... ca-central-1<PHONE_NUMBER>00
  OK   : eu-central-1 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ...... eu-central-1<PHONE_NUMBER>00
  OK   : eu-west-2 IncludeGlobalResourceTypes disabled, AllSupported enabled, Recording enabled and LastStatus is SUCCESS. ............ eu-west-2<PHONE_NUMBER>00
  SKIP : Region is opted out. ......................................................................................................... ap-east-1<PHONE_NUMBER>00
  SKIP : Region is opted out. ........................................................................................................ af-south-1<PHONE_NUMBER>00
  SKIP : Region is opted out. ........................................................................................................ eu-south-1<PHONE_NUMBER>00
  SKIP : Region is opted out. .................................................................................................... ap-southeast-3<PHONE_NUMBER>00
  SKIP : Region is opted out. ........................................................................................................ me-south-1<PHONE_NUMBER>00

Summary

OK ........................................................................................................................................... 16 [========  ]
SKIP .......................................................................................................................................... 5 [===       ]
INFO .......................................................................................................................................... 0 [          ]
ALARM ......................................................................................................................................... 1 [=         ]
ERROR ......................................................................................................................................... 0 [          ]

TOTAL .................................................................................................................................... 1 / 22 [==========]

@yorinasub17 Thanks again for the PR!


Keeps firing scrollListener

In attachScrollListener why do we fire scrollListener(), it causes  load more without even any scroll or resize event happening ?

This package is no longer being maintained, so if you're using a newer version of React, like 15.x you need to be using the fork I'm running at https://github.com/CassetteRocks/react-infinite-scroller.
On mount, we attach the scroll listener and also call it manually. This is to load the first set of items. You could disable it by setting pageStart to -1 and then checking whether the pageToLoad parameter of your loadMore function is greater than 0.

Once scrollListener is being called for the first time...i handle load more with the >0 condition but it calls detachScrollListener as well, after that it is never attaching the event again.

We detach the scroll listener because it would send off infinite calls to loadMore. We attach it again when the component updates (with new items added).

But we add new items on load more.. in this case that would never be called..

We detach the scroll listener AND make the one call that's needed to loadMore.
https://github.com/CassetteRocks/react-infinite-scroller/blob/master/src/react-infinite-scroll.js#L53

yeah but for the first call i have disabled the data fetch as u suggested, so there won't be any update in the component.