Only trigger alarm on movement / opening, not when sensor becomes unavailable (less safe, also less annoying)

Checklist

[x] I checked for similar existing requests (both open and closed) before posting.
[x] My request is generic, other users may benefit from it too.

Proposal
Current behavior:
Alarm triggers when binary sensor state turns to "on" (movement, open, etc), but also when sensor becomes unavailable (for instance when battery is empty)
Proposed behavior:
Alarm only trigger when binary sensor state turns to on, but not when sensor becomes unavailable.
Additional info
Reason:
for some reason the alarm triggered multiple times now in the middle of the night because a sensor was off the zigbee grid for a short time. Wakes me up for nothing :(
I tried fixing the zigbee network, but it's not 100% successful. Also the changes in temprature influence the battery of some sensors too so they suddenly seem empty.
Less secure
I do realize this option is less secure: this way if someone tampers with a sensor or the zigbee network itself, the alarm won't go off. For me, this would be a trade off that is worth while: getting waked by a false positive too many times is annoying, and I really do not expect someone to mess with this alarm installation on purpose; it's just an extra measure for sneak ins or break ins, but a serious alternative for a real alarm installation for us.
As long as the security trade off is stated clearly, I think this would be an interesting option to offer.
Hopefully I'm not the only one that looks for something like this!

Just turn off this setting to do so:

Wow I missed that completely!! Thanks a lot :)


Feature/csharp bindings extension

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

The C# bindings in Continental.eCAL.Core.dll are lacking some of the features of eCAL and some of the existing ones are not easy to use / break if used with .NET 5+
What is the new behavior?

Added minimal ServiceClient implementation

Added minimal ServiceServer implementation

Added overload to Publisher.Send() that takes a byte[] to bypass string conversion

Added GetTime() to Monitoring class

*Changed ReceiveCallbackData->data of Subscriber from string to pointer + length

*Changed return type of GetMonitoring and GetLogging() from string to byte[]

Does this introduce a breaking change?

[x] Yes (Marked with *)
[ ] No

The string conversion is cumbersome to use if eCAL is used to transmit anything (e.g. byte[]) other than strings. Also if used with .NET 5 or above the string conversion outright breaks due to breaking changes in the way encodings are handled.
I therefore suggest changing these methods or adding alternative ways to get a raw byte array which can then be handled by the consumer.
Other information

@lukaswerner  thanks for the contribution, everything is to be merged now on separate PRs.


Docker fixes

Changed dockerhub repo image to original image
Enabled pytorch CUDA support on amd64 platforms
Fixes docker scripts to (hopefully) work on mac
Fixed alias issue in zsh, rossrc now sources ~/catkin_ws/devel/setup.zsh

What was wrong with realpath? That was tested to work on mac?

I don't believe we need torchvision and torchaudio. Just the base is fine

Did we resolve the issue with user groups on Mac?


Support param builder methods returning single args.

Builder methods (that methods used by @genty_deferred) can now
return single parameters. Previous they always needed to
return a list or tuple. Thus, what used to have to be this:
def builder(...):
return (single_value,)
@genty_deferred(builder)
def test_method(...):
...
Can now be this:
def builder(...):
return single_value
@genty_deferred(builder)
def test_method(...):
...

Verified that @potrebic has signed the CLA. Thanks for the pull request!


Make stripe checkout component extendable

Killing this. Too messy. I'll resubmit it with fewer commits.


[Feature request] Add Android Wear projects to gdx-setup.jar

Generating project from gdx-setup.jar would provide build for wear alongside "android", "desktop", "ios", "html", etc.

I don't think we'll be adding Android Wear to the setup. It should be relatively easy to set up Android Wear in your project after generating it.

Do you know about setting up Wear? I've been using LibGDX with android for a while, and I can't set up a project to work with Wear without quite a few errors, which makes me think having an option to pre-generate it would be helpful.

Nope, I've never tried it... Wear isn't really a great fit for libgdx.
What type of errors are you seeing?

It's been a bit since I've tried building a Wear project, so I'll have to reload some and see what I get, but I remember issues with Gradle that weren't solved by re-installing or re-downloading. I also tried using the source for flopsy droid, but there's several errors:

ImageReference class import failed (learned that this is deprecated)
GridPagerAdapter class import failed (don't know about this class)
"Could not find com.android.support:support-v11:". Error log recommends installing Android Support Repository through the SDK manager, although it is installed and on revision 11 through the link to the SDK manager the error log provides.

Those errors seem like misconfiguration on your part, and/or missing SDK components... Which wouldn't be solved by having the setup create a Wear project.


Crash on ADR API16 (Grab has bugfix)

Summary
SSL handshake aborted: ssl=0xb96a4e90:.Found solution here
https://github.com/square/okhttp/issues/2372#issuecomment-244807676
Grab has bugfix
The original author of this bug report is Grab. They have a bug fix and would like to upstream it to MapLibre GL Native.

@wipfli @alanchenboy do we have the steps to reproduce this issue?

The map will crash when running on the ADR API16 OS, you can try because our version is an old version, so not sure if this still happens in the new version

Closing this for now.
Please re-open with a reproduction if it is still an issue.


#48 experience

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.44%. Comparing base (4c6c837) to head (10c0c0b).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #55      +/-   ##
===========================================
+ Coverage    96.07%   96.44%   +0.37%
===========================================
  Files           14       17       +3
  Lines         1274     1408     +134
  Branches        68       74       +6
===========================================
+ Hits          1224     1358     +134
  Misses          50       50

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


How to make dragging to an empty Sortable list easier?

Usually its impossible or very difficult to drag an item from one list to another, if the second list has no items in it. You can give that list some padding, but what if I want that list to take up the size of the whole screen, while still having no items in it?
Think of it in terms of columns, so that you can drag an item from one column to another without having to drag to the "list" which is just a small rectangle (if you use padding). Its similar to trello

When I drag an item of a group's last one, that will be remove when the another group's move trigger. So, I can't cancel drop.

Why is using padding not a good solution? You can use it to control the size of the empty space. I would say that trello uses the same approach...

@karolchmist How would I make it so that the padding's size would change?

You mean while hovering on the target? Ok now I understand. I just leave a bit on empty space. Sorry, I don't have a ready solution to dynamically create it.

Use .sortable:empty + min-height

Tried a lot of things using react-sortable.  In the end decided to make my column label draggable, but disallow dragging into it: onMove: (e, oe) => e.related.tagName === 'SECTION' ? false : true and then disable ghost with user-drag: none;


grsi-config missing TFipps and SiLi fitting changes #880 repeat

I've removed made the change @VinzenzBildstein suggested and it now complies with root 5.
The revert #886 made getting it merged again really messed up, but I think I got everything.

Thanks for making the change, sorry for the complications due to the reverted pull request.


Close tab with middle click does not seem to work on MacOS (possible regression)

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: MacOS Sierra 10.12.6
Hyper.app version: 1.4.6
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/xeroxoid/7d97ee14893e6efb611492569fce97a8
The issue is reproducible in vanilla Hyper.app: Yes

Issue
As the title suggests, middle-clicking with a mouse on an open tab does not do anything.
Expected: close the tab as per https://github.com/zeit/hyper/pull/286 and https://github.com/zeit/hyper/issues/117

I can confirm this issue still exists even on 2.0.4 (pre-release)

Not working on Windows 10 too, hyper 2.0.0.

Any news on this? Deal breaker for me.

@gilad215 if this is a deal breaker for you, please help us to fix it 🙏

Chromium doesn't trigger the click event on middle click. Bound to mouseup instead, which matches the behavior of other editors including vscode, sublime text, and webstorm. PR submitted.

Any news on that PR? Still not working ATM


Remove dead assignment

I threw clang static analyzer at the code
float_increment is assigned again before it is used, making the initial assignment redundant.

Will add a travis.yml file in the very near future.


DndProvider fails with webpack persistant cache

Describe the bug
cache:  {
            type: 'filesystem',
        }

I used persistent cache (cache filesystem) with DndProvider a lot. But now got error in production build for my testing environment when using DndProvider on page while running browser test. Funny thing that i tried it on my cloud Linux dev machine and there is no problem. Now it happens only on my local machine.
Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props}). If you meant to render a collection of children, use an array instead.

if cache: false, then error do not exists. I do not get the reason why it worked for a while and now even on old commits it do not work. I fully cleaned all node_modules files and pnpm caches, i removed fully my project and pulled it from git from scratch - did not helped. Maybe its known problem?
Expected behavior
No error.

OS: macos 14.1.1
Browser Chrome
Version latest

I added manually cache folder and error fixed
{
                  type: 'filesystem',
                  // cacheDirectory: path.resolve(__dirname, '.temp_cache'),
},

But with default cache folder error happens. For me its now not clear why it happens.

Created issue on webpack page
https://github.com/webpack/webpack/issues/18648


Tests with sphinx 2.0 and python 3.7

We already put python3.7 as default in rtd.
And sphinx 2.0 is coming soon!

Sphinx 2.x drop compatibility with 2.7, so I put the tests apart :)

Weird, this passed here, but linter broke in master :man_shrugging:


Update plugin.legend.js with a new option: 'alignment'.

The position options for the legend only allow top, bottom, left, and right.  Then the legends are aligned in the center on the top and bottom and at the top in left and right.
This adds a new option to the legend: 'alignment' which allow the legend to be aligned within its layout box.
In the case of position top or bottom, the legend can be aligned 'left', 'right', or 'center', with center being the default.  For position right or left the legend can be aligned 'top', 'center', or 'bottom', with top being default as the current behavior.
Updated the legend help page to reflect these changes.
Similar: https://github.com/chartjs/Chart.js/issues/3706
See: http://jsfiddle.net/pdht9ces/10/

@Zmimmy Thanks!
Before reviewing, I would like to align the API with the one in this comment:

rename legend.alignment by legend.align
rename left, center, right by start, center, end
rename top, center, bottom by start, center, end

No need to implement stretch of course because it would be more complex.

We also need additional logic in https://github.com/chartjs/Chart.js/blob/d6ac7d8a80a80866d64845c99cbfaec66b377ddd/src/plugins/plugin.legend.js#L441 and https://github.com/chartjs/Chart.js/blob/d6ac7d8a80a80866d64845c99cbfaec66b377ddd/src/plugins/plugin.legend.js#L445 to reset x or y position based on the alignment configuration.

I'm assuming the following default row/column alignment, which needs to be considered in case of more than one row/column, but does this make sense?

position: 'top' or 'bottom'

align: 'start' -> Each row is aligned to the left
align: 'center' -> Each row is aligned to the center
align: 'end' -> Each row is aligned to the right

position: 'left' or 'right'

align: 'start' -> Each column is aligned to the top
align: 'center' -> Each column is aligned to the middle
align: 'end' -> Each column is aligned to the bottom

Thanks for all the feedback!  We just started using chartJS and I am not super familiar with the codebase yet so I appreciate all the insight.  I will start making those changes this afternoon.

I have made the changes and added test cases.

I'm assuming the following default row/column alignment, which needs to be considered in case of more than one row/column, but does this make sense?

position: 'top' or 'bottom'

align: 'start' -> Each row is aligned to the left
align: 'center' -> Each row is aligned to the center
align: 'end' -> Each row is aligned to the right

position: 'left' or 'right'

Yes, this makes sense and is now happening.

align: 'start' -> Each column is aligned to the top
align: 'center' -> Each column is aligned to the middle
align: 'end' -> Each column is aligned to the bottom

This also makes sense but is not currently happening exactly like this when there are multiple columns, all the columns default to the top of the legend container.

Any update on this? I'd really appreciate this feature.

@Zmimmy Thanks for your contribution! We decided to go with #6141 since the implementation is a bit simpler and consistent whatever the legend orientation.


Tune code style in tables

This is a follow up of #26595 and kubernetes-sigs/reference-docs#220.

Preview:
https://deploy-preview-27442--kubernetes-io-master-staging.netlify.app/docs/reference/config-api/kubelet-config.v1beta1/

Preview:
https://deploy-preview-27442--kubernetes-io-master-staging.netlify.app/docs/reference/config-api/kubelet-config.v1beta1/

The font of "field" is getting a little bigger and the background color is removed. it looks more clear.
/lgtm

/area web-development

/approve
We can look at accessibility in a follow-up.


added Dockerfile to project

I've added a Dockfile to the project.
Been using this for years for my websites, because I like to write the content on my iPad then push it to git from there.
I wasn't sure whether you want to proved this as an image yourself, but with the Dockerfile, anyone can do it on their own.
The provided config can easily be overriden, where needed.
Usage (after you have deployed it somewhere):
docker run --rm -v $(pwd)/content:/usr/src/app/content harbor.brendamour.net/brendamour/searchlink $files

Thanks!


[fix][broker] ManagedCursor: mark delete no callback when create meta-ledger fail

Fixes: #16711
Motivation
If the meta-ledger fails to be initialized when mark delete is executed, the callback of mark delete will not execute anymore. this case will occur in 1/1000 probability. You can reproduce it by doing this: "Run unit test ManagedCursorTest.markDeleteWithZKErrors 1000 times".
This problem also makes unit test ManagedCursorTest.markDeleteWithZKErrors flaky. #16711
When the problem occurs, the actual execution process is as follows:
Flow-1. The process we expect

Time
cursor mark deleted
meta thread

1
synchronized pendingMarkDeleteOps

2
check meta-ledger state

3
do create ledger

4
append to pending requests queue

4

synchronized pendingMarkDeleteOps( High light )

5

create ledger fail

6

loop pending requests, and fail callback

Flow-2. The process we did not expect. However, Thread cursor mark deleted and meta thread may be assigned to the same thread,  the actual maybe execution process is as follows:

Time
cursor mark deleted/meta thread

1
synchronized pendingMarkDeleteOps

2
check meta-ledger state

3
do create ledger

4
synchronized pendingMarkDeleteOps ( High light ) reentrant lock by the same thread, which we did not expect

5
create ledger fail

6
loop pending requests, and fail callback

7
append to pending requests queue

8
waiting callback...

9
waiting callback...

Each column means the individual threads.
Column Time is used only to indicate the order of each step, not the actual time.
The important steps are explained below:

step-4: If the ledger fails to be created, will trigger a "fail back" for the pending requests, and the requests that have not been queued will be ignored.
https://github.com/apache/pulsar/blob/c217b8f559292fd34c6a4fb4b30aab213720d962/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L2570-L2577
step-5 ( High light ): If the meta ledger needs to be created, create ledger will be triggered first and the current request will be put into the pending requests queue. It is possible that create ledger fail has been completed before the request is put into the queue, so this request will not get the callback anymore( see flow2 above ).
https://github.com/apache/pulsar/blob/c217b8f559292fd34c6a4fb4b30aab213720d962/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L1870-L1876
Modifications

Selected plain ( High light )
Makes put request into the pending queue executed before create ledger.

Rejected plan
Makes put request into the pending queue and create ledger execute serially. Why rejected this plan? Because plan-1 fewer changes.

Documentation
Check the box below or label this PR directly.
Need to update docs?

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

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

[ ] doc
(Your PR contains doc changes)

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

@315157973 @codelipenghui @rdhabalia Could you take a look.

step-5 ( High light ): If the meta ledger needs to be created, create ledger will be triggered first and the current request will be put into the pending requests queue. It is possible that step 4 has been completed before the request is put into the queue, so this request will not get the callback anymore.

We have synchronized (pendingMarkDeleteOps) for both create cursor failure and internalAsyncMarkDelete, if triggered the ledger creation means the left thread got the lock and the right thread can only get the lock after the mdEntry is added to the pendingMarkDeleteOps , no?

Hi @codelipenghui

We have synchronized (pendingMarkDeleteOps) for both create cursor failure and internalAsyncMarkDelete, if triggered the ledger creation means the left thread got the lock and the right thread can only get the lock after the mdEntry is added to the pendingMarkDeleteOps , no?

According to your tips, I found a new problem: see Flow-2 above. And I have modified the Motivation.
@codelipenghui @Technoboy- @mattisonchao  Could you review this PR again?

@keyboardbobo

and the cursor status has always been CreatingLedger

In ManagedCursorImpl, there has not any stat names creatingLedger, I think you perhaps say ManagedCursorImpl.SwitchingLedger? Otherwise, maybe you say ManagedLedgerImpl.CreatingLedger?

I also encountered a similar scenario here. The pendingMarkDeleteOps has accumulated tens of thousands of requests, and the cursor status has always been CreatingLedger, and the retention cannot be executed, resulting in the situation that the disk space cannot be reclaimed. I don't know if it's the same problem?

If you want to say ManagedCursorImpl.SwitchingLedger. I am afraid not. The stat of ManagedCursor will change like this(even if create ledger failure, it will not stay at SwitchingLedger):

NoLedger --> SwitchingLedger --> open ledger failure --> NoLedger --> SwitchingLedger .... loop

If you want to say ManagedLedgerImpl.CreatingLedger. Could you provide more information? It is best to submit an issue.

/pulsarbot rerun-failure-checks

@poorbarcode

/pulsarbot rerun-failure-checks

Hi @keyboardbobo

If you have any ideas, please remind me

Thank you for the information，I have open a issue #16859, We can discuss  there.

@poorbarcode


Inverted flame graph docs

Issue number of the reported bug or feature request: #
Describe your changes
A clear and concise description of the changes you have made.
Testing performed
Describe the testing you have performed to ensure that the bug has been addressed, or that the new feature works as planned.
Additional context
Add any other context about your contribution here.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (baf7f41) 91.96% compared to head (1441f20) 91.95%.

:exclamation: Current head 1441f20 differs from pull request most recent head b58dc34. Consider uploading reports for the commit b58dc34 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #442      +/-   ##
==========================================
- Coverage   91.96%   91.95%   -0.01%
==========================================
  Files          91       91
  Lines       10790    10790
  Branches     1485     1485
==========================================
- Hits         9923     9922       -1
- Misses        865      866       +1
  Partials        2        2

Flag
Coverage Δ

cpp
85.22% <ø> (-0.03%)
:arrow_down:

python_and_cython
95.40% <100.00%> (ø)

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

Files
Coverage Δ

src/memray/reporters/frame_tools.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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

Oh, and: rendered docs can be previewed at https://godlygeek.github.io/memray/flamegraph.html#inverted-flame-graphs

Congratulations and thanks @ivonastojanovic for the contributions!


Add IUtf8JsonSerializable implementation to Azure plugin serialization

Library name
N/A
Please describe the feature.
Add IUtf8JsonSerializable implementation to Azure plugin serialization files

Since IUtf8JsonSerializable is internal, and we have the public API in place, we don't need to add IUtf8JsonSerializable for Azure plugin.


Simulator build fix — (temporarily) revert "Merge pull request #20103 from lilyball/fix_kvo"

This reverts commit 7c514196fcef1e59673a46c6a452c38d9322cf34, reversing
changes made to 2d7c31b24c3f0dbc9707fa794cc968ca424f642d.
This patch will be reproposed with fixes.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge

cc @jrose-apple @shajrawi Can this be force-merged? Unrelated tests are failing.

The unrelated test has already been reverted. will force merge this one.


Problems with Forex Integration

