Lighthouse http issue

When lighthouse tries to check if http redirects to https (I think) it encounters an error (ERR_CONNECTION_RESET)
This site can’t be reached
So http://localhost:8080/ doesn't work
Can anyone try to reproduce this issue?
I used npm run serve for this

Hi @unlocomqx, does opening https://localhost:8080 work without any SSL errors ? Seems like certificates are incorrect. What os are you on?

I just checked this issue, it works fine for me. Although if https is used, its better to redirect him to https even if he opens in http. Could that be possible?

Chrome is showing "Valid cert" in the security tab of the devtools
I switched to using a h2 apache local server pointing to my build dir for now but I'll try to investigate this ERR_CONNECTION_RESET problem
So I'm fine for now but I'm still curious

When I open http://localhost:8080 this error comes up
http: TLS handshake error from [::1]:58618: read tcp [::1]:8080->[::1]:58618: use of closed network connection
I'm on windows 10 x64
It seems similar to https://github.com/GoogleChrome/simplehttp2server/issues/16

Hi @unlocomqx - is it possible you have a Firewall prevent this from working?  You can check by spawning the server on a different port:
PORT=9090 npm start

then open http://localhost:9090

I already opened all ports temporarily to make a test but nothing works.
I also tried 9090 and also other hosts but no success
I opened this issue https://github.com/GoogleChrome/simplehttp2server/issues/33 hoping I could find a solution
Thank you for this awesome framework, I'm getting the hang of it and it's great!

Perfect, we'll track there and only close this issue once it's resolved :)

Same issue here.
Can't run lighthouse after preact build and preact serve.
Seems like at some point lighthouse tries to redirect to http instead of https causing this ugly error :
http2: server: error reading preface from client [::1]:39646: read tcp [::1]:8080->[::1]:39646: read: connection reset by peer
  http2: server: error reading preface from client [::1]:39650: read tcp [::1]:8080->[::1]:39650: read: connection reset by peer
http2: server: error reading preface from client [::1]:39652: read tcp [::1]:8080->[::1]:39652: read: connection reset by peer
http2: server: error reading preface from client [::1]:39648: read tcp [::1]:8080->[::1]:39648: read: connection reset by peer
http2: server: error reading preface from client [::1]:39654: read tcp [::1]:8080->[::1]:39654: read: connection reset by peer
  http: TLS handshake error from [::1]:39672: read tcp [::1]:8080->[::1]:39672: use of closed network connection

P.S: working on Ubuntu 16.04

@Jonarod check the issue I linked above, it's a know issue with simplehttp2server
I ended up creating a http2 nginx server pointing to my build directory to have proper redirection and lighthouse audits.
Lighthouse will test your http > https redirection that's why it makes a http request
https://developers.google.com/web/tools/lighthouse/audits/http-redirects-to-https

Mmmm too much for me sorry: I lost like 1h just to understand how to:

setup nginx
generate self-signed certificate
Make it work locally

I ended up with serve-https from npm.
Quick and easy:
npm install --global<EMAIL_ADDRESS>
then browsing to my /build repo and finally:
serve-https

And we're good to go !!


Bump Abacus. Increase CC poll period and page size

Signed-off-by: Nikolay Maslarski<EMAIL_ADDRESS>

Coverage remained the same at 89.488% when pulling 99261114d5c2709144edf679244862f17f8a2d2a on SAP:unload-cc into c92c5b6d51c69e8a644bfbcabbe45d50479d8e42 on cloudfoundry-incubator:master.


显卡要求

请问作者使用什么显卡跑的，跑了多久？

Hi, for training LEMMA, 4 GPUs with 12G is enough.

Hi, for training LEMMA, 4 GPUs with 12G is enough.

好的，谢谢！


Documentation error in installation instructions

Describe the bug
Documentation here has incorrect curl syntax:
https://docs.pixielabs.ai
./bash -c "$(curl-fsSL https://withpixie.ai/install.sh)"
Correct syntax for most systems would be:
bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"

@elsonrodriguez, thanks for pointing this out. It has been fixed and deployed in the latest docs.


Rails PR

The gem is a great fix for now but if it hasn't already you should open this as a PR for rails as well.

Thanks, I wasn't sure how well received it would be or how long it would take to get into a release, so I figured a gem was a good first step. I'll see if I can reroll these changes into a PR for Rails, though it may need to be guarded by a new framework default configuration value for ActionView as well.

Well, this is now merged into Rails! 🎉
This gem should still be useful for Rails 6.1.x users, and possibly others with work on #1.


flow: Add flow types for navigation params in AuthScreen.

Thanks @jainkuniya !
Merged this. I am a bit uneasy about this change, though -- it's adding a type, which is good, except that the type doesn't seem to be checked at all. (Try it: replace ApiServerSettings with some random other type, or even change the name of the property serverSettings, and rerun Flow; no error, either in callers nor the callee.) That can be a helpful note -- and I checked that it seems to be right, at least on the caller side -- but it sets us up for confusion in the future, because it may become wrong with a future change and then it'll mislead us when looking at it to understand this code.
So I wouldn't be excited about going through and systematically adding these in more places -- not until we find a way to write the type so it actually gets checked.


Validator on consensus contract should be a key_hash

The validator on the consensus.mligo contract should be represented as a key_hash to match #201 change on the Deku side.
The ligo compiler should be able to help to ensure that all the places were properly fixed. https://ligolang.org/
https://github.com/marigold-dev/deku/blob/main/tezos_interop/consensus.mligo#L4

Closed by #208


Add bitvavo exchange

Can you please add bitvavo exchange?

The exchange is added.
Will be included to the next app version (v2.20).


[Cloud Endpoints] Updating service endpoint to project-id.appspot.com

Cloud Endpoints team wants samples to use project-id.appspot.com instead of echo-api.endpoints.project-id.cloud.goog.  This PR updates both Java 7 and Java 8 samples for Cloud Endpoints backend sample.

@frankyn Ok to merge w/o circle passing, though I'd appreciate if you waited.

Thanks Les!


BREAK: Bump pydantic to v2

A new major version of Pydantic has been recently published, which is already being used by FastApi, but not yet by cachetory.
This new version includes some changes that have a minor impact in cachetory codebase (https://docs.pydantic.dev/2.0/migration/#changes-to-pydanticbasemodel, https://docs.pydantic.dev/2.0/migration/#changes-to-pydanticfield).

Does this update force teams to update fastapi? is there a way to support pydantic v1 and v2 at the same time?

👋 That's a little harsh, as it makes a smooth migration more difficult. Could you try to use from pydantic.v1 import BaseModel first? Or otherwise, try to make it compatible with both v1 and v2 via try … except ImportError?

Agree!
I've loosen the requirement to allow any version <3, so it will install the one that best matches the project requirements. The only thing to pay attention to is to pin in your project Pydantic's version to <2 if needed.
About the code changes, we are still calling BaseModel.parse_obj for both v1 and v2, with the difference that for those using v2 they'll see this message:

The parse_obj method is deprecated; use model_validate instead. Deprecated in Pydantic V2.0 to be removed in V3.0.

Nothing will break though as internally is the same


[test] Using lit incremental mode and rearranging tests.

The incremental mode orders test by the last time modified, instead of
by the path, it also touches the files for failed tests, in order for
them to be prioritized on the next run. Using this mode as the default
improves both the CI and local development experience: CI builds
triggered by the commit, that includes changes to the tests, will run
those tests first; locally, it makes a lot of sense to run previously
failed tests first to make sure they've been fixed.
Since this mode changes the order in which tests get executed, the
'1_stdlib' name no longer has any effect, and can be fixed.
A few most time consuming tests were moved from tests/stdlib to
validation-test/stdlib to speed up the execution of unit test suite
(a.k.a build-script -t).

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - d3254e314ccbbbd0ea4d7a4a4743fcb416184d8d
Test requested by - @moiseev

+1!

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - d3254e314ccbbbd0ea4d7a4a4743fcb416184d8d
Test requested by - @moiseev

Tests failed due to an incorrect symlink in 'validation-test/stdlib'. Fixed now.
@swift-ci Please test.

Can you split the renaming and the rearranging into separate commits, for bookkeeping purposes? This is especially relevant if we continue to cherry-pick things to the swift-3.0-branch.

@jrose-apple Done.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - d3254e314ccbbbd0ea4d7a4a4743fcb416184d8d
Test requested by - @moiseev

Thank you!

@swift-ci Please test and merge

@swift-ci Please test and merge

Thanks @gottesmm. I wonder why mine did not work...


Optimize installation disk size

Description of the new feature / enhancement
I just realized that PowerToys needs 3.1GB of storage. There should be a way to install it without every module requiring its own copies of the same (shared) libraries.
Scenario when this would be used?
It's important to me because I have a small system partition on my work notebook.
Supporting information
No response

Hi, @ArKay74
Thanks for reporting. We are actively working on this. Stay tuned :)

This is also a false positive due to how we're leveraging hard links currently.  The disk footprint is far less than what you're seeing.  https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/disk-usage-footprint.md

Hello PowerToys developers, you really need to think about whether we need such a huge installation size:

