how does output to /dev/null work

Checklist

[X] I'm asking a question and not reporting a bug/feature request
[X] I've looked through the README
[X] I've read the guidelines for opening an issue
[X] I've searched the bugtracker for similar questions including closed ones

Question
Hi.
Is -o '/dev/null'a  valid argument on linux? If I recollect right, it was not letting a video to be saved on a file system, but a few linux distro updates later I have tried it again and it either gives the [Errno 22] or do save a video renaming it to null.ytdl and null.webm for other videos.
Is this new supposed behavior or is it due to an external change?
Verbose log
[debug] Command-line config: ['https://www.youtube.com/watch?v=ZavwtJxmqJI', '-f', '299', '-o', '/dev/null', '-Uv']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.05.18 [b14d52355]
[debug] Python version 3.10.4 (CPython 64bit) - Linux-5.17.9-1-MANJARO-x86_64-with-glibc2.35
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: ffmpeg -bsfs
[debug] exe versions: ffmpeg 5.0 (setts), ffprobe 5.0, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.12.0, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
Latest version: 2022.05.18, Current version: 2022.05.18
yt-dlp is up to date (2022.05.18)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=ZavwtJxmqJI
[youtube] ZavwtJxmqJI: Downloading webpage
[youtube] ZavwtJxmqJI: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
ERROR: [youtube] ZavwtJxmqJI: Requested format is not available. Use --list-formats for a list of available formats
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1395, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1479, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1535, in process_ie_result
    ie_result = self.process_video_result(ie_result, download=download)
  File "/usr/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 2622, in process_video_result
    raise ExtractorError(
yt_dlp.utils.ExtractorError: [youtube] ZavwtJxmqJI: Requested format is not available. Use --list-formats for a list of available formats

The log doesn't match the description!

yeah, my bad. sorry
[debug] Command-line config: ['https://www.youtube.com/watch?v=hA55WshsKvg', '-f', '299', '-o', '/dev/null', '-Uv']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.05.18 [b14d52355]
[debug] Python version 3.10.4 (CPython 64bit) - Linux-5.17.9-1-MANJARO-x86_64-with-glibc2.35
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: ffmpeg -bsfs
[debug] exe versions: ffmpeg 5.0 (setts), ffprobe 5.0, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.12.0, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
Latest version: 2022.05.18, Current version: 2022.05.18
yt-dlp is up to date (2022.05.18)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=hA55WshsKvg
[youtube] hA55WshsKvg: Downloading webpage
[youtube] hA55WshsKvg: Downloading android player API JSON
[youtube] hA55WshsKvg: Downloading player 7eff7529
[debug] Saving youtube-nsig.7eff7529 to cache
[debug] [youtube] Decrypted nsig yPRtpC8ZiSFYSZPf => tmGPPiOjLH0kGw
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[info] hA55WshsKvg: Downloading 1 format(s): 299
[debug] Invoking http downloader on "https://rr1---sn-xguxaxjvh-8v1s.googlevideo.com/videoplayback?expire=1654255067&ei=e5mZYrTmHcbi7QSiirKACQ&ip=<IP_ADDRESS>&id=o-ALObf6ffraIqhmm6zt1OsKSWrGJhJHrSpJ0MjYSzmyJD&itag=299&source=youtube&requiressl=yes&mh=GR&mm=31%2C29&mn=sn-xguxaxjvh-8v1s%2Csn-axq7sn7z&ms=au%2Crdu&mv=m&mvi=1&pcm2cms=yes&pl=24&initcwndbps=1216250&vprv=1&mime=video%2Fmp4&gir=yes&clen=56690849196&dur=111516.197&lmt=1608888423378797&mt=1654233182&fvip=18&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6416222&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRQIgNVMRjDRW3y45-IUDOQEYDNKw-bNeDOlkUwZqQw8sx7ICIQD3l8n0m7GKiu96oyQrF3RnsJI-9wDcIb35vLFATT3AjQ%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhANhGV17PX6DpRlV5XOOI2dtVJsOAY9TW-x_CnmX1eYQmAiEAwBRXAyCbGPrDBjtP80qAqIBjwZfr2YyU5YNJWwmQUt0%3D"
[download] Unable to open file due to file access error. Retrying (attempt 1 of 3) ...
[download] Unable to open file due to file access error. Retrying (attempt 2 of 3) ...
[download] Unable to open file due to file access error. Retrying (attempt 3 of 3) ...
ERROR: unable to open for writing: [Errno 22] Invalid argument
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/yt_dlp/downloader/http.py", line 267, in download
ctx.stream, ctx.tmpfilename = self.sanitize_open(
File "/usr/lib/python3.10/site-packages/yt_dlp/downloader/common.py", line 224, in inner
return func(self, *args, **kwargs)
File "/usr/lib/python3.10/site-packages/yt_dlp/downloader/common.py", line 241, in sanitize_open
f, filename = sanitize_open(filename, open_mode)
File "/usr/lib/python3.10/site-packages/yt_dlp/utils.py", line 621, in sanitize_open
stream = locked_file(filename, open_mode, block=False).enter()
File "/usr/lib/python3.10/site-packages/yt_dlp/utils.py", line 2055, in enter
raise e
File "/usr/lib/python3.10/site-packages/yt_dlp/utils.py", line 2052, in enter
self.f.truncate()
OSError: [Errno 22] Invalid argument

It doesn't seem like /dev/nul ever worked, even with youtube-dl

You left out an l in /dev/null

ah, my bad

Fixed in 8a82af3511b4379af0d239dbd01c672c17a2c46a


Default Gems loading

With Ruby 2.5 the number of "default gems" has expanded to cover a lot of libraries that were previously bundled in Ruby. I think the intention is for this to be mostly an internal change. Developers should be able to just require the same as when they were bundled in Ruby.
In combination with bundler it seems this change is more noticeable. Previously I could just require 'fileutils' without modifying my Gemfile. Now I get this message:
Gem::LoadError (fileutils is not part of the bundle. Add it to your Gemfile.)

It seems to me that the default gems should be assumed in the Gemfile to maintain the historical behavior so I don't need to explicitly include libraries like fileutils in my Gemfile. If someone wants a specific version of a default gem they could of course specify that in their Gemfile.
Steps to Reproduce
Verify at latest versions:
$ ruby -v
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin18]
$ bundle -v
Bundler version 1.17.1
$ gem -v
2.7.8

Verify desired stdlib is not part of Gemfile:
$ grep fileutils Gemfile.lock

Without bundler we can load the stdlib fine:
$ irb
irb(main):001:0> require 'fileutils'
=> true

With bundler we can no longer load the stdlib:
$ bundle exec irb
irb(main):001:0> require 'fileutils'
Traceback (most recent call last):
[....snip backtrace....]
Gem::LoadError (fileutils is not part of the bundle. Add it to your Gemfile.)

I can fix by adding fileutils but that shouldn't seem necessary for stdlibs.

#6963 should fix this, I think.

I believe it will. Closing this under that assumption.


[AKS] az aks: Fix monitoring addon and agentpool NoneType errors.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

Ready to merge?

Ready to merge?

Yes, please help merge it. Thanks!


[FEATURES] fluid+juicefs不支持污点调度

What feature you'd like to add:
Why is this feature needed:

Fixed by #2083


naming OAuthFlow.authorization_url

hey @davebelais  -
When creating a model for an openapi schema, I came across an issue with the OAuthFlow object mapping correctly and found it was because there wasn't a name for the authorization_url property - https://swagger.io/specification/#oauth-flow-object

Thanks for catching this @stephenknoth ! I pulled your branch, applied some formatting (by running make remodel), and created this PR, so am closing this one. I'd hoped to get some time to work on adding proper unit tests and documentation to this project over wellness week, but kids and COVID conspired against me—c'est la vie :-P.


fix(Dialog): fixed dialog overflow, added header caption control to story

If Dialog header has a long word, layout breaks:

I added word-break: break-word so that it looks a bit nicer:

Tested on phrase «Are you sure you want to launch aaa/bbbbbbbbbb/ccccccccccccc/ddddddddddd/eeeeeeeeeee/fffffffffff?».

Ooops, I didn't mean to try to merge without review. Mixed it up with rebase button.


Expense tags

User story
As part of https://github.com/opencollective/opencollective/issues/2394, we want users to be able to add multiple tags when they submit an expense, and not just a single category.

Best solution for this problem
Full ability to add and remove tags on expenses.
MVP
The full feature will be implemented with the new expense flow. This issue is only about implementing the changes in the API while being reverse-compatible with the existing frontend.

[ ] Create a new column on Expenses named tags, an array of strings
[ ] Move all the expense's category to this new field and delete the column
[ ] Adapt the existing graphql category field to return the first tag and deprecate it
[ ] Create a new tags fields for expenses on Expense's graphql type
[ ] Make sure the createExpense and editExpense endpoints are compatible with both usages

Some validations for tags were implemented with conversations. We should extract them in a lib to use the same between the two models: https://github.com/opencollective/opencollective-api/blob/5ff5e291d2dc833a90859b1f3790bef6fa84242d/server/models/Conversation.js#L61

An alternative to this proposal is to store the expense's tags at the conversation level. Because expenses are embed in conversations and conversations already have tags, it could make sense to use it.


Added missing onError handler.

Without this function it was impossible to catch a Parser Error.

Looks good. Merging


Added a way to check the DB's status

This has been extracted both from
https://github.com/openSUSE/docker-containers and #1353, since it will
be useful for #1357 as well.
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Adding @flavio since he was the original author.


[googlebigtable] Upgrading googlebigtable to the latest version.

The API used by googlebigtable has had quite a bit of churn.  This is the minimal set of changes required for the upgrade.

Merged in eaff913d28ab736d517fb4df2488ecb563fd2fc2, thanks!


Get mesh2 ports from correct resource

This PR is fixing installation script for federation poc example. It was not getting ports for mesh2 correctly.
[X] Does not have any changes that may affect Istio users.

/ok-to-test


removing non-base64 windows user_data

Nice catch - thanks @hh

hmm.... we may still have an issue (I was bootstrapping windows,nodes that already had that user_data executed...) as I'm not seeing user-data from the instances after my change


No action bar in Settings after selecting a group of settings

As reported by @moshpirit in #202
There is a fix for this AppCompat library bug: http://stackoverflow.com/questions/17849193/how-to-add-action-bar-from-support-library-into-preferenceactivity

Thinking about this further, I see that the problem appeared due to changing approach in Android to structure preferences. Usage of "Preference headers" is advertized as a solution to separating preferences between several screens.
So it looks like restructuring existing one file with preferences into headers (links to current screens) and several files with preferences (one file per screen) is the most compatible way of implementation.


Redundancy Groups

Closes: #1892
What's Changed

Starting RedundancyGroup implementation.
So far what's implemented:

RedundancyGroup model, supporting custom fields, tags, statuses, SecretGroups

failover_strategy is a choice, currently identified as Active/Active or Active/Passive

Device has been updated:

A FK to RedundancyGroup as redundancy_group
A PositiveSmallInt for optional priority

To be considered:

Built-in validation for no two Devices with same priority?
Different failover strategies
Any missing/unneeded fields on RedundancyGroup

To be implemented

Tests
Documentation
Additional/updated prefetch_related's in responses
Additional information on the Redundancy Group detail/list pages

TODO

[x] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

Built-in validation for no two Devices with same priority?

I'd say no to this validation. There are valid real-world use cases where two devices would have the same priority. For instance, I might have a cluster of 4 firewalls with two 10 and two 20.


Basic Strategy Overview Question

Hi I'm trying to workout how to add a new strategy or fix the current ones, because over the last week any average macd strategy would have created good profits from the uptrend of BTC/USD, but running the same thing on this bot == losses.
Is there a high level overview of how this works? Be great to publish some docs so we can get more PRs added to this project. JS/Node is f#cking crazy.
So I can see the strategies/macd folder how does that work with a sim or trade feature?

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


feat: add activate command

SUMMARY

Allow users to activate venv using make activate
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] 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

