Custom markers flickering due to new Google renderer

Summary
Hi, I just came across this issue while working on my mobile app running on Expo SDK49. While I was able to mitigate the problem following one of the suggestions found in another bug report, I'm wondering, what's the real solution for this?
My journey so far:

some people suggested to set tracksViewChanges={false} but that's not feasible in some scenarios (like mine)
some people suggested to set googleRenderer="LEGACY" which requires upgrading to at least v1.13.2 (like I did)

While the first solution is a non-solution for many cases, the second feels like a workaround while waiting for the inevitable.
I couldn't find anything specific in the changelog so I was hoping the maintainers could shed some light on this.
Reproducible sample code
N/A

Steps to reproduce
Use SVG as custom markers:
<Marker coordinate={{...}} identifier={...} onPress={...}>
  <MySvg />
</Marker>

Expected result
Custom marker should not flicker.
Actual result
https://github.com/react-native-maps/react-native-maps/assets/8156463/cbe31aa3-0478-4d43-8131-90b743063733
React Native Maps Version
1.14.0
What platforms are you seeing the problem on?
Android
React Native Version
0.74.3
What version of Expo are you using?
SDK 51
Device(s)
Google Pixel 5
Additional information
The current Expo version is 51 but the problem started appearing already from version 49.

I have the same problem.
It happen after the June 25, 2024 with the Release 19.0.0. More information here :
https://developers.google.com/maps/documentation/android-sdk/release-notes
Because of Google Play updates (Google Maps) we need to find a solution now with the Release 19.0.0.
I think It would be necessary to investigate by creating an example not in React Native, but in pure Android Studio. And send the problem to Google if flickering. I am not sure it is a react-native-maps issues.
What do you guys think?

With my SM_T580 (Galaxy Tab A (2016, 10.1)), more the device is slow, more this makers are flicking (wasn't the case before the new Google renderer) :
https://github.com/user-attachments/assets/b431a7bf-d90d-4fdb-ae85-662c2a0809f4
Expo : 51
react-native-maps : 1.15.6

AnimatedMarker.js :
import React from "react";
import { Image } from "react-native";
import * as Animatable from "react-native-animatable";
const MarkerContent = () => {
return (
<Animatable.View
animation="tada"
easing="ease-out"
duration={400}
delay={0}
iterationCount="infinite"
>
<Image
source={require("./assets/ANIMALS/cat.png")}
style={{ width: 40, height: 40 }}
/>
</Animatable.View>
);
};
export default MarkerContent;
App.js :
import React from "react";
import { StyleSheet, View } from "react-native";
import MapView, { Marker } from "react-native-maps";
import AnimatedMarker from "./AnimatedMarker";
export default function App() {
return (

<MapView
googleRenderer="LEGACY"
style={styles.map}
mapType={"hybrid"}
initialRegion={{
latitude: 37.78825,
longitude: -122.4324,
latitudeDelta: 0.0922,
longitudeDelta: 0.0421,
}}
>
<Marker coordinate={{ latitude: 37.783333, longitude: -122.416667 }}>

);
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: "#fff",
alignItems: "center",
justifyContent: "center",
},
map: {
width: "100%",
height: "100%",
},
});

sources.zip
Source

did anyone find any solutions yet ?

also have this issue

This issue seems to be a result of marker.setIcon() being repeatedly called in MapMarker.updateMarkerIcon https://github.com/react-native-maps/react-native-maps/blob/d73052b608101e0eb8f09762a33ad65007c022cf/android/src/main/java/com/rnmaps/maps/MapMarker.java#L292
If I do something like this instead and set the flag to false with the debugger once things have rendered, the flickering stops.
  private static boolean doUpdateIcon = true;
  public void updateMarkerIcon() {
    if (marker == null) return;
    var icon = getIcon();
    if (this.doUpdateIcon) {
      marker.setIcon(icon);
    }
  }

This issue seems to be a result of marker.setIcon() being repeatedly called in MapMarker.updateMarkerIcon
https://github.com/react-native-maps/react-native-maps/blob/d73052b608101e0eb8f09762a33ad65007c022cf/android/src/main/java/com/rnmaps/maps/MapMarker.java#L292
If I do something like this instead and set the flag to false with the debugger once things have rendered, the flickering stops.
  private static boolean doUpdateIcon = true;
  public void updateMarkerIcon() {
    if (marker == null) return;
    var icon = getIcon();
    if (this.doUpdateIcon) {
      marker.setIcon(icon);
    }
  }

Why doing this ? this is a Props for <Marker :
https://github.com/react-native-maps/react-native-maps/blob/master/docs/marker.md
tracksViewChanges
No need boolean doUpdateIcon

This issue seems to be a result of marker.setIcon() being repeatedly called in MapMarker.updateMarkerIcon
https://github.com/react-native-maps/react-native-maps/blob/d73052b608101e0eb8f09762a33ad65007c022cf/android/src/main/java/com/rnmaps/maps/MapMarker.java#L292
If I do something like this instead and set the flag to false with the debugger once things have rendered, the flickering stops.
  private static boolean doUpdateIcon = true;
  public void updateMarkerIcon() {
    if (marker == null) return;
    var icon = getIcon();
    if (this.doUpdateIcon) {
      marker.setIcon(icon);
    }
  }

Why doing this ? this is a Props for <Marker :
https://github.com/react-native-maps/react-native-maps/blob/master/docs/marker.md
tracksViewChanges
No need boolean doUpdateIcon

The bug is with tracksViewChanges, it causes flickering with a custom View. This seems to be the cause.

I think Google’s AdvancedMarker could resolve this most easily, as it lets you attach a view to the marker. https://developers.google.com/maps/documentation/android-sdk/advanced-markers/add-marker#use_iconview
But it has a number of limitations which probably make it unsuitable for a library at the moment. You need to use a map id (not the free map) and the new renderer: https://developers.google.com/maps/documentation/android-sdk/advanced-markers/start#check_map_capabilities_required

Google maps issue: https://issuetracker.google.com/issues/369213504


[Suggestion][PRWIP] Move CodeSandbox examples to GitHub and use auto-import

To maintain the codesandbox samples automatically from within this repo, I've tested a POC of using the auto import functionality described in the codesandbox API docs. I'd happily complete a full a PR if this seems useful.
https://github.com/JasonRitchie/react-table/compare/master...JasonRitchie:codesandbox

