failed compile with google.api.http extension, "google/api/Annotations.pbobjc.h" file not found

gRPC 1.0, "pod install" a proto with following google.api extension, failed to build in xcode.
import "google/api/annotations.proto";

    rpc Login(LoginArg) returns(LoginResponse) {
        option (google.api.http) = {
            post: "/user/login"
            body: "*"
        };
    }

It works correctly before I add google.api.http thing into it. Any clue to make it work?

@fabware how did you bring the annotations.proto file into your setup?

It exactly my problem is, since I don't have any clue how to craft a podspec for it.
Use sed comment out #import "google/api/Annotations.pbobjc.h", works temporarily but awkward.

Did you follow these instructions?

Thanks for your reply.
Yes, I have a working MyProject.podspec in my swift project.
In my proto definition, I have to use google/api/annotations.proto, which gives me compile error: google/api/Annotations.pbobjc.h header file not found.
It works before without including google/api/annotations.proto.

Did you make sure that the prepare_command of your podspec is passing google/api/annotations.proto to protoc, alongside your other proto files?

Thanks for your reply. I placed "google/api/annotations.proto"(with folders) into ../../proto, I assume it would be included.
   s.prepare_command = <<-CMD     #{protoc} \         --plugin=protoc-gen-grpc=#{plugin} \         --objc_out=. \         --grpc_out=. \         -I . \         -I #{protoc_dir} \         -I ../../proto \         -I #{protobuf_dir} \         ../../proto/*.proto   CMD

Oh, I think I know what's up. The last argument to protoc is which proto files to generate code for. You have ../../proto/*.proto, which will miss the subfolders. Try ../../proto/**/*.proto so it's recursive? A way to confirm this is to check if the files google/api/Annotations.pbobjc.h and google/api/Annotations.pbobjc.m were actually been generated.

../../proto/**/*.proto gives me error:
[!] /bin/bash -c
set -e
../Pods/!ProtoCompiler/protoc         --plugin=protoc-gen-grpc=../Pods/!ProtoCompiler-gRPCPlugin/grpc_objective_c_plugin         --objc_out=.         --grpc_out=.         -I .         -I ../Pods/!ProtoCompiler         -I ../../proto         ../../proto/**/*.proto

../../proto/**/*.proto: No such file or directory

hardcode folder as ../../.proto ../../proto/google/api/.proto compiles, but google/api/Annotations.pbobjc.h cannot be found anywhere.
After minor changes with
 s.subspec 'Messages' do |ms|
    ms.source_files = '**/*.pbobjc.{h,m}'

I can see google/api/Annotations.pbobj.h and other files under "Development pods", still it won't compile.

@fabware did u manage to solve this?

