[Support]: Need help with tuning the color values

Describe the problem you are having
I used a python script to crop the images from my camera with the same coordinates provided in the config file for Swatch. I then uploaded the cropped images to Swatch to get the color values. Below are the results of this test as well as the result of running detect on the original uncropped pictures.
midday:
{
    "message": "The dominant color is (151, 36, 46) with a mixed palette as [(156, 39, 49), (183, 168, 169), (203, 139, 150), (85, 6, 13)]",
    "success": true
}

{
    "door": {
        "stop_sign": {
            "area": 81,
            "result": false
        }
    }
}

night_lights_on:
{
    "message": "The dominant color is (64, 22, 26) with a mixed palette as [(62, 14, 18), (79, 74, 74), (130, 84, 90), (84, 60, 68)]",
    "success": true
}

{
    "door": {
        "stop_sign": {
            "area": 99,
            "result": false
        }
    }
}

night_spotlight:
{
    "message": "The dominant color is (121, 64, 79) with a mixed palette as [(119, 62, 77), (203, 137, 152), (165, 119, 150), (163, 120, 127)]",
    "success": true
}

{
    "door": {
        "stop_sign": {
            "area": 846,
            "result": false
        }
    }
}

night_door_open:
{
    "message": "The dominant color is (19, 20, 19) with a mixed palette as [(11, 12, 12), (19, 20, 19), (4, 4, 4), (28, 26, 27)]",
    "success": true
}

{
    "door": {
        "stop_sign": {
            "area": 111,
            "result": false
        }
    }
}

I am not sure what lower and upper color values or min/max pixel thresholds I should use so that the first 3 situations are detected and the last one isn't. Any combination I use either one is incorrectly missed or incorrectly detected. For some reason, even when I had the lower RGB values larger than the values of the 4th situations, Swatch marked it as true.
Version
1.0.0
Swatch config file
# REQUIRED: Define a list of objects that are expected to be seen. These can be specific
# to one camera or common between many / all cameras
objects:
  # REQUIRED: Name of the object
  stop_sign:
    # REQUIRED: the lower R, G, B values that are considered a potential match for the object.
    color_lower: 64, 22, 26
    # REQUIRED: the upper R, G, B values that are considered a potential match for the object.
    color_upper: 151, 36, 46
    # OPTIONAL: the min number of pixels with R, G, B values within the bounds to be
    # considered a true positive. This is recommended to be set as a super small amount
    # could be a false positive. (Default: shown below)
    min_area: 1000
    # OPTIONAL: the max number of pixels with R, G, B values within the bounds to be
    # considered a true positive (Default: shown below).
    max_area: 100000

# REQUIRED: Define list of cameras that will be used for color detection.
cameras:
  # REQUIRED: Name of the camera
  garage_cam:
    # REQUIRED: Zones are cropped areas where the object can be expected to be.
    # This makes searching / matches for efficient and more predictable than searching
    # the entire image.
    zones:
      # REQUIRED: Name of the zone.
      door:
        # REQUIRED: Coordinates to crop the zone by.
        coordinates: 645, 712, 1368, 1434
        # REQUIRED: List of objects that may be in this zone. These correspond to
        # the objects list defined previously and are matched by name.
        objects:
          - stop_sign

Relevant log output
N/A

Any other information that may be helpful
No response

Hi, thanks for this comprehensive issue. There are a few things here:

Detect isn't meant to be run on the entire image and just the cropped image, it sounds like the results are from that which is interesting.
There is definitely some tuning to be done for some of these cases, but the night_stoplight case where the area is 846 seems to be a success unless that is for the entire image. Your min_area of 1000 is just too high for that small of an object.

My methodology so far is to use the rgb viewer to see what the dominant color is, set the lower r,g,b to the dominant r * .9,g * .9,b * .9 and the upper r,g,b to r * 1.1,g * 1.1, b * 1.1 and try that.
Thanks for the patience, as I said I intend to get a UI soonish that will make this easier

Also, the latest version will be changing the config so that it supports multiple color-variants so there aren't multiple objects created for the same "object" in different lighting conditions

Thank you for your response. Regarding #1, should I provide the cropped image to the detect API endpoint? I thought Swatch does the cropping itself. Otherwise, what's the point of providing the coordinates in the config?

Thank you for your response. Regarding #1, should I provide the cropped image to the detect API endpoint? I thought Swatch does the cropping itself. Otherwise, what's the point of providing the coordinates in the config?

Yes, that is correct, I think I just misunderstood what you meant above.

Thanks.

@backslashV You will want to check out latest 2.0 version which includes ui to adjust color values in real time to see what the mask will look like.

Absolutely. Will do it in some time. 👌

Would you be able to update the HA addon with the new config options and the UI editor?

Would you be able to update the HA addon with the new config options and the UI editor?

Did it not already get the new version? I'll do that

It seems the new config isn't supported on HA still:
Importing SwatchApp Config
Verified SwatchApp Config
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/opt/swatch/swatch/__main__.py", line 14, in <module>
    swatch_app = SwatchApp()
  File "/opt/swatch/swatch/app.py", line 21, in __init__
    self.__init_config__()
  File "/opt/swatch/swatch/app.py", line 35, in __init_config__
    user_config = SwatchConfig.parse_file(config_file)
  File "/opt/swatch/swatch/config.py", line 126, in parse_file
    return cls.parse_obj(config)
  File "/usr/local/lib/python3.10/site-packages/pydantic/main.py", line 511, in parse_obj
    return cls(**obj)
  File "/usr/local/lib/python3.10/site-packages/pydantic/main.py", line 331, in __init__
    raise validation_error
pydantic.error_wrappers.ValidationError: 2 validation errors for SwatchConfig
cameras -> garage_cam -> snapshot_config -> mode
  extra fields not permitted (type=value_error.extra)
