Draw GameBoy CPU Board schematics in KiCad

Redraw https://github.com/gbdev/pandocs/blob/master/src/imgs/Gameboy1-cpuboard.gif using KiCad's "Schematic" so we could export it in SVG and edit/update itthe KiCad source
Part of https://github.com/gbdev/pandocs/issues/361, @https://github.com/aleksandrabanasiak were you already working on this?

IssueHunt Summary

Backers (Total: $15.00)

 avivace ($15.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

About two years go, I spoke to Bit 9 who reverse engineered schematic and board layouts for the DMG mainboard, and he said it would be ok to share his work. This might be a better point to start off than Jeff's outdated schematic. Those files are made in Eagle, though. Maybe it's possible to automatically convert them to KiCAD to reduce the amount of manual work needed. I should maybe double check what kind of license he would prefer if using his files as a basis for further work.
https://gbdev.gg8.se/files/schematics/DMG-bit9/
I'll also point out that gekkio has done some relevant work, on the LCD board and power converter boards.
https://github.com/Gekkio/gb-schematics

About two years go, I spoke to Bit 9 who reverse engineered schematic and board layouts for the DMG mainboard, and he said it would be ok to share his work. This might be a better point to start off than Jeff's outdated schematic. Those files are made in Eagle, though. Maybe it's possible to automatically convert them to KiCAD to reduce the amount of manual work needed. I should maybe double check what kind of license he would prefer if using his files as a basis for further work.
https://gbdev.gg8.se/files/schematics/DMG-bit9/
I'll also point out that gekkio has done some relevant work, on the LCD board and power converter boards.
https://github.com/Gekkio/gb-schematics

Didn't see those.. Looks like he has already the CPU one: https://github.com/Gekkio/gb-schematics/blob/main/MGB-xCPU/schematic/MGB-xCPU.pdf


MSID: 94391 Version: 1 DOI: 10.1101/2<IP_ADDRESS>4368

MSID: 94391
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>4368
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=94391
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>4368

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/94391v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>4368
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/94391/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c6) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c8) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c19) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c26) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c28) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c29) has a publication-type='other'. Is that correct?


Add a test that the compiler submodule is synced to the right commit

This would fail if, for instance, the person doing the release did a
'git pull' instead of 'git checkout v20160713'

Using the variable name mvnVersion doesn't really make sense without my other PR so maybe I should make these into a single PR. Let me know what you think.

I think it's fine separately.


[Bug]: Multiarch sdk container creation time at epoch causing cleaner agressively delete them

What happened?
and causing ongoing postcommits failure every day around 5 PM (PDT).
From the log of https://github.com/apache/beam/actions/runs/6778016000 one can see
Digests:
- us.gcr.io/***/github-actions/beam_go_sdk@sha256:07d1cda15436c9dd4608b0be6ae77e32103b96ca09eedecaed601224e425e50e
  Associated tags:
 - 20231106-160203
Deleted [us.gcr.io/***/github-actions/beam_go_sdk:20231106-160203].
Deleted [us.gcr.io/***/github-actions/beam_go_sdk@sha256:07d1cda15436c9dd4608b0be6ae77e32103b96ca09eedecaed601224e425e50e].
Deleting image. Command: gcloud container images delete us.gcr.io/***/github-

Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Example containers:
Name | Tags | Virtual Size | Created | Uploaded | Vulnerabilities |
-- | -- | -- | -- | -- | -- | --
c864b0e8bc3a |   | 1.2 KB | Dec 31, 1969 | 2 hours ago | Not supported |   |
fa0191e6b4fb |   | 213.6 MB | 2 hours ago | 2 hours ago | 26 |   |
89124f3fe410 |   | 208 MB | 2 hours ago | 2 hours ago | 26 |   |
b1f9dc6e8656 | 20231107-211804995803113 | — | Dec 31, 1969 | 3 hours ago | — |   |
06e7bb78989b |   | 1.2 KB | Dec 31, 1969 | 3 hours ago | Not supported |   |
242e187d1d8c |   | 213.6 MB | 3 hours ago | 3 hours ago | 26 |   |
39320d763be6 |   | 1.2 KB | Dec 31, 1969 | 3 hours ago | Not supported |   |
ebeb66d5cc96 |   | 208.1 MB | 3 hours ago | 3 hours ago | 26 |   |
Name
Tags
Virtual Size
Created
Uploaded
Vulnerabilities
 c864b0e8bc3a
1.2 KB	Dec 31, 1969	2 hours ago	Not supported
 fa0191e6b4fb
213.6 MB	2 hours ago	2 hours ago	 26
 89124f3fe410
208 MB	2 hours ago	2 hours ago	 26
 b1f9dc6e8656
20231107-211804995803113
—	Dec 31, 1969	3 hours ago	—
 06e7bb78989b
1.2 KB	Dec 31, 1969	3 hours ago	Not supported
 242e187d1d8c
213.6 MB	3 hours ago	3 hours ago	 26
 39320d763be6
1.2 KB	Dec 31, 1969	3 hours ago	Not supported
 ebeb66d5cc96
208.1 MB	3 hours ago	3 hours ago	 26

Also, go container is always build in multiarch, which is not necessary. This can cause both non-arm and arm test failing.


Add Presearch support

Usually, I use Presearch (https://presearch.com/) to replace Google.

Will add in next release


Python: Repository splitting

Currently, we placed all the support across languages/frameworks in one repo, is it possible to split by language?
As a dotnet developer, I only care about the dotnet-related changes, and no need to download the python/java implementations, but since it's all in one repo, I had to fetch them all.
Besides, there are more and more connectors, is it possible to split non-core connectors into another repository? So that we could maintain the core framework and functions easily, and extensions in another or extensions in another solution file?
For multiple languages/frameworks support, I like the open-telemetry repository organization, they put up the Specifications in a repo,
and for the language-specific implementation, separate into different repositories, and core implementation for the spec in one repository, some extensions out of spec maintained in another repo.
Thoughts?

@markwallace-microsoft Good opportunity for an ADR on our decisions for keeping all in once.

This ADR goes into the decisions to keep it in one repo right now.

Going to close this issue right now as the ADR I linked to is where we currently stand. Thanks for asking, @WeihanLi.

seeing https://github.com/microsoft/semantic-kernel/pull/6820, maybe worth another decision


AttributeError: 'ChatCompletion' object has no attribute 'cost' for OpenAIWrapper when using AzuerOpenaAI

Reference:

https://github.com/microsoft/autogen/blob/main/notebook/oai_client_cost.ipynb

I am trying to use autogen to get the cost estimate as described in above notebook.
However, I got the error:
AttributeError: 'ChatCompletion' object has no attribute 'cost'

Info

Windows 10 computer, python 3.11
autogen : 0.2.0

MWE
import autogen
import os

config_list = autogen.config_list_from_json(
    env_or_file=os.path.expanduser('~/.config/autogen_config_list.json')
)

from autogen import OpenAIWrapper

client = OpenAIWrapper(config_list=config_list)
messages = [{'role': 'user',
             'content': 'Can you give me 3 useful tips on learning Python? Keep it simple and short.'
            },]
response = client.create(messages=messages, model="gpt-35-turbo", cache_seed=None)
print(response) # this does not give error

This gives error
print(response.cost)

config list
[{'model': 'gpt-35-turbo',
  'api_key': 'xxx',
  'base_url': 'xxx',
  'api_type': 'azure',
  'api_version': '2023-06-01-preview'}]

How to make it work?

@kevin666aa fyi

autogen : 0.2.0 doesn't have this feature yet. Will be in v0.2.1.

@kevin666aa likewise, also on 0.2.1 (and openai 1.2.4)

@kyang8093 @gbertb
from autogen import OpenAIWrapper

client = OpenAIWrapper(config_list=config_list)
messages = [{'role': 'user', 'content': 'Can you give me 3 useful tips on learning Python? Keep it simple and short.'},]
response = client.create(messages=messages, model="gpt-35-turbo-1106", cache_seed=None)
print(response.cost)

Are you running this code from oai_client_cost.ipynb and get an error? If not, can you share your code ?
If you running a code with cache_seed set and using cache, this could cause the issue, because previous cache doesn't have the cost attribute. I am making a PR to address that. Please let me know if this is not the case.

Yes, I was using my own code with cache_seed set. Thanks for making a PR, hope it's addressed soon!


Create CI plan to build and publish artifact

k8s server should probably also be rebuilt on commits to this repo so a new image is built and pushed

closing this in favor of https://github.com/spring-cloud/spring-cloud-scheduler-kubernetes/issues/4


Define default value for field

Sometimes JSON doesn't have an attribute, but in the record definition there are some fields which are needed. It can happen when a record got new fields during application upgrade, but the old values don't contain those fields in the database.
-json(author, {string, "name"}, {"numberOfBooks", 0}).

Let us note that strings, binaries, boolean and numeric fields can have default value. Default value can be anything, a tuple or a record as well.

Not in this form but it is completed (field option list).


BUG: Correct bug in one_to_many decorator

one_to_many decorator doesn't work atm because of wrongly named object results should be named result.

Hi @TomAugspurger, would you mind merging this?

thanks.


Very small collection filesystem

What Im exactly looking for is an in memory database that transparently persists and loads documents as json files on the filesystem.
Im thinking something like a per document / per file (for good reason), though im not sure that ext4 is up to the task (their are other file systems designed for such a thing).
Do you think that Loki would be a good base for this, and that it is possible to create an adaptor that would provide this kind of behaviour.
There is one level of granularity above document that I can use, for between ten and a hundred or so, that might be good, but either way, the question stands.
Thanks :)

@techfort had begun implementing an 'incremental adapter' similar to what you describe...  maybe that can give some ideas.

Also (as i re-read), if your ok with more than one document per file, you can use the LokiPartitioningAdapter, along with default LokiFsAdapter to break into smaller files.  Along with 'paging' and 'pageSize' options it can dump pages of documents of (roughly) the size you set.
Here's a sandbox gist how you might use it.
When you run that and view output, 'value' will be the contents of your files, and the filenames are variations of your original filename with collection/partition and page number file extensions.
The transparently persisting and loading will have to come from merging that example with an autosave example like quickstart2