Many files can be shared or hard link.
I completely cannot understand why a "toolbox" software that should be very compact has the same weight as PS :(.

.72 we are redoing how we handle files. You are seeing a false positive on disk usage due to the hard links for stuff under .71
please check out the doc I linked to prior


Supplementary unit testing and improve documentation

Supplementary unit testing
Improve documentation
Version 0.1.1

That great, more formal


Migrate exit code

Hi. It seems that migrate always exits with a 0, even if it can't load the database configuration.
$output->writeln('<error>Could not determine database name! Please specify a database name in your config file.</error>');
return;

That's not correct, is it?

:+1:

+1

PR merged.


[BUG] Memory leak

Dear Alls,
After I apply this plugin, the Cookies is store.
However, when i check memory leak via XCode Instruments tool, this tool detected memory leak as below:
100.00% [[NSHTTPCookieStorage sharedHTTPCookieStorage] setCookies:cookies forURL:httpResponse.URL mainDocumentURL:nil];
If you have any suggestion, please let me known.
Thanks

I could not find any issues so far. If anyone is familiar with ObjectiveC, iOS and these tools let me know.


Updates for dbt-utils to dbt-core cross-db macro migration

This pull request was created automatically 🎉
Before merging this PR (refer to Detailed Update Sheet 10/2022 for more information):

[x] Verify dbt_project.yml & integration_tests/dbt_project.yml versions are properly bumped
[x] Spot check for dispatch updates, dbt_utils.macro -> dbt.macro
[x] Verify that .circleci directory has been removed
[x] Verify integration_tests/requirements.txt adapters have been updated to 1.2.0 and dbt-databricks is added
[x] Verify .buildkite directory has been added with the following: hooks/pre-command, scripts/run_models.sh, pipeline.yml
[x] Update packages.yml, will need to bump source package (FT utils should be bumped)
[x] Update .buildkite/scripts/run_models.sh with vars as applicable, if N/A then remove relevant lines from script
[x] Remove databricks block from .buildkite/pipeline.yml if package is incompatible
[x] Update schema names in integration_tests/ci/sample.profiles.yml
[x] Update "spark" strings where applicable
[x] Update CHANGELOG template and remove surrogate keys if not applicable to package
[x] Update README for dbt version badge, install package version range and dependencies for: Fivetran_utils, dbt-utils and source packages
[x] Regenerate docs
[x] Follow Instructions for adding Buildkite
[x] Follow instructions for removing Circleci

Hey @fivetran-sheringuyen,
Any chance to push the upgrade quickly ?
I've got an error when adding:
  - package: fivetran/facebook_ads_creative_history     version: [ ">=0.4.0", "<0.5.0" ]
Version error for package fivetran/fivetran_utils: Could not find a satisfactory version from options: ['=0.4.0', '>=0.3.0', '<0.4.0']

Hi @LouisMonierSpark unfortunately we will not be able to push these changes until dbt Labs releases the dbt-utils v1.0.0 version. Would you be able to share what your packages.yml config is at the moment?
It may be that for the time being you will need to downgrade the fivetran_utils package (if you have it included in your packages.yml) until we are able to releases these migration changes for dbt-utils v1.0.0

@LouisMonierSpark just wanted to share an update that our team is off on a holiday break until the first week of January. You can expect these to be released and live that week!


Unable upload new version of app - Deliver 1.3.0 and Fastlane 1.32.1

I'm using Deliver to create a new version of my app, that already exist in App Store. But alway getting error.
@KrauseFx Please help me soon!
The log:
......
[21:16:55]: Loading './fastlane/metadata/copyright.txt'...
[21:16:55]: Loading './fastlane/metadata/primary_category.txt'...
[21:16:55]: Loading './fastlane/metadata/secondary_category.txt'...
[21:16:55]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[21:16:55]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[21:16:55]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[21:16:55]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[21:16:55]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[21:16:56]: Activating languages da, de-DE, el, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fi, fr-CA, fr-FR, id, it, ja, ko, ms, nl-NL, no, pt-BR, pt-PT, ru, sv, th, tr, vi, zh-Hans, zh-Hant...
[21:16:59]: Variable Dump:
[21:16:59]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios upload_all"}
[21:16:59]: Must be a hash
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | deliver                             | 11          |
+------+-------------------------------------+-------------+
[21:16:59]: fastlane finished with errors
/Library/Ruby/Gems/2.0.0/gems/spaceship-0.11.2/lib/spaceship/tunes/app_version.rb:232:in `update_rating': Must be a hash (RuntimeError)
from /Library/Ruby/Gems/2.0.0/gems/deliver-1.3.0/lib/deliver/upload_metadata.rb:143:in `set_app_rating'
from /Library/Ruby/Gems/2.0.0/gems/deliver-1.3.0/lib/deliver/upload_metadata.rb:54:in `upload'
from /Library/Ruby/Gems/2.0.0/gems/deliver-1.3.0/lib/deliver/runner.rb:52:in `upload_metadata'
from /Library/Ruby/Gems/2.0.0/gems/deliver-1.3.0/lib/deliver/runner.rb:20:in `run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/actions/deliver.rb:18:in `run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:142:in `block (2 levels) in execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/actions/actions_helper.rb:37:in `execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:128:in `block in execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:127:in `chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:127:in `execute_action'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:137:in `method_missing'
from (eval):89:in `block (3 levels) in parse'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane.rb:36:in `call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane.rb:36:in `call'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:51:in `block in execute'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:46:in `chdir'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:46:in `execute'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane_manager.rb:43:in `cruise_lane'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/command_line_handler.rb:31:in `handle'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:35:in `block (2 levels) in run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:136:in `run'
from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:142:in `<top (required)>'
from /usr/bin/fastlane:23:in `load'
from /usr/bin/fastlane:23:in `'

Looking at your stack trace you have an error here:
update_rating': Must be a hash (RuntimeError) from /Library/Ruby/Gems/2.0.0/gems/deliver-1.3.0/lib/deliver/upload_metadata.rb:143:inset_app_rating'

Are you setting update_rating properly? Can you post your Fastfile / Deliverfile?

How can I settings "update_rating"?
====THIS IS MY DELIVERFILE=======
ipa './fastlane/app.ipa'
app_icon './fastlane/appicon/icon.png'
app ENV["kAPP_APPLE_ID"]
copyright "#{Time.now.year} Application"
automatic_release ENV["kAPP_AUTOMATIC_RELEASE"]
app_review_information(
first_name: "Name",
last_name: "Name",
phone_number: "+11111111",
email_address<EMAIL_ADDRESS>demo_user: "",
demo_password: "",
notes: ""
)
app_rating_config_path './fastlane/ratings.json'
price_tier 0
submission_information({
add_id_info_limits_tracking:true,
add_id_info_serves_ads:ENV["kAPP_FURTHER_ADVERTISING_IDENTIFIER"],
add_id_info_tracks_action:false,
add_id_info_tracks_install:false,
add_id_info_uses_idfa:ENV["kAPP_FURTHER_ADVERTISING_IDENTIFIER"],
content_rights_contains_third_party_content:ENV["kAPP_FURTHER_CONTAINS_THIRD_PARTY"],
content_rights_has_rights:ENV["kAPP_FURTHER_HAS_RIGHTS"],
export_compliance_available_on_french_store:false,
export_compliance_contains_proprietary_cryptography:false,
export_compliance_contains_third_party_cryptography:false,
export_compliance_is_exempt:ENV["kAPP_FURTHER_IS_EXEMPT"],
export_compliance_uses_encryption:false,
export_compliance_ccat_file: false,
export_compliance_app_type:false,
export_compliance_encryption_updated:ENV["kAPP_FURTHER_ENCRYPTION_UPDATED"],
export_compliance_compliance_required:false,
export_compliance_platform:false
})
=====AND MY FASTFILE======
fastlane_version "1.6.0"
default_platform :ios
platform :ios do
before_all do
# ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
# cocoapods

# increment_build_number

# ipa # Build your app - more options available

# xctool # run the tests of your app

end
desc "# Runs all the tests"
lane :test do
# snapshot
end
desc "Submit a new Beta Build to Apple TestFlight"
desc "This will also make sure the profile is up to date"
lane :beta do
# snapshot
sigh
deliver(beta: true)
# sh "your_script.sh"
# You can also use other beta testing services here

end
lane :create_app do
produce({
username<EMAIL_ADDRESS>app_identifier: ENV["kAPP_IDENTIFIER"],
app_name: ENV["kAPP_PRODUCE_NAME"],
language: 'English',
app_version: '1.0',
sku: ENV["kAPP_PRODUCE_SKU"]
})
ENV["kAPP_APPLE_ID"]=ENV["PRODUCE_APPLE_ID"]
end
lane :upload_all do
deliver(submit_for_review: false, force: true)
# frameit

end
desc "Uploads metadata only - no ipa file will be uploaded"
desc "You'll get a summary of the collected metadata before it's uploaded"
lane :upload_metadata do
deliver(metadata_only: true, skip_deploy: true, force: true)
end
You can define as many lanes as you want
after_all do |lane|
# This block is called, only if the executed lane was successful
# slack(
#   message: "Successfully deployed new App Update."
# )

end
error do |lane, exception|
# slack(
#   message: exception.message,
#   success: false
# )
end
end
More information about multiple platforms in fastlane:
https://github.com/KrauseFx/fastlane/blob/master/docs/Platforms.md

OK it looks like you are setting the app_rating_config_path:
app_rating_config_path './fastlane/ratings.json'

Does this file exist? And what are the contents of this file?

Yes, this is my ratings.json:
{
  "CARTOON_FANTASY_VIOLENCE": 0,
  "REALISTIC_VIOLENCE": 0,
  "PROLONGED_GRAPHIC_SADISTIC_REALISTIC_VIOLENCE": 0,
  "PROFANITY_CRUDE_HUMOR": 0,
  "MATURE_SUGGESTIVE": 0,
  "HORROR": 0,
  "MEDICAL_TREATMENT_INFO": 0,
  "ALCOHOL_TOBACCO_DRUGS": 0,
  "GAMBLING": 0,
  "SEXUAL_CONTENT_NUDITY": 0,
  "GRAPHIC_SEXUAL_CONTENT_NUDITY": 0,

  "UNRESTRICTED_WEB_ACCESS": 0,
  "GAMBLING_CONTESTS": 0
}

Resovled, Thank @squarefrog

No problem. What was the issue?

Thanks @squarefrog for jumping it! :+1:


Issue #372: Implement zero-padding to a configurable number of decimal places.

What's the status of this PR?

@joshlrogers Hi, thanks for the PR..
I have tried this out using the vanilla-text-mask.  It has some odd behaviour that needs addressing.
First.. if you type in  123.45|, (the pipe | is the cursor) and then delete (backspace) the last two characters I end up with $123.|_0 ...backspace again and I get $1,23|_.00
In the above two cases it should be $123.|00 and $1,2|.00.
Second, similar issue... if you type in 123.45, but this time move the cursor between the decimal point and the 4 (123.|45) and then press backspace to delete the decimal point.. i get $12,3|45.00 which I don't think is correct... I'm not exactly sure what it should be in this case.. either $12|.45, or $12|4.50

any reason why this PR hasn't been merged yet?


When does nuttx have a plan to support stm32H7?

When does nuttx have the plan to support stm32H7?
@dagar @davids5

Sorry, I've seen it


Add bits_per_sample to info

Closes https://github.com/pytorch/audio/issues/1173
This PR adds a bits_per_sample attribute to AudioMetaData as returned by info(), with support for both sox_io and SoundFile. As SoundFile does not expose the bit depth directly, it is inferred from the subtype field as suggested in https://github.com/pytorch/audio/issues/1173.
bits_per_sample is left to 0 for lossy formats or when it cannot be inferred.
CC @mthrok

Regarding the download_third_parties_nix test, it should be fixed on master branch, so rebasing or merging should resolve it.

Regarding the download_third_parties_nix test, it should be fixed on master branch, so rebasing or merging should resolve it.

The failing tests are not related to this PR. Merging this.

The failing tests are not related to this PR. Merging this.


Decoder occasionally skips 2 bytes before length when decoding uncompressed block (Format error: invalid uncompressed block len)

I originally got this error while trying to read a large, incompressible PNG image with the image crate.
fn main() {
    image::open("14.png").unwrap();
}

Image link (3 MB) (MD5:15760e8fe875bbb4273df4381daae041)
Result:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: FormatError("invalid uncompressed block len: LEN: 83d9 NLEN: 3c33")', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

The PNG image in question was encoded using the image crate itself. It can be opened in GIMP without issue, and pngcheck reported no problems with the file:
$ pngcheck -vt 14.png
File: 14.png (3147315 bytes)
  chunk IHDR at offset 0x0000c, length 13
    1024 x 1024 image, 24-bit RGB, non-interlaced
  chunk IDAT at offset 0x00025, length 3147258
    zlib: deflated, 32K window, default compression
  chunk IEND at offset 0x30062b, length 0
No errors detected in 14.png (3 chunks, -0.1% compression).

Inspecting the PNG with a hex editor, I was able to find the byte sequence D9 83 33 3C at offset 0x200029 in the file. It appears that the actual length was 2 bytes before that:
200026: 00     # denotes uncompressed block
200027: 26 7C  # decoder somehow skipped these? (this is actually `len`)
200029: D9 83  # `len`:  0x83D9 (this is actually `nlen`)
20002B: 33 3C  # `nlen`: 0x3C33 (this is actually part of the block)

inflate 0.4.3
image 0.20.1
rustc 1.31.0 (abe02cefd 2018-12-04)

#48 should fix this.


How to move up Toolbar and hide it with navigation bar?

navigationController.followScrollView(table, followers: [tabBarController.tabBar, toolbar])
This will make navigation bar hide, but Toolbar still on the top.
How to hide the Toolbar when scroll up?

I propose adding a new property named downwardFollowers or similar where would try to move those views towards the bottom when navigation bar hides.
Thoughts?

@attheodo
sounds good, more on that, we could probably encapsulate the view in a struct with the direction, something like
enum FollowerDirection { case up, down, left, right }

struct Follower {
  var view: UIView
  var direction: FollowerDirection

  init(view: UIView, direction: FollowerDirection) {
  // ...
}

then:
navigationController.followScrollView(table, followers:
  [Followe(view: topBar, direction: .up),
  [Followe(view: bottomBar, direction: .bottom)]
)

This could be fairly easy to implement and a good starting point if someone wants to contribute.


change track design

QR-Code + short text (slogan + instruction) in the middle of the default track
grey road pieces

ready for review:
Pull request: #151


View 'out of ten' charts in comparative view

Overview
Some questions contain the phrase 'out of ten of your neighbors...'
These questions are formatted as WaffleCharts when viewed as a
single-year chart. However, because each piece of data must be
rendered as a separate waffle chart, this isn't conducive for
comparative view. When viewed with multiple years selected, these
questions are instead displayed as a GroupedBarChart with the maximum
value set to 10.
Connects #137
Demo

Testing Instructions

Select geographies that cover multiple years, select multiple years, and select all of the available 'out of 10' questions. Select several grouped bar chart questions that are not 'out of 10' as well.
The charts should be bar charts. The maximum value for the 'out of 10' charts should be 10. The other bar charts should work as before.
Select the same geographies, a single year, and the 'out of 10' questions.
The charts should be waffle charts.

Thank you for reviewing!


Adding Azure blob and file storage

Hi,
I used your plugin for a while now and had to change my storage to azure.
A while ago I decided to add azure as a new provider in your plugin and used this changes for a while now.
So the code is tested in real life and is hopefully written well enough.
So please check my code, I would be grateful if you could add this to your repository.

@spacedee Sorry, it took very long to integrate :-/
Could you please test the new 2.0-beta-build in #252 (I will attach it today)?


[Rendering] Fixed equality of MaterialSpecularMicroFacetModelFeature

PR Details

Description
The Environment property wasn't checked.
Related Issue

#735
Motivation and Context

Types of changes

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

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Feature Request: Drag and drop Watch variables

I'm getting used to the debugger and it's been really helpful, but it can be difficult to manage at times. I thought giving users the ability to re-order watch items would be nice.

Sometimes I'm watching variables that have similar names but are from different files. It can get a little confusing when there's several watch variables from different locations. I'll put dummy variables between them as dividers to remind me which file they came from.

Being able to do these sorts of things quickly would be awesome. Currently I have to delete and rebuild the entire watch list if I feel the need to re-order or add something in an ordered fashion.

Drag to reorder would be pretty easy. Surprisingly you can't even do that in chrome devtools.
I'm not sure about dividers. Seems very specific to a certain workflow. It would be interesting if the watches that have values, ie don't throw ReferenceError, were sorted to the top, as an alternative to a user-ordered list.

I like the drag to reorder idea, assigning to November to investigate


Ashwin' additions

Codecov Report

Merging #26 (da7d2fd) into master (4a05d59) will decrease coverage by 16.72%.
The diff coverage is 0.00%.

:exclamation: Current head da7d2fd differs from pull request most recent head 2c2c8b4. Consider uploading reports for the commit 2c2c8b4 to get more accurate results

@@             Coverage Diff             @@
##           master      #26       +/-   ##
===========================================
- Coverage   78.54%   61.81%   -16.73%
===========================================
  Files           4        5        +1
  Lines         233      254       +21
===========================================
- Hits          183      157       -26
- Misses         50       97       +47

Impacted Files
Coverage Δ

src/Julia_DT_Notebook.jl
0.00% <0.00%> (ø)

src/chamfer.jl
97.36% <0.00%> (-0.39%)
:arrow_down:

src/squared_euclidean.jl
67.79% <0.00%> (+1.83%)
:arrow_up:

Continue to review full report at Codecov.

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


failOnError is not respected

i have failOnError set to false but my build continues to fail.
looking at the mojo source, i found this:
https://github.com/gleclaire/findbugs-maven-plugin/blob/master/src/main/groovy/org/codehaus/mojo/findbugs/FindBugsMojo.groovy#L1049
which seems to indicate failOnError is always set to true

the unit tests pass.
If you can provide a use case sample we investigate further


Add file mapping detach function

Currently the file mapper is one-way, which is inconvenient if we need to map the workspace to another folder. Add file mapping detach to solve this.

Also added a quick demo for file history tracking, eventual consistency is guaranteed


Add support for extra traces

[x] Adds a extra_traces prop, which is a dcc.Store that users can write a list of traces to.
[x] Adds example to show a contour this way.

I considered using pattern matching, which would make it possible for the application to define multiple stores for additional traces. However, by simply proving a store via a property, we make the simpler cases easier, and the more complex cases can still define multiple stores and then add a callback to aggregate these into the slicer.extra_traces.
Possible alternative names for extra_traces could be e.g. user_traces, `more_traces.

Thanks! The checklist above mentions that you added an example showing a contour but I could not find it, did you maybe forget to add it?

Regarding the name, I like both extra_traces and user_traces (not so much more_traces). Maybe a slight preference for extra_traces ?

[...] did you maybe forget to add it?

Yes I did :)

