regal.ast.name replaced by regal.ast.ref_to_string

I recently upgraded from regal 0.22.0 to 0.26.1 and my custom rule that was using regal.ast.name started throwing the following error
regal lint services/ policies/
error(s) encountered while linting: failed to lint using Rego rules: failed preparing query for linting: 1 error occurred: /<my-dir>/.regal/rules/custom/my_custom_rule.rego:20: rego_type_error: undefined function data.regal.ast.name

I had to replace this with regal.ast.ref_to_string(rule.head.ref)
Saw this was changed in this commit but not called out in any release notes that I saw.
Just creating this issue in the hopes that it saves someone else some time.
Before
import data.regal.ast

report contains violation if {
	some rule in input.rules
        ast.name(rule) in {"my-name"}
}

After
import data.regal.ast

report contains violation if {
	some rule in input.rules
        ast.ref_to_string(rule.head.ref) in {"my-name"}
}

Hi there!
And thanks for filling this. I was just thinking about the many number of changes we’ve done to the Rego library recently, including even the AST JSON format(!), and wondering what the impact might be. While I do think we need that flexibility still for a while, we could certainly list any changes to the Rego lib in the release notes. We’ll do our best to do that from now on!

No problem and wanting the flexibility makes total sense. I also had a moment of "why was I using an undocumented function" but the docs do mention to read the code so calling out breaks in change notes could be useful.
Thanks!

No, you're absolutely right! The Rego library is pretty well-documented in code, but not so much when it comes to how / if one should use it. I've updated the docs on custom rules today to better reflect current Regal: https://github.com/StyraInc/regal/pull/1079
Also mentioned what to expect about the Rego library right now. The ambition is definitely to get that stable sometime soon, and to provide proper API docs for custom rule authors. In the meantime, I'd love to learn more about what type of custom rules you have, and if/how we can support you with that.

Thanks! For a bit of context on how I'm using it. We use OPA as an external authorizer for Istio. Our typical rules look something like this
# Allow users to get their own accounts
allow {
	api_version == "1"
	method == "GET"
	path = ["account", account_id] # account_id taken from JWT
	groups["members"]
}

The api_version part of the rule was something we added and easy to miss so we added a custom rule that ensures everyone is including a check for that in their rule.
I could see us adding another couple rules to ensure that we always check the following as a baseline

API version (in our case taken from an HTTP header)
HTTP method
Path
Groups you're a part of (in our case we use AWS cognito so this is checking which cognito groups you are a part of)

My custom rule looks like the following
# METADATA
# description: Use api_version in rules
# schemas:
# - input: schema.regal.ast
package custom.regal.rules.custom["use-api-version"]

import rego.v1

import data.regal.ast
import data.regal.result

# METADATA
# description: Allow access to a URI if the service rules permit
# entrypoint: true
report contains violation if {
	ast.package_name == "service.authz"

	some rule in input.rules

	ast.ref_to_string(rule.head.ref) == "allow"

	not has_api_version_term(rule.body)

	violation := result.fail(rego.metadata.chain(), object.union(
		result.location(rule),
		{"description": "allow rules should be written using data.http_request.api_version"},
	))
}

has_api_version_term(statements) if has_api_version_strict_equal_term(statements)

has_api_version_term(statements) if has_api_version_in_set_term(statements)

valid_api_version(version) if {
	regex.match(`^[\d]+$`, version)
}

api_version_imported if {
	# import is a reserved keyword
	some import_statement in input.imports
	import_statement.path.type == "ref"

	count(import_statement.path.value) == 3

	import_statement.path.value[0].type == "var"
	import_statement.path.value[0].value == "data"

	import_statement.path.value[1].type == "string"
	import_statement.path.value[1].value == "http_request"

	import_statement.path.value[2].type == "string"
	import_statement.path.value[2].value == "api_version"
}

valid_api_version_reference(term) if {
	term.type == "var"
	term.value == "api_version"

	# regal ignore:external-reference
	api_version_imported
}

valid_api_version_reference(term) if {
	term.type == "ref"
	count(term.value) == 3
	term.value[0].type == "var"
	term.value[0].value == "data"

	term.value[1].type == "string"
	term.value[1].value == "http_request"

	term.value[2].type == "string"
	term.value[2].value == "api_version"
}

# Tests for api_version == "1" (or any number)
has_api_version_strict_equal_term(statements) if {
	some statement in statements
	count(statement.terms) == 3

	statement.terms[0].type == "ref"
	count(statement.terms[0].value) == 1
	statement.terms[0].value[0].type == "var"
	statement.terms[0].value[0].value == "equal"

	valid_api_version_reference(statement.terms[1])

	statement.terms[2].type == "string"

	valid_api_version(statement.terms[2].value)
}

# Tests for api_version in {"1", "2"} (or any set of numbers)
has_api_version_in_set_term(statements) if {
	some statement in statements
	count(statement.terms) == 3

	statement.terms[0].type == "ref"
	count(statement.terms[0].value) == 2

	statement.terms[0].value[0].type == "var"
	statement.terms[0].value[0].value == "internal"

	statement.terms[0].value[1].type == "string"

	# this value seems to just be named member_2?
	statement.terms[0].value[1].value == "member_2"

	valid_api_version_reference(statement.terms[1])

	statement.terms[2].type == "set"
	count(statement.terms[2].value) > 1
	not any_api_version_invalid(statement.terms[2].value)
}

any_api_version_invalid(api_version_values) if {
	some api_version_value in api_version_values

	not valid_api_version(api_version_value.value)
}

All to say, this rule is in the interest of providing guardrails to most developers who are authorizing new endpoints so that they don't miss something that they should be checking 99% of the time.
This rule was very much me hacking things together so I'd be curious to hear if there are simpler ways to get done what I am going for, and also if things like assuming a node in the AST is always called "member_2" is a totally insane thing to do

Awesome! And that's a perfect use case for Regal 👍
Code looks good too. Some suggestions, if you're interested :)
Although I guess I shouldn't recommend our unstable API 😆 I don't see these functions as likely to change though...
api_version_imported if {
	# import is a reserved keyword
	some import_statement in input.imports
	import_statement.path.type == "ref"

	count(import_statement.path.value) == 3

	import_statement.path.value[0].type == "var"
	import_statement.path.value[0].value == "data"

	import_statement.path.value[1].type == "string"
	import_statement.path.value[1].value == "http_request"

	import_statement.path.value[2].type == "string"
	import_statement.path.value[2].value == "api_version"
}

Could be simplified to:
api_version if ast.imports_has_path(input.imports, ["data", "http_request", "api_version"])

valid_api_version_reference(term) if {
	term.type == "ref"
	count(term.value) == 3
	term.value[0].type == "var"
	term.value[0].value == "data"

	term.value[1].type == "string"
	term.value[1].value == "http_request"

	term.value[2].type == "string"
	term.value[2].value == "api_version"
}

