Oci extensions fail to install

Describe the bug
Both oci8 and pdo_oci fail to install with the following messages:
PHP Warning:  PHP Startup: Unable to load dynamic library 'pdo_oci.so' (tried: /usr/lib/php/20190902/pdo_oci.so (/usr/lib/php/20190902/pdo_oci.so: cannot open shared object file: No such file or directory), /usr/lib/php/20190902/pdo_oci.so.so (/usr/lib/php/20190902/pdo_oci.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

PHP Warning:  PHP Startup: Unable to load dynamic library 'oci8.so' (tried: /usr/lib/php/20190902/oci8.so (/usr/lib/php/20190902/oci8.so: cannot open shared object file: No such file or directory), /usr/lib/php/20190902/oci8.so.so (/usr/lib/php/20190902/oci8.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

Version

[x] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[x] v2
[ ] v1

Runners

[x] GitHub Hosted
[ ] Self Hosted

Operating systems
ubuntu-20.04
PHP versions
7.4.11
To Reproduce
  phpunit-oci8:
    name: "PHPUnit on OCI8"
    runs-on: "ubuntu-20.04"

    strategy:
      matrix:
        php-version:
          - "7.4"

    services:
      oracle:
        image: "wnameless/oracle-xe-11g-r2"
        ports:
          - "1521:1521"

    steps:
      - name: "Checkout"
        uses: "actions/checkout@v2"
        with:
          fetch-depth: 2

      - name: "Install PHP"
        uses: "shivammathur/setup-php@v2"
        with:
          php-version: "${{ matrix.php-version }}"
          extensions: "oci8"
          coverage: "pcov"
          ini-values: "zend.assertions=1"

      - name: "Cache dependencies installed with composer"
        uses: "actions/cache@v2"
        with:
          path: "~/.composer/cache"
          key: "php-${{ matrix.php-version }}-composer-locked-${{ hashFiles('composer.lock') }}"
          restore-keys: "php-${{ matrix.php-version }}-composer-locked-"

      - name: "Install dependencies with composer"
        run: "composer install --no-interaction --no-progress --no-suggest"

      - name: "Run PHPUnit"
        run: "vendor/bin/phpunit -c ci/github/phpunit/oci8.xml --coverage-clover=coverage.xml"

      - name: "Upload coverage file"
        uses: "actions/upload-artifact@v2"
        with:
          name: "${{ github.job }}-${{ matrix.php-version }}.coverage"
          path: "coverage.xml"

  phpunit-pdo-oci:
    name: "PHPUnit on PDO_OCI"
    runs-on: "ubuntu-20.04"

    strategy:
      matrix:
        php-version:
          - "7.4"

    services:
      oracle:
        image: "wnameless/oracle-xe-11g-r2"
        ports:
          - "1521:1521"

    steps:
      - name: "Checkout"
        uses: "actions/checkout@v2"
        with:
          fetch-depth: 2

      - name: "Install PHP"
        uses: "shivammathur/setup-php@v2"
        with:
          php-version: "${{ matrix.php-version }}"
          extensions: "pdo_oci"
          coverage: "pcov"
          ini-values: "zend.assertions=1"

      - name: "Cache dependencies installed with composer"
        uses: "actions/cache@v2"
        with:
          path: "~/.composer/cache"
          key: "php-${{ matrix.php-version }}-composer-locked-${{ hashFiles('composer.lock') }}"
          restore-keys: "php-${{ matrix.php-version }}-composer-locked-"

      - name: "Install dependencies with composer"
        run: "composer install --no-interaction --no-progress --no-suggest"

      - name: "Run PHPUnit"
        run: "vendor/bin/phpunit -c ci/github/phpunit/pdo_oci.xml --coverage-clover=coverage.xml"

      - name: "Upload coverage file"
        uses: "actions/upload-artifact@v2"
        with:
          name: "${{ github.job }}-${{ matrix.php-version }}.coverage"
          path: "coverage.xml"

Expected behavior
No crash, extension installs cleanly
Screenshots/Logs
https://github.com/doctrine/dbal/pull/4355/checks?check_run_id=1270725004#step:4:16
https://github.com/doctrine/dbal/pull/4355/checks?check_run_id=1270725081#step:4:16
Are you willing to submit a PR?
I have no idea what is wrong here, so no.

@greg0ire Fixed in eaaab1c

It works again, thanks a lot!


Create helper function to get transceiver name

Create helper function to get transceiver name for each vendor. Fixes optics_power_and_bias_current_test
Test successfully ran on hardware.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1462

Relevant Lines:
2012

💛  - Coveralls


tokenizer suggestions

I have a couple of suggestions for the tokenizer API -- things that I have needed to work around here: https://github.com/ml-explore/mlx-swift-examples/blob/main/Libraries/LLM/Tokenizer.swift

add eosToken / eosTokenId to the Tokenizer protocol

this is needed to know when to stop producing tokens
Tokenizer already has unknownToken
I don't know if any of the other special tokens should be exposed, e.g. bosToken

have a way to add to TokenizerModel/knownTokenizers or otherwise handle unknown tokenizers

right now it would probably be sufficient to map to "PreTrainedTokenizer": BPETokenizer.self
but in the future this might need to be more flexible
TokenizerModel is internal as are the various classes like BPETokenizer
in my workaround I mapped string -> string, e.g. "Qwen2Tokenizer": "PreTrainedTokenizer", which is perhaps the right level -- not exposing too much of the implementation
anyway, some kind of API to allow registration of overrides like this or perhaps just "PreTrainedTokenizer" as a fallback for now

If these fit in with the vision for the tokenizer API, please consider them!
Thanks

Expose eos: +1, I saw your use in mlx-swift and it makes sense. I'll open a PR soon.
Also thought about the fallback tokenizer method but thought it was better to explicitly fail on unsupported tokenizers. A mechanism for the user to register overrides does look interesting!

Opened https://github.com/huggingface/swift-transformers/pull/70 and https://github.com/ml-explore/mlx-swift-examples/pull/28 to address the first topic.


'Authorize' or 'Authorization' not valid in JSON path

Environment

Nuget Package: JsonPath.Net
Nuget Version: 0.1.2
OS: Windows 10
.Net Target: .NET 6.0

Describe the bug
Any usage of the phrase 'Authorize' or 'Authorization' returns false when calling JsonPath.TryParse
To Reproduce
In the immediate window or in a unit test the following give different results:
Failed TryParse
var result = JsonPath.TryParse("$.authorize.sms.title", out var path)
result = false
Successful TryParse - changed 'z' to 's'
var result = JsonPath.TryParse("$.authorise.sms.title", out var path)
result = true
Expected behavior
Both are valid JSON paths and TryParse should return true for any usage of the phrase 'authorize' or 'authorization'

Wow that's a weird one. Thanks for reporting!  I'll set up a test and have a look.

@adamsproul what are your local culture settings?  Both authorize and authorise work for me.
I'm not sure how this would fail.  I'm not doing any kind of spell check or known word check.  It's literally parsing the property name from between the .s.

@gregsdennis  - I could not replicate the behavior in its own project, I did however look to see if there was more detail by just doing a Parse where the original exception is occurring and I get the below exception.
`
JsonPath.Parse("$.authorize.sms.title")
'JsonPath.Parse("$.authorize.sms.title")' threw an exception of type 'Json.Path.PathParseException'
Data: {System.Collections.ListDictionaryInternal}
HResult: -2146233088
HelpLink: null
Index: 9
InnerException: null
Message: "Could not identify selector"
Source: "JsonPath.Net"
StackTrace: "   at Json.Path.JsonPath.Parse(String source)"
TargetSite: {Json.Path.JsonPath Parse(System.String)}
`
That looks like it is the 'z' character it doesn't like. I tried using a virtual keyboard to enter the z in case there was anything weird with it and I still see the same behavior. Wherever the 'z' character goes the exception index changes.
It does not seem to be a limitation with the word 'authorize' but instead something strange in our code that is treating 'z' differently.
We can probably close this ticket for now, and if I can find a good way to replicate it I will re-open.
I appreciate your help

Okay.  Thanks for checking.  I look forward to your replication case, if you find it.


Upgrade all executors to >= 2.0.19

Recently @jacobowitz merged the gRPC runtime to the core.
It allows having Kubernetes managed replicas and will be part of the 2.0.19 release.
Please upgrade all executors to >= 2.0.19

It's unnecessary to upgrade them manually. Hubble will build it on-demand.


Missing null check when trimming whitespace

Please see attached images:

Fixed in https://github.com/peters/LiteDB/commit/0dcd668255708501961148a7c451ce13f5dc5380

Hi @peters, thanks for found this bug, but the bug is in another castle :) When BsonValue is Type == BsonType.String RawValue can be null (if RawValue is null than Type must be BsonType.Null). Now, I need found how did you initialize a BsonValue with Null value but Type marks as String.


Add Samples Entry

We should add an explanation of what Samples are and how to use them.
https://github.com/daytonaio/daytona/pull/954
Additionally, a guide on how to setup your own samples can be provided (how the index json should be formatted).

@Tpuljak yes on samples and how to use them.
For now can skip setup your own.


updated Esp32, merged for testing branch

since the last PR was closed #47 and was intended to merge ESP32 support on master branch
I've issued this new pull resquest to be merged on the testing branch

The library seems to work well with ESP32
but for _TASK_SLEEP_ON_IDLE_RUN, the light sleep mode of the ESP32 is not working as expected (by now), disables connectivity and freezes the MCU, so I've actually implemented with a safe delay(1)  until further framework updates
you can merge now (in testing or even in master)

Yeah, I ran into similar issues with 8266 - their understanding of a "light" sleep is different from AVR.
We can just use the same process as 8266 for now, no?

yes is what I did but the process is not the same as for the 8266, in that delay there are some specific features enabled via "user_interface.h" header
and they don't exists for ESP32 (not analogue found)
so the solution is a standard delay or don't use the _TASK_SLEEP_ON_IDLE_RUN feature at all (maybe it is the best option)
you can merge and close

Thank you for your help!
If not a secret, what are you using TS for?

it is simply and old project based on esp8266 I'm tryng to port to ESP32
The MCU is remotely controlling my heatpump and my home room temperatures in a "cleaver" way

Cool

OK. Done with the merge. Should be OK now.

when will you merge testing to master branch?

Done


instruction video seems to be legacy

Is the youtube instruction link legacy?

No, it's a joke :)
Thanks,
Kenneth Fisher, Microsoft Data Platform MVP
www.sqlstudies.com http://www.sqlstudies.com
On Thu, Jan 28, 2021 at 4:31 PM Ben McNeill<EMAIL_ADDRESS>wrote:

Is the youtube instruction link legacy?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlstudent144/SQL-Server-Scripts/issues/17, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZEU3B57QHOM72PIN3KBG3S4HQVBANCNFSM4WX3JZAQ
.

No, it's a joke :)
Thanks,
Kenneth Fisher, Microsoft Data Platform MVP
www.sqlstudies.com http://www.sqlstudies.com
On Thu, Jan 28, 2021 at 4:31 PM Ben McNeill<EMAIL_ADDRESS>wrote:

Is the youtube instruction link legacy?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlstudent144/SQL-Server-Scripts/issues/17, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZEU3B57QHOM72PIN3KBG3S4HQVBANCNFSM4WX3JZAQ
.

The instructional video is as intended.

The instructional video is as intended.


Plugin does not work on IE browser

The implementation for lrStickyHeader does not work for IE browser. Things like ScrollTop are used, which are not supported for IE. Can you please make this working for IE browsers as well, at least IE11 and higher versions?

nope sorry, however you can submit a pull request which I will likely merge but I don't want to spend time working on browser I don't use

problem is as simple as "window.scrollX and window.scrollY compatibility on IE 11"
https://github.com/imgix/drift/issues/33


Quote CMAKE_BUILD_TYPE in CMakeLists.txt to allow it being unset.

Right now, cmake will fail when called without defining CMAKE_BUILD_TYPE with
CMake Error at CMakeLists.txt:15 (if):
  if given arguments:

    "STREQUAL" "Debug"

  Unknown arguments specified

Quoting the variable will make cmake pass. This is super-trivial and maybe not what you want.
Then I would suggest to set a default build type instead, or ignoring this pull request. :-)

Thank you for noticing this! Kind of on the fence about this, the error will probably make people actually read build.md :)


Vue-admin backstage management system template left navigation bar can not be added to solve!

I want to use your Vue background management model, but the content is a little bit less, I want to add content in the left navigation bar and head, but I can not add it, solve!

this repository will be Archive,please see https://github.com/huanent/vue-quickstart
you can add left navigation bar item in https://github.com/huanent/vue-quickstart/blob/master/src/api/Menu.js


Policy Settings reference is incorrect.

Under the section "Policy settings in preset security policies" it states that

The Standard, Strict, and Built-in protection policy setting values, including the associated quarantine policies, are listed in the feature tables in Recommended settings for EOP and Microsoft Defender for Office 365 security.

However, this is not correct because that page shows that the Standard settings for the First Contact Alert is OFF (EnableFirstContactSafetyTips = FALSE). Recently we noticed in all our tenants that this is now ON (EnableFirstContactSafetyTips = TRUE)

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

ID: 4f6f1cf3-a121-3c6e-9380-79440f4c6671
Version Independent ID: 9b1bc5d1-8ecc-d0f9-092e-325c6acff4fe
Content: Preset security policies
Content Source: microsoft-365/security/office-365-security/preset-security-policies.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@jvaught48, confirmed. Unclear if this change is intentional, but I updated the documentation accordingly.
Thanks for the feedback.
Closing

@jvaught48, confirmed. Unclear if this change is intentional, but I updated the documentation accordingly.
Thanks for the feedback.
Closing

Awesome thank you! Should it also be changed for "Strict"? Seems odd that for Standard it would be true but not for Strict. However, I personally did not check it on Strict, so I'm not actually sure.


I have solved some resolution glitch problems

All the changed are on the commit message

The first image is mine with a 50% resolution

The second one is urs with 50% resolution

As you can already see in your attached image (2nd) that there is an issue with the taskbar. Please fix this and open a pull request.
Thanks for your contribution.
reference:


grpc-client-cli: 1.13.1 -> 1.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/vadimi/grpc-client-cli/releases.
meta.description for grpc-client-cli is: "generic gRPC command line client"
meta.homepage for grpc-client-cli is: "https://github.com/vadimi/grpc-client-cli"
meta.changelog for grpc-client-cli is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.14.0 with grep in /nix/store/7rq7cx68mkqpfzvb5fivgn8rrg55vdx2-grpc-client-cli-1.14.0
found 1.14.0 in filename of file in /nix/store/7rq7cx68mkqpfzvb5fivgn8rrg55vdx2-grpc-client-cli-1.14.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
grpc-client-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7rq7cx68mkqpfzvb5fivgn8rrg55vdx2-grpc-client-cli-1.14.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7rq7cx68mkqpfzvb5fivgn8rrg55vdx2-grpc-client-cli-1.14.0
ls -la /nix/store/7rq7cx68mkqpfzvb5fivgn8rrg55vdx2-grpc-client-cli-1.14.0/bin

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

1 package built:

grpc-client-cli

Maintainer pings
cc @Philipp-M for testing.

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

1 package built:

grpc-client-cli


slash-no-division

What is the problem you're trying to solve?

My current frontend tooling (w/ Dart Sass) doesn't like division with /:
[CRA] 21 │   padding: 0 ($COL_SPACING / 2);
[CRA]    │               ^^^^^^^^^^^^^^^^
[CRA]    ╵
[CRA]     src/client/styles/modules/Foo.module.scss 21:15  root stylesheet
[CRA]
[CRA] DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.
[CRA]
[CRA] Recommendation: math.div($COL-SPACING, 2)
[CRA]
[CRA] More info and automated migrator: https://sass-lang.com/d/slash-div

It currently logs a runtime warning, but presumably in the future it will completely break.
This will probably be caught by our tests, but it would be great if it could also be handled by styelint.

What solution would you like to see?

A new rule that shares the opinion of Dart Sass, squiggling offending uses of the /.
Is this something that stylint-scss  would be interested in?
https://sass-lang.com/documentation/breaking-changes/slash-div
(originally from https://github.com/stylelint/stylelint/issues/5368)

@jrr Thanks for this! We usually try to avoid adding rules that duplicate the work that the compiler is already doing.
I understand that it would be nice to catch these already before hitting the compiler, but in addition to doing things twice, a big problem is that the rule might get out of sync with the warning that the compiler is giving. That's why I would prefer not to add such rules to the library.

Alright, that makes sense, thanks. I could see the difficulty in maintaining a second implementation that agrees perfectly with the reference implementation.
Maybe one day another extension (perhaps https://github.com/microsoft/vscode-css-languageservice ) could provide squiggles right out of the sass compiler.

I would be in favor of adding this to stylelint-scss.
I wouldn't expect much maintenance against the compiler because the warning will be removed from Dart Sass 2.0.0 as stated in the deprecation warning. So after Dart Sass 2.0.0 is removed, no maintenance is required where as developers could still benefit from the linter warning when migrating their heads to the new style.

@ahukkanen I will try to explain my view on this, so maybe that will help you to see why adding such rule does not make sense.
The stylelint-scss is mostly a collection of rules that help to keep your styles consistent by either enforcing some kind of syntax, or disallowing the use of certain features of the language.
For me this kind of rule does not really fall into that normal rule category. The rule would serve as a "migration tool" to the new version of the Sass compiler.
The risk with adding the rule is that there might be false positives or false negatives for what the rule is reporting versus what the compiler warns about, and the rule might get quite complex. Even if it would work perfectly, it seems a bit silly that the rule would just be pointing out the same things that compiler is already telling the user.
In addition to that, the Sass team is already providing all the necessary info and tools to migrate to the new version:

There is a warning that will point out the exact place that needs to be migrated. Later on that warning will be turned into an error and the code will stop compiling, forcing the migration to be done.
There is a website that gives all the info and examples about the breaking change: https://sass-lang.com/documentation/breaking-changes/slash-div
There is an official migration tool that you can use to automatically migrate your styles to the new format to get rid of the warnings: https://sass-lang.com/documentation/breaking-changes/slash-div#automatic-migration

In addition to that, the Sass team is already providing all the necessary info and tools to migrate to the new version:

They're providing everything except for editor squiggles ;)
For better or worse, this project seems to be the default recipient of "there ought to be a squiggle" issues like this one.
Maybe a note on the Readme could map out the ecosystem a little bit, and suggest where to take issues that fall outside this project's scope? (Is there a different project that could/should be responsible for adding VS Code squiggles for that dart-sass warning? I still don't know.)

For better or worse, this project seems to be the default recipient of "there ought to be a squiggle" issues like this one.
Maybe a note on the Readme could map out the ecosystem a little bit, and suggest where to take issues that fall outside this project's scope? (Is there a different project that could/should be responsible for adding VS Code squiggles for that dart-sass warning? I still don't know.)

I agree that stylelint provides a much better developer experience than using the compiler for the errors. Even if the rule does not fit stylelint-scss, it would just require a bit of effort to write a custom stylelint plugin that does the same thing.
I have written multiple stylelint plugins, and it would probably take 2-3 hours of work to add the rule, write a test suite, and to add the boilerplate (CI etc.) for the Github repo.

My main concern is the CI pipeline, when we are fixing this dart sass issue for the project. If someone introduces a new slash division after fixing it, it may go unnoticed because there is no way to catch that in the CI.
And there we cannot even grep the webpack output because there are still external dependencies that produce these warnings that are outside of the project's control.
There's still the possibility to write some rather complex webpack output parser that will automatically detect which warnings come from external dependencies and which come from the project itself. Or just hope for the best.
It would be much easier in such cases to rely on stylelint.

@ahukkanen what about running the migration tool against your project? https://sass-lang.com/documentation/breaking-changes/slash-div#automatic-migration

@kristerkari Yes, that's what my PR is doing but there are external dependencies that still need to be fixed. And that can take from n days to x years according to my previous experiences.

@ahukkanen the problem that you have is a very typical software problem when migrating to a newer version that has a breaking change. If you have external dependencies with breaking changes, then those need to be migrated to the new version regardless of if there is a stylelint rule or not.
So here's my suggestion:

Run the migration tool against your project.
Run the migration tool against an external library with the problem and contribute a PR to that library.
OR build your own stylelint plugin that can be used as tool to find the styles that need migration.

Yep, I understood your point of view @kristerkari.
I was only trying to raise the point that it would be a great help if we had this already incorporated into stylelint.
Based on this discussion it is clear it won't be part of stylelint-scss, I understand that.

I also understand how difficult it is to do codebase migrations to newer versions with breaking changes. It takes a lot of time and any kind of tooling will be helpful when doing that.
It's just that stylelint is not a compiler/parser/analyzer, so it should not be used as a tool to validate whether a code compiles or not.
The Sass compiler can have new versions that make some code invalid that was previously working just fine. It's the Sass team that has the compiler/tools that decides which code is valid and which is not, and to provide the necessary tools to do the migration to newer versions with breaking changes.


Use constexpr statements over enable_if dispatched functions

The conventional if statements with "constexpr" is more readable than complicated enable_if statements. Additionally, the produced object files are smaller due to shorter symbols names.

@blowekamp I'm sorry I don't have time to review the entire PR thoroughly, but you don't need to wait for me. I very much like its direction, and I'm glad I could help with a few suggestions 👍


Dockerfile: switch to almalinux 8 for the base image

What does this PR do
attempt to resolve #22 by enabling Almalinux as the base image

Let's merge https://github.com/metal-toolbox/ironlib/pull/22 first

@Mergifyio rebase


west.yml: Update libmetal and open-amp for v2024.10.0 release

Update to the last release of open-amp and libmetal libraries

For the time being, this PR is in draft to run the CI as a non-regression test for the OpenAMP release.
It will be updated after OpenAMp v2024.10 release


BigNum.div with precision is broken

fun div(other: BigNum, precision: Int): BigNum
is broken, it does not take into account precision parameter at all.
The implementation should be something like:
operator fun div(other: BigNum, precision: Int = other.int.significantBits / 2): BigNum {
return BigNum(int * (10.bi pow (other.scale + precision)) / other.int, scale) * BigNum(1.bi, precision)
}

This is kinda old issue, sadly :disappointed:, but I would provide a minimal reproduce for this:
Not working:
val bi1 = BigNum("1").convertToScale(otherScale = 10)
val bi2 = BigNum("2").convertToScale(otherScale = 10)
assertEquals(
    expected = 0.5.bn,
    actual = bi1 / bi2
)```

Working:
```kotlin
val bi1 = BigNum("1").convertToScale(otherScale = 1)
val bi2 = BigNum("2").convertToScale(otherScale = 1)
assertEquals(
    expected = 0.5.bn,
    actual = bi1 / bi2
)

assertEquals("5000000000".bi, "100000000000000000000".bi / "20000000000".bi)

expected:<5000000000> but was:<705032705>

It seems to be a problem with BigInt division in this case


How to understand the Structural re-parameterization of a RepVGG block

Hi! Really nice work!
I was trying to understand the re-parameterization part

But what I dont get is how identity of 3 X 3 kernel becomes 2 X 1  in the end. I mean, why does it work without information loss?
Any answer is appreciated

@jyang68sh
First, consider that the identity branch (in yellow) does not have any parameter.
If we want to represent this operation (the identity) we can construct a 3x3 kernel with a weight of 1 in the central cell as shown in the figure. The 2X1 kernel that is see is the bias vector.
Why do only two filters out of four have this weight? Because we are considering an example with C_in = 2 and C_out = 2.

@jyang68sh First, consider that the identity branch (in yellow) does not have any parameter. If we want to represent this operation (the identity) we can construct a 3x3 kernel with a weight of 1 in the central cell as shown in the figure. The 2X1 kernel that is see is the bias vector.
Why do only two filters out of four have this weight? Because we are considering an example with C_in = 2 and C_out = 2.

Hi thanks for the reply.
Sorry for the late response. This solves my question


After run getstorybook, vue-loader can't find by npm.

{
  "name": "vue-skeleton",
  "version": "0.0.4",
  "description": "A Vue Base Components",
  "author": "zhaozhe<EMAIL_ADDRESS>  "license": "MIT",
  "main": "dist/index.js",
  "style": "dist/css/index.css",
  "keywords": [
    "plugin",
    "frontend",
    "components",
    "vue",
    "vue ui",
    "vue components",
    "vue plugin"
  ],
  "files": [
    "src/components",
    "src/styles",
    "dist/main",
    "dist/styles"
  ],
  "scripts": {
    "storybook": "start-storybook -p 6006",
    "build-storybook": "build-storybook"
  },
  "bugs": {
    "url": "https://github.com/VueBaseUi/vue-skeleton/issues",
    "email"<EMAIL_ADDRESS>  },
  "repository": {
    "type": "git",
    "url": "https://github.com/VueBaseUi/vue-skeleton"
  },
  "dependencies": {
    "vue": "^2.5.16"
  },
  "devDependencies": {
    "css-loader": "^0.28.11",
    "vue-loader": "^14.2.2",
    "vue-template-compiler": "^2.5.16"
  },
  "engines": {
    "node": ">= 4.0.0",
    "npm": ">= 3.0.0"
  }
}

$ npm i
$ npm list vue css-loader vue-template-compiler vue-loader
$ getstorybook
$ npm list vue css-loader vue-template-compiler vue-loader

But I can find it by cd node_modules && ls vue-loader.

What info should I provide？By the way, vesion is 3.4.6.
╭─zhaozhe@zhaozhe ~/Demo/vue-skeleton/node_modules ‹ruby-2.2.1› ‹master*›
╰─➤  getstorybook -V
3.4.6

I did a little poking around and it seems to work fine with yarn. I suspect it has to do with the package-lock.json file that npm uses. Can you dig into that and report back? It might be a bug in Storybook CLI. Thanks!

How could I show you the package-lock.json ?
It is a little big.


Normalize casing of enum variants

What is wrong?
We currently use all these different forms of enum casing when we'd ideally be only using a single form.
Snake Case
class Thingy(Enum):
    some_thing = auto()
    other_thing = auto()

Capitalized Snake Case
class Thingy(Enum):
    SOME_THING = auto()
    OTHER_THING = auto()

Pascal Case
class Thingy(Enum):
    SomeThing = auto()
    OtherThing = auto()

How can it be fixed

Decide on casing
Correct all places that derive from Enum
Put the rule into our style guide

My vote is on the third option (PascalCase). @ethereum/snake-charmers

I'm in favor of still allowing the variant of all caps for the enum values in cases where we mostly only handle the values (as opposed to code that actually instantiates instances of the enum).  It's nice to be able to treat the enum values as constants.

@pipermerriam maybe that's a good argument to just settle with CAPITALIZED_SNAKECASE then? I think it's good if all follow the same style without exceptions.

Yeah, I don't mind the capitalized snake case style.  I recently ran into this problem when trying to write some code in Rust.  The official preferred style in Rust is PascalCase.  However, there are already lots of things that are already PascalCase and having enum variants the same way doesn't distinguish them visually very much.  So I opted to use CAP_SNAKE instead, especially since you can do use Enum::*; in Rust.  In that case, the CAP_SNAKE case makes it more obvious where particular identifiers are coming from.

Is this open? I'd like to give it a shot. (I assume there's consensus on CAP_SNAKE.)

