using_induction_hyp fails for lemmas with two arguments

F* cannot prove this lemma using automatic induction:
val append_length :
  l1:list 'a -> l2:list 'a ->
  Lemma
    (requires True)
    (ensures (length (append l1 l2) = length l1 + length l2))
let rec append_length l1 l2 = using_induction_hyp append_length

I think the right way to solve this is to drop using_induction_hyp altogether and implement #51 instead.

Syntax got changed to by_induction_on l1 append_length, but the problem is still here.

by_induction_on is gone for good. It never really worked very well, and Nik would prefer to figure out something properly via a tactic language. Closing as wontfix.


Webpack strips out exports from define, introducing circular dependency problems

Webpack when bundling with umd does not handle exports and therefore introduces circular dependency problems.
Actual
in app.bundle.js
	else if(typeof define === 'function' && define.amd)
		define([dependencies], factory);

Expected
	else if(typeof define === 'function' && define.amd)
		define(['require', 'exports', dependencies], factory);
...
var result = webpackJsonp([0,2],{...});
for(prop in result ){
    exports[prop]=result[prop];
}

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.

I thought I answered all the relevant information in the template.  Will create a new issue


Add documentation

Add documentation and upload it to readthedocs.

Solved with https://github.com/mkmenta/python-package-example/pull/9


Switching themes sometimes does not occur immediately

Bug Summary:
Upon switching themes on the settings page sometimes it flashes the old theme for a short period then reverts back to the new theme.

Steps To Reproduce

Go to the settings page
Change theme
Keep repeating step 2

Expected behaviour
Every time the theme is changed colours should only change once.
Observed Behaviour
Sometimes the old theme will flash when changing themes.
Screenshots

Environment

Version: Commit 9fab8f0
Operating System: Ubuntu 18.04
Browser (if any): Chrome v75

will investigate

fix: https://github.com/se701g2/Doto/pull/255


Document gas measuring for releasing

This fixes #492.
[no ci] <-- seems not working https://github.com/raiden-network/raiden-contracts/issues/507

I don't think this should have been merged, the gas cost will change with the version of the smart contract, so this data should go into the json (which has the additional benefit of working with other languages, besides python)

@hackaugusto That's also a nice idea -- but perhaps going for other language other than python may be a premature optimization at the moment. But according to @pirapira 's comment above I understand that what this PR documents is temporary and the "real thing" approach is discussed and documented in this issue

@hackaugusto I do document the current ugly approach before changing it.


Fix type errors when HOMEBREW_SORBET_RUNTIME=1

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

As requested in https://github.com/Homebrew/brew/pull/15705#issuecomment-1640081358

Thanks again @dduugg!


No games List

clone and run:
docker compose up --build

What's in your browser console tab (控制台)? I assume, this is the latest Firefox?
Could you try to reload the page without the cache? That's Ctrl+Shift+R in FF, and Ctrl+F5 in Chrome.


Integrate thumbnail previews during the Wikimedia Commons batch file upload process

See https://commons.wikimedia.org/wiki/Commons_talk:OpenRefine
Request received in a conversation in the Wikimedia Commons Telegram channel. During a batch upload process of media files, it is extremely helpful if one can (easily) see thumbnail previews of the media files that are being uploaded.
Some existing Wikimedia Commons (batch) upload tools support this indeed (the default UploadWizard, for instance), others don't (Pattypan only shows previews of files and their infoboxes during the checking phase of the upload process, after all data has been prepared already).
OpenRefine is essentially a data-centric tool, so this may be a stretch, but it's good to have this request on the radar, as it makes a lot of sense IMO.

The extension can and should be developed to support what users need irregardless of OpenRefine. That's the beauty of an extension. Extending in ways the original program had no need for.

@trnstlntk, @lozanaross and I have discussed this during a training workshop with users from cultural institutions, and one attendee asked if the feature could be available for projects that are unrelated to Wikimedia Commons.
The issue could indeed be formulated like this: say I have a dataset where one column contains local paths to images, I would like to have OpenRefine display small thumbnails of those images in the corresponding cells.
Given that we currently do not have any extension point which would let extensions customize cell rendering (as far as I can tell), it seems that we have two reasons to implement this in the core directly. I think this could go in some sort of view options of a given column, potentially?

@lozanaross has created various wireframes that include file previews. A selection from the latest (April 26) version of the wireframes:
While working on a project:

We're also considering a functionality to make the thumbnail bigger here, especially useful when the user will be working with many similar media files that they want to compare:

During upload (schema) preview:

Assigning this task to @lozanaross (design; work in progress) and @j-sal (development of this feature). I didn't see an explicit deadline attached during the roadmapping exercise we did last week, but we placed this task around July so I'm provisionally adding a July 31 deadline.

@trnstlntk, @lozanaross and I have discussed this during a training workshop with users from cultural institutions, and one attendee asked if the feature could be available for projects that are unrelated to Wikimedia Commons.
The issue could indeed be formulated like this: say I have a dataset where one column contains local paths to images, I would like to have OpenRefine display small thumbnails of those images in the corresponding cells.
Given that we currently do not have any extension point which would let extensions customize cell rendering (as far as I can tell), it seems that we have two reasons to implement this in the core directly. I think this could go in some sort of view options of a given column, potentially?

I'll be happy to edit this issue to reflect the broader scope. We could also split it in seperate tasks?
For Wikimedia Commons, we identified distinct use cases that will need (as I understood it) different development approaches:

[ ] User wants to use OpenRefine to add structured data to existing files from Wikimedia Commons. They load a series of file paths from Wikimedia Commons and then display thumbnails of these in OpenRefine. This can build further upon the work by @eugeneegbe on the Commons Reconciliation Service. (This is the first use case we want to tackle; deadline July 31)
[ ] User wants to use OpenRefine to upload new files to Wikimedia Commons, from harddrive. They select a set of files from their harddrive. We need to develop a way to display thumbnails for these in OpenRefine.
[ ] User wants to use OpenRefine to upload new files to Wikimedia Commons, from the web. They select a set of URLs (or start a project from API, or similar). We need to develop a way to display thumbnails for these in OpenRefine.

For the second and third scenario: we placed work on this task around September 2022 in our roadmap. Due to time constraints perhaps we won't get there during the current grant.

Yes we could potentially have three separate issues I think.

I think we discussed this and indeed we need separate issues, I'll set the others up - I think we also agreed the deadline for this first case (Commons images) is July 01 because we want it for wikimania?

The way the issue is framed at the moment makes me think it belongs in the extension repo, not in the main repo btw. I think it needs to be abstracted and possibly created later (after this issue is closed) in the main OpenRefine repo.

I think we discussed this and indeed we need separate issues, I'll set the others up - I think we also agreed the deadline for this first case (Commons images) is July 01 because we want it for wikimania?

We didn't put a deadline on that specific post it note 😅  but we indeed placed it right before Wikimania, so I'd say yes.

The way the issue is framed at the moment makes me think it belongs in the extension repo, not in the main repo btw. I think it needs to be abstracted and possibly created later (after this issue is closed) in the main OpenRefine repo.

Replying to myself - this is a dumb comment because I realize you cannot move issues across repos in Github (unless I am just not seeing how?? it is possible in Gitlab). I guess we should keep this here for now, but it's technically part of the SDC extension because we're first developing the thumbs for commons only, right? Then later the options to render local / remote files?

I realize you cannot move issues across repos in Github

Yes you can, it is called "Transfer issue" on the right-hand side, and as a member of the organization it should be available to you.


Update PR workflow

Description

$subject

We do not need to update the ballerina-action version. Hence closing the PR.


Disable user consent based claim filtering for back channel grant types

Fixed with https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/839


How to get map object from plugin

When I  import MapGL  from  " import MapGL, { SVGOverlay }  from 'react-map-gl';"
I don't know how to get the map from  .
I need to get the map object to do other operations.
Looking forward to your answer

I don't know how to get the map

This is described in the docs


wrong permissions when running/starting agent first time

Affecting:
Agent
Version:
0.6.10
Describe the bug
when running the natlas-agent firs time, container dont
start. when running docker -D run:
debug-output:

Traceback (most recent call last):
  File "/opt/natlas/natlas-agent/natlas-agent.py", line 13, in <module>
    from natlas.threadscan import ThreadScan
  File "/opt/natlas/natlas-agent/natlas/threadscan.py", line 9, in <module>
    from natlas import screenshots
  File "/opt/natlas/natlas-agent/natlas/screenshots.py", line 11, in <module>
    from natlas import utils
  File "/opt/natlas/natlas-agent/natlas/utils.py", line 8, in <module>
    utillogger = logging.get_logger("Utilities")
  File "/opt/natlas/natlas-agent/natlas/logging.py", line 34, in get_logger
    logger.addHandler(get_file_handler())
  File "/opt/natlas/natlas-agent/natlas/logging.py", line 24, in get_file_handler
    file_handler = RotatingFileHandler("logs/agent.log", maxBytes=1024 * 1024, backupCount=5)
  File "/usr/lib/python3.6/logging/handlers.py", line 150, in __init__
    BaseRotatingHandler.__init__(self, filename, mode, encoding, delay)
  File "/usr/lib/python3.6/logging/handlers.py", line 57, in __init__
    logging.FileHandler.__init__(self, filename, mode, encoding, delay)
  File "/usr/lib/python3.6/logging/__init__.py", line 1032, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python3.6/logging/__init__.py", line 1061, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/opt/natlas/natlas-agent/logs/agent.log'

