Implement intial version of name resolution for items

The goal here is to implement just enough name resolution to account for imports. In particular, we don't want to resolve references in items other then use tree. We also don't want to handle macros, this time.
For the final API, I think we can reuse existing ModuleScope, but it now should contain imported items as well, including those imported via * imports. OTOH, we will use unresolved ModuleScope for other things probably, so it's also find to introduce some kind of ResolvedModuleScope thing.
Here's I think a struct analgous to this ResolvedModuledScoped in rustc:
https://github.com/rust-lang/rust/blob/6b9b97bd9b704f85f0184f7a213cc4d62bd9654c/src/librustc_resolve/lib.rs#L1047
How do we actually implement this? First of all, we need to keep in mind that in rust name resolution is tricky, because use items not only import things, but they also define them, so one import can affect another import. Here's a couple of fun examples:
// Here, resolution goes a -> b -> a
pub mod a {
    pub use crate::b::*;
    pub mod c {
        pub struct D;
    }
    type T = D;
}

pub mod b {
    pub use crate::a::*;
    pub use self::c::*;
}

// Here, we can observe "infinite" paths
pub mod u {
    pub use crate::v;

    type T = crate::u::v::u::v::u::v::S;
}

pub mod v {
    pub use crate::u;

    pub struct S;
}

To deal with this, I think we need to use a kind of fixed point name resolution algorithm.
The algorithm should build a crate-wite module scope map:
scopes: FxHashMap<ModuleId, ModuleResolutionScope>

It should start with an empty scope for each module. Then, all directly defined items should be added (what current ModuleScope is). Than, we should repeat the following algorithm until there are changes (that is, we use fixed point iteration):

pick any import which was not processed, and can be resolved using ModuleResolutionScopes computed so far
if this is a * import, which imports module a into b,

add all items from a to b
Record in some kind of hashmap, that there's a start import from a to b

if this is a usual imprt of item I into module a

add I to a's scope
for all modules, which glob-import from a, add I there as well

The "updating glob imports" bit is implemented here in rustc.
There's a bunch of existing tests we can adapt for this in Intellij: https://github.com/intellij-rust/intellij-rust/blob/9561daee8cfb24a0f8f753b9d9c3a696491428c3/src/test/kotlin/org/rust/lang/core/resolve/RsUseResolveTest.kt

@aochagavia here's the issue

Code wise, I expect this to be handled by two queries:
fn module_resolution_scope(module_id: ModuleId) -> Arc<ModuleResolutionScope> {
    let crate_root = module_id.crate_root();
    Arc::clone(crate_resolution_scope(crate_root)[module_id])
}

fn crate_resolution_scope(root_module: ModuleId) -> Arc<FxHashMap<ModuleId, ModuleResolutionScope>> {
     let res = FxHashMap::default();
     for id in root_module.submodules_transitive() { res.insert(id, ModuleResolutionScope::default()) }
     // run fixed point algo
     loop {
     }
}

Is there a difference between ModuleResolutionScope and ResolvedModuleScope in your description of the issue?

No, it’s just that half way through I’ve came up with a better name and forgot to update the first half

Status update: #236 added the basic infra. It, however, misses pretty crucial bits:

support for glob imports
support for reexports

Status update: #245 implementing proper caching. Now, module name resolution results are not recomputed if you type inside a function.

E-easy issue for folks how want to help out with nameres: fix this test.
I think this should be handled in use tree deshugaring
Here's the entry point to the code which actually resolves the import: https://github.com/rust-analyzer/rust-analyzer/blob/0cda188621b792265c957bdf4ac54af31cbc9947/crates/ra_hir/src/module/nameres.rs

I have some time, so I might try and get that working now.

This was more complicated that I expected, so I've had to leave it for now - I didn't realise we also don't handle resolving enum members either, which this sort of is. I'm not available for a few days, but I'll pick this back up afterwards if it still needs doing.

@DJMcNab sure! Though, I don’t think this should handle enum a specifically? Handling of enums would be another, E-less-easy task.

For “fixed point iteration”,
https://github.com/frankmcsherry/blog/blob/master/posts/2018-05-19.md is an awesome source of inspiration. I wonder if we could use datafrog directly...

Well I mean that handling enum members is a similar mechanism to  handling Item::self, as they both break the assumption the current algorithm makes that each step in the path is a module, and the final is an item.

as they both break the assumption the current algorithm makes that each step in the path is a module, and the final is an item.

That's true, but this assumption is not used in desugaring of use trees step, and I think we need only to tweak desugaring itself to fix the test.
Handling of enums would mean adding a new kind of Def and modifing the import resolution algo, yeah.

This has been pinned as the finishing work (glob imports) is very important for improving how well our current infrastructure works (required to bring the prelude into scope).

Is there a general plan for tackling glob imports?

@kjeremy during name resolution, we should remember the set of glob imports in the form of "module X glob-imports from Z". When we add an item to X's namespace, we should (recursively) fill Z's namespace.
When a glob-dependency edge is introduced, we should should run the same procedure for existing items.

Fixed in #778?

Or at least superceded by #732?


Fixes some edge cases around sampler resetting

I found these working on https://github.com/adriancole/zipkin-voltdb/pull/18
I don't have unit tests for the changes, but integrated looks a bit right now.
I think @pburm might be interested.

I used https://github.com/adriancole/zipkin-voltdb to integration test this and sent 4 bursts of 10 seconds of 3K+ requests/second. Using a throttled rate of 20/second it ended up quite close to correct (778 instead of 800). Note most of the gap seems warmup related and I don't completely understand that. Ex the last burst had 196 traces (20/second * 10 seconds) so quite close.

