fix(dialog): improved handling of scrollable content

Improves the handling of scrollable content inside the mat-dialog-content by using flexbox, rather than a hardcoded max-height, to define the content height. This resolves various issues where the dialog would go out of the screen at certain screen sizes or have multiple scrollbars.
Uses flexbox to ensure that the dialog content elements are always at the appropriate size.

Fixes #2481.
Fixes #3239.
Fixes #6584.
Fixes #8493.

Looking forward to this merge!

Great work on this PR!  I am really looking forward to this enhancement as well.  It looks like the only reason it hasn't been merged in yet is because the Travis CI build failed due to server issues.  Can someone please re-run the build?  Thanks!

What are the presubmit failures that are keeping this from being merged?
I, too, am having the same scrolling issues with the material dialogs.

This fix will be very helpful. Any updates on the PR?

Hi, I would really appreciate this fix too, we've been waiting for a year now for this to land (we're eager to take out our own hacks to overcome some issues that this would fix..)
So, any news about this @crisbeto @jelbourn ?

It's blocked until we can resolve this change breaking some things inside Google.

Hi @jelbourn is this issue still blocked on your side?

Yes

This will fix #13190

@crisbeto is this PR going to happen?

This PR would fix major problems I'm having using MatDialog, any updates?

What is the status of this PR? When will it be completed.

@jelbourn is this still blocked?

Yes- we haven't work on this since the last update. At this point, we'll probably see if we can address this as part of our work on integrating MDC-web into the components.

@jelbourn have you had a chance to find out whether integrating MDC-web into the components will solve the problems that this PR intended to solve?

@crisbeto is this something you've looked at for the mdc dialog?

I haven't looked into the MDC dialog since somebody else implemented it.

@crisbeto Looks like this PR has fallen out of date, can you please rebase the PR.

Hope this PR is not abandoned and will be merged someday


[Question] does the Geolocator plugin supports location changes when the App is closed (not running)

[Question] does the Geolocator plugin supports location changes when the App is closed (not running)?
Is there any way to start the App as a service in order to receive the changes in the CrossGeolocator.Current.PositionChanged event?

You would need to put it in a background service on Android or on iOS enable the background location changes.


Request for supporting the new syntax

I'm creating this issue after discussion in the LuaLS/lua-language-server repository - https://github.com/LuaLS/lua-language-server/issues/2165 .
I'm using lua LSP in my own React Monaco Editor client.
I have a plugin for my own syntax, it is that the notation {@WordD_123} is equivalent to "WorD_123". Word_123 can consist of letters, numbers and '_'. I am attaching the file with this plugin.
plugin.txt
Currently, if the user uses this syntax, he cannot format the code.
I understood the conversation in such a way that here I can ask for support for my syntax in formatting.
So I hereby kindly ask you to support my syntax.

You mean your identifiers support the @ symbol, is there anything else?

I mean that the {@token} should be treated as an equivalent to 'token'
For "token" the notatation is {@token} so I can write
local a = {@token}
and now formater does not work.

the syntax is very strange and too similar to Lua's table expressions. I'm curious why it isn't using the '@symbol'.

We have a big code base with legacy syntax like that. I cannot really determine why this was chosen but i'm stuck with it anyway.

I accept this reasoning, and it may take until tonight to implement.

I completed this feature a few days ago, but it hasn't been updated to Sumneko Lua that quickly. You can fork the Lua Ls project yourself and update this submodule separately, then compile it using luamake.

We did as you advised, thank you very much.


Dev humble v1.2.6

Also refer to https://github.com/lbr-stack/lbr_fri_ros2_stack/pull/105

legacy PR


[SPARK-43380][SQL] Fix conversion of Avro logical timestamp type to Long

What changes were proposed in this pull request?
Fix conversion of Avro logical timestamp type to Long
Why are the changes needed?
The fix in https://github.com/apache/spark/pull/41052 cause regression when trying to convert logical timestamp type to Long type and it's not covered by existing test suite. Fix it and add a test for it.
Does this PR introduce any user-facing change?
NO
How was this patch tested?
New unit test

Yeah, I think https://github.com/apache/spark/pull/41052 is only merged to master branch. @dongjoon-hyun


EXOAvailabilityConfig

Pull Request (PR) description
Add DSC resource EXOAvailabilityConfig
This Pull Request (PR) fixes the following issues

This change is

@malauter I don't see any modified files associated with this PR. Can you please have a look. Thanks

Will be re-created.


Python Apps on V4 suddenly getting import errors.

Investigative information
Please provide the following:

Timestamp: 2022-08-19T09:31:17.043Z
Function App version: 4
Invocation ID: 293176d4-510c-4237-b289-7facf2b18af2
Region: West Europe

Repro steps
Create a function app using python and runtime version 4 and set FUNCTIONS_WORKER_PROCESS_COUNT to 5.
4 out of 5 instances of the function app will get ModuleNotFoundError, 1 out of 5 will work correctly.
Expected behavior
No exceptions
Actual behavior
Function suddenly getting ModuleNotFoundError after months, with 0 changes to function app. Fails on the first non-standard library module included in the imports.
Known workarounds
Setting FUNCTIONS_WORKER_PROCESS_COUNT to 1 and reducing to one instance.
Related information
Python 3.8.

Hi @stewartadam Closing this issue as duplicate, it is already being tracked at #1088


chore: Migration to convert formData references

Creating as draft plugins' consumption needs to be updated as well.

/ok-to-test sha=8d64cd8

/ok-to-test sha=5cef82b

@sumitsum Hey so after I resolved the conflicts from upstream, there have been some changes to the S3 plugin structure. Could you please revisit that merge commit to see if the mapping makes sense?

@sumitsum Hey so after I resolved the conflicts from upstream, there have been some changes to the S3 plugin structure. Could you please revisit that merge commit to see if the mapping makes sense?

@nidhi-nair LGTM 👍


How to find DROW for ros?

HI,
I read the paper: DROW: Real-Time Deep Learning based Wheelchair Detection in 2D Range Data and want to test on my own notebook. Can you provide me the link to the ros package of DROW? I searched but couldn't find it.
Thanks.

This information can be found in the README.


gitignore: ignore vim swap files

[One line description of your change]
Motivation:
[Explain here the context, and why you're making that change. What is the problem you're trying to solve.]
Modifications:
[Describe the modifications you've done.]
Result:
[After your change, what will change.]

@swift-nio-bot test this please


Configure sns (3)

External name configuration of 3 resources in the sns group:

aws_sns_platform_application
aws_sns_sms_preferences
aws_sns_topic_policy

Extracted from https://github.com/upbound/provider-aws/issues/55

Corresponding issue: https://github.com/upbound/provider-aws/issues/254


Can't get custom RequestHandler to trigger

I want an API on my Next.js app so I'm trying to set up a custom API route using the custom RequestHandler system described in ReadMe:
const { createServer } = require('http')
const next = require('next')
const routes = require('./routes')
const app = next({ dev: process.env.NODE_ENV !== 'production' })

const customRequestHandler = ({ req, res, route, query }) => {
	const { path, params } = req
	console.log(`customRequestHandler`, { path, route, params, query })
	res.send('OK')
	// app.render(req, res, route.page, query)
}
const handler = routes.getRequestHandler(app, customRequestHandler)

app.prepare().then(() => {
	createServer(handler).listen(process.env.PORT, err => {
		if (err) throw err
	})
})

For some reason, my customRequestHandler doesn’t trigger at all – any tips?

Didn't get this to work with just Node, so I solved it by using Express.


Data Folder

Hello! Nice preprint :)
Is the data directory available to download? Eg the raw h5ads for each dataset.
Thanks!

Hi, and thanks for your interest!
The myeloid, multiple sclerosis, and pancreas datasets were downloaded from the scGPT repo: https://github.com/bowang-lab/scGPT/tree/main/data#datasets-for-cell-type-annotation. I'll update the documentation to make this explicit.
I'll upload an easily accessibly h5ad for the Zheng68K PBMC data to our repo. I'll update this thread once it's there.

Thank you!

updated! https://github.com/clinicalml/sc-foundation-eval/tree/main#data-availability


"auto: no" is not working

oldestdate is active in import, no matter if I set auto to "no" in configuration.

Are you trying to stop the plugin from running at all?

Yes. Now I have a second config file only to use oldestdate.

Well, obviously it's not supposed to run if auto is not enabled, but surely you can just remove oldestdate from the list of plugins to disable it?

Yes. My main config file does not have oldestdate, and I have a second config that activates oldestdate, and I have defined an alias to use it:
alias beetod="beet -c /mnt/main/configs/beet/oldest.yaml oldestdate data_source:musicbrainz"
All set. Thank you!


FEVER and WebShop code

Hello @ysymyth, thanks for sharing your code, excellent work! Is there any plan to release the code of FEVER and WebShop? Thank you!

Hi, these two have been added. WebShop is a bit of a workaround as it scrapes the live site instead of using https://github.com/princeton-nlp/WebShop, but is usable. I'll close it for now and feel free to open new questions!


Editor: Animations: Add initial play functionality to editor

Summary

Updates pagemenu icons to be closer in size to new designs https://www.figma.com/file/Cd9iacVknHK62RO4pRwb68/Stories-Editor?node-id=11070%3A16
Incorporates StoryAnimation.Provider into editor
Adds play button to play anims
Stops animation if page changes or design panel focused
Makes elements unselectable if animation is playing
Removes movable controls, hover highlights & pointer events from frame elements while animations playing or scrubbing
Moves animation control behind enableAnimation flag in editor

Relevant Technical Choices
Renamed animations states object constant to STORY_ANIMATION_STATE since it made more sense to me.
Moved the animation provider in with the display layer. Figured it was part of the display layer so should live there. also needed to be downstream of the story provider where I put the animation state.
To-do
NA
User-facing changes
Page menu icons made smaller to fit updated designs.
Testing Instructions
set enableAnimation to true in Story_Post_Type.php and open a story created from a template with animations in the editor. See that there's now a play button on the bottom right side.

