test design

Codecov Report
Base: 100.00% // Head: 82.85% // Decreases project coverage by -17.14% :warning:

Coverage data is based on head (b7a098b) compared to base (0fb38a6).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head b7a098b differs from pull request most recent head 2789f02. Consider uploading reports for the commit 2789f02 to get more accurate results

Additional details and impacted files
@@              Coverage Diff               @@
##              master      #54       +/-   ##
==============================================
- Coverage     100.00%   82.85%   -17.15%
  Complexity        12       12
==============================================
  Files              7        8        +1
  Lines             29       35        +6
==============================================
  Hits              29       29
- Misses             0        6        +6

Impacted Files
Coverage Δ

...ain/java/com/l3r8yj/elegramapi/bot/UpdatedBot.java
0.00% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@rultor merge

@rultor merge

@l3r8yj OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@l3r8yj Done! FYI, the full log is here (took me 1min)


Chore: remove supplementary tags

Proposed changes
As mentioned in #196 some of the tags have been depreciated and it was decided to remove all of the supplementary tags.
Closes #196.
Types of changes
I suppose its breaking if people started using them...

[ ] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] Chore (change that does not fix an issue or add functionality, but
improves TwitchJS in some other way)

Checklist

[x] I have read the
CONTRIBUTING.md
doc
[x] My PR is named according to
CONTRIBUTING.md
doc
[x] End-to-end tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

All of them, including broadcasterLanguage and slowDelay?

In a future PR, we can parse roomState.tags and .badges just like we do for message params (i.e. turn strings into numbers or booleans); for now, I would just leave the ...tags.

Codecov is misbehaving.
Do you mind if I merge your PR? The commit will be co-authored by you and me.

Actually, let me try to increase the coverage in #197 and then hopefully when you bring your branch up-to-date, you will be able to merge.

@dbkynd Please merge your PR ❤


Can't run demo "Jaccard Similarity between Dependency Trees"

The cell where the minhashes are created throws an ValueError

The error seems to occur for sentences with contractions of article and preposition (e.g. 'im', 'zur'). The conll-data has extra rows for the contracted form and the underlying isolated forms, thus the index of a token becomes for example (13, '-', 14) (see traceback).
Maybe you can just skip the row with the contracted form?

I see
...
((13, '-', 14), None, '_', 'im'),
 (13, 16, 'case', 'in'),
 (14, 16, 'det', 'dem'),
...

(13, '-', 14) is actually 13-14
and additional information that we don't need at this stage.
https://universaldependencies.org/format.html#words-tokens-and-empty-nodes


infer not returning expected inner type if another inner type is used in the outer type result

Bug Report
Given a generic outer type with 2 or more inner types, e.g. Foo<A, B>, that does an intersection involving multiple inner types, then infer won't return a specific inner type, it will return the intersection of the desired type plus the entire outer type. This is difficult for me to explain since I don't know the correct terms for everything, so please see the example.
🔎 Search Terms
infer intersection
🕗 Version & Regression Information

This changed between versions 4.1.5 and 4.2.3

⏯ Playground Link
playground link
💻 Code
type Foo<T extends {}, N extends string> = T & {
  bar: number;
  asdf: N;
};

interface A {
  things: number;
}

type MyFoo = Foo<A, 'asdf'>;

type InnerFromFoo<F> = F extends Foo<infer I, string> ? I : never;

type inner = InnerFromFoo<MyFoo>;

const a: inner = {
  things: 23
};

🙁 Actual behavior
The type inner is the intersection of A and { bar: number, asdf: string }
🙂 Expected behavior
inner should just be A

It can't match through the type arguments since the MyFoo is an alias. Then it tries to match through the intersection-specific branch through inferFromMatchingTypes but the types are not quite matching so it doesn't infer anything interesting - this is because inferFromMatchingTypes is using isTypeIdenticalTo here.
So it grabs getIntersectionType of both target and the source and we end up here with simplified forms of:
source // A & { bar: number; asdf: "asdf"; }
target // I & { bar: number; asdf: string; }

Here, we can also see how the types are not quite "identical".
And to complete the story... we end up calling inferToMultipleTypes and in it we get to the iteration that sees that:
source // A & { bar: number; asdf: "asdf"; }
target // I

That can easily be matched and thus A & { bar: number; asdf: "asdf"; } becomes the inference candidate.

This result isn't wrong, because it's consistent with what you would get if you wrote the structural expansion of MyFoo, and typescript has a structural type system:
type inner = InnerFromFoo<{ things: number, bar: number, asdf: "asdf" }>;

but the intersection cleaving logic could possibly be improved since the intuitive result here is a bit more obvious I think.

@RyanCavanaugh Is there a reason it changed between TS 4.1 and 4.2 though?


Death saving throws not functioning

When using this sheet the Death saving throw button does nothing, it doesn't throw an error either.
To make sure I did not have a conflicting module I Created a test world with only this module enabled.
I have run into the same issue with other custom sheets.

Thanks for the report! I'll take a look at this asap.

Fixed in 0.9.4


Bug/zero beginning balance value

Migration posting fails because of 0.00 balance brought forward value. If the beginning balance value is equal to zero, do not create a transaction.

Availability update: We will publish a fix for this issue in the next update for release 21.
Build ID to track: 49930.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 49917.


feat: add option to exclude some namespaces from cache

What

This PR adds a new option to allow you to exclude some namespaces from the cache

Ticket

Not applicable
Analytics

Analytics was not relevant for this PR
Demo

@BothrsCI Can you take a look on it, please?

Released in v2.1.0 🎉


ASP.NET Core 1.1 - Look for an app in the store ???

I want to run an ASP.NET Core MVC Project, but I get the following:

Startup.cs
app.UseMvc(routes =>
          {
              routes.MapRoute(
                  name: "default",
                  template: "{controller=Home}/{action=Index}/{id?}");
          });

Controller:
 public IActionResult Testing()
        {
            return View("Testing", new DummyObject() { Age = 23, Name = "Ben" });
        }

And why is it hitting the index action and not the testing action ????
Upgrading doesn't work too...

Woooow ASP.NET Core, I am impressed...
Task Manager is your friend .....
Close, reopen, Upgrade packages ---> Task Manager is my friend again....
I wouldn't be annoyed if VS2017 would be freeware....

@Legends sorry you're running into this. Can you upload your app to a GitHub repo so that we can take a look?

The filter might be affecting the returned MIME type, then windows takes over and prompts for an app in which to open it.

I've deleted this project, sorry...  Changed to a fresh Core 2.0 project... now it's much better..


Race condition when settings are applied

{"time":"2017-06-21T10:02:13.889Z","sourceLocation":{"moduleName":null,"line":null,"functionName":null,"file":null},"severity":"ERROR","metadata":{"error_logger":"format"},"logMessage":"#PID<0.31977.8> running Annon.ManagementAPI.Router terminated\nServer: <IP_ADDRESS>:8080 (http)\nRequest: PUT /apis/ca9e5956-1cb3-47a1-94ba-d5c489301edb/plugins/cors\n** (exit) an exception was raised:\n    ** (Ecto.ConstraintError) constraint error when attempting to insert struct:\n\n    * unique: plugins_pkey\n\nIf you would like to convert this constraint into an error, please\ncall unique_constraint/3 in your changeset and define the proper\nconstraint name. The changeset defined the following constraints:\n\n    * unique: plugins_api_id_name_index\n    * foreign_key: plugins_api_id_fkey\n\n        (ecto) lib/ecto/repo/schema.ex:493: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3\n        (elixir) lib/enum.ex:1229: Enum.\"-map/2-lists^map/1-0-\"/2\n        (ecto) lib/ecto/repo/schema.ex:479: Ecto.Repo.Schema.constraints_to_errors/3\n        (ecto) lib/ecto/repo/schema.ex:213: anonymous fn/13 in Ecto.Repo.Schema.do_insert/4\n        (ecto) lib/ecto/repo/schema.ex:684: anonymous fn/3 in Ecto.Repo.Schema.wrap_in_transaction/6\n        (ecto) lib/ecto/adapters/sql.ex:620: anonymous fn/3 in Ecto.Adapters.SQL.do_transaction/3\n        (db_connection) lib/db_connection.ex:1275: DBConnection.transaction_run/4\n        (db_connection) lib/db_connection.ex:1199: DBConnection.run_begin/3"}

Reproduces with UUID's:
{"timestamp":"2017-07-19T14:43:30.102Z","sourceLocation":{"line":null,"function":null,"file":null},"severity":"ERROR","metadata":{"error_logger":"format"},"jsonPayload":{"serviceContext":{"version":null,"service":null},"message":"#PID<0.3268.0> running Annon.ManagementAPI.Router terminated\nServer: <IP_ADDRESS>:8080 (http)\nRequest: PUT /apis/35d6d358-d33a-423a-9e96-88a2b235d3f5\n** (exit) an exception was raised:\n    ** (Ecto.ConstraintError) constraint error when attempting to insert struct:\n\n    * unique: apis_pkey\n\nIf you would like to convert this constraint into an error, please\ncall unique_constraint/3 in your changeset and define the proper\nconstraint name. The changeset defined the following constraints:\n\n    * unique: api_unique_request_index\n    * unique: apis_name_index\n\n        (ecto) lib/ecto/repo/schema.ex:493: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3\n        (elixir) lib/enum.ex:1229: Enum.\"-map/2-lists^map/1-0-\"/2\n        (ecto) lib/ecto/repo/schema.ex:479: Ecto.Repo.Schema.constraints_to_errors/3\n        (ecto) lib/ecto/repo/schema.ex:213: anonymous fn/13 in Ecto.Repo.Schema.do_insert/4\n        (ecto) lib/ecto/repo/schema.ex:684: anonymous fn/3 in Ecto.Repo.Schema.wrap_in_transaction/6\n        (db_connection) lib/db_connection.ex:1366: DBConnection.transaction_nested/2\n        (db_connection) lib/db_connection.ex:1226: DBConnection.transaction_meter/3\n        (db_connection) lib/db_connection.ex:790: DBConnection.transaction/3"}}


