Require Python 3.7+ / drop support for older versions

vncdotool currently still supports Python 2.7, which is end-of-life since 3 years in a few months.
Also all versions of Python 3.0 up to and including to 3.6 are end-of-life.
Python 3.7 reaches end-of-life in half a year: 2023-06-27
See https://devguide.python.org/versions/

tox.ini is still using py35
.travis.yml is still using 2.7 and 3.5
setup.py ony lists Programming Language :: Python :: 3 but no individual versions.
requirements-dev.txt and requirements.txt seem to lock some old versions; maybe by design to support some older versions, but updating them might be worhwile.

Because of the Python 2.7 support there is still some compatibility code left to handle the bytes / unicode differences, which could be removed if Python 2.7 support was dropped, especially all that ord() handling #219.  That would simplify some code paths and would also simplify adding PEP-484 type annotations (I have a local branch where I already started this.)
What are your plans regarding

removing tox.ini
replacing nosetest
removing Travis-CI support
removing Circle-CI support
removing Python 3.6 and older support
adding type annotations

PS: Some function tests use a tool called vncev, which I could not find. What is that and where can I get it?

I think it's time to retire 2.7 support.  I'd kept it pass EOL as I knew there are users on platforms that are still using 2.7.

tox.ini, not thought about.
I've started removing nosetests and non-std mock.
Travis CI has got to go
CircleCI, could go.  I don't know if it'll be easier to make the intergration tests work on GH Action vs Circle.  That is probably the only reason to keep Circle around.
All EOL python should be dropped
On type annontations, I'm not sure.  I'm not a fan but I've not used them.  I'd be open to looking at a PR and if its not too "noisy" include them.  If there is other value for static analisys or similar I could be convinced.

vncev is an example program from https://github.com/LibVNC/libvncserver.  I use it for intergration testing, but never figured out a good way to build and test it using CI.  I usually do a manual run before packaging a release.

Thank for the information. I have a local branch here which

drops support for Python 2.7 and before 3.7
adds type annotations (supported since Python 3.5 resp. Python 3.6)
rips out all that ord() / chr() handling as Python 3.0 works with bytes already¹
converts string formatting to f-string (available since Python 3.6+)

Currently that branch also has many more changes. I can either try to separate those changes into multiple commits, but that will take some time and even go to waste when you squash my branch into yours. Some things are even hard to separate as they depend on each other, but I tried to do that anyway.
I'll send you a PR to get your feedback.

keep it in one PR, it's mostly mechanical and shouldn't require too much to figure out.


Why OAuth?

Why would one use OAuth for a desktop app? You have nowhere to hide the client secret so in the end everyone can access your users.
Do I get something wrong here?

It seems that Google recommends some workflows to make it work:
https://github.com/googlesamples/oauth-apps-for-windows/tree/master/OAuthDesktopApp

OAuth2 cleate a private unique token per user on device, this token could be detached from the account without change your password and prevent save password on app


No issue : Just a question

Hi;
First of all, thanks a lot for the amazing job you have made with this project!
I have a question, I can see a folder called "WindowsOnly" in the project NP.Ava.Visuals.
Does your lib works on Linux & Mac too?
(I have only Windows to try it)

As far as I remember you do not have to worry about it. It should work at least on linux. Try it using Oracle VM Virtual Box and tell me if it works. Not 100% sure about Mac, I do not have a mac machine to test it on at this point.

Hello;
Thank you for your answer, I will try it this following week for Mac and come back to you with the answer.
Have a great Sunday ))

Hi @npolyak I took the liberty to add you to my private and new repo, I just uploaded your solution.
I created a project called AvaloniaFutures on it and used your examples to start my trading desktop project.
Also, I've upgraded the Docking components from Avalonia 11.0.6 to 11.0.1


Docs CI Build Should Run On Release Completion

The docs team maintains an alternate webhook host than the standard azure devops. As a result, we have a prebuilt way to trigger individual CI builds within the Content CI devops project.
Example for Java:
<webhookurl>/api/webhooks/incoming/github?path=PROD%5CGitHub_Azure_azure-docs-sdk-java&name=Azure_Azure-sdk-for-java-CI
Need to add a notification to the above url in the release process after we post to the package manager.

[ ] .NET
[ ] Python
[ ] Javascript
[ ] Java
[ ] C

Here's the key, we need to trigger the appropriate CI for the packages that were onboarded. New Preview? Should trigger the PREVIEW CI. Otherwise trigger PROD.
I figure if we need to automate this for legacy, we can begin comparing the version outgoing to the versions that were already present. If OLDER than a an existing release, should trigger the legacy pipeline.
I will work with Robert Outlaw to get the appropriate secret into our keyvault.

The Docs CI (created by OPS) pipelines run nightly against the master branch. To publish the updates today, one must open a PR merging changes from the master branch into the live branch.

The Docs CI (created by OPS) pipelines run nightly against the master branch. To publish the updates today, one must open a PR merging changes from the master branch into the live branch.

We're doing this in docindex for nightly doc releases. Onboarding is also updated for preview and latest monikers as part of this build. With automated onboarding running daily we effectively have accomplished the goal of this issue.


eo3  执行sh generate.sh出错 出现G2O_SOLVER_CHOLMOD     linked by target "ygz-util" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/util

eo3  执行sh generate.sh出错 出现2O_SOLVER_CHOLMOD
linked by target "ygz-util" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/util
linked by target "ygz-common" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/common
linked by target "ygz-cv" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/cv
linked by target "ygz-backend" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/backend
linked by target "MakeSceneEurocStereoVIO_ros" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/examples
linked by target "EurocStereo" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/examples
linked by target "EurocStereoVIO_ros" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/examples
linked by target "Kitti" in directory /home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/examples
-- Configuring incomplete, errors occurred!
See also "/home/champossion/soft/GAAS/software/SLAM/ygz_slam_ros/build/CMakeFiles/CMakeOutput.log".
make: *** No targets specified and no makefile found.  Stop.

这是我在github上见过最长的issue标题了

Please confirm that g2o is installed correctly(e.g. have you executed make install), and have you install the dependencies correctly mentioned in the [GAAS tutorial 3].(https://gaas.gitbook.io/guide/software-realization-build-your-own-autonomous-drone/build-your-own-autonomous-drone-part-3-using-slam-in-gps-denied-environment-for-position-estimation)

Please confirm that g2o is installed correctly(e.g. have you executed make install), and have you install the dependencies correctly mentioned in the GAAS tutorial 3.


[BUG] Error with the only video instagram picker

Describe the bug
In your demo, specifically in the instagram selector, if you configure that only videos are shown and only one video can be chosen at most. In the preview it does not change for the selected video, it stays in the default video.
How to reproduce
There is the instagram picker like your demo but configured to only show videos and select max 1 video.
Steps to reproduce the behavior:

With the code, launch the picker
Then select one video
You'll see that the preview doesn't change for the selected video.
Error occurred.

Expected behavior
When the user selects the video, it is displayed in the preview.

Please provide a minimal code example that highlighted your changes rather than a bunch of code which is not helpful to determine what is the cause. cc @LeGoffMael

Hello! The code of instagram picker is the same. The only change is the next code:
  late final DefaultAssetPickerProvider provider = DefaultAssetPickerProvider (       maxAssets: 1,       requestType: RequestType.video,   );

I can reproduce the issue, i will look into it.
It seems that the video preview is not updated well.

Thank you! I'll wait.

The issue seems to be coming from VideoPageBuilder @AlexV525.
When the asset param is updated the state doesn't rebuild.
Adding didUpdateWidget fix this issue, but iCloud videos causes an exception.
@override
void didUpdateWidget(covariant VideoPageBuilder oldWidget) {
  // update current page when index is updated
  if (widget.asset != oldWidget.asset) {
    _isInitializing = false;
    _isLocallyAvailable = false;
    hasErrorWhenInitializing = false;
  }
  super.didUpdateWidget(oldWidget);
}

Verify if #417 resolves the issue.

PR has been updated, please verify the issue again.

It seems that both issues remains, after iCloud download, the video preview is not shown and there is still the same exception on the same video.

Sorry I haven't got time to investigate this recently due to the limited time, please do further digging about this if you're interested, thanks!

Hi can this feature will be fixed, it's a must to have option:( ...thanks in advance!

It seems that both issues remains: after iCloud download, the video preview is not shown and there is still the same exception on the same video.

Is this happening when using the default viewer?


chore: update information_schema to note catalog is now supported

Originally noted in https://github.com/tconbeer/harlequin/issues/89

Thanks, @Mause !


Support relations in result extensions

Problem
At the moment, only scalar fields are allowed to be specified in needs block of result extension. This is by design — since we include computed fields into the default selection, we can't automatically fetch nested relations for performance reasons. However, there are many legit use-cases for using relations inside of computed fields.
Suggested solution
Relation fields should be allowed in needs block. In case computed field depends on relation, it should not be fetched automatically and require explicit include or select:
const xprisma = prisma.$extends({
    result: {
      user: {
        bestPost: {
          needs: { posts: true },
          compute(user) {
            return findBestPost(user.posts)
          },
        },
      },
    },
  })

// does not include `posts` relation or `bestPost` computed field
const user1 = await xprisma.user.findFirst()

// includes `bestPost` computed field
const user2 = await xprisma.user.findFirst({ include: { bestPost: true } })

Closing https://github.com/prisma/prisma/issues/19548 in favor of this

My current workaround (which is not very clean imo) is this:
type UserExtended = {
    id: string;
    posts: Post[];
};
const prisma = new PrismaClient().$extends({
    result: {
        user: {
            bestPost: {
                needs: {id: true},
                compute(user: UserExtended) {
                    if (user.posts) {
                        return findBestPost(user.posts);
                    }
                    return undefined;
                },
            },
        },
    },
});

At least it's type safe and works for my use case 👍

My current workaround (which is not very clean imo) is this:
type UserExtended = {
    id: string;
    posts: Post[];
};
const prisma = new PrismaClient().$extends({
    result: {
        user: {
            bestPost: {
                needs: {id: true},
                compute(user: UserExtended) {
                    if (user.posts) {
                        return findBestPost(user.posts);
                    }
                    return undefined;
                },
            },
        },
    },
});

At least it's type safe and works for my use case 👍

It looks typesafe for sure. But does it work on runtime?

It's weird but you can even put the relation in the needs object and it'll actually work and infer the type - but you need to ts-ignore the needs object or you'll get Type 'boolean' is not assignable to type 'never'
return new PrismaClient().$extends({
    result: {
      user: {
        bestPost: {
          // @ts-ignore
          needs: { posts: true },
          compute(user) {
            if (!user.posts || foo.posts[0].some_needed_value !== undefined) {
              return null;
            }

            return findBestPost(user.posts);
          },
        },
      },
    },
  });

Now if you include the relation posts when getting user:s then bestPost is properly set.
The only problem here is that if you only select a subset of the columns from the posts relation then those needed to compute the bestPostproperty may not be included so you need to explicitly check that anything you use is not undefined. The typescript type will not help as it'll be the complete model. So it's not entirely type safe but if you're careful it seems to work.

Syntax suggestion to keep in line with other methods:
Selects the entire posts row, but no relations:
bestPost: {
  needs: { posts: true },
  compute(user) {
    return findBestPost(user.posts)
  },
},

Selects only the specified fields:
bestPost: {
  needs: {
    posts: {
      title: true,
      likes: true
    }
  },
  compute(user) {
    return findBestPost(user.posts)
  },
},

Selects the entire posts row, but no relations:
  needs: {
    posts: {
      title: true,
      likedBy: {
        name: true
      }
    }
  },
  compute(user) {
    return findBestPost(user.posts)
  },
},