Press the play button and see the animations play.
Select an element then press play and make sure movable controls dissappear when animation playing and reappear when animation complete.
Select an element then press play, while animation playing, select a field in the style editor. see that animation promptly stops.
Press play button. while page is animating press the next page button. Next page should render stopped with play button able to press.
Press play button. while page is animating, try to select an element on the page. Nothing should happen as elements should be unselectable while page is animating.

Select a story you've created that has no animations on it. In editor, make sure play button is there but disabled.
Screenshots

Selecting anything in design panel while animation is playing resets animation to initial stopped state.

Movable boxes disappear & reappear while animation is playing and when it finished

Animation stops when page changed & new page is stopped & playable

(with animation flag disabled) Icon size is closer to new designs

Fixes #3484

I'd think it should be "focusin" event instead?

Yea I can switch to just adding this as a handler to a focusin event in an effect if you'd prefer. Last I checked, react doesn't expose this as a synthetic event, but does differ from the DOM by bubbling up onFocus events which allow the current implementation to work.
Happy to change it regardless, but just for personal learning/growing, what benefits do you see in focusin vs onFocus for the use case here?

That being said, should it pause when we focus into the animations panel itself?

This is how I read the current spec. As soon as you start interacting with the design panel we have it reset the animation to the original state/position.
The other option could be resetting the state from the update element properties action in the reducer so it doesn't reset until you actually submit a value. That feels like a more top down approach, which I like, but is a slightly different UX than the current implementation. idk what are your thoughts here?

Code looks great, but when I click "play" in the editor all the page controls (including the "stop" button) disappear until the animation is complete. Is this intentional?

I fixed this earlier, must have not pushed up most recent commit or something got messed up in a rebase or something. one sec

FYI this needs some merge conflict resolving

@littlemilkstudio It looks like there are some percy visual changes that need to be approved.  It appears that the space of the under-page controls have moved up a little (not sure if that was intentional).

@littlemilkstudio It looks like there are some percy visual changes that need to be approved. It appears that the space of the under-page controls have moved up a little (not sure if that was intentional).

Ah yeaup. I was updating this initially so the play button would fit on the dock, then wassim went through and made a sweeping change that updated the dock. I'll revert it back to wassim's change, then doesn't need to go through QA at all I think


Added FAQ page

For Now I added a static image to the page

adding responsiveness could be better as well

check it once, i did the recommended changes


How to use the tool please

hello im not a developer and i need to run this because i want the courses to be on my laptop please

Hello!
To use this tool is a bit technical, this needs you to have docker install and docker-compose in your local machine (PC) ,
which operating system are you using @lshazly ??

@lshazly ok good, i can give online support if you want please provide me your TeamViewer ID when you ready

can you add me on skype?

add me skype @joramkimata

i added u

Sorry for the silence from my end, haven't (have) no time for github at the moment.
Am crazy busy with my actual work... :/
Here's some extra information and thoughts from me in another issue:
https://github.com/kallqvist/skillshare-downloader/issues/3
I don't have a skillshare account and can't test/develop this any furter so I'm not able to be of much help to anyone.
Good luck!


Stabilize omnisci calcite_server endpoint for serialized calcite input.

I've done some initial work before, so, I need to rebase my changes and do some testing and refactoring.

I've created pr in our omnisci modin branch: https://github.com/intel-go/omniscidb/pull/43

The last changes work with client/server omnisici, but don't work with the embedded engine. For some reason, calcite can not find the schema of the table created by embedded engine, even if it list in its tables() list.
I'm not quite sure where the problem is, need to spend more time debugging.

Should be done now. Waiting for a review after release is finished.


Add Vulnerabilities and license checks

New Feature
Creates two checks:

A check with vulnerabilities added. If the check fails, it adds to the check the list of vulnerabilities found grouped by manifest. The check fails if vulnerable package(s) are added.
License check. A license check is created and it lists on the detail incompatible licenses (if any) and the unknown licenses. The check fails if there are incompatible licenses and succeeds otherwise

By separating the failure in two, users can now control if license or vulnerabilities individually prevent the merge from happening.
Checks names are configurable.
Breaking Changes
A breaking change was introduced, the action no longer fails if there are vulnerabilities or license violations. fail-on-violation parameter can be set to true (default value is false) to maintain backward compatibility.

There is another potential breaking change, since the workflow now requires checks: write permission, might need to add the new permission explicitly. The dependency review starter workflow will also have to be updated to add this permission

@tspascoal I love the idea of having one check per feature, but the main Action one should never be green if one of the children checks fails. Can we overcome this? If not I don't think we should be spending extra cycles here (it's backwards incompatible and adds extra write security permissions).

@tspascoal I love the idea of having one check per feature, but the main Action one should never be green if one of the children checks fails. Can we overcome this? If not I don't think we should be spending extra cycles here (it's backwards incompatible and adds extra write security permissions).

@febuiles Not failing the action, allows extra flexibility since users can fine grain when the PR can't be merged by requiring the checks them want (one of them or both).
Backward compatibility (failing the action if one of the checks fails) can be achieved by explicitly setting the parameter fail-on-violation to true (default value is false).
This allows both the extra flexibility or getting the previous behavior with this parameter.
So getting the old behavior by default, is a matter of changing the default value for  fail-on-violation or let the user control by enabling if they want it.

Backward compatibility (failing the action if one of the checks fails) can be achieved by explicitly setting the parameter fail-on-violation to true (default value is false).
This allows both the extra flexibility or getting the previous behavior with this parameter.

In order for this to be backwards compatible I'd expect it to behave the same way that it has without the user having to modify their YAML. Remember that we pin all release to v2 atm, so we can't release as part of this version because we'll change the behavior for the current users. We can release a v3, but we release major versions only for breaking backwards compatibility!
I don't know how the child checks work, could we default fail-on-violation to true? In that case only users who want this new behavior would be modifying their workflows. We'd be able to switch this behavior once v3 is released if that's the way we want to move forward (still not sure what the right decision is here, would like to hear back from users in case you have feedback!).

I keep forgetting about auth, thanks for bringing it up! We can wait until we have the new config file format before revisiting this.

The latest release of the action (v3) allows users to specify if they want to allow/disallow a specific check (vulns, licenses) in their runs. I know this is not exactly the same functionality this PR provided, but I feel it's close enough to close this for now.


move readme parts and link to new online resources

#171

https://github.com/nfdi4plants/arcCommander-docs/pull/5


Add ErrorEmail plugin to the list

https://github.com/ebrigham1/cakephp-error-email

I really like the thorough documentation on that one!
👍

Thanks :smile:


chore: bdd-nh-1586819313 to 0.0.1

chore: Promote bdd-nh-1586819313 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


What is the difference between LoadSkeletalAnimation and LoadNodeSkeleletalAnimation?

I would like to know the difference between these two methods. The glb I loaded in UE cannot be played. Can you provide a screenshot of the blueprint,
I found that this glb has been parsed as nodeAnimation, but it cannot be played no matter what
Soldier.zip

Hi, Unreal expects animations to be backed up by a skeleton, while glTF allows to animate the transform of any node. For this reason, in addition to standard Skeletal Animations (the ones you extract with LoadSkeletalAnimation) there is a pure-curves extractor that just extracts an array of transforms you can apply as you prefer (there is a pretty naive example in the glTFRuntimeAssetActor class using the Tick).
 You can just use the provided glTFRuntimeAssetActor and you will get the idle animation (it is the first one). Otherwise (once you have the skeletalmesh) you can load one of the 4 with LoadSkeletalAnimation()


add vllm server container, ability to start the server, ilab generate

we now have the ability to do a top level serve in the ilab-wrapper which will start a vllm server, and run generate which will connect to the ENDPOINT_URL specified

cc @n1hility how does this look for vllm. I am working on testing locally, but just making sure the general structure makes sense. This deals with the vllm serve, and the ilab generate.

Are we going to want the vllm container embeded into the nvidia, amd and intel containers?

Are we going to want the vllm container embeded into the nvidia, amd and intel containers?

Yes although starting with just nvidia for now


[diagnostics] handle related informations if sent by compiler

Doesn't have any impact with older Haxe versions, but starting from 4.3 (once https://github.com/HaxeFoundation/haxe/pull/11078 merged), will display better diagnostics
Fixes https://github.com/vshaxe/vshaxe/issues/253
Should also at least improve the situation for https://github.com/vshaxe/vshaxe/issues/388
Before (or after but with Haxe < 4.3)

Above is with Bar.hx open only, giving diagnostics that make no sense on its own

After (Haxe 4.3)

Above is with Bar.hx open only, no diagnostics are relevant there

Maybe position data (Bar.hx[...]) after error text in suberrors will be easier to read? With simple tab for indentation, should be more consistent with first line style.

Maybe position data (Bar.hx[...]) after error text in suberrors will be easier to read? With simple tab for indentation, should be more consistent with first line style.

It's not really the subject here, as that's already how Haxe compiler itself reports this error.
I've made sure to send enough data to be able to improve displaying later, for now it's mostly about not breaking things with Haxe changes.

For context, from the Haxe PR, this is what would happen with Haxe 4.3 without a Haxe LSP update:

A bit of information would be lost for people using outdated Haxe LSP (which should be pretty rare) with Haxe 4.3. Some would say that this would still be more usable than current situation, I suppose.

Still nothing to show here

This one isn't really helpful on its own...

Does this also work with compiler output when compiling ? (not only diagnostics ?)

Does this also work with compiler output when compiling ? (not only diagnostics ?)

Only diagnostics atm but I have a branch I want to revive and cleanup that does that for compiling too


redirect to remove trailing slash

Context
Implement https://github.com/openregister/openregister-java/blob/master/doc/arch/adr-009-trailing-slash.md
Changes proposed in this pull request
Implement redirect in Lambda@Edge.
Guidance to review
See test commands in README. I have also deployed this version of the Lambda to https://country.test.openregister.org

What's the reason for not doing this in ORJ?
I think it makes sense for this to be in the app itself as it's not really adding anything on top of the standard API, it's just an implementation choice. It feels different to API keys, cache invalidation etc.

