Prerequisites have insufficient instructions

I am having issues figuring out how to enable the registration campaign feature, in my new tenant. I'm thinking my issue lies in my misunderstanding of the Prerequisites. Some links to explicit documentation perhaps could have been helpful. Here are my questions:
The first prerequisite states that enabling MFA is required, but enabling MFA doesn't seem to be as clear-cut as changing a configuration on a specific page. There seems to be many ways to do this, including: MFA in a conditional access policy, using identity protection, or with security defaults, and there are probably more. Is every way of enabling MFA compatible with this feature? If I'm forcing MFA on the user with every sign-in using conditional access, doesn't that defeat the purpose of leveraging the authenticator app?
What is the simplest way to meet the prerequisite? I am just looking into how to get started.
The user condition is likely no issue, as I haven't configured any authenticator sign-ins yet.
The final prerequisite is also causing me issue.
Going down the 'MFA Registration Policy' path: I'm assuming this meant configuring the Multifactor authentication registration policy under Identity Protection, but turning it on didn't seem to have an effect other than prompting for a phone number; afterward my user would still just sign in.
Going down the 'Authentication Methods Policy' path: I have enabled the authenticator app in the authentication methods with the 'any' setting, but that too doesn't seem to have any effect. It seems the prerequisites for that feature require 'combined registration' to be enabled. But the page I would expect to explain how to see and edit that configuration, doesn't share those details: https://learn.microsoft.com/en-us/azure/active-directory/authentication/howto-registration-mfa-sspr-combined
I do see there that is says it's now the current default, but I assume it might still not be enabled because in the azure portal it states "If your tenant doesn’t yet use combined security info registration, turn it on now – it’s required to use this policy." So since, this doesn't work either, I assume 'combined registration' is not enabled.
Thank you,

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

ID: 1c8810aa-a874-83bd-1ce6-42617b75557e
Version Independent ID: c5c460d5-e255-40a5-a8bf-2d930d39c392
Content: Nudge users to set up Microsoft Authenticator - Microsoft Entra
Content Source: articles/active-directory/authentication/how-to-mfa-registration-campaign.md
Service: active-directory
Sub-service: authentication
GitHub Login: @mjsantani
Microsoft Alias: justinha

@fei0x
Thanks for your feedback! We will investigate and update as appropriate.

@fei0x
To enable the registration campaign feature, you need to meet the prerequisites. Enabling MFA is required, and you can enable it in multiple ways, including MFA in a conditional access policy, using identity protection, or with security defaults. All of these methods are compatible with the registration campaign feature. If you are forcing MFA on the user with every sign-in using conditional access, it may defeat the purpose of leveraging the authenticator app. The simplest way to meet the prerequisite is to enable MFA using security defaults.
Regarding the final prerequisite, you can configure the Multifactor authentication registration policy under Identity Protection to enable combined registration. However, turning it on may only prompt for a phone number, and afterward, your user would still just sign in. Alternatively, you can enable the authenticator app in the authentication methods with the 'any' setting, but that too may not have any effect. The prerequisites for that feature require 'combined registration' to be enabled. You can turn on combined registration by following the instructions in this link: https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-getstarted#enable-combined-security-information-registration. Once you have enabled combined registration, you can then enable self-service password reset and enable Azure AD Multi-Factor Authentication.

@mjsantani
Kindly take a look at this.


Update init.py-line no: 2920, class Command argument message type…

The Command class in init.py uses mavutil.mavlink.MAVLink_mission_item_message for the message type, which uses the less accurate float32 for sending the long and lat parameters. This can be made more accurate if we use the mavutil.mavlink.MAVLink_mission_item_int_message type which uses int32 for sending, and is the recommended implementation. Hence, for the Command class, we have changed the message type to message_item_int since message_item is now depreciated.

Thanks. This looks great, but same fix in #1209 is more complete.


Sync README.md with current version

README.md Maven and Gradle snippets pointed to the last version of dotenv-kotlin, which does not have the Java 8 fixes.
Resolves #55

@all-contributors add @HarryHenryGebel for doc


fix: update font import #269

close #269

:tada: This PR is included in version 7.34.0-next.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.35.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update PHP to recent version?

Hi there,
first of all thanks for the great work!
Is there any chance to get PHP updated to a supported version that is not having a CVSS score of 10/10?
Best
David

Hi,
Gptwol is not using PHP, so it should not be affected by the CVE you are referring to.
However, some high vulnerabilities from python-slim image are corrected in 2.0.5 release
As no vulnerabilities can be fix for now according to dockerhub scout check vulnerability i'm closing issue.

Sorry, not enough coffee in the morning...I was actually meaning Python being present with version 3.11.9


Use gsha256sum instead of sha256sum if it's available.

