rules yaml files updated as per yaml linting conditions

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

Proposed rule maturity level

Uncomment one (or more) /area <> lines (only for PRs that add or modify rules):

/area maturity-stable

/area maturity-incubating

/area maturity-sandbox

/area maturity-deprecated

What this PR does / why we need it:
to pass yaml lint workflow test.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Yaml_lint may fail on some lines. Am looking into them, and fix it ASAP!

Hey @FedeDP @Andreagit97 @incertum @leogr , finally i 🟢 YAML-Lint check for all rules yaml files🙃. But some other checks still ❌ and am not getting idea to solve it, please give me idea 🥲.

@FedeDP @leogr as per this discussion  I updated all rules files. Now our CI is completely happy 💚

/assign

Hi @leogr, what are your thoughts on this PR? Have we made any decisions yet? Feel free to assign me any related tasks; I would love to work on them.

Hi @leogr, what are your thoughts on this PR? Have we made any decisions yet? Feel free to assign me any related tasks; I would love to work on them.

I have only two points:

Line-width: 80 characters are too few, IMO. I'd propose 120 or more (@falcosecurity/rules-maintainers we need to reach a consensus on this -  cc @falcosecurity/core-maintainers your opinion is welcome).
Using > in yaml should be avoided since it appends an unwanted new line at the end (see example below)

- example1:
    bla bla bla
  example2: >
    bla bla bla

:point_down:
[
    {
        "example1": "bla bla bla",
        "example2": "bla bla bla\n"
    }
]

@h4l0gen, you can proceed to update this PR if you want to (it may be useful as a preview of the end result), but we need to reach a consensus on the style before merging it.

Hi @leogr, what are your thoughts on this PR? Have we made any decisions yet? Feel free to assign me any related tasks; I would love to work on them.

I have only two points:

Line-width: 80 characters are too few, IMO. I'd propose 120 or more (@falcosecurity/rules-maintainers we need to reach a consensus on this -  cc @falcosecurity/core-maintainers your opinion is welcome).
Using > in yaml should be avoided since it appends an unwanted new line at the end (see example below)

- example1:
    bla bla bla
  example2: >
    bla bla bla

👇
[
    {
        "example1": "bla bla bla",
        "example2": "bla bla bla\n"
    }
]

@h4l0gen, you can proceed to update this PR if you want to (it may be useful as a preview of the end result), but we need to reach a consensus on the style before merging it.

@falcosecurity/rules-maintainers @darryk10 @loresuso any thoughts on my above proposal?

Hi @leogr, what are your thoughts on this PR? Have we made any decisions yet? Feel free to assign me any related tasks; I would love to work on them.

I have only two points:

Line-width: 80 characters are too few, IMO. I'd propose 120 or more (@falcosecurity/rules-maintainers we need to reach a consensus on this -  cc @falcosecurity/core-maintainers your opinion is welcome).
Using > in yaml should be avoided since it appends an unwanted new line at the end (see example below)

- example1:
    bla bla bla
  example2: >
    bla bla bla

👇
[
    {
        "example1": "bla bla bla",
        "example2": "bla bla bla\n"
    }
]

@h4l0gen, you can proceed to update this PR if you want to (it may be useful as a preview of the end result), but we need to reach a consensus on the style before merging it.

@falcosecurity/rules-maintainers @darryk10 @loresuso any thoughts on my above proposal?

I agree with both points.
If we can remove the < , it would simplify the overall syntax, and it would be easier to maintain.

@leogr If we increase line length value, we will solve many issues of formatting, as I've accepted this format
- example1:
    bla bla bla
  example2: >
    bla bla bla

Above this one
[
    {
        "example1": "bla bla bla",
        "example2": "bla bla bla\n"
    }
]

as it gives line-length issue. So my vote to increase line length value.

Hi @leogr, need your confirmation, which one you prefer
- macro: inbound
  condition:
    (((evt.type in (accept,accept4,listen) and evt.dir=<) or
      (evt.type in (recvfrom,recvmsg) and evt.dir=< and
       fd.l4proto != tcp and fd.connected=false and fd.name_changed=true)) and
     (fd.typechar = 4 or fd.typechar = 6) and
     (fd.ip != "<IP_ADDRESS>" and fd.net != "<IP_ADDRESS>/8") and
     (evt.rawres >= 0 or evt.res = EINPROGRESS))

or
- macro: inbound
  condition:
    (
     (
      (evt.type in (accept,accept4,listen) and evt.dir=<) or
      (evt.type in (recvfrom,recvmsg) and evt.dir=< and fd.l4proto != tcp and fd.connected=false and fd.name_changed=true)
     ) and
     (fd.typechar = 4 or fd.typechar = 6) and
     (fd.ip != "<IP_ADDRESS>" and fd.net != "<IP_ADDRESS>/8") and
     (evt.rawres >= 0 or evt.res = EINPROGRESS)
   )

Hi @leogr, need your confirmation, which one you prefer
- macro: inbound
  condition:
    (((evt.type in (accept,accept4,listen) and evt.dir=<) or
      (evt.type in (recvfrom,recvmsg) and evt.dir=< and
       fd.l4proto != tcp and fd.connected=false and fd.name_changed=true)) and
     (fd.typechar = 4 or fd.typechar = 6) and
     (fd.ip != "<IP_ADDRESS>" and fd.net != "<IP_ADDRESS>/8") and
     (evt.rawres >= 0 or evt.res = EINPROGRESS))

or
- macro: inbound
  condition:
    (
     (
      (evt.type in (accept,accept4,listen) and evt.dir=<) or
      (evt.type in (recvfrom,recvmsg) and evt.dir=< and fd.l4proto != tcp and fd.connected=false and fd.name_changed=true)
     ) and
     (fd.typechar = 4 or fd.typechar = 6) and
     (fd.ip != "<IP_ADDRESS>" and fd.net != "<IP_ADDRESS>/8") and
     (evt.rawres >= 0 or evt.res = EINPROGRESS)
   )

I prefer the first one.

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

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

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.


Addressing #151: Naive approach to auto-generated operationIds

Thanks for PR, would you prefer a regular code review or should I just push changes to your branch?

Because you don't have much time, I just covered it with test on my own. This change should be already available in the latest snapshot, it'll be also officially available in the next general Javalin version.


Extract ResultLocation creation and handling code to ResultLocationCreator.

The code related to creation of ResultLocation classes is moved to ResultLocationCreator in order to clean-up public API.

Currently an instance of ResultLocationCreator lives inside ResultLocation. Eventually it could make sense to invert this dependency and make ResultLocationCreator actually create instance of ResultLocation.
ResultLocationCreator not only creates ResultLocation, but also performs some handling. Eventually we could split this into ResultLocationHandler.
A IRes1DDataSet properties are introduced to access MIKE 1D .NET instances. For release 1.0.0 we should either remove them and use get_m1d_dataset() or rename them to res1d_node, res1d_catchment, etc.

Looks good, thanks Gedi. I agree that something should be cleaned up for point 3, seeing node.node is confusing.

@ryan-kipawa Do you agree that I go ahead and rename it to node.res1d_node? This will break the current API in some cases (like for reaches), but it should not be used a lot.

Looks good, thanks Gedi. I agree that something should be cleaned up for point 3, seeing node.node is confusing.

@ryan-kipawa Do you agree that I go ahead and rename it to node.res1d_node? This will break the current API in some cases (like for reaches), but it should not be used a lot.

Yeah I agree. I also think it's not used much. If we want to be safe, we could make node a property that returns the new res1d_node, with a future deprecation warning.


Release diagnostics libraries version 4.3.0-beta06

Changes in Google.Cloud.Diagnostics.AspNetCore version 4.3.0-beta06:
Versions 4.3.0-beta04 and 4.3.0-beta05 were not released because of CI errors. This version contains all changes described for the unreleased version 4.3.0-beta04.
Changes in Google.Cloud.Diagnostics.AspNetCore3 version 4.3.0-beta06:
Versions 4.3.0-beta04 and 4.3.0-beta05 were not released because of CI errors. This version contains all changes described for the unreleased version 4.3.0-beta04.
Changes in Google.Cloud.Diagnostics.Common version 4.3.0-beta06:
Versions 4.3.0-beta04 and 4.3.0-beta05 were not released because of CI errors. This version contains all changes described for the unreleased version 4.3.0-beta04.
Packages in this release:

Release Google.Cloud.Diagnostics.AspNetCore version 4.3.0-beta06
Release Google.Cloud.Diagnostics.AspNetCore3 version 4.3.0-beta06
Release Google.Cloud.Diagnostics.Common version 4.3.0-beta06

Was wondering why they weren't showing on NuGet yesterday. Although, these aren't either. When will they show up there?

Internal only ;)


Civ 6011

Before creating a pull request make sure that:

[x] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-6010
https://tools.hmcts.net/jira/browse/CIV-6011
Change description
allow listing officer access GA "Hearing Scheduled" event and enter its screen 1
screen shots are in both ticket
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Re-opening this pull request as it was closed by stale bot


Mvn travis integration

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bug with Node compression module and require

wen i import compression module or if there is any module requires it, this is the error i get
var debug = require('debug')('compression')
                            ^

TypeError: require(...) is not a function

Please, provide more details, can't reproduce

Please, provide more details, can't reproduce

i dont know how to offer more details, i am using Fuse with TypeScript Compiler, could it be the reason ?
also i went back to Fuse version 1.3.23 and problem does not exist

i dont know how to offer more details, i am using Fuse with TypeScript Compiler, could it be the reason ?
also i went back to Fuse version 1.3.23 and problem does not exist

same as in #54 this error goes away up till version v1.3.33

i hope it's fixed in 1.3.38

not yet :)

with 1.3.39 it is solved :)


Show all uploaded images in the UI under the registry tab

Describe the feature
The Registry tab is already available as a placeholder. I'd like to display all uploaded images with additional information in a nice table on this page.

I will try to implement this with https://docker-py.readthedocs.io/en/stable/index.html

To me it looks like the docker SDK needs a connection to a docker socket. I can't directly talk to the registry. I'll probably have to use the request library to talk to the v2 API of the registry


Waterline truncated a join table - this is a MAJOR issue

I had an issue on a production server where all data from a join table was dropped. After days of investigation, I found out that waterline generated a delete statement without any where clause on that table.
Repro steps:

