[Feature Request] Implement Weighted Voting System Instead of Forum

Instead of a traditional question/answer/forum section (https://github.com/nopara73/LongevityWorldCup/issues/33,) the platform could function as a voting system where votes are weighted by the global rank of athletes. This approach encourages easier engagement, generates genuinely valuable insights, and simplifies implementation (after the account system is set up).

In the beginning the most relevant questions might not surface due to lack of activity, so we could have an open source AI prompt that does try to ensure relevance realization. Eg: Give me 7 most important areas to improve longevity. Then for each 7 ask for the 7 most popular strategies and the rank weighted votes would go through those.


Add intro to DG

Codecov Report

Merging #210 (c9747f8) into master (a926507) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #210   +/-   ##
=========================================
  Coverage     63.18%   63.18%
  Complexity      629      629
=========================================
  Files           100      100
  Lines          2325     2325
  Branches        292      292
=========================================
  Hits           1469     1469
  Misses          747      747
  Partials        109      109

Continue to review full report at Codecov.

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

LGTM


Fix CI wamr-ide error

The recent version of the rust toolchain will emit ref types opcodes, need to enable this feature in the iwasm build.
The vector format parsing logic has some errors in the current version. I disabled the check for now and am waiting for further investigation.

The recent version of the rust toolchain will emit ref types opcodes, need to enable this feature in the iwasm build.

Now I see why there is a PR to turn on REF_TYPE by default.


transform_images adds extra dimension to data object

Summary

Statistic maps should be 3D, but when using transform_images to generate a missing map, the outputs are 4D
Additional details

NiMARE version: 0.0.5

What were you trying to do?
create z maps
What did you expect to happen?
3D output
What actually happened?
4D output
Reproducing the bug
run this test:
https://github.com/neurostuff/NiMARE/blob/43d20273f859e3d397547ec2e30c8de9f6fde4fb/nimare/tests/test_transforms.py#L17
and check nib.load(new_z_files[-1]).shape, it will say (10, 10, 10, 1), but I want (10, 10, 10).

I think this is ready for review (if tests pass).
This pull request is necessary for me to finish working on #423, since nilearn's get_cluster_table assumes the statistical map is 3D.


Allow operating on errors instead of logging them

At the moment, there is no option to avoid logging certain errors, which also prevents dependent repositories from operating on these errors in a way that would make more sense to the user-facing side of things. IIUC, it makes sense to use HandleError for all non-user-facing facets, but not so much in cases where this ends up adding to the confusion of the user since the caller had no way to deal with these errors.

A bit of context; at the moment, I'm using reflectors to update stores which are dynamic in nature, in the sense that these can be operated on to add or drop certain resources. This however, leads to reflector.go logging whenever a previously-found resource goes "missing". Is there a possible workaround to this, or maybe something that I'm completely failing to see?

Related: https://github.com/kubernetes/kubernetes/issues/108688.

/remove-lifecycle rotten

/remove-lifecycle stale

/transfer-issue kubernetes


Added Privacy Sandbox references.md

plus linked to front channel logout spec.

@hectormmg @peterzenz can you monitor for feedback and update while I'm out? I think this should be enough to address recent customer feedback.

@EmLauber will do, thanks!

@OwenRichards1

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Architecture check fallback to basic-environment.txt if hardware.txt does not exist

In some supportconfigs hardware.txt does not exist. Suggest adding a fallback file (basic-environment.txt) to check, or adding a flag to manually specify arch when running with -d against a supportconfig.

Done! I now check for basic-environment.txt if hardware.txt does not exist. I also added a "-a" switch to override the architecture.


Removed unnecessary Copyright notices in NOTICE file for bin distribution

Motivation
Based on comments on the 1.19.0-incubating release voting thread (https://lists.apache.org/thread.html/c79ae36fdc1f734337a4f706117be87f4c4c568f87605c59ff4c3a96@<general.incubator.apache.org>), we need to remove unnecessary information from the NOTICE files shipped in the binary pulsar archive.
Eg:

The binary NOTICE file however needs some work:

Notice file lists copyright owners when it doesn’t need to
Notice file list dependancies which while useful shouldn’t be in NOTICE (although that may of    been copied from Netty?)

and

There’s no need to list dependancies in the NOTICE file only a few things are required in NOTICE and it best to kept short. [1][2][3]

retest this please


Implement wildcard in artifacts

I have a target folder in multiple subfolders (using maven modules), and would like this to work, as it is on Gitlab runners :
  artifacts:
    paths:
      - "*/target"

workaround :
  artifacts:
    paths:
      - "module-a/target"
      - "module-b/target"

The main problem here is that alpine images for instance doesn't support

Maybe its time to invoke a little trick I know.
docker volume create ${jobName}-docker-volume
docker create -v ${jobName}-docker-volume:/builds/ ${imageName}
# run scripts
docker run -v ${jobName}-docker-volume:/builds/ --name intercontainer debian bash -c "shopt -s globstar;cp /builds/${artifactPath} /artifacts/"
docker cp intercontainer:/artifacts/ .gitlab-ci-local/artifacts/${jobName}

I would have guessed that cp */target would have worked no matter the image, but you seem way more informed than me on that matter :sweat_smile:

Single asterisk might work in all sorta images, but double globstar certainly won't :smile: But wth, an extra docker run per job with artifacts, we will live :smile:

Sorry @firecow , I forgot to test with emojis in job names, and this does not work :

@bcouetil I'll see if I can add emojies to my safeJobname function... We will be fine 😆😆

@bcouetil https://github.com/firecow/gitlab-ci-local/commit/9e1c27ede3cdc7cf75f1cc413ad573894c6ceb0b Threw it straight into master, hope thats ok.

Tested, working like a charm :tada:


Error while building meteor <IP_ADDRESS> project

=> Errors while adding packages:
While loading package<EMAIL_ADDRESS>error: Command failed:
C:\Users\ASUS\AppData\Local.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\bin\npm.cmd
rebuild --update-binary

@jkd65 It's a subtle issue, I remember I delete module folder and reinstall whole dependencies, and do meteor reset as well.


Make Food Ordering Website Responsive

Issue Type:

[X] Bug Report
[ ] Feature Request
[ ] Documentaion

Tasks
[1] Fix the nav bar

[2] Size this section properly

[3] Improve the UI of the footer(You can change it completely too)

Hi there , i would love to work on this issue. Can u assign it to me under GSSOC22.

I want to work on this issue, because responsive is one of my thing so, can you assign me this issue?

Assigned on the basis of FCFS

@juberiya1ajaz start working on it


Add/expose go-cam reasoning/validation service

Input is an OWL model representing a GO-CAM (expressed using the json format preferred by the Noctua stack)
Output

boolean is_valid  (check OWL consistency)
list of errors if any (nodes that = OWL:Nothing
Any explanations of the errors that can be provided
Inferred types (all the way up to root) for each node in the model

@kltm @tmushayahama @lpalbou @cmungall

assign to @goodb

@kltm to help set up testing environment (call the service from node libraries used by actual client code (probably using command line interface) ).  Provide specifications for request/response structure.

@kltm @balhoff I think I must have missed something when we discussed this.  Why can't @tmushayahama call the existing reasoning service from the form?  It seems like that would be sufficient for his needs - with the addition of returning the root type (MF, BP, CC, etc.) for each individual.

One of the requests we've had from curators is to provide some explanation of what is invalid in a model when they use the reasoner and the screen turns red.  Currently, there is little, if anything to provide hints.  Could this service be used to help with this?

Of course, anyone can use the inference explanations view but this is probably really appropriate for ontology editors who have undergone OWL training.
I believe we can iterate over this, adding server side functionality that will look at patterns in the explanation and summarizing these in a curator friendly way. As an example, as a first pass the server would look at the explanation axioms and see if one looks like a TC. If so, it can inject an explanation text into the payload that says "it looks like TC   was violated somewhere".
This same server-side logic could potentially be reused e.g. in gaferencer (when processing non-GO-CAM submitted GAFs)

I think the UI for explaining errors (or correct inferences) could be significantly improved without any immediate updates to the server side.  One of the problems with the explanation view is searching through it to find the which nodes are inferred to be OWL:Nothing.  Reading about why that inference happened is a second step.  I suggest:

Have the UI visually highlight any nodes with type OWL:Nothing
For any inferred type (including Nothing), link directly to the explanation for that particular inference (isolated from the rest of the explanations).

The first could be done now.  The second may require some minor adjustments to the way the explanation data is sent back, but not much.
From that point, we could iterate on the text of the explanations.

@cmungall UI things like that would not be a lot of work, but it would be enough to slow things down, even if other things were dropped and it was focused on. That said, simple things like highlighting and color changes are approachable.

@kltm  if you want to define the inputs and expected outputs for the service as simple blobs of json that would probably be sufficient to get the core of the service working, though of course running more realistic tests directly from the client API would be best.  I have a test built now that uses the Java/gson class that @cmungall wrote to generate requests but it would be better to be working from a json structure that was already understood by the client to start out with.
That being said.
Given the bandwidth limitations we are operating under I think being clear about why or why not this is needed right now, as I asked about in the Noctua chat room, is very important.  Right now I see interesting use cases for a reasoning service that was to some extent independent of the rest of the Noctua/Minerva stack but I don't see any clear case for why this is crucial in the @tmushayahama form-editor use case that initiated the idea.  If he made use of the existing service it already provides the core information he needs - and if it needs to extended, for example by appending the root inferred classes (MF, BP, etc.) to the output, that would be a straightforward addition.
In fact, if he started developing with this new service, which operates quite differently from the rest of the stack (whole models versus atomic actions on models), it could actually lead to greater splintering and more wasted resources moving forward.

@goodb Sorry, but I thought is might be good to retread some of the gitter comments before they get lost in the timeline, just to give some context.
The first use case--the one that we may have outlined more often--is checking a model after an operation has been performed. This would (eventually) include structural checks, GORULEs, etc., that could be run at a decent speed on every edit, with the responce being send back as part of the standard edit packet.
The second use case is for proactively preventing curators from entering inputs that should be illegal for some reason, before they attempt to edit a model. This is the use case that was outlined for @tmushayahama , but could be applied elsewhere. One would essentially have a model (or build a simple model), make changes to it, and ask if the resulting model would be okay. The temporary model (or model bits) would never be saved or made available to others. The checks for this and the first use case would probably have overlap and differences.
(Apologies for retreading that, I just wanted to make sure that future readers don't get lost in the chain of thought.)
If I'm following you (and I may not be), if we had a separate reasoning service, it would be serving very much the same information as the after-the-fact system that would need to be in minerva to supply checks anyways. But there are other ways forward; I guess the general architectures could be:

all reasoning/validation in general-purpose service, no reasoning/validation in after-the-fact minerva
no general-purpose service, all reasoning/validation in new minerva route and after-the-fact minerva

what we have now is this, minus the new route

a mix of the first two, where we have a general-purpose service for some things and minerva provides some others

If there is interest in providing a public general-purpose service (good!), that would be a viable way forward. I would guess that it would probably share a lot of the same code (if we had both), but incur some additional overhead (bad!). I would be interested in the scope of what additional things may be offered to the public, but as I am not a consumer of such services, I can't really weigh in on how much marginal utility there might be in making something like that available to the community, versus continuing on the current path.

Though I have long bothered @balhoff about making a public general purpose reasoning service for the GO (and its brethren) I don't think it is the right time to do it.  I think that right now we have an acute need for iterative progress on the Noctua front end (which IMO should be considered to directly include the form input editor, the table-based review system and anything else that is built for curators working on GO-CAMs).  After coming to a better understanding of how Noctua/Minerva works, I think the best way that server-side development can help move Noctua forward right now is to develop incremental expansions to the existing service (as there is really only one Minerva service).  Such expansions should be driven very specifically by clearly articulated needs in the client code driving the UI.
I think it would be helpful if @kltm or @tmushayahama could define, with sample inputs and outputs, what is needed by the Noctua client (broadly speaking) that is not currently accessible from an existing call to Minerva with the Reasoner on.  This is not clear to me from your comment above.

@goodb I fully agree. I think that at this point in time it's probably better to evolve what we have and revisit (and possibly split out) when we have worked with it a bit more.
I'll hopefully get back to the client serializer we need tomorrow.

Also see https://github.com/geneontology/noctua/issues/567

My understanding is that as we are no longer implementing a new endpoint for this use case, instead evolving the response of the current system, this can be mothballed for now.


Fix race between addon pods and local-cluster

On bring up, addon pod on hub looks for local-cluster to fetch API URL. Since addon pod comes up during cluster creation, it is possible that local-cluster isn't available yet. This can result in hubHost to be empty and breaks backup/restore.
Signed-off-by: Vishal Thapar<EMAIL_ADDRESS>

/cc @skitt @tpantelis

/lgtm

/approve


Misc doc changes

Besides other documentation changes, this commit ensures the generated
HTML doc for HexDocs.pm will become the source of truth for this Elixir
library and leverage on latest features of ExDoc.

Many thanks for your efforts. I will review the PR as soon as possible.


Style Configurator.

The purpose of this new feature is to modernize the SQL editor, this being the first step.
In the styles settings you can change:

Font name.
Font size.
Background color.
Foreground color.
Bold font.
Italics.
underline
Font Case

4 languages were defined:

Global style.
DIFF.
SQL.
Search results.

Initially only the Global Style and SQL are being used.
Style Cofigurator.

Some ideas are taken from the Notepad++ project and include 23 predefined styles that were taken from the same project and are included in the xml-styles folder. Please check if there are no license issues.
Dark Style.

Hello Kitty Style.

Deep Black Style.

Khak Style.

Ruby Blue Style.

Finally it was necessary to change to version 3.2 of wxWidgets and it was tested on Win7, Win10, Win11 and Debian 11.
With this first part we want to solve the following issues:

#25
#189
#231

We await your feedback for improvements and corrections.
./jo
P.S. The initial implementatation of foldng are include.

@Jdochoa just for info stylers.xml license is GPL3 ?
https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/LICENSE

@Jdochoa just for info stylers.xml license is GPL3 ? https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/LICENSE

I think so.


assigning this does not work in all environments

Hi,
the code:
var object = typeof exports != 'undefined' ? exports : this; // #8: web workers
  var chars = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=';

does rely on the fact, that this is always referring to the global scope; but when somehow base64 is evaluated in other contexts, this can be undefined and thus the subsequent assigning of btoa is failing, because object itself is then undefined.
When using the grunt usemin task for production, we get this error in the production build. There is no easy way around it; maybe one could check simply, whether atob btoa itself is a function, when exports is undefined.

This is the most reliable way I've found to get the global object: https://gist.github.com/michaelficarra/791f9742ca95318278a63f82c536e564.

Personally I would not even bother, either polyfill atob / btoa for a "global" windowor attach them to the global exports. Of course, when someone abused window or exports you are out of luck, but some crimes deserve to be punished :)

We had
typeof exports != 'undefined' ? exports : window

initially, but switched to
typeof exports != 'undefined' ? exports : this

in #8 to support web workers.

when somehow base64 is evaluated in other contexts, this can be undefined

Perhaps an error in your build pipeline is resulting in this module being run in strict mode. That's one explanation for this being undefined:
> (function() { return this === window; }())
true

> (function() { 'use strict'; return this === undefined; }())
true

@davidchambers If you don't want to use my heavy weight approach, self should work in all "browser" contexts.

@davidchambers Still if the specific use case is about supporting web workers, there should be a specific way to get hold of their global object.
The "error in my build pipeline" is using the stock grunt usemin plugin, if I were to use the same library with WebPack it would be the same result - it also enforces strict mode.
I would not write code, that relies on being run in non-strict mode, so yeah basically this is why the error comes up.

Still if the specific use case is about supporting web workers, there should be a specific way to get hold of their global object.

As Michael mentioned, replacing this with self should do the trick. I'll make this change.

The "error in my build pipeline" is using the stock grunt usemin plugin, if I were to use the same library with WebPack it would be the same result - it also enforces strict mode.

I didn't realize these tools are only compatible with modules which work correctly in strict mode. This strikes me as an unfortunate limitation.
Making the module work correctly in both modes seems ideal.

Every serious project I have been working on is using strict mode and for good reasons.  Code linting / hinting fails in our projects, when strict mode is not used.
Every major JS style guide, recommends using strict mode.
I do not see a use case for serious JS projects without using strict mode - well at least not for me and my company. Not using strict mode allows all kind of crazy stuff - this referring to the global object is only the tip of the ice berg.

I absolutely agree that we should opt in to strict mode for new projects.
My point is that tools should not dictate what is and isn't acceptable JavaScript code unless there's something significant to be gained by doing so (and perhaps there is).


Correction for raw affiliation 3rd Floor, West Tower, 555 West 12th Avenue, Vancouver, BC, Canada V5Z 3X7

Correction needed for raw affiliation 3rd Floor, West Tower, 555 West 12th Avenue, Vancouver, BC, Canada V5Z 3X7
raw_affiliation_name: 3rd Floor, West Tower, 555 West 12th Avenue, Vancouver, BC, Canada V5Z 3X7
new_rors:
previous_rors: 028d12s45
works_examples: W2008890209
contact: 812e58b185f1e9aa1ab87aba375c8dd7:0bb24556 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


BUG: Setting Size = ImageSize.Auto does not render in JSON object

"size": "auto" is being dropped when looking at the JSON that the C# classes create and it breaks the rendering of my card when using ImageRenderer or VS Code Viewer (for example).
REPRO:  Construct the card in C# which has an image with Size = ImageSize.Large and look at the JSON that you get
ACTUAL: size is dropped from the JSON
EXPECTED:  "size": "auto" should be in my Json just like "size": "large" is there when I use large.
                                new Image()
                                    {
                                        Size = ImageSize.Large,
                                        Url = $"http://....",
                                    }

Viewing JSON with...
string json = JsonConvert.SerializeObject(card, Formatting.None);
Rendering with...

            ImageRenderer renderer = new ImageRenderer(new HostConfig(), String.Empty);
            Stream stream = await renderer.RenderAdaptiveCardAsync(card, 600);

I would have added the fix but didn't see where this is happening on my first dig.  I'm guessing you figured it wasn't necessary because maybe 'auto' is the default but someone else isn't making the same assumption.

I can confirm that image render works correctly in the current master build but will let you close the bug in case it jogs your brain from something related.
I didn't see the change here that resolved it but I could be wrong.
https://github.com/Microsoft/AdaptiveCards/pull/469

This should be fixed in the latest .NET packages


Diagnostics is wrong when the same unimplemented step is used twice in a specification

Expected behavior
Diagnostics should be displayed correctly
Actual behavior
Undefined step is displayed the first time. The second occurrence is marked as defined
Steps to replicate

Create a gauge-js project
Add an unimplemented step in the specification to the 1st scenario
Add the same unimplemented step in the 2nd scenario.

The second occurrence of the unimplemented step is marked as implemented

Version
Gauge version: 0.9.9.nightly-2018-05-11
Commit Hash: fcb9e9d

Plugins
-------
js (2.3.1.nightly-2018-05-08)

Should be available in gauge-vscode nightly >= 15/05/18

Should be available in gauge nightly >= 15/05/18


matplotlib to show is not convenient for some linux platform

when pip install,some error appear,such as:
Collecting matplotlib>=2.0.0 (from scikit-image>=0.11.0->imgaug==0.2.6)
Downloading http://<IP_ADDRESS>/pypi/web/packages/ec/06/def4fb2620cbe671ba0cb6462cbd8653fbffa4acd87d6d572659e7c71c13/matplotlib-3.0.0.tar.gz (36.3MB)
100% |################################| 36.3MB 101.1MB/s
Complete output from command python setup.py egg_info:
Matplotlib 3.0+ does not support Python 2.x, 3.0, 3.1, 3.2, 3.3, or 3.4.
Beginning with Matplotlib 3.0, Python 3.5 and above is required.

This may be due to an out of date pip.

Make sure you have pip >= 9.0.1.

The latest version in master now uses cv2 to show images.
But I don't think this will change anything as matplotlib is required for some other stuff. Is there any reason to not just manually install an older version of matplotlib if the newest one is not compatible with your configuration any more?


⚠ Bofrost.lu has degraded performance

In 85bc486, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1630 ms

Resolved: Bofrost.lu performance has improved in f2a8b64 after 21 minutes.


refactor(CLI): use go-native k8s client for some CLI commands (4 of 6)

Having introduced a new go-native client and curated packages bundle client,
those constructs now replace the fork/exec based docker & kubectl executions
used in various curated packages CLI commands.
Not all commands curated packages CLI commands have been migrated at this
time, due mainly to lack of time.
Depends on #3603

Closing this PR. It's stale at this point.


[Device Support Request] THIRDREALITY Zigbee Temperature and Humidity Sensor

Is your feature request related to a problem? Please describe.
These cheap Third Reality Temperature and Humidity sensors pair nicely with ZHA except they expose no entities to Home Assistant
Describe the solution you'd like
I should be able to get relative humidity and temperature from these guys.

Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4659, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0302",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0402",
        "0x0405"
      ],
      "out_clusters": [
        "0x0019"
      ]
    }
  },
  "manufacturer": "Third Reality, Inc",
  "model": "3RTHS24BZ",
  "class": "zigpy.device.Device"
}

Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.10.4",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.5",
    "docker": true,
    "arch": "x86_64",
    "timezone": "America/Chicago",
    "os_name": "Linux",
    "os_version": "5.15.72",
    "supervisor": "2022.10.0",
    "host_os": "Home Assistant OS 9.2",
    "docker_version": "20.10.17",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "holidays": {
      "version": "1.8.0",
      "requirements": [
        "python-dateutil>=2.8.2",
        "holidays>=0.14.2"
      ]
    },
    "garbage_collection": {
      "version": "4.8.3",
      "requirements": [
        "python-dateutil>=2.8.2"
      ]
    },
    "pirateweather": {
      "version": "0.1.0",
      "requirements": [
        "python-forecastio==1.4.0"
      ]
    },
    "ui_lovelace_minimalist": {
      "version": "v1.1.0",
      "requirements": [
        "aiofiles==0.8.0",
        "aiogithubapi>=22.2.4"
      ]
    },
    "google_home": {
      "version": "1.9.15",
      "requirements": [
        "glocaltokens==0.6.8"
      ]
    },
    "triones": {
      "version": "0.0.1",
      "requirements": []
    },
    "tuya_v2": {
      "version": "1.5.0",
      "requirements": [
        "tuya-iot-py-sdk==0.4.1"
      ]
    },
    "spotcast": {
      "version": "v3.6.30",
      "requirements": [
        "spotify_token==1.0.0"
      ]
    },
    "androidtv_custom": {
      "version": "0.1.1",
      "requirements": [
        "adb-shell[async]==0.4.2",
        "androidtv[async]==0.0.67",
        "pure-python-adb[async]==0.3.0.dev0"
      ]
    },
    "localtuya": {
      "version": "4.1.0",
      "requirements": []
    },
    "nodered": {
      "version": "1.0.9",
      "requirements": []
    },
    "hacs": {
      "version": "1.28.0",
      "requirements": [
        "aiogithubapi>=22.2.4"
      ]
    },
    "adaptive_lighting": {
      "version": "1.1.0",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.34.2",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.82",
      "zigpy-deconz==0.19.0",
      "zigpy==0.51.3",
      "zigpy-xbee==0.16.2",
      "zigpy-zigate==0.10.2",
      "zigpy-znp==0.9.1"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      }
    ],
    "dependencies": [
      "file_upload"
    ],
    "after_dependencies": [
      "onboarding",
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 42476,
    "manufacturer": "Third Reality, Inc",
    "model": "3RTHS24BZ",
    "name": "Third Reality, Inc 3RTHS24BZ",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4659,
    "power_source": "Battery or Unknown",
    "lqi": 255,
    "rssi": -65,
    "last_seen": "2022-10-17T13:03:02",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4659, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": 260,
          "device_type": "0x0302",
          "in_clusters": [
            "0x0000",
            "0x0001",
            "0x0402",
            "0x0405"
          ],
          "out_clusters": [
            "0x0019"
          ]
        }
      }
    },
    "active_coordinator": false,
    "entities": [],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "TEMPERATURE_SENSOR"
      }
    ],
    "user_given_name": "Master Bedroom Thermostat",
    "device_reg_id": "b0aa368e61026a12cf2e139830732174",
    "area_id": "bedroom",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "TEMPERATURE_SENSOR",
          "id": 770
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "Third Reality, Inc"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "3RTHS24BZ"
              },
              "0x4000": {
                "attribute_name": "sw_build_id",
                "value": "1.00.20"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 30
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 200
              }
            },
            "unsupported_attributes": {}
          },
          "0x0402": {
            "endpoint_attribute": "temperature",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": 1630
              }
            },
            "unsupported_attributes": {}
          },
          "0x0405": {
            "endpoint_attribute": "humidity",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": 5100
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Additional context

That seems like a very straight zigbee device.
Even in Z2M don't seems to have too much to quirk (just battery_voltage?):

https://github.com/Koenkk/zigbee-herdsman-converters/blob/328e2a362e1f67cfc13dc91e1d939e2c5edd75a1/devices/third_reality.js#L139-L147

It can be a pairing issue?
Battery powered devices must be kept awake during the pairing procedure.
To do this, while the pairing lasts, you have to briefly press the button to keep the device awake.

The data is there to expose entities. Are you sure there are no entities? May I have a screenshot of the entire device page?

Pairing log: https://dpaste.org/Ovq4E

Try unbinding all cluster (from device card > manage zigbee device) both to device and groups and bound the temperature cluster to the coordinator and see if its start reporting.

I just got the same device and I am getting Temp and the Battery % in but not the Humidity.

{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2022.10.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.5",
"docker": true,
"arch": "x86_64",
"timezone": "America/New_York",
"os_name": "Linux",
"os_version": "5.15.72",
"supervisor": "2022.10.0",
"host_os": "Home Assistant OS 9.2",
"docker_version": "20.10.17",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"bhyve": {
"version": "3.0.0",
"requirements": []
},
"localtuya": {
"version": "4.1.1",
"requirements": []
},
"nfl": {
"version": "0.1",
"requirements": [
"arrow"
]
},
"anniversaries": {
"version": "4.5.0",
"requirements": [
"python-dateutil>=2.8.1",
"integrationhelper>=0.2.2",
"voluptuous>=0.12.1"
]
},
"deebot": {
"version": "1.4.1",
"requirements": [
"deebot-client==1.5.1",
"numpy>=1.21.2"
]
},
"fullykiosk": {
"version": "1.1.0",
"requirements": [
"python-fullykiosk==0.0.11"
]
},
"google_home": {
"version": "1.9.15",
"requirements": [
"glocaltokens==0.6.8"
]
},
"alexa_media": {
"version": "4.1.2",
"requirements": [
"alexapy==1.26.3",
"packaging>=20.3",
"wrapt>=1.12.1"
]
},
"eufy_security": {
"version": "2.8.0",
"requirements": [
"websocket-client==1.1.0"
]
},
"mail_and_packages": {
"version": "0.3.4-2",
"requirements": [
"imageio>=2.9.0",
"python-resize-image>=1.1.19"
]
},
"govee": {
"version": "0.2.2",
"requirements": [
"govee-api-laggat==0.2.2",
"dacite==1.6.0"
]
},
"fordpass": {
"version": "0.1.37",
"requirements": []
},
"nest_protect": {
"version": "0.3.8",
"requirements": []
},
"watchman": {
"version": "0.5.1",
"requirements": [
"prettytable==3.0.0"
]
},
"hacs": {
"version": "1.28.2",
"requirements": [
"aiogithubapi>=22.2.4"
]
},
"fitbit": {
"version": "v1.1.1",
"requirements": [
"fitbit==0.3.1"
]
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/zha",
"requirements": [
"bellows==0.34.2",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.82",
"zigpy-deconz==0.19.0",
"zigpy==0.51.3",
"zigpy-xbee==0.16.2",
"zigpy-zigate==0.10.2",
"zigpy-znp==0.9.1"
],
"usb": [
{
"vid": "10C4",
"pid": "EA60",
"description": "2652",
"known_devices": [
"slae.sh cc2652rb stick"
]
},
{
"vid": "1A86",
"pid": "55D4",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus v2"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "zigstar",
"known_devices": [
"ZigStar Coordinators"
]
},
{
"vid": "1CF1",
"pid": "0030",
"description": "conbee",
"known_devices": [
"Conbee II"
]
},
{
"vid": "10C4",
"pid": "8A2A",
"description": "zigbee",
"known_devices": [
"Nortek HUSBZB-1"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "zigate",
"known_devices": [
"ZiGate+"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "zigate",
"known_devices": [
"ZiGate"
]
},
{
"vid": "10C4",
"pid": "8B34",
"description": "bv 2010/10",
"known_devices": [
"Bitron Video AV2010/10"
]
}
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly"
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "zigate"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "zigstar"
}
],
"dependencies": [
"file_upload"
],
"after_dependencies": [
"onboarding",
"usb",
"zeroconf"
],
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp"
],
"is_built_in": true
},
"data": {
"ieee": "REDACTED",
"nwk": 59695,
"manufacturer": "Third Reality, Inc",
"model": "3RTHS24BZ",
"name": "Third Reality, Inc 3RTHS24BZ",
"quirk_applied": false,
"quirk_class": "zigpy.device.Device",
"manufacturer_code": 4659,
"power_source": "Battery or Unknown",
"lqi": 112,
"rssi": -72,
"last_seen": "2022-10-20T20:01:41",
"available": true,
"device_type": "EndDevice",
"signature": {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4659, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0302",
"in_clusters": [
"0x0000",
"0x0001",
"0x0402",
"0x0405"
],
"out_clusters": [
"0x0019"
]
}
}
},
"active_coordinator": false,
"entities": [
{
"entity_id": "sensor.office_temp_battery",
"name": "Third Reality, Inc 3RTHS24BZ"
},
{
"entity_id": "sensor.office_temp_temperature",
"name": "Third Reality, Inc 3RTHS24BZ"
}
],
"neighbors": [],
"endpoint_names": [
{
"name": "TEMPERATURE_SENSOR"
}
],
"user_given_name": "Office Temp",
"device_reg_id": "dbe4fb15c5d12990e65d13378de58dbf",
"area_id": "office",
"cluster_details": {
"1": {
"device_type": {
"name": "TEMPERATURE_SENSOR",
"id": 770
},
"profile_id": 260,
"in_clusters": {
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {
"0x0004": {
"attribute_name": "manufacturer",
"value": "Third Reality, Inc"
},
"0x0005": {
"attribute_name": "model",
"value": "3RTHS24BZ"
},
"0x4000": {
"attribute_name": "sw_build_id",
"value": "1.00.20"
}
},
"unsupported_attributes": {}
},
"0x0001": {
"endpoint_attribute": "power",
"attributes": {
"0x0020": {
"attribute_name": "battery_voltage",
"value": 32
},
"0x0021": {
"attribute_name": "battery_percentage_remaining",
"value": 200
}
},
"unsupported_attributes": {
"0x0020": {
"attribute_name": "battery_voltage"
},
"0x0021": {
"attribute_name": "battery_percentage_remaining"
},
"0x0031": {
"attribute_name": "battery_size"
},
"0x0033": {
"attribute_name": "battery_quantity"
}
}
},
"0x0402": {
"endpoint_attribute": "temperature",
"attributes": {
"0x0000": {
"attribute_name": "measured_value",
"value": 2630
}
},
"unsupported_attributes": {
"0x0000": {
"attribute_name": "measured_value"
}
}
},
"0x0405": {
"endpoint_attribute": "humidity",
"attributes": {
"0x0000": {
"attribute_name": "measured_value",
"value": 3600
}
},
"unsupported_attributes": {
"0x0000": {
"attribute_name": "measured_value"
}
}
}
},
"out_clusters": {
"0x0019": {
"endpoint_attribute": "ota",
"attributes": {},
"unsupported_attributes": {}
}
}
}
}
}
}

