user logger instead of log

Fixes #394
log.info was not a recognized command.  Use logger.info to fix TaskExecutionException.
Output when another process runs gradle libertyStop now looks like this:
> Task :libertyDev
Source compilation was successful.
Tests compilation was successful.

[AUDIT   ] CWWKE0055I: Server shutdown requested on Friday, December 13, 2019 at 11:58 AM. The server defaultServer is shutting down.
[AUDIT   ] CWWKE1100I: Waiting for up to 30 seconds for the server to quiesce.
[AUDIT   ] CWWKT0017I: Web application removed (default_host): http://<IP_ADDRESS>:9080/metrics/
[AUDIT   ] CWWKT0017I: Web application removed (default_host): http://<IP_ADDRESS>:9080/
[AUDIT   ] CWWKT0017I: Web application removed (default_host): http://<IP_ADDRESS>:9080/ibm/api/
[AUDIT   ] CWWKZ0009I: The application demo-devmode has stopped successfully.
[AUDIT   ] CWWKE0036I: The server defaultServer stopped after 38.965 seconds.

> Task :libertyDev
The server has stopped. Exiting dev mode.
:libertyDev (Thread[Execution worker for ':',5,main]) completed. Took 50.472 secs.
BUILD SUCCESSFUL in 51s
1 actionable task: 1 executed

Travis build failure looks unrelated and seems to be a connection issue with Maven Central.  Merging this PR.


Consider moving dependency mgmt from glide to dep

The dep tool is emerging as the standard dependency mgmt mechanism for golang projects. The glide README even recommends migrating to dep.

I'll leave this as an open item -- I've used dep on and off over the last year, and it still isn't quite where it should be compared to glide on several fronts. When dep is a bit more mature, we should make that flip.

fixed! moved to go modules


check creation timestamp for nil and minor cleanup for local testing

Had someone run into a strange condition that I have been unable to reproduce locally (due to tricky timing of the condition). It's still a good practice to checks for nils where they are a possibility though... so proposing this as a change.
I have the user running a test build of pod-reaper to help determine is this was indeed the fix:
Please don't merge until I report back my findings!

Will test the newest code overnight.


model: scikit: scorer: Add sklearn model accuracy scorer

Signed-off-by: Sudhanshu<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (accuracy_staging@0b57c12). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             accuracy_staging    #1142   +/-   ##
===================================================
  Coverage                    ?   84.35%
===================================================
  Files                       ?      156
  Lines                       ?    10117
  Branches                    ?     1673
===================================================
  Hits                        ?     8534
  Misses                      ?     1236
  Partials                    ?      347

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 0b57c12...d78ed50. Read the comment docs.


Please add options for sorting and choosing which file type to view in the Explorer panel

VSCode Version: 1.8.1
OS Version: Windows 10

I'm working on an big project. I view my current folder by the Explorer panel in the left. My current folder have a lot of file of many type. And I only want to show files of a specific type. Please add some option for viewing and sorting file!

@phcloc can you not use the files.exclude setting to filter unwanted files out of view?

I think everything is covered.


Add LinearCombination transform

Closes #5
Note that I couldn't get a linear combination using Statistics.mean to work. A lot of operations were returning NaNs. Also, that mean function expects a whole matrix of weights and not just the weights for each column. For these reasons, I opted not to define the CustomTransform instead of doing this explicitly.
From the issue description, I am unclear what the role of dims kwarg is or how it should work.

From the issue description, I am unclear what the role of dims kwarg is or how it should work.

I think dims would apply when you want the linear combination to only operate on a subset of columns.
e.g.
df = DataFrame(
    :time = Day(1):Day(1):Day(5),
    :a = [1, 2, 3, 4, 5],
    :b = [1, 1, 2, 3, 5],
)

lc = LinearCombination([1, 5])

Transforms.apply(df, lc; cols=[:a, :b])

similarly for dims on arrays.
Does this make sense?

similarly for dims on arrays.

If it's selecting a subset of columns, then dims for arrays seems misleading - like it will apply the linear combination along a different axis. I think it should always be called cols for this usage.

similarly for dims on arrays.

If it's selecting a subset of columns, then dims for arrays seems misleading - like it will apply the linear combination along a different axis. I think it should always be called cols for this usage.

I agree using dims would make me thing it's choose only certain rows, not a subset of the array cols

I have implemented cols as Ben suggested and left the dims tests commented out while we decide what dims should mean. I may just not understand what dims means for an Array but having both does seem confusing.

If it's selecting a subset of columns, then dims for arrays seems misleading - like it will apply the linear combination along a different axis. I think it should always be called cols for this usage.

Looks good to me. I don't think there is a use for dims as long as this transform is only applied on columns.

Sorry, that's dead right, in my first response I completely confused dims / cols.
But I think there is still a place for dims because we might not always take the linear combination column-wise.
e.g. consider just taking a sum over some matrix - this resembles a LinearCombination(ones(3)) in this case.
julia> A = [1 2 3; 4 5 6; 7 8 9];

julia> sum(A, dims=2)
3×1 Array{Int64,2}:
  6
 15
 24

julia> sum(A, dims=1)
1×3 Array{Int64,2}:
 12  15  18

I think all that needs to change is to change eachrow to eachslice(...; dims=dims)?


Terminal opens in sub-directory instead of project directory

Android Studio Flamingo | 2022.2.1 Patch 1
Native Terminal Plugin v0.4.6.
OS: Linux Mint 21.1 Cinnamon
Terminal: gnome-terminal 3.44.0
I have been using the Native Terminal plugin for years. Click on the icon, opens a new terminal window in the project directory. Great.
Since the last update of Android Studio (from Electric Eel to Flamingo), when a new terminal window is open, it starts in one subdirectory of the project ( $projectdir/app/src/main/java/com/myexample/somepackage ), which means every time I have to type "cd .. cd .. cd .." several times to go all the way up.  I don't remember if the terminal plugin was also updated since then (meaning, it's not clear if it's the Android Studio update that caused this, or the Terminal Plugin itself).  I could not find any options or setting to modify, to make it behave like it used to.
Is there a way to fix this? Like, a cache to be deleted somewhere, or a setting to modify?

Hi Chris,
I would suggest trying to change the default project directory for the plugin:

Press the right button on your application root directory in the Project tab.
And then click on 'Set as default directory for external terminal'.
Then try to open the terminal window again, now it should open that directory.

@sburlyaev thank you! That did the trick.
I was looking into the wrong place when searching for the relevant settings... never occurred to me that you can configure plugin settings directly from a drop-down menu in the project navigation window.
Anyway, I will close the issue. Thanks a lot :)


audiounit: On unexpected number of returned frames go to error

In audio callback, when returned frames are less that the expected we go to Drain. However if return frames are less than zero or more than expected we should go to error.

Well, the question is: what motivated this change? A specific instance of this triggering, or that you just noticed that the error checking was incomplete?

Just noticed the incompleted check. I was wondering the same think during the development of full duplex for Android in which we decided to go to error so I did the same here.

#256 raised to track that.


Example_Notebook for the class PUPredict

Example nb looks good @VishnuHarshith! Once the merge conflict is resolved, I'll merge this in.


Page Component: Update Responsive Styles

This update changes the breakpoints for the max-width and the changes the padding applied at different breakpoints.
The width is constrained until 1050px (previously 1000px).
Beyond the default padding (y: 50px, x: 50px), we introduced:
Wide Screen: 1050 - 1350 (y: 50px, x: 100px)
Super Wide Screen: 1350 - 1450 (y: 65px, x: 50px)
Full Screen: 1450+ (y: 65px, x: 100px)
I'll update this with a link to the Story after Storybook rebuilds.
See: https://github.com/helpscout/hsds-product-ui/wiki/Responsive

Here's a link to the specific story for the new breakpoints: https://deploy-preview-492--hsds-react.netlify.com/?selectedKind=Page%2FExample&selectedStory=Responsive&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel

@knicklabs This might be another one of those "this is just a Storybook thing" things ... but wanted to ask:
The default block size should be 700px. Its currently 680 though I see in the styles max-width: 700px is set. 🤔

As a result, form label and content widths are off. Currently 480px, should be 500px.

@jaredmcdaniel I fixed up the Story for the responsive Page component. It should behave much more like it's implementation within hs-app now.
Pro tip! for Storybook, add iframe.html in the URL to see the dedicated story (without the other stuff):
https://deploy-preview-492--hsds-react.netlify.com/iframe.html?selectedKind=Page%2FExample&selectedStory=Responsive&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel

Ugh.. really need to fix these long Netlify build times

Looking much better now! 👏
Only thing I noticed is it looks like we're missing breakpoints for 06. Widest. Specifically with the width of the form column. At > 1650px, it should be 650px vs 500px ... making the block container 1200px.

@jaredmcdaniel Haii!! I added the adjustments for the widest breakpoint.

Pull Request Test Coverage Report for Build 1696

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

Totals

Change from base Build 1695:
0.0%

Covered Lines:
6479

Relevant Lines:
6479

💛  - Coveralls

Awesome!! Merging this up


Allow Get Command to pass parameters in the payload

🚀 Feature Request
Relevant Package

 This feature request is for core-command
Description
We support URL query parameter to pass into Device Service for Get Command.
Sometimes, it is not enough because the URL length is limited, and this would be REST only.
Describe the solution you'd like
Allow Get Command to pass the parameters in the payload to Device Services

As discussed in other channels, there is no limit on the URL length. But some web browsers set certain limits.
RFC 2616 Section 3.2.1:

The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).