Thank you very very much for your help. I will study this, and get back to you with what I come up with.
So kind
Chirstopher


Auto-update Javascript paths fails

Issue Type: Bug
Use case:
Given: I want to move a .js file to another folder,
When: I relocate the file, I want VSC to update the import path reference,
Then: the app will compile successfully
Current settings
"javascript.updateImportsOnFileMove.enabled": "prompt"
Example:
Move ./App.js to ./src/App.js
Result:
Expected: VSC prompts me to update, then updates the import path if I select "yes".
Actual: No prompt and no update occur.
Update:
I tried moving the referenced file, App.js, while I had the referencing file, index.js, open. I was prompted to update the path. That is not expected behavior. That would only work if every referencing file were open in the editor when I moved the referenced file.
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:33:47.663Z)
OS version: Darwin x64 19.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_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)
2, 2, 3

Memory (System)
16.00GB (1.69GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (19)

Extension
Author (truncated)
Version

project-manager
ale
11.0.1

vscode-apollo
apo
1.16.0

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.61

vscode-eslint
dba
2.1.5

gitlens
eam
10.2.1

vscode-npm-script
eg2
0.3.12

vsc-material-theme
Equ
32.6.0

vsc-material-theme-icons
equ
1.1.4

prettier-vscode
esb
4.7.0

gitignore
mic
1.0.1

atom-keybindings
ms-
3.0.8

vsliveshare
ms-
1.0.2236

debugger-for-chrome
msj
4.12.8

vscode-react-native
msj
0.16.0

code-settings-sync
Sha
3.4.3

autoimport
ste
1.5.3

alphabetical-sorter
ue
2.0.1

(3 theme extensions excluded)

Please share your project or a small example project that demonstrates the issue

The test project can be found here.
To test:

Open the project in VSC
Check that the setting  Update Imports On File Move: Enabled is set to always
With no files open in the editor, drag App.js to the /src folder.
Open index.js.

Result:
Expected import: import App from './src/App';
Actual import: import App from './App';
If index.js is open in the editor and the file is moved, VSC will update the path. Also, if the import path is incorrect and the file is relocated to its original spot, the import will not update.


What can I do to help get this across the finish line? How close are we?

Join us on Discord and let's discuss -- https://discord.gg/gR4Uye6. Ping me directly when you're there (Nayruden)


[proposal] create titiler namespaces packages

ref: https://github.com/developmentseed/titiler/discussions/278
Why
As mentioned in #278, TiTiler is much more than an application, it's a python module that lets user create custom Tiler.
I believe that splitting core and application could help users to have a better understanding but also help us to move quickly on some features.
How

titiler.core: core functions (e.g tiler factories)

Tiler factories, ressources and models

titiler.application: demo application

basic application (adds Uvicorn, python-dotenv and brotli dependencies)
main changes

split core functionalities and demo application
move custom (colormap, tms) to the demo application
removed unused function titiler.utils.get_hash
switch to pkg_resources to locate templates files

other

use a bash script instead of tox to do PyPI publishing

To Do

talk
update docs
update readmes

Still awaiting for feedback but if we move forward with namespaces here is IMO what we could do:

move mosaic features into titiler.mosaic
add rio-tiler-mvt feature (https://github.com/developmentseed/titiler-mvt) into titiler.raster_to_vector

Maybe

titiler.mvt instead of https://github.com/developmentseed/timvt
titiler.public_datasets instead of https://github.com/developmentseed/titiler-pds
titiler.stac_api (WIP) a mosaic backend based on stac_fastapi

cc @geospatial-jeff @kylebarron

Quick notes from chat

Decide whether to use - or . in PyPI names, i.e. pip install titiler.core or pip install titiler-core. (AWS CDK uses ., Google uses -, I use .)
Should follow up on whether you can use mypy in pre-commit still after moving to namespaces.  If the tool needs to follow imports (mypy, pytest), then it's simplest to run in each module individually.
Ideally put all config in config files, e.g. mypy.ini, setup.cfg, pyproject.toml (my preferred, since it's a PEP standard). Then whether run inside or outside pre-commit should give the same output.


Q: strip hyphens from Key Vault resource name?

I ran into a situation with @pamelafox where the Key vault resource name was created with hyphens but the Azure portal removed the hypens for the endpoint URL. When constructing the URL for the SDK, instead of using the resource name, the hyphens had to be stripped out in order to successfully connect to the key vault.
Is this a known/doc'd issue somewhere? When should customers use hyphens in resource names which will be used with Python SDKs?
Code for reference is copied below:
import logging

from azure.keyvault.secrets import SecretClient

def get_key_vault_secret(azure_credential, key_vault_name, secret_name):

    # TODO: Does this need to have hyphens stripped?
    key_vault_uri = f"https://{key_vault_name}.vault.azure.net"
    logging.info("key_vault_uri=%s", key_vault_uri)

    client = SecretClient(vault_url=key_vault_uri, credential=azure_credential)
    logging.info("created client")

    key_vault_secret_response = client.get_secret(secret_name)
    logging.info("got secret")
    logging.info("secret= %s, value= %s", secret_name, key_vault_secret_response.value)

    return key_vault_secret_response.value

Hi @diberry, thank you for opening an issue! This isn't something I've seen before, and may be a regression. I personally use a Key Vault with a hyphen in its name and haven't had issues with it, but the vault was created a while back. I'll tag someone from the service team who can take a look.
cc @jlichwa

Pinging folks from the service team again who may be able to assist: @nkondamudi, @jackrichins, @jlichwa

@diberry it is likely issue on service side with this particular vault. We have no restrictions on using hyphens with vault name as documented here https://learn.microsoft.com/en-us/azure/key-vault/general/about-keys-secrets-certificates#vault-name-and-object-name.
I recommend to create IcM for assistance.

I was with Dina when we ran into that issue- I'm still not sure why we saw the key vault URI with removed hyphens entirely, since I have successfully deployed key vaults with hyphenated names and hyphenated URIs since then.
However, the documentation does seem to leave out the fact that there can't be consecutive hyphens. I just got this error on a deployment where my auto-generated name had two hyphens:
VaultNameNotValid: The vault name 'simple-flask-api--vault' is invalid. A vault's name must be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. Follow this link for more information: https://go.microsoft.com/fwlink/?linkid=2147742

@pamelafox, thank you for the information. @jlichwa, it does look like the documentation you linked should probably be updated to mention the consecutive hyphen restriction.

We will update the documentation.


Fix bounding box check in collision detection

Description
The bounding box was not correctly built in rc8.
There seems like there still is a problem with the ScreenCollidable though, will continue to investigate that.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
[x] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
[x] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
[x] I read and followed the Flutter Style Guide.
[x] I have added a description of the change under [next] in CHANGELOG.md.
[x] I removed the Draft status, by clicking on the Ready for review button in this PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flame users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
[x] No, this is not a breaking change.

Related Issues
#759

Some tests are failing, will investigate more tomorrow.


copying fix #3961 from 2.4

copying fix #3961 from 2.4

@alalek , could you please review?

:+1:


fix(AgmMap): correct arguments to map click events

map events did not get the correct arguments
fixes: #1845

@SebastianM can you merge and release 3.0.0-beta.1?


Fix IndexPath slicing crash

(Re-open of accidentally closed #3152)
Subscripting of IndexPath using a range currently crashes when removing from the front if the result is a pair or single:
let path = IndexPath(indexes: [ 10, 20, 30, 40 ])
print(path[2...]) // Crash

@swift-ci Please test


Show error immediately

[ ] show error immediately in red (below text) that indicates the account is not a smart contract

error only showed up when submitted

Implemented


The texturepack is not working..

It worked perfectly with 0.12.3 (1.10 block launcher version)
So even without ModPE Javascript, it kept crashing. I cannot even start the block launcher.
(Thank God that u added 'safe mode' :P)

Have you installed an updated version of your texture pack for MCPE 0.13.0? With all the texture additions for the Redstone update, v0.12.x texture packs will not work properly, if at all.


[embedded Rviz]: change background color

Hi,
I am using Rviz embedded (what was formerly used as "librviz") but despite searching in the code, I can't find a way to change the Global Options "Background Color".
Any suggestion?

To clarify, do you want to change the color via the library API? There's a background property that we can call setColor on, however it is a protected member:
https://github.com/ros2/rviz/blob/7b4ba855b5803ef8b77b7732889c8b1b6e43532b/rviz_common/include/rviz_common/visualization_manager.hpp#L376
How was this done in ROS 1? The code looks similar:
https://github.com/ros-visualization/rviz/blob/1dc4953639dd69b4a52db746d7101638fa13e6c9/src/rviz/visualization_manager.h#L433

yes, I would like to do it from the API. Not being public, I don't know how to access it.

@facontidavide is it possible to change the color in ROS 1? I'm trying to understand if this is something that's missing when transition to ROS 2 or if it's strictly a new feature request.
Either way, I think we could add a public method for setting the color to VisualizationManager; which just updates background_color_property_. If you think this accomplishes what you want, I'm happy to review a pull request :)

Probably not possible in ROS1 either.

@facontidavide Would you like to propose a pull request?


Examples for image embeddings and clip

Image embeddings and CLIP have been added to fastembed, but there are no examples or documentation yet

#258


CLOUDP-176134: atlas operator deletion protection

Proposed changes
Added deletion protection flags for the atlas kubernetes operator install command

Jira ticket: CLOUDP-176134

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

It would be good to increment the test and verify the happy path validating the envs were correctly added
https://github.com/mongodb/mongodb-atlas-cli/blob/master/test/e2e/atlas/kubernetes_operator_install_test.go#L300

It would be good to increment the test and verify the happy path validating the envs were correctly added https://github.com/mongodb/mongodb-atlas-cli/blob/master/test/e2e/atlas/kubernetes_operator_install_test.go#L300

Good catch! I added a missing test

Hi @gssbzn please take a look when you have time. Thanks!

@mongodb/mongocli can you please take a look?

@mongodb/docs-cloud-team please take a look as well


Add new option :consume_jobs

The :only_latest and :only_new options are being used to determine which splunk jobs the producer should process.
Instead of having theses as two different options, they should be merged to a single enum called :consume_jobs or similar. The :consume_jobs enum must accept:

latest
new
all

Add new option and put deprecation warnings on the old options. They should still work until next major version.

Fixed


ValueError: need more than 2 values to unpack

use 60*180size to train ,num_classes = 12 then i got it
loading train data, please wait---------------------
('get image: ', 15000)
loading validation data, please wait---------------------
('get image: ', 4999)
2017-11-06 13:16:08.547013: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2017-11-06 13:16:08.641450: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:892] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2017-11-06 13:16:08.641675: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1031] Found device 0 with properties:
name: GeForce GTX 1080 major: 6 minor: 1 memoryClockRate(GHz): 1.86
pciBusID: 0000:01:00.0
totalMemory: 7.92GiB freeMemory: 7.29GiB
2017-11-06 13:16:08.641691: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 1080, pci bus id: 0000:01:00.0, compute capability: 6.1)
=============================begin training=============================
No handlers could be found for logger "Traing for OCR using CNN+LSTM+CTC"
('batch', 99, ': time', 0.1522228717803955)
('batch', 199, ': time', 0.1701350212097168)
('batch', 299, ': time', 0.14639997482299805)
('batch', 99, ': time', 0.1512739658355713)
Traceback (most recent call last):
File "main.py", line 215, in
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "main.py", line 207, in main
File "main.py", line 111, in train
ValueError: need more than 2 values to unpack

                            dense_decoded,lastbatch_err , lr = \
                                sess.run([model.dense_decoded, model.lrn_rate],
                                         val_feed)

sees.run() only return two values,you just need to remove "lastbatch_err ",good luck

@QiangXie @980044579 thanks，I have solve it by your solutions.


Distributed searchlight

Please provide more comments to describe at least the public methods. I found it a bit confused when reading the code now. For example, I am lost when trying to understand how the ownership is distributed.


Trying to fix cmdlet's rendering

Closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/6889

Docs Build status updates of commit c57f851:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoMoveCrossCompatibilityStatus.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit 08e6cf7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoMoveCrossCompatibilityStatus.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Moab doesn't build on kickit because LAPACK is missing.

I was running build_visit on kickit and it failed building moab because LAPACK was missing.
Here is the error message:
checking for ATL_xerbla in -latlas... no
checking for sgemm_ in -lblas... no
checking for sgemm_ in -framework vecLib... no
checking for sgemm_ in -lcxml... no
checking for sgemm_ in -ldxml... no
checking for sgemm_ in -lscs... no
checking for sgemm_ in -lcomplib.sgimath... no
checking for sgemm_ in -lblas... (cached) no
checking for sgemm_ in -lblas... (cached) no
configure: error: LAPACK library not found
+ set +x
make: *** No targets specified and no makefile found.  Stop.

@iulian787 any ideas here. I can't recall, is there a new MOAB config switch we should be setting to control this?

@brugger1 @markcmiller86 For the MOAB plugin, you can use --disable-fortran and either --download-eigen3 or --with-eigen3=$EIGEN_INCLUDE_DIR to use Eigen3 as a dependency instead of BLAS/LAPACK. Please let me know if that resolves the issue. Please feel free to tag me as well in the future.

We expect to have ability to build MOAB without blas, lapack or eigen3 in the near future. When available, that is how we will build on Windows.

Discussion:
MOAB on develop - we feel with a newer version we will be able to disable LAPACK or Eigen -- VisIt doesn't need to leverage the features related to those.
Unsure if we can do this on the RC, however the most important platform for MOAB is Ubuntu.
We don't need MOAB support on Kickit.

@cyrush I have a PR (https://bitbucket.org/fathomteam/moab/pull-requests/700) to disable both LAPACK and Eigen3. So LAPACK is no longer a required dependency. We will get this merged in this week and it will be part of the upcoming MOAB 5.6 release.

Thank you for this info!


Add: Minion xp

This is necessary for SkyHanni PR #639

I know it's a ton of effort, but could you maybe change the format from
item id -> type + value
to
type -> item id = value

from
   "ABSOLUTE_ENDER_PEARL": {
            "type": "Combat",
            "value": 7680.0
        },
        "BLAZE_ROD": {
            "type": "Combat",
            "value": 0.3
        },
        "BLOCK_OF_REDSTONE": {
            "type": "Mining",
            "value": 1.8
        },

to
"Combat": {
"ABSOLUTE_ENDER_PEARL": 7680.0,
"BLAZE_ROD": 0.3
},
"Mining": {
"BLOCK_OF_REDSTONE": 1.8,
....

This is definitely a better way. 😅
I will do it tomorrow. 😑


JSON-RPC spec: fixed the data type of event.sequence_number

The sequence_number property of the transaction event object was erroneously defined as string. Changed to unsigned int64, as it currently appears in the Libra Blockchain.

/land


Make PR checks workflow runnable for external contributors

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
There are parts of our PR workflow that depend on secrets (e.g. E2E tests, integration tests, codecov reports, etc.). We'd like to make sure that in case an external contributor creates a PR, it'll be possible to run all the required checks against it.
Proposed Solution
Implement the workflow described by Michael Heap in his blogpost.
Acceptance Criteria

[ ] When an external contributor creates a PR, it's possible to run all required checks by triggering the workflow by a maintainer

@mheap's PoC to make tests requiring secrets runnable from forks: https://gist.github.com/mheap/2c66574509e90747b9fd885e2376935c

@mheap 's suggestion is to detect whether or not a user has write access or equivalent.
So if I understand correctly the check would fail at first and a maintainer will need to do an action for it to pass (for example pull_request_comment).
Does that sound right?

Does that sound right? Any preference?

Sounds right. Label sounds good to me (just as proposed by @mheap).

The label approach works, but you do lose some metadata as it's technically a different event triggering the job.
If you're comfortable with the "maintainer re-runs the job" it's the exact same job that runs


The schedule endpoints have been setup

The schedule part of the course has been completed along with its schema, dto and its endpoints (namely Post, update by Id and delete by Id)
The course get by id method has been populated accordingly

[x] My code follows the code style of this project.
[x] All new and existing tests passed.
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

Tests:-
1). npm run start:dev
2). nest start
3). npm run lint
4). npm run test
5). Postamn responses