cameras -> garage_cam -> snapshot_config -> snapshot_url
  extra fields not permitted (type=value_error.extra)```

Have you been running in HA OS the whole time? I think there may be more required to get it to work.
As far as the config goes can you paste the whole thing?

Yes, I'm using HA OS. Here's the config
objects:
  stop_sign:
    color_variants:
      midday:
        color_lower: 158, 140, 140
        color_upper: 194, 170, 172
      evening:
        color_lower: 162, 146, 153
        color_upper: 198, 178, 187
      night_lights_on:
        color_lower: 62, 40, 43
        color_upper: 76, 50, 53
      night_spotlight:
        color_lower: 89, 67, 80
        color_upper: 109, 81, 98
    min_area: 55000
    max_area: 190000

cameras:
  garage_cam:
    # auto_detect: 300
    # snapshot_config:
    #   snapshot_url: "<image url here>"
    #   save_detections: false
    #   save_misses: false
    #   mode: "all"
    #   retain_days: 7
    zones:
      door:
        coordinates: 641, 727, 1360, 1440
        objects:
          - stop_sign

The snapshot_url should just be url under snapshot_config

Thanks. Also "mode" should be "snapshot_mode", but I think "mode" is better since this is already nested under snapshot_config. There seems to be other errors with this update on HA:
Unexpected error fetching swatch data:
Traceback (most recent call last):
  File "/config/custom_components/swatch/api.py", line 98, in api_wrapper
    response = await self._session.get(
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 559, in _request
    await resp.start(conn)
  File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 898, in start
    message, payload = await protocol.read()  # type: ignore[union-attr]
  File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 616, in read
    await self._waiter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/config/custom_components/swatch/api.py", line 115, in api_wrapper
    return await response.json()
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 191, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/swatch/__init__.py", line 170, in _async_update_data
    raise exc
  File "/config/custom_components/swatch/__init__.py", line 168, in _async_update_data
    return await self._api.async_get_object_state("all")
  File "/config/custom_components/swatch/api.py", line 76, in async_get_object_state
    await self.api_wrapper(
  File "/config/custom_components/swatch/api.py", line 123, in api_wrapper
    raise SwatchApiClientError from exc
custom_components.swatch.api.SwatchApiClientError

Please let me know if I need to open another issue.

Are these errors happening while the addon is running? These would make sense if the addon isn't working since it would timeout because it can't reach it

Will update the config names shortly

Are these errors happening while the addon is running? These would make sense if the addon isn't working since it would timeout because it can't reach it

Yes, at least the new UI loads and the addon log shows
Starting SwatchApp
Importing SwatchApp Config
Verified SwatchApp Config
Starting Auto Detection for garage_cam
Starting snapshot cleanup for garage_cam

Okay, then yeah please create a new issue in the integration. Most likely it is not able to connect to the addon correctly, will have to see how I can fix that.


Index Modeling

Add index viewing, editing and deleting to the modeling system.

Started new-enum-handling branch.  Might abandon previous idea in this branch.


azcopy list: unable to specify folder depth to list

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.3.4
Which platform are you using? (ex: Windows, Mac, Linux)
Mac
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy ls URL-goes-here
What problem was encountered?
It lists the contents of every folder under that URL.  Not what I want at all.
How can we reproduce the problem in the simplest way?
Trivial.  This is a feature need/request.  The current tools is very limited and doesn't give what's desired.
Have you found a mitigation/solution?
Nope.

Interesting request. Could you think of a case where this would be useful?

Let's say I've mapped hundreds of large database takes to blob storage. Let's say I want to do processing on them in Databricks, so I break them into ~100MB parquet files. Each folder represents a table and each table has potentially hundreds of files within it.
I now want to know, which tables are mapped to blob storage and the tool doesn't give me a simple way to do that. The tool doesn't even give what the API gives, so rather then being a tool it is an obstacle or at least a distraction.
So the best is to throw it out.
If I use it in its current form I have to pipe the output throw sed or similar (and hope I'm not forced to use a Windows box where such tools aren't built in).
That's one of signs of use cases.
I'm sure you can use your imagination to see others that occur regularly.
Sent from my mobile, please expect typos.

From: adreed-msft<EMAIL_ADDRESS>Sent: Friday, April 10, 2020 11:25:22 AM
To: Azure/azure-storage-azcopy<EMAIL_ADDRESS>Cc: Ezra Epstein<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-storage-azcopy] azcopy list: unable to specify folder depth to list (#914)
Interesting request. Could you think of a case where this would be useful?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-azcopy/issues/914#issuecomment-612156950, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANLS6AYBVAHFV3SBGUTD6MTRL5QBFANCNFSM4LOX7VPA.

I +1 this one.
We have an storage that has perhaps 10 top folders. But those have perhaps thousands or millions of files underneath them... azcopy list on the top level takes forever because it tries to list every single file in the storage, even if I just want to check the names of 10 folders or so.

Even if directory depth is an option on the cli, how does it help resolve the issue you face. If you have 10 folders at top level and then possibly millions of files/directories inside it, with potential depth specified it will stop iterating after a certain level. But at the end you wish to copy those files as well in which case you will have to start another azcopy job for that path. If that's what you are going to do then why not start a azcopy job for each of the folder idependently so that azcopy does not have to iterate all of them in one go rather each instance iterate it independently.


[QUERY] Cosmos Sql Container Indexing Policy Included/Excluded paths are get only. Why?

Query/Question
Why are included and excluded paths get only for Cosmos creation via Azure.ResourceManager.CosmosDB? Shouldn't I be able to set the paths upon creation or update?
Environment:

Azure.ResourceManager.CosmosDB 1.0.0-preview.1
Windows 10 .Net Core 3.1
Visual Studio 16.7.7

@YalinLi0312 Please verify if this property is unsettable in the SDK, and route this issue appropriately

The IncludedPaths and ExcludedPaths in IndexingPolicy are unsettable, and I don't see they are read-only in it's swagger. @pakrym Can you take a look?

I found a way to achieve what I was looking for. After the initial SqlContainerCreateUpdateParameters creation, I have to add each item to the list like so:
var parameters = new SqlContainerCreateUpdateParameters(new SqlContainerResource(containerName), new CreateUpdateOptions())
        {
            Location = sqlDbLocation,
            Resource =
            {
                IndexingPolicy = new IndexingPolicy
                {
                    Automatic = containerConfig.Settings.IndexingPolicy.Automatic,
                    IndexingMode = MapToIndexingMode(containerConfig.Settings.IndexingPolicy.IndexingMode)
                },
                DefaultTtl = containerConfig.Settings.DefaultTtl,
                PartitionKey = new ContainerPartitionKey
                {
                    Kind = containerConfig.Settings.PartitionKey.Kind,
                    Version = containerConfig.Settings.PartitionKey.Version,
                    Paths = { containerConfig.Settings.PartitionKey.Path }
                }
            }
        };

        foreach (var includedPath in containerConfig.Settings.IndexingPolicy.IncludedPaths)
        {
            parameters.Resource.IndexingPolicy.IncludedPaths.Add(new IncludedPath
            {
                Path = includedPath
            });
        }

        foreach (var excludedPath in containerConfig.Settings.IndexingPolicy.ExcludedPaths)
        {
            parameters.Resource.IndexingPolicy.ExcludedPaths.Add(new ExcludedPath
            {
                Path = excludedPath
            });
        }

They are mutable collections. You can add/remove items from them.


Issue with device_sun_light_trigger

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.58.1
Component/platform:
device_sun_light_trigger
Description of problem:
I have defined a device group with me and my wife. But if one of us is home, with the lights turned off, and the other one comes home - the lights turn on.
Expected:
If one device in device group is "home" it shouldn't trigger the automation when the other device switches state to "home"
Problem-relevant configuration.yaml entries and steps to reproduce:
device_sun_light_trigger:
  light_group: group.card_alarm_lights
  light_profile: relax
  device_group: group.card_presense
  disable_turn_off: 1

card_presense:
  name: Presense
  entities:
    - device_tracker.rasmus__iphone
    - device_tracker.annbritts_iphone

Should there be two underscores in the device entity id?


Hotfix cleanup nao

Fixed PEP8 for nao_demo_python.py controller, removed useless DEF in Nao proto.
👍

:eyes:


ffmpeginput

FIX ffmpeginput to read all frame. Tested with ffmpeg-2.8.1

Can you explain briefly what problem this addresses? Is this related to issue #1003? Or is it something else?

first it resolved problem with codec AV_CODEC_CAP_DELAY
http://www.ffmpeg.org/doxygen/2.8/group__lavc__decoding.html#ga99ee61b6dcffb7817a275d39da58cc74
second i remove condition to run avcodec_decode_video2 this make that we
put to codec only frame with pts >= pts we looking thats why we see only
key frames.
if (current_pos >= m_subimage) {
avcodec_decode_video2 (m_codec_context, m_frame, &finished, &pkt)
}
Last I add if( current_frame == frame && finished) to be sure we display
exactly this frame we need (current_frame is take from m_frame->pkt_pts
http://www.ffmpeg.org/doxygen/2.8/structAVFrame.html#a47f555732f9c18928de727a163cd7cb6
). this can make infinity loop when something go wrong.
I have not  tested this on codec with bi-directional frame.
2015-12-10 19:40 GMT+01:00 Larry Gritz<EMAIL_ADDRESS>
Can you explain briefly what problem this addresses? Is this related to
issue #1003 https://github.com/OpenImageIO/oiio/issues/1003? Or is it
something else?
—
Reply to this email directly or view it on GitHub
https://github.com/OpenImageIO/oiio/pull/1288#issuecomment-163712920.

Thanks, I'll add that to the commit message before I merge.

Merged into master, with the fix described above and also a few very small formatting changes.
I'll eventually merge this into RB-1.6, but we're trying to lock it down for a release right now, so I don't want to merge it there until after the beta is over and a release is tagged. That will also give people a little while to test this further in master.


Version Bump

Currently the prerelease builds on the experimental feed are a lower version number than the last actual release; I propose that the patch number should be bumped on main as even if whatever release comes next warrants increasing the minor version number both version changes there would be an upgrade

Duplicate of #1199

Please don’t open issues asking when the next update is, please only open an issue if you have a genuine issue to report (like a bug or feature request). For everything else please use GitHub Discussions or Discord.

As for the experimental feed not targeting the next version, this has always been the case except for notable larger updates where we plan the release more carefully. The only valid versioning mechanism for the experimental feed is the build number, you should ignore the actual version number because we don't decide what vNext is until we're actually ready to release it.


Consider sorting entries in gradle/verification-metadata.xml always

Expected Behavior
verification-metadata.xml should have a consistent sort order of the entries.
For instance, Gradle should sort entries when running --write-verification-metadata ..., and Gradle could print a warning (or even error) when it detects unordered entries when reading the file (it is as cheap as O(N)).
Current Behavior
Newly added entries (e.g. after --write-verification-metadata sha256) are appended to the tail of the file, which causes inconsistent behavior, and it is prone to cause maintenance problems.
Context

"Pull request maintenance". If multiple pull requests add different dependencies, then (in the current scheme) they both will add lines to the end of the file, thus it will cause merge conflicts. Note: even though the conflict is trivial to resolve, it is a true merge conflict, and GitHub / Travis stops building the PR until the conflict is resolved.
On the other hand, if the file is always sorted, then the likelihood of the conflict is lower.

"Maintenance of multiple versions". If multiple versions of the same dependency are included in the verification metadata, then it would make sense to have them side by side.
For instance, it would be easier to notice "outdated" versions and remove them. The current approach of appending entries does not make it clear which artifacts have multiple known checksums.

"The lack of tooling" to support consistent formatting typically causes back-and-forth conversation of the code style to use. People might add entries to wrong locations even by mistake (e.g. by failing to sort properly).
There's a well-known case "Harry Potter and the Order of the Imports", and typically it is resolved by sorting imports alphabetically. For instance: https://google.github.io/styleguide/javaguide.html#s3.3.3-import-ordering-and-spacing

This is now done on master.


The server implementation for Linux is needed

Almost all servers are deployed in Linux(unix),  so it's a good reason to implement the linux verison of BarbaTunnel server.
Thanks.

I agree, It is an old project and I just moved it from codeplex and fix some issues. I wish I had time and make it as independent VPN. but unfortunately, I have no time to work on it more.


Issue/#133 fix the update task api

[ ] The pull request is complete according to the following criteria:

[ ] Acceptance criteria have been met
[ ] The documentation is kept up-to-date
[ ] Comprehensive tests (if applicable) have been generated and all pass.
[ ] The pull request describes the changes that have been made, and enough information is present in the description for any developer to understand what has changed
[ ] Commits have been squashed (or will be on merge).
[x] The branch name is descriptive and follows the pull request title format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
[x] The pull request title is of the following format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
[ ] The description uses github syntax to link to the issue. E,g Resolves se701g2/Doto#{Number}
[ ] At least two reviewers assigned. One of which must be the assigner of the issue.
[ ] If there are merge conflicts, run git rebase as opposed to git merge with master.

@jonathanvenema98 I dont think you should be reviewing this one since you committed to it I would wait for approval from 2 others before merging this one in

@jonathanvenema98 I dont think you should be reviewing this one since you committed to it I would wait for approval from 2 others before merging this one in

Good point, sorry about that. I suggested changes, but then applied them myself.


enh: add a (first) recipe in Status SDK

Time Spent

Date
Time

09/19/2023
2.0

09/21/2023
4.0

09/21/2023
4.0 (huddle)

Total
10.0

AWS Status API (Dev) Product: https://aws.amazon.com/marketplace/pp/prodview-curk2dsmlw67a

Acceptance Criteria
Recipe should:

[x] 1. Add a team
[x] 2. Add 3 members to this team (with 1 admin => who would be the creator of the team)
[x] 3. Report status as each of those members for a given day
[x] 4. Fetch status for that day

Feedback changes - 09/21/23

[x] 1. split the methods by the action performer in report team statuses file
[x] 2. use profile id instead of user id for member id
[x] 3. move hard coded values with structs to the bottom of the file (report_status) as constants
[x] 4. display session id, followed by count of tickets, then list of ticket urls
[ ] 5. run the recipe twice in the ac recording and share it
[ ] 6. fix stuct case to sync with API changes SIZE0.5

@AnishKhatri Updated fields.

Time spent to 2.0
kp_eLOE to 6.0 (so one session left on this)

@AnishKhatri Let's discuss this item. I might have some bandwidth to pick this up, and you can perhaps work on something else.

Is there anything you've that's worth committing for the couple of hours spent on this?

@AnishKhatri Let's not run over my LOE and spend additional time without checking with me first (like it happened this time).

PR: https://github.com/snowpal/pitch-go-status-sdk/pull/58

AC Recording
https://github.com/snowpal/pitch-go-status-sdk/assets/3121529/d912fe8d-2081-4dba-8bb0-122ff497afa4

Notes about time taken

Getting acclimated with Status API and Endpoints
Ran into issues with Add Ticket because our error handler wasn't reporting specific message
Make iterative commits, and keep things smaller

https://github.com/snowpal/pitch-go-status-sdk/releases/tag/v1.0.5


AdVAE + 2 stage

This might be the parallel script:
#!/bin/bash
# This runs parallel experiments over all datasets.
# USAGE EXAMPLE
# 	./run_two_stage_parallel.sh knn vae_LOSS_images 3 1 2 datasets_tabular.txt
# Run from this folder only.
MODEL=$1                     # second stage model
TABLE_NAME=$2          # name of table with stored results
NUM_SAMPLES=$3	# how many repetitions
MAX_SEED=$4		# how many folds over dataset
NUM_CONC=$5		# number of concurrent tasks in the array job
DATASET_FILE=$6	# file with dataset list

LOG_DIR="${HOME}/logs/two_stage_${MODEL}"

if [ ! -d "$LOG_DIR" ]; then
	mkdir $LOG_DIR
fi

while read d; do
	# submit to slurm
    sbatch \
    --array=1-${NUM_SAMPLES}%${NUM_CONC} \
    --output="${LOG_DIR}/${d}-%A_%a.out" \
     ./2stage_${MODEL}_run.sh $MAX_SEED $d ${TABLE_NAME} 10
done < ${DATASET_FILE}

Don't forget to make the run scripts executable (chmod +x runscript.sh)


HIVE-27075: removeDuplicateCompletedTxnComponents() task must start o…

…nly if compactions are enabled.

In the HiveAcidHouskeeperService, (AcidHouseKeeperService.java#L85 ). removeDuplicateCompletedTxnComponents() task is an expensive operation an needed only for compaction. Therefore, we should probably move it under the isCompactorEnabled if block.
What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Unit test - TestDbTxnManager2#javatestRemoveDuplicateCompletedTxnComponents()

isCompactorEnabled =
        MetastoreConf.getBoolVar(conf, MetastoreConf.ConfVars.COMPACTOR_INITIATOR_ON) || MetastoreConf.getBoolVar(conf,
            MetastoreConf.ConfVars.COMPACTOR_CLEANER_ON);
    txnHandler = TxnUtils.getTxnStore(conf);

it's wrong, we should only consider COMPACTOR_INITIATOR_ON config (auto-compaction)


Re-add mutation to set a custom attribute

Ref #122
Sets a custom attribute value.

 Create GraphQL mutations to allow modification of company and event fields


What organisms is this designed for?

Description of feature
It is unclear if this pipeline will work on any organism assembly?
Is it haploid genomes only?
Is it especially for bacteria?

Hi @tseemann
At Plant&Food we have been using the pipeline to QC genomes of plants, animals, and fungi. It was also tested with a bacterial genome.
We have also used it on diploid genomes. The two haplotypes can be processed in parallel by inputting them as two fasta files.


Add pandoc as run-time requirement.

rmarkdown uses pandoc to convert files to various formats. I've added it as a run-time requirement.
Demonstrating the issue:
$ conda create -n testrmd r r-rmarkdown
$ source activate testrmd
$ R
> library("rmarkdown")
> file.create("test.Rmd")
> render("test.Rmd", html_document())
Error: pandoc version 1.12.3 or higher is required and was not found.
> file.remove("test.Rmd")
$ source deactivate
$ conda remove -n testrmd --all

Fortunately this missing dependency likely doesn't negatively impact most conda R users because pandoc is installed with r-essentials (which depends on notebook -> nbconvert -> pandoc).
@johanneskoester @bgruening @mdehollander

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

CI builds are passing. Appveyor keeps failing only because one of the matrix builds gets the HTTP error that for some reason is common at the moment.

Thanks @jdblischak!


bug fix for Kia Niro EV and FP2.0 FW_version for 2019 Kia Niro EV

Choose one of the templates below:
Fingerprint
This pull requests adds a fingerprint for <Kia - Niro-EV - 2019 - EX>.
Description
Bug fix and new fingerprint 2.0 for 2019 E-Niro
Testing
'tmux a' was showing controlsd error before. EON could not load OP. after the code changes, everything is working. Drove around and verified OP functions work.

Fingerprint 2.0 How did you extract the data?
i tested data/openpilot/selfdrive/car -> ./fw_version --scan
process and data not...
Found FW versions
{
}

I followed the instruction on this wiki, https://github.com/commaai/openpilot/wiki/Fingerprinting, but it did not work until yesterday, when I pull the latest code from HKG_community branch.


[folding] Disabling plugin removes collapse (+-) of block codes

VSCode Version: 1.29.1
OS Version: Windows 10 1809

Steps to Reproduce:

Open .ps1 file with some code (may work for other files, haven't checked)
Collapse / uncollapse some code block - this works
Disable any plugin
Option to collapse/Uncollapse is gone (+- is not visible).

This happens until you reload VSCode. The same thing happens when you reinstall the plugin. Until VSCode is reloaded you can't collapse code anymore.

Does this issue occur when all extensions are disabled?: Yes/No

I can't reproduce. What extension do you disable? Do you also reload?

It doesn't really matter which. What I noticed just now is that if you Disable extension, Enable it back and Disable again I can use folding again properly.
Reloading fixes things but the point is that if you disable the plugin and don't reload folding stops working (unless you do a workaround as above). It simply disappears.

Please notice the movie starts with already "workaround" in place as I started recording after some testing. But after I reload the window .. it shows how the problem looks like.
Let me know if you need anything else?

Thanks for the great GIF, sadly, I can't reproduce (yet)

dup of #75726


Split out BCrypt hashing to make it reusable

This logic is generic and reusable -- hash a secret; and take an unhashed secret and compare it to a hashed secret. This breaks this out to make it reusable in other places. Specifically, we use this in our own token auth at Bonobos that we plan to split out as a Devise extension. This will make that possible without copy & pasting this code.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:

Thanks for the quick merge.


adding and updating tests

@Ali-Razmjoo Updated connector tests due to the error produced in following ci run
https://github.com/spiderxm/Python-Honeypot/runs/3188636695?check_suite_focus=true


Ikea repeater causes plugin to fail

Issue description
I'm using the Ikea E1746 repeater with the latest version of the Domoticz Zigbee2mqtt plugin. This causes the plugin to fail to work with the error in logs below.
The repeater is supported by zigbee2mqtt as described here - https://www.zigbee2mqtt.io/devices/E1746.html
The repeater is the next device in the list according to the Zigbee2mqtt output.
Deleting the repeater from my Zigbee network makes everything work again, but of course I'd rather have the repeater present.
This used to work ok in the prior version.
Additional information
Zigbee2MQTT version: 1.10.0-dev
Python version: 3.7.3
Domoticz version: v4.11724
Plugin version: 0.1.0
Logs
Feb 23 17:55:16 domoticz domoticz: (Zigbee) Received available devices list from bridge Feb 23 17:55:16 domoticz domoticz: (Zigbee) Device BASICZBR3 0x00124b001e721f58 (Ryans_Blanket) Feb 23 17:55:16 domoticz domoticz: (Zigbee) Device BASICZBR3 0x00124b001e7286ac (Laurens_Blanket) Feb 23 17:55:16 domoticz domoticz: (Zigbee) Device BASICZBR3 0x00124b001e73367e (Dereks_Blanket) Feb 23 17:55:16 domoticz domoticz: (Zigbee) Device BASICZBR3 0x00124b001e728d41 (Lindseys_Blanket) Feb 23 17:55:16 domoticz domoticz: (Zigbee) 'onMessage' failed 'KeyError'. Feb 23 17:55:16 domoticz domoticz: (Zigbee) ----> Line 186 in '/home/pi/domoticz/plugins/zigbee2mqtt/plugin.py', function onMessage Feb 23 17:55:16 domoticz domoticz: (Zigbee) ----> Line 100 in '/home/pi/domoticz/plugins/zigbee2mqtt/plugin.py', function onMessage Feb 23 17:55:16 domoticz domoticz: (Zigbee) ----> Line 167 in '/home/pi/domoticz/plugins/zigbee2mqtt/mqtt.py', function onMessage Feb 23 17:55:16 domoticz domoticz: (Zigbee) ----> Line 141 in '/home/pi/domoticz/plugins/zigbee2mqtt/plugin.py', function onMQTTPublish Feb 23 17:55:16 domoticz domoticz: (Zigbee) ----> Line 32 in '/home/pi/domoticz/plugins/zigbee2mqtt/devices_manager.py', function update F

Could you please provide full error message and ideally MQTT message which causes plugin to fail

The full error message from the Domoticz log file is as above.
The Zigbee2MQTT message is:
info  2020-02-23 17:55:16: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{"ieeeAddr":"0x00124b00014d2b83","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"zStack12","dateCode":"20190608","lastSeen":1582480516619},{"ieeeAddr":"0x00124b001e721f58","type":"Router","networkAddress":23937,"model":"BASICZBR3","friendly_name":"Ryans_Blanket","manufacturerID":0,"manufacturerName":"SONOFF","powerSource":"Mains (single phase)","modelID":"BASICZBR3","hardwareVersion":1,"dateCode":"20190907-V102","lastSeen":1582480422923},{"ieeeAddr":"0x00124b001e7286ac","type":"Router","networkAddress":35024,"model":"BASICZBR3","friendly_name":"Laurens_Blanket","manufacturerID":0,"manufacturerName":"SONOFF","powerSource":"Mains (single phase)","modelID":"BASICZBR3","hardwareVersion":1,"dateCode":"20190907-V102","lastSeen":1582480425168},{"ieeeAddr":"0x00124b001e73367e","type":"Router","networkAddress":40790,"model":"BASICZBR3","friendly_name":"Dereks_Blanket","manufacturerID":0,"manufacturerName":"SONOFF","powerSource":"Mains (single phase)","modelID":"BASICZBR3","hardwareVersion":1,"dateCode":"20190907-V102","lastSeen":1582480461851},{"ieeeAddr":"0x00124b001e728d41","type":"Router","networkAddress":35338,"model":"BASICZBR3","friendly_name":"Lindseys_Blanket","manufacturerID":0,"manufacturerName":"SONOFF","powerSource":"Mains (single phase)","modelID":"BASICZBR3","hardwareVersion":1,"dateCode":"20190907-V102","lastSeen":1582480506375},{"ieeeAddr":"0x000d6ffffe2ee6a9","networkAddress":23880,"model":"E1746","friendly_name":"IkeaRepeater01","manufacturerName":"IKEA of Sweden","powerSource":"Mains (single phase)","modelID":"TRADFRI signal repeater","hardwareVersion":1,"softwareBuildID":"2.0.019","dateCode":"20180828","lastSeen":1582480323832}]}'
Of which, the JSON content is:
{   "ieeeAddr": "0x00124b00014d2b83",   "type": "Coordinator",   "networkAddress": 0,   "friendly_name": "Coordinator",   "softwareBuildID": "zStack12",   "dateCode": "20190608",   "lastSeen":<PHONE_NUMBER>619 }, {   "ieeeAddr": "0x00124b001e721f58",   "type": "Router",   "networkAddress": 23937,   "model": "BASICZBR3",   "friendly_name": "Ryans_Blanket",   "manufacturerID": 0,   "manufacturerName": "SONOFF",   "powerSource": "Mains (single phase)",   "modelID": "BASICZBR3",   "hardwareVersion": 1,   "dateCode": "20190907-V102",   "lastSeen":<PHONE_NUMBER>923 }, {   "ieeeAddr": "0x00124b001e7286ac",   "type": "Router",   "networkAddress": 35024,   "model": "BASICZBR3",   "friendly_name": "Laurens_Blanket",   "manufacturerID": 0,   "manufacturerName": "SONOFF",   "powerSource": "Mains (single phase)",   "modelID": "BASICZBR3",   "hardwareVersion": 1,   "dateCode": "20190907-V102",   "lastSeen":<PHONE_NUMBER>168 }, {   "ieeeAddr": "0x00124b001e73367e",   "type": "Router",   "networkAddress": 40790,   "model": "BASICZBR3",   "friendly_name": "Dereks_Blanket",   "manufacturerID": 0,   "manufacturerName": "SONOFF",   "powerSource": "Mains (single phase)",   "modelID": "BASICZBR3",   "hardwareVersion": 1,   "dateCode": "20190907-V102",   "lastSeen":<PHONE_NUMBER>851 }, {   "ieeeAddr": "0x00124b001e728d41",   "type": "Router",   "networkAddress": 35338,   "model": "BASICZBR3",   "friendly_name": "Lindseys_Blanket",   "manufacturerID": 0,   "manufacturerName": "SONOFF",   "powerSource": "Mains (single phase)",   "modelID": "BASICZBR3",   "hardwareVersion": 1,   "dateCode": "20190907-V102",   "lastSeen":<PHONE_NUMBER>375 }, {   "ieeeAddr": "0x000d6ffffe2ee6a9",   "networkAddress": 23880,   "model": "E1746",   "friendly_name": "IkeaRepeater01",   "manufacturerName": "IKEA of Sweden",   "powerSource": "Mains (single phase)",   "modelID": "TRADFRI signal repeater",   "hardwareVersion": 1,   "softwareBuildID": "2.0.019",   "dateCode": "20180828",   "lastSeen":<PHONE_NUMBER>832 }

Added support for this repeater to the plugin. But it shouldn't be the reason why plugin failed.

That's fixed it - now the log says the following:
2020-02-25 20:44:51.559 (Zigbee) Device 0x000d6ffffe2ee6a9 (IkeaRepeater01) doesn't have "model" attribute, skipped

@derekoharrow should the issue be closed?

Yes. Thank you.


Example for fixing SSR flicker in NextJS page router

Would you happen to have any ideas on how to fix the SSR flicker in the NextJS page router?

the SSR flicker in the NextJS page router

I don't know what this is referring to.
Did you check out the FAQ entry about this though? https://github.com/bvaughn/react-resizable-panels?tab=readme-ov-file#how-can-i-use-persistent-layouts-with-ssr

Ya I was asking if you had a way to do that with the NextJS page router.

Sorry 🤷🏼  Does it not work? If it doesn't work, I'll need to see a repro.

I was just asking if there was a way to persist the layout using a cookie without using react server components as the next/headers API seems to only be available when using the app router.
I'm getting this hydration error in the console:
Prop `data-panel-size` did not match. Server: "null" Client: "13.5"
Sorry, I realized my first question wasn't clear at all. It's flickering because I have a virtualized component that is using a resize observer and since it can't access the localStorage on the server it causes it to render with a width of 0 for the first render when navigating to a new page causing a flicker.
So I was just trying to ask if you have an example of how to use the cookies to persist the layout when using the NextJS page router.

I was just asking if there was a way to persist the layout using a cookie without using react server components

There might be but it's not something I've thought about or have an answer for.

I'm getting this hydration error in the console:
Prop `data-panel-size` did not match. Server: "null" Client: "13.5"

It sounds like you need to access the cookie value on the server somehow. I don't know how, within Next's ecosystem, except for using next/headers.
This is probably a question you'd have better luck asking them. 😄

Thanks for sharing your solution! 🙇🏼


Wrong way of rendering React Components

It seems this line renders React Components in the wrong way.
Is this intended or did I miss some context?! 🤔
https://github.com/Hashnode/starter-kit/blob/c06bebf8e29ab4251d8892248b61a3c829fbe46e/packages/blog-starter-kit/themes/personal/pages/[slug].tsx#L177
Should be something like this
{post ? <Post publication={publication} post={post /> : <Page page={page} />}

The problem is explained in this video: https://youtu.be/QuLfCUh-iwI?t=25

@panda-sandeep see https://github.com/Hashnode/starter-kit/pull/64


DP to CP related Issues in APK Agent

Description:
The following issues can be seen on the APK Agent side.

For an API with prod httproutes, APIM shows endpoints under sandbox endpoints. - Fixed
Portal visibility should be enabled by default. Otherwise endpoint of the URL is not displayed in the devportal. - Fixed
Restrict API creation only for the carbon.super. Enable DP to CP for super tenant only. - Fixed
Update helm chart to have a global subscription enable flag for the Enforcer for DP to CP mode. - Fixed
CORs settings should be added to the API to get this working with the DevPortal. Should be a Global Config.
API Subscription does not work if the API name is having spaces. - Fixed
Internal test token should work. Right now Authentication CR is not there for this type of APIs. - Fixed
Fix query param - preservePortalConfigueation : - Fixed
API UUID should be populated in the CR. - Fixed
Populate all the certs related to backend, mtls, etc.
Handle Rate Limits.
We should not show websocket URLs for the graphql APIs.

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Apart from the items 10,11 and 12, other issues are already fixed. Hence resolving this issue.


Delete preview tag for staging slots

Hi @odvoskin, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Oded Dvoskin). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@odvoskin : Thanks for your contribution to the Azure documentation! The author, @azdocprs, has been notified to review your proposed change.

@rothja Hi Jason. Please review these changes. Thanks.

#sign-off

Thanks folks :)


[HOTFIX] Fix Broken Activity IDs

Tickets addressed: N/A
Review: By commit
Merge strategy: Merge (no squash)

Description
Fix some broken activity instance IDs which were left as long instead of being converted to ActivityInstanceId.
Verification
Tested locally, requesting test from UI developer who found the issue as well.
Documentation
None.
Future work
Hopefully none.

Still encountering the same error in merlin server:
[qtp2050370411-29] WARN io.javalin.Javalin - Uncaught exception
java.lang.NullPointerException: Cannot invoke "gov.nasa.jpl.aerie.merlin.server.remotes.postgres.SimulatedActivityRecord.childIds()" because the return value of "java.util.HashMap.get(Object)" is null
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.GetSimulatedActivitiesAction.lambda$get$0(GetSimulatedActivitiesAction.java:74)
	at java.base/java.util.HashMap.forEach(HashMap.java:1421)
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.GetSimulatedActivitiesAction.get(GetSimulatedActivitiesAction.java:72)
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.PostgresResultsCellRepository.getSimulatedActivities(PostgresResultsCellRepository.java:280)
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.PostgresResultsCellRepository.getSimulationResults(PostgresResultsCellRepository.java:235)
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.PostgresResultsCellRepository.getSimulationState(PostgresResultsCellRepository.java:220)
	at gov.nasa.jpl.aerie.merlin.server.remotes.postgres.PostgresResultsCellRepository$PostgresResultsCell.get(PostgresResultsCellRepository.java:443)
	at gov.nasa.jpl.aerie.merlin.server.services.CachedSimulationService.getSimulationResults(CachedSimulationService.java:14)
	at gov.nasa.jpl.aerie.merlin.server.services.GetSimulationResultsAction.run(GetSimulationResultsAction.java:52)
	at gov.nasa.jpl.aerie.merlin.server.http.MerlinBindings.getSimulationResults(MerlinBindings.java:140)

Closing until the issue is resolved.

This branch was a mess. What happened was the following:
I was working on a separate task, and wrongly thought I found some usages of Long that needed to be converted to ActivityInstanceId that were causing issues. At that same moment, Chris let me know of a bug he ran into in the same file I was looking at, and I immediately thought that it was caused by the issue I had seen, and I jumped on the "fix". Turns out I had actually implemented the code right the first time (last week), and while unrolling these changes I remembered making these decisions quite consciously. Mondays are hard. New PR coming.


snes everdrive 5X base vs snes9X running nested

i tested the snes everdrive 5X base , i tested nes supermariobros 3 on it but it crashes on the fortress level saying that memory is full, i tested metroid on it but all i got is a black screen, if i tryed kirby's adventures on it, i got an error masage saying that the rom is too big,
i check the specs and it says snes roms up to 7,5MB alltrough it does contain 8MB of ram (does it uses the 0,5MB for the os menu or something??)and it does contain 128KB of SRM save,
here are pictures of bothe the everdrive and snes9X so you can judge if the $104 was worth it or just a waste of money for something not fully met the full requirements for nested,,
test on snes everdrive X5 base
srm test 4

srm test 4 on snes9X

srm test 5 on snes everdrive X5 base

srm test 5 on snes9X

snes srm test 10 on snes everdrive X5 base

snes srm test 10 on snes9X

if it turns out that theres yet no everdrive to fully met the nested requirements, that will be a huge disappointment, also if only the snes fx pack/sd2snes does met the full requirements for nested to run on it, well; that's a big slap in the face since it costs over $200 for wich i could spend on an actual nes and many famiclones,
besides i hope you will fix that bug in your software that can detect the total ram size including the srm ram on flash cards sothat we no longer will end upwith falsch info about it,becouse will it correctly detect the amount of ram once you change the ram size of nested,but not on snes flashcards,,
and lastly i readed that some everdrives don't support 16KB  srm files while other everdrive flashcards does support 16KB files,so it really get's confusing wich specefic everdrive is needed to fully run nested on it.

128KB SRAM is size 7. You should be testing size 8 and 7 to see which one works. The display bug with the total of 144KB only happens with 16KB SRAM or below.

Well i want to lower it to 7 just for the sake,but am afraid that it will only crash games even futher earlier on, as i have learned that the more you decrease the ram and then run it on snes9X ,games will crash much earlier on(unless nested it somehow able to care about how memory will be used whether it’s 64KB,128KB,256KB and monitors it to prevent games from crashing, but it may slow things down as well ,i don’t know ) ,but hey i will try it anyways just for you and  see if it will work or not and tell you about the results,,
But theres 1 thing what confuses the most out of me, i con understand that sram is resizible to account for different flashcards,but theres also an option to add sram file you your nes games in wich i always tout that it was only used for save games,but if it turns out that you must add srm file to serve as extra ram for nested, then do i have to add a 8KB srm file to it? Or will that just eat up parts of the neseccary 128 srm ram to render it pointless??
In fact i notice no performance increase or decrease on snes9X or flashcard whether i add 2KB sram,8sram or 32sram,also snes9x treats those added sram as save files even if games don’t support saves,
Now if adding sram files is indeed only is ment to for saving data,then i consider you better off calling it “add save file” because eventrough these are sram files, but saying add sram file or increasing sram size can  confuses the crap out of many i suppose.
Verstuurd vanaf mijn iPhone
Op 4 okt. 2021 om 20:27 heeft Myself086 @.***> het volgende geschreven:

128KB SRAM is size 7. You should be testing size 8 and 7 to see which one works. The display bug with the total of 144KB only happens with 16KB SRAM or below.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Myself086/Project-Nested/issues/35#issuecomment-933742840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVVWMQFAXPBTA74IWFZKBYDUFHW2JANCNFSM5FJT53LA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I've already said that Nested can detect how much SRAM is available, the wrong 144KB was only visual. The visual bug itself can only happen for sizes 16KB or less.
You can change the amount of SRAM that your SNES file should have as part of the settings on the exe's main window, it's a blue setting called "Sram size".

I'm confused as to why you're saying "add sram file".
Test 10 shows that you only have 32KB of SRAM on your Everdrive.

Hil,
I changed the sram size from 8 to 7 and i also activated trunscate memory just in case and i also did not added any sram file to it this time, and yes this time supermariobros 3 finally fully runs on everdrive(aside from the roulette and memory game off couse)  ,and i beated it as well,
So that’s something absolutely fantastic, HOWEVER i still do get a black screen with metroid,
Btw i should,ve to mention that while supermariobros 1 does run fine on my powerpak ,HOWEVER  that game starts ironically enough on a strange world on both the everdrive and snes9X, that’s pretty strange, well thx alot for this golden advice .
Verstuurd vanaf mijn iPhone
Op 4 okt. 2021 om 23:19 heeft Myself086 @.***> het volgende geschreven:

I've already said that Nested can detect how much SRAM is available, the wrong 144KB was only visual. The visual bug itself can only happen for sizes 16KB or less.
You can change the amount of SRAM that your SNES file should have as part of the settings on the exe's main window, it's a blue setting called "Sram size".

I'm confused as to why you're saying "add sram file".
Test 10 shows that you only have 32KB of SRAM on your Everdrive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Myself086/Project-Nested/issues/35#issuecomment-933864174, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVVWMQGY76YDBENNMAP7YUDUFIK6VANCNFSM5FJT53LA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi i finally do got metroid work on the everdrive this time, and you wanna know how?, because i trunscated the rom aside from setting sram size to 7,without truncating the rom i just couldn’t get it working on the everdrive(despite i got no error massage about it’s rom size ), however i still just don’t get this freaking damn game working on my powerpak no matter wich region version i tryed aaarrrggg,
1 cool thing is trough while kirby’s adventure normally cannot run at all on the everdrive because of exceeding the 7,5MB/8MB limit of it,HOWEVER, once i trunscated the rom to 4,5MB i finally do got a glitchy title screen with v1,3 and nothing at all with v1.4, so basically instead of patching the game with obsolute data alongside the nessecary data ,it only patches the game with the required data to make it smaller ,so let’s say that for example that there’re 20 digitized psg sounds ,but a game only uses 5 psg sounds,so instead of patching the game with 20 psg sounds from wich 5 psg sounds are turned on while the remaining 15 psg sounds are turned off, it only patches the game with those 5 needed psg sounds while the other remaining 15 psg sounds turned off are not patched at all with the rom,just in order to make the patched rom smaller,same with the used colors, etc,,, this is absolutely fantastic,so nested cannot only turn off settings but also discard them optionally just in order to make truncating roms possible, this is awesome because it makes up for the everdrive having only 8MB of sdram, my powerpak does contain 16MB of sdram ,so i was able to play kirby’s adventure trough level 1 because of this, wich normally wouldn’t be possible on the everdrive but by truncating roms below the 8MB limit from the everdrive i don’t need 16MB of sdram anymore wich is absolutely great,
Verstuurd vanaf mijn iPhone
Op 5 okt. 2021 om 01:22 heeft johannes mutlu @.***> het volgende geschreven:
 Hil,
I changed the sram size from 8 to 7 and i also activated trunscate memory just in case and i also did not added any sram file to it this time, and yes this time supermariobros 3 finally fully runs on everdrive(aside from the roulette and memory game off couse)  ,and i beated it as well,
So that’s something absolutely fantastic, HOWEVER i still do get a black screen with metroid,
Btw i should,ve to mention that while supermariobros 1 does run fine on my powerpak ,HOWEVER  that game starts ironically enough on a strange world on both the everdrive and snes9X, that’s pretty strange, well thx alot for this golden advice .
Verstuurd vanaf mijn iPhone
Op 4 okt. 2021 om 23:19 heeft Myself086 @.***> het volgende geschreven:

I've already said that Nested can detect how much SRAM is available, the wrong 144KB was only visual. The visual bug itself can only happen for sizes 16KB or less.
You can change the amount of SRAM that your SNES file should have as part of the settings on the exe's main window, it's a blue setting called "Sram size".

I'm confused as to why you're saying "add sram file".
Test 10 shows that you only have 32KB of SRAM on your Everdrive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Myself086/Project-Nested/issues/35#issuecomment-933864174, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVVWMQGY76YDBENNMAP7YUDUFIK6VANCNFSM5FJT53LA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Clarification needed

I create a policy on a resource group with "not allowed resource type" set to "virtualNetwork/subnets". How is it possible that despite the policy I can crete a VNET in this RG, and a VNET is created along with its first subnet?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ba25bd9e-cf20-53f1-bf99-a1b73069cb22
Version Independent ID: ba5c333b-8abf-a47c-96f3-429b8519036b
Content: Sample - Not allowed resource types - Azure Policy
Content Source: articles/governance/policy/samples/not-allowed-resource-types.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@mcurko Thanks for the comment. We are looking into this and will get back to you shortly.

@mcurko Thanks for the question. That parameter, which is a strongType of resourceTypes follows the resource provider naming format of <owner>.<rp>/<resource>. In this case, it looks like you want to use Microsoft.Network/virtualNetworks/subnets instead of virtualnetwork/subnets.
Since this policy uses strongType, that means you can see the values to use if you assign it through the portal (you don't have to complete the process to see the values). On the Parameters tab, you can see the filterable drop-down of available values:

If you select the one(s) you want, and then proceed to the Review + create tab, the UX shows the actual parameter and the value that you chose.  You can use this as guidance for when you create the assignment via SDK:

Hope that answers your question!  Please feel free to continue the discussion if needed on this item or open a new item for other docs issues.  Thanks again!
@MicrosoftDocs/azure-cxp-triage #please-close

No, I selected the right resource, here I typed the label from the text box from the image you attached.
Now I see that my subnets (I created another one 10 minutes after the VNET) are listed as non-compliant! If I try to add another subnet (now, 2 hours after the creation of the policy and the VNET), I finally receive an error:
Failed to add subnet 's3' to virtual network 'vnet5'. Error: Resource 's3' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"Not allowed resource types","id":"/subscriptions/hidden/resourceGroups/rg5/providers/Microsoft.Authorization/policyAssignments/207cacc3787f42179ddd92a7"},"policyDefinition":{"name":"Not allowed resource types","id":"/providers/Microsoft.Authorization/policyDefinitions/6c112d4e-5bc7-47ae-a041-ea2d9dccd749"}}]'.
Next, thing, I try to create another VNET in the RG, and it succeeds!
Strange, isn't it?

Sounds like it is working as expected. Note that a new policy assignment can take 30 minutes to be applied (details here: https://docs.microsoft.com/azure/governance/policy/how-to/get-compliance-data#evaluation-triggers). Once applied, your existing subnets are now non-compliant and creating new subnets is denied per your policy assignment. Creating a virtual network without a subnet should still succeed, since that isn't denied by the definition or assignment parameters.
However, if you continue to see unexpected behavior, please open a Support Ticket so the team can engage directly with you to resolve the issue.

VNET was created with a subnet!

Then please open a Support Ticket so the team can engage directly with you to resolve the issue.

I can confirm that the delay was causing the issue in my case.
After waiting a few minutes, the policy correctly denied the creation of subnets.
Use this to trigger a scan:
az policy state trigger-scan --resource-group <group>


Update react-side-effect to the latest version 2.1.1, please

Could you please update react-side-effect to its latest version, 2.1.1?
react-side-effect that react-document-meta is using still uses componentDidMount which will cause annoying warning message.
I saw latest react-side-effect has change it to unsafe_componentDidMount.

Is there any update on this one? Would love to have it sorted out please :)

yes. I have switched to react-helmet


why not use email and password loging chatgpt?

use cookie is very difficult for most people. I see some one has code to support use email and password to login chatgpt. for example https://github.com/acheong08/ChatGPT/blob/075014c609b4fe41e7f85ce96ee87fdc2e6eafcc/src/revChatGPT/revChatGPT.py#L331
so,could your code support this in the futrue?

Can I directly add the variable of API to start BOT?

Can I directly add the variable of API to start BOT?

chatgpt does not support API now.

today ，I used python openai package to connect chatgpt by API, it work.

today ，I used python openai package to connect chatgpt by API, it work.

Yes, there are several wechatbot in China that use chatgpt's API to run without any restrictions!

today ，I used python openai package to connect chatgpt by API, it work.

Yes, there are several wechatbot in China that use chatgpt's API to run without any restrictions!

可以说一下这些接口在哪吗

在官方的文档就有介绍https://beta.openai.com/docs/api-reference/introduction
通过Python的openai包的命令就可以实现。

use openai API to accesse is too expensive. The free one is only $18, and it can only be used for 3 months. I hope someone can find a way to permanently access it for free.


Add executionContext/create command

Pull Request Description

closes: #587
Changelog:

Add ContextRegistry that handles execution context requests and routes them to the appropriate context manager.
Add ContextManager that holds a set of contexts created by the client.
Add requestId to the Runtime.Api commands

Implementation
Legend:

1  - Singleton
*C - Created per client
*H - Request is forwarded to the intermediate handler. Created per request.

                   *C                            1
  +------------------+   *H    +------------------+
  | ClientController +-------->+ ContextRegistry  |
  +--------------+---+         +---------+--------+
                 ^                       |
                 |                       |
                 |                       v      *C
                 |             +---------+--------+
                 +-------------+  ContextManager  |
                               +---------+--------+
                                         ^
                                         |*H
                                         v       1
                               +---------+--------+
                               | RuntimeConnector |
                               +------------------+

Important Notes

JSON API changed. executionContext/create sent without parameters, and created contextId is returned in the response.
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, Rust or Haskell style guides as appropriate.
[x] All code has been tested where possible.

Changelog:

add: missing unhandled methods
remove: ClientManager
remove: IdGen
refactor: correlationId


Update the README file

Hey! I created the repo, but I could really use help with crafting a better README. Notice that I created the repo at #1


fix: Remove redundant graph walks

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

5 of 6 (83.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 29.25%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/graph/ops.rs
5
6
83.33%

Totals

Change from base Build<PHONE_NUMBER>5:
0.05%

Covered Lines:
1631

Relevant Lines:
5576

💛  - Coveralls


--stats produces no output

We should probably rename it now that we have first pass / second pass also.

See https://github.com/xiph/rav1e/pull/1457 - if you think it should be renamed, what should it be renamed to, considering it does nothing?

Since --stats is now removed, I am closing this issue.


fix filter position for Im2Col

cac52fdebb292bc7706383d07c7987be66882085 fixed the filter position for
the reference class but the same problem exists in the Im2Col class.
This patch makes the calculation of the filter position consistent
with the reference quantized class and the gemm/fused conv_ops
classes.
@petewarden you reviewed the reference class fix. Would you have the time to review this too?

Can one of the admins verify this patch?

Jenkins, test this please.

@petewarden Can you give an official approval or comments for this PR? Thanks.


Link to issuing Authority not working

Example corp: https://orgbook.gov.bc.ca/entity/BC0432724
In the credential history scroll down to the Buy BC Logo Licensee and open it up.

Click on the Investment Agriculture Foundation BC link.
Expected behavior:

The link would take you to a page providing more information about the issuing authority.

Actual Behavior:

Takes you back to the page your already on, the corp's page.

This issue seems to affect the issuing Authority links of any credentials that is not associated to the BC Corporate Registry, so all credentials from:

Liquor and Cannabis Regulation Branch
Ministry of Energy, Mines and Low-carbon Innovation
Investment Agriculture Foundation BC
Ministry of Environment and Climate Change Strategy

This is due to the fact the issuers, other than BC Corporate Registry have not registered a URL that would be used for this link.  The issuer registrations can be found here; https://orgbook.gov.bc.ca/api/v2/issuer.
The default in this case is to have the issuing Authority link link back to the corporation to which the credential was issued.

This default behavior is a little confusing.  I'm wondering if it would be better for the link to go to a generic Issuing Authority page that displays the registration information (and logo if one is registered) for the issuer.  In all cases there is an email address registered for the issuers, but that information is inaccessible through the current UI.

@swcurran, Thoughts?

First, I would encourage us to go back to the issuers and get the URLs and add them in. @DJ-Gordon -- is that something you can do?  I assume once we have them, we can add them easily to the database?
That said, what do we do if we don't have them?
I'd suggest one of two behaviours:

No link
Link to this page: https://orgbook.gov.bc.ca/about/orgbook-data

I don't think it worth adding another page specifically for this situation as it encourages bad behaviour by the issuers -- not supplying the needed info.
Personally, I think I would go with no link.


[question] Aeotech Gen 2 DSB28

I have a Aeotech Gen DSB28. I have been using this device for several years and it has been working fine.
Used it with different controllers and it has worked fine. It also worked in the beginning with zwave2mqtt. But at some point it stopped to work. Due to several reasons I have not been able to report it until now.
I am able to add the device, and it looks ok. But I am not able to get it to auto report. I have tried to use the UI to set it up. And also the aeotech excel sheet and do it manually by setting parameter 101-103 and 111-113.
When I click refresh, I am able to poll new values.
Any ideas?

node_106.json.zip

@haavardNO Did you checked the group associations? Does it have Lifeline association correctly setted up? cc @AlCalzone


Updated architecture of CodeRefactor

The new system provides a more convenient mechanisms for expansion.
Developers of third-party plug-ins can add commands refactoring for languages that are not officially supported by the editor, for example TypeScript.
You will be able to add commands for a specific language, such as find all references, which will run through the Haxe Compiler.
@elsassph @Neverbirth please review this PR.

I'll try to validate this one soon, but since it's so big it may take a bit of time...

@Neverbirth, how does this look?

@Neverbirth thanks, I am very happy


Return trace span ID in a header

@kyessenov commented on Mon Oct 09 2017

Can you elaborate?

Can we add more of a description of desired use case here?  I want to be sure I'm on the same page as the FR.


☂ Supporting Xcode 11 and iOS 13 Beta

This task tracks issues with Xcode 11 and iOS 13. Both are currently in Beta, with an expected release date sometime in September 2019.
Related Issues

Supporting Project Catalyst: Running iPad apps on macOS
Initial UIKitForMac support
Initial UIWindowScene support

Known Issues

[ ] Compatibility with new UIScene, UISceneDelegate APIs

Fixed Issues

[x] EXC_BAD_ACCESS in fishhook.c (iOS 13/Xcode 11)
[X] __unused signature changed

#25182 is apparently related.

I've opened a PR for #25182 at #25212

[ ] A lot of things in UIApplication / UIApplicationDelegate are deprecated and you're supposed to move to UIScene / UISceneDelegate (this is groundwork for supporting multiple windows on iPadOS and macOS -- and even if you don't, this is where the APIs will evolve in the future). I might be interested in sending some pull requests with the necessary changes (necessary for those willing to implement multiple window support in their own apps -- with full backwards compatibility so that most people don't have to do anything)

Copying over from a thread on discord (sorry about formatting):
I'm doing some digging around React Native core to prepare it for support for new UIScene based APIs — that's necessary to be able to support multiple windows on iPadOS (and therefore, multiple windows on macOS via Catalyst)
a problem I'm seeing is that there are many APIs that are RCTBridge-global — and assume the app has one window
for example, status bar is a NativeModule - https://github.com/facebook/react-native/blob/master/React/Modules/RCTStatusBarManager.m
this is a problem, because we need to be able to target a specific UIScene, not the whole UIApplication
I'm interested in helping out on this front as I'd like @Nozbe 4 to work nicely with multiple windows
now, this would be almost a non-issue if every UIScene (window) had its own bridge (the bridge could reference the  uiscene somehow, and each would have its own native module). BUT this is not the right way to do this
the right way (for perf, memory usage, and usability) is to have one RCTBridge and multiple root views
I think we should therefore transitions APIs like this to be component-based instead of plain NativeModules. this is also relevant e.g. for Dimensions
Another idea I've just had is that could have a react context automatically set up, such that when there's a RCTRootView, anywhere in the react tree you can useIOSScene() (or a simple context consumer) that would return some sort of tag uniquelly identifying a UIWindowScene (that this component is embedded in) that you could pass on to NativeModule-based APIs. That would ease the transition and still allow people to invoke some of these functions imperatively if needed.
cc @shergin @fkgozali

Update regarding StatusBar:
I tried upgrading StatusBar to work with multiple UIScenes by passing rootViewTag to StatusBarManager: https://github.com/facebook/react-native/pull/25425/files
I did most of the work, but what I realized is that there is no one-to-one replacement API for UIApplication.setStatusBarStyle etc. — UIWindowScene.statusBarManager is a read-only API.
What Apple really wants us to do is to finally adopt view-controller based status bar management. Here's what I suggest:
I think we should add a RCTRootViewController: UIViewController class, that will conform to status bar management protocol, and have the right hooks for StatusBarManager to be able to control this. The default template for new apps would use RCTRootViewController in the AppDelegate.m. This would be the new default, but 100% opt in — old apps don't have to use it (StatusBarManager would fall back to deprecated UIApplication-based APIs), or brownfield apps / apps that use react-native-navigation or other libraries that mess with view controllers.
WDYT? I'm willing to send the necessary PRs :)

Using a RCTRootViewController seems to be the best solution here. This also requires that UIViewControllerBasedStatusBarAppearance is set to true (this is the default, so simply deleting the entry will do).
To offer a fallback-mode we could control what is returned in childViewControllerForStatusBarStyle on this RCTRootViewController. Default should pass on to whatever view controller is on top, this would nicely resolve the current compatibility issues with 3rd-party plugins. And the old-style calls to StatusBarManager simply set the status on RCTRootViewController and trigger a setNeedsStatusBarAppearanceUpdate - this should result in roughly the same experience as currently.
If native view controllers are used (e.g. navigation plugin) then these need to be updated to support the legacy API.

We had a similar idea around a RCTRootViewController a while back as we needed "base view controllers" for integrating React Native into brown field: https://github.com/maicki/react-native-view-controller .
There is no status bar appearance handling in there yet though.

Update regarding StatusBar:
Other than Peter's comments, I received no specific guidance as for view controller-based status bar management, so I just went ahead and made this PR proposing the adoption of RCTRootViewController: https://github.com/facebook/react-native/pull/25919

Will the existing applications built with React Native crash when users upgrade to ios13?

Will the existing applications built with React Native crash when users upgrade to ios13?

@carlosalmonte04 nope, they work. I've been on iOS 13 (beta) for months, and actively developing my React Native app on my phone with no issues (expect minor things like textbox placeholder texts hard to see because of color changes in Dark Mode etc).

So, if I understood correctly, the StatusBar component is not working on iOS 13 yet? not even with the last RN version?  I was going to open an issue because I couldn't make it work with React Native 0.59.1 and iOS 13 beta.

@cuttlas Pretty sure <StatusBar /> works fine on iOS. We have an app in production with React Native 0.59.9 that uses it, and my phone has been running iOS 13 since it first went in beta. Same goes for current iOS 13.1 beta 3.
But in any case I would recommend upgrading to React Native 0.60.x before making any kind of compatibility determinations.

@rgomezp That error has been fixed.
https://github.com/facebook/react-native/issues/25138

Anybody know anything about:
Last Exception Backtrace:
0   CoreFoundation                	0x193d73278 __exceptionPreprocess + 220 (NSException.m:199)
1   libobjc.A.dylib               	0x193a9c0a4 objc_exception_throw + 56 (objc-exception.mm:565)
2   APP_NAME.               	0x1023cbcb4 RCTFatal + 668
3   APP_NAME.               	0x10241c824 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&) + 712
4   APP_NAME.               	0x10241c3b4 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dy... + 88
5   libdispatch.dylib             	0x193a40658 _dispatch_call_block_and_release + 24 (init.c:1408)
6   libdispatch.dylib             	0x193a411cc _dispatch_client_callout + 16 (object.m:495)
7   libdispatch.dylib             	0x1939f3290 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044 (inline_internal.h:2487)
8   CoreFoundation                	0x193cf0c74 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1749)
9   CoreFoundation                	0x193cebc68 __CFRunLoopRun + 2004 (CFRunLoop.c:3069)
10  CoreFoundation                	0x193ceb16c CFRunLoopRunSpecific + 464 (CFRunLoop.c:3192)
11  GraphicsServices              	0x19db23328 GSEventRunModal + 104 (GSEvent.c:2246)
12  UIKitCore                     	0x197d55d0c UIApplicationMain + 1936 (UIApplication.m:4687)
13  APP_NAME.               	0x1022bc738 main + 88 (main.m:16)
14  libdyld.dylib                 	0x193b76424 start + 4

Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib        	0x0000000193b6bebc __pthread_kill + 8
1   libsystem_pthread.dylib       	0x0000000193a87794 pthread_kill$VARIANT$mp + 112 (pthread.c:1456)
2   libsystem_c.dylib             	0x00000001939dc8c0 __abort + 112 (abort.c:136)
3   libsystem_c.dylib             	0x00000001939dc850 abort + 112 (abort.c:107)
4   libc++abi.dylib               	0x0000000193b347d4 abort_message + 128 (abort_message.cpp:76)
5   libc++abi.dylib               	0x0000000193b349c4 demangling_terminate_handler() + 296 (cxa_default_handlers.cpp:66)
6   libobjc.A.dylib               	0x0000000193a9c358 _objc_terminate() + 124 (objc-exception.mm:701)
7   APP_NAME.               	0x00000001028611a4 CLSTerminateHandler() + 348
8   libc++abi.dylib               	0x0000000193b41304 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59)
9   libc++abi.dylib               	0x0000000193b4129c std::terminate() + 44 (cxa_handlers.cpp:87)
10  libdispatch.dylib             	0x0000000193a411e0 _dispatch_client_callout + 36 (object.m:498)
11  libdispatch.dylib             	0x00000001939f3290 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044 (inline_internal.h:2487)
12  CoreFoundation                	0x0000000193cf0c74 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1749)
13  CoreFoundation                	0x0000000193cebc68 __CFRunLoopRun + 2004 (CFRunLoop.c:3069)
14  CoreFoundation                	0x0000000193ceb16c CFRunLoopRunSpecific + 464 (CFRunLoop.c:3192)
15  GraphicsServices              	0x000000019db23328 GSEventRunModal + 104 (GSEvent.c:2246)
16  UIKitCore                     	0x0000000197d55d0c UIApplicationMain + 1936 (UIApplication.m:4687)
17  APP_NAME.               	0x00000001022bc738 main + 88 (main.m:16)
18  libdyld.dylib                 	0x0000000193b76424 start + 4

@jorisw did you turn on dark appearance in the simulator?

@zhigang1992 I have now, no issues here.

Both are currently in Beta, with an expected release date sometime in September 2019.

@hramos The issue is still opened, does it mean that Xcode 11 is not officially supported yet? Any official plans/date to resolve this issue?

@rumax I haven't heard anything from official support from the RN team, but I am supporting my app in production on iOS 13. The only big big issues I have ran into are the fishhook.c EXC_BAD_ACCESS bug (very critical) and contact imports don't allow access to the notes property.
I haven't ran into anything else major quite yet, but we are monitoring closely.
I hope this helps.

See #26594 .
I cannot build my app after updating xCode to 11.0.

+1

+1

react-native": "0.58.4" -- admittedly a little backdated
xcode 11
I downgraded xcode 11 to 10.3 in a fit of panic/rage, apologies if I'm not helpful.
I could build the app but it got completely hung up on an error similar to below as soon as the app got past the splash screen. Everything went back to normal after downgrading Xcode to 10.3. Digging around, it seems to pertain to 'autoResize' on the IOS side. I have zero clue how I would debug this in a meaningful way. Any pointers I could find assumed the dev had coded in Objective-C/Swift.
<NSLayoutConstraint:0x7f844b716390 H:|-(30)-[UIButton:0x7f844b4be3c0'LOGIN']   (Names: '|':UIView:0x7f844b492a80 )>",
    "<NSLayoutConstraint:0x7f844b706ee0 H:[UIButton:0x7f844b4be3c0'LOGIN'(100)]>",
    "<NSLayoutConstraint:0x7f844b705dd0 H:[UIButton:0x7f844b4be3c0'LOGIN']-(80)-[UIButton:0x7f844b4c0520'SIGNUP']>",
    "<NSLayoutConstraint:0x7f844b706f30 H:[UIButton:0x7f844b4c0520'SIGNUP'(100)]>",
    "<NSLayoutConstraint:0x7f844b7147c0 H:[UIButton:0x7f844b4c0520'SIGNUP']-(30)-|   (Names: '|':UIView:0x7f844b492a80 )>",
    "<NSLayoutConstraint:0x7f844b519f70 'UIView-Encapsulated-Layout-Width' H:[UIView:0x7f844b492a80(375)]>
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x7f844b705dd0 H:[UIButton:0x7f844b4be3c0'LOGIN']-(80)-[UIButton:0x7f844b4c0520'SIGNUP']>

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

+1

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

I have the same problem

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

I have the same problem

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

I solved my problem by use the following method:
in your project directory, open file in myproject/node_modules/react-native/React/Base/RCTModuleMethod.mm. Then correct as below: https://github.com/facebook/react-native/pull/25146/files#diff-263fc157dfce55895cdc16495b55d190

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

I solved my problem by use the following method:
in your project directory, open file in myproject/node_modules/react-native/React/Base/RCTModuleMethod.m. Then correct as below: https://github.com/facebook/react-native/pull/25146/files#diff-263fc157dfce55895cdc16495b55d190

I also solved the problem by use your method, thx

I am using UIView and UITableView without storyboard in sildeMenu.
After clicking slide menu image button, TableView appear in ios12 but in ios13 only transparent screen appear and none of table data appear.
`- (UIModalPresentationStyle)modalPresentationStyle
{
return UIModalPresentationOverCurrentContext;
}