@hughhhh I'm fixing the Pylint issue. I merged https://github.com/apache/superset/pull/16388 however it wasn't rebased on the latest master.

@hughhhh https://github.com/apache/superset/pull/16405 should resolve the issue.


Simplify node start-up

Following https://github.com/input-output-hk/ouroboros-network/pull/938

bors r+


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10 to before v5.10.44",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3ed8e1c2ac9914a2fcb08ec13476b85319536cea",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=18eaf0de50eadeeb395b83310b259b21ad8ed0a6"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "3ed8e1c2ac9914a2fcb08ec13476b85319536cea",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "18eaf0de50eadeeb395b83310b259b21ad8ed0a6",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "usb: typec: tcpm: cancel vdm and state machine hrtimer when unregister tcpm port\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.44 by commit 18eaf0de50eadeeb395b83310b259b21ad8ed0a6, it was introduced in version v5.10 by commit 3ed8e1c2ac9914a2fcb08ec13476b85319536cea. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000957


Deprecation warnings on Swift 4.1 in README Example

Shihab,
Please can you take a look at the Example in the README.md as the package now builds correctly (see #31 for the fixes I put in there), although on Swift 4.1 - there are still 3 warnings: 'copyBytes(from:count:)' is deprecated: renamed to 'copyMemory(from:byteCount:)'. Please could you investigate and resolve these.
Thanks.

@helenmasters I've opened a PR in reference to this - https://github.com/IBM-Swift/Kitura-WebSocket/pull/33

The change to remove deprecation warnings is not yet tagged and there's another API breaking change in master (#28).  The next tag of master will need to be a major - or we could cherry-pick #33 in a patch off 1.0.1, if we think it's worth it.
The deprecation warnings in BlueCryptor have not been fixed yet (needs a PR), and it is also at 1.0 already.  Again, could patch off 0.8.x if we think it's worth it.
If we do move to BlueCryptor 1.0 - which would make sense to include in a new major of WebSocket - we'll need to do the same in Kitura-Session and any other modules that could be used together, else it will require SPM to perform rollbacks.  This may be worth doing as a general piece of work to move the repos to use the 1.0 versions of Socket, Signals, SSLService, Cryptor etc.

As we have now tagged a version 2 I've tested building the README example against both Swift 4.1 and Swift 4.2 and both versions now pass without generating any deprecation warnings, so I'm closing this issue as it is now fixed.


Fixed typo

Removed duplicated "the" word from Note

@JackA655 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


2.0 status?

Wasn't clear from the closed issues regarding 2.0 if this is 2.0-ready or not yet.

Seems like a pretty straightforward question here, any info?

@paulisloud, did you see the gatsby-v2 branch?

Ah, totally missed that. Thanks.


GPIO Tab

The GPIO tab has columns for Pins 1-17 but I cannot enter any values in the boxes and there are no drop-downs.

Thanks for splitting the issues up.
The GPIO tab is in it's very beginning and not functional at this time. I'll keep this issue open to remind me to work on it.

Which Mesa board are you using?

The 7i92m.
On Sun, Dec 4, 2022, 9:05 AM jethornton @.***> wrote:

Which Mesa board are you using?
—
Reply to this email directly, view it on GitHub
https://github.com/jethornton/mesact/issues/59#issuecomment-1336420318,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHL2HSDJNHW5F3KQYZVW4OLWLSQKTANCNFSM6AAAAAASSOCWFU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


12 C implementation of Muskingum Cunge

Port the Muskingum Cunge computation from Cython to pure C.
The primary goal was a cleaner version of Muskingum Cunge that could be free of the Cython boilerplate code, and thus be more readily optimized by a C compiler. This implementation uses double precision floats instead of single precision.
Compiling with -ffast-math give a small, but noticeable performance improvement without any apparent loss of accuracy.

Confirming -- @groutr -- this PR appears to make the introduction of these functions as capability but does not open any direct doors for their use in the existing workflow, is that correct?

@jameshalgren I'm still moving bits an pieces over from the work on my previous branch. I appear to have lost track of some of my commits.

@JoshCu, @TrupeshKumarPatel
Possibly a diversion, but also possibly worth resurrecting.


[Experimental] wasi/wasm32 platform support

Just a quick pass to see if we could get support for the wasi/wasm32 platform on Dagger. Seems to be working and initial impression is that this could be cleaned up to the point of being mergeable; probably not a throwaway experiment.
Based on top of the multiplatform PR.
Usage
Example usage from included test case (pulling and running a test image I built that has a wasm binary and uses platform wasi/wasm32):
https://github.com/dagger/dagger/blob/ff64e543a317d70f3d1fe889cd2a8ac46f050ec8/core/integration/platform_test.go#L346-L351
In that example the Exec defaults to the Entrypoint of the container, but in general args just need to be set to point to a .wasm binary.
Example of building a wasm binary from rust code and then executing it:
https://github.com/dagger/dagger/blob/ff64e543a317d70f3d1fe889cd2a8ac46f050ec8/core/integration/platform_test.go#L285-L336
Implementation
Quick hackish solution implemented in this PR:

Build wasmtime as a static binary
Include it alongside our shim binary
When wasi/wasm32 is being used, our shim invokes the wasmtime binary, which itself invokes the actual user's wasm binary
wasmtime is configured to setup mounts + env vars as configured in the container

Surprisingly that's it.
I started w/ a much more complicated path of using wasmedge and configuring buildkitd to use the containerd worker which is instrumented to use crun w/ wasmedge support (as described here), but I eventually realized all that did was result in this very light wrapper being invoked from crun's codebase.
However, we already have our own shim in dagger, so that's the much easier thing to use right now. It may be the right approach in the long run too? Not sure yet, haven't thought in depth.
Current Caveats

There seems to be module incompatibilities between wasm binaries built by different tools and at different times, so some of the existing wasi/wasm32 images I tried fail to load due to incompatible modules being required

AFAICT this is just an issue in the ecosystem, but I have not done anything w/ Wasm until today so I could easily be missing something. Need to research more.
For example, the michaelirwin244/wasm-example image fails to load w/ our wasmtime shim due to the errors listed here.

wasmtime lets you "mount" directories into the wasm sandbox but not individual files, so right now the silly workaround is that you can only include mounts which don't have a source path. Will need a better solution than this before merging though.
There's probably a lot of other features that don't translate perfectly to the wasm sandbox (i.e. I'm not sure you can set the current workding dir). We can decide if that's a dealbreaker or if it's okay to just have clean errors in those cases.
The shim build code statically compiles wasmtime from source, which takes a while (several minutes on my laptop). It's cached afterwards but still would be nice to avoid this as it slows down uncached CI builds a lot.

Given the speed of this repo -- should we merge this even if unfinished to avoid rotting? Or are there side effects to the non-wasm codepath?

I think I got rid of the impacts to non-wasm codepaths. The wasm code path needs a little love though; it currently statically compiles wasmtime from source, which takes several minutes (though obviously it's cached later). wasmtime is also incompatible with some of the wasm images I tried. So my overall idea was to try to pull a different pre-built image for wasmedge and get it working even when not statically linked (have an idea on how to do this pretty easily).
I don't want this to languish though either I agree. I'll rebase it once there's breathing room around the new SDK release and then quickly try to improve it. If the improvements don't work out, we can just merge it as is and then put a warning label on it that it's experimental or something maybe.


[Refactor] Remaining HPPC to java.util collections

This PR refactors the remaining usages of hppc collections to java.util collections and completely removes the obsolete hppc dependency.
relates #5910
relates #8110

/cc @andrross @saratvemulapalli

@nknize Curious to know, what was the performance impact of replacing primitive collections (such as ObjectIntHashMap, LongArrayList, etc.) with equivalent Java collections? Was the autoboxing impact negligible, or did these changes not fall in the hot path of requests?

Was the autoboxing impact negligible, or did these changes not fall in the hot path of requests?

@ketanv3 please check https://github.com/opensearch-project/OpenSearch/pull/7018 for the comments

Thanks @reta!
I found a place where primitive collections might have helped. In multi-term aggregations, the numeric term values are being boxed (here), which may have a noticeable performance penalty as it's done proportional to the number of hits, the number of fields, and the number of term values per field. I'm yet to measure the exact impact though.


TypeScript's dependency on electron limits the heap size to a point that breaks monorepos, and tsserver-bridge is no longer a workaround

Bug Report
Electron enforces a heap memory limit (due to pointer compression) that causes typescript to crash in large mono-repo. This was originally reported here, and then on the electron side here. One common workaround is to use tsserver-bridge to cause vscode to launch the typescript editor service in node rather than electron. Starting in typescript 4.6, it appears that the tsserver-bridge workaround no longer works.
Error when using tsserver-bridge:
Info 0    [09:17:36.144] Starting TS Server
Info 1    [09:17:36.145] Version: 4.6.4
Info 2    [09:17:36.145] Arguments: /my/path/to/node /my/path/to/.vscode/typescript/lib/_tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/l1/qrb13dbx3l3_wjlh4kgxnpm80000gn/T/vscode-typescript501/8d65dce0fd217a13c1cc/tscancellation-f05eabd1e2d0ae3f8300.tmp* --logVerbosity verbose --logFile /my/path/to/Code/logs/20220509T134031/exthost1/vscode.typescript-language-features/tsserver-log-Y6lofO/tsserver.log --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
Info 3    [09:17:36.145] Platform: darwin NodeVersion: 16 CaseSensitive: false
Info 4    [09:17:36.145] ServerMode: undefined syntaxOnly: false hasUnknownServerMode: undefined
Info 5    [09:17:36.149] Binding...
Info 6    [09:17:36.153] event:
    {"seq":0,"type":"event","event":"typingsInstallerPid","body":{"pid":28855}}
Err 7     [09:17:36.163] Exception on executing command unknown:

    process.send is not a function

    TypeError: process.send is not a function
        at IpcIOSession.writeMessage (/my/path/to/.vscode/typescript/lib/_tsserver.js:177001:29)
        at IpcIOSession.Session.send (/my/path/to/.vscode/typescript/lib/_tsserver.js:172938:22)
        at IpcIOSession.Session.event (/my/path/to/.vscode/typescript/lib/_tsserver.js:172947:22)
        at IpcIOSession.IOSession.event (/my/path/to/.vscode/typescript/lib/_tsserver.js:176966:48)
        at NodeTypingsInstaller.event (/my/path/to/.vscode/typescript/lib/_tsserver.js:176926:31)
        at Immediate.<anonymous> (/my/path/to/.vscode/typescript/lib/_tsserver.js:176776:71)
        at processImmediate (node:internal/timers:464:21)

Unfortunately, tsserver-bridge is no longer supported (author thinks it is no longer required since you can adjust heap size, but electron limits heap size because it implements pointer compression).
Electron has been so far unwilling to provide builds that disable pointer compression, and even if they did, vscode would need to begin leveraging it.
🔎 Search Terms
tsserver-bridge, heap limit, memory limit, process.send
🕗 Version & Regression Information

This changed between versions 4.5.4 and 4.6.4

🙁 Actual behavior
Large mono repos hit the memory limit and tsserver-bridge is not a workaround
🙂 Expected behavior
Allow tsserver-bridge to work or get off of electron

tsserver-bridge likely needs to be updated to support ipc too.

what does this mean? The whole tsserver-bridge package is pretty, short, would appreciate a pointer of what to change here.
The stack trace I shared is already using IpcIOSession (not IOSession), so I think that means it is already using node ipc? I tried passing the flag by patching tsserver-bridge, and I the flag is being passed (according to arguments that are logged in tsserver), but that didn't fix it. Something else needs to change too?

We discussed this today and decided VS Code should possibly let users opt into spawning TS Server in their own installed version of Node (and inform TS Server so it can communicate over STDIO as before, IIUC). @mjbvz was going to see if other language extensions have run into something similar. Matt, can I transfer this issue to VS Code for now?

Is there a related issue on vscode side?

Assigning to @mjbvz since I don't have rights to transfer this to the VS Code repo 😅

Can we keep this open until the vscode team actively takes ownership?


docs: broken links, missing info in mutation update docs

A few issues with https://www.apollographql.com/docs/react/basics/mutations.html#graphql-mutation-options-update (options.update section):

All DataProxy links are broken
The "Apollo Client technical documentation on the subject" link is broken
I believe the semantics of this function is that it is called twice if optimisticResponse is provided and once otherwise, but the docs don't say that explicitly.
It doesn't really explicitly say other than in the example what the second argument looks like (ie that it has a property named data).
Does this function get told that it is being called optimistically? I thought so but I don't see where it says that. (edit: it doesn't, see https://github.com/apollographql/apollo-client/issues/2523)

➤ David Glasser commented:
Also scrolling up a bit "be sure to read the recipe on Optimistic UI" is also a broken link.

➤ David Glasser commented:
Also another thing that's not clear to me: is it the case that any changes written during an optimistic call to update are automatically reverted when the mutation is done? (I think that's true and if so then that's good.) If so that should be explicit.

➤ David Glasser commented:
Also it might be nice to document that if you want to do custom writes optimistically that aren't part of the data returned by the mutation (eg, if you want to set some apollo-link-state state) then you can pass optimisticResponse: {} to trigger the optimistic writing stage without otherwise messing anything up.

➤ M S Morris commented:
Another link that appears to be broken is the cache docs link: https://www.apollographql.com/docs/react/basics/basics/cache.html
The link comes from https://www.apollographql.com/docs/react/basics/setup.html#ApolloClient


Ability to specify tests to run

npm test/npm run e2e without arguments will run all the tests; if one (or multiple) files passed - only them will be used. See updated README for examples.
Also, fixed a typo about e2e config location.

Codecov Report

Merging #55 (3cb0152) into main (37c8035) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3cb0152 differs from pull request most recent head 7cbedb1. Consider uploading reports for the commit 7cbedb1 to get more accurate results

@@           Coverage Diff           @@
##             main      #55   +/-   ##
=======================================
  Coverage   94.56%   94.56%
=======================================
  Files          48       48
  Lines         754      754
  Branches       68       68
=======================================
  Hits          713      713
  Misses         18       18
  Partials       23       23

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


Anti-rug mechanism for JPEGs

:ambulance: half-fix for the random double spend

:bug: (GalleryItem): removed unsued imports
:zap: added rmrk grapghql client
:zap: added Inmemorry cache
:zap: refactored transaction executor into separated functions
:zap: added checker before buy

Thank you for your contribution to the KodaDot NFT gallery,
we really appreciate your contribution!
PR type

[x] Bugfix
[x] Feature
[x] Refactoring

Before submitting this PR, please make sure:

[x] Your code builds clean without any erros or warnigns
[ ] You've posted screenshot of demonstrated change in this PR
[x] Merged recent default branch, main and you have no conflicts
[ ] Didn't break any original functionality

Optional

[ ] You've tested it on mobile
[ ] Are there any edge cases? Name if any

👀 what if we can release it today


🖼 Sprite Editor + ⚡ Electron bump

I apologize for not making these two separate pull requests, but untangling it was annoying.
Electron was bumped to 11.3.0 to add recursive file deletion, which also fixes a bug with the Haxe implemented recursive file deletion where it'd leave folders intact. Another bonus was that it fixes some places the orange outline refused to disappear. I updated font-scanner for x32 and x64, but not mac.
But yea, also there's a sprite editor. This was a nightmare because of how tangled it was with sequences and each frame basically living in 3 places (sequence, layer and on the sprite itself). Not to mention having to measure sprites to figure out their bounding boxes. But I added all features I think are necessary for the vast majority of games.
There's no visual bounding box editor, I'll probably do that later but this PR was already huge.
Pics:

I'm wondering whether it's possible and how hard is it to make room editor?

I'm wondering whether it's possible and how hard is it to make a room editor?

I too dream of a day where I never have to open GameMaker 😊
I'm definitely not the one that'll do it though. Sprites was already really straining and rooms are way more complicated.


Change lifetime ownership of decoded text in Caesar

This changes the clone from happening at every iteration in the Rot1-25(X) loop to only happening if checker_result.is_identified becomes True, which might save us some time!

https://github.com/bee-san/Ares/issues/111 attempting to help alleviate

There is no changes here :(
But removing caesar again does improve it:

Force-merging because this doesn't change much and might be a tiny speed improvement :)


Option to abstract data sources and use an API/database instead of GitHub

Summary
I really like TinaCMS quite a lot, though relying purely on GitHub for storing content is a bit limiting.
Is the Tina team perhaps considering abstracting data sources? For example, it would be great to also have the option to somehow use Tina in production with arbitrary API endpoints to retrieve and save data using a database.
Basic example
Ultimately I'd like to be able to build a website for someone -- example.com -- and then edit the website via an admin area -- admin.example.com.
Motivation
This would expand Tina's capabilities and enable it to be used on more than just repository-based websites.

Maybe this is already possible using useLocalForm + onSubmit as in this demo?

Hey @chaddjohnson ,
I just wanted to follow up on this. You're bang on with the onSubmit idea. Tina tries to avoid being too opinionated about your workflow, but our initial implementations have focused around using local file storage and pushing to a git remote.
We've recently published some new docs that describe the fundamental building blocks of Tina. If you use these instead of the more opinionated Gatsby/Next.js helpers, you will find a lot more flexibility.

The CMS
Forms

Hooking into the onSubmit, you can send the form data wherever you want when it's saved. And registering a custom API can help you abstract the behavior to apply it to multiple forms, if desired (but it's not absolutely necessary.)
Regarding the custom router: this is really only necessary when you need to implement the service layer yourself, and intend to do so in the same codebase as your website. @tinacms/api-git exists to expose a browser-accessible API for manipulating local files and interacting with a git remote. This could instead be achieved by creating a standalone application that exposes a web API, or by interacting directly with a third-party service that stores your content and allows you to make updates via API (as in the firebase example.)


Main

@dotnet-policy-service agree
[ReleasePrep][2023.04.25]RI of dev into main
Summary of the changes (in less than 80 characters):

Detail 1
Detail 2

Addresses https://github.com/NuGet/NuGetGallery/issues/123

@dotnet-github-policy-service agree
@dotnet-policy-bot

No description, too much changes.


Remove comment from momentum block helper

The comment is included everywhere where {{#momentum}} is called.

Thanks @johanbrook - this will go out with the next release.


Inside TouchableOpacity and TouchableHighlight doesn't render on Android

Wrapping a LinearGradient component inside a TouchableOpacity does not render anything on Android. It renders fine on iOS. When wrapping in a TouchableHighlight, an error is shown stating that LinearGradient must implement setNativeProps. Wrapping it instead inside a View, then inside a TouchableHighlight results in it not rendering as well on Android, but rendering fine on iOS.

Fixed in 0.22

save problem in 2.2.0


nvm installation freezes on WSL2

Operating system and version: WSL2 Ubuntu 18.04
nvm debug output:

freezes at Cloning into '/home/j0nimost/.nvm'...

How did you install nvm?

it never completed the installation

What steps did you perform?

I ran this command curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash --verbose
I got this output

=> Downloading nvm from git to '/home/j0nimost/.nvm'
=> Cloning into '/home/j0nimost/.nvm'...

Installation froze after inserting my git ssh key

What happened?

I have a git ssh config so once the prompt asked for my passphrase it freezes

What did you expect to happen?

I expect the installation to complete and nvm to work

Is there anything in any of your profile files that modifies the PATH?

NO

hmm - i suspect that because the command is running in a piped subshell, that perhaps the ssh key prompt is hanging because it can't ever get your input.
I think you might be able to follow https://unix.stackexchange.com/a/12201/137489 before running the install script command? However, ssh keys with a passphrase generally can't be used by non-interactive commands, which is why they're usually avoided.

I just realized the problem, my ssh key was new and I hadn't linked it with Github. Running ssh -vT<EMAIL_ADDRESS>gave me this insight. So I quickly just pushed some code to Github using my ssh key and I ran ssh -vT<EMAIL_ADDRESS>again to confirm the link.
Afterwards, the installation worked.  This issue is not linked to nvm so I'll close this issue


[rke2] unable to deploy production-ready setup with RKE2 linux node driver (3etcd, 2cp, 3worker)

Rancher Server Setup

Rancher version: v2.6-head (4a5a926)
Installation option (Docker install/Helm Chart): helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): rke1, v1.3.9

Proxy/Cert Details: valid certs

Information about the Cluster

Kubernetes version: v1.22.8+rke2r1
Cluster Type (Local/Downstream): downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): linode node driver

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom): admin

Describe the bug
when deploying a cluster using linode rke2 driver, the cluster fails to come up. Some nodes are failing due to an error.
To Reproduce

deploy an rke2 cluster using 1.22.8+rke2r1 with 3etcd, 2cp, 3workers.

Result
some nodes are in this state:

 CreateError: Downloading driver from https://<rancher_server>/assets/docker-machine-driver-linode Doing /etc/rancher/ssl docker-machine-driver-linode docker-machine-driver-linode: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped Running pre-create checks... (ctw-rke2l-c-cf141e4e-nk4gr) Generating a secure disposable linode-root-pass... Creating machine... (ctw-rke2l-c-cf141e4e-nk4gr) Creating Linode machine instance... Error creating machine: Error in driver during machine creation: [408] Please try again The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag

and the cluster never registers any worker nodes.
Expected Result
linode should work with RKE2 when using multiple nodes in the setup
Screenshots

Additional context
a single node rke2 cluster came up fine with the same k8s version

Root cause
The root cause here was the Linode API not being about to handle the number of requests we were making.
What was fixed, or what changes have occurred
The error is still likely to occur, but Rancher will not retry if the request to create the machines fails for some reason.
Areas or cases that should be tested
Provisioning an RKE2 cluster in Linode as described in the description.
What areas could experience regressions?
Creating machines.
Are the repro steps accurate/minimal?
Yes.

Closing this issue as duplicate of 36939


Add fault attribute to generated errors

Description of changes:

Generated service errors (modeled with @error) should have the fault (client or server) as an attribute

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8034de6) 94.64% compared to head (0736ba4) 94.64%.
 Consider uploading reports for the commit cb22851 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #190   +/-   ##
========================================
  Coverage    94.64%   94.64%
========================================
  Files           35       35
  Lines         1682     1682
========================================
  Hits          1592     1592
  Misses          90       90

Flag
Coverage Δ

unittests
94.64% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Develop

ThingSpeak values are not updating i think it is because my university account is suspended. I'll check and update in PR comments.

Value is updateable from postman so there might be a code issue, @wasey-rao you can create an issue if you face same issue with your module.

this PR code's neither stable nor working, make it stable in 24 hours otherwise it will be closed.
@mhamidjamil @hamidjamil0420

code it working fine till version 5.3.5 i have verified it now. Can you please share which errors or blockers you are facing and please also mention the file name and version tag if possible. @wasey-rao

@wasey-rao can you please now verify the code and also the issue as it is fixed on my side now, if this PR is merged then I'll Start working on #82, But in this PR debugging pattern is added which will help me to sort out the issue.


Hopper Overhaul

Instead of awaiting all items at once, for playlists we should instead return only the first item, play it, and then return the rest. This would optimize load times for large playlists..
Possible implementations include making Hopper an event emitter, or making it return a generator.

Would also be ideal to differentiate between a single item and multiple item, so that an emitting/generator-based hopper is only instantiated on requesting a playlist or album.

Implemented in V2.


Ratings don't work at all.

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!
(I've had this ever since I updated JS Engine) The rating images don't show up when I hit notes (drive video below for demonstration), the miss rating still works thought. And no, I had no mods enabled.
https://drive.google.com/file/d/1NRKRHcs_tLxGXgKE6tF-6jlOojQ6ZE6f/view?usp=sharing

Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
Updating JS from V1.35.0 to V1.36.0 directly in-game, not through Github.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

it's possible that you turned on "Even LESS Botplay Lag".

yeah that fixed it


TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator)) in amplify push log