@Abhishek-kumar09  changes have been made


Make note linking case-insensitive

Is your feature request related to a problem? Please describe.
Imported notes that need linking all begin with capital letters.
Describe the solution you'd like
Plugin should link to notes without being case sensitive
Describe alternatives you've considered
Could rename all notes to be the required case but that would be an unimaginable amount of work.

yes please

+1 for this feature
I believe this should be very simple.
Maybe as simple as setting the regex to case insensitive. Probably somewhere here:
https://github.com/AlexW00/obsidian-note-linker/tree/master/src/rs/matching


Clicking Home

It seems that when I click home I get logged out. I have to click login again after clicking home. Also, I saved a study but I have no idea how to find it now. - posted by<EMAIL_ADDRESS>

Closing as a result of no activity


Add Ruby version

i dont know why someone wants multiple versions of a program that'll probably be dead by tomorrow but here you go

Instructions should be added to the README as well!


pageserver_remote_physical_size metric lags behind

While implementing https://github.com/neondatabase/neon/pull/3729 I noticed that the pageserver_remote_physical_size lags behind.
So, I commented out that part of the test.
But we need to get to the bottom of this.

Will be interesting to see if these tests become flaky, since layermap is more consistent than the relaxed counters/gauges which could have whatever value even on amd64.


Step 4: Error Submitting Proof / Failed to Get Merkle Proof

Similar to #253, I just ran into this so its still an outstanding issue.

Definitely real. Right now I believe a refresh fixes it 🙃


Relationship properties

Relationships are an important part of an API or a data model: People have Friends, People have Hobbies, which are shared by other People, ...
OData represents relationships as a special kind of property, a so-called navigation property which allows retrieving related entities, and also retrieving an entity together with related entities:

a single person:
http://services.odata.org/V4/(S(n4bk11pfsypujadnvn5jtwic))/TripPinServiceRW/People('russellwhyte')
the friends of this person:
http://services.odata.org/V4/(S(n4bk11pfsypujadnvn5jtwic))/TripPinServiceRW/People('russellwhyte')/Friends
the person and its friends:
http://services.odata.org/V4/(S(n4bk11pfsypujadnvn5jtwic))/TripPinServiceRW/People('russellwhyte')?$expand=Friends

As the last example shows it makes sense to model navigation properties just as "data" properties in the /definitions section as they may be part of the response if requested with $expand. It is also necessary to tag them as special properties, and include additional metadata about the relationship:
            "Products": {
                "type": "array",
                "items": {
                    "$ref": "#/definitions/ODataDemo.Product"
                },
                "x-relationship": {
                    "partner": "Category",
                    "onDelete": {
                        "action": "Cascade"
                    }                    }
            }
        }
    },

Partner is the navigation property in the target type that leads back to the current type, onDelete describes potential side-effects of deleting an entity of the current type, and referentialConstraints describe value dependencies to the related entity.
Anyone else having similar concepts/constructs in their APIs that would make it worth making this a first-class concept in OpenAPI?

@handrews @sensibleish - Looking for a way to spec relational data in OpenAPI I found this thread. GraphQl 's SDL (Scheme Definition Language) does scaffold relational data types.
Here a User has one blog. It is a 1 to 1 relation. A blog has many Comments. It is a 1 to Many relation. Each blog and each comment has one author. They are a 1 to 1 relation.
type User {
  id: ID! @unique
  comments: [Comment!]! @relation(name: "CommentAuthor", onDelete: CASCADE)
  blog: Blog @relation(name: "BlogOwner", onDelete: CASCADE)
}

type Blog {
  id: ID! @unique
  comments: [Comment!]! @relation(name: "Comments", onDelete: CASCADE)
  owner: User! @relation(name: "BlogOwner", onDelete: SET_NULL)
}