Could use the beforementioned ast.ref_to_string here:
valid_api_version_reference(term) if {
	term.type == "ref"
	ast.ref_to_string(term.value) == "data.http_request.api_version"
}

This double negation..
not any_api_version_invalid(statement.terms[2].value)

..could probably be replaced by an every:
every item in statement.terms[2].value {
    valid_api_version(item.value)
}

About these...
# regal ignore:external-reference

Yeah, we have plenty of those ourselves in the Regal codebase. Next version we'll make this rule a little less annoying :) https://github.com/StyraInc/regal/issues/1002#issuecomment-2332642765
If you're not already there, join the #regal channel in our community Slack! Great to have some place other than issues to talk.

thank for for the feedback! very happy to replace what I have with a simpler + more concise alternative

👍 I saw now that I forgot to answer this

This rule was very much me hacking things together so I'd be curious to hear if there are simpler ways to get done what I am going for, and also if things like assuming a node in the AST is always called "member_2" is a totally insane thing to do

That is a totally sane thing to do :) In the AST, there are no "operators" as they all get rewritten to built-in function calls. So "foo" in ["bar"] gets rewritten to internal.member2("foo", ["bar"]), 1 + 2 to plus(1, 2), and so on ... see the builtins file in the OPA repo for the full list (search for "infix" to see what all operators translate to).


Add workers rules

This implements a new rule for analyzing the limit on the number of workers, which in many scenarios, can compromise the stability of the server while it is expected to be scalable to chaotic scenarios.
See the image below;

Note that before ~9:30 am the CPU was below the limit, however the number of workers had already reached 100%, causing the following SQL error:

The request limit for the database is 600 and has been reached.
See 'https://docs.microsoft.com/azure/azure-sql/database/resource-limits-logical-server' for assistance

So I implemented a new rule that takes the average amount of workers and then scales up when one of the CPU or Workers conditions is needed and scales down when both conditions are met.

@microsoft-github-policy-service agree


how to fuzz unverified contract, using local bytecode and abi

how to fuzz unverified contract?
in this case, i only have abi and bytecode of the contract

file Contract.abi
file Contract.bytecode

something like this?
ityfuzz evm --bytecode-file Contract.bytecode --abi-file Contract.abi

If its deployed on-chain already, you can directly fuzz it by forking. Example: https://docs.ityfuzz.rs/tutorials/exp-hacking-bego


When additional details are opened and no categories have been selected, default attributes should be shown

Tracked by #12

Implemented this task.
{t:40}


Incline free functions to avoid redefinition errors when linking

I was getting "duplicate symbol" errors because multiple .cpp files in the same translation unit were defining the same symbosl and they were clashing. As far as I'm aware, inlining those functions is the best way to ensure those collisions don't cause errors.
Maybe let's move more of the implementation details to .cpp files so that these considerations don't have to be made and to save on compile time for projects that heavily use this library. Header-only makes installation easier but if you're using FetchContent like I am, it makes no different how the cxxcurses::cxxcurses target is built.

@hjaremko Not sure if you automatically get notified of new pull requests so I'll @ mention you just to be sure. I'll stop doing this if you're already getting an email from GitHub about this.

Thanks for taking interest in this project. I don't have any spare time to actively develop this project, but if you want to move implementation to cpp files feel free to. It's ok to ping me, I don't receive any emails.


[firebase_messaging] Activity.getExternalFilesDir causes PlatformException

Hello,
I get this error when calling the configure method and i'm not sure why. I follow the instructions on the readme file. The only difference is i'm using gradle 3.3.0 intead of 3.5.3 because i cant upgrade it yet.
Then, when a notifications message arrives to mi app, and the "onMessage" callback should run, the App closes without any warning or message. The same ocurrs if the app is on background.
However, before i have configured the callbacks (OnMessage, OnBackground...) the messages delivers fine to the notifications system's tray
Am i doing something wrong?
The error log after my call to "configure" method ( the relevant part)
E/flutter (22572): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(error, Attempt to invoke virtual method 'java.io.File android.app.Activity.getExternalFilesDir(java.lang.String)' on a null object reference, null)
E/flutter (22572): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
E/flutter (22572): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:33)
E/flutter (22572): <asynchronous suspension>
E/flutter (22572): #2      FirebaseMessaging.configure (package:firebase_messaging/firebase_messaging.dart:130:16)

I'm using firebase_messaging: 6.0.9
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [VersiÃ³n 10.0.18362.535], locale es-AR)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] Android Studio (version 3.5)
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
[√] VS Code, 64-bit edition (version 1.41.1)
[√] Connected device (1 available)

! Doctor found issues in 1 category.

Build.gradle
dependencies {
 ...
    implementation 'com.google.firebase:firebase-messaging:20.1.0'
}

Same issue here.
I am currently using firebase_messaging 6.0.13 together with location 3.0.2.
If I remove the location dependency from pubspec.yaml I have no error any more.
But I can't find out why.
Has anyone else gained such knowledge?

Closing in favour of trying the latest messaging version which has since this issue was created been heavily reworked to improve it along with detailed documentation: https://firebase.flutter.dev/docs/messaging/overview
If you still have a problem please raise a new GitHub issue with up to date information and code snippets if possible. Thanks.


Docs/user classes

📚 Context
https://github.com/streamlit/streamlit/pull/7408 added Enum coercion to streamlit as a partial fix for a class of commonly-reported issues on the Streamlit bug trackker having to do with un-intuitive interactions between Streamlit's widget state, Python class equality and identity for user-defined classes, and the Streamlit execution model.
As noted in discussions on #7408, the Enum coercion fix is ultimately only able to automatically resolve only some types of these issues -- those involving Enums. Similar problems exist with other user defined classes such as dataclasses or resource managers.
This change adds a new User Classes page which provides advice to users on how to avoid the most common pitfalls of this class of problem, as well as explaining more in detail what the Enum coercion mechanic introduced by #7408 actually does.
🧠 Description of Changes

Added a user_classes.md file
Updated configuration.md and the menu config to point to it.

Revised:

Current:
Page does not exist :)
💥 Impact
Visible to all users in documentation.
Size:

[ ] Small
[x] Not small

🌐 References

https://github.com/streamlit/streamlit/pull/7408

Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.

Thanks @Asaurus1! Since we're just heading into the holiday break, it might take me a few weeks to look at this closely. A quick note off-hand: In the Streamlit docs, a "user" is someone viewing an app as opposed to the person developing an app, often "you." (At least, that's the intended standard. 😄) We'll probably want to avoid "user class" or "user-defined class" since it feels a little off for that reason. Maybe we'll go with "developer-defined classes" or "custom classes" but feel free to share your thoughts, too. I'm excited to dig into this. Happy holidays!

@sfc-gh-dmatthews thanks! Happy to contribute. It's been a busy weekend but I should have some time to work on this in the next few days. You're also welcome to make any corrections you see fit -- I just don't know if that screws with the approval process having a committer also being a reviewer.