(note: this is based on export/tail sampling.. we should probably bundle this in zipkin lib so we don't have to copy/paste for collectors to use it)

Thanks @devinsba and @pburm for finding some bugs!

here's a change that uses this https://github.com/adriancole/zipkin-voltdb/pull/24


Added ability to add relationships to TagsInput

Description
This update adds the ability to create a TagsInput field that utilises a BelongsToMany relationship.
For example, a post relationship that has a ->tags() BelongsToMany relationship.
Example usage:
Filament\Forms\Components\TagsInput::make('tags')
    ->relationship(),

By default, it'll look for a BelongsToMany relationship based on the name value.
In its most basic form, if your BelongsToMany relationship matches the name you've given it (in this case 'tags') and the value column in your tags table is name, then there is no further configuration required.
However, if you need to, you can customise the relationship method and the label column that'll be used:
->relationship(relationship: 'testRelationship'), // change the method that'll be called on the model

->relationship(column: 'title'), // change the column that'll be plucked for the tag value.

->relationship('title', 'testRelationship'), // define both values

Visual changes
No visual changes
Functional changes

[ ✓ ] Code style has been fixed by running the composer cs command.
[ ✓ ] Changes have been tested to not break existing functionality.
[ ✓ ] Documentation is up-to-date.

Hi, apologies but we are no longer accepting new features for v3 as per #13744. Also, please check out our contributing guide which talks about proposing the feature before submitting the PR, to ensure you aren't spending time building something that we won't merge.
I would accept a PR for this feature when v4 is released, if you are still interested. Thank you!

Ah sorry @danharrin I didn't clock that! I'll have a look at whats required to get it converted over to v4 👍
Thanks and have a good week!


chore: move IE 10 and Android 4 to unsupported list

Dropping the support for IE 10 and android 4* versions. Bundling configurations and testing environments are changed to reflect the same

fixes https://github.com/elastic/apm-agent-js-base/issues/132

Unit and E2E Tests now use single saucelabs tunnel to improve the test speed and also parallized the tests for supported/unsupported browsers.

@jahtalab fixed with rebase.

@jahtalab I was expecting our next version would be a major one since we have not released for a long time and we already have lots of useful features. Considering all the bug fixes and features and we do have couple of breaking ones as well. Lets do 4.0.0. WDYT?

@vigneshshanmugam , I'm ok with keeping this open until we are ready to push the version 4. Although, there's more chance of conflict!
Also let's change the title of this one to BREAKING CHANGE.

@jahtalab the commit message body already has breaking change, so our change-log will include that in the Breaking Changes section. Any reason to keep this open? Didn't we already decide to publish 4.0.0 anyways?
Lets merge all the Breaking changes as well and keep it ready for publishing. Including this one #179

Sure, I think the PR should be clearly titled with breaking change as well.
We've decide to publish version 4, it was decided before as well, but we don't have an exact date so I think we should wait until the prerequisites are finished, e.g. https://github.com/elastic/apm-agent-js-base/issues/108

@jahtalab Ah got it, Sure lets wait till all steps are ready. Blocked by #108


tickFormat for scaleLog

tickFormat: v => (String(v)[0] === "1" ? v : ""),
for scaleLog
this doesn't work for values in range 0 to 1. The graph is reversed in this case

Log scales can't include 0. More info here: https://github.com/d3/d3-scale#log-scales
example here: https://codesandbox.io/s/unruffled-goldstine-2btki?file=/Example.tsx:2180-2380


Citation

Hello,
My research team us using your ddG benchmark dataset for a project we are working on. Can I know how we can cite your benchmark dataset?
Much appreciated!
Thanks!

Please cite the paper this benchmark was a part of:
A Web Resource for Standardized Benchmark Datasets, Metrics, and Rosetta Protocols for Macromolecular Modeling and Design
Ó Conchúir S, Barlow KA, Pache RA, Ollikainen N, Kundert K, et al. (2015) A Web Resource for Standardized Benchmark Datasets, Metrics, and Rosetta Protocols for Macromolecular Modeling and Design. PLOS ONE 10(9): e0130433. https://doi.org/10.1371/journal.pone.0130433
Thanks!


Minor captive-core refactorings

I made some small while going through the new captive core code.
Namely, it renames DBLedgerReader to LedgerBackendReader.

@2opremio I think this is superseded by @bartekn's PR here https://github.com/stellar/go/pull/2644

@abuiles true, at least partly.

@2opremio it seems that https://github.com/stellar/go/pull/2644 is a superset of this PR. Do you mind reverting your changes to exp/ingest/io? It will save us some time resolving conflicts.

I am happy to wait on #2644 and resolve the conflicts

@2opremio https://github.com/stellar/go/pull/2644 has been merged.

@bartekn PTAL

Changed base branch to release-horizon-v1.5.0 to be able to remove captive-core branch.


[WIP] Change require to imports (alt)

Mind fixing conflicts and address feedback I left on #145?

@Trancever mind checking that?

@thymikee I hope to help even more in the future 👍

@sidferreira amazing work, really impressive! Looks like module.exports are still there - is the intention to migrate to export syntax at some point, presumably in next PR?

@grabbou as it isn't merged yet, I can take a look on it now

No worries, we can do it after we merge this one. Shall we land it?

If you don't have anything to add then feel free to press the button!

Had to force push as I forgot to reword the PR title.


Fix button alignment on /[chainSlug]

Issue:

📝 Changed routes:

/chain/[chainSlug]

(view full size)

Commit a305ae33a852a72c9d4ba11f7e065dc711cd6180 (https://thirdweb-nlzkrmacl.thirdweb-preview.com).


Require BufRead instead of Read

Optimization - require BufRead instead of Read for consensus decode trait.

First 4 patches are preparatory cleanup.
Patch 6 uses BufRead instead of Read as the trait bound on the Decodable trait.
Patch 7 is crate level docs improvement to the io crate.

Rebasing, undraftin, and eventually merging will unblock my work on push_decode.

Lets go!

Whew, this trait has weirdly-defined methods. I had to check the std docs to be sure that we were supposed to expose the internal buffer size like that with methods like "return the remaning contents of the internal buffer, unless there are none, in which case first fill it as much as we can".
utACK.

Also note that this is not an optimization but it prevents people from accidentally writing horribly unoptimal code.

Without the blanket impl it's differently horrible (though maybe less horrible, on net). It means that we have a BufRead trait that isn't actually implemented on all the things that users expect BufRead to be implemented on. Yes, we can implement it specifically for &[u8] but then what happens when a user wants to use a file handle or something?
On second thought, in this case the blanket impl won't help them ... if they do not have std they won't get the blanket impl. So no matter what, their filehandle type needs to be aware of our io crate and its BufRead type. Ok, yeah, never mind. We should drop the blanket impl.

Since we already have Cursor I'd like to keep it for this PR. It is a very simple type and generally useful. Though I agree we don't need it on &[u8].
I'm ambivalent about switching its internal position to u64. It looks like std uses u64 (and to implement BufRead they need to cast the usize argument to a u64 internally, which I suppose hypothetically could be a bug if it was used on a 128-bit arch and somebody was trying to consume enough bytes..). I believe you're correct that the motivation for this is the Seek trait, which maybe we will want in the future.

@apoelstra &[u8] already implements Read sanely (using #[cfg] trick), it really should implement BufRead. I personally never need Cursor in practice because of the impl and would hate to need it because someone didn't write a few lines of code.
When I wrote that comment I thought blanket impls are the problem and only later I discovered that it's solvable using #[cfg] and the solution is already being used. I no longer believe we should drop them.

Just to be clear, this PR was originally @Kixunil's work in https://github.com/rust-bitcoin/rust-bitcoin/pull/2179

Draft until I resolve @Kixunil's review comments.

Aside from the bug, you previously set the PR to draft until you address my feedback but you now un-drafted it without removing remaining from Cursor...

Ha, that is a comical fail for the start of the year. I literally wondered yesterday about remaining after it appeared to come back (I must have swapped machines and not pulled), I convinced myself it was ok - face palm.

Force push removes remaining ... again. Also casts usize to u64 instead of the other way around.

Also note that this is not an optimization but it prevents people from accidentally writing horribly unoptimal code.

Is it that bad?

Thanks for the review @sanket1729, and yes please wait for @Kixunil before merging.

Changes in force push:

Used take .
Updated the commit log in the first patch.

@sanket1729

Is it that bad?

Yes. Storytime!
Back when I was a kid, I've implemented my own encryption program (yes, the horror; please ignore obvious cryptographic issues; to my defense though I wasn't defending against state-level attackers...) It took a file to encrypt and a key file which was just random noise it xorred each byte of the input file with a corresponding byte of the output file - reading and writing one-by-one.
What would one expect to take under a second took minutes (IIRC, anyway, it was clearly crazy slow) for even few hundred kB files. And as a kid I didn't know about cost of context switch and how buffering avoids it.
We don't parse byte-by-byte but there's a lot of places with similarly short reads and the only thing that actually does bulk reads are scripts and witness elements. So yes, I expect it'd be horrible to make that mistake and could be hard for newbies. Notably I still see questions on /r/rust "why is reading from file slow in Rust?" from time to time.

Changes in force push:

Fixed the comment.
Removed the new bug I just introduced this morning.

Took me a while to understand your reference to "morning". It's midnight here. :laughing:

Ok, I'm seriously having a dismal day today. I finally worked it out - I think. Please confirm that the usage of buf[1..] then call to iter is ok. I believe Rust handles this even if buf only had one element to start with but after the slice (and after todays efforts I'm not totally sure).

Back when I was a kid, I've implemented my own encryption program

The first rule of crypto is don't implement your own crypto because you probably won't get it right :P

@stevenroose how about giving an example of a perfectly reasonable code that breaks with this change? And FTR the age old API will break anyway as we change it to be push-decoding so I don't think it's a big deal to also do this.

@stevenroose how about giving an example of a perfectly reasonable code that breaks with this change? And FTR the age old API will break anyway as we change it to be push-decoding so I don't think it's a big deal to also do this.

push-decoding?

See #2184


Consider optimizing ntz=0

A lot of the packing/unpacking code has variable shifts for ntz. These are relatively expensive on Intel.
However, it is quite likely that ntz==0, so I suggest you generate a version of your code that omits these.

@klauspost I have tried, the optimisation you suggested.
Quite a lot of code gets generated!
In the end, it's about 10% faster in the case ntz=0

I don't know if it makes sense to split it into separate files. Goland is already choking on the 60KLOC file. :)
I can't really make the decision it if makes sense to include, though 10% is a nice bonus.

VSCode is better big files, unless it's full of syntax errors...
I can generate code by type, should be more manageable.


[RIP-37] Add new APIs for consumer

As we mentioned in RIP-37 New and unified APIs, establish a new APIs specifications. we divide it into two independent pull requests.
The producer part.
The consumer part.
Similar to the previous part https://github.com/apache/rocketmq/pull/3987, this pull request is about the consumer part.
related issue: https://github.com/apache/rocketmq/issues/3973

Let's merge this PR to the 5.0 branch first and polish the APIs continuously.


Support animated drawables

This should cover all kinds of animated drawables including Glide and Picasso animations as well as GIF files, based on the work from @NikitaZhelonkin (#236) and @hutcwp (#336).
You can test this by switching your dependency to the feature branch. Just add the jitpack repository to your build file and replace the existing CircleImageView dependency:
repositories {
    ...
    maven { url 'https://jitpack.io' }
}

dependencies {
    ...
    //implementation 'de.hdodenhof:circleimageview:3.1.0'
    implementation 'com.github.hdodenhof:CircleImageView:feature~transition-drawable-support-SNAPSHOT'
}

Merged to master (https://github.com/hdodenhof/CircleImageView/commit/3d1e718314c84b6a4f7e9c521973306c13303de2).


Using WebApps syncFunctionTriggers got an error due to the response status code doesn't match the status code from the operation spec

Package Name: @azure/arm-appservice
Package Version: 8.1.1
Operating system: All
[v] nodejs

version: v14

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Using WebApps syncFunctionTriggers to sync Azure functions by JS SDK got RestError. The reason is that the response status code from Azure API is 200, which is not match the status code from the spec.
To Reproduce
Steps to reproduce the behavior:

Calling the syncFunctionTriggers.

Got the error.

Expected behavior
The spec expects 204 status code from the response.

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
The fix could be adding a mapper for the response and changing the status code to 200.
https://github.com/Azure/azure-sdk-for-js/blob/99343b42a09c2ce1bb4855c39bbe1dc55b3bf2be/sdk/appservice/arm-appservice/src/operations/webApps.ts#L27007

@colawwj  Could you help to take a look see if you can repro it?

@qiaozha @colawwj  similar issue: https://github.com/Azure/azure-rest-api-specs/issues/1275

Then we need someone from the service team to fix this issue and there's nothing we can do here. . Thanks

Check with Function team PG and "synctriggers API" returns 200 but not 204: https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script.WebHost/Controllers/HostController.cs#L231 .

@racchen @kwan-su Can we close this issue now?  As there's an email thread to track on this as I know.


jazzband django push notification using DEBUG=True

This is my issue with push notification.
Problem:
With DEBUG=True. My server will not send out the crash report to sentry.io, but my server can do push notification to iOS.
Question:
How can I activate sentry agent in my server, but keep using DEBUG=True?
If it no such a thing. May I request a dedicated variable in Django environment to activate sentry. For example SENTRY_AGENT=True to let my server sends the report to sentry.io

The sdk reports errors even with debug=True, so this is a bug then. Could you tell me the Django version and if removing push notifications fixes the problem?

@untitaker
Confirm that regardless of DEBUG=True/False. My server always sends the report
I have test with simple URL
@api_view(['GET'])
@permission_classes(())
def trigger_sentry(request):
    raise Exception("test sentry DEBUG=True")

django==2.2.3
After remove push_notification from my pyenv. Sentry works like expected
DEBUG=True no report sent out
DEBUG=False has a report

Hey @elcolie
Could you try this again and see if this is still the case with the newest Sentry SDK? A lot of time passed since then, and I am just wandering if time solved this problem?
Thanks for your feedback!

So sorry. Project is suspended already 😞


refactor(apps/prod/tekton/configs/tasks): extract the task and make execlude the date tags

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Strong name code

Like all NLog libs, with the same key
fix assembly version to <IP_ADDRESS>?

So just add the NLog.snk file from https://github.com/NLog/NLog/blob/dev/src/NLog.snk and update the csproj's as required @304NotModified?
I can do this one.

Yes please!


Java LTS is linked to 17.0.1 but actually installs 1.8

$ env | grep JAVA
JAVA_ROOT=/home/codespace/.java
JAVA_HOME=/opt/java/lts
$ ls -l /opt/java/lts
lrwxrwxrwx 1 codespace codespace 6 Dec 10 19:56 /opt/java/lts -> 17.0.1

and
$ /opt/java/17.0.1/bin/java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)

It's kind of baffling. Doesn't happen for all codespaces, but it does seem reliably always to fail with this one: https://github.com/xmolecules/jmolecules-integrations (whether I open in browser or in vscode locally).

@dsyer Is this in the default codespaces image or something else?
@joshspicer Can you connect with William on this?  I assume its dynamic injection related.

@dsyer Is this in the default codespaces image or something else?

I assume. All I do is open a codespace from Github in the browser. Does it remember anything about previous sessions with this repo?

//cc @2percentsilk as well.

@dsyer Is this in the default codespaces image or something else?

I assume. All I do is open a codespace from Github in the browser. Does it remember anything about previous sessions with this repo?

It appears the repo you linked doesn't supply its own devcontainer.json with a custom image, so in that case it will use the default image.
You can also validate this by running the command devcontainer-info in your terminal. The "Definition ID" for the default image is codespaces-linux.

$ devcontainer-info

Development container image information

- Image version: 1.7.0
- Definition ID: codespaces-linux
- Source code repository: https://github.com/microsoft/vscode-dev-containers/
- Source code release/branch: v0.209.6
- Timestamp: Tue, 14 Dec 2021 00:28:37 GMT

More info: https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux/history/1.7.0.md

Why would it be any different for you?

@joshspicer The odd thing is that a repository with no contents results in 17 being linked to JDK 8.... that's the bit that is shocking.  I think it might be that the default symlink is wrong and that in cases where autodetection kicks in it works.  Very odd.

How can I test this? It is still broken if I open a new codespace on that project above?

Ah yes, although the update with this change is live in our default docker image (mcr.microsoft.com/vscode/devcontainers/universal:1),  we haven't updated our cached version in codespaces yet (we do this caching to get people into codespaces fast).
If you run a Rebuild (Codespaces: Rebuild Container) from the vscode command palette after creating your codespace, it will pull the latest image (ignoring our cache), and you should have the latest changes we're discussing above.

That said, it looks like when oryx is analyzing your project, its deciding to install version 11.0.8 of java
(from the creation.log)
2022-01-24T16:40:24: Oryx Version: 0.2.20220120.1, Commit: 9b4b24ca97b5e87c9b8fcb65ef7adb88c6f709e6, ReleaseTagName: 20220120.1
2022-01-24T16:40:24:
2022-01-24T16:40:24: Build Operation ID: |BsTM32dNplc=.cbb8fe68_
2022-01-24T16:40:24: Repository Commit : 3ddbe548d95954f830cd824dbf71dbd3d5b4d0e5
2022-01-24T16:40:24:
2022-01-24T16:40:24: Detecting platforms...
2022-01-24T16:40:24: Detected following platforms:
2022-01-24T16:40:25:   java: 11.0.8
2022-01-24T16:40:25: Version '11.0.8' of platform 'java' is not installed. Generating script to install it...
2022-01-24T16:40:25:
2022-01-24T16:40:25:
2022-01-24T16:40:25: Source directory     : /workspaces/jmolecules-integrations
2022-01-24T16:40:25: Destination directory: /workspaces/jmolecules-integrations
2022-01-24T16:40:25:
2022-01-24T16:40:25:
2022-01-24T16:40:25: Downloading and extracting 'java' version '11.0.8' to '/opt/java/11.0.8'...

@dsyer - please feel free to reopen if what i'm showing here doesn't match what you expect :)
We should be updating our cache of the docker image in the next day or so, and starting then new codespace creations will look the same as a create->rebuild (like I mentioned above).

Works for me now, thanks.

thank you for letting us know :)