How should this handle N:M and 1:N relations?

Just chiming in to help upvote this.

I would like to add another aspect to this conversation. A solution should also be able to access extended fields. Or is this even possible. My use case is the following: I am computing a user friendly label for some tables. Purpose of this is to have an id/label pair for autocomplete fields. Each object can have a different composition for a label. Extensions are great for this. Now my problem is that I would like to generate a label, where I would like to use the label of a relation.
author: {
    label: {
        needs: { firstname: true, lastname: true },
        compute(author) {
            return `${author.firstname} - ${author.lastname}`
        },
    }
},
post: {
    label: {
        needs: { date: true, title: true, author: true },
        compute(post) {
            return `${post.title} - ${post.author.label}`
        },
    }
}

It's weird but you can even put the relation in the needs object and it'll actually work and infer the type - but you need to ts-ignore the needs object or you'll get Type 'boolean' is not assignable to type 'never'
const prisma = new PrismaClient().$extends({
    result: {
      user: {
        bestPost: {
          // @ts-ignore
          needs: { posts: true },
          compute(user) {
            if (!user.posts || foo.posts[0].some_needed_value !== undefined) {
              return null;
            }

            return findBestPost(user.posts);
          },
        },
      },
    },
  });

Now if you include the relation posts when getting user:s then bestPost is properly set.
The only problem here is that if you only select a subset of the columns from the posts relation then those needed to compute the bestPostproperty may not be included so you need to explicitly check that anything you use is not undefined. The typescript type will not help as it'll be the complete model. So it's not entirely type safe but if you're careful it seems to work.

@nejsimon it seems that once I add the relation field into needs, then it breaks the type of the result itself, i.e. at the calling site
const user = await prisma.user.findFirst({
  { include: { posts: true } },
});
const post = user.bestPost; // this line no longer compiles

And that's the same case when using user.bestPost with and without {include: { posts: true }} in the query.
Is that also your experience? This is on the newest 5.17.0 for @prisma/client


ng-repeat not clearing table

Why is the table not cleared on model change when using ng-repeat?
If i change the array to a new array, it just appends the new entries without clearing the table first.
Am i doing something wrong, is this a feature or a bug?
See this pen for example: http://codepen.io/jonasrafn/pen/EgYkjw

got same issue

have found out that it s a known bug with no current solution. But there is a work around instead of using mdt-row directive use the mdt-row attribute on mdt-table directive.
See this codepen for example: http://codepen.io/jonasrafn/pen/ZpzoZq
And documentation here: https://github.com/iamisti/mdDataTable#table-attributes

How is this a solution?
I don't see a way of being able to inject HTML into a cell using this.

@JonasRafn is there possible to filter in mdt-rows?


Add auto-generate sample for ManagedServices and ManagementPartner

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Upgrade dependencies and switch from alga to simba

The alga crate is deprecated and has been replaced by simba.  This PR also allows the introduction of a much newer nalgebra version which is pretty significant.
Depends on https://github.com/hmeyer/bbox/pull/3 for now, after which the [patch] section will be removed

Build currently fails with this PR. Can you please take a look?

Hey! I'll work on fixing the PR! It would help a little bit if the new bbox version was released to crates.io so I can get this PR ready in one go

The issue is that the normal bbox dependency is set to 0.11 but my patched repo version contains version 0.12 (since you asked me to bump to that version as part of the PR), which means that cargo considers the patch to be incompatible with the normal dependency.
The fix is to remove the patch and select bbox = "0.12.0"  and this PR will start succeeding.  But, that requires the bbox dependency on version 0.12.0 to be released first.


fix SQL toolkit table listing tool name

Description: This PR fixes the erroneous naming convention of the list_tables_sql_db tool used for querying the list of tables present in a database. This is a minor fix which renames all the occurrences of the above tool with the one described in the tool's description.
Issue: Fixes #7440
Dependencies: None
Maintainer: @hinthornw

@hinthornw seems spark sql tool already has this name, should we rename the spark one to indicate it's spark?

@baskaryan Should there be 2 separate tools for the same job?

@baskaryan FYI ^

Closing because the PR wouldn't line up with the current directory structure of the library (would need to be in /libs/langchain/langchain instead of /langchain). Feel free to reopen against the current head if it's still relevant!


Add Chapel as a supported third-party language

Resolves #2800
Changes
This adds an entry for the Chapel language, giving chapel and chpl as its two aliases, and pointing to our repo at https://github.com/chapel-lang/highlightjs-chapel.
Checklist

[x] Added markup tests, or they don't apply here because they're in our repo
[ ] Updated the changelog at CHANGES.md
[ ] Added myself to AUTHORS.txt, under Contributors

[Note: I haven't done the last two items because it's not clear to me whether they apply to something as minor as adding a new third-party language to the list.  Please let me know]

I dunno about authors (I won't stop ya, but I've never really thought about it), but you can definitely add an entry to the changelog if you'd like!

@joshgoebel: I added a CHANGES.md entry as suggested.  I skipped the AUTHORS.md update, but can do it if you prefer.  Let me know if there are any other changes required before this is merged (Travis testing is still pending as I write this).
[Also, in other news, I successfully got our Discourse site using Chapel highlighting even without this being merged which I consider a major win]

Thanks Josh!


Tests fail while running a lot of them together

When running a folder with a lot of test cases the runner fails with the following error:
/playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:452
                        rootSuiteName = parentSuiteObj.rootSuite;
                                                       ^

TypeError: Cannot read properties of undefined (reading 'rootSuite')
    at RPReporter.<anonymous> (/playwright/node_modules/@reportportal/agent-js-playwright/src/reporter.ts:475:42)
    at step (/playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:60:23)
    at Object.next (/playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:41:53)
    at /playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:35:71
    at new Promise (<anonymous>)
    at __awaiter (/playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:31:12)
    at RPReporter.onTestEnd (/playwright/node_modules/@reportportal/agent-js-playwright/build/reporter.js:413:16)
    at /playwright/node_modules/@playwright/test/lib/reporters/multiplexer.js:69:131
    at wrap (/playwright/node_modules/@playwright/test/lib/reporters/multiplexer.js:111:5)
    at Multiplexer.onTestEnd (/playwright/node_modules/@playwright/test/lib/reporters/multiplexer.js:66:45)
    at Dispatcher._reportTestEnd (/playwright/node_modules/@playwright/test/lib/dispatcher.js:556:186)
    at Worker.onTestEnd (/playwright/node_modules/@playwright/test/lib/dispatcher.js:234:12)
    at Worker.emit (node:events:526:28)
    at ChildProcess.<anonymous> (/playwright/node_modules/@playwright/test/lib/dispatcher.js:610:12)
    at ChildProcess.emit (node:events:526:28)

When running the tests individually, so such error occurs.
My playwright.config.ts:
const { devices } = require('@playwright/test');
import { PlaywrightTestConfig } from '@playwright/test';

// /** @type {import('@playwright/test').PlaywrightTestConfig} */
const RPconfig = {
    'token': 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
    'endpoint': 'https://<report-portal>/api/v1',
    'project': 'projname',
    'launch': 'Playwright Runner Test',
    'description': 'Tests with Playwright Runner',
  };

const config: PlaywrightTestConfig = {
    reporter: [['@reportportal/agent-js-playwright', RPconfig]],
    forbidOnly: !!process.env.CI,
    retries: process.env.CI ? 2 : 0,
    use: {
        trace: 'on-first-retry',
    },
    workers: 2,
    projects: [
        {
        name: 'chromium',
        use: { ...devices['Desktop Chrome'] },
        }
    ],
    timeout: 30 * 10000,
};

module.exports = config;

package.json:
{
  "name": "playwright",
  "version": "1.0.0",
  "description": "Dependencies and Report Portal integration information to run Playwright Test scripts",
  "main": "index.js",
  "scripts": {
    "test": "npx playwright test --config=playwright.config.ts"
  },
  "license": "ISC",
  "dependencies": {
     "@playwright/test": "^1.20.1",
    "concurrently": "^6.3.0",
    "playwright-chromium": "^1.18.0",
    "@reportportal/agent-js-playwright": "^5.0.2"

  }
}

Any help will be appreciated!
Cheers!

Hello @chaitanya-uc !
Have you tried latest released 5.0.3 version?

Hey @AmsterGet The latest 5.0.3 version has been installed on my system.

Hello @chaitanya-uc ,
Could you share your folders structure for tests and the structure of the test example inside the file?

@oranje322 Hey!
My folder structure is as follows:
/playwright
---playwright.config.ts
---package.json
---node_modules/
---tests/
------test_cases_1/
---------test1.spec.js
---------test2.spec.js
------test_cases_2/
---------test1.spec.js
---------test2.spec.js