Create a Model with a many to many collection of elements. eg: Team <--> Player
Insert Team T1 with Players P1 and P2. Insert Team T2 with Players P3 and P4. This will generate two rows in the Team table, 4 rows in the Player table and 4 row in the Team_Player join table.
Issue two delete statements for team T1 at the same time. This is important and is probable with HTTP double post.
Waterline will generate the following (extract from my postgres log):

2015-01-27 21:57:02 EST LOG:  execute <unnamed>: DELETE  FROM "team" AS "team"  WHERE "team"."id" = $1  RETURNING *
2015-01-27 21:57:02 EST DETAIL:  parameters: $1 = '12'
2015-01-27 21:57:02 EST LOG:  execute <unnamed>: DELETE  FROM "team" AS "team"  WHERE "team"."id" = $1  RETURNING *
2015-01-27 21:57:02 EST DETAIL:  parameters: $1 = '12'
2015-01-27 21:57:02 EST LOG:  execute <unnamed>: DELETE  FROM "team_players__user_teams" AS "team_players__user_teams"  WHERE "team_players__user_teams"."team_players" IN ($1)  RETURNING *
2015-01-27 21:57:02 EST DETAIL:  parameters: $1 = '12'
2015-01-27 21:57:02 EST LOG:  statement: DELETE  FROM "team_players__user_teams" AS "team_players__user_teams"   RETURNING *

See the last delete statement that does not have a where clause. This will in fact truncate the table thus removing players from all games.
I traced the code and the following change created this issue: https://github.com/balderdashy/waterline/commit/388473fd207d0be7f15a5e42519a6ecadeea6cc7
I tried commenting the if and while I get an exception because the second delete does not return any result (var mappedValues = result.map(function(vals) { return vals[pk]; }); will not contain anything), I don't get any dataloss. Do I need to say that it is better to have an error because of concurrency instead of a silent truncation of all data?

Might also be related to https://github.com/balderdashy/waterline/issues/548.

It seems it is related to this #799 issue too

Just posted a PR in #815 for this

Also related to / duplicate of https://github.com/balderdashy/sails-mysql/issues/174

Wow! So this is a known issue for more than a month now. I had a major data loss in production (lost one day since i had to restore a nightly backup) that could have been avoided by simply disclosing the issue on the sails list.
That's it, i'm done with waterline. Thanks for the kick start but, i'm rewriting the codebase to use another lib.

@MacKeeper I'm so sorry about that, it sounds awful and I'm truly sorry waterline was the cause of this.
This should now be fixed in 0.10.17 thanks to https://github.com/balderdashy/waterline/pull/815

Closely related, also urgent: #858.


Problem with mapping of Materials

I expected to see:
Material: "Oil on Canvas"
but instead I saw:
Material is repeated:
Oil on Canvas		http://data.americanartcollaborative.org/dma/th...
Oil on canvas		http://data.americanartcollaborative.org/dma/th...
The current query was:
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX crm: <http://www.cidoc-crm.org/cidoc-crm/>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dc: <http://purl.org/dc/elements/1.1/>
PREFIX schema: <http://schema.org/>

SELECT ?material_name ?lod_material_term ?material_class
WHERE {
<http://data.americanartcollaborative.org/dma/object/3070639> a crm:E22_Man-Made_Object ;
  crm:P45_consists_of ?material_class .
?material_class a crm:E57_Material ;
  skos:prefLabel ?material_name .
OPTIONAL {
 ?material_class skos:broadMatch ?lod_material_term ;
}
FILTER (!isBlank(?material_class))
}

I can work around this in the browse app, but what's happening is that in the source data both spellings appear.
Our options are:

Treat them both as valid labels for the same concept (what we're doing now)
Treat them as two different concepts (probably not what you want)
fix this in the source data (probably the right solution, but not something that I can do.)


In need of Maintainer(s)

This repository is super helpful to those who use it. @zsprackett, @nstielau and @joemiller took great care of it for quite some time, but it looks now that they could use some help.
I'd like to bring up the need to have a regular maintainer. Someone who is strong in python, knows Sensu and is willing to join a growing number of maintainers across the Sensu projects (active members include @eheydrick @majormoses @luisdavim @sstarcher @mattyjones).
If you're interested, please comment on this issue. If you're a user of this repo, please give a 👍 to let us know you're using it and this is important to you.

I am certainly more than happy to maintain this, I have not done much python in a few years but look forward to picking that back up.
I would like to pose the question of if this currently is helpful enough to migrate to the sensu-plugins org or if we should start from scratch to untie our hands from any decisions that were previously made. I have not looked into the code yet so I do not yet have an opinion other than whatever the go forward path needs to live in sensu-plugins org.

That's a great discussion point @majormoses. I will also be reaching out to people more focused on Python that may have a vested interest in improving what is here. I would like either outcome, though I prefer if someone who has more time focused on Python+Sensu dives in.

As discused on slack I'd quite happily maintain this project or start an alternative from scratch that integrates sensu with python in a sensible manner.
All of the in-house checks we write at work are done in python and it would be good to have a solid alternative to the sensu_plugin gem to make life easier for python developers.

I'm very happy to learn that this exists I've mentioned before that we do need something like sensu-plugin for python. I didn't look at the code yet but for sure I can give an hand when needed.

I’m happy to get anyone more active access.

This can be closed now that @luisdavim and I are set up as maintainers.


[Bug]: v10 Android addView crash

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
Android
@rnmapbox/maps version
10.0.0-rc.5
Standalone component to reproduce
TODO
import React from 'react';
import {
  MapView,
  ShapeSource,
  LineLayer,
  Camera,
} from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{flex: 1}}>
        <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
        <ShapeSource id="idStreetLayer" shape={aLine}>
          <LineLayer id="idStreetLayer" />
        </ShapeSource>
      </MapView>
    );
  }
}

Observed behavior and steps to reproduce

Expected behavior
Adds/removes views without crashing
Notes / preliminary analysis
Only happening on Android.
Happens when switching states within app, so most likely there are items getting removed/added to the map.
This error does not happen on version 10.0.0-beta.73.
Additional links and references
No response

@sweatherall pls add reproduction, otherwise we cannot look into it.
This would happen if you added a view, as child to map view? Something like this, but even with this I cannot reproduce the issue?
You should also recede a warning:

import React from 'react';
import { View } from 'react-native';
import { MapView, ShapeSource, LineLayer, Camera } from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{ flex: 1 }}>
        <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
        <ShapeSource id="idStreetLayer" shape={aLine}>
          <LineLayer id="idStreetLayer" />
        </ShapeSource>
        <View>
          <View
            style={{
              borderColor: 'green',
              borderWidth: 2,
              width: 20,
              height: 20,
            }}
          />
          <View
            style={{
              borderColor: 'red',
              borderWidth: 2,
              width: 20,
              height: 20,
            }}
          />
          <ShapeSource id="idStreetLayer2" shape={aLine}>
            <LineLayer id="idStreetLayer2" />
          </ShapeSource>
        </View>
      </MapView>
    );
  }
}

export default BugReportExample;

Thank you for the response.
I found that the issue was that we had some MarkerViews that were wrapped in a react-native View - once I removed the View wrapper from around the MarkerView component - this crash no longer happened.
This must have been ok with previous versions of rnmapbox - but I'm happy to close this issue since it has a reasonable fix on our end.


Adding all in one c file

Well the issue can be resolved if all is put into one c file as in the PR. Tried the #include guard pattern instead of the #pragma once, but this didn't work.

Can be closed, as it is has been all addressed by #9  now.

Can be closed, as it is has been all addressed by #9  now.


loosen page name validation to allow page names to end in dates

The validatePageName function prevents me from ending my page names with a date.
For example, I placed a file called “notes 14.11.2024.md” in my space.
I can link this page no problem:

But actually opening the page results in a 404:

Using cmd+k, I can see the page, but opening it by pressing Enter results in an error toast:

It would be good to make the name validation more consistent, but more importantly, I would suggest to loosen or entirely remove name validation.
I can’t find an explanation of what the validation is good for. What’s wrong with using page names that end in file extensions?
And even if validation must be kept for some reason, I think the special case of using a date as part of a page name should be considered reasonable enough to be added as a special case.

To serve files with the correct MIME type, Go implements content-type sniffing, see https://pkg.go.dev/net/http#DetectContentType (click on the function name to see the implementation — the longest part are the various file signatures) — maybe such an approach would be available to silverbullet, too, making any sort of configuration unnecessary?
I don’t really understand what MIME types have to do with the restriction on page names, though? Can you explain the connection please?


Adding methods for accepting &mut [MaybeUninit<u8>]

I'm doing an audit of Tokio, and as part of it, we noticed in https://github.com/tokio-rs/tokio/issues/4685 there are a few places where tokio is casting a &mut [MaybeUninit<u8>] to a &mut [u8]. They then pass this slice to a variety of mio methods.
If I'm reading the unsafe guidelines correctly, this is undefined behavior, or at least considered potentially undefined behavior.
Would it be possible to add some methods that accept &mut [MaybeUninit<u8>] to mio? That would let us shrink down the audit scope to these methods to make sure that mio won't accidentally read from these bytes. It'd also give us a place to easily migrate the ecosystem once the standard library is able to take &mut [MaybeUninit<u8>], or std::io::ReadBuf once stabilized.

It's actually not UB, but it's unsound. Mio doesn't read the buffer nor does it write invalid (MaybeUninit::uninit) bytes to the buffers, so we don't trigger any UB. However we don't make the guarantee that we don't do that. I've changed socket2 to be based on MaybeUninit, see https://github.com/rust-lang/socket2/pull/161, so I'm open to a change, but that would be an API breaking change.

After doing a little digging, I found the Unsafe Code Guidelines WG thread about it in https://github.com/rust-lang/unsafe-code-guidelines/issues/71. If I'm reading @RalfJung correctly in https://github.com/nix-rust/nix/pull/1655#discussion_r799694351, it sounds like this pattern is UB, not just unsound. According to @djkoloski, it sounds like in order to make this non-UB, we'd need to use an LLVM intrinsic freeze to freeze the memory first, but Rust doesn't expose this yet.

UB and unsound is the same thing.