It should be theoretically possible to encode the object and pass it as query strings. E.g. GET /device/name/{name}/{command}?json=<base64-encoded-object>.
However, passing body in GET is beneficial when the content is too large or sensitive such that having it appeared in logs or a remote logging infrastructural would cause performance or security issues.
With that said, we should be careful when adding that feature:

The OpenAPI spec disallowed requestBody for GET up until version 3.1.0 which is not yet supported by some tools (incl. the swagger editor). The current core command spec uses version 3.0.0.
The new GET operation should stay RESTful (for obvious reasons). Calling GET /device/name/{name} is expected to retrieve some information about a device named /device/name/{name} and not a command. Note that GET /device/name/{name} currently performs another action and we better not overload by passing body and content type because that is semantically different and backwards-incompatible.

Hope that helps.

What I am proposing here is to pass the whole request, including payload and path query parameters to the Device Service implementation.  We are right now blocked by the transitional REST paradigm.  People have started using GET method with payload for different scenarios.  If we execute the command via message bus, the payload will be passed to the Device Service implementation.  There is no harm for the existing services and device services.
The scenario I encounter is as followings:
To enable more Onvif functions, we need to pass some structural data to the Device.
https://www.onvif.org/ver10/device/wsdl/devicemgmt.wsdl


FIX(animation): consider easing options

Up to now a default easing method 'linear' was used even
if the easing option has been set.
This commit makes sure that the assigned easing option is considered
when animating.
fixes #67

@seriousManual Just mentioning you made this commit with<EMAIL_ADDRESS>and not with the mail address of your Github profile, therefore your commits (also in the other PR) cannot be referenced to your Github. (you see it by the missing profile pictures of the commit)
Maybe you want to change the mail address in the git config and make a git commit --amend and git push --force before I merge? ;)

Hi, thanks a lot for the heads up!
I was doing this change on my work laptop and forgot to change the author config!
It's amended and pushed!

Thanks! Merged. 🍪


Alternative to flex-gap-polyfill with TWBS 5

Hi there,
I created this gist https://gist.github.com/frugan-it/19f94872e4b6005775d91350e87002bf and would love to hear some feedback from you..
Thanks!

I just going to close this as an issue, but people can still find it if they want to look for alternatives. Thanks again!

Link is dead. Seems the user changed username. Link is https://gist.github.com/frugan-dev/19f94872e4b6005775d91350e87002bf


[Bug]:

What happened?
A bug happened
Bug:It won't to open the app after many try the website is crash and i can't open the website
To reproduce the behavior?
reproduce!
Fix you're bug
What browser are you seeing the problem on?
Chrome

which app?


Running grunt shows: Warning: Task "default" not found. Use --force to continue.

Expected behaviour
Success.
Actual behaviour
Running grunt shows: Warning: Task "default" not found. Use --force to continue.
Datepicker version used
1.7.0-RC2
After installing
$ [sudo] npm install --global grunt-cli
$ npm install
That error shows.

This is more an issue with npm I think. Something might have gone wrong during the installation. Did you get any errors? Can you try this process with yarn instead (this is the recommended way of installing)

@jhunexjun use grunt dist


[Feature Request] Option to only inc/dec when augend is under cursor

Problem:
Right now I have this in my config:
        augend.constant.new { elements = { 'on', 'off' }, word = false, cyclic = true, },

I have word = false, since I wanna allow for cases where 'on'/'off' is part of an identifier like 'turn_on` etc.
Now the problem with that is, that I get a ton of false positives when I wanna increment something else in the line. I use <c-a> and it jumps to an occurrence of "on" as part of another word since those 2 letters appear everywhere in the English language apparently.
So then I turned "on" to "off" unintentionally in some word and have to decrement again, to finally jump to the actual place I where wanted to increment something.
Solution:
An option in the augends, that allows to turn off the jumping/seeking for this particular augend, would be great. Eg:
        augend.constant.new { elements = { 'on', 'off' }, word = false, cyclic = true, jumpTo = false},

In that case, the increment would only work, if it matches something right under the cursor.

I will consider the turn off feature, but first let me ask about the false positive problem.
What you want to do is to toggle .*_on identifier and .*_off identifier?
If so, this can be done with the following configuration without the risk of false positives.
require("dial.config").augends:register_group {
    default = {
        -- matches identifiers which end with "_on" and "_off"
        augend.constant.new {
            elements = {"on", "off"},
            pattern_regexp = [[\V_\zs\(%s\)\>]],
        },
        -- matches "on" and "off" as single word
        augend.constant.new {
            elements = {"on", "off"},
            word = true,
        },
    },
}

Alright. Interesting.
Didn't read deep enough into the readme to come up with that solution apparently.
It wasn't just about this very specific snake_case but more generally about "on"/"off" appearing in an identifier. Also when there is text following and for eg. camelCase.
In that same notion an option for case insensitivity of the elements would be nice. I think I've seen a related issue already.
Of course I could adapt the regex to fit my needs. Still I believe the option to turn off the jumping, in general, and for specific augends, would make the plugin more adaptable to user needs.

In that case, the increment would only work, if it matches something right under the cursor.

In fact, you can achieve this functionality with a little advanced configuration. Please try this:
local augend_onoff = augend.constant.new {
    elements = { "on", "off" },
    word = false,
    cyclic = true,
    preserve_case = true,
}

require("dial.config").augends:register_group {
    default = {
        augend.user.new {
            find = function (line, cursor)
                local range = augend_onoff:find(line, cursor)
                if range ~= nil then
                    if range.from <= cursor and cursor <= range.to then
                        return range
                    end
                end
                return nil
            end,
            add = function (text, addend, cursor)
                return augend_onoff:add(text, addend, cursor)
            end
        }
    },
}

In that same notion an option for case insensitivity of the elements would be nice. I think I've seen a related issue already.

Yes, conversion with preserving case has been already supported. The optionpreserve_case does.

Thank you :)
Props to your API design.
I still think adding the flag to the augend config table would be nice, but obviously you gotta judge that for yourself.

This isn't really worth a new issue, I just wanted to mention that the option preserve_case has a very counter intuitive name.
What it effectively does if it's true, is to make the string's case insensitive, right? So ignore_case would be a much more fitting and commonly used name for such an option. Or maybe it's just me getting confused by this^^

Augend with preserve_case = true attempts to preserve the case during conversion.

All lowercase (e.g.: true <-> false)
All uppercase (g.g.: TRUE <-> FALSE)
Only the first letter is uppercase (e.g.: True <-> False)

The name ignore_case does not express this property.

For a better name, I think "try_preserve_case" would be appropriate.


read mode secondary not work

I use the Mongoid 5.0 beta, the configuration
production:
  clients:
    default:
      database: shou_be_production
      hosts:
        - mongodb-rs1:27017 # This is the primary
        - mongodb-rs0:27017 # This is secondary
        - mongodb-rs2:27017 # This is secondary
      options:
        write:
          w: 1
        read:
          mode: :secondary
        heartbeat_frequency: 5
        server_selection_timeout: 10
        max_pool_size: 128
        min_pool_size: 32
        wait_queue_timeout: 5
        connect_timeout: 5
        socket_timeout: 5
        replica_set: rs0

I can see many connections coming from the Rails app in the mongodb secondary log, but in the unicorn.stdout.log I only find logs to the primary node
MONGODB | mongodb-rs1:27017 | shou_be_production.find

Is this an typo in log or an bug? Or am I using it incorrectly?

And I do find many slow query logs in the mongodb primary log, but nothing in the secondary. Only connection accepted, end connection, etc in the secondary.


[HOLD for payment 2024-10-16] [$250] Expensify card - Expensify card link navigates to wallet instead of virtual card details

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.40-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5012494
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
and log in
Create a workspace
Navigate to the workspace settings > More Features
Enable Expensify card option
Navigate to the Expensify card and click on Issue card
Select Connect online with plaid and add the VBA
Issue the virtual Expensify card to the current user
Navigate to the workspace chat
Click on the Expensify card link

Expected Result:
User is navigated to the virtual Expensify card details
Actual Result:
User is navigated to the wallet
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/70545897-820d-4677-8a76-7bbf6b575ed4
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021839673843128973218
Upwork Job ID:<PHONE_NUMBER>128973218
Last Price Increase: 2024-09-27
Automatic offers:

jjcoffee | Reviewer | 104214637
truph01 | Contributor | 104214639

Issue OwnerCurrent Issue Owner: @slafortune

I will check the redirection logic written there and modify it as per requirements to redirect it to wallets.

Proposal
Please re-state the problem that we are trying to solve in this issue.
User is navigated to the wallet
What is the root cause of that problem?

We always navigate the user to wallet page via:
https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1750-L1751

What changes do you think we should make in order to solve the problem?

We should add additional params policyID, cardID to:

https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1745
and instead of ROUTES.SETTINGS_WALLET in:
https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1751
use:
ROUTES.WORKSPACE_EXPENSIFY_CARD_DETAILS.getRoute(policyID, cardID)

policyID and cardID are passed down in where getCardIssuedMessage is called.

What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
User is navigated to the wallet
What is the root cause of that problem?

We always navigate the user to wallet page via:
https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1750-L1751

What changes do you think we should make in order to solve the problem?

We should add additional params policyID, cardID to:

https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1745
and instead of ROUTES.SETTINGS_WALLET in:
https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/libs/ReportActionsUtils.ts#L1751
use:
ROUTES.WORKSPACE_EXPENSIFY_CARD_DETAILS.getRoute(policyID, cardID)