Yes, comment the headers works with the following scripts (replace FlashService with your own generated directory). Haven't touch it for months, don't if it still works.
pod install
sed -i '' -e 's/#import "google\/api\/Annotations.pbobjc.h"/\/\/ #import\ "google\/api\/Annotations.pbobjc.h" \/\/ automatically comment by grpc gen.sh/g ' ./FlashService/*.*
sed -i '' -e 's/    \[registry addExtensions:\[AnnotationsRoot extensionRegistry\]\];/\/\/     \[registry addExtensions:\[AnnotationsRoot extensionRegistry\]\]; \/\/ automatically comment by grpc gen.sh/g' FlashService/*.*

The above script + the following line fixed it for me (GAPIAnnotationsRoot instead of AnnotationsRoot):
sed -i '' -e 's/    \[registry addExtensions:\[GAPIAnnotationsRoot extensionRegistry\]\];/\/\/     \[registry addExtensions:\[GAPIAnnotationsRoot extensionRegistry\]\]; \/\/ automatically comment by grpc gen.sh/g' FlashService/*.*


Custom Color Scales for Conditional Formatting in Data Tables

Feature Description
In Data Tables, would like the ability to pass in a custom list of colors to define the conditional formatting color scale (contentType=colorscale). E.g colors={['#12da42', '#00000' , '#232323']}.
Goal of Feature
Allow for greater freedom, flexibility, and customization of data tables. Would enable so many great formats, such as green-to-red scales and inverted color scales (i.e. min is darker shade, while max is white). Current conditional formatting is somewhat limited with single colors and max always being the darker shade.
Current Solution / Workarounds
No current workarounds.
Alternatives
N/A

This one is very close! #1840

This looks incredible @hughess!  Can't believe how fast your turned this around!

Closed by #1840!


Filters are ignored

When filters are added to instantsearch.configure they are not propagated to meilisearch.
so doing
<Configure filters={`categories = "test"`} hitsPerPage={10} />

when using react is not filtering the results.

Hello thanks for the issue and the PR! I've checked that, it seems ok, I'm going to merge it!


Complete re-design

I have completely redesigned the home page with new icons and design.

It's nice, but I think it's too white and simple. I do like the puff you added. Would it be okay if I implement that on the original?

Sure

Thanks! I'll be implementing it to my version soon.


Consider supporting some more of MiniZinc's Graph sets

It would be good if there would be a set/sets that would allow to encode
that two specific nodes of a graph (modelled as a NxN boolean adjacency matrix)
are / are not reachable from one another.
This is an obvious thing given an actual, non-symbolic, graph
e.g. by simply looking at the graph reachability matrix,
which can be computed by raising the boolean adjacency matrix
to a certain power (by performing matrix self-multiplication multiple times).
but that doesn't so nicely translate to JuMP.
Its easy to model with quadratic constraints, but the performance,
even on the most toy examples seems unsatisfactory.
Its straight-forward to model binary matrix multiplication with linear constraints,
but the number of constraints scales with cube of the number of graph nodes,
so even on the most toy example that results in millions of constraints,
and while the solver performance seems better, it's still unsatisfactory.
I haven't looked deeper, but even just creating those constraints via @constraint can take minutes.
I haven't looked into modelling it as a NLP problem, partly because that iface is still unsupported by both HiGHS and SCIP,
and i'm not sure if there even is any solver that supports said new iface and (MI)LP constraints.
Thus, the only thing left to check is constraint programming.
https://docs.minizinc.dev/en/stable/lib-globals-graph.html#mzn-globals-graph-reachable seems useful,
but i'm not sure about the inverse (non-reachability).

I have transferred this issue to MiniZinc.jl.
If we come up with something that is broadly useful, we can consider adding it to MOI.

So perhaps the right approach is to define a bunch of MOI sets in MiniZinc.jl
predicate reachable(int: N,
                        int: E,
                        array [int] of int: from,
                        array [int] of int: to,
                        var int: r,
                        array [int] of var bool: ns,
                        array [int] of var bool: es)

would become something like:
"""

## Usage

```
@constraint(model, [r; ns; es] in MiniZinc.Reachable(...))
```
"""
struct Reachable <: MOI.AbstractVectorSet
    N::Int
    E::Int
    from::Vector{Int}
    to::Vector{Int}
end

function _write_constraint(
    io::IO,
    predicates::Set,
    variables::Dict,
    f::MOI.VectorOfVariables,
    s::Reachable,
)
    # something here
    return
end

One more thing i hadn't checked yet, was User-defined operators (UserDefinedFunction),
but apparently out of all the solvers that supports (MI)LP,
none support UserDefinedFunction. Oh well...

MiniZinc.jl cannot support user-defined functions because it is a file-based I/O. The user-defined functions supply only callback oracles in Julia.

The adjacency matrix is a matrix of boolean JuMP variables and the nodes are fixed ? Can't you do a sort of MAX-FLOW/MIN-CUT formulation ? Nodes are unreachable is equivalent to the MAX-FLOW/MIN-CUT being zero. If you make the classical formulation and you force the flow for each edge to be zero if the boolean of the adjacency matrix is false (or the corresponding action for MIN-CUT), then is should probably work


make jobs more resilient

catch inner exceptions to be able to proceed with remaining ELBs / instances
don't fail on not found instance ids

Codecov Report

Merging #501 into master will decrease coverage by 0.25%.
The diff coverage is 20.45%.

@@             Coverage Diff              @@
##             master     #501      +/-   ##
============================================
- Coverage     54.95%   54.69%   -0.26%
  Complexity      517      517
============================================
  Files           133      133
  Lines          3008     3033      +25
  Branches        204      205       +1
============================================
+ Hits           1653     1659       +6
- Misses         1274     1293      +19
  Partials         81       81

Impacted Files
Coverage Δ
Complexity Δ

...g/zalando/stups/fullstop/jobs/rds/FetchRdsJob.java
85.1% <ø> (ø)
7 <0> (ø)
:arrow_down:

...g/zalando/stups/fullstop/jobs/ec2/FetchEC2Job.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...stop/jobs/common/impl/EC2InstanceProviderImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ullstop/jobs/elb/FetchElasticLoadBalancersJob.java
52.34% <33.33%> (-0.99%)
9 <0> (ø)

...g/zalando/stups/fullstop/jobs/ami/FetchAmiJob.java
82.47% <50%> (-1.23%)
22 <5> (ø)

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 d826ec7...7a99aff. Read the comment docs.

👍

👍

:+1:


Add optimizer concepts

@Aertalon What do you think about this approach? Should we remove the directories to simplify the directory hierachy? I think we might need a new header for utilities (e.g. is_specialization_of).


More detailed outline/document symbol information

The LSP supports an additional parameter to the Symbol[] response to the documentSymbol request, which is used to retrieve outline and all the document symbols. This currently unused parameter (detail) might be useful to convey some more information about the various symbols for the file. For example:

The signature for functions
The type for variables
The base classes for classes and structs
maybe more that i did not think of...

To demonstrate this I have made a prototype clangd build in which I have been able to implement the first two points that i described before (I could not reliably get the base classes without crashing the server sometimes) and this is the resulting outline for comparison:

I think this might be a useful addition because:

Reading a signature directly in the outline might be useful for differentiating overloaded functions
Knowing the type of a variable in addition to its name helps to identify it quicker
Those details are added in a non too intrusive manner
Those details are also visible in the breadcrumbs

Right now I am working on the prototype and I am having a few difficulties grasping the internal structure of clang and its classes, which means that I am not sure my code is valid in any case.. So I wanted to report it as a feature request at least to keep track of it and have some discussion. I can provide the code if anyone is interested of course.

I agree this would be useful. Note, we already have #520 on file for the function signature part and there's some discussion of it there.
If you'd like to work towards contributing a patch for this, and run into questions, I'm happy to try and answer. It's probably easiest to ask them in the #clangd channel of the LLVM Discord, but you're welcome to ask questions here in the issue as well.

There were improvements made in this area in https://reviews.llvm.org/D96751. @rapgenic do you feel they have addressed this issue sufficiently?


[match] Fix skip_set_partition_list option for certificate imports

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context
The option skip_set_partition_list of match doesn't work in all scenarios. This is an unexpected behaviour and happened due to the differences in importing a newly created certificate vs an existing one.
Description
match uses cert when creating new certificate and cert handles skip_set_partition_list well. In case the certificate is already in storage and imported on new device this option was ignored. I have made changes so that now all certificate imports will respect the skip_set_partition_list flag. This aligns match runner with match generator.
I have tested it in local for match imports.
Testing Steps
Point to this branch from Gemfile
Use bundler to install
Run Fastlane match to import certificates

@nekrich @joshdholtz @lacostej could you please review?


Sync error not helpful

I just wanted to backport a PR and I got the following error:
$ git node backport 33490 --to 14
Error
    at exports.runSync (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/lib/run.js:60:11)
    at new Session (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/lib/session.js:28:26)
    at new BackportSession (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/lib/backport_session.js:18:5)
    at main (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/components/git/backport.js:48:19)
    at Object.handler (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/components/git/backport.js:66:21)
    at Object.runCommand (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/node_modules/yargs/lib/command.js:240:40)
    at Object.parseArgs [as _parseArgs] (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/node_modules/yargs/yargs.js:1154:41)
    at Object.get [as argv] (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/node_modules/yargs/yargs.js:1088:21)
    at Object.<anonymous> (/home/ruben/.nvm/versions/node/v14.2.0/lib/node_modules/node-core-utils/bin/git-node:20:3)
    at Module._compile (internal/modules/cjs/loader.js:1176:30)

We should probably include stdout as well and maybe there's more to improve the error somewhere else as well.

@BridgeAR this was fixed in https://github.com/nodejs/node-core-utils/pull/426 - it just hasn't been published yet :)

Awesome! Should we maybe also include a hint how to fix that?

Can new release on schedule ? running into same issue.

With master looks like still exists:
root@localhost ~/node (master)# git node land 33975
Error
    at exports.runSync (/usr/local/lib/node_modules/node-core-utils/lib/run.js:60:11)
    at new Session (/usr/local/lib/node_modules/node-core-utils/lib/session.js:32:26)
    at new LandingSession (/usr/local/lib/node_modules/node-core-utils/lib/landing_session.js:19:5)
    at main (/usr/local/lib/node_modules/node-core-utils/components/git/land.js:131:17)
    at land (/usr/local/lib/node_modules/node-core-utils/components/git/land.js:114:21)
    at Object.handler (/usr/local/lib/node_modules/node-core-utils/components/git/land.js:78:14)
    at Object.runCommand (/usr/local/lib/node_modules/node-core-utils/node_modules/yargs/lib/command.js:240:40)
    at Object.parseArgs [as _parseArgs] (/usr/local/lib/node_modules/node-core-utils/node_modules/yargs/yargs.js:1154:41)
    at Object.get [as argv] (/usr/local/lib/node_modules/node-core-utils/node_modules/yargs/yargs.js:1088:21)
    at Object.<anonymous> (/usr/local/lib/node_modules/node-core-utils/bin/git-node:20:3)

My root cause is I misconfig upstream. The raw git command git config --get just return 1 with no stderr and stdout.

Closing as resolved by https://github.com/nodejs/node-core-utils/pull/426


Switch to using classList instead of className

The property className returns an object on some (possibly all?) SVG elements (despite stating in the linked documentation that it always returns a string. Maybe there is a different SVG implementation that I missed...). The object behaves under the interface SVGAnimatedString, which does not have method replace. If you have an SVG element somewhere within the mounted component then, as it iterates during a find, it processes the SVG element and throws TypeError: classes.replace is not a function.
I tested classList and it behaves correctly for SVG elements and regular elements alike. It also has a handy contains method too.

👍 I think this is a good approach, very simple. Ideally, we'd add some additional tests to verify this fixes SVG support, but until https://github.com/airbnb/enzyme/pull/421 is merged we can't test with actual SVG instances, so I think this is OK for now if it doesn't break any existing behavior.

#421 should be merged before we can merge something like this, so that we don't pull in something we can't test

This will need a rebase before merging, to get rid of the merge commit.

Rebased 👍

Rebased 👍

Can we add some tests that would fail (even if it's only in a few browsers) without this change?

Okay, test added and commits squashed.
I've confirmed that the test fails on branch karma (at ad3753687de55b176f9d81aef13f09133d3b64f6), and passes when the fix is applied. The test passes regularly within the current test framework, with and without the fix, since the error is specific to browser environments.
I wanted to leave a quick note on IE; seeing that the SVGAnimatedString docs state no support for Internet Explorer. I checked on MSDN for details of their implementation of the className property (see here) and it states that it is also an Object, but nothing further. I'm not sure what the interface for this object is.
But seeing that the current implementation doesn't really change anything (instead just adding the capability to handle it in environments where an issue has been reported), I think this is good to go?

Anything else I need to add to this?

@horyd looks like you need to merge the changes from the master branch.

@horyd I tested className for svgs in IE9/10/11 and className returned an SVGAnimatedString object, so it seems it is supported.

@Aweary Great, thanks for checking that! Should be good to go now :)

Hey guys, rebased this maybe half a dozen times now.. would love to get it merged :)

@horyd LGTM, but our tests seem to be failing in Node 0.10, so we'll need to address that first

@Aweary I have downloaded @horyd branch locally and have all tests pass on v0.10.37.
The error on CI is:
/home/travis/build/airbnb/enzyme/node_modules/eslint-plugin-import/lib/index.js:6
const rules = exports.rules = {
^^^^^

The CI have used eslint-plugin-import 1.10.1 (I checked the logs). On my local machine I have 1.10.2.
I think setting: "eslint-plugin-import": "^1.10.2" in package.json will fix the CI.
BTW I have also tested the @horyd PR in my app - it fixed my issue with mount and material-ci SelectField (which includes SVG icon element).

@Aweary Done! :)

Thanks again @horyd!

No worries! 😃


Manual input for Color code with 6 digit code

It seemed it does not reflect the change when entering 6  digit code while show alpha is enabled. Is it possible to auto convert 6 digit hex color code to 8 digit?

hi, the component design is like this, are you having any trouble? I might try to fix it

the next update of the component will keep the selection or enter a legal value

the function of legal value verification has been added in<EMAIL_ADDRESS>


gRPC Anoncreds client example

What this feature is about?
This is to provide Anoncreds related rpc testing while allowing users of this library to quickly get the idea how client can be built using protofile delivered with this project.
What will be delivered under this module
Deliver gRPC based client side code, preferably written in language other than Python to allow for diversity and giving a chance how client will be written and how will it interact with the server.
This module should provide a gRPC client that invokes almost all the rpcs that are exposed by the server.

will provide an example of issuer flow

https://github.com/bootstrapsp/miu/pull/37


Fix cooldown value

Closes #1211
Thanks a lot to @donkey-donkey for bringing this up and providing a patch!

Shipped as part of 0.28.11


Implement release actions and release 1.0.0

Implemente the release actions to build Android aar and iOS Frameworks and publish to Maven Central and github packages repository.

https://github.com/tiki/tiki-sdk-platform-channel/actions/runs/4758626234


Adding host option to vue ui tool

This allows for using vue ui in virtual development environments (like vagrant for example).

That's PR is already existing at #2568
Thanks!


Suppress AZC0030 warning in Azure.Health.Deidentification.csproj

Suppress AZC0030 warning in Azure.Health.Deidentification.csproj to allow future model names to end in Options
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

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


Compilation error, missing stropts.h header

Compiling vim from source (current master branch) errors with:
In file included from os_unix.c:27:
os_unixx.h:53:11: fatal error: stropts.h: No such file or directory
   53 | # include <stropts.h>
      |           ^~~~~~~~~~~
compilation terminated.

stropts.h is no longer distributed by glibc, ref.
My distro currently is coming with:
libc6 - 2.30-2
gcc - 4:9.2.1-3.1

Have you done "make reconfig"?

No, thanks for the tip :)


Postgres memory leak/high usage triggered by Ecto connection pool

Hello,
I'm having an issue where I get a very high memory usage until I get OOM regardless of how much memory I have (I have 64GB btw).
I first thought it was a Postgres issue, but I can trigger it with MySQL and at the same time I cannot trigger it if using identical queries with a python implementation or an Elixir implementation using Postgrex directly.
It only happens when using Ecto connection pool, even if I limit the pool to 1 connection only.
Environment

Elixir version (elixir -v): 1.10.2
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): PostgreSQL 12.2 (but I tested with other versions too and with and without docker).
Ecto version (mix deps): 3.3.4
Database adapter and version (mix deps): Postgrex 0.15.3
Operating system: Ubuntu 19.04 and Gentoo

Current behavior
So, the issue happens when I insert data in different tables, in my case, I have more than 12k tables. Each time I do a new insert query to a new table (new in the sense that I didn't touch it yet with the current connection) it will increase the memory usage and never release it (only when I close the connection).
To help diagnose it, I created some self-contained Elixir scripts that reproduce the issue, you only need to run it with Postgres installed and with the Ecto and Postgrex dependency too obviously. Also, you need to create the database with create database test_dev; via psql or other Postgres client.
The first script creates the tables:
tables = 1..800 |> Enum.map(fn i -> "table_#{i}" end)

{:ok, pid} =
  Postgrex.start_link(
    hostname: "localhost",
    username: "postgres",
    password: "postgres",
    database: "test_dev"
  )

Enum.each(tables, fn table ->
  query = """
  create table #{table} (
  id integer not null,
  value1 float not null,
  value2 float not null,
  timestamp timestamp not null
  )
  """

  Postgrex.query!(pid, query, [])
end)

The second script triggers the issue:
defmodule Repo do
  use Ecto.Repo,
    otp_app: :db,
    adapter: Ecto.Adapters.Postgres
end

defmodule Table do
  alias Ecto.{Changeset, Schema}

  use Schema

  @primary_key false

  schema "table" do
    field :id, :integer

    field :timestamp, :utc_datetime_usec

    field :value1, :float
    field :value2, :float
  end
end

steps = 16_383

tables = 1..800 |> Enum.map(fn i -> "table_#{i}" end)

{:ok, repo_pid} = Repo.start_link(
  name: :db,
  database: "test_dev",
  username: "postgres",
  password: "postgres",
  hostname: "localhost",
  timeout: 300_000,
  pool_size: 1,
  log: false)

(
Stream.iterate(1, fn id -> id + 1 end)
|> Stream.chunk_every(steps)
|> Stream.map(fn ids ->
  IO.puts("ids: #{hd(ids)}")

  Enum.map(ids, fn id ->
    %{id: id, value1: 1.1, value2: 1.1, timestamp: DateTime.utc_now()}
  end)
end)
|> Stream.map(fn values ->
  [table] = Enum.take_random(tables, 1)
  Ecto.Repo.Schema.insert_all(Repo, repo_pid, {table, Table}, values, [])
end)
|> Enum.to_list()
)

The third script runs an equivalent code as the second one but using Postgrex directly, it doesn't trigger the issue:
steps = 16_383

tables = 1..800 |> Enum.map(fn i -> "table_#{i}" end)

{:ok, pid} = Postgrex.start_link(
  hostname: "localhost",
  username: "postgres",
  password: "postgres",
  database: "test_dev")

(
Stream.iterate(1, fn id -> id + 1 end)
|> Stream.chunk_every(steps)
|> Stream.map(fn ids ->
  IO.puts("ids: #{hd(ids)}")

  ids
  |> Enum.map(fn id -> "(#{id}, 1.1, 1.1, now())" end)
  |> Enum.join(", ")
end)
|> Stream.map(fn values ->
  [table] = Enum.take_random(tables, 1)

  query = "insert into #{table} (id, value1, value2, timestamp) values #{values}"

  {:ok, _} = Postgrex.query(pid, query, [])
end)
|> Enum.to_list()
)

As you can see from the code, basically what it does is create a lot of rows to be inserted into one of the 800 tables created, then it selects one of these tables at random and does the query. The scripts will run infinitely until the user stops it or it runs out of memory (in the case of the second script).
To see the memory usage, you can simply use htop and filter to only show postgres processes, that way you can see the connection elixir will do with the postgres server and how the memory increases.
Also, for completeness, I ran a little python script called psrecord that logs the memory usage of a process, these are the results I got (note that I stopped it when it reached 2 GB usage).
Running the second script:
# Elapsed time   CPU (%)     Real (MB)   Virtual (MB)
       0.000        0.000      387.754     1746.008
       5.045        0.000      387.754     1746.008
      10.093        0.000      543.008     2108.859
      15.149        0.000      725.574     2309.859
      20.205        0.000      930.910     2544.359
      25.271        0.000     1111.582     2745.359
      30.328        0.000     1287.168     2945.863
      35.394        0.000     1474.262     3162.113
      40.452        0.000     1635.703     3347.113
      45.511        0.000     1806.688     3547.863
      50.579        0.000     1923.895     3681.613
      55.641        0.000     2083.008     3864.367

Running the third script:
# Elapsed time   CPU (%)     Real (MB)   Virtual (MB)
       0.000        0.000      358.648     1534.094
      15.138        0.000      423.621     1746.820
      30.303        0.000      497.297     1779.320
      45.477        0.000      540.789     1794.883
      60.629        0.000      542.285     1794.883
      75.782        0.000      533.785     1778.883
      90.943        0.000      534.137     1778.883
     106.101        0.000      534.145     1778.883
     121.251        0.000      534.148     1778.883
     136.407        0.000      547.562     1794.883
     151.573        0.000      534.168     1778.883
     166.726        0.000      534.172     1778.883

Thanks for the help!

This is caused by our query cache which is... surprise, surprise, per table! Given you have so many tables, you may want to disable it. I will work on something.

Set cache_statement: :per_operation in Ecto.SQL master and your problems should be solved.

Hey Jose, I just saw that in commit 377fdbacbe3170039bfc1806881f9650c16251b6 the changes of cache_write_statements was reverted.
Why was that? Without being able to set cache_write_statements to :per_operations I'm back to having my Postgres connections consume all my RAM and crashing with OOM :(

Hi @sezaru! That's because prepare: :unnamed also disables cache_write_statements altogether. So I thought that, if you are using prepare: :unnamed, you don't need cache_write_statement. Did I misunderstand it? :)

Oh, indeed! You are absolutely right.
Sorry, I didn't realise that..


OCIO Shenanigains

#41 also relevant here: Switched to using the OCIO config in Houdini. No errors are thrown as long as the texture manager isn't opened

Closed by commit 92016e2


Screen image shifted up/left when using transitions

I'm not sure what changed (likely a Flutter upgrade) but suddenly earlier today, routing to a screen using a Fluro transition causes the screen image to be shifted once it settles from the transition, so that the bottom left corner of the image is drawn at the center of the screen, with the remainder of the screen remaining black.

Can you update to 1.2.1? There were some breaking changes in how offsets were handled that should now be fixed. Let me know if you still see problems.

Thank you!  I'll check back in when I have a chance to test the update.
On Tue, Oct 10, 2017 at 2:46 PM, Albert Lardizabal<EMAIL_ADDRESS>
wrote:

Can you update to 1.2.1? There were some breaking changes in how offsets
were handled that should now be fixed. Let me know if you still see
problems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/goposse/fluro/issues/17#issuecomment-335586558, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACC_O8vwtAXeHvr-4QeX31efdGQPUZbCks5sq8mggaJpZM4PrXxn
.

The update to 1.2.1 fixed the problems I was having.
Thank you!
On Tue, Oct 10, 2017 at 8:06 PM, Michael Dresser<EMAIL_ADDRESS>wrote:

Thank you!  I'll check back in when I have a chance to test the update.
On Tue, Oct 10, 2017 at 2:46 PM, Albert Lardizabal <
<EMAIL_ADDRESS>wrote:

Can you update to 1.2.1? There were some breaking changes in how offsets
were handled that should now be fixed. Let me know if you still see
problems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/goposse/fluro/issues/17#issuecomment-335586558, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACC_O8vwtAXeHvr-4QeX31efdGQPUZbCks5sq8mggaJpZM4PrXxn
.


Bug when starting up powertoys and then using the tray icon to open window

Microsoft PowerToys version
0.37.2
Running as admin

[X] Yes

Area(s) with issue?
System tray interaction
Steps to reproduce

Close powertoys completely.
Open powertoys from start menu
once the powertoys tray icon loads in, double click it to open the window

✔ Expected Behavior
The powertoys configuration window opens up quickly with a double click
❌ Actual Behavior

Simply double clicking the icon doesn't seem to be working. I had to spam the button 10 times by the time it opened
The window also instantly closes the first time it opens. Only the window not the whole process.
If I spam the tray icon once more, the configuration window opens properly without giltching and closing

Other Software
No response

Hi @rsmyst
Thank you for reporting this.
To open PowerToys from the try icon you should use a single click.
If you press the tray icon just one time are you able to open the settings window?

Hi @rsmyst
Thank you for reporting this.
To open PowerToys from the try icon you should use a single click.
If you press the tray icon just one time are you able to open the settings window?

Clicking it once seems to do nothing...

Are you still experiencing this issue? /needinfo


Fetching after login doesn't work correctly after 2.4.1

Bug Report
In my app, I perform a login through Google, redirect back to my page, then call the database in order to get the profile table for that user.
After 2.4.1, this call seems to hang

That is, using Firefox, no information about the request will ever show, and it doesn't seem to terminate.
Possibly related to supabase/gotrue-js#597
If I first downgrade to 2.4.0, perform the login, then go back to 2.4.1, it seems to work fine. However, I checked the localstorage value for both cases and found no discernible difference. My API Edge Network logs look fine too, and show Supabase returning a 200 on the request to /profiles no matter the version used.
To Reproduce
I call the following code to log in:
async function signInWithGoogle() {   const { data, error } = await supabaseApp.auth.signInWithOAuth({     provider: 'google',     options: {       redirectTo: window.location.origin + '/sign-in-redirect'     }   })   return !!error }
and then from the page they're redirected to:
async function getCurrUserProfile() {   const { data, error } = await supabaseApp     .from('profiles')     .select();   if (data && data.length > 0) { return data[0] };   return error; } (Here I rely on an RLS policy where users only see their own profile)
The code never moves past awaiting the db call. When called in 2.4.0 though, or after logging in on 2.4.0, everything works fine.
System information

OS: Linux (Debian 11)
Browser: Firefox

This is likely related to https://github.com/supabase/gotrue-js/issues/593 and should be addressed with the auth team this week.

Does it now work as expected in version 2.5.0?

No, I was actually on 2.5.0 when I encountered this, then found through testing that 2.4.0 was the latest version that worked.

They reverted the code. So if updating to 2.5.0 doesn't resolve, then this could be another issue.
I was on 2.5.0 as well, then downgraded. After going back to 2.5.0 this morning I was good.

I'm importing client-side through jsdelivr so it could just be that their cache hasn't updated. Will try again after 24 hours have passed since the hotfix since I believe that's how long their cache is.

@earsinkle Do close the issue if it has stopped working for you.

Just saw that supabase-js got a version bump, can confirm that it works fine now on 2.6.0.


host operator sdk cli binary for Power (ppc64le)

Feature Request
Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
hosting a ppc64le binary
This PR got the helm image built for ppc64le: https://github.com/operator-framework/operator-sdk/pull/1533. Would it be possible to host that cli binary?
Happy to submit a PR if needed.

https://github.com/operator-framework/operator-sdk/releases/download/v0.12.0/operator-sdk-v0.12.0-ppc64le-linux-gnu
is that it? or am I misunderstanding?

hah, nope! someone was looking for it and I just assumed they'd done their due diligence. I should have done mine. thanks @jmccormick2001!


Foundation documentation links updated

Documentation updated for Density, Division , Responsiveness and Spacing

Thanks for raising the PR @PROJECTBUDDY21.
We require all contributors to JPMC projects to complete our Contribution Licence Agreement (CLA). You can sign as an individual or as representing your company. You only need to do this once and it covers all current and future projects managed under our GitHub organization.
The contribution agreement can be found here JPMC CLA, follow the instructions to complete and return via email.


Change color of Input focus

Hello! I Can't change color of Input focus. And didn't find a documentation.  I want to use tailwind colors, beside the limited colors in Materials.
The ideal should be, wenever I want to set a color, from tailwind.config theme:
<Input label="Username" color="black-1"  />
I get a results trying this (not ideal):
I achieved to change color in global.css:
  label {
    @apply  peer-focus:text-black-1  peer-focus:before:border-black-1 peer-focus:after:border-black-1 !important;
  }

And added the tailwind theme color in the className:
<Input label="Username" className="focus:border-black-1"  />
But when I did that only work with one color, I tryed to add another selector:
  .black-1 label {
    @apply  peer-focus:text-black-1  peer-focus:before:border-black-1 peer-focus:after:border-black-1 !important;
  }

And in the component:
  <div className="w-72 black-1">
    <Input label="Username" className="focus:border-black-1"  />
  </div>

I need two input colors, from tailwind, and ThemeProvider is to complex, and didn't find documentation

Hi @joaoperigo,
Please follow this page: https://www.material-tailwind.com/docs/react/theme/input
Cheers,
Sajad


Feature request / regression: py3.7 in production docker releases to support BlazingSQL

Issue:
Trying BlazingSQL via a container is difficult, and then going to it in production is difficult, because RAPIDS docker no longer has py3.7 and Blazing requires py3.7. This change happened about 2mo ago.
For new users, navigating dependencies is non-trivial, and for heavy users, the sizes involved make the process slow.
Workaround:
We created an interim container:
FROM gpuci/miniconda-cuda-rapidsenv:10.0-devel-ubuntu18.04-py3.7

RUN source activate rapids \
 && conda install -c rapidsai -c nvidia -c conda-forge -c defaults rapids=0.10 python=3.7

=> https://hub.docker.com/r/graphistry/graphistry-nvidia
cc @felipeblazing @mike-wendt

FWIW, just changed from gpuci/miniconda-cuda-rapidsenv (2.77GB including w/ conda install rapids)

What tag of this are you using? What you're describing isn't much different from what we do now.

nvidia/cuda:10-runtime-ubuntu18.04
We then do g++, boost, ... -> miniconda -> python3.7. I think we can eliminate some of the buildessentials / g++ stuff, but am unsure about numba, and for some of our downstream python/node libs, if we can move their compilation to buildtime. So keeping for now.

Releases now include both py3.6 and py3.7 versions of base and runtime Docker images:
https://hub.docker.com/repository/docker/rapidsai/rapidsai


feat: use internal package and update to slog

Overview

Fixes #4
Notes for reviewer

LGTM!
I have noticed that errors are logged a bit differently, any reason why we are avoiding something like logger.Error("error message", slog.String("error", err.Error())) to explicitly log an error message. Wrapping and printing the error does nothing in this instance.

@ramizpolic I wanted to keep the behavior as close to the existing implementation as possible.
I'm working on a solution that will allow adding details to errors directly (where it makes sense) and then we can tackle where the error belongs at the same time.


System.InvalidOperationException on build

Hi,
I have just tried the plugin in visual studio, and I am having an error on building my project. Every build i get a System.InvalidOperationException, exception details are below. I am running VS2019, build 16.11.00.
Severity	Code	Description	Project	File	Line	Suppression State
Error		System.InvalidOperationException: Due to high risk of deadlock you cannot call GetService from a background thread in an AsyncPackage derived class. You should instead call GetServiceAsync (without calling Result or Wait on the resultant Task object) or switch to the UI thread with the JoinableTaskFactory.SwitchToMainThreadAsync method before calling GetService.
at Microsoft.VisualStudio.Shell.AsyncPackage.GetService(Type serviceType)
at Microsoft.VisualStudio.Shell.Package.System.IServiceProvider.GetService(Type serviceType)
at Microsoft.VisualStudio.Shell.Package.PackageContainer.GetService(Type serviceType)
at System.ComponentModel.Container.get_Components()
at Microsoft.VisualStudio.Shell.Package.GetDialogPage(Type dialogPageType)
at Conan.VisualStudio.Services.VisualStudioSettingsService.GetConanPage() in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\VisualStudioSettingService.cs:line 21
at Conan.VisualStudio.Services.VisualStudioSettingsService.GetConanInstallOnlyActiveConfiguration() in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\VisualStudioSettingService.cs:line 36
at Conan.VisualStudio.Services.VcProjectService.ExtractConanProject(IVCProject vcProject, ISettingsService settingsService) in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\VcProjectService.cs:line 99
at Conan.VisualStudio.Services.VcProjectService.<>c__DisplayClass8_0.b__0() in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\VcProjectService.cs:line 115
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Conan.VisualStudio.Services.VcProjectService.d__8.MoveNext() in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\VcProjectService.cs:line 113
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Conan.VisualStudio.Services.ConanService.d__7.MoveNext() in C:\projects\conan-vs-extension\Conan.VisualStudio\Services\ConanService.cs:line 92
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Conan.VisualStudio.Menu.AddConanDependsProject.d__6.MoveNext() in C:\projects\conan-vs-extension\Conan.VisualStudio\Menu\AddConanDependsProject.cs:line 37
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Conan.VisualStudio.Menu.MenuCommandBase.d__6.MoveNext() in C:\projects\conan-vs-extension\Conan.VisualStudio\Menu\MenuCommandBase.cs:line 31			0

Actually I now cant reproduce this error, so closing ticket.


drivers: eth: mcux: Make MAC address Kconfig global for driver

Rather than having per instance Kconfig settings for how the mac address
is determined we make this global for the driver.  This helps as we
want to move the driver away from having per Kconfig instance paramaters
and getting instance information from devicetree when needed.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

After this it is not possible to have different setting for each controller, not sure if that is desired or needed.

Wasn't sure if it was either, part of the reason for me to post this was to raise that discussion.

We might as well move MAC address config to the device tree?

My 2 cents: AFAIK, adjusting stuff via device tree requires some legwork (DT overlays, etc.). From development comfort PoV, I'd prefer to have some development-related options at fingertips via Kconfig. That definitely don't have to be all options, just a few "master switches" useful during development (with the idea that "product development" should use best practices in configuration and setup, like device tree).

We might as well move MAC address config to the device tree?

We have support for getting the MAC address from DT already.  I'm not sure I understand the value of the ETH_MCUX_RANDOM_MAC option, but the ETH_MCUX_UNIQUE_MAC makes sense as that in theory is unique per board as its coming from some unique ID registers on the SoC.

I'm not sure I understand the value of the ETH_MCUX_RANDOM_MAC option

Possibly for security, rather like how phones change their mac address frequently to avoid tracking.

I'm not sure I understand the value of the ETH_MCUX_RANDOM_MAC

That's an option which can provide non-static (in particular, not duplicate across 2+ boards) MAC address, completely independent of any hardware features (because only generic PRNG is required). OTOH, ETH_MCUX_UNIQUE_MAC would require hardware-specific implementation (and support in the first place).

DEV-REVIEW (4/23): create a dt property for random-mac address so allow for per instance config.

Closed in favor of #24651.  The work in #24651 is based on discussion in dev-review meeting on Apr 23, 2020.


[PROPOSAL] OpenSearch health Project

Proposal
Taking a step forward for OpenSearch community contributions and foundation model, there should be a way to track the health of the entire OpenSearch project (including the repos part of the project). OpenSearch health is a heath dashboard project that showcases and keeps track of several OpenSearch health metrics.  The project goal is to show the health and status of the OpenSearch Project to community.
Background
OpenSearch health Project started with a goal to show the OpenSearch project health by displaying the metrics based out of multiple factors and attributes. In order to display the health we need to evaluate the data collected from multiple data sources.  The high level design is to scrape and collect several heterogenous data sources and create dashboards to visualize the download numbers and data patterns. The idea is to leverage the mechanisms and use the collected data part to run health metric calculations.
Tenets
Transparency: The health dashboard should be transparent and provide clear, real-time information about the OpenSearch project's status, including development activity, issue tracking, and other relevant metrics.
Key Metrics: It should display key metrics (classified as factors/themes/attributes) that indicate the project's health, such as the number of open issues, pull requests, commit activity, and the status of the build and test processes.
User-Friendly: The dashboard should be user-friendly and easy to understand, even for non-technical stakeholders. Use visualizations, charts, and color-coding to make data easily digestible.
Customization: Provide the ability to customize the dashboard to display the most relevant metrics for the project's specific goals and audience.
Historical Data: In addition to current data, the dashboard should offer historical data (filter by date), allowing users to track trends and changes in the project's health over time.
Integration: The dashboard should integrate with other tools and services commonly used in open source development, such as version control systems, continuous integration platforms, and issue tracking systems.
Security: Ensure that sensitive metrics data is not exposed on the dashboard, and that access is properly controlled and authenticated for sensitive project information.
Alerts and Notifications: Implement a system for sending alerts or notifications when certain metrics or health indicators fall below acceptable levels.
Community Engagement: Encourage community engagement by allowing users to contributors and to comment, discuss, or provide feedback directly through the Github repo.
Open Source Licensing: Since the health dashboard itself is an open source project, it should have a clear open source license, and its source code should be accessible for others to contribute to and use.
Accessibility: Ensure that the dashboard is accessible to all users, by following accessibility best practices.
Documentation: Provide clear documentation on how to use, contribute and interpret the information presented on the dashboard.
What problems are you trying to solve?
In the OpenSearch Community, the absence of a centralized dashboard poses a challenge in monitoring project health, assessing the current state of affairs, and tracking essential metrics. Without such a tool, it becomes difficult for the community to comprehend the overall status of the project/repository, including future goals and the current health condition. The lack of detailed information also hinders the attraction of additional contributions. The aim of this project is to present a comprehensive overview by surfacing as much information as possible, allowing a thorough understanding of the holistic status across various metrics.
What is the developer experience going to be?
A Dashboard application that will display all the project (sorted per repo) metrics, based on multiple factors and themes.
Terminology:

Factors: Factors are elements or conditions that can significantly influence the outcome of an score for a given theme.
Themes: Multiple co-related factors are sorted under a single theme, each theme can have one to many factors.

What is the user experience going to be?
A user will access the dashboard that will have the list of repos, each repo showing the current status of the themes and factors. It will also display the top action items that needs to be addressed in order to ensure the repo is healthy. Along with the metrics it will also display the thresholds for the themes and factors and by how much a given factor is exceeding the threshold.
Why should it be built? Any reason not to?
There is no reason not to build this project, as there is no central dashboard that displays the entire OpenSearch metrics at one place.
What will it take to execute?
Following is the high level design
Note: This repo is used to tackle the backend application and business logic that can power the frontend node application. The repo for the frontend node application is https://github.com/opensearch-project/opensearch-health-dashboard.

Closing this issue as the project initial setup is completed and the dashboard is now publicly accessible https://metrics.opensearch.org/.
Thank you


Check Ops: Adds assertEqual to the API

Description

This PR adds tf.assertEqual to the API. Fixes #638.

For repository owners only:
Please remember to apply all applicable tags to your pull request.
Tags: FEATURE, BREAKING, BUG, PERF, DEV, DOC, SECURITY
For more info see: https://github.com/tensorflow/tfjs/blob/master/DEVELOPMENT.md

This change is

Apologies for this review -- I just saw the TensorFlow docs which do this. I'm a little skeptical at all that we need this, or that the use case that would be used would fit the task (it's quite easy to check this yourself with a .data()).
Also it looks like the python version doesn't support eager anyways, so I'm inclined to close this out if that's okay with you!

@pyu10055 would we ever support assert ops in the converter? It seems not very useful.

Hi Manraj,
After some discussion we decided not to add tf.assertEqual() for now. See https://github.com/tensorflow/tfjs/issues/638 for more info.
Thank you for jumping on this and apologies for making you do this work!


[VL] Daily Update Velox Version (2024_06_13)

Upstream Velox's New Commits:
7646e70a3 by Zac Wen, Prevent cache write from exceeding IOV_MAX (10142)
9ab5e27ac by Jimmy Lu, Lazy materialization of RowType::parameters (10144)
f9f6d8228 by Deepak Majeti, Add support for Centos9 Stream + GCC12 (9903)
c5814c96a by Deepak Majeti, Keep DuckDB re2 headers private (10161)
9cc123f49 by Zac Wen, Specify data type in test for tsan (10153)
73fb02e27 by Jialiang Tan, Fix writer OOM by reducing initial flush buffer reservation (10147)
4a8591348 by xiaoxmeng, Free memory from stale cache entry early (10143)
b2bab6fd7 by xiaoxmeng, Add task deletion wait support (10124)

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_6070_time.csv
log/native_master_06_12_2024_7445f02c9_time.csv
difference
percentage

q1
34.62
33.87
-0.749
97.84%

q2
24.71
26.51
1.799
107.28%

q3
34.92
36.94
2.022
105.79%

q4
34.93
34.65
-0.274
99.21%

q5
67.75
69.47
1.723
102.54%

q6
6.01
5.84
-0.169
97.19%

q7
82.69
82.18
-0.513
99.38%

q8
84.57
85.19
0.617
100.73%

q9
121.92
120.19
-1.737
98.58%

q10
45.85
43.54
-2.302
94.98%

q11
22.89
20.47
-2.418
89.44%

q12
26.59
24.09
-2.504
90.58%

q13
37.36
37.22
-0.133
99.64%

q14
21.32
23.00
1.675
107.85%

q15
28.85
30.20
1.350
104.68%

q16
15.93
13.79
-2.149
86.51%

q17
104.10
102.85
-1.249
98.80%

q18
146.71
145.02
-1.685
98.85%

q19
13.71
16.14
2.425
117.68%

q20
28.94
27.34
-1.592
94.50%

q21
257.67
263.30
5.630
102.19%

q22
12.26
12.08
-0.173
98.59%

total
1254.27
1253.86
-0.407
99.97%


Correct behaviour for ^

Same as #12, I misunderstood that ^ was only for the regex root, but actually it is for any alternation.
Should just remove from regex root both hasPrefix and hasSuffix and have two regex op, one DollarOp and one CaretOp

The target architecture does not have enough "power" to correctly encode this behaviour.
The user should update the regex manually.
For example:
^ab|cd => ^(ab|.*cd)
While this could be done at the Regex syntax MLIR level, lets now take a new example:
ab(^cd)
This cannot be compiled in any meaningful way in Cicero.
Hence, I choose to only have ^ as the very first input of the regex, that need to be wrapped outside parenthesis.
The updated grammar is implemented here: https://github.com/thegoldgoat/cicero_compiler_cpp/blob/c6f999c0cfe5233f52c222ce35fde19ce693dda6/Parser/src/antlr-grammar/regexParser.g4#L7C6


[Request] ollama

Link to the package upstream website/repository
ollama
Utility this package has for you
Run latest models, checkout bug fixes and features as soon as they're released. Some models require additional programming for them to work. Ollama receives updates frequently, yet its version in Nixpkgs often lags far behind, making it difficult to test out new changes and hardware support.
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?

[X] Yes

Are you sure the package isn't available upstream already?

[X] Yes

Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?

[X] YES!

Have you read the README to ensure this package is not banned?

[X] YES!

More information
It's the ultra popular client to serve llms locally. Used by many.

https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/ollama/default.nix
https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/ollama.nix


Publish doc updates

OPS Build status updates of commit 90efc02:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/requirements-for-running-office-add-ins.md
:white_check_mark:Succeeded

docs/design/using-office-ui-fabric-react.md
:white_check_mark:Succeeded

docs/develop/create-sso-office-add-ins-aspnet.md
:white_check_mark:Succeeded

docs/develop/create-sso-office-add-ins-nodejs.md
:white_check_mark:Succeeded

docs/excel/custom-functions-best-practices.md
:white_check_mark:Succeeded

docs/excel/custom-functions-errors.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-charts.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-ranges.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-worksheets.md
:white_check_mark:Succeeded

docs/quickstarts/excel-custom-functions-quickstart.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/outlook-requirement-set-preview.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.1/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.1/outlook-requirement-set-1.1.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.2/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.3/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.3/outlook-requirement-set-1.3.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.4/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.5/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.5/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.5/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/outlook-requirement-set-1.6.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/outlook-requirement-set-1.7.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[CARBONDATA-155] Code refactor to avoid the Type Casting in compareTo method

…

+1 perfect I was also working on this you did it before me :)

test

Build Failed, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/

@mohammadshahidkhan are you still working on this?

Build Success with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1081/

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/503/Build result: FAILURE[...truncated 74.87 KB...][ERROR]   mvn  -rf :carbondata-spark-common[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/processing/pom.xml to org.apache.carbondata/carbondata-processing/1.2.0-SNAPSHOT/carbondata-processing-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Processing #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/integration/spark-common/pom.xml to org.apache.carbondata/carbondata-spark-common/1.2.0-SNAPSHOT/carbondata-spark-common-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Spark Common #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/examples/spark/pom.xml to org.apache.carbondata/carbondata-examples-spark/1.2.0-SNAPSHOT/carbondata-examples-spark-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/integration/hive/pom.xml to org.apache.carbondata/carbondata-hive/1.2.0-SNAPSHOT/carbondata-hive-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/common/pom.xml to org.apache.carbondata/carbondata-common/1.2.0-SNAPSHOT/carbondata-common-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Common #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/assembly/pom.xml to org.apache.carbondata/carbondata-assembly/1.2.0-SNAPSHOT/carbondata-assembly-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/pom.xml to org.apache.carbondata/carbondata-parent/1.2.0-SNAPSHOT/carbondata-parent-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Parent #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/examples/flink/pom.xml to org.apache.carbondata/carbondata-examples-flink/1.2.0-SNAPSHOT/carbondata-examples-flink-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/core/pom.xml to org.apache.carbondata/carbondata-core/1.2.0-SNAPSHOT/carbondata-core-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Core #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/hadoop/pom.xml to org.apache.carbondata/carbondata-hadoop/1.2.0-SNAPSHOT/carbondata-hadoop-1.2.0-SNAPSHOT.pomNo artifacts from carbondata-pr-spark-1.6 » Apache CarbonData :: Hadoop #502 to compare, so performing full copy of artifacts[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/integration/presto/pom.xml to org.apache.carbondata/carbondata-presto/1.2.0-SNAPSHOT/carbondata-presto-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/integration/spark-common-test/pom.xml to org.apache.carbondata/carbondata-spark-common-test/1.2.0-SNAPSHOT/carbondata-spark-common-test-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-1.6/integration/spark/pom.xml to org.apache.carbondata/carbondata-spark/1.2.0-SNAPSHOT/carbondata-spark-1.2.0-SNAPSHOT.pomchannel stoppedSetting status of d6607b03b621bb29d891222cb06a414381023c1f to FAILURE with url https://builds.apache.org/job/carbondata-pr-spark-1.6/503/ and message: 'Tests Failed for Spark1.6 'Using context: Jenkins(Spark1.6): mvn clean test -Pspark-1.6

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2600/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/502/Failed Tests: 1carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-spark-common-test: 1org.apache.carbondata.spark.testsuite.dataretention.DataRetentionConcurrencyTestCase.DataRetention_Concurrency_load_date

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/194/

Can one of the admins verify this patch?

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1274/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/643/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2224/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2484/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3467/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2227/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3335/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3103/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4337/


add install steps of macos

fixed by https://github.com/iresty/apisix/commit/374aba472bce4fc08dd11d2da532463d28f4bb31


Support auto pagination

This is just a proof of concept. Feel free to reject or modify.
Set autoPaginate={true} on the GiftedListView to enable auto pagination. onEndReachedThreshold could be used to tune the trigger of auto pagination.

I found on iOS unexpected onEndReached may be triggered, especially at first onFetch. Works well on Android.
Another approach may be using onChangeVisibleRows. That would require a user provided function like
isLastRow(rowData)

to see if last row becomes visible on screen. Just a thought, I haven't tested it yet.

How to run it for ios ,when I run it in xcode, the xcode tell me "RCtRootView.h" file not found.

what as the issue with onEndReached being triggered accidentally? I'm about to use it. I can fix it if necessary.

@faceyspacey I just found it unstable on iOS but did not dig into it. You can test it yourself with latest react native release.

automatic infinite scroll as provided here really would make this package one of the best list view packages. it's the one missing feature that everyone has on their checklist when they go looking around for which of these list views to use.

any word on when this will be merged?

Hello, I didn't merge it because @realaboo said it was a just proof of concept and it was unstable on iOS. I don't have time to improve it but if someone can submit a pull request it will be merged.

code is in for fixing multiple fires of onEndReached (and therefore fetching) on iOS:
https://github.com/FaridSafi/react-native-gifted-listview/pull/37

another thing: I think the prop should be called 'infiniteScrollingrather thanautoPaginate` as that's what people scan the readme looking for to see if it supports it. But I'll leave it up to @FaridSafi .

for anyone following this pull request, i did a lot more:
https://github.com/FaridSafi/react-native-gifted-listview/pull/38
...basically, there were a lot more issues than just the initial load triggering onEndReached. I killed every single one I can find and can easily solve anymore via the things I have setup (panResponder callbacks + datetime flags) to catch "false positive" onEndReach firings. This is on its way to actually being usable, and perhaps more usable than a lot of other React Native infinite scroll components doing this stuff. Basically the onEndReached callback React Native (and perhaps plain iOS) provides is no good, and any package relying simply on that offers an unusable form of infinite scrolling. Not in React Native at least where re-renderings of any sort simply trigger it again (pagination view hiding/showing, manual calls to refresh--when you're near the bottom, any re-rendering is dangerous). So I built a lot to address the various scenarios that arise.

@faceyspacey Thanks!
I'm closing this PR. All discussion will be continued in #38.


feature: partial caching of chromatic Fourier design matrix

This PR adds the ability to cache portions of the construction of the chromatic Fourier design matrix.
Initially testing on NG15yr data shows a 10x speed up to the recalculation of the chromatic Fmat construction.
This constitutes anywhere between a 3% to 15% speed up of the overall likelihood calculation for single pulsar noise when sampling in the chromatic index, alpha.
As the function docstrings say, the actual caching occurs via the @function decorator, which now wraps the later function, caching the initially passed arguments which include the achromatic portion of the Fourier design matrix and the division of TOA observational frequencies by a reference frequency.
This will be implemented in the chromatic_noise_block() of enterprise_extensions for automatic caching when sampling in the chromatic index.

@jeremy-baier linting failed. Can you run the linter? I think enterprise may be on a slightly older version of flake8/black. So just check to see what version it is using..

@AaronDJohnson looks like everything is passing now except one part of the code cov. Does that just mean I have to make a test for the 2 added functions?

@jeremy-baier codecov measures the number of lines covered by tests. So more tests will increase codecov % as long as those lines that you're covering are not already tested.

@AaronDJohnson I added a test which covers both of the added functions. This seemed to satisfy the codecov bot.
I think this PR is ready for merge now!

marking this as a draft for a second because I need to check one part of the compatibility with enterprise_extensions

@jeremy-baier , I marked it as a draft by just using the feature. Or did you by now verified this is compatible?


Release 3.1.0 requires full resync?

Upgrade from 3.0.0 to 3.1.0 causes errors like:
[db-sync-node:Error:48] [2020-07-28 19:12:19.96 UTC] ChainSyncWithBlocksPtcl: SqlError {sqlState = "42703", sqlExecStatus = FatalError, sqlErrorMsg = "column block.epoch_slot_no does not exist", sqlErrorDetail = "", sqlErrorHint = ""}
[db-sync-node.Subscription:Error:44] [2020-07-28 19:12:19.96 UTC] [String "Application Exception: LocalAddress {getFilePath = \"/node-ipc/node.socket\"} SqlError {sqlState = \"42703\", sqlExecStatus = FatalError, sqlErrorMsg = \"column block.epoch_slot_no does not exist\", sqlErrorDetail = \"\", sqlErrorHint = \"\"}",String "SubscriptionTrace"]

If this minor version upgrade requires resync from 0: please update release notes, or provide migration/etc scripts

This is still under heavy development and a resync will be required. Yes it should be mentioned in the changlelog.


Upgrading System.IdentityModel.Tokens.Jwt to version higher than 6.10.0 the signalling stops working

Describe the bug
We are using hosted SignalR on Azure. We recently encountered an issue which I double verified today that when we upgrade the dependency SignalR has - System.IdentityModel.Tokens.Jwt to version higher than 6.10.0 (so even 6.10.1) it breaks the signalling and no signals are arriving.
Today I tried upgrading  System.IdentityModel.Tokens.Jwt to version 6.11.1 and the issue still persists. As soon as we revert back to 6.10.0 the singaling starts working again.
To Reproduce
Send a signal using Microsoft.Azure.SignalR 1.9.1 with System.IdentityModel.Tokens.Jwt higher than 6.10.0
Observe that no Signals are being received
Exceptions (if any)
Unfortunately I can't see any exceptions anywhere.
Further technical details
using Microsoft.Azure.SignalR 1.9.1 (but also happens with 1.8.1)
ASP.NET Core 3.1

Could you provide a mini-repro project? I tried a simple project referencing both packages but failed to repro the issue.
Or could you share with me the exception you see? Follow these steps to get the exception: https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-howto-troubleshoot-guide#troubleshooting-guide

@vicancy Hello, sorry for getting back to you a bit late on this. Today I ran again to the issue when someone updated System.IdentityModel.Tokens.Jwt > 6.10.0 which broke the signalling again. I went through some of the steps but so far I have been unlucky getting the exception (however the problem still persists for us). I will try to enable server side logging for SignalR and see if that catches anything.


suggestion to don't clone self in get_block

Motivation
In https://github.com/ZcashFoundation/zebra/pull/9006 we are cloning self in the get_block implementation which could bring some problems in some tests.
Solution
This is an alternative to do that that @conradoplg might find useful, feel free to discard.

@conradoplg There's very little in RpcImpl being cloned but this looks like a good cleanup if you'd like to merge it into your PR.

Thanks! I'm not sure if this will solve the issues I'm getting implementing #9024 but I'll give it a shot there, inspired on this approoach.


[Bug] Missing discarded/trigger textures when switching scene in editor

This video should explain the issue. I've noticed this happen on the 'discarded surface' and 'trigger' textures. Also to note they reload fine after I double click the scene to make it the main/active one.
https://www.youtube.com/watch?v=c9DCn_51oi0

Hmm, OK it shouldn't be showing the discarded surfaces and triggers for non-active scenes ..
At least that was the intention ..
Do you need to see the triggers / discarded surfaces for non-active scenes?

I would prefer to have it show those surfaces for non-active scenes (unless otherwise set to hidden)

That might be complicated to do since right now only the surfaces for the current scene are being processed .. but I'll see if I can find a way to do this

This is fixed in version 1.332!
As usual this is available on the update site https://prenominal.nl/updates/
I'll close this ticket once this version is available from the asset store!


Editorial rights

Thinking about development two possibilities might help:
implement actual authorization system (that an authorizer authorizes
edits and only then they become public, similar to travel requests in
SAP system of the university, for example)
implement a mechanism to propose a locality and upload a pdf. That
would be useful in general I think, I started collecting such localities
in a folder when I come across recent publications publishing species
lists for localities. I have very few, but I remember Christine said she
has been collecting such publications for NOW as well.


django.db.utils.OperationalError: FATAL:  database "saleordb" does not exist

I have tried to clone and build saleor many times but everytime I run
docker-compose run --rm api python3 manage.py migrate. I get this error.I don't know what's the issue.I have tried all solution and even tried to run saleor using docker on windows as well as on mac but still got same issue while running migrations

I have tried to clone and build saleor many times but everytime I run
docker-compose run --rm api python3 manage.py migrate. I get this error.I don't know what's the issue.I have tried all solution and even tried to run saleor using docker on windows as well as on mac but still got same issue while running migrations

Could not reproduce the issue. Please reopen if it's still occurring with the current version of the platform.


Chart Option -> DropShadow Color options

Hi,
Your charts are excellent and I am glad to use them in my project. Great Flexibility.
However with that dropshadow option provided in chart options, it will be great and will look beautiful if you add support for dropshadow's color property.
like here

Thanks for the suggestion.
Implemented it. Will be available in 3.2.2

hi, is this feature available yet? I'm not seeing it in Docs

ahhh just tested it and it works :)
    dropShadow: {
      enabled: true,
      top: 0,
      left: 0,
      blur: 3,
      opacity: 0.5,
      color: 'yellow'
    }


spec: fix fmt issues and example JSON

Why remove the headers?

@eyakubovich ?

@jonboulle b/c we insert comments there that violate JSON format and cause display issues.

LGTM


Build failure with React-dom and rollup-plugin-polyfill-node

Describe the bug
I ran into an issue when trying to use the
rollup-plugin-polyfill-node with Vite in combination React-dom
A simple example is here:
https://github.com/kohlerm/polyFillIssue
I get the error
'Component' is not exported by node_modules/react/index.js, imported by node_modules/mini-create-react-context/dist/esm/index.js
file: /home/kohlerm/polyFillIssue/node_modules/mini-create-react-context/dist/esm/index.js:1:16
1: import React, { Component } from 'react';
                   ^
2: import _inheritsLoose from '@babel/runtime/helpers/esm/inheritsLoose';
3: import PropTypes from 'prop-types';
error during build:
Error: 'Component' is not exported by node_modules/react/index.js, imported by node_modules/mini-create-react-context/dist/esm/index.js
    at error (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:164:30)
    at Module.error (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:10008:16)
    at Module.traceVariable (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:10392:29)
    at ModuleScope.findVariable (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:9164:39)
    at FunctionScope.findVariable (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:3645:38)
    at ChildScope.findVariable (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:3645:38)
    at Identifier.bind (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:4582:40)
    at CallExpression.bind (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:2893:31)
    at CallExpression.bind (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:7101:15)
    at VariableDeclarator.bind (/home/kohlerm/polyFillIssue/node_modules/rollup/dist/shared/rollup.js:2897:23)
error Command failed with exit code 1.

Any hint how I could get around this issue?
Reproduction
check
https://github.com/kohlerm/polyFillIssue
Run yarn build
System Info
npx: installed 1 in 0.869s

  System:
    OS: Linux 5.4 Kali GNU/Linux Rolling 2020.3
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 16.72 GB / 24.83 GB
    Container: Yes
    Shell: 5.0.18 - /bin/bash
  Binaries:
    Node: 14.17.0 - ~/.nix-profile/bin/node
    Yarn: 1.22.10 - ~/.nix-profile/bin/yarn
    npm: 6.14.13 - ~/.nix-profile/bin/npm
  Browsers:
    Chrome: 85.0.4183.102
    Firefox: 68.11.0esr
  npmPackages:
    vite: ^2.4.0 => 2.4.1

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Watching this issue since i have the same problem
vite.config:
import * as react from 'react';
import * as reactDom from 'react-dom';
import { defineConfig } from 'vite';
import reactRefresh from '@vitejs/plugin-react-refresh';
import reactSvgPlugin from 'vite-plugin-react-svg';
import commonjs from 'rollup-plugin-commonjs';
import polyfillNode from 'rollup-plugin-polyfill-node';

export default defineConfig({
  plugins: [
    reactRefresh(),
    reactSvgPlugin(),
    polyfillNode(),
    commonjs({
      include: '/node_modules/',
      namedExports: {
        'react': Object.keys(react),
        'react-dom': Object.keys(reactDom),
        // 'react-is': Object.keys(reactIs),
        // 'prop-types': Object.keys(propTypes),
      },
    }),
  ],
});

Error: 'useMemo' is not exported by node_modules/react/index.js, imported by node_modules/react-use/esm/factory/createMemo.js

Having exat same issue, chunked bundle and it is located in react.production.min.js, anyone found something new? Checked https://github.com/vitejs/vite/issues/5237 but didn't found something usefull. Thanks and have a good day!

This was not a vite issue.
First the plugin order is userPlugins without enforce -> definePlugin -> commonjsPlugin -> userPlugins with enforce=post.
rollup-plugin-polyfill-node polyfills process so process.env.NODE_ENV becomes not a constant. (I did not check what happens but it uses @rollup/plugin-inject internally)
Then react/index.js becomes not able to be statically analyzed. (since module.exports is not top-level)
'use strict';

if (process.env.NODE_ENV === 'production') {
  module.exports = require('./cjs/react.production.min.js');
} else {
  module.exports = require('./cjs/react.development.js');
}

The reason above is including a guess. But I feel it is mostly correct.
If you use enforce: 'post', it works.
export default defineConfig({
  plugins: [reactRefresh(), { ...nodePolyfills(/* options */), enforce: 'post' }]
})


