FIRRTL disconnected wire false positive

https://travis-ci.org/ucb-bar/rocket-chip/jobs/120801505#L1275
The wire in question is an input which is not used internally. It should not cause an error. It is far too laborious to go in and connect every unused wire that just happens to be in a bundle.

Need the FIRRTL code.  This might actually be a FIRRTL or Chisel bug, as Chisel is supposed to initialize all wires and I/Os to invalid.

In the FIRRTL code, the value is present in the bundle but not assigned to anywhere. So this is probably a Chisel bug.

Can you provide the code?

I'll post the code soon.

Here's the file. The code in question is at 16617.
https://gist.github.com/zhemao/1a978d521229af880422b0e16b7901e6

Can you test this Chisel branch? https://github.com/ucb-bar/chisel3/tree/fix-wire-not-initialized

Why does Chisel3 always emit a DefInvalid for a Wire declaration? Shouldn't that be a bug that ideally is caught by FIRRTL?

Ideally, but it's too pessimistic for writing hardware generators, where it's pragmatic to sometimes declare and not use fields.

Perhaps with aggressive dead-code elimination, it would be more practical to rely on FIRRTL to catch this stuff.

Is it a limitation of Chisel that makes it difficult to parameterize the types of declared components? Alternatively, why not expose the DefInvalid API so users that know Wires have unassigned values can be manually invalidated, instead of moving all instances of a compile-time checked error to a run-time checked error?

I think it's partially a limitation of Chisel, but it's also easier to write generators in general when you don't have to explicitly parameterize everything.  This underpins my suggestion to perform DCE before performing the check.
There's an argument to be made for exposing Invalid somehow.  Always defaulting Wires to Invalid is the correct thing to do for Chisel2 compatibility, but additionally providing a safer Wire construct (akin to the difference between <= vs <-) is a good idea.

Well, that fix does work. But Jack is of the opinion that it removes an important type-safety feature.

Maybe giving an option to the Wire constructor, like invalidOk = true, with the default set to invalidOk = false? Then when people are converting between Chisel 2 and 3, they now have an out, but we don't eliminate all cases of this error occurring (in the future we can use it sparingly)?
My complaints with doing DCE before the check is that dead code elimination shouldn't influence the correctness of a circuit, but instead be simply an optimization.

So I could be misreading, but I don't think we need to invalidate wires.
In this particular example we have regressIOs as a Vector of Bundles, and each member of the Vector is connected to the io bundle of different modules. ie.
    inst T_1126 of PutBlockMergeRegression
    T_1126.io is invalid
    T_1126.clk <= clk
    T_1126.reset <= reset

    wire regressIOs : {...}[8]
    regressIOs[0] <- T_1126.io

Now T_1126's io bundle does match the bundle it's being assigned to. Why is it that this assignment isn't enough? I think the Check might be wrong.

I was wondering about that, too.  Notably, it doesn't complain about T_1126.

The error says that regressIOs[0].cache.s2_nack specifically is not initialized. If you look at the type, this subsubfield is in the flipped direction, meaning if we expanded the assignment regressIOs[0] <- T_1126.io, we would get T_1126.io.cache.s2_nack <= regressIOs[0].cache.s2_nack. Thus, to me it appears correct.

Also, doesn't Chisel2 error on uninitialized wires? https://github.com/ucb-bar/chisel/blob/00562dc99f80ff20f82da9a03767cee575648202/src/main/scala/hcl.scala#L98
Because it lacks DCE, FIRRTL would be more aggressive in disallowing uninitialized wires than Chisel2, but I don't think we should "throw out the baby with the bathwater" by saying Chisel3 should never error on uninitialized wires.

Wires that Chisel2 DCEs are precisely the topic of this issue...

Right. Is too much of a burden for people converting between Chisel2 and Chisel3 to set invalidOk = true for wires that Chisel2 DCE'd? Because my point is otherwise, we've actually regressed from Chisel2, because we can no longer detect an invalid circuit that Chisel2 correctly detected.

I'm having trouble wrapping my head around this.
Chisel2 first runs DCE, then it checks for initialized wires and errors out, correct?
To make the Chisel3 front-end as simple as possible, the idea is to let FIRTTL handle the issue? So FIRTTL must first run DCE and then do a pass to check for initialized wires so we can error out?

@azidar I'm OK with Wire() and UninitializedWire() (is that the right name?).  More flags is messy.
@ccelio @azidar's point is that he doesn't want the legality of a circuit to be defined by an optimization pass, so he doesn't like that approach.

Perhaps this isn't an either or type of question.
Perhaps the semantics of CheckInitialization can be defined to only check that "live" code is initialized. Thus you don't have to actually eliminate the code, but FIRRTL also won't error.
Note that the code in question here isn't defined as a Wire, it's defined as a Vec of some Module IOs
 val regressIOs = Vec(regressions.map(_.io))

@jackkoenig that makes sense if there's a definition of liveness that's suitable to bake into the language spec

It seems to me that this issue is a prime example of the delicate balancing act of what we should expect Firrtl to do, what we should expect Chisel to do, and what we should require the user to do.
It kind of reminds me of #69 except in that case Chisel could do nothing so either Firrtl had to loosen semantics or essentially require users to abandon all benefits of width inference.
I'm not against requiring the user to explicitly invalidate things, I don't think it'll be particularly common (as evidenced by the fact that this only comes up in recent GroundTest things, not in rocket-chip itself). The big problem here is that compared to the liveness proposal, allowing/requiring the user to explicitly invalidate still has the fundamental problem that it sacrifices Firrtl's ability to provide the safety of CheckInitialization.
What if the user actually wants to create a wire with some unused fields, but with initialization checking safety on the fields that are used?

@jackkoenig this issue actually comes up with great frequency, which is why chisel3 invalidates all module inputs and instance outputs.  What's showing up in groundtest amounts to a corner case that chisel3 didn't happen to be invalidating.
I'm in complete agreement with your last point (I'd like checking on used fields but not on dead fields, as is the case in chisel2).