[...] Maybe a slight preference for extra_traces ?

Let's just stick with extra_traces then.

Just a color-related nitpicking comment, but it looks good to go!


docs: fix formatting

I think this should be a regular list.

On a related note: I noticed that lists are often indented in the docs, i.e.
Here is a list:

 * Item1
 * Item2
 * Item3

This will render to

…

. I've replicated this style in my PR in case that's intentional, but I suspect you want plain
…
 here, which you get by not indenting the list.
Likewise capitalization, list bullets (* vs -) and spacing differs between and within docs.

I don't think there's a particular reason to indent the unordered lists. I've added a commit to fix the indentation everywhere (which was inconsistent even within 040_backup.rst).
I'd like to keep the capitalization of Inode if it's used at the start of a sentence. The inode manpage does so too.


install-qt-action pollutes environment on Windows with Python-3.10

install-qt-action or one of its dependencies broke by github action build today. It seems to have brought Python 3.10 into the environment, which overrode the Python 3.9 I was using in my build. I had placed actions/setup-python@v2 before install-qt-action. I've fixed it by swapping the order of the two actions. (It broke my build because the packages I used were not available for Python 3.10).
Is there any way to may install-qt-action not pollute the environment with Python?

Give it setup-python: false

FYI, there is a problem of the dependent components of aqtinstall (the core function of this action) in Python 3.10. It has been reported in https://github.com/miurahr/aqtinstall/issues/423 . Please check it.

