There are java.lang.IllegalStateException on some devices in production

Hello!
Google Play shows me exceptions in production like that:
1.
java.lang.IllegalStateException:
  at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor (AppCompatDelegateImpl.java:686)
  at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor (AppCompatDelegateImpl.java:649)
  at androidx.appcompat.app.AppCompatDelegateImpl.setContentView (AppCompatDelegateImpl.java:542)
  at androidx.appcompat.app.AppCompatDialog.setContentView (AppCompatDialog.java:95)
  at androidx.appcompat.app.AlertController.installContent (AlertController.java:232)
  at androidx.appcompat.app.AlertDialog.onCreate (AlertDialog.java:279)
  at android.app.Dialog.dispatchOnCreate (Dialog.java:524)
  at android.app.Dialog.show (Dialog.java:385)
  at androidx.fragment.app.DialogFragment.onStart (DialogFragment.java:486)
  at androidx.fragment.app.Fragment.performStart (Fragment.java:2632)
  at androidx.fragment.app.FragmentManagerImpl.moveToState (FragmentManagerImpl.java:915)
  at androidx.fragment.app.FragmentManagerImpl.moveFragmentToExpectedState (FragmentManagerImpl.java:1238)
  at androidx.fragment.app.FragmentManagerImpl.moveToState (FragmentManagerImpl.java:1303)
  at androidx.fragment.app.BackStackRecord.executeOps (BackStackRecord.java:439)
  at androidx.fragment.app.FragmentManagerImpl.executeOps (FragmentManagerImpl.java:2079)
  at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether (FragmentManagerImpl.java:1869)
  at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute (FragmentManagerImpl.java:1824)
  at androidx.fragment.app.FragmentManagerImpl.execPendingActions (FragmentManagerImpl.java:1727)
  at androidx.fragment.app.FragmentManagerImpl.executePendingTransactions (FragmentManagerImpl.java:183)
  at androidx.biometric.BiometricPrompt.authenticateInternal (BiometricPrompt.java:749)
  at androidx.biometric.BiometricPrompt.authenticate (BiometricPrompt.java:658)
  at io.flutter.plugins.localauth.AuthenticationHelper$1.run (AuthenticationHelper.java:200)

or that
2:
ava.lang.IllegalStateException:
  at io.flutter.embedding.engine.dart.DartMessenger$Reply.reply (DartMessenger.java:139)
  at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.success (MethodChannel.java:238)
  at io.flutter.plugins.localauth.LocalAuthPlugin$1.onSuccess (LocalAuthPlugin.java:102)
  at io.flutter.plugins.localauth.AuthenticationHelper.onAuthenticationSucceeded (AuthenticationHelper.java:171)
  at androidx.biometric.FingerprintHelperFragment$1.lambda$onAuthenticationSucceeded$3$FingerprintHelperFragment$1 (FingerprintHelperFragment.java:147)
  at androidx.biometric.-$$Lambda$FingerprintHelperFragment$1$B3yO31xQgVO9U1LcWOukmKVRCEg.run (lambda)

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
    • Flutter version 1.22.4 at /home/vvk/snap/flutter/common/flutter
    • Framework revision 1aafb3a8b9 (4 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/vvk/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_275-8u275-b01-0ubuntu1~20.04-b01)
    • All Android licenses accepted.

Hi @ValeriusGC
Can you please provide more information such as which devices are affected by this issue?
Please provide your pubspec.yaml as well.
Thank you

The DartMessenger.Reply exception implies that the local auth plugin is responding twice to the same request.

Hi @ValeriusGC
Can you please provide more information such as which devices are affected by this issue?
Please provide your pubspec.yaml as well.
Thank you

Random... for example:

LGE LG K30 Android 7.1 (SDK 25)
Huawei HUAWEI Y7 Pro 2019 Android 8.1 (SDK 27)
Samsung Galaxy S6 Edge+ Android 7.0 (SDK 24)
Asus ZenFone 4 Max (ZC554KL) Android 7.1 (SDK 25)

The DartMessenger.Reply exception implies that the local auth plugin is responding twice to the same request.

Well, the same code works well for 97% of devices and suddenly crashes on rest 3%. Why?

cc @stuartmorgan @cyanglaz The second trace looks like an issue with the local auth plugin.

Yes, there's also https://github.com/flutter/flutter/issues/76299 which is the same multi-reply issue. https://github.com/flutter/flutter/issues/59318 also discusses some cases where it happens, which may help in figuring out the code path that causes it.


Update hyperledger-fabric-consortium-azure-kubernetes-service.md

@ravastra : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Publicize and/or advertise ESA

After we have an official publication listed as our citation, we should start advertising ESA. One example might include making a "Powerglobe" announcement.

@mzy2240, @SmartJingJing123 - I'll be emailing folks at PNNL about ESA now that it's "complete" and we've got the JOSS paper out. Would you guys be willing to take point on advertising it elsewhere?

https://github.com/mzy2240/ESA/issues/50#issuecomment-645636114
I could volunteer to advertise on Linkedin.

Yeah I will advertise it to my intern company as well as friends in our field.

@mzy2240 @SmartJingJing123 - I've informed my PNNL network about ESA, and also updated the group regarding the JOSS publication. I propose we close this for now, and if anyone has more ideas for getting the word out, we can reopen.

@mzy2240 @SmartJingJing123
We saw some decent cloning traffic before the JOSS paper came out as well as on the day the paper was published:


Chore/add debugging folder

I have added a debugging configuration; you can freely test under the debug folder via VSCode, and set breakpoints in the src/debug folder to inspect the data. 😀

Just received the review request.
Unfortunately, I haven't actually learned typescript yet and so am still unfamiliar with typescript development. I can still approve the changes if you want though.
Also, I'll probably be learning typescript in the next couple weeks, so I'll be able to help with this repo then!


Add Discord timestamps

It's probably a stretch to call it Markdown, but Discord supports a Syntax for adding timestamps which is useful. It would be nice if it could be added to "Additional Syntax Elements".
<t:1585890376:f>
April 3, 2020 1:06 AM
<t:1585890376:F>
Friday, April 3, 2020 1:06 AM
<t:1585890376:D>
April 3, 2020
<t:1585890376:t>
1:06 AM
<t:1585890376:T>
1:06:16 AM
<t:1585890376:R>
2 years ago

source

Hiya!
As others say on Discord's Official Forum, Discord as of today, supports an oversimplified, some sort of markdown, which only consists of basic highlighting of text, code blocks and as you mentioned, these cool timestamps. What I wanna say with this is that Discord only supports a subset of Markdown and they aren't planning to add tables or list element support in the near future. I personally would not count Discord's basic text formatting as Markdown support.
While Markdown is not so standardized, as I can understand it, contains a documentation to the most supported features and most used syntaxes of Markdown and the timestamps, which are only supported by Discord and no one else does not count as widely supported.
However I find them very interesting and cool as they could be dynamic and they use Unix timestamps, but I don't think that this should be added to The Markdown Guide.
Best regards


patchelf.rb fails on go bottling

brew config output
Linux CI / not necessary
brew doctor output
Linux CI / not necessary