GNU coreutils are sometimes installed prefixed with 'g', including on macOS with Homebrew and on BSDs.  The README was recently changed to suggest adding $(brew --prefix coreutils)/libexec/gnubin to $PATH (see #75), but this way is better as it works with the default PATH.
Also remove that bit from the README.
(This still requires coreutils to be installed through Homebrew.  #75 originally proposed to use a different utility to compute SHA256 hashes on macOS, but @s3rvac expressed a desire to standardize on coreutils.  Makes sense, but it's still good to minimize the number of manual steps required to successfully build, so I thought this was a reasonable compromise.)

In commit 0f1281e536bfe2e6053f702138114de51066335d, I have updated the installation script to try the following three commands and use the first one that is available: gsha256sum, shasum, and sha256sum. So, in order to install RetDec, GNU coreutils are no longer required. However, GNU coreutils are still needed to run RetDec. So, at least, the installation will be easier. I know that I proposed to standardize on GNU coreutils in #75, but since sha256sum was the only required command, I think it makes sense support the native version as well.
In commit 9b2c10ee96b9664cd91ba1207a2b64ca88ecf9e4, I have updated all the scripts that used readlink to try greadlink first. This simplifies the setting of PATH as GNU coreutils no longer need to appear before the built-in tools (GNU coreutils just need to be available in PATH).
All in all, from what I have observed, there are not many places where GNU coreutils would be required. So, I believe we might be able to get rid of them and use the default versions that ship with macOS. I will happily take a PR for that.


Default target-sqlite database "meltano" conflicts with system database

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1049
Originally created by @DouweM on 2019-09-26 08:46:28

The default dbname for target-sqlite is meltano, at path [project]/meltano.db, which also happens to be the default path of Meltano's system database, which is used to store things like plugin settings and scheduled jobs.
I think we should change the default dbname to warehouse (or something else) to prevent users from accidentally loading arbitrary data into the system database, which may conflict with our system tables now or in the future.

View 10 previous comments from the original issue on GitLab


Only use getBoundingClientRect method instead of both?

As far as I can see, getBoundingClientRect has good enough support to be the only method we use in this plugin.
Cutting the old calculations would reduce the plugin size to about half... Anyone against that?
http://www.quirksmode.org/dom/w3c_cssom.html#getBoundingClientRect

I am all for it! And a friend on the line too

I think what would be good would be two versions, one with both for those who want to support old browsers, and one with only getBoundingClientRect.


EnsureCreatedAsync() performance downgrade after upgrading Microsoft.Data.SqlClient from version 5.1.1 to 5.1.4(5.1.1-->5.1.4)

Describe the bug
I am using Microsoft.EntityFrameworkCore localDB SQLServer to run test cases, I use below commands in each test cases
await context.Database.EnsureDeletedAsync().ConfigureAwait(false);
await context.Database.EnsureCreatedAsync().ConfigureAwait(false);
But after upgrading Microsoft.Data.SqlClient package version from 5.1.1 to 5.1.4(5.1.1-->5.1.4), EnsureCreatedAsync()  performance downgraded, can you please help me understand this ?
To reproduce
Please use this code to check
using Microsoft.EntityFrameworkCore;
using Moq;
using Xunit;

namespace POCSQLClientPerformence.Tests
{
    public class SQLClientPerformenceDB
    {
        private IDbContextFactory<TestDBContext> factory;

        public SQLClientPerformenceDB()
        {
            CreateDbAsync().GetAwaiter().GetResult();
        }

        async Task CreateDbAsync()
        {
            Func<TestDBContext> CreateContext = () =>
            {
                var optionsBuilder = new DbContextOptionsBuilder<TestDBContext>()
                    .UseSqlServer(@$"Server=(localdb)\MSSQLLocalDb;Database=ABCTestDb;Trusted_Connection=True;MultipleActiveResultSets=true");

                return new TestDBContext(optionsBuilder.Options);
            };

            var factoryMock = new Mock<IDbContextFactory<TestDBContext>>();
            factoryMock.Setup(it => it.CreateDbContextAsync(It.IsAny<CancellationToken>())).ReturnsAsync(CreateContext);

            this.factory = factoryMock.Object;
            using var context = await this.factory.CreateDbContextAsync(CancellationToken.None).ConfigureAwait(false);

            await context.Database.EnsureDeletedAsync().ConfigureAwait(false);
            await context.Database.EnsureCreatedAsync().ConfigureAwait(false);
        }

        [Fact]
        public async Task FirstTest()
        {
            // Arrange
            using var context = await this.factory.CreateDbContextAsync(CancellationToken.None).ConfigureAwait(false);

            // Assert - Validate the results or behavior
            Assert.NotNull(context); // Just a dummy assertion for demonstration
        }

        [Fact]
        public async Task SecoundTest()
        {
            // Arrange
            using var context = await this.factory.CreateDbContextAsync(CancellationToken.None).ConfigureAwait(false);

            // Assert - Validate the results or behavior
            Assert.NotNull(context); // Just a dummy assertion for demonstration
        }

        [Fact]
        public async Task ThirdTest()
        {
            // Arrange
            using var context = await this.factory.CreateDbContextAsync(CancellationToken.None).ConfigureAwait(false);

            // Assert - Validate the results or behavior
            Assert.NotNull(context); // Just a dummy assertion for demonstration
        }
    }
 @}

Microsoft.Data.SQLClient: 5.2.0(Latest) test case execution time:

Microsoft.Data.SQLClient version 5.1.1 or later package test case execution time:

Fixed in 5.2.1

Please try again after the 5.2.1 Hotfix is published and please let us know if you are still having an issue.

I did not find Microsoft.Data.SqlClient version 5.2.1 and 5.1.6 please check published version. https://www.nuget.org/packages/Microsoft.Data.SqlClient/5.2.0?_src=template#versions-body-tab
Could you please explain why this is happening?

That feature you requested to be investigated is in EntityFramework package.  Could you open an issue with EntityFramework instead, please?
https://github.com/dotnet/efcore/issues

Butts due to Microsoft.Data.SqlClient version only you can check upgrading Microsoft.Data.SqlClient version from 5.1.1 to 5.1.4. you can observe time difference

We will investigate and get back to you when we have an update. When the Hotfix 5.2.1 is released later this week, could you try that and let us know if you are still having an issue.

Could you provide a runnable repro in a zip file, please?

@arellegue provided in MS Teams.

Duplicate of #33399

I have investigated this issue and found the root cause to be in the introduction of transient fault handling which added the delay.
We will discuss how to appropriately implement a fix. We will let you know when the issue is fixed.

This is related to fix in #1983.

@akhiltyagi98 htofix v5.2.1 is released. Can you test with that version?

@arellegue @JRahnama JRahnama
Thanks Team issue has been fixed in new release 5.2.1. Please mark this as close.

Fixed in hotfix release 5.2.1.


[4.2.0] Hit error when running debug

Hi @danvick ,
I am getting error when running debug.
It seems something to do with the flutter_typehead package, could you please take a look?
Many Thanks.
Launching lib\main.dart on Android SDK built for x86 in debug mode...
 lib\main.dart
/C:/src/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-4.2.0/lib/src/fields/form_builder_typeahead.dart:184:9: Error: Expected 0 type arguments.
  final TextFieldConfiguration<T> textFieldConfiguration;
        ^
/C:/src/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-4.2.0/lib/src/fields/form_builder_typeahead.dart:328:20: Error: Expected 0 type arguments.
              ) as TextFieldConfiguration<dynamic>,
                   ^^^^^^^^^^^^^^^^^^^^^^

FAILURE: Build failed with an exception.

* Where:
Script 'C:\src\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command 'C:\src\flutter\bin\flutter.bat'' finished with non-zero exit value 1

* 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

BUILD FAILED in 43s
Picked up _JAVA_OPTIONS: -Xmx2g
Exception: Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

Looks like here is the culprit.

Looks like here is the culprit.

Yes,I also ,please fix it

Yes,I also ,please fix it

just got this as well

just got this as well

Found the issue. It was weird since everything was working fine yesterday and not anymore this morning. Turns out the flutter typehead dev pushed an update yesterday/this morning which causes the problem because flutter form builder is depended on it.
Long story short, in the meantime that the dev of typehead fixes the issue, add this to your pubspec.yaml and everything should work:
flutter_typeahead: "<=1.9.1"
Opened an issue as well on their repo if anyone's interested: https://github.com/AbdulRahmanAlHamali/flutter_typeahead/issues/270#issue-781183747

Found the issue. It was weird since everything was working fine yesterday and not anymore this morning. Turns out the flutter typehead dev pushed an update yesterday/this morning which causes the problem because flutter form builder is depended on it.
Long story short, in the meantime that the dev of typehead fixes the issue, add this to your pubspec.yaml and everything should work:
flutter_typeahead: "<=1.9.1"
Opened an issue as well on their repo if anyone's interested: https://github.com/AbdulRahmanAlHamali/flutter_typeahead/issues/270#issue-781183747

Found the issue. It was weird since everything was working fine yesterday and not anymore this morning. Turns out the flutter typehead dev pushed an update yesterday/this morning which causes the problem because flutter form builder is depended on it.
Long story short, in the meantime that the dev of typehead fixes the issue, add this to your pubspec.yaml and everything should work:
flutter_typeahead: "<=1.9.1"
Opened an issue as well on their repo if anyone's interested: AbdulRahmanAlHamali/flutter_typeahead#270 (comment)

Thanks @Silfalion for the update.
I believe the error is not within the flutter_typehead package, but rather in this package.
flutter_typehead has made some changes that causing some breaking changes here.
I removed the generic type  from TextFieldConfiguation and it works.
Anyway, I will leave it to @danvick for the correct fixes.

Found the issue. It was weird since everything was working fine yesterday and not anymore this morning. Turns out the flutter typehead dev pushed an update yesterday/this morning which causes the problem because flutter form builder is depended on it.
Long story short, in the meantime that the dev of typehead fixes the issue, add this to your pubspec.yaml and everything should work:
flutter_typeahead: "<=1.9.1"
Opened an issue as well on their repo if anyone's interested: AbdulRahmanAlHamali/flutter_typeahead#270 (comment)

Thanks @Silfalion for the update.
I believe the error is not within the flutter_typehead package, but rather in this package.
flutter_typehead has made some changes that causing some breaking changes here.
I removed the generic type  from TextFieldConfiguation and it works.
Anyway, I will leave it to @danvick for the correct fixes.

my please @jasonlaw.
I see, so it's a matter of incompatibility.
Thank you for the notice and explanation.

my please @jasonlaw.
I see, so it's a matter of incompatibility.
Thank you for the notice and explanation.

I also received this error when running a flutter run command, but I don't make any use of TypeAhead. I just added one FormBuilderTextField and now I got a whole slew of warnings along with those errors which I never had before.

I also received this error when running a flutter run command, but I don't make any use of TypeAhead. I just added one FormBuilderTextField and now I got a whole slew of warnings along with those errors which I never had before.

Same, also getting this error in my automated builds.

Same, also getting this error in my automated builds.

I'm gettitng frustrated because no matter what version of form_builder I use in pubspec it causes my compilation errors in my app.

I'm gettitng frustrated because no matter what version of form_builder I use in pubspec it causes my compilation errors in my app.

Quick fix for those who can't wait is top remove generics type-safety on the declaration and usage of TextFieldConfiguration lines 184 and 328 in the file form_builder_typeahead.dart

Quick fix for those who can't wait is top remove generics type-safety on the declaration and usage of TextFieldConfiguration lines 184 and 328 in the file form_builder_typeahead.dart


[Update] translate the notes/README.md in English

Issue description
The current notes/README.md is in Chinese, please refer other pages to translate it in Chinese.
Steps：

cope notes/README.md as notes/README_CN.md
translate the notes/README.md in English
add Chinese ([English](./README.md)  | 简体中文 ) and English links(English | [简体中文](./README_CN.md)  ) to notes/README_CN.md and notes/README.md

详情
目前的notes/README.md是中文的，请参考其他页面翻译成中文。
步骤：

将 notes/README.md 处理为 notes/README_CN.md
将notes/README.md翻译成英文

在notes/README_CN.md中添加中文链接([English](./README.md) | 简体中文)和英文链接(English | [简体中文](./README_CN.md)) 注释/README.md

Hi, I have solved the issue. Please see #245.

@songqiang321  you can check your PR link, with a Close #244 in your PR description, you could mention it and the issue could be closed when your PR were merged


Fix max bucket limit in histogram

The max bucket limit in histogram was broken, since some code introduced temporary filtering of buckets, which then resulted in an incorrect increment on the bucket count.
The provided solution handles more use cases correctly, but there are still some scenarios unhandled (See #1702).
https://github.com/quickwit-oss/quickwit/issues/2503

Codecov Report

Merging #1703 (644a8b2) into main (4958243) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1703      +/-   ##
==========================================
+ Coverage   94.06%   94.11%   +0.04%
==========================================
  Files         259      261       +2
  Lines       49637    50009     +372
==========================================
+ Hits        46692    47066     +374
+ Misses       2945     2943       -2

Impacted Files
Coverage Δ

src/aggregation/bucket/histogram/histogram.rs
99.56% <100.00%> (+0.01%)
:arrow_up:

fastfield_codecs/src/lib.rs
98.89% <0.00%> (ø)

fastfield_codecs/src/null_index/dense.rs
99.37% <0.00%> (ø)

fastfield_codecs/src/null_index/mod.rs
100.00% <0.00%> (ø)

src/schema/schema.rs
98.91% <0.00%> (+0.13%)
:arrow_up:

src/postings/stacker/term_hashmap.rs
100.00% <0.00%> (+0.56%)
:arrow_up:

src/fastfield/multivalued/mod.rs
99.22% <0.00%> (+0.77%)
:arrow_up:

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


Very bad advice - off putting - in 10.2: A little Rust with your C

This is a minor point, and can be fixed by removing the offending sentence.  But is is an offensive (in a technical sense) sentence.
I am coming to this chapter via a web search for calling Rust from C
It says this:
Apart from cargo and meson, most build systems don't have native Rust support. So you're most likely best off just using cargo for compiling your crate and any dependencies.

Coming from the perspective of 90k lines of C code, a build system that has been sweated over, saying "you're most likely best off just using cargo" is saying "get lost, we do not care about you".
Removing that sentence - especially right at the start - would help.
Integrating with Make is a bare minimum for calling Rust from C
I am in a situation of settling onto a new job with a project that is over 90k lines of C, so not huge, but significant.  I would like to point my new boss at resources that help explain why new capabilities could be added in Rust - a possibility.
I cannot point them here.  If I were my boss (thirty years programming Linux modules in C) and I saw that, I would stop reading.
All that said I must finish with: Well done!  Keep up the good work!

Hi, thanks for the report. I worry that you've misunderstood the intent behind this sentence as I don't think it's offensive. Perhaps it can be clarified. The sentence intends to say "you should use Cargo to build your Rust code, because it is infeasible to use Make directly to compile Rust", but it does not mean "you should throw away your Makefiles and use Cargo to build your whole project", because Cargo does not build C projects.
The idea is that you use Cargo to compile your Rust crate, typically to a static library (e.g. a .a or .lib file), and then you link that library in your C build process, just as you would any other pre-compiled library. You might additionally want to have your Makefile run Cargo to check the static library is rebuilt when appropriate (probably by always calling cargo, rather than having to tell Make about all the Rust source that the library depends on).

Integrating with Make is a bare minimum for calling Rust from C

Most C projects probably aren't using Make, so I don't think this is true. The important thing is how to build a static library using Cargo which you can then link in to your normal C or C++ build process. Optionally, having the C build process call cargo for you could be convenient too.

Yes.  I was coming to this with the mindset of a C programmer, which I am, looking for advice for/reasons to, use Rust.
Dropping into the middle of the book like that I miss the wider context, and I see the statement about "build using Cargo" as "Go away".  Unfair, I know.  Sorry.
I see the next paragraph talks about "build your crate as usual..."  Again, where I am coming from that makes no sense.  But I am out of context.
I think this is not what I am looking for.  If you want this page to be welcoming to a C programmer, it needs a complete rewrite, but I am unsure if that is your audience.
I love and hate C.  For a long time there was no alternative.  It was the C-way or something really really bad.
Times have changed in the last five years, and I want to change with them.  There is no hope of rewriting a lot of software (I have 95k lines of C in my immediate attention) but for adding units to our system, I think (?) Rust is the way to go.
SO I show up, searching the Interweb for "Calling Rust from C" and I end up on your book, on this page.
That is the background to me raising this issue.
I have no idea what you want to do about that, if anything.
I love your work, you are doing a great job, it is not exactly what I need!
cheers

I have no idea what you want to do about that, if anything.

@worikgh I think you made your point, and got a reply from the book authors. I visited this page today (though via reading through the whole book) and I wouldn’t see anything worth changing in it.
I can see you having two choices now:

Close the issue since you got the message through
Be more specific how you’d like the text to be changed. ”I have no idea what you want to do […]” is not the kind of language that I usually see in GitHub Issues. Try to be friendly and gentle. We are here mostly on our own time, and want to enjoy the neighbourhood. :)


[AutoPR databox/resource-manager] typo: Microsoft.DataBox

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4672

(message created by the CI based on PR content)

Codecov Report

Merging #3930 into restapi_auto_databox/resource-manager will increase coverage by 0.7%.
The diff coverage is n/a.

@@                            Coverage Diff                            @@
##           restapi_auto_databox/resource-manager    #3930      +/-   ##
=========================================================================
+ Coverage                                  56.23%   56.94%    +0.7%
=========================================================================
  Files                                       9600     8850     -750
  Lines                                     197312   174750   -22562
=========================================================================
- Hits                                      110955    99504   -11451
+ Misses                                     86357    75246   -11111

Impacted Files
Coverage Δ

...azure/mgmt/eventgrid/models/topic_type_info_py3.py
41.66% <0%> (-58.34%)
:arrow_down:

...rid/azure/mgmt/eventgrid/models/topic_type_info.py
41.66% <0%> (-58.34%)
:arrow_down:

...ntgrid/azure/mgmt/eventgrid/models/resource_py3.py
55.55% <0%> (-44.45%)
:arrow_down:

...ompute/v2018_06_01/models/grant_access_data_py3.py
62.5% <0%> (-37.5%)
:arrow_down:

...zure/mgmt/eventgrid/models/tracked_resource_py3.py
62.5% <0%> (-37.5%)
:arrow_down:

...mt/compute/v2018_06_01/models/grant_access_data.py
62.5% <0%> (-37.5%)
:arrow_down:

...azure/graphrbac/models/required_resource_access.py
55.55% <0%> (-36.76%)
:arrow_down:

...raphrbac/azure/graphrbac/models/resource_access.py
55.55% <0%> (-36.76%)
:arrow_down:

...re-graphrbac/azure/graphrbac/models/graph_error.py
63.63% <0%> (-36.37%)
:arrow_down:

...zure/mgmt/compute/v2018_06_01/models/access_uri.py
71.42% <0%> (-28.58%)
:arrow_down:

... and 1179 more

Continue to review full report at Codecov.

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


permissions issue

Hi,
My goal is to provide within a custom directory in the goaccess docker container a bunch of directories with logs in it, like the following example:

docker run --name=goaccess --restart=always -d -p 80:8080 \
    -v /path/to/log/apache2:/dwl/var/log/apache2 \
    -v /path/to/data:/srv/data \
    allinurl/goaccess

within /path/to/log/apache2, I m binding /var/log/apache2 directories from other containers.
the main issue I m facing is the permission issue.
on goaccess directories I need this permission root:syslog and on my other containers root:adm
if my other container got root:syslog, they can t update the log files and reverse for goaccess.
any suggestion ?

never mind


Removed a deprecated command

Co-authored-by: Rebecca McFadden<EMAIL_ADDRESS>Co-authored-by: Mohona Ahmed<EMAIL_ADDRESS>

This change is

@MaanavD Please would you rebase this PR so that you're the only author of the commit? It's a very small change (one line removed) so I'm not sure how it could have multiple authors. Having a single author will make the automated CLA check work, and will remove the necessity for repository managers to check all the email addresses in the commit.
/lgtm


UnicodeEncodeError when there is an existing setup.cfg file with non-ascii characters

It was my first use (attempt):
$ pip install --user bumpversion
Downloading/unpacking bumpversion
  Downloading bumpversion-0.5.3-py2.py3-none-any.whl
Installing collected packages: bumpversion
Successfully installed bumpversion
Cleaning up...
$ bumpversion -h
Traceback (most recent call last):
  File "/home/kr/.local/bin/bumpversion", line 11, in <module>
    sys.exit(main())
  File "/home/kr/.local/lib/python2.7/site-packages/bumpversion/__init__.py", line 695, in main
    config.write(log_config)
  File "/usr/lib/python2.7/ConfigParser.py", line 412, in write
    key = " = ".join((key, str(value).replace('\n', '\n\t')))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe1' in position 7: ordinal not in range(128)

Checking what can be the problem in bumpversion/__init__.py, around line 695 the candidate problem source is that I have run it in a project directory with an existing setup.cfg:
$ file setup.cfg
setup.cfg: C++ source, UTF-8 Unicode text

and it is indeed a utf-8 file, with non-ascii characters (my accented name) in it.  It is a project that was originally packaged with pbr - had declarative packaging definition.

Temporary workaround: I have created a .bumpversion.cfg file and now it shows the help.

Good find! Can you try updating configparser (pip install configparser, the version that ships with python 2.7 is too old to handle utf-8 properly here, i think) ?

After installing a configparser it works!  (I have renamed .bumpversion.cfg for the check)

Then we're probably out of luck fixing this bug in bumpversion. Python 3 includes the updated version of configparser (the one that handles utf-8 correctly), so it will fade away with more people moving towards Python 3.
Have fun with bumpversion!

This was quick!
I'll surely remember this configparser vs ConfigParser issue.
It was just shocking at first that  it does not even print the help on a recent-ish ubuntu for me (14.04.2 LTS). Fortunately it is not a blocker.
I will use bumpversion as I am quite sure it is the currently best solution for inserting versions into projects!
Thanks!

Isn't it possible to add configparser as a dependency for bumpversion?

@coredumperror Yes, that would certainly be possible. However, currently bumpversion doesn't have a single dependency and I'd like to treat an updated version of configparser as optional.
The best approach here is probably to catch UnicodeDecodeErrors when using the old ConfigParser and print an error message along the lines of "Can't read the config file because you're using non-ascii characters and didn't update configparser. Use pip install -U configparser to fix" ?


Docker registry v2 authentication failure

Hi there,
I have a bit of a problem : I can't create a json to authenticate on a private docker registry, to pull images... I keep getting this error :
error converting docker image to ACI: unexpected http code: 401, URL:
Even using the config pattern described here. The json config files are present here :
/etc/rkt/auth.d/docker.json /usr/lib/rkt/auth.d/docker.json

Here is the format that I used :
{
    "rktKind": "dockerAuth",
    "rktVersion": "v1",
    "registries": ["r.mycompany.com", "reg.mycompany.com"],
    "credentials": {
        "user": "docker",
        "password": "REDACTED"
    }
}

Note : I tried with base64 encoded and decoded password.

docker2aci fix: https://github.com/appc/docker2aci/pull/113

Thx!

I'm running rkt 1.0.0 and I'm still having this exact problem.

I'm running rkt 1.0.0 and I'm still having this exact problem.

I just tested with a local docker registry and this file:
# /etc/rkt/auth.d/docker.json
{
	"rktKind": "dockerAuth",
	"rktVersion": "v1",
	"registries": ["localhost:5000"],
	"credentials": {
		"user": "iago",
		"password": "password"
	}
}

It seems to work for me:
$ rkt --insecure-options=image,http fetch docker://localhost:5000/busybox
image: remote fetching from URL "docker://localhost:5000/busybox"
Downloading sha256:eeee0535bf3: [==============================] 676 KB/676 KB
Downloading sha256:a3ed95caeb0: [==============================] 32 B/32 B
sha512-2463c14e8f6f49cb03c3416d7bb15c48

Can you give more information about your scenario and paste your auth config? (with passwords redacted, of course :)).

