refactor: replace Controller.isAssociationAllowed with checkAssociation

This PR replaces the Controller.isAssociationAllowed method with the new checkAssociation method that returns the reason why an association is not allowed:
public checkAssociation(
	source: AssociationAddress,
	group: number,
	destination: AssociationAddress,
): AssociationCheckResult;

with
enum AssociationCheckResult {
	OK = 0x01,
	/** The association is forbidden, because the destination is a ZWLR node. ZWLR does not support direct communication between end devices. */
	Forbidden_DestinationIsLongRange,
	/** The association is forbidden, because the source is a ZWLR node. ZWLR does not support direct communication between end devices. */
	Forbidden_SourceIsLongRange,
	/** The association is forbidden, because a node cannot be associated with itself. */
	Forbidden_SelfAssociation,
	/** The association is forbidden, because the source node's CC versions require the source and destination node to have the same (highest) security class. */
	Forbidden_SecurityClassMismatch,
	/** The association is forbidden, because the source node's CC versions require the source node to have the key for the destination node's highest security class. */
	Forbidden_DestinationSecurityClassNotGranted,
	/** The association is forbidden, because none of the CCs the source node sends are supported by the destination. */
	Forbidden_NoSupportedCCs,
}

The old behavior can be restored by checking whether the returned result equals AssociationCheckResult.OK.
The errors thrown by addAssociations in case an association is not allowed (code: ZWaveErrorCodes.AssociationCC_NotAllowed) now contain an array with all forbidden destinations in the error's context property, each with an added checkResult property which contains the reason why the association is forbidden:
{
	checkResult: AssociationCheckResult;
	nodeId: number;
	endpoint?: number | undefined;
}[]

fixes: https://github.com/zwave-js/node-zwave-js/issues/6772

@zwave-js-bot automerge


Fixing generic cluster Resource Definition

This PR removes the unsupported field name from the Driver input values in the generic YAML cluster Resource Definition.
For conformance with its Terraform sibling, it also adds the optional agent_url to illustrate this capacity.

This PR is obsolete, the issue has been fixed in https://github.com/humanitec-architecture/example-library/pull/47. Closing.


Registering SIGINT handler to cleanly exit application doesn't work because phantom gets killed right away

In my application I've done process.on('SIGINT', mySigintHandler) to cleanly exit the application when the current tasks have finished rather than killing the application immediately and leaving the tasks in an inconsistent state.
However, as soon as I do ctrl+c in the console, the application doesn't cleanly exit because phantomjs is killed right away (error message for example is Error reading from stdin: Error: This socket has been ended by the other party).
 This would be a useful feature to add if it's not possible currently.

@rightaway it looks like that is done here. There is no configuration to disable this. I don't think anybody has ever asked for such need.
I am curious if you can patch kill since it is public by doing phantomInstance.kill = function(){ ...}  that's obviously a hack. If it doesn't work, it would make more sense to create a patch that accepts a configuration for this setting.

I'll see if patching kill as you suggested works. But how would I clean up the numerous phantom instances that might be alive from my SIGINT handler when the app is ready to cleanly shutdown? Is there a function I can call in this module that would kill all processes?

Each phantom process is managed by one phantom instance. If you create multiple instances then there will be multiple processes. They don't have knowledge of each other. You would have to track the processes yourself and call .kill().

You are right. You have to save the old function like. Something like:
phantomInstance.oldKill = phantomInstance.kill;
phantomInstance.kill = function (){
...
}
phantomInstance.oldKill() // will actually kill it.

Ps. This is all monkey patching. A pull request is still a good option. But it would be much harder because you'd have to add tests and read through the code. Up to you which on you do.

@rightaway did it work?

@amir20 I decided to work around having to use phantom in this particular case to avoid the monkey patching option. I've been looking through the code to figure out how to create a patch to add configuration to disable automatic termination, but felt fairly lost in the code.
Would you mind re-opening this issue? I do think it's a worthwhile feature request and in the future me or another contributor may have a patch to offer.

Generally, I'd like to keep issues open that are actually bugs. Issues should be actionable. If a behavior as not as expected then it is a bug. Feature requests being open will just get lost and no one will ever look at it. No one has asked for this feature so I doubt it will get a PR. If you want it, then it would be you sending the PR.
The work should be easy. You need to modify the constructor to have some sort of flag to disable the kill. There isn't that much code. Maybe because it uses Flowjs it is confusing.


last element's bottom margin is too much on about and home layouts

Describe the bug

last element's bottom margin is too much.
Screenshots

last element's bottom margin is too much.

Expected behavior

To Reproduce
Steps to reproduce the behavior:

build locally or on github

Desktop (please complete the following information):
all
Mobile devices (please complete the following information):
all
Additional context

fixed with #51


Define capabilities and API for sl-textarea

This issue is where discussion about all of the things we want to change about the sl-textarea component should occur and the final definition of its capabilities and API are defined.  As these items are discussed and vetted, issues will be created to work any individual tasks, with this issue serving as the overall source of progress.
To indicate that a capability of the component needs to be verified, add a comment with **VERIFY** as the first line.
To propose a change to the component, add a comment with **PROPOSAL** as the first line.
To indicate that something needs to be researched, add a comment with **RESEARCH** as the first line.
As you are leaving comments regarding any of these VERIFY, PROPOSAL, or RESEARCH comments, link back to the comments link in your own so that the conversation can be more easily followed (in absence of threaded conversation support in Github).  This should be done on the first line of the comment via **RE: <url>**
Capabilities and API

[ ] ARIA support
[ ] ...

Tasks
Adding them here until issues are created

Update documentation for each change
Complete review of documentation against capabilities

Issues tracking these efforts
https://github.com/softlayer/sl-ember-components/issues?q=is%3Aopen+is%3Aissue+milestone%3A"v0.13.0+(Final+push+for+a+1.0.0+release)"+label%3Asl-textarea

PROPOSAL

Add optional characterLimit property which, when set, would display how many characters are left e.g http://jsfiddle.net/azizpunjani/JCehq/1285/


Broken embed of a video

Issue in ./help/analyze/analysis-workspace/c-panels/average-minute-audience-panel.md
Hi you guys.
On this page, you can see that there is a broken embed of a video. Inspecting it, it looks like maybe it has comment codes around it or something.
The markdown embed code for the video should be:

!VIDEO

If you have any questions, let me know.
Doug Moore
<EMAIL_ADDRESS>

Hey Doug, couldn't see the issue. Maybe it's solved already by someone else? Can you check and if you think it is solved, close the issue?
Thanks.
<EMAIL_ADDRESS>

Doug, Luke fixed this, so I will close it.


Blank App, Packaged (WinUI3 in Desktop) template project: missing High DPI awareness

Describe the bug
Window contents are blur.
In TaskManager, the DPI awareness is "Unknown".
Steps to reproduce the bug

using "Blank App, Packaged (WinUI3 in Desktop)" template to create a c++ project
build and run

Expected behavior
Window contents are clear.
The DPI awareness is "PerMonitorV2".
Screenshots

NuGet package version
1.0.0-preview3
Packaging type
Packaged (MSIX)
Windows version
May 2021 Update (19043)
IDE
Visual Studio 2022
Additional context
200% display scaling:

Duplicated #6075

This should already be fixed with WASDK 1.0 GA

1.0 solved this problem


feat(java): :sparkles: boolean values handled as test data in excel s…

…heet
Boolean values were not handled correctly as test data. This has been fixed in this ticket
Closes: #908
Type of changes?

[ ] Bug fixes: Non-breaking change which fixes an issue
[x] New feature: Non-breaking change which adds a new feature
[ ] Performance improvement: Non-breaking change which improves performance
[ ] Documentation: Non-breaking change which improves documentation
[ ] Other: Non-breaking change which does not fit into the above categories
[ ] Breaking change: A breaking change which requires a new version of the library

Checklist for Java project

[ ] Change not related to Java project

Following checklists are optional if above checkbox is selected:

[x] Copyright banner comment added to newly added files, except *.md, *.yml, *.json?
[x] Proper JavaDoc updated in main and test classes for all public classes and methods?
[x] Tests added for changes?
[x] Tests are passing locally?
[x] Check style checks are passing locally?
[x] Test coverage is at least 80% for newly added changes?
[x] There are no SonarCloud issues?
[x] README updated? (if applicable)
[x] Documentation website updated for the PR raised?

Checklist for Website

[x] Change not related to Website project

Following is optional if above checkbox is selected:

[ ] Lint check passes locally?
[ ] Prettier check passes locally?
[ ] Build command working fine locally?

Reviewers
@BoykaFramework/boyka-core

[!IMPORTANT]
Make sure to check the Allow edits from maintainers box below this window

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

:rocket: This pull request is included in v2.2.0. See Release 2.2.0 for release notes.


sql: Support virtual fields and overriding timestamp via event_time_field

This adds two complementary features:
Virtual columns and overriding the timestamp with a SQL column. These are currently restricted to tables created in SQL with connections, but should be expanded upon in the future.
Virtual Columns
We use the postgres syntax of field_name field_type GENERATED ALWAYS AS ($EXPRESSION). The $EXPRESSION is will come through the SQL AST as a sqlparser::ast::Expr. This then needs to be converted to dataFusion's Expr, and then Arroyo's Expression. I don't love how disjoint this is from the normal dataflow, but we're restricted by DataFusion's capabilities right now.
Event Time Field
We also now support overriding the timestamp from a source configured within SQL. This is done by the event_time_field parameter in the WITH clause of the CREATE TABLE statement. If present it will validate that the column exists and is a timestamp. Currently the pipeline will panic if the timestamp column is null, something that should be configurable in the future.

Here's an example query that behaves as desired
CREATE TABLE top_one (
    row_number int,
    auction int,
    count int,
    time string,
    parsed_timestamp datetime GENERATED ALWAYS AS (CAST(time as TIMESTAMP)),
    )
    WITH (
        connection = 'local',
        topic = 'top_one',
        event_time_field = 'parsed_timestamp'
    );

SELECT row_number, auction, count FROM top_one

Will do


Document code for memory

Add docstrings and comments in the code

Done. Code documented at the same time as creating the tests, as per commit 07fc3c3d2ecb66687eb0979bfc4dbaafda3a83e7


Release.yml added for PR categorisation

