How to Implement TV-like Screen Switching Without Interrupting Existing Clients

I currently have a requirement to cyclically push the footage from two cameras to a streamID according to a schedule, such as automatically switching to another camera every few minutes. However, when switching the camera feed, I don't want to disconnect the existing clients. I hope the clients can switch the footage smoothly, just like how we watch TV broadcasts switch scenes. How can I achieve this?
publish:
  live:

streams:
  live:
  video1:ffmpeg:./demo.mp4
  audio2:ffmpeg:./demo1.mp4

Frigate project has feature named Birdseye https://docs.frigate.video/configuration/birdseye
They manually push frames from different cameras to this stream via ffmpeg.
You can't do this in general and easiest way because every stream can has different codec, resolution, encoding params, etc.

Please forgive my foolish actions; I realized this after posting the issue. Indeed, closing the client connection and reconnecting would be friendlier. However, is it possible to actively close the client connection after pushing a new stream or calling the API in a PATCH manner, rather than waiting for the client to disconnect on its own? This way, the client’s display can switch automatically.

I reviewed previous issues again, and my requirement matches this one. #869


Controller settings crashes the game while Widescreen is enabled.

When entering the controller settings menu while widescreen is enabled, the game will crash.

It may have something to do with one of the text ingame functions.
While debugging on Cheat Engine, I've gotten these crash dump results that leads to the game's code:
EDX: 00718D42
EIP: 0058E292
I have no idea why it's crashing, I'll have to look more into it.

Looks like it's crashing in double __thiscall ScreenTextFont::GetWidth(unsigned short*)... Just a wild shot in the dark, perhaps it's related to Xbox buttons potentially being treated as special characters?

That could be the case.
I dunno if the 360 version has a controller settings menu but if it doesn't then, I guess it explains why the game is crashing on this.

Forgot to mention this, but m_tempUTF16Buffer leads to the EDX, and since it leads to a buffer size, is it hitting a limit or something? (could be wrong here)


onNavigationStateChange isn't triggered for pushstate or #!

This can be duplicated in the UIExplorer example. Go to https://medium.com/ and click on an article — the url stays the same.
Any known workarounds?

@robertgonzales Is this on Android or iOS?

iOS

I think this issue is missing enough information - in particular a link to the example code that does not work. Also do medium links actually change the url? I'm going to close this issue but feel free to reopen if you have a link to for example a rnplay.org code sample reproducing the problem.


Comments rejection after engagement is closed

Issue #: https://github.com/bcgov/epic-engage/issues/17
Description of changes:

Backend changes to add new email template
Changed the logic to pick existing rejection email template while engagement is open and the new one when engagement is closed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #35 (d441b1b) into main (e17746e) will decrease coverage by 0.01%.
The diff coverage is 72.72%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
- Coverage   68.45%   68.44%   -0.01%
==========================================
  Files         472      472
  Lines       15620    15625       +5
  Branches     1194     1194
==========================================
+ Hits        10693    10695       +2
- Misses       4718     4721       +3
  Partials      209      209

Flag
Coverage Δ

metapi
76.50% <72.72%> (-0.03%)
:arrow_down:

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

Files
Coverage Δ

met-api/src/met_api/config.py
96.77% <ø> (ø)

met-api/src/met_api/services/submission_service.py
74.71% <72.72%> (-0.67%)
:arrow_down:


STP-3736: Update SAT 2.6 versions for release

Summary and Scope
Our references to components in version 2.6 are out of date, so I updated them for the upcoming release.
Issues and Related PRs

Resolves STP-3736

Testing
Lint and spell check
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

@haasken-hpe, I'm not sure if you still want me to make these changes to master since the product is moving to CSM.


FORTECH-115: Fix not to change Popup's title position when closeButton is visible

fixed the change of position for Popup title when the closeButton is visible
Enact-DCO-1.0-Signed-off-by: Daniel Stoian<EMAIL_ADDRESS>

If adding a long title text, the text is below the close button. Could you fix it together with proper paddings?

If adding a long title text, the text is below the close button. Could you fix it together with proper paddings?

Thanks for the notice. I added the fixes

Thanks for the notice. I added the fixes

I verified it. Thanks.


event: Google messing with The Federalist's and ZeroHedge's ad accounts

The original NBC disaster piece (archived of course)
The Federalist (2)
ZeroHedge
National Review
Tim Pool commentary
Google's statement (tweet) correcting NBC on the Federalist's standing

https://www.zerohedge.com/political/doj-goes-after-googles-comment-section-trump-admin-propose-section-230-rollback

Styx

https://www.zerohedge.com/markets/status-update

Sargon commentary

This is position we're in: you have a publisher who can't act as a platform for comments, but a platform can act as a publisher and direct the publishers to censor those things that they themselves are not going to become responsible for.


ci: build and deploy with GitHub Actions

related to INFRA-1265

Travis builds fail - should we be bothered?

Travis builds fail - should we be bothered?

Travis also fails on master. It looks like it can't install the requested environment because it's outdated.

Hi @malteser and @jangalinski (tagging you as the main contributors): as you can see, we're moving from building the community projects on GitHub actions instead of "our" Jenkins.
We made this move to improve transparency as well as provide better feedback for contributors.
I'm going to leave this note in all affected repositories once we're done making the changes.
If you experience issues related to our changes to GitHub Actions, please let us know!


JSON get's converted to Base64

When sending the record template
{
	"sensorId": 40,
	"currentTemperature": 76,
	"status": "OK"
}

the payload delivered to Kinesis is Base64 encoded.
{
    "kinesis": {
        "kinesisSchemaVersion": "1.0",
        "partitionKey": "2264290559",
        "sequenceNumber": "49583841783469136626947675794180856103183100390328500226",
        "data": "ewkic2Vuc29ySWQiOiA0MCwJImN1cnJlbnRUZW1wZXJhdHVyZSI6IDc2LAkic3RhdHVzIjogIk9LIn0K",
        "approximateArrivalTimestamp":<PHONE_NUMBER>.471
    },
    "eventSource": "aws:kinesis",
    "eventVersion": "1.0",
    "eventID": "shardId-000000000000:49583841783469136626947675794180856103183100390328500226",
    "eventName": "aws:kinesis:record",
    "invokeIdentityArn": "arn:aws:iam::294557341534:role/lambda_firehoseTranformer",
    "awsRegion": "eu-central-1",
    "eventSourceARN": "arn:aws:kinesis:eu-central-1:294557341534:stream/test"
}

Is this expected behavior? If yes, please update the documentation. Using the sample test events and documentation for AWS Kinesis/Firehose and the AWS Kinesis-Lambda-Templates this does not work without a conversion back to JSON.

This is expected behavior.  The AWS SDK for JavaScript (used in this project) automatically base64-encodes the data before it sends it to Kinesis Data Streams or Kinesis Data Firehose.  The API documentation for Kinesis Data Streams mentions that input data should be base64-encoded:  https://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html
Data consumers need to base64 decode the data to obtain the original record.  This is mentioned in the example in this documentation:  https://docs.aws.amazon.com/streams/latest/dev/fundamental-stream.html


Cannot read property 'on' of undefined

Getting this error since the latest update, in two different homes, on startup.

Also: it reports '0 accessories' and just deleted my motion sensor..

Powering off the Bridge does not give any errors in the Homebridge window.

Did you specify the bridge as host In config.json?  Does it still have the same IP address?
Could you please list the output of homebridge -D?

@ebaauw I did, and it still has. Output:
[2017-4-18 15:22:14] [Hue] <IP_ADDRESS>: hue bridge request #1: ok
[2017-4-18 15:22:14] [Hue] Cannot read property 'on' of undefined
[2017-4-18 15:22:14] [Hue] Bridge Joost: 0 accessories

Please list the full debug output, incl. version numbers, requests, etc.

Whoops sorry @ebaauw:
Here's everything:
[2017-4-18 15:22:13] Loaded plugin: homebridge-dummy
[2017-4-18 15:22:13] Registering accessory 'homebridge-dummy.DummySwitch'
[2017-4-18 15:22:13] ---
[2017-4-18 15:22:13] Loaded plugin: homebridge-hue
[2017-4-18 15:22:13] Registering platform 'homebridge-hue.Hue'
[2017-4-18 15:22:13] ---
[2017-4-18 15:22:13] Loaded plugin: homebridge-itunes
[2017-4-18 15:22:13] Registering platform 'homebridge-itunes.iTunes'
[2017-4-18 15:22:13] ---
[2017-4-18 15:22:14] Loaded plugin: homebridge-people
[2017-4-18 15:22:14] Registering platform 'homebridge-people.People'
[2017-4-18 15:22:14] Registering accessory 'homebridge-people.PeopleAccessory'
[2017-4-18 15:22:14] Registering accessory 'homebridge-people.PeopleAllAccessory'
[2017-4-18 15:22:14] ---
[2017-4-18 15:22:14] Loaded config.json with 1 accessories and 3 platforms.
[2017-4-18 15:22:14] ---
[2017-4-18 15:22:14] Loading 3 platforms...
[2017-4-18 15:22:14] [Hue] Initializing Hue platform...
[2017-4-18 15:22:14] [Hue] homebridge-hue v0.3.15, node v7.7.4, homebridge api v2.2
[2017-4-18 15:22:14] [Hue] <IP_ADDRESS>: hue bridge request #1: get /config
[2017-4-18 15:22:14] Initializing People platform...
[2017-4-18 15:22:14] Initializing platform accessory 'Joost'...
[2017-4-18 15:22:14] Initializing platform accessory 'Kiki'...
[2017-4-18 15:22:14] Initializing platform accessory 'Anyone'...
[2017-4-18 15:22:14] Initializing platform accessory 'No One'...
[2017-4-18 15:22:14] WebHook: Started server on port '51828'.
[2017-4-18 15:22:14] Initializing iTunes platform...
[2017-4-18 15:22:14] Loading 1 accessories...
[2017-4-18 15:22:14] [Server Switch] Initializing DummySwitch accessory...
[2017-4-18 15:22:14] [Hue] <IP_ADDRESS>: hue bridge request #1: ok
[2017-4-18 15:22:14] [Hue] Cannot read property 'on' of undefined
[2017-4-18 15:22:14] [Hue] Bridge Joost: 0 accessories
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