[X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?
Bottling go 1.16
What happened (include all command output)?
2021-02-24T13:07:05.0421541Z ==> brew bottle --verbose --json go --keep-old
2021-02-24T13:08:18.6409734Z ==> FAILED
2021-02-24T13:08:18.6423380Z ==> Installing patchelf...
2021-02-24T13:08:18.6425435Z /home/linuxbrew/.linuxbrew/bin/brew install patchelf
2021-02-24T13:08:18.6427118Z ==> Downloading https://linuxbrew.bintray.com/bottles/patchelf-0.12_4.x86_64_linux.bottle.tar.gz
2021-02-24T13:08:18.6435621Z ==> Downloading from https://akamai.bintray.com/56/56a0ff9acc9ab6c5d7f53d6f8ecce4878fd8c547a581960519504cf9e9dfac51?__gda__=exp=1614172746~hmac=244b54c7e503cb364eace097d882356e0ddff8e99b4d142f80efb8edcf1ddb63&response-content-disposition=attachment%3Bfilename%3D%22patchelf-0.12_4.x86_64_linux.bottle.tar.gz%22&response-content-type=application%2Fgzip&requestInfo=U2FsdGVkX1_jdUz69RdsWjsrSR4X_jmDg5dlt5h7Nb-yBuj-maRRdBkqSm_1Jz_-prCs2RbsOBOjQfpIjTD9WyBV3JbEQNepyLa4KE79tbIwbLbeqSBg516kV6h6N5EpkhIhtuYYsPUnKnNAfTw3Xw&response-X-Checksum-Sha1=584ea8b7f356dc8ebe6ca45f05c81fe8ebbe06d9&response-X-Checksum-Sha2=56a0ff9acc9ab6c5d7f53d6f8ecce4878fd8c547a581960519504cf9e9dfac51
2021-02-24T13:08:18.6442358Z ==> Pouring patchelf-0.12_4.x86_64_linux.bottle.tar.gz
2021-02-24T13:08:18.6443157Z /home/linuxbrew/.linuxbrew/Cellar/patchelf/0.12_4: 7 files, 942.3KB
2021-02-24T13:08:18.6444110Z ==> Bottling go--1.16.x86_64_linux.bottle.tar.gz...
2021-02-24T13:08:18.6445073Z tar cf /github/home/bottles/go--1.16.x86_64_linux.bottle.tar go/1.16
2021-02-24T13:08:18.6445811Z gzip -f go-bottle.tar
2021-02-24T13:08:18.6446721Z ==> Detecting if go--1.16.x86_64_linux.bottle.tar.gz is relocatable...
2021-02-24T13:08:18.6447840Z Warning: String '/home/linuxbrew/.linuxbrew/Cellar' still exists in these files:
2021-02-24T13:08:18.6448905Z /home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/pkg/linux_amd64/runtime/cgo.a
2021-02-24T13:08:18.6450027Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/cgo' at offset 0x5777
2021-02-24T13:08:18.6451524Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/cgo' at offset 0x75cd
2021-02-24T13:08:18.6452717Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/cgo' at offset 0xa6ec
2021-02-24T13:08:18.6453884Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/cgo' at offset 0xe1be
2021-02-24T13:08:18.6455041Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/cgo' at offset 0x10aeb

snip

2021-02-24T13:08:18.9431325Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/profbuf.go' at offset 0x1b352f
2021-02-24T13:08:18.9432584Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/rwmutex.go' at offset 0x1b3578
2021-02-24T13:08:18.9433833Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/select.go' at offset 0x1b35c1
2021-02-24T13:08:18.9435084Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/signal_amd64.go' at offset 0x1b3609
2021-02-24T13:08:18.9436364Z  --> match '/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/runtime/signal_linux_amd64.go' at offset 0x1b3657
2021-02-24T13:08:18.9437157Z Only the first 100 matches were output.
2021-02-24T13:08:18.9437510Z
2021-02-24T13:08:18.9438176Z Error: undefined method `header' for nil:NilClass
2021-02-24T13:08:18.9439644Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:793:in `block in write_replaced_sections'
2021-02-24T13:08:18.9441343Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:792:in `each'
2021-02-24T13:08:18.9442983Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:792:in `write_replaced_sections'
2021-02-24T13:08:18.9444683Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:626:in `rewrite_sections_library'
2021-02-24T13:08:18.9446352Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:469:in `rewrite_sections'
2021-02-24T13:08:18.9447942Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/alt_saver.rb:88:in `save!'
2021-02-24T13:08:18.9449480Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.6.0/gems/patchelf-1.3.0/lib/patchelf/patcher.rb:191:in `save'
2021-02-24T13:08:18.9450843Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/os/linux/elf.rb:175:in `save_using_patchelf_rb'
2021-02-24T13:08:18.9451981Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/os/linux/elf.rb:105:in `patch!'
2021-02-24T13:08:18.9453168Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/keg_relocate.rb:48:in `change_rpath'
2021-02-24T13:08:18.9454595Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/keg_relocate.rb:16:in `block (2 levels) in relocate_dynamic_linkage'
2021-02-24T13:08:18.9455971Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/pathname.rb:356:in `ensure_writable'
2021-02-24T13:08:18.9457334Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/keg_relocate.rb:15:in `block in relocate_dynamic_linkage'
2021-02-24T13:08:18.9458685Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/keg_relocate.rb:14:in `each'
2021-02-24T13:08:18.9460015Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/extend/os/linux/keg_relocate.rb:14:in `relocate_dynamic_linkage'
2021-02-24T13:08:18.9461415Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/keg_relocate.rb:65:in `replace_placeholders_with_locations'
2021-02-24T13:08:18.9462781Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:396:in `block (2 levels) in bottle_formula'
2021-02-24T13:08:18.9464001Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/utils.rb:424:in `ignore_interrupts'
2021-02-24T13:08:18.9465218Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:394:in `block in bottle_formula'
2021-02-24T13:08:18.9466363Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/lock_file.rb:35:in `with_lock'
2021-02-24T13:08:18.9467852Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/keg.rb:332:in `block in lock'
2021-02-24T13:08:18.9469187Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/lock_file.rb:35:in `with_lock'
2021-02-24T13:08:18.9470229Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/keg.rb:330:in `lock'
2021-02-24T13:08:18.9471341Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:301:in `bottle_formula'
2021-02-24T13:08:18.9472521Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:89:in `block in bottle'
2021-02-24T13:08:18.9473715Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:88:in `each'
2021-02-24T13:08:18.9474856Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/dev-cmd/bottle.rb:88:in `bottle'
2021-02-24T13:08:18.9475920Z /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:122:in `<main>'
2021-02-24T13:08:18.9476405Z
2021-02-24T13:08:18.9476954Z ==> brew linkage --test go
2021-02-24T13:08:20.2809156Z ==> brew install --only-dependencies --include-test go

What did you expect to happen?
Bottling should not fail
Step-by-step reproduction instructions (by running brew commands)
See commands used in the logs above

cc @sjackman
I added HOMEBREW_PATCHELF_RB_WRITE: 0 to my build and got the same error.
Also, patchelf is being installed on CI, but it should not.

I added HOMEBREW_PATCHELF_RB_WRITE: 0 to my build and got the same error.

HOMEBREW_NO_PATCHELF_RB_WRITE=1
All of the boolean env vars respond only to being set or not being set. Their value is ignored. The empty string may be treated as being unset, but I wouldn’t rely on that behaviour.

Also, patchelf is being installed on CI, but it should not.

Mike flagged this known issue previously.

@rmNULL @david942j We've bene using patchelf.rb for some months now, and it's been working great! We've just experienced our first failure in bottling go. Would either of you be interested in looking into this issue?
@iMichka Could you provide the ELF file that produces this error?

Here the detail about the file.
I found it out by using patchelf:
patchelf: cannot find section '.interp'. The input file is most likely statically linked

/home/linuxbrew/.linuxbrew/Cellar/go/1.16/libexec/src/debug/elf/testdata/go-relocation-test-gcc930-ranges-no-rela-x86-64: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter *empty*, not stripped

I can probably workaround the issue by not installing this debug/testdata file.
I think either ignoring these cases or at least having a better error message in patchelf.rb would help.

Weird, the ELF is dynamically linked but has no interpreter?  Definitely seems like files that should be ignored or deleted if unneeded.
I'm wondering if we should eventually have an audit that warns us about ELFs missing the .interp section (so we know those binaries are static or weird like this one), and another to catch .debug sections to tell us when debugging symbols haven't been stripped (since file only returns stripped if all symbols have been stripped, not just debugging ones).

My initial attempt to delete the debug files before bottling worked and I could ship go.
But it looks like some other formulae need these files (octant for example):
https://github.com/Homebrew/linuxbrew-core/runs/1974182054

I wouldn't delete all of debug. Just the testdata subdirectory, and maybe the *_test.go files if you really want.

I wouldn't delete all of debug. Just the testdata subdirectory

Thanks that worked

So it Looks like not a bug of patchelf.rb but a bad ELF encountered? If so I can help modify patchelf.rb to throw a better error description in such cases.

Yes, I think the best is to have a better error message. At least a line that tells the name of the file that was broken.
It's not the first time this happens, there was already another weird ELF file in a formula that was used for test/debug purposes by upstream, and that was clearly not ment to be shipped to our users.

It may be a bug in Homebrew if it's calling patchelf.rb for an ELF that should not be patched, like for example calling set_interpreter for an ELF that does not have a .interp section. Improved error messages are always appreciated.

One thing worth to mention is an ELF executable without .interp section is actually legitimate. Section headers are usually used for object files (i.e. .o files), and after objects linked those section headers are not necessary. Nevertheless, at least for common compilers (or to be precisely, linkers) those section headers are kept after linking, so it's usually fine to fetch information from sections in a linked ELF.
And for Unix patchelf, I would say it shouldn't use section headers for fetching the interpreter name (and file command shouldn't do so as well).
patchelf.rb currently supports two modes, one is unix-patchelf-compat mode that performs exact same as what patchelf does, so an error occurs when .interp section is not present is expected. One thing might help to improve is I can slightly modify patchelf.rb to just do not modify the section header when there is no one, maybe after then we are able to process this go binary.
BTW, the other mode of patchelf.rb won't have this issue because it properly handles the cases when there is no section header ;)

Thanks for your input, @david942j!

I wouldn't delete all of debug. Just the testdata subdirectory

Thanks that worked

It looks we have a workaround that got us past this issue. There were some test data ELF files in the go package that weren't needed, so simply deleting them got us past this issue. So no changes are needed for patchelf.rb this time around. Sorry for the noise, and thanks for your help!

I would still like to get a better error message that at least tells me on which file the error happened.

As my description in https://github.com/Homebrew/brew/issues/10696#issuecomment-787003167, I decide to properly handle the case when sections are not preset instead of raising an error: https://github.com/david942j/patchelf.rb/pull/34


Update apache-client, kinesis, sqs to 2.25.67

About this PR
📦 Updates

software.amazon.awssdk:apache-client
software.amazon.awssdk:kinesis
software.amazon.awssdk:sqs

from 2.25.32 to 2.25.67
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #892.


OS#14568840: Remove 'this' binding for indirect eval

Having a 'this' binding in the indirect eval leads to problems if there is a lambda capturing 'this' in the indirect eval. The lambda would try to load 'this' from a scope slot in the global scope of the indirect eval which asserts.
Seems we can simplify the above by just removing the 'this' binding from the indirect eval. Then we'll simply load 'this' like an ordinary lambda at global scope would.
Fixes:
https://microsoft.visualstudio.com/web/wi.aspx?id=14568840

Looks good. This is the way I'd originally hoped we could do it.


Update sysctl and fix NetworkManager

Overall Review of Changes:

Change sysctl settings to be set in specific folders. Instead of dumping all the settings in the main file, use the sysctl.d subfolder and place the sysctl settings in their respective folders.
The check for NetworkManager is applied to the wrong task, move it to the correct one.
Fix some typo's

How has this been tested?:

I've run this role against my own Ubuntu 22.04 installation, without rsyslog, without firewall and with systemd-timesyncd as NTP.

hi @Jeroen0494
Thank you for raising this PR, the official CIS having now been released is now live. I am hoping this resolves this issue for you as there are a large number changes that had to take place compared to the ubuntu2004 this was based upon.
Please let us know if you still see any issues?
Many thanks
uk-bolly

Thanks, I reduces the PR to some typo fixes and the NetworkManager fix.


Swayblur and Azote

I understand this program uses Oguri, but on a dual monitor landscape & portrait setup oguri always starts the portrait orientation wrong, and it doesn't correct until I open up an app. I wondering how hard would it be to tweak the code to read .azotebg file in the home folder instead of oguri config?

I like azote, but I finally got oguri working properly is on start up with dual monitors with different orientations, using a sleep delay.
I understand why you're using oguri because it has an output structure (and animated wallpaper), as opposed to .azotebg which just points to the image with no output instructions (non-animated pics)
Wondering if  this could work in  River tiling windows manager, if I now the port number it should be listen to.


Support SymbolInformation.annotations in metacp

Any pointers on how to solve this one?
Here is what I see:
remove all diffs related to metac vs metacp:
https://github.com/scalameta/scalameta/blob/083ac67910dbd76aed25118f6965ae477a2a9caa/tests/jvm/src/test/resources/metac-metacp.diff#L255-L271


Executing child process in scripts hangs terminal

Output of docker version:
Client:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:        Fri Jun 17 20:35:33 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   a7119de
 Built:        Wed Jun 29 10:03:33 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 2
 Running: 1
 Paused: 0
 Stopped: 1
Images: 482
Server Version: 1.12.0-rc2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 380
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: default
Default Runtime: default
Security Options: seccomp
Kernel Version: 4.4.14-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.954 GiB
Name: moby
ID: Z25L:V4GW:6DNP:UQGU:2DRW:BROW:BPRA:K3S5:LBE7:PYWL:KOYC:UJ2N
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 112
 Goroutines: 211
 System Time: 2016-07-03T15:47:20.113835804Z
 EventsListeners: 49
No Proxy: *.local, 169.254/16
Username: mckn
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
I am running on OSX 10.11.5
Steps to reproduce the issue:

docker run -d --name cassandra cassandra:2
wait until started (takes about 10s)
docker run -e "DATABASE=cassandra" --link cassandra:kong-database -ti mashape/kong /usr/local/bin/kong start
It will hang on [INFO] Auto-generating the default SSL certificate and key...
source to that file is: https://github.com/Mashape/kong/blob/997561b42c27d5917f261065d9b1f5e99079e337/kong/cli/utils/ssl.lua#L43
It will continue if you press ctrl-c

Describe the results you received:
Docker seems to hang when spawning child processes inside executed scripts.
Describe the results you expected:
It should continue in the flow and print [OK] Started and then exit the docker run.
Additional information you deem important (e.g. issue happens only occasionally):

Doing a docker exec into the container while it is hung, it does not look like that script is running any more:
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.3  43624  6540 ?        Ss+  09:31   0:00 /usr/local/bin/luajit -e package.path="/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;"..package.path; package.cpath="/usr/local/lib/lua/5.1/?.so;"..package.cpath -e local k,l,_=pcall(require,"luarocks.loader") _=k and l.add_context("kong","0.8.3-0") /usr/local/lib/luarocks/rocks/kong/0.8.3-0/bin/kong start
root        69  0.0  0.0      0     0 ?        Zs   09:32   0:00 [dnsmasq] <defunct>
root        70  0.0  0.1  15560  2260 ?        S    09:32   0:00 dnsmasq -p 8053 --pid-file=/usr/local/kong/dnsmasq.pid -N -o --listen-address=<IP_ADDRESS>
root        89  0.1  0.5  16304 10396 ?        Sl+  09:32   0:00 serf agent -profile=wan -rpc-addr=<IP_ADDRESS>:7373 -event-handler=member-join,member-leave,member-failed,member-update,member-reap,user:kong=/usr/local/kong/serf_event.sh -bind=<IP_ADDRESS>:7946 -node=afe23829ed93_<IP_ADDRESS>:7946_382c50dd9ae54b65a5b1006626a1acd4 -log-level=err
root       148  0.0  0.0      0     0 ?        Z+   09:32   0:00 [nc] <defunct>
root       149  0.0  0.1  11644  2612 ?        S+   09:32   0:00 sh -c /bin/bash /tmp/lua_1cKwrd > /tmp/lua_gf9DOR 2>&1
root       150  0.0  0.1  11644  2540 ?        S+   09:32   0:00 /bin/bash /tmp/lua_1cKwrd
root       151  0.0  0.5<PHONE_NUMBER>2 ?        S+   09:32   0:00 nginx: master process /usr/local/openresty/nginx/sbin/nginx -p /usr/local/kong -c nginx.conf -g pid /usr/local/kong/nginx.pid;
root       153  0.0  0.7<PHONE_NUMBER>0 ?        S+   09:32   0:00 nginx: worker process
root       154  0.0  0.7<PHONE_NUMBER>2 ?        S+   09:32   0:00 nginx: worker process
root       155  0.0  0.7<PHONE_NUMBER>6 ?        S+   09:32   0:00 nginx: worker process
root       156  0.0  0.7<PHONE_NUMBER>0 ?        S+   09:32   0:00 nginx: worker process
root       196  0.0  0.0      0     0 ?        Z+   09:32   0:00 [serf] <defunct>
root       231  0.0  0.0      0     0 ?        Z+   09:32   0:00 [serf] <defunct>
root       245  0.0  0.0      0     0 ?        Z+   09:33   0:00 [serf] <defunct>
root       259  0.0  0.0      0     0 ?        Z+   09:33   0:00 [serf] <defunct>
root       273  0.0  0.0      0     0 ?        Z+   09:34   0:00 [serf] <defunct>
root       288  0.0  0.0      0     0 ?        Z+   09:34   0:00 [serf] <defunct>
root       303  0.0  0.0      0     0 ?        Z+   09:35   0:00 [serf] <defunct>
root       317  0.0  0.0      0     0 ?        Z+   09:35   0:00 [serf] <defunct>
root       332  0.0  0.0      0     0 ?        Z+   09:36   0:00 [serf] <defunct>
root       346  0.0  0.0      0     0 ?        Z+   09:36   0:00 [serf] <defunct>
root       360  0.0  0.0      0     0 ?        Z+   09:37   0:00 [serf] <defunct>
root       375  0.0  0.0      0     0 ?        Z+   09:37   0:00 [serf] <defunct>
root       389  0.0  0.0      0     0 ?        Z+   09:38   0:00 [serf] <defunct>
root       399  0.6  0.1  11788  2824 ?        Ss   09:38   0:00 bash
root       412  0.0  0.1  47432  3356 ?        R+   09:38   0:00 ps auxww

It might be a signal handling issue as the process is running as pid 1, but I don't think there is an issue with docker specifically, I think you need to debug the program itself, perhaps using strace to trace what is happening after that executes. It might also help to use an init process (eg tini) as you have several processes in the container.

hmm, okay. I will test it with an older version of docker and see if it behaves the same.

You are right, so I wonder why the lua script doesnt continue and hangs. That is wierd.

Seeing this issue as well.


[AIRFLOW-2425] Maintain lineage and make available in other systems

Make sure you have checked all steps below.
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2425
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[X] Here are some details about my PR, including screenshots of any UI changes:

Lineage
Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

X ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Will squash when tests pass and comments are integrated.
cc: @criccomini @jgao54 @Fokko

Codecov Report

Merging #3321 into master will increase coverage by 0.18%.
The diff coverage is 90.5%.

@@            Coverage Diff             @@
##           master    #3321      +/-   ##
==========================================
+ Coverage   75.89%   76.08%   +0.18%
==========================================
  Files         197      201       +4
  Lines       14728    14920     +192
==========================================
+ Hits        11178    11352     +174
- Misses       3550     3568      +18

Impacted Files
Coverage Δ

airflow/operators/email_operator.py
0% <ø> (ø)
:arrow_up:

airflow/logging_config.py
100% <100%> (ø)
:arrow_up:

airflow/utils/module_loading.py
100% <100%> (ø)
:arrow_up:

airflow/operators/bash_operator.py
91.37% <100%> (+0.15%)
:arrow_up:

airflow/models.py
86.83% <100%> (+0.14%)
:arrow_up:

airflow/lineage/backend/atlas/typedefs.py
100% <100%> (ø)

airflow/lineage/datasets.py
84.5% <84.5%> (ø)

airflow/lineage/backend/atlas/__init__.py
86.95% <86.95%> (ø)

airflow/lineage/__init__.py
96.66% <96.66%> (ø)

airflow/utils/email.py
97.4% <0%> (ø)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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

@Fokko PTAL


() is not hyperlinked anymore

Original reporter: sol@
I adapted the tests for now:
https://github.com/ghc/haddock/commit/85665a576b76cdc856ad3727b28a8abe5d185d59
I have no idea which commit introduced that regression.  Finding the commit in a systematic way would require code bisection in GHC's source tree (due to changes to Haddocks interface file and the GHC API).  However, I'm not aware of a systematic way to do code bisection in GHC's source tree.

Closing in favor of #368 which is more general but also covers this, I think.


Material 3 dialog color affected by surface tint differently than bottom sheet

According to the material 3 deisgn docs (https://m3.material.io/components/dialogs/specs#401a48c3-f50c-4fa9-b798-701f5adcf155) a Dialog uses Surface color and Surface tint color to give the container a color, but in reality it looks like it uses primary color but with a calculation to make it a bit off.
The property dialogBackgroundColor in ThemeData can be used, but this seems like something that should be deprecated with material 3 if Surface color gets used correctly.
Tested with the official Material 3 sample https://github.com/flutter/samples/tree/main/material_3_demo

Open the dialog and notice the background color
Look in the Color tab and see that the surface color is different

I can see that in ColorScheme surfaceTint is set to the primary color, but why does the Bottom sheet look different than the dialog? A bottom sheet is also set to use surface and surface tint color, but it doesn't get colored by the primary color like a dialog does.

Sorry, I think it is the elevation that is messing with me. Dialog has level 3 elevation why bottom sheet only has level 1.


bugfix: impose no message size limit, use same version of PAKE in sender and receiver

(Dev -> Master)

Remove message size limitations. This broke portal for larger files than 32KB since the latest release which uses the nhooyr/websocket library.

Sender and receiver had different versions of schollz/pake. The old
version in the receiver was broken in go 1.19.
(golang/go#50974)

Upgrade other packages.

Codecov Report
Base: 25.00% // Head: 24.71% // Decreases project coverage by -0.28% :warning:

Coverage data is based on head (dee7599) compared to base (3ca2f6b).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head dee7599 differs from pull request most recent head 5a7907f. Consider uploading reports for the commit 5a7907f to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
- Coverage   25.00%   24.71%   -0.29%
==========================================
  Files           5        5
  Lines         172      174       +2
==========================================
  Hits           43       43
- Misses        113      115       +2
  Partials       16       16

Impacted Files
Coverage Δ

internal/conn/conn.go
32.05% <0.00%> (-0.85%)
:arrow_down:

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

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


fail fast

command not found should cause stuff to fail?
command not found should be addressed?

script has set -e why does it not fail?
@chuckwagoncomputing need moral support if any available

By default the exit status of a pipe is the exit status of its last command; all other commands' statuses are ignored.
If you add set -o pipefail, the exit status of the pipe will be the status of the right-most command that exited with a non-zero status.

@chuckwagoncomputing this PR has [ $? -eq 0 ] || { echo "crc32 computation failed"; exit 1; } would not I expect it to exit with my error since action output says command not found?

@chuckwagoncomputing nope, did not fail. I give up not my specialy
(master has dependency fixed so any dev should branch from before https://github.com/mck1117/wideband/commit/5cc1199d49e01815d14aec67c5fe3bdfb06bfd3d)

It didn't fail only because it had the dependency fixed. (PR actions run on what the state will be after the PR is merged to master.)
Your change is correct, this PR should be merged.

@mck1117 he says this PR should be merged

do we need both set and manual exit?

If you have set -e as well, it will exit before the manual check, making it unnecessary.

It always had "set -e" yet not failing

he's saying you need both set -e and set -o pipefail

If you don't want to need the manual check, you need both.
If you want to use the manual check, you need only pipefail.


Add test coverage

#95 Adding code coverage tests

Current coverage is 40.80%

Branch #105 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.

just gonna merge cause mostly not code


content-wrapper height problem in AdminLTE v.2.0

I'm using a codeigniter and AdminLTE 2.0 framework to build a project,
I try to remove some menus from the sidebar then my form go overlap through the footer bar,
is there any way I can add my content-wrapper height,
I try using the min-height, but its not work properly

Look like you missed some tag closing. Check and recheck the tags, and this problem will be solved.

As @rafael-renan-pacheco suggested, you should make sure that all your tags are closed properly.
Thanks!

i rewrite my code again, but there no open tag,
this only happen when i view my app at 768px height of screen
ill
attach my code here,
btw thanks guys for all your concern,

load->view('template/head');
?>

load->view('template/topbar');
$this->load->view('template/sidebar');
?>

diberkas.in v.1.1
        it all starts here

 Home
Examples
Blank page

Modul Administrasi Berkas

 BERKAS

input->get('berkas'));
                        }
                    ?>

Nomor Pokok Wajib Pajak
npwp;};?>">

Nama Wajib Pajak
nama_wp;};?>">

Tahun Pajak/Tahun Pemeriksaan

">2008
2009
2010
2011
2012
2013
2014
2015

Jenis Dokumen

SPT Masa
Berkas Pemeriksaan
Induk Berkas

Rak Berkas

A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q

Kolom

1
2
3
4
5

Baris

1
2
3
4

Kardus

1
2
3
4

load->view('template/js');
?>

load->view('template/foot');
?>


API returns bucket url instead of cdn url

Under development i used the default cloudstorage url -
"baseUrl: 'https://storage.googleapis.com/{bucket-name}'".
Works perfectly, however, i'm ready to go into production now, i've created a load balancer cdn -
"media.mysite.com".
Updating "baseUrl" to "media.mysite.com" does not change the return data "url" containing the original URL (example below) -
https://storage.googleapis.com/my-bucket/my-folder/my-image.jpg
Any help is much appreciated.

Hi @rrubio,
In fact, for each media, the relative url is saved in database, so all "old" files must be renamed manually by updating url field of media table.
New uploaded files will have the new url name (in theory, this is working for me with Strapi 3).
Thanks

Did you solve this?

@Lith apologies for the late response. The issue for me was related to not using the new "deep" population.  I ended up using this plugin - https://market.strapi.io/plugins/strapi-plugin-populate-deep


Incompatibility of resize-observer with Nextjs 12.

Describe the bug
We have updated our project to Next 12 and the following appears when we load a page with a component that uses resize-observer.
SyntaxError: The requested module 'react' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export. For example: import pkg from 'react'; const {useRef: r,useEffect: t}from"react";export default e=>{var a=r(e);return t(()=>{a.current=e}),a} = pkg;
To Reproduce
Steps to reproduce the behavior:

Use resize-observer
Update to Next 12

Screenshots

Desktop (please complete the following information):

OS: MacOS
Browser: Chrome Version 96.0.4664.110
@react-hook/resize-observer Version: 1.2.5
next Version: 12.0.7

Not clear to me this is my issue vs. Next's

Not clear to me this is my issue vs. Next's

Hello, it's not clear to me either. Have you maybe tried to reproduce it?

I'm using other hooks in this group that use the same package.json configurations and import React with Next 12.0.7 and haven't run into any issues so far 🤷🏼♂

I'm getting this - NextJS@12^ but it only throws in my Jest@28 tests

Solved it for me. I'm not using next, but had this issue while migrating to jest28 and 29 in a react library project.


Update the game over message

Update the game over message so people know how to play again!

Comment 2


#1: add support for horses in database initialization

Adding support for horses.

/paulo - can you please review this pull request?

/paulo - can you check now?


Switch to user model based on Django model

Gives us authentication for free. Official recommended way to set up user model.
This is a breaking change, I deleted the existing migrations and started fresh. Recommend dropping and re-creating the DB then running python manage.py migrate to apply this change.

+1 @boylea
Dubiously going to merge this one


Unable to get canexecutemethod change notification from inherited class

[ViewModel]
public abstract partial class TreeModel
{
        [Property]
        public ColItem? _rootNode;

        [Property]
        public ColItem? _selectedNode;
}

[ViewModel]
public partial class LocalTreeModel : TreeModel
{
       [Command(CanExecuteMethod = nameof(CanEditNode))]
        public void EditNode()
        {

        }

        [CommandInvalidate(nameof(RootNode))]
        [CommandInvalidate(nameof(SelectedNode))]
        public bool CanEditNode() => RootNode is not null && SelectedNode is not null && SelectedNode != RootNode;
}

At present, I can only manually execute notifications for each command

Thank you @wf-soft, I'll look into this

Hey @wf-soft , I think are only two options
a) Generate the code into the properties of the base class
b) Generate something like you wrote to InvalidateCommands.
I see the issue, and maybe having a general InvalidateCommands method would be the way to go. I'll look into this.
I'll promise that I'll come up with something to support this scenario within the next days. I just have to think about the best way to do it.

@thomasclaudiushuber Great. Mvvmgen is a very easy-to-use library. Less code allows people to reduce errors and omissions

Thank you for reporting this @wf-soft.
NuGet package version 1.1.5 is available that should fix this for you.
To support invalidating commands when a property of a ViewModel base class was changed, a new InvalidateCommands method was introduced in the generator. Instead of invalidating commands in the setter of a property, they're now invalidated in this generated method. That InvalidateCommands method is called now by the OnPropertyChanged method of the ViewModelBase class. That way the framework does not rely on a property setter anymore, which means invalidating a command for a property that is defined in a base class works now without a problem.
You should be able to get rid of your OnPropertyChanged override with version 1.1.5.
Please let me know how things are going. I'll close this issue here, but feel free to comment if something is not working as expected.
Thank you,
Thomas

Note that also the Invalidate Commands section in the docs was updated to include the new InvalidateCommands method
https://github.com/thomasclaudiushuber/mvvmgen/blob/main/docs/03_work_with_commands.md#invalidate-commands
From the usage point of view, nothing has changed. Your scenario should now just work.

@thomasclaudiushuber This is pleasant news


Camera controls extension

Allows free movement of the camera along the X and Y axis, and zooming. Note that this extension automatically removes fencing to make this work correctly.
Adds the following blocks:

I currently do not have an image for the extension, I will make one sometime tomorrow.

This is something I wanted to see for a while now. This is cool.

@DT-is-not-available
Hello! I have slightly changed your extension so that it is in scratch style:

And also I added icon and created new image (#204)

Here is the finished code, just copy it

Would this coincide with Box2D?

@DNin01 I looked at the code, apparently yes, but it's not accurate

@True-Fantom
Thanks! I will update the images and credit you later today. As for the palette layout, I had no idea you could just insert "---" as a separator, very useful.
@DNin01
I have no idea, I'll have to check but I imagine it wouldn't work perfectly if at all.

@DT-is-not-available Was happy to help)

I've gone ahead and added the images to the extension, as well as the modified block palette. I do have an unused "set background color" block, since it doesn't change the result of the touching-color boolean. Does anyone know how to do that? Also at some point I want to add camera rotation, but I'm not sure how to do that at this point, I'll see if I can tell webgl to apply proper transformations before drawing anything rather than messing with the projection values.

It helps to post the code that doesn't work when asking for further help

Ok it is in there, just a bit indirect
Look at vm.renderer.setBackgroundColor

Oh I see now, should look through scratch-render some more, thanks!

@DT-is-not-available Since you added a background color, I think need to add reporter for it:

+position the block a little higher) Here is code

Background color feels unrelated to camera movement, so I'll probably move it and a reporter under the movement blocks. (I may add more visual blocks since proper transformations requires custom shaders, so I might as well use them)

Ok, that's a great idea

I will modify the layout of the extension tonight, and probably leave it as is for a while until I learn more about how webgl works. On that note, is there a way I should go about applying custom glsl code as a vertex shader without screwing up the default?

Why does this extension have unused code related to shaders?

I'm assuming they're not talking about this extension.

The extension in this PR appears to contain a lot of code and shaders that are seemingly unused. Is that intentional?

@GarboMuffin That was not intentional, my bad. I am considering rewriting the extension to use a custom shader however, as this would allow for much easier implementation of things like camera rotation, and well, camera "shader" effects. I've removed the shader related code and updated the set background color block to be at the end of the block palette, along with a background color reporter.

Alright, I'm done updating this for a while.

@GarboMuffin Can you merge this, please?


DSP process time investigation

Hello,
I am evaluating the DSP process time by the bellows source code.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/hexagon/hexagon_graph_execution_test.cc
And, The result was short process time.
As one factor, I think that the reason is quantization to input data of  DSP.
Could you please tell me a change procedure for quantization ?
And, Could I please have the pb file(NOT quantizate) before the bellows quantization pb file ?
tensorflow_inception_v3_stripped_optimized_quantized.pb
I want to compare between DSP process time(quantizate input data) and CPU process time(NOT quantizate input data)

@satok16, could you please take a look?

The input data type to HVX is floating point not quantized data type for fairness purposes.
The quantization (of the graph) is a pre-process before running the inference.
See https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/graph_transforms/README.md for more details.
In this link, you can find a download link for non-quantized model.


Modifying new/changed staff

Adding and removing advocate profiles.

Docs Build status updates of commit 01b7d81:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/index.yml
:warning:Warning
View
Details

advocates/bryan-hughes.yml
:white_check_mark:Succeeded
View

advocates/justin-yoo.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/bryan-hughes.jpg
:white_check_mark:Succeeded

advocates/media/profiles/bryan-hughes.png
:white_check_mark:Succeeded
View

advocates/media/profiles/justin-yoo.png
:white_check_mark:Succeeded
View

advocates/media/profiles/michael-bender.png
:white_check_mark:Succeeded
View

advocates/media/profiles/prashant-sridharan.png
:white_check_mark:Succeeded
View

advocates/media/profiles/tanya-janca.png
:white_check_mark:Succeeded
View

advocates/michael-bender.yml
:white_check_mark:Succeeded
View

advocates/prashant-sridharan.yml
:white_check_mark:Succeeded
View

advocates/tanya-janca.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

advocates/index.html.yml

Line 0: [Warning] Invalid file link:(~/tweets).
Line 0: [Warning] Invalid file link:(~/map).

advocates/index.yml

[Warning] Unable to find uid "advocates.bryan-hughes".
[Warning] Unable to find uid "advocates.james-turnbull".
[Warning] Unable to find uid "advocates.michael-bender".
[Warning] Unable to find uid "advocates.prashant-sridharan".
[Warning] Unable to find uid "advocates.tanya-janca".
Line 0: [Warning] Invalid file link:(~/media/profiles/james-turnbull.png).
Line 0: [Warning] Invalid file link:(~/tweets).
Line 0: [Warning] Invalid file link:(~/media/profiles/tanya-janca.png).
Line 0: [Warning] Invalid file link:(~/map).
Line 0: [Warning] Invalid file link:(~/media/profiles/michael-bender.png).
Line 0: [Warning] Invalid file link:(~/media/profiles/prashant-sridharan.png).
Line 0: [Warning] Invalid file link:(~/media/profiles/bryan-hughes.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


which bert's feature do you use ?

hello,I notice that when use bert to generate feature ,there are four outputs in bert,
last_hidden_state 2.pooler_output 3. hidden_state 4.attention
which bert's feature do you use ? and could you please tell me the detail of generate language feature? use which layer?

Hi, I have met the same problem as u, do you figure it out ?
Any reply will help!

Please see this issue answer:
here


Consider merging scratch/gluon notebooks

(Just for discussion.)
I'm mainly interested in reading at a high-level as possible. However I'm finding I have to go through everything: I tried just reading the gluon notebooks, but they assume you've read through the scratch versions. Things like introducing datasets and how to load them.
If this was a print book, one alternative would be have the -scratch and -gluon versions in the same section, with the -scratch versions done as sidebars. I don't know if such a thing is possible in Jupyter notebooks.
Another alternative would be to split two notebooks into three; a first one introducing the data sets, how to load and prepare, and any theory. Then a short one on how to implement from scratch, then another short one on how to implement in gluon.

This is an important discussion that I've been postponing for now.
Reason to keep separate:
Preserves the one notebook, one working model flow
Reason to merge:
Much cleaner organization
@mli @piiswrong @smolix. Thoughts?

Just my two cents:

One important thing: from scratch implementation is part of the theory explanation, IMO, which makes this repo so valuable and not just a document. Believe it or not, not so many resources online explaining the details and tricks implementing the thoery (thanks cs231n!). So, I don't think splitting the scratch part from theory explanation is a very good idea. After all, who don't know how to copy-and-paste from API page? :-)

I agree that merging scratch and gluon results in the cleaner organization.

The best possible result may be something like spark tutorial, in which we are free to choose python or scala version. But of course it needs serious hack on jupyter notebook (or impossible), or writing some scripts and markdown files then automatically generating the website.

I think it's better to make both the from scratch and gluon versions self contained. Then make a separate index that doesn't list from scratch versions

Something like "quick introduction to gluon for deep learning experts"

I'd rather not have duplicated matter across scratch and Gluon. In fact I'm
thinking of reworking things to merge the scratch and Gluon tutorials
On Sep 3, 2017 1:40 PM, "Eric Junyuan Xie"<EMAIL_ADDRESS>wrote:

Something like "quick introduction to gluon for deep learning experts"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zackchase/mxnet-the-straight-dope/issues/181#issuecomment-326829837,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACR4ztXwz8dCjAafwWW8xXnYxdGPQGqMks5sew6jgaJpZM4PH4hp
.

@piiswrong

Then make a separate index that doesn't list from scratch versions

The problem I found was that the "gluon" tutorials assume you've read and worked through the "from scratch" version. Not just the algorithm theory, but things like introducing the dataset that is being used.


Compliance within pry-byebug

1st test: sucessful
cat import2.rb
require 'predictionio'
require 'pry-byebug'
 >
client = PredictionIO::EventClient.new('key from pio app list')
# binding.pry
client.create_event('$set', 'user', 2_017)

ruby import2.rb

Works fine and I can see the event created at http://localhost:7070/events.json?accessKey=same_access_key

2nd test: fail
cat import2.rb
require 'predictionio'
require 'pry-byebug'
>
client = PredictionIO::EventClient.new('key from pio app list')
binding.pry
client.create_event('$set', 'user', 2_018)

ruby import2.rb

when the interpretor stops calling:

client.create_event('$set', 'user', 2_017)

returns
fatal: No live threads left. Deadlock?
from /Users/jeff/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/predictionio-0.9.6/lib/predictionio/async_response.rb:25:in `pop'
and I can NOT see the event created at http://localhost:7070/events.json?accessKey=same_access_key

a second call to

client.create_event('$set', 'user', 2_000)

does not returns

expected
We can use PredictionIO-Ruby-SDK within pry-byebug
configuration
rbenv local 2.2.3 # also tested with 2.2.2
pry-byebug (3.3.0)
byebug (~> 8.0)
pry (~> 0.10)

We are not familiar with pry-byebug and use RVM instead of rbenv.


[Bug]504 Server Error when loading dataset which was already cached

Describe the bug
I have already cached the dataset using:
dataset = load_dataset("databricks/databricks-dolly-15k",
                        cache_dir="/mnt/data/llm/datasets/databricks-dolly-15k")

After that, I tried to load it again using the same machine, I got this error:
Traceback (most recent call last):
  File "/mnt/home/llm/pythia/train.py", line 16, in <module>
    dataset = load_dataset("databricks/databricks-dolly-15k",
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/datasets/load.py", line 1773, in load_dataset
    builder_instance = load_dataset_builder(
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/datasets/load.py", line 1502, in load_dataset_builder
    dataset_module = dataset_module_factory(
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/datasets/load.py", line 1219, in dataset_module_factory
    raise e1 from None
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/datasets/load.py", line 1186, in dataset_module_factory
    raise e
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/datasets/load.py", line 1160, in dataset_module_factory
    dataset_info = hf_api.dataset_info(
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/huggingface_hub/utils/_validators.py", line 120, in _inner_fn
    return fn(*args, **kwargs)
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/huggingface_hub/hf_api.py", line 1667, in dataset_info
    hf_raise_for_status(r)
  File "/mnt/data/conda/envs/pythia_ft/lib/python3.9/site-packages/huggingface_hub/utils/_errors.py", line 301, in hf_raise_for_status
    raise HfHubHTTPError(str(e), response=response) from e
huggingface_hub.utils._errors.HfHubHTTPError: 504 Server Error: Gateway Time-out for url: https://huggingface.co/api/datasets/databricks/databricks-dolly-15k

Steps to reproduce the bug

cache the databrick-dolly-15k dataset using load_dataset, setting a cache_dir
use load_dataset again, setting the same cache_dir

Expected behavior
Dataset loaded succuessfully.
Environment info

datasets version: 2.12.0
Platform: Linux-4.18.0-372.16.1.el8_6.x86_64-x86_64-with-glibc2.27
Python version: 3.9.16
Huggingface_hub version: 0.14.1
PyArrow version: 11.0.0
Pandas version: 1.5.3

I am experiencing the same problem with the following environment:

datasets version: 2.11.0
Platform: Linux 5.19.0-41-generic x86_64 GNU/Linux
Python version: 3.8.5
Huggingface_hub version: 0.13.3
PyArrow version: 11.0.0
Pandas version: 1.5.3

Trying to get some diagnostics, I got the following:
>>> from huggingface_hub import scan_cache_dir
>>> sd = scan_cache_dir()
>>> sd
HFCacheInfo(size_on_disk=0, repos=frozenset(), warnings=[CorruptedCacheException('Repo path is not a directory: /home/myname/.cache/huggingface/hub/version_diffusers_cache.txt')])

However, that might also be because I had tried to manually specify the cache_dir and that resulted in trying to download the dataset again ... but into a folder one level higher up than it should have.

same problem with a private dataset repo, seems the huggingface hub server got some connection problem?

Yes, dataset server seems down for now

@SingL3 You can avoid this error by setting the HF_DATASETS_OFFLINE env variable to 1. By default,  if an internet connection is available, we check whether the cache of a cached dataset is up-to-date.
@lucidBrot datasets' cache is still not aligned with huggigface_hub's. We plan to align it eventually.

Today we had a big issue affecting the Hugging Face Hub, thus all the 504 Server Error: Gateway Time-out errors.
It is fixed now and loading your datasets should work as expected.

Hi, @albertvillanova.
If there is a locally cached version of datasets or hub cached, when a network problem(either client or server) occurs, is it a better way to fallback to use the current cached version rather than raise a exception and exit?


Spanish Translation

qlcplus.xml
qlcplus.desktop
qlcplus-fixtureeditor.desktop

Thanks!
There are two more entries in qlcplus.xml...

I'll check that out and send another PR


Updates for ember 1.13+

Updated the documentation and script to be compatible (no deprecation warnings) under 1.13. Not yet tested, but should work with Ember 2.0 also.

+1

Sorry guys, thanks a lot for the PR. I haven't had much time on Ember.js lately. This plugin was written when I needed intl-tel-input on one of my client's project that uses Ember.js. It was released right after the project is closed. I didn't have time to write tests for it, and I really need to conduct some testing to make sure everything still works with this PR, especially that there were quite a lot of moving parts on Ember and Ember CLI.
Tests related PR are welcomed, otherwise I will see if I can put them together next week.

@justin-lau I just pushed up a PR to backfill several tests. If you don't have time to review, I'd happily take over as owner.

@tgreiser, @davidgoli helped added some tests to the repo. and I have managed to updated the repo to run with ember and ember-cli 1.13.x. I found that in this PR there are something more than just updating it to 1.13. Would you mind submitted separated PRs so that I understand more easily what they're about?

I'm closing this PR for now. Feel free to bring this up again if you think there is necessity.


Add support for time-lost jewels

Item Class: Jewels
Rarity: Rare
Fulgent Shard
Time-Lost Ruby
--------
Radius: Small
--------
Item Level: 64
--------
Small Passive Skills in Radius also grant 2% increased Totem Damage
Notable Passive Skills in Radius also grant 4% increased Magnitude of Bleeding you inflict
Notable Passive Skills in Radius also grant 7% increased Stun Buildup with Maces
--------
Place into an allocated Jewel Socket on the Passive Skill Tree. Right click to remove from the Socket.

These modifiers are currently not available on the trade website. Until they are supported by the trade website, we can't do more


Unblacklist gulp-rollup

With the release of gulp-rollup v2, this plugin no longer breaks the guidelines as far as I know. It will only read from the filesystem if the user explicitly allows it through an option.

@Permutatrix great work!


[9.x] Get last item of takeUntilTimeout method on a LazyCollection

This PR allows the takeUntilTimeout method of a LazyCollection to accept a second parameter: a closure. This closure will be executed when the timeout has been reach and it will return the first item that it was not able to process anymore.
$lazyCollection->takeUntilTimeout(now()->addMinute(), function ($firstNotTakenItem, $firstNotTakenItemKey) {
    // ...
});

Why?
Sometimes you need to process a lot of data in a job and you can not do it in one job because the job will timeout. Let's say you have thousands of users that need to be processed.
class ProcessUsersJob
{
    public $timeout = 60;

    public function handle()
    {
        User::query()
            ->where(...)
            ->cursor()
            ->each(fn ($user) => ...);
    }
}

This job will timeout if there a lot of users. This is were the current takeUntilTimeout method comes into play. We could just process users until we reach the timeout, but than we still need to know which users we have not processed yet. So we need to keep track of the last processed user in order to prevent duplicate processing. This creates a lot of overhead code which will be the same in every job that processes lots of data.
class ProcessUsersJob
{
    public $timeout = 60;

    public function __construct(
       public ?int $lastProcessedUserId = null
    ) {}

    public function handle()
    {
        $lastUserId = User::query()
            ->where(...)
            ->when($this->lastProcessedUserId, fn ($query) => $query->where('id', '>', $this->lastProcessedUserId)
            ->orderBy('id')
            ->cursor()
            ->takeUntilTimeout(now()->addSeconds(55))
            ->each(function ($user) {
                // Remember the last user that has been processed
                $this->lastProcessedUserId = $user->id

                // ...
            })
            ->last()?->id;

        // If the last user id equals the last processed user id, then that means
        // we have processed all users and we do not need to dispatch a new job
        // to process the remaining unprocessed users.
        if ($lastUserId === $this->lastProcessedUserId) {
            return;
        }

        static::dispatch($this-> lastProcessedUserId);
    }
}

This can be simplified if the takeUntilTimeout returns the first item that it could not process anymore. Now we can just dispatch a new job from inside that closure and we don't need a that boilerplate code anymore.
class ProcessUsersJob
{
    public $timeout = 60;

    public function __construct(
       public ?int $firstUnprocessedUserId = null
    ) {}

    public function handle()
    {
        User::query()
            ->where(...)
            ->when($this->firstUnprocessedUserId, fn ($query) => $query->where('id', '>=', $this->firstUnprocessedUserId)
            ->orderBy('id')
            ->cursor()
            ->takeUntilTimeout(now()->addSeconds(55), function ($user) {
                static::dispatch($user->id);
            })
            ->each(fn ($user) => ...);
    }
}

I'm not really familiar with the types of static analysis. Can anyone help me and tell me what I did wrong? 🤔

This closure will be executed when the timeout has been reach and it will return the first item that it was not able to process anymore.

Hmmm. This actually surfaced a bug in the current implementation of takeUntilTimeout. It currently fetches one extra item, which it shouldn't.
Instead of the implementation here, I think we should instead fix takeUntilTimeout first. Then, we can call the callback (which should really be called $onTimeout) and pass it the iterator, so that it can decide itself whether to pull an additional item.
It's gonna be a little more work in the callback, but I think that's more correct.

@gdebrauwer do you know how to address @JosephSilber's comments?

This PR changes the public interface so it should target master.

do you know how to address @JosephSilber's comments?

@gdebrauwer if you need help, just say the word and I'm there with assistance.

This pull request should target master, as it is a breaking change.

@netpok @JosephSilber is the fear that people are overriding takeUntilTimeout with their own custom implementation? If so, I'm not sure if that would be common at all in practice?

For me it's more like "a major version means there won't be a breaking change" thing, also php already provides "magical ways" to add additional parameters to a function without breaking compatibility:
    public function takeUntilTimeout(DateTimeInterface $timeout)
    {
        $callback = func_num_args() > 1 ? func_get_arg(1) : null;

        // rest of code...
    }

I created a seperate PR that fixes the implementation of the method. Let me know what I should do this PR: target master or 9.x 🙂 I assumed the change would not be a breaking change, because it is an optional parameter and the method is not a method from an interface

@gdebrauwer is this PR superseded by https://github.com/laravel/framework/pull/41370?

That PR fixes an issue that was already present in the takeUntilTimeout method. When that PR has been merged, I will need to create a new PR to add the new extra callback parameter to takeUntilTimeout method, but I don't know yet if I should target master or 9.x 🙂

An extra argument is added to a method here so it should target master. Thanks

@gdebrauwer it does not matter if its an optional parameter.
Take a look here: https://3v4l.org/h5gkL


Update Engine

Hello @maborak! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file ebooksdl/engines/coderprog.py:

Line 9:1: E265 block comment should start with '# '


store_metadata causes file contents to be treated as modified, not the analysis database

As of 2862
Describe the bug
Using the store_metadata sets the wrong dirty bit:

When it should instead set the analysis database being dirty (as demonstrated by renaming a function and closing):

Actually, this just looks like an improper fix for #1174, marking this as a duplicate and re-opening the original.


CLI flag to set Jetty's request header buffer size

My apps have very large Headers which were overflowing Jetty's
Request Header Buffer,  this resulted in response: 413 FULL head
To recreate the problem do any GET with a single header larger
than 9k or so.
Also added console output confirmation when Jetty related command
line flags are specified (there are 3 now total).  They previously
weren't output even when applied which leads to confusion.

Will submit a separate pull request that includes an acceptance test and is synced with 1.54.


Migrate Field name along with value in azure devops

how can we include the field name along with value in a text .for eg supposose a field named Affect Versions in JIra is migrated to some text field  in azure devops so how can miggrated as affect version - value in the text field of azure devops

That's a feature in Jira Migrator PRO. You can read more here: https://github.com/solidify/jira-azuredevops-migrator?tab=readme-ov-file#jira-azure-devops-migrator-pro
Reach out to us at<EMAIL_ADDRESS>to inquire about the product and get a quote.


Replace all unwrap() with expect()

Motivation
We should refactor all unwrap() in SeaORM and use expect() insead. This will force us to provide a explicit message when panicking. This is far more readable than a muted panic.

I wish to take this into account by the way, necessary for error segmentation :https://github.com/SeaQL/sea-orm/issues/881

Oh Nice I wanted to say this a long time ago.
But it's also good to think about whether we can avoid panicking on a case by case basis.

+1

Same here.
Btw, we should document all the method that throw panic, specify under what circumstance it will panic.
Deny this linter and it will tell you which methods need to be documented
https://rust-lang.github.io/rust-clippy/master/#missing_panics_doc

I wish to take this into account by the way, necessary for error distinguish :#881

Hey @baoyachi, what do you mean?
I think in general, we should avoid panic. And should throw Err instead.
Did you mean that?

Can we have a new label named "Motivation" with prefixes like beginner, moderate and expert ....... Would help to filter the issues

I'm going to do a cleanup on the open issues and label some beginner friendly issues as "good first issue". And convert Q&A into discussion.

Can we have a new label named "Motivation" with prefixes like beginner, moderate and expert ....... Would help to filter the issues

I'm going to do a cleanup on the open issues and label some beginner friendly issues as "good first issue". And convert Q&A into discussion.

I agree


Match height tabs bug

Fixes #9678 & #9677
@ncoden @kball for review
Special Thanks: @wonkeythemonkey for reporting and the code.
Have tested it. works perfect now

Commits of #9659 is coming here too but as this is a correct branch for bugfix ( develop ) ...... so i guess i did the right thing.

Noted one change that was unnecessary, other than that this looks good.

done @kball .
Also plz close #9677 on merge as i forgot to tag that for closure in my commits

Merged! Thanks @IamManchanda

Always pleasure kevin sir


Add procedure_cost to fulfillment model

I rule and have completed some work on Case Manager that's ready for review!
This pull request makes the following changes:

adds procedure_cost to Fulfillment model so that rake db:seed does not error out

It relates to the following issue #s:

Fixes https://github.com/DCAFEngineering/dcaf_case_management/issues/1540

Containers are failing to spin up at all it looks like?

yeah we're having a problem with builds from forks. I'll add you to the github group in a bit.

cool coool! thanks @colinxfleming !

Closing in favor of https://github.com/DCAFEngineering/dcaf_case_management/pull/1542


Notifications when builds and pipelines have finished executing

Notifications should be made optional.
Without notifications the user always needs to check the pipeline or build in order to know whether or not it is done building.
Notifications can be browser based (when inside the application) but possible also via integrations such as email or Telegram.

Would be great if we have some form of webhooks. This way users can specify a URL to which we will send the appropriate requests to indicate applications status, e.g. pipeline run failure.

also via integrations such as email

or Slack! I would really like to see this feature added to be honest :smile:

Also for job failures - I find myself realizing that some runs have failed after a few hours or days.
I think webhooks are the way - folks can then connect that to any system they like.

Upvoting this. Impossible to keep track of failures at the moment, unfortunately.

Upvoting this too. Just found out some runs have failed a few hours ago. This notification feature could be a game changer :)

Upvoting this as well, for job failures in particular. It isn't hard to monitor when you only run a few jobs or you are using it for your own purposes. However, we are frequently running into this problem now that we have many jobs run every night, and many people within our organization rely on the data that flows with these job runs.

Hi @liflovs @hamisB @sawtooth9, we are going to start working on this in a few days, we are exploring an array of options and collecting preferences and brainstorming a bit. Would webhooks be a strong preference here, or is some kind of jobs dashboard (https://github.com/orchest/orchest/issues/485) more likely to suit your workflow? Solutions aren't exclusive, so feel free to propose.

@fruttasecca dashboard is "nice" to have but webhooks is "must" to have imho, because we need to know sometimes immediately when something fails and react. In some way we can already check on jobs if we want to, but we have to do it proactively

@fruttasecca The ideal workflow for us would likely be something similar to what is described in #865 so we could create/add to a report that is alongside all of our other monitoring in the dashboard we use day-to-day. That said, a built-in dashboard or webhook would be extremely helpful as well. Most of our jobs run overnight so the immediacy of the webhook isn't necessary for us, but being able to send out a slack notification when a job fails or collecting the events from a webhook would be a great feature.

For everyone interested in enabling notifications in Orchest (which were introduced in v2022.06.3), check out our docs: https://docs.orchest.io/en/stable/fundamentals/notifications.html


[SMALLFIX] close InputStream in DataFileChannelTest

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5814/
Test PASSed.

LGTM


feat: add optimism x-chain

Better to document a bit better on the forwarder what are the L1_CROSS_DOMAIN_MESSANGER_ADDRESS and the CANONICAL_TRANSACTION_CHAIN


Some feedback after testing

Tested it and works fine but to get it working I needed to fork it:

My project uses Symfony 6 and your tool requires version 7 of the console and process components. The tool works perfectly fine with version 6 and will probably work with even lower versions, so you may want to relax those requirements
You added some "replace" configs to your composer.json. This broke my system as it removed the symfony string component which we use
Currently you need to have run composer install on your project because it tries to load an autoload file which will not be there if you have not run this

Release will be fully downgraded to require only PHP 7
2+ and solve all of these issues. Stay tuned, expected this week

I managed to make it work :)
This version is ready to run on PHP 7.2+ with no requirements: https://packagist.org/packages/tomasvotruba/phpstan-bodyscan#0.1.9
Give it a try :+1:

Works perfectly with no dependencies and no issues. Great job


GPU Support

I am able to run llava-cpp-server on CPU without an issue. Is there a way to run llava-cpp-server on GPU?

I believe llama.cpp has some CUDA support. I include llama.cpp as a sub repo so I would recommend looking at their docs to see whether this is true and if so, whether any build flags need to be enabled.


xcodebuild action

Exposes xcodebuild CLI tool via fastlane action with defaults, environment variables & other nice things.
Usage:
lane :build do
  # Create an archive. (./build-dir/MyApp.xcarchive)
  xcodebuild(
    archive: true,
    archive_path: './build-dir/MyApp.xcarchive',
    scheme: 'MyApp',
    workspace: 'MyApp.xcworkspace'
  )

  # Export a signed binary (./build-dir/MyApp.ipa)
  xcodebuild(
    export_archive: true,
    export_path: './build-dir/MyApp'
  )
end

The action supports the following .env vars:

PROJECT
WORKSPACE
SCHEME
BUILD_PATH

For example, if your .env file looked like this:
PROJECT="./MyApp.xcodeproj"
WORKSPACE="./MyApp.xcworkspace"
SCHEME="MyApp"
BUILD_PATH="./build"

...then you can simplify the lane usage to:
lane :build do
  # Create an archive. (./build/MyApp.xcarchive)
  xcodebuild(
    archive: true
  )

  # Export a signed binary (./build/MyApp.ipa)
  xcodebuild(
    export_archive: true
  )
end

When archiving, the path to the .xcarchive file is cached in SharedValues for xcodebuild to use in a subsequent export.
When exporting, the path to the generated ipa is cached in SharedValues::IPA_OUTPUT_PATH for any deploy steps (i.e. Crashlytics) to use (should this also store in ENV["IPA_OUTPUT_PATH"] as the ipa action does now?).
I'd like to add even simpler alias actions for the most common xcodebuild operations; archive, export, build, & test.  Something like: 'xcarchive', 'xcbuild', 'xcexport', and 'xctest'.
This could reduce the usage to a single action verb, for simpler projects.
I was thinking of bundling these into the same module/file as alias classes. Thoughts?
Example usage of alias actions in a complete continuous deployment lane:
lane :inhouse do
  # Run tests
  xctest(
    destination: "name=iPhone 5s,OS=8.1"
  )

  # Generate XML code coverage
  gcovr(
    xml: true,
    output: "./code-coverage/report.xml"
  )

  # Clean the project
  xcclean

  # Create an archive
  xcarchive

  # Fetch/install provisioning profile
  sigh

  # Export a signed IPA
  xcexport

  # Deploy build to Beta
  crashlytics

  # Notify the HipChat room that the build was released
  hipchat(
    message: "iOS build successfully deployed to Beta!",
    channel: ENV["HIPCHAT_ROOM"],
    success: true
  )
end

I'd like to add even simpler alias actions for the most common xcodebuild operations; archive, export, build, & test. Something like: 'xcarchive', 'xcbuild', 'xcexport', and 'xctest'.
I was thinking of bundling these into the same module/file as alias classes. Thoughts?

^^ Yes yes, I agree with this!

Added alias/helper/companion actions:
xcarchive
xcarchive(
  archive_path: "./build-dir/MyApp.xcarchive",
  scheme: "MyApp",
  workspace: "MyApp.xcworkspace"
)

xcbuild
xcbuild(
  scheme: "MyApp",
  workspace: "MyApp.xcworkspace"
)

xcclean
xcclean

xctest
xcarchive(
  destination: "name=iPhone 5s,OS=8.1",
  scheme: "MyApp",
  workspace: "MyApp.xcworkspace"
)

Thank you so much @dtrenz for working on this. Great result! :rocket:


Support excluding files via System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute

People are familiar with the System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute to mark files for exclusion of test coverage.
Plus we want to report the line coverage using the inbuilt dotnet test coverage tooling, for our most of CI/CD pipeline cases (where we use the ExcludeFromCodeCoverageAttribute). And use Stryker for pull request builds (since it really slows the build time to a point where it isn't viable to run on every build)

Hi, @brooknovak 👋 welcome to the club.
I believe this is an issue related to Stryker.NET. Feel free to open an issue there


extracting all etext numbers, titles, and authors

How can I extract all the etext numbers, titles, and authors from the cache?
In other words, how can I first create a list of all the etext identifiers, titles, or authors, and then loop through the list(s) to download the actual text. Based on the documentation (and my ability to read the actual function calls), I don't see a way to so something like this:
from gutenberg.query import get_metadata
from gutenberg.cleanup import strip_headers
from gutenberg.acquire import load_etext
keys = get_etexts('title', '*')
for key in keys :
  text = strip_headers(load_etext(key)).strip()
  print( text, key + '.txt')

Put yet another way, the system seems to be implemented such that one needs to know an exact etext number, title, or author value before they are able to successfully query the cache.
P.S. I guess I'd really like a list of all the valid etext numbers or authors rather than the titles.

Does the code/data in https://github.com/hugovk/gutenberg-metadata help?

@hugovk, yes, thank you. This helps. It is not exactly what I was seeking, but it is a step the right direction. I have downloaded and am running your code. It is outputting the json file which I will loop through to fill an SQLlite database, and from there do various types of additional indexing.
I appreciate the good work done by @c-w, and I thought about sequentially looping through the etext identifiers starting at #1 and continuing until getting an error, but I was wondering whether or not some identifiers were missing for one reason or another.
Put another way, both of you (@c-w and @hugovk) saved me a lot of time. Thank you.

If I understand correctly, you're essentially looking to get a list of all the etexts and then look up some metadata for each of the etexts? If so, you may also be able to compile a list of all the etext identifiers using a SPARQL query against the metadata graph:
from gutenberg.acquire.metadata import load_metadata

metadata = load_metadata()

results = metadata.query('''
select ?ebook
where {
  ?ebook a <http://www.gutenberg.org/2009/pgterms/ebook>
}
''')

text_ids = (int(result[0].toPython().replace('http://www.gutenberg.org/ebooks/', ''))
            for result in results)

print(next(text_ids))  # 25197
print(next(text_ids))  # 25198

Let me know if this helps!

The above is interesting and good for future reference, but I'm going to go with a Personal Plan B.
More specifically, I'm going to use the JSON output of https://github.com/hugovk/gutenberg-metadata to create an SQLite database. From there I will loop through the database to index the content using Solr. To "ferment" the Solr index I will probably add full text as well as statistically significant keywords calculated using TFIDF or some other NLP method.
In my copious spare time I will look at the repository in its canonical form -- a triple store.  :-)

If you're interested in building a SQLite database, note that gutenberg does already have first-party support for a SQLite backend:
# first, set up gutenberg to use the SQLite backend

from gutenberg.acquire import set_metadata_cache
from gutenberg.acquire.metadata import SqliteMetadataCache

cache = SqliteMetadataCache('/my/custom/location/cache.sqlite')
cache.populate()
set_metadata_cache(cache)

# now you can use the library as normal

from gutenberg.query import get_metadata

print(get_metadata('title', 2701))

Perhaps the schema of the database that gets built in this way may be useful to you.

Thank you for the prompt reply, and using the existing triple store, extracting the metadata, and then filling my own local SQL database seem robust and straight forward.


Improve DiskANN GetVectorByIds Performance

issue: #919

Vec same as before, test script without sleep(300ms)
Get 50 ids, measure the time of 200 iterations, DiskANN cache off
Initial runs are ignored
| Before (s) | After (s)
-- | -- | --
Concurrency 1 | 0.151025 | 0.1153
Concurrency 4 | 0.431405 | 0.292123
Concurrency 20 | 1.86118 | 0.962817
Decreased around 23% of total time and 50% when concurrency was high. It should now perform much better when concurrency is high or the number of requested IDs is large.
The fluctuations of I/O latency are considered normal to NVMe SSD.

/lgtm


Update fleet output resource to new API schema format

Updated fleet output to use new schema format, where each output kind now has a strongly typed data structure to hold the relevant configuration items.
Relocated the fleet api generators to match repo style, and cleaned up the schema downloader and filtering functions.
Expose 'ca_trusted_fingerprint' config value
Add test case for logstash output
Update Fleet API version to v8.10.0

Closes #428

@taylor-swanson what happens when this is run against an older Elasticsearch version?

@tobio

It looks like we're still running the relevant acceptance tests on 8.6+ so I'm assuming there's no compatibility issues?

That's my understanding as well. The changes to the Fleet OpenAPI schema were to better define the output types and how the output API should be used. As far as I can tell, this doesn't actually change what data we send to the Fleet API. What it did change was the code that was generated, which necessitated this change. Thankfully, we have the acceptance tests running against the different versions to validate things still work.


Ignore uneeded files for distribution

Change Summary
A good idea is to exclude unneeded dev files from the final production zip archive file, which is also downloaded by composer (unless --prefer -source flag is specified).
Those files are actually only useful when working on the library itself.
In case you are not familiar, further information about export-ignore can be found below for instance:

http://www.pixelite.co.nz/article/using-git-attributes-exclude-files-your-release/
https://madewithlove.be/gitattributes/

I hope it helps @kishorenc / @AbdullahFaqeir 😊
PR Checklist

[x] I have read and signed the Contributor License Agreement.

@karakhanyans Would you mind having a look? 🤔

@pH-7 We apologise for taking forever to review this PR, thank you for it, I went over the references you've mentioned and this actually is helpful, Thanks!.


swiftmac todos

Add function swiftmac-configure to mac-voices.el. 2. Update logic in voice-setup  by adding swiftmac to the if-mac test. 3. Move any/all swiftmac setup into swiftmac-configure.

@parhamdoustdar This is the one I would love your help with, getting these three pieces in place.

From other ticket, merged into this one (I think there is an official way to merge tickets but I didn't bother finding it).
This is a large ticket to create a swiftmac-setup.el that would do stuff like
setup defcustoms for the settings swiftmac supports
use dynamic voice selection (need separate ticket for this)
add to key places in the code like the multi servers, example:
(push "swiftmac" tts-multi-engines)
make it use new features like tts_set_pitch_multiplier and if possible tts_set_voice instead of the embedded voice codes, in a perfect world, no more embeddings / codes
(maybe) allow different voices for like comments versus code, I think I would like this
(maybe) new features like rate change on numbers.

If nobody else is working on this bit, I'm happy to have a crack. Although my elisp is not that great sure I can make something work and polish from there also happy to collaborate if somebody has a start already

@bartbunting features are in now, [{voice ...}] and [[pitch ...]] both as codes, would love your help with this, as I am still chasing a rare bug in swiftmac and want to focus on sharpwin after that.  Sharpwin will follow whatever you create for swiftmac, just tweaked for windows voices and such.

I dont know if the mac server was remote-tts capable, but if possible,
it would be nice for swiftmac to enable the remote tts feature a la
linux; it would make the Mac a more attractive client for those wishing
to program in the cloud.
On Linux this is done via a small TCL wrapper (tcl because the main
server is TCL), that wrapper basically opens a tcp socket, dups that to
stdin/stdout and lets the main server to do the work as usual.
--

So, the "swiftmac" version you saw was a find and replace that had broken
things so it was rolled back.  I had turned "emacspeak" into "eswiftmacspeak"
among other mistakes and invalid replacements.
Due to incompatibilities between mac and swiftmac, we will need our own prefix
and need to change some things like rate into a float, etc.

On Apr 23, 2024, at 14:44, bartbunting @.***> wrote:
So I am slightly confused. We have a swiftmac-voices.el
All the variables and defuns inside that were using swiftmac as their prefix.
The recent commit has changed them back to using Mac as a prefix.
I'm happy to work with anything but just want to be clear on if that was intentional or not. And what the correct answer is.
If we keep Mac as the prefix in someways it seems more logical although it will likely break anybody who is still having a working Max server. That's not me. But not sure if anyone else does.
It would be good to get some clarity on this before I go and change things.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

--
Robert Melton
@.***

Another question is at the moment we define Paul as whatever the system default voice is. In someways that's great because people get the same voice in emacspeak that they defined as their system default on the Mac. In other way, it's annoying because we don't actually know what voice they're using and people may get an inconsistent result. my thought would be to set it to Alex by default and let people change it. Should they wish to.
That way everyone starts from a common place. Especially if we end up using actual voice changes rather than parameters given Ltd in how many knobs we have to turn at the moment.

I feel like Alex is the most popular, but I am not 100% certain it is
installed by default on 14+.  I am fine making the change because even
if you send junk, it will work because it will fallback to the valid
system default voice.
So, I agree with making it Alex.

On Apr 23, 2024, at 14:50, bartbunting @.***> wrote:
Another question is at the moment we define Paul as whatever the system default voice is. In someways that's great because people get the same voice in emacspeak that they defined as their system default on the Mac. In other way, it's annoying because we don't actually know what voice they're using and people may get an inconsistent result. my thought would be to set it to Alex by default and let people change it. Should they wish to.
That way everyone starts from a common place. Especially if we end up using actual voice changes rather than parameters given Ltd in how many knobs we have to turn at the moment.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

--
Robert Melton
@.***

@tvramen
Yeah, I actually got the code to add a -p in a branch somewhere, just need
to reintegrate it and maybe make a wrapper launcher that just passes the
flag, because swiftmac directly listens the port rather than routes data
to stdin.

On Apr 23, 2024, at 13:57, T. V. Raman @.***> wrote:
I dont know if the mac server was remote-tts capable, but if possible,
it would be nice for swiftmac to enable the remote tts feature a la
linux; it would make the Mac a more attractive client for those wishing
to program in the cloud.
On Linux this is done via a small TCL wrapper (tcl because the main
server is TCL), that wrapper basically opens a tcp socket, dups that to
stdin/stdout and lets the main server to do the work as usual.
--
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

--
Robert Melton
@.***

I have it working as far as I can tell.
However we are somewhat stuck in the fact that there is no nice way at the moment to make ACS work as we don't have multiple dimensions to work with.  It would be great if we could artificially create some using some post processing of the sound or something.
Anyway there are two patches, one to swiftmac for swiftmac-voices.el and one to emacspeak for voice-setup.el
I include below some lisp code to setup some voices.  This is user specific and depends on the actual voices being installed on your system.
This needs significant tuning and was more of a test than anything.
; define some voices so we can test things are working
(swiftmac-define-voice voice-bolden "[{voice en_US:Fred}]  [[pitch 0.8]]")
(swiftmac-define-voice voice-animate "[{voice en-US:Kit}] [[pitch 1]]")
(swiftmac-define-voice voice-animate-extra "[{voice en-US:Kit}] [[pitch 1.5 ]]")
(swiftmac-define-voice voice-lighten "[{voice en-AU:Matilda}] [[pitch 1]]")
(swiftmac-define-voice voice-lighten-extra "[{voice en-AU:Matilda}] [[pitch 1.1]]")
(swiftmac-define-voice voice-smoothen "[{voice en-UK:Daniel}] [[pitch 1]]")
(swiftmac-define-voice voice-monotone "[{voice en-US:Eddy}] [[pitch 1]]")
(swiftmac-define-voice voice-monotone-extra "[{voice en-US:Eddy}] [[pitch 1.5]]")
Let me know if it works for you.
emacspeak.patch
swiftmac.patch

Thanks, this is super exciting!  I will try in the morning.
On more customizations, I have a pathway to it but it requires a heavy
lift that I won't start on till next stable release of Emacspeak.
The problem is that I am highly sensitive to latency, so post processing
in my experimentation can never take more than 50ms and feel acceptable
to me on a m1. Right now notifications server manages to just barely stay
in this window but it is more forgiving in terms of feeling the latency.
That 50ms also has to dump the Speech Synthesizer output to pcm and then
do any processing, there is no way on MacOS to hook directly from the
speech synthesis to AudioKit.
Now, with some optimization and concurrently processing the stream as
I write it I think 50ms is doable, but I don't think I can get it
working in like next couple days.  So stable will ship with swiftmac
2.x and effects will be a 3.x feature.
Thanks again Bart!

On Apr 23, 2024, at 23:58, bartbunting @.***> wrote:
I have it working as far as I can tell.
However we are somewhat stuck in the fact that there is no nice way at the moment to make ACS work as we don't have multiple dimensions to work with. It would be great if we could artificially create some using some post processing of the sound or something.
Anyway there are two patches, one to swiftmac for swiftmac-voices.el and one to emacspeak for voice-setup.el
I include below some lisp code to setup some voices. This is user specific and depends on the actual voices being installed on your system.
This needs significant tuning and was more of a test than anything.
; define some voices so we can test things are working
(swiftmac-define-voice voice-bolden "[{voice en_US:Fred}] [[pitch 0.8]]")
(swiftmac-define-voice voice-animate "[{voice en-US:Kit}] [[pitch 1]]")
(swiftmac-define-voice voice-animate-extra "[{voice en-US:Kit}] [[pitch 1.5 ]]")
(swiftmac-define-voice voice-lighten "[{voice en-AU:Matilda}] [[pitch 1]]")
(swiftmac-define-voice voice-lighten-extra "[{voice en-AU:Matilda}] [[pitch 1.1]]")
(swiftmac-define-voice voice-smoothen "[{voice en-UK:Daniel}] [[pitch 1]]")
(swiftmac-define-voice voice-monotone "[{voice en-US:Eddy}] [[pitch 1]]")
(swiftmac-define-voice voice-monotone-extra "[{voice en-US:Eddy}] [[pitch 1.5]]")
Let me know if it works for you.
emacspeak.patch
swiftmac.patch
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

--
Robert Melton
@.***

@bartbunting Where would I do those voice definitions?

@bartbunting nevermind, got it all working, updating docs, actually think we got everything on the list here.  Simplifies setup.  Cool stuff for v2!


different conditions

Hello, I have different conditions and their controls and I am interested in using scGRN but I am not sure how to start. I am familiar with pyscenic and computing aucell and RSS. How to use scGRN when I have different conditions ? do I keep them in the same object? or different ones  (I have the  2 auc matrix for each condition  (healthy included in it) Is there a notebook to follow to compare between them?

@Flu09 thank you for showing interest in using scGRN!

How to use scGRN when I have different conditions ? Is there a notebook to follow to compare between them?

This notebook contains the code where you can compare samples. For example, on the picture below under group I label samples which are controls / moderate and severe cases - this is the metadata that you need to create. You can create a similar dataframe and try to run the notebook, I'm here to help. Please expect some errors because the code was tested only on COVID dataset.

Prior to running the notebook, you need to run the network_inference pipeline (I assume you already ran single cell processing with Seurat or similar). Depending on the type of network you are inferring, you can also do community analysis.

do I keep them in the same object?

All GRNs are stored as physical objects on disc either as gpickle networkx objects or adjacency matrices. When you run analysis functions, the function loads the data and provides the visualizations.
If you provide more concrete information what you are trying to achieve, maybe I can point you to exact code that you can use. What type of network you are using - TF <-> target, or gene <-> gene? As you used aucell, I assume you want to focus on pathway analysis? You can have a look at this notebook in this case.


removeClippedSubviews not working

Coll project.
Tried to use it with ListView. removeClippedSubviews={true} has no effect. Important setting for performance improvement.

@kinhunt Thanks for reporting. I'll have to do some testing.
Which react-native version are you using?

@jaysoo 0.16

@kinhunt I can confirm that removeClippedSubviews prop gets passed to the inner ScrollView, but I'm not sure how to go about testing it is working except memory profiling.
Can you provide some testing details?
I've also updated the example to nest ListView under ParallaxScrollView instead of the other way around, maybe this will help? https://github.com/jaysoo/react-native-parallax-scroll-view/blob/master/Example/Talks.js#L91-L100

@jaysoo I followed your example. You can shake and open the RN performance profiler on your device or simulator. It shows the number of views. It is stable if the removeClippedSubviews is ON.

@kinhunt Sorry for the delayed response. As far as I can tell, the attributes are set on ScrollView properly. Perhaps there's something going on in RN 0.16.0 that is causing problems?
I'm going to close this ticket for now, but if you continue to run into this issue feel free to reopen.

@jaysoo sure. thank you. I will do some tests and give you more details.

@jaysoo happy new year. Unfortunately, the problem is still there with RN 0.17.0

@kinhunt I'll take another look at this.

@kinhunt
Sorry for the delay, been a busy month so far! I dug into the issue and found that removeClippedSubviews is working, but I forgot to add overflow: hidden in my ListView example. I've update the example now.
Here's the test I used. The number of views stays constants at around 55 while scrolling down.

Going to close this for now, feel free to re-open again if anything else comes up.


otelzap zapcore.ArrayMarshalerType is not implemented

The current implementation silently drops a field without any errors.
https://github.com/uptrace/opentelemetry-go-extra/blob/479240184b44f36f1623c6a3c5426e5ff0468c25/otelzap/otelzap.go#L688

It would be wonderful if someone reviewed https://github.com/uptrace/opentelemetry-go-extra/pull/31