Each of the test_cases_1 folders has sub-folders with test cases for different scenarios. In total I have 100 individual .spec.js files under the test_cases_n folders.
Sorry I didn't get what you meant by test example inside the file.
My tests basically opens up a chromium browser and fills some data in my CRM and validates the fields which gets updated.

test.describe structure inside test file.
How many nested describe block you have in tests with errors?

When running the tests individually, so such error occurs.

Do you mean "no such error occurs?"

Do you mean "no such error occurs?"

Sorry it's supposed to be no. Fixed it.

How many nested describe block you have in tests with errors?

I have only 1 describe block per file.

The problem is caused by using the same file names.
Will be fixed in the next version.

The problem is caused by using the same file names. Will be fixed in the next version.

The fix was released in version 5.0.4 https://github.com/reportportal/agent-js-playwright/pull/49


Does SQL Parameter supports "IN"?

Does the SQL parameter support "IN"?  If yes, can we add an example?
The use case is
SELECT * FROM c WHERE c.attribute IN ('value1', 'value2')

https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-keywords#in
Parameter values can be any valid JSON: strings, numbers, Booleans, null, even arrays or nested JSON. Since Azure Cosmos DB is schemaless, parameters aren't validated against any type.

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

ID: d4787bd5-5e70-c491-0772-5158de8b8624
Version Independent ID: cb34b3f3-4dcb-0c98-ace5-1da73b2259bc
Content: Parameterized queries in Azure Cosmos DB
Content Source: articles/cosmos-db/sql-query-parameterized-queries.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @timsander1
Microsoft Alias: tisande

Hello @jeffpeiyt,
Thank you for your feedback! We will review and update as appropriate.

https://stackoverflow.com/questions/60933325/how-to-create-the-sqlqueryspec-in-java-in-order-to-retrieve-a-list-of-documents resolves the issue. Consider add it to the doc so that it saves people 4 hours on trying and googling.


CRM Runbook updates

Wove in the following:

Mention that it's a SaaS product (aka hosted in cloud)
Data aggregated is public
Who has access to data

I believe that's all that was requested in this interaction

@saad-ali @alena1108 -- for TOC liaison approval.
ref: https://cloud-native.slack.com/archives/CT6CWS1JN/p1642020336006700?thread_ts=1642019879.005600&cid=CT6CWS1JN


Added non-generic DeclareSignal overload

I required a way of inserting dynamic type information when declaring signals.

Thanks


Carbon selection style and color

UX to investigate the most appropriate selection styling and color for all data points and graph types.
Include before and after colors.

Use Terra selection colors. The selection should surround the icon, not just be centered within the gantt row for gantt charts.

@laurenbock Can you elaborate on using Terra colors?

Triaging old issues. Has this been resolved outside of this discussion thread?

@jeremyfuksa I missed this one - no it has not been resolved yet. We need to darken the selection state colors in Carbon. I proposed using Terra's colors so that it was consistent and would pass contrast. However, I know there are more than one set of selection colors right now in Terra. Is there one that you'd recommend that is the safest to use?

It's difficult to give a definitive answer since the display criteria are different given the context of the component. However, from a contrast and consistency standpoint, the focus state of pagination might be a suitable style: https://zpl.io/Vq1GqkJ

@jeremyfuksa  I do like that style as it is similar to Carbon today, but I want to check because it doesn't look like the blue passes contrast - is this ok with accessibility?

It wouldn't. Pagination has a number of accessibility issues that are being worked on, it turns out. So my recommendation is not good. The closest color would be #1B9ADF, which is just off @blue60, since it doesn't pass WCAG standards either.
TL;DR: I need to find time to return to my color study that tweaks our color palette for better accessibility.

@laurenbock @jeremyfuksa  So apparently way back in the day I did some update on the selection color - take a look and let me know your thoughts around it. I can continue the exploration if needed.
SelectionState.pdf

@erinplourde I like the approach.

that's really helpful to see, @erinplourde!
@jeremyfuksa do you know the answers to any of the questions in red? I do not - I wonder if Scott would be best to ask (i know he is out on sabbatical atm, though)

Does the selection color need to meet 3:1 to more than just the white background?

Since data points could potentially sit on axis lines, it should. The example in the PDF fails at 2.47:1 on the gray line.

Are the colors bright enough to differential between our palette blues? Currently the new selection blue is close to the dark blue and could cause some worry with bubble and gantt charts - This needs to be looked at.

I think so. So, in order to reach contrast, tweaking the saturation just a bit should get you there. #148bcc looks pretty good and meets contrast. It should also be saturated enough to not compete with the dark blue.

Does our selection colors match with terra selection colors?

They aren't exact at the moment, but they are close. I've been working on unifying the palette a little more on and off over the past year. Once that gets nailed down, we can enhance Carbon's palette to be aligned with whatever we come up with.,

H, @jeremyfuksa / @sdadn, Is there an ETA on this issue. We have a consumption Jira being logged for this.
Thanks,
Joel

@joelsamthomas Sorry, I don't think we have any update on this issue right now as we just migrated Carbon to a new repository and are currently catching up on fixing bugs.

@joelsamthomas Sorry, I don't think we have any update on this issue right now as we just migrated Carbon to a new repository and are currently catching up on fixing bugs.

Let's move this issue over to the new repo and use my suggested color of #148bcc as the fix.


feat: UpperCamelCase naming convention for generated types

Fix #39
See dis-rs/build.rs for more information

@zlubsen Can you try to compile cdis-gateway since I don't have bun installed on my system.
Thanks 🥳

There is a test that fails in the cdis-assemble crate. If you change the pull request to target the development branch that should be fixed.
(The idea is that main contains the latest released version. The development branch is where changes are made to the code. Development is merged into main when a new release is made. Should write that down somewhere...)
Otherwise, the change is working good. The resulting names look much better.

The changes are merged into the development branch, all occurrences in cdis-assemble are fixed.


domain is not defined

In lib/middleware/connect.js, domain isn't defined and a ReferenceError is thrown. It appears that it's not available as a global, and must be require'd.
v0.8.0 on io.js 2.3.0

Ugh. One sec. Fixing.

@dhritzkiv Sorry about that, 0.8.1 pushed.


BUG: Remove unused test when setting suffixes

This commit partially reverts 775776e (ENH: Initialize default list of suffixes) removing unused test when setting the suffix variable.
It also ensures there are no duplicated prefixes.

@dave3d  This is ready for review and integration. Thanks for your time :pray:


Two Errors in GoogleWebAuthorizationBroker.AuthorizeAsync on Google Calendar .NET Example

I have a Problem connecting my .NET C# Application with Google Calendar using the Google.Apis.Calendar.v3 NuGet Package.
If I use the Code provided by the .NET example given by Google, I get two errors.
The example on the Google page: https://developers.google.com/calendar/quickstart/dotnet
The error occurred in the following code section after authenticating on the opened web page.
credential = GoogleWebAuthorizationBroker.AuthorizeAsync(GoogleClientSecrets.Load(stream).Secrets, Scopes, "user", CancellationToken.None, new FileDataStore(credPath, true)).Result;
Error One:

InvalidOperationException: The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set.

Error Two:

ArgumentException: '"UTF-8"' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

Full Code:
https://pastebin.com/1v7C3s66
The Application also creates a folder named token.json and not a token json file.
Is this the problem?
What should I do?

I have the same problem with the token.json file not created (only a directory). My code runs ok in Windows 7 but in Windows 10 the token.json file is not created. I don't know if the OS version is the problem here.

With an update of the Google API the error resolved.


Export browser-friendly JS files

Currently, the commonjs export produces the following export at the end:
module.exports = { main: () => main_1394().run() };