@iaguis Sure. I guess I should have from the start. This is my auth config:
{
    "rktKind": "dockerAuth",
    "rktVersion": "v1",
    "registries": ["index.docker.io"],
    "credentials": {
        "user": "shortusername",
        "password": "password"
    }
}

The user is my short username on docker hub, the password is the password. Dockers own config likes it to be the email and base64 of "shortusername:password" in the auth field it seems. I've tried several combinations in the auth config but none of them seem to work. I get 401:s every time. It's a private repo on docker hub I'm trying to fetch.

Also the error from rkt is this:
image: remote fetching from URL "docker://usernamehere/repohere"
fetch: unexpected http code: 401, URL: https://registry-1.docker.io/v2/usernamehere/repohere/manifests/latest

Can you try changing the registry url in the auth config to registry-1.docker.io?

Yeah I tried that just now with the same result. Is this implemented in rkt:
https://docs.docker.com/registry/spec/auth/token/ - that seems to be what the v2 docker hub requires. To me it seems as if that 401 might be expected and the client should handle it by talking to the authentication service.

After a quick look, It seems it is implemented.
I could reproduce it with one of my private repos , I'll have a look.

The problem was that we weren't passing the username and password for the default docker registry.
When we implemented the v2 API in docker2aci, we modified the Docker URL parsing function to not infer the default registry URL because it could be index.docker.io (API v1) or registry-1.docker.io (API v2). This is not needed anymore because the API v1 is deprecated in the default registry.
Fix in docker2aci: https://github.com/appc/docker2aci/pull/120

