Usage example?

Hi, I work on Chrome, and my next task is to create a native resize observer. It'll be similar to element-resize-detector.
I am currently writing a spec, and am looking for usage examples. Do you have any examples of where resize detector was needed?
PS: The scrolling trick you've used is neat. I've thought about how I'd write a polyfill, and did not come up with anything as clever.

Hi,
That's great news!
Yes, me and my team are currently developing a new responsive version of the web-based bank application for one of the top banks in Sweden. The app currently consists of 3000 pages, and there are several sister-apps to fill different purposes. We wanted to create reusable view modules that can be shared between pages/apps, and therefore we are much interested in element queries. While waiting for element queries to be standardised, we created a JS library to help us with this task called ELQ (https://github.com/elqteam/elq) that of course uses the element-resize-detector in order to detect resize events of elements.
In practice, it means that we do not use CSS media queries at all in order to stay modular. So all our views (tables, forms, menus, etc.) all use element queries and indirect element resize detection in order to know when to change layout. I can provide you tons of specific use cases for our views, If you want.
While modular views using element queries have been the main use case, we have also used the element resize detector in documentation purposes. All our modular views can be viewed in a special documentation app that we created for our customers. In the app, it is possible to see the view live with different data and settings. Also, we visualise the responsivity by showing a ruler marked with breakpoints of the view. The ruler uses element resize detection in order to adapt itself to the container. Also, the user is able to resize views freely to see the responsivity in action. Here, we also use the element resize detection to display the current size of the view for the user.
This is an overview of our usage of element resize detection. I could provide you with more details if you like. We've created an article that might be interesting to you regarding our usage of element queries https://github.com/wnr/chi-elq-note/raw/springer/elq.pdf.

PS: The scrolling trick you've used is neat. I've thought about how I'd write a polyfill, and did not come up with anything as clever.

Thank you! I cannot take full credit as Daniel Buchner originally came up with the idea. However, I do have improved it quite a bit :)
PS: I would love to assist with the spec/polyfill :)

Thanks so much for this, it was helpful. And we'd love to have your input on the rest of it. I'll send you the proposal as soon as I have something interesting. Can you send me your email to<EMAIL_ADDRESS>

Nice, I'm glad you found it helpful :) Yes, I'll send you an email right away. Also, I'll close this issue as I figure we'll continue our discussion by email.


fix(deps): update dependency d3 to v5

CAN WE EVADE THIS UPGRADE BY USING STUFF FROM UI-KIT?
This PR contains the following updates:

Package
Type
Update
Change

d3 (source)
dependencies
major
3.5.16 -> 5.15.0

Release Notes

d3/d3
v5.15.0
Compare Source

Add d3.interpolateNumberArray.
Add support for typed arrays to d3.interpolate.
Add support for typed arrays to d3.interpolateArray.
Fix numeric interpolation to return exact values for t = 0 and t = 1.
Fix trimming of trailing zeroes in exponents.

v5.14.2
Compare Source

Expose brush.touchable.

v5.14.1
Compare Source

Propagate the this context to interpolators in transition.styleTween, transition.attrTween and transition.textTween.

v5.14.0
Compare Source

Add transition.textTween.
Fix handling of zero values in d3.stackOffsetDiverging.

v5.13.1
Compare Source

Fix crash initializing d3.brush.

v5.13.0
Compare Source

Add d3.csvFormatRow.
Add d3.csvFormatValue.
Add d3.tsvFormatRow.
Add d3.tsvFormatValue.
Add dsv.formatRow.
Add dsv.formatValue.
Add support for parsing 4- and 8-digit hexadecimal colors in d3.color. Thanks, @zerovox!
Allow shorthand for current time intervals (e.g., d3.timeDay() returns today’s midnight).
Disallow whitespace and periods in type names passed to d3.dispatch.
Add fa-IR d3-time-format locale. Thanks, @mohsentaleb!
Add %q directive for quarter of the year as a decimal number. Thanks, @jheer!
Fix off-by-one error formatting %U when the year starts with Sunday.
Fix off-by-one error formatting %W when the year starts with Monday.
Fix off-by-one error parsing week and weekday numbers with d3.utcParse.
Fix string coercion of specifier passed to d3.utcParse.
Fix parsing of %L or %f in conjunction with %s.

v5.12.0
Compare Source

Add d3.FormatSpecifier.
Allow minus sign to be localized in d3.format. Thanks, @benib!
Allow NaN to be localized in d3.format.

v5.11.0
Compare Source

Add d3.interpolateTurbo.
Add d3.interpolateCividis.

v5.10.1
Compare Source

Fix broken brush corner resizers.
Fix brush multitouch filtering.

v5.10.0
Compare Source
d3-brush

Add brush.touchable.
Add brush.clear.
Add brush.keyModifiers.
Fix default brush.extent to consider the SVG viewBox, if any.
Fix scroll prevention on touch devices.
Fix coercion of selection and extent inputs.
Fix order of handles in the DOM.
Fix brush.move when selection is empty.
Fix Space key immediately after clicking on a handle.
Fix missing brush event on parallel start.
Fix handling of orphaned input gestures.
Fix default brush.touchable if navigator.maxTouchPoints.
Fix multitouch gestures.
Fix click consumption when brush is not empty.
Fix default brush.filter on control-click.

d3-color

Add color.copy.
Add color.formatHex.
Add color.formatHsl.
Add color.formatRgb.
Deprecate color.hex; use color.formatHex instead.

d3-drag

Fix default drag.filter on control-click.
Fix default drag.touchable if navigator.maxTouchPoints.

d3-path

Fix coercion of anticlockwise argument to path.arc. Thanks, @Fil!

d3-scale-chromatic

Add d3.schemeTableau10. Thanks @akngs!

d3-zoom

Fix default zoom.extent to consider the SVG viewBox.
Fix default zoom.filter to ignore control-click.
Fix default zoom.touchable if navigator.maxTouchPoints.
Fix default zoom.wheelDelta if deltaMode !== 0. Thanks, @Dakkaron!
Fix handling of filtered multitouch gestures. Thanks, @robinhouston and @testower!
Fix handling of orphaned gestures.
Fix emitting of zoom events during dbltap gestures. Thanks, @cambecc!
Add optional point to zoom.transform and related methods.
Fix d3.zoomTransform to inherit the transform from the closest ancestor, if any.

v5.9.7
Compare Source

Revert chroma clamping in hcl.toString.

v5.9.6
Compare Source

Account for rounding when determining whether a color is displayable.

v5.9.5
Compare Source

Implement chroma clamping in hcl.toString.
Fix achromatic representation of white in d3.hcl (again).

v5.9.4
Compare Source

Fix achromatic representation of black and white in d3.hcl.

v5.9.3
Compare Source

Fix d3.stackDivergingOffset when there is only one series.
Fix achromatic representation of black and white in d3.hcl.
Fix d3.geoContains for LineStrings. Thanks, @ondras!
Fix d3.geoContains for longitudes outside of ±180°.
Fix d3.geoBounds for sphers.

v5.9.2
Compare Source

Fix bug when initializing nodes with fixed positions in force simulations.

v5.9.1
Compare Source

Fix corruption when quadtree.cover is coincident with the current extent.
Favor a more concise ISO 8601 format for dates in dsv.format and dsv.formatRows.

v5.9.0
Compare Source
d3-dsv

Add d3.autoType for automatic type inference when parsing!
Add dsv.formatBody, d3.csvFormatBody, and d3.tsvFormatBody.
In dsv.format and dsv.formatRows, use date.toISOString to format dates.

v5.8.2
Compare Source

Fix d3.timeMinute and d3.timeHour for historical times.

v5.8.1
Compare Source

Fix rendering glitch with arc.cornerRadius.

v5.8.0
Compare Source
d3-force

Add iterations argument to simulation.tick. Thanks, @vasturiano!
Fix bug when initializing nodes with fixed positions. Thanks, @vasturiano!

d3-geo

Fix projection where |longitude| > 180°.

d3-scale

Add domain and range (or interpolator) convenience constructors for all scale types.
Add default constructors for sequential and diverging scales.
Add d3.tickFormat.
Add d3.scaleSymlog.
Add transformed sequential scales (e.g., d3.scaleSequentialLog).
Add transformed diverging scales (e.g., d3.scaleDivergingLog).
Add d3.scaleSequentialQuantile for p-quantiles.
Add scale.unknown for all scale types.
Allow unlimited band.paddingOuter and point.padding.
For collapsed domains, use midpoint of domain or range rather than start.

d3-selection

Add selection.join!
Fix selection.order to enforce relative position, rather than exact siblings.
Remove vendor fallback for element.matches in selection.filter and d3.matcher.

d3-shape

Add d3.stackOrderAppearance. Thanks, @isaomatsunami!
Fix d3.stackOrderInsideOut to use appearance (onset) rather than sum.
Fix rendering glitch with rounded arcs.

d3-transition

Add transition.end.
Add cancel events to transition.on.
Improve the performance of transition.style and transition.attr.
Tween functions can now use this to refer to the current node.
Fix removal of styles when the value passed to transition.style is null.
Fix interpolation in transition.style and transition.attr in certain non-string cases.

v5.7.0
Compare Source

Add d3.geoEqualEarth.
Add d3.interpolateHue.
Add d3.interpolateDiscrete.
Fix upper histogram bin threshold in some cases.
Fix axis domain rendering when the outer tick size is zero.

v5.6.0
Compare Source

Add density.weight.
Use currentColor instead of black for axes.

v5.5.0
Compare Source

Add d3.scaleDiverging.
Fix treatment of degenerate domains in d3.scaleSequential.

v5.4.0
Compare Source

Add d3.interpolateSinebow.

v5.3.0
Compare Source

Add ~ option to d3.format to trim insignificant zeros. Thanks, @vasturiano!
Fix d3.formatSpecifier to not bake shorthand aliases.

v5.2.0
Compare Source

Add color.hex.
Add d3.piecewise.

v5.1.0
Compare Source

Add d3.lch.
Add d3.gray.
Switch from D65 to D50 for Lab and HCL color spaces. Thanks, @danburzo!
Fix Lab and HCL representation of achromatic colors.