Runtime query'able version information

Add new API to query Windows App SDK runtime version in use at runtime
WindowsAppSDK-VersionInfo.h at build-time provides what you're built with, but that's merely a "minimum criteria" what you'll use at runtime when using WinAppSDK framework-dependent (aka as MSIX packages). If you build with 1.2.3 you could run with 1.2.3, or 1.2.4, or 1.2.5, or...  Our services aren't available right now.

UpdateUnreliableTests.ps1 lived up to its name. Kicking off another build to test the question, "Do you feel lucky?"...

/azp run


release 0.4.0

use newer edition
version 0.4

Shall I tag this commit before or after merge? Or how does this work?
@ineiti as you know best how to release for iOS, can you take care of https://github.com/c4dt/lightarti-rest-ios/pull/9 & https://github.com/c4dt/lightarti-rest-ios-test/pull/4 please :)

https://github.com/c4dt/lightarti-rest-ios/pull/9 is still in Draft mode. For iOS, a release is simply a tag.
I think it's best to merge, and then to tag. So the tag gets attached to the main branch. I'm not sure what happens if you tag a commit and then merge.


Update PentestMapper.py

Fixed large inputs breaking csv output
Encode and compress original request and response to base64 to avoid issues with special characters breaking exported. This allows the ability to export binary related URLs if you disable the default 'App' or 'Image' exclusion

mean to pull to original author


Firebase Database setPersistenceCacheSizeBytes

I've been trying to debug my flutter app for days; immediately after building, it's been saying "lost connection to device" without giving me any stack trace or error code. Turns out it was because of this line: db.setPersistenceCacheSizeBytes(1000000);
Since the minimum is 1MB, once I set cacheSize to be 1048576 (1MB) or greater, it stopped crashing!
Here are some suggestions:

State the min and max cacheSize's in the documentation
Perhaps implement some error catching so we know what's causing the problem

Thanks 😄
Edit: this only shows up on an iOS simulator on MacOS, not on Android simulator on Windows (it might be perhaps something on my end??)

Thanks for the suggestion, @albertlai431. In the docs you reference, it does say "Cache sizes smaller than 1 MB or greater than 100 MB are not supported.". Whilst the error itself not bubbling up from the platform to your app is annoying, it is not something Flutterfire has much control over I'm afraid.


Mempool

This adds "MemPool" like service to the node.
This is not real MemPool as it doesnt contain all logic like tx validation etc.
Its function is to notify subscribers about 3 types of events:

TxUnConfirmed - triggered on protocol tx msg
TxConfirmed - every time protocol block msg arrives, MemPool checks if any of txs is is inside block, if yes it removes tx from the pool and publishes event
TxRejected - if tx from the pool is not confirmed after "expiryTime"  tx is removed from MemPool and TxRejected event it published, this is mechanism that prevents "flooding" MemPool with fake txs.

This closes #9
@tiero @altafan @louisinger please review.

LGTM but after some reading this weekend about Bitcoin protocol I think we are on the wrong track. We use the tx message to receive transactions. But by definition, tx is the "response" to a getdata message. Empirically, I agree that we receive transactions via tx once broadcast (however, the node doesn't send getdata, which is weird...) it works but I'm afraid it's not very reliable in the future (because getdata is made for objects confirmed on the chain theoretically).
I discovered another message that seems to be made for this: mempool. It's an extended version of getdata that allows to retrieve unconfirmed transactions from a peer. https://en.bitcoin.it/wiki/Protocol_documentation#mempool
the mempool.go implem is OK in my opinion but I would add mempool msg support on nodeService to sync the mempool map instead of tx msg

I'll test this ASAP, but the tx rejection doesn't convince me: maybe this node should reject a transaction only when receiving a confirmed one that spends at least one of the inputs of the former.
Also, rejection is a nice-to-have feature but not a fundamental one because it can be handled client-side. For me it's ok to eventually add it later, but for some this kind of timeou-based rejection is wrong because the waiting time for a tx to be included in a block is not predictable.

Also, rejection is a nice-to-have feature but not a fundamental one

i do believe we should have a mechanism in place: instead of timeout/expiration based, I would simply have a size approach: ie. max 100MB of space, if we go over to that limit we start prune (ie. best term than reject) the old transactions starting with the oldest first (therefore we should have a "first seen" timestamp)

I discovered another message that seems to be made for this: mempool. It's an extended version of getdata that allows to retrieve unconfirmed transactions from a peer. https://en.bitcoin.it/wiki/Protocol_documentation#mempool

I had same doubt but i decided to use tx based on following:
In wiki page there is "It is specified in BIP 35. Since BIP 37, if a bloom filter is loaded, only transactions matching the filter are replied."
With BIP37 SPV client loads bloom filter to the full node with filterload msg, then with mempool msg full node return txs based on prev loaded filter. But since BIP37 has known issues(privacy, dos) BIP157&BIP158 defines other way in which full nodes generates and  sends block filters to SPV clients so that they can do verification, which we are doing in our proj.
My understanding is that we would need use BIP37 and load filter which as said is not good for privacy(there is question also on how we can trust full node about data it is sending).
Also i was checking btcd code and what i found is that after tx is added to mempool it is "announcing" tx to its peers by sending inv msg in here.

Also, rejection is a nice-to-have feature but not a fundamental one ...

Originally, requirement was to have "UnConfirmed" notification, i was thinking it would be nice to have(at least for testing) other two event(Confirmed, Rejected).

i do believe we should have a mechanism in place: instead of timeout/expiration based, I would simply have a size approach: ie. max 100MB of space, if we go over to that limit we start prune (ie. best term than reject) the old transactions starting with the oldest first (therefore we should have a "first seen" timestamp)

This can be complementary to my proposal, keen to have a discussion on it, but what I'm trying to say is that since we are still not aligned on this, i wouldn't add code that it's likely to be changed in the future.

Originally, requirement was to have "UnConfirmed" notification, i was thinking it would be nice to have(at least for testing) other two event(Confirmed, Rejected).

We do already have notifications for confirmed transactions, what we need now is a way to get them also for unconfirmed ones indeed.

We do already have notifications for confirmed transactions, what we need now is a way to get them also for unconfirmed ones indeed.

Agreed! Let-s start with basic support for unconfirmed first (so lets drop Reject notification and expiration time for now), and handle spam/dos attacks (for not valid/censored txs filling the space on the neutrino node).
I do think would be nice tho to add in this PR a "first seen timestamp" field on each tx

TestSendTransaction seems to fail. Rather remove it if not used/unstable


Fails to yarn install

Bug Report
Describe the Bug
Executing quick start tutorial for developer failing to yarn install".
What steps can we follow to reproduce the bug?
OS: latest MacOS

Execute the quick start tutorial.
For installing node.js and yarn user brew.
The yarn install step gives the following wanting and error:

(base) shkolyar@SPB Viewers % yarn install
yarn install v1.22.18
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>warning Resolution field "<EMAIL_ADDRESS>is incompatible with requested version "<EMAIL_ADDRESS>[3/5] 🚚  Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^12.13.0 || ^14.15.0 || >=16". Got "14.8.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

:warning: Reports we cannot reproduce are at risk of being marked stale and
closed. The more information you can provide, the more likely we are to look
into and address your issue.

Hi, I had the same issue, I had to switch to node v14.15.0 as mentioned in the error which resolved the issue.

Same issue - changed dockerfile from
FROM node:12.22.1-slim as builder
to
FROM node:14-slim as builder
and the application started as expected.

Please review the latest code in the master branch. I am confident that this issue has been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing


[AAP-11261] Add MQTT event source

Adding an MQTT event source for rulebooks - Tested

hi team, any news on this one?

@kubealex
Hi, thanks for introducing this plugin!
I have created small patch with following changes for your branch to make it work with the latest collection: https://github.com/kubealex/event-driven-ansible/pull/1

Merge latest main branch
Move mqtt.py from extensions/eda/plugins/event_sources to extensions/eda/plugins/event_source where other plugins are placed
Remove dict from import to avoid the error ImportError: cannot import name 'dict' from 'typing'
Add aiomqtt to requirements.txt to make Ansible Builder installable required modules for this plugin

Thank you @kurokobo! I just merged your contribution into the branch 🚀

I am very much looking forward to seeing this merged. :)

