pathlib models.py

Checklist
GitHub

[ ] I've given this PR a concise, self-descriptive, and meaningful title
[ ] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[ ] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 11 (90.91%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 70.109%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/models.py
10
11
90.91%

Files with Coverage Reduction
New Missed Lines
%

ivadomed/models.py
2
91.79%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4114

Relevant Lines:
5868

💛  - Coveralls


Add setAttributes for View

Users may decide to set className, id, or attributes with a function such that the values can change based on the view's state or model.
In general the user is expected to update these values manually once the element is set.  It isn't terribly hard to manage className or other attributes directly, but there is a little bit of logic regarding className and id overriding the attributes hash.
This simplifies answering how to update the el's attributes after initialization.

Maybe rename to updateAttributes ?

I don't love that this changes the method signature of setAttributes. What if instead we allowed both setAttributes(attrs) and setAttributes(), checking if an attrs object was passed in and then falling back to the old behavior if not?
Admittedly I've never had a use case for either, but I can see arguments both ways.

Yeah I was on the fence about that very issue originally having one function and renaming _setAttributes.
If setAttributes handles both signatures should we keep_setAttributes?

The underscored version is for "hooks" that do the actual DOM manipulation
(see #3003).
On Mon, Mar 20, 2017, 22:19 Paul Falgout<EMAIL_ADDRESS>wrote:

Yeah I was on the fence about that very issue originally having one
function and renaming _setAttributes.
If setAttributes handles both signatures should we keep_setAttributes?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jashkenas/backbone/pull/4128#issuecomment-287956687,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA42KGmR_xqpLB2NQ6t7p9SiZPgohhwmks5rnzO2gaJpZM4Mhu4d
.

--
Adam K (mobile)

Alright updated.
TBH I've never really needed this before either.. but I recently consulted on a project doing a lot of filling in attributes from an endpoint that configures the views.  The data isn't super consistent and the logic they were using to handle it was intense (certainly unnecessarily) when really all they wanted to do was re-run what was happening initially.  Easy enough to implement myself, but I think they would have avoided this had their been the method available.
Won't be heart broken either way, but it seems reasonable to me.

So I'm gonna be a weak close on this. It's easy enough to write your own plugin / base view if you really need it, and no sense adding complexity to the API for the folks that don't.


Hakai CKAN Checker tests?

The Hakai CKAN checker is now running live. The only thing stopping it from being useful is proper checks.
The tests implemented are presented here (see every lines starting with _test( :
https://github.com/HakaiInstitute/hakai-ckan-records-checks/blob/main/hakai_ckan_records_checks/hakai.py
The main question what should we look for?

Add review if it has a DOI @Br-Johnson

We can calose this issue for now and create a new one when changes are desired


add Hands-on Python 3 Tutorial

What does this PR do?
Add resource
For resources
Description
add another python book
Why is this valuable (or not)?
its yet another valuable book for learning python
How do we know it's really free?
its available for free on the internet
For book lists, is it a book? For course lists, is it a course? etc.
book
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Excellent


Appveyor fix

I made sure to test nested IF's & the MSBuild step. After quoting, they ran for me in my cmd prompt.
edit: Seems something is wrong only with 32-bit. I think if I pass some flag or something to cmake it'll fix it.

Thank you!


have build container only claim port 1313 if running make serve

You can only run the build container once, because it port-forwards port 1313.
Makefile.overrides.mk:CONTAINER_OPTIONS = -p 1313:1313 ${ADDITIONAL_CONTAINER_OPTIONS}

This is only necessary if you're using it to run a local Hugo preview, and it stops you being able to do useful things like make gen or make lint-md while it's running.
Is it practical to run this container more than once at once, and if so, can we have this variable only set when the target for make serve is run?
Affected product area (please put an X in all that apply)
[x] Docs
[x] Test and Release

is this for istio.io repo?

Yes, sorry, I thought it was one of the common files.  I'll move the issue to the right repo!


Add example project using CocoaAsyncSocket

Add an additional example project demonstrating use of CocoaAsyncSocket.

This would be great - any pointers here?

I was planning on getting an example built really soon. In the mean time, for sending OSC this works:
import CocoaAsyncSocket
import OSCKit

let oscClient = GCDAsyncUdpSocket()

func oscClientSetup() throws {
    let data = OSCMessage(
        address: "/some/address/here",
        values: [.int32(1), .int32(2), .string("Test")]
    ).rawData

    oscClient.send(data,
                   toHost: "<IP_ADDRESS>",
                   port: 8000,
                   withTimeout: 5.0,
                   tag: 0)
}

I was planning on getting an example built really soon. In the mean time, this is the basic implementation.
Just haven't done any usability tests to see if any particular options need to be set on the socket yet.
Entitlements
If your app is for iOS you don't need to set any app entitlements. The user will be asked to allow local network connections the first time you open the UDP port(s).
Make sure if your app is for macOS and is sandboxed, you enable network connections:

Send
import CocoaAsyncSocket
import OSCKit

let oscClient = GCDAsyncUdpSocket()

func sendOSCMessage() {
    let data = OSCMessage(
        address: "/some/address/here",
        values: [.int32(1), .int32(2), .string("Test")]
    ).rawData

    oscClient.send(
        data,
        toHost: "<IP_ADDRESS>", // sends to local machine; change this to remote IP/hostname
        port: 8000, // standard remote OSC port but can be changed
        withTimeout: 5.0,
        tag: 0
    )
}

Receive
let oscServer = GCDAsyncUdpSocket()

extension AppDelegate: GCDAsyncUdpSocketDelegate {
    func setupOSCServer() throws {
        oscServer.setDelegate(self)
        oscServer.setDelegateQueue(.global())
        try oscServer.bind(toPort: 8000) // standard local OSC port but can be changed
        try oscServer.beginReceiving()
    }

    func udpSocket(
        _ sock: GCDAsyncUdpSocket,
        didReceive data: Data,
        fromAddress address: Data,
        withFilterContext filterContext: Any?
    ) {
        guard let oscPayload = try? data.parseOSC() else {
            return
        }
        print(oscPayload) // handle received osc bundle or osc message here
    }
}

I was planning on getting an example built really soon. In the mean time, this is the basic implementation.
Just haven't done any usability tests to see if any particular options need to be set on the socket yet.
Entitlements
If your app is for iOS you don't need to set any app entitlements. The user will be asked to allow local network connections the first time you open the UDP port(s).
Make sure if your app is for macOS and is sandboxed, you enable network connections:

Send
import CocoaAsyncSocket
import OSCKit

let oscClient = GCDAsyncUdpSocket()

func sendOSCMessage() {
    let data = OSCMessage(
        address: "/some/address/here",
        values: [.int32(1), .int32(2), .string("Test")]
    ).rawData

    oscClient.send(
        data,
        toHost: "<IP_ADDRESS>", // sends to local machine; change this to remote IP/hostname
        port: 8000, // standard remote OSC port but can be changed
        withTimeout: 5.0,
        tag: 0
    )
}

Receive
let oscServer = GCDAsyncUdpSocket()

extension AppDelegate: GCDAsyncUdpSocketDelegate {
    func setupOSCServer() throws {
        oscServer.setDelegate(self)
        oscServer.setDelegateQueue(.global())
        try oscServer.bind(toPort: 8000) // standard local OSC port but can be changed
        try oscServer.beginReceiving()
    }

    func udpSocket(
        _ sock: GCDAsyncUdpSocket,
        didReceive data: Data,
        fromAddress address: Data,
        withFilterContext filterContext: Any?
    ) {
        guard let oscPayload = try? data.parseOSC() else {
            return
        }
        print(oscPayload) // handle received osc bundle or osc message here
    }
}

Nice one! Thanks Steffan 🙏 Will give this a shot later on!
www.lysdexic.com
www.linktr.ee/lysdexic

On 2 Aug 2022, at 06:52, Steffan Andrews @.***> wrote:

I was planning on getting an example built really soon. In the mean time, this is the basic implementation.
Just haven't done any usability tests to see if any particular options need to be set on the socket yet.
Entitlements
If your app is for iOS you don't need to set any app entitlements. The user will be asked to allow local network connections the first time you open the UDP port(s).
Make sure if your app is for macOS and is sandboxed, you enable network connections:
Send
import CocoaAsyncSocket
import OSCKit
let oscClient = GCDAsyncUdpSocket()
func sendOSCMessage() {
let data = OSCMessage(
address: "/some/address/here",
values: [.int32(1), .int32(2), .string("Test")]
).rawData
oscClient.send(
    data,
    toHost: "<IP_ADDRESS>", // sends to local machine; change this to remote IP/hostname
    port: 8000, // standard remote OSC port but can be changed
    withTimeout: 5.0,
    tag: 0
)

}
Receive
let oscServer = GCDAsyncUdpSocket()
extension AppDelegate: GCDAsyncUdpSocketDelegate {
func setupOSCServer() throws {
oscServer.setDelegate(self)
oscServer.setDelegateQueue(.global())
try oscServer.bind(toPort: 8000) // standard local OSC port but can be changed
try oscServer.beginReceiving()
}
func udpSocket(
    _ sock: GCDAsyncUdpSocket,
    didReceive data: Data,
    fromAddress address: Data,
    withFilterContext filterContext: Any?
) {
    guard let oscPayload = try? data.parseOSC() else {
        return
    }
    print(oscPayload) // handle received osc bundle or osc message here
}

}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

I've also pushed a full example app to the repo:
https://github.com/orchetect/OSCKit/tree/main/Examples/CocoaAsyncSocketExample
I'm working on a 0.3.0 release soon so maybe just pull main branch for the time being.

One thing I am likely planning to implement is optional networking modules.
ie:
This would import just the OSCKit library as it does now.
import OSCKit

But this would import OSCKit along with CocoaAsyncSocket as a dependency and some additional abstractions such as OSCClient and OSCServer. That way you just import this target and all the boilerplate would be done for you.
import OSCKitCAS


Revert "Add chem solution atmos heating and cooling"

Reverts space-wizards/space-station-14#17854
Superheating stations

silly

@0x6273

Oops

i for one like the fact that we are able to compress our stations with pressure and temperatures exceeding that of a neutron star

Apparently, before making a heat conversion system, a thermal control system for the station is needed.

Does anyone know what happened to cause the infinite heating? This never happened during my testing..

does it have something to do with anchored entities heating infinitely

might have to do with solutions interacting with space?

might have to do with solutions interacting with space?

Yeah that seems to be it. Goes to Inf then NaN.


feat/pinecone namespaces support

Added support for using namespaces with pinecone indices (as mentioned in https://github.com/Unstructured-IO/unstructured-ingest/issues/65). Since the Pinecone connections through the python library includes support for namespaces, just added the relevant config attributes in the Config dataclasses, and cli flags.
For testing, in line 106, you can add the flag --namespace test to try namespace support.
Note: This is my first contribution so looking forward to making any changes necessary. All tests for pinecone were passing locally.

Closing since this is related to connectors. Please reopen in https://github.com/Unstructured-IO/unstructured-ingest if needed.


Using headers attribute to define headers in simple data tables

Topic: Table validation - bug
We are fairly sure there is a bug in the table validator at http://fae20.cita.illinois.edu/
Check out http://www.aasb.gov.au/Pronouncements/Current-standards.aspx with a "HTML4 Legacy Technique" Ruleset.
It says tables do not have headers, summary etc when they do. We made certain they do by modifying them to the rules stated.
Can you let us know if this is a bug?

Table rule 1 was updated to allow for table headers using the headers attribute


xClusterQuorum: Fixed the filesharewitness checks.

Pull Request (PR) description
This Pull Request (PR) fixes the following issues:
Fixes #35
Task list:
[ x] Change details added to Unreleased section of CHANGELOG.md?
[ x] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
Previous PR-> https://github.com/PowerShell/xFailOverCluster/pull/141

This change is

@Blankf,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #144 into dev will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            dev   #144   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files         7      7
  Lines       413    413
===================================
  Hits        413    413

Thanks for sending is this PR! Really appreciate this! :smile:

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

CHANGELOG.md, line 3 at r1 (raw file):

# Change log for xFailOverCluster

## Unreleased

Please fix lint errors in this README.md (tests are failing)
https://ci.appveyor.com/project/PowerShell/xfailovercluster/build/1.6.273.0#L374

CHANGELOG.md, line 5 at r1 (raw file):

server 2016 test failed on nodeandfilesharemajority if you used filesharemajority

Please make this more descriptive. What do you think of "When using NodeAndFileShareMajority on Windows Server 2016 any subsequent run failed when Test-TargetResource validated the configuration."?

README.md, line 183 at r1 (raw file):

  NodeMajority.

>Note: if you want to use FileShareWitness, use NodeAndFileShareMajority.

Please add the other two as well
NodeMajority = NoWitness
NodeAndDiskMajority = DiskWitness

README.md, line 183 at r1 (raw file):

use NodeAndFileShareMajority

Maybe "..., use the option NodeAndFileShareMajority."?

DSCResources/MSFT_xClusterQuorum/MSFT_xClusterQuorum.psm1, line 42 at r1 (raw file):

                $clusterQuorumType = 'NodeAndDiskMajority'
            }
            elseif ($getClusterQuorumResult.QuorumResource.ResourceType.DisplayName -eq 'File Share Witness' -or $getClusterQuorumResult.QuorumResource.ResourceType.DisplayName -eq 'File Share Quorum Witness')

Could you please write (add) a unit test for this change?

Comments from Reviewable

Hi Johlju,
changed the readme and changelog, need to take a look later at the tests.

Review status: 1 of 3 files reviewed at latest revision, 6 unresolved discussions.

README.md, line 185 at r3 (raw file):

>Note: if you want to use FileShareWitness, use the option NodeAndFileShareMajority.
>Note: if you want to use DiskWitness, use the option NodeAndDiskMajority.
>Note: if you want to use NoWitness, use the option NodeMajority.

Could you please revise these? If you look at the result here you see that they are concatenated, and 'Note:' is part of the paragraph. Maybe revise these so only one 'Note:' is needed.

Comments from Reviewable

Hi johlju,
can you help me out with the checks, i have looked at them a couple of times but cant seem to get them fixed.

@Blankf Sorry that I haven't answered you for so long! 😞 Shall we try get this one over the finish line now? I can help you with the tests. Maybe you can resolve the review comments? If you don't have time then please check the 'Allow edit from maintainers' to the right here and I will get this one over the finish line,


a Null ResultSet returned from JDBC Driver

The Exception detail message is below:
"Method threw 'java.lang.NullPointerException' exception. Cannot evaluate com.orientechnologies.orient.core.record.impl.ODocument.toString()"
The First found on jdbc driver version :2.0.4
Same occurred on version 2.0.6

Stack trace below:
at com.orientechnologies.orient.core.metadata.OMetadataDefault$ThreadLocalSchemaSnapshot.access$100(OMetadataDefault.java:279)
at com.orientechnologies.orient.core.metadata.OMetadataDefault.clearThreadLocalSchemaSnapshot(OMetadataDefault.java:122)
at com.orientechnologies.orient.core.record.impl.ODocument.getGlobalPropertyById(ODocument.java:1948)
at com.orientechnologies.orient.core.record.impl.ODocumentInternal.getGlobalPropertyById(ODocumentInternal.java:55)
at com.orientechnologies.orient.core.serialization.serializer.record.binary.ORecordSerializerBinaryV0.getGlobalProperty(ORecordSerializerBinaryV0.java:275)
at com.orientechnologies.orient.core.serialization.serializer.record.binary.ORecordSerializerBinaryV0.deserialize(ORecordSerializerBinaryV0.java:175)
at com.orientechnologies.orient.core.serialization.serializer.record.binary.ORecordSerializerBinary.fromStream(ORecordSerializerBinary.java:74)
at com.orientechnologies.orient.core.record.impl.ODocument.deserializeFields(ODocument.java:1754)
at com.orientechnologies.orient.core.record.impl.ODocument.checkForFields(ODocument.java:2186)
at com.orientechnologies.orient.core.record.impl.ODocument.fieldNames(ODocument.java:810)
at com.orientechnologies.orient.jdbc.OrientJdbcResultSet.(OrientJdbcResultSet.java:62)
at com.orientechnologies.orient.jdbc.OrientJdbcStatement.execute(OrientJdbcStatement.java:112)
at com.orientechnologies.orient.jdbc.OrientJdbcStatement.executeQuery(OrientJdbcStatement.java:118)

Please could you try with OrientDB 2.0.7-SNAPSHOT?

To reappear the issue,the scene is:
1.Create new property to an existence Class schema ,furthermore the class already have datas .
2.The previous data no default value set for the new property (NULL)
3.Query by sql via Jdbc.
4.A null resultset returned!
the data server is OrientDB-enterprise-2.0.3
Thanks.

@atboo seems the database was closed during that operation. Could you provide me 10 lines of code that reproduce the problem and I can run by myself?

The issue has been closed because no response has been received after a while. In case the issue is still valid, please reopen it or write a comment that explains why it's still valid and a way to reproduce it. Thank you.


THANK YOU!!

Hi Youseff, just wanted to give a quick thank-you!
No solution I tried so far actually worked as expected... thought I'd have to implement this myself haha.
Thank you for saving so much time.

Hi toorusr,
I am very happy that the repository saved some time.
Feel free to contribute to the project.
Thanks.


feat: inject contract id into the namespace for tests automatically

closes #3673.
About this PR
This PR adds CONTRACT_ID injection while building contracts with forc build --test. CONTRACT_ID is the id of the contract without the tests added. To find out that id, we first compile the contract without tests enabled.
The rough outline of stuff happening here:

We iterate over BuildPlan members to find out contracts and collect their contract id into an injection map. In this step only the contracts are built. To determine contract id we need to compile the contract without tests. Since we also need the bytecode of the contract without tests, we are collecting them as we come across them while iterating over members.
With the injection map build and execute all the tests, so basically after first step we are just doing the old forc-test behaviour.

So basically I added a pre-processing step for contract id collection for those members that require it (contracts).
This enables the following test structure:
let caller = abi(MyContract, CONTRACT_ID);
let result = caller.test_function {}();
assert(result == true)

TODO

[ ] Documentation

I wasn't really happy with how this turned out tbh, thanks for the comment @mitchmindtree! I think the proposal seems it would be a lot cleaner. I will come-up with the implementation tomorrow morning 👍

This should be good to go for another review, I will be introducing a general refactor to forc-test to address some of the left over review comments from earlier PRs.


TypeError "Contents: argument 1 must be str, not bytes"

I found this today when trying to research how to create my own addon to edit a fan config file.
I can't seem to find any information on how to do that, so I figured the best bet was to find an addon as close as to what I'm trying to accomplish and mess around with it to see how it works.
Thankfully I came across this because it's extremely close to the addon that I'm trying to create.
But sadly this doesn't work for the latest version of Kodi(v19 matrix) so I've been trying to port it over.
When doing that, I ran into this error:

Error Type: <class 'TypeError'>
Error Contents: argument 1 must be str, not bytes
Traceback (most recent call last):
File "C:\Users\Joe\AppData\Roaming\Kodi\addons\script.advanced.settings.editor\default.py", line 150, in
gui.showGUI()
File "C:\Users\Joe\AppData\Roaming\Kodi\addons\script.advanced.settings.editor\default.py", line 65, in showGUI
utils.log(node.name + " " + str(node.hasChildren))
File "C:\Users\Joe\AppData\Roaming\Kodi\addons\script.advanced.settings.editor\resources\lib\utils.py", line 15, in log
xbmc.log(encode(addon_id + "-" + __Addon.getAddonInfo('version') + " : " + message),level=loglevel)
TypeError: argument 1 must be str, not bytes

From the information I can gather it looks like it's sending the wrong type of information? It's expecting character(s) and it's getting sent number(s)?
As you can see, I don't know what I'm doing or how this exactly operates, yet.
Can you help me understand this better? Or point me anywhere I can get a better grasp on this whole process.
I forked your repo and you can check out the changes I've made here, but they were all basic changes just to get it to install:
https://github.com/jojobrogess/script.advanced.settings.editor

nvm got it.
But thank god you stole a little bit of your own code and kept updating it for xbmcbackup
https://github.com/robweber/xbmcbackup/blob/aa1421876b14dc70e15b2b4772ab1e1f0f688310/resources/lib/utils.py#L22

Glad you found what you were looking for. The Backup addon is way more up to date since it's actually in the Kodi repo. I had a feeling the encode() function was no longer needed in Python3 but looks like that line confirms it.

If I can do it, it'll probably take me a while.
Which is a good thing for me because in doing this I hope to be able to learn how to create an addon for myself.
But the learning curve on this is a little more than what I expected, especially considering I don't know how to code python.
Just can read it, slightly.
As far as I can tell, this code looks like it's from Frodo/Gotham days.
Kodi 12 and 13 respectively. I thought it was at least Jarvis(16), Krypton(17), or Leia(18).
There's been a considerable amount of changes since then and like I stated above, I have no idea what I'm doing lol.
but I did just update the strings to the new localized standard, but that's an easy task comparatively.
As of right now, I can't get any of the functions to work correctly: Add element/child element, change value, delete, or rename.
As well as some hierarchical problems, the videolibrary art type section displays the correct amount of file types but they all display as "landscape" instead of their individual types.
I suspect it has something do with key changes to how Kodi now operates, plus old function calling.
But since this is made for such an old version of kodi, I think updating it is going to be a little slow for me.
If you can help me out by telling me a few things about the addon, that would be great!
Like what do minidom and expaterror do in correlation to script?
Can you remember any major changes that have happened over the years in Kodi that you are pretty sure you never made to this code? Like eg: the Kodi getString function is depeciated people use the $LOCALIZE process now or this functions name is now this.
Literally any piece of information could help, atm I'm stabbing in the dark lol
I don't know python, I'm new to kodi, and I can barely code lol
And google is yelling at me to enter captcha's ever 30 minutes because of all the nonsense I'm searching up.

I think you're right - this hasn't been touched in a while. Prior to the Kodi migration to Python3 that probably wasn't too much of an issue but I can imagine it's not running quite right anymore. The good news is that the format of the advanced settings file hasn't seemed to have really changed over the years so that's a plus!
I took a quick pass through the code again so hopefully I can answer some of your questions. The minidom import is the Python library that actually parses the advancedsettings.xml file and reads, adds, or removes the information there. By default the GUI portion of the program just pulls in the top level xml nodes and displays them. Clicking a node will bring you in to that node tree, or display the text value if it's just a single tag. If you compare your advancedsettings.xml file to what is being read in you can visualize how it's parsing the tree.
That being said, I'm sure some settings display a bit odd. It's because this addon is generic enough that it doesn't care what the actual format of the file looks like, it just reads the file. The video extensions node you mentioned is a good example. This could be filled with tons of extensions and they will just be displayed as one big string value since they're part of the same xml node. You could add some logic to use a line break after each | character in situations like that; but it's more a consequence of how the file is structured.
A few places that might help:
The Cron For Kodi addon has been updated for Matrix. This has more up to date UI code and might help in that area.
Kodi Python Docs - I'm sure stuff like the xbmcgui.Dialog() calls have changed, these will be located here
Any errors or specific things feel free to reach out.

Alright I'm making headway.
But I'm having a problem with the write function.
I've been trying to isolate the issue by deleting my advancedsettings.xml file, so I can start over and try to see what's going on.
This is the function:

def _writeFile(self):
    file = xbmcvfs.File(self.as_file,'w')
    file.write(str(self.doc.toxml()))
    file.close()

And it outputs <?xml version="1.0" ?><advancedsettings/> in the first line of the file.
I've been able to remove it by adding:

def _writeFile(self):
    file = xbmcvfs.File(self.as_file,'w')
    file.write(str(self.doc.toxml().replace('<?xml version="1.0" ?><advancedsettings/>', '<advancedsettings>\n</advancedsettings>')))
    file.close()

It seems to stop it from adding that line when the file is created, but with every write after it re-adds <?xml version="1.0" ?> to front of the file.
And I have no idea why. I suspect it has to do with the formatting of these two lines:

    file = xbmcvfs.File(self.as_file,'w')
    file.write(str(self.doc.toxml()))

Also it seems that the write function writes linearly(flattens the directory to one line). but I'm not 100% sure that even matters, since the user can't see it and I assume as long as the elements are in the correct placement, like within the <advancedsettings> </advancedsettings> tags and it's corresponding tags it shoudn't matter about how it looks just that it works correctly, but with the icon.png you supplied I assume that's how it saves them.
BUT since I've never ran this while it was working correctly, I don't know.
Did this used to save things in advanced settings like this:

or

Cuz if it did........ I also don't know why that's happening. lol

I've been using the Kodi Documemtation Library website you supplied, which has been an absolute help and a complete cheat sheet when it comes to updating calling things within Kodi. Seriously thank you for that one!
I also have xbmcbackup and cronxbmc github pages bookmarked so I can sift through all of your commits, and see what and how you've changed the code over the years.
But a couple of these things are little too out of my element, or maybe I just haven't caught it yet.
If you could shed some light on this, it would help out a lot!
I'm also pretty sure everything should function correctly after the write function gets fixed.
This was my momentary solution to having the value of the node on the element's name, just so it's easier to read:

but it displays it everywhere:

I was thinking of cleaning it up with something like," elementname's value = value " which might look better than my crude solution. And maybe on the other " elenmentname's tree " or something similar.
Doing it this way does burn the select to view value feature, but that could be changed to select to change value.
Probably would also want to remove it from context menu, since the default selection method for elements without a child would then be to "change value" so it wouldn't be needed, but that doesn't really matter necessarily.
Since this is your script and I do want to submit an updated Matrix PR for this, I thought I'd get your suggestions.
What do you think would look/work best?

Nice work, glad those resources are useful. I like the changes of adding setting = value for the ones that aren't the start of a tree of values. Just makes it easier to read. I agree clicking on the value should then either bring up the context menu or just go straight to changing the value. No reason for an additional screen. I kind of like how you have it in the second picture the best. If something has a folder icon and no = then it's pretty easy to tell it's the start of a tree. Since modifying this file is kind of an advanced thing anyway these visual queues should be enough in my opinion.
Regarding the XML declaration statement (<?xml version ....) is Kodi not reading the file correctly if this exists? Having that top line to declare that this is an XML file type is part of the document standard; however I know some parsers (written incorrectly I suspect) will throw a fit if it's there. Your solution to remove it works if you have to but it probably shouldn't cause any harm to be there. I did run across a method in the Minidom documentation called toprettyxml() that will write out the file with the correct newlines and indents. My guess is that I never went this far with it but it does add some viewability for users (or you when testing!). You could even add a setting for the addon to toggle "pretty" xml vs just the one line output. That's probably going a bit overboard but people like options!
Based on the comments sounds like it's going pretty good so far. Looking forward to seeing the end result.


feat: adding a template for pull requests

Issue
Closes #18
Proposed Changes
This pull request adds a template for pull requests. It’ll help contributors, especially those who are new to open source, effectively describe their proposed contributions

looka good thanks


[Flink-1815] [gelly] Add methods to read and write a Graph as adjacency list

Added functionality for Jira Issue [FLINK-1815] Add methods to read and write a Graph as adjacency list

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.


ima-evm-utils: apply upstream fix for attr-2.4.48 compatibility

Motivation for this change
Fix build for release 19.03 by applying upstream patch. (In context of https://github.com/NixOS/nixpkgs/issues/53716)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build ima-evm-utils


[WIP][DO NOT MERGE] add Gomfile importer

Adds Gomfile importer support to init.
TODO

add detection for production/test environments

I consider about production/develop environments for gom. But maybe, all of packages writen in Gomfile should be exported in Gopkg.toml. So I'll remove [WIP] and [DO NOT MERGE].

bump

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


Server error if user applies a default tag manually

I've got this plugin installed and working correctly (I think!), but I've been getting the following server error when a user tries to create a new post with a default tag manually applied:

ActiveRecord::RecordNotUnique (PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "index_topic_tags_on_topic_id_and_tag_id"
DETAIL:  Key (topic_id, tag_id)=(196, 28) already exists.
)
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-2.0.1/lib/patches/db/pg.rb:69:in `exec_params'

I tried to see if I could propose a pull request, but I'm afraid my very limited knowledge of Ruby would only make things worse. I believe a solution would be to check if a tag already exists on a new post before applying a default tag.
Thanks for sharing this great plugin!

Hey theopen. Glad this is almost working for you.
I applied an untested fix. Can you give it a shot and tell me if it works?

I didn't mean to close this.

Seems to be working great! I'll post back if I encounter any unexpected behavior, but on 15 minutes of testing it seems to be fixed. Thanks again!

Great! That's quite a relief. I am pretty sure that's the fix (I should have written it that way to start, now that I think about it!). If it works at all, I'm fairly certain that we're safe.
Thanks for letting me know!


Timout error

iam getting a timeout error everytime i try to connect with a virtual server, here is the throwable
cz.msebera.android.httpclient.conn.ConnectTimeoutException: Connect to vps-1132422-16434.manage.myhosting.com/<IP_ADDRESS>:8080 timed out
it seems like the "cz.msebera.android:httpclient:4.3.6" version have some issues, can you please update to the latest version "4.4.1" and update your library

did you find any solution ?


Is it logical to still use formsy-react?

Hi everyone, it seems like there's no clear maintainer of this project anymore, should I still continue using this or just go with other form validation libraries? I'm a react beginner and this one's the easiest to use so far.

Definitely not. It's really worth it switch to the redux-form library, this project is death and the maintainer don't reply to any requests in this repo (there was some requests about a takeover too but no response). This library is easier to use at the first sight since it uses internal states and the context functionality of react instead of i.e. redux.

Yes: Development is being picked up again, see
https://github.com/christianalfoni/formsy-react/issues/301#issuecomment-211562388

@aight8 not everybody is using or needs redux.  I think its good to support libraries like Formsy that apply a minimal approach to form management without extra dependencies.  While Formsy isn't the best for your use case, it doesn't diminish its value for others.


Prometheus / Mimir : Dynamic tenant id from metric label like Loki

Background
Mimir support multi tenancy like Loki with header in the request, I suppose Loki.write read tenant label in the logs to replace
default tenant_id in the endpoint (like Promtail does).
Today I use cortex-tenant as proxy between Prometheus and Mimir, I use writeRelabelConfig to regex the namespace label and create the tenant label. Cortex-tenant read the tenant label in metric and add the header to the request.
It could be better to implement this directly from Alloy instead use proxy only for doing that's job.
Proposal
This functionality can be implemented in prometheus.remote_write or with a specific mimir.remote_write.

@Ronan-WeScale  could this be a duplicate of #521 ?

@wilfriedroset of course, sorry for duplicate, I tried to search before create this issue.
But https://github.com/grafana/alloy/issues/521 seem stuck from long time.


Outdated cask: screenmailer

Outdated cask: screenmailer.
Info:

version: 2.0.5.
appcast url: https://www.screenmailer.com/releases/current/releases.xml.

Please do not run find_outdated_appcasts unless you are a maintainer.


Uploaded Video thumbnail not display at all.

Recently I have written the code to Video upload in chat and I use SendBird demo project code to upload Video in chat, but the issue is Thumbnail not display in uploaded video.
I try this in SendBird demo as well as in my project, but facing the same issue in both.
I also follow this Docs to generate the thumbnail from video url but no luck.
https://docs.sendbird.com/ios/group_channel_advanced
I use this like below.
// success, data is in imageData
/***********************************/
/* Thumbnail is a premium feature. */
/***********************************/
let thumbnailSize = SBDThumbnailSize.make(withMaxWidth: 320.0, maxHeight: 320.0)

let preSendMessage = self.groupChannel.sendFileMessage(withBinaryData: (videoFileData! as Data), filename: (videoName as String), type: mimeType, size: UInt((videoFileData?.length)!), thumbnailSizes: [thumbnailSize!], data: "", customType: "", progressHandler: nil, completionHandler: { (fileMessage, error) in
    //My Code
}

Once the video uploaded, Video plays successfully.
Please help me regarding this.
Thanks in advance

Hi, @StellarKuldeep
Let me know the App ID in AppDelegate.swift of SendBird demo app that you see.
Do not post your App ID here.
Thanks.

@sf-jed-kyung , Thank for your reply. My App ID of SendBird demo app is 9DA1B1F4-0BE6-4DA8-82C5-2E81DAB56F23

@sf-jed-kyung , Thank for your reply. My App ID of SendBird demo app is 9DA1B1F4-0BE6-4DA8-82C5-2E81DAB56F23

@famous90 May i know why you close this question?

@StellarKuldeep sorry to miss close.

@StellarKuldeep The thumbnail feature is enabled on the demo app. I think the filename and the mime type cause the problem. Let me know the values of them.

@sf-jed-kyung  Filename is 8BD990A9-76EF-45C9-94D5-343194FCD4E8.MOV and mimetype is  video/quicktime

@sf-jed-kyung Today i am not able send text messages, Image/video file message.
When i send any message to any one then it shows me status as sending but when i go back and come again then image/video file message is not there.
Please find the attached screenshot, as you can see the file message status is sending.

When i try to Resend message then i'm getting an error like below screen.

In above screenshots, There's no video thumbnail available.
Please help me regarding this.

@StellarKuldeep  I'm really sorry. The permission option of the demo app was wrong and I've changed it. Could you try it again?

@sf-Jed-Kyung, Thanks, Text messages, chat now works fine but still i am facing video thumbnail problem. Please help me regarding this.

@StellarKuldeep The filename and the mime type are normal.  The debugging is not easy now. So, can you create a group channel and invite sendbird_test_jed user to the channel on the demo app? If you send a video in the channel, then I'll take a look into the thumbnail issue.

@sf-jed-kyung , I have created 1 group channel and invite you sendbird_test_jed and  i was able to send 2 text messages and then i faced below error.

I already send video in this channel and I attached a screenshot. It shows me only "SENDING" and once i go back from this channel and come back to this channel, the sent video was gone.

Please help me about this.

@StellarKuldeep I turned off the profanity filter. Can you try to upload a video again? I'm watching that channel.

@sf-jed-kyung  few minutes ago I uploaded the video in created channel but video not sent successfully and still thumbnail doesn't generate.

@StellarKuldeep
I can see the thumbnails.
Could you compare your implementation with this?

@sf-Jed-Kyung yes, the highlighted code exists in both IncomingVideoFileMessageTableViewCell & outgoingVideoFileMessageTableViewCell

@StellarKuldeep I tested the project of this repo without any modification.

@sf-jed-kyung , yes, but i have been facing this issue in the newly downloaded demo. Will you please try to send video from your end and check weather video thumbnail shows from your end or not?

@StellarKuldeep same happens to me also I have cross-checked all the code and still  no video preview on chat

@abdulKarim002 , Still video preview isn't generating. If you found any solution then please let me know.

@StellarKuldeep Can you take a look at this how to generate thumbnail guide?

@erickimme , It not open source guide, it asks me to request access.

@StellarKuldeep  Hi, I just send you an email with how to generate thumbnail guide since I can't attache a file here.

@erickimme , I have tried that code but what should I pass in below code?
self.chattingView.preSendFileData[preSendMessage?.requestId!] = [
                    "data": videoFileData as AnyObject,
                    "type": mimeType as AnyObject,
                ]
self.chattingView.preSendMessages[preSendMessage.requestId!] = preSendMessage
self.chattingView.messages.append(preSendMessage)
self.chattingView.chattingTableView.reloadData()
DispatchQueue.main.async {
    self.chattingView.scrollToBottom(force: true)
}


Remove instances of auxiliary heating

This Pull request tries to remove the deprecated aux_heating feature from the climate entity.

@georgezhao2010 I have made an attempt to remove aux heating, probably removing some functionality. Let's work together in the PR so we can remove the deprecated instance.
I haven had the chance to test this out on my setup yet. I will post comments after I test with my devices. Unfortunately I have only 1 kind. ANYONE USING THIS PR MIGHT BE UNSTABLE AND USE AT YOUR OWN RISK

Closing the PR since there are other PRs waiting to be merged for the same reason


Remove unused tests, disabled known issues and remove LogCollector

@enmasse-ci run tests profile=smoke test_only

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 3
FAIL: 0
SKIP: 0
BUILD_NUMBER: 344


Linux Fuchsia: Download for build xxxx failure

We are repeatedly seeing failures on Fuchsia Linux bots in https://ci.chromium.org/p/flutter/g/engine/console
The failed steps are in Download for build xxxx.  The logs won't load and don't seem helpful. to me.
Example: https://ci.chromium.org/p/flutter/builders/prod/Linux Fuchsia/5894

The problem is this build is taking more than an hour and it is being killed by a timeout. I'm checking whether the execution time have increased or if this is just a side effect on setting task execution timeout to one hour.

This is a cold vs hot cache.

On the passing task checking out the source code takes ~3mins and in the failing one ~7mins
On the passing task building fuchsia tests takes ~4 mins and in the failing one ~12.

Increasing the timeout for this build to 1 hour and half as with cold caches it takes a little bit more than an hour to complete.

Moving to P1 while we monitor the new builds


cockroach debug zip Doc Update for CockroachCloud

Re: cockroach debug zip
Issue Description
It would be good to have a cockroach debug zip page specific to CockroachCloud. On this page there is a description of the --url option that could potentially be used to get a debug out of cloud (I haven't test this) but it's unclear that one might use that for cloud.
Suggested Resolution
Create a cloud specific page with directions for getting a debug zip.

Closing in favor of CC-3692


Sync with C SDK MQTT (526989a)

Description
Updates MQTT files to commit https://github.com/aws/aws-iot-device-sdk-embedded-C/commit/526989a69215fc991eb737258a4d1b6181b50c15. See commits on C SDK for details.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It's great to see this sync'ing going on - it gives hope to those of us that have to support both Amazon FreeRTOS and the C SDK.  :)
Are there any plans or roadmap to make the C SDK a git submodule in the amazon-freertos repo?  That should simplify this sync exercise, and further assert that bug fixes/features should be made in the authoritative source, which is the C SDK code base.  Plus, if the C SDK has a new feature/fix I want in my amazon-freertos fork, I could simply update the submodule myself.

It's great to see this sync'ing going on - it gives hope to those of us that have to support both Amazon FreeRTOS and the C SDK. :)
Are there any plans or roadmap to make the C SDK a git submodule in the amazon-freertos repo? That should simplify this sync exercise, and further assert that bug fixes/features should be made in the authoritative source, which is the C SDK code base. Plus, if the C SDK has a new feature/fix I want in my amazon-freertos fork, I could simply update the submodule myself.

Thanks Chris for your interest and query. We are committed to supporting our community on Amazon FreeRTOS and the C SDK. We plan to link C SDK and the Amazon FreeRTOS repos through the git submodule mechanism. Please watch this space as we work through executing our plan.

/bot run checks


chore(main): release 0.0.1

:robot: I have created a release beep boop
0.0.1 (2024-05-01)
Bug Fixes

add production stage to Dockerfile (427a05c)
add ReconcileFlaggedCVERule and update global manifest (c2b954c)
group version, namespace, vuln counter (62fbc75)
helm chart nil pointer dereference for SA (42f47f3)
include all src code in Dockerfile build context (525b3e7)
rename charts to chart (96a1825)
typo (eae9f24)
update v1 to v1alpha1 and CRD (9a50145)
v1 to v1alpha1 (7cf2316)

Other

add extra files (d4bfa93)
add github workflows (be53017)
deps: update actions/checkout digest to 0ad4b8f (#19) (9f389b8)
deps: update azure/setup-helm digest to fe7b79c (#20) (deee20d)
deps: update codecov/codecov-action digest to 5ecb98a (#21) (53760d4)
release 0.0.1 (27d0852)
release 0.0.1 (5fa1a9b)
upgrade controller-gen (eb6ab5a)
upgrade github.com/docker/docker (7d6417c)
upgrade github.com/kubescape/storage (358cb4f)
upgrade golang.org/x/net (4488f72)
upgrade to go1.22 (c2c1bf8)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/spectrocloud-labs/validator-plugin-kubescape/releases/tag/v0.0.1 :sunflower:


Task 9

5 Points are assured. No Errors found by AI system, you must be really good in writing uipath code. An expert need to review your code and it will be done before next sunrise :)

5 Points are assured. No Errors found by AI system, you must be really good in writing uipath code. An expert need to review your code and it will be done before next sunrise :)

5 Points are assured. No Errors found by AI system, you must be really good in writing uipath code. An expert need to review your code and it will be done before next sunrise :)

@Navneeth1996
Task -9
Code verified.
Task -10
Code verified.
Task -11
Code verified.


See if we can read slow down penalty info

Maybe an initial call followed by 2 or 3 reminders as the time owed ticks down. If the data is available

iRacing sends "blackflagfolded" when user have a slow down, and then you have to comply within a given time else it converts in to a drive-through.

no data is available in R3E. There's a TimeDeduction integer, but I think this is just the time added at the end of a race for penalties (a whole number of seconds)

we don't know how much time we need to give back, but I've added a 'you need to slow down or you'll get a penalty' message - this is only allowed to play once per lap


Use fallback for widget label translation

1. Why is this change necessary?
Not having a translation for a given language results in NULL for the label making it hard to identify the widget.
2. What does this change do, exactly?
Adds a fallback chain to resolve to the internal widget name instead returning NULL if no translation exists.
3. Describe each step to reproduce the issue or behaviour.

Create a plugin which adds an widget:

$plugin = $context->getPlugin();
$widget = new Widget();
$widget->setName('my-widget');
$widget->setPlugin($plugin);
$plugin->getWidgets()->add($widget);

As you already see the label prop is phased out and replaced by the better fitting snippet management.

Now install the new plugin, reload your backend and try to add the widget. Instead of a name null will be provided.

4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-24437
Please use this issue to track the state of your pull request.

Thanks for your Contribution! :blue_heart:


Support .net core 3.0

Hi Guys, I have faced an issue
:
Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Failed to launch DeviceAgent ExitCode: 64 xcodebuild: error: option 'Destination' requires at least one parameter of the form 'key=value' Stack trace:    at Xamarin.UITest.iOS.iOSAppLauncher.LaunchAppLocal(IiOSAppConfiguration appConfiguration, HttpClient httpClient, Boolean clearAppData)    at Xamarin.UITest.iOS.iOSAppLauncher.LaunchApp(IiOSAppConfiguration appConfiguration, HttpClient httpClient, TestCloudiOSAppConfiguration testCloudAppConfiguration, HttpClient testCloudWsClient, HttpClient xtcServicesClient, Boolean testCloudUseDeviceAgent)    at Xamarin.UITest.iOS.iOSApp..ctor(IiOSAppConfiguration appConfiguration, IExecutor executor)    at Xamarin.UITest.iOS.iOSApp..ctor(IiOSAppConfiguration appConfiguration)    at Xamarin.UITest.Configuration.iOSAppConfigurator.StartApp(AppDataMode appDataMode)    at TEstCore.Tests.Test3() in /Users/ymatviienko/Projects/TEstCore/TEstCore/UnitTest1.cs:line 29
With such configuration:

NUnit 3.12.0

Xamarin.UITest 3.0.5(same issue with 3.0.6. dev)

iOS 13.3 simulator

XCode 11.3

.netcore 3.0
When I have the same configuration but with NET framework 7.7.2, all works well.
Does Xamarin.UITest support .netcore 3.0?

Sadly, the answer is no - it doesn't support .NET Core or 5.


Unused parameter n in numpy.from_generator

It seems like the parameter n, total number of samples, in mmap_ninja.numpy.from_generator isn't actually used. Removing it would make it easier to store an a priori unknown number of samples of the same shape.

Thanks for the issue! This is a leftover from the previous generator. We'll remove this and update you here!

The n parameter is now removed in v0.6.4:
http://microlib.org/mmap_ninja/#create-a-numpy-memmap-from-a-generator
Thanks once again for the issue!


Feature Request: Make the intro pasteme-cli installer command fancier

Give a glowing gradient-like background color to the installation div to make it much more special!

Hi, I tried to give the parent element div a class name glow and then the following code worked for me. hope you enjoy it:
<style>
    .glow pre{
        padding: 3px;
        border-radius: 15px;
    }
    .glow pre code {
        border-radius: 15px;
    }
    .glow {
  position: relative;
  border-radius: 15px;
  padding: 0 2px;
  margin: 2px;
}

.glow:before {
  content: "";
  position: absolute;
  top: 0;
  left: 0;
  z-index: -1;
  width: 100%;
  height: 100%;
  background: white;
  filter: blur(5px); /* remove or reduce this amount if the shape is too blur */
  border-radius: 15px;
}

.glow:after {
  content: "";
  position: absolute;
  top: -2px;
  bottom: -2px;
  left: -2px;
  right: -2px;
  z-index: -2;
  /* take care of browser compatibility here for linear background */
  background: linear-gradient(45deg, #00ddff, #0800ff, #bf00ff, #ff0095, #ff0000);
  filter: blur(15px);
}

</style>

Thank you @mh-firouzjah jan. It's implemented now.


Push master to live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Consume-Packages/Package-Restore.md
:white_check_mark:Succeeded

docs/Release-Notes/Known-Issues.md
:white_check_mark:Succeeded

docs/Schema/Target-Frameworks.md
:white_check_mark:Succeeded

docs/Schema/nuget-config-file.md
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded

docs/Tools/Package-Manager-UI.md
:white_check_mark:Succeeded

docs/What-is-NuGet.md
:white_check_mark:Succeeded

docs/archive/config-priority-order.md
:white_check_mark:Succeeded

docs/archive/readme.md
:white_check_mark:Succeeded

docs/docfx.json
:white_check_mark:Succeeded

docs/index.md
:white_check_mark:Succeeded

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


SonarQube analysis report not showing on build summary when using Gradle Build Task

Hello,
I have a lot of builds using Gradle with Sonar Analysis and after upgrading to TFS 2017.1, the sonar's section that used to be in Build Summary won't appear anymore.
Another Code Analysis tools are working well (eg. checkstyle), but Sonar not... how can I troubleshoot that?

We can start troubleshooting by enable debug logs.  Set "system.debug" to "true" from the Variables tab in your build definition.  The log should give us more context.
Thanks!

I attached the log here. Although every thing looks ok for me, there are no sonar section in build summary...
log_gradle.txt
ps: The sonar is on version 5.6.2

Thanks for the log.  I think there is a bug in the code.  I will create a pull request with a fix soon.

#3823 merged.  Since you are on TFS, we need to manually apply the patch with tfx cli tool.

It's worked! Thanks!
Since the version with bug is bundled in TFS 2017.1, I suppose that I'll have to manually update this task in every install, is it correct? I'm asking that because i'm act as ALM Consultant and I manage many TFS installations...

Unfortunately you need to update all affected servers.  :(  Sorry for the inconvenience.


Update README.md

Don't lock to minor version

Hi there!
As TypeCheck currently is not yet at a stable v1, it seems more prudent to lock to a more precise version.
While SemVer does not require it, we use patch versions already in a forward-compatible manner (for introducing bugixes) and using minor fixes when introducing new features (which sometimes include breaking changes).
Therefore, we currently specify that someone should lock to the minor version in the README.
However, thank you for spotting that the version that is currently mentioned in the README is outdated! :blush:


Implement rule that there can be only one raceplan for a given event.

Now the event can have multiple raceplans. This is an error. An even can have 0 or 1 raceplans.

Solved by 5023929


Add transaction confirmation screen

Add transaction confirmation screen (currently reverts back to token list but hangs on the transaction screen while submitting)

@BrandtH22 is this still an issue, now that the coins will be displayed as pending a transaction? In other words, was the problem lack of UI feedback or lack of confirmation?

I think the transaction confirmation that does appear would be nice to have the coinIDs that will be used in the transaction but that could be me just liking to have more data than needed

I think the transaction confirmation that does appear would be nice to have the coinIDs that will be used in the transaction but that could be me just liking to have more data than needed

I think maybe having a generic transaction confirmation screen that shows all inputs and outputs would make sense. So it builds the full spend bundle, displays it, then adds it to the transactions table if confirmed. This could be reused for WalletConnect and offers


Fixed tag names for Sql

@SenthuranSivananthan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@SenthuranSivananthan : Thanks for your contribution to the Azure documentation! The author, @jimdial, has been notified to review your proposed change.

@SenthuranSivananthan, thanks for catching. #sign-off


OperatorSources errors for marketplace-operators

Thanks for addressing this issue #732 . If the operators have been enabled, then shouldn't the results of >"oc get opsrc -n openshift-marketplaceOperator Sources" show STATUS/MESSAGE of "Succeeded / The object has been successfully reconciled".
My results are:
"Configuring / Get https://quay.io/cnr/api/v1/packages?namespace=certified-operators: dial tcp: lookup quay.io on <IP_ADDRESS>:53: server misbehaving"
The logs for the pod shows apparent issue resolving the package:
certified-operators-6db888f478-xlw8n    1/1     Running   3          20d
community-operators-79c9d7f5f8-rf4bt    1/1     Running   3          20d
marketplace-operator-7fd7d89795-2rjj9   1/1     Running   3          20d
redhat-operators-78f7b4b78f-trczw       1/1     Running   3          20d
C:\Users\GlennNonAdmin>oc logs certified-operators-6db888f478-xlw8n -n openshift-marketplace
time="2019-10-17T16:53:30Z" level=info msg="Using in-cluster kube client config" port=50051 type=appregistry
time="2019-10-17T16:53:37Z" level=info msg="operator source(s) specified are - [https://quay.io/cnr|certified-operators]" port=50051 type=appregistry
time="2019-10-17T16:53:37Z" level=info msg="package(s) specified are - kubeturbo-certified,storageos,insightedge-operator,instana-agent,mariadb,sematext,cic-operator,newrelic-infrastructure,synopsys-certified,percona-xtradb-cluster-operator-certified,percona-server-mongodb-operator-certified,appsody-operator-certified,federatorai-certified,twistlock-certified,couchdb-operator-certified,planetscale-certified,robin-operator,appdynamics-operator,memql-certified,portworx-certified,t8c-certified,anchore-engine,crunchy-postgres-operator,joget-openshift-operator,presto-operator,mongodb-enterprise,hazelcast-enterprise-certified,openunison-ocp-certified,kong,couchbase-enterprise-certified,sysdig-certified,nuodb-ce-certified,oneagent-certified,orca,aqua-certified,tidb-operator-certified,cpx-cic-operator,seldon-operator-certified" port=50051 type=appregistry
time="2019-10-17T16:53:37Z" level=info msg="input has been sanitized" port=50051 type=appregistry
time="2019-10-17T16:53:37Z" level=info msg="sources: [https://quay.io/cnr/certified-operators]" port=50051 type=appregistry
time="2019-10-17T16:53:37Z" level=info msg="packages: [kubeturbo-certified storageos insightedge-operator instana-agent mariadb sematext cic-operator newrelic-infrastructure synopsys-certified percona-xtradb-cluster-operator-certified percona-server-mongodb-operator-certified appsody-operator-certified federatorai-certified twistlock-certified couchdb-operator-certified planetscale-certified robin-operator appdynamics-operator memql-certified portworx-certified t8c-certified anchore-engine crunchy-postgres-operator joget-openshift-operator presto-operator mongodb-enterprise hazelcast-enterprise-certified openunison-ocp-certified kong couchbase-enterprise-certified sysdig-certified nuodb-ce-certified oneagent-certified orca aqua-certified tidb-operator-certified cpx-cic-operator seldon-operator-certified]" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="skipping operator source due to error: https://quay.io/cnr/certified-operators" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="the following packages could not be resolved: map[anchore-engine:false appdynamics-operator:false appsody-operator-certified:false aqua-certified:false cic-operator:false couchbase-enterprise-certified:false couchdb-operator-certified:false cpx-cic-operator:false crunchy-postgres-operator:false federatorai-certified:false hazelcast-enterprise-certified:false insightedge-operator:false instana-agent:false joget-openshift-operator:false kong:false kubeturbo-certified:false mariadb:false memql-certified:false mongodb-enterprise:false newrelic-infrastructure:false nuodb-ce-certified:false oneagent-certified:false openunison-ocp-certified:false orca:false percona-server-mongodb-operator-certified:false percona-xtradb-cluster-operator-certified:false planetscale-certified:false portworx-certified:false presto-operator:false robin-operator:false seldon-operator-certified:false sematext:false storageos:false synopsys-certified:false sysdig-certified:false t8c-certified:false tidb-operator-certified:false twistlock-certified:false]" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="download list is empty, bailing out: [kubeturbo-certified storageos insightedge-operator instana-agent mariadb sematext cic-operator newrelic-infrastructure synopsys-certified percona-xtradb-cluster-operator-certified percona-server-mongodb-operator-certified appsody-operator-certified federatorai-certified twistlock-certified couchdb-operator-certified planetscale-certified robin-operator appdynamics-operator memql-certified portworx-certified t8c-certified anchore-engine crunchy-postgres-operator joget-openshift-operator presto-operator mongodb-enterprise hazelcast-enterprise-certified openunison-ocp-certified kong couchbase-enterprise-certified sysdig-certified nuodb-ce-certified oneagent-certified orca aqua-certified tidb-operator-certified cpx-cic-operator seldon-operator-certified]" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="download complete - 0 repositories have been downloaded" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="No operator manifest decoded" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="decoded 0 flattened and 0 nested operator manifest(s)" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=error msg="the following error(s) occurred while preparing the download list: Get https://quay.io/cnr/api/v1/packages?media_type=helm&namespace=certified-operators: dial tcp: i/o timeout" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=error msg="stat failed on target directory[downloaded] - stat downloaded: no such file or directory" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=warning msg="strict mode disabled" error="error loading manifests from appregistry: [error downloading manifests: Get https://quay.io/cnr/api/v1/packages?media_type=helm&namespace=certified-operators: dial tcp: i/o timeout, error loading operator manifests: stat downloaded: no such file or directory]" port=50051 type=appregistry
time="2019-10-17T16:54:07Z" level=info msg="serving registry" port=50051 type=appregistry
https://github.com/code-ready/crc/issues/732

@gmurray88 This looks like we had issue with bundle since it is produced by using nightly bits of 4.2, please wait for till 23 Oct, we are planning to release new bits which will have fix for this issue.

@jsliacan We need to add a integration test for it so we know it doesn't happen.
$ oc get opsrc -n openshift-marketplace
NAME                  TYPE          ENDPOINT              REGISTRY              DISPLAYNAME           PUBLISHER   STATUS      MESSAGE                                       AGE
certified-operators   appregistry   https://quay.io/cnr   certified-operators   Certified Operators   Red Hat     Succeeded   The object has been successfully reconciled   47h
community-operators   appregistry   https://quay.io/cnr   community-operators   Community Operators   Red Hat     Succeeded   The object has been successfully reconciled   47h
redhat-operators      appregistry   https://quay.io/cnr   redhat-operators      Red Hat Operators     Red Hat     Succeeded   The object has been successfully reconciled   47h

The integration test is tracked in #786 if I'm not mistaken, closing.


line aggregation not working correctly

Just started going through the aggregations for GZ Bar Lengths (project_id == 3). In early spot-checking I came across this subject (493223):

which has 49 line drawings in the relevant workflow (workflow_id = 3, workflow_version = 56.13). Here they are in raw form:

I can't show the aggregated lines because the aggregations report no lines for this subject (despite overall reporting 21,554 aggregated line markings for 7,716 subjects).
Something's gone wrong and I'm not sure what because I haven't checked many other subjects, but I wanted to report this right away.
Really hope this is minor and just because I'm doing something wrong.

Hi all,
Some further checks have shed a bit more light on this.
I've found several more examples where the bar is obvious, p_bar is high, and I'd have expected the clustering performed in the aggregations to have found something, but it didn't:
(Subject IDs 493235, 493211, 465153, 465079)

And here are 3 where the p_bar is actually lower so there were fewer lines drawn total (in general), but the aggregations still managed to return something (yellow are aggregated lines, with line transparency scaled by p_true_positive):
(subject_ids 465075, 465074, 493231)

The aggregated lines sometimes miss one of the measurements as well (there's no yellow line showing width immediately above, or length directly above that) -- but in these cases it's not because the lines aren't detected after clustering, it's because multiple lines with very similar properties were detected at roughly equal (and low) probability.
This is best shown by plotting all the lines reported by the aggregations for the last galaxy above in the same strength of yellow regardless of their p_true_positive:

This subject has detected multiple lines for both the length and the width, and the lines are almost on top of one another. With so many detections, the probability is diluted, so none of them come up as real. For any reasonable cutoff on p_true_positive, I'm often going to miss a measurement that's there in the raw data.
To me this says the criteria for defining a cluster are too restrictive. I think the raw (green) line drawings are really very good in all these subjects (especially in the one where there are 2 barred galaxies and every single volunteer actually followed our instructions and only classified the main galaxy), so I suspect this tightness of line clustering is pretty typical of a project involving line drawings. Thus I'm concerned the line aggregations need more tweaking before they should be used more generally with confidence.
(Side note: we should really give projects the option of tweaking their aggregation parameters... but that's an enhancement.)

After looking through things here I'm wondering if this is related to #144 ? (cc @alexbfree @chrislintott) These marks are overlapping by request - but also I don't understand why that should be a problem as they are very different from each other. If I plot raw marks for any of these by, e.g., [origin, r, theta], or [slope, intercept, length], they separate pretty well into 2 different areas of parameter space. So for reasonable choices for distance cutoff, a hierarchical clustering algorithm ought to do the trick.
I've tested this by applying my own hierarchical clustering, selecting the cutoff distance for defining a cluster as the maximum distance permitted while still requiring that the number of markings registered does not exceed the total number of classifications. That's slightly different than requiring that a cluster not contain 2 marks from the same user, but I did that because we know we have a (small but) non-zero duplication rate, and I haven't removed duplicates yet.
Taking the last example shown above, here's how that comes out:

In my spot-checking, there's still the occasional case where either the bar length or the bar width has more than 1 clustered result with p_true_positive > 0.3 (where I'm defining that as the number of marks in the cluster divided by the number of classifications where the user made any marks), but it's ~0.5% of the total number of subjects with at least 2 detected clusters above that threshold, so I think that's quite good.
This has made me think that:

my side note above is actually really important - my method of finding d_max for a given subject is good for this project, where I know there are likely to be only 2 clusters per subject, but it's probably pretty bad for other projects. Perhaps it's possible to intuit what the researchers need/want some of the time, but that seems very complex -- we could just ask them for each project.
this bit is completely different from the first set of subjects I showed above that are totally missing clustering results. Here's one of those subjects, clustered with my method:

No problems with any of the others, either. So I'm left thinking that is really a bug rather than a choice of method. If the clustering depends on having no duplicate marks from the same user in the same cluster, and given that some of the early stages of live Panoptes had much higher duplicate rates, could that be causing a problem here?


How to add changes

Hello
I love freeboard and plan to use it company-wide!
I am pretty new to JS and I am stuck. The table plugin (https://github.com/daleroy1/freeboard-table) requires me to change the widget model. I do that and add the line as indicated to lib\js\freeboard\WidgetModel.js.
Unfortunately, the change never shows up on my loaded page. I do assume that it has something to do with the minified version.
Can anyone give me hint on how to proceed? Many thanks.
Christophe

Hi Christophe,
Try using index-dev.html, as opposed to index.html which refers only to the
minified libs.
Vish
On Mon, Apr 13, 2015 at 3:09 PM, Christophe Galli<EMAIL_ADDRESS>wrote:

Hello
I love freeboard and plan to use it company-wide!
I am pretty new to JS and I am stuck. The table plugin (
https://github.com/daleroy1/freeboard-table) requires me to change the
widget model. I do that and add the line as indicated to
lib\js\freeboard\WidgetModel.js.
Unfortunately, the change never shows up on my loaded page. I do assume
that it has something to do with the minified version.
Can anyone give me hint on how to proceed? Many thanks.
Christophe
—
Reply to this email directly or view it on GitHub
https://github.com/Freeboard/freeboard/issues/108.

Thanks Vish, very helpful :-)

@christophegalli / @bugvish -- I'm doing cleanup on issues that predate me. Can this be closed?

As far as I am concerned, yes. Thank you.


[HUDI-4855] Add missing table configs for bootstrap in Deltastreamer

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@codope I fixed the tests.  Let's see if the CI can pass now.


Merging latest changes into main

Added Proposal documents
Added empty headers
Added codecov badges

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


dart compile jit-snapshot does not work with program arguments

dart compile jit-snapshot -h yields:
Compile Dart to a JIT snapshot.

Usage: dart compile jit-snapshot [arguments] <dart entry point>
-h, --help      Print this usage information.
-o, --output    Write the output to <file name>.
                This can be an absolute or relative path.

Run "dart help" to see global options.

dart compile jit-snapshot -o nbody.snap nbody.dart works fine.
dart compile jit-snapshot -o nbody.snap nbody.dart 50000000 results in an error:
Missing Dart entry point.

Usage: dart compile jit-snapshot [arguments] <dart entry point>
-h, --help      Print this usage information.
-o, --output    Write the output to <file name>.
                This can be an absolute or relative path.

Run "dart help" to see global options.

dart --snapshot=nbody.snap --snapshot-kind=app-jit nbody.dart 50000000 still works fine.
In addition, the [arguments] in the help output is ambiguous. Does it mean arguments to dart compile jit-snapshot? Or does it mean arguments to my program (in this case, 5000000)?
Also, why not put a few examples in the help output?

/cc @bkonyi


Racer build fails

OS: OSX 10.10.3
cargo 0.0.1-pre-nightly (84d6d2c 2015-03-31) (built 2015-03-31)
rustc 1.0.0-beta (9854143cb 2015-04-02) (built 2015-04-02)
git branch: master , checked out today

$cargo build
Compiling rustc-serialize v0.3.12
Compiling toml v0.1.20
Compiling racer v0.0.1 (file:///projects/rust/racer)
src/racer/ast.rs:41:17: 41:37 error: type &mut syntax::parse::parser::Parser<'_> does not implement any method in scope named parse_stmt_nopanic
src/racer/ast.rs:41         match p.parse_stmt_nopanic() {
^~~~~~~~~~~~~~~~~~~~
src/racer/ast.rs:54:13: 54:18 error: mismatched types:
expected syntax::ast::Crate,
found core::result::Result<_, _>
(expected struct syntax::ast::Crate,
found enum core::result::Result) [E0308]
src/racer/ast.rs:54             Ok(e) => Some(e),
^~~~~
src/racer/ast.rs:55:13: 55:28 error: mismatched types:
expected syntax::ast::Crate,
found core::result::Result<_, _>
(expected struct syntax::ast::Crate,
found enum core::result::Result) [E0308]
src/racer/ast.rs:55             Err(FatalError) => {
^~~~~~~~~~~~~~~
src/racer/snippets.rs:40:17: 40:27 error: mismatched types:
expected syntax::ptr::P<syntax::ast::ImplItem>,
found core::result::Result<_, _>
(expected struct syntax::ptr::P,
found enum core::result::Result) [E0308]
src/racer/snippets.rs:40                 Ok(method) => {
^~~~~~~~~~
src/racer/snippets.rs:55:17: 55:32 error: mismatched types:
expected syntax::ptr::P<syntax::ast::ImplItem>,
found core::result::Result<_, _>
(expected struct syntax::ptr::P,
found enum core::result::Result) [E0308]
src/racer/snippets.rs:55                 Err(FatalError) => {
^~~~~~~~~~~~~~~
src/racer/snippets.rs:41:27: 41:38 error: the type of this value must be known in this context
src/racer/snippets.rs:41                     match method.node {
^~~~~~~~~~~
error: aborting due to 6 previous errors
Could not compile racer.

+1

Yesterday's rustc-1.0.0-beta.2 gets further, building except for unstable feature errors.
$ cargo build
   Compiling rustc-serialize v0.3.12
   Compiling toml v0.1.20
   Compiling racer v0.0.1 (file:///Users/giles/.local/racer)
src/main.rs:1:1: 1:66 error: unstable feature
src/main.rs:1 #![feature(collections, core, rustc_private, str_char, path_ext)]
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: this feature may not be used in the beta release channel
src/main.rs:2:24: 2:45 error: unstable feature
src/main.rs:2 #![cfg_attr(not(test), feature(exit_status))] // we don't need exit_status feature when testing
                                     ^~~~~~~~~~~~~~~~~~~~~
note: this feature may not be used in the beta release channel
error: aborting due to 2 previous errors
Could not compile `racer`.

To learn more, run the command again with --verbose.
tamias:racer giles$ cargo build --release
   Compiling rustc-serialize v0.3.12
   Compiling toml v0.1.20
   Compiling racer v0.0.1 (file:///Users/giles/.local/racer)
src/main.rs:1:1: 1:66 error: unstable feature
src/main.rs:1 #![feature(collections, core, rustc_private, str_char, path_ext)]
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: this feature may not be used in the beta release channel
src/main.rs:2:24: 2:45 error: unstable feature
src/main.rs:2 #![cfg_attr(not(test), feature(exit_status))] // we don't need exit_status feature when testing
                                     ^~~~~~~~~~~~~~~~~~~~~
note: this feature may not be used in the beta release channel
error: aborting due to 2 previous errors
Could not compile `racer`.

To learn more, run the command again with --verbose.
$ rustc --version
rustc 1.0.0-beta.2 (e9080ec39 2015-04-16) (built 2015-04-16)

Oh that's interesting, I didn't realise there was a beta 2 out. It may be feasible to make racer work with this beta (and therefore 1.0!) by depending on https://github.com/erickt/rust-syntex instead of libsyntax.

Closing - racer now builds with beta


message namespace no longer includes a "db"

[x] CHANGELOG.md updated

there's never a case where the "db" portion of the namespace was used downstream so this change removes the expectation of needing to "split" the namespace to obtain the table/collection name.
fixes #221

Coverage decreased (-0.009%) to 59.749% when pulling c0441698b7df986b9c5f353cc15d9c105a86ee59 on 221-better-ns into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

Coverage increased (+0.03%) to 59.789% when pulling c0441698b7df986b9c5f353cc15d9c105a86ee59 on 221-better-ns into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

once #255 is merged I'll rebase and update the etcd adaptor

this is ready for review since #255 is deferred until later

Coverage increased (+0.01%) to 59.773% when pulling 704ba2043f0aafc9f8cfa6715da41e084bfde3f3 on 221-better-ns into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

LGTM 👍


Implement the inclusion/exclusion of files in the config

Specification
Here's my proposed mental model — since we run rules individually, let's consider a single rule at a time. For a rule, there are several cases:

The rule is off for the entire codebase
The solution here is simple — just don't run it
The rule is off for a certain portion or portions A of a codebase, and enabled as error for the rest of the codebase
We create a clone of the VFS that excludes these portions A of the codebase and run the rule on the result. It will be as if these files simply don't exist. For the purposes of FSD, these files will be treated as "outside of the FSD root", so any references to these files from the FSD root are unregulated, and any references of FSD slices in these excluded files are invisible to the rules.
The rule is off for a certain portion or portions A of a codebase, enabled as warn for different non-overlapping portions B, and then enabled as error for yet different non-overlapping portions C (see diagram)
We create a clone of the VFS that includes B + C and run the rule on the result. Then we somehow* determine what the severity is

* About determining severity. This is a difficult question, because some errors are about entire folders, and the config allows us to change severity of individual files. I suggest we make the error severity "viral", in the sense that if at least one file in the mentioned folder has severity error, then that diagnostic will have severity error, same for warn, going further down.
Implementation notes
1. Config merging
First of all, I think all rule definitions (i.e. plugin array elements that add new rules) should be hoisted to the top, so the order should not prevent you from disabling a rule. For example, the following two configs should be identical:
export default [
  { rules: { 'fsd/public-api': 'error' } },
  { paths: 'src/shared/**', rules: { 'fsd/public-api': 'warn' } },
  fsd.plugin, // here it is last
]

export default [
  fsd.plugin, // here it is first
  { rules: { 'fsd/public-api': 'error' } },
  { paths: 'src/shared/**', rules: { 'fsd/public-api': 'warn' } },
]

With that out of the way, I propose that the result of merging a config array is a mapping of rule to a pair of VFSes, one for error, other for warn, where they are enabled. Initially it will be new Map(rules.map(rule => [rule, { warn: null, error: initialVfs }])), but as the array elements are parsed, these VFSes should be updated individually for each rule.

[!NOTE]
We can ignore performance for now, since at the start, there won't be that many rules, and the configs will probably not be too complicated. Later, we can profile and determine what should be optimized.

2. Running rules
When we run a rule, we have two VFSes ({ warn, error }), so ideally we should also implement a merge operator for VFSes. Then we merge the two VFSes, run the rule, get a list of diagnostics and determine the severity of each diagnostic with the algorithm proposed above

Great job! Very straightforward
Yeah, plugins are already kind of hoisted, as we walk through the config array to find and process them first

But I'm a bit concerned by the 2 trees for warn and error. I don't understand if we are going to pass them both to a rule. If yes, then it seems to be an unnecessary over-complication. Because, In this case, we force guys who will develop plugins to come up with a tree merging operation, which could be too sophisticated for an average user. Of course, we can export a function for that purpose from the toolbox, but still.
Looks like a rule shouldn't even "know" about severities. It's just supplied with full VFS or a portion of VFS and collects diagnostics. Then Steiger core decides what to do with those diagnostics (whether to log it as a warning or an error)
We could have a map of FS node path to severity (generate such a map for each rule during the config parsing stage). So, we can quickly decide what to do with a diagnostic when it comes out of a rule.

But I'm a bit concerned by the 2 trees for warn and error. I don't understand if we are going to pass them both to a rule.

No, my intent was to merge the trees before passing them to the rule

Looks like a rule shouldn't even "know" about severities. It's just supplied with full VFS or a portion of VFS and collects diagnostics. Then Steiger core decides what to do with those diagnostics (whether to log it as a warning or an error)

Yes, I agree

@illright
{
      files: <FilesDefinition>,
      Ignores: <IgnoresDefinition>,
      rules: {
        <RuleName>: <Severity> | [ <Severity>, <RuleOptions> ],
      },
}

From this structure, a user can conclude that it is possible to set different rule options for different parts of the VFS (since you can do that for "severity").
But it's not the case based on what we discussed.
So, here I listed ways we can solve the problem:

Think up some other way to provide rule options (just a different syntax, maybe a separate object type inside config), so it will be less misleading for the users
Use only the later options for a rule (and apply to the entire VFS disregarding files and ignores) and reflect that quirk in the documentation
Implement the capability to have different rule options for different VFS part

My personal favorite way is the first one. But I would like to see your opinion on this issue. You may have alternative solutions.

Hm, yes, very good point. Personally, I'm not a huge fan of the first solution, mostly because I don't have any ideas about alternative ways of providing options to rules. However, I am open to considering it if you have some proposals.
Ideally, we would have a system that allows different sets of options, and the way it could work is by running the rule on all non-disabled files as many times as there are different options and then discarding diagnostics that don't apply in selected files. However, this would probably involve a bunch of messy code and effort for a very narrow edge case.
Therefore, I propose an adaptation of the second option. Instead of quietly accepting only the last option, I'd prefer if we threw a validation error if the config file specifies several different rule options. That way, this behaviour cannot be missed, and if it's a problem for anyone, we'll hear about it in the issues.

Actually, wait, you had a proposal in your message for the first solution — a different kind of object in the config array. I would prefer to keep this option as a last resort, because it broadens the API (and also deviates from ESLint conventions) for all users to prevent a narrow edge case (in my opinion, it's narrow, let me know if you disagree). I'd prefer to keep the public API as small as possible and simply let people know when something isn't supported

Yes, your addition to the second option sounds completely reasonable. Let's go with it 👍

Ideally, we would have a system that allows different sets of options, and the way it could work is by running the rule on all non-disabled files as many times as there are different options and then discarding diagnostics that don't apply in selected files.

I agree, it's an absolute overkill at this stage.


python312Packages.azure-mgmt-servicebus: remove unused dependency

msrestazure is not a dependency, so remove it. Modernizations to move to pyproject = true; are included as well
part of #350657
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 362153 run on aarch64-linux 1

6 packages built:

azure-cli
azure-cli.dist
python311Packages.azure-mgmt-servicebus
python311Packages.azure-mgmt-servicebus.dist
python312Packages.azure-mgmt-servicebus
python312Packages.azure-mgmt-servicebus.dist


Suggest use "NULL" to refer to C null pointers instead of "null string"

Ref: https://docs.perl6.org/language/nativecall#Passing_and_Returning_Values
The docs for passing Str with NativeCall say:

Note that a null string can be passed by passing the Str type object; a null return will also be represented by the type object."

On first reading I thought "null string" might mean an empty string.   Suggest using actual C jargon to make this unambiguous, e.g. "a NULL string pointer", "a C NULL pointer", or similar, to avoid confusion with a possibly-empty string which has an actual address.
Note: In C, the symbol "NULL" (in upper case) is used to specify a null string pointer (or any kind of null pointer).  It is a macro defined by <stdlib.h> which expands to 0, (void *)0 or similar.

Closed with https://github.com/perl6/doc/commit/177013b1d6e9343d5d4df26a172efa5890e88eaf

Wow, you guys are on it!    It's nice to see such fast response to doc issues.


[Bug] UI encounters a 'Test Step Error' during the execution of multiple test cases in a single stretch

Describe the bug
While attempting to validate multiple test cases, the UI encounters a 'Test Step Error' during the execution of multiple test cases in a single stretch.

Test Step Error: Error occurred during execution of test case TC-MEDIAINPUT-1.4. sent 1011 (internal error) keepalive ping timeout; no close frame received

Executing Test Step: Step 2: Read the global attribute: FeatureMap

Test Step Not Applicable: Step 2: Read the global attribute: FeatureMap - Test step skipped: Step 2: Read the global attribute: FeatureMap. !MEDIAINPUT.S.F00 == False
Executing Test Step: Step 2: Given MEDIAINPUT.S.F00(NU) ensure featuremap has the correct bit set
Test Step Error: Error occurred during execution of test case TC-MEDIAINPUT-1.4. sent 1011 (internal error) keepalive ping timeout; no close frame received
Test Step Completed [ERROR]: Step 2: Given MEDIAINPUT.S.F00(NU) ensure featuremap has the correct bit set
Test Case Completed[ERROR]: TC-MEDIAINPUT-1.4
Executing Test Case: TC-MEDIAINPUT-3.10
YAML Version: 85a48aabbc4e43c433aa4b2d35b2817d611946de
Executing Test Step: Start chip-tool test
Using PICS file: /var/tmp/pics
Test Step Error: Error occurred during execution of test case TC-MEDIAINPUT-3.10. Connecting to ws://<IP_ADDRESS>:9002 failed.
Test Step Completed [ERROR]: Start chip-tool test
Test Case Completed[ERROR]: TC-MEDIAINPUT-3.10

Steps to reproduce the behavior
No response
Expected behavior
No response
Log files
UI_Test_Run_2023_12_14_16_07_38.log
PICS file
Media Cluster Test Plan.txt
Screenshots

Environment
Version: main - dev
Sha: f17efc4
Additional Information
No response

https://github.com/project-chip/connectedhomeip/issues/29194

Fixed.


[graph] Create new type of plot, like sunburst

Expecting structure like:

with_road:

men
women

without_road:

men
women

with proportional parts

It is questionable how informative this could be, given there are no data about the total number of bikers.


Does php-protobuf support extend

I use php-protobuf to deserialize  protobuf body from upstream。The proto definition file like this：
syntax="proto2";
message Foo
{
required int32 bar = 1;
optional string baz = 2;
repeated float spam = 3;
extensions 10 to 990;
}
message Qoo
{
extend Foo {
optional int32 test = 11;
}
}
but when I compile it to php class，and use it to  deserialize  protobuf body，it does not work well。for example it not sopport function getExtension introduce by https://developers.google.com/protocol-buffers/docs/proto#extensions。So I want ask  if php-protobuf support extend，If it support how can I use it。
thank  you!

The extensions are unfortunately not supported by php-protobuf. I would advice you to use the official Google's implementation if applicable.


ListBox dragging not working properly

When dragging a ListBoxItem with the Class "draggable", the dragging works fine for the first time. After the first drag-and-drop operation, the ListBoxItem cannot be dragged again.

The problem is behavior is detached when removing item and inserting back does not attach it back. Not sure it can be fixed by using behaviors set from styles.
https://github.com/wieslawsoltes/Avalonia.Xaml.Behaviors/blob/72e7a9cd48285abf396c7847a8f7403078e3e7f6/src/Avalonia.Xaml.Interactions.Draggable/ItemDragBehavior.cs#L247-L248


Feature request for the "for" loop

This is a feature request that I think is really missing in Twig.
As a frontend developer I'd like to be able to specify the starting index of the loop, the step of the loop and the number of iteration of the loop.
ie.
{% for product in products with{start:5, step:2, loop:3} %}

This would return:
products[4]
products[6]
products[8]

it can be very, very useful when you want to display list into several columns.

Quick idea, not tested (!):
{% for i in 4..8 if loop.index % 2 == 0 %}
   {{ products[i] }}
{% endfor %}

It's what I'm doing at the moment but it start to be very messy if you want to have x columns using the same array of data

Ok, yes it's working with an array of products that have regular index.
let's say that my array of product is structure like this:
products[a1a] = productObject;
products[a2b] = productObject;
products[a3d] = productObject;
products[a1b] = productObject;
products[a2d] = productObject;
products[a4c] = productObject;
products[b2d] = productObject;
products[f2d] = productObject;
products[a5g] = productObject;
products[r2d2] = productObject;
products[r5t] = productObject;
products[an3] = productObject;

As you can see, indexes are not regular index but product SKU.

Then I want to use the same array to build 5 columns

```jinja

        {% for sku,product in products with{start:0, loop:2} %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

        {% for sku,product in products with{start:2, loop:3} %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

        {% for sku,product in products with{start:5, loop:1} %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

        {% for sku,product in products with{start:6, loop:2} %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

        {% for sku,product in products with{start:8} %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

Same with the step, I'm not using it in this exemple but step is not working for non regular indexed array.

You can use the slice filter.

        {% for sku, project in products|slice(0, 2) %}
            {{ sku }}: {{ product.name }}
        {% endfor %}

@Maxwell2022 For me it's look like all what you need is {% for %} & {% if loop.index > 0 and loop.index < 2 %}

I agree with everything you are saying. All your piece of code work.
It's just that for me it looks like a hack to do what the "for loop" should be able to do.


Naive IdentityUpdate storage

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#156  👈
#154
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @neekolas and the rest of your teammates on  Graphite


Strip leading/trailing spaces from requested usernames

Fixes #477

Codecov Report

Merging #628 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##             master    #628   +/-   ##
========================================
  Coverage      5.89%   5.89%
  Complexity     2249    2249
========================================
  Files           173     173
  Lines         11145   11145
========================================
  Hits            657     657
  Misses        10488   10488

Impacted Files
Coverage Δ
Complexity Δ

includes/Pages/Request/PageRequestAccount.php
0.00% <0.00%> (ø)
16.00 <0.00> (ø)

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 93a2402...d79c815. Read the comment docs.

https://accounts.wmflabs.org/ notes for the username field "Please make sure you don't leave any trailing spaces or underscores on your requested username."
Suggest updating to note that leading or trailing whitespaces will just be ignored instead.
Also, should this/does this handle leading/trailing underscores?


Did moderateForceSkip stop working?

I'm using a manager account to do moderateForceSkip() but it doesn't skip the song. However, it executes the callback I pass into said function.
Did the endpoint change maybe?

Does any error show up in the console you run the bot from?
The only change i've made to moderateForceSkip is to self skip if the bot is the dj.

Also make sure the person you're attempting to skip isn't of a higher rank.

It doesn't show anything in the logs.
It's trying to skip a regular user.

Downgraded to 3.3.0 and it works.

Yes it seems that we're not longer able to skip other people than the bot itself since 3.5.0 ( 3.3.0 was able to skip even higher ranks )
Will try to look to source code to maybe figure out why.

Possibly an issue with room.isDJ?

Whoa nice ! I didn't even noticed that ( ) are missing from isDJ function, Monday is definitely a bad day to start working ^^

Nice :O
Hopefully your PR gets accepted soon™.

I think it will be updated very soon ( by today imho ) cause it's just some missing () .

Thanks Dark !

if you're getting errors like name not resolved or anything DNS related it is due to people hacking DNS Servers, change to something like Google DNS or OpenDNS if you are.
I am currently working on the v4 release of PlugAPI. Testing things out first to try and weed out bugs

Dark, have you considered multiple bot instances running in v4? https://github.com/atomjack/plugbotapi does it with phantomjs.

It should be possible without it now since i removed the cookies.tmp requirement

Oh I haven't tried yet. Up until this point I was forking processes to have multiple bots, but it takes up so much memory :(

I'm back, yes first it was some DNS issues even with my OpenNIC DNS servers, but I had the feeling that plug.dj himself was also slow ( latency in chat, slow request when deleting message, etc... ). But now everything seems to work fine, we're able to skip other people including higher rank again.
Thanks.


[need] Old Firmware for X50Q

Hey, since I upgraded my X50Q to the newest firmware, my LED for the volume control doesn't work anymore by using custom profiles, also what I don't like is by that firmware (0040) that they replaced "mute/unmute" by pushing the volume button to "open Q Software"
If someone has a link to the old firmwares would be awesome. Thanks

Hi @jester187, can you open a ticket on our helpdesk, the tech support will be able to help you
https://daskeyboard.mojohelpdesk.com/