Update ADU device props to GA fields

Verified with @ewertons that the only other change is the manifest version going from 4 to 5. Updated it in the unit tests.


Search tables and new Quiz graphic

Added text tables to OLOCI page and new quiz header graphic to all relevant pages.

Moved OLAM 2.0 section to top of OLAM page


SerializesModels behavior on non-persisted Eloquent Models

When passing a model into a Job with the SerializesModels trait, the serializer checks if the value is an instance of QueueableEntity and transforms it into a ModelIdentifier.
That works fine for persisted models but if you pass a non-persisted model, all the values are lost because the object is transformed into a ModelIdentifier with a null id.
What do you think about checking if the entity is saved and do a regular serialization on non-saved instances?
Something like this
    protected function getSerializedPropertyValue($value)
    {
        if ($value instanceof QueueableEntity && !empty($value->getQueueableId())) {
            return new ModelIdentifier(get_class($value), $value->getQueueableId());
        }

        return $value;
    }

This avoids pass all the properties for a model (even related persisted model instances) to the job.

I'm seeing issues when the unsaved model references other models; wouldn't that in turn cause issues with serialized pdo objects? How about throwing an exception to highlight the issue to the developer, so it can be saved?

Hey @grunjol @sisve,
looks like you have a suggestion for a better handling of the matter, can you please open a PR? It's always better to discuss implementations.
I'm closing this issue since it's not really a bug, but please feel free to continue discussions if you want.
For suggestions and feature requests please use the https://github.com/laravel/internals repo.