@Asaurus1 I've got lots of people around here who can bestow upon us the coveted green check, so no worries there. 😁 I'll leave the PR with the comments for the rest of the week and circle back this coming Monday. I can take care of anything left over or whatever you didn't have time to get to. Thanks!

Sorry I couldn't get back to this last week because of the release, but I'm circling back now. 😄

Ok! I've just finished reviewing and editing everything. This really is great and I love your diagram; it's so pretty! However, I trimmed it out with a chunk of content in the "Class Redefinition" section since we want to avoid getting too far into the weeds. So even though you had a lot of really good things written out, I did condense that part.
There's a plan to have a developer-focused wiki in the future; that may be a good place for some deeper exposition. I just wanted to make sure there was a clear focus on the solutions here. I updated the general guidelines/patterns to try and have a consistent "broken" example that gets "fixed." The readers should be able to execute the snippets to see how each one does (or doesn't) work to help make it clear.
I'll just be giving it another proof read in the morning so this should be merged within a half a day.
Thanks again for the wonderful contribution!

Great! Thanks so much for the help.

@sfc-gh-dmatthews love the edits <3 -- they make it so much clearer than my initial draft. Looks great!

@sfc-gh-dmatthews something is funky with one of the titles on the page on my mobile devide.
Samsung Galaxy S21, Opera browser v 80.4.4424

Thanks for reporting @Asaurus1. I've moved the comment to a new issue. It looks like the code text is displaying as a block so I'll take a look at that today.


tf-nightly prints WARNING:tensorflow during import tensorflow

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.14.0-dev20230706
Custom code
Yes
Python version
3.11
Current behavior?
import tensorflow prints warnings which cannot be disabled with os.environ['TF_CPP_MIN_LOG_LEVEL'].
Standalone code to reproduce the issue
python -m venv tf
source tf/bin/activate
pip install tf-nightly
python
>>> import os
>>> os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
>>> import tensorflow
WARNING:tensorflow:From tf/lib/python3.11/site-packages/tensorflow/python/ops/distributions/distribution.py:259: ReparameterizationType.__init__ (from tensorflow.python.ops.distributions.distribution) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use `tfp.distributions` instead of `tf.distributions`.
WARNING:tensorflow:From tf/lib/python3.11/site-packages/tensorflow/python/ops/distributions/bernoulli.py:165: RegisterKL.__init__ (from tensorflow.python.ops.distributions.kullback_leibler) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use `tfp.distributions` instead of `tf.distributions`.

Hi @lutzroeder ,
I have replicated the reported behaviour and attached logs below.
(bazel) suryanarayanay@surya-ubuntu20:~$ python
Python 3.9.16 (main, Mar  8 2023, 14:00:05)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
>>> import tensorflow
WARNING:tensorflow:From /home/suryanarayanay/miniconda3/envs/bazel/lib/python3.9/site-packages/tensorflow/python/ops/distributions/distribution.py:259: ReparameterizationType.__init__ (from tensorflow.python.ops.distributions.distribution) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use `tfp.distributions` instead of `tf.distributions`.
WARNING:tensorflow:From /home/suryanarayanay/miniconda3/envs/bazel/lib/python3.9/site-packages/tensorflow/python/ops/distributions/bernoulli.py:165: RegisterKL.__init__ (from tensorflow.python.ops.distributions.kullback_leibler) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use `tfp.distributions` instead of `tf.distributions`.

These are deprecation warnings to make sure you update to APIs which won't get deleted on the next release. It is not an issue.

@mihaimaruseac the output shows when running import tensorflow and clutters logs even if none of the APIs mentioned are used. The default method to disable this unnecessary log output does not work. That is an issue.

Hi,
You can silence the command line output temporarily while importing the library and then enable it back again.
Below is the code which silences the warning from tensorflow library.
import os
import sys
# silence command-line output temporarily
sys.stdout, sys.stderr = os.devnull, os.devnull

import tensorflow as tf

# unsilence command-line output
sys.stdout, sys.stderr = sys.__stdout__, sys.__stderr__

Running this before import tensorflow works as well.
import logging
logging.getLogger('tensorflow').setLevel(logging.ERROR)

Is it possible to fix the deprecation warning to only show if these types are actually used? Why is this now showing for all users of TensorFlow.

@lutzroeder this does not work for me:

@salcc this would be for @mihaimarusxeac to investigate. Closing issue given no follow up from maintainers.


Feature Request: Display scale compensation

With two displays not having the same scaling the features are different sizes. I have my 5k iMac monitor set to the smallest possible scaling (smallest text – most content) and an external 1080p monitor set to native scale, which makes text and the screensaver content appear much larger on it.
I assume this is due to the screensaver using pixels/points as reference sizes and not physical size. Maybe an option can be added to correct for that. So if a feature spanning both monitors moves one point/pixel on each monitor the physical distance will be much bigger on the external one.
As you can see in the attached video gif the monitor on the left is scrolling a lot faster than the one on the right.

Hi @Kamik423
That screenshot you sent earlier is from the same system, right ?

To give you an understanding, your 2 screens are seen by macOS as one large virtual screen in points, and the default scaling of each screen (pixels to points) is calculated so it looks "right" even if you have one retina screen, and one non retina screen.
So yes, I'm using that same ratio you see in either Aerial's config panel or System Preferences Display options, and show a portion of the screen based on those sizes as seen. That's why Aerial think your left screen is much smaller than it is (so does macOS). Because that's the only info we accurately have that takes into account position, etc, that's what Aerial uses.

What I am asking for is to add in a field so we can supply the missing physical information by measuring the height of the display or maybe even add a small database of commonly used screens so that can be corrected.

I understand what you want but this is pretty complex to do correctly, as the only accurate information we have is how macOS thinks your screen looks like relative to each others.
I can try to have a look at some point but when you start considering more than 2 monitors, their relative positions, etc, that's a lot of work to get exactly right in all cases, and not something I can add quickly.

I understand. Still hoping for it at some point in the future!
Maybe a visual (approximate) rescale tool, similar to the monitor positioning system dialog, but with resizing and free movement would be the simplest and most user-friendly way to implement that scalably.

Yes you'd need to decouple it all and that kind of UI would work
If you set your iMac scaling to default, their relative size will look the same or close enough, you can check how it works for another user here : https://github.com/JohnCoates/Aerial/issues/194#issuecomment-491516236
That info is what I get from macOS. I can separately get for each screen an estimation of their size in centimeters but that doesn't take into account positionning so that's why you'd need to have something to set that too.
I'm not saying never, but right now I'm more in firefighting more than anything because of Catalina. I marked this as an enhancement at a future point to have a look, but I don't want to get your hopes up that it will come in next build ;)

No pressure – I am just glad your are making this at all. Keep up the great work and extinguish those fires!

once again.. you have to do what Adobe does for photoshop and its other professional apps
you have to be able to input the precise dpi of the monitors so that for example a 100x100 px block drawn across 2 different monitors of 2 different physical sizes and DPI are of the same physical height