I did try and do this in ORJ initially but got into a fight with JAX-RS which wants to resolve both styles and I couldn't make it do the desired behaviour. See https://github.com/eclipse-ee4j/jaxrs-api/issues/468 also https://stackoverflow.com/a/15215730/238230

...actually I will try again to do it in ORJ, I have a different idea, let me try that before closing this PR.

closing in favour of https://github.com/openregister/openregister-java/pull/503


[SPARK-5989] [MLlib] Model save/load for LDA

Add support for saving and loading LDA both the local and distributed versions.

Merged build triggered.

Merged build started.

Test build #35533 has started for   PR 6948 at commit 4f7b7a0.

Merged build triggered.

Merged build started.

Test build #35535 has started for   PR 6948 at commit 7ee8603.

Merged build triggered.

Merged build started.

Test build #35536 has started for   PR 6948 at commit 2782326.

Test build #35533 has finished for   PR 6948 at commit 4f7b7a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(termDistributions: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

Test build #35535 has finished for   PR 6948 at commit 7ee8603.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class Module(object):
    case class Data(termDistributions: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

Test build #35536 has finished for   PR 6948 at commit 2782326.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(termDistributions: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

ping @hhbyyh @jkbradley Would be great if you could have a look !

@hhbyyh Thanks for the comment! I have addressed it. Could you also tell me what the edges while constructing the graph denote, I understand that the vertices store that array of topic weights

Merged build triggered.

Merged build started.

Test build #35831 has started for   PR 6948 at commit c753122.

Test build #35831 has finished for   PR 6948 at commit c753122.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(termDistributions: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

Any other comments? @hhbyyh

@MechCoder. I'm OK with the localLDAModel. And for the distributed one, we need Joseph's opinions.

ping @jkbradley

@MechCoder Making a pass now.
In DistributedLDAModel and EMLDAOptimizer, each edge corresponds to a (document, term) pair.  The TokenCount stored at that edge is the number of times the term appears in the document.
In a follow-up PR, we can add load to LDAModel (the abstract class), where it calls the subclasses' load methods as needed.

I think that's it for a first pass.  Quite a few of my comments for LocalLDAModel apply to DistributedLDAModel as well.

@jkbradley I think I've addressed your initial few comments . please have a look now! :)

Merged build triggered.

Merged build started.

Test build #37053 has started for   PR 6948 at commit ea422d5.

Test build #37053 has finished for   PR 6948 at commit ea422d5.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(topics: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #37076 has started for   PR 6948 at commit 4587d1d.

Test build #37076 has finished for   PR 6948 at commit 4587d1d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(topics: Vector)
    case class Data(globalTopicTotals: Double)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

@MechCoder Thanks for the updates.  Those are the only remaining issues I see.

@jkbradley done ! btw is there a preferred way to manually inspect the Parquet files generated?

Merged build triggered.

Merged build started.

Test build #37418 has started for   PR 6948 at commit cc14054.

Test build #37418 has finished for   PR 6948 at commit cc14054.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(topic: Vector)
    case class Data(globalTopicTotals: Vector)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

@MechCoder If you want to manually inspect the Parquet files, reading them back in using Spark SQL is probably the easiest way.  You could also save them instead as JSON with a single partition, which might make it easier to read the files.

Merged build triggered.

Merged build started.

should look ok now, I think

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #26 has started for   PR 6948 at commit 49bcdce.

Merged build triggered.

Merged build started.

Test build #37474 has started for   PR 6948 at commit 49bcdce.

Test build #26 has finished for   PR 6948 at commit 49bcdce.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #37474 has finished for   PR 6948 at commit 49bcdce.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(topic: Vector, index: Int)
    case class Data(globalTopicTotals: Vector)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

@jkbradley I will not be available till Tuesday, so if you have any minor comments feel free to address them and commit.

LGTM.  I'll retest once more, then merge.  Jenkins test this please
For testing the private fields of DistributedModel, can you please follow up with a PR which makes those items private[clustering] and tests those in the unit suite?  Thanks!
Also, can you please make & link a JIRA for adding save/load to the Python API?

Test build #1144 has started for   PR 6948 at commit 49bcdce.

Test build #1144 has finished for   PR 6948 at commit 49bcdce.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    case class Data(topic: Vector, index: Int)
    case class Data(globalTopicTotals: Vector)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Sounds good,

Merging with master.  Thanks!

Will follow up with both the PR's tonight.


pmbootstrap: 1.50.1->2.0.0

Description of changes
Release 2.0.0

After bumping the minor version 53 (!) times in 1.x.y, we have some
breaking changes justifying a major version bump. For users it should
still feel the same overall. Enjoy this release, and thanks so much to
everybody who contributed to it!

"Breaking" changes:
* Remove distcc support (was already disabled by default since
  crossdirect had been added in 2019)
  * Remove --no-crossdirect argument
* flasher: remove long deprecated flash_system alias
* flasher: set default fastboot rootfs partition to userdata

Features:
* aportgen: replace deviceinfo_modules_initfs for modules file
* pmb.install: create fstab and crypttab
* Add mtkclient as a flasher option
* Install makedepends in native chroot for packages using Rust
* Support --no-cgpt
* lint: drop call to pmb.build.init
* aportgen: use pmb.build.init_abuild_minimal
* pmb.config: only show first 3 releases
* init: allow all locales
* pmb.flasher: Improve flash_lk2nd action
* pmb.helpers.frontend: Also clear testsuite log when running log -c
* Don't use 'sudo' when running as root
* config: use en_US as default locale
* pmb: Remind users to ensure pmbootstrap is updated before reporting errors

Fixes:
* pmb.helpers.run_core: fix proxy env var logic
* pmb/partition: fix cgpt root_size to not cause resize on boot
* pmb.helpers.run_core: always configure proxy vars if set in environment
* install/partition: set efi flag with cgpt
* pmb.config: Use Python 3.8-compatible type annotation
* envkernel.sh: use realpath to deal with symlink
* pmb.helpers.run_core: fix sudo timer when not using sudo
* install: run setup-timezone with "-i" when appropriate
* pmb.config: select default UI in case current is not available
* pmb.config: set default UI to console
* pmb.config: add missing flash_rk_partition* flags
* pmb.qemu.run: replace removed -soundhw option
* pmb.helpers.run: fix sudo timer
* pmb.config.sudo: Use type union compatible with Python 3.7

Other:
* aportgen: device: rename modules to modules-initfs
* test: fix test_build_depends_binary_outdated
* test: fix running test_build_package.py standalone
* deviceinfo: make parse_kernel_suffix private
* pmb.helpers.run_core: move flat_cmd here
* test/test_pkgrel_bump: make sure pmb doesn't cross compile
* test: crossdirect: update stable branch ref
* test: specify default git branch
* test: dont fail on githook symlinks
* CI: add codespell
* treewide: fix typos found with codespell
* install/partition: rearrange cgpt commands in natural order
* CI: enable eval-annotations for vermin
* Remove workaround for gcc with !tracedeps
* install: move setup_timezone to its own function
* treewide: rename _system to _rootfs in various places
* pmb.flasher: remove outdated comment
* Use ruff for linting
* aportgen/binutils: set pmOS bugurl
* aportgen/binutils: add more makedepends_host
* aportgen/binutils: order fields alphabetically
* pmb.flasher.frontend: Use elif instead of repeated if

Release 1.53.0

Features:
* Speed up 'pmbootstrap checksum'
* build: make preferred target arch configurable
* kconfig check: Add USB gadget check to community

Fixes:
* install: write new file instead of modifying locale.sh from alpine-baselayout

Other:
* pmb.build.init: refactor init marker related code
* config: sort config_keys and fix layout

Release 1.52.0

Features:
* pmb.config.init: copy pmaports githooks to default git hooks dir
* pmb: Set PMBOOTSTRAP_CMD to argv[0] in environment
* pmb.parse.kconfig: Pass background color for menuconfig
* install/partition: set esp flag for /boot when using GPT
* qemu/run: add support for EFI boot
* parse/arguments: add qemu --efi option
* install: make cached remote repositories available on first install
* install: run alpine-appstream-downloader if available
* qemu: warn that network won't work with ui=none
* config: Add BINFMT_ELF and BINFMT_SCRIPT
* pmb.config: mount go caching directories

Fixes:
* build: support new abuild.conf path
* envkernel.sh: building x86 on x86_64 does not require a cross compiler
* setup.py: adjust path to pmb.__version__
* pmb.config.pmaports: replace aports split msg
* pmb.helpers.other.validate_hostname: allow periods
* pmb.parse.kconfig.check: fix writing to list arg
* pmb.parse.arguments: don't use python 3.9 feature
* pmb.aportgen.device: fix flash method autocomplete
* kconfig check: ANDROID_BINDER_IPC_SELFTEST not set
* kconfig_options_waydroid: enable PSI
* kconfig_options_waydroid: update to android 11
* kconfig check: extract_arch: support riscv64
* kconfig check: extract_version: replace - with _
* pmb.config.apkbuild_attributes: Add _depends_dev
* pmb/parse/arch.py: add riscv64 -> riscv to kernel carch mapping
* pmb.aportgen.linux: Depend on findutils
* pmb.helpers.run: don't pass stdin to output=stdout

Other:
* Move version to pmb.__version__
* pmbootstrap.py: move all features to pmb:main()
* pmbootstrap.py: require at least python 3.7
* Bump min. required Python version to 3.7
* test/test_zzz_keys.py: move from test/test_keys.py
* kconfig_options_waydroid: order alphabetically
* pmb.build.kconfig: split extract_and_patch_sources
* parse.arguments.add_kernel_arg: add nargs param
* pmb/build/kconfig.py: rename from menuconfig.py
* test: rework kconfig check tests
* kconfig check: less errors for non-detailed mode
* kconfig check: add --no-details argument
* kconfig check: add descriptions to more functions
* kconfig check: move check_config_options_set up
* kconfig check: drop "necessary_"
* kconfig check: config_file -> config_path
* kconfig check: remove redundant component lists
* pmb.parse.kconfig: remove config_path_pretty
* pmb.parse.kconfig.check_option: refactor
* pmb.parse.arch: Include comma after last dictionary items
* partition_cgpt: use pmb.chroot.apk.install
* ci/pytest.sh: check if pmaports dir is clean

Release 1.51.0

Features:
* pmbootstrap init: don't allow 'root' as username
* check_binfmt_misc: print more helpful error
* pmb.build.other: do not copy leftover abuild dirs

Fixes:
* qemu: ssh hostfwd on <IP_ADDRESS> instead of <IP_ADDRESS>
* pmb.qemu.run: fix 3d accel on amd64

Other:
* Bump copyright to 2023

Things done
I've flashed pmOS using a local build of 2.0.0 to one of my phones and everything seems good with pmbootstrap.
Five new tests were added since version 1.50.1 that are not happy but the binary still seems to work if you add them do the list of disabled tests.
Backport to release-23.05 would be appreciated.

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@lilyinstarlight can this PR be merged? pmbootstrap no longer works - at least 1.53.0 is required to make it work.

@ofborg eval
I'm requesting a fresh ofborg eval since this one is a bit stale. Otherwise this change looks fine to me if someone can confirm it works

Backport to release-23.05 would be appreciated

Is this a breaking change? If it's already broken on release-23.05 we can probably still backport even if it is technically breaking, but it might be best to get a RM's blessing if it is and if you still want it backported

I'm on unstable now so I don't mind too much; when I was on 23.05 it was broken as well, so I think I mentioned a backport because of that. But, there are technically breaking changes, per the 2.0.0 release note. Since the package is broken on the current version, maybe the 23.05 release package should be marked as broken if we don't want to push a breaking change?

"Breaking" changes:
* Remove distcc support (was already disabled by default since
 crossdirect had been added in 2019)
* Remove --no-crossdirect argument
* flasher: remove long deprecated flash_system alias
* flasher: set default fastboot rootfs partition to userdata

Since the package is broken on the current version, maybe the 23.05 release package should be marked as broken if we don't want to push a breaking change?

I mean breaking change is broadly better than leaving it broken, but also 23.11 will be here soon enough, so it's up to you
Could also just merge to master for now and let someone ask for a backport if they really want one
Also if someone can confirm that this PR still works, I'm otherwise fine to hit merge on it now. Thank you for the contribution!

@philipwilk is the new update working for you? Looks like it is failing for me because of xkbcommon:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

@philipwilk is the new update working for you? Looks like it is failing for me because of xkbcommon:
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

When does it say this for you, when you run a specific command or always regardless?
Imo it's unlikely to be an issue with this package because it doesn't import libxkbcommon (afaik), and it doesn't really make sense for it to be doing so bc it's a cli app so why would it care about some x11 keyboard lib.

@philipwilk I got rid of the package now, but it looks like if I don't use the flag --host-qemu, it won't work. And the resulting display has an inverted mouse.


Release v0.0.3 ?

Hello,
Would be possible to release a new version with the last changes added after v0.0.2? Or are some things still missing that you would like to add to a release?
Thank you.

@jose-lpa yes, shure, I will add tomorrow!)