Describe the bug
I started a new amplify project and added auth and cognito user groups. Upon pushing these changes I'm now getting
⠋ Updating resources in the cloud. This may take a few minutes...TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at getUniqueStacksEvents (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/aws-utils/aws-cfn.js:477:24)
    at /home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/aws-utils/aws-cfn.js:129:30
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:27683) UnhandledPromiseRejectionWarning: UnknownEndpoint: Inaccessible host: `cloudformation.us-east-1.amazonaws.com'. This service may not be available in the `us-east-1' region.
    at Request.ENOTFOUND_ERROR (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:507:46)
    at Request.callListeners (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
    at ClientRequest.error (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:339:22)
    at ClientRequest.<anonymous> (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/http/node.js:96:19)
    at ClientRequest.emit (events.js:314:20)
    at ClientRequest.EventEmitter.emit (domain.js:486:12)
    at TLSSocket.socketErrorListener (_http_client.js:469:9)
    at TLSSocket.emit (events.js:314:20)
(node:27683) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
⠧ Updating resources in the cloud. This may take a few minutes...TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at getUniqueStacksEvents (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/aws-utils/aws-cfn.js:477:24)
    at /home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/aws-utils/aws-cfn.js:129:30
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:27683) UnhandledPromiseRejectionWarning: UnknownEndpoint: Inaccessible host: `cloudformation.us-east-1.amazonaws.com'. This service may not be available in the `us-east-1' region.
    at Request.ENOTFOUND_ERROR (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:507:46)
    at Request.callListeners (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
    at ClientRequest.error (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:339:22)
    at ClientRequest.<anonymous> (/home/god/.nvm/versions/node/v14.10.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/http/node.js:96:19)
    at ClientRequest.emit (events.js:314:20)
    at ClientRequest.EventEmitter.emit (domain.js:486:12)
    at TLSSocket.socketErrorListener (_http_client.js:469:9)
    at TLSSocket.emit (events.js:314:20)
(node:27683) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

Amplify CLI Version
4.32.1
Expected behavior
No TypeError.
Desktop (please complete the following information):

OS: Ubuntu 20.04 on WSL (Windows 10)
Node Version:  v14.10.1

@kylekirkby Could you specify settings you chose when adding auth?

@nikhname
amplify add auth

? Do you want to use the default authentication and security configuration? Default configuration
? How do you want users to be able to sign in? Username
? Do you want to configure advanced settings? No, I am done.

Also, I believe I added add-to-group functionality.

@nikhname
https://dev.to/dabit3/the-complete-guide-to-next-js-authentication-2aco
amplify add auth

? Do you want to use the default authentication and security configuration? Default configuration
? How do you want users to be able to sign in? Username
? Do you want to configure advanced settings? No, I am done.

Also, I believe I added add-to-group functionality.

I tried to reproduce by following these steps (added user groups as well), however, amplify push completed successfully without any error. My Amplify CLI version is 4.43.0. @kylekirkby are you still facing this issue in the latest version of the CLI?

@rajrajhans - I have seen some random stack traces on occasion. But sadly, I did not keep a log of the exact message. I'll open an issue/add to this if I see it again. Cheers!

Closing in favor of https://github.com/aws-amplify/amplify-cli/issues/6660


Pod status Unknown after recreate

After running bosh with the recreate directive for single VM k8s cluster the coredns pods and any pods deployed outside of the kube-system namespace have a status of "Unknown". Describing the pod shows a Stats of "Running" with a Container state of "Terminated" and an Event message status of "Pod sandbox changed, it will be killed and re-created.".
Terminating the affected pods results in a recovery of those pods.

Using a two-node k8s cluster fewer vms end up in an "Unknown" state, but the issue is still present.

Upgrading from a 2-node to 3-node k8s cluster does not result in any pod failures. Issuing a recreate does still result in a small subset of pod failures.

Yeah, I think we need to start cordoning and draining nodes in a pre-stop.  Curious how that will effect tinynetes, and whether or not we'll have to make that configurable...

I think this is handled in #34, with a drain script.  Take a look, and see what you think.

The fixes in PR #34 will be available in the next (1.18.x) release.


Athentication Google & Microsoft

Authentication with Google and Microsoft Accounts not working.

sorry, I don't know. I try it to working

You've add  the method   ConfirmExternal(string provider, string userName, string name, string accesstoken) in login page but never been used

look at it


Dummy checkin to test recheck hooks

Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>

recheck

recheck

Abandoned.


Removed MapBox related imports

Description (required)
Removed Mapbox related imports
Fixes #5566
Tests performed (required)
Tested ProdDebug on Samsung S21 FE with API level 33.

@nicolas-raoul Kindly review this pull request :)