Go for it
Sent from ProtonMail mobile
-------- Original Message --------
On Oct 3, 2019, 8:48 AM, wschwab wrote:

Is this open? I'd like to give it a shot. (I assume there's consensus on CAP_SNAKE.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

This was addressed in #1219


Recommend increasing body font size for printed book to 11pt or 12pt

@nmegill -
I think we should consider increasing the main body font size for the book from 10pt (current) to 11 or 12.
Currently the book is 10point, which is rather small for a book. I didn't see this problem earlier, sorry about that.  Earlier, when I read it on the screen or printed it to 8.5x11" paper, it was quite readable.  HOWEVER, what I didn't realize is that my PDF reader by default scales to the screen or page... so I was never seeing it at the size it will be in the printed book.
When I tell the system to not scale to the page size, 10pt is barely readable to me & I can only read it slowly (or take off my glasses and put my nose to the book).  I suspect others will have that problem too.  For a long work (like a book) a too-small font seems like a problem.
I tried out 3 different font sizes to compare the page counts:

10pt: 241 pages.
11pt: 289 pages
12pt: 327 pages

At least one source says body text should be 10..12 inclusive. Hardcovers can be up to 800 pages, so there's no problem printing any of those.
Of the 3 options I'm leaning towards 11pt.  That is less likely to lead to bad line breaks, and it makes the book weigh a little less.  I think it's a reasonable compromise for a font size.
If we do switch, we'll need to recheck the result for bad line breaks.  However, I've tried to be careful to avoid things that presume any one width or font size, so it should not be a problem.
Comments?