Thanks very much for your help. It seems to work fine with setup-python: false. Python 3.10 was working for me, but I had setup the compiler environment, so maybe this fixed it. Anyway, now I have everything with Python 3.9 until my dependencies all work.


Wrong License

This project is licenced under CC BY. However, the original orbit template says:

You do not have the rights to resell, sublicense or redistribute (even for free) the template on its own or as a separate attachment from any of your work.

That is incompatible with the CC BY licence because I won't be able to redistribute the work nor use it in any commercial project.

At the date this copy was made (last commit was created May 15, 2017), the license was CC BY. The corresponding commit is https://github.com/xriley/Orbit-Theme/blob/355f83f7a2859999ac4a22d523eae9113c4f27d6/README.md

Thank you for clarifying!


Restrict access to browse-able API with session to super user only.

Currently any logged in user can access the API urls via a session login from TolaActivity or TolaTrack.  We need to limit session access to these api endpoints via the browser to only superusers.

Done and working in staging and Demo


Dividing controls among hands

Is it currently possible to have separate control profiles for each ps move controller? I couldn't find any documentation on this subject if this feature exists at all. This would be useful for games which require the use of both the touchpad and buttons as each set could be bound to its own controller instead of having to choose or do awkward key combinations.

There is currently no way to do this, though it is a feature that has been requested for a while. I've wanted to do this as an in-SteamVR UI that you could use to configure buttons. I just haven't had the time to dedicate to this.

@HipsterSloth can't this do it: https://github.com/cboulay/PSMoveService/commit/ecc68528ceb10826bf9c8a4e123b9435c934cbca? Sorry if I'm missing something obvious.
@TheSmg it's documented at the end of this subsection: https://github.com/cboulay/PSMoveService/wiki/Steam-VR-Setup#virtual-touchpad. Here's an example:
   "psmove_touchpad_directions_0" : {
      "circle" : "touchpad_right",
      "cross" : "touchpad_left",
      "triangle" : "touchpad_up",
      "square" : "touchpad_down"
   },
   "psmove_touchpad_directions_1" : {
      "circle" : "touchpad_down-right",
      "cross" : "touchpad_down-left",
      "square" : "touchpad_up-left",
      "triangle" : "touchpad_up-right"
   },

Thank you, dont know how I missed that. Ill try it when I get the chance

@zelmon64 Oh! You are absolutely right. I totally forgot you added that functionality.

As part of the latest release and adding support for the SteamVR Input API, each controller now has it's own config file in %appdata%/PSMoveSteamVRBridge
https://github.com/HipsterSloth/PSMoveSteamVRBridge/releases/tag/v1.6.0


Add a troubleshooting page

What would you like to be added:
We can start documenting common user errors. For example:

Workload is not admitted

Check CQ status, verify flavors

Job starts but doesn't have any node selectors

Check whether the template has any requests, otherwise they won't get assigned a flavor. Or use quota per pod.

Why is this needed:
I think one of this scenarios was reported in #1407.
/kind documentation

@tenzen-y @kerthcet have you seen any common user errors?

If Workload is not admitted, check the workload status.
Also sometimes, I need to check the feature gates like kubernetes does kubectl get --raw /metrics | grep kubernetes_feature_enabled, maybe we should do the same in kueue. This is not an error.
The integrated component's version is also something we should consider, I used to meet our users complaining about kueue not working with kubeflow, he already installed kubeflow1.7, however, the training-operator is 1.6, but we need 1.7 specifically. Maybe we can take this as a special case.

Q1. The desired flavor isn't assigned to the Job.
A2. The flavor in clusterQueue is evaluated from top to bottom and assigned to jobs. The highest-priority flavor need to be put on the top.
Q2. In spite of a job being admitted, pods from a job are pending.
A2. Kueue will consider only quotas defined in clusterQueues, not consider actual cluster usage. Please check if the cluster has free capacity.
Q3. In spite of enabled sequential admission, all pods can not be started, and the part of pods are started.
A3. Kueue isn't pod's scheduler. Kueue doesn't guarantee that all pods are started at the same time.

/remove-kind feature

/assign

A state diagram of Workload conditions would be useful. Annecdotically, I just got a question from a developer about what is QuotaReserved.

Another common user error: installing the integration (for example jobset or kuberay) after installing kueue.
Kueue will not monitor these jobs.

/remove-lifecycle stale

What is missing here before we can close? We have the base version of the guide. I believe we can improve it in follow up issues focused on specific features. WDYT @tenzen-y ?

/close


Fix #406 by nubbing module list generated from source files

Fix #406 by nubbing module list generated from source files
Inserting a nub here is strictly improving the state of affairs, since cabal chokes on a module list with duplicates.
This patch might also fix #353.

The travis-ci job BUILD=tinc CABALVER=2.2 GHCVER=8.4.3 apparently has problems
https://travis-ci.com/github/sol/hpack/jobs/431630342
GHC 8.4.3 crashes when building cabal:
Building library for Cabal-<IP_ADDRESS>..
[ 55 of 242] Compiling Distribution.CabalSpecVersion ( Distribution/CabalSpecVersion.hs, dist/dist-sandbox-6fba3b3/build/Distribution/CabalSpecVersion.o )

ghc: panic! (the 'impossible' happened)

  (GHC version 8.4.3 for x86_64-unknown-linux):

	Prelude.!!: index too large

Maybe try GHC 8.4.4 instead.
tinc: callProcess: cabal "install" "--bindir=$prefix/bin/$pkgid" "Cabal-<IP_ADDRESS>" "base-compat-0.11.2" ...
... "http-client-tls-<IP_ADDRESS>" (exit 1): failed

@andreasabel I just released hpack-0.34.3 to Hackage (fyi).


If you modify the "editor.lineHeight" setting, multiline tooltips will overlap

VSCode Version: 1,6,0
OS Version: win10x64

Steps to Reproduce:

Open a new file, set as language Javascript, and type this:

var a = [1,
2]

Here is how the tooltip lines are displayed (after clicking the balloon icon) while the  editor.lineHeight setting has its default value (0) :

Now, in File|Preferences|User Settings add this entry editor.lineHeight": 15 ( * )
Here is how the tooltip lines are displayed:

i.e. they now overlap.

( \* ) I use that setting combined with`"editor.fontSize": 13` but this doesn't affect the issue.

How did you get that Fix this semi problem, Fix all auto-fixable problems thing? Which extension gives you that?
@jrieken Is this the lightbulb, which is implemented as a native menu?

Closing as obsolete because since 1.7.0 we use the native context menu for code actions

@joaomoreno commented on Oct 31, 2016, 10:52 AM GMT+2:

How did you get that Fix this semi problem, Fix all auto-fixable problems thing? Which extension gives you that?
@jrieken Is this the lightbulb, which is implemented as a native menu?
vscode-eslint.

I'm glad it's fixed!


Rename parameters for user friendly

Constructor with (x, y, width, height) parameters confused, because rectangle-based ellipse supposed, but it's created from two radiuses and middle point.

Thank you @eXponenta for the PR!


Investigate three failing test files when run in isolation

Running rake test_deps reveals:
Dependency Issues: test/html/test_document.rb
Dependency Issues: test/html/test_document_fragment.rb
Dependency Issues: test/test_reader.rb

Investigate and fix.

Uh, never mind, this went away when I upgraded all the dev dependencies.


Render a histogram for numerical vectors

Right now, this uses color to encode the number of items in a bin:

This is not a good choice, since the color doesn't match with a color used in the table (not even dark vs light matches).
Use a plain histogram instead. If you use color to encode the data in the table, use the same color in the histogram bars. Otherwise make the histogram monochrome.

Looks nice when we have large dataset

Throw in a light frame for the bars just to counter-act white on white please.

That looks good. Question: are you encoding the frequency of the bin with color (looks like it) or the position along the range? I think it should be the latter.

This is the question I was about to the post here. Currently, I encode color with the bin entries. The range you mean the min-max value of the data ?

yes. The color coding here should match what you show in the data. I'd expect this to be a gradient then.

The data in bins are unevenly distributed in histogram lets say we have three bins as here:

First bin: 6 entries  with values [7,8,6,8,7,8]
Second bin: 4 entries with values [12,10,12,12]
Third bin: 2 entries with values [33,25]
How can we make gradient based on this situation?
The another way we can achieve the gradient is as below when we provide each bin for each value with the same width, and the frequency should correspond the height of the width.

