Object Reference not set to an instance of an object [System.Null Reference Exception]

Describe the problem
Love City Skylines - In the last week or so the game has been crashing randomly between 1 minute to an hour and half. I thought the crashes may have been a bad asset -as I had a error message "HSDGCZT5:LOD too many vertices / Object reference not set to an instance of an object" - removed all the assets I had added over the last week, and thought well I guess that's fixed and then last night it crashed again.
Steps to reproduce

I just play the game -BUT I wonder if I have too many assets I played for about 42 minutes and then the game threw up the error message and I had to open the task manager to kill cities.exe.

Then the game works and I can play for 45 minutes to an hour?
Then this:

Log files

https://ufile.io/9s6hhiu2
https://ufile.io/fxm0z0p7
Savegame?

Screenshots?

Notes or questions?
I found this submission area -by accident and I apologize if this is not the kind of thing you assist with -I'm not sure I found a bug I think I may be misusing the mods or the the assets? Thanks, Walt

I suspect some ancient incompatible assets from workshop. That one which throws errors, for sure. Not much I can do
It's not related with this mod.

Thanks for getting back to me, I was able to figure it out -but I
appreciate the response! Thanks again, Walt
On Tue, Nov 17, 2020 at 2:01 PM Krzysztof<EMAIL_ADDRESS>wrote:

I suspect some ancient incompatible assets from workshop. That one which
throws errors, for sure. Not much I can do
It's not related with this mod.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CitiesSkylinesMods/TMPE/issues/996#issuecomment-729135837,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQWWJADMJ5S75CZVHJOTMYDSQLCBVANCNFSM4QIPA2BA
.

Thanks for getting back to me, I was able to figure it out -but I appreciate the response! Thanks again, Walt
…
On Tue, Nov 17, 2020 at 2:01 PM Krzysztof @.***> wrote: I suspect some ancient incompatible assets from workshop. That one which throws errors, for sure. Not much I can do It's not related with this mod. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#996 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQWWJADMJ5S75CZVHJOTMYDSQLCBVANCNFSM4QIPA2BA .

Can you please share your solution... or what the cause of this message was.. I am experiencing this now, myself. Thanks!

Can you please share your solution... or what the cause of this message was.. I am experiencing this now, myself. Thanks!