Clean header search paths and make debug and release paths the same

Fixes #4

Thanks for fixing this and sending a PR.

Happy to help.
On Tue, Jul 12, 2016 at 10:53 AM Daniel Basedow<EMAIL_ADDRESS>wrote:

Thanks for fixing this and sending a PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dbasedow/react-native-webp/pull/5#issuecomment-232125889,
or mute the thread
https://github.com/notifications/unsubscribe/AA8UNa2iqYbljogy2BhwNA5v8aPbXKhkks5qU9SkgaJpZM4JIeO4
.


Tomcat v6 end of life  2016-12-31

Tomcat v6 is end of life soon.
When I try to run this role it fails as the YUM package isn't found.
[vagrant@localhost ~]$ sudo yum install tomcat6
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.supremebytes.com
 * epel: mirror.cs.ucsb.edu
 * extras: mirror.supremebytes.com
 * updates: mirror.keystealth.org
No package tomcat6 available.
Error: Nothing to do

ref: http://tomcat.apache.org/tomcat-60-eol.html

Yeah, I don't actually use this role anymore either... so we should probably put a big DEPRECATED notice on it somewhere.

What role do you use now?
BTW... working from your Ansible for DevOps book.  Thank You!

@ilessing - In the latest book revisions (posted first to LeanPub, then quarterly to iBooks and Amazon, as well as to published hardcopy revisions), I am using Solr's built-in Jetty server with Java directly—see updated example code here: https://github.com/geerlingguy/ansible-for-devops/tree/master/solr

(Therefore I don't have any personal projects where I need to use Tomcat :)


#167319004 An API endpoint to reset password -- [persisting data to DB]

What does this PR do?
An API endpoint for users to reset a password
Description of tasks
The following endpoint should be working;
PATCH /api/v1/resetmail/:user_id
after

creating an endpoint to allow a user reset password
installing node-mailer, socket.io and ejs for email facilitation
adding a validation to handle errors
adding a route to access the endpoint
writing unit tests for the endpoint

How should this be manually tested/checked?
After cloning this repo, cd into this project, run it by typing the command npm start, and test for the particular endpoint on postman, using localhost:5000/api/v1/resetmail/:user_id
For the test, run npm test
Any background context you want to provide?
While testing, if you encounter any error and error messages, properly follow the error guidelines to get it working, this is so because the endpoint is well validated.
What are the relevant pivotal tracker stories?
167319004

Codecov Report

Merging #62 into development will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           development    #62   +/-   ##
==========================================
  Coverage          100%   100%
==========================================
  Files               14     14
  Lines              350    407   +57
==========================================
+ Hits               350    407   +57

Impacted Files
Coverage Δ

SERVER/Routes/index.js
100% <100%> (ø)
:arrow_up:

SERVER/Tests/usersTest.js
100% <100%> (ø)
:arrow_up:

SERVER/DBconfig/index.js
100% <100%> (ø)
:arrow_up:

SERVER/Controllers/users.js
100% <100%> (ø)
:arrow_up:

SERVER/Middleware/validateUsers.js
100% <100%> (ø)
: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 d9ef119...2af8016. Read the comment docs.


[Feature request] Offline transactions?

Currently it seems like it's impossible to make a transaction without internet. This totally makes sense, but personally I often don't have data as I'm doing a transaction (I don't have a data plan).
This is probably quite hard to implement, since you need to figure out when to submit further transactions etc.. But I'd be really grateful!
Thank you for the great app!

I was able to do that using https://github.com/cyxou/firefly-iii-telegram-bot

Would wrapping this function in a helper
https://github.com/watertrainer/waterfly-iii/blob/e6516a5a3b65c52b45b793c9b46483075d44f453/lib/generated/swagger_fireflyiii_api/firefly_iii.swagger.dart#L5064-L5073
storing the transactions if the future was unsuccsesfull using https://pub.dev/packages/flutter_secure_file_storage would make storing transactions possible, wouldn't it? I'm not too sure what the best play is regarding uploading. Having the app try to sync while running seems like wasted resources, maybe posting a notification and asking the user when to sync?

I'm still trying to figure out how to detect if the application is online or offline, so it can decide in which "mode" to start the transaction page (and maybe even other pages in the future). Detecting for a positive connection is quite easy, as you can just update on each succsessfull response in the chopper response interceptor. I couldn't find an easy way to check for a disconnect though, there are two possibilities I saw, which I'm not to sure which one to pick:

There could be wrapper for all api calls, which detects disconnection by calling on error on all the futures. Many api calls would need a wrapper anyway to return the stored values, so the extra code wouldn't be as big, but there would probably still be lots of exxra code
Something like this https://stackoverflow.com/questions/49648022/check-whether-there-is-an-internet-connection-available-on-flutter-app, which would be easier (changing google.com to the firefly url), but adding a extra dependency.


Refactor paging to be more user friendly

This PR does the following:

Adds PackageTag.topic
Replaces packageNameCompletion() with the correct implementation (probably a breaking change?)
Adds packageNames() to get all package
Handle paginated results from packageNames() call. The nextUrl is currently null but it might not always be
Adds a fetchAllPackages  method so that developers don't have to handle recursive paging themselves if they want all the results for a given query
Fixes a test

The package metrics test is failing because packageCreated and packageVersionCreated are no longer present in the returned json. Should we remove these fields? Or make them nullable? That would definitely be a breaking change.

Welp this turned into a lot more than I had originally intended, but I need all of this functionality. If you don't want to take this PR I understand since I kind of rewrote the whole codebase, but I think using freezed is much easier to maintain than manually writing all the to/from json, toString, and equality stuff. I tested the packageMetrics endpoint on every package with https://github.com/Rexios80/pub_stats and had no serialization issues. We might want to structure the rest of the pana report with actual objects, but I wasn't sure if that stuff was subject to frequent changes so I just left them as maps.

@Rexios80 I love using Freezed. The problem with using Freezed on a package for other devs is that can cause dependency conflicts that make it a bit more difficult to keep it up to date., especially if we can achieve the same behavior with just a bit more boilerplate.
Also can you update the readme so I can understand the changes in behavior and the methods? Thank you for your contribution.

Versioning issues could happen with any dependency. It's not our job to worry about other packages as long as we are keeping ours up to date.
I will work on the readme when I have time.

I understand but since Freezed is not adding any functionality that we cannot add without it, I believe we can remove it. There are some ide extensions that automatically generate those methods

I'll just maintain my own fork for now. We can revisit this later if I get time.

@Rexios80 if you can just point me at the changes you made for the API improvements, or mayhbe just remove the other changes, I can hopefully be able to bring it in a document it!

The important part is the extra fields from the metrics endpoint


push podspec for 1.1 out to CocoaPods podspec repo

Currently, CocoaPods is reporting 1.0 as the current version of KLCPopup. Could you guys push out 1.1 to CocoaPods?

For reference, I get this error:
[!] Unable to satisfy the following requirements:

KLCPopup (= 1.1) required by Podfile


Removing old modules.

Pull Request Description
What issue does this change request address?
#1806
What are the significant changes in functionality due to this change request?
Fixes test to use module that actually exists on sawtooth and removes old ones that do not exist and are not needed.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Mingw Test on 7816e73 : invalidated by @joshua-cogliati-inl
failed in fetch

Job Test qsubs sawtooth on 7816e73 : invalidated by @joshua-cogliati-inl
failed in set python environment

All green, checklists pass.


Removed scripts from README that are no longer present [skip ci]

These appear to be some leftovers.

Thanks!


[SPARK-17266] [TEST] Add empty strings to the regressionTests of PrefixComparatorsSuite

What changes were proposed in this pull request?
This PR adds a regression test to PrefixComparatorsSuite's "String prefix comparator" because this test failed on jenkins once (https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-sbt-hadoop-2.4/1620/testReport/junit/org.apache.spark.util.collection.unsafe.sort/PrefixComparatorsSuite/String_prefix_comparator/).
I could not reproduce it locally. But, let's this test case in the regressionTests.

Test build #64505 has started for PR 14837 at commit 6add905.

LGTM

Test build #64505 has finished for PR 14837 at commit 6add905.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64505/
Test PASSed.

Thanks. I will merge this and watch the build.


Fixes source map emit for use with gulp-sourcemaps

This PR includes only the necessary changes from https://github.com/jrieken/gulp-tsb/pull/45 to correctly emit source maps that work well with gulp-sourcemaps.
There are several issues with the source map emit provided by gulp-tsb that prevent gulp-sourcemaps from properly handling the output:

Both TypeScript and _gulp-sourcemaps_add a sourceMappingURL comment at the end of the file.
TypeScript's --inlineSourceMap and --inlineSources options conflict with functionality provided by gulp-sourcemaps. When combined this can result in incorrect or inaccurate source maps.
TypeScript's --sourceRoot and --mapRoot options are in direct conflict with the write function used by gulp-sourcemaps that controls path mapping.
Without a --sourceRoot, TypeScript emits all sourceMaps with the "source" property as the file name only, but gulp-sourcemaps expects the "source" property to be relative to the base directory to correctly compute the output paths.
TypeScript's --outDir conflicts with the dest function used by gulp.

The changes in this PR align TypeScript's sourcemap output with that expected by gulp-sourcemaps.

// CC: @jrieken, @joaomoreno, @dbaeumer, @mjbvz
This supersedes the portion of #45 related to sourcemap emit (except the parts relating to single-file output).

@joaomoreno Did source map support, relaying to him


Return error message for config decryption failure

See #1663

Codecov Report

Merging #1667 into master will decrease coverage by 0.05%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #1667      +/-   ##
==========================================
- Coverage   51.73%   51.68%   -0.06%
==========================================
  Files         143      143
  Lines       11394    11396       +2
==========================================
- Hits         5895     5890       -5
- Misses       4589     4595       +6
- Partials      910      911       +1

Impacted Files
Coverage Δ

internal/repository/repository.go
55.93% <33.33%> (-0.32%)
:arrow_down:

internal/backend/s3/s3.go
60.76% <0%> (-2.31%)
:arrow_down:

internal/archiver/archiver.go
64.68% <0%> (+0.21%)
: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 7f8e269...b3e1089. Read the comment docs.


DBZ-2662 Handle ChangeEventQueue by the size in bytes

JIRA

@vanhoale I think the core functionality is fine now. I'd like to ask you for few more improvements

expose the current queue size ans max queue size as JMX metric, see io.debezium.connector.base.ChangeEventQueueMetrics
with the feature above in please please add to one of the connectors a test that will will verify the size of the queue before events are written, when some of them are in it and that the size is zero again when all records were consumed
add new option and metrics to the documentation
remove the Maven dependency and pull the sourcecode into the project as mentioned elsewhere

Thanks a lot for this new feature

@vanhoale I think the core functionality is fine now. I'd like to ask you for few more improvements

expose the current queue size ans max queue size as JMX metric, see io.debezium.connector.base.ChangeEventQueueMetrics
with the feature above in please please add to one of the connectors a test that will will verify the size of the queue before events are written, when some of them are in it and that the size is zero again when all records were consumed
add new option and metrics to the documentation
remove the Maven dependency and pull the sourcecode into the project as mentioned elsewhere

Thanks a lot for this new feature

Thanks @jpechane ! Yes, I will add improvements.

@jpechane should I use caffeine for the CacheBuilder? As mentioned the bug in the code? I also read an article about the guava inspired by caffeine: https://www.linkedin.com/pulse/asynchronous-reload-guava-cache-caffeine-bhanuprakash-devapatla/

No, the caffein version is much slower then the https://github.com/twitter-archive/commons/blob/master/src/java/com/twitter/common/objectsize/ObjectSizeCalculator.java one

@vanhoale can you please explain what is slower? The use of CacheBuilder inside of ObjectSizeCalculator is an unbounded memoizing map, so technically it is unnecessary as of Java 8. That correlates to our compute benchmark, where Caffeine is faster that Guava or using computeIfAbsent directly. The latter only because we avoid the pessimistic internal lock by optimistically performing a lock-free get(key). That same optimization could be applied to remove the cache dependencies.
Or was the comparison against something else?

@ben-manes @vanhoale Interesting discussion, the benchmark looks convincing. @vanhoale Could you please share your experiences?

@vanhoale can you please explain what is slower? The use of CacheBuilder inside of ObjectSizeCalculator is an unbounded memoizing map, so technically it is unnecessary as of Java 8. That correlates to our compute benchmark, where Caffeine is faster that Guava or using computeIfAbsent directly. The latter only because we avoid the pessimistic internal lock by optimistically performing a lock-free get(key). That same optimization could be applied to remove the cache dependencies.
Or was the comparison against something else?

Hi @ben-manes, thanks so much for looking at this, and for the benchmark chart that looks nice!
I have done 2 test versions of ObjectSizeCalculator that is using caffeine and guava, the code is at:
Caffeine:
https://gist.github.com/vanhoale/02cf479ae26c04946251cae645bcc776
Guava:
https://gist.github.com/vanhoale/b12324695b85a4d4731618749330fbb3
The tests are to calculate the average processing time in nanoseconds of the method: ObjectSizeCalculator.getObjectSize. The results are below:
ObjectSizeCalculator with Caffeine:

ObjectSizeCalculator with Guava:

Thoughts/advice?

Thanks @vanhoale. This makes sense because it is not one-to-one, as you added a workaround to a limitation of ConcurrentHashMap. The result being a higher penalty by delegating the compute to a thread pool since CHM does not allow recursive computations. None of the data structures support it, but Guava does work better (it used to deadlock in that case, which I fixed).
// Have to use buildAsync with a synchronous view due to a CHM bug in Java 8.
// See https://github.com/ben-manes/caffeine/issues/89
private final LoadingCache<Class<?>, ClassSizeInfo> classSizeInfos = Caffeine.newBuilder()
        .buildAsync(ClassSizeInfo::new)
        .synchronous();

