php_cs_fixer_on_save doesn't work

Hi,
Somehow my phpcs plugin stopped working.
I've turned on the debug and this is what I got.
[Phpcs] Linter found 0 errors
[Phpcs] Sniffer found 21 errors
reloading /Users/myuser/Code/laravelkr/app/Http/Controllers/HomeController.php
I have "php_cs_fixer_on_save": true in my config, but somehow the plugin doesn't run it.
How can I fix this?

Sorry, wrong repository;;;

yeah


Django Import Export not supporting bulk create

Is there any tool or solution available to be able to import large csv files using django import export.
Currently uploading a file greater than 35000 row takes too much time. And if not which functions might need to be tweaked ?

@aniket03 Yes you are right. Its taking 25 minutes to load in local server.


fix validation for conversion

Coverage increased (+0.09%) to 74.986% when pulling 9b68895503475075a01ae1ef5bf1540fdb67c8af on indriHutabalian:dev into 60af4cf8b0d2c7e4f5d523e3d0057e5883df3bbe on danliris:dev.


Triggers matched on out-of-context lemmas

Hello! I have a question about a potential QI (performance) issue in Verus.
Consider this snippet of Verus code:
spec fn abs(a: int) -> int
{
    if a >= 0 {
        a
    } else {
        -a
    }
}

#[verifier(nonlinear)]
proof fn equal_square_auto()
    ensures forall |a: int, b: int| a * a == b * b ==> abs(a) == abs(b)
{}

#[verifier(nonlinear)]
proof fn equal_square_auto2()
    ensures forall |a: int, b: int| a * a == b * b ==> abs(a) == abs(b)
{}

proof fn fact(a: int)
    requires a * a == 1
    ensures a == 1 || a == -1
{
    equal_square_auto();
    assert(abs(a) == abs(1));
}

where I have two auto lemmas equal_square_auto and equal_square_auto2 with exactly the same statement.
And then in the fact proof function I’m using only the first lemma to prove something.
However, running rust_verify with --profile-all shows that both lemmas get instantiated:
note: Observed 20 total instantiations of user-level quantifiers

note: Cost * Instantiations: 448 (Instantiated 16 times - 80% of the total, cost 28) top 1 of 2 user-level quantifiers.
  --> test.rs:20:56
   |
20 |     ensures forall |a: int, b: int| a * a == b * b ==> abs(a) == abs(b)
   |             -------------------------------------------^^^^^^----^^^^^^
   |             |
   |             Triggers selected for this quantifier

note: Cost * Instantiations: 16 (Instantiated 4 times - 20% of the total, cost 4) top 2 of 2 user-level quantifiers.
  --> test.rs:25:56
   |
25 |     ensures forall |a: int, b: int| a * a == b * b ==> abs(a) == abs(b)
   |             -------------------------------------------^^^^^^----^^^^^^
   |             |
   |             Triggers selected for this quantifier

Furthermore, when I look at the terms used for instantiation of the first lemma equal_square_auto, it actually uses the skolem constants of the second lemma equal_square_auto2 (which should be out of context).
Then I was trying to read the SMT query for this function, and the relevant parts look like this:
;; Function-Axioms crate::equal_square_auto
(declare-fun ens%equal_square_auto. () Bool)
(assert
 (= ens%equal_square_auto. (forall ((a~10$ Poly) (b~12$ Poly)) (!
    (=>
     ...
     (=>
      (= (Mul (%I a~10$) (%I a~10$)) (Mul (%I b~12$) (%I b~12$)))
      (= (abs.? a~10$) (abs.? b~12$))
    ))
    :pattern ((abs.? a~10$) (abs.? b~12$))
    :qid user_crate__equal_square_auto_0
    :skolemid skolem_user_crate__equal_square_auto_0
))))

;; Function-Axioms crate::equal_square_auto2
(declare-fun ens%equal_square_auto2. () Bool)
(assert
 (= ens%equal_square_auto2. (forall ((a~10$ Poly) (b~12$ Poly)) (!
    (=>
     ...
     (=>
      (= (Mul (%I a~10$) (%I a~10$)) (Mul (%I b~12$) (%I b~12$)))
      (= (abs.? a~10$) (abs.? b~12$))
    ))
    :pattern ((abs.? a~10$) (abs.? b~12$))
    :qid user_crate__equal_square_auto2_1
    :skolemid skolem_user_crate__equal_square_auto2_1
))))