@Thomasdezeeuw would mio be interested in building on top of socket2, or would it make more sense to directly call the correct libc functions?
Also, while it might be cleaner to do a breaking change, we could avoid doing that if we add methods like TcpStream::peek_uninit(buf: &mut [MaybeUninit<u8>]) -> io::Result<u8>, or TcpStream::recv_uninit(buf: &mut [MaybeUninit<u8>]) -> io::Result<u8>, although that gets a little ugly.
We'd also have to do something to handle uninitialized IoVecs like https://docs.rs/socket2/latest/socket2/struct.MaybeUninitSlice.html. Would it be better to just directly build upon socket2, and expose socket2::MaybeUninitSlice as part of mio's public API?

UB and unsound is the same thing.

I'd say they are almost the same thing. ;) "unsound" is when using only safe code (but using libraries that internally might use unsafe code), I can use UB.
UB is a property of a program with a main function; unsound is a property of a library.

But coming to the issue at hand, indeed using [u8] for passing arbitrary data around (like even the stdlib does) is a technical debt we'll have to slowly work ourselves out of. On the stdlib side, the plan for that is ReadBuf. [MaybeUninit<u8>] also works but usually doesn't suffice to provide safe abstractions. (In particular, casting &mut [u8] to &mut [MaybeUninit<u8>] and exposing that to the outside world is unsound, since one could then assign MaybeUninit::uninit() to it, thereby de-initializing the buffer.

@Thomasdezeeuw would mio be interested in building on top of socket2, or would it make more sense to directly call the correct libc functions?

No we decided that Mio won't depend on Socket2, but most users of Mio actually use both.

Also, while it might be cleaner to do a breaking change, we could avoid doing that if we add methods like TcpStream::peek_uninit(buf: &mut [MaybeUninit<u8>]) -> io::Result<u8>, or TcpStream::recv_uninit(buf: &mut [MaybeUninit<u8>]) -> io::Result<u8>, although that gets a little ugly.
We'd also have to do something to handle uninitialized IoVecs like https://docs.rs/socket2/latest/socket2/struct.MaybeUninitSlice.html. Would it be better to just directly build upon socket2, and expose socket2::MaybeUninitSlice as part of mio's public API?

Yeah, I haven't solved in Socket2 either as it has the opposite problem: https://github.com/rust-lang/socket2/issues/223. Maybe ReadBuf can be used, but then the RFC really needs to get a move on because I was targetting a Mio v1 based on rustc 1.61.

In principle Tokio could use mio's try_io methods to make the libc call via socket2.

No that won't work on Windows. We need to go through try_io on Windows to ensure Mio state is correct, otherwise it can't guarantee events. See https://github.com/tokio-rs/mio/blob/c6f39d6ddba12b32793453dfe65a74104445f68d/src/sys/windows/mod.rs#L82-L97

However we did recently add the try_io method to most types we have, e.g. https://docs.rs/mio/0.8.3/mio/net/struct.TcpStream.html#method.try_io.

@Thomasdezeeuw i think they’re still iterating on the standard ReadBuf implementation. @nrc has a new variant in https://github.com/rust-lang/rust/pull/97015 that tries to fix the risk that someone could unexpectedly mem::swap a &mut [MaybeUninit<u8>] to trigger UB. Hopefully this design sticks.
@RalfJung thanks for jumping in again! Just to confirm, is the act of doing let y = &mut *(x as *mut MaybeUninit<u8> as *mut u8) itself unsound? Or is it just easy to trigger unsoundness with this pattern by writing uninitialized data into it? As far as I can tell tokio/Mio doesn’t appear to be writing uninitialized data into the vec.

"unsound" means "safe code can use this to cause UB", so that is definitely unsound. But I guess you are asking if that line of code causes UB.
Under a strict reading of https://doc.rust-lang.org/reference/behavior-considered-undefined.html, it does, because it creates an &mut i32 that points to an invalid (as in, uninit) i32. However, I personally think we should relax this a bit, and say that a &mut i32 can point to uninit memory as long as it is not being loaded from. That is also what Miri implements. That is https://doc.rust-lang.org/reference/behavior-considered-undefined.html.

I think we should close this in favour for an issue that follows the read-buf Rust feature (https://github.com/rust-lang/rust/issues/78485). We decide a while ago to follow API defined in std lib, so let's keep true to that.

We decide to follow the same as the std library, so closing this. Once the read buf (https://github.com/rust-lang/rust/issues/78485) becomes stable we can add support for that.


Add which and where flags

Closes #40

Thoughts on making where and which switches and re-use the Packages param? Looks good otherwise.

Meh. I don't like the idea of typing pwr -packages jdk -where since which/where is my use case is really only designed for single package usage, whereas -Packages is an array. Plus it's a lot more characters to type.

Thoughts on making where and which switches and re-use the Packages param? Looks good otherwise.

Meh. I don't like the idea of typing pwr -packages jdk -where since which/where is my use case is really only designed for single package usage, whereas -Packages is an array. Plus it's a lot more characters to type.

I'm thinking now it makes the most sense to have which and where be `commands on the packages.

I'm thinking now it makes the most sense to have which and where be commands on the packages. If you wanna assert the package length is 1, I'd be okay with that.
After thinking about this more I think changing it to be a command makes a lot more sense. I've added home, where, and which commands, since they all operate on packages (except for home).


Fix bug where machine pool dosen't work

The machine pool uses code that doesn't seem to work with the current version of the library. This should fix it so it is creating snapshots correctly.

Thanks for the PR. Shame we can't conditionally block anymore and now require a blind sleep.


feat: non event sourced aggregates persistence implementation.

Task linked: CU-86bvyp8f0 Aggregate separation to the event sourced and non event sourced types

Task linked: CU-86bvyp8kw Separation of aggregate classes, repositories etc.


Add asimov-ts

Why do you think the link is worth adding on this list?
It's a totally free and open source engine written in pure TypeScript. It can teach a lot about generics and engine development to people who are starting out in both the TS and gamedev spaces.
Does this project has any License?
MIT

My bad, fixed it!


errors in generation, TypeError: gelu()

When I run the following code, it came to the error
"y = model(x)
return torch._C._nn.gelu(input, approximate)
TypeError: gelu(): argument 'approximate' (position 2) must be bool, not str"
from transformers import AutoTokenizer
from transformers import AutoModelForCausalLM

tokenizer = AutoTokenizer.from_pretrained('replit/replit-code-v1-3b', trust_remote_code=True)

model = AutoModelForCausalLM.from_pretrained('replit/replit-code-v1-3b', trust_remote_code=True)
model.to(device='cuda:1')

x = torch.tensor([[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]])
x = x.to(device='cuda:1')
y = model(x)
print(y)

It looks like you might have an issue in your own environment configuration (as in, your pytorch installation might be corrupted).
Here's our recommendation:

upgrade torch to the latest version
upgrade transformers to the latest version
run the new codebase which we recently pushed to this repo

Let us know if that helps!

It looks like you might have an issue in your own environment configuration (as in, your pytorch installation might be corrupted). Here's our recommendation:

upgrade torch to the latest version
upgrade transformers to the latest version
run the new codebase which we recently pushed to this repo

Let us know if that helps!

It works for me to upgrade torch


add bigint detection and sets mssql req.input when appropriate

#1442

Implementation looks correct, but this really would need test case too.

@elhigu I somewhat failing at writing units test for that cas and I can't find one testing similar issue. I tried to mock the connection but it is still trying to connect to a real database :( ). I you can give me a hint :)

I have no I idea if mocking the client is even possible, do you have mssql installed so that you could just write integration test for it?

@elhigu ok just pushed them. I have a questions :). Why bail option is activated by default on test script (this bugged me a while)?  And I see 24 tests failing for mssql, they don't appear to be any related to my changes so I guess mssql support is still a WIP?

It is really hard to keep track how mssql / oracle are working since I have never ran mssql tests myself... Probably at some point all tests were passing and I suppose they are broken again. You should try running tests before applying your changes to check if errors are caused by your changes...
I just few hours ago sent email to microsoft people if they could provide me preview of their upcoming mssql for linux version and if there is any possibility to set it up for knex CI... not having high hopes for that though :) maybe some day.
Test bailing is on at least because of integration tests are stateful so if one test fails, it is possible that all the tests will fail after that since DB is not in correct state. Though I don't know what has been real motivation for that.

@sandorfr could you still confirm that other test failures were not caused by this change and maybe add an issue with errors of failing tests if mssql is currently broken?

Just tested, the errors are on master branch, I think some of them are just outdated tests. I'll open an issue for that.
Regarding mssql tests a basic azure instance is just 5 euros per month so I can provide you an access to one until Microsoft releases mssql for linux (or invites you to join the beta).

@sandorfr thanks for the offer I'll discuss about using azure mssql instance for CI with other collaborators 👍

@sandorfr now that I was thinking how to use external DB from travis CI so that there can be multiple tester instances running against the same DB at the same time, would require some extra coding to implement. If someone is able to make it work I would accept pullrequest for that though :)