type Comment {
  id: ID! @unique
  blog: Blog! @relation(name: "Comments", onDelete: SET_NULL)
  author: User @relation(name: "CommentAuthor", onDelete: SET_NULL)
}

It also performs cascade deletes. Isn't there a tool that does introspection for OpenAPI that map foreign keys into an OpenAPI spec or do those relations not exists? Kinda of new to OpenAPI, but it does seem a $ref would be an interchangeable solution for type and similarly defined decorators could perform the same database operations.

See https://github.com/OAI/moonwalk/discussions/58


new toBase64 function

added a new overload "toBase64" function for converting an html into a base64 string.
usage example: sending an email that received only base 64 ( send grid sdk )

I'd use
pdf.create(html).toBuffer(function (err, buffer) {
  if (err) throw err
  const base64 = buffer.toString('base64')
  ...
})


Azure private image provisioning support

This PR is for Azure private imagine provisioning support.
It does not include support for security groups, floating IPs and key/value pairs because the Azure EMS Refresh does not support these pieces yet. However, support for security groups is in progress.

@gmcculloug, @blomquisg  - this is ready for review
@bdunne  - for ease of review I think a separate commit for the cloud init piece is best

@bronaghs I'm not exactly sure what I need to do for the cloud-init piece.  Openstack and EC2 get the userdata from here: https://github.com/ManageIQ/manageiq/blob/master/app/models/manageiq/providers/cloud_manager/provision/cloning.rb#L22-L23
The same two lines can be reused in your prepare_for_clone_task method.  Then, I believe, the provider gem just needs to send that to the right place on the provisioning call.

@gmcculloug - ready for review
@dclarizio  - I made some UI changes (!!) Can you have someone on your team review please?
cc @blomquisg

@miq-bot remove_label wip

@gmcculloug - any idea what is causing these travis failures? One is in automate.

@h-kataria can you take a look at the UI provisioning changes please?  Thx, Dan

@dclarizio @bronaghs UI changes looks good, tested them in UI.

@gmcculloug any questions / comments on provisioning logic?

@gmcculloug -
I pushed a commit that addresses your feedback. Back over to you.

@bronaghs Two small suggestions but overall looks good.  You should also cleanup the rubocop warnings around  Style/IndentHash and the space issues ("Extra empty line" and " Surrounding space missing").


Breakable constraint

I want to make a constraint that breaks if the force/torque exceeds a threshold. Is there a way to get the force being applied to a constraint so that I could then delete the constraint?

What I'd suggest here is instead to try to roughly estimate stress / strain on the constraint, by comparing its current length to its rest length and average that over a few frames, if it crosses a threshold for a long enough time then consider it broken.


Reusing TestChannel and TestChannelFactory in RetryableConnectionFactoryTest

NetflixOSS » eureka » eureka-pull-requests #70 SUCCESS
This pull request looks good


Vape not compatible with trapify

Installing trapify and then vape gets you this error:
pkg_resources.DistributionNotFound: The 'xerox==0.3.1' distribution was not found and is required by emo

There exist conflicting version requirements in the requirements.txt.

It appears the changes have been made and merged on emo/#4, but have not been updated on pip. (fresh install)

Amazing find.

Emo version updated. Thanks for the report!

Using >= will probably reduce incompatibilities with other versions.


refactor(GUI): get rid of the concept of recommended size

This feature makes no sense after
https://github.com/resin-io/etcher/pull/1055. We will consider
cherry picking functionality from this commit back into the code once we
implement the logic to fetch metadata from a central repository.
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

See https://github.com/resin-io/etcher/pull/1055


Facebook and Instagram

https://www.facebook.com/BlueHenTreats/
https://www.instagram.com/bluehentreats/

Also, e-mail is<EMAIL_ADDRESS>


Error refactoring and thiserror 2.0

Use thiserror 2.0 and refactor errors to be mostly in line with how our other errors are structured, e.g. see https://github.com/0xPolygonMiden/miden-base/issues/972.
So this changes errors to use lowercase messages without trailing punctuation and prefer source style over wrapping source errors.
Other notable changes include:

SourceManagerError::Custom variant which, I think, makes sense to include as SourceManager is a trait implementable by other crates which cannot add variants to SourceManagerError. Let me know if this is not what we want.
Similarly, EventError(String) was changed to EventError(Box<dyn Error>).
Not using #[source] for errors that turn into Report, because Report does not implement core::error::Error and so source errors would be effectively swallowed that way.

There is a problem with building the assembly crate for wasm/no-std with this change. If I understand everything correctly, then this is because of the following. miden_miette uses miden_thiserror which exposes StdError. If we use neither a nightly compiler nor the std flag then StdError is not a reexport of the core::error::Error type but rather a copy of the Error trait, which means it is a separate type. miden_miette however with its Diagnostic trait expects StdError and that trait is no longer implemented by some errors, like SyntaxError. This previously worked because we used miden_thiserror to derive errors and so in that configuration, the derived error was StdError and that always matched what miden_miette was expecting.
It seems to me the proper fix would be to modify miden_miette to use thiserror 2.0. I've tested this change locally and both std and no-std works. This would make miden_thiserror obsolete, and we could consider yanking that crate.
My question is whether we want to go ahead with this change in miden_miette or not. Pinging @bitwalker, as I think you've made the no-std changes to miden-thiserror and miden-miette.
Or should we go one step further and ask if the miette author would be open to have the no_std changes upstreamed?
closes #1261

It seems to me the proper fix would be to modify miden_miette to use thiserror 2.0. I've tested this change locally and both std and no-std works. This would make miden_thiserror obsolete, and we could consider yanking that crate.
My question is whether we want to go ahead with this change in miden_miette or not. Pinging @bitwalker, as I think you've made the no-std changes to miden-thiserror and miden-miette.

I would modify miden_miette for now and then get rid of miden-thiserror. In parallel, we can also see if miette could switch to the latest thiserror - but I think that would be a separate task.

I would modify miden_miette for now and then get rid of miden-thiserror. In parallel, we can also see if miette could switch to the latest thiserror - but I think that would be a separate task.

Sounds good.
I tried to git push a branch to our miette fork but got this, maybe you can add me as a collaborator?
ERROR: Permission to 0xPolygonMiden/miette.git denied to PhilippGackstatter.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I would do only the minimal necessary changes for now, because updating our miette fork from 7.1.0 to the latest miette at 7.4.0 comes with a bunch of conflicts. And if we can get miette to support no_std and use thiserror 2.0 then that will be obsolete.

I tried to git push a branch to our miette fork but got this, maybe you can add me as a collaborator?

You should be able to write to it now.

I would do only the minimal necessary changes for now, because updating our miette fork from 7.1.0 to the latest miette at 7.4.0 comes with a bunch of conflicts. And if we can get miette to support no_std and use thiserror 2.0 then that will be obsolete.

Yes, let's do the minimal changes for now.


Reduce the project Size.

Currenty due to all that demo media the size of the project is around 70 mb we need to get in down.

The GitHub repository's "open_file.gif" and "type_code.gif" graphics contain an issue. These  consume nearly 61MB of storage
I've got a plan. Instead of inserting them into the repository, we can keep these images via an image hosting site like Imgur. In this way, the load on the repository will be minimised because we only need to add the picture links.
I would be very glad to carry out this duty if you are okay with it. I'll compress those pictures and upload them to Imgur. I'll update the picture links in the required files once it is finished.

@Mr-Sunglasses I have finished
Please take a look at the pull request and review the changes and provide feedback.Let me know if any further adjustments or improvements are required.

@Mr-Sunglasses you can close this issue


Add dropdown for previous logs

Signed-off-by: Zack Layne<EMAIL_ADDRESS>Related issue: https://issues.redhat.com/browse/ACM-1967

/lgtm


Gibbed not supporting equipment from Lilith DLC

I played through the Commander Lilith DLC, and found a number of new equips, and I placed them into the bank for later. After updating Gibbed to 1.0.16, I tried to load that character in Gibbed, and was given an error.
"There were weapons or items in the bank that failed to load. Do you want to remove them? If you choose not to remove them, they will remain in your save but will not be editable."
oops.txt
That is the error info that Gibbed copies to clipboard if I select to Cancel.
I specifically selected "bl2_saveedit_1.0.16.zip" to download for updating, in case this could affect it.

Could you attach the save file?

Save0004.zip
This should be the correct save, should be a Lv63 Maya.

This save loads just fine. Please make sure you're actually running the new version of the save editor.


Fails to generate repo with Node 16

Describe the bug
When trying to generate a new repo when using Node 16, the generator will fail during thenpm install step.
To Reproduce
Steps to reproduce the behavior:

Have dev setup with node 16
Run generator as your normally would
Wait for npm i step
See error

Expected behavior
Packages install as expected
Additional context
It appears that this issue is starts when installing the current version of WebCoreStyleSheets that still has a dependency on node-sass.
It has already been reported that WCSS will not install on a Node 16 setup due to this issue and there is a PR to update WCSS to use Dart Sass over Node Sass. It is assumed that once this PR is released, this will resolve this issue.

https://github.com/AlaskaAirlines/WebCoreStyleSheets/pull/103

WCSS was updated to use Dart Sass, but we still have a dependency on wc-sass-render which has a dependency on node-sass.
In order to fully support Node 16, we need to have an update to wc-sass-render. Options are:

submit a PR to the repo in hopes that it will get picked up
If that fails, we can clone the repo and re-publish ourselves
Come up with a plan to get off of this tool

I am obliged to clone the repo and make modifications that make this tool more suited to our needs until we can remove the dependency altogether.


MONDO:0012360 and MONDO:0013757 labels equal to related synonym.

Related to #7685
Two classes have related definitions equal to the label.
Probable fix: change synonym scope to exact.
[Term]
id: MONDO:0012360
name: congenital nongoitrous hypothyroidism 3
def: "A congenital hypothyroidism characterized by autosomal dominant inheritance of resistance to thyrotropin that has material basis in variation in the chromosome region 15q25.3-q26.1." [DOID:0070127]
synonym: "congenital nongoitrous hypothyroidism 3" RELATED [DOID:0070127]