Hi all,
I've been working on FX integration for the past week and I've had some issues with integrating the added modifications within QSTrader. I've already made the necessary changes within my position sizer to reflect the correct amount of units when opening an FX position.
e.x.
Equity = 100k USD
Pair = USDJPY
Price = 103.77
Position =  25% of Equity
Total = 2,594,250 Yen
Quantity = 25,000 Units or $25k USD
I've concluded that I need to make necessary adjustments when opening and closing of positions in order to reflect the correct changes to pnl. I believe I've figured out which necessary changes need to be made within portfolio.py, portfolio_handler.py, and position.py.
The changes I intend to make are:
If FX pair is USD based (e.x. USDJPY), pnl calculations need to be made in the currency of the trading account, which in this case is USD.
When a position is opened:

Modify self.cur_cash to reflect USD += or -= of cash

My code for self.cur_cash:
if "USD" in ticker[:3]:
    self.cur_cash -= (((quantity * price) / price) + commission)
else:
    self.cur_cash -= ((quantity * price) + commission)

When a position is closed:

Modify self.cur_cash to reflect USD += or -= of cash
Modify calculation for self.realised_pnl within transact_shares()

My code for self.realised_pnl for self.action == SLD:
if "USD" in self.ticker[:3]:
   self.realised_pnl += (quantity * (self.avg_price - price) / price) - commission
else:
   self.realised_pnl += quantity * (self.avg_price - price) - commission

No changes need to be made with _add_position() and _modify_position() as those variables are correct.
I've used PriceParser.display() to print the correct values... The math seems to check out, but for some reason, QSTrader fails to reflect the same output when I attempt to integrate.
Any help would be great. Cheers!

Solved. Will post solution after I write up documentation.


clarify that the type of "count(this)" is Long

and that it collapses the result set to one result

Note that this is for consistency with the section titled "Aggregate Functions in the SELECT Clause" of the JPA spec.


implement custom errors

The commit doesn't seem entirely correct. It looks like you squashed the last two commits on your fork.
That would be the first commit you made, which we merged to develop last time and then this new change.

What also now happens is the commit on this PR includes all the changes you already made and merged last time.
You might need to re-fork or reset your fork to the latest develop. Sleep API develop has received some commits since you last contributed so your fork is also out of date by a few commits.


proposal for resolution merge process

Resolution merging can be considered part of ARD, and is supported by the FORCE framework:
https://force-eo.readthedocs.io/en/latest/components/higher-level/l2i/index.html#l2i
The concrete implementation at VITO uses the FORCE approach to increase the resolution of Sentinel-2 20M to 10M.
I named it 'resolution_merge', because 'pansharpening' refers to the usage of a panchromatic band, which is not the case in the Sentinel-2 algorithm. Resolution merging also seems to be used in publications and by force, although sometimes you also see references to pansharpening in that context.
The usage with the Python client is shown here:
https://github.com/Open-EO/openeo-geopyspark-integrationtests/blob/master/tests/test_integration.py#L934
The core of the backend implementation is here:
https://github.com/Open-EO/openeo-geotrellis-extensions/blob/develop/openeo-geotrellis/src/main/scala/org/openeo/geotrellis/ard/Improphe.scala#L62

Closing as stale, we can re-open whenever this gets some attention again.


[PORT]  Deprecate Brand Level Classnames

Description
Once the design token theme aligned tailwind classnames have been created. The next step is to deprecate the brand level classnames in favor of the newly created theme level classnames.
Technical Details

Deprecate all brand level classNames

Acceptance Criteria

All instances of the brand level classnames have been deprecated
The portfolio builders have been notified via slack message

This has been completed and further work will be completed in this epic https://github.com/MetaMask/eslint-plugin-metamask-design-tokens/issues/1


rsync: link_stat "/Users/sreeram/Downloads/ez_flutter-Sagar/build/ios/Debug-iphonesimulator/App.framework" failed: No such file or directory (2)

Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
Running Xcode build...
Xcode build done.                                           13.0s
Failed to build iOS app
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
building file list ... rsync: link_stat "/Users/sreeram/Downloads/ez_flutter-Sagar/build/ios/Debug-iphonesimulator/App.framework" failed: No such file or directory (2)
done
sent 29 bytes  received 20 bytes  98.00 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files could not be transferred (code 23) at /System/Volumes/Data/SWE/macOS/BuildRoots/2288acc43c/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/main.c(996) [sender=2.6.9]
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'FMDB' from project 'Pods')
warning: The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for the "Runner" target. (in target 'Runner' from project 'Runner')
warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'Flutter' from project 'Pods')

Could not build the application for the simulator.
Error launching application on iPhone 12 Pro Max.

doctor --verbose
[✓] Flutter (Channel stable, 2.2.1, on macOS 11.3.1 20E241 darwin-x64, locale en-US)
• Flutter version 2.2.1 at /Users/sreeram/Desktop/Application/flutter
• Framework revision 02c026b03c (5 days ago), 2021-05-27 12:24:44 -0700
• Engine revision 0fdb562ac8
• Dart version 2.13.1
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/sreeram/Library/Android/sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.55.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.22.0
[✓] Connected device (2 available)
• iPhone 12 Pro Max (mobile) • E9EC1A99-8A10-4328-8185-E88E6B258D28 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
• Chrome (web)               • chrome                               • web-javascript • Google Chrome 91.0.4472.77
! Error: Sreeramulu's iPhone is not connected. Xcode will continue when Sreeramulu's iPhone is connected. (code -13)
• No issues found!
Process finished with exit code 0

@PrasadPanyam
Can you provide complete flutter run --verbose log ? It will be large, so you can put that in a file and attach it here.
Also, provide ios/Runner.xcodeproj/project.pbxproj.

flutter run --verbose
flutter run –verbose.docx

@PrasadPanyam
The log you provided may not reflect the error you mentioned in original comment. In the above log, it failed because of below:
[ +138 ms] No supported devices connected.
[ +105 ms] The following devices were found, but are not supported by this project:
                    Chrome (web) • chrome • web-javascript • Google Chrome 91.0.4472.77
                    If you would like your app to run on web, consider running `flutter create .` to generate projects for these platforms.

Is this your current error due to which you aren't able to run ?
Else, attach a physical device or simulator and run the verbose command that'll show your original error you mentioned.

@darshankawar
Thanks for your response, but I didn't run this application on the web. I am using an ios simulator.

Yes, but the verbose log doesn't show iphonesimulator/App.framework" failed: No such file or directory (2) entry which you posted earlier.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Crash on next query after max query returns "No Information Found".

Nickolai reported an error with a script where he loops over materials doing a "Max" query. The first material doesn't have the variable so it returns "No Information Found". The next query on a material that does have the variable crashes the viewer.
Here is a script that reproduces the crash.
mili_file = 'ingrido.dyna.plt.mili'

OpenDatabase("localhost:" + mili_file, 0)

AddPlot("Pseudocolor", "Primal/brick/eps", 1, 0)
DrawPlots()

mats = ['1', '2', '3']

for mat in mats:
    print("Trying mat {}".format(mat))
    TurnMaterialsOff()
    TurnMaterialsOn(mat)

    SetQueryFloatFormat("%g")
    Query("Max", use_actual_data=1)
    max_value = GetQueryOutputValue()
    print(max_value)
    output_string = GetQueryOutputString()
    print(output_string)

Here is the output.
visit -cli -s vis_eps_issue.py
Running: cli3.3.3 -s vis_eps_issue.py
Running: viewer3.3.3 -noint -host <IP_ADDRESS> -port 5600
Running: mdserver3.3.3 -host <IP_ADDRESS> -port 5600
Running: engine_ser3.3.3 -dir /usr/gapps/visit -idle-timeout 480 -host <IP_ADDRESS> -port 5600
Trying mat 1
VisIt: Warning - The Pseudocolor plot of variable "Primal/brick/eps" yielded no data.
()

No Information Found

Trying mat 2
VisIt: Warning - The Pseudocolor plot of variable "Primal/brick/eps" yielded no data.
Traceback (most recent call last):
  File "vis_eps_issue.py", line 16, in <module>
    Query("Max", use_actual_data=1)
visit.VisItException: VisIt's viewer is not running!
>>>

I believe the warning message is from turning off all the materials before turning on the desired one. I guess an update happens every time materials are turned on or off in the CLI.