policyID and cardID are passed down in where getCardIssuedMessage is called:
https://github.com/Expensify/App/blob/70a8a16114d68d871a89a2fb0aef841fac1c948d/src/components/ReportActionItem/IssueCardMessage.tsx#L45

What alternative solutions did you explore? (Optional)

We can navigate to another page instead of ROUTES.WORKSPACE_EXPENSIFY_CARD_DETAILS.getRoute(policyID, cardID) based on future discussion.

@truph01's proposal LGTM!
:ribbon::eyes::ribbon: C+ reviewed

Solution looks good, but I see getCardIssuedMessage is called in other places than IssueCardMessage, can you include details of all of the places we need to update?
Also, I also don't quite get where will you get the cardID from exactly in App/src/components/ReportActionItem/IssueCardMessage.tsx

getCardIssuedMessage is called in other places than IssueCardMessage, can you include details of all of the places we need to update?

Logic displays the report's name:
https://github.com/Expensify/App/blob/c7ee85b2ea207159ef85932055aced28d5d2e29a/src/libs/ReportUtils.ts#L3838-L3840

Logic displays the last message text in LHN:

https://github.com/Expensify/App/blob/c7ee85b2ea207159ef85932055aced28d5d2e29a/src/libs/SidebarUtils.ts#L435-L436

Logic displays copy message:
https://github.com/Expensify/App/blob/c7ee85b2ea207159ef85932055aced28d5d2e29a/src/pages/home/report/ContextMenu/ContextMenuActions.tsx#L482-L483

The getCardIssuedMessage are used in the above places. If we update getCardIssuedMessage function, these places will auto work properly.

I also don't quite get where will you get the cardID from exactly in

We can get cardID can get from the report action data:

PR is ready

PR not yet merged

@jjcoffee can you please complete the checklist?

The PR that introduced the bug has been identified. Link to the PR: N/A - this was a missing feature in https://github.com/Expensify/App/pull/46281
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
Determine if we should create a regression test for this bug. Yes
If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

[Admin] On a workspace with Expensify cards enabled, navigate to Workspace Settings > Expensify card
[Admin] Click on Issue card and issue a virtual Expensify card to any non-admin workspace member
[Admin] Navigate to the workspace chat
[Admin] Verify that tapping the Expensify card link in the card issued message opens the virtual Expensify card details.
[Non-admin] Log in as the user to whom the card was assigned.
[Non-admin] Open the same workspace chat.
[Non-admin] Verify that tapping the Expensify card link in the card issued message opens the virtual Expensify card details.

Do we agree 👍 or 👎

@slafortune All done!

@jjcoffee Role - C+ - Paid $250 via Upwork
@truph01 Role - Contributor - Paid $250 via Upwork


LINK: fatal error LNK1181 - In Insulation

I'm trying to install PYAV in Windows 10
Python Version 3.6.0
follows the error:
LINK : fatal error LNK1181: não foi possível abrir o arquivo de entrada 'swresample.lib'
error: command 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\link.exe' failed with exit status 1181

python setup.py build --ffmpeg-dir=C:\ffmpeg
running build
running build_py
running build_ext
running config
writing build\temp.win-amd64-3.6\Release\include\pyav\config.h
running cythonize
building 'av.buffer' extension
error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": https://visualstudio.microsoft.com/downloads/

I'm not sure what the error is even supposed to be here.
Is it complaining that you need v14 of the compiler... from v14 of the compiler? 😛

@mikeboers I am having the same issue. Even after installing Visual C++ Build tools, it gives an error with exit code 1181. I even tried building PyAV from source with ffmpeg. It doesn't seem to work.
Please Help

You need Visual Studio 2015 (not 2017 or 2019!)
It worked for me after I put ffmpeg\lib and ffmpeg\bin into the PATH

That's kind of annoying, any idea why we are stuck with VS 2015?

I suspect it has something to do with pythons setuptools, but I'm not sure.

I managed to make pip install av work on Windows 10 with Visual Studio 2019 by setting compiler and linker variables. I described the steps in this gist. It works for me and multiple of my coworkers. I can create a pull request for the docs folder to include the steps, if this is desired.

It works for me with the method by copy the lib files into the python "libs" directory and the include directories into the "includes" directory, which can also be seen in this site, https://github.com/mikeboers/PyAV/issues/467

Since release 8.0.0, binary wheels are provided on PyPI so installing PyAV on Windows no longer requires any compilation.


neuroglancer viewer slice view breaks on Firefox 67 (current) and 68 (beta)

Dear all, newest Firefox (windows, macos and ubuntu 16 + 18) update seem to have broken the sliceview in neuroglancer. In console, errors were logged as follows:
Error: WebGL warning: drawArrays: Program has no frag output at location 1, but destination draw buffer has an attached image.

at this line: https://github.com/google/neuroglancer/blob/742c58deb08fa31ad2350cb51f4b17b285a76648/src/neuroglancer/sliceview/frontend.ts#L438
this line seems to be the line that throws the error, edit: introduced by this commit.
I apologise that my webgl foo is not strong enough to provide a fix, and thus can only research on some background.

Thanks for reporting this.  It is now fixed.


Update release process to not require admin access

What does this pull request do?
Currently our release process requires multiple no-check pushed to protected branches. As we (eventually) would like to stop using admin overrides on the repo, our release process needs an update.
I think we want to have the release tags on the major branches (like 6.x) rather than on main. That's how I've written it here. If we want the release tags to show up in git log for both 6.x and main we would need to do a third merge, from 6.x back to main as part of the release process.
This update will require both @beniwohli and I to be around at the same time for releases, as we'll need to approve the PRs. We'll also have to wait for tests to run two extra times. I don't think that's a terrible requirement, but it will hurt our ability to do fast regression releases.
Thoughts welcome.
cc @felixbarny @estolfo @AlexanderWert

On further thought, maybe we can put the release tag on main, because then it will show up on 6.x after we merge from main to 6.x? That's probably an improvement, I'll make that change.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-04-04T17:46:15.984+0000

Duration: 3 min 15 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Another route could be automating the steps that require admin permissions and allow the CI user to bypass the PR requirement. The downside is that if someone gets ahold of the CI user, they can do anything.
@Mpdreamz What's your stance on exempting CI users from certain branch protection rules?

This update will require both @beniwohli and I to be around at the same time for releases, as we'll need to approve the PRs.

Leads can also help out with the reviews if someone is out.

Closing this for now. We can re-address this when we next do more SLSA.


Feature/job specs pt. 1

first of a handful of job specs
details in commits

Coverage increased (+1.0%) to 55.799% when pulling ee69aa39824b6fd8fff1d60f17de5630b6a3b300 on feature/job-specs into 329c01cb1126e2e2d0fe20b5f5a68e9707b48480 on development.


fix(schema): add tight property for lists

Signed-off-by: Diana Lease<EMAIL_ADDRESS>Issue https://github.com/accordproject/markdown-editor/issues/156
Changes
fix(schema): add tight property for lists

Looks good! FYI: The issue I opened in markdown-transform is actually about nested list in Slate (apparently they are gobbled). Do we support nested lists on the UI side? https://github.com/accordproject/markdown-transform/issues/109

Looks good! FYI: The issue I opened in markdown-transform is actually about nested list in Slate (apparently they are gobbled). Do we support nested lists on the UI side? accordproject/markdown-transform#109

not currently, no.


Lock grape-jsonapi gem version to fix malformed Swagger docs

The grape-jsonapi gem introduced a data param "feature" in v1.0.1 that breaks the Swagger doc generation by forcefully wrapping the Swagger JSON in an additional (invalid) data param.
This PR locks the gem version to 1.0.0 to bypass this bug.

I solved it by extracting data key from the hash in grape_jsonapi/formatter.rb:
module Grape
  module Formatter
    module Jsonapi
      class << self
        def call(object, env)
          response = serializable?(object) ? serialize(object, env) : { data: object }
          ::Grape::Json.dump(
            response.merge(env.slice('meta', 'links'))**[:data]**
          )
        end

        ...

@newstler That's one way to do it! But wouldn't this affect the format of all API responses?
I'm going to be forking and updating the grape-swagger gem in the near future, at which point I plan on fixing this particular issue directly where the Swagger docs are generated, and then we can remove the grape-jsonapi version lock.


optimize-rdock.py

Hi, I was trying to read your code especially in optimize-rdock.py
I got confused a little bit in Lines 109-110, if I am not correct, I think there is a typo:
109. initial_genes = [CFGtoGene(cfg_util.encode(smiles), max_len=gene_length)
110.                           for s in initial_smiles]

in Line 109, do you mean cfg_util.encode(smiles) or cfg_util.encode(s)?

Thank you so much for your kind report.
It is a typo. I will fix it soon.


[BUG] Steps are glitchy on strict.2b2tpvp.org

Step works but lags back on strict.2b2tpvp.org, this did not happen on earthhack 1.8.5
Steps to reproduce the behavior:

log on to strict.2b2tpvp.org
turn on step
config:
mode: slow
height: 1.07
use timer: false
timer: 0.95
entity step: false
auto off: false
lag time: 37
mine-gapple: true
compatibility: true
try to step up a few blocks, the first time usually works but rest of the times it lags back one time everytime you step. I've checked and im pretty sure it's not a config issue

Without the bug, the step should work without any lagback on strict server like step on earthhack 1.8.5

[x] I know how to properly use check boxes.
[x] I have included logs, screenshots, exceptions and / or steps to reproduce the issue.
[x] I followed the issue template.

Use build https://github.com/3arthh4ckDevelopment/3arthh4ck-Client/actions/runs/6732545754 and enable Step - Offsets - Old. Open a new issue if this still persists, atleast from my testing this worked fine on 2b2tpvp.


