Binding necklace- Destroy issue

| Operating System | /Windows 10
When I use binding necklace and destroy it, the client doesn't seem to register it's been destroyed so the charges stay the same. It changes the display on the necklace when I use a new binding necklace to '?' untill the next one goes to the number of charges the previous binding necklace was at. Kind of hard to track when i'm trying to use the necklace to disintegrate with every two duelling rings for Runecrafting.

You can right-click and press "Check" to update the counter. This can be used as a work around until someone finds a proper solution.


Wrong versions if package changed versioning scheme

For example python package "neutron" have changed versioning scheme from calver to semver.
https://osv.dev/vulnerability/GHSA-4pmp-38hf-rmwj
New versions marked as affected, but this vulnerability fixed a long time ago.

Hi @kindlycat,
Thanks for reporting.
Hmm, we sort according to PyPI's version sorting rules, and it's unfortunate that the "newer" semver versions sort before the calver versions. That said, I don't actually see any calver versions on https://pypi.org/project/neutron/#history, so either they got deleted, or this advisory is completely wrong.
I've created https://github.com/github/advisory-database/pull/2062 to get this fixed upstream on GitHub.

Looks like https://github.com/github/advisory-database/pull/2062 resulted in a withdrawal of the offending record (although you'd be forgiven for not realising that, because the web interface doesn't make that evident at all)
curl "https://api.osv.dev/v1/vulns/GHSA-4pmp-38hf-rmwj" | jq .

{
  "id": "GHSA-4pmp-38hf-rmwj",
  "summary": "OpenStack Neutron allows remote authenticated users to cause a denial of service",
  "details": "OpenStack Neutron before 2013.2.4, 2014.x before 2014.1.2, and Juno before Juno-2 allows remote authenticated users to cause a denial of service (crash or long firewall rule updates) by creating a large number of allowed address pairs.",
  "aliases": [
    "CVE-2014-3555"
  ],
  "modified": "2023-04-14T18:48:12.698227Z",
  "published": "2022-05-17T03:06:07Z",
  "withdrawn": "2023-04-14T18:33:38Z",
  "database_specific": {
    "cwe_ids": [],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2023-02-08T19:55:29Z",
    "nvd_published_at": "2014-07-23T14:55:00Z"
  },
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2014-3555"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2014:1078"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2014:1119"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2014:1120"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2014-3555"
    },
    {
      "type": "WEB",
      "url": "https://bugs.launchpad.net/neutron/+bug/1336207"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1118833"
    },
    {
      "type": "PACKAGE",
      "url": "https://opendev.org/openstack/neutron"
    },
    {
      "type": "WEB",
      "url": "https://web.archive.org/web/20200228142429/http://www.securityfocus.com/bid/68765"
    },
    {
      "type": "WEB",
      "url": "http://lists.openstack.org/pipermail/openstack-announce/2014-July/000255.html"
    },
    {
      "type": "WEB",
      "url": "http://rhn.redhat.com/errata/RHSA-2014-1119.html"
    },
    {
      "type": "WEB",
      "url": "http://rhn.redhat.com/errata/RHSA-2014-1120.html"
    },
    {
      "type": "WEB",
      "url": "http://seclists.org/oss-sec/2014/q3/200"
    }
  ],
  "affected": [
    {
      "package": {
        "name": "neutron",
        "ecosystem": "PyPI",
        "purl": "pkg:pypi/neutron"
      },
      "ranges": [
        {
          "type": "ECOSYSTEM",
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2013.2.4"
            }
          ]
        }
      ],
      "versions": [
        "0.0",
        "10.0.5",
        "10.0.6",
        "10.0.7",
        "11.0.3",
        "11.0.4",
        "11.0.5",
        "11.0.6",
        "11.0.7",
        "11.0.8",
        "12.0.0",
        "<IP_ADDRESS>b3",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "12.0.1",
        "12.0.2",
        "12.0.3",
        "12.0.4",
        "12.0.5",
        "12.0.6",
        "12.1.0",
        "12.1.1",
        "13.0.0",
        "<IP_ADDRESS>b1",
        "<IP_ADDRESS>b2",
        "<IP_ADDRESS>b3",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "13.0.1",
        "13.0.2",
        "13.0.3",
        "13.0.4",
        "13.0.5",
        "13.0.6",
        "13.0.7",
        "14.0.0",
        "<IP_ADDRESS>b1",
        "<IP_ADDRESS>b2",
        "<IP_ADDRESS>b3",
        "<IP_ADDRESS>rc1",
        "14.0.1",
        "14.0.2",
        "14.0.3",
        "14.0.4",
        "14.1.0",
        "14.2.0",
        "14.3.0",
        "14.3.1",
        "14.4.0",
        "14.4.1",
        "14.4.2",
        "15.0.0",
        "<IP_ADDRESS>b1",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "15.0.1",
        "15.0.2",
        "15.1.0",
        "15.2.0",
        "15.3.0",
        "15.3.1",
        "15.3.2",
        "15.3.3",
        "15.3.4",
        "16.0.0",
        "<IP_ADDRESS>b1",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "16.1.0",
        "16.2.0",
        "16.3.0",
        "16.3.1",
        "16.3.2",
        "16.4.0",
        "16.4.1",
        "16.4.2",
        "17.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "17.1.0",
        "17.1.1",
        "17.1.2",
        "17.2.0",
        "17.2.1",
        "17.3.0",
        "17.4.0",
        "17.4.1",
        "18.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "18.1.0",
        "18.1.1",
        "18.2.0",
        "18.3.0",
        "18.4.0",
        "18.5.0",
        "18.6.0",
        "19.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "19.1.0",
        "19.2.0",
        "19.3.0",
        "19.4.0",
        "19.5.0",
        "19.6.0",
        "19.7.0",
        "20.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "20.1.0",
        "20.2.0",
        "20.3.0",
        "21.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2",
        "21.1.0",
        "22.0.0",
        "<IP_ADDRESS>rc1",
        "<IP_ADDRESS>rc2"
      ],
      "database_specific": {
        "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-4pmp-38hf-rmwj/GHSA-4pmp-38hf-rmwj.json"
      }
    },
    {
      "package": {
        "name": "neutron",
        "ecosystem": "PyPI",
        "purl": "pkg:pypi/neutron"
      },
      "ranges": [
        {
          "type": "ECOSYSTEM",
          "events": [
            {
              "introduced": "2014.1.0"
            },
            {
              "fixed": "2014.1.2"
            }
          ]
        }
      ],
      "database_specific": {
        "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-4pmp-38hf-rmwj/GHSA-4pmp-38hf-rmwj.json"
      }
    }
  ],
  "schema_version": "1.4.0"
}


removed dynamic pricing and pools references in readme

Fixes #1607 .

Changes proposed in this PR:

removed dynamic pricing in readme
removed pool reference in readme

This PR does not fix the linked issue, yet it says so in the PR description. Changed the PR description to reflect that and merging the PR won't auto-close linked issue


Consider using yarn check instead of check-dependencies

[yarn check] [v]erifies that versions of the package dependencies in the current project’s package.json match those in yarn’s lock file.

yarn check is slower than check-dependencies, but it takes the lockfile into account and no dependency is required.

Sounds good.


fixup new support request text

Docs Build status updates of commit 59277e6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publish service's config file: .openpublishing.publish.config.json is not found. Exception:

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


subject area sequencingProperty name needs to be mapped to displayName in OMAS processing

subject area sequencingProperty name needs to be mapped to displayName in OMAS processing

Please leave open


fix: update foundry tutorial link

What changed? Why?
Outdated link that 404s replaced with the correct tutorial link
Notes to reviewers
Confirmed with @briandoyle81CB in base discord that this is the correct link to use
How has it been tested?
yes
Does this PR add a new token to the bridge?

[x] No, this PR does not add a new token to the bridge
[ ] I've confirmed this token doesn't use a bridge override
[ ] I've confirmed this token is an OptimismMintableERC20

Please include evidence of both confirmations above for your reviewers.