Lowering Existential Deposit on Asset Hub for Polkadot

A proposal to reduce the existential deposit required for Asset Hub for Polkadot from 0.1 DOT to 0.004 DOT, making:
(a) asset minting to all DOT token holders more affordable for Asset Minters and
(b) asset conversion on Asset Hub for Polkadot more accessible for all DOT Token holders.

See @joepetrowski's https://github.com/polkadot-fellows/runtimes/pull/131 which proposes to lower 0.1 DOT to 0.01 DOT for Asset Hub on Polkadot, Collective, and BridgeHub.

See @joepetrowski's https://github.com/polkadot-fellows/runtimes/pull/131 which proposes to lower 0.1 DOT to 0.01 DOT for Asset Hub on Polkadot, Collective, and BridgeHub.

As the above has been merged, closing this.


Feature Request: TFRecord file format support

I've had much success w/ this TFRecord plugin for spark.
https://github.com/tensorflow/ecosystem/tree/master/spark/spark-tensorflow-connector
You can build your dataset using the DataFrame API and then save to disk in TFRecord format (Example protos) for fast io during TF training.
I've been migrating my spark workflows to Dask, and thought I would see if this is on anyone's radar?

I'm not aware of anyone doing this yet.
If you were using just pandas, how would you write a DataFrame as a TFRecord?