@elhigu Yes concurrency is definitely non trivial. I think one approach would be to use a different schemas for each build (and drop the schema and its objects at the end of the test run). But I think the current implementation for mssql does not support schemas and assumes it is dbo (see https://github.com/tgriesser/knex/blob/master/src/dialects/mssql/query/compiler.js#L163 for instance). So the first step would be to enable schema support for mssql.


Create mac address

Addresses #23 providing a new MacAddress object and appropriate documentation.
The use of ISerializable neccissitated the reliance and addition of the System.Runtime.Serialization.Formatters package. The impact of this inclusion should be negligible.

Attached is the new set of built docs. The pertinent pages are the Index, the Mac Address page, and the Acknowledgment page.
docs.zip


Increase token byte rate to 32 or 64

The token generation was changed to fix #101. It uses a 16 byte random token. For security reasons, it would be nice to further increase this to 32 or 64 bytes. However, this also requires some UI tinkering as the increasing length does not fit on the screen :)

Suggestion: the token could be generated from the full alphabet, not only [0-f] digits. The security would be stronger, and tokens not so huuuge for UI.


chore(ci): upload artifacts

Helps with being able to test in vm's and such without having to compile locally for each.

Woah! This is so nice 👏🏼

Will need to run it later, windows seems to be complaining about running yarn install

They passed as I did a typo which bugged the pipelines.
Ill merge once I'm happy its uploading as expected and show you guys the outputs.


Create new element to insert custom strings when generating XMLs

Add a new element whose sole purpose is to insert custom strings when generating XMLs. This new element could be called StringElement.

You can create such element by just deriving from svgdom::Element. What needs to be done is to expose the StringWriter visitor class, so that it is also possible to extend it.

@JaimeIvanCervantes what is you exact problem, i.e. what do you want to achieve here? Is it writing the SVG which contains custom elements to string?

I just submitted a PR with my solution: https://github.com/igagis/svgdom/pull/10
What I want to do is very simple, I just want to insert any text to the XML string. I need this to insert code for custom elements that are not found in the SVG spec. I created an Element  called CustomStringElement (in files Custom.hpp and Custom.cpp). Here's an example:
auto dom = utki::makeUnique<svgdom::SvgElement>();
svgdom::PathElement path;

svgdom::PathElement::Step step;
step.type = svgdom::PathElement::Step::Type_e::MOVE_ABS;
step.x = 0;
step.y = 0;
path.path.push_back(step);

step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
step.x = 0;
step.y = 300;
path.path.push_back(step);

step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
step.x = 300;
step.y = 300;
path.path.push_back(step);

step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
step.x = 300;
step.y = 0;
path.path.push_back(step);

dom->children.push_back(utki::makeUnique<svgdom::PathElement>(path));

svgdom::CustomStringElement custom;
custom.setCustomString("Any string goes here.");

dom->children.push_back(utki::makeUnique<svgdom::CustomStringElement>(custom));

cout<<dom->toString()<<std::endl;

The line custom.setCustomString("Any string goes here.") inserts a string in the XML. Here's the output:
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1">
	<path d="M0,0L0,300 300,300 300,0"/>
	Any string goes here.
</svg>

I wrote this out of pure necessity, and I tried to use your code conventions, but feel free to add or rename anything you want.

I made changes to support custom elements. I refactored the StreamWriter so that it now allows writing of custom elements and adding even custom attributes to standard elements.
I added a test cases which demonstrates how to achieve that: https://github.com/igagis/svgdom/blob/master/tests/customElement/main.cpp
The svgdom version 0.2.61 should be available within an hour. Please check if it suits your needs.

I updated the https://github.com/igagis/svgdom/blob/master/tests/customElement/main.cpp test a bit.

Unfortunately my project requires me to insert strings that are not necessarily svg elements or attributes. I know that this might not be a usual case, so I decided to use the following code to create my custom element:
struct CustomElement : public svgdom::Element{
	std::string str;

	CustomElement(std::string s) : str(s) {}

	void accept(svgdom::Visitor& visitor) const override;
};

class CustomStreamWriter : public svgdom::StreamWriter{
public:
	CustomStreamWriter(std::ostream& s) :
			svgdom::StreamWriter(s)
	{}

	using svgdom::StreamWriter::visit;

	virtual void visit(const CustomElement& e){
		auto ind = indentStr();
		this->s << ind;
		this->s << e.str;
		this->s << std::endl;
	}
};

void CustomElement::accept(svgdom::Visitor& visitor) const{
	if(auto v = dynamic_cast<CustomStreamWriter*>(&visitor)){
		v->visit(*this);
	}else{
		visitor.defaultVisit(*this);
	}
}

int main(int argc, char** argv) {
	auto dom = utki::makeUnique<svgdom::SvgElement>();

	svgdom::PathElement path;

	svgdom::PathElement::Step step;
	step.type = svgdom::PathElement::Step::Type_e::MOVE_ABS;
	step.x = 0;
	step.y = 0;
	path.path.push_back(step);

	step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
	step.x = 0;
	step.y = 300;
	path.path.push_back(step);

	step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
	step.x = 300;
	step.y = 300;
	path.path.push_back(step);

	step.type = svgdom::PathElement::Step::Type_e::LINE_ABS;
	step.x = 300;
	step.y = 0;
	path.path.push_back(step);

	dom->children.push_back(utki::makeUnique<svgdom::PathElement>(path));

	dom->children.push_back(utki::makeUnique<CustomElement>("Any string goes here."));

	std::stringstream ss;
	CustomStreamWriter writer(ss);
	dom->accept(writer);
	auto str = ss.str();
	cout<<str<<endl;
}

This will produce the following output:
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1">
	<path d="M0,0 L0,300 300,300 300,0"/>
	Any string goes here.
</svg>

In order for my custom element to work though, I would need to merge the following PR where I am only moving s, indentStr(), and indent members from private to protected: https://github.com/igagis/svgdom/pull/11
This is really important for my project :).

The PR seems OK, but I asked you to add a comment there. Please also check the updated test  https://github.com/igagis/svgdom/blob/master/tests/customElement/main.cpp and update your  code accordingly, because it is not very good to cast to CustomStreamWriter in the accept method.

PR merged


Corrections to LuciBase and LuciSNR

Added small corrections to LuciBase and LuciSNR to smooth function usage, especially regarding the WVT procedure.

It looks like the code in LuciBase is now in duplicate... Could you please verify this... @benjaminvigneron

Should be okay now !


User-defined type guards seemingly unused when given an intersection type

TypeScript Version:  1.8.10
Code
interface Foo {
    x: number;
    s: string;
}

interface Bar {
    y: number;
    z: number;
}

interface HasNum {
    a: number;
}

type FooOrBar = Foo | Bar;

type FooOrBarWithNum = FooOrBar & HasNum;

function is_foo(f: FooOrBar): f is Foo {
    return (f as Foo).x !== undefined;
}

let obj: FooOrBarWithNum = {
    a: 5,
    x: 5,
    s: "hello"
};

if (is_foo(obj)) {
    obj.x; // ERROR: Property 'x' does not exist on type (Foo | Bar) & HasNum
}

let obj_2: FooOrBar = obj; // Cast it back to just a FooOrBar.

if (is_foo(obj_2)) {
    obj_2.x; // This compiles just fine.
}

Expected behavior:
I would expect obj to have type Foo inside of the if-block.
Actual behavior:
obj is not refined, but obj_2 is.

This looks related to or a duplicate of #9919

This works now. Fixed by #11717.


[Artificial Intelligence] Reactive Machine for Artificial Intelligence

Reactive Machine for Artificial Intelligence
Reactive Machines: They perceive and react to the information stored in them. They respond to the same situations in exact and precise forms, all the time. They are no disparity; they do not conceive nor perceive the future. They also do not work with past information.
An easy-to-remember example of reactive AI is; the spam filter (in mails). Also, Netflix recommendations.
Key Takeaways
· What Reactive Machines AI is and what they do.
· Real-life examples of Reactive Machine
. Explanation of Artificial Intelligence
· Types of AI systems
· The usefulness of Reactive Machines in the world.
Topic Suggestion
Proposal Submission
Proposed title of article
Your title should be descriptive of the article/tutorial. Be Specific.
Use keyword research to improve your article's SEO.
Proposed article introduction
We're looking for the first 2-3 paragraphs of your article that appropriately summarize what your article will be about.
We will use this writing snippet to help us assess the overall quality before approval so ensure it has been proofread, spellchecked and grammarchecked.
For example, if the article is based on machine learning, use the following: [Machine learning] Introduction to Machine Learning.
If the article is based on developing an Android application, use the following: [Android] Developing Apps using Android.
ONLY viable topics to pick from:

API
Artificial Intelligence
Blockchain
Containers
Edge Computing
Languages
Machine Learning
Networking
Node.js
Security

Key takeaways
What are the 3-5 most important things the reader should understand or be able to do after reading this article?
Use this area to get your ideas down on the bulk of your article or tutorial.
Article quality
How is your article unique? Tell us what makes your approach different from similar articles that have published on the same topic?
Is yours more in-depth? Does it cover additional topics? Do you provide handy tips or anecdotal advice?
References
Please list links to any published content/research that you intend to use to support/guide this article.
Conclusion
Finally, remove the Pre-Submission advice section and all our blockquoted notes as you fill in the form before you submit.
We look forwarding to reviewing your topic suggestion.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Please fill in the topic suggestion form that I've readded to your issue so we can adaquately review your topic suggestion.

@louisefindlay23  I have edited it.

@kwennB, you don't seem to have filled in the article quality section?

@louisefindlay23I I will see to it now.

Hi @kwennB, interesting topic of choice. This is definitely an article I'd love to read.
However:

Consider editing your topic submission to remove the template that Section provides such that only your submission under each heading remains.

In the article quality section, you have outlined your approach to the article as more of a "why", but not the "how" that makes your angle unique; compared to other content that for instance, talks about the types of AI, or how AI (or a subset of AI) eases or threatens our everyday lives.

Make these adjustments then ping us to complete the review.

@collins-a Thank you. I have made the adjustments.

@kwennB unless covering an angle that hasn't been taken by an author on Section, perhaps replace the explanation of AI and types of AI sections with an in-depth technical section on how reactive machines work.
Now that's an article I'd love to read.

Alright @collins-a
I will update the issue and ping you when it's done.

Per the above chats, this issue appears to be saturated. We focus more on unique projects. Feel free to suggest another issue. Thanks


Support to specify path to retype.json via input argument

It should be possible to point to a retype.json file anywhere within the repository and current branch.

We decided to add a single input to pass the path/config to the file, like:
- using: retypeapp/action-build@v1
  with:
    config: docs/retype.json

It should also support pointing to the directory, where retype would look for an existing retype.json file or assume defaults if none specified.
- using: retypeapp/action-build@v1
  with:
    config: docs

It should also support pointing to the directory,

This config value should just be passed directly to the retype build <config> command. Given your statement above, is building specific logic into action required?

Specific logic is added just for some initial validation of the input; whether the path is valid/exists, basically. Benefit would be, clearly the action failed due to a wrong input value; so less digging thru runtime error messages.

This is now in effect at @v1, @v1.5 and @v1.5.0 tags.


No longer use gemcutter. Update to rubygems.org

You also need to update the tests: https://travis-ci.org/bundler/bundler/jobs/50557995#L2108

also, the :gemcutter symbol maps to rubygems.org already.

Unfortunately, :gemcutter maps to http://rubygems.org and not https (and gives a deprecation warning).
I think we should make this change and fix the tests.

