function to model solar insolation

ignores day-to-day variability in cloudiness, etc; just the pure seasonal and daily pattern for a given latitude. user sets the maximum daily insolation (default is 1000 W/m2). does this all look right to you, @jread-usgs, code and physics and all?

Looks good. Any testables in there?

There are examples, but good point - should also create official tests. Thing is, what to test - that it runs and produces a vector? Don't know how to test the quality of the output beyond looking at the patterns (ggplot calls in examples) to see if they're sensible. Any ideas?

I think there are a number of things that are worth doing there - check when you use the with.units arg that you return a valid unitted object. Check for nighttime darkness, etc.?

OK, I'll give it a shot. Stay tuned.

Coverage decreased (-11.94%) to 8.06% when pulling 1056af689653e6de2209691faf4c8a21823739b5 on aappling-usgs:master into 7ff862c153ade8f7eafee8acd1f5f30430684c3a on USGS-R:master.

@aappling-usgs you want to sneak tests in on this PR, or want me to merge this?

yes, i want to sneak tests in. am working on them now.
On Thu, Apr 23, 2015 at 2:10 PM, Jordan S Read<EMAIL_ADDRESS>wrote:

@aappling-usgs https://github.com/aappling-usgs you want to sneak tests
in on this PR, or want me to merge this?
—
Reply to this email directly or view it on GitHub
https://github.com/USGS-R/streamMetabolizer/pull/19#issuecomment-95688410
.

--
Alison Appling
Postdoctoral Fellow, USGS Powell Center
USGS Center for Integrated Data Analytics and University of Wisconsin -
Madison
Phone:<PHONE_NUMBER>

i think i meant to merge jordan's PR, not this one. oh, well, tests on the way in my next PR


[Improve][Doc] Minor wording and typo fix

Motivation and Modifications
Just minor wording and typo change
Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[x] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Hi @Anonymitaet, please take a look at this PR.
This PR only contains minor language fixes which won't affect formatting, so I did not attach a preview image. Thanks.

@Sherlock113
Thank you! Looking forward to more contributions! 😊


Strange regexp in vagrant-ansible.yml

Can someone comment on this part in https://github.com/kubernetes/contrib/blob/79b0123/ansible/vagrant/vagrant-ansible.yml#L15:
    - name: "Remove hostname from localhost line"
      replace:
        dest=/etc/hosts
        regexp="{{ item }} localhost?"
        replace="localhost"

As far as I understand this regexp will match for example kube-master localhost and kube-master localhos (note missing last letter due to ? in regexp) — is this expected behavior?
I think {{ item }}\s+localhost$ regexp should be used if we want to just match string like kube-master     localhost.
This was introduced by @jasonbrooks in 79b0123a. Jason, can you comment on this?

Yes, it should be $

@jasonbrooks, thanks for the quick reply!
What about space? Should it be replaced with \s+: {{ item }}\s+localhost$?

Actually, I just tested these and the $ doesn't work. The line this is changing starts like:
<IP_ADDRESS>   kube-master localhost localhost.localdomain localhost4 localhost4.localdomain4

And we're getting rid of kube-master w/ this.

Then how about {{ item }}\s+localhost?


Carthage Support

Great that you have CocoaPods support, what about Carthage?  😄
https://medium.com/@filippotosetto/how-to-create-a-carthage-framework-8d9d65f98ac2

I do not have carthage support planned as of now, feel free to raise a PR for it if needed.


SWITCHYARD-2876  Write a test for ENTESB-4587

https://issues.jboss.org/browse/SWITCHYARD-2876

Can one of the admins verify this patch?

ok to test


Start using Jest's "modern" fake-timer implementation.