Thank you @mishagrol , much appreciated :slightly_smiling_face: I will close this issue then.


use calculated spsnal width and height for pixel_dimensions

doesn't cargo.toml need to be updated?


display transaction signers

The transaction view currently displays signatures but not signers. This makes it difficult to understand which signers actually signed the transaction.
A low hanging fruit is to render the hint present in DecoratedSignature similarly to how it's done in Stellar laboratory.
A step beyond that would be to actually match a signer to the hint. This is fairly simple but requires collecting all the signers of the source accounts (of both transaction and operation, if present) and finding a match to the hint.

Implemented in v0.9.27


Include colors from new soroban landing page

Very simple change here. The yellow color looks great in dark mode, but was a bit "grating" on the eyes in light mode, so I went with the teal-ish color there instead. Would love to hear what everybody thinks 👍🏻

Preview is available here:http://soroban-docs-pr451.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr451.previews.kube001.services.stellar-ops.com/


research smart contracts event decoding

The Smart Contract verification now allows to decode events of smart contracts in the following table: https://aescan.io/contracts/ct_9cYQVU42y1icb9VEGijUs93xyTbKwmq4d7JhdnTYPZ7rMQhwz?type=events
A research should outline what can be decoded from the logs endpoint, used in the smart contracts event table:
https://mainnet.aeternity.io/mdw/v2/contracts/logs?contract_id=ct_9cYQVU42y1icb9VEGijUs93xyTbKwmq4d7JhdnTYPZ7rMQhwz&aexn-args=true

related https://github.com/aeternity/aescan/issues/362


Fix incorrect Content-Type headers in Docker

This PR fixes artifacts always being returned with Content-Type: text/plain when Reposilite is run from the default image, which resulted in Firefox saving all artifacts with the .txt file extension (tested with Firefox 82.0.3 on Windows 10 20H2, and reposilite 2.9.6 from the official image on the server).
Reposilite uses java.nio.file.Files.probeContentType(Path) when determining the content type of an artifact, and if this returns null then it falls back to Javalin's default of text/plain. On Linux, OpenJDK uses the /etc/mime.types file to determine file types, but the openjdk:14-alpine image doesn't ship with a mime.types file. This PR changes the Dockerfile to install mailcap which provides a mime.types file, allowing file type detection to work properly.
Note: prior to JDK 9, OpenJDK used to optionally use libmagic when available, but this was removed and is unlikely to return. In JDK 14 (which this image uses), the only implementation of FileTypeDetector present by default on Linux is the MimeTypesFileTypeDetector mentioned previously.

Welcome, @mdcfe!
Thanks for your contribution with this detailed description related to the issue.
I'm aware of some problems associated with native based recognition of mime types and I think it might be a good idea to replace it in the future with some dedicated library or just a list of known files located in the repository.
Anyway, I didn't know about this problem on alpine distributions and I'm ready to merge this 👍

I've released it as a 2.9.6b, just to force Docker CI to build a new version of 2.9.6. It should be available in a couple of minutes.


[IR]  eager constant folding in operator overloading

Make sure Expr now eargerly folds constant when it is integer expression, removes the need to call simplify in all concrete shape inference case so that we can reuse symbolic integer for concrete inference.
Example
x = tvm.const(1)
y = x + 1
assert isinstance(y, tvm.expr.IntImm) and y.value == 2

@yzhliu @MarisaKirisame can you help do a quick round of review?

Thanks @zhiics for very helpful comments, i have fixed them, can you please take another round of look?

Thanks @MarisaKirisame for the comments, I have fixed accordingly

@tqchen LGTM. I have the same question again, will/should we have reach-def and/or liveness analysis in Relay? We might want them to help some data flow related opts.

@zhiics it might make sense to do so, but I would like to see such pass driven by a real end to end usecase, e.g. memory allocation pass

@zhiics @MarisaKirisame can you please https://docs.tvm.ai/contribute/code_review.html#approve-and-request-changes-explicitly

Thanks @MarisaKirisame @junrushao1994 @zhiics this is now merged


Cannot read property 'configureKey' of undefined

It looks like this error is occurring with my MINIZB. It's the only router on the network and it functions correctly as far as I can tell, both routing and switching.
Logs
This is repeated back-to-back. (see "rejection id: 991")
(node:908) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 991)
(node:908) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'configureKey' of undefined
    at ConfigurableAccessory.set isConfigured [as isConfigured] (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:207:74)
    at ConfigurableAccessory.<anonymous> (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:179:28)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/lib/node_modules/homebridge-zigbee-nt/dist/accessories/zig-bee-accessory.js:5:58)
    at runMicrotasks (<anonymous>)
    at runNextTicks (internal/process/task_queues.js:58:5)
    at processTimers (internal/timers.js:494:9)

On restart with debug on:
[5/11/2021, 6:25:58 PM] [ZigBee] Reading KEY 'state' from '0xb4e3f9fffec64732'
[5/11/2021, 6:25:58 PM] [ZigBee] Zigbee message from 0xb4e3f9fffec64732 {
  type: 'readResponse',
  device: Device {
    ID: 2,
    _type: 'Router',
    _ieeeAddr: '0xb4e3f9fffec64732',
    _networkAddress: 35519,
    _manufacturerID: 4098,
    _endpoints: [ [Endpoint], [Endpoint] ],
    _manufacturerName: 'SONOFF',
    _powerSource: 'Mains (single phase)',
    _modelID: '01MINIZB',
    _applicationVersion: undefined,
    _stackVersion: undefined,
    _zclVersion: 3,
    _hardwareVersion: undefined,
    _dateCode: '20200927',
    _softwareBuildID: undefined,
    _interviewCompleted: true,
    _interviewing: false,
    _skipDefaultResponse: false,
    meta: {},
    _lastSeen:<PHONE_NUMBER>526,
    _linkquality: 145
  },
  endpoint: Endpoint {
    ID: 1,
    profileID: 260,
    deviceID: 256,
    inputClusters: [ 0, 3, 4, 5, 6, 4096 ],
    outputClusters: [ 4096 ],
    deviceNetworkAddress: 35519,
    deviceIeeeAddress: '0xb4e3f9fffec64732',
    clusters: { genBasic: [Object], genOnOff: [Object] },
    _binds: [],
    _configuredReportings: [],
    meta: {}
  },
  data: { onOff: 0 },
  linkquality: 145,
  groupID: null,
  cluster: 'genOnOff',
  meta: {
    zclTransactionSequenceNumber: 16,
    manufacturerCode: null,
    frameControl: {
      frameType: 0,
      manufacturerSpecific: false,
      direction: 1,
      disableDefaultResponse: false,
      reservedBits: 0
    }
  }
}
[5/11/2021, 6:25:58 PM] [ZigBee] Decoded state from incoming message { state: 'OFF' }
[5/11/2021, 6:25:58 PM] [ZigBee] Updating state of device 0xb4e3f9fffec64732 with  { state: 'OFF' }
[5/11/2021, 6:25:58 PM] [ZigBee] Updated state for device 0xb4e3f9fffec64732 is now  { state: 'OFF' }
[5/11/2021, 6:25:58 PM] [ZigBee] Updating service 00000049-0000-1000-8000-0026BB765291 for device 0xb4e3f9fffec64732 with state { state: 'OFF' }
[5/11/2021, 6:25:58 PM] [ZigBee] Device state (0xb4e3f9fffec64732):  {}
(node:5153) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'configureKey' of undefined
    at ConfigurableAccessory.set isConfigured [as isConfigured] (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:207:74)
    at ConfigurableAccessory.<anonymous> (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:179:28)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/lib/node_modules/homebridge-zigbee-nt/dist/accessories/zig-bee-accessory.js:5:58)