Wrongly visible on the left / race condition in scrollbarYRight detection

Hi, after a long journey with simplebar and OverlayScrollbars I've finally settled on perfect-scrollbar for a larger project, as that was the only one not messing with the container's styling. It is kind of perfect, really.
One bug I have is that it mistakenly thinks that the scrollbar should be on the left.
What is happening is that scrollbarYRight detection needs to wait a bit, otherwise it gets detected as missing / isNaN / isScrollbarYUsingRight = false.
Problematic part:
https://github.com/utatti/perfect-scrollbar/blob/54103fab66ae255ef73aeea57e095385e03c6c01/src/index.js#L119
If I enter:
console.log(railYStyle.right)   -> ''

window.setTimeout(() => {
  console.log(railYStyle.right)  -> '0px'
}, 0)

The first line will output '' while the timeout one will return 0px. Also, 0px is something that should be taken care of, as it's not an integer.
I've seen other issues about left side visibility, I believe they were running into the exact same issue.
https://github.com/utatti/perfect-scrollbar/issues/784
I cannot make a fiddle out of it, as in simple example the race condition doesn't happen.
Ugly workaround:
.ps__rail-y {
  left: auto !important;
}

The same problem with Vue directive. Looks like Vue.nextTick() helps.
import Vue from 'vue';
import PS from 'perfect-scrollbar';

const cache = new WeakMap();

export default {
  bind(el, binding) {
    if (typeof window === 'undefined') return;

    const defaults = {
      wheelPropagation: true,
      suppressScrollX: true,
    };

    Vue.nextTick(() => {
      const ps = new PS(el, Object.assign(defaults, binding.value));
      cache.set(el, ps);
    });
  },
  update(el) {
    const ps = cache.get(el);
    if (ps) {
      ps.update();
    }
  },
  componentUpdated(el) {
    const ps = cache.get(el);
    if (ps) {
      ps.update();
    }
  },
  unbind(el) {
    const ps = cache.get(el);
    cache.delete(el);
    if (ps) {
      ps.destroy();
    }
  },
};

+1
Also having problems with this.

+1 haha. though, ugly workaround, but it works!

+1, another workaround is by flipping the text direction of the container, and then flip it back in the container items:
container.ps {
  direction: rtl;
}
container > .item {
  direction: ltr;
}

the railling is under div tag, so avoid doing:
container > div {  /* dont do this */
  direction: ltr;
}

+1 also having this problem where the ugly workaround works perfect!

On top of it there is a bug that scrollable area become expanded and you can scroll much more than really occupied space.

Try this: https://github.com/mdbootstrap/perfect-scrollbar/issues/920


parquet-fromcsv with writer version v2 does not stop

Describe the bug

When using the executable parquet-fromcsv to convert csv into parquet and set writer version to 2, the program won't stop. The result Parquet file's size grows indefinitely until filling up the disk.
To Reproduce

I've run with two different schema and csv files, both failed. One is from TPCH lineitem table SF10. The command is:
parquet-fromcsv -s test_schema.txt -i core_test.csv -o core_test.parquet -w 2
Without -w 2 works fine.
The TPCH lineitem schema file is:
message schema {
  optional int64 l_orderkey;
  optional int64 l_partkey;
  optional int64 l_suppkey;
  optional int64 l_linenumber;
  optional int64 l_quantity;
  optional double l_extendedprice;
  optional double l_discount;
  optional double l_tax;
  optional binary l_returnflag (String);
  optional binary l_linestatus (String);
  optional binary l_shipdate (String);
  optional binary l_commitdate (String);
  optional binary l_receiptdate (String);
  optional binary l_shipinstruct (String);
  optional binary l_shipmode (String);
  optional binary l_comment (String);
}

CSV file can be generated using TPCH tools.
Expected behavior

Additional context

Thank you for the report @XinyuZeng !

I'll pick this up. The issue is with the column l_comment. This column exhausts dict_encoder quickly and starts using FallbackEncoder.
In V1 the FallbackEncoderImpl::PLAIN encoder is used where the buffer is cleared in flush_data_page
https://github.com/apache/arrow-rs/blob/08a976f217610cc8b1dea3375fe577027460ecc3/parquet/src/arrow/arrow_writer/byte_array.rs#L282-L284
In V2 the FallbackEncoderImpl::Delta encoder is used where the buffer is not cleared in flush_data_page
https://github.com/apache/arrow-rs/blob/08a976f217610cc8b1dea3375fe577027460ecc3/parquet/src/arrow/arrow_writer/byte_array.rs#L307
The effect of this is ever growing buffer size. This ever growing buffer is written to output every mini batch (1000 rows). Hence the program's output consumes all the disk space. The fix would be to use std::mem::take(buffer) in FallbackEncoderImpl::Delta.
I see the same issue in FallbackEncoderImpl::DeltaLength too. I am assuming this should be fixed too.  However I am not sure where this is used.

cc @tustvold

FallbackEncoderImpl::DeltaLength

This will be used if the user has manually specified an encoding to use for the column, in addition to the default dictionary encoding


Actions are not loading/shown

Explorer is loading and displaying Total Actions, the rest like staking etc wont work, just loads and loads and loads. I tried Brave and Chrome couple of times

V1 is being deprecated. Please use https://iotexscan.io/,  the V2.  Thanks!

Thanks.
Some feedback:

There is no export function at all in this "new" version. This is incredibly important for imports into accounting tools.
Also I have to open every tx to see the date. Not even the (pretty useless) "age" is visible anymore. Please add a row with the concrete date of the tx.
Please re-add a filter to sort for certain transaction types in the subcategories so I dont have to go through all of them to find one. Filter was there in v1 but is now gone. Why?

If this should become a real v2 please add those functions. Without them it seems like a huge step backwards and is just an incredible hassle to use.
Thank you for your work!


Load test deploying apps

Hi, I've done some load tests deploying apps through Git, I deployed 10 apps concurrently. I've found some errors related with the SSH connection but I'm not sure what's  the issue:
[ERROR] Failed handshake: EOF
Accepted connection.
---> [ERROR] Failed handshake: EOF
Accepted connection.
---> [ERROR] Failed handshake: ssh: invalid packet length, packet too large

[ERROR] Failed git receive: Failed to run git pre-receive hook:  (signal: broken pipe)

The only similar error I'm aware of usually derives from ELB configuration: https://deis.com/docs/workflow/managing-workflow/configuring-load-balancers/#idle-connection-timeouts
It's also possible that the load on the controller or builder caused it to miss a livenessCheck, which could cause Kubernetes to stop routing its traffic temporarily.
@arkkanoid is this with Deis Workflow v2.5.1 or earlier? Do you have a test script or steps to help reproduce this error?

The issue is on version v2.4.2.
I simply ran 'git push deis branch' on apps with 15MB of data code.
I ran it to 10 different apps concurrently.
2/10 deploys had this error.
The git push is from an EC2 instance to the Deis ELB.
The controller and the builder have 0 restarts.

Complete logs:

Just to check, did you increase the AWS ELB timeout to 1200s as recommended in our docs?

Yes, I increased it to 2000 sec.

@arkkanoid my apologies for not following up here--I was kind of out of ideas.
Is this still reproducible in current Deis Workflow (v2.6.0)? And do you have an example of one of these apps with 15MB of data code I could use to try to test this?

Sorry I solved it few weeks ago. I think it was an error related with the DNS resolution service. I updated it to a new Kubernetes version and it works now.
Thanks!


[docs] Fix build on windows

[x] I have followed (at least) the PR section of the contributing guide.

Refactor aliases to it's own file, reducing repetition
Add alias to next.config.js

Without adding alias to next.config.js yarn docs:build fails on my machine

This sounds like you refactored and then the build broke requiring even more aliases . This seems like a step back. Now our next build has babel and webpack aliases making module resolution even more opaque.

It has always been broken for me, the refactor was to not repeat the alias.
I can revert the refactor and just add the alias directly

Without the alias in next.config.js:
$ yarn docs:build
yarn run v1.15.2
$ rimraf .next && cross-env NODE_ENV=production BABEL_ENV=docs-production next build
Creating an optimized production build ...

> Using external babel configuration
> Location: "E:\material-ui\babel.config.js"
Failed to compile.

<EMAIL_ADDRESS>Module not found: Can't resolve '@material-ui/core' in 'E:\material-ui\node_modules\@material-ui\pickers\dist'