To Reproduce
isnatll a fresh agent on a fresh VPS, using the
install-instructions from
https://github.com/natlas/natlas/blob/main/natlas-agent/README.md
atlas_env created
run_command:

docker -D run  --restart=no  -v $(pwd)/agent_env:/opt/natlas/natlas-agent/.env natlas/agent:0.6.10

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise running agent-container
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Thanks for opening this issue. Please try to docker pull natlas/agent:main and run that. I believe this issue was addressed in a commit already. You don't need to switch to natlas/server:main in order to use them together at this time, though I'd recommend it.
Let me know if natlas/agent:main fixes this issue for you.

natlas/agent:main did the trick

root@nsa-1:~/doxxer# ./agent_run.sh
2020-07-24 17:30:58,666 — NetworkServices — INFO — Fetching natlas-services file from http://XXXXXXXXXXX
...

Thanks for the follow up! Maybe this is a sign that we should release the current version as 0.6.11. I'm in the middle of a huge agent rewrite to make it more maintainable, but it'll break backwards compatibility, so maybe I should make one more 0.6.x release before going to this for a 0.7.0 release.


Init error on windows when repo path begins with drive letter

Output of restic version
restic 0.3.3 (v0.3.3-4-g9f1f174-dirty)
compiled with go1.7.4 on windows/amd64
Expected behavior
Creation of repo
Actual behavior
Error
C:\Dev\restic>.\restic.exe init --repo D:\backup-photos
debug log file \temp\restic-debug.log
debug enabled
create backend at D:\backup-photos failed: MkdirAll: mkdir \\?: La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

Message in french is "The syntax of the file name, directory, or volume is incorrect"
Steps to reproduce the behavior
See Error. Tested on Windows 7 home
Content of log file
2017/01/22 18:57:50 restic/main.go:39	main.main	1	main []string{".\\restic.exe", "init", "--repo", "D:\\backup-photos"}
2017/01/22 18:57:50 restic/global.go:338	main.create	1	parsing location D:\backup-photos
2017/01/22 18:57:50 restic/global.go:346	main.create	1	create local repository at "D:\\backup-photos"
2017/01/22 18:57:50 restic/lock.go:112	main.unlockAll	1	unlocking 0 locks

Workaround : creation of empty repo directory before calling restic init :
C:\Dev\restic>set DEBUG_LOG=\temp\restic-debug.log
C:\Dev\restic>set RESTIC_PASSWORD=test

C:\Dev\restic>mkdir D:\backup-photos

C:\Dev\restic>.\restic.exe init --repo D:\backup-photos
debug log file restic-debug.log
debug enabled
created restic backend fbc002ea9f at D:\backup-photos

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.

C:\Dev\restic>.\restic.exe  --repo D:\backup-photos backup P:\G4
debug log file restic-debug.log
debug enabled
scan [P:\G4]
scanned 6 directories, 768 files in 0:00

Thanks for reporting this issue. I'd appreciate any help from Windows developers to tackle this :)

os.MkdirAll fails because it cant use the UNC prefix from here.
There is already a ticket at golang/go

Thanks for investigating. It seems we need to reimplement MkdirAll for Windows, maybe we can use the code from syncthing: https://github.com/syncthing/syncthing/commit/f12b8c19be459433de5f6b1507b3b176556ea071


Missing Foreign Key Constraints

Referring back to https://github.com/sumitkumar1503/hospitalmanagement/issues/9#issue-642626502
Please, this needs to be fixed.

@shifat151 He accepted my PR, please close this issue.


Move images directory to root

This PR closes #81 by:

renaming the src/_static/images directory and its contents to src/_images , and
updating all occurrences of _static/images in the doc pages to _images.

@lochhh looking at examples online and in Sphinx's own docs it seems that the recommendation is to use local image paths without the leading _, i.e. using src/images instead of src/_images.
I'm guessing that _ might be more recommended for sphinx infrastructure reserved paths.

