0.7.1 error when creating a chart

Error: Invalid value for <foreignObject> attribute height="NaN"

Can you provide additional details?

Also did you mean 0.7.2 ?

No 0.7.1, and I didn't find anything upon initial investigation, I'll look into it again more in depth.

Can you post the code your using to reproduce the error?

.directive('barGraph', [function() {
		return {
			restrict: 'E',
			scope: {
				data: '='
			},
			link: function($scope, element, attrs) {
				var data = {
					// A labels array that can contain any sort of values
					labels: $scope.data.labels,
					// Our series array that contains series objects or in this case series data arrays
					series: [$scope.data.data]
				};

				var options = {};

				if (attrs.gWidth && attrs.gHeight) {
					options.width = attrs.gWidth;
					options.height = attrs.gHeight;
				}

				$scope.graph = new Chartist.Bar(element[0], data, options);
			}
		};
	}])
	.directive('lineChart', [function() {
		return {
			restrict: 'E',
			scope: {
				data: '='
			},
			link: function($scope, element, attrs) {
				var data = {
					// A labels array that can contain any sort of values
					labels: $scope.data.labels,
					// Our series array that contains series objects or in this case series data arrays
					series: [$scope.data.data]
				};

				var options = {
					lineSmooth: false,
					low: 0,
					showArea: true
				};

				if (attrs.gWidth && attrs.gHeight) {
					options.width = attrs.gWidth;
					options.height = attrs.gHeight;
				}

				$scope.graph = new Chartist.Line(element[0], data, options);
			}
		};
	}]);

Both graphs cause the same error, but I'm not sure why.

Can you also post the markup you're using? Which version of angular.js are you using?

Angular 1.3.13
<bar-graph class="ct-chart ct-perfect-fourth" data="topItemsData" ng-if="topItemsData"></bar-graph>

<line-chart class="ct-chart ct-perfect-fourth" data="ordersPerDayData" ng-if="ordersPerDayData"></line-chart>

I too am having this issue.  I just installed Chartist yesterday evening using bower.  Using version 0.7.1.
And the code that I am getting the error on is the code from the "Getting started" section of the Chartist website.

I checked out revision 3cd52116d93 and used that version and I do not get the error anymore.

Hey guys
I can't reproduce the problem. I'm using the chartist.min.js and chartist.js from v0.7.2 tag with this code:
<!DOCTYPE html>

  <link rel="stylesheet" href="chartist.min.css"/>

I've tested in Chrome 40 and Firefox 35.
What browser are you using?

@Schwoebel are you making an HTTP request for your data?

I am using Chrome 40.0.2214.  I didn't try it in Firefox.
I didn't revert back step by step to see where the error stopped.  In my case I may have just gotten lucky?  It may be something that was changed after that release but before 0.7.2?
Nope, not making any HTTP requests.  In my specific case it was a straight copy/paste from the website.

Is this still am ossue guys?

@gionkunz it seems to actually have to do with the DOM recreating the chart whenever the page is resized.

This is still an issue for me as well. I can also confirm the error happens on resize, though not initially for me. Once it starts happening it gets thrown rapidly. This is perhaps a bit of a tangent, but is there any throttling or debouncing around that resize code? Also, when there's more than one chart on the page, are multiple listeners being attached to the window resize event (or is this taken care of with the event emitter)?
And another thought on debouncing... if there is a problem with calculating height during the resize, would debouncing the function to wait until window resizing has ended to resize the chart fix the bug?

I cannot say if I am stil having the issue.  I am still using the older installation that I used to fix the problem initially.  Today I am going to try using 0.7.2 elsewhere and I will let you know.

I still can't reproduce the problem guys :-) Please give me something I can use to reproduce the problem. Can you post a JSBin and description on how to reproduce the issue?
@bzalasky , debouncing is important on things that can happen a lot like scrolling or user sleeping on his keyboard, however, that users resize their window is simply a myth I believe :-) I think if you'd track how many users resize their browser during a page visit, the outcome would be close to 0 and the leftover are developers checking out the responsiveness of your site. :-) For security / stability reason I agree with you so we should probably think about adding a debounce mechanism. There are mutlipple listeners on the window for each chart instance. The resize listener is attached during Chart creation in https://github.com/gionkunz/chartist-js/blob/develop/src/scripts/base.js#L90 and will be removed during de-initialization or if the chart is getting detached explicitly. I actually don't know what's more performant, one listener that iterates over all charts or multiple listeners (that get iterated when the event occur) that handle their own chart.

In regards to problems calculating container dimensions I'm not aware of any issues except if the container is not visible at the time of initialization.

I would have one listener on the window that publishes an event that all instances subscribe to... this event should be debounced and publish the current screen width. This is so you don't have to re-query the DOM for this information again. I agree that users probably aren't resizing a ton on desktops, but it's reasonable to imagine a user rotating a touch device.
As far as reproducing the bug, another guy on my team commented on it, and I couldn't get it to happen for a good 5-10 minutes. However, we eventually confirmed that it happens on browser resize regardless of the chart and configuration. Both Chartist line chart examples and our configured line charts exhibited the problem.

Well, we don't query the DOM for window width as we don't rely on screen width but parent container width, which we anyway need to reconsider for each chart individually.  I completely agree with you about this and we should use debouncing just for security reasons. With the single window resize listener, as stated, probably makes sens in most cases but if you'd only want to react on the event to rearrange your internals, I don't see the direct benefit of just one event listener.

Also seeing this using Ember CLI Chartist. To reproduce it, I go to a page with a chart, visit a different page, then come back to the page with the chart and resize.

I still have no clue whats going on here. Can someone with Ember or React also produce this in plain JavaScript? Please re-open this ticket if this issue still persists.

I have used the plugin on several projects since this error occured and have not gotten the error again, even with the new installation.
I am very sorry about how long it has taken for me to get back to this thread.

I'm having this too, using Ember + Chrome. It randomly happens, but doesn't break anything, just showing the error on the console.

HI @BenjaminN which version are you using? Please note that the latest state on develop also includes a fix. I'm planing to do a release later this week but to check you could also build develop yourself.
Cheers
Gion

Thanks for the good work @gionkunz, I'll let you know.

Hello.
I catch this error when use foundation tabs with chartist. If chartist bars render without tabs, all work ok.
Error: Invalid value for <foreignObject> attribute height="NaN"

I think this is If parent div have display: none
Chrome - 42.0.2311.135
Ember - 1.11.3
jQuery - 2.1.3
foundation - 5.5.1
chartist - 0.7.4
How can I to get round this error?

@kaermorchen 0.8.0 doesn't throw this error if and of the parent elements is display: none. It does draw the chart, though it has a wrong display of the chart and the axis ticks.
My workaround, because I am also using tabs (bootstrap), was to use the chartist update method when the tab comes into view the first time. This refreshes the chart and has a correct display.
Hope it helps


[WIP] Update changelog for Fine-4

[skip ci]

@miq-bot add_label documentation

Need to resubmit this as a new PR. Closing this one,


feat: use cookies instead of localstorage

This PR introduces a new feature that replaces the usage of local storage with cookies. By using cookies, we ensure a more secure and efficient way of storing data. This change enhances the overall performance and reliability of the application.
Generated using OpenSauced.
Gifs

Working fine when using Postman, but still wondering why the browser(fetch) does not include the cookie when making request to the server :thinking:

Ok, so it's working when credentials: "include" is included in the request and it's client-side.
For SSR, I manually add Cookie: "<value>" in the headers because, for some reason, credentials:"include" does not work there...


Also do we need "$loki": 858 ?

https://github.com/jsdelivr/api/issues/33#issuecomment-41080955 ?
And having a 2nd field for the many JS+CSS projects (eg Bootstrap) would be useful.

mainfile2 was a test but got replaced by the mainfile per version which is live to this day.

Ah, sure let them go, unless you want to give a new purpose to use
mainfile2 mean a second main (eg CSS).
On Thu, May 28, 2015 at 2:09 AM, Dmitriy Akulov<EMAIL_ADDRESS>wrote:

mainfile2 was a test but got replaced by the mainfile per version which is
live to this day.
—
Reply to this email directly or view it on GitHub
https://github.com/jsdelivr/api/issues/74#issuecomment-106224636.

@jimaek we could shape the responses s.t. there is no $loki (it is used internally to identify the object w/i the lokijs db); however, this would require creating an object that has all elements except $loki - that's not so bad for calls that request a single library but can be murder when a user requests all libraries w/i the api.


Histogram switching to per week failed

{"ERROR":{"message":"An error occurred (404) when calling the HeadObject operation: Not Found","traceback":"Traceback (most recent call last):\n  File "./rabbitmq_handler.py", line 25, in rabbitmq_handler\n    s3.downloadToDisk(filename=filename, localpath=localPath, remotepath=remotePath)\n  File "/scripts/writeToS3.py", line 47, in downloadToDisk\n    os.path.join(remotepath, filename), f)\n  File "/usr/local/lib/python3.7/site-packages/boto3/s3/inject.py", line 795, in download_fileobj\n    return future.result()\n  File "/usr/local/lib/python3.7/site-packages/s3transfer/futures.py", line 103, in result\n    return self._coordinator.result()\n  File "/usr/local/lib/python3.7/site-packages/s3transfer/futures.py", line 266, in result\n    raise self._exception\n  File "/usr/local/lib/python3.7/site-packages/s3transfer/tasks.py", line 269, in _main\n    self._submit(transfer_future=transfer_future, **kwargs)\n  File "/usr/local/lib/python3.7/site-packages/s3transfer/download.py", line 357, in _submit\n    **transfer_future.meta.call_args.extra_args,\n  File "/usr/local/lib/python3.7/site-packages/botocore/client.py", line 530, in _api_call\n    return self._make_api_call(operation_name, kwargs)\n  File "/usr/local/lib/python3.7/site-packages/botocore/client.py", line 960, in _make_api_call\n    raise error_class(parsed_response, operation_name)\nbotocore.exceptions.ClientError: An error occurred (404) when calling the HeadObject operation: Not Found\n"}}
When switching tp "per week" for Reddit post it didn't work.