Each column of the pandas DF would map to a Feature in the Example proto. The Example protos are then written to disk in the tfrecords container format.

Can you provide an example? I suspect this is doable with dask.delayed, but I've never used TFRecord before.

@eggie5 can you provide an example using just pandas?

@TomAugspurger
Not sure how to implement this in pandas, but w/ spark which has a DataFrame API, you can do it like this:
def tensorflow_writer(basedir, options):
    """Closure to help build tensorflow writer for rdd.foreach lambda"""

    def _writer(group, iterator):
        """writes protos to tfrecords"""
        filename = "%s/%s/ltr_dataset.tfrecord"%(basedir, group)

        with tf.python_io.TFRecordWriter(filename, options=options) as writer:
            for proto in iterator:
                writer.write(proto)

    return foreach_writer

writer = tensorflow_writer(base_dir, options)

protos.mapPartitionsWithIndex(writer).collect()

It'd be quite similar with dask.dataframe. I think the main limitation is that we don't currently pass through any group / partition info to the user-defined function (_writer) passed to map_partitions.
import pandas as pd
import tensorflow as tf
import dask.dataframe as dd
import tempfile
import numpy as np

df = pd.DataFrame(np.random.randn(100, 10), columns=list('abcdefghij'))
y = df.a > 0
df.head()

def write(df):
    with tempfile.NamedTemporaryFile() as f:
        writer = tf.python_io.TFRecordWriter(f.name)

        for i in range(len(df)):
            label = y.iloc[i]
            features = list(df.iloc[i])
            feature = {
                "train/label": tf.train.Feature(int64_list=tf.train.Int64List(value=[label])),
                "train/image": tf.train.Feature(float_list=tf.train.FloatList(value=features))
            }
            example = tf.train.Example(features=tf.train.Features(feature=feature))
            writer.write(example.SerializeToString())

    return f.name

>>> write(df)
'/var/folders/hz/f43khqfn7b1b1g8z_z6y3bsw0000gp/T/tmpboi8_8_q'

>>> filenames = ddf.map_partitions(write)
>>> filenames
Dask Series Structure:
npartitions=2
0     object
50       ...
99       ...
dtype: object
Dask Name: write, 4 tasks

Closing as this seems to be resolved, but LMK if not.

Oh, and since I didn't explicitly state it, I think that writing to TFRecord is out of scope for dask.dataframe (though others may disagree). But hopefully that snippet helps.

I think that this is something that we would defer to the Pandas community
to implement first.  Alex, I would encourage you to engage there.  Once
Pandas implements a TFRecord reader/writer it will be easy to add it to
Dask.  If they choose not to implement such a reader/writer then this
functionality should probably go in an external package.
On Tue, Nov 26, 2019 at 4:47 AM Tom Augspurger<EMAIL_ADDRESS>wrote:

Oh, and since I didn't explicitly state it, I think that writing to
TFRecord is out of scope for dask.dataframe (though others may disagree).
But hopefully that snippet helps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5618?email_source=notifications&email_token=AACKZTCZ6CFNOLZSW7FRLV3QVULFTA5CNFSM4JPXUUO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFF4FKQ#issuecomment-558613162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTBBV4LNIYUH4SKPC3TQVULFTANCNFSM4JPXUUOQ
.

Ah, I understand better know. I guess why I posted the request here first, is that I was confused b/c spark owns the underlying serialization layer whereas Dask simply defers to Pandas.
I'll explore this w/ the Pandas community.

Hi there, I'm insterested in this as well, and it seems that there's this project for pandas https://pypi.org/project/pandas-tfrecords/

Thanks @tgalery. For reference, there's some discussions on making pandas' IO pluggable: https://github.com/pandas-dev/pandas/issues/26804. But there isn't consensus on how to proceed.


Vacms 8433 typedoc basic setup

Part of https://github.com/department-of-veterans-affairs/va.gov-cms/issues/8433

Something has gone oddly with this branch. Closing.


Is there an additional loss function(TV loss)?

Is there an additional loss function(TV loss)? TV loss seem does not appear in the original paper.

@liulanxi #108

Thank you.


[Torquebox 4] Some files are missing in bundled git gems of war files

jruby <IP_ADDRESS>
wildfly 9.0.2.FINAL
torquebox 4x build 377
This (nasty) problem seems to appears if :

using a gem with bundler Gemfile "git:" or "github:"
and the gemspec refers to a file beginning with a dot (eg. .gitignore) or a file which doesn't exist

16:59:15,825 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./: java.lang.RuntimeException: java.lang.RuntimeException: Initialization failed

        at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Initialization failed
        at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:224)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
        ... 6 more
Caused by: java.lang.RuntimeException: Initialization failed
        at org.projectodd.wunderboss.wildfly.ServletListener.contextInitialized(ServletListener.java:100)
        at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
        at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:195)
        ... 8 more