These are working for me now. If you guys want to leave this open for discussion thats fine otherwise close it.

Small update, I have since purchased 2 more and the new 2 are showing the same thing as before, no home assistant entities.  The previous one worked after a day but its been 24 hours and its not working.

Try unbinding all cluster (from device card > manage zigbee device) both to device and groups and bound the temperature cluster to the coordinator and see if its start reporting.

Could you expand on this?

I did find this in the logs. Is it concerning that the measure_value attributes also show up in the unsupported_attributes
"cluster_details": {
      "1": {
        "device_type": {
          "name": "TEMPERATURE_SENSOR",
          "id": 770
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "Third Reality, Inc"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "3RTHS24BZ"
              },
              "0x4000": {
                "attribute_name": "sw_build_id",
                "value": "1.00.20"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 31
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 200
              }
            },
            "unsupported_attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage"
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining"
              },
              "0x0033": {
                "attribute_name": "battery_quantity"
              },
              "0x0031": {
                "attribute_name": "battery_size"
              }
            }
          },
          "0x0402": {
            "endpoint_attribute": "temperature",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": 2680
              }
            },
            "unsupported_attributes": {
              "0x0000": {
                "attribute_name": "measured_value"
              }
            }
          },
          "0x0405": {
            "endpoint_attribute": "humidity",
            "attributes": {
              "0x0000": {
                "attribute_name": "measured_value",
                "value": 3900
              }
            },
            "unsupported_attributes": {
              "0x0000": {
                "attribute_name": "measured_value"
              }
            }
          }
        },
        "out_clusters": {
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }

This device needs a firmware update. We have let them know

A related problem has been found and is working hard to solve it, we will fix it as soon as possible!

Not sure you are correct. We set reporting parameters for the amount of change needed to trigger a report. This is standard ZCL and has not changed in ZHA.

@xudo-github The measured_value attribute of both the Temperature and Humidity clusters being readable and reportable is aligned with the ZCL R8 specification:

This behavior is only introduced in latest ZHA, the old version actually donot need this.

ZHA has never polled Zigbee 3.0 temperature sensors. Can you clarify which version you're referring to?

You are right, it is a bug in 3R side. Somehow the previous version of ZHA tolerant it, but the latest version is not happy with this. The fixed firmware worked well with multi-round of testing.

This is the missing report capture

And yes the fix is actually made the values reportable which aligns with the spec

Yep so straight up firmware issue. Nothing has changed with ZHA with regards to cluster binding or configuration and the sensor classes for ZHA haven’t been touched in forever. The history is all there. Feel free to look.
If you’re positive that this worked at any point I’m going to guess it was a fluke as you have proven that the firmware was not specification compliant 🤷🏻♂
Glad you have it sorted out so that it will work now for your customers.

@xudo-github please also ensure that the binding table is large enough to accommodate binding the 3 clusters that support attribute reporting.