Improve pruneIndexedPartitions by using futures

This PR updates code for sequential resolution of foldFilter by using futures and executing resolveSupported method in parallel for each file in Parquet partition; partitions are still resolved sequentially.
Manual testing shows about 1.5-2x performance improvement when filtering index partitions (with large portion of files being scanned). But it also introduces a little bit of overhead when filtering partitions on cached index (20ms vs 35ms). This approach is similar to eager loading.
Closes #56.

Coverage decreased (-0.004%) to 95.841% when pulling 619ca41115910b1bb8532acc7564eff6183591f6 on filter-resolution into c107705a05ea9f95be652e84b7feab382d3321a7 on master.


feat(k8s): add filter for k8s application type EE-1627

Closes EE-1627.
Changelog
This pr introduce filter for kubernetes application types:

Deployment
Daemonset
Statefulset
Pod
Helm

Closes https://github.com/portainer/portainer/issues/5726


Opt in to new gds api adapters behaviour

For: https://trello.com/c/B5z6Dq8q/495-get-our-apps-up-to-date-on-new-api-adapters-behaviour-update-at-stand-up
Also took the opportunity to add linting to the app and fix all extant errors.    As part of adding the linter I modernised the jenkins.sh script too, which probably means we'll want to update jenkins branch builder to call jenkins.sh, not jenkins_branches.sh (which is deleted).

Just rebased some changes in, I think I've resolved everything you picked up @jennyd.

Added a commit to shared global site checking behaviour between mappings controller and batches controllers.

Looks great, good job catching those bugs as well. At a later point, we should probably consolidate how the linter is run both on jenkins and in the rake command, but this looks to be happening in other apps too (LocalLinksManager, SpecialistPublisherRebuild). This looks good though, so will merge!


Minor issues with the text in the CI and CD with VSTS - Quickstart document

Minor mistakes with spelling, grammar and formatting.

Thanks, that's just been merged


[SPARK-20798] GenerateUnsafeProjection should check if a value is null before calling the getter

What changes were proposed in this pull request?
GenerateUnsafeProjection.writeStructToBuffer() did not honor the assumption that the caller must make sure that a value is not null before using the getter. This could lead to various errors. This change fixes that behavior.
Example of code generated before:
/* 059 */         final UTF8String fieldName = value.getUTF8String(0);
/* 060 */         if (value.isNullAt(0)) {
/* 061 */           rowWriter1.setNullAt(0);
/* 062 */         } else {
/* 063 */           rowWriter1.write(0, fieldName);
/* 064 */         }

Example of code generated now:
/* 060 */         boolean isNull1 = value.isNullAt(0);
/* 061 */         UTF8String value1 = isNull1 ? null : value.getUTF8String(0);
/* 062 */         if (isNull1) {
/* 063 */           rowWriter1.setNullAt(0);
/* 064 */         } else {
/* 065 */           rowWriter1.write(0, value1);
/* 066 */         }

How was this patch tested?
Adds GenerateUnsafeProjectionSuite.

@hvanhovell

LGTM - pending jenkins

ok to test

Test build #77042 has started for PR 18030 at commit 0e41a26.

Test build #77042 has finished for PR 18030 at commit 0e41a26.

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

Merged build finished. Test PASSed.

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

Test build #77090 has started for PR 18030 at commit eea789d.

Test build #77090 has finished for PR 18030 at commit eea789d.

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

Merged build finished. Test PASSed.

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

LGTM - merging to master. Thanks!


Unexpect inference result with flash_attn_triton

Hi, thanks for the great work! I met a problem with flash_attn_triton.py.
This is the result with flash_attn_cuda, as it show well.

However, when I replaced with flash_attn_triton, it seems the result went to strange as below.

this is how I use flash_attn_triton with hf transformers lib. Just enter the same parameters with flash_attn_cuda.

Is this right? does flash_attn_triton and flash_attn_cuda have the same parameters? Or the have the different shape of matrix?

Idk how those are called in HF, you can put a breakpoint or print out values to check of the outputs of the two implementations are close.

hi, I have try to print out the result. It seems not quit equal/close

Do you have any test about this in the project ? Maybe I can try the test firstly.

You want to compare the difference between the two, compared to e.g. difference between standard attention in fp32 vs standard attention in fp16. Otherwise it's hard to say if things are "close".
I think we used to have tests for the triton impl but idk where they went :D

Ok I see... Just find the output is little strange... I will try myself. Thanks for you reply.

Hi @jchuai is there any updates regarding this thread? I also face the same issue that the inference results is bad when enabling flash attention. Thanks

Hi, sorry for bringing up this issue,  but I've recently encountered a similar problem and was wondering if you were able to resolve the inconsistency


Gap between elements

Is there any way to change the gap between elements ? Ideally, I would like them to be right next to each other i.e need 0 gap.

Didnt see that sneak can be controlled.


Remove mach-related items

...as we recommend using mach2 instead.

I'm confused as to why structures related to the Mach-O file format are being removed. They're not part of the Mach kernel APIs. mach2 does not provide these types, AFAICT, and it claims to provide /usr/include/mach, not /usr/include/mach-o.
mach_header / mach_header_64 are part of the definition of the Mach-O file format. A random subset of other Mach-O structures still remain: segment_command, load_command, and related constants such as MH_MAGIC and LC_SEGMENT.


Added a small README pointing people to the Wiki

For folks who might be a bit lost after the Google Code project
has been shut down, and before Google picks up the new doccos

And with that, nuttiness from #477 is done! Thanks...


what does charsegment.cpp do ?

this file detects text characters using mser and extracts them onto a 28*28 box which is written onto a file pixelwise.

Hi raghavan,
Thanks!
Could one use this file alone for text recognition?
Sent from my iPhone
On 1 Nov 2016, at 16:54, Raghavan <notifications<EMAIL_ADDRESS>wrote:
this file detects text characters using mser and extracts them onto a 28*28 box which is written onto a file pixelwise.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/iitmcvg/OCR-Handwritten-Text/issues/2#issuecomment-257622148, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQIi04Yf1gx1Cud2s8f6N7n6kEMh0GMKks5q5262gaJpZM4KmDUh.

It is for extracting the letters from the text. Implementation would depend on your text size.


redundant coma between last argument and do

Imho, save data do  looks much more natural than save data, do
i understand it's just a caprice but permanently switching between Ruby and Imba makes me forget about that coma.
and when adding it my eyes ache :)

I agree. Imba has different precedence than Ruby when it comes to blocks. I've reasoned about it a few times, and have come to the conclusion that I like the Imba precedence better, but I cannot really remember why. Looks like we should go over it again.
By the way, how it works in imba:
# It will only happen with callable arguments
save data do yes # block is called on data
save "data" do yes # block is called on save
save "data", 100 do yes # still called on save

# I personally never use comma, but use parens around the non-block args:
save(data) do yes

I need to go over this again and try to remember why this was supposedly a better idea :) I did discuss this briefly with @judofyr, maybe he can remember the reasoning?

in most cases i use parens too but for people who prefer parens-less syntax it's a useless payload to recall to put coma if last arg is callable.

The reason I'm leaning towards the existing syntax (besides compatibility) is the fact that it allows for this type of pattern, which I find myself using from time to time:
load something.map do |item|
    item.path

If we had ruby-like precendence, the block must be wrapped:
load something.map(do |item|
    item.path
)

I find it a bit clunkier to need to wrap the block itself, than to sometimes need to wrap the preceding arguments (or use a single comma). It seems easier to control where the do block is with the current syntax, but it's what I am used to, so hard to say.

One "solution" would be to disallow ambiguous do blocks:
# ok:
load(something.map) do |item|
    item.path
# ok:
load(something.map do |item|
    item.path)
# ok:
load something.map(do |item|
    item.path)
# syntax error:
load something.map do |item|
    item.path

+1 on disallowing ambiguous do blocks