Unfortunately, browsers use a completely different module system so this produces a crash at runtime (as module doesn't exist).
Alternative 1
Let's hot-fix that by generating the following export (or a similar one) which works both in a browser and in Node.JS:
(typeof module != 'undefined' && module !== null ? module : {}).exports = $MODULE_NAME = {
  main: () => main_1435().run()
}

[where $MODULE_NAME is the name of our module]
Here's the code that would need to be changed:
https://github.com/effekt-lang/effekt/blob/6f8973ae77e4962b67b3cb626142fab7430a6cd8/effekt/shared/src/main/scala/effekt/generator/js/Tree.scala#L46-L48
Alternative 2
Let's use ES modules instead! They have been stable for about 15 years by now and work both in a browser and in Node*.
This way, we could also get rid of the following hack:
https://github.com/effekt-lang/effekt/blob/6f8973ae77e4962b67b3cb626142fab7430a6cd8/effekt/js/src/test/scala/effekt/WebTests.scala#L29-L34
*The only issue is that for Node.JS, all of our files would have to have the .mjs extension...

For context: at some point we generated several different module formats (which is the reason why this is still called commonjs
https://github.com/effekt-lang/effekt/blob/6f8973ae77e4962b67b3cb626142fab7430a6cd8/effekt/shared/src/main/scala/effekt/generator/js/Tree.scala#L33
It shouldn't be too hard to first hotfix and then implement Alternative 2.
It might also be relevant that the standalone compilation mode now is whole program. That is,  we do not generate separate files that need to be linked when compiling to JS. This is only enabled for the website.

Let's please implement Alternative 2 with .mjs file extensions.


Problems with raw_rnn with dynamic dimensions

I am trying to implement the pointing softmax in TF 1.1 and I am using raw_rnn but I get an error. Since is hard to explain the whole thing, here is how to reproduce it:
$ git clone https://github.com/petrux/LiTeFlow.git
$ cd LiTeFlow
$ git checkout broken
$ ./bin/py3venv.sh
$ source .py3venv/bin/activate
$ python3 -m unittest liteflow.tests.test_layers._TestSmoke

the error that I have is:
petrux@orion:~/Projects/LiTeFlow$ python3 -m unittest liteflow.tests.test_layers._TestSmoke
./usr/local/lib/python3.5/dist-packages/tensorflow/python/util/deprecation.py:212: DeprecationWarning: inspect.getargspec() is deprecated, use inspect.signature() instead
  arg_spec = inspect.getargspec(func)
/usr/local/lib/python3.5/dist-packages/tensorflow/contrib/keras/python/keras/backend.py:3593: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/petrux/.keras/keras.json' mode='r' encoding='UTF-8'>
  _config = json.load(open(_config_path))
/usr/local/lib/python3.5/dist-packages/tensorflow/contrib/labeled_tensor/python/ops/_typecheck.py:233: DeprecationWarning: inspect.getargspec() is deprecated, use inspect.signature() instead
  spec = inspect.getargspec(f)
elements_finished: Tensor("PointingDecoder_1_1/rnn/GreaterEqual:0", shape=(?,), dtype=bool)
next_cell_input: Tensor("PointingDecoder_1_1/rnn/concat:0", shape=(?, ?), dtype=float32)
next_cell_state: Tensor("GRUCellZeroState/zeros:0", shape=(?, 5), dtype=float32)
emit_output: Tensor("zeros:0", shape=(?, ?), dtype=float32)
next_loop_state: (<tf.Tensor 'PointingDecoder_1_1/rnn/LocationSoftmax_1/softmax/truediv:0' shape=(?, ?) dtype=float32>, <tf.Tensor 'PointingDecoder_1_1/rnn/LocationSoftmax_1/Sum:0' shape=(?, 4) dtype=float32>)

E
======================================================================
ERROR: test_smoke (liteflow.tests.test_layers._TestSmoke)
Build a pointer decoder and test that it works.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/array_ops.py", line 1356, in zeros
    shape = tensor_shape.as_shape(shape)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_shape.py", line 800, in as_shape
    return TensorShape(shape)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_shape.py", line 436, in __init__
    self._dims = [as_dimension(d) for d in dims_iter]
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_shape.py", line 436, in <listcomp>
    self._dims = [as_dimension(d) for d in dims_iter]
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_shape.py", line 378, in as_dimension
    return Dimension(value)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_shape.py", line 33, in __init__
    self._value = int(value)
TypeError: int() argument must be a string, a bytes-like object or a number, not 'Tensor'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/petrux/Projects/LiTeFlow/liteflow/tests/test_layers.py", line 518, in test_smoke
    output = decoder()
  File "/home/petrux/Projects/LiTeFlow/liteflow/layers.py", line 616, in __call__
    return super(PointingDecoder, self).__call__()
  File "/home/petrux/Projects/LiTeFlow/liteflow/layers.py", line 147, in __call__
    result = self._call_helper(*args, **kwargs)
  File "/home/petrux/Projects/LiTeFlow/liteflow/layers.py", line 610, in _call_helper
    outputs_ta, _, _ = tf.nn.raw_rnn(self._decoder_cell, self._loop_fn)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/rnn.py", line 965, in raw_rnn
    for size_i, dtype_i in zip(flat_emit_size, flat_emit_dtypes)]
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/rnn.py", line 965, in <listcomp>
    for size_i, dtype_i in zip(flat_emit_size, flat_emit_dtypes)]
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/array_ops.py", line 1359, in zeros
    shape = ops.convert_to_tensor(shape, dtype=dtypes.int32, name="shape")
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 639, in convert_to_tensor
    as_ref=False)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 704, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/array_ops.py", line 905, in _autopacking_conversion_function
    return _autopacking_helper(v, inferred_dtype, name or "packed")
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/array_ops.py", line 867, in _autopacking_helper
    constant_op.constant(elem, dtype=dtype, name=str(i)))
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/constant_op.py", line 102, in constant
    tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/tensor_util.py", line 360, in make_tensor_proto
    raise ValueError("None values not supported.")
ValueError: None values not supported.

----------------------------------------------------------------------
Ran 2 tests in 0.430s

FAILED (errors=1)

EDIT a working implementation is here.

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Cannot see whole sql query

Describe the bug
I cannot see whole sql query if query is too long.
Versions
Ray version 1.2.5
To Reproduce
Steps to reproduce the behavior:

Log a query with long parameters.

Expected behavior
Maybe adding horizontal scrolling into sql query area may fix this issue.
Screenshots

Desktop (please complete the following information):

OS: macOS
Version 11.1 (Big Sur)

Additional context
I can copy whole sql query into clipboard by clicking the copy button. It's working as expected.

Duplicate of https://github.com/spatie/laravel-ray/issues/77

Duplicate of https://github.com/spatie/laravel-ray/issues/77


Allow consumers of Compiler API to override getDirectoryToWatchFailedLookupLocation

🔍 Search Terms
getDirectoryToWatchFailedLookupLocation, watch, resolver, compiler API
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
Consumers of TypeScript's compiler API are typically in a better position to understand the nuances of the layout of the repository and take advantage of that knowledge to optimize file watcher performance than any generic implementation in TypeScript.
For large monorepos especially, TypeScript's implementation of getDirectoryToWatchFailedLookupLocation does not scale well and results in watching tons of excess files and directories.
If TypeScript were to access this method (and possible also getDirectoryToWatchFromFailedLookupLocationDirectory) via the CompilerHost interface (defaulting to the current implementation), consumers of the compiler API who work with customized file system layouts could better instruct the compiler on how to efficiently watch their filesystem. This would also help with exotic file system scenarios (e.g. network file systems, virtual filesystems).
The current method:
https://github.com/microsoft/TypeScript/blob/b258429aaaa6206fd5f911360b094ca626544ce9/src/compiler/resolutionCache.ts#L347C17-L394
📃 Motivating Example
I work in a large monorepo that has a small number of root folder (>1) and hundreds of projects under each root. Frequently projects under one root reference projects under another root, and under the default implementation this results in TypeScript watching hundreds of projects instead of the handful that are relevant to its execution.
On Linux especially, the decision to ask for a recursive watcher by default results in significant over-allocation of file and directory watchers, since the platform has no native support and therefore it results in allocating a non-recursive watcher for each and every directory in the tree.
💻 Use Cases

What do you want to use this for?

Integrating with Heft for use in Rush monorepos, particularly on GitHub codespaces (which are Linux-based)

What shortcomings exist with current approaches?

The current workaround is brittle and will need to be updated any time I update to a newer version of TypeScript.

What workarounds are you using in the meantime?

I have locally patched the installation of TypeScript in my monorepo to override this function with an alternative implementation that non-recursively watches the immediate parent folder of the failed resolution location.
diff --git a/lib/typescript.js b/lib/typescript.js
index fe732a6cb262712d4d79b917b7fa0f0eee9d58b4..e2534aa5dc62b7ea70b337687ed7d194b0ccf1e9 100644
--- a/lib/typescript.js
+++ b/lib/typescript.js
@@ -124353,6 +124353,13 @@ ${lanes.join("\n")}
     if (failedLookupPathComponents.length <= perceivedOsRootLength + 1)
       return void 0;
     const nodeModulesIndex = failedLookupPathComponents.indexOf("node_modules");