Does it make sense  now ?

Yes, looks good now. The color should match the color to the color shown in the table. Also use the red that Alex suggested.
Btw: You can make the handles (black triangles) a bit smaller and center the text horizontally below the triangle (without overlap).

I am updating here #35 also in this issue.

Thanks alot @thinkh for this brushing help.:)

Looks good now. Only one small thing: Could you update the numbers below the frame already on drag and not after mouse up?

This is already merged with the master.


Greater control over Access Logging

what

More clearly distinguish between S3 Access Logging and Cloudfront Access Logging

Deprecate:

access_log_bucket_name
logging_enabled
log_include_cookies
log_prefix

Replace with variables prefixed with s3_access_log and cloudfront_access_log to indicate which access logs they apply to

Provide independent feature flags for S3 Access Logging and Cloudfront Access Logging
Provide ability to configure independent logging object prefixes for S3 Access Logging and Cloudfront Access Logging
Provide ability to direct Cloudfront Access Logging to an existing S3 bucket
Fix issues causing module to fail when enabled was set to false
Add tests

why

This module (potentially) creates an S3 Bucket to use as the Cloudfront Origin, and a Cloudfront Distribution. Both S3 Buckets and Cloudfront Distributions provide the ability to generate Access Logs and save them to an S3 bucket. However, the variables in the module referred only to "log" or "logging", which made it non-obvious whether they applied to S3 Access Logs or Cloudfront Access Logs. The new naming largely removes the confusion, while the old variables are still supported for backward compatibility.
Explicit flags enabling and disabling logging (rather than implicit based on providing a destination bucket name) avoids Terraform problems with plan depending on results of apply when S3 Bucket is created in the same root module that calls this module.
The user was stuck with the prefix this module generated for S3 Access Logs, which may not have been what they wanted.
This module always created a new S3 bucket for Cloudfront Access Logging when Cloudfront Access Logging was enabled, which did not allow users to store logs for multiple distributions in the same bucket.
All Cloud Posse modules should plan and apply without error and without creating resources when enabled is set to false
Ensure module behaves properly when enabled is set to false. Verify that the same S3 Bucket can be supplied for both sets of access logs

/test all


Not fetching translations for modded deaths

I have a server running with the origins mod, and when someone gets a non-vanilla death (such as drowning from air), BlockBot only sends the translation key.

Origins need to bundle their translations in the bundled datapack


Do we keep GOLD add_date and mod_date?

At present, I pull in the add_date and mod_date from the GOLD data tables. These tables pertain to when the record was added to the database, not when the sample was collected.
Example biosample add_date: 28-JUL-14 <IP_ADDRESS>000000 AM.
Do we keep these or remove these?
cc @cmungall @dwinston @jbeezley @jeffbaumes @turbomam @dehays

I do not think they need to be displayed in the UI - particulary in their current context-less form.  2) The question of whether to include them at all depends on how much provenance we wish to retain, part of /nmdc-metadata#318 I think.

I could imagine that for each datum we'd want to have at least the source (GOLD in this case) and perhaps its add/update in that source.

@dehays great point! Yes, the was generated by slot can be used to point back to original record in the biosample table. This would be an ETL enhancement.

Adding @tbkreddy to the conversation.

We can also add information to the model that this information should not be displayed.

Reviving this issue, and suggest to add information that this should not be displayed in the data portal. @wdduncan, sounds like this is an easy fix? Thanks.

@wdduncan were you hoping I would help with this in some way? I don't know where the GOLD input lives and am not sure which repo contains the relevant code.

FYI @turbomam the relevant code for gold translation is in the nmdc-runtime/metadata-translation/  directory of the microbiomedata/nmdc-runtime repo.

But I think @wdduncan indicated that some annotation corresponding to "applications generally should not display this field" may be added to the LinkML model in this repo, unless I'm misunderstanding "add information to the model". So the metadata translation code needn't be touched. And then, going forward, the data portal can consult the model annotation for what not to display, rather than this being hard-coded in nmdc-server code.

Thanks @dwinston . I'll wait to hear whether @wdduncan was thinking I should take any of this on.

Currently I do translate the add_date and mod_date fields from gold. I also convert the dates into ISO 8601 format. Can Kitware simply exclude them from the portal interface if we don't want them displayed?

@aclum is this still useful? do we need or use these fields? I think we do, for workflows.. but I think it's done?

mod_date is potentially useful for keeping track of which record should change if NMDC and GOLD records are get out of sync. I'd say if this isn't a problem we leave these fields as they are so just close this ticket as complete.

Yes, I agree. Mod dates can help us in identifying updated records.
On Wed, Jan 24, 2024 at 11:46 AM aclum @.***> wrote:

mod_date is potentially useful for keeping track of which record should
change if NMDC and GOLD records are get out of sync. I'd say if this isn't
a problem we leave these fields as they are so just close this ticket as
complete.
—
Reply to this email directly, view it on GitHub
https://github.com/microbiomedata/nmdc-schema/issues/8#issuecomment-1908807270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANQT6CDTEO6PK5WTFXMQO6DYQFQJNAVCNFSM42RPQJY2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJQHA4DANZSG4YA
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Extension] Autoupgrade buyer gets stuck

The autoupgrade buyer will often fail to purchase the next highlighted upgrade despite available funds.
Manually purchasing the highlighted ability causes autoupgrade buyer to kick in again.

I've observed similar behavior, but I think this may be a known issue.


Instructions unclear, couldn't generate project files using the .bat script

Sigh... What can i say.

Looks inside
C++

Skill issue?

Fixed with commit #11


Pool tasks for sp_tasks::spawn and add execution limits

Currently the way we implement the sp_tasks::spawn runtime API (which is roughly equivalent to a std::thread::spawn, just called from within the runtime and without any shared memory between the caller and the callee) has a few problems from what I can see:

it is unbound**: you could exhaust system resources by spawning enough tasks
it uses spawn instead of spawn_blocking yet it is blocking (it uses a blocking channel, and calling into the runtime is also effectively a blocking operation)
you can call it recursively without any limit

It can deadlock the whole async loop when called enough times in parallel, or called enough times recursively.
Its docs also say that it's dangerous when used incorrectly.
(** - although due to it using spawn you'll probably exhaust all of the tokio worker threads and deadlock the whole process first)
What we should do to fix this:

Soft-limit the number of tasks which can be concurrently executed; add the rest into a queue. There's no point in supporting an unbound number of tasks executing at the same time since calling into the runtime is an inherently blocking operation, and you don't have an infinite number of CPU cores to run them all anyway. We should pick a preset number of supported parallel tasks and execute only at most that many simultaneously. (This also reduces the risk of triggering network partitions if this is used in a place which can affect consensus.)
Hard-limit the number of levels the tasks can be spawned recursively, or (preferably) even just disallow it completely; otherwise you'll still risk a deadlock

It would also be nice to add a hard-limit for the number of tasks which can be queued at the same time, but unfortunately that could be a source of non-determinism depending on how fast the already queued tasks are executed; we could however add a potential hard-limit to the total number of tasks.
Fortunately from what I can see no one currently really uses this API? (At least it isn't used in polkadot, if my grepping is correct; not sure about other chains though.)

Fwiw, all this code is currently only a test implementation that should not really have hit master. As you already found out it is not used anywhere and it is also disabled for parachains. I would say we keep this issue open until we have decided on how to continue with this feature.


Flaky test S3FileSystemTest.invalidAccessKey

Bug description
Flaky test S3FileSystemTest.invalidAccessKey
This was found by a PR CI test, https://app.circleci.com/pipelines/github/facebookincubator/velox/42841/workflows/c156d45b-7b47-4acc-b5f8-77dc893387b2/jobs/296842
Relevant logs
287: E0119 17:41:19.555821 96311 Exceptions.h:68] Line: ../../velox/connectors/hive/storage_adapters/s3fs/S3FileSystem.cpp:93, Function:initialize, Expression:  Failed to get metadata for S3 object due to: 'Network connection'. Path:'s3://dummy/foo.txt', SDK Error Type:99, HTTP Status Code:-1, S3 Service:'Unknown', Message:'curlCode: 7, Couldn't connect to server', RequestID:'', Source: RUNTIME, ErrorCode: INVALID_STATE
287: ../../velox/connectors/hive/storage_adapters/s3fs/tests/S3FileSystemTest.cpp:134: Failure
287: Value of: e.message().find("Failed to get metadata for S3 object due to: 'Access denied'. Path:'s3://dummy/foo.txt', SDK Error Type:15, HTTP Status Code:403, S3 Service:'MinIO', Message:'No response body.'") != std::string::npos
287:   Actual: false
287: Expected: true
287: Expected error message to contain 'Failed to get metadata for S3 object due to: 'Access denied'. Path:'s3://dummy/foo.txt', SDK Error Type:15, HTTP Status Code:403, S3 Service:'MinIO', Message:'No response body.'', but received 'Failed to get metadata for S3 object due to: 'Network connection'. Path:'s3://dummy/foo.txt', SDK Error Type:99, HTTP Status Code:-1, S3 Service:'Unknown', Message:'curlCode: 7, Couldn't connect to server', RequestID:'''.
287: I0119 17:41:19.557137 96311 TempDirectoryPath.cpp:31] TempDirectoryPath:: removing all files from/tmp/velox_test_S1xysT
287: [  FAILED  ] S3FileSystemTest.invalidAccessKey (27566 ms)

cc @mbasmanova @majetideepak

@majetideepak Deepak, would you help take a look?


ModLoader + HowManyItems crashes on world start-up

