How will Edge Intelligence Benefit IoT?

Proposed title of article
Introduction paragraph (2-3 paragraphs):
With Edge AI, IoT devices are becoming smarter. With machine learning, edge devices are now able to make decisions. They can make predictions, process complex data, and administer solutions.
For example, edge IoT devices can process operating conditions to predict if a given piece of machinery will fail. This allows companies to perform predictive maintenance and avoid the larger damages and costs that would have been incurred in the event of a complete failure.
Also, a security camera equipped with edge AI may no longer only capture video. We will be able to identify humans and count foot traffic. Or, with facial recognition, even identify exactly who has passed through an area and when.
Key takeaways:

Why edge brings on the table (reduced bandwidth requirement, reduced latency, increased reliability)
Chip-enabled intelligent edge
Edge intelligence and smart cameras on the IoT

References:
Please list links to any published content/research that you intend to use to support/guide this article.
N/A
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good afternoon and thank you for submitting your topic suggestion @mumbi00.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Hi, @mumbi00. Great topic suggestion. Topic approved 🚀. Be sure to add lots of detail (especially about how edge intelligence can benefit smart cameras) to make your article stand out from similar ones such as this one.


Requirement of a description of Backend JWT

Description:
A description of Backend JWT should be added to the concepts section in order to provide a better understanding of the feature.
(Reference for the APIM doc - https://apim.docs.wso2.com/en/3.0.0/learn/api-gateway/passing-end-user-attributes-to-the-backend/passing-enduser-attributes-to-the-backend-using-jwt/#passing-enduser-attributes-to-the-backend-using-jwt)

Closing as it is fixed with https://github.com/wso2/docs-mg/pull/10


[BUG] Unable to purchase LightNode _app-a4db3a1c09c6769d.js:374 e ConnectorNotFoundError: Connector not found

CHAIN: Arbitrum
Token: USDC
(anonymous) @ _app-a4db3a1c09c6769d.js:374
_app-a4db3a1c09c6769d.js:374 Object Object Error: WebSocket connection closed abnormally with code: 3000 (Unauthorized: origin not allowed)
at x.onClose (5021.2a7451026a1ac452.js:1:2174)
at a. (5021.2a7451026a1ac452.js:1:2811)
at a.emit (_app-a4db3a1c09c6769d.js:374:362371)
at l.onClose (_app-a4db3a1c09c6769d.js:374:25999)
at WebSocket. (_app-a4db3a1c09c6769d.js:374:25867)
(anonymous) @ _app-a4db3a1c09c6769d.js:374
_app-a4db3a1c09c6769d.js:374 Object Object Error: WebSocket connection closed abnormally with code: 3000 (Unauthorized: origin not allowed)
at x.onClose (5021.2a7451026a1ac452.js:1:2174)
at a. (5021.2a7451026a1ac452.js:1:2811)
at a.emit (_app-a4db3a1c09c6769d.js:374:362371)
at l.onClose (_app-a4db3a1c09c6769d.js:374:25999)
at WebSocket. (_app-a4db3a1c09c6769d.js:374:25867)
(anonymous) @ _app-a4db3a1c09c6769d.js:374
_app-a4db3a1c09c6769d.js:374 Object Object Error: WebSocket connection closed abnormally with code: 3000 (Unauthorized: origin not allowed)
at x.onClose (5021.2a7451026a1ac452.js:1:2174)
at a. (5021.2a7451026a1ac452.js:1:2811)
at a.emit (_app-a4db3a1c09c6769d.js:374:362371)
at l.onClose (_app-a4db3a1c09c6769d.js:374:25999)
at WebSocket. (_app-a4db3a1c09c6769d.js:374:25867)
(anonymous) @ _app-a4db3a1c09c6769d.js:374
4690-0410c14d99d6aef2.js:1 args Array(9)
4690-0410c14d99d6aef2.js:1 ethValue 0
4690-0410c14d99d6aef2.js:1 Estimating gas... 586997
4690-0410c14d99d6aef2.js:1 Preparing transaction hash...
_app-a4db3a1c09c6769d.js:374 e ConnectorNotFoundError: Connector not found
at t9 (_app-a4db3a1c09c6769d.js:378:13130)
at async buyNow (4690-0410c14d99d6aef2.js:1:18801)
at async tE (5126-8054fcbe6da0d8b3.js:1:392590)
nodesale.palomachain.com/api/v2/addaddr:1
   Failed to load resource: the server responded with a status of 400 (Bad Request)

Fixedwit removal of WAGMI


Is it possible to use openapi-backend for proxy

Assume I have OpenAPI yaml with bunch of endpoints, and I need to implement a proxy server, which will validate incoming requests, and then proxy them to one of other servers (let's call them - backend servers) for actual processing. All backend servers follow the same OpenAPI spec (as well as proxy). Proxy has a list of all backend servers, and chose one of them to proxy each request based on some info from incoming request.
The problem I see now is at this:
api.register({
  getPets: (c, req, res) => res.status(200).json({ result: "ok" }),
  getPetById: (c, req, res) => res.status(200).json({ result: "ok" }),
  // ....
  notFound: (c, req, res) => res.status(404).json({ err: "not found" }),
  validationFail: (c, req, res) =>
    res.status(400).json({ err: c.validation.errors }),
});

I don't have a list of all operationIds  (as getPets and getPetById), and I don't want to specify them manually. Logic for any operationIds on proxy is the same: just define one of backend servers, and pass request to it.
And one more question: is it possible to read yaml separately (say, using fs.readFileSync('open-api.yml', 'utf8'), and pass its content to OpenAPIBackend constructor (instead of definition filed as file path)
I appreciate any help/idead/suggestions

OpenAPI Backend will default to the notImplementedHandler if no operation handler is specified for the request. You can use that as your catch all to proxy requests.
And yes, you absolutely can pass the openapi definition as an object to the OpenAPIBackend constructor, instead of as a file path ✅

@anttiviljami, I think, I have an issue following your advice  :(

So I have a OpenAPI yaml, where I have lots of endpoints definitions, each with its own operationId. Here's how I instantiated OpenAPIBackend:
  const api = new OpenAPIBackend({
    definition: API_SPEC_PATH,
    handlers: {
      validationFail: async (context, req: Hapi.Request, h: Hapi.ResponseToolkit) =>
        h.response({ err: context.validation.errors }).code(400),
      notFound: async (context, req: Hapi.Request, h: Hapi.ResponseToolkit) =>
        h.response({ err: 'Not found' }).code(404),
      notImplementedHandler: async (c, req, h: Hapi.ResponseToolkit) => {
        return h.response({ err: 'notImplemented' }).code(502);
      },
    },
  });

And I was hoping that each time call existing endpoint, my notImplementedHandler will be called, and I got 502 error.
But I always get 500 error:
{
    "statusCode": 500,
    "error": "Internal Server Error",
    "message": "An internal server error occurred"
}

and code execution never gets to notImplementedHandler
Am I doing something wrong?


Create README.md

@Stonepia Could you please update the Installation and Getting started parts based on current BKC?

Sure, I will update it in the Readme.md.

@Stonepia Let's remove Installation and Getting started parts. Please update README once ready.


Flask: Process dies while debugging after 1.5 minutes.

I am trying to debug the flask app that's being run in IIS. When debugging a response being sent from the server, IIS kills the process after 1.5 minutes. I have changed Application Pool and site settings in IIS like Time-out and Ping settings. These settings increase the timeout and time it takes for the process to die when not debugging. However, while debugging, it kills the process within 1.5 minutes and returns 500 error to the client. Are there any settings any where in flask or wfastcgi.py that will allow us to increase the timeout while debugging?

This may be worth trying: https://social.msdn.microsoft.com/Forums/en-US/ef324552-8dbc-4188-a476-52b9332fb5f4/pythonweb-apps-python-fastcgi-activity-timeout?forum=opensourcedevwithazure


Release 0.8.0

There are still issues with building the latest llvm from source, but install from bundle (default) seems to work on all supported platforms

Some issues to work out:

Looks like jenkins expects all tests in master to be just like in dev. So either we update all the tests in master or we change the master build-jobs in jenkins. @mnordsletten - is this only for the PR-tests or will this make the master badge go red?
TCP test times out. Was this @AndreasAakesson was this fixed in dev?

Yeah at the moment the PR tests that you can see were performed here expect that the tests are just like in the dev branch. This is something I will have to work out.
When you eventually merge dev into master the exact same tests should be completed in order to update the badge. This uses the ./test/validate_all.sh script to check which of the tests are ready to be tested. So if the dev badge is OK before merge the master badge should be OK after the merge. For both of these badge-tests there is an option in jenkins to disable certain tests. So at the moment the transmit test has been disabled for both master and dev.
As for the tcp test, this was increased in the dev branch. We did still see if time out a couple times after this, but checking the badge_test history it's been a long time since this was an issue now.


problems on building docker image

My operation OS is Ubuntu 14.04.
I followed by the README.md step by step, and wanna to build a docker image.
But when I ran
make docker-image
in p4factory/targets/switch directory, the program seem work well, but when it processed step 14, there are something wrong.
First, it shows that
fatal: Not a git repository: ../../.git/modules/submodules/bm
but when I go to that directory, I tried
git status
the git showes that bm is a git repo.
Then after checking ,it shows
configure: error: The P4_PATH you provided does not exist or is not absolute
mmake: *** [clean] Error 2
Then, after compiling something, it shows many messages like
 Semantic warning: header instance 'outer_udp' is not reachable and will be removed
And finally,
make: *** [bm_tenjin_output_oldest] Error 1
and quit with error 2

Is this issue resolved ?

I find the same error popping up when I say : make docker-image

I am not sure what was causing the issue in the first place, but we don't really support make docker-image any more. I believe that the new steps to build a docker image running switch.p4 are here: https://github.com/p4lang/switch#building-switch-docker-image

Thank you. I'll try it.
And what  can I do to run the INT app in P4factory ?
The README in INT showed that I should use make docker-image

According to the team in charge of the INT demo in p4factory, this code is broken for now. They are trying to update the demo to work with the new docker image building process, but there is no ETA for now. Sorry about that.

ok, thank u


[FR]: Wrap Inlinks & Outlinks

Contact Details
No response
Present your request
Some of my files have like 30 inlinks/outlinks. I don't see a way to wrap the field, which means that entry in the database will take up the whole page. I really would like to not hide them entirely
For which platform do you request this request??
Desktop

same problem


Add PostgreSQL and MySQL floating point type mapping tests

We should also add NaN and inf cases in io.prestosql.testing.AbstractTestDistributedQueries#testDataMappingSmokeTestData.
Can be separate PR.
(There certainly is a duplication in these tests, but I don't see a way to avoid this fully.)

We should also add NaN and inf cases in io.prestosql.testing.AbstractTestDistributedQueries#testDataMappingSmokeTestData.
Can be separate PR.

I will send separate PR. Unless you will be slow in reviewing this one and I find time to amend this one before it gets merged :)


Publish is back on y01y27 in the March 2018 version

In the current version (Version: 2.56.5023.1021 64-bit (March 2018) the publish-button is back on: y27 (instead of y25).

Thanks for comment. Moreover all preview feature buttons are changing the anchor number.
I have to change the method how to call PBI functionality.
Thanks

I changed button identification to use the name of the button i.e. Refresh or Publish. Done in 0.1.15


Remove travis gating for webrender.

Having the travis-ci gate enabled is causing several issues for
the WR repo at the moment (mostly timeouts, but also complicating
updating the Linux version used by the builders).
This moves the WR reviewers to the main reviewers list. This does
give those named reviewers extra repo privileges over what the
previous configuration. I'm not sure if there's a better way to
remove the WR gating while also keeping WR reviewer status.
Fixes #803.

This change is

I have no idea what I'm doing here. Does this make sense?
r? @larsbergstrom or @edunham or @jdm

I'm trying another solution that will retain the reviewer status quo.

https://github.com/servo/saltfs/pull/821 is a more future-friendly solution.

Cunningham's Law in action.


Support for Confluence 7.0.1 Microsoft Azure Active Directory single sign-on for Confluence:

We had to upgrade to Confluence Server 7.0.1 due to security flaws pointed out by Atlassian.  This has now broken your product.  Please fix a compatible version for 7.01 as we tried the latest one and does not work

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

ID: a45acbc6-caae-be6c-939e-55451831d03e
Version Independent ID: 0d88f4ee-2ac5-1ad4-245b-b8c0752a7303
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Confluence SAML SSO by Microsoft
Content Source: articles/active-directory/saas-apps/confluencemicrosoft-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@scootafire Thanks for the question. We are investigating the issue and will update you shortly.

@jeevansd Do you have any insights regarding when we will support 7.0.1 version?

Any feedback here Guys?

Do we have an eta on fixing this?

one on getting this fixed please

Any updates on this?

Please update this plugin, waiting for it for a month now...

Also waiting on an update to this plugin for Confluence 7.0. Thanks for the support so far!

Also waiting on an update to this plugin. Had to upgrade to Confluence 7.0.2. to fix security issues now can't use your plugin.
And it is a great plugin thanks for the hardwork on it and can't wait to get back to using it!

We are completing our testing now and will release this soon.

any update on the testing?

@jeevansd, any update here? We are blocked on it. Looking for a quick update on this plugin.

Any news on this? I did a little bit of digging around and it the plugin seems to crash because of some missing ApplicationInsight components or something like this.

@jeevansd, it's been 2 weeks and a lot of people looking for an update on this. This is so disappointing for not responding to us. This is a critical request for us.

@jeevansd, it's been 2 weeks and a lot of people looking for an update on this. This is so disappointing for not responding to us. This is a critical request for us.

They were all likely at MS Ignite which is why updates have been lacking. Hopefully they get back to us this week.

coming up on two months now without this functionality since Confluence upgrade

We needed to upgrade for security reasons as well.  Very concerned MS hasn't released an update to this plugin yet...

Maybe St. Nicolaus' Day would be a great release date for this plugin. We would really appreciate that!

@scootafire @beastofbobmin @dandyfopper @taaeipa1 @adamharm We have tested the new plugin with these versions please download it from here now https://app.box.com/s/yuc3krl8uo8vr2is59dm44utu8dmquf9 I will upload this on the Download center in the next week. Apologies for the delays here. We have tested these versions with it Confluence: 7.0.1,7.0.2,7.0.3,7.0.4 and 7.1.0

@jeevansd Just installed the new plugin on our Confluence and works like a charm! Thanks!

@jeevansd Installed on our confluence and works great! Great job! Many thanks!

Guys good things takes some time. As these new versions are coming our matrix for testing all the applications with the same plugin is increasing and that is why it takes so much time.

Now I will close this ticket. #please-close

Works for me as well.  Thanks

When will this be available on the Microsoft Download centre?

@beastofbobmin It will be updated by this week.

@jeevansd, Thanks for the reply, i still dont see it in the Microsoft Download Centre. is it meant to be there?


New "hide window via close button" setting is inverted

Aknowledgements

[X] I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.

[X] I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself. I have tested
if this bug occurs on Chromium/Chrome or any other Chromium-based
browser that uses unpatched/upstream Chromium engine.

[X] I have tried running the build from the master branch and it does
not have any fixes implemented according to my issue.

[ ] My issue describes one of the unstable and/or not fully implemented
features.

[X] I have found a workaround to mitigate or temporarily fix this issue
in affected releases (please write it in Additional context section
below).

Operating System / Platform
🐧 Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
v21.2.1
Application version
3.9.2
Bug description
The new "Hide window to tray with the close button" in Webcord settings is inverted - having it checked will cause the application to terminate upon hitting the close button, and vice versa.
This appears to have been introduced in 95b9418 in response to #263 - inverting this boolean check looks like it should fix it, although I don't know enough about JS/TS development to be fully confident in that claim.
Additional context
No response

This is actually on purpose.
It is called Hide window to tray with the close button. and that's meant the opposite of close on close. This is why I made this checkbox inverted. It also represents it disables the feature, rather than enables it – in fact, Electron by the default will close window when clicking on the close button on the title bar – regardless if there's a tray or not.
I'll close this issue as invalid and wontfix…

Oh, actually noticed multiple bugs with it – one is that it doesn't update on live, as it should be.
Not sure how I missed that, but yeah, you're right it doesn't work as it should be… My bad! 😅

To be honest, I've been testing how it works before releasing it with 3.9.0 and I feel ashamed I thought it just seem to work OK, now seeing toggling it doesn't update the value as I expected it would be and why the hell I thought it's somewhere in the event listener when I see now it clearly isn't…
That being said, this will make it to the next patch release. I'll probably wait a little and either do some other bug fixes in that time or wait for any other reports like this.

Thank you so much for your time and effort on this project!  😊


Spell Crit not recognized

As title says, the price distribution doesn't work at all for me. I have to click on "No matches found" to see the items listed.
Also Spell Crit on Shaper Chest isn't recognized as a mod when the window comes up for the item.

After restarting the overlay the price distribution started working. Spell crit still not being recognized though

Can you please share the item data (CTRL + C while hovering)? Thanks! I'll look into it.

Rarity: Rare
Grim Carapace
Vaal Regalia
Quality: +20% (augmented)
Energy Shield: 196 (augmented)
Requirements:
Level: 70
Str: 68
Dex: 105
Int: 194
Sockets: R-B-B-G-R-B
Item Level: 84
+113 to maximum Life
+28% to Chaos Resistance
Spells have +1.5% to Critical Strike Chance
Gain 10% of Maximum Life as Extra Maximum Energy Shield (crafted)
Shaper Item

It's the same with attack crit. It also misses the -15 to mana. I think the error might be that the program has problems handling both the "." and the "-" in searches.

Seem related to: #62 . Can you please check 0.4.4? Thank you!

It fixed the crit, but not the mana cost.

Not fixed for me with 0.4.4
https://i.imgur.com/azknF6l.png
maybe it is a problem also with the localized dot or comma for decimal places? although it does handle the life regen which is also a decimal place.

The following mod is also missing (using 0.4.3):
#% increased Movement Speed if you've Killed Recently
`Rarity: Rare
Hollow Iridescence
Hypnotic Eye Jewel
Abyss
Requirements:
Level: 41
Item Level: 82
Adds 13 to 18 Cold Damage to Spells
+30 to maximum Life
3% increased Movement Speed if you've Killed Recently
Place into an Abyssal Socket on an Item or into an allocated Jewel Socket on the Passive Skill Tree. Right click to remove from the Socket.
`

The following mod is also missing (using 0.4.3):

Thank you! There was an error at the parser. It will be fixed in the next alpha version.


How can I extend the Directive

I would like to extend your NgxTribute directive so I can create a wrapper for additional functionality.
I've originally have tried something like this -
import {NgxTributeDirective} from "ngx-tribute/lib/ngx-tribute.directive";
@Directive({
  selector: '[tagging]' // Attribute selector
})
export class TaggingDirective extends NgxTributeDirective<any> {

  constructor(element: ElementRef, formControlName: FormControlName, formControlDirective: FormControlDirective, ngModelDirective: NgModel) {
    super(element, formControlName, formControlDirective, ngModelDirective)

    this.options = {
      values: [{value: 'Phil Heartman', firstName: 'pheartman'},
        {value: 'Gordon Ramsey', firstName: 'gramsey'}],
      selectTemplate: function (item) {
        return ''  +item.original.value  +'';
      },
    };
  }
}

But I get the following error - Uncaught Error: Cannot find module "ngx-tribute/lib/ngx-tribute.directive"

Please update to the latest version, the directive class was not exposed from the NPM module.
After updating you should be able to do:
import {NgxTributeDirective} from "ngx-tribute";

Remember to add @Optional() decorators to params of constructor. Check https://github.com/ladderio/ngx-tribute/blob/master/projects/ngx-tribute/src/lib/ngx-tribute.directive.ts#L22

Awesome thanks 👍


Updated Experience Available

The experience for creating recurring flows has changed (There's now a dialog process for selecting the recurring information) the link to advanced options is still relevant but may need to be called out more prominently based on the new experience.

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

ID: 5ba2e127-56bc-5910-3af6-30030cf58c1f
Version Independent ID: c8fea93d-3d8d-bf8e-af7d-ae853a936843
Content: Run flows on a schedule - Microsoft Flow
Content Source: flow-docs/run-scheduled-tasks.md
Service: flow
GitHub Login: @stepsic-microsoft-com
Microsoft Alias: stepsic

@syntax922 thanks for your feedback. I checked and it looks like the doc has been updated, so I will close this issue.


Signing endpoint: Firebase

Description
Provide an endpoint for signed urls to firebase, api/sign/firebase?.
GitHub Issue
#1226
Type of Change

✅ New feature (non-breaking change which adds functionality)
✅ Documentation

How have you tested this?
Tested locally using bugs_testing. The needed environment variables can be found in on xyz_settings/bugs_testing.
Testing Checklist

✅ Existing Tests still pass
✅ Ran locally on my machine

Code Quality Checklist

✅ My code follows the guidelines of XYZ
✅ My code has been commented
✅ Documentation has been updated
✅ New and existing unit tests pass locally with my changes
✅ Main has been merged into this PR

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1207876619030546

#1474


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 621fb65, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 8576 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in 59e418a.


Keyboard does not open when checking permissions < android M

Probably because of the transparent activity.
A possible fix is:
getWindow().addFlags(
                WindowManager.LayoutParams.FLAG_NOT_FOCUSABLE
                        | WindowManager.LayoutParams.FLAG_NOT_TOUCH_MODAL
                        | WindowManager.LayoutParams.FLAG_NOT_TOUCHABLE);

Version of the library
2.3.0

Hi @pixis,
Are you trying to open the keyboard while displaying the permissions request dialog? If that's the case, we can't do much as it's handled by the framework. If it's a problem while showing the rationale... I don't think it's safe to modify the window from the library.
Can you describe us what's your use case? I don't fully understand why would you want to show the keyboard while requesting permissions to your user.

I'll close the issue until further information is provided.

Faced with the same and found a solution, I hope someone will help: you must call "token.continue Permission Request();" in the "onPermissionRationaleShouldBeShown" event of your "PermissionListener".
`Dexter.withContext(activity)
.withPermissions(
Manifest.permission.ACCESS_FINE_LOCATION,
Manifest.permission.ACCESS_COARSE_LOCATION
)
.withListener(new MultiplePermissionsListener() {
@SuppressLint("MissingPermission")
@Override
public void onPermissionsChecked(MultiplePermissionsReport report) {
}
            @Override
            public void onPermissionRationaleShouldBeShown(List<PermissionRequest> permissions, PermissionToken token) {
                token.continuePermissionRequest();
            }
        })
        .check();`

Thank you in obviously new to this, lessening my damage as I go along

Thank you in obviously new to this, lessening my damage as I go along

Faced with the same and found a solution, I hope someone will help: you must call "token.continue Permission Request();" in the "onPermissionRationaleShouldBeShown" event of your "PermissionListener".

token.continuePermissionRequest();  saved my day. Thx


Introduce Values sub-project.

This PR creates a new module called values and separates types that used to be a part of client module but were not really used in there.
The purpose of the Values sub-project is to provide protobuf types and utilities for business value objects like email addresses, phone numbers, person names, bar-codes etc.
The reason for separating those types from the client module is that not all application will use some or even most of types provided by this sub-project.
For some near future, this code is going to be part of core-java, but later it would migrate into a separate sub-project with its own deployment artifacts and versioning.

Current coverage is 77.60%

Merging #117 into master will increase coverage by +0.13% as of 15c82ae

@@            master   #117   diff @@
=====================================
  Files           77     77
  Stmts         2344   2344
  Branches       267    267
  Methods
=====================================
+ Hit           1816   1819     +3
+ Partial         87     86     -1
+ Missed         441    439     -2

Review entire Coverage Diff as of 15c82ae

Powered by Codecov. Updated on successful CI builds.

Other than I've mentioned, LGTM.


[BUG]: React Server Component's Not working as expected

What version of drizzle-orm are you using?
0.23.8-d88fc1e
What version of drizzle-kit are you using?
0.17.6-76e73f3
Describe the Bug
Attempting to use inside a react server component
import React from "react";
import { getData } from "./actions";

type Props = {};

async function Workspace({}: Props) {
  const basics = await getData();

  return (

      Workspace

        {basics.map((basic) => (

{basic.name}

        ))}

  );
}

"use server";

import { db } from "@/lib/db";
import { basic } from "@/planetscale/schema";

export async function getData() {
  const basicResult = await db
    .select({ id: basic.id, name: basic.name })
    .from(basic);
  return basicResult;
}

Currently getting error:
- error node_modules/drizzle-orm/utils.js (62:18) @ entries
- error RangeError: Maximum call stack size exceeded
    at Function.entries (<anonymous>)
    at Array.reduce (<anonymous>)
    at Array.reduce (<anonymous>)

Seems like there's an issue with react server components as planetscale's database package functions correctly when used without the drizzle wrapper.
Expected behavior
For the database rows to be returned as normal
Environment & setup
drizzle-orm/planetscale-serverless
@planetscale/database
Nextjs 13.4

Didn't see that this had been put into the docs:
/** @type {import("next").NextConfig} */
const config = {
  reactStrictMode: true,
  experimental: {
    appDir: true,
    serverComponentsExternalPackages: ["mysql2"],
  },
}
export default config

Appears that i got a cached page for a bit, still not working unfortunately


Enhance log UI

Fix #5207
Change log list name change: all to stdout+stderr
Always refresh token when try to download log. Avoid token expired.

Coverage remained the same at 33.933% when pulling 23ce7e3e6cdc6e62516d2bd6e30dc0a628457bdf on binyli/ui into 864622bde62a9f37122117d89b417c8c17f7119f on master.


Consolidated LEDTYPE for Serial and SPI

Change type to ledtype

I agree that the computation isn't changing.  But you have mistaken the
data for the code.
These should be unique values - and then you should look up the code in a
table at the end.
In particular, as it is you can't go *backwards *from the LED type to the
name of the LED!
On Tue, Jun 27, 2017 at 7:19 PM, Adam Haile<EMAIL_ADDRESS>wrote:

@adammhaile commented on this pull request.
In bibliopixel/drivers/ledtype.py
https://github.com/ManiacalLabs/BiblioPixel/pull/252#discussion_r124339177
:

@@ -0,0 +1,25 @@
+from enum import IntEnum

+class LEDTYPE(IntEnum):

GENERIC = 0  # Use if the serial device only supports one chipset
LPD8806 = 1
WS2801 = 2

These are all the same

WS2811 = 3

Trust me. This is never changing. To you and I, yes, it's illogical. But
to our users it's necessary. For example... most users will call the WS2812
just "NeoPixel" which is just a Adafruit brand name for that chipset. But
also there is the WS2812B chipset which is the same protocol, different
form factor. Oh, and WS2811 which is the same exact protocol except not
built into the LED but in an 8 pin SOP IC package. The problem here is that
we've had users contact us and say "I have a WS2811 but you only support
WS2812, can you please support that?". So this avoid problems.
Another is APA102/APA102C/SK9822... it's all the same protocol despite
different names. Again, we'd have lots of questions. It's just easier to
add these duplicates in there because the users don't care what the
protocol is, just that they see the name for the chipset they have.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/252#discussion_r124339177,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdshmPcrLgbGw4xcg5g00z0L-OiyUbks5sITmPgaJpZM4OG6p1
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

AllPixel doesn't take names... it takes an integer value, which is why it's
done this way.
On Tue, Jun 27, 2017 at 2:12 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

I agree that the computation isn't changing. But you have mistaken the
data for the code.
These should be unique values - and then you should look up the code in a
table at the end.
In particular, as it is you can't go *backwards *from the LED type to the
name of the LED!
On Tue, Jun 27, 2017 at 7:19 PM, Adam Haile<EMAIL_ADDRESS>wrote:

@adammhaile commented on this pull request.
In bibliopixel/drivers/ledtype.py
<https://github.com/ManiacalLabs/BiblioPixel/pull/
252#discussion_r124339177>
:

@@ -0,0 +1,25 @@
+from enum import IntEnum

+class LEDTYPE(IntEnum):

GENERIC = 0 # Use if the serial device only supports one chipset
LPD8806 = 1
WS2801 = 2

These are all the same

WS2811 = 3

Trust me. This is never changing. To you and I, yes, it's illogical. But
to our users it's necessary. For example... most users will call the
WS2812
just "NeoPixel" which is just a Adafruit brand name for that chipset. But
also there is the WS2812B chipset which is the same protocol, different
form factor. Oh, and WS2811 which is the same exact protocol except not
built into the LED but in an 8 pin SOP IC package. The problem here is
that
we've had users contact us and say "I have a WS2811 but you only support
WS2812, can you please support that?". So this avoid problems.
Another is APA102/APA102C/SK9822... it's all the same protocol despite
different names. Again, we'd have lots of questions. It's just easier to
add these duplicates in there because the users don't care what the
protocol is, just that they see the name for the chipset they have.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
252#discussion_r124339177>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAPdshmPcrLgbGw4xcg5g00z0L-OiyUbks5sITmPgaJpZM4OG6p1>
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/252#issuecomment-311440628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6g_UiOmqHgDoPGlGSm_fHF7qPbLzks5sIUYmgaJpZM4OG6p1
.

It's certainly convenient, but in a better world, the fundamental types
would be different and mapped onto the internal mapping in AllPixel!
Not an issue, just a note.
On Tue, Jun 27, 2017 at 8:16 PM, Adam Haile<EMAIL_ADDRESS>wrote:

AllPixel doesn't take names... it takes an integer value, which is why it's
done this way.
On Tue, Jun 27, 2017 at 2:12 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

I agree that the computation isn't changing. But you have mistaken the
data for the code.
These should be unique values - and then you should look up the code in a
table at the end.
In particular, as it is you can't go *backwards *from the LED type to the
name of the LED!
On Tue, Jun 27, 2017 at 7:19 PM, Adam Haile<EMAIL_ADDRESS>wrote:

@adammhaile commented on this pull request.
In bibliopixel/drivers/ledtype.py
<https://github.com/ManiacalLabs/BiblioPixel/pull/
252#discussion_r124339177>
:

@@ -0,0 +1,25 @@
+from enum import IntEnum

+class LEDTYPE(IntEnum):

GENERIC = 0 # Use if the serial device only supports one chipset
LPD8806 = 1
WS2801 = 2

These are all the same

WS2811 = 3

Trust me. This is never changing. To you and I, yes, it's illogical.
But
to our users it's necessary. For example... most users will call the
WS2812
just "NeoPixel" which is just a Adafruit brand name for that chipset.
But
also there is the WS2812B chipset which is the same protocol, different
form factor. Oh, and WS2811 which is the same exact protocol except not
built into the LED but in an 8 pin SOP IC package. The problem here is
that
we've had users contact us and say "I have a WS2811 but you only
support
WS2812, can you please support that?". So this avoid problems.
Another is APA102/APA102C/SK9822... it's all the same protocol despite
different names. Again, we'd have lots of questions. It's just easier
to
add these duplicates in there because the users don't care what the
protocol is, just that they see the name for the chipset they have.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
252#discussion_r124339177>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAPdshmPcrLgbGw4xcg5g00z0L-OiyUbks5sITmPgaJpZM4OG6p1>
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
252#issuecomment-311440628>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AA6a6g_UiOmqHgDoPGlGSm_fHF7qPbLzks5sIUYmgaJpZM4OG6p1>
.

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/252#issuecomment-311441435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsm10Wx60LjzqJAxreyCbL7L2ly6Wks5sIUbggaJpZM4OG6p1
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com


Update Python instructions (include venv)

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[x] The title, template, and date are all set
[x] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[x] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[x] Has passed bart check
[x] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[x] Headings are using Title Case
[x] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[x] Have tested with npm run test and resolved all errors
[x] Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

Thanks @dicej - I have a new issue in the docs to update the SDK and Componentize-Py versions at https://github.com/fermyon/developer/issues/1254
Thank you for the review and the information.

Thanks @dicej - this has been updated now. Something going on with the build for cloud preview, but that shouldn't effect anything (i.e. we can still approve/merge and ignore the cloud preview build error for now)


Feature - HR/Manager - Improving department for HR and Manager

Description
The current flow for HR where they can enter their department after being upgraded doesn't really guard Privacy properly. We can handle this on the admin side for now, but we will need a different flow at some point.
I think the best flow would simply be to require the department to be in place before the account gets upgraded.
I think this might also be tied to us duplicating the department property across manager and HR. More basically though, we need a better way for Admins to set the department. Ideally in the same place that admins upgrade their User account. But that again would require the department field be on the user and not manager or HR

Resolved by #2846


Clarify how to subscribe

I couldn't figure out how to subscribe in the Google Groups UI, so I googled it. Hopefully with this PR others won't have to.

Thanks!


wasi-nn: remove Git submodule

To more closely align with the conventions in the wasmtime-wasi and wasmtime-wasi-http crates, this change removes the Git submodule that previously provided the WIT and WITX files for wasmtime-wasi-nn. Like those other crates, the syncing of wasi-nn WIT and WITX files will happen manually for the time being. This is the first PR towards upgrading the wasi-nn implementation to match recent spec changes and better preview2-ABI compatibility.

Could you update this script to additionally vendor this WIT? That way we ideally have a single knob to flip to update when necessary and CI checks that we're matching upstream.


nawk: 20230909 -> 20230911

Description of changes

Note that this updates awk to the version as described in the Second Edition of "The AWK Programming Language"
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

❓ Should the homepage be updated to https://awk.dev?

Result of nixpkgs-review pr 254806 run on x86_64-linux 1

3 packages built:

nawk
noweb
noweb.tex

❓ Should the homepage be updated to https://awk.dev?

yes

I need to think about creating test files for awk.


Link not being sent upon requesting password be reset

3 different users have reported that they are not receiving a link when they request their password be reset (they confirmed checking their spam folders). I tested it using https://couchers.org/password-reset and it worked for me, so perhaps this could be an intermittent issue?

@aapeliv @AndrewFarley Can this be closed?

I think we've determined it is okay, re-open if needed


ARD - URL-format changed

German ARD changed their URL format, and downloading with youtube-dl needs workarounds now.
They flipped the position of bcastID and documentID.
Example: http://www.ardmediathek.de/tv/Nachtmagazin/nachtmagazin/Das-Erste/Video?bcastId=331152&documentId=33606140
First try:
>youtube-dl -F --print-traffic -v http://www.ardmediathek.de/tv/Nachtmagazin/nac
htmagazin/Das-Erste/Video?bcastId=331152&docum
entId=33606140
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-F', u'--print-traffic', u'-v', u'http://www.ardme
diathek.de/tv/Nachtmagazin/nachtmagazin/Das-Erste/Video?bcastId=331152']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2016.02.22
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-73361-g03b2b40, ffprobe N-73361-g03b2b40, rtmpdum
p 2.4
[debug] Proxy map: {}
[ARD:mediathek] Video: Downloading webpage
send: u'GET /tv/Nachtmagazin/nachtmagazin/Das-Erste/Video?bcastId=331152 HTTP/1.
1\r\nHost: www.ardmediathek.de\r\nAccept-Language: en-us,en;q=0.5\r\nAccept-Enco
ding: gzip, deflate\r\nAccept: text/html,application/xhtml+xml,application/xml;q
=0.9,*/*;q=0.8\r\nUser-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/201
50101 Firefox/44.0 (Chrome)\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\
nConnection: close\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'
header: Server: Apache-Coyote/1.1
header: X-Robots-Tag: noindex,follow
header: Content-Type: text/html;charset=UTF-8
header: Content-Encoding: gzip
header: Content-Length: 9506
header: Date: Wed, 24 Feb 2016 15:27:41 GMT
header: Connection: close
header: Vary: Accept-Encoding
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPErro
r()); please report this issue on https://yt-dl.org/bug . Make sure you are usin
g the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl
 with the --verbose flag and include its complete output.
  File "youtube_dl\extractor\common.pyo", line 355, in _request_webpage
  File "youtube_dl\YoutubeDL.pyo", line 1905, in urlopen
  File "urllib2.pyo", line 437, in open
  File "urllib2.pyo", line 550, in http_response
  File "urllib2.pyo", line 475, in error
  File "urllib2.pyo", line 409, in _call_chain
  File "urllib2.pyo", line 558, in http_error_default

'documentId' is not recognized as an internal or external command,
operable program or batch file.

Running youtube-dl with the URL in quotes
>youtube-dl -F --print-traffic -v "http://www.ardmediathek.de/tv/Nachtmagazin/nachtmagazin/Das-Erste/Video?bcastId=331152&documentId=33606140"
or manually flipping the two parameters works around this problem.
>youtube-dl -F --print-traffic -v http://www.ardmediathek.de/tv/Nachtmagazin/nachtmagazin/Das-Erste/Video?documentId=33606140&bcastId=331152

It has nothing to do with arguments' position in query. You must always put URL in quotes when & is present.

Alright, thank you.


Update background check failed

I recently noticed that I got several alerts about this error and idk if this is normal or not, just in case, i'll post it here

This issue occurs even when there is no networking enabled. Pretty much every other app (that I use) avoids doing any networking when WiFi and Mobile Data are disabled, which for me leads to a better UX.

No, that's completely wrong. It does avoid doing networking when a network isn't available, unless you disabled the OS connectivity checks.

Maybe it's a semantic thing. It's not (just) that a network isn't available, networking may be disabled completely on my device and the App Store tries to check anyway.
I do have the Internet connectivity checks set to off.

@Cocolin67

Thing is, network on my phone is always on, when wifi is not available, it switches to mobile data, that's why I found it weird sometimes but so from what I understand : it did a background check with no network available right ?

App Store only runs the background update job when network access is available according to the OS. It even has a pause to wait for the network to become available to work around VPN apps saying that it's available before it is.
Your post above shows BOTH Wi-Fi and mobile data are available.

It is in fact on.

That's the issue. You've disabled the OS feature which makes network-dependent jobs only run when a network is available. On the stock OS, there's no toggle to disable it.

So when Internet connectivity checks is set to off, the service/api is flagging that it's OK to use the network when WiFi and Mobile data are both disabled?


Incorrect documentation for PIXI.Program.from

Documentation for PIXI.Program.from is incorrect. JSDoc says that the signature is (vertexSrc: string, fragmentSrc: string, uniforms: object), when the expected signature is (vertexSrc: string, fragmentSrc: string, name: string).

pixi.js version:  5.1.5
Browser & Version: n/a
OS & Version: n/a
Running Example: https://github.com/pixijs/pixi.js/blob/dev/packages/core/src/shader/Program.js#L225

PR welcome to fix this. good catch.


[Awaiting #62] Use current Swift version to fetch frameworks from cached manifest

Closes #63. Builds on #62 and should be rebased once that PR is merged.

Changes to #62 are only in last two commits...


intellisesne isn't working with .pyc modules

Environment data

Language Server version: 2020.8.1
OS and version: Windows 10
Python version: Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:32:41) [MSC v.1900 64 bit (AMD64)] on win32

Expected behaviour
When provided path to folder containing .pyc files in setting python.analysis.extraPaths intellisense should provide list of methods for modules in that folder.
Actual behaviour
Intellisense isn't able to resolve compiled modules (.pyc). It shows error -> Import "hello" could not be resolvedPylance (reportMissingImports). On based of reading else where I was under the impression that pylance can scrap info from .pycs to provide intellisense. Please correct me if I am wrong. I am using following command to compile
python.exe -m compileall -b ..\library\hello.py
I am attaching pseudo code intellisesne_pyc.zip. This folder contains workspace folder and library folder. The code in workspace folder imports module in library folder that is compiled. I hope this helps.
intellisesne_pyc.zip

Pylance cannot read info from compiled modules, no. Compiled code currently requires a sub to work, and we will not try and execute the compile code to learn of its contents. Note that MPLS didn't do this either for user code, but would for libraries.

Pylance does not attempt to extract type information from binary files. The interface to native files needs to be described with a type stub ("pyi") file. Many library authors are now providing such stubs with the latest versions of their packages, so please check that you have the latest version installed. If the latest version of the library is missing the stub, I encourage you to submit a request to the library author.

Thank you for the quick reply. I am the library author and was experimenting with VS code configuration as if I am the user of library. We are already generating pyi files for pyds. We are using pybind11 tools to do that. I was expecting pyc to work out of the box. I will look into tools to generate pyi file. Please let me know if you have any recommendations.

#166 has a similar discussion. Producing stubs from the pyc files isn't advisable as they don't really contain the right kind of info. You may have a better experience writing the pyi files directly (this is what is being done in numpy, torch, etc), but I'm not sure what the size of your project is.

Pylance cannot read info from compiled modules, no. Compiled code currently requires a stub to work, and we will not try and execute the compile code to learn of its contents. Note that MPLS didn't do this either for user code, but would for libraries.

@jakebailey I got wrong impression because this comment https://github.com/microsoft/python-language-server/issues/1081#issuecomment-498068163. When I read that comment again I think it was in context of Jedi LS. Probably it works with Jedi?

As far as I know, Jedi does not enable its "scraper" mode by default, and requires user configuration to allow it.

Investigating solutions for compiled modules

a new repo for stub is available at python-type-stubs. This is open for contributions. Snapshots from here will be periodically shipped with Pylance.
This is the place to add stubs for compiled modules. As mentioned above, Pylance will not scrape compiled modules.

a new repo for stub is available at python-type-stubs. This is open for contributions. Snapshots from here will be periodically shipped with Pylance.
This is the place to add stubs for compiled modules. As mentioned above, Pylance will not scrape compiled modules.

@judej What about cython files that the user writes (i.e. ones that are not provided by external libraries). Shouldn't pylance try to get typing information from them (similar to how it "guesses" typing information of user-python code)?

Any updates on this?
I know in the end it won't make a difference since python will call compiled functions anyways but it would be very nice to have type hinting and auto-completion on imported cython modules, specially for people making projects that contain both .py and .pyx files

Our solution to this problem is to write type stubs. You can read more about it here:
https://microsoft.github.io/pyright/#/type-stubs?id=importance-of-type-stub-files
Pyright/Pylance is a static type checker that reads python files. It can't crack open pyc files to figure out what the methods or types are in the pyc file. We don't run any python code so we couldn't do something like described here:
https://stackoverflow.com/questions/32562163/how-can-i-understand-a-pyc-file-content.

Scipy is an example where type stubs are provided for pyc files:
https://github.com/scipy/scipy/blob/main/scipy/linalg/_cythonized_array_utils.pyi
That file describes the public types in the pyx file:
https://github.com/scipy/scipy/blob/main/scipy/linalg/_cythonized_array_utils.pyx

Hi I am facing a similar issue
I package my python application into a wheel file .pyc and .pyi files
Pylance reports the following error since it expects .py files
Import "module.path" could not be resolved from sourcePylance[reportMissingModuleSource](https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportMissingModuleSource)
If I add a pyright config to the root of my project as follows, it seems to resolve my issue
{
    "reportMissingModuleSource": false
}

However I was wondering if any config could be added to include .pyc files when checking for the module path alone, I have both pyc and pyi files in the same directory

@abishek-rz, I posted your comment as a new issue. It seems reasonable to me that if a pyc file exists that matches a pyi file, we shouldn't output the reportMissingModuleSource error.


toolkit: add chatbot response regeneration

Description

Added ability to regenerate chatbot responses

AI Description

This PR introduces a new feature for message regeneration, allowing users to regenerate the last message sent by a specific agent within a conversation. The changes are as follows:

src/backend/crud/message.py: A new function, delete_messages, is added to delete messages by IDs. It takes a list of message IDs and a user ID as arguments and deletes the corresponding messages from the database.
src/backend/routers/chat.py: The process_message_regeneration function is added to process message regeneration. It retrieves the last message sent by the specified agent, attaches files to messages, and returns a tuple containing necessary data to regenerate the message.
src/backend/services/chat.py: The process_message_regeneration function is added to process message regeneration. It retrieves the last message sent by the specified agent, attaches files to messages, and returns a tuple containing necessary data to regenerate the message.
src/backend/tests/unit/crud/test_message.py: A new test, test_delete_messages, is added to test the deletion of multiple messages by IDs. It creates three messages, deletes them, and verifies that they are no longer present in the database.
src/backend/tests/unit/routers/test_chat.py: Two new tests, test_stream_regeneration_existing_chat and test_stream_regeneration_existing_chat_without_user_messages, are added to test the regeneration of chat streams for existing conversations with and without user messages.
src/interfaces/assistants_web/src/app/share/[id]/ReadOnlyConversation.tsx: The isReadOnly prop is added to the ReadOnlyConversation component to indicate whether the conversation is read-only.
src/interfaces/assistants_web/src/assets/icons/Regenerate.tsx: A new icon component, Regenerate, is added to represent the regeneration action. It imports React and SVG-related modules and exports a React functional component that renders an SVG path.
src/interfaces/assistants_web/src/assets/icons/index.ts: The Regenerate icon is exported for use in other components.
src/interfaces/assistants_web/src/cohere-client/client.ts: The regenerate property is added to the CohereClient class to enable message regeneration. The getChatStreamEndpoint method is modified to include the /regenerate endpoint when regenerate is true.
src/interfaces/assistants_web/src/components/Conversation/Conversation.tsx: The handleRegenerate prop is added to the Conversation component to handle message regeneration.
src/interfaces/assistants_web/src/components/MessageRow/MessageRow.tsx: The isBotMessage function is added to determine if a message is from a bot. The isRegenerationEnabled function is added to check if message regeneration is enabled. The onRegenerate prop is added to the MessageRow component to handle message regeneration.
src/interfaces/assistants_web/src/components/MessagingContainer/MessagingContainer.tsx: The onRegenerate prop is added to the MessagingContainer component to handle message regeneration.
src/interfaces/assistants_web/src/components/UI/CopyToClipboardButton.tsx: The duration and hoverDelay props are added to the CopyToClipboardIconButton component to control the duration and hover delay of the tooltip.
src/interfaces/assistants_web/src/components/UI/Icon.tsx: The Regenerate icon is added to the IconList for use in the getIcon function.
src/interfaces/assistants_web/src/components/UI/Input.tsx: The duration prop is added to the Input component to control the duration of the tooltip.
src/interfaces/assistants_web/src/hooks/use-chat.ts: The handleRegenerate function is added to handle message regeneration. It finds the latest user message, checks if streaming is active, and regenerates the message if conditions are met.
src/interfaces/assistants_web/src/hooks/use-streamChat.ts: The regenerate property is added to the useStreamChat hook to enable message regeneration.
src/interfaces/assistants_web/src/types/message.ts: The isBotMessage function is added to determine if a message is from a bot.

@danylo-boiko Thank you for this contribution! We will review it as soon as we can

@danylo-boiko merging, thanks!


Support stable remotePattern option

The remotePatterns option is going to be promoted to stable, and so will no longer be in the experimental object (https://github.com/vercel/next.js/commit/4cc7f11da2194aa9ffce4e04b8a0c6ee340f4f85#diff-a9aa71ef3757abaca165c8b1b8726b6d3aca8f95c9db3f12ac9176aadfd0c7f8L400) so we need to support both.

test


Improve instructions for exercise leads

how to enable automated testing
how to avoid notifications when creating within coderefinery organization

set generated repo to public


WIP: Upgrade deps to match k8s 1.17 - [closed]

In GitLab by @arcln on Dec 5, 2019, 22:43
Merges develop -> fix/deps

In GitLab by @arcln on Dec 5, 2019, 22:44
closed


DEC DE implementation and tests

Coverage increased (+0.02%) to 98.966% when pulling 4ee2057734ae14d52d0930aa412b79ffde026ffc on decde-implementation into 1382ec98db67fa968d4724c1cea2a5504cac9b0a on master.


Add HenryBrooker's file

created a branch, created a file and made a commit, and opened a pull request


[WIP] UCP: Add Tracing to Coprocessor

UCP #5714
What have you changed?
Add some OpenTracing info in coprocessor requests.
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

Yes
Does this PR affect tidb-ansible?

No

@sre-bot /release make dist_release

@sre-bot /bench +sysbench +tpcc +tpch

/release make dist_release

@sre-bot /release make dist_release

@sre-bot /bench +sysbench +tpcc +tpch

@sre-bot /sysbench

@sre-bot /bench +sysbench

@sre-bot  /release make dist_release

@sre-bot /release make dist_release

@sre-bot /bench +sysbench

@sre-bot /release make dist_release

@sre-bot /bench +sysbench

@sre-bot /release make dist_release

@sre-bot /run-all-tests

@sre-bot /bench +sysbench +tpcc +tpch

@sre-bot /run-all-tests

@sre-bot /run-all-tests

@sre-bot /run-all-tests

@sre-bot /release make dist_release

@sre-bot /bench +sysbench +tpcc +tpch

@sre-bot /release make dist_release

@sre-bot /bench +sysbench +tpcc +tpch

@sre-bot /release make dist_release

@sre-bot /bench +sysbench +tpcc +tpch

@sre-bot /bench +sysbench +tpch

@sre-bot /run-all-tests

@sre-bot /release make dist_release

@sre-bot /bench +tpch

@sre-bot /bench +tpch

@sre-bot /release make dist_release

@sre-bot /bench +tpch

@sre-bot /release make dist_release

@sre-bot /bench +tpch

/bench +tpch


Symbolic breakpoint crashes app.

I've been enjoying Freddy, and have been using a symbolic breakpoint on JSON.Error. However my app started crashing in strange ways. I get an EXC_BREAKPOINT in my main thread in the runloop:
callq  0x108f85468               ; symbol stub for: getpid.
I'm using Freddy in another thread. If I look at that thread, it's always halted on a line decoding JSON. If I 'po' the code on this line the JSON decodes normally.
If I continue running, the main thread receives a SIGKILL.
If I turn off the symbolic breakpoint, the app runs without error.
Has anyone ever experienced this problem? Thanks.

Can you provide details of what your breakpoint is doing? Additional stack frames from the main thread?
I have encountered this problem with breakpoints before in projects with no use of Freddy. I think it's an Xcode/LLDB/iOS quirk of some kind, but I've never been able to fully track it down.

Closing due to lack of information. Please feel free to reopen if this is still an issue.


Spyder do not start in hard way mode

Description of your problem
I am trying to install spyder without conda, following the steps of hard way. The reason is that only with the specified packages of python the size of installation is 493 mb, but with miniconda the size with the same modules is 2.4 gb. The problem is that when I use the command (python bootstrap.py) the program starts the checkout, it says bootstrap completed in... but Python popup windows appears saying that there is a problem with python and needs to be closed.
What steps will reproduce the problem?

After all packages installed, run the command (python bootstrap.py) gives python crash problem after checkout. The checkout have all the step, and appears to be correct
Trying directly with the spyder.exe do not do nothing.

What is the expected output? What do you see instead?
Please provide any additional information below
I will try the other distributions of spyder, with python x,y and I have the same problem, with WinPython using the Prompt program I obtain the same crash python problem... but with miniconda runs correctly, but I prefer the hard way. I uninstall some packages of my installation to do a downgrade of some packages (like html5lib==0.999) because in miniconda uses this package instead of html5lib==0.999999999 but the same result.
Versions and main components

Spyder Version: 3.1.3
Python Version: 3.6.1 v.1900 32 bit
Qt Version: QtPy==1.2.1
PyQt Version: PyQt5==5.8.2
Operating system: Windows 7 Enterprise x64
List of packages instaled:

alabaster==0.7.10
appdirs==1.4.3
asn1crypto==0.22.0
astroid==1.4.9
Babel==2.4.0
bleach==2.0.0
cffi==1.10.0
chardet==2.3.0
colorama==0.3.7
cryptography==1.8.1
cycler==0.10.0
Cython==0.25.2
decorator==4.0.11
docutils==0.13.1
entrypoints==0.2.2
html5lib==0.999999999
idna==2.5
imagesize==0.7.1
ipykernel==4.6.0
ipython==5.3.0
ipython-genutils==0.2.0
isort==4.2.5
jedi==0.10.2
Jinja2==2.9.6
jsonschema==2.6.0
jupyter-client==5.0.1
jupyter-core==4.3.0
lazy-object-proxy==1.2.2
MarkupSafe==1.0
matplotlib==2.0.0
mccabe==0.6.1
mistune==0.7.4
mpmath==0.19
nbconvert==5.1.1
nbformat==4.3.0
numpy==1.12.1
numpydoc==0.6.0
packaging==16.8
pandas==0.19.2
pandocfilters==1.4.1
pep8==1.7.0
pickleshare==0.7.4
pip-review==0.5.3
prompt-toolkit==1.0.14
psutil==5.2.2
pyasn1==0.2.3
pycparser==2.17
pyflakes==1.5.0
Pygments==2.2.0
pylint==1.6.5
pyOpenSSL==16.2.0
pyparsing==2.2.0
PyQt5==5.8.2
python-dateutil==2.6.0
pytz==2017.2
pyzmq==16.0.2
QtAwesome==0.4.4
qtconsole==4.3.0
QtPy==1.2.1
requests==2.13.0
rope-py3k==0.9.4.post1
simplegeneric==0.8.1
sip==4.19.2
six==1.10.0
snowballstemmer==1.2.1
Sphinx==1.5.5
spyder==3.1.3
sympy==1.0
testpath==0.3
tornado==4.4.3
traitlets==4.3.2
wcwidth==0.1.7
webencodings==0.5.1
wrapt==1.10.10
I do not know the reason for this crash. Any ideas?
Thank you for the program.

but with miniconda runs correctly, but I prefer the hard way

I'm very sorry to say this, if you want to go the hard way, it's up to you to find out what's happening and fix it. This is because the hard way is for experts only, i.e. those who have intimate knowledge of all Spyder dependencies.


All listed short references in the Result page (Table) should be listed at the end of that page

in addition also clickable like in the single society page. Otherwise the user has no chance to get the actual title of this short reference.

Yes, I agree. Right now the short ref --> long reference table is part of the downloadable codebook (Under "Data Sources" tab), but this is not very user friendly (or clear where to find).
On 17 Apr 2016 12:04 pm, Hans-Jörg Bibiko<EMAIL_ADDRESS>wrote:in addition also clickable like in the single society page. Otherwise the user has no chance to get the actual title of this short reference.
—You are receiving this because you are subscribed to this thread.Reply to this email directly or view it on GitHub

Do we still need to do this? I have done it, but it makes the society results page reaaally long. If we don't think it's necessary, I'll close this issue.

Hmm, we need a possibility for the user to get the information about a short reference à la "Wissler (1912)". I agree that a list at the end can be really long but one think of an API i.e. "Wissler (1912)" is a link; if the user clicks on it a page/window/whatever opens and the full reference will be shown. Maybe like Glottolog handles it:
from language http://glottolog.org/resource/languoid/id/zakh1243 you see Sun, Hongkai 1999 which opens http://glottolog.org/resource/reference/id/34534
By doing this we can establish a page where the user can search for references as well (ok, if the sources are tagged by name, year, title etc. of course) [later on]

I agree with @stefelisabeth, this is overloading that page massively so we should just have a page-per-source which is linked to by any short reference. I think this is #257.


chore: Update from _rust template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.789%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
72

Relevant Lines:
95

💛  - Coveralls


2D NavigationPolygon baked in editor produces Navigation map synchronization error in 4.3

Tested versions

Reproducible in v4.3.stable.official [77dcf97d8]
NOT reproducible in v4.2.1.stable.official [b09f793f5]

System information
Godot v4.3.stable - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6700 XT (RADV NAVI22) - 12th Gen Intel(R) Core(TM) i5-12400 (12 Threads)
Issue description
On a simple project (see MRP), I have a NavigationRegion2D (with a simple rectangular outline) and 2 Polygons.

When I launch my scene, I get an error :
E 0:00:00:0231   sync: Navigation map synchronization error. Attempted to merge a navigation mesh polygon edge with another already-merged edge. This is usually caused by crossing edges, overlapping polygons, or a mismatch of the NavigationMesh / NavigationPolygon baked 'cell_size' and navigation map 'cell_size'. If you're certain none of above is the case, change 'navigation/3d/merge_rasterizer_cell_scale' to 0.001.
  <Source C++>   modules/navigation/nav_map.cpp:990 @ sync()

cell_size values are equal and changing navigation/3d/merge_rasterizer_cell_scale to 0.001 has no effect.
Taking a closer look at the produced polygon, I can see this (I guess) problematic triangle :

The thing is, when I open the same project in 4.2.1 and I rebake the navigation map, the produced polygon does not have this problematic triangle, and then I don't have the error. Is it a regression ?
Steps to reproduce

Open MRP
Launch scene and look at output for the error

Minimal reproduction project (MRP)
MRP : mrp_navmapsynchroerror.zip

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Godot 4.2 forced position integer snapping, that was removed due to popular demand. In Godot 4.3 it allows to use floats and they can up and downscaled. So all the precision issues with certain layouts can now survive that would have been removed by the old integer snap. You need to snap or otherwise prevent those situations manually now.

Thanks for your answer. Could you tell me what settings I should modify to have integer snap ?

There is no direct setting but you can e.g. enable the editor snapping so that your positions are not running with some weird float numbers, that alone can help a lot.

To really fix this in scripts you would need to not only snap the vertices of the baked navmesh but also remove any "duplicates", and fix the polygon indices in turn if removed.
The reason why that tiny polygon that has rasterization issues even gets baked is because the general scale is tiny, that white "collision" shape has a lot of tiny small edges and the agent_radius bake size set to 7 is uneven so you end up with more issues to rasterize the resulting edges in the navigation map.

To really fix this in scripts alone you would need to not only snap the vertices of the baked navmesh but also remove any "duplicates", and fix the polygon indices in turn if removed.

Are there any obstacles to adding this process to the navigation mesh baking ? Maybe performances ?

Looking at the code of NavMeshGenerator2D::generator_bake_from_source_geometry_data(), it seems that clipper InflatePaths() function is called (line 957) but path_solution is not simplified then.
To quote clipper documentation (about SimplifyPaths() function):

This function is strongly recommended following offsetting (ie inflating/shrinking), especially when offsetting paths multiple times. Offsetting often creates tiny segments that don't improve path quality.

I (humbly) believe that calling this method could prevent some tiny triangle issues. Moreover, it could improve baking performances since some boolean operations are then performed on path_solution.
What do you think about this ?

I remember I had some commented-out remnant code using the clipper simplification (RamadaDouglasClass or something back then) and while it worked for some cases it mess-upa lot of others so I removed it again. That was a while ago so if someone else wants to spend time on re-testing this be my guest.

I added a call to SimplifyPaths() after InflatePaths() :
if (agent_radius_offset > 0.0) {
    path_solution = InflatePaths(path_solution, -agent_radius_offset, JoinType::Miter, EndType::Polygon);
    path_solution = SimplifyPaths(path_solution, 1.0);
}

With this line of code, the error disappears on the MRP.
I have 2 questions :

SimplifyPaths() needs a epsilon parameter. On my test, I choose epsilon = 1.0, but I wonder what I could use as a more appropriate value. Do you think cell_size could do the job ?
Where could I find some projects to test this change ?

Ok thanks, I tried the nav_mesh_chunks project.
It seems that, when agent radius is equal to 11.0, I get the navigation synchronization error. The project behaves the same in 4.3 and with my modification.
Could you please tell me where I can find information about cell size ? What is it for ? Where is it used ?

The cell sizes is used by the navigation map to rasterize the navigation mesh edges by edge key in order to merge them. In 3D it is also used to define the voxel cell size for the baking.


Adding support for UPnP events

This pull request adds support for UPnP events subscribing, so more info can be retrieved from the TV, in real time. To make it work you need to:

Initiate the server (this is an async method): await rc.async_create_server()
Replace rc.on_event, which is also async and takes two arguments, service (the name of the service) and properties (the changed properties), to handle the incoming data from the events you subscribe to
Subscribe to the service of your desire with rc.upnp_service_subscribe(event), unsubscribe with rc.upnp_service_unsubscribe(event) or resubscribe with rc.upnp_service_resubscribe(event).

A valid service/event is, for example 'nrc/event_0', which sends info such as the TV state (eg on, off) and the current app (eg vc_app:1:product_id=0010000200000001:Netflix)
Suggestions are welcome!

you are awesome! thank you!


Regression: CustomCall with side effect gets optimized out

Since JAX 0.3.15, our MPI CustomCalls are getting optimized out even though they are declared as having side effects (has_side_effect=True).
Example:
import os
os.environ["MPI4JAX_DEBUG"] = "1"

import jax
import jax.numpy as jnp

from mpi4py import MPI
from mpi4jax import send

comm = MPI.COMM_WORLD
assert comm.Get_size() == 1

@jax.jit
def send_jit(x):
    send(x, dest=0, comm=comm)

print("send without JIT")
send(jnp.ones(10), dest=0, comm=comm)

print("send with JIT")
send_jit(jnp.ones(10))

With jax==0.3.15, the second call prints no debug information, indicating that send is being optimized out:
send without JIT
r0 | ie1Jnxae | MPI_Send -> 0 with tag 0 and 10 items
r0 | ie1Jnxae | MPI_Send done with code 0 (4.43e-05s)
send with JIT

With jax==0.3.14 I get the expected output:
send without JIT
r0 | NCAn8Kbh | MPI_Send -> 0 with tag 0 and 10 items
r0 | NCAn8Kbh | MPI_Send done with code 0 (3.68e-05s)
send with JIT
r0 | Cn7a5QRb | MPI_Send -> 0 with tag 0 and 10 items
r0 | Cn7a5QRb | MPI_Send done with code 0 (5.04e-06s)

I double checked the optimized HLO and it's still there:
Pre-compiled HLO
HloModule jit_send_jit.1, entry_computation_layout={(f32[10]{0})->f32[10]{0}}

xla_fallback_send_mpi.3 {
  constant.6 = s32[] constant(10)
  Arg_0.4 = f32[10]{0} parameter(0)
  constant.7 = s32[] constant(0)
  constant.8 = u64[] constant(139673914379968)
  constant.9 = u64[] constant(139673914351872)
  Arg_1.5 = token[] parameter(1)
  custom-call.10 = (token[]) custom-call(constant.6, Arg_0.4, constant.7, constant.7, constant.8, constant.9, Arg_1.5), custom_call_target="mpi_send", custom_call_has_side_effect=true
  ROOT get-tuple-element.11 = token[] get-tuple-element(custom-call.10), index=0
}

send_mpi.12 {
  Arg_0.13 = f32[10]{0} parameter(0)
  Arg_1.14 = token[] parameter(1)
  ROOT call.15 = token[] call(Arg_0.13, Arg_1.14), to_apply=xla_fallback_send_mpi.3
}

ENTRY main.17 {
  ROOT Arg_0.1 = f32[10]{0} parameter(0)
  after-all.2 = token[] after-all()
  call.16 = token[] call(Arg_0.1, after-all.2), to_apply=send_mpi.12
}

Optimized HLO:
HloModule jit_send_jit.2, entry_computation_layout={(f32[10]{0})->f32[10]{0}}

ENTRY %main.17 (Arg_0.1: f32[10]) -> f32[10] {
  %constant.4 = s32[] constant(10)
  %Arg_0.1 = f32[10]{0} parameter(0)
  ROOT %copy = f32[10]{0} copy(f32[10]{0} %Arg_0.1)
  %constant.5 = s32[] constant(0)
  %constant.10 = u64[] constant(139673914379968)
  %constant.11 = u64[] constant(139673914351872)
  %after-all.2 = token[] after-all(), metadata={op_name="jit(send_jit)/jit(main)/create_token" source_file="/usr/local/google/home/sharadmv/workspace/mpi4jax/mpi4jax/_src/collective_ops/send.py" source_line=54}
  %custom-call.1 = (token[]) custom-call(s32[] %constant.4, f32[10]{0} %copy, s32[] %constant.5, s32[] %constant.5, u64[] %constant.10, /*index=5*/u64[] %constant.11, token[] %after-all.2), custom_call_target="mpi_send", custom_call_has_side_effect=true, metadata={op_name="custom-call.8"}
}

I think this is an async issue (the Python program is ending before the message can happen).
I was able to get it to show up in this repro:
import os
os.environ["MPI4JAX_DEBUG"] = "1"

import jax
import jax.numpy as jnp

from mpi4py import MPI
from mpi4jax import send

comm = MPI.COMM_WORLD
assert comm.Get_size() == 1

@jax.jit
def send_jit(x):
    send(x, dest=0, comm=comm)
    return x

print("send without JIT")
send(jnp.ones(10), dest=0, comm=comm)

print("send with JIT")
send_jit(jnp.ones(10)).block_until_ready()

Output:
r0 | 9zBLijKJ | MPI_Send -> 0 with tag 0 and 10 items
r0 | 9zBLijKJ | MPI_Send done with code 0 (2.90e-05s)
send with JIT
r0 | LyW0FOeZ | MPI_Send -> 0 with tag 0 and 10 items
r0 | LyW0FOeZ | MPI_Send done with code 0 (7.85e-06s)

Huh. Actually, mpi4jax registers an atexit handler to prevent this kind of stuff:
def flush(platform):
    """Wait for all pending XLA operations"""
    devices = jax.devices(platform)

    for device in devices:
        # as suggested in jax#4335
        noop = jax.device_put(0, device=device) + 0
        noop.block_until_ready()

Is that not sufficient anymore to wait for all async operations? 🤔

That doesn't seem to be it. I get the same behavior even if I add a 10 second sleep in the end:
import os
os.environ["MPI4JAX_DEBUG"] = "1"

import jax
import jax.numpy as jnp

from mpi4py import MPI
from mpi4jax import send

comm = MPI.COMM_WORLD
assert comm.Get_size() == 1

def flush(platform):
    """Wait for all pending XLA operations"""
    devices = jax.devices(platform)

    for device in devices:
        # as suggested in jax#4335
        noop = jax.device_put(0, device=device) + 0
        noop.block_until_ready()

# send to non-existing rank
@jax.jit
def send_jit(x):
    send(x, dest=0, comm=comm)

print("send without JIT")
send(jnp.ones(10), dest=0, comm=comm)

print("send with JIT")
send_jit(jnp.ones(10))

import time
time.sleep(10)

Actually, it works for any return argument that is not None:
# works
@jax.jit
def send_jit(x):
    send(x, dest=0, comm=comm)
    return 0

# nope
@jax.jit
def send_jit(x):
    send(x, dest=0, comm=comm)
    return None

Do functions that don't return anything get optimized away since recently?

I'm trying to run your repro but it just hangs for me.
I did:
$ apt install libmpich-dev
$ git clone https://github.com/mpi4jax/mpi4jax.git
$ cd mpi4jax
$ git fetch origin pull/151/head
$ git checkout FETCH_HEAD
$ pip install -e .

and then tried running your repro:
$ python m.py
send without JIT
WARNING:absl:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
r0 | yrpTbyMM | MPI_Send -> 0 with tag 0 and 10 items

At this point it hangs apparently forever.
What am I doing wrong?

Sorry, my bad. Because the example code sends without receiving, it will deadlock with many MPI providers.
Here's one that should work for all setups:
import os
os.environ["MPI4JAX_DEBUG"] = "1"

import jax
import jax.numpy as jnp

from mpi4py import MPI
from mpi4jax import sendrecv

comm = MPI.COMM_WORLD
assert comm.Get_size() == 1

@jax.jit
def sendrecv_jit(x):
    sendrecv(x, x, source=0, dest=0, comm=comm)

print("sendrecv without JIT")
sendrecv(jnp.ones(10), jnp.ones(10), source=0, dest=0, comm=comm)

print("sendrecv with JIT")
sendrecv_jit(jnp.ones(10))

import time
time.sleep(10)

Output:
sendrecv without JIT
r0 | 05WTiqzD | MPI_Sendrecv <- 0 (tag -1, 10 items) / -> 0 (tag 0, 10 items)
r0 | 05WTiqzD | MPI_Sendrecv done with code 0 (3.26e-05s)
sendrecv with JIT

After adding return 0 to sendrecv_jit:
sendrecv without JIT
r0 | 05WTiqzD | MPI_Sendrecv <- 0 (tag -1, 10 items) / -> 0 (tag 0, 10 items)
r0 | 05WTiqzD | MPI_Sendrecv done with code 0 (3.26e-05s)
sendrecv with JIT
r0 | XoGaYz72 | MPI_Sendrecv <- 0 (tag -1, 10 items) / -> 0 (tag 0, 10 items)
r0 | XoGaYz72 | MPI_Sendrecv done with code 0 (3.92e-06s)

@sharadmv I think the bug is here:
https://github.com/google/jax/blob/c08b4ee6d9a13787c16bcf867d04e04d81fca063/jax/_src/dispatch.py#L329
note that jaxpr.outvars is empty, and a custom call with a side effect isn't considered to have a jaxpr effect. I suspect we need to treat effectful custom calls as effectful for jaxpr purposes as well?

I see. You need to define your primitives to be effectful. To do that, use:
effect = <some hashable>
def _effectful_abstract_eval(...):
  return ..., {effect}
prim.def_effectful_abstract_eval(_effectful_abstract_eval)
from jax.interpreters import mlir

mlir.lowerable_effects.add(effect)

This will automatically make any jaxpr that contains these primitives have an effect and we will bypass the check that Peter mentioned.
An added benefit will be that you no longer need to use your atexit handler. Instead you can call jax.effects_barrier() which does the same thing.

That seems to work, thanks.
What are the semantics of the effect object? Can I re-use the same object for all primitives?

The effect object can be any hashable (internally we use enums usually). It functions as tag that shows up in jaxprs (in jaxpr.effects). You can re-use it for whichever primitives you want this blocking behavior for.

@sharadmv Would it be posssible to make from jax._src.lax import control_flow as lcf part of the public/exported API? We have several users and would like to avoid mpi4jax breaking too often because we rely on internal things.
If this is part of the API necessary to define custom effectfull primitives, then it might make sense to have it in the public API.

The custom effectful primitive API is considered internal and experimental and will likely change in the future. We can't at the moment promise a public, stable interface. Using custom JAX primitives is also technically internal / unstable (although probably less likely to dramatically change than the new effects system).
I initially recommended an unstable solution because I was under the impression that mpi4jax was okay being broken by JAX internal changes given the existing dependence on primitives.
An alternate, stable solution would be to do manual token threading (this is what the effects system current does underneath the hood) and to block on the output tokens:
@jax.jit
def sendrecv_jit(token, x):
    sendrecv(x, x, source=0, dest=0, comm=comm)
    return token

token can be something as simple as a zero-length array (np.zeros(0, np.bool_) for example) and is just needed to block on the computation. You can look at this design note which informed the current effect system's design.

@sharadmv Thanks for the clarification. We actually already do token threading to enforce order of our primitives, and it's sort of a major pain. So this piqued my interest:

An alternate, stable solution would be to do manual token threading (this is what the effects system current does underneath the hood)

So the effects system actually does automated token tracking? In this case we could just abandon our manual token threading, which would be amazing. But kind of hard to depend on if this is an unstable feature... 🤔

An alternate, stable solution would be to do manual token threading (this is what the effects system current does underneath the hood) and to block on the output tokens:

This is not really an option right now because we'd have to force users to weave tokens themselves in and out of jitted functions, which we are severely trying to avoid.

The custom effectful primitive API is considered internal and experimental and will likely change in the future. We can't at the moment promise a public, stable interface. Using custom JAX primitives is also technically internal / unstable (although probably less likely to dramatically change than the new effects system).

Ah, ok. We have several downstream users so we try to rely on as stable APIs as possible. The current iteration of mpi4jax has persisted practically unbroken for 12+ months (if not for reshuffling of your API entry points), and I would be happy if this could continue.
I was under the impression that jax.core is part of the public API, and since jax.core.Primitive is there as well I expected that to be stable. This is why I asked to make control_flow stable as well.
But if that's not the case it's good to know.

I was under the impression that jax.core is part of the public API, and since jax.core.Primitive is there as well I expected that to be stable. This is why I asked to make control_flow stable as well.

The official list of public modules is available here.

Ah, ok. We have several downstream users so we try to rely on as stable APIs as possible. The current iteration of mpi4jax has persisted practically unbroken for 12+ months (if not for reshuffling of your API entry points), and I would be happy if this could continue.

Is it possible to release mpi4jax versions with pinned JAX/jaxlibs?

That's certainly an option. Thanks for the support @sharadmv.


chore: improve cli

Codecov Report

Merging #117 into master will increase coverage by 0.2%.
The diff coverage is 34.78%.

@@            Coverage Diff            @@
##           master     #117     +/-   ##
=========================================
+ Coverage   25.29%   25.49%   +0.2%
=========================================
  Files          90       91      +1
  Lines        2305     2310      +5
  Branches      296      298      +2
=========================================
+ Hits          583      589      +6
+ Misses       1715     1713      -2
- Partials        7        8      +1

Flag
Coverage Δ

#unittests
25.49% <34.78%> (+0.2%)
:arrow_up:

Impacted Files
Coverage Δ

src/WebTty/Startup.cs
0% <0%> (ø)

src/WebTty/CommandLineConfigSource.cs
0% <0%> (ø)

src/WebTty/Program.cs
0% <0%> (-78.05%)
:arrow_down:

src/WebTty/CommandLineConfigProvider.cs
0% <0%> (ø)

src/WebTty/RootCommand.cs
95.23% <95.23%> (ø)

src/WebTty/CommandLineOptions.cs
89.58% <0%> (+1.04%)
:arrow_up:

Continue to review full report at Codecov.

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


[pyproject.toml: part 2] Separate setup.cfg parsing and extract common post-processing functions

This is part of #2970, split into several stacked PRs as requested in https://github.com/pypa/setuptools/pull/2970#pullrequestreview-868151658
Follows #3064

We can split the process of interpreting configuration files into 2 steps:

The parsing the file contents from strings to value objects that can be understand by Python (for example a string with a comma separated list of keywords into an actual Python list of strings).
The expansion (or post-processing) of these values according to the semantics setuptools assign to them (for example a configuration field with the file: directive should be expanded from a list of file paths to a single string with the contents of those files concatenated)

The idea of this change is to extract the functions responsible for (2.) into a new module, so they can be reused between different config file formats.
Summary of changes

Rename existing setuptools.config to setuptools.config.setupcfg - 300ebba7fe200ba32c9f35d9f1e71aecde573a84
Extract post-processing functions from setuptools.config.setupcfg into setuptools.config.expand - b0346a8e5164e5fca718bc28ff0a2595618db72b
Allow root_dir to be explicit in setuptools.config.expand functions - 9c596074d2f3f2afe7169a8a2bcfbfbc7b257613
Allow single strings in setuptools.config.expand.read_files - 8b0a15a5462c36e2f535ccd533573c6fd75d4b50
Adequate test_setupcfg to latest changes in setuptools.config.setupcfg - 09499a078d31025e562937f6206453a9d7e63442

Please see the commit message of each individual commit for more information about the changes.
Pull Request Checklist

[x] Changes have tests
[x] News fragment added in changelog.d/.
(See documentation for details)

Is setuptools/tests/config/__init__.py really necessary?

Thank you very much for the kind very @webknjaz and valuable suggestions!


Add new repositories to github slack channel

We need to add them the same way we have for the opencollective-api today(deployment, commits, prs comments, etc):

ledger
opencollective-frontend - after renaming this one, the channel stopped sending notifications about it.

done.


Add support for a /me command

One thing missing atm is the addition of a /me command akin to the one we're all accustomed to on IRC. Without such a command, I find that my level of expressivity within zkc chats is a bit limited 😜

I added the capability last time I rolled the protocol.  Feel free to send me a patch :)


Fix issue with generate password

This PR fixes the issue mentioned in issue #4 .

FWIW, with this new line in place - it seems like you could probably remove the prior line entirely and everything still works:
$refs.{{ $getXRef() }}.value = password;


Move geneva action jmespath code to C#

Since https://github.com/Azure/ARO-RP/pull/859:

Note: by running jmespath on the server with paging we will break things like [8:12] (our paging default is 10 clusters per page). so instead of getting 8,9,10,11 we will get 8,9,18,19,...

We should move the jmespath code to the C# wrapper.  This is actually probably a good thing because it removes functionality from the RP.

https://msazure.visualstudio.com/One/_git/Compute-ARO-GenevaActions/pullrequest/3381555


Specify 'userPassword' encrypting type.

I would like to know how can i declare encrypting type for 'userPassword' attribute while adding new user.
When execute client.add method,sending 'userPassword' to LDAP save it like plain text, but i need, for example, MD5 scheme.

const execSync = require('child_process').execSync
...
var passtype = '{MD5}';  // see man slappasswd for all types
var encryptedPassword = execSync('slappasswd -h "' + passtype + '" -s ' + cleartextPassword).toString();
...

to use slappasswd, need to install slapd.
but if we've already insalled slapd, why not just use open-ldap?

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


OneDeploy improvements

Allow absolute paths. Earlier implementation only allows relative paths
Allow WAR to be deployed to JBoss EAP (although it is not supported on Windows, this will help consistency with KuduLite)

@jvano

looks good to me. :shipit:

@suwatch - this is ready to be merged if it looks ok to you. Thanks!


Update rules_swiftformat to use swift_bazel

Opted to change rules_swiftformat to download prebuilt assets. Will add an example that uses rules_swift_package_manager to build SwiftFormat.


Add .vscode to .gitignore

I was wondering if we could add .vscode, the directory created by Visual Studio Code for editor settings, to the .gitignore file? This would both prevent people from accidentally committing their editor settings, and make working with git a little easier by not having to worry about that file accidentally being tracked by git.
I wouldn't mind creating a PR for this one, I just thought I should follow convention and create an issue on GitHub first. 😁 It's a simple fix, so if it's easier for an admin or moderator to do it, that's also fine! 😄

@robbawebba instead lets open this up to first time contributors.

Hey, I'm working on it!

On Feb 2, 2017 4:35 AM, "Vitor Capretz"<EMAIL_ADDRESS>wrote:
Hey, I'm working on it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/13059#issuecomment-276945704,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYSq2jA5-uPmGwwf8-KfwJVYmx6b2OI2ks5rYc2GgaJpZM4L0rsF
.

Pull request here: https://github.com/freeCodeCamp/freeCodeCamp/pull/13074
Let me know if I need to change something


Storage interface in this project differs from typescript Storage interface

First of all, I wanted to say thanks for creating this project and contributing it--I'm finding it quite useful!
I'm running into trouble when trying to pass Cookie storage to another library (angular-oauth2-oidc) that expects an implementation of the typescript Storage interface. I get the following error:
TS2322: Type 'CookieStorage' is not assignable to type 'Storage'.
        Index signature is missing in type 'CookieStorage'.

I took a look, and it seems that the Storage interface included in the cookie storage project (in storage.ts) differs slightly from the one defined by typescript's lib.dom.d.ts in these lines:
    [key: string]: any;
    [index: number]: string;

I tried adding them to CookieStorage's type definition and it seemed to fix the problem. Reading up on "indexable types" in the TypeScript documentation, it was unclear to me whether adding these two lines to CookieStorage's storage.ts would be enough, or whether additional modifications to the CookieStorage class would be necessary to provide robust support.
Would you be open to a pull request along these lines? (I'm happy to prepare one, but I wanted to check first). Are there any other considerations I should take into account? Or maybe there is another approach I could take to accomplish my goals?
Thanks!
Andrew

Thank you for your comment.
I think it would be better to add it to CookieStorage for compatibility and convinience.
But I think it would not be better to add it to Storage. Storage interface is based on WHATWG Storage. I recommend to use the Web Storage API (setItem, getItem, removeItem, key, length) .
https://html.spec.whatwg.org/multipage/webstorage.html#the-storage-interface

Awesome. I went ahead and submitted PR #6
I was considered whether or not to try to implement some additional code so that you could use these string and number accessors (e.g. myCookieStorage["myKey"] = "myValue") to get and set actual cookies instead of just properties on the cookieStorage object. It looked like this might be possible using a Proxy object (see example here), it seemed that this would introduce a dependency on ES6 that could not be easily worked around with transpiling (see here), so I decided against it. I'm open to suggestions however if you think there's another way to do this, or if you think I made the wrong call.

hmm... I forgot that the indexer ([]) could not be implemented easily...

I'm working on a potential implementation now in my fork. It definitely involves the Proxy object, but after looking at the support matrix for that, I think it might still be useful to most folks, since the support is pretty robust across modern browsers. The design goal would be to help make CookieStorage a drop-in replacement for localStorage and sessionStorage, both of which support indexing (e.g. localStorage["myKey"] = myValue). It's not a small change, but I think it could prove useful to other folks, and it is necessary in my case, since the library to which I want to supply CookieStorage uses these indexing techniques. I'll keep you posted on my progress, and I'd definitely appreciate any feedback.

I think PR #7 looks good from my side. Do you have any feedback, suggestions, or ideas about how to improve it?

Thanks for accepting the PR! Hopefully other folks will find it useful.
Did you have any plans about when to do the next release? I'd like to use the indexing feature in my project, and it would be great to be able to include it via public npm (for CI on a service) instead of needing to manually install from source.

I want to release it as v3 in a few days.
I have made some broken changes. See:
https://github.com/bouzuya/cookie-storage/commit/1579e053fdee1431cbc34b0f861e1ba220e82fd3
I'm sorry I delete ProxyIsSupported.  I think, at runtime, the user should not change the calling method with and without Proxy. It is dangerous. It is better to use it only when the proxy is guaranteed.

Awesome! Removing ProxyIsSupported and replacing it with an undefined check does seem simpler and more elegant--I like it.
Just curious--why did you choose to remove Node 5 support? It's doesn't seem important, but in my tests, it appears to work fine still with the latest code. Was it just to save testing time, since testing node 4 should cover it?

https://github.com/nodejs/LTS

v3 release
https://github.com/bouzuya/cookie-storage/releases/tag/3.0.0


Content Dialog backdrop not displaying over custom TitleBar

Which version of the app?
WinUI 3 Gallery
Description
The backdrop that shows over the window does not extend into the non-system title bar when the ContentDialog is displayed. This is causing an inconsistent design and can lead to confusion and unwanted result, because the problem remains still, even if the sample code is copied by the user.
Screenshots

Windows version
Windows 11 22H2 (22621)
Additional context
No response

External issue: https://github.com/microsoft/microsoft-ui-xaml/issues/6534


BOOL.Value should be typed as int

Perhaps unbelievably, it has come to my attention that some BOOL types carry more than just a binary zero/non-zero state. We should expose this in CsWin32 rather than hide it by only exposing it as bool.

Funny. Well, BOOL is 4 bytes, so bool just doesn't quite cut it, theoretically.


isInteractive from  shows locked button incorrectly

Describe the Bug
When <Controls /> is used with nodesConnectable={false} elementsSelectable={false}, isInteractive incorrectly displays "locked" icon.

This is controlled here https://github.com/wbkd/react-flow/blob/c3681fffcef5502d476d0f27a196b922e87ae666/packages/controls/src/Controls.tsx#L16
I think this logic should use OR operator instead of AND operator.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Start a empty flow with the following code
<ReactFlow nodesConnectable={false} elementsSelectable={false} nodes={[]} edges={[]}>
    <Controls />
</ReactFlow>

Expected behavior
With given options, interactive button should not appear "locked" as nodesDraggable is still true (by default)
Screenshots or Videos
No response
Platform

OS: Linux
Browser: Chromium
Version: 111.0.5563.64 (Official Build) Arch Linux (64-bit)

Additional context
No response

good catch. I think this is broken since v1 👀


Fix pubber gateway proxy runtime issues

Just reverted schema upgrade. Unit tests require manual upgrade of sample site model and trace files which I think it should be also handled in another PR


Styles of close Icon weird

Hey there,
I have a style problem with your very cool Package.

The background of the default clear date icon in the SingleDatePicker is not round, because height and width aren't matching.
This is how I use the SingleDatePicker
  <SingleDatePicker
      date={date}
      onDateChange={date => onDate(date)}
      focused={focused}
      onFocusChange={({ focused }) => onFocus(focused)}
      showClearDate={true}
      reopenPickerOnClearDate={true}
      placeholder="Datum"
      block={true}
    />

I believe the problem is this line in /src/components/SingleDatePickerInput.jsx, but I'm not really sure. Maybe the problem is my implementation
 const closeIcon = customCloseIcon || (
    <CloseButton
      {...css(
        styles.SingleDatePickerInput_clearDate_svg,
        styles.SingleDatePickerInput_clearDate_svg__small, // <-- X
      )}
    />
  );

I am grateful for any tips and suggestions.

Thanks!