Core dump check failed

Hello, please tell me what could be the reason? I installed the firmware using ProgramESP32.bat and after rebooting the board in SerialMonitor it gives the following error:
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13964
load:0x40080400,len:3600
entry 0x400805f0
E (587) esp_core_dump_fl���h: Core dump data check failed:
Calculated checksum='de456912'
Image checksum='ffffffff'

I don't think that's a problem, from what I can gather it's normal since there is no core dump on your ESP32 (the program hasn't ever crashed, therefore there's no valid crash data in there). Have you used your ESP32 board for some other program before?
Does the board reboot continuously?

Thank you very much for your reply and for your excellent work on this program. After this error nothing happens, the board does not reboot. After pressing the reset button I noticed that the check engine briefly lights up and goes out, but nothing else happens. Unfortunately I didn't have the mcp2551 chip board available so I changed to a TJA1050 I2C chip, could this be the problem? Also I don't see bluetooth to connect to. The Esp32 board is in good working order, other programs with bluetooth operation were running on it. Can you please tell me, what should be the behavior of the tape recorder or the car when starting the board? I also tried to compile in Arduino IDE, but I get a lot of errors, one of them is in line 13 of A2DP.ino file : 'title_buffer' was not declared in this scope

Can you send a link to the exact type of ESP32 board you have? A detailed photo is fine too.
I tried all the boards I have around and couldn't replicate the issue, even tried fresh ESP32-WROOM modules straight from the tape and they seem fine. You can also show me the full output after running ProgramESP32.bat.
TJA1050 should work, but I have not tested it myself. Bluetooth only starts after ESP32 receives a message from the radio to the display, then prints a message "Bluetooth on, waiting for connection" (ignition is not necessary), afterwards the bluetooth is available to connect to. What is your vehicle, display and radio unit?
As for compilation, I think you're using an older version (1.x.x) of arduino IDE, update to something newer than 2.x and it should compile fine. While compilation will succeed, there's still an issue with the newest release of ESP32 arduino board files, CAN seems to crash very often with these, also the resulting file will not fit in memory unless you modify the ArduinoOTA library. I'd suggest downgrading to 2.0.17 version of the ESP32 board files for everything to work properly (don't forget to do what I have described in this section of readme after downgrading/upgrading the board files).

I've got the same board in my test setup and it works well, same serial chip and all.
Here are the settings.

Can you please tell me the versions of your libraries to compile?

ESP32-A2DP v1.8.3
arduino-audio-tools v0.9.8
esp32 board files v2.0.17
Also, I've got one thing for you to try, maybe erasing the entire flash before programming will work in your case. Use the attached batch file to program your board.
ProgramESP32_erase.zip

Super, thanks a lot, everything compiled perfectly now. However, the problem is still the same, no response. I assume I have wrong soldering, can you tell me if CAN High from TJA1051 is connected to Can high in OBD2 pad (pin 6) and CAN Low is connected to Can Low in OBD2 (pin 14)? When I press RESET on the board, what happens in the video, is it supposed to happen?
https://github.com/user-attachments/assets/5603b010-11f0-464a-976c-0c9c7da23fac

That's what it was all about! Thank you so much, everything works great. I didn't know Opel had a separate CAN line, I was using the standard obd2 pinout.


Carolyn java devs

Most of the changes on the older files like background.html are from the PRs on an older branch that were not reflecting on this new branch so I added them in.

Deployed!

Thank youuuu! This is a very cool feature. Just to check to make sure this is WAI, it seems like this is the logical pattern:

Click place1 and show it below map.
Click place2 and show it below map. Place1 is put below place2.
Click place3 and show it below place2 but above place1.

The third action seems a little strange to me, so I wanted to confirm that.

Feel free to chat DM me if this is an issue, and we can work through it together.

My mistake, this error is unrelated to the PR. Let's submit this and open issues for any bugs we find in the site. We can address those in our free time.


bump_release: always set push.default

We should set push.default regardless of whether push_url is set. If we don't, we get a warning message:
warning: push.default is unset; its implicit value has changed in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the traditional behavior, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.

Since Git 2.0, Git defaults to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)

LGTM


Allow to create Angle GRGlInterface from non UWP environment

Allow to create Angle GRGlInterface from non UWP environment (WPF for an instance) from a new non deprecated Create() API. Another option will be making AngleLoader public to use a CreateAngle (GRGlGetProcedureAddressDelegate get).
Now we are using a deprecated method, but I want to be sure that in the next releases we will be able to init Angle without reflection :) :
GrContext = GRContext.CreateGl(GRGlInterface.CreateNativeAngleInterface());

What I want:
GrContext = GRContext.CreateAngle();

basic Create() call will make an openGL GRContext.

@Mikolaytis Have you tested this? I this the only change needed? All the load library and get procs working as expected?
Not sure why I made that private... Might have been a lack of testing I think.

Yes, I've tested this. It's the only change needed for my case. Everything working as expected. 😀


Question for gitness and drone framework

I found that after upgrading from drone code to gitness, the framework changed a lot.
There used to be a core directory responsible for defining the interfaces of all modules, and each module was organized using dependency inversion. This is the old code: https://github.com/harness/gitness/tree/drone
In the latest code of gitness, each module does not define an interface, and there are often various structure pointers during dependency injection.
I would like to ask, what are the advantages of such a structure, and what considerations did it evolve into?

Could you share your thoughts?
@johannesHarness @tan-nhu @cjlee01


Add correct oauth2 support

At present, using a hack to get oauth2 token. Need to implement legitimate support
https://godoc.org/golang.org/x/oauth2
https://github.com/golang/oauth2

After reviewing the official OAuth2 documentation, this requires a server setup to allow gathering information from a user's profile.


Multi tenancy

Did you think about implementing multi tenancy right into DAVe or is this not a topic so far?
Enabling multi tenancy would also be possible of course deploying all modules in different K8s namespaces or even different clusters.
Just wanted to know how you think about this?

Well the city of munich doesnt need it right now, but we thought about it a bit and identified these high-level tasks to implement muliti-tenancy in DAVe:

Save configuration of tenant data in a separate file / tenant database table

Read out tenant data and configure data sources and connections

Enrich all requests with tenant information