There have been challenges with the codesandbox "individuality" (the owner).  If we combine this with the ability to now actually share codesandbox repos (it's a new feature - I have not tried it yet) - we might get a more maintainable outcome (rather than people just creating them all over the place and submitting PRs to fix things).

Should I go ahead with a full PR covering all the codesandbox samples or should I hold off for now?

What kind of changes will that entail?
On Tue, Mar 27, 2018 at 6:17 PM Jason Ritchie<EMAIL_ADDRESS>wrote:

Should I go ahead with a full PR covering all the codesandbox samples or
should I hold off for now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/react-tools/react-table/issues/878#issuecomment-376717292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCZKePapvSUPENp0QIZ84_nejCUppks5titasgaJpZM4S9J0c
.

It should be a seamless transition with no change to the user experience, if my proof of concept works correctly for all the examples. I linked my own Fork where I tested this and I was able to use yarn run docs and see this in action.
I might suggest that I go ahead and put together a small PR as a work-in-progress perhaps to be merged into a branch to see how this would look, if you like.

I'd probably like @tannerlinsley to be across this before going too far - but it is probably definitely worth doing.

Yep. Throw together a proof of concept and let's see where it leads us
On Tue, Mar 27, 2018 at 6:48 PM Gary Menzel<EMAIL_ADDRESS>wrote:

I'd probably like @tannerlinsley https://github.com/tannerlinsley to be
across this before going too far - but it is probably definitely worth
doing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-tools/react-table/issues/878#issuecomment-376722513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCccy-EqYj50ei6PJzuDed6EnyUReks5tit3ZgaJpZM4S9J0c
.

created https://github.com/react-tools/react-table/pull/880

Closing due to issue age. If you think this issue needs to be reopened or if it should be turned into a pull-request, please check the latest version of React-Table for the issue or feature once more and reopen or create a PR if appropriate. Thanks!


page.render('/dev/stdout', { format: 'pdf' });

Hi,
I'm trying to use page.render('/dev/stdout', { format: 'pdf' }); command in resterize.js file in Windows and I have a problem with the data output coming back with encoding errors.
My original goal was to get the file generated on the fly instead of saving to disk on my server. After reading the git hub source, I found that the file is still being saved to disk temporarily anyway. That's ok. The main issue is the encoding errors in my result from stdout. After searching the github code, I think maybe I may have found the point where the encoding problem is introduced?
https://github.com/ariya/phantomjs/blob/4989445e714bb97fe49ef8c00ccbce8b6cfbfbb0/src/webpage.cpp
Line 926: ((File *)system->_stdout())->write(QString::fromAscii(ba.constData(), ba.size()));
Do you think if you change fromAscii to fromUtf8, my encoding issues will be resolved?
I wish I could do the change myself and test but I can't build the source because I don't have all the required tools installed on my PC.
Could you test this for me please?

Hello, Sorry to pick up this thread so late, I thought it'd be better to take it from here instead of creating a new one. I have the same issue as @zatlite but what I do is run the PhantomJs command from PHP with exec. Then I get the output via the $out second parameter of exec() like this:
$response = exec($cmd, $out)
My problem is that, the data is returned as an array built from the PDF raw string. I tried using
implode(PHP_EOL, $out)
to rebuild the raw file and serve it as PDF but then, I get an empty PDF file. The file has the same number of pages as it should but comes blank with some weird characters as title.
I suspect the charset to be th reason behind this behavior but don't know how to go around this limitation.
Any help will be greatly appreciated.
PS: The script is running on Linux CentOS.


Update shift-drawer-management.md

Add additional information about the "Require starting amounts and tender declaration" behavior as we have received two incidents related to changes introduced in Commerce version 10.0.40.

Bug 958852: Create documentation to explain if drawers are not associated with hardware profile, then no validation will be executed and the shift will be closed
Content Deliverable 962352: Shift and cash drawer management public documentation update


service(darwin): fix status regression

In https://github.com/kardianos/service/pull/196/files#diff-5f554888209e6e12e2ac42ca24862cf09e282924e4c31b7e15c67320ac300d7eR190
"failed with stderr" was replaced with "failed with StandardError". However, the message received is still failed with stderr: https://github.com/kardianos/service/blob/master/service_unix.go#L104
On macOS, this means the status command fails when uninstalled, installed or stopped. The only valid state is when the service is actively running.

Coverage remained the same at 12.799% when pulling 682e80c0bb0d80f7b7799ebc31da240b76e65df5 on saracen:fix-darwin-status into ef35c563203c809a5c48a2310ca90430c064e7c3 on kardianos:master.


Upgrade package version

Purpose
$Subject
Fixes: https://github.com/ballerina-platform/ballerina-standard-library/issues/1334
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the changelog
[ ] Added tests

@kalaiyarasiganeshalingam This will close the original issue if merged, lets update the description to not do so


Factor out polling goroutines from pipeline binary

Right now there are several background goroutines in the main Pipeline binary doing scraping and syncing in a polling manner.
We should factor out these goroutines into separate go binaries within the Pipeline project.

See #2158 and #2167


Implement and test the stack manipulation instructions

See https://github.com/dwayne/whitespace-ruby/commit/f15430e5f6d9b196ac327913398ffa7ca83b466c.


[Go][Parquet] BufferedPageWriter reallocates memory during cleanup, causing a leak

Describe the bug, including details regarding any error messages, version, and platform.
On bufferedPageWriter.Close() the BufferWriter.Finish() method is called but not BufferWriter.Release(). The doc for Finish states that the caller must still release the buffer.
Blocking: https://github.com/apache/arrow-adbc/pull/1866
Component(s)
Go, Parquet

@joellubi, @zeroshade, this appears to have been fixed in #41698, right? Is this issue still open because the fix isn't yet released? I see that PR was merged after the last release (v16.1.0). Any chance of a v16.1.1 soon that would contain this fix?

Hi @jhump. You should be able to update your Go dependency to the latest commit of v17 to get a "preview" of all the latest changes, including this one (example). This may work for your needs.
Otherwise v17 should officially release relatively soon, likely sometime in July (ref).
I would consider this issue closed now. I've added it to the 17.0.0 milestone and closed it to reflect its current state.

Thanks, @joellubi!


override device_map if the model is gptq-based

Override device_map in config if the model is GPTQ-based.
This solves #599, which wasn't entirely addressed by #609.
After this PR, example gptq-lora.yml trains correctly.
Finetuning with 2xRTX3090 works too, but I'm not really sure on how it will perform on custom accelerate configs.

@Napuh This should be fixed with #621 now


Add Unovis

https://github.com/f5/unovis looks really interesting.
Maybe @rokotyan would be open to take a look at https://github.com/cube-js/awesome-tools/tree/master/copy/tools and submit a PR adding Unovis to https://awesome.cube.dev.

@igorlukanin Thanks for the mention, on it!


WA-232 - Feature display token funds

Description
In this PR the logic for displaying balances of different safe's tokens. As a technical aspect it includes:

Tests for simulating transaction of ERC20 Tokens
New way of deploying safes faster in tests
Refactor redux store's balance property  to Map<symbol:string, Balance>
Bunch of flow error fixes

SEE:

Travis automatic deployment:
https://release-48-pr-363-safe-react-gnosis.surge.sh
Storybook book automatic deployment:
https://storybook-release-48-pr-363-safe-react-gnosis.surge.sh


.blockquote-center

responding to a request for .blockquote-center class to mitigate the
border-left and maintain a center block appearance with center aligned
text.

Hi @jonahallibone!
Thanks for wanting to contribute to Bootstrap by sending this pull request!
Unfortunately, your pull request seems to have some problems:

The CNAME file should never be modified.
Changes must be made to the original Sass or Less source code file(s), not just the compiled CSS file(s).
Changes must be made to the original JS source code file(s), not just the generated concatenated JS file(s).

You'll need to fix these mistakes and revise your pull request before we can proceed further.
Once you've fixed these problems, you can either ask the maintainers to re-open this pull request, or you can create a new pull request.
Thanks!
(Please note that this is a fully automated comment.)


Usability: 'Drawings on map' as button

Was confusing for users to locate 'drawings on the map' as they thought it was supposed to be somewhere near the symbols with which to draw the points/polygons. Idea: Distinction between layers of map and results of analyses.

restructured the layer switcher 7f8ec94997e0a53bb9bfcd12180b967529e905a1


Error in the documentation? (section 3.3 Fonts)

Describe the problem or request
The documentation say that the package fontenc needs XeLaTeX or LuaLaTeX. This seems false (fontspec needs these engine, but here the cmbright option don't load fontspec, but fontenc).
Screenshots

Additional context
The lines 99 to 106 of edmaths.sty are:
% If with-cmbright selected, use the (sans-serif) Computer Modern Bright font.
\ifthenelse{\boolean{with-cmbright}}{
    % NOTE must be compiled with xelatex or luatex
    \RequirePackage{cmap}
    \RequirePackage{cmbright}
    \RequirePackage[T1]{fontenc}
    \RequirePackage{microtype}
} {}

The comment in line 101 seems to be wrong.
On lines 108 to 113, we read:
% :)
\ifthenelse{\boolean{with-comicsans}}{
    % NOTE must be compiled with xelatex or luatex
    \usepackage{fontspec}
    \setmainfont{Comic Sans MS}
} {}

Perhaps the line 101 is a copy and paste of line 110 (which is correct, because of the loading of fontspec at line 111).

Thanks so much for catching this!
This misunderstanding stemmed from Computer Modern Bright not actually being installed on my computer. Under those conditions, pdflatex fails to compile with an error. However with both xelatex and lualatex, they just gave a warning and finished compiling with a substitute font which happened to look like CM Bright but actually wasn't.


[RFE] oci-image-tool: produce a layer archive

Add a sub-command where two directory paths can be provided and the utility will produce a layer archive from comparing the two references.
(this exercise will help ensure the layer.md is readable)

I'd like to work on this :)

@coolljt0725 go for it.

working on that, pr is coming :)

This issue was moved to opencontainers/image-tools#20

On Tue, Sep 20, 2016 at 07:48:04PM -0700, Brandon Philips wrote:

This issue was moved to opencontainers/image-tools#20

PR is opencontainers/image-tools#8.


Discover crate type information late if necessary.

Some crates aren't found during eager crate-type searching due to being behind cfg(...) flags. We still want to be able to handle these, though, so when necessary we now call rustc again to get crate-type information for these cfg-ed crates.
This is necessary for https://github.com/rust-lang/rust/pull/41991.
r? @alexcrichton

Updated, I think this fixes the tests.

Thanks! This I think only has a downside of running rustc more times, right? No-op builds of Cargo can sometimes be dominated by this as we've gotta run rustc three times now which actually blows up to 6 processes if you're running rustup. Clocking in at a minimum of 5ms per process (ish) we're getting close to 30-50ms overhead in Cargo for "doing nothing", which can get pretty pricy.
Can you describe the original bug in some more detail? Would it be possible to not need to spawn a new rustc process? I've long intended to have a fancier caching mechanism for rustc processes where we only rarely spawn rustc to learn this sort of info, but that's still a long ways off unfortunately.

I think it's possible we can spawn less rustc processes here (in theory we'd only need to do this cfg/sysroot discovery twice, once for Kind::Target and once for Kind::Host. That might already be what we do, I'm not sure how often the relevant function is called.
Basically, the initial bug here was that we wouldn't look at dependencies which had cfg(..) in their definition in Cargo.toml when attempting to find out what crate types a user had. The problem is likely possible to notice not only with proc-macro crates (most unusual crate types will do), but it's easiest to notice with them. I'm not sure how much we can do here to mitigate or remove the problem entirely; I can't think of anything myself. Let me know if that helps clarify things for you.

Hm ok, thanks! I wonder if we could traverse the whole crate graph, regardless of cfg on the dependencies, to collect the crate types we should be learning about?

Hm, maybe. Although it would mean we'd traverse some crates that we shouldn't (i.e., doing extra work) but that does seem plausible. I'll try to make that change here as soon as I get a chance.

The "extra work" here is fine, I don't think it'll cause any problems.

Okay, pushed up a new version. Note that a few tests are changed/deleted since they either no longer make sense or need to be updated for the new state of things. I'd appreciate comments if there's some area we can do better here to decrease what we have to download.

So we can revert to the patch which runs rustc more times, or keep this and just live with having to download dependencies that we won't actually use. As noted in the commit, it's possible we can change the crates.io API to expose crate-type more directly (without download of the whole crate).
So an alternative approach here is to not query rustc for the prefix/suffix for each crate type, but instead copy that code into Cargo. I assume it's something like a table, though I don't know, in which case maintaining it should be fairly easy. Obviously, it does add some level of overhead to adding new crate types, but adding new crate types is rare enough that it may be worth it. It's not really that much information, though if it varies depending on target platform or other details that's a negative point towards duplicating the information.
Maybe we can alternatively always execute rustc with -o and output into a Cargo-specific file? For example, we'd build rlibs into rlib-cratename or cratename.rlib or something like that. I guess that'd probably confuse rustc and linkers, though.

At this point, it may be worth considering that I'm not sure that the cost of downloading windows dependencies is all that severe, though it may be higher than a slight overhead on all Cargo invocations of calling rustc more times (as the earlier version of the patch did).
I think that this is a bug that needs to be fixed, one way or another, or at least a workaround proposed. It's hitting actual users and is painful to work around. I'm not sure the overhead you noted (30-50 ms) is severe enough to justify not going with that approach because of it. Arguably, though, the current implementation has less overhead in the case of doing nothing, since we've already downloaded all dependencies.

Hm well so just to make sure I've got a handle on this, is this really that much of a widespread problem? I'm under the impression that it's basically limited to "target specific dependencies" which are actually misused for --cfg flags passed through RUSTFLAGS, basically rustc's and only rust's use case. AFAIK this has never come up in the wild in Cargo.
Despite that though I'm relatively firm on (a) not adding more process invocations and (b) not downloading extraneous dependencies. More invocations can seriously affect noop build time and more downloads skews statistics and pollutes caches. Basically budging on either of this is guaranteed to mean a future bug report that we'll need to fix.
It's a good though though to even question why Cargo is doing this! Certainly for a bunch of targets (e.g. almost all built in ones) Cargo can statically know this information without asking the compiler itself. The catch is custom targets, however, which can arbitrarily change their filenames. In that sense it's impossible I think for this logic to 100% live in Cargo without reimplementing custom target specifications from the compiler.
What we may be able to do is whitelist some targets and hardcode knowledge, but it doesn't really solve the problem. Another possible solution though is to dynamically detect this information in these pessimistic cases (which I'd hypothesize are not common). That is, if we don't have cached information for what a crate name will be we immediately run the compiler to learn such info. Most Cargo compilations won't have this extra compile, but some will.

I'm under the impression that it's basically limited to "target specific dependencies" which are actually misused for --cfg flags passed through RUSTFLAGS, basically rustc's and only rust's use case. AFAIK this has never come up in the wild in Cargo.

I believe that this hasn't yet come up in the wild yet because no one has tried to depend on a crate with a non-whitelisted crate-type behind cfg of any kind (e.g., target platform). This is likely because I'd guess most Cargo projects out there are rlibs, some are dylibs, and a few are proc-macro crates. proc-macro crates in general aren't target specific, though I could imagine something like bindgen wanting to target only a specific platform. It does seem possible to encounter though; all you'd need is a crate like winapi to depend on serde, I think.