[2017-4-18 15:22:14] Homebridge is running on port 51826.

Thanks, @jojost1.
That narrows down where the Cannot read property 'on' of undefined error message comes from, but, frankly, I have no clue what's causing it.  I didn't change that part of the code in v0.3.15.  What version where you on before the update?

Also: it reports '0 accessories' and just deleted my motion sensor..
Powering off the Bridge does not give any errors in the Homebridge window.

These are consequences of the first error.
My best guess is a somehow corrupted installation.  Some longshots:

Did you update homebridge-hue through npm?  Could you retry

sudo npm -g install homebridge-hue

Did you update homebridge to v0.4.19?
Does homebridge-hue report the same error when it's the only plugin enabled in config.json?
Is there a reason why you run node v7.7.4?  Could you try node v.6.10.2?

Thanks for the quick response!

What version where you on before the update?

v0.3.14 if I'm correct.

Did you update homebridge-hue through npm? Could you retry...

Did that and tried it again, didn't help :(

Did you update homebridge to v0.4.19?

I did, before updating homebridge-hue.

Does homebridge-hue report the same error when it's the only plugin enabled in config.json?

Bit difficult to test right now. I have to say I did notice the same exact error in my other home, but there I still had my dimmer switch & tap in HomeKit.
Similarities between both setups: I was setting up homebridge-iTunes, which works. Might be that, but that's pretty weird if the case. Maybe you could test it?

Is there a reason why you run node v7.7.4? Could you try node v.6.10.2?

No specific reason. How to 'downgrade' to stable? Can try that.
Thanks!

v0.3.14 if I'm correct.

And re-installing v0.3.14 gets rid of the error?

I have to say I did notice the same exact error in my other home

"Other home" as in another Hue bridge, another installation of homebridge on a another machine?

but there I still had my dimmer switch & tap in HomeKit.

That would be because you killed homebridge in time?  If it's the same error, homebridge would run without homebridge-hue exposing anything, causing HomeKit to delete the accessories.

And re-installing v0.3.14 gets rid of the error?

Nope, it looks like I get the error with v0.3.14/15/17.

I have to say I did notice the same exact error in my other home
"Other home" as in another Hue bridge, another installation of homebridge on a another machine?

Yes, another Bridge, another installation of homebridge, on a completely different Mac. Only common denominator I think is the installation of homebridge-iTunes I was messing around with. Homebridge-hue works on the other Mac right now, but that might be because I deleted homebridge-iTunes there.. I think it is likely that plugin causes problems, is that possible?

That would be because you killed homebridge in time? If it's the same error, homebridge would run without homebridge-hue exposing anything, causing HomeKit to delete the accessories.

See above, I think the plugin exposed the accessories after uninstalling homebridge-iTunes and I don't think I get the error right now, sorry I'm unclear ;) Thanks.

but that might be because I deleted homebridge-iTunes there.. I think it is likely that plugin causes problems, is that possible?

Sadly, yes.  They override Characteristic.prototype.updateValue(), which is scary at best.  To make it worse, they break it by failing to return the characteristic for chaining.  homebridge-hue tries to register an event handler on the return value of updateValue(), which now is undefined and no longer contains a property (method) on.


GTM avoid bad regeneration

Please review @juanignaciosl

This is an interesting scenario for a test, could you do one before CR-ing this, please?

We've already talked offline about this scenario. This fix somehow gives more priority to a user table with matching oid over a user table with matching name, which seems to make sense, I can't think on any scenario where this change makes matching worse. 👍 after the test.


Add annotation NonNull/Nullable for better usage in kotlin (also java)

This is a small improvement but still nice to have for all classes/interface that are public API.
Spring did changes to allow better interoperability with kotlin null checks.
As an example, default generation of methods to overload via Intellij Idea creates:
class MyOwnAssociationResolver : AssociationResolver {
    override fun <T : Any?> validate(associationPropertyName: String?, handler: MessageHandlingMember<T>?) {
        TODO("not implemented")
    }

    override fun <T : Any?> resolve(associationPropertyName: String?, message: EventMessage<*>?, handler: MessageHandlingMember<T>?): Any {
        TODO("not implemented")
    }
}

If annotation are used we should be able to get automatic generation with:
class MyOwnAssociationResolver : AssociationResolver {
    override fun <T : Any> validate(associationPropertyName: String, handler: MessageHandlingMember<T>) {
        TODO("not implemented")
    }

    override fun <T : Any> resolve(associationPropertyName: String, message: EventMessage<*>, handler: MessageHandlingMember<T>): Any {
        TODO("not implemented")
    }
}

We've been discussing this internally as a logical requirement from the perspective of the Kotlin Extension. We will rather introduce a package level default of Non Null, as that's what the majority of the builder assertions are leaning towards any how.
Regardless, we didn't come around to drafting up an actual issue for it, so thanks for doing so @Blackdread.

@smcvb I've been looking into this. It would require a package-info.java file in every package we want the non-null default. It would look like this:
@NonNullApi
package org.axonframework.spring.config;

import org.springframework.lang.NonNullApi;

Note that it is a Spring framework annotation. It is part of the spring-core dependency. For us to be able to use it on all our configuration classes and extendable classes would mean including spring as a dependency

Hmm, I assumed there'd also be a non-Spring variant of this, honestly.
We can't enforce a Spring dependency on all the modules (or, I don't think that's a good idea).
You're certain there's no other means to get a non-null annotation (to for example more cleanly support Kotlin)?

I looked into it some more, the following options are available:
JetBrains (@Nullable and @NotNull from the org.jetbrains.annotations package)
JSpecify (org.jspecify.nullness)
Android (com.android.annotations and android.support.annotations)
JSR-305 (javax.annotation, more details below)
FindBugs (edu.umd.cs.findbugs.annotations)
Eclipse (org.eclipse.jdt.annotation)
Lombok (lombok.NonNull)
RxJava 3 (io.reactivex.rxjava3.annotations)
All these are supported by Kotlin. I'd suggest using JSR-305, since this has the TypeQualifierDefault annotation which can be used on packages

Sweet, thanks for the investigation there, @Morlack.
I agree, the JSR-305 option seems most applicable for our use case.
I'd say we give it a try!


[Question] Wrong .dll name when building hashlink?

Is vcruntime.dll.dll correct lib name ?
https://github.com/openfl/lime/blob/f8a70444f5d8a6bd3208e2e28b53e57568ba2eee/src/lime/tools/HashlinkHelper.hx#L47
I see in hashlink dir only vcruntime140.dll file.

@Apprentice-Alchemist, do you know if this is a typo or a real file?

I also checked hashlink repo, it only mentions vcruntime140.dll

It's probably a typo.


[WFCORE-1274] CLI resolve-parameter-values set to true does not recognize vaulted strings

Jira: https://issues.jboss.org/browse/WFCORE-1274
The format of security vault: ${VAULT::xxx::yyy::zzz} is like system property: ${propName:defaultValue}. I prefer to let user send escaped string: $\{VAULT::xxx::yyy::zzz\}, instead of let CLI distinguish the input for this special case.

@aloubyansky please approve

Not ok. First of all this change makes a decision to return too early. If the line in the added test was e.g. "the value is ${VAULT::text::password::1} ${os.name}" then ${os.name} wouldn't be resolved.
Second, there is actually a way to escape expressions like that by adding the extra '$' in front. (I copied this from some other expression parser David wrote for DMR or something). That's not very obvious but I remember it was a better idea than messing with backslash escaping in a case like this one.

@aloubyansky there is actually a way to escape expressions like that by adding the extra '$' in front" Since there is an existing way to escape the expression, this should NOT be a problem then, I tested that user can use $${VAULT::text::password::1} to escape the expression, which gets the expected: ${VAULT::text::password::1} in standalone.xml

Close it as it should not be a problem.


Azure Cosmos Latency Issue

We are running an IoT architecture where multiple devices (e.g 200) hit IoT every 10 seconds. We have subscribed event hub at our one microservice and it pushed data to Azure cosmos db (Mongo).
We are facing massive latency like 2 hours. We are using Azure Serverless Cosmos. Can you help me understand what could be the possible issue.

@omersalam
Thank you for bringing this to our attention.
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!

@omersalam Thank you for bringing this to our attention. It would be great if you could add a link to the documentation you are following for these steps. This would help us redirect the issue to the appropriate team. Thanks!

There is no specific documentation. We are using Azure Cosmos with mongo API to store IoT device's data. We are using event hubs. But when a lot of device data is triggered we see a huge latency at Cosmos.
The following links were shared with us. But not solved our problems
https://azure.microsoft.com/en-us/blog/build-apps-of-any-size-or-scale-with-azure-cosmos-db/
https://learn.microsoft.com/en-us/azure/cosmos-db/throughput-serverless#detailed-comparison

Also, we applied indexes. We are using it and we feel RU consumption is changing. But in graph, we see Index usage zero.

@omersalam,
Thanks for your comment.
Your contribution is much appreciated.
However, our team can only answer feedback related to the documentation. Please kindly log your product feedback by using the button "Give Product Feedback" at the bottom of the DOCS page or visit the feedback site. If you have any feedback related to the documentation, please feel free to log in through this channel. We truly appreciate your contribution to our articles.
Hope this helps.
Thank you.
#please-close


Google Cloud Functions

Can Tegola be run as a Google Cloud Function? Does anyone have experience deploying Tegola in this way?

@digitaltopo not yet, though a shim could be developed much like we did for AWS Lambda. Would you be interested in working on this?