Support for ByteList (aka List(byte, N), as well as List[ByteList, N]

Currently the fastssz parser makes assumptions about ssz-size/ssz-max struct tags that do not allow us to support multi-dimensional lists. Also there are assumptions that byte lists do not need to be supported, resulting in incorrect generated code for List[byte, N] types, which do not mixin the list length. These issues prevent the prysm implementation of several Altair and Merge types from passing spectests:
Altair:

BeaconState.PreviouEpochParticipation
BeaconState.CurrentEpochParticipation
note: we use []byte for these types, unlike fastssz fixtures which use uint8, so the previous fixes in fastssz did not address our specific problem.

Merge:

ExecutionPayload.ExtraData
ExecutionPayload.Transactions

This PR attempts to solve both of these issues in one set of changes, and make the parsing code for dealing with lists more robust and easier to follow, also adding a tag parsing implementation with unit tests. Some changes were also made to parsing code that deals with computing fixed sizes. Rather than determining different sizes at parsing time, a fixedSize method was added to the Value type allowing the computation to be deferred to codgen time and determined recursively.
There is one change to codegen code which affects existing code. Rather than looping over collection types using a for loop with an array offset counter, the generated code now uses a for _, elem := range construction. This simplfies code generation because we can assume the name of the subelement is equal to the loop variable and don't need to keep track of nested list access. As a bonus this code should also be marginally more efficient, as benchmarks have show that go generates more efficient code using the range-element pattern than it does when using offset counters.

cc @ferranbt

Two things here:

Please run make build-spec-tests to see the changes in the encoding structs.
It might take me some time to review this because the changes are massive on the codebase and I am not sure how I feel about that.

I tested https://github.com/ferranbt/fastssz/pull/41/files last week for List(byte, N) and it was already working fine with much less code. Is there any reason for that big of a change?


Can construct value from nothing with case

Example:
(inductive Example ((a tau))
  (new ((x a)) (Example (Π () a))))

(let (ex (Example (Π () i64))) (Example.new i64 0))
(let (f (Π () i64)) (Example.case (Π () i64) (Π () i64) ex (Π-introduction ((f (Π () i64))) f)))

(f)

This results in a SIGSEGV on my machine, for obvious reasons. The issue seems to be the type of Example.case:
(Π ((internal.case-tau tau) (a tau) (_ (Example a)) (Example.new (Π ((x a)) internal.case-tau))) internal.case-tau)
The a used when creating ex and the a in the type of ex are confused it seems.

After thinking over this, you ought to separate parameters and indices like is done in other dependently typed languages. Then, the return type of the constructor should only allow you to specify indices. You could even just remove the I p_0 ... p_1 part from the return type, where I is the inductive type and p_i are the parameters.
The above code could e.g. become:
(inductive Example () ((_ tau))
  (new ((a tau) (x a)) ((Π () a))))

(let (ex (Example (Π () i64))) (Example.new i64 0))
(let (f (Π () i64)) (Example.case (Π () i64) (Π () i64) ex (λ (a x) x))) ; won't compile

(f)

The case eliminator ceases to be powerful enough though, since you can't unwrap the Example anymore.
Translating the above inductive type to Coq:
Inductive Example : Type -> Type :=
	example_new : forall (A : Type) (x : A), Example A.

Then we get the following eliminator:
Example_rect
     : forall P : forall T : Type, Example T -> Type,
       (forall (A : Type) (x : A), P A (exnew A x)) ->
       forall (T : Type) (e : Example T), P T e

This also allows one to define a function which unwraps the Example, which isn't possible with the primitive case, as evidenced here:
Definition extract (A : Type) (ex : Example A) : A :=
	Example_rect (fun T _ => T) (fun A x => x) A ex.

If you gave Example.case a type like the one for Example_rect, then you could define something like extract in neut too.
Fixing this would also allow you to define a HList in neut, which is currently impossible! I actually came across this bug because I was trying to implement a heterogeneous list in neut.

Hi, from the future. Thanks for your good catch. Also sorry for my (astronomically) delayed reply.
It has been about three years since this issue was opened, and now Neut doesn't have GADTs but only ADTs, at least for now. Because of that, I can't immediately apply your suggested fix, but I'll definitely reflect your point when I chose to re-add GADTs to the language.


[Snyk] Security upgrade postgres from 15.5 to 16.1

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

postgres/15/Dockerfile

We recommend upgrading to postgres:16.1, as this image has only 63 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

182
Out-of-Bounds SNYK-DEBIAN12-GLIBC-1547196
No Known Exploit

182
Out-of-Bounds SNYK-DEBIAN12-GLIBC-1547196
No Known Exploit

182
Out-of-Bounds SNYK-DEBIAN12-GLIBC-1547196
No Known Exploit

182
Out-of-Bounds SNYK-DEBIAN12-GLIBC-1547196
No Known Exploit

264
Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Thanks for the PR!
Any new images should be viewable with our repo packages.  :)

Since this is a container repository we won't be stepping up major versions.  Issue to block using renovate.json below.
https://github.com/bcgov/nr-containers/issues/67


Rollup: 'InfiniteScrollModule' is not exported by node_modules/angular2-infinite-scroll/angular2-infinite-scroll.js

Hello, i'am not sure is it issue of angular2-infinite-scroll (0.2.6) itself or rollup-plugin-commonjs(5.0.5). I just can't make Rollup after AOT compilation work. Code rollup.js:
plugins: [
    nodeResolve({jsnext: true, module: true}),
    commonjs({
        include: ['node_modules/rxjs/**','node_modules/angular2-infinite-scroll/src/**'],
        namedExports: {
            'node_modules/angular2-infinite-scroll/angular2-infinite-scroll.js': [ 'InfiniteScrollModule' ]
        }
    }),
    uglify()
]

And in my module:
import { InfiniteScrollModule } from 'angular2-infinite-scroll/angular2-infinite-scroll';

And in system.config.js:
map: {
//...
    'angular2-infinite-scroll': 'npm:angular2-infinite-scroll'
}

hi.
can you supply a sample repo for that?

Sure. https://github.com/EgorBurykin/angular2-infinite-scroll-problem

Any news here? Is there any way to make it work? Any help would be great)

hi.
I didn't identify the issue yet.

hi @EgorBurykin
please try beta version<EMAIL_ADDRESS>before I move this package to the next patch version.

fixed by 252ba10199f279366c00e69dfdddf36bd2e1adf1


Unify optional contexts into a single API call

Something like:
tracker.enableContexts(Contexts.MOBILE | Contexts.GEO | Contexts.SESSION);

Closing because it has been with no activity for a long time.
Please, feel free to reopen or comment this issue, whether it's of your interest or you want to contribute on this.


Fix MIUI (#4)

Fixes #4

[x] Tests pass
[x] Appropriate changes to README are included in PR

Works with code:
    public AppIconLoader(@Px int iconSize, boolean shrinkNonAdaptiveIcons,
                         @NonNull Context context) {
        try {
            Class<?> MiuiThemeHelper = context.getClassLoader().loadClass("android.app.MiuiThemeHelper");
            Field sMiuiOptimizationEnable = MiuiThemeHelper.getDeclaredField("sMiuiOptimizationEnable");
            sMiuiOptimizationEnable.setAccessible(true);
            sMiuiOptimizationEnable.set(null, false);
        } catch (Exception e) {
        }
        mIconSize = iconSize;
        mShrinkNonAdaptiveIcons = shrinkNonAdaptiveIcons;
        mContext = context;
    }

I see. Yes this may work, but I was expecting some flag under AdaptiveIconDrawable or similar. Upon second thought, turning off the entire MIUI optimization might have too much impact so I'd be careful with it, at least make it optional.
But before we go with turning off the entire optimization, I noticed that there is an AdaptiveIconDrawableInjector.drawMiuiStroke() method. Canvas drawing are typically done with a Paint object, and regular Android coding practice avoids allocating new objects on each draw call (to avoid GC pause), so I think there's some chance that there is a Paint field inside the AdaptiveIconDrawableInjector. Could you looked into the logic there and see what we can do, e.g. set the color of the Paint to transparent to make it a no-op? This would be a much safer approach for users of this library.

A simple way is override this method using reflection.

That sounds new to me. How would you "override" the static method AdaptiveIconDrawableInjector.drawMiuiStroke() with reflection? I thought one would need things like JVMTI or a hook framework to do that.

Oops, I don't know that. However, drawMiuiStroke update the Paint each time using setStyle, setColor and setStrokeWidth. Here I find an alternative to hide the shadow:
    public AppIconLoader(@Px int iconSize, boolean shrinkNonAdaptiveIcons,
                         @NonNull Context context) {
        try {
            Class<?> AdaptiveIconDrawableInjector = context.getClassLoader().loadClass("android.graphics.drawable.AdaptiveIconDrawableInjector");
            Field MASK_PAINT = AdaptiveIconDrawableInjector.getDeclaredField("MASK_PAINT");
            MASK_PAINT.setAccessible(true);
            Paint paint = (Paint)MASK_PAINT.get(null);
            paint.setXfermode(new PorterDuffXfermode(PorterDuff.Mode.DST));
        } catch (Exception e) {
        }
        mIconSize = iconSize;
        mShrinkNonAdaptiveIcons = shrinkNonAdaptiveIcons;
        mContext = context;
    }

Yeah, setting the transfer mode to to desitination sounds like a good fix for MIUI.
About the proposed code:

Could you use Class.forName() instead of context.getClassLoader().loadClass()?
Could you rename AdaptiveIconDrawableInjector to adaptiveIconDrawableInjectorClass, and MASK_PAINT to maskPaintField, to follow the naming convention of local variables?
Could you do it in a static initialization block, so that it is done only once?

Ok, please check the new commit.

LGTM. I would mvoe the code to a standalone class but I can do it myself.
Did you test again that this actually works? If so, I'll merge this and include it in the next release

Double checked. It works.

Merged, thanks for the contribution!

Released in v1.3.1 on Maven Central.


0.4.0-rc merge into main

Earth2Studio Pull Request
Description

Checklist

[ ] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

/blossom-ci

/blossom-ci

/blossom-ci


Hero section

https://www.figma.com/design/6yFZ706ebyXpjG4VULay2E/EarthFi?node-id=34-5&t=8jfO3KbS5NOKKsOJ-4

Desktop view done.
To be reopened for other screen designs


fix(router): improve useParams's type

This isn't something that can be made generic. The type of params is static.


Download file API causes Gateway memory to rise by fileSize

Expected Behavior
When we download a file, the gateway size should remain mostly unchanged
Actual Behavior
when a file is downloaded, even the same file multiple times, each time, the Gateway process' size increases by roughly the downloaded file's size.
Steps to Reproduce the Problem

Get the code from the repo mentioned below
Open using VS2022
Setup both the projects as startup.
Debug them (F5)
from postman or browser, try this URL to download the file:
https://localhost:7279/Download/smallfile
Observe in the Task manager that everytime you download the file, the Gateway process's memory increases by around 25MB, which is the size of the downloaded file.

repository
https://github.com/alahane-techtel/DownloadViaGateway

Dear @alahane-techtel !
What's your full name?
We are not going to open any your archive files.
Please upload code to your Github account instead of zipping!

@ggnaegi  Please confirm that our fix for downloads/uploads of large files is ready!
We could possibly link this issue to current open PRs, so closing the issue officially respecting our dev process.

Here's the repository:
https://github.com/alahane-techtel/DownloadViaGateway
Lemme know if this helps.

@alahane-techtel @raman-m We are currently testing a new approach, avoiding the http client full buffering. It might be the cause.

ok. lets hope that it will fix it. At least we got one test scenario in my repo to check if the new approach works on that :)
However, when you think the fix will be ready? just a rough estimate. like, couple of days? or weeks, or months? So that I can at least get some workaround ready. Because I need to fix the issue urgently.