I looked at several technical books that I have, mostly paperback, and they seem to use around 10pt (sometimes even smaller) when they are a "smaller" (6x9-ish) size, and a larger font when they are expensive and heavy 8.5x11-ish college textbooks with glossy paper.  Novels often use a larger font, but that is a different category.  Perhaps you can look at some typical books in your collection to compare.
My original goal was a small, lightweight book that would be easy to carry around.  Hardcover defeats that to a certain extent, and ~300 pages even more so.  Neither is my personal preference.  But since I'm not the primary market, I will go along with what others prefer.  I think the question should be posed to the metamath group.

I tried to get a fractional font (10.5), but it turns out that's not so easy in LaTeX.  You can easily ask for it:
usepackage[fontsize=10.5]{scrextend}

... but it won't work without regenerating fonts (ugh), and there are warnings about it (because the document class doesn't fully know about it).
I'll ask the group.  I think there's a modest preference for hardcover; it's more durable, and it also has the advantage of making it easier to "take seriously".  As you note, hardcover already makes it less lightweight.  I think its' 10pt vs. 11pt, and there are advantages to each.  I think 11pt is a little better, but there are clearly pluses and minuses to each.

Looks like I'm the only one who would prefer 11pt, no one else seems to care.  My eyesight problems are my own I guess :-).  Switching to 11pt would require some fixes of some verbatim text, which is hard to justify if no one else cares.
It's easier to go with "what's already there", so I think we'll just do that.  So I'm closing this, and we'll leave it all as-is.


