Enable/Disable Zoom

Hi,
I saw that you removed EventCapture https://github.com/rrag/react-stockcharts/blob/78bbf30e4e29580aceedbc0e6fe0c8829b95b88b/docs/md/CHANGE-LOG.md
Is there any way now to enable/disable the zoom on demand? The problem being when you scroll down a page and happen to be on top of a chart then it starts zooming instead of scrolling. We want to have a button to enable chart interaction instead of having it by default.
Thanks, we <3 your lib :)

it is not possible to disable pan/zoom in 0.6-beta
It has to be added. If you are interested in doing a PR, I can guide you on what needs to be done.
Closing - Duplicate of https://github.com/rrag/react-stockcharts/issues/161

Yep, we are interested in helping. Please let me know the details of what you have in mind for the implementation (new props? HOC? new component?)
thanks

Great here is what I am thinking
in ChartCanvas.jsx
class ChartCanvas extends Component {
	...
	...
	render() {
		...
		...
		<EventCapture
-			mouseMove={interaction}
+			mouseMove={!disableMouseMoveEvent && interaction}
-			zoom={interaction}
+			zoom={!disableMouseMoveEvent && interaction}
-			pan={interaction && !drawMode}
+			pan={!disableMouseMoveEvent && interaction && !drawMode}

			width={dimensions.width}
			height={dimensions.height}
			chartConfig={chartConfig}
			xScale={xScale}
		...
	}
}

ChartCanvas.propTypes = {
	width: PropTypes.number.isRequired,
	height: PropTypes.number.isRequired,
	...
	...
+	disableMouseMoveEvent: PropTypes.bool.isRequired,
+	disablePanEvent: PropTypes.bool.isRequired,
+	disableZoomEvent: PropTypes.bool.isRequired,
	onSelect: PropTypes.func,
};

ChartCanvas.defaultProps = {
	...
	defaultFocus: true,
	onLoadMore: noop,
	onSelect: noop,
	// ratio: 2,
+	disableMouseMoveEvent: false,
+	disablePanEvent: false,
+	disableZoomEvent: false,
};

and then when you use it in your component

handleSelect() {
	this.setState({ focus: true })
}