Recent improvements have been made to Jest's implementation of fake timers, on an opt-in basis, with a plan to make them the default in the future: https://github.com/facebook/jest/pull/7776.
Some prep work has been done toward this (https://github.com/facebook/react-native/pull/29011), but I don't find an existing issue for the actual change.
Simply flipping the switch to the "modern" implementation gives several test failures, likely due to some combination of

dependency on wrong semantics of the legacy implementation, and
https://github.com/facebook/jest/issues/10221

I'm excited for facebook/react-native's own tests to be made more correct, but I particularly hope to draw attention to the fact that React Native apps can't currently use the new implementation (https://github.com/facebook/jest/issues/10221, https://github.com/facebook/react-native/issues/29303, https://github.com/facebook/react-native/pull/29754). This is a problem for apps that can't use the legacy implementation either, because of its issues (not having Date.now() faked is a big one).
React Native version:
v0.61.5. (See https://github.com/facebook/react-native/issues/29767#issuecomment-691334464, below, for more environment info.)

Ah, here's the missing environment info for the bot 🙂:
System:
    OS: macOS 10.15.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 2.87 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29
      Build Tools: 27.0.3, 28.0.3, 29.0.2
      System Images: android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>41897
    Xcode: 11.7/11E801a - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5

Hi @chrisbobbe thanks for the request & all the details.
You opened a PR here: https://github.com/facebook/react-native/pull/29754/files
Would this resolve the Jest issue, if merged in?


Add extra docs for CSV classes

Add docs for:

lib/csv/fields_converter.rb
lib/csv/parser.rb
lib/csv/writer.rb

@kou that's understandable. I'd suggest adding the responsibilities above the classes/methods and remove any extra detail that could explain how to use the objects.
Right now lib/csv/parser.rb is a relatively big class, it doesn't have docs and needs to be improved.

OK. Let's do so.
How about adding "Don't use this class directly. This is an internal class." or something too?


Implemention and EMD Loss

Hi vinits:
Thanks for your nice work and open source code. I find the following code is not good, because the normalization operation almost removes the translation between the source point cloud and the template point cloud.
# mean substraction
source = source - torch.mean(source, dim=1, keepdim=True)
template = template - torch.mean(template, dim=1, keepdim=True)

I re-implemented the network in https://github.com/zhulf0804/PCReg.PyTorch with modifications(iterative emd loss, partial registration, pairs point cloud generation, without mean substration, etc.), I got the following visualization results:

I found EMD loss or CD loss is not friendly for point clouds registration with symmetrical structure.

Hi @zhulf0804,
Thank you for your interest in our work. I understand your concern about the translation. The mean subtraction step is present in code as we follow the same settings as of ICP and PointNetLK algorithms. We have observed that even if you train the network without mean subtraction, the results will follow similar trends.
I understand that EMD and CD loss won't be very friendly in case of symmetrical structure or higher initial misalignments.
I see the partial-to-complete as a very interesting result. If you would be able to share the trained model with me then, I would be glad to have it on the repository for everyone's benefit. Of course, you will be acknowledged.
My contact details<EMAIL_ADDRESS>

Hi vinits5,
Glad to hear from your. And i have sent the trained model by the email you provided above.
I observed some partial-to-complete registration results may not good due to the simple network design, but most partial-to-complete registration results seems ok.
I am doing some attempts to optimize the model. Looking forward to communicating with you.
Best regards.


Primary Consultant ID field is appearing on the create an account form and should not be

Expected behavior
Create account Mock up:

Actual behavior
Create account page looks like this in tech sandbox. The Primary Consultant ID field should not be displayed:

Steps to reproduce behavior
Click on 'Sign In then 'Create an account'.

7/20 SH - Sounds like Jared was testing something, the field is gone now. Closing bug.


Introduce doc tests

Because, well, doc tests are really cool. And it helped me realise there was actually a wrong example in there. Let's prevent that! :)

Great work! :)


Not working in GTA san andreea

so , im running this library so that when i type ch01 it types chittychittybangbang
because i cant type it fast enough
ive tried every library and it still wont work even as admin

from pynput import keyboard

import pydirectinput
import time
import pyautogui
reg = []
keyboardc = keyboard.Controller()
runningmacro = False
def on_press(key):
try:
print('alphanumeric key {0} pressed'.format(
key.char))
if len(reg) == 8:
del reg[0]
tempa = [key.char]
reg.extend(tempa)
listToStr = ''.join([str(elem) for elem in reg])
print(listToStr)
if runningmacro == False:
if listToStr.endswith('ch01'):
typek('chittychittybangbang')
except:
print('special key {0} pressed'.format(key))
def typek(string):
runningmacro = True
pyautogui.write(string, interval=0.05)
runningmacro = True
runningmacro = False
def on_release(key):
print('{0} released'.format(
key))
if key == keyboard.Key.esc:
# Stop listener
return False
listener = keyboard.Listener(
on_press=on_press,
on_release=on_release)
listener.start()

can you reformat your code so it is readable. It is difficult to see what is in and out of scope of your functions to aid in diagnosing your issue

done

still not showing with indents

idk how to do that
On Mon, Jun 7, 2021, 12:35 jorg-j @.***> wrote:

still not showing with indents
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/asweigart/pyautogui/issues/564#issuecomment-855652721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUJCTZJAZAAKILSVBQHM53TRRVSVANCNFSM43ZWBJKQ
.

i can send the file
On Mon, Jun 7, 2021, 13:00 PranshuTheGamer @.***>
wrote:

idk how to do that
On Mon, Jun 7, 2021, 12:35 jorg-j @.***> wrote:

still not showing with indents
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/asweigart/pyautogui/issues/564#issuecomment-855652721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUJCTZJAZAAKILSVBQHM53TRRVSVANCNFSM43ZWBJKQ
.

stick it on https://www.file.io/ and drop the link in there if it's easier


Helm upgrades using --wait succeed without readiness checks passing if you downscale replicas to 0

Output of helm version:
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.21.3"}
Output of kubectl version:
Client Version: v1.28.3
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
EKS 1.28
I encountered this when testing if kube-downscaler would block pipelines due to scaling down pods before they became ready in downscale enabled environments, but pipelines always succeeded passing the scaled down env where pods never became ready before being terminated in response to kube-downscaler setting the replicas on the deployment to 0.
In this case helm releases were managed by fluxcd HelmRelease but I've read this should be using helm upgrade --wait.
I recreated by creating a bitnami/nginx helm chart via helm but then adding a non existent readiness check path in the values so that it would never become ready:
readinessProbe:
enabled: true
failureThreshold: 3
httpGet:
path: /non-existent-path
port: http
initialDelaySeconds: 90
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
I can make the 'helm upgrade --wait' succeed by simply scaling the nginx deployment to 0 whilst helm is waiting for the readiness checks to succeed.
If I don't scale it down then obviously the helm release fails after the default --wait timeout of 5 minutes.
I haven't looked at the code yet but I could make a PR to make helm fail if readiness checks don't pass, regardless if pods get terminated before the helm timeout elapses by being scaled down by the deployment.
But I'm not sure if this has been considered before and the current behaviour is intended as the preferable way to deal with pods that are scaled down in the midst of a helm upgrade?

Is this a duplicate of https://github.com/helm/helm/issues/12747?

Helm is waiting on the deployment to be ready (like @banjoh points out in the linked issue). What alternate behavior are you proposing?

Is this a duplicate of #12747?

It's very similar, changing the code to fix the behaviour here would likely fix that issue too :)
Also I noticed on the other issue there was mention of that example having 1 replica with 1 unavailable. I have tested with multiple replicas and setting maxUnavailable to 0 so this isn't the issue here as when you scale a deployment down to 0 it has status:
Replicas:       0 desired | 0 updated | 0 total | 0 available | 0 unavailable
So because the desired replicas is 0 after scaling it's always 0 unavailable

Helm is waiting on the deployment to be ready (like @banjoh points out in the linked issue). What alternate behavior are you proposing?

I can't think of a nice way to make it work with downscaler tbh but I'd prefer if it failed and I had to make a workaround in the downscaler implementation than helm succeeds without pods becoming ready.
The only proposed solution I can think of is perhaps looking at the labels from the deployment and then checking that atleast 1 of or all the initially desired number of pods pods becomes ready.
I don't know how cleanly this can be done and if it's worth it for the downscaler edge case

Maybe the solution would be to disable downscaler during install and then enable it in a post-install hook?

Yes my solution was going to be to add annotations in the GitHub workflow
to do that when downscaler gets enabled by customer.
I think checking the deployment status is the correct behaviour from helm
and working around the downscaler edge case isn’t a good idea!
I’ll close the issue?
Thanks
On Fri, 2 Feb 2024 at 19:55, Ian Zink @.***> wrote:

Maybe the solution would be to disable downscaler during install and then
enable it in a post-install hook?
—
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/12768#issuecomment-1924585274, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALAZUVAIZEYFQY7TJIDOQWTYRVACTAVCNFSM6AAAAABCUZPYAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGU4DKMRXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Maybe the solution would be to disable downscaler during install and then enable it in a post-install hook?

Yes my solution was going to be to add annotations in the GitHub workflow to do that when downscaler gets enabled by customer.
I think checking the deployment status is the correct behaviour from helm and working around the downscaler edge case isn’t a good idea!
I’ll close the issue?
Thanks


Feature build tools

Fixes #
Running mvn site is working as expected
Proposed Changes

Following the guide here for multi-module pmd configurations https://maven.apache.org/plugins/maven-pmd-plugin/examples/multi-module-config.html


Parameter debug is set to true for insertAll by Standard

Hi I wonder if the parameter debug is supposed to be set to true by standard for function insertAll?
 Future<int> insertAll({     required String table,     required List<Map<String, dynamic>> insertData,     replace = false,     debug = true,   }) async {

This is an error and should be false by default. Immediately release a new version to fix it.


Search  Relevance Tweaks

Search Terms
Search, Relevance, Lunr
Problem
My colleagues and I have spent the last few weeks rigging up TypeDoc on our TypeScript library. For the most part it works beautifully and we're astonished how well this project works out of the box, but we've been having some trouble with a few quirks in the search feature:

exact matches don't seem to get a boost in relevance. We have a class called "Button", but when we search for "button", the main result we're interested in gets muscled down to the 53rd slot by other minor results that have "button" in their name (eg. "Foo.primaryButton"),
there's no way to adjust the number of search results, and no "View all" option
classes don't seem to get a boost over props and other minor features
there's no way to boost on things like categories

I understand that not everyone wants search to work the same way, so I thought this might be a good candidate for a plugin, but once I looked into it I realized that plugins seem to have more to do with reflection than runtime adjustments like this.
So, before we dive in and start preparing a PR, I thought I'd see if you folks can provide any insight or background.
Suggested Solution
Off the top of my head, I would like to see some kind of search configuration on typedoc.json. Maybe something like this:
{
  ...
  "search": {
    "maxResults": 10,
    "weights": {
     "isClass": 1.1,
     "exactMatch": 2.1,
     "byCategory": {
        "component": 3.4,
        "coreComponent": 4
      }
    }
  }
}

Thoughts?

exact matches don't seem to get a boost in relevance. We have a class called "Button", but when we search for "button", the main result we're interested in gets muscled down to the 53rd slot by other minor results that have "button" in their name (eg. "Foo.primaryButton"),
classes don't seem to get a boost over props and other minor features

These two I'd definitely like to do by default. I don't think there's anyone who would not like these changes.

there's no way to adjust the number of search results

It seems like the optimal number of results to display to me will depend on the screen height/rendered results... I'm certainly open to adjusting this, not sure an option makes sense.

there's no way to boost on things like categories

Seems like a reasonable request :+1:

Implementation wise - TypeDoc's current option parser doesn't play nicely with nested objects. Otherwise, I like it

Thanks for the feedback. I'm up to my elbows in the code at the moment, and will try to produce a PR relatively soon.

@shmax now that this has been around for a bit, do you have any thoughts on a good default for searchGroupBoosts? I just noticed that we never ended up creating a default map when updating it to work with 0.23's @group tag

Oh, good question; I figured you would just want to leave it blank and let users season to taste,, but I can look into it a bit when I get a chance. I'll have to do some debugging, anyway, because I tried to use the category boosts the other day in our project, and it didn't seem to do anything. Let me see if I can get back to you this weekend...

It's definitely a good thing that it's configurable, but I think some reasonable default to produce better search results without requiring configuration is a good thing :)

How would you prefer to handle defaults? Two main possibilities off the top of my head:

set defaultValue when we invoke options.addDeclaration. Easy enough, but I assume that all the defaults will get written over as soon as the user makes any kind of edit.
do something inline in the JavascriptIndexPlugin, eg:

 const kindBoost = kindBoosts[kinds[reflection.kind] ?? ""] ?? defaultGroupBoosts[reflection.kind];

but then you would have a fair amount of bloat in search.js, so maybe we should move the default information into the runtime search stuff?
Let me know what ya think.

The defaultValue is the way to go I think, with the default boosts documented on the website. gzip ought to take care of the extra bloat, so I don't think that's much of an issue

Going to go ahead and close this, PR welcome if you (or anyone) would like to propose some defaults, but just having exact matches boosted does pretty well.


API: check identifier validation

check with .isidentifier

[x] experiment id
[x] metic name

closed by #75


(3) URL using bad/illegal format or missing URL

I keep getting "(3) URL using bad/illegal format or missing URL" when trying to get my access and refresh token. I've tried using terminal on my pc and on the homebridge site.

As this is not an issue with this plugin itself I will be closing it.


[test_operator] Pass externalPlugin to the tempest operator config

This allows using an arbitrary version of a plugin without overriding the whole cifmw_test_operator_tempest_config.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

Testing is being done on: https://github.com/openstack-k8s-operators/telemetry-operator/pull/284
Logs can be browsed here: https://review.rdoproject.org/zuul/buildset/bc255a9339b24efdaa59dacba2d4bd5b
The telemetry-operator PR actually depends on https://github.com/openstack-k8s-operators/ci-framework/pull/1065, which does the same thing as this PR, but had other changes on it that became irrelevant.

Overall looks good to me!:) Let's wait on how the job in the depends-on PR ends.

/lgtm
lgtm

There seems to be a spelling issue:
<htmlcontent> docs/_build/html/roles/test_operator.html: html>body>div>section>div>div>div>div>section>section>ul>li>p
--------------------------------------------------------------------------------
changeRefspec
changeRepository
--------------------------------------------------------------------------------

The en-custom.txt file probably needs to be updated.


Immovable?

All slime blocks seem to be immovable?

Works fine for me. Do you have any other mods installed that may be causing some kind of conflict here?


[Feature]  where can get the scores of the outputs for "outputs = model.generate(..)" or "model.stream_generate()" or "model.chat()"

Is your feature request related to a problem? Please describe.
I need the scores of the outputs do some choice.
Solutions
the outputs  from  functions of
"model.generate(..)"
"model.stream_generate()"
"model.chat()" all has no the items
Additional context
No response

Could you post the code of generate score? Very thankful !!!

Your meaning score is logits probs?


declare EventPublishingException in NakadiClient.publish

declare EventPublishingException in NakadiClient.publish
https://github.com/zalando-nakadi/fahrschein/issues/270

:+1:

:+1:

👍


Doesn't seem to work with Python "Anonymous Files"

Issue Type: Bug
Open new tab > Change language to Python > Write code...
Example code I used as a test:
x = 's'
x.

Suggestions I got was:
datetime
PyZipFile
ZipFile

Extension version: 1.2.10
VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.84GB (4.24GB free)

Process Argv
--crash-reporter-id 890fbd32-b85c-48d5-894b-184331acf6c0

Screen Reader
no

VM
80%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221877
python763:30178808
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
python504:30227505
vswsl492cf:30211402
wsl2prompt:30224612
pythonvsdeb440:30237827
unusedpromptcf:30224611
folderexplorercf:30224615
openfilemenu:30224647
pythonvsded773cf:30236630
vsjup459:30237187

A quick update:
I tried saving the file and then it suddenly worked.

@savannahostrowski @jakebailey - adding to bubble up this feature request to the Python Language Server team.

@savannahostrowski @jakebailey - adding to bubble up this feature request to the Python Language Server team.

@SonOfDiablo, Thank you for providing this feedback and providing the work around. The IntelliCode team is looking into this. Thanks!

@SonOfDiablo, Thank you for providing this feedback and providing the work around. The IntelliCode team is looking into this. Thanks!

This is microsoft/pylance-release#739, and IC would be fixed with it.

This is microsoft/pylance-release#739, and IC would be fixed with it.

doc-bug to document current behavior as described by this bug.

This was fixed in Pylance 2021.1.0 and should no longer be an issue.

Based on @savannahostrowski comment, this should no longer need documenting as it's fixed. Closing


[error message feedback] provide feedback for InvalidFileLink

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Problem:
This error is incorrect, the file which includes includes/dns-powershell-setup-include.md is correctly rendered: https://review.docs.microsoft.com/en-us/azure/dns/private-dns-getstarted-powershell?branch=pr-en-us-64565
This needs to be fixed, or at least ignored so that this PR can proceed.
Log code info
(This is auto filled, no need to modify)

Severity
Type
Code
Category
File
Message
Source
Line
Time

Warning
Unspecified
InvalidFileLink
Markdown
includes/dns-powershell-setup-include.md
Invalid file link:(~/includes/requires-azurerm.md).
BuildCore.Build Document.LinkPhaseHandlerWithIncremental.ConceptualDocumentProcessor.Save
17
01/30/2019 17:11:13