@digitaltopo Have you considered Google Cloud Run?  It's basically like Cloud Functions but runs any docker container as a function.  I haven't used it with Tegola but I have deployed my GIS REST API to it and it worked flawlessly.

@digitaltopo I can confirm it works on Google Cloud Run.  I'll put up a repo when I can sanitize my config file, but I basically created a new git repo with my config.toml and a Dockerfile like below
FROM gospatial/tegola:latest
COPY config.toml /opt/tegola_config/config.toml
ENTRYPOINT ["/opt/tegola", "serve", "--config=/opt/tegola_config/config.toml"]

and then created a trigger in Google Cloud Builder to create a docker container from the Dockerfile.  Then I went into Cloud Run and created a new service using the built container and added some ENV variables.  All I did in my TOML was make everything a env variable (this was all using the console.cloud.google.com GUI).
[webserver]
port = ":${PORT}"

# register data providers
[[providers]]
name = "mypostgis"           # provider name is referenced from map layers
type = "postgis"        # the type of data provider. currently only supports postgis
host = "${PG_HOST}"      # postgis database host
port = "${PG_PORT}"          # postgis database port
database = "${PG_DB}"       # postgis database name
user = "${PG_USER}"         # postgis database user
password = "${PG_PASSWORD}"           # postgis database password
srid = "${SRID}"

I also create a cloudbuilder.yaml to auto deploy a new Cloud Run instance whenever a new container is built in Cloud Builder.  So basically I can just push an updated config to github and it will auto deploy that.  It's pretty slick to be honest.  I haven't tested it too thoroughly but tweaking the RAM limit and concurrent connections in Cloud Run seems like all that would be required to have an "infinitely scaling" tegola setup (at least until you run into PostGRES limits).


Bart as single-library + introducing Python module library pyBART v2

New take on #131 but separating the changes in multiple commits for easier review.

Excellent. Thank you! I will slowly add some comments.

I have pushed some changes addressing some of the comments.
Regarding the indentation issues with the second commit, these only occur because the indentation is correct for the final state after the last commit.
In order to split the changes into multiple commits, I simply selectively committed chunks of changes together (ie. without properly re-indenting the changes).

I will start cherry-picking and revising some individual commits. I you want, you can rebase. But if it is too much trouble, don't worry you can also just continue to work on your branch and leave the merging to me.

Ok, so I've rebased it and addressed the debug_level issue inside the BART main function.

I just did a new rebase to take the latest commits on the master branch into account.

I've rebased the remaining changes onto the current master and removed the fcopy commit from the changes.

Okay, I merged most of it in some way. Thank you for your work!
For the in memory function I used a different solution. Let' me no whether this works for you.
I also edited the python module without testing, I hope nothing broke...
Finally, I lost the CMake integration testing a while ago (April 29 "update compiler on travis"). As you know CMake much better than me: If you have time, I would appreciate if you could help restore this...

I will take a look at the CMake integration testing over the next few weeks.

Thank you! We had it already, so maybe only a minor change is needed to make it work again.


List is Flickkering/lagging when scrolling

Hi!
I am experiencing some problem when i scroll through my list.
Also notice the huge space at the bottom.
See video : https://vimeo.com/215349521
As far as i can see, im not making any huge mistakes.
But i do belive the problem is due to the CellMeasurer.
Chrome version: 58.0.3029.81
class PromotionList extends Component {

constructor(props) {
    super(props);

    this.cache = new CellMeasurerCache({
        defaultHeight: 100,
        fixedWidth: true,
    });

    this.rowRenderer = this.rowRenderer.bind(this);
}

componentWillMount() {
    this.props.fetchPromotionsIfNeeded();
}

rowRenderer({ index, parent }) {
    const { promotions } = this.props;
    const data = promotions.list[index];

    return (
      <CellMeasurer
        cache={this.cache}
        columnIndex={0}
        key={uuid.v1()}
        parent={parent}
        rowIndex={index}
      >
        <BlobItem
          key={uuid.v1()}
          type={BlobTypes.promotion}
          data={data}
          onClick={this.props.onItemClick}
          index={index}
        />
      </CellMeasurer>
    );
}

render() {
    const { promotions, previewSize } = this.props;

    return (
      <List
        height={300}
        width={previewSize.width}
        rowCount={promotions.list.length}
        deferredMeasurementCache={this.cache}
        rowHeight={this.cache.rowHeight}
        rowRenderer={this.rowRenderer}
        className="blobList"
      />
    );
}
}

Hi!
This type of question should probably be asked in the Slack or Stack Overflow channel rather than as a GitHub issue. Issues are for bugs and feature requests only. Troubleshooting things like this are easier to handle in the #general Slack channel where there are more people and easier back and forth communication.

ever found a solution to your problem? I'm having the same issue, empty space at the bottom and weird flickering

@pablote
Yes I solved this, but forgot to put it up here.
I did answer it in stackoverflow:
https://stackoverflow.com/questions/43700938/react-virtualized-list-is-flickkering-lagging-when-scrolling/43710140#43710140


Translate  Header

By merging this PR, and #36 #37 #38 the Home page become entirely translated  🎉

thanks for the review @asantarissy  👍


PDF generation

I know the first request already got closed, but a gentle reminder that having these Keyboard shortcuts in a handy small PDF format would be nice, instead of getting whole PDF of docs.
But the PDF generation does not render the Mac chars correctly... something about character encoding I guess!
For example:
Next Issue in File	⌥⇟
Renders like so in the PDF:
Next Issue in File        []⇟

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

ID: a2a1d38f-f2fc-3fe6-bfb4-b73b7f4a56bc
Version Independent ID: 90b1f5ca-71dd-2c14-8023-c3f238fc2686
Content: Default Keyboard Shortcuts in Visual Studio for Mac - Visual Studio 2019 for Mac
Content Source: mac/keyboard-shortcuts.md
Product: visual-studio-mac
Technology: vs-ide-general
GitHub Login: @BytesGuy
Microsoft Alias: adhartle

Hi @Depechie we're actively working with the design team on making this available in a nice, easy to reference format. Hopefully we'll have something for you soon!

I no longer work on this product, hopefully this is something @heiligerdankgesang can address!

We added a pdf download of keyboard shortcuts to this documentation page.

@TerryGLee I don't have permissions to close this. Can you please help us get this closed, thanks?

Closing per request. Thanks all for helping to improve our documentation!


chore: stucturing

Figure out how to structure repository efficiently to build multiple separate example configs. One way could be to have multiple workflow files, one for each example. The updating of these would be handled by Dependabot anyway. Ideally the examples could be used to copy-paste from. Maybe symlinking the build.yml from each example to the root of the main repository could work?

Basically done now. The idea is that examples not requiring a custom build.yml will use build-simple.yml. Each example will have its workflow file symlinked to be next to all the other config. This structure requires https://github.com/blue-build/github-action/pull/43


Added login routes 🐾 🚀 ,Initiated cookie management 💯

Changes to the login and register routes,,,
Buttons working correctly and routing respectively cept for read more and bit of register page.


[SMALLFIX] Update Fingerprint.java

Add @Nullable annotation if the method may return null in /alluxio/core/common/src/main/java/alluxio/underfs/Fingerprint.java

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2895/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2896/
Test PASSed.

@MhDang the @Nullable change looks good. Can you revert the changes to npm-shrinkwrap.json?

@aaudiber Hi, thanks for your advice. The changes in npm-shrinkwrap.json are due to I run "mvn clean install -DskipTests" in my local machine, and I get SUCCESS. If I revert the changes to npm-shrinkwarp.json, I will get "Merged build finished. Test FAILed." You can see my first commit.

@MhDang The failing test looks unrelated to npm. Can you try again without the shrinkwrap changes?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2920/
Test PASSed.

@aaudiber Hello, it works this time. Thanks a lot for your guidance.

alluxio-bot, merge this please


07/18/2018 02:22 : Create Pull Request for branch master -> prTesting1_2018071802

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


chore(master): Release 0.13.1

:robot: I have created a release beep boop
aztec-packages: 0.13.1
0.13.1 (2023-10-31)
Bug Fixes