My complaint with the DCE is not that dead code is actually eliminated, but it is the case where a module could be either legal or illegal depending on whether some other place in my module (or even someone else's module) reads from a value or not. This property is very unintuitive for users.
As far as checking initialization on used subfields, but not unused ones, firrtl supports setting subfields to be invalid, so we would just need to expose that API.

It sounds like several people would like chisel/firrtl to automatically determine that subfields are unused; exposing the Invalid construct doesn't help with that.  And it may well be possible to define liveness in an intuitive way (which probably does require that the analysis not cross module boundaries).

Perhaps FIRRTL does not require DCE but given that Chisel is intended for
writing hardware generators and requiring the user to manually specify
which fields are not connected is pretty onerous (unless we want users to
always throw the baby out with the bathwater), Chisel could require FIRRTL
to run DCE.
On Apr 5, 2016 5:53 PM, "Andrew Waterman"<EMAIL_ADDRESS>wrote:

It sounds like several people would like chisel/firrtl to automatically
determine that subfields are unused; exposing the Invalid construct doesn't
help with that. And it may well be possible to define liveness in an
intuitive way (which probably does require that the analysis not cross
module boundaries).
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/ucb-bar/firrtl/issues/106#issuecomment-206055731

To clarify my previous statement, I think the case @zhemao brought up is a great example.
You can see the Chisel code in question at: https://github.com/ucb-bar/groundtest/blob/axi-fix/src/main/scala/regression.scala
We have a fairly straightforward Module interface specification

class RegressionIO(implicit val p: Parameters) extends ParameterizedBundle()(p) {
  val start = Bool(INPUT)
  val cache = new HellaCacheIO
  val mem = new ClientUncachedTileLinkIO
  val finished = Bool(OUTPUT)
}

abstract class Regression(implicit val p: Parameters)
    extends Module with HasTileLinkParameters {
  val io = new RegressionIO
}

And a fairly straightforward instantiation of these Modules:
class RegressionTest(implicit p: Parameters) extends GroundTest()(p) {
  disablePorts(mem = false, cache = false)

  val regressions = p(GroundTestRegressions)(p)
  val regressIOs = Vec(regressions.map(_.io))

with p(GroundTestRegressions) giving a Seq of Module(new BlahRegression)
There are fields within the interface that are not intended to be used. The user could of course just invalidate the whole Vec, but that is throwing out any initialization checking safety. The user could pick which fields are not being used, but that goes against much of the convenience of generators and I highly doubt anyone will actually do that. It seems to me that unless we offload some of this generator support to FIRRTL, then this is going to be a problem all over the place in Chisel. That will likely lead to Chisel just punting to run-time and invalidating everything (as evidenced by @aswaterman 's point that Chisel already invalidates module IO and instance IO already)

Given that it appears designers would overly-use the is-invalid mechanism in FIRRTL, I am slowly being convinced. Certainly, a non-intuitive error is better than never catching it at all (which is what is happening now). In my spare time, I'll think about defining a liveness definition, and see where we can go from there. For now, the current solution is ok, so let's go ahead and merge Andrew's pull request.

Andrew's fix merged in https://github.com/ucb-bar/chisel3/commit/f9689cab3bbb5cb2cddbb429bc30d630c886034d
Should this issue be closed or the discussion left open?

I'll start a new issue that references this thread, but more clearly states the problem/potential solution.

Sounds good!


Add driver-did-solid

Ah @BernhardFuchs added the solid method already! This PR was going to be to do that.
Updated it to change the example DID to a mainnet one, but it is not high priority.

Part of our PR process is to add the new methods and example DID's to the frontend too, once we merge the driver. So no need for a separate PR here.
@dankelleher  is did:solid:DSb8Guj9tB1jvsyqrsE3Yi44hwnzrVVQc2gcS1J1dUxy the correct example? If so it's already in the UI at https://dev.uniresolver.io/ and we can close this.


Disqus Chat and Page view count

It would be nice if we had a Discus chat on every replay page like Osu! has with beatmaps page https://disqus.com/

Other alternative suggestion is if we could send an private message to other users

An page view count would works like profile/replay views count

Added in last release https://github.com/codevirtuel/osu-replayViewer-web/releases/tag/v0.2.2


ODA bug fixes

Fix of some ongoing bugs with the ODA code, and improving the code for 7.a.1 and 4.b.1. Summary of edits on this branch:

The QA file should now be successfully generated as intended - only displaying information for the selected indicators in the config. There was a problem before where as part of the intro text the QA was looking for gni_api object regardless of which indicator was being updated.
There were irrelevant warning messages printed before, which should only be reserved for indicators 1-a-1 and 15-b-1 under special circumstances. Those are fixed now with extra conditional statements.
Added some more information in README and trimmed away some bits which were no longer true.
Edited the example_config to demonstrate how to automate a single indicator
Added more CRS codes to 7.a.1 after topic expert noted that some data may be missing based on the UN metadata
Shuffled the column order of 4.b.1 to make consistent with other ODA
Changed the sentence case for 4.b.1 disaggregations after latest QA comments

15-a-1/15-b-1 yields weird results for the non-ODA part (biodiversity) and needs to be investigated, but will do that in a separate pull request. From a quick look it seems like it's the OECD data that has been revised and is now mainly 0s, so not actually a problem with the code itself.
To whoever is reviewing this pull request - try to run versions of single and multiple indicator updates and check if you get any errors. Also do run 15-a-1 to double check if you also get weird outputs for it. And as usual, read through the README in case it doesn't make sense as I did a few patchy edits there.

Closing as more changes are required. Will re-open once those are integrated

Added a few more edits (description updated), so now ready for review - shouldn't take long as not a lot of the original code has bee changed (see summary above)

Have picked up and will hopefully get done tomorrow.

Thanks Michael - no rush on this one!

FYI, I just did an extra change to the code for 17-19-1, so worth updating the branch is it's already pulled locally. This will not make any difference to the edits so far as it's contained within the 17-19-1 script (and the QA bits for it)

Readme changes good.
Still need to change the deflators filename to 2021 in "example_config"?
And the constant USD issue in 17-19-1

Thanks @MichaelGNairn ! I have edited the readme now and also added clarification in the example config - edited out the year of the deflators and put YYYY instead, as people will have to use the latest file and rename accordingly. The readme also explains that.
The edits of 17.19.1 should produce USD (thousands) value, without using the deflators. I also added a "Units multiplier" column as it was missing before. I removed the $ and £ signs from the Unit label because that was causing havoc when I was creating the feature branch (in fact, looking at SDMX standards they should not be there at all, it should just say USD or GBP, but I kept the "thousands" as a reminder for the user, as this indicator is not reported through SDMX anyway so we have flexibility".
If you pull the changes onto your local branch, the results should be identical to what I currently have on the feature branch for review. Hope you won't have any issues, runs smoothly for me!

pulled to local branch and works perfectly now, same as on FB.


Update data-protocols-formats/frontend-backend.md for v23.3.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: sitingren:x: DMickensYou have signed the CLA already but the status is still pending? Let us recheck it.


Bug: CLI Issue for flexible Heredoc syntaxes

PHP Version
7.4
CodeIgniter4 Version
4.2.11
CodeIgniter4 Installation Method
Manual (zip or tar.gz)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
No response
What happened?
CodeIgniter v4.2.11 Command Line Tool - Server Time: 2023-01-06 08:41:28 UTC-06:00
[ParseError]
Invalid body indentation level (expecting an indentation level of at least 8)
at SYSTEMPATH\Commands\Database\ShowTableInfo.php:53
Steps to Reproduce
php spark debugbar:clea
Expected Output
...
I fixed this issue before but when I updated to CI 4.2.11 it appear again please fix this

@ChibuezeAgwuDennis What is your exact PHP version?
php -v

php v7.4.9

Cannot reproduce:
bash-3.2$ php spark debugbar:clea

CodeIgniter v4.2.11 Command Line Tool - Server Time: 2023-01-06 17:30:17 UTC-06:00

Command "debugbar:clea" not found.

Did you mean this?
    debugbar:clear

bash-3.2$ php spark debugbar:clear

CodeIgniter v4.2.11 Command Line Tool - Server Time: 2023-01-06 17:30:21 UTC-06:00

Debugbar cleared.

I can reproduce it, with the following changes:
    /**
     * the Command's usage
     *
     * @var string
     */
    protected $usage = <<<'EOL'
        db:table [<table_name>] [options]

            Examples:
            db:table --show
            db:table --metadata
            db:table my_table --metadata
            db:table my_table
            db:table my_table --limit-rows 5 --limit-field-value 10 --desc
        EOL;

    /**
     * the Command's usage
     *
     * @var string
     */
    protected $usage = <<<'EOL'
    db:table [<table_name>] [options]

        Examples:
        db:table --show
        db:table --metadata
        db:table my_table --metadata
        db:table my_table
        db:table my_table --limit-rows 5 --limit-field-value 10 --desc
        EOL;

I don't know why this is happening to you by default. Maybe because of the settings of IDE or the activation of a plugin in Editor.

This is the code in v4.2.11:
https://github.com/codeigniter4/framework/blob/543dd5e5d3cadee764962712de29458b5524dd24/system/Commands/Database/ShowTableInfo.php#L46-L60
It seems no problem.

I did not change file there

Please update to PHP v7.4.10+. This is a bug of PHP itself https://bugs.php.net/bug.php?id=79934

Also, please update your IDE settings not to convert LF endings to CRLF.

https://www.php.net/ChangeLog-7.php#PHP_7_4

Version 7.4.10
...
Fixed bug #79934 (CRLF-only line in heredoc causes parsing error).


Add PowerShell Dockerfile

This adds the PowerShell Language Worker Dockerfile.
It grabs the nupkg from the myget feed
Unzips it and places it in the host's workers folder

I'm a little confused by the merge conflict because I don't know what mesh is. I'm hoping @ahmelsayed has the answer on what should the result of conflict be.

We will need another PR here https://github.com/Microsoft/mcr/tree/master/teams/azurefunctions to onboard this image on MCR. I can do that part.

Thanks @ahmelsayed!


story(rest): implement rest.Api on top of a chi.Router

Description
As a contributor, I want to implement the rest.Api interface on top of a chi.Router, so that things like not found and method not allowed default reponses can be defined.
Note, not found and method not allowed behaviour can not be overridden for the standard http.ServeMux; hence the use of the chi.Router.
Acceptance Criteria

[ ] rest.Mux should implement rest.Api
[ ] rest.Mux should allow for overriding of Method Not Allowed
[ ] rest.Mux should allow for overriding of Not Found

Related Issues
No response

Closed by #59


Fix Default/OEM encoding behavior PowerShell Core

Based on conclusion in discussion #3248

[x] - OEM

We need internal fix because .Net Core haven't "OEM" term.
The fix should provide PowerShell Core behavior:

on Windows - as Windows PowerShell based on GetOEMCP() and legacy encodings (System.Text.Encoding.CodePages)

on Unix - the same as default encoding in PowerShell Core

[x] - Default

We need internal fix because CoreFX default for all platforms is UTF8
Until we have completed Encoding RFC we should restore behaivor as in Windows PowerShell.
The fix should provide PowerShell Core behavior:

on Windows - as Windows PowerShell based on GetACP() and legacy encodings (System.Text.Encoding.CodePages)

on Unix - UTF-8 without BOM (We are expecting that the same will be in CoreFX)

[ ] - Tests

Now we don't have a full set of encoding tests (only for redirections). I believe we need to create them during future RFC implementation, not now.

I was able to build locally with
<PackageReference Include="System.Text.Encodings.Web" Version="4.0.11" />
in Microsoft.PowerShell.SDK.csproj
but on CI build failed 😕 I revert to Version="4.3.0" but build failed again.
@daxian-dbw Could you please help?

Add @mirichmo to review the new windows API set added to PInvokeDllNames.cs, to see if that's fine for downlevel machines like win7.
@iSazonov I don't see you change the .csproj file. Did you miss that?

<PackageReference Include="System.Text.Encodings.Web" Version="4.0.11" />

Why are you using System.Text.Encoding.Web? The CodePagesEncodingProvider type is available in System.Text.Encoding.CodePages

@daxian-dbw
I change CodePages version on 4.0.11 but CodePagesEncodingProvider cannot be finded. 😕

@JamesWTruher @mklement0, you have been closely following up with this issue (and related), could you please take a look at the fix?

I still cannot resolve CodePagesEncodingProvider .

@daxian-dbw: I know this debate is cumbersome, but I think it's a very important one to have, and I don't think we're ready to move ahead yet - I've just added further thoughts here.

@daxian-dbw @SteveL-MSFT CI have passed - many thanks! Sorry for many typos (make the PR in the weekend night was bad my idea). Please continue code review.
@mklement0 Can you build the branch and check our expectations? If no, could you please attach files with your tests?

@iSazonov: I built on my macOS 10.12 machine and I can confirm that the following ad-hoc tests return true on macOS (and, judging by the source, therefore all Unix platforms), as desired:
# Setup: *create* a  BOM-less UTF-8 file.
'ö' | set-content -nonewline /tmp/$pid.txt

# Tests: Both should output $True

# Compare the raw bytes of the new file to the UTF-8 encoding of 'ö' (0xc3 0xb6)
# With the current alpha17, this would return $False, because Set-Content creates an
# ISO-8859-1 file.
$null -eq (Compare-Object (Get-Content -Encoding Byte -Raw /tmp/$pid.txt) (0xc3, 0xb6))

# See if the BOM-less UTF-8 file is *read* correctly.
'ö' -eq (Get-Content -Raw /tmp/$pid.txt)

(I wasn't able to run the tests - the powershell binary crashed  at the following point:
Describing New-PSSession basic test
 [-] New-PSSession should not crash powershell 228ms
   Expected string length 66 but was 77. Strings differ at index 0.
   Expected: {InvalidOperation,Microsoft.PowerShell.Commands.NewPSSessionCommand}
   But was:  {System.DllNotFoundException,Microsoft.PowerShell.Commands.NewPSSessionCommand}
...

)

@mklement0 Thanks for confirmation! It means the code is step in right direction!
All tests have passed on CI. I believe "New-PSSession basic test" too and you can ignore the error in context of the PR (or try discover a root of the error: copy-past test code in your session and see $error[0] - I think you don't install any package).

I added comment about tests in first post.

@iSazonov:
Great idea, but I suggest, to avoid ambiguity, that you explicitly mention in your comment that this PR implements BOM-less UTF-8, especially given that your comment links to the .NET Core Encoding.Default property, which is currently UTF-8 with BOM (which, as stated, is not the actual default encoding (though, fortunately, it looks like  getting Encoding.Default in line with that actual default is coming)).
To add some more fodder for upcoming tests, here's a simple one that tests whether PowerShell itself correctly reads BOM-less UTF-8 source code (such as scripts) by default in PS Core on Unix:
# Setup:
# Create a no-BOM UTF-8 file with the following literal content:
#   'ö'
# which, when executed as a PS script, should echo 'ö' back, IF the script
# was correctly decoded from UTF-8 by PS.
# UTF-8 bytes: 0x27 (single quote), 0xc3 0xb6 (encoding of 'ö', U+00F6), 0x27 (single quote)
[byte[]] (0x27, 0xc3, 0xb6, 0x27) | Set-Content -Encoding Byte /tmp/$PID.ps1

# Test: See if the 'ö' is echoed back correctly.
#       Should return $True
'ö' -eq (& /tmp/$PID.ps1)

@mklement0 I corrected first post about BOM-less, in the code it is obvious.

@iSazonov are you going to add tests to this PR?

I added in first post:

Now we don't have a full set of encoding tests (only for redirections). I believe we need to create them during future RFC implementation, not now.

I am confused. Partial test is meaningless. The full test also does not make sense until the approval of the Encoding RFC. What is compromise?

@iSazonov the code changes look good to me. If the corresponding tests will come later, then we should keep that work item tracked in an issue. Is #3248 considered fixed with this PR? If not, the test work item should be tracked in the first post of that issue, similar to how you are tracking OEM, Default and tests in this PR.
And @mklement0 provides some good testing snippets here, we should also keep them in the same issue that tracks the test work item, so they can be easily referenced when it's time to complete the tests.

@daxian-dbw Tracking Issue #3488.

@iSazonov Thank you! I will merge this PR later today.


created new file

resolves #issueNumber
Checklist for profile addition

[x] Name the PR fix: add <your-username>.
[x] You've added file named your-username.json in the profiles directory.
[x] You've linked the PR to the correct issue.

Other additions/changes

[ ] Changes made in this PR are mentioned below
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.
[ ] I've read the contributing guidelines

This PR adds/fixes

Notes

Duplicate of https://github.com/EddieHubCommunity/awesome-github-profiles/pull/1733

duplicate of https://github.com/EddieHubCommunity/awesome-github-profiles/pull/1733

Duplicate of https://github.com/EddieHubCommunity/awesome-github-profiles/pull/1733


v 4+ (URGENT BUG - SHIPBLOCKER) 'Tree type' in AddTree is erroneously showing as 'Can't be blank' when it IS NOT blank

Caught this bug while testing the new APK (1/23/2023) that Mony sent out.
Need to fix. Watch video for repo steps.
Expected behavior: If 'Tree Type' (whether it was populated by TreeBot - or not) shows an entry on the AddTree screen - then the error 'Can't be blank' SHOULD NOT show up when the user selects 'Calculate and Save'.
https://user-images.githubusercontent.com/62637055/214213780-e82ece6c-603a-4716-8969-78df4fd7c42e.mp4
In the app - if the user repeatedly clicks on the 'Tree Type' options (even though it appears selected) than you can get passed the error. However - if the screen is showing that there is already a selected 'Tree Type' - we should have a selected 'Tree Type' (and not be throwing the 'NULL' error response).
https://user-images.githubusercontent.com/62637055/214216258-0c95ac46-bc0b-40d8-ba74-997770417f0c.mp4

Christy verified this was not fixed in Version 71.

Fixed as of Version 74


Tag recent commits?

Could we tag the recent commits on master as a release or is there some reason against it?

Done: https://github.com/IdeasOnCanvas/Ashton/releases/tag/2.0.7


Use local DB for integration tests

...in progress..very experimental.

Closing this - this was to see if the implementation is easy and quick. As this is just a 'nice to have', I don't want to spend more time and close it.


Check if attribute is empty for whereNotIn on QueryBuilder

I use the whereNotIn function with a "dynamic" array, and this array may be empty.
When the array is empty, SQL return a syntax error, because it is translated to a not in ().
It would be great if the whereNotIn function could check the emptiness of the array passed, and not translate anything to SQL if it is the case.
Ex:
    $array = array();
    DB::table('users')->whereNotIn('users.id', $array);

This will become
   SELECT * FROM users WHERE users.id NOT IN ();

And this throws a SQL syntax error.
(Edited for ex.)

Does this need a PR or what is the status on this? I would like to see this added to the Eloquent ORM :)

I think it was rejected a few times, but there's obviously demand. ;)
I'd love to see this, too!

Discussion can continue on the pull request if still required.


Database fixes

Adds the following:

New logic to handle necessary database connection string modifier for Tower v24.1+
Fix for RDS snapshot configuration.

Warning: New mechanism introduced (_use of external provider to offload logic to a Python script within the project. You will need to run terraform init -upgrade to re-sync).

Can one of @adriannavarrobetrian @markpanganiban @cristina-v-seqera try this out please before I merge?


CustomTitleBar Style not working

I am trying to color the background and foreground of the TitleBar in the Template10 Hamburger Template to look like the following screenshot:

I have used code in the code-back to do this, but was reading about the XAML way that is built into the Bootstrapper.
I have only changed the colors in the Custom.xaml as a test.  The rest of the Solution is completely standard.  I have added the following code in the "Light" and "Default" styles:
<Style TargetType="controls:CustomTitleBar">
    <Setter Property="BackgroundColor" Value="#FFFFB900" />
    <Setter Property="ButtonBackgroundColor" Value="#FFFFB900" />
    <Setter Property="ButtonForegroundColor" Value="White" />
    <Setter Property="ButtonHoverBackgroundColor" Value="#FFFFC83D" />
    <Setter Property="ButtonHoverForegroundColor" Value="White" />
    <Setter Property="ButtonInactiveBackgroundColor" Value="#FFFFB900" />
    <Setter Property="ButtonInactiveForegroundColor" Value="DimGray" />
    <Setter Property="ButtonPressedBackgroundColor" Value="#FFFFB900" />
    <Setter Property="ButtonPressedForegroundColor" Value="White" />
    <Setter Property="Extended" Value="False" />
    <Setter Property="ForegroundColor" Value="White" />
    <Setter Property="InactiveBackgroundColor" Value="#FFFFB900" />
    <Setter Property="InactiveForegroundColor" Value="DimGray" />
</Style>

This is a screenshot of the app with just the style added:

As you can see, the colors are the default accent color of my computer.  Please let me know if I am using the style wrong.
P.S. As an aside, the standard code to change the TitleBar that I am using is below:
    <Color x:Key="CustomColor">#FFFFB900</Color>
    <Color x:Key="CustomColorLight">#FFFFC83D</Color>
    <Color x:Key="ContrastColor">White</Color>
var titleBar = Windows.UI.ViewManagement.ApplicationView.GetForCurrentView().TitleBar;
titleBar.BackgroundColor = (Color)Application.Current.Resources["CustomColor"];
titleBar.ForegroundColor = (Color)Application.Current.Resources["ContrastColor"];
titleBar.InactiveBackgroundColor = (Color)Application.Current.Resources["CustomColor"];
titleBar.InactiveForegroundColor = (Color)Application.Current.Resources["ContrastColor"];
titleBar.ButtonBackgroundColor = (Color)Application.Current.Resources["CustomColor"];
titleBar.ButtonForegroundColor = (Color)Application.Current.Resources["ContrastColor"];
titleBar.ButtonInactiveBackgroundColor = (Color)Application.Current.Resources["CustomColor"];
titleBar.ButtonInactiveForegroundColor = (Color)Application.Current.Resources["ContrastColor"];
titleBar.ButtonHoverBackgroundColor = (Color)Application.Current.Resources["CustomColorLight"];
titleBar.ButtonHoverForegroundColor = (Color)Application.Current.Resources["ContrastColor"];
titleBar.ButtonPressedBackgroundColor = (Color)Application.Current.Resources["CustomColor"];
titleBar.ButtonPressedForegroundColor = (Color)Application.Current.Resources["ContrastColor"];

No matter where I insert this code, the Foreground color of the TitleBar is always Black (see first screenshot)!  The hover and pressed foregrounds of the buttons work perfectly and are both white. If someone knows why this is happening, I would be very grateful. (I have loaded a standard Blank App Template from VS 2015 and the same thing occurs, which is why I don't think it is the Template10 Template).
The foreground White is also working when the window is inactive:

When using the bootstrapper, all you have to do is use the template described here: https://github.com/Windows-XAML/Template10/wiki/Docs-|-Controls#customtitlebar . Paste the code in your App.xaml. If you are using a resource dictionary (like Styles\Custom.xaml in the template), you can copy and paste the <Style TargetType="controls:CustomTitleBar"> block in your <ResourceDictionary> block as direct child.
Resource Dictionary example:
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
                    xmlns:controls="using:Template10.Controls">
    <x:Double x:Key="NarrowMinWidth">0</x:Double>
    <x:Double x:Key="NormalMinWidth">521</x:Double>
    <x:Double x:Key="WideMinWidth">1200</x:Double>

    <Color x:Key="CustomColor">SteelBlue</Color>
    <Color x:Key="ContrastColor">White</Color>
    <Color x:Key="SystemAccentColor">SteelBlue</Color>

    <Style TargetType="controls:CustomTitleBar">
        <Setter Property="BackgroundColor" Value="SteelBlue" />
        <Setter Property="ButtonBackgroundColor" Value="Maroon" />
        <Setter Property="ButtonForegroundColor" Value="White" />
        <Setter Property="ButtonHoverBackgroundColor" Value="Orange" />
        <Setter Property="ButtonHoverForegroundColor" Value="White" />
        <Setter Property="ButtonInactiveBackgroundColor" Value="DimGray" />
        <Setter Property="ButtonInactiveForegroundColor" Value="White" />
        <Setter Property="ButtonPressedBackgroundColor" Value="Green" />
        <Setter Property="ButtonPressedForegroundColor" Value="White" />
        <Setter Property="Extended" Value="False" />
        <Setter Property="ForegroundColor" Value="White" />
        <Setter Property="InactiveBackgroundColor" Value="LightSteelBlue" />
        <Setter Property="InactiveForegroundColor" Value="DimGray" />
    </Style>

    <ResourceDictionary.ThemeDictionaries>
        <ResourceDictionary x:Key="Light">[...]</ResourceDictionary>
        <ResourceDictionary x:Key="Default">[...]</ResourceDictionary>
        <ResourceDictionary x:Key="HighContrast">[...]</ResourceDictionary>
    </ResourceDictionary.ThemeDictionaries>
</ResourceDictionary>

I find I have to use RequestedTheme


⚠ Community has degraded performance

In ca8e5d6, Community (https://community.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 213 ms

Resolved: Community performance has improved in 04d4045.


Fb API update to V9

New API Version -> V9.0

@flaviobritohelloprint Facebook API been updated to v10 in latest release. Please check it.


[Go] DeltaBitPack deltaBitWidths overflow

Describe the bug, including details regarding any error messages, version, and platform.
I wrote some int64 using c++ ::parquet::Encoding::DELTA_BINARY_PACKED
and then tried to read this with go but got:
panic: runtime error: index out of range [4] with length 4

goroutine 199 [running]:
github.com/apache/arrow/go/v14/parquet/internal/encoding.(*DeltaBitPackInt64Decoder).unpackNextMini(0xc1aee302a0)
        /home/dstasenko/go/pkg/mod/github.com/apache/arrow/go/v14@v14.0.0-20231023113027-37935604bf16/parquet/internal/encoding/delta_bit_packing.go:230 +0x2da
github.com/apache/arrow/go/v14/parquet/internal/encoding.(*DeltaBitPackInt64Decoder).Decode(0xc1aee302a0, {0xc1cc73b008?, 0xa7d50d?, 0xc1adb08360?})
        /home/dstasenko/go/pkg/mod/github.com/apache/arrow/go/v14@v14.0.0-20231023113027-37935604bf16/parquet/internal/encoding/delta_bit_packing.go:267 +0x118
github.com/apache/arrow/go/v14/parquet/file.(*Int64ColumnChunkReader).ReadBatch.func1(0x15a201, 0x167d01)
        /home/dstasenko/go/pkg/mod/github.com/apache/arrow/go/v14@v14.0.0-20231023113027-37935604bf16/parquet/file/column_reader_types.gen.go:93 +0xa3
github.com/apache/arrow/go/v14/parquet/file.(*columnChunkReader).readBatch(0xc1adb08360, 0x3c9c00, {0xc1d3f26000, 0x3c9c00, 0x3c9c00}, {0x0, 0x0, 0x0}, 0xc1aeb73c80)
        /home/dstasenko/go/pkg/mod/github.com/apache/arrow/go/v14@v14.0.0-20231023113027-37935604bf16/parquet/file/column_reader.go:508 +0xc2
github.com/apache/arrow/go/v14/parquet/file.(*Int64ColumnChunkReader).ReadBatch(0xc1aee2e3d0?, 0xc1aee36960?, {0xc1cbc6a000?, 0x2b21d60?, 0xc0001a9d58?}, {0xc1d3f26000?, 0x1a49d55?, 0xa?}, {0x0, 0x0, ...})

I assume that this line lacks boundaries check https://github.com/apache/arrow/blob/ac581fd2a87b35c872cf334bb147851fe1287714/go/parquet/internal/encoding/delta_bit_packing.go#L228
Component(s)
Go

Would you mind provide the test data which might trigger the bug here?

storage_000000000.parquet.txt
added .txt ending because github does not allow to upload parquet files

https://github.com/apache/arrow/blob/ac581fd2a87b35c872cf334bb147851fe1287714/go/parquet/internal/encoding/delta_bit_packing.go#L175-L176
probably you forgot "if err != nil return"

I've find out the reason. Let me submit a fixing

@Hattonuri I've submit a fixing here: https://github.com/apache/arrow/pull/38413
You can have a try at the new code.

Now it works! Thank you

Now it works! Thank you


href= not working?

Monterey 12.6.7 here, xbar 2.1.7-beta.
I have the following code:
echo "Admin requests: $CNT | href=https://url | color=red"

It displays correctly:

But when I click on it, the browser doesn't open, and instead I get the xbar menu:

Bug?

It's currently not possible to have an action happen when you click the menu bar icon.
You have to add a menu entry to do this:
echo "Admin requests: $CNT"
echo "---"
echo "Open url | href=https://url"
Related: #910


Azure IPI with cluster proxy builds 3 masters but does not find bootstrap complete

Describe the bug

Azure IPI with cluster proxy setting builds 3 masters but does not find bootstrap complete, and times out at about 40 minutes.
The Azure network is private.
The same install-config.yaml with no proxy setting builds cluster to completion.

NOTE:  Red Hat Openshift works with proxy settings in install-config.yaml (same file).
Version

./openshift-install version
./openshift-install 4.6.0-0.okd-2020-11-27-200126
built from commit 7b5bd8be9e5f18cc9b8af5f95d629ddd64c015cc
release image quay.io/openshift/okd@sha256:a5392db432c990ee012ab189e9fa0d7b6a168f6e9b9e9da7fb10768b48752ca0
How reproducible

100% fails with proxy settings in install-config.yaml
100% works with NO proxy settings in install-config.yaml
Log bundle

Cluster does not install to provide.  Please let me know what logs I can provide.  I can ssh to bootstrap machine, it reboots about every 6 minutes -- and there are pods that are attempting to start and then restarting.  Not sure how to collect logs as openshift-install gather bootstrap only indicated that it could not connect -- even though I could ssh core@${BOOTSTRAP_IP} with no password (I tried every thinkable permutation related to --key= and even without).
Can go on and on -- but please let me know what is best information to help, and I will provide that.
Here is a snippet from the install-config
platform:
  azure:
    baseDomainResourceGroupName: ${REDACTED}
    networkResourceGroupName: ${REDACTED}
    virtualNetwork: ${REDACTED}
    controlPlaneSubnet: ${REDACTED}
    computeSubnet: ${REDACTED}
    region: ${REDACTED}
    outboundType: UserDefinedRouting
publish: Internal

iirc the installer needs to run azure analogue of openshift-gcp-routes.service on bootstrap too

Here is an install attempt of OKD 4.6.0-0.okd-2020-11-27-200126 (conducted 2020/12/03), with a snippet of the output below.  This is conducted just after successfully installing Red Hat Openshift 4.6.4 with the same install-config.yaml.
Please let me know if I can provide additional information or take alternative actions.
Thank you very much.

One addendum -- the network connect is ESTABLISHED with the proxy server :
OUTPUT from command --> netstat -an | grep -i tcp | grep -v LISTEN
tcp        0	  0 ${OPENSHIFT_INSTALL_SYSTEM_IP}:41400        ${PROXY_SERVER_IP}:8080       ESTABLISHED

Is there more information needed?  I re-attempted again today with 4.6 2020-12-12 and same issue.  WorkerNodes get created / MasterNodes are created but bootstrap node is never seen as completed and times out at ~40 minutes.
We know that when all 3 masters are created -- the worker nodes are then created.  The openshift-install process is not "seeing" the bootstrap machine as completed.
What can I do to help?

This issue still exists in 4.5 and 4.6.  However, I will close this ticket and attempt to get traction with Openshift 4.7 version


Resumes

First of all thanks for the great lib !!!
I've just started creating one myself, but perhaps i'll contribute now to yours.
one scenario for me is trying to download Resumes for Candidates, but i dont seem to be able to determine what files are Resumes vs anything else, e.g. Contracts, Certificates etc.
Is that something you've come across ?

You are welcome 😃. There could be much more done on this library and I would like to refactor it and clean up once I have got some time to do it...
I think type returns the file type but it might vary from client to client
entity/Candidate/123456/fileAttachments?fields=name,type,id,fileType,externalID,fileExtension,fileSize,directory,contentType,contentSubType,distribution
When I tested this query above, I could see different types showing up, same as individual Bullhorn client has in their Bullhorn UI.
http://bullhorn.github.io/rest-api-docs/entityref.html#entity-fileattachment
http://bullhorn.github.io/rest-api-docs/index.html#get-entity-entitytype-entityid-fileattachments

Thanks, i also noticed the 'meta' URLs return the schema from the actual api, which i guess is the way to go. rather than the Docs
e.g. https://123.bullhornstaffing.com/rest-services/123/meta/Candidate?fields=*&meta=full&BhRestToken=123


Both Node-Red examples give debug error - TypeError: URLBrowserResolver is not a constructor

Using both examples exactly as provided in Node-Red - simple pdf and image svg pdf.
Both examples give the debug error "TypeError: URLBrowserResolver is not a constructor".
Have tried in two browsers Chrome 84.0.4147.89 & FireFox 79.0
Windows 10 64 bit environment
Node-Red v 1.1.2
Java 8 261
Thanks

same here (3 users - same error)
node-red forum thread for reference: https://discourse.nodered.org/t/contrib-pdfmake-node-help-please-getting-node-to-work/30867

PDFMake has fixed this problem - it is pending release.
Once they update above v0.1.67 I suggest you update your package.json to request "pdfmake" version "^0.1.67"
In the mean time, to make your node work, you could update the package.json to target "pdfmake" version "0.1.65" (exclude the ^)

A fix to pdfmake had resolved this issue. @ollixx I strongly recommend you update this node to ensure your dependancy targets ^0.1.68 to prevent anyone encountering this again.

Hey folks, thx for reporting and the hint. Will fix that asap updating the lib as suggested.


feat(async): async functions in parallel are now called with an additional index parameter

Description
feat(async): async functions in parallel are now called with an additional index parameter
test(async): added test for the new index parameter in parallel
Checklist

[x] Changes are covered by tests if behavior has been changed or added
[x] Tests have 100% coverage
[x] If code changes were made, the version in package.json has been bumped (matching semver)
[x] If code changes were made, the yarn build command has been run and to update the cdn directory
[ ] If code changes were made, the documentation (in the /docs directory) has been updated

Resolves
Resolves #288

Hey @UnKnoWn-Consortium thanks for the PR 🙏 and sorry for the delay 🙃
This is interesting, I'm just not sure it's going to be very helpful. My concern is that the index will be misunderstood and/or misused by devs.
Would love to here you're thoughts, I'm happy to be convinced!

Hello @rayepps my use case for this is rather simple. It is for building UI, specifically progress bars showing the status for each queue. May I know more about your concern on misuse?

@UnKnoWn-Consortium My concern is that it feels a little like we're exposing an internal implementation detail that users won't understand unless they look at the code.
If an index is going to pass I would expect it to be the index of the item being worked on but this is passing the index of the queue that is doing the processing.
I could be wrong BTW, just hesitant

@UnKnoWn-Consortium you think queueIndex is still useful if you have the individual index?

@rayepps I believe they two serve different purposes. The former refers to the position of the item that is being processed in the original array while the latter refers to which queue or parallel pipeline the item is being processed in. Yes the latter can be considered an internal construct of the function but exposing the latter read-only does not hurt. It may be useful to somebody (myself included lol). (P.S. Maybe it should be included in the returned WorkItemResult too.) Also, to be frank, I cannot quite wrap my head around how item index can substitute queue index in my progress bar scenario....
Let me elaborate my use case further. I am using parallel to run multiple detached long-running tasks (e.g. video encoding and object recognition) in parallel. The number of tasks is limited by the number of CPU (or in some cases GPU) cores available. So effectively I am using it like a work queue. That is why I want to have a small peek into the internals of the queues and have something to monitor and report to the users. Before encountering radash, I was using a custom implementation that bore a lot of resemblance to parallel albeit being way less elegant and way more bloated.

@rayepps I believe they two serve different purposes. The former refers to the position of the item that is being processed in the original array while the latter refers to which queue or parallel pipeline the item is being processed in. Yes the latter can be considered an internal construct of the function but exposing the latter read-only does not hurt. It may be useful to somebody (myself included lol). (P.S. Maybe I should add it to the returned WorkItemResult too.) Also, to be frank, I cannot quite wrap my head around how item index can substitute queue index in my progress bar scenario....
Let me elaborate my use case further. I am using parallel to run multiple detached long-running tasks (e.g. video encoding and object recognition) in parallel. The number of tasks is limited by the number of CPU (or in some cases GPU) cores available. So effectively I am using it like a work queue. That is why I want to have a small peek into the internals of the queues and have something to monitor and report to the users. Before encountering radash, I was using a custom implementation that bore a lot of resemblance to parallel albeit being way less elegant and way more bloated.

albeit being way less elegant and way more bloated

stop, I'm blushing

The former refers to the position of the item that is being processed in the original array while the latter refers to which queue or parallel pipeline the item is being processed in.

This makes sense. If you can bare with me a bit I'm curious if something like this would work. It's a naive example where you track the state without an index.
const results = await parallel(gpuCount, items, async (item) => {
  incrementProgress()
  // do work on item
  incrementComplete()
}

const results = await parallel(gpuCount, items, async (item) => {
  incrementProgress()
  // do work on item
  incrementComplete()
}```

Yes this is how I increment the overall progress bar. But without the queue number I cannot have by-queue (or as in this example by-GPU) progress bars.

@rayepps I have taken the liberty to add the item index as the second arguments (and the queue index becomes the third) supplied to the async functions called in parallel in case I may not have time to work on it later on.

A similar PR (https://github.com/rayepps/radash/pull/291) was merged last year so is there any reason this change is not accepted @rayepps ?
I need this and would like to avoid copy/pasting the implementation into my own codebase


[CORE-1708] Propagate cluster defaults

This PR implements propagation of cluster defaults to pipelines when the regenerate flag is true. When it is, the effective spec for each pipeline is calculated from the cluster defaults and the user spec; if the newly-calculated effective spec differs from the old effective spec, then the effective spec is replaced (as in an update pipeline operation). Furthermore, if the reprocess flag is set then the pipeline will reprocess datums (again, as in an update pipeline operation).
In order to implement this, create-pipeline transactions had to be reworked. They were previously just the create pipeline request message; they are now a special message which captures the user and effective specs in addition to the create pipeline request. Rather than implement this change in the old private ppsBuilderClient.CreatePipeline methods — uncalled in the codebase — the dead code is deleted.
The defaults-handling code is abstracted, in order to provide a single place for wrapping and unwrapping of JSON values and in hopes of improving legibility of the API server.
The former details_json name is updated to the more accurate user_spec_json, to pair with the new effective_spec_json.

couple general comments - I see CORE-1913 https://pachyderm.atlassian.net/browse/CORE-1913 - it will be interesting to see the performance impact from these new json conversions particularly for large pipelines
if regenerate changes a pipeline, will it be possible to tell the reason and distinguish it from a user update? also generally is it possible to see the source/origin of any pipeline spec field - if it's coming from defaults or not - without doing a diff?

if regenerate changes a pipeline, will it be possible to tell the reason and distinguish it from a user update?

No, not currently.

also generally is it possible to see the source/origin of any pipeline spec field - if it's coming from defaults or not - without doing a diff?

No, not currently.


initialCount is not defind for useReducer

Hi
Most programmers copy-paste the examples and play around with them until they learn how to use the API.
On the sample code given here  the code does not work because the initialCount is not defined.
It should be fixed like this:
function init(initialCount) {   return {count: 0}; }

my solution to the problem
function init(initialCount = 0) {
return {count: initialCount};
}


Potential fix for #265

I think this fix is ok as in recent versions mob_recon by default triggers mob_typer. I will check next week, Just noticed this PR


Create an oracle for channel structure

rat-king-whispers could be a channel name for users who has the governor or king advisor role to chat with the rat king


Renovate: enable auto-merge of lockfile and minor version updates

#67  👈
main

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

Join @jespert and the rest of your teammates on  Graphite

Merge activity

May 18, 6:37 AM EDT: @jespert merged this pull request with Graphite.


Is it possible to make the queue filled by multiple subprocesses?

Currently you use a subprocess to fill the queue. I wonder what is the best way to use multiple processes, when the data is hard to process. It is difficult to share a generator among subprocesses.

yes, this approach is not suited for this scenario I am afraid.


Update sbt to 1.3.3

Updates org.scala-sbt:sbt from 1.3.2 to 1.3.3.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: semver-patch

@regadas I just re-triggered it - let's see what happens.

Codecov Report

Merging #731 into develop will increase coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop    #731      +/-   ##
==========================================
+ Coverage    89.29%   89.5%   +0.21%
==========================================
  Files          114     114
  Lines         8965    8965
  Branches       325     325
==========================================
+ Hits          8005    8024      +19
+ Misses         960     941      -19

Impacted Files
Coverage Δ

.../main/scala/com/twitter/algebird/BloomFilter.scala
95.57% <0%> (+1.32%)
:arrow_up:

...main/scala/com/twitter/algebird/monad/Reader.scala
55.55% <0%> (+5.55%)
:arrow_up:

.../main/scala/com/twitter/algebird/Successible.scala
95.83% <0%> (+8.33%)
:arrow_up:

...in/scala/com/twitter/algebird/scalacheck/Gen.scala
100% <0%> (+9.09%)
:arrow_up:

...src/main/scala/com/twitter/algebird/Interval.scala
87.82% <0%> (+9.56%)
:arrow_up:

Continue to review full report at Codecov.

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


Setting a default value from  element itself

Hi again - based on your "Movies" example, I have a [select] box pulling in remote data. What's the best way to set a default value? Could it happen using the HTML element itself, it would it need to happen from within the selectize options object?

@dule
The problem with this approach is that onChange event is fired.
I need to load the page, set some initial value inline on a  and then watch for selection changes made by the user.
Something like this:
.

@temuri416: According to @brianreavis, the newest release supports a data-data field:
https://github.com/brianreavis/selectize.js/issues/155#issuecomment-72153150
But the setValue also accepts a silent param that should suppress the change event: https://github.com/brianreavis/selectize.js/blob/master/docs/api.md#methods_other

The best way to set the default value is to set the selected attribute on the option(s) that you want selected. This of course means that the selected options need to exist in the DOM first, which isn't a bad idea regardless (i.e. when you submit a form before javascript loads, you don't want your form data to be invalid).

@brianreavis
But that is not possible when select options are provided using "options" parameter.
The following trick works for me, but it's kind of ass-backwards:
<select ...>
    <option value="5" selected="selected"></option>
</select>

Select's options are populated from JSON.

@temuri416 That's not the question though, is it? For that, set items: ['5'] in your settings. I just updated the usage documentation to cover that.

Thanks... items is what I was looking for.


Remove android-apt plugin

Thank you this repository!
android-apt is now available in the Android plugin.
ref. https://bitbucket.org/hvisser/android-apt/wiki/Migration

I confirm that using 'annotationProcessor' is working as expected.

@android10
Is it possible to see this pr?

@mapyo I will try to review it this week.

@android10 ping 🙏


Extended classes; ::get() and $managed_model gridfield show objects of parent class

Affected Version
silverstripe/recipe-cms      4.9.0
Description
Classes that extend another class, show objects of that parent class in the model admin.
I expected to be able to manage the two models separately.
Also, using ::get() on the second object, returns a DataList with objects of both classes.
I expected the query to retrieve only the named class.
Note: This behaviour doesn't happen with pages
e.g. Homepage extends ContentPage but Homepage::get() doesn't return objects of class ContentPage
Steps to Reproduce
With a vanilla silverstripe install (e.g. composer create project):

put the below models into a src/Models folder, and the admin into a src/Admins folder.
Build the project
Create one of each object
Observe that the Class1 tab of the ClassAdmin displays objects of Class1 as well as Class2
Add  \SilverStripe\Dev\Debug::show(Class1::get());die; to the init() function of the PageController class
Visit the front-end and observe that the DataList contains objects of both classes.

Class 1
<?php

namespace App\Models;

use SilverStripe\Assets\Image;
use SilverStripe\ORM\DataObject;

class Class1 extends DataObject {
    private static $singular_name = 'Class 1';
    private static $table_name = 'Class1';
    private static $db = [
        'Title' => 'Varchar(255)',
    ];
    private static $has_one = [
        'MainImage' => Image::class
    ];
}

Class 2
<?php

namespace App\Models;

class Class2 extends Class1
{
    private static $singular_name = 'Class 2';
    private static $table_name = 'Class2';
    private static $db = [
        'Checkbox' => 'Boolean'
    ];
}

Class admin
<?php

namespace App\Admin;

use App\Models\Class1;
use App\Models\Class2;
use SilverStripe\Admin\ModelAdmin;

class ClassAdmin extends ModelAdmin
{
    private static $menu_title = 'Class admin';
    private static $url_segment = 'class-admin';
    private static $managed_models = [
        Class1::class,
        Class2::class
    ];
}

The workaround as per this gist:
https://gist.github.com/muskie9/107df3a689468866da1340c6af1bb4a2
public function getList()
    {
        $list = parent::getList();

        if ($this->modelTab === Class1::class) {
            $list = $list->filter([
                'ClassName' => Class1::class,
            ]);
        }

        return $list;
    }

I think this is intentional behaviour, if Class2 extends Class1 then a ModelAdmin that displays Class1::class should show Class2 as well. For example in the assets module we have Image extends File, if you were to set up a ModelAdmin that referenced File::class I’d expect that to include images too, as they are files.

Note: This behaviour doesn't happen with pages
e.g. Homepage extends ContentPage but Homepage::get() doesn't return objects of class ContentPage

That example is the wrong way around - if you call ContentPage::get(), you will get instances of HomePage included too.

if Class2 extends Class1 then a ModelAdmin that displays Class1::class should show Class2 as well.

You've got it backwards there I think @kinglozzer - you describe that ParentClass::get() should show ChildClass objects too. That's correct.
But what @jules0x is saying is that ChildClass::get() (loosely put - it seems to be specific to ModelAdmin) is showing ChildClass ✔ AND ParentClass ❌
In other words...

ModelAdmin that referenced File::class I’d expect that to include images too, as they are files.

But the issue in the OP is that a ModelAdmin to show Images is also showing e.g. a bunch text, PDF, and word documents.

But what @jules0x is saying is that ChildClass::get() (loosely put - it seems to be specific to ModelAdmin) is showing ChildClass ✔ AND ParentClass

I don’t think that’s what @jules0x is saying based on their recreation steps:

Observe that the Class1 tab of the ClassAdmin displays objects of Class1 as well as Class2

Class1 is the parent class, and they’re describing seeing Class1 and Class2 when they only expect to see Class1

🤔
Right you are in that case.
I think some clarification is needed @jules0x. There was a long Slack thread about it, to which I had thought the entire time what I've described is taking place.
But the workaround describes what you've picked up on @kinglozzer - Filtering to Class1 in the example (as the parent class - the names probably don't help) would get you only parent class items.


Adding ACL List, Show Cli

Weaver CLI is ready for review.
Commands will register them selves with CLI. In main we need to import the commands that we want them to be with the binary.
Let's say we want to separate out acls commands, we can create weaverctl in cmd/weaverctl and import only acl commands. Binary produced from weaverctl will have only acls commands and will not have acl commands.
View layers currently renders output to json, this can manipulated easily using a flag and rending to outputs like yaml, table and etc. This will be a enhancement. For now will stick to json output.

@rShetty this is done and ready for review. Will be adding create, edit cli's in future.


add julian's info to the blog authors file

Preview is available here:http://developers-pr920.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr920.previews.kube001.services.stellar-ops.com


Transfer RMSD calculation function from docking.docking.run_docking_oe to docking.analysis

"calculate_rmsd_openeye" added to asapdiscovery.docking.analysis in #88


fix defaults section to match the spec/reference_implementation

See https://github.com/popsim-consortium/demes-spec/issues/23

Closed by #209.


buffer filter: add content-length when ending stream with trailers

Description: https://github.com/envoyproxy/envoy/pull/7848 introduced content-length population in the buffer filter. However, it is only populated if the client stream ends on a data frame. This PR adds content-length population when closing the stream via trailers.
Risk Level: low - expanded functionality runtime guarded.
Testing: unit and integration tests.
Release Notes: I believe the current release notes added by https://github.com/envoyproxy/envoy/pull/7848 are still adequate.

looking at test failures


Clarify how to treat width of notification banner

What
Revisit the content about how wide to make notification banners.
Why
A user on Slack raised that the guidance is a bit ambiguous. The guidance currently says "the notification banner should be the same width as the page content".
I think what we mean is if your page content is 2/3, make it 2/3, if its full width, make it full width. But interpretations of 'page content' could differ. Worth seeing if there's a more explicit way to express this.
Who needs to know about this
Designers, content

@christopherthomasdesign I think one option (this applies to other patterns too) would be to show it in a worked example - the notification banner in the context of a wider page.

By 'page content,' do we mean individual bits of a page, or everything-on-the-page-considered-together?
Also, if the page content is full width, does that go against the 'Grid system' section of our Layout guidance?

Your main content should always be in a two-thirds column even if you’re not using a corresponding one-third column for secondary content.


Kwxm/expose optimisers (PLT-1145)

[PLEASE DON'T REVIEW THIS YET: I'm trying to fix something]
This does what it says in the changelog:

Adds  optimise options for the pir, plc, and uplc commands.
Adds a compile option for the pir command which allows a PIR file to be compiled to PLC or UPLC.
Generalises some of the other things in pir to accept both flat and textual input.

The optimise options just do the easiest things that were already available (in particular, for PIR optimisation is kind of mixed up with translation to PLC so it was tricky to expose everything that it does).  There's another ticket to add a configurable optimisation pipeline so when/if that gets done I may come back and extend the optimise commands here.

Here's something worrying.  Either I've messed up or something's not getting the types right (maybe it's not supposed to).
$ cabal exec plc example -- -s factorial > fac.plc
# <edit the file to change the final number to 20>

$ cabal exec pir compile -- -i fac.plc -o fac.uplc
# Valid PLC should also be valid PIR, so this should work

$ cabal exec uplc evaluate -- -i fac.uplc
(con integer<PHONE_NUMBER>176640000)   # Success!

$ cabal exec pir optimise -- -i fac.plc -o fac-opt.pir

$ head fac-opt.pir
(program
  [
    [
      [
        (let
          (nonrec)
          (typebind
            (tyvardecl b_4 (type))
            (fun
              [
# Looks good ...

$ cabal exec pir compile -- -i fac-opt.pir
pir: Error during PIR typechecking:
Type mismatch at () in term
  '(lam
    s_5
    [
      (lam
        a_1
        (type)
        (ifix
          (lam
            self_6
            (fun (type) (type))
            (lam a_1 (type) (fun [ self_6 (con integer) ] (con integer)))
          )
          (con integer)
        )
      )
      (fun (con integer) b_4)
    ]
    (lam
      x_7
      (con integer)
      [ [ (builtin multiplyInteger) [ (unwrap s_5) s_5 ] ] x_7 ]
    )
  )'.
Expected type
  '(fun
    (ifix
      (lam
        self_6
        (fun (type) (type))
        (lam a_1 (type) (fun [ self_6 (con integer) ] (con integer)))
      )
      (con integer)
    )
    (con integer)
  )',
found type
  '(fun
    (ifix
      (lam
        self_6
        (fun (type) (type))
        (lam a_1 (type) (fun [ self_6 (con integer) ] (con integer)))
      )
      (con integer)
    )
    (fun (con integer) (con integer))
  )'
CallStack (from HasCallStack):
  error, called at executables/pir/Main.hs:240:24 in main:Main

# Oh. :(

Thanks! This is nice.

Here's something worrying. Either I've messed up or something's not getting the types right (maybe it's not supposed to).
...

It turns out that this was because I'd failed to apply rename to the AST (although I thought that was supposed to happen during loading anyway).

I'm going to close this and open a new PR for a different branch.


How to implement ViT using eager mode?

I modified _attn_implementation in the config.json file, but it doesn't work.
"vision_config": {     "_flash_attn_2_enabled": true,     "_attn_implementation": "flash_attention_2", }

Try this
model = AutoModelForCausalLM.from_pretrained(
    model_id_or_path,
    device_map="auto",
    torch_dtype=torch.bfloat16,
    trust_remote_code=True,
    attn_implementation="eager"


Layouts

This PR addresses the layout issue where by the sidebar and TOC were not sticky and scrolled with the content.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.903%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1255

Relevant Lines:
1741

💛  - Coveralls


Rotate 90 degree?

Your lib does not Support a Rotation of certain degree? Or is it in the lib? How to Set?
Thanks for help.. +1
(Or are you expanding your Code?)

This python library (https://github.com/rm-hull/max7219) supports the "vertical" configuration needed to work with modules like this one http://www.gearbest.com/raspberry-pi/pp_391811.html
I'm going to take a look to see if I can incorporate this functionality in this library. I'll submit a PR if I get it working.

I have fixed by changing the commit() api as below :
void LedMatrix::commit() {
    byte index = B0000001;
    byte col;

    if(deviceOrientation == HORIZONTAL) {
        for (col = 0; col < myNumberOfDevices * 8; col++) {
            sendByte(col / 8, col % 8 + 1, cols[col]);
        }
    } else if(deviceOrientation == VERTICAL){ // orient the device vertically
        for (col = 0; col < myNumberOfDevices * 8; col++) {
            xcols[col] = 0;
        }
        // little inefficient, can be enhanced, rotate the matrix !
        for (col = 0; col < myNumberOfDevices * 8; col++) {

            for(byte bits = 0; bits < 8; bits++)
              xcols[col] |= ((cols[bits + 8*(col/8)] & (index << (col%8))) ?
                                     (B10000000 >> bits) : 0);
            sendByte(col / 8, col % 8 + 1, xcols[col]);
        }
    }
}

See the image on a 1x4 matrix module


/api/login is not documented in swagger and swagger documentation broken

I am trying to use groovy script to publish deploy data from Jenkins to Hygieia. Since hygieia is using JWT authentication by default /api/deploy POST method requires authentication token.
To obtain JWT token at the groovy script I need to use /api/login and it's not documented if I launch <HYGIEIA_BASE_URL>/api/swagger/index.html

@bargemb if you have time please contribute back by fixing the swaggerdocs


neocomp: init at 2019-03-12

Motivation for this change
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.

Not totally sure about this versioning scheme, but it's what's used internally.

Bump!


Add raw-window-handle feature

This PR adds a raw-window-handle feature that implements raw_window_handle::HasRawDisplayHandle for XCBConnection.

@kchibisov Do you have some time to give this a quick look? Does it seem fine? (I am not quite sure when raw-window-handle would be useful for me and I am also not sure what to do with the fields that are not set in this PR (screen and visual_id), so... it would be great if someone else could take a look at this.)

I am not quite sure when raw-window-handle would be useful for me

I ran into this issue while writing rust-windowing/softbuffer#52, while trying to register an XCBConnection into a function that takes an HasRawDisplayHandle type. While it's possible to construct my own raw handles, it's more ergonomic to pass a reference to the source object in.

I am also not sure what to do with the fields that are not set in this PR (screen and visual_id)

The raw-window-handle spec says that it is up to the consumer of the handle to fill these fields in if they need them.

(screen and visual_id)

You may not set them, however you can use default value for screen, I guess?
But the default screen should be coming from the xcb_connect. And visual is an X11 visual the window is using. In general you may omit it, however it would be impossible for client to know whether it'll have alpha mask or not for example. Though, you likely know all of that.
As @notgull said you can safely omit those values if you don't know what to provide.

Reverted in #799 due to an MSRV bump in raw-window-handle 0.5.0. See https://github.com/rust-windowing/raw-window-handle/pull/101. I also added this to the list in #538


AttributeError: 'ModelEMA' object has no attribute 'eval'

你好，我在训练的时候，epoch4之后在临时测试的时候，报了这个错误，请问是什么问题？
2024-06-26 07:44:13,280 - mmdet - INFO - Epoch [4][7000/7033]   lr: 1.000e-04, eta: 2 days, 1:50:24, time: 1.272, data_time: 0.013, memory: 15817, loss_occ: 0.2565, loss_cls: 0.0794, loss_mask: 0.3734, loss_dice: 0.7583, loss_depth: 0.1387, loss: 1.6063, grad_norm: 2.772
7
2024-06-26 07:44:55,410 - mmdet - INFO - Saving checkpoint at 4 epochs
Traceback (most recent call last):
File "./tools/train_occ.py", line 263, in
main()
File "./tools/train_occ.py", line 252, in main
train_occ_model(
File "/home/lthpc/phd/cotr/mmdet3d/apis/train_occ.py", line 350, in train_occ_model
train_detector(
File "/home/lthpc/phd/cotr/mmdet3d/apis/train_occ.py", line 325, in train_detector
runner.run(data_loaders, cfg.workflow)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 130, in run
epoch_runner(data_loaders[i], **kwargs)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 56, in train
self.call_hook('after_train_epoch')
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/base_runner.py", line 309, in call_hook
getattr(hook, fn_name)(self)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/hooks/evaluation.py", line 267, in after_train_epoch
self._do_evaluate(runner)
File "/home/lthpc/phd/cotr/mmdet3d/core/hook/eval_hooks.py", line 78, in _do_evaluate
results = multi_gpu_test(
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmdet/apis/test.py", line 100, in multi_gpu_test
model.eval()
AttributeError: 'ModelEMA' object has no attribute 'eval'
terminate called after throwing an instance of 'c10::CUDAError'
what():  CUDA error: driver shutting down
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Exception raised from query at ../aten/src/ATen/cuda/CUDAEvent.h:95 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x42 (0x7f1a8234cd62 in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libc10.so)
frame #1: c10d::ProcessGroupNCCL::WorkNCCL::finishedGPUExecutionInternal() const + 0x11a (0x7f1adf60c9ba in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so)
frame #2: c10d::ProcessGroupNCCL::WorkNCCL::isCompleted() + 0x50 (0x7f1adf60ecb0 in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so)
frame #3: c10d::ProcessGroupNCCL::workCleanupLoop() + 0x11c (0x7f1adf60f77c in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so)
frame #4:  + 0xd6df4 (0x7f1b4a3bedf4 in /lib/x86_64-linux-gnu/libstdc++.so.6)
frame #5:  + 0x8609 (0x7f1b4ff72609 in /lib/x86_64-linux-gnu/libpthread.so.0)
frame #6: clone + 0x43 (0x7f1b4fd3d353 in /lib/x86_64-linux-gnu/libc.so.6)
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 279812 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 1 (pid: 279813) of binary: /home/lthpc/anaconda3/envs/cotr/bin/python
Traceback (most recent call last):
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/run.py", line 710, in run
elastic_launch(
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 259, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
./tools/train_occ.py FAILED
Failures:
[1]:
time      : 2024-06-26_07:44:59
host      : lthpc-Super-Server
rank      : 2 (local_rank: 2)
exitcode  : 1 (pid: 279814)
error_file: <N/A>
traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html

你好，我在训练的时候，epoch4之后在临时测试的时候，报了这个错误，请问是什么问题？
2024-06-26 07:44:13,280 - mmdet - INFO - Epoch [4][7000/7033] lr: 1.000e-04, eta: 2 days, 1:50:24, time: 1.272, data_time: 0.013, memory: 15817, loss_occ: 0.2565, loss_cls: 0.0794, loss_mask: 0.3734, loss_dice: 0.7583, loss_depth: 0.1387, loss: 1.6063, grad_norm: 2.772 7 2024-06-26 07:44:55,410 - mmdet - INFO - Saving checkpoint at 4 epochs Traceback (most recent call last): File "./tools/train_occ.py", line 263, in main() File "./tools/train_occ.py", line 252, in main train_occ_model( File "/home/lthpc/phd/cotr/mmdet3d/apis/train_occ.py", line 350, in train_occ_model train_detector( File "/home/lthpc/phd/cotr/mmdet3d/apis/train_occ.py", line 325, in train_detector runner.run(data_loaders, cfg.workflow) File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 130, in run epoch_runner(data_loaders[i], **kwargs) File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/epoch_based_runner.py", line 56, in train self.call_hook('after_train_epoch') File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/base_runner.py", line 309, in call_hook getattr(hook, fn_name)(self) File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmcv/runner/hooks/evaluation.py", line 267, in after_train_epoch self._do_evaluate(runner) File "/home/lthpc/phd/cotr/mmdet3d/core/hook/eval_hooks.py", line 78, in _do_evaluate results = multi_gpu_test( File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/mmdet/apis/test.py", line 100, in multi_gpu_test model.eval() AttributeError: 'ModelEMA' object has no attribute 'eval'
terminate called after throwing an instance of 'c10::CUDAError' what(): CUDA error: driver shutting down CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect. For debugging consider passing CUDA_LAUNCH_BLOCKING=1. Exception raised from query at ../aten/src/ATen/cuda/CUDAEvent.h:95 (most recent call first): frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x42 (0x7f1a8234cd62 in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libc10.so) frame #1: c10d::ProcessGroupNCCL::WorkNCCL::finishedGPUExecutionInternal() const + 0x11a (0x7f1adf60c9ba in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so) frame #2: c10d::ProcessGroupNCCL::WorkNCCL::isCompleted() + 0x50 (0x7f1adf60ecb0 in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so) frame #3: c10d::ProcessGroupNCCL::workCleanupLoop() + 0x11c (0x7f1adf60f77c in /home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/lib/libtorch_cuda_cpp.so) frame #4: + 0xd6df4 (0x7f1b4a3bedf4 in /lib/x86_64-linux-gnu/libstdc++.so.6) frame #5: + 0x8609 (0x7f1b4ff72609 in /lib/x86_64-linux-gnu/libpthread.so.0) frame #6: clone + 0x43 (0x7f1b4fd3d353 in /lib/x86_64-linux-gnu/libc.so.6)
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 279812 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 1 (pid: 279813) of binary: /home/lthpc/anaconda3/envs/cotr/bin/python
Traceback (most recent call last):
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/run.py", line 710, in run
elastic_launch(
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 131, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/home/lthpc/anaconda3/envs/cotr/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 259, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
./tools/train_occ.py FAILED
Failures: [1]: time : 2024-06-26_07:44:59 host : lthpc-Super-Server rank : 2 (local_rank: 2) exitcode : 1 (pid: 279814) error_file: <N/A> traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html

抱歉，这是由于eval_hook.py文件的错误导致的。你可以将mmdet3d/core/hook/eval_hook.py中Line 62和79改为runner.ema_model.ema_model以修复这个bug


New moon in-app icon cuts out Nitro in-app icons.

well crap, i don't have nitro sooo...
could you inspect element and send a screenshot of the html tree?

also, would you rather keep the nitro icon or the moon? it might be possible to only show the moon on the default discord icon.

well crap, i don't have nitro sooo...
could you inspect element and send a screenshot of the html tree?

I'm no developer at all so this might not even be what you need.

You can use the Nitro app-icons yourself without Nitro when enabling FakeNitro in Vencord's plugin tab.

also, would you rather keep the nitro icon or the moon? it might be possible to only show the moon on the default discord icon.

I don't like the moon at all so I'd rather just stick with the Nitro icons. Not to mention that I'd probably use them anyway to feel less embarrassed about spending 10€ a month for Discord.

i pushed a fix (using the preview nitro icon), please verify it works.

i pushed a fix (using the preview nitro icon), please verify it works.

Yep, works just fine. Thanks.


Support for PHP 8.0

Is this in the works?
We have a project where we use PHP 8.0 and would love to use this package to distinguish between production and development tabs in the browser.

Maybe #14 would close this?

Seem like no support anymore on this :(

@vajda-media PR was merged long ago and release was made. So it does support PHP8


Google Universal Analytics

Google analytics social event tracking with _trackSocial is no longer supported by universal analytics and analytics.js
Sharrre should use the social interactions method
https://developers.google.com/analytics/devguides/collection/analyticsjs/social-interactions

Additionally there is the tag manager, which uses a dataLayer array. Instead of _gaq.push() (old google analytics) or ga() (new universal analytics) it would have to use dataLayer.push().
See also http://www.simoahava.com/analytics/google-tag-manager-track-social-interactions/


Sending object fails on node 7.x

var express = require('express');
var expressWs = require('..');

var expressWs = expressWs(express());
var app = expressWs.app;

app.use(function (req, res, next) {
  console.log('middleware');
  req.testing = 'testing';
  return next();
});

app.get('/', function(req, res, next){
  console.log('get route', req.testing);
  res.end();
});

app.ws('/', function(ws, req) {
  ws.on('message', function(msg) {
    console.log(msg);
    ws.send({test: 'test'});  //<== will fail with "TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object."
  });
  console.log('socket', req.testing);
});

app.listen(3000)

Hi,
I think this snippet would also fail on earlier versions of Node. ws.send() doesn't do any implicit JSON encoding of the data. To transfer an object you would need to encode & decode it explicitly.
The current implementation directly exposes a WebSocket type object from the API of the ws library. It might make sense for us to augment the ws object a little bit here though. I can understand that it's confusing when you're able to pass objects to res.send(), but not to ws.send().

Actually express-ws uses ws to send data, and ws supports sending objects Sender.js

I agree that res.send() and ws.send() may be confusing but the send() method does not work with objects in the WebSocket browser interface.
If you pass an object you'll get the result of obj.toString().
As per this comment https://github.com/websockets/ws/issues/1102#issuecomment-300487700 I think that a WebSocket library should not have anything to do with SerDes.

OK, I closed the issue on ws. I will close the issue here too if there is no agreed resolution. It's really a minor issue for new-comers and code readability. This is a really small enhancement.
I would prefer to write just ws.send({test: 'test'}); and not ws.send(JSON.stringify({test: 'test'})); and in client JSON.parse everywhere, it's more readable for me, and more logical, I'm sending an object and I don't care what method it is doing for SerDes, and in the client I should receive the same object so the complexity should be abstracted from the developer.

// This middleware lets you send objects on websockets.
app.use((req, res, next) => {
  if (req.ws && isinstance(req.ws, WebSockket)) {
    let oldSend = req.ws.send
    req.ws.send = function() {
      let args = [].slice.call(arguments, 0);
      let arg0 = args[0]
      if (Object.prototype.toString.call(arg0) == "[object Object]") {
        let arg0String = JSON.stringify(arg0);
        args[0] = arg0String;
      }
      oldSend.apply(this, args)
    }
  }
  next()
})


toMetadata for String splits long strings

Closes #1343.
Pre-review checklist

[x] All code has been formatted using our config (make format)
[x] Any new API features or modification of existing behavior is covered as defined in our test plan
[x] The changelog has been updated under the ## Unreleased header, using the appropriate sub-headings (### Added, ### Removed, ### Fixed), and the links to the appropriate issues/PRs have been included

According to the CIP-25 metadata standard, strings longer than 64 bytes should be split into arrays of strings of a smaller size. This PR causes strings to automatically be split as such

@rynoV npm run test is not enough, make run-ci-actions is the way

Re-creating here https://github.com/Plutonomicon/cardano-transaction-lib/pull/1356 for CI to run. Thanks!


认领Defi task 11

No description provided.

Great!  Do you want to dome research on open?  You may claim it on Issue.  Please read the link https://github.com/rebase-network/Dapp-Learning/blob/main/docs/dao.md
add WeChat to join our developer group


(Short time) network disconnection on primary instance could mislead MOCO into believing that errant transactions have occurred on replica instances

Describe the bug
In our environment, we experienced a brief network disconnection (for reasons unrelated to MOCO) and received the following errors.

primary
2022-06-24T04:15:53.924593Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001158 - Got an error reading communication packets
2022-06-24T04:15:53.925788Z 16406 [Note] [MY-011171] [Server] Stop semi-sync binlog_dump to slave (server_id: 805432148).
2022-06-24 13:15:53

replica
2022-06-24T04:15:53.894865Z 16087 [Note] [MY-011026] [Repl] Slave I/O thread killed while reading event for channel ''.
2022-06-24T04:15:53.894958Z 16087 [Note] [MY-010570] [Repl] Slave I/O thread exiting for channel '', read up to log 'binlog.000121', position 807839346

No failover occurred because the network disconnection was immediately resolved. However, MOCO detected an errant transaction in the replica (moco_cluster_errant_replicas{} = 2) and declined to execute a START SLAVE. Investigation using SHOW BINLOG EVENTS did not find any errant transactions.
Environments

Version: v0.12.1 (chart-v0.2.3)
OS: Flatcar Container Linux (stable)

To Reproduce
Steps to reproduce the behavior:

Create MySQLCluster
Use benchmarking tools to ensure that transactions are constantly being committed
Disconnect the network connection between the primary instance and the replica instances
See moco_cluster_errant_replicas

Expected behavior
In evaluating an errant transaction, the primary instance is treated as having the GTID of a transaction that has been committed to binlog but not committed to InnoDB.
Additional context
This behavior can be occured in loss-less semisynchronous replication. In this configuration, the primary instance commits the transaction to InnoDB only after confirming that the replica has received the transaction's binlog.
Consider the case where a network disconnection occurs while a replica is sending packets acknowledging receipt of transaction binlog. The replica SQL thread can apply the received binlog to its own InnoDB, whereas the primary cannot commit the transaction to InnoDB due to the constraint of loss-less semisynchronous replication.

A possible workaround would be to START SLAVE anyway when the replica seems to have an extra transaction.

Fixed.
https://github.com/cybozu-go/moco/pull/491


Add bit grooming in MAPL?

The guru of NCO, @czender, came up with a cool variant of bit shaving called "bit grooming" as detailed in this poster with @JeremySilver and this paper. (And another!)
Whereas bit shaving uses just zero bits, bit grooming alternates between 0's and 1's. This helps with bias of the shaved/groomed data.
Now, MAPL can bit shave (though maybe not exactly like NCO does), so maybe we can look at adding the grooming algorithm as well to our online netCDF writing. Of course, our code is in C and I'm already night-useless with bit-shifting in Fortran (hello ishft!) so hacking our C code might be beyond me. So I'll assign others, though maybe this is a good opportunity for me to brush up on C... 😄

Look for BitGrooming to arrive in the next version (4.8.2) of the netCDF C and Fortran libraries.

ooh. Huh. Well, maybe that solves things in another way! :)

And because @czender has updated NCO for a new algorithm:
A. Lossy quantization algorithms have been refactored. First, the
   attribute name that store the level of quantization are now
   algorithm-specific, e.g.,
   QuantizeBitGroomNumberOfSignificantDigits. Previsously, NCO
   stored the NSD attribute number_of_significant_digits. However,
   this was deemed too ambiguous, given the increasing number of
   supported quantization methods. The new attribute names better
   disambiguate which algorithm was used to quantize the variable.
   Second, the default algorithm has been changed from BitGroom with
   BitRound masks from R. Kouznetsov (2021), to what we call Granular
   BitGroom (GBG). GBG combines the best features of BitGroom,
   BitRound, and DigitRound by Delaunay et al. (2019).  Bit-Groom/Shave/Set are described here:
   http://nco.sf.net/nco.html#ppq
   http://nco.sf.net/nco.html#gbg

cf., http://nco.sourceforge.net/nco.html#gbg
I'll use this issue so I can keep track of the references:

R. Kouznetsov (2021)
Delaunay et al. (2019)

as well as any experiences I have with NCO 5.0.3 and the new options (once I get it into Baselibs).

@tclune Pros and cons of layer-by-layer scaling is discussed, with respect to bit grooming and packing, in this paper. The method you describe can be used in conjunction with packing to improve the compression relative to BitShaving alone. Everyone has different tolerances for how much precision, dynamic range, speed, and portability they are willing to sacrifice during lossy compression. You are in a good position to make an informed judgement about all that because your group has obviously thought about it a lot, and with NCO 5.0.3 you can experiment with new algorithms pretty easily.


Fix #5213, set boolean options in config file.

Kind of change
Bugfix
Related
fix #5213
More information
When set any boolean option in webpack config file (like: profile, cache ,bail, v.v... ), it's broken.
After this PR, all will work usual.

Wait, it's not done. I still working.

@sokra it's done. Please review it <3. Thank you.

Yes @sokra, i will add it tomorrow.

Great


Disable scrollTop event

Hello,
The plugin is amazing! I am new to jQuery, but I was able to get right in and this functional beyond my expectations.... The problem I am having is that I can't figure out how to disable the scrollTop event from happening when a sticky element is displayed. I need the sticky element to .fadeOut/In without repositioning the window.
Would you mind sharing some thoughts on disabling the scroll event?
Thanks again for the plugin... Brilliant...

I am guessing I would adjust lines 42-46 (see below), but when I comment it out, it breaks the plugin...
scroller = function() {
  var scrollTop = $window.scrollTop(),
    documentHeight = $document.height(),
    dwh = documentHeight - windowHeight,
    extra = (scrollTop > dwh) ? dwh - scrollTop : 0;

Is there a fix to this?  It would be nice to not have the content scrolled to the top when its stuck/unstuck.


[InputBase] Fix cursor on disabled state

Resolves #13000.

@itskibo Good call! Thank you for digging into it and not picking what I suggested 👍


"Publish" in Squiggle AI

(done on top of still unmerged #3463)

In that deployed URL, I got an error:

I feel like the terminology in this PR can be improved. Right now it seems confusing to me.

Change "Publish" to "Publish Model"

Add some text saying, "Save this as a model on Squiggle Hub"
Change "Publish Workflow" to "Save Model"
Change "Publish" to "Save"
(At very least, I think "Publish Workflow" is misleading, as it's the model you are publishing)

In that deployed URL, I got an error, when I tried Publishing. I assume some of the issue is just the fact that this this test environment on Vercel isn't fully set up. (In which case it would be nice if you could fix that)

Strange, it's working fine for me. Does this happen every time you try?

I feel like the terminology in this PR can be improved. Right now it seems confusing to me.

Fair, fixed


added spinnaker header

We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
https://devopsmx.atlassian.net/browse/OP-6971

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://spin.prod.opsmx.com/#/applications/gitprtrigger/executions/details/01FAFD4RE0JKR8H8R9A7QT5BN1

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://spin.prod.opsmx.com/#/applications/gitprtrigger/executions/details/01FAFESVN4VAKQX3TC3YAVNDAC

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://spin.prod.opsmx.com/#/applications/gitprtrigger/executions/details/01FAFG2ZMV3C6KVTH7KS0N2009


Tags/NavBuilder: Navigation should come from new Nav object

As a Reaction storefront user, I can view the navigation built by the admin, so that I can see a nice custom Navigation.
As a followup to https://github.com/reactioncommerce/reaction/pull/4683, the navigation should come from the new navigation tree object.
Dependency
https://github.com/reactioncommerce/reaction/pull/4683

@machikoyasuda We were looking at asking @kieckhafer to do this as part of the SE team since this is something we need but are y'all going to handle it?

@zenweasel We are not going to be doing it in this Sprint. @kieckhafer - it's all yours.

More info from the ticket I had created: https://github.com/reactioncommerce/reaction-next-starterkit/issues/427

@zenweasel @dancastellon is there a limit to how deep the tag tree can go? Currently I think we have two levels of sub tags under navigation. Are we keeping it at two levels? and if not, do we have designs for going deeper than 2?

@kieckhafer I believe we agreed to keep it as is - 3 levels deep (Shoes -> Casual -> Sneakers for example).

Yeah, I think we currently support 3 (at least in the Classic UI we did) and that's all we should do for now


feature | updating cost management budget thresholds

What?
Update cost management thresholds.
Why?
The threshold was too low generating false positive alerts.

@marcosgacosta Markz just approved it and I'll merge it in this occasion in order to create the latest release of the Ref Arch. Thanks for your collab!


Cannot remove adaptive lighting switch from HA

I tried to remove an adaptive_lighting switch by commenting it out in the YAML, but it still shows up in HA.
The following switch still shows up in HA:
adaptive_lighting:
  # - name: Dining
    # <<: *lightsettings
    # interval: 270
    # lights:
      # - light.dining_lights_template

I've actually deleted the whole switch from my YAML config, but it still shows up in HA:

switch.adaptive_lighting_dining
off
brightness_pct: null color_temp_kelvin: null color_temp_mired: null rgb_color: null xy_color: null hs_color: null sun_position: null friendly_name: Adaptive Lighting: Dining icon: mdi:theme-light-dark

How do I permanently remove adaptive lighting switches that I no longer want?
Really like this component.
Thanks.

I have the same problem and also want help

So adaptive lighting now shows up on the integration page (configuration-->integrations). I was able to delete the switch from there by selecting the switch I didn't want, clicking the 3 vertical dots and selecting the red delete option.


[Issue 2267]Extension - Add fields to update logo for custom token/network

Allow user to update logo for custom network/token. To do it, add a textbox field to contain the link (online) to the logo.  The following screen have been updated:
Import token
Token detail
Import network
Network detail

🚀 Deployed on https://pr-2312--sw-web-runner.netlify.app


better README

We should have a better readme explaining what and why bush is. Maybe some example commands / scenarios.

The README.md at the root of the repository should explain everything because it is what people will read. However the README.md inside the client/ folder is the one used for the distribution of the python package so it should be complete as well.
This means we will have some content duplication between those two. Does anyone see a solution to this?

This is WIP on #41.

[x] global readme
[x] client readme
[ ] server readme