V2 API

This is expected to be a long running ticket where we can list breaking changes that we want to include in a V2 API. As part of this work, we should plan the new API interface around the key journeys that customers need to use our REST API for to simplify admin integrations.

Add consistent API interface across all Edge endpoints. These should all respond with a consistent schema that follows a well defined framework, e.g. https://jsonapi.org/.

specifically, this will allow us to remove the 'updated at' value from the header of the /flags/ endpoint and into the response body

Look into fixing the typing issues. All dynamically typed fields should be removed and replaced with a combination of a string field and a provided data type.
Replace all references to 'unicode' with 'string'
Create endpoints to manage state of a feature for an environment, identity or segment without needing to make multiple API requests
Prevent updates to FeatureState objects - we should only allow new versions to be created
Remove endpoints reliant on influx data in favour of endpoints that return data from influx or postgres for analytics purposes
Update authentication such that it includes context of the organisation for each request
Remove integration configuration objects from environment-document endpoint
Remove dynatrace configuration from the engine / edge api entirely
Remove need for FeatureSegment

Looks like https://pypi.org/project/djoser/#history is inactive we should consider this in V2 phase

Displaying features
One of the main things that would make writing a frontend more feasible is to reduce the number of API calls needed to display a feature and its information for a particular environment.
Related to https://github.com/Flagsmith/flagsmith/issues/1619:

Given that features are paged, if we wanted to show the number of segment overrides, the endpoints we'd be hitting to show a list of features would be as follows:

Get every page of featurestates for the environment

https://api.flagsmith.com/api/v1/environments/4vfqhypYjcPoGGu8ByrBaj/featurestates/?page_size=20

Get the paged features for the project

https://api.flagsmith.com/api/v1/projects/12/features/?page=1&page_size=200&is_archived=false&sort_field=name&sort_direction=ASC

For each feature in the list, get the "feature-segments"

 https://api.flagsmith.com/api/v1/features/feature-segments/?environment=22&feature=8266

##Ideal solution
Create an endpoint like
https://api.flagsmith.com/api/v1/projects/12/features/?page=1&page_size=200&is_archived=false&sort_field=name&sort_direction=ASC

That returns:
id,
name,
created_date,
description,
owners,
multivariate_options,
is_archived,
default_enabled,
initial_value,
tags,
feature_state?: {
id
enabled
feature_state_value
}

Managing feature segments
Currently, to get the list of segment overrides for a feature the frontend hits:
https://api.flagsmith.com/api/v1/features/feature-segments/?environment=12560&feature=15060

and

Retrieving feature segments
Currently, to get the list of segment overrides for a feature the frontend hits:
https://api.flagsmith.com/api/v1/features/feature-segments/?environment=12560&feature=15060

and
https://api.flagsmith.com/api/v1/features/featurestates/?environment=12560&feature=15060

it then combines valid feature states and joins them to feature-segments.
Ideal solution
Since I imagine we can't break away from "feature-segments", an endpoint like
https://api.flagsmith.com/api/v1/features/feature-segments/?environment=12560&feature=15060

That returns something like
id
priority
segment
segment_name
feature_state

@kyle-ssg this one is already done: https://github.com/Flagsmith/flagsmith/issues/1645

I dont think so, the frontend still has to do what's outlined.

Scheduled Flag Change Customer Requirement:
Create Scheduled Event
In 1 API call, create a scheduled flag change. In X days for Y% of users, set this flag state to Y.
Returns the ID of the scheduled event.
Delete Scheduled Event
With the ID of the scheduled event, remove the event.

Endpoints should not rely on user supplied object level keys for the supplied JSON. For example, SDKAnalyticsFlags in the post method takes in JSON that lists feature names and associated counts. This makes it difficult to add additional data to the post body, so this (any similar) should be replaced with proper API supplied structure.


Change use of * as matmul to UserWarning

Addresses https://github.com/cvxgrp/cvxpy/issues/980#

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for addressing this! @rileyjmurray I thought we added this warning already?

@SteveDiamond  We added a deprecation warning. Turns out deprecation warnings are suppressed by default, and so many users would not see the warning. This PR switches to a UserWarning, which ensures the warning is seen unless explicitly suppressed.

The CI builds show this works as expected. Thanks @juesato!


Document pre-requisite initialization of coordinates

The layout fails whenever x and y attributes are not set in the input graph.
As a result, layout returns x:NaN, y: NaN for all the nodes.
This change initializes coordinates to 0 whenever they are not already defined in the graph.

cancelling the pull request: this does not seem to be working, will resubmit a pull request whenever the problem is actually fixed.

Hello @mef. This behavior is "normal". I am not sure that this library should choose a random or circular or whatever layout if the user failed to do so before applying FA2. What's more, you can use graphology-layout for that. This said, I agree the matter can be a bit puzzling to a first user. So my proposition is:

We could improve the docs to clearly state that the graph must have starting positions for the nodes and point towards the relevant layouts initializers.
The various lib functions could throw a helpful error if we find some nodes missing positions.

Thanks for the reply.
I have just undone the change and documented the constraint in README, does it look good to you?
I would rather not modify the lib to throw, as the extra checks might affect the performance (your call, though).

Thanks @mef. Merging right now.


RAD-4162 Sync file download for unit test validation

Description
Fix for flaky tests that requires validating downloaded file content

Looks correct to me @MertCingoz
Any reason its not ready for review?

It is ready, we were about to move npm organization from https://www.npmjs.com/org/infinite-automation  to https://www.npmjs.com/org/radixiot. Since you are the only one can access and release npm packages right now.

Since you are the only one can access and release npm packages right now.

@terrypacker has access too. But yes we should move it to a new org.

@jazdw I couldn't get it as it uses my old IAS email address.  I will make a note to see if I can fix that or maybe just open new account for Radix?

I invited your Radix email address to the infinite-automation org.

FYI the radixiot org already exists, but I am not an owner.
https://www.npmjs.com/package/@radixiot/react-cache-buster


Store annotations within the node they annotate

From https://github.com/crystal-lang/crystal/issues/9322#issuecomment-859676500:
@[Bar]
def foo
end

Is currently parsed as:
Expressions.new([
  Annotation.new(Path.new(["Bar"])),
  Def.new("foo", [] of Arg),
] of ASTNode)

@straight-shoota suggested changing this in https://github.com/crystal-lang/crystal/issues/9322#issuecomment-862129869 such that the annotation in this example would be stored within the Def node itself. Similar to how https://github.com/crystal-lang/crystal/pull/12044 handled it for method/macro parameters. Which makes a lot more sense to me as well.
From an implementation perspective it's a bit tricky since unlike annotated parameters we do not necessarily know what specific node we're parsing until after the annotations have already been parsed. The best way I could think of is keeping track of the Annotation nodes within the parser itself, then apply them to an applicable node once we determine what it is, then clear the annotations array to prepare it for the next method/type/what have you.
Backwards compatibility also came up, which seems to suggest we would want to keep both APIs, meaning like we'd still represent the annotations as an Expressions, but also store a copy of them within the Def?

So this may actually be a bit trickier than I thought. I got a prototype mostly working, however I'm unsure how to go about handling this:
@[Link("pcre2-8", pkg_config: "libpcre2-8")]
{% if compare_versions(Crystal::VERSION, "1.11.0-dev") >= 0 %}
  @[Link(dll: "pcre2-8.dll")]
{% end %}
lib LibPCRE2
end

$ ccrystal run --prelude=empty test.cr
name        # => LibPCRE2
annotations # => [@[Link("pcre2-8", pkg_config: "libpcre2-8")]]
...

It seems we can't actually do this purely in the parser due to macro code like this not yet being evaluated to allow adding the second Link annotation to the LibDef node directly. The current implementation works I guess because by the time the semantic visitor runs, the macro has expanded which results in def visit(node : Annotation) being called twice properly populating @annotations with both. Whereas the ones I parsed directly and added to the LibDef only has the first one.

Maybe the current implementation is actually best then. It all happens in TopLevelVisitor: macro expressions are expanded and annotations are collected and attached to the following node.

Yea, probably just going to shelve this for now in that case. Given there isn't a use case, yet at least, that really requires this refactor.


Remove Endpoints - auth

User Story - Business Need

In the effort to clean up our code we need to investigate and remove unused endpoints. This ticket is to take a look at the endpoints under /auth/ and remove the ones marked for removal. You can view the table of endpoints here.
User Story(ies)
As an engineer
I want to clean up and reduce our codebase
So that it is easier to maintain and upgrade in the future.
Additional Info and Resources

Endpoint Table
Endpoint Spreadsheet

Engineering Checklist

[ ] Investigate the endpoints starting with /auth/ to make sure they aren't being used
[ ] Remove tests associate with those endpoints
[ ] Remove the code associated with those endpoints (if possible). Make sure not to remove any code used by other parts of the application.

Acceptance Criteria

When the designated code and tests have been removed, the application retains full functionality.

QA Considerations

[ ] The QA Regression Suite passes
[ ] The Cypress regression passes

Potential Dependencies

Make sure the removal of these endpoints doesn't affect the work Strike is doing.

Closing/no longer relevant.


Added 'What you can expect from Maintainers' doc

This document is a new contributing document that describes what contributors can expect from maintainers (hence the title).
I am using this PR to gather feedback on the proposed content, both the content itself and the more general engagement between contributors and maintainers that it describes.
At a minimum, this PR will be held open for 1 week before merging. If feedback suggests otherwise, a different course of action will be taken.
I wrote this document and have gotten initial feedback from a small set of maintainers and contributors.

Can this be merged now?


Text corrupted on C# supported lastest version

Tested versions
4.2.2 stable c# support
System information
Windows 11 - Godot.v4.2.2.stable
Issue description
Due a configuration to use external editor visual studio.ink acces direct on windows 11 all text of godot get corrupted and it doesn't read well.
I add a picture of the bug:

Steps to reproduce
create a .cs script, then try to change the highlight text form godotscript to c# on text editor in godot, then go to preferences and activate external editor and select the .ink of visual studio community 2022. Finally close and open godot proyect.
Minimal reproduction project (MRP)
godot proyect.zip

This looks like the messages used in pseudolocalization. Check if pseudolocalization is enabled in Editor Settings:

Indeed, this isn't a bug, but a debug feature, which you seem to have enabled inadvertently.
Closing as it's not a bug - but we'll remove the feature anyway as several users seem to have had issues with it over the years, and the feature isn't used much.


[Storage] Fix #28603: az storage blob set-tier-batch/delete-batch: Add batch support to set-tier, add --blobs and --tags-condition for delete-batch

Related command

Description

[Storage] az storage blob set-tier-batch/delete-batch: Add batch support to set-tier, support --blobs for delete-batch
Fix #28603, support --tags-condition for delete-batch
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

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

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage

i see the pr is now targeting backlog, so no milestone, is there any estimate this will be implemented?

i see the pr is now targeting backlog, so no milestone, is there any estimate this will be implemented?

currently waiting for Azure PowerShell .NET SDK dependency fix, so both client tools can release together, thanks.


Scan only open files

I would like the extension to show suggestions only for open files.
Currently, the suggestions appear as soon as I open a file, but when I close it they remain in the "Problems" tab.
If possible, I would like them to automatically go away when I close the file to avoid clutter.

Hi - thanks for the suggestion.
We're going to be working on the UX in the next few weeks so will definitely consider this for inclusion.

That's great news, thank you very much.
I am looking forward to seeing this feature added.

This has now been added in as a feature in the latest extension version.


question: lock node engine to >= v6.x?

I see that CircleCI uses node 6.4, and package.json engine is >=5.11.
How do you feel about locking the node engine to >= 6.4.0 in package.json and .circle.yml?
We recently switched to 6.5.0 at my work and haven't had any issues.

Sweet! I'll create a PR. 6.4 or 6.5?

6.5 please

PR #98 submitted :)


WebWindow Size & Positioning

Please consider adding support for changing/setting height/width and top/left of the WebWindow as well as z-ordering of the WebWindow.
It would also IMHO be good to have support for multi-monitor so to open WebWindow on a given monitor

This was implemented in #31
(Not the multi-monitor part though)


Issue in printing invoice in transaction page

Describe the bug

Quantity is not calculated in total amount
When showing amount calculation there is some text in capital and some are camel case
When we print there is one extra white page in printing
Pay button not working

Screenshots
If applicable, add screenshots to help explain your problem.

text in capital and some are camel case in client Entry


ag cannot find accent letters

Version: windows port 0.29.1-1641 (built on 2015-07-04)
System: windows 7 pro, language français
Issue: Ag cannot find french accent letter, such as ô, é, è, ç, à, etc.

Bonjour,
Having the same problem, I've just done another port of ag for Windows that can find non-ASCII characters... But so far only in text files encoded as UTF-8.
Also, it will find files that have non-ASCII characters in their pathname.
The sources are there: https://github.com/JFLarvoire/the_silver_searcher
If you don't have Visual C++ for rebuilding it, I've uploaded pre-built versions in: http://jf.larvoire.free.fr/temp/ag.zip
Eventually, I plan to add a dynamic detection of the encoding (ANSI/UTF-8/Unicode), to allow finding non-ASCII characters in any kind of text file.
Jean-François

This should be an issue for Windows port author.  If it was ag issue, it has been fixed already:
 % ag ô /tmp/ag.txt
1:ô, é, è, ç, à

(Linux amd64)

Yes, this was indeed a problem in previous Windows ports, not in Unix builds.
I've released a few days ago a new version 2.0.0 for Windows with full support for this at last:
https://github.com/JFLarvoire/the_silver_searcher/releases
As proposed in my previous post above, it dynamically detects the encoding, and can search both in files encoded in UTF-8 and in the Windows System code Page (CP 1252 for west-european versions of Windows).
And whatever the file encoding, and whatever the current console code page, the strings found will be displayed correctly.


Missing throws doc block

This gonna improve code quality for library users

https://github.com/stephen-hill/base58php/pull/25

I merged this into the php8.0 branch.


Leaving ffmpeg and vlc running after stream closed

Please first read the documentation. Problems affecting the client, e.g. Plex or Emby should be reported there in the forum.
Describe the bug
xTeVe is leaving ffmpeg and vlc running when a stream fails from the server-side.
Server (please complete the following information):

Linux - PhotonOS with ubunto docker container
Intel 64 Bit
2.1.2 Build: 0121

To Reproduce
Steps to reproduce the behavior:

Watch a stream that is proxied by xTeVe
Allow the stream to fail from the provider end
See the new process start to restart the stream
See the old process remain

Expected behavior
The failed stream's ffmeg or vlc process should exit
Screenshots
root      1193  0.1  0.1  79000 23396 ?        S    01:54   0:16 /usr/bin/ffmpeg -user_agent xTeVe -hide_banner -loglevel info -i http://example.com:80/dir/key/3907 -codec copy -f mpegts pipe:1
root      1275  0.2  0.1  68884 23008 ?        S    02:20   0:19 /usr/bin/ffmpeg -user_agent xTeVe -hide_banner -loglevel info -i http://example.com:80/dir/key/3527 -codec copy -f mpegts pipe:1
root      1276  0.1  0.1  67056 22044 ?        S    02:20   0:15 /usr/bin/ffmpeg -user_agent xTeVe -hide_banner -loglevel info -i http://example.com:80/dir/key/3907 -codec copy -f mpegts pipe:1
root      1325  0.3  0.1  78408 23284 ?        S    02:51   0:27 /usr/bin/ffmpeg -user_agent xTeVe -hide_banner -loglevel info -i http://example.com:80/dir/key/3527 -codec copy -f mpegts pipe:1
root      1329  0.2  0.1  65036 20136 ?        S    03:00   0:15 /usr/bin/ffmpeg -user_agent xTeVe -hide_banner -loglevel info -i http://example.com:80/dir/key/3907 -codec copy -f mpegts pipe:1

Additional context
NA

If you use FFmpeg or VLC, xTeVe is not involved with the network connection to the provider. As long as the provider sends data to FFmpeg / VLC, the process is not terminated. Only the connection between Clinet and xTeVe can be monitored, if the last client ends a stream from xTeVe, the FFmpeg / VLC process is also ended.
Provider --> FFmpeg / VLC --> xTeVe <--> Client


Add support for message fields: "allowedMentions" and "flags"

This PR adds support to new message fields that are included in Discord docs:

allowedMentions - allows to set up what mentions can be used in message that is sent by webhook - it's useful when someone would want to pass through user generated text to webhook message and doesn't want to allow mentions in it.
flags - there are only two flags supported, but are useful as well.

It appears that your other PR created a merge conflict. Can you fix it and create some unit tests? Thanks!


Fix broken links in download commands in spaceflights tutorial

Description
The current spaceflights tutorial has broken links in the download commands. This patch fixes that and solves #623.
Checklist

[x] Read the contributing guidelines
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change and added my name to the list of supporting contributions in the RELEASE.md file
[ ] Added tests to cover my changes

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

✅  All good, thanks a lot @guludo !! Hope to see you again around here soon!


Closure stylesheets

Use closure-stylesheets
Use closure-stylesheets with basic error reporting
Use closure-stylesheets with improved error reporting
Enable source map generation for JS
Enable renaming files to .min
Add tests for error handling
Add comment for empty method
Rename "renameToMin" to "originalFileNames" and default to true
Enable source map generation for JS

Do you release this?

I will make this 1.4.0


Push staging.

LGTM, but it looks like your commits came from another account? It looks like it's you, though, so I don't care.


upgrading influxdb from 1.0.0 to 1.0.2

looking for documentation on how to upgrade influxdb (and kapacitor) from v1.0.0 to v1.0.2 on centos7
can anyone share his experience with the new versions, any problems?

Hello @nirpodo, support questions should go to the mailing list instead of the issue tracker. Thanks!


investigate using fix-path

fix-path may be able to make the path work when Atom is launched as an app. It won't fix problems with node-gyp during installation or update, though.

The one thing I'd want to be sure of is that fix-path won't override what's currently in the path (if someone is being explicit).

Per my comment in #34, I think this is going to lead to bugs down the road and should be corrected in Atom instead.


Triage old issues in this repository

Context
This repository has 388 open issues right now. Many of these are stale, out of date or not actionable. Having this many open issues makes it hard to have a realistic backlog, especially given many of these are stale. It takes constant triaging and grooming to keep our list of open issues manageable. But before that, we need to have a round of going through and cleaning up existing issues. This is difficult work!
Proposal
I propose we go through all the open issues, and take one of the following actions:

Close as completed - something we have done already, let's celebrate, mark as done.
Close as duplicated - link to another issue (in the same or different repository) tracking the same thing, and mark as closed. Prefer leaving open the issue that has had the most useful activity.
Close as no longer relevant - due to decisions made since the last activity on this issue, it is no longer relevant. Write a short comment stating this, and close. Can be re-opened if someone disagrees.
Copy into ProductBoard as a feature request insight - if this is a feature request, copy it into the appropriate productboard feature as an insight, and link back to the ticket before closing.
Close as not planned - Some things are just not going to be things we're going to be able to do in the near or medium future. We thank the issue for giving us ideas, and close them. They can be re-opened if necessary.
Describe action items in the issue body - if this issue should continue to stay here, it must have an Action Items section in the issue body, with an active list of things that must be done to close the issue. This can be time consuming, but worth it for keeping the issue list manageable.