Just noticed that this is fixed in this open PR (https://github.com/base-org/web/pull/395). Feel free to merge or close as duplicate as needed.


Version specific packet implementation pattern

This PR is built on top of #77
This PR adds the pattern for minecraft version specific packet implementation that was discussed in #68.
The newly added PacketSourceGenerator project runs when building the MineSharp.Protocol project and generates C# files that add (via partial keyword) methods/fields/properties to the packet types.
To debug the source generator:
Select Debug build and create the file:
Components/MineSharp.PacketSourceGenerator/debugSourceGenerator.txt.user
then do a rebuild of the MineSharp.Protocol project. This will then run the source generator.
The source generator will look for the file mentioned above and if it exists will call Debugger.Launch().
Then you can attach with your debugger.
TODO:
There are still some things that could be improved:

[x] add interfaces for IPacketClientbound and IPacketServerbound to add type constraints for On<Packet> and SendPacket
[ ] let the source generator emit diagnostics when it detects something wrong (currently this error messages can only be seen when debugging the source generator)

As I was implementing the new version specific packet pattern for RespawnPacket I encountered this problem:
Since Minecraft 1.16.3 this packet changed multiple times but only slightly.
And making multiple records that all have almost the same fields and also almost the same Read and Write methods feels wrong.
How should we deal with this?
Possible solutions:

let (version specific) packet sub types inherit other packet sub types
create a common data container record that is then used in the packet sub types

My thoughts on the solutions:

I do not like it. All packet sub types should only inherit the base packet type. Because otherwise this would break type checking (is keyword)
This is better but still not super nice to use. Usage would be something like respawnPacket.SharedData.DimensionName

What do you think?
Code for RespawnPacketV_1_19_4:
    public sealed partial record RespawnPacketV_1_19_4(
        Identifier DimensionType,
        Identifier DimensionName,
        long HashedSeed,
        GameMode Gamemode,
        GameMode? PreviousGamemode,
        bool IsDebug,
        bool IsFlat,
        DataKeptFlags DataKept,
        bool HasDeathLocation,
        Identifier? DeathDimensionName,
        Position? DeathLocation
    ) : RespawnPacket
    {
        /// <inheritdoc />
        public override void Write(PacketBuffer buffer, MinecraftData data)
        {
            buffer.WriteIdentifier(DimensionType);
            buffer.WriteIdentifier(DimensionName);
            buffer.WriteLong(HashedSeed);
            buffer.WriteByte((byte)Gamemode);
            buffer.WriteSByte(PreviousGamemode.HasValue ? (sbyte)PreviousGamemode : (sbyte)-1);
            buffer.WriteBool(IsDebug);
            buffer.WriteBool(IsFlat);
            buffer.WriteByte((byte)DataKept);
            buffer.WriteBool(HasDeathLocation);
            if (HasDeathLocation)
            {
                buffer.WriteIdentifier(DeathDimensionName!);
                buffer.WritePosition(DeathLocation!.Value);
            }
        }

        /// <inheritdoc />
        public static new RespawnPacketV_1_19_4 Read(PacketBuffer buffer, MinecraftData data)
        {
            var dimensionType = buffer.ReadIdentifier();
            var dimensionName = buffer.ReadIdentifier();
            var hashedSeed = buffer.ReadLong();
            var gamemode = (GameMode)buffer.ReadByte();
            var previousGamemodeValue = buffer.ReadSByte();
            var previousGamemode = previousGamemodeValue == -1 ? null : (GameMode?)previousGamemodeValue;
            var isDebug = buffer.ReadBool();
            var isFlat = buffer.ReadBool();
            var dataKept = (DataKeptFlags)buffer.ReadByte();
            var hasDeathLocation = buffer.ReadBool();
            Identifier? deathDimensionName = null;
            Position? deathLocation = null;
            if (hasDeathLocation)
            {
                deathDimensionName = buffer.ReadIdentifier();
                deathLocation = buffer.ReadPosition();
            }

            return new(dimensionType, dimensionName, hashedSeed, gamemode, previousGamemode, isDebug, isFlat, dataKept, hasDeathLocation, deathDimensionName, deathLocation);
        }
    }

RespawnPacketV_1_20_0 then only added the int PortalCooldown field at the end.

Hi,
sorry for the delay, I'm currently a little stressed out.
I'd also go with option 2. But maybe we can put the shared fields right into the super class, instead of putting them into another SharedData record? It would be syntactically a little bit nicer or is there another drawback?

But maybe we can put the shared fields right into the super class, instead of putting them into another SharedData record? It would be syntactically a little bit nicer or is there another drawback?

The drawback is that with this approach we are now back to our orignal problem for which we started the sub class for every version refactoring. The base class would get fields that the actual packet (sub class) does not have.
For example:
We might want to add the "common" fields (DimensionType, DimensionName, HashedSeed, ...) to the base class. Then the sub classes for V_1_19_4 and V_1_20_0 could use and share these fields. But the sub class for V_1_7_0 would have some fields that are not actually contained in the packet. The V_1_7_0 packet only has these fields: Dimension, Difficulty, Gamemode, LevelType. So the HashedSeed field in the base class is "fake" for V_1_7_0

But the SharedData record shouldn't have nullable types as well right?

Yes. Fields should only be nullable if the packet for the matching protocol version contains nullable (wiki.vg language: Optional) fields.

So maybe we'd need multiple of theses for a packet.

Yes that is correct. And was the idea. SharedData is a bad name then. The fields for the shared data records need names that give some info about the data fields they contain.
We then can build packets like this (only example names):
TestPacketV1: PlayerData, string Name
TestPacketV2: PlayerData, WorldData, string Name
TestPacketV3: WorldData, int Id
(The *Data fields are shared data records)
This way we could make sub packets for multiple versions without much code duplication and copying/processing this data is easier between minecraft versions.
We might also need some shared data records that contain other shared data records. For example when there are 6 fields in the first shared data record and in some later version 2 more fields are added (and versions after that also contain these fields) then we need a new shared data record that contains the first one and also these 2 new fields.
At this point we could also go with inheritance of the shared data records but I think composition is better.
What do you think?

Okay, lets go with the composition approach.
One more idea: We could pass the properties of shared records through to the packet class.
Something like this:
internal PlayerData PlayerData { get; private set; }

public Uuid Uuid
{
     get => PlayerData.Uuid;
     set => PlayerData.Uuid = value;
}

This way we can hide the (probably messy) data records from the outside and keep the Api concise. But it would add a lot of boiler plate code again...
Would it be possible to source generate this? (I have never worked with source generators).

One more idea: We could pass the properties of shared records through to the packet class.

I though of this too. (see below)

Would it be possible to source generate this?

Yes that is possible.
We could do this. But I would not hide the shared data records (instead add these properties in addition to the shared data records). Because these records bundle the fields that most use cases of these packets will need.
What I mean is:
When receiving these packets you probably want to check a condition based on the fields of the packet. And you want to do this check regardless of the actual protocol version. If this check only contains one field then the properties will be helpful. But if this check contains (for example) 6 fields. Then you probably want to extract this check in its own function. And now you would need to pass these 6 fields to the function for every versioned packet class. This is not so nice. If the shared data records are accessible then you could just pass that to the check function.
But you would still need to switch (pattern matching) all the versioned packet classes that provide this shared data record.
Maybe we also need to let the packet classes implement interfaces that provide such shared data records. Then a type check for that interface would be enough to get the shared data record for every versioned packet class that has these values.
These interface could also be source generated.


Spawns Locked In One Location

Bug
Spawn areas are not switching positions and only sticking to one location. When the spawns are like this the game grinds to a halt and turns each match into a spawn camping bore. I'm unsure if this is on all game modes, but in skirmish its always the case. I have no clue what the latest update did to have this happen because it was working as intended before 1.5.1. (unsure if it has something to do with the CTF spawn algorithm change). I hope it can get looked into because its super unfun to play it now when 1. it turns into who can spawn camp better, and 2. The whole map gets closed off with only activity in one area. When both teams only spawns in the same spot every time there's no point in going elsewhere. I hope this gets fixed because it doesn't feel like Titanfall anymore when you just spawn in the same two areas every time.
Steps to reproduce

Specifications

Northstar version:
Platform:

I'm closing this due to missing Northstar version and lack of updates. There have been many changes since so it's not clear whether this is still an issue.

It is still an issue, i popped in for a match and its still the exact same. If its needed i'll write a longer explanation on the issue with pictures if my point didnt come across. My theory is still with the CTF spawn algorithm change that happened in v 1.5.1 ''New spawnzone algorithm for CTF'' is probably where the problem is. The problem with the spawns wasnt happening before that update. Let me know if you need me to explain further.

How did you test it? Just start a private match and suicide?

No, i joined a public server (Skirmish) that was full enough and played for abit. Still same exact areas that the spawns are locked to since last time i played which has been a like two months. When i tested this before i played several other game modes, maps, whatever and still for all of them they had the same problem.

Aight, tagging @BobTheBob9 :3

Closing, issue fixed with https://github.com/R2Northstar/NorthstarMods/pull/829


Incorrect Address

Just ran the allthethings branch and noticed a bug. I started everything from scratch and got this:
C:\Users\work\AppData\Roaming\DriveShare\dataserv-client\dataserv-client.exe --config_path=C:\Users\work\AppData\Roaming\DriveShare/drives/91b818ceb30f1297e07195b614f6ede254d33ddf --store_path=D:\ --max_size=10GB farm
INFO dataserv_client.messaging 43: Query: http://status.driveshare.org/api/address

INFO dataserv_client.messaging 43: Query: http://status.driveshare.org/api/register/18Prv6CxFWFyvwbYRPDJFybq4mBkcDJRGT/18Prv6CxFWFyvwbYRPDJFybq4mBkcDJRGT

INFO dataserv_client.api 88: Registered on server 'http://status.driveshare.org'.

Notice the register command has the 18Prv6CxFWFyvwbYRPDJFybq4mBkcDJRGT address twice. This is incorrect. The endpoint url is /api/register/<bitcoin address>/<(optional)payout address>. I put 1P1eHxxfhsLM3ufQXDuYZKGdM3oBM5jrLh as the payout in the GUI, but seems it did not make it to dataserv-client.

Ack

This will be closed by #65

fixed with driveshare-gui develop (0.4.0)
INFO dataserv_client.messaging 43: Query: http://status.driveshare.org/api/register/1KYki1iw2ErP3UFL3JKZNpab2nhe9KqBY7/16zw6QGFbfmEyrAXDQKbVFhMceZcHobdtP

@littleskunk All the issues fixed by the new version will be automatically fixed when this is merged Monday.


Add Redirects to OpenAI branch

Redirects are currently implemented only on the main branch. They should be extended to OpenAI branch as well.

Implemented with release v1.2.1-OpenAI


Fix to clear SO Allocations on receipt of Return Order Line Item

Added stock_item.clearAllocations() to order/models.py ReturnOrder.receive_line_item
Fixes issue #6092

@mcollins-DL please address style issues :) You should also check out our contributing guide - you can setup so that most of these style issues are fixed automatically on each git commit

Thanks @mcollins-DL for the fix


Relay problam

At startup, the relay output is activated for a moment. Without any command and this seriously endangers the system.please help
thanks a lot

Try a different GPIO

Try a different GPIO

Thank you very much the problem was solved


chore: Fix linter errors. Remove some minor functionality duplications. Resolve dependency deprecation warn

resolves https://github.com/opendatadiscovery/odd-platform/issues/1158

lgtm


fix: Update config to be flexible for host

Currently our config is hardcoded for localhost at a few places, which is okay for development. This PR aims to remove the hardcoding and allow values for process.env.HOST , process.env.PORT and process.env.SYNC_PORT to be configured for working in special cases such as C9 IDE.
Tested changes locally and C9 IDE.
This is advantageous in certain scenarios where contributors may want to work with a Cloud IDE, instead of a local environment.
I am up for a blog post on how I do so if this is accepted.
/cc @QuincyLarson @BerkeleyTrue

@Greenheart yes, the idea is to provide flexibility while not providing any dedicated support for Cloud IDEs.
I'll create a writeup soon to get this working, if this is accepted. This helps in working from anywhere 😉 ..!

@raisedadead is

@QuincyLarson Yes, this is ready!

One more change and this can be merged. I've tested it out locally.

Sorry about the delays, have been AFK since long.

@raisedadead did you address @BerkeleyTrue's review? If so please mark it resolved.
I'll leaving this for @BerkeleyTrue to QA since he's already in the loop.

@QuincyLarson yes, I have addressed the review. I can't dismiss/approve Berkeley's comments, for sake of keeping the history.
@BerkeleyTrue whenever you can this is ready for a merge.