Caused by: org.jruby.exceptions.RaiseException: (SystemCallError) Unknown error - Unknown Error (0) -
.gitignore
        at org.jruby.RubyFile.stat(org/jruby/RubyFile.java:901)
        at RUBY.block in validate_permissions(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/rubygems/specification.rb:2716)
        at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1560)
        at RUBY.validate_permissions(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/rubygems/specification.rb:2715)
        at RUBY.validate(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/rubygems/specification.rb:2582)
        at RUBY.block in validate(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/rubygems_integration.rb:51)
        at RUBY.silence(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/ui/silent.rb:40)
        at RUBY.validate(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/rubygems_integration.rb:51)
        at RUBY.block in load_gemspec_uncached(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler.rb:346)
        at org.jruby.RubyDir.chdir(org/jruby/RubyDir.java:327)
        at RUBY.block in chdir(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/shared_helpers.rb:53)
        at RUBY.mon_synchronize(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/monitor.rb:211)
        at RUBY.chdir(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/shared_helpers.rb:52)
        at RUBY.load_gemspec_uncached(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler.rb:339)
        at RUBY.load_gemspec(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler.rb:329)
        at RUBY.block in load_spec_files(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/source/path.rb:135)
        at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1560)
        at RUBY.load_spec_files(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/source/path.rb:134)
        at RUBY.load_spec_files(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/source/git.rb:188)
        at RUBY.local_specs(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/source/path.rb:92)
        at RUBY.specs(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/source/git.rb:159)
        at RUBY.block in index(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:209)
        at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1560)
        at RUBY.block in index(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:207)
        at RUBY.build(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/index.rb:9)
        at RUBY.index(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:204)
        at RUBY.resolve(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:198)
        at RUBY.specs(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:137)
        at RUBY.specs_for(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:182)
        at RUBY.requested_specs(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/definition.rb:171)
        at RUBY.requested_specs(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/environment.rb:18)
        at RUBY.setup(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/runtime.rb:13)
        at RUBY.setup(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler.rb:92)
        at RUBY.<top>(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/gems/shared/gems/bundler-1.11.2/lib/bundler/setup.rb:8)
        at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:937)
        at RUBY.(root)(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1)
        at RUBY.<top>(/tmp/wunderboss8215384550760604451/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:128)

Are you still having this issue? I tried to reproducing using both the rake and thor gems from git, since both have at least one dotfile in their gemspec. I was unable to reproduce the error.

No it's ok. Thanks.


Reworkmd

coverage: 93.759%. remained the same
when pulling bef5395337fb1ad4b7ac91143b52520ad04cae36 on reworkmd
into 40f8bc548caf095d0c3db625124ed332dd0ee0b3 on main.


Reorganized the POMs, bumped some versions and fixed JavaDoc

Made indentation consistent.
Removed redundant declarations from POMs
Locked down additional plugin versions
Bumped versions of some dependencies
Moved configuration of common dependencies to parent POM
Replaced <tt> tags in DD.java with {@code} tags so project builds correctly in release profile

Thanks putting in so much effort to clean up the pom.xml files.  You changes substantially improve Tinfour's use of Maven.
Also, thanks for fixing the Javadoc in DD.java.  The code was adopted from another project and I was reluctant to change it more than I already had.  But the corrections to the Javadoc should have been done a long time ago...  Even so, I'm glad I waited because your changes were much better than what I would have done.

Thanks putting in so much effort to clean up the pom.xml files. You changes substantially improve Tinfour's use of Maven.

No problem, I enjoy working with Maven so it was fun to do. :)


App won't close even pop() or press back button on the last page

I noticed this while developing my own app, and when I tried it with the official example, the same problem occurred.
Here is the error log. Also, the same error is displayed even when pop() succeeds when there are other pages.
E/flutter ( 5908): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: NoSuchMethodError: The getter 'length' was called on null.
E/flutter ( 5908): Receiver: null
E/flutter ( 5908): Tried calling: length
E/flutter ( 5908): #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:54:5)
E/flutter ( 5908): #1      Uri.parse (dart:core/uri.dart:726:17)
E/flutter ( 5908): #2      VRouterState._updateUrl (package:vrouter/src/router.dart:1065)
E/flutter ( 5908): #3      VRouterState._pop (package:vrouter/src/router.dart:1516)
E/flutter ( 5908): #4      VRouterState.systemPop (package:vrouter/src/router.dart:1948)
E/flutter ( 5908): #5      VRouterData.systemPop (package:vrouter/src/router.dart:2127)
E/flutter ( 5908): #6      _VRouteState.build.<anonymous closure> (package:vrouter/src/route.dart:67)
E/flutter ( 5908): #7      _VRouteState.build.<anonymous closure> (package:vrouter/src/route.dart:66)
E/flutter ( 5908): #8      VRouterDelegate.popRoute (package:vrouter/src/navigation_2_wrappers.dart:497)
E/flutter ( 5908): #9      _RouterState._handleBackButtonDispatcherNotification (package:flutter/…/widgets/router.dart:613)
E/flutter ( 5908): #10     _CallbackHookProvider.invokeCallback (package:flutter/…/widgets/router.dart:767)
E/flutter ( 5908): #11     BackButtonDispatcher.invokeCallback (package:flutter/…/widgets/router.dart:851)
E/flutter ( 5908): #12     RootBackButtonDispatcher.didPopRoute (package:flutter/…/widgets/router.dart:944)
E/flutter ( 5908): #13     WidgetsBinding.handlePopRoute (package:flutter/…/widgets/binding.dart:635)
E/flutter ( 5908): <asynchronous suspension>
E/flutter ( 5908): #14     MethodChannel._handleAsMethodCall (package:flutter/…/services/platform_channel.dart:435)
E/flutter ( 5908): <asynchronous suspension>
E/flutter ( 5908): #15     _DefaultBinaryMessenger.handlePlatformMessage (package:flutter/…/services/binding.dart:284)
E/flutter ( 5908): <asynchronous suspension>
E/flutter ( 5908):

Hi, are you using the nullsafe version or the other one?

Thanks for the quick reply.
I have checked with 0.0.14.
I just tried it now with 1.0.0-nullsafety.11 and the error is gone, but it did not solve the problem of the app not closing.

The nullsafe version does not have it because the package I need to do it has not migrates yet.
0.0.14 should work though, I'll have a look and let you know!

OK, Thank you😊

v0.0.15 should fix this, please reopen this issue if it did not.
Thanks for your interest in vrouter !

I checked it now and it is fixed.
Thanks for fix, and for great package!


Add limitRunwayQuery method to allow resources to be filtered/limited

This PR adds support for a method to the index and field type listings that limits the results returned based on the developers requirements.
Our use case is we have a multi-site environment so we only want to return resources relevant to the site the user is editing. By providing this method we can filter the results.
To Do

[x] Made changes to the BaseFieldType and ResourceListingController files
[ ] Added a test
[ ] Updated the documentation

Haven't added tests or docs yet as I want to see if this is something you'd want to support.

Would you be able to add a code example of how this would look inside a model?

Yeah of course...
    public function limitRunwayQuery($query)
    {
        return $query->whereHas('categories')->where('something_else', true);
    }

Yeah that makes sense. I've called the scope runwayListing to follow the same convention as runwaySearch.
    public function scopeRunwayListing($query)
    {
        return $query->whereHas('categories')->where('something_else', true);
    }

Thanks - if you're able to, would you be able to add a test & mention it in the docs? I'll take a look tonight and get it merged in.


Android activity creation spans

Fixes #
Changes
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist

[ ] CONTRIBUTING.md guidelines followed.
[ ] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[ ] schema-next.yaml updated with changes to existing conventions.

Rather than defining this strictly for Activities, have you thought about generalizing this to apply to all Android Lifecycle events? I can imagine wanting to track this for Fragments (no comment about whether or not Fragments are a good thing ;-) ), so it might be good to define it once and have additional metadata describing what this applies to.

Rather than defining this strictly for Activities, have you thought about generalizing this to apply to all Android Lifecycle events? I can imagine wanting to track this for Fragments (no comment about whether or not Fragments are a good thing ;-) ), so it might be good to define it once and have additional metadata describing what this applies to.

That sounds interesting. I haven't thought about it so far because I was planning to create another PR for the fragment creation spans after this one got sorted, where we could specify more fragment-specific methods such as onCreateView for example.
Having said that though, it could be nice to have some sort of consistency across these spans regardless of whether they happened in an activity or a fragment, although I have a few concerns about coming up with our own set of spans to describe things in a more generalized way without having to specify activity/fragment specific method names, one of them is that we'd be putting some sort of blanket over Android's conventions, which worries me about having to maintain/adapt it in the long run to any changes that might be added there in the future (which I guess is pretty unlikely but it wouldn't be the first time they make breaking changes to stuff that's been untouched for a long time). The second one is that I believe having specific spans for each type (activity/fragment) could help identify more accurately the part of the code that might be causing bottlenecks during the screen rendering process, whereas with the generalized naming, you can tell that something's taking quite long but it wouldn't be obvious where exactly to look in the code to improve it. Though I'm open to suggestions to address those issues, is just that right now it's not clear to me how to deal with the nuances.


Secure Boot related refine

Re-organize the secure boot keys
Add OTP provisioning to menu
Warn usage of dummy key

You need to describe better the boundary conditions when this starts to break. Currently, it works. I suppose it fails when the links we have in keys/ are pointing outside of the keys/ folder, right?

You need to describe better the boundary conditions when this starts to break. Currently, it works. I suppose it fails when the links we have in keys/ are pointing outside of the keys/ folder, right?

Yep.


WIP: Add source builds for HDF5 on Linux