Not fixed yet, godep not updated.


Move model rotation to Face class property

Better to start after #49 task will be implemented

Closed by https://github.com/char-lie/mfm/commit/d61ee0da2b4ed834318d8467d66d6382a0301b06


web.enable-lifecycle  flag   false status

This flag value shows that it is not in line with reality, it is obviously enabled and the test has passed, and then the false state is also displayed here.

I can not reproduce it. Are you sure that you are pointing to the same release?

I found the reason. My docker-compose mounts prometheus.yaml as a file, so even if the interface is dropped, the effect cannot be seen, because docker needs to mount a directory to do file synchronization, and the directory permission is 775.

I truly appreciate your timely help.

Thanks!


Minor tweaks and cleanup

@lukeapage: after this I could have a look at bumping clean-css and making the adaptation.
Also, this closes #17 since it includes a similar change.

I added you as a collaborater.. if you give me your npm username I can give you publishing permissions.

Hey. I use the same username on npm just lowercase  (xhmikosr).
How do you want to proceed with the clean-css upgrade? I think I will merge
this and release a patch version and then look into the new clean-css.
On Feb 19, 2017 18:31, "Luke Page"<EMAIL_ADDRESS>wrote:

I added you as a collaborater.. if you give me your npm username I can
give you publishing permissions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/less/less-plugin-clean-css/pull/19#issuecomment-280930085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtUfGHT-HGNmpyykynPGXgH2RJIg8ks5reG5GgaJpZM4MFZx7
.

Sounds good. I'm no longer involved much with less.js and have precious little time for o/s at the moment.

I understand. No worries I'll make a few changes now that I have time for
open source.
On Feb 19, 2017 22:16, "Luke Page"<EMAIL_ADDRESS>wrote:

Sounds good. I'm no longer involved much with less.js and have precious
little time for o/s at the moment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/less/less-plugin-clean-css/pull/19#issuecomment-280945350,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtQKP4rPeAz6UAbVJZcelZ5Onatejks5reKMfgaJpZM4MFZx7
.

When you give me npm rights I'll publish a patch version and then look into the clean-css update.
I'd still like your opinion about dropping advanced and just use clean-css default which is O1.


Issue with openBox and typeAdapters

I noticed an old closed ticket about the same subject so I opened a new one. My issue is at next comment.