@alahane-techtel we are on it, i'm working on the unit and acceptance tests at the minute. https://github.com/ThreeMammals/Ocelot/pull/1824
But you could try it. It seems to me it solves the issue, if you compare the memory usage between the two benchmarks.

Thank you, guys, for testing!
I believe #1824 will be merged to develop today, because I've added the PR to the current release.

@alahane-techtel commented on Jan 17:

Amazing!! I just checked. It works. No mem issue with this branch. Waiting eagerly for the release now :) Thanks a lot @ggnaegi

Release is here as Nov-December'23 milestone.
Watch for this milestone activities and progress plz...

Since the actual release may take few more weeks, is it possible to create a pre-release meanwhile? I'll really appreciate it.

@alahane-techtel commented on Jan 18
Since the actual release may take few more weeks

No, it will take 2-3 days to release completing the current release milestone.
Linked PR is merged and this ticket is closed as implemented.
So, if you want to test the version right away, then take develop branch code and compile a DLL by your own.
Note
We don't publish alpha, beta, pre-release versions. Because if feature is ready and delivered to develop branch then engineer can build a DLL from develop branch. There is no technical restrictions on such a "self-releasing".

thanks @raman-m. Will the release take more time? more than 10 days now :(

@alahane-techtel Our team was busy with testing in Production environment of our team member...
Getting and watching in Prod now...

@alahane-techtel commented on Jan 29

It was released on Feb 13 as version 23.0


XMPP error: unmarshal : expected element type  but have

Describe the bug
Matterbridge is unable to start XMPP bridge due to unmarshal error.
I'm getting this curious error that is seemingly impossible to google. Wondering if this an error in my config or an edge case bug since I haven't seen any reports.
To Reproduce
I'm not sure how to reproduce with out disclosing my actual config. Matterbridge was run in a conventional manor $ ./matterbridge-linux-amd64 -conf matterbridge.toml
Expected behavior
Normal operation of Matterbridge.
Screenshots/debug logs
cli debug flag passed
$ ./matterbridge-linux-amd64 -conf matterbridge.toml -debug
[0000]  INFO main:         Enabling debug
[0000]  INFO main:         Running version 1.11.3 0bd5a0d
[0000]  INFO gateway:      Parsing gateway gate
[0000]  INFO gateway:      Starting bridge: slack.work
[0000]  INFO slack:        Connecting using token (sending and receiving)
[0000]  INFO bridge:       slack.work: joining tech-chat (ID: tech-chatslack.work)
[0000] DEBUG slack:        Choosing token based receiving
[0000] DEBUG slack:        == Receiving event &slack.ConnectingEvent{Attempt:1, ConnectionCount:0}
[0000]  INFO gateway:      Starting bridge: xmpp.work
[0000]  INFO xmpp:         Connecting im.example.com
[0000] DEBUG xmpp:         &errors.errorString{s:"unmarshal <features>: expected element type <features> but have <error>"}
[0000] FATAL main:         Starting gateway failed: Bridge xmpp.work failed to start: unmarshal <features>: expected element type <features> but have <error>

Environment (please complete the following information):

OS:
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
KERNEL="4.4.0-134-generic"

Matterbridge version:
version: 1.11.3 0bd5a0d

Additional context:
[xmpp.workxmpp]
Server="im.example.com:5222"
<EMAIL_ADDRESS>Password="LDAP-PASSWORD"
Muc="conference.im.example.com"
Nick="xmppbot"
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "

[slack.workslack]
Token="TOKEN"
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "

[[gateway]]
name="gate"
enable=true

[[gateway.inout]]
account="slack.workslack"
channel="tech-chat"

[[gateway.inout]]
account="xmpp.workxmpp"
channel="tech"

Can not reproduce this, I've setup an own ejabberd to test this, but it works fine.
Try adding debug=true to your [xmpp.workxmpp] section, this will show the xml from xmpp which maybe gives some hints.
Below is what I tried
docker run --name ejabberd -d -p 5222:5222 ejabberd/ecs
docker exec -it ejabberd bin/ejabberdctl register admin localhost passw0rd

[xmpp.myxmpp]
Server="localhost:5222"
Jid="admin@localhost"
Password="passw0rd"
Muc="localhost"
Nick="xmppbot"
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "
SkipTLSVerify=true
debug=true

Alright, I was able to get this working. It was a misconfig on the ejabbered side that the server admin took care of. Thanks again for looking into this.

@dev01d Care to share? I'm having the exact same issue.


"In Vue 2.7, when using Tailwind CSS 2.0 version and the Tailwind Element component without enabling the JIT mode, the ripple effect of buttons may not be successful."

Describe the bug
No, using Tailwind Element in Vue 2.7 does not require you to enable JIT mode. However, if you want to use certain features, such as the button ripple effect, then you may need to enable JIT mode.
ata-te-ripple-init cannot be compiled

In Tailwindcss JIT mode, it is very slow to rebuild the project every time it is saved.

Hi. This is an older issue so I don't know whether that was fixed in v1.0.0-beta2 but I do not see the issue right now. I created a new app with vue 2.7 and latest tailwind (our components are using some of the newer things offered by tailwind, so the most recent version the better).
I've used the first examples from Ripple and Datepicker in my test. I found out while dealing with issues experienced in nuxt and next, that sometimes importing components with use of dynamic imports inside mounted hooks helps.
For example like that:
<script>
export default {
  name: "App",
  components: {},
  mounted: async function () {
    const { Datepicker, Input, Ripple, initTE } = await import("tw-elements");

    initTE({ Datepicker, Input, Ripple });
  },
};
</script>

Let us know if the issue is still here and whether my solution helped.


Asset directory mounts do not work on Windows

The was reported by freaky.ashes on Discord - thanks to them for flagging it.
To reproduce:

Create a Spin app with an asset directory mount (e.g. files = [{ source = "assets", destination = "/" }])
Run it on Windows
You get a "couldn't resolve \assets<component>" error for the component asset directory, because the assets directory didn't get created

This happens because of a conflict between canonicalisation and the glob crate: when a glob is prefixed with a canonical (UNC) path, it does not match any files.  (And asset directories get created only when files exist to be copied into them.)  To reproduce this, create this Rust app:
use std::path::PathBuf;

fn main() {
    println!("Using plain dir");
    let bp = PathBuf::from(env!("CARGO_MANIFEST_DIR"));
    let paths = glob::glob(bp.join("src/**/*").to_str().unwrap()).unwrap();
    for path in paths {
        println!("{path:?}");
    }

    println!("Using canonicalised dir");
    let bp = PathBuf::from(env!("CARGO_MANIFEST_DIR")).canonicalize().unwrap();
    let paths = glob::glob(bp.join("src/**/*").to_str().unwrap()).unwrap();
    for path in paths {
        println!("{path:?}");
    }
}

It prints something like
Using plain dir
Ok("D:\\Code Experiments\\globtest\\src\\main.rs")
Using canonicalised dir

This breaks directory mounts on Spin 2 because we canonicalise the source path, and use <source-path>/**/* to implement directory copying.  I assume it also breaks glob mounts too but have not tested that case.
This is a known bug in the upstream glob crate: https://github.com/rust-lang/glob/issues/132.  The issue suggests a workaround which, although unsafe for general use, should be fine for us.  Alternatively it might suffice to absolutise rather than canonicalise.  The issue is 6 months old and there's no movement on it so we should not expect a fix from upstream.

Also, this implies we're not testing asset loading on Windows.  It would be good to cover that gap - I thought those tests ran across all platforms.

This also affects wildcard globs, but not single-file patterns.  If you have a mix that contains a single-file pattern, the app runs but the files from wildcards and directory mounts are not there, only the single files.


Fix conflicts 2

What does this change
Fixes merge conflicts. I ran go mod tidy and go mod vendor to get our bitbucket package added back.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1611

Relevant Lines:
4513

💛  - Coveralls


MODORDERS-391 Release all encumbrances when order is closed Api test

Signed-off-by: Yauheni Kuzmianok<EMAIL_ADDRESS>


convergence problems with poissonexp

I got negative pseudo-R2s on the V4 data
so I checked:
running with default reg_lambdas seems to work fine
import numpy as np
import scipy.sparse as sps
from sklearn.preprocessing import StandardScaler
from pyglmnet import GLM

# create an instance of the GLM class
model = GLM(distr='poissonexp', verbose=False, alpha=0.05)

n_samples, n_features = 10000, 100

# coefficients
beta0 = np.random.normal(0.0, 1.0, 1)
beta = sps.rand(n_features, 1, 0.1)
beta = np.array(beta.todense())

# training data
Xr = np.random.normal(0.0, 1.0, [n_samples, n_features])
yr = model.simulate(beta0, beta, Xr)

# testing data
Xt = np.random.normal(0.0, 1.0, [n_samples, n_features])
yt = model.simulate(beta0, beta, Xt)

# fit Generalized Linear Model
scaler = StandardScaler().fit(Xr)
model.fit(scaler.transform(Xr), yr)

# we'll get .fit_params after .fit(), here we get one set of fit parameters
fit_param = model[-1].fit_

# we can use fitted parameters to predict
yhat = model.predict(scaler.transform(Xt))
print 'reg_lambdas:', model.reg_lambda
print 'pseudo_R2s:', [model.pseudo_R2(yt,i,np.mean(yr)) for i in yhat]

Output:
reg_lambdas: [ 0.5         0.3237394   0.2096144   0.13572088  0.08787639  0.0568981
  0.03684031  0.02385332  0.01544452  0.01      ]
pseudo_R2s: [0.43841608601335824, 0.49823894207455854, 0.54805964244862948,
0.5411179410997351, 0.56589624430495222, 0.52914657441486135, 0.57277441499592874,
0.52690973730494284, 0.57043414426245309, 0.53886579676913726]

However if I choose another, even not that different range here’s what happens:
import numpy as np
import scipy.sparse as sps
from sklearn.preprocessing import StandardScaler
from pyglmnet import GLM

# create an instance of the GLM class
model = GLM(distr='poissonexp', verbose=False, alpha=0.05, reg_lambda=[0,0.0001,0.001,0.01,0.1,0.2,0.5])

n_samples, n_features = 10000, 100

# coefficients
beta0 = np.random.normal(0.0, 1.0, 1)
beta = sps.rand(n_features, 1, 0.1)
beta = np.array(beta.todense())

# training data
Xr = np.random.normal(0.0, 1.0, [n_samples, n_features])
yr = model.simulate(beta0, beta, Xr)

# testing data
Xt = np.random.normal(0.0, 1.0, [n_samples, n_features])
yt = model.simulate(beta0, beta, Xt)

# fit Generalized Linear Model
scaler = StandardScaler().fit(Xr)
model.fit(scaler.transform(Xr), yr)

# we'll get .fit_params after .fit(), here we get one set of fit parameters
fit_param = model[-1].fit_

# we can use fitted parameters to predict
yhat = model.predict(scaler.transform(Xt))
print 'reg_lambdas:', model.reg_lambda
print 'pseudo_R2s:', [model.pseudo_R2(yt,i,np.mean(yr)) for i in yhat]

output:
reg_lambdas: [0, 0.0001, 0.001, 0.01, 0.1, 0.2, 0.5]
pseudo_R2s: [0.10370201748019414, -0.024446271196854941, 0.10307940713282349,
-0.019807866066520852, 0.040822101620644258, 0.087468883241032636, 0.17386339833109343]

if I switch the order of the reg_lambdas then it works again.
i.e. if I give it
reg_lambda=[0.5, 0.2, 0.1, 0.01, 0.001, 0.0001, 0]) instead of reg_lambda=[0, 0.0001, 0.001, 0.01, 0.1, 0.2, 0.5]) then it works.
So my guess is that it is working well in this particular example for the higher values of reg_lambda and then it takes advantage of the warm restart.
Which brings 2 issues:

should converge better for any individual lambda;
if it doesn’t then warm restarts might biasing results and hiding bugs/issues: we should always compare warm restar vs non-warm to check for biases, we should have an option to switch-off warm-restarts while we are testing/developing pyglmnet, since it might be hiding bugs

should converge better for any individual lambda

maybe this could be a test?

if it doesn’t then warm restarts might biasing results and hiding bugs/issues: we should always compare warm restar vs non-warm to check for biases, we should have an option to switch-off warm-restarts while we are testing/developing pyglmnet, since it might be hiding bugs

okay, we can do that too but option should not be in the public API. Maybe in a private function / method ...

an alternative to shutting down warm restarts is  to just run it for each individual lambda at a time and compare it to when running them together.
I haven’t manage to get positive pseudo-R2s on the V4 neuron for the canonical link function in pyglmnet distr=poissonexp, I have tried several reg_lambdas.
Using R with the canonical link I get pseudo-R2 = 0.0383 (+/-0.0059)
Using pyglmnet with the (non-canonical) default link function I get 0.0260 (+/-0.0070).

according to the paper, the logic of warm restarts doesn't work if we go from low to high lambda. they recommend fitting the largest lambda first and initializing the next lambda after.
fix: the documentation should include this so that user knows to specify lambda's in decreasing order.
@hugoguh shall i close this issue and create a new issue for documentation related changes?

still it should converge for a single reg_lambda
import numpy as np
import scipy.sparse as sps
from sklearn.preprocessing import StandardScaler
from pyglmnet import GLM

model = GLM(distr='poissonexp', verbose=False, alpha=0.05, reg_lambda=[0.001])

n_samples, n_features = 10000, 100

# coefficients
beta0 = np.random.normal(0.0, 1.0, 1)
beta = sps.rand(n_features, 1, 0.1)
beta = np.array(beta.todense())

# training data
Xr = np.random.normal(0.0, 1.0, [n_samples, n_features])
yr = model.simulate(beta0, beta, Xr)

# testing data
Xt = np.random.normal(0.0, 1.0, [n_samples, n_features])
yt = model.simulate(beta0, beta, Xt)

# fit Generalized Linear Model
scaler = StandardScaler().fit(Xr)
model.fit(scaler.transform(Xr), yr)

# we'll get .fit_params after .fit(), here we get one set of fit parameters
fit_param = model[-1].fit_

# we can use fitted parameters to predict
yhat = model.predict(scaler.transform(Xt))
print 'reg_lambdas:', model.reg_lambda
print 'pseudo_R2s:', [model.pseudo_R2(yt,i,np.mean(yr)) for i in yhat]

output:
reg_lambdas: [0.001]
pseudo_R2s: [-0.024434697354696278]

I don’t think this issue should be closed.
It’s not about documenting the order of the lambdas when using warm starts (though that should be documented).
This issue was about the convergence which still fails in this case. While R doesn’t.
So far I have tried pyglmnet on two real datasets and it has failed to converge for both:

failed on V4 (canonical poisson) while R works
failed on Electro imaging data (normal with l1-reg) for which sklearn' lasso worked, it worked better when we changed the learning rate but sill with poor results.
needs a better optimization algorithm

@hugoguh I agree we should crease out the convergence issues urgently. Did you manage to trace the source of the bug?

@hugoguh agreed that we should make the outputs conform to sklearn and R glmnet package for whichever use cases exist in those tools. I appreciate all the testing!

Let's aim to get to the bottom of the bug.
In your bug report above, I wouldn't call it a convergence issue, so much as a poor choice of reg. parameter. Note that the absolute value of reg. parameter lambda cannot be directly compared for scikit learn and pyglmnet. This is because the cost function (negative log likelihood) is normalized slightly differently. Therefore the relative weight of the penalty term will be different in scikit learn and pyglmnet for the same choice of lambda.
In your bug report above, the test set pseudo-R2 being negative, simply indicates that the model has overfit to the training set. This can be verified if you print both training set (R2r) and test set pseudo-R2s (R2t) for the above example for both scikit learn and pyglmnet.
I would expect to see comparable R2r and R2t for scikit learn but a large positive R2r and negative R2t for pyglmnet

As for the linear case with Roozbeh's data, we figured out that the fit improves a lot with a better choice of learning rate. We can only get to the bottom of this issue after the learning-rate-free newton-cg solver has been implemented in issue #39. My goal is to solve #39 this weekend

@pavanramkumar
we can compare them directly when setting reg_lambda to zero. R with V4 data and sklearn with Roozbeh’s data worked fine with reg_lambda=0, while pyglmnet didn’t. So I think it is a convergence issue.
I agree that we need the adaptive learning rate optimizer, and while it is not implemented (and also when it is) implemented we should use sklearns newton on our cost function to check that the bug is only a optimization issue

From here: http://scikit-learn.org/stable/modules/generated/sklearn.linear_model.ElasticNet.html
alpha : float
Constant that multiplies the penalty terms. Defaults to 1.0 See the notes for the exact mathematical meaning of this parameter. alpha = 0 is equivalent to an ordinary least square, solved by the LinearRegression object. For numerical reasons, using alpha = 0 with the Lasso object is not advised and you should prefer the LinearRegression object.

Turns out this is mainly an issue of regularization path. See conversation in #76
Should I create new issue for "solution dependence on regularization path"?

let's just rename this issue so that all the conversation is in the same place?


Question: Can I use i18n for support documentation from property

In this moment I'm using applicaction.properties for documentation properties, but I wanna use messages properties for that, considering that it allow me to document in several languages

Same here, someone help us plz!
Cheers

@gasperlf thanks for the great suggestion. Any of you brave enough to try your hand at a PR? Its very similar to DescriptionResolver

I'd like to help you, with this improvement, tell me what need to do?

@gasperlf thank you for helping out. I'll outline how to go about it in a bit


Waf generator and some tests

Hi,
I've had this custom Waf generator floating around some of my projects for a while, and while it was buggy, I was using extra layers in my stack to work around any issues.
However, I got motivated a few weeks ago to finally fix it and try to make it more standard, and right now I think it's in a much more useful state as a standalone generator. So I'm posting it here after @memsharded's recommendation in case someone else using Waf can try it out and report back.
One part I'm not too sure about in this PR is the tests, since I also had to include a copy of the waf script in there. Maybe it'd be better to have the test script download it instead, since most people who config install probably won't need it?
Usage
The generator works by generating a waf tool, which is essentially just a Python script that the user loads during project configuration. This means the generator has a big ugly string template in it, but it makes it much easier to use since it means it can be added to any existing Waf project without having to install/ship a custom Conan extension (and worry about versioning issues).
I also wrote some guides on how to use it on my website

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


chunkNames in Server Stats file different from Client stats file