Hi,
I don't have root access so I added support to build HDF5 from sources.   I tried the above but it failed.  Then I went into the src/ directory and ran ./configure --prefix=/path/to/.julia/v0.3/HDF5/deps/usr and make install.  Then it works from Julia.  So I don't understand how to use the build system well enough to figure out this trivial error.  Hopefully someone knows and we can get HDF5 working when a user doesn't have root access.
Glen

Seems to have been superseded by #291.


chore: adaptations for nightly-2024-05-01

Looks great, thanks! Where did the test failures from #128 go?


change check behavior to only use double types

Description
stan/math/prim/err/check_simplex.hpp is doing its checks on the autodiff type that it's supplied.
Here's the current code for a vector of scalar type T_prob.
  check_nonzero_size(function, name, theta);
  if (!(fabs(1.0 - theta.sum()) <= CONSTRAINT_TOLERANCE)) {
    std::stringstream msg;
    T_prob sum = theta.sum();
    msg << "is not a valid simplex.";
    msg.precision(10);
    msg << " sum(" << name << ") = " << sum << ", but should be ";
    std::string msg_str(msg.str());
    throw_domain_error(function, name, 1.0, msg_str.c_str());
  }

That first sum and subtraction from 1 is being done with autodiff types.
check_cholesky_factor_corr is just as bad.  This habit probably started because the first ones like positive and negative didn't require any intermediate expressions.
Someone needs to go through all of these things and make sure that the values are extracted and that we don't factor an autodiff variable for a covariance matrix test.
This one's actually pretty important for performance since it hits every parameter defined with a constrained type other than the simple lower and upper bounds and orderings:  unit vectors, simplexes, correlation cholesky factors, and covariance and correlation matrices.
It'd be good to spot check the other ones so there aren't anything like this fabs(1 - x) thing going on anywhere, because that'll also drop things on the stack.
Current Version:
v3.1.0

I don't see the problem with check_cholesky_factor_corr; it calls check_unit_vector, which needs to be fixed, but check_cholesky_factor_corr itself is fine? I see it calls transpose, but I don't think transpose makes autodiff nodes?
All of these functions need help:

stan/math/prim/err/check_2F1_converges.hpp
stan/math/prim/err/check_3F2_converges.hpp
stan/math/prim/err/is_unit_vector.hpp
stan/math/prim/err/check_unit_vector.hpp
stan/math/prim/err/is_corr_matrix.hpp
stan/math/prim/err/check_corr_matrix.hpp
stan/math/prim/err/is_symmetric.hpp
stan/math/prim/err/check_symmetric.hpp
stan/math/prim/err/check_simplex.hpp
stan/math/prim/err/is_mat_finite.hpp

Note that (is|check)_symmetric use value_of, but they need to be using value_of_rec.
Note also that is_mat_finite delegates to this bit of code inside Eigen:
template<typename Derived>
inline bool DenseBase<Derived>::allFinite() const
{
#if EIGEN_COMP_MSVC || (defined __FAST_MATH__)
  return derived().array().isFinite().all();
#else
  return !((derived()-derived()).hasNaN());
#endif
}