> Build error occurred
Error: > Build failed because of webpack errors
    at Object.build [as default] (E:\material-ui\node_modules\next\dist\build\index.js:154:15)
    at processTicksAndRejections (internal/process/task_queues.js:89:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

$ yarn docs:build
yarn run v1.16.0
$ rimraf .next && cross-env NODE_ENV=production BABEL_ENV=docs-production next b
uild
Creating an optimized production build ...

> Using external babel configuration
> Location: "D:\material-ui\Desktop\material-ui\babel.config.js"
Failed to compile.

<EMAIL_ADDRESS>Module not found: Can't resolve '@material-ui/core' in 'D:\material-ui\
material-ui\node_modules\@material-ui\pickers\dist'

> Build error occurred
Error: > Build failed because of webpack errors
    at Object.build [as default] (D:\material-ui\node_modul
es\next\dist\build\index.js:154:15)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this comm
and.

I can confirm the issue :P

<EMAIL_ADDRESS>
Wait, nextjs is picking up the esm build of pickers on windows?
In this form this change seems very brittle. On the surface level this is just redundant but it seems like a subtle difference is introduced with this change.
I'd like to put this on hold until #16046 comes to a conclusion. But if this does get merged we need to understand why we both need babel alias and webpack alias.

But if this does get merged we need to understand why we both need babel alias and webpack alias.

@eps1lon I figured it out, there is a bug in next-plugin-transpile-modules which has been fixed in the renamed version next-transpile-modules


[PropTypes] Allow React components for matchElement

Hi @helior and many thanks for your library! With react-highlighter I got from zero to all done in just 10 minutes, which is mind-blowing even in the React world!
I'm writing to share a minor issue I've faced when using <Highlight /> together with styled-components. Here's my code:
import styled from "styled-components";

const HighlightMark = styled.span`
  background: rgba(255, 255, 0, 0.3);
  border-radius: 4px;
  display: inline-block;
  margin: auto -3px;
  padding: 0 3px;
`;

// ...

<Highlight search={highlightRegexp || false} matchElement={HighlightMark}>
  {text}
</Highlight>

This produces a warning in development environment:
Warning: Failed prop type: Invalid prop `matchElement` of type `function` supplied to `Highlighter`, expected `string`.

It'd be great if matchElement in PropTypes allowed using custom react components in addition to strings. The issue is only with the warning – all working great apart from that 🎉

@helior would you be happy to release a new patch version if I submit a PR?

Hi @kachkaev, I'm glad to hear you were up in running so quickly 👍 . This is a great idea to define components for the matching element. If you have a PR, I would be happy to release a version with the new feature.

Here you go: #56 🙌
Looking forward for a new patch release! 😉


Use single package for both iOS and macOS. Add support for SPM on macOS.

Is there any reason why there are two separate repositories for macOS and iOS version of this library?
It'd be way more convenient to have a single package for both platforms which conditionally compiles some source files.

macOS package doesn't support Swift Package Manager right now. Would be great if Agora could add support for it :)

Sorry I haven't been ontop of the issues on this repo!

Yes I completely agree; this is something being worked on, in addition to other apple platforms
I believe the sdk team are no longer supporting a separate audio SDK for macOS, and possibly iOS soon too. The size of the SDK is pretty much the same for audio vs video, so there's not much point to it.


Please also add error handling example

Hi!
Really like your library.
I cannot figure out how to make it handle errors (wrong URL for example).
Could you add this somewhere?
Greetings,
Martin

Hi,
You're completely right, I'll add a couple of examples in the next few days.
Thank you, for your input.

Any update on this? Don't see any error handling in the examples...

would love to see some examples of error handling as well

I've added one example that covers various cases of how to handle errors.

@ruipgil Awesome, thanks. Does the same approach of using throw work in the DynamicScraper?

Good point @chmac ! In the dynamic scraper, exceptions from the scrape promise cannot be catch by the onError promise. I may tweak the code to take it into account.


Using ES_TAGS_AS_FIELDS_INCLUDE writes a giant blob of tags as well as the fields

Describe the bug
I'm not entirely sure from the documentation if this is intended, or a bug...
I'm trying to use ES_TAGS_AS_FIELDS_INCLUDE to decide which tags get written as fields to Elasticsearch.  This works quite nicely, however as well as writing my desired fields I also get a blob called tags which contains the raw data.
The purpose of me using ES_TAGS_AS_FIELDS_INCLUDE is to reduce the ingestion data for stuff we don't care about, so it's counter productive for me to also write a big blob such as this.
To Reproduce
Steps to reproduce the behavior:

Configure a collector with ES_TAGS_AS_FIELDS_INCLUDE as a subset of available tags
Observe what gets written to elasticsearch

Expected behavior
The tags field to not be written when using ES_TAGS_AS_FIELDS_INCLUDE, or have a documented means of not writing it.  I appreciate i could drop it on the ES side, but at that point it's already been transferred (data egress costs) and also means i'm maintaining two lots of config for fields, in different places.
Screenshots

Version (please complete the following information):

Jaeger version: 1.27.0
Deployment: Kubernetes

What troubleshooting steps did you try?
Reading documentation.
Additional context
Add any other context about the problem here.

This sounds like a bug.
@Stono would you like to fix it?

No thanks, I already commit a lot of my spare time to other open source work and I don't have capacity for more.

thanks is fine, thanks for reporting anyways.

@pavolloffay can you review the PR. Happy to make any changes if required.

@Stono can you confirm if you want to remove the raw data altogether or not. My understanding is that you want an option to remove the last 'tags' entry (in the screenshot) completely. You have already extracted the data you need in fields so the rest of the data (raw blob of data) is simply eating up space. Right ?

Hey, yes that’s exactly it :)

If the code already avoids data duplication, then there is no bug, and I don't agree that it needs to be fixed, at least not in the ES storage implementation. Storage stores what it is given, it does not drop data. If you need to filter out data from the spans, it should be done earlier in the pipeline, independent of the storage. For example, OTEL collector may already have components like that, and would be the adequate place to do it.

Isn’t this the product of this specific storage driver though?
eg it uses the tags to creat es fields but still stored the original tags block, which is redundant?
how could you do it earlier in the proces?

If it duplicates the tags in fields and blob, then it's a bug. If it cleanly partitions the tags into fields and blob, then it works as designed.

99% sure it does duplicate, but it was a while ago when I was experimenting with it.  I’ll test again tomorrow and let you know for sure.

@yurishkuro It's not exactly a bug it's more of a new feature. I completely agree. It completely partitions the tags properly.
If we remove the remaining tags before ES, like you suggested, would it be acceptable ?

I think it's a reasonable feature to have pruning of the tags somewhere in the pipeline. Again, I would suggest checking OTEL collector plug-ins if they already have it, and if not then perhaps implementing it there. The reasons are: a) we're working on rebuilding Jaeger backend on top of OTEL collector, so the same functionality will be available in Jaeger directly, and b) OTEL has more flexible configuration for these pipeline plugins than Jaeger. Not to mention that OTEL collector can be run earlier in the pipeline and reduce the overall data throughput if you drop the tags early.

ok. Thanks for the support @yurishkuro ! 🙂


Viasp backend quickstart

Hi Luis,
please just ignore this pull request. I accidentally pulled to your repo instead of to my fork.
I'm working with Javier to extend viasp, btw.


[proposal] Add Padding and ScrollPhysics to ReorderableListView

it is possible to wrap the child in padding and give it some space but the shadow effect will be broke completely.
so add a possibility in ReorderableListView to change shadow offset or itemSpacing.

screen shot of bad shadow

also it is not possible to use custom physics.
I am using BouncingScrollPhysics for all of scrolling items in my app.
excuse me but this misbehaved widget is weird from flutter team

Hi @mohammadne
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @TahaTesser
this is the code :
import 'package:flutter/material.dart';
import 'package:mate_machine/util/style.dart';

class CustomOptionDragger extends StatefulWidget {
  const CustomOptionDragger(this.options);
  final List<String> options;

  @override
  _CustomOptionDraggerState createState() => _CustomOptionDraggerState();
}

class _CustomOptionDraggerState extends State<CustomOptionDragger> {
  List<String> options;

  @override
  void initState() {
    super.initState();
    options = widget.options;
  }

  @override
  Widget build(BuildContext context) {
    return ScrollConfiguration(
      behavior: ScrollBehavior(),
      child: GlowingOverscrollIndicator(
        color: Colors.white,
        axisDirection: AxisDirection.down,
        child: ReorderableListView(
          onReorder: _onReorder,
          padding: EdgeInsets.symmetric(vertical: 4),
          children: List.generate(
            options.length,
            (int index) => BuildOptionDraggerItem(
              index: index + 1,
              text: options[index],
            ),
          ),
        ),
      ),
    );
  }

  void _onReorder(int oldIndex, int newIndex) {
    setState(
      () {
        if (newIndex > oldIndex) {
          newIndex -= 1;
        }
        final String item = options.removeAt(oldIndex);
        options.insert(newIndex, item);
      },
    );
  }
}

class BuildOptionDraggerItem extends StatelessWidget {
  BuildOptionDraggerItem({this.text, this.index}) : super(key: ValueKey(text));
  final String text;
  final int index;

  @override
  Widget build(BuildContext context) {
    final style = Style.instance;
    final textTheme = Theme.of(context).textTheme;

    return Container(
      constraints: BoxConstraints(minHeight: 52),
      width: double.infinity,
      padding: EdgeInsets.symmetric(vertical: 8),
      margin: EdgeInsets.symmetric(vertical: 10),
      decoration: BoxDecoration(
        color: Colors.white,
        border: Border.all(color: style.colors.grey),
        borderRadius: BorderRadius.circular(style.borderRadius.main),
      ),
      child: Row(
        children: <Widget>[
          Padding(
            padding: EdgeInsets.symmetric(horizontal: 12),
            child: Text(
              index.toString(),
              style:
                  textTheme.subtitle2.copyWith(color: style.colors.disabled2),
            ),
          ),
          Expanded(
            child: Text(
              text,
              style: textTheme.subtitle1,
              textAlign: TextAlign.center,
            ),
          ),
          Padding(
            padding: EdgeInsets.symmetric(horizontal: 12),
            child: Text(
              "⋮⋮",
              style:
                  textTheme.subtitle2.copyWith(color: style.colors.disabled1),
            ),
          ),
        ],
      ),
    );
  }
}