Hello,
I have read the issues and Readme, and I've been struggling with this for a few days now. I am trying to set up loadable for a un-ejected CRA app. I'm using Craco to override webpack config and it seems to be working, as the client side loadable-stats.json is being generated. When I run the build command, the chunks are named based on id. So for my server config, I decided to name the chunks by id too. But unfortunately the chunkNames seem to be the path to the modules in the server stats file, rather than id. The actual chunks are named by 'id` though.
Due to this, when I run the nodeExtractor (which is reading from the server stats file) to collectChunks and then webExtractor (which is using the client stats file) to getScriptElements I get an empty array of loadable chunks. If I only use the webExtractor it throws an error that chunkNameFromServerStatsFile not found.
If this is a duplicate issue I'm sorry I'll remove it, but I'm at my wits end trying to solve this.
My webpack config for the server is using the server.js file which contains the Express code as the entry point, whereas the webpack config for the client has the index file for the app as the entry. I get an empty {} as the server requireEntrypoint result. I'm not really sure what is supposed to happen here, the actual documentation is not very clear. I am following the SSR example on Github to set this up.
    const nodeStatsFile = path.resolve(__dirname, 'node-stats.json');
    const nodeExtractor = new ChunkExtractor({ statsFile: nodeStatsFile, entrypoints: ["server"] });
    const nodeEntryPointResult = nodeExtractor.requireEntrypoint("server");  // ==> {}
    const webStatsFile = path.resolve(__dirname, '../web-stats.json');
    const extractor = new ChunkExtractor({ statsFile: webStatsFile });
    const client = generateApolloClient();
    const app = (<ApolloProvider client={client}>
        <HelmetProvider context={helmetContext}>
          <Router location={req.url} context={staticContext}>
            <CookiesProvider cookies={req.universalCookies}>
                <App />
            </CookiesProvider>
          </Router>
        </HelmetProvider>
      </ApolloProvider>);
    getDataFromTree(app).then(() => {
      const jsx = nodeExtractor.collectChunks(app);
      const content = ReactDOMServer.renderToString(jsx);
      const state = client.extract();
      const { helmet } = helmetContext;

      const html = ReactDOMServer.renderToString(
        <Html content={content} helmet={helmet} assets={assets} extractor={extractor} />,
      );
      res.status(staticContext.status || 200);
      res.send(`<!doctype html>${html}`);
      res.end();
    })

In the Webpack config for both client and server I have set chunkFilename: '[id].js', and I can see that even on the server the actual chunk files are named by ID. the node-stats.json has the whole path as the chunkName though.
Any help here would be appreciated and again if this is not a valid question please let me know I'll remove it. Thanks!
## System:
 - OS: macOS Mojave 10.14.6
 - CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
 - Memory: 632.42 MB / 16.00 GB
 - Shell: 3.2.57 - /bin/bash
## Binaries:
 - Node: 8.16.0 - ~/.nvm/versions/node/v8.16.0/bin/node
 - Yarn: 1.16.0 - ~/.nvm/versions/node/v8.16.0/bin/yarn
 - npm: 6.13.1 - ~/.nvm/versions/node/v8.16.0/bin/npm
## npmPackages:
 - @loadable/babel-plugin: ^5.10.0 => 5.11.0
 - @loadable/component: ^5.9.0 => 5.11.0
 - @loadable/server: ^5.9.0 => 5.11.0
 - @loadable/webpack-plugin: ^5.7.1 => 5.7.1

You have to use the same loadable-stats generated for the client for both the server and the client.

@theKashey Thanks! I'll give that a try, but just to confirm, should I be running the @loadable/webpack-plugin in the server Webpack build as well? If it's not being used, perhaps I'm making a mistake by including it there as well.

Update: This was happening because I forgot to include the @loadable/babel-plugin into the Client side Webpack override, in my craco config. Closing the issue as everything works great now, thanks!


Feature | Stats page

Stats page
Backend:
new statsRouter

Total users count
Total blogs count
Total contributors count
Top 5 users by subscriber count
Top 5 blogs by claps count
Top 5 tags by blogs count

Frontend
new /stats page
Minimalistic ui, be creative if needed, not mandatory. Just display these stats as list / cards.

I will get started on this feature

@nipunh - What's the update on this one ?

Will complete over the weeken

Will complete over the weekend
Can you give me access to the repo, I have forked it for now and working on it


fix(init): check env_path when privileged worker init

Privileged worker will sleep 10 ms to wait other worker create lmdb directory.
See FT-3534 and https://github.com/Kong/kong/pull/9755

It may introduce artificial race condition, so I close it.


update submodules

I followed the readme instructions to test this with : ros2 launch nav2_bringup tb3_simulation_launch.py use_simulator:=False map:=~/Rapyuta3/Prog/turtlebot3-UE/Content/Turtlebot3_benchmark.yaml but RViz does not display anything and I get the messages : Timed out waiting for transform from base_link to odom to become available, tf error: Invalid frame ID "odom" passed to canTransform argument target_frame - frame does not exist

Did you  do fastdds_setup.sh ?


RC3+ support?

Any plans to upgrade the code base? I'd really like to upgrade my project to RC3 or RC4 but the swiper code is hold it back with the breaking error about Directive annotation.
thanks.

Will update it to latest angular in a day or two


Mac: Using Migration Assistant

I recently used the Apple Migration Assistant to migrate all my user data to a new Mac.  I have Keybase setup on the old Mac (this was in fact the original device used to create my Keybase account).  The Migration Assistant essentially make a complete copy of all data in your user profile and copies it to the new Mac.  I imagine this issue might also occur of you do a manual copy of the Keybase folder in your profile Library (but I have not confirmed that).
I was able to open Keybase and access all my data on the new Mac, however in the Devices list the Keybase app lists the current device as the old Mac.  I was still logged into Keybase on the old Mac as well, and messages were being received on both devices.  I was able to send messages as well.
I had to log out of and quit Keybase on my new Mac, renamed the Keybase folder in my Library folder, then open Keybase again to start as if it was a fresh install and properly add the device.

Thanks for sharing the above.  Same issue, same solution.
Does seem like "disassociate device" feature would handle this scenario.  I didn't want to revoke the old machine, just disassociate the clone so I could define a new device id for the new migration clone.


[ZEPPELIN-2584]. Livy doesn't work under kerberos and ssl

What is this PR for?
We found that Livy doesn't work under kerberos and ssl, this is due to a bug when constructing KerberosRestTemplate. This PR fix this issue.
What type of PR is it?
[Bug Fix]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-2584

How should this be tested?
Unfornatelly it is difficult to add system test, so I manually tested it in a secure cluster.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@prabhjyotsingh Mind to review this ? Thanks

Generally looks good, will test it out in one of my test clusters, and update this thread.

Took me a while to configure zeppelin.livy.ssl.trustStore and zeppelin.livy.ssl.trustStorePassword but looks good works on my local.

Thanks @prabhjyotsingh , will merge it if no more discussion.
The failed test is not related.
Tests in error:
  ZeppelinSparkClusterTest.pySparkTest:295 NullPointer


Ingress controller: TLS support