@raisedadead awesome - thanks for finishing this! And thanks to @BerkeleyTrue for QA'ing!


fix(mpa): support mpa fallback

Description

fixes #10966
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

the docs would need to be updated: https://vitejs.dev/config/shared-options.html#apptype

@brillout you might be interested in taking a look at this PR

What’s the difference between returning undefined and returning request.url?

Undefined will crash the server instead of calling next() per the issue.

@benmccann would you do another PR modifying the docs if you see something to improve there? I don't see references to the fallback right now there that should be updated.

Undefined will crash the server instead of calling next() per the issue.

👍 I don't see any objections then.


registration form component issue 33

In "AuthService" I created the constructor, and noticed that the singIn implementation was not done. I have added the http request to the backend and processed the response for login case. Let me know if it conflicts with your code/plans.
public async signIn(userData: User) {
const response = await this.http
.post(${environment.serverURL}/sign-in, userData)
.toPromise()
    if (!response?.access_token) {
        throw new Error("Invalid response body!")
    }

    localStorage.setItem("ACCESS_TOKEN", response.access_token)
    this.stateChanges.next(true)
}

The registration endpoint will be at /api/accounts/register/. A POST request has to be made; it expects data to be JSON:
{
    "password": "..",
    "username": "...",
    "password_confirm": "..."
}

So, the front end needs to ask for the password to be repeated. The registration may fail if the passwords don't match or if the password is "too common". It will probably also fail if the username is already taken. I don't remember what the exact HTTP status codes are for those responses, but I will get back to you with that information later. However, I do know that on success the status code is 201.
By default, I don't think an e-mail can be given to the API, but I will be researching how to configure that.
Registration will not log in the user. For that, there is a separate login endpoint. I believe it is /api/accounts/login/. I haven't done enough research into that endpoint, and plan to do that research next. Then I will let you know how authorization needs to be handled.

I will update registration endpoint shortly in my Pull Request. Still I need the server url, under what domain the backend is deployed, now I put it “https://exmaple.com”

About confirm password -  I covered this via Angular ngIf directive-  attribute which works essentially as an “if” statement for HTML. You can see it in sign-up.component.html
“

        Confirm your password

        Not matching

“

Registration POST request logic:
IMO(In My Opinion) registration creates a new user in the backend, generates a token for it, and returns already logged-in user data to the frontend. There is a separate login endpoint for another user case when user is already logged in, comes to the site e.g. second time, and taps on the Login button directly from the UI.
It means when I do a registration request, I do not have to do another login request, login should be and required to be included in the registration.
Registration = create new user + login + return user data
Login = find user by email and password + return user data

IMO(In My Opinion) registration creates a new user in the backend, generates a token for it, and returns already logged-in user data to the frontend. There is a separate login endpoint for another user case when user is already logged in, comes to the site e.g. second time, and taps on the Login button directly from the UI.
It means when I do a registration request, I do not have to do another login request, login should be and required to be included in the registration.

I think the reason django-rest-registration does not do it this way is because it needs to suppose intermediary steps like e-mail verification (if we enable it). I'm not sure if it's feasible to modify the API to log in upon registration. If it is a problem to just make a separate request to the login endpoint, then I can look into how to login upon registration from the back end.

For the registration endpoint, there are some optional fields. You could still add fields to the form for these, but leave them as optional rather than required:

email
first_name
last_name

Still I need the server url, under what domain the backend is deployed, now I put it https://exmaple.com

We don't know yet. Are you not able to just use a relative URL, so that the current host is prepended?

Logging In
The login API is fairly simple. You send a POST request to /api/accounts/login/. The data should be JSON, which contains login and password keys. For login, currently only the username is allowed; users cannot log in using their email, but this can be changed later if we want.
If login is successful, it will return a 200 status code. It will also set two cookies: csrftoken and sessionid. The CSRF token will be important for making authenticated requests later.
Example Request
Here is the code I pasted into my browser's console to try out the endpoint. Note that this uses the JS fetch API, which is part of the language. Angular probably has its own way of doing this, so just take this as an example rather than thinking you need to do it exactly like this.
(async () => {
    let response = await fetch(
        "/api/accounts/login/",
        {
            method: "POST",
            headers: {
                'Accept': 'application/json',
                'Content-Type': 'application/json',
            },
            body: JSON.stringify({
                login: "user2",
                password: "9023fj32",
            }),
        }
    );
    let content = await response.json();
    console.log(content);
})();

Logging Out
Logging out is a bit more complex, since it is an authenticated endpoint. Authentication works by providing the CSRF token in the request's header. The CSRF token comes from the cookie described earlier, which was generated by logging in.
Django's documentation describes how to get the token and how to pass it to the request. Note that Angular may have an easier way to retrieve cookies, so look into that. If not, maybe it's worth using the cookie library that Django's documentation recommends.
For now, Django is configured with the default, which is to store the CSRF token in a cookie. Maybe later I will investigate the alternative of using a session instead. However, that isn't a priority, so you can be safe to assume it's a cookie for the time being.
Example Request
function getCookie(name) {
    let cookieValue = null;
    if (document.cookie && document.cookie !== '') {
        const cookies = document.cookie.split(';');
        for (let i = 0; i < cookies.length; i++) {
            const cookie = cookies[i].trim();
            // Does this cookie string begin with the name we want?
            if (cookie.substring(0, name.length + 1) === (name + '=')) {
                cookieValue = decodeURIComponent(cookie.substring(name.length + 1));
                break;
            }
        }
    }
    return cookieValue;
}

(async () => {
    let response = await fetch(
        "/api/accounts/logout/",
        {
            method: "POST",
            headers: {
                'Accept': 'application/json',
                'X-CSRFToken': getCookie('csrftoken'),
            }
        }
    );
    let content = await response.json();
    console.log(content);
})();

Note that in #45 I have also added support for logging in with email. Thus, the user can log in either with an email or with their username.

Superseded by #63


reference a more modern UTF-8 RFC

This address this comment:

** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629)

by https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-cellar-ebml-02.txt

LGTM


chore(concurrency, fee): add a sanity check when the fee transfer is …

…None

This change is

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