Getting the same error again. Here is the stacktrace:
_CastError
type '_OneByteString' is not a subtype of type 'int' in type cast
user.g.dart in UserAdapter.read at line 17
binary_reader_impl.dart in BinaryReaderImpl.read at line 321
binary_reader_impl.dart in BinaryReaderImpl.readFrame at line 266
frame_helper.dart in FrameHelper.framesFromBytes at line 16
frame_io_helper.dart in FrameIoHelper.framesFromFile at line 37
Called from: <asynchronous suspension>
storage_backend_vm.dart in StorageBackendVm.initialize at line 74
Called from: <asynchronous suspension>
box_base_impl.dart in BoxBaseImpl.initialize at line 82
hive_impl.dart in HiveImpl._openBox at line 95
Called from: <asynchronous suspension>
hive_impl.dart in HiveImpl.openBox at line 112
main.dart in main._openBoxes at line 30
Called from: <asynchronous suspension>
main.dart in main at line 42
Called from: async_patch.dart in _AsyncAwaitCompleter.start
main.dart in main at line 20
Called from: hooks.dart in _runMainZoned.<fn>.<fn>

This is what I do in main.dart
void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  Future _openBoxes() async {
    await Hive.initFlutter();
    return Future.wait([
      Hive.openBox('user'),
      Hive.openBox('submenu'),
    ]);
  }

  Hive.registerAdapter(UserAdapter(), 1);
  Hive.registerAdapter(SubMenuAdapter(), 2);
  Hive.registerAdapter(MenuTypeAdapter(), 3);
  await _openBoxes();

  runApp(
    ChangeNotifierProvider(
      create: (context) => AuthProvider()..init(),
      child: Oregon(),
    ),
  );
}

User class:
@HiveType()
class User extends HiveObject {
  @HiveField(0)
  int userId;
  @HiveField(1)
  int driverId;
  @HiveField(2)
  String name;
  @HiveField(3)
  String email;
  @HiveField(4)
  String password;
  @HiveField(5)
  String authToken;

@HiveField(6)
String gsm;
@HiveField(7)
String avatarUrl;
@HiveField(8)
String timeZone;
@HiveField(9)
String locale;
@HiveField(10)
String language;
User({
this.userId,
this.driverId,
this.name,
this.email,
this.password,
this.authToken,
this.gsm,
this.timeZone,
this.locale,
this.language,
this.avatarUrl,
});
}

auto generated UserAdapter:
The corresponding line in stacktrace for this file is

`userId: fields[0] as int`

class UserAdapter extends TypeAdapter {
@override
User read(BinaryReader reader) {
var numOfFields = reader.readByte();
var fields = <int, dynamic>{
for (var i = 0; i < numOfFields; i++) reader.readByte(): reader.read(),
};
return User(
userId: fields[0] as int,
driverId: fields[1] as int,
name: fields[2] as String,
email: fields[3] as String,
password: fields[4] as String,
authToken: fields[5] as String,
gsm: fields[6] as String,
timeZone: fields[8] as String,
locale: fields[9] as String,
language: fields[10] as String,
avatarUrl: fields[7] as String,
);
}
@override
void write(BinaryWriter writer, User obj) {
writer
..writeByte(11)
..writeByte(0)
..write(obj.userId)
..writeByte(1)
..write(obj.driverId)
..writeByte(2)
..write(obj.name)
..writeByte(3)
..write(obj.email)
..writeByte(4)
..write(obj.password)
..writeByte(5)
..write(obj.authToken)
..writeByte(6)
..write(obj.gsm)
..writeByte(7)
..write(obj.avatarUrl)
..writeByte(8)
..write(obj.timeZone)
..writeByte(9)
..write(obj.locale)
..writeByte(10)
..write(obj.language);
}
}

Do you think this is related to Hive?

Originally posted by @selimkundakci in https://github.com/hivedb/hive/issues/214#issuecomment-589606229

I am facing this same issue now. Got any idea what is it related to?
type '_OneByteString' is not a subtype of type 'int' in type cast
This started to occur on few devices (Galaxy A8 and Oneplus 7 Pro) after delete and reinstall of the app. I have been using only the latest version v1.4.1+1
I have nested TypeAdapters in one box that I am trying to open:
var box = await Hive.openBox<Week>("weekBox");
_CastError: type '_OneByteString' is not a subtype of type 'int' in type cast
  File "day.g.dart", line 21, in DayAdapter.read
  File "binary_reader_impl.dart", line 325, in BinaryReaderImpl.read
  File "binary_reader_impl.dart", line 212, in BinaryReaderImpl.readMap
  File "binary_reader_impl.dart", line 316, in BinaryReaderImpl.read
  File "week.g.dart", line 17, in WeekAdapter.read
  File "binary_reader_impl.dart", line 325, in BinaryReaderImpl.read
  File "binary_reader_impl.dart", line 273, in BinaryReaderImpl.readFrame
  File "frame_helper.dart", line 17, in FrameHelper.framesFromBytes
  File "frame_io_helper.dart", line 41, in FrameIoHelper.framesFromFile
  File "<asynchronous suspension>"
  File "storage_backend_vm.dart", line 82, in StorageBackendVm.initialize
  File "<asynchronous suspension>"
  File "hive_impl.dart", line 106, in HiveImpl._openBox
  File "<asynchronous suspension>"
  File "hive_impl.dart", line 135, in HiveImpl.openBox
  File "<asynchronous suspension>"

@HiveType(typeId: 0)
class Week extends HiveObject {
  @HiveField(0)
  String weekNumber;

  @HiveField(1)
  Map<String, Day> weekDays;

class WeekAdapter extends TypeAdapter<Week> {
  @override
  final int typeId = 0;

  @override
  Week read(BinaryReader reader) {
    final numOfFields = reader.readByte();
    final fields = <int, dynamic>{
      for (int i = 0; i < numOfFields; i++) reader.readByte(): reader.read(),
    };
    return Week(
      weekNumber: fields[0] as String,
      weekDays: (fields[1] as Map)?.cast<String, Day>(),
    );
  }

  @override
  void write(BinaryWriter writer, Week obj) {
    writer
      ..writeByte(2)
      ..writeByte(0)
      ..write(obj.weekNumber)
      ..writeByte(1)
      ..write(obj.weekDays);
  }

  @override
  int get hashCode => typeId.hashCode;

  @override
  bool operator ==(Object other) =>
      identical(this, other) ||
      other is WeekAdapter &&
          runtimeType == other.runtimeType &&
          typeId == other.typeId;
}

@HiveType(typeId: 1)
class Day {
  @HiveField(0)
  String text;

  @HiveField(1)
  int value;

class DayAdapter extends TypeAdapter<Day> {
  @override
  final int typeId = 1;

  @override
  Day read(BinaryReader reader) {
    final numOfFields = reader.readByte();
    final fields = <int, dynamic>{
      for (int i = 0; i < numOfFields; i++) reader.readByte(): reader.read(),
    };
    return Day(
      text: fields[0] as String,
      value: fields[1] as int,
    );
  }

Version

Platform: Android
Flutter version: 1.22.5
Hive version: 1.4.1+1

I am facing this same issue now. Got any idea what is it related to?
type '_OneByteString' is not a subtype of type 'int' in type cast
This started to occur on few devices (Galaxy A8 and Oneplus 7 Pro) after delete and reinstall of the app. I have been using only the latest version v1.4.1+1
I have nested TypeAdapters in one box that I am trying to open:
var box = await Hive.openBox<Week>("weekBox");
_CastError: type '_OneByteString' is not a subtype of type 'int' in type cast
  File "day.g.dart", line 21, in DayAdapter.read
  File "binary_reader_impl.dart", line 325, in BinaryReaderImpl.read
  File "binary_reader_impl.dart", line 212, in BinaryReaderImpl.readMap
  File "binary_reader_impl.dart", line 316, in BinaryReaderImpl.read
  File "week.g.dart", line 17, in WeekAdapter.read
  File "binary_reader_impl.dart", line 325, in BinaryReaderImpl.read
  File "binary_reader_impl.dart", line 273, in BinaryReaderImpl.readFrame
  File "frame_helper.dart", line 17, in FrameHelper.framesFromBytes
  File "frame_io_helper.dart", line 41, in FrameIoHelper.framesFromFile
  File "<asynchronous suspension>"
  File "storage_backend_vm.dart", line 82, in StorageBackendVm.initialize
  File "<asynchronous suspension>"
  File "hive_impl.dart", line 106, in HiveImpl._openBox
  File "<asynchronous suspension>"
  File "hive_impl.dart", line 135, in HiveImpl.openBox
  File "<asynchronous suspension>"

@HiveType(typeId: 0)
class Week extends HiveObject {
  @HiveField(0)
  String weekNumber;