Exposing PXE.getBlock, exporting createAztecNodeClient from aztec.js (#3139) (7af345e)
Revert push cli docker image to docker hub (#3142) (7119382)

barretenberg.js: 0.13.1
0.13.1 (2023-10-31)
Miscellaneous

barretenberg.js: Synchronize aztec-packages versions

barretenberg: 0.13.1
0.13.1 (2023-10-31)
Miscellaneous

barretenberg: Synchronize aztec-packages versions

This PR was generated with Release Please. See documentation.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit db67aa1e and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,972
867,800
3,449,528

l1_rollup_execution_gas
842,059
3,594,908
22,204,897

l2_block_processing_time_in_ms
1,993 (-1%)
7,509 (-1%)
29,620 (-1%)

note_successful_decrypting_time_in_ms
291 (+1%)
855
3,127 (-3%)

note_trial_decrypting_time_in_ms
92.0 (-1%)
64.0 (+5%)
135 (-1%)

l2_block_building_time_in_ms
13,157
52,269
208,532

l2_block_rollup_simulation_time_in_ms
11,846
47,049
187,634

l2_block_public_tx_process_time_in_ms
1,270
5,091
20,408 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,444 (-1%)
42,322

note_history_successful_decrypting_time_in_ms
2,000 (-2%)
3,946 (-1%)

note_history_trial_decrypting_time_in_ms
122 (+1%)
145 (-22%)

node_database_size_in_bytes
1,626,956
1,094,154

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
72.3
61,697
18,841

private-kernel-ordering
43.3
24,233
8,089

base-rollup
1,769
656,309
811

root-rollup
77.3
4,072
1,097

private-kernel-inner
53.0 (-1%)
81,504
18,841

public-kernel-private-input
41.5
41,455
18,841

public-kernel-non-first-iteration
26.4
41,497
18,841

merge-rollup
0.935 (+3%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,723
27,240

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/aztec-packages-v0.13.1 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/barretenberg.js-v0.13.1 :sunflower:

:robot: Release is at https://github.com/AztecProtocol/aztec-packages/releases/tag/barretenberg-v0.13.1 :sunflower:


Errors from Istiod result in increasing Envoy request size, eventually exceeding limit

In a broken cluster state where istiod is returning errors, we accumulate a fixed ~10kb to the request message size on each error. We need to figure out why.
This is reported by 2 users on 1.9 in GKE

https://github.com/envoyproxy/envoy/issues/15838

Fixed in 1.10.0 and 1.9.x with e6f334e45c


Issue template for the website repo

We might benefit from an issue template on the website repo.  We can make a callout that this is not where folks file bugs for Ghostty and redirect them to the CONTRIBUTING.md document.

#192


posix: add argument to change the CWD

#9046
Because the paths/files generated by px4 depend on the location of the current working directory, simply changing it allows us to avoid conflicts with launching multiple instances.

launching one vehicle with mavros_posix_sitl.launch

launching three vehicles with multi_uav_mavros_sitl.launch

@bkueng I made the changes you requested.

Hey @lamping7 so I've tested your changes and I don't know if it's because something I'm doing but when I push 3 different missions to the uav's via mavros they say that they received the waypoint. Now the problem is that they don't use these waypoints they only use the height I've set for the rest they just fly a square and all land on top of each other.

Can you share more info? Was one of the missions a square? I can't tell what you did there.

Hey so the problem was that my coordinates where being rounded of so they ended up at almost the same location. I have tested it again and it's working correctly.


api: Add missing annotations to generate DeepCopy for new status fields

The referenced commits below did not add the annotations required to generate
the DeepCopy() code. Add the annotations and autogenerate the code.
Fixes: b2271f74c0f ("api: Extend proxy redirect status")
Fixes: 06add2d8ba7 ("api: Add KubeProxyReplacement field to StatusResponse")

This change is

test-me-please

Coverage decreased (-0.005%) to 44.543% when pulling de67a5dfe6cb9441ccd752d9e52ecdbbd3e96a97 on pr/tgraf/add-missing-annotations into da2e6526b8da79ce8948399fca23691ef0b62be2 on master.

test-me-please


Fix each* methods to return a receiver itself

All each and methods like each should return a receiver itself. For example, current Deque#each returns Range?, it looks like a bug. (But each_cons and some Enumerable methods return nil same as Ruby)

Thank you!
We copied Ruby here when we made each return self. However, now I'm more inclined to make them return nil. I never understood why it's useful to return self. But I'd like others' opinion here :-)

@asterite I asked it to matz in twitter, and answered now. https://twitter.com/yukihiro_matz/status/815905904084197376
Matz says "To return self by Array#each and some methods is not big meaning. But it is better than to return nil."

@asterite My question: To return self, does it have effects for optimization? And if returning nil, does it have no effect?

Yes, of course :-)
If a method returns nil then for code generation it returns void in LLVM. Then if you have a method like:
def foo
  some_array.each do
  end
end

then foo now returns the array, but if each returns nil then foo will return nil. This can also prevent some union types.
But this is not the point. I never understood why each (or p, or puts) return something other than nil. This is kind of ugly:
obj.each do
  # ...
end.do_something_else

so maybe I'd like to remove that anti-feature from the standard library.

I think we can remove it. It's not such a big deal.

Closed in favor of #3826


Update scalafmt-core, scalafmt-dynamic to 3.7.10

About this PR
📦 Updates

org.scalameta:scalafmt-core
org.scalameta:scalafmt-dynamic

from 3.7.2 to 3.7.10
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #104.


Index user specific cast data

Index number of cast
Index cast activity

Resolved by https://github.com/shrimalmadhur/trendcaster/commit/97535369043bdf8c7fcf4bed39d36b7b716b6f7d


Conflict leftover in component file TheComponentTreeContainer.vue

Just a friendly reminder about unmerged conflict in
https://github.com/oslabs-beta/vuety/blob/b2d1a332e1bc67623e0eacfb6cfe6a585d6f04fa/src/components/componentTree/TheComponentTreeContainer.vue#L23-L28

Thank you for bringing up this issue. It has now been rectified.


Add relay proxy to tests, docs, fix offline

Adds documentation, test for Relay proxy class
Fix offline mode for proxy
Forward login packet in proxy

Ready for review


future is timeout but socket has not timeout

hello：
future is timeout but socket has not timeout
The connection pool will not be exhausted？
thanks

@johnyannj I will take a look, if you have bandwidth, a PR is welcome.


feat: crash screen

Checklist

[x] JIRA - <LW-11945>
[ ] Proper tests implemented
[x] Screenshots added.

Proposed solution
Add crash screen
Screenshots
https://github.com/user-attachments/assets/69275203-21d0-4720-88a9-2c40150f4f67
https://github.com/user-attachments/assets/7a1ba24a-6601-4f33-aa4a-1eb84d4158f7
https://github.com/user-attachments/assets/ea4bfd00-7487-4ee9-8c39-1ecba15c38fb
https://github.com/user-attachments/assets/f8d15988-4cbd-4277-bd72-b3461857a1a6

Allure Report
allure-report-publisher generated test report!

processReports: ❌ test report for 20e57a08

passed
failed
skipped
flaky
total
result

Total
32
1
4
0
37
❌

Is the reload icon present when not in developer mode?

Yes, it works the same


Pub get socket error trying to find package angular at https://pub.dartlang.org

I'm using dart 1.24.3 and I'm trying to resolve dependencies for the first time (angular package) I was trying out the example code (tour of hero) but I can't seem to get past this error message "got socket error trying to find package angular at https://pub.dartlang.org" I'm new to dart so I don't know what really is the problem... my internet connection does not have proxy settings
Operating system : windows 10
Dart SDK: 1.24.3

I think this was a transient error with the pub server. We now have more retries in the pub client as well.


Client call hangs when returning a Stream object

Describe the bug
If an interface definition contains a method returning Stream, then calling this method hangs indefinitely.
Interface example:
public interface IComputingService
{
    float AddFloat(float x, float y);
    Stream GetMemoryStream();
}

I suppose that streams are not supported yet but it is not stated implicitly so I am creating a bug report.
To Reproduce
Steps to reproduce the behavior:

Clone the .NET Core console application.
Compile and run IpcServiceFrameworkTest project.
The application hangs waiting for Stream response.

Expected behavior
No hanging. If streams are not supported then an exception with an appropriate error message should be raised.

I realized that exception is not caught properly, that's why it hangs. Anyway, error message is confusing (NullReferenceException) so that I propose to propagate such kind of errors from server to client (see https://github.com/jacqueskang/IpcServiceFramework/pull/52).


Support Quarkus

[Question]
Can someone list what exactly needs to be done to support Quarkus?
I might be able to work on that.
Thanks in advance

Hi @sherviiin,
Thanks a lot for your interest!
The idea here is that we could run a Quarkus application with Stove; essentially, it is as simple as adding a SystemUnderTest.
If you look at how Ktor is implemented, it will give an idea.
Steps: Writing a SystemUnderTest

Create a folder named quarkus under starters under it stove-quarkus-testing-e2e folder.
Add this into settings.gradle.kts to include the build
Create a code structure similar to the ktor implementation
Implement the functionality
Create an example Quarkus application and write tests under the examples folder. (don't forget to add it to settings.gradle.kts for build purposes). Example project should be similar to what we have in Spring:

HTTP endpoints for a basic Product manipulation
Database interaction, Couchbase/Mongo/RDBS (Stove supported ones)

[Optional] Adding stove-quarkus-testing-e2e into the list of publishedProjects in build.gradle.kts

Kafka Integration (optional)
I am unfamiliar with the Quarkus framework, but it would be more appreciated if we could intercept Kafka messages and write assertions for Quarkus. Spring provides consumer and producer interceptors so we can understand the messages and write assertions for them. If Quarkus has a Kafka integration, we could also create a Kafka integration package like stove-spring-testing-e2e-kafka, and it would be stove-quarkus-testing-e2e-kafka.
But the overall idea is just being able to start the process, meaning writing a system under test.
Please let me know if that is enough information to proceed, and don't hesitate to ask any questions!

If anyone is interested can continue from where I left, my quarkus knowledge is limited, for now, I've created a spike here: https://github.com/Trendyol/stove/pull/625


Add hubot-adapter topic

The list of hubot adapters in the hubot documentation is being replaced with a link to a GitHub topic search. Add the hubot-adapter topic to your repository on GitHub to include it in this list.
/cc https://github.com/github/hubot/pull/1320

@bkeepers thanks for the heads-up!  I've added the topic to the repo and now shows up in the topic search :+1:


update to new event api

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

LGTM


Upgrade to Rails 5

I only had to fix one test which was stubbing the render method (more info in the commit message).
It seemed to be a little invasive anyway so I wasn't too worried.  I'm not sure anything else is particularly contentious.
https://trello.com/c/koLLxmdS/83-upgrade-calendars-to-rails-5
Paired with @deborahchua

No probs, thanks for the review 👍


update code to work with new version of Selenium

Update the code to work with the latest version of Selenium

Replace deprecated find_elements_by_class_name
Replace deprecated ChromeOptions

@CatchZeng PTAL


Simplify JDBC service customization

I understand that it is difficult (impossible?) to come provide implementations that work out of the box with all DBs but it would be helpful if the default implementations were simpler to customize.
For example, I'm finding that customizing JdbcOAuth2AuthorizationService to handle mariadb to be somewhat cumbersome.
The mariadb jdbc driver, for some reason that is not entirely clear to me, sets the BLOB column type to LONGVARBINARY which JdbcOAuth2AuthorizationService does not handle.  It seemed that the simplest way to deal with this was to override a method and map LONGVARBINARY to BLOB so that the rest of the code could handle it without further changes.
That is simple enough with JdbcOAuth2AuthorizationService.OAuth2AuthorizationParametersMapper#apply with something like:
@Override
apply(OAuth2Authorization authorization) {
  return super.apply(authorization).stream.map(v -> {
	if(v.getSqlType() == Types.LONGVARBINARY && v.getValue() != null) {
		return new SqlParameterValue(Types.BLOB, ((String)v.getValue()).getBytes(StandardCharsets.UTF_8));
	}
	return v;
}).collect(Collectors.toList());

A similar operation would be required for JdbcOAuth2AuthorizationService#findBy but that method is private so it's not possible to override and overriding the findBy methods that call findBy is not feasible because those method rely heavily on private static members.
The only option that I had, short of completely writing my own implementation, was to make a copy JdbcOAuth2AuthorizationService and make one simple change:
private static SqlParameterValue mapToSqlParameter(String columnName, String value) {
	ColumnMetadata columnMetadata = columnMetadataMap.get(columnName);
	return (Types.BLOB == columnMetadata.getDataType() || Types.LONGVARBINARY == columnMetadata.getDataType()) && StringUtils.hasText(value) ?
			new SqlParameterValue(Types.BLOB, value.getBytes(StandardCharsets.UTF_8)) :
			new SqlParameterValue(columnMetadata.getDataType(), value);
}

To my mind, a wholesale copy of a class just to make such a simple change is a bit of overkill.

@dciarniello This appears to be a duplicate of gh-774.
Please see this comment as it explains how you can completely override the default schema.

I don't think this is a duplicate of #550. In that ticket the suggestion is to customize the implementation using a custom OAuth2AuthorizationParametersMapper specific to the database in use. That however does not allow to customize all of the database specific code.
The problem is that JdbcOAuth2AuthorizationService uses some database-specific code internally that is not customizable because it's private and/or static.
Ideally the implementation should be as generic as possible and should allow database-specific adaptations to be made without having to duplicate the whole class.


Minor fix to ensure positional variable isn't overwritten

The $3 variable can be overwritten in ::Sass::_checksum SEARCH loop.
Resulting error messages become without the filename.
This change stores it in a local variable.

Awesome! 👍


Add chunked processing back into v2 client

Moving the to v2 client removed this functionality. This copies
code back into the client. The tests were also added back into
the test suite.

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

Fixes #7977

Can you rebase this and then I'll merge it?

Done. Thanks.

The build error looks unrelated to I'm going to merge this.


How to use kalidoface 3d

Hello, I want to run your repo https://github.com/yeemachine/kalidoface-3d. Are there any tutorials about how to run it?

That repo can be run using a local server like http-server. It's a static site


Support for SKLearn KNN

Please add support for KNN within SKLearn.

I hear you are working on this @scnakandala? let me know if that's not the case :)

Yes, @ksaur. I am exploring what we can do to support it. Can you assign this to me?


[WFCORE-6706] Upgrading JBoss MSC to 1.5.3.Final

https://issues.redhat.com/browse/WFCORE-6706

Thanks @ropalka


[CLI]: openai wandb sync exception

Describe the bug
After running openai wandb sync in the terminal as per documentation, this happens. I have the latest versions of openai and wandb. Seems somewhat similar to this issue, tried WANDB_START_METHOD="thread" but it didn't work.

openai wandb sync
wandb: Currently logged in as: sidyakinian (use `wandb login --relogin` to force relogin)
wandb: Tracking run with wandb version 0.12.15
wandb: Run data is saved locally in /Users/sidyakinian/wandb/run-20220428_164026-ft-jdOTgW5l5kZZ8zwfz7CQlC52
wandb: Run `wandb offline` to turn off syncing.
wandb: Syncing run ft-jdOTgW5l5kZZ8zwfz7CQlC52
wandb: ⭐ View project at https://wandb.ai/sidyakinian/GPT-3
wandb: 🚀 View run at https://wandb.ai/sidyakinian/GPT-3/runs/ft-jdOTgW5l5kZZ8zwfz7CQlC52
Exception in thread ChkStopThr:
Traceback (most recent call last):
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Exception in thread NetStatThr:
Traceback (most recent call last):
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/threading.py", line 892, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 152, in check_network_status
    self.run()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/threading.py", line 892, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 170, in check_status
    status_response = self._interface.communicate_network_status()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface.py", line 125, in communicate_network_status
    resp = self._communicate_network_status(status)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 405, in _communicate_network_status
    status_response = self._interface.communicate_stop_status()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface.py", line 114, in communicate_stop_status
    resp = self._communicate(req, local=True)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 226, in _communicate
    return self._communicate_async(rec, local=local).get(timeout=timeout)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 231, in _communicate_async
    resp = self._communicate_stop_status(status)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 395, in _communicate_stop_status
    raise Exception("The wandb backend process has shutdown")
Exception: The wandb backend process has shutdown
    resp = self._communicate(req, local=True)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 226, in _communicate
    return self._communicate_async(rec, local=local).get(timeout=timeout)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 231, in _communicate_async
    raise Exception("The wandb backend process has shutdown")
Exception: The wandb backend process has shutdown
Problem at: /Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/wandb_logger.py 149 _log_fine_tune
Traceback (most recent call last):
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 995, in init
    run = wi.init()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 683, in init
    run._on_start()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 1946, in _on_start
    self._on_ready()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 1961, in _on_ready
    self._telemetry_flush()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 583, in _telemetry_flush
    self._backend.interface._publish_telemetry(self._telemetry_obj)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 74, in _publish_telemetry
    self._publish(rec)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_queue.py", line 49, in _publish
    raise Exception("The wandb backend process has shutdown")
Exception: The wandb backend process has shutdown
wandb: ERROR Abnormal program exit
Traceback (most recent call last):
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 995, in init
    run = wi.init()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 683, in init
    run._on_start()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 1946, in _on_start
    self._on_ready()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 1961, in _on_ready
    self._telemetry_flush()
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_run.py", line 583, in _telemetry_flush
    self._backend.interface._publish_telemetry(self._telemetry_obj)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_shared.py", line 74, in _publish_telemetry
    self._publish(rec)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/interface/interface_queue.py", line 49, in _publish
    raise Exception("The wandb backend process has shutdown")
Exception: The wandb backend process has shutdown

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/sidyakinian/opt/miniconda3/bin/openai", line 8, in <module>
    sys.exit(main())
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/_openai_scripts.py", line 63, in main
    args.func(args)
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/cli.py", line 543, in sync
    resp = openai.wandb_logger.WandbLogger.sync(
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/wandb_logger.py", line 74, in sync
    fine_tune_logged = [
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/wandb_logger.py", line 75, in <listcomp>
    cls._log_fine_tune(
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/openai/wandb_logger.py", line 149, in _log_fine_tune
    wandb.init(
  File "/Users/sidyakinian/opt/miniconda3/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 1033, in init
    raise Exception("problem") from error_seen
Exception: problem
/Users/sidyakinian/opt/miniconda3/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 6 leaked semaphore objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '

Environment
WandB version: 0.12.15
OS: macOS 12.0 Monterey
Python version: python --version 3.9.5

Hi @sidyakinian, do you have any issues running a basic run of W&B or is the issue isolated to the Open AI integration?
For example do you see this when running the following script:
import wandb
run = wandb.init()
run.log({"metric":1})
run.finish()

@nate-wandb Yes, I see the same issue!

Downgrading conda python to 3.7.10 solved the issue.


Get the Internet Gateway attached to the VPC from AWS as a data source

What

Get the Internet Gateway attached to the VPC from AWS

Why

Since only one Internet Gateway could be attached to a VPC (and we suppose it's already attached since we use its ID), we can get its ID from AWS instead of manually defining it in variables.tf

References

https://www.terraform.io/docs/providers/aws/d/internet_gateway.html
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInternetGateways.html

LGTM, but please apply terraform fmt.
Otherwise we would need to manually refactor the formatting each time.

Applied terraform fmt


Implement all available components

[ ] Batch thinking
[x] Button
[x] Card
[ ] Layout w.i.p. in branch feature/Layout
[ ] ...

fyi: I just hacked together a http://www.getmdl.io/components/index.html component scraper, that may help me auto-generate component files:
https://gist.github.com/nikvm/e3abd7dfc8bbe9d9c073
If all goes well this will speed up the process.

Claim a Component now! And I will add it to the list.


[6.8] [meta] add helm 3.6.2 support (#1232)

Backports the following commits to 6.8:

[meta] add helm 3.6.2 support (#1232)

jenkins test this please


refactor(instr-fetch): move fetch to use SEMATRR

Which problem is this PR solving?
Updates https://github.com/open-telemetry/opentelemetry-js/issues/4567
Short description of the changes

Updates deprecated SemanticAttributes in experimental package instrumentation-fetch

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

[x] npm test

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[x] Documentation has been updated

Hi @mmouru
thanks for contributing into our effort to update semantic conventions. 🎉
Would you please complete this PR by adding a section in the README file listing the attributes used in this instrumentation?
You can have a look at intrumentation-http README

Thank you @mmouru for your contribution :)
Would you please add a section in the README file listing the attributes used in this instrumentation? Here is an example (you can omit the 3rd column) https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-instrumentation-http#semantic-conventions

done my bits

Oh. @mmouru I've just realized you haven't signed the CLA. Can you please take care of that so we can move forward with this PR?

Oh. @mmouru I've just realized you haven't signed the CLA. Can you please take care of that so we can move forward with this PR?

🤔  Looks like you've contributed before; there was a problem for a short time with EasyCLA, try adding a comment that says /easycla and that might fix it.

/easycla

I'm not sure why the rest of the status checks / tests are not showing up right now 🤔

I'm not sure why the rest of the status checks / tests are not showing up right now 🤔

Conflict in the CHANGELOG file. I'm not sure if that is what blocks running the other checks.

Conflict in the CHANGELOG file. I'm not sure if that is what blocks running the other checks.

Ah looks like you're right. For some reason I was thinking that wouldn't block tests. I've just pushed up a merge and update to remove the conflict and the rest of the checks are running now.


Dazel: dart_vm_binary rule 'dazel' in package '' conflicts with existing dart_library rule

This is tested on the web_application sample that is checked into the tests directory, tested it on two operating systems. Centos7 and Opensuse, same exact error. Opensuse was a 100% clean install, so I doubt that this is somehow my fault.
errors.txt
The errors seem to be referencing this file:
BAZEL.txt

somebody made this issue in the correct place instead


[sail] fix layout in vcpkg include tree

Is your feature request related to a problem? Please describe.
the primary header expects to be
#include <sail/sail.h>
but vcpkg creates it as
#include <sail/sail/sail.h>
... which causes failure to load the content of sail.h:
#include <sail-common/sail-common.h>
#include <sail/codec_bundle.h>
#include <sail/codec_bundle_node.h>
#include <sail/codec_info.h>
#include <sail/codec_priority.h>
#include <sail/context.h>
#include <sail/io_file.h>
#include <sail/io_memory.h>
#include <sail/io_noop.h>
#include <sail/sail_advanced.h>
#include <sail/sail_deep_diver.h>
#include <sail/sail_junior.h>
#include <sail/sail_technical_diver.h>
Proposed solution
the most sustainable solution would be to add sail's headers in the expected places
Describe alternatives you've considered
it would also be possible to modify the headers when building the sail package, but that probably requires more work and produces a result inconsistent with the library's documentation
Additional context
No response

@ghesketh, Thanks for posting this issue, After I installed sail:x64-windows locally, I created a simple cmake project and could successfully include the following content
#include <sail/codec_bundle.h>
#include <sail/codec_bundle_node.h>
#include <sail/codec_info.h>
#include <sail/codec_priority.h>
#include <sail/context.h>
#include <sail/io_file.h>
#include <sail/io_memory.h>
#include <sail/io_noop.h>
#include <sail/sail_advanced.h>
#include <sail/sail_deep_diver.h>
#include <sail/sail_junior.h>
#include <sail/sail_technical_diver.h>

May I ask if there is something wrong with my understanding?

@ghesketh, Thanks for posting this issue, After I installed sail:x64-windows locally, I created a simple cmake project and could successfully include the following content
#include <sail/codec_bundle.h>
#include <sail/codec_bundle_node.h>
#include <sail/codec_info.h>
#include <sail/codec_priority.h>
#include <sail/context.h>
#include <sail/io_file.h>
#include <sail/io_memory.h>
#include <sail/io_noop.h>
#include <sail/sail_advanced.h>
#include <sail/sail_deep_diver.h>
#include <sail/sail_junior.h>
#include <sail/sail_technical_diver.h>

May I ask if there is something wrong with my understanding?

Thank you for the reply!
I have an existing Visual Studio (msbuild) project, and after I installed sail, Visual Studio did not see sail's headers because their locations in the include tree were not correct.
-- Gifford

I also created a C++ project and can still find it automatically using msbuild mode.

I also created a C++ project and can still find it automatically using msbuild mode.

No? You cannot, according to the screenshot: You end with sail/sail/... but official usage is sail/....

OK, I will Ok, I have modified the label, I will try to fix this issue.

It should be noted that vcpkg can only find header files in the include folder by default. In order to prevent conflicts, vcpkg adds a layer of directory xxx and installs some libraries in the include\xxx folder. At this time, you need to manually add include\ xxx to the msbuild project.

I am not sure I understand your comment.  Sail only expects to find its headers below the include directory.  It does have multiple folders (sail, sail-common, sail-manip) that it expects there, but there are other packages (ffmpeg, fast_io, etc.) that install multiple directories as include\xxx, so equivalent behavior between CMake and msbuild seems not to be difficult.


Dockerfile.gpu does not build, errors out installing torch

Running on a Macbook M1 -- does that matter?
Prior to this error, when setting up the build env when I run:
pip3 install torch==1.13.1+cu117 -f https://download.pytorch.org/whl/torch
I get:
Looking in links: https://download.pytorch.org/whl/torch
ERROR: Could not find a version that satisfies the requirement torch==1.13.1+cu117 (from versions: 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2)
ERROR: No matching distribution found for torch==1.13.1+cu117

Similarly, when running docker build for the GPU, the following error is obtained:
 => ERROR [stage-2 15/15] RUN /app/.venv/bin/pip install torch==1.13.1+cu117 -f https://download.pytorch.org/whl/torch                                                                      1.1s
------
 > [stage-2 15/15] RUN /app/.venv/bin/pip install torch==1.13.1+cu117 -f https://download.pytorch.org/whl/torch:
0.306 Looking in links: https://download.pytorch.org/whl/torch
0.994 ERROR: Could not find a version that satisfies the requirement torch==1.13.1+cu117 (from versions: 1.10.2, 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1)
1.044 ERROR: No matching distribution found for torch==1.13.1+cu117
------

 1 warning found (use docker --debug to expand):
 - JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 84)
Dockerfile.gpu:80
--------------------
  78 |
  79 |     RUN poetry install
  80 | >>> RUN $POETRY_VENV/bin/pip install torch==1.13.1+cu117 -f https://download.pytorch.org/whl/torch
  81 |
  82 |     EXPOSE 9000
--------------------
ERROR: failed to solve: process "/bin/sh -c $POETRY_VENV/bin/pip install torch==1.13.1+cu117 -f https://download.pytorch.org/whl/torch" did not complete successfully: exit code: 1

Running on a Macbook M1 -- does that matter?

Yep. You're trying to install pytorch with nvidia CUDA drivers, which are only supported on nvidia gpus. The gpu docker tag only supports CUDA.
If you are using docker desktop on macos, you are really just using a Linux VM. If you want to use Apple Silicon acceleration (Metal Performance Shaders), you have to run whisper natively.
You're better off trying https://github.com/ggerganov/whisper.cpp, which has good support for Apple Silicon.

@ayancey I see. In fact, what I'm trying to do is build the docker image on my Mac, but use it on AMD64 in Ubuntu. I guess I have to do the docker build on an Ubuntu AMD64 machine as well, is that correct?

@ayancey I see. In fact, what I'm trying to do is build the docker image on my Mac, but use it on AMD64 in Ubuntu. I guess I have to do the docker build on an Ubuntu AMD64 machine as well, is that correct?

I believe that is correct.

@ayancey That worked, running on my Ubuntu machine. Thanks!


[SPARK-31401][K8S] Show JDK11 usage in bin/docker-image-tool.sh

What changes were proposed in this pull request?
This PR adds an JDK11-based build example in bin/docker-image-tool.sh.
Why are the changes needed?
This helps the users migrate to JDK11 more easily.
Does this PR introduce any user-facing change?
Yes, but this is a usage help.
How was this patch tested?
First, check the help usage manually.
$ bin/docker-image-tool.sh -h
...
  - Build and push JDK11-based image with tag "v3.0.0" to docker.io/myrepo
    bin/docker-image-tool.sh -r docker.io/myrepo -t v3.0.0 -b java_image_tag=11-jre-slim build
    bin/docker-image-tool.sh -r docker.io/myrepo -t v3.0.0 push {code}

Then, build the image and check Java version.
$ docker run -it --rm docker.io/myrepo/spark:v3.0.0 java --version | tail -n3
openjdk 11.0.6 2020-01-14
OpenJDK Runtime Environment 18.9 (build 11.0.6+10)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.6+10, mixed mode)

Test build #121043 has started for PR 28171 at commit 1d3fe79.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25734/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25734/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25734/
Test PASSed.

Test build #121043 has finished for PR 28171 at commit 1d3fe79.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121043/
Test FAILed.

Retest this please.

Test build #121049 has started for PR 28171 at commit 1d3fe79.

Test build #121049 has finished for PR 28171 at commit 1d3fe79.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121049/
Test FAILed.

Merged build finished. Test FAILed.

Retest this please.

Test build #121051 has started for PR 28171 at commit 1d3fe79.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25740/

The UT failure is consistent but irrelevant to this PR. I made a PR to fix the master branch.

https://github.com/apache/spark/pull/28174

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25740/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25740/
Test PASSed.

retest this please

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25742/

Test build #121053 has started for PR 28171 at commit 1d3fe79.

Test build #121053 has finished for PR 28171 at commit 1d3fe79.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121053/
Test FAILed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25742/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25742/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25744/

retest this please

Test build #121051 has finished for PR 28171 at commit 1d3fe79.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121051/
Test FAILed.

Test build #121057 has started for PR 28171 at commit 1d3fe79.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25744/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25744/
Test PASSed.

retest this please

Test build #121059 has started for PR 28171 at commit 1d3fe79.

Thank you for review and approval, @HyukjinKwon .
Since this PR is irrelevant to the Jenkins UT, I'll merge this. The JDK11 docker image generation is verified locally. Merged to master/3.0.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25747/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25747/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25747/
Test FAILed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25749/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/25749/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25749/
Test PASSed.

Test build #121057 has finished for PR 28171 at commit 1d3fe79.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121057/
Test PASSed.

Test build #121059 has finished for PR 28171 at commit 1d3fe79.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121059/
Test FAILed.


Gallery with mixed content types

Gallery with mixed content types, it always opens the first element, should open the clicked element
http://codepen.io/anon/pen/KvcCJ

its been a while on this thread but thought id update in case anybody else comes across this, gallery:{enabled:true} is working for me using this solution.

For anyone coming in through Google. Youtube / Vimeo / etc videos don't load properly locally (as in running your site from file:// while having the standard http:// for youtube). Spun my wheels on this for awhile thinking the above configuration didn't work, but it was just due to running it locally. Once I put a local web server in the middle everything worked as expected.

This works for non-image or non-video elements too.
Just set item.type = 'inline' and item.src='something.file download here';
You have to provide your css for white-popup. Cheers! :wine_glass: cheers!

$('.Class_NAME_HERE').magnificPopup({
			type: 'image',
			gallery:{
				enabled:true
			},
			callbacks: {
				elementParse: function (item) {
					// Function will fire for each target element
					// "item.el" is a target DOM element (if present)
					// "item.src" is a source that you may modify

					item.type = $(item.el.context).data('itemtype');
					item.iframe = {
						/*markup: '
'+
						 '

'+
						 ''+
						 '
', // HTML markup of popup, `mfp-close` will be replaced by the close button*/
						patterns: {
							dailymotion: {
								index: 'dailymotion.com',
									id: function(url) {
									var m = url.match(/^.+dailymotion.com\/(video|hub)\/([^_]+)[^#]*(#video=([^_&]+))?/);
									if (m !== null) {
										if(m[4] !== undefined) {
											return m[4];
										}
										return m[2];
									}
									return null;
								},
								src: 'https://www.dailymotion.com/embed/video/%id%'
							},
							youtube: {
								index: 'youtube.com/', // String that detects type of video (in this case YouTube). Simply via url.indexOf(index).
									id: 'v=', // String that splits URL in a two parts, second part should be %id%
									// Or null - full URL will be returned
									// Or a function that should return %id%, for example:
									// id: function(url) { return 'parsed id'; }
									src: '//www.youtube.com/embed/%id%?autoplay=1' // URL that will be set as a source for iframe.
							},
							vimeo: {
								index: 'vimeo.com/',
									id: '/',
									src: '//player.vimeo.com/video/%id%?autoplay=1'
							}
						},
						srcAction: 'iframe_src'
					}

				}
			}
			// other options
		});

in the anchor tag put data-itemtype='image'  for photo type or data-itemtype="iframe"  for video type


removed flexible checkwitness for 66 or 40 bytes addresses

What current issue(s) does this address, or what feature is it adding?
The Runtime_CheckWitness from neo-python currently accepts "addresses" (scripthash/pubkey) to have 66 or 40 bytes. This cannot be accepted, because the "original" network only accepts 20 or 33.
One problem this may cause (that we verified using Eco neocompiler.io) is that the same path may diverge from Python and C# implementations... The following code does this:
from boa.interop.Neo.Runtime import Notify, CheckWitness
from boa.interop.Neo.Storage import Get, Put, Delete, GetContext
from boa.interop.Neo.Runtime import Notify

def Main():
    OWNER=b'031a6c6fbbdf02ca351745fa86b9ba5a9452d785ac4f7fc2b7548ca2a46c4fcf4a'
    result = CheckWitness(OWNER)
    if result:
        print("OWNER is caller")
        Put(GetContext(), "oi", "python")
        return True
    else:
        print("OWNER is not caller")
        Put(GetContext(), "oi", "C#")
        return True

    return False

Storage "oi" in python rpc will be  "python", and in neo-cli C# node will be different... for the same execution.
How did you solve this problem?
I removed both problematic lines.
How did you make sure your solution works?
I tested this solution in neocompiler.io Eco locally.
Are there any special changes in the code that we should be aware of?
I believe these lines were put to simplify neo-boa work... but neo-boa needs some improvements, and there's an opportunity here.
Currently, both codes generate the same opcodes:
    OWNER=b'031a6c6fbbdf02ca351745fa86b9ba5a9452d785ac4f7fc2b7548ca2a46c4fcf4a'
    OWNER="031a6c6fbbdf02ca351745fa86b9ba5a9452d785ac4f7fc2b7548ca2a46c4fcf4a"

The opcode is: 	PUSHBYTES66<PHONE_NUMBER>63366662626466303263613335313734356661383662396261356139343532643738356163346637666332623735343863613261343663346663663461  ### "031a6c6fbbdf02ca351745fa86b9ba5a9452d785ac4f7fc2b7548ca2a46c4fcf4a"
In other words, it assumes the input is a string composed of ascii chars. It would be nice if the binary input was treated like: OWNER=b'\x03\x1alo\xbb\xdf\x02\xca5\x17E\xfa\x86\xb9\xbaZ\x94R\xd7\x85\xacO\x7f\xc2\xb7T\x8c\xa2\xa4lO\xcfJ'
(which is the output of binascii.unhexlify(OWNER), if OWNER is binary string)
I don't know if this information is available (binary string vs pure string) for byteplay, etc, but this is possibly a transparent solution for the user. If not possible, however, user must manually apply unhexilfy in order to make string real 20 or 33 bytes... that's life.
Please check the following, if applicable:

[X] Did you add any tests?
[ ] Did you run make lint?
[ ] Did you run make test?
[X] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

I think we will just have to require that when an owner is defined in a contract that it is defined in an unhexxed binary format such as OWNER=b'\x03\x1alo\xbb\xdf\x02\xca5\x17E\xfa\x86\xb9\xbaZ\x94R\xd7\x85\xacO\x7f\xc2\xb7T\x8c\xa2\xa4lO\xcfJ'

Thanks for the contribution!  Could you update the changelog?

Ok, I'm doing the tests, then I'll update the changelog.

Ok, I finished the tests. How do I submit them?
By the way, I think the docs part failed:
$ make docs
make -C docs html
make[1]: Entering directory '/home/imcoelho/git-reps/neo-python/docs'
/home/imcoelho/git-reps/neo-python/myvenv/bin/python: No module named sphinx
Makefile:20: recipe for target 'html' failed

I wouldn't worry about the docs, you'll need to have a separate venv with python 3.5 for those to build correctly.
You could add the tests to one of the existing tests in neo/SmartContract/tests or create a new test file there.

Ok, I didn't create new tests, only executed make lint, make test and make coverage. I believe that's all then.


npm run test fails

I followed the instructions to create smart contrat from here(https://docs.near.org/develop/contracts/quickstart)
app created successful.
Build was also successful.
[transpileJsAndBuildWasm] › ✔ success   Generated build/hello_near.wasm contract successfully!
npm run test keeps failing
here is the error message
><EMAIL_ADDRESS>test
> ava ../build/hello_near.wasm

Uncaught exception in ../build/hello_near.wasm

  ~/~/dev/hello-near-sm/build/hello_near.wasm:1

  SyntaxError: Invalid or unexpected token

  › SyntaxError: Invalid or unexpected token
  › require.extensions.<computed> (node_modules/ts-node/src/index.ts:1608:43)

  ✘ ../build/hello_near.wasm exited with a non-zero exit code: 1
  ─

  1 uncaught exception

node v20.11.0
npm v10.2.4

I advise you to use the test sript from package.json it is called like this: npm run test or add "--" after ava in your call and pass the correct file path!

the test is working on multiple node versions:
https://github.com/near/create-near-app/blob/master/.github/workflows/test-contract-ts.yml


test on multiple computers

Has been installed and tested on multiple computers; closing. Let's discuss testing strategy closer to next release.


Vim-which-key support

I see that which-key support was breifly added and then removed here.
Are you still planning on supporting it at some point?
If not would you mind saying why? Just so it shows up in google :)

I think I ran into weird errors with it and it was pretty involved to set up. But I'll reinvestigate!

Thanks!

I guess folke/which-key.nvim works better.

It looks cool but it looks like it requires neovim 0.5 which isn't stable yet.
Soon though hopefully 🤞

I think I'll use this newer implementation but yeah, it'll require 0.5 for
it to work, which shouldn't be much longer! Lots of us are already on 0.5,
come on in, the water's fine and TreeSitter-y :)
On Sun, 30 May 2021 at 22:49, Oliver Marshall @.***>
wrote:

It looks cool but it looks like it requires neovim 0.5 which isn't stable
yet.
Soon though hopefully 🤞
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/205#issuecomment-851066410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XKTDUKB3EO4GI3TTNLTQKXIHANCNFSM44ZRONCA
.

IMHO nvim is rolling release :smile:

Haha, I'm inclined to agree, although I look forward to using a stable pin
of Neovim that I don't recompile every day :D
On Mon, 31 May 2021 at 11:31, Leiser Fernández Gallo <
@.***> wrote:

IMHO nvim is rolling release 😄
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/205#issuecomment-851394321, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XOZKGWH4VLA4OUQUKTTQNQPNANCNFSM44ZRONCA
.

I've just spent the whole weekend reading into it all. I think I'm going to
be spending today converting to it and all the new fancy plugins 😅
On Mon, 31 May 2021, 11:32 Oliver Caldwell, @.***>
wrote:

Haha, I'm inclined to agree, although I look forward to using a stable pin
of Neovim that I don't recompile every day :D
On Mon, 31 May 2021 at 11:31, Leiser Fernández Gallo <
@.***> wrote:

IMHO nvim is rolling release 😄
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/205#issuecomment-851394321,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AACM6XOZKGWH4VLA4OUQUKTTQNQPNANCNFSM44ZRONCA
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/205#issuecomment-851394892, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACD2NARSWE6ZOEFC4K7TGY3TQNQUDANCNFSM44ZRONCA
.

Just bumping now that 0.5 is out.
I hope you're still interested in this :)

I just sat down to write these out and it ended up being much easier than I'd assumed 😅.
Here's my code, I assume that the leader set to <leader>, but that's easy enough to change.
I've only added the mappings for the clojure client as that's all I use. It was pretty easy to just go to the mappings section of the relevant client's doc file and fill in what you want though, much recommeded.
I'm also using my package manager to only load this when I open a clojure file, you'll need some other method of sorting that out :).


flow check-contents --all parameter redundant

produced on flow version 0.37.4
according to the docs --all causes flow check-contents to Ignore absence of an @flow pragma. To me this suggests that, without this flag, flow check-contents will ignore stdin missing the /* @flow */ declaration. However, running echo 'a = "str";a(5);' | flow check-contents outputs:
-:1
  1: a = "str";a(5);
     ^ assignment of identifier `a`. Could not resolve name

-:1
  1: a = "str";a(5);
               ^^^^ function call. Function cannot be called on
  1: a = "str";a(5);
               ^ string

It's unclear to me what the --all parameter is for or if I am simply misunderstanding it or if there is an issue with the default flow check-contents functionality.
Thanks in advance for the help!

Hi @drabinowitz! You're right! --all is currently a no-op. The reason for this is that we're planning on changing the behavior of check-contents to respect the presence or absence of a @flow pragma. Adding --all makes the transition a little easier.
@mroch detailed his plan in https://github.com/facebook/flow/commit/768201006495f867e9bdfe2b922e5fa7de09f1d5.

Ah, thanks a lot for clearing that up!

Hi @gabelevi. Could you please clarify, in 0.45 --respect-pragma is not listed as a possible option in flow check-contents --help, but it works as expected and changes the behavior. Will you keep it after making it the default option?

🏓 check-contents --all is still the default, is still documented without mentioning that it is the default behavior and therefore a no-op, and --respect-pragma is still not documented despite having an often quite desirable effect. see #4924


Add clang variants

Added all major clang versions from 6 to 10 in ci-common images, mainly:

ci-common:1-clang6.6, ci-common:1-clang7.6, ci-common:1-clang8.6, ci-common:1-clang9.6, ci-common:2-clang10.2
ci-openvdb:2018-clang7.6, ci-openvdb:2019-clang6.6, ci-openvdb:2019-clang7.6, ci-openvdb:2019-clang8.6, ci-openvdb:2019-clang9.6, ci-openvdb:2020-clang7.6, ci-openvdb:2021-clang10.2
ci-osl:2018-clang7.2, ci-osl:2019-clang6.2, ci-osl:2019-clang7.2, ci-osl:2019-clang8.2, ci-osl:2019-clang9.2, ci-osl:2020-clang7.2, ci-osl:2021-clang10.2

As I had to add quite a few changes to the version definitions I finished moving some of that data into the versions.yaml file.
I also had to lock the version of black in both the pre-commit and pipenv configs to work around a problem where the pre-commit got upgraded and the pipenv version of black was still behind...
I've released aswftesting/ci-openvdb:2019-clang6, aswftesting/ci-openvdb:2019-clang7, aswftesting/ci-openvdb:2019-clang8, aswftesting/ci-openvdb:2019-clang9, aswftesting/ci-openvdb:2021-clang10 for early testing if @danrbailey wants to try them first?

Thanks @danrbailey with the changes that I've done it would be trivial to add a whole range of images. I've got the feeling that 2020 is not going to be a very "popular" year as the main difference with 2019 was python3, and I feel 2019 will stick around for quite some time as it is the last py2 + gcc-6 combo... But I'd rather not push images out if you think you would rather have 2020 versions.
I'm happy to update the version.yaml file to be like this instead:
  openvdb:
    - "2018-clang7.6"
    - "2019-clang7.6"
    - "2020-clang6.6"
    - "2020-clang7.6"
    - "2020-clang8.6"
    - "2020-clang9.6"
    - "2021-clang10.2"

Fantastic work all, thank you! @danrbailey I'll test these asap

I've got a few days off starting today, so that gives @Idclip some time to test the aswftesting images. If everything is OK I'll kick off the build of the new aswf images next Wednesday.

Looks good so far!
https://github.com/Idclip/openvdb/runs/1203442514?check_suite_focus=true
The 2021 g++ error can be ignored, but I'm getting a failure with the 2019-clang7 container with clang (where as the same container with gcc succeeds) - at first glance this seems like a bug with the software rather than the container, but this does pass after building LLVM from source:
https://github.com/dneg/openvdb/runs/1179581003?check_suite_focus=true
I've not see this before so will need time to investigate.
One last thought - any plan to add vfxall-clangx containers? The way I'm structuring our CI currently is to build a few builds with the openvdb image and then test the various versions of llvm within the vfxall containers as the new library we're introducing depends on the core openvdb build. In this way I avoid building openvdb itself and test against an existing install:
https://github.com/AcademySoftwareFoundation/openvdb/pull/818/files#diff-629a662cb0429237d9cc099d647f87f8R78
This isn't a big problem, I can simply switch to using the openvdb images and install the core lib first (which is relatively fast).

Lemme know when you've got the ci-osl varieties built for aswftesting, and I'll give them a try.

The https://github.com/dneg/openvdb/runs/1179581003?check_suite_focus=true error is puzzling indeed, do you know if this works with aswf/ci-openvdb:2019? In theory the only difference between aswftesting/ci-openvdb:2019-clang7 and aswf/ci-openvdb:2019 is the addition of clang-tidy...
Just looking at the logs it seems that in your working job has LLVM_DIR specified explicitely... Maybe that could cause some difference?

The aswftesting/ci-osl docker images are ready for testing https://github.com/AcademySoftwareFoundation/aswf-docker/actions?query=workflow%3ARelease

I'm having errors trying to get these images. Is this not the right way?
container:
  image: aswftesting/ci-osl:2019-clang7.2

Strange... what error are you getting?
I just tried docker run -it --rm aswftesting/ci-osl:2019-clang7 clang --version and it pulled the image and worked...
Also, I'd recommend without the minor version number:
container:
  image: aswftesting/ci-osl:2019-clang7

I think it's fine now that I dropped the minor version

That's good to hear, any issues with the various clang versions? I'm happy to pull the trigger on the official image builds if you tell me you're good with them!

I haven't exhaustively tested, but the ones I tried seem all ok to me.

Thanks Larry, I'll merge and start releasing the images, I'll go with ci-common and ci-osl first and release new sets every day this week :-)

@aloysbaillet I've been investigating the issue with the vdb-clang7 container and believe I've figured it out; it is indeed an ABI issue with versions of libLLVM.so built with gcc and applications built with clang. This was fixed and backported for 7.1.0 but is broken in 7.0.1. Our tests that build with clang++ are thus broken in this container - you're correct in that this problem also exists in openvdb:2019.
http://llvm.1065342.n5.nabble.com/LLVM-7-1-0-Release-td128369.html
https://bugs.llvm.org/show_bug.cgi?id=39427
Apologies for the delay in reporting. @lgritz out of curiosity do you have a test building with clang 7.0.1 and using llvm 7.0.1? @aloysbaillet Is there a difference in the version of clang 7.x.x that the VDB and OSL containers are using? Either way, would it be possible to provide me a 7.1.0 clang container to test? I've been able to reproduce the issue locally and 7.1.0 fixes it. It seems that that's the version I'll need.

@Idclip I think I don't test the specific combination of clang7 + llvm7. I test gcc vs each supported llvm, and I have a clang9+llvm9 (I think) and also a clang10+llvm10 (on Mac).


Unable to push app with manifest.yml using a non-default stack

Please fill out the issue checklist below and provide ALL the requested information.

[X] I reviewed open and closed github issues that may be related to my problem.
[X] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[X] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[X] I am reporting a bug that others will be able to reproduce.
[ ] If this is an issue for the v7 beta release, I've read through the official docs and the release notes.

Describe the bug and the command you saw an issue with
Using cf7 v7.0.2 I'm unable to push an app to the stack specified in the manifest.  For example:
---
applications:
- name: aspxtest01
  stack: windows2012R2
  buildpacks:
  - hwc_buildpack
  instances: 1
  health-check-type: port

What happened
App failed to push.
cf push
Pushing app aspxtest01 to org test / space test as admin...
Applying manifest file C:\Development\aspxtest\manifest.yml...
For application 'aspxtest01': Buildpack "hwc_buildpack" must be an existing admin buildpack or a valid git URI

If I override the stack on the command line, it does work:
cf push -s windows2012R2
Pushing app aspxtest01 to org test / space test as admin...
Applying manifest file C:\Development\aspxtest\manifest.yml...
Manifest applied
Packaging files to upload...
Uploading files...
 1.28 KiB / 1.28 KiB [=================================================================================================================================================] 100.00% 1s

Waiting for API to complete processing files...

Staging app and tracing logs...
   Downloading hwc_buildpack...
   Downloaded hwc_buildpack
   <snip>

Expected behavior
App should be deployed successfully, manifest works with cf v6.
To Reproduce

Create manifest per above.
cf push
See error

Provide more context

API version:    3.87.0

We discovered this issue is actually in the cf CLI code base, we have submitted a PR to fix this https://github.com/cloudfoundry/cli/pull/2148 which should go out in the next cf CLI release.
Closing this now, please feel free to follow up further if you do not see this get resolved, thanks!
Jenna

Thanks for following up on this, I'll monitor the CLI issue.


Improve camera focus of plot_read_inverse

This PR improves the focus of the camera of the plot_read_inverse-py example.
Before:

After:

Thank you, tuple is more consistent actually.

thx @GuillaumeFavelier


Release/1.21.0

1.21.0 - 2022-08-23
Important: This update requires a MongoDB update schema due to a bug in the original migration  of showing summary statistics at the
space level. Make sure to start the application with -DMONGOUPDATE=1. You can also run the fixCounts.js
script prior to upgrading to minimize the downtime.
Added

MRI previewer for NIFTY (.nii) files.
HEIC (.heic) and HEIF (.heif) mimetypes to support new Apple iPhone image file format.
In the docker container the folder /home/clowder/data is now whitelisted by default for uploading by reference.
This can be changed using the environment variable CLOWDER_SOURCEPATH.
The current CLA for developers of clowder.

Fixed

Send email to all admins in a single email when a user submits 'Request access' for a space
Send email to all admins and request user in a single email when any admin accepts/rejects 'Request access' for a space #330
script/code to count space in files was not correct #366
github actions would fail for docker builds due to secrets not existing
Fix to remove dataset from a space #349
(The count might be off to existing spaces, please run fixCounts script)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: ddey2:white_check_mark: cconsta1:white_check_mark: robkooper:x: pgrovesYou have signed the CLA already but the status is still pending? Let us recheck it.


⚠ ClamAV has degraded performance

In bda586d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 732 ms

Resolved: ClamAV performance has improved in 41cdd13.