Project coverage is 78.47%. Comparing base (f64dc0e) to head (430d60f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1999   +/-   ##
=======================================
  Coverage   78.47%   78.47%
=======================================
  Files          62       62
  Lines        8967     8967
  Branches     8967     8967
=======================================
  Hits         7037     7037
  Misses       1483     1483
  Partials      447      447

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


feat: multiple audio tracks playing simultaneously

see https://gist.github.com/standinga/24342d23acfe70dc08cbcc994895f32b

still in wip because we need to use new instance of SAPlayer, to play more than one track at a time

It is now possible to instantiate more than one instance of JustAudioPlayer with the same engine to handle more than one AudioSource, play/pause, streams, etc. are closely linked to the single audio source


Unable to display mobile interface

After the success is displayed, there is no response and the mobile phone interface will not pop up
scrcpy 2.1 https://github.com/Genymobile/scrcpy
C:\Program Files\scrcpy-win64-v2.1\scrcpy-server: 1 file pushed, 0 skipped. 64.5 MB/s (56955 bytes in 0.001s)
[server] INFO: Device: [meizu] meizu MEIZU 18 (Android 11)
INFO: Renderer: direct3d
INFO: Texture: 1080x2160
The above content is displayed, but the mobile interface will not appear

Version 2.0 works normally

scrcpy on Meizu phones:

Are you comfortable building the project from sources, and use git bisect to find the offending commit?
Might probably be 6ba99a62ff51c0ce209db78a9ed17f1633170027 or fb21bbf763691407bc069d84b8e6248667a80e6f.

Probably fixed by 7e936fa879d9ee37608d9d0ce36f66ea06a6317d available in v2.1.1


update php language source

this is more complete and reliable
Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

add "in progress" notation (translated).
Please read CONTRIBUTING.md guidelines.


Feat/identity rebased

Description of change
Please write a summary of your changes and why you made them.
Links to any relevant issues
Be sure to reference any related issues by adding fixes issue #.
Type of change
Add an x to the boxes that are relevant to your changes.

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Add an x to the boxes that are relevant to your changes.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Work will continue at https://github.com/iotaledger/identity.rs/pull/1436 using a cleaned (but rewritten) history


finish 3min video

https://docs.google.com/document/d/1s0moCe8rEe0BdHwgVEsJ4wSOnziiTXLaYgHbZeluWHc/edit

Two more links. Working on the script as well the slide.
Slide: https://docs.google.com/presentation/d/1G3Fdj0XSDu6lYG5i1CGdGIvqsl3QlAVdOzS0CQBYsK4/edit?usp=sharing
Script: https://docs.google.com/document/d/1NK0sBjsrIFXQTM08aliPJxU7khmO1sU8zgGwIdf64VI/edit?usp=sharing

https://youtu.be/t5bbhck4Q7Y

done I guess. Might reopen if there is something needed to be improved


Index Europe data

Index new data europe data from:
https://github.com/geometalab/OSMNames/releases

Done.
Reported 40 invalid lines in https://github.com/geometalab/OSMNames/issues/32
And found one duplicate by random https://github.com/geometalab/OSMNames/issues/33
# time /usr/bin/indexer -c /etc/sphinxsearch/sphinx.conf --rotate --all
Sphinx 2.2.10-id64-release (2c212e0)
Copyright (c) 2001-2015, Andrew Aksyonoff
Copyright (c) 2008-2015, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file '/etc/sphinxsearch/sphinx.conf'...
WARNING: key 'charset_type' was permanently removed from Sphinx configuration. Refer to documentation for details.
WARNING: key 'charset_type' was permanently removed from Sphinx configuration. Refer to documentation for details.
indexing index 'ind_charset'...
ERROR: index 'ind_charset': key 'path' not found.
indexing index 'ind_main_charset'...
ERROR: index 'ind_main_charset': key 'path' not found.
indexing index 'ind_name'...
collected 8478284 docs, 832.2 MB
sorted 96.7 Mhits, 100.0% done
total 8478284 docs, 832248306 bytes
total 180.877 sec, 4601165 bytes/sec, 46873.01 docs/sec
indexing index 'ind_name_metaphone'...
WARNING: index 'ind_name_metaphone': dict=keywords and prefixes and morphology enabled, forcing index_exact_words=1
collected 8478284 docs, 832.2 MB
sorted 193.3 Mhits, 100.0% done
total 8478284 docs, 832248306 bytes
total 269.618 sec, 3086758 bytes/sec, 31445.44 docs/sec
indexing index 'ind_name_soundex'...
WARNING: index 'ind_name_soundex': dict=keywords and prefixes and morphology enabled, forcing index_exact_words=1
collected 8478284 docs, 832.2 MB
sorted 193.3 Mhits, 100.0% done
total 8478284 docs, 832248306 bytes
total 231.773 sec, 3590780 bytes/sec, 36580.02 docs/sec
skipping non-plain index 'name_index'...
skipping non-plain index 'search_index'...
total 25453477 reads, 11.466 sec, 0.5 kb/call avg, 0.0 msec/call avg
total 42992 writes, 49.681 sec, 436.0 kb/call avg, 1.1 msec/call avg
rotating indices: successfully sent SIGHUP to searchd (pid=19).

real	11m22.294s
user	9m19.740s
sys	0m32.592s

It is not yet deployed, is it?

Aha - it is "Brno" does not jump on top of phrase "Brno". Issue #13

Yes, I know :( I am going to fix it now.


It is not possible to select more than 1 week

Hello. There may already be a solution, but I haven't found it.
The essence of the problem is that with the range and week-range parameters, the calendar allows you to select only one week, but I need to select a range by week
This is the choice of weeks I need to implement

but when I try to implement it in the sandbox, I feel like the calendar is breaking

without range parameter

But if we select a month or a year, then we can select a range by month or year

I will be very grateful if you suggest a solution to the problem.
Thank you.

The range in combination with week-picker is not supported, as a week is already a type of range. It would introduce a lot of possible conflicts by adding it.


Issue With The User Details Activity Screen.

From @imharish29 on August 1, 2017 19:45
The screen gets crashed on opening. Please suggest a solution.
Issue with the // Paint.setShadow
Copied from original issue: firebase/friendlypix#95

Cleaning up issue fixed in upcoming v2.


Initial release

Checklist

[x] The PR has a meaningful title. It will be used to auto-generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[x] PR contains a single logical change (to build a better changelog).
[ ] Update the documentation.
[x] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[ ] Link this PR to related issues or PRs.

We can't use the same key as for S3. I've changed the vault path and updated the install instructions accordingly: https://github.com/appuio/openshift4-docs/pull/347


Incorrect fallback to Direct3D 12 on Vulkan-unsupported device

Tested versions

Reproducible in v4.3.stable.official.77dcf97d8 and v4.4 dev 3

System information
Windows, Intel 4600 graphics
Issue description
When opening an existing project that is set to use the Forward+ renderer, these errors occur on this device:
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
OpenGL API 3.3.0 - Build <IP_ADDRESS>26 - Compatibility - Using Device: Intel - Intel(R) HD Graphics 4600

Project is missing: D:/CURSOS/UTP/ENDLESS/GAME MAKING/path-to-the-throne/godot/project.godot
Editing project: D:/CURSOS/UTP/ENDLESS/Game Maiking/path-to-the-throne/godot
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
WARNING: Your video card drivers seem not to support Vulkan, switching to Direct3D 12.
     at: DisplayServerWindows (platform/windows/display_server_windows.cpp:5985)
D3D12 11_0 - Forward+ - Using Device #0: Intel - Intel(R) HD Graphics 4600
WARNING: PSO caching is not implemented yet in the Direct3D 12 driver.
     at: pipeline_cache_create (drivers/d3d12/rendering_device_driver_d3d12.cpp:4906)
ERROR:ERROR: Shader translation at stage Compute failed.
 Shader translation at stage Compute failed.
   at: ERROR:(drivers/d3d12/rendering_device_driver_d3d12.cpp:3289)

After this, several hundred more gfx-related errors appear in the logs, with the Godot editor window fully black.  After a few seconds the window goes away with this crash:
================================================================
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] error(-1): no debug info in PE/COFF executable
[2] error(-1): no debug info in PE/COFF executable
[3] error(-1): no debug info in PE/COFF executable
[4] error(-1): no debug info in PE/COFF executable
[5] error(-1): no debug info in PE/COFF executable
[6] error(-1): no debug info in PE/COFF executable
[7] error(-1): no debug info in PE/COFF executable
[8] error(-1): no debug info in PE/COFF executable
[9] error(-1): no debug info in PE/COFF executable
[10] error(-1): no debug info in PE/COFF executable
[11] error(-1): no debug info in PE/COFF executable
[12] error(-1): no debug info in PE/COFF executable
[13] error(-1): no debug info in PE/COFF executable
[14] error(-1): no debug info in PE/COFF executable
[15] error(-1): no debug info in PE/COFF executable
[16] error(-1): no debug info in PE/COFF executable
[17] error(-1): no debug info in PE/COFF executable
[18] error(-1): no debug info in PE/COFF executable
[19] error(-1): no debug info in PE/COFF executable
[20] error(-1): no debug info in PE/COFF executable
-- END OF BACKTRACE --
================================================================

Intel 4600 does not support Vulkan nor Direct3D 12 on Windows.
The same thing happens in Godot 4.4 dev 3. (Sorry I did not capture logs from 4.4)
However, Godot 4.4 will not allow me to create a new project with Forward+ because it detects the lack of gfx support. That's a great addition!
Can something similar be applied to opening of existing projects? In this case, I would expect Godot to either give me a friendly error message saying that it can't open the project because of incompatible renderer, or for it to automatically fall back to Compatibility renderer (perhaps with some notification of this).
I see some type of fallback has been implemented via https://github.com/godotengine/godot-proposals/issues/8006 but it seems not to be working in this case.
Steps to reproduce

Open Godot project manager
Open any existing project that uses Forward+ renderer

I see some type of fallback has been implemented via https://github.com/godotengine/godot-proposals/issues/8006 but it seems not to be working in this case.

D3D12 11_0 - Forward+ - Using Device #0: Intel - Intel(R) HD Graphics 4600

The problem with current fallback system, it is done in an early stage of renderer initialization, and only works if API is completely missing (e.g, DX12→GL should work on Windows 7). Windows 10+ always have some level of DX12 support. It's running with 11.0 feature level, which is insufficient for Godot, but renderer init still works, and fallback doesn't trigger.

Godot can work with DX12 11_*  as long as they support SM6.1 (some older Intel GPUs actually do this and their Vulkan support is not that good anyway).
The issue at hand here is #98207 but I currently do not have the time to do a proper pull request for this one. Older SM cannot be supported due with the approach Godot took for DirectX support.

Thanks for the context.
On this device, Godot 4.4 refuses to create a new project with Forward+. Does that imply there is a codepath there that is detecting that D3D12 is not usable? If so, I wonder if we can use it (or get inspiration from it) here.


Category not updating

Bug report
Preconditions
Please provide as detailed information about your environment as possible.
1. master branch

Steps to reproduce
It is important to provide a set of clear steps to reproduce this bug.If relevant please include code samples.
1. Try to update category

Expected result
Tell us what should happen.

Updated category

Actual result
Got an error
SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '=' (SQL: update categories set position = 2, updated_at = 2020-01-14 03:24:24 where id = 2)

hey, its was fixed? i have identical problem :/

Hi @monter08
create Database using this one -
CREATE DATABASE DATABASE-NAME CHARACTER SET utf8 COLLATE utf8_unicode_ci;

Thats works, thanks!


NUMBERS-200: Don't use compensation if it's NaN in Sum#add

Codecov Report

Merging #136 (c11d4c8) into master (844fa94) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #136   +/-   ##
=========================================
  Coverage     99.14%   99.14%
- Complexity     1681     1682    +1
=========================================
  Files            65       65
  Lines          4305     4308    +3
  Branches        854      855    +1
=========================================
+ Hits           4268     4271    +3
  Misses           10       10
  Partials         27       27

Impacted Files
Coverage Δ

...main/java/org/apache/commons/numbers/core/Sum.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[FLINK-11260] Bump the Janino compiler to 3.0.11

Fixes minor (NPE) issues and performance improvoments: http://janino-compiler.github.io/janino/changelog.html
Calcite master is at 3.0.11: https://github.com/apache/calcite/blob/master/pom.xml#L106

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
Bump the Janino compiler dependency
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): yes
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

It passed on my fork: https://travis-ci.org/Fokko/flink/builds/474918896

I think we're better off with a process and schedule for updating dependencies during the release cycle.

@Fokko did you experience any bugs while running a Flink table program? If not, I would suggest to follow @zentol's suggestion and stay in sync with Calcite.


Created QueueusingLL.py

Created Queue using LinkedList

instead of exit(-1) try-catch block
eg:

eg:


Bootstrap for linux

Thanks for the contribution! I modified the packageLinux task to make a deb, as the 'native' type wasn't recognised or doing anything. It works! Graviton appears in the application menu in Ubuntu, albeit with an ugly low res icon, and starting it opens the app. We need to adjust the layout slightly to make it look right on Linux too, but otherwise, no problems! "Wrote once, ran it everywhere!"

Awesome


Import works, but no control or state

Nice to see someone else trying to integrate their Savant switches in to Home Assistant.
I got this installed and setup - it correctly imports my loads from Savant and differentiates switches vs dimmers, but I have no control of them and they all report off, and do not update their state.
I have debug logging enabled for savant_lighting but don't see anything beyond the intial line when it is discovered.
Is there something that needs to be enabled on the Savant side? Is your Savant system host a Linux based host or a macOS based host ('Smart' or 'Pro'), and what version is yours running?

Hey!  Likewise, glad you found your way here.  This is a quick side-project I threw together to get my lights integrated, so apologies for the lack of debug logging and whatnot.
My host is running 10.3.0:582-cprd1.  It's a point release behind my Android app version (10.4), so my system might be behind the latest.  It's running on MacOS (Pro).
The main lighting app runs on port 80 on my host, and includes a full control interface based on websockets.  The websocket server runs on a different port (8480).  That's hardcoded in this integration, so if you're getting any light information at all, that part is at least the same.
I would assume (without any further information) that your version might be ahead of (or behind) mine, and that they've updated their protocol.  There are separate websocket messages for getting information about devices vs. getting their state, so maybe the state-loading messages changed.  According to the initial protocol handshake, my system is using protocol version 0.1.
I'll try to get some proper logging checked in, as well the python scripts I used to test my integration.  In the meantime, if you can load the web app on port 80, and you're comfortable in the Chrome web tools, try to examine the websocket connection on the network tab.  The first message should include the protocol version
Thanks for checking this out!