render() {
	...
	var focus = this.state.focus;
	...
	return (<ChartCanvas
		disableMouseMoveEvent={focus}
		disablePanEvent={focus}
		onSelect={this.handleSelect}
		...
		...>
		...
		...
	</ChartCanvas>

Refer CONTRIBUTING.md on how you can test your changes
Change any of the charts in https://github.com/rrag/react-stockcharts/tree/master/docs/lib/charts to test your changes.
I always use
https://github.com/rrag/react-stockcharts/blob/master/docs/lib/charts/CandleStickChartWithEdge.jsx
to play with my experiments before it becomes an example on its own

I tried to add the values from https://github.com/rrag/react-stockcharts/blob/master/docs/md/ZOOM-AND-PAN.md in the ChartCanvas. It works on chart display but not in the Y-axis label. How can I fully disable the mouse and scroll events in both chart and the label section?
My result is the same if we add the following props in ChartCanvas in https://codesandbox.io/s/github/rrag/react-stockcharts-examples2/tree/master/examples/CandleStickChartWithCompare
return (
	<ChartCanvas height={400}
		mouseMoveEvent={false}
		panEvent={false}
		zoomEvent={false}
		clamp={false}
        ...

Actual result when I drag the Y-axis.

Okay, I think this is the solution im looking for. https://github.com/rrag/react-stockcharts/pull/164#issuecomment-259113522

look at zoomEnabled prop in XAxis, YAxis in CandleStickChartWithZoomPan.jsx


[Question] Does code mirror support different font size?

Sorry if duplicate. If so please provide some links and close.
Suppose I have following block:
i want this *BIG* and this -small-

in the above block, *BIG* would have bigger font size and -small- would have smaller font size. Is it doable with codemirror ?

Yes, see http://codemirror.net/demo/variableheight.html

Thanks, what a bout both different height and color for certain block of text ?


adapt to GHC 8.8.1 (plus administrative changes for a new release)

Fixes https://github.com/sol/hpack/issues/371.

rebased and pushed to master.  Thanks for the PR.


VLAZ: Watch techaid71.xyz

VLAZ requests the watch of the watch_keyword techaid71\.xyz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

techaid71\.xyz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Out-of-date description and screenshot of Azure Portal

Regarding the section "Acquire Azure Active Directory GUID ID" https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-nps-extension-rdg#acquire-azure-active-directory-guid-id
The written steps and screenshot discuss a Directory ID which is not shown in the actual Azure portal. The actual Azure portal shows a Tenant ID.

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

ID: 61df48bb-a963-b1f0-8f64-b55d0bd6904c
Version Independent ID: 677de59f-a222-8905-11c0-a3ac619d8b56
Content: Integrate RDG with Azure MFA NPS extension - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension-rdg.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@gorillatechnology Thank you for pointing it out. We will have this reviewed and engage the content authors as needed.

@gorillatechnology  Directory ID and tenant ID both refer to the same thing . Its the Unique guid which refers to the Azure AD instance. I will request the author for updating the screenshot as I do not have permissions to update screenshots in the repo.

@iainfoulds Could you please help update the screenshot on this document as requested by the customer because currently the term Tenant ID is used in the portal instead of Directory ID as it was earlier ?

Thanks. I can see this has been updated.


Landing Page Repair

Expected behavior
Provided links bring the user to the desired information.
Actual behavior
All the links seem to point to orientdb.com/ which in turn has a message referring the user back to orientdb.org ... even the 'Contact Us' link!
Additional context
I brought some folks to the website because I had remembered orientdb as a potential graph database candidate.  Needless to say it didn't go well.  First impressions matter.  The longer you delay fixing it, more and more potential clients visit and leave unimpressed.

Hi @MikeB2019x we are working on that. It will take some time to resolve some obstacles but we are completely aware of the problem.

That would be great!  Thank you for the quick response.
On Fri, Sep 10, 2021 at 2:33 AM Andrey Lomakin @.***>
wrote:

Hi @MikeB2019x https://github.com/MikeB2019x we are working on that. It
will take some time to resolve some obstacles but we are completely aware
of the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/orientechnologies/orientdb/issues/9679#issuecomment-916666056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALV3V73AHYLSZZ2EO725MALUBGRDPANCNFSM5DXIMGCQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
http://mindbridge.ai/
Michael Bourassa
Data Scientist | MindBridge
+1<PHONE_NUMBER> <+1-613-894-9189>
Bourassa
mindbridge.ai
[image: twitter] https://twitter.com/mindbridge_ai
[image: linkedin] https://www.linkedin.com/company/mindbridge-ai/
[image: banner]
https://www.mindbridge.ai/news/mindbridge-named-to-forbes-ai-50-list-of-most-promising-ai-companies

After 3 months, is this fixed?


fix: configure systemd priorities

Fixes RVT-4031
Changes

#1384  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Fixes #515

When the image is rotated it was keeping its old height and width, sometimes resulting in a distorted rectangle. This is changed to reflect the new dimensions.

Is there anything that needs to be done on this before it can be merged into master? I am having the same issues as @AlexanderLyon and others mentioned on rotating and then resizing a rectangle in #515.

I'm not opposed to this approach (although it may seem like since I haven't responded in almost a year).  Sorry for not responding to this PR earlier, just been caught up in other things.
But I do think this comment is right: https://github.com/Foliotek/Croppie/issues/515#issuecomment-470631693.  If someone rotates the image 180 deg, the width and height shoudln't change.

That makes sense. If @AlexanderLyon isn't interested or doesn't have time to make that change I can create a PR next week.

This can be closed in favor of #647 as these changes have all been rolled into #647.

Thanks @jedsmith13!


Cloning a graph

I've a lot of ESXi hosts to plot & i decided to clone an IN/OUT (and complicated) graph.
Two ways for that, CLI or Web-GUI :

for the first, a failed (i located the json file, modify, check the user's rights) : "Failed to load" "graph" in the preview ;
via web interface, when you clone a graph and update the data sources (updating host/source) it shows a red message (An error occurred while performing operation studs) and a "Failed to load" "graph" in the preview.

Am i doing something wrong ?

Hi Thomas,
Do you have any specific error message in the logs when the red message triggers?

OK, sorry, my bad, i forgot to watch the log : this is a config mistake, a portgroup isn't present in that ESX... the log said :
2015/11/16 14:54:31 WARNING: server: unknown metric snmp.if_octets-YYY.rx' for source esx-XXX' in origin collectd' 2015/11/16 14:54:31 WARNING: server: unknown metric snmp.if_octets-YYY.tx' for source esx-XXX' in origin collectd'
2015/11/16 14:54:31 ERROR: server: unable to make plots response: unable to find plots for `snmp.if_octets-YYY.rx' series
I remove the data source from the graph & it works now.


Cannot copy and paste from/to a webview's iframe

VSCode Version: all
OS Version: all

Steps to Reproduce:

Create a webview with an iframe in it. It can point to http://localhost:8080
Create an http server to serve from http://localhost:8080. It can serve an index.html file with the text 'copy me'
Try to load the iframe in the vscode webview. The text will appear.
Try to copy the text
Try to paste the text. The text wasn't copied

Does this issue occur when all extensions are disabled?: Yes/No
Yes

Duplicate of #65452


Redesign the BeginLocation and EndLocation Data Frames to facilitate translating the WZDx specification into the geoJson specification.

Issue name: “Redesign the BeginLocation and EndLocation Data Frames to facilitate translating the WZDx specification into the geoJson specification.”
Summary
The BeginLocation and EndLocation Data Frames in Version 1.0 of WZDx specification are difficult to translate into the geoJson specification because the fields are not normalized. Specifically, latitude-est, latitude-ver, longitude-ver, milepost-est, milepost-ver all contain data elements in the field name.  To normalize the data, and thus ease the translation from WZDx to geoJson, I suggest the changes below.
Motivation
Work Zone Data is inherently spatial and temporal.  By facilitating the use of the geoJson format publishers and consumers can leverage Geographic Information Systems and spatially enabled applications to quickly and easily visualize WZD information.
Proposed changes
Work Zone Feature

Convert the Common Core Table to a spatial feature called WorkZone by adding a geometry field.
The geometry field may represent any geometry as described in the geoJson specification. (Point, Multipoint,  LineString, MultiLineString, Polygon, or MultiPolygon)
Add a spatialAccuracy field in the common core table.
spatialAccuracy is required and represented as an Enumeration with the values of Verified or Estimated.
Add a wzFeatureType field to the common core table
wzFeatureTypes is required and represented as an Enumeration with the values of Work Zone, Entry Point, and Exit Point.  Work Zone feature types may be added to the specification as needed.

Work Zone Feature

Data Name
Data Type
Description
Conformance
Notes

Geometry
geometry
May be represented as any geometry   type defined in the GeoJson Specification. (Point, Multipoint, LineString,   MultiLineString, Polygon, or MultiPolygon)
Required, can be null
Content conforms to the GeoJson Spec

wzFeatureType
Enum
A description of the Work Zone Feature   Type
required

SpatialAccuracy
Enum:   Estimated or Verified
A measure of how accurate the geometry   is.
required

Identifier
Data Element
A unique identifier issued by the data   feed provider to identify the work zone project or activity
required
Request that this be a standardized   identifier for a future version

Subidentifier
Data Element
A unique identifier issued by data   feed provider   that provides additional references to   project or activity
optional
This identifier may be used in more   than one feed as a reference to an   agency project number or permit ID

startDateTime
Data Element
The time and date when a work zone is   established
Required
All date/time formats shall use ISO   8601 Data elements and interchange formats – Information interchange

startDateTimeAccuracy
Enum:   Estimated or Verified
A measure of how accurate the start   Date Time is.
Required

endDateTime
Data Element
The time and date when a work zone   is removed
Required
All date/time formats shall use ISO   8601 Data elements and interchange formats – Information interchange

endDateTimeAccuracy
Enumeration:   Estimated or Verified
A measure of how accurate the end Date   Time is.
Required

wzStatus
Enum
The status of the work zone
Optional
See Enumerated Type Definitions

totalLanes
Data Element
The total number of lanes associated with   the road segment designated by the workzone geometry
Optional
A segment is a part of a roadway in a   single direction designated the work zone geometry

openLanes
Enum
The laneType that is opened on the   road segment   designated by the work zone geometry
Optional

closedLanes
Enum
The laneType that is closed due to the   work zone on the road segment designated by the work zone geometry

More detailed lane   impacts / status will be described in Version   2 of the specification

closedShoulders
Enum
An enumerated type identifying the shoulder   lanes that are closed
Optional
To explicitly state that no   shoulders are closed,   use none

workersPresent
Data Element
A flag indicating that there are workers   present in the work zone
Optional

reducedSpdPosted
Data Element
The reduced speed limit posted in the   work zone
Optional

RoadRestrictions
Enum
One or more roadRestriction flags indicating   restrictions apply to the work zone road segment associated   with the work zone bounded by the   work zone geometry
Optional
More details may be added to future   WZDx versions; these are included as flags rather than detailed restrictions

Description
Data Element
Short free text description of work   zone
Optional
This will be populated with formal phrases   in a later WZDx version

issuingOrganization
Data Element
The organization issuing the data feed
Optional
Will create a list in a future version

timestampEventCreation
Data Element
The time and date when the activity or   event was created
Optional

timestampEventUpdate
Data Element
The time and date when the activity or   event was updated
Optional

Provide TMDD Example
Provide XML Example
Provide geoJson Example

BeginLocation Data Frame

Extract the BeginLocation Data Frame from the common core to a spatial feature called wzEntryPoint by adding a geometry field.
The geometry field is represented as a point geometry as described in the geoJson specification.
Consider changing the feature name from BeginLocaton to wzEntryPoint because the BeginLocation descriptor maybe become ambiguous as the specification adds more spatial features.
Add a spatialAccuracy field in the common core table.
spatialAccuracy is required and represented as an Enumeration with the values of Verified or Estimated.
Add a wzFeatureType field to the common core table
wzFeatureTypes is required are represented and an Enumeration with the values of Work Zone, Entry Point, and Exit Point.  Work Zone feature types may be added to the specification as needed.
Add an identifier field
The identifier field serves as a foreign key and relates the wzEntryPoint feature to the WorkZone feature.

Work Zone Entry Point Feature

Data Name
Data Type
Data Description
Conformance
Notes

Geometry
Point
geoJson definition of a point
Required

wzFeatureType
Enum
A description of the Work Zone Feature   Type
Required
“Work Zone Entry Point”

SpatialAccuracy
Enum:   Estimated or Verified
A measure of how accurate the geometry   is.
Required

Identifier
Data Element
A unique identifier issued by the data   feed provider to identify the work zone project or activity
Required
Request that this be a standardized   identifier for a future version

roadName
Data Element
The name of the road on which   the work zone applies which is   known by the public
Required
Add a business rule that   pulls data from a specified   list or formal naming   conventions, for example,   (1) arterials comply with the USPS   Street Suffix Abbreviations (USPS Pub   28); (2) all Interstates will   be abbreviated as I-#, state route   with the   state abbreviation and then the   number, etc.

roadNum
Data Element
The road number designated   by a jurisdiction such as a   county, state or interstate
Optional
Examples I-5, VT 133

roadDirection
Data Element
The designated direction of the   roadName that is impacted by   the work zone activity
Required
Example North (for I-5 North)

Milepost
Data Element
The linear distance   measured against a milepost   marker along a roadway where the work   zone begins

A milepost or mile marker is a surveyed   distance posted along a roadway measuring the length (in miles or tenth of a   mile) from the south west to the north east. These markers are typically   notated on State and local government digital road   networks. Provide link to   description of milepost   method in metadata file   (see Section 2.7).

milepostAccuracy
Enum:   Estimated or Verified
A measure of the accuracy of the   milepost value

crossStreet
Data Element
The cross street along the   roadway where the work zone   area begins

Required when Road   Classification is arterial

Provide TMDD Example
Provide XML Example
Provide geoJson Example

EndLocation

Extract the EndLocation Data Frame from the common core to a spatial feature called wzExitPoint by adding a geometry field.
The geometry field is represented as a point geometry as described in the geoJson specification.
Consider changing the feature name from EndLocaton to wzExitPoint because the EndLocation descriptor maybe become ambiguous as the specification adds more spatial features.
Add a spatialAccuracy field in the common core table.
spatialAccuracy is required and represented as an Enumeration with the values of Verified or Estimated.
Add a wzFeatureType field to the common core table
zFeatureTypes is required are represented and an Enumeration with the values of Work Zone, Entry Point, and Exit Point.  Work Zone feature types may be added to the specification as needed.
Add an identifier field
The identifier field serves as a foreign key and relates the wzExitPoint feature to the WorkZone feature.

Work Zone Exit Point Feature

Data Name
Data Type
Data Description
Conformance
Notes

geometry
Point
geoJson definition of a point
Required

wzFeatureType
Enum
A description of the Work Zone Feature   Type
required
“Work Zone Exit Point”

SpatialAccuracy
Enum:   Estimated or Verified
A measure of how accurate the geometry   is.
Required

identifier
Data Element
A unique identifier issued by the data   feed provider to identify the work zone project or activity
required
Request that this be a standardized   identifier for a future version

Milepost
Data Element
The linear distance   measured against a milepost   marker along a roadway where   the work zone begins

A milepost or mile marker is a   surveyed distance posted along a roadway measuring the length (in miles or   tenth of a mile) from the south west to the north east. These markers are   typically notated on State and local government digital road   networks. Provide link to   description of milepost   method in metadata file   (see Section 2.7).

milepostAccuracy
Enum:   Estimated or Verified
A measure of the accuracy of the milepost   value

crossStreet
Data Element
The cross street along the   roadway where the work zone   area begins

Required when Road   Classification is arterial

Provide TMDD Example
Provide XML Example
Provide geoJson Example

Create a Work Zone Feature Collection Class

A Feature Collection Object represents a collection of Features.

The Work Zone Feature Collection object conforms to the data content defined in the GeoJson Specification

Provide TMDD Example

Provide XML Example

Provide geoJson Example

Updated the issue with a suggested data structure.  Its normalized and should serves as a neutral specification that can be translated to and from multiple formats.  Will update with TMDD, XML, and geoJson examples.

The WZDD attached estimated and verified to a point to distinguish how the location was measured, not specifically "accuracy". Most locations are currently assigned a location when placed on a map or located relative to a mile marker if designated in the field.  Some were assigned during the planning process (and the actual placement may be different). An appropriate translation may be a flag that indicates that a location is verified using an accurate measuring method. Additionally, lat/long may have a different verification method than elevation.  In most cases this won't be a problem except when a work zone snakes along a mountain or is on hilly terrain.
In addition, confidence was included as a statistical measure of accuracy.  I did not see confidence in the list of attributes. This measure was recommended during the initial discussions on the WZDx 1.1.
wZFeatureType works to describe different spatial feature types.  The MUTCD includes naming conventions for specific zones.  The WZDD associates point and polyline features based on the zones. The WZDD used these zones to drive feature naming conventions (begin/end zone). See diagram below.

Polly Okunieff (ICF) on behalf of the FHWA Work Zone Data Initiative (WZDI)

Interesting information on the WZ spatial features diagram from MUTCD, in that most customers we have spoke with actually call the “Begin Location” the Taper Point and call the “Advanced Warning Location” the Start of the WZ.
From: Polly-Okunieff<EMAIL_ADDRESS>Sent: Thursday, October 3, 2019 7:32 AM
To: usdot-jpo-ode/jpo-wzdx<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [usdot-jpo-ode/jpo-wzdx] Redesign the BeginLocation and EndLocation Data Frames to facilitate translating the WZDx specification into the geoJson specification. (#41)
The WZDD attached estimated and verified to a point to distinguish how the location was measured, not specifically "accuracy". Most locations are currently assigned a location when placed on a map or located relative to a mile marker if designated in the field. Some were assigned during the planning process (and the actual placement may be different). An appropriate translation may be a flag that indicates that a location is verified using an accurate measuring method. Additionally, lat/long may have a different verification method than elevation. In most cases this won't be a problem except when a work zone snakes along a mountain or is on hilly terrain.
In addition, confidence was included as a statistical measure of accuracy. I did not see confidence in the list of attributes. This measure was recommended during the initial discussions on the WZDx 1.1.
wZFeatureType works to describe different spatial feature types. The MUTCD includes naming conventions for specific zones. The WZDD associates point and polyline features based on the zones. The WZDD used these zones to drive feature naming conventions (begin/end zone). See diagram below.
[image]https://user-images.githubusercontent.com/54638091/66126310-2be95a80-e5b7-11e9-8ec0-6d83f256a760.png
Polly Okunieff (ICF) on behalf of the FHWA Work Zone Data Initiative (WZDI)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/usdot-jpo-ode/jpo-wzdx/issues/41?email_source=notifications&email_token=AMWYPBS76CR23SRDHVXZNODQMXQ5LA5CNFSM4IWTPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIBITQ#issuecomment-537924686, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMWYPBTR22KWTSPIYGENXUTQMXQ5LANCNFSM4IWTPZCA.
F. TODD FOSTER, P.E.
T:<PHONE_NUMBER>
C:<PHONE_NUMBER>
F:<PHONE_NUMBER>
VER-MAC.COMhttp://VER-MAC.COM

The WZDD attached estimated and verified to a point to distinguish how the location was measured, not specifically "accuracy". Most locations are currently assigned a location when placed on a map or located relative to a mile marker if designated in the field. Some were assigned during the planning process (and the actual placement may be different). An appropriate translation may be a flag that indicates that a location is verified using an accurate measuring method. Additionally, lat/long may have a different verification method than elevation. In most cases this won't be a problem except when a work zone snakes along a mountain or is on hilly terrain.
In addition, confidence was included as a statistical measure of accuracy. I did not see confidence in the list of attributes. This measure was recommended during the initial discussions on the WZDx 1.1.
wZFeatureType works to describe different spatial feature types. The MUTCD includes naming conventions for specific zones. The WZDD associates point and polyline features based on the zones. The WZDD used these zones to drive feature naming conventions (begin/end zone). See diagram below.

Polly Okunieff (ICF) on behalf of the FHWA Work Zone Data Initiative (WZDI)

Would demarcationMethod enumerated with "Verified" and "Estimated" be a more accurate descriptor?

Updated the post.
Split the geometry field into geometryType and geometry.
Changed spatialAccuracy to demarcationMethod
Changed milepostAccuracy to mpDemarcationMethod
Dropped Feature Collection class.

geoJSon Work Zone Feature examples
<script src="https://gist.github.com/DeraldDudley/ae492b090fdddca6574e72f804d9a2f5.js"></script>

Updated the Post
Added links to geojson examples for Work Zone Features, Begin Location Features, and End Location Features.

If I am understanding this correctly, if I want to provide the begin and end locations I must include both as separate features?  So in your begin and end location example (https://gist.github.com/DeraldDudley/d1155539e31467e5725eb9f6f7f0b3cf) I would just be replicating the data associated to each point?

If I am understanding this correctly, if I want to provide the begin and end locations I must include both as separate features? So in your begin and end location example (https://gist.github.com/DeraldDudley/d1155539e31467e5725eb9f6f7f0b3cf) I would just be replicating the data associated to each point?

Yes.  Beginning and Ending Locations have different attributes and would therefor be different features.

Updated the post with a Maricopa County Example...
Maricopa County WZD as a geoJson feed:
https://maps.bts.dot.gov/.well-known/wzd/maricopa_county_wzd.geojson
Maricopa County WZD feed Mapped:
https://gist.github.com/DeraldDudley/1c686933be7fbb99b96d7205f5ff79d9

Begin/End Location is a point feature that includes lat/long, road name and/or number, roadDirection (cardinal value of the road direction). Sometimes the feature location is ambiguous due to  the accuracy of the spherical coordinates, or two roads are too close together. The WZDD includes city/jurisdiction and state in the definition for geometric features particularly if the WZ starts in one state and ends in another; we did not include that in WZDx 1.1.
From: Derald Dudley<EMAIL_ADDRESS>Sent: Tuesday, October 8, 2019 11:21 AM
To: usdot-jpo-ode/jpo-wzdx<EMAIL_ADDRESS>Cc: Okunieff, Polly<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [usdot-jpo-ode/jpo-wzdx] Redesign the BeginLocation and EndLocation Data Frames to facilitate translating the WZDx specification into the geoJson specification. (#41)
If I am understanding this correctly, if I want to provide the begin and end locations I must include both as separate features? So in your begin and end location example (https://gist.github.com/DeraldDudley/d1155539e31467e5725eb9f6f7f0b3cf) I would just be replicating the data associated to each point?
Yes. Beginning and Ending Locations have different attributes and would therefor be different features.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/usdot-jpo-ode/jpo-wzdx/issues/41?email_source=notifications&email_token=ANA3MC2HFTJ7RACF6HUUVUDQNSQPDA5CNFSM4IWTPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAURYCA#issuecomment-539565064, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANA3MCZP3JJAFJ3OR6LJK7DQNSQPDANCNFSM4IWTPZCA.

This is resolved in the GeoJSON formatting (#53) and Relational Data Model (#54) implemented for the v2 release.


Update pr61

The wikipedia link to  you check for Angola is invalid, some holidays in that calendar are no longer holidays.
This a correct link
https://pt.wikipedia.org/wiki/Feriados_em_Angola.
Regarding Japan the nuget is a project that I found that as several astronomical formulas, including one to calculare solstices and equinoxes, because two holidays in Japan depend on the date of those equinoxes.


Qubole Notebook not showing federation databases

When running following set of command via hive or spark engine on Qubole, proper results are displayed. i.e.  List of all the databases from primary & federated MSs are showing.
hive> show databases;
LIST_OF_PRIMARY_MS_SCHEMAS
LIST_OF_FEDERATED_MS_SCHEMAS

When running same query via qubole-notebook, only PM schemas are displayed. I am using same Spark cluster.
spark.sql("show databases").show()
ONLY_LIST_OF_PRIMARY_MS_SCHEMAS

That to me looks like the spark query is not using WD. Can you check the hive.metastore.uris property and confirm it is the thrift uri for Waggle Dance?

I will check this.
Since hive.metastore.uris is configured at cluster level and if I am using same cluster in notebook then it should work out of the box unless notebook is overwriting this property.

We've had lots of fun and games with Hive settings being changed within Qubole and also within Spark itself. Let us know what you find, we can then check what teams on our side have done to get this working in our equivalent environments.

I ran following command on Qubole notebook
spark.sql("set hive.metastore.uris").show()

And it returned following result:
+-------------------+-----------+
|                key|      value|
+-------------------+-----------+
|hive.metastore.uris|<undefined>|
+-------------------+-----------+

So looks like notebook is overwriting (atleast) this property.

UPDATE
I changed updated this property using following command:
spark.sql("set hive.metastore.uris=thrift://waggle-dance:12345")

And executed the same command and no success. I am still getting same results.

UPDATE
Using following property solved the issue:
spark.hadoop.hive.metastore.uris thrift://waggle-dance:12345

Navigation
Clusters > [EDIT specific Spark Cluster] > Advance Configuration > SPARK SETTINGS

Thanks for the extra info on resolving the issue!

May be adding this info in the README should be helpful to everyone.

Yeah, I'm not sure, it should really be documented in Spark/Qubole - "How to specify a custom Hive metastore" as it's not really related to WaggleDance directly. If we add it to our documentation then we have the maintenance burden of keeping this up to date for different versions of Qubole/Spark etc.


Memory bank features normalization

I the create_memory features of the memory bank seem to be normalized along the spatial dimension. I believe this is a bug, maybe the dimension should be specified as "-1" instead of dim=1, although there is another normalization done further in the code.

Hello @sirkosophia,
Thank you very much for pointing this out. You are absolutely correct.
There is this small issue in the uploaded source code.
Unfortunately, we had fixed this in our local hummingbird evaluation for our publication but did not push it yet here.
We also finished the evaluation on ADE20k. I will try to push all the changes tomorrow.
Thanks again for pointing it out though.

Hello @sirkosophia again,
We investigated the effect of this small change in the code and it consistently and minimally affects better the performance of all the algorithms we tried.
You can see below the results of different algorithms on the Pascal VOC (Augmented) with 512 image size.

 Model
 Type
mIoU With Mistake
mIoU Without Mistake

ViT-S/16
DINO
47.9
48.7

ViT-S/16
SelfPatch
50.1
50.8

ViT-S/16
CrOC
59.5
60.5

ViT-S/16
TimeT
61.3
62.3

ViT-S/16
Leopart
63.4
64.5

ViT-S/16
CrIBo
71.2
72.4

ViT-S/14
DINOv2R
73.8
75.0

ViT-S/14
NeCo
78.9
80.2

ViT-Β/16
MAE
6.9
7.0

ViT-Β/16
DINO
56.5
57.3

ViT-Β/16
Leopart
68.2
69.5

ViT-Β/16
CrIBo
73.1
74.2

ViT-Β/14
DINOv2R
76.2
77.3

ViT-Β/14
NeCo
82.2
83.5

I am closing the issue as it seems closed. Please reopen It if you have further questions.


add rule to add correct bg color to all application pages

Can you update lines 95 - 98 in application.scss too?
Also, maybe the controller class is sufficient and we don't need jobseeker too?

yes ill sort the application css but id rather leave the .jobseeker bit, as although you are correct that the controller class is sufficient, im bit by bit making all sass files namespaced to what they deal with

Can you update lines 95 - 98 in application.scss too?
Also, maybe the controller class is sufficient and we don't need jobseeker too?

yes ill sort the application css but id rather leave the .jobseeker bit, as although you are correct that the controller class is sufficient, im bit by bit making all sass files namespaced to what they deal with


[tool_crash] String: <57 characters>

Command
flutter --no-color run --machine --device-id=4d00b5df65599097 --profile --dart-define=flutter.inspector.structuredErrors=true lib/main.dart

Steps to Reproduce

...
...
...

Logs
String: <57 characters>

[✓] Flutter (Channel stable, 3.10.0, on macOS 12.6.1 21G217 darwin-x64, locale en-TR)
    • Flutter version 3.10.0 on channel stable at /Users/mac/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (3 weeks ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/mac/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio Preview.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] Connected device (3 available)
    • SM N900 (mobile) • 4d00b5df65599097 • android-arm    • Android 5.0 (API 21)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 12.6.1 21G217 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 113.0.5672.126

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 84a1e904f44f9b0e9c4510138010edcc653163f8
Plugins
connectivity_plus-4.0.1
device_info-2.0.3
firebase_analytics-10.4.2
firebase_analytics_web-0.5.4+2
firebase_core-2.13.1
firebase_core_web-2.5.0
firebase_messaging-14.6.2
firebase_messaging_web-3.5.2
flutter_local_notifications-14.1.0
flutter_plugin_android_lifecycle-2.0.15
google_sign_in-6.1.3
google_sign_in_android-6.1.14
google_sign_in_ios-5.6.2
google_sign_in_web-0.12.0
image_picker-0.8.7+5
image_picker_android-0.8.6+16
image_picker_for_web-2.1.12
image_picker_ios-0.8.7+4
local_auth-2.1.6
local_auth_android-1.0.28
local_auth_ios-1.1.3
local_auth_windows-1.0.8
package_info_plus-4.0.2
path_provider-2.0.15
path_provider_android-2.0.27
path_provider_foundation-2.2.3
path_provider_linux-2.1.10
path_provider_windows-2.1.6
share_plus-7.0.2
sqflite-2.2.8+4
url_launcher-6.1.11
url_launcher_android-6.0.34
url_launcher_ios-6.1.4
url_launcher_linux-3.0.5
url_launcher_macos-3.0.5
url_launcher_web-2.0.16
url_launcher_windows-3.0.6
webview_flutter-4.2.1
webview_flutter_android-3.7.0
webview_flutter_wkwebview-3.4.3

Closing as duplicate of https://github.com/flutter/flutter/issues/108812 which has the same crash log (log is truncated). May be also related: https://github.com/flutter/flutter/issues/118400.


MPI_Abort when running on TACC

running the newest compilation from Takis's patch, in /work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart
The preprocessing seems to work fine, but when spinning up parallel jobs it fails with MPI_Abort
removed ‘PET0.ESMF_LogFile’
removed ‘PET1.ESMF_LogFile’
removed ‘PET2.ESMF_LogFile’
removed ‘PET3.ESMF_LogFile’
removed ‘PET4.ESMF_LogFile’
removed ‘PET5.ESMF_LogFile’
removed ‘PET6.ESMF_LogFile’
removed ‘PET7.ESMF_LogFile’
 INFO: Processing --np
 INFO: Processing --partmesh
 File                                                      fort.14
 WAS FOUND!  Opening & Processing file

 from alloc_main1:

 memory currently allocated =    834350176  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 memory currently allocated =    928059968  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Global Grid file read successfully.
INFO: This mesh has 7698 weir node pairs.
INFO: Maximum number of duals for any weir node is 2.
 maximum co-nodes for any node =           21
 edge count =      5385262

 Grid Partition Data
 METIS 4.0 will require approximately    604899540  bytes
 Total Edges Cut =        72899
INFO: Writing mesh partition to partmesh.txt.
 INFO: METIS has partitioned nodes successfully.

 memory currently allocated =    928059968  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 INFO: Processing --np
 INFO: Processing --prepall
 File                                                      fort.14
 WAS FOUND!  Opening & Processing file

 File fort.15
 WAS FOUND!  Opening & Processing file

 Elevation Station Locations contained in fort.15
 Velocity Station Locations Contained in fort.15
 NHSTAR =            5
 *****************************************************
 *   Based on input and information extracted from   *
 *   the ADCIRC UNIT 14 and 15 (grid and horiz run   *
 *   info) files the following paramter values will  *
 *   be set:                                         *
 *                                                   *
 *       MNPROC =     8                             *
 *       MNE =  3564104      MNP =  1813443          *
 *       MNEI =       9                               *
 *       MNOPE =      1      MNETA =    186          *
 *       MNBOU =    186      MNVEL =  62973          *
 *       MNTIF =      8      MNBFR =     13          *
 *       MNSTAE =   398      MNSTAV =     1          *
 *       MNSTAC =     1      MNSTAM =     1          *
 *       MNWP =       1                               *
 *       MNWLAT =     1      MNWLON =     1          *
 *       MNFFR =      1                              *
 *                                                   *
 *   Also, NO wind forcing will be used,             *
 *   means and variance calculation will NOT be made,*
 *   the GWCE matrix will be left in consistent form *
 *   the model will be set up for a 2DDI run,        *
 *   and an iterative solver will be used            *
 *****************************************************

 from alloc_main1:

 memory currently allocated =    835157964  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 memory currently allocated =    928867756  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Global Grid file read successfully.
 INFO: Opening file partmesh.txt
 INFO: Closed partmesh.txt file.
 INFO: Start reading in fort.15.
 nstae=         398
 Elevation Station Locations contained in fort.15
 Velocity Station Locations Contained in fort.15

 memory currently allocated =    928867776  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 INFO: Fulldomain fort.15 file read successfully.
 INFO: Initializing the netCDF output files.

 Determine the parameters MNPP and MNEP
  Setting MNPP =       234076
  Setting MNEP =       462069
 Allocate arrays dimensioned by MNPP and MNEP
 from alloc_main2:

 memory currently allocated =    995965109  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Decomposition of grid begins
 Decomposition Data
 DOMAIN  RES_NODES  GHOST_NODES  TOT_NODES  ELEMENTS
 ------  ---------  -----------  ---------  --------
 GLOBAL                           1813443    3564104
 PE0000    227289        470       227759     440713
 PE0001    225597        670       226267     445040
 PE0002    231831        784       232615     462069
 PE0003    219811        760       220571     434603
 PE0004    232899       1177       234076     460421
 PE0005    221280        441       221721     433178
 PE0006    222149       1047       223196     432613
 PE0007    232587        784       233371     461564
 Decomposition successful
 Writing Local UNIT 14 (Grid) File for each PE

 Boundary Node Decomposition Data
 DOMAIN      NOPE    NETA    NBOU  NVEL    NWEIR
 GLOBAL       1     186     186   62972    7698
 PE0000       0       0      75   14462    5844
 PE0001       0       0      36    6870    1867
 PE0002       0       0       7    2395       0
 PE0003       0       0      11    5808       0
 PE0004       0       0       2    6557       0
 PE0005       0       0       5    9835       0
 PE0006       1     186      69   12749       0
 PE0007       0       0       1    4394       0
 Writing Local UNIT 15 (Run Info) File for each PE

 Station Data
 DOMAIN      NSTAE   NSTAV    NSTAC    NSTAM
 GLOBAL     398       0       0       0
 PE0000      32       0       0       0
 PE0001      26       0       0       0
 PE0002      29       0       0       0
 PE0003      32       0       0       0
 PE0004      29       0       0       0
 PE0005      76       0       0       0
 PE0006     136       0       0       0
 PE0007      38       0       0       0
 Writing Message-Passing Info Files for each PE

 Communication Data
 DOMAIN  COMM_PE  %(SURF/VOL)
 ------  -------  -----------
 PE0000        2      0.21
 PE0001        2      0.30
 PE0002        4      0.34
 PE0003        4      0.35
 PE0004        4      0.51
 PE0005        2      0.20
 PE0006        4      0.47
 PE0007        2      0.34

 memory currently allocated =    995965109  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Writing subdomain Nodal Attributes (unit 13)
 file for each PE.
File fort.13
 WAS FOUND!  Opening & Processing file.

     Finished processing mannings_n_at_sea_floor
 for processor range            1  to            8
     Finished processing primitive_weighting_in_continuity_equation
 for processor range            1  to            8
     Finished processing surface_canopy_coefficient
 for processor range            1  to            8
     Finished processing surface_directional_effective_roughness_length
 for processor range            1  to            8
     Finished processing surface_submergence_state
 for processor range            1  to            8

 memory currently allocated =    995965089  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Writing domain-decomposition file for post-processor

 INFO: Finished pre-processing input files.

 memory currently allocated =    995965089  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

TACC:  Starting up job 6999047
TACC:  Starting parallel tasks...
application called MPI_Abort(comm=0x84000004, 1) - process 0
application called MPI_Abort(comm=0x84000002, 1) - process 1
application called MPI_Abort(comm=0x84000002, 1) - process 2
application called MPI_Abort(comm=0x84000002, 1) - process 3
TACC:  MPI job exited with code: 1
TACC:  Shutdown complete. Exiting.

when running ibrun NEMS.x
TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.TACC:  Starting up job 6999729
TACC:  Starting parallel tasks...
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
/work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart/NEMS.x: error while loading shared libraries: libnetcdf.so.13: cannot open shared object file: No such file or directory
TACC:  MPI job exited with code: 127
TACC:  Shutdown complete. Exiting.

when running NEMS.x ADCIRC+WW3DATA+ATMESH coldstart on the HSOFS Sandy case, without ibrun:
application called MPI_Abort(comm=0x84000000, 1) - process 0
[unset]: readline failed

running the newest compilation from Takis's patch, in /work/07531/zrb/stampede2/runs/hsofs/sandy/coldstart
The preprocessing seems to work fine, but when spinning up parallel jobs it fails with MPI_Abort
removed ‘PET0.ESMF_LogFile’
removed ‘PET1.ESMF_LogFile’
removed ‘PET2.ESMF_LogFile’
removed ‘PET3.ESMF_LogFile’
removed ‘PET4.ESMF_LogFile’
removed ‘PET5.ESMF_LogFile’
removed ‘PET6.ESMF_LogFile’
removed ‘PET7.ESMF_LogFile’
 INFO: Processing --np
 INFO: Processing --partmesh
 File                                                      fort.14
 WAS FOUND!  Opening & Processing file

 from alloc_main1:

 memory currently allocated =    834350176  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 memory currently allocated =    928059968  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Global Grid file read successfully.
INFO: This mesh has 7698 weir node pairs.
INFO: Maximum number of duals for any weir node is 2.
 maximum co-nodes for any node =           21
 edge count =      5385262

 Grid Partition Data
 METIS 4.0 will require approximately    604899540  bytes
 Total Edges Cut =        72899
INFO: Writing mesh partition to partmesh.txt.
 INFO: METIS has partitioned nodes successfully.

 memory currently allocated =    928059968  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 INFO: Processing --np
 INFO: Processing --prepall
 File                                                      fort.14
 WAS FOUND!  Opening & Processing file

 File fort.15
 WAS FOUND!  Opening & Processing file

 Elevation Station Locations contained in fort.15
 Velocity Station Locations Contained in fort.15
 NHSTAR =            5
 *****************************************************
 *   Based on input and information extracted from   *
 *   the ADCIRC UNIT 14 and 15 (grid and horiz run   *
 *   info) files the following paramter values will  *
 *   be set:                                         *
 *                                                   *
 *       MNPROC =     8                             *
 *       MNE =  3564104      MNP =  1813443          *
 *       MNEI =       9                               *
 *       MNOPE =      1      MNETA =    186          *
 *       MNBOU =    186      MNVEL =  62973          *
 *       MNTIF =      8      MNBFR =     13          *
 *       MNSTAE =   398      MNSTAV =     1          *
 *       MNSTAC =     1      MNSTAM =     1          *
 *       MNWP =       1                               *
 *       MNWLAT =     1      MNWLON =     1          *
 *       MNFFR =      1                              *
 *                                                   *
 *   Also, NO wind forcing will be used,             *
 *   means and variance calculation will NOT be made,*
 *   the GWCE matrix will be left in consistent form *
 *   the model will be set up for a 2DDI run,        *
 *   and an iterative solver will be used            *
 *****************************************************

 from alloc_main1:

 memory currently allocated =    835157964  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 memory currently allocated =    928867756  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Global Grid file read successfully.
 INFO: Opening file partmesh.txt
 INFO: Closed partmesh.txt file.
 INFO: Start reading in fort.15.
 nstae=         398
 Elevation Station Locations contained in fort.15
 Velocity Station Locations Contained in fort.15

 memory currently allocated =    928867776  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 INFO: Fulldomain fort.15 file read successfully.
 INFO: Initializing the netCDF output files.

 Determine the parameters MNPP and MNEP
  Setting MNPP =       234076
  Setting MNEP =       462069
 Allocate arrays dimensioned by MNPP and MNEP
 from alloc_main2:

 memory currently allocated =    995965109  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Decomposition of grid begins
 Decomposition Data
 DOMAIN  RES_NODES  GHOST_NODES  TOT_NODES  ELEMENTS
 ------  ---------  -----------  ---------  --------
 GLOBAL                           1813443    3564104
 PE0000    227289        470       227759     440713
 PE0001    225597        670       226267     445040
 PE0002    231831        784       232615     462069
 PE0003    219811        760       220571     434603
 PE0004    232899       1177       234076     460421
 PE0005    221280        441       221721     433178
 PE0006    222149       1047       223196     432613
 PE0007    232587        784       233371     461564
 Decomposition successful
 Writing Local UNIT 14 (Grid) File for each PE

 Boundary Node Decomposition Data
 DOMAIN      NOPE    NETA    NBOU  NVEL    NWEIR
 GLOBAL       1     186     186   62972    7698
 PE0000       0       0      75   14462    5844
 PE0001       0       0      36    6870    1867
 PE0002       0       0       7    2395       0
 PE0003       0       0      11    5808       0
 PE0004       0       0       2    6557       0
 PE0005       0       0       5    9835       0
 PE0006       1     186      69   12749       0
 PE0007       0       0       1    4394       0
 Writing Local UNIT 15 (Run Info) File for each PE

 Station Data
 DOMAIN      NSTAE   NSTAV    NSTAC    NSTAM
 GLOBAL     398       0       0       0
 PE0000      32       0       0       0
 PE0001      26       0       0       0
 PE0002      29       0       0       0
 PE0003      32       0       0       0
 PE0004      29       0       0       0
 PE0005      76       0       0       0
 PE0006     136       0       0       0
 PE0007      38       0       0       0
 Writing Message-Passing Info Files for each PE

 Communication Data
 DOMAIN  COMM_PE  %(SURF/VOL)
 ------  -------  -----------
 PE0000        2      0.21
 PE0001        2      0.30
 PE0002        4      0.34
 PE0003        4      0.35
 PE0004        4      0.51
 PE0005        2      0.20
 PE0006        4      0.47
 PE0007        2      0.34

 memory currently allocated =    995965109  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Writing subdomain Nodal Attributes (unit 13)
 file for each PE.
File fort.13
 WAS FOUND!  Opening & Processing file.

     Finished processing mannings_n_at_sea_floor
 for processor range            1  to            8
     Finished processing primitive_weighting_in_continuity_equation
 for processor range            1  to            8
     Finished processing surface_canopy_coefficient
 for processor range            1  to            8
     Finished processing surface_directional_effective_roughness_length
 for processor range            1  to            8
     Finished processing surface_submergence_state
 for processor range            1  to            8

 memory currently allocated =    995965089  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

 Writing domain-decomposition file for post-processor

 INFO: Finished pre-processing input files.

 memory currently allocated =    995965089  bytes
 memory high water mark     =<PHONE_NUMBER>  bytes

TACC:  Starting up job 6999047
TACC:  Starting parallel tasks...
application called MPI_Abort(comm=0x84000004, 1) - process 0
application called MPI_Abort(comm=0x84000002, 1) - process 1
application called MPI_Abort(comm=0x84000002, 1) - process 2
application called MPI_Abort(comm=0x84000002, 1) - process 3
TACC:  MPI job exited with code: 1
TACC:  Shutdown complete. Exiting.

Zach, are you sure that all required files to run the application are in their correct locations
so NEMS.x can find them?


fixes #74 entry animation for cards

fixed the entry animation for entry of cards
fixed the alignment of board and action

@vatsalya25 please merge develop


Wiki: How to install bourbon and neat in ember-cli

Can we have a wiki on what did you do to install bourbon and neat?
Looks like you did some unconventional stuff!

I basically copied https://github.com/yapplabs/ember-cli-bourbon, except I tried to be a hipster and use the latest version (which requires latest sass, which requires Ruby sass instead of libsass, which turned out to be a bad idea – see #5 :smile:). I ended up using few of bourbon/neat anyway, pretty sure I would have been fine with the older version from ember-cli-bourbon :smile:
To be honest, I still don't know if it really requires creating an in-repo-addon just to use bourbon/neat, if I'm just doing it for one local project. I couldn't figure out how to make the sass @import work without doing what yapplabs did. Maybe @stefanpenner will know :stuck_out_tongue:

thanks @chancancode  :+1:  :)


docs: add information about appBinaryPath for MacOS

Hi, thank you for your work!
With this PR I would like to add information about appBinaryPath for MacOS.
I was trying to run webdriverio for my electron application on MacOS without luck, but then I suddenly realised (while digging into the source code of wdio-electron-service) that I had configured appBinaryPath incorrectly. It wasn't clear to me that I had to set the path this way, so I'm suggesting this information so that it might save someone a few hours/days in the future.

I see the need for this - we don't mention anywhere in the docs about how to find Electron binaries in the different OS's.  I guess it didn't come up before now because most people use the binary autodetect.  I'll make some changes to the copy and merge.


stm32h7: add usb hs ulpi support

Add support for the STM32H7 USB OTG HS and support for the ULPI PHY. Add the ulpi definition example with the STM32H747-Disco Board.
Signed-off-by: Ryan McClelland<EMAIL_ADDRESS>

There is the issue of the pinctrl dtsi slew rate for the ulpi pins are not set right. These are left at the default and these need to be at least "fast-speed"

I have verified this with a custom board... but I don't have a have STM32H747-Disco in front of me yet. I can get one later this week which I can run the test on (unless if someone else is anxious and can test sooner for me :) )

You should probably split that in several commits.

Looks globally fine aside from the comments already given which should be taken into account.
Current driver implementation is not great regarding clocks and should be reviewed to make things clearer but this should be done in another PR.
Note that I tried to test on stm32h747_disco_m7 (modifying pin slew rate), no success.

I wonder if that could be because CONFIG_USB_DC_HAS_HS_SUPPORT is not set as @jfischer-no mentioned. I have that enabled in the custom board that I have which is working...I should be able to get ahold of that disco board on Wednesday to test it out on it.

Note that I tried to test on stm32h747_disco_m7 (modifying pin slew rate), no success.

I wonder if that could be because CONFIG_USB_DC_HAS_HS_SUPPORT is not set as @jfischer-no mentioned. I have that enabled in the custom board that I have which is working...I should be able to get ahold of that disco board on Wednesday to test it out on it. I may have to update the KConfig to imply that if that otghs is enabled

Depending on what "no success" means. The CONFIG_USB_DC_HAS_HS_SUPPORT only modifies the bulk endpoint max packet size (from 64 to 512, however the old stack does not take the current speed into account). Therefore, if "no success" means "device enumerated but does not work properly" then that can be due to missing CONFIG_USB_DC_HAS_HS_SUPPORT but if it means "device doesn't even send the device descriptor to host" then it's different problem.

CONFIG_USB_DC_HAS_HS_SUPPORT

I got a hold of my STM32H747-Disco.... It works working for me with the code as is and shows up in dmesg
[156084.598332] usb 3-6.1: new high-speed USB device number 26 using xhci_hcd
[156084.675055] usb 3-6.1: config 1 interface 1 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
[156084.675077] usb 3-6.1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[156084.676430] usb 3-6.1: New USB device found, idVendor=2fe3, idProduct=0001, bcdDevice= 3.02
[156084.676444] usb 3-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[156084.676450] usb 3-6.1: Product: Zephyr CDC ACM sample
[156084.676456] usb 3-6.1: Manufacturer: ZEPHYR
[156084.676461] usb 3-6.1: SerialNumber: 3438510C00290033
[156084.682997] cdc_acm 3-6.1:1.0: ttyACM0: USB ACM device

Although there is the error about the maxpacket which is due to the CONFIG_USB_DC_HAS_HS_SUPPORT missing.
This was with the samples/subsys/usb/cdc_acm sample
After adding that Kconfig to be auto-selected if the speed is HS.
[156760.938437] usb 3-6.1: new high-speed USB device number 31 using xhci_hcd
[156761.015702] usb 3-6.1: New USB device found, idVendor=2fe3, idProduct=0001, bcdDevice= 3.02
[156761.015727] usb 3-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[156761.015737] usb 3-6.1: Product: Zephyr CDC ACM sample
[156761.015744] usb 3-6.1: Manufacturer: ZEPHYR
[156761.015750] usb 3-6.1: SerialNumber: 3438510C00290033
[156761.019991] cdc_acm 3-6.1:1.0: ttyACM0: USB ACM device

There is the issue of the pinctrl dtsi slew rate for the ulpi pins are not set right. These are left at the default and these need to be at least "high-speed"

Can you add a commit that updates west.yaml and points to commit e1c54e99a40da705c156ae3464a14720e7d668c8 ?


PRIMAVERA tables and filtering

Hi all,
Thanks to your help I am able to make work PRIMAVERA tables  with master branch, which means that the most of the required variables can be correctly obtained (if the correct variables and parameters tables are used)
However, at the moment of the filtering I am getting this error for a few variables:
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 133.128, level type 100, level 40. Dismissing task hus23 in table Primday
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 130.128, level type 100, level 40. Dismissing task ta23 in table Primday
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 131.128, level type 100, level 40. Dismissing task ua23 in table Primday
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 132.128, level type 100, level 40. Dismissing task va23 in table Primday
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 135.128, level type 100, level 40. Dismissing task wap23 in table Primday
ERROR:ece2cmor3.grib_filter:Field missing in the first day of file: code 129.128, level type 100, level 40. Dismissing task zg23 in table Primday

As long as I understand the filtering is not finding in the first file the pressure level 40 for hus,va,zg etc. However, the pressure level a 40 Pa is there, as all the other 44 pressure levels shown by:
[pdavini0@r000u07l02 IFS]$ cdo showlevel -selcode,129 ICMSHqctr+194912
cdo showlevel: Started child process "selcode,129 ICMSHqctr+194912 (pipe1.1)".
<PHONE_NUMBER>0 95000 92500 90000 87500 85000 82500 80000 77500 75000 74000 70000 65000 62000 60000 55000 50000 45000 40000 37500 35000 30000 25000 24500 22500 20000 17500 15000 12500 10000 9000 7000 5000 3000 2000 1000 900 700 500 300 200 100 40

So I am thinking there is an issue in the way the filtering operates on those vars, perhaps we need to fix something in the Primavera tables?
Thanks for any hint

I know the problem: 40 Pa is too low for the standard encoding in GRIB so it uses a different level type, which I didn't account for in the filtering. I will fix this asap.

Should be fixed after rev. f7ffe034eb513b5f62416d1bd3e3f883440232fc

Great! I am testing it right now and it's working like a charm. I can close this.


move agent into go-choria

Since its now in go-choria by default always, we should move the agent into that code based to keep it up to date easily.

TODO: update readme for the fact that rebuild isnt needed


feature request: field name for prompts

Hey first of all, thanks for the library, it's really simple and beautiful.
I was wondering if it would be possible to have something like this:
from bullet import Bullet
cli = Bullet(
    prompt = "Choose from the items below: ",
    choices = ["first item", "second item", "third item"],
    field_name="item_name")
result = cli.launch()
print(dict(result))

Current output
{
    "Choose from the items below: ": "first item"
}

Expected output
{
    "item_name: ": "first item"
}

Sorry if it's already there, but I haven't seen it in the source code.
Thanks!

@Mckinsey666 love the library. I also think this would be a useful addition to allow you to automatically structure the output in a way that works for whatever it gets sent off to.


Deleting a label on a node through the API does not delete the labels

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Add a label to a node template - say DO
Bring up a cluster - 1 node all roles using this node template
click on View in API of the node
Delete the label. Send request.
the label is NOT deleted.

Expected Result:
Label should be deleted
Other details that may be helpful:

When the user does a delete of the label from the API the second time, the label is deleted.
The label gets deleted the first time, when the action is performed through the UI.
Behavior is the same for a node with all roles/worker only node

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.2
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke do
Kubernetes version (use kubectl version):

1.17.4

@sowmyav27 isn't this a duplicate of https://github.com/rancher/rancher/issues/15825?

Duplicate issue.
Closing this one


alex-3.2.0 fails to generate correct parser for ghc-HEAD

https://github.com/simonmar/alex/commit/00431304aa18ada0a12aab43443023a86521f353
added explicit type signature for alex_accept:
--- a/src/Output.hs
+++ b/src/Output.hs
@@ -63,43 +66,89 @@ outputDFA target _ _ typesig dfa
-    outputAccept
-        = case typesig of
-          Nothing ->
-              -- No type signature: we don't know what the type of the actions is.
-              -- str accept_nm . str " :: Array Int (Accept Code)\n"
-              str accept_nm . str " = listArray (0::Int," . shows n_states
-            . str ") [" . interleave_shows (char ',') (map outputAccs accept)
+    outputAccept =
+        str accept_nm . str " :: Array Int (AlexAcc ())\n"
+      . str accept_nm . str " = listArray (0::Int," . shows n_states . str ") ["
+      . interleave_shows (char ',') (snd (mapAccumR outputAccs 0 accept))
+      . str "]\n"

and GHC relies it to be user-defined:
compiler/parser/Lexer.x:2658:21: error:
    • Couldn't match type ‘Word64’ with ‘()’
      Expected type: ()
        Actual type: ExtsBitmap
    • In the first argument of ‘alexScanUser’, namely ‘exts’
      In the expression: alexScanUser exts inp sc
      In a stmt of a 'do' block:
        case alexScanUser exts inp sc of {
          AlexEOF
            -> do { let ...;
                    setLastToken span 0;
                    .... }
          AlexError (AI loc2 buf)
            -> reportLexError loc1 loc2 buf "lexical error"
          AlexSkip inp2 _
            -> do { setInput inp2;
                    lexToken }
          AlexToken inp2@(AI end buf2) _ t
            -> do { setInput inp2;
                    let ...;
                    .... } }

compiler/stage1/build/Lexer.hs:116:15: error:
    • Couldn't match type ‘Word64’ with ‘()’
      Expected type: Array Int (AlexAcc ())
        Actual type: Array Int (AlexAcc ExtsBitmap)
    • In the expression:
        listArray
          (0 :: Int, 207)
          [AlexAccNone, AlexAcc 167, AlexAcc 166, AlexAcc 165, ....]
      In an equation for ‘alex_accept’:
          alex_accept
            = listArray
                (0 :: Int, 207) [AlexAccNone, AlexAcc 167, AlexAcc 166, ....]

alex-3.2.0 generates the following alex_accept:
alex_accept :: Array Int (AlexAcc ())
alex_accept = listArray ...

Removing explicit type signature makes lexer build fine.
Adding @emc2 for visibility.

@trofi Is is possible to narrow down exactly what in that file is causing problems? I'm thinking that such a very much reduced example should end up in the tests.

I expect any lexer that uses alexScanUser style
will break (alex has no tests/ or examples/ for alexScanUser).
Will try to write example (and a fix) today.

Added lexer test: https://github.com/simonmar/alex/pull/99
It triggered the same build failure.


Define Sqitch changes naming conventions

[ ] document naming convention
[ ] update sqitch plan according to convention
[ ] edit sqitch plan to prevent altering the table when possible

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @matthieu-foucault @wenzowski

Before estimating, can we add in the description the conventions we want to follow to know the amount of work?


Amendment XLS-35: URIToken — Lightweight first-class NFTs

High Level Overview of Change
The URIToken Amendment (XLS-35d) provides a lightweight alternative to XLS20 suitable for both main-net and side-chains.
The amendment adds:
A new type of ledger object: ltURI_TOKEN
A new serialized field: URITokenID
Five new transaction types:
URITokenMint
URITokenBurn
URITokenBuy
URITokenCreateSellOffer
URITokenCancelSellOffer

[x] New feature (non-breaking change which adds functionality)

@dangell7 is this ready for review?

note: there are merge conflicts you'd need to resolve

@dangell7 is this ready for review?

Ready for review

I am requesting a code review on this. Anyone feel like reviewing it please?

I am requesting a code review on this. Anyone feel like reviewing it please?

From the ripple side, @ledhed2222 will be able to help provide code review on this.  In terms of timing, I'm predicting he will be able to get to this in two weeks or so
It would be great if we can seek additional help from non-ripple in terms for code review so that we can get more community representation/participation in this process.  Would anyone else be able to help review?  🙏

just started taking a look at this :)

@ledhed2222 Thank you very much for your time and review of the code. I have marked everything that I have updated with a thumbs up.
Richard and I are going to address some of the other comments and then I will push the changes for a second review.

@dangell7 - at your convenience, please respond to the comments above

lacks reviews - community is welcome to review.


Unable to use programmatic_auth not possible

Using programmatic_auth as auth_uri it failes to generate a correct URL.
redirect_uri and response_type aren't allowed but they get added using FlowType::InstalledInteractive.
Google says Parameter not allowed for this message type: redirect_uri and Parameter not allowed for this message type: response_type
also the scopes need to be devided by a + instead of spaces.
After that it would be nice to get the code which is in the cookie "oauth_token".
This is needed for generating the correct token for using the hangouts chat api (see hangups). Idea is to do automatic logins/auths. 100% from CLI
Did I miss something?

I googled around for the programmatic_auth issue, it seems to be some known issue with the hangouts API (as described in the hangups issue #260). Please be advised that only APIs in https://github.com/Byron/google-apis-rs are supported. I wonder whether it might be easier for you to just do the HTTP requests yourself?
w.r.t. the scope divider, I fixed this.

Found that out too after that, Sadly I am stuck to googles page "Cookies are ot enabled" :/

oh, and I looked after the scope separation; the official documentation uses %20, not +: https://developers.google.com/identity/protocols/OAuth2InstalledApp

hm oh thats interesting because in there fromular on the login page they use a plus :/

@dermesser quick question. Is there a way to get the url that the dialog prints to a variable so that I can use that url in a request?

@dermesser basicly I mean how can I get the response of the build_authentication_request_url() function?

if you really want to go that route, you can supply Authenticator::new() (https://github.com/dermesser/yup-oauth2/blob/master/src/authenticator.rs#L73) with a delegate (https://github.com/dermesser/yup-oauth2/blob/master/src/authenticator_delegate.rs#L62) that captures the verification_url.

Thanks. Reason is I have to use (sadly) programmatic_auth for hangouts because hangouts uses a oauth1.0 scope which is only allowed via programmatic_auth but I want still to use your crate :) so I have to intercept it a little bit


KAFKA-3050: Acceptor allows hostnames surrounded by whitespaces

The Kafka config parsing code already seems to trim white spaces. See - https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/config/ConfigDef.java#L197
Not sure why do we need to trim again.

Issue 3050 affected <IP_ADDRESS> version. This code fixed bug on that branch, but no new release planned for 0.8.2 so I pushed it to master. With this config, in master this doesn't seem to have sense. Should I push it to that branch?

I see similar code (trim) in <IP_ADDRESS> as well.
https://github.com/apache/kafka/blob/<IP_ADDRESS>/clients/src/main/java/org/apache/kafka/common/config/ConfigDef.java#L143
Maybe its failing in some other code path ? I am not able to replicate that issue by adding space after the hostname.

Try to replicate it in <IP_ADDRESS> branch, for me without that trim it throws exactly the same exception as Navin reported in jira.

yes, it fails in <IP_ADDRESS> branch. apparently it was not trimming all the values, but seems to have got fixed in the trunk.

Closing this since the issue was already fixed. Please reopen if you think this was a mistake.


base image need to be upgraded because RHEL 7.6 was end of maintenance.

We security team find around 500 CVEs in secondary-scheduler-operator image:
https://github.com/openshift/secondary-scheduler-operator/blob/master/Dockerfile
which use RHEL 7.6 as base image, we need to upgrade it to 8.x or 9.x to get rid of security issues.
Thanks!

@yimingwangdell the mentioned Dockerfile is not used for building the actual image. It is used only for developer purposes.
/close


How can i have a row read only

Hi,
nice grid,
is there any way to have the grid on read-only mode. don't want to edit the value in the grid
thank you

Hi,
nice grid,
is there any way to have the grid on read-only mode. don't want to edit the value in the grid
thank you

Thx, its not perfect, but Im trying :-)
Dont have one simple for setting entire row or grid
But under column setup you can use the col-add-row-attributes to add custom/extra normal ones to the inputs/checkboxes, like readonly or disabled
<v-grid>
  x-attributes..
x-attributes..

  <v-grid-col
     col-field="someattribute"
     col-add-row-attributes"readonly">
  </v-grid-col>

</v-grid>

https://vegarringdal.gitbooks.io/dev-rebuild/content/chap03/col-add-row-attributes.html

Guessing you got it working just fine


Can't build the app

No matching variant of androidx.navigation:navigation-safe-args-gradle-plugin:2.7.0 was found.
I'm getting the above error when doing the gradle building.
Please let me know how to fix this error.

Here is the reference to prefer.

@bestras023 be
Did you fix it ?

Got the same error.

Fixed.


Update spatial report name

In https://github.com/AlexsLemonade/scpca-docs/pull/257, the spatial report is being renamed from library_spaceranger_summary.html -> library_spaceranger-summary.html.
We'll want to update accordingly here:
https://github.com/AlexsLemonade/scpca-nf/blob/b6246b2b7f1d10ff40e2673b6da84eec3d64a833/modules/spaceranger.nf#L68

Closed by #679


Added Columnar Cipher in Python

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Implemented columnar cipher in python. It is a form of transposition cipher. The plaintext is written in rows and ciphertext is read out by columns using the order of key.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #3805

@anushkrishnav I have made the changes. Please have a look.


Deployment Failed, Error: Failed to deploy web package to App Service. Not Found (CODE: 404)

Hello,
i'm using the action with version 2 and i've got an error on some of subscription:
##[debug]Polling for ZIP Deploy URL: https://my-application.scm.azurewebsites.net:443/api/zipdeploy?isAsync=true&deployer=GITHUB_ZIP_DEPLOY&message=%7B%22type%22%3A%22deployment%22%2C%22sha%22%3A%2295d06efe0f59b3fd0eb81431a266113da7ebed2b%22%2C%22repoName%22%3A%22myorg%2Fmybackend%22%2C%22actor%22%3A%22johndoe%22%2C%22slotName%22%3A%22%22%2C%22commitMessage%22%3A%22%22%7D/api/deployments/latest?deployer=GITHUB_ZIP_DEPLOY&time=2023-08-02_13-34-46Z
##[debug]setting affinity cookie ["ARRAffinity=c98e7e9285c7dbb7fa977a8333eee2544318b89fdea1c8072c0ae10c26b5a0f3;Path=/;HttpOnly;Secure;Domain=my-application.scm.azurewebsites.net","ARRAffinitySameSite=c98e7e9285c7dbb7fa977a8333eee2544318b89fdea1c8072c0ae10c26b5a0f3;Path=/;HttpOnly;SameSite=None;Secure;Domain=my-application.scm.azurewebsites.net"]
##[debug][GET] [https://my-application.scm.azurewebsites.net:443/api/zipdeploy?isAsync=true&deployer=GITHUB_ZIP_DEPLOY&message={"type"%3A"deployment"%2C"sha"%3A"95d06efe0f59b3fd0eb81431a266113da7ebed2b"%2C"repoName"%3A"myorg%2Fmybackend"%2C"actor"%3A"johndoe"%2C"slotName"%3A""%2C"commitMessage"%3A""}/api/deployments/latest?deployer=GITHUB_ZIP_DEPLOY&time=2023-08-02_13-34-46Z](https://my-application.scm.azurewebsites.net/api/zipdeploy?isAsync=true&deployer=GITHUB_ZIP_DEPLOY&message={"type"%3A"deployment"%2C"sha"%3A"95d06efe0f59b3fd0eb81431a266113da7ebed2b"%2C"repoName"%3A"myorg%2Fmybackend"%2C"actor"%3A"johndoe"%2C"slotName"%3A""%2C"commitMessage"%3A""}/api/deployments/latest?
##[debug]Could not parse response body.
##[debug]{}
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Error: Failed to deploy web package to App Service.
Not Found (CODE: 404)
Any idea of the pb?
Regards

I just start getting this too. Some web apps still deploy fine, but few now gives this every time
Run azure/webapps-deploy@v2
Package deployment using ZIP Deploy initiated.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed, Error: Failed to deploy web package to App Service.
Not Found (CODE: 404)
App Service Application URL: https://***.azurewebsites.net

However the deploy seems to actually go through so the issue is just in the action and it's response status.

I'll confirm the deployment is ok, in the portal it says ok but the action failed. It's like it's do some polling to get the status of the deployment and it cannot find it. As workaround i use az webapp deploy from cli which works fine.

Same issue here but deployment is working fine despite the error.

It seems that MS is deploying new version of app service:

Non Working AS :  PLATFORM_VERSION = <IP_ADDRESS>2
Working AS :  PLATFORM_VERSION = <IP_ADDRESS>

Hi @vimarie @Benjamin-DAGUE @larts1 , based on our investigation we found out a code defect in latest kudu patch which caused the malformed deployment status uri. There was no issue in deployment but while polling the status because of malformed uri the logs were showing 404.
We have rolled out the fix. Can you please check now?
In case this issue reappears, restarting the site will mitigate the issue.

Hi, it's working for me now , problem solved!
Thanks

The issue has been fixed and rolled out. Closing this now, thanks.


Quickstart #6 - JavaScript Client

Hi!
I've followed steps on quickstart #6 to add a JavaScript client.
I run the JavaScript client app. I click on Login button and it redirects me to IdentityServer UI login page. I try login as user:alice, password:alice, but in return I get the following exception:
InvalidOperationException: Endpoint IdentityServer.ConsentController.Index (IdentityServer) contains authorization metadata, but a middleware was not found that supports authorization. Configure your application startup by adding app.UseAuthorization() inside the call to Configure(..) in the application startup code.
Here you have the resulting log file:
identityserver4_log.txt
NOTE: All projects on the solution target .NET Core 3.0
Please, help!
Thank you!

@libypur2k19
Add middleware app.UseAuthorization(); in Startup method public void Configure(IApplicationBuilder app).

Thanks - not all quickstarts have been updated to ASP.NET Core  3 yet. We will work on it ASAP.


Can we automatically detect the language being entered?

Simple version: HTML vs Jade vs Markdown
Harder: JavaScript vs React
Harder: SCSS vs LESS

Bottom line: no.
Well, not yet in computing. But maybe one day.