text:
Issue #1 fix build

Problem:
This new package did not build.
Solution:
Setup vagrant and travis build mechanisms similar to libuavcan.
Testing:
Built and flashed. Verified olimex board worked.

@thirtytwobits Would you be interested in contributing an example for a PWM extender using that board (or any other)? Essentially a UAVCAN to PWM converter. I believe this would be instrumental in getting more adoption of the protocol. Given the configurability of PX4 it might be also worth looking into building a slave device using the existing PX4 driver infrastructure. The flight control apps could be completely disabled.

@LorenzMeier is this what you're looking for? https://kb.zubax.com/x/PQB8

Yes, but I would like to make it easier to access - so a dedicated build for it and preferably a dedicated low-cost board with the right connectors.

@pavel-kirienko how do I setup travis for this repo?

Log into Travis, select the UAVCAN account (you're an admin, so you should have access there), find the repo and enable it (which I just did). Then add .travis.yml (you did that already). I'm going to force a rebuild now.

Okay. Looks green. Let me know if I can merge this. Also, is this pattern okay to apply to the remaining driver repos? My Makefile hackery isn't perfect since there's no good correlation between the include.mk rule from libuavcan and the state of the git repo that the rule clones. CMake does a better job of this but it's not perfect either. Perhaps it's time to talk about conan.io? Not sure what dronecode is doing for dependency management?

Also, is this pattern okay to apply to the remaining driver repos?

Yes, I think so. I think we could also check out not just the master of libuavcan, but the latest release, for extra robustness. Check this out [pun not intended]: https://stackoverflow.com/questions/17414104/git-checkout-latest-tag

Perhaps it's time to talk about conan.io?

Finally I meet this thing in the wild. I first heard about it on some C++ conference years ago and I thought the day will never come.


text:
Words of encouragement

Your final report is very well done! Congrats!

Thanks! @garyzhubc

source: gharchive/issue

authors: garyzhubc jnederlo

license: MIT

license_type: permissive

license_source: github-api


text:
Peer Review - Mo Garoub

Dear Group 21,
It was a pleasure reviewing your project. I must say, I enjoyed reading the EDA report and learned a lot from it.
Please allow me to share review with you all:
Documentation

The project is properly documented and very clear to understand.

Code

The code is readable and reproducible. Overall the scrip looks great.

Analysis and reasoning

The EDA report is well written. The analysis look great to me. I liked the approach of the storytelling in your report. It was easy to follow and I appreciate all the details.

Communication

The report was clear and easy to follow.

Suggestions

The link provided for the final report is not updated. Perhaps you made few changes and forgot to update the README.md
Listing the important features only instead of all the features in the README would be better in my opinion.
Add figures numbers for easy references
The report is missing the reference section (link the .bib under analysis)

All in all, great job! I'm impressed with the quality of the produced report. Looking forward to reading the final report next week.

Thank you for the review!

Thank you for taking time to give us feedback!

Mo thank you very much for your suggestions! The readme and the report have finally been updated with the correct link and figure numbers. We still consider it important to mention all features in the readme as we´ve seen is a common practice, nonetheless, we added where the feature was going to be used or dropped in the machine learning model.
Again thank you for uplifting our spirits with the nice response and for the useful feedback.

authors: GuanshuTao YikiSu ansarusc mgaroub


text:
To-do

[x] team work contract
[x] add contributors to README.md
[x] Edit CONDUCT.md
[x] edit CONTRIBUTING.md to reflect your strategy
[ ] edit README.md
[ ] function specification

Next meeting: Friday 1:00p.m.
zoom link; TBD


text:
🛑 Student Media - Motley is down

In 9cee6ab, Student Media - Motley (https://motley.ie) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Student Media - Motley is back up in a6f79b4 after 6 minutes.

repo: UCCNetsoc/upptime


text:
Add documentation

A really lazy way: paddyroddy/python-template#9 (+ paddyroddy/python-template#10 + paddyroddy/python-template#11) as I'm an idiot) which allows you to just use github-pages deploying from a gh-pages branch with these settings

A better example that I just did looks like: https://astro-informatics.github.io/sleplet/

Decision
We will move to mkdocks. This should go green again.

FWIW I'm 👎 on making sphinx amber - in my opinion it's more complicated than mkdocs, but there are advantages such as:

More widely used by scientific Python projects
A wider range of plugins to work with documenting Python libraries (e.g. sphinx-gallery, sphinx-automodapi)

So I think worth keeping both mkdocs and sphinx as green, but explaining briefly the different use cases for them?

MkDocs also has a wide range of plugins: https://github.com/mkdocs/catalog

🟢 At least one person in ARC uses this. We actively recommend using it above other tools. It is the single recommended tool for a given purpose.
🟠 We don’t discourage using this, but it may duplicate functionality of a green tool.

I don't think we should regularly "double-green" things. Especially not when we're going to include one in the template.
So I would demote one of the two to amber (we don't discourage it!) and have the simplest(?) most beginnerfriendly-est(?) be the recommended one which is also in the template.
From memory, the arguments in favour of mkdocs were:

simpler,
markdown out of the box.

And in favour of sphinx:

widely used.

Specifically against sphinx:

the need to use plugins to get many features that we want by default,
rst is dead, long live markdown.

Specifically against sphinx:
the need to use plugins to get many features that we want by default,
rst is dead, long live markdown.

I think the first (need to use plugins / extensions) equally applies to Mkdocs as for example there is no built-in support for generating API documentation which I would say is something we would pretty much always want by default (and while autodoc is an extension in Sphinx it is maintained by the core Sphinx team).
With regards to the latter - there is decent Markdown support in Sphinx, see for example this guide and autodoc2 extension which provides support in docstrings. While I personally prefer writing documentation in Markdown because of familiarity, I think there are good arguments against having it as the default given the lack of standardization of Markdown, greater complexity in parsing it (and so more edge cases where you get unexpected formatting / differences between implementations) and the requirement to have specific syntax extensions to support the variety of directives needed when writing documentation (rather than general purpose text formatting provided by most Markdown flavours) as provided by MyST Markdown (https://mystmd.org/).
I think also the 'Mkdocs is simpler' is partly subjective - I've set up a lot of projects with Sphinx docs and after getting over the initial learning curve it was pretty easy to work with for basic use cases of generating API documentation plus a few top-level documentation pages. I think it gets more complex when you start to use lots of plug-ins, but that's opt-in.
Overall I don't have a strong preference between Sphinx and Mkdocs, I think both are great tools and would be happy with recommending either.

At least one person in ARC uses this

Any ARC projects using MkDocs? I can think of 3 using Sphinx.

after getting over the initial learning curve

This is enough of a reason against, seeing as we are aiming at beginners...

Any ARC projects using MkDocs? I can think of 3 using Sphinx.

The Heracles Euclid project (repo private)
SRR XNAT
...

I'm sure @p-j-smith is doing some too? There are probably others I'm forgetting.
I think what annoys most about sphinx is the amount of boilerplate the comes with it, e.g. Makefile, etc.

For the purposes of illustrating that setting up Sphinx doesn't require much boilerplate (no Makefiles present 😛) and would be simple for a user to set up (no additional steps compared to current use of cookiecutter) I've opened a PR at #318 which shows how we could add autogenerated docs using Sphinx to template

I think I vote for MkDocs → 🟢  and Sphinx → 🟠 .
Having used the latter quite a lot, I wouldn't say it's particularly "I don't care about configuration, please just set it up for me" -friendly. Which, we should remember, is our audience.
We can write some caveats into our recommended tooling website.

I don't think we should regularly "double-green" tools that 100% overlap functionality. Especially not when we're going to include one in the template.

👍 , my bad for not reading our own definitions of red/amber/green

the need to use plugins to get many features that we want by default,

What features are you thinking of that ship with mkdocs by default, but need a plugin in Sphinx?

seeing as we are aiming at beginners...

While beginner-freindliness is important I think is not the only consideration. For example I think using tools that are common in other open source Python projects (to avoid having to relearn when hopping across projects), and using tools that are commonly used across ARC are also important considerations.
I think Matt's PR shows that sphinx doesn't have to have a lot of boilerplate? So I'd medium-hard vote for MkDocs → 🟠 and Sphinx → 🟢.

What features are you thinking of that ship with mkdocs by default, but need a plugin in Sphinx?

For one that you need a plugin to use markdown I believe?
Also navigation menu in MkDocs is just done with the following (not saying this syntax is nice, just showing it works out of the box)

To make a reasonable looking website for SRR I only installed mkdocs, mkdocs-include-markdown-plugin (to include the project README.md), and the thme mkdocs-material. It really is that simple.

For the purposes of illustrating that setting up Sphinx doesn't require much boilerplate

It has:

configuration from a python file rather than a YAML (only benefit I can see if having access to Python for updating some bits)
an empty _static folder to be committed
using RST (which many users won't know, i.e. me)
a command so complex you're having to abstract it behind tox, rather than mkdocs serve

Other than your familiarity with it, and the fact that you both don't think any open source projects use MkDocs. I don't know how you can underestimate the complexity and confusion it will give new users - which, like it or not, will be many of our user base. I appreciate you might be long-term sphinx uses, but I've only used it in the last year or two, and my eyes were opened upon discovering MkDocs. I'm not saying it's perfect, but I see little reason for me to use sphinx other than in a pre-existing project.

FWIW I'm heavily in favour of MkDocs → 🟢 and Sphinx → 🟠 based on how we define the traffic system and comments above. However, I do think it should be documented that many projects do and will continue to use sphinx.

I do also fear that #318 being worked one will mean it gets merged. For a fair comparison, an mkdocs PR could also be made.

Can you link to a project that uses mkdocs so we can make a comparison with how complicated the setup/config is?

the fact that you both don't think any open source projects use MkDocs

Please can we keep discussion civil! In my experience most scientific Python projects do use sphinx - I'm happy to be be shown otherwise though.
I do agree that mkdocs has some nice advantages over sphinx - but I still think sphinx has some nice advantages over mkdocs. In my (quick, biased) opinion sphinx advantages outweigh mkdocs advantages, but I think the best way forward here would be to collaboratively come up with a table of advantages for each one, then we can come to a more considered consensus, and perhaps involve a wider set of folks in the decision?

Can you link to a project that uses mkdocs so we can make a comparison with how complicated the setup/config is?

The problem with the ones I've used are ARC projects that are private, so you won't have access :(

Also FYI I was being civil...

configuration from a python file rather than a YAML (only benefit I can see if having access to Python for updating some bits)

Being able to doing things like access the dynamically created version as recommeded by setuptools_scm is I think a good argument of why using a Python file for configuration can be helpful.

an empty _static folder to be committed

Now removed thanks to @dstansby's comment.

using RST (which many users won't know, i.e. me)

There is no reStructured Text required in the example in #318 - everything is configured to use Markdown.

a command so complex you're having to abstract it behind tox, rather than mkdocs serve

The reason for abstracting behind tox is the same reason you run tests in tox - so you are building documentation in an isolated environment and specifying dependencies that need to be installed.
I also wouldn't say
sphinx-build -W -b html docs docs/_build/html

is particularly complex and mkdocs serve is not the equivalent command - that would be mkdocs build which similarly has a range of options you can specify. Here actually we could just use
sphinx-build docs docs/_build/html

as -b html is equivalent to the current default behaviour and -W is just to get stricter checking by having warning enforced as errors.

I do also fear that https://github.com/UCL-ARC/python-tooling/pull/318 being worked one will mean it gets merged. For a fair comparison, an mkdocs PR could also be made.

Definitely no expectation that because I've worked on this we go with Sphinx, as I've said already here and on the PR.

Just to close the loop (sorry for the noise)

the need to use plugins to get many features that we want by default,

What features are you thinking of that ship with mkdocs by default, but need a plugin in Sphinx?

I was thinking mostly of autodoc but might have misremembered and cede to Matt's comment.

Anyone used mkdocstrings cross-references?

I've used
- mkdocstrings:
    handlers:

syntax before. But that was in the Heracles code that they've removed my access to. I don't know what I was using it for though, could well have been a different feature.

FYI from SRR
I have this GitHub Action (which checks that all files are mentioned in the nav section
---
name: MkDocs

# yamllint disable-line rule:truthy
on:
  push:
    branches:
      - main
      - release
      - renovate/**
  pull_request:
    types:
      - opened
      - ready_for_review
      - reopened
      - synchronize

concurrency:
  cancel-in-progress: true
  group: >-
    ${{ github.workflow }}-
    ${{ github.event.pull_request.number || github.ref }}

jobs:
  documentation:
    if: github.event.pull_request.draft == false
    runs-on: ubuntu-latest
    steps:
      - name: Checkout source
        # yamllint disable-line rule:line-length
        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4

      - name: Set up python
        # yamllint disable-line rule:line-length
        uses: actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c # v5
        with:
          python-version: 3.x
          cache: pip
          cache-dependency-path: requirements.txt

      - name: Install dependencies
        run: python -m pip install --requirement requirements.txt

      - name: Run MkDocs
        run: mkdocs build --strict

and
This is the config file, using various features. The nav section is horrible due to how many pages that project has.
---
copyright: Copyright © 2023 - 2024 ARC
edit_uri: edit/main/docs
repo_name: UCL-MIRSG/UCLH-MPBE-SRR-XNAT
repo_url: https://github.com/UCL-MIRSG/UCLH-MPBE-SRR-XNAT
site_author: UCL ARC
site_name: UCLH MPBE SRR XNAT

extra:
  generator: false
  icon:
    edit: material/pencil
    repo: fontawesome/brands/github
    view: material/eye

markdown_extensions:
  - pymdownx.superfences:
      custom_fences:
        - name: mermaid
          class: mermaid
          format: "!!python/name:pymdownx.superfences.fence_code_format"

nav:
  - Home: index.md
  - Background:
      - background/index.md
      - Existing Pipeline:
          - background/existing_pipeline/index.md
          - SRR Processing Flowchart: >-
              background/existing_pipeline/SRR_pipeline_overview.md
  - Development:
      - development/index.md
      - Ansible: development/ansible.md
      - Docker: development/docker.md
  - Quality Management System Documentation:
      - qms/index.md
      - Software Development Plan:
          - qms/software_development_plan/index.md
          - System Overview: qms/software_development_plan/system_overview.md
          - Software Development Overview: >-
              qms/software_development_plan/software_dev_overview.md
      - Software Requirement Analysis:
          - qms/software_requirement_analysis/index.md
          - Overview of Product Use: >-
              qms/software_requirement_analysis/overview_of_product_use.md
          - User Requirements Process: >-
              qms/software_requirement_analysis/user_requirements_process.md
          - Verification and Validation: >-
              qms/software_requirement_analysis/verification_and_validation.md
          - Appendices: qms/software_requirement_analysis/appendices.md
      - Software Architecture Design:
          - qms/software_architecture_design/index.md
          - Software Architecture Document: >-
              qms/software_architecture_design/software_architecture_overview.md
      - Software Detailed Design:
          - qms/software_detailed_design/index.md
      - Software Unit and Integration Testing:
          - qms/software_unit_and_integration_testing/index.md
          - qms/software_unit_and_integration_testing/srr_testing.md
          - qms/software_unit_and_integration_testing/unit_test_protocols.md
      - Software System Testing and Validation:
          - qms/software_system_testing_and_validation/index.md
      - Software Risk Management:
          - qms/software_risk_management/index.md
      - Software Change Control and Problem Resolution Processes:
          - qms/software_change_and_problem_processes/index.md
      - Software Release Process:
          - qms/software_release_process/index.md
      - Post Market Surveillance and Software Maintenance:
          - qms/software_maintenance/index.md

plugins:
  - include-markdown
  - search

theme:
  features:
    - announce.dismiss
    - content.action.edit
    - content.action.view
    - content.code.copy
    - header.autohide
    - navigation.expand
    - navigation.footer
    - navigation.indexes
    - navigation.tabs
    - navigation.top
    - navigation.tracking
    - search.highlight
    - search.suggest
    - toc.follow
  name: material
  palette:
    # palette toggle for dark mode
    - scheme: slate
      toggle:
        icon: material/brightness-4
        name: Switch to light mode
    # palette toggle for light mode
    - scheme: default
      toggle:
        icon: material/brightness-7
        name: Switch to dark mode

validation:
  absolute_links: warn
  omitted_files: warn
  unrecognized_links: warn

These are the only files. The rest are markdown files in a docs folder. I use mkdocs serve locally to visualise, and mkdocs build in CI.

Now added an equivalent PR #319 adding MkDocs support to template
Overall I would say similar level of complexity for the user. In both cases if they wanted add a new page they would create a Markdown file in docs directory, and have it reference in the top-level navigation / table of contents. I'm not entirely sure if mkdocstrings would automatically create new entries in API reference for each sub-module in the package or only for things directly exposed in top-level __init__.py.
MkDocs supports Google, NumPy and Sphinx style docstrings - I've currently used the Google style.
The intersphinx equivalent seems to work well.

For automatically generating API docs in sphinx I've used https://numpydoc.readthedocs.io/en/latest/index.html +  https://github.com/astropy/sphinx-automodapi with NumPy style docstrings.
I'm now coming round to the list of MkDocs features outweighing the wide usage of sphinx, so happy for it to go 🟢 and the MkDocs PR to be merged 👍
I think worth having a discussion about which docstring style to recommend/use, but that's definitely for another issue 😄

authors: dstansby matt-graham paddyroddy samcunliffe

repo: UCL-ARC/python-tooling


text:
Additional detail for map search results

Would be good if we could display richer detail of a selected search result. We're using maplink api, so I'm not sure how rich our data can really be without an overhaul. But getting started on something would be nice. Having this slide up and down to reveal would be nice too.
Uses:
Parking Type Display
Dining Detail (hours?)
Labs (Printers/hours?)

As mentioned above, MapLink does not support rich enough data to accommodate most of what is seen above in the screenshots. We will revisit when the VirtualMap API is available.

repo: UCSD/campus-mobile

license: mit

license_source: bigquery


text:
release-update: upgrade hwloc to 2.8.0

Strip out references in hwloc/config/hwloc.m4 to a file that does not exist
utils/hwloc/test-build-custom-topology.sh.in
In order to update to latest stable hwloc 2.8.0

Not hard to reproduce the build error, but the output is so cryptic I can't tell what the actual issue is.

Looks like -Werror=vla is getting passed down into the compiler used by the configure tests inside hwloc.  This causes a warning about a variable-length array used in the code in their C99 tests to be treated as a failure.  Which means hwloc thinks we aren't using a C99 compiler and so it bails out.

Looks like -Werror=vla is getting passed down into the compiler used by the configure tests inside hwloc. This causes a warning about a variable-length array used in the code in their C99 tests to be treated as a failure. Which means hwloc thinks we aren't using a C99 compiler and so it bails out.

I can reproduce this locally. Can we just drop the -Werror=vla?

Strip out references in hwloc/config/hwloc.m4 to a file that does not exist
utils/hwloc/test-build-custom-topology.sh.in In order to update to latest stable hwloc 2.8.0

The update-hwloc.sh script handles these. When a new error appears during an update, you can add it to one of the lists at the top of the file.

Looks like -Werror=vla is getting passed down into the compiler used by the configure tests inside hwloc. This causes a warning about a variable-length array used in the code in their C99 tests to be treated as a failure. Which means hwloc thinks we aren't using a C99 compiler and so it bails out.

In the past, we've patched hwloc to disable this configure test. The instructions at the end of update-hwloc.sh say to review the git history of hwloc/ and squash any such patch commits into the update. The commit in question no longer applies cleanly so I kept an updated one separate this time.

Strip out references in hwloc/config/hwloc.m4 to a file that does not exist
utils/hwloc/test-build-custom-topology.sh.in In order to update to latest stable hwloc 2.8.0

The update-hwloc.sh script handles these. When a new error appears during an update, you can add it to one of the lists at the top of the file.

Looks like -Werror=vla is getting passed down into the compiler used by the configure tests inside hwloc. This causes a warning about a variable-length array used in the code in their C99 tests to be treated as a failure. Which means hwloc thinks we aren't using a C99 compiler and so it bails out.

In the past, we've patched hwloc to disable this configure test. The instructions at the end of update-hwloc.sh say to review the git history of hwloc/ and squash any such patch commits into the update. The commit in question no longer applies cleanly so I kept an updated one separate this time.

All good points, I failed to understand all the elements of the script and the followup commits.

source: gharchive/pull-request

repo: UIUC-PPL/charm


text:
Performance

Original issue: https://charm.cs.illinois.edu/redmine/issues/415

Profile and improve the performance of projections.  Look into using hardware acceleration for drawing.

Original date: 2016-09-21 18:26:21

Break this up into subtasks with this as a parent task so that achievable and measurable units of progress can be made and tracked.

authors: ericjbohm rbuch

repo: UIUC-PPL/projections


text:
feat(DTFS2-6863): added table headers for amendment tasks

Introduction :pencil2:
Table headers missing when facility is amended.
Resolution :heavy_check_mark:
Add table headers for each section when facility is amended.

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (6da84ce) 21.88% compared to head (baf8fa6) 22.40%.
Report is 46 commits behind head on main.

Files
Patch %
Lines

dtfs-central-api/src/drivers/db-client.js
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2444      +/-   ##
==========================================
+ Coverage   21.88%   22.40%   +0.51%
==========================================
  Files        1132     1135       +3
  Lines       27048    27205     +157
  Branches     4447     4470      +23
==========================================
+ Hits         5920     6094     +174
+ Misses      18403    18386      -17
  Partials     2725     2725

Flag
Coverage Δ

api-test
0.48% <ø> (ø)

ui-test
65.45% <ø> (+0.31%)
:arrow_up:

unit-test
4.34% <0.00%> (+0.55%)
:arrow_up:

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

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

authors: codecov-commenter vamshidharukef


text:
DTFS2-User-Passwords : Password module

Introduction
User password management module had myriad of bugs ranging from self user password reset to admin password creation. This PR aims to mitigate all those known bugs reported alongside with other discovered UI bugs. Following cross routes improvements have been accompanied in this PR:

GDS UI standardisation.
Enhanced abbreviations.
Meaningful re-directions.
Updated mock data.
Updated Jest test cases.
Updated Cyperss E2E tests.
Improved documentation.
Lint fixes.

User actions
1. Password reset

currentPassword field check, due to unified function currentPassword field is not applicable for password set by the user upon admin account creation.

2. Password update

Removal of password and passwordConfirm attribute.
loginFailureCount set to 0.
passwordUpdatedAt set to password update timestamp.
Password update notification.

Admin actions
1. Account creation

CSRF token removal.
User existence check.
Null field checks.
Improved error handling.

2. Account password

Removal of password and passwordConfirm attribute.
loginFailureCount set to 0.
passwordUpdatedAt set to password update timestamp.
Password update notification.
Introduction of adminUpdateRules for ruleset operations.

We need E2E tests & UI tests. I've left a few comments as well

Added.

We need E2E tests & UI tests. I've left a few comments as well

Have added and updated.


text:
Fix case owner not being indexed properly upon changing case owner

Description
This addresses a bugthat happens when changing case owner, the investigation is not re-indexed breaking the search by "My team" or "Me" showing investigation owned by other teams or owned by users in other teams.

Checklist:

[X] Have you documented your changes in the pull request description?
[ ] Has acceptance criteria been tested by a peer?

 'My team' case owner search filter also showing cases you are added to in results list

repo: UKGovernmentBEIS/beis-opss-psd


text:
allow CI checks to be run manually with workflow_dispatch

Avoids opening a PR just to get the workflow to run on a new branch
This PR contains:

[ ] New features
[x] Changes to dev-tools e.g. CI config / github tooling
[ ] Docs
[ ] Bug fixes
[ ] Code refactor

I personally would find this useful in my fork of the repo -- and maybe you will like it too

Thanks!

authors: jjallaire tadamcz


text:
Remove VSCode configs and add IDE related files to gitignore

.vscode/ might have been committed by accident as it's not usually included in packages. Deleting the VSCode configs and adding IDE related files to .gitignore.

That is actually committed on purpose to help enforce coding and tooling conventions. See discussion here: https://stackoverflow.com/questions/32964920/should-i-commit-the-vscode-folder-to-source-control
It's possible that there is too much stuff in there (i.e. some settings that are inconvenient to have imposed on every user) but the intention is very much to give everyone a standardised and properly dialed VS Code for working on the project.

Not everybody uses VSCode, shall we move to a universal editor config that works with most IDEs? See EditorConfig (it works natively with PyCharm and VisualStudio and needs a plugin for Atom, Eclipse, Sublime, VSCode among others). Let me know what you think and I can port the VSCode specific settings to an .editorconfig file.

Yes, I would be totally down for that! I might suggest that we still keep the .vscode stuff though as if people don't install the VS Code Extension for EditorConfig they won't get the settings. Also, some of the settings are really about configuring MyPy and Ruff (not just stuff like indent, etc.) -- not sure whether EditorConfig covers setting arbitrary VS Code settings? (i.e. settings of VS Code extensions)

authors: alexandraabbas jjallaire-aisi


text:
draco-corrcal pipeline

We want to develop a pipeline that use draco, corrcal, and in-house codes to simulate, calibrate, calculate power spectrum, and perform relevant analysis and visualisation.
The pipeline will consist of Python modules and a Jupyter notebook. The latter will be primarily for analysis and visualisation. This pipeline will serve as our development platform for #7, and will fulfil #3, #5, and #10.
For convenient, we will develop and test this pipeline with a simple set of simulations, but the pipeline will be scalable:
Simulation Components

[ ] 2x2 array
[x] Somewhat realistic beam, e.g. airy beam
[x] A few point sources
[x] A few time
[x] A few frequency
[ ] 21 cm

Analysis Components

[ ] Functions for applying and visualisation of gain solutions
[ ] Functions for analysis and visualisation of visibility
[ ] Functions for power spectrum calculation and visualisation

@Zahra-Kader @dcrichton Are you on board? Any suggestions or comments?

Yes, I'm on board. I will get started on this today and list any questions/concerns that I have.

Sounds good to me. Although, given the way draco works with caput-pipeline, a jupyter notebook might be a bit annoying for some aspects.

@dcrichton Can you elaborate? My thought is that this notebook would not just be a pipeline that simply run the codes. We will also use it for documentation, analysis and visualisation. If you mean that we might have to execute Python scripts outside of the notebook and read in thee data, that should be easy to do with magic commands.

Yeah exactly. It will depend on some configuration files, external script runs and generated outputs which means it won't be super self-contained in a notebook. I think it's fine to use terminal calls or magics in the notebook for this but you'd just want to make sure all the additional files are kept in sync or just have the notebook generate the configs too.

@Zahra-Kader I suggest making a new directory in the repo for the notebook, associated scripts, and all input and output files that they produce. It might also be handy to try other IPython magics. I think %%writefile is a particularly useful one, so you develop the content of your script as a cell in a notebook, save it out into a file, and in the next cell you can run it with %run or %%bash or something else. This page lists all of the magic commands https://ipython.readthedocs.io/en/stable/interactive/magics.html.

I updated the first post to re-scope and include points from today discussion

I uploaded some details of the working pipeline. So far it can be used to generate corrected visibility timestreams after computing recovered gains with CorrCal. The code currently is not set up to do power spectrum estimation. I need sidereal streams to do that. I still need to show the results of this in a notebook.

@Zahra-Kader Great! I see you put the gain fitting function in the Python file. That's a good thing. Keep it this way while you are still developing the codes. It will become clear if it'd better be put somewhere else.
For getting the sidereal stream, it is just a matter of simulating visibility time stream from the same LST right? Correct me if I am wrong. Do you foreseen any sort of "utility functions" that we might need?

With draco, you can get sidereal streams, and from that, the timestreams are generated (see draco/synthesis/stream.py). I currently set up the code to return gain solutions in the shape (nfreq, 2*Ndish, ntime) which is correct for timestream data. I would need to change this if I am to use sidereal streams. I'll look into this more a bit later. I think for now I'll just focus on making sure everything works with the calibrated visibility timestreams.

authors: Zahra-Kader dcrichton piyanatk


text:
Side Bar

I found this side bar that integrates with google maps and thought it might be better than the current panel.
sidebar v2
I'll look into it some more, just wanted to put it out there.

I have started implementing this in my fork; check it out:
Parcel Assessment Tool (my fork)
I posted something similar to this on slack, but I'll post it here too:
I'm looking for ideas on how to reformat the data to follow the new paradigm this bar presents.
I can add new buttons to the menu, so I was thinking the buttons could lead to different tools ie. the building envelope is one tool, the info viewer is another tool, etc.
This might require a reversion to the old single parcel at a time method for showing info as the old tab system doesn't look/work as well.
I also want to add a help pane to the panel that can include info on zoning definitions and such to help the user.

Josh. I understand the question but don't see where the Folder works now. That is, i can select a site and it pops up with Add to Folder but there is

no folder view.

HI Jim, what browser are you using? It works for me on firefox and chrome on Windows 10 and Ubuntu.

This transition is still a WIP, I haven't made it automatically open when a building is added yet because it was causing issues. I'm looking into what's causing the issue, I should have it at least back to its original functionality soon.

Hi Josh. I’m using Firefox. Jim
James R. DeLisle, Ph.D.
Director, Lewis White Real Estate Center
Associate Professor, Henry W. Bloch School of Management
University of Missouri-Kansas City
5110 Cherry Street, Suite 217
Kansas City, MO 64110
Office: (816) 235-6288 / Cell: (913) 747-8580
Email contact: DeLisleJ@umkc.edumailto:DeLisleJ@umkc.edu
Personal JRD Website: www.JRDeLisle.comhttp://www.jrdelisle.com/
LinkedIn Contact Name: Jim DeLisle
[1LewisWhite_v1]                           Check out our new
Master of Entrepreneurial Real Estatehttp://bloch.umkc.edu/graduate-program/mere/default.aspx
(MERE) Fall 2015 Openings
From: Josh [mailto:notifications@github.com]
Sent: Sunday, September 20, 2015 3:22 PM
To: UMKC-Law/Parcel-Assessment-Tool Parcel-Assessment-Tool@noreply.github.com
Cc: DeLisle, James R. delislej@umkc.edu
Subject: Re: [Parcel-Assessment-Tool] Side Bar (#38)
HI Jim, what browser are you using? It works for me on firefox and chrome on Windows 10 and Ubuntu.
—
Reply to this email directly or view it on GitHubhttps://github.com/UMKC-Law/Parcel-Assessment-Tool/issues/38#issuecomment-141830982.

Josh. I'm using Firefox 38.2 on Windows 8.1. Jim

I tested it in Firefox 38.2 LTS and it is working as expected.

Josh. I just checked it and it works great. You have enough of the shell that some input from users would be great. Let's get Ben and Jonathan in on the review and refinement. We probably need to bring them up to speed on GitHub and Slack (me too). There are some navigation issues that we need to document for you as well as some definitions. For example, the Land Use should return a description or short name vs. number which is what you have also suggested.  The back button once you get to taxable value also needs some work but that's what we need to review to give you feedback. Great job.

I added some extra sections to the panels, they aren't filled in yet though.
On a side, I'm using icons from fontawesome for the buttons. If you see something you think would fit better for any of the sections, let me know. I can also use glyph-icons from bootstrap but I think it's just a subset of those available from font awesome anyway.

I also changed the orange in the bar to the blue I was using in the old panel. I'm open to other colors though.

authors: JRDeLisle QuestofIranon

repo: UMKC-Law/Parcel-Assessment-Tool


text:
Feat: Implement unique values legend on string properties in vectors (Issue #1146)

Thank you for submitting a pull request!
Description
Please describe what you changed briefly.
Type of Pull Request

[x] Adding a feature
[ ] Fixing a bug
[ ] Maintaining documents
[ ] Others ()

Verify the followings
Fixes #1146

[x] Code is up-to-date with the develop branch
[x] No build errors after pnpm build
[x] No lint errors after pnpm lint
[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check
[x] Make sure all the existing features working well

Changesets

[ ] If your PR makes a change under packages folder that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Refer to CONTRIBUTING.MD for more information.

repo: UNDP-Data/geohub


text:
Рефакторинг

Добавлен workflow, запускающей тесты и линтер (flake8 + mypy + isort). Код отредактирован , чтобы соответствовать линтеру.

Не актуально

repo: UNN-ITMM-Software/iOpt


text:
Add due date handling

Description:

Add a calendar date-picker for setting due dates.
Conditionally highlight tasks that are near/overdue.

Added a calendar date-picker for setting due dates, and conditionally highlighted tasks that are near/overdue.

Added a calendar date-picker for setting due dates, and conditionally highlighted tasks that are near/overdue.

repo: UPye/Taskinator


text:
View Validation Outcome Report

Feature Benefit
Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Monitoring Plan Requirements Package

Duplicate of #171

Duplicate of #171

authors: JorjaComer karenhwwoo

repo: US-EPA-CAMD/easey-ui


text:
CensoredData

Function title: CensoredDataSubstitutions or TransformCensorData?
Generate DetectionQuantitationLimitTypeName (and associated DetectionQuantitationLimitMeasure/MeasureValue and DetectionQuantitationLimitMeasure/MeasureUnitCode) and ResultDetectionConditionText from Result Value where needed
Depends on ResultsSpecialChars Function:

Convert Result Values that start with "<" into an appropriate Detection Condition and Detection Limit Value. That is: a Result Value of "<0.25" would be converted into a ResultDetectionConditionText of "Present Below Quantification Limit", a Nondetect Result Value of "0.25", and a DetectionQuantitationLimitTypeName of "Lower Quantitation Limit"

Two options (best for when <70% of data are censored):

Robust ROS [Regression on Order Statistics (ROS)] (for lower limits, use random number between detection limit and 0)
x times the detection limit

Notes about detection limit from Christy Meredith Montana DEQ
"If the ResultMeasureValue=NA, usually that means that the measurement is below the detection limit, not that there wasn’t a measurement. So I usually replace it with the detection limit or half the detection limit (Montana DEQ protocol). I’m not sure what other people do, but this functionality could be added".

FROM:
'Dennis Helsel' dhelsel@practicalstats.com
pauljulianphd@gmail.com
Lee, R. Lopaka rclee@usgs.gov
Glad you got in touch!  Yes, officially I'm retired as of this past April.  But I've kept my hand in the nondetects / WQ world a little bit, however.  I've been advising an international group of SETAC scientists on data analysis for censored data.  You'll see two results of that on the Videos section of practicalstats.com, a webinar presentation to Australian scientists titled "Two Things I've Learned After 43 Years of Applying Statistics to Environmental Science", and a webinar to the entire SETAC group on why better methods for censored data need to be used in WQ titled "The Cost of Complacency".  Both were given and recorded this past spring. Both might be of interest to your workgroup.
I've also continued to add a bit to the NADA2 package.  Paul has just posted a new version of NADA2 that includes a new function I wrote for trend analysis after adjusting for a covariate, a non-time variable like streamflow or depth to water. I hope to write a few more new functions in the coming year(s), at my own pace of course. The new version of
NADA2 includes a tutorial Paul and I wrote on stats for censored data, listed as a "vignette" -- that's the best place to start for your working group to learn about how NADA2 can be leveraged for their workflows.  It can be downloaded from the NADA2 page on the CRAN site and uses examples from the Nondetects And Data Analysis course I taught for over a decade, and which is now available online at practicalstats.com for free.  Perhaps someone in the working group might benefit from taking that course and reporting back to the others?  Or perhaps someone in the group already has taken it.
As far as a presentation, if you want someone to discuss the stats of the methods in NADA and NADA2, I'm probably your guy.  I'd do an online presentation; probably not one in person unless the location is somewhere I really want to go to (Charleston, SC, say). If instead you want someone to speak about programming and interfacing with the packages, Lopaka or Paul would be the ones to ask.
One of the nice things about retirement is that I avoid conference calls.  If the objectives of a call are laid out explicitly and a time limit for it set, a call might be OK.  For the topics of stats, what the packages do and why they're important, I'd prefer your workgroup instead put together questions and send them to me, and I'll answer them by email rather than a video call.  I find that more efficient. If the topic is the computer aspect of the TADA effort Lopaka and / or Paul will have to speak for their own time and interest.
Best regards, and best wishes on the work, Dennis Helsel

@ehinman can this be closed?

Mostly, yes. The basics are there to ID non-detects and use simple methods to fill them (x times detection limit, random number between detection limit and 0). However, we do not currently handle more complex approaches to handling nondetects that depend upon the detects in the dataset (Robust ROS, MLE, Kaplan-Meier), just offer suggestions in the summary. Should I create a new issue for this?

@ehinman awesome!!! let's use this issue for that & close this one

authors: cristinamullin ehinman

repo: USEPA/TADA


text:
Update spatial function to sf

The package current depends on sp and geos, which will be deprecated in Oct 2023. We need to update all spatial functions to sf.

I went through the code and removed any direct calls to sp or raster. The ll_ratio function still depends on geosphere::distVincentyEllipsoid, which imports sp.

repo: USFWS/fwspp


text:
Feed back on disclaimer

I installed sbtools on my Windows 7 USGS computer (R version 3.2.1). The disclaimer "This information is preliminary or provisional and is subject to revision..." is much longer than one line and I had trouble scrolling through it to read it all. Perhaps you add in some line breaks. (This is a Windows R problem more than anything else. If I recall correctly, emacs ess and OS X R all have word wrap.).

That's a great point. Thanks for the note!

fixed in #110

authors: lawinslow rerickson-usgs

repo: USGS-R/sbtools


text:
could we use sc_indicate to give us a hash table for several local files?

I love what sc_indicate produces from
8_drivers_munge_tasks:
    command: sc_indicate(I('8_drivers_munge/out/8_drivers_munge_tasks.ind'), hash_depends=I(TRUE), depends_target=I('8_drivers_munge_tasks'), depends_makefile=I('8_drivers_munge_tasks.yml'))
    depends:
      - ...

which is this:
8_drivers_munge/out/NLDAS_time[0.346848]_x[284]_y[144].csv.ind: a75f2789336c8626c2de19b7e72731f0
8_drivers_munge/out/NLDAS_time[0.346848]_x[250]_y[169].csv.ind: 88083431fb49a37316682b6eb0be3bed
8_drivers_munge/out/NLDAS_time[0.346848]_x[242]_y[177].csv.ind: ce6b055b602eb803d5d6ffdd013a9461
8_drivers_munge/out/NLDAS_time[0.346848]_x[244]_y[177].csv.ind: f798f371fe79f9d1cb0a10435204f0b4
8_drivers_munge/out/NLDAS_time[0.346848]_x[243]_y[179].csv.ind: 09e02bce6fb6c49275f8dd99fc300768
8_drivers_munge/out/NLDAS_time[0.346848]_x[246]_y[179].csv.ind: c28b43084a3ef4d7598f3e74b5368126
8_drivers_munge/out/NLDAS_time[0.346848]_x[260]_y[183].csv.ind: 51207ab200f6343a74b803c13854e627
8_drivers_munge/out/NLDAS_time[0.346848]_x[258]_y[187].csv.ind: 0a442d50e4c48e5b8dff89a6a5e87bb7
8_drivers_munge/out/NLDAS_time[0.346848]_x[255]_y[188].csv.ind: 07964a7212182889ce9f65566c716f2d
8_drivers_munge/out/NLDAS_time[0.346848]_x[221]_y[132].csv.ind: ffe4752c4dee581fe8738c80aeb8cf78
8_drivers_munge/out/NLDAS_time[0.346848]_x[344]_y[196].csv.ind: d37c564497dd708583f799a6aba46cd2

This is a nice hash table that we could use to hold the coordinates of one-to-many target inputs.  The target output would just be one file, this hash .ind file, but it points to the many files generated within a function that created it.
Here is a use-case:
I have a huge .nc file, and I need to write 2000 files from it. A normal scipiper workflow is to make a task table where each of those 2000 files is a task, and each of those tasks opens the .nc file, takes what it needs, closes the .nc, then writes the file. Trouble is, this is prohibitively slow. So, we need a way to open that .nc file once, take all 2000 files worth of data, write the files, then close the .nc file.
So, what I'd like to do is something like
sc_indicate(ind_file = 'example_many.ind', data_file = c('8_drivers_munge/out/NLDAS_time[0.346848]_x[344]_y[196].csv', '8_drivers_munge/out/NLDAS_time[0.346848]_x[284]_y[144].csv'))

Then 'example_many.ind' can be an input to a later function that wraps create_task_plan() where I can read that hash table, and use it to generate my task list.
Currently this doesn't work because data_file inputs are length 1, and the hash when you use data_file doesn't include the file name. Using depends_target would work, but I'd have to create a fake remake.yaml as a workaround.
Bad idea? We've used similar table outputs in the past (I think the internal analytics viz uses this principle w/ a .csv table).

Could look like this:
sc_indicate(ind_file = '', data_file = c('8_drivers_munge/out/NLDAS_time[0.346848]_x[344]_y[196].csv', '8_drivers_munge/out/NLDAS_time[0.346848]_x[284]_y[144].csv'))
$`8_drivers_munge/out/NLDAS_time[0.346848]_x[344]_y[196].csv`
[1] "35910bbf7e7522889e0ba36e590aadd0"

$`8_drivers_munge/out/NLDAS_time[0.346848]_x[284]_y[144].csv`
[1] "0823ba6a3db0073e2c6acb219c85887f"

sc_indicate(ind_file = '', data_file = '8_drivers_munge/out/NLDAS_time[0.346848]_x[344]_y[196].csv')
$hash
[1] "35910bbf7e7522889e0ba36e590aadd0"

I tried this out for my use-case, and it seemed to perform well. Instead of one task per cell feather file, I have one task per variable that writes all files and uses sc_indicate to generate a yaml that holds the filepaths and hashes for each of the files created. So a task looks like this:
  # --- cellgroup_time[0.346848]_var[tmp2m].yml --- #

  6_drivers/log/feather/cellgroup_time[0.346848]_var[tmp2m].yml:
    command: cubes_to_cell_files(target_name, cells = nldas_new_cells, out_dir = I('6_drivers/out/feather'),nc_dir = I('6_drivers/out/nc'),
       '6_drivers/log/nc/NLDAS_time[000000.024999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[025000.049999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[050000.074999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[075000.099999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[100000.124999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[125000.149999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[150000.174999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[175000.199999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[200000.224999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[225000.249999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[250000.274999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[275000.299999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[300000.324999]_x[221.344]_y[132.196]_var[tmp2m].nc.ind',
       '6_drivers/log/nc/NLDAS_time[325000.346848]_x[221.344]_y[132.196]_var[tmp2m].nc.ind')

and the output (truncated) looks like this (from 6_drivers/log/feather/cellgroup_time[0.346848]_var[tmp2m].yml) :
6_drivers/out/feather/NLDAS_time[0.346848]_x[311]_y[134]_var[tmp2m].feather: a3d9f6ae8f37d38f08482dfa1b44f7eb
6_drivers/out/feather/NLDAS_time[0.346848]_x[312]_y[134]_var[tmp2m].feather: 577628006d282c34877e226ee4b5592c
6_drivers/out/feather/NLDAS_time[0.346848]_x[313]_y[134]_var[tmp2m].feather: 40aa69b62af6e59cd1556d4d143efd43
6_drivers/out/feather/NLDAS_time[0.346848]_x[314]_y[134]_var[tmp2m].feather: b31f0b89139cfe663a8fe0a41c98e43e
6_drivers/out/feather/NLDAS_time[0.346848]_x[315]_y[134]_var[tmp2m].feather: 2aba97db3bbf86df8b36a5e6b16eaa6f
6_drivers/out/feather/NLDAS_time[0.346848]_x[316]_y[134]_var[tmp2m].feather: 00754639e2c94dae02f5b5e3ac1c235a
6_drivers/out/feather/NLDAS_time[0.346848]_x[317]_y[134]_var[tmp2m].feather: 0db990fab089f2f78bad66f099a7189d
6_drivers/out/feather/NLDAS_time[0.346848]_x[318]_y[134]_var[tmp2m].feather: 7a5b87b6bd97249222b5a705b8f87685
6_drivers/out/feather/NLDAS_time[0.346848]_x[319]_y[134]_var[tmp2m].feather: a8aaa04c25f566a4831d0d14c469b1e2
6_drivers/out/feather/NLDAS_time[0.346848]_x[320]_y[134]_var[tmp2m].feather: bc55b56b14e35b4edb2325851d5bca96
6_drivers/out/feather/NLDAS_time[0.346848]_x[322]_y[134]_var[tmp2m].feather: c82724eaa83639f6b23ea6e1e3ab54ee
6_drivers/out/feather/NLDAS_time[0.346848]_x[323]_y[134]_var[tmp2m].feather: 67133c44a8827dd47c1b5895fb0bdc0b
6_drivers/out/feather/NLDAS_time[0.346848]_x[324]_y[134]_var[tmp2m].feather: 15c96d3ce7091da200ac8f704a154ff8
6_drivers/out/feather/NLDAS_time[0.346848]_x[325]_y[134]_var[tmp2m].feather: 445573ad097125c52e9ac288bdf8bc41
6_drivers/out/feather/NLDAS_time[0.346848]_x[311]_y[135]_var[tmp2m].feather: 1c1a3cd6a2d61abe5a8fd412c8366856

I re-wrote the .csv tasks (these build the multi-variable driver file output) to include an additional step that filters this hash table into only the files that go into each individual driver file:
  # --- NLDAS_time[0.346848]_x[322]_y[134].csv --- #

  NLDAS_time_0.346848_x_322_y_134_cell_group_table:
    command: filter_cell_group_table(cell_group_table, pattern = I('time\\[0.346848\\]_x\\[322\\]_y\\[134\\]'))

  8_drivers_munge/out/NLDAS_time[0.346848]_x[322]_y[134].csv:
    command: feathers_to_driver_file(target_name, cell_group_table = NLDAS_time_0.346848_x_322_y_134_cell_group_table)

  8_drivers_munge/out/NLDAS_time[0.346848]_x[322]_y[134].csv.ind:
    command: sc_indicate(target_name)
    depends:
      - 8_drivers_munge/out/NLDAS_time[0.346848]_x[322]_y[134].csv

This seems to be a good solution for me, but it would be great to discuss. The time to move through the 16K feather files as individual targets was projected to be 44 days(!), this pattern allowed me to build them in ~1.5hr.

Here is the difference between the two approaches

Looks good to me.
Did you update scipiper::sc_indicate to vectorize data_file? PR coming? I think that'd be a useful addition to the package.
The major thing to point out for posterity is that your use case (1) involves enough files to really bog down remake hashing, and (2) does not involve a need for fault tolerance (or the fault tolerance is written into the function rather than relying on scipiper for retries). To decide to move from loop_tasks to this pattern, I think users should maybe have (1) and should definitely have (2) for their use case.

JR's PR is https://github.com/USGS-R/scipiper/pull/75

yes, and another thing to point out with this approach is that we lose the beneficial modularity of the initial approach - Adding a single new "cell" to the previous approach would rebuild the task makefile and then build one new file (or in this case, 8, since there is one file per variable). The one-to-many approach will rebuild all feather files, which is heavier. But in this case, the full re-build doesn't take that long (I looked at timestamps and it may even be less than an hour).

authors: aappling-usgs jread-usgs

repo: USGS-R/scipiper


text:
new figure 1

Taking some major shortcuts on the data dependency for this one, but doing so for time limits. The original geometry is built from the data, and I grabbed that geometry and did some direct edits to the svg to get the syle right. Now it is templated for mobile and desktop, but is not impacted by changes to the source data. We can tackle that later if it is a priority.
Looks like this now:

default is to have that one tab expanded when you load the app, and then it collapses if you mouseover anything else.

@ldecicco-USGS try this out?

@mwernimont note major change to fig1.mustache

:100:

COOL!!!

authors: aappling-usgs jread-usgs ldecicco-USGS

repo: USGS-VIZLAB/great-lakes-microplastics


text:
introducing vizmake()

First draft of vizmake(). I mentioned a plan for this in #288 and have been chewing on it. The idea will be to build the project via vizmake() rather than by calling remake::make directly. This PR just implements easy things, mostly what's needed for issue #292 - we can expand vizmake() in future PRs.
This PR addresses the problem diagnosed in #292 (and first encountered in #246 & #281): remake doesn't load the source for S3 methods that are called in the remake.yml via their generic. E.g., calling fetch('cars-data') won't load the fetch.cars method even if that script is listed in the sources: block of the remake.yml makefile. This vizmake implementation therefore sources those scripts before calling remake::make.
For this PR, I also toned down validateVizYaml.R to give warnings rather than errors so that the USGS-VIZLAB/example repo can be used as-is. Pretty soon we can update that repo to use underscore-separated viz item IDs and then we can hop back up to stop()s, assuming we want to stick to our most recent style decision to use snake case for viz ids. Caveat: I originally thought remake would FORCE us to switch to snake case, but it turns out hyphen-separated (kebab-case) IDs are still OK - remake treats cars-data as a single variable name if it's used as a target. But that's sorta weird, and I like that snake_case IDs could exactly correspond to the fetch/process/visualize/publish methods that create them, so I still think we should make the switch to the new style.

a few warnings showing up in travis (and those set to be shown as errors) but otherwise looks good to me

Hmm - I did what Github said: "Add more commits by pushing to the vizmake branch on aappling-usgs/vizlab" - but the new commit isn't showing up here. I will close and create a new PR with the R CMD check fixes.

repo: USGS-VIZLAB/vizlab


text:
每章在奇数页起始？

我觉得有必要再讨论一下chapter从奇数页起始，aka openright；
教务处规定的是“每章另起一页”，aka openany，我觉得这一点没必要非要跟《规范》对着干吧。
我这里有本GTM73就是openany的，Knuth自己的Concrete Math也是openany的，所以openright也不是行业的硬性规范，毕竟springer和pearson也不能说是外行吧。
@ywgATustcbbs 在 https://github.com/ywgATustcbbs/ustcthesis/issues/12 说“制本厂装订的时候会提醒学生每章从奇数页开始”，我还想了解一下制本厂会干预多少排版问题？他们会自行插入空白页？

openright和openany之间可以直接通过\documentclass的选项来实现切换，可以供用户自己选择。

制本厂的干预其实没什么意义，毕竟论文是学生自己的，他们没有权利管排版的问题，顶多是提醒一下学生罢了。
打印正文、制作封面、胶装，这三个步骤，也就只有制作封面是必须在学校制本厂做的，其他的都可以自己DIY。

我知道可以自定义，我问的是默认情况设置的情况，用哪个更合适？
一个问题是，现在的abstract是用\chapter做的，如果改了openany，英文abstract就在中文摘要的背面了。
我想应该把默认的预设做好，省得他们一个个来问。

恩，我更倾向于openright，毕竟这样看上去更加直观，而且也是大多数书籍的处理方法。
至于openany的时候英文abstract的问题，应该可以加一个额外的cleardoublepage来解决吧？

我倾向于教务处规定的openany。所以召唤@ywgATustcbbs 来投票吧哈哈

我觉得选哪个都无所谓，只要在模板以及文档里都写清楚就好。
至于那些连写好的文档都不看遇到问题就问的人，还是不要浪费时间去回答了。。。

authors: seisman zepinglee

repo: USTCThesis/USTCThesis-Rework


text:
made changes for 'extension arrows' and ratio='autot'

All tests pass.

@mcenerney1 shouldn't we be getting new baselines?

repo: UV-CDAT/uvcmetrics


text:
Remove unused variables

Removing the -Wno-unused flag from VIC's makefile reveals 401 unused variables in the current VIC source code.  I propose these be removed (or used as they were originally intended).
CalcAerodynamic.c:22:13: warning: 'vcid' defined but not used [-Wunused-variable]
CalcBlowingSnow.c:147:7: warning: unused variable 'count' [-Wunused-variable]
CalcBlowingSnow.c:142:16: warning: unused variable 'temp3' [-Wunused-variable]
CalcBlowingSnow.c:142:10: warning: unused variable 'temp' [-Wunused-variable]
...

There are still some unused variables in develop:vic_run/src/CalcBlowingSnow.c
:511:24: warning: unused parameter 'AirDens' [-Wunused-parameter]
:512:24: warning: unused parameter 'ZO' [-Wunused-parameter]
:518:24: warning: unused parameter 'Zrh' [-Wunused-parameter]
:710:21: warning: unused parameter 'Tsnow' [-Wunused-parameter]
:711:21: warning: unused parameter 'Tair' [-Wunused-parameter]
:810:30: warning: unused parameter 'es' [-Wunused-parameter]
:812:30: warning: unused parameter 'AirDens' [-Wunused-parameter]
:814:30: warning: unused parameter 'EactAir' [-Wunused-parameter]
:815:30: warning: unused parameter 'F' [-Wunused-parameter]
:819:30: warning: unused parameter 'Zrh' [-Wunused-parameter]

I can delete them, but just want to make sure first that they were not kept for a reason.

I seem to remember there being a reason that I left some of those around.  I think it had to do with the solvers used in CalcBlowingSnow.c.  Just be careful to track any function pointers or variable argument lists carefully.  If it can be done cleanly, by all means, let's get rid of them.

OK - I seem to remember the same - so I will leave it alone for now. When I have time I may go through and document within CalcBlowingSnow why these vars cannot be deleted.

authors: bartnijssen jhamman

repo: UW-Hydro/VIC


text:
Auto Calibration scripts

Bug Reports

Version of VIC that you are using (e.g. VIC.5.0.0)
Name and version of the C compiler you are using
Operating system
A description of relevant model settings
A summary of the bug or error message you are getting

Feature Requests

Description of feature
Description of the problem the feature addresses
Will the proposed feature be backward compatible?
Will the proposed feature change the science results of VIC?

closing as there was no description given.

authors: Arivolie jhamman


text:
Google speech recognition issue

Hi ,
@Uberi
I had two query to ask.
1.How can I use this Speech to Text API without external microphone. I want to use laptop built-in microphone.
2.When I start speaking the listen() only listen for 2 sec instead of 10 sec.
Can you help me with these two issues ASAP

I think you should put those into 2 separate issues.
(1) should just work. Can you tell us more about your setup?

Check out the documentation for the Microphone class.
You likely need to adjust the threshold settings. See adjust_for_ambient_noise documentation.

Please feel free to re-open this if you are still having these issues! I highly recommend filling in the issue template as well.

authors: Uberi gagana-hg zenogantner


text:
Invalid JSON

I'm trying to save a config on the web panel but i recieve invalid json message. I think the error is because config is too large, deleting some kill targets processes config works, so I think it's limiting it by chars.
My config has almost 1k kill targets now, is there any way to put the config in the website files or when the request is made miner will ignore it because is invalid?
From the pastebin the miner will take the json as invalid too?
And this drugged list will lag the miner or something?

No there's no limit to it, most likely I would guess one of the "Stealth Targets" you deleted was invalid in some way. Try pasting it into a JSON validator online and see what it says. I don't think that amount will lag anything in the miner, I've tried to optimize it as much as possible.

Oh, right, it's to stop PoD attacks. You can increase the limit from 10000 characters here:
https://github.com/UnamSanctam/UnamWebPanel/blob/b8b30b7b0412fa2f817fb80df9b561291eddb186/UnamWebPanel/assets/php/session-header.php#L39

authors: UnamSanctam Xeneht

repo: UnamSanctam/UnamWebPanel


text:
🛑 WebMail CIAC is down

In 4101c09, WebMail CIAC (https://webmail.ciac.cu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WebMail CIAC is back up in 4b26b73.


text:
[BUG] Authentication is not working

Description of the bug
Hey, if I click the Google login button and then back then it redirects to the dashboard page but I am not login. I think this issue needs to fix.
Can you please assign it to me?
Please add screenshots (if applicable)
No response
Add any other context about the problem here
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@SubhamB2003 how are you gonna fix this issue? Can you please explain a little bit?

Yes if I am successful in login then only it redirects to the dashboard page otherwise it stays on the sign in page.
Can you please assign it to me

@SubhamB2003 how are you gonna fix it?

@SubhamB2003 how are you gonna fix it?

I changed the fallback URL to "/" currently it was "/dashboard"

@SubhamB2003 is it working fine locally?

repo: UniKonf/vibey


text:
Create Deploying wallet instead of FutureWallet if refund is paid

Summary
A description of the changes proposed in the pull request.
Fixes #number
Checklist

[ ] Change is small and easy to review (please split big changes into multiple PRs)
[ ] Change is consistent with architecture
[ ] Change is consistent with test architecture
[ ] Change is consistent with naming conventions
[ ] New code is covered with tests
[ ] Tests related to old code are updated
[ ] Documentation is up to date with changes

rename createFutureOrDeployingWallet to createWallet

repo: UniLogin/UniLogin


text:
🛑 Heritage Operations Group is down

In 625a3dc, Heritage Operations Group (https://heritageofcare.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Heritage Operations Group is back up in d71b29f after 11 minutes.

repo: UniSynTechnologies/Upptime


text:
adding hashchain detailed explanation

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ x ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (yarn build) was run locally and any changes were pushed
[ ] Lint (yarn lint --check) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ x ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

There is a observation asking for more "detailed explanation" fro Hashchain, so I just added that in case it's helpful.
Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ x ] No

Other information

Closing this because we're likely going to remove the hashchain structure in the next unirep pre-release. For more info see #270

authors: marciob vimwitch

repo: Unirep/Unirep


text:
Make transaction hash smaller to fix box

Summary
Make transaction smaller to fix in the box
Fixes: 0
Checklist

[x] Change is small and easy to review (please split big changes into multiple PRs)
[x] Change is consistent with architecture
[x] Change is consistent with test architecture
[x] Change is consistent with naming conventions
[x] New code is covered with tests
[x] Tests related to old code are updated
[x] Documentation is up to date with changes

repo: UniversalLogin/UniversalLoginSDK


text:
Test: Student page link to course statistics

When on a student's page, clicking a course's arrow should show that course's course statistics.
This should be tested as it was broken already.

we already have these

repo: UniversityOfHelsinkiCS/oodikone


text:
Provide a changelog

Describe the feature request
Without a changelog, it is difficult to know if we are safe to upgrade.
Background
No response
Solution suggestions
No response

Thanks for opening this issue @rwparris2!
As proxy-client-vue still hasn't reached a minor version, having a look at the commit history may be your best bet for now: https://github.com/Unleash/proxy-client-vue/commits/main
If it helps, I made a new release on this repo with the aggregated changelog since v0.0.3:
https://github.com/Unleash/proxy-client-vue/releases/tag/v0.0.8
I hope this helps. We'll take your feedback into account for future releases.

repo: Unleash/proxy-client-vue


text:
Laravel 10.15.0 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v10.15.0 branch.
Before merging, you need to:

Checkout the shift-ci-v10.15.0 branch
Review all pull request comments for additional changes
Run composer update
Thoroughly test your application (no tests?, no CI?)

:x: Shift was unable to run composer update. Please be sure to run composer update before merging to ensure your dependency changes are fully compatible and reflected in your composer.lock file.


text:
Updates on README.md

Updating all the outdated information to catch up with the recent development.

I think it might be time for 0.2.0 after this gets merged, thoughts?

As for the releasing: I have not done tests with real devices for a bit. Waiting for the docker installation from @easybe before doing that work. Not sure how close we are there though? If it still takes a bit, I can do some tests locally tonight (CET).

As for the releasing: I have not done tests with real devices for a bit. Waiting for the docker installation from @easybe before doing that work. Not sure how close we are there though? If it still takes a bit, I can do some tests locally tonight (CET).

Our internal deployment will be updated today.

authors: b-rowan easybe tsagadar

repo: UpstreamDataInc/goosebit


text:
Unable to Operate Data Between Worker Threads

Hi, I've been working on a service that runs a video capture on a separate worker.
The approach to this has been to get the data from the frame read from the video capture and make a transferable object like Uint16Array or similar then reconstructing the matrix from the buffer on the main thread.
Unfortunately it seems like I get some type errors coming from the C bindings and I am not sure how to debug them. I've made a repository with the minimum viable reproduction of this issue at: https://github.com/jdmg94/opencv4nodejs-worker-bug
The repo has a control script to demonstrate these methods otherwise work if they're not on different threads
Error Message

Can you log the element that looks not to have the correct type, before the crash?

Can you log the element that looks not to have the correct type, before the crash?

I have included a code sample with a control file precisely to demonstrate that they are in fact the same type.
When the code runs in the main thread the conversion works flawlessly, it is only when transferring the buffer between workers that the native C bindings seem to complain (this is not a TS error)


text:
Add Color Options

It would be great to have the ability to specify a color for the spinner, even if it were a simple subset of colors (e.g. black, white).

Yes, here is how I did it:
.wave-spinner>div {
            background-color: burlywood;
    }

Here's how to change the colors for each of the spinners:
(Note I am using version 1.2.5)
In this file I am setting all the colors to Red (#FF0000)

.sk-rotating-plane {
  background-color: #FF0000;
}

.sk-double-bounce > .sk-child {
  background-color: #FF0000;
}

.sk-wave > .sk-rect {
  background-color: #FF0000;
}

.sk-wandering-cubes > .sk-cube {
  background-color: #FF0000;
}

.sk-spinner {
  background-color: #FF0000;
}

.sk-chasing-dots > .sk-child {
  background-color: #FF0000;
}

.sk-three-bounce > .sk-child {
  background-color: #FF0000;
}

.sk-circle .sk-child:before {
  background-color: #FF0000;
}

.sk-cube-grid > .sk-cube {
  background-color: #FF0000;
}

.sk-fading-circle > .sk-circle:before {
  background-color: #FF0000;
}

.sk-folding-cube > .sk-cube:before {
  background-color: #FF0000;
}

It'd be really handy to add this to the README and/or provide a single class that would change any type of spinner. I'm a newb at CSS and this was super helpful for me.

@allancaffee can you PR the README?

authors: Mahmoudz Urigo allancaffee andrewmunsell hopewise

repo: Urigo/angular-spinkit


text:
handle nested object in sourceArgs map

Description
Allows to use nested objects in the sourceArgs argument of additionalResolvers or @resolveTo directive.
Fixes #5729
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Tested using the example getting started repo.
Checklist:

[x] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests and linter rules pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

should there be a test added that covers that bug?

authors: EmrysMyrddin Urigo

repo: Urigo/graphql-mesh


text:
feat: support generic templates in proposal PDF

Description
This adds support for GENERIC_TEMPLATE question type in proposal PDFs. These question types can contain sub-questions.
We decided to make these generic templates display in grid format to save space. For now this is 2 columns wide but can be changed in the future. Further down the line, we may also want to include an option on whether to display these questions in grid format (similar to "omit from pdf") .
Motivation and Context
Generic template questions don't display at all currently
Screenshots

Known issue
The boxes don't split properly onto separate pages (see screenshot).
I think this is because the CSS rule page-break-inside: avoid; isn't being respected. I tried various things with Bootstrap columns and rows, and also overriding that by using flex. The only way I could get it to work was with a single column, not multiple. It seems to be an older CSS rule and the only possible solution I could find was to put the layout in a table. I guess this would be fine since it's all rendered to PDF anyway, but I think it would require additional logic of when to insert new rows, which I wasn't sure was the right route.

How Has This Been Tested
Pretty much what is shown in the screenshots, please let me know if I should test more than this:

Proposal PDF with a generic template question but no answer
Proposal PDF with a generic template question and 1 answer
Proposal PDF with a generic template question and multiple answers
Proposal PDF with no generic templates
Existing test extended to cover generic templates

Fixes
Closes UserOfficeProject/stfc-user-office-project#222
Changes

New partial created, genericTemplates.hbs that handles generic template logic
questionaryAnswer.hbs modified so that when the question type is GENERIC_TEMPLATE, the template info is passed to genericTemplates.hbs
genericTemplates.hbs gives each question back to questionaryAnswer.hbs for rendering, to avoid repeated logic

Depends on

Tests included/Docs Updated?

[x] I have added tests to cover my changes.
[ ] All relevant doc has been updated

Can you open an issue for generic templates being broken between pages? If we're seeing it affect our users a lot, we can increase the priority.

authors: TickleThePanda simonfernandes

repo: UserOfficeProject/user-office-factory


text:
Allow subdivision box modelling in Godot 4 using godot-ply

https://github.com/jarneson/godot-ply

[x] port to 4

Ported to 4 but needs work.


text:
Change module paths to lowercase

Wanted to suggest this, because I ran into trouble building the project on Unix systems. The files are actually lowercase, and when I tried to build them on Unix-like systems, the relative paths are wrong. This is probably different on DOS systems, where the is no difference between upper and lowercase names.

Hello,
I build on Linux and I see uppercase folders:
$ ls -la
total 56
drwxrwxr-x  8 lexa lexa  4096 mars  28 17:25 .
drwxrwxrwt 10 root root 16384 mars  28 17:25 ..
drwxrwxr-x  8 lexa lexa  4096 mars  28 17:25 .git
-rw-rw-r--  1 lexa lexa   333 mars  28 17:25 .gitignore
-rw-rw-r--  1 lexa lexa  1097 mars  28 17:25 LICENSE.txt
-rw-rw-r--  1 lexa lexa  3392 mars  28 17:25 README.md
drwxrwxr-x  4 lexa lexa  4096 mars  28 17:25 RISE-V2G-Certificates
drwxrwxr-x  3 lexa lexa  4096 mars  28 17:25 RISE-V2G-EVCC
drwxrwxr-x  3 lexa lexa  4096 mars  28 17:25 RISE-V2G-PARENT
drwxrwxr-x  3 lexa lexa  4096 mars  28 17:25 RISE-V2G-SECC
drwxrwxr-x  4 lexa lexa  4096 mars  28 17:25 RISE-V2G-Shared

I don't have problem building neither.
This is out of a fresh git clone.

Ah, just tested it from a fresh clone, and I see the same. Probably a problem that occurred while transferring it to Gitlab.

authors: AxelVoitier kristbaum


text:
Plan: Update runners

Tasks:

Move runner calculations to SpecSuite
Integrate inline runner into SpecSuite as SpecSuite.(Print, Results, Debug, etc.)
Make display runner prettier: Progress, clearer failures and overall results, cleaner UI

What would SpecSuite.Debug do?
Might be better to separate the running from the displaying, which will help in writing custom display methods without having to worry about the runner portion of it.
This will allow the runner calculations to live inside of SpecSuite, but then allow a printer/display delegate to be assigned which will get (event?) callbacks when a spec is started, "it" is ran, and final results, etc.?
The printer would only then be responsible for displaying information it's provided.

I agree, I think the whole idea of a "runner" doesn't work currently since the SpecSuite actually runs the specs.
Adding events for specs is interesting (I've been reading more about them lately, http://www.cpearson.com/excel/Events.aspx). That'll require some changes to separate SpecSuite creation and running (currently the runner gets the spec suite after it's run so no events would be fired). At the minimum, the goal is to move the calculations to SpecSuite
The main idea of SpecSuite.(Print, Results, Debug) was to have a simple way of output spec results to the Immediate Window, but I'll re-evaluate after I start playing with it.

repo: VBA-tools/Excel-TDD


text:
Unable to use ordinal variables as categorical variable in overlay

Identified by @bobular. Using PRISM2 ICEMR cohort, he tried to use "Acres categorization" (a household variable) as an overlay variable and found that an empty plot appeared. The plot appears correctly if you use a categorical variable that's not ordinal, like "Bank account"

similar to veupathdb/edasubsettingservice#19 .. think the problem is the variable vocabulary claims things like ">3" and then gives actual values like "4. >3". the response from the data service succeeds and is accurate given what it was provided in any case. and the variable vocabulary seems fine to me. the values there are the ones i imagine wed like to display, and in the proper order. think this may be for @steve-fischer-200 and the subsetting service?

to be clear, i dont think the values need to have the numbers indicating order in front of them, so long as the vocabulary is known to be properly ordered.

This seems fixed now?

histogram endpoint is now returning >3  not 4: >3
{"overlayVariableDetails":
  {"variableId":"EUPATH_0020221",
   "entityId":"PCO_0000024",
   "value":">3"
  }
}

Yes, looks fixed. I'm closing it

authors: SheenaTomko bobular d-callan

repo: VEuPathDB/EdaDataService


text:
Add attribute to study details to indicate presence of geographic attributes

Resolves https://github.com/VEuPathDB/EdaSubsettingService/issues/119

dan, in lines 91, 92 in 7e1ca4c#diff-617659a5876e291386b98eb5ec9cb1173220e2b1defc546c2bd687fe254f1350
we are checking that an entity has 3 variables, each with one of those 3 types right?

We're checking that an entity has any one variable with a display type equal to one of those types.

repo: VEuPathDB/lib-eda-subsetting


text:
OOM Errors

MBlast is thrown oom errors with -Xmx256M.
We suspect the issue is the number of failures in the job queue as they are cleared lazily 1 at a time but the list is continually growing and now has ~2k errors.  These errors are all being pulled into memory and converted to POJOs on each request which means we could feasibly be holding onto 10k+ of these POJOs at any given time.
To correct this we have 3 proposals:

Ensure that only one page of errors is loaded into memory per request at any given time.
Ignore the error list in the queue and use flag files to signify whether a job completed successfully or failed.
Proactively clear errors from the error list that are greater than 30 days old.

Merged in all commits related to the filesystem error checks rather than the Fireworq error queue checks.

repo: VEuPathDB/service-multi-blast


text:
Pre-trained checkpoints needed

Thank you for providing code for this excellent work!
I'm wondering if you could add some pre-trained Aug-NeRF checkpoints into your codebase in convinience of my studies, as for my lacking of computing power for training.
Appreciate your help in advance!

And for addition, what should I do, like how to modify the code for extracting adversarial examples of certain image?

repo: VITA-Group/Aug-NeRF


text:
Basscss update

Closes #28

Updated basscss to v8
Changed event classnames to item in jobs and events boards.
Updated specs with new classnames
Updated css files with new classnames

Many thanks!  I love this PR, but the update to basscss 8 is even trickier.
Basscss is not "bower friendly", when you add it to the project it downloads the repo, but there is no dist available, so i had to compile it and add it manually to vendor folder (https://github.com/VLCTechHub/VLCTechHub/blob/master/vendor/css/basscss.css) so upgrading the bowerfile alone does not trigger the update of the css.
Moreover, basscss 8 is quite a change from basscss 7 and I am not sure if we should update. (http://www.basscss.com/ vs http://www.basscss.com/v7/) @Pardiez suggested this library is "ok" for prototyping but we should use another css approach.
I'm open to suggestions. Meanwhile, to merge this PR, could you put back version 7 on bowerfile? Thanks!

repo: VLCTechHub/VLCTechHub


text:
Bug Missing = after date_from on uri

Hi,
You missed an "=" in the query after "date_from"
@VMelnalksnis.NordigenDotNet/Accounts/AccountClient.cs
@public async Task GetTransactions
@line 65
uri += $"?date_from{value.Start:yyyy-MM-dd}&date_to={value.End:yyyy-MM-dd}";
should be:
uri += $"?date_from={value.Start:yyyy-MM-dd}&date_to={value.End:yyyy-MM-dd}";
Thx

Just published v0.4.4, should be available shortly in nuget.org

authors: VMelnalksnis uploaded

repo: VMelnalksnis/NordigenDotNet


text:
Allow testmethod to continue running after failed test

Sometimes one testmethod implements multiple tests.
It would be nice to have an option to log any failures, but allow the test to run in order to detect any subsequent failures as well.
One option would be to use code like this:
  try
    Assert.IsTrue(ResultF = ResultS, 'message');
  except
    LogFailureWithDUnitX('other message');
  end;

Can this already be done, if not adding the LogFailure code would be useful.

Not really doable with the current design, DUnitX uses exceptions to fail/abort a test (the Assert class does that).

Can't we make a warn.isTrue to supplement the assert. Sometimes you really want to see what happens after the first fail.

Closing this as won't fix, it would require a major redesign (not sure I know how) to do this. The work around is don't use Assert, as it is designed to abort the test immediately.

Junit introduced the concept of @Rule that handles this use case, but i don't know how much effort is required for implement similar feature neither how do it myself.
Maybe this will give you new ideas. :smiley:

authors: JBontes fabriciocolombo vincentparrett

repo: VSoftTechnologies/DUnitX


text:
chore(main): release 1.0.1

:robot: I have created a release beep boop
1.0.1 (2024-07-26)
Bug Fixes

commit (7866c3e)
module name (0d2d924)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.1
:sunflower:

repo: VU-ASE/roverrtc


text:
Caching with FirstOrDefaultAsync query seems broken

Summary of the issue
Hello, retrieving data asynchronously using FirstOrDefaultAsync doesn't place objects in cache. Retrieving data using the same query, except using FirstOrDefault instead of FirstOrDefaultAsync does place objects in cache. I see no cache related output when using FirstOrDefaultAsync.
Environment
.NET (Core) SDK version: 3.1.422
Microsoft.EntityFrameworkCore version: 5.0.15
EFCoreSecondLevelCacheInterceptor version: 3.6.3
Database: (e.g. SQL Server, SQLite, etc.): PostgreSQL
Cache provider: (e.g. in-memory, redis, etc.): Redis
# Other packages
EasyCaching.Redis: 1.6.1
EasyCaching.Core: 1.6.1
EasyCaching.Serialization.Json: 1.6.1

Example code/Steps to reproduce
Startup.cs
public void ConfigureServices (IServiceCollection services) {
    services.AddEncryptedDbContext<IEmployeeDbContext, EmployeeDbContext>(Configuration,
        (provider, builder) =>
            {
                builder.UseNpgsql(Configuration.GetConnectionString("DefaultConnection"))
                        .AddInterceptors(provider.GetRequiredService<SecondLevelCacheInterceptor>());
            });

            services.AddEFSecondLevelCache(options =>
            {
                options.UseEasyCachingCoreProvider("redis").DisableLogging(false).UseCacheKeyPrefix("EF_");
                options.CacheAllQueriesExceptContainingTableNames(CacheExpirationMode.Sliding, TimeSpan.FromMinutes(5),"__EFMigrationsHistory");
            });

        services.AddEasyCaching(options =>
        {
            options.WithJson("json");
            options.UseRedis(config =>
                {
                    config.DBConfig.Endpoints.Add(new ServerEndPoint("127.0.0.1", 6379));
                    config.SerializerName = "json";
                    config.EnableLogging = true;
                }, "redis");
            });
        }
}

Repository.cs
public class EmployeeRepository
{
    private readonly IEmployeeDbContext _context;

    public EmployeeRepository(IEmployeeDbContext context)
    {
        _context = context;
    }

    public Employee Get(long id)
    {
        // Works, entry is added to cache
        return _context.Employees
            .Where(p => p.Id == id)
            .FirstOrDefault();
    }

    public async Task<Employee> GetAsync(long id)
    {
        // Does not work, no output from EFCoreSecondLevelCacheInterceptor
        // No entry is added to Redis
        return await _context.Employees
            .Where(p => p.Id == id)
            .FirstOrDefaultAsync();
    }
}

Output
EmployeeRepository.Get:
info: Microsoft.EntityFrameworkCore.Infrastructure[10403]
      Entity Framework Core 5.0.15 initialized 'EmployeeDbContext' using provider 'Npgsql.EntityFrameworkCore.PostgreSQL' with options: None
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. Using EFCachePolicy: EFCachePolicy --> Sliding|00:05:00|||False.
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. ContextTableNames: Employee, PossibleQueryTableNames: Employee -> CacheDependencies: Employee.
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. KeyHash: EF_21B72244C9CCDB92, CacheDependencies: EF_Employee.
info: EasyCaching.Redis.DefaultRedisCachingProvider[0]
      Cache Missed : cachekey = EF_21B72244C9CCDB92
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. [KeyHash: EF_21B72244C9CCDB92, CacheDependencies: EF_Employee.] was not present in the cache.
info: Microsoft.EntityFrameworkCore.Database.Command[20101]
      Executed DbCommand (29ms) [Parameters=[@__id_0='?' (DbType = Int64)], CommandType='Text', CommandTimeout='30']
      SELECT e."Id", e."ActivatedAt", e."ActivationStatus", e."ActivationStatusMessage", e."ContactEmailAddress", e."CreatedAt", e."CreatedByUserId", e."FirstName", e."Gender", e."LastName", e."PhoneNumber", e."UserEmailAddress", e."UserId"
      FROM "Employee" AS e
      WHERE e."Id" = @__id_0
      LIMIT 1
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. Using EFCachePolicy: EFCachePolicy --> Sliding|00:05:00|||False.
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. ContextTableNames: Employee, PossibleQueryTableNames: Employee -> CacheDependencies: Employee.
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. KeyHash: EF_21B72244C9CCDB92, CacheDependencies: EF_Employee.
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[0]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. Skipped invalidating a none-CRUD command[SELECT e."Id", e."ActivatedAt", e."ActivationStatus", e."ActivationStatusMessage", e."ContactEmailAddress", e."CreatedAt", e."CreatedByUserId", e."FirstName", e."Gender", e."LastName", e."PhoneNumber", e."UserEmailAddress", e."UserId"
      FROM "Employee" AS e
      WHERE e."Id" = @__id_0
      LIMIT 1].
info: EasyCaching.Redis.DefaultRedisCachingProvider[0]
      Cache Missed : cachekey = EF_Employee
dbug: EFCoreSecondLevelCacheInterceptor.EFDebugLogger[100001]
      InstanceId: 198431d7-a6a0-489f-a2dc-1b9fd6ca22f8, Started @09/07/2022 12:38:11 UTC. TableRows[48a0f0a1-b540-4008-8677-7dc4f13ce203] added to the cache[KeyHash: EF_21B72244C9CCDB92, CacheDependencies: EF_Employee.].

EmployeeRepository.GetAsync:
info: Microsoft.EntityFrameworkCore.Infrastructure[10403]
      Entity Framework Core 5.0.15 initialized 'EmployeeDbContext' using provider 'Npgsql.EntityFrameworkCore.PostgreSQL' with options: None
info: Microsoft.EntityFrameworkCore.Database.Command[20101]
      Executed DbCommand (26ms) [Parameters=[@__id_0='?' (DbType = Int64)], CommandType='Text', CommandTimeout='30']
      SELECT e."Id", e."ActivatedAt", e."ActivationStatus", e."ActivationStatusMessage", e."ContactEmailAddress", e."CreatedAt", e."CreatedByUserId", e."FirstName", e."Gender", e."LastName", e."PhoneNumber", e."UserEmailAddress", e."UserId"
      FROM "Employee" AS e
      WHERE e."Id" = @__id_0
      LIMIT 1

I have some integration tests here using FirstOrDefaultAsync and it works for me. I use the SQL Server's Profiler to validate it.
Also I have some async tests here too.

Hello, I don't have that much time these weeks to look at it, but I see that in the tests and example you linked you always used CacheExpirationMode.Absolute. I will try to use that instead of CacheExpirationMode.Sliding, maybe that might make a difference.
I understand that FirstOrDefault and FirstOrDefaultAsync generate the same queries. However, with an empty Redis instance, I couldn't see any activity in the logs (no lookups or cache misses).

authors: VahidN gitknul


text:
Resolved issues and Updated About Us Page

Pull Request
Title
Updated the About Us page
Description
Updated the About Us page and made it fully responsive for all devices and dimensions
Added Interactive and sleek animations
Fixed the spacings
Related Issues
Fixes #346
Changes Made
New Features and bug fixes
Checklist

[x] I have tested the changes locally
[x] Documentation has been updated (if necessary)
[x] Changes are backward-compatible

Screenshots (if applicable)
Video Demo
https://github.com/user-attachments/assets/a6ecd3ed-670c-49bb-a691-a2cb4c39dade
These are the screenshots

Additional Notes

Footer

@VaibhavArora314 resolved the conflicts. It might happen again if anyone else pushes their deprecated code before you merge this pr. So kindly merge it.


text:
Conversion fails

Interesting package. it would be nice if it worked. we are using confluence across the org and it would be awesome if we could share are results like this directly from the notebook.
Unfortunately, it does not work:
nbconflux path/to/notebook.ipynb https://path/to/page
traceback:
Traceback (most recent call last):
  File "/Users/laukea/.pyenv/versions/miniconda3-latest/bin/nbconflux", line 10, in <module>
    sys.exit(main())
  File "/Users/laukea/.pyenv/versions/miniconda3-latest/lib/python3.7/site-packages/nbconflux/cli.py", line 57, in main
    extra_labels=args.extra_labels)
  File "/Users/laukea/.pyenv/versions/miniconda3-latest/lib/python3.7/site-packages/nbconflux/api.py", line 56, in notebook_to_page
    exporter = ConfluenceExporter(c)
  File "/Users/laukea/.pyenv/versions/miniconda3-latest/lib/python3.7/site-packages/nbconflux/exporter.py", line 100, in __init__
    self.server, self.page_id = self.get_server_info(self.url)
  File "/Users/laukea/.pyenv/versions/miniconda3-latest/lib/python3.7/site-packages/nbconflux/exporter.py", line 149, in get_server_info
    page_id = int(segs[5])
ValueError: invalid literal for int() with base 10: 'create'

This was due to the path   to the confluence page. my fault...

repo: Valassis-Digital-Media/nbconflux


text:
Windows XP & blockcheck

Под XP тулза не работает :

blockcheck-0.0.9.5-windows.exe - Точка входа не найдена
Точка входа в процедуру GetFinalPathNameByHandleW не найдена в библиотеке DLL KERNEL32.dll.

Fatal Error!
Error loading Python DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp_MEI25842\python35.dll (error code 127)

Не работает, и работать не будет. Windows XP давно не поддерживается. Используйте современную ОС.

repo: ValdikSS/blockcheck


text:
🛑 b2b MarketingServices is down

In 9fb10cc, b2b MarketingServices (https://b2b-marketingservices.de/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: b2b MarketingServices is back up in 1c626ac after 32 minutes.


text:
🛑 b2b MarketingServices is down

In 5f24b43, b2b MarketingServices (https://b2b-marketingservices.de/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: b2b MarketingServices is back up in db66a02 after 7 minutes.


text:
🛑 b2b MarketingServices is down

In 9252e81, b2b MarketingServices (https://b2b-marketingservices.de/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: b2b MarketingServices is back up in f692230 after 10 minutes.


text:
Incompatibility with NotEnoughIDs

Game Crashes during world gen when NotEnoughIDs is installed.
See:
2018-02-10-7.log

@maxZZzzz Could you test this again with the latest build? I believe I fixed this issue in the last release.

After looking into it further I seem to be in the wrong, I hadn't fixed it in the latest release. Anyways I'm pushing out a commit soon that does fix it.


text:
Voicerange

Sup, is it possible to add a command which allows you to specify your voicrange for example 8/16 or 32 Blocks

Hi, You can change it in config file, Also you can change everything about voice.
`
------ sound configs ------
3D-sound: true # player voice 3D mode.
hear-lazy: true # default player volume (when 3DSound is "false" you can use this feature).
max-distance: 30 # distance that players can hear each other.
ref-distance: 5  # distance that players can hear each other max volume.
inner-angle: 120 # angle that players can hear each other max volume.
outer-angle: 180 # angle that players can hear each other.
outer-volume: 0.3 # outer angle volume.
`

Yeah i saw that but it would be a nice feature if it is possible to do it ingame for each player for example in an roleplay situation

The feature is examined in the first opportunity, and if there are no issues, this feature will be added to the plugin.

authors: DerVerplanteTom Vallerian

repo: Vallerian/MelodyMine