I'm on a Smart Host, 9.4.x (I think 9.4.2, but my Mac Mini is on the fritz so I don't have access to SDE/SAM currently.)
Also appears to be protocol version 0.1 and same ports
Websocket request info:
Request Headers:
GET ws://<IP_ADDRESS>:8480/ HTTP/1.1
Host: <IP_ADDRESS>:8480
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
Origin: http://<IP_ADDRESS>
Sec-WebSocket-Version: 13
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Sec-GPC: 1
Sec-WebSocket-Key: redacted
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Sec-WebSocket-Protocol: savant_protocol

Response Headers:
HTTP/1.1 101 Switching Protocols
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: redacted
Sec-WebSocket-Protocol: savant_protocol

Initial WS Message:
{"messages":[{"protocolVersion":"0.1","device":{"name":"windows","version":null,"app":"Savant Smart Lighting (build.rev:7.0 Dev)","ip":"<IP_ADDRESS>","model":"unknown"}}],"URI":"session/devicePresent"}

Example 'Turn On' Message:
{"messages":[{"state":"load.300","value":"100%"}],"URI":"state/set"}

Example 'Turn Off' Message:
{"messages":[{"state":"load.300","value":"0%"}],"URI":"state/set"}

I can provide any other specific messages too, if helpful.
Here us the messages seen when monitoring status of load (when controlling my load Kitchen Overhead from within Savant, not from 'Lighting WebGUI')
Kitchen Overhead On:
{ "messages": [
{ "state": "rtc-out", "value": "RLGLV,Kitchen Overhead Scene,7,100,1" },
{ "state": "rtc-out", "value": "RLGLV,Whole Home On,9,100,0" },
{ "state": "rtc-out", "value": "RLGLV,Whole Home Off,10,0,0" },
{ "state": "rtc-out", "value": "RLGLV,Movie Time,11,100,0" },
{ "state": "rtc-out", "value": "RLGLV,HassKitchenOn,15,100,1" },
{ "state": "rtc-out", "value": "RLGLV,HassKitchenOff,16,0,1" },
{ "state": "rtc-out", "value": "RLGLV,Room:Kitchen,34,100,1" },
{ "state": "rtc-out", "value": "RLGLV,RoomMid:Kitchen,35,100,1" },
{ "state": "rtc-out", "value": "RLGLV,RoomLow:Kitchen,36,100,1" }
], "URI": "state/update" }

Kitchen Overhead Off:
{ "messages": [
{ "state": "rtc-out", "value": "RLGLV,Kitchen Overhead Scene,7,0,0" },
{ "state": "rtc-out", "value": "RLGLV,Whole Home On,9,75,0" },
{ "state": "rtc-out", "value": "RLGLV,Whole Home Off,10,0,0" },
{ "state": "rtc-out", "value": "RLGLV,Movie Time,11,100,0" },
{ "state": "rtc-out", "value": "RLGLV,HassKitchenOn,15,0,0" },
{ "state": "rtc-out", "value": "RLGLV,HassKitchenOff,16,0,0" },
{ "state": "rtc-out", "value": "RLGLV,Room:Kitchen,34,50,1" },
{ "state": "rtc-out", "value": "RLGLV,RoomMid:Kitchen,35,50,1" },
{ "state": "rtc-out", "value": "RLGLV,RoomLow:Kitchen,36,50,1" }
], "URI": "state/update" }

Interesting.  When you click on a particular light in the web UI, do you see any messages with a URI like state/module/xxx/get?  This is what my client uses to get the state of a certain device.  Home Assistant will periodically tell the client to update the lights' states, and it sends that message to savant for each light.  If you can capture those types of messages (in and out), I should be able to figure out if there's a difference.
The messages you posted are only for scenes, but it seems like one can also send a message like this to receive module updates on the state/update URI:
{messages: [{state: "module"}], URI: "state/register"}

which subscribes to messages like this:
{ "messages": [
{ "state": "module.029", "value": "100,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1" }
], "URI": "state/update" }

I've already pushed an updated client with updated debug logging, I'll also try to add support for that state/update message tonight.  Give the updated version a shot when you can!

Sorry I still haven't had the time to re-mess with this - the more I thought about it, it is almost surely because of my Savant setup. I have the 'lighting' disabled on the lighting device buttons, but 'control' enabled
e.g.:

This is due to the combination of most of my loads having 'smart' bulbs (so I am not wanting to control the load output of the dimmer/switch, just capture the button press) and my hacky 'integration' between HASS <-> Savant via emulated rokus
Because of my use-case of not wanting to control the actual load output of the dimmers/switches, I expect to have to modify what you have done.
Should have time this coming week to really dive in to it.

This is more of an issue with my implementation than an issue with code, will open a new GH issue for code-specific issue(s)


Update davmail to 4.6.2p1

Thank you for the contribution. It needed some fixes, so they were made in 1f535714cc114965a017724c65e2a8bcdfbb24ed. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


MaterialEditTextPreference bugs

Altered MaterialEditTextPreference to use the inner EditText view from
parent class.
EditText now also uses colorAccent from theme to color the underline

Thank you


Cloning non-existent repository creates empty working directory

Steps to reproduce:

Install dgit
Clone any non-existent repo, e.g. git clone dgit://nope/not-real

Results:
git outputs warning: You appear to have cloned an empty repository. and the not-real directory exists with a .git subdirectory.
Expected:
The not-real directory is not created.

I can no longer reproduce this w/ v0.0.14-alpha.


Remove old code

Resolves: OLPEDGE-1145
Signed-off-by: Mykhailo Kuchma<EMAIL_ADDRESS>

Please, add more descriptive comment into commit according to our commit template


When pausing and starting again, the final track is only the last one.

When pausing the recording and then resuming, the final uploaded track is just the last one.

I've just installed the npm package, but I am still running into this problem. The jsfiddle provided in the demo also seems to have this issue: https://jsfiddle.net/grishkovelli/rb1anxyj/.

Still experiencing this issue today.


Fix win32 error code handling in NamedSecurityInfo

Hello,
In certain case, NameSecurityInfo methods can fail and return an HR result diffrent from ERROR_SUCCESS; current implementation call Chef::ReservedNames::Win32::Error.raise! which tries to get the last error code.
But often the last error code has changed in the meantime... resulting to that kind of error message:

---- Begin Win32 API output ----
System Error Code: 0
System Error Message: The operation completed successfully.
---- End Win32 API output ----

So this PR update the raise! method to allow to pass the error code, and use this new feature in some methods that directly get the HR error code.
cc. @aboten

@Annih We'd like to get this merged but a test to validate the use would be helpful.  If you can add a test, that'll help us get this merged more quickly.

@Annih I have cherry-picked the required commits from this PR into the PR.


Is there a feature that offers a shortcut to reset zoom?

Another question related to zoom is that CTRL + and CTRL - zoom in and out, but how to reset it to default? CTRL + 0 could be an option? I do not see nothing about zoom level reset in https://github.com/Microsoft/vscode-tips-and-tricks#editing-hacks
Regarding touchpad

VSCode Version:
OS Version:

Steps to Reproduce:

Go to terminal or code editor
Press CTRL +  to zoom in
Press CTRL + 0 to reset
Nothing happens (you have to press CTRL -

Reproduces without extensions: Yes/No

You can go to command palette and search reset Zoom and you can see the shortcut key there for your platform.


[Bug]: cannot install puppeteer in android

Bug description
Steps to reproduce the problem:
When os.platform() returns Android, there is an error that prevents it from being installed
Puppeteer version
v19.4.1
Node.js version
v18.12.1
npm version
8.19.2
What operating system are you seeing the problem on?
Linux
Configuration file
No response
Relevant log output
All fragments that determine the device according to os.platform()

Don't close without a proper solution.
Atleast let us know why puppeteer cannot be installed on Android via a linux emulator where we have a browser and nodejs.

Please do not open duplicate issues. Closed issues can always be reopened.
Duplicate of https://github.com/puppeteer/puppeteer/issues/9460


prepend HGT score values with rank (0, 1, 2, etc) so they can be sorted in a heirarchically meaningful way

implemented in #32


Creating too many types for DOM

Commit 06fe1ed53721862b56c61ebb89b1daee2bc10710 introduced a regression in the number of types created when compiling a snippet of @types\d3.  Specifically, it appears to be elaborating types for an error message that ends up getting dropped.
Repro:
{
  "compileOnSave": false,
  "compilerOptions": {
    "alwaysStrict": true,
    "noImplicitAny": true,
    "noEmit": true,
    "lib": [ "es5", "dom" ],
    "noResolve": true,
    "types": [],
    "skipLibCheck": true
  },
  "files": [
    "test.ts",
}

test.ts
declare function select<GElement extends BaseType, OldDatum>(selector: string): Selection2<GElement, OldDatum, HTMLElement, any>;

type BaseType = Element | Document | Window | null | number;

type ValueFn<T extends BaseType, Datum, Result> = (this: T, datum: Datum, index: number, groups: T[] | ArrayLike<T>) => Result;

interface Selection2<GElement extends BaseType, Datum, PElement extends BaseType, PDatum> {
    select<DescElement extends BaseType>(selector: ValueFn<GElement, Datum, DescElement>): Selection2<DescElement, Datum, PElement, PDatum>;
}

For an apples-to-apples comparison, use nolib and specify the 3.1 lib.es5.d.ts and lib.dom.d.ts for both compilations.
In round numbers, there are ~150 types without the change and ~2500 types with the change.

FYI @DanielRosenwasser

Note that 06fe1ed53721862b56c61ebb89b1daee2bc10710 can be rolled back without losing (all of) the functionality it provides because it was a revision of another commit in the same PR.


Greenkeeper keeps creating branches and then deleting them later

The bot keeps creating branches for minor updates, but not PRing them. It just deletes the branch shortly after.
This is causing excessive notifications for me and is quite annoying.
Here's one of the commits it created: https://github.com/turt2live/matrix-dimension/commit/f23fae8ceab64680c3a95dc246ec52bfcc0bb22b
Another is here: https://github.com/turt2live/matrix-dimension/commit/db771744d1bd648ef8bc18d4a67946f4313a8f15
It didn't PR either of these, and the first one seems unneeded to me. Is there some configuration I might be missing?

That's how it's supposed to work. It creates the branch for every new version of your dependencies, runs CI, and only if the build failed or it's a version outside of your current range does it actually create a PR/issue.

That's kind of annoying. But alright.


Implement Approximate NMPC

Should follow Algorithm 1 in http://folk.ntnu.no/torarnj/Paper-NMPC05.pdf?id=ansatte/Johansen_Tor.Arne/Paper-NMPC05.pdf. This will allow for computation of explicit piecewise-linear control laws for nonlinear systems.

Depends on #81

Depends on #81


deployment / replicaset issue helm / terraform-helm

gke 1.17
helm 3.3.4
terraform-helm (latest)
https://github.com/hashicorp/terraform-provider-helm/issues/606
somehow when upgrading via terraform helm / helm the  current replicaset pods are terminated and new ones are created for the previous 'replicaset'.
At the same time the new replicaset also creates new pods.
The beavior should be identical to kubectl edit deployment but it seems that via Helm 3.3.4 the deploymentupdate screw up the replicaset? Not too sure why...

It looks like using an older helm provider,  ie: hashicorp/helm v1.2.0
Basically an older version it seems better.....
with 3.3.4 if i used force_update = true it seems to do rolling update but chrashes on kind: Services  cannot set clusterIP to "" which is related to another bug i've seen in this helm repo

I'm not entirely sure if what you're seeing is a Kubernetes issues, terraform-helm issue, a Helm issue, or something in the chart itself. So, it might take a little bit to figure out.
When the application was last installed, was Kubernetes at version 1.17 or was it an older version? What was the api version on the Deployment at that time? Is there just one deployment and replicaset or is there more than one of those after the upgrade?

This always been Kubernetes 1.17
the kubectl edit of deployment works like a charm, and follow the rollingUpdate Strategy.
When I use latest helm and force_update = true  vs force_udpate = fasle
One of them behave properly but fails due to the following bug https://github.com/helm/helm/issues/7956

I believe it also have something to do with the revisionHistoryLimit.
The use of
  revisionHistoryLimit: 0

Seems to have huge impact / correct the issue. IF set > 0 it seems to have problems

@FLavalliere were you able to determine the issue? Trying to determine if there's a bug in Helm or if this is a chart issue, in which case a ticket should be filed against the chart.

I'd be surprised its a chart issue. I mean the chart works well...
If we manually edit the k8s 'deployment' to update something such as the docker image it works well, ie: perform the rolling update as needed.
But either terraform or helm recreate the 'old replicaset' which terminates all the existing pods with the OLD image and then recreate with the OLD image. Then perfom the creation of new replicaset with the new IMAGE doing rolling update.
I'm not too sure what changes in the old replicaset that would tell kubernetes to terminate all running pods...


Redirect back with anchor

Hi. I am using anchors on pages and when I save the form via post the anchor is removed.
How can I go back with an anchor?

Duplicate of https://github.com/inertiajs/inertia/issues/729


Qdrant - Load the saved vector db/store ?

Issue you'd like to raise.
I use Qdrant through langchain  to store vectors.  But I can't find any example in docs where the dataset is searched based on a previously created collection. How to load the data? I found that Pinecone has "from_existing_index" function, which probably does the thing. But Qdrant doesn't have such a function. I created my own solution using qdrant_client, but I would like to use Langchain to simplify the script. How to do it?
Suggestion:
No response

hi

🤖
Hello,
Thank you for your question. Currently, the Qdrant class in LangChain does not have a method similar to Pinecone's "from_existing_index" function for loading a previously created collection. However, you can use the construct_instance or aconstruct_instance class methods of the Qdrant class to create a new instance and connect to the existing collection. Here's an example:
from qdrant_client import QdrantClient
from langchain.vectorstores import Qdrant
from langchain.embeddings import OpenAIEmbeddings

embeddings = OpenAIEmbeddings()
collection_name = "MyExistingCollection"  # replace with your collection name

qdrant = Qdrant.construct_instance(
    texts=[],  # no texts to add
    embedding=embeddings,
    collection_name=collection_name,
)

In this code, embeddings is an instance of the Embeddings class that you want to use. If you don't have it, you can create it using the appropriate model. For example, if you're using OpenAI's GPT-3 model, you can do:
from langchain.embeddings import OpenAIEmbeddings

embeddings = OpenAIEmbeddings()

Please note that this will not check if the collection actually exists in the Qdrant server. If the collection does not exist, any operation that requires the collection (like add_texts, similarity_search, etc.) will fail.
This approach was derived from the source code of the Qdrant class in the LangChain repository here.
I hope this helps! If you have any other questions, feel free to ask.
Sources

Documentation should point out how to retrieve a vectorstore already uploaded in a database
[Q] How to re-use QDrant collection data that are created separatly with non-default vector name?
libs/langchain/langchain/vectorstores/qdrant.py

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
@dosu-bot the above mentioned method does not work out for RAG based implementations

here is it
    from qdrant_client import QdrantClient
    client = QdrantClient(path=saved_db_path)         db = Qdrant(             client=client,             collection_name=self.collection_name,             embeddings=embeddings,         )
the above piece of code helps you to load the saved qdrant path

🙏 thanks
On Mon, 8 Jan 2024 at 12:28, V.Prasanna kumar @.***>
wrote:

here is it
from qdrant_client import QdrantClient
client = QdrantClient(path=saved_db_path) db = Qdrant( client=client,
collection_name=self.collection_name, embeddings=embeddings, )
the above piece of code helps you to load the saved qdrant path
—
Reply to this email directly, view it on GitHub
https://github.com/langchain-ai/langchain/issues/11471#issuecomment-1880471333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AESCYLPP37EKL4Q6GLF2S2DYNOKKFAVCNFSM6AAAAAA5VTWVXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGQ3TCMZTGM
.
You are receiving this because you commented.Message ID:
@.***>


fix(theme): use react-markdown to render inline markdown

Summary
When we use renderHtml in renderInlineMarkdown, we found that:

if we write a text <list>, It will be rendered to element
we need replace md syntax by RegExp, now it only support code and strong.

Related Issue

Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

The size is a little large, nearly adding a react-dom package

For text <list>, we can transform it as \<list\>

For text <list>, we can transform it as \<list\>

ok, how to test the case, regExp?

For text <list>, we can transform it as \<list\>

ok, how to test the case, regExp?

Both replaceAll or replace + RegExp  can implement it.


Fix initializers.Identity for ideep backend

Initializers were not checking the actual device id in multi gpu environments.
The lack of tests using the cuda_id 1 hid this behavior.
This PR fixes this problem and reworks the test to use the inject_backend_tests
ChainerX support will be added in another PR.

@niboshi review please :)

Apparently it was the caller's responsibility to set the current device before calling initializers' __call__.
Is it plausible to change this requirement?

You mean like in the tests of #7531

Sorry, what do you mean?

Sorry, as I understand from your comment the current allowed behavior in chainer is to do:
  with chainer.using_device(backend_config.device):
            w = initializers.generate_array(initializer, self.shape, xp)

Instead of calling chainer.using_device(backend_config.device) inside initializers.generate_array

Yes

Should we put this PR on hold till a decision is made?

We have decided that the caller of initializers is responsible of using_device.
Could you fix as such?

@niboshi fixed!
with chainer.using_device is now called on the test codes instead of initializers body

Oh, sorry maybe I was wrong about this comment: https://github.com/chainer/chainer/pull/7548#issuecomment-504875677
initializers.generate_array is a "caller" of initializers, so it's responsible of calling using_device.

Addressed!! thanks for the feedback!

Updated

Jenkins, test this please

I fixed the title to reflect the current status.
(Fixes to other initializers are trivial).

Jenkins CI test (for commit d8a9062ed5fb898d89324c6bde176300ba09a0e1, target branch master) failed with status FAILURE.

Jenkins failure is unrelated.


Cannot Process Erasure Request

I get this error on concole:
index.js:4 [justoverclock/be-active-user-indicator] Hello, forum!
www.superbraga.com/:1  is deprecated. Please include
mount-redraw.js:15 TypeError: this.groups(...).forEach is not a function
at e. (index.js:13:12)
at forEach.t. [as badges] (extend.ts:86:24)
at n.view (UserCard.js:32:25)
at forEach.t. [as view] (extend.ts:37:41)
at Function.a (render.js:30:16)
at render.js:155:45
at render.js:160:3
at c (render.js:66:8)
at l (render.js:50:5)
at render.js:134:5
a @ mount-redraw.js:15
(anónimo) @ mount-redraw.js:25
requestAnimationFrame
u @ mount-redraw.js:23
O.handleEvent @ render.js:890
Mostrar mais 4 frames
Mostre menos
mount-redraw.js:15 TypeError: Cannot read properties of undefined (reading 'onbeforeupdate')
at render.js:929:60
at p (render.js:407:8)
at f (render.js:302:11)
at render.js:477:5
at p (render.js:416:15)
at f (render.js:302:11)
at render.js:477:5
at p (render.js:416:15)
at f (render.js:302:11)
at render.js:477:5
a @ mount-redraw.js:15
(anónimo) @ mount-redraw.js:25
requestAnimationFrame
u @ mount-redraw.js:23
O.handleEvent @ render.js:890
And I only get this window on screen.

It can eventually be some extension, has it worked on the past, is there any way to list active extensions using CLI ?
Tried to google it, but found nothing

This is related to Traditional Rank Badges Extension, after disabling it, everything works.


Pivot function is returning None values, when reading DB "too fast"

Hello, I have been going through this issue already on influxdb-python-client, but from the communication with Jakub and additional tests, it seems like it is issue of the DB itself, not a client.
Here is the link to related issue on python-client page: https://github.com/influxdata/influxdb-client-python/issues/662
Steps to reproduce:

A process/thread that is writting about 200 data points into bucket "test_bucket" every second. Each data point has 5 tag and 7 field "columns". One of the field is unique sequence integer. It is generated externally, since InfluxDB does not have such capability, and added to data points before sending the batch of data points to DB (python-client).
Second thread/process that is reading from "test_bucket" every second. No stop time given, just a start time. We are basically querying "give me data that were added since my last query". To receive every data only once, I use |> filter(fn: (r) => r["row_id"] > <last_received_id>)
Even if "writter" does not store any null values in DB, sometimes "reader" receives null in random field value of random data point. Often more than one null column is present, but it is never tag.

Full query:
f'from(bucket: "{self.bucket_name}")'
f' |> range(start: _start)'
f' |> filter(fn: (r) => r["_measurement"] == "measurement_name")'
f' |> drop(columns: ["_start", "_stop"])'
f' |> pivot(rowKey: ["_time"], columnKey: ["_field"], valueColumn: "_value")'
f' |> filter(fn: (r) => r["row_id"] > {id_start})'

What we have observed so far is, that those nulls happen very close to now() date. And Jakub suggested, it is caused by pivot function. To test that, I have added stop date, so delay. Jakub suggested this: |> range(start: _start, stop: -10ms). I did test with 1 minute delay, where start and stop datetimes were calculated in python and passed to query as parameters.
This is working, once I added this delay in reading, I havent seen any null values extracted from DB.
(It was like 5 nulls per hour before delay. No nulls observed after 24h of running test with delay)
BUT, this is not a solution for us. The data we are receiving (and writting) are not chronologically ordered, and it is impossible to have them chronologically ordered (on input). We also need to extract each new data point only once, not more. Otherwise next layer, above us will have duplicates and that will cause errors.
That is why we added the row_id for filtering. And because we use also row_id to filter data, it is possible that we will be loosing data if we add stop time in range() function.
Basically, the chronologically "younger" datapoint, that is excluded by stop parameter, can have lower row_id because it was received earlier than "older" data points. In that case, this data point will be excluded in first query by stop range parameter. Than in next query, it will be filtered out again by r["row_id"] > {id_start} filter. And we will never extract it from DB.
(I dont want to go too much in details about this here, since is different topic, but I can explain it in comments, if asked).
Expected behaviour:
Once datapoints are written, they are fully usable. So if I ask DB "give me all data from 1min ago until now", it will give me all data that are fully available. In know that internal structure of DB has each field assigned to its tag separately. But if I write datapoint with 7 field values, none of those 7 field values should be available for reading, until all of them are "processed" correctly. It should be one transaction.
Actual behaviour:
If I write data point with 7 field values, some of the values are available for reading before others. And if I read the data point "too fast" I can receive only partial information for this data point. This is unacceptable. It would be no issue, if I do not receive this data point at all, since it is not yet fully "processed". But returning partial data is causing us big issues in our implementation.
Environment info:

Client Version: influxdb-client-python/1.40.0
InfluxDB Version: 2.7.3
Platform: alpine-linux

Config:
No modification in config.
Logs:
Unfortunately, I cannot share any details publicly, because of corporate cybersecurity rules. However, I have permission to share details  needed to reproduce the issue privately (direct messages on Slack, for example).

InfluxDB is a columnar, schema-less database.  There is no way for InfluxDB to know when a point is fully written, because new fields can be added at any time.  When processing a write operation, each field is written separately (which is how fields can be added to a point via multiple writes).
Writes to different fields for the same point can happen at different times. Here are two points being inserted.  One has two values written in a single INSERT statement, then the other is written with two INSERT statements separated by a SELECT, and then the first point has a third field written.
As a user, if you add all fields of a point in one write operation, you can be assured that all fields are written when that operation finishes and returns a success code. So perhaps you can query by looking for data by row ID only after you a sure that the write for that row ID has completed.  So in your filter you could say something like
<omitted code>
|> filter(fn: (r) => r["row_id"] > {id_start} and r["row_id"] <= {id_last_written})'

> INSERT foo,tagone=t1 v1=34,v2=35<PHONE_NUMBER>301626470
> select * from foo
name: foo
time                tagone v1 v2
----                ------ -- --
1721684170301626470 t1     34 35
>
> INSERT foo,tagone=t2 v1=13<PHONE_NUMBER>301626480
> select * from foo
name: foo
time                tagone v1 v2
----                ------ -- --
1721684170301626470 t1     34 35
1721684170301626480 t2     13
>
> INSERT foo,tagone=t2 v2=15<PHONE_NUMBER>301626480
> select * from foo
name: foo
time                tagone v1 v2
----                ------ -- --
1721684170301626470 t1     34 35
1721684170301626480 t2     13 15
>
> INSERT foo,tagone=t1 v3=67<PHONE_NUMBER>301626470
> select * from foo
name: foo
time                tagone v1 v2 v3
----                ------ -- -- --
1721684170301626470 t1     34 35 67
1721684170301626480 t2     13 15
>


Switch generate commands over to policyfiles

We should switch the generate commands over to policyfiles. Optionally we could create a config to set it back to berkshelf. I'd need to be sold on that work given the effort.

This was done in DK 4


Run python script on boot

Idk if we talked about this already, but we should be able to edit rc.local. It's basically a list of extra commands the pi will run while booting, so we can add yinzer.py into the file. We'll want to fork the process to make sure the pi actually boots instead of just hanging (because we want yinzer.py to run continuously), but I think it shouldn't be a problem.
This article talks a bit more about some details: https://raspberrypi-guide.github.io/programming/run-script-on-boot


13-CURRENT: Failed to add WC MTRR error message during boot

Acer RevoOne RL85:
Failed to add WC MTRR for [0xe0000000-0xefffffff]: -22; performance may suffer

/etc/rc.conf contains
kld_list="cuse ig4 iicbus iichid utouch /boot/modules/i915kms.ko"

https://github.com/helloSystem/ISO/commit/5d1a4e6cb531232d2137b1eb5e64c0ef1e005240


Add most features but multi data source support (READY FOR REVIEW)

Todo:

[x] Make it easier to export and save in your data app
[x] Support features to enable recreating https://pygwalkerdemo-cxz7f7pt5oc.streamlit.app/

[x] PureRenderer
[x] GraphicRenderer
[x] TableWalker

[x] Add bike sharing app example like https://pygwalkerdemo-cxz7f7pt5oc.streamlit.app/

[x] basic code
[x] Solve bugs:

[x] Change renderer options to 'explorer', 'profiler', 'viewer', 'chart'.
[x] Make sure all examples in README, examples and PY.CAFE are up to date.
[x] Document bike sharing and earth quake examples
[x] Bump version
[x] Change all README links to absolute urls for pypi rendering.
[ ] Philipp: Fix bug (Optional). When changing to chart renderer the data should be sent to client if not already done. Same when changing from server_computation=True to server_computation=False.
[ ] Philipp: Review, merge and Release v. 0.4.0 (or 0.4.0rc1?)
[ ] Marc: Verify all urls and examples are valid on PY.CAFE. Contribute fixes in 0.4.1 if needed.

Reference App

Will push the fixes you asked for shortly. I do not believe we should be shipping datasets inside the repo however.

Unless you object I will refactor things as I suggested.

Please read comment. You will have to remove more functionality if you do.

I will trust your judgement :-)


