re-compilation of git repo download...

Problem

a dependency on a git repo is resulting in its repeated recompilation and that of
some of its own dependencies (though not recursively).
Steps

ocaml="*" is switched to ocaml= {git="git://github ...."} which was done
to take advantage of a quick fix before publication to the crates registry.

Possible Solution(s)

Notes
Output of cargo version:

You can try running Cargo with the CARGO_LOG=cargo::core::compiler::fingerprint=trace environment variable which should display the reason Cargo thinks something needs to be rebuilt. It may provide a clue what's going on.

here's the output:
dev@raspberrypi:~/experiments/ocaml-rust-starter$
CARGO_LOG=cargo::core::compiler::fingerprint=trace cargo build
--target-dir=_build/default/target/
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml2rust-3233e6ec320c45ec/lib-ocaml2rust
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint] new
local fingerprints deps
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint] old
local fingerprints deps
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint] new
local fingerprints deps
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint] stale:
missing "/home/dev/.cargo/git/checkouts/ocaml-rs-da52f9c65e24ce66/40c8624/sys/ocamlopt"
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
fingerprint error for ocaml2rust v0.1.0
(/home/dev/experiments/ocaml-rust-starter)/Build/Target { ..:
lib_target("ocaml2rust", ["staticlib", "dylib"],
"/home/dev/experiments/ocaml-rust-starter/src/lib.rs", Edition2018) }
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
err: current filesystem status shows we're outdated
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-ac6d5da7244ae0b7/lib-ocaml-ac6d5da7244ae0b7
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
fingerprint error for ocaml v0.12.0
(git://github.com/zshipko/ocaml-rs#40c86247)/Build/Target { ..:
lib_target("ocaml", ["lib"],
"/home/dev/.cargo/git/checkouts/ocaml-rs-da52f9c65e24ce66/40c8624/src/lib.rs",
Edition2018) }
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
err: current filesystem status shows we're outdated
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-derive-211fa08717e35cab/lib-ocaml_derive-211fa08717e35cab
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/proc-macro2-8cbec4c8ffe35c50/lib-proc_macro2-8cbec4c8ffe35c50
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/proc-macro2-c261c29f1d5c2acc/run-build-script-build_script_build-c261c29f1d5c2acc
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/proc-macro2-832c187024763536/build-script-build_script_build-832c187024763536
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/unicode-xid-946a2714430f1d30/lib-unicode_xid-946a2714430f1d30
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/quote-03bd8ed9b65a7ad7/lib-quote-03bd8ed9b65a7ad7
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/syn-e31d63e372a675cf/lib-syn-e31d63e372a675cf
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/syn-5f8b30aabeb9e45d/run-build-script-build_script_build-5f8b30aabeb9e45d
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/syn-d2f03ae6218364a7/build-script-build_script_build-d2f03ae6218364a7
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/synstructure-2f10559ceab00947/lib-synstructure-2f10559ceab00947
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-sys-3d8f179b282c1d27/lib-ocaml_sys-3d8f179b282c1d27
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
fingerprint error for ocaml-sys v0.12.0
(git://github.com/zshipko/ocaml-rs#40c86247)/Build/Target { ..:
lib_target("ocaml-sys", ["lib"],
"/home/dev/.cargo/git/checkouts/ocaml-rs-da52f9c65e24ce66/40c8624/sys/src/lib.rs",
Edition2018) }
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
err: current filesystem status shows we're outdated
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/cty-95dd7124dde8449b/lib-cty-95dd7124dde8449b
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-sys-d5b78c7bca8b48b3/run-build-script-build_script_build-d5b78c7bca8b48b3
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
fingerprint error for ocaml-sys v0.12.0
(git://github.com/zshipko/ocaml-rs#40c86247)/RunCustomBuild/Target {
..: custom_build_target("build-script-build",
"/home/dev/.cargo/git/checkouts/ocaml-rs-da52f9c65e24ce66/40c8624/sys/build.rs",
Edition2018) }
[2020-05-06T13:45:00Z INFO  cargo::core::compiler::fingerprint]
err: current filesystem status shows we're outdated
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint]
fingerprint at:
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-sys-8cf61dcdf5f11556/build-script-build_script_build-8cf61dcdf5f11556
   Compiling ocaml-sys v0.12.0 (git://github.com/zshipko/ocaml-rs#40c86247)
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint] new
local fingerprints deps
[2020-05-06T13:45:00Z DEBUG cargo::core::compiler::fingerprint] write
fingerprint (b80c7e1f6c701374) :
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-sys-d5b78c7bca8b48b3/run-build-script-build_script_build-d5b78c7bca8b48b3
   Compiling ocaml v0.12.0 (git://github.com/zshipko/ocaml-rs#40c86247)
[2020-05-06T13:45:02Z DEBUG cargo::core::compiler::fingerprint] write
fingerprint (371bbafae1b528b6) :
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-sys-3d8f179b282c1d27/lib-ocaml_sys-3d8f179b282c1d27
[2020-05-06T13:45:13Z DEBUG cargo::core::compiler::fingerprint] write
fingerprint (288325c04691658e) :
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml-ac6d5da7244ae0b7/lib-ocaml-ac6d5da7244ae0b7
   Compiling ocaml2rust v0.1.0 (/home/dev/experiments/ocaml-rust-starter)
[2020-05-06T13:45:16Z DEBUG cargo::core::compiler::fingerprint] write
fingerprint (3395f29ea89d46f8) :
/home/dev/experiments/ocaml-rust-starter/_build/default/target/debug/.fingerprint/ocaml2rust-3233e6ec320c45ec/lib-ocaml2rust
    Finished dev [unoptimized + debuginfo] target(s) in 16.38s

On 06/05/2020, Eric Huss<EMAIL_ADDRESS>wrote:

You can try running Cargo with the
CARGO_LOG=cargo::core::compiler::fingerprint=trace environment variable
which should display the reason Cargo thinks something needs to be rebuilt.
It may provide a clue what's going on.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/rust-lang/cargo/issues/8209#issuecomment-624396503

stale: missing "/home/dev/.cargo/git/checkouts/ocaml-rs-da52f9c65e24ce66/40c8624/sys/ocamlopt"

This is the reason. The build script tells Cargo that it should re-run if that file changes. By default, "ocamlopt" is a package-relative path.  But that file doesn't exist in the repo. Missing files are always treated as "changed", so it re-runs every time.  I don't understand how that code is supposed to work, or what OCAMLOPT means, but it looks like you need to set it to something.

the package creator was very responsive and has now fixed the problem.
thanks for clarifying the problem!


Admin UI no longer works

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
No response
Region
No response
Amplify Console feature
No response
Describe the bug
Trying to open Admin UI from the Amplify Console and it throws this error -> "An error occurred while opening Admin UI: ResourceNotFoundException - An error occurred while processing your request: ResourceNotFoundException: Amplify feature flag file (cli.json) not found."
This was not the case over the last days and without changing anything on the backend I just get this error now!
Expected behavior
Open the Admin UI  as usual
Reproduction steps
On the amplify console click on Open admin UI
Build Settings
No response
Additional information
No response

Hi  :wave:, thanks for raising. I'm going to transfer to the AdminUI repo to get some more eyes on it.


Chrome bug？ nuxt bug?

OS: Win 10 latest;
Chrome: 60.0.3112.113 64bit;
template: nuxt/koa;
Sorry, My, English...
When the transparency is switched, the page flashes unexpectedly.
I'll upload screenshots later.
.page-enter-active,
.page-leave-active {
    transition: opacity 1s
}

.page-enter,
.page-leave-active {
    opacity: 0
}


Capybara/FeatureMethods: False positive in FactoryGirls factory.

This file creates a false positive when running Rubocop.
The autocorrect also will change the word feature for describe.
# spec/factories/things.rb

FactoryGirl.define do
  factory :thing do
    name 'my_name'
    feature 'my_feature'
  end
end

Rubocop version: 0.5.0
Rubocop-rspec version: 1.17.1

This is already fixed in master, see #469
I will prepare a release soon

Thanks!

@Darhazer @bquorning I don't think this is resolved. I'm running version 1.24.0 and I'm still seeing the issue.
Here's my factory:
FactoryGirl.define do
  factory :company do
    name { Faker::Company.unique.name }

    # ...

    trait :with_background do
      background { Faker::Lorem.sentence }
    end
  end
end

running rubocop, I get:
spec/factories/companies.rb:19:7: C: Capybara/FeatureMethods: Use before instead of background.
      background { Faker::Lorem.sentence }
      ^^^^^^^^^^


Is 'export as namespace' something new ?

The template module.d.ts uses a 'export as namespace' command that is flagged as an error by VsCode.
Is this something new in TypeScript 2.0 and vsCode just hasn't caught up?

It's apparently been added with 2.0 (it's on the 2.0 section of the What's New page.
Handbook reference.


Can't configure keyboard on launch

Sorry if this is a noob question, but I've searched and haven't found the answer. I Downloaded and installed via the retropie binary.
Launching brings up the configuration screen. It detects my wireless USB keyboard fine and lets  me assign the various keys. But at the end I can't select 'ok'. The only input that does anything is 'f4' which just quits - therefore I'm stuck.
Any idea how to resolve this?

Pressing whatever button you set up as "A" doesn't work?

Pressing whatever button you set up as "A" doesn't work?

I'd suggest improving this UX a bit. It's not immediately clear that the button that the user has configured as "A" is the new "select this option" button. This results in frustration. Folks are used to the enter key just working. Once past this step, the UI includes visual hints (A = Select, Start = Menu, etc) which help a lot. However, this legend doesn't appear in the Configuration screen. Consider allowing the Enter key just for this one part of the workflow of clicking on "OK", or providing a visual hint.

I agree, the UI/UX should be improved by letting the user pass the keyboard/input configuration with Enter or hint that the "A" key should be pressed.

This is an issue for X-Arcade users too because you can't easily enable Xarcade2Jstick without doing some command line stuff: https://support.xgaming.com/solution/articles/5000554993-how-to-use-x-arcade-with-raspberry-pi
It would be great if keyboard/X-Arcade users had a way to bypass the gamepad setup entirely so they could at least set up that.


Client request -- redirect request in case of failures

not default leader (while coming up):

tries redirecting to new leader after docker pause but leader times out the request.

https://github.com/SCPD-Project/raft-kv-store/issues/96

@varks for the crash, hard to tell as it was during random testing and so just a temp fix to continue with testing. Will have to come back to this again to understand why it occurred.
https://github.com/SCPD-Project/raft-kv-store/issues/95

Discussed over slack before merging.


ci: investigate issues and fix weekly CI

Investigate and try to fix the multiples issues we have on the weekly CI.

SELinux tests are failing because OpenSSH package has been removed from the base image.

The main issues have fixed, can be closed.


File versioning closes #95

Coverage remained the same at 100.0% when pulling b4dd076048d14afedf55866c4134d3ce5af28daf on file-versioning-#95 into 2fc375b6d8d0e7f46c0f86260ea04ef7e3f80d5d on develop.


[BUG] Wrong name and avatar when switching user

Your Rocket.Chat.Android version: 1.0.20-DEBUG also tested on 1.0.18
Mobile device model and OS version: Galaxy A3 - Android 6.0.1
When I log in with user A, logout, then log in again with user B, I have user A name and avatar displayed in the menu.
Minimize the app, closing it in the background or even reboot the device doesn't change anything. I have to uninstall and reinstall the app to get the correct name and avatar.
If I do the reverse, first user B then user A, the correct name and avatar are displayed. If I then switch again for user B, I get the wrong user displayed again. In short, user A is always displayed if it has been logged once.
Of course, user A has a smaller ID than user B in the database. User A is also admin, user B is not.

Hum ... pulled the changes, and it seems to work as intended ... :p


Label-studio will not start in previously working environment

Describe the bug
Label-studio has been installed and in a working state. Then 'out of nowhere' it will not start.
To Reproduce
Steps to reproduce the behavior:

python label_studio/manage.py runserver

Expected behavior
starts and runs as expected
Environment (please complete the following information):

OS: Mac OSX Monterey 12.3.1 M1
Label Studio Version 1.4.1post1

Additional context
Label-studio will not start from previously working setup

is properly set up and running
stop server, then will not start anymore
no code changes have been made

python label_studio/manage.py runserver
...
Performing system checks...
...
Exception in thread django-main-thread:
...
...
...
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named 'data_manager.actions.'

Issue:
data_manager/actions/__init__.py tries to import python modules on start
if a non python file appears in the path, it triggers the module not found exception (in my case .next.py.swp)
Attaching PR
after PR applied:
python label_studio/manage.py runserver
...
...
Performing system checks...

No module named 'data_manager.actions.__pycache_'
No module named 'data_manager.actions.tag'
System check identified no issues (1 silenced).
...
...
Django version 3.1.14, using settings 'core.settings.label_studio'
Starting development server at http://<IP_ADDRESS>:8080/
Quit the server with CONTROL-C.

Describe the bug Label-studio has been installed and in a working state. Then 'out of nowhere' it will not start.
To Reproduce Steps to reproduce the behavior:

python label_studio/manage.py runserver

Expected behavior starts and runs as expected
Environment (please complete the following information):

OS: Mac OSX Monterey 12.3.1 M1
Label Studio Version 1.4.1post1

Additional context Label-studio will not start from previously working setup

is properly set up and running
stop server, then will not start anymore
no code changes have been made

python label_studio/manage.py runserver
...
Performing system checks...
...
Exception in thread django-main-thread:
...
...
...
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named 'data_manager.actions.'

Issue: data_manager/actions/__init__.py tries to import python modules on start if a non python file appears in the path, it triggers the module not found exception (in my case .next.py.swp)
Attaching PR
after PR applied:
python label_studio/manage.py runserver
...
...
Performing system checks...

No module named 'data_manager.actions.__pycache_'
No module named 'data_manager.actions.tag'
System check identified no issues (1 silenced).
...
...
Django version 3.1.14, using settings 'core.settings.label_studio'
Starting development server at http://<IP_ADDRESS>:8080/
Quit the server with CONTROL-C.

I also tried the docker version, and verified the docker-compose within pSQL, tables ready, but the docker or runserver version used sqlite, maybe the table not initialized.

I think that will be the same for Mac OS


Hide empty component box when user doesn't have write permissions

Purpose
Very simple fix to hide empty component box when user does not have write permissions.
https://github.com/CenterForOpenScience/osf.io/issues/2892
Side Effects
Is this feature desired?

Looking good! I noticed that the component box still shows up on registrations if the user does not have write permissions -- I think it should be removed from registrations as well for consistency. But just to make sure I will ask in #2892.

Fixed!

Thanks! :tada:
@sloria, I think this is good to go! :tada:


Record metrics

TODO (when other parts ready):

[x] add default pushgateway address
[x] use the methods in code

recheck


Move Replay Tool to json stable for better diffs of snapshot json

TestData: https://github.com/microsoft/FluidFrameworkTestData/pull/39

Thanks for signoff @tylerbutler if you get a chance could you also sign off on the test data change that needs to go in with this: https://github.com/microsoft/FluidFrameworkTestData/pull/39
it's just a regen with the json stable

@anthony-murphy Done!


Exception: RangeError (index): Invalid value: Valid value range is empty: 0

Trying to integrate this awesome widget into my map. Problem occuring when calling getRouteBetweenCoordinates Not sure why I'm getting this error, only difference from example is that I'm getting dynamic location data from user. Any help would be appreciated!
Positioned(
                top: 30,
                left: MediaQuery.of(context).size.width * 0.05,
                child: SearchMapPlaceWidget(
                  icon: Icons.location_on,
                  iconColor: Colors.green,
                  clearIcon: Icons.cancel,
                  placeholder: 'Pick your Destination',
                  apiKey: apiKEY,
                  location: LatLng(-37.763356, 144.958447),
                  radius: 10000,
                  onSelected: (place) async {
                    final geolocation = await place.geolocation;

                    PolylinePoints polylineGetter = PolylinePoints();
                    List<PointLatLng> result =
                        await polylineGetter.getRouteBetweenCoordinates(
                      apiKEY,
                      _curloc.latitude,
                      _curloc.longitude,
                      geolocation.coordinates.latitude,
                      geolocation.coordinates.longitude,
                    );
                    print("results: $result");

                    List<LatLng> polylineCoordinates = [];

                    for (var point in result) {
                      polylineCoordinates
                          .add(LatLng(point.latitude, point.longitude));
                    }

                    // Adding marker to the selected location using a custom icon.
                    final destination = Marker(
                      markerId: MarkerId('user-destination'),
                      icon: goodBrewIcon,
                      position: geolocation.coordinates,
                    );

                    final GoogleMapController controller =
                        await _mapController.future;
                    setState(() {
                      _selectedPlace = place;
                      _polylinePoints = polylineCoordinates;
                      _markers.add(destination);
                    });
                  },
                ),
              ),

Fixed! Didnt have directions API enabled. Make sure to check your APIs in google cloud

This isn't a feature of this package itself. That's why it isn't explained in the documentation.


Add a note telling how to specify compiler' paths

This adds a clarification which should help people struggling with problems
like the one described in bug #174.

Argh, you're right, I have submitted it to the right repo (https://github.com/JuliaParallel/MPI.jl/pull/224), thanks!


Argument parsing doesn't accept parameter settings before SCRIPT_NAME

Despite the usage info, setting -p before SCRIPT_NAME doesn't work. It would be great if usage documentation was harmonized with actual behavior.
vadimkantorov@5CD8223LBY:~/convasr/scripts$ spotty run -p TAG=master train
usage: spotty run [-h] [-d] [-c CONFIG] [-s SESSION_NAME] [-S] [-l] [-r]
                  [-p [PARAMETER=VALUE [PARAMETER=VALUE ...]]]
                  [INSTANCE_NAME] SCRIPT_NAME
spotty run: error: the following arguments are required: SCRIPT_NAME

vadimkantorov@5CD8223LBY:~/convasr/scripts$ spotty run train -p TAG=master # works

Thanks for pointing out. It's an argparse bug, but following this StackOverflow question, I think the best option is to use the -p flag before each parameter. I'll add this fix with the next release.

Fix released.


v0.0.15

Notable changes:

Use GetThreadTimes() on Windows for CLOCK_THREAD_CPUTIME_ID.
Increase the precision of the process and thread clocks on Windows.

Review anyone? Maybe @phated?

uvwasi version bump PR to Node: https://github.com/nodejs/node/pull/46253


Update version constraints and fix CI Workflow

The exact same code is working fine on my fork! What is going on with the cache key.... :-/

Would have fixed itself after 24 hours
https://github.com/actions/cache/issues/485#issuecomment-744145040


Implement darts

(I apologize for putting this here, but I have no idea how to edit a draft pull request on GitHub. Feel free to point me in the right direction.)
My solution follows:
# exercises/practice/darts/.meta/solutions/Darts.rakumod

unit class Darts;

has Rat() ($.x, $.y);

method score {
    given sqrt( $.x² + $.y² ) {
        when 0  ..  1 { 10 }
        when 1 ^..  5 {  5 }
        when 5 ^.. 10 {  1 }
        default       {  0 }
    }
}

@exercism/reviewers New exercise implementation.


Fix dead link in System.Threading.Tasks.Extensions package readme

Fixes https://github.com/dotnet/maintenance-packages/issues/175

Do we think this is a good enough reason to enable IsPackable again for this assembly?


now both hare and tortoise can update state

Motivation
Closes #1805
Changes
added a unified method in mesh to update the state updateStateWithLayer
Now inputs can be received via 2 code paths, the first is ValidateLayer which runs tortoise validation and then update the state
Note: this may result in different states received when running a node and receiving inputs from hare and syncing a node, since potentially, if assumptions are broken , tortoise may contain more blocks than first agreed by hare protocol for a certain layer @barakshani , please re affirm this
Test Plan
add UT to test receiving inputs from both tortoise and hare,
test state received when syncing from tortoise vs state received from hare

bors try

bors try

bors try

Yes, if the assumptions are broken then Tortoise and Hare may not agree (this is true in general). Indeed, when miners only run the tortoise (e.g. a syncing miner) then they may have a different state than miners that builds their state on top of the Hare.

bors try

bors try

bors try

bors try

bors try

bors try

bors try

bors try

bors try

bors try

bors merge

bors merge


More doc comments, split with_exit() method for exit into two methods

Codecov Report

Merging #1012 into master will increase coverage by <.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #1012      +/-   ##
==========================================
+ Coverage   64.65%   64.65%   +<.01%
==========================================
  Files          96       96
  Lines       16872    16870       -2
  Branches     3770     3768       -2
==========================================
- Hits        10908    10907       -1
  Misses       3408     3408
+ Partials     2556     2555       -1

Impacted Files
Coverage Δ

vm/src/obj/objtype.rs
72.69% <ø> (ø)
:arrow_up:

vm/src/pyobject.rs
78.81% <ø> (ø)
:arrow_up:

vm/src/bytecode.rs
58.73% <ø> (ø)
:arrow_up:

vm/src/obj/objbool.rs
79.8% <ø> (ø)
:arrow_up:

vm/src/frame.rs
69% <66.66%> (+0.04%)
: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 b6edd19...3b5cc1a. Read the comment docs.


Chinese translation

Provide Chinese translation (100%).
Also, fix a trivial error in layout activity_start.

Thanks for helping!


Fix deprecation warnings for UE 5.2

Change for this has been applied with some other fixes to bring us up to 5.4 compatible - we will just live with the breaking change.


GC drops all the series from the head-block every 2 hours

Bug Report
What did you do?
Normal Prometheus operation with ~1000000 series in the head block
What did you expect to see?
Smooth operation with all the data available ~99.99% of time.
Some percentage of time-series being dropped from the head block on every GC execution but not all of them.
What did you see instead? Under which circumstances?
It seems that every 2 hours all the series are dropped from the head block and then restored in ~10 minutes.
This event coincides with the GC execution.
Time-series data from time to time becomes unavailable during this "drop-restore" period.
Relevant metrics:

And it happens every 2 hours:

Environment

System information:

Linux 4.9.91-40.57.amzn1.x86_64 x86_64

Prometheus version:

prometheus, version 2.2.1 (branch: HEAD, revision: bc6058c81272a8d938c05e75607371284236aadc)
  build user:       root@149e5b3f0829
  build date:       20180314-14:15:45
  go version:       go1.10

Prometheus configuration file:

global:
  scrape_interval: 30s
  scrape_timeout: 10s
  evaluation_interval: 30s
  external_labels:
    account: aws_account_name
    monitor: prometheus-stack
    region: eu-west-1
scrape_configs:
- job_name: node_exporter
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-116:9100
  relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: ^(.*)$
    target_label: tier
    replacement: p4
    action: replace
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p4
    action: replace
- job_name: prometheus-server
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-116:9090
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p4
    action: replace
- job_name: federate_lts
  honor_labels: true
  params:
    match[]:
    - '{job=~"[a-z].*",job!="federate_lts"}'
  scrape_interval: 1h
  scrape_timeout: 2m
  metrics_path: /federate
  scheme: http
  static_configs:
  - targets:
    - internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090

Logs:

level=info ts=2018-04-26T03:00:00.789789541Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1524700800000 maxt=1524708000000
level=info ts=2018-04-26T03:00:20.711380725Z caller=head.go:348 component=tsdb msg="head GC completed" duration=2.95190116s
level=info ts=2018-04-26T03:00:22.715362637Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=2.003904086s
level=info ts=2018-04-26T03:00:23.670799123Z caller=compact.go:393 component=tsdb msg="compact blocks" count=3 mint=1524679200000 maxt=1524700800000
level=warn ts=2018-04-26T03:07:03.171395946Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=11585
level=warn ts=2018-04-26T04:06:50.777899371Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=26652
level=info ts=2018-04-26T05:00:00.789822667Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1524708000000 maxt=1524715200000
level=info ts=2018-04-26T05:00:20.636595412Z caller=head.go:348 component=tsdb msg="head GC completed" duration=2.961173699s
level=info ts=2018-04-26T05:00:22.712209338Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=2.07554931s
level=warn ts=2018-04-26T05:07:02.716418894Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=14158
level=warn ts=2018-04-26T06:06:50.703605369Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=21808
level=info ts=2018-04-26T07:00:00.789336883Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1524715200000 maxt=1524722400000
level=info ts=2018-04-26T07:00:17.381170201Z caller=head.go:348 component=tsdb msg="head GC completed" duration=2.120526312s
level=info ts=2018-04-26T07:00:19.36616827Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=1.984937139s
level=warn ts=2018-04-26T07:07:02.628056348Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=10883
level=warn ts=2018-04-26T08:06:50.339291254Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=40776
level=info ts=2018-04-26T09:00:00.79663534Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1524722400000 maxt=1524729600000
level=info ts=2018-04-26T09:00:17.869411821Z caller=head.go:348 component=tsdb msg="head GC completed" duration=2.191874292s
level=info ts=2018-04-26T09:00:19.864876385Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=1.995408902s
level=info ts=2018-04-26T09:00:20.843168795Z caller=compact.go:393 component=tsdb msg="compact blocks" count=3 mint=1524700800000 maxt=1524722400000
level=warn ts=2018-04-26T09:07:02.5320854Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too far into the future" num_dropped=45838

this looks normal to me.
the head is a temp in memory object and the series are persisted to disk  (I think every 2h by default)
The in memory head is used to avoid frequent writes to disk.

regarding missing metrics  you might be hitting this
https://github.com/prometheus/tsdb/issues/260
which already has an open PR

scrape_interval: 1h

This does not look like a sane setup, and the logs confirm you're doing something odd.

@brian-brazil it's a higher-level Prometheus scraping another one with less frequency
what's the oddness of such an approach and choosen scrape_interval?

are you actually missing any metrics when you run a query?
As I mentioned the head gets persisted to disk when it is cleared so the metrics aren't lost.

The maxmimum sane interval is 2m, and the logs indicate metrics are clashing. I'd presume that this behaviour is due to your setup, and not an issue with Prometheus.

it took me a while to realise the real issue :smile:
@semyonslepov just had a quick look at the code for the scraping and it seems that if the target in the federate_lts exposes metrics with a timestamp that doesn't overlap with the current head time range the samples won't get ingested.
so worth checking if the target doesn't expose samples with an incorrect timestamp.

Got the real data-loss issue with more sane configuration and it again correlates with the GC execution.
Configuration:
global:
  scrape_interval: 30s
  scrape_timeout: 10s
  evaluation_interval: 30s
  external_labels:
    account: spt-observability-pro
    monitor: prometheus-stack
    region: eu-west-1
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      - ip-10-58-130-53:9093
    scheme: http
    timeout: 10s
rule_files:
- /etc/prometheus/alert_configs/*.yml
- /etc/prometheus/recording_rules/*.yml
scrape_configs:
- job_name: alertmanager
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-53:9093
- job_name: node_exporter
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-53:9100
  relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: ^(.*)$
    target_label: tier
    replacement: p1
    action: replace
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p1
    action: replace
- job_name: health-check-target
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /_/metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-53:8181
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p1
    action: replace
- job_name: grafana
  honor_labels: true
  scrape_interval: 30s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - region: eu-west-1
    refresh_interval: 1m
    port: 3000
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: metrics-platform-frontend
    replacement: $1
    action: keep
- job_name: prometheus-stack
  scrape_interval: 30s
  scrape_timeout: 15s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - region: eu-west-1
    refresh_interval: 1m
    port: 9090
  relabel_configs:
  - source_labels: [__meta_ec2_tag_prometheus_tier]
    separator: ;
    regex: ^p.+$
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_prometheus_tier]
    separator: ;
    regex: ^(.*)$
    target_label: tier
    replacement: $1
    action: replace
- job_name: datadog
  scrape_interval: 5m
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - ip-10-58-130-53:9091
- job_name: obs_p0_federate
  honor_labels: true
  params:
    match[]:
    - '{job=~"[a-z].*"}'
  scrape_interval: 30s
  scrape_timeout: 15s
  metrics_path: /federate
  scheme: https
  static_configs:
  - targets:
    - prometheus-aws-eu-central-1.spt-mkt-trust-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-mkt-trust-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-observability-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-infra-sre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.cre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.blocket-insight-pro.schibsted.io:443
    - prometheus-creservices-pro.ingress.cre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.mp-pro.schibsted.io:443
    - prometheus-aws-eu-west-3.search-engineering-dev.schibsted.io:443
    - prometheus-aws-eu-west-3.search-engineering-pro.schibsted.io:443
    - prometheus-mp-mads-dev.ingress.cre-pro.schibsted.io:443
  metric_relabel_configs:
  - separator: ;
    regex: pod_template_hash
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_deployed_by
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_deployment_id
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_version
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kubernetes_pod_name
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: awsHostId
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: awsHostname
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_app_deployed_at
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_created_at
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kube_aws_coreos_com_autoscalinggroup
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kube_aws_coreos_com_launchconfiguration
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: ec2_autoscaling_group
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: label_kube_aws_coreos_com_launchconfiguration
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: label_kube_aws_coreos_com_autoscalinggroup
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: container_id
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: image_id
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: pod
    replacement: $1
    action: labeldrop
- job_name: ext_p0_federate
  honor_labels: true
  params:
    match[]:
    - '{job=~"[a-z].*"}'
  scrape_interval: 30s
  scrape_timeout: 15s
  metrics_path: /federate
  scheme: https
  static_configs:
  - targets:
    - prometheus-aws-eu-west-1.rkt.schibsted.io:443
    - prometheus-aws-eu-west-1.ami-store.schibsted.io:443
    - delivery-prometheus-local.ingress.cre-pro.schibsted.io:443
    - prometheus.sol-osl01.finntech.no:443
    - prometheusadin.finntech.no:443
    - prometheusadout.finntech.no:443
    - prometheuscustomer.finntech.no:443
    - prometheusfrontend.finntech.no:443
    - prometheuspenger.finntech.no:443
    - prometheussearch.finntech.no:443
    - prometheusk8s.prod.finntech.no:443
    - metrics.kufar.by:443
    - prometheus-aws-eu-west-1.devrel-dev.schibsted.io:443
    - prometheus-aws-eu-west-1.search-engineering-dev.schibsted.io:443
  metric_relabel_configs:
  - separator: ;
    regex: pod_template_hash
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_deployed_by
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_deployment_id
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_version
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kubernetes_pod_name
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: awsHostId
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: awsHostname
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_app_deployed_at
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: fiaas_created_at
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kube_aws_coreos_com_autoscalinggroup
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: kube_aws_coreos_com_launchconfiguration
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: ec2_autoscaling_group
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: label_kube_aws_coreos_com_launchconfiguration
    replacement: $1
    action: labeldrop
  - separator: ;
    regex: label_kube_aws_coreos_com_autoscalinggroup
    replacement: $1
    action: labeldrop
- job_name: obs_p0_prom_metrics
  honor_labels: true
  scrape_interval: 30s
  scrape_timeout: 15s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - prometheus-aws-eu-central-1.spt-mkt-trust-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-mkt-trust-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-observability-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.spt-infra-sre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.cre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.blocket-insight-pro.schibsted.io:443
    - prometheus-creservices-pro.ingress.cre-pro.schibsted.io:443
    - prometheus-aws-eu-west-1.mp-pro.schibsted.io:443
    - prometheus-aws-eu-west-3.search-engineering-dev.schibsted.io:443
    - prometheus-aws-eu-west-3.search-engineering-pro.schibsted.io:443
    - prometheus-mp-mads-dev.ingress.cre-pro.schibsted.io:443
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p0
    action: replace
- job_name: ext_p0_prom_metrics
  honor_labels: true
  scrape_interval: 30s
  scrape_timeout: 15s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - prometheus-aws-eu-west-1.rkt.schibsted.io:443
    - prometheus-aws-eu-west-1.ami-store.schibsted.io:443
    - delivery-prometheus-local.ingress.cre-pro.schibsted.io:443
    - prometheus.sol-osl01.finntech.no:443
    - prometheusadin.finntech.no:443
    - prometheusadout.finntech.no:443
    - prometheuscustomer.finntech.no:443
    - prometheusfrontend.finntech.no:443
    - prometheuspenger.finntech.no:443
    - prometheussearch.finntech.no:443
    - prometheusk8s.prod.finntech.no:443
    - metrics.kufar.by:443
    - prometheus-aws-eu-west-1.devrel-dev.schibsted.io:443
    - prometheus-aws-eu-west-1.search-engineering-dev.schibsted.io:443
  metric_relabel_configs:
  - source_labels: [__name__]
    separator: ;
    regex: .*
    target_label: tier
    replacement: p0
    action: replace

up metric from one of the federated targets:

scrape_samples_scraped from the same target:

Log messages on the federating instance:
level=info ts=2018-05-07T13:00:01.543596388Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1525687200000 maxt=1525694400000
level=info ts=2018-05-07T13:00:26.694997426Z caller=head.go:348 component=tsdb msg="head GC completed" duration=1.400530985s
level=info ts=2018-05-07T13:00:32.643341791Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=5.94827516s

That's a failed scrape, which is not data loss. See also https://www.robustperception.io/federation-what-is-it-good-for/

@brian-brazil how did you figure it is a missed scrape?

up is 0.

thanks I didn't notice the screenshot untill now.
@semyonslepov this looks different than the original issue with the ingestion logs.
..."Error on ingesting samples that are too old or are too far into the future" num_dropped=40776
@semyonslepov did you check if the target exposes the correct timestamps?

I am still a bit curious why this happens.
looking at the code ErrOutOfBounds is returned when you try to ingest metrics outside  the current time window of the  in-memory buffer (or the head) .
https://github.com/prometheus/prometheus/blob/5b27996cb3adeedb5fe10a5c4ce08fe9aaa218b3/vendor/github.com/prometheus/tsdb/head.go#L481-L483
I just tried the federation  and it returns the mos recent ingested sample+timestamp so even if you scrape the main Prometheus server every 2h (like in your original config) you should still be getting a recent timestamp which should be within the current head time range.
The only explanation would be if the main server that you are federating returns a timestamp that is too old so it cannot be ingested in the current head

I would imagine that it's an issue for the first configuration with per-1h scrape. However, it still happens for per-30s scrapes. Moreover, in this case, it doesn't happen randomly, it happens at the same time as GC comes.

I think dropping at gc is normal as this is when the code verifies that the metrics have the correct timestamp sequence and drops the once that are not within the head time range.
Still curious as of why these would be marked as OutOfBounds if the federated Prometheus returns correct timestamps.
I might be wrong , but don't see any problem how often you scrape the federated instance as long as it returns recent timestamps for all metrics.
I would be interested to read some more insights on this.

@semyonslepov  is it behaving as expected after you changed the configs?

@krasi-georgiev I didn't change configuration, there are two different configurations on two different hosts, I just wanted to emphasize that they both have the same issue

I am running out of ideas on this one.
@semyonslepov do you have any new info on the issue?

@krasi-georgiev no news, scrapes still fail leaving gaps afterwards (it happens together with out of bounds error or without it, out of bounds errors can happen separately from time to time but it doesn't lead to such a big gap - OutOfBound counters change is too low at these moments).

@krasi-georgiev I will try to increase scrape timeouts and look how it works, probably it's all about too heavy federation target

Timeout increase didn't help (and scrape_duration_seconds is within some reasonable range of 0-2 seconds). Just following messages at the time of failed scrape:
level=warn ts=2018-06-17T16:46:59.808406963Z caller=scrape.go:932 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284
009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="Error on ingesting samples that are too old or are too
 far into the future" num_dropped=47427
level=warn ts=2018-06-17T16:46:59.808488624Z caller=scrape.go:697 component="scrape manager" scrape_pool=federate_lts target="http://internal-prometheu-Internal-94VCZL74ZSUN-1346284
009.eu-west-1.elb.amazonaws.com:9090/federate?match%5B%5D=%7Bjob%3D~%22%5Ba-z%5D.%2A%22%2Cjob%21%3D%22federate_lts%22%7D" msg="append failed" err="out of bounds"
level=info ts=2018-06-17T17:00:00.36112907Z caller=compact.go:393 component=tsdb msg="compact blocks" count=1 mint=1529244000000 maxt=1529251200000
level=info ts=2018-06-17T17:00:18.261083468Z caller=head.go:348 component=tsdb msg="head GC completed" duration=2.878933852s
level=info ts=2018-06-17T17:00:20.346929019Z caller=head.go:357 component=tsdb msg="WAL truncation completed" duration=2.085781882s

And empty result when trying to fetch the test metric's value (we have a monitoring script on it, it asks Prometheus API for known metrics every 5 minutes).

maybe if you add some debugging info it will give you a clue what samples are dropped but the output would be quite busy so not sure if it will help
func (a *headAppender) Add(lset labels.Labels, t int64, v float64) (uint64, error) {
	if t < a.mint {
		if lset.String() == "..........?? filter by a specific lset" {
			fmt.Println("Dropping")
			fmt.Println(lset)
			fmt.Println(t)
			fmt.Println(v)
		}
		return 0, ErrOutOfBounds
	}

add here
https://github.com/prometheus/prometheus/blob/5b27996cb3adeedb5fe10a5c4ce08fe9aaa218b3/vendor/github.com/prometheus/tsdb/head.go#L480-L483
to compile a binary after the change
git clone .....
cd cmd/prometheus
go build

seems stale, feel free to reopen if you think we should revisit.


Support setting comment for ACL

There is a feature that allows to block ACL edits from admin console by specifying special comment in the top of the ACL: https://tailscale.com/kb/1204/gitops-acls/#prevent-others-from-accidentally-modifying-your-tailnet-policy-file
However, there is no way to pass such comment when using Client's SetACL() method, because it only accepts ACL structure. Maybe it could be added via SetACLOption?
After adding it here it would be nice to add the same feature in https://github.com/tailscale/terraform-provider-tailscale.

We should also stop maintaining two clients and migrate the terraform provider to use https://pkg.go.dev/tailscale.com/client/tailscale


Databricks database support

Databricks has recently expanded its data warehousing offerings, and because of this companies have begun to forgo using Databricks in combination with other warehouses like Snowflake or BigQuery and instead have decided just to keep everything within Databricks.  Because of this shift, there is a need for more traditional SQL tooling that supports the Databricks SQL divers and dialect.  This merge request is designed to create a community-supported Databricks SQL implementation for the flyway database migration tool.
References:
What is a Databricks SQL Warehouse: https://docs.databricks.com/sql/admin/sql-endpoints.html
Databricks SQL Reference Docs: https://docs.databricks.com/sql/language-manual/index.html

 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.

+1
We were looking into writing this ourselves, so very much looking forward to this PR getting merged in.

@zayscue Did you get this working with Unity Catalog? I'm trying to follow along here and connect to the catalog then database/schema, and it's not working as intended. Did you need to complement catalog support separately? Or changes to the URL?

Came here looking for Databricks support in Flyaway

Would love to utilize this feature and see it get some attention by Databricks and Red-Gate folks and get merged.

Any news on this?

Forked this and made some additional changes: https://github.com/flyway/flyway/pull/3681

Waiting for this feature - please merge and release!  Even if it's 'beta', lets try it.

Are there any updated on this feature?

Any Update on this features

+1

Closing as been merged in via https://github.com/flyway/flyway-community-db-support/pull/26


[fmt] Build error

Host Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
 ./vcpkg install spdlog
Failure logs
`CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:83 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: D:/Users/Administrator/Documents/GitHub/vcpkg/buildtrees/fmt/x86-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      D:\Users\Administrator\Documents\GitHub\vcpkg\buildtrees\fmt\config-x86-windows-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:238 (vcpkg_execute_required_process)
  ports/fmt/portfile.cmake:12 (vcpkg_cmake_configure)
  scripts/ports.cmake:146 (include)

error: building fmt:x86-windows failed with: BUILD_FAILED `

Additional context
Full Text:
` Computing installation plan...
The following packages will be built and installed:
  * fmt[core]:x86-windows -> 8.1.1#1
    spdlog[core]:x86-windows -> 1.10.0#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet "x86-windows"...
Restored 0 packages from C:\Users\Administrator\AppData\Local\vcpkg\archives in 222.3 us. Use --debug to see more details.
Installing 1/2 fmt:x86-windows...
Building fmt[core]:x86-windows...
-- Using cached fmtlib-fmt-8.1.1.tar.gz.
-- Cleaning sources at D:/Users/Administrator/Documents/GitHub/vcpkg/buildtrees/fmt/src/8.1.1-11f8359597.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/Users/Administrator/Documents/GitHub/vcpkg/downloads/fmtlib-fmt-8.1.1.tar.gz
-- Applying patch fix-write-batch.patch
-- Applying patch fix-invalid-command.patch
-- Using source at D:/Users/Administrator/Documents/GitHub/vcpkg/buildtrees/fmt/src/8.1.1-11f8359597.clean
-- Found external ninja('1.10.2').
-- Configuring x86-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:83 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: D:/Users/Administrator/Documents/GitHub/vcpkg/buildtrees/fmt/x86-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      D:\Users\Administrator\Documents\GitHub\vcpkg\buildtrees\fmt\config-x86-windows-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:238 (vcpkg_execute_required_process)
  ports/fmt/portfile.cmake:12 (vcpkg_cmake_configure)
  scripts/ports.cmake:146 (include)

error: building fmt:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+fmt
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[fmt]+Build+error
Include '[fmt] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2022-06-17-9268e366206712e38102b28dbd1617697a99ff2e
    vcpkg-scripts version: 4826ede84 2022-07-01 (3 days ago)

You can also use the prefilled template from D:\Users\Administrator\Documents\GitHub\vcpkg\installed\vcpkg\issue_body.md `

Fixed...
but i don't know how it worked....

Good to know that the issue is gone, I can't reproduce the same on my side.
I'll close this issue, and if it reappears with you, please reopen this issue and send the failure log to us.


Nuget Packages available?

I tried using the repo but get the following error message. Are the Beta3 packages available on Nuget?

Finally found the location. It was hidden under the badge on the OrchardCore ReadMe.
https://myget.org/feed/orchardcore-preview/package/nuget/OrchardCore.Application.Cms.Targets


ADD: SPEED UP and CANCEL

Need to allow xchainjs to facilitate handling pending tx
CANCEL
Need to find the pending UTXOs or pending NONCE and spend back to SELF
SPEED UP
Need to find the pending UTXOs or pending NONCE and redo the desired tx.
Implementation - CANCEL
cancel() should:

if UTXO, then find the pending UTXOs and re-consume them back to self
if Account, then find the latest nonce and re-spend back to self

Implementation - SPEED UP
bump(txData) should:

if UTXO, then find the pending UTXOs and re-consume them with new txData
if Account, then find the latest nonce and re-spend back with new txData

Closing this issue as nothing has been heard here in a year


Remove gcsfuse from mergeSTR script

removes gcfuse from mergeSTR script, replace with local file copying into job environment
adds job storage param to change when needed.

the tortoise (mergeSTR) beats the hare (bcftools merge)...


Trigger before_trading_start() on a mid-day start

Fix the problem that before_trading_start() is only called if the algo was running at 8:45 EDT
(before_trading_start_minutes).

Coverage decreased (-0.4%) to 85.675% when pulling f3ce2adfdeeabdde162978ca789294a31c6ca86d on tibkiss:before_trading_start_trigger into 09672d466d31bd288f1784c6427ec1a1882cbb1a on zipline-live:master.

Rebased on top of master, ready to merge.

Coverage remained the same at 86.057% when pulling ddbdf86ecd49122ec5e0816f43715e7f42ad17ea on tibkiss:before_trading_start_trigger into 816e8cf26e5b019de299f1a6fbb7b472c64d6dd0 on zipline-live:master.


Fix Docker environment and improve reproducibility

Have guild work in the Docker environment

For some reason it installs a broken virtualenv==20.0.0b2
Set LANG
Use python3 and pip3 since python2.7 had reached EOL.

Increase reproducibility

Explicitly use Ubuntu 18
No apt-get upgrade

Follow Docker best practices for Ubuntu base containers

Looks great - thanks a lot!


Svelte ssr

Hey 👋
I was trying urql with svelte and managed to get it working. I've made a few tries to add ssr support in exchanges but failed.
Before making another attempt I'd like to ask if it's possible to use ssr with svelte in current version?
Thanks
urql version & exchanges:

@urql/svelte: 0.3.0

Related issue with the error I get - https://github.com/sveltejs/sapper/issues/1176, has linked bug issue https://github.com/sveltejs/svelte/issues/3582


Add coverage job to the build workflow

coverage: 100.0%. remained the same
when pulling b66020539912c1e838c52bd1f26365c8862ff0f2 on add_coverage_job_to_build_workflow
into d4188ad0ab04d6709a2ef09eeef79cae65b71d20 on master.


Fixup sysfs/system_cpu.go lint errors

Remove unnecessary nil assignment in sysfs/system_cpu.go to fix linter errors.
Followup to https://github.com/prometheus/procfs/pull/627

:eyeglasses: @rexagod


General: Fix conversion of dates in submission result component

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I followed the coding and design guidelines.

Motivation and Context

Fix sentry issue: https://sentry.ase.in.tum.de/organizations/artemis/issues/28726
Description

The exercise date were not converted from strings to dayjs objects when the submission/participation was loaded from the server, leading to an error in the console.
Steps for Testing

Prerequisites:

1 Instructor
1 Student
1 Text exercise with a due date

Log in to Artemis
Participate in the exercise and try to submit a text
Check that there is no error in the console

Review Progress

Performance Review

[ ] I confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Tested on TS2, participated in an exercise, and tried to submit text => there were no errors in the console


[rmkit] update remux to 0.1.5-1

launch remux on 3 finger tap (much more useful on rM2)
remux launches when SIGWINCH signal is sent

Looks good. Could you please update the source timestamp in the recipe?

Looks good. Could you please update the source timestamp in the recipe?


docs: Hide "Edit on GitHub" buttons

Following the instructions here, remove the buttons to edit on github
since this is confusing for contributors since it opens PRs against
branches where we don't accept contributions, bypasses the standard
instructions like requiring signoffs, etc.
https://github.com/readthedocs/readthedocs.org/blob/master/docs/guides/remove-edit-buttons.rst

I didn't test this yet, I just prepared a PR following the instructions in the link. I figured it's probably easiest to just submit & merge and get RTD to build the new version to validate.

make -C Documentation live-preview is rather quick and works well to render.
Current documentation

With your PR


Deprecate support for older macOS versions

Issue: #4

added the prettier formatter for code formatting conventions
removed few redundant catches in promises
reused retryPolicy options in retrying-promise package for handling number of maximum retries.
added few error messages in unhandled promises
removed all functionality that took care of distinguishing between macOS versions

Will work on getting the npm package updated by end of today.


WIP: move cvo override between create manifest and create cluster

It works but I'm not sure this is the right path to follow.
Pros:

Unwanted operators never run
It's what we aim with cluster profile
Simpler snc script

Cons:

Still leave broken contents (ns with services but not the operator, etc.)
CRDs created by operators are not present (PrometheusRule and ServiceMonitor for example)
It doesn't speed up snc
Override list is hard to maintain.

Another con to this approach.
If a user want to enable monitoring or any disable operator, it is quite easy override list till now to remove required component from the override list and CVO again start to bring that operator to the cluster ( https://code-ready.github.io/crc/#starting-monitoring-alerting-telemetry_gsg ). I think with this PR it would be very difficult.

We could also introduce a crc command to do it. I just added in the overrides:

all PrometheusRule
all ServiceMonitor
some ClusterOperators

It's a just a big list but we could automate that by listing PrometheusRule and ServiceMonitor in the release image.

It's a just a big list but we could automate that by listing PrometheusRule and ServiceMonitor in the release image.

@guillaumerose you mean using https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusterversion.md#setting-objects-unmanaged ( oc adm release extract ..) and parse the Rules ?

Not better than before, closing.


python SDK copy_blob doesn't work for storage account KIND BlobStorage

Hi,
We recently encounter a problem when copying a vhd file from our public blob to storage account with KIND  BlobStorage.
When create the ARM storage, the default storage KIND is general purpose which we don’t have an issue to copy with. But if user select special KIND BlobStorage, our image download using copy_blob failed silently until we poll the blob status and find out the blob doesn’t exist.
We are on python SDK rc2 with azure-storage upgraded to 0.32.0. And the code snippet is as following, we tried both BaseBlockService and BlockBlockService both failed on this special KIND of storage account, General purse storage account doesn’t have issue:
    storage_container_name = 'armcommunityimages'
    cloudn_image_url = 'https://hsiangwesteurope.blob.core.windows.net/vhds/CloudN-ARM-20160406-os-2016-04-06.vhd’
    storage_account_keys = \
       storage_client.storage_accounts.list_keys(rg_name, storage_name)
    blob_service = BlockBlobService(
                       account_name=storage_name,
                       account_key=storage_account_keys.key1)

   blob_service.create_container(container_name=storage_container_name)
   time.sleep(x)
    …
    blob_service.copy_blob(
                      container_name=storage_container_name,
                      blob_name=vhd_blob_name,
                      copy_source=cloudn_image_url)
    …
    blob_service.get_blob_properties(container_name, blob_name)  When we poll the status of the blob, we see blob doesn’t exist.
    …

Tried both BaseBlobService and BlockBlobService for the above, neither was successful. And also try to get this KIND field of the storage account, the list storage account property doesn’t contain this field, not sure which API should I use to get the ‘BlobStorage’ KIND.
result = storage_client.storage_accounts.list()
for acc in result:
vars(acc)
{'secondary_location': u'northeurope', 'account_type': <AccountType.standard_ragrs: 'Standard_RAGRS'>, 'name': u'lyanblobstorage', 'tags': {}, 'primary_location': u'westeurope', 'secondary_endpoints': <azure.mgmt.storage.models.endpoints.Endpoints object at 0x7f4b9bae3690>, 'creation_time': datetime.datetime(2016, 6, 18, 5, 36, 56, 778994, tzinfo=<isodate.tzinfo.Utc object at 0x7f4b9c581e90>), 'provisioning_state': <ProvisioningState.succeeded: 'Succeeded'>, 'primary_endpoints': <azure.mgmt.storage.models.endpoints.Endpoints object at 0x7f4b9bae36d0>, 'location': u'westeurope', 'last_geo_failover_time': None, 'status_of_primary': <AccountStatus.available: 'Available'>, 'status_of_secondary': <AccountStatus.available: 'Available'>, 'type': u'Microsoft.Storage/storageAccounts', 'id': u'/subscriptions/cda16bf7-f6d4-40b1-84fa-a74fab8001ac/resourceGroups/rg-westeurope/providers/Microsoft.Storage/storageAccounts/lyanblobstorage', 'custom_domain': None}
Hope you can help us on solving this issue.
Thanks.
Li

Is your public blob a page blob?

Hi Emily,
Our public blob is a vhd file which I consider it a page blob right? I saw the description said that the BlobStorage doesn’t support page blob, but the copy_blob API doesn’t give either exception or error until we poll the blob property.
Another question is how do we get the storage account KIND field, which python API to use? When I list the account I can get storage account type, but not this KIND field.
Thanks.
Li
From: Emily Gerner<EMAIL_ADDRESS>Sent: Tuesday, June 21, 2016 9:57 AM
To: Azure/azure-storage-python<EMAIL_ADDRESS>Cc: Li Yan<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-storage-python] python SDK copy_blob doesn't work for storage account KIND BlobStorage (#189)
Is your public blob a page blob?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-python/issues/189#issuecomment-227503008, or mute the threadhttps://github.com/notifications/unsubscribe/AJ2yjNS8qGEn_eSOOm91e61JLs7QLIRVks5qOBfNgaJpZM4I6GW0.

Yes, VHDs are page blobs. So, you can't copy a page blob into this account type as it does not support the blob type.
Could you confirm for me what the copy_blob API returns for you? It returns a CopyProperties object with quite a few fields and I'm curious what values you're seeing for those.
Questions on the management libraries should go in the azure-sdk-for-python repo, though I believe the answer is simply that the Python management libraries are still in preview and may be slightly behind the newest features. I know they're working very hard on getting these up to date, but you'd have to ask there for any timelines.

Hi Emily,
Thanks for the prompt response!
I ran the python interpreter, the copy_blob actually provides an exception of AzureHttpError that tells the page blob is not supported. But in our case we use pyinstaller to compile, we are not seeing any exception, not sure why, my coworker once told about similar api for storage had similar discrepancy between the interpreter vs pyinstaller compiled code.
I will check the link you sent me to find out the API to read field so that we can filter out that storage type for customer to copy.
Best Regards,
Li
From: Emily Gerner<EMAIL_ADDRESS>Sent: Tuesday, June 21, 2016 10:12 AM
To: Azure/azure-storage-python<EMAIL_ADDRESS>Cc: Li Yan<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-storage-python] python SDK copy_blob doesn't work for storage account KIND BlobStorage (#189)
Yes, VHDs are page blobs. So, you can't copy a page blob into this account type as it does not support the blob type.
Could you confirm for me what the copy_blob API returns for you? It returns a CopyProperties object with quite a few fields and I'm curious what values you're seeing for those.
Questions on the management libraries should go in the azure-sdk-for-pythonhttps://github.com/Azure/azure-sdk-for-python repo, though I believe the answer is simply that the Python management libraries are still in preview and may be slightly behind the newest features. I know they're working very hard on getting these up to date, but you'd have to ask there for any timelines.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-python/issues/189#issuecomment-227507418, or mute the threadhttps://github.com/notifications/unsubscribe/AJ2yjOIwN3SU7Ra_U04OC8w39QVITBG5ks5qOBtmgaJpZM4I6GW0.

Good to hear you figured it out! That's the error message I expected you to get.
I have no experience with pyinstaller, nor have I heard of any other users having issues with our APIs not throwing exceptions in any other use cases. If you can get more detail on whats wrong and have thoughts on what storage could change to make things work better, feel free to spin up a new issue thread and we can discuss options.

Thanks for all your help Emily!
Li
From: Emily Gerner<EMAIL_ADDRESS>Sent: Tuesday, June 21, 2016 10:42 AM
To: Azure/azure-storage-python<EMAIL_ADDRESS>Cc: Li Yan<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-storage-python] python SDK copy_blob doesn't work for storage account KIND BlobStorage (#189)
Good to hear you figured it out! That's the error message I expected you to get.
I have no experience with pyinstaller, nor have I heard of any other users having issues with our APIs not throwing exceptions in any other use cases. If you can get more detail on whats wrong and have thoughts on what storage could change to make things work better, feel free to spin up a new issue thread and we can discuss options.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-python/issues/189#issuecomment-227515892, or mute the threadhttps://github.com/notifications/unsubscribe/AJ2yjM3rYeSrFaf44skVBg0kDPfdnc0Aks5qOCJhgaJpZM4I6GW0.


Does this trigger authorizers attached to the lambda function?

For example:
# serverless.yml
functions:
  auth:
    handler: path/to/auth.js
  hello:
    warmup:
      enabled: true

// auth.js
module.exports.auth = (event, context, callback) => {
  if (event.source === 'serverless-plugin-wawrmup') {
    callback(null, 'Is warm')
  }
  ... auth logic
}

Would this kind of setup work?

Hi @reilg,
This module simply calls the function directly. Not through the API Gateway.
So it's irrelevant whether you have an authorizer set up or not.

Yeah, that makes sense. Thanks, @juanjoDiaz.


TileEntityBasicBlock causes incompatibility

TileEntityBasicBlock updates neighbouring blocks during the chunk loading process by calling markDirty(). This may happen before the server is running and therefore may cause errors in other mods.
For example this results in XNet networks to not load correctly as described here.

Just wanted to +1 this. Causing issues using Xnet in the Enigmatica 2 modpack.

Any chance on getting the call removed and a new release moved out. This has disabled a large server with some complicated Xnet that I am a part of and we would love to get back to using both Mekanism as well as Xnet


The full screen AD cannot be displayed on a perforated phone

Steps to Reproduce

SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge, overlays: []);
on Android

getWindow().getDecorView().setSystemUiVisibility(
    View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN |
    View.SYSTEM_UI_FLAG_LAYOUT_STABLE |
    View.SYSTEM_UI_FLAG_FULLSCREEN |
    View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY
);

RewardedInterstitialAd.show

Expected results:
I wanted to display a fullscreen AD, but on the perforated phone, the status bar was not covered by the AD, Or set it to a black background instead of a transparent one
Actual results:

Logs

Hi @crazecoder, this may also be the default behavior on Android. Are you able to reproduce with our Android Rewarded Interstitial sample?

@malandr2 This problem also occurs in the Android Rewarded Interstitial example
just change style.xml
<!-- Base application theme. -->
    <style name="AppTheme" parent="Theme.AppCompat.Light.NoActionBar">
        <item name="android:windowNoTitle">true</item>
        <item name="android:windowTranslucentNavigation">true</item>
        <item name="android:statusBarColor">@android:color/transparent</item>
        <!-- Customize your theme here. -->
    </style>

and set activity_main.xml a red background
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:background="@android:color/holo_red_dark" //add this
    tools:context="com.google.ads.rewardedinterstitialexample.MainActivity">

Hi @crazecoder, thanks for checking that. Because the flutter plguin behaves the same, this appears to be the intended behavior. To further clarify if this is expected (for Android), please create a new thread in the AdMob Developers Forum to the confirm Android behavior. If this is unexpected, Android will have to address in the Android SDK.
Closing this out for now. Thanks!


Derive Hash and Eq for Slice and IndexBuffer

Changed

Derive Hash and Eq traits for Slice and IndexBuffer.

@homu r+

:pushpin: Commit 6f36c95 has been approved by kvark

:hourglass: Testing commit 6f36c95 with merge 05d6460...

:sunny: Test successful - status


reworked the README and changed the logo

I reduced that scope of this PR to the bare minimum to get the rebranding finished. The link to the documentation has also been corrected to point to the installation docs.


(1) Expose Attach/Detach (2) Add hns unit testing

(1) Expose Attach/Detach
(2) Add hns unit testing

ping @jhowardmsft  @msabansal

ping @pradipd @dineshgovindasamy

Also, could you split this into two commits? One for Attach/Detach and one for tests.

Took care of the review comments

LGTM

Some more testing is being done. Wait for Merge

Testing Complete. Ready for merge. Ping @jhowardmsft

On vacation... @darrenstahlmsft can you take a look pls

Merged.


Some links in documentation site are unaccessable

Describe the bug
some link errors are detected by link checker workflow.
the links return 404.
https://github.com/tier4/scenario_simulator_v2/actions/workflows/DocumentationLinkCheck.yaml
Expected behavior
No errors on the link checker workflow.

It's probably due to this PR.
https://github.com/tier4/scenario_simulator_v2/pull/1113


Improve get feed with pagination

Fix #31752
@somera

Sorry, I added the label mistakenly, please ignore.


ProgressBar overlap list

Observed Behaviour
ProgressBar overlap list in TracksFragment,  BookmarksFragment, ScheduleFragment, SpeakerListFragment, SponsorsFragment.
Screenshots

Expected Behaviour
On scroll ProgressBar should come to top and list should be below progressBar.
@the-dagger Please assign me this, I would like to work on this.

@vishwesh3 Go ahead and work on this please. Thanks

@mananwason created PR #867 . Please have a look on it.

@mananwason shall I work on this?

Please go ahead
On Tue 10 Jan, 2017, 11:13 PM Rohan Agarwal<EMAIL_ADDRESS>wrote:

@mananwason https://github.com/mananwason shall I work on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-android/issues/831#issuecomment-271644471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFKCXTiRFtNAUotLsJC_iSt-MopOgj8ks5rQ8MtgaJpZM4LJ4zH
.

--
Regards,
Manan Wason
4th year, B.tech - CSE
Indraprastha Institute of Inf. Tech. (IIIT) Delhi
Okhla, Phase-III, New Delhi-110020, INDIA
Website: www.mananwason.me http://www.mananwason.me/

@mananwason please have a look at my existing pr so that I could submit another one for this.

@rohanagarwal94 Thanks for your interest in the issue. You can switch to different branch and work on this issue. I have done some work on this https://github.com/fossasia/open-event-android/pull/867 this might be helpful.

@vishwesh3 I just checked your pr and it is same as my changes to this issue. Please submit a fresh PR from your side since I noticed, it only closed down due to branching issues.

@rohanagarwal94 You can start working on a new branch by checking out from upstream development. Meanwhile, I'll look at your PR asap.

@mananwason please close this. This has already been solved.


resource builders without the need for AnyResource

AnyResource is nice for quick and readable setup.
But we should still support manual/coded setup of a ConfijResource as well.
Especially for complex resources like Git with a repoPath + authentication + a file + a refspec...

extendable idea with lambdas inside the builder...
ConfijBuilder.of(Cfg.class).loadFromProperties((anySrc,format) -> ...).build()
ConfijBuilder.of(Cfg.class).loadFromSource(MyResource.class, MyFormat.class, (src, format) -> ...).build()


Update to Gradle 7.5.1

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>Description
Update to Gradle 7.5.1
Issues Resolved
Closes https://github.com/opensearch-project/geospatial/issues/133
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock sorry to drag you in, do you now when / how we publish OpenSearch snapshots? I don't see the job on Jenkins ....

@dblock sorry to drag you in, do you know when / how we publish OpenSearch snapshots? I don't see the job on Jenkins .... It seems the latest one is from 24th of Aug

The issue was https://github.com/opensearch-project/opensearch-build/issues/2535.


iOS, Recaptcha, and WebView

We have a webview for our game app. When a user goes to register on our site, we have a recaptcha image. It works fine on web and Android. For iOS however, something very strange happens. When we press the button to go to the login page with the recaptcha code, it loads the recaptcha in a separate browser (launches safari).
Here is the snippet. What is strange is that I have set javaScriptCanOpenWindowsAutomatically and setSupportMultipleWindows to false. I've also tried to override onShouldStartLoadWithRequest.
<SafeAreaView style={{ flex: 1, backgroundColor: 'black' }}>
      <WebView
        allowFileAccess={true}
        allowFileAccessFromFileURLs={true}
        allowsBackForwardNavigationGestures={true}
        allowsFullscreenVideo={false}
        allowsInlineMediaPlayback={true}
        allowUniversalAccessFromFileURLs={true}
        domStorageEnabled={true}
        javaScriptEnabled={true}
        javaScriptCanOpenWindowsAutomatically={false}

        mediaPlaybackRequiresUserAction={false}
        // set useragent to desktop chrome
        userAgent={
          'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ' +
          '(KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36'
        }
        onShouldStartLoadWithRequest={
          handleOnShouldStartLoadWithRequest // this function just returns true
        }
        onContentProcessDidTerminate={() => {
          if (webViewRef.current) {
            webViewRef.current.reload();
          }
        }}
        onNavigationStateChange={(navState) => {
          console.log('onNavigationStateChange', navState.url);
        }}
        originWhitelist={[
         // our website domain
        ]}
        setSupportMultipleWindows={false}

        pullToRefreshEnabled={true}
        ref={webViewRef}
        sharedCookiesEnabled={true}
        source={{ uri: webViewUrl,
          baseUrl: host
        }}
        startInLoadingState={true}
      />
    </SafeAreaView>
    ```

@k2xl
Have you solved this problem yet? I'm also having this problem, hope you solved it.

I have a similar issue too, it works fine on Android(emulator and device), on iOS(device) works but never on the simulator, in my case it breaks when executing recaptcha v3 execute function, I receive:
null is not an object (evaluating '(e=[1,(l=function(a,P){V.P.has((P=[!0,9,\"error\"],gQ))?Q[P[1]](1,V.P,gQ,P[0])(a):a&&h&&console[P[2]](a)},\"ny\"),\"window\"],V.O).then


add function to update module files copying replace directives from o…

…ne to the other

@amnonbc what is the purpose of this?

@amnonbc what is the purpose of this?

@dmotylev go.mod replace directive is not transitive, so doesn't work for us in the go sandbox. Amnon's fix reads it from the Sift's go.mod and write it to the sandbox's go.mod to overcome this.

@dmotylev go.mod replace directive is not transitive, so doesn't work for us in the go sandbox. Amnon's fix reads it from the Sift's go.mod and write it to the sandbox's go.mod to overcome this.


Adding CI workflow for Windows OS (#264) (#265)

Signed-off-by: Joshua Palis<EMAIL_ADDRESS>Signed-off-by: Joshua Palis<EMAIL_ADDRESS>(cherry picked from commit 54a10417530c9c9eeb31f1fd443332bf8d4042e1)
Co-authored-by: Joshua Palis<EMAIL_ADDRESS>Description
Adding CI Workflow for Windows OS
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #266 (54a1041) into 2.4 (da0e6c8) will decrease coverage by 0.22%.
The diff coverage is n/a.

:exclamation: Current head 54a1041 differs from pull request most recent head 59cff6d. Consider uploading reports for the commit 59cff6d to get more accurate results

@@             Coverage Diff              @@
##                2.4     #266      +/-   ##
============================================
- Coverage     53.19%   52.96%   -0.23%
+ Complexity       65       64       -1
============================================
  Files             8        8
  Lines           438      438
  Branches         50       50
============================================
- Hits            233      232       -1
  Misses          186      186
- Partials         19       20       +1

Impacted Files
Coverage Δ

...pensearch/jobscheduler/scheduler/JobScheduler.java
72.94% <0.00%> (-1.18%)
:arrow_down:

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


Per-file OWNERS

Forked from #739
The OWNERS mechanism in the main repo is directory-based. However, we have many docs with different technical content side by side. Therefore, we need a file-based OWNERS mechanism for automatic PR assignment. #739 suggested representing owners in doc front-matter.
Tests need sub-file owners, but it doesn't look like that mechanism would fit the doc use case very well.
cc @kubernetes/contributor-experience @kubernetes/kubernetes-docs-maintainers

I agree that a per-file OWNERS is probably necessary, but I think it would still be useful to restructure many of the guides into directories. There are already implicit groupings that the flat directory structure is hiding.

@Kashomon I'm fine with adding structure, though we need to be careful to not break existing URLs. We will break everything when we do the overhaul, but we need to avoid repeatedly breaking links, which we've not been great about.

@foxish Many of the documents were copied from the kubernetes repository in a way that didn't preserve git history.
Compare:
https://github.com/kubernetes/kubernetes.github.io/blame/master/docs/user-guide/configmap/index.md
with:
https://github.com/kubernetes/kubernetes/commits/master/docs/user-guide/configmap.md
We'll need to extract the original authors from the kubernetes repository.
Also, it would be useful to support both per-directory and per-file owners. We'll want to be able to easily cover files that are part of the site layout and navigation, for instance, such as:
https://github.com/kubernetes/kubernetes.github.io/tree/master/_includes

@bgrant0607 What is the long-term plan with the generation of OWNERS? Is it to generate them once and then let the OWNERS themselves maintain it, or to maintain and re-run the script from time to time to update the lists?

@foxish I expect we'll generate it once and then curate it manually thereafter, but we do have several more repositories we need to generate OWNERS information for, and there will likely be new repositories donated in the future that we'll need to generate OWNERS information for.

The current way in which coreos/findowners operates is to take the top N committers over the last 6 months. However, as we saw in case of contrib/, it missed some owners who had committed the original file, because they hadn't contributed in over 6 months.
I think we can fix this in one of the following ways:

Going over the entire commit history instead of just the last 6 months
Using the last 6 months, but also adding the original author to the list of owners.
Looking at a fixed number of commits prior to HEAD and pick top N committers from that.

I can tell at least on the docs side that the older docs may not have had any substantial changes in a while and using the 6 months criterion definitely wouldn't suffice there.

Closing as this is done.


How to handle MoyaError  with Result Framework with Swift 5?

Hi there,
I'm using Moya 13.0.1 with swift 5 , and Moya remove Result Framework because it's in built in Swift 5 , so the issue is that in older version of Moya like 12.0.1 when Status code is 400 then it automatically goes to Failure state , but right now with the new version of Moya it goes to Success state .
This is happened in  Older Version of Moya(12.0.1)
po result
▿ .failure(underlying(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableStatusCode(code: 400)), Optional(Status Code: 400, Data Length: 25)))
▿ failure : MoyaError
▿ underlying : 2 elements
▿ .0 : AFError
▿ responseValidationFailed : 1 element
▿ reason : ResponseValidationFailureReason
▿ unacceptableStatusCode : 1 element
- code : 400
▿ .1 : Optional
▿ some : Status Code: 400, Data Length: 25
This is happened in  Newer Version of Moya(13.0.1)
po result
▿ Result<Response, MoyaError>
▿ success : Status Code: 400, Data Length: 25
And other issue is that How to handle Moya error because thay remove error variable from Moya(13.0.1)

and don't know how to use mapError , and FlatmapError

When i am use this function it never come in to the body .
so , please help me that how to handle moya error with this new "mapError" or "flatMapError" and this is bug from moya that Status code like 400 goes to Success case .

There seems to be a misunderstanding: the Result framework have been replaced by the built-in Result in Moya 14, not in Moya 13.
To get the underlying error with the built-in Result you case to extract it with a case let statement:
switch result {
case let .failure(moyaError):
case let .success(response):
}

if case let .failure(moyaError) = result { }
About the mapError and flatMapError I suggest to report to the Apple's doc. Basically map and flatMap are used to transform the success value, mapError and flatMapError are used to transform the failure value.
Finally, in Moya 13 the deprecated property validate  of TargetType has been removed in favor of validationType. Maybe your issue with the error 400 is from there? Can you show us your implementation of TargetType?


[JSON spec] sync spec files

This PR syncs the JSON spec files with the v8.11.0 Elasticsearch tag.

Yep its a direct copy of the spec files from the Elasticsearch repo with the exception of _common.json which shouldn't be copied, make contrib takes care of reformatting the JSON files and regen the API.


12.5, crash

Probably they change something in the game packets

Should be fixed after #11 and #12 ?

Yes, thanks you sir 😊


Issue with hitting return

Please see https://github.com/froala/meteor-froala/issues/20 not sure if should have posted here instead?

Hi,
Unlikely to be related to this package, as its code does not have any
special 'enter' key handling.
Have you experimented with FE's 'enter' option?
On 28 Jan 2016 11:49 a.m., "adamgins"<EMAIL_ADDRESS>wrote:

Please see froala/meteor-froala#20
https://github.com/froala/meteor-froala/issues/20 not sure if should
have posted here instead?
—
Reply to this email directly or view it on GitHub
https://github.com/froala/froala-reactive/issues/26.

Closed
https://github.com/froala/meteor-froala/issues/20#event-539096811


PBR hair shader

Karis describes a real-time PBR hair shader in SIGGRAPH 2016 which we can adapt to Godot.

Looks really cool.
Would be amazing to have that in godot too.

I added anisotropy for this stuff, but that shared seems pretty cool.
I also just fixed light shaders, so it's now possible to write a custom
shader for a material, may not be necessary to add it as built-in.
On Sun, Oct 1, 2017 at 7:03 PM, Timo<EMAIL_ADDRESS>wrote:

Looks really cool.
Would be amazing to have that in godot too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/11759#issuecomment-333410250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z213IWeNAut9jKyAV0BK7jlMiws7_ks5soAwkgaJpZM4PqCrY
.

With anisotropy it looks like a nice shader for toon/anime style hair but their is actually physically based, with terms for R, TRT, and TT (multiple transmissions and reflections), so I really think it'd be a nice addition complimenting subsurface scattering to get a physically-correct looking humans and animals

Anisotropy essentially just gives something similar to the R term for single reflection

Not to mention they refer to mobile so it's probably fast enough to fit in Godot's overall choices

Heh "mobile" for Unreal is relative, they mostly focus on the high end
section of it.
In any case, it should be interesting, if you want to test it, to use the
new light shader feature.. I wonder how that could work and if exposes
enough for something like this..
On Sun, Oct 1, 2017 at 7:38 PM, Ferenc Arn<EMAIL_ADDRESS>wrote:

Not to mention they refer to mobile so it's probably fast enough to fit in
Godot's overall choices
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/11759#issuecomment-333412120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z26hQYPX39WHQCvjzf9GtB3wv-xBrks5soBRigaJpZM4PqCrY
.

Ah didn't know that!
We should be able to add a HQ setting for it like as in ssurf code, which would turn off, let's say TRT for exampe.
Yeah I'd like to test it on mobile once I prepare the code although might take me a while I'm still trying to get an overall sense of scene.glsl while reading literature

This guy (Karis) is super sloppy in slides and presentation. In N_R, I have no idea what h in attenuation function is, and it doesn't even appear on the right hand side. In the remainder, no idea what Φ(p,h), μa, p are.
His talk is equally unhelpful because he's just basically saying "just see the slides".
I'll check references sometime in the future, hoping that he used their notation for those.

I'll close this as an hair shader can be provided by a third party on the asset library. The Anisotropy property in SpatialMaterial can be helpful here.


I can't setup serverless middleware

I have function
getCategories:
    middleware:
      pre:
        - ./src/middleware/auth.middleware
    handler: ./src/handlers/categories/getAll.handler
    events:
      - http:
          path: /api/categories
          method: GET
          cors: true

src/middleware/auth.ts
export const middleware = async (event: any, context: any) => {
	try {
		console.log("hello from auth middleware");
		console.log(event);
		console.log(context);
	} catch (err) {
		console.log(err);
	}
};

when i trigger my function it ignores the middleware

Hi @salamat9 ,
How are you triggering your function?
Did you check the code that was publish to AWS?
Did it include the middleware?


Update miniscript, rpc references

updates miniscript link to miniscript topic
updates rpc base url to 0.20

If there is a cleaner way to do # 1, please opine, @harding

Untested ACK.  # 1 looks perfect to me.

I think https://github.com/bitcoinops/bitcoinops.github.io/blame/a1d67247e742f839a4354a27ca15b63d6d6b9f07/_posts/en/newsletters/2019-08-28-newsletter.md#L86 is the only place where the new miniscript link makes the text incorrect. You could fix that by changing the text to say 'see our miniscript topic page' or similar.

Pushed a commit to implement @jnewbery 's suggestion (good idea!).