Route each DB operation via the tenant using the correct connection (e.g. with spring's AbstractRoutingDataSource)

Configuration UI for tenant data (e.g. DB connections, client-specific settings (e.g. city districts), user-to-tenant assignment, etc)

Extend authentication by tenant id

Consider tenant-specific settings for display in the frontend and calculations in the backend

@armintsys Since we as the city of Munich have no need for this, we will not implement it, but we are open to contributions

@klml thats fine, there are different solutions possible which do not require code changes. I think one of them could be enough for now. Thanks for help anyways.


feat: Add minimum permissions to workflows

Adding minimum permissions to workflows is important to protect your repository against supply-chain attacks. GitHub, by default, gives higher permissions to workflows but recommends adjusting them to minimum permissions as necessary. I see build.yml seems to be used to check if build is fine, testing and fuzzing. Thus, build.yml does not need high permissions to perform it's work. From what I see, setting contents: read permission would be enough. If you'd like I can open a PR to make the changes!
This setting is considered good-practice and recommended by GitHub, as mentioned, but also by other security tools, such as Scorecards and StepSecurity.
Additional Context
I'm Gabriela and I work on behalf of Google and the OpenSSF suggesting supply-chain security changes :)

Hi! Friendly ping here. This issue has been idle for quite some time. Do you plan on considering these changes? If yes, please let me know! Otherwise I will wait up to 2 more months to close the issue. Thanks!

Hey! Just to let you know I'm closing this issue. If you want to consider this change, please reopen :)


asterisk-amr

Added asterisk-amr

ims cellphones uses amr-wb (not sure they can fall back to "simple" amr)
rtpengine has support for amr and amr-wb (so, we can transcode in rtpengine and have g711 to/from FreeSwitch/Asterisk)
also, freeswitch can be compiled with amr and amr-wb (I have patches for it),even latest freeswitch
do we need asterisk on board? (just asking, I'm not against)


Add a generator for components

generates all the required files in the right places
does not generate JS file as not all components need them
will appear in the component guide without changes but test should fail

https://trello.com/c/57dzR66x/73-write-a-component-generator-in-the-gem

Is there a way to test this against the dummy app?


Add permission to hide holograms

if you want to hide a hologram by default you'll need to execute
/holo edit holoname visibleByDefault false
then you can set fancyholograms.holo.holoname to true to allow the player to see the holo
I already tested the code


boost-python failed to compile

Building boost-python[core,python2,python3]:x64-windows-static-md...
warning: -- Using community triplet x64-windows-static-md. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: D:\Projects\vcpkg\triplets\community\x64-windows-static-md.cmake
-- Using cached boostorg-python-boost-1.82.0.tar.gz.
-- Extracting source D:/Projects/vcpkg/downloads/boostorg-python-boost-1.82.0.tar.gz
-- Using source at D:/Projects/vcpkg/buildtrees/boost-python/src/ost-1.82.0-316083640d
CMake Error at ports/boost-python/portfile.cmake:11 (include):
include could not find requested file:
D:/Projects/vcpkg/installed/x64-windows/share/boost-build/boost-modular-build.cmake

Call Stack (most recent call first):
scripts/ports.cmake:147 (include)
error: building boost-python:x64-windows-static-md failed with: BUILD_FAILED
Elapsed time to handle boost-python:x64-windows-static-md: 445 ms
internal error: D:\a_work\1\s\src\vcpkg\commands.build.cpp(1511): Value was null
Please open an issue at https://github.com/microsoft/vcpkg/issues/new?template=other-type-of-bug-report.md&labels=category:vcpkg-bug with detailed steps to reproduce the problem.
NativeCommandExitException: Program "vcpkg.exe" ended with non-zero exit code: 1.

@kxgy, Thanks for posting this issue, I can not repo this issue:
Could you please confirm if exist this file?

Ping @kxgy for response.


Mobile publish fixes

Closes Mobile publish flow (layout)#1075.
Changes proposed in this PR:

check all publish screens on mobile
adapt problematic component layouts as needed (not really needed, everything looks ok)
check all form navigation for user surprises (e.g. using Continue scrolls to top of viewport) - didn't find any issue on the forms

would suggest looking at the NFT & Datatoken form fields which to me look like they should be stacked by default and then get left/right placement as viewport gets bigger.

Correction for mobile merged to PR

@kremalicious thank you, you're right. Fixed in the last commits

when switching between Metadata & Access, the Data NFT and Datatoken fields should look the same. Right now the NFT is stacked, but Datatoken is still left/right placement on mobile. Although Datatoken field kinda fits better, being consistent is more important here.
Also, would just left-align image/text on mobile, centering that NFT image looks unbalanced when input label above and content below is left-aligned.

Found 2 more things we can improve:
Using really narrow viewport here but still seems 2 fee fields at bottom would still fit beside each other, we could also make them slightly smaller by default to gain a bit more space. On same screen the tokens in the pool box are misaligned, should both be left aligned when they are stacked like that, otherwise looks chaotic and unbalanced in current state.

On submission screen, number & title should always be on one line, and the transaction label should be then in new line, left aligned with the edge of the text beneath it

pricing and submit tabs fixed for small viewports 🤙🏽


[macOS] Add Xcode 13.4 to macOS-12 image

Description
Xcode 13.4 RC has been released.
Related issue:
n\a
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos12


Documentation typos

Hi Robert. Awesome looking package, and I can't wait to dive into it.
The documentation has a bunch of small typos in it. Would you be open to having someone help fix those or would you prefer me to list them all in this issue?

If you can list them. I have a free gitbook account and can't add anyone else to it!
Thanks for pointing any out!

Will update this on next release. Thanks.

Updated


[Docs]: Guide for OAuth Client Credentials workflow

@rohan-arthur - I've added the content to Gitbook. Could you please review the changes?

We will be picking this up as part of top how to guides project


Add a sound for urgent notifications

Related to https://github.com/elementary/notifications/pull/85
Source: https://notificationsounds.com/standard-ringtones/answer-quickly-45

Sorry for taking so long to review! The sound is good for me, but the name doesn't appear to be in the fd.o draft spec: http://0pointer.de/public/sound-naming-spec.html
It looks like the fd.o sound them uses dialog-warning and symlinks dialog-error to it. We should probably do the same

It looks like according to their license they also require attribution in the README

merged with changes in #12


Add note about minSdk 21 (AndroidX)

Couldn't find a proper (blog) announcement but there is a big warning on the website:

+ PRs started failing to compile: https://github.com/TWiStErRob/android-lint-examples/pull/67
Execution failed for task '...:processDebugMainManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 14 cannot be smaller than version 21 declared in library [androidx.appcompat:appcompat-resources:1.7.0] /home/runner/.gradle/caches/8.8-rc-2/transforms/bd5f4f58eb143a6fc57ebc3ec976ba60/transformed/appcompat-resources-1.7.0/AndroidManifest.xml as the library might be using APIs not available in 14
  	Suggestion: use a compatible library with a minSdk of at most 14,
  		or increase this project's minSdk version to at least 21,
  		or use tools:overrideLibrary="androidx.appcompat.resources" to force usage (may lead to runtime failures)

Couldn't find a proper (blog) announcement but there is a big warning on the website:

Apparently there hasn't been a proper announcement (nor is this mentioned in the changelogs of things like AppCompat):
https://stackoverflow.com/questions/78586493/does-appcompat-now-require-minsdkversion-21

Thank you!


filter out unhandled account type

Description
This fixed issue: https://github.com/BitBotFactory/poloniexlendingbot/issues/459
TESTING STAGE
Local bot works after implementing this change.
Types of changes

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have read CONTRIBUTING.md
[X] I fully understand Github Flow.
[X] My code adheres to the code style of this project.
[ ] I have updated the documentation in /docs if I have changed the config, arguments, logic in how the bot works, or anything that understandably needs a documentation change.
[ ] I have updated the config file accordingly if my change requires a new configuration setting or changes an existing one.
[ ] I have tested the bot with no issues for 24 continuous hours. If issues were experienced, they have been patched and tested again.

Wouldn't it make this change more functional if this account type would be added somehow to the results?
https://github.com/BitBotFactory/poloniexlendingbot/blob/04fe799f42bcb7c8db8f4eedaf439b8fd77f95fd/modules/Bitfinex2Poloniex.py#L100

Don't think that by itself would make it more functional. From what I can see this is a codebase following common python patterns, making things more functional can often become harder to understand, i.e.: don't have a 'filtered_response' variable, just pass the list comprehension directly as a parameter.
Something that might be more elegant is creating an excluded set and filtering the response against it.

On Aug 15, 2017, at 5:58 PM, Raanan<EMAIL_ADDRESS>wrote:
Wouldn't it make this change more functional if this account type would be added somehow to the results?
https://github.com/BitBotFactory/poloniexlendingbot/blob/04fe799f42bcb7c8db8f4eedaf439b8fd77f95fd/modules/Bitfinex2Poloniex.py#L100
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Compatibility with PyTorch when the distributed package is available

🐛 Bug
From v1.7.0 Lightning is not compatible anymore with PyTorch when the distributed package is not available.
For example, commits 35841613c and c600f987c import from torch.distributed without checking if torch.distributed.is_available().
Is this a bug or the intended behavior?
To Reproduce
Install PyTorch from source setting USE_DISTRIBUTED=0 then install pytorch-lightning>=1.7.0.
$ python -c "import pytorch_lightning as plt"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/x86_64/pytorch-lightning/1.7.2/lib/python3.9/site-packages/pytorch_lightning/__init__.py", line 34, in <module>
    from pytorch_lightning.callbacks import Callback  # noqa: E402
  File "/x86_64/pytorch-lightning/1.7.2/lib/python3.9/site-packages/pytorch_lightning/callbacks/__init__.py", line 14, in <module>
    from pytorch_lightning.callbacks.callback import Callback
  File "/x86_64/pytorch-lightning/1.7.2/lib/python3.9/site-packages/pytorch_lightning/callbacks/callback.py", line 25, in <module>
    from pytorch_lightning.utilities.types import STEP_OUTPUT
  File "/x86_64/pytorch-lightning/1.7.2/lib/python3.9/site-packages/pytorch_lightning/utilities/types.py", line 26, in <module>
    from torch._C._distributed_c10d import ProcessGroup
ModuleNotFoundError: No module named 'torch._C._distributed_c10d'; 'torch._C' is not a package

Expected behavior
Successfully import pytorch-lightning.
Environment

Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow): None
PyTorch Lightning Version (e.g., 1.5.0): 1.7.2
Lightning App Version (e.g., 0.5.2):
PyTorch Version (e.g., 1.10): 1.12
Python version (e.g., 3.9): 3.9.7
OS (e.g., Linux): Linux
CUDA/cuDNN version: 11.6
GPU models and configuration:
How you installed PyTorch (conda, pip, source): SOURCE
If compiling from source, the output of torch.__config__.show():
PyTorch built with:

GCC 11.2
C++ Version: 201402
Intel(R) Math Kernel Library Version 2020.0.1 Product Build 20200208 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.6.0 (Git Hash N/A)
OpenMP 201511 (a.k.a. OpenMP 4.5)
LAPACK is enabled (usually provided by MKL)
NNPACK is enabled
CPU capability usage: AVX2
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.6, CUDNN_VERSION=8.4.1, CXX_COMPILER=/mpcdf/soft/SLE_15/packages/x86_64/gcc/11.2.0/bin/g++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.12.0, USE_CUDA=1, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=OFF, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF,

Running environment of LightningApp (e.g. local, cloud):
Any other relevant information:

Sorry for the inconvenience. Yes, this is a bug.
Would you like to open a PR with a fix?

Yes, I'll open a PR in the next days.


Changing alphaMode to 'blend' causes rendering problem since v0.9.6

Try changing the version in the example to v0.9.5, where the model is rendered correctly.
Example: https://codesandbox.io/s/pixi3d-097-3lb69
v0.9.5

v0.9.7

Thanks, I'll take a look.

For now you can solve it with:
goalkeeper.meshes[0].material.alphaMode = "blend"
goalkeeper.meshes[0].material.state.depthMask = true

I did some changes in develop branch, please let me know if this fixes your issue. You can clone the repo, then:
npm install
npm run build

You will find output in dist folder.

That fixed my issue. Thanks.


Default config not load

Hello,
still have typo mistake in /image_collage_twig_extension.php
$this->loadParamsFromConfig([
            'column' => 'column',
            'border_size' => 'borderSize',
            'image_width' => 'width'
        ], 'plugins.image_collage.');

plugins.image_collage need to be written with a dash plugins.image**-**collage

Fixed. Thank


Fix error logging

Coverage decreased (-0.3%) to 91.097% when pulling 886607bd60ab61ef3a87a36a827cf62d1e416785 on mttrbrts:mr-fix-error-logging into da606ecce49024615508242372b3130d1701ac0c on accordproject:master.


666 - added FAQ for testing

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[X ] Code is formatted according to the tidyverse style guide
[X ] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[X ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[X ] Update to all relevant roxygen headers and examples
[X ] Run devtools::documents() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[X ] Address any updates needed for vignettes and/or templates
[X ] Update NEWS.md
[X ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[X ] Address or fix all lintr warnings and errors - lintr::lint_package()
[X ] Run R CMD check locally and address all errors and warnings - devtools::check()
[X ] Link the issue so that it closes after successful merging.
[X ] Address all merge conflicts and resolve appropriately
[X ] Pat yourself on the back for a job well done!  Much love to your accomplishment!

@koegerr i added the one extra FAQ question and also removed some blank lines.

@thomas-neitmann i got some fails for "R-CMD-check / ubuntu-20.04 (release)" but can't see why from the messages and the minor updates I made. has this happened for any other recent PRs?

This is not related to any changed you've made. We fixed the failing test cases on the devel branch. To get those changes into your branch please run the following commands in your RStudio terminal:
git checkout devel
git pull
git checkout 666_testing_faq
git merge --no-edit devel
git push

Thanks @thomas-neitmann - that fixed it! appreciate if you or @koegerr could review and merge this PR.


Easy streaming

Something that addresses my comments on #4, based on explorations and habnabit's gist @ https://gist.github.com/habnabit/6885876.
Notes & questions:

It's somewhat under-tested. Am happy to take suggestions for tests to add.
Should I re-export this from parsley top-level?

I'm not going to do any work on this.


Big endian support

This patch allows AtomVM to compile and run on MIPS.
utils_h-enable-big-endian-support.patch.gz

Thanks for the contribution, I'm going to use your input as a first step for proper big endian support.
If you'd like to share more information on the target CPU where you tested it might be interesting.

@rtATvw please, make sure to use latest snapshot from master. The patch you provided is a good starting point but it is not enough for building AtomVM that is able to pass our tests.


[Modelio] Connection Diagram - Error R2680 - Line Follower Robot example

Hi,
I was development a study case in:
windows 10, modelio 3.4, with module INTOCPS_1.0.40.jmdac
but suddenly I realized that I´ve one particular error:

R2680 -
Summary
The number of parameters of a TaggedValue must be the same as the number of parameters defined in the TaggedValue type.

Later, I was trying to compare what I was doing wrong with the tutorials, particulary with the Line Follower Robot (LFR). I realized that in the LFR´s conection diagram has the same error BUT it only appears if you clic the sensor block.
You can take a look of this in the audit tab showing: (1) Error, (0) warning and (0) advise.
Also I´ve realized that if you save your project with the same mistake and then re-open it, the error dissapears. But if you clic again in the block that contains the error, re-appears.
Should I care about this? Or  continue?
Thanks in advance,
Enrique V.

Hi Enrique,
You can continue, I will check that.
Cheers,
Etienne

Thank you Etienne form the quick answer! Let me know if you have news
Regards,
Enrique

@etiennebrosse any news? otherwise close the issue with a description of the state and workaround or solution.


When animation is turned off in android settings, elements under a submenu aren't shown

Title tells everything.
When in the settings of the phone, we turn of animations (accessibility settings) the options under a submenu do not appear.
e.g. Settings -> Theme -> light, Dark ...   Here when we click on 'Settings', we should see 'Theme' but there is nothing there.
Maybe I miss something, but haven't seen anything what could help.

Hi @sandorfimarci, I don't see this happening on my side. Possible for you to share a reproducer along with details of your device and android version?
https://github.com/saket/cascade/assets/2387680/7e135d3e-40b1-40f6-aced-2c66f582f982

Closing due to inactivity. Please feel free to reopen.


get two different test result of phantomjs with TAP format on one URL

I'm using phantomjs for test my site on Jenkins, and got the different result of the TAP within two builds, There is nothing changed. However, The result of Junit xml are same as we expected.
This is what I compared the result of TAP.
3,4c3,4
< ok 1 B (82) overall score
< not ok 2 D (68) ynumreq: Make fewer HTTP requests
---
> not ok 1 C (78) overall score
> ok 2 B (80) ynumreq: Make fewer HTTP requests

24c21
<   message: There are 50 static components without a far-future expiration date.
---
>   message: There are 45 static components without a far-future expiration date.

77c69,81
< ok 6 A (100) ycompress: Compress components with gzip
---
> not ok 6 F (12) ycompress: Compress components with gzip

Thanks for the report.  We need more information before we can do anything about it.  Your tests appear to be checking for compliance with Yahoo's performance guidelines, is that right?  Did you write them yourselves, or did you get them from somewhere?  What website is this?  Exactly how are you using TAP and Jenkins?
FYI, I think this is more likely to be a problem within your own build process or testsuite than a problem with PhantomJS itself.  How did you verify that the two builds were exactly the same?  Is it possible that some of the tests are not 100% deterministic?  They seem to be reporting results in a different order each time, that is often a sign of race conditions.

@zackw  Thanks ! I've find out the reason, It seems like what you said.
The URL of I tested that is a live server on line, and it's a CDN domain which resolved multiple servers.

OK, I am going to close this issue now.  Thanks for clarifying.


Do not generate reports into same folder

It's a little annoying when you run check-ttf.py which then dumps the Ms Validator reports in your shiny google/fonts family dir.

before

after
I recommend these are stored elsewhere.

ok, cool. Let's avoid that!

Thanks man!

It may also be nice to put all output in $pwd/FB/* so that we can add that
to gitignore files
On May 10, 2017 6:29 PM, "Marc Foley"<EMAIL_ADDRESS>wrote:

Thanks man!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlefonts/fontbakery/issues/1340#issuecomment-300631113,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP9y9QQy7HM8k8LczIl4UStpMULoEBxks5r4jo7gaJpZM4NWi0I
.


Request for Causal AR Version Release

Great work! Could you please release the causal AR version used in your experiments from the paper? It would be incredibly helpful for further exploration. Thank you!

Thanks for your interest! To keep this repo clean, we don't have a plan to release the causal AR code in this repo. However, it is very easy to reimplement using the current repo -- almost all hyper-parameters remain the same as MAR. The only difference is the causal attention mask and the teacher-forcing loss.

Would it be possible to share the causal-AR inference code and checkpoints? Your help would mean a lot. Many thanks in advance!

Great work! Could you please release the causal AR version used in your experiments from the paper? It would be incredibly helpful for further exploration. Thank you!

https://github.com/lucidrains/autoregressive-diffusion-pytorch?tab=readme-ov-file There is another version that lucidrains Implemented.


Get rid of div grouping metro name and state

Currently metro names and states are individually treated as divs. These divs are nested under another div which makes its size too large to fit in one line in the compare table. This PR gets rid of the parent div and adjusts each individual text to span to enable the elements that would fit to roll up to the first line, as illustrated below.
Before:

After:

 Fix wrapping for metro names on the homepage. Consider truncating

The styling is not quite what we need (the locations shouldn't be underlined, and we want to keep the spacing around the dot), let's sync tomorrow!


Fix RayHook conn_name_attr

Historically, someone assigned the incorrect value to this property.
It overrides the KubernetesHook and all the examples and tests (including test_dag_example.py actually use conn_id, as opposed to ray_conn_id.

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

Project coverage is 98.52%. Comparing base (8ccc839) to head (b079817).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
+ Coverage   98.03%   98.52%   +0.49%
==========================================
  Files           7        7
  Lines         610      610
==========================================
+ Hits          598      601       +3
+ Misses         12        9       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Option to write out all individual test case results to json output file

I am quite interested in individual test case results for Pass, Fail and Skipped (vs just failed).  It would be nice if we somehow expose the option to access individual test case results in the output json (the contents of this object)
https://github.com/EnricoMi/publish-unit-test-result-action/blob/master/python/publish/publisher.py#L296
I'm happy to submit a PR that does something like add a cleaned up version of that object to the output json if an optional parameter is supplied to the action, for instance, if it makes sense.

Can you provide an example JSON that you would like to add to the output json?
Why do you want to upload it to the Checks API (according to https://github.com/airbytehq/airbyte/pull/18004)? You could upload the JSON file as an artifact and retrieve that? Or is that because checks are easier to retrieve for a commit than artifacts?

Sorry if it wasn’t clear from the wording of the issue. The ask is to add it to the output file only if some optional parameter is specified and not to modify what gets uploaded to the Checks API. 100% agree that this info is very often way too big to even remotely fit in a lot of use cases; with my use case the output of the “cases” object easily exceeded 1 million bytes.
I the way the “cases” key/value exists as it does currently would probably be more than sufficient if it was added to the output JSON file with little to no modification.

PR with aforementioned approach: https://github.com/EnricoMi/publish-unit-test-result-action/pull/366

Then we are on the same page. Sounds good to add this to the JSON file!

@cpdeethree Btw., can you please remove your forked action from the GitHub Marketplace, or clearly state that it is a fork: https://github.com/marketplace/actions/publish-test-results-with-json-text

@EnricoMi delisted!

Appreciated!


Highlight Tagged Monsters

As far as I know, there currently isn't a way to know if the monster you're fighting has been tagged by another player unless it has a visible red health bar. I'd like to suggest a plugin that highlights monsters that have already been tagged by another player. This would be useful for Ironmen seeing as they do not get drops if a monster has been attacked by someone else. Perhaps it could highlight the monsters the same way the NPC Indicators plugin does.

Almost a year later and this still doesn't exist but it would be so nice if it did!

We can do this much more easily once the hitsplat tinting feature lands in OSRS. Until then, we're not likely to add this.

I've been looking into potentially creating it myself, but why specifically would the hitsplat tinting help there?

It will let you know with certainty when a monster has been hit by another player.


GeoJSON support

Is GeoJSON supported yet? The chunking would be easy here, since one GeoJSON object is typically one Feature.

No, GeoJSON is not supported yet. GeoRocket can only import/export XML at the moment.
You may convert JSON to XML. AFAIK this should work well since GeoRocket does not check namespaces or the validity of XML documents. You may use Jackson, for example, to do an easy conversion. See the following StackOverflow thread. Jackson also supports converting back from XML to JSON.
http://stackoverflow.com/questions/6742705/simplest-method-to-convert-json-to-xml
GeoJSON is one of the things that we want to implement next, so I'll keep this issue open to track the progress.

GeoJSON support is now ready in the master branch. It will be part of the soon be released version 1.0.0.
Cheers,
Michel


HTTP2 CVE's

A number of CVE's were published today that affect a lot of HTTP2 implementations. I wanted to flag them here in case cowboy is also vulnerable to any of them.
Relevant vulnerabilities: https://www.kb.cert.org/vuls/id/605641/
Example of some mitigations: https://github.com/kubernetes/ingress-nginx/commit/333d9fd48d69730a03e087fb6e0f0dae5601c04f

Well let's go over them one by one. In bold the ones that are more important:

Data Dribble: We should probably have an option to not try to send data unless the window is above a certain size (or the window is larger than what's left to send). This is a good idea even just as an optimization.
Ping Flood: I'm not too worried about that one but I guess a generic flood detection could be good to have at some point.
Resource Loop: Cowboy has not implemented the priority mechanism, in part because of issues like this. These have been well known from the start.
Reset Flood: Same as ping, except here I'd be more worried about the CPU lost to decoding headers (if it goes that far).
Settings Flood: Same as ping.
0-Length Headers Leak: I suppose that's more relevant if you pre-allocate header strings. For Cowboy that's not the case and they would be an empty binary. Still we probably should reject them since they're not valid, if we don't already.
Internal Data Buffering: I think at some point the Transport:send will simply not return and timeout. The question then becomes is the connection dropped as a result. A test would be good to know Cowboy's behavior definitely, regardless of this being used as an attack vector.
Empty Frame Flooding: Same as ping.

Flood I think we should just count the number of frames received and compare it to the number of non-useful frames received (ping, priority, settings, frames resulting in stream errors, empty frames), if the latter is too high then we drop the connection. Maybe have two options: one indicates how many non-useful frames we accept without question (without considering it a flood even if that's 100% of frames received, can happen if there's no ongoing streams for example), and one indicates the ratio we accept when we look for a potential flood.

I guess the minimum DATA frame size would be a good default for a minimum window size before we start sending data (if we have less to send we of course just wait for the window to get high enough). Then if this limit is configurable users can increase it depending on their application's needs.

I suppose we could also be flooded with 1-byte DATA frames, not just empty frames. Or large headers sent with many 1-byte CONTINUATION. I guess a configurable limit in the number of frames received for a specific stream would be a better approach in that scenario. So Empty Frame Flooding is not exactly the same as ping.

Thoughts welcome on how to detect, fix (if necessary) and test the Internal Data Buffering one. I currently have no idea what to do about it.

Re Internal Data Buffering. I think the backpressure implemented recently in master is the fix that was necessary. With it it's possible to configure a maximum size of buffered data for the stream. This with socket options and configurable maximum number of streams should allow limiting the total memory a connection can take. But perhaps it could be augmented with a configurable connection-wide buffered data limit.
I don't really know how to write a test for the vulnerability itself though.

OK going to add the following options:

max_connection_buffer_size the equivalent of max_stream_size but applying to the entire connection, for an easier control of the upper memory bound of a connection. Defaulting to 16MB (stream is 8MB).
max_frame_rate given as {Intensity, Period} to configure how many frames are allowed per period of time (including infinity). Default probably something like {1000, 10000}, 1K frames in 10 seconds. 1K data frames at the default size of 16384 is therefore around 1.6MB/s, which is probably too small for some applications but ought to be large enough in most cases. All frames will be counted because that's just simpler. Rather than use a timeout or query the time every frame I'll just add the frames and check how much time has passed when the maximum has been reached.
max_reset_stream_rate is basically the same except we count the number of streams we've had to reset because an error occurred. The default in this case should be something like {10, 10000}, so 10 every 10 seconds. If clients are well written they should not get streams reset.
stream_data_threshold is how large the window ought to be before we start sending data, in order to avoid sending too many DATA frames. Default should be the same as the default frame size, 16384.

 Feedback welcome!

I've started pushing all this but I'll have to finish tomorrow or Thursday.

Done.

@essen Thanks for the fix. I just feel the default value is a little small for HTTP/2 because users may use multiple streams over one single connection in HTTP/2.

Could you be more specific? Which default value?

I mean max_received_frame_rate. I got an error when I tested sending a large body. But it’s indeed hard to find a perfect default value.

Maybe it should be increased. Question is to what value. Please open a separate ticket.


View all option to put the limit at 1000

It's the second time this week I have been ask to have a view all option in Magento and we currently have a pending pull request for that. Can we consider adding that in the core ?

Sorry, I don't understand what you're refering to. What options? Could you link to the PR?

Yes the PR is here https://github.com/algolia/algoliasearch-magento/pull/233 but it's not really explicit. Basically e-commerce guys want to let the ability for the user to remove the hitsPerPage by clicking on a "View All" button. For us this means having a button to set hitsPerPage to 1000

I think an option to add this in the pagination widget could be good

Yes the PR is here algolia/algoliasearch-magento#233 but it's not really explicit. Basically e-commerce guys want to let the ability for the user to remove the hitsPerPage by clicking on a "View All" button. For us this means having a button to set hitsPerPage to 1000

I don't think having hitsPerPage=1000 is a good idea, do you think an infinite scroll widget could help?

I guess that could do the trick, but as I understood it, it seems to be something the end user need to be able to choose.

But event without this, I think having a infinite scroll widget makes a lot of sense

widgets.infiniteHits :)

Yep infiniteHits would be fun to build :)

@maxiloc: Would an infinite scroll widget fit you need? If so I'll rename the issue.

@pixelastic You can also create a new one with your proposal in it. Also this is "next" :)

@pixelastic Yes infinite scroll would fit. Would it be switchable with the hits widget by the user on the fly ?

I've added a specific issue for the infiniteScroll here: https://github.com/algolia/instantsearch.js/issues/328
I don't think this is something we would want to let the user toggle on/off (so many corner cases).
Maybe what you need is something like the indexSelector widget but for hitsPerPage?

Maybe what you need is something like the indexSelector widget but for hitsPerPage?

Yes that is better and would solve the issue better than the infinite scroll widget

Yes that is better and would solve the issue better than the infinite scroll widget

But displaying 1000 hits on a single page will be a fail without a proper lazy loading right? 1000 divs + 1000 images = you kill the browser

Yes I know that fetching 1000 hits is not good, but having a widget to change the hitsPerPage seems good anyway. We just need to explain that fetching 1000 is not a good idea.

I've also added an issue for the hitsPerPageSelector here : https://github.com/algolia/instantsearch.js/issues/331
I close this one.


Wrong configuration on Android

I'm trying to figure out why the logs aren't being sent to New Relic dashboard. I followed all steps described in Readme

+1

+1

+1, @lucasfjportela @lyseiha did you found any workaround.

I'm not using this lib anymore, but I didn't find any workaround to this issue.


Discussion: repo naming as seedcase vs seedcase-project?

https://github.com/seedcase-project/seedcase-project/blob/56e3536e6b1bb543e82beea91d95f43fd53433ea/community/guide-entries/documentation-first/index.qmd#L82-L98
It's not entirely clear to me from the naming or description what the seedcase vs seedcase-project repo is :-)
Also: It seems there are more repos in the organisation (seedcase-registry and seedcase-theme) than on this list. Is this intentional or does this list need to be updated?

seedcase-website or seedcase-home.


Get faster

Benchmarks are currently running about 3X slower than for commonmark.js.  It would be good to understand why and narrow the gap.

Funny thing is that when I benchmark the commonmark.js CLI against the djot one, the djot one is always slightly faster. So I am not sure how to interpret these results.  It could be that there's a bit more startup overhead in each conversion for djot (perhaps because of how parser objects are created) and that this predominates in repeated tests parsing very small texts. When longer texts are using, the difference in startup overhead gets swamped and djot comes out ahead.
It may be that there's some low hanging fruit to be plucked, but I'd probably need guidance from someone who is more experienced in optimizing JS.

As a data-point, for me djot takes about 1.75x more time than common mark when rendering a 3.5mb file.
Here's a flamegraph for djot, haven't look at it yet: https://share.firefox.dev/3IuG1qg

With node

This part looks potentially optimizable:
    for (let i = this.firstpos; i <= this.lastpos; i++) {
      if (this.matches[i]) {

If I understand this correctly, here we go through every "char" position and do a hashmap lookup. I think the map should be pretty sparse, so it'd be more efficient to convert matches to array and sort them by pos rather than enumerating every pos

this.matches actually is an array -- though it's a sparse array and perhaps that's implemented just as a hash map.
Anyway, the reason it needs to be indexed by pos is that we sometimes override an earlier match, e.g. * might first be categorized as str but then later +emph.
If we just used an array, we could perhaps just add the +emph with the same position later in the array, then sort the array, then remove the first of every pair of adjacent elements with the same startpos, or something like that.

Yeah, there's some water to squeeze out this stone: if I replay array with Map, I get 10% win. Though, I commented out the code that handles hardline breaks, as that uses the last element of the array, and we don't have that with Map.

I am wondering: can we refer to an earlier match not by codepoint offset, but by its position in the matches array? That is, we accumulate events in an array, events are generally   .sorted by their startpos, but, if we change our mind about some past events, we go to their position in an array and replace them with tombstones.
I use a similar device in rust-analyzer:
https://github.com/rust-lang/rust-analyzer/blob/80cabf726068187d8686b5ccf37aac484da84904/crates/parser/src/event.rs#L20-L81
Parsing events are accumulated into a flat array, but events can be tombstones, or they can refer to future events.

Yes, this sounds like a plausible idea.
The main change would be adding to Opener a field for the index into the matches array (since we wouldn't be able to use the startpos for this).  This would have to be added in addOpener. It would also be a good idea to incorporate adding the "default match" to addOpener; this would ensure we get the right index. Currently we do addOpener and then addMatch to add the default match.
Other cases to handle:

currently we delete earlier "str" matches for $ or $$ before verbatim (since this turns into math). (lines 217-222). This should be doable with the proposed approach; we'd have to talk back through the array a bit and change these to tombstones.  But this is going to be infrequent and wouldn't require walking back more than a few elements.
line 408 we use strMatches to convert all the matches between start and endpos for reference to str. This should be doable with the proposed approach; we can just walk back through the array til we get to the start position.
line 490 similarly but with destination

And then we need to figure out what the tombstone is and how to strip it out.  It could just be null, I suppose, and we could filter the array on !== null before sorting?  But maybe v8 would prefer if we used the same type throughout, in which case we could have annot = "tombstone".

I've made a stab at this in #24. I think the code is more elegant (and shorter) now.  But two tests fail and I haven't yet gotten to the bottom of it.

Looked at the perf profile again this morning. Sadly, nothing more stands out: at this (function) level of granularity, the profile looks mostly flat, it's "stuff takes time" basically. I think we'll need some sort of line profiler to get further along, but quick googling didn't show how to get that with JS.
Nonetheless:

I see a bunch of time taken by Builtins_KeyedLoadIC_Megamorphic. I have no idea what calls this function, but the "megamorphic" in the name seems to imply that we hit deoptimized path somewhere. Specific "somewhere" is missing, so this is unlikely to be actionable.
I see v8::internal::StringTable::Data::TryStringToIndexOrLookupExisting. I think that one comes from doing lookups in the handlers array in parse.js. It seems that what is happening here is genuine hash-table lookup -- we hash the tag name, etc. In particular,(hypothesis) because we do things like "-" + annotation, our annotations aren't really interned-at-compile-time symbols, but actual runtime strings.
The array sorting from getMatches is visible in the profile. It seems that in principle we can avoid the need to sort.
accumulatedText.join("") is visible in the profile, would probably be faster if we += strings directly

I adjusted the commonmark.js profiling so it matches what we're doing (parsing only, constructing object inside the profiling loop), only with cm versions of our dj files.
The differences are rather astounding, though I must say I don't understand why the observed differences on real-world conversions are not very large:
block-bq-flat.md 263,041 ops/sec ±0.21% (100 runs sampled)
block-bq-nested.md 146,306 ops/sec ±0.18% (100 runs sampled)
block-code.md 555,951 ops/sec ±0.13% (100 runs sampled)
block-fences.md 600,999 ops/sec ±0.12% (99 runs sampled)
block-heading.md 283,913 ops/sec ±0.18% (100 runs sampled)
block-hr.md 437,882 ops/sec ±0.14% (100 runs sampled)
block-html.md 154,155 ops/sec ±0.21% (99 runs sampled)
block-lheading.md 386,463 ops/sec ±0.16% (100 runs sampled)
block-list-flat.md 34,534 ops/sec ±0.16% (101 runs sampled)
block-list-nested.md 34,284 ops/sec ±0.19% (101 runs sampled)
block-ref-flat.md 85,683 ops/sec ±0.22% (94 runs sampled)
block-ref-nested.md 73,614 ops/sec ±0.18% (95 runs sampled)
inline-autolink.md 92,900 ops/sec ±0.16% (101 runs sampled)
inline-backticks.md 451,831 ops/sec ±0.16% (100 runs sampled)
inline-em-flat.md 120,869 ops/sec ±0.21% (100 runs sampled)
inline-em-nested.md 168,278 ops/sec ±0.17% (101 runs sampled)
inline-em-worst.md 170,375 ops/sec ±0.17% (101 runs sampled)
inline-entity.md 193,644 ops/sec ±0.19% (98 runs sampled)
inline-escape.md 131,929 ops/sec ±0.15% (101 runs sampled)
inline-html.md 57,738 ops/sec ±0.18% (100 runs sampled)
inline-links-flat.md 52,047 ops/sec ±0.19% (97 runs sampled)
inline-links-nested.md 104,131 ops/sec ±0.16% (101 runs sampled)
inline-newlines.md 187,799 ops/sec ±0.25% (100 runs sampled)
lorem1.md 72,545 ops/sec ±0.16% (100 runs sampled)
README.md 7,623 ops/sec ±0.24% (99 runs sampled)

One thing I want to try is loading the webpacked bundle instead of lib/*.js.

PS. My memory of optimizing the commonmark.js parser was that it was largely a matter of doing things that made the v8 optimizer happy -- so, it wasn't like optimizing a regular program, where you look for hot spots, but more about doing magic tricks that suddenly made a huge difference.

Tried replacing accumulatedText with a string, but no improvement, slight slowdown in some cases.

I think your first two findings are the most promising.  Something is megamorphic, and if we figure out what's triggering that it could have a big effect. Note that in commonmark.js, we just use a Node object that, essentially, has all the fields anything will need (stringContent, destination, title, level, fenceChar, etc.).  That ensures that all the objects have the same "shape," which apparently makes the optimizer happy.  In djot.js, by contrast, we have AST nodes with different shapes.  I'm not sure how to fix this, though; we want different shapes.  One possible option to explore would be keeping the things that vary under a data field, so we have
{ tag: "heading",
  children: ...,
  attributes: ...,
  data: { level: 5 }
}

The second thing, avoiding things ilke "+" + annotation, seems worth exploring for sure.

OK, I managed to remove the need for the .sort() in inlines.
This gives us the following benchmarks (around a 20% improvement in inline heavy text):
parse block-bq-flat.dj x 111,995 ops/sec ±0.64% (97 runs sampled)
parse block-bq-nested.dj x 54,569 ops/sec ±1.51% (97 runs sampled)
parse block-code.dj x 224,163 ops/sec ±0.68% (98 runs sampled)
parse block-fences.dj x 210,808 ops/sec ±0.46% (100 runs sampled)
parse block-heading.dj x 77,986 ops/sec ±0.43% (101 runs sampled)
parse block-hr.dj x 83,618 ops/sec ±0.38% (97 runs sampled)
parse block-list-flat.dj x 11,321 ops/sec ±0.54% (101 runs sampled)
parse block-list-nested.dj x 14,747 ops/sec ±0.52% (99 runs sampled)
parse block-ref-flat.dj x 24,116 ops/sec ±0.36% (98 runs sampled)
parse block-ref-nested.dj x 17,338 ops/sec ±0.27% (100 runs sampled)
parse inline-autolink.dj x 44,454 ops/sec ±0.33% (101 runs sampled)
parse inline-backticks.dj x 125,638 ops/sec ±0.37% (101 runs sampled)
parse inline-em-flat.dj x 41,196 ops/sec ±0.28% (96 runs sampled)
parse inline-em-nested.dj x 41,667 ops/sec ±0.24% (101 runs sampled)
parse inline-em-worst.dj x 48,444 ops/sec ±0.32% (100 runs sampled)
parse inline-escape.dj x 39,112 ops/sec ±0.35% (96 runs sampled)
parse inline-links-flat.dj x 22,038 ops/sec ±0.50% (99 runs sampled)
parse inline-links-nested.dj x 17,464 ops/sec ±0.31% (101 runs sampled)
parse lorem1.dj x 22,343 ops/sec ±0.36% (101 runs sampled)
parse readme.dj x 3,100 ops/sec ±0.57% (100 runs sampled)
renderHTML readme x 17,336 ops/sec ±0.08% (98 runs sampled)

In a real-world test with converted versions of the same document, I'm getting:
djot: 2874 bytes/ms
commonmark.js: 3780 bytes/ms

After a few more optimizations, I've improved it a bit more:
parse block-bq-flat.dj x 116,613 ops/sec ±0.58% (99 runs sampled)
parse block-bq-nested.dj x 57,481 ops/sec ±1.44% (96 runs sampled)
parse block-code.dj x 282,016 ops/sec ±0.48% (98 runs sampled)
parse block-fences.dj x 272,059 ops/sec ±0.49% (95 runs sampled)
parse block-heading.dj x 86,364 ops/sec ±0.65% (97 runs sampled)
parse block-hr.dj x 89,644 ops/sec ±0.38% (99 runs sampled)
parse block-list-flat.dj x 12,203 ops/sec ±0.54% (98 runs sampled)
parse block-list-nested.dj x 15,496 ops/sec ±0.50% (100 runs sampled)
parse block-ref-flat.dj x 24,117 ops/sec ±0.35% (100 runs sampled)
parse block-ref-nested.dj x 17,079 ops/sec ±0.26% (98 runs sampled)
parse inline-autolink.dj x 44,118 ops/sec ±0.32% (100 runs sampled)
parse inline-backticks.dj x 125,903 ops/sec ±0.35% (100 runs sampled)
parse inline-em-flat.dj x 41,459 ops/sec ±0.30% (100 runs sampled)
parse inline-em-nested.dj x 42,237 ops/sec ±0.30% (96 runs sampled)
parse inline-em-worst.dj x 47,392 ops/sec ±0.32% (97 runs sampled)
parse inline-escape.dj x 39,054 ops/sec ±0.32% (99 runs sampled)
parse inline-links-flat.dj x 22,308 ops/sec ±0.36% (101 runs sampled)
parse inline-links-nested.dj x 17,341 ops/sec ±0.30% (99 runs sampled)
parse lorem1.dj x 22,885 ops/sec ±0.36% (98 runs sampled)
parse readme.dj x 3,262 ops/sec ±0.56% (98 runs sampled)
renderHTML readme x 17,430 ops/sec ±0.05% (97 runs sampled)

After 1492366b9451aa6055ea9dd9c55a0ca18de10632 :
parse block-bq-flat.dj x 132,922 ops/sec ±0.63% (97 runs sampled)
parse block-bq-nested.dj x 64,055 ops/sec ±1.37% (93 runs sampled)
parse block-code.dj x 305,707 ops/sec ±0.67% (98 runs sampled)
parse block-fences.dj x 289,597 ops/sec ±0.52% (97 runs sampled)
parse block-heading.dj x 96,519 ops/sec ±0.59% (93 runs sampled)
parse block-hr.dj x 100,535 ops/sec ±0.73% (99 runs sampled)
parse block-list-flat.dj x 12,279 ops/sec ±0.92% (99 runs sampled)
parse block-list-nested.dj x 15,425 ops/sec ±0.59% (99 runs sampled)
parse block-ref-flat.dj x 27,987 ops/sec ±0.54% (93 runs sampled)
parse block-ref-nested.dj x 19,508 ops/sec ±0.32% (96 runs sampled)
parse inline-autolink.dj x 49,090 ops/sec ±0.32% (100 runs sampled)
parse inline-backticks.dj x 139,996 ops/sec ±0.54% (100 runs sampled)
parse inline-em-flat.dj x 46,086 ops/sec ±0.30% (96 runs sampled)
parse inline-em-nested.dj x 47,134 ops/sec ±0.29% (96 runs sampled)
parse inline-em-worst.dj x 57,647 ops/sec ±0.35% (99 runs sampled)
parse inline-escape.dj x 47,039 ops/sec ±0.34% (100 runs sampled)
parse inline-links-flat.dj x 26,364 ops/sec ±0.39% (101 runs sampled)
parse inline-links-nested.dj x 21,174 ops/sec ±0.33% (98 runs sampled)
parse lorem1.dj x 26,566 ops/sec ±0.38% (100 runs sampled)
parse readme.dj x 3,529 ops/sec ±0.57% (99 runs sampled)
renderHTML readme x 17,457 ops/sec ±0.04% (101 runs sampled)

After ddb155a9849c89f52a958af303e290a88d8447a8
parse block-bq-flat.dj x 131,276 ops/sec ±0.60% (96 runs sampled)
parse block-bq-nested.dj x 63,742 ops/sec ±1.39% (95 runs sampled)
parse block-code.dj x 301,477 ops/sec ±0.64% (100 runs sampled)
parse block-fences.dj x 286,620 ops/sec ±0.50% (97 runs sampled)
parse block-heading.dj x 95,016 ops/sec ±0.50% (99 runs sampled)
parse block-hr.dj x 103,091 ops/sec ±0.37% (102 runs sampled)
parse block-list-flat.dj x 12,714 ops/sec ±0.51% (101 runs sampled)
parse block-list-nested.dj x 15,965 ops/sec ±0.53% (100 runs sampled)
parse block-ref-flat.dj x 28,886 ops/sec ±0.38% (99 runs sampled)
parse block-ref-nested.dj x 19,939 ops/sec ±0.27% (102 runs sampled)
parse inline-autolink.dj x 50,233 ops/sec ±0.35% (100 runs sampled)
parse inline-backticks.dj x 145,375 ops/sec ±0.38% (98 runs sampled)
parse inline-em-flat.dj x 46,144 ops/sec ±0.27% (99 runs sampled)
parse inline-em-nested.dj x 46,735 ops/sec ±0.27% (98 runs sampled)
parse inline-em-worst.dj x 57,474 ops/sec ±0.33% (99 runs sampled)
parse inline-escape.dj x 47,054 ops/sec ±0.35% (99 runs sampled)
parse inline-links-flat.dj x 26,326 ops/sec ±0.37% (101 runs sampled)
parse inline-links-nested.dj x 21,142 ops/sec ±0.32% (101 runs sampled)
parse lorem1.dj x 26,505 ops/sec ±0.37% (98 runs sampled)
parse readme.dj x 3,523 ops/sec ±0.57% (99 runs sampled)
renderHTML readme x 29,028 ops/sec ±0.04% (98 runs sampled)

After 57c81eaaca51e13d0f94b66a4dec63dda95fb6d7
parse block-bq-flat.dj x 132,939 ops/sec ±0.65% (94 runs sampled)
parse block-bq-nested.dj x 64,598 ops/sec ±1.51% (92 runs sampled)
parse block-code.dj x 324,897 ops/sec ±0.68% (100 runs sampled)
parse block-fences.dj x 309,821 ops/sec ±0.53% (97 runs sampled)
parse block-heading.dj x 98,134 ops/sec ±0.49% (95 runs sampled)
parse block-hr.dj x 103,908 ops/sec ±0.39% (100 runs sampled)
parse block-list-flat.dj x 12,846 ops/sec ±0.54% (98 runs sampled)
parse block-list-nested.dj x 16,011 ops/sec ±0.77% (98 runs sampled)
parse block-ref-flat.dj x 29,263 ops/sec ±0.54% (97 runs sampled)
parse block-ref-nested.dj x 19,837 ops/sec ±0.57% (97 runs sampled)
parse inline-autolink.dj x 51,005 ops/sec ±0.33% (99 runs sampled)
parse inline-backticks.dj x 151,295 ops/sec ±0.38% (97 runs sampled)
parse inline-em-flat.dj x 46,415 ops/sec ±0.27% (102 runs sampled)
parse inline-em-nested.dj x 46,887 ops/sec ±0.26% (102 runs sampled)
parse inline-em-worst.dj x 57,678 ops/sec ±0.33% (101 runs sampled)
parse inline-escape.dj x 47,065 ops/sec ±0.35% (102 runs sampled)
parse inline-links-flat.dj x 26,569 ops/sec ±0.41% (101 runs sampled)
parse inline-links-nested.dj x 21,242 ops/sec ±0.33% (100 runs sampled)
parse lorem1.dj x 26,592 ops/sec ±0.36% (101 runs sampled)
parse readme.dj x 3,577 ops/sec ±0.56% (100 runs sampled)
renderHTML readme x 28,820 ops/sec ±0.05% (98 runs sampled)

After upgrading to node v16, times are slower. I note this here so we don't think changes in the code have caused the slower performance:
parse block-bq-flat.dj x 118,939 ops/sec ±0.77% (99 runs sampled)
parse block-bq-nested.dj x 56,804 ops/sec ±0.68% (100 runs sampled)
parse block-code.dj x 287,796 ops/sec ±0.58% (91 runs sampled)
parse block-fences.dj x 279,181 ops/sec ±0.58% (98 runs sampled)
parse block-heading.dj x 91,807 ops/sec ±0.92% (94 runs sampled)
parse block-hr.dj x 90,520 ops/sec ±0.11% (96 runs sampled)
parse block-list-flat.dj x 11,376 ops/sec ±2.63% (94 runs sampled)
parse block-list-nested.dj x 14,992 ops/sec ±0.84% (99 runs sampled)
parse block-ref-flat.dj x 26,437 ops/sec ±0.58% (97 runs sampled)
parse block-ref-nested.dj x 18,655 ops/sec ±0.51% (100 runs sampled)
parse inline-autolink.dj x 48,486 ops/sec ±0.59% (98 runs sampled)
parse inline-backticks.dj x 139,860 ops/sec ±0.54% (99 runs sampled)
parse inline-em-flat.dj x 51,949 ops/sec ±0.45% (97 runs sampled)
parse inline-em-nested.dj x 51,112 ops/sec ±0.51% (98 runs sampled)
parse inline-em-worst.dj x 51,228 ops/sec ±0.45% (96 runs sampled)
parse inline-escape.dj x 42,468 ops/sec ±0.48% (99 runs sampled)
parse inline-links-flat.dj x 24,437 ops/sec ±1.18% (99 runs sampled)
parse inline-links-nested.dj x 18,685 ops/sec ±0.49% (98 runs sampled)
parse lorem1.dj x 23,750 ops/sec ±0.48% (97 runs sampled)
parse readme.dj x 3,275 ops/sec ±0.94% (96 runs sampled)
renderHTML readme x 29,720 ops/sec ±0.07% (98 runs sampled)


The import com.github.tomakehurst.wiremock.client.WireMock cannot be resolved

I'm trying to use Wiremock standalone. This is how I'm using the maven dependency

com.github.tomakehurst
wiremock-standalone
2.8.0

junit
junit
4.12
test

The Jar is installed properly but when I try to access the Library using import it thows below error
The import com.github.tomakehurst.wiremock.client.WireMock cannot be resolved

That sounds like a build tool issue rather than something WireMock specific. I suggest you post on the support list for whatever build tool you are using.


Test case for the undownload problem in createReadStream

https://gist.github.com/pfrazee/e5cf70dfd06a8d9f4e25e468b33c748e
If you clone that gist, npm i, then node index.js, you'll see the undownload error emit.

fixed in latest release

Thanks!!
On Sat, Jul 1, 2017 at 7:53 AM, Mathias Buus<EMAIL_ADDRESS>wrote:

Closed #174 https://github.com/mafintosh/hyperdrive/issues/174.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mafintosh/hyperdrive/issues/174#event-1146948823, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNhU3k3_54eKNV-RSAPFgqiCHvoIUFrks5sJkFQgaJpZM4OF3pm
.


[Feature] MongoDB on Amazon EKS

Build a Terraform template to build and deploy scalable MongoDB platform on Amazon EKS

Terraform Template for deployment
If you need new Kubernetes add-ons then use EKS Blueprints to add a new add-on
README with deployment steps
Add a new Website Doc with design diagram, deployment (refer to README here for deployment steps) and how to run sample tests etc.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Describe the solution you would like

Describe alternatives you have considered

Additional context

Hi @vara-bonthu, I am interested on this one. For MongoDB, there are three versions (community, enterprise and Atlas). Which one you would like to cover? enterprise may require the license and key I don't have and Atlas is SaaS version. So I am thinking to work on community version.
pls let me know if anything you think I should cover. I will book a meeting with you if you think it is more convenient to share ideas. Thanks.

The is for opting this one. Yes, the community would be better to start with, and we can provide guidelines for the MongoDB enterprise version in the docs. Ideally, we want partners to build enterprise versions in EKS.
Docs and best practices are critical for our DoEKS patterns. Let me know for any questions

Closing this issue as its in the ROADMAP


scheduler: add grant hot region scheduler for test

What problem does this PR solve?
add grant hot region scheduler for test

What is changed and how it works?
Check List

Tests

Unit test
Integration test

Code changes
Side effects
Related changes
Release note

Codecov Report

Merging #2 (6a24eb1) into master (22d8802) will increase coverage by 0.44%.
The diff coverage is 76.84%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   74.38%   74.82%   +0.44%
==========================================
  Files         260      265       +5
  Lines       26468    27483    +1015
==========================================
+ Hits        19688    20564     +876
- Misses       4999     5093      +94
- Partials     1781     1826      +45

Flag
Coverage Δ

unittests
74.82% <76.84%> (+0.44%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

server/config/config.go
75.05% <ø> (ø)

server/region_syncer/server.go
83.08% <ø> (-0.13%)
:arrow_down:

server/schedule/opt/opts.go
100.00% <ø> (ø)

tests/cluster.go
80.78% <0.00%> (-0.88%)
:arrow_down:

server/api/scheduler.go
48.63% <50.00%> (+0.04%)
:arrow_up:

server/api/unsafe_operation.go
55.55% <55.55%> (ø)

server/schedule/operator_controller.go
84.72% <55.55%> (+0.71%)
:arrow_up:

server/schedulers/grant_hot_region.go
56.28% <56.28%> (ø)

server/cluster/coordinator.go
75.10% <64.28%> (+1.78%)
:arrow_up:

server/schedule/checker/priority_inspector.go
81.08% <66.66%> (ø)

... and 75 more

Continue to review full report at Codecov.

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


feat : Deferred rendering

Add Geometry Pass and Ligthing Pass in order to have more performance while having a lot of lights
Combine Deferred rendering with Forward rendering to keep transparency
F5 to use the debug render mode (The order is Position -> Normal -> Diffuse -> Specular)
Lighting Pass is using a Clip space of a triangle instead of a quad to be more efficient
TODO Add emissive texture in deferred (and batch)

Should we wait for @MacXxs's approval before merging?

Should we wait for @MacXxs's approval before merging?

Yeah it should be better


Poll

Adds poll functionality to wid bot. Users can create polls with up to 4 custom named options (due to Discord constraints) and set a duration of up to 1 day. Votes are dynamically updated as users click on them.
Can potentially add anonymous voting or restricted voting.

WIP ideas so i dont forget because I am in bed

add more colors
allow users to clear their vote either via clear button or clicking the same vote twice
hours/minutes arguments
look into making it a persistent view so the poll doesn't break between restarts (would need some sort of data storage though)


Generated docs have full paths in module names

These paths should not appear in the generated doc website:

https://ipfs.github.io/interface-datastore

Fixed in master, feel free to re open if this still happens.
Thank you 🙏🏼

Fixed in master, feel free to re open if this still happens.
Thank you 🙏🏼


DECT 200 Temperature broken

Hey there,
thanks for your work on this!
It seems like in the most recent version DECT200's temperature readings are broken.
The switch itself seems to be working, however temperature readings are a constant 0.0 with no data points in the Fakegato history.

Nevermind, I debugged that thing and figured it out, it's worth fixing or at least documenting, but I'm not familiar with the codebase enough myself to do it quickly.
Basically what happened was that I forgot to replace the ain on first launch. While a subsequent change of the ain propagated to the switch, it was never checked for the temperature accessory (which continued to look for the 0123456.. one).

Yes, that's normal. Fakegato always checks the AIN address entered in the config.json. If this is changed, Fakegato looks for the new address.
It is "checked". But Fakegato has problems with multiple cached data in the accessories folder and it needs several minutes to refresh the data.
To fix this, i recommend to remove the accessory and re-add with correct AIN address


Outsource vos commands to cs_util

Summary
The vos (VIrtual ObServatory) commands in canfar.py are moved to the library cs_util. These are used also elsewhere.
Need to wait for v 0.0.3 of cs_util, https://github.com/CosmoStat/cs_util/pull/14, and https://github.com/CosmoStat/shapepipe/pull/606
Reviewer Checklist

Reviewers should tick the following boxes before approving and merging the PR.

[x] The PR targets the develop branch
[x] The PR is assigned to the developer
[x] The PR has appropriate labels
[x] The PR is included in appropriate projects and/or milestones
[x] The PR includes a clear description of the proposed changes
[x] If the PR addresses an open issue the description includes "closes #"
[x] The code and documentation style match the current standards
[x] Documentation has been added/updated consistently with the code
[ ] All CI tests are passing
[x] API docs have been built and checked at least once (if relevant)
[x] All changed files have been checked and comments provided to the developer
[x] All of the reviewer's comments have been satisfactorily addressed by the developer

v0.0.4 of cs_util needs to be released before this PR can be merged.

Done, should work now.


Simplify actor-critic with shared layers

The current implementation of ActorCriticBase makes it a bit trick to have custom actor and critic networks that have shared layers. This is because the instantiation of the networks happen in the ActorCriticBase class. You can probably get around it but it's very tricky. I'd recommend you pass in the actor/critic objects rather than the class types and let the user initialize them.

Thank you for the comment. Yes, we have that planned for actor-critic methods. Note that for value based methods, we do give the option to users to pass in a network instance.


Track max checkpoint in big query tables

Description
With this PR, we should be able to report max checkpoint watermark in bq tables which would be used to set up alerts on.
Test Plan
Running in test data pipelines and confirming it to be working

Approved


Cannot create new container with DB backup

On version <IP_ADDRESS>, I'm not able to create containers using my own backup. I'm running a script that has worked previously, so something must have changed in the code. Also, I think it's just aliases, but I get the same result using new-navcontainer or new-bccontainer. The database version and requested docker version are the same.
new-navcontainer -accept_eula -accept_outdated -containerName dev-wkep -imageName mcr.microsoft.com/businesscentral/onprem:cu2-w1 -updateHosts -includeCSIDE -enableSymbolLoading -doNotExportObjectsToText -licenseFile "\fs1\FTPRoot\BCDevLicenses\13.flf" -includeTestToolkit -includeTestLibrariesOnly -additionalParameters @('--storage-opt size=40G', '--volume c:\temp:c:\temp', '--env bakfile="c:\temp\WKEPDev.bak"')
NavContainerHelper is version <IP_ADDRESS>
Host is Microsoft Windows 10 Enterprise - 1903
Docker Client Version is 19.03.2
Docker Server Version is 19.03.2
Using image mcr.microsoft.com/businesscentral/onprem:cu2-w1-ltsc2019
Removing dev-wkep from hosts
Removing C:\ProgramData\NavContainerHelper\Extensions\dev-wkep
Creating Container dev-wkep
Version: 14.3.34444.0-W1
Style: onprem
Platform: 14.0.34251.0
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.17763.557 (ltsc2019)
Host OS Version: 10.0.18362.356 (1903)
The container operating system does not match the host operating system, forcing hyperv isolation.
Using locale en-US
Using hyperv isolation
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file \fs1\FTPRoot\BCDevLicenses\13.flf
Files in C:\ProgramData\NavContainerHelper\Extensions\dev-wkep\my:

AdditionalOutput.ps1
AdditionalSetup.ps1
license.flf
MainLoop.ps1
updatehosts.ps1
Creating container dev-wkep from image mcr.microsoft.com/businesscentral/onprem:cu2-w1-ltsc2019
d5fbebf6073109032008f03ba37713ea9adebbba09e46442451c5428c516ab16
Waiting for container dev-wkep to be ready
Initializing...
Starting Container
Hostname is dev-wkep
PublicDnsName is dev-wkep
Using Windows Authentication
Starting Local SQL Server
Starting Internet Information Server
Using Database .bak file 'c:\temp\WKEPDev.bak'
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Failed to start service 'Dynamics 365 Business Central Server [NAV] (MicrosoftDynamicsNavServer$NAV)'.
at , C:\Run\navstart.ps1: line 142
at , C:\Run\start.ps1: line 121
at , : line 1Error
Initializing...
Starting Container
Hostname is dev-wkep
PublicDnsName is dev-wkep
Using Windows Authentication
Starting Local SQL Server
Starting Internet Information Server
Using Database .bak file 'c:\temp\WKEPDev.bak'
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Failed to start service 'Dynamics 365 Business Central Server [NAV] (MicrosoftDynamicsNavServer$NAV)'.
at , C:\Run\navstart.ps1: line 142
at , C:\Run\start.ps1: line 121
at , : line 1
Initialization of container dev-wkep failed
At C:\Program
Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\ContainerHandling\Wait-NavContainerReady.ps1:44 char:17

...             throw "Initialization of container $containerName failed" ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Initialization ...dev-wkep failed:String) [], RuntimeException
FullyQualifiedErrorId : Initialization of container dev-wkep failed

Actually... just realized that it isn't pulling the same version. Apparently the cu2 tag isn't pulling the cu2 image listed on the Release Cumulative Updates page. https://support.microsoft.com/en-us/help/4470116/released-cumulative-updates-for-microsoft-dynamics-365-business. Trying again know with the explicit version tag (13.2.26556.0)...

Yep. The issue was in the cu2 tagging. Starts fine with the right image. Still, though, would be nice to know why the service tier failed to start.

When you have this scenario, you can probably use Get-NavContainerEVentlog to extract the event log and see the reasoning there.
If you want to make sure you get the right version, you should add 1810-cu2-dk or 1904-cu2-dk - these will always end up in the same version.

Ah, thanks. What does the 1810 and 1904 tie to? In general, I really find figuring out the right versions of things extremely confusing with BC, since the version numbers displayed in the application don't seem to tie to the released build numbers.


[SPARK-40510][PS] Implement ddof in Series.cov

What changes were proposed in this pull request?
Implement ddof in Series.cov, by switch to SF.covar
Why are the changes needed?
for API coverage
Does this PR introduce any user-facing change?
yes, ddof supported now
        >>> s1 = ps.Series([0.90010907, 0.13484424, 0.62036035])
        >>> s2 = ps.Series([0.12528585, 0.26962463, 0.51111198])
        >>> with ps.option_context("compute.ops_on_diff_frames", True):
        ...     s1.cov(s2)
        -0.016857...
        >>> with ps.option_context("compute.ops_on_diff_frames", True):
        ...     s1.cov(s2, ddof=2)
        -0.033715...

How was this patch tested?
added UT

also cc @HyukjinKwon

Merged into master, thank @HyukjinKwon @itholic for reivews!


Issue 1957

This change is

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-email/lib/test/util.js  2
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-content/tests/test-search.js  5
- packages/oae-email/lib/test/util.js  2
- packages/oae-version/tests/test-version.js  6

Clones removed
==============
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-email/lib/test/util.js  2
- packages/oae-version/tests/test-version.js  6

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-version/tests/test-version.js  6
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-email/lib/test/util.js  2
- packages/oae-version/tests/test-version.js  6

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-version/tests/test-version.js  6
- packages/oae-content/tests/test-search.js  5
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-version/tests/test-version.js  6
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-content/tests/test-search.js  5
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  187
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-preview-processor/lib/test/util.js  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-content/tests/test-search.js  5
- packages/oae-version/tests/test-version.js  6

Clones removed
==============
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  183

Clones removed
==============
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-version/tests/test-version.js  6
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-version/tests/test-version.js  6
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-email/lib/test/util.js  2
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-content/tests/test-search.js  5
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-util/lib/mq.js  -3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-version/tests/test-version.js  6
- packages/oae-email/lib/test/util.js  2
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-util/lib/mq.js  -3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-preview-processor/tests/test-previews.js  183
- packages/oae-version/tests/test-version.js  6
- packages/oae-content/tests/test-search.js  5

Clones removed
==============
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-activity/tests/test-email.js  -2
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-util/lib/mq.js  -3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/oae-email/lib/test/util.js  2
- packages/oae-version/tests/test-version.js  6

Clones removed
==============
+ packages/oae-preview-processor/tests/test-previews.js  -6
+ packages/oae-util/lib/mq.js  -3
+ packages/oae-preview-processor/lib/test/util.js  -1
+ packages/oae-util/tests/test-mq.js  -2
+ packages/oae-content/tests/test-search.js  -1

See the complete overview on Codacy


Maximum of 200 globally accessible variables allowed in rega scripts

Up to recent CCU firmware versions (2.27.8) the included ReGaHss only allows to define up to 200 globally accessible variables. As soon as one tries to define the 201st variable ReGaHss returns strange syntax errors.
See here for more information (german):
https://homematic-forum.de/forum/viewtopic.php?f=34&t=25388#p254999

fixed with latest commit (see b8696e7c6c56e79fab207f3712b177805cc1d429)


Both runs on M1 Max MacBook with Ventura, and default installation of ml-stable-diffusion.
Model Name:	MacBook Pro
  Model Identifier:	MacBookPro18,2
  Model Number:	Z14X0002GD/A
  Chip:	Apple M1 Max
  Total Number of Cores:	10 (8 performance and 2 efficiency)
  Memory:	32 GB
  System Firmware Version:	8419.41.10
  OS Loader Version:	8419.41.10

Chipset Model:	Apple M1 Max
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	32
  Vendor:	Apple (0x106b)
  Metal Support:	Metal 3
![randomSeed_93_computeUnit_ALL_modelVersion_CompVis_stable-diffusion-v1-4](https://user-images.githubusercontent.com/3430712/205510539-7aeccfa0-75bb-491b-a100-176d19ac5731.png)
![randomSeed_93_computeUnit_CPU_AND_GPU_modelVersion_CompVis_stable-diffusion-v1-4](https://user-images.githubusercontent.com/3430712/205510545-b1e08456-cc10-49cd-b43e-3527f2f6d8c3.png)

Thank you.

I'm on 13.3, and I'm also facing this issue.

You must upgrade to macOS 13.1 beta to use GPU

@hirakujira  where to get this information?


Consider refactoring genotype column

Currently, snps normalizes data into a dataframe with four columns named rsid, chrom, pos, and genotype.
genotype can either be np.nan or a string of length 1 or 2. For autosomal SNPs and the X chromosome, the genotype is always a length 2 string. See #43.
The Y chromosome and mtDNA alleles are often strings of length 1; however, SNPs in the pseudoautosomal region on the X and Y chromosomes often have two alleles reported.
So, to better handle various numbers of alleles reported for the X, Y, and mtDNA chromosomes, consider refactoring the genotype column into allele1 and allele2.
Note that this would also more naturally support phased genotypes (vs. indexing a length 2 string genotype), wherein allele1 could be alleles on one chromosome, and allele2 could be alleles on the other. See #44.

Hi @willgdjones, what are your thoughts on this?

This seems like a sensible approach 👍 . We have just encountered the issue you describe in #43 ourselves in fact with Sano genotype data files where the X chromosome is duplicated for male samples.

Hi @apriha - were you in the midst of tackling this? This is functionality that will be soon be important for us so I'm considering jumping in on this.

In fact - it is more #43 that is directly relevant for us so I will look to fix that first.

Hey @willgdjones , I started looking at this as part of #44 and plan to push some parsing updates related to this soon.
I was just thinking - perhaps for backwards compatibility, we can also on the fly optionally generate the current data frame structure (i.e., with the genotype column as described above) when requested, while using allele1 and allele2 in the underlying structure.

I like that suggestion about keeping the genotype column for backward compatibility.


kyleschnirring answering the final questions

Thanks for everything. I had a great time.

Thank you for coming, and thank you for the feedback!


Upgrade build system

Need to look into this.
 No name was provided for external module

Resolved in 63d9a55


publish for Scala 3.0.0-RC3

needed for downstream http4s

I'll try to get to this tonight.

well, I tagged the release from the UI assuming that would work as well as pushing (I don't have my git credentials on this machine), and that didn't work...
I looked for a way to manually trigger the publishing action, but I can't see that....
I'll try to do it the old fashioned way tonight. Sorry for the delay.

okay, the action is running: https://github.com/typelevel/cats-parse/actions/runs/818748614

seems the publish worked.
Closing for now. Please reopen if there is a problem.


RFE: read Slurm AdminComment field during sacct queries

NERSC systems populate the Slurm AdminComment field in sacct queries with information about the job that ran. We would like to have a ReFrame test that ensures that this field is being populated correctly. However it seems that ReFrame ignores this field during its sacct queries while it waits for a job to finish.
Is it possible to capture this field, maybe with an optional flag (disabled by default, if that makes it less disruptive), and store the data in that field in a variable like self.AdminComment or something like that?

Hi @vkarak - thanks for the quick reply! I will try your suggestion and let you know if it is sufficient.
Sorry I have been slow to test the MRs that you've created in response to my several RFEs recently; trying to catch up in the next few weeks.

Sure, no problem!

Hi @bcfriesen is this issue still relevant?

Hi @vkarak, sorry I forgot about this issue - I think we have what we need, so this can be closed. Thanks!