And that subtraction there should make an autodiff node.
I think everything else in prim/err/* is fine as far as this issue goes.

Nice catch inside the Eigen code!  I wonder why they did it that way.


Make the parse module public

Ref: #22

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

So I guess the primary concern I have with this is that the AST is really an implementation detail of regular expressions, and as such, it could change in the future.
I am personally satisfied if the module documentation contains a clear warning that clients cannot rely on the interface to be stable, but that seems kind of wonky given 1) semantic versioning and 2) Rust's current approach to stability, which is, "if it isn't stable, don't let people use it."
On the other hand, having a regex parser can be immensely useful. The parser itself is at least as complicated as the VM, so it's a good piece of code to have available for general use.

Yeah, I agree that this is not something we want to commit to stability - but, like you said, the parser is super-useful to have available for common use.  I considered also marking it as #[doc(hidden)], but all that really does is make it a bit more irritating to read about.
I'm happy to either put a big warning in the module-level documentation, or just outright hide it.  I'd be interested in the input of @alexcrichton or any other core-team members here.

I'm not a fan of hiding it. I see #[doc(hidden)] as a tool to expose something that shouldn't be exposed but must be exposed. For example, a whole bunch of internals are actually public so that regex_macros can use it: https://github.com/rust-lang/regex/blob/master/src/lib.rs#L391-L421
But yes, more input is welcome!

In terms of long-term stability I believe I'd expect an implementation detail such as this to remain private, but we're not currently providing a whole bunch of guarantees about the stability of external crates beyond "we'll follow semver". I would personally err on the side of being conservative and leaving it private for now, although I don't have a great grasp on how it might change in the future.
Basically my consideration would be that any modification to the parser which broke an API would require a new major version for the crate, which is just something to balance :)

Basically my consideration would be that any modification to the parser which broke an API would require a new major version for the crate, which is just something to balance :)

That's a fair point, yeah.  I wonder if there's a sensible way to say "this module is completely free from any security guarantees" - essentially, omit it entirely from semver.  I think that for internals like the parser, that's an entirely reasonable stance to take.

Unfortunately we don't currently have a method of enforcing that sort of guarantee, so this may end up being too much of an overcommitment for now.

That's fair.
@andrew-d For now, I'd recommend doing a copy & paste of the parser for now. We can re-examine opening it up later when we're more confident that it's actually stable.


Fix error in toPlonkConstraint

ConstVar one is used in the spot where we are supposed to have an "impossible variable". I believe it appeared as a result of refactoring. The expression
toPlonkConstraint @Fr @1 $ var (ConstVar one)

results in an error. Any other value, except one works here.

[ ] Fix the error
[ ] Improve the test

Here is an example of a polynomial that does not transform into a Plonk constraint:
1∙xSysVar (NewVar "y\ETX^\246\226\195\154S\130M\tL\146y\248\201\162\220 \237n6p\bC\151\186\241\US\136\225\139")∙xSysVar (NewVar "~\180\185\222\SOH!\t\254\155\v\SI\187\&9\227\163|^\168Z\184Q\129\rN\218\SYN\GSp\189\139~^")


Child node is not rigid during transition

Child node does not track its parent and lags behind during transition (Famous/engine@0.6.2):
'use strict';

var DOMElement = require('famous/dom-renderables/DOMElement');
var FamousEngine = require('famous/core/FamousEngine');
var Transitionable = require('famous/transitions/Transitionable');

FamousEngine.init();

var bg = FamousEngine.createScene().addChild();
new DOMElement(bg).setProperty('background-color', 'grey');

var x = new Transitionable(0);

bg
  .setSizeMode('absolute', 'absolute')
  .setAbsoluteSize(250, 250);

var logo2 = bg.addChild();
new DOMElement(logo2, { tagName: 'img' })
  .setAttribute('src', './images/famous_logo.png')
  .setProperty('background-color', 'red');

logo2
  .setSizeMode('absolute', 'absolute')
  .setAbsoluteSize(120,120);

var position = bg.addComponent({
  onUpdate: function(time) {
    bg.setPosition(x.get());
    if(x.isActive()) {
      bg.requestUpdate(position);
    }
  }
});
bg.requestUpdate(position);

var transition = {
  duration: 3 * 1000,
  curve: 'spring'
}

x.set(400,transition);

I am not seeing the behavior you are talking about.  The red logo seems glued to the top left corner for me.

Please check the screen recording: https://www.dropbox.com/s/53ua77gc38ksi6m/child.mov?dl=0

@hornos Thanks for the recording. I am also not able to reproduce what your screen recording shows on the latest version of the engine. What you are showing is a known bug in the pre v0.6.x version of the engine, which makes me suspicious that somehow you aren't on the current version. Can you reconfirm that you are on v0.6+ ?

You are right, it was an old version.Sorry for the false alarm.


python3Packages.xknx: init at 0.16.0

Motivation for this change
KNX Library Written in Python.
https://github.com/XKNX/xknx
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109301 run on x86_64-linux 1

3 packages built:

python37Packages.xknx
python38Packages.xknx
python39Packages.xknx

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109301 run on x86_64-linux 1

3 packages built:

python37Packages.xknx
python38Packages.xknx
python39Packages.xknx

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109301 run on x86_64-darwin 1

3 packages built:

python37Packages.xknx
python38Packages.xknx
python39Packages.xknx

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109301 run on x86_64-darwin 1

3 packages built:

python37Packages.xknx
python38Packages.xknx
python39Packages.xknx


Handle empty/missing meta contents

We allow our templates to be customized by end users (via liquid) and need to be robust in the face of "invalid" options, such as:
    <meta name="description" content="Demo Invoice">
    <meta name="author" content="Demo Invoice">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="pdfkit-header_html" content="">
    <meta name="pdfkit-footer_html" content="{{ footer_url }}">

There was a change way back in https://github.com/pdfkit/pdfkit/commit/4f971f4920bceccab7821caedec35f392e9baa97 (released in v0.6.2) that changed the content parser such that line 4 here would raise an error.
This PR changes that parsing regexp from + to * allowing emptystring fields to be passed through, and also be robust in the face of a pdfkit- meta tag with no content attribute.

PR still relevant.


replace for loop in loss function with sum()

This is more clear and easy to read.

Found out this will probably make the training process very unstable.


Allow tagging of NWC Profiles

Currently we can only assign a name for a NWC profile, it'd be great if I could tag a nwc profile so I could assign it to a contact. For example if I have a NWC for Zapple Pay, it would be great to tag the NWC with Zapple Pay so all the activity items have the zapple pay logo

Actually looks like this is already supported if you set the name to label you wanted, maybe this should just be a frontend feature

This was done in #815


Add Discord Injection

Yes, I am thinking about whether to do it or not. The reason that I haven't added it is that I have tried discord injection a couple of times and it broke the discord app. The app show javascript error and tries to restart just to show the error again + nothing gets sent to the webhook. Also if we do this, then it would be so much easier for someone to find the webhook. He would just have to open the file in an editor and there is our webhook, in plain text.

You could add it as optional feature

Added


[Author] Update Transmission Remote GUI to v5.12.0

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

leonsoft-kras/transmisson-remote-gui has moved to transmission-remote-gui/transgui

Thanks for the PR!

Oops, sorry, I thought I should separate them in different PR so didn't commit it together.


Error build Redis binary Apple Silicon

For some reason, when download redis binary from https://download.redis.io/releases/redis-stable.tar.gz not working property.
Different behavior occur when the binaries are download from http://download.redis.io/redis-stable.tar.gz
Compare two binaries, they're different. I fixed this changing the location from binary will be downloaded when is stable version.
Has anyone seen this?
S.O: MacOS BigSur
Version: 11.6
Make: 4.3

Interesting... I did not notice the difference between those two. Check this out:
$ curl -I https://download.redis.io/releases/redis-stable.tar.gz
-> last-modified: Sat, 27 Jun 2020 15:51:04 GMT

$ curl -I https://download.redis.io/redis-stable.tar.gz
-> last-modified: Wed, 21 Jul 2021 18:52:01 GMT

Seems we should be using the more recent version. I will create a PR.


Bulk "Set finding to Verified" set the findings to "Inactive"

Bug description
When bulk updating the findings to the "Verified" status, the "Active" findings are set to "Inactive", which seems to be a non-sense.
Steps to reproduce
Steps to reproduce the behavior:

Go to Findings view
Select 2 or more "Active" findings
Click on the Bulk Edit and submit a "Verified" status

Expected behavior
A "Verified" finding should remain "Active" as long as is is remediated of accepted.
Environment information
DefectDojo 1.5.4 RC6

Could you try with dev branch? master is very old.

The way this works is that you need to check all of the status fields that you want to become or stay checked. So if you are marking active findings as verified, you need to both check the active box and the verified box.

Ok I understand the behavior. Not the expected at first glance, but it's ok.
Related to #1875, causing some trouble to understand :)

no problem.


Unwanted extra build with flutter build ios before xcode archive

the build should happen once not twice; If you follow the official docs, which requires to run flutter build ios first then only xcode archive which will cause double build (aka: unwanted extra build) https://flutter.dev/docs/deployment/ios
and also, its has been 6 month no one answering the questions, https://stackoverflow.com/questions/61851720/what-exactly-does-flutter-build-ios-do-is-this-really-necessary
or maybe Is there a way to just trigger xcode version number without build the project with flutter cli?
ref https://github.com/flutter/flutter/issues/71909

Duplicate


VueJS missing : after property id

Hi -
We are having troubles compressing VueJS using this package, although it works just fine using the original java version. Error message:
Failed to read/parse data in file [\scripts\libraries\vue.js]
missing : after property id

Also, it would help if the error message included the line number in the JS file that is being compressed so that we can debug it more easily.

Can you put together a minimal example project demonstrating the problem?

Closing due to lack of response from reporter


Rename to onSelectTab to onSelectFeedTab

Kind (Required)

Improvement

Overview (Required)

Because there is onSelectOtherTab

Links

https://github.com/DroidKaigi/conference-app-2021/blob/main/uicomponent-compose/main/src/main/java/io/github/droidkaigi/feeder/AppContent.kt#L127

🙋

Thanks! Assigned 👍

My work conflicts with current main branch.
I assume this issue has already been resolved.

in https://github.com/DroidKaigi/conference-app-2021/pull/261
onSelectTab  was removed.

Oh.. Sorry. I didn't notice it.
I look forward to your next contribution!


Add DJM init script for EMR

What does this PR do?
Add a new Data Jobs Monitoring init script flavor for AWS EMR.
Motivation
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

/merge

/merge


Collect exploit pointers?

I am not sure we want to go there... but if so there is

PACKETSTORM https://packetstormsecurity.com/
exploitdb https://github.com/offensive-security/exploitdb
metasploit https://github.com/rapid7/metasploit-framework and https://www.metasploit.com/
Here this fork has CVE tagged https://github.com/CERTCC/metasploit-framework

exploitdb has moved to https://gitlab.com/exploit-database/exploitdb

This is a nice dataset:

https://github.com/nomi-sec/NVD-Exploit-List-Ja the license is TBD though https://github.com/nomi-sec/NVD-Exploit-List-Ja/issues/1

Also:

https://github.com/Patrowl/PatrowlHearsData is Apache-licensed
https://github.com/CERTCC/labyrinth/ by @ahouseholder now has a license and already aggregates the above.

And also https://github.com/nomi-sec/PoC-in-GitHub

We're tagging vul IDs (more than just CVE) at

https://github.com/CERTCC/exploitdb
https://github.com/CERTCC/metasploit-framework

We pull updates from their respective repositories every few hours, crawl the diffs for IDs we recognize, and then tag the commit in which the ID first appeared.

https://github.com/CERTCC/metasploit-framework/tags
https://github.com/CERTCC/exploitdb/tags

The ID patterns we look for are here:
https://github.com/CERTCC/git_vul_driller/blob/dd49cec61aac5ee9e84d57313a7876145e0b1522/git_vul_driller/patterns.py#L15-L56

https://github.com/CERTCC/labyrinth/ by @ahouseholder now has a license and already aggregates the above.

Please be aware of the notes about signal-to-noise in the Labyrinth README. An ID that shows up in Labyrinth might be because there's an exploit repo that mentions it, or it could be a number of other relatively benign reasons because our code isn't smart enough to tell the difference. Labyrinth's findings are meant to serve as input to an analysis process, not a production exploit feed.

On the other hand, we're more confident about the exploitdb/metasploit tags indicating exploits because there's a human vetting process involved (i.e., their developers decide what to include in their product).

@ahouseholder Thank you for the valuable insights. In the end, I want to know if my code is vulnerable. So the idea here with exploits is this, inc combination with reachability:

Using scancode to detect packages (PURL) or any of the many other tools that use PURLs and a lookup in VulnerableCode or in any other vulnerability DB that uses PURL I know I am potentially vulnerable
The I would like to automate as much as possible things to find out if my usage of the vulnerable package is exploitable. For this there are two tracks that I think can help:
2.1. Static reachability: given knowledge of a fix commit and a static analysis of the vulnerable library interaction with my code, do I use any of the vulnerable code paths?
2.2. Dynamic exploitability: given an exploit script (eventually curated to conform to a common interface and setup), is my configuration exploitable?

And if I am either exploitable or the vulnerable code is reachable, then I need to patch (possibly with the fix commit)

Related: https://github.com/nexB/vulnerablecode/issues/655

See discussion document at https://docs.google.com/document/d/1XtMmxthmANhr-IqXsyMgFnrOq5fTGfsE/edit?usp=sharing&ouid=117241222429542576816&rtpof=true&sd=true
See work-in-progress normalized model spreadsheet at https://docs.google.com/spreadsheets/d/1J2t2T_s015pnAouy5ss-AA0SI4e2xjT4uICjlL_Aa38/edit?usp=sharing

The proposed normalized model spreadsheet at https://docs.google.com/spreadsheets/d/1J2t2T_s015pnAouy5ss-AA0SI4e2xjT4uICjlL_Aa38/edit?usp=sharing  is ready for review.

The proposed normalized Exploits model spreadsheet at https://docs.google.com/spreadsheets/d/1J2t2T_s015pnAouy5ss-AA0SI4e2xjT4uICjlL_Aa38/edit?usp=sharing has been reviewed and ready for implementation.

@DennisClark I’ve been working on the Exploit model but encountered a few challenges:

The resources_and_notes in Metasploit is a set of options like this:

"notes": {
  "AKA": ["Zerologon"],
  "Stability": ["crash-safe"],
  "Reliability": [],
  "SideEffects": ["config-changes", "ioc-in-logs"]
}

should we store it as a JSON or just a string?

I'm also unsure about what should be stored in source_url for Metasploit, as references can include multiple URLs. Any guidance on this?

We have a decent coverage now. I am closing, and we have secondary issues available for later.


Added Ingress Greenfield sample for AKS Cluster with Windows Node Pool

Already merged this pull request on App Gateway docs
https://github.com/Azure/application-gateway-kubernetes-ingress/pull/743

@kunalbabre : Thanks for your contribution! The author(s) have been notified to review your proposed change. @caya

Hi @kunalbabre
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
For more information, see Should I work in a private or a public repo?
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
Would you create a pull request in the private repo to make these updates? We'll close this PR. Let us know if you need help moving the commits in this PR.
Thank you.


Update http4s-circe, http4s-dsl to 1.0.0-M37

Updates

org.http4s:http4s-circe
org.http4s:http4s-dsl

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

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

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

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

Superseded by #515.


Cherrypick #38911

fixes https://github.com/istio/istio/issues/38915

@ingwonsong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.14
631fac7545d1ba886286e611e5350ae480cbb57b
link
true
/test release-notes_istio_release-1.14

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio_release-1.14