I installed the official NFC versions of ModLoader and HowManyItems, ModLoader as a jar mod and HowManyItems in the mods folder. As soon as I opened my world, the game crashed with this report: https://www.toptal.com/developers/hastebin/dasaruyena.http

Hello dear @robbieradiant!
Are you sure you have installed the patched version of both ModLoader and HowManyItems? If not, there is a link to the NFC's website with patched versions of mods (v3.4.1):
https://newfrontiercraft.net/thread/165/nfc-v3-4-mods-addons

This issue tracker is for bugs in the vanilla game, issues with mods should be talked about in the Discord channel instead.


atom freeze when open compress file

Hi
atom 1.14.2x64. ubuntu 16.04.
disable all installed modules. open compress js file:
compress.txt
in attache txt file, change to js
editor not responding and freeze.

+1

Should be fixed in Atom 1.15.0-beta3 and later.


Capture console log

Thanks - appreciate the PR. Will take a look over the next few days!

Hi peter,
I don't know if you remember me, I'm Melvin from Sedicii's Tenerife office.
I've forked your fuge project and adding a frontend to manage it without
needing to use the console. It is not yet finished and didn't mean to push
to your repo. Sorry for this.
If you like this approach, i'm working along with a colleague, and will
notice when we have a working version.
Thank you in advance.
Melvin Gutiérrez
El jue., 7 mar. 2019 a las 10:46, Peter Elger<EMAIL_ADDRESS>escribió:

Thanks - appreciate the PR. Will take a look over the next few days!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apparatus/fuge/pull/180#issuecomment-470478027, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEjbRnOj0f6OLlGIaVevZyXDti-0A79qks5vUO4HgaJpZM4bbOvE
.


fix/illegal-move

Fixes #3 where clicking on opponents piece while in human vs. human allows for illegal move and causes game "suicide".
Check is put in to only select pieces of the same color as the current turn.

Legit, looks good! Thanks for fixing this!


update to go 1.5.4

Signed-off-by: Victor Vieux<EMAIL_ADDRESS>

ping @docker/core-swarm-maintainers

LGTM

LGTM
eagerly waiting for all test to be green !!

LGTM

@chanwit your wish has been granted :)


Testing Data Tagging explanation

[ ] added a .md5 checksum file generated with make_check_sums.py Not Applicable

This PR adds an explanation on how to best use development branches with xclim, whether they are for local (pytest or tox) or CI (GitHub Actions). This also explains how to properly tag the commit when making changes so that no warnings occur for developers and users wishing to test xclim.

@tlvu This is ready for merge. I'll be making a new tag with the merge of this PR.


Add permissions for arturas to release phabricator-jenkins plugin

Description
Adding permissions for arturas (@artms) to release phabricator-jenkins plugin @kageiit can you confirm?
When adding new uploaders (this includes newly created permissions files)

[X] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[X] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[X] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[X] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

You checked "All users have logged into Artifactory at least once", but
User name not known to Artifactory: arturas in the build...

I swear I logged into artifactory yesterday:

Maybe a race condition or caching  issue. retriggered CI


Add mention about significant whitespace

While learning Elm I found it confusing that the documentation A) said indenting function body is best-practice and B) didn't mention anything about significant whitespace. Clearly it is not best-practice, but mandatory.
> over9000 powerLevel = \
| if powerLevel > 9000 then "It's over 9000!!!" else "meh"
-- SYNTAX PROBLEM -------------------------------------------- repl-temp-000.elm

I ran into something unexpected when parsing your code!

3│   over9000 powerLevel =
                         ^
I am looking for one of the following things:

    end of input
    whitespace

You have misunderstood that paragraph. The best practice it is talking about is this:
function x y =
   body

vs. this:
function x y = body

And no, that is not mandatory. It is only best practice (according to Evan).

Okay, thank you for clarification. What is the cause of the error in the example? When I add indentation to the second line compiler error is gone.

I didn't say that
function x y =
body

would be legal as well. It isn't. But the sentence in the docs you changed was not about this. And the change you did cuts out some meaning that was intended to be there, namely about the difference between the two code snippets I showed in my previous comment.


python37Packages.howdoi: 2.0.8 -> 2.0.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python37Packages.howdoi is: "Instant coding answers via the command line"
meta.homepage for python37Packages.howdoi is: "https://pypi.python.org/pypi/howdoi"
meta.changelog for python37Packages.howdoi is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

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

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

found 2.0.10 with grep in /nix/store/hbmd06w25p8dc1xvk2r9lly3sqglsq7h-python3.7-howdoi-2.0.10

directory tree listing: https://gist.github.com/50571695e7ede04c4b4a7cee23b8dd73

du listing: https://gist.github.com/564832e2db7eb2dbfd251922798bc111

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

12 total rebuild path(s)

3 package rebuild(s)

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

First fifty rebuilds by attrpath
python37Packages.howdoi
python38Packages.howdoi
python39Packages.howdoi

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hbmd06w25p8dc1xvk2r9lly3sqglsq7h-python3.7-howdoi-2.0.10
ls -la /nix/store/hbmd06w25p8dc1xvk2r9lly3sqglsq7h-python3.7-howdoi-2.0.10/bin

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

3 packages built:

python37Packages.howdoi
python38Packages.howdoi
python39Packages.howdoi

Maintainer pings
cc @costrouc for testing.

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

3 packages built:

python37Packages.howdoi
python38Packages.howdoi
python39Packages.howdoi


[Alert] [HTTP Plugin] Lose HTTP port

close #14340

Codecov Report

Merging #14341 (8bf3631) into dev (66e09dc) will decrease coverage by 0.17%.
The diff coverage is 21.42%.

:exclamation: Current head 8bf3631 differs from pull request most recent head 8b6e0f6. Consider uploading reports for the commit 8b6e0f6 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14341      +/-   ##
============================================
- Coverage     38.65%   38.49%   -0.17%
- Complexity     4534     4557      +23
============================================
  Files          1236     1239       +3
  Lines         43185    43503     +318
  Branches       4779     4784       +5
============================================
+ Hits          16695    16746      +51
- Misses        24651    24907     +256
- Partials       1839     1850      +11

Impacted Files
Coverage Δ

...dolphinscheduler/plugin/alert/http/HttpSender.java
47.76% <0.00%> (ø)

...low/instance/pause/pause/PauseExecuteFunction.java
0.00% <0.00%> (ø)

...or/workflow/instance/stop/StopExecuteFunction.java
0.00% <0.00%> (ø)

...api/service/impl/TaskDefinitionLogServiceImpl.java
7.69% <0.00%> (ø)

...uler/api/service/impl/TaskInstanceServiceImpl.java
51.79% <0.00%> (ø)

...e/dolphinscheduler/common/constants/Constants.java
75.00% <ø> (ø)

...ler/server/master/event/TaskDelayEventHandler.java
0.00% <0.00%> (ø)

.../server/master/event/TaskDispatchEventHandler.java
0.00% <0.00%> (ø)

...er/server/master/event/TaskResultEventHandler.java
0.00% <0.00%> (ø)

...r/server/master/event/TaskRunningEventHandler.java
0.00% <0.00%> (ø)

... and 42 more

... and 31 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

PTAL @caishunfeng @SbloodyS @EricGao888

Could we also add a test case for it? @qingwli

approval to run test


Not cached with postman

Hi all,
My cache system is working on browser but not in postman
@app.get("/", include_in_schema=False) @cache(expire=600) async def app_home(request: Request):     return {'Domain : %s' % generate_random(20)}
Do you have an idea ?

Postman sends no-cache header by default which is not necessarily set on your browser, that is why the response is cached on your browser and not on the postman. You can remove this header in the settings.

To add to @Sajadrahimi's comment. Another way you can disable Cache-Control: no-cache set by postman is by simply sending a dummy header eg:
Cache-Control: <some invalid value>


Change AncestryChanged to Destroying

Resolves #62

I'm changing the base of this PR to merge it into another Trove change. Thanks for the PR!


9.9.0.beta.2 release does not work, no sub-commands found

Something seems to be wrong with the released 9.9.0.beta.2 package. If I do
sudo gem install licensee -v 9.9.0.beta.2

then I get
$ licensee help
Licensee commands:
  licensee help [COMMAND]  # Describe available commands or one specific command

Options:
  [--remote], [--no-remote]  # Assume PATH is a GitHub owner/repo path

whereas when running from source I get
$ bundle exec bin/licensee help
Licensee commands:
  licensee detect [PATH]        # Detect the license of the given project
  licensee diff [PATH]          # Compare the given license text to a known license
  licensee help [COMMAND]       # Describe available commands or one specific command
  licensee license-path [PATH]  # Returns the path to the given project's license file
  licensee version              # Return the Licensee version

Options:
  [--remote], [--no-remote]  # Assume PATH is a GitHub owner/repo path

@sschuberth sorry for the delay.  I believe the fix is in https://github.com/benbalter/licensee/commit/b6396e5fd8a3ff1b8b174453e63f8c35f26515a5. I'll cut another beta.

$ licensee version
9.9.0.beta.3

🎉


Links to the grant contracts in the applications index

Add Grant column and populate it using heuristic script

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


mix format failed for file: .iex.exs