Installation failed

Installation failed because the extension is not compatible with the installed applications.

win 1909
After Effects 2020

Hi, can you try using the aescripts zxp installer?
https://aescripts.com/learn/zxp-installer/

Hi, can you try using the aescripts zxp installer?
https://aescripts.com/learn/zxp-installer/

oh....


[Feat] : we can fetch cart from supabase

Description
@pooranjoyb
We can fetch cart items from supabase
And display in cart page
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

Congratulations, @dhruv8433! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines

Go for it! @dhruv8433 🚀

Thank you


Bug Fix empty html useless added by PR #1123 / v1.2.0

Reasons for making this change
The merged PR #1123 add useless wrapping html tag (with empty className) for all field, even if they are no additonal field. This PR fix this.
See comment: https://github.com/mozilla-services/react-jsonschema-form/pull/1123#discussion_r249196311
Some points:

I add new cssClass form-additional-* to help targeting (like for array field)
I use col-9 and 3, like array field, and I don't put on the same line the "Key" field and the "value" field by default. It's unusable on small screen. I think it will be the job of the integrator to add css rules to put this on the same line, if needed.
Maybe it will be good a day to found an other solution for the "key" label name, its really not internationalizable...

Checklist

[x] I'm adding or updating code

[x] I've added and/or updated tests
[x] I've updated docs if needed
[x] I've run npm run cs-format on my branch to conform my code to prettier coding style

@aerfio It's because it's a change on your contribution.
For the blank space, I think it's not a real problem. It's not the best visual, but we are limited on bootstrap style.
Dev's can esealy overwrite css to style this.
I thinks it's better than apply a style on a DOM node, because it's realy harder to overwrite, I agree with @glasserc position. On the ArrayField I think it's a technical depth.
Maybe a good option for inline-style, will be to have an api to overwrite the inline-style object, like react-select do.

@pieplu Could you please modify this PR not to use the WrapIfAdditional component? That way it will be easier to see what logic exactly you are changing. Thanks!

I push it, but I don't think it will be better. It will insert code duplication. It's a big risk of bugs for all future editing of the component.
The reason why I add WrapIfAdditionals Component is to be more understandable. But maybe I lost it.
I will try to explain it:
SchemaFields.js part, before the "additional properties feature":
<div className={classNames}>
     {displayLabel && <Label label={label} required={required} id={id} />}
      {displayLabel && description ? description : null}
      {children}
      {errors}
      {help}
  </div>

Html output:

PR #1021 and #1123 added some code around that to support the additional properties feature.
The big problem, since v1.2.0, for ALL fields (even if no additional properties), looks like this:

To be able to support additional properties feature, it will be important to wrap the schema field with some div. It's the problem, the level of complexity had grown up, and if we preserved same render for all other fields, the wrapping div should not be present any time.
Maybe a better solution will be to introduce a new field component (like ArrayFieldDo) ?

@pieplu , thanks for the explanation, I see what you're doing now. To remove code duplication, you could store the duplicated code in a variable as shown here: https://stackoverflow.com/a/33710901
Also, can you please include only the changes that fix the wrapping div's and the col-xs-12 div in this PR? I appreciate the other changes you made, but I think it's best if those are made on another PR so there is a chance to examine and discuss those changes separately. 👍

@epicfaace Good point for the other PR. +1
For your suggestion, I will, try, but I don't think it will works, because it's not one React node, but many. And on React 15 we don't have React.Fragment built-in.

@pieplu sounds good, please make that other PR!
And, yes, I see your point for using WrapIfAdditional now. Once you separate the additional changes to the other PR, then the diff will be cleaner even with the WrapIfAdditional component. Thanks for sticking with this! 😄