Link to report
(This is auto filled, no need to modify)
report url

thank you for the feedback, we are constantly working on improving our messaging and document for build reports.  Providing this feedback helps us track messaging that requires improvement.


use graphical icon that not just repeats the name

the old icon just uses the text "hello" black on white.
while maybe stylish,
set in context where the icon is usually used,
this looks repetitive and a bit weird,
esp. as the icon has also white background.
of course, this is not "wrong" and other apps can pick up this style, but we should not use that as a default pattern we encourage ppl to use.
also, my idea is to have sth more "funny" and "shiny", not sure if that was successful :)
starburst inspired from https://codepen.io/lethargic/pen/aBybeK , the hand is just an emoji,
put together with gimp - if someone want to do a vector or has another idea, this is very welcome :)
before / after:

closes #41

btw, hope there are no weird copyright nonsense with that emoji?

hm, good questions, idk. if you know of a  similar "hand" where we know that it is free-for-being-used, i can recreate the icon on top of that. just to be sure, as this questions is raised now :) - i assume it is okay to use an emoji glyph the way we are doing above.

answering myself: i think we should be able to use the emoji from "Noto" license-wise,  https://github.com/googlefonts/noto-emoji , that emoji even fits better to the backgou d as being more flat


Does not work in AOT(IL2CPP)

May be create separate method for structs? Or may be there is general method to work with all types?

https://github.com/ltrzesniewski/InlineIL.Fody cannot be made generic https://gitlab.com/dzmitry-lahoda/UnTools/blob/master/src/StructLayoutInspector.cs . Could I make it on IL level?
Next works for unmanaged structs. May be will work for managed either, classes (after some modification regarding equality)?

    public struct StructFieldInfo
    {
        public int Offset;
        public ushort Size;
        public Type Type;
    }

    public static class StructLayoutInspector<TComponent>
        where TComponent : unmanaged
    {
        public static IReadOnlyList<StructFieldInfo> FieldsInfo { get; private set; }

        public static IReadOnlyList<StructFieldInfo> Parse()
        {
            if (FieldsInfo == null)
            {
                var offsets = 0;
                var componentType = typeof(TComponent);
                var fieldsInfo = new List<StructFieldInfo>();
                if (!IsPrimitive(componentType))
                {
                    var typeHierarchy = new List<Type> { componentType };
                    var fieldsHierarchy = new List<FieldInfo>();
                    Recurse<TComponent>(ref offsets, typeHierarchy, fieldsHierarchy, fieldsInfo);
                }

                FieldsInfo = fieldsInfo;
            }

            return FieldsInfo;
        }

        private static void Recurse<TRoot>(ref int offsets, List<Type> typeHierarchy, List<FieldInfo> fieldsHierarchy, List<StructFieldInfo> fieldsInfo)
            where TRoot : unmanaged
        {
            var fields = typeHierarchy.Last().GetFields();

            foreach (var field in fields)
            {
                var fieldType = field.FieldType;

                if (!fieldType.IsValueType)
                {
                    throw new InvalidProgramException($"TODO: good text to say that all fields should be stucts");
                }

                if (IsPrimitive(fieldType))
                {
                    fieldsHierarchy.Add(field);
                    var newOffset = FindOffset<TRoot>(offsets, fieldsHierarchy);
                    fieldsHierarchy.RemoveAt(fieldsHierarchy.Count() - 1);

                    var fieldOffsetAttribute =
                                (FieldOffsetAttribute)field
                                .GetCustomAttributes(typeof(FieldOffsetAttribute), true)
                                .SingleOrDefault();
                    var offset = fieldOffsetAttribute != null ? fieldOffsetAttribute.Value : newOffset;
                    var size = fieldType.IsEnum ? Marshal.SizeOf(fieldType.GetEnumUnderlyingType()) : Marshal.SizeOf(fieldType);
                    var info = new StructFieldInfo { Offset = offset, Size = (ushort)size, Type = fieldType };
                    fieldsInfo.Add(info);
                    offset = newOffset + size;
                }
                else
                {
                    typeHierarchy.Add(field.FieldType);
                    fieldsHierarchy.Add(field);
                    Recurse<TRoot>(ref offsets, typeHierarchy, fieldsHierarchy, fieldsInfo);
                    typeHierarchy.RemoveAt(typeHierarchy.Count() - 1);
                    fieldsHierarchy.RemoveAt(fieldsHierarchy.Count() - 1);
                }
            }
        }

        private static bool IsPrimitive(Type componentType)
        {
            return componentType == typeof(decimal)
                                || componentType == typeof(char)
                                || componentType.IsEnum
                                || componentType.IsPrimitive
                                || componentType == typeof(TimeSpan) || componentType == typeof(DateTime) || componentType == typeof(DateTimeOffset);
        }

        // https://stackoverflow.com/questions/18937935/how-to-mutate-a-boxed-struct-using-il
        // https://docs.unity3d.com/2018.3/Documentation/ScriptReference/Unity.Collections.LowLevel.Unsafe.UnsafeUtility.html
        private static unsafe int FindOffset<T>(int offsets, List<FieldInfo> fieldsHierarchy) where T : unmanaged
        {

            T dummy = default;
            ref var dummyRef = ref Unsafe.As<T, byte>(ref dummy);
            var size = Unsafe.SizeOf<T>();
            Zero(ref dummyRef, size);

            for (int i = offsets; i < size; i++)
            {
                object value1 = dummy;
                foreach (var field in fieldsHierarchy)
                {
                    value1 = field.GetValue(value1);
                }

                dummyRef = byte.MaxValue;

                object value2 = dummy;
                foreach (var field in fieldsHierarchy)
                {
                    value2 = field.GetValue(value2);
                }

                // TODO: uwrap to bytes and compare byte by byte
                if (!value1.Equals(value2))
                {
                    offsets = offsets + i;
                    break;
                }

                dummyRef = ref Unsafe.Add(ref dummyRef, 1);
            }

            return offsets;
        }

        // paddings are not zeroed and need to pad after each iteration of searchin offset
        private static void Zero(ref byte dummyByte, int size)
        {
            for (int i = 0; i < size; i++)
            {
                dummyByte = 0;
                Unsafe.Add(ref dummyByte, 1);
            }
        }
    }
}

@dzmitry-lahoda to be honest, I'm not 100% sure what is the question:((

TypeLayout generates IL during run time. Is it possible to generate IL during compilation to allow use of TypeLayout in AOT?
I have found that for unmanaged structs I can use unsafe to get layout. I guess it can be supported up to managed structs, but I have not done that.
I propose TypeLayout via Unsafe could be nice addition to ObjectLayoutInspector

@SergeyTeplyakov, would you accept a patch with StructLayoutInspector similar to TypeLayout (with same output pattern), but working by mechanism as described above?

I propose TypeLayout via Unsafe could be nice addition to ObjectLayoutInspector

I think it would be a nice addition and I will definitely appreciate such kind of change.

I guess I can support classes either, but need find out how to access no blittable classes on the heap

@SergeyTeplyakov would you mind to look into my pull?
It does not supports classes (as I do no know how to add these), partially supports nullables (can fix some time later), and works on Unity IL2CPP ARM 32/64 bit Android/iOS (will retest this again soon).

@dzmitry-lahoda I've added a bunch of comments. None of them are critical, but I would like to address at least some of them. And I'll take a look at other changes because I reviewed the PR yesterday and you've pushed a bunch of changes after that.

thanks. I will fix these. Want to add that nullables totally broken recursion and need double level of it to pass all info (may be wrap - field and property into something) - so it looks not good (but needed to support nullables - test commented out now).

I do not know now how to differentiate what structure owns padding. See padding 2 and 4. Such padding are irrelevant for some purpose (my main is serialization), but for showing layout may have some meaning.
Type layout for 'VeryVeryComplexStruct'
 Size: 128 bytes. Paddings: 33 bytes (%25 of empty space)
 |=====================================================|
 |  0-11: StructWithExplicitLayout one (12 bytes)      |
 | |================================|                  |
 | |     0: Byte m_byte1 (1 byte)   |                  |
 | |--------------------------------|                  |
 | |     0: Byte m_byte1_1 (1 byte) |                  |
 | |--------------------------------|                  |
 | |     1: Byte m_byte2 (1 byte)   |                  |
 | |--------------------------------|                  |
 | |   2-3: Int16 m_short (2 bytes) |                  |
 | |--------------------------------|                  |
 | |   4-5: padding (2 bytes)       |                  |
 | |--------------------------------|                  |
 | |   6-9: Int32 m_int (4 bytes)   |                  |
 | |--------------------------------|                  |
 | | 10-11: padding (2 bytes)       |                  |
 | |================================|                  |
 |-----------------------------------------------------|
 | 12-15: padding (4 bytes)                            |
 |-----------------------------------------------------|
 | 16-39: DoubleByteStructByteStruct two (24 bytes)    |
 | |========================================|          |
 | |  0-15: DoubleByteStruct one (16 bytes) |          |

Interesting methods Unity:
https://docs.unity3d.com/2018.3/Documentation/ScriptReference/Unity.Collections.LowLevel.Unsafe.UnsafeUtility.GetFieldOffset.html  (somehow should work in AOT)
https://docs.unity3d.com/2018.3/Documentation/ScriptReference/Unity.Collections.LowLevel.Unsafe.UnsafeUtility.PinGCObjectAndGetAddress.html (I guess somehow may work with non blittable, unlike GCHandle, but I may be wrong).

Recursive is no much slower than flat. So will be on by default always. As then goes to flat as needed. Will simplify code. Will have real tree inside (need to exected FieldLayoutBase to support parent child?). For crossed paddings (as there is no need to be 100% sure where to split - will 2 default padding rulse for x86 or ARM - somthing like to next 4 bytes split (or use Explicit layout if exists)).
                              Method |     Mean |     Error |    StdDev | Gen 0/1k Op | Gen 1/1k Op | Gen 2/1k Op | Allocated Memory/Op |
------------------------------------ |---------:|----------:|----------:|------------:|------------:|------------:|--------------------:|
                    TypeLayoutStruct | 5.031 ms | 0.1232 ms | 0.1152 ms |     46.8750 |     23.4375 |           - |           149.12 KB |
            TypeLayoutPaddingsStruct | 5.008 ms | 0.0681 ms | 0.0569 ms |     46.8750 |     23.4375 |           - |           149.12 KB |
                  UnsafeLayoutStruct | 1.067 ms | 0.0065 ms | 0.0058 ms |    148.4375 |           - |           - |           459.23 KB |
          UnsafeLayoutPaddingsStruct | 1.092 ms | 0.0067 ms | 0.0063 ms |    148.4375 |           - |           - |           459.59 KB |
 UnsafeLayoutPaddingsRecursiveStruct | 1.110 ms | 0.0221 ms | 0.0410 ms |    171.8750 |           - |           - |           530.68 KB |