mix format is broken when the .iex.exs file is present in the project.
❯ mix format
mix format failed for file: .iex.exs
** (MatchError) no match of right hand side value: {#Sourceror.Zipper<
   #root
   {:alias, [trailing_comments: [], leading_comments: [], end_of_expression: [newlines: 1, line: 1, column: 20], line: 1, column: 1], [{:__aliases__, [trailing_comments: [], leading_comments: [], last: [line: 1, column: 11], line: 1, column: 7], [:App, :PullStats]}]}
 >, [{:alias, [trailing_comments: [], leading_comments: [], end_of_expression: [newlines: 1, line: 1, column: 20], line: 1, column: 1], [{:__aliases__, [trailing_comments: [], leading_comments: [], last: [line: 1, column: 11], line: 1, column: 7], [:App, :PullStats]}]}]}
    (recode 0.7.2) lib/recode/task/alias_order.ex:46: Recode.Task.AliasOrder.do_run/3
    (elixir 1.17.1) lib/enum.ex:2531: Enum."-reduce/3-lists^foldl/2-0-"/3
    (recode 0.7.2) lib/recode/runner/impl.ex:55: Recode.Runner.Impl.run/3
    (elixir 1.17.1) lib/enum.ex:2531: Enum."-reduce/3-lists^foldl/2-0-"/3
    (mix 1.17.1) lib/mix/tasks/format.ex:668: Mix.Tasks.Format.format_file/2
    (elixir 1.17.1) lib/task/supervised.ex:101: Task.Supervised.invoke_mfa/2
    (elixir 1.17.1) lib/task/supervised.ex:36: Task.Supervised.reply/4

Thanks for reporting. I will have a look. Can you post your .iex.exs?

.iex.exs looks like this:
alias App.PullStats

I've bypassed this issue by updating the .formatter.exs:

I have made a new release. This should fix the problem.

Wow, that was fast. Thank you so much!


Update Angular 2 to latest official release beta.9

Update Angular 2 to latest release and accompanying dependencies.
For systemjs demo had to switch back to using non-minified libraries for now as the .min ones are broken.

Thanks @kukicadnan!


Help Maintaining?

Hi! I think you're very busy with the other repos and your job, so I'd like to help you here a bit and volunteer to (co-)maintain this project if you're fine with this.

I'm fine with this, but I'm afraid there is not that much to do there! I will add you to the contributor list.


Is Archetype is actively maintained?

I've tried to check the possibility to verify my contract in ChatGTP and this is what I've got:
"It is important to note that Archetype is no longer actively maintained, and LIGO has become the recommended language for Tezos smart contract development. Consider exploring LIGO or SmartPy for building FA2 contracts and marketplaces in Tezos."

Hi Michal, strange enough indeed. This is fake news from ChatGPT. Archetype is still maintained!

Was it from plain ChatGPT from openai or from an chatbot built on top of it ?

pure ChatGPT.

Now repeat it like a 1000 times and we can say that this issue has been solved? :D

which version is it ? 3.5 or 4 ?

3.5

Ask about example of NFT market place in Archetype or something like that. IMHO he knows that Archietype is active but in more complex scenarios he is returning wrong answer.

ok thanks for the feedback.

Closing because, there is no solution for that issue :D


Update gradle files & replace deprecated object of Exoplayer

Update gradle files & replace deprecated object of Exoplayer.

Thank you for the contribution!
Taking a quick look at this, it seems as though I might have made the updates in this PR already? Is there anything that stands out to you that I've missed?

Thank you!

I see we have created some same changes, I just created the pull request before your commits :)


Fix skdman link

The current link takes me to https://github.com/sparrowwallet/sparrow/blob/master/docs/sdkman.io with an "404 not found error" message.

Thanks!


[latest] Add overload SimpleAuthOutput.authenticateSuccessfully with boolean parameter to clear auth passwords after authentication

Card: https://hivemq.kanbanize.com/ctrl_board/4/cards/27287/details/
Related card: https://hivemq.kanbanize.com/ctrl_board/4/cards/26231/details/

@cla-bot check


app.message() not being triggered on my AWS api gateway + lambda set up

(Filling out the following details about bugs will help us solve your issue sooner.)
Reproducible in:
aws api gateway and lambda
The slack_bolt version
https://github.com/slackapi/bolt-python/releases/tag/v1.2.0b3
Python runtime version
(Paste the output of python --version)
python 3.8
OS info
AWS Lambda
Steps to reproduce:
Having issues with the app.message(':wave:') basic functionality behind an api gateway and lambda. I have a current working slack bot using bolt-python and the rest of the functionality works. Things such as app.event('app_mention'), app.command('/mycommand'), and app.action() all work smoothly. Now, i'm trying to implement a listen for a certain message "form_request" to trigger my bolt-python app but nothing happens. The slack client does not send any event to my api gateway endpoint. The bot has proper permissions such as channel.read and channel.history to perform the right actions. Scratching my head with this one. Does my bolt-python always have to be running and listening? and since my api-gateway + lambda implementation is waiting to be invoked, does the slack client not handle the invoking but instead I need to be fetching?

my code implementation

My results

My api gateway traffic (no triggers recently during the trigger)

My permissions

Expected result:
expected to have a request come in, and say processing result
(Tell what you expected to happen)
Actual result:
(Tell what actually happened with logs, screenshots)
nothing happens..... no http request, no logs during the time frame, nothing to trigger my api gateway + lambda
Requirements

[SOLVED] thanks to slack teams help, they pointed me in the right direction. The solution was subscribing to the message.channel event in the bot permissions.

Hey @epuerta9 👋🏻 I'm glad to hear that you've solved your problem! Thanks sharing your solution so that others can find the answer!
Your issue had an immense amount of detail 🙇🏻 Really appreciate that! In the end, it looks like you had everything set up, including the scopes, but missed subscribing to the event.

Is there an example of the subscription method somewhere?