(node:5153) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)

[5/11/2021, 6:26:58 PM] [ZigBee] Reading KEY 'state' from '0xb4e3f9fffec64732'
[5/11/2021, 6:26:58 PM] [ZigBee] Zigbee message from 0xb4e3f9fffec64732 {
  type: 'readResponse',
  device: Device {
    ID: 2,
    _type: 'Router',
    _ieeeAddr: '0xb4e3f9fffec64732',
    _networkAddress: 35519,
    _manufacturerID: 4098,
    _endpoints: [ [Endpoint], [Endpoint] ],
    _manufacturerName: 'SONOFF',
    _powerSource: 'Mains (single phase)',
    _modelID: '01MINIZB',
    _applicationVersion: undefined,
    _stackVersion: undefined,
    _zclVersion: 3,
    _hardwareVersion: undefined,
    _dateCode: '20200927',
    _softwareBuildID: undefined,
    _interviewCompleted: true,
    _interviewing: false,
    _skipDefaultResponse: false,
    meta: {},
    _lastSeen:<PHONE_NUMBER>526,
    _linkquality: 145
  },
  endpoint: Endpoint {
    ID: 1,
    profileID: 260,
    deviceID: 256,
    inputClusters: [ 0, 3, 4, 5, 6, 4096 ],
    outputClusters: [ 4096 ],
    deviceNetworkAddress: 35519,
    deviceIeeeAddress: '0xb4e3f9fffec64732',
    clusters: { genBasic: [Object], genOnOff: [Object] },
    _binds: [],
    _configuredReportings: [],
    meta: {}
  },
  data: { onOff: 0 },
  linkquality: 145,
  groupID: null,
  cluster: 'genOnOff',
  meta: {
    zclTransactionSequenceNumber: 17,
    manufacturerCode: null,
    frameControl: {
      frameType: 0,
      manufacturerSpecific: false,
      direction: 1,
      disableDefaultResponse: false,
      reservedBits: 0
    }
  }
}
[5/11/2021, 6:26:58 PM] [ZigBee] Decoded state from incoming message { state: 'OFF' }
[5/11/2021, 6:26:58 PM] [ZigBee] Updating state of device 0xb4e3f9fffec64732 with  { state: 'OFF' }
[5/11/2021, 6:26:58 PM] [ZigBee] Updated state for device 0xb4e3f9fffec64732 is now  { state: 'OFF' }
[5/11/2021, 6:26:58 PM] [ZigBee] Updating service 00000049-0000-1000-8000-0026BB765291 for device 0xb4e3f9fffec64732 with state { state: 'OFF' }
[5/11/2021, 6:26:58 PM] [ZigBee] Device state (0xb4e3f9fffec64732):  {}
(node:5153) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'configureKey' of undefined
    at ConfigurableAccessory.set isConfigured [as isConfigured] (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:207:74)
    at ConfigurableAccessory.<anonymous> (/usr/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:179:28)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/lib/node_modules/homebridge-zigbee-nt/dist/accessories/zig-bee-accessory.js:5:58)
    at runNextTicks (internal/process/task_queues.js:58:5)
    at processTimers (internal/timers.js:494:9)
(node:5153) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)

Config
{
    "bridge": {
        "name": "Homebridge",
        "username": "0E:E1:23:A2:21:xx",
        "port": 51433,
        "pin": "567-52-xxx"
    },
    "accessories": [
        {
            "name": "Air Purifier",
            "deviceId": "foobar",
            "nameAirQuality": "AQ",
            "showAirQuality": true,
            "showPlasmawave": true,
            "accessory": "WinixC545"
        }
    ],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "email": "foobar",
            "password": "foobar",
            "platform": "myQ"
        },
        {
            "name": "ZigBee",
            "port": "/dev/ttyACM0",
            "channel": 17,
            "secondaryChannel": "19",
            "adapter": "deconz",
            "routerPollingInterval": 30,
            "disableRouterPolling": false,
            "disableHttpServer": false,
            "disableLed": false,
            "preferAutoDiscover": false,
            "customDeviceSettings": [
                {
                    "ieeeAddr": "foobar",
                    "friendlyName": "Front Door"
                },
                {
                    "ieeeAddr": "foobar",
                    "friendlyName": "Front Room Window"
                }
            ],
            "platform": "ZigbeeHomebridgeNTPlatform"
        }
    ]
}

Environment
noah@fleetwood:~$ uname -a
Linux fleetwood 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

noah@fleetwood:~$ sudo lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 1: Dev 5, If 0, Class=Communications, Driver=cdc_acm, 12M
    |__ Port 1: Dev 5, If 1, Class=CDC Data, Driver=cdc_acm, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 8: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
            |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/3p, 12M
                |__ Port 3: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M
                |__ Port 3: Dev 8, If 2, Class=Vendor Specific Class, Driver=btusb, 12M
                |__ Port 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=btusb, 12M
                |__ Port 3: Dev 8, If 3, Class=Application Specific Interface, Driver=, 12M
            |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

Node.js Version | v14.16.1

The same happens with IKEA of Sweden TRADFRI bulb E27 WW 806lm Model LED1836G9.