  @HiveField(1)
  Map<String, Day> weekDays;

class WeekAdapter extends TypeAdapter<Week> {
  @override
  final int typeId = 0;

  @override
  Week read(BinaryReader reader) {
    final numOfFields = reader.readByte();
    final fields = <int, dynamic>{
      for (int i = 0; i < numOfFields; i++) reader.readByte(): reader.read(),
    };
    return Week(
      weekNumber: fields[0] as String,
      weekDays: (fields[1] as Map)?.cast<String, Day>(),
    );
  }

  @override
  void write(BinaryWriter writer, Week obj) {
    writer
      ..writeByte(2)
      ..writeByte(0)
      ..write(obj.weekNumber)
      ..writeByte(1)
      ..write(obj.weekDays);
  }

  @override
  int get hashCode => typeId.hashCode;

  @override
  bool operator ==(Object other) =>
      identical(this, other) ||
      other is WeekAdapter &&
          runtimeType == other.runtimeType &&
          typeId == other.typeId;
}

@HiveType(typeId: 1)
class Day {
  @HiveField(0)
  String text;

  @HiveField(1)
  int value;

class DayAdapter extends TypeAdapter<Day> {
  @override
  final int typeId = 1;

  @override
  Day read(BinaryReader reader) {
    final numOfFields = reader.readByte();
    final fields = <int, dynamic>{
      for (int i = 0; i < numOfFields; i++) reader.readByte(): reader.read(),
    };
    return Day(
      text: fields[0] as String,
      value: fields[1] as int,
    );
  }

Version

Platform: Android
Flutter version: 1.22.5
Hive version: 1.4.1+1

I added subfolder-attribute for initFlutter-function, released a new version and tried again with Oneplus 7 Pro.
void main() async {
  Hive
    ..initFlutter("flutterfiles")
    ..registerAdapter(DayAdapter())
    ..registerAdapter(WeekAdapter());

    ...
}

The app was working once, but after remove and reinstall of the app the issue reoccured.
type '_OneByteString' is not a subtype of type 'int' in type cast
Could it be that the database file is not deleted when removing the app from phone and there's something else left that shouldn't be there?

I added subfolder-attribute for initFlutter-function, released a new version and tried again with Oneplus 7 Pro.
void main() async {
  Hive
    ..initFlutter("flutterfiles")
    ..registerAdapter(DayAdapter())
    ..registerAdapter(WeekAdapter());

    ...
}

The app was working once, but after remove and reinstall of the app the issue reoccured.
type '_OneByteString' is not a subtype of type 'int' in type cast
Could it be that the database file is not deleted when removing the app from phone and there's something else left that shouldn't be there?

Hey there having the same issue with some few android devices, I noticed that If I try to install an old version of the app from the App Store and then updating it using an APK(the one causing issues) it works.
But if I try installing the app from scratch it does not, I feel like something is being left behind the scenes after deleting the app.

This is complaining about this model:

I added subfolder-attribute for initFlutter-function, released a new version and tried again with Oneplus 7 Pro.
void main() async {
  Hive
    ..initFlutter("flutterfiles")
    ..registerAdapter(DayAdapter())
    ..registerAdapter(WeekAdapter());

    ...
}

The app was working once, but after remove and reinstall of the app the issue reoccured.
type '_OneByteString' is not a subtype of type 'int' in type cast
Could it be that the database file is not deleted when removing the app from phone and there's something else left that shouldn't be there?

did you had any luck at the end on this? :/ I am thinking of using something else.. this is a major issue for me.

I got rid of this error. I wish I had tested and documented this properly, but I couldn't reproduce this on my own devices. It probably had something to do with having extra initialization for Hive. Or initing Hive too late.
At least do not use this:
  final appDocumentDir = await getApplicationDocumentsDirectory();   ..init(appDocumentDir.path)

same error in 2022. I'm moving to sqflite :(

Try change android:allowBackup="false".

Try change android:allowBackup="false".

Thanks. hope you have good day!


Prime ′ (U+2032) and Double Prime ″ (U+2033) should be slanted to left

Similar issue as in this Noto bug: https://github.com/googlei18n/noto-fonts/issues/510
Prime ′ (U+2032) and Double Prime ″ (U+2033) should be slanted to left, based on Microsoft's recommendation:  https://www.microsoft.com/typography/developers/fdsspec/symbol.aspx.
They should be mirrored glyphs of Reversed Prime ‵ (U+2035) and Reversed Double Prime ‶(2036).

I had a chat with @christianrobertson about this about a year ago. He slightly preferred the Roboto quotes to be upright IIRC, but considering what we have unearthed since then, I strongly believe they should be angled.
/cc @raphlinus

And, there's a consistency concern because 1) U+2034 (triple prime) is slanted while U+2032 and U+2033 are not 2) Reverse counterparts to U+203[23], U+203[56] are slanted while  U+203[23] are not.


fix(deps): Update NextJS dependency to version ^13.4.1

Closes #1399
✅ Checklist

[ ] I have followed every step in the contributing guide (updated 2022-10-06).
[ ] The PR title follows the convention we established conventional-commit
[ ] I performed a functional test on my final commit

Changelog
[Short description of what has changed]

Screenshots
[Screenshots]
💯

Would this make the appDir available in create-t3-app?


[SMALLFIX ] validate inode's id earlier during image loading

we should check inode's id before updating the inode map.

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

@chen-tian could you resolve the merge conflicts please?

@chen-tian, the MasterInfo has changed significantly after the refactoring, do you still want to keep this PR?

No longer needed because of code refactoring


Re-deploy ontology.biosimulations.dev with new version of KiSAO

Needed to update annotations of simulation tools

Done


Add metric details to docs

Adds documentation for metrics

@dzucker-tab care to have a look before I merge this?


keysToCamelFromSnake is called twice

It seems like we are calling keysToCamelFromSnake twice in App.js, both at the initial sequence and later when we serve the page component. Since keysToCamelFromSnake is recursive is looks unnecessary.
We should be able to just unpack componentProps here: https://github.com/Frojd/Wagtail-Pipit/blob/10c09ac55fe5f5b2f720fc379d0777a879eba025/{{cookiecutter.project_name}}/frontend/src/containers/App/App.js#L17

Solved in our new way of loading props in Next.js


UI change to require extra clicks?

I've tried to get used to, but not sure if this is only me. The current dataset overview page has folded many functional buttons under the ⠇menu. This not only make daily activities more cumbersome, but also add difficulties in training scenarios.
I do appreciate that IPT UI has become more modern and sleek. Though please do keep function buttons as prominent as possible, such as edit, delete, preview, public/private, publish and register. There are not that many functions that need folding after all on the page IMO. The border line already adds much clarity.
In short, I am suggesting those folded functions under ⠇menu would be released as visible buttons/links upon page loading. Thanks for considering and saving trainees some trouble navigating features.

@ckotwn Thank you very much for your feedback.
Intention was to simplify the interface and improve the mobile version. If the current view is causing problems we can of course change that by replacing the three-dot menus for the desktop version with real buttons. But I would also like to hear more opinions on that.
I'll post screenshots of possible solutions here.

Thanks. I am not sure whether IPT should be mobile-first.  Oh, and in terms of procedure, if there were no hearing-opinions before implementing the 3-dot menu, I think it may be a bit unfair for the reverse? ;) My general concern of IPT UI changes is the associated efforts needed to update the materials (still lagged and being voiced by trainees) and costs when we need to help users navigate the changes. I know, I know, they are not the end of the world, they are just annoying at worst.
Anyway please post possible solutions here and I am keen to work with you to the most sensible one. Others please chime in!
Great job on the sleekness again, @mike-podolskiy90 !

Hi, I just had a look at the latest version of the IPT and here are my thoughts on it:

I like the new UI & colour scheme, I think it makes it visually clearer for the user(s)
I'm still getting used to the  ⠇menu but I don't think it will be 'worse' than previous upgrades for training materials, we regularly have to update our screencaps anyway :)
The extra-clicks might indeed be a bother for some users though? But nothing that can't be explained/demo-ed, especially as it's still possible to take screenshots with the hidden option appearing on screen (just tested it with the Firefox screenshot tool)
One detail (bug?) I noticed is that we cannot access the source file page (with technical details such as the encoding format or separator option) anymore? I can only see the "+ Add" option in the  ⠇menu for the source file section
I agree with @ckotwn that the IPT is mainly used on desktop, so adjustments for the mobile version should not privileged in my opinion
thanks for your great work @mike-podolskiy90 ! :)

@SophiePamerlon Thank you very much for your feedback, I appreciate it.
Editing sources/mappings should be accesible by just clicking on the element. Should we also add an explicit button for that?
Registration is not accesible anymore indeed (it's still accesible on the main resource page though at the top of the page)

I also have just passed through the newest release of the IPT. Some additional thoughts:

I agree with @ckotwn and @SophiePamerlon that the extra clicks will be annoying. As a user who once or twice a year has to update 100+ resources manually on an IPT, these extra clicks will grow tiresome. I know that my case may not be the norm, but even when setting up multiple resources in the same session those extra clicks make a difference. As a user of both Mac and PC platforms I have a sense that this is the sort of thing that will pass once people use the U/I for a couple of weeks. The really annoying stuff, if anything, will rise to the top and find its way to GitHub.

The color scheme is a nice idea, especially in the tables one the home and manage resource tabs, BUT the execution makes the interface look schizophrenic and messy when there are multiple colors in multiple columns. I might suggest picking a color palette for each columns (e.g, various shades of blue/purple in the Type column, shades of red/orange in Subtype and, shades of green/yellow in Visibility). As it is now the reds and oranges in different columns pull the eye in 10 different directions and it is distracting when attempting to read content and navigate the lists.  E.g., this screen view has my eyes shooting all over the place between red alert text, Subtype status and Visibility.

Giving those colors some structure and organization, and possibly even using slightly muted tones would help significantly.

When working with a resource via the overview page those "three dots" over on the right, are difficult to see - once you know they are there, you see them, but even I was wandering around trying to find an "edit" option. Like the extra click issue, the regular need to scroll to the right side, when everything else is over on the left is annoying. Could the dot menu be located in proximity to the rest of the content - perhaps just to the right of the section headers (e.g., Source Data, Darwin Core Mappings)? It just feels like the dot menu offended someone at GBIF has has been banished to the right-hand margin until it agrees to apologize.

Re: the extra clicks and missing buttons - The first place I looked to find the option Add a new source file or to Edit the mappings was not the menu on the far right, it was the dot menu in the existing source and mapping files/links. It was a bit surprising not to find either Add or Edit right there. That will freak some people out. Relocating the primary dot menu over might help.

Similarly, the boxes that contain the files or references to source files, mappings and other info are a bit confusing. Some of those boxes are clickable and take the user to a new page or view. Others don't do anything and leave the user wondering if something is supposed to happen. For example, clicking on a source file, takes you to the source overview, but clicking on the name of a resource manager or on the Registration does nothing even though the interaction with all of the boxes is the same (Note the width of the registration box is double that of every other box on the page). Perhaps those boxes that don't result in a change can be viewed more like the content in the Visibility section to eliminate any expectations that clicking will bring users to the Promised Land?

Finally, I already miss the "View" button in the current version. I know it's in the menu, but, but, but, it was so easy to click.... right there.... waving at me.... Saying "click me!"    I'll survive it. Just sayin'.

@mike-podolskiy90 This still looks amazing and I have enjoyed watching the evolution of the tool over the years. The look overall is much cleaning and more modern, which I think reflects well on your work and GBIF's image. Nothing listed above is a deal-breaker for me, although I think there can be some improvements. Mind you, I'll never be a @SophiePamerlon, but I can try.

@dbloom Thank you for your comments

Hi,
the updated UI fine. I'm not sure how often folks do any real work on a mobile device but that might just be me. I certainly can't foresee training anyone to do that, but it's fun to have.
I am sure all the accessibility checking has been done, just a couple of possible niggles/pet peeves:

I'm a little concerned about the contrast of text and background for readability. Especially on the pastel tags.
The 3 dot menus don't include all the options. Most obviously for me the "edit" option, leaving you to click around to eventually realise that the box around the text shades thereby making it a button!

Otherwise, great job.

@rondlg Thank you for your feedback

Thanks for the great feedback on this.
I think I've managed to apply most of the desired changes to https://ipt.gbif-uat.org.
We're still working on the color scheme and look of the pills, but here are some ideas:

Can I suggest the following colours for the badges:

Dataset type and subtype: I would treat these as tags of the same colour, so they are given the same visual weight. I opted for regular text color (--color-gbif-secondary) for text and border + a white background.
Visibility: I would treat these as ordered categories. I opted for the same design as (hoovered) buttons in the IPT, using the color for text and border + a background with the color at opacity 0.04:

private: either the red --color-gbif-danger or the milder yellow --color-gbif-warning. I think I prefer the warning one.
public: --color-gbif-primary
registered: --color-gbif-primary with full opacity background and white text

CSS

   .type {
      /* --color-gbif-secondary */
      color: rgb(78,86,95);
      border: 1px solid rgb(78,86,95);
      background: white;
   }
   .private-danger {
      /* --color-gbif-danger */
      color: rgb(227,99,112);
      border: 1px solid rgb(227,99,112);
      background: rgba(227,99,112, 0.04);
   }
   .private-warning {
      /* --color-gbif-warning */
      color: rgb(255,193,8);
      border: 1px solid rgb(255,193,8);
      background: rgb(255,193,8, 0.04);
   }
   .public {
      /* --color-gbif-primary */
      color: rgb(97,168,97);
      border: 1px solid rgb(97,168,97);
      background: rgba(97,168,97, 0.04);
   }
   .registered {
      /* --color-gbif-primary */
      color: white;
      border: 1px solid rgb(97,168,97);
      background: rgb(97,168,97);
   }

@peterdesmet Thank you for your suggestions!
We're currently finalising home pages, they'll be looking something like this

https://ipt.gbif-uat.org/

@mike-podolskiy90 thanks for the update. I've had a look at the resource overview. It looks great that the functions are not folded. To make it visually more relevant, would you consider enlarge the button and place it at the top right of <div class="mt-4"></> hence below the heading and after the first line of the paragraph? (It looks too far out to me, not sure others though).

@mike-podolskiy90 That last screen cap looks much better. Thank you for taking the time to smooth the colors. It is much easier to view and navigate now.
I'd like to look through the UAT, but my login doesn't appear to be functional. I will check with you separately about that.

Thank you all for the suggestions. We've applied most of them.
IPT is almost ready and available to reviewing.

@ckotwn @dbloom @SophiePamerlon @rondlg @peterdesmet
If you happen to have time please give it a try at ipt.gbif-uat.org

Thanks, Mike. I agree with dbloom that the colors on the resource list are much reasonable now. For what I suggest about making function buttons more prominent with bigger text and color buttons, will you consider to implement? I will certainly love IPT more if that happens :)

Looks good to me! Labels on homepage are great. Showing the buttons rather than the ... is an improvement. Agree with @ckotwn that the buttons are not very prominent, but it doesn't bother me.
A very minor nitpick: I would increase the spacing between icon and text for better readability.

to:

I did this by adding margin-right: 0.2rem to .overview-action-button-icon

Thank you @peterdesmet , I'll apply that.
@ckotwn Thank you for the suggestion, but looks like it just doesn't look nice. I'd prefer to keep as it is

I don't think I have a login to the UAT to see what the buttons look like right now but maybe a compromise is to make the buttons bigger but keep them transparent (i.e. not green)?

@albenson-usgs  How it looks right now:

I can create an account for you there if you wish

Yes, please create me an account if that's not too much trouble. Thank you!

After logging in and working a bit, I do agree the buttons are a little small. I still think a good compromise would be to keep them the current color combination but make them a bit bigger.

@ckotwn Thank you for the suggestion, but looks like it just doesn't look nice. I'd prefer to keep as it is

Thanks for trying out. I can see that the bold button could steal attention from the overall light-coloured visuals.

Thank you all for your input. I'm closing the issue.


please provide git tags for the releases

Dockefile of the bids-app installs<EMAIL_ADDRESS>which suggests nice versioning but I see no tags in the clone of this repository.
I was interested to try https://github.com/INCF/bids-validator/pull/210 which was merged in 7b31778c7e9398e51f883ee9de772bfe16560f30  but it is hard now to figure out which release should I try since
$> git describe --contains --tags 7b31778
fatal: cannot describe '7b31778c7e9398e51f883ee9de772bfe16560f30'

The versions are managed here: https://github.com/INCF/bids-validator/blob/master/package.json#L3
The feature you are interested in is in all versions since 0.19.0.
Tag based versioning will come when this is finished: https://github.com/INCF/bids-validator/pull/225


Adding justified text

Scribble is great and would be even better if it could justify text. I realize this is tricky since I couldn't come up with a perfect solution.
Here's my attempt to justify text by modifying the scale on spaces within the string so that all the empty space at the end of each line is used by increasing the scale on previous spaces within the line. While it justifies most lines correctly, it's not perfect and breaks when adding formatting commands. A better solution is required.
Example of left aligned text:

Example of "justified" text:

Below is the code for the "justify_scribble_cache()" function which modifies the string within the scribble_cache to justify text. Perhaps it will be of some use for adding this feature.
function justify_scribble_cache(){

	var _scribble_cache = argument[0];
	var _page_width = _scribble_cache[@ SCRIBBLE.WIDTH];

	var _string = _scribble_cache[@ SCRIBBLE.STRING];
	var _string_mod = _string;
	var _space_width = scribble_get_width(" ");
	var _idx_mod = 0; // index modifier for manipulating _string_mod

	// Parse each line on each page to determine how much to scale each space to justify text
	var _page_num = _scribble_cache[@ SCRIBBLE.PAGES];

	for (var _page=0; _page < _page_num; _page += 1)
	{
		//var _line_num = _scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES]; // Not always correct! Check Scribble array for real answer
		var _line_num = array_length(_scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES_ARRAY]);
		if (_scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES_ARRAY][_line_num-1] == undefined)
		{
			_line_num -= 1;
		}
		var _page_width = _scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.WIDTH];

