Support for enderchest plugins

Would it be possible to add support for plugins that provide multiple ender chests, such as AdvancedEnderChests? In this plugin I access a Gui via "/aec" which Is what I would like the enderchest to open instead of the vanilla chest. Something as simple as a config to execute a command on click instead of opening the inventory would be sufficient.
P.S. Apologies for my previous issue

Is this the plugin you mean?
If so for true compatibility (opening shulker boxes within these new ender chests, without any dupes) I'd have to get in touch with the developer to see if I can get a copy to test with, since it's a paid plugin
Simplest way to do it could be if the plugin has a similar feature where you right click on/with an ender chest
Then making that take priority over this plugin would do the trick

P.S. Apologies for my previous issue

All good, I suspected as much :)

Yes, that's the plugin.

Apologies, I am little pressed for time for the rest of the year so won't be looking into this for a bit, assuming you have built the plugin using your PR #15 and are happy with that solution for now
When I revisit this my compatibility concerns (that just executing a command won't solve) are:

Will ender chests implemented by the plugin support right-clicking on shulker boxes inside them, correctly with no duplication bugs
If so, if an admin uses the command to see someone else's ender chest through this plugin, they can likely move a shulker box that is already open and cause a duplication bug so would need to discuss with the developer

Until then I can't guarantee full compatibility so use at your own risk :)


State logic update

Update logic for RC state logic

Resolved over several commits (this is probably why people do PRs lol)


PNT-294: stale polling

This makes stale polling results fallback to the next data source. Once we find a datasource that is not stale (or we run out), we take the most recent quote out of our data sources. This would allow us to re-enable crypto on 1 forge, as that error they had awhile back was a stale price quote.
So questions for reviewers before I make this a not-draft pr:

Should I re-enable crypto on 1 forge in this PR?
Should we explicitly handle weekends for forex? (I think this is a must, just want to talk about how)

I ended up programming in the Open/Close market times for Forex and Commodities. Holidays and such will count as "open" and all data sources will be queried. So that means if you have 4 sources for forex, all 4 will be queried when the market is closed on an unusual time. Do you think we will need a syntax for "only fallback during a price error, not a stale error"?

Is 30 min a good "stale" duration?

@WhoSoup Can we merge this?


chore: Remove orphaned copy of troubleshooting-sil

Appears to be an older copy of https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/WindowsServerDocs/administration/software-inventory-logging/troubleshoot-sil.md that ended up in the root

Thanks, @nschonni!


Show have_enqueued_job deprecation warning only when called

Currently, when rspec-sidekiq is loaded, it always prints this deprecation warning:
[DEPRECATION] `have_enqueued_job` is deprecated.  Please use `have_enqueued_sidekiq_job` instead.

This PR ensures that the warning is only shown when the method is actually called.

Coverage increased (+0.3%) to 91.413% when pulling 675ee4fe927d5790592add1a03fd327c9f74a989 on makandra:fix-deprecation-warning into fc0e1f754b05a1796b9855971144ed2c1b2252b9 on philostler:develop.

Coverage increased (+0.3%) to 91.413% when pulling 675ee4fe927d5790592add1a03fd327c9f74a989 on makandra:fix-deprecation-warning into fc0e1f754b05a1796b9855971144ed2c1b2252b9 on philostler:develop.

Coverage decreased (-0.3%) to 90.859% when pulling 04896412eb8e8c959cca169a45f34d6512d625f2 on makandra:fix-deprecation-warning into fc0e1f754b05a1796b9855971144ed2c1b2252b9 on philostler:develop.

Coverage decreased (-0.3%) to 90.859% when pulling 04896412eb8e8c959cca169a45f34d6512d625f2 on makandra:fix-deprecation-warning into fc0e1f754b05a1796b9855971144ed2c1b2252b9 on philostler:develop.

Closed in favor of #130


Android documentation and CI

This series primarily adds CI and Documentation for Vulkan on Android.  A couple of other minor fixes I found when building RenderDoc on Linux.
Thanks to @michaelrgb for providing the basis of the documentation.

docs: Add Android documentation
Added a "How to" for Android.  Walks through how to modify your APK for debugging, and how to use the interface to target Android.

build: Add Android to travis config
Only targets one ABI, but is sufficient for smoke testing Android builds.  Also packages the RenderDocCmd APK.  All the builds could probably be sped up with some caching, but I did not introduce that here.

android: Attempt to call adb directly if path not provided
Before I had documentation, I lost some time when "adb" calls from the interface weren't succeeding.  This change simply tries to use adb from PATH if not provided in the UI.

android: Target android-23 explicitly for APK
Using "1" here was very specific to the build system, as noted by the comment.  When run on systems with older APIs install, it resulted in java compile errors.  This will still run on Marshmallow and newer Android installs.

Thanks for the android CI support. It would be nice to tidy up the travis config a bit to remove all the VAR=0 specifiers and just have the scripts handle them being empty instead of 0, but that can happen separately.
I'm not sure if this is the right time to sort out the documentation though. I discussed this before with @michaelrgb offline, but I think we should first make improvements to get the android support ready for public use before committing the documentation. For now android is still an internal-only thing that's more user-unfriendly than it needs to be.
I'd like to document it once we've smoothed out the issues, since some of the steps necessary will be gone. Plus even if it's kind of unannounced, a documented feature is something that users will expect to work well.

Okay, I'll join the offline conversation. :)  Feel free to cherry-pick the other changes and hold off on the documentation.  Or I can submit another PR.

Thanks! I've merged in the CI changes.


Add support for custom rules with no priority

Current version need a priority for each custom rule. We should add the ability to set the priority for custom rules if not specified.

@dcaro Thanks for opening this issue. Currently we don't support default priority value in custom rules, but the predefined rules does.


Can anyone provide the multi-GPU version of image re-training would be great !!!!

Can anyone provide the multi-GPU version of image re-training(retrain.py) would be great !!!!

Worked?

Not working!!!

@inkritillc sloved it？

did you find the multi-GPU version of retrain.py?


What is the performance gain?

Hello, @cyrusbehr, I can see that you provide tensorRT model for C++ inference. Currently, I am using tensorRT's .engine model exported for python API and it's working around 60% faster (in object tracking) compared to pytorch's .pt model. I wonder if I can make it more faster (with little or no accuracy drop) with your solution. Do you have any estimates on this, like how much faster it gets and what % accuracy is lost (specific to your GPU model)? Thank you a lot!

The accuracy should be the same since you are using the same underlying inference engine (TensorRT in both cases). You can get more performance if you switch to using FP16 inference instead of FP32 inference.
If you provide me with the Python TensorRT inference code, I can run benchmarks on my end and compare those with C++ implementation to provide you with a comparison.

@cyrusbehr Thank you, I now understand. I benchmarked .pt, .onnx and .engine models with yolov8's tracking and got faster performance on .engine. I wrote a simple code to compare:
from ultralytics import YOLO
import time

models = {
    'pt model': 'custom.pt',
    'onnx model': 'custom.onnx',
    'engine model': 'custom.engine'
}
times = 100

execution_times = {}
average_times = {}

for model_description, model_name in models.items():
    model = YOLO(model_name)
    execution_times[model_description] = []
    total_time = 0

    # print(f"{model_description}:")
    for run in range(1, times + 1):
        start_time = time.time()
        results = model.track(line_thickness=1, source="F:/v8/ultralytics/assets/video.mp4",show=True, imgsz=(736, 1280), verbose=False)
        execution_time = time.time() - start_time
        execution_times[model_description].append(execution_time)
        total_time += execution_time

    average_time = total_time / times
    average_times[model_description] = average_time

print("Execution:")
header = "{:<20}".format("Model")
for model_description in models.keys():
    header += "{:<20}".format(model_description)
print(header)

max_runs = max(len(times) for times in execution_times.values())

for run in range(max_runs):
    row = "{:<20}".format(f"Run {run+1}:")
    for model_description in models.keys():
        exec_time = execution_times[model_description][run]
        row += "{:<20.3f}".format(exec_time)
    print(row)

avg_row = "{:<20}".format("Avg time")
for model_description in models.keys():
    avg_time = average_times[model_description]
    avg_row += "{:<20.3f}".format(avg_time)
print(avg_row)

Not sure if it'd be useful but still.

Great thank you for sharing the script.

@cyrusbehr Hi, thank you very much for this project! I'm trying to evaluate the performance. Could not get to the pointers that were introduced in this article - https://www.stereolabs.com/blog/performance-of-yolo-v5-v7-and-v8 /.  I want to share my performance indicators. It was possible to access Ubuntu 18.04 and on Tesla T4, A2, A100 cards (when building OpenCV, it is impossible to load CUDA_ARCH_BIN for the console card - https://arnon.dk/matching-sm-architectures-arch-and-gencode-for-various-nvidia-cards /).
On Tesla A2:
  model yolov8n:
    1280x720- 138 FPS;
    640x480 - 168 FPS;
  model yolov8x:
    1280x720 - 35 FPS;
    640x480 - 36 FPS.

On Tesla A100, yolov8n:
  640x480 - 248 FPS;
  1280x720 - 230 FPS.

On Tesla T4:
  1280x720 - 196 FPS.

Please share your performance results. Do you have any ideas how colleagues managed to achieve 1000+ FPS?

Thanks for sharing the benchmarks. I imagine those numbers were attained with the use of batching. Even then, a 5X speed up would be required to achieve 1000 FPS. I’ll need to run some benchmarks on my end and get back to you.

If you provide me with the Python TensorRT inference code, I can run benchmarks on my end and compare those with C++ implementation to provide you with a comparison.

May I expect any news on this, @cyrusbehr ?

@pva22 I pushed a change which cuts down on some of the preprocessing time (ex. Benchmark using an image which is already 640x640, RGB, and in GPU memory), so that cuts the time down a bit. Even then, I'm having a hard time seeing how they achieved 1000+FPS
On my 3050 Ti Laptop GPU and i9 11th gen, using yolo8n
======================
Avg time:
3.825ms

Avg FPS:
261 fps
======================

I've created a branch timing which you are welcome to checkout. It breaks down the timing:
ex.
Preprocess time: 144us
Inference: 2581us
Postprocess time: 959us

Seems quite a lot of time is being taken up by post-processing. The post processing (bbox decoding and NMS) is done entirely in CPU memory. I probably need to do it in GPU memory using cuda kernels to speed things up.

@bit-scientist
I tried your provided script, and also tried writing my own, but in the end, I decided to just use the command that Ultralytics used for their benchmakrs:

I use the yolov8n model.
On my 3050 Ti Laptop GPU the results are Speed: 0.7ms preprocess, 6.4ms inference, 0.0ms loss, 0.5ms postprocess per image which is a total of 7.6 ms. You can compare that to my results breakdown above.

On my RTX 4090 and Intel(R) Xeon(R) W-3323 CPU @ 3.50GHz, my implementation:
Benchmarking complete!
======================
Avg time:
3.6974ms

Avg FPS:
270 fps
======================

With a sample breakdown of times:
Preprocess time: 151us
Inference: 1372us
Postprocess time: 2015us

So the post processing is definitely the bottle neck. I need to work on that.
Running yolo val detect data=coco128.yaml batch=1 device=0 yields the following:
Speed: 0.3ms preprocess, 7.6ms inference, 0.0ms loss, 0.8ms postprocess per image

You can check out the Benchmarking section here

@cyrusbehr appreciate your efforts, thanks.

If you want a faster implementation, check this one out. It's faster than the one I've written. It's also much more complex though, it involves using the TensorRT API to build the graph from scratch.


fix: update resolves docs

I think there is something wrong that a sentence of resolves descrition .
Use it to unwrap value from pending promise and assert its value with usual assertions.

Shouldn't we be able to wrap value when promise is fulfilled, instead of pending?

Promise is pending if it was not fullfilled/rejected. Your sentence implies it should be called like this:
expect(await promise).resolves.toBe('smth');

But it Promise will always be pending if it was passed just as is (because microtask wasn't fired yet), so current wording is more correct

You're right, I'll have to think about it.
thanks.


Generated API docs

Also include best practices around RFC / specs?
https://gitlab.liris.cnrs.fr/edp/mkdocs_template/-/tree/master
https://squidfunk.github.io/mkdocs-material/getting-started/

Portray ( https://timothycrosley.github.io/portray/ ) seems nice. It has comprehensive docs, respects pyproject.toml, and includes expand source code a la PyTorch docs.


Us04 porta slot

Coverage remained the same at 100.0% when pulling 757efbf61a27117116bf8cac934c0dfa3f9bb746 on US04-Porta-Slot into 92c5ecd011b8260901c4a1c4609bfbeb25c63541 on master.


Support running in dev mode inside of a Docker image by binding to all available network interfaces

per our earlier discussion, I'm guessing this isn't needed any more?

Yes, it's not important anymore. Kiva's dev setup was very very unorthodox and I managed to talk them out of it. Closing


Move column validator into columnInternals

Pull Request
🤨 Rationale
Resolves #1389
👩💻 Implementation
Previously, any column that had validation associated with it would:

Create a validator class that derives from ColumnValidator
Create a class member within the column that was the validator, making sure that it was defined in the appropriate order within the file so that it got instantiated before it was used in any change handlers
Override the base TableColumn implementation of the validity getter to return the validity object from the class member's validator

With these changes, a column that has validation associated with it will:

Create a validator class that derives from ColumnValidator
Create an instance of the validator as part of creating its ColumnInternalsOptions, and return it as the validator property in the ColumnInternalsOptions
Use the validator returned from getTypedValidator on the base TableColumn to perform validation

Note, the validator is owned by the column's columnInternals instance, but the column is the one that knows the type of the validator instance. Making TableColumn generic on the type of the validator proved problematic because of the way the mixins work. Similar to the fact that a given table column instance isn't strongly typed for TColumnConfig, it also isn't strongly typed for the validator type. Therefore, calling the new getTypedValidator utility allows columns to be written with a strong assertion that the validator has the expected type.

🧪 Testing

Mostly relying on unit tests still passing for table columns and the table
Manually spot checked a few table columns to make sure validation still worked as expected

✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@atmgrifter00, will you buddy this PR for me?

Closing this PR in favor of #1999


[1.x] Add BatchNormWithReLU fp32/bf16

Description
@pengzhao-intel @TaoLv
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [sanity, unix-gpu]

@mxnet-bot run ci [sanity]

@mxnet-bot run ci [sanity]

how is the change tested?

forget to cherry-pick #17679 from master and test added.

@mxnet-bot run ci [edge, macosx-x86_64]

@mxnet-bot run ci [edge, centos-gpu]

@mxnet-bot run ci [centos-cpu]

@szha can you help take a look at the ci?

there are some issues on the 1.x CI and the team is working on it. once resolved, we can trigger the CI for this PR again.

there are some issues on the 1.x CI and the team is working on it. once resolved, we can trigger the CI for this PR again.

Thanks a lot!

@mxnet-bot run ci [centos-cpu, centos-gpu, edge, unix-cpu, unix-gpu, windows-gpu]

@mxnet-bot run ci [centos-cpu, centos-gpu, unix-gpu, windows-gpu]

@mxnet-bot run ci [unix-gpu]

@pengzhao-intel ready to merge now:)


Frontend for yields & raises docstrings

closes https://github.com/huggingface/doc-builder/issues/172

I know @LysandreJik was using warning blocks for the raises block to have something in color. Not sure whether it's something we want or not.

I like the current approach! Thanks @mishig25!

@LysandreJik

I like the current approach! Thanks @mishig25!

do you mean: you prefer using  for the raise?
if so, should I make this PR only render yields, which should look like returns?

Sorry, just realized I didn't answer: I was mentioning I like the approach you have taken in your PR, @mishig25

Bump on this, we're using Raises quite a bit in huggingface_hub and we would benefit from having this in :)
cc @Wauplin


super laggy / unresponsive

UI Version: 0.9.3
Description: maybe it's my old computer on these hot days but i'm getting very poor performance from voyager. Pages freeze all the time, clickable things never turn to the click cursor and the click itself hangs for ages before anything occurs

i noticed this yesterday as well on my new macbook pro in a highly air conditioned room.

maybe has to do with caching, which also encrypts the value, on every store update

Closed by #1121


Add preprint link to model_cards

Checklist

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[ ] I've added relevant tests for my contribution
[ ] I've updated the documentation and/or added correct docstrings
[x] I've assigned a reviewer
[ ] I've consulted ADS's internal developer documentation to ensure my contribution is in line with any relevant design decisions

Linked issues

Resolves #832

coverage: 93.854%. remained the same
when pulling 092f2850383e5152e8c737a3fbb70693170b32c2 on mb/832
into 4a5fc6c9898437c98287d1797c8d0d084fac1b00 on master.


PhotoView loses Scale on Rotation

While Rotating, the PhotoView loses scale.
Setting scale after rotation is not working too.

This should be resolved with #255 merge I've just done


NoSuchMethodError exception thrown

Hi! first, of all, I'd like to thank you for creating this framework, it's incredibly useful to me & (pretty sure) others!
Back to the point, the NoSuchMethodError exception is being thrown when attempting to access the player's locale (Player#getLocale) on 1.8.8. Such a method doesn't exist on 1.8.8 unfortunately.
java.lang.NoSuchMethodError: 'java.lang.String org.bukkit.entity.Player.getLocale()'

[02:10:10 WARN]:        at revxrsal.commands.bukkit.core.BukkitActor.getLocale(BukkitActor.java:90)

[02:10:10 WARN]:        at revxrsal.commands.command.CommandActor.errorLocalized(CommandActor.java:106)

[02:10:10 WARN]:        at revxrsal.commands.exception.DefaultExceptionHandler.missingArgument(DefaultExceptionHandler.java:25)

You can avoid the exception by adding a check that ensures that the server version is on a certain version (1.12.2 & higher) before attempting to execute the method.

Fixed in 3.0.1. Thank you for reporting!


Error calling subtitle_stream.decode()

Minimum repro:
# Any input that has a subtitle stream, codec does not matter
src = "/Users/wyattblue/projects/auto-editor/resources/subtitle.mp4"

c = av.open(src)
s = c.streams.subtitles[0]

for subset in s.decode():
    pass

zsh: segmentation fault  python3 test.py

Calling decode like this sidesteps the segfault and works as expected. This confirms this is our fault and not a downstream lib.
for subset in c.decode(subtitles=0):
    for sub in subset:
        print(sub)

Versions
OS: All (confirmed macos-arm64 macos-x86_64)
Python: All (confirmed 3.12, 3.11)
PyAVs: from at least 10.0.0, til 12.3.0rc1

(lldb) run test.py
Process 21360 launched<EMAIL_ADDRESS>(arm64)
Process 21360 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x0000000102804c2c libavcodec.60.31.102.dylib`avcodec_decode_subtitle2(avctx=0x000000014862f800, sub=0x0000000104282710, got_sub_ptr=0x000000016fdfdf54, avpkt=0x0000000000000000) at decode.c:972:9
   969  int avcodec_decode_subtitle2(AVCodecContext *avctx, AVSubtitle *sub,
   970                               int *got_sub_ptr, const AVPacket *avpkt)
   971  {
-> 972      int ret = 0;
   973
   974      if (!avpkt->data && avpkt->size) {
   975          av_log(avctx, AV_LOG_ERROR, "invalid packet: NULL data, size != 0\n");
Target 0: (Python) stopped.
(lldb) frame variable avpkt
(const AVPacket *) avpkt = NULL
(lldb) kill
Process 21360 exited with status = 9 (0x00000009) killed
(lldb) run test2.py
Process 21617 launched<EMAIL_ADDRESS>(arm64)
Process 21617 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x0000000102804c2c libavcodec.60.31.102.dylib`avcodec_decode_subtitle2(avctx=0x000000015b0a8450, sub=0x000000010423ea70, got_sub_ptr=0x000000016fdfddb4, avpkt=0x0000000159e28050) at decode.c:972:9
   969  int avcodec_decode_subtitle2(AVCodecContext *avctx, AVSubtitle *sub,
   970                               int *got_sub_ptr, const AVPacket *avpkt)
   971  {
-> 972      int ret = 0;
   973
   974      if (!avpkt->data && avpkt->size) {
   975          av_log(avctx, AV_LOG_ERROR, "invalid packet: NULL data, size != 0\n");
Target 0: (Python) stopped.
(lldb) frame variable avpkt
(const AVPacket *) avpkt = 0x0000000159e28050

seems to be related to this part
https://github.com/PyAV-Org/PyAV/blob/4bd4984daaf1c81731185e3bcada1e017ca1720c/av/subtitles/codeccontext.pyx#L14-L16

My patch stops the segfault but the functionality still does not work.

Won't it be as simple as changing SubtitleStream.decode(self, Packet packet=None) to SubtitleStream.decode(self, Packet packet)?


openjdk8-<IP_ADDRESS> fails to build, configure error

openjdk8 won't build in poudriere, failes to pass configure for Java.  It does seem to build the bootstrap and it exists but I suspect it cannot run.  It may be related to bootstrap-openjdk8:
WARNING: This port only exists for bootstrapping java/openjdk8.
You are advised to remove this port as soon as a stable JDK is built.
This OpenJDK implementation requires fdescfs(5) mounted on /dev/fd and
procfs(5) mounted on /proc.
If you have not done it yet, please do the following:
    mount -t fdescfs fdesc /dev/fd
    mount -t procfs proc /proc

To make it permanent, you need the following lines in /etc/fstab:
    fdesc   /dev/fd         fdescfs         rw      0       0
    proc    /proc           procfs          rw      0       0

======================================================================
`=======================<phase: configure      >============================
===>  Configuring for openjdk8-<IP_ADDRESS>
Warning: You are using legacy autoconf cross-compilation flags.
It is recommended that you use --openjdk-target instead.
Running generated-configure.sh
configure: loading site script /usr/ports/Templates/config.site
configure: Configuration created at Fri May 31 19:09:54 UTC 2019.
configure: configure script generated at timestamp<PHONE_NUMBER>.
checking for basename... /usr/bin/basename
checking for bash... /usr/local/bin/bash
checking for cat... /bin/cat
checking for chmod... /bin/chmod
checking for cmp... /usr/bin/cmp
checking for comm... /usr/bin/comm
checking for cp... /bin/cp
checking for cut... /usr/bin/cut
checking for date... /bin/date
checking for gdiff... no
checking for diff... /usr/bin/diff
checking for dirname... /usr/bin/dirname
checking for echo... /bin/echo
checking for expr... /bin/expr
checking for file... /usr/bin/file
checking for find... /usr/bin/find
checking for head... /usr/bin/head
checking for ln... /bin/ln
checking for ls... /bin/ls
checking for mkdir... /bin/mkdir
checking for mktemp... /usr/bin/mktemp
checking for mv... /bin/mv
checking for nawk... /usr/bin/nawk
checking for printf... /usr/bin/printf
checking for rm... /bin/rm
checking for sh... /bin/sh
checking for sort... /usr/bin/sort
checking for tail... /usr/bin/tail
checking for tar... /usr/bin/tar
checking for tee... /usr/bin/tee
checking for touch... /usr/bin/touch
checking for tr... /usr/bin/tr
checking for uname... /usr/bin/uname
checking for uniq... /usr/bin/uniq
checking for wc... /usr/bin/wc
checking for which... /usr/bin/which
checking for xargs... /usr/bin/xargs
checking for gawk... (cached) /usr/bin/awk
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... (cached) /usr/bin/egrep
checking for fgrep... (cached) /usr/bin/fgrep
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking for cygpath... no
checking for greadlink... no
checking for readlink... /usr/bin/readlink
checking for df... /bin/df
checking for SetFile... no
checking for cpio... /usr/bin/cpio
checking build system type... amd64-portbld-freebsd11.2
checking host system type... amd64-portbld-freebsd11.2
checking target system type... amd64-portbld-freebsd11.2
checking openjdk-build os-cpu... bsd-x86_64
checking openjdk-target os-cpu... bsd-x86_64
checking compilation type... native
checking for top-level directory... /wrkdirs/usr/ports/java/openjdk8/work/openjdk-jdk8u-jdk8u212-b04.1
checking for presence of closed sources... no
checking if closed source is suppressed (openjdk-only)... no
checking which variant of the JDK to build... normal
checking which interpreter of the JVM to build... template
checking which variants of the JVM to build... server
checking which debug level to use... release
checking for sysroot...
checking for toolchain path...
checking for extra path...
checking where to store configuration... in default location
checking what configuration name to use... bsd-x86_64-normal-server-release
checking for apt-get... no
checking for yum... no
checking for port... no
checking for pkgutil... no
checking for pkgadd... no
configure: Testing potential make at /usr/local/bin/gmake, found using user supplied MAKE=/usr/local/bin/gmake
configure: Using GNU make 3.81 (or later) at /usr/local/bin/gmake (version: GNU Make 4.2.1)
checking if find supports -delete... yes
checking for unzip... /usr/bin/unzip
checking for zip... /usr/local/bin/zip
checking for ldd... /usr/bin/ldd
checking for readelf... /usr/bin/readelf
checking for hg... no
checking for stat... /usr/bin/stat
checking for time... /usr/bin/time
checking pkg-config is at least version 0.9.0... yes
checking for 7z... no
checking for unzip... unzip
checking for wget... no
checking for lftp... no
checking for ftp... ftp
checking headful support... headless only
configure: Found potential Boot JDK using configure arguments
configure: Potential Boot JDK found at /usr/local/bootstrap-openjdk8 is incorrect JDK version (Error occurred during initialization of VM); ignoring
configure: (Your Boot JDK must be version 7 or 8)
configure: error: The path given by --with-boot-jdk does not contain a valid Boot JDK
configure exiting with result code 1
===>  Script "../../configure" failed unexpectedly.
Please report the problem to<EMAIL_ADDRESS>[maintainer] and attach the
"/wrkdirs/usr/ports/java/openjdk8/work/openjdk-jdk8u-jdk8u212-b04.1/common/autoconf/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1
Stop.
make: stopped in /usr/ports/java/openjdk8
=>> Cleaning up wrkdir
===>  Cleaning for openjdk8-<IP_ADDRESS>
build of java/openjdk8 | openjdk8-<IP_ADDRESS> ended at Fri May 31 12:09:57 PDT 2019
build time: 00:00:53
!!! build failure encountered !!!
At this point I restarted building my set with -i interactive, was able to cd to /usr/ports/java/openjdk8 and it passes configure and compiles no problem  For a work around to ublock the things requiring java, I did a make package.  It failed to copy.
===>  Building package for openjdk8-<IP_ADDRESS>
cp: /packages/All/openjdk8-<IP_ADDRESS>.txz: Read-only file system
So I just copied it from outside to the packages/All directory and was able to move on with my builds.
Initial guesses as to why it may not be able to run the bootstrap jdk for me were maybe the procfs and fdescfs mounts weren't set until it failed and dropped to interactive shell, but the fact that I can build in interactive but not in bulk seems like it is some kind of bug.
Also included is ports list I am building.
11-2x64.ports.txt

Full build log
build.log.txt

Yes, I still have the same issue, I have to run the batch in manual mode
whenever a java update comes up. I go to openjdk8 and make pkg (which does
not have a configure error) and manually copy out of jail. Then batch works
with everything else.
On Wed, Aug 28, 2019, 9:43 AM Bryan Drewery<EMAIL_ADDRESS>wrote:

Is this still a problem? At first glance it looks like a port problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freebsd/poudriere/issues/696?email_source=notifications&email_token=ADQ44GJGNMLBMYCSM56EG43QG2TKDA5CNFSM4HR7CRP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5LXWRQ#issuecomment-525826886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQ44GL5EJC5J5GZDLJJV2LQG2TKDANCNFSM4HR7CRPQ
.

I'm having the same issue.  Was there any update on poudriere's fix on this problem?

Still happening. For now the interactive workaround is working, I don't
know if there is a true fix yet.
On Thu, Dec 5, 2019, 1:14 AM skitchin<EMAIL_ADDRESS>wrote:

I'm having the same issue. Was there any update on poudriere's fix on this
problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freebsd/poudriere/issues/696?email_source=notifications&email_token=ADQ44GMVNXMBBZDETFGLK5DQXCZ7PA5CNFSM4HR7CRP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF74ADY#issuecomment-562020367,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ44GJWS4IJMQCYU6PAEJ3QXCZ7PANCNFSM4HR7CRPQ
.

Did you read my edited post in the thread about customized GENERIC?

I replied to email that (oddly) did not include that, sorry. I don't think
I am running a modified GENERIC file, but I could be on a custom kernel
still. Most of my FreeBSD installs have been stock kernels for some time
now, but this server may still be an exception to that. I will investigate
the kernel further and get back to you.
On Thu, Dec 5, 2019, 9:11 AM skitchin<EMAIL_ADDRESS>wrote:

Did you read my edited post in the thread about customized GENERIC?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freebsd/poudriere/issues/696?email_source=notifications&email_token=ADQ44GO6G3ZCLUDZ4GQARA3QXERZHA5CNFSM4HR7CRP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGBHMQY#issuecomment-562198083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ44GN27DDRLIJMYK4QWIDQXERZHANCNFSM4HR7CRPQ
.

We were running a GENERIC kernel so I don't know what was up but after we upgraded to FreeBSD 11.3 it builds without intervention now.


Generate and review validation reports: csa_omeka

Step 2: Generate reports [status: in progress --> ready for review]

[x] Generate validation reports (run validate_by_mapper DAG)
[x] Add a comment (in this issue) to the output URLs
[x] Download the validation reports locally; prepend the collection registry number to the filename
[x] Upload validation reports to the Rikolti Data Validation folder

Step 3: Review reports  [status: ready for review --> review in progress]

[x] Review sample collections validation reports; leave notes in the spreadsheet
[x] Quickly (and not very deeply) scan through other validation reports (to identify if any new metadata fields surface)
[ ] Synthesize notes at the mapper level
[ ] Share an update (and surface any anomalies) during a weekly check-in (Mondays at 3:00pm)

Step 4: Have data validation issues? Address & resolve validation issues (synthesized mapper-level):

[ ] Create a new issue (“Validation results: Rikolti mapper name“) and report/request CIC fixes & investigations. Assign to CIC.
[ ] Add a comment to link to the new “validation results” issue.
[ ] Add a “blocked/paused” label to this issue. Include a status note in this issue title (e,g., HOLD for CIC fixes; HOLD for code review; etc.)
[ ] Move this issue back to the “To Do” pile.

[Re-generate & re-review (repeat steps 2-3 above, as needed.]
Step 5: Have acceptable validation reports?

[ ] Move the valid (accepted) reports to the “VALID” folder in google drive.
[ ] Update the mapper progress spreadsheet; indicate that the mapper is accepted

@amywieliczka @barbarahui: We're trying to generate reports for the legacy csa_omeka mapper, but hit this error.
We think it's because CSA's endpoint is resulting in a 404: the issue is that CSA has moved off Omeka, and is now on Omeka S--they are on our ETL list. However, UCSB ADC is using the both the legacy csa_omeka mapper, as well as the replacement rikolti omeka.ucsb_adc mapper. We're curious how we should approach this: Should we take CSA off the legacy csa_omeka mapper in the registry? (Note that I was planning to use the associated registry mapper filter to generate the collections to ETL.) Are there other options?
Traceback (most recent call last):
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/airflow/decorators/base.py", line 220, in execute
    return_value = super().execute(context)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/airflow/operators/python.py", line 181, in execute
    return_value = self.execute_callable()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/airflow/operators/python.py", line 198, in execute_callable
    return self.python_callable(*self.op_args, **self.op_kwargs)
  File "/usr/local/airflow/dags/rikolti/dags/utils_by_mapper_type.py", line 33, in fetch_endpoint_task
    fetcher_job_result = fetch_endpoint(endpoint, limit, logger)
  File "/usr/local/airflow/dags/rikolti/metadata_fetcher/fetch_registry_collections.py", line 54, in fetch_endpoint
    fetch_result = lambda_function.fetch_collection(collection, None)
  File "/usr/local/airflow/dags/rikolti/metadata_fetcher/lambda_function.py", line 33, in fetch_collection
    fetcher = fetcher_class(payload)
  File "/usr/local/airflow/dags/rikolti/metadata_fetcher/fetchers/oai_fetcher.py", line 41, in __init__
    self.metadata_prefix = self.get_md_prefix_from_feed()
  File "/usr/local/airflow/dags/rikolti/metadata_fetcher/fetchers/oai_fetcher.py", line 49, in get_md_prefix_from_feed
    md_formats = [x for x in sickle_client.ListMetadataFormats()]
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/app.py", line 195, in ListMetadataFormats
    return self.iterator(self, params)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/iterator.py", line 135, in __init__
    super(OAIItemIterator, self).__init__(sickle, params, ignore_deleted)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/iterator.py", line 46, in __init__
    self._next_response()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/iterator.py", line 138, in _next_response
    super(OAIItemIterator, self)._next_response()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/iterator.py", line 84, in _next_response
    self.oai_response = self.sickle.harvest(**params)
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/sickle/app.py", line 130, in harvest
    http_response.raise_for_status()
  File "/usr/local/airflow/.local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://exhibits.sos.ca.gov/oai-pmh-repository/request?verb=ListMetadataFormats

[2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/232/validation/11-02-2023T20:50:33.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#232/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/3297/validation/11-02-2023T20:50:33.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#3297/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/5445/validation/11-02-2023T20:50:33.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#5445/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/8476/validation/11-02-2023T20:50:34.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#8476/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/17012/validation/11-02-2023T20:50:34.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#17012/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/18384/validation/11-02-2023T20:50:35.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#18384/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/19562/validation/11-02-2023T20:50:35.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#19562/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/20936/validation/11-02-2023T20:50:35.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#20936/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/24852/validation/11-02-2023T20:50:36.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#24852/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27277/validation/11-02-2023T20:50:36.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27277/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27278/validation/11-02-2023T20:50:37.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27278/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27279/validation/11-02-2023T20:50:37.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27279/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27280/validation/11-02-2023T20:50:37.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27280/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27281/validation/11-02-2023T20:50:38.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27281/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27282/validation/11-02-2023T20:50:39.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27282/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27283/validation/11-02-2023T20:50:39.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27283/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27284/validation/11-02-2023T20:50:40.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27284/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27285/validation/11-02-2023T20:50:40.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27285/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27317/validation/11-02-2023T20:50:41.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27317/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27319/validation/11-02-2023T20:50:41.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27319/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27398/validation/11-02-2023T20:50:41.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27398/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27399/validation/11-02-2023T20:50:42.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27399/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27400/validation/11-02-2023T20:50:42.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27400/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27401/validation/11-02-2023T20:50:43.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27401/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27402/validation/11-02-2023T20:50:43.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27402/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27560/validation/11-02-2023T20:50:43.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27560/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27561/validation/11-02-2023T20:50:44.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27561/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27562/validation/11-02-2023T20:50:44.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27562/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27563/validation/11-02-2023T20:50:45.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27563/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27567/validation/11-02-2023T20:50:45.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27567/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27568/validation/11-02-2023T20:50:45.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27568/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27604/validation/11-02-2023T20:50:46.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27604/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27664/validation/11-02-2023T20:50:46.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27664/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27665/validation/11-02-2023T20:50:47.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27665/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27835/validation/11-02-2023T20:50:47.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27835/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27836/validation/11-02-2023T20:50:48.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27836/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27837/validation/11-02-2023T20:50:48.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27837/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27847/validation/11-02-2023T20:50:49.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27847/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27848/validation/11-02-2023T20:50:49.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27848/ [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27849/validation/11-02-2023T20:50:50.csv [2023-11-02, 20:50:50 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27849/

Validation results posted here: https://github.com/ucldc/rikolti/issues/626

[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/232/vernacular_metadata_2024-02-01T17:21:31/mapped_metadata_2024-02-01T17:21:54/validation_2024-02-01T17:22:13.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#232/vernacular_metadata_2024-02-01T17:21:31/mapped_metadata_2024-02-01T17:21:54/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/3297/vernacular_metadata_2024-02-01T17:21:31/mapped_metadata_2024-02-01T17:21:54/validation_2024-02-01T17:22:13.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#3297/vernacular_metadata_2024-02-01T17:21:31/mapped_metadata_2024-02-01T17:21:54/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/5445/vernacular_metadata_2024-02-01T17:21:32/mapped_metadata_2024-02-01T17:21:55/validation_2024-02-01T17:22:13.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#5445/vernacular_metadata_2024-02-01T17:21:32/mapped_metadata_2024-02-01T17:21:55/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/8476/vernacular_metadata_2024-02-01T17:21:32/mapped_metadata_2024-02-01T17:21:55/validation_2024-02-01T17:22:14.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#8476/vernacular_metadata_2024-02-01T17:21:32/mapped_metadata_2024-02-01T17:21:55/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/17012/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:55/validation_2024-02-01T17:22:14.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#17012/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:55/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/18384/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:55/validation_2024-02-01T17:22:15.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#18384/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:55/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/19562/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:56/validation_2024-02-01T17:22:15.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#19562/vernacular_metadata_2024-02-01T17:21:33/mapped_metadata_2024-02-01T17:21:56/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/20936/vernacular_metadata_2024-02-01T17:21:34/mapped_metadata_2024-02-01T17:21:56/validation_2024-02-01T17:22:16.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#20936/vernacular_metadata_2024-02-01T17:21:34/mapped_metadata_2024-02-01T17:21:56/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/24852/vernacular_metadata_2024-02-01T17:21:34/mapped_metadata_2024-02-01T17:21:56/validation_2024-02-01T17:22:16.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#24852/vernacular_metadata_2024-02-01T17:21:34/mapped_metadata_2024-02-01T17:21:56/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27277/vernacular_metadata_2024-02-01T17:21:35/mapped_metadata_2024-02-01T17:21:57/validation_2024-02-01T17:22:17.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27277/vernacular_metadata_2024-02-01T17:21:35/mapped_metadata_2024-02-01T17:21:57/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27278/vernacular_metadata_2024-02-01T17:21:35/mapped_metadata_2024-02-01T17:21:57/validation_2024-02-01T17:22:17.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27278/vernacular_metadata_2024-02-01T17:21:35/mapped_metadata_2024-02-01T17:21:57/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27279/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:57/validation_2024-02-01T17:22:18.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27279/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:57/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27280/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:57/validation_2024-02-01T17:22:18.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27280/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:57/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27281/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:58/validation_2024-02-01T17:22:18.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27281/vernacular_metadata_2024-02-01T17:21:36/mapped_metadata_2024-02-01T17:21:58/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27282/vernacular_metadata_2024-02-01T17:21:37/mapped_metadata_2024-02-01T17:21:58/validation_2024-02-01T17:22:19.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27282/vernacular_metadata_2024-02-01T17:21:37/mapped_metadata_2024-02-01T17:21:58/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27283/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/validation_2024-02-01T17:22:19.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27283/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27284/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/validation_2024-02-01T17:22:19.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27284/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27285/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/validation_2024-02-01T17:22:20.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27285/vernacular_metadata_2024-02-01T17:21:38/mapped_metadata_2024-02-01T17:21:59/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27317/vernacular_metadata_2024-02-01T17:21:39/mapped_metadata_2024-02-01T17:21:59/validation_2024-02-01T17:22:20.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27317/vernacular_metadata_2024-02-01T17:21:39/mapped_metadata_2024-02-01T17:21:59/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27319/vernacular_metadata_2024-02-01T17:21:39/mapped_metadata_2024-02-01T17:22:00/validation_2024-02-01T17:22:21.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27319/vernacular_metadata_2024-02-01T17:21:39/mapped_metadata_2024-02-01T17:22:00/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27398/vernacular_metadata_2024-02-01T17:21:40/mapped_metadata_2024-02-01T17:22:00/validation_2024-02-01T17:22:21.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27398/vernacular_metadata_2024-02-01T17:21:40/mapped_metadata_2024-02-01T17:22:00/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27399/vernacular_metadata_2024-02-01T17:21:40/mapped_metadata_2024-02-01T17:22:01/validation_2024-02-01T17:22:22.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27399/vernacular_metadata_2024-02-01T17:21:40/mapped_metadata_2024-02-01T17:22:01/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27400/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:01/validation_2024-02-01T17:22:22.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27400/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:01/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27401/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:01/validation_2024-02-01T17:22:22.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27401/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:01/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27402/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:02/validation_2024-02-01T17:22:23.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27402/vernacular_metadata_2024-02-01T17:21:41/mapped_metadata_2024-02-01T17:22:02/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27560/vernacular_metadata_2024-02-01T17:21:42/mapped_metadata_2024-02-01T17:22:02/validation_2024-02-01T17:22:23.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27560/vernacular_metadata_2024-02-01T17:21:42/mapped_metadata_2024-02-01T17:22:02/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27561/vernacular_metadata_2024-02-01T17:21:42/mapped_metadata_2024-02-01T17:22:02/validation_2024-02-01T17:22:23.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27561/vernacular_metadata_2024-02-01T17:21:42/mapped_metadata_2024-02-01T17:22:02/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27562/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:02/validation_2024-02-01T17:22:24.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27562/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:02/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27563/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:03/validation_2024-02-01T17:22:24.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27563/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:03/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27567/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:03/validation_2024-02-01T17:22:24.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27567/vernacular_metadata_2024-02-01T17:21:43/mapped_metadata_2024-02-01T17:22:03/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27568/vernacular_metadata_2024-02-01T17:21:44/mapped_metadata_2024-02-01T17:22:03/validation_2024-02-01T17:22:25.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27568/vernacular_metadata_2024-02-01T17:21:44/mapped_metadata_2024-02-01T17:22:03/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27604/vernacular_metadata_2024-02-01T17:21:44/mapped_metadata_2024-02-01T17:22:04/validation_2024-02-01T17:22:25.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27604/vernacular_metadata_2024-02-01T17:21:44/mapped_metadata_2024-02-01T17:22:04/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27664/vernacular_metadata_2024-02-01T17:21:45/mapped_metadata_2024-02-01T17:22:04/validation_2024-02-01T17:22:26.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27664/vernacular_metadata_2024-02-01T17:21:45/mapped_metadata_2024-02-01T17:22:04/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27665/vernacular_metadata_2024-02-01T17:21:45/mapped_metadata_2024-02-01T17:22:05/validation_2024-02-01T17:22:26.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27665/vernacular_metadata_2024-02-01T17:21:45/mapped_metadata_2024-02-01T17:22:05/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27835/vernacular_metadata_2024-02-01T17:21:46/mapped_metadata_2024-02-01T17:22:05/validation_2024-02-01T17:22:27.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27835/vernacular_metadata_2024-02-01T17:21:46/mapped_metadata_2024-02-01T17:22:05/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27836/vernacular_metadata_2024-02-01T17:21:46/mapped_metadata_2024-02-01T17:22:05/validation_2024-02-01T17:22:27.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27836/vernacular_metadata_2024-02-01T17:21:46/mapped_metadata_2024-02-01T17:22:05/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27837/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:05/validation_2024-02-01T17:22:27.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27837/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:05/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27847/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:06/validation_2024-02-01T17:22:28.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27847/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:06/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27848/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:06/validation_2024-02-01T17:22:28.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27848/vernacular_metadata_2024-02-01T17:21:47/mapped_metadata_2024-02-01T17:22:06/data/
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27849/vernacular_metadata_2024-02-01T17:21:48/mapped_metadata_2024-02-01T17:22:06/validation_2024-02-01T17:22:29.csv
[2024-02-01, 17:22:29 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27849/vernacular_metadata_2024-02-01T17:21:48/mapped_metadata_2024-02-01T17:22:06/data/

Accepted on 2024, Feb 2!


Unicode Pokémon nicknames are not appearing

See the following example replay.

At turn 2, the Fletchling should be named 焼き鳥.
At turn 11, the Pawniard should be named クイーン.

Both of them appear as though they have no nickname. Other Pokémon use only characters in the standard ASCII range, and their names display like normal.

This is a name validator thing that is server-specific based on how we parse usernames, since Pokemon nicknames have the same constraints.
Tagging @Zarel since he built that and I'm unsure whether or not it actually needs fixing.

Katakana is valid in Pokemon nicknames, so that certainly is a bug

Certain Unicode ranges can probably be easily allowed, however the issue is deeper than that.
I would say we may reserve our right to filter nicknames. We can't even have every English character though: commas are forbidden for protocol safety...
Unless we use some sort of escaping?
What troubles me a bit is that the language of nicknames may influence the perception that a player has about their opponent, and thus have a psychological competitive value.

The problem itself can only be updated by Zarel because it relies on server-specific functions.
Validator#validateSet uses Config.namefilter as its nickname filter (which is also used to validate PS usernames) if it exists. It varies between servers and is not enabled by default.

namefilter probably shouldn't be shared between Pokémon and user names.

It varies between servers and is not enabled by default.

If it's a setting, that explains why I seem to remember these names being usable some time ago (probably a couple of months up to half a year—haven't played in a while).
Of course, there's nothing wrong with filtering nicknames (you always need to get rid of trailing spaces or possible exploits such as Zargo-style glitch text), but of course it'd be nice for non-English players to be able to use their own script for their Pokémon names.

Trivia: Zarel's own teams use Japanese nicknames

If it's a setting, that explains why I seem to remember these names being usable some time ago (probably a couple of months up to half a year—haven't played in a while).

When the Pokemon Showdown hard drive crashed a few months back, we lost the name filter, so we had to rebuild one from scratch as fast as possible to prevent usernames from using gimmicky characters like the Cyrillic A and Unicode control characters. The fastest way to do this was to write the name filter to block all characters but a select few.

de9c3847fd88e14284e53f286dd5cfc796ef6691 removes the namefilter from Pokemon names.

It had already been fixed for a few weeks, I just left it uncommitted for a while since I was waffling on implementation details.

Well, yeah. But now we have a commit to prove it's been done :3


Fix integration test

Test could sometimes fail if the server fatal'd for any reason (usually due to working with tests) and the defer would not fire to clean up directories.

+1


Add Secondary Water Systems from DWR

Summary

Proposed Readable Name: Utah Secondary Water Systems
Proposed Internal Dataset Name: SecondaryWaterSystems
Proposed External Dataset Name: Secondary_Water_Systems
Proposed Data Category: Water
Data Description: Service areas of secondary water suppliers
Source Agency/Entity: DWR (Water Resources)
Contact: Adam Clark
Update Frequency: Quarterly

AGOL service that DWR asked to be included in the SGID. Service represents non-potable water suppliers for lawn and garden use.
https://utahdnr.maps.arcgis.com/home/item.html?id=6d75d02478a74e128ac726890a93dff8
The data should be available in
1 Check [x] all the areas where you expect the data to show up.

[ ] Internal SGID
[ ] Open SGID
[x] ArcGIS Online
[x] Open Data

The data is of high quality

[ ] Sweeper checks have run and passed (@ZachBeck  on 2022/00/00)
[x] The minimum requirements for metadata are populated (@ZachBeck on 2022/11/22)
[x] The data complies with our domain rules (@ZachBeck on 2022/11/22)

Where is the data source
Choose one.

[ ] Internal SGID
[x] Farm from AGOL (https://utahdnr.maps.arcgis.com/home/item.html?id=6d75d02478a74e128ac726890a93dff8)

Action items

Assign a person who should complete the task by replacing name with their github @name.
Check [x] the box when the task is completed and add the date of completion.
~Strike~ out all items that do not apply.

~- [ ] Add data to the Internal SGID (, completed: 2022/00/00)~
~- [ ] Configure forklift for Farm from AGOL (, completed: 2022/00/00)~

[ ] Update relevant gis.utah.gov data pages (@ZachBeck, completed: 2022/00/00)
[x] Add a Stewardship record (@ZachBeck, completed: 2022/12/13)
~- [ ] Complete a SGID.META.AGOLItems record (@ZachBeck, completed: 2022/00/00)~
~- [ ] Complete an AGOLItems_shelved record for any static or shelved item (name, completed: 2022/00/00)~

:robot: Automation validation

Assign yourself or someone to check the item by replacing name with their github @name.
Check [x] the box and add the date of verification 2020/01/01 when the task is verified.
~Strike~ out all items that do not apply.

~- [ ] Open SGID via cloudb (on 2022/00/00)~
~- [ ] ArcGIS Online via forklift (@stdavis on 2022/00/00)~

[ ] Auditor ran successfully (@jacobdadams on 2022/00/00)
[x] Open Data (@stdavis on 2022/12/09)
[ ] gis.utah.gov data pages (@steveoh on 2022/00/00)
[x] sgid-index (@steveoh on 2022/12/19)

Notification

[x] Twitter (@steveoh)

Group Task Assignments

Check [x] the box when you have assigned all the tasks relevant to your group.

[ ] Data Team (@gregbunce)
[x] Dev Team (@steveoh)
[ ] Cadastre Team (@rkelson)

Ok, I think open data / agol will be fine.

conductor results for tasks - 215

check
status

@ZachBeck has completed 2 out of 5 tasks
:no_entry:

@steveoh has completed 0 out of 5 tasks
:no_entry:

@stdavis has completed 0 out of 1 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for tasks - 215

check
status

@ZachBeck has completed 2 out of 6 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

@steveoh has completed 1 out of 5 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for water.SecondaryWaterSystems

check
status

internal sgid
:no_entry:

meta table

- item id
:no_entry:

- item name
:no_entry:

- geometry type
:no_entry:

stewardship

- Website URL
:no_entry:

- Endpoint
:no_entry:

- Data Type
:no_entry:

- Description
:+1:

- Data Source
:+1:

conductor results for tasks - 215

check
status

@ZachBeck has completed 2 out of 6 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

stdavis has completed 1 out of 1 tasks
:+1:

@steveoh has completed 1 out of 4 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for water.SecondaryWaterSystems

check
status

internal sgid
:no_entry:

meta table

- item id
:no_entry:

- item name
:no_entry:

- geometry type
:no_entry:

stewardship

- Website URL
:no_entry:

- Endpoint
:no_entry:

- Data Type
:no_entry:

- Description
:+1:

- Data Source
:+1:

conductor results for tasks - 215

check
status

@ZachBeck has completed 3 out of 5 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

stdavis has completed 1 out of 1 tasks
:+1:

@steveoh has completed 1 out of 4 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for water.SecondaryWaterSystems

check
status

internal sgid
:no_entry:

meta table

- item id
:no_entry:

- item name
:no_entry:

- geometry type
:no_entry:

stewardship

- Description
:+1:

- Data Source
:+1:

- Website URL
:+1:

- Endpoint
:+1:

- Data Type
:+1:

conductor results for tasks - 215

check
status

@ZachBeck has completed 3 out of 5 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

stdavis has completed 1 out of 1 tasks
:+1:

@steveoh has completed 3 out of 4 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for water.SecondaryWaterSystems

check
status

internal sgid
:no_entry:

meta table

- item id
:no_entry:

- item name
:no_entry:

- geometry type
:no_entry:

stewardship

- Description
:+1:

- Data Source
:+1:

- Website URL
:+1:

- Endpoint
:+1:

- Data Type
:+1:

conductor results for tasks - 215

check
status

@ZachBeck has completed 3 out of 5 tasks
:no_entry:

@jacobdadams has completed 0 out of 1 tasks
:no_entry:

stdavis has completed 1 out of 1 tasks
:+1:

@steveoh has completed 3 out of 4 tasks
:no_entry:

@gregbunce has completed 0 out of 1 tasks
:no_entry:

@rkelson has completed 0 out of 1 tasks
:no_entry:

conductor results for water.SecondaryWaterSystems

check
status

internal sgid
:no_entry:

meta table

- item id
:no_entry:

- item name
:no_entry:

- geometry type
:no_entry:

stewardship

- Description
:+1:

- Data Source
:+1:

- Website URL
:+1:

- Endpoint
:+1:

- Data Type
:+1:


Unit-Testable components

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
Hey together,
this feature request is more a container of smaller improvements in regards to testability. Short background, I am Steven and core contributor to bUnit. I saw that you use bUnit internally to test your components. Lovely to see and great work!
Imagine a user unit testing a component which consists out of your beautiful components. He is faced with some pitfalls.

Is there JavaScript involved? If so, the user has to mock it or set the mock-behaviour to loose. In any case it needs manual intervention. This mainly concerns the chart because it is based on chart.js. But also "common" components like the BitDropDown uses JS calls
How can I trigger / click a button in bUnit? BitButton for example can have multiple representations. Either an <a href> or <button>.

Describe the solution you'd like
Multiple things can help here. Maybe a special part in your documentation highlighting how to trigger certain behaviour with for example bUnit. That should cover a lot of cases.
For the JS-Interop stuff you could offer an baseclass which does already a lot of the mocking:
public abstract class BitUITestContext : TestContext
{
}

The main part here would be to make it convenient for all users independent if they use xUnit, nUnit or MSTest.
Telerik does something similar. I just can't find their base class.
Anyway the idea is to guide the user how to unit test component which do rely on your components.
Additional context
If you need any help bUnit-wise let me know.

@linkdotnet thanks for submitting this issue
It is an interesting suggestion and I think we can discuss it with our team to have it designed and implemented.
we will announce the plans or feel free to submit a PR of your own solution.

Sure thing. If you need anything, just let me know ;)

Maybe a few ideas from my side. AntBlazor has a similiar way of dealing with things. They internally have their own AntDesignTestBase. For BitPlatform "we" could introduce a similiar approach. For example a dedicated nuget package for bUnit which makes testing easier. I am not aware of any other unit testing framework for Blazor, so that should keep maintenance cost low.
Additionally one could introduce extension methods for clicking a button for example:
public class BitButtonTestExtensions
{
    public static void ClickButton(this IRenderFragment<BitButton> button)
    {
        if (button.Href is not null)
            button.Click("a");
        else
            button.Click("button");
    }
}

The user can then simply use the extensions:
// By inheriting from BitPlatformTestContext all JS is already either setup or JSRuntime is set to Loose
public class MyNiceTest : BitPlatformTestContext
{
    [Fact]
    public void ShouldDoAwesomeStuff()
    {
        var cut = RenderComponent<MyCustomComponent>();

        // Now we can use the extension method
        cut.FindComponent<BitButton>().ClickButton();

        // Assert
    }
}

Paired with a nice documentation that should cover a lot of use cases. Keep in mind that a simple documentation might be good enough for starters and if you or we from bUnit see users often time running into trouble those helpers might be useful.
Let me know your thoughts.

@linkdotnet sry for late response, we are getting ready for a new prerelease version.
interesting ideas you've got there. I'll jump in after we are done here.

Nah no worries. Take your time. I was just throwing ideas around ;)

@linkdotnet

about the dedicated nuget package for bUnit which makes testing easier, could you please explain it a bit?
the base test class is a great idea, and it would be even greater if you could submit a PR for it 😊
the extension method is also a good idea, lets go for it 😊

Sure. Before I give explanation about the nuget package.
Base class VS Extension method
After thinking about this, I would favour an extension method over a subclass. Subclass would restrict options for the user, he can't use other base classes. Also the usage is super trivial:
using Bit.BlazorUI;

public class MyComponentTest : TestContext
{
    public MyComponentTest()
    {
        // Maybe a better name, but you get the idea
        // This method would setup all JS
        Services.AddBitPlatformUi();
    }

    [Fact]
    public void TestWithABitPlatformButton();
    {
        var cut = RenderComponent<MyComponent>();

        // Click is an extension from you... I'll show later how it works
        // This might make it easier for users, so they don't have to know if
        // the button is <button> or <a href>
        cut.FindComponent<BitButton>().Click();
    }
}

Extension:
namespace Bit.BlazorUI;

public static class RenderFragmentBaseExtensions
{
    public static void Click(this IRenderFragmentBase<BitButton> button)
    {
        ArgumentNullException.ThrowIfNull(button);

        // Only click if we don't have Href as the <a> element has no onclick event
        if (string.IsNullOrEmpty(button.Instance.Href))
            button.Find("button").Click();

    }
}

Nuget
Right, so there are two ways giving the user the abilities described above:

Documentation - so he can copy & paste
Having a separate nuget package the user can include

Of course you don't want to couple your production code with bUnit. a) you don't need it and b) you don't want to ship bUnit as dependent package to your customers in production.
That is why a separate package is necessary.
So having another project inside your solution which then will be published to nuget.

@linkdotnet tnx a lot for the explanation.
I do agree with the extension method approach, but adding a new project and configuring the pipeline to publish its nuget package and also the documentation is a bit too much for us atm.
let me discuss it with our team and come back to you.
if you have any suggestions about implementing this approach, just let me know.

@linkdotnet
tnx again for your contributions, and sorry for the late response. we are super busy atm 😁😭
I discussed these approaches with the team and we believe that currently, we don't have enough time/resources to handle these issues, and also our approach in these situation is using custom Code Analyzers to warn developers about their mistakes/issues which we have already done with other problems (like the async void cases).
in the end, we would really appreciate it if you could take care of the desired solution(s) for these problems and let us know if you need any help to implement them.
I'm going to move this issue to the V-Next milestone since we don't have time to plan them for the team in the near future.
👌✌

Don't worry. Nothing urgent and totally understandable.
Otherwise we can also wait until the first users report issues and check their feedback.

not planned yet


First Capstone Project

In this project you can find:

Mobile version is all functional.
Desktop version fully functional.
Linters, and License functional.

This is how it seems in my Live Server, I don't know why isn't updating in my deploy the changes

Hi @usorfaitheloho I fix it, please check if the margin between each card is right now, thanks you.
https://saveryiv.github.io/First-Capstone-Project/

Hello @SaveryIV, the margin looks good. You can go ahead with your submission.
Weldone 👍


Added a sample using JSZip

Adds a new sample that shows how to create a UXP plugin that uses JSZip alongside Photoshop. Incorporates all features mentioned in issue #15
Features:

Open all images in an imported zip file
Export all artboards in the current document to a zip file
Allow a zip file to be created with selected files

One thing I'd suggest adding is just a little notice when exporting the artboards is complete -- just so the user is aware the process has actually finished.


routes with jade partials

the jade partials only renders once, and kind of catches itself and renders the same every time even though a new file is rendered ,,. at least for me,. shifted to angular router and every thing started working

I'm not sure what your question/issue is.

http://bit.ly/UIR-SOF


use rector/rector:dev-main again

It seems the composer.json using tagged version, it should use dev-main again to have faster feedback, eg after crucial PR:

https://github.com/rectorphp/rector-src/pull/3356

:+1:


Author auto-hide replies with specific tags or words/phrases

Describe the Feature
As the author of a root post, I can hide specific replies for everyone ("Hiding Replies" from this blog entry). I'd like to be able to automatically hide replies that match specific words/phrases/tags. I'm imagining similar ergonomics to how Muted Words & Tags work for affecting my own experience... just applied to replies, and with the strength of the author-hidden replies feature.
Attachments
No response
Describe Alternatives
No response
Additional Context
No response

The core aspect of this (automatically hiding replies for everyone based on preset criteria from a root post's author) could also be used for handling suggestions like John Scalzi mentioned recently. Instead of a mute terms/tags list, it would be an account list.

The one thing Threads has that I wish we had here is the "restrict" function, in which people can still read what you post, but all their comments are in a silo where no one else sees them. It's brilliant for the "you aren't evil but you sure are exhausting" category of person who exists online.


branch-DG

Codecov Report

Merging #36 (10c89be) into master (d899388) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #36   +/-   ##
=========================================
  Coverage     65.99%   65.99%
  Complexity      411      411
=========================================
  Files            77       77
  Lines          1394     1394
  Branches        138      138
=========================================
  Hits            920      920
  Misses          438      438
  Partials         36       36

Impacted Files
Coverage Δ

src/main/java/seedu/address/Main.java
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


[VS Code] Starting collaboration session: The type initializer for 'Microsoft.Cascade.Agent.AuthenticationService' threw an exception.

Error:
Starting collaboration session: The type initializer for 'Microsoft.Cascade.Agent.AuthenticationService' threw an exception.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.540

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.36.1

platformName
MacOS

platformVersion
18.6.0

Your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

Resolving as a duplicate of #2468  Please attach the logs to that bug if you can get them.


Bump version to 1.4.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

There seems an API change between CLI11 1.9 and 2.0, but I can't find it in https://github.com/CLIUtils/CLI11/blob/main/CHANGELOG.md#version-20-simplification .

There seems an API change between CLI11 1.9 and 2.0, but I can't find it in https://github.com/CLIUtils/CLI11/blob/main/CHANGELOG.md#version-20-simplification .

Actually there is, the relevant change is:

The final "defaulted" bool has been removed, use ->capture_default_str() instead. Use app.option_defaults()->always_capture_default() to set this for all future options. https://github.com/CLIUtils/CLI11/pull/597

There seems an API change between CLI11 1.9 and 2.0, but I can't find it in https://github.com/CLIUtils/CLI11/blob/main/CHANGELOG.md#version-20-simplification .

Actually there is, the relevant change is:

The final "defaulted" bool has been removed, use ->capture_default_str() instead. Use app.option_defaults()->always_capture_default() to set this for all future options. CLIUtils/CLI11#597

Upstream fix: https://github.com/gazebosim/gz-utils/pull/60 backported in this PR.