Updates and actions
No response

I would like to do a 4h round on this as a first pass, but it'll have to be put through our sprint planning system.

Should a similar review should be made of our other repositories as well?
As a I scroll through infrastructure I see some issue which I recognize as being duplicates of ideas captured elsewhere. Please let me know if joining co-working session to triage these old issues would be helpful.

I've updated (4) (feature request) to incorporate product board.

I've started doing this on and off, moving things into productboard as appropriate.

Issue tracking making productboard more publicly visible at https://github.com/2i2c-org/meta/issues/900

I've converted this into an epic, and split https://github.com/2i2c-org/infrastructure/issues/3789 off into its own subtask.


gamemode: init at 1.4

Motivation for this change
GameMode is a pretty popular package. It requires a daemon as well, which I have not written a NixOS module for due to a lack of experience. If necessary, I can add it to this or a separate PR.
Things done

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

Had issues with it while reinstalling NixOS, so disabled it

Built on platform(s)

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

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

I've got a similar package I've been working on.  There's a few more patches I've added in prep for a NixOS module to add the daemon; in particular, setting the default config file location (/usr/share/gamemode won't exist in a running NixOS), fixing the dlopen call, and fixing the polkit calls.  I don't have the LD_LIBRARY changes you do, so maybe the second two changes I've made are redundant.  If you're OK with this sitting for a day (work's busy atm), I can push you the config file patch?
Also -- some games that can be run with this are still 32-bit, so I tried to get a multiarch build going but eventually had to give up.  Have you looked into that at all?

For reference: https://gist.github.com/frio/03a2731903bf40ae0c11b2c99a24dedf.  I've got no further input, I'm really happy to see this and would be happy to put together a module when merged :).

Fixes: #84682

I would love to see this merged! @leo60228 are you still willing to maintain this? The suggestions in this PR haven't been resolved and this has been stale for a while now.
I'd be willing to start a new PR on v1.6.1 with a NixOS module.

I've mostly lost interest in this package. It'd be great if you were willing to make a new PR, though!

I've created a new PR for GameMode here: https://github.com/NixOS/nixpkgs/pull/123433 :slightly_smiling_face:


ProcessInfo.processInfo.environment doesn't work in Package.swift

Hello!
If Package.swift contains a condition on a environment variable like in grpc:
ProcessInfo.processInfo.environment["GRPC_NO_NIO_SSL"] == nil .appending(   .package(     url: "https://github.com/apple/swift-nio-ssl.git",     from: "2.14.0"   ),   if: includeNIOSSL )
If build or just update through terminal - works great (no swift-nio-ssl):

But when open Xcode - it adding swift-nio-ssl, seems to work only through the terminal:

I've added GRPC_NO_NIO_SSL=1 to ~/.zshenv, ~/.zprofile and to ~/.bash_profile
echo 'export GRPC_NO_NIO_SSL=1' >> ~/.zshenv
source ~/.zshenv

env and printenv contains this variable.
Maybe need to add something differently so that xcode see it?

Unfortunately there isn't currently a way to convey external parameters like this to package manifests.  I think what Boris said will work, but is a bit subtle.  xcodebuild, being a command line tool, will also see any environment variables set in the environment in which it's invoked.


Xib2Nib.exe failure should not be fatal

Unable to find class mapping for required object
C:\WinObjC\msvc\sbresources.targets(174,5): error MSB3073: The command ""C:\WinObjC\msvc..\bin\Xib2Nib.exe" "....\Resources\Base.lproj\DebugDialog.xib" "Debug\Base.lproj\DebugDialog.nib"" exited with code -1.
I realize this is nearly a duplicate of #367 but it would be more useful if I got a runtime crash instead of being able to see how well the bridge works for all the other views in my app. (Probably poorly because I also use UIStackView, but I'd love to see something show up to know if it’s worth continuing down the WinObjC path.)

Thank you for the feedback. Would you be able to share the list of controls you're using in your xib files and storyboard and we can tell you which one will cause problem with Xib2Nib? We did "stub" some of the unsupported control in Xib2Nib to avoid this but we did not do that for all of them.

Oops, I didn't realize that GitHub didn't show the actual class: it's UIVisualEffectView. I don't have a great way to catalog the UIKit classes I use, especially since I don't even know how to exclude this from the build to get to the next error.

I wonder if this was an Interface Builder bug?
                        <label opaque="NO" userInteractionEnabled="NO" contentMode="left" horizontalHuggingPriority="251" verticalHuggingPriority="251" text="Sacred Time" lineBreakMode="tailTruncation" baselineAdjustment="alignBaselines" adjustsFontSizeToFit="NO" translatesAutoresizingMaskIntoConstraints="NO" id="ijC-2a-i2C" customClass="SmallCapsLabel">
                            <rect key="frame" x="0.0" y="0.0" width="96.5" height="20.5"/>
                            <fontDescription key="fontDescription" type="system" pointSize="17"/>
                            <color key="textColor" red="0.0" green="0.0" blue="0.0" alpha="1" colorSpace="custom" customColorSpace="sRGB"/>
                            <nil key="highlightedColor"/>
                        </label>

I manually removed any <nil …> lines and proceeded.


MINOR: mention KAFKA-15905 in docs "Notable changes in 3.7.1"

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

As discussed in https://github.com/apache/kafka/pull/15910#issuecomment-2127588361

cherry-picked on 3.7
thanks @gharris1727


Get body of POST request

Hi!
In the examples, I did not find examples of get params of the POST request.
Found example in the repository of the project that uses your framework.
request.body
But it is not available from TypeScript.

Error in index.d.ts? Maybe it's worth adding body?: Record<string, string>?
https://github.com/jkyberneees/ana/blob/d271aacb07b13c963501ff6620396d38866120ce/index.d.ts#L27-L30
Or am I doing something wrong? :)
Thanks!
upd:
I've checked - there the parameters of the POST request actually passed (casted as (request as unknown as Record<string, string>))

Hi @vladislav805, thanks for reporting. I kindly ask you to review my proposed solution here: https://github.com/jkyberneees/ana/pull/75
Thanks

@jkyberneees, thanks for answering.
I would instead { [prop: string]: Body } write as Record<string, Body>. But this is just my opinion. To be honest, I don’t know how to be right. This looks like probably be so.
Logically, here can be not only JSON, but also just an object with urlencoded.

Hi @vladislav805 thanks for your input. I think body does not always will be an object. For example, the body-parser middleware is one of the most used libraries for this, multiple types are supported: https://github.com/expressjs/body-parser
Will merge and release. Thanks

Okay, thanks!


Add technical documentation about task model

I thought it would be useful to document the task model put into writing the assumptions we make about tasks and slots.
I'm not entirely sure where this document belongs and I'm open to suggestions.
Note that this preemptively covers rolling updates which start the new task before stopping the old one, a feature added in #1383 (not merged yet).
ping @aluzzardi @stevvooe @sfsmithcha @dongluochen

Current coverage is 55.12% (diff: 100%)

No coverage report found for master at 6890aff.

Powered by Codecov. Last update 6890aff...4f656f1

Went through all of it and nicely done on the in-depth explanation. Couldn't even find a typo :)
I wonder if this makes sense to put this on the Docker documentation as well? Or just a subset to understand the big picture. It's very useful imho.
LGTM

LGTM, good explanation. Will probably revisit it regularly.

LGTM
@sfsmithcha @mgoelzer Do we want to have some kind of "architecture documentation" somewhere in the docs? Or should this just live in this repo for now until we define a process?

This can probably go inside of a directory named design, along with nomenclature.

Moved to design, along with nomenclature.md.

LGTM


Add support for string based footnotes

I usually name my footnotes like [^footnote], but this plugins doesn't support it.
Could you consider adding it? 😃

👋 @elboletaire. This plugin is no longer maintained, I recommend you to use hexo-renderer-markdown-it which supports footnotes and many more features.


[Partner] Prevent requesting new items for Partners with diaper_base_status='deactivated'

Summary
We don't want deactivated Partners to continue having access to the partner application. Let's restrict access to Partner with diaper_base_stauts='deactivated'
** Note - One way to achieve this possibly is to modify authorization logic on the controller level**
Update.
After talking with @seanmarcia , it might be a better idea not to unauthorized or prevent access to the dashboard for partners. Instead, let's prevent their ability to request items from the diaper bank.
When the diaper_base_status='deactivated' replace the UI for requesting items with a message that says they've been deactivated and if they want to regain access email the organization.
Blockers
#1600
Criteria Of Completion

When a deactivated partner access the request items page, it does not show the UI for requesting items but instead a message that says they've been deactivated and they need to contact the organization via their email to reactivate
When a non-deactivated partner access the request items page, they can request items

I am going to close this issue and move this to the repo that the change is expected in. Had a bit of confusion from https://github.com/rubyforgood/diaper/issues/1600.
Moved this issue to the right repo here - https://github.com/rubyforgood/partner/issues/308


Event for just clicking a day / time? Detecting Click without Dragging

Version 2.1.3

Test Environment

Windows 10, newest Chrome Browser
Current Behavior

I cant find an event which is fired, when a day / time is just clicked by the user and not "dragged" which in my opinion would be quite important since not everyone always wants to create an for example multi day event.
Does such an event exist / is there any workaround?
Expected Behavior

It would be best if there would be an event triggered just by clicking some time / day on the calendar view

@Bxnnet
Do you mean this event?
https://github.com/nhn/tui.calendar/blob/main/docs/en/apis/calendar.md#clickevent

hey @adhrinae
thanks but thats not what im looking for. This one is fired when an event is clicked, I want an event which is fired when I click on the date for example 22.09 in the calendar view in order to create a new event. You get me?

@Bxnnet
I see. the selectDateTime event fires even if you click a date or time, not dragging.
https://github.com/nhn/tui.calendar/blob/main/docs/en/apis/calendar.md#selectdatetime
I wonder how you set the calendar to fire the event and which event you tried. Any sample code reproducing the problem would be helpful.

There is currently just the code loading the calendar and adding some events. For me the selectDateTime just fires when I drag trough any day oder time and not just when clicking a day.
To understand better: I now print 'hi' on
calendar.on('selectDateTime', ({event}) => {
                console.log('hi');
            })

which works fine when dragging.

But without dragging, no hi appears :(

@Bxnnet
I'm not sure what the cause is because I'm not aware of your app's structure and what options you gave to the calendar. That is why I asked you for a sample code reproducing the problem. Not just what you did.
Here's a simple example tried to reproduce the problem. But It works fine.
https://user-images.githubusercontent.com/14539203/191868363-bbf01abf-f5fb-48c8-b1ef-e2c9575647cc.mov

@adhrinae nevermind your video gave me the hint I needed. It seems like I initialized the calendar in an invalid way and now every thing works finde!
Thank you so much for your help and patience!
Have a nice weekend mate


render_boolean template filter implementation

Fixes: #803

Also please document this filter in nautobot/docs/additional-features/template-filters.md. Thanks! :-)


Local protocol support based on node-mihome

Hi
Could you add local miIO protocol support by storing the token in the node and then being able to send or request a payload? Eg similar to https://flows.nodered.org/node/node-red-contrib-xiaomi-miio
To support the project I would be happy to donate 50$ for this together with a node and an example for sending a command to and requesting data from the airpurifier Xiaomi Air 3H (zhimi.airpurifier.mb3) which is also supported by node-mihome.
I believe your module would then become the defacto standard for node-red and miIO devices.
Cheers,
Adrian

I'm currently implementing a node with the feature myself, so its no longer required.


Gate library and example for synqs singlequdit backend

This allows for using our singlequdit backend.

Hi Rohid,
this looks pretty cool, nice to see the experimental data reproduced.
A few comments:

I'm not sure whether this repo is the right place for the spin demo notebook, as it requires access to your own simulator backend. Right now you are disclosing username and password to this, is this intended?
If we want to put this as a tutorial here, maybe it would make senses to instead call the spin simulator backend already included in the repo.
TheRLXGate, RLZGate, RLZ2Gate gates look pretty much like duplicates of some of the gates already defined in the spin_gate_library, no? I think you should be able to use these rather than having to create your own gate library.
The load instruction is indeed something which needs to be added. I would suggest just adding this to the existing spin gate library.

@LaurinFischer concerning your suggestion with spin demo notebook. This means that it would be more 'proper' to build a package for all synqs devices/simulators that basically builds up on qiskit-cold-atom as an external dependency ? Same would hold for anyone else that would like to expose his back-ends ?

I think that this PR is not required anymore as it was already implemented in #17


File dependencies

A decision was made early on in the project to aim for 1-to-1 compilation targets. This massively simplified the codebase, with the caveat that we wont play well with compilers such as less, sass, typescript, etc, that produce a single file from one or more files.
Personally, I'm hesitant to pursue this with any speed, but it would be quite useful in a lot of the projects that we maintain, so it's definitely worth at least an investigation.

This would probably require something like:

during tracing, identify each file dependency
start watching those files
when those files change, retrace the record(s) that depend on them

When retracing records, we'll need to persist the record -> file connections, so that we can detect changes during compilation. Once the retrace completes, the connections should be replaced with the new ones.

From a perf/convenience perspective, we'll probably want to maintain by-directional maps, so that we can trivially associate file dependencies to records, and vice-versa.

One thing to consider is that perhaps we should use this as an opportunity to refactor all the watching so that it only uses file dependencies. In effect, every record should have its file as a file dependency. So, when we're tracing records, we'd ask for the file dependencies and the resolved deps.
Prob want to ask for file deps first so that we can get fast change detection.

An open, and potentially difficult question, is how this interacts with caching.
First of, we'll need to generate cache keys that reflect all file dependencies. This could be implemented trivially, but would probably be a perf issue once a record has multiple file deps.

My instinct suggests that we'll probably want one (or both) of:

another graph
another record store

A second graph:

would increase the code complexity (although our interactions would be much more limited)
would enable us to encapsulate the by-directional lookups, so invalidation would be performant
would enable us to encapsulate the graph structure manipulation as file deps are added or removed

A second record store:

would enable us to memoize each dep's data, but may create problems with invalidations...?
doesn't necessary expose the lookup maps

Another big issue, this will probably end up breaking the per-file boundaries that we've established for jobs. Admittedly, only for generating the cache key. Still, it will violate a key principle that's kept the record store incredibly simple.

Need some hacky prototypes so that we can try out solutions and find the simplest one. I'm happy to sacrifice lookup maps if it keeps state management simple. Best to aim for simple and leave perf concerns for when it becomes an issue.


load shaders from separate files

Shader code (GLSL) is now part of the html files. This should be in external files.

solved Aug 5, 2015


Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.
Location: None
Error type: An existing branch is blocking Renovate
Message: Renovate needs to create the branch "renovate/configure" but is blocked from doing so because of an existing branch called "renovate". Please remove it so that Renovate can proceed.

fixed


nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified

I'm trying to compile Faster R-CNN, but when I execute make in $Fast_root$/lib, I got an issue
nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
followed with
g++: error: roi_pooling_op.cu.o: No such file or directory
g++: error: GOOGLE_CUDA=1: No such file or directory
I have already added /usr/local/cuda-9.0/bin to PATH, and nvcc --version tells me Cuda compilation tools, release 9.0, V9.0.176
anyone help me?

Have you dealed with this? I have the same problem!

你好想问下　这个问题如何解决的，我也遇到了这样的问题


Does coretweaks is work on server today? or not

It should. (If it doesn't, that's a bug and you should report it!)

ok


Move SDK interface+mock from public pkg dir -> internal

Move SDK interface+mock submodule (internal code) from public pkg->internal dir.
Update imports for move.

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is 20%.

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   61.49%   61.49%
=======================================
  Files          10       10
  Lines         883      883
=======================================
  Hits          543      543
  Misses        290      290
  Partials       50       50

Impacted Files
Coverage Δ

pkg/stub/secrets.go
100% <ø> (ø)
:arrow_up:

pkg/stub/pvc.go
36.23% <0%> (ø)
:arrow_up:

pkg/stub/handler.go
50% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[share_plus] sharePositionOrigin PlatformException on iPad

Platform
iPad13,6
Plugin
share_plus
Version
6.3.1
Flutter SDK
3.7.5
Steps to reproduce
Unsure exactly how to reproduce, but we're seeing this error rarely in production on iPad:
PlatformException: PlatformException(error, sharePositionOrigin: argument must be set, {{0, 0}, {0, 0}} must be non-zero and within coordinate space of source view: {{0, 0}, {834, 1194}}, null, null)
  File "message_codecs.dart", line 653, in StandardMethodCodec.decodeEnvelope
  File "platform_channel.dart", line 315, in MethodChannel._invokeMethod
  File "<asynchronous suspension>"
  File "method_channel_share.dart", line 134, in MethodChannelShare.shareFilesWithResult

The triggering code:
await Share.shareXFiles(<XFile>[XFile(path)]);
The referenced file is a screenshot generated by https://pub.dev/packages/screenshot - so maybe it's empty and that's unhandled by share_plus?
Same issue is seen here: https://www.cloverfield.co.jp/2023/01/26/flutter　share-sharefiles-deprecated　sharexfilesエラー/?doing_wp_cron=1679592278.2726008892059326171875
Code Sample
      Uint8List imageData = await ScreenshotController().captureFromWidget(
        widget,
        context: context,
        pixelRatio: 2,
      );

      Directory directory = await getApplicationDocumentsDirectory();

      String path = '${directory.path}/image.png';

      await XFile.fromData(imageData).saveTo(path);

      await Share.shareXFiles(<XFile>[XFile(path)]);

Logs
n/a

Flutter Doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.5, on macOS 13.2.1 22D68 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.76.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

Checklist before submitting a bug

[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

maybe you need add sharePositionOrigin in iPad. example.

@jingluoguo Perhaps, but it works >99.9% of the time without it, so I assume share_plus is handling it correctly but missing some edge case.

@stx share_plus requires iPad users to provide the sharePositionOrigin parameter.
Without it, share_plus will not work on iPads and may cause a crash or letting the UI not responding.

@jingluoguo Ah, I see now in the readme! Thank you.

I have solved it with


Explicitely fail content length fetch in case of error

Fetching artifacts is done in two steps:

use a HEAD request to get size of the remote object
allocate needed space on disk (by eventually removing old cached data)
fetch artifact
validate size of fetched artifact and adapt cache behavior if there is no match (but it's outside the scope of this PR)

The issue takes place if the remote server does not answer properly to HEAD request (ie a 404 or a 500), the current code will return the size of the 404 or 500 page as if it was the size of the artifact.
There is no "real" issue now that #414 is merged, but there could still be some rare issues if the artifact is significantly larger and available cache is too small (Mesos would write more on disk than configured for its cache).
This patch will make Mesos fail sooner if HEAD request fails, but most of the time this is not an issue as the second request (GET) will fail too anyway.

@cf-natali @qianzhangxa  can u help here?

@cf-natali for me it looks fine and with the response code handling more "nice" then before. :+1:

Hey,
I need to think about this a bit ore, I'm a bit concerned about the potential non backward-compatibility.

May I asked where you see potential backward compatibility problems?

One possibility is the server returning the correct Content-Length, but returning a non-200 status.
It'd be a bit weird but who knows.
Also, as explained by @Lqp1, the following GET will fail anyway in case of error - and generally relying on HEAD/Content-Length is fragile since it's not atomic: the file could be modified between the HEAD and the GET.
So given the risk of breakage, and the limited impact since the downstream problem has been fixed, I'd be tempted to ignore.

Ok, I understand. More risk then we can win makes also no sense for me. But in these case, I think we should close these PR. :-)

Hello :)
Thanks for your feedback.

the file could be modified between the HEAD and the GET.

Just FYI, we are now running this patch in production, without any issue so far.

Yes - I'm sure it works as intended in your environment, the problem is guaranteeing it will won't regress anywhere :).
I'm closing, but thanks for the contribution!