PR Details
Implement automated Release Notes generation, well semi-automated, we have to manually create the comparison, which will generate the content, but at least we can test it. Maybe TeamCity will automate/trigger this process fully.
Description
This PR introduces an automated process for generating release notes using a release.yml GitHub Actions configuration. This workflow is tailored to categorize changes into sections such as Breaking Changes, New Features, Bug Fixes, and more, based on the labels assigned to merged PRs. It also excludes specific labels and authors (e.g., dependabot) from the changelog to streamline the release notes.
Once it is merged, we can test it and correct the categorisation according our needs.
Workflow
Who ever merges PRs:

Must/should categorise each PR with a label.

Related Issue
N/A - This is an improvement to our CI/CD process, not directly related to an existing issue.
Motivation and Context
The primary goal of automating release notes generation is to enhance the efficiency and accuracy of our release process. Manually compiling release notes is time-consuming and prone to omissions. By leveraging GitHub Actions, we ensure that all significant changes are automatically documented in each release, providing clear and consistent communication to our users about what has changed.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have built and run the editor to try this change out.

Example

Looks good but PRs can only be within one category right ? If we were to mark one PR with both new feature and rendering it would only be included in the first OR the second.
If that's the case, how should we classify things, either bug fix or new features then have a prefix Rendering:  for bug fixes or new features related to rendering ?
Or should we do the opposite, and have Bug Fix:/new Feature: as prefix ?

Looks good but PRs can only be within one category right ? If we were to mark one PR with both new feature and rendering it would only be included in the first OR the second.

Let me test in locally and find out..

If that's the case, how should we classify things, either bug fix or new features then have a prefix Rendering:  for bug fixes or new features related to rendering ?

That is exactly what we need to figure out, some guidiance, how we are going to catogorise it and mainly, how we want to communicate it.
Maybe we should categorise it in the first place, where it belongs to, with the game related terminology, regardless it is a bug or new feature, maybe people more relate to these game terms?:

categories: Physics, Audio, Rendering, Graphics, GameStudio, Docs, Engine, ..