Customizeable Axis Title Rendering

In order to make 2-axis (opposing axis) charts a bit more readable than this https://jsfiddle.net/tah74jm4/ (which line belongs to which label?), the designer wanted a color indication on the label for each line. I know there are legends, however that takes up additional space and is also not very flexible in positioning the legend items. In this case, a legend next to each label would better indicate which values belong to which line.
One option we were considering was coloring the label in the matching color of the line, however since the colors can be dynamic based on user selection, there could be colors which would make the label text hard to read. So this option was thrown out.
The option chosen was a black label with a dot next to it in the color of the line, as you can see here:

This is a screenshot of an actual graph, which I was able to generate by making a slight modification in the draw function in core.scale.js in the  scaleLabel.display part:
if (scaleLabel.display) {
  // Draw the scale label
  scaleLabelX = options.position === 'left' ? this.left + (scaleLabelFontSize / 2) : this.right - (scaleLabelFontSize / 2);
  scaleLabelY = this.top + ((this.bottom - this.top) / 2);
  var rotation = options.position === 'left' ? -0.5 * Math.PI : 0.5 * Math.PI;

  // added "if-condition" allows for multi-colored label
  if (scaleLabel.labelString instanceof Array) {
    var x = 0;
    var fullText = '';
    var fullTextOffset;
    var labelOffset;

    context.save();

    helpers.each(scaleLabel.labelString, function (obj) {
      fullText += obj.text;
    });

    fullTextOffset = context.measureText(fullText).width / 2;
    labelOffset = options.position === 'left' ? fullTextOffset : fullTextOffset * -1;

    context.translate(scaleLabelX, scaleLabelY + labelOffset);
    context.rotate(rotation);
    context.font = scaleLabelFont;
    context.textBaseline = 'middle';

    helpers.each(scaleLabel.labelString, function (obj) {
      context.fillStyle = obj.color;
      context.fillText(obj.text, x, 0);
      x += context.measureText(obj.text).width;
    });

    context.restore();
  } else {
    context.save();
    context.translate(scaleLabelX, scaleLabelY);
    context.rotate(rotation);
    context.textAlign = "center";
    context.fillStyle = scaleLabelFontColor; // render in correct colour
    context.font = scaleLabelFont;
    context.textBaseline = 'middle';
    context.fillText(scaleLabel.labelString, 0, 0);
    context.restore();
  }
}

This would allow me to pass in an Array of Objects into the labelString as opposed to just a String. This looks like the following:
'yAxes': [{
  'id': 'y-axis-1',
  'type': 'linear',
  'position': 'left',
  'scaleLabel': {
    'display': true,
    'labelString': [{
      'text': '● ',
      'color': '#fc6062'
    }, {
      'text': 'My Left Label Text',
      'color': '#000'
    }],
    'fontFamily': 'AB',
    'fontColor': '#000',
    'fontSize': 11
  },
}, {
  'id': 'y-axis-2',
  'type': 'linear',
  'position': 'right',
  'scaleLabel': {
    'display': true,
    'labelString': [{
      'text': '● ',
      'color': '#4dc1e7'
    }, {
      'text': 'My Right Label Text',
      'color': '#000'
    }],
    'fontFamily': 'AB',
    'fontColor': '#000',
    'fontSize': 11
  }
}]

Obviously, a change like that should not be done directly in the library. If I were to create a custom Scale though, I would have to override the whole draw function, which is not ideal either as there is a lot of code in there which might change with library versions going forward.
Question is, how would I be able to implement something like this in the least intrusive way? Any suggestions would be greatly appreciated, thanks!

One idea would be to factor out a drawLabel function. The current implementation would do what we currently do. Then only that function could be overridden. The challenge would be figuring out the API to that function so that we don't have a lot of duplicated code for getting config options, etc.

Thanks for the suggestion! And yes, good point, that does get a bit tricky with the API. I'll give this some thought...

If anyone is wanting to implement this, the idea is to replace these lines with a separate function that could be overridden to provide this behaviour. Shouldn't be too hard to do, the key will be documenting the API and explicitly making this function for public use.

Hi , Is this issue is open , i want to work on it.


Readme points to the wrong file for modeline stuff

I guess you moved it over to https://github.com/hlissner/.emacs.d/blob/master/core/core-modeline.el, the readme points to the core-ui file

I'm confused. Where do you see a core-ui link in the readme? There should be a link to my modeline file in either case though. I will add it.

I updated the readme a while ago, so I'll consider this fixed.


🐛 [firebase_messaging] background message handler is not being invoked on a 'release' build on flutter 2.10.0+

Bug report

The background message handler is not being invoked on a 'release' build using flutter 2.10.0 to 2.10.3 on Android.
On flutter 2.8.1 and older versions I don't see this issue.
The issue occurs on multiple versions of firebase_messaging and firebase_core.  The most recent versions I have tested are (11.2.11) and firebase_core (1.13.1).
I have only tested on Android.
I have tested on a physical device and also on the Android emulator, running Android API 28.
The issue only happens on a 'release' build of the app, a 'debug' build works as expected.
In my working example the app is subscribing to a topic, and the FCM message is a data message sent with high priority - so should be delivered to the background message handler, and is in the debug build.

Steps to reproduce
The issue can easily be reproduced using a new flutter android studio project, and doing the bare minimum to make firebase messaging work.
In my case I am using Android Studio 2021.1.1 Patch 1

create a new flutter project
follow the instructions at https://firebase.flutter.dev/docs/overview/ to setup your project to use firebase messaging
add firebase_messaging and firebase_core to your pubspec.yaml
add your app to your firebase project
release apk built with flutter build apk --release --obfuscate --split-debug-info build/app/outputs/debug --shrink --split-per-abi
APK installed with adb install build/app/outputs/apk/release/app-x86_64-release.apk
When running the test app, filter the output of logcat on the string 'XXX' to see when a message is received
example main.dart below is the standard flutter demo, but with firebase messaging enabled.  It just logs when an FCM message is received with the text XXX for easy filtering of logcat