i am testing UnsafeLayout on devices (common iOSes and Androids with IL2CPP). Will close story than.

#26

Combo of UnsafeLayout and https://github.com/dzmitry-lahoda/NetStack allowed to create ultra fast generic struct serialize. And now seems UnsafeLayout will work for creating ultra fast tagged Union and OverlappedUnion for C#, kind of closed world fast marker interface pattern, also as fast as manual coding of all boilerplate (which can be generate in some time in future).


Jest encountered an unexpected token from vue 2 application

I'm trying to update the node version from 12 to 16 and all node packages. I'm able to build successfully and clean up errors from
ESLint but while running jest most of the test failed due to that import underscore issue.

This is jest failing, not eslint, so you'll need to file an issue on jest.
Either way, I'd suggest updating packages one at a time, and jumping from node 12 to 14 to 16, instead of trying to do it all at once.

This is jest failing, not eslint, so you'll need to file an issue on jest.
Either way, I'd suggest updating packages one at a time, and jumping from node 12 to 14 to 16, instead of trying to do it all at once.
Could you please direct me any places where I can post?

@ashif25 jest's repo is https://github.com/facebook/jest


Visual Studio 2019 Automatically Switches To Dark Theme

Hello,
Visual Studio 2019 Enterprise automatically switches to dark theme, which is very annoying.
Please fix it.
Regards,
Venu

That sounds like a VS bug and should be filed on developercommunity.visualstudio.com


Mac tool_integration_tests_4_4 is timing out

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac tool_integration_tests_4_4/1476/overview

This check used to complete just fine in 22-25 minutes (example: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac tool_integration_tests_4_4/1473/overview), but after https://github.com/flutter/flutter/pull/88048 is times out after 30 minutes with only 75% done.
It doesn't appear to be hanging at anything in particular, looking at the log, steps that just to be fast are now taking a very long time. Is there something wrong with the Bot "build799-m9"?
/cc @CaseyHillers @godofredoc

Caching issue maybe? For example iOS app validation build in debug mode (setUpAll)  took 8:00 in the failing run, but only 50 seconds in the previous commit.
All that test setup is doing is running flutter create once:
https://github.com/flutter/flutter/blob/b08366ce7b706ffb4304741b89f275847f23f1a3/packages/flutter_tools/test/integration.shard/ios_content_validation_test.dart#L32-L43

What jumps out from the log: the test/integration.shard/ios_content_validation_test.dart: iOS app validation build in debug mode (setUpAll) used to complete in ~55s, but now takes almost 8 minutes. Other steps are also slower.

@jmagman I noticed that too, but it doesn't seem to be limited to just that step, everything just seems to take longer.

@jmagman by cache issues do you mean things in the cache that should have been deleted?
caching at the bot level does not affect the tests execution.

The 3 failures are coming from the same bot. I blocked that bot, can we retry the task to see if some other bots succeed?

@godofredoc I requested another re-run. Will report back.

Interestingly, it just passed on the blocked bot again: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac tool_integration_tests_4_4/1477/overview

Reduced priority for now since tree is green again.

by cache issues do you mean things in the cache that should have been deleted?

I was thinking pub cache, but that may not make sense.  It should never take 8 minutes to run flutter create, even if the tool had to be built.

I investigated this as a possible issue from the ci.yaml migration, and I don't think it's an issue. The caches and dependencies are the same on the task runs.
Swarming task post-ci-migration
Swarming task pre-ci-migration
@godofredoc is the best practice to just quarantine the bot and remove it from the active pool?

We are not sure it is the bot, before quarantining the bot we need to validate running the build with led using the same bot.
If the bot is in bad state then we can quarantine it.

Since the framework directory is cached, it could help the bot complete the task on repeat runs.

The flutter source is checked out in star_dir https://cs.opensource.google/flutter/recipes/+/master:recipes/flutter/flutter_drone.py;l=61 caches should not be affecting the execution.

This is most likely a test problem. The same issue has been happening in different bots:

https://chromium-swarm.appspot.com/bot?id=build799-m9
https://chromium-swarm.appspot.com/bot?id=build811-m9

Why would there be so much variability in testing time between builds?  The tests haven't changed.
We could just throw a 5th shard at this and see what happens.

Maybe the underlying functionality the test is using? I don't think adding a new shard will help, from the messages above it seems like a single test has been taking taking longer than usual ios_content_validation_test.dart.

Seems like this test has been passing correctly for the last few iterations. Did we change something that could have fixed this issue indirectly?

@jmagman Can we disable ios_content_validation_test.dart, on every failure that single test has been taking 15+ mins?

@jmagman Can we disable ios_content_validation_test.dart, on every failure that single test has been taking 15+ mins?

I still think there's something wrong with these bots, or the testing harness or something environmental.  This test takes ~1:30 on my machine:
$ time flutter test test/integration.shard/ios_content_validation_test.dart
01:20 +10 ~1: All tests passed!
flutter test test/integration.shard/ios_content_validation_test.dart  18.28s user 9.85s system 34% cpu 1:21.75 total

The whole group (every test in that file, together) already has a 5 minute timeout.  So if it was something with just that test, the test group would be failing for taking more than 5 minutes instead of the whole shard timing out?
https://github.com/flutter/flutter/blob/4053b4b16cbec129f03cd7201ab1b8250bda72e8/packages/flutter_tools/test/integration.shard/ios_content_validation_test.dart#L249

@jmagman Can we disable ios_content_validation_test.dart, on every failure that single test has been taking 15+ mins?

I don't want to turn it off for any length of time. It's one of the most valuable tests I've written for iOS/tooling in terms of finding bugs...
I could move the logic back into https://github.com/flutter/flutter/blob/master/dev/devicelab/bin/tasks/ios_content_validation_test.dart but that's against the spirit of https://github.com/flutter/flutter/issues/65790. I originally moved it in https://github.com/flutter/flutter/pull/73577.
What if we shuffle these tests to see if the failing shard follows that test?  https://github.com/flutter/flutter/pull/88398

/cc @christopherfujino

We could also apply #86793 seed shuffling logic to the tool tests to randomize which tests are in which shard.  That doesn't particular help this timeout, and it would spread the flakiness around, but it might help find some common tests that are tickling this problem.
We intended to move more and more tooling tests out of devicelab into these subshards, so they will get longer and longer.  But it's the variability between test runs that's concerning for this particular issue.

For example iOS app validation build in debug mode (setUpAll)  took 8:00 in the failing run, but only 50 seconds in the previous commit.

There is a similar behavior in build_tests_shard_and_subshard_3_4, in that test the smoke tests take 2x the time in a failing build compared to the one that passes:

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8838938386860890208/+/u/run_test.dart_for_build_tests_shard_and_subshard_3_4/test_stdout(failing build)
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8838610942718216720/+/u/run_test.dart_for_build_tests_shard_and_subshard_3_4/test_stdout(passing build)

Do you know of anything that could be affecting the performance of dart in the failing builds?

Let's add some verbosity and print all the things: https://github.com/flutter/flutter/pull/88404

Here's a failing run with verbosity on a particular commit:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8838533891013746177/+/u/run_test.dart_for_tool_integration_tests_shard_and_subshard_4_4/test_stdout
And a successful run on the same commit:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8838531073745422384/+/u/run_test.dart_for_tool_integration_tests_shard_and_subshard_4_4/test_stdout
Some example of the same work being done on the successful vs failing runs:

rsync
Succeeding
[ +659 ms] Exit code 0 from: rsync -av --delete /opt/s/w/ir/x/t/flutter_tools.EhR30e/flutter_artifacts.zip.Ah1WMC/Flutter.xcframework /opt/s/w/ir/x/w/flutter/bin/cache/artifacts/engine/ios

Failing
[+16853 ms] Exit code 0 from: rsync -av --delete /opt/s/w/ir/x/t/flutter_tools.eoLO3p/flutter_artifacts.zip.s8s9S4/Flutter.xcframework /opt/s/w/ir/x/w/flutter/bin/cache/artifacts/engine/ios

release_unpack_ios
Succeeding
[  +35 ms] release_unpack_ios: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /opt/s/w/ir/x/w/flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart,/opt/s/w/ir/x/w/flutter/bin/internal/engine.version}
[+3172 ms] Skipping target: gen_localizations

Failing
[  +25 ms] release_unpack_ios: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /opt/s/w/ir/x/w/flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart,/opt/s/w/ir/x/w/flutter/bin/internal/engine.version}
[+129488 ms] Skipping target: gen_localizations

xcrun cc
Succeeding
[ +233 ms] executing: xcrun cc -arch armv7 -miphoneos-version-min=9.0 -isysroot /opt/s/w/ir/cache/osx_sdk/XCode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk -c /opt/s/w/ir/x/t/flutter_ios_content_validation.dwFK0E/hello/.dart_tool/flutter_build/0361048dda7d733469360e2cadfcc95b/armv7/snapshot_assembly.S -o /opt/s/w/ir/x/t/flutter_ios_content_validation.dwFK0E/hello/.dart_tool/flutter_build/0361048dda7d733469360e2cadfcc95b/armv7/snapshot_assembly.o
[ +894 ms] executing: xcrun clang -arch arm64 -miphoneos-version-min=9.0 -isysroot /opt/s/w/ir/cache/osx_sdk/XCode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk -dynamiclib -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -install_name @rpath/App.framework/App -o /opt/s/w/ir/x/t/flutter_ios_content_validation.dwFK0E/hello/.dart_tool/flutter_build/0361048dda7d733469360e2cadfcc95b/arm64/App.framework/App /opt/s/w/ir/x/t/flutter_ios_content_validation.dwFK0E/hello/.dart_tool/flutter_build/0361048dda7d733469360e2cadfcc95b/arm64/snapshot_assembly.o