and
[Term]
id: MONDO:0013757
name: congenital nongoitrous hypothyroidism 6
def: "Any hypothyroidism, congenital, nongoitrous in which the cause of the disease is a mutation in the THRA gene." [MONDO:patterns/disease_series_by_gene]
synonym: "congenital nongoitrous hypothyroidism 6" RELATED [DOID:0070128]

This issue blocks this PR


Revert "add new resource"

Reverts Rhymen/go-whatsapp#518

What's the problem with the pl? Why you want to revert it? @fernandadepaula

Duplicate of #

What do you mean @fernandadepaula I don't understand you, is there a problem with the PL?


Foreign Key Constraint fails from unit tests

I have some unit tests that create and modify models in the test database, and I get FK constraint failures when the test saves a new model instance:
IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (`test_apptest`.`apptest_historicalprofile`, CONSTRAINT `apptest_history_user_id_34e23bc9_fk_auth_user_id` FOREIGN KEY (`history_user_id`) REFERENCES `auth_use)')

I'm using the middleware-based solution to collect the current user, which I guess is part of the reason for this issue (no request is made in the test, so no user to capture), but it looks like the historical* object allows a Null for the user_id, so what is happening here? And what is the workaround?
(Django 1.9.5, django-simple-history 1.8.0)

Hello! This should be fixed in the latest release. Which version of Django
simple history are you using?
On Apr 18, 2016 1:08 PM, "Howard Jones"<EMAIL_ADDRESS>wrote:

I have some unit tests that create and modify models in the test database,
and I get FK constraint failures when the test saves a new model instance:
IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (test_apptest.apptest_historicalprofile, CONSTRAINT apptest_history_user_id_34e23bc9_fk_auth_user_id FOREIGN KEY (history_user_id) REFERENCES `auth_use)')
I'm using the middleware-based solution to collect the current user, which
I guess is part of the reason for this issue (no request is made in the
test, so no user to capture), but it looks like the historical* object
allows a Null for the user_id, so what is happening here? And what is the
workaround?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/treyhunner/django-simple-history/issues/216

I missed the version on my phone. Try upgrading to 1.8.1, it should be resolved.

I have confirmed that updating to version 1.8.2 resolved this issue for me.

Please close the issue 👍

I am getting this issue in my tests now with version 1.9.0:
django.db.utils.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (test_kid_hr.users_historicaluser, CONSTRAINT users_historicaluser_history_user_id_7f91d047_fk_users_user_id FOREIGN KEY (history_user_id) REFERENCES users_user (id))')
What is the fix?

@surfer190 what version of Django are you running? Are you still seeing this issue?

Getting same error when running my tests.
Version 2.0.4
django.db.utils.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (test_weme.roles_faces, CONSTRAINT roles_faces_role_id_a5ddc8a0_fk_roles_role_id FOREIGN KEY (role_id) REFERENCES roles_role (id))')

Getting same error when running my tests.
Version 2.0.4
django.db.utils.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (test_weme.roles_faces, CONSTRAINT roles_faces_role_id_a5ddc8a0_fk_roles_role_id FOREIGN KEY (role_id) REFERENCES roles_role (id))')

Getting the same error
Version: 2.0.4
django.db.utils.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (test_weme.roles_faces, CONSTRAINT roles_faces_role_id_a5ddc8a0_fk_roles_role_id FOREIGN KEY (role_id) REFERENCES roles_role (id))')

@kingkoma, my guess is that you're using django-webtest. Look here: https://django-simple-history.readthedocs.io/en/latest/reference.html#using-django-webtest-with-middleware

Thanks @rossmechanic.


Static CSS files are not found.

This is my own fault for changing the name of the plugin/repository right before releasing it. Fix incoming.

Fixed by f6e6381fec8463195b863d66170225383c8fc1b2


Reintroduce convenience where appropriate

First of all I want to point out I'm very happy that with 8.13 and that it finally feels like we're moving towards the point where we can actually depreciate the nest client in our solution rather than using two clients at once.
When migrating however, I noticed that most of the changes that broke our code required rewrites that do the same thing, just in more code, most of which feels unnecessary. Maybe I've overlooked some obvious solutions though, so I'd be happy for suggestions.
Otherwise I want to at least point them out here, even though I fully understand these probably have not been at the top of the priorities when writing 8.13, so here are some examples.
First and foremost obviously the aggregation change, that requires an additional add, straight from the release notes:
var aggExampleResponse = await client.SearchAsync<StockData>(s => s
    .Aggregations(aggs => aggs
        .DateHistogram("by-month", dh => dh
            .CalendarInterval(CalendarInterval.Month)
            .Field(fld => fld.Date)
            .Aggregations(subaggs => subaggs
                .Sum("trade-volumes", sum => sum.Field(fld => fld.Volume))
            )
        )
    )
);

to:
var aggExampleResponse = await client.SearchAsync<StockData>(s => s
    .Aggregations(aggs => aggs
        .Add("by-month", agg => agg
            .DateHistogram(dh => dh
                .CalendarInterval(CalendarInterval.Month)
                .Field(fld => fld.Date)
            )
            .Aggregations(subaggs => subaggs
                .Add("trade-volumes", agg => agg
                    .Sum(sum => sum.Field(fld => fld.Volume))
                )
            )
        )
    )
);

In addition, I find subbaggregations alot clearer in the original example.
MatchAll now needs a parameter:
q => q.MatchAll()

to:
q => q.MatchAll(m => m.QueryName("all"))

Indexing:
await this.Client.IndexAsync(elasticCustomer, indexName, token);

to:
await this.Client.IndexAsync(elasticCustomer, i => i.Index(indexName), token);

Highlighting (simplified):
private HighlightField HighlightField => new() { PreTags = new List<string> { "" }, PostTags = new List<string> { "" } };

.Highlight(h => h.Fields(fs => fs.Add(new Field("field"), this.HighlightField)))

to:
private HighlightField HighlightField => new() { PreTags = new List<string> { "" }, PostTags = new List<string> { "" } };

.Highlight(h => h.Fields(fs => fs.Add(new Field("field"), hf => hf.PreTags(this.HighlightField.PreTags).PostTags(this.HighlightField.PostTags))))

Again I'm grateful for the effort I can live with all these, but I figured I'd at least point them out in case some of these are just oversights (e.g. MatchAll).

Hi @stefanobranco,

The aggregation change requires a little bit of additional code, but on the same time this new structure maps closely to the corresponding JSON request. This is a good thing as it's consistent now with the REST documentation and as well allowed me to remove a lot of internal hacks that were previously required to support the old strucutre in the .NET client (these hacks caused several issues in the past).
I will bring back the parameterless MatchAll(). This one somehow got lost in the refactoring process 🙂
The HighlightField case I have to check in detail, but it seems like you are mixing up descriptors and class initializer style here. A solution would be to initialize a HighlightFieldDescriptor with your default values instead of HighlightField:

private HighlightFieldDescriptor HighlightField = new().PreTags(...).PostTags(...);

.Highlight(h => h.Fields(fs => fs.Add(new Field("field"), HighlightField)))

Hi @flobernd!
Thanks for the quick response.

The aggregation change requires a little bit of additional code, but on the same time this new structure maps closely to the corresponding JSON request. This is a good thing as it's consistent now with the REST documentation and as well allowed me to remove a lot of

I figured it was something like that. I guess I find the 'Add' a bit 'unattractive', but that's probably a personal thing and it's completely reasonable as it is. I did notice one more small thing, as I'm trying to now completely move away from our nest client. When ordering aggregations:
Before (Nest):
.Order(o => o.CountDescending())

Now (unless I missed something):
.Order(new List<KeyValuePair<Field, SortOrder>>(new []{new KeyValuePair<Field, SortOrder>(Field.CountField, SortOrder.Desc)})))

I will bring back the parameterless MatchAll(). This one somehow got lost in the refactoring process 🙂

Perfect, I figured this was just an oversight

The HighlightField case I have to check in detail, but it seems like you are mixing up descriptors and class initializer style here. A solution would be to initialize a HighlightFieldDescriptor with your default values instead of HighlightField:

You're right. I'm pretty sure the previous variant did work that way but either way your solution works just as well and is more consistent, so there's probably no need to spend more time on this.

.Order(new List<KeyValuePair<Field, SortOrder>>(new []{new KeyValuePair<Field, SortOrder>(Field.CountField, SortOrder.Desc)})))

You don't need the List, and depending on the C# version you can write it like this:
// C# 9
.Order(new KeyValuePair<Field, SortOrder>[] { new(Field.CountField, SortOrder.Desc) })

// C# 12
.Order([new(Field.CountField, SortOrder.Desc)])

.Order(new List<KeyValuePair<Field, SortOrder>>(new []{new KeyValuePair<Field, SortOrder>(Field.CountField, SortOrder.Desc)})))

You don't need the List, and depending on the C# version you can write it like this:
// C# 9
.Order(new KeyValuePair<Field, SortOrder>[] { new(Field.CountField, SortOrder.Desc) })

// C# 12
.Order([new(Field.CountField, SortOrder.Desc)])

Hahaha you're right of course, the list is beyond silly here. I guess the C# 12 version is reasonable enough.


HIP58 distance problem invalid beacons/witness

Hello i would like to make proposal for adjustment of hip58.
I am getting too many invalids witnesses on mine beacon and i am getting invalid witnesses from others due limit 100km which is totaly fine by me.
But im failing to earn anything because of that.
I have plenty hs under 100km who can witness mine beacon and yet im getting invalid 7/14 very often due witness is too far which greatly impact mine reward.
Mine proposal is when hs send beacon dont let other hotspots who are above 100km to participate in lottery for witness. Like if limit is alredy here which is ok by me why at first place those hs above 100km even participate in poc since they are invalid by system. Its damaging valid beaconers and witnesses under 100km