the part
ScrollConfiguration(
      behavior: ScrollBehavior(),
      child: GlowingOverscrollIndicator(
        color: Colors.white,

I add that to reduce physics effect , because I couldn't use Bouncing Scroll Physics

flutter doctor -v :
[√] Flutter (Channel beta, v1.17.0, on Microsoft Windows [Version 10.0.18363.720], locale fa-IR)
    • Flutter version 1.17.0 at C:\flutter
    • Framework revision d3ed9ec945 (3 weeks ago), 2020-04-06 14:07:34 -0700
    • Engine revision c9506cb8e9
    • Dart version 2.8.0 (build 2.8.0-dev.18.0 eea9717938)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\Nasr\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: C:\Users\Nasr\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\192.6308749\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    X Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit visit https://flutter.dev/docs/get-started/install/windows#android-setup for
      detailed instructions.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.5)
    • Android Studio at C:\Users\Nasr\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\191.6010548
    • Flutter plugin version 44.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] Android Studio (version 3.6)
    • Android Studio at C:\Users\Nasr\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\192.6308749
    • Flutter plugin version 44.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[!] IntelliJ IDEA Ultimate Edition (version 2019.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.2.4
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[√] VS Code (version 1.44.2)
    • VS Code at C:\Users\Nasr\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.9.1

[√] Connected device (3 available)
    • AOSP on IA Emulator • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • Chrome              • chrome        • web-javascript • Google Chrome 81.0.4044.129
    • Web Server          • web-server    • web-javascript • Flutter Tools

! Doctor found issues in 2 categories.
➜  /d/Mohammad/Programming/Flutter/mate_machine git:(develop) ✗

Hi @mohammadne
regardless the intrinsic issue with the shadows
would a constructor similar to ListView.separated fit your needs?
Thank you

yes , and how about physics?
how can I use BouncingScrollPhysics ?

and Do you add ListView.separated for ReorderableListView ?

@iapicca A constructor would be great. Would it be possible to decouple more things (ie add as parameters) from the ReorderableListView, such as decoration / shadow color (#45799), animation (like onDrag, onDragStart, onDragEnd, etc) and so on? Currently it feels very Material heavy but it may work better as a general widget onto which people can add their own decorations, Material, Cupertino, or otherwise. I also do some work in the React ecosystem and I've found some interesting libraries that handle the low level dragging stuff as well, not sure if this is useful to you as highlighting what I mean:
framer-motion: https://codesandbox.io/s/framer-motion-drag-to-reorder-wip-nuiz9
react-spring + react-use-gesture: https://codesandbox.io/s/draggable-list-fh8r8

@shihaohong I would like to work on this issue about adding the physics property in the ReorderableListView. I would also look at the possibility of adding a ReorderableListView.separator if team is looking to add it.

Padding and scroll physics are supported now. Closing this as completed.


License

Hey,
Thanks for releasing this. Could you clarify the license of the repo, couldn't find it anywhere in the Readme/code.
Is it MIT?

Hi, sorry, I've just added it. Yes, it is MIT.


Fix issue with argument entityName

The condition was always true, even if the entityName was not provided, that could cause issues

@gregquat thanks


fix(autoware_auto_tf2): modify build error in rolling

Description

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@esteve Thank you for notifying me.
Okay, then I'll send another PR to fix them. Please review it later!

@wep21 Thank you for fixing typos, but I think it's better to split PRs.
So could you wait for #751?

@kenji-miyake sorry, I meant @wep21 :sweat_smile: , I guess I pinged you because I was reviewing #210

Oh, lol. :smile:
But yeah, it's alright.

@kenji-miyake

So could you wait for https://github.com/autowarefoundation/autoware.universe/pull/751?

I will rebase after #751 is merged.

@esteve @kenji-miyake I've finished. Could you review again?

@esteve It seems your comment https://github.com/autowarefoundation/autoware.universe/pull/718#discussion_r852042154 is resolved, I'll clear your review status. :bow:


Find a way to package python driver wheels

Currently the packaging part packages python driver as source package zip file
We should find a way to package wheels, since in python 3.12 we'll need the libev eventloop enable, otherwise we'll fall back to asyncio which isn't full operational yet
Or error, not find a default eventloop
We might in the process need to change the package to be arch specific, so we won't pack all architectures, or find a way to select correctly the wheel to load

Using shiv might elevate some of the issues, and allow having a full virtual env included include binary wheels
https://github.com/linkedin/shiv

taking this change for ride in scylla:
https://github.com/scylladb/scylladb/pull/19385
to see if it would be compiled, packaged, and running in dtest as expected

Note: one would need to check if scylla-pkg need any adaptation for this


Add minimal regression test

Take as input test.log, produce test.sql. Compare to test_expected.sql
As we discover new log parsing shenanigans ensure that this original test data set does not regress.

closed with f1fa1321


add block size to unikernel_info, also add the possibility to change arguments in restart

//cc @PizieDust @reynir
There's still more work needed to retain backwards compatibility.
The main question I have is about the albatross-client.. Now the restart subcommand can replace the arguments, but this is guarded by an additional flag "--replace-arguments". I came there since just checking whether the arguments are provided or not does not suffice (due to default values, and also maybe a user wants to restart their "hello world" this time with providing no argv at all. -- this wouldn't easily be possible without such a flag. Still it makes me wonder whether we want a separate (sub)command for it -- but then I struggle with naming. Any ideas?
Also, the restart-with-arguments-replaced can't check the manifest on the client side (since there's no image available)... I'm hesitating on what to do here -- I'd like to avoid someone to do a restart and end up with "sorry, your arguments didn't specify the required devices". Any ideas?

I added the needed backwards-compatibility code. This is ready for review.
So, old clients can talk to new servers. There's no attempt to make new clients talk to old servers (they'd need to send old commands, so figure out which version the server has before sending the initial command, or re-connect on failure and try with an older version).

Maybe to elaborate a bit: we're not concerned about API versioning / compatibility here. We just upgrade the API as we want. ;)
What we are concerned are the clients and servers that are deployed by different parties (i.e. not under our control), so esp. an old client should not be punished by our server. In this specific PR, the old client will get reasonable (the same, expected) answers from the new server.
This means that in our serialisation (vmm_asn.ml), we do some extra work to keep track of the old wire formats. In addition the `Old_unikernel_info3 has been introduced (used to be named `Unikernel_info), which now results in the `Old_unikernels_info3 (used to be `Unikernel_info) -- the wire format of these two constructors is preserved -- the naming differs, since the current one (used by up-to-date clients and servers) is named `Unikernel_info.
For the restart, it is slightly simpler, since the old command did result in a generic reply - not a specific one (i.e. a success or an error only) -- here we can just translate the old wire format to `Unikernel_restart None to preserve the existing behaviour.
I guess reading the diff is sometimes confusing (as is writing the code) - and we should add tests for the different versions. But I've been too lazy for writing these tests.


Add make fmt for src

Description
Adds make command for code formatting.
Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[ ] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[ ] :computer: CI/Deployment
[x] :broom: Tech Debt/Cleanup

I'm curious as to why these things (especially import ordering) aren't causing lint failures in CI

Yeah, I am a bit concerned about that too. Except for the betasdk(which we skip), I can' think of a reason why it would not have already failed in CI.


[LOC] Broken translation (ja-jp)

ja-jp:"https://docs.microsoft.com/ja-jp/microsoftteams/accessibility-solutions-in-france"

en-us:"https://docs.microsoft.com/en-us/microsoftteams/accessibility-solutions-in-france"

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: 78884968-d899-5744-dda1-b74276c33c07
Version Independent ID: b8d04634-e8f3-cdc4-6ad2-5b8a9a67982a
Content: Skype for Business Online および Microsoft Teams のアクセシビリティ ソリューション
Content Source: Teams/accessibility-solutions-in-france.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@hyoshioka0128 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@OfficeGlobal @samanthaw

related to #2950

@Reeced40  It seem, it's the same issue - is the french text expected in ENG version?

@OfficeGlobal I see the heading is in English but the content is in French, what would you suggest?

@tonysmit could you please confirm French is expected in ENG article?

@tonysmit Following up on the above request. Thanks!

This article is intended for French market only, and is not localized on purpose. It only exists in the en-us docset in French because that is our source repo.


GO:0001871     pattern binding

very bad
GO:0001871     pattern binding
Interacting selectively and non-covalently with a repeating or polymeric structure, such as a polysaccharide or peptidoglycan. PMID:12072369 PMID:12225919 PMID:12507420 PMID:12925128 PMID:14523544
This is a terrible term.
It's a parent of
GO:0030247    polysaccharide binding | is_a
GO:0001876    lipoarabinomannan binding | is_a
and
neither of these stipulate "pattern" binding , whatever that means.... (which is actually.... nothing)
A repeated polymeric structure isn't a 'pattern'
and it has a synonym
pattern recognition activity???!!!???

Obsolete ?
No direct annotations, 2 children can be rehoused:
'lipoarabinomannan binding'
'polysaccharide binding'

Yes for sure.

Dear all,
The proposal has been made to obsolete: GO:0001871 pattern binding
The reason for obsoletion is that this term was an unnecessary grouping term. There are no annotations, no InterPro2GO mappings to this term. This term is present in one slim: goslim_pir
Any comments can be added to the issue: https://github.com/geneontology/go-ontology/issues/16620
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on November 23rd, 2018. Unless objections are received by November 23rd, 2018, we will assume that you agree to this change.
Thanks, Pascale

@nataled Do you want to replace this term by something else, or just remove it ?
Thanks, Pascale

@ukemi any idea why the term labels of some ChEBI and CARO have changed ?
https://github.com/geneontology/go-ontology/pull/16645/commits/b5841e9ab314cc035cf7f03c4f7f1d7d5ca4bc8a
should I worry about that ?