I've been using this patch locally and has been working as expected, thanks!!

Hi @kubealex
We want to express our sincere appreciation for your effort and contribution. After careful consideration, we have concluded that this plugin doesn't align with the scope of our official collection, and unfortunately, it will not be included. It might be a better fit for a dedicated collection of curated plugins for Kubernetes.
However, this does not diminish the value of your work. We believe your plugin can still be highly beneficial and encourage you to offer it through your own collection. You are welcome to upload it to galaxy with the "eda" tag.
As a fellow Red Hatter, we also suggest reaching out to your product management team to explore if such a collection could be supported within Red Hat as a maintained collection.
Thank you for your understanding and contribution.

Thank you for the feedback Alex, much appreciated!
@jpmens @tonyskapunk and anyone who could be interested in using or including it, no worries, I'll leave it here [1] the link to the custom collection that includes the plugin.
[1] https://galaxy.ansible.com/kubealex/eda

@Alex-Izquierdo
Hi, thanks for working on this.
Do you have any plan to update the documentation for Ansible Rulebook?
In the documentation, the mqtt plugin is mentioned as example of Event Bus Plugins.

Event Bus Plugins
These are plugins that listen to a stream of events from a source where the connection is established by the plugin itself.
Examples of this are the kafka and mqtt plugins.
https://ansible.readthedocs.io/projects/rulebook/en/stable/sources.html

This is why I reached out here to find the status of MQTT plugin. This documentation might cause users misunderstanding that an officially maintained MQTT plugin exists (yes, I am one of the users who misunderstood).
It would be great if the MQTT plugin is officially implemented as the documentation shows, but since as you stated this plugin no longer merged into this collection, the documentation should be updated.
Please let me know if I should create an issue in ansible-rulebook or create a PR to remove MQTT from the documentation. Thanks in advance!

Thanks for raising this issue @kurokobo
It will be fixed on https://github.com/ansible/ansible-rulebook/pull/590

Thanks for rapid update😃