OTA updates for ThirdReality devices are now natively available in Home Assistant (https://github.com/zigpy/zigpy/pull/1096).
They can be activated by adding this to the configuration.yaml:
zha:
  zigpy_config:
    ota:
      thirdreality_provider: true

An "update notify" command also needs to be send to the device.
Are all bugs fixed with the latest firmware available now?

Yes, we have all latest firmware updates uploaded.
On Tue, Jan 3, 2023 at 9:12 PM TheJulianJES @.***>
wrote:

OTA updates for ThirdReality devices are now natively available in Home
Assistant (zigpy/zigpy#1096 https://github.com/zigpy/zigpy/pull/1096).
They can be activated by adding this to the configuration.yaml:
zha:
zigpy_config:
ota:
thirdreality_provider: true
An "update notify" command also needs to be send to the device.
Are all bugs fixed with the latest firmware available now?
—
Reply to this email directly, view it on GitHub
https://github.com/zigpy/zha-device-handlers/issues/1835#issuecomment-1370497178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4BKI2WUFPXV4DEO32HLPWDWQUBETANCNFSM6AAAAAARHKCULA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Current tag 0.01 is not working, create new tag for current master head

@simonster @ihnorton I would like to use the DICOM Package but the current tag 0.01 is not working. Could you create a new tag of the current master head which is working fine?

New tag should be, and a recent version can be obtained via Pkg.update().
Better late than never. ;)


[spaceship][match] fix and improve team selection flow with Spaceship::ConnectAPI client

Motivation and Context
Fixes #17153
Fixes #17157
Fixes #17155
Description

match was not passing in team id and team name through environment variables to select team so need to manually pass
Improve Spaceship::ConnectAPI.login so always call select_team (even if no team id or team name passed in)

This is needed to allow manual selecting of team through the UI if nothing passed in
login still takes parameters for team id and team name or environment variables to prevent UI login

Spaceship::ConnectAPI.select_team is called specifically in actions/tools because login handles it

Testing Steps
Update Gemfile and run bundle update fastlane, bundle update, or bundle install
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-match-fix-team-select-and-improve-spaceship-connect-team-select"

@joshdholtz still getting this error:
bundler: failed to load command: fastlane (/usr/local/lib/ruby/gems/2.7.0/bin/fastlane)
NoMethodError: [!] undefined method `team_id' for #<Spaceship::ConnectAPI::Client:0x00007f7eeb7107e8>
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/spaceship_ensure.rb:28:in `team_id'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/storage/google_cloud_storage.rb:110:in `currently_used_team_id'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/storage/google_cloud_storage.rb:119:in `prefixed_working_directory'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/runner.rb:141:in `prefixed_working_directory'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/runner.rb:155:in `fetch_certificate'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/runner.rb:94:in `run'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/commands_generator.rb:68:in `block (3 levels) in run'
  /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
  /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/commands_generator.rb:187:in `run'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/match/lib/match/commands_generator.rb:25:in `start'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
  /usr/local/lib/ruby/gems/2.7.0/bundler/gems/fastlane-e6afe5f93751/bin/fastlane:23:in `<top (required)>'
  /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in `load'
  /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in `<top (required)>'

Locally fixed this with this hack:
    def team_id
      return ENV['FASTLANE_TEAM_ID']
    end

@nkt Thanks for reporting this! I will find a fix right away and let you know when new thing is pushed ❤

@joshdholtz yes, it works! :+1:

@nkt Thank you so much for testing! Huge help 😊


[ HOTFIX #22 ] Blacklist syncing issues

Added fix to syncing issues as pointed out by @dylandamsma in #22
Sets default block explorer for initial extension install to etherscan.io
Enabled blacklist domain detection by default

New tag: v1.3.5


AzureCLI input connectedServiceNameARM references service connection $(azureServiceConnection) which could not be found

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureCLI@2
Environment

Azure DevOps Services

Account name: asset-toolbox
Team project name: container-app
Build definition name/build number: container-app-iac

Agent - Hosted (ubuntu-latest)

Issue Description
I am using AzureCLI@2 task to run a bicep script
I configured the task to use a variable with the name of my service connection
- task: AzureCLI@2
  displayName: Azure Bicep
  inputs:
    azureSubscription: $(azureServiceConnection)
    scriptType: bash
    scriptLocation: inlineScript
    inlineScript: |
      az group create --name $(azureResourceGroup) --location $(azureLocation) --debug
      az deployment group create --resource-group $(azureResourceGroup) --template-file main.bicep --parameters acrName=$(azureContainerRegistry) clusterName=$(azureKubernetesName) sqlserverName=$(azureSqlServerName) kvName=$(azureKeyVaultName) loadTestName=$(azureLoadTestName) --debug

So I created a group variable containing the azureServiceConnection variable, but when I run the pipeline the task cannot interpret the variable's value

If I create a global variable $(azureServiceConnection) inside my yml pipeline, everything works.
The problem is when I try to use variable group
My variable group is configured without restrictions, any pipeline can access
My service connection has pipeline permission confured

Are you using the same pipeline for QA and PRD?  If so, how are you selecting which environment the pipeline runs against?

Then define which variable group you need per Stage, like so:
- stage: Stage_Deploy_DEV
  displayName: Stage Deploy DEV
  dependsOn: Stage_Build
  variables:
  - group: varGroupDev
  jobs:
  - deployment: Job_Deploy_DEV
    displayName: Job Deploy DEV
    pool:
      vmImage: $(vmImageName)
    environment: 'aks-containerapp-demo-dev.default'
    strategy:
      runOnce:
        deploy:
          steps:

- stage: Stage_Deploy_PRD
  displayName: Stage Deploy PRD
  dependsOn: Stage_Deploy_DEV
  variables:
  - group: varGroupPrd
  jobs:
  - deployment: Job_Deploy_PRD
    displayName: Job Deploy PRD
    pool:
      vmImage: $(vmImageName)
    environment: 'aks-containerapp-demo-prd.default'
    strategy:
      runOnce:
        deploy:
          steps:

Exactly! I made this setting but it doesn't work, results in the error in the print above

Yeah, if your variables groups have a variable named azureServiceConnection then this should work.  Otherwise, yeah, might be a bug possibly.

I am able to reproduce the same behavior in AzureFunctionApp@1 task also. I believe the issue exists in all places where the input type is connectedService:AzureRM.
But when variable is defined at pipeline level (direct or through template), this works without any issue. Issue is only when variable is defined at stage or job level (direct or through template.

Source
It also answers another common issue: why can't I use [variables](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops) to resolve service connection / environment names? Resources are authorized before a stage can start running, so stage- and job-level variables aren't available. Pipeline-level variables can be used, but only those explicitly included in the pipeline. Variable groups are themselves a resource subject to authorization, so their data is likewise not available when checking resource authorization.

I am also facing same issue. Anyone found any solution please?


add: base64url support

Using string replaceAll since base64 is external base64-js.
Dependency does not yet support base64url beatgammit/base64-js#53

Any news for this ? Please.

same issue, any news?

Thanks for coding this, @jrschumacher! Using it for a fork

I need base64url encoding support for my project, can we review and merge this ASAP?

It's probably not going to happen if it's been this long. Just use my branch or just wrap the base64 function in a string replace.

Hopefully this is merged some day.  It seems to work well
npm install feross/buffer#pull/314/head

Hopefully this is merged some day. It seems to work well
npm install feross/buffer#pull/314/head

@dcousens I removed trailing spaces on line 955 of buffer.js

@dcousens still interested in taking this?

I rebased with the master branch and removed my lint scripts from the package.json to reduce conflicts.

Thanks @jrschumacher, I'm happy to take this from here next I can

Would it be possible to merge and release this first since the other PR seems stuck for a long time now?


NoBid version 1.3.4

🏷 Type of documentation

[ ] new bid adapter
[x] update analytics adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[ ] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[ ] For new adapters check submitting your adapter docs

Hello,
Can someone please review this PR? It's related to this PR https://github.com/prebid/Prebid.js/pull/11420 and these 2 work together.
Thank you


DNS leak fix in server_config.txt

Added fix to prevent DNS leak on Windows systems. If the OS on the client side is Linux, this option is ignored by the client.

Seems good to me.
Tough some care with this option might be required.

--block-outside-dns
Block DNS servers on other network adapters to prevent DNS leaks. This option prevents any application from accessing TCP or UDP port 53 except one inside the tunnel. It uses Windows Filtering Platform (WFP) and works on Windows Vista or later.
This option is considered unknown on non-Windows platforms and unsupported on Windows XP, resulting in fatal error. You may want to use --setenv opt or --ignore-unknown-option (not suitable for Windows XP) to ignore said error. Note that pushing unknown options from server does not trigger fatal errors.

Looks good to me, thanks @Cyb0rk!


add test for exporter metrics

/lgtm

ok static code passing @ramessesii2 @enarha and I believe extra space is accounted for @enarha

/lgtm

tests are green
given @ramessesii2 and @enarha prior lgtm's I'm merging


audit warnings because of a dependency on an outdated mem

Getting audit warnings because of a dependency on an outdated mem, via an outdated deppcheck.
Kinda ironic, isn't it?

fixed in the 5.9 series


Fix driver caching

Two reports of outdated drivers when they shouldn't be.
Check that the cache is actually working

A theory I have is that this library does not work in the same way as the webdrivers ruby gem does and that people which use both are running into this issue.


Setting up es-git in a dev environment

Hey, It's me again. Sorry if I'm flooding the issues here.
I was planning on contributing to this package by rewriting this creatonix package in Typescript/EcmaScript.
https://github.com/creationix/js-github
The main goal is to have a working git client in the browser, that can fetch from and commit to a github repo, that does not depend on a github proxy running at the server.
So I cloned this repository, and got everything to work, but all the module identifiers point to the npm packages.  I'm guessing that's not how it has been developed, so I thought you might have used npm-link-shared, to create symlinks to the local packages.
But if I run webpack after creating symlinks, I run into all sorts of webpack/babel related issues with regards to unresolved module indentifiers. I can't get them to play nice with npm link. So my question is, how was this done during development of these packages? How should this be done?
Thanks for any pointers or help.

Thank you @mariusGundersen
I did as told and ran into a small issue, that I'm sharing here so that other people may benefit from it.
The push-mixin package wouldn't install properly upon bootstrapping with Lerna, resulting in the following error
ENOENT: no such file or directory, rename 'C:\repositories\es-git-new\packages\push-mixin\node_modules\.staging\@es-git\core-5f2d41df\node_modules\text-encoding' -> 'C:\repositories\es-git-new\packages\push-mixin\node_modules\.staging\text-encoding-4a8cc963'

After running npm install in that specific package folder C:\repositories\es-git-new\packages\push-mixin and then running lerna bootstrap again in the root, it worked, and even replaced the installed packages for push-mixin with a symlinks.
lerna WARN EREPLACE_EXIST @es-git/core is already installed for @es-git/push-mixin. Replacing with symlink...

I'm just sharing my progress while going along.
Another way I could solve the above problem was by executing this in the root
lerna clean

And then run
npm run bootstrap

(fun fact: don't run npm run clean, because that forwards to lerna run clean and the latter doesn't work.

The next hurdle:
running npx webpack --config webpack.config.js in the packages\example folder leads to these kind of errors:
Module not found: Error: Can't resolve '@es-git/walkers-mixin' in 'C:\repositories\es-git-new\packages\example\ts'

I feel that it's has to do with the symlinks installed by Lerna, but I can't get it to work.
I've tried
resolve: {
      symlinks: false
    },

in webpack.config.js and
"preserveSymlinks": true,

in tsconfig.json
Got stuck at this point. Any help would again be greatly appreciated.

Great, thanks for trying the build on a different machine!
npm run clean removes all the built output, which is different from what lerna clean does. I use it to clean away old files before running npm run compile, npm run tsc and/or npm run test. If you want to run lerna clean try running npm run lerna -- clean (the dash dash forwards any parameter after it to the command being run)
For the example package you should use npm run (which will list all options when called without a parameter) to compile and run it. npm run compile will generate the bundles in production mode, while npm run dev will start webpack in watch mode and start the server.
As mentioned, I try to have every build and run tool tied to npm run so I don't have to guess or remember how to do something. If I'm uncertain I can run npm run and it will list all the scripts that can be called.

Great, thanks for trying the build on a different machine!

It's my pleasure! I think you did an awesome job with these packages.
I now successfully have set up a dev environment on my windows machine.
On windows, npm run doesn't play nice with forward slashes in tha package.json file. That caused all the compile commands to crash, which in turn was causing the Module not found errors I experienced earlier. They where just caused by the fact that those modules were still uncompiled.
I couldn't find a cross platform solution, so in the package.json files I had to replace all paths like this
../../node_modules/.bin/tsc

with this
..\\..\\node_modules\\.bin\\tsc

Specifically for the package.json in the example package, I also had to replace this
"compile": "NODE_ENV=production webpack --progress --colors",

with this
"compile": "set NODE_ENV=production && webpack --progress --colors",

After that npm run compile from the root worked smoothly.

That's unfortunate, not sure how to fix this. You can run Ubuntu on windows now though, which would fix this particular problem, but would be nice with a proper way to do it for both windows and Linux


Frequent PkgEval failures

FastaLoader.jl frequently fails on PkgEval due to what seems like a bad test:
FastaLoader.jl: Test Failed at /home/pkgeval/.julia/packages/FastaLoader/Nczh3/test/runtests.jl:19
  Expression: sum(acgt_freq_test) == 1
   Evaluated: 0.99999994f0 == 1
Stacktrace:
 [1] macro expansion
   @ /opt/julia/share/julia/stdlib/v1.10/Test/src/Test.jl:477 [inlined]
 [2] macro expansion
   @ ~/.julia/packages/FastaLoader/Nczh3/test/runtests.jl:19 [inlined]
 [3] macro expansion
   @ /opt/julia/share/julia/stdlib/v1.10/Test/src/Test.jl:1502 [inlined]
 [4] top-level scope
   @ ~/.julia/packages/FastaLoader/Nczh3/test/runtests.jl:5
Test Summary:  | Pass  Fail  Total   Time
FastaLoader.jl |    5     1      6  16.2s
ERROR: LoadError: Some tests did not pass: 5 passed, 1 failed, 0 errored, 0 broken.
in expression starting at /home/pkgeval/.julia/packages/FastaLoader/Nczh3/test/runtests.jl:4

This should probably be an isapprox test?

Thanks! Just got it updated.


Always return false positive with ternary

ESLint Version: 3.8.1
Promise Plugin Version: 3.0.0
Configuration
{
  "plugins": ["promise"],
  "rules": {
    "promise/always-return": "error"
  }
}

Minimal example
something.then(function (a) {
  return a ? 'answer' : 42;
});

Expected: No error
Actual: error  Each then() should return a value or throw

Great suggestion, can you work on the pull request?

I have a potential fix for this on my fork, but I'm worried about unforeseen side effects due to my limited understanding of AST.
I solved it by propagating the 'good' property down the segment branches from parent to children.
So once return or throw is found and marked as good, all the child segments of that one get marked as good also.
The reason I took this approach is to handle ternary expressions nested inside of an object literal which were getting marked as errors.
For example:
return {
  foo: {
    bar: (x ? 1 : 0)
  }
}

I considered checking if the last line of the function was a return or throw (old logic) and then falling back to the new branch based logic but that wouldn't work in this more complex example that has branching and ternary mixed:
if (useBool) {
  return x ? 1 : 0; // Simple ternary.
}
else {
  return {
    bar: (x ? 1 : 0) // Ternary in object literal.
  }
}

I think it's safe since the prevSegments of a function is empty. So the good doesn't propagate from outer function to inner function if someone happens to structure their promise chain that way.

I've submitted a PR for a potential fix, any thoughts? #56

Thanks for submitting. Let me take a look this weekend

resolved by #56


TN-529 Resources Page for Eproms staff

address TN-529:
https://jira.movember.com/browse/TN-529
new resources page for eproms staff

Hello @achen2401! Thanks for submitting the PR.

In the file portal/eproms/views.py, following are the PEP8 issues :

Line 262:1: E302 expected 2 blank lines, found 1
Line 268:1: E302 expected 2 blank lines, found 1
Line 284:1: E302 expected 2 blank lines, found 1
Line 300:1: E302 expected 2 blank lines, found 1
Line 315:37: E127 continuation line over-indented for visual indent
Line 321:1: E302 expected 2 blank lines, found 1
Line 330:101: E501 line too long (103 > 100 characters)
Line 335:37: E127 continuation line over-indented for visual indent
Line 339:58: W292 no newline at end of file

@ivan-c Ivan, I think I address all the issues you raised - but let me know if you see any issue with my latest changes.  A note about passing multiple tags to LR url - query parameter for tag(s) is anyTags=tag1&anyTags=tag2 instead of the expected anyTags=tag1,tag2,...making reformatting a bit challenging - I am not sure using requests.compat.urlencode to serialize the parameters in that case will work.  I added comment in the code - hopefully that will make sense.

@achen2401 Sorry, that example was kinda broken. The way LR works with the tag querystring parameters is pretty standard and our preferred way of passing multiple values for a single key (apparently there's no standard consensus), and should be supported with urlencode, as long as you pass doseq=True.
Give this a try, or let me know if I misunderstood something, otherwise I'll merge
import requests
liferay_qs_params = {
    'anyTags': [
        'tag1',
        'tag2',
        'tag3',
    ],
    'sort': 'true',
    'sortType': 'DESC',
}
requests.compat.urlencode(
    liferay_qs_params,
    doseq=True,
)

>>> requests.compat.urlencode(
...     liferay_qs_params,
...     doseq=True,
... )
'sort=true&sortType=DESC&anyTags=tag1&anyTags=tag2&anyTags=tag3'

@ivan-c ivan, thank you very much.  that makes sense.  I will give it a try.

@ivan-c Ivan, I hope this looks better now.  I think I misunderstood what you meant before.  Let me know if you see any issue with my latest changes.


Implement a timeout

Something like --timeout 30, I'm writing a benchmark and I need to set this value

🤔 a timeout on what? can you be more specific?
Also, if I'd implementing a benchmark, and we're talking about a timeout on request time, I'd implement it on the client side, not on the server. Having a timeout on the server would produce false results in a benchmark IMHO.

For handling the requests timeouts, I have something like
echo "# Django Workers" > $FILE

sudo fuser -k $PORT/tcp
gunicorn mysite.asgi --timeout $TIMEOUT --workers $THREADS --worker-class uvicorn.workers.UvicornWorker & echo "starting server..."
sleep $SLEEP_TIME
echo "## ASGI Gunicorn Uvicorn" >> $FILE
bench

sudo fuser -k $PORT/tcp
granian --interface asgi mysite.asgi:application --port $PORT --workers $THREADS --loop asyncio --no-opt & echo "starting server..."
sleep $SLEEP_TIME
echo "## Granian Asyncio" >> $FILE
bench

sudo fuser -k $PORT/tcp
granian --interface asgi mysite.asgi:application --port $PORT --workers $THREADS --loop uvloop --no-opt & echo "starting server..."
sleep $SLEEP_TIME
echo "## Granian uvloop" >> $FILE
bench

sudo fuser -k $PORT/tcp

And I thought if each server would have different timeout it should affect the results, and I'm working over Heroku, it has a request timeout of 30 seconds
My benchmark is not so realistic, I think but cover a lot of common tasks

benchmark: https://github.com/breatheco-de/apiv2/blob/main/benchmarks/django-workers/bench.sh
urls: https://github.com/breatheco-de/apiv2/blob/main/benchmarks/django-workers/mysite/urls.py
views: https://github.com/breatheco-de/apiv2/blob/main/benchmarks/django-workers/myapp/views.py

I got good results, but I could not get any good results for AIOHTTP or HTTPX test, so I think maybe the default request timeout should affect to Granian result

And it appears even with --no-opt, apparently it is not handling the requests timeout, and it should penalize the results for all the output it is generating in the console
[WARNING] Application callable raised an exception
Task exception was never retrieved
future: <Task finished name='Task-55077' coro=<future_watcher_wrapper.<locals>.future_watcher() done, defined at /home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/granian/_futures.py:2> exception=TypeError('PyFutureAwaitable.cancel() takes no arguments (1 given)')>
Traceback (most recent call last):
  File "/home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/granian/_futures.py", line 4, in future_watcher
    await inner(watcher.scope, watcher.proto)
  File "/home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 170, in __call__
    await self.handle(scope, receive, send)
  File "/home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 218, in handle
    task.cancel()
TypeError: PyFutureAwaitable.cancel() takes no arguments (1 given)
Task exception was never retrieved
future: <Task finished name='Task-55434' coro=<ASGIHandler.listen_for_disconnect() done, defined at /home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/django/core/handlers/asgi.py:226> exception=RequestAborted()>
Traceback (most recent call last):
  File "/home/jefer/dev/work/apiv2/benchmarks/django-workers/.venv/lib/python3.11/site-packages/django/core/handlers/asgi.py", line 230, in listen_for_disconnect
    raise RequestAborted()
django.core.exceptions.RequestAborted

@jefer94 1.0 added the proper code to handle cancel calls on PyFutureAwaitable, this should solve your issue.
As for the timeout thing, I'm still not convinced Granian should implement this and leave it to the application/framework.

I will make an endpoint in Heroku with an asyncio.sleep(40); print('somebody') on Wednesday to see how them interact

A timeout would be nice, timeout with the proxy, nging or whatever, just like unicorn and gunicorn

Closing this as stale

It would be really nice to have to kill "misbehaving" workers.
I've started using granian for one "legacy" service (in wsgi mode) and faced issue when some requests are hanging - deadlocking in DB transaction on hot table. Because of this postgres spikes in memory usage when this happens. After app is restarted - everything is ok. This deadlock happens very rarely and is hard to debug - so seems like timeouts are best solution for this.

faced issue when some requests are hanging - deadlocking in DB transaction on hot table. Because of this postgres spikes in memory usage when this happens. After app is restarted - everything is ok. This deadlock happens very rarely and is hard to debug - so seems like timeouts are best solution for this.

To me it sounds like you actually want statement execution timeouts and lock acquire timeouts in postgres and thus deal with the relevant errors in the Python app.
There's no way for Granian in WSGI to stop postgresql queries.

Yes, surely it would be better to fix that in code.
But it's legacy that stinks 😃. I was unable to pinpoint exactly why/where it happens.
Global timeouts will cause other stuff to break for sure, but I'll try them out, thanks for the tip.
In that case I would be fine if hanging worker was killed altogether, so rolled back to gunicorn with timeouts for now because of that.

We would also find a request timeout extremely useful. (I was going to file a new issue for this, but found this one.)
I agree that in an ideal app, all blocking operations would have correctly set timeouts, however, many libraries/frameworks default to no timeouts (including several popular HTTP clients), making it's extremely easy for end developers of an app to inadvertently end up with indefinitely blocking operations in some edge cases. Without a "timeout of last resort" in the web server, these can permanently block use of a worker/thread until the server is restarted.
In addition, some platforms (such as Heroku) have their routing layer terminate requests over a certain max request time threshold (in the case of Heroku, 30 seconds), to ensure stable platform/app operation and to encourage app architecture best practices (like moving long running tasks out of the web server and to a background worker job instead). Once the routing layer has responded with an HTTP 503 to the client, there is no point wasting additional time on the request in the server - and by terminating the request early it makes it more likely that the server/app can recover when under load.
Having a way to add a request timeout at the Granian level would help with both of these cases. It's also much easier to tell beginner end users to "use this web server with these best practice CLI arguments" (eg in a getting started guide) to help prevent them shooting themselves in the foot, than it is to expect every single one of them to remember to set app level timeouts for every blocking call from the outset :-)
Such a web server request timeout is possible when using gunicorn's sync worker type, via the --timeout argument.

Such a web server request timeout is possible when using gunicorn's sync worker type, via the --timeout argument.

@edmorley that's because the sync worker in gunicorn is serial and processes requests 1 by 1 – which also why it shouldn't definitely be used in production environments.

We would also find a request timeout extremely useful. (I was going to file a new issue for this, but found this one.)
Having a way to add a request timeout at the Granian level would help with both of these cases.

Based on your comment, I assume you're talking about WSGI applications. For that protocol there's nothing Granian can do to enforce a timeout, given the lack of support in tokio to cancel blocking operations:

Be aware that tasks spawned using spawn_blocking cannot be aborted because they are not async. If you call abort on a spawn_blocking task, then this will not have any effect, and the task will continue running normally. The exception is if the task has not started running yet; in that case, calling abort may prevent the task from starting.

that's because the sync worker in gunicorn is serial and processes requests 1 by 1 – which also why it shouldn't definitely be used in production environments.

Yeah I'm very aware of the differences between the gunicorn workers types :-) I was giving this as an example of prior art that does allow for request timeouts. Also whilst I understand why you might say the sync worker type is not suitable for production - I feel that's a bit of an oversimplification - it can be suitable depending on the workload. (Though I would agree that the gunicorn docs oversell sync as a "probably good enough", when in fact it's not for many cases.)

Based on your comment, I assume you're talking about WSGI applications. For that protocol there's nothing Granian can do to enforce a timeout, given the lack of support in tokio to cancel blocking operations:

Yes, WSGI. That's unfortunate that tokio's featureset doesn't make this possible.


Add start-app package install instructions

As a newcomer to Elm I tried to get "hello world" working using the provided example but wasn't sure how to download the package.
Added a "Getting Started" section based on the one in elm-html1 to give readers enough information to type up the example and get it running locally.

See my comment over at the related issue.

This commit seems like a good idea.  As a complete beginner, I initially tried running elm-package install StartApp and was confused when the terminal said "StartApp is not a valid package".  So I think it would definitely be helpful to provide some install instructions for those who are not familiar with the package system.

:+1:
Of course the info can be found elsewhere, but if start-app is supposed to be the entry point it makes sense to have all instructions in this readme

+1 Came here while searching how to install this.


Fixed state transitions for MSAA ScreenGrab

State transition handling when capturing MSAA resources which is supposed to get resolved was incorrect.

Bug found and verified fixed with MSAATest
https://github.com/walbourn/directxtk12test/pull/53


Support Forest in offline mode with appending blocks

Issue summary

As requested by Curio, Forest should have a way of starting in a on offline mode, i.e., don't sync to the chain, but with the possibility to submit new blocks and growing the chain.
Perhaps this can be done already with some combination of flags and configuration?
Other information and links

After discussion, the requirement is an online mode but Forest should be able to bootstrap a new network.


Role based permissions broken

;rc "command" disable "role" is not working/being enforced. nadeko lists the command as banned for the role but does not stop the users of the role from executing it.

You have to ban it for "everyone" role too first.
If a user has a role whcih allows him to do something, he will be able to do it. So you need to prevent everyone role and all roles that user has, in order to prevent him from doing that command.


⚠ Jenkins Plugins Artifactory has degraded performance

In f399c80, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1244 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 18ce4d6 after 12 minutes.


I can not get MMM-CalendarExt to run again.

Here is my config in config.js please help when you can.
I want to run it in month or monthly configuration I am using a 32" TV/Monitor as my display.
Just did a fresh install from loading Debian Buster to fresh auto load of MagicMirror.
Everything else works fine but can't figure out what I am doing wroing in the config.js, passes npm run config:check and MagicMirror is showiing default calendar, clock, MMM-MyWeather
randomquotes, daily quotes, MMM-ATM, MMM-Globe and MMM-NASA, all running on most of the screen as single pages using MMM-Carousel they run great. So you can see why I am asking for help.   All that works great together.

config of MMM-CalendarExt itself has no problem. But with MMM-Carousel, it should be the first page or all page.
(I didn't consider MMM-Carousel).
Or you can use MMM-CalendarExt2 instead.

Will look into the CalendarExt2 might be more what I am looking for anyways.
Thank you for the Information so quickly.
I am new to MM but am having a lot of fun with this little project.

Cant get either to work for me.   The config.js and custom.css are really confusing for CX2.
Jeff Burdick
From: Seongnoh Sean Yi
Sent: Friday, August 16, 2019 1:56 AM
To: eouia/MMM-CalendarExt
Cc: Jeff; Author
Subject: Re: [eouia/MMM-CalendarExt] I can not get MMM-CalendarExt to runagain. (#67)
config of MMM-CalendarExt itself has no problem. But with MMM-Carousel, it should be the first page or all page.
(I didn't consider MMM-Carousel).
Or you can use MMM-CalendarExt2 instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Bump version to v2.1.0, update min core compatibility

Questions
Answers

Description?
Bump version to v2.1.0, update min core compatibility because https://github.com/PrestaShop/dashactivity/pull/16 requires PrestaShop >= 1.7.7

Thank you for review !


changelog for storage common and blob

Look through these:
https://github.com/Azure/azure-sdk-for-cpp/compare/ef4b7c5268963f4c5ca554e304b72a83e0e55270...97af13d7e627d65676abc9e606bce40ba0f42751

Changed path of blobs.hpp and others:
blobs/inc/azure/storage/blobs/blob.hpp → ...storage-blobs/inc/azure/storage/blobs.hpp
https://github.com/Azure/azure-sdk-for-cpp/pull/837

Changed path of blobs.hpp and others:
blobs/inc/azure/storage/blobs/blob.hpp → ...storage-blobs/inc/azure/storage/blobs.hpp
#837

that's in ## 1.0.0-beta.5 (Unreleased)

Made SharedKeyCredential a class: https://github.com/Azure/azure-sdk-for-cpp/pull/942

Renamed/removed storage_version.hpp and added version.hpp
https://github.com/Azure/azure-sdk-for-cpp/pull/845

Made SharedKeyCredential a class: #942

Is that even worth mentioning in changelog? Because it sounds to me pretty much just an implementation details. How is our customers' code gonna be affected?

Is that even worth mentioning in changelog? Because it sounds to me pretty much just an implementation detail. How is our customers' code gonna be affected?

I agree its a subtle change but can be considered breaking (though unlikely, someone could have forward declared it with the same name). We called out the exception struct -> class change in Other changes for that reason:
https://github.com/Azure/azure-sdk-for-cpp/releases/tag/azure-core_1.0.0-beta.3

Update SDK-defined exception types to be classes instead of structs.

what
the

These are some fun commit messages :p


Unable to connect to ODFE Docker Container using the Spring Boot App

Am unable to connect ODFE Docker Container from a Java Spring Boot App. The following error is seen:
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{_nQbb0bvTTi0NOGs_Jm8Dw}{localhost}{<IP_ADDRESS>:9200}]
Application properties:
spring.data.elasticsearch.cluster-name=odfe-cluster
spring.data.elasticsearch.cluster-nodes=localhost:9200

Hi @sureshkoduri123  have you tried to access the endpoint with curl command? https://opendistro.github.io/for-elasticsearch-docs/docs/install/docker/ could you share the output of it?

close this issue firstly. if you still have issue, feel free to reopen it

@weicongs-amazon when I run the following curl command, I get this output:
curl -XGET https://localhost:9200 -u admin:admin --insecure
{   "name" : "dc070ebe91e9",   "cluster_name" : "my-cluster",   "cluster_uuid" : "neFiF5W1Q1Sq-bCpELKirA",   "version" : {     "number" : "7.6.1",     "build_flavor" : "oss",     "build_type" : "tar",     "build_hash" : "aa751e09be0a5072e8570670309b1f12348f023b",     "build_date" : "2020-02-29T00:15:25.529771Z",     "build_snapshot" : false,     "lucene_version" : "8.4.0",     "minimum_wire_compatibility_version" : "6.8.0",     "minimum_index_compatibility_version" : "6.0.0-beta1"   },   "tagline" : "You Know, for Search" }
After updating the application.properties file of spring boot app with:
ES_URL=https://admin:admin@localhost:9200
I am getting this error:
Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
NOTE: Am using RestHighLevelClient for connecting the cluster

this is related to certification. in the curl command, --insecure is used to skip the certification. If you wanna use this env in your cluster, you can also skip the certification in http client. btw, it's not recommended for production env. it's better to take a look how to set up the security related configuration for production env. https://opendistro.github.io/for-elasticsearch-docs/docs/install/docker-security/


Fixed typo in example

Hello :)
Noticed and fixed a typo in the README.md.
Cheers,
Raui

My bad, I had "pip installed" the wrong package...


Need Thread.Interrupt() capability

Hello,
Using TinyCLR v0.8.0
Can somebody please give me some insight as to why the Interrupt() method doesn't exist for Thread objects in c#?
If I put a thread to sleep using Timeout.Infinite, the documentation says it can be awoken using the Abort() or Interrupt() methods.  The Abort() method exists and I see that I could potentially use this to awaken a thread without killing it but would need the ResetAbort() method which I also don't see exists.
This leaves the Suspend() and Resume() methods but the documentation says these are obsolete.
So just curious how to awaken a thread put to sleep indefinitely?
And, are there plans to provide Interrupt() and/or ResetAbort()?
Thanks!

Well, the short answer is we haven't reviewed adding either Interrupt or ResetAbort yet. In general, I wouldn't rely on the regular .NET API docs too heavily for specifics yet.
In the mean time, if the thread is sleeping indefinitely, you may be able to create a solution using AutoResetEvent or ManualResetEvent where you call Wait instead of Thread.Sleep.

Sounds good, I look into your suggestions.  Thanks!

@Arke64 , Using ManualResetEvent and WaitOne did the trick.  Thanks for your help!

Happy to hear you got it working!


Feature: Improve codegen support for static assets and improve font loading for prototype-ui

Changes in this PR:

Improve font loading for prototype-ui.
Use the Google Fonts css2 API to use latest best practices https://developers.google.com/fonts/docs/css2
Use local hathora logo to reduce number of remote requests.

This was the original scope, but then I realized that plenty of non-handlebars files were loaded and passed through the compiler even they didn't use any handlebars features.
Thus, additional changes in this PR include changes related to how the codegen handles static assets:

Only use handlebars for the template files that need it, and copy the rest directly.
Slight codegen performance improvement
Simplified template maintenance by clarifying which files actually use dynamic codegen, compared to being static assets/configs.
Enable proper syntax highlighting for non-handlebars template files.

Feedback appreciated! :)

Just some minor formatting changes, otherwise this looks good!

Awesome, thanks! :smile:


question about datasets in Classification task

hi，your work is very gorgeous.I am reproducing ur work,which  be interested. Could you share your UCR dataset?
UCRdataset i got don't incould trian.pt,val.pt,test.pt.Thank you!
looking forward to your reply.

The data is already public and preprocessing codes are the same as my previous works, eg., https://github.com/emadeldeen24/TS-TCC/tree/main/data_preprocessing/epilepsy


Vulkan DynamicLoader returns null for vkGetInstanceProcAddr & vkGetDeviceProcAddr

Since MoltenVK's static symbols have been hidden (see #2121), the Vulkan DynamicLoader returns null for vkGetInstanceProcAddr & vkGetDeviceProcAddr functions when linking directly to MoltenVK, i.e.
static const vk::DynamicLoader dl( "libMoltenVK.dylib" );
vkGetInstanceProcAddr = dl.getProcAddress<PFN_vkGetInstanceProcAddr>( "vkGetInstanceProcAddr" ) yields null.
vkGetDeviceProcAddr = dl.getProcAddress<PFN_vkGetDeviceProcAddr>( "vkGetDeviceProcAddr" ) yields null.
VULKAN_HPP_DEFAULT_DISPATCHER.init( vkGetInstanceProcAddr ) no longer works.
This breaks my app which links to MoltenVK when in release mode (vulkan loader is used for debugging mode only).
In addition it breaks SDL when trying to create a Vulcan window (SDL_CreateWindow).  The SDL error message is:
Failed to find vkGetInstanceProcAddr in either executable or libMoltenVK.dylib: (null)
Even though symbols have been hidden for static linking, shouldn't they remain available to the DynamicLoader?  How  will MoltenVK 1.2.7 behave when delivered as part of the new Vulkan SDK 1.3.275?
(FYI - Removal of static symbols is a pretty disruptive change to be happening so late in a release cycle without notice.  While I can adapt in due time to the removal of static symbols, retaining dynamic PFN address retrieval for MoltenVK is critical. Otherwise you are basically saying the Vulkan loader is mandatory and MoltenVK should no longer be used directly.)

Thanks for testing it, and posting this! It will help us get this right.
The default MoltenVK build is now the same hidden-symbols build used in the SDK in previous releases. It's also compatible with how Volk works.
So we need to figure out what is needed for other dynamic loaders like the Vulkan Dynamic Loader and SDL.
@richard-lunarg Can you comment on how the SDK loader interacts with MoltenVK to access vkGetInstanceProcAddr() and vkGetDeviceProcAddr(). I agree with @SRSaunders that perhaps those two functions should be static. Thoughts?
@SRSaunders In the meantime, building MoltenVK with MVK_HIDE_VULKAN_SYMBOLS=0 will get you the same static build that was the default in previous releases. What happens when you try that?

The default MoltenVK build is now the same hidden-symbols build used in the SDK in previous releases

Something must be different about the new 1.2.7 build.  If I change my build include path and library path from my local build of MoltenVK 1.2.7 (main head) located at .../MoltenVK/Package/Release/MoltenVK/... to the previous SDK build at .../VulkanSDK/1.3.268.1/MoltenVK/..., everything works fine.  The Vulkan Dynamic Loader and SDL both pick up the necessary symbols at runtime from libMoltenVK.dylib.  If I use my local 1.2.7 build the symbols are not found.

In the meantime, building MoltenVK with MVK_HIDE_VULKAN_SYMBOLS=0 will get you the same static build that was the default in previous releases.

This does work, but is only useful in the dev environment.  For end-users, they need to use MoltenVK as provided by the Vulkan SDK.  I don't want them building local versions of MoltenVK to make things work - too much of a barrier.

On further investigation of the Volk in the MoltenVK Cube demo, it uses the default SDK /usr/local/lib/libvulkan.dylib if it can't find libMoltenVK.dylib locally. So I'll have to update the Cube demo in MoltenVK to copy libMoltenVK.dylib from the MoltenVK build, to make the MoltenVK Cube demo a standalone build, that doesn't require the SDK to be installed.
Then, once connected to libMoltenVK.dylib directly, Volk also chokes on not finding vkGetInstanceProcAddr() within libMoltenVK.dylib. I was able to fix Volk by statically exposing just this one function.
@SRSaunders Can you try building MoltenVK with the default hidden symbols, but also with the following change in vulkan.mm, please:
MVK_PUBLIC_SYMBOL PFN_vkVoidFunction vkGetInstanceProcAddr(

Note the change of MVK_PUBLIC_VULKAN_SYMBOL to MVK_PUBLIC_SYMBOL. This statically exposes vkGetInstanceProcAddr().
If that isn't enough, try making the same change to vkGetDeviceProcAddr() in vulkan.mm.
Either way, let me know what happens, please.

If I change my build include path and library path from my local build of MoltenVK 1.2.7 [snip] to the previous SDK build [snip] everything works fine with no code changes
...
For end-users, they need to use MoltenVK as provided by the Vulkan SDK.

@richard-lunarg My understanding was that, for the past few SDK releases, MoltenVK in the SDK has been built with MoltenVK static symbols hidden (MVK_HIDE_VULKAN_SYMBOLS=1). Is that not the case?

Can you try building MoltenVK with the default hidden symbols, but also with the following change in vulkan.mm, please:
MVK_PUBLIC_SYMBOL PFN_vkVoidFunction vkGetInstanceProcAddr(

I had to do some juggling to call (*vkGetInstanceProcAddr)(m_VulkanInstance, "vkGetDeviceProcAddr" ) only after device creation, otherwise you get null.  However, with code changes in place it works!
You can get away with exposing only vkGetInstanceProcAddr if you are careful as I had to be above.  I wonder if other applications may depend on having vkGetDeviceProcAddr defined earlier?  I'm not sure, others will have to comment.

I had to do some juggling to call (*vkGetInstanceProcAddr)( m_VulkanInstance, "vkGetDeviceProcAddr" ) only after device creation, otherwise you get null. However, with code changes in place it works!

Do you mean after device creation, or instance creation?

One workaround is to use the symbol name “vk_icdGetInstanceProcAddr” as that is an equivalent function still exposed in the dylib (presumably this is what libvulkan hooks into). But I imagine it’s still a problem since a number of applications and libraries are built with “vkGetInstanceProcAddr” in mind as that’s what you need to use with libvulkan.

Do you mean after device creation, or instance creation?

When I wrote this I actually meant device creation, but on second look you are right, it works after instance creation.

How were you calling (*vkGetInstanceProcAddr)( m_VulkanInstance, "vkGetDeviceProcAddr" )

I was just shorthanding the explanation.  The actual code looks more like:
static const vk::DynamicLoader dl( "libMoltenVK.dylib" );
const PFN_vkGetInstanceProcAddr vkGetInstanceProcAddr =
	dl.getProcAddress<PFN_vkGetInstanceProcAddr>( "vkGetInstanceProcAddr" );
VULKAN_HPP_DEFAULT_DISPATCHER.init( vkGetInstanceProcAddr );

createInstance();	// m_VulkanInstance is defined here

const PFN_vkGetDeviceProcAddr vkGetDeviceProcAddr =
	(PFN_vkGetDeviceProcAddr)(*vkGetInstanceProcAddr)(m_VulkanInstance, "vkGetDeviceProcAddr" );

...

createDevice();

Hopefully this more complete code snippet makes better sense.

PR #2124 should fix this now. Please test with latest MoltenVK, and close this issue if the problem has been fixed.

Thank you very much for fixing this for dynamic lookups (vkGetInstanceProcAddr), and also for reverting to allowing static linkage for the moment.  This hopefully avoids me having to submit emergency changes for SDK 1.3.275 compatibility.  I can make the changes for dynamic lookups in a more planned way.
One question confirming before I close:  Will the SDK version of MoltenVK still allow for static symbols?  You expressed some doubt about this earlier in the thread. Do you now have confirmation on how MoltenVK is built for the SDK?

Yup. LunarG confirmed that the MoltenVK library shipped with the upcoming SDK will expose static links.

Thanks for confirming.  Closing now.


[v2][build] follow Angular Package Format

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request

https://docs.google.com/document/d/1CZC2rcpxffTDfRDs6p1cfbmKNLA6x5O-NtkJglDaBVs/preview

we will use https://github.com/dherges/ng-packagr

Hi @aitboudad, any update on this?
I'm trying to make my own library with ng-formly as a dependency to share my custom types between projects, but building the lib with ng-packagr fails, maybe because ng-formly doesn't follow Angular Package Format yet ?
I can try to make a PR to use ng-packagr to build ng-formly if needed.

not yet but already done on my local but right now you can use @ng-formly/core which follow Angular Package Format

Many thanks sir, It works much better with it! I didn't knew that @ng-formly/core was available :)

the package name might change in the future :), see https://github.com/formly-js/ng-formly/issues/466

Yes I saw #466 and was looking forward to it and more generally issues tagged v2 :smile:


Handle premium chatgpt accounts

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
any premium chatgpt account
Describe the Bug
Looks like we'll need to use the text-davinci-002-render-paid model as noted by @waylaidwanderer
Maybe this is just an overridable option in the constructor?

Fixed in https://github.com/transitive-bullshit/chatgpt-api/releases/tag/v3.5.1

@transitive-bullshit could it still be used in a new version?