		for (var _line=0; _line < _line_num; _line += 1) // Don't scale spaces in the last line
		{
			var _start_char_line = _scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES_ARRAY][_line][@ __SCRIBBLE_LINE.START_CHAR];
			var _last_char_line = _scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES_ARRAY][_line][@ __SCRIBBLE_LINE.LAST_CHAR];
			var _char_count_line = _last_char_line - _start_char_line + 1; // index starts at 0 in scribble so +1 for index 0
			var _line_string = string_copy(_string, _start_char_line + 1, _char_count_line); // index starts at 1 for string_copy()
			var _line_width = scribble_get_width(_line_string);

			// Code hack below needed for better results. Perhaps a bug in scribble_get_width() for lines with line width from array greater than page width
			var _line_width_array = _scribble_cache[@ SCRIBBLE.PAGES_ARRAY][_page][@ __SCRIBBLE_PAGE.LINES_ARRAY][_line][@ __SCRIBBLE_LINE.WIDTH];
			if (_line_width_array >= _page_width)
			{
				_line_width = _line_width_array;
			}

			// Determine the number of spaces in line, the empty line space, and new scale for spaces for justified text
			var _space_num = string_count(" ", _line_string) - 1;
			var _empty_line_space = _page_width - _line_width;

			if (_empty_line_space <= 0)
			{
				var _space_scale_line = string_format(0.95, 1, 12); // This shouldn't be necessary but it is for better results
			}
			else if (_empty_line_space > 0)
			{
				var _space_scale_line = string_format((1 + ((_empty_line_space / _space_width) / _space_num)), 1, 12);
			}