Another possible solution though is to dynamically detect this information in these pessimistic cases (which I'd hypothesize are not common)

I think this seems like a viable solution to the problems this PR faces; I'll try to implement it soon.

@alexcrichton Updated with the late-discovery method. Generally seems to work quite well; no tests failed locally.

Thanks yeah looks good! I think right now though we need to remove the duplication because there's features like RUSTFLAGS handling which aren't shared between these two code paths. Perhaps the original function could have a structured return value and the new invocation being added would just handle a few fields coming out of that? It should be essentially "free" to call one rustc invocation to learn about extra information and then discard it.

Hm, I'm not entirely sure I follow you. You mean we'd stash the rustflags and other arguments into a struct to reuse later?

Er sorry, basically we need to share the definitions here, I'd prefer to not land two copies of the same function. However that happens I don't mind.

Alright, I think I sufficiently deduplicated the two code paths. Let me know what you think.

@bors: r+
Thanks!

:pushpin: Commit 4cfaf9a has been approved by alexcrichton

:hourglass: Testing commit 4cfaf9a591e5c055b87b8eb265c665a4cc1305d9 with merge 7847f75bb6fc4fee6f511ca740bbe6872c08502b...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 7847f75bb6fc4fee6f511ca740bbe6872c08502b to master...


how to connect harmony hub

hello
iam new to ha-bridge. I would like to connect my harmony hub to the ha-bridge to control some Homematic devices.
but my problem is that my harmony app keeps telling me that I have to press the middle button on the hue bridge. so where do I press this button? or what do I need to do.

I have the same issue. In #218 @memojo and @klein0r pointed out, that it helps to discover first the non-existent "Hunter Douglas Powerview Hub" and then trying the Philips Hue again - but this doesn't work for me either. Maybe it works for you?

This is an issue already identified in #797

Hello I'm having the same question
Problem is that don't event understand the answers (what mean those references to a "Douglas Powerview Hub" and Hue Bridge since the request is about an Harmony Hub issue)
I've correctly declared my Harmony Hub IP address in "Bridge Control" page
The "Harmony devices tab" is still empty
I guess I've to initiate a pairing process pair but I've been unable to found where it's described in the documentation


Unsupported 1-dimensional matrix types

HLSL has 1-dimensional matrix types that DXC accepts. Metal does not have them.
I think for on ramping it might be just to have them in case someone uses them.
I don't know if they have specific load/store ordering dependencies. But the DXC has SPIR-V opcodes:
https://github.com/microsoft/DirectXShaderCompiler/blob/main/tools/clang/test/CodeGenSPIRV/binary-op.arith-assign.matrix.hlsl
void main() {

    float1x1 a, b;
    b += a;

    {

        float1x2 c, d;
        d -= c;

        float1x3 e, f;
        f *= e;

        float1x4 g, h;
        h *= h;
    }

    {
        float2x1 c, d;
        d -= c;

        float3x1 e, f;
        f *= e;

        float4x1 g, h;
        h *= h;
    }
}

NOTE: This applies to other types besides float as well.

On my first attempt, HLSL seems fine but SPIR-V validation errors it out.
error: line 32: Illegal number of components (1) for TypeVector
  %v1float = OpTypeVector %float 1

I will see how to avoid it.

I like to leave a quick update.
HLSL seems fine with 1-dimensional matrix types.
But GLSL and SPIR-V don't support natively.
Slang will be able to handle them as a vector type; not matrix type.


Backup failed?

A player reported backup failing due to space in the backups path?

https://paste.ubuntu.com/p/M3SmDth4wm/

I think the file that stores a reference to the last backup is somehow corrupted so that it contains only spaces. Tell the person that opened the issue to try deleting the file backups\REDRED\Last.

That fixed it.
Do you know why it happened?

No, I have no idea why that happened. In the next update I'll try to make it so the backup doesn't fail if the last backup file is corrupted, so that'll help.


[Environments reliability] Empty properties shouldn't be shown

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Have a virtual machine/Dev Box with not all the information available from APIs.
The empty property is still shown.
Expected result
Probably skip the unavailable info.
Actual result

Included System Information
No response
Included Extensions Information
No response

@shakersMSFT could you opine on this?


Car under the floor partially

Play the Omi Gohan map
In the curve after the broken bridge pass next to the wall
The car crosses some terrain and goes under it
Video here:
https://drive.google.com/open?id=0B_f_RtJ2CmCuLTR4ZVZqdThIaVU

Partially solved. Need testing but terrain has been changed.


Executing custom tasks

Hello!
Thanks for this fantastic repo! The paper is also very amazing and insightful.
I was wondering whether it's possible to define custom HTML pages and tasks to be executed.
I was thinking of adding the custom HTML file in computergym/miniwob/miniwob_interface/html/miniwob directory and also including it in available_tasks.txt
Would this approach work? Please, let me know your thoughts about this.
Regards

Hello, thank you for your interest in this repo, and sorry for the delay.
Currently, the RCI agent is using the MiniWoB++ benchmark, which is wrapped by the OpenAI Gym interface. Therefore, it will not be easy to add a custom HTML environment to the MiniWoB++ benchmark. Instead, I recommend running the agent directly on your custom website using Selenium. I have already implemented this code for the facebook.com webpage in the main.py. You can play around with the code and let me know if you have more questions.
You can lunch the code with the below argument.
--env facebook


Sync eng/common directory with azure-sdk-tools repository

Sync eng/common directory with azure-sdk-tools repository

We need to merge this PR to allow further work on eng/common directory. Should the changes be made to the tools repo instead so it syncs to all the repos?
@ahsonkhan @weshaggard

Yes, I plan to port the changes over from https://github.com/Azure/azure-sdk-for-c/pull/1012#discussion_r466740175 today.


How do repeated info tags in variants fit with GAKeyValue?

There are some variants and call info fields which are repeated in VCF. (e.g. any tag that is repeated per-allele - AC, AF, HQ, EC etc)
How should these fields be represented as GAKeyValue - which has a single string value for each key?
Should we:
a) smash values together in some well known way :(
b) make GAKeyValue::value an array :(
c) some better idea I'm missing?

The last comment on this was Oct 2014 I'm closing this in 2 days.

Closing due to inactivity. This can be reopened if necessary.


Remix Denoiser is unstable in BeamNG.drive

Describe the bug

When the denoiser is enabled in BeamNG.drive, it introduces major visual artifacts and performance issues
dxvk-remix-717c1d2-278-debugoptimized
bridge-remix-0903dd0-33-debugoptimized
RTX 3090
537.42
BeamNG.drive (Steam) Beta build <IP_ADDRESS>-dx9
Note: Remix is installed straight to the 64 bit build, no bridge

Attach files!
BeamNG.drive.x64_d3d9.log
rtx.conf.txt
To Reproduce
Steps to reproduce the behavior:

Download BeamNG.drive beta build <IP_ADDRESS> through Steam
Load the game
Select Cliffs or Gridmap
Toggle denoiser on/off to observe issue

Expected behavior

The denoiser should be stable and clean up the image, not introduce further artifacts

API Trace

I have included an API Trace at the request of Mark: https://drive.google.com/file/d/1W_CuYxUAThc6gBOSJJoXLa0wqlN0y2BN/view?usp=drive_link

Screenshots
Video Denoiser Example
Screen Space Motion Vectors

Figured I'd follow up with a small discovery. Switching to ReLAX with the default settings yields an improvement in visuals, however it still has major artifacts and looks worse than when the denoiser is disabled entirely.
Video

REMIX-2332 for tracking.

https://github.com/NVIDIAGameWorks/rtx-remix/assets/62084776/9c8d4372-bf7b-4605-b4e3-6ca9832cd873
Here's a new sample showcasing it more in-depth

I'm getting the same issue in GTA SA,
https://youtu.be/HQvANTLVtZY Here the grass is weirdly reacting to motion
https://youtu.be/iZYo1aDg9_A   Here the DLSS is just making the rays freak out, the less DLSS i apply the less deconstructed it looks

@KCDQYaniss is your problem in GTA SA resolved?

Ray Reconstruction has helped BeamNG.drive immensely. This game still has major lighting issues however (it's almost as if there aren't enough samples per pixel). In motion this is more apparent.


pdf2djvu: unbreak

ZHF: #122042
Motivation for this change
The released version requires "poppler-splash", but as of 20.12, that package is not part of poppler, it seems. The included patch is already merged to jwilk/pdf2jdvu:master, and simply changes the requirement to "poppler" only.

Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

I also ran make test after hacking up the build env to be able to run it. I can add the relevant checkInputs to the build if you like; I'm not sure what the convention is there for smaller packages like this one.

I also ran make test after hacking up the build env to be able to run it. I can add the relevant checkInputs to the build if you like

That would be nice.

@dotlambda same commit, or new commit, or does it not matter?

Result of nixpkgs-review pr 122377 at a747ac9a run on x86_64-linux 1

1 package built successfully:

pdf2djvu

1 suggestion:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/typesetting/pdf2djvu/default.nix:68:5:
   |
68 |     license = licenses.gpl2;
   |     ^

Shall we merge this and let you make any more improvements at your own pace? A fixed package is better than nothing :)


Fix the auto assign GitHub action

now updated code help to do : assign to multiple issues as long as each issue has a pull request

Awesome thank you!

Awesome thank you!

My pleasure, and thank you for the information, sir. 😊


Debashish_CTC_Prediction

CTC Prediction of newly hired students based on the data of college , city etc.
Different Regression Models are used and the accuracy is compared and scrutinized .

Revert for any concern


Missing sample for new feature in ASP.NET Core 8

Description
Would be great to have this added, it is very useful: https://github.com/dotnet/aspnetcore/pull/42646
Page URL
https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/health-checks?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/host-and-deploy/health-checks.md
Document ID
52d8efc9-a336-71d9-6d90-98173cbf6bf4
Article author
Rick-Anderson

Associated WorkItem - 186859

Thanks, @Rick-Anderson


Firebase plugins have flaky iOS compile failures

See https://cirrus-ci.com/task/5391245930135552 for an example.
    === BUILD TARGET firebase_ml_vision OF PROJECT Pods WITH CONFIGURATION Release ===
    In file included from /Users/anka/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.3.0+1/ios/Classes/FirebaseCorePlugin.m:7:
    In file included from /var/folders/sy/2x5qvs0n4lg18fry9jz4y21m0000gn/T/cirrus-ci-build/packages/firebase_ml_vision/example/ios/Pods/Headers/Private/Firebase/Firebase.h:8:
    In file included from /var/folders/sy/2x5qvs0n4lg18fry9jz4y21m0000gn/T/cirrus-ci-build/packages/firebase_ml_vision/example/ios/Pods/Headers/Public/FirebaseAnalytics/FirebaseAnalytics/FirebaseAnalytics.h:1:
    In file included from /var/folders/sy/2x5qvs0n4lg18fry9jz4y21m0000gn/T/cirrus-ci-build/packages/firebase_ml_vision/example/ios/Pods/Headers/Public/FirebaseAnalytics/FirebaseAnalytics/FIRAnalytics+AppDelegate.h:3:
    /var/folders/sy/2x5qvs0n4lg18fry9jz4y21m0000gn/T/cirrus-ci-build/packages/firebase_ml_vision/example/ios/Pods/Headers/Public/FirebaseAnalytics/FirebaseAnalytics/FIRAnalytics.h:4:9: fatal error: 'FIRParameterNames.h' file not found
    #import "FIRParameterNames.h"
            ^~~~~~~~~~~~~~~~~~~~~
    1 error generated.