And if we think that in some cases, it is better to communicate it as a bug fix, then we could use "Bug Fixes" category as well if needed.
Additionally, I like prefixes so we could use (https://www.conventionalcommits.org/en/v1.0.0/):

fix, feat, build, chore, docs, refactor,..

So that would mean that a person who is merging would need to assign a only one label and correct the prefix, or add if missing.
And then fix or feat can be in any category obviously.
Any other thoughts, anyone?
Once you merge it, we can actually test it, we would need to label last 10-20 PRs, and probably if we can, also add prefixes.
If it is going to work, then we can decide properly on categories and prefixes we would like to have.

If this is based on PRs then we can rename them even after merging. If it were based on commits that's a different story.
We've generally tried to prefix PRs with the area [Core]/[Rendering]/[Editor] etc. I'm personally not a big fan of conventional commits, because you need to align to their convention rather than coming up with one that suits you.
For this release notes split, would be good to make some sort of poll maybe on Discord and ask people whether they prefer this or the other split.
But I would say something like below 3 categories would be enough to communicate the important bits.

Breaking changes
New features
Bug fixes

Having anything more is just for people to be aware other work is being done, but usually they are interested in what's going to break, what was fixed and what is new.

Hello. Thank you, everyone, for your feedback. After conducting a few tests, here are the findings:

The GitHub release notes are generated based on PRs, not individual commits.
PR titles can be renamed at any time.
The categories in Release.yml can encompass multiple labels under a single category.
While a PR can possess multiple labels, the release workflow generates only one entry per PR for each category, prioritized from top to bottom. This means a PR will appear under only one category in the release notes, even if it has multiple applicable labels.
Updates to categories/labels in Release.yml will take effect starting from the subsequent release tag.

Given these insights, we should consider discussing in Discord our preferred approach to PR categorization.
Option 1, as suggested by @manio143, includes the following categories (subject to refinement):

Breaking Changes
New Features
Bug Fixes
XML Docs
Other

Furthermore, we should prefix each PR for easier referencing and searching within the release notes, e.g., "Physics:" related PRs.
Prefixes: Physics, Engine, Performance, Graphics, Input, Launcher, Shaders, Audio, etc.—essentially, any relevant category.
Option 2 involves using our existing label areas or any other existing labels:

Asset
Audio
Build
Docs
GameStudio
Graphics
Input
Launcher
...
Other

Moreover, we should adopt prefixes as per Conventional Commits 1.0.0:
Prefixes: feat:, refactor:, fix:, chore:, build:, docs:, perf:, test:, etc.
A breaking change can be denoted by adding an exclamation mark, e.g., feat!:, chore!:.
Regardless of the chosen option, the person merging a PR would need to:

Label the PR, which requires just a few clicks. Some of us can label the PRs ourselves.
Check and update the PR's prefix if incorrect or missing. Often, this might already be done by the PR creator.

What do you think now, with this additional input?

IMO it makes sense for the person merging PR to ensure it's categorized and named correctly.

This PR was updated according the discussion we had on Discord, and then summarised here https://discord.com/channels/500285081265635328/707563402482024488. We can further fine-tune as desired.

If no further questions, can this be merged?

Thanks @VaclavElias !


Refresh all "classic" How-To Guides

Earn up to $600 worth of XLM for all or $100 worth of XLM each
What problem does your feature solve?
Most Encyclopedia entries that explain Stellar functions include examples. They need a little refresh to ensure they work.
What would you like to see?
Refresh:
https://developers.stellar.org/docs/encyclopedia/channel-accounts
https://developers.stellar.org/docs/encyclopedia/claimable-balances
https://developers.stellar.org/docs/encyclopedia/clawbacks
https://developers.stellar.org/docs/encyclopedia/liquidity-on-stellar-sdex-liquidity-pools#examples
https://developers.stellar.org/docs/encyclopedia/signatures-multisig
https://developers.stellar.org/docs/encyclopedia/sponsored-reserves

@briwylde08 🫱🏻🫲🏼 Checkout: working on all six (per #664, P1489, and #256)


sd.query_devices not seeing all devices?

Hello,
Could you possibly provide insight into the following problem.
sd.query_devices() generates the output below. There is an ASIO driver available which is not being picked up. The second set of listings is generated by the pyo package, which sees and uses the ASIO driver; this is how I know it is available and working fine. The sound card is an SB Audigy 5/Rx with the latest driver. We are running Python 2.7.11 on Windows 7 (32-bit). The sounddevice module works fine in all other respects!
   0 Microsoft Sound Mapper - Input, MME (2 in, 0 out)
>  1 Microphone (Sound Blaster Audig, MME (2 in, 0 out)
   2 Stereo Mix (Realtek High Defini, MME (2 in, 0 out)
   3 "What U Hear" (Sound Blaster Au, MME (2 in, 0 out)
   4 Line-In (Sound Blaster Audigy 5, MME (2 in, 0 out)
   5 Microsoft Sound Mapper - Output, MME (0 in, 2 out)
<  6 Speakers (Sound Blaster Audigy , MME (0 in, 8 out)
   7 SPDIF Out (Sound Blaster Audigy, MME (0 in, 2 out)
   8 Speakers / Headphones (Realtek , MME (0 in, 2 out)
   9 SPDIF Out (Sound Blaster Audigy 5/Rx), Windows WASAPI (0 in, 2 out)
  10 Speakers (Sound Blaster Audigy 5/Rx), Windows WASAPI (0 in, 2 out)
  11 Speakers / Headphones (Realtek High Definition Audio), Windows WASAPI (0 in, 2 out)
  12 Stereo Mix (Realtek High Definition Audio), Windows WASAPI (2 in, 0 out)
  13 "What U Hear" (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
  14 Microphone (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
  15 Line-In (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
  16 S, Windows WDM-KS (0 in, 2 out)
  17 S, Windows WDM-KS (2 in, 8 out

Pyo AUDIO devices:
0: IN, name: Microsoft Sound Mapper - Input, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
1: IN, name: Microphone (Sound Blaster Audig, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
2: IN, name: Stereo Mix (Realtek High Defini, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
3: IN, name: "What U Hear" (Sound Blaster Au, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
4: IN, name: Line-In (Sound Blaster Audigy 5, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
5: OUT, name: Microsoft Sound Mapper - Output, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
6: OUT, name: Speakers (Sound Blaster Audigy , host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
7: OUT, name: SPDIF Out (Sound Blaster Audigy, host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
8: OUT, name: Speakers / Headphones (Realtek , host api index: 0, default sr: 44100 Hz, latency: 0.090000 s
9: IN, name: Primary Sound Capture Driver, host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
10: IN, name: Microphone (Sound Blaster Audigy 5/Rx), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
11: IN, name: Stereo Mix (Realtek High Definition Audio), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
12: IN, name: "What U Hear" (Sound Blaster Audigy 5/Rx), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
13: IN, name: Line-In (Sound Blaster Audigy 5/Rx), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
14: OUT, name: Primary Sound Driver, host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
15: OUT, name: Speakers (Sound Blaster Audigy 5/Rx), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
16: OUT, name: SPDIF Out (Sound Blaster Audigy 5/Rx), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
17: OUT, name: Speakers / Headphones (Realtek High Definition Audio), host api index: 1, default sr: 44100 Hz, latency: 0.120000 s
18: IN, name: Creative ASIO, host api index: 2, default sr: 48000 Hz, latency: 0.050000 s
18: OUT, name: Creative ASIO, host api index: 2, default sr: 48000 Hz, latency: 0.050000 s
19: IN, name: Realtek ASIO, host api index: 2, default sr: 44100 Hz, latency: 0.008707 s
19: OUT, name: Realtek ASIO, host api index: 2, default sr: 44100 Hz, latency: 0.008707 s
20: IN, name: SBAudigy5/Rx ASIO 24/96[D000], host api index: 2, default sr: 96000 Hz, latency: 0.050000 s
20: OUT, name: SBAudigy5/Rx ASIO 24/96[D000], host api index: 2, default sr: 96000 Hz, latency: 0.050000 s
21: IN, name: SBAudigy5/Rx ASIO[D000], host api index: 2, default sr: 48000 Hz, latency: 0.050000 s
21: OUT, name: SBAudigy5/Rx ASIO[D000], host api index: 2, default sr: 48000 Hz, latency: 0.050000 s
22: OUT, name: SPDIF Out (Sound Blaster Audigy 5/Rx), host api index: 3, default sr: 44100 Hz, latency: 0.003000 s
23: OUT, name: Speakers (Sound Blaster Audigy 5/Rx), host api index: 3, default sr: 44100 Hz, latency: 0.003000 s
24: OUT, name: Speakers / Headphones (Realtek High Definition Audio), host api index: 3, default sr: 48000 Hz, latency: 0.003000 s
25: IN, name: Stereo Mix (Realtek High Definition Audio), host api index: 3, default sr: 48000 Hz, latency: 0.003000 s
26: IN, name: "What U Hear" (Sound Blaster Audigy 5/Rx), host api index: 3, default sr: 44100 Hz, latency: 0.003000 s
27: IN, name: Microphone (Sound Blaster Audigy 5/Rx), host api index: 3, default sr: 44100 Hz, latency: 0.003000 s
28: IN, name: Line-In (Sound Blaster Audigy 5/Rx), host api index: 3, default sr: 44100 Hz, latency: 0.003000 s
29: OUT, name: Speakers (Realtek HD Audio output), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
30: IN, name: Jack Mic (Realtek HD Audio Front Mic input), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
31: IN, name: Stereo Mix (Realtek HD Audio Stereo input), host api index: 4, default sr: 48000 Hz, latency: 0.010000 s
32: OUT, name: SPDIF Out (SB Audigy 5/Rx SpdifOut [D000]), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
33: IN, name: Wave (SB Audigy 5/Rx [D000]), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
34: IN, name: Microphone (SB Audigy 5/Rx [D000]), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
35: IN, name: Line-In (SB Audigy 5/Rx [D000]), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s
36: OUT, name: Speakers (SB Audigy 5/Rx [D000]), host api index: 4, default sr: 44100 Hz, latency: 0.010000 s

I don't know, but let's find out!
You should check which PortAudio version you are using. You can do that with sd.get_portaudio_version(). I don't know how it's done with pyo.
Which version of sounddevice are you using?
In the last version (0.3.6) I changed the DLL to a newer PortAudio version, are you using that?
Either way, you should check the other available DLL.
If that doesn't shed light on the problem, you can try to install Christoph Gohlke's wheel package for sounddevice: http://www.lfd.uci.edu/~gohlke/pythonlibs/#sounddevice
You can also try any other PortAudio DLL you can find ...

ok.
We are using version 0.3.6 of sounddevice, and portaudio version 1899 V19-devel (built Oct 8, 2013)

This is very strange, it should use a newer PortAudio version.
How did you install the sounddevice module?
What is the output of the following code?
from ctypes.util import find_library
find_library('portaudio')

Did you try the Gohlke wheels?

Thank you for the suggestions. I had wondered. There was indeed an old version of portaudio earlier in the search path. All works fine now.
In case others encounter a similar issue, note that find_library() does work on Windows. None is always returned.

Great. I'm glad that it works now.
Just out of curiosity, can you please post your new list of devices?
Thanks for pointing out that find_library() doesn't work. I thought it would work if a file named portaudio.dll is in Python's path.
Do you know another way to find out if the DLL in _sounddevice_data/ is used or another one from somewhere else?

The new list is below.
I wish I knew. Such a routine would be handy. Off hand, one thing that could be done is to alert the user to the presence of multiple copies of portaudio on the device by searching through the entire dir structure.
0 Microsoft Sound Mapper - Input, MME (2 in, 0 out)

1 Microphone (Sound Blaster Audig, MME (2 in, 0 out)
2 Stereo Mix (Realtek High Defini, MME (2 in, 0 out)
3 "What U Hear" (Sound Blaster Au, MME (2 in, 0 out)
4 Line-In (Sound Blaster Audigy 5, MME (2 in, 0 out)
5 Microsoft Sound Mapper - Output, MME (0 in, 2 out)
<  6 Speakers (Sound Blaster Audigy , MME (0 in, 2 out)
7 SPDIF Out (Sound Blaster Audigy, MME (0 in, 2 out)
8 Speakers / Headphones (Realtek , MME (0 in, 2 out)
9 Primary Sound Capture Driver, Windows DirectSound (2 in, 0 out)
10 Microphone (Sound Blaster Audigy 5/Rx), Windows DirectSound (2 in, 0 out)
11 Stereo Mix (Realtek High Definition Audio), Windows DirectSound (2 in, 0 out)
12 "What U Hear" (Sound Blaster Audigy 5/Rx), Windows DirectSound (2 in, 0 out)
13 Line-In (Sound Blaster Audigy 5/Rx), Windows DirectSound (2 in, 0 out)
14 Primary Sound Driver, Windows DirectSound (0 in, 2 out)
15 Speakers (Sound Blaster Audigy 5/Rx), Windows DirectSound (0 in, 2 out)
16 SPDIF Out (Sound Blaster Audigy 5/Rx), Windows DirectSound (0 in, 2 out)
17 Speakers / Headphones (Realtek High Definition Audio), Windows DirectSound (0 in, 2 out)
18 Creative ASIO, ASIO (14 in, 20 out)
19 Realtek ASIO, ASIO (2 in, 2 out)
20 SBAudigy5/Rx ASIO 24/96[D000], ASIO (2 in, 8 out)
21 SBAudigy5/Rx ASIO[D000], ASIO (14 in, 20 out)
22 SPDIF Out (Sound Blaster Audigy 5/Rx), Windows WASAPI (0 in, 2 out)
23 Speakers (Sound Blaster Audigy 5/Rx), Windows WASAPI (0 in, 2 out)
24 Speakers / Headphones (Realtek High Definition Audio), Windows WASAPI (0 in, 2 out)
25 Stereo Mix (Realtek High Definition Audio), Windows WASAPI (2 in, 0 out)
26 "What U Hear" (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
27 Microphone (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
28 Line-In (Sound Blaster Audigy 5/Rx), Windows WASAPI (2 in, 0 out)
29 Speakers (Realtek HD Audio output), Windows WDM-KS (0 in, 2 out)
30 Jack Mic (Realtek HD Audio Front Mic input), Windows WDM-KS (2 in, 0 out)
31 Stereo Mix (Realtek HD Audio Stereo input), Windows WDM-KS (2 in, 0 out)
32 SPDIF Out (SB Audigy 5/Rx SpdifOut [D000]), Windows WDM-KS (0 in, 2 out)
33 Wave (SB Audigy 5/Rx [D000]), Windows WDM-KS (2 in, 0 out)
34 Microphone (SB Audigy 5/Rx [D000]), Windows WDM-KS (2 in, 0 out)
35 Line-In (SB Audigy 5/Rx [D000]), Windows WDM-KS (2 in, 0 out)
36 Speakers (SB Audigy 5/Rx [D000]), Windows WDM-KS (0 in, 8 out)

Thanks, looks good!
If you find something out about getting information on the used DLL, please let me know.
In the meantime, we can close this issue, right?


Update sites.yml

https://radar.cloudflare.com/scan/6a26c390-b620-4110-8e92-b5acbf63d062/summary

This PR is:

[X] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[X] I used the uncompressed size of the site
[X] I have included a link to the Cloudflare report
[X] This site is not an ultra lightweight site
[X] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[X] Check to confirm

- domain: missionfranceguichet.fr
  url: https://missionfranceguichet.fr/
  size: 56.17
  last_checked: 2024-01-30

Cloudflare Report: https://radar.cloudflare.com/scan/6a26c390-b620-4110-8e92-b5acbf63d062/summary

Thanks!

Thank you Kev for adding my website to the list.Have a nice day.
Le mercredi 31 janvier 2024 à 09:46:29 UTC+1, Garrit Franke @.***> a écrit :
Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


[Feature Request]: Add GithubLLM

Feature Description
We propose adding a new GithubLLM class to LlamaIndex. This custom LLM interface would allow users to interact with AI models hosted on GitHub's inference endpoint, with automatic fallback to Azure when rate limits are reached. Key features include:

Seamless integration with GitHub-hosted AI models
Automatic fallback to Azure when GitHub rate limits are reached
Support for both completion and chat-based interactions
Streaming support for both completion and chat responses
Easy integration with the existing LlamaIndex ecosystem

The implementation would be similar to other custom LLMs in LlamaIndex, inheriting from the CustomLLM class and implementing the necessary methods (complete, stream_complete, chat, stream_chat, etc.).
Reason
Currently, LlamaIndex does not have built-in support for GitHub's hosted AI models. Users who want to prototype with these models and potentially transition to Azure for production use don't have a straightforward way to do so within the LlamaIndex framework.
Value of Feature
Adding GithubLLM to LlamaIndex would provide several benefits:

Prototyping: Developers can easily experiment with GitHub-hosted AI models for free, lowering the barrier to entry for AI development.
Seamless Production Transition: The implementation allows for a smooth transition from prototyping to production by simply switching from a GitHub token to an Azure token.
Rate Limit Management: Built-in rate limit handling and Azure fallback ensure that applications can continue functioning even when GitHub limits are reached.
LlamaIndex Integration: Users can leverage all of LlamaIndex's powerful features while using GitHub-hosted models.
Flexibility: Support for both completion and chat-based interactions, as well as streaming, provides flexibility for various use cases.

This feature would make LlamaIndex an even more comprehensive platform for AI development, from prototyping to production, and would align well with GitHub's efforts to provide accessible AI models to developers.

@Josephrp GitHub models are hosted in Azure. Use the LlamaIndex integration we have there. It should be supported: https://docs.llamaindex.ai/en/stable/examples/llm/azure_inference/. You need to pass the parameter model_name though. I will update the docs so it's properly displayed, but it's already supported.

Following up on @santiagxf,
I tried his suggestion here: https://github.com/leestott/azureai-x-arize/pull/1
Some functions work out of the box others error due to not specifying a model_name
Example for working functions without changing anything other than specifying the model name in the initialization:

AzureAICompletionsModel.complete
AzureAICompletionsModel.stream_complete

Example for functions that do not work:

RagDatasetGenerator.generate_questions_from_nodes
SummaryIndex.as_query_engine

The error is the same for all, Traceback for error:
---------------------------------------------------------------------------
HttpResponseError                         Traceback (most recent call last)
Cell In[16], line 1
----> 1 summarize_query_engine = summary_index.as_query_engine(
      2     llm=llm,
      3     response_mode="tree_summarize",
      4     use_async=True,
      5 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/indices/base.py:411, in BaseIndex.as_query_engine(self, llm, **kwargs)
    404 retriever = self.as_retriever(**kwargs)
    405 llm = (
    406     resolve_llm(llm, callback_manager=self._callback_manager)
    407     if llm
    408     else llm_from_settings_or_context(Settings, self.service_context)
    409 )
--> 411 return RetrieverQueryEngine.from_args(
    412     retriever,
    413     llm=llm,
    414     **kwargs,
    415 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/query_engine/retriever_query_engine.py:110, in RetrieverQueryEngine.from_args(cls, retriever, llm, response_synthesizer, node_postprocessors, response_mode, text_qa_template, refine_template, summary_template, simple_template, output_cls, use_async, streaming, service_context, **kwargs)
     88 """Initialize a RetrieverQueryEngine object.".
     89
     90 Args:
   (...)
    106
    107 """
    108 llm = llm or llm_from_settings_or_context(Settings, service_context)
--> 110 response_synthesizer = response_synthesizer or get_response_synthesizer(
    111     llm=llm,
    112     service_context=service_context,
    113     text_qa_template=text_qa_template,
    114     refine_template=refine_template,
    115     summary_template=summary_template,
    116     simple_template=simple_template,
    117     response_mode=response_mode,
    118     output_cls=output_cls,
    119     use_async=use_async,
    120     streaming=streaming,
    121 )
    123 callback_manager = callback_manager_from_settings_or_context(
    124     Settings, service_context
    125 )
    127 return cls(
    128     retriever=retriever,
    129     response_synthesizer=response_synthesizer,
    130     callback_manager=callback_manager,
    131     node_postprocessors=node_postprocessors,
    132 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/response_synthesizers/factory.py:74, in get_response_synthesizer(llm, prompt_helper, service_context, text_qa_template, refine_template, summary_template, simple_template, response_mode, callback_manager, use_async, streaming, structured_answer_filtering, output_cls, program_factory, verbose)
     68     prompt_helper = service_context.prompt_helper
     69 else:
     70     prompt_helper = (
     71         prompt_helper
     72         or Settings._prompt_helper
     73         or PromptHelper.from_llm_metadata(
---> 74             llm.metadata,
     75         )
     76     )
     78 if response_mode == ResponseMode.REFINE:
     79     return Refine(
     80         llm=llm,
     81         callback_manager=callback_manager,
   (...)
     91         service_context=service_context,
     92     )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/llms/azure_inference/base.py:282, in AzureAICompletionsModel.metadata(self)
    279 @property
    280 def metadata(self) -> LLMMetadata:
    281     if not self._model_name:
--> 282         model_info = self._client.get_model_info()
    283         if model_info:
    284             self._model_name = model_info.get("model_name", None)

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/core/tracing/decorator.py:94, in distributed_trace.<locals>.decorator.<locals>.wrapper_use_tracer(*args, **kwargs)
     92 span_impl_type = settings.tracing_implementation()
     93 if span_impl_type is None:
---> 94     return func(*args, **kwargs)
     96 # Merge span is parameter is set, but only if no explicit parent are passed
     97 if merge_span and not passed_in_parent:

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/ai/inference/_patch.py:660, in ChatCompletionsClient.get_model_info(self, **kwargs)
    653 """Returns information about the AI model.
    654
    655 :return: ModelInfo. The ModelInfo is compatible with MutableMapping
    656 :rtype: ~azure.ai.inference.models.ModelInfo
    657 :raises ~azure.core.exceptions.HttpResponseError:
    658 """
    659 if not self._model_info:
--> 660     self._model_info = self._get_model_info(**kwargs)  # pylint: disable=attribute-defined-outside-init
    661 return self._model_info

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/core/tracing/decorator.py:94, in distributed_trace.<locals>.decorator.<locals>.wrapper_use_tracer(*args, **kwargs)
     92 span_impl_type = settings.tracing_implementation()
     93 if span_impl_type is None:
---> 94     return func(*args, **kwargs)
     96 # Merge span is parameter is set, but only if no explicit parent are passed
     97 if merge_span and not passed_in_parent:

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/ai/inference/_operations/_operations.py:558, in ChatCompletionsClientOperationsMixin._get_model_info(self, **kwargs)
    556         response.read()  # Load the body in memory and close the socket
    557     map_error(status_code=response.status_code, response=response, error_map=error_map)
--> 558     raise HttpResponseError(response=response)
    560 if _stream:
    561     deserialized = response.iter_bytes()

HttpResponseError: (no_model_name) No model specified in request. Please provide a model name in the request body or as a x-ms-model-mesh-model-name header.
Code: no_model_name
Message: No model specified in request. Please provide a model name in the request body or as a x-ms-model-mesh-model-name header.

I digged deeper in the codebase and found out that this is the reason for erroring:
You call get_model_info if the model_name is not set I did set the model_name and it works for some functions and others it doesn't, I'm suspecting that it might not be passed correctly but it seems to be a bug for now not a new feature that needs to be implemented.
llama_index/llms/azure_inference/base.py", line 282
    @property
    def metadata(self) -> LLMMetadata:
        if not self._model_name:
            model_info = self._client.get_model_info()

Workaround for now that seems to fix the previous errors, this is compatible with GitHub models,
@Josephrp someone needs to fix the init for the model_name
To create a chat model client use this code:
llm = AzureAICompletionsModel(
    endpoint=os.environ["AZURE_AI_ENDPOINT_URL"],
    credential=os.environ["AZURE_AI_ENDPOINT_KEY"],
    model_name=os.environ["AZURE_AI_MODEL_NAME"],
)
llm._model_name = os.environ["AZURE_AI_MODEL_NAME"]

To create an embedding model client use this code:
embed_model = AzureAIEmbeddingsModel(
    endpoint=os.environ["AZURE_AI_EMBED_ENDPOINT_URL"],
    credential=os.environ["AZURE_AI_EMBED_ENDPOINT_KEY"],
    model_name=os.environ["AZURE_AI_EMBED_MODEL_NAME"]
)
embed_model.model_name = os.environ["AZURE_AI_EMBED_MODEL_NAME"]    # This is the fix

Hi @john0isaac! Thanks for helping with the debug! I can get a PR and fix it.

You are most welcome @santiagxf, I was already working on a branch PR is now ready at your repo.

@john0isaac can you verify if you are using the latest version of the library? Because I checked and I happen to added a test for this case and I see it passing.
https://github.com/santiagxf/llama_index/blob/729d5f2e76cca29284157c6fd8b55fb9953739dd/llama-index-integrations/llms/llama-index-llms-azure-inference/tests/test_llms_azure_inference.py#L19

@john0isaac can you verify if you are using the latest version of the library? Because I checked and I happen to added a test for this case and I see it passing.
https://github.com/santiagxf/llama_index/blob/729d5f2e76cca29284157c6fd8b55fb9953739dd/llama-index-integrations/llms/llama-index-llms-azure-inference/tests/test_llms_azure_inference.py#L19

I am using the latest version, It seems weird that some functions work and others don't.
See the ones I listed up there.
Btw it's starting to make sense to me there are two attributes in the AzureAI Class one called model_name and another called _model_name and you never assign the init model_name to _model_name
And in the metadata you are checking for the _model_name not the model_name

Good point. That's the fix then. I need to wrap that on a try/except in case the endpoint doesn't support metadata retrieval. We will bring support soon to the GH endpoint though. I'll follow up by tomorrow on it.

@john0isaac can you help me validate if the following branch solves the issue?
https://github.com/santiagxf/llama_index/tree/santiagxf/azure-ai-inference-gh
You can install with pip install git+https://github.com/santiagxf/llama_index.git@santiagxf/azure-ai-inference-gh#subdirectory=llama-index-integrations/embeddings/llama-index-embeddings-azure-inference

sure, I'm not sure are you intentionally doing this or not.
You never pass in the initializer model_name to the private _model_name
if you just pass the value in the init it's gonna solve the issue.
But sure I will test what you did.

Using your branch, I receive these warning which I was receiving when I didn't follow my workaround:
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for event.span_id='AzureAICompletionsModel.complete-2c97c998-908b-494a-b91f-ddbce575792f', event.id_=UUID('15b072f0-94b7-4ae9-90da-63a3a903cc3c')
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for event.span_id='AzureAICompletionsModel.chat-691b82de-3e49-4084-83d2-b0d220b2fcea', event.id_=UUID('048349d3-b65f-4b94-bbc5-7c821ac53a41')
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for event.span_id='AzureAICompletionsModel.chat-691b82de-3e49-4084-83d2-b0d220b2fcea', event.id_=UUID('bb31a2eb-2842-4c0f-aa25-330193571b4c')
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for id_='AzureAICompletionsModel.chat-691b82de-3e49-4084-83d2-b0d220b2fcea'
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for event.span_id='AzureAICompletionsModel.complete-2c97c998-908b-494a-b91f-ddbce575792f', event.id_=UUID('ff6c9138-aced-4057-9956-4dc22752ee57')
WARNI [openinference.instrumentation.llama_index._handler] Open span is missing for id_='AzureAICompletionsModel.complete-2c97c998-908b-494a-b91f-ddbce575792f'

And I get these new errors resulting from the code that you changed:
{
	"name": "AttributeError",
	"message": "'ChatCompletionsClient' object has no attribute 'endpoint'",
	"stack": "---------------------------------------------------------------------------
HttpResponseError                         Traceback (most recent call last)
File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/llms/azure_inference/base.py:288, in AzureAICompletionsModel.metadata(self)
    285 try:
    286     # Get model info from the endpoint. This method may not be supported by all
    287     # endpoints.
--> 288     model_info = self._client.get_model_info()
    289 except Exception:

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/core/tracing/decorator.py:94, in distributed_trace.<locals>.decorator.<locals>.wrapper_use_tracer(*args, **kwargs)
     93 if span_impl_type is None:
---> 94     return func(*args, **kwargs)
     96 # Merge span is parameter is set, but only if no explicit parent are passed

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/ai/inference/_patch.py:660, in ChatCompletionsClient.get_model_info(self, **kwargs)
    659 if not self._model_info:
--> 660     self._model_info = self._get_model_info(**kwargs)  # pylint: disable=attribute-defined-outside-init
    661 return self._model_info

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/core/tracing/decorator.py:94, in distributed_trace.<locals>.decorator.<locals>.wrapper_use_tracer(*args, **kwargs)
     93 if span_impl_type is None:
---> 94     return func(*args, **kwargs)
     96 # Merge span is parameter is set, but only if no explicit parent are passed

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/azure/ai/inference/_operations/_operations.py:558, in ChatCompletionsClientOperationsMixin._get_model_info(self, **kwargs)
    557     map_error(status_code=response.status_code, response=response, error_map=error_map)
--> 558     raise HttpResponseError(response=response)
    560 if _stream:

HttpResponseError: (no_model_name) No model specified in request. Please provide a model name in the request body or as a x-ms-model-mesh-model-name header.
Code: no_model_name
Message: No model specified in request. Please provide a model name in the request body or as a x-ms-model-mesh-model-name header.

During handling of the above exception, another exception occurred:

AttributeError                            Traceback (most recent call last)
Cell In[17], line 1
----> 1 summarize_query_engine = summary_index.as_query_engine(
      2     llm=llm,
      3     response_mode=\"tree_summarize\",
      4     use_async=True,
      5 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/indices/base.py:411, in BaseIndex.as_query_engine(self, llm, **kwargs)
    404 retriever = self.as_retriever(**kwargs)
    405 llm = (
    406     resolve_llm(llm, callback_manager=self._callback_manager)
    407     if llm
    408     else llm_from_settings_or_context(Settings, self.service_context)
    409 )
--> 411 return RetrieverQueryEngine.from_args(
    412     retriever,
    413     llm=llm,
    414     **kwargs,
    415 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/query_engine/retriever_query_engine.py:110, in RetrieverQueryEngine.from_args(cls, retriever, llm, response_synthesizer, node_postprocessors, response_mode, text_qa_template, refine_template, summary_template, simple_template, output_cls, use_async, streaming, service_context, **kwargs)
     88 \"\"\"Initialize a RetrieverQueryEngine object.\".
     89
     90 Args:
   (...)
    106
    107 \"\"\"
    108 llm = llm or llm_from_settings_or_context(Settings, service_context)
--> 110 response_synthesizer = response_synthesizer or get_response_synthesizer(
    111     llm=llm,
    112     service_context=service_context,
    113     text_qa_template=text_qa_template,
    114     refine_template=refine_template,
    115     summary_template=summary_template,
    116     simple_template=simple_template,
    117     response_mode=response_mode,
    118     output_cls=output_cls,
    119     use_async=use_async,
    120     streaming=streaming,
    121 )
    123 callback_manager = callback_manager_from_settings_or_context(
    124     Settings, service_context
    125 )
    127 return cls(
    128     retriever=retriever,
    129     response_synthesizer=response_synthesizer,
    130     callback_manager=callback_manager,
    131     node_postprocessors=node_postprocessors,
    132 )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/core/response_synthesizers/factory.py:74, in get_response_synthesizer(llm, prompt_helper, service_context, text_qa_template, refine_template, summary_template, simple_template, response_mode, callback_manager, use_async, streaming, structured_answer_filtering, output_cls, program_factory, verbose)
     68     prompt_helper = service_context.prompt_helper
     69 else:
     70     prompt_helper = (
     71         prompt_helper
     72         or Settings._prompt_helper
     73         or PromptHelper.from_llm_metadata(
---> 74             llm.metadata,
     75         )
     76     )
     78 if response_mode == ResponseMode.REFINE:
     79     return Refine(
     80         llm=llm,
     81         callback_manager=callback_manager,
   (...)
     91         service_context=service_context,
     92     )

File ~/Developer/azureai-x-arize/.venv/lib/python3.10/site-packages/llama_index/llms/azure_inference/base.py:291, in AzureAICompletionsModel.metadata(self)
    288     model_info = self._client.get_model_info()
    289 except Exception:
    290     logger.warning(
--> 291         f\"Endpoint '{self._client.endpoint}' does support model metadata retrieval. \"
    292         \"Failed to get model info for method `metadata()`.\"
    293     )
    294     self._model_name = \"unknown\"
    295     self._model_provider = \"unknown\"

AttributeError: 'ChatCompletionsClient' object has no attribute 'endpoint'"
}

missed the action i'll catch up on your branch i hope

@Josephrp @john0isaac fixed the error. Can you please take a look again?

This issue has been fixed in the following PR: https://github.com/run-llama/llama_index/pull/15747. Please update to llama-index-llms-azure-inference>=0.2.2


Creating my post for my final app

But I still need reflection which I am working on in another text editor and will paste here.

All done.
Ready to :goat: (my new favorite pun)

I'll send out more personalized feedback and a grade to you directly, but wanted to get a few comments to you now.  Congrats on being the first one done! 🚀


[Bug] Crafting Recipes with STAPI are broken

Craft anything while STAPI is installed, and it causes a crash, plus HMI doesn't display recipe.
I think the best solution is if possible, try to use STAPI recipe event to add recipes after adding to a recipe array.

Fixed by https://github.com/thecatcore/Apron/commit/e7c9bc8d81dd69ecc920596d59682a870164d4c3


Support new format on info fields in clinvar vcf

Differences
CLNSIG=5; vs CLNSIG=Pathogenic; (code vs text)
CLNACC=RCV000132731.1 vs * missing * (missing)
CLNDBN=Smith-Magenis_syndrome; vs CLNDN=Smith-Magenis_syndrome; (different tag)
Latest clinvar
ALLELEID=152915;
CLNDISDB=MedGen:C0795864,OMIM:182290,Orphanet:ORPHA819,SNOMED_CT:401315004;
CLNDN=Smith-Magenis_syndrome;
CLNHGVS=NC_000017.10:g.17698535G>A;
CLNREVSTAT=no_assertion_criteria_provided;
CLNSIG=Pathogenic;
CLNVC=single_nucleotide_variant;
CLNVCSO=SO:0001483;
GENEINFO=RAI1:10743;
MC=SO:0001587|nonsense;
ORIGIN=32;
RS=527236033
Working (on production) clinvar
RS=527236033;
RSPOS=17698535;
dbSNPBuildID=141;
SSR=0;
SAO=3;
VP=0x050060000605000002110100;
GENEINFO=RAI1:10743;
WGT=1;
VC=SNV;
PM;
NSN;
REF;
ASP;
LSD;
OM;
CLNALLE=1;
CLNHGVS=NC_000017.10:g.17698535G>A;
CLNSRC=.;
CLNORIGIN=32;
CLNSRCID=.;
CLNSIG=5;
CLNDSDB=MedGen:OMIM:Orphanet:SNOMED_CT;
CLNDSDBID=C0795864:182290:ORPHA819:401315004;
CLNDBN=Smith-Magenis_syndrome;
CLNREVSTAT=no_criteria;
CLNACC=RCV000132731.1

Here is another example of the new version.  Notice that there are still | to delimit different conditions
ALLELEID=102081;
CLNDISDB=MedGen:CN169374|MedGen:CN517202;
CLNDN=not_specified|not_provided;
CLNHGVS=NC_000017.10:g.17700043_17700045delGAG;
CLNREVSTAT=criteria_provided,_conflicting_interpretations;
CLNSIG=Conflicting_interpretations_of_pathogenicity;
CLNSIGCONF=Benign(2),Likely_benign(3),Uncertain_significance(1);
CLNVC=Deletion;CLNVCSO=SO:0000159;
CLNVI=HGMD:CD116392;
GENEINFO=RAI1:10743;ORIGIN=1;RS=149716029

Model new vcf parsing after SampleModel._addClinvarEutilInfoToVariant

clinvar uuid needs to come from id column in vcf rec
take out temp vcf
code and
try with ftp vcf

Using VCF rather than EUTILS, results in clinvar entry when it looks like it is for another allele:

Hi Al.  I’m mystified by the coordinates in the clinvar entry: https://www.ncbi.nlm.nih.gov/clinvar/variation/96187/
ncbi.nlm.nih.gov
NM_030665.3(RAI1):c.3781_3783delGAG (p.Glu1261del) Simple - Variation Report - ClinVar - NCBI
ClinVar archives and aggregates information about relationships among variation and human health.
According to ClinVar, here are the GRCh37 coords - Chr17: 17700043 - 17700045 (on Assembly GRCh37)
But look at the ClinVar vcf:
17    17700037    96187    AAGG    A
Al [1:27 PM]
That’s less than ideal
I’m on the train, but I’ll take a look when I get in. Seems really odd
tonydisera [1:28 PM]
The starting position in the ClinVar vcf seems right to me.  17700037.  Why could the ClinVar web interface show at start position at 17700043?
Thanks.  I know you can help me unravel this.  I’m scratching my head…
Al [1:30 PM]
I’m not I’ll be able to help, but two sets of eyes are often better than one!!
Al [2:08 PM]
Ok, so this can be even more exciting
I looked on dbSNP
Screen Shot 2018-10-30 at 4.08.57 PM.png
So there it is listed as 17700038. Different again
Ok, so here are some thoughts
This is the genome browser view of this region
Screen Shot 2018-10-30 at 4.14.37 PM.png
So it looks to me that 17:17,700,037 is the first A at the left. The variant is a deletion of GAG, and the ClinVar variant you listed is deletion of AGG
So, I agree with you that 17:17,700,037 is the starting location for the deletion of AGG
But that ClinVar page is showing deletion of GAG
In a VCF, we would then set the coordinate to be the anchor base to the left of the GAG, so we should see a ref allele of GGAG going to G at position 17:17,700,039
But, ClinVar lists it at 17:17,700,043 and this actually makes sense to me
An annoying feature is that we always left align indels in a VCF. So, in this case, the sequence has GAG followed by GAG. So technically, it is equivalent to claim either the first or second GAG is repeated
For a VCF, we left align, so would delete the first GAG and list the coordinate as one base to the left of the first G
HGVS codes obviously, to maximise confusion, right align, so they would delete the last (e.g. second) repetition of GAG
This would mean bases 17:17,700,043 to 17:17,700,045 are deleted
As listed in ClinVar
This is super confusing
ClinVar points to dbSNP and this is the 1000G browser
https://www.ncbi.nlm.nih.gov/variation/tools/1000genomes/?gts=rs149716029
The highlighting shows the second GAG deleted, but in the table shows the allele as AAGG, consistent with the deletion of AGG
So there seems to be some real confusion surrounding what is actually deleted here
Al [2:50 PM]
@tonydisera
tonydisera [2:51 PM]
Hi!
Wow.  Thanks for the research!  I will try to digest your analysis.  Thank you.  This is very confusing.
Al [2:52 PM]
The key thing here which is super annoying is that VCF spec is left align and HGVS is right align
That means that when we have a deletion in a repeat region, when we convert to HGVS coordinates, we are guaranteed to be wrong
tonydisera [2:52 PM]
Oh!  I see.

Al [2:53 PM]
I know. Literally the dumbest thing in the world
tonydisera [2:53 PM]
But what is weird is this clinvar del seems like an outlier.  The others are showing as left aligned.
Al [2:53 PM]
Do you have other examples?
tonydisera [2:54 PM]
I will try to look at some more.
Thank you for your explanation.  This is very confusing.
Al [2:54 PM]
Yeah, but I'm glad you uncovered this
http://varnomen.hgvs.org/recommendations/DNA/variant/deletion/
The several nucleotides example states you take the most 3' representation
This is only important with repeats, e.g. TTTTTTTTCAGCAGCAGTTTTTTTT
HGVS includes the coordinates of the deleted bases. VCF gives the position of the base to the left of the deleted bases
tonydisera [3:01 PM]
Would you mind a zoom call at some point to talk about this?

Added #274 to address issue with RAI deletion showing a ClinVar entry when pointed to ClinVar vcf that doesn't show when using ClinVar eutils.

I think this is fixed


[SR-10317] Generated xcodeproj should set MACOSX_DEPLOYMENT_TARGET according to Manifest

Previous ID
SR-10317

Radar
None

Original Reporter
matthew_seaman (JIRA User)

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s
Package Manager

Labels
Bug

Assignee
None

Priority
Medium

md5: e45d538de4c8c01eefb21e9ba493c70a

Issue Description:
MACOSX_DEPLOYMENT_TARGET in generated Xcode projects should be set to the minimum macOS version in "platforms" in the Manifest, if applicable. Right now, it is set to 10.10.
This may not be high priority since each individual target has its deployment target properly set.

@tomerd this can be closed since generate-xcodeproj has been removed.


Minor release 2.0.8 breaks library built with 2.0.1

On instantiating FasterLog I get this exception:
    System.MissingMethodException: Method not found: 'Void FASTER.core.FasterLog..ctor(FASTER.core.FasterLogSettings)'.

this is part of my code (was built with v2.0.1 under .NET 6.0):
    public FasterChannel(string deviceLogPath) {
      _device = Devices.CreateLogDevice(deviceLogPath);
      _log = new FasterLog(new FasterLogSettings { LogDevice = _device });
    }

When I replace FASTER.core.dll with the original version 2.0.1 the exception goes away.
Looks like it binds to a method signature that went missing, because the signature with the optional parameter is not the same as the one without.

Thanks for the report. Currently we do not guarantee binary compatibility of releases; you will probably need to rebuild. We will update this in the future if our release cadence changes.


fix(chat): remove dotes from unnecessary parts (Issue #2356)

Description:
Need to remove ... from the 'See all addons...' , 'Continue review...' and 'Go to a review'
Issues:

Issue #2356

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review


Starting today, Next.js deployed with amplify is showing an internal server error

We have the same issue. Tried downgrading Next.js version, but that did not help.
Tried the following:
export NEXT_PRIVATE_STANDALONE=true
npm run build

cp -r .next/static .next/standalone/.next/static
cp -r public .next/standalone/public

node .next/standalone/server.js
It runs successfully locally, but not when deployed to Amplify Hosting.

Same test and same results as @espenbye.

What's your package manager ? Using pnpm with symlinks broke our apps. We're now using another mode to avoid symlinks as a hot fix #3467

This appears to be a duplicate of #3466. Please continue any further engagements on that issue. We will provide an update there shortly. Thank you for your patience!


Create admin page to propose new challenge

For admin only, there should page a where admin can prepare the next week challenge. It would be something like a blog. Also have the ability to add new section apart from the fixed sections.
Checkout the current format:
https://theweeklychallenge.org/blog/perl-weekly-challenge-259/

I would like to work on this issue, please assign it to me

@soniyaprasad77 Done. Good luck and all the best.

I believe the functionality to add new challenges should be present on the admin's dashboard. ( Also have the ability to add new section apart from the fixed sections. ) Additionally, there should be a section on the admin's dashboard that provides access to another page specifically designed for creating new challenges.
Do you agree with this? For that, I have to work on the dashboard first! i.e issue #136

@soniyaprasad77 Feel free what makes more sense to you. For admin dashboard, it is going to be loaded as compare to logged user dashboard as you can imagine.
On admin dashboard, it should have square box like tile where each tile would for one task. For example, Any new comments by user that needs approval. Adding new challenge for coming week. Fixing typo to an existing challenge. Approving new member request. Remove member from mailing list. Create mailing list of active members. The list will go on as we progress.

I appreciate the clarification, and the information now has greater clarity for me. Thank you :)

can i show the performance metrics something like this :

In our case , we can show the reviewers count and guest users count and challenge participation, completion rates, and user engagement.

@soniyaprasad77 SRS looks perfect to me.


input  base on some field value

function Form(props) {
var objBarCode;
if (props.record && props.record.type === "STOCK") {
objBarCode = ;
}
return (
<SimpleForm {...props}>

<SelectInput
source="type"
label="Type"
validate={[required]}
choices={[
{ id: "STOCK", name: "Stock" },
{ id: "RMK", name: "Remark" },
{ id: "SVR", name: "Services" }
]}
/>
{objBarCode}

);
}
hi,how to achieve something like this??which some input are only appear by some conditions, the above code does not rerender when the condition value change , the goal was the Textinput Bar Code  only appear when type="STOCK"

We don't provide support through GitHub issues. If you need advice on using or debugging your own project based on admin-on-rest, please use StackOverflow.


drivers other than IOS?

What else needs to be installed to support drivers other than IOS? like EOS?
python get_l3_facts.py -H switch1.lab --driver eos
No handlers could be found for logger "pyeapi.eapilib"
Traceback (most recent call last):
File "get_l3_facts.py", line 174, in
main()
File "get_l3_facts.py", line 154, in main
args.ssh_config,
File "get_l3_facts.py", line 22, in open_device
device.open()
File "/usr/local/lib/python2.7/dist-packages/napalm/eos/eos.py", line 169, in open
raise ConnectionException(py23_compat.text_type(ce))
napalm.base.exceptions.ConnectionException: Socket error during eAPI connection: [Errno 111] Connection refused
if I switch the driver to IOS, it mostly works, except that it's an arista switch, so it's not quite happy either.
get_l3_facts - [1 / 1]: Opening connection to sw1.lab
get_l3_facts - [1 / 1]: Getting interface facts
get_l3_facts - [1 / 1]: Found 0 addresses
get_l3_facts - [1 / 1]: Closing connection to sw1.lab
get_l3_facts - Found 0 addresses total
get_l3_facts - Saving results to l3_facts.csv
Traceback (most recent call last):
File "get_l3_facts.py", line 174, in
main()
File "get_l3_facts.py", line 169, in main
save_csv(args.csv_path, results)
File "get_l3_facts.py", line 73, in save_csv
with open(csv_path, "w", newline="") as f:
TypeError: 'newline' is an invalid keyword argument for this function
Ideas?

Looks like we need to retool the args passed to napalm in open_device() based on --driver. We need to specify port and we don't need to pass ssh_config. See this example. I may be able to look into it, or you can submit a PR.

Using --driver eos works for me just fine. From the looks of the last pyeapi error, do you have the management api enabled?
management api http-commands
no shutdown


relationship between "abolished mitotic sister chromatid separation" and metaphase/anaphase

FYPO:0001946	abolished mitotic sister chromatid separation
and
abnormal cell cycle arrest at mitotic metaphase/anaphase transition
?
Its true I guess, but in this case I think we would want to record what we see if that is
abolished mitotic sister chromatid separation
I presume its has_output
abnormal cell cycle arrest at mitotic metaphase/anaphase transition
If so, I think we need to reconsider whether we still see these as suggestions, because we wouldn't really be capturing what we saw.
I think I have  another ticket about this issue, so I'll see if its the same relation as this one, and we can make a decision based on this.

The link is has_part. Can you ever get arrest at the metaphase/anaphase transition but still have chromatid separation happen? I thought not, so I included the link.
I suspect has_output would also agree with biology (i.e. arrest has_output abolished separation, not the other way round), and might even be a bit better.
If you can have metaphase/anaphase arrest but still get some chromatid separation, then I'll have to just delete the link.

I'm now not sure how we could separate these 2 terms.
I would use
FYPO:0001946 abolished mitotic sister chromatid separation
if NO separation was detected (i.e chromosomes were condensed, but cells were still in metaphase , i.e the APC was never activated)
I would use
"abnormal cell cycle arrest at mitotic metaphase/anaphase transition"
in exactly the same circumstances, I think.  (i.e chromosomes were condensed, but cells were still in metaphase , i.e the APC was never activated)
I'm going to check what the phenotypes look like for these 2 terms.

this is the phenotype for
abnormal cell cycle arrest at mitotic metaphase/anaphase transition
you could also easily also make the annotation
abolished mitotic sister chromatid separation any time you saw this?

However, we also have a term
"abolished rDNA separation"
I don't know if this means that only the rDNA fails to separate.

So in summary, its all OK isn't it!
abnormal cell cycle arrest at mitotic metaphase/anaphase transition
is the best term to use, because this will always be annotated to
abolished mitotic sister chromatid separation
I think it might be useful just to add a comment to
Definition: "A cellular process phenotype in which progression through the mitotic cell cycle is arrested at the metaphase/anaphase transition under conditions where arrest does not normally occur." [
that NO chromosome separation occurs in this phenotype.

Over in #2580 we've decided FYPO:0000392 gets the ax, so I've made changes for this ticket to FYPO:0000620. Added a comment and the link FYPO:0000620 has_output FYPO:0001946.

edit file: 138d806d362c771009d917f669073b54cb4452af
release: 0c9f107ee56df966ee46641cac1897aa7fa31157


Rename test files to be unique

Currently most of the test files have identical names to other files in the project which is generally considered bad practice. It makes the project harder to navigate and talk about, as well as running the risk of compilation errors with name clashes
Various options for naming the test files, I've gone for a common one that seems to make sense: if X.cpp contains the code for X then XTests.cpp contains the code for X's tests

SFMLBuildMaster: Build this please.

which is generally considered bad practice

I've never heard this.

It makes the project harder to navigate and talk about

I think it makes the project easier to navigate since it takes zero brainpower to know what file contains the tests for a given header.

as well as running the risk of compilation errors with name clashes

There is no way this is true. Even if we were globbing source files this would still not be true,

I'm indifferent to this, but how about using the .t.cpp suffix instead of repeating Tests for each filename?

@thr

How could the current name scheme cause compilation issues? We explicitly tell CMake what files to build. There is no ambiguity in the current naming convention.

For what it's worth, those two C++ project structure conventions suggest .test.cpp extension. I am not aware of other documented C++ project structure conventions.

The Pitchfork Layout
Canonical Project Structure

In addition, they suggest putting unit test files next to the files under test (referenced to as "merged test placement").

How could the current name scheme cause compilation issues? We explicitly tell CMake what files to build. There is no ambiguity in the current naming convention.

Because the output of compilation may go to the same directory

I would prefer @kimci86's suggestion of X.test.cpp

I would also rather add this extension than add a Tests suffix to the filename.

Renamed and rebase

All Debug CI jobs failed due to network error in Codecov, I restarted them.

SFMLBuildMaster: Build this please.

Bump

Thanks for the small enhancement!


Task :react-native-google-fit:compileDebugJavaWithJavac FAILED

I upgraded to 0.16.1 and now while I'm trying to run the project but I'm getting those issues:
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:78: error: cannot find symbol
                .read(DataType.TYPE_SLEEP_SEGMENT)
                              ^
  symbol:   variable TYPE_SLEEP_SEGMENT
  location: class DataType
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:77: error: cannot find symbol
                .includeSleepSessions()
                ^
  symbol:   method includeSleepSessions()
  location: class Builder
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:84: error: cannot find symbol
                        .addDataType(DataType.TYPE_SLEEP_SEGMENT, FitnessOptions.ACCESS_READ)
                                             ^
  symbol:   variable TYPE_SLEEP_SEGMENT
  location: class DataType
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:134: error: cannot find symbol
            sleepStage.putInt("sleepStage", dp.getValue(Field.FIELD_SLEEP_SEGMENT_TYPE).asInt());
                                                             ^
  symbol:   variable FIELD_SLEEP_SEGMENT_TYPE
  location: class Field
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:148: error: cannot find symbol
                .setDataType(DataType.TYPE_SLEEP_SEGMENT)
                                     ^
  symbol:   variable TYPE_SLEEP_SEGMENT
  location: class DataType
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:162: error: cannot find symbol
                            .setField(Field.FIELD_SLEEP_SEGMENT_TYPE, stage.getInt("sleepStage"))
                                           ^
  symbol:   variable FIELD_SLEEP_SEGMENT_TYPE
  location: class Field
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:170: error: cannot find symbol
                .addDataType(DataType.TYPE_SLEEP_SEGMENT, FitnessOptions.ACCESS_WRITE)
                                     ^
  symbol:   variable TYPE_SLEEP_SEGMENT
  location: class DataType
/Users/***/node_modules/react-native-google-fit/android/src/main/java/com/reactnative/googlefit/SleepHistory.java:169: error: cannot find symbol
                .accessSleepSessions(FitnessOptions.ACCESS_WRITE)
                ^
  symbol:   method accessSleepSessions(int)
  location: class Builder
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
8 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-google-fit:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

I've already cleaned build, Gradle, node_modules and don't know what to do next

which react-native version do you use? Do you use react-native link on this package in the past? I believe this kind of problems always come from your android build gradle setting.

RN version is 0.63
No, I chose manual installation
I was trying to update package since play beta demanding targetSdkVersion starting from 29 and  app crashes on getting steps count because of missing permission of activity_recognition

Can you paste your build.grade setting?

apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
apply plugin: "com.android.application"
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: "com.google.firebase.firebase-perf"

import com.android.build.OutputFile

project.ext.react = [
    entryFile: "index.js",
    enableHermes: false,  // clean and rebuild if changing
]

rootProject.ext.set("authVersion", "18.0.0")
rootProject.ext.set("fitnessVersion", "18.0.0")

apply from: "../../node_modules/react-native/react.gradle"
apply from<EMAIL_ADDRESS>

def enableSeparateBuildPerCPUArchitecture = false

def enableProguardInReleaseBuilds = false

def jscFlavor = 'org.webkit:android-jsc:+'

def enableHermes = project.ext.react.get("enableHermes", false);

android {
    compileSdkVersion rootProject.ext.compileSdkVersion

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    defaultConfig {
        applicationId "app.id"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 63
        versionName "1.1.2"
        multiDexEnabled true
    }
    signingConfigs {
        debug {
            if (project.hasProperty('DEVELOPMENT_KEYSTORE_FILE')) {
                storeFile file(DEVELOPMENT_KEYSTORE_FILE)
                storePassword DEVELOPMENT_KEYSTORE_PASSWORD
                keyAlias DEVELOPMENT_KEY_ALIAS
                keyPassword DEVELOPMENT_KEY_PASSWORD
            }
        }
        staging {
            if (project.hasProperty('STAGING_KEYSTORE_FILE')) {
                storeFile file(STAGING_KEYSTORE_FILE)
                storePassword STAGING_KEYSTORE_PASSWORD
                keyAlias STAGING_KEY_ALIAS
                keyPassword STAGING_KEY_PASSWORD
            }
        }
        release {
            if (project.hasProperty('PRODUCTION_KEYSTORE_FILE')) {
                storeFile file(PRODUCTION_KEYSTORE_FILE)
                storePassword PRODUCTION_KEYSTORE_PASSWORD
                keyAlias PRODUCTION_KEY_ALIAS
                keyPassword PRODUCTION_KEY_PASSWORD
            }
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
    buildTypes {
        debug {
            debuggable true
            signingConfig signingConfigs.debug
        }
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
        staging {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            matchingFallbacks = ['release']
            signingConfig signingConfigs.staging
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // https://developer.android.com/studio/build/configure-apk-splits.html
            def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    implementation project(':react-native-google-fit')
    apply from: "../../node_modules/react-native-vector-icons/fonts.gradle"
    implementation 'com.facebook.android:facebook-android-sdk:[5,6)'

    implementation fileTree(dir: "libs", include: ["*.jar"])

    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation 'androidx.appcompat:appcompat:1.1.0-rc01'
    if (enableHermes) {
            def hermesPath = "../../node_modules/hermes-engine/android/";
            debugImplementation files(hermesPath + "hermes-debug.aar")
            releaseImplementation files(hermesPath + "hermes-release.aar")
        } else {
            implementation jscFlavor
        }

}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply plugin: 'com.google.gms.google-services'
apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)

defaultConfig {
    minSdkVersion rootProject.ext.minSdkVersion
    targetSdkVersion rootProject.ext.targetSdkVersion
}

I believe it comes from your android/build.grade

buildscript {
    ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 27
        compileSdkVersion = 29
        targetSdkVersion = 29
        androidXCore = "1.0.2"
    }
    repositories {
        maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
        mavenCentral()
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.2'
        classpath 'com.google.gms:google-services:4.3.2'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.2.0'
        classpath 'com.google.firebase:perf-plugin:1.2.1'
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.6, 0.99.99]'
    }
}

allprojects {
    repositories {
        mavenLocal()

        maven {
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        maven {
            url("${project(':react-native-background-fetch').projectDir}/libs")
        }
        google()
        jcenter()
        maven { url 'https://jitpack.io' }
    }
}

Here it is. I changed only compileSdkVersion and targetSdkVersion.

I just upgrade my build.gradle setting like yours, and did not see any build script problem except the permission.Activity_recognition on runtime, I believe this is due to the Google Policy changes and it can be solved by request permission manually by yourself.

Same  issue  here  any solution  so far ?

I resolved the compiling issue by removing fitnessVersion = "18.0.0"
But I m facing a crash when trying to get steps
I'm using react-native 0.63 and react-native-google-fit 0.16.1

I resolved the compiling issue by removing fitnessVersion = "18.0.0"
But I m facing a crash when trying to get steps
I'm using react-native 0.63 and react-native-google-fit 0.16.1

It seems like you all have some own configurations. Notice that if you want to upgrade something please try to read through the commits. I remember the set fitness version is a "temporary" hot fix when googlefit decided to drop some deprecated codes🤔. And you shouldn't upgrade packages if it works fine since the version is fixed. Google fit will further drop some deprecated codes based on its recent updates.
The new functionalities introduced some new types that are not available from old fitness version. So your fitness version might want to match specific  package version that you are using currently.
It's obvious that we can write some code to make version compatibility, but then the codebase will be a mess. Idk

This is because you should have fitness version 20.0.0 to run this library. I think this can be added to Documentation. Check out the release notes from here to find out what's changed. https://developers.google.com/android/guides/releases

This is because you should have fitness version 20.0.0 to run this library. I think this can be added to Documentation. Check out the release notes from here to find out what's changed. https://developers.google.com/android/guides/releases

@ensargunesdogdu  good point, I can add it later. If developers does not hard set fitness version in their own apps, They  wouldn't have the problem. Ppl who encountered the similar issues was because they followed the temp solution in the past when google decided to drop some deprecated codes, which it's fixed later but they did not remove the temp version.

@ensargunesdogdu  good point, I can add it later. If developers does not hard set fitness version in their own apps, They  wouldn't have the problem. Ppl who encountered the similar issues was because they followed the temp solution in the past when google decided to drop some deprecated codes, which it's fixed later but they did not remove the temp version.

Same issue as --> https://github.com/StasDoskalenko/react-native-google-fit/issues/206#issuecomment-765308172
Getting below error:
Cannot resolve symbol 'TYPE_SLEEP_SEGMENT'
But here:
https://developers.google.com/fit/datatypes/sleep
Data type object | TYPE_SLEEP_SEGMENT
Mentioned in the DOC.
Any Solution?

@StasDoskalenko I faced with the same error but I didn't hardcode google fit version in by app/buildGradle file. Adding
rootProject.ext.set("authVersion", "18.0.0") rootProject.ext.set("fitnessVersion", "20.0.0")
helped me

Fixed by add
buildscript {
    ext {
        buildToolsVersion = "29.0.3"
        minSdkVersion = 21
        compileSdkVersion = 29
        targetSdkVersion = 29

        authVersion = "18.0.0"
        fitnessVersion = "20.0.0"
    }
    ...
}

to android/build.gradle


Add DataMasking swagger and examples

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 3
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 3
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 3
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 3
Thanks for your co-operation.

@jianghaolu we've completed our internal review and checks are passing - could you please have a look?  Thanks!

Test comment

For some reason github is not letting me reply to comments right now.
I see the you also have api-version 2015-05-01-preview. Is this feature not available in that api-version ?

Correct, it is not available on that version.

minor: Although we not using tags directly but we'd prefer to keep tag as the same as NOUN part of the operationId. like here Databases

For singleton resources, the pattern we've been told to use has been to set tags to the singleton resource, but have the operation id use the ParentResource_ListSingletonResource pattern.
See https://github.com/Azure/azure-rest-api-specs/blob/master/arm-sql/2014-04-01/swagger/sql.core.json#L977 and https://github.com/Azure/azure-rest-api-specs/blob/master/arm-sql/2014-04-01/swagger/geoBackupPolicies.json#L24

Feel free to refactor this parameter to a global parameter section to avoid repetition.

Is there any reason for not including default response code for any operations here?

Is this required now?  We have it auto-generated in 2015-05-01-preview to document our error values, but we're actually fine with just passing through the error message and code coming from the API directly.

Just making sure here: This is not a long running operation. Right?

Right.

why no default response? Ref: https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/creating-swagger.md#DefaultResponse

Is this required now?  We have it auto-generated in 2015-05-01-preview to document our error values, but we're actually fine with just passing through the error message and code coming from the API directly.

Should this be named as Databases_ListByDataMaskingPolicy ?

I don't think so.  That would imply we're listing databases by data masking policy.  There's only one policy, and this is a child resource of that singleton, so Databases_ListDataMaskingRules makes the most sense.

Otherwise the client would look like this client.DataMaskingRules.ListByDataMaskingPolicy("myrg", "myserver", "mydb"), but with no policy name, because policy name is always "default."  That's a bit confusing.
Is this readOnly i.e server populated property?

Yes.  Fixed.

Do service still returns this property on GET call?

Yes, unfortunately.

minor: two spaces between state. and Also

k

Do we have any default value for enum?

Behavior of this property is in the description.

Do we have any default value for enum?

No, and it is required on every PUT.

why not integer/number?

It is returned as a string by the API.

minor: 2 spaces between string. & Otherwise is unnecessary. Please format the file with one space

k

should this be integer as description suggest a potential number

The description already says this property is a number

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Before the PR: Warning(s): 0  Error(s): 0
After the PR: Warning(s): 2  Error(s): 1
Thanks for your co-operation.

@vishrutshah
Regarding this question:  Should this be named as Databases_ListByDataMaskingPolicy ?
What if we did DataMaskingRules_CreateOrUpdate and DataMaskingRules_ListByDatabase?  Again, since the dataMaskingPolicy is singleton, it might be confusing the client to make it ListByDataMaskingPolicy and not require a DataMaskingPolicy name in the client parameters.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-sql/2014-04-01/swagger/dataMasking.json
Before the PR: Warning(s): 0  Error(s): 0
After the PR: Warning(s): 2  Error(s): 1
Thanks for your co-operation.

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-python

 https://github.com/Azure/azure-sdk-for-ruby/pull/810

@vishrutshah Thanks, Vishrut!


peview.exe not found

I tried x64 Dependencies, but right-click->View Module in Peviewer tells me peview.exe not found.

Did you download the v1.8 : https://github.com/lucasg/Dependencies/releases/tag/v1.8 ?
I've checked any of the zipped binary packages (Debug/Release, and x86/x64) and peview.exe is present in it.
Alternatively, you can set peview.exe (or any PE analyzer) path in the settings window.

Yes, I downloaded 1.8. And ran it on Windows 10 x64. You can see in one of the screenshots that peview.exe is present in my unzipped folder, but DependenciesGui.exe just doesn't find it (same problem with the x86 version).
Great tool, by the way.

There was actually a typo in the default settings. This commit fix it : https://github.com/lucasg/Dependencies/commit/c1a748afc4efbe556ab350f240492a94303a6fb7.


Repository Topics

Hello!
Would it be possible to add the commonly used bannerlord topics bannerlord, bannerlord-mod and mount-and-blade-bannerlord for the repo?
Thanks!

Done! :)


TabView in title bar of window below buttons to minimize, maximize and close the window

Describe the bug
When you want to use TabView control in combination with ExtendViewIntoTitleBar, the tabs are visible underneath the window controls
Steps to reproduce the bug
Follow the guidelines in the docs or see the "Complete TabView windowing sample" in XAML Controls Gallery app.
Expected behavior
TabView should not show up underneath the window controls
Screenshots

Version Info

NuGet package version:
Microsoft.UI.Xaml 2.4.3

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

May 2020 Update (19041)
Yes

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

@stmoy Is this a scenario we actively support/encourage? I know that in the case of the XAML Controls Gallery, that sample has multiple problems which are on our side (i.e. XAML Controls Gallery, not WinUI side).

I think this is useful to support. It's convention now to extend into the title bar even with tabbed interfaces like this example. It should be possible to at least set a custom margin to push the tab headers out from under the window buttons.

You can put content inside the TabStripFooter, e.g. an empty Grid occupying the necessary space to achieve the necessary padding. The question is if there should be a separate API here, similar to the NavigationView.IsTitlelBarAutoPaddingEnabled.

Ah, yes, I forgot about how the NavigationView automatically handles this. It would be great for the TabView to do the same. Both of these controls have evolved into a fundamental layout of applications and should support this scenario the same way.

Is this a scenario we actively support/encourage?

Yes, this is a "mainline" scenario. It's pretty gnarly to get right though...
Resizing the window fixes this issue. I'm not sure if this is a XCG bug or a Title bar bug - it seems like the latter to me especially since there is code to handle this case.

I don't think this is an issue with title bar, the values get passed to the TabView correctly, yet we can end up in that bad state. This is an issue with TabView not responding to the size changes of the TabFooter content. The root cause of this is this line:
https://github.com/microsoft/microsoft-ui-xaml/blob/8c8f29cbf8b6e30e3f26ba208d6d4f44fe26a7ca/dev/TabView/TabView.xaml#L37
Quite frankly, I am not quite sure what the best approach to fixing this would be, @teaP @stmoy @StephenLPeters What do you think?

@stmoy Regarding the mainline scenario, do you think the current way to support this is sufficient (by allowing to add the necessary spacing through the TabFooter) or should we have a separate API that would add the necessary padding automatically? NavigationView also has something similar where it changes the header position to not occlude content.

Regarding the mainline scenario, do you think the current way to support this is sufficient (by allowing to add the necessary spacing through the TabFooter) or should we have a separate API that would add the necessary padding automatically? NavigationView also has something similar where it changes the header position to not occlude content.

The TabFooter spacing isn't optimal, no. I think TabView often takes up the entire window, so this scenario should probably be better supported. Using NavigationView as a precedent for a new API makes sense to me. In the short term, though, it might be faster to fix the bug you highlighted above rather than introducing a new API...

does nav view really have an API to handle this? I would imagine it being more automatic than that

There is the IsTitleBarAutoPaddingEnabled API, which updates the padding on some parts. Having this automatic is very difficult, since that would require some way to reliably detect whether or not the control is the root and is affected by the custom titlebar behavior or not.


Integrate with existing worker code?

How can I integrate this to an existing worker? That is, I'm already able to fetch and return a complete HTML document. But I'd like to use HTMLRewriter to append some HTML to the document. I can't quite figure it out from the getclaps example -- everything seems to be based around using the HTMLResponse function.

everything seems to be based around using the HTMLResponse function.

Yes that is correct. This library isn't really intended to work with HTMLRewriter. As a workaround you could use something like
await new HTMLResponse(html`...`).text()


[Bug/Feature]: Problems importing from JabRef

Debug log ID
D435554656.
What happened?
Good morning,
I work as a researcher in history and for a long time I have been using the JabRef program for my bibliographic database. I recently started using Zotero, given the dynamism of that program.
I imported my database from JabRef and everything seemed to work fine, until I realized that certain entries weren't working in Zotero.
The fact is that, for the construction of bibliographies with primary sources, JabRef allows you to create custom bibliography types that allow you to cite unpublished or daily documents. I created a type in JabRef (Periodical) that has worked perfectly for me. However, Zotero is unable to import it and consequently I am unable to use those entries.
Zotero gives me an import error, which I'll pass on immediately.
here the Zotero's error
Don't know what Zotero type to make of 'periodical' for @BolLegi186672, importing as document
Here the JabRef Citation
https://github.com/periodical{BolLegi186672,
journal = {Legislative and Official Bulletin 1866-1872},
title = {{{\normalfont A.N.H. -- Legislative and Official Bulletin}}},
year = {1866},
number = {Series 1a, No. 1},
month = {02},
address = {Tegucigalpa},
keywords = {Newspapers},
}

Best regards,A bug happened!

I can work with the sample you gave.

closing for inactivity


[PlutusTx.Ratio]: Added INLINABLE pragmas to recip, fromInteger, toGHC, fromGHC

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

Summary
Some exported functions do not have a pragma INLINABLE:

recip
fromInteger
toGHC
fromGHC
As a result, they may not be possible to use in on-chain code.

For these INLINABLE pragma has been added.

Removed pragmas from functions toGHC and fromGHC. So we can just add pragmas to the other two.

Thanks!


Only send BTCUSD offers via /itchysats/offer/1.0.0

Fixes https://github.com/itchysats/itchysats/issues/2817 (maybe).
The taker listening for /itchysats/offer/1.0.0 can only handle BTCUSD offers, so anything else leads us to "undefined" behaviour.

bors retry

bors retry

bors cancel

bors thank you


Add missing Blizzard hostnames

When using this i found Battle.net would half use my cache and half download from their servers. After adding these two entries which i found on other DNS Caches for blizzard the problem was resolved.

You have referenced /var/lib/bind/db.blizzard in cache.conf. This file doesn't exist, the file is located in at /etc/bind/cache/blizzard/db.blizzard as the lines above which you added state.
We don't require forwarders in named.conf.options, bind will query root servers for information for anything it isn't hosting.
Thanks for the information regarding the blizzard domains, I have added these with commit bd07788