I found if I add a value to the output in avtMinMaxQuery::CreateMessage the crash goes away. I suspect that the lack of a value results in corrupted data being sent to the viewer, which causes it to crash the next time a query is executed.
void
avtMinMaxQuery::CreateMessage(const int nMsg, const MinMaxInfo &info1,
                              const MinMaxInfo &info2, string &msg,
                              doubleVector &vals)
{
    if (nMsg == 0)
    {
        vals.push_back(0.);
        return;
    }

Perhaps it is GetQueryOutputValue and/or GetQueryOutputString that need to verify if there is anything in 'vals'.

I put a check in to handle it in visit_GetQueryOutputValue and it still crashed. I think catching it there is already too late since it is crashing the viewer and not the cli. Here are my code mods:
STATIC PyObject *
visit_GetQueryOutputValue(PyObject *self, PyObject *args)
{
    ENSURE_VIEWER_EXISTS();

    QueryAttributes *qa = GetViewerState()->GetQueryAttributes();
    doubleVector vals = qa->GetResultsValue();
    PyObject *retval;
    cerr << "visit_GetQueryOutputValue vals.size()=" << vals.size() << endl;
    if (vals.size() == 0)
        retval = PyFloat_FromDouble(0.);
    else if (vals.size() == 1)
        retval = PyFloat_FromDouble(vals[0]);
    else
    {

Here is the stack trace from the viewer crash.
Thread 1 "viewer" received signal SIGSEGV, Segmentation fault.
0x000015554b303e54 in QueryAttributes::SetResultsValue(double) ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libvisitcommon.so
(gdb) pwd
Working directory /g/g17/brugger.
(gdb) where
#0  0x000015554b303e54 in QueryAttributes::SetResultsValue(double) ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libvisitcommon.so
#1  0x0000155554d56e4b in ViewerQueryManager::Query(MapNode const&) ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libviewercore_ser.so
#2  0x0000155554d047f6 in ViewerActionManager::HandleAction(ViewerRPC const&)
    ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libviewercore_ser.so
#3  0x00001555550c723e in ViewerSubject::HandleViewerRPCEx() ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libviewer.so
#4  0x00001555550c7426 in ViewerSubject::HandleViewerRPC() ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libviewer.so
#5  0x0000155546fbe018 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/workspace/visit/visit/thirdparty_shared/3.3.0/toss4/qt/5.10.1/linux-x86_64_gcc-10.3/lib/libQt5Core.so.5
#6  0x000015554b33bb99 in Subject::Notify() ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libvisitcommon.so
#7  0x000015554b22272d in AttributeSubject::Notify() ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libvisitcommon.so
#8  0x000015554b36fe0e in Xfer::Process() ()
   from /usr/workspace/brugger/visit_dev_git/visit/build/lib/libvisitcommon.so
#9  0x00001555550c78a3 in ViewerSubject::ProcessFromParent() ()

I added some debugging code to the QueryAttributes::SetResultsValue(double). Here is the debugging code.
void
QueryAttributes::SetResultsValue(const double val)
{
    cerr << "QueryAttributes::SetResultsValue val=" << val << ",resultsValue.size()=" << resultsValue.size() << endl;
    resultsValue[0] = val;
}

Here is the output.
/usr/workspace/brugger/visit_dev_git/visit/build/bin/visit
Running: gui -dv
Running: viewer -dv -geometry 1560x1014+360+28 -borders 26,4,4,4 -shift 0,0 -preshift 4,26 -defer -host <IP_ADDRESS> -port 5600
Running: mdserver -dv -host <IP_ADDRESS> -port 5601
Running: engine_ser -dv -host <IP_ADDRESS> -port 5600
QueryAttributes::SetResultsValue val=0,resultsValue.size()=1
QueryAttributes::SetResultsValue val=0,resultsValue.size()=1
QueryAttributes::SetResultsValue
QueryAttributes::SetResultsValue adding a value
QueryAttributes::SetResultsValue val=0,resultsValue.size()=0

Loguru caught a signal: SIGSEGV
VisIt's viewer exited abnormally! Aborting the Graphical User Interface. VisIt's developers may be reached via our GitHub discussions, https://github.com/visit-dav/visit/discussions

Clearly, the length is 0, even though I thought I was ensuring it was at least of length 1 everywhere.

Ok, my fix was bad. When I correctly modified the QueryAttributes so that the length of the array was always at least 1, the crash went away.

I think I will change QueryAttributes to no longer require an array length of a minimum of 1 and then have the Python function GetQueryOutputValue return an appropriate value if there is no value.
Here is the code for GetQueryOutputValue. @biagas What should go in the comment with "What goes here?"
STATIC PyObject *
visit_GetQueryOutputValue(PyObject *self, PyObject *args)
{
    ENSURE_VIEWER_EXISTS();

    QueryAttributes *qa = GetViewerState()->GetQueryAttributes();
    doubleVector vals = qa->GetResultsValue();
    PyObject *retval;
    if (vals.size() == 0)
        // What goes here?
        retval = ???;
    else if (vals.size() == 1)
        retval = PyFloat_FromDouble(vals[0]);
    else
    {
        PyObject *tuple = PyTuple_New(vals.size());
        for(size_t j = 0; j < vals.size(); ++j)
        {
            PyObject *item = PyFloat_FromDouble(vals[j]);
            if(item == NULL)
                continue;
            PyTuple_SET_ITEM(tuple, j, item);
        }
        retval = tuple;
    }
    return retval;
}

Not really sure. If there is no value to report it seems strange to supply anything that might be considered valid, so INF? or NAN?
How about a python error condition, or PyNone?
Not sure how any of these would affect user scripts.

Not sure either. It seems like a python error or PyNone would make the most sense. I assume a python error would break scripts, since I assume the script would exit if it wasn't catching exceptions. PyNone could also cause failures if a numeric value was expected.
Do any python experts have thoughts on this? @cyrush

I vote for PyNone. I think that makes the most sense. Before my changes in PR #5750, PyNone was being used in some cases as a proxy for an error condition. However, that behavior is long gone and, in fact, there is no code currently in VisIt's external python modules that has any reference to PyNone.

Ok, yeah, no code that ref's PyNone but a lot of code that refs Py_None....so, hold on a min...I am misremembering something about this.

Ok, Py_None is used as the return value for many Python methods that are involved with writing to an object. I don't see it being used anywhere to indicate error when returning a value from an object. So, at least the part of my remark about about Py_None not being used to indicate error anywhere in return values from VisIt, I believe is correct.
So, again, I vote for Py_None being set as the value. There is nothing returned in the case @brugger1 describes.

Py_None it is!


implement single_line_let_else_max_width

This is a follow up PR to #5690
This allows users to configure the maximum length of a single line let-else statements. let-else statements that otherwise meet the requirements to be formatted on a single line (as described by the style guide) will have their divergent else block formatted over multiple lines if they exceed this length.

Thanks for getting this up so quickly! We're only going to get this one shot at it, so will need to make sure this is both complete/perfect (as much as it can be) and stable which is a bit of an usual path for a net-new config opt.
Will try to review later tonight after work

also @fee1-dead if you have the bandwidth an are interested in giving this a review your perspective would be greatly appreciated

@calebcartwright let me know if these additional test cases are good. I'm happy to add any others you think are necessary for the new option.

I wouldn't be opposed to merging this as-is, and tackling any potential changes needed to address the above scenario in a separate PR.
My only slight reservation is that it may create some ambiguity for folks subscribed to the tracking issue (i.e. this PR and the associated issue are the last pending "big steps" articulated there), though I guess the same would be true for the blog post.
Lmk what you think; I'm probably leaning towards merging but not a strongly held position

updating the PR now

updating the PR now

in that case I guess we'll park this until there's direction one way or another from t-style :smile:
I think there's enough here to justify having separate commits, though I also think the current 10 could probably be condensed into a smaller number. That's not strictly necessary, but wanted to share my observation in case you concur and would be interested in adjusting the commit history

Yeah, there's definitely room to reduce the number of commits. I'm happy to rebase! I just figured it was easier to have individual commits while working on this.
If we get word from t-style I can always remove the last commit. I'll hold off on making changes until it's clear how to move forward, though I guess we have discretion to make this change without an amendment to the guide, since this is the implied formatting from the style guide, correct?

though I guess we have discretion to make this change without an amendment to the guide, since this is the implied formatting from the style guide, correct?

Eh, I suspect this is something the Style team needs to explicitly respond to one way or the other, even if the position is "we defer to tools to interpret", though I suspect that's the least likely outcome

though I guess we have discretion to make this change without an amendment to the guide, since this is the implied formatting from the style guide, correct?

Eh, I suspect this is something the Style team needs to explicitly respond to one way or the other, even if the position is "we defer to tools to interpret", though I suspect that's the least likely outcome

Seems wrapping is the expected behavior, and I anticipate an update to the rules to make this more explicit. As such I'm probably going to merge this later tonight, and move the blog post out of draft.

alright, I'll try to get the rebase in soon, just have a few more things I need to do for work

alright, I'll try to get the rebase in soon, just have a few more things I need to do for work

sorry I forgot about modifying the commit history. no rush, whenever you're ready.
i just wanted to share that we had an answer on the expected behavior from the style team

@calebcartwright I think we'er good to go now. I've broken this up into 3 commits. The first fully implements single_line_let_else_max_width, while the other 2 make tweaks to the let-else formatting code.
Of those 2 extra commits the first inverts some existing logic, but doesn't change any formatting behavior, and the second implements wrapping the else when the pattern is too long.


Add ability to 'dump' full layout as a json object

Really useful for debugging purposes.
Can be used for snapshot testing.

From our discussion with @cztomsik
We probably want to move text measuring to rust. In order to do that safely we need some sort of unittesting. So we can be confident switching + it would probably give a better migration scoping as well.
Example (don't attach to the shape/syntax ):
const layout = {
  view: {
    color: 'red',
    border: [1, 2, 2, 1 /* + other props*/],
    layout: { x: 50, y: 10, w: 100, h: 100 },
    children: [
      {
        text: {
          parts: [
            ['fist part', { x: 50, y: 20, w: 100, h: 10 }],
            ['second part', { x: 50, y: 40, w: 100, h: 10 }]
          ]
        }
      }
    ]
  }
}

Also we can probably just use jest snapshots to get auto diffing

related to #77

later :)


Ignore Flaky test FlowTriggerServiceTest & slow tests

Temporary fix for https://github.com/azkaban/azkaban/issues/1981
Those slow tests took 5 & 6 seconds. There shouldn't be any sleeping in unit tests..

@chengren311 @jamiesjc could this be merged, please? Almost all PR merge builds are failing and it makes it quite slow to check if a PR is legit.

When making PRs it's a bit counterproductive that the "codecov/project" check is almost always failed. Do you think it could be disabled, or then set some higher threshold for that check? For example a limit of 0.5% would allow this PRs check to pass.

I think it makes sense to set some higher threshold for codecov.
cc @kunkun-tang

Pull Request Test Coverage Report for Build 4114

0 of 0   changed or added relevant lines in 0 files are covered.
80 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.3%) to 35.889%

Files with Coverage Reduction
New Missed Lines
%

azkaban-web-server/src/main/java/azkaban/flowtrigger/DependencyInstance.java
2
92.31%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
2
76.67%

azkaban-web-server/src/main/java/azkaban/flowtrigger/FlowTriggerExecutionCleaner.java
3
80.0%

azkaban-web-server/src/main/java/azkaban/flowtrigger/TriggerInstanceProcessor.java
3
89.71%

azkaban-exec-server/src/main/java/azkaban/execapp/event/JobCallbackRequestMaker.java
21
56.25%

azkaban-web-server/src/main/java/azkaban/flowtrigger/FlowTriggerService.java
49
60.47%

Totals

Change from base Build 4109:
-0.3%

Covered Lines:
10472

Relevant Lines:
29179

💛  - Coveralls


Minor fixes

round bridge values to one decimal
added total score to radar chart
change default pill volume to 1
sum density for concentration blends

closes #101 #103  #104 #105


Disable traversal by default

Update https://github.com/googlefonts/use-skrifa after.

Traversal is in a weird spot; it was really a sort of proof-of-concept I wanted to play around with, and then ended up using it to implement Debug. It is also the basis of the otexplorer tool, which was useful for me when I was initially implementing tables, but is maybe less useful longterm?
Basically we should decide if this is worth it, and then either rip it out or rework it such that it works consistently.
Ignoring that, then the question of having it on by default, I would reframe this as, "do we want Debug impls for read types, by default?"

Thinking "aloud," if we didn't have traverse I wouldn't implement it just to get Debug. Perhaps that points to ripping it out?

Yea, so part of my thinking with traversal is that it would give us a common mechanism that could then be easily reused for Debug, PartialEq, Hash, etc; otherwise we would need to generate a bunch of code for each of these.
(The reason these traits are annoying is that we want to actually follow offsets to subtables, instead of just printing out the offset value, which is what a naive derive(Debug) would do)

I think ot-explorer has the potential to be a very useful tool. We should consider removing the traversal feature from read-fonts, adding simple debug derives, and teaching codegen to emit the traversal code in a new crate (maybe ot-explorer as lib?)

I both agree with ^ and feel that we have bigger fish to fry. WDYT about removing traversal, adding simple debugs, and moving on to higher priority tasks?

Let me see what that looks like and we can go from there.


No object named "swift4" exists

When I try to update the Carthage I have this error:
*** Fetching SwinjectStoryboard Failed to check out repository into /Users/user/Library/Caches/org.carthage.CarthageKit/dependencies/SwinjectStoryboard: No object named "swift4" exists (Error Domain=CarthageKit.CarthageError Code=22 "(null)")

Found an issue. Gays you forgot to create a new one release after you merge the branch "Swift4" to "master"

I'll make a release soon. Please specify an SHA to install Swinject by Carthage👍

Should be fixed now by latest release (2.0.0-beta.1)


add_wind_and_stack_open_area measure is broken as of E+ 9.6

Reported at https://unmethours.com/question/76215/error-when-using-add-wind-and-stack-open-area-measure/
Since this measure is an EnergyPlus measure, it references surface properties by index. As of EnergyPlus v9.6, surfaces have a new Space property, so many of the referenced indices are off by 1. For example, this needs to reference property 5, not 4. And all of the coordinates (here, here, etc.) need to be incremented by 1. Other changes may be needed, I haven't fully audited the measure.

Fixed with https://github.com/BuildingPerformanceSimulation/openstudio-measures/commit/c13b332bea890d61799032f3fec2c70e82b7e717


command not found

after installation the project like document in ubuntu i get this error when i want to run:
camover: command not found

You might want to check if PATH is set.


[Analysis Engine] Export new domain to graph db

Changes
Added export to data-service for domains.
Requirements
Requires: N/A
PR Dependencies
Depends on: #30
Merged Branches and Other Dependencies
Merged branch(es): N/A
Other dependencies: N/A
Testing

[ ] Manual
[x] Automated

List of added tests:

Export test for domains

This PR depends on a specific branch on data-service. Not quite sure if I should swap the branch reference in the Github Actions config.

This PR depends on a specific branch on data-service. Not quite sure if I should swap the branch reference in the Github Actions config.

@Mapleia toggle it for now, then we'll switch it back master before this gets merged.

@rlnsy / @Mapleia what is the bug here? What action is needed to finish / merge this PR?

We have put data-services on hold for now to increase our development speed. We will use BigQuery for data export and analysis instead.

Obsolete


[HIL] X-Plane, QGC, and Pixhawk Are Connected but No Radio Control

Hi everyone,
I'm trying to run HIL using X-Plane 10, QGC, and the Pixhawk. I followed the instructions on the dev guide and everything seems to be connected, except nothing happens when I move the radio sticks. The system arms and I get a solid green light on the Pixhawk but I can't control it in Manual mode. Here is a screenshot of my setup.

Here are the net connections:

Please help,
Marc

Just an update, I replaced QGC stable with the latest build. I cannot also not load the one-waypoint mission suggested by the dev guide without getting the error "MAV_MISSION_ERROR".

Okay, I had to change the HIL port on QGC to be 49000 as opposed to 49005 but now radio control is inverted on X-Plane. I believe this may be an X-Plane configuration and should work after this.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


AMBARI-24383. A NPE occurs if a Kerberos identity descriptor is missi…

clone of #1929

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3401/
Test PASSed.


Automatically closing brackets not supported

Microsoft/vscode-python#1772
Don said this was something that required language server support.

This is actually not about auto-closing brackets. Auto-close is when user types (, editor adds ). This is VS Code internal thing, we do not control it - same for quotes. #1772 is about auto-inserting () on completion of function names. I.e. print completes to print() with caret inside (|).

Dupe of #35


Translation README

I want to help translate the README and the others files into Spanish. :earth_americas:

I can help with that.

Can I help with this?


Automatically monitor cluster hosts for disk space

As a sysadmin, I need to know when a host fills up so I can replace it.

Currently, this happens via the same bash script as every other server. In the future we'll have an autoscaling system


Failure to provide inference for Arrayed Objects

See the code here
https://github.com/codyduong/ytmusicapiJS/blob/c4f9a51ee0e2ad872fe823861b1c6126ddab40ed/src/mixins/watch.ts#L153-L159
The inference type blows up. Discover why.

Because of this line here https://github.com/codyduong/ytmusicapiJS/blob/c4f9a51ee0e2ad872fe823861b1c6126ddab40ed/src/mixins/watch.types.ts#L17


[wip] pro-typing poller very early draft

Associating PR with tracking issues:
Fixes #5805, Fixes #5809, Fixes #5923


Split zodiac-core, add zodiac-tsrp

Second PR for #63, after #64. Doing this as a prelude to adding protocol-specific identifiers to keys and key IDs (#62).
No zodiac-tarp package yet, implementation can happen after the spec is done.
@erikd-ambiata @thumphries

🍯


(#2020) Bump to Spark 3.5.1

🛑 Important:
Please open an issue to discuss significant work before you start. We appreciate your contributions and don't want your efforts to go to waste!
For guidelines on how to contribute, please review the CONTRIBUTING.md document.
Purpose of this PR
Resolves #2020 by updating the default Spark version.
Proposed changes:

Bumps the default Spark version to 3.5.1

Change Category
Indicate the type of change by marking the applicable boxes:

[X] Bugfix (non-breaking change which fixes an issue)
[X] Feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that could affect existing functionality)
[X] Documentation update

Rationale

Integrates bug fixes and IA fixes from upstream Spark
Checklist
Before submitting your PR, please review the following:

[X] I have conducted a self-review of my own code.
[X] I have updated documentation accordingly.
[X] I have added tests that prove my changes are effective or that my feature works.
[X] Existing unit tests pass locally with my changes.

Additional Notes

@andreyvelich @yuchaoran2011 Could you please review this PR? 🚀 The version bump includes several security and bug fixes.

Bumped to Spark 3.5.2 in https://github.com/kubeflow/spark-operator/pull/2154


fix(relate-tags): send with trackRelatedTags instead

fix with the function call, from previous problem was a meta function not calling
and, avoid the confusing onClick meta function naming

replaced by #2696


Scheduled message

Hi,
I've gone through the readme and the tutorial found here but I still can't figure out how to make my bot send a scheduled message at a specific time every day. Is there a tutorial out there for this? Sorry if this has been asked for or if I'm missing something obvious. Thanks!

No such tutorial AFAIK.
I do lots of periodic stuff like this and we use https://github.com/socketry/timers. I haven't seen functionality that lets you just do something at a specific time, but you can probably implement something on top of that or contribute to timers.
I'll close this since this is not a bot library question, but feel free to ask more questions here.

Thank you for your response! I've had experience with the whenever gem and I think I can use it but can you take a look at it and see if I can actually use it? I just want to post a message every day, so something like this in the schedule.rb file:
every 1.day, at: '12:00am' do
  # I'm not sure what to put here, but tell the bot to post a message
end

Looks reasonable. Inside of that you can try MyBot.instance.client.call_a_slack_api.

Ah I see. Thank you for your help! I think I have an idea of where to go next and I shall give it a try!


Question: How do I use uploadthing with Clerk (clashing middleware)?

Hey 👋
I'm using Next.js with pages. Project built with create-t3-app v7.13.1.
I'm trying to use Clerk with uploadthing and inside the uploadthing middleware function I want to check the user is logged in an associate the data with the user via an id.
uploadthing.ts:
/** server/uploadthing.ts */
import type { NextApiRequest, NextApiResponse } from "next";
import { createUploadthing, type FileRouter } from "uploadthing/next-legacy";

import { getAuth } from "@clerk/nextjs/server";

const f = createUploadthing();

const auth = async (req: NextApiRequest, res: NextApiResponse) => ({
  id: getAuth(req).userId,
});

// FileRouter for your app, can contain multiple FileRoutes
export const ourFileRouter = {
  // Define as many FileRoutes as you like, each with a unique routeSlug
  textUploader: f({ text: { maxFileSize: "2MB", maxFileCount: 10 } })
    // Set permissions and file types for this FileRoute
    .middleware(async (req, res) => {
      // This code runs on your server before upload
      const user = await auth(req, res);

      // If you throw, the user will not be able to upload
      if (!user) throw new Error("Unauthorized");

      // Whatever is returned here is accessible in onUploadComplete as `metadata`
      return { userId: user.id };
    })
    .onUploadComplete(async ({ metadata, file }) => {
      // This code RUNS ON YOUR SERVER after upload
      // console.log("Upload complete for userId:", metadata.userId);

      console.log("file url", file.url);
    }),
} satisfies FileRouter;

export type OurFileRouter = typeof ourFileRouter;

middleware.ts:
import { authMiddleware } from "@clerk/nextjs";

export default authMiddleware({
  publicRoutes: ["/", "/api/uploadthing"],
});

export const config = {
  matcher: ["/((?!.*\\..*|_next).*)", "/", "/(api|trpc)(.*)"],
};

When I run this code I get errors
Frontend alert / error says "ERROR! Failed to get presigned URLs"
I've double checked my .env and API keys mentioned in another issue.
Terminal error:
[UT] UploadThing dev server is now running!
[UT] middleware failed to run
Error: You need to use "authMiddleware" (or the deprecated "withClerkMiddleware") in your Next.js middleware file. You also need to make sure that your middleware matcher is configured correctly and matches this route or page. See https://clerk.com/docs/quickstarts/get-started-with-nextjs

If I remove the Uploadthing middleware block, the upload works, but then I can't tag it / confirm the users Id.
I hope this is the right place to post / hope I can help others because this seems like a pretty common setup to run Clerk + uploadthings...
Feel free to ask for more details / info...
I've been racking my head with this one, any help would be appreciated!

You middleware isn't making all of uploadThings API public, only the base route. Use something like this for your public routes
  publicRoutes: ['/sign-up(.*)', '/sign-in(.*)', '/api(.*)'],
Regardless, for questions there is a uploadThing discord where we can help with questions and help debug. The invite is on the ut docs.

I tried altering the public routes as suggested but still get the error:
Error: You need to use "authMiddleware" (or the deprecated "withClerkMiddleware") in your Next.js middleware file.

and its dependant on making the getAuth(req) which I now try, catch and the upload goes through, but I'm no closer to adding the metadata.
I do wonder how new the authMiddleware is and if its a potential issue or Next version mismatch.
I whipped up a quick project using app dir and the middleware worked fine, accessing the userId metadata but feels a tad to experimental to jump to 😱 with tRPC in the mix.

Interesting. I'll try and dig into it, but I would be surprised if this is an issue with ut itself. I am currently working on a project using trpc, app dir, clerk and ut, with all of them are functioning fine.

I'd really appreciate that – I've opened up a question in the Clerk discord, will report back if I find anything!
In the meanwhile I'll use the frontend onClientUploadComplete to handle my docs.

Just following up on this, made a demo repo to show folks over on the Clerk forum – will post here and keep this up to date as I work to solve the issue:
https://github.com/matthewspear/uploadthing-clerk-app

Following up on this, found a solution and posted: https://github.com/matthewspear/uploadthing-clerk-app
TLDR:

Run getAuth in the API before calling the handler
Pass in any data you want into the body of the request of the handler
Access data from the middleware request body


Change in subdirectory does not trigger upload of built asset during theme watch

This is an issue with Themekit v1.0.0, reverting to v0.8.1 fixes this issue. My guess is the issue was introduced in https://github.com/Shopify/themekit/pull/601.
I run my build process with Gulp. It takes the entry file at /src/app.scss and generates /assets/app.css, which is used in my theme.liquid template.
Directory structure:
- assets
  - app.css
- src
  - app.scss (build entry file)
  - components
    - helloWorld.scss (referenced by /src/app.scss)

When running theme watch I get the following behaviour:

:white_check_mark: a direct change to /assets/app.css successfully uploads /assets/app.css.
:white_check_mark: a change to the build entry file /src/app.scss triggers a build and successfully uploads /assets/app.css.
:x: a change to /src/components/helloWorld.scss does trigger a build, updating /assets/app.css as expected, but /assets/app.css is not uploaded.

If I make a change to /src/components/helloWorld.scss and then theme deploy assets/app.css it does successfully upload the change, as expected.
Update: To clarify I have gulp watch running in a second terminal window which watches the /src directory for changes, and triggers a /assets/app.css build when a change is received.

This is a deuplicate of https://github.com/Shopify/themekit/issues/607 and an issue with Gulp and not themekit. Please see this comment specifically on how to workaround this.


WIKI: FAQ - SSL Certificate Instruction Typo

FAQ\Question 8 - How can I use my own SSL Certificate?
Solution #2 It States:

CERTIFICATE=/secrets/ssl/MY_SSL_CERT.key

Should READ:
CERTIFICATE_KEY=/secrets/ssl/MY_SSL_CERT.key

Thank you. It is fixed


Create a notebook to demonstrate accessing the expanded extents  data

we can make a demonstration notebook for the expanded extents data and how to handle it

I reckon this could even just be a small extra bit at the end of the existing Landsat and Sentinel-2 ARD notebooks - my understanding is that the data should be generally usable in the same way as before, but there might be some extra caveats and important things to keep in mind (have been planning to ask @uchchwhash to organise a presentation on the Expanded Extents project outcomes so we can all understand those caveats/limitations/changes better).


walletDriverName is not well documented

Expected or acceptable values for the parameter walletDriverName is not documented, so the user is prone to receiving unknown driver name error.
Documentation should be changed to indicate the suggested values (e.g. sqlite).

This documentation is autogenerated and is due to a lack of documentation on the Algorand REST APIs.
Adding it in manually should solve the problem by default, but anytime the kmd client is regenerated, the apis will need to be regenerated.


fix(all): Increase min Flutter version to fix dartPluginClass registration

Description
Fixes the issue where the dart_plugin_registrant.dart file is not generated correctly.
Tested this locally with packages referenced by path. When I increased the Flutter SDK version to 2.11 then the issue we saw in #1270 was gone.
Related Issues

Fix: https://github.com/fluttercommunity/plus_plugins/issues/1270
Related: https://github.com/flutter/flutter/pull/96610
Related: https://github.com/flutter/flutter/issues/113720
Related: https://github.com/fluttercommunity/plus_plugins/issues/1274

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

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

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Since we are at it, I have also upgraded the platform interfaces (although not required for this fix) and removed some of the SDK requirements from the examples, as they are not required.

Why do we need the platform_interface packages if there is only one package for everything?

Why do we need the platform_interface packages if we only need one package for every platform?

It has been a long discussion in the maintainers team, and the conclusion is that having a package interface as an external package allows for expandability. I'd personally get rid of it but not everyone agreed.


Assignment to attribute changes id() but not referenced object

The example below is simplified from a larger package in which a line like assert a.common is b.common is used as a consistency check. I want to ensure that multiple instances of Foo share references to the same instance of a common object.
When migrating that package from traitlets to pydantic, the assertion began to fail.
As the example shows, id(…) gives different values for the original object, and the references to it in two instances of Foo; but the same value for attributes of the common object itself. I feel this is counterintuitive.
Maybe related to #154.

OS: Ubuntu 19.04
Python version: 3.7.3 (default, Apr  3 2019, 05:39:12) [GCC 8.3.0]
Pydantic version: 0.25

from pydantic import BaseModel

class Common(BaseModel):
    # …attributes…
    x: int = 3
    pass

class Foo(BaseModel):
    common: Common

    def common_id(self):
        return id(self.common), id(self.common.x)

    def get_x(self):
        return self.common.x

c = Common()
a = Foo(common=c)
b = Foo(common=c)

# Objects appear to be different:
print((id(c), id(c.x)), a.common_id(), b.common_id(), sep='\n')
#<PHONE_NUMBER>91728, 9079072)
#<PHONE_NUMBER>91872, 9079072)
#<PHONE_NUMBER>92016, 9079072)

print(a.common is b.common)
# False

# …but are in fact linked:
c.x = 5
print(c.x, a.get_x(), b.get_x())
# 5 5 5

print(a.common.x is b.common.x)
# True

For now, I've worked around this by subclassing BaseModel and overloading validate() to replace value.copy() with simply value in the code below:
https://github.com/samuelcolvin/pydantic/blob/fe72ba13f469377057112d2f301f52cd3b206467/pydantic/main.py#L426-L434

I'm afraid this is a perfect example of how hard it is to please everyone ... #154.
I don't really see a way around this, I think not share items between model instances is probably right.

I expected also that its possible to share instances. I have a bigger model (~20 classes) with many references between and it is shared with the outer world via JSON. Would be awesome if pydantic could support something like object identities in some way. So also serialization does take care on that. E.g. $ref could be used for the serialization of instances already integrated in the JSON string.
class Person(BaseModel):
    id: int
    name = 'Jane Doe'

class Car(BaseModel):
    id: int
    owner: Person
    driver: Person

def test_pydantic():
    hannah = Person(id=11)
    hannah.name = "Hannah"
    test = Car(id=55, owner=hannah, driver=hannah)
    hannah.name = "?" # currently no effect because copied at constructor
    print(f"Driver: {id(test.driver)} Owner: {id(test.owner)}") # currently different ids because copied at constructor
    json_string = test.json()
    print(f"JSON: {json_string}")
    # JSON {"id": 55, "owner": {"id": 11, "name": "Hannah"}, "driver": {"id": 11, "name": "Hannah"}}
    car_reinstanced = Car.parse_raw(json_string)
    print(f"Driver: {id(car_reinstanced.driver)} Owner: {id(car_reinstanced.owner)}") # expected to be same

I expected also that its possible to share instances. I have a bigger model (~20 classes) with many references between and it is shared with the outer world via JSON. Would be awesome if pydantic could support something like object identities in some way. So also serialization does take care on that. E.g. $ref could be used for the serialization of instances already integrated in the JSON string.
class Person(BaseModel):
    id: int
    name = 'Jane Doe'

class Car(BaseModel):
    id: int
    owner: Person
    driver: Person

def test_pydantic():
    hannah = Person(id=11)
    hannah.name = "Hannah"
    test = Car(id=55, owner=hannah, driver=hannah)
    hannah.name = "?" # currently no effect because copied at constructor
    print(f"Driver: {id(test.driver)} Owner: {id(test.owner)}") # currently different ids because copied at constructor
    json_string = test.json()
    print(f"JSON: {json_string}")
    # JSON {"id": 55, "owner": {"id": 11, "name": "Hannah"}, "driver": {"id": 11, "name": "Hannah"}}
    car_reinstanced = Car.parse_raw(json_string)
    print(f"Driver: {id(car_reinstanced.driver)} Owner: {id(car_reinstanced.owner)}") # expected to be same


pulumi up fails because of a multiline string in _inputs.py

A bug in _inputs.py - probably caused by the tfgen code generation - currently is causing pulumi-vsphere not to work.
https://github.com/pulumi/pulumi-vsphere/blob/69145724f1fb0aa91b229cc0120a0824b8807d37/sdk/python/pulumi_vsphere/_inputs.py#L969-L990
Using the vSphere provider will fail with

SyntaxError: EOL while scanning string literal
error: an unhandled error occurred: Program exited with non-zero exit code: 1

This can easily be fixed by wrapping any string that contains a EOL char in tripple quotes. I'd submit a PR but since this is generated by  tfgen it probably makes more sense to fix it in there, since this seems to be a generic issue with the python code generation.

Hi @omniproc
Apologies you are getting this error - I will get this fixed up and a new version shipped ASAP!
Paul


Change PHP_MIRROR to us2.php.net

us1.php.net was removed a while ago.
Fixes

$ make -f travis/pecl/Makefile php
mkdir -p /home/travis/job-20.3/src
printf "master\tmaster\tgit clone --depth 1 -b master https://github.com/php/php-src php-master && cd php-master && ./buildconf\n" >/home/travis/job-20.3/src/releases.tsv
curl -Ss "http://php.net/releases/index.php?json&version=7&max=-1" | travis/pecl//php-version-url-dist.php >>/home/travis/job-20.3/src/releases.tsv
curl -Ss "http://php.net/releases/index.php?json&version=5&max=-1" | travis/pecl//php-version-url-dist.php >>/home/travis/job-20.3/src/releases.tsv
curl -Ss "http://qa.php.net/api.php?type=qa-releases&format=json"  | travis/pecl//php-version-url-qa.php   >>/home/travis/job-20.3/src/releases.tsv
cd /home/travis/job-20.3/src && awk -F "\t" '/^5.6\t/{exit system($3)}' </home/travis/job-20.3/src/releases.tsv
curl: (6) Could not resolve host: us1.php.net

Sorry, I did not recognize this PR in time. PHP mirrors were retired meanwhile and the mirror has been changed to php.net.
Easy fix would have been:
make -f travis/pecl/Makefile PHP_MIRROR=https://php.net/distributions/ php

Sorry again for missing out!


Add CUDA 12.5 and update 12.4 builds

This PR adds CUDA 12.5.0 builds for both Windows and Linux. Additionally, CUDA 12.4.0 is bumped to 12.4.1 and is now enabled for Windows.
Fixes #1264
@Titus-von-Koeller

i am still getting this error how to fix?
cuda 12.4

i am still getting this error, with bitsandbytes version of 0.45.0, for cuda 12.4, how to solve it.


Simplified comparison update

With just the Func and the check for IEquatable.
Replacing previous pull request

:pineapple: Done with my review. Some comments for you.

Cheers, will make those changes now.

Changes done. In the CompareResults method I have moved the null checks to the top so any consumers do not need to worry about null checking the objects that are passed to their comparison code.

I'll fix up these conflicts as I want to make some slight changes.


when using the Image.copy() function for sub-classes of Image (e.g. Darks) the sub-class type is not copied

This was brought to my attention by the fact that @JuergenSchreiber created a new copy function for the KGain class in PR #80.
You can see this like this:
`import corgidrp.mocks as mocks
import corgidrp.detector as detector
dark_dataset = mocks.create_dark_calib_files()
dark_frame = detector.create_dark_calib(dark_dataset)
dark_frame_copy = dark_frame.copy()
print(type(dark_frame))
print(type(dark_frame_copy))`
Gives the output:

Hopefully there's a way we can generalize this without the need for new copy methods for each new calibration datatype.

unfortunately the best solution is to write a new version of the copy() class, unless we can guarantee that all constructors have the same signature (all __init__() functions take the same constructor). There is a hack we can do, but I can't guarantee it'll always work

Only if that function actually gets used.

I suppose. It's low priority, but I still think something we want eventually.

I made a new low priority tag

If we want to use the copy module, we could save writing copy functions.
I tested it on a kgain instance and it seems to work:
import copy
#reference copy
kgain_copy = copy.copy(kgain)
#deep data copy
kgain_copy = copy.deepcopy(kgain)
What do you think?

Good idea!

Sounds good!

Closed with Merge PR #217

So that I understand, @JuergenSchreiber, your PR #217, updated the readme, but it doesn't affect existing implementations, right?

@maxwellmb yes, correct

Should we just replace the innards of the existing copy functions to use copy.deepcopy() instead?

sounds like a good idea to me

I am not sure whether I understand what you mean. Deleting the existing copy functions? The copy module also works with the existing copy functions. I think the drawback is that it does not update the drp version and time header keywords
'DRPVERSN" and "DRPCTIME", which the existing copy functions do.

I think Max might mean take the ~10 other lines of code that involve new object creation and use deepcopy(), but still keep the few extra lines of code that moidfy DRPVERSN and DRPCTIME

I have created a new branch  copy_replace where I removed the copy functions from the subclasses and used the Image.copy function using the copy module. It seems to work. Could you please check whether we should make a PR out of it?

Took a glance at it, and it looks good to me. we can iterate details in PR if needed

Addressed in #248


uses v2 interface of github.com/goavro

Update gogen-avro to use v2 interface of github.com/linkedin/goavro

Sorry for the slow reply, there's no linting in CI right now, just the unit tests and integration tests. Adding megacheck and golint sounds like a good idea.

Also thanks for taking this on!


WMT results do not correspond to a WMT task

The download script https://github.com/tensorflow/nmt/blob/master/nmt/scripts/wmt16_en_de.sh corresponds to the parallel data from WMT 2016.  But your table https://github.com/tensorflow/nmt#wmt-english-german--full-comparison only reports results on newstest2014 and newstest2015, not newstest2016.  So your system was trained on more parallel data (WMT 2016) than systems that appear as "WMT SOTA" in the table (WMT 2014 and 2015).
I also contend that the term "WMT SOTA" i.e. "state of the art" should include WMT 2017 baselines.

Hi Kenneth,
Thanks for the the comments! Yes, we will improve by reporting results on newstest2016 + adding WMT'16 SOTA results from http://matrix.statmt.org/. Does that sound good?
FWIW, we were trying to keep the tutorial simple by not reporting results of both models trained on WMT'14 and WMT'16 data. If we compare WMT de-en data across 3 years (2014, 2015, 2016), the only data source that changes is News Commentary (5% of total data); the data sizes go from 77MB (2014) -> 122MB (2015) -> 72MB (2016). As such, I suspect there will not be drastic differences for de-en across years.
-T


Looking for transfer out from Bangladesh

#need to leave, overloaded

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

ID: 8ce7d1e8-e4b9-6152-4fbe-5d3f3d9f0583
Version Independent ID: 7676911e-6a80-06f1-b429-a3ce399c386e
Content: How to add an existing Azure subscription to your Azure AD directory
Content Source: articles/active-directory/active-directory-how-subscriptions-associated-directory.md
Service: active-directory
GitHub Login: @curtand
Microsoft Alias: curtand

closing as spam


Redirect users away from canonical hostnames

This un-reverts 1713c9a53c0060275350af9fb78c05d5e1c856f6 and
3d479fcba1aa86dfe6d35bd43ddf8c8c3de7c5e3. It also includes one fix, to
work around an apparent Phoenix bug whereby
SiteWeb.Endpoint.config(:url)[:host] is not set to the canonical
hostname as it should be. Instead we reach directly for System.get_env.
Asana Ticket: mbtace.com being indexed/viewed by public

Before getting review, please check the following:

[x] Does frontend functionality render and work correctly in IE?
[x] Have we load-tested any new pages or internal API endpoints that will receive significant traffic?
[x] Are interactive elements accessible to screen readers?
[x] Have you checked for tech debt you can address in the area you're working in?
[x] If this change involves routes, does it work correctly with pertinent "unusual" routes such as the combined Green Line, Silver Line, Foxboro commuter rail, and single-direction bus routes like the 170?
[x] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages?

@thecristen I tried it in dev-green and I'll double check in dev as well; if it works in those two it should work in prod. Just to be safe I'm going to be ready to roll this back quickly when I do deploy.


Build failed on lost-pixel-update.yml

Github workflow shows build unsuccessful, used the same file as mentioned in this link https://blog.logrocket.com/storybook-visual-regression-testing-lost-pixel-react/#what-is-lost-pixel

<EMAIL_ADDRESS>My config file looks like:-
import { CustomProjectConfig } from 'lost-pixel';
export const config: CustomProjectConfig = {
storybookShots: {
storybookUrl: './storybook-static',
},
// OSS mode
generateOnly: true,
failOnDifference: true
// Lost Pixel Platform (to use in Platform mode, comment out the OSS mode and uncomment this part )
// lostPixelProjectId: "xxxx",
// process.env.LOST_PIXEL_API_KEY,
};

Now I'm facing this another weird issue

I am not able to update my baseline images, can you let me know why this is happening

It was resolved thanks for your time


feat: implement persistedDocuments.hashAlgorithm

Description
Proposal to add the ability to specify the hash algorithm used for persisted documents as mentioned by #9108.
Ideally, we would like the ability to pass our own generateDocumentHash function so consumers could use their own hash implementation. But, I figured we mostly want to comply with Apollo Server and/or still rely on crypto and therefore to avoid the dance with crypto: createHash, update, and digest, it should be more friendly to accept an algorithm directly.
import { type CodegenConfig } from '@graphql-codegen/cli'

const config: CodegenConfig = {
  schema: 'schema.graphql',
  documents: ['src/**/*.tsx'],
  generates: {
    './src/gql/': {
      preset: 'client',
      presetConfig: {
-       persistedDocuments: true
+       persistedDocuments: {
+         hashAlgorithm: 'sha256',
+       },
      }
    }
  }
}

Related #9108
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Warning: There's no documentation related to persistedDocuments accepting an object instead of a boolean, outside of within the code. We should document those options (mode, hashPropertyName) and document hashAlgorithm at the same time.

How Has This Been Tested?

[x] Still defaults to sha1
[x] Passing hashAlgorithm: 'sha256' uses sha256
[x] Passing hashAlgorithm: 'sha1' uses sha1
[x] Added test

Checklist:

[x] I have followed the CONTRIBUTING doc and the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Can you please also document this on the docs?

@n1ru4l persistedDocuments as a config object is currently not documented in the docs—at least, I couldn't find it. I plan on sending another pull request to document all the options of persistedDocuments including this new one.


FR: Decoupling reflection

Hi,
I want to create custom templated serialization method based on provided reflection capabilities for aggregate types(visit_members_types, visit_members).
Unfortunately those methods depends on number_of_members, which depends on has_serializer producing circular dependency.
It makes those reflection functions unusable in serialize methods.
I think that it might be useful to make those reflections methods independent of any serialization methods.
https://godbolt.org/z/GqT6f67Wd

Interesting idea, I’ll need to think if there is a workaround that you can use right now without any code change, because this usage of visiting members is intended to work without the custom serialization function.


Error during build process on Nuxt project

Hey there I'm having some issue while deploying my nuxt project to now.
I'm posting to nuxt as well to see if they can assist but since the problem is only existing currently while deploying to now.sh and I can't replicate it locally I thought I'd see what people had to say.
The repo to project I'm speaking of can be found here:
https://github.com/devanflaherty/milleniaoffice.com
So around 8 hours ago I deployed the above repo to now, and it succeeded.
Moments later I modified a few files, nothing intensive, and then went to deploy again.
Kept failing during the build. SO I tried some things.

I changed node versions.
Removed Node_Modules.
Changed the node 'engines' called for in package.json.

A few time randomly I'd get EsLint errors for a few components. For some reason the back-tick in my template literals were causing issues. SO I removed those. Still nothing. I don't get the EsLint errors but it still doesn't build.
So low and behold, this is the error I keep getting:
Ran with now -d
> Deploying ~/Repositories/millenia under<EMAIL_ADDRESS>> [debug] Detected `deploymentType` = `npm`
> [debug] Detected `deploymentName` = "millenia"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.git"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.gitignore"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.nuxt"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/dist"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/node_modules"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/assets/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/assets/panos/.DS_Store"
> [debug] locating files /Users/devanflaherty/Repositories/millenia: 7.440ms
> [debug] Getting files: 9.120ms
> [debug] Computing hashes: 144.651ms
> [debug] get files ready for deployment: 3.320ms
> [debug] v2/now/deployments: 3246.175ms
> Using Node.js 9.2.1 (requested: `>8.1.x`)
> Ready! https://millenia-rmdkschhqx.now.sh (copied to clipboard) [3s]
> You<EMAIL_ADDRESS>are on the OSS plan. Your code and logs will be made public.
> NOTE: You can use `now --public` to skip this prompt
> Initializing…
> Error! The build step of your project failed. To retry, run `now --force`.
millenia  master ✗ 6h28m ✖ △ ⍉ -> now -d
> Deploying ~/Repositories/millenia under<EMAIL_ADDRESS>> [debug] Detected `deploymentType` = `npm`
> [debug] Detected `deploymentName` = "millenia"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.git"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.gitignore"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/.nuxt"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/dist"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/node_modules"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/assets/.DS_Store"
> [debug] ignoring "/Users/devanflaherty/Repositories/millenia/static/pano/assets/panos/.DS_Store"
> [debug] locating files /Users/devanflaherty/Repositories/millenia: 7.690ms
> [debug] Getting files: 9.496ms
> [debug] Computing hashes: 138.464ms
> [debug] get files ready for deployment: 3.434ms
> [debug] v2/now/deployments: 2038.909ms
> Using Node.js 9.2.1 (requested: `>8.1.x`)
> Ready! https://millenia-ykqckoyncw.now.sh (copied to clipboard) [2s]
> You<EMAIL_ADDRESS>are on the OSS plan. Your code and logs will be made public.
> NOTE: You can use `now --public` to skip this prompt
> Initializing…
> Building
> ▲ npm install
> ✓ Using "yarn.lock"
> ⧗ Installing 35 main dependencies…
> ✓ Installed 1213 modules [8s]
> ▲ npm run build
> ><EMAIL_ADDRESS>build /home/nowuser/src
> > nuxt build
> 2017-12-30T08:40:58.347Z nuxt:build Building...
> Sat, 30 Dec 2017 08:40:58 GMT nuxt:pwa Adding icons
> Sat, 30 Dec 2017 08:40:58 GMT nuxt:pwa static/icon.png not found! Please create one or disable icon module.
> Sat, 30 Dec 2017 08:40:58 GMT nuxt:pwa Adding manifest
> Manifest meta already provided!
> Sat, 30 Dec 2017 08:40:58 GMT nuxt:pwa Adding meta
> Sat, 30 Dec 2017 08:40:58 GMT nuxt:pwa Adding workbox
> 2017-12-30T08:40:58.722Z nuxt:build App root: /home/nowuser/src
> 2017-12-30T08:40:58.722Z nuxt:build Generating /home/nowuser/src/.nuxt files...
> 2017-12-30T08:40:58.755Z nuxt:build Generating files...
> 2017-12-30T08:40:58.764Z nuxt:build Generating routes...
> 2017-12-30T08:40:58.787Z nuxt:build Building files...
> Killed
> npm ERR! code ELIFECYCLE
> npm ERR! errno 137
> npm ERR<EMAIL_ADDRESS>build: `nuxt build`
> npm ERR! Exit status 137
> npm ERR!
> npm ERR! Failed at the<EMAIL_ADDRESS>build script.
> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/nowuser/.npm/_logs/2017-12-30T08_41_24_443Z-debug.log
> Error! The build step of your project failed. To retry, run `now --force`.

Also here is the initial working deployment:
https://milleniaoffice.now.sh
Please help if you can.

Well after hours, around 8 total (damn) I found this was what was crushing me.
plugins: [
    // ... more plugins above
    { src: `~plugins/axios` },
  ]

This is what the plugin looked like:
import axios from 'axios'

let options = {}
// The server-side needs a full url to works
if (process.server) {
  options.baseURL = `http://${process.env.HOST || 'localhost'}:${process.env.PORT || 3000}`
}

export default axios.create(options)

Found out I shouldn't have added that plugin to the plugins nuxt.config.

I removed axios plugin from nuxt.config but still got this error during nuxt build.
Also I changed host and port configs in nuxt.config to
port: 83,
host: 'mysitename.com'
Am I doing wrong? Which part? Please give me any suggestions...
Thanx

Same


update build image to use latest go

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
the image gcr.io/k8s-staging-releng/releng-ci:latest-go1.17 is not being generated and that image has go 1.17rc2 we now build two configs for the latest tag:

gcr.io/k8s-staging-releng/releng-ci:latest-go1.17-bullseye
gcr.io/k8s-staging-releng/releng-ci:latest-go1.17-buster

let's use the one with the bullseye for now
to show that we are building bom with 1.17rc2
$ docker run gcr.io/k8s-staging-bom/bom:dcaf425 version
Unable to find image 'gcr.io/k8s-staging-bom/bom:dcaf425' locally
dcaf425: Pulling from k8s-staging-bom/bom
b0b160e41cf3: Pull complete
250c06f7c38e: Pull complete
2be54ece9dd9: Pull complete
Digest: sha256:f16abe64f52e60b519c0acfc205f955e6d304a8529282393ff12f437ff86833c
Status: Downloaded newer image for gcr.io/k8s-staging-bom/bom:dcaf425
  ____     ___    __  __
 | __ )   / _ \  |  \/  |
 |  _ \  | | | | | |\/| |
 | |_) | | |_| | | |  | |
 |____/   \___/  |_|  |_|
bom: A tool for working with SPDX manifests

GitVersion:    v0.2.2-73-gdcaf425
GitCommit:     dcaf425
GitTreeState:  clean
BuildDate:     2022-03-29T05:49:11Z
GoVersion:     go1.17rc2
Compiler:      gc
Platform:      linux/arm64

/assign @puerco
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

Thanks @cpanato !
/lgtm


refactor: concatenate all variables files into one in core

Centralize all variables into one file
Remove useless imports

CDS Report yarn-build#1318.0 ✘

build & test

build ✘
test ✘

Why ?

@FredericEspiau To facilitate the creation of themes (ovh stack, dark mode). And also for the maintainability, we have all in one place (like Bootstrap).