@emcniece You can't programmatically subscribe to the message.channels event and instead you'll need to manually subscribe using the App Settings. It will also add a new scope channels.history that will require the app to be reinstalled to your workspace (or user's workspaces).
Here is the documentation for message.channels event that is mentioned above.
You'd subscribe to this event in your App Settings ⟶ Event Subscriptions:


Works with special characters in YAML values

I've made a fix so that special values in YAML are also included in the results (before only word-like characters were included).
I've also cleaned up the code in YamlParser and renamed the file to make it work with the changes you made yesterday evening.

I also changed all the / in a subtag to - when it's exported so that it doesn't throw the error FileNotFoundError: [Errno 2] No such file or directory: 'Exported_tag1/tag2/tag3.zip'.

There's one thing I'm not sure about:
Each YAML value with multiple words/characters seperated by spaces currently gets split at the spaces and then joined with one space.
When linking to an alias in Obsidian, if there are multiple spaces, the spaces will be in the alias but because Markdown strips it all down to one space, in Preview only one space is visible. This also applies to the Metadata viewer in Preview.

This would only be relevant if people have multiple spaces on purpose in a YAML value. I've implemented it in a way to strip it down to one space because I assume two or more spaces would only erroneously be entered.


Update README file

Description
I noticed that the README file wasn't following any pattern for the writing. It seemed like the gem was made of little pieces of code joined together. In order to keep a default, I standardized some of the content of the README.md file. I still feel like there's more to do in this file, but I'm not sure what would be the best in these places (e.g.: in the examples for a specific object, should we keep a default of searching for an specific id, or looking for the first item? Or both?).

Pull Request Test Coverage Report for Build 131

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 128:
0.0%

Covered Lines:
891

Relevant Lines:
891

💛  - Coveralls


ocamlPackages.astring: 0.8.3 -> 0.8.4

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ocaml4.10.0-astring/versions.
meta.description for ocamlPackages.astring is: "Alternative String module for OCaml"
meta.homepage for ocamlPackages.astring is: "https://erratique.ch/software/astring"
meta.changelog for ocamlPackages.astring is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

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

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

found 0.8.4 with grep in /nix/store/r48gcz2j6kh6hxz7cy7drgrb7jlvfp3w-ocaml4.10.0-astring-0.8.4

directory tree listing: https://gist.github.com/9da0653ca813d4237b83a659f52857f8

du listing: https://gist.github.com/df77a7db29a3a1a3efa39431e23469e7

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

29 total rebuild path(s)

8 package rebuild(s)

8 x86_64-linux rebuild(s)
7 i686-linux rebuild(s)
7 x86_64-darwin rebuild(s)
7 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dune-release
jackline
libbap
ocamlformat
python27Packages.bap
python37Packages.bap
python38Packages.bap
stog

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r48gcz2j6kh6hxz7cy7drgrb7jlvfp3w-ocaml4.10.0-astring-0.8.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r48gcz2j6kh6hxz7cy7drgrb7jlvfp3w-ocaml4.10.0-astring-0.8.4
ls -la /nix/store/r48gcz2j6kh6hxz7cy7drgrb7jlvfp3w-ocaml4.10.0-astring-0.8.4/bin

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

2 packages failed to build:

ocamlPackages.irmin-http
ocamlPackages.irmin-unix

112 packages built:

dune-release
jackline
libbap
ocamlPackages.alcotest
ocamlPackages.alcotest-lwt
ocamlPackages.angstrom
ocamlPackages.angstrom-async
ocamlPackages.angstrom-lwt-unix
ocamlPackages.angstrom-unix
ocamlPackages.asn1-combinators
ocamlPackages.astring
ocamlPackages.base64
ocamlPackages.bigarray-overlap
ocamlPackages.bigstringaf
ocamlPackages.biocaml
ocamlPackages.bistro
ocamlPackages.bos
ocamlPackages.checkseum
ocamlPackages.cohttp
ocamlPackages.cohttp-lwt
ocamlPackages.cohttp-lwt-unix
ocamlPackages.conduit
ocamlPackages.conduit-lwt
ocamlPackages.conduit-lwt-unix
ocamlPackages.containers
ocamlPackages.cow
ocamlPackages.crowbar
ocamlPackages.cstruct-sexp
ocamlPackages.curly
ocamlPackages.decompress
ocamlPackages.digestif
ocamlPackages.dispatch
ocamlPackages.dns
ocamlPackages.dns-client
ocamlPackages.domain-name
ocamlPackages.duff
ocamlPackages.duration
ocamlPackages.eliom
ocamlPackages.encore
ocamlPackages.faraday
ocamlPackages.farfadet
ocamlPackages.fiat-p256
ocamlPackages.fpath
ocamlPackages.functoria
ocamlPackages.functoria-runtime
ocamlPackages.git
ocamlPackages.git-http
ocamlPackages.git-unix
ocamlPackages.gmap
ocamlPackages.graphql
ocamlPackages.graphql-cohttp
ocamlPackages.graphql-lwt
ocamlPackages.graphql_parser
ocamlPackages.hacl_x25519
ocamlPackages.hkdf
ocamlPackages.httpaf
ocamlPackages.imagelib
ocamlPackages.imagelib-unix
ocamlPackages.ipaddr
ocamlPackages.ipaddr-cstruct
ocamlPackages.ipaddr-sexp
ocamlPackages.irmin
ocamlPackages.irmin-fs
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mem
ocamlPackages.irmin-pack
ocamlPackages.irmin-test
ocamlPackages.irmin-watcher
ocamlPackages.irmin_1
ocamlPackages.iter
ocamlPackages.ke
ocamlPackages.mdx
ocamlPackages.metrics
ocamlPackages.metrics-lwt
ocamlPackages.metrics-unix
ocamlPackages.mirage-crypto-pk
ocamlPackages.mirage-crypto-rng
ocamlPackages.mirage-crypto-rng-mirage
ocamlPackages.mirage-flow-unix
ocamlPackages.mirage-protocols
ocamlPackages.mirage-runtime
ocamlPackages.mirage-stack
ocamlPackages.mirage-time-unix
ocamlPackages.mirage-unix
ocamlPackages.nocrypto
ocamlPackages.notty
ocamlPackages.ocb-stubblr
ocamlPackages.ocp-ocamlres
ocamlPackages.ocsigen-start
ocamlPackages.ocsigen-toolkit
ocamlPackages.ocsigen_server
ocamlPackages.odoc
ocamlPackages.opium
ocamlPackages.opium_kernel
ocamlPackages.otr
ocamlPackages.owl
ocamlPackages.phylogenetics
ocamlPackages.piqi
ocamlPackages.ppx_blob
ocamlPackages.rpclib
ocamlPackages.tls
ocamlPackages.tsort
ocamlPackages.tuntap
ocamlPackages.webmachine
ocamlPackages.x509
ocamlPackages.yaml
ocamlformat
python27Packages.bap
python37Packages.bap
python38Packages.bap
stog

Maintainer pings
cc @sternenseemann for testing.

@vbgl not sure how we should go about updating astring, I had a quick look and some packages that depend on it are available on lower OCaml versions than 4.05, for example:

irmin 1.4
domain-name
functoria
ocp-ocamlres

might be others which have no mimimum bound set.
Not sure if it is safe to break those for OCaml < 4.05 or we should hold up on updating?

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

1 package marked as broken and skipped:

python27Packages.bap

7 packages built:

dune-release
jackline
libbap
ocamlformat
python37Packages.bap
python38Packages.bap
stog

This is required for OCaml 4.12 support.

See #105688

This PR is SPAM


DIR not available?

I just upgraded from rc2 to rc5 and new things started to fail. In rc2, the (Nashorn) extension variable DIR worked (I didn't use compatibility mode). In rc5, it doesn't. Is there a replacement?

We had two flags: Nashorn extensions (enabled by default) and Nashorn compatibility mode (disabled by default). This was confusing. So, the Nashorn extensions flag was removed and the corresponding functionality (including __DIR__ Nashorn extension) was moved behind the Nashorn compatibility mode. That's why __DIR__ become disabled by default.
I am not aware of any replacement available outside Nashorn compatibility mode. Is there a reason why you can't/don't want to use --nashorn-compat flag/option?

No particular reason - it felt appropriate to attempt to use Graal "cleanly". I'll try the compatibility mode!

Nashorn compatibility mode works, closing.


Ok implement better default option handling for the CORS case.  Previous hack would report a 200 status even for nonexistent paths.  This fix is much better and honors the applicaiton.properties cors config for OPTIONS requests.

Ok implement better default option handling for the CORS case.  Previous hack would report a 200 status even for nonexistent paths.  This fix is much better and honors the applicaiton.properties cors config for OPTIONS requests.

Closing, I like the simplicity of PR #113 better

Codecov Report

Merging #114 into master will decrease coverage by -0.94%.
The diff coverage is 30%.

@@             Coverage Diff              @@
##             master     #114      +/-   ##
============================================
- Coverage     46.63%   45.69%   -0.94%
  Complexity       82       82
============================================
  Files            63       63
  Lines           549      558       +9
  Branches         48       50       +2
============================================
- Hits            256      255       -1
- Misses          269      280      +11
+ Partials         24       23       -1

Impacted Files
Coverage Δ
Complexity Δ

...ipaas/rest/v1/controller/SwaggerConfiguration.java
0% <ø> (ø)
0 <ø> (ø)
:x:

...a/com/redhat/ipaas/runtime/CorsOptionsFeature.java
38.09% <31.57%> (-31.14%)
0 <ø> (ø)

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 bb152a7...edaf53b. Read the comment docs.

Actually don't think #113 fully works.  Reopening this one for now.

#113 does work ;)


[spk] Introspection dashboard header "Spektate" takes up a lot of real estate

As a: user
I want: to maximize the screen space to view deployments and filters
So that: I can view more information on the screen in one go
Describe the solution you'd like:
Right now, the Spektate black bar on the top is taking a lot of space, especially on smaller devices.

[ ] Discuss with designer to come up with a solution that preserves the branding somewhere on the page without taking too much room
[ ] Implement the solution

Acceptance Criteria:
Describe alternatives you've considered:
Additional context:
Does this require updates to documentation?: no

We can decrease the height of the top bar.
Before:

After:

@edaena that may be a good solution for now. @gemorris thoughts?


Feature Req: Option to modify commit message

Is your feature request related to a problem? Please describe.
Not really a problem. I would like to change the default commit message of the action (Automated change by https://github.com/cicirello/user-statistician) to a custom one.
Describe the solution you'd like
It would be nice to have an additional input to the action, e.g. commit_message, which could be provided by the user.
Describe alternatives you've considered
n.a.
Additional context
none
By the way: thanks for the wonderful action.

@afuetterer Thanks for the suggestion. This was very easy to implement, and I had the time to do it. There is now a new input to customize the commit message, which you can now do with: commit-message: Your custom commit message. It is now available in v1.23.0 or via the major release tag v1.

Excellent, thank you very much for the quick fix.
I will try the new version and input later today.

It works as expected, thanks again!

@afuetterer You're welcome


CMDEP-8

Add credit, customerinfo, provisioning and wallet api operations to the rate_db.sql db script.

test this please

test this please


Proposed actions for updated CG Core information product types

After a review of the usage of output types in several CGIAR open access repositories¹ we have come up with a list of proposed actions for CG Core:

Add Abstract
Add Blog
Add Blog Post
Add Brief

Add alternative label Factsheet

Add Case Study

Add synonym Outcome Case Study

Remove Data file
Remove Database
Add Data Paper
Rename Dataset As A Collection Of Data to Dataset
Remove directive document
Remove Financial Report
Remove Geospatial raster file
Remove Geospatial vector file
Add Guidelines as an alternative label for Manual
Rename Journal (full) to Journal Issue
Remove Legal Document
Add Magazine
Remove Magazine Article
Add User Manual as a synonym for Manual
Remove Newspaper
Remove Personal Communication
Remove Post
Rename Research Report to Report
Remove Standard
Add Template
Remove Technical Report
Add Questionnaire
Add Tool
Add Training Material
Remove Video Recording

To decide with @marieALaporte how to proceed. A few next steps:

Update the RDF schema
Update the schema guidelines
Update the controlled vocabulary

//cc @ayabowork @monday2016 @valentina-dc @MargaritaRamirez

¹ CGSpace, MEL, MARLO, and CG Core

currently, the list of product types is not part of the RDF. Should we add the list to the cgcore RDF file or have it published as it own thing?

@marieALaporte oh! I didn't realize that. So we just publish the product types as a separate controlled vocabulary. Something like a plaintext CSV with types and definitions that can be machine read, then we produce some HTML or whatever other things from that.


SQLite Empty Aggregate returns "I'm a stub, not a real handler for aggregate"

FerretDB version
1.9
Backend
SQLite
Environment

OS: Linux
Deployment: ghcr.io/ferretdb/ferretdb:1.9.0
Deployment details: Docker on Ubuntu

What did you do?
Query with empty aggregate
What did you expect to see?
All elements from the collection
What did you see instead?
"I'm a stub, not a real handler for aggregate"

It will be available in v1.10.0.

Duplicate of #3148


v10 - README UrlTracker:Backoffice:Notifications:Enable description typo

Related issue
There is a typo on line 63 of the README in the description of the UrlTracker:Backoffice:Notifications:Enable app setting which states the value should be true to disable
Proposed changes
Fix the typo by changing the value from true to false
See also #156

@Infocaster/developers

Hi @chrden ! Thanks a lot, I hadn't noticed that! Your contribution is much appreciated!!