@kubealex thanks for the link to the custom collection that includes the plugin (https://galaxy.ansible.com/kubealex/eda), but that is 404 which, I assume, is because of the transition from Galaxy to -NG.
The current link is https://galaxy.ansible.com/ui/repo/published/kubealex/eda/ but I think it's probably safer to mention the link to your repository at https://github.com/kubealex/kubealex.eda


Timeout

i get this error always
HTTPSConnectionPool(host='services.nvd.nist.gov', port=443): Read timed out. (read timeout=30)

Hi,
This error usually means that your system you are running NVDLib on is failing a connection to the NVD API, and not a problem with the NVDLib library itself. I suggest ensuring your internet connection doesn't disconnect, or troubleshooting why your computer is failing to establish a connection the NVD API at "services.nvd.nist.gov".
Thank you,
vehemont

My internet connection is good, but the NVD service has a problem

I was able to replicate this issue using the following command: r = nvdlib.searchCVE(keywordSearch='Microsoft'). I do believe there is an issue with the NVD API as you have stated. I see requests taking upwards of over 60 seconds but on average 45 seconds, which is above the threshold for NVDLibs 30 second timeout. I have reached out to the NVD team with this finding and will reply to this issue once I receive a response.

I get the same error on my side including 503 Server Error: Service Unavailable for url. Thank you @vehemont for reaching out to the NVD team.

I received an update that the NVD API is having issues at this time and the team is aware. I'll keep this issue open to post further updates and for visibility.

Thank you for notifying the NVD. We are aware of timeout errors being provided to users of the vulnerability search page and APIs and are currently investigating the root cause for resolution. We apologize for the inconvenience during this time.

@vehemont Thanks for your update

Hi,
Please also consider https://github.com/vehemont/nvdlib/pull/38
Regards,
Titus

occasionally (Asia region)

I got an update from the NVD that they are still trying to resolve the 503 errors:

Thank you for the feedback email. We are aware of the current performance issues with the API (specifically the 503 errors) and are actively working to address them.  We apologize for the inconvenience.

The issue still for now

I am no longer receiving timeout or 503 errors. Can someone else confirm before I close this issue?

I can confirm that.
Thank you for creating and maintaining nvdlib!
From: vehemont @.>
Sent: Thursday, January 18, 2024 12:44 PM
To: vehemont/nvdlib @.>
Cc: johnlabuyfoy1024 @.>; Comment @.>
Subject: Re: [vehemont/nvdlib] Timeout (Issue #37)
I am no longer receiving timeout or 503 errors. Can someone else confirm before I close this issue?

Reply to this email directly, view it on GitHubhttps://github.com/vehemont/nvdlib/issues/37#issuecomment-1898938518, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCWEONOUXCA4KSTPB3R23TYPFNOHAVCNFSM6AAAAAA7X4ZJZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYHEZTQNJRHA.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

I still get this error everyday:
403 Client Error: Forbidden for url: https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=pandas&virtualMatchString=cpe%3A2.3%3Aa%3A%2A!

@vehemont The issue still occurs for me ,, you don't get the same?

@vehemont The issue still occurs for me ,, you don't get the same?

I do not receive any 403 error. This usually means you are hitting the rate limit in some way. You could try setting the delay parameter to something like 12 seconds, instead of the default 6 seconds. Using the same API key on multiple instances can induce the rate limit error since they are tracked with the same rate limit. This is also true if you are accessing the NVD API with multiple instances from a single IP address with no API key.

@vehemont You are right, I fixed it, thanks


AttributeError: 'DiscoveryV1' object has no attribute 'get_environments'

I get this error when running the app in bluemix. It then crashes.
It looks like watson_developer_cloud.DiscoveryV1 has changed its API.

thanks @deveops we'll take a look at this

reproduced

Closed with #120

Looking at #120 shows that now we need to use list_environments instead.


JAVA-2312: Handle UDT named "tuple" in metadata

Out of curiosity, what happens if the UDT is named list or frozen, will that work as expected?

🤦♂ you're right, I don't how it didn't occur to me to check that. list, map and frozen are also valid UDT names, set isn't.


Implementing "after" logic when ripping reddit-stuff

Right now, if I run
java -jar ripme.jar -d -t 25 -u "https://www.reddit.com/user/userid"
ripme will run through the userid and download all the submissions, the ones already downloaded will be skipped, but ripme will still try to download them.
If ripme could remember what the last submission it downloaded was, the next time I ripped the same user, ripme could resume where it last stopped.
The reddit API has the after-tag which you could easily save in a textfile, then the next time the userid is ripped, read the textfile and resume from there.
This would also solve the "problem" of deleteing unwanted files. Since ripme will resume from the last submission it downloaded last rip, it will not re-download old files.
Also, if you want to re-download a user, just delete the textfile with the after-tag

I have been considering this as well. One concern with the "if you want to re-download, just do XYZ" is that sort of thing gets to be pretty terrible when there's a different way for each kind of album. I'd like to attach this to some global setting for all rerip-related things. There's a number of issues open related to improving re-rip scenarios. The general solution is to save a list of links to actual image files that have already been downloaded and not re-download those. To optimize for certain sites like reddit, we could have additional logic for most recently ripped.
Note: the reddit ripper actually starts at most recent and works backward. Wouldn't necessarily be required to filter with the after-tag if the link of the most recently ripped post were saved, but that would certainly help.
Also, I want to make sure we continue to support the scenario where you had to cancel a rip when it was partially complete for some reason, but it was still working backwards. You'd still want to continue ripping the stuff you hadn't yet ripped that was older when you resumed. So the logic for saving and resuming based on the most recent link only should only be enabled if it is the case that the rip previously completed the entire rip completely and successfully (modulo 404s).


Processor Consumption [Too High]

I was testing on a virtual machine without a GPU and to my surprise the processor consumption of it is too high and slowing down the other processes. Is there any way to make it consume less power?

Set lower bitrate, maybe it will help
Video encoding is computationally heavy operation...
You can also change the encoder but that will require to rebuild c++ code

Hey, @Andrey1994 , i am already on a relatively lower bitrate and can't go any further down. Can you just point to the code block in your package where the encoder is specified. I can't seem to find it.

you can change this line https://github.com/Andrey1994/screen_recorder_sdk/blob/master/src/ScreenRecorder/inc/MFEncoder.h#L37
if it does the trick, maybe it makes sense to make it configurable from python code(user api), PR for that will be welcome
I believe here all possible options are listed https://docs.microsoft.com/en-us/windows/win32/medfound/video-subtype-guids
to rebuild and reinstall it you will need to compile locally first using https://github.com/Andrey1994/screen_recorder_sdk/blob/master/cmake_build.cmd(you will need cmake and vs)
after that reinstall the python package from a local folder using commands like:
cd python
python -m pip install -U .


FIX Reports linking to pages now use the correct CMS edit link

Fixes https://github.com/dnadesign/silverstripe-elemental/issues/629

Maybe we should just sent both of those links straight to the page, since inline editing is likely to become the default behaviour going forward

Alright I've just updated it so it works

Technically it’s a breaking change, but I’m ok with it

getEditLink() probably should be @internal anyway 😉


PeerMetrics: interpolate results when inserting a new peer

Description
This PR makes sure that newly added peers to PeerMetrics are never in 20% of worst performing peers.  Currently the churn interval and number of records kept by PeerMetrics are in sync, peers added just before the churn event can be removed as they might have too few results.  In the future the churn interval and the number of records kept by PeerMetrics might diverge, and thus it's more important to make sure that newly added peers are not immediately removed.
This PR solves this problem by keeping track of average results when a peer joined the leader board and is using linear regression to adjust peer results for the leader board period where the peer was absent from the leader board.
Fixes #3861
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

bors merge


Feature Request: Use Document Picture-in-Picture Web API

Users should be able to use the Shaka Player in a Picture-in-Picture window, not just the HTML video inside the web player.

Before the Document Picture-in-Picture API, it was only possible to put an HTML <video> element into a Picture-in-Picture window. This new API makes it possible to open an always-on-top window that can be populated with arbitrary HTML content. It is available as an origin trial starting in Chrome 111 on desktop.
async function togglePictureInPicture() {
  // Close Picture-in-Picture window if any.
  if (documentPictureInPicture.window) {
    documentPictureInPicture.window.close();
    return;
  }

  // Open a Picture-in-Picture window.
  const pipWindow = await documentPictureInPicture.requestWindow({
    initialAspectRatio: 640 / 360,
    copyStyleSheets: true,
  });

  // Move video to the Picture-in-Picture window.
  const video = document.querySelector("#video");
  pipWindow.document.body.append(video);

  // Listen for the PiP closing event to move the video back.
  pipWindow.addEventListener("unload", (event) => {
    const videoContainer = document.querySelector("#videoContainer");
    const pipVideo = event.target.querySelector("#video");
    videoContainer.append(pipVideo);
  });
}

Documentation:

https://developer.chrome.com/blog/the-future-of-picture-in-picture/
https://developer.chrome.com/docs/web-platform/document-picture-in-picture/
https://github.com/WICG/document-picture-in-picture/issues

@beaufortfrancois are you interested on send a PR for this?

Thanks @beaufortfrancois !


Make manifest metadata configurable

at the moment it's tied to required fields, but if this were a config then it would be easy to change without overriding code
(this would be a PR to Hyku)

This will be a config in Hyrax.


Error in Luis: 'Forbidden'

Hello,
In samples, all luis returns exception: 'Operation returned an invalid status code 'Forbidden'
Even making a new empty project in Azure, the same error occurs with all the default settings

Hello. Did you configure your bots to use valid LUIS endpoints and keys?

@PDVSeven - Are you still working on this?

Closing due to lack of activity


Explain analysis mode and protection mode in readme

We currently do not have an explanation.

Additionally, we should update the permissions section as it is slightly out of date.

This should also include the Wiki.

I cleaned up our ReadMe a bit, should be looking alright now.


Java 8 examples fixup: add SNAPSHOT repository & add bundling configuration

R: @francesperry

LGTM -- thanks.

Coverage remained the same at 70.088% when pulling 97adef2e7b749623624bd8a94a0eed45d5d6396f on davorbonaci:examples into 59451bca60ef45b1daeb14b8194bac0f8bdcc98b on apache:master.

Coverage increased (+0.01%) to 70.095% when pulling a6f5ad75dcd95d2511e7c8de2cd7c31feae338dc on davorbonaci:examples into 9541f8fcc505830a24decb8a69b82532e9a8f69c on apache:master.

(unrelated failure, merging)


Route53 private zone support

support for HostedZone.Config.PrivateZone=True

Thanks for this. One question, but otherwise happy to merge

Great, thanks!


Update example project

if we update the example project we won't be able to judge if will still keep the backward compatibility with all 1.x.x versions

if we update the example project we won't be able to judge if will still keep the backward compatibility with all 1.x.x versions

I thought we use example_project as more of showcase and projects in tests/test_data/test_projects are used for checking backwards compatibility .

ok, you are right, we have still project in test to keep backward compatibility indeed


Make triton backend work again

Global loops with 4 or more dims, local, and cast aren't implemented.
4 or more dims should be easy to fix. Local should use block pointers(?) or tl.arange(). I think cast is ok not implemented? Since its only used for float4?

Can you get triton (and CUDA) in CI? That's what's really needed to make them first class citizens.

Sure, should I just add runners to test.yml? Or write additional tests?

The issue is how to do it :)

Hmm, it looks like the simplest method is to use a self-hosted runner with a GPU. Unless there's some consistent method for emulating CUDA on CPU.

Yea, I might have to do that. I got $5k in AWS credits to burn, wonder what the cheapest machine is and how easy it is to set up?

I looked a bit into this, and it looks like there are a couple projects to emulate CUDA on CPU, but most of them seem abandoned. Apparently nvcc even used to support outputting CPU code but that feature was dropped a long time ago. Everything else is third-party, at various levels of unmaintained:

gpgpu-sim
CU2CL
gpuocelot
MCUDA

I'm sure there are many more, but this is most of what I found.

Yea none of these look great. I'm standing up a self hosted machine with a 3080 Ti now.

Getting a bunch of failures with TRITON=1 pytest

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/runtime/ops_triton.py           113               0
------------------------------------------------------------
lines added in the tinygrad folder: 113

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/runtime/ops_triton.py           113               0
------------------------------------------------------------
lines added in the tinygrad folder: 113

I fixed four or more dims upstream.

Added $200 bounty for fixing this (all tests pass) + testing this + CUDA in CI.

We are close to CUDA CI and can revisit this.

Sorry about the long hiatus on this, got pretty busy and working on this fell to the wayside.
test/test_ops.py is now fully passing, but there are still a fair amount of tests that need some work. In particular, all types except float32 are broken (I'm not sure how to typecast in triton).
Also, I need to figure out how to make sure that reduction/local loops are actually getting parallelized (this may require block tensors) and implement emulated testing using gpuocelot.

Ahh, cool. Locking the bounty to you. Check out my work in #1085 on the actually getting parallelized.

Sounds good. I'll start by getting the CI working and fixing the bugs, and leave the parallelization to @ptillet. With regards to the test_dtype.py errors, is there a reason why computations are done all in float32? The two failed tests I'm still getting are matmul in fp64 and fp16, since the reduction is computed in fp32, and I haven't figured out how to cast in triton yet. Should I switch to doing computation in the respective precision or cast to fp32?

All computation should be float32.

Ok sounds good, I'll use cast in the triton code.
As far as I know the ops tests are real, perhaps triton is automatically figuring out how to optimize reasonably well.

Ok almost all the tests are passing locally now. The only tests not are a couple of the model tests in test_efficientnet.py and test_onnx.py, which seems to be a problem with the CUDA backend overall.

Those test failures are fine, see comments above.

If tests pass, I'll merge and the bounty is yours.

So the Triton test wasn't actually running Triton, it was running CPU since there was no CUDA=1.
Fixed, now sadly test is failing.

Missing pycuda from dependencies

Hmm, so the error in CI is that the version of torch installed doesn't have CUDA support. Not sure if it's possible to force pip to install the CUDA-enabled version in CI (or whether that would even work if it is possible). I also was looking into using @triton.jit(interpret=True), but it looks like this requires torch with CUDA too. Triton can also produce HIP code, which may be easier to emulate? Otherwise I may need to create a shim for torch that still allows triton to generate PTX to test with gpuocelot.

@christopherm99 do the tests pass locally? were you able to generate triton code conducive to tensor cores and peak perf? if yes i'm willing to see what I can do. Triton in interpreter mode shouldn't require torch-cuda.

Almost all the tests pass locally (still need to fix up a few bugs). The generated triton code is definitely suboptimal however, as far as I know tensor cores are not being used. It looks like triton relies on torch-cuda to detect the local gpu capabilities and various other minor things (if I can successfully hardcode shim torch-cuda out of triton, I'll have a list of the dependencies).

How is this coming?

Going to unlock bounty in 24 hours.

Am starting work on this. If I finish this, pls send bounty money to @christopherm99 as he did most of the work and this is very low hanging fruit at this point.

Am starting work on this. If I finish this, pls send bounty money to @christopherm99 as he did most of the work and this is very low hanging fruit at this point.

Upped bounty to $300 for this, we need it brought across the finish line!

Closing in favour of #1547


Fix 'TypeError: Invalid URL'

Fix an issue of import.meta.url being undefined, in which case Node.JS throws an exception TypeError: Invalid URL.
Got this error when attempted to run compiled by esbuild code of my CommonJS project - probably import.meta.url is set to undefined in CJS and to the correct value for ESM.

Hm, I was afraid we were going to run into an issue like this.  I think I'd like to fix this a different way, using https://github.com/hildjj/package-extract to pull the bits we need out of package.json at compile time.  I think that approach should work in all situations.
I'm going to leave this open, whip up a parallel PR, and ask for your review.

Just found a much better way to solve this issue, seems to be simple and elegant:
import {name as pkgName, version as pkgVersion} from '../package.json';

Sorry, I just realized my tests aren't running correctly on pull requests, or you would have seen errors when you pushed this change.
Imports from JSON files don't work in node.js unless both of these things are true:

node.js v20.10 or later
you add with { type: "json" } at the end of the import

I'm still going to support node.js v18 until it goes end-of-support in April 2025.
Given that, I think #59 is a better solution, unless you have an issue with that approach.

@hildjj, If you don't like the above idea of using the require statement, then just pull #59

Closed in favor of #59


Update SVT-AV1 to v1.8.0

Updates the SVT-AV1 repo commit to 5fbddb53b3dc1a32f35ade563e2f6d32dc500417.
Old version is v1.7.0-17-ga49c786a.
Chanelog below

Encoder

Improve the tradeoffs for the random access mode across presets:
Speedup CRF presets M6 to M0 by 17-53% while maintaining similar quality levels
Re-adjust CRF presets M7 to M13 for better quality with BD-rate gains ranging from 1-4%
Improve the quality and speed of the 1-pass VBR mode
More details on the per preset improvements can be found in MR !2143
Add API allowing to update bitrate / CRF and Key_frame placement during the encoding session for CBR lowdelay mode and CRF Random Access mode
ARM Neon SIMD optimizations for most critical kernels allowing for a 4.5-8x fps speedup vs the c implementation

Cleanup and bug fixes and documentation

Various cleanups and functional bug fixes
Update the documentation for preset options and individual features

I somehow missed this. Should have been part of the last dependency updated already.


fixed zoom issue

Page was breaking on zoom in/out  (eraser icon was vanishing on zoom in)  which has been fixed.
Fixed #6

@DhairyaBahl Have a loot at this!

@sunidhisachan LGTM !

Merged.


Any luck with Logitech C920

Hey All,
I am working on a new project and trying to use a HD Pro Webcam C920 with the simple video filter example. When ever I try to use that camera (or any other external camera) the screen is blank. Does the code below look correct? The only difference between my code and the example is the final argument to initWithSessionPreset where I am passing device instead of nil.
for ( device in [AVCaptureDevice devices] ) {
         if( [device.localizedName isEqualToString:@"HD Pro Webcam C920"] )
        {
            break;
        }
    }
    videoCamera = [[GPUImageAVCamera alloc] initWithSessionPreset:AVCaptureSessionPreset640x480 cameraDevice:device];

Thanks in advance,
Joe

So I actually have a Logitech C920 here as part of a test rig (it's what I tested the GPUImageAVCamera code against), and I can get it to connect just fine in the FilterShowcase sample. I used the following code as a modification of the SLSFilterShowcaseWindowController in the windowDidLoad method:
    AVCaptureDevice *cameraToUse = nil;
    for (AVCaptureDevice *connectedDevice in [GPUImageAVCamera connectedCameraDevices])
    {
        NSLog(@"Device: %@, UUID: %@", connectedDevice, [connectedDevice uniqueID]);
        NSLog(@"Device: %@, name: %@", connectedDevice, [connectedDevice localizedName]);

        if ([connectedDevice.localizedName isEqualToString:@"HD Pro Webcam C920"])
        {
            NSLog(@"Device found");
            cameraToUse = connectedDevice;
        }
    }

//    inputCamera = [[GPUImageAVCamera alloc] initWithSessionPreset:AVCaptureSessionPreset640x480 deviceUniqueID:@"0x1d111000046d082d"];
    inputCamera = [[GPUImageAVCamera alloc] initWithSessionPreset:AVCaptureSessionPreset640x480 cameraDevice:cameraToUse];

and that seemed to do the trick. The camera connected and started displaying just fine with that. I also did it with the device ID, to make sure that connected properly too.

Like a charm!Bring on the new project.
Thank you Brad!
From: Brad Larson<EMAIL_ADDRESS>To: BradLarson/GPUImage<EMAIL_ADDRESS>Cc: Joe<EMAIL_ADDRESS>Sent: Friday, April 24, 2015 9:35 AM
Subject: Re: [GPUImage] Any luck with Logitech C920 (#1971)
So I actually have a Logitech C920 here as part of a test rig (it's what I tested the GPUImageAVCamera code against), and I can get it to connect just fine in the FilterShowcase sample. I used the following code as a modification of the SLSFilterShowcaseWindowController in the windowDidLoad method:    AVCaptureDevice *cameraToUse = nil;
for (AVCaptureDevice *connectedDevice in [GPUImageAVCamera connectedCameraDevices])
{
NSLog(@"Device: %@, UUID: %@", connectedDevice, [connectedDevice uniqueID]);
NSLog(@"Device: %@, name: %@", connectedDevice, [connectedDevice localizedName]);
    if ([connectedDevice.localizedName isEqualToString:@"HD Pro Webcam C920"])
    {
        NSLog(@"Device found");
        cameraToUse = connectedDevice;
    }
}

//    inputCamera = [[GPUImageAVCamera alloc] initWithSessionPreset:AVCaptureSessionPreset640x480 deviceUniqueID:@"0x1d111000046d082d"];
inputCamera = [[GPUImageAVCamera alloc] initWithSessionPreset:AVCaptureSessionPreset640x480 cameraDevice:cameraToUse];
and that seemed to do the trick. The camera connected and started displaying just fine with that. I also did it with the device ID, to make sure that connected properly too.—
Reply to this email directly or view it on GitHub.


Can we get rid of the pagination?

Since we can expand interfaces, one often has to scroll, but we also have pagination. Could we always use a single page instead?
Probably wouldn't fix https://github.com/GoogleChrome/confluence/issues/165 but may be related.

That seems feasible. Something like this should do the trick.

Pagination is long gone!


refactor: preset slugs

@Kikobeats this is the initial progress of the preset slugs as we discussed, I've just used Bytes and Humans as an example for now.
It's all working fine, however it's not as I'd like for the generate-previews script. Due to the setup, the filename has to match the generated slug. That's ok for bytes-and-humans.js, but I would love if preset names could include special characters.
To achieve this we'd need to know the preset's name within the script (instead of the filename), to be able convert it to the slug.
What do you think, any suggestions?

Looks good 👍
I understand your point related to generate-previews script; what we can do is to throw an error under mismatch, that should be more than enough since still we are going to review every PR that adds a new preset.
Also, I think it's a good moment to improve the seo now you have the name preset 🙂

Thanks @Kikobeats, I made some adjustments that should resolve the potential generate-previews issue in the case of special characters. Instead of escaping them with encodeURIComponent I simply strip them. For example, the preset I've adjusted - Next.js Conf - would be converted to nextjs-conf, and therefore matching the filename.

Want me to add a CONTRIBUTING file with some simple instructions, including the naming?
Is the build failing because of replaceAll? I was running the site with node v12 on local and it failed, switched to v16 and all ok, but if the Vercel build is taking the version from the engines property it could be that.
What do you think about splitting the SEO into a separate task? Just to keep the PRs as bite-size as possible.


Electricity Cost Calculator Added.

Fixes Issue🛠
Closes #355
Description👨💻
Electricity Cost Calculator to accurately calculate electricity costs based on user-supplied units, time, and cost parameters.
Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅
Completely Tested in Local Environment.
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

The new recent change and PR which is updated is here : #391 Thank you !


Suggestion

Hi,
I have the same idea for an extension, and was happy to land here and see it already implemented.
For my idea, I intended to use VSCode built-in settings to manage the bundles, what do you think of that idea?
The idea is to add a user-level setting
 "extension.bundles": {
     "Python”: {
         "extensions": [
              // list of extensions....
            ],
           // maybe more configurations here, e.g. 'inherit bundles'
        }
"extension.globalBundle": ... // not sure if needed actually, maybe?

then, in the vscode workspace settings I would have:
"extension.profile": {
   "bundles": [...]
}

This way everything uses VSCode internal sync mechanism, and is git friendly.
Do you think this is something that you would want for your extension to have/use?
Maybe you have already considered it and decided to not use this design, I guess.
I haven't tried your extension just yet, but I'm definitely going to give it a try. This was something I was missing.

Hi,
I did used the settings at first but whenever you had bundles defined, there was a huge block of json used for my extension only that was 5-10 times bigger than the whole vscode settings without it.
It is possible but not really nice to edit (and even worse when trying to edit another application's settings around all that json block)
The last downside is when you try to remove my extension, you would have to remove those blocks manually form the vscode settings.

That makes sense. Thanks for explaining.


Upgrade Chart.js usage for version 3 (or latest if newer)

Curtis Delicata is scamer. He doesn't pay any profits. Don't work with him.


[REQUEST] Workarounds for powering off GPU in hybrid mode

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. When using hybrid mode, the nvidia gpu keeps taking power. The command nvidia-smi finishes immediately and there is a Xorg / gnome-shell process using GPU memory.
My laptop is Zephyrus G14 2020 with R7-4800HS and RTX 2060. The computer is running GNOME with wayland.
Describe the solution you'd like
Recently I followed https://github.com/SnipeXandrej/zephyrus-g15-tweaks and it seems to fix the problem. nvidia-smi takes time to activate the GPU and there is no process running on the GPU.
So maybe it is worthwhile to integrate a few workarounds from the repo?

Hello,
I understand your concern regarding disabling the Nvidia dGPU. It's important to note that some of these tweaks may have unintended consequences for other users (eg: using modesetting 0 or deleting an EGL library).
One potential solution could be to make this feature opt-in through a CLI option. However, at the moment, there are no immediate plans to introduce additional features.
Feel free to submit a PR in the meantime ;)

@ZZYSonny Try adding ibt=off to grub if it's not there, on the Nvidia github some people wrote that it helps them.

I also found that enabling nvidia-persistenced.service also seems to fix rtd3.

@bayasdev I ran tests with a gtx 1650 video card with the service enabled consuming 16 watts at idle with it turned off 32 watts

Must be fixed in
https://github.com/bayasdev/envycontrol/pull/127/commits/f7941af475b6d97bf19cc09f81d78018a41d7669

@bayasdev This can be closed as the bug has been fixed.


Dark titlebar in classic CMD is broken in Insider builds

Environment
Windows build number: 10.0.18985.1 (Sorry for being outdated, I haven't been able to update to a more recent Insider build)
Windows Terminal version (if applicable): N/A

Any other software? No

Steps to reproduce
Open cmd.exe compiled from this repo or built in Windows.
Expected behavior
The titlebar is black, like in the current stable Windows.
Actual behavior
The titlebar isn't black:

Does the tittle bar becomes black when you click on the window?

The window is active in this screenshot

Funny enough -- you filed this shortly after I saw an uptick in log entries (in a local dev build) about this API failing. Thanks!

The API used is technically undocumented and got moved to WCA_USEDARKMODECOLORS in the also undocumented SetWindowCompositionAttribute API, IIRC.
IMO it should be documented, because other apps might also want a dark titlebar, especially if they have a built-in dark theme because the white titlebar becomes an eye sore.

Hey! The fix for this went out in Windows in the Insider channel's Fast Ring with build 19013.

The API used is technically undocumented and got moved to WCA_USEDARKMODECOLORS in the also undocumented SetWindowCompositionAttribute API, IIRC.

Thank you! Can confirm that such change works.

IMO it should be documented, because other apps might also want a dark titlebar, especially if they have a built-in dark theme because the white titlebar becomes an eye sore.

Exactly.

We don't disagree with you.

Finally got to update my insider build after windows update kept refusing, can confirm it works (third party apps are still broken so they'll have to move to SetWindowCompositionAttribute).
The code here also hasn't been updated https://github.com/microsoft/terminal/blob/9b92986b49bed8cc41fde4d6ef080921c41e6d9e/src/interactivity/win32/windowtheme.cpp#L47


Release - Signer Fix

Try out Leather build 7624c0a — Extension build, Test report, Storybook, Chromatic

This release contains fixes for:

https://github.com/leather-wallet/extension/issues/5243
https://github.com/leather-wallet/extension/issues/5255
https://github.com/leather-wallet/extension/issues/5251

Why would we release this w/out Runes included?

Why would we release this w/out Runes included?

I've added the Runes UI work https://github.com/leather-wallet/extension/issues/5246 . I didn't want to merge your PR again.
If there is more stuff to add we can before releasing. Maybe this PR? https://github.com/leather-wallet/extension/pull/5179

We will need to add https://github.com/leather-wallet/extension/pull/5262 also

If there is more stuff to add we can before releasing. Maybe this PR? #5179

We can leave https://github.com/leather-wallet/extension/pull/5179 for the next release. I am still finishing some refactoring there.

I forgot to add the default Runes symbol to my last PR. I will get the change merged then update the release branch.


Geometry buttons style refactor

This PR fixes #11542.
In order to do the acceptance, make sure you test every corner case:

[x] Check the buttons are positioned properly when you switch between map and table view mode.
[x] Geometry buttons disappear in table view mode.
[x] Buttons are positioned properly when time series are attached.
[x] Buttons are positioned properly with other widgets attached.
[x] Try the above between breakpoints, in map view and table view.

Working like a charm! ✨
I've been messing around removing widgets, resizing the window, changing between table view and map view, and the buttons stayed in their place, so let's go to deploy!

retest this please


DEC-497: Export collection

Why: User needs a way to export a collection to a Google spreadsheet in the correct format
How: Added client side code that creates the spreadsheet then requests an auth token for access to the new sheet that the server can use to populate the data. Added routes/methods server side to export item data for a collection using the auth token and worksheet provided by the client. Once the export is complete the server will redirect the user to the new sheet.
Note: The google api does not currently allow programmatically setting a cells format. Because of this, by default, it will attempt to translate dates into a new format which will cause problems when reimporting. For the time being I'm using the old string literal trick (which google supports in its sheets) by prepending the value with a ' character. I don't really like this solution because it's known to cause problems for users who want to do additional processing with their data. In the future, we may want to just separate the date fields into separate columns, but this would be a fairly big change to both export and import so I want to try this simple method first.

:+1:

:+1:


Moodchoicejs

made changes to front and backend routes to correctly use api to retrieve emojis and store them correctly. also made changes to moodpage handlebars buttons by adding data-emoji to better access emoji to store as moo.

--outdated--


Automatically call rosdep update if needed

This calls rosdep update automatically if it hasn't been already, which is the default state after running ros2_example_bazel_installed/setup/install_prereqs.sh assuming the user has never used rosdep before.
We can't just add rosdep update to install_prereqs.sh because rosdep update must be run as the non-root user.
To test what happens if the rosdep database has been initialized but not updated, delete the rosdep cache in the home directory.
$ rm -rf ~/.ros/rosdep

To test what happens if the rosdep database has never been initialized, delete both of these folders:
$ rm -rf /etc/ros/rosdep/
$ rm -rf ~/.ros/rosdep

@IanTheEngineer & @EricCousineau-TRI  FYI

This change is

Why not just use same setup from Anzu?
as-user() {
  if [[ -n "${SUDO_USER:+D}" ]]; then
    sudo -u ${SUDO_USER} "$@"
  else
    "$@"
  fi
}

...

[[ -d /etc/ros/rosdep ]] || rosdep init
as-user rosdep update --rosdistro=rolling

I'd prefer we keep user-filesystem altering commands outside of repository commands as well - so yeah, can we just use as-user here?

Why not just use same setup from Anzu?

I didn't realize that was possible. Using as-user in e18e26b16dbad616ec5777a2895bf32200e34010


Group validation

I want to validate the widgets in group. i mean if there are two field at least one field is required. is it possible?

The rules are dynamic, so you could have the required-rule as a computed property, and set to false if any of the other fields are valid.

can you please provide me small example. i have two input field for surname and nickname. but i need at least one value either nickname or surname.

I guess it would be something in the lines of
<input v-validate="nickNameRule" id="nickName"/>
<input v-validate="surNameRule" id="surName"/>

<script>

export default {

....

  computed: {
    surNameRule() {
      return {
        required: !this.nickName
      };
    },
    nickNameRule() {
      return {
        required: !this.surName
      };
    },
  },

.....

};

</script>

@sqpdln Thanks for helping out with the issues!
here is an example: https://jsfiddle.net/logaretm/p0766ckj/1/


Disabling WebHook

It is valid to set URL to an empty string to disable a webhook.
Either not throw exception when URL is empty in setWebHook() or create a disableWebHook() method.
Thanks!!!

Thanks for reporting it will be fixed
On 24 Nov 2015 00:29, "Iván Baldo"<EMAIL_ADDRESS>wrote:

It is valid to set URL to an empty string to disable a webhook.
Either not throw exception when URL is empty in setWebHook() or create a
disableWebHook() method.
Thanks!!!
—
Reply to this email directly or view it on GitHub
https://github.com/akalongman/php-telegram-bot/issues/53.

Fixed in 0.23

if fixed why there's nothing about it on the doc? how it works?

It is in the readme, right here 👍
Check the appropriate file to see the usage.
Basically $telegram->unsetWebHook();

well i meant the telegram documents :) :+1:


Fix: Error while converting null to RootStore

Fixes the following issue:
[mobx-state-tree] Error while converting null to RootStore: value null is not assignable to type: RootStore (Value is not a plain object).
Please verify the following:

[ ] yarn test jest tests pass with new tests, if relevant
[ ] README.md has been updated with your changes, if relevant

Describe your PR

:tada: This PR is included in version 8.8.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


consistent data (automaticaly check)

Hi, we plan to use seaweedfs for large file storage. In this regard we have a problem with consistent data. How we can automaticaly check, that our cluster in consist state? Its will be good if master sometimes check volume for consist and we can periodicaly fetch this information from him. What do you think about it? Im going to implement something like this.

Do you mean to check data consistency? It i hard to do so efficiently without re-scan everything.

Well, yes it hard, but it strongly need for production. We can do periodic re-scan

Not sure what kind of check you are thinking about for one individual file.

Not individual file. I want to know all copies of the volume file (and disks) in what state. No data corruption. All disks are available. No bad sectors and etc.

Well, in total

Seaweedfs permanently collect garbage
Seaweedfs cant guarantee that data is consistent and all file copies is exist

Sounds bad(( Its a conscious assumptions?

Guarantee the file exists if the system acknowledged so.

We have large data storage. And problem with disks, files, sectors is usual. We want maximum atuomaticaly actions (check, reclaim, monitoring, recovery and etc) with our data storage and want maximum guarantee that our data will be redundant and always available for client.
The trash can become critical beacuse we cant provide consistent. Cant compare volumes on replicas.
Why its always need? Because shows our expirience that problems there is a arise during operation of a big cluster of data and all situations strange at first sight are very often demanded
We want to do system maximum safe.

@seifer
looks like you need to build some custom script that runs on the nodes periodically and executes md5deep for example. this hashes every file with md5 and you can output this to a file. compare for missing files and missmatching hashsums and redistribute them.

@libwtf Yes its. We work on the decision right now. Probably if we find simple solution than seaweedfs go to production))

@chrislusf Hi. What do you think about transaction id? With tid we can delete file in master volume and replicas if there was a failed replication

@seifer
did you ever find a solution to that issue?


dashboard: misaligned filters

str

login and go to dashboard

Closed via https://github.com/CartoDB/cartodb/pull/10353


Format generated files

#364

Is this one done?

I still need to port over terraform-clean-syntax so that we convert "${foo}" to just foo.

got it

Re-opening as we still need to clean up empty lines

@umairidris can we also clean up empty lines before 0.2.0 release?

Sure I'll spend some time today looking into this.


Alignments for radiocontrols and checkboxes on NavigationViewPage

Added alignments for all the Radiocontrols and checkboxes on each page in case they don't align when scaling fails
Description
Just set the VerticalAlignment property for each to center
Motivation and Context
To have consistent scaling.
https://github.com/microsoft/microsoft-ui-xaml/issues/1520
How Has This Been Tested?
Building
Screenshots (if appropriate):
Types of changes

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

Same comment as for #243. This change won't fix the problem introduced by scaling.


zabbix version

zabbix 3.0 import err

modify line 196 to whatever version you want
https://github.com/Sean-Bradley/SNMP2ZABBIX/blob/master/SNMP2ZABBIX.py#L196
good luck,
no guarantees


Clear temp file if S3 upload failed

This aims to fix https://github.com/Alluxio/alluxio/issues/11492
The temp files should be removed if the upload failed.

Merged build finished. Test FAILed.

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

Merged build finished. Test FAILed.

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

jenkins, test this please

Merged build finished. Test PASSed.

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

@ns1123 I assume this should cherry-pick to 2.2 as well?

Merged build finished. Test FAILed.

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

alluxio-bot, test this please

Merged build finished. Test PASSed.

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

alluxio-bot, cherry-pick this to branch-2.2 please.


Repeat sound

Hi All,
Love the script and how far developers are with implementation of Alexa into HA!!!
Is there a way to repeat a sound until there will be send a stop signal?
I want use Alexa to repeat a alarm sound... and when I hit a button (in ha) it will send a stop signal.
cheers

Probably not as I don't think the app allows it. Questions like this are probably best asked on the forum since that has higher traffic; GitHub is best for technical issues.  Perhaps someone has an automation that does what you want. I'll leave this open for a week to see if anyone else chimes in, but will close it after that point.

THank you for the answer and true maybe on forum someone has build a solution.


Why I can't vote?

Discussed in https://github.com/snapshot-labs/snapshot/discussions/767

Originally posted by metrox-eth September 29, 2021
Suggest answers below or vote for an answer.

For

في ثلاثاء، ٢٠ يونيو، ٢٠٢٣ في ٧:٥٧ ص، كتب caubetaitu <
@.***>:

Discussed in #767
https://github.com/snapshot-labs/snapshot/discussions/767
Originally posted by metrox-eth September 29, 2021
Suggest answers below or vote for an answer.
—
Reply to this email directly, view it on GitHub
https://github.com/snapshot-labs/snapshot/issues/4007, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4VJCR27VTHMPOIHKXHWRMDXMEUTBANCNFSM6AAAAAAZMW2CHY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

في ثلاثاء، ٢٠ يونيو، ٢٠٢٣ في ٧:٥٧ ص، كتب caubetaitu <
@.***>:

For
—
Reply to this email directly, view it on GitHub
https://github.com/snapshot-labs/snapshot/issues/4007#issuecomment-1598116448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4VJCR7JMZH7DQ2HUZYOWPDXMEUU3ANCNFSM6AAAAAAZMW2CHY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Updates to egui 0.24

@mvlabat ?

@naomijub Why did you close this?

stale for a week

I reopened this in #234 since this didn't need to be closed


Fix import syntax

Fixes #41

@guilhermedecampo Hi, I saw your comment on #41 and since I ran into it too here's a PR :)


[Release-1.21] - Unable to use secrets-encrypt subcommand with CP/Etcd-Only configuartion.

Backport fix for Unable to use secrets-encrypt subcommand with CP/Etcd-Only configuartion.

#5225

Encounter the same issue noted in https://github.com/k3s-io/k3s/issues/5225#issuecomment-1077951857 on v1.21.11-rc2+k3s1

Validated using v1.21.11-rc3+k3s1 that the error seen previously is resolved and running all of the secrets-encrypt subcommands are successful


Creating batch insert with associations which've large data is causing 'too many placeholders' error

type Users struct {
	Id             int
	Email          *string
	...
	Settings       *Settings    `gorm:"foreignkey:user_id"`
	BlackList      []*BlackList `gorm:"foreignkey:user_id"` // almost 5k records
	Groups         []*Groups    `gorm:"foreignkey:user_id"` // almost 20k records
	Contacts       []*Contacts  `gorm:"foreignkey:user_id"` // almost 1b records
	Reports        []*Reports   `gorm:"foreignkey:user_id"` // almost 700k records
	// also Reports struct contains another stuct which called ReportDetails is contains
	// almost 15b records.
	SubUsers       []*Users     `gorm:"foreignkey:parent_user_id;association_foreignkey:id"` // not such a large data
}

If i want to add them seperately with chunk of data on large data, there's no problem. It's adding them clearly but i've bunch of associative data and they must be added properly.
So, in this case I can use another way to add like;
// reports have 20k records.
db.Model(&models.Reports{}).CreateInBatches(reports, 2000)

// or another way is chunk the data by 2000 and loop through them
for _, reports:= range chunk {
	db.Model(&models.Reports{}).Omit(clause.Associations).Create(reports)
}

But with gorm way, I'm getting mysql error Error 1390: Prepared statement contains too many placeholders.
##Update:
I tried it with setting up gorm config for CreateBatchSize but it's not working too.
gorm.Config{
	CreateBatchSize: 2000,
}

decrease 2000 to a smaller number

decrease 2000 to a smaller number

already tried with smaller numbers even i used 10 as batch size but it`s not working

already tried with smaller numbers even i used 10 as batch size but it`s not working

if you think there is a bug, create a reproduable playground pull request.

if you think there is a bug, create a reproduable playground pull request.


add text next to a token without needing a space

It would be cool if there was a way to add text next to a token without needing a space or needing to figure out how to rewrite the token so that it includes the text.
For ex:
app.use(logger(':method :status :url :response-time ms :res[content-length]'));

What if I want to remove the space between the ms and the :repsonse-time without rewritting the token? Is there a way to do this? Thanks.

Not with the string syntax, but you can do this if you use a custom function for the formatting:
var morgan = require('morgan')

app.use(morgan(function (tokens, req, res) {
  return tokens.method(req, res)
    + ' ' + tokens.status(req, res)
    + ' ' + tokens.url(req, res)
    + ' ' + tokens['response-time'](req, res) + 'ms'
    + ' ' + tokens['content-length'](req, res)
}))

That works! Thank you.

app.use(logger(':method :status :url :response-time\\ms :res[content-length]'));

works too

@denisu that only works because '\m' is not an escape in JavaScript. If, perhaps, he wanted the end to me "ns" (with an n instead of m), then your solution wouldn't work, since '\n' would translate to a newline character.

You are right, its a little hacky, you could also squeeze a valid escape character in there, but it might produce dirty logfiles.
app.use(logger(':method :status :url :response-time\0ms :res[content-length]'));
app.use(logger(':method :status :url :response-time\bms :res[content-length]'));


How to authenticate endpoints with a path?

Take the simple-separate-pod example and modify it to have a path:
---
# Ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: whoami
  labels:
    app: whoami
  annotations:
    kubernetes.io/ingress.class: traefik
    traefik.ingress.kubernetes.io/rule-type: PathPrefixStrip # <--- see explanation below
    ingress.kubernetes.io/auth-type: forward
    ingress.kubernetes.io/auth-url: http://traefik-forward-auth:4181
    ingress.kubernetes.io/auth-response-headers: X-Forwarded-User
spec:
  rules:
  - host: whoami.example.com
    http:
      paths:
      - path: /foo/ # <-------------------------------------------- add this
        backend:
          serviceName: whoami
          servicePort: http

Then navigate to https://whoami.example.com/foo/ (replace the host with your actual host). The authentication flow is started and then the user is redirected back to https://whoami.example.com/_oauth.
That page then shows

404 page not found

which makes sense because on https://whoami.example.com/ there is no forward auth configured, only on https://whoami.example.com/foo/.
I couldn't find any configuration to make this work. I believe there are two ways to solve it, but both require changes in Traefik Forward Auth.
Possibility 1: Use X-Forwarded-Prefix
If you add the annotation traefik.ingress.kubernetes.io/rule-type: PathPrefixStrip (see above) to the Ingress, Traefik will strip the /foo/ from the path before forwarding the request to Traefik Forward Auth. It will however add a header X-Forwarded-Prefix containing the /foo/ part. Traefik Forward Auth could simply add this to the redirect URL, so that it becomes https://whoami.example.com/foo/_oauth.
This is actually #49.
Possibility 2: Use Auth-Host mode
I tried switching to the Auth-Host mode. This solution is slightly inferior because it requires all authenticated hosts to run under one common cookie domain. (By the way, there is no error when AuthHost is set but CookieDomain isn't, the AuthHost will simply be ignored, making debugging difficult.)
When AuthHost is set, the authentication itself seems to work, but the following redirect back to the application is missing its path. The solution is simple: Don't discard the path when redirecting to the application.

Hi - thanks for the detailed and well written question :)
You're right - they're two good ways to solve the issue, I'm keen to get #49 merged which would offer quite a nice solution to this.
Another option would be to manually add the path, using the traefik 1.7 as per your example:
---
# Ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: whoami
  labels:
    app: whoami
  annotations:
    kubernetes.io/ingress.class: traefik
    ingress.kubernetes.io/auth-type: forward
    ingress.kubernetes.io/auth-url: http://traefik-forward-auth:4181
    ingress.kubernetes.io/auth-response-headers: X-Forwarded-User
spec:
  rules:
  - host: whoami.example.com
    http:
      paths:
      - path: /foo/
        backend:
          serviceName: whoami
          servicePort: http
      - path: /_oauth
        backend:
          serviceName: whoami
          servicePort: http

?

Interesting idea. I actually have no idea what would happen, but I guess Traefik would just send the request to any of the Ingresses that have this path set? And it doesn't matter which one, because they all end up at the same service? I'll try that out right away.

I'll have a test with this to see if it's possible

Also, notice that enabling traefik-forward-auth globally (in Kubernetes and traefik2 this is done with the argument "--entrypoints.web.http.middlewares=default-traefik-forward-auth@kubernetescrd"), make the last redirect works. Still don't know why, but experimentally, at least for me, it is like that.


Cpp check - use cmake's built in cpp check property

Description
As per morrisonlevi's proposal, avoid using manual lookup of files in favour of the cmake cpp check support.
Motivation
A more generic usage of cpp check.
Additional notes
This makes it slightly slower to execute cpp check as it considers all Zend files.

Looks good to me! I'm a bit suspicious though: are there really no warnings outside of PHP? I would have expected to have to fix at least something, you know?

The only warning I ran into was fixed in an earlier PR and related to scope of a variable.


cordova app - unable to select  / click in the suggestion list

Hi, I'm testing my app on iOS (meteor run ios-device), the map displays correctly but when typing a location, the autosuggestion list appears but when I click on one of the suggestion it closes the list without selecting my choice.
When typing something and hitting enter, the location is correctly selected though.
Just the problem with auto-suggested list click/selection.
same behavior in the iOS simulator from xcode.
It doesn't happen when using chrome dev-tool to simulate mobile view in browser.
Any clue? Is someone experiencing the same behavior?

@dburles any clue on this issue? if you need more details please let me know, thanks for your help

Not sure on that one @steven-tib sorry. You might have more luck asking here https://gitter.im/dburles/meteor-google-maps or perhaps on stackoverflow.


Add correct docker image fetch in beta CI

Missed the correct docker fetch in the second part of the beta tests

bors merge


Mitigate memory leak

What does this PR do?
This PR bumps the mux dependency version, because it contains a work-around to mitigate a memory leak.

Motivation
To fix a memory leak, which might be the one observed at #7964 for example.

More
~- [ ] Added/updated tests~
~- [ ] Added/updated documentation~
Additional Notes
#8044, #7533

Is this also affecting Traefik 1.7? And if so, will this be backported? (#7191)

Hi, is there a fix for version 1.7? I didn't find a newer version.

We are looking into it, we will get back to you soon. :)

@darkl0rd @llussy Just to clarify version 1.7 is not supported anymore and we are preparing a new doc section that would make it easy to find what versions we are actively maintaining and what are the rules for that, including exceptions if any.
The PR is still under review, and feedback is welcomed as always.
Having said that, yes this problem affects 1.7 and we might look at backporting it at some point if really needed. Really needed in this context means a customer is affected and couldn't finish the migration to 2.x in time or hit some blocker in doing so, then we might consider a priority to avoid production issues until the migration is finished.
Of course if someone in the community is willing to work on it and backport the fix into 1.7 I see no reason why we would not review and merge it as soon as possible.