Thank you!
Click To Expand main.dart
import 'package:flutter/material.dart';
import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';
import 'package:firebase_messaging/firebase_messaging.dart';

Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  print("XXX: Handling a background message: ${message.messageId}");
}

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
  await FirebaseMessaging.instance.subscribeToTopic('test-topic');
  FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);
  FirebaseMessaging.onMessage.listen((RemoteMessage message) {
    print('XXX: Got a message whilst in the foreground!');
  });

  runApp(const MyApp());
}

// Everything below this line is just the standard flutter demo app

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Expected behavior
The background message handlder (_firebaseMessagingBackgroundHandler) should be called in 'release' mode when receiving a firebase message.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
martin@ost:/app$ flutter doctor -v
[✓] Flutter (Channel stable, 2.10.3, on Ubuntu 20.04.3 LTS 5.13.0-30-generic, locale en_US)
    • Flutter version 2.10.3 at /app/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (2 weeks ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /home/martin/Android/Sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /app/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 2021.1)
    • Android Studio at /app/android-studio
    • Flutter plugin version 64.1.2
    • Dart plugin version 211.7798
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.64.2)
    • VS Code at /usr/share/code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (1 available)
    • Android SDK built for x86 64 (mobile) • emulator-5554 • android-x64 • Android 9 (API 28) (emulator)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
martin@ost:~/StudioProjects/test_app$ flutter pub deps -- --style=compact
Dart SDK 2.16.1
Flutter SDK 2.10.3
test_app 1.0.0+1

dependencies:
- cupertino_icons 1.0.4
- firebase_core 1.13.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_messaging 11.2.11 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta typed_data vector_math sky_engine]

dev dependencies:
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.0
- charcode 1.3.1
- clock 1.1.0
- collection 1.15.0
- fake_async 1.2.0 [clock collection]
- firebase_core_platform_interface 4.2.5 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_messaging_platform_interface 3.2.1 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.2.9 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta typed_data vector_math]
- js 0.6.3
- lints 1.0.1
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.3
- meta 1.7.0
- path 1.8.0
- plugin_platform_interface 2.1.2 [meta]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.8 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- vector_math 2.1.1

Same issue

Please take a look at #8301, maybe it's related?

Same issue!

flutter build apk --release --obfuscate --split-debug-info build/app/outputs/debug --shrink --split-per-abi

Can you try without --obfuscate and see if it helps ? I am just trying to think if this flag is causing anything unusual.

Having the same issue :/

flutter build apk --release --obfuscate --split-debug-info build/app/outputs/debug --shrink --split-per-abi

Can you try without --obfuscate and see if it helps ? I am just trying to think if this flag is causing anything unusual.

I just tried removing --obfuscate and --shrink too and the issue is still there.
Full command run was:
flutter build apk --release --split-debug-info build/app/outputs/debug --split-per-abi

In my working example the app is subscribing to a topic, and the FCM message is a data message sent with high priority

Does sending a notification message using FCM work ? or is this specific to data message only ?

In my working example the app is subscribing to a topic, and the FCM message is a data message sent with high priority

Does sending a notification message using FCM work ? or is this specific to data message only ?

I just tested sending a notification message and it has the same issue.

Everyone who is facing this issue, please upvote original issue description instead of commenting same issue. This will help the team to prioritise based on number of upvotes.

Using the sample code provided in release mode and running with latest plugin version and latest stable, I observed that Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {   print("XXX: Handling a background message: ${message.messageId}"); }
Isn't getting called.
There's a similar issue reported for iOS and some comments indicate that in release mode too, the handler isn't getting called.
Labeling it for further investigation from the team.
/cc @russellwheatley @Salakar

 stable flutter doctor -v