+
+    if (process.env.CODESPACE_NAME) {
+      // Hack to prevent excessive directory watching on Linux.
+      // In a Rush repo, the node_modules folder is considered immutable while running, so don't watch it.
+      // Linux does not support recursive watching, so always only watch the immediate parent folder.
+      return nodeModulesIndex >= 0 || failedLookupComponents.length < 3 ? void 0 : getDirectoryOfFailedLookupWatch(failedLookupComponents, failedLookupPathComponents, failedLookupComponents.length - 1, true);
+    }
     if (nodeModulesIndex !== -1 && nodeModulesIndex + 1 <= perceivedOsRootLength + 1)
       return void 0;
     if (isInDirectoryPath(rootPathComponents, failedLookupPathComponents)) {
@@ -124376,6 +124383,13 @@ ${lanes.join("\n")}
     );
   }
   function getDirectoryToWatchFromFailedLookupLocationDirectory(dirComponents, dirPathComponents, dirPathComponentsLength, perceivedOsRootLength, nodeModulesIndex, rootPathComponents) {
+    if (process.env.CODESPACE_NAME) {
+      // Hack to prevent excessive directory watching on Linux.
+      // In a Rush repo, the node_modules folder is considered immutable while running, so don't watch it.
+      // Linux does not support recursive watching, so always only watch the immediate parent folder.
+      return nodeModulesIndex >= 0 || failedLookupComponents.length < 3 ? void 0 : getDirectoryOfFailedLookupWatch(failedLookupComponents, failedLookupPathComponents, failedLookupComponents.length - 1, true);
+    }
+
     if (nodeModulesIndex !== -1) {
       return getDirectoryOfFailedLookupWatch(dirComponents, dirPathComponents, nodeModulesIndex + 1);
     }

@sheetalkamat thoughts?

Related #58866.

I think better approach is to handle this like in https://github.com/microsoft/TypeScript/pull/58866 than adding API for this as this is not just resolutionCache issues but also needs to handle closed script info's node_modules folder etc as well


static audio graph of 6 nodes, no sound, memory leak. code attached.

I've hit upon an odd situation that needs a few things to hit. In my experiemnts trying to figure out a fast growing memory issue that kills my app in 20 min or so.
I've attached the code (xcode 12.2 RC build) on simulator and device running 14.2 release build.
There was another mem leak on mixers etc on dynamic graph but this is a static graph with no changes. There's no sound playing and the app memory increases over time. The more complex the graph, the faster the leak.
I wanted to see if this is an apple or audiokit issue, but so far, i'm not sure, though given that there' no other report like this out there, could be v5 branch changes.
It's certainly an odd one. needs a few things happening that exacerbates it. I can't see the pattern. small changes to the graph and the memory doesn't leak. I have no insight in the deep down code that audiokit uses.
audiokit-leak-autoreleasepool.zip
    // This leaks memory in autoreleasepool. Lots of increasing
    //  AUAudioUnitV2Bridge_Renderer thingys, 4KB each,
    //
    // From my experimentation, these things are needed to make the memory leak happen:
    //  - mic input
    //  - setPreferredIOBufferDuration
    //  - 3 or more things in a chain
    // with a more complex graph, there's a much more severe leak. I've a graph that creates
    // a 1 MB per minute leak! The app dies in about 20 min.

I'm on the v5-develop branch btw.

I have downloaded and tried the project. I don't have an answer yet, but I wanted to extend the conversation with my observations.
When I view the app in the simulator and look at the memory usage, it does go up. If I put it through the Profiler for Memory leaks, there are a few but none of them seem AudioKit related per se:

They also happen exactly once at the beginning of the app but not again.
When I run the app on a device (iPhone X), the way the memory usage increase goes from being chunks every minute or so to a little bit all the time, linearly increasing.
When I profile the app on the device, the profile is showing zero memory leaks.
So I don't think the increase of memory usage is a leak per se.
You're right that all the memory is stuck in the autorelease pool:

We might have to make this happen with out AudioKit just using AVAudioEngine and then file a bug with Apple. This wasn't happening before AK5 so it still is probably our mistake somewhere.

We are seeing the same issue with AudioKit 4.11.2.

We are seeing the same issue with AudioKit 4.11.2.

@themichael123 Project link to it happening in 4.11.2 please.

@themichael123 Project link to it happening in 4.11.2 please.

@aure Please find a sample project attached.
AKTEST.zip
Thank you.

@aure Please find a sample project attached.
AKTEST.zip
Thank you.

No repro on iOS 14.5.1 / AK 5.1.

Had to comment out these lines for it to compile:
        Settings.audioInputEnabled = true
        Settings.defaultToSpeaker = true
        Settings.playbackWhileMuted = true
        Settings.allowAirPlay = true

Closing. Reopen if you can repro.


Upgrade the chromadb version to 0.4.8 and open its settings configuration.

Description

update the chromadb version to 0.4.8
allow user can set chromadb settings

Fixes #516
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[x] Unit Test
[ ] Test Script (please provide)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

@candidosales  @gasolin  please help to review 😊

Hey, I'm working on a refactor for the whole database and how it's configured. So I think we're going to have to work on some merge conflicts.

@cachho
Okay, if possible in the future, please provide a separate branch for refactoring. I can submit the relevant code on that branch.

@mggger : thanks for your contribution. Looks good to me.
Can you please resolve the merge conflict?

Hi @mggger , can you check why the tests are failing?

@taranjeet  Got it, due to the removal of the "allow_reset" configuration option, the unit test did not pass. It has been fixed.

@mggger : the test are still failing. Can you please check?

@taranjeet  I'm sorry, previously I only ran test_chroma_db.py, but this time I ran all the unit tests.

No worries.
thanks for your PR @mggger
Merged it

I noticed that you disabled allow_reset=True @mggger

@cachho  Please check the review message above. I left a comment in the review, but it doesn't seem to have been followed up on.

@taranjeet Got it, due to the removal of the "allow_reset" configuration option, the unit test did not pass. It has been fixed.

but how has it been fixed?

@cachho  Create app with allow_reset
 app = App(
            CustomAppConfig(
                provider=Providers.OPENAI, embedding_fn=EmbeddingFunctions.OPENAI, chroma_settings={"allow_reset": True}
            )
        )


Feature : Collaboration and Study Groups

Is your feature request related to a problem? Please describe.
A major problem while doing some group project, assignment and everything is to make a whatsapp group everytime which can have all the nessesary people we need in it with all the materials in the group at a place.
Describe the solution you'd like
A solution to that would be study groups or collaboration system in the app when we add some assignment we can add collaborators in it which can edit and upload stuff. also with a built in chat for support and discussion
Describe alternatives you've considered
The chat part can be complex as of now for starting we can consider the collaborator feature like for example if one assignment is a group work so all collaborators can have like permissions of view or edit like that

Go Ahead @Pratik-11

Please assign me this @avinashkranjan
I have already started working on it, and I will soon open a pull request for it.
Thank you

Hey @avinashkranjan Please review my pull request @avinashkranjan
Thank you


Student credits: CSB 4-6 - can be found in SIS-DB but not showing in individual student stats

For instance student 014862438, has AY5823956 and AY5823954 in DB but not in käli.

Seemed to be working now.


Keyboard malfunctioning in specific use case. It seems to be opening and closing.

Bug description:
I noticed a strange behaviour for a very specific case while using this library. Keyboard flashes when clicking on a select box that is inside a modal. I'm uploading a video that demonstrates this odd behaviour.
The problem seems to be caused by the select box or because there is a modal opening another modal and the user action opens a keyboard sequentially.
To Reproduce:
The important thing here is the uri: https://www.att.com/buy/bundles/hsiaplans. When you open the listed link, a Modal should be prompted waiting for the user to input an address. If this address contains multiple units, for example: 3 Olvera St, Los Angeles, CA 90012, the webpage will prompt another modal and here comes the problem. When I try to click the select box to pick an unit the keyboard will flash (open and close very fast) making it impossible for the user to finish this process.
Code I'm using:
        <WebView
          style={styles.webView}
          source={{uri: 'https://www.att.com/buy/bundles/hsiaplans'}}
          incognito={true}
          startInLoadingState={true}
          renderLoading={() => <Loading size={96} />}
        />

Expected behavior:
The expected behaviour would be to either have the unit select box to open without even triggering the keyboard or to toggle(open) the keyboard and wait for user action without flashing (opening and closing keyboard very fast).
Screenshots/Videos:
This is what should happen when the select box is clicked:

This is a link for a video demonstrating the issue:

mov
https://user-images.githubusercontent.com/63731464/104505721-1e48c000-55c3-11eb-957d-349e85486413.mov
mp4
https://user-images.githubusercontent.com/63731464/104508788-83061980-55c7-11eb-8c0e-121e102ad190.mp4

Environment:
This only happens in iOS (mobile and tablet). Android works perfectly!

OS: iOS
OS version:  11
react-native version: 0.63.4
react-native-webview version: "^10.10.2"

Please let me know if you need more information on the issue or anything.
Thank you 🙏

No solution yet

Hello,
I am also facing same issue. Have you found any solutions

Hello,
I am also facing same issue. Have you found any solutions

Hey. Sorry I didn't read your comment before.
And actually no I did not find any solution... I just mentioned the issue to my client and we moved forward with development.
Two things I also mentioned to them was:

Open the user default browser
The possibility to re-do the needed web logic/code-flow inside React Native using same endpoint or w/e...
but I didn't find any solution using this lib

What about you? Did you find any solution for this?


64 bit required for App Store submissions

As you no doubt know, from Feb 1st new apps have to have 64 bit compatible binaries. Are you working on a 64 bit compatible ANE?

Google Analytics ANE is also my delay stone to publish my game. Hope to hear a good news from you soon.

Thanks for your great work, your ANE works like a charm. I hope you can deliver a 64-bit update soon!

:+1:

+1

+1

Almost done guys.
I just need to upgrade google's native library because the current one doesn't support 64bit. this might cause some issues so finger crossed. i should have an update in the next couple of days

+1

I go to this site everyday to see the update :))

Any updates for 64 bit, sir?

:+1: cant wait :)

Getting nervous!!!

I think I owe an update here ...
It's taking longer than expected because the native sdks have changed significantly in the meantime and i need to upgrade them in order to support 64bit. that required quite a lot of changes on the native side of the extension but i managed to leave the as3 interfaces untouched.
The code update is done, and the extension compiles ... but that's no guarantee.

I'm going to release it by the end of the week and ask everyone to do a deeper round of testing to see that everything works as expected.
We're almost there guys ... bear with me and my slowlyness

Yay!
I know you're working hard.
You're going to make us very happy when the new version comes out and we can check that everything works perfectly.
Thank you for your work.

just thanks for author! well job!

thanks :+1:  awesome work!

great job! May I know where is the extension you compile?

Thank you! Looking forward to it.

It's nearly 1st Feb limit day from Apple. Are there any new updates, sir? :)

Can't wait :)

Don't know should I replace this ANE or not :(. Love Google Analytics, but cannot wait so long for upload new version :(

I love your work, this is the last 64 bit ANE i need ( no presure of course ) X)     :+1:

It is too long. So said.

@Iaan Just replace this ANE by Flox to upload to App Store. Sadly I cannot delay my projects too long :(

@wanting252  Thanks for your reply. But what is Flox? Would you please give a detail page? Thanks again.

If you want to pay you can also use the Analytics ANE from Milman Games...

@Iaan http://lmgtfy.com/?q=flox+gamea

@harry248  milkmanagames‘s ANE support 64-bit system?

Their GoViral and CoreMobile ANE's are 64-bit compatible since a few weeks now, so I expect their Analytics ANE to be compatible too. Haven't purchased this one yet.

@harry248  So, there is no Google Analytics ANE supports 64-bit system.

As I said - I don't know, because I did not purchase this extension yet. I purchased other extensions from Milkman Games and those are already 64bit compatible. You will have to ask them but I expect the analytics extension to be compatible too.

all milkman ane is 64 bit compatible atm. however if you could use the Alebianco's ANE for free with the same function, that would be great. I could wait for a little more, but in the mean time I suggest you guys try Flurry instead of GA. 64 bit version of Flurry could be found in freshplanet

+1

Thanks for your great work.
I hope you can deliver a 64-bit update soon!

Any update? Should I wait? :)

+1

Looking forward!

any news on this?

I'd suggest buying the milkmangames extension, I did, it works perfectly for iOS x64 and Android.

+1

I need 64 bit ANE! Please!

news?

+1
Thumbs up for the great work.

I know it is too much to ask since it's free, but could you at least let us know if you plan to update or not? and an ETA on this? just to see if decide to wait or get another solution... thanks and we really appreciate your work!

I know it is too much to ask since it's free, but could you at least let us know if you plan to update or not? and an ETA on this? just to see if decide to wait or get another solution... thanks and we really appreciate your work!

i already have gone with milkmangames ane and it works perfectly. unfortunately i had to drop this.

+1

any chance you would share a ANE binaries that are compatible with the newest iOS8 apple requirements ? Even if not everything work perfectly ?
Cheers!


Part 1 Step 16 Failure messages should follow the offending packet

Start Step 1.16.


v0.9.0 and v0.9.1 tags missing

Looks like there have been releases for v0.9.0 and v0.9.1, but those tags are missing.
@ktoso looks like you cut those releases. Could you push the relevant tags please?

https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.typesafe.sbt/sbt-osgi/scala_2.10/sbt_0.13/
https://github.com/sbt/sbt-osgi/releases
https://github.com/sbt/sbt-osgi/pull/36/commits/84d838cfb8d161327c256a14ee71a9a601312710
https://github.com/sbt/sbt-osgi/pull/37/commits/5b93fbea3e7692fa85f82709164b94f0fe5c007e

Yes, my bad - fixed

https://github.com/sbt/sbt-osgi/releases/tag/v0.9.1
https://github.com/sbt/sbt-osgi/releases/tag/v0.9.0


