Matching documents in array

There is some operator that iterates over an array.
https://github.com/TotalTechGeek/json-logic-engine/blob/5f1d2b5b039e9add4a505f8a23713ebd0bb6d9c4/test.js#L466
Empty var: '' is confusing, a special character like $this could make it more explicit.
test('some true', () => {
      const answer = logic.run({
        some: [
          [1, 2, 3],
          {
            '>': [
              {
                var: '$this'
              },
              2
            ]
          }
        ]
      })

      expect(answer).toBe(true)
    })

Regarding the nested object, I'd expect something like this:
test('some true', () => {
      const answer = logic.run({
        some: [
          [{ a: 5 }, { a: 1 }],
          {
            '>': [
              {
                var: '$this.a'
              },
              2
            ]
          }
        ]
      })

      expect(answer).toBe(true)
    })

What do you think?

Hi @Mihailoff! I appreciate your contributions to the repo!
I actually do agree that being more explicit improves readability in this case, but I'd like to remain as spec-compliant as possible with JSON-Logic.
Thinking through options:

One approach could be to erase "$this" as if it weren't there if it's at the beginning, allowing for both the explicit and implicit syntax. However, this would cause a divergence from the spec without extending behavior

Another approach is to override the var method with a different implementation, to customize it for the use case. However, there are some optimizations baked into var though that make me feel uncomfortable recommending this to a general user of the engine. Perhaps I could improve this somewhat.

If "$this" was added, would the traversal syntax remain the same?
For example,
If you wanted to access data from an above section,
../../a inside of the some block would let you access the data from   what was passed into the function.

Where is the spec? :) https://jsonlogic.com doesn't mention empty var...

../../a

Following the "path" style, should it be then a dot .?

This is my use case, a document with subdocuments. Will this work?
// doc = { items: [ { a: 1 }, { a: 2 } ] }
{ 'some': [
   { 'var': 'items' },
   { '<': [
     { 'var': 'a' }
     10
   ] }
] }

Hm, the website fails to mention it there:
But it is implemented in the mainline repo here: https://github.com/jwadhams/json-logic-js/blob/9c805e9ac6a3787e8508e982a079888d3cc295b5/logic.js#L126
And shows up on the website under this section: https://jsonlogic.com/operations.html#all-none-and-some
And is part of the test suite: https://jsonlogic.com/tests.json
[ {"var":""}, 1, 1 ],
[ {"var":null}, 1, 1 ],
[ {"var":[]}, 1, 1 ],

Also yes, your rule there will work perfectly!
import LogicEngine from './logic.js'

const engine = new LogicEngine()

const validate = engine.build({
  some: [
    {
      var: 'items'
    },
    {
      '<': [
        {
          var: 'a'
        },
        10
      ]
    }
  ]
})

console.log(validate({
  items: [
    {
      a: 1
    },
    {
      a: 2
    }
  ]
})) // true

console.log(validate({
  items: [
    {
      a: 11
    },
    {
      a: 12
    }
  ]
})) // false


Fix a watcher task name

Change a watcher task name from "Watch new files" to "WatchMyFolder" to be in sync with images.

@alexandair : Thanks for your contribution to the Azure documentation! The author, @eamonoreilly, has been notified to review your proposed change.

#sign-off


Update config for coroutines on ARM

@eugeneswalker would you be able to try #38812? This is a missing conflict in the package. @hkaiser I think you can also update the ifdefs in HPX to fall back to the posix implementation as an alternative to Boost.Context. If and when you update those in HPX we can add an upper bound for the version in the conflict.
Originally posted by @msimberg in https://github.com/spack/spack/issues/38796#issuecomment-1628469565

This has been fixed.

Are there plans to officially support ARM officially as a platform? As ARM became more and more relevant in all areas, including servers/cloud, this would make hpx more interesting.
The documentation does not list ARM as supported:
https://github.com/STEllAR-GROUP/hpx/blob/master/docs/sphinx/manual/prerequisites.rst?plain=1#L20-L29


Fix for Bounding Box definitions with GS 2.12

What does this PR do?
GeoServer changed how the extent was serialized in 2.12 which
causes the extent and CRS to be stored differently in the
layer object's metadata.
2.11 style is metadata.bbox.extent.crs
2.12 style is metadata.bbox.extent.extent.crs
2.12 will also return EPSG:4326 as CRS:84.

New alias definition has been added for CRS:84
MapService has been updated to recognize both extent structures.
Tests add to prove it works for both 2.11 and 2.12 style structures.

Screenshot
Related Issue
BEX-418

Hold off on merging this. It looks like the real issue is GetCapabilities with Version 1.1.1 vs 1.3.0.

Closing in favor of PR https://github.com/boundlessgeo/MapLoom/pull/114


Cannot horizontally centre a custom content dialog defined with ContentDialogPlacement.InPlace in its owning panel.

Describe the bug
The discussion was started in issue #3751 and has been separated out.
A custom content dialog defined with ContentDialogPlacement.InPlace and HorizontalAlignment="Center" is displayed with the top left corner of the content dialog positioned at the horizontal centre of its parent panel. Where it was have expected that the dialog would be horizontally centred in the parent panel.
Steps to reproduce the bug
Can be reproduced by running the sample located here:
https://github.com/BrianDT/UWPTemplatedContentDialogIssue.git
Ensure that the PureUWPApp project is selected.
Expected behavior
Expected that the dialog would be horizontally centred in the parent panel.
Screenshots

Version Info

NuGet package version:
Microsoft.NETCore.UniversalWindowsPlatform 6.2.12
Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

@BrianDT this is very familiar, but I think the linked issue is incorrect. Can you double check it?

Linked issue number corrected

A status update would be appreciated, just scheduled, backlog or discarded would be enough.


[Enhancement]: Allow customization of the database container by supplying a customization function

Module
Core
Proposal
We can customize the DB created by the Testcontainer's JDBC integration using a function passed on the database connection URL.
What if we could customize the container using a similar scheme?
I propose we introduce a URL parameter named TC_CONTAINERCUSTOMIZER (maybe we can come up with a smaller name). It takes the fully qualified name of the function we want to call to customize the newly created container. For instance, using the URL below would call the sampleCustomizer method of the on org.testcontainers.jdbc.JDBCDriverTest before starting the database container.
jdbc:tc:mysql:5.7.34:///databasename?TC_CONTAINERCUSTOMIZER =org.testcontainers.jdbc.JDBCDriverTest::sampleCustomizer
The signature of the sampleCustomizer should be something like the snippet below.
public class JDBCDriverTest {
    public <S extends JdbcDatabaseContainer<S>> static S sampleCustomizer (S container) throws Exception {
        // e.g. change parameters, change entry point and etc. here...
        return container;
    }
}

What do you guys think about it? If you guys think it would be a nice add-on I'll submit a PR for it.

Hi @bsofiato, thanks for raising this issue. We would like to understand the use cases for this first. Then we can discuss if we should proceed with a PR or not.

As a general note, I feel advanced use cases that require detailed configuration of the container are much better suited to using the existing OOP Testcontainers API, rather than improving the complexity of the JDBC integration (which is already a more specific use case).

Sure, @eddumelendez. In one project, we used the WNameless Oracle image with OracleAQ.  To make it run correctly, we had to disable Oracle's "asynch.io" feature, which is done by setting an environment variable of the docker image.
@kiview, I feel bootstrapping database containers thru JDBC url is way simpler than providing a custom database. Especially when using SpringBoot as all the container's lifecycle is (indirectly) handled by the spring test framework itself (which is complex since spring might cache test contexts for latter use).
I might be wrong, but it is up to the developer to manually bootstrap the datasource when using the OOP container approach (which might not be the approach used in production).

@bsofiato Are you aware of the DynamicPropertySource configuration approach in Spring-Boot for setting the respective properties using the container object? It is the recommended way by Spring-Boot and the mechanism was specifically introduced to allow for an easier integration with Testcontainers. It works specifically well with Spring-Context caching and gives you rich controls of instrumenting and bootstrapping the container to your liking.

I totally agree with @kiview here. Testcontainers JDBC integration is a convenient way to use however in case there are most complex cases the recommended way is to use the container class for customization.


[10.3] Morph one of many query error

Laravel Version: 10.3.1
PHP Version: 8.2.3
Database Driver & Version: Postgres 14.7