You can't say it's the same issue just because seeing it was NullReferenceException. It's one of the most generic error possible which means more or less: something went wrong, code expected some data in memory but it's not there, so something is missing.
The easiest way to get help is contacting support volunteers over Cities skylines discord text chat server (I'm pretty sure the invite is still available from paradox launcher). Just prepare output_log.txt (or Player.log if MacOS or Linux) log location from the game session where error occurred or just check it yourself.
I'm 99.999% sure this mod is not the source of that error, neither the vanilla game itself. You can try also on TM:PE discord server but we don't really provide support for general issues not related with the mod (it's just too much to handle, there are better places)


Input from soundcard

In https://github.com/windytan/redsea/wiki/Use-cases#decoding-mpx-from-a-file-or-via-sound-card there is a howto when I want to use my 192kHz soundcard to feed it into redsea
But in my case, this did not work as everything above 48kHz was filtered out, see screenshot.

$ rec -t .s16 -r 171000 -c 2 - | redsea
rec WARN alsa: can't encode 0-bit Unknown or not applicable

Input File     : 'default' (alsa)
Channels       : 2
Sample Rate    : 171000
Precision      : 16-bit
Sample Encoding: 16-bit Signed Integer PCM

In:0.00% 00:00:08.53 [00:00:00.00] Out:1.45M [      |==-   ]        Clip:0    ^C
Aborted.

I found out that I need to specify the below mentioned parameters and used -q which stands for quiet.
AUDIODEV=hw:2,0 AUDIODRIVER=alsa rec -t .s16 -r 171000 -c 1 - -q | redsea -E

$ AUDIODEV=hw:2,0 AUDIODRIVER=alsa rec -t .s16 -r 171000 -c 1 - -q | redsea -E
rec WARN formats: can't set sample rate 171000; using 176400
rec WARN formats: can't set 1 channels; using 2
{"pi":"0xA201","group":"14A","bler":0,"other_network":{"pi":"0xA213","kilohertz":98600,"tp":false},"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"3A","bler":0,"open_data_app":{"app_name":"RDS-TMC: ALERT-C","oda_group":"8A"},"prog_type":"No PTY","tmc":{"system_info":{"is_encrypted":false,"is_on_alt_freqs":true,"location_table":1,"scope":["national"]}},"tp":false}
{"pi":"0xA201","group":"8A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":0,"di":{"stereo":true},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"2A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"14A","bler":0,"other_network":{"pi":"0xA213","prog_type":"No PTY","ta":true,"tp":false},"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":0,"di":{"dynamic_pty":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}

But due to the hint in the output this might be better:
$ AUDIODEV=hw:2,0 AUDIODRIVER=alsa rec -t .s16 -r 192000 -c 1 - -q | redsea -E -r 192000
rec WARN formats: can't set 1 channels; using 2
{"pi":"0xA201","group":"2A","bler":4,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"8A","bler":4,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":4,"di":{"dynamic_pty":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"14A","bler":4,"other_network":{"pi":"0xA502","kilohertz":97000,"tp":false},"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":4,"di":{"compressed":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"8A","bler":4,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":4,"di":{"artificial_head":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"14A","bler":4,"other_network":{"pi":"0xA502","kilohertz":99600,"tp":false},"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","ps":"  OE 1  ","alt_frequencies_b":{"tuned_frequency":87700,"same_programme":[90900,92800]},"bler":4,"di":{"stereo":true},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"2A","bler":4,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"8A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":0,"di":{"dynamic_pty":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"2A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"14A","bler":0,"other_network":{"pi":"0xA502","kilohertz":95600,"tp":false},"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"8A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"0A","bler":0,"di":{"compressed":false},"is_music":true,"prog_type":"No PTY","ta":true,"tp":false}
{"pi":"0xA201","group":"2A","bler":0,"prog_type":"No PTY","tp":false}
{"pi":"0xA201","group":"14A","bler":0,"other_network":{"pi":"0xA502","kilohertz":95900,"tp":false},"prog_type":"No PTY","tp":false}

Soundcard stuff can be highly platform specific. I suspect some devices may even silently upsample without providing the requested bandwidth...
I actually opened the wiki so it should be editable now. Would you be willing to add a short explanation about this in the wiki? Just something simple about the alternative recording command.

I forgot to mention, this is Ubuntu 64bit


If there isn't a tile, consider it blocked (note: this should probably factor in ignoreMissingTiles)

My layers were not in the correct order. Closing.
https://discord.com/channels/1033320723105730611/1115684925019005050/1317594113066926192


mage test:all should produce a combined code coverage result

If we add the -coverprofile flag to ever go test func in magefiles/test.go, we can aggregate them all into a single coverage file in All().
This'll be useful to track (perfect coverage is a non-goal of the project), but is also required for submitting to awesome-go

Hi, i'm interested in contributing to this!

@sephialaureenciaa thanks! have you checked out the CONTRIBUTING file? That should be all you need to get started and we'd welcome a pull request. If there's anything about the contribution guidance that seems like it's missing or confusing we'd also like to hear about it.


WIP: feat: Implement customize hook

Implementation of https://metacontroller.app/design/customize-hook/
This doesn't need review yet, but might be interesting to others to see progress/ideas

@enisoc So I'm thinking that the way to do this is for parentController to create individual objects per Parent, and maintain all of these in memory?
And on a parent update, call the customize hook again, and recreate the parent object, like is done when a CompositeController is updated?

Yeah that matches what I was imagining. Essentially we'd have an in-memory cache of customize hook responses (if the hook is defined) that gets invalidated whenever the parent spec changes. We don't want to invalidate the cache every time we update the parent status (which also updates metadata.resourceVersion), since that defeats the purpose.
The cleanest way to do that is to remember the metadata.generation of the parent object that resulted in a given customize response. This means the related resources feature will only work for CRDs with true /status subresource handling turned on, but I think that's ok as long as we document it (and maybe validate it at runtime?). In general, it's recommended for everyone to enable that on CRDs that follow the usual controller pattern.

As a suggestion for prototyping: semantically we want this to be exactly like if we called the customize hook every time just before we call sync. You can prototype the API/UX and even write an integration test without worrying about the above caching yet. Just hard-code it to always call customize right before sync.

I whipped up an implementation for this on Kritzefitz:related-objects-impl. Should I open a new merge request or somehow attempt to merge my work into this one?

@Kritzefitz Thank you!
Feel free to start a separate PR. I haven't had time to work on this lately, so please carry on :)


Problem with Has Many Through Association Rails

class Document < ActiveRecord::Base
  has_many :sections
  has_many :paragraphs, through: :sections
end

class Section < ActiveRecord::Base
  belongs_to :document
  has_many :paragraphs
end

class Paragraph < ActiveRecord::Base
  belongs_to :section
end
Paper_Trail 4.0.0 Beta doesn't cater this situation. It looks for foreign key of association Paragraph i.e, section_id in the through model i.e, Section which will not be available in the above mentioned case.

Please see #466


Broken highlighting- no option to reset the environment

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Win 10
- Continue version: v0.8.59
- IDE version: Vscode 1.95.3
- Model: Codestral
- config.json:

Description
After some activity, often happens that the highlighting gets messed up and I have found no way to clear that up.
Closing and opening the file does not help.
Sometimes the accept/reject option does not appear, and as you try to delete suggested code manually, the highligthing stays fixed and everything turns into an utter nightmare. Pressing the ctrlShiftenter/esc does not help.

To reproduce
No response
Log output
No response

@edolis We are working on fixing the buttons not showing up. There should be updates in a pre-release soon. Otherwise, you can use cmd+shift+backspace/enter to reject/accept all changes

thanks, unfortunately as I wrote that does not fix it. Now I am thinking of renaming the file and deleting it, but having it in source control is just making things so painful.
also thought for asking a review of the whole code, but then I get an endless and arbitrary list of suggestions to remove my comments and so on. Which is another issue.
Together to the issue that the AI (codestral) sometimes abbreviates blocks of code and that is being pushed as a proposed deletion. Every time over and over again.
But these are other issues you can manage with local inserts. But which invalidate the use of asking full code review to clear that formatting issue.

Ah, OK, found a workaround. Need to restart VScode.

yes, that's a common problem. I can use it only on source control where I can compare version and roll back afterwards selectively.
So use only the insert at position option (and do the clean ups manually afterwards).
The arrow to apply the full code is workable only if, from the beginning, you have the whole code generated by the AI (so in very limited cases of small code chunks). It won't understand your commenting and using variable to extract parameters and so on

This is good feedback. I think it might be helpful in the future for us to add the ability to open a virtual diff view instead of directly writing to the editor, or at least give you the option to switch to this after the initial diff is shown

I'm facing this exact problem in PHPSTORM. Restarting also helps


MY COOKIE I NOT WORKING CAUSING ALL MY API FAILED IT WAS  WORKING FINE PREVIOUSLY BUT TODAY NOT WORKING

Expected Behavior
Error: [object Object] at Object.validate (C:\Users\DELL\AppData\Local\insomnia\app-9.3.0\resources\app.asar\node_modules\tough-cookie\lib\validators.js:91:13) at formatDate (C:\Users\DELL\AppData\Local\insomnia\app-9.3.0\resources\app.asar\node_modules\tough-cookie\lib\cookie.js:322:14) at Cookie.toString (C:\Users\DELL\AppData\Local\insomnia\app-9.3.0\resources\app.asar\node_modules\tough-cookie\lib\cookie.js:952:29) at wS1 (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:110:16004) at Ze (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/workspace-environments-edit-modal-Bf0HPEMW.js:1:16292) at Ok (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:43:17033) at NK (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:44104) at kK (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:39822) at Z9e (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:39748) at Yh (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:39598) at ME (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:35960) at EK (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:45:34907) at L (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:30:1594) at Immediate.oe [as _onImmediate] (file:///C:/Users/DELL/AppData/Local/insomnia/app-9.3.0/resources/app.asar/mainWindow-BuUzBfxG.js:30:1965) at process.processImmediate (node:internal/timers:478:21)I WANT TO FIX IT PLEASE
Actual Behavior
..
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
NO
Insomnia Version
9.3
What operating system are you using?
Windows
Operating System Version
WINDOW
Installation method
DOWNLOAD FROM WEBSITE
Last Known Working Insomnia version
3.9

+1

Same problem for us, the application crashes when we click on "Manage cookies" and the cookies are no longer sent. After closing the application and reopening it, I can access the "Manage cookies" window, but as soon as I send a request, the behavior returns to the same level. This is very annoying, as we can no longer request our API from Insomnia.

This is a duplicate of #7604

Please tell me how to solve this problem my uni project is pending
On Fri, 28 Jun 2024, 7:33 pm redbaran, @.***> wrote:

This is a duplicate of #7604
https://github.com/Kong/insomnia/issues/7604
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/insomnia/issues/7616#issuecomment-2197081564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDEUKRIHLNQ7YL4GPXYBSVDZJVX2NAVCNFSM6AAAAABKB6QV32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGA4DCNJWGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Turn off automatic updates (Application>Preferences)
Install the 9.2 version:
https://github.com/Kong/insomnia/releases/tag/core%409.2.0
https://github.com/Kong/insomnia/releases/download/core%409.2.0/Insomnia.Core-9.2.0.exe

Thanks for the feedback. Closing as this was fixed in 9.3.1


ISSUE #183 Adds del component

Issue https://github.com/basemate/matestack-ui-core/issues/XXX: Adds del component
Changes

[x] Adds the the del component to main components

Notes

Nothing special here

@cameronnorman I think if you merge the latest version of the develop branch into your issue-183 branch the CI won't complain anymore!

Hey @pascalwengerter @michaelrevans please can I get a review on this one now that the branch is up to date and passing


Cross repo tests for core PR #19620

Cross repo tests for core PR #19620 (ManageIQ::Providers::CloudManager::Template queue name).

@agrare or @Fryguy is this a real failure, or did I do something wrong again? Seemed to fail very fast.

Core PR was merged, closing.


Kinect Device Crash and Unresponsive

Using two new Kinect DK devices. Getting the same result with both. Connected them to my PC into two separate USB ports. I am able to reproduce this issue every single time. When I run Azure Kinect Viewer, both cameras are available. After I open either device and simply attempt to start it, I get IMU errors.
After the error messages, Kinect Viewer isn't able to detect either of the devices, even after I stop them. They completely disappear. I check the device manager and the devices are gone. I have to do a hard reboot to get the PC to see the devices again.
Below is the Log report:
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233733333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233766666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233800000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233833333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233866666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233900000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:1233933333
[ warning  ] : depth_engine_thread(). Dropping depth image due to bad timestamp at startup
[ warning  ] : imu_capture_ready(). IMU startup dropped last 368 samples, the timestamp is too large
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     16088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     49422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     82755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    116088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    149422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    182755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    216088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    249422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    282755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    316088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    349422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    382755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    416088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    449422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    482755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    516088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    549422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    582755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    616088 type:Depth
[ warning  ] : queue_disable(). Waiting for blocking call to complete
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : capturesync_add_capture(). Capture Error Detected, Depth
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ warning  ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu
[ error    ] : usb_cmd_io(). Error calling libusb_bulk_transfer for initial tx, result:LIBUSB_ERROR_NO_DEVICE
[ error    ] : usb_cmd_io(usbcmd_handle, cmd, p_cmd_data, cmd_data_size, NULL, 0, p_data, data_size, NULL, &cmd_status) returned failure in usb_cmd_write()
[ error    ] : usb_cmd_write(colormcu->usb_cmd, DEV_CMD_IMU_STREAM_STOP, NULL, 0, NULL, 0) returned failure in colormcu_imu_stop_streaming()

Hi @thedevguy, what OS are we talking about. The log indicates you are not getting color images from the camera. Please make sure you are not using an extra cables, make sure you are powered sufficiently with the device power supply provided in box. Then please review the USB host controller compatibility info below, and finally look for third party software and drivers that may be impacting your ability to use the color camera in the camera app (assuming we are talking about Windows here).
https://docs.microsoft.com/en-us/azure/kinect-dk/troubleshooting#usb3-host-controller-compatibility

OS: Windows 10
Not using any extra cables. Using what came in the box. Both devices are plugged into the wall charger using the wall charger that came in the box.

I've purchased a new USB card from Amazon for my PC (https://www.amazon.com/gp/product/B00HJZEA2S) that has 4 discreet Renesas controllers. Once I get the card I'll report on the issue.

I received and installed the usb controller that meets published specifications. The specifications are here: https://www.startech.com/Cards-Adapters/USB-3.0/Cards/PCI-Express-USB-3-Card-4-Dedicated-Channels-4-Port~PEXUSB3S44V
The kinect is detected however using the Kinect Viewer neither camera are available to open. When I try to refresh devices I get this error:
[ error    ] : find_libusb_device(). Unable to open LIBUSB at index 0
[ error    ] : usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[ error    ] : depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()
[ error    ] : find_libusb_device(). Unable to open LIBUSB at index 1
[ error    ] : usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[ error    ] : depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()

I have done the following trouble shooting steps:

installed new drivers for the usb card
unsinstalled the kinect dk sdk software and reinstalled it
scarified small goat

Here is a screen capture of how the device manager looks and how the viewer doesnt show the device listed.

The yellow triangles next to "Azure Kinect Depth Camera" and "Azure Kinect 4k Camera" indicate the two cameras are not enumerated successfully. You should be able to double click on the errored out devices to determine what the error is. Also please try multiple USB ports on the card, don't assume they are all exactly the same.

Wes here are what the devices show when I double click on the error-ed out devices. I have tried every port I have on the USB controller with no change to the error.

Can the Kinect DK work with Windows PCs that have AMD CPUs?

These devices should have WinUsb installed on them. I can't see the full history via the images. Not sure if you have some 3rd party software messsing with the WinUsb driver or not. You might try updating the driver and specifically telling Windows to use WinUsb.inf.

And yes, AMD CPU's work fine.

I had a similar problem,

[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42100000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42133333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42166666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42200000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42233322
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42266666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42300000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  42333333
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : imu_capture_ready(). IMU startup dropped last 408 samples, the timestamp is too large
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     17733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     51066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     84400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    117733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    151066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    184400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    217733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    251066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    284400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    317733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    351066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    384400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    417733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    451066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    484400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    517733 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    551066 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    584400 type:Depth
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : CFrameContext(). No metadata attached to the sample
[ warning  ] : queue_disable(). Waiting for blocking call to complete
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : capturesync_add_capture(). Capture Error Detected, Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     17733 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     51066 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     84400 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    117733 type:Depth

Try this:

Open device manager - Windows Button + r -> devmgmt.msc
Unplug all Kinects
Set View-> Devices by Type
Set View -> Show Hidden Devices
Under "Cameras" right click on all instances of "Azure Kinect 4k Camera" and select "Uninstall Device"
Under "USB Serial Bus devices" right click and select "Uninstall Device" for all "Azure Kinect 4k Camera" and "Azure Kinect Depth Camera" instances present.
Plug the Kinect in and try again.

试试这个：

打开设备管理器 -  Windows按钮+ r  - > devmgmt.msc
拔掉所有Kinects
按类型设置视图 - >设备
设置视图 - >显示隐藏的设备
在“Cameras”下右键单击“Azure Kinect 4k Camera”的所有实例，然后选择“卸载设备”
在“USB串行总线设备”下右键单击并为所有“Azure Kinect 4k Camera”和“Azure Kinect Depth Camera”实例选择“卸载设备”。
将Kinect插入并再试一次。

I tried. It didn't work.

Try this:

Open device manager - Windows Button + r -> devmgmt.msc
Unplug all Kinects
Set View-> Devices by Type
Set View -> Show Hidden Devices
Under "Cameras" right click on all instances of "Azure Kinect 4k Camera" and select "Uninstall Device"
Under "USB Serial Bus devices" right click and select "Uninstall Device" for all "Azure Kinect 4k Camera" and "Azure Kinect Depth Camera" instances present.
Plug the Kinect in and try again.

I tried. It didn't work.

@lllbrucccce I didn't notice this before, but [ warning ] : CFrameContext(). No metadata attached to the sample is unique to your log and makes your issue different. Please lets start a new issue for this. Does the camera work fine with the camera app? I am wondering if you have some other camera software installed that may be filtering the camera images.

I am closing this issue as it seems like the original issue has been resolved. We can reopen if new information is available.

This issue has not been resolved. Please keep open.
On Mon, Jul 22, 2019 at 11:18 AM wes-b<EMAIL_ADDRESS>wrote:

Closed #459
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/459.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/459?email_source=notifications&email_token=AAGXPN4CAM5B4BPIAAE7YHLQAX2XPA5CNFSM4H5NYM2KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSUGT5VI#event-2500673237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGXPN7WIUP3BXARZEM32FTQAX2XPANCNFSM4H5NYM2A
.

--
Ali Daniali
Follow me on Twitter: http://twitter.com/thedevguy
LinkedIn: http://www.linkedin.com/in/alidaniali

Sure, what is your current status after trying:
Try this:
Open device manager - Windows Button + r -> devmgmt.msc
Unplug all Kinects
Set View-> Devices by Type
Set View -> Show Hidden Devices
Under "Cameras" right click on all instances of "Azure Kinect 4k Camera" and select "Uninstall Device"
Under "USB Serial Bus devices" right click and select "Uninstall Device" for all "Azure Kinect 4k Camera" and "Azure Kinect Depth Camera" instances present.
Plug the Kinect in and try again.

Closing the issue due to no new information.

Please reopen. I havent had access to the PC with the issue until now.

I tried the following and there isn't an option for "cameras". I've attached what I see in Device Manager.

I realized I was looking at the wrong view, Resources by Type, rather than Devices by Type. I followed the steps provided and did not have any different results.

When starting the viewer I dont see the device and see the following error:
[ error    ] : find_libusb_device(). Unable to open LIBUSB at index 0
[ error    ] : usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[ error    ] : depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()

@tesych would you please reopen this issue. Thank you.

Using the Non-Renesas USB Controller the device is detected in the viewer however it crashes and I get these errors:
[ warning  ] : depth_engine_thread(). Depth image processing is too slow at 56ms (this may be transient).
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82400000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82433333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82466666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82500000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82533333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82566666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82600000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82633333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82666666
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82700000
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82733333
[ warning  ] : capturesync_add_capture(). Dropping depth capture as TS is too large TS:  82766666
[ warning  ] : imu_capture_ready(). IMU startup dropped last 448 samples, the timestamp is too large
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     16088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     49422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:     82755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    116088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    149422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    182755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    216088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    249422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    282755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    316088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    349422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    382755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    416088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    449422 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    482755 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    516088 type:Depth
[ error    ] : replace_sample(). capturesync_drop, releasing capture early due to full queue TS:    549422 type:Depth
[ warning  ] : queue_disable(). Waiting for blocking call to complete
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : queue_error(). Error detected, shutting down queue and notifying consumers
[ warning  ] : capturesync_add_capture(). Capture Error Detected, Depth

@thedevguy I was using Startech USB 3.0 card (PEXUSB3S44V) with Renesas drivers and had the same issue and here's what fixed it for me:
Unplug all kinects. Go into device manager, look for the Renesas USB root hubs, uninstall the devices and delete the drivers when prompted. Install the Renesas drivers as administrator. Re-plugin the kinect and verify that the 4k camera as well as the depth have no yellow flags.
The kinect streams were then viewable in the tool. I tried the above steps without deleting the drivers and it didn't work. My guess is that the automatically installed renesas hub drivers were sticking around and not being replaced by the drivers startech provided. The hub name also changed to eXtensible afterwards.
This is a screenshot of my Renesas hubs, note that the hub says eXtensible now:

and the kinect in device manager when viewed by container:

Sorry if you've already tried this

@ultrafro-ptc thanks for the image. The (Microsoft) at the end of Renesas USB 3.0 eXtensible Host Controller -1.0 (Microsoft) also tells you that you are running the Microsoft driver rather than the Renesas driver.

I’ll check it out thank you.
-Ali
On Mon, Aug 5, 2019 at 12:15 PM wes-b<EMAIL_ADDRESS>wrote:

@ultrafro-ptc https://github.com/ultrafro-ptc thanks for the image. The
(Microsoft) at the end of Renesas USB 3.0 eXtensible Host Controller -1.0
(Microsoft) also tells you that you are running the Microsoft driver
rather than the Renesas driver.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/459?email_source=notifications&email_token=AAGXPN5MX3VVETJA6SYF6ALQDB335A5CNFSM4H5NYM2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SZMNY#issuecomment-518362679,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGXPN7527QXGOXIA5AMUYDQDB335ANCNFSM4H5NYM2A
.

--
Ali Daniali
Follow me on Twitter: http://twitter.com/thedevguy
LinkedIn: http://www.linkedin.com/in/alidaniali

I had a similar experience at the beginning. But that I came to know that my laptop's installed webcam was being called upon somehow when I try to run the cameras. I then uninstalled the laptop's camera. Then upon lowering the protection standards in my Kaspersky AntiVirus, I was able to run the cameras smoothly. Weird but worked for me.

@thedevguy I was using Startech USB 3.0 card (PEXUSB3S44V) with Renesas drivers and had the same issue and here's what fixed it for me:
Unplug all kinects. Go into device manager, look for the Renesas USB root hubs, uninstall the devices and delete the drivers when prompted. Install the Renesas drivers as administrator. Re-plugin the kinect and verify that the 4k camera as well as the depth have no yellow flags.
The kinect streams were then viewable in the tool. I tried the above steps without deleting the drivers and it didn't work. My guess is that the automatically installed renesas hub drivers were sticking around and not being replaced by the drivers startech provided. The hub name also changed to eXtensible afterwards.
This is a screenshot of my Renesas hubs, note that the hub says eXtensible now:

and the kinect in device manager when viewed by container:

Sorry if you've already tried this

I have tried this solution. the StarTech driver performed even worse than microsoft drivers. I had to uninstall them to at least to be able to see the camera in Azure viewer. Btw, i'm using a StarTech PCI card with 4 slots.

I`m using
https://www.siig.com/4-port-superspeed-usb-3-0-pcie-card-quad-core-lp.html
Chipset: Renesas uPD720202
Cant see kinect devices when they connect.

@barakooda are you talking about Windows or Linux?
USB Card JU-P40811-S1  works fine. Awesome! Thank you.

works fine :
https://www.asrock.com/MB/Intel/X299 OC Formula/index.asp

What do you mean by this? mainboard and USB  card works great? USB3 ports on the main board work great?

kinect devices not turn on \ recognized when they connected.
Z370-A PRO

What do you mean by this? USB ports don't work for you? Do you know what USB Host controllers are used here?

Sorry for not being clear, I updated my text.
thanks.

there is hardware section we can share our test results ?
should we open one ?

@barakooda, thanks for the idea, https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/936 has been opened.


Does not work correctly with Collection Groups

When there are no selected objects and when you bring mouse cursor to the BBox of the group, there is an error.

When you snap a normal object to a group, touching a BBox - an error appears

https://drive.google.com/drive/folders/1gfH1mQHKMXTBXnVIvstdJsIrTGtBT0tn?usp=sharing

Could you tell me how you created it? I have not actually used those before. I have used instances, but then the original group is in the scene collection, but you do not have that here.

To be honest, I just now learned the difference between 'Instance to scene' and 'Group from collection'.  Group from collection' - as I see it, was removed/hidden in version 3.2, in 3.0 and 3.1 it is.
Group from collection' - hides the collection and creates a group from it.
'Instance to scene' - creates a group from the collection, but does nothing with the original collection.
There was confusion, instances were not exactly instances when using modifiers and further ungrouping, maybe because of this they changed something

Here's another group puzzle :) https://drive.google.com/file/d/1xHZ_a-KfwQdrkHUexvlQX96n30FJ1Zxc/view?usp=share_link

Better to forget about "Group from collection", it seems to have been their unsuccessful attempt to create groups, this operator developers completely cut out.
But the problem remained, and what is interesting, if the collection-source is hidden, then pops up an error, if it is not hidden, then there is no error, but it snaps only on the pivot

I remember like removing the object from the view and instantiating it with an empty object. ray can find the instantiated object, but it is not in the view, it reports an error


Get rid of timestamp web resources versioning

Relates to cuba-platform/cuba#425

Reopened.
Remove 'webResourcesTs' usages in CubaPlugin, CubaDeployment, CubaUberJarBuilding and CubaWarBuilding


fix: submodule caused test errors

This PR removes git submodules.
And then, ament tests check caret_analyze_cpp_impl sources only.

build-and-test-differential can be passed after #18


Modules and Showcase pages are down

Environment
The nuxt.com website
Reproduction
https://nuxt.com/modules
https://nuxt.com/showcase
Describe the bug
When trying to navigate:

When refreshing the page:

Additional context
No response
Logs
No response

Same issue here, but looks that whole website is down, only page that is rendered correctly is index for me

Back to normal for me

Same, closing here 🤷🏽


[RELEASE] Release 1.8.0

What's the task? Please describe.
Action items for releasing v1.8.0
Roles

Release captain: @derekbit
QA captain: @roger-ryao

Describe the sub-tasks.
Pre-Release
The Release Captain needs to finish the following items.

[x] Before creating RC1, create a new release branch for the following component repositories, and then create RC1 from the new branch. Leave the master branch for the next feature release development (This task is only needed when doing a feature release such as x.y.0).

longhorn-manager
longhorn-ui
longhorn-tests
longhorn-engine
longhorn-instance-manager
longhorn-share-manager
backing-image-manager
longhorn-spdk-engine (needed after GA)
cli

[ ] Update image versions in https://github.com/longhorn/longhorn/tree/v1.8.0/chart/README.md.
[ ] Trigger the GA release build by longhorn/release Actions

The QA captain needs to coordinate the following items before the GA release.

[x] Update Best Practices>Operating System in Longhorn official document.
[x] Regression test plan (manual)
[ ] Run e2e regression for pre-GA milestones (install, upgrade)
[ ] Run security testing of container images for pre-GA milestones

[] Create security issues at upstream for unresolved CVEs in CSI sidecar images

[ ] Verify longhorn chart PR to ensure all artifacts are ready for GA (install, upgrade)
[ ] Run core testing (install, upgrade) for the GA build

Upgrade from the previous patch of the same feature release.
Upgrade from the last patch of the previous feature release.

Release
The Release Captain needs to finish the following items.

[ ] Release note - Release Captain

[ ] Deprecation note
[ ] Upgrade notes including highlighted notes, deprecation, compatible changes, and others impacting the current users

[ ] Publish the new version of doc and add a next patch version of dev doc.

[ ] Update image versions in https://longhorn.io References > Helm Values
[ ] Update image versions in https://longhorn.io Snapshot and Backups > CSI Snapshot Support > Enable CSI Snapshot Support on a Cluster

[ ] Release longhorn/chart from the release branch to publish to ArtifactHub by longhorn/charts Actions
[ ] Mark the release as latest release in longhorn/longhorn README.md

Post-Release

[ ] Mark the release as stable release and update stable versions in https://github.com/longhorn/longhorn/blob/master/support-versions.txt

For the first stable release, we need to consider several factors and reach a consensus by maintainers before claiming it stable.
For any patch release after a stable release, we need to wait 1-2 weeks for user feedback.

After marking the release as a stable release, Release Captain needs to coordinate the following items

[ ] Update https://github.com/longhorn/longhorn/blob/master/deploy/upgrade_responder_server/chart-values.yaml  - @PhanLe1010
[ ] Add another request for the rancher charts for the next patch release - @rebeccazzzz
[ ] Update the support matrix - @asettle

Rancher Charts
The Release Captain needs to coordinate the following items.

[ ] Verify the chart can be installed & upgraded - QA captain
[ ] rancher/image-mirrors update - @mantissahz @PhanLe1010
[ ] rancher/charts active branches for Rancher App Marketplace - @mantissahz @PhanLe1010

cc @longhorn/qa @longhorn/dev

Run e2e regression for pre-GA milestones (install, upgrade):
v1.8.0-rc1 amd64: 12 failures
v1.8.0-rc1 arm64: 11 failures
v1.8.0-rc1 amd64 upgrade: 167 failures
v1.8.0-rc1 arm64 upgrade: 171 failures

Run e2e regression for pre-GA milestones (install, upgrade):
v1.8.0-rc1 amd64: 12 failures v1.8.0-rc1 arm64: 11 failures v1.8.0-rc1 amd64 upgrade: 167 failures v1.8.0-rc1 arm64 upgrade: 171 failures

Are the all issues fixed in the v1.8.x-head?

Run e2e regression for pre-GA milestones (install, upgrade):
v1.8.0-rc1 amd64: 12 failures v1.8.0-rc1 arm64: 11 failures v1.8.0-rc1 amd64 upgrade: 167 failures v1.8.0-rc1 arm64 upgrade: 171 failures

Are the all issues fixed in the v1.8.x-head?

Most of the failed cases have already been fixed in the v1.8.x-head. I still need some time to summarize the current status.

Run security testing of container images for pre-GA milestones:
v1.8.0-rc1: 0 CRITICAL, 17 HIGH


TypeError: argument of type 'NoneType' is not iterable fp16

An error appears when I want to train the model:
2021-07-14 10:48:04,872 - mmdet - INFO - workflow: [('train', 1)], max: 10 epochs
Traceback (most recent call last):
  File "train.py", line 30, in <module>
    train(mmdet_model_conf)
  File "/home/src/model_operations/train.py", line 33, in train
    distributed=distributed, validate=True)
  File "/home/mmdetection/mmdet/apis/train.py", line 170, in train_detector
    runner.run(data_loaders, cfg.workflow)
  File "/home/.conda/envs/1/lib/python3.7/site-packages/mmcv/runner/epoch_based_runner.py", line 108, in run
    self.call_hook('before_run')
  File "/home/.conda/envs/1/lib/python3.7/site-packages/mmcv/runner/base_runner.py", line 307, in call_hook
    getattr(hook, fn_name)(self)
  File "/home/.conda/envs/1/lib/python3.7/site-packages/mmcv/runner/hooks/optimizer.py", line 105, in before_run
    if 'fp16' in runner.meta and 'loss_scaler' in runner.meta['fp16']:
TypeError: argument of type 'NoneType' is not iterable

Here is the env:
sys.platform: linux
Python: 3.7.10 (default, Jun  4 2021, 14:48:32) [GCC 7.5.0]
CUDA available: True
GPU 0: Tesla T4
CUDA_HOME: /usr/local/cuda
NVCC: Build cuda_11.1.TC455_06.29069683_0
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.9.0+cu102
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v2.1.2 (Git Hash 98be7e8afa711dc9b66c8ff3504129cb82013cdb)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 10.2
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70
  - CuDNN 7.6.5
  - Magma 2.5.2
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=10.2, CUDNN_VERSION=7.6.5, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.9.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.10.0
OpenCV: 4.5.1
MMCV: 1.3.9
MMCV Compiler: GCC 7.5
MMCV CUDA Compiler: 11.1
MMDetection: 2.14.0+5f61347

It happens with and without:
fp16 = dict(loss_scale=512.0)

Any reason for this behavior ?

What command did you run? Do you modify the model or configs?

 I want to start training with fp16 precision.

facing same problem. tried to bypass it by adding cfg.runner.meta = dict(fp16 = dict(loss_scaler=[512.]))  but that caused something else to break

I will solve this problem ASAP.

MMDetection does not support pytorch1.9 currently, can you try to use PyTorch <= 1.8 and check whether this error occurs?

Its running in a docker created by your dockerfile
On Sat, Jul 17, 2021, 01:51 Guangchen Lin @.***> wrote:

MMDetection does not support pytorch1.9 currently, can you try to use
PyTorch <= 1.8 and check whether this error occurs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-881465662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWCYPDSLTXANWB6URZMDTYA2MRANCNFSM5ALAPKTA
.

I'm sorry and I check whether MMDetection supports Pytorch 1.9 and the result is yes.
I start training with our configs in configs/fp16 and this problem does not occur.
It seems that the runner.meta is None in your training process.
Can you start training with the configs provided in configs/fp16? And what command you run to start training process？

The problem occur when you add val to the workflow. Can you please try that?
Single gpu in my case
On Sat, Jul 17, 2021, 18:01 Guangchen Lin @.***> wrote:

I'm sorry and I check whether MMDetection supports Pytorch 1.9 and the
result is yes.
I start training with our configs in configs/fp16 and this problem does
not occur.
It seems that the runner.meta is None in your training process.
Can you start training with the configs provided in configs/fp16? And what
command you run to start training process？
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-881837189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWCYTOVFDSMS7MX7KIXLTYEMC7ANCNFSM5ALAPKTA
.

sorry, my bad, it has nothing to do with the val, just fp16
here is a colab notebook that demonstrate the problem with the fp16 config
(this is the mmdetection demo notebook, very slightly modified to use the
fp16 config)
https://colab.research.google.com/drive/1k2FjX-b9VADEbx5SrYyWXiJzl7MCWdhs?usp=sharing
On Sat, 17 Jul 2021 at 21:17, Moshe Livne @.***> wrote:

The problem occur when you add val to the workflow. Can you please try
that?
Single gpu in my case
On Sat, Jul 17, 2021, 18:01 Guangchen Lin @.***>
wrote:

I'm sorry and I check whether MMDetection supports Pytorch 1.9 and the
result is yes.
I start training with our configs in configs/fp16 and this problem does
not occur.
It seems that the runner.meta is None in your training process.
Can you start training with the configs provided in configs/fp16? And
what command you run to start training process？
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-881837189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWCYTOVFDSMS7MX7KIXLTYEMC7ANCNFSM5ALAPKTA
.

I also face same problem.How to solve finally?Could you tell me？

Still open...
On Thu, Aug 12, 2021, 15:57 kingoo123 @.***> wrote:

I also face same problem.How to solve finally?Could you tell me？
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-897329189,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWC6XLIJWZZORWE23RXLT4NBCJANCNFSM5ALAPKTA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Still open...
…
On Thu, Aug 12, 2021, 15:57 kingoo123 @.***> wrote: I also face same problem.How to solve finally?Could you tell me？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5611 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7IWC6XLIJWZZORWE23RXLT4NBCJANCNFSM5ALAPKTA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

Maybe due  to the version of pytorch or cuda. I try it in another environment, the problem is not appear.

Look at the colab. It is exactly the environment that you recommend. And
it's happening in my environment, in your docker
On Thu, Aug 12, 2021, 20:05 kingoo123 @.***> wrote:

Still open...
… <#m_4353179415442278638_>
On Thu, Aug 12, 2021, 15:57 kingoo123 @.***> wrote: I also face same
problem.How to solve finally?Could you tell me？ — You are receiving this
because you commented. Reply to this email directly, view it on GitHub <#5611
(comment)
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-897329189>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWC6XLIJWZZORWE23RXLT4NBCJANCNFSM5ALAPKTA
. Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.
Maybe due to the version of pytorch or cuda. I try it in another
environment, the problem is not appear.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/5611#issuecomment-897433163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7IWC4KYMXNQE3ILIWPA33T4N6E7ANCNFSM5ALAPKTA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Sorry, I was too busy some time ago.
I checked the colab notebook, you have not set the meta in your train_detector function in the last code block.
You can refer to  https://github.com/open-mmlab/mmdetection/blob/master/tools/train.py#L184

Sorry, I was too busy some time ago. I checked the colab notebook, you have not set the meta in your train_detector function in the last code block. You can refer to https://github.com/open-mmlab/mmdetection/blob/master/tools/train.py#L184

Thank you closed the problem，jupyter tutorial  sample  code  not set the meta in  train_detector function in the last code block.


Build error

/System/Library/Frameworks/Sparkle.framework/Versions/B/Sparkle' (no such file, not in dyld cache)
'/Library/Frameworks/Sparkle.framework/Versions/B/Sparkle' (no such file),

ok, when I set my account info ,solved, thanks.


Support HF-based native contract update

Port https://github.com/neo-project/neo/pull/2942 and enable/refactor tests that were disabled in https://github.com/nspcc-dev/neo-go/pull/3212.

See https://github.com/neo-project/neo/issues/2834 also, it's fixed in the same PR.


Use k8sutils directly instead of passing unnecessary parameters

I rebased off of v1.3.0 and tested this. It works nicely! I can write up a short blog post summarizing the changes I made to the stock configuration to get the operator to watch two namespaces.


Cannot use https with webpack-dev-server

Laravel Mix Version: 6.0.9
Node Version (node -v): 14.15.0
NPM Version (npm -v): 6.14.9
OS: catalina

Description:
I'm trying to upgrade my Laravel Mix project. I am running webpack-dev-server over https, however, all hot updates are coming back as http and thus not working (I get a mixed content warning as the json is served over HTTP).
Steps To Reproduce:
This is my config:
mix
  .options({
    hmrOptions: {
      host,
      port: 8080,
    },
  })
  .webpackConfig({
    devServer: {
      host,
      port: 8080,
      https: {
        cert: // path to cert,
        key:  // path to key,
    },
});

When I run mix watch --hot it loads correctly initially. However, subsequent hot updates receive a mixed content warning that it is served over HTTP.
I see this line which suggests to me that --https needs to be in the command. However, when I pass that command I get either "unknown option --https" ... or if I do mix watch --hot -- --https it is not respecting my key and cert and host as specified in my webpack config.

Note: adding process.argv.push('--https') to the top of my mix config will address the issue.
I used to address this issue by adding --key and --cert flags to my hot task, but it does not appear to allow me to do it this way anymore.

Note: adding process.argv.push('--https') to the top of my mix config will address the issue.
I used to address this issue by adding --key and --cert flags to my hot task, but it does not appear to allow me to do it this way anymore.

I figured out that there are a few steps involved in fixing this problem. I'm writing my understanding of things and the steps I performed in order to fix it.
First of all: Laravel Mix, as you have noticed, looks at the presence of the --https command line option in order to toggle HTTPS support. The problem is that if we specify the --https flag then webpack-dev-server probably expects the certificate and key to passed via CLI (--key and --cert options). If those CLI options are not present then webpack-dev-server will generate its own self-signed certificates.
process.argv.push(
    '--https',
    '--key ' + process.env.APP_SSL_KEY,
    '--cert ' + process.env.APP_SSL_CERT
);

Secondly, we need to update the Webpack configuration so that it looks a bit like this:
{
    config: {
        publicPath: 'https://' + process.env.APP_DOMAIN + ':8080/',
    },
    devServer: {
        public: 'https://' + process.env.APP_DOMAIN + ':8080/',
        https: {
            key: fs.readFileSync(process.env.APP_SSL_KEY),
            cert: fs.readFileSync(process.env.APP_SSL_CERT)
        }
    }
}

We can easily merge our own Webpack configuration using mix.webpackConfig(config).
P.S. Laravel Mix 6 uses the ^4.0.0-beta.0 version of the webpack-dev-server which introduces some breaking changes:

I figured out that there are a few steps involved in fixing this problem. I'm writing my understanding of things and the steps I performed in order to fix it.
First of all: Laravel Mix, as you have noticed, looks at the presence of the --https command line option in order to toggle HTTPS support. The problem is that if we specify the --https flag then webpack-dev-server probably expects the certificate and key to passed via CLI (--key and --cert options). If those CLI options are not present then webpack-dev-server will generate its own self-signed certificates.
process.argv.push(
    '--https',
    '--key ' + process.env.APP_SSL_KEY,
    '--cert ' + process.env.APP_SSL_CERT
);

Secondly, we need to update the Webpack configuration so that it looks a bit like this:
{
    config: {
        publicPath: 'https://' + process.env.APP_DOMAIN + ':8080/',
    },
    devServer: {
        public: 'https://' + process.env.APP_DOMAIN + ':8080/',
        https: {
            key: fs.readFileSync(process.env.APP_SSL_KEY),
            cert: fs.readFileSync(process.env.APP_SSL_CERT)
        }
    }
}

We can easily merge our own Webpack configuration using mix.webpackConfig(config).
P.S. Laravel Mix 6 uses the ^4.0.0-beta.0 version of the webpack-dev-server which introduces some breaking changes:

@silvioiannone your suggestion does not work it completely ignores it as well you cannot pass config to webpack options if you still want to use laravel mix. publicPath is available with mix.options({ publicPath }), but its functionality is completely different. So will this be solved? I want to test webShare API locally... Guess with laravel mix hmr its not possible...

@juslintek This is how I solved it for my project and, regardless of what you say, it's working: https://github.com/silvioiannone/spa-skeleton/blob/next/webpack.mix.js. What you want to look at is the init() function.
You can also check the related webpack.config.js file (loaded by webpack.mix.js) here: https://github.com/silvioiannone/spa-skeleton/blob/next/webpack.config.js

@juslintek the solution with injectHot fixed the same problem on mix 6.0.13.  Thank you

I'm unable to use injectHot. I get this error:
Invalid configuration object. Object has been initialized using a configuration object that does not match the API schema.
 - configuration has an unknown property 'injectHot'. These properties are valid:
   object { bonjour?, client?, compress?, dev?, firewall?, headers?, historyApiFallback?, host?, hot?, http2?, https?, liveReload?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, public?, setupExitSignals?, static?, transportMode?, watchFiles? }

`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>
I also try to use needHotEntry, as seems deleted (https://github.com/webpack/webpack-dev-server/blob/master/CHANGELOG.md#-breaking-changes-1), but neither works.

@nelson6e65 my solution for that was to downgrade the<EMAIL_ADDRESS>... man this whole webpack v5 upgrade is a mess across all packages.

@juslintek Your solution got me closest to the setup that I had with Mix V5. Everything works with HTTPS but when I change a file, the request still comes through with HTTP which causes a cross-origin problem.
yarn cross-env NODE_ENV=hot node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js --https --key $CERTS_FOLDER/app/nginx-selfsigned.key --cert $CERTS_FOLDER/app/nginx-selfsigned.crt

On v5 I used cross-env to set up the HTTPS configs while running --hot and that worked like a charm, but with v6 not luck yet. Does anyone figured out a way to set up this properly?.

Working config for mix 6 and webpack 5 in Docker served over https:
mix.webpackConfig({
    mode: "development",
    devServer: {
        port: 8080,
        host: '<IP_ADDRESS>',
        hot: true,
        headers: {
            "Access-Control-Allow-Origin": "*"
        },
        https: {
            ca: path.resolve('/path/to/rootCA'),
            key: path.resolve('/path/to/server.key'),
            cert: path.resolve('path/to/server.crt')
        }
    },
    output: {
        publicPath: `https://${process.env.APP_HOST}:8080/`
    }
});

mix.options({
    hmrOptions: {
        host: process.env.APP_HOST,
        port: 8080
    },
    https: false
})

package.json
"scripts": {
        "watch": "mix watch",
        "hot": "mix watch --hot",
        "dev": "mix",
        "prod": "mix --production"
},

Specifics (how to avoid mix' bugs):

Do not use --https option in package.json or your certificates will be ignored
Force https: false in mix.options or certificates your will be ignored
Provide output.publicPath  with https:// to fix requesting hot updates over http

This config tested in Windows + WSL2 + Docker. Should normally work in Linux too.
docker-compose.yml part for hot reload service:
  react:
    user: ${UID}:${GID}
    build:
      context: ./.docker/nodejs
      args:
        - UID=${UID}
    container_name: ${PROJECT_NAME}_react
    working_dir: ${APP_PATH}/src
    volumes:
      - ./:${APP_PATH}:cached
    ports:
      - "8080:8080"
    networks:
      - your.network
    command: sh -c 'npm run hot'

This will launch npm run hot accessible through port 8080.
This config is required for Windows because running hot reloader any other way will not open a port and it won't work.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Why are first letters escaped?

Hello, a question just as someone looking forward to this feature. Two of the examples given are:
RegExp.escape("The Quick Brown Fox"); // "\\x54he\\x20Quick\\x20Brown\\x20Fox"
RegExp.escape("Buy it. use it. break it. fix it.") // "\\x42uy\\x20it\\.\\x20use\\x20it\\.\\x20break\\x20it\\.\\x20fix\\x20it\\."

Why are the first letters escaped? There doesn't seem to be anything special about them.

Thanks Kevin!


Lost/missed messages when playing continuously

I have noticed, when trying to play many notes at the same time, the whole system cannot manage to process them all.

The best way to reproduce is to use MIDI controller with a built-in arpeggiator. Set the tempo to 60+ BPM and division to 16th and literally just press one key.
You'd notice the synthesizer/instrument playing very very swingy, nowhere near the expected BPM and time division.
Other way is just to continuously press one key and observe the behaviour of the instrument. The note will be ignored at times, and play continuously at others.
Is there a way to make the MIDI transmission more robust? If high BPM cannot be supported, is there a way to at least make it not lose the messages?

I'm having the same kind of issues, hanging notes, retriggers etc. Anyone got a lead on some working code?


More Dutch Base Translations

Decapitalised various words.
Added/removed certain dashes.
Added new VS Race translations.
Added a spaced in speed classes.
Added new and improved vehicle names.
Fixed GBA Shy Guy Beach's name.
Fixed Mushroom Cup's name.
Cleaned Drift Explanation message.


Fix file names

Thanks for sharing this mix task :+1:!
The goal of this PR is to fix the mix task following the description in issue #11.

@mathieul awesome, thanks 👍


We cannot delete one query from estimate sessions

Thanks for reporting. We'll dig into this.

I could not reproduce this issue, can you describe your environment? Can you see any error in the console or network log in the browser (using F12, debug tools)?

Hi! if you still have the same issue please provide us with more information.
describe your environment. Can you see any error in the console or network log in to the browser (using F12, debug tools)?

Hi again if you still have the same issues let me know.


Validate $perms parameter

Small change to confirm that $perms has a proper value. I had some kind of issue with this at some point long before I merged the most recent code, so it might not be as relevant anymore (e.g. if $perms now has a default value). It seems like a reasonable thing to do, though.

Well, I made a mess oput of the merge process but I got everything caught
up and rational. I'll test and if it looks good upload to PAUSE Friday.
Louis
On Tue, 14 Jul 2015, Steven N. Severinghaus wrote:

Small change to confirm that $perms has a proper value. I had some kind of issue with this at some point long before I merged the most
recent code, so it might not be as relevant anymore (e.g. if $perms now has a default value). It seems like a reasonable thing to do,
though.

You can view, comment on, or merge this pull request online at:

https://github.com/iamcal/perl-Flickr-API/pull/15
Commit Summary

Warn and return if perms is not passed to request_auth_url

Merge branch 'master' of https://github.com/lbmoore/perl-Flickr-API

Merge branch 'master' of https://github.com/iamcal/perl-Flickr-API
File Changes

M lib/Flickr/API.pm (3)
Patch Links:

https://github.com/iamcal/perl-Flickr-API/pull/15.patch

https://github.com/iamcal/perl-Flickr-API/pull/15.diff

—
Reply to this email directly or view it on GitHub.[AFyzxWBvj33u81ScttIOhtQI6QpZZaMSks5odZhigaJpZM4FYq93.gif]


Ignore VIM swap files

Ignore *.swp pattern
DCO 1.1 Signed-off-by: Alexey Miroshkin<EMAIL_ADDRESS>

Cool. Cheers :beers:
/cc: @jianqiu and @mattcui and @karafelix let's monitor pipeline for any issues. Should not be but please comment here or new issue if there are.

Oh, yeah, that was one of the things I fixed in my bats branch. Wasn't sure how this suddenly became a problem; it didn't look like anything had changed, so I thought maybe it was something I messed up.
Thanks, Alexey.


0.2.0

0.2.0

Detect and handle gz files or plain files
--compression arg to select compression type
zlib-ng to speed up gzip handling
--children and --parents to save children and parents based on kraken report

0.2.0

Detect and handle gz files or plain files
--compression arg to select compression type
zlib-ng to speed up gzip handling
--children and --parents to save children and parents based on kraken report


Larger backbone

Hi, thanks for the nice project. Have you guys tried using a larger backbones like resnet50 or hrnet? If yes, do you know the rough performance gains?

We have tried resnet50 and found the same performance as the resnet34 model. But we haven't tested the improved model (i.e. the one that predicts camera parameters). Since it used more data and outputs more predictions, a larger backbone might be better.


Add toHaveBeenNthFetchedWith

✨ Feature proposal

Add toHaveBeenNthFetchedWith.
🎯 Motivation

We would like to assert that an endpoint has been called with a given payload at a certain point in time.
👀 Example

wrap(App)
	.withNetwork([
		path: '/users/1/update/',
		requestBody: {
			name: 'Alexander',
			surname: 'Nevsky'
		},
	])
	.mount()

await startSomeFlow()
await updateUser() // Let's suppose that in this page we update the user data
await doSomethingElse()
await updateUserAgain() // At the end we update the user again

expect('/users/1/update/').toHaveBeenNthFetchedWith(1, {
	name: 'Alexander',
	surname: 'Nevsky',
}) // We want to assert that the first time this endpoint was called, the payload was this one.

💬 Comments

We had a situation within acmofy-app that required this.

:notbad: it would be very useful sometimes… maybe the naming is what confuses me a bit more but I have no better alternative to propose so 🤐 (I thought something with "at" but it doesn't work)


train.py

I cant run Training, maybe someone can help me please
``(sdk) D:\Lesson8\models\research\object_detection>python legacy/train.py --logtostderr --train_dir=training/ --pipeline_config_path=training/faster_rcnn_inception_v2_pets.config
WARNING: The TensorFlow contrib module will not be included in TensorFlow 2.0.
For more information, please see:
https://github.com/tensorflow/community/blob/master/rfcs/20180907-contrib-sunset.md
https://github.com/tensorflow/addons
If you depend on functionality not listed there, please file an issue.
Traceback (most recent call last):
File "legacy/train.py", line 51, in
from object_detection.builders import model_builder
File "D:\Lesson8\models\research\object_detection\builders\model_builder.py", line 27, in
from object_detection.builders import post_processing_builder
File "D:\Lesson8\models\research\object_detection\builders\post_processing_builder.py", line 22, in
from object_detection.protos import post_processing_pb2
File "D:\Lesson8\models\research\object_detection\protos\post_processing_pb2.py", line 16, in
from object_detection.protos import calibration_pb2 as object__detection_dot_protos_dot_calibration__pb2
ImportError: cannot import name 'calibration_pb2'`

Check the step 2 from the Readme file. It is different from the video. You would have missed the protos part


Impossible to consume Cyclops locally

It's not possible to reference a local build of Cyclops in another project. You must push to master and use cyclops-dev. We should fix this so we can actually test pull requests against actual consumers of Cyclops.

👍

a289d660fb and cb6ceac63123d should fix this.


Getting exception when trying to login with any social sites.

Bug report
Title
Getting exception when trying to login with any social sites.
Issue Description
Getting exception when trying to login with any social sites.
Preconditions
1. framework Version.-master

Steps to reproduce
1. step1- Click on any social signin button

Expected result
It should redirect for login
Actual result
Getting exception

@jyoti-webkul
follow this solution https://github.com/bagisto/bagisto/issues/3369

Hi @jyoti-webkul
Kindly run composer install at the root of project than check.


WIP: [DataFmt] Add formatters for Accelerate/simd

Add Swift data formatters for vectors, matrices, and quaternions from
the Accelerate/simd framework.
rdar://40294100

@swift-ci test

@swift-ci test

This is WIP because in stale REPL sessions, LLDB may trigger a use-after-free bug when formatting a simd_double3 object. Here's an example:
$ /Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/bin/lldb -S /Users/vsk/src/github-swift-master/lldb/lit/lit-lldb-init --repl < /Users/vsk/src/github-swift-master/lldb/lit/SwiftREPL/SIMD.test | tee ~/Desktop/result.log
Welcome to Swift version 4.2-dev (LLVM c096c44a23, Clang c7422ffe24, Swift c23942012a). Type :help for assistance.
$R0: simd_int2 = (-1, 2)
$R1: simd_int3 = (-1, 2, 3)
$R2: simd_int4 = (-1, 2, 3, 4)
$R3: simd_uint2 = (1, 2)
$R4: simd_uint3 = (1, 2, 3)
$R5: simd_uint4 = (1, 2, 3, 4)
colf2: simd_float2 = (1.500000e+00, 2.000000e+00)
colf3: simd_float3 = (1.500000e+00, 2.000000e+00, 3.000000e+00)
colf4: simd_float4 = (1.500000e+00, 2.000000e+00, 3.000000e+00, 4.000000e+00)
cold2: simd_double2 = (1.500000e+00, 2.000000e+00)
cold3: simd_double3 = (3.000000e+00, 2.000000e+00, 3.000000e+00)
...

FAIL: lldb :: SwiftREPL/SIMD.test (389 of 389)
******************** TEST 'lldb :: SwiftREPL/SIMD.test' FAILED ********************
Script:
--
/Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/bin/lldb -S /Users/vsk/src/github-swift-master/lldb/lit/lit-lldb-init --repl < /Users/vsk/src/github-swift-master/lldb/lit/SwiftREPL/SIMD.test | /Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/llvm-macosx-x86_64/bin/FileCheck /Users/vsk/src/github-swift-master/lldb/lit/SwiftREPL/SIMD.test
--
Exit Code: 1

Command Output (stderr):
--
/Users/vsk/src/github-swift-master/lldb/lit/SwiftREPL/SIMD.test:39:11: error: expected string not found in input
// CHECK: cold3: simd_double3 = (1.500000e+00, 2.000000e+00, 3.000000e+00)
          ^
<stdin>:12:1: note: scanning from here
cold3: simd_double3 = (3.000000e+00, 2.000000e+00, 3.000000e+00)
^

--

********************
Testing Time: 23.01s
********************
Failing Tests (1):
    lldb :: SwiftREPL/SIMD.test

  Expected Passes    : 388
  Unexpected Failures: 1
FAILED: lit/CMakeFiles/check-lldb-lit
cd /Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/lit && /usr/bin/python2.7 /Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/llvm-macosx-x86_64/bin/llvm-lit --param lldb_site_config=/Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/lit/lit.site.cfg --param lldb_unit_site_config=/Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/lit/Unit/lit.site.cfg /Users/vsk/src/github-swift-master/build/Ninja-DebugAssert/lldb-macosx-x86_64/lit -sv
ninja: build stopped: subcommand failed.
./swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting

@swift-ci test

I debugged a stale REPL session and found that the DataExtractor provided by the ValueObject for a simd vector actually contained the incorrect values. What's more, is that calling print(vec) also printed the wrong value for the vector.
I think this shows that the issue isn't a bug in the data formatter, but rather some kind of use-after-free or data corruption within a component which manages the REPL session's memory. I filed rdar://40490685 to track this.
I've kicked off a testing run because I'm curious about whether the test will fail on the bots.

(meant to just comment, not approve, sorry).

@jimingham I've updated the coding style to be consistent with the rest of lldb, and added a comment about the data layout of simd vectors. PTAL.

@swift-ci test

Thanks everyone! I'll see if I can get one more clean test run here to prep the commit. I'm working up a fix for the memory corruption bug in IRMemoryMap, and plan on landing that before this PR goes in.

This is superseded by #672.


default message should be removed from schema

The schema lists message as required, but it has a default value, which makes no sense because default values are useful only if the field is optional. If message being required is not an error, then its default value should be removed from the schema.

Thanks @acli for creating this issue!
I agree with you generally, but we also use JSON Schema to suit the needs of downstream clients, e.g., an initializer website that is currently under construction. And while for strict uses of the schema file I agree that this wouldn't make sense, I think that it does make sense in this (and some other) context, where the value is required (which is correct, by the way), but we also provide a default value as pre-fill information, or as suggestion to the user.
What do you think?
Let me also bring @jspaaks into the conversation to get his opinion, but I'm leaning towards making this a wontfix, as I cannot predict this breaking anything (other than the strict logic).

Agree with @sdruskat on this one. Having a default doesn't break anything, and may help downstream tools, for example when populating a dropdown list with examples (from examples) and preselecting a default (from default).
For reference: http://json-schema.org/understanding-json-schema/reference/generic.html#annotations

Thanks @jspaaks.
@acli Closing this as wontfix. Please re-open if you disagree.


Is this library still maintained ?

Just a simple question: do you need any help to maintain this library ?
Do you think you will continue to maintain it or allow people to become repo admins ?
@shiren
@hanjung
@kyuwoo-choi
@junghwan-park
@heenakwag
@monibu1548
@seonim-ryu
@jung-han
Thanks a lot for your help !

cc @jinwoo-kim-nhn @2lja1018

up !

up!


Increment versions for signalr releases

Increment package versions for signalr releases

API change check
API changes are not detected in this pull request.


'NoneType' object has no attribute 'name'

I am trying add new sections to dynamic_preferences_registry.py but after changes django admin get this error:
'NoneType' object has no attribute 'name'
My registry
# blog/dynamic_preferences_registry.py

from dynamic_preferences.types import BooleanPreference, StringPreference, LongStringPreference
from dynamic_preferences.preferences import Section
from dynamic_preferences.registries import global_preferences_registry
from dynamic_preferences.users.registries import user_preferences_registry

# we create some section objects to link related preferences together

sec_admin = Section('ft5000admin')
sec_servis = Section('ft5000servis')
sec_view = Section('ekasa')

# # We start with a global preference
@global_preferences_registry.register
class BlHlavicka(LongStringPreference):
     section = sec_servis
     name = 'bl_hlavicka'
     default = 'FT 5000\nTestovacia hlavicka'
     required = False

@global_preferences_registry.register
class MaintenanceMode(BooleanPreference):
    #section = general
    name = 'maintenance_mode'
    default = False

How have you solved this error?

After editing the default sections and adding new sections to dynamic_preferences_registry.py, django admin shows the error: 'NoneType' object has no attribute 'name'
Here is the stack
Environment:

Request Method: GET
Request URL: http://<IP_ADDRESS>:8000/admin/

Django Version: 2.1.7
Python Version: 3.6.1
Installed Applications:
['grappelli',
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'rest_framework',
 'rest_framework.authtoken',
 'django_filters',
 'corsheaders',
 'fontawesome',
 'taggit',
 'taggit_autosuggest',
 'taggit_serializer',
 'colorfield',
 'myapp',
 'dynamic_preferences']
Installed Middleware:
['django.middleware.security.SecurityMiddleware',
 'corsheaders.middleware.CorsMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware']

Traceback:

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner
  34.             response = get_response(request)

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
  156.                 response = self.process_exception_by_middleware(e, request)

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
  154.                 response = response.render()

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/template/response.py" in render
  106.             self.content = self.rendered_content

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/template/response.py" in rendered_content
  83.         content = template.render(context, self._request)

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/template/backends/django.py" in render
  61.             return self.template.render(context)

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/template/base.py" in render
  169.                 with context.bind_template(self):

File "/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/contextlib.py" in __enter__
  82.             return next(self.gen)

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/django/template/context.py" in bind_template
  246.             updates.update(processor(self.request))

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/dynamic_preferences/processors.py" in global_preferences
  10.     return {'global_preferences': manager.all()}

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/dynamic_preferences/managers.py" in all
  187.             return self.load_from_db()

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/dynamic_preferences/managers.py" in load_from_db
  205.         db_prefs = {p.preference.identifier(): p for p in self.queryset}

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/dynamic_preferences/managers.py" in <dictcomp>
  205.         db_prefs = {p.preference.identifier(): p for p in self.queryset}

File "/Users/myuser/mypath/myproject-api-venv/lib/python3.6/site-packages/dynamic_preferences/preferences.py" in identifier
  93.         if not self.section.name:

Exception Type: AttributeError at /admin/
Exception Value: 'NoneType' object has no attribute 'name'

After playing around a bit I realised this was because I edited the existing "MaintenanceMode" preference in dynamic_preferences_registry.py, adding a "section" to it.
@global_preferences_registry.register
class MaintenanceMode(BooleanPreference):
    name = 'maintenance_mode'
    default = False

Upon reverting that and applying manage.py checkpreferences for good measure, the error went away.
This is definitely a confusing way to do things.

(venv) ft5000@localhost:~/devel/200$ python3 manage.py checkpreferences  /home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/registries.py:136: UserWarning: Creating a fallback preference with section "None" and name "dic".This means you have preferences in your database that don't match any registered preference. If you want to delete these entries, please refer to the documentation: https://django-dynamic-preferences.readthedocs.io/en/latest/lifecycle.html   warnings.warn(message.format(section_name, pref_name)) Traceback (most recent call last):   File "manage.py", line 15, in <module>     execute_from_command_line(sys.argv)   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line     utility.execute()   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute     self.fetch_command(subcommand).run_from_argv(self.argv)   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv     self.execute(*args, **cmd_options)   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute     output = self.handle(*args, **options)   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/management/commands/checkpreferences.py", line 37, in handle     manager.all()   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/managers.py", line 199, in all     a.update(self.load_from_db(cache=True))   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/managers.py", line 205, in load_from_db     db_prefs = {p.preference.identifier(): p for p in self.queryset}   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/managers.py", line 205, in <dictcomp>     db_prefs = {p.preference.identifier(): p for p in self.queryset}   File "/home/ft5000/devel/200/venv/lib/python3.6/site-packages/dynamic_preferences/preferences.py", line 93, in identifier     if not self.section.name: AttributeError: 'NoneType' object has no attribute 'name' (venv) ft5000@localhost:~/devel/200$

The problem still persist, but now I can't cleanup all settings.

I solved the problem by removing record without "section" manually into db. This is a fast way, but not a perfect one.

+1


Container Network Aliases

What did you implement:

Fixes serialization of network commands
Adds ContainerConnectionOptionsBuilder

@schrieveslaach sorry for the long delay. the travis errors look unrelated


Paper citation

Greetings everyone,
I'm currently working on a paper regarding electrocatalysis and am using this package to fit an equivalent circuit for my electrochemical systems. I would like to reference this package in my paper. Could someone direct me to the repository's preferred citation format, or let me know if there's an official way to reference this tool?
Thank you everyone in advance.

Hi Matheus,
This package is linked to the publication:
"Practical Equivalent Electrical Circuit Identification for Electrochemical Impedance Spectroscopy Analysis With Gene Expression Programming"
Which you can find on the following link:
https://ieeexplore.ieee.org/document/9539171
Kind regards,
Maxime


@OmarJay1 consider switching to the new file URL paths

Hi @OmarJay1! We have changed the location of the output files because we started exceeding the limits of GitHub pages. Please refer to the documentation for all the new info. If you are already using the files in the v2 folder, it should be as simple as changing the URL path to: https://storage.googleapis.com/covid19-open-data/v2/<table-name>.csv. We will continue to update the older files in the root path like data.csv and stringency.csv. However, I encourage you to look into the new files since they provide a lot more information (including county-level data for the U.S.)

Thanks.  I actually run the Python scripts on my own server to fetch data.  I've been meaning to look into the new data features, but have gotten behind with other stuff as usual.  Hopefully this week I can catch up.  Thanks.

Great!


Dropzone multipart

AWS S3 Multi-part Uploading using DropzoneJS

Closing this PR in favor of https://github.com/nimbis/s3commander/pull/25


Provide with migrations following #3656

Add postgres/cassandra migrations
Change default config.header_type value from ldap to LDAP
Remove temporary code in ldap-auth/access.lua

NOTE: Please read the CONTRIBUTING.md guidelines before submitting your patch,
and ensure you followed them all:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#contributing
Summary
Provide with migrations following #3656
Full changelog

Add postgres/cassandra migrations to update config.header_type value from ldap to LDAP
Change default config.header_type value from ldap to LDAP
Remove temporary code added in #3656 in ldap-auth/access.lua

Issues resolved
Cleanup following #3656

It seems like #3731 removes the need for this PR. If the ldap string is hardcoded, then it is logical that the if scheme == "ldap" test stays hardcoded as well.
There's an option though: we could just remove the capitalization check and keep:
  if not (authorization_value or proxy_authorization_value) then
    local scheme = conf.header_type
    ngx.header["WWW-Authenticate"] = scheme .. ' realm="kong"'
    return false, {status = 401}
  end

That would be a breaking change (the default WWW-Authenticate header would change from LDAP kong to ldap kong, but I don't think anyone would notice since, from my understanding, this code is only triggered when no authentication header is passed, which would only be the case in a human interactive call... and since neither LDAP nor ldap are official types, no browser/client should be using it.
What do you think... breaking change that should not be seen, or 3 "dirty" lines of code? Or maybe another option?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Francois Maillard (fmaillard) seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I am closing this as it feels like #3731 gave alternative way to fix it. If there is still work to be done here, could you please open a new one and rebase on latest code.