Failing
[ +279 ms] executing: xcrun cc -arch armv7 -miphoneos-version-min=9.0 -isysroot /opt/s/w/ir/cache/osx_sdk/XCode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk -c /opt/s/w/ir/x/t/flutter_ios_content_validation.P5hGKZ/hello/.dart_tool/flutter_build/1fa5f9a9ac702b3243a31b7ac575c11d/armv7/snapshot_assembly.S -o /opt/s/w/ir/x/t/flutter_ios_content_validation.P5hGKZ/hello/.dart_tool/flutter_build/1fa5f9a9ac702b3243a31b7ac575c11d/armv7/snapshot_assembly.o
[+10303 ms] executing: xcrun clang -arch arm64 -miphoneos-version-min=9.0 -isysroot /opt/s/w/ir/cache/osx_sdk/XCode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS14.3.sdk -dynamiclib -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -install_name @rpath/App.framework/App -o /opt/s/w/ir/x/t/flutter_ios_content_validation.P5hGKZ/hello/.dart_tool/flutter_build/1fa5f9a9ac702b3243a31b7ac575c11d/arm64/App.framework/App /opt/s/w/ir/x/t/flutter_ios_content_validation.P5hGKZ/hello/.dart_tool/flutter_build/1fa5f9a9ac702b3243a31b7ac575c11d/arm64/snapshot_assembly.o

debug_unpack_ios
Succeeding
[  +36 ms] debug_unpack_ios: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /opt/s/w/ir/x/w/flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart,/opt/s/w/ir/x/w/flutter/bin/internal/engine.version}
[+1812 ms] Skipping target: gen_localizations

Failing
[  +27 ms] debug_unpack_ios: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /opt/s/w/ir/x/w/flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart,/opt/s/w/ir/x/w/flutter/bin/internal/engine.version}
[+25727 ms] Skipping target: gen_localizations

deferred_components_test
Successful (1:02, 00:51)
24:00 +39 ~1: loading test/integration.shard/deferred_components_test.dart
24:00 +39 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle missing golden fails
...
25:02 +40 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle missing golden fails
25:02 +40 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle all targets succeeds
...
25:53 +41 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle all targets succeeds
25:53 +41 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle mismatched golden fails

Failing (1:03, 0:57)
08:19 +39 ~1: loading test/integration.shard/deferred_components_test.dart
08:19 +39 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle missing golden fails
...
09:22 +40 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle missing golden fails
09:22 +40 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle all targets succeeds
...
10:19 +41 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle all targets succeeds
10:19 +41 ~1: test/integration.shard/deferred_components_test.dart: simple build appbundle mismatched golden fails

Various parts of ios_content_validation_test seem slower.  It's not just dart, it's rsync (which should just be I/O), it's Xcode commands, it's compilation.  However the following deferred_components_test test seems about the same.
I can pull this test into its own shard, but it seems weird that it's so variable...

Various parts of ios_content_validation_test seem slower. It's not just dart, it's rsync (which should just be I/O), it's Xcode commands, it's compilation. However the following deferred_components_test test seems about the same.

Given that it's multiple steps/sub-processes that are slower, maybe it's an OS-level process that's simultaneously running and slowing down the system?

Looks like the timing out build had fseventsd running:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8838533891013746177/+/u/OS_info/stdout
While the passing build had it sleeping:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8838531073745422384/+/u/OS_info/stdout
Could that be it?

Looks like that's the daemon that is used for filesystem watchers, so that would definitely explain rsync going slowly...
https://techblog.willshouse.com/2011/05/05/what-is-fseventsd/

I'm not sure what's using this daemon, but it looks like you can block fsevent logging on a volume: https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/FSEvents_ProgGuide/FileSystemEventSecurity/FileSystemEventSecurity.html#//apple_ref/doc/uid/TP40005289-CH6-SW5

The CPU usage is a 4% higher in the failing case, @jmagman @yjbanov do you see any potential leaked processes here https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8838533891013746177/+/u/OS_info/stdout?
I/O throughput sounds like a potential culprit, the test step keeps all the logs in memory to be able to collect a summary of the standard output at the end of step execution. If that output becomes too big it will eventually start writing to disk.
This is the disk data from the passing task bot: Disks: 2015748/17G read, 329949/24G written.
This is the disk data from the failing task bot: Disks: 1346665/8307M read, 24152/675M written.

It seems like disks metrics for the same bot are changing in the passing tasks compared to the failing ones.
Bot: build810-m9, https://chromium-swarm.appspot.com/bot?id=build810-m9
Passing task disk data: Disks: 2052769/17G read, 364079/25G written.
Failing task disk data: Disks: 1346665/8307M read, 24152/675M written.

@godofredoc did you see my previous comments regarding fseventsd?

Looks like a duplicate of https://github.com/flutter/flutter/issues/88286


Fixed segmentation fault when eigen values are less than 1

Hey @krish8484, thanks for the pull request, did you close it on purpose?

Ah, I didn't, must be by mistake.
Reopening it.


pythonPackages.varint: init at 1.0.2

Motivation for this change
This is needed for adding py-multihash package. https://github.com/NixOS/nixpkgs/pull/83203
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Nit-pick: typo in commit message: pyhton -> python
Hi @jonringer
done. Thanks.
For future i will also try to use nitpick offline before pushing.

Does this package have any tests?
Result of nixpkgs-review pr 83197 1

3 package built:

python27Packages.varint
python37Packages.varint
python38Packages.varint

@GrahamcOfBorg build python3Packages.varint

Ran 0 tests in 0.000s

No tests are found. Either the test runner cannot find tests and needs to be patched, or there simply are no tests in which case the tests need to be disabled. Do include a comment explaining why the tests are disabled.

tests

@FRidh , I have disabled the check Phase as there are no tests. Also added pythonImportsCheck.
Thanks.

Hi @jonringer , I have updated as suggested. Thanks.


Docs: revised join command

What/Why/How?
Reference
Testing
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

This pr seems to be ready as well


Harmony: Goal preview header

PR includes

[x] Feature

Related issues
Resolve #2311
QA Instructions, Screenshots, Recordings
GoalPreview RU locale

GoalPreview EN locale

GoalPreview change state
https://github.com/taskany-inc/issues/assets/95316053/7b4e8b2a-4c3e-4b1e-899e-db2a34678207
GoalPage RU locale

GoalPage showing 2 projects EN locale


camera cant detect qr

Hi i try generate vcard qr .But when the qr content is larger, the qr reader is not able to detect. Any solution?example
http://postimg.org/image/g2t534lzb/

Hi,
first of all sorry for the late.
I tried to scan your QRCode with an iPhone 6 and an iPad Mini Retina 2; it works great. Which kind of devices are you using?


Add Img2vector tools

Img2Vector tools could convert imgae directory into Vectorized RDD，for example：
Images stored in hdfs://namenode:9000/user/xxx/images/
scala> import ml.dmlc.mxnet.spark.utils.Img2Vector
scala> val sc = new SparkContext(conf)
scala> val imagesRDD = Img2Vector.getRGBArray(sc, "hdfs://namenode:9000/user/xxx/images/")

There exists some scala code style check failure. Please refer to the travis-ci for more information.
And could you make the description you wrote here as a brief javadoc for Img2Vector.getRGBArray?
Thank you!


Question: Is it possible to force update of an observabe (.obs) value.

Say for some reason I wanted to use a .obs but did not want to wrap it in a RxController and use it in GetX, I just wanted to continue using my regular GetController and GetBuilder.
Now later on in the project, I have a value that I want to be observable, and the update(this) function was not enough because the observable is used in separate views, update(this) only causes the current view to update, a hot reload or other rebuild of some sort is needed for this to work.
How can I make the observable value change for all listeners and trigger rebuild?

I think I can do that:
Currently, all my views use:
class BaseView<T extends BaseModel> extends StatelessWidget {
  const BaseView({
    Key key,
    this.builder,
  }) : super(key: key);

  final Widget Function(T) builder;

  @override
  Widget build(BuildContext context) {
    return GetBuilder<T>(
      builder: builder,
    );
  }
}

And all my viewmodels use:
class BaseModel extends GetController {
  ViewState _state = ViewState.Idle;

  ViewState get state => _state;

  void setViewState(ViewState viewState) {
    _state = viewState;
    update(this);
  }
}

So I'm guessing I just create maybe ObservableBaseView and ObservableBaseModel that use GetX and RxController respectively. Any final thoughts?

In 30 seconds of work you can do a Builder together, but I will think if I will insert it in the library, because it will be heavier because it contains a mixin of two classes, and the creators of other state managers are doing anti Get campaign on Twitter and Reddit, that would be giving material to a giant text from them haha.
In case I don't insert it, you can use it immediately using this widget:
class MixinBuilder<T extends GetController> extends StatelessWidget {
  @required
  final Widget Function(T) builder;
  final bool global;
  final String id;
  final bool autoRemove;
  final void Function(State state) initState, dispose, didChangeDependencies;
  final void Function(GetBuilder oldWidget, State state) didUpdateWidget;
  final T init;
  const MixinBuilder({
    Key key,
    this.init,
    this.global = true,
    this.builder,
    this.autoRemove = true,
    this.initState,
    this.dispose,
    this.id,
    this.didChangeDependencies,
    this.didUpdateWidget,
  })  : assert(builder != null),
        super(key: key);

  @override
  Widget build(BuildContext context) {
    return GetBuilder<T>(
        init: init,
        global: global,
        autoRemove: autoRemove,
        initState: initState,
        dispose: dispose,
        id: id,
        didChangeDependencies: didChangeDependencies,
        didUpdateWidget: didUpdateWidget,
        builder: (controller) => obx(() => builder.call(controller)));
  }
}

Use GetController normally, and insert the observable variables into it normally, MixinBuilder will be rebuilt both when update.this is called, and when any variable changes.

Will try this out soon, anti-get haha. Why on earth would the do that.

Added on 2.10

Yay!!


Allow to hide nz-badge title

What problem does this feature solve?
The non-standalone nz-badge cannot hide the title which appears when hovering the badge.

NG-Zorro version: 8.5.2
What does the proposed API look like?
Allow a [nzText]="null" to explicitly hide the title on hover.
<nz-badge [nzCount]="5" [nzText]="null">
  foo bar
</nz-badge>

@krokofant Does set [nzCount]="0" work for you?

@hsuanxyz It's not the badge that cannot be hidden - it's the the title text. See this image and note the arrow:

Every time you hover badge you'll see a title and it can't be hidden.

I see, this is a bug and we'll fix this. Because it has the [nzTitle] property but does not work when the value is null


fix: Cast in SceneBuilder.PropagateLayer

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Fixes #9604

You can test this PR using the following package version. 11.0.999-cibuild0026959-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-nightly/nuget/v3/index.json) [PRBUILDID]


Update fedora img to fc32

What this PR does / why we need it:
Update the fedora VMI images from fc29 (which is unsupported) to fc32 (newly released).
Release note:

Update the VMI fedora image from fc29 to fc32.

/retest

@maiqueb I see that there is still an issue with the guest agent. Perhaps you can try updating the guest agent package here as well?

@maiqueb I see that there is still an issue with the guest agent. Perhaps you can try updating the guest agent package here as well?

I've created this bug on fedora's 32 qemu-guest-agent.
I'm not sure if this fix would not simply mask the symptom, and hide a real bug.
Would you accept if this test is skipped / XIt until the aforementioned bug is fixed ?

I'm not sure if this fix would not simply mask the symptom, and hide a real bug.

There may be a bug somewhere in the synchronization, I'm not sure where. It's great that you've opened a bug. However, we calculate the time ourselves and the --sync option is really optional from my pov. Therefore, we can simply set the time ourselves.
Normally,  when you provide --sync parameter, the provided time is being ignored and the time is read from the domain's RTC instead. I think, not relying on this synchronization is the right solution anyway.
Also, see that other projects don't rely on this as well [1]

Would you accept if this test is skipped / XIt until the aforementioned bug is fixed, @vladikr ?
I don't see how skipping the test resolves anything for the users.

https://github.com/openstack/nova/blob/master/nova/virt/libvirt/guest.py#L148

I'm not sure if this fix would not simply mask the symptom, and hide a real bug.

There may be a bug somewhere in the synchronization, I'm not sure where. It's great that you've opened a bug. However, we calculate the time ourselves and the --sync option is really optional from my pov. Therefore, we can simply set the time ourselves.
Normally, when you provide --sync parameter, the provided time is being ignored and the time is read from the domain's RTC instead. I think, not relying on this synchronization is the right solution anyway.
Also, see that other projects don't rely on this as well [1]

This changes things :)
I'll bring that commit from the other PR then. Thanks for the effort; should have thought of looking for what we're doing in other projects.

Would you accept if this test is skipped / XIt until the aforementioned bug is fixed, @vladikr ?

I don't see how skipping the test resolves anything for the users.
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/guest.py#L148

/lgtm
/approve

/test pull-kubevirt-e2e-k8s-1.16
/test pull-kubevirt-e2e-k8s-1.15-ceph

/retest

/hold cancel

/lgtm


tests: making memfiles default for tests

Protyped files-as-in-memory-strings and got most tests happy.
We could do something more sophisticated and only have files prefixed with memfile create memfiles, but I thought this would catch far more unit tests than doing it that way, so if the goal is to speed up CI this may work better but it's surely less elegant to have a global boolean for which file type to use.    We can always move that over later as well.
The one functional exception is tests which use the filewatcher, as those are not created via the filesystem() so aren't memfile-aware.  I think that'd take a lot of reworking so I simply memfile-disabled tests which need that, most of the xds file reload tests and added a release assert to make it easy for folks creating tests to know what to do.
If we think it's worth going this route I'll go clean the rest up to make CI happy.
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
Most of #11121

Out of curiosity, do you have any data on test execution time(s) with in-memory vs. "regular" fs implementation?

running on my local machine I was actually disappointed at how little of a difference it made.  I do hope tweaking functions like waiting for access logs will improve some without the sleep() that it's doing now and it may do better on CI where it's not running on a dedicated machine (waiting on that to finish).  I'd been thinking of dropping it given the low gains I saw locally, but it looks like it may be useful as a functional improvement for Mobile testing, which is why I tagged @junr03 for go/no-go.  I think @asraa had said it might help with fuzzing speed at some point but now I'm looking for that comment I can't find it so may have made it up =P

running on my local machine I was actually disappointed at how little of a difference it made

I'd expect that for repeated reads, given sufficient available memory, fs cache (at least in linux, but I'd wager Windows would exhibit similar performance) would negate most of the benefits of trying to keep files in memory. Is making tests more hermetic also a goal (if eventual)? This might help isolate and discard changed between tests then (and probably would speed up affected tests too).

I just read the descriptions I wrote up in https://github.com/envoyproxy/envoy-mobile/issues/124 to page back into memory the initial thoughts I had (almost two years ago -- oh how time flies!).
The thought I had back then was that perhaps we would want to run all of Envoy's tests against mobile toolchains to suss out any oddities that might arise (around types mismatches across toolchains, behavior differences not present in core prod code, etc.). Since then, we have taken a more targeted testing approach, and have not ran into cases that require interaction with the filesystem. So afaict, Envoy Mobile is not in direct need of an in-memory file system.
So as far as go/no-go for need, I don't think I see a immediate need for Envoy Mobile. But I am more than happy to review and move forward if we want to go this direction for hermetic tests, notifier injection, and performance(?) reasons.
(Now, to the other point in the linked issue, we would still be interested in an implementation of the filesystem based on std::filesystem that could actually reach into mobile APIs. This would be useful for certain client scenarios around disk caching. But that is obviously not your goal in this PR, just thought I would mention.)

@alyssawilk I wouldn't expect this to be much faster yet until we have files in testdata/ into the string constants in CC files. WDYT?

CC @asraa who was interested in this from a fuzzing perspective.

I think @asraa had said it might help with fuzzing speed at some point but now I'm looking for that comment I can't find it so may have made it up =P

Yes! There are H/1 H/2 e2e fuzzer flakes caused by not finding filepaths for Envoy's test bootstrap (see illegal path messages in failures like this https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31617)

I agree much of the wins might come from putting testdata in memory, butI'd expect at least some from the config of the integration tests being written to memfile not disk, and I'm not seeing it.
For the integration test perspective, I'd be inclined to drop this because without speed wins, it's not worth the extra debug complexity of figuring out where files went.
If it's a win for fuzzing we could also default it off and run for fuzzing?  @asraa worth doing that, or should I just close it off?

If it's a win for fuzzing we could also default it off and run for fuzzing? @asraa worth doing that, or should I just close it off?

That would work well. Note that for a fuzz-only fix we could just do some hacking to start envoy with a config string instead of the config path in fuzzing integration tests, but since this works already here then sure!