@pieplu just a reminder to make the PR when you get a chance! I'd like to start merging your changes.

I keep it in mind, sorry, I will try to take time this week.
On févr. 25 2019, at 5:21 pm, Ashwin Ramaswami<EMAIL_ADDRESS>wrote:

@pieplu (https://github.com/pieplu) just a reminder to make the PR when you get a chance! I'd like to start merging your changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/mozilla-services/react-jsonschema-form/pull/1158#issuecomment-467207803), or mute the thread (https://github.com/notifications/unsubscribe-auth/ADG_fSaK2-wLBDUI1XNCZCQ6vFDV-1dfks5vRGHygaJpZM4aWR62).

@epicfaace done!
I will make an other PR with CSS className change for easy customisation

@epicfaace Done!

@epicfaace re Done!

Great! It looks good. Thanks for the good work!


items Sheets not displaying updated properties after being enchanted

dnd version : 4.0.2
foundry version : 12.331
0 modules enabled
items Sheets display the properties of the initail item and not the overriden properties given by the enchantment.
Enchantment has :

system.properties and overrides  are correctly set up after enchantement is applied but do not reflect in the weapons properties of the item sheet

note that this work from tsystem perspective :
=> the "Attunement" section appears, meaning that the item is considered magical (and the magical icon shows on the inventory tab of the PC)
=> the Ammunition section is not shown when launching an attack with the enchanted weapon and the "Use Ammunition' section disapparead from the item sheet.

That is intentional at the moment, so the underlying data can still be edited properly. In a future version there is a plan to make more use of the edit toggle on item sheets so in editing mode it will show the underlying values before enchantment, and then in play move it will show the values post-enchantment (but they will be locked).

re: #4833


Installing Mediaconch in Debian 10 (Buster)

What is the roadmap for installation on Debian 10? I've tried creating a Docker image and only get it working in Debian 9:
FROM debian:jessie-slim

RUN apt-get update
RUN apt-get install -y wget apt-transport-https

RUN wget https://mediaarea.net/repo/deb/repo-mediaarea_1.0-9_all.deb
RUN dpkg -i repo-mediaarea_1.0-9_all.deb
RUN apt-get update
RUN apt-get install -y mediaconch

Replacing the first line with FROM debian:buster-slim results in the following error:
Step 6/7 : RUN apt-get update
 ---> Running in 2d399ff71780
Hit:1 http://security-cdn.debian.org/debian-security buster/updates InRelease
Ign:2 https://mediaarea.net/repo/deb/debian testing InRelease
Err:3 https://mediaarea.net/repo/deb/debian testing Release
  404  Not Found [IP: <IP_ADDRESS> 443]
Hit:4 http://cdn-fastly.deb.debian.org/debian buster InRelease
Hit:5 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease
Reading package lists...
E: The repository 'https://mediaarea.net/repo/deb/debian testing Release' does not have a Release file.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100

Perfect, thank you!


Docker for local dev

This dockerizes the API!
What does this mean you ask?
Well it means that instead of having to learn and manage rails, ruby, postgres and assorted dependencies on your machine, you instead need to learn and manage your install of docker. This should hopefully speed up the on-boarding process and make it easier for folks to get to a running environment.
This also adds in a make file. You can read a bit more about the make targets on the readme that was edited in  this commit for details on how to run the different make targets. The things we should be able to do with those are:

Start the API services
Stop the API services
Create and migrate the development DB
Reset the development DB
Run the rspec (unit tests)

Otherwise you can do normal docker stuff to these containers.

 [Voma] Setup docker infrastructure for local dev so that it's easier to get an environment spun up


Error while passing alternative URL to binaryURL (eversdk.wasm)

I'm trying to pass an alternative URL where this URL returns eversdk.wasm file. but I'm getting this error.
what type of URL should I pass here? @melsomino  @cryshado @Artem-Zhdanov

This image from Vercel shows the usage of our bandwidth. within 10 hours it grew by 300+ GB @melsomino @alex-novikov-1990 @ch1seL


Add handle to order item option model

It's good to have a handle on product option, but not having it on order item option means that you can only use the option name to process the options on the submitted orders, which defeats the purpose of having the handles. This PR adds a handle to order item option model and sets it to the handle of the product option.

Took me a little thinking to understand the problem, but I understand it now. Without saving down the handle, there's no way to reliably fetch it again for an order. And having this handle in place means you can do things like look through the options that were selected to find a specific one.
The only thing that appears missing is that I think there should also be a corresponding getOrderItemOptionHandle method.

Added it


How to force List/Grid views?

Hi,
The view setting (List/Grid) seems to be used as global setting, so if I browse categories in List mode, also the thunbnail are browsed in List mode.
Is there a way to force List view in Categories/Index pages and Grid view in Thumbnails pages in the code?
I'm not practical in piwigo programming structure and I was unable to find a way to do it.
(In my case, since I use description in albums but no texts in photos, I'll disable also the change view bottons)
Thanks in advance.

Hi,
any way to force List view in categories/index and Grid view in thumbnails?
Thanks in advance

There is currently no way to set this separately.

Ok thank you anyway.
In case others need to do the same, I describe the workaround I implemented (although not really beautiful) to have this functionality.
I've modified the footer.tpl file, adding at the bottom (just before the  statement) a simple javascript code that runs on page load and triggers (with a little delay) the grid/list view buttons, depending of the presence of the slideshow icon (which appears in Thumbnails page).
    <script type="text/javascript">
        $("document").ready(function() {
            setTimeout(function() {
                document.getElementById('btn-grid').click();
            },10);
        });
    </script>
{else}
    <script type="text/javascript">
        $("document").ready(function() {
            setTimeout(function() {
                document.getElementById('btn-list').click();
            },10);
        });
    </script>
{/if}```

With this workaround, all index and categories pages appears in list view and all thumbnails pages appear in grid view.


gitea dump creates zip with backslashes as path separator

Gitea version (or commit ref): 1.3.3
Git version:
Operating system: Windows 2012 R2
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
When run on Windows the export/backup command gitea.exe dump creates a ZIP archive using backslashes as a path separator. This leads to a flat output on unzipping this archive on a unix system.
Using unzip on unix:
~ % unzip -d gitea gitea-dump-1519632627.zip
Archive:  gitea-dump-1519632627.zip
   creating: gitea/custom/
   creating: gitea/custom\conf/
  inflating: gitea/custom\conf\app.ini
[...]

Shouldn't this be already addressed in this commit? https://github.com/Unknwon/cae/commit/c6aac99ea2cae2ebaf23f26f76b04fe3fcfc9f8c

It seems a dependency's bug?

I don't know. The commit I referenced should already handle backslashes. The vendor.json for 1.3.3 points to this exact commit (https://github.com/Unknwon/cae/commit/c6aac99ea2cae2ebaf23f26f76b04fe3fcfc9f8c, https://github.com/go-gitea/gitea/blob/7b297808cee599f5ff58b9f6afa64d3ee980998e/vendor/vendor.json#L24-L27), gitea-repo.zip inside the dump also uses backslashes.
I worked around the issue by extracting the archive on a Windows machine and zipping it again.

@tobias-- is this still the case?

@6543 I don't know. Unfortunately I do not have a setup at hand to reproduce the issue.


Fix typos

Fix typos

Thanks for the PR @omahs
Will try to merge it asap. Can you update the branch?

@kumaryash90 Hey sure, just updated!


Remote development (over ssh) bug after latest upgrade

We have written the needed data into your clip
Issue Type: Bug

Configure remove ssh vsc server (python code)
Start debugging
Output console don't print some characters (looks like 'r' 'n' 'e')
Normal output "Starting Monitor..."
Current output "Sta ti g Mo ito ...".
But copy from console works fine.
Looks like some console (python debug console) bugs.
I can't check now in local debug console..

VS Code version: Code 1.47.0 (d5e9aa0227e057a60c82568bf31c04730dc15dcd, 2020-07-09T08:02:06.629Z)
OS version: Windows_NT x64 10.0.18363
Remote OS version: Linux x64 4.15.0-109-generic

System Info

Item
Value

CPUs
Intel(R) Celeron(R) CPU N3450 @ 1.10GHz (4 x 1094)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
5.85GB (1.97GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: <IP_ADDRESS>

OS
Linux x64 4.15.0-109-generic

CPUs
Common KVM processor (2 x 2394)

Memory (System)
1.18GB (0.18GB free)

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-language-pack-ru
MS-
1.47.3

python
ms-
2020.6.91350

vscode-language-pack-ru
MS-
1.47.3

remote-containers
ms-
0.128.0

remote-ssh
ms-
0.51.0

remote-ssh-edit
ms-
0.51.0

remote-wsl
ms-
0.44.4

vscode-remote-extensionpack
ms-
0.20.0

HOCON
sab
0.0.1

bootstrap4-vscode
the
6.1.0

board because it was too large to send. Please paste.

Fixed by remote server and VSC restart.


Clean database close attempt

Describe your changes
Added a clean database close in the SQL destructor.
Issue ticket number and link
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I have made corresponding changes to the documentation
[ ] If OCPP 2.0.1: I have updated the OCPP 2.0.1 status document
[ ] I read the contribution documentation and made sure that my changes meet its requirements

Updated to use the new auto-managed interface.

The changes here for the DeviceModelStorageSqlite class seem to have broken our tests. It doesn't seem to work with in-memory databases properly?
Are there changes we need to make to our database setup?

I found the fix. In DatabaseConnection::open_connection() you have the following:
    if (this->database_file_path.string().find(":memory:") == std::string::npos and
        !fs::exists(this->database_file_path.parent_path())) {
        fs::create_directories(this->database_file_path.parent_path());
    }

SQLite has multiple ways to initialize in-memory databases:

If two or more distinct but shareable in-memory databases are needed in a single process, then the mode=memory query parameter can be used with a URI filename to create a named in-memory database:

The code above only checks for :memory: and not mode=memory. We need to use mode=memory to give the device model database a unique name so we don't mangle the device model db and other dbs. So the code needs to look like this:
    if (this->database_file_path.string().find(":memory:") == std::string::npos and
        this->database_file_path.string().find("mode=memory") == std::string::npos and
        !fs::exists(this->database_file_path.parent_path())) {
        fs::create_directories(this->database_file_path.parent_path());
    }

Fix here: https://github.com/EVerest/libocpp/pull/659/files