The alternative would be to either use a racy get-load-put call or to implement locking yourself. The racy approach is probably okay since this has no I/O and should be fast. The manual locking isn't too hard, but adds code complexity. Either way, continuing to use Guava is probably the simplest and best choice. I agree with your decision and thanks for clarifying what the slowdown was due to.

CHM bug

yeah, it seems to be fixed at jdk8_120. Thanks @ben-manes for the explanation

@vanhoale Please check now the content of installation artifacts. It contains guava (which is expected) and then couple of more probably pulled in by Guava. Are they necessary for runtime? If not could you please exclude them in debezium-assembly-descriptors/src/main/resources/assemblies/*?

@vanhoale Squashed and applied, thanks. Could you please also take a look at https://issues.redhat.com/browse/DBZ-2766
I wonder if we could reduce the performance penalty with it or not.

@vanhoale Squashed and applied, thanks. Could you please also take a look at https://issues.redhat.com/browse/DBZ-2766
I wonder if we could reduce the performance penalty with it or not.

thanks @jpechane ! Yes, I can take a look at it!

@vanhoale Hi, I've just noticed that metrics are documented but ot the config option itself. Could you pleas eprepare a new PR with docs update? Thanks


Needs some documentation to gain acceptance

Unless you happened to have used it at Y! (and even if you have)  getting libcrange going can be very difficult.
We need a:

quick getting started guide
build instructions
config file instructions
range syntax documentation
how to extend with modules

+1 for more docs. I'm an ex-Yahoo! and I am having a tough time getting this working too.


viewing GC details from Azure Portal

adding just the portal compliance details view

@mgreenegit : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.


Implement regex filter as iterator

Provides a new filtering path .Regex. The implementation largely mirrors that of .Filter

Well done! Looks much better now. Few minor changes (which I should apply to Comparison also) and I'll merge it.
Also please add Regex to Gremlin, or as an alternative, I can add it after the merge.

Reviewed 5 of 5 files at r1.
 Also, remove " around Regex to match Go convention for comments.

graph/iterator/regex_iterator.go, line 72 at r1 (raw file):

func (it *Regex) Reset() {
	it.subIt.Reset()

Also set a it.result and it.err to nil

graph/iterator/regex_iterator.go, line 102 at r1 (raw file):

func (it *Regex) Result() graph.Value {
	return it.result

We can potentially drop it.err and it.result and return them from sub iterator directly.

graph/iterator/regex_iterator.go, line 180 at r1 (raw file):

func (it *Regex) Size() (int64, bool) {
	return 0, true

Returning true here means that result is exact. Optimizer may think that this iterator is empty and remove it from the tree. I should fix this for Comparison also.

Comments from Reviewable

I went for the 'set err/result to nil' approach instead of returning directly from subiterator. I feel like I would need to do some more comprehensive tests for that case.
If you could add the Gremlin API that would be great - I'm not too familiar with the code there and unfortunately quite time constrained at the moment.

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


How to make a condition for the absence of a property?

How to make a condition for the absence of a property?
Something similar to
{
    properties: {
        name: {$exists: false}
   }
}

{not: {required: ['name']}}


Add new http(s) driver using the Requests library.

This is an alternative http(s) driver that uses Requests
(https://github.com/rmccue/Requests) instead of Guzzle.
I don't really know composer all that well to know how optional libs would fit in there. Hints welcome :)
We've been using this driver in multiple projects in production settings for close to a year now, no issues at all.
However, we're also mostly using it in a write workflow.

@pprkut could you perhaps add some benchmarks ?

I can certainly try. What would you be interested in seeing in those? Just request times? Memory usage?
FWIW, our interest in using Requests instead of Guzzle wasn't really performance related, but centered around Requests having less dependencies and not using PSR-7.

@thecodeassassin just revisiting this from our TODO list. What kind of benchmarks would you want?

The curl driver works good enough for us, so this is no longer needed.


Onboard dependabot workflows

Generated by https://github.com/adevinta/vulcan-cicd/actions/runs/6183231035

Updated by https://github.com/adevinta/vulcan-cicd/actions/runs/6185344163


Expose CustomAppRoot in GeoParser's Girder plugin

Adding exposed = True as per https://github.com/Kitware/minerva/blob/master/server/loader.py

https://github.com/MBoustani/GeoParser/commit/c5c78ebf60dd78a38e8f9ca66ca8e036560107a4?diff=unified


New version: Pathogen v0.3.2

Registering package: Pathogen
Repository: https://github.com/jangevaare/Pathogen.jl
Created by: @jangevaare
Version: v0.3.2
Commit: ac583407d6d50516d018bcf82b80335a343642dd
Reviewed by: @jangevaare
Reference: https://github.com/jangevaare/Pathogen.jl/commit/ac583407d6d50516d018bcf82b80335a343642dd#commitcomment-36199814

Do you want to add the bounds? https://github.com/bcbi/CompatHelper.jl might be of interest. [noblock]

If you are dropping support for Julia 1.0, then you need to bump your minor version number, not the patch version number.
[noblock]

@DilumAluthge the previous patch version was julia = "≥ 1.1.0"

[noblock]
According to https://github.com/jangevaare/Pathogen.jl/blob/v0.3.1/Project.toml it was:
[compat]
julia = "≥ 1.0.0"

This can be closed now


[google_maps_flutter] Fix LatLng returning slight different values

Description
Previously
LatLng location = LatLng(50, 6.123456789);
print(location.latitude.toString() + ', ' + location.longitude.toString());

would produce:
50, 6.123456788999988

Now it produces:
50, 6.123456789

I signed it!

this PR needs tests.

@google-admin @joaoatgoogle @mravn-google
Google Map Android provides KML support in maps.
https://developers.google.com/maps/documentation/android-sdk/utility/kml
How we can use KML support in flutter ?

@zubyf09 please create a new issue here https://github.com/flutter/flutter/issues/new

Since it's been almost a month and the committer has not addressed the comments. I'm closing the pull request. Please re-open a new one when you are ready. Thanks!


Fix: #135 -- Run travis tests

Add func setDriverPaths to check if the driver paths have been set, and
if they have not been set, set them

@minusnine Just a heads up. I have already made the requested changes.

Thanks! Sorry for the delay.

Codecov Report

Merging #137 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #137   +/-   ##
=======================================
  Coverage   47.88%   47.88%
=======================================
  Files           4        4
  Lines         969      969
=======================================
  Hits          464      464
  Misses        414      414
  Partials       91       91

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 5ee96d6...af982db. Read the comment docs.

No worries


Remove NGSIv1 references in the Tour Guide

once Context Providers are fully supported in NGSIv2, any reference to NGSIv1 shall be dropped.
In the meantime perhaps we can remove all NGSIv1 and leave only the context provider related content. Or even drop it now as @jason-fox is working on
https://github.com/Fiware/tutorials.Context-Providers
@fgalan opinions?

I fully support removing any reference to NGSIv1 in any piece of documentation, Tour Guide included of course :) Please, go ahead. Put me in CC in the PR doing so if you want me to have a look to the changes.

fixed.


Finding out the firmware version from a coredump elf (IDFGH-13255)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
We have collected hundrets of millions of coredump elf files from our ESP32 products around the globe and every time we receive another crash report, we have a hard time finding out which firmware this resulted from (we do some heuristics on the database on what the device reported earlier using websockets).
Is there some easy way to find out the exact project_name and version of the firmware from inside the coredump elf?
Or can we somehow embed custom information like customer name, serial number, firmware project_name and version directly into the elf?

Core dump ELF files contain the SHA-256 sum of the IDF applications. You can get it using the esp_core_dump_get_summary API. Does this work for you?


[EN DateTimeV2] Fixed inconsistency between English and Spanish in handling "from" and issue with list (#2287)

Moved support for ranges like "from 2015" from Standard to Experimental mode in analogy with Spanish behaviour (#2287).
Added pattern "from 2015 and 2016"  to PotentialAmbiguousRangeRegex (FromToRegex) to avoid considering 'from' a modifier in this case.
Updated affected test cases in DateTimeModel and moved the originals to DateTimeModelExperimentalMode.

Currently fails for "3 minutes from today", which ideally should be a single entity in either mode.
But it's ok to be two separate entities for now.

Modified test cases in Merged according to the corresponding case in Model.
Strangely in Visual Studio the original test cases (with extracted text 'from today') pass (in Merged) and the updated cases (with extracted text 'today') fail.


Increased code coverage 100%

Increased code coverage of the test class and it is now covering 100% code now.


feat: add search to docs

@ryscheng I think the PR is failing because I included the yarn.lock file. Would you mind having a quick look?

Couple comments on this PR

There's a bunch of docs changes in the PR that I don't think are relevant to search. In service of clean PRs, I made a new one here. https://github.com/opensource-observer/oso/pull/730
You don't need to install the algolia preset, we use the classic theme that comes with it automatically. (see docs)
The way Algolia works, is someone has to build the index. In our main app, I have to pull the data from the database. For documentation, Algolia has a nice docsearch program that automatically indexes your website for you, as long as it has real content and is open source (see docs). So all you need to do is apply to the program, which I've already done.


Use target_include_directories to publicly expose include dir

To use discord-rpc in a project before this change:
add_subdirectory(discord-rpc)
target_include_directories(${PROJECT_NAME} PRIVATE discord-rpc/include)
target_link_libraries(${PROJECT_NAME} PRIVATE discord-rpc)

To use discord-rpc in a project after this change:
add_subdirectory(discord-rpc)
target_link_libraries(${PROJECT_NAME} PRIVATE discord-rpc)

Hey @p0358 , could you take a look at this when you get a chance? Thanks!

@p0358 gentle ping

Aaa, sorry for the big delay. Yeah this seems to be fine.


Maven and JCenter publish

Status
READY
JIRA Ticket
SPACON-386
Description
Publish android artifacts to maven and jcenter
Todos

[ ] Tests
[ ] Documentation
[ ] License

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git fetch --all
git checkout <feature_branch>
./gradlew connectedCheck

@boundlessgeo/spatial-connect

👍


Bug Fixes

Closes #555
Closes #547
Closes #546
Closes #545
Closes #539

Building in unstable now.


Couple of bugs - referring to different keras versions?

Hi,
I had to fix a couple of things in the code , I presume keras latest version changed some variable definitions, but I haven't tried with older keras versions so I'm not sure about that.
Anyway, in the Wasserstein gan code:
in utiles/data_utils.py the beta1 parameter to the Adam solver needs to be changed to beta_1
in /model/models_WGAN.py happens an error in conv2d_init function  caused by dim_ordering variable. putting dim_ordering=None seems to fix it, so I suggest:
def conv2D_init(shape, name=None,dim_ordering=None):     return initializations.normal(shape, scale=0.02, name=name)

You're right about that !
My plan is to wait for keras 2 which should be released shortly. The API will hardly change from there so I'll refactor all the code

Keras 2.0.1 is here! Please help, I have been trying to train model since 3 days but there are so many errors.

I refactored my actual implementation, heavily based on yours but on a jupyter notebook.
Anyway, I encountered a very big problem: I never managed to get nice output with batchnorm mode 0 and 1.
I get output image varying with the input noise only when using batchnorm mode = 2. (applying batch statistic both on training and on testing, so no moving average)
The big problem is there: keras 2.0 removed batchnorm mode 1 and 2!
I don't see any viable option of using keras 2.0 on our GAN.
Do you encounter the same problem with batchnorm mode 0 and 1?

I'm mostly using pure tensorflow at the moment so that I have better control over the whole pipeline.
Anyway, there still seems to be a couple of bumps on the road to keras 2 (running my benchmarks, it seems that the new NCHW data format for tensorflow is not running as expected) so I'll wait a bit more before updating the keras script.
I've seen your issue on keras repo so we may also get fchollet's feedback.

I adjusted the small variations needed to run your code on keras 2.0, but still remains the big issue: both on keras 1.2 and on keras 2.0, the Wasserstein GAN ( and I suppose the traditional GAN too) doesn't work when using batchnorm mode=0 on the generator.
I updated the issue on keras repo but looking at the amount of bugs accompanying the new keras version I do not expect a fast solution.
I understand your point of view about tensorflow better control over the whole pipeline, still it will be a pity if you will not update anymore your "recent papers implementations" on keras, because I found it a very valuable resource of code on the easiest Deep Learning framework - most of tensorflow unexperienced researchers, like me, would lose a LOT of time on the question "how to code it" instead of "what experiment should I run now" ;)
Anyway, would you mind reporting your finding about GANs and batchnorm mode if you will play with them on tensorflow? I'm curious to see if the batchnorm mode problem is present only on keras or on tensorflow too.

As far as I can tell, the only difference between mode 0 and mode 2 should be at inference time not training time and thus there should not be that many differences during training.
I'll try to re-run a WGAN experiment with keras 2 over the week end.

The problem is not on "training" itself - maybe I have badly explained the issue. The problem happens when, during the training, we plot some of the images from the actual generator, like your code do on the file "current_batch.png"; in this istant we are at inference time, and so there is the different behaviour between mode 0 and mode 2.
So the training is going nicely with both modes, but we cannot get proper output from the generator at inference time with mode 0 (both on keras 1.2 and 2.0, still unknown what happens on tf / torch / pytorch / etc)

Gotcha.
As far as tf is concerned, you pass keywords to tf.contrib.layers.batch_norm to specify whether you're training (i.e. accumulate mean and std dev statistics) or inferring (use the accumulated statistics instead of the current batch statistics). There's a catch in that you may have to manually specify you want the statistics to be accumulated.
I had a look at a full porting to keras 2 and ran into what looks like a nasty BN bug: the discriminator graph should be independent from the generator graph but when training, tensorflow asks for a value for noise_input which belongs to the G graph. This error only occurs when one includes BN layers in the discriminator.
Did you have a similar issue and if yes how did you solve it ?

Again, any update for this issue?  My WGAN generator basically spits put uniform noises and training simply collapsed.

see https://github.com/fchollet/keras/issues/5892


Storybook

Can you help adding story book to this starter kit?
I would like to add it if you point me some direction and do code review :)

@BatuhanW Yes, it should be easy actually:
https://github.com/sysgears/larix/blob/master/packages/zen/docs/programmatic.md


DocumentDB: Expose EnableAutomaticFailover and ConsistentPrefix consistency policy

Switching to latest documentdb management pypi package 0.1.3.
Exposing DatabaseAccount property "enableAutomaticFailover" in the create/update operations
Exposing new consistency policy 'ConsistentPrefix'

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[X] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[X] Each command and parameter has a meaningful description.
[] Each new command has a test.

(see Authoring Command Modules)

Codecov Report

Merging #3153 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #3153      +/-   ##
==========================================
- Coverage   70.57%   70.57%   -0.01%
==========================================
  Files         369      369
  Lines       23907    23911       +4
  Branches     3658     3659       +1
==========================================
+ Hits        16872    16874       +2
- Misses       5959     5961       +2
  Partials     1076     1076

Impacted Files
Coverage Δ

...tdb/azure/cli/command_modules/documentdb/custom.py
20.32% <0%> (-0.34%)
:arrow_down:

...db/azure/cli/command_modules/documentdb/_params.py
73.68% <100%> (+0.95%)
: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 fb15da8...178a297. Read the comment docs.

For your reference: this is the code coverage for document db module: https://codecov.io/gh/Azure/azure-cli/pull/3153/tree/src/command_modules/azure-cli-documentdb/azure/cli/command_modules/documentdb

@troydai @tjprescott only testing changes that are introduced in this PR. Will add more comprehensive tests moving forward.

Thank you.


nested_under and see_instead interaction

I have a document where I want to achieve an index that looks like:
PAIR, see protocol, PAIR
... other entries..
protocol,
   PAIR,

I've come up with a hack but I think it would be better if you could add more formal support for it.
Essentially, I'm using  to create fake index entries like this:
[preprocessor.indexing.see_instead]
"_PAIR_" = "protocol, _PAIR_"

[preprocessor.indexing.nest_under]
"_PAIR_" = "protocol"

Anyway, maybe you could make this a little nicer somehow?

Alternatively, if I had a way to specify the nesting, such as:
{{ni:protocol:PAIR}}
(I assume we'd want hni and maybe nii variants as well?)  this would help.  Or possibly just treat commas in the index as nesting terms?  Although not everyone might want that.

I've generally done this by including repetition in the sub-entries:
[preprocessor.indexing.see_instead]
"PAIR" = "protocol, PAIR"

[preprocessor.indexing.nest_under]
"protocol, PAIR" = "protocol"

giving:
PAIR, see protocol, PAIR
protocol, 1
      protocol, PAIR, 1
      protocol, PUSH, 1
PUSH, see protocol, PUSH

but the repetition/redundancy isn't ideal.
One possible approach might be to remove leading "<head>, " text from any subentry, if the text before the comma matches the head entry.  That should result in:
PAIR, see protocol, PAIR
protocol, 1
      PAIR, 1
      PUSH, 1
PUSH, see protocol, PUSH

(That's probably a smaller/easier change than specifying nesting at the index point, although explicit nesting might be closer to other indexing systems, e.g. AsciiDoc.)

I've put in #6 as something that should hopefully work in the short term, and raised #14 for re-thinking nesting support in general.


Unable to build for Android with versions 1.2.0-alpha01-devXX

I'm currently unable to built for Android using any of the dev builds for 1.2.0-alpha01-devXX, although building for desktop works great.
The issue seems to be in the resolution of some android dependencies with a -debug suffix:
FAILURE: Build completed with 8 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:mergeDebugResources'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:mergeDebugAssets'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

4: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:processDebugMainManifest'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

5: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':common:generateDebugRFile'.
> Could not resolve all files for configuration ':common:debugCompileClasspath'.
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Required by:
         project :common > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Required by:
         project :common > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Required by:
         project :common > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Required by:
         project :common > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Required by:
         project :common > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

6: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:checkDebugDuplicateClasses'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

7: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:desugarDebugFileDependencies'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

8: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android:mergeDebugNativeLibs'.
> Could not resolve all files for configuration ':android:debugRuntimeClasspath'.
   > Could not find org.jetbrains.compose.foundation:foundation-layout-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/foundation/foundation-layout-android-debug/1.2.0-alpha01-dev606/foundation-layout-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.foundation:foundation-layout:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.material:material-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/material-android-debug/1.2.0-alpha01-dev606/material-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.material:material:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.animation:animation-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/animation/animation-android-debug/1.2.0-alpha01-dev606/animation-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.animation:animation:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.runtime:runtime-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/runtime/runtime-android-debug/1.2.0-alpha01-dev606/runtime-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.runtime:runtime:1.2.0-alpha01-dev606
   > Could not find org.jetbrains.compose.ui:ui-util-android-debug:1.2.0-alpha01-dev606.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/ui/ui-util-android-debug/1.2.0-alpha01-dev606/ui-util-android-debug-1.2.0-alpha01-dev606.pom
     Required by:
         project :android > org.jetbrains.compose.ui:ui-util:1.2.0-alpha01-dev606

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/7.0.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 5s
46 actionable tasks: 41 executed, 5 up-to-date

Should be fixed in the next 1.2 dev build

@akurasov it appears there's a small publication bug still. If you look at the pom.xml of foundation 1.2.0-alpha01-dev620, it pulls in the wrong foundation version:
<dependency>
<groupId>androidx.compose.foundation</groupId>
<artifactId>foundation</artifactId>
<version>1.1.0</version>
<scope>runtime</scope>
</dependency>

Link to full pom here

@tunjid what is wrong with it? Currently 1.2.0-dev builds reference 1.1.0 version of Jetpack Compose.

@akurasov oh I see, I thought dev builds used tip of the tree compose versions. For example on desktop I can use some lazy grid apis from the compose 1.2.0-alpha01 just fine.
Thanks for fixing the original issue

Nope, we set this version manually. Actually, you can override it, by just adding JC of required version to the dependencies explicitly. However, keep in mind that it affects only android binaries.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


LICENSE

Which software license is this software distributed under? I think your source code or LICENSE/COPYING file should include the license. Currently as far as I can tell there's a little shield icon in the README.md and that's it.

Added license.


Fix the case sensitivity button in search in High Contrast

Because the Path inside the case sensitivity button is not text, it wasn't getting themed by the Xaml runtime's text style.

name change: done