Ruby installation failed in macOS Big Sur

Unable to install any ruby version and budler on macOS Big Sur
I am following these steps:-
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/cask).
==> Updated Casks
Updated 3 casks.

==> Downloading https://homebrew.bintray.com/bottles/rbenv-1.1.2.big_sur.bottle.tar.gz
Already downloaded: /Users/name/Library/Caches/Homebrew/downloads/dbb4da662766f6b1e426b189d6d9a17d063eb9691bbbe62b78e832f82900350e--rbenv-1.1.2.big_sur.bottle.tar.gz
==> Pouring rbenv-1.1.2.big_sur.bottle.tar.gz
🍺  /usr/local/Cellar/rbenv/1.1.2: 36 files, 105.2KB

rbenv install
Downloading openssl-1.1.1i.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242
Installing openssl-1.1.1i...
Installed openssl-1.1.1i to /Users/name/.rbenv/versions/2.6.5

Downloading ruby-2.6.5.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.5.tar.bz2
Installing ruby-2.6.5...
ruby-build: using readline from homebrew

BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)

Inspect or clean up the working tree at /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216124622.91669.v6m2Eq
Results logged to /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216124622.91669.log

Last 10 log lines:
ld: warning: dylib (/usr/local/lib/libgmp.dylib) was built for newer macOS version (11.0) than being linked (10.15.6)
Undefined symbols for architecture x86_64:
  "__mh_execute_header", referenced from:
      _rb_dump_backtrace_with_lines in addr2line.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [libruby.2.6.dylib] Error 1
make: *** Waiting for unfinished jobs....
ln -sf ../../../.ext/include/x86_64-darwin20/rb_mjit_min_header-2.6.5.h include/ruby-2.6.0/x86_64-darwin20/rb_mjit_min_header-2.6.5.h
transdb.h updated
name-Singh:number26_ios name$ brew install openssl
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
Updated 1 formula.

Warning<EMAIL_ADDRESS>1.1.1i is already installed and up-to-date.
To reinstall 1.1.1i, run:
  brew reinstall<EMAIL_ADDRESS>
$ export RUBY_CONFIGURE_OPTS="--with-openssl-dir=$(brew --prefix openssl@1.1)"

$ rbenv install 2.7.0

Downloading ruby-2.7.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.0.tar.bz2
Installing ruby-2.7.0...
ruby-build: using readline from homebrew

BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)

Inspect or clean up the working tree at /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216125938.15886.AZCdH0
Results logged to /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216125938.15886.log

Last 10 log lines:
    VALUE mesg;
              ^
               = 0
eval.c:744:5: warning: function 'rb_f_raise' declared 'noreturn' should not return [-Winvalid-noreturn]
    UNREACHABLE_RETURN(Qnil);
    ^
./include/ruby/ruby.h:59:35: note: expanded from macro 'UNREACHABLE_RETURN'
#  define UNREACHABLE_RETURN(val) return (val)
                                  ^
3 warnings generated.

I am unable to install any version of ruby. Please help.

Had the same problem on BigSur
Reinstalled OpenSSL, rbenv, ruby-build, llvm and it helps

I never reproduce it. If you provide the instructions for reproducing this, I can help you.

Unable to install any ruby version and budler on macOS Big Sur
I am following these steps:-
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/cask).
==> Updated Casks
Updated 3 casks.

==> Downloading https://homebrew.bintray.com/bottles/rbenv-1.1.2.big_sur.bottle.tar.gz
Already downloaded: /Users/name/Library/Caches/Homebrew/downloads/dbb4da662766f6b1e426b189d6d9a17d063eb9691bbbe62b78e832f82900350e--rbenv-1.1.2.big_sur.bottle.tar.gz
==> Pouring rbenv-1.1.2.big_sur.bottle.tar.gz
🍺  /usr/local/Cellar/rbenv/1.1.2: 36 files, 105.2KB

rbenv install
Downloading openssl-1.1.1i.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242
Installing openssl-1.1.1i...
Installed openssl-1.1.1i to /Users/name/.rbenv/versions/2.6.5

Downloading ruby-2.6.5.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.6/ruby-2.6.5.tar.bz2
Installing ruby-2.6.5...
ruby-build: using readline from homebrew

BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)

Inspect or clean up the working tree at /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216124622.91669.v6m2Eq
Results logged to /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216124622.91669.log

Last 10 log lines:
ld: warning: dylib (/usr/local/lib/libgmp.dylib) was built for newer macOS version (11.0) than being linked (10.15.6)
Undefined symbols for architecture x86_64:
  "__mh_execute_header", referenced from:
      _rb_dump_backtrace_with_lines in addr2line.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [libruby.2.6.dylib] Error 1
make: *** Waiting for unfinished jobs....
ln -sf ../../../.ext/include/x86_64-darwin20/rb_mjit_min_header-2.6.5.h include/ruby-2.6.0/x86_64-darwin20/rb_mjit_min_header-2.6.5.h
transdb.h updated
name-Singh:number26_ios name$ brew install openssl
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
Updated 1 formula.

Warning<EMAIL_ADDRESS>1.1.1i is already installed and up-to-date.
To reinstall 1.1.1i, run:
  brew reinstall<EMAIL_ADDRESS>
$ export RUBY_CONFIGURE_OPTS="--with-openssl-dir=$(brew --prefix openssl@1.1)"

$ rbenv install 2.7.0

Downloading ruby-2.7.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.0.tar.bz2
Installing ruby-2.7.0...
ruby-build: using readline from homebrew

BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)

Inspect or clean up the working tree at /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216125938.15886.AZCdH0
Results logged to /var/folders/0m/d_d_3jb10hnbqhrwf01p5v380000gp/T/ruby-build.20210216125938.15886.log

Last 10 log lines:
    VALUE mesg;
              ^
               = 0
eval.c:744:5: warning: function 'rb_f_raise' declared 'noreturn' should not return [-Winvalid-noreturn]
    UNREACHABLE_RETURN(Qnil);
    ^
./include/ruby/ruby.h:59:35: note: expanded from macro 'UNREACHABLE_RETURN'
#  define UNREACHABLE_RETURN(val) return (val)
                                  ^
3 warnings generated.

I am unable to install any version of ruby. Please help.

any luck, im also facing same issue?

I never reproduce it. If you provide the instructions for reproducing this, I can help you.

Which version of mac os you are using?

same issue

I'm also experiencing this exact issue, under MacOS Monterey.

Has anyone found a fix for this? running into too. Running MacOS Monterey (12.2.1).


iOS 12.4.1 support for 6s plus

Can we get iOS 12.4.1 support for iPhone 6S plus (a9)? I get unsupported message as it is not supported I have confirmed.
I’m definitely willing to beta-test any solution. I have a number of older tweaks and even apps that will still not work on iOS 13.
The Only other thread that was relevant is now closed. In that thread other people also had issues with the three pieces of hardware that do support 12.4.1 with uncover.

well it will happen sometime soon™ because time_waste works on ios 12.

Why not just use Checkra1n if Unc0ver has not incorporated or does Checkra1n not have one either being if that’s the case is it because no exploit was ever found to bypass the Apple security model and allow root.
Sincerely,
Aaron Lax

On Apr 5, 2020, at 4:57 PM, eglacias<EMAIL_ADDRESS>wrote:

Can we get iOS 12.4.1 support for iPhone 6S plus (a9)? I get unsupported message as it is not supported I have confirmed.
I’m definitely willing to beta-test any solution. I have a number of older tweaks and even apps that will still not work on iOS 13.
The Only other thread that was relevant is now closed. In that thread other people also had issues with the three pieces of hardware that do support 12.4.1 with uncover.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

We do use check rain on it. Works ok. What we want is an on device jailbreak. Having to find a computer anytime I lose power is not convenient. Reprovision  also works to sign it right now

Is there any chance of ever getting support for this version? It would be nice if it’s not going to happen or for some seemingly impossible reason can’t happen, for:
One of the developers to just mark this not gonna happen so I don’t have to Check up on him covered anymore for this phone!
I would be equally happy happy to see that going to happen :-)

I think it's now supported.

Yes it’s technically supportive but not working. If I restore rootfs with checkrain then uncover after reboot, then uncover jailbreak install cydia filza and use batchomatic to reinstall all of my tweaks, everything runs perfectly and I can respring too. Now if I reboot, it gets stuck on the white Apple.
At that point even though it jailbroke it self and I could install all of my tweaks and run them, it failed to jailbreak again on a reboot.
Regular iOS 12.4 worked perfectly fine with the old uncover with the exact same tweaks
I don’t have tweaks that I don’t need, so I’ll go through the painful process of removing stuff until it finally jailbreaks and we’ll see what happens. No fun at all.

Watchdog pro seem to be the culprit. That’s really too bad because there is no backgrounding tweak at all other than that that actually backgrounds apps. it was working fine with old uncover and checkrain. It also works if I install it and only do a respring.

Checkrain is not working with version five. I’m guessing substitute or Cydia substrate is not the same Anymore or something?
It gets the jailbreak, but has me in safe mode essentially without telling me it is in safe mode

I guess I still won’t close this thread because:
Checkrain no longer works with uncover.
Uncover it self is working marvelously however. I noticed the Reddit page on what is jailbreakable has not been updated either.
Why is substitute and substrate both used interchangeably but mutually exclusive between these two and the 2 jailbreaks?
Basically checkrain is in safe mode and will not leave safe mode.

Another reason not to close this thread is because I enumerated a very important tweak which was functioning perfectly well using substrate instead of substitute on uncover 5: watchdog pro.  It may be a very old application, but it was still working perfectly right up to iOS 12.4.1 which I run,  and there is no other background application in the world other than this one

What don't you people understand, ios 12.4.1 to 12.4.7 is not bloody compatible. I know unc0ver says all versions are, but you should read around, read the fine print. You should appreciate what goes into a jailbreak, and you can't expect everything you want to just happen. It is currently impossible to jailbreak you device, and there is no way you can change that, unless you update to ios 13.5.

I am running iOS 12.4.1. With uncover 5. On an iPhone 6s Plus. It is compatible.
On It is entirely compatible. I have one single tweak that doesn’t work and everything else is working more stable than any jailbreak I have ever run.