:+1:

On Feb 13, 2015, at 10:06 AM, Tim Moore<EMAIL_ADDRESS>wrote:
Unfortunately, :gemcutter maps to http://rubygems.org and not https (and gives a deprecation warning).
I think we should make this change and fix the tests.
—
Reply to this email directly or view it on GitHub https://github.com/bundler/bundler/pull/3394#issuecomment-74184050.

er... it isn't obvious from how GitHub formats this, but I fixed the test in the merge commit


isMobilePhone true on empty string

Behavior: string with 11 spaces returns true as valid phone number
Expected: Returns false
Fix: validation isMobilePhone runs .trim() on string before checking
EDIT
Additional details: I used the locale 'any'

In theory it thinks it is correct based on length, but some additional validation through a simple regex should be applied.
I will get this cured correctly for next update
Thanks for report 😁

@mikeerickson Forgot a potentially important detail. Added it to the original post.


Experiment with tweaking Rust install

Currently it's downloading Rust from rustup.rs, but I think that's not necessary as there's already a Rust installed. This patch changes it to assume there's already a rustup to set the default toolchain.

This doesn't seem productive to me, closing.


make subscription methods more consistent with __contains__

message["tool_calls"] will now raise an exception if it's not set to be consistent with the old map behavior and the __contains__ operation updated in 0.4.1

Ran examples as well - looks good!


Writing a Flutter Web Plugin

Proposed title of article
Writing a Flutter Web Plugin
Introduction paragraph (2-3 paragraphs):
Flutter is a wrapper for native code such as Android and iOS .
The url launcher plugin now has web functionality, as demonstrated in this post. You should be familiar with plugin development and the ideas discussed in Developing plugin packages before reading this article.
Key takeaways:
-How to add web support to a Flutter plugin.
-How to refactor your plugin.
-How to register the plugin.
References:
N/A

@FaithZawadi
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

@FaithZawadi - Please provide more details on your topic.

@Kayere ,
I have added some details.
You may have a look.
Thank you.


Carrier Sense Implementation

Check if the adaptor is idle before sending with a probability 1 (1 - persistent) whenever the adaptor is idle (adaptor is a variable in class host).

Done in 2cca3ab31c89051cf66633ad3e8d3cc43d0c612b


Switch shuffler to assumed fill

Closes #119

@lunarsoap5 @NoobTenLuka @Redriel57 anyone able to give this a look over? I think I got it right, I pretty much just implemented the assumed-fill pseudo-code from https://digitalcommons.lsu.edu/cgi/viewcontent.cgi?article=6325&context=gradschool_theses, with some slight adjustments due to the way we differentiate between logic and aux data.

Approving as it works for now. As I mentioned in the discord, there are some edge cases we will need to account for later, but nothing that impedes the implementation of this PR.


Class AMSupportURLConnectionDelegate is implemented in both ??

What version of Go are you using (go version)?

$ go version
go version devel +bc7e4d9257 Mon Dec 21 21:48:47 2020 +0000 darwin/arm64

Does this issue reproduce with the latest release?
Yes. Just did git pull.
What operating system and processor architecture are you using (go env)?
go env Output
$ uname -a
Darwin M1 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec  2 20:40:21 PST 2020; root:xnu-7195.60.75~1/RELEASE_ARM64_T8101 arm64
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/adam/Library/Caches/go-build"
GOENV="/Users/adam/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/adam/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/adam/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="devel +bc7e4d9257 Mon Dec 21 21:48:47 2020 +0000"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/0d/lxlj8q611gv3myfyq2dq6l6c0000gn/T/go-build8557189=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

$ sudo codesign -s - /opt/go/bin/*

What did you expect to see?
No errors about AMSupportURLConnectionDelegate and AMSupportURLSession.
What did you see instead?
$ sudo codesign -s - /opt/go/bin/*
objc[49507]: Class AMSupportURLConnectionDelegate is implemented in both ?? (0x1f721f8f0) and ?? (0x113fa02b8). One of the two will be used. Which one is undefined.
objc[49507]: Class AMSupportURLSession is implemented in both ?? (0x1f721f940) and ?? (0x113fa0308). One of the two will be used. Which one is undefined.

It isn't clear to me what you are actually trying to do. Is this problem related to Go? Are you trying to sign binaries produced by the Go compiler?

I don't think this has anything to do with Go. I've seen this message when running non-Go commands like cc or git. (The message doesn't stop the command from succeeding, though.)

 If this is unrelated to
Go, and has more to do with Xcode, please close it. Thank you!
On Tue, Dec 22, 2020 at 7:55 AM Matt Layher<EMAIL_ADDRESS>wrote:

It isn't clear to me what you are actually trying to do. Is this problem
related to Go? Are you trying to sign binaries produced by the Go compiler?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/43318#issuecomment-749526409, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANGWNDI3AVQUKNLCKKN4M3SWCJMNANCNFSM4VFOWXOQ
.


TL Localization Updates

Hi @severinolorillajr, there is one conflict need to be resolved before I can merge.

@Celia18305 , updated the conflict. Thanks.


Renamed MLLifeCycleManager to MLOpsContext

Resolves
Fixes #59
Description
Renamed MLLifecycleManager to MLOpsContext

This is ready for a review

LGTM


(RE-5087) Fix init script behavior on sles/suse when run by puppet

On suse/sles 10, when executed by puppet, the init script will not start the puppet
service because startproc checks and finds a puppet process running.
This updates the init script to force start the process unless there is
a running process matching the pid in the pidfile. It also updates the status
command to only return true if the pidfile matches a running puppet pid.
This is a direct port of a fix for SLES 10 from previous PE releases.

:+1:

CLA signed by all contributors.

Tested on sles 10, seems to do the right thing:
Debug: Executing: '/sbin/service puppet status'
Debug: Executing: '/sbin/service puppet start'
Notice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running'
Info: /Service[puppet]: Unscheduling refresh on Service[puppet]
Debug: Finishing transaction 70845210
Debug: Storing state
Debug: Stored state in 2.58 seconds
Debug: Executing: '/sbin/service puppet status'
service { 'puppet':
  ensure => 'running',
}


[Question] May I distribute this with mods I create?

Hey! I was just wondering if I could distribute this server with my mod (Dark Souls III Coop Overhaul) so it is easier for the users of my mod to setup the mod and get ingame faster?

By all means, go for it.
This project is MIT licensed, you can do pretty much whatever you wish with it.

All right! Thank you so much! Closing issue now!


Add a bridge from AllDifferentExceptConstant to MILP

FlatZinc has two implementations: one based on a variant of GCC, another on conjunctions of disjunctions (either the constant to ignore or difference).
https://github.com/MiniZinc/libminizinc/blob/master/share/minizinc/std/fzn_alldifferent_except.mzn

Solved with 82e5edd9e3ca0d5ad391fddcec0a859435b3b01e and d784441bd6800b7d7f1345f77de920e0eb94019e.


Update Compound.finance on Optimism

Hey.
The purpose of this PR is to verify that 0x2501713A67a3dEdde090E42759088A7eF37D4EAb address was a deployer of 0x7e7d4467112689329f7E06571eD0E8CbAd4910eE using Optimism Bridge.
In the optimistic scan, we see that our address 0x2501713A67a3dEdde090E42759088A7eF37D4EAb has deployed COMP token https://optimistic.etherscan.io/address/0x7e7d4467112689329f7E06571eD0E8CbAd4910eE#internaltx, however, we deployed it via this contract - https://optimistic.etherscan.io/address/0x4200000000000000000000000000000000000012

@ccerv1 please, review. Thanks

/validate 1c8e949a15d15099213b7b9fd8ef0d458ba16596

@dmitriy-woof-software thanks for this! Your PR looks good. We have a bug that we are working where our validator may fail if there's an error in another project file. Anyway, no action on your end. We'll merge as soon as we can. Thank you againm!


Implement build pipeline

Implement build pipeline

Thanks for your work on https://github.com/ameyer505/D365FOAdminToolkit/pull/28
I did a bit of snooping on your profile and discovered this lovely repo. Happy to help with this issue, already created pr #23 for it. It's basically the same build action that the D365FOAdminToolkit has. It is based on the nice work of FSC-PS for GitHub and the simple template I created for it.

Thanks @FH-Inway!


Can't add controls to dock panel

I can't add controls to the dock panel making it useless

You are supposed to create dock contents (a type of child forms) and add controls to them. Dock panels are simply logic containers, so it never supports drag controls into itself,
http://docs.dockpanelsuite.com/getting-started/installing-on-windows.html

@lextm wait so this has no design time features?

Commercial docking libraries might have their design time support, but this project does not.

@lextm your link is broken

The doc site was down for a few hours. Now it is back.


Deployment Request on WEMIX3.0

Chain Name
WEMIX3.0 Mainnet
Chain ID
1111
RPC URL
https://api.wemix.com
Block Explorer URL
https://wemixscan.com (please set the gas price to 101Gwei)
Deployment Funds
Yes
Or please give me the signed tx with 101Gwei gasprice

Do I need to use 101 gwei for the base fee or the priority fee, or both? When I tried sending a transaction with the defaults I received a JSON RPC error

Thank you for your trying. You should set 1wei+ for the base fee and 100 Gwei for the priority fee. So you can set 101 Gwei for the gas price.

Hi, did you try it? If you have a problem with those gas configuration, please let me know that.

Done, thanks!


java.lang.NoClassDefFoundError: Failed resolution of: Lcom/facebook/drawee/backends/pipeline/info/ImagePerfDataListener;

Description
Once my app is installed in the device i try opening it but it crashes. Used to work but recently i did a npm install, npm upgrade, npm update and installed the lastest react native version 0.73.0.
Already tried to reset cache and gradlew clean but didnt work.
Steps to reproduce
(Dont know how to reproduce, maybe by creating a project in react native 0.72.4 and trying to upgrade it)
React Native Version
0.73.0
Affected Platforms
Runtime - Android
Output of npx react-native info
info Fetching system and libraries information...
System:
  OS: Windows 10 10.0.19045
  CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
  Memory: 1.86 GB / 7.93 GB
Binaries:
  Node:
    version: 18.17.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 9.6.7
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "33"
      - "34"
    Build Tools:
      - 30.0.3
      - 33.0.0
      - 33.0.1
      - 34.0.0
    System Images:
      - android-30 | Google Play Intel x86 Atom
      - android-34 | Google APIs Intel x86_64 Atom
      - android-34 | Google Play Intel x86_64 Atom
    Android NDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-223.8836.35.2231.10406996
  Visual Studio:
    - 17.8.34322.80 (Visual Studio Community 2022)
Languages:
  Java: <IP_ADDRESS>
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: ^18.2.0
  react-native:
    installed: 0.73.0
    wanted: ^0.73.0
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs
java.lang.NoClassDefFoundError: Failed resolution of: Lcom/facebook/drawee/backends/pipeline/info/ImagePerfDataListener;
 at com.gestorum.ReactNativeFlipper.initializeFlipper(ReactNativeFlipper.java:33)
 at com.gestorum.MainApplication.onCreate(MainApplication.java:60)
 at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1190)
 at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6582)
 at android.app.ActivityThread.access$1400(ActivityThread.java:224)
 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1887)
 at android.os.Handler.dispatchMessage(Handler.java:107)
 at android.os.Looper.loop(Looper.java:224)
 at android.app.ActivityThread.main(ActivityThread.java:7562)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.facebook.drawee.backends.pipeline.info.ImagePerfDataListener" on path: DexPathList[[zip file "/data/app/com.gestorum-SB2v2uWfMrjH0B3TmmtzKg==/base.apk"],nativeLibraryDirectories=[/data/app/com.gestorum-SB2v2uWfMrjH0B3TmmtzKg==/lib/arm64, /data/app/com.gestorum-SB2v2uWfMrjH0B3TmmtzKg==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]
 at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:230)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
 ... 12 more

Reproducer
.
Screenshots and Videos
No response

Hello, have you found a solution?

Hello, have you found a solution?

Kinda, but youll need to create a new project and copy and paste all files, classes and configuration and install packages again 😅. This worked for me but you might need to check what packages versions youve want because if you didnt upgraded them until now might cause some issues.

Problem
It looks like the ImagePerfDataListener has been moved.
facebook/fresco@ac00658: Move ImagePerfState and ImagePerfData to ui-common target:
- import com.facebook.drawee.backends.pipeline.info.ImagePerfDataListener;
+ import com.facebook.fresco.ui.common.ImagePerfDataListener;

The above change was merged into<EMAIL_ADDRESS>and RN v0.73 bumped Fresco to this version in commit 823839bc.
I suspect that some necessary change was not made, hence the problem for upgrading users.
Solution/workaround
At the same time, ReactNativeFlipper.kt:14 mentions:
/**
 * Stub class that does nothing to ease the migration out of Flipper. Users should stop calling
 * `ReactNativeFlipper.initializeFlipper` in their `MainApplication.java` as this class will be
 * removed in React Native 0.75 or future versions.
 */