This could be a possible bug if you consider dropping a pivot-model into the queue-job. Since the ModelIdentifier uses firstOrFail() and the PK of a pivot usually consist of 2 columns.

Guys
How about to check Model for exists?
Current code tries to query Model if it have the ID. But someone may use pre-defined IDs like a UUID and then Job with SerializeModels trait crashes.


Model Silhouette is wrong when silhouette alpha is not 1

What happened?
Reported on the forum: https://community.cesium.com/t/behavior-of-entity-model-silhouette-color-options-with-alpha/37082
It seems this may have started happening in version 1.121
https://github.com/user-attachments/assets/d2df426e-ec4e-4637-98e3-4e0ef25d2a9c
It looks like something about the model is not getting translated correctly when it's rotated while processing the silhouette color. Could this be related to https://github.com/CesiumGS/cesium/issues/11067?
Reproduction steps

Load the 3D Models Coloring sandcastle
Set the model color to white to avoid confusing the colors
Change the Silhouette alpha to anything lower than 1

Sandcastle example
No response
Environment
Browser: Chrome
CesiumJS Version: 1.124
Operating System: Linux

Given the post processing depth buffer ties, perhaps https://github.com/CesiumGS/cesium/issues/7705 is related?


Issue viewing team

https://courageleague.azurewebsites.net/division/6e616fa0-4c61-474e-8a17-2bef77c82a40/team:0f44c497-c70e-44ed-a636-741f57c296ab/199fdb13-2090-48a1-9cd1-df5e52b1ae4f