For integration tests I suspect they are so slow for other reasons that they are not file-i/o-bound, and thus you did not see much of a win from config-writing.
For hot-restart that uses statically built Envoy, not a test link, so I don't think it matters whether there is real-file-system fallback behavior as your new filesystem class would not be in the binary.
I was thinking (as suggested in #11121) this would improve unit tests (eventually) but you won't be able to measure that till you a bunch more work. Having a filesystem-watcher callback might be worth it though for some integration tests that depend on it. But again you'd need to do a lot of work to evaluate that.

Asra, if I added these but off by default do you think we'd get around to turning them around in fuzzers, or no?  As said I'm inclined to leave them off for the rest of the test system until there's gains but I'm happy to check in if it'd be used in the not too distant future.

Asra, if I added these but off by default do you think we'd get around to turning them around in fuzzers, or no? As said I'm inclined to leave them off for the rest of the test system until there's gains but I'm happy to check in if it'd be used in the not too distant future.

yes! looks like a one-line change I'm happy to make as a follow-up

ok, finally got the windows build to be happy.  PTAL, let's get this to a place we're happy, and I'll switch it off and tag for final LGTM.

ping!

I left a couple of comments/questions; do you want to ack/nack or do something with those?

also a merge is needed.


Add default_user or default_change_reason for bulk_create or bulk_update

Just getting #636 across the finish line before doing a new release.

Codecov Report

Merging #653 into master will decrease coverage by 0.76%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master     #653      +/-   ##
==========================================
- Coverage   97.08%   96.31%   -0.77%
==========================================
  Files          17       17
  Lines         925      922       -3
  Branches      138      138
==========================================
- Hits          898      888      -10
- Misses         15       20       +5
- Partials       12       14       +2

Impacted Files
Coverage Δ

simple_history/utils.py
88.67% <80.00%> (ø)

simple_history/manager.py
97.29% <100.00%> (ø)

simple_history/admin.py
95.90% <0.00%> (-2.49%)
:arrow_down:

simple_history/models.py
97.19% <0.00%> (-1.25%)
:arrow_down:

..._history/templatetags/simple_history_admin_list.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Getting a 500 error when rejecting a request

I'm getting a 500 error when rejecting a request. The request is rejected, the status is updated in DynamoDB and the reject email is sent, but the below FlashMessage is displayed.

Here's the API log.
{ 'requestId':'bb5387b6-8e99-42a7-b642-36de59bc0725', 'ip': ', 'caller':'-', 'user':'-','requestTime':'08/Sep/2022:16:40:06 +0000', 'xrayTraceId':'Root=1-631a1ae6-583ae0e6723c7be14df47737', 'wafResponseCode':'-', 'httpMethod':'GET','resourcePath':'/get_pending_requests', 'status':'500','protocol':'HTTP/1.1', 'responseLength':'16' }
Here is the log from the custom_authorizer Lambda
ERROR Invoke Error {"errorType":"TypeError","errorMessage":"Cannot read property 'split' of undefined","stack":["TypeError: Cannot read property 'split' of undefined"," at Parser.parse (/var/task/node_modules/njwt/index.js:290:28)"," at Verifier.verify (/var/task/node_modules/njwt/index.js:349:24)"," at /var/task/node_modules/@okta/jwt-verifier/lib.js:206:21"," at new Promise ()"," at OktaJwtVerifier.verifyAsPromise (/var/task/node_modules/@okta/jwt-verifier/lib.js:204:12)"," at OktaJwtVerifier.verifyAccessToken (/var/task/node_modules/@okta/jwt-verifier/lib.js:238:28)"," at verifyAccessToken (/var/task/index.js:88:31)"," at Runtime.exports.handler (/var/task/index.js:134:9)"," at Runtime.handleOnceNonStreaming (/var/runtime/Runtime.js:73:25)"]}

I was able to fix this issue by updating the PendingTable.tsx file. Line 171: I changed userInfo.user to userInfo.token.


Correct naming for TPR creation

fixes issue #428
func TPRName() comes from #441
cc/ @arschles

CLA signed

I signed it!

CLA is now fixed

LGTM

Added LGTM1 for @arschles

@simonleung8 CI is failing on a vet error. Can you fix and ping me when done? I'll merge at that point

I've been trying to see those travis logs all morning w/o luck - that link you posted only worked for me once, then fails over and over.  Known travis issue....

@duglin don't know why but I could see it. Anyway, the issue is that the boilerplate header is missing from the new pkg/storage/tpr/resources_test.go file. @simonleung8 if you add that, hopefully we can get CI passing even though viewing the logs looks to be problematic.

@simonleung8 you may want to rebase on master too since if you don't your make verify might see other issues that are now fixed.

@duglin @arschles I wasn't able to see them until like 2 am this morning, but I can see them now.

LGTM, thanks for the fix.  Will merge on green ci

merging now


Run tests in CI on Windows and macOS

Right now the test suite is only run on Ubuntu. It looks like things don't quite work on Windows; running CI on each PR at least on Windows and macOS would be good.
All other platforms would be nice too, but if that requires emulation that's a bit less urgent.

Fixed in #24.


Providing Nix / TeXLive dependencies with a custom LaTeX package

Problem

I've made my custom LaTeX package that I pretty much use in all my projects, following the example in the nixpkgs manual. This is all done in a flake so I can import it directly in my other flake-based projetcs:
inputs = {
    # ...
    mypkg = {
      # ...
    };
  };
# ...
(texlive.combine {
  inherit (texlive) scheme-small latexmk ieeetran biblatex-ieee;
  inherit (mypkg) mypkg_tex;
})

However, mypkg relies on a lot of both TeXLive and Nixpkgs dependencies, and I've found no way to install these dependencies from a document's flake. I've tried the following so far:

Adding packages (from both TeXLive and Nixpkgs) to nativeBuildInputs in mypkg's derivation;
Writing a combined list using texlive.combine and having it in my flake's output;
Writing a collection by putting TeXLive packages as { pkgs = [ list of packages ]}, not sure whether it works like that...;
Passing a combined TeXLive package in another texlive.combine call.

From what I can tell, you cannot have multiple combined packages in your buildInputs, neither can you compose calls to combine. Is there a documented way somewhere?
Thank you for your help, I hope this can serve improving the docs somewhere.
Checklist

[x] checked latest Nixpkgs manual (source) and latest NixOS manual (source)
[x] checked open documentation issues for possible duplicates
[x] checked open documentation pull requests for possible solutions

Proposal

Ideally, the method for providing said dependencies should be detailed in the manual, in the same Custom packages section.

I hit the same stumbling block, a couple hours later I have a solution which seems to be working. So texlive.combine is expecting a set with the attribute pkgs: [derivation] the problem is this pkgs attribute has to refer to the derivation itself for this to all work. It looks like nix uses a recursive thing in mkDerivation to get that to happen. So the final diddy I ended up on was this:
{pkgs}:
with pkgs; let
  pkg = stdenv.mkDerivation (finalAttrs: {
    name = "uiowa-thesis";

    # texlive.combine expects these I think?
    pname = finalAttrs.name;
    tlType = "run";

    src = fetchFromGitHub {
      owner = "uiowa-mgb";
      repo = "uiowa-thesis";
      rev = "ab2bb48";
      sha256 = "5L0+0ykenZGYLZq9/iG2A3Ym8VvkD28ElghgYETOTEc=";
    };

    phases = ["installPhase"];

    passthru.pkgs = with texlive;
      lib.lists.foldr (a: b: a.pkgs ++ b) [pkg] [
        memoir
        biber
        biblatex
      ];

    installPhase = ''
      mkdir -p $out/tex/latex/
      cp -t $out/tex/latex/ $src/uiowa-thesis.cls
    '';
  });
in
  pkg

you then can call this like so:
{
  description = "A very basic flake";

  outputs = {
    self,
    nixpkgs,
    rooke,
  }: let
    system = "x86_64-linux";
    pkgs = nixpkgs.legacyPackages.${system};
    tex =
      pkgs.texlive.combine {
        inherit (pkgs.texlive) scheme-medium;
        uiowa-thesis = rooke.packages.${system}.uiowa-thesis;
      } ;
  in {
    formatter.${system} = pkgs.alejandra;

    devShells.${system}.default = pkgs.mkShell {
      buildInputs = [
        tex
      ];
    };
  };
}

I have no idea what I'm doing so there may be a cleaner or more idiomatic way of doing this?

Thank you very much @erooke ! I managed to reproduce your approach, even though I'm not sure to understand it fully. Would you mind to elaborate a bit on the following?
lib.lists.foldr (a: b: a.pkgs ++ b) [pkg] [
        memoir
        biber
        biblatex
      ];

While it solves my problem, I'd like to let this issue open while we do not have a proper documentation on the subject.

You're welcome :smile:
That's merging the list of all the derivations the dependencies are expecting. So for example memoir.pkgs is a list of derivations which memoir needs to function. This snippet creates a list with your derviation in it then goes through all the dependencies, extracts their requirements, and then appends them.
So that bit there is the same as saying
[pkg] ++ memoir.pkgs ++ biber.pkgs ++ biblatex.pkgs

it just generalizes better.

Much clearer, thanks again!

Hi all, we changed mechanism for TeX Live dependencies in #218331 (the attribute passthru.tlDeps) and wrote new documentation. @phdcybersec could you please confirm if the new system works for you? If so, we should close the issue!

Where is the documentation about this change? I have issue loading my custom packages.

One thing I didn't like so much is that we now MUST add the version attributes.

Thanks for the report! I am writing a tiny PR as we speak. The version attribute is not essential and we can make Nixpkgs accept packages without them.
If you spot something else that's weird, please let me know. Apart from the pkgs = [ finalAttrs.finalPackage ]; thing, it's cumbersome and I want to get rid of it, but it's another big change, so probably something for the 23.11 release.

How can I be aware of such changes in Texlive in Nix ? To be honest, I was quite surprised this morning when a colleague told me "It's not working" !

How can I be aware of such changes in Texlive in Nix ? To be honest, I was quite surprised this morning when a colleague told me "It's not working" !

Good question, unstable is a moving target so I don't think there is an official channel announcing these changes. For stable releases, there are release notes, although I didn't propose one about TeX Live – maybe I should in this case.
At any rate, the tlDeps upgrade was meant to be backward compatible and invisible, so the breakage was a genuine new bug I introduced.

I think this is essentially solved: we have new documentation in place, as well as a less obscure mechanism for specifying TeX Live dependencies. If not, please comment and/or reopen the issue.


Module is undefined

I npm installed, followed every little detail in the readme for XCode. Everything checks.
As soon as I create an Icon it says the Module is undefined and to try restarting the packager.
Cant seem to get it to work. Any clue? Tomorrow at work I'll add more information about the error.
Im including it just like in the example 'react-native-vector-icons/FontAwesome'

Did you try restarting packager? ;-)
Can you get the example to run?

Yes I basically closed everything and restarted and build.
Unless there is something I'm missing. What do you recommend to "debug" this problem? I'm really thinking it's Xcode screwing me over.
I didnt have time at work to try the example out because I take night classes. it's currently 1 AM here in Portugal xD about to go to bed

It's most likely not Xcode related but a javascript problem. Note that Packager is separate from Xcode so it won't close even if you quit Xcode. Try again tomorrow and let me know more details about the problem and some code.

So basically just got back and I restarted the computer.
I try to use the icon in the very first screen so the error it throws is:
"Requiring unknown module "undefined". If you are sure the module is there, try restarting the packager."
it only throws this when I try to use it in NavigatorIOS like:
leftButtonIcon: require(myIcon.getImageSource),
myIcon being: var myIcon = ();
If I dont put the leftButtonIcon on the navigator it doesnt blow up

Read the documentation or see the TabBarExample.

i had this problem
for other that may have problem with react-native-vector-icons and react-native-maps i suggest check my config in this thread
#2051


Fix: use runUntilPendingCommandsAreFullyHandled in CommandersActTrackerIntegrationTest

Pull request
Description
This commit replaces playUntilStartOfMediaItem with runUntilPendingCommandsAreFullyHandled in the CommandersActTrackerIntegrationTest file.
Changes made

Switch from playUntilStartOfMediaItem to runUntilPendingCommandsAreFullyHandled in CommandersActTrackerIntegrationTest.
Try to enable two @Ignored tests in ComScoreTrackerIntegrationTest.

Checklist

[x] Your branch has been rebased onto the main branch.
[ ] APIs have been properly documented (if relevant).
[ ] The documentation has been updated (if relevant).
[ ] New unit tests have been written (if relevant).
[ ] The demo has been updated (if relevant).
[x] All pull request status checks pass.

Doesn't no why in the past tests passes and now no more. Hint: stream provider changes some days ago.


How to use multiple ann_file in coco_instance?

train_dataloader = dict(
    batch_size=2,
    num_workers=2,
    persistent_workers=True,
    sampler=dict(type='DefaultSampler', shuffle=True),
    batch_sampler=dict(type='AspectRatioBatchSampler'),
    dataset=dict(
        type=dataset_type,
        data_root=data_root,
        ann_file=[
            data_root + "/mmdet/train/train_20230327.json",
            data_root + "/mmdet/train/train_20230213.json",
            data_root + "/mmdet/train/train.json",
        ]
        data_prefix=dict(img=data_root + "/mmdet/train/images/"),
        filter_cfg=dict(filter_empty_gt=True, min_size=32),
        pipeline=train_pipeline,
        backend_args=backend_args))

At the new version of mm-series, list of coco json files are not supported.
What's the appropriate config?

@ccomkhj did you solve this ?

train_dataloader = dict(
    batch_size=2,
    num_workers=2,
    persistent_workers=True,
    sampler=dict(type='DefaultSampler', shuffle=True),
    batch_sampler=dict(type='AspectRatioBatchSampler'),
    dataset=dict(
        type=dataset_type,
        data_root=data_root,
        ann_file=[
            data_root + "/mmdet/train/train_20230327.json",
            data_root + "/mmdet/train/train_20230213.json",
            data_root + "/mmdet/train/train.json",
        ]
        data_prefix=dict(img=data_root + "/mmdet/train/images/"),
        filter_cfg=dict(filter_empty_gt=True, min_size=32),
        pipeline=train_pipeline,
        backend_args=backend_args))

At the new version of mm-series, list of coco json files are not supported. What's the appropriate config?

Hi, may I ask that, dose version mmdet==2.26.0 support multipul coco anno files?

Greetings! Is there any update on this issue?

I created another solution to merge coco sustainably.
https://github.com/ccomkhj/cvops


Complex state access from styled component

I think styled-components have one big problem. It's too hard to make flexible component styles based on main component state/props
Currently, AFAIK passing props to styled component is only able via DOM element props. Let's look on one example of StyledDiv that was created from styled.div element.
<StyledDiv stateProp={ this.state.someProperty } />
I tried to pass stateProp into styled css generator. So what if i don't want to pass any props into this element but i need access master component state? May be it'll be better if we could access this component props/state via something like this styled.div`left<EMAIL_ADDRESS>?
Problems

Passing local state into components down may cause hard-detectable and unexpected bugs.
Passing spread (Containing style sensitive and others props) may break component look and feel. (E.g. if i pass {...this.state} as prop to styled component and state contains 'title' prop, this title will show in the child component as popup on hover). Selective props passing can cause problems from 1 paragraph

Possible solutions
I think that it need to add some sugar to have:

Access to state via ${@state}.
Access to holder component props via ${@props}
Access to this (styled) components props via<EMAIL_ADDRESS>
By this way we will be able to generate styles based on component state without passing props down
Currently i'm using that way <StyledComponent props={ ...this.props, ...this.state } /> but it's too complex to keep track on that prop and easy to be mistaken.
UPD
I'm developing card game and have component named PlayerHandDeck that contains Card elements as state (Will be replaced with redux store). Cards should be placed on above each other relative to screen width and cards count. So i need pass count={this.state.cards.length} to calculate offset and it'll passed into each Card component. On card click i'm lifting props up from card to PlayerHandDeck and get property count: 20. This is only one concrete example but i have a lot of such cases
Sorry for bad english

Currently i'm using that way <StyledComponent props={ ...this.props, ...this.state } /> but it's too complex to keep track on that prop and easy to be mistaken.

That's exactly why we recommend being explicit, so you always know which props are being passed in:
<StyledComponent count={this.state.cards.length} />

I think that it need to add some sugar

We won't add any syntactic sugar to the CSS you write in styled-components, at least definitely not in the core library.
If you really want to have this feature you could write a Babel plugin that does this transformation:
// Input:
const Bla = styled.div`
  color: $state.color;
`

// Output:
const Bla = styled.div`
  color: ${p => p.state.color};
`

I still wouldn't recommend it and would stick with the explicit way of doing things, even if it might take a couple more keystrokes.


chore: Update Actions labeler and labeler config to v5.0

Closes: #7008
What is the purpose of the change
This pull request updates the Actions labeler version to v5.0 and updates the labeler.yml file to be compatible with the v5.0 config file structure.
The new config file matches the existing functionality, and in the future it can be updated to take advantage of the new features from the v5.0 actions/labeler.
Testing and Verifying
This change added tests and can be verified as follows:

Since this workflow runs on pull_request_target it needs to be tested with a pull request to a branch with the updated workflow.
Thankfully, it was possible to manually test this with within my fork, and I ran through a few cases here: https://github.com/umbr4g3/osmosis/pull/1/files

I modified specific files within my PR to trigger the action, and it added the expected labels.

Additionally, reviewers can look through https://github.com/actions/labeler?tab=readme-ov-file#basic-examples to confirm that the changes align with the expected structure and match the behavior of the old file.

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[x] N/A

Thank you for the change @umbr4g3


1.21 Version 2.1.4 Causes Some Containers to be Invisible

In the latest version of the mod, some containers, such as trapped chests, chests, and shulker boxes are totally invisible in inconsistant situations. Removing the mod fixes these issues. For example, There is a storage system I have and every now and then either the input trapped chest or the storage itself turns invisible. I have attached an image of invisible chests and a video of chests, and my latests.log

Video: https://github.com/ItsThosea/BadOptimizations/assets/126922551/f8bbb915-7451-4ab1-b39f-ddc48acc5481
Log: https://mclo.gs/sLP7brM

Does disabling block entity render caching fix it?

Does disabling block entity render caching fix it?

Sorry, how do I change the settings? there is no settings option in Mod Menu for it

You open the badoptimizations.txt file in your config folder and change block entity renderer caching to false, then reboot your game.

that fixes it, yes.

So, issue fixed?

yes.

Do you know what mod caused this? Do you have any block entity tinkering mods? Going to mark it as incompatible.


GPC-151: Set Postgres to verify-full

This builds on #55, but I want to check it works as Corretto first

This may not work, so I want to watch when it gets merged :)

This went badly


Problems loading custom data in Branch.io

I've been using Branch.io few times before, but now i hit this error when running my app (This still did work 3 months ago). This is my stack trace:
System.InvalidCastException: Unable to cast object of type 'Foundation.NSString' to type 'Foundation.NSArray'
at ObjCRuntime.Runtime.GetNSObject[T] (System.IntPtr ptr) [0x000f1] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/ObjCRuntime/Runtime.cs:1166
at IOSNativeBranch.BranchLinkProperties.get_Tags () [0x00018] in :0
at BranchXamarinSDK.iOS.BranchIOSUtils.ToDictionary (IOSNativeBranch.BranchLinkProperties linkProperties) [0x0006b] in :0
at BranchXamarinSDK.iOS.BranchBUOSessionListener.InitCallback (IOSNativeBranch.BranchUniversalObject buo, IOSNativeBranch.BranchLinkProperties blp, Foundation.NSError error) [0x0001d] in :0
at ObjCRuntime.Trampolines+SDcallbackWithBranchUniversalObject.Invoke (System.IntPtr block, System.IntPtr arg0, System.IntPtr arg1, System.IntPtr arg2) [0x00029] in :0
at (wrapper native-to-managed) ObjCRuntime.Trampolines+SDcallbackWithBranchUniversalObject.Invoke(intptr,intptr,intptr,intptr)
--- End of stack trace from previous location where exception was thrown ---
And this is the data that i'm receiving:
{
data = "{"$marketing_title":"JDE-Procurement-139","~creation_source":1,"+click_timestamp":1527664859,"$ios_passive_deepview":"branch_passive_default","~stage":"","~feature":"marketing","+match_guaranteed":false,"~tags":"","$user_identity":"AAAA","~marketing":true,"+clicked_branch_link":true,"$one_time_use":false,"~id":"529720247461479146","~campaign":"jde-login-december","+is_first_session":false,"~referring_link":"","~channel":"E-mail"}";
"device_fingerprint_id" =<PHONE_NUMBER>59809569;
"identity_id" =<PHONE_NUMBER>64754921;
link = "https://jde.app.link?%24identity_id=529697551264754921";
"session_id" =<PHONE_NUMBER>39747095;
}

please update xamarin sdk

This fixed the issue, thank you for your help.


Backend migrations fail on Postgres for ~v0.1.1-alpha.15

After upgrading a standalone app around 0.1.1-alpha.15, I started getting migration failures for a new migration. I tried dropping and re-creating the databases and same problem. Have not tried sqlite3 and assume it may work fine.
Expected Behavior
The migrations run correctly.
Current Behavior
The following error occurs:
migration file "20200721115244_location_update_log_latest_deduplicate.js" failed
migration failed with error:
  CREATE VIEW location_update_log_latest AS
  SELECT t1.* FROM location_update_log t1
  JOIN
  (
     SELECT location_id, MAX(created_at) AS MAXDATE
     FROM location_update_log
     GROUP BY location_id
  ) t2
  ON t1.location_id = t2.location_id
  AND t1.created_at = t2.MAXDATE
  GROUP BY t1.location_id
  ORDER BY created_at DESC;
 - column "t1.id" must appear in the GROUP BY clause or be used in an aggregate function
Backend failed to start up, error:
  CREATE VIEW location_update_log_latest AS
  SELECT t1.* FROM location_update_log t1
  JOIN
  (
     SELECT location_id, MAX(created_at) AS MAXDATE
     FROM location_update_log
     GROUP BY location_id
  ) t2
  ON t1.location_id = t2.location_id
  AND t1.created_at = t2.MAXDATE
  GROUP BY t1.location_id
  ORDER BY created_at DESC;
 - column "t1.id" must appear in the GROUP BY clause or be used in an aggregate function

Possible Solution
?
Your Environment

NodeJS Version (v12): 12
Operating System and Version (e.g. Ubuntu 14.04): macOS
Postgres Version: 12.3 running in docker (debian)

@shmidt-i I guess this is related to the changes with the service catalog polling?

Yes, seems so. Will look into that👍

@shmidt-i - I have not tested this for correctness, but this will run without error on both pg & sqlite3 clients:
SELECT t1.*
FROM location_update_log t1
  JOIN
  (
    SELECT location_id, MAX(created_at) AS MAXDATE
    FROM location_update_log
    GROUP BY location_id
  ) t2
    ON t1.location_id = t2.location_id AND t1.created_at = t2.MAXDATE
GROUP BY t1.id, t1.location_id
ORDER BY created_at DESC;

Yes, that part I figured, however atm I'm looking into bringing the pg workflow into our end-to-end test to avoid this kind of situations ;)

Yeah, that's a great idea!


iceweasel not playing videos from cnn.com

Using Debian Jessie.
When using pepperflashplugin-nonfree (1.8.1) in chromium  (50.0.2661.94-1~deb8u1) I can view videos on cnn.com.
e.g. http://edition.cnn.com/2016/05/26/middleeast/libya-isis-europe-doorstep/index.html
These videos fail to play (black screen) using the same pepperflashplugin-nonfree in
iceweasel (38.8.0esr-1~deb8u1). (using browser-plugin-freshplayer-pepperflash 0.3.5-1~bpo8+1)
Flash version <IP_ADDRESS>
Already discussed with debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825331
Thanks for looking into this.

Ignore that post. Turns out the problem was related to my iceweasel apparmor profile, which was preventing access to .config/freshwrapper-data.
Now works.


Doc examples not working

For the following components the examples in the documentation are not working:

[ ] Busy indicator
[ ] Color palette popover
[ ] Menu
[ ] Popover
[ ] Responsive Popover
[ ] Dynamic Side Content
[ ] Flexible Column Layout
[ ] Product Switch  - last example
[ ] Side Navigation
[ ] View Settings Dialog
[ ] Dialog - the dialogs don't show
[ ] Toast - toasts don't show

Hi, yes all will be working after the PR https://github.com/SAP/ui5-webcomponents-ngx/pull/126 is merged


Adds reflection and conversions from common types

I also fixed the CI failures and some issues with the license
Fix #53

@traversaro @GiulioRomualdi friendly ping

Thanks a lot @traversaro. Merging


Custom CSS to work in pop outs.

I was trying to edit the background of the call screen to green for chroma key for streaming. I was able to find the class and edit it. And it does make the main video call screen green, but it does not apply it to the video call window if popped out.
If I use the console on the pop out window and apply the same edit to the same class in my custom css, it will work. So they both use the same class, it just isn't applied on pop outs. The class just for reference is:
.wrapper-2qzCYF {
background-color: green;
}

This would be a duplicate of https://github.com/BetterDiscord/BetterDiscord/issues/464

See above


Slide: Violin Plot breakdown and explanation

The violin plot is complex and needs to be broken down into parts and explained to the lay person.

done, the BSides slide deck has this