How to define custom log format name in `goaccess.conf' just like COMBINED, COMMON, W3C etc. ?

Hi！
For example:
First, I set myself log format name in `goaccess.conf',
log-format NGINX %h %^ %e [%d:%t %^] "%r" %s %b %T "%R" "%u" "%^" %^ %^ %^
log-format HAPROXY "%r" %s %b %T "%R" "%u" "%h"

Then, I could use it in cli like this:
goaccess --log-format=NGINX -f nginx-access.log
or
goaccess --log-format=HAPROXY -f haproxy-access.log
If GoAccess already have a similar way to do this, please tell me, thanks a lot!

There's no way right now to define your own format, however, I can see this being useful. I'll take a look at it. Please keep this open.

goaccess still not support yet?

@vincentqiu not yet. Thanks for the reminder though :+1:

@allinurl do we have any update on this? :upside_down_face:

@guptarohit not yet... still working on priority issues for the next release. I'll bump a bit this on the list.

@allinurl
New year, new bump 😅
Happy new year by the way 🥳


[backport fortress] camera info topic published with the right data

🦟 Bug fix
Summary
In Garden some PR were included to fix the camera topic info. This PR backport some of the relevant PRs
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Is this depending on another in gz-rendering? Some methods seem to be not defined in CI.

Yes, this one https://github.com/gazebosim/gz-rendering/pull/905

@iche033 can we make a ign-rendering6 release?

@iche033 can we make a ign-rendering6 release?

yep on it.
While preparing for release, I ran into some warnings and like clean it up: https://github.com/gazebosim/gz-rendering/pull/929

@osrf-jenkins run tests please!

@iche033 thank you for the release

the INTEGRATION_camera test is failing crashing on actions. I backported more changes from gz-sensors8 to see if it fixes the issue. 1de1e8a


chore(deps): update dependency yup to v1

This PR contains the following updates:

Package
Type
Update
Change
Pending

yup
devDependencies
major
^0.32.11 -> ^1.0.0
1.2.0

Release Notes

jquense/yup
v1.1.1
Compare Source
Bug Fixes