Thanks @glopesdev. The issue (#81) is that Sphinx copies all images (regardless of where they are) into the _images dir, so we end up with duplicate copies of the images (one in the original dir and another in _images). If we drop the leading _, we will end up with duplicate copies of the images again.

The issue (https://github.com/SainsburyWellcomeCentre/aeon_docs/issues/81) is that Sphinx copies all images (regardless of where they are) into the _images dir, so we end up with duplicate copies of the images (one in the original dir and another in _images).

Are you sure the images are being copied from the original dir? Don't forget to clean/delete the html folder to make sure no leftover files are there. Files outside of _static are not usually copied unless they are part of a processing pipeline.
For images that pipeline involves the assets being referenced in the articles and will be copied to _images. As long as the folder is outside of _static they should not be duplicated. I did a quick test which seems to verify this, but I am curious if you are observing something else.

The issue (#81) is that Sphinx copies all images (regardless of where they are) into the _images dir, so we end up with duplicate copies of the images (one in the original dir and another in _images).

@lochhh Are you sure the images are being copied from the original dir? Don't forget to clean/delete the html folder to make sure no leftover files are there. Files outside of _static are not usually copied unless they are part of a processing pipeline.
For images, that pipeline involves the assets being referenced in the articles, and each image will be copied to _images with their URL rewritten in the final output. As long as the image source folder is outside of _static they should not be duplicated. I did a quick test which seems to verify this, but I am curious if you are observing something else.

Thanks @glopesdev you're right. I've now removed the _ and made the same change for the downloadable files (BOM, wiring diagrams, building instructions).


Move resolved_toolchain into the main workspace

Closes #47
Moves the resloved_toolchain rule implementation into the main workspace.
Defines a resolved_toolchain target in the main workspace.
Deletes resolved_toolchain in toolchains_repo.

FYI @kormide I'll start updating this in rules we forked from the template.


User Story - BT11 Bug report details

User Story
As a user,
I want to be able view the details of a bug report,
So that effectively review the bug report and work on resolving the bug.
Acceptance Criteria

[ ] AC1 - The user is able to view the details of a bug report by selecting a details button in the bug report list page.

Feature merged into development via #26


Add support for visibility property. Resolves #146.

Description of the change
This pull request adds support for the visibility property. Mostly a direct port from Clay with the following caveats in mind:

separate is not a valid value: https://github.com/sebastiaanvisser/clay/issues/225
auto is not a valid value: https://github.com/sebastiaanvisser/clay/issues/224
unset is a valid value: https://github.com/sebastiaanvisser/clay/issues/224

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a link to this PR and your username
[x] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation in the README and/or documentation directory
[x] Added a test for the contribution (if applicable)

Thanks for taking a look @thomashoneyman !


Activate Conda and Mamba if possible

Currently we automatically initialize Micromamba. However, when they are installed, we do not automatically initialize Conda or Mamba. Since these tools are so closely related, it seems natural to me that we could extend the activation logic.
This resolves the following error messages.
$ docker run --rm -i mambaorg/micromamba
(base) mambauser@c044080d3465:/tmp$ micromamba install -y -c conda-forge conda
(base) mambauser@c044080d3465:/tmp$ bash
(base) mambauser@c044080d3465:/tmp$ conda activate base
...
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

and similarly for Mamba
$ docker run --rm -i mambaorg/micromamba
(base) mambauser@c044080d3465:/tmp$ micromamba install -y -c conda-forge mamba
(base) mambauser@c044080d3465:/tmp$ bash
(base) mambauser@c044080d3465:/tmp$ mamba activate base
Run 'mamba init' to be able to run mamba activate/deactivate
and start a new shell session. Or use conda to activate/deactivate.

Assuming there are no objections, I'll provide tests at some point.

Anything beyond tests that you have in mind for fleshing this out?

I don't think any documentation in the README.md is needed, but we should have a mention in the CHANGELOG.md.

I would be interested in having this feature as well. Possible to merge?

I'm not sure whether or not @wholtz would be willing to merge without tests. I simply haven't managed to find the time to write any tests. :disappointed:
@hadim if you manage to find some time, you're welcome to write some tests yourself. (I invited you to my fork.)

I have added a test file but it does not work. I am not sure how test activation mechanisms during a Docker build. @wholtz could you help here?

Thanks @hadim for the draft test!
To answer your question: to activate inside the Dockerfile, set ARG MAMBA_DOCKERFILE_ACTIVATE=1. The mechanism for that is in _dockerfile_shell.sh.

Ah, sorry, I see you're already doing that!

The use case I had in mind was for docker run and not docker build. In particular, _activate_current_env.sh is sourced from the entrypoint script.

I tried but I keep having messages for conda and mamba saying I need to init the shell first.

As the PR is currently written,  _activate_current_env.sh will only install the conda  and mamba shell hooks if conda and mamba are in the PATH without any environment activated.  I have added a test that works if conda and mamba are placed in the PATH, but I'm not sure that is going to be aligned with the expectations of users.
I'm curious how @maresb envisioned this feature working. Right now I'm leaning more towards an implementation that expands on the current one, so that when an environment containing conda or mamba is activated, then the shell hooks will get installed immediately after environment activation. This probably also means that if conda and mamba are not in the pre-environment PATH, then on environment deactivation, we would want to remove the conda and mamba shell hooks. I'm not sure if there is a clean way for to trigger the removal of the shell hooks on environment deactivation.

Thanks @wholz for pointing out the inconsistency. I meant to use MAMBA_ROOT_PREFIX in place of CONDA_PREFIX. Does it make more sense now?

I should probably write a few words about the intent of the current implementation, since Bash is so horrendously confusing for me.
The goal is to have conda activate work in the shell spawned by the entrypoint. For example, I want to use this as a base image, install Conda, and allow users to run an interactive shell where conda activate works.
A really nasty Bash pitfall is that running bash -c 'conda activate' will run a non-interactive subshell, so .bashrc won't be sourced, and conda activate will fail. To fix this, we can add -i to the bash command. I'll include a test for this...

I reverted the test I just added... it was working locally, but in CI where there's no TTY it was failing with:
# (from function `assert_output' in file test/test_helper/bats-assert/src/assert_output.bash, line 194,
#  in test file test/conda-mamba-activate.bats, line 24)
#   `assert_output ""' failed
#
# -- output differs --
# expected :
# actual   : the input device is not a TTY
# --

If I were to fix it by also using faketty, then it would be almost identical to my previous test.

@wholtz, is it clear what the current PR accomplishes? If so, is the current test sufficient?

Right now I'm leaning more towards an implementation that expands on the current one, so that when an environment containing conda or mamba is activated, then the shell hooks will get installed immediately after environment activation.

I've thought about it a little, and I still don't quite follow your idea yet. Do you have any particular use case in mind? Also, any idea for how to implement it?

The issue with MAMBA_ROOT_PREFIX and CONDA_PREFIX did have me a bit confused. The use case that I was concerned about works now that the prefix variable has been swapped.

Ugh. I did the merge too fast and did rebase instead of a squashed merge.  Sorry for leaving a messy history on the main branch.

Do you want to force push a reset on main and I can reopen the pr for a squash merge?

No. I don't want to be doing a reset on anything that is in main. Just kicking myself for not paying enough attention.

I think it's extremely unlikely that anyone pulled main in the past 2 hours. And in case anyone did, I think they'd be able to deal with it.


Fix coverage

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fix

What is the current behavior? (You can also link to an open issue here)
nyc ignore .ts files

What is the new behavior (if this is a feature change)?

Other information:

Hey @didierdemoniere thanks for opening a PR! I can't seem to reproduce the issue – the extension settings should already be automatically set by the extends: @istanbuljs/nyc-config-typescript in package.json:
{
  "cache": false,
  "extension": [
    ".ts",
    ".tsx"
  ],
  "exclude": [
    "**/*.d.ts",
    "coverage/**",
    "packages/*/test/**",
    "test/**",
    "test{,-*}.ts",
    "**/*{.,-}{test,spec}.ts",
    "**/__tests__/**",
    "**/node_modules/**"
  ]
}

If you create a new project, do you still see the issue?

I had to manually install @istanbuljs/nyc-config-typescript.

Hi @bitjson, to reproduce this i run: npx typescript-starter then npm run cov inside the project.
is @istanbuljs/nyc-config-typescript installed globally on your setup ?

@didierdemoniere thanks for responding! (And thank you to @mrGibi too.) You were right – the package was being removed on install by the CLI. I credited you in https://github.com/bitjson/typescript-starter/commit/710bf3e871ee162f3f7bdbfb1438c9b6130562e1, released as v2.4.7.

thanks @bitjson. This package is a huge time saver, keep up the good work.


FLA-764 re-implement Package Confirmation file list

Description
This PR includes the following proposed change(s):
https://justice.gov.bc.ca/jira/browse/FLA-764

Re-implemented the file list on the Package Confirmation screen
Refactored to smaller sub-components

Eventually, its would be nice to have the Package Review screen use the same sub-components. We'll do this on a separate PR to keep them smaller.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
yarn lint
yarn test
Does the change impact or break the Docker build?

[ ] Yes
[x] No

Checklist:

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

Agree with you on the component for the list @KDNeufeld


option to deploy to website bucket

Closes https://github.com/cloudposse/terraform-aws-cicd/issues/88

/test all

/rebuild-readme

/test all


Resize Simulation Control

The simulation framebuffer should be resizable to allow for higher resolution simulation. It doesn't necessarily need to match the screen resolution, because the canvas already scales itself independently of the framebuffers. Also, if it did match the canvas size there would have to be a solution to prevent resize or orientation changes from clearing or disrupting parts of the canvas.
The simulation itself is fixed at 256 pixels square. This was mainly chosen because any higher with the current number of iterations caused bad performance on mobile. The default should probably be kept at 256. But, it would be nice to have either a numeric input or a fixed radio group with a few sizes to choose from, so if you were on desktop you could access higher resolution choices.

It may be good to use Screen.width to guess whether a device might be something like a phone. So it could set the default based on that guess.
That way, desktop could get a nice high resolution simulation and mobile would get one that runs speedily, by default.


Upgrade acvm to v0.9.0

Problem
Version 0.9 of acvm has been released here: https://github.com/noir-lang/acvm/pull/182
Proposed solution
Upgrade to v0.9
This is blocked by backends being updated to v0.9. See https://github.com/noir-lang/aztec_backend/issues/104
Alternatives considered
No response
Additional context
No response
Submission Checklist

[X] Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

This has to happen with UP so I'm assigning to me.


Add support for profiling Flexmeasures

Currently, Flexmeasures has no support for profiling. This makes it difficult to identify and analyze performance bottlenecks in the code as the application matures.
Some proposed solutions are

Integrate pyinstrument in Makefile:
Integrate pyinstrument into the Makefile allowing the developer to call make with appropriate commands to start flexmeasures with profiler attached.
A possible target in Makefile can be make run-profiler
This calls the profiler which in turn starts flexmeasures.  Can be run to profile the entire application.

Integrate pyinstrument as a part of the pytest suite or CI:
Integrate the profiler to benchmark and profile critical parts of the code and automatically generate profile reports which can be quickly viewed by the developer to check the impact on performance.

Closing this as #722 enable us to use it. Not sure if we ever want the pytest integration, as well.


[Master to v0_10] Fix n-m db access in ProjectResource.getProjects to add projectsWithLatestRevision

#1187

Rebase to the latest v0_10 branch.

Rebase to the latest v0_10 branch again.
CI passed.


[Minor] Add assert to test to test something

What changes were proposed in this pull request?
Add assert to test so it tests something.
Why are the changes needed?
Tests should contain at least one assert and test things.
Fix: # (issue)
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Built and tested locally.

@justinmclean please check all the places that need to be fixed, not just a one-line fix here.

Close this PR as it has no update for a long time. Please re-open if needed.


feat: Add hollow triangle pattern #34

@Reynadi531 if there's any change required let me know

@Reynadi531 How about now ?

Awsome thanks for contribute


Alarm programming

Hi,
It seems to me than a FOSS app forked from ASOP Clock app that implement complete functionalities of Google Clock and more is just indispensable.
So thank a lot for your app.
Speaking of that, if I'm not mistaken, programming option of Google Clock is missing. It's a must have function for me, so I'll be more than happy to replace my not FOSS Google Clock by this one if it's implemented.

Thank you for your compliment. I do the best I can even if unfortunately I don't have enough knowledge to do some things. 😬
I'm closing this topic because it's a duplication with #4 where unfortunately I need help to implement this addition.


Add optional fastq-screen step

Since we run NGI QC for all samples that we sequences, including RNA, it would save us CPU time if we could run fastq-screen as a part of the pipeline. This would have to be optional, since most other users likely won't have a use for this.

For the record, I don't really like this idea as I think it will be confusing to have conflicting alignment rates in the same MultiQC report..

Fair point, and in addition to the things we discussed earlier I don't see this happening.


mvn package results test errors

[x] installed jdk 8
[x] installed maven
[x] added my github token to application.properties

I managed to resolve some weird 404 error by adding -Dapitoken=mygithubtoken as suggested in #2 but I can figure out what's wrong here
attached is what's returned from mvn -DapiToken=github_token -e -X package
github-matrix.log

okay, I managed to run it locally, so I'm adding some comments here for future reference, or whoever comes here in the future for help:

Even if jdk 8 is installed, it does not automatically change jdk version to 8 (as of writing on 2024. Jul. 02, newest version seems to be openjdk-21-jdk), so you might want to set your JAVA_HOME variable, in my case the command ran like export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-armhf. It fixed my issue above.
java also won't update automatically so I had to run update-java-alternative -s java-1.8.0-openjdk-armhf with sudo previlege.
you also might want to set port in case of remote access; I set it in github-matrix/src/main/resources/application.properties with server.port=[desired port number] at the bottom (under where apiToken is supposed to be added, according to the document). Port forward also is required.


⚠ TorrentLeech has degraded performance

In 63141ad, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 4698 ms

Resolved: TorrentLeech performance has improved in b8f59c7 after 6 minutes.


By use of Python package, at action cpp-linter is not found

I followed Running without the docker container hopefully correct and in my action I have:
jobs:
  cpp-linter:
    runs-on: ubuntu-22.04
    steps:
...
    - name: Install conan package manager and cpp-linter
      run: |
        python -m pip install --upgrade pip
        pip --disable-pip-version-check --no-cache-dir install wheel conan \
          git+https://github.com/cpp-linter/cpp-linter-action@v1
...

    - name: Run cpp-linter (clang format && tidy)
      id: linter
      run: |
        cpp-linter --version=14 --style=file --tidy-checks='' --ignore=build --database=build/ci-linux-clang

which results to:
Run cpp-linter --version=14 --style=file --tidy-checks='' --ignore=build --database=build/ci-linux-clang
  cpp-linter --version=14 --style=file --tidy-checks='' --ignore=build --database=build/ci-linux-clang
  shell: /usr/bin/bash -e {0}
  env:
    CONAN_V2_MODE: 1
/home/runner/work/_temp/405c3607-29ac-42c3-af1e-b4afbe18453f.sh: line 1: cpp-linter: command not found
Error: Process completed with exit code 127.

The info in setup.py recently moved to pyproject.toml. Was there any warnings or errors when installing the pkg with pip? Can I see the workflow log?

https://github.com/cpp-linter/cpp-linter-action/blob/92298bd41cc62a33375a77a515e64bb3daf30fc4/pyproject.toml#L2
I may have to upgrade the setuptools requirement to >=v61. It would also help to know what version of Python you're using.
The pkg is now available on PyPI, so you just install it (faster) from there:
pip install cpp-linter

The cpp-linter related GH action workflow log is here: 3_Install conan package manager and cpp-linter.txt
The python version is
-- Found Python3: /usr/bin/python3.10 (found version "3.10.4") found components: Interpreter

what I've got from CMake. I've not seen any other errors.
Please note, that I'm not familiar with Python's infrastructure, more C++ :) How to install from PyPI? The default location doesn't seem to have these update you mentioned above.

In your build logs it does state that it installed a pkg titled UNKNOWN:
Installing collected packages: UNKNOWN, pluginbase, patch-ng, node-semver, distro, bottle, urllib3, tqdm, python-dateutil, PyJWT, fasteners, conan
Successfully installed PyJWT-2.4.0 UNKNOWN-1 bottle-0.12.23 conan-1.52.0 distro-1.6.0 fasteners-0.17.3 node-semver-0.6.1 patch-ng-1.17.4 pluginbase-1.0.1 python-dateutil-2.8.2 tqdm-4.64.0 urllib3-1.26.12

Given that our cpp-linter pkg isn't listed there, I have to assume UNKNOWN is our cpp-linter pkg.
When I downgrade my local env version of setuptools to v45, I get a result:
pip install git+https://github.com/cpp-linter/cpp-linter-action@v1
...
Installing collected packages: cpp-linter
Successfully installed cpp-linter-1

But it shouldn't be named cpp-linter-1, and I can still execute cpp-linter -h afterwards. So, I think this is still related to https://github.com/cpp-linter/cpp-linter-action/issues/94#issuecomment-1232906182. I just wish I could fully reproduce this "cpp-linter not found" problem.
Either way, installing the pkg from PyPI (pip install cpp-linter) should not have this problem because the package on PyPI is already built and doesn't require setuptools to install.

Ok, thanks! I'm using pip install cpp-linter for now and it's working as expected. So I'll close the issue.


MDC Usage regression

Hello,
Currently i'm using Slf4j version 2.0.11 and Logback version 1.4.14
I'm working on an old products with a lot of code and using a lot of thread, so I need to have MDC properties thread inheritance. So I force the usage of a BasicMDCAdapter by setting the MDC.mdcAdapter to new BasicMDCAdapter() when my program starts.
The problem is that, using Slf4j version 2.0.11 and Logback version 1.4.14 this doesn't work anymore.
I don't have any MDC info in my logs.
Could you please tell me what is the correct way to use your BasicMDCAdapter ? or tell me another way to have MDC properties thread inheritance ?
Many thanks

Off the top of my head, the idea is to get a copy of the MDC map from the parent thread, pass it to the child thread and have the child thread insert it into the MDC programmatically.

Doing it programmatically is an extreme solution, since it is an old project with millions of lines of code. I am looking for a solution that will avoid modifying the entire project.

Which version of logback are you upgrading from?

I upgraded from logback 1.2.9 and slf4j 1.7.26. we made an adaptation to use the MdcAdapterReplacer like this
MdcAdapterReplacer.replaceMdcAdapter(new BasicMDCAdapter());
and it worked fine. but with the upgraded version it no longer works.

Hello @pauljean
I am unfamiliar with MdcAdapterReplacer. Do you have a reference?

it's just an adaptation, which allowed us to update the context. with the upgrade it no longer works.
Map<String, String> oldMap = MDC.getCopyOfContextMap();
MDC.mdcAdapter = new BasicMDCAdapter();
if (oldMap != null) {
MDC.setContextMap(oldMap);
}

In more recent versions of logback, the MdcAdapter that you wish to use needs to be attached to the LoggerContext as well, in addition to MDC.mdcAdapter.
See LogbackServiceProvider, lines 44 or so.

Here is a test that allows to reproduce the problem.
run ./compile.sh and ./run.sh
java-slf4j-test.zip

If you set  you will see this printed:
22:43:07,129 |-ERROR in ch.qos.logback.classic.LoggerContext[default] - mdcAdapter cannot be set multiple times java.lang.IllegalStateException: mdcAdapter already set
        at java.lang.IllegalStateException: mdcAdapter already set
        at      at ch.qos.logback.classic.LoggerContext.setMDCAdapter(LoggerContext.java:418)
        at      at Main.main(Main.java:40)

So it looks like the code prevents the mdcAdapter from being set anew. I have to think about relaxing this hurdle.

we don't understand why you locked the code to prevent a new definition of the MDCAdapter. It will be very useful if you relax the definition of the MDCAdapter. thank you for keeping us informed
Many thanks


Moved contents from wiki to demo bundle docs

Closes #18.

These changes are already in master. Weird stuff.


Support search on facets NULL values

Updated the code to support search on facets NULL values.

So far, the NULL values were excluded from the facets sidebar search page.
As the ermrest /attributegroup request is returning also the NULL distinct value, it can be added to the facets sidebar search page.
The ermrest predicate for NULL values is col::null::.
The label for the checkbox representing the IS NULL predicate is an empty string and it is displayed at the end of the facet's values, as the ermrest sort() function returns the NULL values at the end.
Known limitation: a filter can not be applied any more to a text column having the null string value (predicate col=null), as it translates now in the col::null:: predicate.


use last instead of end for calculating line count

Using end messes up the formatting if the span goes to the end of the line (with end at the start of the next line)
Before:

After:

Using:
let input = "white
             space";
let mut formatter = source_span::fmt::Formatter::new();
formatter.add(
    Span::new(
        Position::new(0, 0),
        Position::new(0, 4),
        Position::new(1, 0),
    ),
    Some("Plain Text".to_string()),
    source_span::fmt::Style::Note,
);

let chars = input.chars().map(|char| Ok(char));
println!(
    "{}",
    formatter
        .get(
            chars,
            Span::new(
                Position::new(0, 0),
                Position::new(1, 22),
                Position::new(1, 23),
            ),
        )
        .unwrap()
);

ping @timothee-haudebourg

Nice catch!
Sorry for the delay.
I'll try to publish the next version with this fix soon. Thanks for your contribution.

Your changes are included in the version 1.4.0 that I just published.


add a flag to allow tutorials to show blocks collapsed in hints, template code

e.g. so if you have a template section in a tutorial like the following it starts off collapsed in order to 'hide' it from view at the start (or if you want to show it exists in a hint, but not in detail)
No bug associated, just a very quick feature that came out of a chat with kiki~

Maybe we could even emit this so collapsed / non collapsed state persists through compile / decompile ;)

This is going to be so helpful in trying to wean off of magic blocks.  Thanks so much, @jwunderl !


SoloCam E40 rapid battery drain when add-on enabled

Describe the bug
The battery for the SoloCam E40 is drained in a few hours when add-on is enabled.
To Reproduce
I have a Eufy 2K Doorbell and SoloCam E40. Both seem to work fine with the add-on. However the battery of the SoloCam E40 is drained from 100% to 0% in just a few hours once the add-on is enabled. Prior to installing the add-on I had the SoloCam running fine for a few months, so am confident it's not a hardware fault. However, if I check the logs I can see the add-on repeatedly connecting and disconnecting from the SoloCam multiple times each minute. I would imagine it's this behaviour that is draining the battery.
Expected behavior
Functionality wise the add-on seems to work with the SoloCam E40, and entities are populated correctly. It seems this connecting/disconnecting behaviour could be the cause of the battery drain though?
Screenshots/logs
2021-12-02 15:20:22.278  INFO Eufy Security server listening on port 3000
2021-12-02 15:20:24.179  INFO Connected to station T8010P23211226D3 on host x.x.x.x and port 11265
2021-12-02 15:20:24.855  INFO Push notification connection closed
2021-12-02 15:20:24.989  INFO Push notification connection successfully established
2021-12-02 15:20:27.489  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 28588
2021-12-02 15:20:30.215  INFO Push notification connection successfully established
2021-12-02 15:20:37.385  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:20:46.181  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 25130
2021-12-02 15:20:55.945  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:21:05.040  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 18840
2021-12-02 15:21:14.184  WARN Station T8010P23211226D3 - Heartbeat check failed. Connection seems lost. Try to reconnect...
2021-12-02 15:21:14.185  INFO Disconnected from station T8010P23211226D3
2021-12-02 15:21:15.032  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:21:19.857  INFO Connected to station T8010P23211226D3 on host x.x.x.x and port 16090
2021-12-02 15:21:20.265  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 17707
2021-12-02 15:21:29.924  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:22:04.968  WARN Station T8131N63212326AB - Tried all hosts, no connection could be established
2021-12-02 15:22:04.968  INFO Timeout connecting to station T8131N63212326AB
2021-12-02 15:22:19.407  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 22940
2021-12-02 15:22:29.168  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:22:37.792  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 19281
2021-12-02 15:22:47.618  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:22:56.493  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 18824
2021-12-02 15:23:06.206  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:23:15.231  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 18199
2021-12-02 15:23:25.000  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:23:34.136  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 25216
2021-12-02 15:23:43.931  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:23:52.774  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 29405
2021-12-02 15:24:02.534  INFO Disconnected from station T8131N63212326AB
2021-12-02 15:24:11.692  INFO Connected to station T8131N63212326AB on host <IP_ADDRESS> and port 14104
2021-12-02 15:24:21.513  INFO Disconnected from station T8131N63212326AB
(This repeats continuously. Obfuscated some public IP addresses)
**Hardware Information about Home Assistant
Home Assistant 2021.11.5 running in a VMware ESXi Virtual Machine.
**Hardware Information about Cameras

SoloCam E40
Live Streaming Protocol: N/A

Additional context
The SoloCam E40 in the logs appears to be 'T8131N63212326AB '.
My 2K doorbell and HomeBase 2 is 'T8010P23211226D3'. This works fine so can be ignored I believe.

Can you please move this here? https://github.com/bropat/eufy-security-client/

Apologies if this is in the wrong place. I've copied the issue to the new repo. Feel free to remove this, or would you like me to do so? Thanks

no worries it is fine, please share the link here for new issue and resolve. I am also closely following other repositories.

https://github.com/bropat/eufy-security-client/issues/74


How to trigger system.cron_trigger() or system.cron_flush() automatically on APItools UI.

I've just installed the APItools monitor in my server according to On-Premise APItools Monitor. After adding a service, I can't see any traces on the "Traces" tab when I access my local APIs.
After diving into the source code of monitor, I found that traces are saved here:
# lua/models/pipeline.lua
Trace:async_save(trace, ...)

Trace:async_save() enqueue the trace object which will be actually saved later by Model:consume(). And then, Model:consume() is called by system.cron_trigger() or system.cron_flush().
Finally, I found the route mapping here:
# lua/apps/api.lua
router:post(   '/api/system/cron/flush'                      , r('system.cron_flush'))
router:post(   '/api/system/cron'                            , r('system.cron_trigger')) -- async

I said god bless me when I am trying to POST to "/api/system/cron" manually, it did work! When I access my APIs, traces are generated and shown in list. Thank godness!
But my quessions here are:

How to trigger the  POST action on APItools UI?
How to save traces automatically without extra manual work?

Hi Russel,
Every monitor has several separate "threads" (it's more complicated than that, but it's a good enough approximation).
One of the threads is in charge of dealing with presenting the website and responding to the API. Another one is in charge of acting as a "proxy" - it's the one which receives requests, puts them through the middleware, calls the API, and returns the transformed responses.
There is a third one which is in charge of running background jobs. Its code is here:
https://github.com/APItools/monitor/blob/master/lua/crontab.lua
As you can see, this background thread does a bunch of things, not only saving the delayed traces.
The background thread is initialized here: https://github.com/APItools/monitor/blob/master/config/global.conf#L8-L12. Nginx should have kept it alive, but it seems that in your particular case it has died.
This has happened a couple times before in some of our workers (we have hundreds of them). It's frustratingly difficult problem to reproduce since it happens so infrequently. Still, we're investigating how to prevent it.
In the meantime, the only way to revive the background jobs is to re-launch nginx. If you have installed it on-premise with the deb package you should be able to do so using supervisor:
$ sudo supervisorctl restart openresty

That should re-start the background jobs and get the traces saved automatically. If that doesn't work, you can try restarting supervisor (sudo service supervisor restart). A last thing to try would be rebooting (sudo reboot). Let's hope you don't need to get to that.
Please let me know how it goes.
Regards,
Enrique

Thanks for your detailed reply, kikito!
After changing the log level of nginx to info:
# config/nginx.conf
error_log stderr info;

I found this message in the log file:
2015/04/01 22:10:59 [info] 218#0: [lua] crontab.lua:348: run(): [cron] skipping run of async_traces job async_traces-A486BC47-05D4-40AC-80CA-89471C56609E: slug name not set, context: ngx.timer

which is obviously caused by the failure of this condition:
https://github.com/APItools/monitor/blob/master/lua/crontab.lua#L340-L340
Since the value of crontab.enabled() is determined by three factors:
https://github.com/APItools/monitor/blob/master/lua/crontab.lua#L332-L332
and the value of crontab.forced is determined by the environment variable SLUG_CRON_FORCED:
https://github.com/APItools/monitor/blob/master/lua/crontab.lua#L369-L369
so I set SLUG_CRON_FORCED to 1:
# config/env.conf
env SLUG_CRON_FORCED=1;

Then, everything works well now.
But I still have some questions:

What's the difference among crontab.disabled, crontab.forced and slug_name?
Is this the correct way for me to set SLUG_CRON_FORCED to 1 to make crontab.initialize() work?
I also found crontab.initialize() executed two times, first triggerd in "config/nginx.conf", then trigger near the end of "lua/crontab.lua". Why?

This should be fixed by #53. If it is not, please reopen the issue.
Cron now runs all the time, not checking any environment variables.


[Question] how to config it to support pnpm link and file protocol

You can try something like this:
  "path-autocomplete.transformations": [
    {
      "type": "inputReplace",
      "parameters": ["^link:", "", "g"],
      "when": {
        "path": "link:.*"
      }
    }
  ]

Works fine, thanks @mihai-vlc
    "path-autocomplete.transformations": [
        {
            "type": "inputReplace",
            "parameters": ["^(link|file):", "", "g"],
            "when": {
                "path": "^(link|file):.*"
            }
        }
    ],


Not Compatible r.js Optimization Tool

Because the script has more than one define() call, r.js says:
svg.js has more than one anonymous define. May be a built file from another build system like, Ender. Skipping normalization.

This PR should fix it https://github.com/wout/svg.js/pull/312


fix: Reconcile amundsengremlin descriptions with the Databuilder

Signed-off-by: Andrew Ciambrone<EMAIL_ADDRESS>
Summary of Changes
Changes the description's source to be description_source like in the databuilder:
https://github.com/amundsen-io/amundsendatabuilder/blob/master/databuilder/models/table_metadata.py#L125
Adds the Vertex type Programmatic Descriptions.
Changes the behavior of make_description_uri
to be similar to the databuilders:
https://github.com/amundsen-io/amundsendatabuilder/blob/master/databuilder/models/table_metadata.py#L176-L183
CheckList
Make sure you have checked all steps below to ensure a timely review.

[X] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[X] PR includes a summary of changes.

there are CI errors.

👍 Should be all set @feng-tao


Add Getting Started Section

Addresses #83
Added the Getting Started Section. I have nested it as:
Getting Started
- Getting Started with refine.bio dataset
- Getting Started with Species Compendia
But can make it flatter structure if needed.
Getting Started with refine.bio dataset section contains same content as https://github.com/AlexsLemonade/refinebio/blob/dev/workers/README_DATASET.md. It is slightly restructured so it makes sense in this context.

Filled in the species compendium section per our in person discussion @dvenprasad. I think we should include a structure diagram in that section as well, how does that sound?


ultrablue-server: init at unstable-2023-01-25

Description of changes
https://github.com/ANSSI-FR/ultrablue
Ultrablue is a remote attestation (TPM2) server which uses Bluetooth to perform the verification with a Bluetooth client pre-enrolled, usually your phone.
In an upcoming PR, I will add an integration for systemd stage 1 and legacy stage 1.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@SuperSandro2000 The commit message was wrong… :P I'm at fault for not putting it in draft while I was working on it.


Pagination support (NOT READY TO MERGE)

This PR is a partial solution for #100. Only project pagination has been implemented. The reason for submitting a partial solution is to enable discussions before implementing pagination for all resource types.
Notes:

I see a number of options for obfuscating page tokens:

Don't
Encode with e.g. base64
Encrypt the tokens using a key that is only known to the server

The memstore backend uses option 1in this PR (for simplicity).
The postgres backend uses option 2 in this PR.
Clair uses option 3.
I started out with option 3 but figured I would keep it simple until I got some feedback. What is the preferred option   for the postgres backend? Is there any best practice at google?

I added a ListOptions struct to keep the number of parameters down. Not sure if this was an improvement or not. Feedback welcome.

We might have to add new db indexes if the upcomming filtering functionality will support ordering.

You should probably use fernet rather than base64 to avoid leaking primary keys from the database. This is what clair uses.

Sorry - I wasn't clear, I meant an encrypted base64 encoded string. fernet also looks fine.
Agree that we need to support migrations, we'll eventually get to that point :)

Ok. I'll add page token encryption.

@furuholm is this ready for another look?

@R2wenD2 I haven't got around to it. I will try to get some time to do it during this week. Do you have other work that is being held up by this?

no blockers on my part. just wanted to make sure you weren't waiting on me for a review :)

Tokens are now encrypted using fernet-go.
Will keep this PR open until we are satisfied with project pagination. Will create a new PR that adds pagination for the other entity types.

@vtsao: I've pushed fixes that addresses your comments, but I didn't rebase the changes so there are a a bunch of other things that has been added to this PR that really should be put in a new PR. You can ignore them for now if you want to.

I've created a new PR #115 where I have squashed and rebased the commits.
(I've pushed all of the commits that was squashed into #115 to this PR if anyone prefers reviewing individual changes.)


Realm: PendingCompletion::invoke_local_completions assertion

I am hitting this assertion on Perlmutter at 96 and 128 nodes:
s3d.x: /global/u1/s/seshu/legion_s3d/legion/runtime/realm/gasnet1/gasnetmsg.cc:3233: bool PendingCompletion::invoke_local_completions(): Assertion `(prev_state & LOCAL_PENDING_BIT) != 0' failed.

Here is a stack trace:
[127] Thread 6 (Thread 0x7fe9523fc700 (LWP 129402) "s3d.x"):
[127] #0  0x00007fe96cb07157 in waitpid () from /lib64/libc.so.6
[127] #1  0x00007fe96ca846af in do_system () from /lib64/libc.so.6
[127] #2  0x00007fe9669cd829 in gasneti_system_redirected () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #3  0x00007fe9669cdee8 in gasneti_bt_gdb () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #4  0x00007fe9669d16ac in gasneti_print_backtrace () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #5  0x00007fe9661d5907 in gasneti_defaultSignalHandler () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #6  <signal handler called>
[127] #7  0x00007fe96ca77360 in raise () from /lib64/libc.so.6
[127] #8  0x00007fe96ca78941 in abort () from /lib64/libc.so.6
[127] #9  0x00007fe96ca6fa5a in __assert_fail_base () from /lib64/libc.so.6
[127] #10 0x00007fe96ca6fad2 in __assert_fail () from /lib64/libc.so.6
[127] #11 0x00007fe9664f5776 in PendingCompletion::invoke_local_completions (this=this@entry=0xb49e230) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/gasnet1/gasnetmsg.cc:3233
[127] #12 0x00007fe9664f5ac8 in PendingCompletionManager::invoke_completions (this=0x7fe966f16da0 <completion_manager>, index=<optimized out>, do_local=<optimized out>, do_remote=<optimized out>) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/gasnet1/gasnetmsg.cc:3396
[127] #13 0x00007fe9669ca77b in gasnetc_ofi_poll () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #14 0x00007fe9669bee59 in gasnetc_AMPoll () from /global/homes/s/seshu/legion_s3d/legion/language/build/lib/librealm.so.1
[127] #15 0x00007fe9664f7bab in _gasneti_AMPoll () at /global/u1/s/seshu/legion_s3d/gasnet/release/include/gasnet_help.h:1310
[127] #16 _gasnet_AMPoll () at /global/u1/s/seshu/legion_s3d/gasnet/release/include/gasnet_help.h:1523
[127] #17 EndpointManager::do_work (this=0xb37c5a0, work_until=...) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/gasnet1/gasnetmsg.cc:2825
[127] #18 0x00007fe9663c7349 in Realm::BackgroundWorkManager::Worker::do_work (this=0x7fe9523f8a00, max_time_in_ns=<optimized out>, interrupt_flag=0x0) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/bgwork.cc:621
[127] #19 0x00007fe9663c7b71 in Realm::BackgroundWorkThread::main_loop (this=0xb256fd0) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/bgwork.cc:125
[127] #20 0x00007fe9664a9d8f in Realm::KernelThread::pthread_entry (data=0xb451f80) at /global/u1/s/seshu/legion_s3d/legion/runtime/realm/threads.cc:774
[127] #21 0x00007fe965ca1539 in start_thread () from /lib64/libpthread.so.0
[127] #22 0x00007fe96cb39e0f in clone () from /lib64/libc.so.6

Using gasnetex works on Perlmutter.


pull request for e2e test at 11/07/2016 10:45:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


pick up origin-master-api and origin-master-controllers journals

@stevekuznetsov @smarterclayton fyi

@jim-minter thanks, LGTM


GestureRecognizers not working when a TextSpan wraps another TextSpan

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Create a TextSpan that wraps another TextSpan and place a TapGestureRecognizer on that, like so:
TextSpan(
  recognizer: TapGestureRecognizer()
    ..onTap = () {
      print('Was able to tap');
    },
  children: [
    Text('Inner Span', style: TextStyle(color: Colors.red)),
  ],
)

Notice that on tapping the outer-span, nothing get's printed on the console.
Expected results
It should recognize the tap on the TextSpan and print to the console
Actual results
Nothing happens
Code sample
Complete code can be pasted in https://dartpad.dev directly
import 'package:flutter/material.dart';
import 'package:flutter/gestures.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Text.rich(TextSpan(
            children: [TextSpan(text: 'Hello World')],
            recognizer: TapGestureRecognizer()
              ..onTap = () => print('Hello World'),
          )),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
❯ flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on macOS 14.0 23A344 darwin-arm64, locale
    en-IN)
    • Flutter version 3.13.6 on channel stable at
      /Users/pavanpodila/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (2 weeks ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from:
      https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK
      components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup
      for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup
      for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.2)
    • IntelliJ at /Users/pavanpodila/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 75.1.4
    • Dart plugin version 232.9559.10

[✓] IntelliJ IDEA Ultimate Edition (version EAP IU-233.9102.97)
    • IntelliJ at /Users/pavanpodila/Applications/IntelliJ IDEA Ultimate 2023.3
      EAP.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • iPhone 15 (mobile) • ADA60AA2-613A-4F33-ACDC-2D327412498F • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)    • macos                                • darwin-arm64
      • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)       • chrome                               • web-javascript
      • Google Chrome 117.0.5938.149

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Hi @pavanpodila. Thanks for filing this. From the documentation, this seems to be the expected behaviour.

A gesture recognizer that will receive events that hit this span.
[InlineSpan] itself does not implement hit testing or event dispatch. The object that manages the [InlineSpan] painting is also responsible for dispatching events. In the rendering library, that is the [RenderParagraph] object, which corresponds to the [RichText] widget in the widgets layer; these objects do not bubble events in [InlineSpan]s, so a [recognizer] is only effective for events that directly hit the [text] of that [InlineSpan], not any of its [children].

The recognizer is only effective on the text and not on any of its children.
Closing this as this seems to be its expected behaviour, if you disagree please comment and I'll reopen this.
Thank you!

Ok... @dam-ease I guess by text I understood as the children with text...got it.


Added => Maths_And_Stats => Algebra => Factorial => Python

Assigned Issue Number ?
#279
Language Opted ?
Python
Number of files added or updated ?
1
Name of these files ?
Maths_And_Stats => Algebra => Factorial => factorial.py
Checklist

[x] I've read the contribution guidelines.
[x] I've referred the correct issue number.
[x] I've fill up this entire template correctly.

Thank you for accepting my code.
Cheers!😄


Question: why expire the scheduler key?

Can someone enlighten me as to what is the purpose of expiring the scheduler key?
We've created a script that does everything Scheduler.run() does, but in addition, it processes another type of job during each iteration of the master while True loop:
        scheduler = get_scheduler(name=queue, interval=options.get('interval'))

        scheduler.log.info('Running RQ scheduler...')
        scheduler.register_birth()
        scheduler._install_signal_handlers()
        try:
            while True:
                # Enqueue `rq-scheduler`'s scheduled jobs
                scheduler.enqueue_jobs()
                time.sleep(scheduler._interval)

                # Perform another scheduling task here
                do_task_b()
        finally:
            scheduler.register_death()

If my understanding is correct, the top portion of the while True loop checks for rq scheduling jobs which are due, enqueues any as necessary, then sleeps scheduler._interval seconds (e.g. 60 seconds in the default case).
After the time.sleep call, scheduler._interval seconds have elapsed, which means that the scheduler_key Redis key is set to expire in 10 more seconds (because of the call to StrictRedis.expire here)
So, am I correct in my understanding that if do_task_b() takes more than 10 seconds, the scheduler_key will be expired by the time we iterate once more on the master while True loop?
Why do we want to expire the scheduler_key at all? Isn't this the index for all scheduled jobs?

The index for all scheduled jobs is different
class Scheduler(object):
    scheduler_key = 'rq:scheduler'
    scheduled_jobs_key = 'rq:scheduler:scheduled_jobs'

If do_task_b() takes more than scheduler._interval, scheduler_key will indeed expire and it will become possible to bring up a second scheduler and mess things up. The original run() method doesn't have any additional tasks so the algorithm seems sound. The key might also expire if enqueue_jobs() takes to long, but that'd be an indication of a different problem. Why would you need to do a long-running task there anyway?

This makes sense, thanks for the explanation.
The idea was to save money on Heroku by running, in a single app, the infinite loops for two of our scheduling systems. If it causes problems with the design used by rq-scheduler, I think the next best thing is implementing both loops as threads in the same process, for greater isolation.

That is possible, just keep in mind that scheduler._install_signal_handlers() can only be done in the main thread. Or you could try multiprocessing. I did a similar thing with multiprocessing once.


chore: fix example usage of indy-sdk-react-native package to show correct usage

Just cosmetic fix. But can be misleading, so best to fix

Codecov Report

Merging #1382 (ccc6c7a) into main (a4204ef) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1382   +/-   ##
=======================================
  Coverage   87.27%   87.27%
=======================================
  Files         780      780
  Lines       18706    18706
  Branches     3210     3210
=======================================
  Hits        16326    16326
  Misses       2373     2373
  Partials        7        7

Impacted Files
Coverage Δ

packages/indy-sdk/src/IndySdkModuleConfig.ts
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix VisualStudio throwing multiple C4996 warnings in vulkan_context.cpp.

Use Godot's String to concatenate C-strings instead of strcat and sprintf, which are unsafe, because they don't check for buffer overflows.

looks good, I just did copypasta from the official example, so improving this is nice

Thanks!


Error installing package - attribute 'jless' in selection path 'nixos.jless' not found

Describe the bug
When I try to install jless as described on the NixOS Search Packages I get an error.
Steps To Reproduce
Steps to reproduce the behavior:

Copy installation command from the NixOS package search to install jless (see link above)
Paste the command into the command shell

❯ nix-env -iA nixos.jless
error: attribute 'jless' in selection path 'nixos.jless' not found

Expected behavior
jless is installed.
Notify maintainers
@jfchevrette
Metadata
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.16.8, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos-21.11.336020.2128d0aa28e"`
 - channels(max): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Guessing you have to update

 - channels(root): `"nixos-21.11.336020.2128d0aa28e"`

Your channel seem to be up-to-date as of Feb 16, 2022 at commit https://github.com/NixOS/nixpkgs/commit/2128d0a
jless was backported to 21.11 on Feb 17 in commit https://github.com/NixOS/nixpkgs/commit/b68340cbd4165c48c1cdf025009018dc0de7ee7f
Update and jless should become available to install


[release-1.14] revert PR #38659

Manual cherrypick required.
#38826 failed to apply on top of branch "release-1.14":
Applying: revert PR #38659
Using index info to reconstruct a base tree...
M	pkg/config/analysis/local/istiod_analyze.go
Falling back to patching base and 3-way merge...
Removing releasenotes/notes/38659.yaml
Auto-merging pkg/config/analysis/local/istiod_analyze.go
CONFLICT (content): Merge conflict in pkg/config/analysis/local/istiod_analyze.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 revert PR #38659
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

resolved by https://github.com/istio/istio/pull/38863


Question: What am I missing here?

I'm trying to leverage AsyncKeyedLock to "debounce" some API calls coming from the outside. I want to lock on the Guid Id of the incoming object. The library seems straight-forward, but I wrote a test to try to simulate our situation just to be sure, and I can't get it to act the way I think it should. Here's an isolated test to illustrate what I'm seeing.
    [Test]
    public void ParallelVersion()
    {
        var output = new ConcurrentQueue<(int Ordinal, long Start, long Stop)>();
        var stopwatch = Stopwatch.StartNew();

        Parallel.Invoke(
            () => ProcessEntry(Guid.Parse("00000000-0000-0000-0000-000000000000"), 0).Wait(),
            () => ProcessEntry(Guid.Parse("00000000-0000-0000-0000-000000000000"), 2).Wait(),
            () => ProcessEntry(Guid.Parse("00000000-0000-0000-0000-000000000000"), 4).Wait(),
            () => ProcessEntry(Guid.Parse("11111111-1111-1111-1111-111111111111"), 1).Wait(),
            () => ProcessEntry(Guid.Parse("11111111-1111-1111-1111-111111111111"), 3).Wait(),
            () => ProcessEntry(Guid.Parse("11111111-1111-1111-1111-111111111111"), 5).Wait()
        );

        return;

        async Task ProcessEntry(Guid id, int ordinal)
        {
            using (await SUT.LockAsync(id.ToString()))
            {
                var start = stopwatch.ElapsedMilliseconds;
                Console.WriteLine($@"Processing ordinal {ordinal} at {stopwatch.ElapsedMilliseconds}");
                Thread.Sleep(1000);
                var stop = stopwatch.ElapsedMilliseconds;
                output.Enqueue((ordinal, start, stop));
                Console.WriteLine($@"Processed ordinal {ordinal} at {stopwatch.ElapsedMilliseconds}");
            }
        }
    }

What I expect to see is that none of the even numbered entries should be processed at the same time, and the same for the odds. I expect one of the evens to start processing, and the other two to wait in line. Meanwhile, one of the odds should also start processing while the other two wait in line. When the first even/odd pair have finished, I would expect another two to get picked up, and so on.
I don't really expect to see them line up 0-5 in the output because Parallel.Invoke isn't going to guarantee order. What I'm seeing in the output queue, though, is that every single entry started processing at the exact same time. It could be that I'm outrunning the library's lock itself, in which case I'm out of luck. The other day we saw two identical calls to our API 2ms apart, so that's the kind of timing I'm trying to guard against. Any guidance would be appreciated.

Hi,
For completeness sake, can you please include the rest of the class, showing the initialization of SUT?

I believe you may have hit on exactly the problem. SUT is created by Moq.Automocker. It's not a mock itself, but any of its dependencies would be, and maybe that's where things are going wrong. The automocker is going to pick the greediest constructor, so it should have settled on the one that takes options, concurrencyLevel, capacity, and a comparer. Since it will have mocked these all out, we can probably assume that at the very least, the mocked comparer is what's throwing it off. Inlining the creation of the locker and taking the default options makes it behave.
Thanks for pointing me in the right direction.

I have a follow-up question, though. At runtime, the .Net IoC is also going to try to grab the greediest constructor. I haven't looked at the internals of the .Net IoC, but could this cause similar issues if it picked the wrong one?

Wouldn't you usually set that up as a singleton via IoC?


How to display trimmerView in a SmalllView.

I am using this PryntTrimmerView in my project.My project is in Objective-c . i drag and drop the trimmer files in my project. According to the design i have a small view with height of 56 height i already using the AVplayer to play the videos. how to display the trimmerView in the Small View.and add the delegate methods. I tried ... but i am unable to access delegate methods and the properties to change the colour and assign the asset to the trimmerView.I don't understand the sample code. please give suggestions to implement the trimmerView in Objective-c code. or please provide the sample code totally in One ViewController to understand easily.
Thank you

I'm closing this issue as this is a duplicate of your other one #15 which is better documented.


Requires Node.js version 18.20.4

Is there a timeline for remediation of this plugin to work with latest HB node version?

Is there a fix for this?

It's unclear what impact this is having on the overall performance of my install, however I do notice inconsistent updates with my LG Wifi AC in the Home App that can break automation.
LMK what context I can provide to assist in resolving.

[12/5/2024, 7:35:04 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 7:35:05 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 10:34:08 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 10:34:09 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 10:39:39 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 10:39:39 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 11:33:26 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 11:33:27 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 8:17:35 PM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 8:17:35 PM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 8:18:43 PM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/5/2024, 8:18:43 PM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/8/2024, 10:42:17 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/8/2024, 10:42:18 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/9/2024, 11:02:53 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/9/2024, 11:02:54 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 6:51:32 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 6:51:32 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 6:57:57 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 6:57:57 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 7:04:09 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 7:04:09 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 9:01:54 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF
[12/10/2024, 9:01:54 AM] The plugin "homebridge-lg-thinq" requires Node.js version of ^18.20.4 || ^20.15.1 which does not satisfy the current Node.js version of v22.12.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF

I'm currently working on v2.0.0-beta.4 to made it compatible with homebridge v2, node v22 also support on that version too, you can try this

installed, I'll keep an eye out for odd behavior.   Prior to the update Home would fall out of sync multiple times a day, showing the AC on hours after it being off and with no additional interactions from the user to change that status... its like an out dated message in a q got released telling home the AC was on.
It's also important to mention that I have to alter my automation when these behaviors occur, tweaking "reset" automation that tries to re-align the home app with the devices actual current state.  I adjust wait times and sequence to work around the plugins limitations.
So by the time the plug is updated, my environment has changed LOL -  I'll can't role them back.  Complicates my ability to compare apples to apples in this process.


[FEAT]: Added Char Time Series Chart

title: Issue #None | [FEAT]: Added Char Time Series Chart

Discord Username: @dekomori_sanae09
What type of PR is this? (select all that apply)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 🚧 Breaking Change
[ ] 🧑💻 Code Refactor
[ ] 📝 Documentation Update

Description
I have added a chart similar to word toggle history chart ( monkeytype ).
Key Feature:
Uses local storage to send data so the same chart can be used for unauthorized users.

Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings
Video:
https://github.com/webdevcody/code-racer/assets/95468529/efe9102a-59a9-498a-98a6-1a2c1b7a77af

UI accessibility concerns?
The graph is unbearable in smaller screens.

Added/updated tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

oh nyo!


use a simpler implementation for isGitInstalled()

Before we start doing commands with git, we need to check and make sure that git is installed at the git path on the command line. Our current solution is this, but we can use a better implementation.

We can use child_process.execFile, as outlined here.

here's some prototype code:
import { execFile } from "node:child_process";

export default function isGitinstalled(): Promise<boolean> {
  return new Promise((resolve) => {
    execFile("git", ["--version"], (err) => {
      if (err) resolve(false);
      else resolve(true);
    });
  });
}


Terminal Not Opening

Issue Type: Bug
Hi,
I am facing issue with terminal related.
Terminal not open properly when I tried.
Thanks!!
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx   (8 x 1996)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
11.55GB (5.51GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

This looks like an issue with our old terminal backend "winpty", going forward we are focusing our efforts on the new backend "conpty" which is build by the Console team at Microsoft and should fix many issues with the terminal under Windows. You can read more about getting ConPTY here.
/duplicate https://github.com/Microsoft/vscode/issues/45693


Write and BulkWrite metods

Hello @babenkoivan
I look at your library and it's cool!
One thing prevents me to use it - I can't fill the index by using it.
If you could add methods that may fill an index (such as write, bulkWrite, reindex) it would be perfect.
Cheers.

Hey @masterjus, you can create an index by using https://github.com/babenkoivan/elastic-migrations and then import your data with standard Scout functionality https://laravel.com/docs/8.x/scout#batch-import.


Reworked motion blur post-process to include screen based mode.

By default the motion blur post-process is object based. To save performances on large scenes, it can be useful to fallback on screen base mode which doesn't require to compute any velocity texture. In screen based, only depth texture is required.
Also fixed badly decorated members for serialization.
I can see that prepass renderer fallbacks automatically on geometry buffer renderer when failed. Do you think the constructor parameter "forceGeometryBuffer" should not set to "false" by default now? If yes, the same should be done for SSAO2

We are setting forceGeometryBuffer = true for now because of all the problem we face lately. We are going to ship 4.2 in a week:)
we will turn it off by default for 5.0
I will also merge your change after shipping 4.2

cc @CraigFeldspar


Figtext for many GTIs in sci_plots (minor issue)

When the event file has a lot of GTIs, the display command
plt.figtext(str(gtitable['START'][:]))
of the astropy.Table automatically truncates the number of rows in the table, but there are still too many, and the list of GTIs overlaps with the title and goes out of the page.
That's a minor issue, but I can't find a way to truncate the display even more. There doesn't seem to be any way to tell 'print' or 'str()' to shorten the output of the astropy.Table
Any ideas?

Maybe the code could count the number of lines in the str representation and then set the font size accordingly, so that the whole table fits?

I did something like this:

if there are more than 7 GTIs, the table shows only the first and last 3, replacing the middle ones by '...', and in the duration column, it shows the sum of the omitted GTIs.
changed the font to courier to have fixed-width characters.


Network error

Dear Vogelbacher,
I did the download an follow the installation guide from:
https://github.com/vogelbac/LAB-QA2GO
After I Import the LAB-QA2Go tool as a virtual machine, I tried to start the tool and got the Error:
"Could not start the machine LABQA2GO because the following physical network interfaces were not found:
VirtualBox Host-Only Ethernet Adapter (adapter 1)
You can either change the machine's network settings or stop the machine."

"Código de Resultado:
NS_ERROR_FAILURE (0x80004005)

Componente:
ConsoleWrap

Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"

After this, I tried to open the configuration page of the tool and change the network settings and wasn't able to make any changes in the network to solve the problem.
Please if you have any advice to help us solve this error would be such a help for us.
Thank you so much!
Greetings,
Carolina

Hey Carolina,
first of all I am sorry for my late response. Would it be possible to get access to the virtual machine, so that I can have a look?
Best
Christoph


SQL Agent loading indicator doesn't go away when there are no jobs

SQL Operations Studio Version: master

Steps to Reproduce:

Connect to a server with no jobs.  Like an Azure DB instance

Expected: Loading indicator goes away

@abist this is on a server that doesn't supported SQL Agent (like Azure SQL), so there are not any jobs to load.  Does your hypothesis make sense in this context?

@kburtram I'll confirm this and fix if this is an actual issue


Add binary type

Coverage decreased (-1.5%) to 31.296% when pulling 6b67fb4cd0a9371a05fb0d4e3319fcb92d59af9f on fcastilloes:binary-type into bd3d9bc2c18dc16624b5f56bc02cbcd975e31736 on kusanagi:master.


Remove setting CMAKE_OSX_SYSROOT

Change Description

Setting CMAKE_OSX_SYSROOT has shown to cause build failures on fresh macos 10.13 installs
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

https://buildkite.com/EOSIO/eosio-nightly-builds/builds/232

Merging this in; it may cause a resurgence of weird warnings for some users with broken installs (#5418) but that's better than build failures on clean installs.


feat: bump terra core

Description and Motivation

Related Issues

Checklist:

[ ] I have read Migaloo's contribution guidelines.
[ ] My pull request has a sound title and description (not something vague like Update index.md)
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation.
[ ] The code is formatted properly golangci-lint run ./... --fix.

Because we are bumping other module versions, let's take this opportunity to upgrade everything else.

we also need to update go in the ci system

...and in Docker....


Altered quality info so bowties can't map

Hi,
new to this biof stuff. But used sabre a few times on my fastqs and worked great (Thanks a Lot). However, last run....can use bowtie2 to map non demultiplexed fastq fine no errors. Demultiplex with sabre then about half the new fastqs throw errors saying "Error: Read M00733:9:000000000-A5T8E:1:2116:15800:22597 2:N:0:1 has more read characters than quality values.
terminate called after throwing an instance of 'int'
bowtie2-align died with signal 6 (ABRT) (core dumped)"
Got MiSeq to remake fastqs and tried again. Same problem. Deleted the entry for the error throwing line, found a new one. Gave up after deleting four reads worth.
Not sure what to do next!!!
Any help appreciated..

I met similar problem with you too.
Hope someone can help with it .


Rep balance errors

there's an error in rep balances when supporting an outcome:

similar issue happening with disputing an outcome

I have a PR to fix this issue of balances not updating.

Check through and DR and OR appears to be fixed.
Disputing is still having issues with adding pre-filled stake to outcomes. Some markets are working fine but below is an example where the amount is coming out of the users available rep balance and is showing on the market card under pre-filled stake but it's not showing up in the users 'My Total REP Staked'

Ok, could be UI isnt refreshing user data after a dispute or there is some error preventing the updating of user data. I can look.

I'm not seeing this issue. @matt-bullock can you confirm

Checked through all scenarios and rep balances are all being deducted/adding up correctly


2561 handle validation errors on course creation

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

https://trello.com/c/xiQ91ACB/2561-handle-validation-errors-on-course-creation


Time to update I think

Hi,
Terminology 1.11 is came out with new look
It will be a good idea to update your theme
so I can fork it 😁 with different  character and colors
thanks man 😊👍

Hi,
Sorry answering that late. Since I am not using terminology anymore, maintenance from my part will be quite scarce  :/
However, I would be more than happy to accept pull requests, if any ;)