I used to see this a lot but just saw it again recently. In the past as long as identifiers were the same, I didn't worry about it. At the end of the day, it is the identifier to the external ontology that gets used. I am curious as to why this happens though. Those imports haven't been regenerated in a while.

I did an RO_import update yesterday, which came with some CARO label changes: https://github.com/geneontology/go-ontology/pull/16644/files

So, would I be merging old labels ? I did a git pull before starting.

Thanks Jim. That explains it.

@pgaudet it's just because the OBO format puts the label in a comment anywhere the term is referenced, so there is a bit of a cascading effect as different files are edited.

These pattern terms were created to match the usage of the word pattern in the scientific literature.  Not something I made up.  There are five Pubmed references associated with this term.  Did you read any of them?

For sure they are  called "pattern recognition proteins", but can  "pattern binding" really be used  in this context as a grouping term for these descendants?
Can't gene products can bind to a polysaccharide  or a peptidoglycan without being a pattern recognition molecule?  I thought the pattern binding was to refer to recognizing a specific arrangement of  saccharide residues in a polymer  ?  Presumably binding to homomeric polymers are not recoginising specific "patterns"
if it isn't always true it should be
polysaccharide binding
--polysaccharide pattern binding
with the grouping term renamed to "polymeric pattern binding"

I should have been clearer with my original request. My gripe is with the use of the word "pattern" to group "polysaccharide" and "lipoarabinomannan".
Polysaccharides occur in lots of contexts in addition to those recognised by immune molecules and these aren't called "patterns"    (cell wall polysaccharides, for example)

What is the fix? It's really unclear to have
"pattern binding" as a parent of
"GO:0030247    polysaccharide binding "
It really means to bind a repeating motif in a polymer .
This would be analogous to making  "DNA lop binding" a parent of "DNA binding" or "protein motif binding " a parent of "protein binding". It doesn't seem to be ontologically correct as it is....

The fix is that pattern binding is now obsolete.

GO:0030247 polysaccharide binding  is now a child of carbohydrate binding
GO:0001876    lipoarabinomannan binding is a GPI anchor binding.

This is consistent with the MF structure. The 'pattern binding' aspect is relevant for the signaling BPs (see other tickets).
OK ?
Thanks, Pascale

I think the term is valuable for "polymeric pattern binding", but it in the wrong place.
Should wait for @addiehl  to comment on my suggestion to move  and specify it.

I am okay if 'pattern binding' goes away as a MF term, if pattern seems too vague and not referring to binding of a specific chemical class of molecules.  However, the mechanism of binding polysaccharides and related structures of bacterial origin as a means for activating the innate immune response and regulating the type of adaptive immune response that develops subsequently is well investigated (and indeed, was already well understood in 2005-2006 when I worked on many of these terms) and researchers in this field had already settled on the phrase 'pathogen-associated molecular patterns' to describe the targets of particular receptors and their signaling pathways, so we need continue to represent associated biological processes appropriately.

But isn't this just a normal binding? Can we not make the distinction under BP ?
I think many of the children are NOT relevant to the kind of pattern binding we are discussing:
(children of polysaccharide binding):
'(1->3),(1->4)-beta-glucan binding'
'(1->3)-beta-D-glucan binding'
'(1->4)-beta-D-galactan binding'
'(1->6)-beta-D-glucan binding'
'alpha-D-glucan binding'
'arabinogalactan binding'
'cellodextrin binding'
'cellulose binding'
'cyclodextrin binding'
'galacturonan binding'
'glycogen binding'
'heteropolysaccharide binding'
'inulin binding'
'mannan binding'
'pullulan binding'
'starch binding'
'xylan binding'
These are all inferred from ChEBI.
Pascale

well,  if we can convey the meaning precisely with the receptor function terms, probably there is no need for this term in binding.

This depends on the outcome of https://github.com/geneontology/go-ontology/issues/16616

Q would the "pattern binding" term be used for any other gene products apart from receptors ?


'onRef' inyecting null ref on event handler

Issue
Hi there! The onRef event's handler is inyecting null ref ({ current: null }) when mounting the <DraggableFlatList /> component. Any ideas why could this be?
Here's my code:
<DraggableFlatList
    onRef={ref => {
	alert(JSON.stringify(ref));
    }} ... />

Platform & Dependencies

Platform: Android
React Native: 0.61.5
Reanimated version: 1.8.0
React Native Gesture Handler version: 1.6.1

Thanks in advance for your help.

Refs are always null on first render -- there's no backing element until the component has mounted. Typically you'd do any ref-based logic in componentDidMount or equivalent.
Is the ref correctly populated once mounted?

Issue
Hi there! The onRef event's handler is inyecting null ref ({ current: null }) when mounting the <DraggableFlatList /> component. Any ideas why could this be?
Here's my code:
<DraggableFlatList
    onRef={ref => {
	alert(JSON.stringify(ref));
    }} ... />

Platform & Dependencies

Platform: Android
React Native: 0.61.5
Reanimated version: 1.8.0
React Native Gesture Handler version: 1.6.1

Thanks in advance for your help.

I have the same probem :/

Refs are always null on first render -- there's no backing element until the component has mounted. Typically you'd do any ref-based logic in componentDidMount or equivalent.
Is the ref correctly populated once mounted?

Thanks for answering! Nope. As @terrorpixel points out, we are getting a null ref everytime.
By the way, I'm using version 2.3.2 of the plugin.

@mcama are you sure about that?
I just did a quick hacky check by logging the ref in a setTimeout and I see the populated ref:
          onRef={ref => {
            console.log("initial ref", ref.current)
            setTimeout(() => console.log("timeout ref", ref))
          }}

Now it's working! 🎉
<DraggableFlatList
   onRef={ ref => { exampleRef = ref }}
   />

// somewhere else
exampleRef.current._component.scrollToOffset({offset: 100, animated: true});

(Functional component)
My fault was to define exampleRef as a ref in addition by this line:
let exampleRef = React.useRef(); // don't use that

In that case exampleRef just persists "null". Sorry, I'm a rookie :neckbeard:

The issue was in fact a mistake in my code too... My bad! Thanks for your feedback @terrorpixel and thanks @computerjazz for this awesome plugin.

@terrorpixel could you explain why you don't have to declare exampleRef before onRef?


Thanks for your help!

I'd like to express my gratitude for sharing your guide on building a custom component. As I'm not a Python developer, I encountered some difficulties understanding certain aspects in the documentation. However, after following your tutorial, I was able to successfully implement an integration for my alarm central.
Here is the repository:  https://github.com/merencia/amt8000-hass-integration
Thank you!

I'm glad this was helpful to you :tada: !  At some point this tutorial needs some updates as a lot has changed since I first wrote it.


Update deploy-docs.yml

User description

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[ ] No

ℹ Additional Information

Description

Enhanced the deployment workflow by updating GitHub Actions and Node.js version.
Added a deployment step to GitHub Pages for better documentation accessibility.

Changes walkthrough 📝
Relevant filesEnhancement

deploy-docs.ymlUpdate GitHub Actions and Node.js version in deploy-docs.yml

.github/workflows/deploy-docs.yml
Updated GitHub Actions versions for better performance.  Changed Node.js version from '16' to '20'.  Added a step for deploying to GitHub Pages.

+5/-3

💡 Penify usage:
Comment /help on the PR to get a list of all available Penify tools and their descriptions

Summary by CodeRabbit

Chores

Updated documentation deployment workflow to use newer action versions and Node.js 20.
Added a new step for deploying to GitHub Pages.