Folks have lobbied this concern already, but it's been determined there's no useful sensor application capable of communication over 100km, let alone any that require it. HIP58 is designed to both prevent spoofing and encourage unique hotspot placement. the witnesses over 100km will need to be invalid for this fix to work, despite the fact spoofers will simply reassert their location to be within these limitations. I've been slowly aiming my mountain off-grid's directional antenna more and more downward every time I make a trip up there and am still witnessing and beaconing over 130km. There can be too good of a deployment now, but the network was designed to provide coverage to sensors incapable of communicating those distances so there's no benefit to the network to reward hotspots for providing unusable coverage. Focus your energy on maximizing the coverage you're providing to hotspots nearby, even if that means relocating to be closer to a town, or lower on the mast/mountain. My off-grids experience about a 25% invalid rate because of too great a distance, so my solution will simply be to reduce my range, and reducing elevation is the easiest way to do so.

Its not about limit. Its about to remove all hotspots from getting witness if they are 100km plus away. There is too many invalid witnesses in beacon

I asked this on Discord just the other day, if - for example 20 miners witness your beacon the 100km+ responders should be removed from the running before the max of 14 are selected as witnesses

i hear what you both are suggesting but that would negate the result of HIP58. Unfortunately solutions that are rewards-centric around proof-of-coverage will not impact the course of anti-gaming legislation on a network designed to transfer data.

It would not negate. Limit would stay as it is 100km. I just want beacons to go on hotspots under 100km. On that way rewards would go to valid witnesses only...

i suppose how i meant to phrase it is that the fact you and other hotspot owners wish you were getting more rewards for meaningless/useless/impossible coverage will not impact anti gaming policies created to prevent hotspots from being rewarded for providing meaningless/useless/impossible coverage. lower your antenna or aim it downward.
there’s no benefit to the network hotspots proving coverage over 100km because there’s no proof sensors can communicate any more than 50km. there is already a large leniency built into HIP58, it will not stop gamers. literally nothing ever will. we can only continue to make things harder and less rewarding for them. the impact on the earnings of honest well placed hotspots will be a negligible.
All of this has been iterated by core developers from Helium in previous iterations of these grievances, there will be no extension to 100km limit and no removal of >100km witnesses in the foreseeable future. off gridders and long distance crushers need now only adapt.

Pls go read what i writed.

I do not want rewards from those 100km plus hotspots. I just want them to be removed from reward pool for beacons which will make invalids.

Likewise. So, for example if 20 respond to a beacon and 2 are over 100km then they get automatically stripped away and it's from the remaining 18 that the 14 witnesses get chosen.
I also am absolutely fine not getting rewarded for witnesses over 100km.

Idk i got feeling that they writed hip58 too fast to just patch it. By mine opinion it is not done propertly. Those from 100km should not be able to get in those 14 witneses.
I know thats why i edited msg. Gor pissed because ppl dont understand rly what is issue...  If i downgrade antenna or move it lower i wont have trouble with 100km plus hotspots but i will loose those under 100km because im surrounded by 2 sides with high mountians.

Thanks for your submission, but this repository is for Helium Improvement Proposals (HIPs) and is not a support or discussion forum.
If you'd like to write and submit proposal, you should follow the format and process prescribed in HIP7, Process for managing Helium Improvement Proposals
I've also written a rough guide to doing this using the github.com web interface: https://jamiedubs.com/blog/how-to-submit-helium-manufacturer-application/
I am closing this as invalid but feel free to ask further questions here or in Discord


Added additional gun types and stat fields.

Hi, thanks for putting this repository together. I was toying around with building my own replay parser in Clojure and parts of your library were helpful to have as a reference. I found a few more gun type values and post-game stat values in the replay file and decided to contribute those back to your project. I don't have C# installed, so I haven't compiled and tested this exact implementation, but it should give you a good starting point if you pick this project up again. I'd love to see what you come up with for doing parsing of the checkpoint and replay-data chunk types.

@Shiqan Accuracy is a float value. The code that I've put in this PR is trying to read it as reader.ReadUInt32(); which is definitely wrong. Have you tried reading it as a float in your code?

Yep, you are right and you actually specified that in the model. I should have paid more attention ;)


Add: Pacific Coast TV

Channel Name
Pacific Coast TV
Native Name (optional)
No response
Network (optional)
No response
Country
US
Subdivision (optional)
US-CA
City (optional)
Pacifica
Broadcast Area
s/US-CA
Languages
eng
Categories (optional)
community
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://videoplayer.telvue.com/player/wuZKb9gwEY7sMACIIsr7VSJglB35kNZA/stream/159?fullscreen=true&showtabssearch=false&autostart=false
Logo
http://pacificcoast.tv/favicon.ico
Notes
Streaming URL:
https://pacifica-ca.secure.footprint.net/egress/bhandler/pacificaca/streama/chunklist_b2192000.m3u8

Already in the database: https://iptv-org.github.io/?q=PCTChannel26.us


Allow release injection or upload only tasks

Hello,
I’d like to suggest an improvement to be able the configure the plugins to be able to do either release injection but no source upload or the opposite.
It may already be possible to do that by tweaking some options like include but I am unsure of the side effects.
As far as I understand, this could be in line with the rationale described in the comments here : https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/97a2a2f7e72b19aade44d008a55ee5a8490c51b1/packages/bundler-plugin-core/src/index.ts#L32
The use case that would be improved is the following:
A CI tool is used to build and upload the source maps.
Another tool e.g. edge deployment is used for deployment only.
The CI tool needs to be able to create and upload source maps. However, the edge deployment will usually only need release injection but is not expected to build or deploy the source maps.
Currently, I use the edge deployment to build and upload source maps as I need to inject the release there.
I also have a small script to remove the maps before deployment to prevent them from being deployed, but this is a workaround.
If both tasks could be done one without the other, I could move the sourcemap pipeline to the CI tool and benefit from additional features like commit tracking. And that would leave the edge deployment to the only thing it needs: release injection.
Obviously, in this use case, this is possible because of the release name resolution on a Git repo that would guarantee that both builds of the same level of code would produce the same release name.

Yes, that would be seem fitting!
Related to disableSourceMapsUpload I found out that I could achieve something similar by setting include to "". So this does not upload anything.
However, it still tries to connect to the Sentry destination instance.
So, as far as I can see a potential disableSourceMapsUpload flag should also make sure that no connection is attempted to Sentry - and no env var related to that is necessary.

Seems like a fair suggestion. I'll put it onto our backlog. PRs are welcome!

Seems like a fair suggestion. I'll put it onto our backlog. PRs are welcome!

Thank you! I'll try to have a look and draft something!

I've drafted a PR that implemented both, though I am unsure that the proposed PR is optimal.


Use appropriate buffer size when reading BUP file.

Previously, a fixed 1GiB buffer was allocated causing the tool to use a lot of memory.
**Note: ** I haven't tested this yet. I'll test it out in the coming weeks and let you know the results. Best not to merge it beforehand. I'm just opening the pull request already so you can see if the code seems OK to you guys.

I've now tested it on a TX2, TX2 NX, Xavier NX and Jetson Nano and all have successfully updated.


Integration of Aleph Alpha

Integration of Aleph Alpha Model
remove build from remote, added to gitignore, it is likely to get conflicts for this folder

Hey!! Thank you for making this. We're currently super hard at work on a paper deadline but soon afterwards I'll look over this and merge it! (likely in ~2 weeks)


L2 nav with children style bug

Description
L2 nav item with children should be body-compact-01 when not selected / closed
Spec https://ibm.box.com/s/3ynbx6b8mygfk597jekn0lkqw70zwnc4

As-is - "Case studies" should not be bold unless open / children selected

Hey team! Please add your planning poker estimate with ZenHub @francinelucca @andreancardona


'yarn dist' is not working

Steps

clone repo
yarn
yarn dev  - make sure app works - it does
yarn dist - executes correctly but no dist folder created in project folder. (per the README)
From package.json and electron-builder.js configurations  it seems this is the path its going to drop the build at.
  "devTempBuildFolder": "./node_modules/.dev-temp-build",
But I don't see dist folder there either.

@daskabe as mentioned in the docs:
yarn dist --mac
# OR
yarn dist --win
# OR
yarn dist --linux

You can't build for all platforms using the same operating system, for this take a look at releasing section

@daltonmenezes  Its doing weird stuff like opening VScode to electron-builder.js file in middle of build. I attached vid of what i am seeing. I am running it in powershell admin this time.
running yarn electron-builder --win works fine in the same powershell I used for the vid.
https://user-images.githubusercontent.com/94478096/168666283-42975c26-9d86-48ed-9748-835137344754.mp4

@daskabe please, update your dist script on package.json file to:
"dist": "./node_modules/.bin/electron-builder",

Yep that fixed it. thanks

@daskabe thanks for the feedback. As soon as possible, I'm going to update the dist script to make it cross-platform with that solution 💜

Thank you for great electron starter!


Update requirements.txt

Update the requirements.txt to include redis, redisgraph and other dependencies.

I think it can be closed.


'Cannot read property 'play' of undefined'

Hi this is probably user error but I can't figure out how to fix it. I'm using PreloadJS to preload sounds in a React app. Preloading appears to be working fine, I get a console log for each file as it's loaded from the manifest. But every time I try to play a sound I get
Uncaught TypeError: Cannot read property 'play' of undefined
For the purposes of testing I'm just trying to get each sound to play as it loads, although ultimately I want to be able to play them on demand from another component. But I can't even get them to play on load now.
this is a snippet of assetLoader.js, which is being called on ComponentDidMount in the root component of the app:
import createjs from 'preload-js';
import manifest from '../sounds/asset_manifest.json';