Description:
My test suite blew up in the upgrade from 10.2.0 to 10.3.0/10.3.1.
I have Property which has many Image with an order. I use morphOne()->ofMany() to fetch properties with their primary image (i.e. with the minium order).
This worked fine on 10.2.0 but on 10.3.0 I get a query error:
SQLSTATE[42803]: Grouping error: 7 ERROR: column "images.order" must appear in the GROUP BY clause or be used in an aggregate function LINE 1: ...oin (select min("images"."id") as "id_aggregate", "images"."... ^ (Connection: pgsql, SQL: select "images".* from "images" inner join (select min("images"."id") as "id_aggregate", "images"."order" as "order_aggregate", "images"."imageable_id", "images"."imageable_type" from "images" inner join (select min("images"."order") as "order_aggregate", "images"."imageable_id", "images"."imageable_type" from "images" where "images"."imageable_id" in (...) and "images"."imageable_type" = App\Models\Property group by "images"."imageable_id", "images"."imageable_type") as "image" on "image"."order_aggregate" = "images"."order" and "image"."imageable_type" = "images"."imageable_type" and "image"."imageable_id" = "images"."imageable_id" group by "images"."imageable_id", "images"."imageable_type") as "image" on "image"."id_aggregate" = "images"."id" and "image"."order_aggregate" = "images"."order" and "image"."imageable_type" = "images"."imageable_type" and "image"."imageable_id" = "images"."imageable_id")

Here's the basic model setup;
class Property extends Model
{
    public function image()
    {
        return $this->morphOne(Image::class, 'imageable')
            ->ofMany('order', 'min');
    }

    public function images()
    {
        return $this->morphMany(Image::class, 'imageable');
    }
}

class Image extends Model
{
    public function imageable()
    {
        return $this->morphTo();
    }
}

And the query that blows up;
Property::with('image')->simplePaginate();

As a sanity check I tested this against SQLite and it's a non issue. Didn't test against MySQL but I presume it may be Postgres specific.
Steps To Reproduce:
I've replicated this issue in a new Laravel app: https://github.com/dwightwatson/bug-report

Looking through the changes between the two tagged versions it looks like #46309 could be the cause.

Looking through the changes between the two tagged versions it looks like #46309 could be the cause.

Totally is, I added a comment in it, asking a temporary rollback because I can't fix it right now.


Support other mathematical fonts

Support other mathematical fonts. There are a couple of fonts with a MATH table:

Asana Math
Cambria Math
DejaVu Math TeX Gyre
Latin Modern Math
Libertinus Math
Lucida Bright Math
Minion Math
STIX Math
TeX Gyre Bonum Math
TeX Gyre Pagella Math
TeX Gyre Schola Math
TeX Gyre Termes Math
XITS Math

One thing I like about Latin Modern Roman is that the font-weight is a lot finer. Which makes it look more elegant. Alternatively, it would be helpful if you could set the font-weight of the default KaTeX font.

For a visual comparison:
KaTeX Font:

Latin Modern Roman font:

Duplicate of https://github.com/Khan/KaTeX/issues/123.


Refactoring with flutter standards for UX/UI

smoothie is currently a bit messy, regarding UX/UI. For historical reasons.
I can see that standard flutter widgets have been emulated sometimes in smoothie, like the BottomNavigationBar, the FloatingActionButton or the AppBar. But the standard versions work very well, thank you.
And if we don't use the standards, we keep struggling emulating them, like "it would be a great idea to have a back button on the top of the screen", though we wouldn't even have to think about it if we used the standard widgets in the first place (cf. #125).
The goal of this refactoring issue is to use systematically standard and bullet proof widgets like BottomNavigationBar, FloatingActionButton, AppBar, ListTile, Card, ...
Maybe there will be a time when we can make our widgets more user-friendly, more beautiful and more robust than the standard versions, and that it will be a priority. I don't think we reached that level for the moment.

Yes, I think that's an important thing. I am also of the opinion that we should use the standard widgets.
Especially the navigation bar is very confusing...

Yes, I think that's an important thing. I am also of the opinion that we should use the standard widgets.
Especially the navigation bar is very confusing...

That would be really helpful indeed. I'm still very much struggling when I navigate the app code, so the less code, the better. :)
On a related note, more comments about what the different classes and functions are supposed to do would be helpful as well.

That would be really helpful indeed. I'm still very much struggling when I navigate the app code, so the less code, the better. :)
On a related note, more comments about what the different classes and functions are supposed to do would be helpful as well.

There seems to be a consensus then.
My suggestions, for a first step:

use BottomNavigationBar, FloatingActionButton and AppBar instead of whatever is currently used
use named routes

There seems to be a consensus then.
My suggestions, for a first step:

use BottomNavigationBar, FloatingActionButton and AppBar instead of whatever is currently used
use named routes

I could take over the BootomNavigationBar

I could take over the BootomNavigationBar

@M123-dev The first obvious thing to fix is main.dart, which displays an ersatz of BottomNavigationBar with 4 items and a FloatingActionButton.
If I had to do it, this is what I'd do:

make ChoosePage the explicit home page of the app, with a BottomNavigationBar and a FloatingActionButton instead of the current code
when we click on the BottomNavigationBarItems, we explicitly call Navigator.push in order to open a new page (that won't use the same BottomNavigationBar by default, but we don't need it)

@M123-dev The first obvious thing to fix is main.dart, which displays an ersatz of BottomNavigationBar with 4 items and a FloatingActionButton.
If I had to do it, this is what I'd do:

make ChoosePage the explicit home page of the app, with a BottomNavigationBar and a FloatingActionButton instead of the current code
when we click on the BottomNavigationBarItems, we explicitly call Navigator.push in order to open a new page (that won't use the same BottomNavigationBar by default, but we don't need it)

@monsieurtanuki, is still something missing here or can we close this issue?

@M123-dev I wouldn't say it's over but there's no strong reason to keep it open.


Regression of indentation of single-expression control flow in match arms

As of PR #1877, I expect this to remain unchanged:
fn main() {
    match 1 {
        a => {
            match a {
                1 => 1,
                2 => 2,
                x => x,
            }
        },
    }
}

I recall this working for a while. However, now the match is moved up a line:
fn main() {
    match 1 {
        a => match a {
            1 => 1,
            2 => 2,
            x => x,
        },
    }
}

I see this behavior with:

0.3.8-nightly (346238f 2018-02-04)
rustfmt 0.4.2-nightly (1415a4dc 2018-04-14)

Thank you.
As you might imagine, I strongly disagree with this particular style aspect. It appears that force_multiline_blocks = true uses the style that I'd prefer; do you happen to know if that will have unexpected effects beyond this case?


Change type of RocSenderConfig.packetInterleaving

packetInterleaving should be boolean, not integer.
We need to update RocSenderConfig, RocSenderConfig.Builder, and their methods, as well as the JNI side.

Closing because this option is going to be removed in toolkit 0.5


Add rules_apple_linker

can you start CI on this one again?

I think that you can only verify targets in CI that build with non-dev drops only - the tests are run from an anonymous main module and are intended to test targets relevant for downstream consumers.

hrm, so in this case all test dependencies are dev dependencies, it seems weird to have to make those public dependencies just for the bcr, wdyt?

@keith Yes, that's why it's recommended to have a separate test module. It has to be part of the source archives, but its dependencies don't pollute the main module's deps. See tests/bcr in rules_go for an example (and the presubmit.yml).

hrm yea that makes sense but I think that degrades my local devx on that rule set because from the root I could no longer bazel test ...

@alexeagle as rules_python seems to have a solution for that

seems like the value of dev_dependency is lowered a lot if this is the recommendation as well. I was thinking maybe we could build with dev dependencies disabled but test with them enabled but it doesn't look like there's a flag to do that when you're not the root module

Dev dependencies still cover things like stardoc or rules_pkg and your full test suite run in your ruleset's CI.
The BCR presubmit is, at least according to the initial design, rather meant to be a smoke test for your Bzlmod API. For that, not bringing in more dependencies than your downstream consumers will see is probably a feature rather than a limitation.
I will defer to @meteorcloudy and @Wyverald though for authoritative answers. I do agree that more work will have to go into making the testing strategy for BCR modules more obvious.

Hmm... IMO it does sound a bit bad that the test targets can't be built because we're setting the module under test as a dependency, instead of just using it as the root module. @meteorcloudy I believe you set it up this way because we'd need to implement logic to interpret source.json and fetch it in the BCR presubmit pipeline, instead of just letting Bazel handle it. The downside is indeed that no dev dependencies of the module under test can be used. Do you think this warrants reworking the presubmit pipeline?

I believe you set it up this way because otherwise we'd need to implement logic to interpret source.json and fetch it in the BCR presubmit pipeline,

No, that's not the reason. In fact, we already have the logic to interpret source.json and fetch it in the BCR presubmit pipeline for the test module. We were discussing the possibility to always let Bazel download it because the patch tool behaves differently from native implementation in Bazel.
You can check the documentation of anonymous module test and testing module to understand their purposes. Basically, the first one ensures the basic targets want to expose build correctly, the second one gives you a chance to actually test your APIs in some example use cases.
If you want to just run bazel test //test/..., I think you can consider just setting module_path="" under bcr_test_module section, then you should be able to use your original repo as the test module.

I was thinking maybe we could build with dev dependencies disabled but test with them enabled but it doesn't look like there's a flag to do that when you're not the root module

You can build with dev dependencies disabled if you are the root module with flag --ignore_dev_dependency. Maybe we can add a flag --fetch_all_dev_dependency? But I doubt it's necessary since we probably don't want to run tests of a non-root module because that's not how you run those tests usually anyway.
That said, I'm also happy to hear any suggestion on how to improve the BCR presubmit set up ;)

pushed an attempt at the bcr test module being the root


Updated put.py

Added in line of code to assign "serviceInstanceProfile" to be an empty dict as the method was erroring without this.

Code already implemented in main.


kubectx: build fails on aarch64-darwin

Steps To Reproduce
Steps to reproduce the behavior:

nix build /nix/store/1ikzh2ax90ji2156hh921gp4iambgwsm-kubectx-0.9.4.drv

Build log
# golang.org/x/sys/unix
vendor/golang.org/x/sys/unix/syscall_darwin.1_13.go:29:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.1_13.go:27:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.1_13.go:40:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:28:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:43:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:59:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:75:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:90:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:105:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:121:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:121:3: too many errors

Additional context
Add any other context about the problem here.
Notify maintainers
@superherointj
@teto
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.5.0, macOS 12.4`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.4`
 - channels(root): `"nixpkgs-22.05pre334669.f366af7a1b3"`
 - channels(davidsmith): `"home-manager, nixpkgs-21.05.4726.530a53dcbc9, unstable-22.05pre372961.e10da1c7f54"`
 - nixpkgs: `/Users/davidsmith/.nix-defexpr/channels/nixpkgs`

sry I dont use darwin, my reflex would be to mark darwin as not supported except if someone can step up

it looks like this may be solved by upgrading x/sys but does anyone here know how to do that in nixpkgs? I have no idea about the go ecosystem here.

@shmish111 Please test kubectx from master.

I was able to get this to build with the following:

rev: master
sha256: 1cd5bs7gd75sy38y83dcajr36j0cmj56fi3dv5yi41cr39h2d16b
vendorSha256: sha256-LYGv0hFZy4dV9qRXdxNur8CN3IS4bWp03+BCwO+YrYc=

The approach to pin go 1.17 here is wrong. The package just requires a bump of golang.org/x/sys.


velocityHelpers can't be used in a server-side render environment.

The original velocity-animate package expects to be client-side, so requiring it, in order to enable the velocityHelpers, isn't possible when you are rendering on the server.

Hrm. Good point. Let me look into this.

Does #54 help you with this?
You'll still want to wrap your primary require calls in:
if (typeof window !== 'undefined') {
  …
}

and the velocity-react components will use their shim.

I'm still having the issue with<EMAIL_ADDRESS>I've wrapped the require for velocity-animate/velocity.ui in a check to determine if the code is being run in the browser environment, but I receive the error:
throw "Velocity.RegisterEffect not found. You need to require('velocity-animate/velocity.ui') at a top level for UI Pack.";
Seem's like it's not no-op'ing on the server.

Lemme get this reviewed and we can get a release up.

Fixed in 1.1.2.


[Feat] Add before and after execution middleware functions

Summary
This PR adds two new middleware functions, .withBeforeMiddleware() and afterMiddleware()
Competed Tasks

[x] Add the beforeMiddleware function and the middleware builder method
[x] Add the afterMiddleware function and the corresponding middleware builder method

Is there a documentation for this feature?

Not yet, I will document it along with the other custom loggerMiddleware task using the same ticket, since they are very similar.


merging tk_to_qujax and tk_to_qujax_symbolic and all related function…

…s / tests

Just had a thought, maybe we should rename qujax_to_tk to qujax_args_to_tk ?

Can you check if this requires any changes in the example at: https://github.com/CQCL/pytket/blob/main/examples/python/pytket-qujax_heisenberg_vqe.py

Good thinking! It will be fine though as it just uses the most basic tk_to_qujax
After the symbolic API is finalised we will add a second example notebook that demonstrates the use of symbolic parameters

From my side we can merge this now :)


Transmit EPK and use as public key during decrypt

RFC 7518 Section <IP_ADDRESS> states:

The "epk" (ephemeral public key) value created by the originator for
the use in key agreement algorithms.  This key is represented as a
JSON Web Key [JWK] public key value.  It MUST contain only public key
parameters and SHOULD contain only the minimum JWK parameters
necessary to represent the key; other JWK parameters included can be
checked for consistency and honored, or they can be ignored.  This
Header Parameter MUST be present and MUST be understood and processed
by implementations when these algorithms are used.

EPK was referred to by comments in the code, but it seems that it was never used. Since the spec clearly states that the "Header Parameter MUST be present and MUST be understood and processed", I make the argument that this PR fixes a bug (#1951) and is not a feature enhancement.
This change does the following:

Takes the EncryptingKey's public parameter, encodes it as a JWK public key, and adds it into the JWT header.
Upon decryption, the discovered keys are used as the private decryption key. (This is typically TokenValidationParameters.TokenDecryptionKey)
JWK is extracted from the header and converted into an EcdsaSecurityKey. It is then used as the public key for the key agreement.

This PR also contains an extra commit that I've covered in PR #2119 . I can remove that from this change list if we decide not to proceed with that other PR.

@microsoft-github-policy-service agree company="Yubico"

@GregDomzalski we might as well drop #2119 and just take this PR.

I've updated this PR to be based on the new 7.x code.
I still need to do some regression testing on my side. But it would be really nice if we could get some traction on this PR. We're about to launch a product that takes a dependency on ECDH based key exchange / wrap algorithms working properly. I would really like to get these changes pushed upstream.
Please let me know what I can do to help make that a reality 😄

@GregDomzalski this looks good, we will have to account for users who have used the work-around.
I am thinking AppContext switch.

Some users could have coded up using a workaround, so we have to account for that.
I propose we add an AppContext switch to provide an override of the logic.
https://learn.microsoft.com/en-us/dotnet/api/system.appcontext?view=net-8.0

@brentschmaltz Thanks for the feedback. That seems like a reasonable approach.
What would you like the default behavior to be?
Based on the documentation and assuming an opt-in to the new behavior, a possible switch identifier could be:
Switch.Microsoft.IdentityModel.UseRfcDefinitionOfEpkAndKid or perhaps
Switch.Microsoft.IdentityModel.SetEpkAndKidHeadersAccordingToRfc
I'm not quite sure how to describe the change in behavior, so I'm happy to take other name suggestions :smile:

Alrighty. Let me know if that aligns with what you were thinking.
The diff definitely looks a lot cleaner - basically just adds at this point.
I introduced a centralized (public) class in Microsoft.IdentityModel.Tokens for defining constants for the switch values. There's only one const now - but I figured it would be a useful thing to have for consumers. Not to mention it provides a place to hang some documentation off from.
Here's the signature and accompanying documentation:
namespace Microsoft.IdentityModel.Tokens;

/// <summary>
/// Identifiers used for switching between different app compat behaviors within the Microsoft.IdentityModel libraries.
/// </summary>
/// <remarks>
/// The Microsoft.IdentityModel libraries use <see cref="System.AppContext" /> to turn on or off certain API behavioral
/// changes that might have an effect on application compatibility. This class defines the set of switches that are
/// available to modify library behavior. Application compatibility is favored as the default - so if your application
/// needs to rely on the new behavior, you will need to enable the switch manually. Setting a switch's value can be
/// done programmatically through the <see cref="System.AppContext.SetSwitch" /> method, or through other means such as
/// setting it through MSBuild, app configuration, or registry settings. These alternate methods are described in the
/// <see cref="System.AppContext.SetSwitch" /> documentation.
/// </remarks>
public static class AppCompatSwitches
{
    /// <summary>
    /// Uses <see cref="EncryptingCredentials.KeyExchangePublicKey"/> for the token's `kid` header parameter. When using
    /// ECDH-based key wrap algorithms the public key portion of <see cref="EncryptingCredentials.Key" /> is also written
    /// to the token's `epk` header parameter.
    /// </summary>
    /// <remarks>
    /// Enabling this switch improves the library's conformance to RFC 7518 with regards to how the header values for
    /// `kid` and `epk` are set in ECDH key wrap scenarios. The previous behavior erroneously used key ID of
    /// <see cref="EncryptingCredentials.Key"/> as the `kid` parameter, and did not automatically set `epk` as the spec
    /// defines. This switch enables the intended behavior where <see cref="EncryptingCredentials.KeyExchangePublicKey"/>
    /// is used for `kid` and the public portion of <see cref="EncryptingCredentials.Key"/> is used for `epk`.
    /// </remarks>
    public const string UseRfcDefinitionOfEpkAndKid = "Switch.Microsoft.IdentityModel.UseRfcDefinitionOfEpkAndKid";
}

Let me know if there's any additional API or doc review that needs to happen as a result of this addition.
I really appreciate your time looking into this and providing feedback. Thanks!

Hey @brentschmaltz - just following up here.

@brentschmaltz do we want to take this?

@jennyf19 we should take this for 8.

@GregDomzalski there are some conflicts, are you able to fix them?
We would like to get this into our 8 release that will be picked up by asp.net 9.

@jamiehankins @aafortner - Can you guys take this over?

Hi @brentschmaltz - I won't be able to do this personally as I'm no longer with Yubico, but I did hand this off prior to my departure. I'll work with my former colleagues to make sure we get this branch updated and merged in a timely manner. Thanks for the sign-off.

I don't and @AaFortner doesn't likely have write access to the fork. It takes less than five minutes to pull dev and rebase this branch on it. The only conflict is in a class header comment.
If @GregDomzalski still has write access to this, then maybe he can add us. Otherwise, we'd need to get our IT people involved.

Looks like I do still have access to this PR itself which means I can simply clone the fork and point the PR to that. I'll give that a try in the morning.

I sync'd up with @GregDomzalski offline, and it sounds like he hit some access issues after all. I'll follow up with our IT to see if we can get Jamie and/or myself added.

@AaFortner @GregDomzalski the PR is small enough that i could cherry pick in the commits.
If it gets to be too much effort let me know.

@brentschmaltz It wasn't big at all. Just had to get access handled.
It should be up to date now.

@jamiehankins @GregDomzalski thanks folks, merged.


nuxt3 notworking

is it normal?

Hey; the package is now fully compatible with Nuxt 3, even has auto imports using @vueuse/sound/nuxt! :)

I'm currently unable to get this to work @Tahul . It says npm package not found when I try to install @vueuse/sound/nuxt.


Added Contributing-hi.md file (needs Hindi review)

What does this PR do?
Add  Contributing-hi.md file
Description
Why is this valuable (or not)?
its valuable for those people how stack with english and not read contributing guide's  but they not Hindi after reading this .md they were know it
#11298 solved .

@eshellman  please check the solution
Thank you

I would You to please check it and if everything is clear then please merge this pr

you have not resolved the merge conflicts correctly

can you please describe it where is conflicts are ??

read what you have now, you will see completely duplicated content. I suggest you start with a fresh branch


Typo Fix

TimlineJS -> TimelineJS

Thanks @BeansBeefBroccoli ! (I wonder what "TimlineJS" is like, generates lines of Tims?)


Total objects detected?

How to count of the all detected objects?

It is enough to parse the string "counting_mode" to get the count of the each detected object cluster so then you can add them all and get the total detected objects.


Enable explicit API mode

Enables explicitApiMode, which means that public methods, properties must be explicitly marked as such and have explicit return types.
This PR is currently based on #26 for convenience.

🧛 Project Code Coverage: 100.00%
Coverage of Modified Files:

File
Coverage

SealedEnum.kt
100.00%

Modified Files Not Found In Coverage Report:
CamelCase.kt
EnumForSealedEnumProvider.kt
GenSealedEnum.kt
SealedClassExtensions.kt
SealedEnumWithEnumProvider.kt
SuppressRedundantModifierInGetter.kt
TreeTraversalOrder.kt
WildcardedTypeParameters.kt
build.gradle.kts

Codebase cunningly covered by count Shroud 🧛

🧛 Project Code Coverage: 97.48%
Coverage of Modified Files:

File
Coverage

CamelCase.kt
83.87%

SealedClassExtensions.kt
100.00%

SuppressRedundantModifierInGetter.kt
100.00%

WildcardedTypeParameters.kt
88.24%

Modified Files Not Found In Coverage Report:
EnumForSealedEnumProvider.kt
GenSealedEnum.kt
SealedEnum.kt
SealedEnumWithEnumProvider.kt
TreeTraversalOrder.kt
build.gradle.kts

Codebase cunningly covered by count Shroud 🧛

  Generated by :no_entry_sign: Danger


Update hero.css

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main----.hlx.page/
After: https://----.hlx.page/

yellow looks OK


Redundant grouping in Gene Associations

Whilst I'm working on the CI pipeline for the WJ model, I've noticed we have a lot of redundant parentheses in our gene associations. Some examples are below
R_RC02241
((WBGene00020264 or WBGene00022646 or WBGene00044631) or (WBGene00010339 or WBGene00011543) or (WBGene00016934 or WBGene00007446 or WBGene00013995)) or WBGene00017888
R_rnasynth_m
((WBGene00009658 or WBGene00011791 or WBGene00012528) and WBGene00001596 and WBGene00014115) and (WBGene00012999 and WBGene00008781 and WBGene00000123 and WBGene00016140 and WBGene00004411 and WBGene00017300 and WBGene00013680)
Whilst this makes no difference to the actual way genes are handled, it is potentially something we should tidy up at some point.

I totally agree... I guest most of it is coming from the merging process. We should make clear rules for the future how this is used. I prefer to have the AND only for multiprotein complexes and not for lumped/nested reactions. If their are alternative multimers we can have parentheses llike (A AND B) OR (A AND C).


#323 excel converter

Allowed to used objects which inherits from cl_gui_alv_grid

Thank you Fidley, can you please also provide an example of usage... You can also create a new demo report
Ivan

I've done some programs in which I created a class which is inheriting from cl_gui_alv_grid. In such classes I usually add some common handling of toolbar and other events. Once done and can be reused within the project, but when I wanted to use A2X to bind ALV grid from my class this was not possible because you read only name of the class of object which was passed to bind_alv method. So I've added a check if passed class is not inheriting from other and if yes it's checking if this is one from handled by A2X. That's all. I don't think it needs a demo report. It's rather bug correction.

Ok thank you for the explanation
On Sat, Jan 10, 2015 at 1:46 PM, Łukasz Pęgiel<EMAIL_ADDRESS>wrote:

I've done some programs in which I created a class which is inheriting
from cl_gui_alv_grid. In such classes I usually add some common handling of
toolbar and other events. Once done and can be reused within the project,
but when I wanted to use A2X to bind ALV grid from my class this was not
possible because you read only name of the class of object which was passed
to bind_alv method. So I've added a check if passed class is not inheriting
from other and if yes it's checking if this is one from handled by A2X.
That's all. I don't think it needs a demo report. It's rather bug
correction.
—
Reply to this email directly or view it on GitHub
https://github.com/ivanfemia/abap2xlsx/pull/352#issuecomment-69469122.


Clean up "Should be removed" fields

In https://github.com/temporalio/api/pull/121 I added a few "Should be removed" comments to some fields. Remove them and mark them as reserved. Was not done in that PR to avoid doing any non-comments changes.

Looks like there are still some TODOs that snuck in there too so address those


Interpolation Removal Issue

Configs used:
https://www.mediafire.com/file/fbn4z053umr2c7r/legit.fw/file
https://www.mediafire.com/file/kab1akm8de71h64/devosal.fw/file
Description:
Teammate animations still nolerp'd (choppy animations, caused by removed interpolation frames)
Steps to reproduce:

Exclude "Interpolation" from the Visual -> Removal section
Join any server
Teammate will still have interpolations disabled.

Additional info:
Video of interpolation-less animations on teammates :
https://imgur.com/a/N9RLeTY
The Interpolation Removal on Visual only affects enemies.

user issue ngl

user issue ngl

What do you mean? I tried going to a match without injecting fware, and the animations are normal. I went and inject fware, and the problem gets replicated, suddenly it's like the game re-renders animations of player models.
I'm not sure what causes this problem, I attempted to fix it by always returning Hook.Original() to functions that hooks interpolation, but the problem still persists..

I solved this issue by removing most detour hooks, only adding the hooks related to features that I use.


rename include directory

Codecov Report

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

@@          Coverage Diff           @@
##           master    #379   +/-   ##
======================================
  Coverage    4.97%   4.97%
======================================
  Files           1       1
  Lines        4483    4483
======================================
  Hits          223     223
  Misses       4251    4251
  Partials        9       9

Continue to review full report at Codecov.

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

Thank you


Allow copy and pasting of image files.

In a markdown cell, it would be super neat if I could put in pictures there by both copy and pasting an image and by selecting an image from any directories in my computer without the need for code. This would enable me to teach python programming in a more visual way.

Currently, there is an option to do this through the base64 encoding of the image. You would use the following in a markdown cell:
![](data:image/jpeg;base64,***Image base64 code***)

I would very much like if this were automatically done when pasting image content in a cell.

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/5774, https://github.com/microsoft/vscode/issues/119961


Failed to fetch dynamically imported module

Hello, I have a problem when loading the module from a page other than the root of the site.
The application tries to import the script from the relative path of the page and not from the root.
I already tried to add this line "app.UsePathBase("/");" but nothing helps.
How can I force the import of the script from the root of the site?

https://github.com/zuozishi/MediaSession.Blazor/blob/294b5cc4252ad4e4a71b95161a93205e7ef4f582/MediaSession.Blazor/Components/MediaSession.cs#L14
I think the problem in here.


Is it possible to use differrent Django version?

Try to use Django 1.11.10 but failed.

Cartoview Version : 1.4.5
Geonode Version : 2.6.3
Django Version: 1.11.10

(myenv) az@ubuntu:~/sfd$ python manage.py makemigrations app_manager
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 364, in exec                       ute_from_command_line
    utility.execute()
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in exec                       ute
    django.setup()
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/__init__.py", line 27, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/apps/registry.py", line 85, in populate
    app_config = AppConfig.create(entry)
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/apps/config.py", line 120, in create
    mod = import_module(mod_path)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/geonode/social/apps.py", line 2, in <module>
    from actstream import registry
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/actstream/registry.py", line 11, in <module>
    from actstream.compat import generic, get_model
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/actstream/compat.py", line 22, in <module>
    from django.contrib.contenttypes import fields as generic
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/contrib/contenttypes/fields.py", line 5, in <mo                       dule>
    from django.contrib.contenttypes.models import ContentType
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/contrib/contenttypes/models.py", line 139, in <                       module>
    class ContentType(models.Model):
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/db/models/base.py", line 110, in __new__
    app_config = apps.get_containing_app_config(module)
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/apps/registry.py", line 247, in get_containing_                       app_config
    self.check_apps_ready()
  File "/home/az/.virtualenvs/myenv/local/lib/python2.7/site-packages/django/apps/registry.py", line 125, in check_apps_read                       y
    raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

no please use django==1.8.7

Thanks

you are welcome 💯


Zone.js 0.7.4 - View not updating

The code inside the callback of a MongoObservable subscription is not updating the view. Its working when I put zone.run(). Before the update I used v0.6 without problems.

I have the same problem (but doesn't seem related to zone.js version, things are still broken with 0.7.3 and 0.7.2)
Furthermore a map operator is not invoked. E.g.
const t = Task.find({}).map((tasks)=>{console.log(1); return tasks}).zone();

t.subscribe((tasks)=>{
 console.log('tasks: ', tasks);
})

the map operator is SKIPPED (no console.log) if I use zone()
I'm wondering why there aren't more people tripping into this issue.

Found a workaround. Moved the .zone() to the MeteorObservable.subscribe. E.g.
MeteorObservable.subscribe('AllTasks').zone().subscribe(() => {
     const t = Task.find({}).map((tasks)=>{console.log(1); return tasks}).zone();

     t.subscribe((tasks)=>{
       console.log('tasks: ', tasks);
    })
}


adds type hints for config

additional context can be found here https://github.com/markdoc/markdoc/issues/260

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


fix: issue template

Description
Fixed the tags, and added the domains table, w.r.t discussion with @bhavyaberlia

@ChakshuGautam can you please review


[ACR] Harden downloadBlob and getManifest validation

Packages impacted by this PR

@azure/container-registry

Issues associated with this PR

Fix #25645

Describe the problem that is addressed by this PR
Add extra validation to downloadBlob and getManifest:

Restrict manifest size to 4 MB
Throw early if bytes read during downloadBlob exceed the value in the
Content-Length header

Based somewhat on the Java PR for the same thing, but without validation of the Content-Range header since we are using optimistic download.

API change check
API changes are not detected in this pull request.


When will subscriptions be supported?

In the meantime, is there a way to integrate this library with https://github.com/edvinerikson/relay-subscriptions ?

Sorry, I not ready to answer about subscriptions right now. I have no experience, yet with them. And will look on subscriptions somewhere in the mid of summer.
You may see this fork https://github.com/zzish/react-relay-network-layer/commits/socket
BTW @blaiprat @edcarr maybe you have enough experience with subscriptions and can make PR?

Hi, the fork we have it's actively being used in our projects in Zzish, but I can't say at this point if it's standard enough to be merged, specailly after the release of Relay 1.0 wich supports subscriptions out of the box.
Give me some time to do a little more digging and I'll update this issue to see how can we help


Wiki broke

https://github.com/ariya/phantomjs/wiki/API-Reference-WebPage/_compare/41277d919d3b1216c3850cb4d3a19f0141144b80...14e2e75be29b6bd44c1c807fa66bd613c5ad647a
Several wiki pages are replaced with emoji characters.

That particular page got fixed: https://github.com/ariya/phantomjs/wiki/API-Reference-WebPage
--but others seem to be oddly wiki-vandalized.

Fixed.


Refactor the PheWAS module

Tidying up the PheWAS code, addressing the following points:

[ ] Ideally read and write files to google bucket(s). Files that need to be read are:
The data file from phewas.org: phewas-catalog.csv
Mapping file from phewas.org: phecode_icd9_map_unrolled.csv.zip
OT mapping file from the mapping GitHub repository: phewascat.mappings.tsv
[x] Filter the evidence strings based on p-value (< 0.05) while reading in the phewas-catalog.csv file
[x] Move phewas-related settings back into settings.py file (from constants.py)
[ ] Consolidate run.py and make_efo_mapping.py into a single phewas.py file

Moved to 19.04 - post EFO 3 work.

Moving under "Roadmap: Harmonize evidence_datasource_parsers" #535

The PheWAS catalog parser has been revamped (see PR #44) and the main changes are the following:

Parser is now called PheWAS.py and is located directly in the modules directory. The phewascat directory in modules an all the files and scripts underneath it have been deleted.
Input and output file names are specified in settings.py instead of being hardcoded in module.
The input csv file has to be local
The Phecode to EFO mapping file is read from the GitHub mappings repo.
Odds ratio and number of cases have been moved to the evidence section from the unique_association_fields.
Target and disease ids have been added to unique_association_fields

In a nutshell, the parser has been simplified given that now that the Phecodes to EFO mappings have been completed (see #420) there is no need to use complementary files for the mapping.
The only thing that is left to be done is to refine the unique association fields to reduce the number of duplicate evidence strings. That work can be followed in #795.


Fix disconnect from redis

The redis package has no disconnect method, use quit instead

Your change breaks all the tests for ioredis, which is now the default for this package.
This is a safer chnge: https://github.com/taskrabbit/node-resque/commit/e59c01960855abfef6967838f3065cfdf3201d37

> npm publish
+<EMAIL_ADDRESS>


Contributor guide

We didn't have a contributor guide yet, so this is a first attempt at that. Right now it focuses on how people can contribute to the project, and in understanding where everything goes, and what each thing does. Some parts (like the coding style section) need to be improved.
What I'm mostly interested here is if this document is okay. Are there areas that need to be better explained, or important information that's mising?
/cc @origamitower/folktale

Its good.


knapsack_pro 7.6.1 fails with RSpec

Dependabot created a PR on our repo to bump knapsack_pro from 7.6.0 to 7.6.1 and our build fails inside KnapsackPro internals, probably due a require that was missed on #262. This is the backtrace we get 👇
/bundle/ruby/3.3.0/gems/knapsack_pro-7.6.1/lib/knapsack_pro/formatters/time_tracker.rb:148:in `now': uninitialized constant KnapsackPro::Utils (NameError)
        KnapsackPro::Utils.time_now
                   ^^^^^^^
	from /bundle/ruby/3.3.0/gems/knapsack_pro-7.6.1/lib/knapsack_pro/formatters/time_tracker.rb:23:in `initialize'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/formatters.rb:157:in `new'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/formatters.rb:157:in `add'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/configuration.rb:997:in `add_formatter'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/configuration_options.rb:122:in `block in load_formatters_into'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/configuration_options.rb:122:in `each'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/configuration_options.rb:122:in `load_formatters_into'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/configuration_options.rb:24:in `configure'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:132:in `configure'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:99:in `setup'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:86:in `run'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:71:in `run'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:45:in `invoke'
	from /bundle/ruby/3.3.0/gems/rspec-core-3.13.0/exe/rspec:4:in `<main>'

What does the knapsack pro command look like that you use to run tests? I'm wondering why our integration tests did not catch this issue.
Please could you use 7.6.0 before we fix this issue.

Our pipeline runs KNAPSACK_PRO_LOG_LEVEL=info bin/rake knapsack_pro:rspec

We've released the knapsack_pro 7.6.2 version that fixes the problem. Please update it.


Added code/documentation example for converters.

:white_check_mark: Build ExtendedXmlSerializer <IP_ADDRESS>8-kxymrolk completed (commit https://github.com/ExtendedXmlSerializer/home/commit/f5e1eec10c by @Mike-EEE)
Install it by running the following command in Package Manager Console:
Install-Package ExtendedXmlSerializer -Version <IP_ADDRESS>8-kxymrolk -Source https://ci.appveyor.com/nuget/extendedxmlserializer-preview


odd error on failed tcp stream

PS C:\Users\Isaac> Connect-PowerCat -RemoteIp <IP_ADDRESS> -Port 443 -Execute
WARNING: Connection to <IP_ADDRESS>:443 [tcp] failed. Exception calling "EndConnect" with "1" argument(s): "No connection
could be made because the target machine actively refused it <IP_ADDRESS>:443"
WARNING: Failed to open Tcp stream. Method invocation failed because [System.Net.Sockets.TcpClient] doesn't contain a
method named 'Dispose'.
WARNING: Tcp connection broken, exiting.
WARNING: Failed to dispose Tcp socket. You cannot call a method on a null-valued expression..

"No connection could be made because the target machine actively refused it <IP_ADDRESS>:443"
This means the firewall on that machine blocked it, all the rest are a waterfall of the blocked connection. I put in a lot of warning messages for trouble shooting. These will likely be changed to verbose outputs soon.

On Nov 11, 2015, at 2:48 PM, Isaac Levy<EMAIL_ADDRESS>wrote:
"No connection
could be made because the target machine actively refused it <IP_ADDRESS>:443"

The bug was about

Method invocation failed because [System.Net.Sockets.TcpClient] doesn't contain a method named 'Dispose'.

and

Failed to dispose Tcp socket. You cannot call a method on a null-valued expression..

You're right. It seems the older CLR in v2.0 didn't have the dispose method. Try it now.


Complete the set of instructions with two-nops afterward

Fixes #14.
As per the CPU manual, https://cgi.cse.unsw.edu.au/~cs3231/doc/R3000.pdf, page 258 or A-46, the MFHI instruction says

"To ensure proper operation in the event of interruptions, the two instructions which follow a MFHI instruction may not be any of the instructions which modify the HI register: MULT, MULTU, DIV, DIVU, MTHI."

I have taken the liberty of adding all of these instructions to the keepout section after mflo and mfhi instructions. I also used Python's any keyword to make the line neater.
I removed mthi from the set because the SOTN decomp does not use that instruction, and because mthi and mtlo would require us to separate some of the logic for handling mflo versus mfhi, rather than the combined approach that is currently used. Therefore, ultimately, all this PR does is add the unsigned versions of mult and div to the keepout-zone.
I have confirmed that, with this change in place, the sotn-decomp project compiles successfully, so this should not introduce any regressions.

Awesome, thanks for finding the bug, and even bigger thanks for fixing it!


Show all DNS results in cft

Improve the ability of cft to explaining certificate issues in stackoverflow etc. One of the variable is the DNS hosts returned as seen by the OP Author, and secondly the variance between them.

Twitter
CN: 	api.twitter.com
...
CA: true

Strict Transport Security: max-age=631138519

OCSP status: GOOD

api.twitter.com/<IP_ADDRESS>: CN=api.twitter.com,OU=lon3,O=Twitter\, Inc.,L=San Francisco,ST=California,C=US
api.twitter.com/<IP_ADDRESS>: CN=api.twitter.com,OU=lon3,O=Twitter\, Inc.,L=San Francisco,ST=California,C=US
api.twitter.com/<IP_ADDRESS>: CN=api.twitter.com,OU=lon3,O=Twitter\, Inc.,L=San Francisco,ST=California,C=US
api.twitter.com/<IP_ADDRESS>: CN=api.twitter.com,OU=lon3,O=Twitter\, Inc.,L=San Francisco,ST=California,C=US

Facebook
CN: 	*.facebook.com
...
CA: true

Strict Transport Security: max-age=15552000; preload

OCSP status: GOOD

facebook.com/<IP_ADDRESS>: CN=*.facebook.com,O=Facebook\, Inc.,L=Menlo Park,ST=California,C=US
facebook.com/2a03:2880:f129:83:face:b00c:0:25de: java.net.SocketException: Network is unreachable: no further information


[CI] Label commenter workflow failing

Description
Label commenter workflow fails due to a problem with workflow configuration
Expected Behavior
Label commenter workflow should not fail because of an internal error with workflow configuration
Screenshots/Logs

To Reproduce
Steps to reproduce the behavior:

Create a PR in meshery
Add component/ui label to it
See error

Contributor Resources:

(Contributing Docs](https://docs.meshery.io/project/contributing)

@sudo-NithishKarthik it's not the UI label alone, all labels have stopped working because of that indentation. Hopefully that you have solved it'll work now


[Question] Undefined symbols when building with -fPIC

[REQUIRED] Please fill in the following fields:

Pre-built SDK from the website or open-source from this repo: Source (main)
Firebase C++ SDK version: 8.7.0
Main Firebase Components in concern: firebase_app
Other Firebase Components in use: all
Platform you are using the C++ SDK on: Linux
Platform you are targeting: iOS, Android

[REQUIRED] Please describe the question here:
Hi, I'm planning to use Firebase C++ SDK as a plugin in Unreal Engine (4.27). Using the library from the website, it gives this error when compiling with the supplied library
[1/2] Link (lld) libUE4Editor-TestFirebase.so
ld.lld: error: relocation R_X86_64_PC32 cannot be used against symbol firebase::kFirebaseVersionString; recompile with -fPIC
>>> defined in /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a(2821dc7f0f996caf95294ccbe3bb0f98_app_desktop.cc.o)
>>> referenced by app_desktop.cc
>>>               2821dc7f0f996caf95294ccbe3bb0f98_app_desktop.cc.o:(firebase::App::Create(firebase::AppOptions const&, char const*) (.part.0)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

Using fresh image of Ubuntu 20.04 LTS, I've set up build-essential, cmake, libssl-dev, python-is-python3, python3-pip from apt and installed Abseil-py, Protobuf with pip. Following the instruction, I've used cmake -DCMAKE_POSITION_INDEPENDENT_CODE=ON .. in the desktop_build directory then cmake --build . --target firebase_app to build the app library.
Unfortunately it gives different type of error when compiled with Unreal Engine:
[1/2] Link (lld) libUE4Editor-TestFirebase.so
ld.lld: error: undefined symbol: std::basic_ifstream<char, std::char_traits<char> >::basic_ifstream(char const*, std::_Ios_Openmode)
>>> referenced by app_desktop.cc:60 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:60)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_ios<char, std::char_traits<char> >::operator bool() const
>>> referenced by app_desktop.cc:61 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:61)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::istream::seekg(long, std::_Ios_Seekdir)
>>> referenced by app_desktop.cc:62 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:62)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:66 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:66)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::istream::tellg()
>>> referenced by app_desktop.cc:63 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:63)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_ios<char, std::char_traits<char> >::fail() const
>>> referenced by app_desktop.cc:70 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:70)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:74 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:74)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::istream::read(char*, long)
>>> referenced by app_desktop.cc:73 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:73)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_ifstream<char, std::char_traits<char> >::~basic_ifstream()
>>> referenced by app_desktop.cc:60 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:60)
>>>               app_desktop.cc.o:(firebase::(anonymous namespace)::LoadAppOptionsFromJsonConfigFile(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()
>>> referenced by app_desktop.cc:100 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:100)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:46 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:46)
>>>               app_desktop.cc.o:(__static_initialization_and_destruction_0(int, int)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:120 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:120)
>>>               app_desktop.cc.o:(firebase::AppOptions::AppOptions()) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 27 more times

ld.lld: error: undefined symbol: std::string::c_str() const
>>> referenced by app_desktop.cc:106 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:106)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:113 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:113)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:150 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:150)
>>>               app_common.cc.o:(firebase::AppOptions::app_id() const) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 14 more times

ld.lld: error: undefined symbol: std::string::operator+=(std::string const&)
>>> referenced by app_desktop.cc:109 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:109)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_common.cc:228 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:228)
>>>               app_common.cc.o:(firebase::app_common::LibraryRegistry::UpdateUserAgent()) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::string::operator+=(char const*)
>>> referenced by app_desktop.cc:110 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:110)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string()
>>> referenced by app_desktop.cc:110 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:110)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:100 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:100)
>>>               app_desktop.cc.o:(firebase::AppOptions::LoadDefault(firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:122 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:122)
>>>               app_desktop.cc.o:(firebase::App::~App()) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 95 more times

ld.lld: error: undefined symbol: std::string::operator=(char const*)
>>> referenced by app_desktop.cc:150 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:150)
>>>               app_desktop.cc.o:(firebase::App::Create(firebase::AppOptions const&, char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_desktop.cc:178 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:178)
>>>               app_desktop.cc.o:(firebase::App::SetDefaultConfigPath(char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by reference_counted_future_impl.cc:391 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/reference_counted_future_impl.cc:391)
>>>               reference_counted_future_impl.cc.o:(firebase::ReferenceCountedFutureImpl::SetBackingError(firebase::FutureBackingData*, int, char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 8 more times

ld.lld: error: undefined symbol: std::string::empty() const
>>> referenced by app_desktop.cc:186 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:186)
>>>               app_desktop.cc.o:(firebase::App::SetDefaultConfigPath(char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_common.cc:464 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:464)
>>>               app_common.cc.o:(firebase::app_common::GetOuterMostSdkAndVersion(std::string*, std::string*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_common.cc:201 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:201)
>>>               app_common.cc.o:(firebase::app_common::LibraryRegistry::RegisterLibrary(char const*, char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 10 more times

ld.lld: error: undefined symbol: std::string::back()
>>> referenced by app_desktop.cc:187 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:187)
>>>               app_desktop.cc.o:(firebase::App::SetDefaultConfigPath(char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::string::operator+=(char)
>>> referenced by app_desktop.cc:189 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_desktop.cc:189)
>>>               app_desktop.cc.o:(firebase::App::SetDefaultConfigPath(char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&)
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::AppOptions(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::AppOptions(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::AppOptions(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 24 more times

ld.lld: error: undefined symbol: std::string::operator=(std::string const&)
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::operator=(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::operator=(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app.h:99 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/include/firebase/app.h:99)
>>>               app_desktop.cc.o:(firebase::AppOptions::operator=(firebase::AppOptions const&)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 12 more times

ld.lld: error: undefined symbol: std::string::append(char const*)
>>> referenced by basic_string.h:6061 (/usr/include/c++/9/bits/basic_string.h:6061)
>>>               app_desktop.cc.o:(std::basic_string<char, std::char_traits<char>, std::allocator<char> > std::operator+<char, std::char_traits<char>, std::allocator<char> >(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by basic_string.h:6123 (/usr/include/c++/9/bits/basic_string.h:6123)
>>>               app_common.cc.o:(std::basic_string<char, std::char_traits<char>, std::allocator<char> > std::operator+<char, std::char_traits<char>, std::allocator<char> >(std::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

ld.lld: error: undefined symbol: std::allocator<char>::allocator()
>>> referenced by app_common.cc:284 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:284)
>>>               app_common.cc.o:(firebase::app_common::AddApp(firebase::App*, std::map<std::string, firebase::InitResult, std::less<std::string>, std::allocator<std::pair<std::string const, firebase::InitResult> > >*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_common.cc:320 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:320)
>>>               app_common.cc.o:(firebase::app_common::FindAppByName(char const*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_common.cc:345 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_common.cc:345)
>>>               app_common.cc.o:(firebase::app_common::RemoveApp(firebase::App*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced 36 more times

From these errors, it seems like the library is missing some standard c++ headers, but I don't know which or how to include/link into the library.
*Not sure if this is relevant, but UE4.27 is using clang-11.0.1-based toolchain to cross-compile.

Hi @drpsyko101,
The original error is expected since we don't provide libraries compiled with -fPIC enabled.

From these errors, it seems like the library is missing some standard c++ headers, but I don't know which or how to include/link into the library.

Yep, these errors you're encountering with your custom-built libraries look to be link-time issues and not compile-time issues (that is, not a problem with your headers).  The linker attempts to resolve symbols that are in the C++ Standard Library, as you guessed, but they're missing and cannot be found.
Specifically the standard library includes the symbols for std::strings, std::istreams, and the std::allocator missing symbol. Android targets require libc++ , and we internally test against this on iOS as well (see our iTest integration projects).
Unfortunately I'm not too familiar with how Unreal Engine build configuration works.  It might be worth asking their support about how you can ensure libc++ is configured correctly in your link path, and also to ensure that you link with the corresponding -fPIC flag as well.
I hope this helps!

Thanks @DellaBitta for the clarification. It does seems like it is related to Unreal Engine build configuration rather than compile issue. I'll bring this up to Epic and hopefully get a solution from their side.

Ok, thanks for following up. Also, if you would, please let us know what you find out so that we may help others in the future!

Before attempting to change UE4 linux compiler (and possibly a lot of codebase), I've decided to use similarly versioned clang to match as much dependencies as possible. In that regard, I've found out that I need to build firebase lib with libc++ and UE4 clang does not contain some include/lib needed such as algorithm.
For that, I've added
set (CMAKE_POSITION_INDEPENDENT_CODE ON)
set (CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++")
set (CMAKE_EXE_LINKER_FLAGS "-stdlib=libc++ -lc++abi")

to the CMakeLists.txt and build using clang-10 which still has algorithm include/lib via this command
CC=/usr/bin/clang-10 CXX=/usr/bin/clang++-10 cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX:PATH=../tdlib -DCMAKE_AR=/usr/bin/llvm-ar-10 -DCMAKE_NM=/usr/bin/llvm-nm-10 -DCMAKE_OBJDUMP=/usr/bin/llvm-objdump-10 -DCMAKE_RANLIB=/usr/bin/llvm-ranlib-10 ..
This will include all the missing standard c++11 header errors above, but new linker error pops out instead
ld.lld: error: undefined symbol: flatbuffers::Parser::Parse(char const*, char const**, char const*)
>>> referenced by app_options.cc:46 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_options.cc:46)
>>>               app_options.cc.o:(firebase::AppOptions::LoadFromJsonConfig(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a
>>> referenced by app_options.cc:52 (/home/ubuntu/Documents/git/firebase-cpp-sdk/app/src/app_options.cc:52)
>>>               app_options.cc.o:(firebase::AppOptions::LoadFromJsonConfig(char const*, firebase::AppOptions*)) in archive /home/ubuntu/Documents/git/FirebasePluginTest/Plugins/TestFirebase/Source/ThirdParty/libs/linux/x86_64/cxx11/libfirebase_app.a

Already tried using flatbuffers built from source -DFLATBUFFERS_SOURCE_DIR=/home/ubuntu/Documents/git/flatbuffers -DFLATBUFFERS_BINARY_DIR=/home/ubuntu/Documents/git/flatbuffers/build but the error still persists.
I'm a little bit happy with the progress, but will look into the linker association issue later on.


fix xg index name

right now is the name of the last graph + .xg.  doesn't make much sense when more than one graph.  should rename to something less confusing

Closed by #111


Error setting reconnect_time_min

nng 1.3.0
protocol pair:v1
gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
code:
sockx->set_opt_ms(nng::to_name(nng::option::reconnect_time_min), (nng_duration)1000);
throws
test: malloc.c:2401: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Aborted (core dumped)

This kind of error is caused by a memory corruption bug in your code.


Update cryptography to 0.8

https://cryptography.io/en/latest/changelog/#id1

Seems like a fine thing to do. I believe this is just the version pulled in by PyOpenSSL and is not really used by SuPPort directly at the moment. Any specific reason why you singled out this package for a version bump? I don't see any major bugfixes or anything?

I recently updated it on a separate project and noticed it was behind a version in this one

Ah, ok, good lookin out! I'll see how bumping that version plays with our feature roadmap.


Added support for resolving nodes via an interface method

Summary of the changes (Less than 80 chars)

Added support for resolving nodes via an interface method.

Closes #4860

This would also address #5414 right?


More consistent default positioning of menu items

I noticed today that in the overview of accounts, the "new message" icon is in the middle of the menu bar, with to it's right a plus symbol to add new accounts.
When going into an account, the new message symbol shifts one position ot the right.
To me this has lead to some unconcious confusion many times, when I intent to write a new email but accidentally press the wrong button by muscle memory. Only now I realised this is because the icon is not in the same position in all menu's where it occurs.
Suggestion:
On the account overview menu, swap the "add account" button and the "new message button", so that buttons which occur on multiple views are consistently positioned accros those views.
It's a minor detail, but it makes life easier.

I had a more indept look at the sorting of menu items. I now see that on ladscape mode the first 3 items are shown as icons, the rest as menu items.
composing emails is of upmost importance on a email client, therefor it deserves a place on the menu bar as an icon.
Instead of switching the compose buttons with the new identity button on the identities overview, I suggest switching "compose" with "sort"on the inbox view. This way the compose button is prominetly displayed, while the sort button becomes the fisrt item in the menu. Composing is probably done more spontaniously and more often than sorting.

Looking at the code, I haven't been able to figure out where the order of menu items is determined.


Api Change & Reply System

Is there anyway you can change the API? I messed around with it a little but it just says undefined. Also can you make the bot actually reply instead of quoting? I don't know how to do it, maybe you can (i cant do pull requests i put it here hopefully you don't mind)

There are something called rate-limits in the api that is why you got the undefined error.
Yes I can remove the quoting system

You can even open a pr.

pr? idk what that means but uhh the quoting is fine, i just would've liked a "reply" system (you know, the one that says like replying to ___ and has a ping/no ping option) if you don't know how to do it, no problem. This is still fine and you saved my day with your bot <3

pr? idk what that means but uhh the quoting is fine, i just would've liked a "reply" system (you know, the one that says like replying to ___ and has a ping/no ping option) if you don't know how to do it, no problem. It's just that i've seen a few bots do it so it must be possible. This is still fine and you saved my day with your bot <3

I can do that also "pr" means pull request xD

pr? idk what that means but uhh the quoting is fine, i just would've liked a "reply" system (you know, the one that says like replying to ___ and has a ping/no ping option) if you don't know how to do it, no problem. It's just that i've seen a few bots do it so it must be possible. This is still fine and you saved my day with your bot <3

I can do that also "pr" means pull request xD

yeah i don't really know how to do pull requests lol... and also did you code the reply system?


[BUG] - tailwind styles aren't working in nextjs standalone build

NextUI Version
2.**
Describe the bug
In simple terms the project just created using nextui init my_app built in standalone mode,
bun .next/standalone/server.js - no styles applied.
bun run start - working as expected.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

create new application nextui init my_app
change output mode to standalone in next.config.js output: 'standalone'
build the application bun run build
run the application using bun .next/standalone/server.js
finally observe the web app in browser, in my case safari

Expected behavior
tailwind styles should show up in the web page built in standalone mode.
Screenshots or Videos
No response
Operating System Version
macOS Sonoma 14.5 - intel silicon
Browser
Safari

same problem, someone find a way to go ahead of this error?

Did you try to remove your .npmrc ? in some case that can fix the problem for Docker user

Have you setup tailwindcss ?

Have you setup tailwindcss ?

Yes, Styles are working as expected when run with dev or start. Problem with only standalone build.

Have you added your .npmrc on the build phase ?

The 'standalone' build doesn't copy the .next/static folder by default. Try copying it to .next/standalone/.next and see if it works.


update production deps

Only prod deps

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

:tada: This PR is included in version 3.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Thread safety, especially HolidayManager (?)

More information
Hello,
I haven't found any information about thread safety. My profiler shows, that e.g. HolidayManager.createManager() is quite time consuming.
Therefore, I would like to cache the instances per country / region.
Is this possible or are there any known multi-threading issues?
I don't know if HolidayManager is thread-safe.
If you have any information about thread-safety, I would be glad to know.
Thanks a lot!

Hey @HoffmannTom,
I would say yes the HolidayManager should be thread safe. We/I do create one HolidayManager per country and save them in a HashMap to access it later. We did not see any errors over the last years.

@derTobsch
Thanks for the information!


When CommandBarFlyout open direction is "Top", the origin point is not correct (Miss calculate the height of "PrimaryCommand")

Describe the bug

Steps to reproduce the bug

Steps to reproduce the behavior:

Show Commandbarflyout in different direction
Find bug

Expected behavior
CommandBarFlyout should always show from the point where mouse pressed
Version Info

NuGet package version:
Microsoft.UI.Xaml 2.5.0
Microsoft.UI.Xaml 2.6.0

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Fixing this will be a bit tricky. You'll need to get the secondary popup from the commandbar flyout and attach a handler to it's ActualPlacementChanged event, to determine if it will open above or below. Then you can call OpenAt and change the Enum value you use to open above...
This seems like something common enough that we should build it in automatically to winui2, but I don't think it is easy to fix.

So no solution for WinUI2.5 ?


Catching URL nonsense in a DOI

We should stop processing a DOI when we see an important URL character -- e.g. "?", "&" or "#".
Still there are some DOIs that have these characters in them.  e.g. 10.1002/(SICI)1097-0142(19960401)77:7<1356::AID-CNCR20>3.0.CO;2-#
But most of the time it's because we're processing a messy URL.

10.1002/(SICI)1097-0142(19960401)77:7<1356::AID-CNCR20>3.0.CO;2-#

I've met this one too!
doi_isbn_pubmed_and_arxiv.enwiki-20161201.tsv.bz2 also contains some /download such as:

10.18352/bmgn-lchr.7417/galley/7464/download
10.4038/tapro.v5i1.5654/galley/4523/download

That "/download" could be a perfectly valid part of a DOI.  At this point, we'll be implementing heuristics to know when to stop processing a DOI.  It seems we could have a list of known suffix patterns that we should strip -- like extensions, "/download", "/getPDF", etc.  That would mean DOIs that actually had that as part of the DOI would be broken, but in the end, I expect this will be more useful.

That "/download" could be a perfectly valid part of a DOI.

Are you sure? This is not how I read https://www.doi.org/doi_handbook/2_Numbering.html#2.5 :

Handle syntax imposes two constraints on the prefix — both slash and dot are "reserved characters", with the slash separating the prefix from the suffix and the dot used to extend sub prefixes.

AFAICT, everything starting with the second / in a matched string should be dropped.

Oh good.  I hadn't caught that in the spec.

Ah, I indeed misread the sentence, which is preceded by

Neither the Handle System nor DOI system policies, nor any web use currently imaginable, impose any constraints on the suffix, outside of encoding (see below).

Of course a DOI like 10./1234/abcdef or 10..1234/abcdef would be invalid. In the suffix, the dot is frequently used, but I've yet to find any slash. Sadly there's also stuff like:

10.1671/0272-4634(2002)022[0564:EAEFTC]2.0.CO;2
Which I think the current regex doesn't match.

All in all
I'm running an extraction on the latest dumps and to get a clean list of DOIs I wil run the output through these sed commands, with regexes which IMHO can easily be incorporated in mwcites:
s,/(getPDF|currentissue|issue|abstract|summary|pdf|asset|full|homepage|otherversions|epdf|issuetoc|meta|pdb|references|suppinfo|citedby|standard|download).*$,,g
s,(;jsessionid=.+|"/?>.*|<|\.|&amp|]]|:--&gt|</nowiki>|>| |'*\.?\)?\[http.+)$,,g
s,&([a-z]+=.*)$,,g
s,^([^(]+)\.?\)$,,g

cut -f5,6 citations.tsv | grep ^doi | cut -f2 | sed --regexp-extended -f doiclean.sed | sort

The cleanup reduces the latest dump extraction from 777452 to 765499 DOIs, which is a whopping 1.53745 % error correction. ;-)

Thanks for this thorough analysis.  Just finished reading through it.

Not sure if it's caught in the above issue or is a separate thing but we just ran into an issue with Google Maps URLs being caught as DOIs, because they look similar.

Were those regexes incorporated in the latest release https://figshare.com/articles/Wikipedia_Scholarly_Article_Citations/1299540 or should I run them myself after downloading it?

Self-answer: there's still all sorts of spurious DOIs (attached the whole list).
2018-03-23_dois.txt.gz
After applying my regexes above, the list goes from 1100422 to 1067405 lines.
2018-03-23_dois_cleaned.txt.gz


Using Actor.CreateFromGltf() creates a child actor in Unity but isn't accessible in the Nodejs App

When using Actor.CreateFromGltf(), the assets are created on a child actor (GameObject) but isn't accessible in the nodejs app.
It would make sense to apply the assets on the actor that is creating the glTF if it's a single mesh. Otherwise, update Actor.children[] so that each actor is accessible.
Current solution is to use AssetManager.loadGltf() then assigning the loaded assets manually to an empty Actor.

The way glTF in general, and the UnityGLTF loader in particular, is set up is it always creates a GameObject/actor for the scene you're loading, then puts the real contents underneath it. This is a consequence of how glTF itself is structured. The real contents are available, but you have to wait for the creation to complete: await rootActor.created(); the root actor will have its children populated by then. If you have more questions, please reopen this issue.


Support for global FIAT currencies

The wallet features EUR and USD, but it should support all global fiat currencies 🌎
Some providers:

Bitpay
https://bitpay.com/rates
Coindesk
https://api.coindesk.com/v1/bpi/currentprice/JPY, https://api.coindesk.com/v1/bpi/currentprice/BRL

Cool, the wallet has now 22 currencies! It certainly covers the most important ones, and it covers all my uses, but I'm wondering why you didn't pick https://bitpay.com/rates since it gives more than 100 currencies in a single call. Licensing issues I guess?

That's for technical reasons. Bitpay API returns an array which you have to parse. I prefer using the blockchain.info API where each currency is an object that you can retrieve with its code. It makes for a cleaner code.


Fix typo

.Net -> .NET

Verified editorial correction.

@changeworld while these are correct and much appreciated, these small requests do take a lot of time to process and randomizes many different people who read the requests.
It might be 30 different people seeing 30 different pull requests and spending 2 minutes each to approve a one letter change, so the time adds up.
As you aim high to help, please consider batching similar work for find-replace kinds of changes (a Azure > an Azure for example).  We also enjoy higher value changes other than spacing and capitalization and minor grammar. I'm not the approver, but seems like that would help for small issues. Regardless, thanks for your contributions.
Thanks again, Jason


Line Graphs

https://uxdesign.cc/designing-charts-principles-every-designer-should-know-5bd3969a0150

https://medium.com/@Kateryna_r_s/line-chart-design-made-simple-a1b823510674

@sabrinatbs would we be able to adjust the colours in these to match the colours used in the design system? i.e. you can use the colours Nick put for bar graphs.


Documentation for web support and integration

Flutter API docs should clearly specify features unavailable in the web and the known issues related to specific widgets. Basic web features should be well documented. For example many of tye features which completely depend on the browser can be achieved by using package:js. However this is not documented anywhere.

Hi @sidrao2006,
There are flutter web samples using different material design widgets, that may indicate which widgets are supported and working properly in web.
Also, this guide could also be helpful to know flutter's support for web and a FAQ.
Additionally, there are web supported plugins which shows current limitation in respective ReadMe which might be helpful to know what works in web and what not for that plugin.

@darshankawar , thanks a lot for the information. I knew about the  guide and the various plugins.
However I definitely didn't know about the samples, I think it wasn't documented in the guide.
As I have mentioned, the guides still don't include popular functions implemented in the web.
Thanks for the reply

@sidrao2006 Good to know you found the links helpful.
Do you feel you now have some more clarity / information on your question and if this issue can be closed ?
Thanks.

@darshankawar thanks for the reply.
As I mentioned, flutter has provided documentation, however a lot more is required- more for web functionality than the UI

I think there currently lacks official docs on how to deal with web-only imports in a multi-platform project. Or more broadly how to deal with code requiring platform dependent imports that would fail compiling on other platforms.
Dart do offer a way to do conditional exports. Using this technique you can have a proxy file that in this example export web.dart on web and not_web.dart on non-web targets. Then in common code you import this proxy file and get either web.dart or not_web.dart. This technique allow to put for example import 'dart:html' in web.dart without causing compilation of android/ios to fail.
// On Flutter Web the web.dart file is exported, otherwise not_web.dart
export 'not_web.dart'
  if (dart.library.html) 'web.dart';

What I typically do is to provide the same methods in both, but not_web being no-op and web version actually being functional. Then at other places in the code have if (kIsweb) myWindow.getHref().
If there is better/other ways that is meant to be the official solution, please document those as I'm just a random flutter app developer.


scrollWheelZoom set as false, map is still zoomable with mouse wheel

Hey ! :)
I have a hard time disabling the scroll wheel zoom on my map. The scrollWheelZoom option is set as false, but the map is still zoomable :
Code :
_map.leafletMap.options.scrollWheelZoom = false;
Result in console :

Do you have any idea about this issue ?
Thanks a lot in advance !
Em.

@mourner Why is it listed as an option then if it doesn't work? http://leafletjs.com/reference.html#map-scrollwheelzoom

@timblakely it works; if you set scrollWheelZoom: false when creating your map, it will not let you zoom with the scroll wheel.
Although not entirely apparent from the question, the issue is if you want to disable scroll wheel zoom after the map is instantiated, you can't do it by just overwriting the option. Leaflet has no way of knowing that you changed the option. Instead, you need to disable the scrollWheelZoom handler as described by @mourner above.

@perliedman Ah, sorry for the confusion.
All makes sense now, thanks.

map.scrollWheelZoom.disable(). is not working for my case.
I have initialised map earlier like :
map = new L.Map('container',
{
center: [20, 0],
zoom: 2,
attributionControl: false,
scrollWheelZoom: false
});
now on ctrl+scroll need to set  scrollWheelZoom: true. Can anyone please help , how to update the leaflet properties?

@snehakamble if you want to enabled the scroll wheel again, simply use map.scrollWheelZoom.enable() instead.

<l-map ... :options="{scrollWheelZoom : false,}" ...>

I'm trying to disable an existing map scrollWheelZoom as per the above
document.addEventListener("DOMContentLoaded", function () {         var existingMap = L.DomUtil.get('map-edit-field-geo-location-0-value');         existingMap.scrollWheelZoom.disable(); });
but am getting a TypeError: Cannot read properties of undefined (reading 'disable'). What am I missing?


96 biodetail

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--world-bank--aemsites.hlx.live/
After: https://96-biodetail--world-bank--aemsites.hlx.live/en/drafts/naina/bio-detail

Also, padding seems to be incorrect in different viewports.


[release-v1.11] Re-generate test/config/tls/cert-secret.yaml

What this PR does / why we need it:
As the certificates in the test/config/tls/cert-secret.yaml has been expired we need to bump it.
This cherry-pick https://github.com/nak3/serving/commit/10b25455ecb9ca6b4b7c862ca636e5ac3a3c766d
Does this PR needs for other branches:
/cherry-pick release-v1.10
/cherry-pick release-v1.9
/cherry-pick release-v1.8
Does this PR (patch) needs to update/drop in the future?:
NONE

/cherry-pick release-v1.10
/cherry-pick release-v1.9
/cherry-pick release-v1.8

/cherry-pick release-v1.9

/cherry-pick release-v1.8

/cc @ReToCode @skonto