Fixed REST API height always behind by 1

What current issue(s) does this address, or what feature is it adding?
The REST API height is always behind by 1 as returned by /status.
How did you solve this problem?
Added 1 to the return value for consistency with the height checks everywhere else (including in JSON-RPC and other REST API endpoints)
How did you make sure your solution works?
Tested that it always returns the same value as JSON-RPC now.
Are there any special changes in the code that we should be aware of?
No.
Please check the following, if applicable:

[ ] Did you add any tests?
[X] Did you run make lint?
[X] Did you run make test?
[X] Are you making a PR to a feature branch or development rather than master?
[X] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage remained the same at 79.753% when pulling 542e7dcb8f1154a9e158756cb1441f7f8d68dcbb on brianlenz:fix-rest-api-height into 88e33a607c6d4b161cb0321539794600b1f0e586 on CityOfZion:development.


proposal for more flexibility in URL based versioning

situation
As stated in the docs, and verifiable in the code:

If a particular route is a child route, the chain will happen at the top-most ancestor.

Also, the version segment is always prepended to the route.
request
I would like to have an option to get the version segment appended instead of prepended.
And to have it applicable to a child route.
This way I could keep my route configuration nested. And I wouldn't have to specify an uri configuration key for each resource.
example case
Desired route: /module-name/api/v1/some-resource/1234
'zf-versioning' => array(
    'append_version_segment' => true,
    'allow_child_routes' => true,
    'uri' => array(
        'vendor.module/api',
    ),
),
'router'=> array('routes' => array(
	'vendor.module' => array(
		'type' => 'literal',
		'options' => array(
			'route' => '/module-name',
			'defaults' => array(
				'controller' => __NAMESPACE__ . '\Controller\Foo', // for a web UI
			)
		),
		'child_routes' => array(
			'api' => array(
				'type' => 'Segment',
				'options' => array(
					'route' => '/api'
				),
				'child_routes' => array(
					'delivery-method' => array(
						'type' => 'Segment',
						'options' => array(
							'route' => '/some-resource[/:id]',
							'defaults' => array(
								'controller' => __NAMESPACE__ . '\Api\V1\SomeResourceController',
							),
						),
					),
				),
			),
		),
	),
)),