(void)viewWillDisappear:(BOOL)animated
{
[super viewWillDisappear:animated];
CGRect frame = self.lst_MainMenu.frame;
frame.size.width = 0;
[UIView beginAnimations:nil context:nil];
[UIView setAnimationDuration:0.1];
[UIView setAnimationDelegate:self];
[UIView setAnimationDidStopSelector:nil];
self.lst_MainMenu.frame = frame;
[UIView commitAnimations];

}
//

(void)viewDidAppear:(BOOL)animated
{
[super viewDidAppear:animated];
//    NSInteger r = self.arr_list.count;
//
//    CGRect frame = self.lst_MainMenu.frame;
CGRect frame = self.orgFrame;
//    frame.size.height = self.lst_MainMenu.rowHeight * r;
frame.size.width = 270;
frame.size.height += self.ypos;
frame.origin.y = self.ypos;
CGRect startFrame = frame;
startFrame.size.width = 0;
self.lst_MainMenu.frame = startFrame;

//    self.lst_MainMenu.frame = frame;
self.lst_MainMenu.hidden = false;
self.lst_MainMenu.separatorInset = UIEdgeInsetsZero;
if ([self.lst_MainMenu respondsToSelector:@selector(layoutMargins)]) {
    self.lst_MainMenu.layoutMargins = UIEdgeInsetsZero;
}

[UIView beginAnimations:nil context:nil];
[UIView setAnimationDuration:0.1];
[UIView setAnimationDelegate:self];
[UIView setAnimationDidStopSelector:nil];
self.lst_MainMenu.frame = frame;
[UIView commitAnimations];

}
//