Ingress resource specification allows to secure an ingress by specifying TLS configuration which is used for TLS termination.
This probably needs to be resolved as part of the larger story of TLS support within the Istio proxy (see #52).

Istio Auth alpha design omits ingress entirely. We should do an ad-hoc solution using secrets/configmaps following kubernetes practices and revisit this once the in-cluster auth is past alpha.

I think Isaiah is starting to take a crack on that.
On Tue, Mar 14, 2017 at 12:39 AM Kuat<EMAIL_ADDRESS>wrote:

Istio Auth alpha design omits ingress entirely. We should do an ad-hoc
solution using secrets/configmaps following kubernetes practices and
revisit this once the in-cluster auth is past alpha.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/216#issuecomment-286320273, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd_80G4GHZIymBiAOMwgt-Hv_icidks5rlhnygaJpZM4MNE54
.

--
~shriram

https://github.com/istio/manager/pull/352 provides basic TLS support for ingress.

Does anything else need to be done for this issue for alpha?

I don't know about alpha vs. future prioritization, but I think we should at least support reading TLS secret name from ingress resource, as specified here. That should probably be satisfactory TLS support to start with.

The main obstacle for implementing this is that it's still unclear how to represent the ingress TLS configuration in the model.
One option that @kuat raised in #151 was to create a different model object for ingress (e.g., IngressRule) and use that instead of RouteRule.
Another option is to extend the model with some more specific object (e.g. a TLSContext associating a port/vhost to a secret) and also extend the RouteRule.Match so that we can indicate that a RouteRule (derived from an ingress) is for HTTPS traffic.
Thoughts?

I think we have worked out a solution to that for the interim. Waiting on
Isaiah to finish his PR for this.
On Tue, Apr 4, 2017 at 9:11 AM Zvi Cahana<EMAIL_ADDRESS>wrote:

The main obstacle for implementing this is that it's still unclear how to
represent the ingress TLS configuration in the model.
One option that @kuat https://github.com/kuat raised in #151
https://github.com/istio/manager/issues/151 was to create a different
model object for ingress (e.g., IngressRule) and use that instead of
RouteRule.
Another option is to extend the model with some more specific object (e.g.
a TLSContext associating a port/vhost to a secret) and also extend the
RouteRule.Match so that we can indicate that a RouteRule (derived from an
ingress) is for HTTPS traffic.
Thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/216#issuecomment-291494834, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd-MHvbUdVTEJpZRqJvz3GV9jBvbiks5rskGSgaJpZM4MNE54
.

--
~shriram

@rshriram are you referring to the TLS secret name passed with a flag to the manager?

Yep. Trying to model the ingress specifically for kubernetes seems odd.
Ideally it should be part of auth but that's a different conversation.
Besides, all route rules deal with a destination service (from perspective
of caller).
We do not have configuration constructs that deals with a service from
perspective of a service provider or server. Today they are baked into k8s.
What kinds of certs does the service have, what kinds of policies does it
want to expose, etc. a slightly similar argument applies for egress to
external services, where mutual tls auth may not apply.
I think these are part of service configurations and they have to be made
as first class entities and dealt with in proper manner.
On Tue, Apr 4, 2017 at 9:27 AM Zvi Cahana<EMAIL_ADDRESS>wrote:

@rshriram https://github.com/rshriram are you referring to the TLS
secret name passed with a flag to the manager?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/216#issuecomment-291499142, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd3z7wdPiFC37ENXyAlunqW9LTMuyks5rskVFgaJpZM4MNE54
.

--
~shriram

I was thinking how ingress differs from the regular route rule. If you think of ingress proxy as a special service, then the main difference is that the destination weight field refers to a different service than the ingress. E.g.
destination: ingress-service
match:
  httpHeaders:
    uri:
      prefix: /a
route:
- destination: a.default.svc.cluster.local

This poses two questions:

do we apply route rules towards the destination service, that is do we unroll the target destination into a bunch of route rules? if we allow any route rule to refer to a distinct destination in the route than its destination, then how do we prevent multiple unrolls, e.g. if "a.default" is actually routing to "b.default", do we also apply rules of "b.default"?
should TLS context be a property of the route? I think @rshriram is proposing to use "authority" header to uniquely identify the TLS certs but then nothing in our model prevents from using multiple route rules that use the same "authority".

You are right that we can use route.destination for ingress. However, the
top level destination cannot just be targeting istio-ingress. Users could
define custom hosts like foo.bar.com and route it to a.default. So we can
capture these by allowing users to use foo.bar.com as the top level
destination field. While generating configs for ingress envoys, we should
accept rules with destinations that do not match any internal service.
destination: foo.bar.com
route:

destination: a.default.svc.cluster.local
tags: version=v1..
weight: 50

When generating Envoy configuration, we need to have foo.bar.com in the
virtual host domain match, and the rest of istio-ingress in wildcard match.
With regard to unrolling multiple times, it's something we will have to do
eventually, imo. But we could cross the bridge when we get there. Typical
ingress specs don't unroll. And our typical routing examples do not unroll
either (yet).
Now with respect to tls certs, we can model it internally but do we have to
capture it in the route rule? Because these can be specified via the
ingress resource (internal tls is handled by auth already).
On Wed, Apr 26, 2017 at 12:06 AM Kuat<EMAIL_ADDRESS>wrote:

I was thinking how ingress differs from the regular route rule. If you
think of ingress proxy as a special service, then the main difference is
that the destination weight field refers to a different service than the
ingress. E.g.
destination: ingress-service
match:
httpHeaders:
uri:
prefix: /a
route:

destination: a.default.svc.cluster.local

This poses two questions:

do we apply route rules towards the destination service, that is do
we unroll the target destination into a bunch of route rules? if we allow
any route rule to refer to a distinct destination in the route than its
destination, then how do we prevent multiple unrolls, e.g. if "a.default"
is actually routing to "b.default", do we also apply rules of "b.default"?
should TLS context be a property of the route? I think @rshriram
https://github.com/rshriram is proposing to use "authority" header
to uniquely identify the TLS certs but then nothing in our model prevents
from using multiple route rules that use the same "authority".

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/216#issuecomment-297232245, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd0NQku0vxXcYUFoClwNtmsW32sYPks5rzsLfgaJpZM4MNE54
.

--
~shriram

I'm not so sure whether we want to allow external service names as destinations. Destinations after all is inside the cluster. One idea could be to mark a route rule as "external" and that will expose the rule outside the cluster. The ingress service will be an implementation detail. In the example above:

destination: a.default.svc.cluster.local
external: true
match:
  httpHeaders:
    authority:
      exact: my.domain.com
    uri:
      prefix: /a

Using authority as a destination has some drawbacks: how do we handle the wildcards (*.my.domain.com)? I find it confusing to have two destinations "my.domain.com" and "a.default.svc.cluster.local" for the same route...

TLS is a property of route as defined by Ingress spec. You can have TLS and non-TLS paths for the same domain which is a reasonable use case.

support exists as of istio 0.1.6

TLS is rather half-baked. No SNI and poor security with secret transfer. Leave it open until it's beta-quality.

Just SNI left. Secret transfer sorted out.

#484  is tracking SNI support..


Alphabetical ordering for all files

If anyone wants to review this, I'll leave it open for 24h.

Many thanks @onebree for the fantastic review! I fixed the errors. Could you please tell me what you think?


Unable to see the image

Image Link broken for 3 illustrations showing how different customers distribute workloads across cloud providers.

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

ID: da811d0e-df5f-0715-cc72-8b4f1bb1bb49
Version Independent ID: 55e4182b-954d-0822-d6cf-2f59c37a1b2c
Content: Ready methodology for Hybrid and Multicloud - Cloud Adoption Framework
Content Source: docs/scenarios/unified-operations/ready.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 363781

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 363781

This has been fixed in the private repo. Thanks,

This has been fixed in the private repo. Thanks,


[Bug]: Code coverage reports fail to generate if path is given as the first argument

Description
We can run test command by passing a path as bal test <PATH>. However if we try to generate code coverage reports using bal test <PATH> --test-report --code-coverage this would just run the tests without generating code coverage report. Also note if we run bal test  --test-report --code-coverage <PATH> (path as the last argument) it will generate the code coverage report.
Steps to Reproduce

Create a ballerina project at say ~/foo directory and add a dummy test file in to the test sub directory
Run bal test ~/foo --test-report --code-coverage

Affected Version(s)
2201.8.1
OS, DB, other environment details and versions
Linux
Related area
-> Test Framework
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

bal test <PATH> --test-report should print an error since Picocli does not allow params (--test-report) after the argument ().

This is mentioned in the test command synopsis.
$bal test -h

SYNOPSIS
       bal test [OPTIONS] [<package>|<source-file>] [(-Ckey=value)...]


Serve logo with proper MIME type

Chalk logo on npm.com: I don't feel so good, Mr. Stark.

Strange: I looked into the public npm repository. I saw 761,349 packages.
Stark: How many of those had incorrect incorrectly served images in their readme?
Strange: Many of them. But Chalk was the most popular repo of all of them

Sorry for the above one, I did this PR 1:35 AM and wanted to have some extra fun.
If you would like to use rawgit as you used in the screenshot, please let me know and I can use that.

Can you explain the use of this query param?

Report it here: https://github.com/npm/marky-markdown/issues I'm not interested in changing something to work around npm's lousy Markdown rendering :)

@Qix- : it serves the linked file with an appropriate content type, in this case, instead of text/plain it will be image/svg+xml
Please check the difference here:
https://raw.githubusercontent.com/chalk/chalk/master/media/logo.svg
https://raw.githubusercontent.com/chalk/chalk/master/media/logo.svg?sanitize=true
@sindresorhus With due respect, I don't think this is the issue of npm's markdown rendering. GitHub uses this parameter when displaying an image.

With due respect, I don't think this is the issue of npm's markdown rendering. GitHub uses this parameter when displaying an image.

It's GitHub that adds that parameter and so should npm. If npm wants to render GitHub readme's they should do it properly and follow how GitHub does it.

npm's lousy Markdown rendering

For context, this is far from the first npm Markdown issue I've had to deal with. Probably the twentieth or more issue. So excuse my grumpiness 😃🙌


Do something about the horrible logo on the Operating System panel

Under System Settings → System →Operating System it shows the logo from the LOGO attribute in /etc/os-release. Currently this points to the Fedora logo which doesn't look correct at all in its current state:

It clashes with the default background behind it quite badly.
It overflows the circle.
It doesn't fit elementary's look.

We could either modify the Fedora logo to fit and match, or come up with a new logo?

Fixed in 434db9d237d52f19d37d1facbc861c019d9a8030


Unable to access postgres DB

Unable to access postgres DB
pooler error log:
DbHandler: Connection failed {:error, :econnrefused} to '2600:1f18:2e13:9d01:6cbe:1d1d:2d4f:8387':5432
metadata:
[
{
"ansi_color": null,
"app_name": null,
"callers": [],
"context": [
{
"application": "supavisor",
"domain": [
"elixir"
],
"file": "lib/supavisor/db_handler.ex",
"function": "handle_event/4",
"gl": "<0.2765.0>",
"line": 116,
"mfa": [
"Elixir.Supavisor.DbHandler",
"handle_event",
"4"
],
"module": "Elixir.Supavisor.DbHandler",
"pid": "<0.4119.7558>",
"registered_name": null,
"time":<PHONE_NUMBER>829675,
"vm": [
{
"node"<EMAIL_ADDRESS>}
]
}
],
"db_name": null,
"depth": null,
"error_logger": [],
"formatter_error_params": [],
"instance_id": "i-0b956f1542891a9c7",
"internal_log_event": null,
"level": "error",
"local": null,
"mode": "session",
"peer_ip": null,
"project": "vwdxziqtyecgiwrzfttb",
"region": "us-east-1",
"request_id": null,
"stacktrace": [],
"type": null,
"user": "postgres"
}
]
Restarting the project did not help. The issue has been ongoing for 7 hours.

@dz235 are you still experiencing this issue? If this is a hosted instance at supabase.com you can reach out to support at https://supabase.com/dashboard/support/new
This issue queue is for reporting issues with the open source release of supabase/postgres. I will close this, but feel free to  re-open if your issue is with the open source release. Otherwise, if you open a support ticket if you are still experiencing problems, our support team will respond.


Fix build

The travis versions contained release instead of tip. I'm not sure if this was simply a typo.
Concerning the code, Layer does not define a method UsePhase but simply Use which accepts a string. So the code was changed accordingly to fix the build.

:eyes:

Thanks for the PR.
As clarification, the current project stage should be considered as private alpha under heavy development. Packages are not stable, there're missing tests, interface contract may change and docs are missing.


Kill the id-to-func map after wrap-opkill

Wrap-opkill will create a new function, invalidating the id-to-func map.
The preserved analyses for the pass have been updated to reflect that.
Also adding consistency check for the id-to-func map.  With this new
check, old tests identify this problem.  No new tests are needed.
Fixes #3038

The macos failure is related to the nosetest that is being looked into.


Improving documentation

Pull Request Test Coverage Report for Build 6a7075308077abc1c8bd7c70f4d302d5ef023828-PR-5

4 of 6 (66.67%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 86.236%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/connection/executor/request_executor.ex
1
2
50.0%

lib/rql/query.ex
2
3
66.67%

Totals

Change from base Build 0b43fae6f9a23d5f06b5d67f1c88ea8edd597788:
0.5%

Covered Lines:
614

Relevant Lines:
712

💛  - Coveralls


state change with data image whacks the xy cursor of the zoom, also the prev, next button does not work

when i tried to make a state change to the data image, bec the image data is mostly coming from a backend call, the xy cursor of the zoom function has become not aligned with the image, also the prev, next button will not work
pls find code below added to SliderImage.examples.md :
import {useState, useEffect} from 'react';
import SliderImage from 'react-zoom-slider';

const data = [{
  image: 'https://cdn.tgdd.vn/Products/Images/42/209800/oppo-reno2-f-xanh-1-org.jpg',
  text: 'img1'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/209800/oppo-reno2-f-xanh-4-org.jpg',
  text: 'img2'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/209800/oppo-reno2-f-xanh-10-org.jpg',
  text: 'img3'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/210653/iphone-11-pro-max-256gb-mau-bac-1-org.jpg',
  text: 'img4'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/210653/iphone-11-pro-max-256gb-mau-bac-6-org.jpg',
  text: 'img5'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/221926/huawei-y6p-xanh-1-org.jpg',
  text: 'img6'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/221926/huawei-y6p-xanh-10-org.jpg',
  text: 'img7'
}, {
  image: 'https://cdn.tgdd.vn/Products/Images/42/221926/huawei-y6p-xanh-12-org.jpg',
  text: 'img8'
}, ];

function Test(props){
  const [myData, setData] = useState([{image: ''}])

  useEffect(() => {
    setData(data.map(el => ({image: el.image, })))
  }, [])

  return (
    <SliderImage data={myData} width="500px" showDescription={true} direction="right" />
  )
}

<Test />

..the solution is so simple....i dont know if the developer just forget this??
just add '[data]' into the useEffect, and useCallback function of the 'SliderImage.js' file in the source folder...then the zoom image and prev, next button will all work fine.


Update the validation of the privilege property on the windows_user_privilege resource

Built off #10421

I read #10420 and I'm confused what the actual problem was and how this PR addresses it.

There's more to that issue than this fix, but this resolves some strange code in the validation, gives us users as strings and adds specs


swiftyjson add fails

marathon add https://github.com/SwiftyJSON/SwiftyJSON.git
it does have a package.swift file and a tag. not sure why it doesn't work.
https://github.com/SwiftyJSON/SwiftyJSON/issues/823

@johndpope You can add by marathon add git@github.com:SwiftyJSON/SwiftyJSON.git.
 ✘ pixyzehn ⮀ ~ ⮀ marathon add git@github.com:SwiftyJSON/SwiftyJSON.git
📦  SwiftyJSON added

@pixyzehn is right - use SSH-based cloning at it'll work 👍 But, we should totally add support for HTTPS-based clones. I'll rename the issue to reflect that.

@JohnSundell If one were interested in implementing this, where would one begin to look? I'll have a look around and see if I might be able to do it. No promises though :)

@garricn Actually, this has already been fixed, just forgot to close the ticket 😱


Slow startup times and laggy usage

I love this plugin, but something in a recent update made it way slower for some reason. It takes 3,011ms to start up, which is about half of the community plugin startup time. It also seems to sometimes not work at all. Not really sure why that is but I hope it is fixable. I also found this error in the console.

Hi @SandmansDreams, thanks for the good feedback!
Please try to update the plugin in obsidian. I see that you have installed the version v1.0.6. This week i made the update to version v1.1.2, which is now also compatible with the new obsidian version.

Open settings in obsidian
Go to the community plugins Tab and click the button "check for updates"
After that, an update button should pop up for the plugin.

Please give a short feedback, if this solution helped.
Regards
Dario

Wow you really got it. Down to 1ms at the bottom of my plugins list!

However, still just as slow when in use when collapsing and opening folders unfortunately. However, this might be due to something on my end somehow, not 100% sure its the plugins fault.

Hi @SandmansDreams, glad that the update helped!
I haven't noticed/experienced any lags/slowdowns when collapsing a folder. Also made a couple of stress tests to check how much the plugin can handle.
I'll close this issue, but if the problem further persists, and you assume that it's the "auto folder collapse" plugins fault, do not hesitate to open an issue👍
Regards
Dario


Limited exception to take only Interrupted and ExecutionExceptions.

Description
Limiting UncheckedInterruptedException only to take InterruptedException and ExecutionException.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

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


Phlow: make it possible to switch displayed objects in individual composed tools

In this example, both Phlow tools share same number:

Explanation:


Does this limitation also apply for Free tier.? cause i am facing same issues with device twin tag that occurs with basic tier?

I am using Message enrichment in Free tier of IoT Hub and adding device twig tag property called "Location".
when I try to use it in Azure stream analytics / in backend application, I get string "$twin.tags.Location" instead of actual value.
I have set device twin as
  "tags": {
    "Location": {
      "building": "43",
      "floor": "1",
      "XCor": "150",
      "YCor": "200"
    }
}

my understanding is free tier is in standard tier, and it should support it? Can you please clarify.?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 09122ce7-4c60-89f8-205f-a9f0a4796fe7
Version Independent ID: 860539b6-44f5-5d09-b371-02864d4366d2
Content: Overview of Azure IoT Hub message enrichments
Content Source: articles/iot-hub/iot-hub-message-enrichments-overview.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

@omki12 Thanks for the feedback! We are currently investigating and will update you shortly.

@omki12  Could you please use $twin.tags.location instead of $twin.tags.Location and see if that makes any difference?
These are the current limitations.

You can add up to 10 enrichments per IoT Hub for those hubs in the standard or basic tier. For IoT Hubs in the free tier, you can add up to 2 enrichments.

In some cases, if you are applying an enrichment with a value set to a tag or property in the device twin, the value will be stamped as a string value. For example, if an enrichment value is set to $twin.tags.field, the messages will be stamped with the string "$twin.tags.field" rather than the value of that field from the twin. This happens in the following cases:

Your IoT Hub is in the basic tier. Basic tier IoT hubs do not support device twins.
Your IoT Hub is in the standard tier, but the device sending the message has no device twin.
Your IoT Hub is in the standard tier, but the device twin path used for the value of the enrichment does not exist. For example, if the enrichment value is set to $twin.tags.location, and the device twin does not have a location property under tags, the message is stamped with the string "$twin.tags.location".

Updates to a device twin can take up to five minutes to be reflected in the corresponding enrichment value.

The total message size, including the enrichments, can't exceed 256 KB. If a message size exceeds 256 KB, the IoT Hub will drop the message. You can use IoT Hub metrics to identify and debug errors when messages are dropped. For example, you can monitor d2c.telemetry.egress.invalid.

Message enrichments don't apply to digital twin change events (part of the IoT Plug and Play public preview).

I understand that you are referring to Free tier. To add more clarity regarding to your specific query, I am adding content author @robinsh for further review and update the doc as appropriate.

@omki12  Could you please use $twin.tags.location instead of $twin.tags.Location and see if that makes any difference?
I have assigned the issue to the content author @robinsh  to evaluate and update the doc as appropriate.

mmm...
here's the update.

It works for
"Location": "12"
but not for

"Location":{
      "XCor": "150"
    }

@omki12 Thanks for the confirmation.

#reassign v-gpettibone

Old issue. Customer using free tier can have up to 2 enrichments, but that doesn't seem to be the issue. Customer was advised to change Location to location. Not sure if he followed the advice or, if he did, whether it helped. No doc changes ("enhancements") are necessary. The docs are accurate. Closing.

#please-close


Firestore does not generate any callback/exception on attempting to upload data offline

Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository file a Github issue.

If you are filing an issue about FCM in the background make sure to read #4 and #89 first!

For general technical questions, post a question on StackOverflow tagged appropriately.
For general Firebase discussion, use the firebase-talk google group
For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel

Step 2: Describe your environment

Android device: Xiaomi Mi A
Android OS version: 7.1
Google Play Services version: not sure
Firebase/Play Services SDK version: Firestore 17.0.3

Step 3: Describe the problem:
Firestore does not generate any callback/exception on attempting to upload data when device is offline. Hence, I am not able to alert the user to check their internet connection and retry.
Neither the onCompleteListener, nor the OnFailureListener callbacks get triggered.
Steps to reproduce:
Write code to upload data to firestore:
FirebaseFirestore.getInstance().collection("users").document("abcd").set(user).addOnCompleteListener(...).addOnFailureListener(...);

Observed Results:
No callback/exception thrown
Expected Results:
onFailure callback or onComplete callback should be triggered and throw error or exception.

@AayushTaneja that's actually expected behavior.  Those listeners only fire when the write has actually been written to the backend (or failed to do so).  So when offline, they just never fire.
However when you write it's immediately written to the offline cache.  So if you attach a snapshot listener to the location you're writing, you can get confirmation of the offline write that way (you'll get a DocumentSnapshot with the pending changes indicator set to true).

Am making a get Query only AddOnSuccessListener get called, even when there is no network connection

I have the same issue as @Zedonboy but when reading some data, not writing. How are we supposed to distinguish lack of connection vs real empty result received from server?

@algrid you can check:
querySnapshot.getMetadata().isFromCache()

That will tell you if the result is from the server or not (true means it's a local offline result).
https://firebase.google.com/docs/reference/android/com/google/firebase/firestore/SnapshotMetadata.html#isFromCache()


Wait and use create-react-app@2

Things that create-react-app@2 solves:

Extending babel configuration to use babel-plugin-react-remove-properties that removes e.g. data-test react property in production

Did with 2e0092679a87354071e596e69ea92e7d248d63a8


Slow one snail image doesn't show up on drive forward block

See answer from Stack Exchange by Bartel De Brabandere on how to get GitHub to recognize a file name change that only differs by case