discussion
Do you think this is useful and makes sense? I would be happy to code it.

Honestly, URI-based versioning is an anti-pattern. The only reasons we support it out-of-the-box are:

mediatype versioning is difficult for many to pick up in order to consume out-of-the-box (we are trying to deal with this via education)
some HTTP clients are broken and do not allow specifying headers easily (for this, we recommend using better HTTP clients).

Appending the version segment is terrible; the last item in the URI path should be the resource you are fetching, not metadata.
#9 will let you do it, and I'll likely merge it as I like the idea of being able to refactor my routes to be nested children. But I would encourage you to re-consider your needs for having the version in the URI in the first place.


#119 added a link to Analytics Dashboard in footer Section

What This PR Do?
Adding the Analytics Dashboard with the link

Hi @alshareef49,
Thanks for submitting this pull request. Unfortunately, I will be closing this because you were not the one assigned to do it. To be fair, I will let the person currently assigned to issue https://github.com/conda-incubator/conda-dot-org/issues/119 complete this.


⚠ Bofrost.be has degraded performance

In 3eb1698, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1462 ms

Resolved: Bofrost.be performance has improved in bfc06e4 after 6 minutes.


Tool for extracting targets and weights from an existing PoN.

We need a tool that can create a target BED file and a target weights file from an existing PoN.
For the target BED:
pon.getRawTargets() for the targets (alternatively, we can produce the targets that remain after filtering with pon.getPanelTargets())
For the target weights:
// code snippet for generating the weights from a PoN
// this function probably already exists by the time someone addresses this issue.
final double[] targetVariances = pon.getTargetVariances();
final double[] targetWeights = new double[targetVariances.length];
for (int i = 0; i < targetVariances.length; i++) {
     targetWeights[i] = 1/targetVariances[i];
}

Good idea!  If we implement #102 and have an allelic PoN then we would have parallel methods for getting per-target priors on allelic bias.

@davidbenjamin Assigning to me, since I've already done this in the PoN QC branch.

@davidbenjamin Actually, nevermind.  I've just made it so that the information is there.  We will still need a tool to actually extract this information.  HOWEVER, this should not be addressed until that branch is merged.  And it may make more sense for me to do it.

@LeetTL agreed.

Whoever handles this should probably also address #249.

@davidbenjamin We should also have this tool be used in our workflow scripts to automatically generate weights before launching a segmentation.....  See pull request for PoN QC (comments in issue #283 )


Add backchannel support for rtsp server

Currently, there is no way for clients to send audio data to go2rtc via RTSP backchannel, as the RTSP server lacks a backchannel implementation.
This PR adds a backchannel to the stream (when backchannel=1) and thus allows clients to send audio data to go2rtc.
Tested streams so far:

webrtc:ws://
tapo://
rtsp:// with backchannel

I think other streams with backchannel should also work

@seydx, out of curiosity, what use case this enables? Connecting a go2rtc server to another?

@seydx, out of curiosity, what use case this enables? Connecting a go2rtc server to another?

This implementation allows me to send audio data directly to go2rtc using my RTSP client via rtsp. The data is sent interleaved over the connected socket
Since go2rtc offers two-way audio for some cameras, e.g. tapo etc, the rtsp client can connect to the go2rtc rtsp link of the tapo camera and send audio data directly
This functionality is natively available in WebRTC, where you can send audio directly from the browser to the camera. With this implementation, virtually anyone can do it, regardless of the programming language and environment, since rtsp ist just a tcp connection


add assume_condition

APPSRE-4674
Signed-off-by: Feng Huang<EMAIL_ADDRESS>

Can you provide some context for this change?

Are these the kind of conditions that we can add here? https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html
If so, it would be nice for the schema reader to add a small description about this field, what it exactly means and possibly that very link 😄
Or maybe https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_iam-condition-keys.htm . It has taken me a bit to understand what was all of this 😅

Are these the kind of conditions that we can add here? https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html
If so, it would be nice for the schema reader to add a small description about this field, what it exactly means and possibly that very link 😄
Or maybe https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_iam-condition-keys.html. It has taken me a bit to understand what was all of this 😅

Updated. This is for condition context keys for IAM and AWS STS  with format


Run tests outside of xunit synccontext

@BrennanConroy seems like this made things worse. I'm seeing lots of failures locally.

Works on my machine

🎉


Authenticated user is not allowed access - GoDaddy changed the API requirements

Not an issue with godaddy-ddns as such, but in case anyone else tries using the API service for the first time like me, it seems GoDaddy changed the requirements of usage a couple of days ago so that you have to have 50 domains registered with them to be able to use the API.
You'll see this error in the godaddy-ddns logs:
Authenticated user is not allowed access, StatusCode: 403, StatusCode: 1

@rnlgreen Thanks for reporting. I am not able to find any document about change in API policy. Could you please help me with document or announcement about this change

is there any way to get this working?  I was just about to create a thread that it no longer updates ip.
i get the following error in my logs like you mentioned.
"Failed to update record. Error: addRecord Error getting DNS record Error: Authenticated user is not allowed access, StatusCode: 403, StatusCode: 1"

I will try to look into some alternatives. Currently it looks like GoDaddy has changed its developer policy and does not allow API access for users having less than 50 domains (I am yet to find a document/announcement/article to verify this).

Damn, bummer.  Ill keep checking this post.  Thanks!

I don't think there's any documentation or announcement, I just found a thread on Reddit:
https://www.reddit.com/r/godaddy/comments/1chs1j8/godaddy_access_denied_via_apicall/

maybe its possible to use OTE environment which is hosted at https://api.ote-godaddy.com/. its possible to add a parameter to specify the ote env?

Will check this. Thanks

Are there any advancements in finding out a solution?

I will need some help from community. I checked on internet but I do not find any alternative and most articles shows old API key ways. I also tried to reach out to GoDaddy customer support, but looks like since I have moved my domain out of GoDaddy, they are also not helpful.
Can you please reach out to GoDaddy support team and ask what alternatives they suggest to setup DDNS, if API keys are not working.

My solution was to move out my domain from godaddy. I reach out the Godaddy api support team. I get this answer:-(
Hi,
We have recently updated the account requirements to access parts of our production Domains API. As part of this update, access to these APIs are now limited:
Availability API: Limited to accounts with 50 or more domains
Management and DNS APIs: Limited to accounts with 10 or more domains and/or an active Premium Discount Domain Club plan.
If you have lost access to these APIs, but feel you meet these requirements, please reply back with your account number and we will review your account and whitelist you if we have denied you access in error.
Please note that this does not affect your access to any of our OTE APIs.
If you have any further questions or need assistance with other API questions, please reach out.
Regards,
API Support Team

Yeah, I just moved all my stuff to cloudflare. They have a dns update that works and had to renew my domain name too so I just went with them for everything. Sucks I was with GoDaddy for a long time always liked them. Too bad.

I would with to see this thread before I registered a domain with GoDaddy, now I have the same issue.

It's such a bullshit move on their part but I didn't know this before bought domain and no idea where else to buy domain I wanted so stuck with them. Technically it's possible to update it thru website way but I would start just telling everyone to avoid them like plague and look into moving to other providers.

I have switched to namecheap and https://github.com/navilg/namecheap-ddns-docker works like a charm

I'm affected by this new GoDaddy policy. Does anyone know an alternative registrar that has an API that supports querying the DNS records? I need to list, remove and add TXT records.

@codemonstur  https://porkbun.com/ their API works fine and libraries are widely available.

@davispuh hey thanks that looks nice. But I ultimately chose to go with https://zone.eu.


[Code app]: Runtime version drop down is displayed on the code editor text area in Full screen mode

EPAM AI DIAL chat version
0.20.0
How to reproduce
Steps:

Open Add Code app form
select any folder for source files -> code editor displayed
click on Full screen button -> Runtime version dropdown displayed in code editor text area -> bug

Actual result

Expected result
List of files on the left side and text area in the right side should be displayed in Full screen mode
Confidential information

[X] I confirm that do not share any confidential information

verified on staging successfully


[Bug] lmdeploy: command not found

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.

Describe the bug
I use pip install lmdeploy to install this pacakge. But when I run it successfully, I got a error: lmdeploy: command not found
Reproduction
pip install lmdeploy -> lmdeploy -> lmdeploy: command not found
Error traceback
lmdeploy: command not found

The latest main branch hasn't been released yet.
After we release a new version next week, you can use the cli.

same issue

@amulil @lubancafe try pip install lmdeploy==0.0.13

The latest main branch hasn't been released yet. After we release a new version next week, you can use the cli.
same issue，have you solved the problem yet?


response$.request should be read-only

From @staltz on July 6, 2015 16:8
Use Object.defineProperty to make a no-op setter for request property under response$.
Copied from original issue: cyclejs/cycle-http-driver#7

Should request's properties be also read-only?
I volunteer to PR this :)

Hi @chadrien thanks for volunteering. I believe the properties don't need to be read-only, and this feature suggestion should work so that if someone tries to set response$.request, it will raise a warning in the console for instance.

Alright, will do so :+1:

I removed help wanted so you are now "assigned" to this :)