(void)viewDidLoad
{
[super viewDidLoad];
// Do any additional setup after loading the view from its nib.
self.lst_MainMenu.delegate = self;
self.lst_MainMenu.dataSource = self;
self.lst_MainMenu.rowHeight = 44.0f;
self.arr_list = _arr_list;
self.orgFrame = self.lst_MainMenu.frame;
self.lst_MainMenu.tableFooterView = [[UIView alloc] init];
if (@available(iOS 13.0, *)) {
self.overrideUserInterfaceStyle = UIUserInterfaceStyleLight;
}
}

//

(void)didReceiveMemoryWarning
{
[super didReceiveMemoryWarning];
// Dispose of any resources that can be recreated.
}

//

(void) touchesBegan:(NSSet<UITouch *> *)touches withEvent:(UIEvent *)event
{
[self dismissViewControllerAnimated:YES completion:nil];
}

//

(NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
{
return 1;
}

//

(NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section
{
return self.arr_list.count;
}

//

(UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
{
UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:@"Cell"];
if (cell == nil)
{
cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:@"Cell"];
}
[cell setBackgroundColor:[UIColor blackColor]];
cell.textLabel.textColor = [UIColor whiteColor];
[cell setSelectionStyle:UITableViewCellSelectionStyleGray];
cell.textLabel.text = self.arr_list[indexPath.row];
return cell;
}

//

(void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
self.lst_MainMenu.hidden = true;
[self dismissViewControllerAnimated:YES completion:nil];
[self.delegate selectedMainMenuItem:indexPath.row];
NSLog(@"Selected : %ld", (long)indexPath.row);
[self.lst_MainMenu deselectRowAtIndexPath:indexPath animated:YES];
}
`

when I push to RN page with Xcode 11, the iOS app crashes， but it's no problem with Xcode 10.
Exception 'createView:(nonnull NSNumber *)reactTag viewName:(NSString *)viewName rootTag:(attribute((unused)) NSNumber *)rootTag props:(NSDictionary *)props is not a recognized Objective-C method.' was thrown while invoking createView on target UIManager with params (
2,
RCTView,
1,
{
flex = 1;
pointerEvents = "box-none";
}
)
RCTFatal
-[RCTBatchedBridge callNativeModule:method:params:]
__33-[RCTBatchedBridge handleBuffer:]_block_invoke.388
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

I solved my problem by use the following method:
in your project directory, open file in myproject/node_modules/react-native/React/Base/RCTModuleMethod.m. Then correct as below: https://github.com/facebook/react-native/pull/25146/files#diff-263fc157dfce55895cdc16495b55d190

Excelent, works! :))

Our app is already on RN 0.61.4 and was trying to run with xcode 11.2.1 but the app crashed in xcode after the build is successful. Did anyone face this problem before? I need to use xcode 11 because I will need Apple Authentication. Screenshots for xcode crash is attached. Thanks a lot as I have zero knowledge on iOS Dev but started purely on RN :D

Our app is already on RN 0.61.4 and was trying to run with xcode 11.2.1 but the app crashed in xcode after the build is successful. It was running fine for xcode 10. Did anyone face this problem before? I need to use xcode 11 because I will need Apple Authentication. Screenshots for xcode crash is attached. Thanks a lot as I have zero knowledge on iOS Dev but started purely on RN :D

I managed to get xcode 11 working. I needed to update Firebase and Facebook Login SDK :D

We're having the same issue in production.
This error results in 0.005 crashes per session for our users, not terrible, but not great either.
We can't see any pattern in what platform version the error occurs on. The number or crashes on 12.x and 13.x seem directly related to how many users adopted the version.
Dependencies

react: 16.9.0
react-native: 0.61.2

iOS app rejected by apple due to following issue, app crashed on iOS version 13, on other it is working fine.
{"app_name":"","timestamp":"2020-02-13 12:19:03.15 -0800","app_version":"1.0.0","slice_uuid":"353b6dbc-72d2-3f16-894f-ee0be7638ff7","adam_id":1495537992,"build_version":"2","bundleID":"com.org.app","share_with_app_devs":true,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 13.3.1 (17D50)","incident_id":"1DBCAB2C-8819-4B6E-8024-E637BD8D436A","name":""}
Incident Identifier: 1DBCAB2C-8819-4B6E-8024-E637BD8D436A
CrashReporter Key:   a1e0c5d1372b56e5695f9f8c1a2d812178664397
Hardware Model:      xxx
Process:              [56724]
Path:                /private/var/containers/Bundle/Application/7277B38A-A665-42D4-889E-B348881CCF3C/
Identifier:          com.org.app
Version:             2 (1.0.0)
AppStoreTools:       11C29
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.orgapp [2722]
Date/Time:           2020-02-13 12:19:02.9953 -0800
Launch Time:         2020-02-13 12:18:42.8564 -0800
OS Version:          iPhone OS 13.3.1 (17D50)
Release Type:        User
Baseband Version:    n/a
Report Version:      104
Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, scene-create watchdog transgression: application<com.org.app>:56724 exhausted real (wall clock) time allowance of 19.70 seconds | ProcessVisibility: Foreground | ProcessState: Running | WatchdogEvent: scene-create | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 25.900 (user 25.900, system 0.000), 65% CPU", | "Elapsed application CPU time (seconds): 0.292, 1% CPU" | )
Triggered by Thread:  0

This looks like you are stalling the main thread roo long on startup, the SPRINGBOARD watchdog timer kicks in. Are you maybe doing sync network requests on startup?

Same here. App rejected because of crashes on 13.3.1. Works fine when running a debug version of the app. Will post an update here if I figure it out

Looks like a recent change to RCTAlertController is causing RN Alerts to no longer display in iOS 13+ apps that use the new Scene APIs. Related issue here https://github.com/facebook/react-native/issues/31251


test: update opae metrics tests

remove mock d5005 metrics tests

Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage decreased (-0.05%) to 63.987% when pulling 3c2537e650c41fbc606ae8fe94734d873ee21c56 on aravuri/fix_fpgainfo_tests into 9a22d09f6e61a212b0f0194ce05f4bfb30454496 on master.


Ghidra fails to decompile function: 'Low-level Error: Unable to merge address forced indirect'

Describe the bug
Decompiling the function FUN_180059a30 throws the error Low-level Error: Unable to merge address forced indirect.
The function is part of a custom type checking compiler for a modified version of squirrel.
IDA is able to generate pseudocode for the function.
To Reproduce
Steps to reproduce the behavior:

Download the binary (server.dll.zip)
Decompile the function FUN_180059a30 at 0x180059a30
After a few seconds the decompiler should throw the error Low-level Error: Unable to merge address forced indirect

Expected behavior
The decompiler is able to generate pseudocode
Attachments
server.dll.zip
Environment:

OS: Windows 10
Java Version: 17.0.6
Ghidra Version: 10.3
Ghidra Origin: official GitHub distro

The error is thrown by Merge::mergeIndirect in merge.cc:881 (in the source of Ghidra 10.3, the file has seen some changes since, so line numbers have changed compared to current master). I added indop->printDebug(std::cout); just before the error is thrown, compiled decomp_dbg, created an .xml of the function (which I zipped and attached to this comment as well) and loaded that in decomp_dbg. Then I tried decompiling the function again and reproduced the problem. Additionally, the offending INDIRECT operation was printed: 0x00018005b169:d742: s0x00000010(0x00018005b169:d742) = u0x10004f15(0x00018005b169:112cd) [] i0x00018005b169:2aab(free) -> i.e. by one of the PCode operations that is produced by the instruction at address 0x18005b169.
Going back to Ghidra, I noticed that this address is undefined data. This is because when I initially disassembled at address 0x180059a30, Ghidra was unable to resolve the switch table that is at address 0x180059a8e. When manually going through each of the cases of the switch table, and disassembling there, I noticed that all of the branches are decompiled correctly. Even the CALL instruction at 0x18005b169 decompiles correctly when decompiled as part of the (fake) function starting at 0x180059a91.
From reading the relevant code in merge.cc (see below), it seems that the problem is that indop->getIn(0)->getHigh() and outvn->getHigh() overlap at line 879. I am not sure why that happens or what causes this.
https://github.com/NationalSecurityAgency/ghidra/blob/104d9592485c2fb6c7ab5177c71d8d70140a3d03/Ghidra/Features/Decompiler/src/decompile/cpp/merge.cc#L845-L882
Although I could not track down the root cause of this problem, I hope my initial analysis will be useful in the further investigation of this issue.
server.xml.zip

From what I can tell, the first case at 0x180059a91 causes the error - replacing the bytes at 18005e290 and 18005e291 (00 => 01) allows the function to decompile