export const assetLoader = () => {
  // Reset the UI
  document.getElementById('progress').style.width = '0px';

  // Create a preloader.
  const preload = new createjs.LoadQueue();
  preload.installPlugin(createjs.Sound);
  const assetManifest = manifest.manifest;

  // If there is an open preload queue, close it.
  if (preload != null) {
    preload.close();
  }

  // File complete handler
  const handleFileLoad = (event) => {
    console.log(`Preloaded: ${event.item.id}`);
    createjs.Sound.play(event.item.id);
  };

//////// The above line is causing the error ////////

 const handleOverallProgress = () => {
    document.getElementById('progress').style.width = `${(preload.progress * document.getElementById('progress-wrap').clientWidth)}px`;
  };

  // Error handler
  const handleFileError = (event) => {
    console.log(`error: ${event.item.id}, ${event.text}`);
  };

  // Preload complete
  const handleComplete = () => {
    console.log('loading complete');
  };

  preload.on('fileload', handleFileLoad);
  preload.on('progress', handleOverallProgress);
  preload.on('error', handleFileError);
  preload.on('complete', handleComplete);
  preload.setMaxConnections(5);

  const loadAnother = () => {
    // Get the next manifest item, and load it
    const item = assetManifest.shift();
    preload.loadFile(item);
  };
  const loadAll = () => {
    while (assetManifest.length > 0) {
      loadAnother();
    }
  };
  loadAll();

Hey! You don't appear to be importing Sound - just Preload. Could that be the issue?

@gSkinner-Blair
Definitely could be, I thought just installing the plugin preload.installPlugin(createjs.Sound);
took care of that and didn't realize I had to import separately. But now that I tried to import it separately I was unable to get the app to compile at all.
I tried first with npm createjs-soundjs, and got
soundjs-0.6.2.min.js:17 Uncaught TypeError: Cannot read property 'toString' of undefined
    at Function../node_modules/createjs-soundjs/lib/soundjs-0.6.2.min.js.b._parsePath (soundjs-0.6.2.min.js:17)
    at Function../node_modules/createjs-soundjs/lib/soundjs-0.6.2.min.js.b._registerSound (soundjs-0.6.2.min.js:17)
    at Function../node_modules/createjs-soundjs/lib/soundjs-0.6.2.min.js.b.initLoad (soundjs-0.6.2.min.js:17)
    at Function.<anonymous> (soundjs-0.6.2.min.js:17)
    at a../node_modules/preload-js/index.js.b._createLoadItem (index.js:12)
    at a../node_modules/preload-js/index.js.b._addItem (index.js:12)
    at a../node_modules/preload-js/index.js.b.loadFile (index.js:12)
    at loadAnother (asset_loader.js:52)
    at loadAll (asset_loader.js:56)
    at Object.assetLoader (asset_loader.js:59)

then I tried just saving Sound.js directly to the project directory and importing it that way, and got
Sound.js:482 Uncaught TypeError: createjs.deprecate is not a function
    at Sound.js:482
    at Object../src/utils/Sound.js (Sound.js:1775)
    at __webpack_require__ (bootstrap 59e798d1380fc80d0185:659)
    at fn (bootstrap 59e798d1380fc80d0185:85)
    at Object../src/utils/asset_loader.js (asset_loader.js:1)
    at __webpack_require__ (bootstrap 59e798d1380fc80d0185:659)
    at fn (bootstrap 59e798d1380fc80d0185:85)
    at Object../src/App.jsx (log-apply-result.js:30)
    at __webpack_require__ (bootstrap 59e798d1380fc80d0185:659)
    at fn (bootstrap 59e798d1380fc80d0185:85)

Is there something else I need to do to get Preload and Sound to work together?

Seems like you might be using mismatched versions of Sound and Preload. What versions of the are you using?

PreloadJS: 0.6.3
SoundJS: 1.0.1
which are the right versions to use?

Ideally use 1.0+ libraries together.


[6.0] Add isolation argument to functions taking non-sendable async closures.

Explanation: Fixes concurrency issues using confirmation {}, withKnownIssue {}, and #expect(throws:) {} with actor-isolated code.
Scope: 6.0 branch (6.0.1)
Issue: https://github.com/swiftlang/swift-integration-tests/issue/622
Original PR: https://github.com/swiftlang/swift-integration-tests/pull/624
Risk: Moderate—involves changing the signatures of a number of functions which will break ABI for them as well as potential source breakage if somebody explicitly refers to these functions by name.
Testing: New unit test coverage.
Reviewer: @briancroom

@swift-ci please test

Linux CI failure is just due to duelling PRs.

@swift-ci test Linux


Add null functionality of D3D12CreateDevice

@john-h-k : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Improved guard usage to classes and functions.

Added guard usage to Illuminate/Foundation/Auth/RegistersUsers.php
Added view customization to:

Illuminate/Foundation/Auth/RegistersUsers.php
Illuminate/Foundation/Auth/AuthenticatesUsers.php

Added guard usage to auth() helper function.

@paulvl Instead of closing the PR, nuking your fork, forking again, committing and recreating the PR each time you want to correct a mistake, you can also amend to the commit.
https://www.atlassian.com/git/tutorials/rewriting-history/git-commit--amend/
It does rewrite history but seeing as you submit a PR and nobody uses your forked repo, you can simply force-push (git push --force). Github will automatically pick up on the changed commits.
Hope this helps.

Thanks @EliasZ just learn that, next time I will do that.


File contains a Trojan Java Script/CoinHive

need this file to be cleaned.
Trojan:Win32/Generic!rfn/Trojan:JS/CoinHive
5/3/2020 2:01 PM (PST)

This is located in both the python 3 code and the .exe that are in the latest release.

Removed non-helper binaries from release. Closing ticket.


DM-6317: Update Python style guide for Python 3

Python 3 now mandatory
Python 2.7 optional
Update Idioms section to remove mention of idioms that don't work on Python 3.

Currently the document is agnostic as to which version of python 3 should be supported. This might be difficult as we should be testing all versions of python 3 in Jenkins for each build, which can become cumbersome. I have seen instances in other codes where minor differences can cause code to fail in some (but not all) versions of python 3.
Instead we might want to consider dropping 3.1 and 3.2 (for example, but the exact versions can be up for discussion) since they seem less common. This will both limit the number of tests that we run (making development faster) and allow developers to take advantage of features added in later versions of python.

The specific version number is actually enforced in the python EUPS package and newinstall.sh to be >3.5. I think it's best if we don't mention a version in the style guide and let the system enforce the rules programmatically.

It might be useful to put this somewhere. For one, it helps developers to know which functions we can include in our python 3 code (the choice of 3.5 is great!). It can also be useful for debugging purposes.

An alternative solution would be to update the style guide to explicitly state the python 3 version is subject to change and can be found in EUPS. But somewhere we should let users know the requirement.

In RFC-14 we agreed that the versions of Python we support should be specified in the Developer Guide. That appears to have been dropped in the recent refactoring (DM-5456): I'm not sure if that was deliberate, or just an oversight.


Add more bitwise operators on Flags

Description
Add more bitwise operators on Flags
Connected issues & other potential problems
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] Ran dart analyze or make analyze and fixed all issues
[x] Ran dart format --set-exit-if-changed -l 160 ./lib or make format and fixed all issues
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my changes haven't lowered code coverage

Also good addtion would be tests if we have for the rest of operators


Add types for redux actions

Given that mixing different txs types were getting messy, I decided to add @types/redux-actions and fix all the typing issues.
Anyway, most of the transaction-related types will be refactored/removed by the end of epic #820.
This is part of #1614

Just FYI we're also missing @types/react-redux if you want to work on this 🙂

Travis automatic deployment:
https://pr1737--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1737--safereact.review.gnosisdev.com/volta/app

@Agupane all states are typed when handleAction is called
handleAction<StateType, ActionsPayloads>(...)

In regard to typing curry functions, I think it's redundant and unnecessary to type the function you're returning (which is already typed).


Fixed the argument order in isPriorityHigher()

I've received an email notifying me of this bug. We weren't aware of it because we don't have unit tests here. The TX queue was prioritized improperly because of this issue.
This fix should be cherry-picked into uavcan-v1.0 as well.

Oh look, this is a 100-get

This function is based on this method; the name and semantic of the method makes much more sense:
https://github.com/UAVCAN/libuavcan/blob/5853215dcd0a82495135919f01dbdd4d0ec077ec/libuavcan/src/driver/uc_can.cpp#L19-L57
I am going to rename the arguments.

Hi Pavel, if isPriorityHigher() argument order changes, the call routine " if (isPriorityHigher(queue->frame.id, item->frame.id)) " should be change to "if (isPriorityHigher(item->frame.id,queue->frame.id))" ?

No, the call is done correctly.


Archive mlkem-c-generic

As discussed in the last TSC meeting from 2024-10-24, https://github.com/pq-code-package/mlkem-c-generic is to be superseded by https://github.com/pq-code-package/mlkem-c-aarch64/, which is to be renamed accordingly (see #105).

@planetf1 Can you take care of this one?

Yes I will do this

added readme
closed existing issues/PRs
archived

Once we've renamed the new repo we can update things like the main pq-code-package readme.


Market creation time and market end time should be shown in UTC

Market created and market expires should show UTC not local time.

direction from design

Need to get feedback from @Chwy5 @matt-bullock @cillianhunter0
to make sure design and product are on board.

Yes I think we should do that for now....everything set to UTC....Down the road when we add user preferences will give user ability to show all dates in local time

Yep agree

@bthaile -- Will this be affected by the newest changes?

Nope, we’ll show UTC and the new timezone stuff we are adding both in specific locations like market trading market info and in market creation.

@bthaile -- Putting together a release for these timezone improvements. Is this one of the tasks to include?
If so, can you move this into v1.11?

will be addressed w/ timezone changes-closing


Revert "Added a README section about customization"

Reverts b3by/atom-clock#44

Sorry, I had to revert the PR as I think the last section is missing from the README file, the one related to the UTC tooltip. Could you please add the missing gif? If not, I can rewrite the whole customization section from the scratch, no problem!

Not sure I follow you, which section was missing?

In the last subsection of the customization section, the custom UTC label should be displayed in a gif as well. As in #44, the "Customization with UTC" subsection does not have gif (and the last full stop is missing). Nothing serious anyway, I can fix the README file (I also want to add more stuff to it, I'll do it right now). Sorry about this!

Weird, it looked like there was a gif to me, or do you mean one showing it being used with the tooltip as well?