Object.defineProperty / Object.freeze both throw a TypeError when trying to write a read-only attribute. So if we only want a warning in console we would need a Proxy that could try/catch internally. Is that OK with you or is it too much "complexity" and throwing a TypeError would be OK?

Throwing TypeError would be ok :)

This is done long ago. :D


Type inference resulting in incorrect type for function result

TypeScript Version:  2.2.1
Code
function functionReturningVoid() {
}
function functionReturningNumber() {
  return 0;
}
function returnValueFrom<R, F extends (() => R)>(f: F) {
  return f();
}
const rVoid = returnValueFrom(functionReturningVoid); // Argument of type '() => void' is not assignable to parameter of type '() => {}'.
const rNumber: number = returnValueFrom(functionReturningNumber); // Type '{}' is not assignable to type 'number'.

Expected behavior:
Compiles successfully.
Actual behavior:
Compiles with the above errors noted in comments.

Note: it's valid to assign the value of a void-returning function, e.g. the following compiles:
const v = functionReturningVoid();

This might be related to #5884 and #5254 (for which #5884 was closed in favor of) but as all the types are specified at each line, it seems it's not a problem that call site inference is not taking place, but rather that R is widened unneccesarily?

@magnushiie
Have you tried this?
(I've checked this snippet on http://www.typescriptlang.org/play/)
function functionReturningVoid()  {
}
function functionReturningNumber() {
  return 0;
}
function returnValueFrom<R>(f: () => R): R {
  return f();
}
const rVoid = returnValueFrom(functionReturningVoid); // ok
const rNumber : number = returnValueFrom(functionReturningNumber); // ok

Or are you trying to illustrate some more generic problem?

Ah, yes, this solves it. I thought I had a more generic instance where this would not be a solution, but I can't find it anymore.

Constraints don't produce an inference site, so there's nothing to infer R from.


fixed Llama._create_completion suffix check

We discovered that it was possible to exploit  Llama._create_completion suffix parameter to send string-like object which could actually lead to Arbitrary Code Execution.
Here is PoC: https://github.com/tangledgroup/llama-cpp-python-exploit/blob/f99baf1e66b9fa79987c594179ac93eadfb2ca97/exploit.py#L45

@mtasic85 thank you, very good catch!


Is it possible to set the height size for select, input, etc ?

Using : http://getbootstrap.com/css/#forms-control-sizes
Thanks a lot

Interested in this as well. It needs to be applied on .form-group container though, not on the input element directly. I feel there should be an option for this.

I was able to change the form control size by passing the control_class param:
<%= f.text_field :name, control_class: "form-control input-lg" %>

Figured I'd add it here in case anyone else came across this issue looking for a solution!


3.0: Migrate Batch and CWLogs substacks to CDK

Add possibility to suppress validators and filter by validation level to create command

Rename ClusterInfo to ClusterStackInfo
Rename FullClusterInfo to ClusterInfo
Created an internal dictionary to pass compute_security_group information to slurm construct.

Move CDK code related to slurm in a SlurmConstruct

Added utility method in HeadNode e BaseQueue to retrieve instance_role.
Added utility method in HeadNode and ComputeResource to check if simultaneous_multithreading
must be disabled manually with a cookbook script.
Added is_intel_hpc_platform_enabled and is_cw_logging_enabled properties in ClusterConfig.
Added extra_chef_attributes and custom_chef_cookbook properties in ClusterConfig.
Moved Slurm specific code into a SlurmConstruct in the slurm_builder module.
Size of cluster_stack reduced from 1800+ rows to 1200+.
Splitted HeadNode and ComputeFleet role, the code now will create a Role for each queue.
Moved all the methods used by both SlurmConstruct and ClusterCdkStack in the cdk_builder_utils
Moved packages_versions mappings in constants module and added it to bump-version.sh script.
Fixed _add_compute_security_group to not use head_security_group if not created by us.
(In the old template there was a single condition to create all the security groups,
in pcluster3 there are different conditions).
Moved role and policy creation in the same method because they are strictly related.
Refactored roles and policies creation to use the same code for head node and queues.
Pass the stack_name to use it as a string rather than using the internal self.stack_name from the Stack
that is a reference, so it cannot be used for utility methods.
Removed underscore prefix for stack variables passed to Slurm construct.
Moved  head_ip and head_eni creation in the same method because they are strictly related.
Moved _add_cleanup_resources_lambda and _add_cleanup_resources_bucket_custom_resource in the same method.
Created an internal structure to store head_node/queue roles and the information if they are created by us
or provided by the user. It is used to pass information to Slurm construct.

Add possibility to configure different security groups for each queue

We're creating a single new security group for compute fleet and associating it
to all the queues for which there is no security group specified by the user.
Defined some utility methods to return the complete list of security groups
to be used for head node and compute.
Fixed EFS mount target creation to use all the compute security groups,
both created by us and provided by the user.
Fixed FSx security groups list by using all the compute security groups,
both created by us and provided by the user and not just the ones from the config.
Created an internal dictionary to pass compute_security_group information to slurm construct.
Define PclusterLambdaConstruct and refactor code to avoid code repetition
Create utility method to create Lambda role to avoid code duplication

Migrate AWS Batch substack to CDK Construct
Model

Move instance_type info and properties from BaseComputeResource to SlurmComputeResource
because we can't get instance type information from Batch, on which the user can provide
a list of instance types or instance families.
Move validators using architecture property from BaseComputeResource to SlurmComputeResource
Move EFA os architecture validator from BaseClusterConfig to SlurmClusterConfig
Align validators tests/mocking to these changes.

CDK builder

Move get_queue_security_groups_full to cdk_builder_utils because it's required by both
scheduler construct.
Add raw_dict parameter to utility functions to generate tags, because Batch is accepting
a raw dictionary.
Migrated CloudWatch log groups creation into Awsbatch construct.

Tests

Generate two different dummy cluster config and test template creation for both the schedulers.

Note about CfnRule
We're using a raw event_pattern rather than using events.EventPattern because of: aws/aws-cdk#5703
Migrate ClodWatch logs substack to CDK

Move log group creation for lambda function into PclusterLambdaConstruct
Added a timestamp to CloudWatch Log group name for the cluster

Awesome and speedy work. Thank you!


Drains

About the PR
Closes https://github.com/space-wizards/space-station-14/issues/6814.
Currently placable by mappers only, the obstruction check is a bit too CBT until collision group rework.
Screenshots

https://user-images.githubusercontent.com/60792108/164318676-d7edf090-280f-4b83-b9b2-63e1381f1ed4.mp4
Changelog

:cl: Rane

add: Drains will soon be added to stations, making the jobs of Janitors, Chefs, and Chemists much easier.

Presumably you can empty drains with a bucket to collect all those sweet sweet reagents?

will you be able to left click the drain to get rid of chems? That will be so useful

Presumably you can empty drains with a bucket to collect all those sweet sweet reagents? Gives Janitor something to do going round unblocking drains.

You empty buckets into drains not the other way around

will you be able to left click the drain to get rid of chems? That will be so useful

It goes into the abyss at a rate of 3u / second (until we get plumbing???)

Presumably you can empty drains with a bucket to collect all those sweet sweet reagents? Gives Janitor something to do going round unblocking drains.

You empty buckets into drains not the other way around

will you be able to left click the drain to get rid of chems? That will be so useful

It goes into the abyss at a rate of 3u / second (until we get plumbing???)

I get the logic but seems counter. Until we get plumbing perhaps it should function as a bucket in the floor that needs periodically emptied (I don't see plumbing coming on the horizon and would be a good way to harvest chems I guess).

I get the logic but seems counter. Until we get plumbing perhaps it should function as a bucket in the floor that needs periodically emptied (I don't see plumbing coming on the horizon and would be a good way to harvest chems I guess).

Isn't the point of the drain to delete reagents?

I get the logic but seems counter. Until we get plumbing perhaps it should function as a bucket in the floor that needs periodically emptied (I don't see plumbing coming on the horizon and would be a good way to harvest chems I guess).

Isn't the point of the drain to delete reagents?
Otherwise we need a super drain so that the janitor can dump reagents into that to delete them.

I thought it was to get rid of puddles of reagents? I mean go for it as is if deleting is what y'all want. I can see it working either way.

i don't super like that it deletes reagents but i get why it exists, might need to be made slower though

Reviews addressed


Add protons back

Motivation
In #310 we have to switch back to protobufjs because protons is 20x slower than protobufjs, we should add it back once the performance of protons is comparable or better than protobufjs
Description
Use the following benchmark (need to add "@dapplion/benchmark" as devDependencies):
import { itBench, setBenchOpts } from '@dapplion/benchmark'
import { RPC } from '../../../src/message/rpc.js'

/**
 *  rpc
    ✔ decode Attestation message                                           6807815 ops/s    146.8900 ns/op        -    1977187 runs   30.1 s
 */
describe.only('rpc', function () {
  this.timeout(0)
  setBenchOpts({
    maxMs: 60 * 1000,
    minMs: 30 * 1000,
    minRuns: 200
  })

  const rpc: RPC = {
    subscriptions: [],
    messages: [
      {
        topic: 'topic1',
        // typical Attestation
        data: Buffer.from(
          'e40000000a000000000000000a00000000000000a45c8daa336e17a150300afd4c717313c84f291754c51a378f20958083c5fa070a00000000000000a45c8daa336e17a150300afd4c717313c84f291754c51a378f20958083c5fa070a00000000000000a45c8daa336e17a150300afd4c717313c84f291754c51a378f20958083c5fa0795d2ef8ae4e2b4d1e5b3d5ce47b518e3db2c8c4d082e4498805ac2a686c69f248761b78437db2927470c1e77ede9c18606110faacbcbe4f13052bde7f7eff6aab09edf7bc4929fda2230f943aba2c47b6f940d350cb20c76fad4a8d40e2f3f1f01',
          'hex'
        ),
        signature: Uint8Array.from(Array.from({ length: 96 }, () => 100))
      }
    ],
    control: undefined
  }

  const bytes = RPC.encode(rpc)

  console.log('@@@ encoded to', Buffer.from(bytes.slice()).toString('hex'), 'length', bytes.length)

  itBench({
    id: 'decode Attestation message',
    fn: () => {
      RPC.decode(bytes)
    },
    runsFactor: 100
  })
})

need to also add similar benchmark for encode

I have incorporated the above benchmark into protons and running it with the latest version (5.1.0) yields good results:
% node packages/protons-benchmark/dist/src/rpc.js
protons x 3,174,965 ops/sec ±0.40% (87 runs sampled)
protobufjs x 2,976,375 ops/sec ±1.72% (89 runs sampled)
Fastest is protons

thanks @achingbrain , protons 5.1.0 is really faster than older versions however it's not very stable, see the statistics here https://github.com/ChainSafe/js-libp2p-gossipsub/pull/327

That's interesting<EMAIL_ADDRESS>uses the Reader and Writer classes from<EMAIL_ADDRESS>are you sure something else isn't affecting the benchmark run?
Also, how are you generating those stats, I can't see anything new in the benchmark folder?

Also, how are you generating those stats, I can't see anything new in the benchmark folder?

I just run the test in my local environment

That's interesting<EMAIL_ADDRESS>uses the Reader and Writer classes from<EMAIL_ADDRESS>are you sure something else isn't affecting the benchmark run?

I cannot think of anything that affect the benchmark but we can only be sure if we track the benchmark as part of CI steps. But I didn't see that same issue with protobufjs
@achingbrain  If you have a chance please run it multiple times in your environment too (using #327) to see if the issue happens or not

Got memory leak issue with protons 5.1.0 that causes lodestar to be restarted multiple times, this is from a test mainnet node subscribing to all subnets:

Are you sure this is protons related?  protons 7.x shipped six months ago, has 20-30k downloads a week, is used all over the libp2p/ipfs/helia stack and this hasn't been reported.

Are you sure this is protons related? protons 7.x shipped six months ago, has 20-30k downloads a week, is used all over the libp2p/ipfs/helia stack and in a bunch of other projects and this hasn't been reported.

@achingbrain I haven't used protons 7.x as it only supports proto3. This happens with protons 5.1.0 and protons-runtime 3.1.0

src/message/rpc.proto is already proto3 syntax so I'm not sure anything is blocked here?

Actually looking at this more, this is proto2 with the syntax field set to proto3.

There is an error on this line - proto3 does not have a required type.

By default fields are not sent on the wire if they are set to the default value (0 for most number types, etc) but in proto2 it meant that the value always has to be sent, otherwise the message is invalid.
You can simulate this in proto3 by marking the field optional and ensuring the value is always set.

In proto3 the default type is singular, this means if the field is set to the default value it is not sent on the wire, at the other end if the field is not on the wire it's set to the default value - e.g. there's no way to tell if the value was sent or not

This is how optional behaved in proto2

In proto3 the optional type means if the field is not set, no value is sent on the wire and no value is read out at the other end

In proto3 this lets us detect if a field was not set
There is no equivalent in proto2
In proto2 a default type is always returned, even for "optional" fields

TLDR for converting from proto2 to proto3 is:

Remove optional keyword (proto3 "singular" behaves like proto2 "optional")
Add optional keyword to fields that were required in proto2 and ensure they are set at the application level

the memory leak was lodestar issue of not using correct NodeJS version, see https://github.com/ChainSafe/lodestar/issues/5851
@achingbrain thanks for the migration guide. I updated to proto3 using protons 7.0.5, and it requires protons-runtime version 5, and it's 2x slower compared to protons-runtime 3.x as in https://github.com/ChainSafe/js-libp2p-gossipsub/pull/327#issuecomment-1658059241 (you can give it a try in tuyen/protons_7 branch)
do you have any ideas? should I go with proto2 + protons 5 + protons-runtime 3 as in the PR or wait for an improvement in protons-runtime?

created https://github.com/ipfs/protons/issues/109 to track the performance issue of protons-runtime v5

#327 is ready to test once lodestar migrated to latest libp2p https://github.com/ChainSafe/lodestar/pull/5869


Cannot add custom views like buttons that need to recognize gestures

The PaperOnboarding class has a GestureControl view that gets added as the last subview and spans the entire content area and swallows gestures.  Adding any buttons or subviews cannot get taps. Is there a workaround or can you update to support this properly?

If you want you can replace logic from GestureControl into PaperOnboarding view, in that case there will be no problems with any subviews


Increase number of character slots per account

Currently the server allows for only two character slots per account.
I couldn't find where this is regulated in the source, but we should expand this to 12.

This is pretty simple task to increase this CharacterDatabase::CreateLinkedAccount has the required magic. A slightly more challenging will be making this a configuration variable.

Tested this with 12 slots but the GUI of the target client version doesn't handle a long list gracefully. Found the unused macro MAX_CHARACTER_SLOTS in Character.h, which is set at 8 and using that for now.
Recommend leaving this issue open as a max slots variable can be pulled from the settings.cfg


Training the ctpn and crnn Model for mobile

@Sanster How did you train the mobile ctpn model & crnn model?

Freeze tensorflow checkpoint to pb file, and use tensorflow-android to load the model

Can you answer in more details of how did you create the models, along with:

Which repositories in github that you used for creating the models?
How did you get such small model sizes?
How did you freeze the models?

Which repositories in github that you used for creating the models?

ctpn: https://github.com/Sanster/tf_ctpn
crnn: https://github.com/Sanster/tf_crnn

How did you get such small model sizes?

use small cnn(mobilenet)；tensorflow freeze_graph will make the model small

How did you freeze the models?

ctpn: https://github.com/Sanster/tf_ctpn/blob/master/tools/freeze_graph.py
crnn: https://github.com/Sanster/tf_crnn/blob/master/tools/freeze_graph.py

You can check  tensorflow document for more detail

@Sanster hello, how do you deploy the model to the anaroid? use tensorflow-lite or mace or ncnn?

org.tensorflow:tensorflow-android:1.9.0


Adding sivaavkd to admin-list

Adding my name to admin-list

Can one of the admins verify this patch?

[test]


incompatible - No compatible package found for 'en_core_web_trf_lg' (spaCy v3.6.0

✘ No compatible package found for 'en_core_web_trf_lg' (spaCy
v3.6.0)
i have tried using spacy version 3.5.1, 3.6, 3.7 dev(0) none works

This doesn't seem like a question about spacy-llm?
The available English pipeline packages are described here: https://spacy.io/models/en


Idle Time spike when NavigationAgent is present

Godot version
3.5.beta2 and 3.5.beta4
System information
Windows 10, GLES3, NVIDIA GeForce RTX 2070 Super
Issue description
If a NavigationAgent is a child of NavigationMeshInstance there is noticeable lag even when not in use.
Profiler shows a big spike in Idle Time not coming from any script function. Removing the NavigationAgent and running the scene again removes the spike.

Happens with or without baked NavMesh.
Moving the NavigationAgent somewhere else also removes the spike.
Issue spotted when adding a NavigationAgent node to a RigidBody in character mode to move to a destination (3.4.beta2)
Steps to reproduce
Add a Navigation node, a NavigationMeshInstance as child and a NavigationAgent as child of that.
Run with the Profiler on.
Running the same scene without the NavigationAgent
Minimal reproduction project
Both Main (scene with valid NavMesh) and MinimumTest (just the 3 nodes mentioned above).
NavigationIdleTimeExample.zip

This might be a duplicate of #56838 which was fixed recently. The fix will be included in 3.5 beta 5.
Could you test latest CI builds from the 3.x branch to confirm? https://github.com/godotengine/godot/actions/runs/2244474520
Alternatively if you can build 3.x from source, that would work too.

@akien-mga yes, the problem is gone after building from source. Closing the issue then.


refactor: remove supportsInterface

What kind of change does this PR introduce?
Braking Feature Change: This PR removes the this.supportsInterface(...) and ERC725.supportsInterface(...) functions, as well as their tests and documentation.
What is the current behavior?
Currently, erc725.js can be used to resolve and detect whitelisted ERC165-based interface IDs of a given contract based on their standardized string inputs:
// Object
myErc725.supportsInterface("ERC725X")
myErc725.supportsInterface("LSP8IdentifiableDigitalAsset")

// Class
ERC725.supportsInterface("ERC725X", "0x...")
ERC725.supportsInterface("LSP8IdentifiableDigitalAsset", "0x...")

While this is a convenient way to check interfaces without further redo, resolving and manually updating IDs can be cumbersome.
What is the new behavior?
The decision was made to completely remove this functionality and keep it completely separated from contract libraries (like lsp-smart-contracts), that feature additional information like ABIs and schemas on top of being up-to-date with the latest standardization changes.
If you are affected by this breaking feature change, please use the following method to read ERC165-based interface IDs:
// Example using IDs from the @lukso/lsp-smart-contracts library
import { INTERFACE_IDS } from "@lukso/lsp-smart-contracts";

// Define a global EIP165 ABI
const eip165ABI = [{
    inputs: [{
        internalType: 'bytes4',
        name: 'interfaceId',
        type: 'bytes4',
      }],
    name: 'supportsInterface',
    outputs: [{
        internalType: 'bool',
        name: '',
        type: 'bool',
      }],
    stateMutability: 'view',
    type: 'function',
  }];

  try {
    const myEip165Contract = contract(eip165ABI as any, address)
    return await eip165Contract.methods.supportsInterface(INTERFACE_IDS.ERC725X).call()
    return await eip165Contract.methods.supportsInterface(INTERFACE_IDS.LSP8IdentifiableDigitalAsset).call()
  } catch (error: unknown) {
    console.error(error)
    return false
  }

Other information:
The following repositories have been checked:
✅ erc725-inspect
✅ my.universalprofile.cloud
✅ wallet.universalprofile.cloud
None of them is using ERC725's supportsInterface function anymore.

Codecov Report

Merging #352 (ab0db08) into develop (9640d9f) will decrease coverage by 0.21%.
Report is 15 commits behind head on develop.
The diff coverage is 73.52%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff             @@
##           develop     #352      +/-   ##
===========================================
- Coverage    83.71%   83.51%   -0.21%
===========================================
  Files           18       17       -1
  Lines         1130     1122       -8
  Branches       255      258       +3
===========================================
- Hits           946      937       -9
+ Misses          98       94       -4
- Partials        86       91       +5

Files
Coverage Δ

src/constants/constants.ts
100.00% <100.00%> (ø)

src/index.ts
78.12% <100.00%> (+3.12%)
:arrow_up:

src/lib/detector.ts
100.00% <ø> (+4.00%)
:arrow_up:

src/lib/getDataFromExternalSources.ts
61.29% <33.33%> (-2.05%)
:arrow_down:

src/lib/utils.ts
82.09% <81.81%> (-1.03%)
:arrow_down:

src/lib/encoder.ts
82.78% <64.28%> (-1.18%)
:arrow_down:

This could be duplicate with #317
I had opened the PR already, but we could close it and keep this one (or the other way around)

Oh you are right. Did not check if there already was a PR open for that. 😅 Has there been an outcome yet? @frozeman

From my side, I would go ahead with this PR so that we focus this library purely on the encoding / decoding side.
Which is what this library is aimed for.

Nice that the other repos were updated.
If this is a breaking change, don't forget to add ! in the commit name.
refactor: remove supportsInterface

https://www.conventionalcommits.org/en/v1.0.0/


Add unproxy() method to session

As noticed by @gbadner the fetch() method currently features the semantics of Hibernate.unproxy() rather than the semantics of Hibernate.initialize() (i.e. it passes your callback a "naked" reference to the entity).
That's probably wrong, and we should change it. But if we do so, we should add an additional method with the semantics of unproxy().

I pushed a fix to CascadeComplicatedTest. Now #testMergeTransient passes.

Done.


The client is using an unsupported version of the Socket.IO or Engine.IO protocols

When trying to connect to the server from the client, I get the following error:
The client is using an unsupported version of the Socket.IO or Engine.IO protocols (further occurrences of this error will be logged with level INFO)
[22:27:30] engineio.server _log_error_once::710 ERROR - The client is using an unsupported version of the Socket.IO or Engine.IO protocols (further occurrences of this error will be logged with level INFO)

Do you think this could be a duplicate of #34? I'll respond there.

Yeah I managed to get this to work locally but updating the
socket.io-client dependency to 3.0.4
On Tue, Dec 15, 2020, 11:56 PM Justin D. Harris<EMAIL_ADDRESS>wrote:

Do you think this could be a duplicate of #34
https://github.com/juharris/switch-remoteplay/issues/34? I'll respond
there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/juharris/switch-remoteplay/issues/37#issuecomment-745763649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3VGUJG6ZQHGUXCAR2AND3SVA4WDANCNFSM4U5KY2UQ
.

That's great to hear! I'll test it out myself in a few days and use specific version numbers in setup.py/package.json. Sorry about this.

@juharris no problem! Thanks for putting this tool together!

If you have a kofi or anything like that, let me know and I'll definitely throw you some money

That's very kind of you! Perhaps you can just make a donation to something and think of me? Something environmental/STEM related that helps young students/women/disadvantaged people.


chore(deps): update dependency @trinsic/web-ui to v0.5.5

This PR contains the following updates:

Package
Type
Update
Change

@trinsic/web-ui (source)
dependencies
minor
0.3.1 -> 0.5.5

Release Notes

trinsic-id/sdk (@trinsic/web-ui)
v0.5.5
Compare Source
v0.5.0
Compare Source
v0.4.3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (0.5.5). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Add a short tutorial of 3 lines to explain how to configure

For my part, I didn't understand why the extension wasn't working, and it was by returning to the GitHub page that I saw that I needed to put a link to the Steam manifest, and I had to quickly search on the internet where to find it to make the extension work.
I think a very brief 3-line tutorial for less savvy people like me could help.
PS: Sorry for any mistakes, English is not my native language.

Hi mate, no worries your English is great! I haven’t worked on this plugin for a while but I’ll add something onto the github to make it easier. Is that what you mean?

Yes, exactly, put a tutorial on GitHub or directly in the description on Playnite. I think it could help people like me who are discovering Playnite and transitioning. That would be great.

Added in the commit 2f7df3a to the github, and requested to add to the plugin description  https://github.com/JosefNemec/PlayniteAddonDatabase/pull/357

No problem!! :)


Cdfreeman google patch 1

Adds a simple notebook for interactively testing a bigbench task.

I'm excited you created this! Some suggestions:
I would move the pickers for dataset, number_json_examples, number_json_shots into their own cell, between the cell that does imports, and the cell that actually evaluates the task.
I would rename the "Dataset:" picker to the "Task:" picker. I would add some text to the form after the task picker, noting that the json options only apply for json tasks.
I would add some text before printing the ScoreData list, like:
`\n\nTask completed!\n\nThe task returned the following score data structure:\n"
I would also include in this PR edits to the task instructions in the top level README.md and in docs/doc.md which link to this colab and suggest using it to verify task behavior.

@Sohl-Dickstein Alright, changes implemented!  Post merge, I need to take at least one more pass to make sure links aren't broken, but this should be nearly ready to go!


repackaging - Illumio Core/SecurityBridge/Trend Micro TippingPoint

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Hi @v-rusraut, in Solutions/SecurityBridge App/Package/mainTemplate.json please change the "Azure sentinel" to "Microsoft Sentinel"

Hi @v-rusraut, please remove older versions of the zip in TrendMicro TippingPoint zip.
.


provide options to use uek or rhck

By default, the script installs and sets the UEK as default. If required, you can change the default kernel to the RHCK after the switch is complete.

By default, the script installs and sets the UEK as default. If required, you can change the default kernel to the RHCK after the switch is complete.

I can see the value in supporting this option and would accept a PR that allowed it but I agree with Avi that it's not an Issue with the code

I can see the value in supporting this option and would accept a PR that allowed it but I agree with Avi that it's not an Issue with the code


optimize concurrent multi-block requests

Fall back to SplitRanges() behavior on concurrent multi block reads. This kicks-in in the following case:
request 1 needs blocks: ABCD
request 2 needs blocks:   CDE

With SplitRanges(true), the behavior is unchanged, osio will make 5 requests for each individual block.
Each block may be read in the context of either request 1 or 2, depending on who managed to aquire the
lock on each individual block.
Before this patch, osio would emit a 4-block read (ABCD) for request 1, and a 3-block read (CDE) for request 2.
i.e. 2 blocks (CD) will have been read twice instead of once.
After this patch, depending on lock ordering, osio will either emit:

a 4-block read (ABCD) for request 1, and a 1-block read (E) for request 2
a 3-block read (CDE) for request 2, and a 2 1-block reads (A),(B) for request 1

Pull Request Test Coverage Report for Build 989777362

106 of 122 (86.89%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.4%) to 94.353%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

namedoncemutex.go
48
50
96.0%

adapter.go
57
71
80.28%

Totals

Change from base Build 816963526:
-2.4%

Covered Lines:
518

Relevant Lines:
549

💛  - Coveralls