:white_check_mark: Build VTEX-SDK-dotnet 2.3.1119 completed (commit https://github.com/guibranco/VTEX-SDK-dotnet/commit/971a0acd2d by @guibranco)


Axis-Aligned Brush

Summary
This feature introduces the concept of an axis aligned cuboid, which will be referred to as a "brush". A brush can be textured on all six sides with wall textures and sized in editor. The aim is to reduce the number of custom meshes needed to prop out a level.
Goals

A brush can be created and sized in editor.
Each brush face can be uniquely textured. Both the tex id and wall atlas.

For convention call the brush faces top, bottom, left, right, front, and back.

The brush should dynamically UV itself to neatly tile.

Stretch Goals

A brush can be rotated arbitrarily.

Feature request, configurable incremental adjustment. Snap edges to grid sizes 1 texel and higher configurable in the brush editor menu. Extrusion widgets, grabbable arrows on each face, drag to extrude face along axis, similar to blender's translation widget.

Perhaps we could compromise by reusing the existing tile handles? But yeah, I'd love a nicer way to resize things.

Perhaps we could compromise by reusing the existing tile handles? But yeah, I'd love a nicer way to resize things.

Yeah that could be a great alternative!


Host UI - Application Submit Button - Loading Animation

Issue:

https://github.com/bcgov/entity/issues/23658

Description of changes:
Fixes issue with applications being submitted multiple times.
Desktop

Mobile

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-251-u0zpa1gr.web.app

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-251-u0zpa1gr.web.app


Present EIP-712 nicer

Is your feature request related to a problem? Please describe.
When signing any offchain data using EIP-712, TrustWallet present the user in a non-user friendly way.
It presents just a JSON blob.
The users have a hard time verifying what they sign, which is a security concern.
Describe the solution you'd like
Do something like Metamask do, present the structured data:

Additional context
You can try to trade in https://cowswap.exchange/ to validate the feature

This is a known issue, we will consider improving it and thanks for the report.

Note that this also affects OpenSea NFT listing, which is probably the most popular use case for wallet signatures at the moment. User sees a giant JSON blob.

Please check latest iOS build in App Store, user can navigate the JSON easily now, Android will follow similar idea later

@hewigovens i just updated the IOS app 7.0, it stills look pretty not user friendly:

I would honestly reopen the issue

Can you try WalletConnect? Dapp browser will be updated later (just added back finally)


feat: Add Go to Runner Image

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

GitHub release
v1.3.0

Your semantic-release bot :package::rocket:


When Creating a new product it says, please edit mod_servicehosting_order_form.phtml file in order to change order form for hosting category products.

When Creating a new product it says, please edit mod_servicehosting_order_form.phtml file in order to change order form for hosting category products.
and when  we click on open editor editor does not open correctly.

Please perform changes from commit above or download new release with this bugfix included.

Hi, I have latest version installed & still get this error

Which error are you talking about? Filemanager error was fixed in commit above. Do you see files when you open file manager? Are you talking about this informational message? If yes, you need to edit the form only if you want to change order form for particular product.

sorry, my bad...appologies

edit mod_servicedomain_order_form.phtml file in order to change order form for domain category products.

RENAMME SERVISEDOMAIN Menjadi domain


Artnet Input is not listening on unicast, only on broadcast // SoundSwitch broken

Hello everyone !
I had problems with communicating SoundSwitch with QLC+
Discovered then that QLC+ in ArtPollReply packets sends IP address of listening interface.
https://github.com/mcallegari/qlcplus/blob/master/plugins/artnet/src/artnetpacketizer.cpp#L74
The problem is I see that you can't communicate with QLC+ using unicast as it only listens on broadcast.
https://github.com/mcallegari/qlcplus/blob/master/plugins/artnet/src/artnetcontroller.cpp#L56
I am talking about macOS build. I manually changed ArtPollReply packet to send broadcast address and suddenly DMX data was received correctly.

@mcallegari

How much are you willing to pay to have this change done?
Because you paid for SoundSwitch, right?

I've found a bug in this project that has nothing to do with any 3rd party application.
ArtnetPoolReply packet has an advertisement IP that is not matching with the UDP socket that QLC+ is listening to.
This is a bug in QLC+.

I've found a bug in this project that has nothing to do with any 3rd party application.
ArtnetPoolReply packet has an advertisement IP that is not matching with the UDP socket that QLC+ is listening to.
This is a bug in QLC+.

it's ArtPoll, not ArtPool
You mentioned Soundswitch in the ticket title, so IT HAS to do with a 3rd party application
as far as I can recall, no one reported this before
this is a bug in your opinion. A missing feature in my opinion. Many other users successfully used ArtNet input with QLC+
I'm not suggesting this is an invalid report, I am suggesting you guys don't appreciate free software. Go ask Soundswitch to broadcast on ArtNet and see what they reply. I just tested if/how much you are willing to contribute to this project for me to work on your request. As I suspected, the answer is: zero.

it's ArtPoll, not ArtPool
You mentioned Soundswitch in the ticket title, so IT HAS to do with a 3rd party application
as far as I can recall, no one reported this before
this is a bug in your opinion. A missing feature in my opinion. Many other users successfully used ArtNet input with QLC+
I'm not suggesting this is an invalid report, I am suggesting you guys don't appreciate free software. Go ask Soundswitch to broadcast on ArtNet and see what they reply. I just tested if/how much you are willing to contribute to this project for me to work on your request. As I suspected, the answer is: zero.

For the record, I just checked with 2 PCs running both Linux.
Transmitter with IP <IP_ADDRESS>/<IP_ADDRESS> and the receiver with IP <IP_ADDRESS>/<IP_ADDRESS>
Transmission on <IP_ADDRESS> (QLC+ default) or <IP_ADDRESS> doesn't make any difference for the receiver.
Both configurations work. I double checked with Wireshark.
So the OP is either an error on subnets or specific to macOS.
Therefore I need to check also on Windows and macOS

For the record, I just checked with 2 PCs running both Linux.
Transmitter with IP <IP_ADDRESS>/<IP_ADDRESS> and the receiver with IP <IP_ADDRESS>/<IP_ADDRESS>
Transmission on <IP_ADDRESS> (QLC+ default) or <IP_ADDRESS> doesn't make any difference for the receiver.
Both configurations work. I double checked with Wireshark.
So the OP is either an error on subnets or specific to macOS.
Therefore I need to check also on Windows and macOS

Finally tested also on macOS. The behaviour is the same of Linux and Windows, so QLC+ is receiving data correctly from broadcast or unicast.
Therefore this report is invalid.

Finally tested also on macOS. The behaviour is the same of Linux and Windows, so QLC+ is receiving data correctly from broadcast or unicast.
Therefore this report is invalid.

Honestly, this is borderline harassment - do you expect anyone to help if the first reply they get is "are you paying"? I mean come on.


Missing codeCoverageRestoreOriginalPomXml  property in documentation

This documentation is missing codeCoverageRestoreOriginalPomXml option.

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

ID: 81921de1-7801-99b8-30ff-92530ceb49b2
Version Independent ID: 50fb21ad-2049-fd80-db73-3d78c305cdac
Content: Maven build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/maven.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

@meehaws That task input has been added in our new task reference: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/maven-v4?view=azure-pipelines
Thank you for letting us know.


ui.prefersReducedMotion

Twice in a document with different values. First it is enabled, and then, according to the instructions for non-RFP users, it is disabled.

Correct. It's disabled as part of RFP because that comes before the one in RFP alts: so it makes no sense to put it in the 5000's, inactive, and ask users to add it as an override: so it's enabled active be default and does not affect fingerprinting (due to RFP)
But if a user decides to disable RFP and instead they turn on the RFP Alts section, then the second value is applied last, and the fingerprinting is still covered
how a user.js works

It parses the user.js in the order it is written, i.e if the same preference is listed twice with two different values, the last one will be applied last

/* 4520: disable chrome animations [FF77+] [RESTART]

Where is the FPing/Security?

Are you asking how PRM is fingerprintable (it is), or why it's included when all the other prefs not in 5000s have some sort of privacy/security/anti-tracking/anti-FPing aspect and this one doesn't?

I'm wondering why we need to disable animations for firefox. There is no security issue and I don't see the FPing (as long as RFP is used).

Because Mozilla tied a chrome setting to a web setting
The pref is already covered by RFP, but if we enforce it as 1 (which leaks with no RFP) then no-one will need to add it as an override to disable the megabar etc, which means anyone who then needs to flip on RFP Alts is not compromised
capisce?

@Thorin-Oakenpants Is there anything you have not think of at all? 😄 ❤

@Thorin-Oakenpants Is there anything you have not think of at all? 😄 ❤

I forgot my mom's birthday once .. she's never let me live it down ... 47 years and counting .. *sigh*


Unable to load json models in React app

Issue Description
I am unable to load the json models in a React webapp. I get the following error: Failed to parse model JSON of response from ../models/blazeface-back.json. .
Human() is working (with config as well), and gives back the expected the result. When calling .detect(image) on human, it gives this error that it was unable to load the models. I tried overwriting the basepath etc, but that didn't seem to help either.
Steps to Reproduce
Start a react app with typescript template. Add the package ( I used yarn ). I try to run the code to detect my face on an image I have of myself. I import with
import Human from '@vladmandic/human';
also tried different types of input like import Human from<EMAIL_ADDRESS>Expected Behavior
Give some result of the detect method instead of an error on not being able to load the models.
**Environment
Tried different versions of the package, 1.4.1, 1.5.1, and also some older ones. Same issue.
Running in latest version of Chrome and Firefox.
Mac OS
Running with yarn react-scripts start
Additional
https://gist.github.com/roelandwyns/95c2bd6b43f9b1a07bda6d1e9ea63ffc

Thanks in advance! Awesome library, would love to integrate it in a react app :)

One quick suggestion - can you try placing models in a folder below your server root, not above it? http requests deal poorly with .. in paths. so your modelBasePath = 'models/'
Second, check the network tab of your browser inspector:

what is the http status code for the blazeface-back.json
what is it's MIME type (I've seen cases where misconfigured web server returns incorrect MIME type so client doesn't know what it received)
can you actually see a JSON response when you select that network request in browser?
copy the URL from that network request and try to access it manually in a new browser tab - can you actually download the file correctly?

Thank you for the quick response!
I tried the modelBasePath changing (already tried it with the absolute paths as well).
HTTP status code is 200 and content type is text/html; charset=UTF-8 .
On the third thing in the network tab, I am unable to see the json response of the file in the browser, in the response it gives back my index.html from my react-app, which is probably wrong. -> same goes for copying that url, it gives me back the react app instead of the json file. Will look deeper into it this week!
Thanks again for the quick reaction, I will try to check what went wrong with it this week! :)

definitely a local web server issue.
btw, you can try using a local web server that ships with human instead: npm run dev

You can close the issue, I will look deeper into it. But indeed not a library issue!

any update on this? i have the same issue

@stefanCojocariu what is the web server you're using? how is it configures? and did you try using built-in dev web server that ships with human library?

I have a reactjs basic project, that's started with react-scripts start. It's running on localhost. I placed the models in src folder and modified the modelBasePath to 'models', and the get request url is, for example: http://localhost:1234/models/blazeface-back.json.

Solved it just now, haha.
So the reactjs project has a public folder for serving static files, added the models folder there and modified the value of modelBasePath to 'models'. I think that will help you, too, @roelandwyns.
Thank you for the quick reply and help!

@stefanCojocariu oh that makes sense indeed! :) Didn't have time yet to check in the evenings this week, but that works perfectly! Awesome, thank you!