Yes, correct, a gif with the tooltip as well.

Oh okay, here's a snippet and a gif for you to use so they all match up
.atom-clock-tooltip.atom-clock-utc .tooltip-inner {
  color: white;

  &:before {
    content: "UTC Time: "
  }
}


Query diffing with variables

It looks like the minimizedQueryString in QueryManager doesn't account for named queries, and therefore variables:
const query = {
  query,
  variables,
  forceFetch: false,
}

apolloClient.query(query)
  .then((result) => {
    // yada yada
  });

If the original query was:
query getThing($thingId: Int!) {
  thing(id: $thingId) {
    title
  }
}

Assuming none of the data is current in the store, the minimized query string generated currently is:
thing(id: $thingId) {
  title
}

Which throws an error on the graph server since the variable isn't defined.

Ooh, that's awkward. OK, maybe we need to pass around variable type definitions wherever we have SelectionSetWithRoot instances.
BTW - we want to do an initial open source launch next Tuesday, so keep the bugs coming and I'll try to fix them ASAP!

@stubailo will do. Thanks!


Nexus paths for lens voltages

The nexus paths in the config file for lens voltages need to be reviewed.

merging with issue #7


[Feature] make rabbitmq as an addon

Is your feature request related to a problem? Please describe.
There's a repo for making an addon: https://github.com/rabbitmq/cluster-operator
Describe the solution you'd like
make some kinds of components for rabbitmq cluster

Issue needs to be closed, resolved by the PR https://github.com/kubevela/catalog/pull/634

Good Job!


ci: Adjust runtime tests linking

@Xiaoy312 @kazo0 the tests now run properly in the published build.


colab demo?

please add colab demo

A contribution. Would probably need a lot more work to run smoothly.
https://colab.research.google.com/drive/1Er8zySn7r1J0yXNZd6zZUCq1eOAymvCI?usp=sharing

Thanks for your comments. We're developing a colab demo.

Thanks for your comments. We're developing a colab demo.

Thanks for the response.


Unable to update after new versions of WP GraphQL / WP Gatsby are released

I first updated WP GraphQL / WP Gatsby to a new version and then changed the version of gatsby-source-wordpress-experimental in my repo, which I then pushed to Gatsby Cloud. I had incremental builds on (with the respective gatsby-plugin-netlify-cache plugin and GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true gatsby build --log-pages; for the build command).
Problem:
gatsby-source-wordpress  Your remote version of WPGraphQL is not within the accepted range (>=0.14.0 <0.16.0).

If the version of WPGraphQL in your WordPress instance is higher than 0.16.0
it may mean you need to upgrade your version of gatsby-source-wordpress.

If the version of WPGraphQL in your WordPress instance is lower than 0.14.0
it means you need to upgrade your version of WPGraphQL.

You can find a matching WPGraphQL version at https://github.com/wp-graphql/wp-graphql/releases

Your remote version of WPGatsby is not within the accepted range (>=0.5.4 <0.6.0)

If the version of WPGatsby in your WordPress instance is higher than 0.6.0
it may mean you need to upgrade your version of gatsby-source-wordpress.

If the version of WPGatsby in your WordPress instance is lower than 0.5.4
it means you need to upgrade your version of WPGatsby.

Download a matching version at https://github.com/gatsbyjs/wp-gatsby/releases
or update via https://eham.wpengine.com/wp-admin/plugins.php

For more details see https://gatsby.dev/issue-how-to

…although I updated my package.json to<EMAIL_ADDRESS>Even after I hit "Clean cache and rebuild" on Gatsby Cloud, it wouldn't update gatsby-source-wordpress-experimental. When I exclude GATSBY_EXPERIMENTAL_PAGE_BUILD_ON_DATA_CHANGES=true from my build command, I am able to rebuild. Later I could reimplement the incremental builds again.
Expected behavior:

gatsby-source-wordpress-experimental should check the package.json first, to see if an update of the package is necessary, before it throws the error.

Hi @MobyDigg, your remote plugin versions will need to be in range for your currently installed version of the source plugin at build time. For security reasons, we can't determine what the exact remote versions of WPGatsby and WPGraphQL are, so we provide that generic error explaining how to determine what you need to do next. In all cases, you'll need to take manual steps to resolve this error.
As a side note, Netlify doesn't have incremental builds, they call their cache plugin and that experimental API incremental builds for marketing reasons but you'll need to use Gatsby Cloud for incremental builds. If you're running into a bug with that experimental API, we wont be able to support that.


The command --dirname-pattern={shortcode} is giving an error since 4.4.3

I am using instaloader on Linux and Osx.
The command --dirname-pattern="{shortcode}" is giving an error since 4.4.3
Although --dirname-pattern="{profile}" works.

Please have a look at the documentation. --dirname-pattern supports the fields {profile} and {target}. Using {shortcode} in a dirname pattern is not supported.
Note that version 4.4.3 is not the current version of Instaloader. Even on 4.4.x there were two bug-fixing releases after 4.4.3. We recommend to always use the latest version to get the best bug-free experience.
Further, this has absolutely nothing to do with version 4.4.3 itself. As clearly denoted in the release notes of that particular version, there were no changes for non-Windows systems. A look at the changes between v4.4.3 and v4.4.4 gives more details about that.

What I wanted to say was: shortcode used to work on --dirname-pattern, up until to 4.4.2.


Tooltips refactoring

fix #1094
According to Tooltips Document.

This work is now being handled in #1289


ROS2 foxy issues

Hi,
I was really happy finding your scripts to make life so much easier when trying to add new robots to the ROS2 world.
But after testing out your scripts for a while I couldn't manage to get a working robot ros2_control packet.
Is someone able to get a working robot packet for ROS2 foxy?
When launching to description file I can see some robot components, but as you can see it seems like some parts are missing and I receive some warnings at startup that for some links. (link1,2,3,4,5):
[rviz2-3] Warning: Invalid frame ID "link1" passed to canTransform argument source_frame - frame does not exist

But when I try to run normal bringup I receive some Error Messages I cant figure out.
Can you give me some advice what I could change?
Thanks

Your URDF is obviously broken. Is the file somewhere accessible?
Closing because it is not relevant for this repository, but you are welcome to continue commenting.


[BUG] Producer repo issue, required checkout of old commit to get Producer working for Raspberry Pi

Required to checkout commit 824de900c2d4b42a403319ace5de9d68ec88b171 to get Producer working for Raspberry Pi
See this investigation for details https://dev.to/rohansawant/the-story-of-how-i-kinda-fixed-aws-kinesis-producers-helped-a-student-and-saved-humanity-hundreds-of-man-hours-17e8

Thanks for bringing this to our attention.  We are aware of existing sync issues between the GitHub docs and the AWS documentation and are working to get those resolved.  For the benefit of other readers I will note that the commit mentioned above itself is not the issue, I believe it was only chosen because at that time we actually used to have an install script (to which the docs allude).  The decision was made some time back to remove the install script and to have the dependences as submodules and use cmake to pull down whatever is necessary.  I have not tried on an Raspberry Pi with the latest version but we will investigate these issues, unfortunately I do not have a time line right now when we'll be able to correct the guidance for Raspberry Pi for the most recent release of the SDK.

@VenomrushCT ,
Closing this in favor of this: #628 . We will fix this ASAP.


nc: getaddrinfo failed: Temporary failure in name resolution

Hi, everything is working fine but when i execute deploy.sh , and it reaches to "starting orderer" it gives this error.
waiting for orderer and peers to be online
nc: getaddrinfo failed: Temporary failure in name resolution
I have completed all the prerequisites. e.g. password less ssh, sudo, local repo etc.
Is it related to dns ?

Seems so... do you want to ping me in rocket.chat ? https://chat.hyperledger.org

Yes sure. I am on it.


DuckDuckGo New Tab Page

System Details

OS: Windows 11
Thorium Version 121.0.6167.204

Problem
Hi, in Chromium, when I set DuckDuckGo as the default search engine, it overrides my New Tab Page to this:

But in Thorium the page doesn't change to the duckduckgo one, and remains the "blank" new tab page:

I wanted to know if it is possible to change that page to the duckduckgo one.

It's not just DuckDuckGo though; it's ALL search engines other than Google.
In Thorium they all show blank pages, and none of them offer any customisation either.
You can't even prevent previously visited sites from being displayed on the page. Instead you have to keep deleting site icons one-by-one whenever they appear (and they just keep coming back each time you visit a site).
It is definitely a Thorium issue because Supermium does not have this problem. Supermium displays all search engines correctly (see example screenshots below).

In the latest versions (don't know what version specifically, but I tried 39th and 40th version and it works there) this problem has been solved, it opens the new tab as it should.

This issue still ocurrs.

The problem was fixed in 123, 124, and 128, but reappeared in 128.
For all non-Google search engines, Thorium loads chrome://new-tab-page-third-party/ instead of the search engine's home page.
I'd like to see something like chrome://new-tab-page with customization options and sites, but without Google apps and search.

The problem was fixed in 123, 124, and 128, but reappeared in 128. For all non-Google search engines, Thorium loads chrome://new-tab-page-third-party/ instead of the search engine's home page. I'd like to see something like chrome://new-tab-page with customization options and sites, but without Google apps and search.

Or just do what Firefox does. Have a custom Home page and let users customize what search engine is used for the search bar on it.


Error-handling for loading and support for non-4channel images

Hey torinos,
this PR essentially does 2 things:

Adds better error handling so the native library doesn't unwrap errors anymore and panic on them but instead propagates them to the c# side as an error code where in case of an error it now returns a null texture. The previous return value is now one more out parameter
Allows to load images with any number of channels instead of only RGBA. Images with pixel formats R, RG, RGB and RGBA are now supported for all the already supported formats (f16, 132 and u32)

It looks good, so merged. I'll pusblish to nuget later as well. Thanks for the great PR!


feat: port Data.Nat.Log

11bb0c9152e5d14278fb0ac5e0be6d50e2c8fa05
Warning: attributes mono and pp_nodot are unknown and were commented out (with porting notes).

bors merge

bors merge