I am running iOS 12.4.1. With uncover 5. On an iPhone 6s Plus. It is compatible.
On It is entirely compatible. I have one single tweak that doesn’t work and everything else is working more stable than any jailbreak I have ever run.

Oh sorry I put my comment on the wrong thread, and I meant anything in between 13.4.1 and 13, not inclusive, sorry for the confusion

@eglacias - Based on the iOS jailbreak chart ( https://docs.google.com/spreadsheets/d/11DABHIIqwYQKj1L83AK9ywk_hYMjEkcaxpIg6phbTf0/ ), Chimera ( https://chimera.coolstar.org ) is also listed as supporting your device and I didn't see it mentioned so far here. Could it work for you?


Running server

Hey, I have been working on making this exact task easier myself It's refreshing to see others working on it as well!
I am curious how you are handling starting up the server (not dev server) between compilations?

just start the server after compile? like in https://github.com/ream/ream

What about on re-compilation?

Like this?
let element

serverCompiler.plugin('done', stats => {
  element = requireBundle('/path/to/bundle')
})

app.get('*', (req, res) => {
  if (!element) return res.end('please wait for compiltation...')
  renderToString(element, (err, html) => res.send(html))
})

in mean for reloading the server after the server has compiled not the browser code.

you mean refresh the browser? it will be refreshed since client code is changed too.

Doesn't this handle building the server side? I'm thinking if I'm building an API and it's updated how is that handled/reloaded on the server side? Like nodemon or similar. Maybe that's out of scope for this library.

maybe something like https://github.com/palmerhq/backpack

I'll check that out. Thanks for chatting.


fix negative samples in nt_xent loss

What does this PR do?
Fixes #252.

Hello @Alokaado! Thanks for opening this PR.

In the file pl_bolts/losses/self_supervised_learning.py:

Line 21:58: E226 missing whitespace around arithmetic operator
Line 21:99: E226 missing whitespace around arithmetic operator
Line 22:57: E226 missing whitespace around arithmetic operator
Line 22:99: E226 missing whitespace around arithmetic operator

Do see the Hitchhiker's guide to code style

@ananyahjha93

The denominator does contain the positive sample itself, so the calculation checks out to be fine. We do not work with log(pos/neg), but rather log(pos / (pos + sum over neg)). This is not a bug, but rather how the contrastive loss is designed.


Travis CI

We should have some set of basic unit tests run as part of a Travis CI suite. The goal should be to quickly verify that new changes do not horribly break existing functionality.
Perhaps the feed provider application could be unit tested directly without requiring a full OpenWhisk deployment?

When we enable the Travis CI:
do we intend to run unit tests for the feed actions(KafkaFeed and MessageHubFeed) without OpenWhisk installation?
Or do we run other tests for python code of the Kafak package?

My primary concern is to ensure that the Travis run is fast. If we can somehow test against a current OpenWhisk deployment in Travis and keep the time reasonable (under 30 minutes) then that is preferable. However, I doubt that is really possible, and so I would lean toward running unit tests against the feed service itself.


Need example of standalone browser app with pre-bundled orbit-db, without Node

I am coming from .NET (C#) and I find it extremely difficult to integrate orbit-db into my Blazor app. Geting Node, webpack, browserify, make and babel to work in windows was pain in the ass in the first place and I can't bundle orbit-db properly with these tools whatever I try, probably because I am not familiar with them.
What I need help with, for simplicity sake, is making your browser example work standalone (I can take it from there) (https://www.dropbox.com/s/2nhlfhbkx7z9bgq/orbitdb-example.zip?dl=0).
I can't make it work even if I take the bundle generated using npm run build:examples. I am always getting error saying that: OrbitDB.createInstance is not a function.
if you could take 5 minutes of your time to show me how to make it work in the browser, without node, as a standalone app, using es modules (import { x } from "x.js") I would be grateful (ipfs is not the problem, I was able to import IPFS on first try).

OrbitDB won't be able to connect to libp2p from within the browser because it doesn't have the ability to make a UDP socket.  It could pull down a read-only replica from IPFS, but that isn't as interesting. You could use IPFS with PocketDB and have a CoudhDB instance sync for HTTP clients.

Its good to know as it is making orbit-db not viable for my project but it still doesn't resolve the issue preventing me from bundling it properly (if sb else would like to shed some light on it feel free to do so). However... it makes my issue irrelevant :).
My initial idea was to log "actions" on ipfs, fingerprint them on some (any) blockchain and then interpret those "actions" as data and store these data in local copies of sqlite accessed using EF in memory and persisted in IndexDB (doable from WASM: https://stackoverflow.com/questions/67966259/how-to-use-sqlite-in-blazor-webassembly/71325939#71325939). I guess I need to go back to that approach. I just thought orbit-db could make my life easier. if you are curious, in general in my personal project, I want to achieve serverless, blockchain agnostic architecture where different node "classes" are decoupled (they know of blockchain but not about each other) without having a single point of failure and without resorting to Tendermint.
CouchDb won't do for the reasons above but I can give your way a try with slight modifications because there is PouchDB which is a portable "version" of CouchDb if memory serves me well. I don't know PocketDb and it looks like the documentation is non-existent? I am not sure how to use it with IPFS but browsing the code quickly reveals that it tries to store data in physical location.

i cant even get nodejs to create an instance, what to do?

Bundling should be fixed in 1.0.0. Note the new package name.
If the issue persists, feel free to re-open the issue.


Move to functional components (Part III)

Description

Type of change

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

How to test

Checklist

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 91 (4.4%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.03%) to 32.966%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/pages/contributors/subcomponents/ContributorsList.tsx
1
13
7.69%

src/commons/editingWorkspaceSideContent/EditingWorkspaceSideContentProgrammingQuestionTemplateTab.tsx
1
34
2.94%

src/pages/academy/grading/subcomponents/GradingEditor.tsx
2
44
4.55%

Files with Coverage Reduction
New Missed Lines
%

src/pages/academy/grading/subcomponents/GradingEditor.tsx
1
3.31%

src/pages/contributors/subcomponents/ContributorsList.tsx
1
6.25%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
4363

Relevant Lines:
12307

💛  - Coveralls

@chownces I'm not sure how I would be able to test the GradingEditor for regressions; are you able to test the two TODOs in this PR?


libcurl3 dependency is problematic, should be libcurl3-gnutls

[ ] master
[ ] 4-2-stable

The debian package depends on libcurl3:
https://github.com/irods/irods_microservice_plugins_curl/blob/9e3a6f9cd9658dbdd21dff4949215631061ee1d3/CMakeLists.txt#L159
We build against libcurl4-gnutls-dev on xenial and bionic:
https://github.com/irods/irods_development_environment/blob/f33141d780d5f5e73fd971e2238362fd08490cc3/Dockerfile.irods_core_builder.ubuntu16#L57
https://github.com/irods/irods_development_environment/blob/f33141d780d5f5e73fd971e2238362fd08490cc3/Dockerfile.irods_core_builder.ubuntu18#L58
On xenial, libcurl3 and libcurl4-gnutls-dev come from the same source package
That source package also exists for bionic, but libcurl3 became libcurl4. On bionic, libcurl3 comes from a different source package and is incompatible with libcurl4. Installing libcurl3 breaks everything that depends on libcurl4, including the curl command itself.
Furthermore, the only curl library that libmsiCurlGetObj.so, libmsiCurlGetStr.so, and libmsiCurlPost.so link to is libcurl-gnutls.so.4, which is not in the libcurl3 (xenial nor bionic) or libcurl4 packages.
Instead, it's in libcurl3-gnutls in both xenial and bionic

that makes my head hurt.    thanks for untangling.


BMC Boot side keyword

[x] Test code to to check which side the BMC is booted..

BMC has two flash memory chips. For chiplet select side - 0 <-- Current side , if 1<-- Alt side
root@witherspoon:~# echo $(($(devmem 0x1e785030) >> 1 & 1))
0
root@witherspoon:~#

In review https://gerrit.openbmc-project.xyz/#/c/10453/


Shutting down memcached crashes program with "Abort trap: 6"

With a memcached server running run this program:
#!/usr/bin/env python

import time
import pylibmc

mc = pylibmc.Client(['<IP_ADDRESS>'])

mc.set('mc_test_foo', 10)

while True:
	try:
		print mc.get('mc_test_foo')
	except:
		print "Got exception"
	time.sleep(1)

Now shut down memcached. At the next get() the program crashes with the following output:
Assertion failed: (0), function memcached_io_read, file libmemcached/io.cc, line 356.
Abort trap: 6
I'm not sure if this is not the intended behavior, please educate me on what to do if it is.
Relevant software versions:
OS X 10.7.2
Python 2.7.2 (via brew)
pylibmc 1.2.2
libmemcached 0.50 (via brew)

I suggest upgrading libmemcached, this does not happen with libmemcached 1.0.2:
~/devel/pylibmc git:master % pbpaste | PYTHONPATH=build/lib.macosx-10.7-intel-2.7 python -
10
10
10
None
Got exception
Got exception
Got exception
^CTraceback (most recent call last):
  File "<stdin>", line 15, in <module>
KeyboardInterrupt

Closing as this is an issue with a previous release of libmemcached.

Upgrading libmemcached worked, thanks!


Error in lambda event registration description

In the sentence:
"Unlike delegates, they can be directly assigned as the left-hand side of event registration or in various LINQ clauses and methods."
Shouldn't it be the "right-hand" side?

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

ID: 36115425-3181-1363-dcbd-42e48db8613c
Version Independent ID: 57ca5426-2ae3-7260-cef9-e92dc9d4e856
Content: Delegates and lambdas
Content Source: docs/standard/delegates-lambdas.md
Product: dotnet
Technology: dotnet-standard
GitHub Login: @richlander
Microsoft Alias: wiwagn

/assing


change doc dynamically

it would be great to have something similar to this.$refs.editor.clearContent() that we can use to replace doc dynamically. eg. this.$refs.editor.replaceDoc(doc)

I already thought about this. Would it solve your problem if doc were reactive? Currently the editor do not update itself whenever the doc prop changes.

that would solve the problem definitely.
I tried destroyEditor() change doc and initEditor(), but since it happens in the same cycle things didn't work as expected : )

A reactive doc prop would solve the same issue for my wiki project, which lets the user view older versions of the page and does so by modifying that prop.
Calling the destroyEditor and initEditor hooks fixed this issue for me in my project, but it would always render doc from one click ago, rather than the one on the current click, if that makes sense. I fixed that with this.$nextTick, like so:
<template>
  ...
  <tiptap-editor ref="editor"
          :doc="document"
          :editable="!history_id"
          :extensions="tiptap_extensions"
          @update="editor_update">

  </tiptap-editor>
  ...
</template>

In v0.12.0 the editor re-renders on changes to doc. There is also a setContent() function if you want to update the content manually (this.$refs.editor.setContent(doc)).

thank you for fast response.
I have one small suggestion, maybe emitUpdate should be false by default. I'm not sure that replacing the doc is same as update.

Good point! Wasn‘t sure about this one. Will change it.

In v0.12.1 it is set to false by default


Custom highlights don't work

The highlights are defined inside the setup() function with command highlight! so my custom highlights won't work if I define them earlier (I'm lazy loading fidget.nvim). With this diff I can work around the problem:
diff --git a/lua/fidget.lua b/lua/fidget.lua
index cdd20a7..5dc5ea7 100644
--- a/lua/fidget.lua
+++ b/lua/fidget.lua
@@ -246,8 +246,12 @@ function M.setup(opts)
     options.text.spinner = spinner
   end
   vim.lsp.handlers["$/progress"] = handle_progress
-  vim.cmd([[highlight! default link FidgetTitle Title]])
-  vim.cmd([[highlight! default link FidgetTask NonText]])
+  if vim.fn.hlexists('FidgetTitle') ~= 1 then
+    vim.cmd [[highlight default link FidgetTitle Title]]
+  end
+  if vim.fn.hlexists('FidgetTask') ~= 1 then
+    vim.cmd [[highlight default link FidgetTask NonText]]
+  end
 end

 return M

But there is also a problem with winhighlight that makes the text color dimmed or brighter. Here are the screenshots for the same settings on different buffers:

The colors in used here are #b48ead (for FidgetTitle) and #d8dee9 (for FidgetTask) and I'm using Neovim v0.6.1 in Alpine Linux.

Ok so I think there's actually two things going on here, both related to the kind of confusing way highlights in Vim work.
First of all, I shouldn't have used highlight!, which effectively elevates the precedence of default link and forces the link. I fixed that in a5039a5.
hi default link Foo Comment
" hi Foo -> Comment
hi Foo guifg=blue
" hi Foo := guifg=blue
hi default link Foo Comment
" hi Foo := guifg=blue

What adds another layer of confusion here is that when you set your colorscheme, any non-default highlights will disappear, and it will revert to the default highlight. I suspect what's going on is that your highlights were cleared during a colorscheme switch at some point.
You may want to wrap them in an autocmd:
augroup fidget-highlights
  autocmd!
  autocmd ColorScheme * highlight FidgetTitle guifg=#b48ead
  autocmd ColorScheme * highlight FidgetTask guifg=#d8dee9
augroup END

(Alternatively, put both highlight statements in a function and call that from the autocmd.)
Does that work for you? If so, I can add this to the documentation.

I use my own colorscheme though (which is part of my config) and it is loaded with :colorscheme myscheme. I do have a 'hi clear' command before defining my own highlights, but it shouldn't interfere (as long as I explicitly define them in the colorscheme).
I pulled the latest commit, and can define the highlights now. The result appears the same as the screenshots from my previous message (the screenshots above was after I applied my diff).
I guess for some reason the window highlight is disrupting the defined highlights, which makes the colors look dimmed or bright randomly.
Should I open another issue for this problem? Probably related to #11 as you pointed. What do you think?

Yeah the flaky winhighlights seem to be a different issue. Let's move the discussion to #11 and close this one. We can always revisit this issue or open a new one if #11 turns to be yet a different problem.


A text layout should be able to have indents for consecutive sentences or for the first sentence

Steps to Reproduce
I am trying to layout a poem: when the text line is too long for the widget width, the line should be softwrapped to the next line, with an indent: everybody understands that the sentence should have been on one line.
Also, it is quite familiar to indent the first line of a paragraph. So it should be possible to somehow do s softwrap indent or a first line indent (this could also be negative, so the first line of a sentence protrudes to the left in the case of left-to-right example.
At the moment I resolved it by creating a function that calculates the width of words in a sentence, and when the sentence is too long for the width of the widget, insert a newline and some spaces.
The calculation however, is crude: it does not take into account ligatures and different widths of characters.

If the problem is with your application's rendering, please attach a screenshot and any relevant source code.
If you are getting an exception in the logs, and your code is implicated in the first few frames, then please include the source code for the functions involved.
Logs
Run your application with flutter run and attach all the log output.
Run flutter analyze and attach any output of that command also.
Flutter Doctor
Paste the output of running flutter doctor here.
breitlings:examples johan [master] $ flutter doctor
[✓] Flutter (on Mac OS X 10.13 17A365, locale en, channel master)
• Flutter at /Applications/Developing/flutter
• Framework revision a08b5e00af (9 hours ago), 2017-09-25 18:56:37 -0700
• Engine revision 005212683c
• Tools Dart version 1.25.0-dev.11.0
[✓] Android toolchain - develop for Android devices (Android SDK 26.0.1)
• Android SDK at /Applications/Developing/android-sdk-mac_x86
• Platform android-26, build-tools 26.0.1
• ANDROID_HOME = /Applications/Developing/android-sdk-mac_x86
• Java binary at: /Applications/Developing/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.0, Build version 9A235
• ios-deploy 1.9.2
• CocoaPods version 1.3.1
[✓] Android Studio (version 2.3)
• Android Studio at /Applications/Developing/Android Studio.app/Contents
• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
[✓] Android Studio (version 2.3)
• Android Studio at /Applications/Developing/Android Studio.app/Contents
• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
[✓] IntelliJ IDEA Community Edition (version 2017.2.4)
• Flutter plugin version 17.0
• Dart plugin version 172.4155.35
[✗] Cannot determine if IntelliJ is installed
✗ Directory listing failed
[✓] Connected devices
• LG H440n       • LGH440n1a15d72                           • android-arm • Android 6.0 (API 23)
• iPad van Johan • bd30d3f168d079bd5e41a905a26d8c040afcd02a • ios         • iOS 11.0

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.

Added an entry to https://github.com/flutter/flutter/issues/224.


Avoid failing test on cleanup when filesystem has issues

Signed-off-by: Alessandro Bellina<EMAIL_ADDRESS>Closes https://github.com/NVIDIA/spark-rapids/issues/6515.
This fixes a sporadic issue in CI where we have seen failures when cleaning up temporary shuffle data, when what looks like NFS is failing to delete. We create a new temporary directory for each test, and we are not writing a ton of data, so I feel is fairly safe to ignore this.

I'm assuming this is tempDir so at the end of the tests this ends up being cleaned up anyway, right?

No this is created using Spark's Utils.createDirectory. It is not a java temp dir. It is normally cleaned by the SparkContext on shut down. Do we want to change this to be a java temp directory? Might be better...
The function I changed here was copied verbatim from Spark's BypassMergeSortShuffleWriterSuite.scala

I'd say as long as its cleaned when SparkContext shut down it should be fine, if we run into issue we can revisit.

I'd say as long as its cleaned when SparkContext shut down it should be fine, if we run into issue we can revisit.

Verified that the directories would be deleted by the shutdown hook if I don't:
22/09/29 12:11:32.492 shutdown-hook-0 INFO ShutdownHookManager: Shutdown hook called
22/09/29 12:11:32.492 shutdown-hook-0 INFO ShutdownHookManager: Deleting directory spark-a15133fc-e34a-4120-b98a-8bf8e44bc19a
...

Also this hook catches all Exception and throws them away (but logs them).

build

Could not transfer artifact org.apache.maven:maven-settings-builder:jar:3.0.3 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings-builder/3.0.3/maven-settings-builder-3.0.3.jar.

retriggering

build

@tgravescs @gerashegalov mind taking another look?

integration tests failed on:
329858 [2022-09-29T19:20:59.531Z] FAILED ../../src/main/python/explain_test.py::test_explain_bucketd_scan[ALLOW_NON_GPU(ANY)]

329842 [2022-09-29T19:20:59.531Z] converted = AnalysisException('java.lang.RuntimeException: The root scratch dir: /tmp/hive on HDFS should be writable. Current per...che.spark.sql.hive.HiveExternalCatalog.withClient(HiveExternalCatalog.s       cala:102)\n\t... 21 more\n', JavaObject id=o404)

I am retriggering.

build


Communities as a native feature

I would like to see a community as a different type of post (publicationTypes: COMMUNITY) that would allow me to work easily with the communities in a similar way the lenster does this. On top of publication POST functionality, it will be nice to be able to fetch communities I subscribed to and fulltext search.

Hey Adam, we have plans to bring native community feature to Lens. If you, or anyone reading, have any ideas for community features feel free to drop them here!


Behavior documentation

This pull request adds documentation to the behaviors.
Please have a look to see if it conforms with the expectations. Want 2 approves on this.

It is for some reason not possible to assign Neovici/frontend here.

@dotpointer Is this PR still relevant? I would like to rebase and merge this branch.

@dotpointer @nomego rebased this branch and submitted as separate PR (because I cannot push to this repo) https://github.com/Neovici/cosmoz-behaviors/pull/28

Closing in favor of #28


Add example of using credentials in GS backup/restore URI

need to add example of how to use GS CREDENTIALS parameter in backup/restore URI

https://github.com/cockroachdb/vendored/blob/master/golang.org/x/oauth2/google/default.go#L61
an example of using the credentials in the backup URI is fine. i also think it’s prob ok to provide some info on how to set the cluster setting since it’s in CRDB. i don’t think including steps on how to generate the keys is necessary

After researching a bit more, I think the guidance and links we provide are sufficient.


Auto-provided JDK does not work with Mac OS ARM

Hi, I was just testing AEMC and I'm very impressed ! Great work @krystian-panek-wttech .
However I found a minor bug in your config:
On my MacBook Pro with Apple M1 chip running Mac OS Ventura 13.6.1 auto provided JDK does not work.
ERRO[2023-10-26 15:52:32] cannot check java version properly: '': fork/exec /Users/xxx/IdeaProjects/xxx-aem/aem/home/opt/java/jdk/jdk-11.0.18+10/Contents/Home/bin/java: bad CPU type in executable
task: Failed to run task "aem:setup": exit status 1

changing this options:
      # enforce non-ARM Java as some AEM features are not working on ARM (e.g Scene7)
      "arm64": "x64"
      "aarch64": "x64"

to
      # enforce non-ARM Java as some AEM features are not working on ARM (e.g Scene7)
      "arm64": "aarch64"
      "aarch64": "aarch64"

fixes the issue.

Thanks for the feedback.
It is intentional because as stated in comment AEM is not officially working on AEM. Moreover scene7 as far as I know does not work at all... That's why I am forcing to install non-arm java I on arm. It works but you then need to have rosetta installed on your mac. And that part is missing here. I just haven't documented that. I will document it thanks.


Updated Workflow Files

Updated workflow files to send events to RabbitMQ

Building VM-Manager Code. For more details refer below link:
job/satg-aee-android-ci/job/TEST-VM-MANAGER-PR-FLOW/39/

Build successful.
job/satg-aee-android-ci/job/TEST-VM-MANAGER-PR-FLOW/39/

Please find the Deb Package Path :
artifactory/dev-automation-ba-local/vm-manager-binaries/342/PR/fcfdbcf


Deadlock if aeron::Aeron object destroyed too quickly

I managed to get a deadlock by destroying an aeron::Aeron object too quickly after its construction. It happens if m_isRunning = false in AgentRunner::close executes before atomic_compare_exchange_strong in AgentRunner::run (which sets AgentRunner::m_isRunning back to true thus the spawned thread never exits).
Should it be that AgentRunner::run checks while (!m_isClosed) instead of while (m_isRunning)? I think that would fix it so that a close-request can't be "missed". Or can you see a better way to fix this? Thanks!

Can you check if this works for you now?

Thanks for the quick patch. I think this may now crash if if (m_isRunning) in close runs before m_isRunning = true; in run (because m_thread never gets joined so calls std::terminate in its destructor).

Just tested this and no more deadlock - thanks again.


Accessibility Unit Testing

Background on the problem the feature will solve/improved user experience
Five Fifths Voter users with accessibility needs should be able to use our solution without limitations.
Describe the solution you'd like
Unit testing is needed to identify if Level 1 accessibility requirements are met. IBM has a robust process for guaranteeing accessibility athttps://www.ibm.com/able/. This is publicly available as a reference for creating, designing, and testing for accessibility needs.
Tasks

Unit test of 5/5 voter website (can use https://www.ibm.com/able/toolkit/verify)
Check against Level 1 accessibility requirements [select Level 1 in Level to Achieve on left hand side filter pane]

Acceptance Criteria

Checklist of Level 1 accessibility requirements met or failed
Path forward to meeting 75% of the 21 requirements under Level 1

Accessibility_Report-five-fifths voter.xlsx

Fiewor - these are the 2 most critical issues (copied from the spreadsheet attached above):

[ ]     The element with "menuitem" role is not contained in or owned by an element with one of the following ARIA roles: "group, menu, menubar"
[ ]      The 'id' "user-panel" specified for the ARIA property 'aria-controls' value is not valid

Hmm I actually see different violations compared to what is attached in the spreadsheet. I see:

[ ] Content is not within a landmark element

What to do
Enclose the content within an HTML5 sectioning element with an implicit landmark role (e.g. Content);
Or, use the "role" attribute on an enclosing element to specify an appropriate ARIA landmark value (e.g.
...
).

[ ] Content is not within a landmark element

What to do
Enclose the content within an HTML5 sectioning element with an implicit landmark role (e.g. Content);
Or, use the "role" attribute on an enclosing element to specify an appropriate ARIA landmark value (e.g.
...
).

[ ] The 'id' "user-panel" specified for the ARIA property 'aria-controls' value is not valid
What to do

Update the ARIA property value with the unique id value of a valid visible element.

For example:
<form action="" method="post">
  Last Name
  <input type="text" name="lastname" id="ln1" value="enter last name" title="enter last name" aria-describedby="ln2">
</form>

Last Name must be alpha only characters

[ ] Multiple elements with "navigation" role do not have unique labels
What to do

For each element with a "nav" role, either set the value of the aria-labelledby attribute to the id value of any visible text that appropriately and uniquely describes that navigation region;
Or, use the aria-label attribute to add an invisible, unique, non-empty label to an element with the "nav" role.

For example:

Weather portlet

    ...

        ...

I cannot reproduce the The element with "menuitem" role is not contained in or owned by an element with one of the following ARIA roles: "group, menu, menubar" issue that was originally reported. Maybe it has been fixed since the report was run. I see that the all "menuitem" are in a "menubar".

Alright. Let me take a close look

@upkarlidder this is the issue we discussed on the scrum but the title I think may be off? I think we discussed just getting fixes for the existing accessibility issues but this one calls for unit tests.
The unit tests is a bigger ask so I think we continue tracking accessibility fixes here and, once complete, work on a unit test. Maybe that is your intent too. Just making sure we are aligned.

I agree @davidnixon. Let's change the title to Identify and fix  Level 1 accessibility issues. And I can create a new one for adding accessibility testing as a requirement in CI/CD pipeline. Would that work?
FYI @Sabine-Justilien @demilolu

@upkarlidder @davidnixon can you help here?

@Fiewor I see why you are stuck. There seems to be some leftovers here from a different navigation that is no longer available.
This code has a label already but i looks like just a placeholder. I think that one should be something like "main menu"
https://github.com/Call-for-Code-for-Racial-Justice/Five-Fifths-Voter/blob/efbe06b3c8147c6d0d5b2182e5482582da688861/ui/src/components/AppHeader/AppHeader.vue#L10
And this code has a nav container but it is never visible because areLeftPanels is always false
https://github.com/Call-for-Code-for-Racial-Justice/Five-Fifths-Voter/blob/efbe06b3c8147c6d0d5b2182e5482582da688861/ui/src/components/AppHeader/AppHeader.vue#L29-L48
I suggest this:

[ ] Update the aria label on cv-header-nav
[ ] Delete the entire template v-slot:left-panels and its content<template v-slot:left-panels v-if="areLeftPanels">
...
</template>

[ ] Since areLeftPanels is never used, remove it from the components datadata() {
return {};
}

Alright. Thank you. I was stuck. I'll do that.

are we set to close this :)? I'm also looking for your pull request @Fiewor where is it :)

I have opened a pull request @demilolu  but I'll have to close it and send another one because @davidnixon has pointed out some errors that I have to correct

@Fiewor FYI you should be able to push new commits to an open pull request. No need to close/reopen.

+1 @krook
@Fiewor if you commit to the same branch in the remote, it pushes to the same PR as a new commit. Your PR can have multiple commits. GitHub is smart to recognize that you are working on the same branch. If you deleted the branch locally, recreate with the same name and push.

Oh. I didn't know that. Thank you. I'll do this .


Inconsistent Results when Executing Statements in a Loop

SQL Operations Studio Version:

0.23.6 (0.23.6)

Background:
I often find myself writing scripts to perform a series of tasks against a list of entities, for example, calling a sproc n times where n = a list of ids I need to work with.
I've always preferred to perform these tasks using a simple loop instead of a cursor.
In SQL Operations Studio, I see inconsistent results of executing this looping logic - it seems the first one or two iterations function as I'd expect, but after that I don't see the results I would traditionally see if I executed the script using SSMS.
Steps to Reproduce:
I've attached a small sample script that should reproduce the behavior.
What I Would Expect to See from the attached Script

I would expect my loop to execute 10 times, and I would expect to see 10 result sets, each outputting the text "Working With {N}" where {N} is replaced by the record ID of the processed record.

What I see Instead:

I see the loop execute 10 times, but the result sets are inconsistent. I see 1 to 3 actual results sets where the expected text is returned. The other expected result-sets have no returned data.

In SSMS:

The same script executes and behaves as expected.

sqlOps_LoopBug_ReproScript.txt

I was unable to reproduce this bug with the script you provided (also on 0.23.6).  I did notice, however, that there is a noticeable delay on the result sets data (the header loads immediately) when scrolling.  If I scroll quickly and then stop, then the results show after a brief delay, even if I have already viewed them.

@arinwt That's really odd! I ran this multiple times before submitting this issue, and each time I paused as I scrolled through the list of results and never saw anything show up past the first 3!
I just re-ran the script and now it works as you describe.
For what it's worth, the "actual" script I observed this in I was calling into a sproc multiple times with different sets of parameters and saw only the first few executions return data. I expected results, so ran the process in SSMS and immediately saw the results I was looking for. Went back to SQL OPS and saw the reported behavior, so I created a simple script to illustrate what I was seeing.

@tlentine I wasn't able to repro this on the latest build with the attached script.  I saw similar to @arinwt where there is a small delay to render the result sets when scrolling.
That said, we do have other active bugs related to failed rendering with lots of resultsets, so perhaps we may fix the underlying issue here when we resolve those.  Please reactive if you're still hitting this issue.  Thanks!


nice mod

but how does it works? I don't understand japanese
I'm just among us hacker

This script is just a deployment script. not a MOD itself.
Run bat file w/ your own risk.
https://github.com/Maximilian2022/AmongUs-Mod-Auto-Deploy-Script/releases/download/latest/StartAmongUsModTORplusDeployScript.bat
when you run bat, it downloads latest ps1 file and run it.
ps1 file will check ps v7 is in there or not, and install ps v7 if not installed.
if ps1 file install ps v7, then you need to re-run bat file.
after you re-run batfile, you may see GUI.
if you are installing original amongus folder w/ custom place, then you need to specify where is original amongus installed folder.
after that, plz read following. you may need google translate.
https://github.com/Maximilian2022/AmongUs-Mod-Auto-Deploy-Script/wiki/このScriptでやってること
https://github.com/Maximilian2022/AmongUs-Mod-Auto-Deploy-Script/wiki


Top Salary Request Filtered to CS Classification

When I query https://ps-salary-data.vercel.app/api/top - Only the 5x CS classifications are available. Thanks a lot for this Doug - another small suggestion would be to include in the description some sense of how you pull the data/and confidence whether this can be relied upon for continual updates.
Cheers from DND

Thanks for catching that!  Will get that one fixed.
And a great suggestion on adding how it was collected too.  All scraped from the website. In an ideal world we would have it accessible as a dataset from something like open.Canada.ca but after going through it myself I can understand how having a 100% complete set would be difficult to obtain within a single data model.
There are a lot of complexities around the edges of classifications.
Can definitely be achieved but will break the simplicity of this MVP.
Really appreciate the comments


PhantomJS 2.0 (on mac osx) gets confused after taking a screenshot

In our setup we are using PhantomJS to run Readium ePub Reader, page through the
book and take a screenshot of every page. It works fine as long as the page's
viewport height >= 500.
However when viewport height < 500, JS evaluation gets confused, pages are not
properly opened, timer events are not fired at expected time intervals etc.
Here is the code excerpt that gives the idea of what we are trying to do:
page.viewportSize = { width: width, height: height };
page.onConsoleMessage = function (msg) { console.log("-> " + msg); };
// handle callback from the JS executing in the page
// called to signal that page was loaded and ready for the snapshot
// also contains a flag indicating that this is the last page
page.onCallback = function (lastPage) {
// if this is the last page
if (lastPage) {
console.log("Last page - exiting Phantom");
phantom.exit();
}
// take a snapshot
pageNumber++;
var fileName = options.output + "_" + pageNumber + ".png";
console.log("taking snapshot in a file " + fileName);
page.render(fileName);

// signal back to the page that snapshot is ready
console.log("Calling PhantomPageSnapshots.snapshotReady()");
page.evaluate(function() {
    PhantomPageSnapshots.snapshotReady();
});

Any ideas of what may be going wrong ?
thanks, Michael

Thank you for submitting this ticket!
This issue tracker primarily serves as the tool to report and track bugs, defects, and development tasks.
For general question, code review request, or other related discussion, please post it to either:

the official PhantomJS users mailing-list
Stack Overflow (with phantomjs tag)

If you have not read it yet, please check also a few tips on Effective Q&A.


Laravel Breeze

Shouldnt the package be compatible with Laravel Breeze?

The package isn't compatible with the latest Laravel at all...


Distributed Experiment Support

I recently started using sacred and enjoy it a lot! However may of my experiments are distributed across either GPUs or also across machines. Take horovod for example, which uses MPI to execute the training script once for every GPU. Are there currently any solutions to using sacred to capture distributed experiments? Or are there any plans for enabling this?
Thx!

That is an interesting problem, thanks for bringing it up. So far I have only used Sacred with experiments that have a central collection point. So even if they were distributed there was a kind of master process, and I would only use sacred in that process. But if I understand your usecase (and horovod) correctly, then you are interested in a pool of equal workers that collaborate on one experiment. Maybe the individual workers might even change, but the overall experiment should stay the same. Is that what you have in mind?
So far I haven't thought about this usecase, and I suspect it would require some careful thought. But if you want we can discuss this here, and once we are clear on the requirements I'd be happy to try and incorporate it.
Note however that I'll be on vacation until early July, so I won't be able to react until then.

While the use-case you describe is certainly interesting, it is the simpler scenario with the master process that I am trying to enable. The situation with horovod is that experiments are launched via the MPI interface. Each worker therefore executes the same script which, as far as I understand sacred, would cause many "starts" of (identical) sacred experiments. Now horovod allows to access the workers "rank", where rank=0 denotes the "master" of the pool of workers. In theory what would be enough is that I can configure sacred to not record or connect to mongodb unless the worker has rank 0. I would require it to fill in configurations though.
Now that I am describing it it doesn't sound so difficult.
I will have need for this functionality in the coming weeks and will post a minimum working example here once it is done.

Maybe you could do something like this (using @main instead of @automain)?
if __name__ == '__main__':
    rank = ...
    args = list(sys.argv)
    if rank != 0:
        args.append('--unobserved')
    ex.run_commandline(args)


Revert "ARTEMIS-2240 ActiveMQThreadPoolExecutor should use LinkedTransferQueue"

This reverts commit ea294834

Nudge nudge @michaelandrepearce I have performed some single-producer single-consumer tests with 100 bytes messages and no persistence (core protocol) and I have found several interesting things:

the new thread pool theoretically should scale way better then the original: there are no more locks associated to the tail/head of the linked blocking task queue
the new thread pool try to reuse dormient and existing threads, but it means that with few producers/consumers then avaialble threads the cost to wakeup them will add a huge latency hit (the percentiles show it for small burst) :(

This is a regression if compared with other commits:

7dfa0fe7f43012f2f4ee5715049878019fe0bef7
71d549434591715c1f02359000e424e4d7dfbfda
https://github.com/apache/activemq-artemis/tree/2.6.4

I suggest anyone that has enough cores to perform tests on these commits and check the latencies/throughput, because although on my box the throughput is not that different, the performance regression is evident on latency side.
Shame on me that I have trusted that a lock-free q would have performed better in any case: the cost to scale better is just too high and I think is better to work after the release to improve the thread pool.

The commits you reference are other features a bit confused why your referencing them

@michaelandrepearce
I have added them for a specific reason :)
The 2.6.4 tag was my original baseline, while 7dfa0fe7f43012f2f4ee5715049878019fe0bef7 was my original bet about the reason of the regression and 71d549434591715c1f02359000e424e4d7dfbfda was the commit right before it (that I have used to validate that  7dfa0fe7f43012f2f4ee5715049878019fe0bef7 wasn't guilty of anything).
I have already tried the commit that has introduced the new thread pool too and reverting it and master + this PR too: my box always report the new thread pool as the source of the latency regression.

So where is this putting us back to. My original ? Or the version we had perf issue with?

I've reverted the change in order to use the first revert you did on the thread pool: I know that is twisted

please, use the complete commit on the this Reverts to..
3 reasons: the report I wrote only takes full commit IDs. Second: I don't want to change it as I don't have time;)
3rd.. pretty please?

Ok merge it.

I will merge it, but referencing the whole commit ID... leave it with me

Guys if you have better machines then mine don't you want to give a shot?

@clebertsuconic Fixed the commit hash message


[SPARK-45955][UI] Collapse Support for Flamegraph and thread dump details

What changes were proposed in this pull request?

This PR supports collapse flamegraph and thread dump details like other pages
https://github.com/apache/spark/assets/8326978/ea5e224b-7edf-4bcd-bd83-c4243cdd7e58
Why are the changes needed?

UX improvement for UI
Does this PR introduce any user-facing change?

yes， UI changes
How was this patch tested?

As shown in the above video
Was this patch authored or co-authored using generative AI tooling?

no

Thank you @dongjoon-hyun

Merged to master!

Late LGTM. Thank you @yaooqinn !

Thank you very much @sarutak !


Crash on Windows

There is a crash every now and then on Windows due to an unwrap() inside the library. This PR https://github.com/carllerche/mio/pull/401 intends to fix that.

Thanks for the fix!


XIVY-7171 Add deprecation page

Please add a simple test DeprecationActionTest.php
have a look e.g. TeamActionTest.php
This is really simple to write and will test the hole stack which you have implemented.
To execute test: see README.md

Hi @alexsuter
I've done:

the formatting stuff
Put deprecated features into json file
Cleanup
I've not done so far but will in a separate PR:
Tests
Get versions from ReleaseInfoRepository

I think it is good enough for 9.3 release. Will work on Monday on followup PR


⚠ gorzdrav.org has degraded performance

In affd021, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 1856 ms

Resolved: gorzdrav.org performance has improved in 3df443c.


Allow choosing programming language

I would like the ability to choose which languages the editor allows switching between. For example:

Hide blocks and only show one language (JavaScript or Python).
Hide text languages and only show blocks.
Allow blocks and allow one of the text languages.

@EdwinSaenz I am assuming you are hosting the arcade.makecode.com in an iframe right?

@abchatra yes, that is correct. I'm passing the ?controller=1 argument.


Be live during state clone for full replays

When we need to do a full replay, we currently do a synchronous clone of the source operator's state. This holds up processing other writes and backfills through that operator, which is sad. If we could find some kind of data-structure that allowed us to efficiently capture a snapshot of it which we could then use for the backfill, that'd be awesome!

@ekmartin has been thinking about this I think.


core: do not persist Policy contract

Close #1389 .
I have decided to exclude Policy instead of enumerating NEO and GAS, because calling onPersist seems like a default behaviour and can be tested.

It's a little strange for Policy contract to still have OnPersist in the manifest, but not really use it.


AFL_LLVM_LAF_SPLIT_FLOATS breaks bogofilter

When compiling the bogofilter project from sourceforge, AFL_LLVM_LAF_SPLIT_COMPARES breaks the binary. Although the first run of the binary will work as expected, because the bogofilter home directory is not yet populated, the second invocation will result in an abort:
$ /targets/bogofilter-1.2.5/build-afl/src/bogofilter -e -u -p -d ./home_bogofilter/ < /targets/bogofilter-1.2.5/src/tests/inputs/dump.load.inp
gsl: ../../src/../gsl/specfunc/gamma_inc.c:449: ERROR: domain error
Default GSL error handler invoked.
Aborted

This looks like https://github.com/ampl/gsl/blob/master/specfunc/gamma_inc.c#L503 is hit with the AFL binary:
int
gsl_sf_gamma_inc_Q_e(const double a, const double x, gsl_sf_result * result)
{
  if(a < 0.0 || x < 0.0) {
    DOMAIN_ERROR(result);
  }

AFL binary with ASAN has the same problem. Vanilla clang and clang-ASAN binary with no AFL involvement work as expected and do not produce the above error.
Doing an unset AFL_LLVM_LAF_SPLIT_COMPARES AFL_LLVM_LAF_SPLIT_FLOATS before compiling with cd build-afl && CC=afl-clang-fast CXX=afl-clang-fast++ CFLAGS="-Wno-error" ../configure && CFLAGS="-Wno-error" make && cd .. creates a valid binary that does not have the problem. I expected that because this looked like a split-compare issue and it seems to be one. Do you agree?
Let me know if you need any further information.

Thanks, that depends on AFL_LLVM_LAF_SPLIT_FLOATS=1, so the error is confirmed.
I could not reproduce with only AFL_LLVM_LAF_SPLIT_COMPARES=1 set (like the title suggested).
Will investigate...

oh yeah, sorry about that, it is really AFL_LLVM_LAF_SPLIT_FLOATS of course (I enabled it by default in my docker image...)

So, i think i fixed the issue with commit https://github.com/vanhauser-thc/AFLplusplus/commit/064cd3315c2c31a26eef5fd0f70d6fd2c77ef0f8. Could you please retest?
Thanks!

This seems to have fixed it, thank you!
Btw. we haven't announced it yet, but there is https://github.com/pentagridsec/5-AFL-suite-docker now. I can recommend using containers, it makes it much easier to get reproducible builds and realizing things about dependencies.

Great! We should add that to our docs after the official announcement.


Beginning work on converter

Starting work on the converter, which aims to take an HTML element and reproduce it accurately in the physics simulation. The goal is to account for various positioning methods and transforms. Go to /converter/ to see it in action. There are 4 divs with different styles and the physics canvas is overlaid on top to show if if they are getting represented correctly in the simulation. Looks like this...

Mostly everything works, it gets tricky when you start mixing rotation and scale in the transform rules, as well as setting different scales for the X and Y dimensions (this is see in the error on the red box in the top left).
For scaling, we can also apply it after we initially build the object instead of when we first create it. As there is a Matter.Body.scale(body, scaleX, scaleY, [point]) method we can call.
Also eventually we should account for the border radius property and if something is "round enough" make it into a circle.

Here's a breakdown of how to break down a matrix transformation into it's component parts...
https://math.stackexchange.com/questions/13150/extracting-rotation-scale-values-from-2d-transformation-matrix/13165#13165

@pomax - is that something you have done before? The problem is such.

We modify an element with a bunch of transforms (mix or rotate, scale, etc) via CSS
When the element is rendered, we ask for it's transform properties via getComputedStyle
The transforms we applied are baked into a matrix transform

Ex - matrix(0.984808, 0.173648, -0.173648, 0.984808, 38.2266, -44.0309)

Do you know how to break this back down into the original transforms

Rotation
Scale X / Scale Y

👍 this is awesome. Shame you can't just plug this matrix into the physics engine.

Don't merge yet please, updating.

It looks like the only one that's wrong is the skewed one, right? In that case, it should just be an ordering thing.

If we want to try to find the skew/shear for objects, https://stackoverflow.com/questions/5107134/find-the-rotation-and-skew-of-a-matrix-transformation is a good enough starting point. But, we'd have to create polygons each time, and try to get each vertex in the right spot.

whoa, activity. What's going on, anything cool happening?

Heya @Pomax - yeah check out this comment here...
https://github.com/secretrobotron/games/pull/7#issuecomment-329975663
In a nutshell, we are building a little platform that uses the matter.js physics library to interact with the DOM. So, one of the first pieces is to accurately convert what's happening in a DOM into the physics simulation (parsing all the properties and creating "physics" objects). The harder part.
Second, to then run the simulation and update the DOM as necessary <- the easier part.

What's the matrix size here? For a 4x4 matrix the decomposition is pretty exact (see https://math.stackexchange.com/questions/237369) so I'm pretty sure we can find the solution for whatever this 6 argument matrix represents.


Resolve package conflicts and errors

Here's a list of npm warns:
npm warn ERESOLVE overriding peer dependency
npm warn While resolving<EMAIL_ADDRESS>npm warn Found<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   dev<EMAIL_ADDRESS>from the root project
npm warn   44 more (@design-systems/utils, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm warn node_modules/@storybook/addon-actions/node_modules/react-inspector
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/addon-actions
npm warn
npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/addon-actions/node_modules/react-inspector
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn     node_modules/@storybook/addon-actions
npm warn ERESOLVE overriding peer dependency
npm warn While resolving<EMAIL_ADDRESS>npm warn Found<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   dev<EMAIL_ADDRESS>from the root project
npm warn   44 more (@design-systems/utils, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm warn node_modules/@storybook/addon-docs/node_modules/@mdx-js/react
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/addon-docs
npm warn
npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/addon-docs/node_modules/@mdx-js/react
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn     node_modules/@storybook/addon-docs
npm warn ERESOLVE overriding peer dependency
npm warn While resolving<EMAIL_ADDRESS>npm warn Found<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   dev<EMAIL_ADDRESS>from the root project
npm warn   44 more (@design-systems/utils, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer<EMAIL_ADDRESS>|| ^15.0.1 || ^16.0.0 || ^17.0.1" from<EMAIL_ADDRESS>npm warn node_modules/@storybook/react/node_modules/react-element-to-jsx-string
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/react
npm warn
npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm warn node_modules/react
npm warn   peer<EMAIL_ADDRESS>|| ^15.0.1 || ^16.0.0 || ^17.0.1" from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/react/node_modules/react-element-to-jsx-string
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn     node_modules/@storybook/react
npm warn ERESOLVE overriding peer dependency
npm warn While resolving<EMAIL_ADDRESS>npm warn Found<EMAIL_ADDRESS>npm warn node_modules/react-dom
npm warn   dev<EMAIL_ADDRESS>from the root project
npm warn   34 more (@design-systems/utils, @storybook/addon-actions, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer<EMAIL_ADDRESS>|| ^15.0.1 || ^16.0.0 || ^17.0.1" from<EMAIL_ADDRESS>npm warn node_modules/@storybook/react/node_modules/react-element-to-jsx-string
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/react
npm warn
npm warn Conflicting peer dependency<EMAIL_ADDRESS>npm warn node_modules/react-dom
npm warn   peer<EMAIL_ADDRESS>|| ^15.0.1 || ^16.0.0 || ^17.0.1" from<EMAIL_ADDRESS>npm warn   node_modules/@storybook/react/node_modules/react-element-to-jsx-string
npm warn<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm warn     node_modules/@storybook/react
npm warn deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm warn deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm warn deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm warn deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm warn deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm warn deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm warn deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm warn deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

Time to get cracking!

Following #3, here's the new npm audit output:
 npm audit
# npm audit report

babel-traverse  *
Severity: critical
Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code - https://github.com/advisories/GHSA-67hx-6x53-jw92
No fix available
node_modules/babel-traverse
  babel-core  5.8.20 - 7.0.0-beta.3
  Depends on vulnerable versions of babel-helpers
  Depends on vulnerable versions of babel-register
  Depends on vulnerable versions of babel-template
  Depends on vulnerable versions of babel-traverse
  Depends on vulnerable versions of json5
  node_modules/babel-core
    babel-cli  *
    Depends on vulnerable versions of babel-core
    Depends on vulnerable versions of babel-register
    Depends on vulnerable versions of chokidar
    node_modules/babel-cli
    babel-register  *
    Depends on vulnerable versions of babel-core
    node_modules/babel-register
  babel-template  *
  Depends on vulnerable versions of babel-traverse
  node_modules/babel-template
    babel-helpers  *
    Depends on vulnerable versions of babel-template
    node_modules/babel-helpers

braces  <=3.0.2
Severity: high
Regular Expression Denial of Service in braces - https://github.com/advisories/GHSA-g95f-p29q-9xw4
Regular Expression Denial of Service (ReDoS) in braces - https://github.com/advisories/GHSA-cwfw-4gq5-mrqx
Uncontrolled resource consumption in braces - https://github.com/advisories/GHSA-grv7-fg5c-xmjg
No fix available
node_modules/chokidar/node_modules/braces
node_modules/readdirp/node_modules/braces
  micromatch  0.2.0 - 3.1.10
  Depends on vulnerable versions of braces
  Depends on vulnerable versions of braces
  node_modules/chokidar/node_modules/micromatch
  node_modules/readdirp/node_modules/micromatch
    anymatch  1.2.0 - 1.3.2
    Depends on vulnerable versions of micromatch
    node_modules/chokidar/node_modules/anymatch
      chokidar  1.3.0 - 1.7.0
      Depends on vulnerable versions of anymatch
      node_modules/chokidar
    readdirp  2.2.0 - 2.2.1
    Depends on vulnerable versions of micromatch
    node_modules/readdirp

json5  <1.0.2
Severity: high
Prototype Pollution in JSON5 via Parse Method - https://github.com/advisories/GHSA-9c47-m6qq-7p4h
No fix available
node_modules/babel-core/node_modules/json5

12 vulnerabilities (2 low, 6 high, 4 critical)

To address issues that do not require attention, run:
  npm audit fix

Some issues need review, and may require choosing
a different dependency.

It seems like all the issues stemmed from Babel.  In #3 I selected "SWC" as the new tool, so after deleting babel dependencies they should be gone.

New npm install reveals these warns:
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

 npm outdated
Package                    Current   Wanted   Latest  Location                                Depended by
@changesets/cli             2.23.0   2.27.7   2.27.7  node_modules/@changesets/cli            react-hexgrid
@emotion/react              11.9.3  11.13.0  11.13.0  node_modules/@emotion/react             react-hexgrid
@emotion/styled             11.9.3  11.13.0  11.13.0  node_modules/@emotion/styled            react-hexgrid
@testing-library/jest-dom   5.16.4   5.17.0    6.4.8  node_modules/@testing-library/jest-dom  react-hexgrid
@testing-library/react      13.3.0   13.3.0   16.0.0  node_modules/@testing-library/react     react-hexgrid
@types/jest                 28.1.5   28.1.8  29.5.12  node_modules/@types/jest                react-hexgrid
classnames                   2.3.1    2.5.1    2.5.1  node_modules/classnames                 react-hexgrid
fsevents                    1.2.13   1.2.13    2.3.3  node_modules/fsevents                   react-hexgrid
jest                        28.1.3   28.1.3   29.7.0  node_modules/jest                       react-hexgrid
jest-environment-jsdom      28.1.2   28.1.3   29.7.0  node_modules/jest-environment-jsdom     react-hexgrid
react                       18.2.0   18.3.1   18.3.1  node_modules/react                      react-hexgrid
react-dom                   18.2.0   18.3.1   18.3.1  node_modules/react-dom                  react-hexgrid
react-test-renderer         18.2.0   18.3.1   18.3.1  node_modules/react-test-renderer        react-hexgrid
react-transition-group       4.4.2    4.4.5    4.4.5  node_modules/react-transition-group     react-hexgrid
react-use                   17.4.0   17.4.0   17.5.1  node_modules/react-use                  react-hexgrid
ts-jest                     28.0.6   28.0.8   29.2.3  node_modules/ts-jest                    react-hexgrid
ts-node                     10.8.2   10.9.2   10.9.2  node_modules/ts-node                    react-hexgrid
typescript                   4.7.4    4.9.5    5.5.4  node_modules/typescript                 react-hexgrid

#5

following #6:
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead

rimraf, glob, and inflight come from:
jest 29 - jest 30 will bump the various uses of rimraf and glob
react-docgen-typescript-plugin > preset-react-webpack > react-webpack-5 : uses an outdated version of flat-cache, which depends on the offending version of inflight.  I've submitted a pull request to the project.

abab and domexception are no longer used in jsdom 24.  However, upcoming jest-environment-jsdom 30 depends on jsdom 22, which still uses abab and domexception.  I'll open an issue - I'll make a pull request later.

related:#15217

We'll have to wait for jest and react-docgen to upgrade.  In the mean time, these install errors only appear when installing dev dependencies and don't affect the product.


Implement node refresh command

Once a network is deployed, if we need to refresh (setup & start) a single node using solo node setup -i node1, it fails because it generates a new config.txt assuming there is only one node.
Also node start fails because it tries to setup mirror-node with one node.
We should implement solo node refresh command to refresh a single/multiple node with the below functionalities:

It shouldn't generate config.txt

It shouldn't generate new keys

It should not restart the mirror node

It should dump all saved state

It should allow destroying the whole pod....

It should only setup and start the specified nodes.

[ ] required by #186

While solo node refresh is useful, but we need to allow adding a new node.
solo state should maintain a list of all members so that we can generate config.txt when provisioning a new node or refreshing a node.

:tada: This issue has been resolved in version 0.24.0 :tada:
The release is available on:

npm package (@release-0.24.x dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Port Range in Outbound Nat Rule not Possible

To Reproduce
Steps to reproduce the behavior:

Go to 'NAT -> Outbound'
Click on 'New Rule'
Scroll down to 'Source port'
Try to Create a Rule with a Port Range
See error ->   You must supply either a valid port or port alias for the destination port entry.

Expected behavior
Normally a Outbound NAT Entry with the PortRange should be created.
Screenshots
Attached

Environment
Software version used and hardware type if relevant.
OPNsense 20.1.6-amd64
FreeBSD 11.2-RELEASE-p19-HBSD

Please set the correct protocol

The Protocoll doenst matter. I can choose just TCP and get the same Result. Its not possible to add an Range here.
Btw. Pfsense suffered the same Bug some time ago:
https://redmine.pfsense.org/issues/4300

https://github.com/opnsense/core/commit/adbb91289f67f2dfd508df9c45fb15233e117629 should do the trick


Sentence structure & grammar fixes

Great utility! Just thought I would throw in my 2 cents to make it better~

Thank you very much. :)


convert nullhandler, separator from js to ts. fix a line in upload.ts

Functions that guarantees and should only return a number should only return a number i.e. ?? 0 defaults to 0 if there is nothing in the cache, that means the cache contains only numbers here! Change it to return only numbers

Make the key type being string not specific string value

Doesn't have a return type

That can be simplified iirc

This doesn't have a type return yet can be set to the same return type as get since it retursn a response

add type to the isFn variable isFn: boolean = false
Request here might error if received a promise, make it accept both promises and functions?
Also add a return type on it

Fix indentation here
Might need to make a separate pr later so prettier works everywhere

Since the let mysterious_value = ... has no purpose anymore, make it just return the null coalescing operator
What is the/a null coalescing operator?
cache.get("end time") ?? cache.get("start time") ?? 0
if (cache.get("end time") === null) // run strict equality; {   if (cache.get("start time") === null) { // if true aswell     return 0;   } ; };

LGTM but where the rest

 That can be simplified iirc

Could you explain how it can be simplified, since it already looks good imo

It's abit more complicated than I thought but it has to do with changing line 136 of upload.ts

and also changing how the handler works and return promises, then change the way we receive it, I made a bandaid fix of
type formData = { request: { formData: () => FormData } }
which works for now but for now just ignore it 👍

Ill change it on my end when u finish up


fluxcd: 0.10.0 -> 0.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fluxcd/flux2/releases.
meta.description for fluxcd is: "Open and extensible continuous delivery solution for Kubernetes"
meta.homepage for fluxcd is: "https://fluxcd.io"
meta.changelog for fluxcd is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/wz34dwxgq91gdlzka79llv1yhdrl8dfm-fluxcd-0.11.0/bin/flux passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.11.0 with grep in /nix/store/wz34dwxgq91gdlzka79llv1yhdrl8dfm-fluxcd-0.11.0

found 0.11.0 in filename of file in /nix/store/wz34dwxgq91gdlzka79llv1yhdrl8dfm-fluxcd-0.11.0

directory tree listing: https://gist.github.com/3e4d5420e43e8dc3cfa7b3fd808b36bc

du listing: https://gist.github.com/0f3173d8589fbf3d634b02ab90aa5b88

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
fluxcd

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

fluxcd

Maintainer pings
cc @jlesquembre @kalbasit for testing.

Looks like this is duplicated by https://github.com/NixOS/nixpkgs/pull/118318.


RcTerm::Triple and ArcTerm::Triple do not live up to the "cheap clone" promise

One reason for using RcTerm or ArcTerm is that they are cheaper to clone than SimpleTerms (SimpleTerm uses MownStr internally, which may require a new allocation on cloning -- when they own their data).
However, in their current implementation, the Triple variant of RcTerm and ArcTerm are still expensive to clone, as they contain a Box (which also needs a new allocation when cloned). Instead, RcTerm::Triple should contain a Rc<[RcTerm; 3]> and ArcTerm::Triple should contain a Arc<[ArcTerm; 3]>.
This should probably be achieved by adding a second generic parameter to GenericTerm, for the content of the Triple variant.

This should probably be achieved by adding a second generic parameter to GenericTerm, for the content of the Triple variant.

In fact, using Self in generic types seems to be forbidden. An alternative option is to turn GenericTerm into a macro generating the implementation of ArcTerm and RcTerm...

As a side-note, more than ArcTerm, it would be great to have an EcoTerm using EcoString . EcoString has phenomenal properties. It is cheap to clone. And can also be mutable (clone-on-write), and can have small strings (upto 15 bytes) inlined without allocation.
It also has correspondent EcoVec, with same properties. The crate is from typst team,  and also recommonded by rust-analyzer author. Works great in Manas too.

@damoo EcoTerm would indeed be nice. I would rather keep ArcTerm and RcTerm as they don't require additional dependencies, but adding EcoTerm in sophia_term, behind a feature gate, would be a very nice addition...

adding EcoTerm in sophia_term, behind a feature gate, would be a very nice addition...

That would still be a separate issue, though.


Better tests and bugs fix

New search/getByMail method
Better phone handling
Fix cache issues

and more...

Close #1

Close #2 via dcd7fb2


How to access raw image data?

I am attempting to load a dzi that uses 16-bit pngs.
I would like to use an update-viewport handler to update the canvas with those values converted to 8-bit. (Yes, I realize this sounds inefficient, but I am simplifying the use-case here.)
How can I access the original data? Is this even possible?

By default the image is copied to a canvas when it's first drawn and the image is discarded:
https://github.com/openseadragon/openseadragon/blob/eafdc452c9e312f1f69a44bbb0db0023826da92d/src/tilecache.js#L72
I believe you can circumvent that and draw the image to canvas in your own way if you want by hooking it to the tile-loaded event. Something like:
viewer.addHandler('tile-loaded', function(event) {
  var canvas = document.createElement('canvas');
  canvas.width = event.image.width;
  canvas.height = event.image.height;
  event.tile.context2D = canvas.getContext('2d');
  event.tile.context2D.drawImage(event.image, 0, 0);
});

You'd still be converting it to 8-bit, but you could do it however you wanted to.
Does that help?

Thank you. It does help to point me in the right direction.
I am realizing that I will need to load the image via XMLHttpRequest and use a png parser to get at the 16-bit data, which adds additional complication. (There is no good way that I am aware of to get at the raw data of an image element without first dumping it into a canvas, at which point it automatically becomes 8-bit.)
Essentially the use-case is that I have multiple layers that I want to composite with their 16-bit values and then convert to 8-bit and deliver the result to the OSD canvas.
I am wondering if I could maybe make a custom TileSource for this. Is that possible?
The other option is to composite the images server-side and return the 8-bit values and keep things simple for OSD.

It does seem like it should be possible within OSD, but you're right that it would be easier on the server. For the OSD side, take a look at the discussion in https://github.com/openseadragon/openseadragon/issues/1643.


Can't install locally with provided instructions

Hello,
I've been trying to install it a few days go but I get stuck at that part :
You will need to set up the config/database.yml. Copy what is in config/database.example.yml and add the password you used earlier for the epets postgres user
I can't find any file named database.example.ymlin the config file.
Could you provide any help?
Thanks!

I pulled master branch and there a file named database.yml and that's where I added the lines

username: epets
password: mysecretpassword

anyone else?

I'm going to be updating the README tonight with the latest instructions but if you need to override the authentication details then create a .env.local file like this:
DATABASE_URL=postgresql://user:pass@localhost

Whatever you do don't put the database name in that file since that will take precedence over the database.yml file and running the tests will blow away any data you've put in there.

It'd be great if the readme was updated so I didn't have to go hunting for this issue.

I believe the README is now up to date. The only issue I found when running ./bin/setup is this one:
== Removing old logs and tempfiles ==

== Restarting application server ==
touch: tmp/restart.txt: No such file or directory


[SPARK-41278][CONNECT] Clean up unused QualifiedAttribute in Expression.proto

What changes were proposed in this pull request?

With https://github.com/apache/spark/commit/2b2ffcdc5ad1ffde0f4ec351495026106a226614 there is no longer a need to have a schema field in LocalRelation proto, thus the old way to specify that schema which was QualifiedAtttribute is no longer used.
This PR cleans QualifiedAttribute proto and all its unused code.
Why are the changes needed?

Codebase cleanup
Does this PR introduce any user-facing change?

NO
How was this patch tested?

UT

@cloud-fan

Merged to master.

late lgtm

late LGTM


title and thumb are part of the media's metadata

... at least if the pychromecast implementation is correct.
But it seems it is correct, because:

the title is not shown without that change
the title is shown with that change

With respect to: https://github.com/vitalidze/chromecast-java-api-v2/pull/38#issuecomment-256162377

Merged. Thanks!


Update current CouchDB databases to the new schema supported in v.2.3.x

Impact of the new feature
WMCore in general (including cmsweb databases)
Is your feature request related to a problem? Please describe.
This is a sub-task of https://github.com/dmwm/WMCore/issues/8853
Yes, we cannot upgrade CouchDB to version 3.1.1 and keep the same database schema/files in the CMSWEB backends. The current schema is not compatible with CouchDB 3.1.1
Describe the solution you'd like
Before we can upgrade CouchDB to version 3.1.1, we must upgrade the database schema in CMSWEB. This will likely require an outage of the CouchDB instances.
Max - the summer student who worked on this - came up with a docker-based procedure to update our databases/documents to the compatible schema. So we will have to perform that procedure before CouchDB can be upgraded.
Describe alternatives you've considered
To be discussed
Additional context
Sub-task of https://github.com/dmwm/WMCore/issues/8853

@amaltaro can you provide details of what schema/files are not compatible? The CouchDB is schema-less database, meaning any valid JSON can be injected into it. Therefore, I don't understand the statement that schema is not compatible. Which schema/files you're taking about? May be you referring that internal CouchDB files which keep the data has different data-format, but in this case I would expect that simple replication can bring data from one couch to another, i.e. we just need to re-inject the data.

@vkuznet Hi Valentin, right. It's not the schema of our documents that get written to CouchDB, but actually its internal mechanism on how this data is compressed/stored in the file system.

For the record, here is where it's documented that we cannot upgrade directly from CouchDB 1.x to 3.x:
https://docs.couchdb.org/en/stable/whatsnew/3.0.html#upgrade-notes
also pasting that text here:
"""
Due to code changes in #2324, it is not possible to upgrade transparently from CouchDB 1.x to 3.x. In addition, the couchup utility has been removed from CouchDB 3.0 by #2399. If you are upgrading from CouchDB 1.x, you must first upgrade to CouchDB 2.3.1 to convert your database and indexes, using couchup if desired. You can then upgrade to CouchDB 3.0. Or, you can start a new CouchDB 3.0 installation and replicate directly from 1.x to 3.0.
"""

We have upgraded all the databases to the new format, but for the acdcserver. See more details here: https://github.com/dmwm/WMCore/issues/10833#issuecomment-1184479717
In short, the procedure was:

setup another CouchDB node (vocms0745) with 3+
replicate databases from CMSWEB to this new node
upgrade CMSWEB VMs to the new CouchDB version
move all the database shards (and _dbs and _users databases) to the VMs running the new version.

This ticket can be closed once the last database - acdcserver - is fully available in CMSWEB production.

And the acdcserver database has been updated as well. Further details can be found in this post:
https://github.com/dmwm/WMCore/issues/10833#issuecomment-1185485925
closing this out.


Added required files to run as a Docker's container.

It can be used for production/development environment.

nice thanks for the PR, i will check and merge

@mrbrazzi i will consider this addition for future versions and will check if some else also requests the same feature for now i 'm closing it.


Add another typechecking pass

We do a lot of code transformations, and it may be that we end up with something that isn't well-typed. It might be worth adding another typechecking pass towards the end of the compiler to make sure all the code we generated makes sense.

I was debugging some stuff yesterday where this would have been nice.
One thing I just realized is that after the type inferencer has annotated everything, type checking gets much easier. It's truly type checking, and not type inference.


DatePicker: fix date and time value format error

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

1.DatePicker: fix date and time value format error

#15791

@qingdengyue 大佬 merge似乎失败了？

It does not recurrent in your demo

It does not recurrent in your demo

cc @WaSheep

It does not recurrent in your demo

依旧有问题
yyyy年MM月dd日HH时mm分 => ["yyyy年MM月dd", "HH时mm分"]; “日”字没有了

倾向于 https://github.com/ElemeFE/element/pull/13764 这个方案
@iamkun @island205


Generated favicons has a faint border

For some reason my generated favicons have a faint border at various points. I'm wondering if it has something to do with my source png.
Source:

Generated:

@mattdrose is was due to the white stroke on the src image. removed stroke. fixed border ghosting.

Beauty! Thanks 👍


Spline easing

What does the pull request do?

Adds an option for users to just define their animation easings with a curve bezier parameters, just like in CSS.
Also introduces a new easing function called SplineEasing. Thanks @Deadpikle for the easy to use KeySpline class.

@MarchingCube I addressed all the issues, hopefully it's okay now :)


Platform Manifest in ASP.NET Core targeting pack should use the targeting pack package name

In the ASP.NET Core targeting pack (Microsoft.AspNetCore.App.Ref), there is a data/PlatformManifest.txt file which includes assembly and file versions for the contents of the targeting pack.  This is an optimization so that the files don't need to be read from disk to get these versions for conflict resolution.  The format looks like this:
aspnetcorev2_inprocess.dll|Microsoft.AspNetCore.App||13.0.19219.0
Microsoft.AspNetCore.Antiforgery.dll|Microsoft.AspNetCore.App|<IP_ADDRESS>|<IP_ADDRESS>702
Microsoft.AspNetCore.Authentication.Abstractions.dll|Microsoft.AspNetCore.App|<IP_ADDRESS>|<IP_ADDRESS>702

The second element is interpreted as the package name.  This should be updated to match the targeting pack package name, or Microsoft.AspNetCore.App.Ref.  As it is currently, the versions from the platform manifest aren't being used by conflict resolution, as it thinks they apply to files from a different package name.

@jkotalik @JunTaoLuo I think this should be a simple fix.  We'd like to take it through ask mode (for Preview 9) this week if possible.

I'm not entirely clear on why this issue is arising now. I presume things are working today or we'd have encountered an issue in our testing. Is this mostly a missed optimization?

@jkotalik fixed this, closing


Incorrect cli commands to enable soft delete

The command given, doesn't match up with cli docs:
az storage account blob-service-properties update --account-name <storage-account> \
    --resource-group <resource-group> \
    --enable-delete-retention true \
    --delete-retention-days 7

--resource-group isn't a valid parameter
--enable-delete-retention should be --delete-retention
--delete-retention-days should be --delete-retention-period

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

ID: ce25ff08-4d2a-70db-df3f-650ea80f9c4b
Version Independent ID: 6e61f44d-c752-6818-ad21-2377efcee633
Content: Enable soft delete for blobs - Azure Storage
Content Source: articles/storage/blobs/soft-delete-blob-enable.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

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

@bhalbright This appears to match what I am seeing on the CLI page. Could you share the CLI page you are referencing?
https://docs.microsoft.com/en-us/cli/azure/storage/account/blob-service-properties?view=azure-cli-latest#az_storage_account_blob_service_properties_update

@bhalbright - I know this is confusing, but there are two CLI commands for setting service properties. Note the difference between them is just a hypen:

az storage account blob-service-properties
az storage blob service-properties

You can use either one to configure blob soft delete. Our example shows how to use the first one and as such is correct as written.

Thanks @tamram, my apologies. I guess instead of following the link in the doc I searched for "az storage account blob-service-properties" in google and the top search result is the page for "az storage blob service-properties" instead. I didn't notice the difference.


Patient information encryption

We need to encrypt and decrypt the patient information.
Data should be stored encrypted and should be decrypted client side.

Encrypting the Data: Using the Fernet cipher, you'd encrypt the data you want to perform operations on. Fernet generates a key and initialization vector (IV) for encryption and decryption.
Performing Operations on Encrypted Data: FHE allows computations to be performed on encrypted data without decrypting it. However, traditional Fernet encryption does not support this. FHE schemes like the Brakerski-Gentry-Vaikuntanathan (BGV) or the somewhat homomorphic schemes like the Paillier cryptosystem can perform certain operations on encrypted data.
Decrypting the Result: After performing operations on the encrypted data, you'd decrypt the result using the Fernet cipher to get the final output.


Combine .animate syntax with m_tree class insertion

Description of the proposed feature

We have functionality present where we can call the insertion into our m_tree class and call the animation to move the node to its proper location. We want to mimic Manim syntax more closely and have the method we call .animate on do both of these.

I will see this issue resolved if its the last thing I do!!!


JBR: Move videos to events

@hythloda  Please review and merge
I think I found the right code for the 2 columns problem


GOVERNANCE capability does not disable contract upgrades

(module hello GOVERNANCE
     (defcap GOVERNANCE ()
       "upgrade disabled"
        false)
      ...
)

While the defcap GOVERNANCE should disable the contract to be upgraded, the contract gets overwritten when a new contract with the same module name is loaded.

Closing as won't fix and/or as a doc bug if we ever encourage this. The proper usage is
(defcap GOVERNANCE () (enforce false "upgrade disabled"))

The boolean result type is simply to echo the result type of enforce. It is confusing but would be better fixed by having a unit/log-only type to indicate a function whose result value is meaningless (ie most database functions return string as status-only, so make a status or log type for this to indicate that it's meaningless)