feat: enable canister sandboxing

The mainnet runs with canister sandboxing, so dfx also should
run with canister sandboxing to be consistent otherwise some
upcoming features like deterministic time slicing would not
work in dfx.
Checklist:

[x] The title of this PR complies with Conventional Commits.
[x] I have edited the CHANGELOG accordingly.
[ ] I have made corresponding changes to the documentation.

Please take a look

I have made corresponding changes to the documentation.
I am not sure what does this mean.

I am also not sure if this should be considered as feat or fix.


Backup never completes

The
Describe The Bug:

When using the backup feature, the backup process never completes and the 3 tar.gz files remain in /tmp. Even when left for hours, process never completes.
To Reproduce:
Run backup
Expected behavior:

Single backup archive created
Logs:

[7/11/2020, 8:15:25 PM] [Config] Creating temporary backup archive at /tmp/homebridge-backup-pDHoje/homebridge-backup-CC223DE3CE85.tar.gz,
[7/11/2020, 8:17:44 PM] [Config] Creating temporary backup archive at /tmp/homebridge-backup-MCifhl/homebridge-backup-CC223DE3CE85.tar.gz,
[7/11/2020, 8:19:25 PM] [Config] Creating temporary backup archive at /tmp/homebridge-backup-oMGLDe/homebridge-backup-CC223DE3CE85.tar.gz,
[7/11/2020, 8:25:34 PM] [Config] Backup is skipping "storage/core" because it is larger than 10MB.,
[7/11/2020, 8:25:35 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg" because it is larger than 10MB.,
[7/11/2020, 8:25:35 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg_g" because it is larger than 10MB.,
[7/11/2020, 8:25:35 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe" because it is larger than 10MB.,
[7/11/2020, 8:25:35 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe_g" because it is larger than 10MB.,
[7/11/2020, 8:26:50 PM] [Config] Backup is skipping "storage/FFmpeg/libavcodec/libavcodec.a" because it is larger than 10MB.,
[7/11/2020, 8:27:29 PM] [Config] Backup is skipping "storage/FFmpeg/libavfilter/libavfilter.a" because it is larger than 10MB.,
[7/11/2020, 8:28:00 PM] [Config] Backup is skipping "storage/FFmpeg/libavformat/libavformat.a" because it is larger than 10MB.,
[7/11/2020, 8:28:38 PM] [Config] Backup is skipping "storage/fdk-aac/.libs/libfdk-aac.a" because it is larger than 10MB.,
[7/11/2020, 8:29:05 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.idx" because it is larger than 10MB.,
[7/11/2020, 8:29:05 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.pack" because it is larger than 10MB.,
[7/11/2020, 8:37:12 PM] [Config] Backup is skipping "storage/core" because it is larger than 10MB.,
[7/11/2020, 8:37:12 PM] [Config] Backup is skipping "storage/core" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg_g" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe_g" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg_g" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe" because it is larger than 10MB.,
[7/11/2020, 8:37:13 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe_g" because it is larger than 10MB.,
[7/11/2020, 8:38:16 PM] [Config] Backup is skipping "storage/FFmpeg/libavcodec/libavcodec.a" because it is larger than 10MB.,
[7/11/2020, 8:38:16 PM] [Config] Backup is skipping "storage/FFmpeg/libavcodec/libavcodec.a" because it is larger than 10MB.,
[7/11/2020, 8:39:37 PM] [Config] Backup is skipping "storage/FFmpeg/libavfilter/libavfilter.a" because it is larger than 10MB.,
[7/11/2020, 8:39:37 PM] [Config] Backup is skipping "storage/FFmpeg/libavfilter/libavfilter.a" because it is larger than 10MB.,
[7/11/2020, 8:40:13 PM] [Config] Backup is skipping "storage/FFmpeg/libavformat/libavformat.a" because it is larger than 10MB.,
[7/11/2020, 8:40:13 PM] [Config] Backup is skipping "storage/FFmpeg/libavformat/libavformat.a" because it is larger than 10MB.,
[7/11/2020, 8:40:52 PM] [Config] Backup is skipping "storage/fdk-aac/.libs/libfdk-aac.a" because it is larger than 10MB.,
[7/11/2020, 8:40:55 PM] [Config] Backup is skipping "storage/fdk-aac/.libs/libfdk-aac.a" because it is larger than 10MB.,
[7/11/2020, 8:41:24 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.idx" because it is larger than 10MB.,
[7/11/2020, 8:41:24 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.pack" because it is larger than 10MB.,
[7/11/2020, 8:41:25 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.idx" because it is larger than 10MB.,
[7/11/2020, 8:41:25 PM] [Config] Backup is skipping "storage/FFmpeg/.git/objects/pack/pack-e92cd81d9f0ba1766dca6d58e04fac8adb2e121d.pack" because it is larger than 10MB.

Homebridge Config:
          {
            "name": "Config",
            "port": 8080,
            "auth": "form",
            "theme": "dark-mode",
            "tempUnits": "c",
            "lang": "auto",
            "log": {
                "method": "native",
                "path": "/homebridge/homebridge.log"
            },
            "platform": "config",
            "sudo": false,
            "sessionTimeout": 28800
        }

Screenshots:

Environment:

Node.js Version:  12.18.1
NPM Version:  6.14.5
Homebridge Version:  1.1.1
Homebridge Config UI X Version: 4.23.2
Operating System: Docker
Process Supervisor: Docker

Remove the FFmpeg/.git folder from your storage directory.
I'll do an update at some point to ignore .git folders.

Worked great, thanks!

Spoke too soon, running into this now, is it another folder I can delete?
[7/19/2020, 5:55:07 PM] [Config] Backup is skipping "storage/core" because it is larger than 10MB.

[7/19/2020, 5:55:07 PM] [Config] Backup is skipping "storage/core" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg_g" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe_g" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg_g" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffmpeg" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe" because it is larger than 10MB.

[7/19/2020, 5:55:08 PM] [Config] Backup is skipping "storage/FFmpeg/ffprobe_g" because it is larger than 10MB.

[7/19/2020, 5:56:35 PM] [Config] Backup is skipping "storage/FFmpeg/libavcodec/libavcodec.a" because it is larger than 10MB.

[7/19/2020, 5:56:36 PM] [Config] Backup is skipping "storage/FFmpeg/libavcodec/libavcodec.a" because it is larger than 10MB.

[7/19/2020, 5:58:49 PM] [Config] Backup is skipping "storage/FFmpeg/libavfilter/libavfilter.a" because it is larger than 10MB.

[7/19/2020, 5:58:50 PM] [Config] Backup is skipping "storage/FFmpeg/libavfilter/libavfilter.a" because it is larger than 10MB.

[7/19/2020, 5:59:46 PM] [Config] Backup is skipping "storage/FFmpeg/libavformat/libavformat.a" because it is larger than 10MB.

[7/19/2020, 5:59:47 PM] [Config] Backup is skipping "storage/FFmpeg/libavformat/libavformat.a" because it is larger than 10MB.

[7/19/2020, 6:00:24 PM] [Config] Backup is skipping "storage/fdk-aac/.libs/libfdk-aac.a" because it is larger than 10MB.

[7/19/2020, 6:00:30 PM] [Config] Backup is skipping "storage/fdk-aac/.libs/libfdk-aac.a" because it is larger than 10MB.

Does it complete though? The warnings are just that.

Unfortunately not, those are the last logs regarding backup. I started the
process at 6pm yesterday, it’s been 15 hours, so it’s clear nothing is
going to happen.
On Mon, Jul 20, 2020 at 12:57 AM oznu<EMAIL_ADDRESS>wrote:

Does it complete though? The warnings are just that.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/oznu/homebridge-config-ui-x/issues/774#issuecomment-660867591,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWLHYAZXFERM3ZGG3FZT7LR4P2E5ANCNFSM4OX2ZLSQ
.

Just cleared those out, not even sure why they were there - maybe from when I compiled ffmpeg before it was an included package...
Anyway, backup completed this time! Thank you.


Add CD for Docker images

Our Docker org no longer grants access to developer accounts, only bots. This runs afoul of our current decK release process, where we build and push Docker images locally.
We need to add a CD-based Docker image build for tags to handle this instead.

There is a desire to move off Github for hosting our release assets.
Note to future selves: do not increase the scope of this release to include automation for goreleaser.


New package: ECCO v0.0.1

Registering package: ECCO
Repository: https://github.com/gaelforget/ECCO.jl
Created by: @gaelforget
Version: v0.0.1
Commit: ea87296d36a53d03b57826e3c80bc939594a10c5
Reviewed by: @gaelforget
Reference: https://github.com/gaelforget/ECCO.jl/issues/1#issuecomment-2409075382

I would like my pull request to be manually merged instead of via AutoMerge.
Explanation : the chosen name ECCO.jl stands for Estimating the Circulation and Climate of the Ocean and is widely known in the climate and ocean science community by its acronym, ECCO.

ECCO is a 40+ years running effort initiated by Pr. Carl Wunsch at MIT, and which now involves distributed academic projects accross the US (MIT, NASA JPL, UCSD, UTA, WHOI), Europe (AWI, UH), and the UK (BAS).
extending the acronym would make it both (1) much harder to find by the targeted scientific community, and (2) a very long package name to type.
if another package ended up called ECCO.jl later, this would be damageable to our climate science and community building effort (by making it even harder for users to find the present package, and possibly turn them off from bridging to Julia, which is one of the goal of this package).

I like the name, and I’d definitely support merging this. In my opinion, pronounceable acronyms should always be okay (it’s just hard for the bot to distinguish pronounceable from unpronounceable acronyms)
It’s not up to me, though. The 5 letter minimum rule can only be overridden with a manual merge from a registry maintainer.
You have to fix the compat issues first, though. Those are mandatory.

I like the name, and I’d definitely support merging this. In my opinion, pronounceable acronyms should always be okay (it’s just hard for the bot to distinguish pronounceable from unpronounceable acronyms)
It’s not up to me, though. The 5 letter minimum rule can only be overridden with a manual merge from a registry maintainer.

Thanks for the feedback and supporting words! Makes me hopeful that a registry maintainer will agree with you and merge

You have to fix the compat issues first, though. Those are mandatory.

should be all set with compat now I think, following

https://github.com/gaelforget/ECCO.jl/commit/ea87296d36a53d03b57826e3c80bc939594a10c5
https://github.com/gaelforget/ECCO.jl/commit/3d8305377a6c1535eaca6c99cd6d3065c5694e72

Or am I overlooking something?

Hi @goerz & @vchuravy
just giving this a ping to bring it back up on your radar. Would be awesome if this could be merged today.
I am almost ready to release the next version, v0.1.1, which I am hoping to do live as a demo tomorrow (at this hackweek).

I don't have merge permission, unfortunately, but yes, this should be merged as soon as possible, since the three-day period is up. If @vchuravy can't help you out with this, maybe ping the #pgk-registration channel on Slack.

I am almost ready to release the next version, v0.1.1

That seems like a version jump… Do you mean v0.1.0? In any case, do not try to register a new version before this PR is merged.

I don't have merge permission, unfortunately, but yes, this should be merged as soon as possible, since the three-day period is up. If @vchuravy can't help you out with this, maybe ping the #pgk-registration channel on Slack.

Cool. Will give it a minute for now

I am almost ready to release the next version, v0.1.1

That seems like a version jump… Do you mean v0.1.0? In any case, do not try to register a new version before this PR is merged.

Good point. Did mean v0.1.0


cmd/vet: remove check for trailing newline in Println

One of the requirements for a vet check is correctness.
Currently, the vet tool has a check for trailing "\n" in fmt.Println. It doesn't seem like this is a matter of correctness, but rather of style. Should this check be moved from vet to lint?
\cc @robpike

I would like to leave it in, under the unwritten "venerable" criterion. It fits in well with the existing Printf checks, some others of which are also arguably less clearly wrong. But in practice, it does find errors, at least in my experience.


Attention weights visualization

Thank you very much for your work, how can I visualize the selfattention part?  For example the outputs of encoder or the inputs of crossattention?

i just extract the attention map in the multi head attention module.

Thank you


Remove Kubeflow 0.6 section in Authenticating Kubeflow to GCP?

https://www.kubeflow.org/docs/gke/authentication/
Shall we remove the section about "Kubeflow v0.6 and before: GCP service account key as secret"?
I think it's been a while, keeping it on the page is only getting confusing. We can just mention workload identity now.
/assign @jlewi
What do you think?

@Bobgy  LGTM


Fix to allow safe automerge

Fixes #272
Previously, automergable PRs had automerge enabled externally immediately after the PR was created assuming that only if the sentinel check passed, the PR would work. However, in case of failure in tests the sentinel check is skipped entirely causing the PR to be immediately merged when we don't want.
This change tries to enable automerge from within the sentinel step which will execute when the steps it depends on are successful.

One side-effect of checking the user who opened the PR is that if anyone adds extra commits on the end, it'll then auto-merge.
We also no-longer disable auto-merge if there's breaking changes.

This change is a bit more myopically done for the long-tail TF providers. AFAICR there was no such guardrail in place for these providers around breaking change detection.

I think the safer approach would be to also introduce an auto-merge tag which can be added immediately and checked in the enable-automerge step. We could also then later adapt the schema check to remove the tag if there's breaking changes found.

Yup - I wanted to test things out with this approach which seemed to work based on a couple of toy things I ran. I will add the auto-merge model to this PR.

Closing in favor of https://github.com/pulumi/ci-mgmt/issues/311


Create a Standard Readme linter

There should be a linter, after the spec in the main readme is filled out. The linter will most likely use remark and remark-lint. This is the planning issue for the linter. Please subscribe here, and open new issues for tangential questions about Standard Readme.

Hi @RichardLitt is there a linter already in progress? I started working on one that uses remark and remark-lint before discovering this conversation: https://github.com/SparkartGroupInc/quality-docs
It's definitely a work in progress, but I'd be interested in contributing toward this piece of the puzzle for standard-readme.

I've updated quality-docs to use remark's defaults and to accept a configuration file to override the default rules. The configuration file wouldn't have to be used in the case of standard-readme, but it made more sense to keep the defaults in remark rather than in quality-docs.

@josiahsprague Nice! There is a linter in progress, but I haven't gotten very far at it. I don't have much bandwidth for making the linter right now (unfortunately). quality-docs looks good from a quick glance; I think that making it standard-readme compatible would be 100% awesome.
I'm a bit confused by your second post: is the default remark's defaults, or standard-readme's (based on the spec) defaults?

The default I was referring to was remark's default. Seems reasonable to me to try to make remark-lint's defaults match the standard-readme spec. I'm assuming it's already pretty close, and I could open some PRs to update it where it's not. @wooorm what do you think?

I think you’re talking about lint defaults, right? So whether to use * or _ for emphasis?
In lieu of standard-readme being named after “standard”, it should probably have one style to rule them all. So no configuration.
That being said, not sure if @RichardLitt envisions this project, and an accompanying linter more as style linter (* or _) or an outline linter (required sections, required naming standards, etc.)?

I was thinking more of an outline linter. I don't care about style - that's useful, for some things, but largely unimportant for the purposes of humanely digesting the information of the README. As long as it is Markdown format, I am happy. In some cases, like adding a
## Header
, adding HTML is fine with me, too. Also, people are really attached to their READMEs, and enforcing style will lead to a lot of bikeshedding, tiredness, and ultimately abandonment of any standard readme style, I think.

Yup, I think so too!

Ok, in that case I can add a set of rules to quality-docs that modifies the remark-lint defaults to check the standard-readme spec in a lenient way that helps people avoid bike-shedding and fatigue. I'll make it possible to override in the case that someone wants to use the linter outside of the context of standard-readme, but I'll set it up to be the default.
Any thoughts on renaming quality-docs to standard-readme-linter?

@josiahsprague That sounds good to me. If it works, renaming also makes sense! Let's rename when we have a working product; might also be smart to move the linter into this repo, like is done with feross/standard, so that we can actually download the linter with npm i standard-readme.

👍
It’s also possible to have both project alongside each other, right? In that case, quality-docs can focus on more subjective matter like readability and style, and it could work on files not called readme.md as well, where standard-readme-linter would focus just on outline of readme.md files?

I'll have to put this on the back burner for now, but now that I've gotten more familiar with the project, I'm thinking that quality-docs could be used as a dependency in a project that runs something like;
quality-docs readme.md --rules standard-readme-spec.json --silent

Where standard-readme-spec.json would be a config file tailored to match the standard-readme spec. It'd take some work to support all of the features needed for the standard-readme spec, but still probably a good start.

If someone wants to tackle this before I get back to it, feel free to open issues or PRs in quality-docs for any features that need to be added.

Any updates on this? Love this project :heart: Was just thinking about a similar project and was really happy to see that someone else is already working on this! :tada:

From my side, I'm working on a different team now, and don't have time to work on this. But feel free to fork what's there and continue working on it. I'm happy to answer questions.

From mine, it isn't being prioritized at the moment, but should be in the next few months.

What's current status of the linter?

but should be in the next few months.

This was overly ambitious. I'm not currently working on it. I would be happy to advise on any PRs, though.

It might be useful to link to https://github.com/RichardLitt/standard-readme-preset ?

It might be useful to link to https://github.com/RichardLitt/standard-readme-preset ?

That would be a great idea. PRs accepted.

That would be a great idea. PRs accepted.


Metadata object in pact file not standards compliant

IN #34 we found a problem where the metadata section of the pact generated by my pact-js consumer tests is not compatible with the pact-jvm's PactReader.loadPact resolves the pact spec version.
This code in PactReader (from the master branch/latest version):
 static Pact loadPact(Map options = [:], def source) {
    def pact = loadFile(source, options)
    def version = '2.0.0'
    def specification = pact.metadata?.'pact-specification'
    if (specification instanceof Map && specification.version) {
      version = specification.version
    }
    if (version == '3.0') {
        version = '3.0.0'
    }
    def specVersion = Version.valueOf(version)
    switch (specVersion.majorVersion) {
        case 3:
            return loadV3Pact(source, pact)
        default:
            return loadV2Pact(source, pact)
    }
  }

expects a metadata spec. version section that has this format:

"metadata": {
        "pact-specification": {
            "version": "x.x.x"
        }

BUT pacts generated from pact-js generates a metadata section that looks like this:

"metadata": {
    "pactSpecificationVersion": "3.0.0"
  }

See #34 and https://github.com/realestate-com-au/pact/issues/137 for background.

@mefellows is this still an issue and shouldn't this be lodged with pact-jvm than with pact-node?

Looking through the threads, looks like we need to move to pactSpecification.version as per https://github.com/pact-foundation/pact-mock_service/commit/5b89d95167013ac4b11030b362c439f5632e7540

Pact JS now generates metadata as per beow:
  "metadata": {
    "pactSpecification": {
      "version": "2.0.0"
    }
  }

... ☝ as of a long time ago!


Code review - configuration / RPC agent config

*General code review and assistance in consuming configuration helpers
*Assistance in using configuration implementation as performed in RPC Agent

Scheduled for Wed 24th August

Complete :)


chore: remove underscore from builtin_time_grains label

SUMMARY

remove underscore from builtin_time_grains label

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks for the fix @cnabro!


Document binary messages

How would one go adding a binary-encoded message as a response from a publish?
E.g.
Client subscribes to a channel requesting a series of sensor data
Server is optimizing such request and packing in an array the values of 10 sensors in binary format
Client will start receiving a stream of data (timestamp, <array>) and will unpack accordingly

@fgadaleta hey, are you sure this is the right repo where you wanted to create an issue? It doesn't sound like related to asyncapi website. Is it AsyncAPI spec related question?

you are absolutely right @derberg
i am closing and posting to the correct repo.
Thank you


Tensorflow lite demo app gives wrong result in GPU delegate (Honor Play Android 9.0 GPU Turbo)

System information

OS Platform and Distribution: Android 9.0 (API 28)
Mobile device : Huawei Honor Play 9.0 ,GPU: Mali G72 MP12 (GPU Turbo)
TensorFlow installed from: tensorflow-lite:0.0.0-gpu-experimental

Describe the current behavior
The tensorflow lite gpu delegate demo application gives incorrect results for image classification , when it is run on GPU; whereas the same float model gives correct results when it is run on CPU.Even the quantized model in the demo application gave correct inference results in this application.We even tried the official deeplab model for semantic segmentation with the same phone; but even in this scenario it gave wrong results (square/stripes), instead of correct masks.
The same model is running in other phones with Adreno GPU and also in some phones with Mali GPU (eg: Samsung A8+ Android 9.0).
Describe the expected behavior
The tensorflow lite gpu inference should give same results in cpu and gpu in all the android phones.
Other info / logs
It looks like the  phone uses a new feature called GPU Turbo .Initially the model
was working correctly with android 8.1 (stock os).But after the 9.0 upgrade the tflite models are giving wrong results.

It is working fine in tensorflow-lite:0.0.1-gpu-experimental and latest nightly version ...


[TRACKING] Rules syntax enhancements (backward-compatible)

Motivation
This issue tracks all the efforts aimed to introduce new constructs (in a backward compatible fashion) to address the most common user requests, as per the Falco 1.0.0 roadmap.
N.B. Other issues will be opened for backward-incompatible changes to the language syntax.
Additional context

https://github.com/falcosecurity/libs/issues/1789
https://github.com/falcosecurity/falco/issues/2403

### Tasks
- [ ] https://github.com/falcosecurity/libs/issues/1925
- [ ] https://github.com/falcosecurity/libs/issues/1927
- [ ] https://github.com/falcosecurity/libs/issues/1928
- [ ] https://github.com/falcosecurity/libs/issues/2025

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


Create ja_jp.json

Japanese translation. Some word-for-word translation doesn't fit in Japanese, I used the following words:
"Vein Goblin" to "溶岩ゴブリン" (Lava Goblin)
"Annoyed Grunt" to "ゴブリンのうめき声" (Goblin's groaning sound or voice)
"Idle Grunt" to "ゴブリンの声" (Goblin's sound or voice)

Thank you!


most up to date screen pics

Hi,
Are the screens shared on this page the most up to date for MFA authentication set up?
thanks!
Sophie

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

ID: 4fc7dec3-d354-6e40-8662-0e8175e3cb09
Version Independent ID: 49976ef5-2893-8f73-3a64-94c2f3753d04
Content: Set up an authenticator app as your two-factor verification method - Azure Active Directory
Content Source: articles/active-directory/user-help/multi-factor-authentication-setup-auth-app.md
Service: active-directory
Sub-service: user-help
GitHub Login: @curtand
Microsoft Alias: curtand

@sorosgaa
Thanks for your feedback! We will investigate and update as appropriate.

Hey @sorosgaa
Thanks for providing feedback that helps improve our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response.  We are currently updating all the end-user content and will be migrating to the Microsoft Support site. We are closing the issue as we are migrating the content to a new site. #please-close


Problem with 'Sidekiq'

Problem with 'Sidekiq' (https://docs.publishing.service.gov.uk/manual/sidekiq-retries.html)
Sidekiq monitor link at bottom of page is broken

Addressed in https://github.com/alphagov/govuk-developer-docs/pull/189

Closing this as #189 has been merged.


Manage CommitmentKeyHints properly in supernova

This is where the optfn1, optfn2 parameters from above come in. They need to be parametrized by a preference expressed as a static function of the SNARK that will eventually be used to compress the proof. See #5. We should open an issue to fix this across SuperNova.
Originally posted by @huitseeker in https://github.com/lurk-lab/arecibo/pull/51#discussion_r1334773944

Closed in #95


Rebuild for latest conda-forge pins

We need to bump our versions of both fontconfig and freetype.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Whoops, this can't go ahead until harfbuzz is rebuilt.

Kicking CI since all dependencies should now be updated, I think.

Yes, CI tests now pass. Should be OK to merge.


Persistent configuration between sessions

Note: enhancement request.
As a Plex-aaos user I want to have the settings and state of my playback persisted between sessions including:

current playlist
repeat status
shuffle status
current position in playlist
so that I can continue my listening where I left off without having to navigate the app to restore the configuration.

Additional bonus ask: perhaps persist the config per playlist so switching between playlists restores the state from a prior session with that playlist.

Sounds good. My only concern with remembering settings per playlist is heavy disk usage which will only get worse once I start to support additional browsing methods (artist, ...). If that feature is important, maybe a buffer storing the settings for the last X playlists?

Yeah, I could see the storage issue with many playlists. Maybe a last x playlists as a settable option with a user selected range from 1 to 10 or something sane. Good idea, sir!


using tanentId and Application Id but get the following error #invalid grant type

{
"error": "invalid_grant",
"error_description": "AADSTS50056: Invalid or missing password: password does not exist in the directory for this user.\r\nTrace ID: ddaee820-5ced1-47ee-b8d7-73dc9e70a000\r\nCorrelation ID: cb9553fd-4db3-47f3-8b95-369bdfcbe106a4b\r\nTimestamp: 2020-03-09 09:04:24Z",
"error_codes": [
50056
],
"timestamp": "2020-03-09 09:04:24Z",
"trace_id": "ddaee820-5ce1-47ee-b8d7-73dc9efd70a000",
"correlation_id": "cb9553fd-4db3-47f3-8b95-36dd9bbe106a4b",
"error_uri": "https://login.microsoftonline.com/error?code=50056"
}

@imshreya please provide a link to the document you are following so that we can better assist.

@imshreya please change the"Default Client type" to "yes" to activate ROPC flow, if you have not done so already.
Since this is not posted to a particular document you will need to open a thread on Q&A and we will continue the discussion there.


Upgrade to latest 'common' and 'build-tools'.

If building against the latest build-tools, you typically get:
tools/runner/runner.go:18:2: cannot find package github.com/weaveworks/common/mflag

This change fixes this issue by upgrading both:

weaveworks/common, and
weaveworks/build-tools

to their latest versions.

Thanks for the suggestion Bryan, just did it in 8f9b2a3.
I had a look at docker/docker too, and it seems we only use it for/in:
/proxy/tls.go:	"github.com/docker/docker/pkg/homedir"

I suggest moving Weave's use of mflag from weaveworks/docker to weaveworks/common, to match the change in runner.
Then we can remove weaveworks/docker entirely

was going to do this today, you beat me to it!

I just saw we also replaced:
"github.com/weaveworks/weave/common/mflagext"
with
"github.com/weaveworks/common/mflagext"
in build-tools, so I'll replace this in Weave Net as well, unless anyone has any objection.


refactor the examples

move the original examples into fit_a_line sub folder
add the ctr exampel
test=develop

Force merged, I'll fix the build issue on develop branch later.


Remove PR template

Describe your changes
The PR template feels like make-work, and I know that I for one have not been using it / finding it helpful.
I think it's good to prompt for self-review and testing but this checklist doesn't feel like the right way to do it.
WDYT @teesloane @sereprz

THIS IS WHAT WILL NO LONGER BE IN PRs:
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] If it is a core feature, I have added tests.
[ ] Are there other PRs or Issues that I should link to here?
[ ] Will this be part of a product update? If yes, please write one phrase
about this update in the description above.

I think that the purpose of a template is to encourage to be explicit about what the PR is for and track decisions so I'm pro some template over no template. I think the 3 of us agreed on this when we were working on stuff that wasn't getting reviewed always?
This feels like a very lightweight format to me (it's just a checklist? 🤷♀ ) - what would be a better way?

I see your point and I agree that being explicit about what a PR is for and tracking decisions is good. I will be totally honest "I have performed a self-review of my code" gives me a negative emotional reaction and makes me feel condescend to.
With that said, I don't think the checklist is serving it's purpose; I've looked through the past 10 merged PRs and

I have performed a self-review of my code - 8  checks
If it is a core feature, I have added tests. - 0 checks
Are there other PRs or Issues that I should link to here? - 3 checks
Will this be part of a product update? If yes, please write one phrase - 0 checks

The Are there other PRs or Issues that I should link to here? is covered by the comment in the description  so it's superfluous.  For example here's what I think is a good PR that only has the first item checked, even though it does reference the relevant issues, as in closes #346: https://github.com/bikebrigade/dispatch/pull/382 . Another thing I like about this PR is the screenshots, a practice I think should be encouraged, more on this later.
So of the 4 item checklist, one I feel called out by, one is already covered by a comment in the issue body, and two aren't used[^1]. That's why I feel getting rid of the checklist is good user-experience.
If we want to encourage PRs that aren't empty and linking to issues to facilitate decision tracking, we can leave the original top-level part / I also wouldn't be opposed to adding a nudge to add screenshots, e.g.
## Describe your changes

<!-- Please add a link to a ticket if relevant: eg: "closes #340" -->

## Screenshots
<!-- Only include screenshots if it's a user-facing change -->

[^1]: I do think we should encourage writing of tests! It just seems this checklist isn't doing it, and also it's unclear what a "core feature" is.


Release 12-12-23

fix filtering for mccc
change to using a boolean instead of math for setting crop.inactive
fix loading screen for explorer
remove unneeded logic for local variable in Filters
more error handling for returning No Data in data extractor

Left align cover crop names in the calendar view

Make cover crop name text black instead of light green

deleted unneeded json file

made drainage class unselectable
fix default crop sorting
simplify logic for reducing opacity in crops that aren't recommended, remove unneeded activeCropDataShadow variable, and delete CropDataRender.js
rename selectedCrops to selectedCropIds
rename activeCrops to activeCropIds
allow the user to proceed with no goals selected
add all goals to the calendar view instead of average goal rating
fix background of hessian fly free date
remove unneeded props from CropCalendarView.js and CropTable.js
rename CropTableListItem.js to RenderTableItems.js
rename pullCropData to updateCropData to match redux naming convention
simplify cropDataFormatter logic
updated infosheet to display the label if one exists
remove region data in user history.
solve a bug that select field would not get updated after click next and click back to return.
rename LocationComponent to Location.
reduce login modal padding on mobile
remove hessian fly free date from legend in NECCC
remove unneeded sfliters logic
combine soil and weather steps in the recommendation flow
fix crops being filtered by drainage class by default
replace next with View My List in the last step of the recommendation flow
remove weather editing
rename Cover Crop Council to Cover Crops Council
fix a bug with logos not changing

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.

Your review app has been deployed and is available at 'http://<IP_ADDRESS>:80'.Learn More about how to test and provide feedback for the app.


InsertModel and UpdateModel

Following up on #97 #94 #96
I have a rough idea:

to annotate the attributes of Entity's Model, where each attribute has three possible 'requirements': auto_identity (auto generated primary key), required (implied and thus can be omitted) and optional

from there, we can derive two more structs, InsertModel and UpdateModel
For InsertModel, auto_identity will be omitted, and required fields will be wrapped with RequiredValue, which must be Set. Optional fields will be wrapped with ActiveValue, which can be Set or Unset.
For UpdateModel, auto_identity will be wrapped with RequiredValue, while all other fields will be wrapped with ActiveValue (thus are optional)

change the Insert and Update API such that they accept IntoInsertModel and IntoUpdateModel respectively. ActiveModel can still be converted automatically into InsertModel and UpdateModel, but will panic if the 'requirements' mismatch

I like what you've desribed here... looks promising.
I think this could be related to: https://github.com/SeaQL/sea-orm/issues/105 - perhaps a refactor to the API can be considered.

After #105, I think it will provide us some compile-time info to work with, i.e. the default_value and default_expr tags.
As such, we'd be able to generate two extra models InsertModel, UpdateModel along with ActiveModel, under the following rules:
For insert model, skip the 'auto_increment primary_key' columns. Fields without default will be wrapped with RequiredValue, ActiveValue otherwise.
For update model, the 'primary_key' columns will be wrapped with RequiredValue while all other fields will be wrapped with ActiveValue

Btw... why we cant set an value for primary key with auto_increment?

It is possible to specify the primary key even if a primary key column is auto_increment, but I can't imagine many situations where that'd be useful to anyone.
I'm also thinking that the update and insert models can be used with async-graphql under a feature flag in the future, and you typically wouldn't allow the primary key to be set when inserting a new item. But for the async-graphql case, it could just add #[graphql(skip)] to the primary key on the insert model if it were to be kept.

Please also note all GENERATED ALWAYS columns should be excluded from insert/update queries or use DEFAULT as value. See for example Postgres or MySQL.

A generated column cannot be written to directly. In INSERT or UPDATE commands, a value cannot be specified for a generated column, but the keyword DEFAULT may be specified.

Maybe those could be directly excluded for InsertModel/UpdateModel ? In ActiveModel, maybe ActiveValue could be split into ReadableActiveValue + WritableActiveValue for these columns ?

Thanks @nicoulaj I think you raised a good point not yet considered.


Convert "unsafe extern "system" fn()" to "unsafe extern "C" fn()"

So the crate has a type pub type PFN_vkVoidFunction  = unsafe extern "system" fn(). The "system" part makes it incompatible with extern "C" for some reason, and so it is impossible to pass the returned value to any other function which expects it as an argument but as extern "C". Is it possible to change such types (mainly for get_instance_proc_addr and get_device_proc_addr) from system to C?

No, that would be incorrect. Vulkan on win32 uses the stdcall ABI, which is what extern "system" represents. You must not use extern "C" to represent Vulkan function pointers in portable code.

A brief search suggests bindgen supports specifying ABI just fine: https://github.com/rust-lang/rust-bindgen/pull/2329
If not, that's a bindgen problem; you shouldn't use an incorrect ABI definition. If you know you're on Linux where they're equivalent, you can cast the pointers.


horizontally keep in viewport

aligns menu to the right border of the element if it doesn't fit in viewport
horizontally

Hrmm...wouldn't it be better to keep it left aligned if it doesn't fit in the viewport? Then you could at least see the beginning of each option, rather than the end? This might be useful for a right-to-left implementation, though.

You are right, this is for the cases where there is space on the left of the select box, but the right part goes out of the viewport. I'll update the pull request making sure that when there's no space on the left to stay left aligned.


fix(iroh-net)!: DiscoveredDirectAddrs need to update the timestamp

Description
DiscoverdDirectAddrs has a timestamp of when it was last changed, which is used to decide if the direct addr information is recent enough to use in call-me-maybe messages.  However when it was updated this timestamp was not included in the comparison to see if there were changes, so that watchers would not get updates when the direct addresses did not change.  Unfortunately this meant the timestamp also never updated and the DiscoveredDirectAddrs was always considered out of date (unless there were changes in the discovered addresses).
This fixes this by putting only the DirectAddrs in the watcher.
It does a few other improvements:

Moves all logic about DiscoveredDirectAddrs into one place.  This could be split out to a module now if desired.

Tidies up the code which creates the DirectAddrs from the portmapper, netcheck and the local addresses.  Again this is just a first pass in cleaning up this code, there is so much more that could be done.

Breaking Changes

iroh_net::Endpoint::direct_addresses now returns a stream yielding Items of BTreeSet<DirectAddr> instead of Vec<DirectAddr>.
iroh_base::node_addr::NodeAddr::from_parts now takes a BTreeSet<DirectAddr> instead of Vec<DirectAddr>.

Notes & open questions
The crux of this fix is moving from Watchable<DiscoveredDirectAddresses> to DiscoveredDirectAddresses::addrs being Watchable<Vec<DirectAddr>> instead of the whole struct being watchable.
I could split the refactoring of store_direct_addr_update and the renaming of it's related functions into a separate PR in front of this bugfix if desired.  I had to change that code because of the format change from Vec<DirectAddrs> to BTreeSet<DirectAddr> and it was just way clearer doing it with the refactoring.
As indicated in the (already existing) comments that whole direct address updating logic can still be more refactored and improved.  But many small steps is how we improve.
I went very opinionated on the imports... apologies.
Change checklist

[x] Self-review.
[x] Documentation updates following the style guide, if relevant.
[x] Tests if relevant.
[x] All breaking changes documented.

About imports: We could/perhaps should add a .rustfmt.toml file configured to your personal import style. (Let's also talk about it with the team first ;) ) Specifically, there's the imports_granularity and group_imports settings.
edition = "2021"
imports_granularity = "Module"
group_imports = "StdExternalCrate"

I would love this! But they're not on stable rust.


g:startify_update_oldfiles = 1 should still skip empty v:oldfiles entries

With
let g:startify_update_oldfiles = 1
let g:startify_update_oldfiles= 1

:Startify causes in  [0] = last file (OK!) and [1] = dir of [0] (BAD!) because v:oldfiles[0] = ''.

Did you mean to paste two different options? :-)
At least with only g:startify_update_oldfiles = 1 I can't seem to reproduce it. (As in, empty entries actually get skipped.)

Oops, of course. Sorry for the wrong paste. Unsafe was meant.
Even though it's unsafe, at least empty entries should be skipped.

Hmm, actually empty entries get skipped already. But this only happens in the dir list (recent files in current directory), not in the files list (recent files), right?
The problem I see is that with unsafe set, even directories get added to the lists. This is the root problem, as they should contain files only. I can probably filter them by checking if the last character is a path separator.
Apart from that, directories are shown correctly -- except in one case! If the entry describe the current working directory.
This probably gets you an empty output:
:echo fnamemodify(getcwd . '/', ':.')

Do you agree with filtering all directories instead?

I agree. And, Yes, they are only shown in the upper half, 0-9, of the Startify screen.

So, is it still happening with the latest commit?

Works perfectly, Thanks!


Global TopicAttributes not being applied

Hi, I am trying to use Masstransit in a .Net Core web api with SQS/SNS to auto create fifo queues and subscribe them to fifo topics.
FIFO queues get created fine with ContentDeduplication enabled but when it comes to Topics I think there could be an issue.
Software versions:
MassTransit: 7.2.2
MassTransit.AmazonSQS 7.2.2
MassTransit.AspNetCore 7.2.2
MassTransit.Extensions.DependencyInjection 7.2.2
Microsoft.Extensions.DependencyInjection.Abstractions 5.0.0
I register MassTransit as follows

My Topic name formatter is:

In this example nothing actually gets created but when I remove the .fifo from the topic name then both the queue and the topic get created but the queue does not end up subscribing to the topic because the topic gets created as a standard topic and not a fifo topic.
My teams goal is to do all this automatically as manually adding the receive endpoints is not a viable option for us.

You need to try 7.2.3, it contained a number of FIFO fixes.

Yep every time I change something

Okay, I stand corrected, the attributes were not be added by the consumer configuration, only the publish configuration.
18:34:34.945-I Configured endpoint message-in-order.fifo, Consumer: MassTransit.AmazonSqsTransport.Tests.When_using_an_entity_name_formatter+MessageInOrderConsumer
18:34:35.058-D Starting bus: amazonsqs://localhost/
18:34:35.081-D Connect: https://localhost/
18:34:35.133-D Endpoint Ready: amazonsqs://localhost/ChrissMacPro_ReSharperTestRunner_bus_5o7yyy8mzd1fypkqbdc3gsenba?durable=false&autodelete=true
18:34:35.337-D Created topic MessageInOrder.fifo arn:aws:sns:us-east-1:000000000000:MessageInOrder.fifo
18:34:35.419-D Created queue message-in-order.fifo arn:aws:sqs:us-east-1:000000000000:message-in-order.fifo http://localhost:4566/000000000000/message-in-order.fifo
18:34:35.421-D Binding topic name: MessageInOrder.fifo, durable, attributes: ContentBasedDeduplication=True;FifoTopic=true, subscription-attributes: RawMessageDelivery=true to name: message-in-order.fifo, durable, attributes: FifoQueue=true;ContentBasedDeduplication=True
18:34:35.470-D Endpoint Ready: amazonsqs://localhost/message-in-order.fifo
18:34:35.471-I Bus started: amazonsqs://localhost/
18:34:35.521-D Created topic MessageInOrder.fifo arn:aws:sns:us-east-1:000000000000:MessageInOrder.fifo
18:34:35.637-D SEND amazonsqs://localhost/MessageInOrder.fifo?type=topic dc3a0000-ebb8-e450-b05e-08d9935902a2 MassTransit.AmazonSqsTransport.Tests.When_using_an_entity_name_formatter+MessageInOrder
18:34:35.771-D Stopping bus: amazonsqs://localhost/
18:34:35.775-D Endpoint Stopping: amazonsqs://localhost/message-in-order.fifo
18:34:35.776-D Stopping receive transport: amazonsqs://localhost/message-in-order.fifo
18:34:35.780-D Stopping consumer: amazonsqs://localhost/message-in-order.fifo
18:34:35.782-D Endpoint Stopping: amazonsqs://localhost/ChrissMacPro_ReSharperTestRunner_bus_5o7yyy8mzd1fypkqbdc3gsenba?durable=false&autodelete=true
18:34:35.782-D Stopping receive transport: amazonsqs://localhost/ChrissMacPro_ReSharperTestRunner_bus_5o7yyy8mzd1fypkqbdc3gsenba?durable=false&autodelete=true
18:34:35.783-D Stopping send transport: MessageInOrder.fifo
18:34:35.786-D RECEIVE amazonsqs://localhost/message-in-order.fifo dc3a0000-ebb8-e450-b05e-08d9935902a2 MassTransit.AmazonSqsTransport.Tests.When_using_an_entity_name_formatter+MessageInOrder MassTransit.AmazonSqsTransport.Tests.When_using_an_entity_name_formatter+MessageInOrderConsumer(00:00:00.0239500)
18:34:35.823-D Endpoint Completed: amazonsqs://localhost/message-in-order.fifo
18:34:35.832-D Consumer completed amazonsqs://localhost/message-in-order.fifo: 1 received, 1 concurrent
18:34:35.835-I Bus stopped: amazonsqs://localhost/


The download links of your pre-trained models are invalid now

the links are here:
https://drive.google.com/file/d/1vxqTda4MIYb1VDIA4NOokq7uCM4MW_1J/view?usp=sharing
https://drive.google.com/file/d/17F-wS4PwR6iz-Ubj0TaNsxNyMscgO3VV/view?usp=sharing
if possible, I hope you can update them.
Thanks in advance.

Hi @smileix
I linked them now to the huggingface.

ToD-BERT-mlm V1
ToD-BERT-jnt V1


RigiBody not colliding with negative gravity scale

Godot version:
3.2 beta 2
OS/device including version:
Ubuntu 18.04 (KDE Neon)
Issue description:
After setting a RigidBody's gravity scale to a negative value, it will not collide will other bodies when moving upwards.
However, I noticed that placing another physics body below it will stop it, as if the RigidBody was still, internally, falling down instead of going up.
Steps to reproduce:

Create a new scene
Add a RigidBody
Set its gravity scale to -1
Add a StaticBody above it
Test the scene; the RigidBody will go right through the StaticBody instead of being stopped by it

Minimal reproduction project:
gravity.zip

Set its gravity scale to -1

I think you get what you asked, a kind of wormhole physics :-P

Silly me, I didn't see that only my MeshInstance was above my ball. The StaticBody was actually below it... Nevermind this issue, I had this problem in another project but the issue must come from somewhere else


Regression in v0.6.0 when using an INSERT ... RETURNING clause with SQLite

Compiling a non-trivial INSERT query that contains a RETURNING clause results in long compile times, with very high memory consumption.
I've created an example repository which demonstrates the issue: jaehl/sqlx-bug
With v0.6.0 that project compiles on my machine in 100 seconds (and using 7GB of memory). With v0.5.13 it compiles in about 150 milliseconds.
First bad commit appears to be ed56622526298cd1df52338892dd5c6c9553b6d2 (more specifically it seems to be this commit from the PR: e5a5e36f6664878e0280ba6cd204be4bb7c1148a).

cc @tyrelr who worked on the refactors to SQLite, sounds like some unintentional exponential blowup.

I went ahead and gathered a perf profile and it looks like an overwhelming amount of time is spent in QueryPlanLogger::add_result(), specifically HashSet::insert():

And here's the output of EXPLAIN for that query in a Gist: https://gist.github.com/abonander/1e189216efb5941cf25824b6db2a9090

Thanks for the perf results.
The call to logger.add_result is hashing a Vec<(i64, String, i64, i64, i64, Vec)>, which is also cloned.  So that large struct acting as a hash-key is probably the root issue.
I see a few ways to improve performance of that:

use Vec instead of hashset (it should have no duplication anyways)
move the '.map()' conversion history indices into operations until output-time, to avoid clone-ing each operation for each distinct historical path to a ResultRow
check log-level before even making calls to the logger

I was hoping to use the logging to see how many end-to-end paths to ResultRow commands are found.  But, I haven't convinced cargo/sqlx-cli to show me the logs from running explain.  Hopefully I'll have some time to look closer on the weekend.

After playing with the code for a bit, this looks like a combination of a HUGE number of potential unique paths, exacerbating the inefficient logging code.
On my machine I can see these numbers when I run the reproducer:
0.5.7 --------------------------------------- real    0m0.333s
0.6.0 --------------------------------------- real    3m16.316s
(and against some local builds)
0.6.0 without the logging code -------------- real    1m5.493s
0.6.0 with 'merged' path detection & bail --- real    0m27.714s

I've run out of time for now, so haven't figured out how many execution paths were followed, nor measured the timing of combining the 2 approaches.

There was a fix PR opened in #1946 but I'm still waiting for response from the author.

As far as I can tell the fix is included in 0.7.0, should this be closed?

I can't reproduce the issue with 0.7.0, so it seems like this is fixed.


Customized the scroll bar

I customized the scroll bar in order to align it with the design of the website.
I contributed it under hacktoberfest'22.
Screenshots:

If there is any other change, I need to incorporate, kindly notify :)

Can it be tagged hacktoberfest-accepted? @Rick-mad-lab

Also this PR is linked with issue #13


internal/poll: ppc64le stuck waiting for semaphore

Note: I haven't finished debugging this, but discussing with @laboger, we thought it is important enough to raise an issue for the beta. This issue involves docker + go master (including 1.10beta1), and at the moment I'm thinking it's a go issue because it only occurs on ppc64le, and docker + main dependencies don't have much architecture specific code.
What version of Go are you using (go version)?
go1.10beta1
Does this issue reproduce with the latest release?
Yes beta, No 1.9.2
What operating system and processor architecture are you using (go env)?
Ubuntu 16.04 host, Debian:Stretch container
GOARCH="ppc64le"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_ppc64le"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build571013459=/tmp/go-build -gno-record-gcc-switches"
What did you do?
Testing upstream docker with go version 1.10beta1
Set GO_VERSION to go1.10beta1 in Dockerfile.ppc64le, and on ppc64le run
TESTFLAGS="-check.f DockerSuite.TestAttachClosedOnContainerStop" make test-integration
(This runs this specific test https://github.com/moby/moby/blob/d65ab869e8712d08fb94a5337b83df5d247bf25b/integration-cli/docker_cli_update_unix_test.go#L272)
What did you expect to see?
PASS
What did you see instead?
FAIL / panic (test timed out)
https://gist.github.com/tophj-ibm/4049252d8ad8227c8aad45598d08750a
The test, and a few other tests, get stuck at cmd.Wait(), waiting indefinitely for a semaphore.
We've narrowed the commit down to https://github.com/golang/go/commit/382d4928b8a758a91f06de9e6cb10b92bb882eff. But seeing as that is basically a check to make sure fd's are closed, makes me think there is an underlying issue somewhere with an fd not being closed correctly.
Again, I'm still trying to trace what is happening, but if you have any ideas, all help is appreciated.
All the go tests pass.

It's very unclear to me why anything around here would be ppc64le specific.  Does this test pass on other architectures?

There is a gorouting got stuck at this line, a pty.Read() call. pty is set to blocking mode by an (*os.File).Fd() call.
https://github.com/moby/moby/blob/d65ab869e8712d08fb94a5337b83df5d247bf25b/integration-cli/docker_cli_attach_unix_test.go#L54
https://github.com/kr/pty/blob/95d05c1eef33a45bd58676b6ce28d105839b8d0b/pty_linux.go#L35
An (*os.File).Read() call on a blocking mode file will block (*os.File).Close().
On Linux, I guess this can be fixed by adding syscall.SetNonblock(f.Fd(), true) at somewhere.
If the file is not opened by os.OpenFile, setting non-block won't help.
https://github.com/kr/pty/blob/95d05c1eef33a45bd58676b6ce28d105839b8d0b/pty_freebsd.go#L11
I encountered this before so I opened https://github.com/golang/go/issues/22939.

@crvv Thanks for the explanation.  I think I see the problem and I will send a CL.

I just tested the cl with commit c7a0e4b6ce and everything fails the same way. I should have mentioned that this test does pass on at least amd64, and I suspected go because we've had issues with syscalls being wrong in the past.

@tophj-ibm Thanks for trying it.  I think the CL is still a good one, and it comes with a test case that it fixes, but I don't know what is happening here.  Are you able to debug this further?

I'm still looking at it, yes.

just re-tested with both cls cherry-picked into 1.10beta1 and these fix the issue. thanks guys 🎉
I'm still going to look around because I'm not sure why the file would be blocking just on power and not on anything else, but I think it's safe to close this.


flow disappears from hugging face

I create a flow on langflow 1.0 preview and after a day the flow disappears from hugging face and I have to recreate it and re connect the api

where do I look this?

I have deployed it on Huggingface

where do I find this on Hugging face ?

HuggingFace common space is only meant as playground.
You might find useful the new free hosting cloud solution by DataStax. You can sign up here langflow.datastax.com


[#172] Add section for voting process to Wiki

#172
What happened 👀
Added a section to Home.md to define how we vote on RFC's
Proof Of Work 📹

@ryan-conway The step for "Verify newproject script" has failed
I think because there's a new update to the Kotlin library, it's causing the script to fail.
I'll make a fix asap 🚀

@ryan-conway I've created a pull request for the fix: https://github.com/nimblehq/android-templates/pull/238 🔨


Allow crafting upgrades to be used in the Interface to craft exported…

… items. fixes #158

Does it also work when you have multiple items set up for exporting?

Also, the crafting task scheduler has to be written to NBT

Ah! Not as easy as I thought! Digging...

You could set up an array of 9 crafting task schedulers, I think.

I am not sure of the best way to write the NBT tags with an array of CraftingTaskSchedulers. I think I should use a NBTTagList but I would have to create a different implementation of CraftingTaskSchedulare.writeToNBT because currently it expects to write to an NBTCompoundTag

Something like this:
NBTTagList l = new  NBTTagList();
for (int i = 0; i < 9; ++i)
{
   if (schedulers[i] == null) continue;
   NBTTagCompound t = new NBTTagCompound();
   t.setInteger("Id", i);
   NBTTagCompound x = new NBTTagCompound();
   schedulers[i].writeToNBT(x);
   t.setTag("Scheduler", x);
   l.appendTag(t);
}

Is the code at https://github.com/raoulvdberge/refinedstorage/blob/mc1.10/src/main/java/refinedstorage/apiimpl/autocrafting/CraftingTaskScheduler.java#L40 correct? It sets the scheduled item but should it not also call something like https://github.com/raoulvdberge/refinedstorage/blob/mc1.10/src/main/java/refinedstorage/apiimpl/autocrafting/CraftingTaskScheduler.java#L24 to actually request the crafting?

CraftingTaskScheduler doesn't need to handle calling addCraftingTask, the controller calls that already because it saves the crafting state.

I'll close this for now, since it is kinda tricky to implement indeed. Gonna try implementing this myself soon.

(Also, there are some bugs with the current CraftingTaskScheduler, I'll probably have to rework the craft on request system a bit)

Yea I couldn't get it to work! Sorry!
On Sat, Jul 30, 2016 at 1:16 PM, Raoul<EMAIL_ADDRESS>wrote:

(Also, there are some bugs with the current CraftingTaskScheduler, I'll
probably have to rework the craft on request system a bit)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/raoulvdberge/refinedstorage/pull/159#issuecomment-236362221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH8JLaKevyX_5Fl_aRfZFK9AHwqTSt9ks5qa0C3gaJpZM4JFNB-
.

No problem & no need to excuse yourself, guess what, I couldn't get it to work myself :P


Add a simple C formatter

This formatter outputs failures in a similar fashion to the C compiler
— file:line:message — allowing straightforward integration with text
editors like vim and without adding extra dependencies to the project
(relying on the quickfix-window from vim or simlar feature for other
editors).
One can configure his editor with the following line (vim) and start
jumping between failures using the regular editor keybindings, without
having to visualy parse the output from rspec to find out the file and
line number he want to reach:
autocmd FileType ruby set makeprg=bundle\ exec\ rspec\ --format\ c

Thoughts @samphippen ?

I am in favor of this :)

I like this idea but I'm wondering if it should be third party as opposed to in core?
having quickfix output from RSpec is great though. Not sure about the name c formatter.

having quickfix output from RSpec is great though. Not sure about the name c formatter.

Yeah, this was spotted by @JonRowe, I fixed the code but forgot to update the issue title accordingly.  It's now done :wink:


Implementing a better Navbar UI for Mobile screen device

Figma Design

I want to add this figma design to your website, which will give users mobile app like experience on your web
Please assign this issue to me, Under @GSSOC2023

Navbar is responsive on mobile screens for some pages, although it'll be the same on all pages soon.


Advanced nginx configuration: Extra security & performance tuning.

Advanced configuration for nginx
There are some small changes you can make to make your website faster, and a little more secure.
Security enhancements
The original configuration will keep you safe, but it is always good to see what else can be done.
Giving less information to attackers
By default, the nginx.conf will return "403 Forbidden" errors for system files that are not supposed to be accessed directly.
However, there's a good alternative, like so:
server {
    ...

    ## Begin - Index
    # for subfolders, simply adjust:
    # `location /subfolder {`
    # and the rewrite to use `/subfolder/index.php`
    location / {
        try_files $uri $uri/ @index;
    }

    location @index {
        internal;
        try_files = /index.php?_url=$uri&$query_string;
    }
    ## End - Index

    ## Begin - Security
    # set error handler for these to the @index location
    error_page 418 = @index;
    # deny all direct access for these folders
    location ~* /(\.git|cache|bin|logs|backup|tests)/.*$ { return 418; }
    # deny running scripts inside core system folders
    location ~* /(system|vendor)/.*\.(txt|xml|md|html|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 418; }
    # deny running scripts inside user folder
    location ~* /user/.*\.(txt|md|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 418; }
    # deny access to specific files in the root folder
    location ~ /(LICENSE\.txt|composer\.lock|composer\.json|nginx\.conf|web\.config|htaccess\.txt|\.htaccess) { return 418; }
    ## End - Security
    ...
}

What happens here is the following:

Try and see if the file exists on disk, and if not, give the request to the @index location.
The new @index location will reroute requests to the /index.php as usual.
Instead of returning a "403 Forbidden" error, we now return a 418.
Because we set the error_page 418, any 418 will be handled by the @index location.
Grav's /index.php will pick up the route it is given, determine if there's a matching route,
and if not, simply return a 404 by itself.

Normally, we route all non-existing files to Grav. However, returning any status code from nginx itself, will give a different
kind of error than if it had been routed through Grav. That gives the attacker the information that those files are special
and actually exist. More than that, that you explicitly don't want them to try and read those. They will try harder.
This is better, because if you reroute it to Grav, Grav will handle it like any other non-existing file.
No direct access to other .php-files
In the example nginx.conf, all requests to files ending in .php are sent to the PHP-handler. This is not necessary, as Grav
only uses the /index.php to route requests. Every other location is handled internally.
Some vulnerabilities in CMS's are targeted specifically at plug-ins, themes or other third-party libraries. There is no reason
to keep direct access to them open (unless you run Grav combined with other pieces of software in the same webroot!).
So, alternatively, only route /index.php to the PHP-handler, and block the rest! Like so:
server {
    ...
    ## Begin - PHP
    location = /index.php {
        # Choose either a socket or TCP/IP address
        fastcgi_pass unix:/var/run/php7.0-fpm.sock;
        # fastcgi_pass <IP_ADDRESS>:9000;

        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }
    ## End - PHP

    ## Begin - Security
    ...
    # deny access to other .php-scripts
    location ~ \.php$ { return 418; }
    ...
    ## End - Security
    ...
}

With this, any .php-file that is not /index.php, will be rerouted to and be handled by /index.php.
Performance
nginx is a very capable webserver, but it is also very capable of doing advanced caching.
Do not check for the existence of directories
Many, many examples use this line:
try_files $uri $uri/ @index;

Few people actually realise that it does, which is:

Check for the existence of the file.
If it does not exist, try and see if there's a directory with that name.
Otherwise, fall back to @index (/index.php).

But, in reality, you only really use $uri/ (step 2) if you really are linking to a directory that will have its own index.php
or index.html. Considering you're using Grav, you will only go to /, and that already goes to /index.php in step 3.
If you're not going to use it, don't keep it around, and you will take out an extra filesystem stat():
try_files $uri @index;

Caching filesystem metadata of files
The open file cache caches metadata about files. If they exist or not, what file permissions they have, if they are readable or not..
This can help a little on local filesystems, especially that are not on SSD. It shines more in environments with network storage.
Keep in mind that this goes outside of the server{}-block, directly into the http{}-context:
open_file_cache                 max=10000 inactive=5m;
open_file_cache_valid           1m;
open_file_cache_min_uses        1;
open_file_cache_errors          on;

server {
    ...
}

In this example, we told nginx to:

Keep a maximum of 10k entries.
Delete metadata of a file from the cache if they it is not used for 5 minutes.
Refresh the metadata it has every minute.
Put the metadata of a file in the cache immediately upon accessing it the first time.
Cache errors like "Permission denied", "Not found", as well.

Precompressing resources
In the example nginx.conf, we enable GZip-compression. While excellent, it also means that the output is compressed on a per-request basis.
This in turn means that with every request, it adds extra CPU-cycles and latency (you have to wait or the compression to be done).
There is an alternative in nginx, which is gzip_static. gzip_static will make nginx look for the same file, but with a .gz extension.
So if I have main.css, it will try and see if there is already a main.css.gz present, and send that instead.
Best way to use this To enable this, use:
server {
    ...

    ## Begin - Index
    ...

    location / {
        try_files $uri @index;

        location /assets {
            gzip_static on;
        }
    }

    ...
    ## End - Index
    ...
}

By using a nested location /assets, you will not incur extra filesystem stat()s for the rest of Grav.
If enabled, the /assets location will contain pipelined/minified assets.
!! nginx does not automatically compress the files for you. You will have to do this yourself.
To compress the files (on UNIX-based systems), you can do the following:
cd assets
for asset in *.css *.js; do gzip -kN9 "$asset"; done

Note that these are automatically deleted when you clear your (asset) cache, and you will have to redo it after new resource files are created.
There is an outstanding Pull Request to allow automatic precompression of assets upon creation of these files.
FastCGI caching for basic/static "grav"-sites.
!! ONLY USE THIS FOR COMPLETELY STATIC SITES! Do not use this if you make use of the Admin-panel or have any other dynamic part (especially content behind any form of authentication).
nginx has caching for FastCGI. In the example below, we will leverage this. Note that if anything on the site sets a cookie or similar dynamic content headers, the cache is invalid and will not be used at all.
First, define a cache zone in the main http{}-context of your nginx.conf (in other words: not in the server{}-section:
fastcgi_cache_path      /path/to/cache/on/disk          levels=1:2
                        keys_zone=fastcgi:10m           max_size=200m
                        inactive=1440m                  use_temp_path=off;

server {
    ...
}

You should change the path of where the cache is stored on disk, but what it does is:

Set the path. You can use this to cache on disks that might be faster. (Tip: Use /dev/shm/something on Linux systems to use a RAM-disk instead!).
Define the directory hierarchy structure of 1 character, then 2 characters. (i.e. /path/to/cache/on/disk/c/29/...)
Give the cache zone a name ("fastcgi" here) and an initial size (10 MB).
Allow a maximum of 200 MB to be cached.
Delete a resource from the cache if it hasn't been used for 24 hours.
Do not base the cache path off of fastcgi_temp_path.

Next, you can use this cache zone in your configuration:
server {
    ...
    ## Begin - PHP
    location = /index.php {
        ## Begin - FastCGI caching
        fastcgi_cache           fastcgi;
        fastcgi_cache_key       "$scheme$request_method$host$request_uri";
        fastcgi_cache_valid     200 30m;
        fastcgi_cache_valid     404 5m;
        fastcgi_cache_valid     any 1m;
        fastcgi_cache_use_stale error
                                timeout
                                updating
                                http_429
                                http_500
                                http_503;

        fastcgi_cache_background_update on;
        ## End - FastCGI caching

        # Choose either a socket or TCP/IP address
        fastcgi_pass unix:/var/run/php7.0-fpm.sock;
        # fastcgi_pass <IP_ADDRESS>:9000;

        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }
    ## End - PHP
}

Now, what is happening here, is the following:

The cache zone named "fastcgi" will be used for this (we defined that earlier).
The cache key to lookup a cached resource is set to something like "httpsGETwww.example.com/".
Cache times:

200 "OK"-responses: 30 minutes.
404 "Not Found"-responses: 5 minutes.
Any other status code: 1 minute.

Keep serving our cache when the following happens:

There is an error.
There is a timeout.
nginx is busy updating the cache.
There is a 429 Too Many Requests on the backend (backend is too busy).
There is a 500 Internal Server Error on the backend (backend has a misconfiguration).
There is a 503 Gateway Timeout to the backend (backend has other problems).

And last but not least: Upgrade the cache in the background, don't make our clients wait.

Please note, once again, that this will not (and should not) work if you're using the Admin panel, or use any other sessions on your site.
It is not recommended to use this caching with any authenticated content, for security reasons.
If you wish to test if your cache is working, you can add a simple header (remove on production):
add_header X-Cache $upstream_cache_status;

You can view the header with cURL (or any other tool):
$ curl -I https://www.example.com/
...
X-Cache: MISS
...
$ curl -I https://www.example.com/
...
X-Cache: HIT
...
$

Again, you might want to disable the header again after confirming it is done.
If you feel the need to purge your cache entirely:

Stop nginx.
Remove the directory.
Start ngnix.

The cache is automatically updated and pruned in the background, so you shouldn't need to do so.

I'm still trying to write up a configuration for sites that are more dynamic (authenticated content) that I'm happy with. I have something, and it works well, but only if you know extremely well what you're doing, so I don't feel it's safe enough for general use.
Pretty much all of the stuff above can be incorporated (preferably commented out) in the standard webserver-configs/nginx.conf config. Another idea is to review my post above and adapt it for Learn.

This should also be integrated as a sub-page of https://learn.getgrav.org/security/server-side.

yah please consider a PR to add it to learn docs.  I think it might make more sense under the existing nginx page. https://learn.getgrav.org/webservers-hosting/local/nginx

Ok. I've updated the original post to add caching for authenticated content and disabling cache for admin users and the admin panel. I will look into incorporating it into Learn and/or the default nginx.conf.

Thank you @Eihrister for sharing this information. 👍

Thank you again @Eihrister for this great guide. I sat down this morning with my first real live Grav Site and the following config and it's working like an absolute charm.
map $http_cookie $sessionkey {
    default '';
    ~grav-site-(?<hash>[0-9a-f]+)=(?<sessionid>[^\;]+) $hash$sessionid;
}

# This is used by fastcgi_cache_bypass and fastcgi_no_cache.
# If you don't want certain URI's cached, add them here with a value of 1.
map $request_uri $no_cache1 {
        default                 0;
        ~^/(../|)admin          1;
}

# This is used by fastcgi_cache_bypass and fastcgi_no_cache.
# To disable caching based on cookie names, add them here with a value of 1.
map $http_cookie $no_cache2 {
    default 0;
    ~grav-site-([0-9a-f]+)-admin=([^\;]+) 1;
}

open_file_cache                 max=10000 inactive=5m;
open_file_cache_valid           1m;
open_file_cache_min_uses        1;
open_file_cache_errors          on;

server {
    listen *:443 ssl http2;
    listen [::]:443 ssl http2;
    index index.php;

    ## Begin - Server Info
	............
	## End - Server Info

	# Begin - SSL Configuration
	............
	# End - SSL Configuration

    ## Begin - Index

    location / {
        try_files $uri @index;

	location /assets {
            gzip_static on;
        	}
		}

    location @index {
        try_files = /index.php?_url=$uri&$query_string;
    }

	## End - Index

    ## Begin - Security
    # set error handler for these to the @index location
    error_page 418 = @index;
    # deny all direct access for these folders
    location ~* /(\.git|cache|bin|logs|backup|tests)/.*$ { return 418; }
    # deny running scripts inside core system folders
    location ~* /(system|vendor)/.*\.(txt|xml|md|html|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 418; }
    # deny running scripts inside user folder
    location ~* /user/.*\.(txt|md|yaml|yml|php|pl|py|cgi|twig|sh|bat)$ { return 418; }
    # deny access to specific files in the root folder
    location ~ /(LICENSE\.txt|composer\.lock|composer\.json|nginx\.conf|web\.config|htaccess\.txt|\.htaccess) { return 418; }
    ## End - Security

    ## Begin - PHP
    location = /index.php {

        ## Begin - FastCGI caching

        fastcgi_cache_bypass $no_cache1 $no_cache2;
        fastcgi_no_cache     $no_cache1 $no_cache2;
		fastcgi_cache           MYCACHENAME;
        fastcgi_cache_key       "$scheme$request_method$host$request_uri$sessionkey";
        fastcgi_cache_valid     200 30m;
        fastcgi_cache_valid     404 5m;
        fastcgi_cache_valid     any 1m;
        fastcgi_ignore_headers  "Cache-Control"
                                "Expires"
                                "Set-Cookie";

        fastcgi_cache_use_stale error
                                timeout
                                updating
                                http_429
                                http_500
                                http_503;

        fastcgi_cache_background_update on;

        ## End - FastCGI caching

		fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root/$fastcgi_script_name;

		# Choose either a socket or TCP/IP address
		fastcgi_pass unix:/run/php/php7.0-fpm.sock;
        }

    ## Begin PHP Security
    # deny access to other .php-scripts

    location ~ \.php$ {
    	return 418;
    	}

    ## End PHP Security

    location ~ /purge(/.*) {
        fastcgi_cache_purge MYCACHENAME "$scheme$request_method$host$1";
    }

Is anyone aware of progress on the precompression pull request (https://github.com/getgrav/grav/pull/1621)?

Everyone using this wonders why their server is a teapot all the time.


#3411 Making a user-defined column reference another user-defined column

Description
Currently supported, but some errors exist. In the process of deleting unused user-defined columns for performance, there is a situation that cannot be processed. Druid removes unused columns during query optimization, so modify to include all user-defined columns in the query.
Related Issue :
https://github.com/metatron-app/metatron-discovery/issues/3411
How Has This Been Tested?
https://github.com/metatron-app/metatron-discovery/issues/3411
Need additional checks?
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional Context

deploy to 1


Linear interpolation for the game screen

It is possible to get rid of picture smoothing with video mirroring onto a preconfigured canvas (image-rendering: pixelated).
Could be helpful in the future for some client display scaling modes (integer scaling, smoothed, etc.)
Comparison
Despite transcoding artifacts, it has the nearest-neighbor scaling on the left and the default bilinear filter on the right. The original size of the game frame is 256x240 and it was scaled with an x2 factor in the browser.
https://user-images.githubusercontent.com/846874/104768637-0c138100-577f-11eb-9935-742cf96e1d4e.mov

"video mirroring onto a preconfigured canvas":  Do you mean there is a CSS option for scaling on front-end right (both nearest neighbor and billinear is supported)
?

"video mirroring onto a preconfigured canvas":  Do you mean there is a CSS option for scaling on front-end right (both nearest neighbor and billinear is supported)
?

It's working like that. Yes, right now I could find just 2.5 options for CSS scaling.
The problem is that by default HTML5  element uses a bilinear filter when the video container is being stretched and there is no option to change it there. If we would want to use Nearest algo on the server in that case it would be not-blurred just for the original game frame size. You might say Nearest Neighbor is a trash algo anyway with all these jitterings, jagged edges (going back to Earthbound scaling example issues (:) but in the form of Integer scaling it's very pleasant, compared to blur.

It's working like that. Yes, right now I could find just 2.5 options for CSS scaling.
The problem is that by default HTML5  element uses a bilinear filter when the video container is being stretched and there is no option to change it there. If we would want to use Nearest algo on the server in that case it would be not-blurred just for the original game frame size. You might say Nearest Neighbor is a trash algo anyway with all these jitterings, jagged edges (going back to Earthbound scaling example issues (:) but in the form of Integer scaling it's very pleasant, compared to blur.

It's working like that. Yes, right now I could find just 2.5 options for CSS scaling.
The problem is that by default HTML5  element uses a bilinear filter when the video container is being stretched and there is no option to change it there. If we would want to use Nearest algo on the server in that case it would be not-blurred just for the original game frame size. You might say Nearest Neighbor is a trash algo anyway with all these jitterings, jagged edges (going back to Earthbound scaling example issues (:) but in the form of Integer scaling it's very pleasant, compared to blur.

It's working like that. Yes, right now I could find just 2.5 options for CSS scaling.
The problem is that by default HTML5  element uses a bilinear filter when the video container is being stretched and there is no option to change it there. If we would want to use Nearest algo on the server in that case it would be not-blurred just for the original game frame size. You might say Nearest Neighbor is a trash algo anyway with all these jitterings, jagged edges (going back to Earthbound scaling example issues (:) but in the form of Integer scaling it's very pleasant, compared to blur.

he, so life is easy. Just scale down everything before scale-up. Have you tested the optimal screen size to have ~30FPS?

he, so life is easy. Just scale down everything before scale-up. Have you tested the optimal screen size to have ~30FPS?

he, so life is easy. Just scale down everything before scale-up. Have you tested the optimal screen size to have ~30FPS?

I must say, it won't work for um... graphic-intensive consoles, starting from N64 and beyond. For primitive graphics and a limited color palette, we can scale-down it quite a lot and restretch it wherever.
I've not tested performance, first, we need a deterministic reproducible environment or a baseline system config. Since everything is CPU driven it will be CPU+RAM. Something like lo, med, hi Amazon instances.
As is, I can get 60 fps in any not 3D emulator with default frame size x2, up until N64 where I have to scale it down from defaults times two (:

he, so life is easy. Just scale down everything before scale-up. Have you tested the optimal screen size to have ~30FPS?

I must say, it won't work for um... graphic-intensive consoles, starting from N64 and beyond. For primitive graphics and a limited color palette, we can scale-down it quite a lot and restretch it wherever.
I've not tested performance, first, we need a deterministic reproducible environment or a baseline system config. Since everything is CPU driven it will be CPU+RAM. Something like lo, med, hi Amazon instances.
As is, I can get 60 fps in any not 3D emulator with default frame size x2, up until N64 where I have to scale it down from defaults times two (:

One more thing I'm planning to try in the future is an AI-based upscale like Nvidia DLSS. When we have a proper GStreamer AV pipeline because it's a pain to do manually ((post-)processing queue).

One more thing I'm planning to try in the future is an AI-based upscale like Nvidia DLSS. When we have a proper GStreamer AV pipeline because it's a pain to do manually ((post-)processing queue).

Yes, we haven't push the project to the limit that we can apply GPU for streaming.
The AI-based upscale is mentioned a lot of time, it's the future of video call as well. I just don't know if it's really possible, the upscale AI model has to perform at around 100fps on front-end. I'm really curious and would like to know your experiment result as well .

Yes, we haven't push the project to the limit that we can apply GPU for streaming.
The AI-based upscale is mentioned a lot of time, it's the future of video call as well. I just don't know if it's really possible, the upscale AI model has to perform at around 100fps on front-end. I'm really curious and would like to know your experiment result as well .

ah. When you mention: "proper GStreamer AV pipeline", what will be the change in our infrastructure to achieve that?

ah. When you mention: "proper GStreamer AV pipeline", what will be the change in our infrastructure to achieve that?

I don't know yet, how it works with Go. First I would integrate AV-encoders instead of existing C-wrappers which requires no changes to our infrastructure. It's something like a push-poll on the pipeline.

I don't know yet, how it works with Go. First I would integrate AV-encoders instead of existing C-wrappers which requires no changes to our infrastructure. It's something like a push-poll on the pipeline.


Chapter 13 : §3.* missing corresponding handbook

Hello,
I am using the French version of the book (ISBN 978-2-10-079006-1), and it seems that chapter 13 (i.e. chapter 5) differs from the original version (at least the notebook), as :

There is no reference to the Standardization class in the notebook(except in the exercise solution)
The one-hot encoding is not implemented the same way (tf.lookup.StaticVocabularyTable in the book, and tf.feature_column.categorical_column_with_vocabulary_list and tf.feature_column.indicator_column in the handbook),
Moreover, bucketization, hash_bucket, numeric_column is not included/explained in the french version

In fact,

the whole tf.feature_column part is not explained in the french version of the book (even if the code is easily understandable),
the use of tf.one_hot and tf.lookup, in the notebook, is only seen in the exercise solutions (added recently : link) but clearly explained in the french book,
and finally, the usage of tf.nn.embedding_lookup seems to be mentionned only in the French book.

Is it a mistake ? or maybe it is the same for the original book ? or some of these differences are on purpose ? the tf.feature_column shall be now forgotten in favor of tf.lookup ?
Note : I am still in the process of reading the chapter 13 (5) so far, so I may be misunderstanding and/or there may be other differences within this chapter.
Edit : I did not have to workaround the "import tensorflow.train" bug, it worked well for me

Ok, I had not read the beginning of 13.3.3 (5.3.3), nevermind. I suggest that you should include the same comment as in the book in the handbook at cell 85, precising that Feature Column API may be replaced by the new API (lookup, one_hot). This would avoid other reactions like mine.
So far, only the TextVectorization Layer seems to be still experimental (i did not manage to include it in my model, got an AttributeError).

Thanks for your feedback @lebaste77 👍 , I'll add a note in the notebook. I hope you're enjoying the rest of the book.


Closed change requests not showing on front end

Looks like work needed to get and show complete CRs

Should be sorted now


How to change Bing Maps language/culture/market

I've tried culture parameter below but the map always stays English. Please help.
L.BingLayer = L.TileLayer.extend({
options: {
subdomains: [0, 1, 2, 3],
type: 'Aerial',
attribution: 'Bing',
culture: 'zh-Hans'
},

Found out zh-Hans is not support for Imagery based on https://msdn.microsoft.com/en-us/library/hh441729.aspx table.


[DAG] Add python sdk tests in CI

https://github.com/filecoin-project/bacalhau/pull/1616

Fixed byy https://github.com/filecoin-project/bacalhau/pull/1519


fix: ref function for duckdb in encapsulated adapter

What happend if not?

Couldn't find the table


Added P4_16 code for P4-NetFPGA

Hi @ralfkundel , thank you for this great contribution! Before I can merge this we need to make sure you have a CLA signed with ONF. Have you ever committed code to other ONF-managed repositories? If so, which one? If not, we need to find a way for you to sign such CLA. We usually do this trough Gerrit, but this repo is not hosted on Gerrit. I'm working with the ONF IT team to figure out a way to plug automated CLA management on Github-managed repos, but this might take some time...

Wil close this PR and re-open to trigger CLA validation


How to identify trips in GT06n?

Hi, I am trying to work with GT06n based device. Requirement is to create Trips. I need a unique identifier which I can get from device data so that I can use it to create Trips. Please let me know if any such thing is there.

As far as I know, gt06n doesn't provide such info, neither traccar.
You've to manage it by yourself.  So you can traverse the array and calculate trip distance, duration, avg speed, max speed, etc.

I never heard of any device that provides unique ids for trips.

Actually @tananaev, I had also work on Castel protocol. There I got "acc_on" attribute which is constant for each Trip. That is why I am trying to find something similar in this GT06n protocol. But as @slachtar said, I will have to manage Trips by myself. Anyways thanks for responding.

You are basically talking about ignition value. It is available for many protocols. But I don't think you can call it an identifier.


national Korea Maritime&Ocean University

Please add the national Korea Maritime University
kmou.txt
This is the URL of our school : https://www.kmou.ac.kr/kmou/main.do
But my school uses Google's gmail, so the domain gets "g"
domain: @g.kmou.ac.kr

@leesg912 lib/domain/kr/ac/kmou/g.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@leesg912 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

@leesg912 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

@leesg912 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

@leesg912 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

@leesg912 The domain is already in the repository. I am closing the request.


Some things Breeze beta

Win7 64 bit

Give the create new wallet page same layout als first startup screen. Breeze logo top middle, text starting right under it.
Create, Restore buttons next to each other with same styling (perhaps other colors). Create button first, then restore button.
Back button under these two buttons.

Same for next page when you can give the wallet name, password ect. Breeze logo on top. Back button same styling as previous page on bottom of the page.

When creating the wallet the 'create' button dissapears and the 'red' icon is shown. Maybe better to display some text also: 'Please be patient while creating your wallet etc...'

Wallet info after wallet is created is says you can recover with wallet creation time. But where can this creation time be seen??

Wallet shows text 'save image' when hovering over strat or BTC logo.

Newly created wallet with balance of 0 trying to send gives message 'no spendable transactions found on account account 0', I assume the last should be the wallet name instead of 'account 0'

Style the 'cancel' button in the send screen just like the rest (rounded with a color).

Style the 'cancel' button in het logout screen just like the rest (rounded with a color).

When sending TBTC al my balance goes to unconfirmed. When sending Tstrat only the amount I am sending goes to unconfirmed. Is this correct?

Good feedback, but splitting out into individual issues might be better

thanks for the feedbacks. Some are already mentioned by others on the Github issues 👍

Hi,
Look bellow how the Github suggestion is made :
capture d ecran 2017-10-24 a 15 29 43
Left button is for cancelling the process. This is not the main suggested action from Github.
Right side has the main button or "call to action" with a different styling and it's on the same side as breeze wallet.
It is my assumption that breeze does not have a  cancel and back button, but cancel and back link. It does not look like a button. On the first screen to create the wallet the back button is now above the text, this looks strange to me.. Why not at the bottom and make it a real button?
But could also be a question of what someone prefers... Those cancel and back links look cheap in my opinion and not consequent..

Newly created wallet with balance of 0 trying to send gives message 'no spendable transactions found on account account 0', I assume the last should be the wallet name instead of 'account 0'

has been fixed in https://github.com/stratisproject/StratisBitcoinFullNode/pull/640


[Bug]: Missing explanation

Summary
The paragraph in section https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations states "There are two problems with this code.", but only addresses one problem and never gets to explain what the second problem was.
Page
https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations
Details
No response

Hello @smith558, thanks for reporting!
The second issue is actually written just below the paragraph with the first one, and it's starting with

Even if it weren’t slow, as your code evolves, you will run into cases where the “chain” you wrote doesn’t fit the new requirements.

I agree it would be more readable if started with "Second issue is that, even if (...)", etc.


ES6 Syntax

Can we get support for ES6 syntax in Visual Studio, please?
With transpilers like Babel allowing us to safely and powerfully develop using the syntax right now, VS seriously lacks the support to match.
See here for a full list but, in my opinion, features most likely to improve a developers efficiency (ordered in descending impact) are:

[ ] Object / array destructuring
[ ] Object literal shorthand notation
[x] Generator functions
[ ] Arrow functions
[ ] for..of loops
[ ] Module definitions: export default / export var
[ ] Module usage: import xyz from 'xyz' / import { abc } from 'xyz'

I'm only asking for syntax not intellisense -- just highlight correctly and don't show red squiggles

I would really appreciate ES6 support too, intellisense included. Thanks for the great work.

The best place for feature request for VS is http://visualstudio.uservoice.com/. There is an open feature request for ES6 Modules http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/7017377-support-for-es6-modules. Please open this where they are actually counting the votes.
It's a shame that Microsoft JSLS and the underlying JS AST (unlike AST for CSS, Less, Sass) classes are all internal, even in VS2015! which means that third party extensions cannot extend on MS-JSLS to augment VS JS capabilities. Some people were asking for it on Twitter and GitHub since last year, but it didn't happen in VS2015. Having JSLS reusable will probably make VS the best tool for JavaScript in market, with third-party extensions bringing the feature-set up to the speed and adding more fascinating features/enhancements.
@mousetraps, IMO this issue should be closed here as the support to ES6 VS is not confine to v8/node.js.
@RamIdeas, please share the uservoice links here once you lodge feature request(s) there (preferably keep those as separate features like you did here)., so we can upvote it there. :)

@jasonwilliams200OK Thanks for your input, but this actually does belong here as well.
We used to use JSLS (it is extensible btw) and still do for client-side code (switch the "build action" to "content" instead of "compile"). JSLS was nice and accurate, but the problem was that it works by executing your code, which simply did not scale well to the large node projects that people were working with.
So sometime after Beta 1, we replaced JSLS with our own homegrown static analysis engine for Node.js code. The unfortunate side effect of this is that we cannot simply piggyback on JSLS for any new features. The fortunate side effect of this is that NTVS is open-source, and we're happy to accept contributions. :wink:
FWIW we do plan on prioritizing ES6, but it's a lot of work for our small core team so thanks in advance for your patience. Here's a little more info on ES6 support so far, including when you can expect to see squigglies.

In the meantime is there a way of getting Visual Studio (2015 RC) to run my node.js code? Currently, it fails the "build" and opens up the error list (after asking if I would like to run from the last successful build).
I moved to Sublime Text to write all my code but the debugger would really help right now -- console.logs create a very slow iteration cycle.

This feature is currently available if you switch on the new ES6 IntelliSense Preview mode, available in the latest NTVS release. Please check it out and file issues as you run into them!


chargingstatus: also buzz on disconnect from charging

This buzzes after a slight delay, to allow other "charging" handlers to run and not interrupt the buzz.

Yes, please. It is way too easy to connect charger badly, where it disconnects immediately after connecting.

Thanks - yes that's my thinking exactly, nice to hear if the connection becomes unplugged

Thanks!