Required input next

This is the next version of #5269. It doesn't include any tests yet, because I don't get them to run (npm test doesn't seem to actually run my unit tests). Any help is highly appreciated.

This PR adds required inputs as shown in the Material Specs. This is really useful to show that input is required before the user starts typing or submits a form.

[ ] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).


AWQ performs worse than llm-awq

If I am not mistaken, the awq implemented in ammo uses a default alpha_step = 0.1 to search the parameter. However, the model quantized by ammo have a larger performance reduction than AWQ. Is ammo opensource so that I can check where I make mistake or not?

Hi @spongezz , could you provide more details on the accuracy difference? There are several difference between our AWQ implementation and llm-awq.

lm_head is quantized in ammo (this causes accuracy drop on some models, so we just disabled it in the most recent release last weekend)
ammo uses symmetric quantization instead of the asymmetric quantization in llm-awq, which will cause slight more accuracy drop
llm-awq is a combination of awq scale and clipping while ammo by default only runs awq scale for fast quantization

@RalphMao Thank you for your reply! I will recheck and give you feed back soon.

Hi @spongezz , could you provide more details on the accuracy difference? There are several difference between our AWQ implementation and llm-awq.

lm_head is quantized in ammo (this causes accuracy drop on some models, so we just disabled it in the most recent release last weekend)
ammo uses symmetric quantization instead of the asymmetric quantization in llm-awq, which will cause slight more accuracy drop
llm-awq is a combination of awq scale and clipping while ammo by default only runs awq scale for fast quantization

Same problem. There is a big difference between the score of awq and the score of fp16. Are there any other parameters that can be adjusted?

@RalphMao Thank you for your reply! I will recheck and give you feed back soon.

Is your problem solved?

@RalphMao Thank you for your reply! I will recheck and give you feed back soon.

Is your problem solved?

Not yet. I tried using full quantization but it was too slow. I don't know whether it becomes faster in the lastest commit. I just use the int 8 quant to meet my needs. Would you please let me know if you solve the problem?

@RalphMao Thank you for your reply! I will recheck and give you feed back soon.

Is your problem solved?

Not yet. I tried using full quantization but it was too slow. I don't know whether it becomes faster in the lastest commit. I just use the int 8 quant to meet my needs. Would you please let me know if you solve the problem?

I now use GPTQ instead of AWQ and the accuracy is acceptable.
https://github.com/NVIDIA/TensorRT-LLM/blob/main/examples/llama/README.md#gptq

@spongezz Do you still have the problem? If not, we will close it soon.


Small edits

I made some small edits. I added a sentence stating that FAIR does not imply OSS, but OSS facilitate FAIR. We might want to say this again somewhere else.
I added a sentence saying "The publication of SEQUEST exemplifies a subsequent reoccurring pattern in MS-based proteomics; the development of software drives the adoption of novel experimental methodology." Yiu say this further down in the document, but I think it is important to stress that proteomics is software.
I also changed a large set of em dashes into hyphens. It seems like you pressed the wrong replacement at some moment, because even the url's were wrongly formated.

Great edits.


sip: check consistency between CSeq method and that of request line

Fixes baresip/baresip#1571

this patch looks fine


Fix Relative Actor positioning

There was a bug in the implementation of the relative positioning.
the y axis was using the value for the x axis, and the offset was always too big.

Was going through this earlier, almost made the exact same commit :-D The +8 you had on the x and y values was an offset for the coordinate system and wasn't needed when moving relative.


Edits based on support investigation

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

#sign-off


Fandl

@KyleMit please review.
I believe I obfuscated the GIF's appropriately, but if you feel I missed someone, just let me know.
FANDL Preview Page

Here's my overall take -
I feel a little bit icky about having such a direct viewpoint to our DB names. Which could be rectified by pivoting this article to "An Introduction to SSMS and SQL" or something like that and connecting directly to the Northwind Database or something - perhaps even accompanied by another article about how to get the northwind database up and running.
There's a ton of really cool stuff in here about just how to query data for folks just getting started with SSMS and SQL for the first time.  There's a tiny little bit about specifically how to connect to the FANDL system, but that might be better left to an architectural overview of FANDL and how that system works specifically.  I'd say that most of the SSMS specific stuff could be abstracted out into a more generic example that could help onboard devs who aren't necessarily assigned FANDL.
Especially since the audience for a lot of these tips is someone at a very beginner level, retreating to a level of abstraction where we're just talking about a "Client"/"Name" or "Order"/"Date" provides a really easy entry point into grasping some of the semantics around querying.


Is there anything interesting about rx which aren't allocated to practices?

When a prescription can't be allocated to a practice by BSA, but it can be allocated to a CCG, it is recorded as UNSPECIFIED PRACTICE.
This data is available in the new data source we're going to ingest (q.v. issue #282) and we've agreed to drop it on the grounds it's not actionable.
Before we forget about it, just in case there's some kind of interesting pattern, here is a quick comparison between rx which are unspecified versus specified.
This BigQuery SQL sorts prescriptions for all unspecified practices by total items, and adds a rank column based on this. It then compares the rank with those for specified practices, filtering for "interesting" ones.
These are items which are considerably more likely to end up against an unspecified rather than specified code:

A tweak of the same query shows those items which are considerably more likely to end up allocated to a specific practice:

And these are items which are never allocated to an unspecified practice:

The data is probably because of non-medical FP10 prescribing.  Nurses working for different practices (e.g. district nurses, health visitors etc) will often have to write in the practice code manually on the prescription.  Sometimes they will write this incorrectly, and one of two things will happen.  If they happen to write an code for another practice (within the CCG or not) the costs will get misallocated to them.  Sometimes CCGs will find this and will have to bill the correct CCG (this is also in the case of GPs who have moved but the systems haven't followed them correctly).  If the code is not for an existing practice, then it will go to the prescribers "home" CCG under a %998 code.
Note:  NHSBSA never correct the data when it's found to be misallocated.


densMAP parameters don't seem to be working

I was trying out running the densMAP version of UMAP by setting the dens_frac and dens_lambda parameters, and it appears that those values are not actually set when the algorithm is running. Happy to take a look at the code and file a PR if this is simple!
See screenshot with verbose=True:

Oops I see now that there is a densmap option to set to True, sorry


Windows containers missing from Dockerhub

Windows containers are removed from Dockerhub, was this removed by mistake?
https://hub.docker.com/_/microsoft-windows-servercore
https://hub.docker.com/_/microsoft-windows-nanoserver
https://hub.docker.com/_/microsoft-windows
https://hub.docker.com/_/microsoft-windows-server/

AFAICT, It's all good now.

Thank you!


How to fetch different version from hbase?

I do not find any function about how to fetch data with different version

I have the same problem, how do I get different cell versions ?

Sorry that I didn't get back to you on time. This test case illustrates who to fetch multiple versions.


Plan incorporation of https://github.com/mikejohnson51/ref_dams

@mikejohnson51 -- let's walk through how to get your work incorporated here. It may be a complete rewrite, but I want to keep the registry intact and some aspects of the overall workflow. I'll do #15 and tidy things up before we get started.

Currently, the workflow looks like this:
graph LR
  style Graph fill:#FFFFFF00,stroke:#000000;
  subgraph Graph
    direction LR
    x45079be5e9dad71e(["nat_db"]):::none --> x0d37c0787182d513(["nhdpv2_fline"]):::none
    x26c28590358ed1f6(["nid_gpkg"]):::none --> xde13d5897adf176a(["nid"]):::none
    xa0ffbbb184c91736(["nid_meta"]):::none --> xde13d5897adf176a(["nid"]):::none
    x5a093a06e6e82fb6(["dams"]):::none --> x367057a71281c312(["dam_locations"]):::none
    xde13d5897adf176a(["nid"]):::none --> x367057a71281c312(["dam_locations"]):::none
    x7b8f98c0b818a18a(["registry"]):::none --> x164a1fd6fa5b800d(["registry_out"]):::none
    x367057a71281c312(["dam_locations"]):::none --> x2dd2f719129b7fe6(["reference_out"]):::none
    x2ed57357c0c06777(["providers"]):::none --> x2dd2f719129b7fe6(["reference_out"]):::none
    x7b8f98c0b818a18a(["registry"]):::none --> x2dd2f719129b7fe6(["reference_out"]):::none
    x0d37c0787182d513(["nhdpv2_fline"]):::none --> x6c59ac2b7db5bcf8(["nhdpv2_fline_proc"]):::none
    x367057a71281c312(["dam_locations"]):::none --> x7b8f98c0b818a18a(["registry"]):::none
    x2ed57357c0c06777(["providers"]):::none --> x7b8f98c0b818a18a(["registry"]):::none
    x60fc93676537b647(["providers_csv"]):::none --> x2ed57357c0c06777(["providers"]):::none
  end
  classDef none stroke:#000000,color:#ffffff,fill:#7500D1;

Can you use the reference_flowlines? My plan was to use the outputs of this workflow; add any updates from the latest NID release (assuming the nid_gpkg stays 2019?), then run and refine the full conflation algorithm we have on it, using targets, and updated input sources. Does that sound ideal to you?

Yeah -- switching to reference_flowlines shouldn't be a problem.
I think this does sound like the right plan. Can we open up a stepwise set of issues that you can close as you work through it?
Thinking:

update data access to incorporate new data sources
incorporate core conflation algorithm and get running end to end
refactor / document code and workflow files
finalize and output release artifacts
update readme and other documentation
cut release and publish final artifacts

That make sense for the basic flow of the issues to tick off? Would it make sense to split 2 into a few pieces? Would be good to get a small review in between each step.

I think breaking (2) into series of a steps for each data source using Geoconnex inputs and uris where possible (may not need a review on each step) and then an additional step for ranking and qualifying/quantifying the agreement and final location would be good. Otherwise this looks great. You want me to take a stab at writing out a more granular process?

Whenever you are ready to start digging into the work, let's break this all out into stand along issues.


Add anoncreds issuance and presentation format

This adds issuance and presentation anoncreds formats which use the anoncreds registry.
Any anoncreds issuer must use this format as the anoncreds objects the format uses are saved in the wallet in the anoncreds way.
There is some backwards compatibility for a holder which isn't anoncreds capable. It will fall back to the indy handlers. Any holder that needs to use anoncreds objects which are not indy will need to use the askar-anoncreds profile. Any holder that uses the anoncreds format will need to be updated to a version of acapy which includes this PR.
There is a lot of duplication because I copied the Indy objects and added them to the anoncreds module and removed any indy  references. I think this is better than trying to rename them and share them amongst indy and anoncreds modules. The indy module should be able to be pulled out as a plugin once depreciated.
The object examples have anoncreds examples now. They have there own validation, but it's not actually validating anoncreds objects. I'm not sure if there is validation patterns we can use for anoncreds schemas, cred defs and revocation objects or not.
There is a scenario test for anoncreds issuer doing issuance and presentation with a anoncreds and a non-anoncreds holder.
These will need to get interop OWL-ATH tests.

I approved but we have test failures that should be resolved before merging.

Added support for the demo but still need to fix the integration tests. Not sure why the scenario test is failing with github actions and the BDD tests need to be updated.
The OATH tests should be updated with an askar-anoncreds wallet. These should be testable against a credo holder, and should work with a credo issuer and acapy holder as well if the objects are consistent with the indy format.

I removed the BDD tests for issuance and presentation after the anoncreds upgrade because the anoncreds check uses the agent context object which hasn't been updated. I'm going to try and figure out how to do that and add them back.
There classes I moved and renamed from the indy module to the anoncreds module aren't unit tested. I don't think this is much of an issue because they are pretty much the same as the ones in the indy module that are unit tested. I might try and copy some tests as well as they would be good to have if they indy module gets pulled out. Don't think this should be required to get this merged though.

Question regarding interoperability - should an agent using an "askar" wallet be able to send/receive a presentation request/presentation from a holder that has received an anoncreds credential?  (And the other way - an "askar-anoncreds" agent asking an agent with an "askar" wallet for a proof?)
Also what should happen if an "askar-anoncreds" agent issues to an "askar" holder and the other way around?

Question regarding interoperability - should an agent using an "askar" wallet be able to send/receive a presentation request/presentation from a holder that has received an anoncreds credential? (And the other way - an "askar-anoncreds" agent asking an agent with an "askar" wallet for a proof?)
Also what should happen if an "askar-anoncreds" agent issues to an "askar" holder and the other way around?

Issuer (askar) --> Holder (askar-anoncreds): This issuer won't be able to issue or request a presentation using the anoncreds format because of the wrong wallet type (schema and cred def tables are different). However, the agent can use the indy format still and the credential will work. I think this is still tested but I should make sure.
Issuer (askar-anoncreds) --> Holder (askar): This works and is tested. The holder falls back to the indy handler in specific areas where it needs to, for both issuance and presentation flows.

@ianco
I just looked at Issuer (askar) --> Holder (askar-anoncreds) and it looks like there's a problem here with issuance. There was a test but it was only running on release. I'll try and fix this scenario.

FYI @jamshale the "1a" was added to the demo to support this kind of interoperability testing.  (Available to an askar-anoncreds issuer only - this toggles between Anoncreds/Indy credentials and presentation requests.  So as Faber I can issue an Anoncreds credential, select "1a" to switch to Indy, then issue an Indy presentation request.  And vice versa.)
I did a quick test and when I sent the Indy presentation request I got an error: Problem report message: This issuer is anoncreds capable. Please use the anonreds format..
We should probably setup a table with the various options to define what is supported or not (and also we need to confirm that other Aries wallets support the same scenarios.)

issuer wallet type
holder wallet type
credential type (Indy or Anoncreds)
verifier wallet type
presentation type (Indy or Anoncreds)

Maybe this is already defined somewhere?  @swcurran ?
Also I recall that we also assume that all Indy credentials are updated to Anoncreds format when the wallet is upgraded?  (At least I think the Javascript framework does this, I don't recall if we implemented this for Aca-Py or not.)

That error was expected. I don't think it's possible for an askar-anoncreds agent to use the indy format handler after it's been upgraded to anoncreds. Before the indy format was just re-routing it to the anoncreds handler. I thought forcing the anoncreds issuer to use the explicit format would be better than keeping the indy format switching over to the anoncreds handler.
The original plan was to completely remove the indy format according to the comments. I wanted to keep both for backwards compatibility. But having both and trying to force indy format to re-route to anoncreds handler caused problems.

I'll create a table with the compatibility matrix after I fix this issue of issuer (askar) --> holder (askar-anoncreds)

Added an ugly commit. Will be working on further testing and refactoring still.
Issuer (anoncreds) --> use anoncreds format --> works with both (indy, askar wallet type) and anoncreds holder.
Issuer (indy, askar wallet type) --> use indy format --> works works with both (indy, askar wallet type) and anoncreds holder.

 Will be working on further testing and refactoring still.
Issuer (anoncreds) --> use anoncreds format --> works with both (indy, askar wallet type) and anoncreds holder. Issuer (indy, askar wallet type) --> use indy format --> works works with both (indy, askar wallet type) and anoncreds holder.

Tested using the alice/faber demo, everything is looking good ...
Question - is this a "breaking" change?  (i.e. will the controller need to be updated if they are currently using the "old" indy format?

It is a breaking change for anoncreds (wallet type askar-anoncreds) issuers. They will need to change their formats to anoncreds for issuance and presentations.
Any other type of agent is unaffected. Although holders will need to be upgraded to the latest version to handle the anoncreds format. I don't think there's any way to avoid this.

Scenario test has been expanded. It won't pass currently because of a bug with tails upload. See https://github.com/openwallet-foundation/acapy/pull/3346.

@jamshale  is this PR ready to go or are you still working on it?

@ianco It should be good to go. It has pretty thorough testing now.
I'll add some more documentation at some point but that can be a separate PR.

Some of the stuff I had to do for compatibility is a bit ugly. But one day it can be removed.

Some of the stuff I had to do for compatibility is a bit ugly. But one day it can be removed.

I agree we should make it easy to pull out the "indy" specific code.


Wrong handling of cli options

Hi,
I was testing flow againt brunch and i found this bug in watch.js (options should not be quoted):
if (typeof 'options' === 'function') {

It seems the bug is here since the start of the feature:
https://github.com/brunch/brunch/commit/a88d5cc8849c0d168675434d78785a8371a19131
So, should we fix it or remove it?

fix.

https://github.com/brunch/brunch/pull/1076


Added SRV records

Hi, thank you for this nice approach managing DNS records with terraform. We integrated it in our environment and added the feature to manage SRV records. Would you like to add it into the repo?

Hi @kingfisher77 , I've pushed the latest release v0.2.0 within my own repo : https://github.com/Xat59/terraform-azurerm-dns
The latest version supports SRV records.
Feel free to test it and give me a feedback.


add proxy size annotation for ingress

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.159%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
591

Relevant Lines:
999

💛  - Coveralls


[#2179] Improvement: Potential SQL injection point in generateDropDat…

…abaseSql
What changes were proposed in this pull request?
Improve security in generateDropDatabaseSql() .
This PR adds the following checks for database name

Regex check

As a best practice, it's generally advised to avoid including spaces in database names. In this PR, database names that include space will be considered illegal.

String length check, since SQL injection usually requires using longer string

Mysql: at most 64 characters
Postgresql: at most 63 characters

We refer to specifications of the earliest version of DB that gravitino currently supports:

Postgresql identifier rules: https://www.postgresql.org/docs/12/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
Mysql identifier naming: https://dev.mysql.com/doc/refman/5.7/en/identifiers.html
Mysql identifier length limit: https://dev.mysql.com/doc/refman/5.7/en/identifier-length.html

Why are the changes needed?
Fix: #2179
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing test & two new tests in TestPostgreSqlSchemaOperations and TestMysqlDatabaseOperations

@zivali
Can you also survey the table naming conventions besides the database name?

@zivali Can you also survey the table naming conventions besides the database name?

Absolutely! Do you mean we should apply similar checks in JdbcTableOperations (MysqlTableOperations / SqliteTableOperations / PostgreSqlTableOperations)?

hey @justinmclean,  is this improvement done? If not, may I look into this?

@simarjeetss IThanks for offering to help, but as this is almost complete, I woudl suggest you find another issue to work on.

@simarjeetss IThanks for offering to help, but as this is almost complete, I woudl suggest you find another issue to work on.

Sure, thanks for letting me know!

@jerryshao
Is this related to the issue https://github.com/datastrato/gravitino/issues/1652?  If so, should we temporarily merge it?

I would say it is not related to #1652. Might consider merging this as it is an overall improvement to the existing code?

@zivali Are you still interested in working on this? No issue if you can't, it would just be good to know.

@justinmclean Hi, I am still working on it. Will update here when finished. Thank you!

I'm introducing a catalog capability framework(#2819), I think this should be one of the catalog capabilities - name specification capability.
If you want, I think you can continue to work based on #2819 or after it is merged

@mchades Got it. Will integrate this PR to https://github.com/datastrato/gravitino/pull/2819 Thanks for the info!


can't disable labels for piechart

I'm trying to draw a PieChart without labels, but both showInnerLabels={false} and showOuterLabels={false} aren't doing anything.
looked through src, looks like props should be propogating down from PieChart all the way to Arc but it looks like the default might be overriding these values between ArcContainer and Arc. is this a known bug?

If that's happening, it's either standard behavior or a bug with React; I've been under the impression that defaultProps is only used when the prop isn't specified at all from the parent, and {...this.props} should count as specifying props.

((didn't realize I was using the other react d3 library, switched to this one & it works :stuck_out_tongue_closed_eyes:))


fix(v2): refactor color mode system

Motivation
Some things impossible with current api:

disable the toggle, but use the dark mode by default
disable the toggle, and respect the user preferred color
force default light theme, ignoring the user preferred color
set dark theme by default, but respect the user preference to light if set

Breaking change to classic theme config to support all possible scenarios
Superseed #2939 (as I now work on a branch of the main repo)
Doc

Would love to have this!


Add function and notebook that are used to create the highest scoring kernel on the public leaderboard

I just took a quick glance, looks neat.
I thought maybe it is a good idea to make a separate library common.nn where we can put all neural network related code. These layers you added are not specific to NLP (some not even to sequence models) and I got some nearly finished working files on other deep learning implementations from previous competitions that I should add at some point.
Also, importing from common.nlp.sequence_models_elements is a bit verbose for my taste.

Well done Chris!


How to view older version of documentation

How can I view older material documentation for versions which looked like this: md-datepicker?

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.

I have closed this issue out, but a feature for allowing version selection for the documentation would be very nice espically considering how quickly angular versions are changing.


Updated notebook link

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Please read the comments on an issue before contributing to it, and follow the guidelines to open a PR. Your PR is not linked to the issue because of it. Also, is there a particular reason for which you decided on only one file?

Closing in favour of a more comprehensive PR: https://github.com/freeCodeCamp/freeCodeCamp/pull/43618


Using Variables in Aggregation and Dimension

Hi,
Is there a way currently we can define variables for creating multiple aggregations and dimension. Based on the variables selected need to build multiple aggregation and dimensions. Tried using "${Variable:druid:json}" but it doesnt add multiple aggregations nor dimensions. This is for query builder. Please let me know of there are any work around for this.
Regards,
Akhilesh

Hello @Murthy7587
I believe ${Variable:druid:json} would work for columns attribute of a scan query for instance (Variable being a multiple variable). To repeat an aggregation based on a multiple variable.. we have to figure out an UX for that. Do you have any idea in mind ? would you will to contribute it ?
Thank you!


Run on custom video

Hi, thank you for your great work.
Is there any inference code or demo to run your work on a custom video?
can I implement it by using lib.test.evaluation.tracker.py ?

I did it.


SAK-42871 Update pending events with gradebookng denomination

Please make sure that this change does not negatively impact SiteStats (particularly the User Activity feature which does parse event references). As far as I can tell it will not cause a problem, but SiteStats should always be considered when making any changes to events.

I think we should discuss these event name changes.


Add a Wizard tab

Add a Wizard tab where users basically only have to worry about the basic processing, but not the detailed lists. It should have functions like...

Just Scan It
Scan single disks
Just Rip It
Rip single disks
Show the status when single actions have last preformed
History storage (and recall?)
...

The Lists tab had been simplified. Nothing will be done for now...


Deprecate CLI Flags

The following CLI flags are marked as DEPRECATED:

db.password
bus.apiPassword
bus.remoteAddr
worker.apiPassword
worker.remoteAddrs

They should be removed and everyone should use their env variable counterparts, or through yaml.

Hi, please assign me this issue

can i take this one ?

Hi @peterjan
Can you tell me which files need to be updated?

@ShatilKhan you can find the CLI flags in cmd/renterd/main.go


Cocoon logs do not open in browser window anymore.

They're downloaded as an attachment instead.  This is probably a matter of headers or something?
/cc @CaseyHillers @digiter @keyonghan

This is intentional (https://github.com/flutter/cocoon/pull/531).
There is work on https://github.com/flutter/flutter/issues/43124 to be able to redirect to the Google Cloud Log Viewer OR download the logs.

Hmm.  Seems unfortunate, but will close in favor of https://github.com/flutter/flutter/issues/43124


Function in submission-created doesn't have payload.form_name

Netlify provides a form_name value in the payload for submission-created.js functions. This is necessary for handling multiple forms in a single Netlify site. netlify-cli doesn't provide that key/value in payload for submission-created.js.
Configuration

Install netlify-cli
Create submission-created.js in your functions folder.
Have 2 forms in your site.
Try to use payload.form_name in Netlify live: it works.
Try to use payload.form_name in netlify-cli: it's missing.

Expected behavior
netlify-cli should expose payload.form_name for form functions, just like Netlify.com

Hi @jdsteinbach! Due to the mechanics behind the form submission system, it's not trivial for us to add that behaviour to the CLI (at the moment). That could chance in the future. As a workaround for you, you could embed a hidden form field into your forms:
<form netlify name="foo">
+  <input type="hidden" name="form-name" value="foo">
  ...
</form>

@netlify-team-account-1 Thanks for the reply! I'll use the hidden field workaround for now.

Closing as stale. Please re-open if needed


Wrong badge links corrected. [skip ci]

Wrong badges links were added to the README.md for the wrong
platform. This is now corrected.
[skip ci]
Resolves: OLPEDGE-1741
Signed-off-by: Andrei Popescu<EMAIL_ADDRESS>

please forcepush again, travis stuck.


Using httplib instead of httplib2 to get GCE metadata.

Fixes #575.
Feel free to run the bash script I included in the bug to torture test the fix.

Coverage remained the same at 100.0% when pulling b35c64f98a812438e77c596c012169805908f958 on dhermes:fix-575 into bf93d461298d0980a41c5dfa426d9f32af3d42fb on GoogleCloudPlatform:master.

I realized I need to use the _Httplib stub in the default fall through as well. Will fix when back at keyboard

Coverage remained the same at 100.0% when pulling 8dc13b522e0a0fbfa8c16e278720962b9d35bee5 on dhermes:fix-575 into bf93d461298d0980a41c5dfa426d9f32af3d42fb on GoogleCloudPlatform:master.

@tseaver PTAL, with 8dc13b522e0a0fbfa8c16e278720962b9d35bee5 I made sure all calls to set_default_dataset_id have the httplib stub.

@tseaver Any other comments before I push the content = None fix?

Nope -- "merge when ready, Gridley!"

Coverage remained the same at 100.0% when pulling 8febd04f764c94e707cc9b70b00fa5c8454bf03d on dhermes:fix-575 into bf93d461298d0980a41c5dfa426d9f32af3d42fb on GoogleCloudPlatform:master.


[QUANTUM][WHISPER] Edit text files, make list of extensions

html editing without onlyOffice for simple files (txt, js, json, markdown,...)

[x] Implement in Quantum
[x] Edit shared files
[x] Implement in Whisper
[x] Use readOnly view for read shares
[x] Make mobile friendly
[x] extra save button with the editor

on staging, will check it myself , good for forum @sasha-astiadi


Bump version to 4.1.

See https://github.com/opensim-org/opensim-core/issues/2170

@aymanhab this version is how we set app.version; https://github.com/opensim-org/opensim-gui/blob/87398e2c07820fe10e26713196f03e88ceb48f1d/Gui/opensim/CMakeLists.txt#L139
So for the purpose of building a distribution, this is intended to be the single place where the version number is set and used.

Thanks for the clarification @chrisdembia though the block you pointed to is only for mac installer. Would be good to unify the mac and windows at some point. unrelated to this PR.


A question about the dice loss

@FabianIsensee Hi, sir. As far as I know the labels in the dataset of brats 2017 are 0,1,2,4. But in the definition of the function  hard_dice_per_img_in_batch in the utils.py you use for i in range(n_classes): y_true_i = T.eq(y_true[b], i_val). Since n_classes is 4 i is in [0,1,2,3] which seems  to be inconsistent with the true labels. I do not know whether it is that. Thank you!

Please look in the code. Labels are converted to 0, 1, 2, 3 during preprocessing

Thank you！


PHP 8.2 support

Add the #[\AllowDynamicProperties] attribute to squash deprecation warning for dynamic properties e.g. $this->$name = $value; within __set() methods
Change deprecated string interpolation "${var}" to sprintf() -  I did not use "$var" or "{$var}" syntax as that failed linting e.g. Squiz.Strings.DoubleQuoteUsage.ContainsVar e.g. Variable "$message" not allowed in double quoted
Adds PHP 8.2 to CI matrix

OK fair enough - do you know roughly when the stable for 15 will be released?


What is proc-macro2

@alexcrichton @mystor
Did I do this right?

Right now procedural methods have no method of preserving span information of expanded code or otherwise dealing with spans. That's all due to the usage of strings on both ends of the interface where you to_string a TokenStream and then parse back into a TokenStream. Clearly this isn't the best interface for all of time, so we'd like to fix that!
Upstream in rust-lang/rust the proc_macro crate is getting an enhanced API which will enable preserving and customizing span information of streams coming out of and going back into the compiler. This should be a great benefit to all procedural macros in terms of error messages and debugging usability.
All of those new APIs, however, are naturally unstable. They'll take some time to stabilize and the timeline for stabilization is unclear. To work around this the proc_macro2 crate is an attempt to sidestep this stabilization timeline. The proc_macro2 crate intends to provide the exact same API as proc_macro (if it were stable) yet also compile on stable Rust. To do that proc_macro2 by default will use the to_string and parse interfaces to convert to/from TokenStream. You can, however, enable the unstable feature of the proc_macro2 crate which actually compiles against the unstable interface of proc_macro. This requires a nightly compiler, but should be able to losslessly preserve all span information.
So basically tl;dr; proc_macro2 is future-proofing. Macros written against it have a turnkey solution for better spans on nightly today, and will have a turnkey solution for better spans in the future once the new proc_macro API is stabilized.
Does that make sense?

It does make sense, yes. So how do I get one of these


Add category info

The category is available in the initial json from emoji-data. Do you think it would be interesting to add the information in the js library as well?

The category is the one thing missing for building an emoji picker using only the data in js-emoji. Currently need to pull in emoji-datasource and cross reference, it would be great to drop loading both.


docs(hub) optum logo update

Summary
Update logo for Kong Hub listings published by Optum
Checklist:

[x] Commit message & atomicity checked
[ ] Documentation N/A
[ ] Spellchecked my updates N/A
[x] Ready to be merged

Thanks Cooper :+1:

Actually cooper - Could we delay this merge for a bit? I need to have the branding team check my handiwork before we can go fully public.

I've labeled this PR to hold merge @rsbrisci - I'll remove those labels when you say so. No rush, we can tune this up anytime.

We have gained approval from our branding team.
Thanks,
Jeremy

@coopr Any ideas when this will go live to see the Logo in action?

@jeremyjpj0916 this should get deployed later today.


[FEATURE]  apm 有什么推荐，swoole那个不维护了。需要监控 到方法 ，内存，cpu

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

https://hyperf.wiki/3.1/#/zh-cn/metric 或者 Apache SkyWalking 之类的。


Load Failure

i get a trouble "Load FAILURE" i have some models andI've put it in the folder
Why does it appear? Do I need to change the model path?

I think this means UGATIT is failing to find the dataset. Is the selfie2anime/testA folder inside your dataset dir?