I've occasionally seen these errors locally, but never figured out how to consistently reproduce them.  They generally "fix themselves" in CI after running the check a second time.
/cc @bparrishMines

There are several that have similar error messages.
#27281, #26159, #25676, #24875, #23277, #22071, #18673, #18342, #18143, #16246, #16049, #15409, #9817

@mklim
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/451. Any further collaboration will be done there.


Registry UI Exception

When using the UI the following error is thrown causing the UI to stop functioning:
vendor.bundle.js:5 Uncaught (in promise) RangeError: Maximum call stack size exceeded
at p._renderValidatedComponentWithoutOwnerOrContext (vendor.bundle.js:5)
at p._renderValidatedComponent (vendor.bundle.js:5)
at p._updateRenderedComponent (vendor.bundle.js:5)
at p._performComponentUpdate (vendor.bundle.js:5)
at p.updateComponent (vendor.bundle.js:5)
at p.receiveComponent (vendor.bundle.js:5)
at Object.receiveComponent (vendor.bundle.js:1)
at Object.updateChildren (vendor.bundle.js:4)
at v._reconcilerUpdateChildren (vendor.bundle.js:5)
at v._updateChildren (vendor.bundle.js:5)
Promise rejected (async)
e @ application.js:23
e.notifyAll @ vendor.bundle.js:3
close @ vendor.bundle.js:6
closeAll @ vendor.bundle.js:2
perform @ vendor.bundle.js:2
u @ vendor.bundle.js:3
perform @ vendor.bundle.js:2
batchedUpdates @ vendor.bundle.js:5
a @ vendor.bundle.js:1
_renderNewRootComponent @ vendor.bundle.js:3
_renderSubtreeIntoContainer @ vendor.bundle.js:3
render @ vendor.bundle.js:3
(anonymous) @ application.js:32
t @ vendor.bundle.js:1
window.webpackJsonp @ vendor.bundle.js:1
(anonymous) @ application.js:1

@gss2002 Have you built registry from the source or downloaded any particular version?

@shahsank3t I tried to build from source using maven on RHEL/Centos7. This happens with both 0.3.0 build and 0.4.0 build.
mvn package -DskipTests
When enabling webpack development I see the following:
| printWarning | @ | warning.js:33
-- | -- | -- | --
  | warning | @ | warning.js:57
  | createElement | @ | ReactElementValidator.js:190
  | patchedCreateElement | @ | patch.dev.js:188
  | render | @ | SchemaInfoForm.jsx:236
  | render | @ | createPrototypeProxy.js:44
  | (anonymous) | @ | ReactCompositeComponent.js:793
  | measureLifeCyclePerf | @ | ReactCompositeComponent.js:73
  | _renderValidatedComponentWithoutOwnerOrContext | @ | ReactCompositeComponent.js:792
  | _renderValidatedComponent | @ | ReactCompositeComponent.js:819
  | performInitialMount | @ | ReactCompositeComponent.js:359
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | mountChildren | @ | ReactMultiChild.js:234
  | _createInitialChildren | @ | ReactDOMComponent.js:701
  | mountComponent | @ | ReactDOMComponent.js:520
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | mountChildren | @ | ReactMultiChild.js:234
  | _createInitialChildren | @ | ReactDOMComponent.js:701
  | mountComponent | @ | ReactDOMComponent.js:520
  | mountComponent | @ | ReactReconciler.js:43
  | mountChildren | @ | ReactMultiChild.js:234
  | _createInitialChildren | @ | ReactDOMComponent.js:701
  | mountComponent | @ | ReactDOMComponent.js:520
  | mountComponent | @ | ReactReconciler.js:43
  | mountChildren | @ | ReactMultiChild.js:234
  | _createInitialChildren | @ | ReactDOMComponent.js:701
  | mountComponent | @ | ReactDOMComponent.js:520
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | mountChildren | @ | ReactMultiChild.js:234
  | _createInitialChildren | @ | ReactDOMComponent.js:701
  | mountComponent | @ | ReactDOMComponent.js:520
  | mountComponent | @ | ReactReconciler.js:43
  | performInitialMount | @ | ReactCompositeComponent.js:368
  | mountComponent | @ | ReactCompositeComponent.js:255
  | mountComponent | @ | ReactReconciler.js:43
  | mountComponentIntoNode | @ | ReactMount.js:102
  | perform | @ | Transaction.js:141
  | batchedMountComponentIntoNode | @ | ReactMount.js:124
  | batchedUpdates | @ | ReactDefaultBatchingStrategy.js:58
  | batchedUpdates | @ | ReactUpdates.js:95
  | _renderNewRootComponent | @ | ReactMount.js:317
  | _renderSubtreeIntoContainer | @ | ReactMount.js:399
  | renderSubtreeIntoContainer | @ | ReactMount.js:340
  | Portal._this._renderOverlay | @ | LegacyPortal.js:75
  | componentDidMount | @ | LegacyPortal.js:97
  | (anonymous) | @ | ReactCompositeComponent.js:262
  | measureLifeCyclePerf | @ | ReactCompositeComponent.js:73
  | (anonymous) | @ | ReactCompositeComponent.js:261
  | notifyAll | @ | CallbackQueue.js:74
  | close | @ | ReactReconcileTransaction.js:78
  | closeAll | @ | Transaction.js:207
  | perform | @ | Transaction.js:154
  | perform | @ | Transaction.js:141
  | perform | @ | ReactUpdates.js:87
  | flushBatchedUpdates | @ | ReactUpdates.js:170
  | closeAll | @ | Transaction.js:207
  | perform | @ | Transaction.js:154
  | batchedUpdates | @ | ReactDefaultBatchingStrategy.js:60
  | batchedUpdates | @ | ReactUpdates.js:95
  | dispatchEvent | @ | ReactEventListener.js:145

@gss2002 Thanks for the details, I'll take a look at it in a while.

@shahsank3t found some more info.. When building on Centos7 and Rhel7 and OS X High Sierra I noticed the following vs the version pushed via the release here:
registry-0.4.0.tar.gz contains registry-webservice-0.4.0-SNAPSHOT.jar and it has more files than what I am getting when I build with maven. So the question is why are these missing??
 Something specific with maven. I've tried with Maven 3.3.3, 3.3.9 and Maven 3.5.2 all with same issues along with Oracle JDK 8_102, 8_121 and 8_151.. All with same issue missing the files I list above from the diff.
unzip -t webservice/target/registry-webservice-0.4.0-SNAPSHOT.jar
Archive:  webservice/target/registry-webservice-0.4.0-SNAPSHOT.jar
testing: META-INF/                OK
testing: META-INF/MANIFEST.MF     OK
testing: assets/                  OK
testing: assets/fonts/            OK
testing: assets/images/           OK
testing: assets/js/               OK
testing: assets/styles/           OK
testing: assets/styles/css/       OK
testing: assets/styles/img/       OK
testing: com/                     OK
testing: com/hortonworks/         OK
testing: com/hortonworks/registries/   OK
testing: com/hortonworks/registries/ha/   OK
testing: com/hortonworks/registries/ha/zk/   OK
testing: com/hortonworks/registries/listeners/   OK
testing: com/hortonworks/registries/webservice/   OK
testing: assets/fonts/fontawesome-webfont.eot   OK
testing: assets/fonts/fontawesome-webfont.ttf   OK
testing: assets/fonts/fontawesome-webfont.woff   OK
testing: assets/fonts/fontawesome-webfont.woff2   OK
testing: assets/fonts/glyphicons-halflings-regular.eot   OK
testing: assets/fonts/glyphicons-halflings-regular.ttf   OK
testing: assets/fonts/glyphicons-halflings-regular.woff   OK
testing: assets/fonts/glyphicons-halflings-regular.woff2   OK
testing: assets/images/fontawesome-webfont.svg   OK
testing: assets/images/glyphicons-halflings-regular.svg   OK
testing: assets/index.html        OK
testing: assets/js/application.js   OK
testing: assets/js/vendor.bundle.js   OK
testing: assets/styles/css/style.css   OK
testing: assets/styles/css/style.css.map   OK
testing: assets/styles/img/back-default.png   OK
testing: assets/styles/img/data-not-found.jpg   OK
testing: assets/styles/img/favicon.ico   OK
testing: assets/styles/img/logo.png   OK
testing: assets/styles/img/start-loader.gif   OK
testing: com/hortonworks/registries/ha/zk/ZKLeadershipParticipant$1.class   OK
testing: com/hortonworks/registries/ha/zk/ZKLeadershipParticipant.class   OK
testing: com/hortonworks/registries/listeners/TransactionEventListener$UnitOfWorkEventListener.class   OK
testing: com/hortonworks/registries/listeners/TransactionEventListener.class   OK
testing: com/hortonworks/registries/webservice/RegistryApplication$1.class   OK
testing: com/hortonworks/registries/webservice/RegistryApplication$2.class   OK
testing: com/hortonworks/registries/webservice/RegistryApplication.class   OK
testing: com/hortonworks/registries/webservice/RegistryConfiguration.class   OK
testing: META-INF/maven/          OK
testing: META-INF/maven/com.hortonworks.registries/   OK
testing: META-INF/maven/com.hortonworks.registries/registry-webservice/   OK
testing: META-INF/maven/com.hortonworks.registries/registry-webservice/pom.xml   OK
testing: META-INF/maven/com.hortonworks.registries/registry-webservice/pom.properties   OK

@gss2002

Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. Check the render method of SchemaFormContainer.

The above error is due to the version update of the react-select package to v1.1 whereas we need v1.0.0-rc.10.
0.3.0 build shouldn't have any such issues but 0.4.0 might have this since react-select's new version came out a couple of days before ours. I'll check that after creating a fix for this one.

@gss2002

[root@ha21t52nf goodjar]# diff -Naur /tmp/badfiles.txt /tmp/goodfiles.txt

In the above command, badfiles.txt is the output of released build version (0.3.0 or 0.4.0) or your local build?

0.4.0