; the actual VC
(assert
  (=>
   %%query%%
   (not (=>
     ens%equal_square_auto.
     ....

I think what’s happening here is that Z3 somehow matched the patterns abs(...) of the first lemma on the subterms of the skolemized version of the second (unused) lemma.

Is it possible this is related to this Z3 discussion/fix?  For example, if you rename the quantified variables in equal_square_auto2, does the issue persist?

@parno Hmm it does seem like a similar issue. However, changing the variable names didn't help in my case: lemma 1 still instantiates on the subterms of lemma 2, and lemma 2 also gets instantiated on a and 1 (appearing in fact).
If I just change the formula of lemma 2 slightly, like to the following
#[verifier(nonlinear)]
proof fn equal_square_auto()
    ensures forall |a: int, b: int| a * a == b * b ==> abs(a) == abs(b)
{}

#[verifier(nonlinear)]
proof fn equal_square_auto2()
    ensures forall |c: int, d: int| c * c * c == d * d * d ==> abs(c) == abs(d)
{}

Then the second kind of instantiation (lemma 2 instantiating on terms in fact) does not happen anymore, but the first kind still happens.

I was wondering if a potential solution is to just modify all definition of ensure clauses to use define-fun's. For example:
(define-fun ens%equal_square_auto2. () Bool (forall ((a~10$ Poly) (b~12$ Poly)) (!
    (=>
     ...
     (=>
      (= (Mul (%I a~10$) (%I a~10$)) (Mul (%I b~12$) (%I b~12$)))
      (= (abs.? a~10$) (abs.? b~12$))
    ))
    :pattern ((abs.? a~10$) (abs.? b~12$))
    :qid user_crate__equal_square_auto2_1
    :skolemid skolem_user_crate__equal_square_auto2_1
)))

I was under the impression that z3 unfolds these macros very early, so maybe that would avoid the duplicated quantifiers to even appear in the goal.

I was wondering if a potential solution is to just modify all definitions of ensure clauses to use define-fun

Out of curiosity, does the problem go away if you apply that idea to ens%equal_square_auto and ens%equal_square_auto2?

Yes it does work in my case. The only instantiations after the fix were lemma 1 applied on terms in fact (a and 1).

Interesting!  Thanks for trying the experiment.  @Chris-Hawblitzel Can you tell us more about the tradeoffs of using declare-fun+assert to define the ensures, vs. using define-fun?  We could also test it empirically to see what happens.

Thanks for raising this; this is a known issue for functions with 0 arguments.  The SMT encoding should either treat these specially or add a dummy argument.

Try it now.

Thanks! I can confirm this fixed it in my case.


[Feature] Datatypes of metric in resulting dataframe should always return numeric

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Some partners have raised concerns about needing to know the datatype of the metric before visualizing it. For their purposes, we need to ensure consistency that the metric is always returned as a numeric.
We already coalesce to 0 but there might be some odd behavior around min and max with date fields. If we see that the metric type isn't a numeric, we should fail loudly.
Describe alternatives you've considered
No response
Who will this benefit?
Everyone who likes consistency
Are you interested in contributing this feature?
You betcha
Anything else?
No response

So it looks like this is less of a concern than I thought - if the data type is non numeric then it has a failure at runtime.

Closing because of above data tests


Fixed DebuggerDisplay in DefaultTagHelperContent

Also refactored it in few other places

#1580
@rynowak @NTaylorMullen

🆙 📅


Errors/Incorrect generation when the filters value is zero "0"

To Reproduce:

Open the App.
Change the value of any filter to zero "0" and click generate.
The value is not generated or the generated value is correct.

When will the release be?

Fixed.


Bump concurrency and limits for javabuilder-test

Bumping up the hourly/daily limits and concurrency on the javabuilder-test stack a bit so that multiple developers can develop against it without too easily running into throttling or rate limiting. I matched the daily and hourly limits to the adhoc config, but the concurrency is just a ballpark estimate based on how many developers might be working on it concurrently, so let me know if these should be adjusted.
For reference - this change makes the javabuilder-test stack the default for local development, so we would expect its usage to increase.

No special deploy steps required for this. Once merged the pipeline will use the new values when deploying to Test.


Build Compound v3 subgraph

Closing this since QA is being tracked here: https://github.com/messari/subgraphs/issues/1545


add a few words

this is was merged in manually.  Sorry for the delay here... actually you need to add these in by editing a different source file.  In the future just file issues (not PR), and we'll sort it work.
thanks so much.


Merge

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1578 of 1594 (99.0%)  changed or added relevant lines in 44 files are covered.
20 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.01%) to 97.898%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/src/plan/planner.rs
131
132
99.24%

core/src/result.rs
4
5
80.0%

core/src/executor/fetch.rs
21
23
91.3%

core/src/executor/aggregate/state.rs
0
3
0.0%

core/src/executor/alter/table.rs
55
58
94.83%

core/src/plan/context.rs
18
21
85.71%

storages/sled-storage/src/store.rs
21
24
87.5%

Files with Coverage Reduction
New Missed Lines
%

core/src/executor/fetch.rs
1
93.7%

test-suite/src/tester.rs
19
88.89%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
30741

Relevant Lines:
31401

💛  - Coveralls


TypeError: Converting circular structure to JSON

TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'BufferImageSource'
    |     property '_events' -> object with constructor 'Events'
    |     property 'resize' -> object with constructor 'Array'
    |     ...
    |     property 'context' -> object with constructor 'Texture'
    --- property '_source' closes the circle
    at JSON.stringify (<anonymous>)
    at o._stringifyDescriptor (webgpu_inspector.js:1:49239)
    at o._recordCommand (webgpu_inspector.js:1:50652)
    at o._postMethodCall (webgpu_inspector.js:1:41320)
    at t.emit (webgpu_inspector.js:1:906)
    at GPUDevice.createSampler (webgpu_inspector.js:1:12318)
    at GpuTextureSystem._initSampler (WebGPURenderer-cc3732e7.js:1818:63)
    at GpuTextureSystem.getGpuSampler (WebGPURenderer-cc3732e7.js:1822:59)
    at BindGroupSystem._createBindGroup (WebGPURenderer-cc3732e7.js:105:40)
    at BindGroupSystem.getBindGroup (WebGPURenderer-cc3732e7.js:69:61)

This happens when trying to debug anything on https://dubbelboer.com/sillysky/
WebGPU Inspector: 0.0.9
OS: MacOS Sonoma 14.4
Browser: Chrome 123.0.6312.59 (Official Build) (arm64)

I have that fixed in the github version. I'll get the Chrome store version updated.

Chrome store update has been requested. Usually takes a day or so for them to publish. Will be version 0.1.0 when they do.

Of course I fix a couple more issues inspecting that game after  I submit the chrome store update. Guess I'll have to do another release soon.

This was fixed 👍 . Didn't get a change to test it earlier.


TypeError: undefined is not an object (evaluating 'process.version.split'), and Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.

Description

Version
0.67.4
Output of npx react-native info
Node: v16.15.0
react: 17.0.2
react-dom: 17.0.2
react-native: 0.67.4
Steps to reproduce
1.npm install
2.npm run android
i found the some solution but it not work for me
ex:
//
var process = require("process");   // THIS LINE
var pna = require('process-nextick-args');
//
Snack, code example, screenshot, or link to a repository
Snack, code example, screenshot, or link to a repository

Facing the same error. Has anyone found a solution?


Switch to AdoptOpenJDK-based JVM base image

The background here is that - again - the Debian OpenJDK builds turn out
to have the wrong version numbers on them, with the package being
stamped as a java update that was released after the package was built.
See https://mail.openjdk.java.net/pipermail/jdk8u-dev/2019-May/009330.html
We don't use the Debian packages, we use Alpine, but inspecting the
provenance of the Alpine OpenKJDK packaging, it seems to suffer from the same
issue. The current latest alpine OpenJDK has versioning that does not
seem to line up. At the very least, the source of those builds is of a
similar kind to Debian.
This moves our base image to images provided by AdoptOpenJDK, a well
regarded source of up-to-date OpenJDK builds. The base image remains
Alpine Linux.

Note that I'm not changing below Neo4j 3.1; those images are not alpine based.. and only 3.4 and 3.5 are officially supported, so I don't think that should be a problem


feat:change comments

The comments at this position does not match the actual result

I agree with your viewpoint. However, retaining comments can help readers better understand the logic of this code,I am available to assist you in either refining the comments or deleting them.


Adding Feature of Share Images and Solving the Bug in Tag Division of…

What does this PR do?
The search page lacks responsiveness because the tags section overflows the web page. I am addressing this issue by applying the overflow-x-scroll property to enable horizontal scrolling.
And Adding the Feature of Sharing Images using react-share and headless UI and also Rewriting the Router.
Related Issue
This PR Solves issue #208
Changes
This PR Resolves the Search Page Tag Division Overflow and Adds the Feature of Sharing Images on Social Media
Demo Video
https://github.com/Vijaykv5/SnapGrid/assets/112365664/5e402312-5fd3-43e0-b310-b8e19faa9c2a
https://github.com/Vijaykv5/SnapGrid/assets/112365664/b70f4174-b30a-48c3-acd7-005d60bf8245
Checklist

[x] I have read and followed the contributing guidelines.
[x] My code follows the project's coding style and conventions.
[ ] I have added unit tests (if applicable) to ensure the code works as expected.
[ ] I have updated the project documentation (if necessary).

By submitting this PR, I confirm that:

[x] I have reviewed my code and believe it is ready for merging.
[x] I understand that this PR may be subject to review and changes.
[x] I agree to abide by the code of conduct and contributing guidelines of this project.

Hey @Vijaykv5 please checkout this PR

Thanks for your contribution @JavidSumra


Update README to match values.yaml

Readme doesn't reflect correctly default values contained on values.yaml

/joke

/ok-to-test

I'd say that wasn't my fault :stuck_out_tongue:

/lgtm


Fix azure environment support

ensure that env var AZURE_ENVIRONMENT is set to the parsed cloud so that the Azure REST authoriser is contacting the correct endpoint url

fixes https://github.com/vmware-tanzu/velero/issues/3440


Problem: travis doesn't run against new directory layout

Solution: refactor nasty travis scripts
Please don't merge, debugging nasty travis scripts

@sorpaas as soon as it goes green it's good to merge.


Scopes enhancements

Mapper now defaults to entities' scopes instead of empty array. The method scopes was already defined in Entity, but I don't think it was used from what I saw in the code.
Scopes can be used from relations:
//Get post with id 1, then its comments, then just yesterday's.
$yesterday_comments = $mapper->get(1)->comments->yesterday();

Looks good. I'll check the noQuote issue in a separate issue/PR. :+1:


Index out of range exception

no matter what settings i use i get this error
IndexOutOfRangeException: Index was outside the bounds of the array.
d4rkAvatarOptimizer+<>c__DisplayClass119_3.<CombineSkinnedMeshes>b__18 (System.Int32 i) (at Packages/d4rkpl4y3r.d4rkavataroptimizer/Editor/d4rkAvatarOptimizer.cs:2531)
System.Linq.Enumerable+SelectIPartitionIterator`2[TSource,TResult].PreallocatingToArray (System.Int32 count) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
System.Linq.Enumerable+SelectIPartitionIterator`2[TSource,TResult].ToArray () (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
System.Linq.Enumerable.ToArray[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
d4rkAvatarOptimizer.CombineSkinnedMeshes () (at Packages/d4rkpl4y3r.d4rkavataroptimizer/Editor/d4rkAvatarOptimizer.cs:2530)
d4rkAvatarOptimizer.Optimize () (at Packages/d4rkpl4y3r.d4rkavataroptimizer/Editor/d4rkAvatarOptimizer.cs:95)
d4rkAvatarOptimizerEditor.OnInspectorGUI () (at Packages/d4rkpl4y3r.d4rkavataroptimizer/Editor/d4rkAvatarOptimizerEditor.cs:959)
UnityEditor.UIElements.InspectorElement+<>c__DisplayClass58_0.<CreateIMGUIInspectorFromEditor>b__0 () (at <a259d3c004024353a2c217da97495055>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

From the looks of this error message it seems like you have a skinned mesh that is in a faulty state. Specifically one that has a mismatched amount of bones and bindposes.
To find which mesh is the culprit you can use the exclusion list.

Put all skinned meshes in the exclusion list. Now it should finish the optimization without error but also don't optimize anything really.
Remove 1 of the meshes and click optimize again.
Repeat the previous step until the error appears again. Then you know which mesh is the problem.
Tbh I don't know how to really fix this bug as having a differently sided bindpose array from the bone array makes no sense.

well even after excluding all the meshes im left with this error
IndexOutOfRangeException: Index was outside the bounds of the array.
d4rkAvatarOptimizerEditor.OnInspectorGUI () (at Packages/d4rkpl4y3r.d4rkavataroptimizer/Editor/d4rkAvatarOptimizerEditor.cs:1005)
UnityEditor.UIElements.InspectorElement+<>c__DisplayClass58_0.<CreateIMGUIInspectorFromEditor>b__0 () (at <a259d3c004024353a2c217da97495055>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Actually it spamming the console aswell with the message

For the second issue, I don't know what causes it. My best guess was meshes with 0 materials but that doesn't reproduce the error on my end.

I've added some extra guarding code without being able to reproduce the original issue. If you have time it would be nice if you could check if the problem still persists in v2.2.0
The secondary issue should be fixed in the newest version as I could reproduce it eventually.


Revert "Consolidate Container Properties cache in Client Instance"

Reverts Azure/azure-sdk-for-python#35293
Will be added later with container recreate fix

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


The Page.Content().S don't have any space character

From code of https://github.com/rsc/pdf/blob/master/page.go#L421
I see you skip all   character, why do you do it. Not sure I got your idea but when reading all text form pdf, we can't use the content and the result's very useless.

Thank you for pointing this out!
After commenting out the if on Line 421 out and then adding one additional space when Y changes from one character to the next in my loop over pages & text, I was able to get basically what I was shooting for all along: text [cleanly] extracted from PDF.
So I'm curious as well: why exclude spaces?
I don't imagine it was a mistake and would speculate that spaces weren't the goal of the package... but... having spaces is supremely helpful when trying to work at the "word" level.
At the very least, I'm going to fork this repo now and would also be happy to submit a pull request with these changes in the near future. Only problem is that this fundamentally changes the output of the package and I'm not sure if this is something people would be happy about (but I sure would be).

Thanks @puddingfactory, I'm very hapy with your library 👍


TEST ONLY - Reconnect State Machine 5 State Variant

Overhauled the ReconnectStage to use a 5-state state machine in order to fix known issues. Among the changes:

Auto-reconnect and SAS renewals should no longer cause problems if one or the other is turned off
Operations now fail if they require a connection, and one cannot be automatically established
All user-initiated actions should now return errors in case of failure rather than any kind of indefinite retry
Added locking for thread protection in the ReconnectStage
Created completely separate flows for automatic reconnection vs other connections
Added more explicitness in conditional logic and improved documentation for clarity

/azp run Azure.azure-iot-sdk-python-horton-e2e (build_linux_amd64 py27)

/azp run

            # above to run.  Just because we just connected, it doesn't mean the connection won't drop

Comment needs updating.

Refers to: azure-iot-device/azure/iot/device/common/pipeline/pipeline_stages_base.py:483 in e327bce. [](commit_id = e327bce2a2f31298b50b9587cab9681bcd8442a2, deletion_comment = False)


Chore: Enable builtin pre-commit checks

Enables a selection of builtin pre-commit checks, which are fast to run and prevent some common issues.
Seeing as we have already enabled pre-commit, this seems like a reasonably unintrusive ci change.

I note that the codecov patch target is missed by this PR. I feel comfortable in this instance, as the changes are purely are made by the automatic end-of-file-fixer check and have no functional consequences. However, it's does highlight the gaps in the test suite that we can hope to close over time.


JSONDecodeError when inserting

Describe the bug
I'm getting a JSON Decode Error in SyncQueryRequestBuilder.execute. Any idea what happened?
Exact error message:
File ~/.asdf/installs/python/3.11.0/lib/python3.11/site-packages/postgrest/_sync/request_builder.py:62, in SyncQueryRequestBuilder.execute(self)
     53 r = self.session.request(
     54     self.http_method,
     55     self.path,
   (...)
     58     headers=self.headers,
     59 )
     61 try:
---> 62     return APIResponse.from_http_request_response(r)
     63 except ValidationError as e:
     64     raise APIError(r.json()) from e
...
    354 except StopIteration as err:
--> 355     raise JSONDecodeError("Expecting value", s, err.value) from None
    356 return obj, end

JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce
Steps to reproduce the behavior:
import os

from supabase import create_client, Client

url: str = os.getenv("SUPABASE_URL")
key: str = os.getenv("SUPABASE_KEY")
supabase: Client = create_client(url, key)

def storeRepos(toAddRepos):

    #fetch current repos
    supabaseCurrentRepos = supabase.table("repos").select("name").execute()
    currentRepos = [r["name"] for r in supabaseCurrentRepos.data]

    for repo in toAddRepos:
        # check if already exist
        if currentRepos.count(repo["name"]) == 0:
            repo["scraped"] = False
            supabase.table("repos").insert(repo).execute()
            currentRepos.append(repo["name"])

storeRepos(testrepo)

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS using Python 3.11.0

Additional context
Add any other context about the problem here.

Hey,
Just tested insert and it seems to work now - this was probably caused by the way Python3.11 handles stringification of Enums leading to an invalid query.
Going to close this issue but feel free to reopen if there are issues


Strip internals in declarations

This will remove @internal functions in the public packages.
The reason for moving the core build to the end is that the core build rebuilds the core package, and if it is built first, other packages depending on core will faill if they use internals.

Reviewer - this PR has made changes to one or more package.json files.

Snapshot stored with reference name:
refs/pull/14982/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14982/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14982/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14982/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14982/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14982/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14982/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14982/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14982/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14982/merge/testResults/webgpuplaywright/index.html


scipy.stats "setting array element with a sequence" error

When I try to run the following snippet:
from autograd import grad
from autograd import numpy as np
from autograd import scipy

n_dimensions = 2
n_examples = 1000

def linear_regression_log_likelihood(beta, x, y):
    predictions = x.dot(beta)
    return scipy.stats.norm.logpdf(y, loc=predictions, scale=1.).sum(-1)

fake_args = [np.zeros(n_dimensions), np.zeros([n_examples, n_dimensions]),
np.zeros(n_examples)]
grad(linear_regression_log_joint)(*fake_args)

I get this error:
Traceback (most recent call last):
  File "/tmp/test.py", line 14, in <module>
    grad(linear_regression_log_joint)(*fake_args)
  File "/usr/local/lib/python2.7/site-packages/autograd/wrap_util.py", line 20, in nary_f
    return unary_operator(unary_f, x, *nary_op_args, **nary_op_kwargs)
  File "/usr/local/lib/python2.7/site-packages/autograd/differential_operators.py", line 24, in grad
    vjp, ans = _make_vjp(fun, x)
  File "/usr/local/lib/python2.7/site-packages/autograd/core.py", line 10, in make_vjp
    end_value, end_node =  trace(start_node, fun, x)
  File "/usr/local/lib/python2.7/site-packages/autograd/tracer.py", line 10, in trace
    end_box = fun(start_box)
  File "/usr/local/lib/python2.7/site-packages/autograd/wrap_util.py", line 15, in unary_f
    return fun(*subargs, **kwargs)
  File "/tmp/test.py", line 11, in linear_regression_log_joint
    return scipy.stats.norm.logpdf(y, loc=predictions, scale=1.).sum(-1)
  File "/usr/local/lib/python2.7/site-packages/autograd/tracer.py", line 48, in f_wrapped
    return f_raw(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/scipy/stats/_distn_infrastructure.py", line 1691, in logpdf
    x = np.asarray((x - loc)/scale, dtype=dtyp)
  File "/usr/local/lib/python2.7/site-packages/numpy/core/numeric.py", line 492, in asarray
    return array(a, dtype, copy=False, order=order)
ValueError: setting an array element with a sequence.

This can be fixed by replacing
scipy.stats.norm.logpdf(y, loc=predictions, scale=1.)
with
scipy.stats.norm.logpdf(y, predictions, scale=1.)
Right now autograd doesn't differentiate through named arguments, unfortunately.


help

how do i locally deploy?

reopening because i still need help

resolved—thanks @kaleb!

resolved— thanks @ teero!


[labs/context] Add a contextProvider directive to support providing to part of an element's subtree

An element may want to provide different context values to different parts of its subtree. Consider, for example, a context that provides styling data to elements inside a custom element like a dialog. The element might want style various different elements like buttons inside it differently via this styling context data.
This could be addressed via a contextProvider element directive. It would be used something like this:
<my-dialog id="favorites" ${contextProvider({context: styling, value: favoritesCss})}>...</my-dialog>
<my-dialog id="settings" ${contextProvider({context: styling, value: settingsCss})}>...</my-dialog>

@benjamind and I should document why this was left out of v1 (that might be a good year for an ADR process).
The reason is that because rendering is async, and context can be used to provide values to light DOM children, you can get in a race condition where light DOM children fire context request before a parent has rendered and set up the context provider directive.
A controller is initialized earlier and avoids this. It could then wait to see what slot the request congress from.
We do know that this isn't a problem for shadow subtrees.

Closing this as not planned because of the race condition with initial render.


Using deprecated patchesStrategicMerge in kustomize files

What would you like to be cleaned:
Use patches instead of patchesStrategicMerge.
Why is this needed:
We are getting this warning when using kustomize:
# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.

/assign


Can't run the app

Hey Anton,
This project looks really good, and I would like to try it out. It seems something is wrong and I can't make the app work. I see the same behavior for both the compiled version and the one I compile from the source. I'm running Sierra 10.12.6.
Do you have any idea what am I doing wrong? Thanks!

Hi @vst-ableton, thanks for your feedback. It may be unclear from readme, but to be able to see something you need to open the app, so you see it in the status bar and then run snapshot test. After the tests are done and if you have failed tests or recorded images the icon of the FBSnapshotsViewer will become red and if you click you'll see the pop up with information.
Let me know of that helped 😄

All clear now! Thank you ;-)


Allow cmd to be customized in settings

I have phpunit installed globally, and I would always like the phpunit cmd to be used when running the tests even if my vendor/bin/phpunit exists. Can that be added as a setting?

How about an setting: phpunit.cmd?
Currently we figure out the command to use by checking if vendor/bin/phpunit exists relative to the phpunit.xml configuration file, if not, then we fallback to what would be the global command phpunit.
So, if phpunit.cmd is set that will be used otherwise the default is to check for a composer installed phpunit, or default to the global one.
You will then be able to configure it globally or project specific:
Project > Edit Project
{
    "settings": {
        "phpunit.save_all_on_run": false
    }
}

Or maybe easier, add the option phpunit.composer_support which defaults to true?

I went with the setting phpunit.composer.
    // Enable/disable composer installed PHPUnit support.
    //
    // For example, if composer installed PHPUnit exists then it is used as the
    // command to run PHPUnit, otherwise defaults to the command "phpunit".
    "phpunit.composer": true,

Fast! Awesome, ty :)


RFC: release 0.1.0 stable

Many public projects (recOrder, VisCy, Mantis, DaXi etc) depend on the current API. While we have an ongoing effort to introduce breaking changes with UAPI, it may be of value for downstream projects to release the current API under v0.1.0 stable and release UAPI with v0.2.0.

@mattersoflight any thoughts?

https://pypi.org/project/iohub/0.1.0/


add in:header tag cache for http request to enhance performance

https://github.com/gogf/gf/issues/2060
顺便修一个bug https://github.com/gogf/gf/issues/2904

Codecov Report
Patch coverage: 83.90% and project coverage change: +0.10% :tada:

Comparison is base (7d4c59a) 79.16% compared to head (7525310) 79.26%.
Report is 2 commits behind head on master.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2923      +/-   ##
==========================================
+ Coverage   79.16%   79.26%   +0.10%
==========================================
  Files         638      632       -6
  Lines       52557    52366     -191
==========================================
- Hits        41608    41510      -98
+ Misses       8884     8803      -81
+ Partials     2065     2053      -12

Flag
Coverage Δ

go-1.18-386
79.23% <83.90%> (+<0.01%)
:arrow_up:

go-1.18-amd64
79.23% <83.90%> (+<0.01%)
:arrow_up:

go-1.19-386
?

go-1.19-amd64
?

go-1.20-386
?

go-1.20-amd64
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

net/ghttp/ghttp.go
100.00% <ø> (ø)

net/ghttp/ghttp_request_middleware.go
84.21% <66.66%> (+1.32%)
:arrow_up:

net/ghttp/ghttp_server_service_handler.go
64.70% <73.91%> (+1.44%)
:arrow_up:

net/ghttp/ghttp_request_param_request.go
91.75% <89.09%> (+0.58%)
:arrow_up:

os/gstructs/gstructs_field_tag.go
100.00% <100.00%> (ø)

... and 18 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@hailaz CI失败了，请查看一下呢。另外这提交的修改代码量有点多，能否把bug修复和改进分成两个pr方便review。

@hailaz CI失败了，请查看一下呢。另外这提交的修改代码量有点多，能否把bug修复和改进分成两个pr方便review。

@gqcn 先看https://github.com/gogf/gf/pull/2931


Fixed #25138 -- Added view_decorator for CBVs.

django.views.generic.view_decorator takes a function decorator, converts it to a method decorator using django.utils.decorators.method_decorator, and applies it to dispatch method on the given class. For example:
from django.views.generic import TemplateView, view_decorator
from django.contrib.auth.decorators import login_required

@view_decorator(login_required)
class ProtectedView(TemplateView):
    template_name = 'secret.html'

Trac: https://code.djangoproject.com/ticket/25138

Closing. See Trac for details.


Dav1dMCDSPContext: Deduplicate and anonymize function pointers

The various callback functions (for both asm routines and the C/Rust fallback fns) are now declared using macros.
Since all that's left in the mc_tmpl_*.rs files are the init fns, I'm gonna follow this PR up with one that deduplicates those and removes the Option wrappers around the fn pointer types.

Oh wait, just realized I still haven't deleted the duplicate instances of Dav1dMCDSPContext 🤦 Fixing that now.


force_polling and ignore_permission_denied are not working together

Description
Hi there,
I'm using watchfiles in production code, and I've found some strange behaviour depending on whether or not the force_polling and ignore_permission_denied options are used.
I will describe all the scenarios, changing those two options when needed.
1) force_polling = False, ignore_permission_denied = False
If force_polling is not activated, and a directory containing files is copied into the watched folder, only the top directory is notified. Even with recursive option activated (by default).
When the watcher is running, in an other terminal:
➜  /tmp mkdir /TEST
➜  /tmp touch TEST/file.txt
➜  /tmp cp -r TEST watcher/

Result:
watcher: INotifyWatcher { channel: Sender { .. }, waker: Waker { inner: Waker { waker: WakerInternal { fd: File { fd: 8, path: "anon_inode:[eventfd]", read: true, write: true } } } } }
raw-event=Event { kind: Create(Folder), paths: ["/tmp/watcher/TEST"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=1
Change.added /tmp/watcher/TEST

➜  /tmp ls watcher/*/*
➜  /tmp watcher/TEST/file.txt

2) force_polling = True, ignore_permission_denied = False
The scenario 1) with force_polling activated:
Result:
watcher: PollWatcher { watches: Mutex { data: {"/tmp/watcher": WatchData { root: "/tmp/watcher", is_recursive: true, all_path_data: {"/tmp/watcher": PathData { mtime:<PHONE_NUMBER>, hash: None, last_check: Instant { tv_sec: 172960, tv_nsec: 959087850 } }} }}, poisoned: false, .. }, data_builder: Mutex { data: DataBuilder { build_hasher: None, now: Instant { tv_sec: 172960, tv_nsec: 959087850 } }, poisoned: false, .. }, want_to_stop: false, message_channel: Sender { .. }, delay: Some(300ms) }
raw-event=Event { kind: Modify(Metadata(WriteTime)), paths: ["/tmp/watcher"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=2
raw-event=Event { kind: Create(Any), paths: ["/tmp/watcher/TEST"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=1
raw-event=Event { kind: Create(Any), paths: ["/tmp/watcher/TEST/file.txt"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=1
Change.added /tmp/watcher/TEST/file.txt
Change.modified /tmp/watcher
Change.added /tmp/watcher/TEST

➜  /tmp ls watcher/*/*
➜  /tmp watcher/TEST/file.txt

First question, how to achieve this result with force_polling deactivated?
3) force_polling = True, ignore_permission_denied = True
Now the fun part, let's say that we want to copy a directory with some bad permissions into the watcher, when force_polling = True AND ignore_permission_denied = True. I copy the directory using sudo, as our users are on Windows/MAC, and they copy the directories/files via direct transfer - so they don't care about permissions:
➜  /tmp sudo chmod u-rwx TEST2
➜  /tmp ls -la | grep TEST2
d---rwxr-x  2 user user    4096 août   7 17:36 TEST2
➜  /tmp sudo cp -r TEST2 watcher/

The permission error is not ignored at all:
watcher: PollWatcher { watches: Mutex { data: {"/tmp/watcher": WatchData { root: "/tmp/watcher", is_recursive: true, all_path_data: {"/tmp/watcher": PathData { mtime:<PHONE_NUMBER>, hash: None, last_check: Instant { tv_sec: 173190, tv_nsec: 820411807 } }, "/tmp/watcher/TEST": PathData { mtime:<PHONE_NUMBER>, hash: None, last_check: Instant { tv_sec: 173190, tv_nsec: 820411807 } }, "/tmp/watcher/TEST/file.txt": PathData { mtime:<PHONE_NUMBER>, hash: None, last_check: Instant { tv_sec: 173190, tv_nsec: 820411807 } }} }}, poisoned: false, .. }, data_builder: Mutex { data: DataBuilder { build_hasher: None, now: Instant { tv_sec: 173190, tv_nsec: 820411807 } }, poisoned: false, .. }, want_to_stop: false, message_channel: Sender { .. }, delay: Some(300ms) }
raw-event=Event { kind: Modify(Metadata(WriteTime)), paths: ["/tmp/watcher"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=2
raw-event=Event { kind: Create(Any), paths: ["/tmp/watcher/TEST2"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None } change=1
Traceback (most recent call last):
  File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/watchfiles/main.py", line 253, in awatch
    raw_changes = await anyio.to_thread.run_sync(watcher.watch, debounce, step, timeout, stop_event_)
  File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
  File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2177, in run_sync_in_worker_thread
    return await future
  File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 859, in run
    result = context.run(func, *args)
_rust_notify.WatchfilesRustInternalError: error in underlying watcher: IO error for operation on /tmp/watcher/TEST2: Permission denied (os error 13)

During handling of the above exception, another exception occurred:

  + Exception Group Traceback (most recent call last):
  |   File "/home/mathieu/PerfectMemory/Pmscs/nascar/src/pmsc/bin/test_watcher", line 32, in <module>
  |     asyncio.run(main())
  |   File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
  |     return loop.run_until_complete(main)
  |   File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
  |     return future.result()
  |   File "/home/mathieu/PerfectMemory/Pmscs/nascar/src/pmsc/bin/test_watcher", line 27, in main
  |     await asyncio.gather(task_watcher)
  |   File "/home/mathieu/PerfectMemory/Pmscs/nascar/src/pmsc/bin/test_watcher", line 11, in run
  |     async for changes in awatch(
  |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/watchfiles/main.py", line 251, in awatch
  |     async with anyio.create_task_group() as tg:
  |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 680, in __aexit__
  |     raise BaseExceptionGroup(
  | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/watchfiles/main.py", line 253, in awatch
    |     raw_changes = await anyio.to_thread.run_sync(watcher.watch, debounce, step, timeout, stop_event_)
    |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
    |     return await get_async_backend().run_sync_in_worker_thread(
    |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2177, in run_sync_in_worker_thread
    |     return await future
    |   File "/home/mathieu/.cache/pypoetry/virtualenvs/nascar-services-DFvlMQM0-py3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 859, in run
    |     result = context.run(func, *args)
    | _rust_notify.WatchfilesRustInternalError: error in underlying watcher: IO error for operation on /tmp/watcher/TEST2: Permission denied (os error 13)
    +------------------------------------

I know this is a specific use case, but this is what we got on our end with final users...
Of course, when force_polling is False, the permission error is completely ignored.
My final questions:
How can I achieve the result of having a force_polling + ignore_permission_denied that actually works?
If not possible, is there a way to catch the exception, without crashing the watcher?
Example Code
import asyncio
from watchfiles import awatch

DIR_TO_WATCH = '/tmp/watcher'

async def run(stop_event, *args):

    async for changes in awatch(
        DIR_TO_WATCH,
        debug=True,
        force_polling=False,  # will change depending on explained scenarios
        ignore_permission_denied=False,  # will change depending on explained scenarios
        stop_event=stop_event
    ):
        for change in changes:
            print(change[0], change[1])

async def main():
    stop_event = asyncio.Event()

    task_watcher = asyncio.create_task(run(stop_event))
    await asyncio.gather(task_watcher)

    stop_event.set()

if __name__ == "__main__":
    asyncio.run(main())

Watchfiles Output
No response
Operating System & Architecture
Linux-5.15.0-56-generic-x86_64-with-glibc2.35
#62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022
Environment
No response
Python & Watchfiles Version
python: 3.10.12 (main, Mar 22 2024, 16:50:05) [GCC 11.4.0], watchfiles: 0.22.0
Rust & Cargo Version
No response

Downgrading to watchfiles 0.21.0 fixed the issue. Thank you.


Azure cloud service deployment template fails staging deployment when diagnostics is used

(Brought this issue over from the xplat agent repo)
kaspernortoft commented an hour ago
The Azure cloud service deployment script fails the second deployment if the service uses the diagnostics extension and is swapped from staging to production.
ConflictError: The extension ID RoleName-PaaSDiagnostics-Staging-Ext-0 is already in use for this deployment.
It seems possible to use the Set-AzureServiceDiagnosticsExtension instead to set the diagnostics, but it is pretty slow
Thanks for reporting this issue.  I'll investigate this.  If possible, could you set the "system.debug" variable to true on your definition (on the Variables tab), run that definition again, then send me downloaded logs?  The Azure PS cmdlets will write a lot of diagnostics information that I can go through and see exactly where it's failing.

It looks like this issue was reported and fix very recently.
An initial report is at https://social.msdn.microsoft.com/Forums/en-US/5a37b1fc-86ec-4b26-be2e-75ab5360d20d/bug-with-diagnostics-extensions-in-azure-sdk-26-myrolepaasdiagnosticsstagingext0-is-already-in?forum=azureautomation.
A good explanation of the repro steps and the bug is at https://github.com/Azure/azure-powershell/pull/361 and the final pull request looks to have happened at https://github.com/Azure/azure-powershell/pull/466/files.
Once those changes get into an Azure PS cmdlet update, we can get them out on to the hosted pool.  Before then, if you've got your own Build agent, you can update to the version of the Azure PS cmdlets that have the fix (the Azure PS cmdlets changelog is at https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.txt and it doesn't look like the change has been released yet).

I'm using azure-powershell 0.93 cmdlets.
The New-AzureServiceDiagnosticsExtensionConfig ->  Set-AzureDeployment or New-AzureServiceDiagnosticsExtensionConfig -> Remove-AzureDeployment -> New-AzureDeployment fails.
If I use Set-AzureDeployment (without extensionConfiguration) -> Set-AzureServiceDiagnosticsExtension it seems to work.

Just for information we still have this issue with the August release of AzurePS (0.9.6).

They have released AzurePS 0.9.7 which fixes the issue. The hosted agents should also have this fix.

just updated azure ps to 0.9.7 and still running into the issue. agent version is 1.86


Set proper context in props that are functions

I'm trying to make two fields interdependent like this:
const Schemas = {};
Schemas.User= new SimpleSchema({
  name: { type: String },
  surname: {
    type: String,
    allowedValues(){
      if ( this.field('name').value === "Daniel" ) {
        return SomeCollection.find().fetch().map(obj => ...)
      }
    }
});

But it's not possible to use this.field and other function specefic to custom() inside allowedValues().
What I want: make allowedValues to depend on what the user put in the name field ( this.field('name').value === "Daniel" ). Or is it possible to use allowedValues inside custom()?
custom(){
  ...
  return allowedValues; // limit what the user can provide to the field.
}

The problem with this approach is that you don't really know why/when allowedValues is getting called. We can potentially change it to pass in the this.field context and such when validation is happening, but often allowedValues are used for other reasons outside of validating.
This could work outside of validation, if you're just getting the values for your own use. Something like this:
Schemas.User.get('surname', 'allowedValues', { name });

Where name is the value from the name field. The last arg is used as this within allowedValues function, so you could then do if (this.name === "Daniel").
To get it working as expected while validating, the simple answer is to pass the desired this context as the third argument here: https://github.com/aldeed/simple-schema-js/blob/master/package/lib/doValidation.js#L214
Currently the context object is created within validate function in that file (https://github.com/aldeed/simple-schema-js/blob/master/package/lib/doValidation.js#L82-L114) so it would need to be moved to be created earlier, before getDefinition is called. This may or may not be easy. I'll take a look at a pull request if anyone has time to get it working.

Hi, @aldeed  I actually need it to be done during/inside the validation. I've checked the source code you suggested, but couldn't find any way to achieve this without performing changes to the source code. I'm struggling to find a workaround for this. I even tried to use a Session variable as a container that will store the value of the name field inside a custom function with no positive result:
Outside my schema: Session.set('test', '');
Inside my schema:
custom(){
  if (this.isSet || !this.value === null || !this.value === "" || this.value) {
            Session.set('test', this.value);
        }
}

You'd have to pass in the value of the name field there, and you would call it wherever you need the allowedValues array.
That example is only if you are trying to get the list of allowed values for something other than when validating, for example for an options list in a form.
But if you want it to work when validating, then someone will need to do a pull request with the changes I mentioned.


PHP 8.2 with dependencies

PR Description
Ticket - https://spryker.atlassian.net/browse/SC-13160
Relation:

https://github.com/spryker-sdk/docker-new-relic/pull/1 (image spryker/newrelic-extension:<IP_ADDRESS>4-php8.2 should be available)
https://github.com/spryker/suite-nonsplit/pull/7765 (Nonsplit for QA)
https://github.com/spryker/spryker/pull/10121 - (Core PR)
https://github.com/spryker/docker-sdk/pull/323 - should be implemented

Changelog:

PHP 8.2
Blackfire: 1.86.4
Tideways: 5.5.14
NewRelic: <IP_ADDRESS>4
Composer: 2.5.5

Checklist

[x] I agree with the Code Contribution License Agreement in CONTRIBUTING.md

Hi @kalaputsik, could you please remove Alpine 3.14 from our list as Alpine 3.14 will be deprecated in 6 days?


Add the proto-ipv4 feature

Users should be able to choose to use smoltcp without IPv4 support.
Fixes: #76

I've revised required-features even further and added them upstream, so you can discard my commit here.

:+1: I'll rebase and force push

Updated. I added the mock addrs to wire::ip::test. I did not update the RawSocket or IcmpSocket tests because we should have both IPv4 and IPv6 tests for RawSockets and IcmpSocket does not support IPv6 at the moment.
BTW the test_like_travis.rb script is a lifesaver.


Error while submitting pull request

What is missing?
Pipeline YAML:
trigger: none # Disable CI trigger

schedules:
- cron: '0 2 * * *' # daily at 2am UTC
  always: true # run even when there are no code changes
  branches:
    include:
      - master
  batch: true
  displayName: Daily

pool:
  vmImage: 'ubuntu-latest' # requires macos or ubuntu (windows is not supported)

steps:
- task: dependabot@1
  inputs:
    packageManager: 'nuget'

Log:
Updating Microsoft.ApplicationInsights from 2.12.1 to 2.17.0
Submitting Microsoft.ApplicationInsights pull request for creation. Error updating Microsoft.ApplicationInsights from 2.12.1 to 2.17.0 (continuing)
/home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/response/raise_error.rb:14:in `on_complete': GET https://api.github.com/repos/Microsoft/ApplicationInsights-dotnet/contents/: 403 - API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) // See: https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting (Octokit::TooManyRequests)
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/middleware.rb:19:in `block in call'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/response.rb:59:in `on_complete'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/middleware.rb:18:in `call'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/request/retry.rb:148:in `call'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/rack_builder.rb:154:in `build_response'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/connection.rb:492:in `run_request'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/faraday-1.4.1/lib/faraday/connection.rb:198:in `get'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/sawyer-0.8.2/lib/sawyer/agent.rb:94:in `call'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/connection.rb:156:in `request'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/connection.rb:19:in `get'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/client/contents.rb:40:in `contents'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/clients/github_with_retries.rb:95:in `public_send'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/clients/github_with_retries.rb:95:in `block in method_missing'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/clients/github_with_retries.rb:115:in `retry_connection_failures'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/clients/github_with_retries.rb:92:in `method_missing'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:259:in `fetch_github_file_list'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:241:in `fetch_dependency_file_list'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:236:in `dependency_file_list'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:135:in `changelog_from_ref'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:123:in `default_branch_changelog'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:86:in `changelog'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base/changelog_finder.rb:34:in `changelog_url'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/metadata_finders/base.rb:40:in `changelog_url'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator/message_builder.rb:327:in `changelog_url'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator/message_builder.rb:292:in `metadata_links_for_dep'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator/message_builder.rb:279:in `metadata_links'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator/message_builder.rb:56:in `commit_message'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator.rb:171:in `azure_creator'
	from /home/dependabot/dependabot-script/vendor/ruby/2.6.0/gems/dependabot-common-0.142.1/lib/dependabot/pull_request_creator.rb:104:in `create'
	from ./update-script.rb:374:in `block in <main>'
	from ./update-script.rb:222:in `each'
	from ./update-script.rb:222:in `<main>'

You are hitting rate-limiting on the GitHub API because your requests to GitHub are unauthenticated. You need to supply a githubConnection so that your requests are authenticated. dependabot makes requests to GitHub to get release notes and/or changelog. The requests tend to be quite a number.


Issue In scroll behavior in latest Flutter release iOS

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

a. Open the app and navigate to the screen with Listview or Scrollview containing TextFields and a sticky button.
b. Scroll down the screen.
c. Observe the appearance of white lines over the button, as shown in the attached screenshot.
Expected results
When scrolling down the screen with Listview or Scrollview containing TextFields and a sticky button at the bottom, the application should exhibit smooth scrolling without any visual artifacts. There should be no lines or graphical glitches appearing over the button or any other UI elements. The scrolling action should be seamless and free from any distracting visual elements, ensuring a pleasant user experience.
Actual results

Observe the appearance of white lines over the button, as shown in the attached screenshot.
Code sample
Code sample
Column(
          children: [
            Expanded(
              child: SingleChildScrollView(
                controller: widget.scrollController,
                child: Column(
                  crossAxisAlignment: CrossAxisAlignment.start,
                  children: [
                    AppAlert.information(
                      content: context.shareRequestAmountScreenDepositInfoLabel,
                    ),
                    const AppGap.m(),
                    SectionHeader(
                      context.depositTo,
                      padding: const AppEdgeInsets.symmetric(
                        horizontal: AppGapSize.xs,
                      ),
                    ),
                    const AppGap.xxs(),
                    RequestMoneySelectAccountsWidget(
                        initialAccountNumber: widget.initialAccountNumber,
                        initialAccount: widget.initialAccount),
                    const AppGap.s(),
                    FocusAwareScrollerWidget(
                      scrollController: widget.scrollController,
                      child: const RequestMoneyAmountWidget(),
                    ),
                    const AppGap.s(),
                    const RequestMoneyDepositReasonWidget(),
                    const AppGap.s(),
                    const RequestMoneyDepositDescriptionWidget(),
                    const AppGap.m(),
                    AppPadding(
                      padding: const AppEdgeInsets.symmetric(
                          horizontal: AppGapSize.xs),
                      child: AppText.captionBold(
                          context
                              .shareRequestPayerScreenQuestionWhoIsTheRecipient,
                          color: AppTheme.of(context).colors.textBodySecondary),
                    ),
                    const AppGap.xxs(),
                    const PayerNameWidget(),
                    const AppGap.xs(),
                    const PayerLanguageItem(),
                    const AppGap.m(),
                  ],
                ),
              ),
            ),
            const ShareRequestButtonWidget(),
          ],
        )

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.9, on macOS 13.4.1 22F770820d darwin-arm64, locale en-KW)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.84.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Hi @ahmedshikashaker, the code sample you have provided is not complete.
Please provide a complete minimal runnable code sample preferably without any third-party packages/plugins so that we can investigate this. If you could also share a video of the issue, that would be appreciated.
PS: It would be best if the sample is a single main.dart file. It also does not have to be code from your project. Just the smallest code sample that reproduces the issue is fine.
Thank you

@danagbemava-nc i found the issue,
the issue is in the button in clipBehavior: Clip.antiAliasWithSaveLayer,  in Material Widget like
Material(
clipBehavior: Clip.antiAliasWithSaveLayer,
color: Colors.transparent,
when i removed  clipBehavior or changing it to Clip.hardEdge  it works fine

Hi @ahmedshikashaker, can you provide a complete minimal reproducible code sample so that we can investigate this? I don't think visual artefacts are expected regardless of the clip behaviour you use.
Thank you


Leading zeros. Confusing amount after parsing and formatting

Hello everyone!
I've encountered the confusing behavior with parsing numbers, starting from leading zeros. Like "003", "0003" and so on.
When you pass "003" to DecimalMoneyParser, it makes Money object with amount "3", which equals to "0.03" after formatting.
When you pass "0003" to it, it makes Money object with amount zero. (why?)
I expect passing "003" should be "3" after formatting, so the amount inside Money object should be 300. Am I right?
Regarding "0003" - I expect this also to be "3", as it's the way how intval(), floatval(), etc. default number functions process numeric values with leading zeros.
Please check the snippet below for better understanding:
<?php
//require your autoload file or make require_once for used classes manually

use Money\Currencies\ISOCurrencies;
use Money\Currency;
use Money\Parser\DecimalMoneyParser;
use Money\Formatter\DecimalMoneyFormatter;

$decimalMoneyParser = new DecimalMoneyParser(new ISOCurrencies());
$decimalMoneyFormatter = new DecimalMoneyFormatter(new ISOCurrencies());

$money = $decimalMoneyParser->parse('003', new Currency('USD'));
var_dump($money->getAmount()); //3 (should be 300)
$result = $decimalMoneyFormatter->format($money); //0.03
var_dump($result); //0.03 (should be 3);
var_dump(intval('003')); //3 - correct!

Maybe you are on an older version, because the following script.
<?php
require_once __DIR__ . '/vendor/autoload.php';

use Money\Currencies\ISOCurrencies;
use Money\Currency;
use Money\Parser\DecimalMoneyParser;
use Money\Formatter\DecimalMoneyFormatter;

$decimalMoneyParser = new DecimalMoneyParser(new ISOCurrencies());
$decimalMoneyFormatter = new DecimalMoneyFormatter(new ISOCurrencies());

$money = $decimalMoneyParser->parse('003', new Currency('USD'));
var_dump($money->getAmount()); //3 (should be 300)
$result = $decimalMoneyFormatter->format($money); //0.03
var_dump($result); //0.03 (should be 3);
var_dump(intval('003')); //3 - correct!

gives me this output.
/usr/bin/php8.1 /srv/libraries/money/test.php
/srv/libraries/money/test.php:13:
string(3) "300"
/srv/libraries/money/test.php:15:
string(4) "3.00"
/srv/libraries/money/test.php:16:
int(3)

I added a test for this specific situation in 6fcdcaf.


Segmentation Fault

Issue Description
While running distance_to_object.ipynb, I often receive a segmentation fault that stops the execution of the program. How do I limit the number of times that this error appears? Currently, I am looping the code so that the camera continuously detects objects as the camera is moving. Perhaps is there a better solution as well?

Hi ShadowHunter0510**,**
I tried to test the distance_to_object.ipynb code in a python2.7 setup, and don't see the segmentation fault with multiple runs.
And as for now, my system has all dependencies on python2.7, I will see if I can test python3 somewhere else.
BTW, which version of python3 you have?
Thanks!

Hi ShadowHunter0510**,**
Wonder if there is any update? If nothing else is needed, this one will be closed soon.
Thanks!


Function prefixes

First, congratulations for the work!
I was seeing the example usage:
// Listen to HTTP requests and start facil.io
int main(int argc, char const **argv) {
  // allocating values we use often
  HTTP_X_DATA = fiobj_str_new("X-Data", 6);
  // listen on port 3000 and any available network binding (NULL == <IP_ADDRESS>)
  http_listen("3000", NULL, .on_request = on_request, .log = 1);
  // start the server
  facil_run(.threads = 1);
  // deallocating the common values
  fiobj_free(HTTP_X_DATA);
}

And, at least for me, using 3 different prefixes (http, fiobj, facil) appear a bit unintuitive.
What about all prefixes being just http_?
In this way we don't need to remember each functions should use this or that prefix. The learning curve is smaller, and hence the adoption can be bigger.
Just an idea.
Another thing is this line:
FIOBJ HTTP_X_DATA;

Generally in C we use uppercase letters for constants, but this is a variable.
The typedef is also in uppercase. A bit unusual for me.
But this can be less important.
Cheers,

Hi @kroggen ,
Thank you for opening this issue.
This appears to be an issue related to the 0.6.x API if I am correct.
In 0.7.x versions you will find more consistency. All facil.io core functions where moved to the fio_ namespace (prefix).
As for merging all namespaces to a single namespace, I believe this would be a mistake.
The facil.io library is a modular library. The facil.io core isn't limited to HTTP services, and can be easily compiled without the HTTP services extension.
Also, facil.io and it's extensions provide quite a large number of functions. When using an IDE, the different namespaces / prefixes empower the auto-complete feature to make meaningful suggestions in less time.
As for going forwards and suggesting further improvements towards the upcoming 0.8.0 API, please feel free to join the discussion in issue #60. It would be great to read your opinion on these issues.
Kindly,
Bo.
P.S.
In this specific case, the HTTP_X_DATA is a constant, it's just not a compile-time constant and has to be initialized (and eventually destroyed) during runtime.
The FIOBJ type name started as a macro and I've kept it this way because I want to be able to change the implementation easily (without changing the name or breaking existing code).


readthedocs build failure not carried forward to github action

Build action completed while readthedocs reported failure, see
https://readthedocs.org/projects/surmise/builds/25524079/

Some investigation:
In RTD, between build 25464477 and build 25462853 is when the build has failed.
The commits between the two builds seem to indicate no problem.
But Sphinx v7.4.7 and v8.0.2 are called respectively in the two builds. With Sphinx v8.0.2, RTD build seems to fail, but does not notify GH action.

One solution is to specify Sphinx version for now - but we should maybe look deeper..

Local and GH action builds use tox, which has been setup so that all sphinx dependencies are always installed.  Therefore, these pass.
The RTD config was originally specified to install the "docs" optional dependencies as specified in pyproject.yaml.  However, at commit b56e0c3fedd4834a82207e7f5c13b29a16cf1efb, we removed those to keep things simpler and because users don't need to build the docs.  Hence the failure.
At commit e6f7e349c86b7721c9001558dd7bcc87bb3111d2, we included these dependencies in a requirements file bundled with the doc files.  We presently prefer this method since it still keeps things simpler and the deps are specified in a more direct way.  Also, the package might need to eventually move to using only a setup.py, which is compatible with the current implementation.
Closed.


visual bug in selector

Good morning, cordial greetings, as you can see in the following image, the component is calculating the space for the options, despite the fact that these options have a display style of none, it is probably being validated by the child nodes of the element without having Take this detail into account, since when these child nodes are eliminated, the selector is displayed correctly.
I attach screenshots with the evidence of the inconvenience.

Good day, I don't think it's a problem with the refresh, below I put an example recreated in js fidle so you can validate the error.
https://jsfiddle.net/o5dv26z9/23/

@NicolasCARPi please review


Change in Table in doc as Andoid and iOS support for FIDO2 is GA

Since FIDO2 key is now supported for Android and iOS, (https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/azure-ad-certificate-based-authentication-cba-on-mobile-now/bc-p/3814939#M4964)
the table at https://learn.microsoft.com/en-us/azure/active-directory/standards/memo-22-09-multi-factor-authentication#application-sign-in-scenarios-from-various-clients might be updtaed, probably?

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

ID: 5a73d324-5e4b-4f6e-36ae-4ff352a8060a
Version Independent ID: 2deac1ec-8746-30ff-ee65-68caffef6470
Content: Memo 22-09 multifactor authentication requirements overview - Microsoft Entra
Content Source: articles/active-directory/standards/memo-22-09-multi-factor-authentication.md
Service: active-directory
Sub-service: standards
GitHub Login: @Gargi-Sinha
Microsoft Alias: gasinh

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

That GA announcement is not for FIDO2. Its certificate on a security key
(which may also be FIDO2). The feature is still not fully implemented in
Android and iOS devices. Checking with the Feature PM team and will
update this thread.
On Wed, May 10, 2023 at 1:18 AM ManoharLakkoju-MSFT <
@.***> wrote:

@Gargi-Sinha https://github.com/Gargi-Sinha
Could you Please review this and update as appropriate.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/109220#issuecomment-1541556181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALX3IOUS2UC2KMTFJ32X6ELXFNFNVANCNFSM6AAAAAAXZQUTPA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Gargi-Sinha
Thanks for your inputs
@JFRgt
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@ManoharLakkoju-MSFT Thanks for the follow-up.
@Gargi-Sinha Thanks for the clarification.

Thanks all for the follow-up and clarification.
Le jeudi 11 mai 2023, 07:55:02 UTC+2, ManoharLakkoju-MSFT<EMAIL_ADDRESS>a écrit :

@Gargi-Sinha
Thanks for your inputs
@JFRgt
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


skip waiting for XHR/fetch to resolve

What is your Scenario?
I have a UI that will make an API request while user types. Until  the API is resolved, a button should be disabled.
While the functionality to wait for the XHR and fetch requests to resolve, it makes testing this behavior more complicated.
It would be helpful if this 3 second wait could be skipped in such scenarios.
What are you suggesting?
something like awaitFetch:false  to skip waiting for 3 seconds
t.typeText(Selector('input'), 'yoo hoo', {awaitFetch:false });

What alternatives have you considered?
Stretching to mock timeout, but too long slows down tests and too short becomes flaky.
I've also tried storing a resolve function for a promise in a global variable which gets called during the test.
let resolveFn = null;

RequestMock()
  .onRequestTo(/my\-trunk/)
  .respond(async (req, res) => {
    await new Promise((resolve) => (resolveFn = resolve));
    res.setBody("my junk");
  });

// in test...
  await t.typeText(Selector('input'), 'yoo hoo', {awaitFetch:false });
  resolveFn()

but it still waits for those 3 extra seconds, but it's now less flaky
Additional context
No response

Hi @dasDaniel

it makes testing this behavior more complicated.

Could you please share a test code example that illustrates the described behavior?

Hi @dasDaniel

it makes testing this behavior more complicated.

Could you please share a test code example that illustrates the described behavior?

sure, here's a repo
https://github.com/dasDaniel/example-testcafe-timeout
This illustrates the workaround, but if I start to add more complexity, like a long debounce, this will no longer work as-well.
If there are many of such assertions in the test, this can make the time to complete test grow very fast.

Hi @dasDaniel
In your test, you try to check that the myBtn button is disabled during the fetch request to the api.json resource. Since the request is performed very fast on a local machine, it's difficult to check the disabled state of the myBtn button.
If you perform the test actions manually, you will see the same result.
To check the disabled state, the approach from your test is correct.
Also, you can imitate the fixed delay of the api.json resource:
import { RequestMock, Selector } from "testcafe";

const API_DELAY = 10000;

const mock = RequestMock()
  .onRequestTo(/api\.json/)
  .respond(async (req, res) => {
    await new Promise((resolve) => {
        setTimeout(resolve, API_DELAY);
    });
    res.setBody({ ok: "👌" });
  });

fixture`example`.page`http://<IP_ADDRESS>:7772/index.html`.requestHooks(mock);

test("example", async (t) => {
  const btn = Selector("button"),
    input = Selector("input");

  await t
    // assert button enabled
    .expect(btn.hasAttribute("disabled"))
    .notOk()

    // add some text
    .typeText(input, "🤖")

    // assert button disabled
    .expect(btn.hasAttribute("disabled"))
    .ok()
    .wait(API_DELAY);

  // now check that it is enabled again
  await t.expect(btn.hasAttribute("disabled")).notOk();
});


feat: support Module Federation format

Summary
Add format called 'mf' to build Module Federation assets and add example for both host and remote scene in rslib
closes: #212
Related Links

Checklist

[x] Tests updated (or not required).
[x] Documentation updated (or not required).

@nyqykk Let’s keep pushing this PR.

@nyqykk Let’s keep pushing this PR.

i write a rsbuild plugin in mf repo, for both app project and rslib which is build by rsbuild, so this branch will be changed
https://github.com/module-federation/core/pull/3062

Generally LGTM. 👍

Append examples/module-fedration/mf-react-component to https://github.com/web-infra-dev/rslib/blob/main/tests/benchmark/index.bench.ts then we're good to merge.
You could remove the 'esm' and 'cjs' lib from the config like what disableDts does. This could help us only foucs on measure the benchmark of MF bundling. disableDts should also be applied as well.

The benchmark shows examples/react-component-bundle-false got improved, but it should be irrelevant. cc @SoonIter any idea?

Great work!


Fix #17; support scanning for files that have URI-encoded paths

The FileBrowser API returns paths that are URI-encoded. Map the results array using decodeURI to bring the special characters back. Tested with Foundry 11.315.

Can no longer reproduce issue


Change datepicker with timeline slider (#19)

Based on issue #19 and #100 related to new UI for datepicker
Before:

After:

@hav142 nice! How does it look on mobile?

@hav142 nice! How does it look on mobile?

Thanks @ericboucher. It should be responsive like this:

Ok, let's add a bit of spacing maybe to make it look a bit better on mobile?
On Fri, Feb 19, 2021 at 12:00 AM hav142<EMAIL_ADDRESS>wrote:

@hav142 https://github.com/hav142 nice! How does it look on mobile?
Thanks @ericboucher https://github.com/ericboucher. It should be
responsive like this:
[image: image]
https://user-images.githubusercontent.com/25983260/108469337-a2751e00-72ba-11eb-8fef-8810e1b5408f.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WFP-VAM/prism-frontend/pull/139#issuecomment-781875600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAQEAYKD6462F2RKNBPSDLS7YECJANCNFSM4XUCEMPA
.

@ericboucher I added some spacing and change the code structure a litle bit to make sure it works on all screen size

Sorry to nitpick, but is there a Material UI design solution we can use for this? I like the functionality but the UI is not in harmony with other elements

Good first steps to help achieve this might be to choose a different variant for the dates (maybe matching the text in the navbar) and using a MUI icon for the arrow, with a color already used in the app.

Sorry to nitpick, but is there a Material UI design solution we can use for this? I like the functionality but the UI is not in harmony with other elements

Good first steps to help achieve this might be to choose a different typography variant for the dates (maybe matching the text in the navbar) and using a MUI icon for the arrow, with a color already used in the app.

good recommendations - thanks Ryan. @hav142 - can you make an attempt to implement these suggestions?

Sorry to nitpick, but is there a Material UI design solution we can use for this? I like the functionality but the UI is not in harmony with other elements

Good first steps to help achieve this might be to choose a different typography variant for the dates (maybe matching the text in the navbar) and using a MUI icon for the arrow, with a color already used in the app.

good recommendations - thanks Ryan. @hav142 - can you make an attempt to implement these suggestions?

is this good enough?

Looks good from the screenshot - thank you!
On Wed, Mar 31, 2021 at 5:39 PM hav142 @.***> wrote:

Sorry to nitpick, but is there a Material UI design solution we can use
for this? I like the functionality but the UI is not in harmony with other
elements
Good first steps to help achieve this might be to choose a different
typography variant for the dates (maybe matching the text in the navbar)
and using a MUI icon for the arrow, with a color already used in the app.
good recommendations - thanks Ryan. @hav142 https://github.com/hav142 -
can you make an attempt to implement these suggestions?
is this good enough?
[image: image]
https://user-images.githubusercontent.com/25983260/113227638-59eb5000-92bd-11eb-8223-b48b957f6543.png
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/WFP-VAM/prism-frontend/pull/139#issuecomment-811556843,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZQJMGQRQOORVF2SC7SVUDTGO6EZANCNFSM4XUCEMPA
.

* The DateSelector test is insanely large. Maybe we can mock some things so we can cut it down to something more reasonable?

i tried to add one more param to DateSelector component so it become like this <DateSelector availableDates={selectedLayerDates} dateRangeBy="days" />, then in the test file, i change it to dateRangeBy="months" so that the snapshot only create 12 month as mock instead of hundreds. and maybe it can be useful in the future if we want to display the timeline as monthly for some specific layer instead of daily. is this ok? what do you think?

* All good that we use a FontAwesome arrow icon, but it might be worthwhile to use the MUI icon instead for consistency.  Up to you and what you think looks best 👍

it's the same case with the one here. will update if using MUI icons is possible

* I think there's a few comments left from last review that you haven't responded to yet. If you have any quesitons, let me know :) They are quite small so I'm ok to overlook them if they don't seem worthwhile.

sorry i haven't replied them yet because i'm not sure about how to solve them:

TS complaint. not sure about this because i got no complaint in my local machine
Constant for classes. can you give an example on how to implement this one? 🙏

For the DateSelector, you could spot which lib components take multiple lines and mock them in setuptTest
Another thing you can do is break down your component into a few different ones, and test them separately. So that you only test the component within the .map once. @Ry-DS any other ideas?

Another thing you can do is break down your component into a few different ones, and test them separately. So that you only test the component within the .map once. @Ry-DS any other ideas?

noted, i will try to break down the component first and see how is it going. Thanks @ericboucher

TS complaint. not sure about this because i got no complaint in my local machine
Constant for classes. can you give an example on how to implement this one? 🙏

Should have been more explicit haha. I assumed you were casting to any because if you didn't, TS would complain. I was thinking that maybe we could avoid this any cast by replacing import Moment from 'moment' with import * as moment from 'moment';. All good if this doesn't work, but might be worth a shot.
The &:hover styles were repeated, so I was thinking something like:

const DATE_ITEM_STYLES: CreateCSSProperties = {
  borderTop: '1px solid white',
  color: 'white',
  position: 'relative',
  top: -5,
  cursor: 'pointer',
  minWidth: TIMELINE_ITEM_WIDTH,
  '&:hover': {
    borderLeft: '1px solid #5ccfff',
  },
};
const styles = () =>
  createStyles({
    dateItemFull: {
      ...DATE_ITEM_STYLES,
      borderLeft: '1px solid white',
      height: 36,
    },

    dateItem: merge(DATE_ITEM_STYLES, {
      '&:hover': {
        '& $dayItem': {
          borderLeft: 0,
        },
      },
    }),
// continued

Great job @hav142 ! Let's do the two small changes @Ry-DS suggested and we should be good to go :)

Thanks @Ry-DS for the clear guideline

1. Should have been more explicit haha. I assumed you were casting to `any` because if you didn't, TS would complain. I was thinking that maybe we could avoid this `any` cast by replacing `import Moment from 'moment'` with `import * as moment from 'moment';`. All good if this doesn't work, but might be worth a shot.

it works when i remove the cast and use your approach like this:
import * as Moment from 'moment';
...
const moment = extendMoment(Moment);

but then there is an error when running yarn test

Point no. 2 is good, but i need to install @material-ui/styles for using  CreateCSSProperties, and add new config in eslint: import/no-extraneous-dependencies. am i doing it right?

it works when i remove the cast and use your approach like this:
import * as Moment from 'moment';
...
const moment = extendMoment(Moment);

but then there is an error when running yarn test

Ahh I see, you can keep the any cast then.
For the second point, I was able to use the type without a new dependency. I removed it in a new commit to see if the build passes. Let me know if you still face issues :+1:


Block domain overledger.tech

Domain: domain
Requested by @vinkingbyte

Whiplash token promoted to steal money to the people with pump dump actions

Falsified Company/Asset Association
Branding and Trademark Infringement
Counterfeit Token
Counterfeit Domain not part of the qnt (Quant Network Ltd}
Falsified TOML file information  fake email now points to a domain that is for sale.


Dd/oracle

use pyth_client instead of copy pasta code
allow pyth to be behind by 50 slots instead of the current 25 enforced by Pyth program

Tested on devnet (with devnet cfg flags removed) and works fine

@acamill Do you know why our CI always fails the UXD composability test?

@acamill Do you know why our CI always fails the UXD composability test?

This fails due to github auth token to private repositories, @acamill  told us to ignore it for now, they will open source soon after audit and we wont require a token to run their tests

@acamill Do you know why our CI always fails the UXD composability test?

This fails due to github auth token to private repositories, @acamill told us to ignore it for now, they will open source soon after audit and we wont require a token to run their tests

Oh yes I though you guys removed it entirely for now.
I'll look into it today

Here is the PR #167


fix slab_layer arg to accept None

The component grating_coupler_rectangular_arbitrary doesn't accept the None type for the slab layer (other similar components e.g. grating_coupler_rectangular do!). This PR fixes that.

Thank you Lawrence!


Show tabbed structure panel with toc, text, (layers)

"… select which transcriptions and/or translations and/or commentaries to view with the image."

Can this be closed?


ci: fix rust-fmt breakage

Add force to cargo fmt

Assumed the wrong fix. Actual style errors to be corrected in separate PR. Closing


Setting Credentials parameter on "PowerShell on Target Machine" task

I get the following error when trying to run the "PowerShell on Target Machine" task.
##[error]Cannot process command because of one or more missing mandatory parameters: Credential. For more info please refer to http://aka.ms/powershellontargetmachinesreadme
I would like to add that "Credential" parameter but I'm not really sure that it's possible.

@phklemmensen
Credentials need to be passed in the input fields Admin Login and Password.
For security you can declare secure variables and use them with $(var_name) notation in these fields

@KrishnaAdityaB
Thanks for the quick answer.
I guess I must be using an older version of the task because those field are not available to me.

@phklemmensen

If you are using VSTS (visualstudio.com)
a. If you are creating a new definition:
you should get the latest UI with these fields.
b. if you are viewing an old definition:
please add a new task and delete the old one

if you are using on-premise TFS
please share the TFS version and the scenario you are trying

@KrishnaAdityaB
We are using an on-premise TFS server (version number 14.0.24712.0 (Tfs2015.Update1))
I'm trying to use the  "PowerShell on Target Machine" task to run a PowerShell script located on a machine in a work group separate from the domain where the TFS build agent is running.
I've tried using HTTPS connection (but that currently fails with a certificate revocation check).
So now I'm trying to use plain HTTP connection (with the target machine added to TrustedHosts) but I can't currently do that as I am unable to add the -Credential parameter.
(I've also started to look into creating my own PowerShell script to execute the remote script, but I would really prefer to use the built-in)

@phklemmensen it's bit surprising, per git history, with 2015 Update 1 you should see an input similar to following:
.
You may try using machine group with details of target machine. The name of machine group can be provided in Machines or Machine Group input in the task.
However kindly note that machine groups is not a secure option (please don't use for production machines) and this feature may be deprecated soon. Please consider moving to TFS Update 2 if possible.

@phklemmensen
I am thinking your build/release definition might be an old one created before update 1.
Can you open the definition and add the task freshly?

The task looks like this (just added)

@codito the machine group approach is what I am currently using

the group is set up like this

I'm focusing all effort on geting the HTTPS solution to work so I'm closing this issue. Thank you very much for your help.


Generating Lite Build from Existing Code

🚀 Feature request
Command (mark with an x)

- [ x ] build
- [ x ] serve

Description
 As application builds day by day it become very heavy to load. Heavy in the sense it require good connection to load vendor.js, main.js which are huge in size.
We can not deny that there are still low internet connection are available on the globe. When user having less speed he prefers to see lighter version of application. What I want to show user is there is lighter version of application is available(On different domain).
Is there any way we can create build from current code base with limited feature? If its not we should have this feature.
Describe the solution you'd like
 Option for lite build.
Describe alternatives you've considered
 Currently I am using file replace option in angula.json to replace it with lighter version of HTML TS. But its very difficult and also I didn't get success on that.

Do you use lazy loaded modules . I think it is a good first solution for minimizing the build size.

Yes @EmmanuelDemey I am already using lazy loaded component. I want to do further cut down by feature reduce on lite build.

A production build should not have a vendor.js file.  Are you building using the production configuration? (e.g., ng build --prod).
The file sizes for a new application using 9.0.0-rc.1 are as follows:
141032 Nov  6 20:08 main-es2015.ed01ec5f480fa886325f.js
163321 Nov  6 20:08 main-es5.ed01ec5f480fa886325f.js
 36808 Nov  6 20:08 polyfills-es2015.b6fe2b19564e29c5d554.js
127927 Nov  6 20:08 polyfills-es5.9cbeb6b4a192c8c548fe.js
  1485 Nov  6 20:08 runtime-es2015.52756d3ab8e6582f0541.js
  1485 Nov  6 20:08 runtime-es5.52756d3ab8e6582f0541.js

@clydin : I have set "vendorChunk": true in configuration that is why its generation separate vendor chunk while build. Default is false so its not generating for you.

That should not be used outside of development scenarios.  Its purpose is to improve rebuild performance during “ng serve”.  For builds, it causes a massive deoptimization of the final output and will result in significantly larger file sizes.

We already do our best with the defaults to have the smallest possible build. Whenever we find new ways of making user bundles smaller, we just do it automatically as bundle size is one of our biggest focus areas.
I'd like to reiterate that you really shouldn't have a vendor bundle in production for the reasons @clydin mentioned. Having a separate vendor chunk will always ensure it will be very large.
Additionally reducing the main bundle can be done by using lazy loaded components as much as possible. For the fastest initial load, you should structure your app such that the main bundle is as small as possible.

@filipesilva : I am already using lazy loaded component.
I am not getting why issue with different vendor. Because with vendor true my main.bundle size 900kb without vendor it increased to 2.6 MB.
My vendor.js file is 1.7 mb that I think appending in main.bundle.js file. Am I doing anything wrong?
My production build setup
"production": {
          "optimization": true,
          "outputHashing": "all",
          "sourceMap": false,
          "extractCss": true,
          "namedChunks": false,
          "aot": true,
          "extractLicenses": true,
          "vendorChunk": true,
          "buildOptimizer": true,
          "serviceWorker": true,
          "fileReplacements": [{
            "replace": "src/environments/environment.ts",
            "with": "src/environments/environment.prod.ts"
          }]
        }

@filipesilva @clydin can you help me on this? I am curious to know.

No, you're not doing anything wrong I think. When disabling the vendor chunk it will be included in the main chunk. This allows for better optimizations when possible. In your case, maybe optimizations are not possible.
Having a bundle that large is probably due to many third party libraries. Some can be very large. You can see where the size comes from by doing a production build with sourcemaps (ng build --prod --source-map) and then using https://www.npmjs.com/package/source-map-explorer to see the size of each library in your bundle.
Using lazy routes helps, but if you want to reduce the size of your main bundle then you need to move as much code and third party imports the the lazy routes. If you have lazy routes but still a lot of code in the non-lazy routes, you will still have a large main bundle.
You can also get some more advice and help on how to reduce your application size by asking on Stack Overflow. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Functionaljava

Converters for

JDK
Guava
jooλ
simple-react

Supported Functional Java Monads include

IO
Either
Option
Stream
List
State
Reader
Writer
Trampoline
Validation

What is the best way for me to get started having a try of this?

@mperry  Hey Mark, a couple of options

You could try checking out the code on the functionaljava branch and adding some unit tests. I think your main challenge there would be the use of Lombok in the code base. You'd need to install Lombok 1.16.4 into your IDE. Lombok val is used in some places which requires IntelliJ 14.1 and above. Should be no problems with Eclipse. To use AnyM, you only need cyclops-base, to use for comprehensions cyclops-for-comprehensions is also required.
I could create a snapshot and make it available somewhere (Maven, or in the releases section as a fatjar?)

@mperry Hope your finger is ok, btw. I've added in a conversion of this Scala based blog post to Java8. Reader Monad for Dependency Injection. There are also some thoughts on how to improve things going forward.
https://github.com/aol/cyclops/blob/functionaljava/cyclops-functionaljava/src/test/java/com/aol/cyclops/functionaljava/reader/DITest.java

I will have to look later.  I tried to compile but got an error, see #47.  Yes, the reader monad is a normal function and we use partial application.  Not sure if FJ has a good demo of this in the code.
Tony Morris did a great talk online about this:

http://chariotsolutions.com/presentation/dependency-injection-without-the-gymnastics/
https://vimeo.com/44502327

Didn't realize the λ caused problems on Windows. We've removed it from some other places. Will remove it entirely.

The promise of Java: compile once, debug everywhere.

The dreaded lambda character has been removed from the functionaljava branch. Will have to wait until this is merged back to master to remove it fully from there.

@mperry  I'm going to merge this into master, I don't doubt we'll have to change some things to get the behaviour correct - but it's probably simpler to do that on a branch with less changes - this one is very large.

Feel free to reopen for comments, or continue to comment here / log an issue / email / twitter etc by the way. Just felt this PR was too big.

Sure, no problem.


stack trace infinite loop

I'm just getting started using probe-run, testing a threading crate I'm building.
So (on Cortex-M), the thread stacks are populated with a frame like an exception would do, [r0-r4, r12, LR, PC, APSR].
LR is set to the location of a cleanup(), which does some house-keeping, then triggers the scheduler to switch away, then does a loop {}, which is practically unreachable.
Now when I run something with probe-run, the resulting stack trace endlessly repeats in cleanup():
[...]
    Finished dev [optimized + debuginfo] target(s) in 0.01s
     Running `probe-run --chip nRF52840_xxAA /home/kaspar/src/own/rust/riot_core/target/thumbv7em-none-eabi/debug/examples/bench_lock`
flashing program ..
^[[CDONE
resetting device
stack backtrace:
   0: 0x00001752 - <unknown>
   1: 0x000016b6 - cortex_m_semihosting::hio::hstdout
   2: 0x00001650 - cortex_m_semihosting::export::hstdout_fmt::{{closure}}
   3: 0x00001558 - cortex_m::interrupt::free
   4: 0x00001638 - cortex_m_semihosting::export::hstdout_fmt
   5: 0x000007b6 - user_main
   6: 0x0000112a - riot_core::main_trampoline
   7: 0x00000d20 - riot_core::thread::cleanup
   8: 0x00000d20 - riot_core::thread::cleanup
   9: 0x00000d20 - riot_core::thread::cleanup
  10: 0x00000d20 - riot_core::thread::cleanup
  11: 0x00000d20 - riot_core::thread::cleanup
  12: 0x00000d20 - riot_core::thread::cleanup
  13: 0x00000d20 - riot_core::thread::cleanup
[...]

The lines <N>: 0x00000d20 - riot_core::thread::cleanup repeat extremely fast, and the process cannot be cancelled with CTRL-C.
While I might have messed up something on the stack to make it invalid and look like this to probe-run, I'd expect it to stop after maybe the second iteration, letting the user know that this would repeat.
(I'm assuming that probe-run's rtt support uses a different BKPT scheme than traditional semihosting, and that's why this exits on the first hprintln!(), but that is a unrelated to this issue.)
This is on probe-run 0.1.3 installed today via "cargo install probe-run".

Thanks for the report! https://github.com/knurling-rs/probe-run/pull/47 should fix the behavior of Ctrl+C while the backtrace is being generated. To investigate the broken backtrace, it would be great if you could provide the source code of riot_core.

7: 0x00000d20 - riot_core::thread::cleanup
8: 0x00000d20 - riot_core::thread::cleanup

in these situations we should check both the PC (printed) and SP (not printed); if both haven't changed in one iteration then the virtual unwinder has gotten stuck and we should stop it and print an error message. (I thought there was already some logic to check for this condition but maybe not)

We do have such a check, but it seems like that isn't enough:
https://github.com/knurling-rs/probe-run/blob/e1964b8dda6a679e2a348d1f8061e56d18264d8e/src/main.rs#L579-L582

@kaspar030 It would be great if you could re-run this on the current main branch (which includes #48), with RUST_LOG=probe_run=debug set. That should print some more information we can use to diagnose what's happening.

@kaspar030 It would be great if you could re-run this on the current main branch (which includes #48), with RUST_LOG=probe_run=debug set. That should print some more information we can use to diagnose what's happening.

Done, here's the end of the output:
stack backtrace:
   0: 0x0000139e - <unknown>
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(2000039c) -> 200003bc
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001303 pc=0x0000139e
   1: 0x00001302 - cortex_m_semihosting::hio::hstdout
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003bc) -> 200003c4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001245 pc=0x00001302
   2: 0x00001244 - cortex_m_semihosting::export::hstdout_str::{{closure}}
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003c4) -> 200003d4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001177 pc=0x00001244
   3: 0x00001176 - cortex_m::interrupt::free
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003d4) -> 200003e4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001231 pc=0x00001176
   4: 0x00001230 - cortex_m_semihosting::export::hstdout_str
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003e4) -> 200003f4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000617 pc=0x00001230
   5: 0x00000616 - app::func
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003f4) -> 200003fc
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000aa5 pc=0x00000616
   6: 0x00000aa4 - riot_core::thread::cleanup
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000aa5 pc=0x00000aa4
   7: 0x00000aa4 - riot_core::thread::cleanup

I guess the thumb bit needs to be ignored in the check that's mentioned above.

Yeah that sounds like the right fix. Can you try with https://github.com/knurling-rs/probe-run/pull/50 to see if that fixes it?

Thanks a bunch!