[✓] Flutter (Channel stable, 2.10.3, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 2.10.3 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7e9793dee1 (11 hours ago), 2022-03-02 11:23:12 -0600
    • Engine revision bd539267b4
    • Dart version 2.16.1
    • DevTools version 2.9.2

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

@darshankawar  is this because of the SHA-1?  @martcollins @lore-co @Tom3652 @Hhazeen
I just had release push notifications not working and debug working recently and resolved it by adding the SHA-1 (from jks via terminal or play store console)

Same as @martcollins in my case.
It's on iOS that it's never called but i have read this in the documentation :

On iOS, if the user swipes away the application from app Switcher, it must be manually reopened again for background messages to start working again.

So i don't really understand because the backgroundHandler should actually be used when app is terminated right ? It's at this specific moment that one would like to increase the app badge number for example when receiving a notification ?

Having the same issue, too.

Any solution for this?

same issue.

Please upvote this issue. Does anyone have any workaround for this till it gets fixed properly?

same issue

Facing the same issue.

Same issue for me.

Same issue for me, and its blocked publishing our app to public.

upgrade to flt2.10.3.Looks the same issue.
but shared_preferences  and  path_provider(path_provider_android) are used.
maybe shared_preferences and path_provider_android's version.
(https://github.com/flutter/flutter/issues/100844)

@russellwheatley  @Salakar Is there any update on this issue? Have you guys started looking into it already? It has been opened for quite some time now, and is a blocker for most of us.

the problem remains in iOS

I also have same problem, but as I tested, it stopped working when I added "--split-debug-info" in release mode.
When I just run "flutter run --release", it was working fine.

@darshankawar I faced the same issue, and it seems it happens only when --split-debug-info is enabled, when app starts Logcat shows the following error
E/flutter: [ERROR:flutter/shell/common/shell.cc(93)] Dart Unhandled Exception: NoSuchMethodError: No top-level getter '_firebaseMessagingCallbackDispatcher' declared.

it seems that exactly the same was happening here https://github.com/firebase/flutterfire/issues/8301

I am also having this problem.
I don't have --split-debug-info flag in my build.
Regular notifications work fine, but data messages don't.
The release apk seems to work fine on the Android emulator, but it doesn't work on a real device.

@russellwheatley I created a PR with a fix, is there any probability that this fix may be released any time soon?

Awesome, @TatsuUkraine! I will check this out and try and get a release out ASAP 👍


Data visualization

As it's mentionned in Orange's Web Browsing Guideline — entitled "Data display", Boosted should try to implement a data visualization component, using supporting color palette.

Have you ever thought about it yet? Would it be something from scratch or by using a third-party library as Chart.js or D3.js for example?

@julien-deramond No idea since we don't really have a target for now! The Global Design Language team wants to provide some guidelines for such things, but I don't know when to expect anything.
Moreover the Digital & Data UX team is also trying to provide some guidance for One-i (mostly for B2B design teams). @notabene is my only contact point on this topic at OFR.
Using a third-party library is obviously a way. Here's what I summed up regarding dataviz and accessibility (when interviewed by D&D).
Data visualization types
Some resources to know when and how to use each kind of data visualization:

DataViz Catalogue
DataViz project
Financial Times' Chart Doctor — Financial Times one, here's a PDF to catch
Serial mentor Dataviz

Third-party libraries
Selected because of their accessibility resources, docs and explanations:

Nivo (React + D3.js)
Apex charts
AmCharts
High Charts
chaarts, which is my very own POC in pure HTML & CSS (maybe not use this :p)

The main accessibility rule here is to ensure content is either accessible or rely on HTML to provide a fallback content (e.g. a standard HTML table).
Accessibility resources

WAI example regarding contrasts, in WCAG 2.1
Sarah Fossheim post about accessibility in dataviz design
Scott Vinkle wrote about accessibility and charts, too
Benjy Stanton provide a plan for accessible charts

Depending on whether the chart is dynamic or not, should provide some interactions or not, how many dimensions the datas represent… the tech choice might (should?) vary a bit.
Logging this for posterity :wave:

Another resource that could be useful apparently focused on a11y:

Visa Chart Components
Example: Visa Chart Components > Bar Chart
Visa Chart Components - GitHub

Potential useful article:  « Making data visualization more accessible for blind and low-vision individuals » : https://news.mit.edu/2022/data-visualization-accessible-blind-0602


Server-side sampling is broken with ASPNET Core SDK. 2.0+

ASP.NET Core SDK 2.0+ generates sequential operation IDs that result into non-uniform distribution when IDs are converted into server-side hash codes for sampling. Sampling algo that we are using requires that operation IDs are random, not just unique.

This has been resolved with the updated build of DiagnosticSource.
The Id's from the diagnostic source are still not random but they are sequential in the middle of the {x:8}-{x:16} string (e.g. 4c25b178-5a48cd6132f9d68a22bc -> 4c25b179-5a48cd6132f9d68a22bc) and this causes the server side sampling hashing to perform as expected.


fix: upgrader error msg to show current/max

Title

fix: upgrader error msg shows current/max
Description

Provides more information in the error message so users can better understand the error state.
Notes & open questions

CodeError: Too many outbound protocol streams for protocol "/ipfs/id/push/1.0.0" - limit 1

This error message is not super helpful for debugging. What's the overage amount?
Also, the check is checking >=, and if your limit is 1, that will prevent ANY outbound protocol streams. Is this intended? should we be comparing with only > ?
Change checklist

[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation if necessary (this includes comments as well)
[ ] I have added tests that prove my fix is effective or that my feature works

Also, the check is checking >=, and if your limit is 1, that will prevent ANY outbound protocol streams. Is this intended? should we be comparing with only > ?

No, because the stream has been opened already so at this point we are above the limit.
That is, when we carry out multistream select, and we support multiple stream protocols, we don't know ahead of time which one will be selected.  We have to let the stream open, negotiate a protocol, then carry out the check.  We could compare with === instead, but the >= is slightly safer.


Individual Major Donors Recipe

Create a recipe that sets up major donor records. For the purposes of this recipe, let's make major donors people who have given $10k+ at least once in the last few years.
Expected objects: Contacts with Household Accounts, Opportunities with Payments (optionally, add in a pledge record or two) spanning at least five years.

[ ] Create donor records
[ ] Create opportunity records
[ ] Create pledge records

Feeling Fancy? additional bells and whistles

[ ] Create engagement plan templates for major donors
[ ] Assign engagement plans to the donors

Thanks, y'all! This looks great!
I'm going to make a followup issue with enhancements.


SSO login not working

When trying to login using SSO I end in an infinite page reload.

Resolved by switching from Oracle's implementation to OpenJDK


[ttGlyphSet] Support VARC CFF2 fonts

@justvanrossum @anthrotype May I commit this?

It looks fine to me, but I didn't properly test it.


Subject Area OMAS breaks when a new enum is added.

Subject Area OMAS breaks when a new enum is added. The enums that the Subject Area is concerned with should only be limitted to only those that are relevant to it.

I think this is fixed when the generator moved to the FVT suite?

I agree


Xiaomi Vacuum 1S (not just 1, 1S) is not recognised

Hello,
It seems that the new Vacuum model 1S (an improvement from the 1st Gen) is not being recognised. I get the error
ERR getDocked | No vacuum cleaner is discovered yet
ERR getDevice | Is not a vacuum cleaner!
Adding manually the token to miio, the device shows this info:
miio inspect <IP_ADDRESS>
INFO  Attempting to inspect <IP_ADDRESS>
Device ID: 260239815
Model info: roborock.vacuum.m1s
Address: <IP_ADDRESS>
Token: 6d7a62614e6c5a6c4941366d4d47335a via stored token
Support: At least generic
Type info: miio
Capabilities:
Firmware version: 3.4.5_0848
Hardware version: Linux
It shows no capabilities which is not a good thing...
I guess that due to the newest model, it still has not been included in the miio database.

Hi @vmiraboronat,
i add the roborock.vacuum.m1s.
Unfortunately, I can not do more. Try it, maybe everything works. 🙏
npm uninstall -g homebridge-xiaomi-roborock-vacuum
npm install -g homebridge-xiaomi-roborock-vacuum@latest --unsafe-perm

Thanks for the update @nicoh88. It is working!!. It seems that the speed do not quite match, as it reports over 100%, but it does the job :-)
For a basic operation of the device, it is working perfectly for me.
Again, thanks!!!


Add git auto complete

I think this would be a great addition so it would auto complete branch names etc

Shouldn't it take this from the bash-completion package?

Doesn't seem to be working for me, but when I use standard iTerm it autocompletes

seems to work for me
do you have git-completion installed/available?
And is 'standard iTerm' the Terminal application (built-in) or iTerm2/3?

I do have git-completion installed and by standard iTerm I meant the iTerm application sorry 😄

@thomasbritton Seems to work for me too (v 0.0.3)

Ah!
It's not picking up my aliases in my .gitconfig
I'd normally use the following to switch branch: git co <branchname>
So I guess it would be nice for Black Screen to potentially reference any git aliases if possible but not essential.

I think it would be simpler to be able to create your own shortcut in a .blackscreen.config.js or something like and to link git co to git checkout?

@thomasbritton, that's a good idea, we'll definitely implement it.
@iDams aliases can't consist of two words.

@thomasbritton, thanks to @ekaragodin git aliases are now supported. Check it out!


Make DataCollection behave like a dict

DataCollection is an obvious dict wrapper. In my opinion, it should behave like one. This will make the code more intuitive.
See #11

I decided to keep the API as is to prevent user errors if they attempted to use DataCollection as a dict.  This collection will likely be deprecated in the future, since Python has advanced since this class was created.


Rate checker links have been removed

Links and content removed in a temporary fashion.
Also, this removes the debounce requirement because that change was sitting in my code. It should have been included with https://github.com/cfpb/owning-a-home/pull/265 but it wasn't... debounce isn't being used anywhere that I can see, but feel free to double-check before merging!

:+1:


Add support for alizer framework version detection

Which area this feature is related to?
/area alizer
Which functionality do you think we should add?
Right now alizer only detects a framework as a dependency of a component while not sharing more information about it. One important information we could return to every user could be also the version of each detected framework.
Why is this needed? Is your feature request related to a problem?
Adding the version value to the alizer response might help other developers to quickly check a piece of source code and what framework version is using. For example, if they have issues running the code, they can easily check if they should update/downgrade their language version.
Detailed description:
Upon component detection process alizer has access to this information. As a result it would be straightforward to catch the value and enrich the response.
Additional context
As the response format might change, a proposal should be made first from the assignee and the acceptance criteria should be defined then.

Removing the lifecycle/stale label as the issue is not rotten


BlobServiceClient find_blobs_by_tags should return a reduced / empty iterator when not matching.

bsc = BlobServiceClient.from_connection_string("Some_connection_string)
matches = bsc.find_blobs_by_tags("ID='1' \ ID='2')
matches.next()

Returns a StopIteration error today if no blob exists with the ID 1 or 2.
We have a usecase where the tag might not exist, thus causing the entire search to fail.
Idearly find_blobs_by_tags would only return an iterator for the matching cases.

Thanks for the feedback, we will investigate asap.

So I can solve my problem with the following code :
    match_cases = []
    not_match_cases = []
    for case in cases:
        try:
            blob_service_client.find_blobs_by_tags(f"ID='{case}'").next()
            match_cases.append(case)
        except Exception:
            not_match_cases.append(case)
            print(f"Could not find match for {case}")

yielding a two lists, one of the matches and one where there is no match.
Iterating over the matches now looks like.
for case in match_cases:
        match = blob_service_client.find_blobs_by_tags(self.case_list_to_string([case]))
        for blob in match:
            Do your thing with the blob here

Apparently  find_blobs_by_tags("ID='1' \ ID='2'") is valid syntax, however the iterator will only return the first match, that is ID=1 and then never return the ID=2 cases. This should not be allowed. (This is why I have the for case in match_cases for loop and not just one big query)
The better and more beautiful way of solving this is to have an OR statement, this have been suggested two years ago https://github.com/MicrosoftDocs/azure-docs/issues/55912 and as we can see it is still not implemented : https://docs.microsoft.com/en-us/rest/api/storageservices/find-blobs-by-tags#constructing-a-search-expression

Hi @petoor Peter, unfortunately the service still does not support a logical OR for this case. It seems there has not been enough demand for this feature to make it into a release.
That being said, I can offer a suggestion on a modification to your solution which may make it a little cleaner and avoid duplicate calls to the service for each ID. You could try using a dict to track your matches in the first request. Additionally, using the list constructor rather than .next() will avoid the StopIteration exception and just yield an empty list if there were no results. So something like this:
all_matches = {}
for case in cases:
    matches = list(service_client.find_blobs_by_tags(f"ID='{case}'"))
    if len(matches) > 0:    # If you care about non-matches, you can leave out this if
        all_matches[case] = matches

for case, matches in all_matches.items():
    # Do something with matches for each case

Hopefully that helps a bit. Please let me know if this doesn't meet your requirements.

I have made a formal, internal request to the service team to add logical OR in FindBlobsByTags as this is the second GitHub request for it. However, it is unlikely this will be prioritized anytime soon if I'm honest.
I think for now the best approach is to implement something like you had originally posted or my suggestion above.


Added rte configuration

Allows to change the rte config

Testet out this patch and it works really well!

Hi @AaronMorf
We don't really have a lead developer or an internal "owner" of this package, which is why this PR hasn't had any replies from us.
The changes work nicely, but I also notice that the PR fails to set a default value for the RTE configuration. Umbraco' RTE property editor, which the package is using, does have a fallback - but that fallback is different from the configuration this package have used so far.
This is therefore a breaking. Not a big one though. I and maybe so little that we don't really care about it in the end. But I need to have a chat with my colleagues on how best to proceed.
I'll hope to be back with more information soon 😉

Hi @AaronMorf
We had a chat about this PR, and decided to merge it 👍
It is a breaking change for the reasons that I mentioned in previous comment, but we're fine with having this part of a new v1.1.0 release 😉


Replace distutils usages

Replaces the usages of the deprecated distutils module. Closes #88.

Great work, merging.


Table of variants and their features

I checked the table against the previously stated features. I can't guarantee I haven't made any errors.

NOTE: the third commit incorporates #4.


[swift2objc] Fix bug with optional string params

The wrapper for
public func funcOptionalStrings(str: String?) -> String? { return str; }

was being generated as
@objc static public func funcOptionalStringsWrapper(str: String?) -> String? {
  return funcOptionalStrings(str: str?)
}

The str? is generated by maybeUnwrapValue, which was inserting ? because in most cases it's expecting to unwrap a wrapper type, which would add a .wrappedInstance to get str?.wrappedInstance. But strings don't need to be wrapped, because they bridge directly to NSString. So we end up with str?, with this unnecessary ? at the end, which causes compile errors.
The fix is just to drop the ? if the nested maybeUnwrapValue call didn't do anything.

coverage: 88.852% (+0.002%) from 88.85%
when pulling a4842e3f4e741f73dc44506562284569f0032cdf on optfix
into e69c74d1b15e53115f8bb7adc4d20a15034b604d on main.


[SPARK-33360] simplify DS v2 write resolution

What changes were proposed in this pull request?

Removing duplicated code in ResolveOutputRelation, by adding V2WriteCommand.withNewQuery
Why are the changes needed?

code cleanup
Does this PR introduce any user-facing change?

No
How was this patch tested?

existing tests

cc @rdblue @HeartSaVioR @dongjoon-hyun

Test build #130653 has started for PR 30264 at commit 005eff6.

Merged build finished. Test FAILed.

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

Test build #130653 has finished for PR 30264 at commit 005eff6.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Could you fix the compilation error?
[error] /home/jenkins/workspace/SparkPullRequestBuilder@2/sql/core/src/test/scala/org/apache/spark/sql/DataFrameWriterV2Suite.scala:103:14: class FakeV2WriteCommand needs to be abstract, since:
[error] it has 2 unimplemented members.
[error] /** As seen from class FakeV2WriteCommand, the missing signatures are as follows.
[error]  *  For convenience, these are usable as stub implementations.
[error]  */
[error]   def isByName: Boolean = ???
[error]   def withNewQuery(newQuery: org.apache.spark.sql.catalyst.plans.logical.LogicalPlan): org.apache.spark.sql.catalyst.plans.logical.V2WriteCommand = ???
[error]   case class FakeV2WriteCommand(table: NamedRelation, query: LogicalPlan) extends V2WriteCommand

Test build #130658 has started for PR 30264 at commit d6e854c.

Test build #130659 has started for PR 30264 at commit 8579675.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35270/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35269/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35269/

Build finished. Test FAILed.

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

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35270/

Merged build finished. Test FAILed.

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

Test build #130658 has finished for PR 30264 at commit d6e854c.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

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/130658/
Test PASSed.

Test build #130658 has finished for PR 30264 at commit d6e854c.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Is it false-alarm or can happen? I would expect the tests are even not running once it fails to merge. Anyway, retest would make it clear.

retest this, please

Test build #130669 has started for PR 30264 at commit 8579675.

Test build #130659 has finished for PR 30264 at commit 8579675.

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/130659/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35280/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35280/

Merged build finished. Test FAILed.

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

Test build #130669 has finished for PR 30264 at commit 8579675.

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/130669/
Test PASSed.

+1
Thanks, @cloud-fan, this looks good.


Complete implementation in Swift and add some unit tests

I've updated to Swift 3 syntax. It still compiles under Swift 2.
Most of the calls to respondsToSelector were replaced by optional chaining. No need to check if it responds to selector.

I made some more additions.

Documentation for the protocols
Completed the missing parts in DZNEmptyDataSet.swift
Implemented Swizzling for UITableView.endUpdates and UICollectionView.performBatchUpdates in addition to reloadData
Created a project to build a framework
Added some unit tests

hey, So what's happened ? :)

Hi, as a newbie to iOS dev, this is one of those, that is a must-have for my current app and probably for future apps.
Apologies, that I'm not yet a contributor but only a passive user. But, will you be able to let me know about the developments? Is it ready for swift 3?
Many thanks for your efforts and time. :)

@dzenbot Are there any news on this? I would love to see this soon. It's been almost half a year...


docs: Custom Document Loaders

Add information that shows how to create custom document loaders

cc @ccurme thanks for the review


no matches for kind "AdmissionConfiguration" in version "apiserver.config.k8s.io/v1"

Trying to enforce Pod Security Standards by Configuring the Built-in Admission Controller on AKS which has kubernetes version 1.23 by following this setups which is explained here: https://kubernetes.io/docs/tasks/configure-pod-container/enforce-standards-admission-controller/
However when I apply the yaml file, I get this error:
$ k create -f podsecurity.yaml error: unable to recognize "podsecurity.yaml": no matches for kind "AdmissionConfiguration" in version "apiserver.config.k8s.io/v1"
I am able to activate podsecurity on namespace level by adding a label under every namespace. However I can not activate it on cluster level using admissionconfiguration.
Is this something that AKS doesn't support? If so, when they have plan to support it?

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

ID: a7dc4598-18d3-bdcc-e21a-f838fb752268
Version Independent ID: edf2d399-9bbb-1c1e-e4cc-d69bf2ce0f05
Content: Use pod security policies in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/use-pod-security-policies.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@Mina69
Thanks for your Question! We are currently investigating and will get back on this.

@Mina69
Currently this is not supported at the Cluster level. The Feedback has been shared to the document author to update the document to make this clear.
You can achieve this using Azure Policy refer this document once.
BTW, AdmissionConfiguration cannot not be applied via kubectl, they are used with the api-server parameter --admission-control-config-file.
Alternative solution would be to install the admission webhook for Pod Security Admission.
Once this is deployed you can configure with a ConfigMap which you will find in the namespace. Please note this is not supported by Microsoft and could potentially cause issues if misconfigured.

Hope the provided information is helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.


met_ann = None, but used in infflux  and efflux (vignette)

Hello,
First thanks for this nice tool!
In the vignettes, both efflux and infflux use in the met_ann which is none in the whole script. How can i access this ?
efflux_mat = pd.merge(efflux_mat, met_ann[['Secondary_HMDB_ID', 'metabolite']]

Hi this should be fixed in the version 1.0.4 at https://github.com/kaifuchenlab/MEBOCOSTPlease try it and let me know if you still have question. Thanks!Best Regards!Rongbin ZhengOn Jun 18, 2024, at 7:53 AM, NeuralBind @.***> wrote:
Hello,
First thanks for this nice tool!
In the vignettes, both efflux and infflux use in the met_ann which is none in the whole script. How can i access this ?
efflux_mat = pd.merge(efflux_mat, met_ann[['Secondary_HMDB_ID', 'metabolite']]
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

oh, just saw there was another repository. Thanks! I will try it out.


Minor fixes to dataprotection extension

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

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

To be reviewed internally by @Miraj50 first.

Reviewed. Thank you for making the fix.

The PR validation seems to be failing due to something unrelated.


Expand and collapse list items by range

In 2.0.0, we can expand/collapse individual list items or we can expand/collapse the entire list. We should add the ability to expand/collapse a group a list items by providing a range of indices from the list of parents.

Resolved in 2.1.0.


Chart missing when no events

I think it is still good to show the chart with no events than blank space

https://beta.kodadot.xyz/bsx/collection/1865909717/activity

can you please lower the opacity for it, just to indicate that there is normally a chart there.

I will add some designs in the future - empty state - something like faded chart + some copy

solved


DOC-5379 add dbconsole metrics known issue

Addresses: DOC-5379

Added brief known limitation to v22.1.4 and v22.1.5 release notes advising of DB Console metrics page load failure / slowness.
Added same mention to v22.1 standard known-limitations page.

NOTE: Indicating that v22.1.6 contains the fix. Confirming this is the case?
v22.1.md | known-limitations.md

This change is

Confirming that the fixes will be in 22.1.6


(backlog)KAFKA configuration and integrate with Anomaly detection

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
To integrate the KAFKA output with Anomaly detection, define and update the code to write metrics data to KAFKA in the format expected by Anomaly detection module
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Hotpot(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

#777 addresses this.


Use the python module to change an ACL or the sql of a dataset

Dremio client version: 0.10.1
Dremio version: 4.1.8
Python version: 3.8.2
Operating System: docker/python:3
Description
I'm trying to write to the dremio catalog with the python module (not the utility).
For instance changing an ACL or a sql definition.
What I Did
from dremio_client import init
client = init()
catalog = client.data

Then I tried to change the attribute and then commit...
a = catalog.BDF.example_bug_round.get()
b = a.meta
b.sql = "SELECT * FROM bug_round_test limit 3000"
setattr(a,"meta",b)
a.commit()

But commit seems deactivated (_dirty=False?)
So I don't even know if it's possible right now.
Can you please advise ?
Thank you.

Hey @insatomcat the _dirty flag isn't set automatically yet (on my todo list). You can set it by hand. From your example above a._dirty = True

Thanks


Warning: Could not find any test files matching pattern:

Why the plugin doesn't see files when files 100% exist in my test folder?
I want to run test for certain files only.
How do I do it with mocha?
My set up:
// test folder. Files are the same. Changed name for the sake of showing you an error
/test
    nock.js
    nock_test.js

// package.json
"scripts": { "test": "mocha" }

None of these work. All throw the same error:
$ npm test nock
$ npm test nock.js
$ npm test nock_test
$ npm test nock_test.js

Error:

Warning: Could not find any test files matching pattern: nock
Warning: Could not find any test files matching pattern: nock.js
Warning: Could not find any test files matching pattern: nock_test
Warning: Could not find any test files matching pattern: nock_test.js
No test files found
npm ERR! Test failed.  See above for more details.

How it can be? No test files matching pattern? It is not even a pattern! It is exactly a file name.
How to run it?

You should be writing test/nock.js/test/test_nock.js instead of just nock.js/test_nock.js. Please let us know if that resolves your issue!
(Mocha supports putting your test files in other folders than test; for example, some projects put test files in the same folders as corresponding source files and with the same name except using .test.js or .spec.js instead of .js at the end of the test file's name. It's a tradeoff between cleanliness of source directories vs ease of association of test and source, but the important thing is Mocha supports both and therefore won't prevent the one by turning lib/someModule.spec.js into test/lib/someModule.spec.js.)

In my project:

Tree:
project
------build
------node_modules
------src
-----------components
------------------A.js
------------------A.spec.js
------test
-----------setup.js
------package.json
Test script:
"test": "mocha --compilers js:babel-core/register -r ./test/setup.js './src/**/*.spec.js*'"
Dependencies:
"devDependencies": {
"babel-core": "^6.26.0",
"babel-loader": "^7.1.2",
"babel-preset-es2015": "^6.24.1",
"babel-preset-react": "^6.24.1",
"babel-preset-stage-1": "^6.24.1",
"babel-preset-stage-2": "^6.24.1",
"chai": "^4.1.2",
"enzyme": "^2.9.1",
"html-webpack-plugin": "^2.30.1",
"jsdom": "^11.2.0",
"mocha": "^3.5.3",
"react-addons-test-utils": "^15.6.0",
"webpack": "^3.5.6",
"webpack-dev-server": "^2.8.1"
},
"dependencies": {
"react": "^15.6.1",
"react-dom": "^15.6.1"
}

When i run npm test:

Warning: Could not find any test files matching pattern: './src/**/.spec.js'

        Please, help me!

It looks like mocha is including the single quotes in the pattern itself. I was able to get around it by using escaped double quotes:
"test": "mocha --compilers js:babel-core/register -r ./test/setup.js \"./src/**/*.spec.js*\""

Hi ! I have same issue, but here with Circle CI 2.0 (Ubuntu 14.04)
Works fine on MacOSX and Ubuntu 16.04, how could i solve this error with Circle CI environment ? Seems to be a Mocha trick... Thanks a lot !
In my term :
$ eslint .
$ mocha "./src/migrations/index.test.js" --require babel-core/register
Warning: Could not find any test files matching pattern: ./src/migrations/index.test.js
No test files found
error Command failed with exit code 1.

My package.json :
...
"test-migrations": "mocha \"./src/migrations/index.test.js\" --require babel-core/register",
"test": "yarn run lint && yarn run test-migrations && mocha \"./src/index.test.js\" --require babel-core/register",
...

@xurei's is the only thing I've seen here that could be an actual Mocha bug.  I'll try to reproduce this.

@xurei What shell are you using?
If you're in PowerShell, glob (which interprets your glob-containing path, because it's in double-quotes) expects your paths to look like your second example; the first example is not a valid path, AFAICT.
If you're in bash on Windows, then either should work, at least in my limited testing.

@boneskull I'm using Git BASH

My package.json has this:
"test": "mocha server/spec/server-spec.js; RES=$?; kill %1; exit $RES"
And my file structure is:
server
    spec
        server-spec.js

And, of course,  I'm currently in the rrot directory where the server directory is located, but when I run npm test I get that error:
Warning: Could not find any test files matching pattern: server/spec/server-spec.js;
I'm using a Windows OS. I've tried cmd.exe & Git Bash, but I get the same result... Any idea?

@MuhammadJamaluddin, you should be able to just have:
"scripts": {
  "test": "mocha server/spec/server-spec.js"
}

Depending on what version of mocha you're using, you may see something helpful in the debug output by using cross-env and launching it like this:
$ npm install --save-dev cross-env

"scripts": {
  "test": "cross-env DEBUG=* mocha server/spec/server-spec.js"
}

Or use a glob and just see what mocha finds... JIC you misspelled something...
"scripts": {
  "test": "cross-env DEBUG=* mocha 'server/**/*.js'"
}


css output is being truncated

hello, thanks for your code, and its not strictly an issue for your code, but i am getting desperate.
the css minifier had been working perfectly, then, out of the blue, it has started to truncate the output to around 3.85kb (regardless of input file size or content)
i was wondering if you had any inkling on what may be causing this.
i do regular yum updates of the server which is the only thing that has changed. i have tested and it has nothing to do with any characters in the input which may have broken the code.
have searched extensively for a solution for a number of hours and tried a number of things for myself and came up with a blank.
EDIT!! after trying for a few more hours, it seems that once the input file moves over 30.8kb it truncates the output. always to around 3.85kb. will keep trying.
cheers - rs

Since this is now hosted on Toptal I believe this is no longer an issue, I'll close this for now, please re-open if you still have any problems with it.


[WIP] default ssh user

In order to run commands on cluster nodes that do not have root access over SSH enabled by default a cluster advertises the default SSH user that can be used instead.

Really lovely work Tim! Just the minor comments to go.


Browser support docs - add flexbox section

The browser support section should list supported browsers for the flexbox mode, linking to any necessary polyfills for IE 10/9/8.

There are no polyfills for Flexbox that I know of. Flexie is broken and the rework of it is a dead project.

Bummer, that was my impression as well.
I think we're on the same page about the core point: browser compatibility section should have a clear explanation:
calc mode: works in Chrome X+, IE X+ with polyfill Y, ..
flexbox mode: <similar>

Fixed https://github.com/corysimmons/lost/commit/b6f5e619098f3340e093649baccd645d7d71fbb7


Datepicker to allow 2 date format

Is it possible to allow two date format specifically just the zeros for month and day?
E.g.:
01/01/2015
1/01/2015
01/1/2015
1/1/2015

Please do not use the issues forum for support related requests.  Rather, please follow the instructions here.

See this SO article for your answer.

I'm reopening this as it needs further investigation.  <input type="date"/> is not supported in all browsers so we support type="text" to mitigate.
What would help is if you could create a bare bones plunker using the latest code to demonstrate this issue.  That should help get us started.  Thanks.

@icfantv here you go: http://plnkr.co/edit/NPqifjimoAnuJgvFPyDm?p=preview
I put both MM/dd/yyyy and M/d/yyyy text boxes.

Linking in the SO article here:  http://stackoverflow.com/questions/32832161/angular-bootstrap-how-to-allow-2-different-date-format

Quick question, where would be the appropriate place to add a clarification/feature request that's related to this issue?

@icfantv not sure what you have in mind for a fix. One solution came to mind is to enforce formatting on blur. Not sure if that is acceptable solution/method.

I need to talk to the other devs about the right fix here assuming that it is a bug (I freely admit I have not yet investigated it).  Currently we're focused on getting 0.14.0 out the door and getting ng-bootstrap (the ng2/BS4 port) ready for Angular Connect, London in a few weeks.
We have weekly meetings on Tuesdays and I will bring it up then.  Thanks.

To implement this, this would involve modifying the uibDateParser service - we may be able to support this, but this is work that would be scheduled for backlog, and likely only implemented if someone submitted a high quality PR.
One needs to be careful about the letters chosen to support double date formats. We follow the native dateFilter in Angular, so any choice cannot conflict with this.

@wesleycho So one thing that is desperately needed is the ability to databind to a date format that is different than what is displayed.  For example, binding to a datetime in ISO, then displaying simple mm/dd/yyyy.

That is separate from this issue and should be in a separate issue if that is requested - we removed string support though due to cross-browser issues, so that particular proposal is a no-go.

In 0.13.1 (and earlier, probably), the text box accepted many date formats. Starting in 0.13.2, it accepts only the date format specified in datepicker-popup. You can reproduce this in the docs - scroll down to the 0.13.1 datepicker demo here and enter 1/1/17 or 2017-01-01 or jan 1 17 and it works. Try that in the 0.13.2 or later datepicker demo, and it doesn't work, unless you use the format specified in datepicker-popup. Was it intentional to remove this functionality?

This was intentional - this was due to unexpected cross-browser issues that were impossible to fix.

This feature is now supported in master via b1cfc57

Many thanks for the fix, we struggled with the same issue. Is there an approximate date we can expect this fix in a (npm) release?

@brunnurs, the 1.x release will be soon.  In the interim, you can pull master and do a SNAPSHOT build.

@icfantv Thanks for the V1.0.3 release, which includes the new feature. Unfortunately, it doesn't seem to work with the uib-datepicker-popup.
I extended your plunkr with the format d!.M!.yyyy. I expected to be able to enter a date in format 13.01.2016 OR 13.1.2016. But it doesn't seem to work. Is it a bug or my rookie-mistake?

@brunnurs, if you think you've found a bug, please follow these instructions.
In practice, it's never a good idea to ask for help on a closed thread.  Doing so is a good way for it to get missed or ignored.