GunicornWebWorker: Support for unix domain sockets

At the moment GunicornWebWorker doesn't support unix domain sockets. I think it can be fixed by checking for socket type and not setting host and port for unix domain sockets. Something like:
    @asyncio.coroutine
    def _run(self):
        for sock in self.sockets:
            if isinstance(sock, gunicorn.sock.UnixSocket):
                handler = self.make_handler(self.wsgi, "", 0)
            else:
                handler = self.make_handler(self.wsgi, *sock.cfg_addr)
            srv = yield from self.loop.create_server(handler, sock=sock.sock)
            self.servers[srv] = handler

        ...

From other side I am really not sure, why does ServerHttpProtocol contains host and port. They are not used and probably not needed. So better solution would probably be to remove them completely. But it will break backwards compatibility though.
If you think either of this solutions is fine, let me know and I'll provide a pull request.

As a side question I want to ask why does aiohttp has it's own worker instead of being compatible with the WSGI spec and Gunicorn's gaiohttp worker? I found this comment, but it was never answered...

originally i wrote wsgi compatible gunicorn worker. right now i do not have enough time to unify both workers and submit to gunicorn repo.

Fixed by 1ac5e26


Problems with tag ordering

First of all I want to say it's really good to have this project. It's awesome I really like it.
But unfortunately there are some problems with the tags. I made a system where the first tag is the main category of the post and other tags are used as normal tags. This way we can display related categories under each posts to display content in the same category.
So tag ordering is important in this case, but I realized that tags are reordered on post save, and the user inputted order changes to a different order (ordered by tag creation time I guess). So when I access tags via $post->tags it returns me a reordered list and this way we can not define the main tag as a category.
Is there any way to keep the order entered by the user after saving the post?
It would be really nice to have.
Can I do something to prevent the original ordering entered by the user?

In basic it isn't ordered, see: https://github.com/writingink/wink/blob/master/src/WinkPost.php#L66 I think you need to have a custom option to set the main category.

In basic it isn't ordered, see: https://github.com/writingink/wink/blob/master/src/WinkPost.php#L66 I think you need to have a custom option to set the main category.

Not really, because it only become ordered when you get the tags. Should be returned ordered by relation creation time defined in the relation table. So we could have to ability to keep the ordering.
Why should the tags be displayed in the same order everywhere? Same order just causes duplicate content.

I'd accept a PR that adds categories support on branch 2.x


read the "with datasource" test file

currently we're reading from a data file that doesn't have the DATA_SOURCE field, fix that.

updated


iOS - Expense - Tapping Save button (from Merchant page) for the second time returns to BNP

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.67-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Launch the app.
Go to workspace chat.
Tap + > Submit expense.
Enter amount > Next.
Tap Merchant.
Enter merchant.
Tap Save.
Tap Save button again after the keyboard closes (merchant editor exits after delay).

Expected Result:

Merchant editor will exit instantly after tapping Save button (production behavior).
App will return to confirmation page when tapping Save button for the second time.

Actual Result:

Merchant editor does not exit instantly after tapping Save button. It closes the keyboard first and exits after some delay, which allows Save button to be tapped for the second time.
App returns to BNP when tapping Save button for the second time.

Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[x] iOS: Standalone
[x] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/835b8708-0db9-4b13-8038-cd92c2249a99

View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
iOS - Expense - Tapping Save button (from Merchant page) for the second time returns to BNP
What is the root cause of that problem?
When clicking save button twice, function call for updateMerchant is triggered twice.
And hence updateMerchant function function calls navigateBack() function twice here.
https://github.com/Expensify/App/blob/967cc5c21600d4706f40364cb6c7022ded0d6d8a/src/pages/iou/request/step/IOURequestStepMerchant.tsx#L121
https://github.com/Expensify/App/blob/967cc5c21600d4706f40364cb6c7022ded0d6d8a/src/pages/iou/request/step/IOURequestStepMerchant.tsx#L86-L108
What changes do you think we should make in order to solve the problem?
To avoid this we should make use of singleExecution and isExecuting  from hook useSingleExecution to ensure updateMerchant function is executed only once. As we do here on WorkspaceInitialPage.
https://github.com/Expensify/App/blob/967cc5c21600d4706f40364cb6c7022ded0d6d8a/src/pages/workspace/WorkspaceInitialPage.tsx#L98
https://github.com/Expensify/App/blob/967cc5c21600d4706f40364cb6c7022ded0d6d8a/src/pages/workspace/WorkspaceInitialPage.tsx#L306
And disable the save button when isExecuting is true.
https://github.com/Expensify/App/blob/967cc5c21600d4706f40364cb6c7022ded0d6d8a/src/pages/workspace/WorkspaceInitialPage.tsx#L426-L439
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

@ChavdaSachin can you please point what PR caused this regression from the checklist?

@kirillzyusko @c3024 could you please investigate this flow for a fix? this is in standalone app too so you should be able to test

Yes this is coming from #52392.
Specifically from this line
https://github.com/margelo/expensify-app-fork/blob/84175de2f85e89cee967b3f9c73153e115620a53/src/components/Form/FormProvider.tsx#L210

Updated Proposal
Added root cause and improvement around it.

Yes, let's give some time to @kirillzyusko first since it is a regression.

I agree with proposal from @ChavdaSachin
Two things that I would do differently:

for isSubmitting I would use useRef (to avoid unnecessary re-renders);
we need to set the variable back to false in KeyboardUtils.dismiss().then(() => { /*.set ref/state to false here */ onSubmit(trimmedStringValues); });

@ChavdaSachin will you fix this problem? Or should I fix it because it was my changes that introduced a regression?

@ChavdaSachin will you fix this problem?
I would be happy to fix this

@ChavdaSachin then I'm happy to approve your proposal. Is there anything else required from my side?

As of now it's pretty straightforward, but I will let you know if I face any further complications.

@ChavdaSachin What is your ETA for raising the PR?

Assigned myself as I have co-reviewed the original PR

we need to set the variable back to false in KeyboardUtils.dismiss().then(() => { /*.set ref/state to false here */ onSubmit(trimmedStringValues); });

I tried to implement this suggestion but this is causing same issue of double execution somehow.
So, I am currently investigating the issue further.
Will provide next update within an hour.

@ChavdaSachin I am going to assign @kirillzyusko as this is one of the more challenging deploy blockers. Given the urgency, we will proceed with his help on this issue

Feel free to provide any more context and if your solutions will be used, we are happy to provide some compensation for your help

I have got it working

just testing on all the platforms
And raising PR in few minutes

@ChavdaSachin Nice, please feel free to make a draft

@IuliiaHerets I also discovered that a problem with double navigations happens on:

Settings -> Profile -> Date of birth
Settings -> Profile -> Phone number (you can close keyboard and then press submit)
Settings -> Profile -> Address

CPing the fix, thanks @kirillzyusko

BugZero Checklist:

[x] [Contributor] Classify the bug:

Bug classification

Source of bug:

[x] 1a. Result of the original design (eg. a case wasn't considered)
[ ] 1b. Mistake during implementation
[ ] 1c. Backend bug
[ ] 1z. Other:

Where bug was reported:

[ ] 2a. Reported on production
[x] 2b. Reported on staging (deploy blocker)
[ ] 2c. Reported on both staging and production
[ ] 2d. Reported on a PR
[ ] 2z. Other:

Who reported the bug:

[ ] 3a. Expensify user
[ ] 3b. Expensify employee
[ ] 3c. Contributor
[x] 3d. QA
[ ] 3z. Other:

[x] [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NA. This was identified in regression testing and the blocker was fixed by offending PR author.

[x] [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:

[x] [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal Template

[ ] [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:

Regression Test Proposal
Precondition:

Test:

Launch the app.
Go to workspace chat.
Tap + > Submit expense.
Enter amount > Next.
Tap Merchant.
Enter merchant.
Tap Save.
Tap Save button again after the keyboard closes.
You should be redirected to the previous screen.

Do we agree 👍 or 👎

I dont think we need to add a regression test specifically for this, the QA will most likely catch some bug in normal testing

Given this came from a PR @c3024 reviewed and the author fixed it, I think we can just close it, thanks!


[typescript] Style typing improvements

Fixes definition of Omit so that it distributes across union types. This allows us to give better return types for withStyles, withTheme and withWidth.
Use a custom AnyComponent definition instead of React.ComponentType, which allows us to get rid of the ugly type annotation when using union-typed props. Remove corresponding caveat from the docs.
Better typing of withStyles so that if the type checker can statically determine that you passed the withTheme: true option to withStyles, then theme will not be undefined in the inner component's props.

Resolves #12070, supersedes #12106.
Closes #12106

@pelotom Commenting here because it was reasonably recently and might be fresh in your mind.
Whatever you've done to withStyles here prevents type inference for styles which use the theme, e.g.:
const styleDecorator = withStyles(theme => ({
  active: {
    backgroundColor: theme.palette.grey[200],
  },
}));

Here the type params of withStyles are inferred as <never, {}> (don't know why) which means that the classes prop of a wrapped component has type Record<never, string> which is obviously no use.
It isn't clear to me why you've chosen to make the theme parameter become optional rather than gone either.
Surely this problem would have been better solved by multiple overloads of the function typing rather than introducing another generic argument? Or even just living with existing return typing since you've barely changed it anyway.

Check the latest guide for explanation: https://material-ui.com/guides/typescript/
You will need to add the createStyles function.

@rosskevin I don't think that's the issue here.
Typescript has some issue with function parameter types inside generics (don't quote me on that; it's the same issue with generic props and event handlers).
Basically you need to explicitly annotate the function parameter with Theme. But I think it might be worth investigating using overload instead of a generic argument. The reason for the change is somewhat explained in https://github.com/mui-org/material-ui/pull/12673#issuecomment-418988649

Did some quick testing with overloads on not only does this add quite a bit of duplicate code it also breaks the patterns we document and test against.
@gordonmleigh I would recommend you explicitly type your function parameters. This might be also required in the future when we make our Props generic which again will cause typescript to fail because it can't infer function paremters in generic types.

I would love to someday have a withStyles which is typed perfectly and does everything we want it to do without needing superfluous type annotations... unfortunately every time we push something onto one end of the shelf something seems to fall off the other end, and we've gone through many iterations of this. PRs always welcome!

Doubtful compromise between ease of code writing and type safety, we haven't experienced any problems with the previous solution. This solution prevents our codebase (and I think others) from upgrading to next version of the library without large rewritings.

@DenisNeustroev What pattern did you previously use?

@DenisNeustroev  For me it was opt-in to omit the *ClassKey, not a forced rewrite.  I indeed still have some code doing it the older way that I have yet to touch.
Note that there was a point release with a type breaking change in the withStyles parameterized type options which was quickly solved and another point release.  But if you are using the current release I see no reason why you would think a style rewrite is in order.

We need the component to enable defaultProps. Otherwise this information is lost.
I don't understand what you are trying to do with your withStyles implementation.
const styles = withStyles({ root: { background: 'white' } })

interface Props {
    text: string
}

export const WhiteText = styles<Props>(({ classes, text }) => (
    {text}
))

I understand but again we had to change this for defaultProps. It doesn't do anything different than
const styles = { root: { background: 'white' } }

interface Props extends WithStyles<typeof styles> {
    text: string
}

export const WhiteText = withStyles(styles)(({ classes, text }: Props) => (
    {text}
))

It's the same pattern we use in our codebase and throughout the docs.
I think that you don't have to expect any major shifts anymore. When you add typings to an existing codebase you have to expect changes especially since the overall typescript support for react was very immature. If you simply can't migrate I recommend you pull out the typings of withStyles from 3.0 and configure your tsconfig to use those e.g.
"paths": {
  "@material-ui/core/styles/withStyles": ["path/to/3.0/styles/withStyles"]
}

but again you're disregarding a lot of edge cases in your implementation.

@eps1lon sure we'll migrate, I just gave you an example of how we had used it before since you asked & shared my opinion regarding new typings

@nmchaves for now we use the following hack:
import {  withStyles as mWithStyles } from '@material-ui/core/styles'

export function withStyles<ClassKey extends string>(
  style: StyleRules<ClassKey> | StyleRulesCallback<ClassKey>,
  options?: { name: string },
) {
  return function styles<Props extends {}>(
    component: React.ComponentType<Props & WithStyles<typeof style>>,
  ) {
    // @ts-ignore
    const componentWithStyles = mWithStyles(style, options)(component)
    return componentWithStyles as React.ComponentType<
      Props & StyledComponentProps<ClassKey>
    >
  }
}

It kind of should work without ts-ignore, but ts throws strange error, maybe it will work fine with future versions of withStyles typings

@vmajsuk Do you have strictNullChecks enabled in your tsconfig?

@eps1lon Yep


node-sonos-http-api got an update and now Module doesnt work

node-sonos-http-api got an update to accomodate node v6.x and now the module doesnt display any track information.
The module displays speaker/room name but no track or artist name or album art.
Any ideas why this might be?
Marc

same problemsame node version any solutions?

Hey guys, need to do some research here.. no idea. Have the same problem currently..

I found the bug problem is solved when replace line number 35 in sonos.js to
var state = item.coordinator.state.playbackState; //

So my sonos.js looks like this now
	render: function(data){
		var text = '';
		$.each(data, function (i, item) {
			var room = item.coordinator.roomName;
			var state = item.coordinator.state.playbackState; //
			var artist = item.coordinator.state.currentTrack.artist;
			var track = item.coordinator.state.currentTrack.title;
			var cover = item.coordinator.state.currentTrack.absoluteAlbumArtURI;
			var streamInfo = item.coordinator.state.currentTrack.streamInfo;
			if(item.members.length > 1){
				room = '';
				$.each(item.members, function (j, member) {

this isnt working for me.
instead my mirror now shows this image :  click here for image

Hello,
i have the same issue. The module only shows the room names. If i change the line 35 in the sonos.js i see no picture but i get the album and artist info.

I hate to pile on, but I have nothing more to add than "me too!".  If I modify line 35 as described above, I get only a list of zone names.  Interestingly, if I leave lined 35 unmodified I get the same output: simply a list of zone names.

@dinkybluebug @pixelecho @Sillec123 @skpy sorry for the delay, it should work now.


Mixin doesn't pull in &:extend() in 1.5.0-beta3

Tried to upgrade to 1.5.0-beta3 because I really need some Less 1.5.0 features.  Stumbled across this bug in a real world case using bootstrap.  If you use a class containing an extend as a mixin, the extend doesn't apply to the mixed in.  Steps to reproduce:
Use the less code:
.test
{
  color: orange;
}

.replacement
{
	&:extend(.test);
}

.foo
{
	.replacement();
}

In dotless 1.5.0-beta3, that compiles to:
.test,
.replacement {
  color: orange;
}

Using http://less2css.org, less v1.5.0 it compiles to:
.test,
.replacement,
.foo {
  color: orange;
}

Notice how with the official less compiler, .test is extended with .foo.
I stumbled across this using multiple bootstrap 3.3.2 classes as mixins because they will frequently use &:extend(.clearfix all);

Thanks for finding this, I'll take a look at it in the next couple of days.
It's worth noting that since 1.4, dotless' version number hasn't been equal to the less language version it implements -- although it's likely that 1.5 does contain most if not all the language-level (syntactic) features of the latest less language version. If you find a feature that is missing, let me know.

Thanks for the heads up about the dotless version numbers no longer matching the less language feature version.  You should update the wiki to reflect that.  It made me believe dotless was farther behind that it sounds like it is. I table of which versions they correspond to would be good. We were running dotless 1.4.4 and needed the (reference) import option.

I agree that a table like that would be good, but putting one together would require quite a bit of effort -- and since I'm currently the only one actively working on dotless, I'd rather spend my energy on getting to 100% feature parity with the official less.js implementation and then document what we've got.
By the way, did this usage of :extend work in 1.4.4?

Tested for myself with 1.4.2 and yes, it did work before, so this is a regression.

Yet another consequence of the fairly fragile way :extend was originally implemented -- I changed the evaluation order from last-to-first to first-to-last to make certain namespace resolution scenarios possible, and it broke this thing. Try 1.5.0-beta4, it's fixed there. And thanks again for finding the issue.

Thanks for the rapid response.  1.5.0-beta4 fixed this issue.  Also, wanted to let you know that upgrading to 1.5.0-beta4 from 1.4.4 seems to not have broken anything else on our reasonably sized project using bootstrap 3.3.2.  The only difference is due to the changes discussed in #144 where the new behavior is correct and the old was wrong.

That's great news. I did make an effort to test that the output of compiling Bootstrap would not be adversely affected by the changes, but it didn't occur to me to try all the ways to mix in Bootstrap.
The changes I made towards more comprehensive mixin/extend support actually resulted in us supporting scenarios that the official implementation does not (yet) do: we now re-parse selectors after evaluating them, so you can do things like extend Bootstrap's columns or call them as mixins.

I think we can bump the dotless version to match the less.js version once
we hit feature parity.
The current version was mostly a result of me merging change-requests and
one or two breaking changes that needed to be reflected in the version
number.
greetings Daniel
Lauri Kotilainen<EMAIL_ADDRESS>schrieb am Fr., 15. Mai 2015 um
18:17 Uhr:

That's great news. I did make an effort to test that the output of
compiling Bootstrap would not be adversely affected by the changes, but it
didn't occur to me to try all the ways to mix in Bootstrap.
The changes I made towards more comprehensive mixin/extend support
actually resulted in us supporting scenarios that the official
implementation does not (yet) do: we now re-parse selectors after
evaluating them, so you can do things like extend Bootstrap's columns or
call them as mixins.
—
Reply to this email directly or view it on GitHub
https://github.com/dotless/dotless/issues/443#issuecomment-102451364.


raft:not current leader

Describe the bug
Raft has no leader in the cluster forever.
it seems a raft bug because of snapshotting.
Thinking of the scenario below：
The cluster has 3 masters. Master-0 is the leader, the others are followers.
Each master has a snapshot.

When the followers restart, they will fall into snapshot loop to reply snapshot, other than a leader or canidata or follower.
Snapshot loop does not have a timeout chan to reselect except receiving a appendRpc with new term.
Restart the leader. Because of the log have been clear, raft forbid the leader to promote.
Thus the cluster has no leader forever because on one to be a candicate.

Screenshots

Is it resonable to set state to follower after snapshot resp sucess in snapshot_loop?
@chrislusf

Sounds reasonable. Would be good to see how other raft implementations are handling this.


Generate js sourcemaps

Is there any reason why the js files don't have sourcemaps like the css files do? Both the concat and uglify tasks support this when you set sourceMap to true.

Good question. While I am not aware of a reason, when I get home / if the core team is interested I should be able to put together a PR to fix / add that.

The minified css files don't have sourcemaps either. This can be enabled with cssmin the same way.

Punting on this since I believe we don't really do anything crazy to our JS. No matter what format you're running—individual, compiled, or minified+compiled—you'll get JS that runs in browser. Thanks though!


MetaTag

I am trying pass meta data for my live streaming, the meta data will contain batsman and bowlers details. Later after the live streaming is completed, I want to edit the MP4 format video based on meta data.
Is there any way to do that

You have 2 ways.

Change packets header if you want change metadata in real time.
Add info in connection packets:
RTMP:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/rtmp/src/main/java/com/github/faucamp/simplertmp/io/RtmpConnection.java#L348
RTSP:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/rtsp/src/main/java/com/pedro/rtsp/rtsp/CommandsManager.java

After that, you need modify server to extract it.


Recreate Netdata icon

@alexcontini Could you please recreate a version of https://static.distribooted.com/logos/netdata.png. It is based on https://www.iconsdb.com/soylent-red-icons/seo-performance-icon.html (which unfortunately doesn't seem to have high-res versions) and the name added.
Cc https://github.com/firehol/netdata/issues/3801#issuecomment-396004881

Thank you!

Done, thanks.


Add improved version of Hungarian algorithm.

Follow-up to https://github.com/google-deepmind/optax/pull/1083#issuecomment-2487415673.

@vroulet Seems to me it’s cleaner to keep each implementation in a separate file since

It keeps their respective helper functions separate and prevents confusion.
More implementations might be added in the future, and this results in less crowded files.

WDYT?

It keeps the implementations less entangled and keeps their respective helper functions separate, avoiding potential confusion.

In any case we should add in the docstring why they differ.

It keeps the modules shorter/less crowded, especially if more implementations are added in the future.

I would actually agree with you, but typically the alias file in optax has an ever increasing list of optimizers. So let's keep the same logic here.

@vroulet Done.


feat(engine) Rewrite control flow inside loops.

Closes #393.
Loops are already translated as folds. This PR wraps their accumulators to add control flow information (in case of break return or continue). Some specific fold operators are also added to handle these wrapped accumulators.
This PR puts LocalMutation before RewriteControlFlow. In RewriteControlFlow, we now deal with the body of loops (to push control flow in return position, like this phase already does for returns outside loops). We also wrap loops that have a return inside a pattern matching over the result (to propagate a returned value), and apply the phase to inline what comes after in the branches of the pattern matching. Phase DropNeedlessReturns is now DropREturnBreakContinue. Inside loops it replaces return , break and continue by their encoding in the ControlFlow enum. It treats a value in return position of a loop body like a continue. Phase FunctionalizeLoops selects the correct fold operator (each fold should now come in 3 versions: the normal one, the one supporting break and continue, and the one supporting all type of control flow).

Code generation should be almost stable. The remaining part is to write the specific folds as part of the fstar Rust_primitives

@W95Psp still testing but you can start to review.

@W95Psp I think I fixed everything according to your feedback!


Vimeo doesn't autoplay in Safari Desktop

Thank you for you hard work on this tool. It's been indispensable to my project, however, I'm running into an autoplay issue for Vimeo embeds in Safari
Expected behaviour
When you set autoplay: true in the options argument for a Vimeo embed the video starts on page load.
Actual behaviour
In Safari: Doesn't autoplay
In Firefox: Autoplays but with circle play button in front
In Chrome: Works as expected
It does, however, still play when you fire the .play() method
Environment
Tested with Plyr 3.0.7

Browser: Safari
Version: 11.0.3
Operating System: macOS High Sierra
Version: 10.13.3

Steps to reproduce
-Visit this Codepen in Safari: https://codepen.io/ThatGuySam/full/eMyzgK

This is a browser feature. Nothing Plyr can do. Disabling or muting audio make it work. For more details see https://github.com/sampotts/plyr/issues/716#issuecomment-345351316

Aw shoot, muted: true and volume: 0 don't seem to work.
https://jsfiddle.net/thatguysam/zbt4b4f6/5/
(BTW I forgot to say that this is specifically Safari Desktop issue)
I can, however, do a fake autoplay by just adding an event listener.
player.on('ready', function () {   player.play(); });

I'm surprised your pseudo-autoplay works. This makes it not quite the same issue since it wasn't initiated by a gesture, and in turn perhaps there is something either Plyr or Vimeo could do to avoid this.

BTW: https://economictimes.indiatimes.com/magazines/panache/google-chrome-officially-announces-to-permanently-block-audio-enabled-autoplay-videos/articleshow/63467106.cms

It looks like there are some exceptions to unmuted autoplay in the new policy based on what they call Media Engagement Index with includes several factors like, times unmuted, video size, and video length.
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#mei

Yeah. I'm not really a fan of MEI. It's a "but it works for me" blindspot that devs will not get, but end users wil. Also, it isn't really the issue you are having of course, but I thought you should know.

Sorry yeah there are issues with the muted and volume options. Looking into it.

Can you try again? I think this is fixed in v3.0.11

Thank You @sampotts!!
It's now working as expected in Safari Desktop and even Firefox is fixed.
https://jsfiddle.net/thatguysam/zbt4b4f6/8/

I add the
player.on('ready', function () { player.play(); });
with a timeout and then it works.
If anyone have the same problem it fix mine.


Add a push method to scalar list update input in addition to set

Problem

Right now we only provide a set method for scalar lists
For example, lets say we have this model:
model User {
  id         String   @id @default(cuid())
  permission String[]
}

We generate the following update type:
export type UserUpdatePermissionsInput = {
  set?: Enumerable<string> | null
}

This is not ideal when you want to push items to the array. For that right now you will need to read the whole record and add the previous items to the old array and then set it which costs a db request and it is not the best DX.
Suggested solution
Add a push key to the update input which will add the new item instead of resetting the set
export type UserUpdatePermissionsInput = {
  set?: Enumerable<string> | null
  push?: Enumerable<string> | null
}

Under the hood this can be backed by the || postgres operator or the array_append method
Alternatives
I am not sure how we can provide a better way of doing this right now.

Additional context
Suggested by @kitze in his livestream

This would come in very handy. This would simplify things quite a bit.

What do folks in this thread think about adding a "pushUnique"
which essentially would skip duplicates

How can this functionality be achieved in a MongoDB database?

How can this functionality be achieved in a MongoDB database?

What do folks in this thread think about adding a "pushUnique"
which essentially would skip duplicates
Update: #19370

In MongoDB it's called $addToSet


Create pangram_check.cpp

Added code to check whether the given string is pangram or not in C++ language

@abranhe Please see this PR.


Debug Console scrolls to top after every command I run in python

Issue Type: Bug
This is in python.   It's super annoying.
VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:59:35.033Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.86GB (21.52GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

githistory
don
0.4.6

RunOnSave
eme
0.2.0

vscode-test-explorer
hbe
2.13.0

nbpreviewer
jit
1.2.2

vscode-python-test-adapter
lit
0.3.8

linecounter
lyz
0.2.2

rainbow-csv
mec
1.1.1

anaconda-extension-pack
ms-
1.0.1

python
ms-
2019.6.24221

team
ms-
1.149.2

vscode-yaml
red
0.4.1

vscode-coverage-gutters
rya
2.4.0

indenticator
Sir
0.6.0

vscode-counter
uct
1.2.0

This should be fixed with latest vscode insiders
https://code.visualstudio.com/insiders/
Let me know if you an still reproduce.
And if you can, please write down exact reproducable steps.
Thanks!


Allow appending extra values to embedding vector

This feature lets you inject extra per-sample or per-atom values into the model.  They are appended to the embedding vector for each atom, then a linear layer mixes them in and reduces the vector back down to its original size.  In the config file, you specify one or more extra fields from the dataset that should be added to the embedding:
extra_embedding: partial_charges

or
extra_embedding:
  - partial_charges
  - total_charge

Each one can have a single value per sample (for a global scalar like total charge) or a value for each atom.
When calling the model for inference, you specify them with extra_args:
model(z, pos, extra_args={'partial_charges':partial_charges)

See https://github.com/torchmd/torchmd-net/issues/26#issuecomment-1939258460 for discussion.

The design and implementation are great and retrocompatible.
@guillemsimeon, could you comment on the architecture changes?
Peter made it so that the extra arguments are mixed with the embedding using a Linear layer:
https://github.com/torchmd/torchmd-net/blob/13926ad59446ab1c8bdf0354845028d3d30cff8f/torchmdnet/models/tensornet.py#L308-L311
https://github.com/torchmd/torchmd-net/blob/13926ad59446ab1c8bdf0354845028d3d30cff8f/torchmdnet/models/tensornet.py#L345-L347

We already discussed the changes in the issue.
On Thu, 22 Feb 2024 at 09:30, Raul @.***> wrote:

The design and implementation are great and retrocompatible.
@guillemsimeon https://github.com/guillemsimeon, could you comment on
the architecture changes?
Peter made it so that the extra arguments are mixed with the embedding
using a Linear layer:
https://github.com/torchmd/torchmd-net/blob/13926ad59446ab1c8bdf0354845028d3d30cff8f/torchmdnet/models/tensornet.py#L308-L311
https://github.com/torchmd/torchmd-net/blob/13926ad59446ab1c8bdf0354845028d3d30cff8f/torchmdnet/models/tensornet.py#L345-L347
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd-net/pull/289#issuecomment-1958942241,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANJMOA7P6RGGUMZ7FUX7ZADYU363DAVCNFSM6AAAAABDTZIFNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYHE2DEMRUGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is finished and ready to merge as far as I'm concerned.  I'm getting good results with it.  Can someone review it?

we cannot merge this for now,  use it in a branch for now.
Once we finish what we are doing we will come back to it to see how it
performs and if it makes sense to merge it into main.
On Tue, Feb 27, 2024 at 1:16 AM Peter Eastman @.***>
wrote:

This is finished and ready to merge as far as I'm concerned. I'm getting
good results with it. Can someone review it?
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd-net/pull/289#issuecomment-1965563924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOVDIKFDBRXUDNTTFZTYVUQXHAVCNFSM6AAAAABDTZIFNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGU3DGOJSGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Why can't we merge it?  What are you doing that conflicts with it?
If this isn't going to be run as an open source project, I can't use it.  I need a stable, reliable base to build my research on.  That means development is done in public, and I can add features that are essential to my research.  If you're going to reject changes without explanation because they conflict with things you're doing in secret and can't tell me about, then I need to end my involvement in this project.

I don't think that what you are saying is right at many levels. Simply, as
explained before, the change that you propose has not yet been tested by
us. It is a model change, not a cosmetic one. As I wrote before, it might
be superseded by another change that we are working on and that we have
tested already. Use it in your branch for a bit until we can assess it. If
it is better, we will of course merge it, but we also test many things and
not all go to main. Happy to clarify further tomorrow.
On Tue, Feb 27, 2024 at 6:52 PM Peter Eastman @.***>
wrote:

Why can't we merge it? What are you doing that conflicts with it?
If this isn't going to be run as an open source project, I can't use it. I
need a stable, reliable base to build my research on. That means
development is done in public, and I can add features that are essential to
my research. If you're going to reject changes without explanation because
they conflict with things you're doing in secret and can't tell me about,
then I need to end my involvement in this project.
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd-net/pull/289#issuecomment-1967294988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUORGPZSDNZGSQWBTTU3YVYMNXAVCNFSM6AAAAABDTZIFNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXGI4TIOJYHA
.
You are receiving this because you commented.Message ID:
@.***>

As I said before, it is not a change to the existing model.  It's a completely new feature.  If you don't use the new feature, nothing in your model changes the slightest bit.  It breaks nothing.  It conflicts with nothing.
I've already done extensive testing of it and found that it substantially improves accuracy.  I can post numbers if you want to see them. What additional validation do you need?
And we really need to do development in public.  Being told you are working on "something" that "might" supersede this in the future, but it's secret and you can't tell me about it, is very frustrating and not useful.  In an open source project, decisions get made in public based on public information.  You can have your own internal branch where you work on things you don't want to share.  But you can't block development of the public version for private reasons that you won't tell anyone.
If I'm going to base my research on this project, it needs to be a stable base to build on.  That means having a clear process for reviewing and merging PRs.  I have a whole series of features I want to add.  I can't create a branch with a new feature, then another branch with another feature based on top of that one, then a third branch with a third feature based on the second one, and so on for months, with my version of the code steadily diverging from the main repo and never knowing whether the very first PR will get rejected and break everything I did after.


Refactor code to reduce duplication

You have almost the identical code written twice: https://github.com/MizuhoOkimoto/pajama-ssg/blob/main/pajama-ssg/pajama-ssg.js#L64-L96.  You should create a function that takes the stylesheet as an arg, and constructs the string only once instead of having to define it twice.

It then happens again at https://github.com/MizuhoOkimoto/pajama-ssg/blob/main/pajama-ssg/pajama-ssg.js#L121-L153.


Problem when trying to use mass storace

Describe the bug
[A clear and concise description of what the bug is]
How To Reproduce
Steps to reproduce the behavior:

Boot the boot.img (spes)
Use the arrow keys to go to dec options
press the power button

Expected behavior
Should boot the developeroptions.efi file
Details (please complete the following information):**

Device: Redmi note 11 (spes)
OS: Windows 11
UEFI Version: idk

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
[Add any other context about the problem here]

Did you tried to boot other uefi app?

I meant MSM app

I found the UEFI version: 2.8
built from repo today

I meant MSM app

The windows 11 option?

Spes has host mode. MSM wont work without Device mode. Try to use unpatched UsbConfigDxe

Spes has host mode. MSM wont work without Device mode. Try to use unpatched UsbConfigDxe

send download

No change, stuck on a black screen, also the partition is the esp one (created using the guide) where i have to copy the files right?
Also is it right i have to use the power button as my enter key?

try to boot other msm app

Thank you, let me try

wen make uefi mass storage binded at vol down?

When I made UI, But thats not Related to this Issue

IT WORKED, THANK YOU

If using spes, just use the Mass storage from this guide: https://github.com/Project-Silicium/WoA-Guides/blob/main/Mu-Qcom/Devices/Xiaomi-Redmi-10C/Mass-Storage.md

Windows doesn't recognize the drives but linux does

You have to Mod the Registry in Windows so USB will Init in Host Mode
https://github.com/Project-Silicium/WoA-Guides/blob/main/Mu-Qcom/OS/Windows/Win.md#fixing-work-usb-step-6


Dependencies are not in organization dependency overview

Hey, when I use this action my dependencies do not show up in my organization overview (i.e.
https://github.com/orgs/{org_name}/insights/dependencies) but they do show up in my repos dependency graph page (i.e. https://github.com/{org_name}/{repo_name}/network/dependencies). Repositories that generate an dependency graph automatically seem to populate to the organization overview correctly (e.g. maven, npm).
Is this expected behavior?
Here is my workflow:
name: Update Dependency Graph

on:
  push:
    branches:
      - master

jobs:
  dependency-graph:
    name: Update Dependency Graph
    permissions:
      contents: write # this permission is needed to submit the dependency graph
    steps:
      - uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 # v4.1.0
      - uses: coursier/cache-action@d1039466d0812d6370649b9afb02bbf5f646bacf # v6.4.3
      - uses: coursier/setup-action@48280172a2c999022e42527711d6b28e4945e6f0 # v1.3.4
        with:
          apps: sbt
      - uses: scalacenter/sbt-dependency-submission@1eef19c779b0b4722ab3d72b4e52279070ac7945 # v2.2.0

Any help with this would be greatly appreciated.

I asked GitHub Support about this, and just got this reply (highlight is mine):

Thanks for your patience. I can reproduce your issue for Scala and Gradle.
I have also the confirmation that it is an expected behaviour as we don't include dependency submission results in org insights yet. I can see the documentation is not clear, we will look into to improve it.
As a workaround, you can considering using Maven build for your Scala project, as pom.xml is automatically detected.

Thanks @MPV  for figuring this out.

I also asked:

What’s the outlook for supporting it in the future? Should we invest in the Dependency Graph on GitHub and hope/aim for it to be supported for Dependency Submission soon too?

And just got the reply:

Hi,
I have checked with our engineering team, and they have inform that the feature will be implemented but there is no ETA currently. In addition, I have raised an internal issue for this, so we recommend that you keep an eye on the GitHub Blog and the Changelog for related updates.
I will therefore mark this ticket as Solved.
Kind Regards

It seems the Github team have fixed this issue on their side.

It seems the Github team has fixed this issue on their side.

Oh, I'm not seeing this on my side.
How did you experience this being resolved?


Actually preserve pinned tabs + promisify

One more extension. Sorry! But there was a real bug. It was totally necessary, I swear!

Awesome! I never mind improvements to projects :)


LHError: PROTOCOL_TIMEOUT Internal Error

The following error happened in a build:
UnhandledRejection: a promise was rejected but not handled: LHError: PROTOCOL_TIMEOUT
Plugin "netlify-plugin-is-website-vulnerable" internal error
> 12:13:12 PM: Build ready to start
> 12:13:13 PM: build-image version: 3571f0130496395a23bffe9820bc78b4f73a6234
> 12:13:13 PM: build-image tag: v3.7.0
> 12:13:13 PM: buildbot version: c8ebd612d11de8df807ee80082ae1ebcb899414f
> 12:13:14 PM: Fetching cached dependencies
> 12:13:14 PM: Starting to download cache of 614.9MB
> 12:13:17 PM: Finished downloading cache in 3.75549561s
> 12:13:17 PM: Starting to extract cache
> 12:13:40 PM: Finished extracting cache in 22.889814292s
> 12:13:41 PM: Finished fetching cache in 27.019929066s
> 12:13:41 PM: Starting to prepare the repo for build
> 12:13:41 PM: Preparing Git Reference pull/121/head
> 12:13:44 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: '_site' versus '_site/' in the Netlify UI
> 12:13:45 PM: Starting build script
> 12:13:45 PM: Installing dependencies
> 12:13:45 PM: Python version set to 2.7
> 12:13:46 PM: Started restoring cached node version
> 12:13:53 PM: Finished restoring cached node version
> 12:13:54 PM: v10.24.0 is already installed.
> 12:13:55 PM: Now using node v10.24.0 (npm v6.14.11)
> 12:13:55 PM: Started restoring cached build plugins
> 12:13:55 PM: Finished restoring cached build plugins
> 12:13:55 PM: Attempting ruby version 2.6.2, read from environment
> 12:13:57 PM: Using ruby version 2.6.2
> 12:13:57 PM: Using bundler version 2.2.3 from Gemfile.lock
> 12:13:59 PM: Successfully installed bundler-2.2.3
> 12:13:59 PM: 1 gem installed
> 12:13:59 PM: Using PHP version 5.6
> 12:13:59 PM: Started restoring cached ruby gems
> 12:13:59 PM: Finished restoring cached ruby gems
> 12:13:59 PM: Installing pip dependencies
> 12:13:59 PM: Started restoring cached pip cache
> 12:13:59 PM: Finished restoring cached pip cache
> 12:13:59 PM: DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
> 12:14:00 PM: Collecting ics>=0.7
> 12:14:00 PM:   Using cached ics-0.7-py2.py3-none-any.whl (42 kB)
> 12:14:00 PM: Collecting requests>=2.25.1
> 12:14:00 PM:   Using cached requests-2.25.1-py2.py3-none-any.whl (61 kB)
> 12:14:00 PM: Collecting PyYAML>=5.4.1
> 12:14:00 PM:   Using cached PyYAML-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl (574 kB)
> 12:14:00 PM: Collecting tatsu>4.2
> 12:14:00 PM:   Using cached TatSu-4.4.0-py2.py3-none-any.whl (85 kB)
> 12:14:00 PM: Collecting arrow<0.15,>=0.11
> 12:14:00 PM:   Using cached arrow-0.14.7-py2.py3-none-any.whl (39 kB)
> 12:14:00 PM: Requirement already satisfied: six>1.5 in /opt/buildhome/python2.7/lib/python2.7/site-packages (from ics>=0.7->-r requirements.txt (line 1)) (1.15.0)
> 12:14:01 PM: Collecting python-dateutil
> 12:14:01 PM:   Using cached python_dateutil-2.8.1-py2.py3-none-any.whl (227 kB)
> 12:14:01 PM: Collecting chardet<5,>=3.0.2
> 12:14:01 PM:   Using cached chardet-4.0.0-py2.py3-none-any.whl (178 kB)
> 12:14:01 PM: Collecting urllib3<1.27,>=1.21.1
> 12:14:01 PM:   Using cached urllib3-1.26.4-py2.py3-none-any.whl (153 kB)
> 12:14:01 PM: Collecting idna<3,>=2.5
> 12:14:01 PM:   Using cached idna-2.10-py2.py3-none-any.whl (58 kB)
> 12:14:01 PM: Requirement already satisfied: certifi>=2017.4.17 in /opt/buildhome/python2.7/lib/python2.7/site-packages (from requests>=2.25.1->-r requirements.txt (line 2)) (2020.12.5)
> 12:14:01 PM: Collecting backports.functools-lru-cache>=1.2.1; python_version == "2.7"
> 12:14:01 PM:   Using cached backports.functools_lru_cache-1.6.1-py2.py3-none-any.whl (5.7 kB)
> 12:14:01 PM: Installing collected packages: tatsu, backports.functools-lru-cache, python-dateutil, arrow, ics, chardet, urllib3, idna, requests, PyYAML
> 12:14:03 PM: Successfully installed PyYAML-5.4.1 arrow-0.14.7 backports.functools-lru-cache-1.6.1 chardet-4.0.0 ics-0.7 idna-2.10 python-dateutil-2.8.1 requests-2.25.1 tatsu-4.4.0 urllib3-1.26.4
> 12:14:03 PM: Pip dependencies installed
> 12:14:03 PM: Started restoring cached go cache
> 12:14:05 PM: Finished restoring cached go cache
> 12:14:05 PM: Installing Go version 1.12
> 12:14:05 PM: unset GOOS;
> 12:14:05 PM: unset GOARCH;
> 12:14:05 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64';
> 12:14:05 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.12.linux.amd64/bin:${PATH}";
> 12:14:05 PM: go version >&2;
> 12:14:05 PM: export GIMME_ENV='/opt/buildhome/.gimme_cache/env/go1.12.linux.amd64.env';
> 12:14:05 PM: go version go1.12 linux/amd64
> 12:14:05 PM: Installing missing commands
> 12:14:05 PM: Verify run directory
> 12:14:07 PM:
> 12:14:07 PM: ────────────────────────────────────────────────────────────────
> 12:14:07 PM:   Netlify Build
> 12:14:07 PM: ────────────────────────────────────────────────────────────────
> 12:14:07 PM:
> 12:14:07 PM: ❯ Version
> 12:14:07 PM:   @netlify/build 9.10.2
> 12:14:07 PM:
> 12:14:07 PM: ❯ Flags
> 12:14:07 PM:   apiHost: api.netlify.com
> 12:14:07 PM:   cacheDir: /opt/build/cache
> 12:14:07 PM:   deployId: 6052f6805b4c730007a04f27
> 12:14:07 PM:   mode: buildbot
> 12:14:07 PM:   testOpts:
> 12:14:07 PM:     silentLingeringProcesses: ''
> 12:14:07 PM:
> 12:14:07 PM: ❯ Current directory
> 12:14:07 PM:   /opt/build/repo
> 12:14:07 PM:
> 12:14:07 PM: ❯ Config file
> 12:14:07 PM:   No config file was defined: using default values.
> 12:14:07 PM:
> 12:14:07 PM: ❯ Context
> 12:14:07 PM:   deploy-preview
> 12:14:07 PM:
> 12:14:07 PM: ❯ Loading plugins
> 12:14:07 PM:    -<EMAIL_ADDRESS>from Netlify app
> 12:14:07 PM:    -<EMAIL_ADDRESS>from Netlify app
> 12:14:09 PM:
> 12:14:09 PM: ────────────────────────────────────────────────────────────────
> 12:14:09 PM:   1. Build command from Netlify app
> 12:14:09 PM: ────────────────────────────────────────────────────────────────
> 12:14:09 PM:
> 12:14:09 PM: $ jekyll build
> 12:14:10 PM: Configuration file: /opt/build/repo/_config.yml
> 12:14:11 PM:             Source: /opt/build/repo
> 12:14:11 PM:        Destination: /opt/build/repo/_site
> 12:14:11 PM:  Incremental build: disabled. Enable with --incremental
> 12:14:11 PM:       Generating...
> 12:14:11 PM:                     done in 0.359 seconds.
> 12:14:11 PM:  Auto-regeneration: disabled. Use --watch to enable.
> 12:14:11 PM:
> 12:14:11 PM: (build.command completed in 2.2s)
> 12:14:11 PM:
> 12:14:11 PM: ────────────────────────────────────────────────────────────────
> 12:14:11 PM:   2. onPostBuild command from netlify-plugin-checklinks
> 12:14:11 PM: ────────────────────────────────────────────────────────────────
> 12:14:11 PM:
> 12:14:14 PM: ...................................................
> 12:14:14 PM:   51 tests
> 12:14:14 PM:   51 passed
> 12:14:14 PM:
> 12:14:14 PM: (netlify-plugin-checklinks onPostBuild completed in 3.3s)
> 12:14:14 PM:
> 12:14:14 PM: ────────────────────────────────────────────────────────────────────
> 12:14:14 PM:   3. onPostBuild command from netlify-plugin-is-website-vulnerable
> 12:14:14 PM: ────────────────────────────────────────────────────────────────────
> 12:14:14 PM:
> 12:14:14 PM: Serving and scanning site from directory '_site'
> 12:14:17 PM:  ⚠  warning (DeprecationWarning)  OutgoingMessage.prototype._headers is deprecated
> 12:14:17 PM: [DEP0066]
> 12:14:17 PM:     at new module.exports (/opt/build/repo/.netlify/plugins/node_modules/union/lib/response-stream.js:50:60)
> 12:14:17 PM:     at new module.exports (/opt/build/repo/.netlify/plugins/node_modules/union/lib/routing-stream.js:30:17)
> 12:14:17 PM:     at Server.requestHandler (/opt/build/repo/.netlify/plugins/node_modules/union/lib/core.js:27:25)
> 12:14:17 PM:     at Server.emit (events.js:310:20)
> 12:14:17 PM:     at parserOnIncoming (_http_server.js:786:12)
> 12:14:17 PM:     at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)
> 12:15:33 PM:
> 12:15:33 PM: ────────────────────────────────────────────────────────────────
> 12:15:33 PM:   Plugin "netlify-plugin-is-website-vulnerable" internal error
> 12:15:33 PM: ────────────────────────────────────────────────────────────────
> 12:15:33 PM:
> 12:15:33 PM:   Error message
> 12:15:33 PM:   UnhandledRejection: a promise was rejected but not handled: LHError: PROTOCOL_TIMEOUT
> 12:15:33 PM:
> 12:15:33 PM:   Plugin details
> 12:15:33 PM:   Package:        netlify-plugin-is-website-vulnerable
> 12:15:33 PM:   Version:        1.0.10
> 12:15:33 PM:   Repository:     git+https://github.com/erezrokah/netlify-plugin-is-website-vulnerable.git
> 12:15:33 PM:   npm link:       https://www.npmjs.com/package/netlify-plugin-is-website-vulnerable
> 12:15:33 PM:   Report issues:  https://github.com/erezrokah/netlify-plugin-is-website-vulnerable/issues
> 12:15:33 PM:
> 12:15:33 PM:   Error location
> 12:15:33 PM:   In "onPostBuild" event in "netlify-plugin-is-website-vulnerable" from Netlify app
> 12:15:33 PM:       at Timeout._onTimeout (/opt/build/repo/.netlify/plugins/node_modules/is-website-vulnerable/node_modules/lighthouse/lighthouse-core/gather/driver.js:352:21)
> 12:15:33 PM:       at listOnTimeout (internal/timers.js:549:17)
> 12:15:33 PM:       at processTimers (internal/timers.js:492:7)
> 12:15:33 PM:
> 12:15:33 PM:   Error properties
> 12:15:33 PM:   {
> 12:15:33 PM:     code: 'PROTOCOL_TIMEOUT',
> 12:15:33 PM:     friendlyMessage: 'Waiting for DevTools protocol response has exceeded the allotted time. (Method: Emulation.setScriptExecutionDisabled)',
> 12:15:33 PM:     lhrRuntimeError: true,
> 12:15:33 PM:     protocolMethod: 'Emulation.setScriptExecutionDisabled'
> 12:15:33 PM:   }
> 12:15:33 PM:
> 12:15:33 PM:   Resolved config
> 12:15:33 PM:   build:
> 12:15:33 PM:     command: jekyll build
> 12:15:33 PM:     commandOrigin: ui
> 12:15:33 PM:     environment:
> 12:15:33 PM:       - REVIEW_ID
> 12:15:33 PM:     publish: /opt/build/repo/_site
> 12:15:33 PM:   plugins:
> 12:15:33 PM:     - inputs: {}
> 12:15:33 PM:       origin: ui
> 12:15:33 PM:       package: netlify-plugin-checklinks
> 12:15:33 PM:     - inputs: {}
> 12:15:33 PM:       origin: ui
> 12:15:33 PM:       package: netlify-plugin-is-website-vulnerable
> 12:15:33 PM: Caching artifacts
> 12:15:33 PM: Started saving ruby gems
> 12:15:33 PM: Finished saving ruby gems
> 12:15:33 PM: Started saving build plugins
> 12:15:33 PM: Finished saving build plugins
> 12:15:33 PM: Started saving pip cache
> 12:15:33 PM: Finished saving pip cache
> 12:15:33 PM: Started saving emacs cask dependencies
> 12:15:33 PM: Finished saving emacs cask dependencies
> 12:15:33 PM: Started saving maven dependencies
> 12:15:33 PM: Finished saving maven dependencies
> 12:15:33 PM: Started saving boot dependencies
> 12:15:33 PM: Finished saving boot dependencies
> 12:15:33 PM: Started saving rust rustup cache
> 12:15:33 PM: Finished saving rust rustup cache
> 12:15:33 PM: Started saving go dependencies
> 12:15:35 PM: Finished saving go dependencies
> 12:15:35 PM: Build failed due to a plugin error: Build script returned non-zero exit code: 3
> 12:15:35 PM: Failing build: Failed to build site
> 12:15:35 PM: Failed during stage 'building site': Build script returned non-zero exit code: 3
> 12:15:35 PM: Finished processing build request in 2m21.883662912s

Hi @covalentbond, is this a reproducible bug? If so can you share a repo reproducing it?
There was an incident yesterday that might have contributed to this issue.

Hey sure! the most recent build failed log can be found here
The repository can be find here

Thanks @covalentbond I was able to reproduce https://app.netlify.com/sites/erez-zowe/deploys/60533a3b21ad63c1a9e85f9b.
Seems to be related to https://github.com/GoogleChrome/lighthouse/issues/6512#issuecomment-780805548
FYI, running locally via netlify-cli does seem to work (using netlify build).


feat: bot.isRunning()

Adds a way to inspect whether or not the bot is currently running.

Interesting... so this never worked before:
// Some transformer to always throw 401 error on getUpdates

try {
  await bot.start();
} catch {}

console.log('abc');
console.log(bot.pollingRunning);

try {
  await bot.start();
} catch {}

grammy:bot Initializing bot +0ms
grammy:core Calling getMe +0ms
grammy:core Calling deleteWebhook +9ms
grammy:bot I am he_exp_bot! +605ms
grammy:bot Starting simple long polling +2ms
grammy:error msg (401: abc) +0ms
abc
true
grammy:bot Simple long polling already running! +3ms

Correct. That was a bug.


Fix a memory reference issue caused by the fact that we always append a new value.

Codecov Report

Merging #1420 into master will decrease coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1420      +/-   ##
============================================
- Coverage     83.71%   83.69%   -0.03%
- Complexity     1522     1523       +1
============================================
  Files           233      233
  Lines          6993     6996       +3
  Branches        661      660       -1
============================================
+ Hits           5854     5855       +1
- Misses          939      940       +1
- Partials        200      201       +1

Impacted Files
Coverage Δ
Complexity Δ

.../sleuth/v1x/OpenCensusSleuthSpanContextHolder.java
81.25% <100%> (-3.2%)
17 <3> (+1)

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 dccc590...1e9857f. Read the comment docs.


Bad UX for starting projects

Let's say I want to create a go project. If I already had the go compiler (etc) installed, I could do a go init followed by garn init. But if I don't, I first have to make a base project with go in an env, then enter that env, then go init, then change the project to a go project (if you did it any earlier, everything would fail since it wasn't a go project).
(This is, mutatis mutandis, true of other stacks too.)
Not sure what the solution is. Maybe making the environment of e.g. a go project succeed even if we can't parse the go project?

It's not a solution to this specific problem, but at least a mitigation: We should have a collection of working examples of garnished projects for different tech-stacks. Either as a cookbook on the website or as a collection of repos on github. So people could either just clone those or at least look up exactly how to set a go project up. (Again, not really a specific solution to this problem, but makes it less bad.)

+1 for working examples. Maybe similar to Realworld Apps or TodoMVC. Maybe, one could even work to show how garn behaves in each setting of TodoMVC and Realworld App.


Include chrono to TimeTypes

Included <chrono.h> in TimeTypes header. My Baxalta lobby app complained when I tried to build it on ubuntu.

Can you make this against the exp_channel branch?

Thanks, Alex!


Update pull_request_template.md with grammar update

Description
Related Issues
How can it be tested?
Impacted packages
Check the NPM packages that require a new publication or release:

[ ] manifest
[] add-manifest
[ ] @mnfst/sdk

Check list before submitting

[ ] I have performed a self-review of my code (no debugs, no commented code, good naming, etc.)
[ ] I wrote the relative tests
[ ] I created a PR for the documentation if necessary and attached the link to this PR
[ ] This PR is wrote in a clear language and correctly labeled

Hello @brunobuddy
Both work.

@JeffJeff4252 chatgpt does not agree
The correct form depends on the tense you're aiming to use. Here's a breakdown:
Correct form:
"I have written" (present perfect tense)
Example: I have written a book.
"I wrote" (simple past tense):
Use this if you're talking about a specific past action.
Example: I wrote an email yesterday.
Why?
"Wrote" is the past tense of write.
"Written" is the past participle, which is used with auxiliary verbs like have or has.
Let me know if you'd like more examples! 😊

I am closing this PR as it is does not solve any problem


Create DenoDB driver

DenoDB project seems to be on ice, closing for now.

DenoDB project seems to be on ice, closing for now.

ya i havent been paying any attention, do you know if anything else has taken its place?

@kinghat Not sure, looking at the issues, people seem to be forking it quite a bit to meet their own needs. Would be nice to have a good Deno ORM.


refactoring

Fixes TypeScript confusion over default object so that the if statements can be removed.

@williamli See https://github.com/zeit/now-cli/pull/2099. I'm not sure we'll need this PR afterwards.


TESTS: DO NOT MERGE refactor(button): convert button to SFC

tests for #305

Codecov Report

Merging #306 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #306      +/-   ##
==========================================
- Coverage   97.15%   97.14%   -0.01%
==========================================
  Files          35       35
  Lines        1369     1367       -2
  Branches      131      131
==========================================
- Hits         1330     1328       -2
  Misses         39       39

Impacted Files
Coverage Δ

packages/button/index.js
92.3% <100%> (-1.03%)
:arrow_down:

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 fbe7999...f17e363. Read the comment docs.

merged #305


What is expected behavior wrt Diagnostic Scopes of Operation?

We have:

LowLevelFuncOperation (which has OperationInternalBase inside with only _updateStatusScopeName) for raw LRO.

ConvertOperation (which has both _waitForCompletionScopeName and _updateStatusScopeName) for grow-up LRO.

That leads to the inconsistent behavior between raw lro and grow-up lro. After we call WaitForCompletionAsync, raw lro has scope DPGClient.Lro.UpdateStatus while grow-up lro has scope DPGClient.LroValue.WaitForCompletion.
Raw LRO:
https://github.com/Azure/autorest.csharp/blob/86230daa6868fb0eb63939fff4801fce5efcb4af/test/AutoRest.TestServerLowLevel.Tests/dpg-customization.cs#L101-L105
Gro-up LRO:
https://github.com/Azure/autorest.csharp/blob/86230daa6868fb0eb63939fff4801fce5efcb4af/test/AutoRest.TestServerLowLevel.Tests/dpg-customization.cs#L119-L123
Could you check out this and let me know what is the expected behavior? Then we could see if it could be fixed.

@pshao25, the guidance can be found here:
https://github.com/Azure/autorest.csharp/issues/2136#issuecomment-1092257699
In general, distributed tracing spans should have the same name as the public API call the customer made.  That means if someone does:
 Operation<BinaryData> result = await new DPGClient(Key, host, null).LroAsync(WaitUntil.Started, "raw");
 await lro.WaitForCompletionAsync();

The spans created should look like:

DPGClient.Lro

HTTP Call

Operation.WaitForCompletion
HTTP Call
...
HTTP Call

This should be true regardless of whether it is a protocol method or a grow-up method.
If someone instead does:
Operation<BinaryData> result = await new DPGClient(Key, host, null).LroAsync(WaitUntil.Started, "raw");
while (!operation.HasCompleted)
{
    await operation.UpdateStatusAsync();
}

The spans created should look like:

DPGClient.Lro

HTTP Call

Operation.UpdateStatus
HTTP Call
Operation.UpdateStatus
HTTP Call
...

This should also be true regardless of whether the customer calls a protocol method or a grow-up method.

@pshao25, could you file any follow-up issues needed to address getting this implemented consistent with the spec?

@annelo-msft Thank you! Then unfortunately, I have to file https://github.com/Azure/autorest.csharp/issues/2236


[FIX] Apply formatting to code

Hi!
Was exploring this repository and saw quite few distracting inconsistencies in the code formatting -- semicolons/no semicolons, 2/4 space indentations, etc.
So, thought I would take the opportunity to run a quick code format. If Stripe's formatting standards are different, I'm very happy to update the configuration or use a different tool (eslint, for example). This PR makes no changes to any content, just formatting.

Thank you for that ❤


evaluate SurfaceViewControlHost for GUI integration

This looks quite interesting. I was totally unaware of it. https://commonsware.com/blog/2020/03/27/peek-surfacecontrolviewhost-android-r.html  (not likely just me; I quickly searched it on handful of communities and got no result)

I have been experimenting this SurfaceControlViewHost thing. I got basic ComposeView working in a standalone example project without any AAP context. Probably we could adopt it as an UI option. It was not simple though: I had to explore some lifecycle and state management bits and stuck at UI theme differences.
There could be more pitfalls as users explore this SurfaceControlViewHost API, but it is the best suited GUI alternative we could choose. No dangerous permissions involved. No complicated transition between UI and non-UI-yet-non-DSP code (e.g. preset loader) required.
Yet, it involves another Service which brings in some consideration. We basically avoid another connection between plugin and host, claiming that any extension requests and replies could be represented "either in the MIDI2 messages or the extension() binder messages". If there is another service connection for GUI, then the overall design might feel awkward.
Unifying the GUI service with AudioPluginService would be an option, but since we have to send a Binder, it will need another function definition which may break service compatibility (V3 -> V4).
Hopefully adding a new message definition would not break it, but we have to ensure that.

^ https://github.com/atsushieno/android-experiment/tree/main/SurfaceControlViewHost-Compose

The initial implementation has landed. It is as (non-)functional as System Alert Window so far.
This issue is only about evaluating SVCH, so handing over any remaining tasks to #150.


infer capture not obtain captured files.why?

Hello infer developers!
I use the infer(v0.17.0) capture command to capture files, but there is no captured folder in the output infer-out directory, and no *.cfg and *.cg files are found. Why?

Infer version v0.17.0.

https://fbinfer.com/docs/advanced-features


Enable shutdown even in presence of poisoned timelines or tenants

I've observed that shutdown doesn't work if layermaps have been poisoned; this was with cargo build_testing and intentional poisoning, then running tests which started to fail because of no free ports.
Initial idea was: We should have a way to poison all of the locks in timeline and tenant, then make sure in a test that these tenants remain /ignore and /load'ble, so we will gain more confidence that we are in fact able to assert! in code. This could be an http endpoint similar to always panic which will be added in #3475.
Initially we should just ensure that poisoned locks are tolerated during shutdown, then on tenant ignore (which could work already).

Alternatively panicking/poisoning could lead to automatic tenant/timeline brokeness, but unsure if that state transition is supported (broken tenants appear only during startup).

It may be a good idea to try parking-lot once again to avoid poisoning

I don't think the poisoning is the issue. We should have a way to gracefully teardown when a panic happens, because there's no knowing if any or all details of tenants/timelines with poisoned internals are okay to continue with. For example: https://github.com/neondatabase/neon/pull/3869#discussion_r1148938447 -- if an assertion is hit, then our metrics would be off and those might get used for billing (might not be used right now). Also I have a PR regarding fixing the metrics because they are just wrong, but that now-draft predates the linked discussion (#3775).

https://github.com/neondatabase/neon/issues/6373#issuecomment-1902125377 shows how when layer flush loop dies (for whatever reason), we get stuck. However, it seems that we lost the feature of poisoning shutting down flush task. So I'll just create new issue and close this.


Playground option to choose among recent, current, and nightly builds

It would be helpful to check specific cases if the playground allowed us to play around in different versions of typescript.  Can that please be an option?

Also, it isn't obvious which version of typescript the current playground is even running.

Is the website source not open? If someone (like me) wanted to make a contribution to address a Website issue like this, where should they look?

Being able to pick the target JS version would also be nice.

There is a selector for the TS version now, but not for nightlies, so I'm going to move this to the TypeScript website repo.


Added time measurements for key steps.

I would like to gain better insight as to what is taking time.
As a result, added some basic timing for some key steps like running an Analysis, Checking for Updates, and Downloading and Processing NVD files.

The other thing you may want to time is the creation of the in memory lucene index - as this can also take a bit more time. I have updated org.owasp.dependencycheck.analyzer.CPEAnalyzer


Fix scalastyle errors of DeltaLogging.scala

What changes were proposed in this pull request?
Fix scalastyle errors of DeltaLogging.scala. Change "// scalastyle:off on" to "// scalastyle:on println" to ensure the validity of grammar checks.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.maruilei seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Bug: BwX fails with different top_level_targetss

Describe the bug
Given //:Library is a dependency of both //:App and //:Test.
xcodeproj(
    ...
    build_mode = "xcode",
    top_level_targets = ["//:App"] # `App` target builds
    # top_level_targets = ["//:App", "//:Test"] # `App` target errors with `no such module Library`

The App target builds if I add //:Library to unfocused_targets.
Versions

Bazel: 6.0.0-pre.20220804.3
rules_xcodeproj: https://github.com/buildbuddy-io/rules_xcodeproj/commit/e11d1d9c799f051f9a01a948fcbebfa83b61e28a
rules_apple: d04edf4136b4818662d7126582ec257aee372339
rules_swift: 6153a848f747e90248a8673869c49631f1323ff3

Additional context
I'll send you the log.

I'm still looking into this. Seems to be an issue with "automatic unfocusing".

This was an interesting bug. Thanks for the report @thii!


Feature: Support config files named "mprocs.yml"

Thanks for creating this terminal UI! I was looking for something just like this and found it really helpful.
Do you think it would be reasonable to support .yml file extension as well? It's also a very common extension for YAML files, and it's supported by GitHub Actions, Docker Compose, and most editors.

Thank you for the PR! I would prefer to keep mprocs simpler when possible. Also, checking an additional file will add a bit to the startup time when no config file was provided. AFAIK, .yaml extension is always supported by editors.
The reason why mprocs.json alternative is supported is because it was the default config file until I switched from json to yaml. So it's kept only for backward compatibility.

Got it -- makes sense! I did some more Googling and it seems like .yaml is the official extension. Closing this.


SSCS-10803 allow clerk and judge to action postponement

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

https://tools.hmcts.net/jira/browse/SSCS-10803

version bump will be done once approved


Allow looping within options menu via keyboard

T268771

Looks good on my side. Thank you @bereket-WMDE, master of keyboard navigation wink. Just address the failing tests and comment @micgro42 made, and I'll leave the final approval to him.

Michael is in Bahamas until next week.

Looks good on my side. Thank you @bereket-WMDE, master of keyboard navigation wink. Just address the failing tests and comment @micgro42 made, and I'll leave the final approval to him.

Michael is in Bahamas until next week.

Michael is in Bahamas until next week.

Thanks for letting me know

Michael is in Bahamas until next week.

Thanks for letting me know

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

Looks good on my side. Thank you @bereket-WMDE, master of keyboard navigation wink. Just address the failing tests and comment @micgro42 made, and I'll leave the final approval to him.

haha.. thanks. thanks.
and thank you for looking into it.

Looks good on my side. Thank you @bereket-WMDE, master of keyboard navigation wink. Just address the failing tests and comment @micgro42 made, and I'll leave the final approval to him.

haha.. thanks. thanks.
and thank you for looking into it.

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

Looking good! I'm realizing now that I failed to understand the issue. It actually had to do with scroll not being activated via keyboard on Chrome (the last option remains hidden), which I guess will be tackled separately ((T267829)). Sorry for the silly confusion 🤦

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

Looking good! I'm realizing now that I failed to understand the issue. It actually had to do with scroll not being activated via keyboard on Chrome (the last option remains hidden), which I guess will be tackled separately ((T267829)). Sorry for the silly confusion 🤦

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

Looking good! I'm realizing now that I failed to understand the issue. It actually had to do with scroll not being activated via keyboard (I was confused because the last option remains hidden in Chrome – while Firefox it all works just fine). I guess thihs will be tackled separately (T267829), so all good. Sorry for the silly confusion facepalm

@SaiSan-WMDE no worries at all. yes, the issue you mentioned is fixed in https://github.com/wmde/wikit/pull/360
thank you for looking into it.
P.S. you can also test that functionality.

I just checked, and it appears that the focus disappears first instead of moving directly to the next option (either the first or the last) whenever the down/up arrow keys are pressed. In other words: two keystrokes are needed in order to loop to the first or last options in the menu.

@SaiSan-WMDE can you check again ? it just finished deploying the new version

Looking good! I'm realizing now that I failed to understand the issue. It actually had to do with scroll not being activated via keyboard (I was confused because the last option remains hidden in Chrome – while Firefox it all works just fine). I guess thihs will be tackled separately (T267829), so all good. Sorry for the silly confusion facepalm

@SaiSan-WMDE no worries at all. yes, the issue you mentioned is fixed in https://github.com/wmde/wikit/pull/360
thank you for looking into it.
P.S. you can also test that functionality.


[MRG] ADD support Apple Silicon (arm64) NEURON mechs

This adds support for Apple Silicon ("M"-series, 64-bit ARM architecture). Tested on a system running

M1 Pro system with 8 cores (6 "performance" and 2 "efficiency" cores)
miniforge instead of vanilla conda (for the arm support)
Python 3.10 (got picked up by conda, not sure by which dependency

(Almost) all tests pass locally. MPI example is working fine, but test_parallel_backends.py chokes when oversubscribing (will create a separate PR).
Support for Mx Macs in hnn-core might need to be flagged as 'experimental'?

 I was just mentioning to @stephanie-r-jones today that hnn_core does not work on M1

Codecov Report

Merging #538 (6b6e20a) into master (9f719c2) will decrease coverage by 0.22%.
The diff coverage is 75.00%.

:exclamation: Current head 6b6e20a differs from pull request most recent head 6d86f13. Consider uploading reports for the commit 6d86f13 to get more accurate results

@@            Coverage Diff             @@
##           master     #538      +/-   ##
==========================================
- Coverage   89.51%   89.29%   -0.23%
==========================================
  Files          20       20
  Lines        3957     3941      -16
==========================================
- Hits         3542     3519      -23
- Misses        415      422       +7

Impacted Files
Coverage Δ

hnn_core/network_builder.py
94.09% <75.00%> (-0.28%)
:arrow_down:

hnn_core/parallel_backends.py
81.49% <0.00%> (-1.66%)
:arrow_down:

hnn_core/cell_response.py
84.00% <0.00%> (-0.54%)
:arrow_down:

hnn_core/extracellular.py
86.50% <0.00%> (-0.27%)
:arrow_down:

hnn_core/cell.py
97.10% <0.00%> (-0.11%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Haha, that's a very positive review! Do you know anyone with an M1 who could test this? I could assist in order to write down the steps. As I recall, I installed miniforge and first conda installed everything I could think of involving compiled code (numpy, matplotlib, probably others) and of course openmpi and mpi4py. The combination will have fetched python=3.10 from conda-forge, hence the new python. Then I just pip install'ed mne, NEURON and hnn-core.

I have @klankinen with whom we tested this a week ago. We could give it another shot with your pull request merged
Is this good to go from your end?

Sure, go ahead and merge since this won't affect anyone with x86 hardware. Perhaps hash out the installation-business over email or in an issue?
It just occurs to me that I don't know how much of my installation is running through Rosetta2. My goal was 0%, and the introduction of ARM support in NEURON 8.1.0 seemed to make that feasible. Just something to keep an eye out for.

Great, thanks @cjayb ! 💯 I'll report back how this goes.

Seems like it worked! Thanks @cjayb !

Excellent! More or less like I described? Perhaps worth saving as an environment.yml for future reference 😅

it was just a pip install !

Nah 🤷♂ I suppose most packages are now building wheels for arm64 per default, so why not just pip away! conda-forge tends to be needed for bleeding edge. I see vanilla miniconda is now also available for M1. MPI of course is still needed from one conda channel or anothe.


Removed unnecessary div reference

I removed the div class reference here because it is not needed. The list is a bullet list.

@caseydierking : Thanks for your contribution! The author, @MashaMSFT, has been notified to review your proposed change.

I just realized what this div reference was for. I was only viewing the documentation on github. I see now that it is necessary for displaying it as a checklist on the Microsoft Docs site.


History inspection episode: refactoring

Here are my plans:

[x] "We will use the following four commands" (grep, show, annotate, checkout -b) becomes a demonstration, not only a list. Instructor will demonstrate these on a real example repo.
[x] Archaeology exercise: instead groups of 2, groups of 4? (in case of video)
[x] Instead of git clone, git clone a particular version (to make sure this will work in future also)
[x] After the exercise bring everybody back into main room and discuss
[x] Git bisect exercise

"Discuss" (collect ideas on how to solve it in the main room)
Distribute participants into breakout rooms with size 4

[x] At the end discuss in the main room and answer hackpad questions

Also I will try to add an advanced exercise to the first exercise (grep, show, annotate, checkout -b).

Solved by #235.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.5 to before v4.9.303",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2f4ce5ec1d447beb42143a9653716a2ab025161e",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3c5ba8d82f5c4df4fbe30e6c5fff49853dad19d1"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "2f4ce5ec1d447beb42143a9653716a2ab025161e",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "3c5ba8d82f5c4df4fbe30e6c5fff49853dad19d1",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "libsubcmd: Fix use-after-free for realloc(..., 0)\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.303 by commit 3c5ba8d82f5c4df4fbe30e6c5fff49853dad19d1, it was introduced in version v4.5 by commit 2f4ce5ec1d447beb42143a9653716a2ab025161e. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000296


Revert "[kmac] Use Empty signal from FIFO"

This reverts commit 0e0c1a99f5a45584017d42bc8cba0aa376745908.
The change appears to have broken the CW310 CI tests
Signed-off-by: Greg Chadwick<EMAIL_ADDRESS>

Merging to fix CI.

Looks like a false alarm this didn't fix the problem. Looking more like an infrastructure issue now.

Sorry @eunchan, I got a bit ahead of myself merging this.

So, did you revert this revert PR?

As you see on the suspected PR, The CI check was passed (pasted as a screenshot in that PR).


[ECC] missing reduction operation on hashed message

To sign or verify a message, the input hash must be reduced modulo q, as specified in RFC6979 page 9. This step was missing in the ECC implementation and caused a discrepancy with the HMAC_DRBG output. This error was not detected by our random tests because the chance of getting a random number larger than q is very low.
We need to add a new test vector with a message that exceeds q to verify this step.

The fix has been implemented, and a set of test vectors (with message greater than q) has been added to ecc testbench to verify this.

https://github.com/chipsalliance/caliptra-rtl/pull/240 sync fixed this.


consider regex matching

Dodo used (read: stole) the e// notation from the ed school of syntax, most other users of this syntax support regex matching and this was always a potential feature for dodo.
PCRE is probably too much but POSIX regex should be sufficient.
Regex search is probably too expensive as in the failure case it would have to go through the whole file, but an anchored regex match (match from current position or die, similar to `expect) could be quite useful.
A potential issue here is of course that any multiple-character matches could be dangerous m/a.*z/, especially if they are greedy by default.
We could make .* NOT match newline characters, but this only helps in the case of files being newline delimited and I think we need to consider the case of operating on large files that lack newlines (however we could just push this issue onto the end user).

If we use
m/Jack and.*Jill/
w/foo/

on the text "Jack and his close childhood friend, Jill", what is the expected output?
Since this is an in-place editor, I'd personally expect "Jack andfoos close childhood friend, Jill", but this goes against the grain of what regex is normally useful for.
Apart from that, matches like m/J... and J... had [0-9] pails would be easy enough to implement.

@phillid I think your interpretation is correct regarding "bark and his close childhood friend, Jill", thanks for the great concrete examples.
For me the important part is to never have a regex search (as I don't want to be performing a text search across a 14G file), only ever a 'match' which is anchored to the current location.

To spitball / scope creep a little:
There is another interesting case in that if we have the sentence
"Jack and his close childhood friend, Jill" and we want to replace Jill ONLY when preceded with a sentence matching a pattern
m/Jack and.*Jill/

is insufficient as it doesn't move the cursor, and there is no current way to know the byte offset from the cursor to the start of Jill (as we lack a search, on purpose).
It might be worth later considering a syntax for specifying where within the regex the cursor should be placed after the match, but would require careful thought around the notation used (so we could strip it out before regex matching)

But that is for later, for now the focus should be getting a concrete implementation of the basic m/pattern/ system
For now it should be sufficient to mock up a wrapper around the posix functions regcomp and regexec, later on we could consider migrating to re2 (https://github.com/google/re2/)
Thanks @phillid for the great work, I should have some time this weekend to start on this but you are also welcome to dive in first.

'This weekend' he said 26 days ago, sorry I have delayed with other things and wont be able to get around to this for a little while yet.


Failed to add scan task

System and Python Environment

Item
Tooltip
Value

System
uname -a
macOS 10.12.4

Python
python -V
2.7.13

Cobra
python cobra.py
v1.7

Description
[Description of the bug or feature]
Steps to Reproduce

Upload a pay2016-master-51f30b3391a0b97edec614bcf918de7b34e394a6.tar.gz file

Background log error

    self._flush(objects)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 2137, in _flush
    transaction.rollback(_capture_exception=True)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__
    compat.reraise(exc_type, exc_value, exc_tb)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 2101, in _flush
    flush_context.execute()
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 373, in execute
    rec.execute(self)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 532, in execute
    uow
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 174, in save_obj
    mapper, table, insert)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 800, in _emit_insert_statements
    execute(statement, params)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 914, in execute
    return meth(self, multiparams, params)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/sql/elements.py", line 323, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1010, in _execute_clauseelement
    compiled_sql, distilled_params
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1146, in _execute_context
    context)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1341, in _handle_dbapi_exception
    exc_info
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 202, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context
    context)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute
    cursor.execute(statement, parameters)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/MySQLdb/cursors.py", line 205, in execute
    self.errorhandler(self, exc, value)
  File "/Users/Users1/Documents/github/cobra/lib/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
DataError: (_mysql_exceptions.DataError) (1406, "Data too long for column 'name' at row 1") [SQL: u'INSERT INTO projects (repository, url, name, author, framework, pe, remark, status, last_scan, created_at, updated_at) VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s, %s, %s)'] [parameters: ('/tmp/cobra/uploads/pay2016-master-51f30b3391a0b97edec614bcf918de7b34e394a6.tar/pay2016-master-51f30b3391a0b97edec614bcf918de7b34e394a6', '', 'pay2016-master-51f30b3391a0b97edec614bcf918de7b34e394a6', 'Upload', '', '', '', 1, '2017-05-10 10:15:55', '2017-05-10 10:15:55', '2017-05-10 10:15:55')]

Because the file name is too long caused.
In the Q2 quarter will be reorganized Cobra, reduce the use of cost, open scanning rules.


Office 365 Cloud App Security link

There is a Note at the top of this page that claims to take you to more info about Office 365 Cloud App Security, but it just redirects to the following page, which doesn't mention Office at all and just has a couple of references to M365.
https://docs.microsoft.com/en-us/cloud-app-security/getting-started-with-cloud-app-security
The same issue occurs with the very first link at the top of the page below ("For information about Office 365 Cloud App Security, see Get started with Office 365 Cloud App Security.").
https://docs.microsoft.com/en-us/cloud-app-security/editions-cloud-app-security-o365
If there has been a rename and the original links are gone, please reconsider how this is called out in the current docs. Thanks!

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

ID: 92f1881c-1d0b-7a96-f8c1-3989b3b5e0cd
Version Independent ID: b50ed5b9-18ab-abde-406e-b3fd1ff61fa2
Content: What is Cloud App Security?
Content Source: CloudAppSecurityDocs/what-is-cloud-app-security.md
Service: cloud-app-security
Product: ****
Technology: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@dcbrown16  Thanks for contacting Microsoft with feedback about our product documentation. Depending on the complexity, it could take from a few business days to a few weeks to look further into your question, issue, or suggestion. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.
Thanks again for submitting your feedback. Your suggestions help improve our documentation.


Navbar update

Update the navbar, merge when finished

[ ] Remove hover/active size changes
[ ] Display Login/Register correctly by checking for loggedIn
[ ] Keep nav displayed on scrolling downwards
[ ] Clean up inline styles & css, prioritize Bootstrap utility classes

Should complete today @HE176788MaiNhatHoang


nz-mention need a '@' with blank as prefix, but ant of react just need '@' as prefix

Reproduction link
https://stackblitz.com/edit/nz-mention
Steps to reproduce
en: Just input @, you will find nothing's going to happen. But if the text you input is ' @'(with blank), the select panel will appear.
cn: 直接输入@, 没有什么反应, 但是输入空格再输入艾特才会出现选择框.
What is expected?
en: The select panel appears whenever I input @
cn: 每次输入@的时候下拉框都会出现
What is actually happening?
en: The prefix is ' @'(with blank)
cn: 前缀是' @'(带有空格)

Environment
Info

ng-zorro-antd
7.5.1

Browser
Firefox 67.0.3 (64-bit)

en: Ant of React does as I expect
cn: Ant of React是直接输入艾特的.

@Eve-1995 感觉是 react 的 bug，因为没办法输入邮箱了， 上一个版本的 mention 不会出现这个问题 https://ant.design/components/mention-cn/。

@Eve-1995 https://github.com/ant-design/ant-design/issues/15694, 看来是新行为。

Still unsolved?

Still unsolved?

Yes, it's not a big deal. But it still exist.


Reduce GA events to stay within limits

We shouldn't be firing off events for every redux action :disappointed:

Thanks for taking care of this so quickly, @Bouncey!


dev: return  JSON RPC error if a RPC endpoint is not implemented

Currently, hitting an endpoint which is not implemented makes the madara panicking.
For instance here, in the RPC lib.
The goal of this issue is to replace this todo! by a JSON RPC error, which will inform the RPC caller that the endpoint is now available yet, and not panicking.
This issue will be using something like:
return Err(StarknetRpcApiError::TxnHashNotFound.into());

Where we may want to add a new RPC error here to handle this specific case (at least for now).

can i take this?

can i take this?

of course, assigned to you.


How to configure CMS block to get image slider and featured product in JSON response?

I have created a cms block and added two category list in it, one is men sale and other is women sale, I don't know which plugin you have used to show  image carousel(slider) hence i haven't added any image slider.
When i am hitting this api
http://<IP_ADDRESS>/magento/index.php/rest/default/V1/cmsBlock/19
I am getting this response in JSON API
{"id":19,"identifier":"MHP9","title":"Mobile Home Page","content":"<p>{{widget type=\"Magento\\CatalogWidget\\Block\\Product\\ProductsList\" title=\"Men Sale\" show_pager=\"0\" products_count=\"10\" template=\"Magento_CatalogWidget::product\/widget\/content\/grid.phtml\" conditions_encoded=\"a:2:[i:1;a:4:[s:4:type;s:50:Magento|CatalogWidget|Model|Rule|Condition|Combine;s:10:aggregator;s:3:all;s:5:value;s:1:1;s:9:new_child;s:0:``;]s:4:1--1;a:4:[s:4:type;s:50:Magento|CatalogWidget|Model|Rule|Condition|Product;s:9:attribute;s:12:category_ids;s:8:operator;s:2:==;s:5:value;s:2:31;]]\"}}<\/p>\r\n<p>{{widget type=\"Magento\\CatalogWidget\\Block\\Product\\ProductsList\" title=\"Women Sale\" show_pager=\"0\" products_count=\"10\" template=\"Magento_CatalogWidget::product\/widget\/content\/grid.phtml\" conditions_encoded=\"a:2:[i:1;a:4:[s:4:type;s:50:Magento|CatalogWidget|Model|Rule|Condition|Combine;s:10:aggregator;s:3:all;s:5:value;s:1:1;s:9:new_child;s:0:``;]s:4:1--1;a:4:[s:4:type;s:50:Magento|CatalogWidget|Model|Rule|Condition|Product;s:9:attribute;s:12:category_ids;s:8:operator;s:2:==;s:5:value;s:2:30;]]\"}}<\/p>","creation_time":"2019-03-26 09:54:43","update_time":"2019-03-27 07:32:13","active":true}
This JSON response  is not in the format that you are getting in your app. Hence I am unable to show anything on Home screen.
I am attaching the link of image showing cms block from magento admin that I have created
Image 1
Image 2
Can you tell me how to configure CMS Block to get JSON response like you are getting for home screeen.

As I can see you receive the same data as you put to the cms block, so it is working correctly. What do you want to receive on the mobile app end?

I want the response that you are getting for home data
{   "slider": [     {       "title": "New Luma Yoga Collection",       "image": "wysiwyg/home/home-main.jpg"     },     {       "title": "Even more ways to mix and match",       "image": "wysiwyg/home/home-t-shirts.png"     },     {       "title": "Find conscientious, comfy clothing in our eco-friendly collection",       "image": "wysiwyg/home/home-eco.jpg"     }   ],   "featuredCategories": {     "30": { "title": "Woman Sale"},     "31": { "title": "Man Sale"}   } }
I want like this so that I can easily extract values and display sliders and list

To get such result, you have to put it to the cms block content.

So you mean you manually typed in this format in the editor????

yes, no magic :)

On Apr 18, 2019, at 1:15 PM, Sanjeev yadav<EMAIL_ADDRESS>wrote:
So you mean you manually typed in this format in the editor????
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/troublediehard/magento-react-native/issues/38#issuecomment-484439165, or mute the thread https://github.com/notifications/unsubscribe-auth/ABSJ5OE7B4NBNKV4H5IKTD3PRBC2PANCNFSM4HGTFPXA.

if you want to generate it automatically, you have to create Magento module which will have admin interface, will generate this output from your selection, and create custom API endpoint to get this information.

Ok thanks for clarification, and how did you know image url, "wysiwg/home/home-t-shirts.png", ??

on magento side it was added from wysiwg editor

on mobile app side
getMediaUrl() {
    return this.storeConfig.base_media_url;
  }


wasm: add support for resuming downstream connection.

Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

@moderation PTAL for deps.

/lgtm deps

@lizan PTAL.

/lgtm deps

This was lost after the merge with the main branch. @moderation could you approve again? Thanks!

/lgtm deps