			for (var _idx=_start_char_line + 1; _idx < _last_char_line; _idx += 1) // First character shouldn't be a space
			{
				if (string_char_at(_string, _idx) == " ")
				{
					_string_mod = string_insert("[scale,]", _string_mod, _idx + _idx_mod);
					_string_mod = string_insert(_space_scale_line, _string_mod, _idx + _idx_mod + 7);
					_idx_mod = _idx_mod + 22;
					_string_mod = string_insert("[/scale]", _string_mod, _idx + _idx_mod + 1);
					_idx_mod = _idx_mod + 8;
				}
			}
		}
	}

	return _string_mod;
}

I also added
scribble_set_line_height(scribble_get_height("t"), scribble_get_height("t"));

in the create event since increasing the scale on spaces will increase the height of text which affects line spacing.

FYI- All lines of text in the example above were properly justified (including lines 4 and 22) by preventing text from going to multiple pages using the code below.
scribble_set_wrap(page_width, -1, false);

Something strange happens when text is being formatted into multiple pages. The first few characters in the first word of the 2nd page are not being displayed.

Implemented for v7.2.0pre002

okay, i think i might have some fun with this


Fixes 'Can't modify frozen autoload_paths' issue

Summary
This PR adds before: :bootstrap_hook to view_component.set_autoload_paths initializer as a way to avoid the app loading process crashing due to frozen autoload_paths as described in #365
Other Information
I'm not sure this is the right way to fix this issue but it was the only workaround I found to start using View Components in my Rails application. I'm more than open to do any change to this PR based on your guidance on the best way to fix this problem.
Fixes #365

@ortegacmanuel might you be willing to look into the approach suggested here? https://github.com/github/view_component/issues/365#issuecomment-640779870


Puzzle cannot be opened after import

Getting a key error in puzzle_screen() line 283:
puzzle = Puzzle.from_json(session['puzzle'])

Figured out the problem.  The puzzle JSON is too big to be stored in the session:
/home/saspeh/.local/lib/python3.6/site-packages/werkzeug/wrappers.py:1116: UserWarning: The "b'session'" cookie is too large: the value was 4300 bytes but the header required 26 extra bytes. The final size was 4326 bytes but the limit is 4093 bytes. Browsers may silently ignore cookies larger than this.
  samesite=samesite

Steps I took:
pip install Flask-Session


Automatically open app with timer of 0s

.. by long pressing on them

Thanks for the suggestion! I've thought about this a little, but I'm torn on how it should be implemented. A long-press wouldn't work on gesture apps for example


[Android] Implement for supporting ICD device

Fix #29390
For sending ICD check out message in Android Controller, I add some API and callback function in Android Platform.

Could you add one java test in java example app, and run new pairing api against lit example app?

@yunhanw-google
I added it. Please review this.


Cannot connect to sockets on production

Sails version: "sails": "^1.0.2",
Node version: v10.1.0
NPM version: 5.6.0
DB adapter name: "sails-postgresql":
DB adapter version: "^1.0.1"
Operating system: mac OS HighSierra 10.13.4 (17E202)

Hi,
Connecting to sockets on dev works fine.
When going to prod I'm declaring the config in an env variable but sails doesn't allow the connection.
I've enabled a log level to read (Note the trailing slash of the url):

The env variable is read from Sails since when I delete it Sails doesn't allow to run the app as it throws an error saying that sockets allow origins is not set up.

The problem is that somehow the env variable doesn't match with the string in the query. Could it be maybe the trailing slash that it outputs in the first image?

@tomascharad the trailing slash shouldn't make a difference. Just to rule this out as a possibilty: would you try configuring your onlyAllowOrigins array in config/env/production.js in your project? (You should find it commented out here.) Just want to make sure the issue's not with setting it in a heroku config var.

Hi!
I just did what was mentioned, the problem still happens.

Pretty weird.
Can it be due to using a raw socket.io connection without a sails wrapper?

Hi, is there anything I can do to sort this out? Does this happen to you in production?

Can it be due to using a raw socket.io connection without a sails wrapper?

@tomascharad that could definitely be it, if the custom logic on top of the raw socket.io client doesn't mimic the sails.io.js client. To troubleshoot this:
First:

check https vs http in your onlyAllowOrigins -- put both if you're unsure
check that this works properly when using the normal sails.io.js client.  If not, then check the version of the sails.io.js client you're using to be sure it matches the server  (generate a new sails app and see what's bundled)

...then if it works with the sails.io.js client, then you know it's something wrong with the raw socket.io-client usage.  Either switch to sails.io.js (recommended) or continue troubleshooting your custom implementation.
If you need to use your own custom implementation:

check that you're using the right version of the raw socket.io-client
check that you're properly mimicking the behavior of sails.io.js


Add prototype landmark navigation (in DD)

Could you help out with this? @PaulPickhardt I think I could use your experience from the audio navigation/speed advisory stuff.

Works as a prototype for now. We are not going to merge this for the time being.