And indeed, if the ReactNativeFlipper.initializeFlipper() line in MainApplication.java is commented-out, the issue is resolved. 🎉
Alternatively, it's possible to keep Flipper without having to create a new project and transferring everything manually. One way to do this would be to check the changes from 0.72.7 to 0.73.1 using the upgrade helper, and manually merge the relevant parts, although this would be a very manual process.
Godspeed.

java.lang.NoClassDefFoundError: Failed resolution of: Lcom/facebook/drawee/backends/pipeline/info/ImagePerfDataListener;
at com.gestorum.ReactNativeFlipper.initializeFlipper(ReactNativeFlipper.java:33)

The issue is caused by your update which is not done correctly.
Specifically once you update to React Native 0.73, you should remove your local ReactNativeFlipper file (which you still have as the package is com.gestorum. in the stacktrace).
See https://react-native-community.github.io/upgrade-helper/?from=0.72.8&to=0.73.1:

Please make sure you follow the upgrade helper correctly

That worked like a charm, thx @cortinico

Thanks @cortinico and @parlet for the solutions!!!! Works perfectly!

The issue still persist even after using the upgrade helper

How do I use flipper in react native if I remove it? I am on RN 0.75.3.
Thanks


Adding a glossary of commonly used terms

The terms herein will be used in future documents that make progress toward completing https://github.com/kubernetes-incubator/service-catalog/issues/14
This patch partially replaces #13
cc/ @pmorie @bgrant0607 @duglin @judkowitz @slack @MHBauer
TODO:

[x] Rework this into the README.md

I'm good with this, if @krancour's comment is addressed.

agree with @krancour's comments.
Should this be in the README or in the API docs?   I was reviewing https://github.com/kubernetes-incubator/service-catalog/pull/18/files and it defines some terms in there too.  Seems like we should merge them.

@pmorie, @arschles gave me write access to his fork while he's abroad. I've amended the PR to address the outdated diff we'd previously discussed. This is ready for re-review.

I think more CLAs are needed.

@arschles and I should both be all set CLA-wise. Not sure what's going on here.

@krancour I know Google's CLAbot didn't work on PRs with commits from multiple authors. Perhaps this is also the case with the LF CLAbot.

RE @krancour's earlier comment - I am also registered under the deis org's LF CLA, and all of my PRs have failed the CLA bot.
I'm guessing it's because the LF account page can't connect my GH account

geez I wish we would just use DCOs  :-)

Superseded by #25. Closing


Correctly passes localNotification to app on wakeup

Currently if an RN app is started in response to a remote notification, that notification's data is available on startup via PushNotificationIOS.popInitialNotification(). However, if the app is started in response to a "local" notification, that information is never passed in. This PR modifies the popInitialNotification behavior so it will return the notification used to launch the app, no matter if it was local or remote.
Test Plan
I've tested this change in my app and ensured that when the app is woken up with a localNotification it's passed in to PushNotificationIOS.popInitialNotification. I've also tested that the localNotification event continues working as before.

@corbt updated the pull request.

@javache ok, nits fixed.

@corbt I think this must be based on an old version of RCTPushNotificationManager, because I added a
RCT_EXPORT_METHOD(getInitialNotification:(RCTPromiseResolveBlock)resolve
                                           reject:(__unused RCTPromiseRejectBlock)reject)

Last week, with a view to eventually removing the constantsToExport. Since your change will affect that method too, can you make sure you rebase and resubmit?

@corbt updated the pull request.

@corbt updated the pull request.

@nicklockwood fixed! There's some duplicated logic between constantsToExport and getInitialNotification but since constantsToExport is deprecated anyway I figured it's better that way (so it can be removed cleanly).

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Forward warping

Dear author
Thank you for your great work. And I am trying to incorporate your work into my pipeline. I found a problem that you use forward  warping to get the new RGB information and the new depth. But according to my understanding, forward warping will create holes and loss accuracy. Please point it out if I am wrong. If you stick to the plan I mentioned, how do you solve the problem related with forward warping? Thank you so much!

Yes, there will be holes. We didn't do interpolation or inpainting and only supervised the available pixels that are non zero

Thank you for your response. Considering your application, you did not change a lot between the direction of the reference and warping view, so I don't think holes will be a big problem. However, if I want to generalize it to big direction change, the holes will be a big problem. And I don't think interpolation can can solve it. Could you please give me some suggestions?

The biggest one is 90 degree

I appreciate your sharing of the great work. I have a question. I have been trying to reproduce your work. On the LLFF dataset, however, I can't obtain a reliable warping image by using the depth maps you provided on this website. The warping error seems critical when comparing the warped and target images. Is there an additional process such as depth scaling? If so, please let me know.


Mazumder - Fixing fav_icon for data.argosdb.org

The fav_icon still shows GlyGen's on the tab:

Please fix this asap

@rykahsay it is still appearing in the tab.

For me, I found that the GlyGen fav icon appears in Safari browser. But on chrome, firefox, and microsoft edge it's the argos icon

Interesting, I see it still in Chrome

I see it is fixed. Will close this ticket


[Fix] TModal - normalizedWidth & Height

This PR is related to #39 .
Scope of work
Remove negation from normalizedWidth and Height.
Description
Number.isNaN will tested value and return true if the value is number.
So, I have removed negation to supported string value case.

@figurluk Thank you for your comment 😁
I have updated by convert to isNaN as global, instead of Number.isNaN.
Because global isNaN will parse the value to number before tested.
So, 100 and "100" will be true in condition.
Ref: https://www.w3schools.com/JSREF/jsref_isnan_number.asp?fbclid=IwAR2iG31EWzEXHzTqd4JvnxgExUGN9uZExVuOJMQvDlWBxRPFSBgeLdXKmNY#:~:text=The Number.,Otherwise it returns false

@figurluk @runyasak  thank you both neede to create a new branch since master now is v1 but already buy fixed it using your ideas, just upgrade to 0.4.7


Allow testing for exported resources