v5.0.2
Compare Source
Replaced by 5.1.0.
v5.0.1
Compare Source

Fix occasional overlap and hang in d3.packSiblings. Thanks, @robinhouston!

v5.0.0
Compare Source

Remove d3-request; add d3-fetch.
Remove d3-queue; see Promise.all.
Add d3-scale-chromatic.
Add d3-contour.
Add selection.clone.
Add d3.create.
Add projection.angle.
Remove d3.schemeCategory20* categorical color schemes. (See note below.)
Fix duplicate installation of D3 modules at different versions. (#3256)
Fix d3.format’s SI format for locales with currency suffixes.

D3 now includes new categorical color schemes from ColorBrewer, along with ColorBrewer’s excellent diverging, sequential single-hue and sequential multi-hue color schemes. The twenty-color schemes were removed because their grouped design often falsely implied non-existent relationships in the data: a shared hue can imply that the encoded data are part of a group (a super-category), while the relative lightness can falsely imply order.
For more on what’s new, read CHANGES.
v4.13.0
Compare Source

Add selection.clone.
Add d3.create.
Fix d3.format’s SI format for locales with currency suffixes.

v4.12.2
Compare Source

Pin to earlier version of UglifyJS to fix minified bundle.

v4.12.1
Compare Source

Point unpkg and jsDelivr to the minified bundle.

v4.12.0
Compare Source

Add d3.clientPoint.
Add zoom.constrain.
Add f, Q, s, u and V time format specifiers. Thanks, @BrianMitchL @krukon!
Add projection.fitWidth, projection.fitHeight. Thanks, @mfogel!
Add tr-TR time format locale. Thanks, @filiz137!
Improve messages for transition lifecycle errors.
Fix infinite loop in interval.range.
Fix sub-millisecond ticks for time scales. Thanks, @FracturedShader!
Fix thousands separator in fr-FR number format locale. Thanks, @victornoel!
Fix missing data.columns when the input to dsv.parse is empty. Thanks, @tomwanzek!
Minor optimization to d3.interpolateArray. Thanks, @jetzhliu.

v4.11.0
Compare Source

Add d3.forceRadial. Thanks, @nbremer!
Add drag.touchable. Thanks, @nicolas-van!
Add zoom.touchable.
Add d3.geoNaturalEarth1. Thanks, @Fil!
Add projection.preclip. Thanks, @Fil!
Add projection.postclip.
Add d3.geoClipAntimeridian.
Add d3.geoClipCircle.
Add d3.geoClipRectangle.
Fix d3.ticks when start is equal to stop and count is positive.

v4.10.2
Compare Source

Fix d3.timer sleeping for too long when timer invocation is expensive.

v4.10.1
Compare Source

Fix DSV parsing when the last field is empty (e.g., foo,bar,).
Replace the browser field in package.json with unpkg and jsdeliver. (#3138)
Replace the prepublish script with prepublishOnly.
Update dependencies.

v4.10.0
Compare Source

Add d3.areaRadial; deprecate d3.radialArea.
Add d3.lineRadial; deprecate d3.radialLine.
Add d3.pointRadial.
Add zoom.translateTo.
Re-implement d3.packEnclose using Matoušek-Sharir-Welzl. Thanks, @robinhouston!
Fix d3.packSiblings to center the circles more consistently around a fixed origin.
Fix axis rendering when a scale has a non-numeric range.
Fix interval.offset on filtered time intervals when step is negative.
Fix invocation of requestAnimationFrame in Edge. Thanks, @KonradKlimczak!
Invoke nest.sortValues comparator prior to nest.rollup aggregator.
Drag & zoom behaviors now only register touch event listeners when touch is supported.
Drag & zoom behaviors now set the touch-action style to “none” when touch is supported.

v4.9.1
Compare Source

Fix d3.linkRadial to use radians rather than degrees.
Optimize path.pointRadius slightly.

v4.9.0
Compare Source

Change selection.style to return the inline style, if present.
Change transition.style to start from the inline style, if present.
Add link shapes!
Add d3.stackOffsetDiverging.
Add random.source to allow custom sources of randomness. Thanks, @rolyatmax!
Add drag.clickDistance for setting the click distance threshold. Thanks, @Epiphero!
Add zoom.clickDistance for setting the click distance threshold.
Add d3.style.
Fix rounding errors in continuous.nice.
Fix inconsistency between continuous.ticks and continous.nice. Thanks, @danielyule!
Fix axis tick offset for band and point scales.
Fix drag click suppression to ignore mousemove events that don’t actually move.
Fix zoom click suppression to ignore mousemove events that don’t actually move.
Fix error trying to interpolate objects without prototypes. Thanks, @devgru!
Optimize generated axis DOM slightly.
Improve error message descriptions in d3.queue. Thanks, @ethervoid!

v4.8.0
Compare Source

Add d3.tickIncrement.
Fix d3.ticks to always return the most-precise representable values in IEEE 754!
Fix histogram.thresholds to retain thresholds equal to the domain’s upper bound.
Number format locales can now override the percent sign suffix. Thanks, @davinov!

v4.7.4
Compare Source

Fix primary touch location on secondary touchend when zooming.

v4.7.3
Compare Source

Fix the Mercator projection’s built-in clipping when projection.rotate is used.
Fix the transverse Mercator projection’s built-in clipping when projection.rotate is used.
Fix the transverse Mercator projection’s built-in clipping when projection.clipExtent is used.

v4.7.2
Compare Source

Optimize d3.pack.
Fix string coercion in transition.style and transition.attr. Thanks, @sghall!
Update dependencies.

v4.7.1
Compare Source

Fix the Mercator projection’s built-in clipping when projection.center is used.
Fix the Mercator projection’s built-in clipping when projection.clipExtent is used.
Ignore small-angle arcs in path.arc to workaround rendering bug in Chrome on Ubuntu.
Fix escaping of strings containing carriage returns in d3-dsv. Thanks, @jsedlacek!

v4.7.0
Compare Source

Add d3.cross.
Allow d3.pairs to take an optional reducer.
Add d3.geoContains. Thanks, @Fil!
Fix invalid transforms when an ordinal axis transition is interrupted.
Localized number formats can now define numeral systems, such as Hindu–Arabic.
Fix number formatting of negative infinity.
Maybe make rounded arcs a little more robust.
Optimize d3.geoCentroid. Thanks, @Fil!

v4.6.0
Compare Source

Add path.measure.
Improve d3.pack layout.
Fix d3.geoBounds for certain line geometries.
Fix d3.geoCentroid for detailed features. Thanks, @Fil!

v4.5.1
Compare Source
v4.5.0
Compare Source

Add node.count.
Fix overlapping circles in d3.pack and d3.packSiblings.

v4.4.4
Compare Source

Fix calculation of clock skew when page is backgrounded before timers are scheduled.

v4.4.3
Compare Source

Fix d3.event export on Node. (#3055)

v4.4.2
Compare Source

Fix d3.interpolateRgb.gamma’s opacity interpolation.

v4.4.1
Compare Source

Fix handling of zoom gestures that start with multiple touches.
Fix crash with coincident points in voronoi diagram.find.
Fix crash with coincident points in voronoi diagram.triangles.

v4.4.0
Compare Source

Add identity.reflectX and identity.reflectY to d3.geoIdentity.
Add zoom.interpolate to control zoom transition behavior.
Allow double-click and double-tap zoom transitions to be disabled.
Fix handling of a zoom.translateExtent smaller than the zoom.extent.
Fix handling of zero-valued nodes in squarified treemaps.
Fix parsing of unusual number formats in color specifications.
Fix implementations of force.initialize to allow isolation.
Fix d3.geoPath’s default projection and contex to be null, not undefined.
Improve performance of d3.path.

v4.3.0
Compare Source

Add diagram.find for fast searching of Voronoi diagrams. Thanks, @Fil!
Add d3.geoIdentity for scaling, translating and clipping planar geometry.
Add d3.geoGraticule10 for conveniently generating a default 10° global graticule.
Add optional arguments to d3.geoPath for projection and context.
Deprecate d3.geoClipExtent; use d3.geoIdentity’s clipExtent instead.

v4.2.8
Compare Source

Fix reporting of interrupt transition events.

v4.2.7
Compare Source

Fix bug where calling collide.radius had no effect.
Improve error message when link.links references unknown nodes.
Fix d3.geoConicConformal’s invert for south-pointing cones.
Fix d3.geoConicEqualArea when the cone is a cylinder.

v4.2.6
Compare Source

Fix hang in interval.every(…).range given invalid dates.

v4.2.5
Compare Source

Fix cache invalidation bug in d3.geoAlbersUsa.

v4.2.4
Compare Source

Fix a crash if brush selection is cleared via brush.move during a gesture.

v4.2.3
Compare Source

Chained transitions no longer sometimes interrupt their preceding transition.
Transitions no longer get stuck if an error is thrown on the last tick.
Transitions no longer leak memory if an error is thrown.
Optimize d3.geoPath.
Fix swallowed error in d3.queue’s await callback after a synchronous task.
Fix benign bug in d3.curveCatmullRom.
Fix for invalid timestamp argument in requestAnimationFrame in RStudio.
Update Rollup.

v4.2.2
Compare Source

Fix d3.geoStereographic’s invert.

v4.2.1
Compare Source

All modules now expose a module entry point (rollup/rollup-plugin-node-resolve#48).
Fix crash in d3.geoBounds.

v4.2.0
Compare Source

Add projection.fitExtent and projection.fitSize. Thanks, @veltman!

v4.1.1
Compare Source

Better defaults for map projections.
Fix crash when d3.zoom is simultaneously applied to an element and its ancestor.
Throw an error if a d3.request callback is invalid.
Deprecate the optional step argument to time.ticks; use interval.every instead.
Fix voronoi.size when the minimum values of the extent are non-zero.

v4.1.0
Compare Source

Export raw geographic projections.
Add d3.interpolateDate.
Change d3.interpolate to special-case dates.
Change d3.interpolate to special-case number-like objects.
Include d3-chord.
Fix for missing performance.now in IE9.

v4.0.0
Compare Source
D3 is now modular, composed of many small libraries that you can also use independently. Each library has its own repo and release cycle for faster development. The modular approach also improves the process for custom bundles and plugins.
There are a lot of improvements in 4.0: there were about as many commits in 4.0 as in all prior versions of D3. Some changes make D3 easier to learn and use, such as immutable selections. But there are lots of new features, too! These are covered in detail in the release notes; here are a few highlights.
Colors, Interpolators and Scales

Colors now have opacity (rgba, hsla, etc.).
New Cubehelix color space.
New sequential color scales, including Viridis and cyclical Rainbow.
New point and band scales replace ordinal.rangeBands and ordinal.rangePoints.
New basis spline interpolators (e.g., continuous ColorBrewer schemes).

Shapes and Layouts

Shapes (e.g., lines, areas, arcs) can now render to Canvas.
Fixed cardinal and monotone splines.
Added parameterized Catmull–Rom and natural splines.
New deterministic, extensible velocity Verlet force layout.
New circle-packing layout!
New extensible treemap layout; improved squarified treemaps; added binary treemaps.
New d3.stratify for tabular hierarchical data.
New faster, mutable, non-recursive quadtrees.
Voronoi diagrams now expose topological information.

Selections, Transitions, Easings and Timers

Selections and transitions are now immutable, providing a cleaner interface.
New selection.raise, selection.lower and selection.dispatch methods.
Time is now frozen in the background, avoiding unintended effort.
Timers can now be stopped externally.
Transitions can now interpolate CSS transforms (in addition to SVG transforms).
You can now cancel transitions using selection.interrupt.
Easier transition chaining thanks to new d3.active and changed transition.delay.
Better performance for homogenous transitions (e.g., shared interpolators across elements).
Better state persistence and enforcement for transitions.
Fixed elastic and bounce easing.

Even More!

Better default axis appearance.
Better brush interaction.
Built-in asynchronous queue for loading files in parallel.
New low-level d3.ticks API.

v3.5.17
Compare Source

More robust treatment of degenerate, almost-empty polygons in d3.geo.path (#2025).

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Enabled.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

PR has been edited
:construction_worker: This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


gpio:add feature for gpio wakeup

Summary
1.add pin type to cfg gpio as wake up source
2.add IOEXPANDER_OPTION_WAKEUPCFG for set wake up option
Impact
Add more feature in ioexpand.
Testing
CI-test.

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements.
Here's a breakdown of what's missing and how to improve it:
Summary

Insufficient Detail: The summary provides a high-level overview but lacks specifics.

Why is this change necessary?  What problem does it solve, or what new capability does it provide?
What functional part of the code is changed? Be more specific than "ioexpand". Mention the files or modules affected.
How does it work?  Provide a technical explanation of the implementation. For example, how are pin types configured for wake-up sources? How is IOEXPANDER_OPTION_WAKEUPCFG used?

Missing Issue References: If this PR addresses a specific issue in the NuttX or NuttX Apps repositories, include the issue numbers.

Impact

Too Vague: The impact section needs to be more specific.  Address all the bullet points with "NO" or "YES" and provide detailed explanations where applicable:

New Feature: You've indicated a new feature is added. Describe it clearly. What can users now do that they couldn't before?
User Impact:  Will users need to change their code or configuration to use this feature? If so, how?
Build Impact: Will adding this feature require changes to the build system (Kconfig, Makefiles, etc.)?
Hardware Impact:  Does this affect specific architectures, boards, or drivers? List them.
Documentation Impact:  Does this PR require documentation updates? If so, have you included the updates in the PR?
Security Impact:  Could this change introduce any security vulnerabilities? Consider potential risks carefully.
Compatibility Impact: Does this affect backward compatibility, forward compatibility, or interoperability with other systems/software?

Testing

Insufficient Information:

Local Setup: Specify the details of your local build host (OS, CPU, compiler) and target(s) (architecture, board, configuration) used for testing.
CI Tests Alone Are Not Enough:  While CI tests are important, they might not cover all edge cases. Describe the specific tests you performed locally to validate the changes.
No Logs: You haven't provided any testing logs to demonstrate the functionality before and after the change. Include relevant log snippets to show the issue and the fix.

How to Improve:

Expand on the Summary: Provide a clear and concise explanation of the change, its purpose, and its technical details.
Address All Impact Points: Go through each impact bullet point and provide a specific "NO" or "YES" response along with a detailed explanation if necessary.
Provide Comprehensive Testing Details: Describe your local test setup, the specific tests performed, and include relevant log snippets that demonstrate the change's effect.

Please update Documentation/

Please review the append patch describe about io expander


Add missing filter errors to openapi.json

Add missing filter errors to openapi.json.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


What is going on here??

Problem
I see people having the exact same issues ranging months back without anyone stepping in and providing a solution.
People jumping in to Shopify theme development will end up using Slate as it's referred everywhere and spend countless hours with the same issues.
Write in the very top of the main readme that assets url for images is broken and you will not provide a solution.
Or simply fix this issue.
 This is such a disaster, really.  You are wasting the time of the people are suppose to make life easier for

Slate is an open-source project that is currently in Beta. Any user can help improve it by creating an issue with constructive feedback or opening a Pull Request with changes they would like to see. There is also the option to fork Slate and modify it to your needs.
Mathias Åsberg (@Mindgames), the tone of your feedback is rude, unconstructive, and violates Slate's Code of Conduct . It adds nothing to this project and reflects poorly on your character as a developer. I understand you might be frustrated with parts of Slate, but this is not the way to communicate it.


CI jobs often fail with minikube error X Exiting due to GUEST_PROVISION

Describe the bug
When runninc CI jobs, minikube regularly fails with the following error:
* Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

This prevents the job from continuing, and a /retest ... is needed.
Logs
From mini-e2e_k8s-1.20/1523:
* Creating kvm2 VM (CPUs=8, Memory=14336MB, Disk=20000MB) ...
* Deleting "minikube" in kvm2 ...
! StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute
* Creating kvm2 VM (CPUs=8, Memory=14336MB, Disk=20000MB) ...
* Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

https://github.com/ceph/ceph-csi/pull/2343#issuecomment-891825471 failed again (logs)

https://github.com/ceph/ceph-csi/pull/2308#issuecomment-891856084 failed here too (logs)

https://github.com/ceph/ceph-csi/pull/2354#issuecomment-892400000 as well (logs)

failed in https://github.com/ceph/ceph-csi/pull/2350#issuecomment-892500553 too (logs

https://github.com/ceph/ceph-csi/pull/2341#issuecomment-892516420 hit this too (logs)

@nixpanic as we are hitting frequently is it a good idea to add a wrapper to retry?

https://github.com/ceph/ceph-csi/pull/2322#issuecomment-892634477 hit this (logs)

@nixpanic as we are hitting frequently is it a good idea to add a wrapper to retry?

I don't know. There is already an automated retry by minikube. We should try to identify the cause and work on preventing it. Gathering the hostnames of the CentOS CI bare-metal machines might give a clue. Different groups of hosts have different hardware, and are in different subnets (https://wiki.centos.org/QaWiki/PubHardware).

https://github.com/ceph/ceph-csi/pull/2341#issuecomment-892773815 as well (logs)

https://github.com/ceph/ceph-csi/pull/2339#issuecomment-892851474 hit this too (logs)

https://github.com/ceph/ceph-csi/pull/2351#issuecomment-893288535 has seen this

2x even! https://github.com/ceph/ceph-csi/pull/2351#issuecomment-893288932

backports sometimes hit this too, like https://github.com/ceph/ceph-csi/pull/2369#issuecomment-893454809

hit it again https://github.com/ceph/ceph-csi/pull/2374#issuecomment-895014980

once more https://github.com/ceph/ceph-csi/pull/2376#issuecomment-895195300

https://github.com/ceph/ceph-csi/pull/2448#issuecomment-908397774 failed too

I don't know if it was by chance or the real workaround, but after generating the ssh keys locally via ssh-keygen it worked now for me for the first time after 20-25 different attempts.
Is this something that we can try?

I don't know if it was by chance or the real workaround, but after generating the ssh keys locally via ssh-keygen it worked now for me for the first time after 20-25 different attempts.
Is this something that we can try?

Just want to be sure how generating ssh keys will fix this issue?

I don't know if it was by chance or the real workaround, but after generating the ssh keys locally via ssh-keygen it worked now for me for the first time after 20-25 different attempts.
Is this something that we can try?

Just want to be sure how generating ssh keys will fix this issue?

Yac!  It doesn't make any sense.
The other thing I tried was

Flushing IP tables locally
Disable SELinux

Maybe it worked because of this!

Today I'm hitting this again locally and none of my previous mentioned guess workarounds are working :-(

adding minikube logs when this fails might be helpful to see what's happening.

! StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

* Creating kvm2 VM (CPUs=8, Memory=14336MB, Disk=32768MB) ...

* Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

*

���                                                                                ���

���    * If the above advice does not help, please let us know:                                 ���

���      https://github.com/kubernetes/minikube/issues/new/choose                               ���

���                                                                                ���

���    * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    ���

���                                                                                ���

���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������

This is definitely not fixed yet :disappointed:

Seems like kubernetes/minikube#11459 is reported too.

This has not happened since a long time.


Smarter Default sizing of dataframe via widget

setup the python widget code to only send a max of 500 rows of data to the JS widget by default.  more data is likely to cause performance problems and isn't the right way to explore large datasets - summary stats are.

Fixed via sampling


reverse proxy example? thx

reverse proxy example? thx

Thanks for attention. Reverse proxy is on the way.


Moving psr/log onto a 1.x version instead of dev master

There doesn't seem to be any reason to use dev-master as psr/log hasn't been updated for 4 years. ~1.0 or 1.0.0 should be fine here.

@Crisfole ping!
Can someone give some attention to the PRs the community is opening? It's quite unsettling the lack of feedback/attention this is getting for a paid service.

Thanks @NoodlesNZ! Looks like this is done in 1.0 - we now have:
"psr/log": "~1.0.2",


Provide support to add optional parameters in OAuth2 introspection request [1.2.x]

Purpose
This PR provide the capability to add the optional parameters to the OAuth2 introspection request [1]. The updated oauth2:IntrospectionServerConfig is as follows:
public type IntrospectionServerConfig record {|
    string url;
    string tokenTypeHint?;
    map<json> optionalParameters?;
    cache:Cache oauth2Cache?;
    int defaultTokenExpTimeInSeconds = 3600;
    http:ClientConfiguration clientConfig = {};
|};

Example:
oauth2:IntrospectionServerConfig introspectionServerConfig = {
    url: "https://localhost:20102/oauth2/token/introspect",
    tokenTypeHint: "access_token",
    optionalParameters: {
        "custom": "custom-value"
    },
    clientConfig: {
        auth: {
            authHandler: basicAuthHandler
        },
        secureSocket: {
           trustStore: {
               path: config:getAsString("truststore"),
               password: "ballerina"
           }
        }
    }
};

[1] https://tools.ietf.org/html/rfc7662#section-2.1
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[x] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #26464 into ballerina-1.2.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #26464   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

Continue to review full report at Codecov.

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


Locking and unlocking by ways other than input action id.

From the real world, before locking the cursor, the game shows the game menu and other stages where standard behaviour is required. And then, when the player presses the "Start Game" button, the game level loads and the cursor is locked. Conversely, when the player, for example, opens a chest in the game world, the inventory window opens and the cursor is unlocked.
In this case it would be more convenient to have some kind of interface for locking, a module method or message handling. As it is not clear why locking should be related to mouse click.
Maybe I don't fully understand the idea of a virtual cursor and this is the solution?

In this extension (although it's more just an example implementation rather than an extension anymore) I was assuming the behaviour of large PC games, where the game launches and you give the game cursor control with a mouse click.
That's the industrial standard in PC games, in my opinion.
As it is, I agree that this behaviour should be made customisable.

I realised that games really do capture the cursor always by providing their own virtual cursor.
Then, if the cursor is even virtual, usually, when you start a PC game, the cursor is captured immediately and automatically, without an additional click.

To do it still need some sort of command, other than a click.

Yeah, but you can lock mouse without user iteraction only on PC/Mac. So just call window.set_mouse_lock(true) on these platforms.
P.S. I will add a flag like autolock or lock_on_click.

Wait a minute, it's possible to do with the inbuilt api at the moment? Omg, where have I been all this time... 😂
Thanks for the discovery! Now I'll have to figure out the best way to use it all for the operator 🤔

Yes, there is a huge statement on the top of Pointer Lock's README:

💡 Prior to Defold 1.3.7, this extension had C API to lock/unlock mouse cursor. After the release of Defold 1.3.7, the C API was cut and since then the extension has been the demo project of how to implement mouse lock in your Defold game.


Mark secretKey as secret on Provider

Problem
If I use a custom provider and pass in a secretKey, the secret key value ends up in plaintext in the state file.
Suggestion
secretKey should be marked secret automatically by the provider itself so that users don't have to do the workaround below.
Code to reproduce
const awsProvider = new aws.Provider("main", {
    region: <aws.Region>env["AWS_REGION"]!,
    accessKey: env["AWS_ACCESS_KEY_ID"]!,
    secretKey: env["AWS_SECRET_ACCESS_KEY"]!,
});

Workaround
const awsProvider = new aws.Provider("main", {
    region: <aws.Region>env["AWS_REGION"]!,
    accessKey: env["AWS_ACCESS_KEY_ID"]!,
    secretKey: pulumi.secret(env["AWS_SECRET_ACCESS_KEY"]!), // Use pulumi.secret(...) to protect this value
});

Just for reference, in python it would be
import pulumi
import pulumi_aws as aws

aws_provider = aws.Provider("main", region=env["AWS_REGION"], access_key=env["AWS_ACCESS_KEY_ID"],
                        secret_key=pulumi.Output.secret(env["AWS_SECRET_ACCESS_KEY"]))

We don't store these values in Provider any more - that was fixed since this issue was raised - sorry for the issue here
Paul


There is problem about sequence_expand op doc.

There is problem about the lod of the cases. The right case should be:

Which can be infer from:
https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/fluid/operators/sequence_expand_op.cc#L122

It's OK. You can treat the LoD in the original doc as the length-based LoD, instead of the offset-based one. In the Python end, we prefer to let users get used to the length-based LoD.

我看到 c++端的op都是使用的 offset-based。是python端会将 length-based LoD改成offset-based么？

python端已经改成offset-based, C++端也要改。

@luotao1 原来这样。我之前对sequence 这块不是太熟悉，想了解这个op，发现两边的文档不一致就会感觉到疑问。我感觉对其他的刚接触这块的同学也应该会遇到这个问题，所以会影响到用户体验，感觉有必要进行fix


eb create - ERROR: OS Error - [Errno 102]

I got an error when creating a new environment using the CLI on my Mac. What's odd about this is the error message is saying related to operation not supported on socket related to Adobe Acrobat notification.
FOO-MBP01:~ foo$ eb create
Enter Environment Name
(default is foobar-01-dev): foobar-01-dev
Enter DNS CNAME prefix
(default is foobar-01-dev): foobar-01-dev

Select a load balancer type
1) classic
2) application
3) network
(default is 2): 2

Would you like to enable Spot Fleet requests for this environment?
(y/N): N
Creating application version archive "app-200304_175640".
ERROR: OSError - [Errno 102] Operation not supported on socket: './Library/Application Support/Adobe/Acrobat/DC/Reader/Synchronizer/Notification'

Thanks for reporting this. We will look into the issue and report back here when have an update.

@iu-cedilla , can you rerun eb create with the --debug argument? This will print a stack trace that will help identify the problem.
Also, which terminal software did you run this command on?

Closing this issue due to inactivity

@iu-cedilla I'm seeing this problem too, any luck?

No since I decided to not continue with this method. eb create --debug spits out a lot of info so you should capture it to a file.

This issue should be resolved in v3.18.2.


pista: init at v0.1.5

Motivation for this change
Adds the pista prompt to nixpkgs.
Things done

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

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

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

This is my first contribution to nixpkgs, I hope everything is in order.

Result of nixpkgs-review pr 118914 at e8f96d47 run on x86_64-linux 1

1 package failed to build:

pista

1 suggestion:

warning: unused-argument
Unused argument: stdenv.
Near pkgs/tools/misc/pista/default.nix:1:3:
  |
1 | { stdenv, lib, rustPlatform, fetchFromGitHub, openssl, pkg-config }:
  |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

Made changes as requested.

Um.. https://github.com/NerdyPepper/pista/archive/v0.1.5.tar.gz appears to have disappeared and is now 404ing for me.

@risicle should be working now.

@ofborg eval
@ofborg build

lgtm. Please rebase and test.

Closing due to inactivity from author.


dev4

General question regarding the Timer class: Why we need that, instead of using a simple timer based on millis()? It only counts seconds, so there is no advantage in precision, but complexity and more flash resources.

Good question, I asked myself the same if timers should be used. Of course, alternatively a task could be utilized which periodically checks the sessions, though this would require to spawn a new thread which runs for the whole time and mostly just waits. It felt more "natural" to me to use an timer ISR for this case which also cannot be blocked by any other higher-priority task.
Of course, if desired, this will be changed/simpliefied as suggested.

Good question, I asked myself the same if timers should be used. Of course, alternatively a task could be utilized which periodically checks the sessions, though this would require to spawn a new thread which runs for the whole time and mostly just waits. It felt more "natural" to me to use an timer ISR for this case which also cannot be blocked by any other higher-priority task.

Ok, I understand. There are two ways in a RTOS system to do so:

Use the background task to check, no further task is necessary.
Use a task of course, which is most of the time in blocking state. Therefore only needs resources for the task context.

Don't destroy your real time behaviour by trying to do stuff in ISRs if not necessary. Especially in the case for just cyclic session timeout checking. Remember that the ISR duration has a negative influence on task scheduling.

Good question, I asked myself the same if timers should be used. Of course, alternatively a task could be utilized which periodically checks the sessions, though this would require to spawn a new thread which runs for the whole time and mostly just waits. It felt more "natural" to me to use an timer ISR for this case which also cannot be blocked by any other higher-priority task.

Ok, I understand. There are two ways in a RTOS system to do so:
* Use the background task to check, no further task is necessary.

* Use a task of course, which is most of the time in blocking state. Therefore only needs resources for the task context.

Don't destroy your real time behaviour by trying to do stuff in ISRs if not necessary. Especially in the case for just cyclic session timeout checking. Remember that the ISR duration has a negative influence on task scheduling.

Very good argument. I'm going to replace the Timer ISR with an FreeRTOS task.

Good question, I asked myself the same if timers should be used. Of course, alternatively a task could be utilized which periodically checks the sessions, though this would require to spawn a new thread which runs for the whole time and mostly just waits. It felt more "natural" to me to use an timer ISR for this case which also cannot be blocked by any other higher-priority task.

Ok, I understand. There are two ways in a RTOS system to do so:
* Use the background task to check, no further task is necessary.

* Use a task of course, which is most of the time in blocking state. Therefore only needs resources for the task context.

Don't destroy your real time behaviour by trying to do stuff in ISRs if not necessary. Especially in the case for just cyclic session timeout checking. Remember that the ISR duration has a negative influence on task scheduling.

Very good argument. I'm going to replace the Timer ISR with an FreeRTOS task.

Fixed with 767fe98

@luismoser99 There is still a finding open, from Yann.

Ok ... had some time before meal, so I was able to review. :-)

Great, thank you :)

@luismoser99 There is still a finding open, from Yann.

Which one do you mean?

@luismoser99 Please push your client changes too.
Change language attribute here: https://github.com/NewTec-GmbH/ZumoComSystem/blob/d2f639e5905648fe2ec1e8e882b7fcac4e9a2cba/Coding/client/public/index.html#L2

@luismoser99 Please push your client changes too.
Change language attribute here:
https://github.com/NewTec-GmbH/ZumoComSystem/blob/d2f639e5905648fe2ec1e8e882b7fcac4e9a2cba/Coding/client/public/index.html#L2

Fixed with ee714a1


add collector start script for window

PR for #3

@zone1511  Thanks for your contribution.
This project is used for plugin automation testing. All automated tests use the docker environment. For the moment, Windows startup scripts are not required.

@zone1511 I think more reasonable question is? Are you going to run this in a windows? And for what purposes?

I used to test the skywalk plugin in window and don’t want to start the collector. So the mock one will be good enough for me.
Sent from my iPhone

On 24 Mar 2018, at 8:48 AM, 吴晟 Wu Sheng<EMAIL_ADDRESS>wrote:
@zone1511 I think more reasonable question is? Are you going to run this in a windows? And for what purposes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Research Cardano transaction validation rules

Find out what are the rules by which Cardano transactions are validated. Obtain or produce a rigorous description of these rules, sufficiently precise to translate those rules into an arithmetic circuit.

This research appears to be done.


Implement User Creation

This implements the POST call /user in the API to create the user in the database.

Will resolve #116 on merge.


How can I present the dialog on top of ViewController?

Hi,
First of all thank you for this amazing library.
I want to present my MZFormSheetPresentationController in this way, so it starts a the top of the ViewController and it has transparent background. I have read the documentation in the README but I can't realize how to do it.

I would really appreciate some help. Thank you again!

I realized how to do it. Just added this two lines:
formSheetController.presentationController?.backgroundColor = UIColor.clear
formSheetController.presentationController?.portraitTopInset = 0.0


Lights that support color_temp can't be controlled properly

Lightener is not able (sometimes) to calculate its own brightness properly if any of the controlled lights has support for color_temp. When the issue happens:

The Lightener level is set to None.
The controlled light level also keeps set to None, although physically the light shows the proper brightness.

I was able to more easily confirm this with Zigbee2MQTT group lights but this doesn't happen always.

Although Lightener sends just brightness information to the turn_on service, it seems that sometimes ha sends also color information to the light, which maks things work. If color information is not sent, the reported issue happens.

I'm closing this for now since this this can't be fixed by Lightener. It's a HA core issue.


nodePackages: fix builds on x86_64-darwin

Description of changes
Follow-up to #193337 to fix several x86_64-darwin build failures due to missing xcrun/xcodebuild (see https://hydra.nixos.org/eval/1782541#tabs-now-fail)
I'm waiting on OfBorg to build these because I do not personally have access to any darwin systems. It probably also fixes aarch64-darwin errors, but those are additionally failing because the nodejs build had a transient failure (and the failure has been since cached - see #193331)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build bitwarden-cli epgstation joplin mastodon-bot theLoungePlugins.plugins.giphy

@ofborg build bitwarden-cli epgstation joplin mastodon-bot theLoungePlugins.plugins.giphy

Result of nixpkgs-review pr 193533 run on x86_64-darwin 1

1 package failed to build:

epgstation

4 packages built:

bitwarden-cli
joplin
mastodon-bot
theLoungePlugins.plugins.giphy

FYI, we have a patch for Node 14 to disable the use of xcbuild (no clue why it wasn't applied to any future versions).
As part of my work on buildNpmPackage, I was going to port it to newer versions, which would (hopefully) mean that it's not required for these packages. If you'd like to do it instead, let me know -- no need to duplicate work :)

Result of nixpkgs-review pr 193533 run on x86_64-darwin 1
1 package failed to build:

epgstation

4 packages built:

bitwarden-cli
joplin
mastodon-bot
theLoungePlugins.plugins.giphy

@veprbl, do you have logs for that epgstation failure? It works in OfBorg

FYI, we have a patch for Node 14 to disable the use of xcbuild (no clue why it wasn't applied to any future versions).
As part of my work on buildNpmPackage, I was going to port it to newer versions, which would (hopefully) mean that it's not required for these packages. If you'd like to do it instead, let me know -- no need to duplicate work :)

Ah, that would explain why it suddenly became required then! I was wondering but didn't really dive into it because I'm not too familiar with the Node.js ecosystem and just kinda wanted node2nix/nodePackages working again. I'll see if I can forward-port that patch real quick and test whether it fixes these builds as an alternative to adding xcbuild to stuff
(Also the buildNpmPackage stuff looks lovely and I can't wait for it to be available)

Result of nixpkgs-review pr 193533 run on x86_64-darwin 1

5 packages built:

bitwarden-cli
epgstation
joplin
mastodon-bot
theLoungePlugins.plugins.giphy

The failure was due to a known nix bug with sandboxing.

The failure was due to a known nix bug with sandboxing.

Just for posterity, logs/what bug? (I'd build myself but I can't at the moment and figure you have them on hand :)

Could either of you run nix build github:lilyinstarlight/nixpkgs/fix/nodepackages-darwin-v2#bitwarden-cli on darwin to see if nodejs and bitwarden-cli build with just the xcodebuild patch?
That branch is effectively @winterqt's suggestion above, but I don't have a Mac to test it on

The failure was due to a known nix bug with sandboxing.

Just for posterity, logs/what bug? (I'd build myself but I can't at the moment and figure you have them on hand :)

This one https://github.com/NixOS/nix/issues/2311

@winterqt, I tested out my branch in the macOS runner in GitHub Actions and it does look like just forward-porting that patch will work to remove the need for xcbuild in these packages
It also looks like the buildNodejs function patches xcode_emulation.py in postPatch and postInstall to deal with lack of Xcode, but not in a way that seems to work with any recent Node.js versions. So I could instead update that to patch it in a somewhat interpreter agnostic way -- it could just be somewhat fragile and version-specific patches like the one for v14 may be better long-term
Also, I'm assuming a PR to patch Node.js to avoid the need for xcbuild would have to go to staging, since touching nodejs makes quite a few rebuilds (~1k on x86_64-linux alone) even if it is a low-risk change?

It also looks like the buildNodejs function patches xcode_emulation.py in postPatch and postInstall to deal with lack of Xcode, but not in a way that seems to work with any recent Node.js versions.

It looks like the patches you talk about are ancient (introduced in 822abc49adc7b130e3bdc99bdfaf2503a6cf699d), so that doesn't surprise me. We can definitely drop them in favor of version-specific patches, IMO.

Also, I'm assuming a PR to patch Node.js to avoid the need for xcbuild would have to go to staging, since touching nodejs makes quite a few rebuilds (~1k on x86_64-linux alone) even if it is a low-risk change?

The high amount of rebuilds was caused by your nodePackages change, I presume. I think that's a candidate for staging then, yes. (@vcunat can confirm, though.)

Edit: I also did not see any reason that patch was dropped for the v16 update in #120008

Yeah, I assume it was just forgotten about. 😔

Also, I'm assuming a PR to patch Node.js to avoid the need for xcbuild would have to go to staging, since touching nodejs makes quite a few rebuilds (~1k on x86_64-linux alone) even if it is a low-risk change?

Yes, sounds like staging to me.  (Doesn't sound urgent, like security fixes.)

@lilyinstarlight Your nodePackages PR added, at most, 500 packages to this rebuild count -- any clue what the other 500+ packages that would be affected by the Node change would be? I'd really only think it would be nodePackages at the most (at least now, since it's not using Node 14), though we also have assorted web apps and such.

OfBorg lists all rebuilt packages if you click on details.

OfBorg lists all rebuilt packages if you click on "Details" on the "ofborg-eval" line.

Somehow I forgot this... thanks.

I've opened #193759 targeting staging with the change to patch nodejs as before and reverted some of the changes from this PR that added xcbuild in overrides


Proxy

Coverage increased (+0.1%) to 97.867% when pulling c27063b5c75910e6eca319922c2b586be0ec816c on proxy into 93527cc56c249a39b1a7aa896d4f06dcf8a9230a on v7.


Support XCM for Ledger

User requests XCM transfer for DOT on Polkadot

Resolved in https://github.com/Koniverse/SubWallet-Extension/issues/3458


https

https://github.com/SteveLTN/https-portal

https://github.com/ksmzn/ProbabilityDistributionsViewer/commit/ba24761a890e7d4f06f180316ca088d8210c4940


Thanks for sharing

Hey @scottyhq, this repo popped up in my feed and I thought it was pretty cool! I was inspired to build on the idea by throwing STAC and GitHub Actions into the mix. The result: a periodically updating map displaying a ~recent Sentinel-2 true color image that intersects a randomly selected National Park that updates every 6 hours.
https://github.com/bmcandr/stac-tile-map

Awesome, good to hear from you @bmcandr, those additions are great! Reminds me a bit of https://github.com/wildtreetech/sentinel2-bot but with the bonus of interactivity :)


Support links in dartdoc tooltip

It would be nice (like in the old DartEditor), if links in dart doc's (/// [foo]) viewed with F1 were clickable and navigated to the declaration.

You'd want it to navigate to the definition of the element, or display the dartdoc for that element in the tooltip window?

Personally I'd like it to navigate to the declaration of the element (so if it's a parameter, go to the parameter in the method signature, if it's a field, go to the field declaration in the class, etc). IIRC this was what the old DartEditor used to do.

imho would be best if it follows the rest of the functionality: f1 for doc, f3 for navigation.


Assembly version no longer being updated

VSTS Extension you are using
Version .NET Core Assemblies
Where are you running it?
VSTS
Version of Extension/Task
1.25.4
Expected behavior and actual behavior
Expecting the resulting assembly (dll) to have the correct version.  Actual behavior is it still has the default <IP_ADDRESS> version.
Steps to reproduce the problem
Run my build
This worked in version 1.24.19.  And, to be honest, I'm not sure how my build configuration was automatically upgraded to 1.25.4.  I guess that's something that just happens automatically?
Thanks,
Kevin

Updates to minor versions automatically get rolled out.
I'll have a look at this a bit later, I think I know what the problem could be so I'll just double check.
Can you look under Advanced in the task and check that a value is in the FileName Pattern? It should be AssemblyInfo.* or AssemblyInfo.cs or something similar.

Filename Pattern:
.csproj
This is ASP.NET Core with the csproj file structure.
Thanks for checking!

That's what I get for skim reading, I assumed it was the normal .net versioning task.
The solution for that is to specify the field you want to modify to be AssemblyVersion. There was a change recently to default to Version instead as that populates a different field and filters through into nuget packages.

That did the trick.
Previously, my "The version field to update" was blank.  I updated it to "AssemblyVersion" and that corrected the problem.
Thanks!


Allow installing an interpreter directly inside a project dir

Cargo builds artifacts in a target directory which is unique per project. This allows each projects to be self-contained.
Python does not offer this functionality; packages are installed (using pip) alongside the interpreter, or "globally" for the user (typically inside ~/.local/).
It would be useful to be able to isolate interpreters per project, or at least installed packages.
Maybe there's an environment variable to could be set that would install packages (with pip) inside the project directory.

Or maybe virtualenv is enough for this. Maybe it could be included automatically?


External-lb integration

Nice to see the extarnal-lb keeps going. I'm wondering how the external-lb will be integrated in rancher, can a external-lb included in a stack like the internal-lb? or is it totally separate like the external-dns thing?

@hwinkel I'm going to close the issues in this repo. Can you ask in rancher repo? We direct all issues into Rancher so that we can try to answer them.


Modifier that serves files from a local directory and skips the roundtrip

Thanks for the comments I'll address in another pr
On Mon, Nov 21, 2016, 10:54 AM cpasillas<EMAIL_ADDRESS>wrote:

@cpasillas commented on this pull request.
In static/static_file_modifier.go
https://github.com/google/martian/pull/145#pullrequestreview-9517332:

+// local to Martian.
+package static

+import (

"encoding/json"
"mime"
"net/http"
"os"
"path"
"path/filepath"

"github.com/google/martian"
"github.com/google/martian/parse"
+)

+type staticModifier struct {
Most other modifiers are named simply 'Modifier' or 'modifier'. Do we want
to stay consistent with that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/martian/pull/145#pullrequestreview-9517332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADI-bBssGhts7TPjqeDnAXHrJnexPwaks5rAejVgaJpZM4K34R3
.


wxGTK31: 3.1.4 -> 3.1.5

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

this didn't have to go into staging
./maintainers/scripts/rebuild-amount.sh  HEAD~3
Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
    156 x86_64-linux

Originally it triggered red flags about many builds on master.


OPERA-SDSVnV-9_1

Reference:
https://cae-testrail.jpl.nasa.gov/testrail/index.php?/tests/view/3351557&group_by=cases:section_id&group_order=asc&group_id=69570

To Do:
o Steps 9 and 11: must have a process to compare the result of the query to a reference output, because simply checking manually is error prone. For example, you can compare versus the same query executed against CMR, or capture the output in files and diff the current and a previous file
o To be more true to the requirement that needs to be tested, change steps 8 and 13 to query only the latest available data, for example for the last 1, 2 or 3 days

https://cae-testrail.jpl.nasa.gov/testrail/index.php?/tests/view/3351557&group_by=cases:section_id&group_id=69570&group_order=asc

o Section 2 (query for HLSS30) has both the query for the last 60 minutes of available data, and data for some time interval in the past. Section 3 (query for HLSL30) only has the query for the last 60 minutes - can you please add the query for the some interval in the past?
o Also, in all cases, how do we make sure that the results are correct? At the very least we should compare the number of results from querying CMR and executing the script.

Updated:
https://cae-testrail.jpl.nasa.gov/testrail/index.php?/tests/view/3351557

For now, "Response should match", will be implemented by screen. capture and highlighting the number of files.

Updated as suggested:
https://cae-testrail.jpl.nasa.gov/testrail/index.php?/tests/view/3351557

Thanks for the corrections, closing.


Adding the GSAP-Animation for the website

I thought of adding the best animation to the website by using the GSAP library. This can be used to enhance the user experience and make the user visit the website many times. So I would like to work on this. Can you please assign this to me under @GSSOC'24 @khushi-joshi-05

Hey, I am a frontend developer who creates stunning and modern websites.
I completed the internship as a frontend developer.
I create websites with HTML, CSS, JS, and React, and I use JS libraries for animation and smooth scrolling.
The following are the works where I used lgsap animation and locomotive js :
https://exoape-clone-parth.netlify.app/
https://ochi-clone-parth.netlify.app/


Update reverts theme back to default Sublime theme

Hi Ihor,
Today's update caused Sublime to revert back to the default Sublime theme again (Default.sublime-theme).
This has happened a few times with past updates as well. Is it a Sublime bug?
Your Environment

boxy version: 3.1.1
Environment name and version: Sublime Text 3, Build 3114
Operating System and version: Windows 10, 64-bit, Version 1511, Build 10586.494

Hi! This is the cost of using theme addons such as Boxy Theme Addon - Font Face & Boxy Theme Addon - Mono File Icons because they are hacks. In 3.1.0 I added some project structure changes that caused this bug, fixed in 3.1.1. I hope this behavior will not happen again. However I'll add theme configurator in the next release, it will enable activating theme in easier way than now.


Use precondition instead of fatalError in DateInterval initializer

Comment of the function says:

/// - precondition: end >= start

but it actually uses if -> fatalError instead of precondition,
Other functions of DateInterval use precondition-s, only this one uses 'fatalError', probably makes sense to change it as well.

@swift-ci please test

LGTM
@swift-ci please test and merge

This is shared with overlay code; we should attempt to keep them in sync.

@parkera Should I make the same change here https://github.com/apple/swift/blob/4654a230fb67fc8ba34348c1f5f3758292223260/stdlib/public/SDK/Foundation/DateInterval.swift#L58  ?

Yup, that would be great.

@parkera here you are https://github.com/apple/swift/pull/12743


Snapshot detail page grid error

Describe the bug
If there is something like HTML tag in the content, a blank line is generated.
내용에 HTML 같은 것이 있으면 빈 줄이 생겨납니다.
To Reproduce
Steps to reproduce the behavior:

Import finefood.sample.txt with colon delimiter.
Click the new generated I.DS.
Click Create dataflow with this dataset.
Edit rules.
Drop column3 and all after.
Click "Snapshot" button
Click "Done" (make a CSV snapshot)
Click the new generated snapshot.
Scroll down and you'll see the empty lines (in the middle)

Expected behavior
All contents should be shown clearly no matter what the column value is.
Screenshots

Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: 68.0.3440.106

Additional context
@sang-hee-lee told me that this is because of HTML tags in the contents.
@ksparknot seems to have some idea about this issue.

Apply METATRON-1560 issue


limit the max value of cluster.max_shards_per_node to avoid int overflow

Signed-off-by: kkewwei<EMAIL_ADDRESS>
Description
Limit the max value of cluster.max_shards_per_node to avoid int overflow. We can't reach  1_500_000 in the current opensearch struct.
Related Issues
Resolves #13907
Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@shwetathareja Any issues with this? This is a new limit, so anyone setting it higher than 1.5M will see a failure in upgrade.

a flaky test

AwarenessAttributeDecommissionIT.testConcurrentDecommissionAction #12197

@dblock @shwetathareja please have another look.

❌ Gradle check result for b2cf752: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

ReindexBasicTests.testMultipleSources #13913

@shwetathareja  please see again.

@kkewwei please fix the conflict in ChangeLog.md


Python: "No refactorings available" / "No code actions"

Type: Bug

Create a new folder
Create a file called testvscode.py with the following content

def f():
    print("Ohh no")

f()

Open the folder in VS Code
Right click somewhere in the text Ohh no. Choose Refactor... from the popup menu. The message is: No refactorings available.
I think it should allow you to at least extract the text as a variable.

If I use the keyboard shortcut to extract text to variable I get this error:

I have tried using not only the release version of the Python/Pylance plugins, but the pre-release versions as well.
The default Language Server for Python was default, I have set it explicitly to Pylance now, without success:

I don't see any other errors and don't know how to debug this issue further.

VS Code version: Code 1.92.2 (fee1edb8d6d72a0ddff41e5f71a671c23ed924b9, 2024-08-14T17:29:30.058Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.73GB (19.58GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

EditorConfig
Edi
0.16.4

vscode-edit-csv
jan
0.9.2

intellij-idea-keybindings
k--
1.7.2

debugpy
ms-
2024.11.2024081401

python
ms-
2024.12.3

vscode-pylance
ms-
2024.8.1

powershell
ms-
2024.2.2

vscode-sailpoint-identitynow
yan
1.3.2

/extPython


[SPARK-16550] [core] Certain classes fail to deserialize in block manager replication

What changes were proposed in this pull request?
This builds on @JoshRosen 's original patch to also fix block replication for repl-defined classes. This is done by erasing the classTag when using the default serializer, since it's not needed in that case, and the classTag was failing to deserialize on the remote end.
The proper fix is actually to use the right classloader when deserializing the classtags, but that is a much more invasive change for 2.0.
How was this patch tested?
End-to-end test in ReplSuite (also more tests in DistributedSuite from the original patch).

Test build #62698 has started for PR 14311 at commit c67fbdb.

Test build #62698 has finished for PR 14311 at commit c67fbdb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 test(\"replicating blocks of object with class defined in repl\")
        |case class Foo(i: Int)

Merged build finished. Test FAILed.

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

@ericl, these test failures appear legitimate.

Weird, both core/test-only *DistributedSuite* and repl/test-only *ReplSuite* pass locally for me (jdk-8). I'll look into it tomorrow when I have access to my desktop.

This does appear to be a Java-7 issue.

Test build #62906 has started for PR 14311 at commit 7cccb39.

Ok weird, I can't reproduce locally any more, even after many tries. I wonder if it's just very rarely flaky, though that seems unlikely.

Test build #62906 has finished for PR 14311 at commit 7cccb39.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Looks like the second jenkins run failed a slightly different set of the tests than the first.

Test build #62981 has started for PR 14311 at commit 7543c4a.

Test build #62981 has finished for PR 14311 at commit 7543c4a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #3204 has started for PR 14311 at commit 7543c4a.

Test build #3204 has finished for PR 14311 at commit 7543c4a.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

We should fix this one and move on ..

Test build #63551 has started for PR 14311 at commit 9435f26.

Test build #63551 has finished for PR 14311 at commit 9435f26.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ShuffleIndexInformation
public class ShuffleIndexRecord
class SparkConf(loadDefaults: Boolean) extends Cloneable with Logging with Serializable
case class MonotonicallyIncreasingID() extends LeafExpression with Nondeterministic
case class SparkPartitionID() extends LeafExpression with Nondeterministic
case class AggregateExpression(
case class Least(children: Seq[Expression]) extends Expression
case class Greatest(children: Seq[Expression]) extends Expression
case class CurrentDatabase() extends LeafExpression with Unevaluable
class GenericInternalRow(val values: Array[Any]) extends BaseGenericInternalRow
class AbstractScalaRowIterator[T] extends Iterator[T]
case class CachedData(plan: LogicalPlan, cachedRepresentation: InMemoryRelation)
class CacheManager extends Logging
trait DataSourceScanExec extends LeafExecNode with CodegenSupport
case class RowDataSourceScanExec(
case class FileSourceScanExec(
case class ExternalRDD[T](
case class ExternalRDDScanExec[T](
case class LogicalRDD(
case class RDDScanExec(
trait FileRelation
case class LocalTableScanExec(
abstract class RowIterator
trait LeafExecNode extends SparkPlan
trait UnaryExecNode extends SparkPlan
trait BinaryExecNode extends SparkPlan
case class PlanLater(plan: LogicalPlan) extends LeafExecNode
abstract class SparkStrategies extends QueryPlanner[SparkPlan]
class UnsafeRowSerializer(
class TypedSumDouble[IN](val f: IN => Double) extends Aggregator[IN, Double, Double]
class TypedSumLong[IN](val f: IN => Long) extends Aggregator[IN, Long, Long]
class TypedCount[IN](val f: IN => Any) extends Aggregator[IN, Long, Long]
class TypedAverage[IN](val f: IN => Double) extends Aggregator[IN, (Double, Long), Double]
case class ScalaUDAF(
case class InMemoryRelation(
case class InMemoryTableScanExec(
trait RunnableCommand extends LogicalPlan with logical.Command
case class ExecutedCommandExec(cmd: RunnableCommand) extends SparkPlan
case class AlterTableRecoverPartitionsCommand(
case class DataSourceAnalysis(conf: CatalystConf) extends Rule[LogicalPlan]
class FindDataSourceTable(sparkSession: SparkSession) extends Rule[LogicalPlan]
case class InsertIntoDataSourceCommand(
case class InsertIntoHadoopFsRelationCommand(
case class PartitionDirectory(values: InternalRow, path: Path)
case class PartitionSpec(
case class CreateTable(tableDesc: CatalogTable, mode: SaveMode, query: Option[LogicalPlan])
case class JDBCPartition(whereClause: String, idx: Int) extends Partition
class ResolveDataSource(sparkSession: SparkSession) extends Rule[LogicalPlan]
case class PreprocessDDL(conf: SQLConf) extends Rule[LogicalPlan]
case class PreprocessTableInsertion(conf: SQLConf) extends Rule[LogicalPlan]
case class PreWriteCheck(conf: SQLConf, catalog: SessionCatalog)
 case class DebugExec(child: SparkPlan) extends UnaryExecNode with CodegenSupport
class ExchangeCoordinator(
case class MapPartitionsRWrapper(
class IncrementalExecution(
class ExecutionPage(parent: SQLTab) extends WebUIPage(\"execution\") with Logging
class SQLHistoryListenerFactory extends SparkHistoryListenerFactory
class SQLListener(conf: SparkConf) extends SparkListener with Logging
class SQLHistoryListener(conf: SparkConf, sparkUI: SparkUI)
class SQLTab(val listener: SQLListener, sparkUI: SparkUI)
case class SparkPlanGraph(
 implicit class SchemaAttribute(f: StructField)

Merged build finished. Test FAILed.

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

Test build #63558 has started for PR 14311 at commit 3fe7b54.

Test build #63558 has finished for PR 14311 at commit 3fe7b54.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Ok interesting, seems the repl fix I attempted breaks DistributedSuite in jenkins.

Test build #63699 has started for PR 14311 at commit a6c9db4.

I've split the part causing the test flakes into a separate sub-task so we can get the main patch merged. https://issues.apache.org/jira/browse/SPARK-17042
@JoshRosen now this is basically your original patch.

Test build #63699 has finished for PR 14311 at commit a6c9db4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Hmm, weird. Looks like replication tests are still failing. I can help investigate later.

Test build #63871 has started for PR 14311 at commit 94682a2.

Test build #63871 has finished for PR 14311 at commit 94682a2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

@JoshRosen could I get ssh access to the jenkins machines to try reproducing the flakiness there?

Test build #64013 has started for PR 14311 at commit b480ec6.

Thanks, attempting to reproduce this on jenkins....

Test build #64013 has finished for PR 14311 at commit b480ec6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

On jenkins, it seems sometimes one block manager will fail to register. The only clue from the logs is
16/08/18 18:54:25.796 netty-rpc-connection-0 INFO TransportClientFactory: Successfully created connection to /<IP_ADDRESS>:44000 after 1534 ms (0 ms spent in bootstraps)

1534ms is much longer than the usual

Test build #64235 has started for PR 14311 at commit 8ed8fb6.

Test build #64235 has finished for PR 14311 at commit 8ed8fb6.

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

Merged build finished. Test PASSed.

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

Merging in master/2.0.

@rxin  @ericl
This PR may cause the following code to throw an exception
private def getRemoteValues(blockId: BlockId): Option[BlockResult] = {
    getRemoteBytes(blockId).map { data =>
      val values =
        serializerManager.dataDeserializeStream(blockId, data.toInputStream(dispose = true))
      new BlockResult(values, DataReadMethod.Network, data.size)
    }


format of dataset

It seems that the format of the dataset you provided is wrong

Can you post a screenshot of error? And describe which dataset you are using, what running script you are using.
Otherwise I do not know what could be the reason for the problem you are facing, because these datasets are what I used previously, and other people use this repo haven't reported any similar problem with datasets, so I have no clue now.

The zip file datasets I provided are already pre-processed, you don't need to process them any further.

The zip file datasets I provided are already pre-processed, you don't need to process them any further.

Thank you very much for your reply！Maybe I misunderstand, I thought the format of the zip file is that each image corresponds to a text file. Thanks again for your reply!

You're welcome, that dataset_tool.py is used for creating your own dataset.


RSS Feed / OPML reader and article parser

Submitted to llama-index and tested.  PR here also in response to suggestion by @jerryjliu.

awesome thanks! will review soon


remove on create initial metadata

Signed-off-by: Pengyuan Bian<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

We don't need to actually. There is already a option in GrpcService that adds the initial metadata. https://github.com/envoyproxy/envoy/blob/9186ebf374b1bd7d7c65ed1cec748377f88ec0a7/api/envoy/api/v2/core/grpc_service.proto#L225

While the initial metadata can indeed be set in the GrpcService proto, you need to modify proto for each request and you're mixing service and per-stream metadata in a weird way, IMHO.
I think we should still add the initial metadata to the calls, like @jplevyak mentioned, and as we discussed in the past. What do you think?

Yeah that makes sense to me. John talked to me offline and he is going to work on the PR to add that param. He mentioned the other reason though that GrpcService proto is Envoy specific and we want to make ABI proxy neutral.


SDK Does not work when location services are not present

SDK requires location services on the device. Unfortunately many devices have this feature either disabled or even not provided in ROM (Chinese Devices).
Any chance to disable this requirement?

Hi, thanks for reaching out.  Correct, SumUp's app and SDKs do indeed require location services for security reasons.  We cannot disable this requirement unfortunately.  Sorry for the inconvenience.

Is there a possibility to use location over WIFI? Because I am implementing your SDK on an App using Android things OS on a raspberry Pi.
Can you maybe make it possilbe to fixate a location (like in my case in a fix store) or get location via WIFI?
I am unfortunately totally stuck here and absolutely depending on your help
Thanks

Hi there.  Can you please email<EMAIL_ADDRESS>with your Merchant Account details and further details about how you're looking to use SumUp?

@vladaman I understand.  Can you please email<EMAIL_ADDRESS>so that we can discuss your use further?

What is the result (for everyone ELSE out here looking at Android based POS system)?

@MarcusWolschon: I tried an usb gps, but it didn't work for me, also the gps mocking didn't work out. If someone succeeds or if sumup will enable the option without gps, it would be awesome for all our businesses I guess!

Hi @MarcusWolschon @anizeani .  Appreciate your feedback and very much understand the perspective.  Currently the geolocation must be passed to the SumUp SDK / App upon performing a transaction for security reasons.  Thanks


New command: m365 graph directoryextension add

Usage
m365 graph directoryextension add
Description
Creates a new directory extension
Options

Option
Description

-n, --name <name>
The name of the directory extension

--appId [appId]
Application (client) ID of the Entra application where the directory extension is registered. Specify either appId, appObjectId or appName, but not multiple.

--appObjectId [appObjectId]
Object ID of the Entra application where the directory extension is registered. Specify either appId, appObjectId or appName, but not multiple.

--appName [appName]
The name of Entra application where the directory extension is registered. Specify either appId, appObjectId or appName, but not multiple.

--dataType <dataType>
The data type of the value the extension property can hold. Possible values are: Binary, Boolean, DateTime, Integer, LargeInteger and String.

targetObjects <targetObjects>
Comma-separated list of Microsoft Graph resources that can use the extension. Possible values are: User, Group, Application, AdministrativeUnit, Device and Organization.

--isMultiValued
Defines the directory extension as a multi-valued property

Examples
Create a new directory extension of string type defined for user resource.
m365 graph directoryextension add --name gitHubWorkAccountName --appName ContosoApp --targetObjects User --dataType String

Create a new multi-valued directory extension of integer type defined for device and application resource
m365 graph directoryextension add --name departmentIds --appId 1caf7dcd-7e83-4c3a-94f7-932a1299c844 --targetObjects 'Application,Device' --dataType Integer --isMultiValued

Default properties
No response
Additional Info
Directory extensions allow to add custom data to user, group, administrative unit, application, device and organization resources inside the Microsoft Graph.

Nice spec @MartinM85, the only thing I would change is the description. Defines the directory extension doesn't say much in my opinion. Let's try something like Adds a new directory extension or Creates a new directory extension.
Are you willing to implement this? Or should we open it up?

I'd like to remind you that we require all new commands to be using a ZOD scheme. You can find some examples in login, spo site get or: #6214, #6216, #6303

@milanholemans  Description upgraded
Regarding to ZOD, should I use a ZOD scheme for commands that are already in pull requests?

Actually, we are asking that all new commands use the ZOD scheme indeed.

I will take this ticket


Preserve group keys as indices when groupby(...).agg(...).

We should preserve group keys as indices of the result DataFrame when groupby(...).agg(...).

Codecov Report

Merging #240 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #240      +/-   ##
=========================================
- Coverage   91.63%   91.6%   -0.03%
=========================================
  Files          35      35
  Lines        3023    3026       +3
=========================================
+ Hits         2770    2772       +2
- Misses        253     254       +1

Impacted Files
Coverage Δ

databricks/koalas/tests/test_groupby.py
100% <100%> (ø)
:arrow_up:

databricks/koalas/groupby.py
97.84% <100%> (-0.03%)
:arrow_down:

databricks/koalas/__init__.py
88.88% <0%> (-3.71%)
:arrow_down:

Continue to review full report at Codecov.

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


Visio Standard worked and then became not activated

We have several Visio 2016 standard installs.  We installed with the deployment tool and the provided Visio Standard 2016
VisioStdXVolume NY48V-PPYYH-3F4PX-XJRKJ-W4423 key above.  This worked without issue.  Then several people all of a sudden are getting activation failed now.  Reinstalled and same results failed activation.  We are using the shared Office365 install.  Any help?

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

ID: 1e6c0641-503d-7959-2afb-839821cc792f
Version Independent ID: 046c52d9-4fbe-4fe7-0778-5c1d4138f69e
Content: Use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016
Content Source: DeployOffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

I had the same issue with Visio Pro 2016. Install worked a month ago, and Visio was activated. I tried to use it today and it says it's not.

This continues to be a problem exactly as reported previously. Unable to use our volume licensed Visio Professional 2016 product alongside Office 365 installed apps.  When will we have a working solution? Thank  you!

Can the device see/contact the KMS Server? You can use the ospp.vbs script to check that. If you continue to have problems, we recommend that you contact Support as they are the resource best equipped to do this sort of troubleshooting.

I figured it out in my case, and it was about seeing the server.
I had turned off DHCP, so I was no longer getting the DNS suffix that was required to resolve the server on my machine. I manually added my org's suffix as “DNS suffix for this connection” and restarted. Then I could resolve the server and Visio re-authorized.

@jacktose -- glad you were able to get your issue resolved.


Many Identical Threads found in dump of Visual Studio

Hi
I was examining a dump of Visual Studio from a customer who was running out of memory
In the dump under WinDbg, there are 13 identical stacks
This looks suspiciously inefficient:
1cf00000 1d03a000   System_Reactive   (no symbols)
    Loaded symbol image file: System.Reactive.dll
    Image path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions\Xamarin.VisualStudio\System.Reactive.dll
    Image name: System.Reactive.dll
    Browse all global symbols  functions  data
    Using CLR debugging support for all symbols
    Has CLR image header, track-debug-data flag not set
    Image was built with /Brepro flag.
    Timestamp:        87C43E2F (This is a reproducible build file hash, not a timestamp)
    CheckSum:         00140CEB
    ImageSize:        0013A000
    File version:     <IP_ADDRESS>399
    Product version:  <IP_ADDRESS>
    File flags:       0 (Mask 3F)
    File OS:          4 Unknown Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      .NET Foundation and Contributors
        ProductName:      System.Reactive (net46)
        InternalName:     System.Reactive.dll
        OriginalFilename: System.Reactive.dll
        ProductVersion:   4.3.2+67d891dfbf
        FileVersion:      <IP_ADDRESS>399
        FileDescription:  System.Reactive
        LegalCopyright:   Copyright (c) .NET Foundation and Contributors.
        Comments:         Reactive Extensions (Rx) for .NET
00 ntdll!NtWaitForMultipleObjects
01 KERNELBASE!WaitForMultipleObjectsEx
02 clr!WaitForMultipleObjectsEx_SO_TOLERANT
03 clr!Thread::DoAppropriateAptStateWait
04 clr!Thread::DoAppropriateWaitWorker
05 clr!Thread::DoAppropriateWait
06 clr!SOIntolerantTransitionHandler::SetNoException
07 clr!CLREventBase::WaitEx
08 clr!CLREventBase::Wait
09 clr!Thread::Wait
0a clr!Thread::Block
0b clr!SyncBlock::Wait
0c clr!ObjHeader::Wait
0d clr!Object::Wait
0e clr!ObjectNative::WaitTimeout
0f mscorlib_ni!System.Threading.Monitor.Wait(System.Object, Int32, Boolean)
10 System_Reactive!System.Reactive.ObserveOnObserverLongRunning`1[[System.__Canon, mscorlib]].Drain()
11 System_Reactive!System.Reactive.ObserveOnObserverLongRunning`1+<>c[[System.__Canon, mscorlib]].<.cctor>b__17_0(System.Reactive.ObserveOnObserverLongRunning`1<System.__Canon>, System.Reactive.Disposables.ICancelable)
12 System_Reactive!System.Reactive.Concurrency.NewThreadScheduler+<>c__DisplayClass7_0`1[[System.__Canon, mscorlib]].<ScheduleLongRunning>b__0()
13 mscorlib_ni!System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
14 mscorlib_ni!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
15 mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
16 mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
17 mscorlib_ni!System.Threading.ThreadHelper.ThreadStart()
18 clr!CallDescrWorkerInternal
19 clr!CallDescrWorkerWithHandler
1a clr!MethodDescCallSite::CallTargetWorker
1b clr!MethodDescCallSite::Call
1c clr!ThreadNative::KickOffThread_Worker
1d clr!ManagedThreadBase_DispatchInner
1e clr!ManagedThreadBase_DispatchMiddle::__l16::Cleanup::{dtor}
1f clr!ManagedThreadBase_DispatchMiddle
20 clr!ManagedThreadBase_DispatchOuter
21 clr!ManagedThreadBase_FullTransitionWithAD
22 clr!ThreadNative::KickOffThread
23 clr!Thread::intermediateThreadProc
24 kernel32!BaseThreadInitThunk
25 ntdll!__RtlUserThreadStart
26 ntdll!_RtlUserThreadStart

If the code using Rx (Xamarin.VisualStudio?) is using NewThreadScheduler (see frame 12), this behavior is to be expected. Question is if they can use another scheduler in this particular case. Either way, it's not an Rx bug. The code asks for a new thread and gets a new thread.

Closing as by design but linking https://github.com/dotnet/reactive/issues/266 where we track potential improvements to diagnostics.


fixed sokol_debugtext.h for SOKOL_WGPU backend

Just a minor typo and some code that probably didn't get updated during a past refactoring session.

Many thanks! I'll merge the PR, but please keep in mind that the sokol_gfx.h WebGPU backend hasn't been kept uptodate with the latest WebGPU API changes and probably won't currently work. My plan is to delay this until the API has stabilized (so probably "pretty soon now").

Many thanks! I'll merge the PR, but please keep in mind that the sokol_gfx.h WebGPU backend hasn't been kept uptodate with the latest WebGPU API changes and probably won't currently work. My plan is to delay this until the API has stabilized (so probably "pretty soon now").


Easymon catches any request starting with /up even when it shouldn't

I have a site where the following path is being picked up by easymon:
/uppababy-2018-cruz-stroller-emmett-green.html
In the site, this path is a 404, which should then get picked up by our error controller and redirected to a configured destination but it seems like easymon is picking it up before that.
{"method":"GET","path":"/up/pababy-2018-cruz-stroller-emmett-green.html","format":"html","controller":"easymon/checks","action":"show","status":404,"duration":0.92,"view":0.49,"ip":"<IP_ADDRESS>","route":"easymon/checks#show","request_id":"7ad5a34f61be33b45a268c486ccd7e0d","source":"app-7f76cd6859-8z497","tags":["request"],"@timestamp":"2019-05-17T14:37:57.568Z","@version":"1"}

It is unclear how the path is changing from /uppababy-2018-cruz-stroller-emmett-green.html to /up/pababy-2018-cruz-stroller-emmett-green.htm

Hi Jessie!
The quickest workaround here is to change where Easymon is mounted.
Easymon doesn't care about where it's mounted, we picked /up because it didn't conflict with anything we were doing.  So you could easily do something like this in your routes.rb:
mount Easymon::Engine => '/health'
# or
mount Easymon::Engine => '/upz'

I don't have time to dig into this, but feel free to investigate and submit a PR if you solve your issue!
I'm closing this, feel free to re-open with a PR or new info!

In case anyone ends up here:
This seems to be fixed in Rails 5.2 (see https://github.com/rails/rails/pull/35162)
For version prior to 5.2, this is easily worked around by using a constraint:
mount Easymon::Engine => '/up', constraints: { path: /\/up(?:\/([a-zA-Z]*))?$/ }


Add support for non-Node worker environments

What would you like to see in the library?
Support for non-NodeJS runtimes like Cloudflare workers. Currently this library fails to compile for Cloudflare when using Nitro framework. In other workers it could just fail in runtime.
Describe alternatives you've considered
It works to use this library only for Typescript types and send requests the other way:
import type { protos } from '@googlemaps/places'

const data = await $fetch<protos.google.maps.places.v1.IAutocompletePlacesResponse>('https://places.googleapis.com/v1/places:autocomplete', {
  method: 'POST',
  body: {
    input,
    languageCode: language,
    sessionToken,
    locationBias: { rectangle: {
      low: { latitude: businessArea.minLat, longitude: businessArea.minLng },
      high: { latitude: businessArea.maxLat, longitude: businessArea.maxLng },
    } },
  } as protos.google.maps.places.v1.IAutocompletePlacesRequest,
  headers: { 'X-Goog-Api-Key': googleMapsApiKey },
})

Please do this