Any solution yet? I had to re-install everything I cannot pair my devices anymore  because of this :(


Make helper functions in CoreDataModelable public

This PR:

renames entityInContext to entityDescriptionInContext
makes entityDescriptionInContext a public function
makes fetchRequestForEntity a public function
enables code coverage gathering for all targets

Addresses #89

:eyes: @jeremy-w


change command structure to allow array of help messages

This makes each 'module' / 'addon' more functional, and can return more detailed help than the.. terrible thing we got now.

Done


No result when taking image with camera

So I start the ImageCropper like this:
findViewById(R.id.fab).setOnClickListener(v -> CropImage.activity()                 .setGuidelines(CropImageView.Guidelines.ON)                 .setFixAspectRatio(true)                 .setAspectRatio(1, 1)                 .start(this));
And try to retrieve the result of it like this:
@Override protected void onActivityResult(int requestCode, int resultCode, @Nullable Intent data) {    super.onActivityResult(requestCode, resultCode, data);    if (requestCode == CropImage.CROP_IMAGE_ACTIVITY_REQUEST_CODE) {    CropImage.ActivityResult result = CropImage.getActivityResult(data);             if (resultCode == RESULT_OK && result != null) {                 Uri resultUri = result.getUri();                 try {                     Bitmap bitmap = MediaStore.Images.Media.getBitmap(this.getContentResolver(), resultUri);                     evaluateImage(bitmap);                 } catch (IOException e) {                     e.printStackTrace();                 }             }         }     }
But this only works when I select an image from my gallery. When I try to take an image with the camera and confirm the image afterwards, I get redirected to the MainActivity. I don't have a chance to crop the image i just took. Is there something I'm missing?

🚨🚨🚨🚨🚨 THIS LIBRARY IS NOT MAINTAINED, PLEASE READ THIS 🚨🚨🚨🚨🚨 #818


questions about Table 2 in the paper

Hello, thanks for the good work.
Just about the Generalization without fine-tuning evaluation of PSMNet in Table 2.
In the Table 2, the Middlebury 3 px Error of PSMNet trained on Scene Flow datatest is 12.96, while we got the 21.2, which is far from that reported in your paper. And the pre-trained model from github performances 23.24.
We use the 15 training images of Middlebury from https://vision.middlebury.edu/stereo/submit3/
Do you use a subset of these 15 images or
10 evaluation training sets with GT or
13 additional datasets with GT from https://vision.middlebury.edu/stereo/data/scenes2014/#description ?
Wondering the reason about it.
Thanks.

Hi @jiaw-z, this is odd. Here are some info I think can clarify things up a little.

Dataset: I used the 15 training images from Middlebury. And quarter resolution.
Pretrained weights: I used the one provided by the author, which gives me the 12.96 3px error. I re-trained PSMNet with the same setup but with my augmentation, which gives me 10.24 3px error.
Evaluation: do you evaluate all pixels of non-occluded only? I evaluated non-occluded only for fair comparison against STTR. This may also make a difference.

Problem solved.
It's I evaluate both the occ and noc.
Thanks for your help.


Incompatible with Gorm V2

This library is currently not compatible with Gorm v2. I've tried to create a PR, but I don't understand what should be used instead of NewScope or tx.New(), so I'm unable to rewrite his for the new version.
Could someone look into this and release an updated version? Thank you.
/cc @jinzhu

https://gorm.io/docs/write_plugins.html

me too


Use version of optional dependencies

Quoting earlier issue https://issues.gradle.org/browse/GRADLE-1293:

I have a dependency to log4j.
dependencies {
compile group: 'log4j', name: 'log4j', version: '1.2.+'
}
The log4j has an optional dependency to javax.mail.
ivy-1.2.16.xml:
<dependency org="javax.mail" name="mail" rev="1.4.1" force="true" conf="optional->compile,master"/>

I defined a runtime dependency, because we need the mail.
dependencies {
compile group: 'log4j', name: 'log4j', version: '1.2.+'
runtime group: 'javax.mail', name: 'mail', version: '1.+'
}
I do not want to define the version ('1.+'). But without the version I
get an error.

Expected Behavior
Another example: spring-web:4.3.5.RELEASE declares an optional dependency on jackson-databind:2.8.5.
There could be a way to tell to include that particular dependency with version specified by the spring-web module itself, e.g. something like
    compile (group: 'org.springframework', name: 'spring-web', version: '4.3.5.RELEASE') {
        include 'com.fasterxml.jackson.core:jackson-databind' //  wishful thinking here
    }

Context
This feature would seem to have supported general usage pattern of transient dependencies. That it, as long as version of a transient dependency is not that important, one does not need to manually specify it.
Your Environment
Gradle 3.3

Duplicate of #867

@oehme Why is this a duplicate of #867 ? They can be fixed together, but this is not a duplicate. Please reopen this issue.
I created the original issue 7 years ago and there is still no solution.

You're right, this is not a duplicate, I misjudged it based on the title.

This will be supported in Gradle 4.6 using this opt-in in settings.gradle:
enableFeaturePreview('IMPROVED_POM_SUPPORT')
It will be supported by default with Gradle 5.0.
Feel free to try this with the current nightly and provide feedback.

@jjohannes I think a bit more explanation is necessary here: @jevgeniv originally asked for this syntax to turn an optional dependency into a hard one:
 compile (group: 'org.springframework', name: 'spring-web', version: '4.3.5.RELEASE') {
    include 'com.fasterxml.jackson.core:jackson-databind' //  wishful thinking here
  }

With the new feature this will instead look like this:
 compile (group: 'org.springframework', name: 'spring-web', version: '4.3.5.RELEASE')
 compile 'com.fasterxml.jackson.core:jackson-databind' //version comes from the optional dependency in spring-web

Thank you. It works.
dependencies {
    implementation 'log4j:log4j:1.2.17'
    runtimeOnly 'javax.mail:mail'
}

runtimeClasspath - Runtime classpath of source set 'main'.
+--- log4j:log4j:1.2.17
|    \--- javax.mail:mail:1.4.3
|         \--- javax.activation:activation:1.1
\--- javax.mail:mail -> 1.4.3 (*)


Wrote a high level description of the slope

Included an equation, related it to derivatives and linked to a writeup of them.

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding. ✈


設定客製抬頭會與設定不符

Problem

會與config.json不一樣 會有亂碼
Steps to reproduce
0
Expected behavior
0
PTSD version
commit b55fbeb4
Operating system/version
win11
CMake version
unknown
CMakeCache.txt
CMakeCache.txt
OpenGL Info
[info] OpenGL Info
 [info]   Vendor: NVIDIA Corporation
 [info]   Renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
 [info]   Version: 4.1.0 NVIDIA 552.22
 [info]   GLSL Version: 4.10 NVIDIA via Cg compiler

This is caused by the string_view PTSD_Config::TITLE pointing to bad address. Will be fixed in days.


Rewrote postinstall to Python (3.6+)

What does this PR (Pull Request) do?
This PR features a rewrite of postinstall to Python3 (specifically the _postinstall Perl script). This is important because the Perl version of the script depended upon multiple libraries installed as dependencies of the Perl version of Traffic Ops - and if we are ever to get rid of that TO version things that depend on its dependencies will need to be reworked.
The new postinstall.py script has no dependencies outside of the Python3 standard library, and features several unit tests and an end-to-end test bash script whereas the Perl version had only a single unit test (executed at run time on every run).
To be clear, though, it - like the Perl script it is intended to replace - has dependencies on external programs including wget, openssl and psql. wget is only needed for Maxmind download support, so it could possibly be removed as the hard-coded URLs don't work anyway, but is left in for consistency with the old script. Besides that, its only external dependencies are already dependencies of TO - even the Go version - and the Python3 interpreter itself.
Finally, I should mention that this doesn't actually replace the old script, which is totally untouched, but provides the new Python script as an alternative. Many machines running TO in the wild may not have Python3 installed yet, so it may be too soon yet to require that for TO installations/upgrades.

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?
To run the doctests, use python -m doctest path/to/postinstall.py.
To run the end-to-end tests, use the postinstall.test.sh script, which should also output nothing (except spitting out some ssl keys/certs/requests in the current directory) and exit successfully.
The following criteria are ALL met by this PR

[x] This PR includes tests
[x] Documentation is unnecessary - this isn't actually used yet. It does have docstrings and a -h/--help option, though
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Python 2.7 is supported by Red Hat through June 2024. Although we definitely don't need to support Python 2.7 just for this script to exist in the repo, there would be a much stronger case for this Python script to replace the Perl one if it could be run using both Python 2.7 and 3.6.

But ATC as a project doesn't support Python2.7 as of 4.0.0

But ATC as a project doesn't support Python2.7 as of 4.0.0

Not trying to convince you, just describing the conditions under which it
could replace the Perl postinstall.
On Tue, Nov 10, 2020 at 12:42 PM ocket8888<EMAIL_ADDRESS>wrote:

Python 2.7 is supported by Red Hat through June 2024. Although we
definitely don't need to support Python 2.7 just for this script to exist
in the repo, there would be a much stronger case for this Python script to
replace the Perl one if it could be run using both Python 2.7 and 3.6.
But ATC as a project doesn't support Python2.7 as of 4.0.0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/trafficcontrol/pull/4763#issuecomment-724924255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVFRL2UTPLRQYKUSYTHNLTSPGJRPANCNFSM4NX4BGAA
.

Everything looks good so far, just need to test

I think that's because the Perl script will silently fail to apply database configuration if no database is present, which is why the Python script now comes with a command-line option to skip database operations. Silent failures are a bug, IMO.

I think that's because the Perl script will silently fail to apply database configuration if no database is present, which is why the Python script now comes with a command-line option to skip database operations. Silent failures are a bug, IMO.

But there is a database present, and the Perl script does succeed. Pushed 337785b0f0 to the postinstall-python-centos8 branch, so now trafficops-perl initializes the database using the Perl _postinstall so you can observe it succeeding.

Looks like the error stems from my use of capture_output, which was added in Python 3.7. Currently the oldest minor release still receiving security fixes is 3.6 - and that's what's in the CentOS8 /usr/libexec/ - so we should definitely still support it. Fixed.
Also added support for a Python interpreter at /usr/libexec/platform-python - but not Python 2 support. Python 2 is dead and I'm no necromancer. If it would help adoption I would not be in any way opposed to making the script support Python 2 until CentOS 7's end-of-life either after this is merged or through a PR directly to my branch before it's merged, but it's work I don't want to do. I like my type hints, and part of the point of doing this rewrite was to eliminate dependencies outside of the standard library which supporting the two cleanly might require (like future or six) .


Implementation details about consistency loss

Hi @SeanChenxy ,
For the implementation of consistency loss, I come up two different approaches but don't know which one is the right one used in the paper, could you give some hints on this? Thanks.
First approach
Use the (image, vertex) from one camera, and then randomly generate a custom T to create paired (image, vertex) as inputs for consistency loss
Second approach
Use two images at the same time from different camera in dataset (e.g., camera 1 and camera 2 in FreiHAND),  as the input of consistency loss, i.e., no need to generate novel camera, just use already existing ones

Hi, we use the first approach. (ps. the code of this part will be released before the conference.)


fix: https://cert-manager.io/v1.12-docs doesn't work

I forgot to change the manifest.json when releasing v1.12. The command is:
sed -i.bak 's|/docs/|/v1.12-docs/|g' content/v1.12-docs/manifest.json

I also edited the release process document to reflect that in #1229.

The preview build failure looks legitimate!

Relates to #1243


Maya collect render fails when no render products are generated

Bug
collect_render collector plugin in Maya will fail very ungracefully when conditions are so no render products are generated - for example frame range is set so, and so on. It should check if they are generated and if not then fail with specific error message. Currently the traceback doesn't say anything useful as it crashes on completely unrelated part of code.
[cuID:]

Could you post the traceback/error that is seemingly unrelated?
Are you seeing this No render cameras found.? Did you test with this fix implemented?

Or did you get this error:
Message:
expected str, bytes or os.PathLike object, not NoneType
Traceback (most recent call last):
  File "S:\openpype\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "S:\openpype\OpenPype\openpype\hosts\maya\plugins\publish\collect_render.py", line 279, in process
  File "C:/Program Files/Autodesk/Maya2022\Python37\lib\ntpath.py", line 452, in normpath
    path = os.fspath(path)
TypeError: expected str, bytes or os.PathLike object, not NoneType

I'm getting that when setting end frame to 1000 and start frame too 1001 (so start frame is lower than end frame, and thus NO frames are rendered).

it fails sometimes before but the reason is probably the same:
Traceback (most recent call last):
  File "C:\Program Files (x86)\OpenPype\dependencies\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "C:\Users\foo\AppData\Local\pypeclub\openpype\openpype-v3.9.5\openpype\hosts\maya\plugins\publish\collect_render.py", line 276, in process
  File "C:\Program Files\Autodesk\Maya2020\bin\python27.zip\ntpath.py", line 419, in normpath
    if path.startswith(('\\\\.\\', '\\\\?\\')):
AttributeError: 'NoneType' object has no attribute 'startswith'


feat(windows): Adds demo containers based on Windows

Adds the makefile definitions and the checks to build Windows based
demo containers on the CI.
Fixes #3880
Signed-off-by: Sotiris Nanopoulos<EMAIL_ADDRESS>

Lets see what the CI things of the change first

Codecov Report

Merging #3921 (d125989) into main (43d7278) will decrease coverage by 0.09%.
The diff coverage is 79.06%.

@@            Coverage Diff             @@
##             main    #3921      +/-   ##
==========================================
- Coverage   67.48%   67.38%   -0.10%
==========================================
  Files         204      203       -1
  Lines       11523    11485      -38
==========================================
- Hits         7776     7739      -37
+ Misses       3696     3695       -1
  Partials       51       51

Flag
Coverage Δ

unittests
67.38% <79.06%> (-0.10%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cmd/osm-controller/osm-controller.go
13.66% <ø> (+0.33%)
:arrow_up:

...certificate/providers/vault/certificate_manager.go
62.72% <0.00%> (ø)

pkg/debugger/debugger_config_listener.go
0.00% <0.00%> (ø)

pkg/envoy/ads/cache_stream.go
27.45% <0.00%> (ø)

pkg/envoy/ads/stream.go
10.71% <0.00%> (ø)

pkg/metricsstore/metricsstore.go
100.00% <ø> (ø)

pkg/catalog/dispatcher.go
36.66% <33.33%> (ø)

pkg/configurator/client.go
84.80% <80.00%> (ø)

pkg/ticker/ticker.go
90.00% <85.71%> (ø)

cmd/osm-controller/log_handler.go
79.31% <100.00%> (ø)

... and 9 more

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 d796f9a...d125989. Read the comment docs.

Updating to non-draft as the validation locally passes:
davinci@MININT-9CEC7NF:~/osm$ curl -X GET http://localhost:5000/v2/_catalog
{"repositories":["bookbuyer","bookbuyer-windows","bookstore","bookstore-windows","bookthief","bookthief-windows","bookwarehouse","bookwarehouse-windows","init","init-osm-controller","my-ubuntu","osm-controller","osm-crd-converter","osm-crds","osm-injector","tcp-client","tcp-client-windows","tcp-echo-server","tcp-echo-server-windows"]}

@nojnhuh do you want to take this review since you are involved with the docker images?

Currently blocked as the Windows insider images that we need to use cannot be built with docker buildx. This PR should be good to go when non-insider versions of Windows server become available

@nojnhuh the container image went out of public preview so we should be able to do merge it now.
davinci@MININT-9CEC7NF:~/osm$ make docker-build-windows-bookbuyer
make OS=windows build-bookbuyer
make[1]: Entering directory '/home/davinci/osm'
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 go build -o ./demo/bin/bookbuyer/bookbuyer.exe ./demo/cmd/bookbuyer
make[1]: Leaving directory '/home/davinci/osm'
docker buildx build --platform "windows/amd64" -t osmwindevregistry.azurecr.io/bookbuyer-windows:latest  -f dockerfiles/Dockerfile.bookbuyer.windows demo/bin/bookbuyer
WARN[0000] No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
[+] Building 11.8s (7/7) FINISHED
 => [internal] booting buildkit                                                                                2.7s
 => => starting container buildx_buildkit_img-builder0                                                                                2.7s
 => [internal] load build definition from Dockerfile.bookbuyer.windows                                                                                0.1s
 => => transferring dockerfile: 201B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/nanoserver:ltsc2022                                                                                1.1s
 => [internal] load build context                                                                                0.5s
 => => transferring context: 24.44MB                                                                                0.5s
 => [1/2] FROM mcr.microsoft.com/windows/nanoserver:ltsc2022@sha256:3df3372895223b44475125ab3553fd39a71d89a896099d463d3216f1e22a3ab0                                                                           6.9s
 => => resolve mcr.microsoft.com/windows/nanoserver:ltsc2022@sha256:3df3372895223b44475125ab3553fd39a71d89a896099d463d3216f1e22a3ab0                                                                           0.0s
 => => sha256:ee7a9c9193e3d9bee1b6c8ddddddd5356aed50f77c78d18d377241f4aee6d676 117.98MB / 117.98MB                                                                                4.5s
 => => extracting sha256:ee7a9c9193e3d9bee1b6c8ddddddd5356aed50f77c78d18d377241f4aee6d676                                                                                2.3s
 => [2/2] COPY bookbuyer.exe bookbuyer.html.template /

LGTM, but I tried it out on my Mac but I get an "operating system is not supported" error which seems to agree with the output I get for docker buildx ls:
% docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS
desktop-linux   docker
  desktop-linux desktop-linux   running linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
default *       docker
  default       default         running linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6

I wonder if the GitHub actions runners would hit the same error. I don't think any of the CI jobs try to build the Windows images currently. Or do you know if we were going to have Windows CI machines build the images so this probably wouldn't matter?

At @davinci26's suggestion, running docker buildx create --name img-builder --use before  building any of the images fixed this issue for me.

@shashankram should we merge this one?


Installing sqlite3 ir better-sqlite3 fails

Installing this dependency fails with something along these lines.  I have tried multiple workarounds with customPatchPackages and patchPackages with no luck. I am also having no luck with alternatives like npmlock2nix or nix-npm-buildpackage.  Anyone has success with these?
npm info run<EMAIL_ADDRESS>install node_modules/better-sqlite3 prebuild-install || node-gyp rebuild --release
npm info run<EMAIL_ADDRESS>install { code: 1, signal: null }nst
npm timing reify:rollback:createSparse Completed in<EMAIL_ADDRESS>inst
npm timing reify:rollback:retireShallow Completed in 0ms
npm timing command:install Completed in 1104ms
npm verb stack Error: command failed
npm verb stack     at ChildProcess.<anonymous> (/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
npm verb stack     at ChildProcess.emit (node:events:527:28)
npm verb stack     at maybeClose (node:internal/child_process:1092:16)
npm verb stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /build/server
npm verb Linux 6.1.34
npm verb argv "/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/bin/node" "/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/bin/npm" "install" "--loglevel" "verbose" "--nodedir=/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/include/node"
npm verb node v16.15.0
npm verb npm  v8.5.5
npm ERR! code 1
npm ERR! path /build/server/node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c prebuild-install || node-gyp rebuild --release
npm ERR! sh: /build/server/node_modules/.bin/prebuild-install: /usr/bin/env: bad interpreter: No such file or directory
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli   '/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/bin/node',
npm ERR! gyp verb cli   '/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli   'rebuild',
npm ERR! gyp verb cli   '--release'
npm ERR! gyp verb cli ]
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| linux | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb find Python Python is not set from command line or npm configuration
npm ERR! gyp verb find Python Python is not set from environment variable PYTHON
npm ERR! gyp verb find Python checking if "python3" can be used
npm ERR! gyp verb find Python - executing "python3" to get executable path
npm ERR! gyp verb find Python - "python3" is not in PATH or produced an error
npm ERR! gyp verb find Python checking if "python" can be used
npm ERR! gyp verb find Python - executing "python" to get executable path
npm ERR! gyp verb find Python - "python" is not in PATH or produced an error
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration
npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
npm ERR! gyp ERR! find Python checking if "python3" can be used
npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error
npm ERR! gyp ERR! find Python checking if "python" can be used
npm ERR! gyp ERR! find Python - "python" is not in PATH or produced an error
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python You need to install the latest version of Python.
npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
npm ERR! gyp ERR! find Python you can try one of the following options:
npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python   (accepted by both node-gyp and npm)
npm ERR! gyp ERR! find Python - Set the environment variable PYTHON
npm ERR! gyp ERR! find Python - Set the npm configuration variable python:
npm ERR! gyp ERR! find Python   npm config set python "/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python For more information consult the documentation at:
npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
npm ERR! gyp ERR! stack     at PythonFinder.fail (/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)
npm ERR! gyp ERR! stack     at PythonFinder.runChecks (/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)
npm ERR! gyp ERR! stack     at PythonFinder.<anonymous> (/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:202:16)
npm ERR! gyp ERR! stack     at PythonFinder.execFileCallback (/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:294:16)
npm ERR! gyp ERR! stack     at exithandler (node:child_process:406:5)
npm ERR! gyp ERR! stack     at ChildProcess.errorhandler (node:child_process:418:5)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
npm ERR! gyp ERR! stack     at onErrorNT (node:internal/child_process:478:16)
npm ERR! gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:83:21)
npm ERR! gyp ERR! System Linux 6.1.34
npm ERR! gyp ERR! command "/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/bin/node" "/nix/store/6g5y6hq3npg9gy04q4ya1xzz9nj0bh59-nodejs-16.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
npm ERR! gyp ERR! cwd /build/server/node_modules/better-sqlite3
npm ERR! gyp ERR! node -v v16.15.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm verb exit 1
npm timing npm Completed in 1223ms
npm verb unfinished npm timer reify<PHONE_NUMBER>617
npm verb unfinished npm timer reify:build<PHONE_NUMBER>602
npm verb unfinished npm timer build<PHONE_NUMBER>603
npm verb unfinished npm timer build:deps<PHONE_NUMBER>603
npm verb unfinished npm timer build:run:install<PHONE_NUMBER>606
npm verb unfinished npm timer build:run:install:node_modules/better-sqlite3<PHONE_NUMBER>606
npm verb code 1

npm ERR! A complete log of this run can be found in:
npm ERR!     /build/tmp.nRE4fM60rN/.npm/_logs/2023-12-12T16_45_06_500Z-debug-0.log

error: builder for '/nix/store/wphiq151fwzf09b2n75nh2rrbcn01dxb-server-0.0.0.drv' failed with exit code 1;
       last 10 log lines:
       > npm verb unfinished npm timer reify:build<PHONE_NUMBER>602
       > npm verb unfinished npm timer build<PHONE_NUMBER>603
       > npm verb unfinished npm timer build:deps<PHONE_NUMBER>603
       > npm verb unfinished npm timer build:run:install<PHONE_NUMBER>606
       > npm verb unfinished npm timer build:run:install:node_modules/better-sqlite3<PHONE_NUMBER>606
       > npm verb code 1
       >
       > npm ERR! A complete log of this run can be found in:
       > npm ERR!     /build/tmp.nRE4fM60rN/.npm/_logs/2023-12-12T16_45_06_500Z-debug-0.log
       >
       For full logs, run 'nix log /nix/store/wphiq151fwzf09b2n75nh2rrbcn01dxb-server-0.0.0.drv'.
error: build of '/nix/store/gjiifk5hh2q9xg7gjl0nrfw7vl2qvzvr-client-0.1.0.drv', '/nix/store/wphiq151fwzf09b2n75nh2rrbcn01dxb-server-0.0.0.drv' failed

For node-gyp, you need to pass the following to napalm.buildPackage:
  nativeBuildInputs = [
    # For node-gyp
    pkgs.python3
  ];


Allow snabbnfv to pass all traffic on an Ethernet port to a single virtual machine

The port configuration for snabbnfv requires a valid mac_address, which is used to correctly place incoming packets to a virtual queue. I'm in need of having all traffic on a given Ethernet port reaching a single virtual machine, e.g. a virtual router, in order to support all kinds of protocols (pppoe, mpls, etc).
This patch checks if a mac_address is set in the port definition of the config file and sets vmdq to false if its omitted and to true (matching the original behavior) if a mac_address is set.
The following port definition will accept all packets from the wire and pass it to the virtual machine:
# cat xe0.cfg
return {
  {
    port_id = "xe0",
  }
}

Does this make sense beyond my very specific application that I have in mind, which basically turns an Ethernet port into trunk mode into a single virtual machine?
Ideally I'd like to be able to cover not only the use case to treat a port as a trunk interface, but also cover use cases where one can serve multiple virtual machines by using the vlan tag only instead of mac_address plus vlan_id.

This seems like a valuable feature to me. Likewise pure VLAN dispatch.
I wonder whether we should restrict snabbnfv config to only having one port in this setup? If we support multiple ports with a mix of VMDq/non-VMDq then we would have to document how this is expected to behave and keep that consistent across current/future NICs that we support. Could be simpler at least immediately to report an error if this feature is used in a config file that contains multiple ports.
Side-thought: Looking ahead I think it is likely that we will end up replacing VMDq with a software solution instead. The hardware offloads always seem to become limiting and fragile at a certain point. Based on experiments with #603 I am even becoming hopeful that we could write a software traffic dispatcher for 100G ethernet ports. However, VMDq is the solution we have today and it does work fine up to this point.

As a barely-related side-thought: one thing I'd like to do in the near future is the split-app driver we've talked some time ago: one app to configure the NIC, and one or more extra apps pushing packets in and out of the chip's rings.
This would allow different CPU cores to handle different packet streams, not only for VMDq, but also for RSS.  The nice thing is that it wouldn't require any communication between those processes, removing many obvious scalability limits.  100G could be doable with current JIT schemes.

@javierguerragiraldez I am experimenting with the "split driver" approach on #561 (Intel I350/1G) now. I will resubmit that when the design is more mature. Meanwhile I added some comments this morning to explain the design a bit. Basic concept is to move decisions from happening automatically inside the app (e.g. assignment of TX/RX queues) to being explicitly configured in the app network. So when you create an intel1g app you tell it which TX queue to use (if any) and which RX queue to use (if any) and whether to initialize the NIC (or assume that somebody else does this). It seems promising to me and it should make basic I/O orthogonal to queue setup (VMDq / RSS / etc) as you say. If this design makes sense we could even add 82599 support to that driver?
The downside though of hardware offloads like VMDq and RSS is that they are not universal. Marcel mentions being interested in more exotic protocols and we can't really depend on commodity NICs to handle dispatching on PPPoE, MPLS, GTP, and so on. So I like the idea of making the hardware capabilities available, and for some applications they will be exactly the right thing, but I am anticipating that people will prefer well-optimized and flexible software dispatching in the future. Juho Snellman made a similar remark in a great recent presentation: Mobile TCP Optimization - lessons learned in production. The product that Juho is describing is actually an ancestor of Snabb Switch: I worked on that with Juho immediately before starting Snabb Switch and that was the first time we ditched vendor libraries and wrote our own drivers.

Closing because this was merged together with #618.


Provide a meaningful error when the view server fails to connect to the downstream server

I found this testing Glossary author, if the view server does not find the downstream server, then I would want to see some error relating to Not connected - similar to if the view server was not contactable.
The scope of this change is to change the view sever and ensure that the glossary author displays the appropriate error in this case.

I believe should be the view service's reponsibility to handle this case - not the view server?


Rewrite UI using react.

Take a look, hope this is helpful. I'm attached to nothing here so feel no remorse with comments.

I'm cleaning up old PRs and don't think I'm going to go this direction any time soon. Thanks for the experiment! 👋


Added IDENA project

Feel free to rearrange. I just added it to the top since the list is not alphabetical.

It should be added at the bottom, but otherwise thanks for the contribution!

It should be added at the bottom, but otherwise thanks for the contribution!


chapter-2: typo in the "io writer usage" test

The code in the io writer usage test adds an extra empty argument to the writer function.  zig fmt should remove the extra , after the last argument, but currently it formats the code as:
write(
        "Hello World!",
);

Thanks.

Sorry; I learned that this is the intended behavior of zig fmt.


How to define  & ?

pose &  truncated are needed for yolo, but i can't find how to define them in labelimg.
anyidea or any other tools? thx.

truncated is true if object is at the limits of the image [Code in libs/pascal_voc_io.py]
truncated = SubElement(object_item, 'truncated')
if int(each_object['ymax']) == int(self.imgSize[0]) or (int(each_object['ymin'])== 1):
    truncated.text = "1" # max == height or min
elif (int(each_object['xmax'])==int(self.imgSize[1])) or (int(each_object['xmin'])== 1):
    truncated.text = "1" # max == width or min
else:
    truncated.text = "0"

A truncated button might be defined the same way as the difficult button.


Update error message to indicate exact file missing

Fixes https://github.com/fastlane/ci/issues/996

Actually no, gonna update this

Ready to be reviewed & merged from my side 👍

@AndrewMcBurney why? I thought that not having this file will allow the CI to run just fine, right? It's not actually required to get the server running and use fastlane.ci. From what I understand, the list should contain the files that are absolutely necessary to get the CI running. Once a user edits one ENV variable through the UI the file will automatically be created

@AndrewMcBurney I totally misunderstood how we used that list of files. I just synced with @KrauseFx and it makes sense to keep this file out of that list.
I thought that this list was also used to generate the files, I didn't realize we generate this file only when needed.
So, in this case, we can leave it out of the CONFIGURATION_FILES list. Sorry for any confusion I caused here!

And to complete the context, here's where we create the file for the user: https://github.com/fastlane/ci/blob/be64b5a12ac22f73c4a6ccf855aca2f3fbb19e23/app/services/configuration_repository_service.rb#L127


Trim pathing error

Hi Hernan!
Unfortunately another trim path issue :( Maybe even multiple!
Attached is the zip with including the bodymovin export ;)
Hopefully its fixable
Trim paths - animatie .zip

Hi Tom, I took a look at your test project (just out of curiosity) and I get an error--and it may be just me, but I thought I'd share it anyway if it could be of some help:

SCRIPT5007: Unable to get property 'effect' of undefined or null reference
eval code (8) (2,1)

When I inspect the eval code, I see this, with the error indicator pointing to line 2:
var fn = function(){var $bm_rt; $bm_rt = comp('Kleuren').layer('Hoofdkleur').effect('Fill')('ADBE Fill-0002');;this.v = $bm_rt;}

Hi jeremy!
We have used an expression so you have to include an extra comp with
bodymovin, you can click on the cog wheel to enable extra comps and select
the 'kleuren' comp. ( forgot to translate the comps, sorry!)
Op do 19 jan. 2017 18:56 schreef Jeremy Knudsen<EMAIL_ADDRESS>
Hi Tom, I took a look at your test project (just out of curiosity) and I
get an error--and it may be just me, but I thought I'd share it anyway if
it could be of some help:
SCRIPT5007: Unable to get property 'effect' of undefined or null reference
eval code (8) (2,1)
When I inspect the eval code, I see this, with the error indicator
pointing to line 2:
var fn = function(){var $bm_rt; $bm_rt =
comp('Kleuren').layer('Hoofdkleur').effect('Fill')('ADBE
Fill-0002');;this.v = $bm_rt;}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bodymovin/bodymovin/issues/222#issuecomment-273848987,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABP1yjAH-qTI-lKvx6NJztpO3F626aJ6ks5rT6O_gaJpZM4LoEdX
.

I think this time it's not a trim path issue, but an effect issue.
Because of the way that browsers handle filters (that is used in this case to apply the fill effect of AE), strokes are not correctly measured and they end up cropped.
If you add a transparent rectangle as part of each layer with strokes that cover the whole surface the stroke animates, browsers use the rectangle as measurement and strokes with effects don't get cropped.
I'm attaching the project as an example. Check the comp "Order_her".
Animatie 3.zip

Any chance the workaround of adding a transparent rectangle could be done automatically by the Bodymovin extension when rendered?

Good idea :)
I'll think about it.


Faculty list

Alphabetize (?Randomize) faculty names in the “browse all faculty” page

Alphabetize by last name.

Make the faculty who is logged in first on the list in the "browse all faculty" view

Jane, I made this a separate issue just to clarify work flows.

This has been implemented in 6ee79a7

I'm noticing that Dean Saldana's profile is at the top, and not listed alphabetically like all the other faculty profiles.

There are two faculty names at the top that are not alphabetized.

There was a space after those 2 faculty names, which was confusing the sorting. I made it so that trailing spaces are now removed and updated the 2 existing ones directly in the database.

This looks great, thanks!
On Fri, Nov 16, 2018 at 12:22 AM Razzi Abuissa<EMAIL_ADDRESS>wrote:

Everything should work now. MD and other suffixes after a comma also now
do not affect alphabetization.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/razzius/hms-weave/issues/3#issuecomment-439317037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApxaURV4Y4eYiAovBWqJaPrxscBlzo0Oks5uvnXfgaJpZM4XFMIr
.


CLN: less reckless update, consistent leading v

If 23.02.2 or lower was the CLN version run before update, update only to the recommended version.
Fixes previous workarounds for the inconsistency in the leading v in version numbers.
Context: CLN v23.05 breaks RTL:

We have to update cl-rest and RTL's code to accommodate cln's msat purge. You can follow these issues here https://github.com/Ride-The-Lightning/c-lightning-REST/issues/168 & https://github.com/Ride-The-Lightning/RTL/issues/1231

Needs testing.

We dont have much time for testing left - is this PR a go for v1.9.0?

First test worked:
a node running v23.05 got updated to v23.05. Could be improved with not needing to install the 23.02.2 beforehand as compiling on the Rpi takes ages,

Second install test went ok and kept the fatpack version v23.02.2.