Fixes #113
I wasn't entirely sure where the support class which patches Puppet's internals should go, as there didn't seem to be an existing place that did anything similar, so I added a new file under rspec-puppet/support for this. I also tried to defend against puppet changing this class in the future by adding a couple of guards, and I changed the original code from the gist to make it more obvious that catalogue.__rspec_puppet_exported_resources is intended to be something internal to rspec-puppet and not something to rely on.
Let me know if it needs tidying up.
I've added tests for 2 matchers (contain_X and have_X_resource_count). I found that the standard have_resource_count matcher didn't work with this implementation, as it blindly subtracts 1 from the count (it assumes Stage[main] is always in the catalogue it's testing) -- I didn't want to change the matcher as part of this PR, as it didn't seem like something people would normally want to do with exported resources and I'm not sure if the @actual_number = @actual_number - 1 line can safely be changed without breaking people's tests.

Looks great. If you could squash all the commits into one, that would make the git history so much nicer.

Squashed the commits for making it work with ruby 1.8 / rspec 2.

Actually I think changing https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/adapters.rb#L70 by:
Puppet::Parser::Compiler.compile(node)

Should be sufficient, you don't need to monkey patch the indirector. Just don't call the indirector.
This will give you a catalog with resources like:
{
  "type": "File",
  "title": "PATH",
  "tags": [
  ],
  "file": "config.pp",
  "line": 20,
  "exported": true,
  "parameters": {
    "ensure": "present",
    "content": "BLAH",
    "mode": "0644",
    "owner": "root",
    "group": "root"
  }
}

See #371
Diff: https://github.com/nhinds/rspec-puppet/compare/test-exported-resources...baloo:exported

I like it, looks much cleaner...
Unfortunately that has the downside of changing the existing catalogue that tests are written against to include exported resources (e.g. even without calling exported_resources, exported resources would match the contains_X matcher). That could possibly be fixed by adding catalog.filter { |r| r.virtual? } (which used to be called by Puppet::Resource::Catalog::Compiler.filter) somewhere in rspec-puppet...
I'm also not sure what other changes in functionality there will be due to skipping all the code in Puppet::Resource::Catalog::Compiler.find / Puppet::Indirector::Indirection.find, and whether this makes this more or less likely to cause problems due to future changes in puppet.
Maybe instead of changing the regular RSpec::Puppet::Adapters::Base.catalog(node) method, leave it calling the indirector and have a new method there for getting the exported resources which uses Puppet::Parser::Compiler.compile(node)? That way if something changes, it's only tests for exported resources which break, rather than all tests.

@baloo I've incorporated your change into this PR, and added a test to ensure that exported resources aren't exposed to the regular catalog.
I've tweaked it so that the indirector is called for normal catalog retrieval, and your method (calling the compiler directly) is used for exported resources, where we need to override the filter.

:heart: great stuff. I'll see to it that I squeeze in time to run a few more tests on this to get this merged.

@nhinds awesome, then I'm closing #371

@DavidS is there anything I can do to help get this merged?


Hibernate mode cannot create popups

The hibernate mode loop's roll_for_initiative() calls don't send the corruption chance, and all hibernation modes fail when they attempt to create a popup.
This is separate from #55. Hibernation mode is cursed.

Same issue here on linux. no errors when ran in console, but the log says
WARNING:failed to successfully run Glitch hibernate.     Reason: roll_for_initiative() missing 1 required positional argument: 'corr_chance'

This should be fixed by #59, I was waiting for @araten10 to merge it but I suppose I can do that now.


Waybill printout

A station owner should be able to print waybills for the stations customers cargo flow. There will be the following options when selecting what to print:

Select meeting layout: waybills can only be created for specific meeting layouts. The module station must be registered for the meeting layout and must belong to a country.
Select Receiving cargo: waybills are created for for receive or import cargo.
Select Sending cargo: waybills are created for send or export cargo.
Select Match shadow yard: waybills are created for all cargo to and/or from shadow yards. This option guarantees that waybills will be created for all cargo flows.

Implemented in release 1.4.1.


🎨  😎  config env usages

refs #7488

remove all ugly env checks
rather use config properties
replace process.env.NODE_ENV by config.get('env')

TODO

[ ] discuss naming for new config properties

Want to add this slack message as reference: https://ghost.slack.com/archives/help/p1486009008003835

The changes in this PR are awesome. We will review the individual naming of the config items separately 👍


Separate nightly as ci-nightly.yml

Codecov Report

Merging #37 (111547d) into master (144e081) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   87.50%   87.50%
=======================================
  Files           1        1
  Lines         184      184
=======================================
  Hits          161      161
  Misses         23       23

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 144e081...111547d. Read the comment docs.


Ingress with CNAME and TXT registry

When using a TXT registry and creating CNAMES on AWS.  I get the following error.
{"level":"info","msg":"Changing records: CREATE {\n  Action: \"CREATE\",\n  ResourceRecordSet: {\n    Name: \"domain.name\",\n    ResourceRecords: [{\n        Value: \"target.domain\"\n      }],\n    TTL: 300,\n    Type: \"CNAME\"\n  }\n} ...","time":"2017-09-05T18:09:15Z"}
{"level":"info","msg":"Changing records: CREATE {\n  Action: \"CREATE\",\n  ResourceRecordSet: {\n    Name: \"domain.name\",\n    ResourceRecords: [{\n        Value: \"\\\"heritage=external-dns,external-dns/owner=owner\\\"\"\n      }],\n    TTL: 300,\n    Type: \"TXT\"\n  }\n} ...","time":"2017-09-05T18:09:15Z"}
{"level":"error","msg":"InvalidChangeBatch: RRSet of type TXT with DNS name domain.name. is not permitted because a conflicting RRSet of type  CNAME with the same DNS name already exists in zone target.domain\n\tstatus code: 400, request id: 57afcaff-9265-11e7-9215-53b7bf265623","time":"2017-09-05T18:09:21Z"}
{"level":"info","msg":"Changing records: CREATE {\n  Action: \"CREATE\",\n  ResourceRecordSet: {\n    Name: \"domain.name\",\n    ResourceRecords: [{\n        Value: \"target.domain\"\n      }],\n    TTL: 300,\n    Type: \"CNAME\"\n  }\n} ...","time":"2017-09-05T18:14:24Z"}

Looks like CNAME and TXT records conflict

Duplicate of #270 ?

No they are different issues.  This is trying to create 1 CNAME and 1 TXT.  The linked issue is trying to create 2 A records and 2 TXT records.

The behavior seems to be missing implementation of the suggested approach in the proposal: https://github.com/kubernetes-incubator/external-dns/blob/master/docs/proposal/registry.md#bads

Actually one can workaround that by specifying some value for the --txt-prefix install option. Then the CNAME and TXT records are created with different DNS names and the RFC1912 is not violated.

Ref: http://www.rfc-editor.org/rfc/rfc1912.txt
CNAME's cannot co-exist with other types of records. That's exactly the reason why we have --txt-prefix flag, as @valdemon pointed out. Closing this issue.

@ideahitme would it make sense to document this or to default --txt-prefix to some value so a user won't have this issue in the first place?

@sstarcher 👍 for documenting, would you like to do it ?

Keeping it simple - https://github.com/kubernetes-incubator/external-dns/pull/397


Not able to login, blank screen

I am using Ubuntu 20.04.2 LTS.
Yesterday i deleted my tusk application and reinstalled, from then i am facing certain issues :-

i am not able to login using "sign in with google option" it shows this browser is not supported, which leads me to exit my application

I am trying to login by entering my username and the moment i hit continue it the screen becomes blank

It works with this solution:
https://github.com/klaussinani/tusk/issues/308


Tests are not working

The tests are not working. The recently changed tests are not integrated into the github actions. I have added a branch correct_unique_conda_environment that creates a single environment for all steps to be used (conda create -f environment.yml). This is then also added in the actions.

Its possible that the failure of the FEM test has nothing to do with the changes in this repo. I fear there is some outside dependency that has changed. Annika and I have the same problem within the fenics concrete repostory.


DSD-691: Link custom anchor styles bug fix

Fixes JIRA ticket DSD-691
This PR does the following:

Fixes the styles of custom anchor elements in the Link component when they are passed as a child prop.

How has this been tested?
Storybook.
Accessibility concerns or updates

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr833-npj5pidbb1vhy17wug0m1l9lo3wjpre1.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d74ff65f46ed13d8e1906f

Tugboat has finished building the preview for this pull request!
Link:

https://pr833-npj5pidbb1vhy17wug0m1l9lo3wjpre1.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d74ff65f46ed13d8e1906f

Tugboat has finished building the preview for this pull request!
Link:

https://pr833-npj5pidbb1vhy17wug0m1l9lo3wjpre1.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d74ff65f46ed13d8e1906f

Tugboat has finished building the preview for this pull request!
Link:

https://pr833-npj5pidbb1vhy17wug0m1l9lo3wjpre1.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d74ff65f46ed13d8e1906f

Tugboat has finished building the preview for this pull request!
Link:

https://pr833-npj5pidbb1vhy17wug0m1l9lo3wjpre1.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d74ff65f46ed13d8e1906f


Use System.Data.SqlDbType enums for column types instead of .NET Types

The CreateDataTable method should configure the DataColumn.DataType properties using System.Data.SqlTypes rather than .NET CLR Types, which involves some ambiguity and assumptions that serve no useful purpose.
The README documentation should also reflect this preference in the section showing how to add custom property columns.
Could probably be implemented alongside feature request #130.

The next PR will use System.Data.SqlDbType enums which will allow us to accurately represent all (well, most) of the correct SQL Server column types.

When did this change? ColumnOptions now requires a Type for the DataType.... Which is pretty ambiguous.


Update rio dependencies

Currently rio's crates are updated to 0.7.x minor, and sophia pegs to 0.6.x. Thus one have to peg rio to older version to resolve clash.

yes, an new release of Sophia should be released soon (it is currently stalled on the stabilization of Generic Associated Types), that should fix that.


Shadowservice canary

ServiceCanary is automatically added or deleted according to the creation and deletion of shadowservice

Codecov Report

Merging #107 (a1c1833) into main (6335c01) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
- Coverage   77.50%   77.46%   -0.04%
==========================================
  Files          64       64
  Lines        5308     5308
==========================================
- Hits         4114     4112       -2
- Misses        953      956       +3
+ Partials      241      240       -1

Impacted Files
Coverage Δ

.../client/command/meshinstall/controlpanel/deploy.go
50.70% <0.00%> (-1.41%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6335c01...a1c1833. Read the comment docs.


Jond/civil connector schema 2023 additional updates

Additional WIP updates to Civil Connector-related schemas.

/azp run


support overloaded functions

Currently, the constructs like expectTypeOf.toBeCallableWith, expectTypeOf.parameters, expectTypeOf.parameter do not work with function overloads.  Basically they just assume the signature of the last overload and give error otherwise.
I believe this could be made work, doing something similar to what is described here:
https://stackoverflow.com/questions/59535995/parameters-generic-of-overloaded-function-doesnt-contain-all-options/59538756#59538756
Although, for expectTypeOf.parameter, I m not sure how to refer to a parameter at given index for specific overload.  But i believe "toBeCallableWith" and "parameters" could be made work.
Thanks.

Oh that's an interesting workaround. Yes, I'd be open to adding that. Let me know if you would like to create a PR. There are some big-ish perf changes in flux right now, but this would probably be separate enough that it doesn't affect them.

@mmkal I'm gonna give this a shot!


feat: provide developer documentation for our signal service and Bridge contracts

Describe the feature request
We have documentation for users to use the Bridge, but we do not have sufficient technical documentation for dApp developers who wants to use our Bridge and the new ISignalService. @d1onys1us correct me if I'm wrong.
BTW, the IServiceSignal will be added (refactored) later this month.
Describe alternatives you've considered
Description of the alternatives you've considered here.
Additional context
Additional context here.

dddd

finished most documentation here. added a separate issue for next sprint, which is a dapp building tutorial: https://github.com/taikoxyz/taiko-mono/issues/13148


🐛 Could not start dynamically linked executable: ./biome-linux-x64

VS Code version
1.89.1
Extension version
2.2.3
Biome version
1.7.3
Operating system

[ ] Windows
[ ] macOS
[X] Linux

Description
The bundled biome cli uses a dynamically linked release. This is not a good choice since it introduces several hidden dependencies on the end users and limits the compatibility:

linux-vdso.so.1
libgcc_s.so.1
libpthread.so.0
libm.so.6
libdl.so.2
libc.so.6

The biome-linux-x64-musl release is statically linked, meaning that it has no external dependencies and all necessary code is contained within the binary. This is the best choice if talking compatibility.

Please consider using a self-contained binary for the use within the extension.
Steps to reproduce
N/A
Expected behavior
Extensions uses statically linked biome cli release.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
No response

@nhedger The issue here is that the *-musl binaries aren't correctly picked

@ematipico It appears that this code snippet will not work in the NixOS case. NixOS is glibc-based but prevents dynamically linked executables (via custom /lib64/ld-linux-x86-64.so.2). Is there any reason for simply not using the musl release on all systems? Statically linked programs can run anywhere without additional dependencies, be it a glibc system or a musl system. If the musl binary was not statically compiled, then indeed it would require a musl-compatible system, but this is not the case here.

@Zaczero No specific reason other than we never looked into it. I personally don't have a lot of experience with musl, so I never assumed that it was possible. Are we certain that there no trade-offs ?

@Zaczero would you have time to send a PR?

@nhedger @ematipico I can prepare a PR and the change would be straightforward. The questions is whether it's fine to use musl builds globally. Given my understanding, x64 statically compiled binaries will work on all x64 systems, as they have no external dependencies. They are basically self-contained. It doesn't matter what system they are running on - because they are independent. In the situation where the glibc build is not statically compiled, it has an external dependency on glibc which makes it incompatible with Alpine/NixOS/and similar. Additional info on the wiki.


Location message not responding when click the option (ver 4.0.14)

I'm still using ver 4.0.14. However, found that the location sharing option no longer. Is it something wrong with the configuration? I did included the API generated by Firebase in the manifest file, enabled the Places API & Static Map API at google cloud platform. Kindly need your advise on this. Thanks.

I'm using the online library for the text input at UI

Attached with the manifest part that having the geo API key


[Feature Request] do you plan to upgrade to tailwindcss v2 ?

What is your enhancement?
new features..

Any updates?

Any updates?

Hello there, @dzcpy @lironmo ,
Sorry for this late reply. I do not understand why Github did not notify me about this.
Yes, we'll update to Tailwind v2 in about 2 months.
Best,
Manu

Great!

Could you please tell me how to upgrade latest version of this project?

Hello there, @shankar-bavan ,
You can follow our instructions from our release here: https://github.com/creativetimofficial/notus-react/releases.
After that, you will have to replace your tailwind.config.js file with our, and you're good to go.
Best,
Manu

Hello there, @shankar-bavan ,
You can follow our instructions from our release here: https://github.com/creativetimofficial/notus-react/releases.
After that, you will have to replace your tailwind.config.js file with our, and you're good to go.
Best,
Manu

Great. Thank you very much for your great work :)


Create CR and CRD from the same helm chart

We have a scenario where we wanted to create both CRD and one CR resource of that CRD in  the same helm chart.
We tried using the CRD folder approach as suggested in the documentation. But we won't be able to support upgrade scenario of existing charts because of this limitation: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations
So we tried the following:
Install CRD as pre-install hook and try installing the CR as a normal template. But we are getting the following error:
PS C:\Users\rapatchi\Desktop\chart> helm install azure-arc .\azure-arc-k8sagents-0.1.4002-private\azure-arc-k8sagents\ -f userValues.txt --atomic --timeout 5m0s --debug
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: C:\Users\rapatchi\Desktop\chart\azure-arc-k8sagents-0.1.4002-private\azure-arc-k8sagents
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ClusterConnectCertificate" in version "clusterconfig.azure.com/v1beta1"
helm.go:81: [debug] unable to recognize "": no matches for kind "ClusterConnectCertificate" in version "clusterconfig.azure.com/v1beta1"
unable to build kubernetes objects from release manifest
helm.sh/helm/v3/pkg/action.(*Install).Run
/home/circleci/helm.sh/helm/pkg/action/install.go:258
main.runInstall
/home/circleci/helm.sh/helm/cmd/helm/install.go:242
main.newInstallCmd.func2
/home/circleci/helm.sh/helm/cmd/helm/install.go:120
github.com/spf13/cobra.(*Command).execute
/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
/go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
/home/circleci/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
/usr/local/go/src/runtime/proc.go:204
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1374
Could you suggest us the correct way to handle this scenario ?.
Output of helm version:
version.BuildInfo{Version:"v3.5.2", GitCommit:"167aac70832d3a384f65f9745335e9fb40169dc2", GitTreeState:"dirty", GoVersion:"go1.15.7"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"e1d093448d0ed9b9b1a48f49833ff1ee64c05ba5", GitTreeState:"clean", BuildDate:"2021-06-03T00:20:57Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  AKS

If you're looking at CRDs, upgrades, and changes I would suggest reading the context around CRD handling in Helm. There is a great deal of information on how Kubernetes handles CRDs and problematic situations you may end up in.
The issue you're seeing is that manifests for everything are built before the hooks are run. This is needed to that helm has the hook manifests to run. In doing this, Helm (Kubernetes packages really) will see that some of the built manifests are not valid for this cluster. That will cause an error.
I'm not sure of a nice way around it, off hand. Have you considered installing the CRDs via a second chart. This is the alternative method in the Helm docs.


context manager capabilities for cluster config

Expected Behavior
Should be possible to do something like: with Cluster(...) as cluster: and declare tasks within this with block. This would result in the cluster object being assigned to all tasks declared within this block.
Current Behavior
NA
Steps to Reproduce (for bugs)
Context
Your Environment

pyjaws version used:

Hey @rafaelpierre, this is for syntactic sugar? We don't seem to access any resources in the cluster.
Adding something like this to Cluster...
class Cluster(BaseModel):
   ...
    def __enter__(self) -> Cluster:
        return self

    def __exit__(self, *args):
        pass

We can use it like this...

with Cluster(...) as cluster:
    task_1 = NotebookTask(
    ...
    cluster=cluster)

I've seen with syntax used quite differently in the kubeflow dsl though, ExitHandler & ParallelFor for example.

Yep, I can take this. I'll create a pr in sometime.

Amazing @aaravind100!

Closed with https://github.com/rafaelpierre/pyjaws/pull/14


dunst: 1.11.0 -> 1.12.0

Release: https://github.com/dunst-project/dunst/releases/tag/v1.12.0

The behaviour of the setting height has been changed in a breaking way. [...] If you are a maintainer it would be helpful to include the message above when an user updates from an older version of dunst.

It's a breaking change but I don't think it's worth mentioning in the release notes.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360503

x86_64-linux

:white_check_mark: 3 packages built:

betterlockscreen
dunst
dunst.man


Default module configuration missing status codes

When deploying the exporter by default the module configuration looks like below:
modules:
  http_2xx:
    http: null
    prober: http
    timeout: 5s

When it is like this all Prometheus queries from the exporter return 0, whether or not they are reachable. This happens because most of the config for the variable blackbox_exporter_configuration_modules in the defaults file is commented out, and the README doesn't specify that variable as something that must be defined. There should be some sane values in the defaults file, eg:
blackbox_exporter_configuration_modules:
  http_2xx:
    prober: http
    timeout: 5s
    http:
      valid_status_codes: []
      method: GET

Could you create a PR to fix this?


Fix the AddActivityIndexes migration's down() method

This PR fixes artisan migration:rollback, which was broken due to incorrect index names in the 2020_09_19_094251_add_activity_indexes migration:
SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP INDEX `key`; check that it exists (SQL: alter table `activities` drop index `key`)

Proposed a workflow to automatically test migrations in https://github.com/BookStackApp/BookStack/pull/2270

Thanks for fixing this @gertjankrol, I really need to remember that index and dropIndex work in different ways. Merging in now for next patch release.


Filters in Canvas 2D

Spec: https://html.spec.whatwg.org/multipage/scripting.html#filters
We'd like to ship this in Blink in Chrome 52, which in practice means enabling it by May 6th.
Blink Intent-to-Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Jhwj8QAYaFY
Mozilla Intent to Implement and Ship: https://groups.google.com/forum/#!topic/mozilla.dev.platform/AKVp1cqQYHQ
This spec has been discussed on the whatwg mailing list:
https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Sep/0110.html
cc @mstange @junov

I think this is mostly straightforward, allowing application of existing filter concepts to canvas.  I filed two minor issues (see above).
I don't think this exposes any issues about the atomicity of canvas drawing operations beyond what's already exposed by globalAlpha and globalCompositeOperation, although it would be nice to check that somebody else agrees with my assessment there.
One other thing I need to look into a little further is that I recall that SVG filters used to define a concept of a filter effects region.  I need to figure out if this concept is still present in filters or if it's been removed.  (I think I recall some talk about removing it.)  If it's not removed, then this section would presumably need to define it.  (I think it's better off gone, replaced by "use the region that's needed to get the right result".)

Discused this briefly on the call today.  As noted, I raised the 5 minor issues above, but we don't see a need to have this on the TAG's agenda again, though hopefully there will be continued discussion in the linked issues.


[Bug]: there are omissions in disabling the export entry

ODC version
4.2.2
OB version
none
What happened?
After setting odc.data.export.enabled to false in metadb, the most entry of export function are disabled. But we still can find an export entry in project -> databases.

What did you expect to happen?
All entry should be disabled.
How can we reproduce it (as minimally and precisely as possible)?
setting odc.data.export.enabled to false in metadb.
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 035abd43c3654b591545442c387b8c94172ebdcf
------
xiaokang
Mon Dec 4 13:57:06 2023 +0800