Resolved by clearing the server cache for the react components


python310Packages.pyairvisual: 2022.11.1 -> 2022.12.0

Changelog: https://github.com/bachya/pyairvisual/releases/tag/2022.12.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant-component-tests.airvisual
python310Packages.pyairvisual
python39Packages.pyairvisual


docs: initial version of COMPONENT-OWNERS.md file

Closes #3

I am seeking help from maintainers to review all the components I have added, and the people I have tentatively put in the list (based on my understanding). Please make sure you add people you think should be there.


Split task dependent on ansible_pkg_mgr fact

This role has a hidden dependency on epel role,
because the default packages installed may be from external repository epel.
When a node previously configured with epel repo disabled is accepted in a new ansible environment,
the(your) epel role is not activating epel again.
Hence the following task using the generic package module will fail in EL7 cases.
https://github.com/robertdebock/ansible-role-python_pip/blob/496c0ffb1df8cf2f9cfe0590757e9054a6a49b83/tasks/main.yml#L9-L12
- name: install python pip
  when: ansible_pkg_mgr == 'apt'
  ansible.builtin.package:
    name: "{{ python_pip_packages }}"
    state: present
- name: Yum | install python pip
  when: ansible_pkg_mgr == 'yum'
  ansible.builtin.yum:
    name: "{{ python_pip_packages }}"
    enablerepo:
      - epel
    state: present