docs: Broken anchores (#1979) (4ed4576)
make null validation errors consistent across schema (#1982) (f999497)
object: excluded edges are merged when concating schema (c07b08f), closes #1969

v1.1.0
Compare Source
Bug Fixes

tuple describe() method (#1947) (297f168)

Features

only resolve "strip()" for schema when used as an object field (#1977) (2ba1104)
respect context for object's children (#1971) (edfe6ac)

1.0.2 (2023-02-27)
Bug Fixes

fix array describe not including conditions (4040592), closes #1920

1.0.1 (2023-02-25)
v1.0.2
Compare Source
Bug Fixes

fix array describe not including conditions (4040592), closes #1920

v1.0.1
Compare Source
v1.0.0
Compare Source
Migrating from 0.x to 1.0.0: #1906

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: frontend/package-lock.json
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Versions '1.x' and '2.x' of '@aws-amplify/ui' have been deprecated. Please visit https://ui.docs.amplify.aws/ for the current version of Amplify UI.
npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated<EMAIL_ADDRESS>The Amazon Sumerian service is no longer accepting new customers. Existing customer scenes will not be available after February 21, 2023. The AWS Amplify XR features depend on the Amazon Sumerian service to function and as a result, will no longer be available.
npm ERR! code 127
npm ERR! path /tmp/renovate/repos/github/bcgov/nr-forests-access-management/client-code-gen/gen
npm ERR! command failed
npm ERR! command sh -c -- npm run build
npm ERR! ><EMAIL_ADDRESS>build
npm ERR! > tsc && tsc -p tsconfig.esm.json
npm ERR! sh: 1: tsc: not found

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2023-05-27T11_18_00_729Z-debug-0.log

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

To update yup to ^1.0.0, GrantAccess.vue page needs to be fixed for build (syntax error, type errors and behaviour correctness).

yup 1.0.0 syntax changes for "when"-"is"-"then" usage.

previous "roleUI" validation schema field with object() schema wasn't correct anymore.

I think we did not even use yup object() correctly previously but was working.
no need for validation schema on whole role object, only role_id is needed.

fix schema field "forestClientNumber" for nullable() wasn't correct.

fix "onRoleSelected" event trigger bug (renamed from "statusSelected" method) when role is changed from "abstract" back to "concrete".

fix previous html template select  uses :value="JSON.stringify(role)" causing yup throw error at version 1.0.0.

previously substitute value with stringfy "role" seems to be a hack and was strange it should not have been working but it did.
It no longer works at version 1.0.0 with "object()" schema for "roleUI" field.
Change back to use normal "role_id" for selected  since we only need to know which role id is selected.


add ratelimit populate descriptors log

Signed-off-by: hejianpeng<EMAIL_ADDRESS>Commit Message: add ratelimit populate descriptors log to help debug
Additional Description:
Risk Level: low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @mattklein123


Themes: sorting on tables

As an editor, I want to be able to sort rows and columns items on themes

This is not a priority anymore.

Changed selection interface to "multi select", allows reordering selected values.


Notification system skipping mentions when multiple mentions present

From @solstag on May 12, 2014 18:28
Ni!
I can faithfully reproduce the following with latest git and also have users telling me this has been going on for a while:
Usar A mentions user C => User C gets an email notification.
Usar A mentions user D => User D gets an email notification.
Usar A mentions users C and D in the same message => User C gets an email notification but user D does not.
The order in which the mentions appear in the message does not seem to matter.
I have also seen this:
User A mentions users C, D and E in individual messages => They get emailed.
User A mentions users C, D and E in the same message => Users C and D get emailed but user E does not.
Something seems to be wrong with the logic of handling whom to notify and email, I'm looking at the code but haven't figured it out yet...
Copied from original issue: friendica/red#459

From @solstag on May 12, 2014 18:50
I forgot to mention something that might be important: all of the channels above, in my tests, are on the same hub.

From @solstag on May 12, 2014 19:29
More debugging info...
In the A=>(C,D) case, all recipients (A, C and D) show up in $recip_list in include/notifier.php, as they all show up in the log.
Then, I get the following lines in the log:
2014-05-12 19:03:11: item_store: created item 17503
2014-05-12 19:03:11: tag_deliver: mention found for C
2014-05-12 19:03:11: notification: entry
2014-05-12 19:03:11: calling localize
2014-05-12 19:03:11: notification: sending notification email
2014-05-12 19:03:11: notification: enotify::send returns 1
2014-05-12 19:03:11: tag_deliver: not a plus tag
2014-05-12 19:03:11: item_store: created item 17504
2014-05-12 19:03:11: tag_deliver: mention found for D
2014-05-12 19:03:11: notification: entry
2014-05-12 19:03:13: notifier: basic loop complete.
2014-05-12 19:03:13: notifer: complete.
Therefore user D gets called into enotify.php, but it does not deliver to it, while it does deliver to it if mentioned alone (not along user C).

From @solstag on May 12, 2014 20:37
I've logged a var_export of the $params for the function notification($params) in include/enotify.php.
Comparing the params for each run (C which got delivered, and D which did not), I have absolutely no idea how could the first get to the point of logging "calling localize" and the second did not, as seen in the log output from my previous message.
From my reading both should by all means have logged "calling localize".
I suspect this may be the consequence of more complex interaction with other stuff and beyond my current understanding : P
If you're interested in this issue but can't reproduce it, and wants to take a look at my full logfiles including the $params var_export, ask here and I'll send them in private.
Thanks... =)

From @friendica on May 13, 2014 4:45
I can't duplicate this on my test site. However, you should see "calling localize" if
$params['item'] exists and
$params['item']['verb'] exists
The only error return prior to this is checking both sender and recipient exist, and this would be logged if one was missing.
If all these conditions are met, there may be something killing the process. This happens occasionally to me on a shared host. It shouldn't happen on a VPS unless you've exhausted memory.

From @solstag on May 13, 2014 8:54
Both item and item:verb exist in all cases. And it's definitely not memory, I'm on a VPS at around 500mb of 1gb capacity and during sharing the post it doesn't seem to add more than a few mb or tens of mb. :\
I tracked the breakage down to line 39 of include/enotify.php:
push_lang($recip['account_language']); // should probably have a channel language
Logging immediately before it works when running for C and D, immediately after it doesn't work for D. I checked and $recip['account_language'] is the same whether running for C and D.
Then, moving into include/language.php in push_lang, the breakage seems to happen at line 95:
load_translation_table($language);
And then, descending further, it breaks in include/language.php line 122:
``` include("view/$lang/strings.php"); ````
Which means it's breaking upon including the strings from pt-br, something it does all the time without breakage, really weird.
So, I tried removing the only thing in view/pt-br/strings.php that didn't seem completely inocuous, and that was the declaration of function "string_plural_select_pt_br"...
...and now it works!!!!!!!!!
Given that the issue has a concrete code related reason, I don't think this was exclusive to my server.
The interwebs tells me that PHP throws an error upon trying to redefine a function, which seems to be what is happening (given the first target works but then the second fails).
So, how should we fix this? Somehow isolating the scope of each target so each defines its own function? Or changing strings.php so we test for the function's existence before trying to define it?
Let me know what you consider the best solution and if it's not straightforward I'll work on a patch =)
Cheers!

From @friendica on May 13, 2014 9:14
Good detective work. That makes sense. We generate the strings file from messages.po so I added a check for function existence to the script that generates the file and rebuilt all the languages (once I knew what was happening it took three minutes from start to finish, otherwise I would've let you patch it. )

From @solstag on May 14, 2014 4:20
Thanks mike, closing this one! =D


APOC TTL Does not load in Desktop

Neo Desktop Version: <IP_ADDRESS>
Database Version 5.11
APOC Version 5.11
on MacOS 12.4
I installed the APOC plugin using the Desktop UI. Default APOC functionality loads fine.
I created a file in the conf directory called apoc.conf with apoc.ttl.enabled=true
Nope, still no TTL
I put a copy of it it in every single directory in the DMBS folder (I kid you not).
Still not matter what, apoc.ttl is not available.
If I put apoc.ttl.enabled=true  in the neo4j.conf file the DBMS won't even start (as expected).

Ok, this is the repo for APOC core which is supported by Neo4j engineering and is included in e.g. Aura and available under 'Plugins' in Desktop. The reason that you got TTL by default in 4.4 is that APOC core and extended was packaged together then and Desktop provided the full package. This is no longer the case, as described e.g. here: https://towardsdatascience.com/what-happened-with-apoc-in-neo4j-v5-core-and-extended-edition-23994cdf0a2c.
If you have installed APOC Extended correctly and it still does not work, I would think it is a bug in APOC Extended which is a separate Labs repo, maintained by individual contributors and not officially supported by Neo4j. If you like  to raise this bug, you better open a Github issue here instead: https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues


#2467 - add sgroup attachment point serializer/deserializer (mol v2000)

connected #2467
NOTE
👉  If you wish to test these changes locally (with full understanding) - please use another branch (that contains changes from several connected PRs) #2768

Just for whom would like to check this PR, you can follow steps:

draw a functional group in Marvin, such as Bn, and remember its attachment point is the one with a dashed circle

copy its lines of The Connection Table [CTAB] (V2000)

paste them in Ketcher

turn on Show atom Ids option in Ketcher

open the browser console, and check if the sgroup in ketcher.editor.render.ctab.molecule.sgroups has property attachmentPoints and attachment atom Ids are correct.

I agree to approve this PR. In case merging it by accident, please notify me when it's ready to merge, and I'll approve it. @kaluginserg

done


[Communication] Call Automation Next-Pylint

fixes #31620
Fixing usage of legacy HttpResponse

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


Migrate pytest configuration to pyproject.toml

🚀 Feature Request
Pytest supports configuration via pyproject.toml. Migrate its configuration from setup.cfg to pyproject.toml.

https://docs.pytest.org/en/6.2.x/customize.html#pyproject-toml

🔈 Motivation
pyproject.toml is becoming the standard configuration location for Python package. Doing this takes one step closer to removing the need for the setup.cfg file and simplify the overall project.
🛰 Alternatives

📎 Additional context

When darglint supports pyproject.toml (https://github.com/terrencepreilly/darglint/issues/130) setup.cfg could be removed entirely from this template.

Thanks, @johnthagen that's gread. I didn't know pytest is already accept pyproject.toml. I will include this update in the next minor version

Done in v1.1.0 :)


Ignore mono_crash files

These can be generated by Unity on crash
Reasons for making this change:

Unity can generate mono_crash.* files in some crash conditions.
This happened to us recently and we ended up with these files in version control.

Links to documentation supporting these rule changes:
Honestly I can't find it documented in Unity docs. I asked in official Unity discord and was told it was created by Unity.
A mention of it here: https://forum.unity.com/threads/debugging-editor-crashes.1457002/
I assume they're created by Mono itself, which is embedded in Unity.

This is also covered by #4358


[vcpkg-cmake-get-vars] Build error

Copy issue body from C:/src/vcpkg/installed/vcpkg/issue_body.md
error: building vcpkg-cmake-get-vars:x64-windows failed with: BUILD_FAILED
Elapsed time to handle vcpkg-cmake-get-vars:x64-windows: 42.1 ms
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+vcpkg-cmake-get-vars
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[vcpkg-cmake-get-vars]+Build+error&body=Copy+issue+body+from+C%3A%2Fsrc%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

How to report a package build failure [explanation video]

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


About Multiview Demo

Dear Author,
Thank you for your great work.
I am trying to apply your work in multi-view dataset, but struggling in loading data.
I wonder if is it possible for you to provide a small example of loading multiview dataset demo code.

Hello! We don't plan on releasing a demo for this part. To run on your own dataset you can edit BatchedImageDataset class.
The class expects the data to be in a .pkl  file containing the path and the bounding box of each person, and are grouped for all available views of each subject:
import pickle
data = pickle.load(open(<dataset_name>.pkl, "rb"))
data = [
  {
   "imgname":  np.array(num_views),      # paths for num_views images for person 1
   "center"     : np.array(num_views, 2),   # center for the bounding box for person 1 in each of the views
   "scale"      : np.array(num_views),        # scale for the bounding box for person 1 in each of the views
  },
  ...  # same of person 2, 3, ...
]

You can load the data with BatchedImageDataset, perform inference with a regression network to get the initial regression estimates, and then run multi-view refinement with ScoreHMR similar to the eval/eval_multiview.py script.


Dependency from specific bucket?

Is is possible to specify a dependency in a way that provides a URL to a bucket containing that dependency?
(The reason I ask for this is that I am maintaining my own bucket and a third-party bucket for some of the things my stuff relies on, so I want to specify dependencies in a way so that someone who doesn't realize there are two buckets doesn't have a problem.)

I'm not sure. It looks like "depends": [ "http://example.com/manifest.json" ] might work, but I can't confirm and it wouldn't be well supported if it does work.

I guess I will implement optional [bucket/]package dependencies because it is useful in whole set of cases (for example, we have an ambiguity whether a package from a repository should depends on a package from that repository or current user set of enabled repositories, and latter one looks like hell).
@lukesampson @r15ch13 Can you confirm that will be okay?

Curious to see if there's any new thoughts about this? ping

I just ran into this issue with rabbitmqadmin which requires python27 but I did not have versions bucket, so the install just failed with Couldn't find manifest of python27.


Is it possible to obtain the fine-tuning details for the LLaMA_GPT4 Chinese model?

The same as the English veron.


iOS: Full screen with status bar shows toolbar popping into view on scroll

Turn on status bar while in full screen and ensure there's multiple long stories in a row. As you scroll horizontally between them (once you scroll down enough to enter full screen mode), you then see the toolbar for a split second as you scroll down the full screen story. Happy to capture a video.

As a note, once these four issues (#1329, #1330, #1331, and #1332) we'll ship out the next update. But on full screen, would it be possible to have the toolbar attached to scrolling instead of sliding out of view? Sort of like how the story traversal buttons are attached to scrolling at the bottom of a story.

Do you mean having the bar interactively scroll away with the content, like in Safari etc? We could do that if we adopted the native hiding features, instead of fighting it — which would let us strip out a bunch of custom behavior.

Yes, that would be ideal

Okay, I've just committed incomplete changes to change the fullscreen behavior to use the iOS conventions:

The story fullscreen function now uses the standard behavior, like in Safari and other apps, where the navigation bar scrolls away with the content, and a quick swipe down or up shows or hides it, respectively.
When auto-scrolling is not enabled, a tap in the story will toggle the bar.  When auto-scroll is enabled, it briefly shows the auto-scroll controls, as before.

Currently there is some incorrect behavior when hiding the navigation bar with the status bar shown; I'll fix that in the coming week. I just wanted to commit this now to check that you're okay with the new behavior, since we went through several iterations in the past. Other than those minor issues, I think it works much better than before.

I like how the navbar scrolls away, but there is still some jumping that is happening. Also the feed bar isn't shown as I swipe between stories. Also, let's add a background to the status bar, since I don't like the look of story text underneath the clock. Looking forward to this week's fixes!

Yes, the feed bar and status bar background are the remaining issues I haven't fixed yet. Positioning them properly during the transitions are tricky, so I hid them for that commit. I'll fix those this week in between watching WWDC videos.


ValueError: Image size of 582400x436800 pixels is too large. It must be less than 2^16 in each direction.

I got error when running the demo, could you pls give me some advice? thx!
QFactoryLoader::QFactoryLoader() checking directory path "/home/lwh/miniconda3/envs/nice-slam/bin/imageformats" ...
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqgif.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqicns.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqico.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqjpeg.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqsvg.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqtga.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqtiff.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqwbmp.so"
loaded library "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqwebp.so"
Tracking Frame 50:  10%|█▌             | 50/500 [00:46<07:00,  1.07it/s]
Process Process-1:
Traceback (most recent call last):
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
    self.run()
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/multiprocessing/process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "/home/lwh/nice-slam/src/NICE_SLAM.py", line 266, in tracking
    self.tracker.run()
  File "/home/lwh/nice-slam/src/Tracker.py", line 230, in run
    idx, cam_iter, gt_depth, gt_color, camera_tensor, self.c, self.decoders)
  File "/home/lwh/nice-slam/src/utils/Visualizer.py", line 68, in vis
    fig.tight_layout()
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/site-packages/matplotlib/figure.py", line 3159, in tight_layout
    renderer = get_renderer(self)
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/site-packages/matplotlib/tight_layout.py", line 183, in get_renderer
    return canvas.get_renderer()
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/site-packages/matplotlib/backends/backend_agg.py", line 417, in get_renderer
    self.renderer = RendererAgg(w, h, self.figure.dpi)
  File "/home/lwh/miniconda3/envs/nice-slam/lib/python3.7/site-packages/matplotlib/backends/backend_agg.py", line 91, in __init__
    self._renderer = _RendererAgg(int(width), int(height), dpi)
ValueError: Image size of 582400x436800 pixels is too large. It must be less than 2^16 in each direction.
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqgif.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqicns.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqico.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqjpeg.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqsvg.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqtga.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqtiff.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqwbmp.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/imageformats/libqwebp.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/iconengines/libqsvgicon.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/xcbglintegrations/libqxcb-glx-integration.so"
QLibraryPrivate::unload succeeded on "/home/lwh/miniconda3/envs/nice-slam/plugins/platforms/libqxcb.so"
QLibraryPrivate::unload succeeded on "Xcursor" (faked)

I think there should be some problem with the matplotlib and its default backends. Maybe your default is not the same as ours. Please double-check the environment and configurations.
Normally people are able to run the demo after they install the environment using conda YAML file, no other operation is required.


subnet maps is not returned properly

output should merge special_subnets and subnets

Thanks for your PR Milan, will review with the team!


Ensure ALB protocol is HTTPS

Possible check to target the following resource

[ ] aws_alb_listener

HTTPS won't be the only requirement here. The port number has to be checked as well.

Correct me if I'm wrong but this check shouldn't fire up when one of the LB actions is a redirect to HTTPS. 🤔

Looks like it's already implemented as part of #12 here https://github.com/tfsec/tfsec/pull/14

agree - this isn't required


HSIEO-5499: Fix build error (unnecessary usage of removed class IProgressListener)

Merging this without approval to unblock the work for IPM team

@Beiming-Zhang Will you handle using the verbose flag + optionally giving a file path to write to in another PR? If so, please create a Jira and note it here.


Error processing --bam

I am getting errors running proovread with SR files in BAM format, but runs with equivalent SR data in FASTQ format succeed.
Sample dataset, attached below, is created as follows:

Create minimal (5 read) LR FASTQ file from human PacBio reads ("LR.fq").
Create a small SR BAM file (100 reads) from an Illumina 125bp paired end 60X BAM, aligned to GRCh38 ("SR.bam").
Create corresponding FASTQ file ("SR.fq") with bedtools bamtofastq.

I run proovread on SR.fq (Test A) and SR.bam (Test B) using commands below.

Test A: perl proovread -l LR.fq -s SR.fq --pre test.A
Test B:perl proovread -l LR.fq --bam SR.bam --pre test.B

Test A succeeds, while Test B exists with an error while parsing bam2cns output:
test.A.stdout.txt
test.B.stdout.txt
Digging a bit deeper, the problem seems to stem from a call within bam2cns to samtools view.  Specifically, bam2cns issues the call,
samtools view test.B/read-bam/test.B.bam "m140726_060753_42161_c100663510310000001823133012201490_s1_p0/61/0_2239:"
To which samtools issues the warning:

[main_samview] region "m140726_060753_42161_c100663510310000001823133012201490_
s1_p0/61/0_2239:" specifies an unknown reference name. Continue anyway.

It appears that bam2cns is trying to find the LR reference "m140..." which does not exist in test.B.bam; here, test.B.bam contains SR reads aligned to GRCh38.
A minimal example which reproduces this error is here:
proovread.test.tar.gz
Thanks in advance for your help.  Note that I'm a proovread newbie, so user error is always a possibility.  :)

Sorry for my late reply. Yes, the direct processing of bam files is not really well supported in proovread. I usually only use it for debugging purposes. Unfortunately I probably won't find the time to change this behaviour in the near future


Which part represents the Convolutional layer？

Which part represent the Convolutional layer in that code？Dense, Input, Lambda, LSTM, TimeDistributed layers used in that code，and Which part represent the Convolutional layer？

@fuhailin - https://github.com/airalcorn2/Recurrent-Convolutional-Neural-Network-Text-Classifier/blob/master/recurrent_convolutional_keras.py#L42.


Update github action "upload-artifact" from v3 to v4

This is more complex. We probably need a small rework of the pipleines. Closing for now.


docs: Add WARNING for single backticks in API docs

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
This makes use of the newly ~fixed RST backticks checker, and applies it to API docs as they are being built (by protodoc)
This just throws a warning for now, we can make it an error once these are cleaned up
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

output can be seen here https://dev.azure.com/cncf/envoy/_build/results?buildId=108826&view=logs&j=91e633a5-4907-5da1-5862-92a79fe2387a&t=f29e24e7-a093-5724-80bd-d79975d268cb&l=365


svg_loader: ommiting xml entities in the svg file

SVG files created using 'sketch' may contain xml entities,
which are not understandable by the svg loader.
For now only '"' is ommitted.

Tests or Samples :

Screen Shots:
current:

expected:

That's a good point. But in this case, only " is resolved.
If all XML entities should be treated the same, I think it would be good if these symbols   (1 space), < (<), > (>), & (&), " (“), # (#), ' (‘) are handled together.
Also you could pre-process this code in tvgXmlParser.
Would you consider it to be handled by XmlParser?

@mgrudzinska ping?

@hermet  - I'll do this today

@JSUYA could you please take a look?
I did not finish, because it seems to me that this version is illegible and sensitive to errors. Perhaps I misunderstood what you meant?
I do not know where to expect the XML entities, so I tried to keep the solution as general as possible.
If you confirm that it should look like that I will add all other entities.


tensorflow 1.7?

If I can use the high version tensorflow to run this code? Thanks.

I am able to run training with Tensorflow r1.8, cuda 9.0, protobuf 3.4.0 (change this last one in requirements.txt)

I think it is compatible up to 1.8 as far as I have tested. We noticed a slight decrease in computation speed for TF > 1.3, but the results are almost identical.

@asharakeh, computation speed during training, inference, or both?

Both. Usually training ~ 2x inference.


Add changelog

I was wondering what has changed from major version 2 to 3, and couldn't find a changelog.md. Is there another place where I can see what's changed?
If not, it'd be nice to add a changelog (or something similar) to the project.

Changelog added and up to date with latest


[Candidate 1v1 Freezing Rain v2] Title text is not concise

Issue Description
Title says: "Freezing Rain v1 by Millard9, queenmuff & Spalding."
Expected behavior
Title says: "Freezing Rain, by Millard9, queenmuff & Spalding"
Screenshots

Can change this Easy will do so if required.

It is not required to change anything on the map. Map will not be eligible for Ranked Maps and GenTool Auto download with this however.

So if I change the Text to "Freezing Rain v2 by Millard9, queenmuff & Spalding" it will be

No. "Freezing Rain v2 by Millard9, queenmuff & Spalding" will not qualify. "Freezing Rain, by Millard9, queenmuff & Spalding" will.
If you look at other Ranked Maps we have 2 styles of credits:
a) Map created by X
b) MapName, by X
I will accept these 2 formats. This is required for consistent style between all maps.

Issue is not fixed in new version

I'm not sure what you mean by it not being concise. I thought Freezing Rain v2 by Millard9, queenmuff & Spalding. Was correct?
Sent from my Galaxy
-------- Original message --------
From: xezon @.>
Date: 27/03/2021 10:01 (GMT+00:00)
To: xezon/GeneralsRankedMaps @.>
Cc: Millard9 @.>, Assign @.>
Subject: Re: [xezon/GeneralsRankedMaps] [Candidate 1v1 Freezing Rain v2] Title text is not concise (#59)
Issue is not fixed in new version
[shot_20210327_104653_1]https://user-images.githubusercontent.com/4720891/112717251-b4666400-8eeb-11eb-8430-8eb848418de8.jpg
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/xezon/GeneralsRankedMaps/issues/59#issuecomment-808704996, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATM5LCKSTU767GNTFWKGQHLTFWUGTANCNFSM4ZRQD3JA.

Repository front page explains rules for credit text:
https://github.com/xezon/GeneralsRankedMaps

So just to confirm you want it to say "Made by Millard9, queenmuff & Spalding. Freezing Rain ZH v2" is this correct?
Sent from my Galaxy
-------- Original message --------
From: xezon @.>
Date: 27/03/2021 10:22 (GMT+00:00)
To: xezon/GeneralsRankedMaps @.>
Cc: Millard9 @.>, Assign @.>
Subject: Re: [xezon/GeneralsRankedMaps] [Candidate 1v1 Freezing Rain v2] Title text is not concise (#59)
Repository front page explains rules for credit text:
https://github.com/xezon/GeneralsRankedMaps
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/xezon/GeneralsRankedMaps/issues/59#issuecomment-808707418, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATM5LCMZ7HSQRQGXHRU6CKLTFWWXDANCNFSM4ZRQD3JA.

I already posted above twice how it should be named. I copy it again:
"Freezing Rain, by Millard9, queenmuff & Spalding"

Ok i will change it to that then. thanks
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: @.>
Sent: 27 March 2021 10:38
To: @.>
Cc: @.>; @.>
Subject: Re: [xezon/GeneralsRankedMaps] [Candidate 1v1 Freezing Rain v2] Title text is not concise (#59)
I already posted above twice how it should be named. I copy it again:
"Freezing Rain, by Millard9, queenmuff & Spalding"
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/xezon/GeneralsRankedMaps/issues/59#issuecomment-808709181, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATM5LCL2CFIW52C2ED5OZRDTFWYSNANCNFSM4ZRQD3JA.

Fixed with https://github.com/xezon/GeneralsRankedMaps/commit/615b40c2937fdedfec1d5ae9f72917f978a3c911


bump boilerplate to v5.0.1

To fix failing builds due to rhel8 build node change
https://ci.int.devshift.net/job/openshift-osd-metrics-exporter-gh-build-main/lastBuild/console
12:57:46 [1/2] STEP 1/4: FROM registry.redhat.io/openshift4/ose-operator-registry:v4.14 AS builder
12:57:46 Trying to pull registry.redhat.io/openshift4/ose-operator-registry:v4.14...
12:57:46 Error: creating build container: initializing source docker://registry.redhat.io/openshift4/ose-operator-registry:v4.14: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication

/retest

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

Project coverage is 45.00%. Comparing base (ccd34f7) to head (34d1c73).

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #150       +/-   ##
===========================================
- Coverage   56.66%   45.00%   -11.67%
===========================================
  Files          11       12        +1
  Lines         540      680      +140
===========================================
  Hits          306      306
- Misses        220      360      +140
  Partials       14       14

see 1 file with indirect coverage changes

/lgtm


Change link in status header

Mojang's help page has been updated and no longer shows the status indicators. I changed the link to go to mc-heads.net's status page, as that's a great site in my opinion. I can change it to @MojangSupport on twitter if you want, let me know here.

Thanks! This is something I wanted to look into and that status page was in fact one of the few possible options I considered.
However, this is only really useful when the status information and the status page come from the same source. At the moment, status information comes from Mojang. That status info hasn't updated in months though, which is why there's a 24/7 warning on crafatar.com although everything is working fine.
If @MisterFixx is willing to enable CORS on his status page API, we could fetch the information from there instead :)

If that's the case, as I see it, there are three options:

Ping the individual endpoints ourselves
Ask @MisterFixx to enable CORS on that endpoint, like you said
Just wait for Mojang to update their own APIs, which could take a while

My apologies for the disabled CORS, I thought i had already enabled it, it should be fixed now.

@jomo - Because I'm not that familiar with XHR, I'm closing this PR and I'm going to open a new issue so someone else can take this on.

Just pushed a commit from last week (that I forgot to push), which implements this change. Thanks to @MisterFixx for providing the API!


chore: make local net redeployable

Purpose
Enable using script for local-net deployment to redeploy the same network with adjusted configs...
./for_devs/local-net start --boot-nodes 3 --rpc-nodes 1 --tps 1 ./cmake-build-debug/bin/taraxad

prnet cleaned-up successfully


feat(native): support CardInputWidget

setupIntent require SetupIntentParams from CardInputWidget:
https://stripe.com/docs/payments/save-and-reuse
But Capacitor can't put Native Elements to WebView. So we should create half-modal, and present CardInputWidget.

solution is here: https://github.com/capacitor-community/stripe/pull/87


Panic on giving ZedTokens from CRDB to Postgres

When giving a ZedToken that was created by CRDB-backed SpiceDB to a Postgres-backed SpiceDB, a panic can be raised if the ZedToken contains a timestamp that is too large for Postgres to handle
This should instead return an error.
Thanks to Duncan in Discord for reporting (https://discord.com/channels/844600078504951838/1153638230051270698)

Thanks for opening this up so fast.


delete some old figures

@ariaaay i believe @rishizsinha wanted you to add axis? are these the plots you're deleting?

@cxmo I modified the code. these are not the same plot


QFUF delete-then-set stmt issue.

QFUF fails to solve domains with a delete-then-set stmt such as the one found in the rover domain.
Here is an effect from one of the actions:
(:action communicate_image_data
 :parameters (?r - rover ?l - lander ?o - objective ?m - mode ?x - waypoint ?y - waypoint)
 :precondition (and (at ?r ?x)(at_lander ?l ?y)(have_image ?r ?o ?m)(visible ?x ?y)(available ?r)(channel_free ?l)
            )
 :effect (and (not (available ?r))(not (channel_free ?l))(channel_free ?l)(communicated_image_data ?o ?m)(available ?r)
          )
)

The available and channel_free are cleared and set again. The problem is that those predicates are used as preconditions, which makes the formula unsatisfiable.
One simple solution is to detect and remove such a pattern from the effects. The grounded version removes them from both preconditions and effects. For us the solver will assign the proper precondition values.

It is now fixed in 750305e.
@JoanEspasa, can you review the fix? If it is okay with you, can we close the issue?

Added some comments in the commit. Let me know what you think :)

The idea is to follow the same steps that FD does: https://www.fast-downward.org/ForDevelopers/ProblemTransformations
That is, when finding an action that removes and adds a fluent, we remove the delete effect. We should also document this in the README. To avoid duplicating code, it might be the best course of action to create a UP compiler to remove this and execute it before it is passed to any encoder.

This issue has struck again. This time, when we add a quality metric like the oversubscription metric, such a pattern is not removed during grounding. For now, I have moved the delete-then-set function into encoders.utilities but a cleaner solution is to have a Compiler for such patterns.
current fix in daeb48f

Yep, a compiler in UP land will ensure you never have to worry about that in pyPMT :)

@MFaisalZaki do you have a list of the domains that suffer from this issue?

Unfortunately, I don't have a list. Yet, the one I'm sure of is the rover domain.


Dask running out of memory reading in csv files post 2021.04.0 update

I have been using dask since the beginning of the year to calculate stats, plot histograms and convert file types for some large datasets (~1000 csv files with identical column names totalling ~180GB).
Using version 2021.3.0, dask has worked exactly as expected.
For example the code below uses very little memory, around 1GB for the whole duration of the program.
df = dd.read_csv(my_list_of_csv_files, dtype=np.float32, blocksize='64MB')
mean = df.mean(axis=0).compute()

However, since updating to 2021.04.0 (which I need to do in order to use the multi-dimensional histogram functions) running the exact same code causes the memory usage to steadily increase until it hits 16GB, at which point my job is killed. I have tried all the versions after 2021.04.0 (using: conda install dask=XXXX) and none have worked. Reverting back to 2021.03.0 fixes the problem instantly.
I should point out that the memory issue is avoided altogether in all versions if I make the slight modification:
df = dd.read_csv(my_list_of_csv_files, dtype=np.float32, blocksize='64MB')
arr = df.to_dask_array()
mean = arr.mean(axis=0).compute()

Unfortunately, there are other steps in my program that similarly cause the memory to snowball until failure and I can not get away with converting all steps to arrays.
Was there some change to read_csv() or to compute() that happened post 2021.03.0? Why would such a simple script keep failing?
Any help is greatly appreciated.

Thanks for raising an issue @mattcleigh. It seems like you're running into https://github.com/dask/dask/issues/7583. A fix for this was included in the latest dask==2021.08.1 release (xref https://github.com/dask/dask/pull/8040). If you're not using dask==2021.08.1 yet, could you update and retry your workload?

@mattcleigh checking in here.  Are you still having this issue or has an update to Dask 2021.08.1 solve this problem for you.

Ah, thanks for following up here @ncclementi! Indeed I think https://github.com/dask/dask/pull/8040 resolves this issue. @mattcleigh let us know if that's not the case and we can re-open


Zowe Site Flow

From @Tbr00ksy on August 24, 2018 18:42
Need to review different site flows and improve user navigation. Jay/BJ/Jessica?

Proposed changes to the arrows in green.
Copied from original issue: zowe/zlc#6

From @Tbr00ksy on September 12, 2018 13:1
@hogstrom can you please assign @jayenzi and @nannanli as the "owners"/"assignees"?

Updates / Owner needed

I'm going to move this item to the Documentation Squad.


New user helper warning about router policies

It seems like every person that learns how to Ziti stumbles on the fact that ERPs and SERPs aren't set up automatically. The least we could do is notice this condition in the console and warn them about it.

This would require a check everytime an administrator logs in and it might be entirely intentional. i don't think this is needed. i'll close this and we can reopen it if the community surfaces the need


Question: RSSI and variable mapping

Does the RSSI-field have any functunallity? I think it is not yet implemented in mysensor but it would be nice if it could be implemented like the battery leavel.
Would it be possible to map specific mysensor-message types to a mycontroller-message-type RSSI?
Like Mapping mysensors VAR5 to mycontroller RSSI? I would love to implement some custom RSSI measurement .. even if it would be just a percentage to note how many messages got lost on the way.

@cimba007 RSSI was introduced for ESP8266. This is not yet implemented on MyController. I will try to address this soon. Thank you!

Make sure it is customizable. For example in my setup (RF24) I don't have a RSSI availalbe, only a combination of (IS RSSI > -64db) and the # of failed transmissions. So something like a float with at least 2-3 decimalpoints would be needed if I wanted to show a number like 0-100.000%
Thanks for your hard work

@cimba007 MyController will not do anything on RSSI. receives and displays what you sent.
you have to send RSSI message as follows from MySensors,
MyMessage msg(CHILD_ID,V_VAR5);
msg.set("rssi:95 dBm");
  send(msg);

IMPORTANT: message-type should be set, sub-type should be V_VAR5 and payload should starts with rssi: (lowercase)

Thanks, that sounds very promising. I will try it out and report back, thank you ;-)

rssi feature is working very good for now. I did some slightly abuse of the "db"-value

Using my custom wrapper class for sending messages I try to keep track of some stuff:
static void rssi(char * buff, int buff_size)
{
  // "rssi:95 dBm"
  int s = snprintf(buff,buff_size,"rssi: %u|%u|%u|%u",_successful,_sendtotal,_retry,_failure);
  if(s >= buff_size)
  {
    snprintf(buff,buff_size,"rssi: %d%%",100*_successful/_sendtotal);
  }
  //Serial.println(buff);
}

in combination with your code snippet:
    static char buf[25];
    rssi(buf,25);

    MyMessage msg(1,V_VAR5);
    msg.set(buf);
    send(msg);

With this I can keep track of #lost messages thus providing an "indirect" qualit of my link.
Remark: I do not use the NRF24 hardware autoretry as it is buggy on my modules.

I even added an RPD-counter for the software ack from mycontroller .. keeping track of the number of received acks with good signal quality (RPD==1)

I guess MyController will not send any ack response. Let me check the code and update you.

I use this code and mycontroller or the gateways (don't know) is sending mysensor software ack and this is working very reliable!!
        send(_message,true);
        while(!ok && c)
        {
          // Ack?!
          if(wait(ms,_message.getCommand(),_message.type))
          {
            r.rpd = RF24_readByteRegister(RPD);
            _rpd += r.rpd;
            r.elapsedtime = micros()-starttime;
            r.success = true;
            r.retrycount = retrycountlimit-c;

            _successful++;
            return r;
          }

Is working very good at the moment. Thanks ;-)


strip-ansi utility has outdated code

details?

ansi-regex has new support
https://github.com/chalk/ansi-regex/blob/2b56fb0c7a07108e5b54241e8faec160d393aedb/index.js#L3-L10

i was wondering if we had a concrete example that this fixes?

yes, my zsh will only work with the latest ansi-regex pattern. Otherwise, I will get the following characters unstripped when using the stripAnsi utility: "\u001b]7;file://mengtinmcomsMBP.home/Users/mengting.yan1ibm.com/Workspace/kui3/plugin-kubeui\u0007"

i was wondering if we had a concrete example that this fixes?

yes, my zsh will only work with the latest ansi-regex pattern. Otherwise, I will get the following characters unstripped when using the stripAnsi utility: "\u001b]7;file://mengtinmcomsMBP.home/Users/mengting.yan1ibm.com/Workspace/kui3/plugin-kubeui\u0007"

great, thanks!


Use browser APIs for URL manipulation

Fixes #73
https://caniuse.com/url
https://caniuse.com/urlsearchparams

Thanks for the fix, @fredden!

Tagged 1.1.21 release with this fix. Thanks again 👍


Add more random Avatar generators (DiceBear, Robot) and make it configurable

DiceBear: https://codeberg.org/Codeberg/avatars
Robot: https://github.com/lafriks/go-avatars
None: use default images

[x] POC
[ ] Settings via ini
[ ] more tests :)

Can such feature be optional? I just worry if we introduce too many packages, the size of Gitea binary would become too big, sooner and sooner.
And it seems that the random avatar can use the "gravatar" mechanism, just point the gravatar webserver to the  DiceBear avatar server.

the problem ... as is what you propose would be best to solve via #2222 whitch to not exist :/

Maybe #14799 can be easily fixed by a left-right mirror random avatar.

Please have a look at:

https://github.com/go-gitea/gitea/pull/17707

Should this be added as a second option or be closed since #17707 is merged?

I'm for a second option since it does not add mouch to the size ... but asap we have a plugin system we should make both to plugins and fallback to the "default" avatar

and about the svg lib: I'll also use that for other features ... like the request to be able to upload svg as profile image etc ...

ps: the random generated DiceBear avatars have beard/braid, I think it's not suitable for a general purpose avatar generator before we know user's gender or preference.

We could also use my library https://github.com/lafriks/go-avatars (it does generate png avatars also)

Quote my question:

Can such feature be optional? I just worry if we introduce too many packages, the size of Gitea binary would become too big, sooner and sooner.
And it seems that the random avatar can use the "gravatar" mechanism

To avoid code bloat, do we really want to introduce new avatar generators? Could the avatars provided by external gravatar servers instead of compile code into Gitea?

TAGS="bindata sqlite sqlite_unlock_notify" make build -j1
before (0d05bdbea8a4ffdd37e7268db75f7a1a8fdcadfb): 84M (85384)
at 0a0b147513e5e5f56cc6475ec406ab49b497a0c1: 84M (85900)
at 8c6bed3f1956f9e95c8c81fc4223afb6851b23b9: 85M (86196)
so I think we can remove monsterid and wavatars
but the rest should be good to go - and yes you can use gravatar like service but it will not be that fine granular & easy to do for selfhost admins

To avoid bloating Gitea's code base, let users use their own avatar service (like self-maintained gavatar) to provide their customized avatars?
After #17707 , nobody complains about swastika avatars #14799

I am cleaning stale/pending PRs, according to the discussion and vote above, I think this PR could be closed.


Always being prompted for 2FA key when using the cred file

Good morning!
The last few releases I've noticed that I'm now always being prompted at startup for the 2FA key even though I'm using the cred file approach:
blink = Blink()
auth = Auth(json_load("c:\Blinkpy\cred.json"))
blink.auth = auth
blink.start()
blink.save("C:\Blinkpy\cred.json")
I'm not following how to change this to not be prompted, do I change:
auth = Auth(json_load("c:\Blinkpy\cred.json"), no_prompt=True)
Then add:
auth.send_auth_key(blink, )
blink.setup_post_verify()
Before blink.start()?
Where do I get the key from?  Should I do some sort of pre-auth script that forces it to generate a key and email me then plug this key into this script and will it work every time? I'm still getting a new key emailed to me about every 24 hours I have my service up and running.

Same here. On the first login, I sent the verification code I got by E-mail. Now I'm saving credentials
to file per the instructions. I see from log messages that the token gets refreshed more or less daily.
Except I get an E-mail with a new verification code every time, about once a day.
And yet, I don't lose access even if I don't send in the new verification code.
My code where I authenticate:
blink = blinkpy.blinkpy.Blink()
auth = blinkpy.auth.Auth(blinkpy.helpers.util.json_load(AUTH_FILE))
auth.no_prompt = True
blink.auth = auth
blink.start()
blink.save(AUTH_FILE)  # Write refreshed token.

I am having problems while sending the key.  I am not getting the response correctly for the send_auth_key() called by blink.start(). I am giving my credentials along with the key sent to my mail when prompted.
File "blink_capture.py", line 78, in
blink.start()
File "C:\Program Files\Python36\lib\site-packages\blinkpy\blinkpy.py", line 114, in start
self.setup_prompt_2fa()
File "C:\Program Files\Python36\lib\site-packages\blinkpy\blinkpy.py", line 121, in setup_prompt_2fa
result = self.auth.send_auth_key(self, pin)
File "C:\Program Files\Python36\lib\site-packages\blinkpy\auth.py", line 207, in send_auth_key
json_resp = response.json()
File "C:\Program Files\Python36\lib\site-packages\requests\models.py", line 898, in json
return complexjson.loads(self.text, **kwargs)
File "C:\Program Files\Python36\lib\json_init_.py", line 354, in loads
return _default_decoder.decode(s)
File "C:\Program Files\Python36\lib\json\decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Program Files\Python36\lib\json\decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

As of today, the usual token refresh returns a 403 error for me (and no PIN E-mail).
So I'm trying to login again from scratch.
On Wed, 8 Jul 2020, sakthiram wrote:

I am having problems while sending the key. I am not getting the response correctly for the send_auth_key() called by blink.start(). I am giving my credentials along with the key sent to my mail when prompted.
...
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Same here:
Expected json response from https://rest-u020.immedia-semi.com/networks, but received: 403: Forbidden
Ah...:
"[...]
The request could not be satisfied.

Bad request.
We can't connect to the server for this app or website at this time. There
might be too much traffic or a configuration error. Try again later, or
contact the app or website owner.

If you provide content to customers through CloudFront, you can find steps
to troubleshoot and help prevent this error by reviewing the CloudFront
documentation.

Generated by cloudfront (CloudFront)
[...]"
Works on my phone though.

Same here, I'm totally locked out now, any command including blink.start() gets a 403 return.

Seemed to recover, back to only the intermittent 403's which I still wish I could get rid of.

Hi @fronzbot, I still get the key emailed to me but the script does start without requiring me to input it after changing based on your recommendation:
from blinkpy.blinkpy import Blink
from blinkpy.auth import Auth
from blinkpy.helpers.util import json_load

blink = Blink()
# Can set no_prompt when initializing auth handler
auth = Auth(json_load("path/to/cred/file"), no_prompt=True)
blink.auth = auth
blink.start()


Access riven dashboard gets 500 Internal Error

Describe the bug
After initing, access riven dashboard gets 500 Internal Error
Docker Compose
version: "3.8"
services:
  DMB:
    container_name: DMB
    image: iampuid0/dmb:latest
    volumes:
      - /mnt/data/plex/DMB/config:/config
      - /mnt/data/plex/DMB/log:/log
      - /mnt/data/plex/zurg/RD:/zurg/RD
      - /mnt/data/plex/zurg/mnt:/data:shared
      - /mnt/data/plex/riven/data:/riven/backend/data
      - /mnt/data/plex/riven/mnt:/mnt
    environment:
      - TZ=Asia/Shanghai
      - ZURG_ENABLED=true
      - RD_API_KEY=xxxxxxxxxxxxxxxxx
      - RCLONE_MOUNT_NAME=real
      - RIVEN_BACKEND_ENABLED=true
      - RIVEN_FRONTEND_ENABLED=true
      - ORIGIN=http://<IP_ADDRESS>:3000
    ports:
      - 3000:3000
    devices:
      - /dev/fuse:/dev/fuse:rwm
    cap_add:
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
      - no-new-privileges

Logs
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | plex_watchlist.validate - Plex Watchlists is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | listrr.validate - Listrr is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | mdblist.validate - Mdblist is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | trakt.validate - Trakt is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | annatar.validate - Annatar is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | torrentio.validate - Torrentio is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | knightcrawler.validate - Knightcrawler is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | orionoid.validate - Orionoid is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | jackett.validate - Jackett is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | torbox.validate - TorBox Scraper is set to disabled
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | mediafusion.validate - Mediafusion is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | prowlarr.validate - Prowlarr is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | zilean.validate - Zilean is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | comet.validate - Comet is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | symlink.__init__ - Rclone path symlinks are pointed to: /data/real/__all__
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | symlink.__init__ - Symlinks will be placed in: /mnt
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | ✔  SUCCESS   | symlink.__init__ - Symlink initialized!
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | plex.validate - Plex Updater is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | local.validate - Local Updater is set to disabled.
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | 🔗 DEBRID    | realdebrid.validate - Your account expires in 51 days.
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | ✔  SUCCESS   | realdebrid.__init__ - Real Debrid initialized!
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | torbox.validate - Torbox downloader is not enabled
DMB  | Jul 26, 2024 13:28:03 - WARNING - Riven_backend: | alldebrid.validate - All-Debrid is set to disabled
DMB  | Jul 26, 2024 13:28:03 - ERROR - Riven_backend: | program.initialize_services - No Requesting service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:03 - ERROR - Riven_backend: | program.initialize_services - No Scraping service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:03 - ERROR - Riven_backend: | program.initialize_services - No Updater service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | 🤖 PROGRAM   | program.start - ----------------------------------------------
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | 🤖 PROGRAM   | program.start - Riven is waiting for configuration to start!
DMB  | Jul 26, 2024 13:28:03 - INFO - Riven_backend: | 🤖 PROGRAM   | program.start - ----------------------------------------------
DMB  | Jul 26, 2024 13:28:04 - INFO - Riven_backend: | 👾 API       | main.dispatch - GET /settings/get/all - 200 - 0.00s
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | overseerr.validate - Overseerr is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | plex_watchlist.validate - Plex Watchlists is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | listrr.validate - Listrr is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | mdblist.validate - Mdblist is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | trakt.validate - Trakt is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | annatar.validate - Annatar is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | torrentio.validate - Torrentio is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | knightcrawler.validate - Knightcrawler is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | orionoid.validate - Orionoid is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | jackett.validate - Jackett is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | torbox.validate - TorBox Scraper is set to disabled
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | mediafusion.validate - Mediafusion is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | prowlarr.validate - Prowlarr is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | zilean.validate - Zilean is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | comet.validate - Comet is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - INFO - Riven_backend: | symlink.__init__ - Rclone path symlinks are pointed to: /data/real/__all__
DMB  | Jul 26, 2024 13:28:04 - INFO - Riven_backend: | symlink.__init__ - Symlinks will be placed in: /mnt
DMB  | Jul 26, 2024 13:28:04 - INFO - Riven_backend: | ✔  SUCCESS   | symlink.__init__ - Symlink initialized!
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | plex.validate - Plex Updater is set to disabled.
DMB  | Jul 26, 2024 13:28:04 - WARNING - Riven_backend: | local.validate - Local Updater is set to disabled.
DMB  | Jul 26, 2024 13:28:05 - INFO - Riven_backend: | 🔗 DEBRID    | realdebrid.validate - Your account expires in 51 days.
DMB  | Jul 26, 2024 13:28:05 - INFO - Riven_backend: | ✔  SUCCESS   | realdebrid.__init__ - Real Debrid initialized!
DMB  | Jul 26, 2024 13:28:05 - INFO - Riven_backend: | torbox.validate - Torbox downloader is not enabled
DMB  | Jul 26, 2024 13:28:05 - WARNING - Riven_backend: | alldebrid.validate - All-Debrid is set to disabled
DMB  | Jul 26, 2024 13:28:05 - ERROR - Riven_backend: | program.initialize_services - No Requesting service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:05 - ERROR - Riven_backend: | program.initialize_services - No Scraping service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:05 - ERROR - Riven_backend: | program.initialize_services - No Updater service initialized, you must enable at least one.
DMB  | Jul 26, 2024 13:28:05 - INFO - Riven_backend: | 👾 API       | main.dispatch - POST /settings/set - 200 - 0.82s
DMB  | Jul 26, 2024 13:28:05 - INFO - Settings saved successfully.
DMB  | Jul 26, 2024 13:28:05 - INFO - Riven_backend: | 👾 API       | main.dispatch - POST /settings/save - 200 - 0.00s
DMB  | Jul 26, 2024 13:28:05 - INFO - Configuring Riven_frontend
DMB  | Jul 26, 2024 13:28:05 - INFO - Fetching latest riven-frontend release.
DMB  | Jul 26, 2024 13:28:06 - INFO - riven-frontend latest release: v0.2.5
DMB  | Jul 26, 2024 13:28:06 - INFO - Fetching release information from https://api.github.com/repos/rivenmedia/riven-frontend/releases/tags/v0.2.5
DMB  | Jul 26, 2024 13:28:07 - INFO - No assets found. Using zipball_url.
DMB  | Jul 26, 2024 13:28:07 - INFO - Downloading from https://api.github.com/repos/rivenmedia/riven-frontend/zipball/v0.2.5
DMB  | Jul 26, 2024 13:28:10 - INFO - Successfully downloaded rivenmedia-riven-frontend* and extracted to ./riven/frontend
DMB  | Jul 26, 2024 13:28:10 - INFO - Sucessfully downloaded the latest release for Riven_frontend
DMB  | Jul 26, 2024 13:28:10 - INFO - Automatic update disabled for Riven_frontend
DMB  | Jul 26, 2024 13:28:10 - INFO - Setting up Riven frontend
DMB  | Jul 26, 2024 13:28:20 - ERROR - The Riven frontend process is not running.
DMB  | Jul 26, 2024 13:29:21 - ERROR - The Riven frontend process is not running.
DMB  | Jul 26, 2024 13:30:05 - INFO - npm install complete
DMB  | Jul 26, 2024 13:30:05 - INFO - Starting Riven_frontend
DMB  | Jul 26, 2024 13:30:05 - INFO - Riven_frontend w/ None subprocess: Listening on <IP_ADDRESS>:3000
DMB  | Jul 26, 2024 13:30:23 - INFO - Riven_backend: | 👾 API       | main.dispatch - GET /services - 200 - 0.00s
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: TypeError: fetch failed
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at node:internal/deps/undici/undici:12500:13
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: [cause]: ConnectTimeoutError: Connect Timeout Error
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at onConnectTimeout (node:internal/deps/undici/undici:6621:28)
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at node:internal/deps/undici/undici:6573:50
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at Immediate._onImmediate (node:internal/deps/undici/undici:6605:13)
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: at process.processImmediate (node:internal/timers:478:21) {
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: code: 'UND_ERR_CONNECT_TIMEOUT'
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: }
DMB  | Jul 26, 2024 13:30:33 - INFO - Riven_frontend: }

It seems backend get the request: main.dispatch - GET /services - 200 - 0.00s, but somehow frontend timeout

I tried the "raw" method to deploy the stack. It seems when settings have some errors or incomplete , the onboard  setting page function normally. But with correct complete settings or finish the onboard settings, 500 error occurred

Great, it finally works! Though every time starting docker container needs to init poetry environment, really takes a long time


Fixed download of secrets back to all secrets

@jaykeshur This will fix missing KUBECONFIG files when created as secrets.

Added "-R", now LGTM


drag/drop item to menubar event?

I have no idea, I'd ask here https://github.com/atom/atom-shell/issues as it would need to be doable on mac, linux, windows for it to make it into atom-shell

This would be so great! Any recent developments that would enable it?

Trying to listen to drop-files event on menubar.tray but it never fires. Not sure what I'm missing, investigating :)
https://github.com/atom/electron/blob/master/docs/api/tray.md#event-right-clicked

Nevermind, I was using a older version of electron :) works now! :)


Crash when using soulglimmer pigment

crash-2022-06-08_09.29.25-client.txt

Do you have PAUCAL installed?
What version is it? For Hex Casting 0.8.x you should be on PAUCAL 0.3.4.

i have paucal 0.4.5

Try 0.3.4. 0.4.x versions won't work until we release hexcasting 0.9.

Considering this closed for now...


Restore the Azure Client

The null value is fixed here https://github.com/Azure/go-amqp/pull/336

Well done @Gsantomaggio!!!!


README: ProGuard changes for OkHttp 3.8.0

Brilliant, thank you. Wanna do Retrofit also?

@swankjesse Thanks for the offer but I do not currently use Retrofit so it would be an untested config. I guess the place to document it would be https://github.com/square/retrofit/blob/master/website/index.html

It's the same two additions.
On Sat, May 13, 2017 at 8:15 PM Andrew Shu<EMAIL_ADDRESS>wrote:

@swankjesse https://github.com/swankjesse Thanks for the offer but I do
not currently use Retrofit so it would be an untested config. I guess the
place to document it would be
https://github.com/square/retrofit/blob/master/website/index.html
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/pull/3354#issuecomment-301282442, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEEESohRkRhtW7MlmO-hk7uCOEZgxJ6ks5r5ke9gaJpZM4NaOjx
.

Go for it, I don't need to take credit for the PR on Retrofit.


Update RunCodeFormatter to temp build for VS2017

Issue: #451

[X] Tick here to confirm that you have run RunCodeFormatter.ps1

Description:
Updates RunCodeFormatter.ps1 to use a temporary build of CodeFormatter uploaded to Azure Storage that targets .NET 4.6. This is a temporary solution for #451 until CodeFormatter adds official support
Test:
On a machine with VS2017 (but not VS2015), run RunCodeFormatter.ps1 -ForceCodeFormatterDownload to download the latest CodeFormatter and check that it runs successfully

@stuartleeks,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Works well on a machine without Visual Studio 2015 now. I'm incorporating the changes in the master branch and we can revert back to other version of code formatter once supported. Good job


🌐 Add Chinese translation for docs/zh/docs/deployment/concepts.md

📝 Docs preview for commit 47abc02e26346c60678e8eea723af85de8a8b08a at: https://a19f2068.fastapitiangolo.pages.dev

📝 Docs preview for commit 758204d0808cd360c466de2cd7e57d9d8c1b1e22 at: https://8dd1d228.fastapitiangolo.pages.dev

Thanks for your interest! @xzmeng
Do you think this is ready to merge now with the suggested changes? Please let me know @socket-socket 🤓

@alejsdev It's good!

📝 Docs preview for commit d1a3b0d6bfd9ba0757c78d265e62df1777e2350f at: https://d0b5d225.fastapitiangolo.pages.dev

Thank you for the help! @xzmeng 🤓
And thanks for the review @socket-socket 🚀


UGVs are turning on NATO even if player built

Suspect the beginning of skynet.
In actuality object init is setting them to enemy side after mission begins. Suspect simple fix is to set all UGVs made within 5 seconds of mission start to friendly then, after that, do nothing to them and let them naturally spawn with the right crew

reproduction steps:
Repro 1:
build uav
make sure it doesn't kill you
Repro 2:
hack a enemy uav
bring it to fob
save and exit game
reload game
make sure it doesn't kill you

Appears fixed in b1a6063956b1a63c7ba5714df7a86ab4cf4a4557


Deploying a ScaledJob and ScaledObject fails

The deployment of a ScaledJob and a ScaledDeployment worked until yesterday, but today it is failing with the following error,
error: unable to recognize ".\\scale_job.yml": no matches for kind "ScaledJob" in version "keda.sh/v1alpha1"

The installed version of kedacore is 2.4.0
helm ls -n keda

NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION
keda    keda            1               2021-09-16 11:55:03.0501125 +0530 IST   deployed        keda-2.4.0      2.4.0

The scaled job was deployed through the following manifest definition,
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: azure-servicebus-auth
spec:
  podIdentity:
    provider: azure
---
apiVersion: keda.sh/v1alpha1
kind: ScaledJob
metadata:
 name: test-keda-scaledjob
 namespace: keda-python-sample
spec:
  jobTargetRef:
    parallelism: 1
    completions: 1
    activeDeadlineSeconds: 120
    backoffLimit: 6
    template:
      metadata:
        labels:
          app: order-processor-mi
          aadpodidbinding: sb-app
      spec:
       containers:
       - name: order-processor-mi
         image: <acr_name>/pysbmidemo:1.1.4
         env:
         - name: QUEUE_NAME
           value: "<receive_queue>"
         - name: QUEUE_NAME_REC
           value: "<send_queue>"
         - name: MY_POD_NAME
           valueFrom:
             fieldRef:
               fieldPath: metadata.name
  pollingInterval: 1
  successfulJobsHistoryLimit: 2
  failedJobsHistoryLimit: 50
  # envSourceContainerName: {container-name}
  maxReplicaCount: 100
  triggers:
  - type: azure-servicebus
    metadata:
      queueName: "<receive_queue>"
      namespace: "<service_bus_namespace>"
      messageCount: "1"
    authenticationRef:
      name: azure-servicebus-auth

Moving the issue to Keda tahn charts


vitest/browser fails to run when the dependent package has storybook

Describe the bug
If a project has Storybook as a dependency, tests that used to succeed will now fail.
Test case:
import { test, expect } from "vitest";

test("sample", () => {
  expect(1 + 1).toBe(2);
});

Error message:
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Reload Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: Vitest failed to load "vitest/utils" after 10 retries.
 ❯ WebSocket.<anonymous> ../../../../../../__vitest_browser__/index-30Y0Db8-.js:977:36

Caused by: ReferenceError: exports is not defined
 ❯ ../../../../../../node_modules/util/util.js:33:1

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  no tests
      Tests  no tests
     Errors  1 error
   Start at  01:03:19
   Duration  3.56s (transform 0ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)

 FAIL  Tests failed. Watching for file changes...
       press h to show help, press q to quit
Cancelling test run. Press CTRL+c again to exit forcefully.

Reproduction
https://github.com/odan-sandbox/vitest-browser-issue-with-storybook
System Info
System:
    OS: macOS 14.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 102.89 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.local/share/asdf/installs/nodejs/18.12.1/bin/node
    Yarn: 1.22.19 - ~/.local/share/asdf/installs/nodejs/18.12.1/bin/yarn
    npm: 8.19.2 - ~/.local/share/asdf/plugins/nodejs/shims/npm
    pnpm: 8.10.5 - ~/.local/share/asdf/installs/nodejs/18.12.1/bin/pnpm
  Browsers:
    Chrome: 120.0.6099.234
    Safari: 17.1
  npmPackages:
    @vitest/browser: 1.2.1 => 1.2.1
    vitest: 1.2.1 => 1.2.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Thanks for raising an issue.
It looks like there is something wrong when util (node util polyfill https://github.com/browserify/node-util) installed. I can reproduce the same error by just adding util without storybook https://github.com/hi-ogawa/repro-vitest-browser-basic/pull/2
I'm suspecting that the issue is related to loupe (used by Vitest for formatting internally) has require("util") and Vite's resolution and deps optimization is confused by locally install util https://github.com/chaijs/loupe/blob/9b8a6deabcd50adc056a64fb705896194710c5c6/src/index.ts#L34

I'm glad to see that the issue has already been reported. As a temporary solution, I'm currently removing it from the bundle using a custom plugin. I would appreciate knowing if there are any better solutions available.
export default defineConfig({
  plugins: [
    // ...
    {
      name: "exclude-util-package",
      transform(_src: string, id: string) {
        if (/node_modules\/util/.test(id)) return { code: "", map: null };
      },
    },
  ],
  // ...
  test: {
    globals: true,
    browser: {
      enabled: true,
      name: "chrome",
      headless: true,
    },
  },
});


Changed the text doc a little bit in order to make it more readable

Fixes:

Coverage remained the same at 74.658% when pulling e1bf400665e7255893bde05ec1f3a3ac8c3fe1e3 on omershtivi:docs into 2693a569506f5d5150c5e122fba3fb640ab7a358 on respawner:master.

Coverage remained the same at 74.658% when pulling e1bf400665e7255893bde05ec1f3a3ac8c3fe1e3 on omershtivi:docs into 2693a569506f5d5150c5e122fba3fb640ab7a358 on respawner:master.


Standardize the name of Android API level annotations

Rename min_api_version, max_api_version and target_api_version to android_api_min, android_api_max and android_api_target. It fits better with the other android_ annotations (as seen in lib/android/aware.nit) and with the app_ annotations.

Please ignore the first commit, it is from #1325.

+1

+1

+1

@xymus can you solve merge conflicts? I prefer that you hold the knife yourself.


Undefined index

I just restored default error handler and got multiple notices.
Notice: ob_end_clean() [ref.outcontrol]: failed to delete buffer. No buffer to delete in D:\www\flight\net\Response.php on line 154
Notice: Undefined index: router in D:\www\flight\core\Dispatcher.php on line 74
Notice: Undefined offset: 1 in D:\www\flight\net\Router.php on line 61
Notice: Undefined index: router in D:\www\flight\core\Dispatcher.php on line 74
Notice: Undefined index: request in D:\www\flight\core\Dispatcher.php on line 74
Notice: Undefined index: HTTP_X_REQUESTED_WITH in D:\www\flight\net\Request.php on line 50
Notice: Undefined index: CONTENT_TYPE in D:\www\flight\net\Request.php on line 54
Notice: Undefined index: CONTENT_LENGTH in D:\www\flight\net\Request.php on line 55
Notice: Undefined index: GET in D:\www\flight\net\Router.php on line 123
Strict Standards: Only variables should be passed by reference in D:\www\flight\Flight.php on line 279
hello world!
Notice: Undefined index: response in D:\www\flight\core\Dispatcher.php on line 74

Here is my code:
require 'flight/Flight.php';
restore_exception_handler();
restore_error_handler();
error_reporting (-1);
Flight::route('/', function(){
  echo 'hello world!';
});
Flight::start();

Fixed in commit 830088733dce12ac441046474d1ae7e07cfb477e


Tiny deprecation fix

As per http://refactorcop.com/DefactoSoftware/Hours

Hound makes a good point, but 'bundler/setup' does need the single quotes to avoid extra backslashes, and it seems weird to me to have both double and single quotes on one line without a reason (interpolation).

Thanks for the change!
Don't worry about hound here, but I don't think that your change needs single quotes:
require "bundler/setup"

Is totally valid
What we do not want are things like:
"this string \"needs\" backslashes"

Then we'd prefer:
'this string "needs" backslashes'

Our styleguide is to always use double quoted strings, the reason being that this way most strings will use the same quotes, there's no real benefit in using single quotes, and this way you can add an interpolation without having to change the strings quotes.


Babel 7

Babel 7 was recently released so I gave a shot at upgrading it. Followed the advice from the official upgrade guide here. Also, stage presets were removed so I used babel-upgrade to make sure we had the relevant plugins for stage 0 (as we had until now).

Coverage remained the same at 100.0% when pulling 98a197d6492e2d8ca3e81ca4b8c494600a3c5ace on babel-7 into 98f5c0e5bc54a5540466515e38dea9e9cb752019 on master.

Fixed the base to be 'dev' instead of 'master' and added a a fix to #2297.


Add barrows door highlight

This adds a green/red highlight on doors depending on unlocked/locked. This will help being able to see what path is useful to take at a glance.
Currently I am using strange old lockpicks to reach the center, but obviously I want to minimize the use of them so I try and take as many unlocked doors as possible, but it's not always obvious which ones are unlocked as sometimes it's too dark to distinguish the slightly paler unlocked doors. This change allows me to see it way more easily. I believe this isn't against the 3rd party client guidelines set out by Jagex.

Exists as a phub plugin


Add link to openstack_client_exporter

How does this differ from the openstack exporter we already list, and have you talked to the listed one's maintainers about changes you'd like to make?

They have both different functionalities and a different level of access to the OpenStack APIs.openstack_client_exporter works with an unprivileged user within a single project to ensure that user facing functionalities are working. It does so by creating an instance and sshing into it, uploading and retrieving files from the object store, ...The existing openstack_exporter needs admin credentials and is useful for retrieving global cloud metrics but create or delete an resources by itself.I'm not sure it would make much sense to try to combine both of them in a single exporter.On Jul 19, 2019 21:51, Brian Brazil<EMAIL_ADDRESS>wrote:How does this differ from the openstack exporter we already list, and have you talked to the listed one's maintainers about changes you'd like to make?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Okay, so this is more of a blackbox exporter. Can you put Blackbox in the entry name?
openstack_client_spawn_timing and friends should include their unit in the metric name, openstack_client_spawn_success and openstack_client_object_store_success should not have the error as a label - that's a matter for logs.

Okay, so this is more of a blackbox exporter. Can you put Blackbox in the entry name?

Yep, done.

openstack_client_spawn_timing and friends should include their unit in the metric name

Good point, I'll look into releasing a new version with s/_timing/_seconds/.

openstack_client_spawn_success and openstack_client_object_store_success should not have the error as a label - that's a matter for logs.

Conceptually, I agree. However, it is a pretty convenient way to create annotations in a grafana dashboard with the reason why something failed.

Conceptually, I agree. However, it is a pretty convenient way to create annotations in a grafana dashboard with the reason why something failed.

Doing logging in a metrics system can easily lead to both cardinality and semantic issues, it should be avoided.


Graphite Emitter Issue Druid 0.14

I'm using Druid 0.14 and try sending metrics to graphite.
I'm using the following configuration in the common file and the graphite metrics Are not sent I try it in the coordinator and the historicals service and still nothing is being sent.
Important to say that we worked with graphite emitter in druid 0.9 and everything worked smoothly.
Attached the logs and my configuration! thx!
When the service is up it wrote this lines to the log file
2019-07-10T20:32:00,666 INFO [main] org.apache.druid.guice.JsonConfigurator - Skipping druid.emitter.graphite.hostname property: one of it's prefixes is also used as a property key. Prefix: druid
2019-07-10T20:32:00,666 INFO [main] org.apache.druid.guice.JsonConfigurator - Skipping druid.emitter.graphite.port property: one of it's prefixes is also used as a property key. Prefix: druid
2019-07-10T20:32:00,666 INFO [main] org.apache.druid.guice.JsonConfigurator - Skipping druid.emitter.graphite.alertEmitters property: one of it's prefixes is also used as a property key. Prefix: druid
2019-07-10T20:32:00,667 INFO [main] org.apache.druid.guice.JsonConfigurator - Skipping druid.emitter.graphite.eventConverter property: one of it's prefixes is also used as a property key. Prefix: druid

My configuration
# Monitoring
druid.monitoring.monitors=["org.apache.druid.java.util.metrics.JvmMonitor"]
druid.monitoring.emissionPeriod=PT10s

druid.emitter=graphite
druid.emitter.logging.logLevel=info

# Graphite configuration
druid.emitter.graphite.hostname=my.graphite.domain
# Text port = 2003, Pickle port = 2004. Graphite emitter uses Pickle protocol
druid.emitter.graphite.port=2004
druid.emitter.graphite.eventConverter={"type":"all", "namespacePrefix": "app-druid-014",
# in milliseconds
druid.emitter.graphite.flushPeriod=10000
druid.emitter.graphite.alertEmitters=["logging"]

@vogievetsk
Hi Vadim,
I opened the issues 6 days ago and no response yet.
I didn't find someone which the graphite metrics worked for him with druid 0.14.
Is this a known issue?
By the way, when changing druid.emitter to logging, it writes the metrics to log but bit able to send them.

Facing the same issue.

It doesn't work, I have been told to upgrade Druid ...
On Mon, Oct 28, 2019 at 10:55 PM Viacheslav Chimishuk <
<EMAIL_ADDRESS>wrote:

Facing the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-druid/issues/8058?email_source=notifications&email_token=AAIQ4XY7VGR6ZKSPMHCOK6TQQ5GTTA5CNFSM4H7XN7K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECOLQDI#issuecomment-547141645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQ4X2RXR4RRT4M566FRVLQQ5GTTANCNFSM4H7XN7KQ
.

@alonshoshani, and it works for 0.16.0?

don't know, didn't try it yet
On Mon, Oct 28, 2019 at 11:25 PM Viacheslav Chimishuk <
<EMAIL_ADDRESS>wrote:

@alonshoshani https://github.com/alonshoshani, and it works for 0.16.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-druid/issues/8058?email_source=notifications&email_token=AAIQ4X3EUAFXCUCLF64YWGDQQ5KANA5CNFSM4H7XN7K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECOOC4A#issuecomment-547152240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQ4XYDA6DA5FAPYH57L7LQQ5KANANCNFSM4H7XN7KQ
.

I have tried to update to the latest version -- 0.16.0,  and still have the same issue.
2019-10-29T09:09:57,608 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.StatusResource
2019-10-29T09:09:58,084 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.BrokerQueryResource
2019-10-29T09:09:58,139 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.http.BrokerResource
2019-10-29T09:09:58,141 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.ClientInfoResource
2019-10-29T09:09:58,141 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.client.HttpServerInventoryViewResource
2019-10-29T09:09:58,147 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.query.lookup.LookupListeningResource
2019-10-29T09:09:58,147 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.query.lookup.LookupIntrospectionResource
2019-10-29T09:09:58,347 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.sql.http.SqlResource
2019-10-29T09:10:00,837 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.hostname property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,839 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.port property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,840 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.protocol property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,840 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.eventConverter property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,875 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.server.DruidNode] from props[druid.] as [DruidNode{serviceName='druid/broker', host='druid.env.geomotiv.com', bindOnHost=false, port=-1, plaintextPort=8082, enablePlaintextPort=true, tlsPort=-1, enableTlsPort=false}]
2019-10-29T09:10:00,904 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.curator.CuratorConfig] from props[druid.zk.service.] as [org.apache.druid.curator.CuratorConfig@2b5183ec]
2019-10-29T09:10:00,912 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.curator.ExhibitorConfig] from props[druid.exhibitor.service.] as [org.apache.druid.curator.ExhibitorConfig@73437222]

sorry to hear,
maybe just open them bug in github , I will vote for you.
send me the link
On Tue, Oct 29, 2019 at 11:30 AM Viacheslav Chimishuk <
<EMAIL_ADDRESS>wrote:

I have tried to update to the latest version -- 0.16.0, and still have the
same issue.
2019-10-29T09:09:57,608 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.StatusResource
2019-10-29T09:09:58,084 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.BrokerQueryResource
2019-10-29T09:09:58,139 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.http.BrokerResource
2019-10-29T09:09:58,141 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.server.ClientInfoResource
2019-10-29T09:09:58,141 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.client.HttpServerInventoryViewResource
2019-10-29T09:09:58,147 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.query.lookup.LookupListeningResource
2019-10-29T09:09:58,147 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.query.lookup.LookupIntrospectionResource
2019-10-29T09:09:58,347 INFO org.apache.druid.guice.Jerseys: Adding Jersey resource: org.apache.druid.sql.http.SqlResource
2019-10-29T09:10:00,837 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.hostname property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,839 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.port property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,840 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.protocol property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,840 INFO org.apache.druid.guice.JsonConfigurator: Skipping druid.emitter.graphite.eventConverter property: one of it's prefixes is also used as a property key. Prefix: druid
2019-10-29T09:10:00,875 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.server.DruidNode] from props[druid.] as [DruidNode{serviceName='druid/broker', host='druid.env.geomotiv.com', bindOnHost=false, port=-1, plaintextPort=8082, enablePlaintextPort=true, tlsPort=-1, enableTlsPort=false}]
2019-10-29T09:10:00,904 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.curator.CuratorConfig] from props[druid.zk.service.] as [org.apache.druid.curator.CuratorConfig@2b5183ec]
2019-10-29T09:10:00,912 INFO org.apache.druid.guice.JsonConfigurator: Loaded class[class org.apache.druid.curator.ExhibitorConfig] from props[druid.exhibitor.service.] as [org.apache.druid.curator.ExhibitorConfig@73437222]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-druid/issues/8058?email_source=notifications&email_token=AAIQ4X4EIMKW37LT67BTPTLQQ77DNA5CNFSM4H7XN7K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECP2ATI#issuecomment-547332173,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQ4X4ADORI27WUGJ5662LQQ77DNANCNFSM4H7XN7KQ
.

We have this one, I guess we can use it.
@leventov, sorry, if I have cast a wrong person. I see you as active Druid contributor. Do you know any plans for this issue?
Thanks in advance.

I don't know of any plans.
In general, unless you come along with a PR yourself, it's unlikely that anyone will debug and solve this issue for you.

@leventov, I see. Thank you for the reply.


Deployment issues for Openshift.io

I tried using my Openshift.io account to test nodeshift out.  Here is what happened:
First i logged in like this:
oc login https://api.starter-us-east-1.openshift.com --token=MB8Y_fIBPQWcmoq5tS4N3ub7-aHfHRZ-D8B0x6jXyFY

Then created a new project using the oc commands as normal
oc new-project oso-node-demo

Then using the example app i've been using, https://github.com/bucharest-gold/nodejs-rest-http, i ran the npm script
npm run openshift

When i got to the step that pushes the binary up, i first got this message(on the builds details screen)
Failed to create build pod: No API token found for service account "builder", retry after the token is automatically created and added to the service account.

I just waited and maybe a minute later, the s2i build actually started and but there was an authentication issue when trying to push the image to the internal repository
Receiving source from STDIN as archive ...

Pulling image "bucharestgold/centos7-s2i-nodejs:latest" ...

Pulling image "bucharestgold/centos7-s2i-nodejs:latest" ...

---> Installing application source

---> Building your Node application from source

---> Using 'npm install'

added 50 packages in 3.546s

Pushing image <IP_ADDRESS>:5000/try-again/nodejs-rest-http:latest ...

error: build error: Failed to push image: unauthorized: authentication required

Then i decided to try the swarm booster i've been playing with to see if that had an issue also, but it built and deployed without an issue.
I then ran npm run openshift again, and i didn't get any of the error messages from before and the image was successfully pushed into the internal repository
It's very possible the maven plugin is doing something wrt authentication that is differnt on Openshift.io than it is on minishift

Just an update:
I went back and tried the process again,  first i had to login again, then ran the npm script
same errors from before.
I came back a couple hours later and ran npm run openshift again,  and everything worked.  This time without doing the maven stuff.
It took a while before the exposed route was ready,  but i don't think that is nodeshifts issue.

I just deployed the REST level 0 booster, https://github.com/bucharest-gold/nodejs-rest-http , successfully on my starter account(ca-central-1)
closing


[flutter_tools] handle case where file is deleted by other program or running on read only volume

Description
I've seen some odd bugs in crash reporting where the tool fails to delete a file that it just checked does exist. It could be that a different program was deleting the file and the timing was just right. Be defensive to this and test on an OSError of 2 if it still exists. If it does, then it is probably pointing at a read-only volume
Fixes https://github.com/flutter/flutter/issues/57950

Friendly ping @zanderso


Add statistics for prod86 studies

This was generated using https://github.com/IDR/idr-utils/pull/16 and
/opt/omero/server/venv3/bin/python ~/idr-utils/scripts/stats.py --release prod86 idr0048-abdeladim-chroms idr0085-walsh-mfhrem/ -vvv  >> ~/idr.openmicroscopy.org/_data/studies.tsv

The command completed in a few seconds

A few seconds is impressive! When I tried idr0048-abdeladim-chroms yesterday on a test server it hung for about an hour before failing...

Arguably I ran it from omeroreadwrite on prod86 i.e. where the studies got imported in the first place. Maybe I benefited from caching?

LGTM


made a google colab ☀, feel free to share on your repo

https://colab.research.google.com/drive/1FZ2vRE_uMaNShLKZGDY5hFP6GcGmU12z

Good works :+1:
Hopefully this colab will be featured to the Readme section :eyes:

@valleballe Nice work! Would you mind me modifying it a little and share a copy? All the credits will be kept, I just want to display a different scene.

@ashawkey sure no problem!

@valleballe Nice work! Would you mind me modifying it a little and share a copy? All the credits will be kept, I just want to display a different scene.

Dear @valleballe , thanks for your amazing work! But I encounter some problems, after I ran all the requirements, I ran the COLMAP, but all I get is stuck in "Exhaustive feature matching", why this will happen? I'm using the free version of Colab, and it shows that I have "zero compute units available".
Do you know if this is normal? because it stuck there for a while, or is it just too slow due to using CPU to compute, so it's still going?

work! But I encounter some problems, after I ran all the requirements, I ran the COLMAP, but all I get is stuck in "Exhaustive feature matching", why this will happen? I'm using the free version of Colab, and it shows that I have "zero compute units available".

@godisme1220 you most likely will have to upgrade your Google Colab subscription.

@ashawkey

@valleballe Nice work! Would you mind me modifying it a little and share a copy? All the credits will be kept, I just want to display a different scene.

@ashawkey Did you manage to get it to work? I am also a bit curious about the Colab implementation since I did not manage to get usable results on the example for custom data. I wonder if it is because of instant-NGP or colmap not performing well on environmental scenes with atypical camera paths.

Cool job, but when i run STEP 2: Generate a NeRF model of the data, it mentioned as belows. So how can i handle this? Thanks a lot~

Cool job, but when i run STEP 2: Generate a NeRF model of the data, it mentioned as belows. So how can i handle this? Thanks a lot~

I encountered totaly the same problem with you. Dose someone know how to fix it?


Zero-shot evaluation for downstream datasets?

Firstly, I would like to express my appreciation for the insightful research presented in the paper.
The paper shows the results:

baseline: training the model without pretraining on MALS
APTM: training the model with pretraining on MALS

I am interested in understanding the zero-shot performance, where no further training is performed after pretraining on MALS. Specifically, I would like to see evaluation results on the downstream datasets(CUHK-PEDES, ICFG-PEDES, and RST-PReid):

zero-shot: no training, just the model pretraining on MALS, then test on downstream datasets

During pre-training, we used the CUHK-PEDES test set for evaluation, which should provide the experimental results you need. You can try it out.