I have tested in smile.smm.ncsa.illinois.edu site with reddit and per week worked. And all others worked as well. Could you test one more time?

can't reproduce. Close for now.


Add new tech for pipeline

After having unittests and functional tests integrated into CICD we can think of using couple of nice tools that github provides:

DependaBot to check for updates and their compatibility. This will be nicely checked by pipeline.
ReportCi - tool for marking which test failed on PR, and also stores history of tests executions. Unfortunately, it does not handle robot logs, but we could check if parsing them to JUnit/xUnit xml format would do the trick.

@pbylicki what do You think? Maybe You have something else in mind for project?

@MaciejWiczk If you want to set it up, go ahead. It would be nice to see it in action.

@pbylicki I would love to, but I think my repository permissions/github policy would not allow that :(

I forked a repo, and did some checks. Dependabot works like a charm, creates PR for updates it finds, and that triggers build. Setting it up requires to choose language and that's it. Suppots Python, JavaScript and docker. Regarding ReportCi, it can create robot/UnitTests statistics, but it will not annotate test code from those, thus does not seem like something we need. Sadly, there is no real alternative on GithHub for robot jenkins plugin :(
@pbylicki, If you had some spare time, to install dependabot, that would be nice.

@MaciejWiczk I have seen the dependabot PR and merge it. I thought that you were able to set it up by yourself. If there are still some steps to be done, I will try to look into it.

Dependabot introduced for Python dependencies. I disabled it for JS dependencies because CI currently does not build/test JS code.


Implement max line width and max line count, and make word highlighting optional

This implementation is based on word_timestamps and so it requires that option to be turned on. Word highlighting has also been made optional and turned off by default.
Examples:
# Each subtitle has a maximum of 2 lines wrapped to 47 characters:
whisper --word_timestamps True --max_line_width 47 --max_line_count 2 audio.mp3
# Same with word highlighting:
whisper --word_timestamps True --max_line_width 47 --max_line_count 2 --highlight_words True audio.mp3
# Each subtitle preserves the original Whisper segment but wrapped to 47 character lines:
whisper --word_timestamps True --max_line_width 47 audio.mp3
# Same with word highlighting:
whisper --word_timestamps True --max_line_width 47 --highlight_words True audio.mp3

When --max_line_count is specified, subtitles will be segmented at the line limit, or when there is a pause in the speech. This overcomes segmentation artifacts that can occur at window boundaries mid sentence.
This segmentation approach works better in conjunction with #1114 because that PR fixes some bugs with timestamp accuracy near segment boundaries where boundary words are stretched to cover pauses, making it harder for the current PR to detect those pauses. In the meantime, the current PR detects pauses by measuring the distance between the start timestamps of successive words rather than between the end timestamp of the previous word and the start timestamp of the current word.

Suddenly whisper transcribe started to misbehave, probably something related to line length?
My transcribed text used to look like this:
New line here.
And another new line.
And another,
which continues here

Now instead it looks like this:
New line here. And
another new line. And
another, which continues
here

What option do I need to add to this minimal code?
I think that the default behaviour should stay identical to the past, since now the output is all messed up.
thanks for any help
# load the entire audio file
audio = whisper.load_audio(audio_in)

options = {
    "language": "en", # input language, if omitted is auto detected
    "task": "transcribe", # "translate" or "transcribe" if you just want transcription
    'fp16': True,
    'verbose': True
}

result = whisper.transcribe(model, audio, **options)

I Agree with @GianniGi would be great to have an option to force a line break at the end of the sentence.

This pull request is not about sentence segmentation, it is about wrapping subtitles to a maximum line width and line count.
If you are interested in the discussion about sentence segmentation, it is over here: #1243

Do we know when this will make it into the API? I can't see it in the docs yet

Hello, sorry in advance if this is not the right place to ask, but I'm writing a python script that takes a mp4 file in output and outputs a WEBVTT file of the transcription. I managed to make it work, but now I'm trying to reduce the size of each subtitle lines and get closer to word-level transcriptions in WEBVTT but I'm having trouble understanding how to set the word_timestamps parameter to True when implementing Whisper in a Python script.
I understand from this snippet of code (from https://github.com/ilanit1997/whisper/commit/819074f53caf056f814aa4ade50d85f56b4384d1):
if not args["word_timestamps"]:
for option in word_options:
if args[option]:
parser.error(f"--{option} requires --word_timestamps True")
that you can set it using its command line argument, but I can't find out how to do it in my basic python script. (pasted it down below for reference).
import whisper
from whisper.utils import get_writer
model = whisper.load_model('base.en')
whisper.DecodingOptions(language='en', fp16='false')
audio = 'final_video.mp4'
result = model.transcribe(audio)
output_directory = "./"
word_options = {
"highlight_words": True,
"max_line_count": 50,
"max_line_width": 3
}
srt_writer = get_writer("srt", output_directory)
srt_writer(result, audio, word_options)
Sorry again if it's not the place to ask or if it's something I should be able to figure out myself, but I'm kind of stuck.
Kindly,


Leave room button doesn't work on new design

Describe the bug
When you enter a room the leave button doesn't work on new next.js design
To Reproduce
Steps to reproduce the behavior:

Go to 'next.dogehouse.tv'
Login with GitHub
Click on a random room
Click "Leave room" button on bottom right corner
See error

Expected behavior
Leave the room you are currently in
What device are you on?
HP Laptop, Google Chrome version 89.0.4389.90 (Latest stable release)
Additional context
Italian language active.

Can confirm

should be fixed now


Copying objects from Realm Sync to local Realm fails with EXC_BAD_ACCESS

Goals

Copy objects from a synced Realm to a local Realm file for backup
Expected Results

Successfully copy objects from synced Realm to local Realm
Actual Results

Using create(_:value:update:) fails with EXC_BAD_ACCESS
Steps for others to Reproduce

Created a button to update the local Realm manually
Code Sample

var localConfig = Realm.Configuration()
localConfig.fileURL = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask)[0].appendingPathComponent("local.realm")
let localRealm = try! Realm(configuration: localConfig)
let syncedRealm = try! Realm(configuration: app.currentUser()!.configuration(partitionValue: Constants.REALM_PARTITION_VALUE))
let accounts = syncedRealm.objects(Account.self)
let transactions = syncedRealm.objects(Transaction.self)
let productTypes = syncedRealm.objects(ProductType.self)
localRealm.beginWrite()
accounts.forEach { account in
    localRealm.create(Account.self, value: account, update: .all)
}
transactions.forEach { transaction in
    localRealm.create(Transaction.self, value: transaction, update: .all)
}
productTypes.forEach { type in
    localRealm.create(ProductType.self, value: type, update: .all)
}
try! localRealm.commitWrite()

Version of Realm and Tooling

Realm framework version: 10.0.0-beta.2
Xcode version: 11.5
iOS/OSX version: 13.5.1

Keep in mind that the Realm database on the device is already a local copy.
If you need to copy the entire for file management, see the writeCopy in file management.
If neither of those resolve the issue and you still believe this is a bug, please comment with the full stack trace.

Closing because of recommendation above. If anyone sees a similar exception, please open a new issue with the full stack trace.


Script fail or just no slots being released now?

Seems the script is running fine but not identifying any dates at all. Also, @allmiqdates is showing the same: no slots available since 1511 today, NZ time.
Could be the system has been frozen due to the announced Level 4 lockdown in NZ, but last time this happened (both script fail and Twitter bot fail) it was due to a change in the MIQ web site that had to be corrected for by v10.0.
Any way to tell, @alexDrinkwater ?

@HKG2301 Good to hear someone else is having same issues. The scripts are running for me but it doesn't seem to trigger the alerts anymore. Either empty slots are going so fast that we can't even detect it, or there's nothing available?

I was getting a few last night (I'm in the US). I just had it set for all dates, assume it was picking up August spots. Even so, I was still too slow to secure one and I had the laptop right next to me. Go figure.
Also now seeing this fun little warning pop up. I mean WTF. Don't use a script. But feel free to sit at your laptop all hours of the day and night clicking the refresh button while trying to not go insane  :|

It looks like they are messing with the name of the class for the dates in an explicit attempt to block scripts like this one.  For instance I now see the dates in the form:
1
where "omsoms" used to be something like "___item" which the code used to find the list of dates.  I'm going to change my local source code to search for omsoms, but I'm betting they will change this string every so often (every hour, every login, every reload ???  not sure yet.  I'll see if I can write some code to generalize and detect what the string each time the page reloads.

Yes, the class names keep on changing. I haven't noticed it being based on some particular rule though, so I think it's changing just after some arbitrary time.
I've made a change locally in my own script and haven't noticed any new spot open up yet so I'm thinking they might have done a change to how the available date's div structure looks like as well.

Looking at the css and searching for "/assets/images/not-available.png" there appear to be 281 different class names they are alternating between, e.g. nicely named things like gqagqa and yw0yw0.   I'm still trying to figure out what an available date will look like, but at least I know what unavailable ones look like (I feel like that calendar of x's will be burned into my retina for the rest of my life).

I see the Twitter bot is working again, with dates listed at 0941 and 0955 NZT this morning, so they seem to have sussed the change.

@HKG2301 Sorry can you explain what you mean by the twitter bot?

@HKG2301 Sorry can you explain what you mean by the twitter bot?

Check out: https://miqdates.com/ There are links to the twitter accounts there as well as a nice description of the statistics of the availability.  The twitter bot was temporarily blocked by the change of the web page, but has developed a work-around.

@HKG2301 Sorry can you explain what you mean by the twitter bot?

Check out: https://miqdates.com/ There are links to the twitter accounts there as well as a nice description of the statistics of the availability. The twitter bot was temporarily blocked by the change of the web page, but has developed a work-around.

Thanks Martin! Every little bit of info helps! Spent days getting these scripts up only to be thrown into despair again with this script change

hello everyone,
just created a pull request to make the tool works again with latest Aug 18th MIQ Updates
#128
can @alexDrinkwater  or someone else from maintainers merge it?
I hope this helps more in this difficult situation of getting back to NZ

Looking at the css and searching for "/assets/images/not-available.png" there appear to be 281 different class names they are alternating between, e.g. nicely named things like gqagqa and yw0yw0. I'm still trying to figure out what an available date will look like,

@cmartin-kavlifoundation - Yeah no hits whatsoever since around 8am this morning. Would be great if you could please share (when you figure it out) the change we can make on the .js file.
Cheers,

Looking at the css and searching for "/assets/images/not-available.png" there appear to be 281 different class names they are alternating between, e.g. nicely named things like gqagqa and yw0yw0. I'm still trying to figure out what an available date will look like,

@cmartin-kavlifoundation - Yeah no hits whatsoever since around 8am this morning. Would be great if you could please share (when you figure it out) the change we can make on the .js file.
Cheers,

I've been refreshing entirely by hand today since I didn't want to run afoul of the new "no automation" rule, and haven't been lucky enough to spot ANY of the handful of openings that have come up.  So while I haven't been able to confirm the code that appears when a date is available, the patch that @monagjr has proposed looks like what I would expect based on the css files.  So when I do start running the bot again, that is the code I intend to try.  For the time being I'm going to keep running by hand and keep an eye out for an open spot.  If anyone else happens to catch a glimpse of the div class line that represents an available slot, please go ahead and post the html source here.
Thanks!

I'm now running the script directly with the patch from @monagjr
Will update if I find a slot!

// CHANGE DATES TO WHAT YOU ARE LOOKING FOR
let myDates = ['2021-08', '2021-09', '2021-10', '2021-11', '2021-12'];

2 have already confirmed the code updates #128 are working (monitoring,  beeping, and clicking dates), hopefully we can get this merged soon along with building new releases.

 I think "myDates" should have the full targeted dates (e.g 2021-08-18)

I'm now running the script directly with the patch from @monagjr
Will update if I find a slot!

Thanks, we would appreciate that

Quick question (and this is probably a stupid question), but assuming the below myDates selects all months from August to December right?
 I think "myDates" should have the full targeted dates (e.g 2021-08-18)

Ah ok. I figured it was similar to how the program allows you add a month rather than a date. But I guess I'll just manually add all the dates just to be sure. Thanks!

// CHANGE DATES TO WHAT YOU ARE LOOKING FOR
let myDates = ['2021-08', '2021-09', '2021-10', '2021-11', '2021-12'];

My reading of the source code and past experience is that 2021-08 does in fact search for the entire month.  I don't think it will hurt to specify the entire list of days in a month, but my understanding is that it is overkill.

// CHANGE DATES TO WHAT YOU ARE LOOKING FOR
let myDates = ['2021-08', '2021-09', '2021-10', '2021-11', '2021-12'];

My reading of the source code and past experience is that 2021-08 does in fact search for the entire month. I don't think it will hurt to specify the entire list of days in a month, but my understanding is that it is overkill.
Furthermore with findAnyDate=true the program will trigger on ANY date so the list of dates is irrelevant. You only need to set that if findAnyDate=false

Makes sense thanks! @monagjr confirming the alert just worked for me. I reacted immediately and still missed out, as per usual 😛. I did get hit with the recaptcha images however. I might need to check out this nut-tree mentioned in the other thread. Seems like every second counts!

I'm also trying @monagjr code but no beeps so far probably because my dates are mostly end Sep, Oct and Nov

@monagir Thanks for the update.  Any way you can make this an automatic download for us non coders?  I tried copying as a js file using notepad and replacing it but it did not work.  Refreshes the page but no alerts when dates came up.  And the evil MIQ game continues.....

@cmartin-kavlifoundation
Here is what a normal crossed out date looks like

24

Available Date:

24

Selected Date:

24

@Saj22 and anyone else who needs ready-made pre-built version of the APP latest version (v0.10.4):
https://github.com/monagjr/miq-nz-booking-tools/releases/latest

https://www.buymeacoffee.com/mojr

Thanks @monagjr.  Makes thing much easier!  Do you have any idea how to get rid of the pesky recaptchas.  I seem to only have ticks until dates become available and then I have to click on all these images.  Arggggg.

Thanks @mouarg for your support. I appreciate it.

@Saj22 and anyone else who needs ready-made pre-built version of the APP latest version (v0.10.4):

Hi monagjr, could I ask what the limitations of the "pre-built" version are please?
I ask from from here https://github.com/jvolker/miq-nz-booking-tools/issues/108 TigaNZ said:
snip...

Also editing the MIQ-assistance.js to include your login details helps cut downtime.
Find it using windows search, look for the path which is similar to c:\users\appdata\local\miq_nz_booking_tools\app-0-10.3\resources\app
You can edit this in notepad, but notepad++ is free and very good for scripting.

snip...
I'm struggling a wee bit with this part (above). I have installed 10.4 (thanks to the you), navigated to the MIQ-assistance.js file in the c:\users\appdata\local\miq_nz_booking_tools\app-0-10.4\resources\app directory, edited it by adding the required dates, set the dates option true to false to make it select the specific dates, edited my login/password but when I run it, none of the changes seems to stick.
When I go back in to the path again, and check the MIQ-assistance.js file it seems to have been overidden once again, by the default script. Is there something fundamental I am missing here please?
I also tried a 10.3-based version by mark-bloom that I downloaded a few days ago and this one seems to be able to be run and keep the edits (but is not up to date).
Can I assume the "pre-built" version assumes you add Dates/logins from the little popup window only?
Is there something I need to do to be able take advantage of editing the MIQ-assistance.js manually?
thank you
k.

Fixed in the latest release: https://github.com/jvolker/miq-nz-booking-tools/releases/latest
Thanks to @monagjr and everyone else helping with this release.


Update trust_delegation.md

Fix subject-pronoun disaggrement.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @scjane :)


Error occurred while redirecting file '/Users//config/fnm/version"

When interacting with node I see this error. Things seem to work alright though.

I'm guessing it's related to a .node-version file because it seems to work in directories without one.

@wesbaker Thanks!


Add Plausible to track visits

See e.g. https://plausible.io/gbif.org

Do do not need to add a gdpr/cookie banner for plausible: https://plausible.io/privacy-focused-web-analytics
Maybe it's still nice to mention somewhere that tracking does happen, but on in an aggregated anonymised way.


Add support for custom response headers

This is helpful when you want to return custom response headers. For example, if you want to enable SharedArrayBuffer support for a Flutter app with the skwasm renderer:
flutter build --wasm --web-renderer=skwasm
dhttpd --path=build/web_wasm --headers="Cross-Origin-Embedder-Policy=require-corp;Cross-Origin-Opener-Policy=same-origin"

@johnpryan – maybe support headers in a file? Is there a convention for that?
it'd be MUCH easier to repeat over time

I'm not sure there's a common way to define HTTP headers other than in code. How about a JSON file?

I think I prefer a flag, normally I use scripts when I want repeatability.

I was overriding the header in Chrome :P, this is much easier 💙


[Task]: Show only SELECT queries in the table data field

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

As of now we don't have any way of identifying query type, so will be following up with data-integrations pod on this. So for now we are moving this to Needs info.
cc: @dilippitchika


[LinkWithIcon]: allow left/right icon placement

Detailed description

Describe in detail the issue you're having.

Changes from #2852 now cause link icons to display in the wrong direction, since currently the vertical orientation always displays icons on the left. This causes issues when a vertical LinkList is used in another component with a requirement of icons being on the right.

Is this a feature request (new component, new icon), a bug, or a general
issue?

Feature request to have option of displaying links left or right in LinkWithIcon.

Is this issue related to a specific component?

LinkWithIcon

What browser are you working in?

What version of the IBM.com Library are you using?

v1.8.0
Steps to reproduce the issue
See example
Additional information

@kennylam is already working on enhancing the LinkWithIcon component here: https://github.com/carbon-design-system/ibm-dotcom-library/pull/2980


KServe 0.10.0 release tracking

/kind feature
Describe the solution you'd like
KServe 0.10 release tracking:
RC release Date: 11/18/2022
Release Date: TBD
KServe Model Serving:
See project dashboard to see what all features/bugs are covered as part 0.10 and their current status
ModelMesh:
Models UI::
Website:
TIMELINE

Week
Start
End
When
Event (Actual timelines)

0
Friday, July 22, 2022
Thursday, July 28, 2022

Gap week between releases. 0.9.0 release happened on July 22, 2022

1
Friday, July 29, 2022
Thursday, August 4, 2022

Development

2
Friday, August 5, 2022
Thursday, August 11, 2022

Development

3
Friday, August 12, 2022
Thursday, August 18, 2022

Development

4
Friday, August 19, 2022
Thursday, August 25, 2022

Development

5
Friday, August 26, 2022
Thursday, September 1, 2022

Development

6
Friday, September 2, 2022
Thursday, September 8, 2022

Development

7
Friday, September 9, 2022
Thursday, September 15, 2022

Development

8
Friday, September 16, 2022
Thursday, September 22, 2022

Development

9
Friday, September 23, 2022
Thursday, September 29, 2022

Development

10
Friday, September 30, 2022
Thursday, October 6, 2022

Development

11
Friday, October 7, 2022
Thursday, October 13, 2022

Development

12
Friday, October 14, 2022
Thursday, October 20, 2022

Development

13
Friday, October 21, 2022
Thursday, October 27, 2022

Development

14
Friday, October 28, 2022
Thursday, November 3, 2022

Development

15
Friday, November 4, 2022
Thursday, November 10, 2022

Development

16
Friday, November 11, 2022
Thursday, November 17, 2022

Development +Start the prep i.e.Announce/Reminder about upcoming feature freeze date in 2 weeks

17
Friday, November 18, 2022
Thursday, November 24, 2022
Friday, November 18, 2022
Feature Freeze + RC0 Released + Documentation update starts

18
Friday, November 25, 2022
Thursday, December 1, 2022

Testing

19
Friday, December 2, 2022
Thursday, December 8, 2022

Testing

20
Friday, December 9, 2022
Thursday, December 15, 2022

Testing

21
Friday, December 16, 2022
Thursday, December 22, 2022

Testing

22
Friday, December 23, 2022
Thursday, December 29, 2022
Tuesday, December 27, 2022
RC1 Released

23
Friday, December 30, 2022
Thursday, January 5, 2023

Testing

24
Friday, January 6, 2023
Thursday, January 12, 2023

Testing

25
Friday, January 13, 2023
Thursday, January 19, 2023

Testing

26
Friday, January 20, 2023
Thursday, January 26, 2023
Sunday, January 22, 2023
0.10.0 Released

Updated the issue with actual timelines that we ended up following.


Can't import Horusec report to DD v2.9.1 (demo) or v2.10.0 (local)

Bug description
Attempt to parse Horusec report raises an error and the report doesn't get imported. The problem occurs both with v2.9.1 (demo version at the moment of this writing) and v2.10.0 running locally.
Steps to reproduce
Steps to reproduce the behavior:

Login as admin at https://demo.defectdojo.org/login
Browse to All Products (second sidebar icon > All Products)
Click "BodgeIt"
Engagements > Add New Interactive Engagement (the same error happens if you select "Add New CI/CD Engagement" here)
Import Scan Results
Selected "Production" as environment
Selected "Horusec Scan" as Scan Type
Choose File >> Selected Horusec report reproduced in "Sample scan files" section
Clicked Import

Expected behavior
It was expected the Horusec report to get imported but an error is displayed instead:

An exception error occurred during the report import:time data '2022-05-0' does not match format '%Y-%m-%d'

Deployment method (select with an X)

[ ] Docker Compose
[ ] Kubernetes
[ ] GoDojo
[X] Demo DefectDojo (https://demo.defectdojo.org)

Environment information

Demo DefectDojo (https://demo.defectdojo.org)

Logs
Not accessible.
Sample scan files
Sample Horusec report used in this procedure:
{
  "version": "v2.7.1",
  "id": "069b99dd-b629-422a-ab84-c3e604db16dd",
  "repositoryID": "00000000-0000-0000-0000-000000000000",
  "repositoryName": "",
  "workspaceID": "00000000-0000-0000-0000-000000000000",
  "workspaceName": "",
  "status": "error",
  "errors": "Error while running tool YarnAudit: {HORUSEC_CLI} Error It looks like your project doesn't have a yarn.lock file. If you use Yarn to handle your dependencies, it would be a good idea to commit it so horusec can check for vulnerabilities; Error while running tool NpmAudit: {HORUSEC_CLI} Error It looks like your project doesn't have a package-lock.json file. If you use NPM to handle your dependencies, it would be a good idea to commit it so horusec can check for vulnerabilities",
  "createdAt": "2022-05-06T10:20:51.708730164-03:00",
  "finishedAt": "2022-05-06T10:20:56.195480404-03:00",
  "analysisVulnerabilities": [
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195484682-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "975c9a7e-38c3-44ab-a9ec-810c35a7ba06",
        "line": "0",
        "column": "0",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/webapp/js/jquery/jquery-ui-1.9.1.custom.min.js",
        "code": "",
        "details": "No use eval\nThe eval function is extremely dangerous. Because if any user input is not handled correctly and passed to it, it will be possible to execute code remotely in the context of your application (RCE - Remote Code Executuion). For more information checkout the CWE-94 (https://cwe.mitre.org/data/definitions/94.html) advisory.",
        "securityTool": "HorusecEngine",
        "language": "JavaScript",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "8de87f081b762ff58ab73fd5056d22ffc330a9e59a90d31cce2bfc9319e1dfcd"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195486104-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "a3a5ec03-d94c-496f-b994-3c02fbc98a2e",
        "line": "35",
        "column": "3",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/webapp/js/jquery/jquery-limit-1.2.js",
        "code": "eval(substringFunction);",
        "details": "No use eval\nThe eval function is extremely dangerous. Because if any user input is not handled correctly and passed to it, it will be possible to execute code remotely in the context of your application (RCE - Remote Code Executuion). For more information checkout the CWE-94 (https://cwe.mitre.org/data/definitions/94.html) advisory.",
        "securityTool": "HorusecEngine",
        "language": "JavaScript",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "f66f21b91a63ec0d202120234638a11a11f6013a29267df1e4beb29250686980"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195495231-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "b066e64a-2195-492e-83fd-d846512a7c0e",
        "line": "26",
        "column": "55",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestaoInternet/security/env.xml",
        "code": "\u003cenv key=\"authn.cas.fixed.initial.url\" value=\"http://<IP_ADDRESS>:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "37a7b568e8d412123e2252e891c6cdf0cb74d2d8f1565404a37e84c15f1227ed"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195496504-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "039f2a4e-ac8c-4fad-bbb2-744ac901739c",
        "line": "27",
        "column": "45",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestaoInternet/security/env.xml",
        "code": "\u003cenv key=\"authn.cas.service\" value=\"http://<IP_ADDRESS>:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "7e072c58edc6e16f829380fffb8a37c685e4f0c7ced73889a076ecdee1f38ca5"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195497836-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "68c1c9f5-e8ca-4e4b-bee9-4e63935b1e1b",
        "line": "35",
        "column": "95",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestaoInternet/security/env.xml",
        "code": ".65.10.137:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "cf47b012e90c5df40df45cf5a786dd928a050a62acb1fa4fbd6a894807206b77"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195502956-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "b6195166-8b9c-458d-b06d-1557aeaf2996",
        "line": "46",
        "column": "63",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/resources/config/security/env.xml",
        "code": "value=\"https://hgeridinss.dataprev.gov.br/cas/logout?http://<IP_ADDRESS>:7001/gestaotarefas/\" /\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "f027016b3e370c00fac4541f079d3ac3a2ee72360a0fc61e3bccd2d6b5e5a9f2"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195504298-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "347886aa-8bab-4e3e-9ef1-926405369ed1",
        "line": "53",
        "column": "17",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/resources/config/security/env.xml",
        "code": "value=\"http://<IP_ADDRESS>:7001/gestaotarefas/\" /\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "7aed2bc6c33ce82ca4f257c09ae575421b54b59994dd47dd55dc92a1a98fb05b"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195505571-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "28d4bd3a-95dd-4cf6-92c7-659d317bf6a1",
        "line": "55",
        "column": "17",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/resources/config/security/env.xml",
        "code": "value=\"http://<IP_ADDRESS>:7001/gestaotarefas/\" /\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "1d7b3fbc9d913f49fa3653468c8a272e248755aa7f387611c68e413cae6c2185"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195506863-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "04613eb5-dcc6-4ed5-aaad-bce242953ade",
        "line": "26",
        "column": "55",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestao/security/env.xml",
        "code": "\u003cenv key=\"authn.cas.fixed.initial.url\" value=\"http://<IP_ADDRESS>:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "02ae35db2145f20ce3211b7922da10888fabf95728ad9e40b4c474cfc6caee27"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195508196-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "7eef0369-0b1e-4edf-b71d-d6725ebdffd3",
        "line": "27",
        "column": "45",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestao/security/env.xml",
        "code": "\u003cenv key=\"authn.cas.service\" value=\"http://<IP_ADDRESS>:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "0da647dea51664cc7ea8cf44b5736551cce1c79c97d45e5fbaf56f5f0207ab70"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195509458-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "fe5f782f-50b3-4623-879b-bb071bc2634b",
        "line": "35",
        "column": "95",
        "confidence": "MEDIUM",
        "file": "resources-external/GetGestao/security/env.xml",
        "code": ".65.10.137:7001/gestaotarefas\"/\u003e",
        "details": "Remote code injection Apache Log4j\nLog4j versions prior to 2.17.1 are subject to a remote code execution vulnerability via the ldap JNDI parser, uncontrolled recursion from self-referential lookups and some other vulnerabilities. For more information checkout the CVE-2021-44228 (https://nvd.nist.gov/vuln/detail/CVE-2021-44228), CVE-2021-45046 (https://nvd.nist.gov/vuln/detail/CVE-2021-45046), CVE-2021-45105 (https://nvd.nist.gov/vuln/detail/CVE-2021-45105) and CVE-2021-44832 (https://nvd.nist.gov/vuln/detail/CVE-2021-44832) advisories.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "ac5e0ae2a9b400655f8c0d0e81cb5eaed329e17e2de7d1f36792c195531ac4ce"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195513085-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "04908034-7730-48d7-b3cc-371569d72869",
        "line": "37",
        "column": "52",
        "confidence": "MEDIUM",
        "file": "scripts/sibeVars.conf",
        "code": "[ \"${MW_PASSW}a\" == \"a\" ]         \u0026\u0026      export MW_PASSW=\"weblogic00\"",
        "details": "Hard-coded password\nThe software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. For more information checkout the CWE-798 (https://cwe.mitre.org/data/definitions/798.html) advisory.",
        "securityTool": "HorusecEngine",
        "language": "Leaks",
        "severity": "CRITICAL",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "135912fe0ecacafaf374d3ae1d8c2bdbbcc0d8db186238064bf8dda1b4803a53"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195480664-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "f2754733-28ab-4789-9b0b-78bd7fbf52d7",
        "line": "0",
        "column": "0",
        "confidence": "MEDIUM",
        "file": "GetGestaoVisaoWeb/src/main/webapp/js/jquery/jquery-validate.min.js",
        "code": "",
        "details": "Origins should be verified during cross-origin communications\nBrowsers allow message exchanges between Window objects of different origins. Because any window can send / receive messages from other window it is important to verify the sender's / receiver's identity: When sending message with postMessage method, the identity's receiver should be defined (the wildcard keyword (*) should not be used).\nWhen receiving message with message event, the sender's identity should be verified using the origin and possibly source properties. For more information checkout the OWASP A2:2017 (https://owasp.org/www-project-top-ten/2017/A2_2017-Broken_Authentication) and (https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) advisory.",
        "securityTool": "HorusecEngine",
        "language": "JavaScript",
        "severity": "HIGH",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "234b1d2c99e3bb26a1b7c405366e297a44a0c81752017620547f4cd697cb3bff"
      }
    },
    {
      "vulnerabilityID": "00000000-0000-0000-0000-000000000000",
      "analysisID": "069b99dd-b629-422a-ab84-c3e604db16dd",
      "createdAt": "2022-05-06T10:20:56.195501693-03:00",
      "vulnerabilities": {
        "vulnerabilityID": "19f9f287-a5d3-4a4c-9a5b-63fdc43c0507",
        "line": "146",
        "column": "33",
        "confidence": "LOW",
        "file": "GetGestaoVisaoWeb/src/main/java/br/gov/dataprev/get/web/util/ErrorHandlingUtils.java",
        "code": "String errorCode = Base64.encodeBase64String(input);",
        "details": "Base64 Encode\nBasic authentication's only means of obfuscation is Base64 encoding. Since Base64 encoding is easily recognized and reversed, it offers only the thinnest veil of protection to your users, and should not be used.",
        "securityTool": "HorusecEngine",
        "language": "Java",
        "severity": "MEDIUM",
        "type": "Vulnerability",
        "commitAuthor": "-",
        "commitEmail": "-",
        "commitHash": "-",
        "commitMessage": "-",
        "commitDate": "-",
        "vulnHash": "7b46dd376eb1dee966320f834e3ab0e060ece64b17f67b233f43cdabfea86a5b"
      }
    }
  ]
}

Screenshots

Additional context (optional)
Horusec version: v2.7.1
Export command: horusec start -o="json" -O="./get-spa.json" -i="tests/"

Seems to be a bug -_-, will work on a patch.

Got the same problem, just writing here to let you guys know!
I've tried different versions of Horusec and tweaked the exported json to see if it could parse it correctly but no success.
Let me know if I can help.

Fixed in dev


Viewhelper returns empty string when asking for a route defined as Method with verb 'post'

I have a route defined as follows:
'email-signup' => [
    'type' => \Zend\Router\Http\Method::class,
    'options' => [
        'route' => '/email-signup',
        'verb' => 'post',
        'defaults' => [
            'controller' => \Email\Controller\EmailController::class,
            'action' => 'emailSignup',
        ],
    ],
],

However the URL Viewhelper is not able to echo that route at all:
// Returns nothing
echo $this-url('email-signup');

If I change my route to a Literal, or Segment, it works fine, but not when defined as a Method.
Maybe there's a reason for this, but it's incredibly annoying when building forms (which require and action URL, but the URL itself should only accept posts).

Apparently Method doesn't use route names at all. Will find another way.


2.1.2 - NullPointerException at com.tinkerpop.blueprints.impls.orient.OrientEdge.remove

Hi,
Sometimes when trying to delete an edge via the java API, we get the following exception:
java.lang.NullPointerException: null
at com.tinkerpop.blueprints.impls.orient.OrientEdge.remove(OrientEdge.java:406) ~[com.orientechnologies.orientdb-graphdb-2.1.2.jar:2.1.2]
There is no problem deleting those edges via the web UI.
The use case is as follows:
Assume we have 2 vertices connected with an edge of class edgeCls
Within the same transaction we do the following:
v1.getVertices(Direction.OUT, edgeCls).asScala.foreach(.remove)
v1.getEdges(Direction.OUT, edgeCls).asScala.foreach(.remove)
v1.remove()
The removal of the edge after removing one of the vertices it is connecting seems to sometimes throw the above exception.
Is deletion of the edge after deleting one of the vertices it is connecting required at all?
Even if not, there seems to be some issue when trying to delete an edge which should be deleted, since sometimes it seems some leftovers are there since we get to the edge.remove() method.
I don't know if it is relevant, but we have the 'distributed' flag turned on and it happens in both single machine cluster or 3 machines cluster.
Thanks,
Moti.

Hi @motih78
Just a couple of considerations and requests:

are you working in tx mode (you should)?
when you delete a vertex, all the connected edges are automatically removed, so removing them manually is absolutely not needed
any chance to have a full stack trace?
can you reproduce the same problem in non-distributed mode? (just to understand if it's a problem with distributed layer or with TinkerPop API implementation)

Thanks
Luigi

Hi @luigidellaquila

Yes - we work in tx mode
If that is indeed the case, then edge.remove() should not be invoked after deleting a vertex (but sometimes it is invoked - maybe this is why the NullPointerException is thrown - since there is no edge to remove)
I'll try to provide a full stacktrace
I can try - the issue is intermittent, so it might be problematic to reproduce in a timely manner. but since this happens before we commit the transaction - i would guess the problem is with the TinkerPop API implementation.

Thanks,
Moti.

Seems the edge has broken links to vertices. Are you sharing the same Graph or Database instance across threads? However I introduced an additional check to avoid NPE.


remote profile is broken on 1.5.0-beta.2

Bug description
When installing the istio 1.5.0-beta.2 release with the remote profile the only thing thats installed is the istio-ingressgateway. No istiod or citadel/sidecar-injector is deployed.
In the file install/kubernetes/operator/profiles/remote.yaml all the components (except ingressGateways) are disabled (also with istioctl profile dump remote or istioctl manifest generate --set profile=remote ).
[x ] Configuration Infrastructure
[ ] Docs
[ x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
An istiod or citadel/sidecar-injector deployment and services.
Steps to reproduce the bug
istioctl manifest apply --set profile=remote
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
1.5.0-beta.2
How was Istio installed?
istioctl manifest apply --set profile=remote
Environment where bug was observed (cloud vendor, OS, etc)

I don't think you need citadel or sidecar-injector in remote cluster.  BTW, there is an endpoint issue i fixed in https://github.com/istio/istio/pull/21372

If certProvider=citadel, do you need citadel in the remote cluster?   I am thinking no as long as the remote cluster is using the same CA as local cluster. @costinm @howardjohn @ayj please share your thoughts.

We need the sidecar-injector in remote clusters in 1.5. This could be run remotely but would require additional config changes and testing.
cc @lei-tang @myidpt for citadel requirements with remote clusters. IIUC, we still need to run citadel (istiod) in each cluster because citadel doesn't yet perform OIDC discovery with remote kube-apiserver authenticating remote workloads.

https://github.com/istio/istio/pull/21534

This should be fixed by https://github.com/istio/istio/pull/21534.


zsh: command not found: dotnet on Arch Linux

Issue Title
After countless reinstalls trying different binaries from AUR I tried to install the precise version I needed manually but didn't really understand how it works and ended up just rm the dotnet executable from /usr/bin. Now when trying to install sdk from AUR again, I end up with the error from the title
General

╰─$ dotnet --version
zsh: command not found: dotnet

╰─$ whereis dotnet                                                                                127 ↵
dotnet: /usr/local/bin/dotnet /usr/share/dotnet

╰─$ which dotnet
dotnet not found
╰─$ file dotnet
dotnet: broken symbolic link to /usr/local/share/dotnet/dotnet

I have tried fixing the broken syslink with the
sudo ln -s /usr/local/share/dotnet/dotnet /usr/local/bin/

but it just creates a broken link anyways

cc @alucryd @Saancreed
Sounds like a mix of AUR packages and Microsoft packages and they dont play nice with each other. I dont use Arch, so I dont know of the step-by-step fix.

@AzimovParviz What exactly are you trying to achieve? The latest dotnet runtime and sdk are in the official repos. As long as dotnet-host from the repositories is installed, you can theoretically install and use any runtime or sdk from AUR (if they follow the same layout as our official packages), but you'll always need at least dotnet-host, which provides /usr/bin/dotnet.
BTW please don't randomly delete or create files from/on your filesystem, linux has package managers, you'll make them very upset.

Can you list step by step how you're installing .NET Core?

@AzimovParviz What exactly are you trying to achieve? The latest dotnet runtime and sdk are in the official repos. As long as dotnet-host from the repositories is installed, you can theoretically install and use any runtime or sdk from AUR (if they follow the same layout as our official packages), but you'll always need at least dotnet-host, which provides /usr/bin/dotnet.
BTW please don't randomly delete or create files from/on your filesystem, linux has package managers, you'll make them very upset.

I misunderstood how dotnet works and passed dll to the "dotnet run" command and it told me to have the particular version of the framework installed for the program i was trying to run.

Can you list step by step how you're installing .NET Core?

pacman -Syu dotnet-sdk
and also tried
yay -S donetn-sdk-bin and yay -S dotnet-sdk-preview

Can you list step by step how you're installing .NET Core?
https://dotnet.microsoft.com/download/dotnet-core/thank-you/sdk-3.1.102-linux-x64-binaries

also I used this guide (but for another dotnet version) as well. After I messed up installing runtime, I deleted the executable from the usr/bin folder and messed up everything

pacman -Syu dotnet-sdk

That should do it. If you have ever deleted some files related to one of dotnet packages then try reinstalling all of them with pacman -Syu dotnet-host dotnet-runtime dotnet-sdk. After that you should have /usr/bin/dotnet as a symlink to /usr/share/dotnet/dotnet binary (both files are owned by dotnet-host package). Also make sure you don't have some broken dotnet stuff in /usr/local, because it will conflict with packages.
And if you need some other version of .NET Core, then dotnet-{runtime,sdk}-{2.1,3.0} from AUR should integrate nicely with dotnet-host from official Arch repo.

pacman -Syu dotnet-sdk

That should do it. If you have ever deleted some files related to one of dotnet packages then try reinstalling all of them with pacman -Syu dotnet-host dotnet-runtime dotnet-sdk. After that you should have /usr/bin/dotnet as a symlink to /usr/share/dotnet/dotnet binary (both files are owned by dotnet-host package). Also make sure you don't have some broken dotnet stuff in /usr/local, because it will conflict with packages.
And if you need some other version of .NET Core, then dotnet-{runtime,sdk}-{2.1,3.0} from AUR should integrate nicely with dotnet-host from official Arch repo.
(Although dotnet-sdk-3.0 will conflict with dotnet-sdk because of duplicated netstandard targeting pack that exists in both packages.)

installing all 3 together helped, it seems to work now, thank you a lot


Add source type: module

What would this fix for you? Also, we're moving to LernaJS so merging this will be a bit delayed.

One of my projects is also using es6 modules. Are we able to figure how to support es6 modules without extra configuration?

Full ES6 support is a bit of an issue unfortunately. The module we use to genrage code is no longer supported and the module that I want to use instead isn't documented well enough to easily implement it

@simondel it seems to work fine for me with ES6 code as long as I either use babel-node or Node v7 + sourceType: module. What are the other ES6 issues that need to be resolved?

Hmm. I tried to clone your fork and npm link it without any luck. Am I missing something @jeznag ? Id love to use it with node 7. My hypothesis is supporting babel / node 7 would get a lot more visibility in the community.

@SxMShaDoW what errors do you get using it with NodeV7? It works fine for me. To handle import statements, I've had to change the stryker exec to have #!/usr/bin/env babel-node

@jeznag - I got similar error to the travis ci job
Compiling...
Using tsc v2.2.1
src/utils/parserUtils.ts(29,50): error TS2345: Argument of type '{ comment: boolean; loc: boolean; sourceType: string; range: boolean; tokens: boolean; }' is not assignable to parameter of type 'Options | undefined'.
  Type '{ comment: boolean; loc: boolean; sourceType: string; range: boolean; tokens: boolean; }' is not assignable to type 'Options'.
    Types of property 'sourceType' are incompatible.
      Type 'string' is not assignable to type '"script" | "module" | undefined'.

thus I wasn't able to npm link it.
As far as the changes to stryker exec for imports, you should include the file change as well if people wan tot handle imports :). Still hoping a solution will exist in the future.
Would love to see this work with create-react-app out of the box.

We won't fix this for now. We will fix it when supporting es6. See also https://github.com/stryker-mutator/stryker/issues/101


Add isDefinition to references

This allows clients to distinguish definitions from usages. I used this to change tide to behave more like  Resharper: tide-references now jumps directly to a single usage if only one usage and one definition exist. For example,
function f() {
  const once/*1*/ = 12;
  const twice/*2*/ = 13;
  const thrice/*3*/ = twice + 1;
  return once + twice + thrice + thrice + thrice;
}

If you get all references at /1/, you'll jump straight to the return line. If you get all references at /2/, you'll get the normal buffer listing references. Because of the deduping logic I wrote for tide, /3/ will behave the same as /1/ since all references are on the same line. But that's not necessarily the right thing.
@andy-ms I believe you were interested in this for Sublime too. @zhengbli, can you look at this and say whether it's the right approach?

i would add a test for a binding pattern, import/export, string literal names property, computed property, and numeric named property.

👍


luci-theme-openwrt-2020: add missing css success color

This fixes #4734
I would also cherry-pick this to openwrt-21.02 if this works for @ajayramaswamy you.

Nitpicking, but the commit title (and the PR title) talks about luci-theme-openwrt, while it actually concerns another theme, luci-theme-openwrt-2020

Yes I confirm that this works for me. I put the cascade.css on the router directly and now the color is correct. Thank you.


Minifying required html/css

What's the best way to go about minifying or applying other transforms on the files that partialify requires? I realize that partialify shouldn't be responsible for the minification. Is this a feature that should be added to partialify or does browserify already support nesting transforms in this way?

+1 on this. @tjconcept, did you plan to work on that PR still? If not, I might be willing to pick it up.

Funny thing I actually revisited this last night, and had an in-my-head discussion on whether this was the right approach.
The problem with partialify in general (and a lot of similar modules) is that they "extend" the language. This is never going to work in anything else than a browserified context. This is contrary to a module like https://www.npmjs.com/package/brfs.
The result? Two very specific modules: https://github.com/paylike/bryles and https://github.com/paylike/brarkup. They will actually run in node as well.
These modules are of course way too tailored. It might be possible to implement independent static transforms for jade/slim, clean-css, Autoprefixer and Stylus in stead.


Wave disappears after loading subsequent files with the MediaElement backend

In Chrome (not an issue in Safari/FF).
The waveform disappears after loading a subsequent audio file. The issue is demonstrated clearly on this playlist example page when clicking another play button:

http://www.wavesurfer.fm/example/playlist/
It's also apparent on the main page when dragging and dropping a new audio element:
http://www.wavesurfer.fm/

I can't reproduce. The previous waveform does disappear, because it loads the new one. GitHub (which hosts the website) is very slow to serve media files for some reason. But in a couple of seconds a new file appears, that's what I see.

Still seeing the issue, I'm on Version Chrome 42.0.2311.90 (64-bit) on OS X 10.10.13

Do you see any errors in the console?
What exactly is the sequence of steps you perform to observe the bug?

I navigate to the page, the first wave renders correctly and the waveform shows.
Then I click play on another song in the list, the wave disappears. It never returns, even when going back to the initial wave.
See video:
http://dropshots.com/micahlisonbee/date/2015-04-23/13:39:23

I see this issue too. Chrome on OSX.

Same error here, it only happens to me when init wavesurfer with AudioElement backend.

I was having the same issue; glad to see I'm not the only one.  This was particularly noticeable for me in Firefox (Linux) and both Chrome and Firefox (Windows).  Chrome seems to handle it more wisely.
By any chance are you initializing Wavesurfer when its DOM element is hidden, has a w/h of 0, or any other kind of display property that might prevent the element from not being accessible?
The above scenario was true in my case, and I 'fixed' the issue by attempting to instantiate Wavesurfer once its particular page area was visible.  Then I stored a flag to denote it had been loaded rather than trying to re-init each time.  This resolved the issue in Chrome / Windows (44.0) for me anyways.

Accidentally commented on a different issue.
On this topic, are you calling .empty() on your wavesurfer object in-between file loads?

Sorry, missed your reply. Yep am calling empty between file loads. As a temporary workaround I've found calling redrawBuffer on a timeout means that it now works across the board. Not ideal, but does the job!

Seeing this on Chrome 48.0.2564.116 (64-bit) on Mac OS X El Capitan (10.11.3). Safari functions fine.

closing, working fine on chrome 59+

I know this is closed but just in case someone else has this issue like I did I found it was because I had created WaveSurfer with the partialRender option true.  I set it to false or just don't include it when you create the WaveSurfer object because it defaults to false.


Implements argmin()/argmax() for Index/MultiIndex

https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.Index.argmax.html#pandas.Index.argmax
>>> kidx = ks.Index([10, 9, 8, 7, 100, 5, 4, 3, 100, 3])
>>> kidx
Int64Index([10, 9, 8, 7, 100, 5, 4, 3, 100, 3], dtype='int64')

>>> kidx.argmax()
4
>>> kidx.argmin()
7

and not support for MultiIndex like pandas.
>>> midx = ks.MultiIndex([[100, 200, 300],
...                       [50, 60, 70]],
...                      [[0, 0, 0, 1, 1, 1, 2, 2, 2],
...                       [1, 1, 1, 1, 1, 2, 1, 2, 2]])
>>> midx.argmax()
Traceback (most recent call last):
...
TypeError: reduction operation 'argmax' not allowed for this dtype
>>> midx.argmin()
Traceback (most recent call last):
...
TypeError: reduction operation 'argmin' not allowed for this dtype

Codecov Report

Merging #1162 into master will decrease coverage by 2.51%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1162      +/-   ##
==========================================
- Coverage   95.21%   92.69%   -2.52%
==========================================
  Files          35       35
  Lines        7061     7077      +16
==========================================
- Hits         6723     6560     -163
- Misses        338      517     +179

Impacted Files
Coverage Δ

databricks/koalas/missing/indexes.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/indexes.py
96.85% <100%> (+0.18%)
:arrow_up:

databricks/koalas/internal.py
96.53% <100%> (+0.03%)
:arrow_up:

databricks/koalas/usage_logging/__init__.py
24.32% <0%> (-72.98%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
78.72% <0%> (-6.39%)
:arrow_down:

databricks/conftest.py
92% <0%> (-6%)
:arrow_down:

databricks/koalas/frame.py
93.74% <0%> (-3.27%)
:arrow_down:

databricks/koalas/groupby.py
89.6% <0%> (-2%)
:arrow_down:

databricks/koalas/namespace.py
85.97% <0%> (-1.53%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


Serial output too fast

@hamachiwa
When running the rc_driver.py (or nn only), the forward output responses on a straight track comes too fast and quickly (I get 10 forward responses in just 1 second). Due to this my car is unable to keep up and even if I terminate the code (i.e. rc_driver.py) it keeps on running straight unless I plug out the arduino cable. Any solution?

yeah buddy i'm facing the same issue the frames are slow and the prediction and frames are out of sync . when i slowly move my camera around the track it predicts well. Solution is either to increase the frame rate or to reduce the car speed

Slowing the car will make the problem worse. My car is slow enough, but the serial output rate is just too fast. I need a way to reduce the rate of serial output (like three forwards per second or three forward rights per second). Also my camera is fine and the frame rate is satisfactory. The only problem is the serial output rate.

@VishalWrench BTW did you successfully train your car?

I found the solution to my problem. Closing thread

How did u solved it??
On Thu 4 Apr, 2019, 8:26 PM MyFirstRoboticProject<EMAIL_ADDRESS>wrote:

Closed #188 https://github.com/hamuchiwa/AutoRCCar/issues/188.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hamuchiwa/AutoRCCar/issues/188#event-2253219054, or mute
the thread
https://github.com/notifications/unsubscribe-auth/At7cbgbRaruWvcxopSDtwNtXmtVkGZmyks5vdhKugaJpZM4cafFf
.

Well, the output serial data would change instantaneously regardless how fast it was, so it didn't matter. And also if you want to achieve a greater accuracy for training make the driving path as narrow as possible.

have you made your car by your self? @MyFirstRoboticProject

No. Used a normal rc car

Have you code for cr's motor to control it's speed? @MyFirsrRoboticProject
On Fri 5 Apr, 2019, 6:12 PM MyFirstRoboticProject<EMAIL_ADDRESS>wrote:

No. Used a normal rc car
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hamuchiwa/AutoRCCar/issues/188#issuecomment-480261267,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Asnmx8U26ZhtmQq1PbuN5wPGoEYJ77hUks5vd0SqgaJpZM4cafFf
.

Yup. Not an ideal solution though. I'm trying to find some other way to slow my car's speed (other than using a potentiometer or a resistor)

I am having the same problem everything is working properly but car is very fast so it's not working properly.
If you find the solution plz let me know.
Thanks for your help

Ok


unable to use Alamofire 1.3.1 to support iOS7?

I got the error below when installing the podfile to the project, as the app should support iOS7, I wrote "pod 'Alamofire', '<=1.3.1'" in the podfile.
[!] Unable to satisfy the following requirements:

Alamofire (<= 1.3.1) required by Podfile

Specs satisfying the Alamofire (<= 1.3.1) dependency were found, but they required a higher minimum deployment target.
Any sugguestions?

Check the README for version 1.3.1

Embedded frameworks require a minimum deployment target of iOS 8 or OS X Mavericks

It's not possible to use CocoaPods or Carthage to integrate Alamofire on iOS 7 since they use frameworks to integrate and thus require iOS 8 onwards.
Check the instructions at https://github.com/Alamofire/Alamofire/tree/1.3.1#source-file

ths! :+1:


align color to depth

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
4.15.0-36-generic

Platform

SDK Version
2.x - from apt

Language
python

Segment

Issue Description
I have some trouble getting the depth aligned color data.
This code:
import matplotlib.pyplot as plt
import numpy as np
import pyrealsense2 as rs
pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)
profile = pipeline.start(config)
frames = pipeline.wait_for_frames()
align_to = rs.stream.depth
align = rs.align(align_to)
aligned_frames = align.process(frames)
fig, ax = plt.subplots(1,2, figsize=(12,12))
ax[0].imshow(np.asanyarray(aligned_frames.get_color_frame().get_data()))
colorizer = rs.colorizer()
ax[1].imshow(np.asanyarray(colorizer.colorize(aligned_frames.get_depth_frame()).get_data()))

produces:

And in case the config does not enforce the same resolution for both stream, then align.process does crash.
The rs-pointcloud example does work perfectly though.

Hi @toinsson
I can't see anything immediately wrong with your code.
I did try to run the distance to object  notebook, and replaced Stream Alignment section with:
# Create alignment primitive with **depth** as its target stream:
align = rs.align(rs.stream.depth)
frameset = align.process(frameset)

# Update color and depth frames:
aligned_color_frame = np.asanyarray(frameset.get_color_frame().get_data())

# Show the two frames together:
images = np.hstack((aligned_color_frame, colorized_depth))
plt.imshow(images)

Maybe something in this example can help you find the problem...

thanks for the quick reply. It is the same code indeed. I'll do a fresh reinstall and see if this problem disappears.

Seems like the issue was in pyrealsense2. Was using v<IP_ADDRESS>4. Move up to v<IP_ADDRESS>1 and it works now. Sorry for the noise.

@dorodnic  I have tried the example that you have mentioned above. I am pointing my camera to a flat surface and I have corresponding RGB plus depth. Check out the image uploaded below.

Later I replace the whole depth value with a mean value as the depth is supposed to be constant for a flat surface.  When I calculate "aligned_color_frame", I get the following result.

I don't know why I am still getting holes in the aligned_color_frame even though the depth has no holes?
I will add my code snippet below:
Stream Alignment
Create alignment primitive with color as its target stream:
align = rs.align(rs.stream.color)
frameset = align.process(frameset)
Update color and depth frames:
aligned_depth_frame = frameset.get_depth_frame()
colorized_depth = np.asanyarray(colorizer.colorize(aligned_depth_frame).get_data())
mean_depth = np.mean(colorized_depth)
print(mean_depth)
#colorized_depth[colorized_depth >= 0] = mean_depth
Show the two frames together:
images = np.hstack((color, colorized_depth))
plt.imshow(images)


The operator client running failed and throw ClassNotFoundException due to the the necessary jar was not added in the classpath

Date: 2016/07/01
[Steps to reproduce]

Enter the folder of "operatorclient";
Open a command line, input "ant -f build.xml";
Include the "oscm-rest-api-interfaces.jar" into the lib of "operatorclient";
Open the command line and "ant -f build.xml" again.

[Expected result]
In step 4, the operator client can be build successfully.
[Observed result]
In step 4, the operator client build failed and the " ClassNotFoundException" was thrown.
[Details]
The new added “oscm-rest-api-interfaces.jar” was not added in the class-path of the oscm-operatorsvc-client, please see the attachment.

I refactored the api and removed the dependency, shouldn't be a problem anymore.

does that mean it has been changed in master?

yes, i just merged my changes

verified by FNST
[verified-build]20160715094705
[verified-details]Copy all the related jar to operatorclient, then execute the "ant -f build.xml" command, it is OK, so verified.


peerDependencies problem

Hi and thanks for the great tutorial and the effort that you put into it, really like it!
Here is a problem I cannot solve myself:
Running npm install --save-dev eslint eslint-config-airbnb eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-react (Chapter 06) results in
npm WARN package.json<EMAIL_ADDRESS>No description
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No README data
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from eslint-config-airbnb will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Darwin 15.6.0
npm ERR! argv "/Users/Johannes/.nvm/versions/node/v4.5.0/bin/node" "/Users/Johannes/.nvm/versions/node/v4.5.0/bin/npm" "install" "--save-dev" "eslint" "eslint-config-airbnb" "eslint-plugin-import" "eslint-plugin-jsx-a11y" "eslint-plugin-react"
npm ERR! node v4.5.0
npm ERR! npm  v2.15.9
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Johannes/Documents/3_code/node/npm-debug.log

How can I get past this error?

My friend and js-expert @ryppyy just showed me how to make this work. Basically, you need to specify the version of the eslint-plugin-import module, like so:
npm install --save-dev eslint eslint-config-airbnb<EMAIL_ADDRESS>eslint-plugin-jsx-a11y eslint-plugin-react
Works for me.

I see you are using Node v4.5.0. I had this kind of issue in 4.x, but not in 6.x+, maybe try upgrading? That should solve the issue :) In 6.x+ it doesn't crash when it finds unmet peer dependencies.
Your solution is good for 4.x though, thanks!


WIP Getting simple box example to work

closes #5
TODO:

[x] vertex buffers
[ ] index buffers
[ ] uniforms
[x] let material define compute shaders
[ ] python-shader support for matrices (and multiplying with vectors)
[ ] take camera into account
[ ] take world transform into account
[ ] Skim over all todo's that were added

Resolved #5

Ok, things are more or less working. The triangle example and the qt-embedding example work again. The box example draws something on my machine, but that's because I have made changes to wgpu that I have yet to push :)


removed kie-dmn-bom leftovers

depends on https://github.com/kiegroup/submarine-bom/pull/14

asking @mariofusco and @tarilabs to review, since the build has broken, but I am not sure what the current layout for DMN is on submarine


Updating 'to-many' relationships through PUT

If a to-many relationship is included in the links section of a resource object, it MUST be an object containing:

type and ids members for homogeneous to-many relationships; to clear the relationship, set the ids member to []
a data member whose value is an array of objects each containing type and id members for heterogeneous to-many relationships; to clear the relationship, set the data member to []

http://jsonapi.org/format/#crud-updating-resource-to-many-relationships

Update should also include to-many linked relationships.
http://jsonapi.org/format/#crud-updating-to-many-relationships


Clarification on setting up MOM5 velocity data for 3D advection

Hi parcels team. I’m trying to compute 3D advection with B-grid MOM5 velocities. I've seen some discussion of B-grid interpolation here and in this documentation example, however I’m still a bit confused about the vertical dimension setup and am looking for some clarification.
In the MOM5 data, u, v, and w have the following dimensions:
u (st_ocean, xu_ocean, yu_ocean)
v (st_ocean, xu_ocean, yu_ocean)
w (sw_ocean, xu_ocean, yu_ocean)

The vertical velocity w and the vertical coordinate for the velocity cells (sw_ocean) are defined on the bottom interface of the tracer cell such that the uppermost w value is located at the bottom of the surface layer and there is no w data for the surface at 0 m. The sw_ocean coordinate starts at 1.08 m and extends down to ~5800 m (increasing down). From the documentation example  and this section of the code, I understand that parcels wants the u, v and w velocities defined at the same point in the top corner of the grid cells. Because of this I modified sw_ocean by shifting it up one cell with a zero at the surface so that sw_ocean_mod now extends from 0 to ~5600 m. I’ve then been setting up parcels as follows:
ufiles = 'datapath/ocean_ufile.nc'
vfiles = 'datapath/ocean_vfile.nc'
wfiles = 'datapath/ocean_wfile.nc'
mesh_mask = 'datapath/Southern_Ocean_coordinates.nc'

filenames = {'U': {'lon': mesh_mask, 'lat': mesh_mask, 'depth': mesh_mask, 'data': ufiles},
              'V': {'lon': mesh_mask, 'lat': mesh_mask, 'depth': mesh_mask, 'data': vfiles},
              'W': {'lon': mesh_mask, 'lat': mesh_mask, 'depth': mesh_mask, 'data': wfiles}}

variables = {'U': 'u',
             'V': 'v',
             'W': 'wt'}
dimensions = {'U': {'lon': 'geolon_c', 'lat':'geolat_c', 'depth':'sw_ocean_mod', 'time':'time'},
             'V': {'lon': 'geolon_c', 'lat': 'geolat_c', 'depth': 'sw_ocean_mod', 'time': 'time'},
             'W': {'lon': 'geolon_c', 'lat': 'geolat_c', 'depth': 'sw_ocean_mod', 'time': 'time'}}

fieldset = FieldSet.from_b_grid_dataset(filenames, variables, dimensions, field_chunksize=(1,7,300,400))
fieldset.W.set_scaling_factor(-1)  # set scaling factor for vertical velocities to -1

Is this the correct way to assign the vertical coordinate for these MOM5 b-grid velocities? I’m currently having an issue with particles getting stuck at the bottom of the ocean prompting me to think there may be something wrong with my set up. This also happens if I use the original sw_ocean coordinate. Should the vertical coordinate have a value at both the ocean surface and the ocean floor? In which case the dimensions of sw_ocean would not be equal to the vertical dimension of w, and I would perhaps need to add a layer of zeros to w inside the parcels code at the surface – something like this for pop interpolation.
Ideally I want to give parcels a 3D array of depth to account for bottom shaved cells used in the model, but I first want to understand the correct set up using a Rectilinear Z grid. Any help is greatly appreciated! I’m happy to share some code and/or data if that assists at all.

Thanks @hrsdawson, for this elaborate and very detailed comment/question! You clearly really dug into this quite a bit already. I'm not really sure how much I can help you further, our grid interpolation guru, @delandmeterp, has taken up another position so is not officially part of the Parcels team anymore. I assume you've also looked at section 2.1.3 of his GMD paper, which specifically deals with 3D B-grids?
That said, here are some thoughts:

Assuming that W is indeed zero at the ocean surface in MOM, it could make sense to add a layer of zeros at the surface. You could either adapt the Parcels code itself, but that is somewhat cumbersome; alternatively, it might be possible to first open the data with ds=xarray.open_mfdataset(...), add a layer of zeros in this xarray DataSet (?), and then convert the DataSet to a FieldSet using FieldSet.from_xarray_dataset(ds, ...)
If you follow step 1 above, be careful what to do with U and V too. Does the first level of these then correspond to the depthw=0? You'll need to think about that
Shaved cell support is indeed something that has been on my wish-list for a long time! Let me know how this goes

Perhaps it would be good to engage some of the MOM developers too, to further discuss them with this? @StephenGriffies, would you happen to know who we could ask for advice in figuring out using Parcels with MOM5 fields?

Hi @erikvansebille, thanks for the quick reply and the suggestions.  Looks like I might need to do some more digging. Yep I have seen that section of the paper. I should have also mentioned above that some of my confusion is arising from this contributed OFAM example, which has the same dimensions as above, but uses the vertical tracer cell coordinate (st_ocean) for the depth dimension, rather than the vertical velocity coordinate (sw_ocean). I can see that a line setting up dimensions with sw_ocean has been commented out. Should I be using the vertical tracer coordinate as in this OFAM example?

Ah, that may be a bug in https://github.com/OceanParcels/parcels_contributions/blob/master/Examples/example_OFAM3.py. @CKehl, do you remember why you used 'st_ocean', rather than 'sw_ocean'?

Hi,
Here are some comments.
1/ wt is not zero at the top model grid cell in MOM5.  The model uses an explicit free surface that is fully nonlinear. And when using z* vertical coordinates, all grid cells have a time dependent thickness.
2/ The wt field in MOM5 is registered with the following axes
id_wt = register_diag_field ('ocean_model', 'wt', Grd%vel_axes_wt(1:3), Time%model_time, &
'dia-surface velocity T-points', 'm/sec', missing_value=missing_value, range=(/-10.e4,10.e4/))
where vel_axes_wt places the wt velocity at the center of the tracer cell top/bottom.  I am unsure of the st_ocean and sw_ocean grid definitions you refer to.  These are static.  The correct static analog to the wt grid is indeed the sw_ocean grid.
3/ Veronica Tamsitt<EMAIL_ADDRESS>is actively using Parcels with MOM5 output.  I suggest connecting with her for further details.

Thanks Erik and Steve. @hrsdawson is doing her PhD with Matt England, myself and @vtamsitt. Veronica is still using CMS with MOM5, not Parcels yet. We're trying to switch everyone over to Parcels, starting with @hrsdawson.
A couple of points in reply to the above:
1/  To start with we are trying to get Parcels working with the approximation of stationary z layers, rather than z*. This is what we did for CM2.6 with CMS @StephenGriffies. Do we know how large the errors are for this approximation? I guess we will also have problems with particles trying to leave through the surface due to this approximation. We could in time work on setting up Parcels to represent the time-varying z* layers using the Curvilinear S Grid implementation, if we think it is worth it.
2/  Regarding what w values to insert at the surface, perhaps the best option would be to make a copy of w from the bottom of the top z layer (i.e. the uppermost w that we have saved), rather than zeros?
Erik, I don't think your point 2. above about matching the correct u/v to this new surface w is an issue. As I understand it for b-grids in Parcels, it is expected that there will be a w value at the uppermost surface (i.e. half a grid cell above u/v). But we are currently missing that uppermost w value.

Thanks @adele157 for clarification: My mistake forgetting that CMS was still in use.
I also wish to clarify my comment 2/ above.  The wt velocity is indeed defined at sw_ocean.  This setting is specified in
https://github.com/mom-ocean/MOM5/blob/master/src/mom5/ocean_core/ocean_grids.F90
which is the latest MOM5 Github repo.  I see no substantial changes in that file since 2014, though not sure if there was a change made before that effects this discussion.

In regards to @adele157 comment about stationary z-levels rather than z*.  I am not sure what is meant.  Is it related to the following?
Namely, the wt diagnosed in a z* configuration of MOM5 measures the transport through the z* coordinate surface.  This transport is distinct (but only by a bit) from the transport through a z-coordinate surface.
Let's write wt* for the vertical velocity diagnosed in z*-coordinate configuration and write wt for the transport diagnosed in a z-coordinate configuration.  Are you concerned about the difference between wt* and wt for use in particles?   That difference is very small in general, and it is a difference I never bothered with.  But do you think it is a difference that has qualitative impact on particle trajectories?  Or perhaps there is an issue at the boundaries?

Hi @adele157

1/ To start with we are trying to get Parcels working with the approximation of stationary z layers, rather than z*. This is what we did for CM2.6 with CMS @StephenGriffies. Do we know how large the errors are for this approximation?

There's two types of errors here. The one that @StephenGriffies described above (the difference between wt* and wt), and another that the interpolation of U and V depends on the particle's position in the grid, so that if the depth layers move up and down, the particle's relative position in the grid moves too, even if the particle's depth doesn't change. But again, I expect that this difference is very small?
In any case, it might be a good idea at some point to compare particle trajectories assuming a fixed depth grid to particle trajectories using the time-varying cS-grid implementation. I'd be keen to see how big the difference is!

Ah, that may be a bug in https://github.com/OceanParcels/parcels_contributions/blob/master/Examples/example_OFAM3.py. @CKehl, do you remember why you used 'st_ocean', rather than 'sw_ocean'?

That was based (a) of the use case we chose at that point and (b) of the variable declarations in the NetCDF file. It can be chunked either way, it just depends on how the dimensions are linked as variable parameters in NetCDF.

Hi everyone!
I add something here as it might be interesting for the MOM5 community.
We found that when creating the fieldset with from_mom5(), it was not accounting for the grid rotation (especially important in the Arctic). We found a way to solve that by modifying the Kernel AdvectionRK4_4D to include the curvilinearity of the grid. This has been solved in #1509, don't hesitate to check it out if you are working in the Arctic!


How to preset fields?

I would like to invite a user AND preset their role value to something e.g. invite one person as an admin and another as a regular user. Is this possible using this gem?

I don't see why that should be the responsibility of this gem.

With devise, you can use different models for user and admin,in that case, you can enable invitations for both models. If using only one model, you need to override invite_resource of invitations controller, as explained in README, Configuring controllers section. In the block, set the role instead of setting skip_invitation


Leaking TraceViewerWidget instances

At post-construction, the trace viewer widget adds a color theme change listener to the ThemeService and a Tsp client change listener to the Tsp client provider, but these listeners are not removed when the widget is disposed. This causes the trace viewer widget instance to leak.

Picking up this issue