- name: Dnf | install python pip
  when: ansible_pkg_mgr == 'dnf'
  ansible.builtin.dnf:
    name: "{{ python_pip_packages }}"
    state: present

I don't fully understand your remark, but I guess it's good to keep this issue for others to read.
Thanks!


Dropping edges refactoring

Pull Request Description
WIP
Important Notes

Checklist
Please include the following checklist in your PR:

[ ] The documentation has been updated if necessary.
[ ] All code conforms to the Scala, Java, and Rust style guides.
[ ] All documentation and configuration conforms to the markdown and YAML style guides.
[ ] All code has been tested where possible.

The PR is postponed, as there are significant difficulties when implementing it. Leaving it open for a while so @farmaazon will be able to easily pick the necessary code when he would be working on his attempt of this refactoring.


Unable to resolve module lodash.isstring from /[...]/node_modules/react-native-vector-icons/lib/icon-button.js: Module lodash.isstring does not exist in the Haste module map

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed issues): https://github.com/oblador/react-native-vector-icons/issues

macOS Big Sur Version 11.0.1 (And catalina before this)
Target platform is iPhone 11 iOS 14.2 (Though error appears on every other one I've tried)
"react-native-vector-icons": "^7.1.0",
And also "react-native-vector-icons": "oblador/react-native-vector-icons", which is what the current app I am meant to be working on is using, but I changed it to use the specified version because I thought that might be the cause. Same problem with both.
RN version 0.60.0 for the existing app I initially tried to get working, and
"react-native": "~0.63.3", for the dummy project I created to test the library alone

Description
I originally cloned the git repo for a working app that I am meant to be working on, did npm i && npx pod-install ios and encountered the error below. Then I created a fresh standalone project, made sure it worked without the library then added plus npm/pod install.
When trying to run react-native run-ios or running it from XCode I get this error:
Unable to resolve module lodash.isstring from /[...]/node_modules/react-native-vector-icons/lib/icon-button.js: Module lodash.isstring does not exist in the Haste module map
I've tried installing lodash globally, to no effect, and changing the package.json entry as noted earlier. I'm new to RN so I'm not really sure where to go from here. Any help would be appreciated, thanks.

I have the same issue with RN 0.63.2 and react-native-vector-icons: 7.1.0. Can you share how to fix the problem?

@newalias34 any update?

@newalias34 any update?

@newalias34 any update?

Sorry I didn't see this earlier. Unfortunately I had to go in a different direction as I could not get past this issue.

@newalias34 any update?

Sorry I didn't see this earlier. Unfortunately I had to go in a different direction as I could not get past this issue.

I got the same error

Just got the same error.
react-native version is 0.60.5
react-native-vector-icons version is 8.1.0.
Looking into  node_modules/react-native-vector-icons/yarn.lock and node_modules/react-native-vector-icons/node_modules/lib/icon-button.js I can see that lodash.isstring is being referenced but cannot find the lodash module. It'd be nice if this issue were reopened.

same error coming.

I have the same issue. I fixed it by the following --

Re-Install the module by  :   npm install lodash --save
And run expo by :   expo start --clear

Thanks.


Added check for Available DiskSpace during App Instance Activate.

Added check for Available DiskSpace during App Instance Activate.
the total diskspace used by all apps at any point of time must be less
than a threshold ( default 80% of /persist ). The rest of the
20% is reserved for Dom0. When calculating this diskspace:

readonly drives are not included in the calculation.
Only Apps with all images downloaded and verified are taken into
account
Containers are not included in this calculation.

Other cleanup done:

Added two methods for AppInstanceStatus - SetError and ClearError.
Moved some routines into diskmetrics from domainmgr.

Sorry I missed your update, because the build still fails; this time with yetus complaints.
pkg/pillar/types/zedmanagertypes.go:190:1: receiver name statusPtr should be consistent with previous receiver name status for AppInstanceStatus
pkg/pillar/types/zedmanagertypes.go:198:1: receiver name statusPtr should be consistent with previous receiver name status for AppInstanceStatus
pkg/pillar/types/zedmanagertypes.go:205:1: receiver name statusPtr should be consistent with previous receiver name status for AppInstanceStatus


reCaptcha options set using apos-override-options are found server side

https://github.com/apostrophecms/apostrophe-forms/blob/e7e9a3d95dd96d11b6e6414b3ca90c0b95480bd1/index.js#L126-L130
We're setting this up for easy overriding project-level to set reCAPTCHA options in global settings. The getOptions override is working nicely in the form widget template file, but is not in the apos-form/index.js file.

This branch is configured to work as a test site. https://github.com/apostrophecms/apostrophe-boilerplate/tree/forms-recaptcha-test

I pushed you a commit for this, closing.


docs: improved JS example (with node-fetch)

Improvements for the JS example, as discussed in #104

@jameslinjl @derhuerst I just added a note about node-fetch installation with NPM and ESM vs CJS. Can you give me your opinion on this please?

@gauthier-th lgtm!

@gauthier-th @derhuerst any other thoughts on this guy?

@isabelle-dr we should be good-to-go for merging this documentation / example change!


fixed url_launcher link in url_launcher_web README

Description
fixed url_launcher link in url_launcher_web README. It was being sent to 404 not found
Related Issues
Fixes https://github.com/flutter/flutter/issues/57819
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@ditman I committed the changes you suggested.

@ditman I committed the changes you suggested.

@ditman
https://github.com/flutter/plugins/pull/2793
this can be closed i guess

@ditman
https://github.com/flutter/plugins/pull/2793 this can also be closed

Merged and published 0.1.2+1


Unable to create entities with dependencies

Right now it's not possibile to create entities with dependencies. It's possibile to use the Instantatior but it's not aware of data on creation, so it's not possible if you have something like this:
class User
{
    public function __constructor(string $name)
    {
        $this->name = $name;
    }
}

Of course we could instantiate the entity with an empty string, but it's not the right way and things will be more complicated when a dependecy is needed (imagine a Role).
Should be useful another event that will allow to create entity based on POST data.

Originally posted by @thomasvargiu at https://github.com/zfcampus/zf-apigility-doctrine/issues/313

You're wrong.  https://github.com/zfcampus/zf-apigility-doctrine/blob/master/src/Server/Resource/DoctrineResourceFactory.php#L102
You can create your own type of instantiator called an Entity Factory to create your entities.  If you create a proper Entity Factory it will have access to the request or whatever else you inject it with.

Originally posted by @TomHAnderson at https://github.com/zfcampus/zf-apigility-doctrine/issues/313#issuecomment-399536599

Ok. Thank you. The only thing is that I have no access to filtered data or I should call it two times.

Originally posted by @thomasvargiu at https://github.com/zfcampus/zf-apigility-doctrine/issues/313#issuecomment-399539352

It will be up to you to configure your Entity Factory.  If you need to fetch filtered data you'll probably have to fetch it explicitly in your factory rather than waiting for it to roll around to the resource method.

Originally posted by @TomHAnderson at https://github.com/zfcampus/zf-apigility-doctrine/issues/313#issuecomment-399545026


Enhancement: Clarify need to switch to undeground mode

This is mainly for lane connector tool, but probably other tools too...

See also: #1330
Just showing a 🚫 cursor isn't enough to explain to user that they need to be in underground mode to customise that node/segment etc. From user perspective it's "There's a node here but you're not allowed to change it" - and it doesn't explain why?
For node-specific tools, it might be better not to show the node circle and, instead, show a down arrow - similar to what's planned for speed limits tool:

The down arrow could become the consistent way across all tools to indicate something underground.
In this case, the 🚫 cursor would no longer be required because we wouldn't be showing a tempting node to user any more; we'd be showing an indicator that something lurks underground. We could potentially show mouse tooltip when they hover down arrow with text explaining what it is (maybe only if tutorials are enabled?) etc.

ok.  so how does one "go underground"?

just like in vanilla, with PageDown key, it's configurable since v<IP_ADDRESS>

just like in vanilla, with PageDown key, it's configurable since v<IP_ADDRESS>

no, no - for lane connecting  :p

Ok, so you didn't try.