More info looks like something is definitely related to npm/node with maven as the sizes and output of the javascript is definitely different
total 1212
-rw-r--r--. 1 root root  200899 Nov 21 09:22 vendor.bundle.js
-rw-r--r--. 1 root root 1032971 Nov 21 09:22 application.js
drwxr-xr-x. 6 root root      84 Nov 21 09:22 ..
drwxr-xr-x. 2 root root      50 Nov 21 09:22 .
[root@js]# pwd
/tmp/badjar/assets/js
[root@js]# ls -latr ../../../goodjar/assets/js/^C
total 1240
-rw-rw-r--. 1 root root  200790 Nov 30 09:04 vendor.bundle.js
-rw-rw-r--. 1 root root 1063012 Nov 30 09:04 application.js
drwxrwxr-x. 2 root root      50 Nov 30 09:04 .
drwxrwxr-x. 6 root root      84 Nov 30 11:07 ..

@gss2002
registry-0.4.0-src.zip? registry-0.4.0.zip? or Source code (zip)

More info looks like something is definitely related to npm/node with maven as the sizes and output of the javascript is definitely different

It can differ based on when the packaging is done. The day when the released version was packaged, maybe react-select package (or some other) version was not updated(or updated to a certain version) and today when you building it locally, npm has downloaded the latest react-select package. Does it make sense?

@gss2002 Raised PR https://github.com/hortonworks/registry/pull/310 to fix this.
You can try on your local with the fix and let me know if you still get an error.
@satishd - Days before we released 0.4.0 build, one of UI library (react-select) version for updated. For us, we already had the older version in our cache (node_modules/) and so it didn't matter but for any new user who builds (from the latest master or src build) will eventually end up getting latest version which breaks the UI. PR I have raised will fix that.
I was wondering would you like (& how) to add this fix to 0.4.0 version since it breaks the UI completely (won't let a user add a schema). Your thoughts?

I tried to build with this and it also fails because the zip doesn't contain node_modules.. This also happens with the 0.3.0 build also. Same issue
Just tried this
registry-0.4.0-src.zip

@shahsank3t testing the fix now on 0.4.0 source

@shahsank3t that patch fixes it for 0.4.0

@gss2002 Great. Thanks for testing out the patch.
JFYI: node_modules is never present in any src builds. It gets created and has all the libraries downloaded when you build it.
And that's the very same reason why all the previous released source builds will fail since the newer version of a library (react-select to be precise in our current case) is breaking the existing UI.

@shahsank3t thanks for helping resolve this so fast!! It's much appreciated and great work with Schema Registry so far! We have been using it with Nifi and Kafka

@satishd - Days before we released 0.4.0 build, one of UI library (react-select) version for updated. For us, we already had the older version in our cache (node_modules/) and so it didn't matter but for any new user who builds (from the latest master or src build) will eventually end up getting latest version which breaks the UI. PR I have raised will fix that.
I was wondering would you like (& how) to add this fix to 0.4.0 version since it breaks the UI completely (won't let a user add a schema). Your thoughts?

@shahsank3t We should not update existing 0.4.0 modules but we need to have a hotfix kind of release(may be 0.4.1) to address this issue. We should make sure UI is tested in a clean environment before the release.

@satishd This kind of issues tend to happen even if we test in a clean environment before releasing (only for users who build binaries from source).
Reason being in our package.json, we have auto-updating for few UI library and if those libs get update but fail to support backward compatibility, we run into such issues.
In the fix, I have fixed such lib version so we don't run into such issue again in future.

@gss2002 Thanks for reporting this issue. This will be part of 0.4.1 which will be released next week.


Port developement: vcpkg x-add-version

It seems there is a difference with "vcpkg x-add-version ..." on a branch with a remote to your own fork, or if you are not executing it on the master branch.
Don't know exactly which is the problem, but for me it produces the wrong result If I'm not executing it directly on my master branch, which has microsoft/vcpkg set as remote. Would be good if that would be documented somewhere in an understandable way
I could test out which one of the above produces the problem, but would need to create a PR for that to test on

Please provide steps to reproduce the problem. Many contributors use this command without a problem, on their personal forks and branches. (And basically it doesn't care about remotes.)

Alright I can't reproduce it for now :D So it probably has nothing to do with the remotes, I have know idea what caused that problem. I already had it two times on two different PRs, I have no idea what exactly I did differently from everyone else. Or even what I do differently from myself when it works. I thought that the branch was the only difference.
So perhaps close it for now, till I have the problem again and then can find out how to reproduce it?

Remember that you must git commit changes to  ports/<PORT> before running vcpkg x-add-version <PORT>.
(You can amend the previous commit. But you must preserve this order also when amending.)

Yes I know, that's also what I have done.  My problem was that the git-tree id was somehow wrong. But as I said I couldn't reproduce it, so I don't exactly know what I did wrong

If you are currently unable to reproduce this issue, please close this issue. If the same issue occurs in the future, please open this issue again or resubmit an issue.


add support for (non negative) signed integers in constantFoldCompare

radar rdar://problem/29033745
Constant propagation's constantFoldCompare() only supported the comparison between unsigned integers and zero.
This PR adds support + tests to the comparison of signed integers when said integers are inside a assumeNonNegative builtin

@swift-ci Please smoke test

@moiseev , @swiftix this should help with the code pattern you found.

@shajrawi Looks good. In principle, you could have put the AssumeNonNegative into the pattern as a nested m_BuiltinInst check...

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


python311Packages.dvc-data: 0.54.2 -> 0.54.3

Diff: https://github.com/iterative/dvc-data/compare/refs/tags/0.54.2...0.54.3
Changelog: https://github.com/iterative/dvc-data/releases/tag/0.54.3
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 236032 run on x86_64-linux 1

2 packages failed to build:

python311Packages.dvclive
python311Packages.dvclive.dist

10 packages built:

dvc
dvc-with-remotes
dvc-with-remotes.dist
dvc.dist
python310Packages.dvc-data
python310Packages.dvc-data.dist
python310Packages.dvclive
python310Packages.dvclive.dist
python311Packages.dvc-data
python311Packages.dvc-data.dist


Landing zone creation with collections fails for large study

In a study of 5000+ samples, creating a landing zone with collection creation enabled results in a timeout. Status at error:

Zone perpetually stuck with CREATING status
No errors logged in timeline, docker or even sentry
Zone collection does exist, with at least a part of the collections intended to be created

This same project didn't have these problems a short while ago, so my feeling is we managed to reach some limit somewhere and the

The failure was in fact caused by me restarting the celeryd process. This does still take a very long time though, will add a new ticket regarding parallelization.


17 Oct 2024 - A11y Theme Builder Meeting Minutes

Date
2024-10-17 - 09:15am EDT
Zoom info

Meeting link: https://zoom.us/j/91013899295?pwd=Qnh5UVN1aUZ4ak9tODgvMVNLNUg5Zz09
Meeting id: 910 1389 9295
Password: 123225
Call-in: +1<PHONE_NUMBER> US (New York) (Check calendar for more options)

Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene & roll call (5mins)
[x] Display FINOS Antitrust Policy summary slide
[x] Review Meeting Notices (see above)
[x] Approve past meeting minutes
[x] Community WG Update (@PaulaPaul)
[x] Mentorship Update (@omesh-omg)
[x] ...
[x] AOB, Q&A & Adjourn (5mins)

Minutes

As we reviewed last week's minutes, we discussed the results of the Grace Hopper event
Aaron spoke of the Community WG status

Meetings to re-convene beginning next Wednesday (2024-10-23) at its normal time.
Check the Finos calendar for more information (https://www.finos.org/calendar)

Omesh and Aaron spoke on the mentorship project

Omesh to create a document of blockers that he's encountered with the SDK
We'll use this document in a future meeting to start planning out the SDK work that needs to be accomplished once Evan and Aaron have freed up

Decisions Made

[ ] ...

Action Items

[ ] (from last week) Lise to get Omesh and Aaron CSS and responsive breakpoints and behaviors for #820 design

will provide CSS for framework only for now

[ ] (from last week)Aaron and Evan need to break the Epic that will be worked on by the mentee into detailed and digestable issues
[ ] (from last week) Lise to work with Aaron to update video in mkdocs documentation
[ ] (from last week) Cody to look at pre-push hook
[ ] (from last week) Aaron to follow up with author of #1026
[ ] Omesh to create a document of SDK blockers

Attendees of this meeting:
Aaron Reed - DFS
Kathleen Burkhardt - Black Rock
Omesh Kumawat

Approved in today's call


Aborted at<PHONE_NUMBER> (unix time) try "date -d @1708448659" if you are using GNU date

Has anyone seen this before??/ How do I fix this issue?
I'm trying to process my own set of data - I can process and view the example data easily and without issues but when I try to process my own images it is immediately stopping with this error:
(nerfstudio) C:\Users\india>ns-process-data images --data nerfstudio\data\IKdata\ScentDress --output-dir nerfstudio\data\IKdata
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1708448659" if you are using GNU date ***
@     0x7ffad8c94090 log2f
@     0x7ff77df82698 OPENSSL_Applink
@     0x7ffabc14e390 __C_specific_handler
@     0x7ffadb7d441f __chkstk
@     0x7ffadb74e466 RtlFindCharInUnicodeString
@     0x7ffadb7d340e KiUserExceptionDispatcher
@     0x7ffa9219264e void __cdecl __ExceptionPtrRethrow(void const * __ptr64)
@     0x7ff93358916e public: void __cdecl c10::ivalue::Future::markCompleted(void) __ptr64
@     0x7ff933919d42 struct _object * __ptr64 __cdecl THPGenerator_initDefaultGenerator(struct at::Generator)
@     0x7ff932e5dec5 (unknown)
@     0x7ff9333b6b29 PyInit_pycolmap
@     0x7ffa99161080 (unknown)
@     0x7ffa991626a5 __NLG_Return2
@     0x7ffadb7d3c66 RtlCaptureContext2
@     0x7ff932e60936 (unknown)
@     0x7ffa5b2b6f60 _PyMethodDef_RawFastCallKeywords
@     0x7ffa5b2b5f26 _PyObject_MakeTpCall
@     0x7ffa5b2c266b PyWrapper_New
@     0x7ffa5b2fe34a _PyObject_GenericGetAttrWithDict
@     0x7ffa5b2fd939 PyObject_GetAttrString
@     0x7ff932e95dfe PyInit_pycolmap
@     0x7ff932eed98d PyInit_pycolmap
@     0x7ff932ec628d PyInit_pycolmap
@     0x7ff932e83ed0 (unknown)
@     0x7ff932e907a8 PyInit_pycolmap
@     0x7ff932e902ae PyInit_pycolmap
@     0x7ffa5b3c21cd PyImport_AppendInittab
@     0x7ffa5b3c1896 PyImport_Import
@     0x7ffa5b2f94b5 _PyCFunction_DebugMallocStats
@     0x7ffa5b2b606e PyVectorcall_Call
@     0x7ffa5b393a20 PyEval_GetFuncDesc
@     0x7ffa5b390571 _PyEval_EvalFrameDefault
Thank you in advance

I'm getting the same issues, whereas this was working for me just yesterday!

i got it fixed now. I deleted every file of nerfstudio and colmap and unistalled it. After that I re install colmap first by using the colmap documentation and not from the Nerfstudio page.
Dont use the vcpkg line!
After Colmap, reinstall the nerfstudio normally

i got it fixed now. I deleted every file of nerfstudio and colmap and unistalled it. After that I re install colmap first by using the colmap documentation and not from the Nerfstudio page. Dont use the vcpkg line! After Colmap, reinstall the nerfstudio normally

I'm having this issue as well.  Everything was working just fine until I tried to install HLOC so I could use it for feature extraction and matching...now the ns-process-data command produces the kind of error seen above posted by others.  I can still run ns-train, though.
Which folders and files, specifically, did you delete?  And, when reinstalling colmap via the colmap documentation, which vcpkg line did you avoid?
Thanks in advance!

i got it fixed now. I deleted every file of nerfstudio and colmap and unistalled it. After that I re install colmap first by using the colmap documentation and not from the Nerfstudio page. Dont use the vcpkg line! After Colmap, reinstall the nerfstudio normally

I'm having this issue as well. Everything was working just fine until I tried to install HLOC so I could use it for feature extraction and matching...now the ns-process-data command produces the kind of error seen above posted by others. I can still run ns-train, though.
Which folders and files, specifically, did you delete? And, when reinstalling colmap via the colmap documentation, which vcpkg line did you avoid?
 I deleted every file of nerfstudio and colmap and unistalled it. After that I re install colmap first by using the colmap documentation and not from the Nerfstudio page. Dont use the vcpkg line! After Colmap, reinstall the nerfstudio normally

I'm having this issue as well. Everything was working just fine until I tried to install HLOC so I could use it for feature extraction and matching...now the ns-process-data command produces the kind of error seen above posted by others. I can still run ns-train, though.
Which folders and files, specifically, did you delete? And, when reinstalling colmap via the colmap documentation, which vcpkg line did you avoid?
  I ended up having to make a new conda environment and reinstall nerfstudio (without trying to install hloc).  Nerfstudio is back up and running now...hoping they get hloc to work.  Maybe I'll clone the new working environment, uninstall pycolmap and then try hloc again.  I was just hoping hloc might do a better job of matching/calibrating camera poses.  We have a few really challenging data sets that colmap simply isn't doing a great job with.  Hloc might not fare any better, but I at least wanted to be able to give it a shot!  Thanks for the reply!

Any luck with this problem? I am experiencing the same problem. I can get around with it by uninstalling pycolmap. However, by doing this I am not able to use hloc.

I just found something at a recent issue #2935. It works for me and I am able to run hloc now.

I just found something at a recent issue #3161. It works for me and I am able to run hloc now.

Nice!  Maybe I'll give it another shot.  I'll probably build a new environment to test it so I don't hose my existing one again, lol.  Does hloc seem to help with the matching/camera calibration process?

No, for me the result is not better...

No, for me the result is not better...

There doesn't really seem to be a magic bullet with this stuff outside of doing your best to take high quality photos with plenty of continuity/common objects between shots.


opensubdiv doesn't compile

Issue description
opensubdiv-3.3.0 fails to compile. Relevant output:
[ 87%] Built target osd_gpu_obj
[ 89%] Building NVCC (Device) object opensubdiv/CMakeFiles/osd_dynamic_gpu.dir/osd/./osd_dynamic_gpu_generated_cudaKernel.cu.o
/nix/store/xd2mlzvlgmskbyyb33lz2vdq15k74xpr-glibc-2.26-75-dev/include/bits/floatn.h(61): error: invalid argument to attribute "__mode__"

/nix/store/xd2mlzvlgmskbyyb33lz2vdq15k74xpr-glibc-2.26-75-dev/include/bits/floatn.h(73): error: identifier "__float128" is undefined

2 errors detected in the compilation of "/tmp/nix-build-opensubdiv-3.3.0.drv-0/tmpxft_00007876_00000000-6_cudaKernel.cpp1.ii".
CMake Error at osd_dynamic_gpu_generated_cudaKernel.cu.o.cmake:264 (message):
  Error generating file
  /tmp/nix-build-opensubdiv-3.3.0.drv-0/source/build/opensubdiv/CMakeFiles/osd_dynamic_gpu.dir/osd/./osd_dynamic_gpu_generated_cudaKernel.cu.o

Steps to reproduce
build opensubdiv-3.3.0 from source.
Technical details

System: 18.03pre119292.cfafd6f5a8 (Impala)
Nix version: nix-env (Nix) 1.11.15
Nixpkgs version: "18.03pre119910.27831cbd86"
Sandboxing enabled: false

I can reproduce this error when cuda is enabled.

Related issue: caffe2/caffe2/issues/1194
It seems to be a problem with cuda 3.3.0 and glibc 2.26

Evaluating nixpkgs-unstable with these arguments, opensubdiv build with cuda support, specifically with cuda 10.2: https://hercules-ci.com/accounts/github/SomeoneSerge/derivations/%2Fnix%2Fstore%2Fc6knggf4rffvm24vd6b1il2cm8l9azs2-opensubdiv-3.4.4.drv?via-job=5db289ae-240a-40c3-95c3-9eb0566ce090


Improve UI and functionality of Crypto Tracker blog for enhanced aesthetics and user experience

Fixed #771
https://github.com/user-attachments/assets/068bc192-7294-4785-aee6-26f73e999eec

@MastanSayyad

@vanshchauhan21 remove the levels!! It is clear that you broke the guidelines and did spams!


Properly own the duplicated string

The original code would not ensure that string duplication succeeded and failed to properly own the duplicated string when the fully assembled object couldn't be "pushed" into the collection.

:+1:

+1

Merged

Commit https://github.com/openssl/openssl/commit/b7b8e948014d93e1eb6d954d0799ae68ab0e068b


feat: add timeswap-lens-followers group in playground

Badge for early timeswap followers on lens

Hey @waverune, thanks for the PR!
It should appear in https://playground.sismo.io in around 5 minutes :-)


Add readme for microsoft/dotnet-framework-build repo

View the second commit if you want to see a nice view of what changed in README.dotnet-framework.md.

I am coming to the conclusion that we should provide 3.5 builder images from the start. See: https://github.com/Microsoft/dotnet-framework-docker-samples/pull/16#pullrequestreview-79669205

@richlander - README.md looks much better.  Are you good with merging?  If not what work remains?


running by Docker is not working

My System: Windows 8, I am using: Docker Toobox
After changing database connection string  "databaseConnectionString": "mongodb://mongodb:27017/expresscart"
and executing: docker-compose up --build
Visiting  http://<IP_ADDRESS>:1111 doesnt show the site
I got below in terminal and terminal hangs up (Note: mongo and expressCart container does show in the docker ) :
D:\Node project\expressCart-master\expressCart-master>docker-compose up --build
Creating network "expresscart-master_default" with the default driver
Creating volume "expresscart-master_expresscart-mongo-data" with default driver
Pulling mongodb (mongo:3.4.10)...
3.4.10: Pulling from library/mongo
c4bb02b17bb4: Pulling fs layer
3f58e3bb3be4: Pulling fs layer
c4bb02b17bb4: Pull complete
3f58e3bb3be4: Pull complete
a229fb575a6e: Pull complete
8f5ddc533743: Pull complete
5e9d2af6e206: Pull complete
8b17a0553222: Pull complete
1723351cb8b4: Pull complete
78dd8437755a: Pull complete
61012c043572: Pull complete
76aeb242d479: Pull complete
bdc8171e92f4: Pull complete
Digest: sha256:b84baeffd0f14bebaf057b36de9414ee41584a897351795f4a3889257cf19b6d
Status: Downloaded newer image for mongo:3.4.10
Building expresscart
Step 1/17 : FROM mhart/alpine-node:8
8: Pulling from mhart/alpine-node
5a3ea8efae5d: Pull complete
daa037a6151f: Pull complete
Digest: sha256:c880e941cde8af52dbd543f1c3a45b0f53b8370f906f6f469581edadf2059df9
Status: Downloaded newer image for mhart/alpine-node:8
 ---> b9df20fda4ef
Step 2/17 : ENV NODE_VERSION 8.9.4
 ---> Running in e7559ce45246
Removing intermediate container e7559ce45246
 ---> 996aff966848
Step 3/17 : RUN apk add --no-cache make gcc g++ python bash
 ---> Running in 6a4de3ad9021
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz
(1/25) Installing ncurses-terminfo-base (6.0_p20171125-r1)
(2/25) Installing ncurses-terminfo (6.0_p20171125-r1)
(3/25) Installing ncurses-libs (6.0_p20171125-r1)
(4/25) Installing readline (6.3.008-r5)
(5/25) Installing bash (4.3.48-r1)
Executing bash-4.3.48-r1.post-install
(6/25) Installing binutils-libs (2.30-r1)
(7/25) Installing binutils (2.30-r1)
(8/25) Installing gmp (6.1.2-r0)
(9/25) Installing isl (0.17.1-r0)
(10/25) Installing libgomp (6.3.0-r4)
(11/25) Installing libatomic (6.3.0-r4)
(12/25) Installing pkgconf (1.3.7-r0)
(13/25) Installing mpfr3 (3.1.5-r0)
(14/25) Installing mpc1 (1.0.3-r0)
(15/25) Installing gcc (6.3.0-r4)
(16/25) Installing musl-dev (1.1.16-r15)
(17/25) Installing libc-dev (0.7.1-r0)
(18/25) Installing g++ (6.3.0-r4)
(19/25) Installing make (4.2.1-r0)
(20/25) Installing libbz2 (1.0.6-r5)
(21/25) Installing expat (2.2.0-r1)
(22/25) Installing libffi (3.2.1-r3)
(23/25) Installing gdbm (1.12-r0)
(24/25) Installing sqlite-libs (3.25.3-r0)
(25/25) Installing python2 (2.7.15-r0)
Executing busybox-1.26.2-r11.trigger
OK: 208 MiB in 40 packages
Removing intermediate container 6a4de3ad9021
 ---> f8b3137927c7
Step 4/17 : WORKDIR /var/expressCart
 ---> Running in 6ed5661066dc
Removing intermediate container 6ed5661066dc
 ---> 2b5cfcf0a37d
Step 5/17 : COPY lib/ /var/expressCart/lib/
 ---> f54b49ddff01
Step 6/17 : COPY bin/ /var/expressCart/bin/
 ---> 8cd111eeba01
Step 7/17 : COPY config/ /var/expressCart/config/
 ---> 3fc769e44a11
Step 8/17 : COPY public/ /var/expressCart/public/
 ---> 2c70e3fb2f42
Step 9/17 : COPY routes/ /var/expressCart/routes/
 ---> 2fc3ad9964cf
Step 10/17 : COPY views/ /var/expressCart/views/
 ---> c3ff4c74520d
Step 11/17 : COPY app.js /var/expressCart/
 ---> ac1f39e9a854
Step 12/17 : COPY package.json /var/expressCart/
 ---> d6990c64503b
Step 13/17 : COPY gulpfile.js /var/expressCart/
 ---> 0d913acea24d
Step 14/17 : RUN npm install
 ---> Running in 3dce193ad42a
npm WARN deprecated<EMAIL_ADDRESS>bcrypt-nodejs is no longer actively maintained. Please use bcrypt or bcryptjs. See https://github.com/kelektiv/node.bcrypt.js/wiki/bcrypt-vs-brypt.js to learn more about these two options
npm WARN deprecated<EMAIL_ADDRESS>Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header).  This notice will go away with v5.0.2+ once it is released.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to 2.2.19 or higher

><EMAIL_ADDRESS>install /var/expressCart/node_modules/fibers
> node build.js || nodejs build.js

make: Entering directory '/var/expressCart/node_modules/fibers/build'
  CXX(target) Release/obj.target/fibers/src/fibers.o
  CXX(target) Release/obj.target/fibers/src/coroutine.o
  CC(target) Release/obj.target/fibers/src/libcoro/coro.o
  SOLINK_MODULE(target) Release/obj.target/fibers.node
  COPY Release/fibers.node
make: Leaving directory '/var/expressCart/node_modules/fibers/build'
Installed in `/var/expressCart/node_modules/fibers/bin/linux-x64-57-musl/fibers.node`

><EMAIL_ADDRESS>postinstall /var/expressCart/node_modules/core-js
> node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /var/expressCart/node_modules/node-cron
> opencollective-postinstall

Thank you for using node-cron!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/node-cron/donate

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.3.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/glob-watcher/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1121 packages from 494 contributors and audited 8512 packages in 79.66s
found 0 vulnerabilities

Removing intermediate container 3dce193ad42a
 ---> f4308de707e2
Step 15/17 : VOLUME /var/expressCart/data
 ---> Running in ecd772a8fc8d
Removing intermediate container ecd772a8fc8d
 ---> 300813b670e6
Step 16/17 : EXPOSE 1111
 ---> Running in 94affc999a67
Removing intermediate container 94affc999a67
 ---> 825a066d12b8
Step 17/17 : ENTRYPOINT ["npm", "start"]
 ---> Running in c19b3ab92d29
Removing intermediate container c19b3ab92d29
 ---> 70a6d41e2c43
Successfully built 70a6d41e2c43
Successfully tagged node:8
Creating expresscart-mongodb ... done
Creating expresscart         ... done
Attaching to expresscart-mongodb, expresscart
expresscart    |
expresscart    | ><EMAIL_ADDRESS>start /var/expressCart
expresscart    | > node app.js
expresscart    |
expresscart    | Setting up indexes..
expresscart    | - Product indexing complete
expresscart    | - Order indexing complete
expresscart    | - Customer indexing complete

This is working as expected in latest version.


ParaTimes: deposit and withdraw

Next PRs will cover:

logic for custom fees
add warnings (old extension modals)
improve UX for transaction errors
ledger (some extra warnings)
CR:I think this should be BigInt(amount) > BigInt(value), and no need for EVM specific variant

#978 fees component, unit tests, allow access route only when wallet is 'open'

I will push more UI changes here


Add feature gate for AppArmorFields in v1.30

Searched for AppArmor in Kubernetes code base
Tracked to this code PR.
This was implemented for KEP-24.

/sig node
cc: @tallclair @kubernetes/sig-node-leads
Can we please get some help contributing some detail to this feature gate doc? We appreciate it, thanks!


Confusing Licensing Information in Gradle User Manual

Hello, I'm looking to update Gradle's entry in the Free Software
Directory, and I noticed some files in the user manual that have
confusing licensing information.
A couple of files in the user guide say that the "Gradle user manual
and DSL reference manual are licensed under Creative Commons
Attribution-NonCommercial-ShareAlike 4.0 International License." This
sentence appears in licenses.adoc and userguide.adoc. Both of
these files have an invisible Apache license header (example), but
not all of the files in the userguide directory have those headers. For
example, extending-gradle/custom_gradle_types.adoc does not have
that header.
Is some of the user guide dual-licensed, and are the files without
Apache headers CC-BY-NC-SA only? What was the intended license for the
documentation?
Expected Behavior

The Gradle User Manual should have clear licensing information in which invisible headers match visible text. If the text is meant to be dual-licensed, both the invisible headers and visible text should have both licenses.
Current Behavior

The Gradle User Manual has some files with invisible headers that do not match what the visible text says about licensing. As a result, the licensing of the Gradle User Manual is unclear.
Context

I want to update Gradle's entry in the Free Software Directory, so that free software that uses Gradle as a dependency can be added to the directory more easily. For Gradle to be added to the Free Software Directory, the source repository should not contain nonfree documentation. For documentation to be free, it needs a free license, which would include Apache but not CC-BY-NC-SA. Resolving the documentation issue is a step towards updating Gradle's entry in the Free Software Directory.
Steps to Reproduce

Go to https://raw.githubusercontent.com/gradle/gradle/master/subprojects/docs/src/docs/userguide/licenses.adoc and see the Apache header at the top as well as the text towards the bottom that mentions "Creative Commons Attribution-NonCommercial-ShareAlike 4.0".
Your Environment

Build scan URL: not applicable
It probably doesn't matter which web browser you use, but the licensing information appears in both Abrowser 108.0 and curl 7.68.0.

Sorry for the late reply.
Thank you for your interest in Gradle!
This is a valid issue that we will address.


Video on Failed Tests only option

Added option to only add video recordings to failed tests in the mochawesome report

@LironEr I went for the lazy option of using the screenshot-folder example for the testing of this reporterOption instead of making a separate set of examples for it (like I probably should have) with the corresponding tests... Let me know if that's a blocker for you or if you can give it a pass 😉


Duplicate tags

When generating markdown syntax for detection rules, tags that are not Mitre ATT&CK tags are generated and listed twice in the "other" tags syntax.

Hey @xg5-simon
Thank you for notification. Issue has been fixed


Document post requests

I don't understand this issue.

The fresh docs currently only show how to write handlers for GET requests but not POST requests. It would be helpful to have an example that includes using the POST request body
(Also thanks for your work on this framework!)

Hey!
I'm not sure if anyone has been working on this, but I have a PR open addressing this. Thank you!


Dockerfile improved

Hello! I see that you've significantly revised the Dockerfile and everything has improved, but I have a couple of comments:

Hiding the Dockerfile in .dockerfile may not be the best idea. Historically, in most repositories, it's stored in the root directory so that one can easily navigate to the repository, execute the 'docker build' command, and compile the project. Could you consider adhering to this convention?

I notice that you haven't set default environment variables, instead moving them to the README. While this is a viable approach, many clients and other "life simplifying" tools use this information for easy importing (e.g. Synology's Dockerfile interface, IDEs, and so on).

Please think about these points as they could make the project easier to use for others.
Your hard work is appreciated!

Hi!

If the .dockerfile contents is good enough for general use I can move it to Dockerfile, np. I was not really sure if it suits all the cases as it's just a wrapped binary w/o any OS.
Do you mean that some tools are exposing the Dockerfile's ENV block? If so I'm totally fine to add them. I wasn't aware of such behavior 🤔

This isn't strictly necessary, it's just that sometimes it can be more convenient :)


integration with redux

I may keep the forms implemented in native react, with jobid storage in redux.

Being addressed in release-4.0.0. As of https://github.com/superphy/reactapp/commit/8fc0c0f756e7f3a79748c4a89b52639aa5aabb3d the jobIds are added to redux store correctly

For building Results cards, see https://github.com/superphy/reactapp/issues/17

Complete as of https://github.com/superphy/reactapp/pull/23


If a attacker break mostly through the ramparts send all resources away

Describe what you want the bot to do
Before the attacker reach the inside of a room we should transfer the resources from the storage to the terminal and transfer all of them to the neares safe room.
And we should stop to transfer back resources to the attacked room by the manageAllyRequests() and transfer only energy of needed.
Idea is to minimize losing all of the resources inside the room.

I love it. Will get to work on it soon


Windows authentication with dotnet watch?

The IIS snippet works when the application is published and running under IIS, but doesn't work with dotnet watch. And vice-versa: The others don't work with IIS.

Do I have to use different configuration with IIS and with dotnet watch run (both Negotiate and HTTPSys seems to work)? Or did I miss something?
If yes, what is the most reliable way to detect if the application is running under IIS? I know I can pass ASPNETCORE_ENVIRONMENT, but is there a way explicitly detect IIS as that feels the best.
Official concrete example would be welcome, because mis-configuration may lead to potential security issue.

This does work, but feels hack-ish; would be :
#if DEBUG
// works with dotnet watch
            services.AddAuthentication(NegotiateDefaults.AuthenticationScheme)
                    .AddNegotiate();
#else
// works under IIS
            services.AddAuthentication(IISDefaults.AuthenticationScheme);
#endif

Any better way to do it?

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

ID: 401ad9a0-9e51-80a2-5846-82e9790d7257
Version Independent ID: fbc36c26-9992-1f4c-66d3-02f898ee7ec4
Content: Configure Windows Authentication in ASP.NET Core
Content Source: aspnetcore/security/authentication/windowsauth.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @scottaddie
Microsoft Alias: riande

If you're just asking about the conditional service registration, did you see/try ...
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-3.1#inject-iwebhostenvironment-into-the-startup-class

@guardrex  You are right, conditional service registration would look nicer. Should have made my question clearer.
To clarify:

Do I have to use different configuration with IIS (code from the IIS section works) and with dotnet watch run (both Negotiate and HTTPSys seems to work)? Or did I miss something?
If yes, what is the most reliable way to detect if the application is running under IIS? I know I can pass ASPNETCORE_ENVIRONMENT, but is there a way explicitly detect IIS as that feels the best.
Official concrete example would be welcome, because mis-configuration may lead to potential security issue.

It's very difficult for the team to provide guidance for all of the scenarios out there ... there are so many ways to set things up that we don't have the capacity to cover them all. Our general guidance is to talk to devs on support channels for assistance ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

WRT your questions ... a few quick thoughts .........
In my way of thinking about hosting apps, IIS would be the Production environment. Running with dotnet watch would occur in the Development environment. Each would have its own config generally for all differences between Production and Development (e.g., using the appsettings.{Environment}.json files. That's the way that I would go.
On on your second question, "pass ASPNETCORE_ENVIRONMENT"? I don't follow ... You can get the environment anywhere by injecting IWebHostEnvironment. Yes, I think I would stick with a simple Production/Staging/Development model and check for the environment to know if the app is on IIS or not. That's what I would do.
Example? I don't think I understand what you're asking for an example of. We have examples for the pattern that I've described across the Fundamentals node docs.


freeipa provisioner should follow redirects

freeipa.go code uses low level http.transport which doesn't follow redirects
https://github.com/guilhem/freeipa-issuer/blob/master/provisionners/freeipa.go#L32
https://github.com/golang/go/blob/master/src/net/http/transport.go#L71
So when it tries to connect IPA server via unencrypted HTTP and by chance gets redirested to
https://ipa.beer.best/ipa/session/login_password , it fails with HTTP 400

@bd-spl did you find out what was the reason? We are getting the same error.


should we refactor the plugins to be in the org.apache.maven.plugins folder?

Not 100% sure on this one ;) Only if folks just type this:
$ mvn fabric8:setup
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
Downloading: https://repo.maven.apache.org/maven2/com/ning/maven/plugins/maven-metadata.xml
Downloaded: https://repo.maven.apache.org/maven2/com/ning/maven/plugins/maven-metadata.xml (616 B at 0.8 KB/sec)
Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml (13 KB at 16.9 KB/sec)
Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (20 KB at 26.1 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.262 s
[INFO] Finished at: 2016-09-02T18:40:47+01:00
[INFO] Final Memory: 14M/302M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "quickstarts" could not be activated because it does not exist.
[ERROR] No plugin found for prefix 'fabric8' in the current project and in the plugin groups [com.ning.maven.plugins, org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/jstrachan/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException

in a project which hasn't been configured to use fabric8 yet, it can't find the fabric8-maven-plugin as its in the io.fabric8.maven package.
Not 100% sure if we should do this - just floating the idea; lots of mvn plugins seem to be in this package

AFAIK this is only 'allowed' for plugins which are blessed by Maven itself, which are plugins named like 'maven-foobar-plugin'. All others named liked 'foobar-maven-plugin' are supposed to be non-official plugins and cannot benefit from this short form. Also one need to get out plugin into Maven central's maven-metadata.xml which I'm afraid will not be easy.

Yeah - lets not bother ;)


Let's Encrypt certificates sometimes fails to write to Traffic Vault - postgresql

Notices that this happened after a 6.1.0 upgrade from 5.1.2 and also after a Traffic Vault Riak -> Postgresql migration.
This Bug Report affects these Traffic Control components:

Traffic Ops

Current behavior:
When requesting certificate renewal, the ACME/Let's Encrypt process goes through but fails to write the new certificate to the database.
/var/log/message:
Oct 12 13:52:13 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:13 [INFO] acme: Querying account for https://acme-v02.api.letsencrypt.org/acme/acct/102607427
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [] acme: Trying renewal with 543 hours remaining
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Obtaining bundled SAN certificate
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/163738563286
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Could not find solver for: tls-alpn-01
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Could not find solver for: http-01
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: use dns-01 solver
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Preparing to solve DNS-01
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Trying to solve DNS-01
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Checking DNS record propagation using [x.x.x.x:53]
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] Wait for propagation [timeout: 20m0s, interval: 30s]
Oct 12 13:52:14 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:14 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Waiting for DNS record propagation.
Oct 12 13:52:44 cdn1cdcms0001 traffic_ops: 2022/10/12 13:52:44 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Waiting for DNS record propagation.
Oct 12 13:53:01 cdn1cdcms0001 systemd: Started Session 56323 of user root.
Oct 12 13:53:20 cdn1cdcms0001 traffic_ops: 2022/10/12 13:53:20 [INFO] [crs.national-linear-red.cdn1.coxlab.net] The server validated our request
Oct 12 13:53:20 cdn1cdcms0001 traffic_ops: 2022/10/12 13:53:20 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Cleaning DNS-01 challenge
Oct 12 13:53:20 cdn1cdcms0001 traffic_ops: 2022/10/12 13:53:20 [INFO] [crs.national-linear-red.cdn1.coxlab.net] acme: Validations succeeded; requesting certificates
Oct 12 13:53:20 cdn1cdcms0001 traffic_ops: 2022/10/12 13:53:20 [INFO] [crs.national-linear-red.cdn1.coxlab.net] Server responded with a certificate.

Traffic Ops Log:
x.x.x.x:55562 national-linear-red: putting keys in Traffic Vault: could not begin Traffic Vault PostgreSQL transaction: context deadline exceeded: context deadline exceeded
Error posting acme certificate to Traffic Vault: could not begin Traffic Vault PostgreSQL transaction: context deadline exceeded: context deadline exceeded
failed to write response (method = POST, URL = /api/4.0/deliveryservices/xmlId/national-linear-red/sslkeys/renew, request ID = 711, remote addr = x.x.x.x:55562, bytes written = 0): http: Handler timeout

Expected behavior:
Certificate to be written to DB.
Steps to reproduce:
See above.

Notices that this happened after a 6.1.0 upgrade from 5.1.2 and also after a Traffic Vault Riak -> Postgresql migration.

Does that mean after doing both of those things, or after doing either of them?

Seems related to #7128. Looks like there is issues with Traffic Vault - postgresql backend.

@smalenfant - can you add to the description which version(s) of TC this bug exists in.

@mitchell852 I added. I'm pretty this should also affect master/7.1.x as I don't see changes regarding the backend.

Just an update here. When I issue a renew, this will always happen on the first try (500 error on the UI). I just go back and renew again and it "renews successfully".
First "renew":
2023/01/23 14:01:45 [INFO] [*.ds.cdn1.coxlab.net] acme: Validations succeeded; requesting certificates
Error posting acme certificate to Traffic Vault: could not begin Traffic Vault PostgreSQL transaction: context deadline exceeded: context deadline exceeded
Second "renew":
2023/01/23 14:03:42 [INFO] [*.ds.cdn1.coxlab.net] Server responded with a certificate.

I fixed/workaround this problem by increasing the timeouts in cdn.conf from 60 seconds to 120 seconds. The renew API is not asynchronous and prone to timeout depending how long it takes to complete the renewal.
I'm not exactly sure which one of the 8-10 timeout defined fixed it. Possibly the idle_timeout.


instuctions

how do you combine this with the python code? and can a custom gui be made with it?

bump

Lol.

bump again


1.10 bugfix backport

As mentioned at some issues, I'm backporting the fixes of 1.11 to 1.10. The idea is to backport a lot of fixes to make one last and final 1.10 version with the latest fixes to make that version a lot more stable for the users of it.
Huge thanks and shout out to @thiakil for the largest part of back porting!
Things added:

ForgeEnergy support
IItemHandler support
Username to UUID conversion to make it non-breaking
Formulatic assembler stock controll

Bugfixes:

Silktouch drops of miner
Better gas management
Fluid issues
IMC Recipe removal
Runoff worldgen
Better computer support
Atomic assembler offhand
Client desync causing wrong facings and nullpointers
Lot more of little changes

Reason for WIP: There are some issues with the backported item handling of logistical transporter pipes.

There's still one known bug remaining in this regarding item handling with logistical pipes.
When a machine on auto output pushes something in a pipe which is connected to a chest the resulting itemstack has a size of 0.
Still debugging that fault, for the rest it looks stable and doesn't crash.

@thommy101 I'd suggest looking at getPredictedInsert if you haven't already. I recall having to fudge that method a lot because the API used didn't exist in 1.10

That does sound like a probable cause by the name of it, thanks!

Finally got some time to check the last issue here. Looks like getPredictedInsert is functioning correctly, the correct TransporterStack is given to MultipartTransporter's transit HashList. But somewhere when transporting "in the pipe" the stack amount gets changed to 0. Still looking where that would/could happen.

Found the missing commit! ba3c37b6c3eb2d9cde0a681463725afc4610a7ff
Branch is ready for merge! 😃

O_O
Where I never would have thought to look (because of the commit message)
Jolly good work!

Commit messages might be slightly misleading... Learned it the hard way
I didn't look at the commits, I debugged for hell until I found one thing messing with itemstacks which could cause the bug, launching my 1.12 workspace I saw some differences and thanks to git annotate I found the corresponding commit :)

This is great, thanks!


Build with public assets fails

Describe the bug
Hey, I have a custom slidev theme which I deployed on an interal artifactory (npm like).
The theme has custom styles, components and layouts as well as some assets like pictures stored in the themes public directory (for example bg_gray.png).
So far so good: I am able to build and deploy my theme as an NPM package in my artifactory.
I am also able to pull the theme into my slides repo and use it while running npm run dev (slidev --open) (so slidev in dev mode/watch).
As soon as I want to build the slidedeck (slidev build) for deployment, I receive the following error:
vite v4.5.0 building for production...
transforming (33<EMAIL_ADDRESS><EMAIL_ADDRESS>referenced in<EMAIL_ADDRESS>didn't resolve at build time, it will remain unchanged to be resolved at runtime

<EMAIL_ADDRESS>referenced in<EMAIL_ADDRESS>didn't resolve at build time, it will remain unchanged to be resolved at runtime

<EMAIL_ADDRESS>referenced in<EMAIL_ADDRESS>didn't resolve at build time, it will remain unchanged to be resolved at runtime
✓ 97 modules transformed.
✓ built in 700ms
[vite]: Rollup failed to resolve import "alt1.png" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
Error: [vite]: Rollup failed to resolve import "alt1.png" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at viteWarn (file:///Users/user1/slides/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:48216:27)
    at onRollupWarning (file:///Users/user1/slides/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:48248:9)
    at onwarn (file:///Users/user1/slides/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:47976:13)
    at file:///Users/user1/slides/node_modules/rollup/dist/es/shared/node-entry.js:24194:13
    at Object.logger [as onLog] (file:///Users/user1/slides/node_modules/rollup/dist/es/shared/node-entry.js:25867:9)
    at ModuleLoader.handleInvalidResolvedId (file:///Users/user1/slides/node_modules/rollup/dist/es/shared/node-entry.js:24780:26)
    at file:///Users/user1/slides/node_modules/rollup/dist/es/shared/node-entry.js:24740:26

The themes repo has no special configuration for vite and as written above, in dev mode, everything works (including referenced images from the public dir of the theme).
But: to be able to reference Images in CSS in the Themes repo as well as the consuming repo, I had to define a small CSS trick in the themes CSS:
background-image: url("node_modules/@my-npm-org/slidev-theme-my-theme/public/bg_gray.png"), url("/bg_gray.svg")

This was needed, so the consuming repo is satisfied with the first part, the themes repo uses the local reference.
I Assume this way to do it is not the best / the wrong one. Can you help me solve it?
To Reproduce
Steps to reproduce the behavior:

Create a theme with referenced assets
Deploy the theme as NPM package
Use the theme
Run: slidev build

Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Slidev version: 0.44.0

Okay, I managed to fix it. There were two problems:
I replaced my assets in the theme package from public to assets and needed to adjust the paths (using a relative path):
problem in theme
-background-image: url("node_modules/@my-npm-org/slidev-theme-my-theme/public/bg_gray.png"), url("/bg_gray.svg")
+background-image: url("../assets/bg_gray.svg")

problem in slide repo
In the slide repo, the build was not successfull since I forgot the leading slashes (/):
-
+

Probably this helps others running into the same issues :)