pandas df with datetime.date cols returns false differences if ignore_case=True

When ignore_case=True, identical values with type datetime.date will be reported as unequal.
This happens because in core.py/columns_equal() the attempt to call str.upper() on the col for case insensitive-comparison will throw an exception. The try/except returns false for any caught exception.
import pandas as pd
import datacompy
import datetime

df1 = pd.DataFrame([{'date_field':datetime.date(2024,5,8)}])
df2=df1.copy()

print("incorrectly reports unequal")
results = datacompy.Compare(df1=df1,df2=df2,on_index=True, ignore_case=True)
print(results.report())

results = datacompy.Compare(df1=df1,df2=df2,on_index=True, ignore_case=False)
print("Works correctly")
print(results.report())

So it seems to be an issue of datetime.date vs datetime.datetime. date returns an O (object) vs datetime which returns a type of M. We could just convert all objects to "strings" and then compare, but I'm sure that will break something else.

Hi [@fdosani ],
I understand that the issue arises because datetime.date returns an object type 'O', while datetime.datetime returns a type 'M'. Applying str.upper() to non-string types like datetime.date throws an exception, leading to the incorrect comparison.
Proposed Solution:
To resolve this issue, I propose updating the columns_equal() function in core.py to handle non-string types more gracefully. Here’s the approach:

Check if the column values are strings before applying str.upper():

If the values are of type str, apply the case-insensitive comparison using upper().
If the values are of another type (e.g., datetime.date), fall back to the default equality comparison without case sensitivity.

Example of How It Could Be Implemented:
def columns_equal(col1, col2, ignore_case=False):
    try:
        # Apply case-insensitive comparison for strings only
        if isinstance(col1, str) and isinstance(col2, str) and ignore_case:
            return col1.upper() == col2.upper()
        else:
            return col1 == col2
    except Exception as e:
        # Log the error if needed, and return False
        return False

@divithraju Sorry for the delay and appreciate the effort here. I don't think you can check isinstance(col1, str) since you are checking the column which is of type: pandas.core.series.Series. It will never equate to true. I have a fix in the works for this.

@ak-gupta @jdawang Want to get your thoughts here on a specific proposal. The main issue is with Pandas you can have mix typing with object columns. This can lead to really funky situations.
I think we should stop supporting mixed typing. Especially with arrow becoming the standard it is something which will be a thing moving forward even with Pandas if and when they make a full switch over. Ideally we can just not support mixed types and if it is mixed we just return a default False. Are you both OK with this?
Here is a PR with the actual proposal: https://github.com/capitalone/datacompy/pull/335

No need for a PR I've already put one up in as referenced above.


NFD_SaveDialog is missing a pre-set filename

Compilation Environment
Java - LWJGL (version 3.2.3)
Describe the bug
I am missing an option to pre-set the filename for the NFD_SaveDialog. I am able to pre-set the path, but not the filename itself.
User Description
I am about to introduce NFD for the tool tinyMediaManager as a replacement of the JavaFX file open dialog (since there is no other dependency to JavaFX)

yes, this is highly needed, voted

3f3e7956915bbbc355e0a2f6daf0e6c2080be001 on devel branch enables pre-set filenames for all relevant dialogs.

3f3e7956915bbbc355e0a2f6daf0e6c2080be001 on devel branch enables pre-set filenames for all relevant dialogs.


HSEARCH-3338 +  HSEARCH-3368 Javadoc fixes and improvements

https://hibernate.atlassian.net//browse/HSEARCH-3338
https://hibernate.atlassian.net//browse/HSEARCH-3368
This is mostly about the predicate and sort DSLs.

Pull Request Test Coverage Report for Build 1

7 of 10 (70.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 86.708%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

engine/src/main/java/org/hibernate/search/engine/search/dsl/predicate/impl/SearchPredicateContainerContextImpl.java
2
3
66.67%

engine/src/main/java/org/hibernate/search/engine/search/dsl/predicate/spi/DelegatingSearchPredicateContainerContextImpl.java
0
2
0.0%

Totals

Change from base Build 16:
0.002%

Covered Lines:
10131

Relevant Lines:
11684

💛  - Coveralls

Looks good.

Fixed the typo and merged. Thanks!


Scaffolding pages

wireframe: https://www.figma.com/file/x49RWTMPXmN5UgbaCAkraN/wallet

@IronLu233 any update for this issue?


Pause on touch in cellphone not work

I try to pause video by touch on video but i cant do that , so pause video just work when touch on pause button.
In window browser by click on video frame, video paused.

This is intended. Tapping in the video on a touch device will show the controls. Much like other players do.

I set options visible (hideControls: false), but touch not work for pause video.

Sorry, you're right. That is a bug then. I'll check it out.

Just pushed a fix for this in the latest version 👍


versioning and tagging releases

We generally try not to have egregious breaking changes in this library, but we're also not afraid to do them when necessary (the latest example being #375).  We've gotten a couple of people asking for us to use semver on google/go-querystring#11, which we could also consider doing here.
That doesn't help us for #375, but would allow us to do future breaking changes at a version boundary.  I have no intention of changing the import path to use gopkg.in or anything like it, but it would still help set appropriate expectations for folks when they do upgrade to a new version.  And keeping a CHANGELOG.md file might be nice (although a bit of work to keep up to date) to point out new APIs that we support, etc.
@gmlewis @shurcooL what do you think?

To me, vendoring makes this a moot issue - users can upgrade when they are ready and vendor the version they wish to use. This is ideal, however, and does not represent everyone's workflow. But it is something to suggest as people come pointing fingers about blame.
I had a package break due to the addition of a parameter to PullRequestsService.Merge. I fixed it and moved on. Go makes it very easy to deal with small breaking changes like that.
Moving the canonical source to gopkg.in is, in itself, a breaking change, right? Now that Go forces you to use the canonical import path?

I suppose there are varying levels of supporting semantic versioning as well.
The bare minimum is to have a file somewhere in the repo with a version string in it.
A step up would have a compiled file with a const string in it that gets bumped.
This repo already has libraryVersion which appears to have remained at 0.1 since the beginning.
On other projects that I supported, maintaining a CHANGELOG.md was a pain and I always wondered if anyone ever really looked at it or found it useful.
All that said, I don't have really strong opinions either way.
My recommendation moving forward is to bump libraryVersion to 0.2 in #375 since it is a breaking change and let the commit message suffice for the change log. Let people vendor the library as they see fit.

Moving the canonical source to gopkg.in is, in itself, a breaking change, right?

In case you misread, I have zero intention of moving to gopkg.in.  It think it's a clever service and I greatly respect Gustavo, but I'm not about to add an extra single point of failure that I have no control over to how people access this package if I don't have to.  And I definitely don't want to cede control of the namespace; I actually don't even like "github.com" in the import path either (as you know from my personal packages), but I don't have a good Google controlled hostname that would work well for this.  And as you point out, vendoring mostly obviates the need for a service like gopkg.in.
All that said, there are still other advantages to versioning and tagging the library, some hypothetical/theoretical, some practical.

A tagged release my carry with it some extra assurance of stability or having been more thoroughly tested (for example, running go 1.6.x versus tip).  That's not really an issue with go-github, since we tend to keep master well tested.
As pointed out in https://github.com/google/go-querystring/issues/11#issuecomment-226850306, glide supports semver similar to Gemfiles where you can specify a major version you want and it will always grab the latest within that range.
Even if you're not using glide (or any other vendoring tool for that matter), sticking to semver sends a signal as to what users of the library can expect (in terms of compatibility) from a given release.

Now even with that said, I don't typically version my go libraries because I always vendor anyway, and versioning is not all that common in the go community.  And I don't relish the idea of trying to keep a changelog up to date, making decisions about version numbers, etc.

I don't have strong opinions, but I would hope we lean towards doing the simpler thing. A more complex solution IMO is going to add overhead and little actual benefit.

My recommendation moving forward is to bump libraryVersion to 0.2 in #375 since it is a breaking change and let the commit message suffice for the change log. Let people vendor the library as they see fit.

I agree with this recommendation, but maybe just make it an integer and increment it by 1 with every breaking API change (so, make it "2"). I don't think it's valuable for us to track the minor and patch parts of semver with every commit.
We have great commit messages, let's keep that up.
We may make some minor breaking API changes, but only when it makes sense, leads to a better API, and isn't hard to update. If you're vendoring go-github, you update whenever you want and re-vendor. If you choose not to vendor (knowing the risks and choosing to accept them), you update right away. This API of this package is quite mature and unlikely to change or evolve much in the future.

Another observation is that this library tends add support for new GitHub API features while those are still in preview, which means if you choose to use those features, they may break at any point. That just goes without saying, but I guess I'm saying it anyway. If you need full reliability at all times, you must vendor go-github AND not use any of the preview API endpoints.

sounds good to me... we'll leave things as they are.

A timely post: http://dave.cheney.net/2016/06/24/gophers-please-tag-your-releases

I wonder if @davecheney has seen this thread when writing that.

I was going to make a big comment after my request for versioning go-querystring was closed, but Cheney covered my thoughts pretty well.

That's Mr. Cheney.
On Sat, 2 Jul 2016, 01:19 Jim Deville<EMAIL_ADDRESS>wrote:

I was going to make a big comment after my request for versioning
go-querystring was closed, but Cheney covered my thoughts pretty well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/go-github/issues/376#issuecomment-229974232,
or mute the thread
https://github.com/notifications/unsubscribe/AAAcAz2_Mi87Pp6RTFvkNRtKZdzRaPwcks5qRS_-gaJpZM4I4qYJ
.

Hi,
I d like to re open that issue. As i faced a build issue with your repo because i basically can t track it via semver.
I m using glide, and yeah, despite all, this particular case where a dependency relies on a commit is not handled in a satisfactory way.
Whatever, i m just arguing that having a git tag x.x.x is not an overwhelming load in your process.
I d like also to point out that i developed method to help to manage a changelog, version bumping and so on.
this or that, please consider tagging your git.

Reopening this discussion, particularly in light of the direction that https://github.com/golang/dep is taking.  It will support specifying specific versions of dependencies, presumably relying on git tags, though I haven't tried it out yet.  See also my comment in #529 that I'm not sure that the libraryVersion const is actually doing us any good since it doesn't protect against build breakages.
To @shurcooL's point above, if we go this route, we will need to decide (and document) when we bump which version numbers.  semver is pretty clear on most of that, but what about the preview APIs?  Do we explicitly call them out in the godocs and say that they are excluded from any versioning policy?
This is somewhat complicated by the fact that many of our standard API calls are actually using a preview media type in order to get some different behavior or extra information in the response.  In those cases, do we say that only the subset of behavior or fields are excluded from the versioning policy? (I think the answer has to be "yes", since otherwise we could be taking a previously stable method and regressing it back to preview status).

Instead of using SemVer, which greatly complicates things and will favor backporting when a breaking change is made, simply tag big changes as v1, v2, v3, etc and allow people to upgrade to discrete points in time, as requested. Anytime you have N commits on master, you could automatically tag a new release. There would be no "minor" or "patch" releases, as they complicate things for the end user and for maintainers. 💭

Instead of using SemVer, which greatly complicates things and will favor backporting, simply tag chunks of changes as v1, v2, v3, etc and allow people to upgrade to discrete points in time, as requested. Anytime you have N commits on master, you could automatically tag a new release. There would be no "minor" or "patch" releases, as they complicate things for the end user and for maintainers. 💭

Nothing in semver says when you have to cut releases.  So we could simply decide to only cut releases at major versions, call them v1.0.0, v2.0.0, etc.  That would achieve the same result and still be semver compatible.
I'm not entirely sure we want to do that (only tag at major versions), but it's at least an option.

@shurcooL or a third option, if we're willing to deal with both major and minor versions:
a) major version is bumped with any breaking change to non-preview functionality, including changes to function signatures or behavior.
b) changes to preview functionality would only require a minor version bump.  The non-preview functionality hasn't changed, so does not necessitate a major version bump, but by cutting a new minor release it gives us an opportunity to call out what new APIs have been added, etc.  The frequency of cutting these releases is of course at our discretion... maybe queue them up for a bit so it doesn't add too much overhead.

Instead of using SemVer, which greatly complicates things and will favor backporting

Semver doesn't imply any level of support or backporting of bug fixes onto older branches.  I would be completely fine saying that we only focus on supporting master (and maybe the latest tagged release).  Older releases are simply there as a convenience to avoid the inevitable breakages that will happen when you build against master.
And if golang/dep adopts semver, which it sounds like they will, then we may not have a choice but to follow suit (which I'm fine with).
Also, it could be said that older versions come with the exact same level of support as the master branch... none at all.  (Or "best effort" if you prefer.)

Any other final thoughts on this topic?  I haven't heard adamant opposition to moving forward with semver tagging, so I'm going to plan on that being the path forward.  I'll put together a PR that updates our docs to talk about how we handle versioning.

Can you quickly summarize the final semver scheme you're thinking of going with? We've discussed at least 3 options above, so I'm not sure which one you're referring to.

Hi @willnorris @shurcooL, Is something finalized on this? If yes are we tracking it somewhere else? Also, I want to know if there's anything I can help with :)

I'm waiting on a summary of the final semver scheme that @willnorris had in mind. It's a little hard to deduct from reading the comments above, because a lot of different options were being discussed with back and forth.

yep, this is squarely on me.  I'll try and carve out some time soon.


Live dash not playing on shaka due to 20ms innacuracy time

Have you read the FAQ and checked for duplicate open issues?
Yes
If the problem is related to FairPlay, have you read the tutorial?

N/A
What version of Shaka Player are you using?

Latest
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Yes
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
FF and Chrome MAc
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

What configuration are you using?  What is the output of player.getNonDefaultConfiguration()?

Default configuration
What did you do?

I play a live but the buffer associated to the live is full of hole.
This happen after the each manifest refresh
What did you expect to happen?
The playback to work and the video buffer to be fully filled without any hole into it
What actually happened?

Each next segment (Reference) that should be added into the timeline is skipped due to inaccuracy of 20ms in the manifest.
here the code associated
// Append timeline
     let newEntries;
     if (currentTimeline.length) {
       const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
       newEntries = info.timeline.filter((entry) => {
         **return entry.start >= lastCurrentEntry.end;**
       });
     }

if we introduce an accuracy tolerance of few ms all is working fine and we are not removing the next segment for the timeline.
 // Append timeline
      let newEntries;
      if (currentTimeline.length) {
        const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
        newEntries = info.timeline.filter((entry) => {
          **return entry.start >= (lastCurrentEntry.end - 0.5);**
        });
      }

or this approach but not tested on my side
 // Append timeline
      let newEntries;
      if (currentTimeline.length) {
        const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
        newEntries = info.timeline.filter((entry) => {
          **return entry.end > lastCurrentEntry.end;**
        });
      }

event if it's working with that approach i'm not sure it's correct.
I also share the manifest format
Are you planning send a PR to fix it?
If you agree on the possible approach yes otherwise i'm happy to help you to reproduce
I have already a possible solution but i'm not sure it's correct and i would like to have your adivce
I don't want to make shaka break
SegmentTemplate of the manifest at the first download
<Representation id="1" width="1920" height="1080" sar="1:1" frameRate="50" bandwidth="4423000" codecs="avc1.64002a">
             <SegmentTemplate initialization="XXXXXX" media="XXXXX" timescale="1000"  startNumber="77">
                <SegmentTimeline>
                  <S t="346554266" d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                </SegmentTimeline>
             </SegmentTemplate>
           </Representation>

SegmentTemplate of the manifest at the second download
<Representation id="1" width="1920" height="1080" sar="1:1" frameRate="50" bandwidth="4423000" codecs="avc1.64002a">
              <SegmentTemplate initialization="XXXXXXX" media="XXXXX" timescale="1000"  startNumber="78">
                 <SegmentTimeline>
                   <S t="346556266" d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                 </SegmentTimeline>

I propose the following solution to address the live issue


Bugfix computeObject null handling.

Since null is an object, this method would try to call Object.keys on null, causing an error.

Thanks @lukeasrodgers. I'll publish a new release ASAP.

Cool thanks.


docs: Update SECURITY.md for Ireland release.

Close #3341
Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number:
Closes #3341
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

cc @Castle1984

Codecov Report

Merging #3546 (c57c61f) into master (ebe3624) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3546   +/-   ##
=======================================
  Coverage   47.57%   47.57%
=======================================
  Files         120      120
  Lines        8301     8301
=======================================
  Hits         3949     3949
  Misses       3974     3974
  Partials      378      378

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 ebe3624...c57c61f. Read the comment docs.

Merging blocked by compile tools issue
[2021-06-08T14:51:19.092Z] + make build
[2021-06-08T14:51:19.092Z] go mod tidy
[2021-06-08T14:51:19.355Z] go mod tidy: go.mod file indicates go 1.16, but maximum supported version is 1.15
[2021-06-08T14:51:19.355Z] makefile:19: recipe for target 'build' failed
[2021-06-08T14:51:19.355Z] make: *** [build] Error 1
[2021-06-08T14:51:19.616Z] Failed to run 'override-build': Exit code was 2.
[2021-06-08T14:51:19.616Z] Run the same command again with --debug to shell into the environment if you wish to introspect this failure.


"Best image" should be aerial, not other categories

Description
In NRW there are two data layer marked as "best", one ALKIS and one aerial imagery.
It looks like the system picks the first "best" imagery of any category sorted by name.
However, I think it should look for a "best" image of category aerial imagery first and only then fall back to a list of all "best" layers.
Test area: https://www.openstreetmap.org/edit#map=18/50.82658/6.35559
Screenshots

I marked this as "good first issue" because I assume that the part of the code that handels the layer that is selected by default should be straight forward to find and adjust as described above. But I did not look into it myself, yet.

This is an issue for editor-layer-index, not iD

This is an issue for editor-layer-index, not iD

@bhousel Only if ELI defines that the "best" option should only be applied to aerial imagery. The Alkis layer is in fact the best of it's category.
I don't think it unreasonable to specify a "best" per category.
Unfortunately, ELI's documentation on the topic of category and "best" ist not that extensive.

What are your concerns in adding this check in iD/Rapid?

What are your concerns in adding this check in iD/Rapid?

If the data is set up wrongly in the source, it should be fixed there, not by the imagery consumers.
best does have a well defined meaning, (it's a local override to the global Bing default), and it shouldn't be set for a source that's not orthoimagery for tracing.

@bhousel thanks for your insight. I do not consider the best flag well documented and as such defined. But I agree with your definition and will try to find the time to suggest upstream changes to improve the docs and fix the wrong usage. I now remember that I ran into the same issue 2018 but that staled in its research state https://github.com/osmlab/editor-layer-index/issues/538.
Note to self: This https://github.com/osmlab/editor-layer-index/blob/gh-pages/schema.json#L109-L112 will also have to change to clarify the intended usage of "best" as "local override to the global Bing default".
I will close this issue here.


Issue when creating Package due to Object allowed range (Oct Preview)

Hi,
I am getting the below error when i create a package  for all objects in my custom range which starts from 70097620:

Can you please suggest why this is not possible.
Also i have uploaded our licence which contains permission for this range of objects.
Thanks & Regards
Varun Reddy

we found out how to solve this issue.
Please remove the idrange proeprty in aap.json or change it to your range this issue will not come.
Hope this will help others


SmartRedis Fortran Client Does Not Build with PGI Compilers

Description
Building the serial Fortran client example smartredis_put_get_3D.F90 located in examples/serial/fortran with PGI compilers (nvfortran specifically) version 21.3.0 I get the following error message:
Scanning dependencies of target smartredis_dataset
[ 10%] Building Fortran object CMakeFiles/smartredis_dataset.dir/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/fortran_c_interop.F90.o
[ 20%] Building Fortran object CMakeFiles/smartredis_dataset.dir/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90.o
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   1 severes, 0 fatal for get_meta_scalars_i32
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   2 severes, 0 fatal for get_meta_scalars_i64
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   3 severes, 0 fatal for get_meta_scalars_float
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for get_meta_scalars_double
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for add_meta_scalar_i32
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for add_meta_scalar_i64
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for add_meta_scalar_float
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for add_meta_scalar_double
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
NVFORTRAN-S-0155-IGNORE_TKR may not be specified for meta (/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90)
  0 inform,   0 warnings,   4 severes, 0 fatal for add_meta_string
CMakeFiles/smartredis_dataset.dir/build.make:107: recipe for target 'CMakeFiles/smartredis_dataset.dir/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90.o' failed
make[2]: *** [CMakeFiles/smartredis_dataset.dir/projects/cfdml_aesp/ML/smartredis-0.1.1/src/fortran/dataset.F90.o] Error 2
CMakeFiles/Makefile2:96: recipe for target 'CMakeFiles/smartredis_dataset.dir/all' failed
make[1]: *** [CMakeFiles/smartredis_dataset.dir/all] Error 2
Makefile:102: recipe for target 'all' failed
make: *** [all] Error 2

Please note that the specific branch of SmartRedis was cloned with the following command git clone https://github.com/CrayLabs/SmartRedis.git --depth=1 --branch v0.1.1 smartredis-0.1.1. The CMakeLists.txt file was used to build the example code, with the only modification being that CMAKE_FC_COMPILER is set to the desired nvfortran compiler path.
How to reproduce
The error is produced on the ThetaGPU machine at ALCF. From a clean environment obtained executing module purge, CMake version 3.19.5 and the NVIDIA HPC SDK version 21.3 are loaded. The CmakeLists.txt file available in the example directory  (ensuring nvfortran is used) is then used to configure and build the smartredis_put_get_3D.F90 example code, producing the compiler error pasted above. No PrgEnv is loaded since none is available on ThetaGPU.
Expected behavior
The expected behavior is for the Fortran client to build correctly.
System

OS: Ubuntu 18.04.5 LTS
Commit/version of library: I am using the following SmartRedis commit 95ca568474db37d8a027b1def7e87672a592416b

Thanks @rickybalin. We are looking into this. As stated, we haven't specifically used the Nvidia Fortran compiler before, but we have compiled with PGI I believe. I will post here as soon as we know more.

I was able to reproduce the error.
As for using the Nvidia toolchain:

It seems as though some of our dependencies (Redis++ and Hiredis) also utilize GNU specific flags which is the first problem.
we don't regularly test on the nvidia compilers so users should expect some turbulence when trying to use them

For the GNU MPI issue

The base GNU on theta-gpu doesn't have gfortran so we need to use the GNU 10 toolchain on theta-gpu. however, this toolchain was installed through spack and the openMPI built on theta-gpu seems to not be compatible.
we get the following error when we try this [OMPI users] Fatal Error: Cannot read module file 'mpi.mod' opened at (1), because it was created by a different version of GNU Fortran

So next things to try:

use the mpicc mpixx and mpifort for the compilation of all deps and the application
if that doesn't work, try a separate install of either gfortran for GNU 7 or openmpi for GNU 10.

When @mellis13 is back, he will likely take over this investigation.

I was playing around with this and compiling the Fortran client directly (it technically doesn't need any dependencies) on my own Ubuntu machine with nvfortran 21.3.0. I'm actually thinking this might be a compiler bug. That seems like a little bit of a copout, but there's two reasons why it might be the case:

If I comment out all the routines except for the get_meta_scalars and add_meta_scalar the code compiles just fine
We never use the IGNORE_TKR directive (which I'm pretty sure neither the Intel or GNU compilers support)

I'll spend a little more time in the coming days trying to see if we can work around this (and before pointing fingers too much). It could very well be that there's a coding mistake in one of the other routines that's causing the compiler to signal (incorrectly) in these routines.

IGNORE_TKR was an invention of the Cray compiler that predated the TYPE(*),DIMENSION(..) declaration in (what is now) standard Fortran.  The sources should probably be "modernized".  (Although nvfortran 21.3 falls pretty far short of conforming to the published Fortran standard.)

NVIDIA relatively recently announced that their F18 implementation was accepted by LLVM. There's no date that I could find when it would make it into NVHPC SDK, but the chatter on the forums indicates that they will in the future.


docs: Updated small error in FSMState documentation

I noticed the _on_update method signature was wrong in the docs.  It caused me a bit of trouble.  Please review

Thank you for contributing!


Node not taking incoming conections

My node works and set up 8 outgoing connections, but does not accept incoming connections. It does not show either up on the map here: https://bitnodes.21.co/ or pass a checkout. I have opened port 8333 in the router, and even tried to completely shut down the firewall on the router. Is there any more ports that have to be opened? Or does something have to change in the setup?
pi@fullnode ~ $ bitcoin-cli getinfo
{
"version" : 110200,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 389716,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "<IP_ADDRESS>:9050",
"difficulty" :<PHONE_NUMBER>6.32380676,
"testnet" : false,
"keypoololdest" :<PHONE_NUMBER>,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00005000,
"errors" : ""
}
pi@fullnode ~ $
The node has the local ip of <IP_ADDRESS> - and the port is opened pointing to this

NAT setup on my router

It seems we solved it by adding these lines to bitcoin.conf and rebooting
server=1
daemon=1
Thanks to Peter Frank


Create infra guidelines

/cc @ankitm123 since you've gone through AWS application, it would be great if you could provide feedback about what is documented here.

Merging this so we have the initial information available which can be updated and refined as needed.


Complete content - all images, QA, etc.

[x] Date and dimensions in connect images. CM to standardise.
[x] Missing images and double-check filenames and images match (CM)
[x] Explore > Hind Mezaina - seems to be missing curator-image

From Clint:

I have updated the final images (the ones we have anyway) and put them in the 'New' folder as I did last time. I have also added a picture for Hind (not approved by her but she has been unresponsive so...) to the folder with all the connect images and portraits. It is called 1_Portrait_Hind_Mezaina_8612_square which I have reflected on the json. I added artist countries to the artwork captions of connect so all the captions now match.

I've uploaded the latest images and json and created a new version of the app. Closing this issue.


missing class guid

There seems to be a number of missing ClassGuid for example
{1ed2bbf9-11f0-4084-b21f-ad83a8e6dcdc}
{4d36e966-e325-11ce-bfc1-08002be10318}
{533c5b84-ec70-11d2-9505-00c04f79deaf}
{62f9c741-b25a-46ce-b54c-9bccce08b6f2}
{c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
When will these be updated on this page?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c231a8b4-24a8-c339-8660-52a2b9d28226
Version Independent ID: 093b0d00-46ae-b685-760c-c04e10b27595
Content: System-Defined Device Setup Classes Available to Vendors - Windows drivers
Content Source: windows-driver-docs-pr/install/system-defined-device-setup-classes-available-to-vendors.md
Product: windows-hardware
Technology: install
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Hi @Garthjag, thanks for the feedback.
The second and third GUIDs that you list (4d... and 53...) are both listed on https://docs.microsoft.com/en-us/windows-hardware/drivers/install/system-defined-device-setup-classes-reserved-for-system-use, which is a page that forms a pair with the page you found, https://docs.microsoft.com/en-us/windows-hardware/drivers/install/system-defined-device-setup-classes-available-to-vendors, to list the Class and ClassGuid values.
I am looking into the other 3.

It turns out the other 3 should all be on the "reserved for system use" page as well.  I will make that change sometime soon.

Just pushed the doc update, should be on the live site soon.  Thanks again for the report!


Install CEMiTool

This PR installs CEMiTool.
Installation sequence for tool-installers

[x] Test using @galaxybot test this
[x] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

@galaxybot test this

@galaxybot deploy this


Intellisense now displays connector optional parameters as record

Issue https://github.com/microsoft/Power-Fx/issues/2045.
This fix addresses the intellisense problem only. Other mentioned issues are now individual filed issues.

✅ No public API change.

✅ No public API change.

✅ No public API change.


Timezome change from 12h to 24h

On the Dashboard i want to Change the time and Date Format to 24h i changed the Language in Webmin configuration from utf8 en_us to en_gb utf8 but nothing Happens date and Time format are displayed 12h am pm format

Date and time for System Information page are controlled using theme's settings. Try settings LLLL for long format.

I think this is due to the fact that in authentic-init.pm the get_current_user_language sub subtracts the "_gb" part of the language name (as only two characters from the beginning is allowed the html data-language tag gets only "en". Which is interpreted as US time format by the momentjs.
A logic may needed to be introduced that checks whether the language is 2 or 5 character long (i.e. "en" or "en_GB") or if the string before the ".utf-8" is returned by get_current_user_language.
sub get_current_user_language
{
return
substr(
($gconfig{ 'lang' . '' . $base_remote_user } ? $gconfig{ 'lang' . '' . $base_remote_user } :
$gconfig{'lang'}
),
0, 2);
}
I am not very good at Perl but somthing like a regex check could work. The below is probably not a very elegant way but it works :)
$lang_string = ($gconfig{ 'lang' . '' . $base_remote_user } ? $gconfig{ 'lang' . '' . $base_remote_user } :
$gconfig{'lang'});
$lang_string =~ s/..*//;
return $lang_string

Sounds very good but i am Not The best in edit files like this where should i paste this code

Sorry @qooob LLLL is Standard Setting ist does Not work

I will push the commit tomorrow morning, so you could test it. It should just work. No need to edit theme's settings. After installing tomorrow's patch it will just show up correctly.

Unsent from yesterday:
momentjs accepts full string in locale function, thus en-gb will work just fine.
Thank you for pointing this out.
I'm adding this for 19.01 release that is scheduled for tomorrow. :wink:

Give it a try, please.


Update build.rs to eliminate vergen and gitoxide dependencies

Description
This PR updates the build.rs build script for the node to remove the vergen and gitoxide dependencies from the node, while retaining the build scripts behavior of including the current git revision short hash in the version info at compile time.

bors r+

bors r+


affected/package:  x/term

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

$ go version
go version go1.20.8 linux/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/kedar/.cache/go-build"
GOENV="/home/kedar/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/kedar/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/kedar/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.8"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/kedar/go/src/goted/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2743902907=/tmp/go-build -gno-record-gcc-switches"

What did you do?
using the golang.org/x/term package trying to get the terminal into raw mode and it isn't exiting the raw mode even after the program completes execution
oldState, err := term.MakeRaw(int(os.Stdin.Fd()))
if err != nil {
    panic(err)
}

defer term.Restore(int(os.Stdin.Fd()), oldState)

What did you expect to see?
The terminal exiting raw mode and inputs going back to echoing
What did you see instead?
The terminal stayed in raw mode

Error is not with the package but something to do with the defer it seems


conda-forge

Description
meta.yaml for conda-forge
Status

[ ] Ready to go

Codecov Report

Merging #66 (401929b) into main (049e260) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files


Host request timed out

When I sent command request it returns correct json response but when I try to send host or to configure IPMI connector it returns timeout error.

http://<IP_ADDRESS>:9595/command?params=-I lanplus -H <IP_ADDRESS> -U Administrator -P 95XGFGBC bmc info

{"success":true,"output":"Device ID                 : 17\nDevice Revision           : 1\nFirmware Revision         : 2.32\nIPMI Version              : 2.0\nManufacturer ID           : 11\nManufacturer Name         : Hewlett-Packard\nProduct ID                : 8192 (0x2000)\nProduct Name              : Unknown (0x2000)\nDevice Available          : yes\nProvides Device SDRs      : yes\nAdditional Device Support :\n    Sensor Device\n    SDR Repository Device\n    SEL Device\n    FRU Inventory Device\n"}

http://<IP_ADDRESS>:9595/?host=<IP_ADDRESS>&port=623&user=Administrator&password=95XGFGBC

2023/12/31 17:32:24 [error] 206#206: *34 upstream timed out (110: Operation timed out) while reading response header from upstream, client: <IP_ADDRESS>, server: _, request: "GET /?host=<IP_ADDRESS>&port=623&user=Administrator&password=95XGQTGC HTTP/1.1", upstream: "fastcgi://<IP_ADDRESS>:9000", host: "<IP_ADDRESS>:9595"

Please get the latest ipmi integration and addon and let me know if they work for you.

Thank you, it was fixed in v1.2.5 . I tried it yesterday :)


Add support for  tags

In my specific case I need  tag support which will be added using the attached implementation.
Thanks for providing this library! ;-)

Hi, can you add some test cases for this patch? Thanks :)

Have implemented this :) thank you for the PR!

Unfortunately I was very busy the last weeks, I really forgot this issue. Thanks for implementing this! ;-)


"!id_map.has(p_rid.get_data())" error with YSort populating during runtime

Godot version: 03bd4d2
OS/device including version: Ubuntu
Issue description:
Creating and adding Node2Ds to a YSort after setting up the tree, will result in a spam in the debugger with the following error:
  <C Source>     ./core/rid.h:164 @ getornull()
  <Stack Trace>  Player.gd:31 @ _physics_process()

(The last line is just my debug script)
The following image should illustrate my issue/concern:

Steps to reproduce:
Create a new scene with YSort as the base node.
Include add_child(Node2D.new()) in any function which is called after the tree is initialized (e.g. not ready)
Look at the errors in the debugger.

Will look into it during the weekend (or a bit after it), sorry for the delay so far.


Added ROC Leeuwenborgh

Added the Dutch ROC Leeuwenborgh
URL: http://www.leeuwenborgh.nl/

@Finley7 Could you please give us a link to an IT-related long-term (> 1year) course which your institution offers?

Yes, its an 3-year education called application & media development => http://www.leeuwenborgh.nl/Opleidingen/paginas/Tonen.aspx?oid=243&opleiding=Applicatie- en Mediaontwikkelaar (4) 3-jarig

@Finley7 Thank you for the clarification. Pull request merged.


v1.15 Backports 2024-07-08

[x] #30580 (@Pionerd)
[x] #33514 (@aanm)
[x] #33509 (@julianwiedmann)
[x] #33420 (@gandro) :warning: resolved conflicts
[x] #33472 (@jasonaliyetti) :warning: resolved conflicts
[x] #33512 (@jasonaliyetti) :warning: resolved conflicts
[x] #33551 (@julianwiedmann)
[x] #33569 (@chaunceyjiang)
[x] #33624 (@julianwiedmann) :warning: resolved conflicts
[x] #33599 (@rgo3)

PRs skipped due to conflicts:

#33449 (@jrajahalme)
#33511 (@skmatti)

dropped the PR due to some build failures

Once this PR is merged, a GitHub action will update the labels of these PRs:
 30580 33514 33509 33420 33472 33512 33551 33569 33624 33599

/test-backport-1.15

@jibi If possible, can you merge https://github.com/cilium/cilium/pull/33663 into this?

@jibi If possible, can you merge #33663 into this?

@skmatti I think it should be fine to merge your PR separately :+1:

(rebased and fixed the backport note on all commit messages)

/test-backport-1.15

Great contribution! I've been manually editing the dashboards to make them work before. 🏆


Automated release not working correctly

Describe the bug
When we try to release a new version, we use the lerna release command. Up to the last step - the release of NPM.js - everything runs correctly, but the release of the Angular Package fails without giving a helpful error message.
To Reproduce
⚠  Caution! When executing the lerna publish command, the core and the react packet will be irreversibly published.
Steps to reproduce the behavior:

Clone the project
Install dependencies
Run lerna publish
See the error on angular package

Expected behavior
The angular package to be successfully released as well.
Your Environment

Software
Version

@inovex.de/elements
1.0.2

I've just tested it again and here is a more detailed description of what's happening and what's the error:

Run lerna publish --conventional-commits

--conventional-commits in order to follow the semantic versioning

The packages are build and tested
Packages elements and elements-react publish successfully
Error on package elements-angular

lerna http fetch PUT 403<EMAIL_ADDRESS>849ms
lerna ERR! E403 You cannot publish over the previously published versions: 1.0.2.

The reason is, that the build inside the elements-angular/dist is outdated with the old package.json where the old version is stated. In this case, the version field in package.json was 1.0.2 (the current version) but should be 1.1.0. Even though the version is bumped correctly as you can see in the following output:
➜ lerna publish --conventional-commits
lerna notice cli v3.22.0
lerna info current version 1.0.2
lerna info Looking for changed packages since v1.0.2
lerna info getChangelogConfig Successfully resolved preset "conventional-changelog-angular"

Changes:
 - @inovex.de/elements-angular-builder: 1.0.2 => 1.1.0 (private)
 - @inovex.de/elements-react: 1.0.2 => 1.1.0
 - @inovex.de/elements: 1.0.2 => 1.1.0
 - @inovex.de/elements-storybook: 1.0.2 => 1.1.0 (private)
 - @inovex.de/elements-angular: 1.0.2 => 1.1.0

To fix this, I ran yarn build inside of elements-angular and published the package by hand with npm publish dist/.

So in order to fix this issue, we have to find the reason why the build files are outdated even though the bumping takes place before the build command.

Closed with #168


Output the name of vnet

Output the name of vnet so that it can be used elsewhere, for example, in creating vnet peering.

FWIW you can obtain this value by using the existing vnet output.

Ah! Correct.
vnet.name would do. Will cancel this PR.


[WIP] fix(expand): accept scheduler parameter

@kwonoj @blesh could you guys take a look if I'm going in the right direction here? ;)

Just updated this PR addressing the previous comments.
Still missing some test cases using a custom scheduler. Suggestion are very welcome. ;)

Merged with 79e9084. Thanks @luisgabriel!


Refresh Grid after component size changes

I have an application that starts off with minimalized items. When the user clicks on a particular item it is re-rendered and the width and height changes. However, when the small component is replaced by the larger, the other un-clicked smaller components stack over the larger component as if it does not recognize that it is present. Only when I change the browser size does it re-render the grid correctly taking the larger component into exception.
<StackGrid                     columnWidth={350}                     duration={480}                     gutterWidth={5}                     gutterHeight={5}                     easing={easings.quartOut}                     appear={flip.appear}                     appeared={flip.appeared}                     enter={flip.enter}                     entered={flip.entered}                     leaved={flip.leaved}                     monitorImagesLoaded={true}                 >                     {this.groupLoop(groups, groupSelected)}                 </StackGrid>
With in groupLoop, its decides if the component is small or large, the large component is rendered by calling another component whereas the small was are not. I can give more details if needed.

Hi @derwydd, Thanks for Issues :smiley:
I think it is probably the same issue as # 19.

As a solution there is a way to detect the size change of each item of the grid, but it will greatly degrade performance.
Instead, I'm considering an API to rerender the grid manually:
/**
 * It calls the API of the StackGrid instance
 * when the height of the grid item changes.
 */
class YourComponent extends React.Component {
  /**
   * It simulates when the height of the grid item changes.
   */
  something() {
    this.node.updateLayout();
  }

  // ...

  render() {
    return (
      <StackGrid
        onInitialized={node => this.node = node}
      >
        {/* Grid items */}
      </StackGrid>
    );
  }
}

It is an idea to handle item clicks and run updateLayout().
What do you think of this idea?

This would be great. The ability to call a function with in an event change make best sense. What would be the time frame for this? We  would love to use this library in a production App.

@derwydd , Thanks for quick response !

What would be the time frame for this?

The promise is difficult, but I think we can release it this week.

We would love to use this library in a production App.

Thanks, very encouraging for me... :wink:

Hi @derwydd.
Released version 0.3.0 which supports manual layout update :tada:
Please check when you have time.
Reference

Live Demo (Source Code)
How to manually update layout ?

Note: The onInitialized used in the proposal is renamed to gridRef.

We were able to implement, but it seems that it does not work in every GridItem height. We have some items/panels that are about 900px height and the height is dynamic and not set. Should we be setting the height? Also is there a way for a particular item to grow in width that is greater than the column width?

The UI that we are using Material, I'm not sure if that is a factor
Can I send you pictures via email to demonstrate what is happening?

Hi @derwydd, Thank you for confirmation.

Also is there a way for a particular item to grow in width that is greater than the column width?

No, unfortunately react-stack-grid does not support it.

Can I send you pictures via email to demonstrate what is happening?

Thanks for your cooperation. Instead of e-mail, it is helpful to share the minimum reproducible code.
A repository like react-stack-grid-issue-XXX is ideal.


Cant pay an invoice created with LND on mainnet

If I try to scan the code or paste it manually it shows invalid data
I generated the invoice via
lnd addinvoice 120
LN v0.11.0-beta
Invoice
lnbc1200n1p054grypp5vhjgmnjfuzn2cwcxm8wnhwj5hk0nly87q374y5m90e36nvludn2qdqqcqzpgsp5se7ve8pym9h06uvp638ehg88edn70qfk6pw3a9j0h7jq3mt3gyhq9qy9qsqsmdrqux8f5lrs2myjj

Hi, could you add the invoice to the issue?

Sure!
lnbc1200n1p054grypp5vhjgmnjfuzn2cwcxm8wnhwj5hk0nly87q374y5m90e36nvludn2qdqqcqzpgsp5se7ve8pym9h06uvp638ehg88edn70qfk6pw3a9j0h7jq3mt3gyhq9qy9qsqsmdrqux8f5lrs2myjj

I found the issue.. my transmission method was truncating the invoice .. sorry for the inconvenience


Mono Install Package/Nuget throws Microsoft.NETFramework.ReferenceAssemblies error

Godot version:
Godot Engine v3.2.2.stable.mono.official
OS/device including version:

Building on Windows 10 64 bit with Visual Studio 2019 installed.
Issue description:

Each time when running the command Install-Package in Visual Studio 2019 to get packages like Newtonsoft.Json it throws the following error consistently:
Install-Package : NU1101: Unable to find package Microsoft.NETFramework.ReferenceAssemblies. No packages exist with this id in source(s): Local mono packages, Microsoft Visual Studio Offline Packages, Project Packages
And this error prevents the installation of the C# packages. I can load in dll files but unfortunately far from all C# packages have dll files available to download, many require a Install-Package command installation.
Steps to reproduce:
Create a new Godot mono project, add a C# script, build it once. Open up the .sln with Visual Studio 2019 and use the NuGet package manager to install whatever package.

This may or may not also be related to #40805 as they are both missing assemblies. It is just a guess.

Can you try with 3.2.3 RC 3?

Thanks for the response akien, I just tried it with 3.2.3 RC 3! I now get this error message in the mono console of the Godot editor when attempting to build and launch the project from the Godot editor:
error NU1101: Unable to find package Microsoft.NETFramework.ReferenceAssemblies. No packages exist with this id in source(s): Local mono packages, Microsoft Visual Studio Offline Packages, Project Packages [C:\Users\Classy\Desktop\rc3testproj\Rc 3 Testproj.sln]
Mind you this didn't happen in the Godot mono console before, only in visual studio 2019 when attempting to install packages.
Also, a new interesting thing happens when opening this newly RC3 created project with Visual Studio 2019, I got an incompatibility message stating that "The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?LinkID=299083&projecttype=8F3E2DF0-C35C-4265-82FC-BEA011F4A7ED"
With a then generated by visual studio upgrade log stating the same.

And visual studio 2019 displays the newly created project in the following way after the incompatibility message:

I am far from an experienced C# programmer, any help with this is appreciated!
In 3.2.2stable I could still build and launch the project just fine and that error only occurred when attempting to install packages.

Note that starting with 3.2.3 (including the RC3), there's an addin you can use for Visual Studio support: https://github.com/godotengine/godot-csharp-visualstudio
Maybe that's what the error is referring to? I'm not so familiar with the C# development workflow either, so I'm not sure.
In any case, it's a bit confusing so usability-wise there are likely necessary improvements.

Unfortunately in order to extend Visual Studio to add functionality for Godot projects we need to the project to have a custom project type guid the extension can handle. At the same time if there's no extension that recognizes that project type guid then Visual Studio can't open the project at all.
It's very annoying because both MonoDevelop/VSMac and Rider allow the extension to use its own logic to detect whether to handle the project or not. But it's what it is, so starting with 3.2.3 in order to open the solution with VS you will need to install the extension: https://github.com/godotengine/godot-csharp-visualstudio/releases/tag/v1.1.1 (it will be available in the marketplace soon as well)

Great, I can now open new Godot 3.2.3 RC3 projects with Visual Studio! I just can no longer build them, not from the Godot editor either. I get the following error with RC3: C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.csproj(0,0): error NU1101: Unable to find package Microsoft.NETFramework.ReferenceAssemblies. No packages exist with this id in source(s): Local mono packages, Microsoft Visual Studio Offline Packages, Project Packages [C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.sln]

I use a lot of NuGet packages with 3.1
The way I get it working is like this:

Create a console project in visual studio (.net framework)
Add the NuGet references
Manually copy the lines from the .csproj and packages files
msbuild takes care of fetching the nuget packages

Not a fix, but maybe it can help you out for now.

@timothyparez Thank you, this works!!
I do hope that for Godot 3.2.3 this missing Microsoft.NETFramework.ReferenceAssemblies error gets resolved because otherwise, I won't be able to work with C# at all anymore as no project will build or run then! But for now, in 3.2.2 I can still build & run Godot mono games/projects and install C# packages using the aforementioned method.

@Classy11 Try out 3.2.3rc3 if you want to know this.

@Calinou I have tried it out with 3.2.3RC3 and this is what I experienced: the missing Microsoft.NETFramework.ReferenceAssemblies error becomes critical and I can no longer run and build Godot mono projects. Whereas in 3.2.2 this error only occurs when attempting to install packages with Nuget but building and running Godot mono projects still work fine.

Can you enable the option Mono > Builds > Print Build Output, try to build again and paste the full Godot command line output here?

Project "Rc 3 Proj.sln" (Restore target(s)):
	Message: Building solution configuration "Debug|Any CPU".
	Project "Rc 3 Proj.csproj" (_IsProjectRestoreSupported target(s)):
	Done building project "Rc 3 Proj.csproj".
	NuGetMessageTask: Determining projects to restore...
	Project "Rc 3 Proj.csproj" (_GenerateRestoreProjectPathWalk target(s)):
	Done building project "Rc 3 Proj.csproj".
	Project "Rc 3 Proj.csproj" (_IsProjectRestoreSupported target(s)):
	Done building project "Rc 3 Proj.csproj".
	Project "Rc 3 Proj.csproj" (_GenerateRestoreGraphProjectEntry target(s)):
	Done building project "Rc 3 Proj.csproj".
	Project "Rc 3 Proj.csproj" (_GenerateProjectRestoreGraph target(s)):
	Done building project "Rc 3 Proj.csproj".
	RestoreTask: Restoring packages for C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.csproj...
	C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.csproj(0,0): error NU1101: Unable to find package Microsoft.NETFramework.ReferenceAssemblies. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, Project Packages [C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.sln]
	RestoreTask: Committing restore...
	RestoreTask: Writing assets file to disk. Path: C:\Users\Classy\Desktop\rc3proj\.mono\temp\obj\project.assets.json
	RestoreTask: Failed to restore C:\Users\Classy\Desktop\rc3proj\Rc 3 Proj.csproj (in 250 ms).
	RestoreTask:
	RestoreTask: NuGet Config files used:
	RestoreTask:     C:\Users\Classy\AppData\Roaming\NuGet\NuGet.Config
	RestoreTask:     C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config
	RestoreTask:     C:\Program Files (x86)\NuGet\Config\Xamarin.Offline.config
	RestoreTask:
	RestoreTask: Feeds used:
	RestoreTask:     C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
	RestoreTask:     C:\Users\Classy\Documents\Godot Projects\spaceServer\nugetPackages
Done building project "Rc 3 Proj.sln" -- FAILED.

This is the biggest error trace that I can find, I get it when I press "View Log" in the Godot "Mono" warnings/error console. And in this case turning on Mono > Builds > Print Build Output does not change the error and build outputs I get and the regular Godot output window remains empty.

Issue resolved! In Visual Studio with the RC3 project open I went to References > Manage Nuget Packages, and then looked for Microsoft.NETFramework.ReferenceAssemblies and just uninstalled it. Now the project can build and the hello world print from the C# script works. I did not manually add or install Microsoft.NETFramework.ReferenceAssemblies, it just gets there upon creation. I assume that this is fine to remove and won't break things. At least I haven't seen that it breaks stuff right now.

#41408 may fix this issue.

Assuming that #41408 fixed it.
Please comment if you can still reproduce the issue with 3.2.3 or any later release.


allow atomic on external db

Coverage increased (+0.003%) to 90.329% when pulling b28f550c37f4baa4782555b46e9f2a32230bc3c4 on issue#652 into 00fe611b86d23523710da2eecd1470861968b224 on master.


[Bug]: Not allowed to add Outlook Service

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Ferdi Version
5.6.5
What operating system are you using?
Windows
Server
Ferdi
Operating System Version
Windows 11 Pro version 21H2
What arch are you using?
x64
Last Known working version of Ferdi
No response
Git SHA and/or build date
No response
Steps to reproduce

Go to "Add New Srvice"
Search for "Outlook"
Click on "Outlook" (Not "Office 365 - Outlook")

and then you won't be able to add it, nothing it's going to happen once you click on "Outlook"
Expected Behavior
Once I select "Outlook" to be added I expected that that service be added
Actual Behavior
Not adding Outlook once it's selected
Screenshots
No response
Debug information
No response
Testcase Gist URL
No response
Additional Information
No response

Related to https://github.com/getferdi/recipes/issues/612, https://github.com/getferdi/recipes/issues/143, https://github.com/getferdi/ferdi/issues/2152.
Fixed via https://github.com/getferdi/server/commit/e4a7fcbde65f399bc09065890cad750e40d1568e.
@all-contributors please add @crscaballero for bug


Title

Describe the bug
When using leptos_meta's <Title>, the <title> tag gets correctly set from server, but becomes empty when navigating on the client side.
Leptos Dependencies
axum = { version = "1.7", features = ["macros"], optional = true }
console_error_panic_hook = "0.1"
derive_more = { version = "0.99.17", default-features = false, features = [
    "deref",
] }
http = "1"
icondata = "0.3.1"
icondata_core = "0.1"
indoc = "2.0.5"
leptos = { git = "https://github.com/leptos-rs/leptos", branch = "leptos_0.7", features = [
    "nightly",
] }
leptos_axum = { git = "https://github.com/leptos-rs/leptos", branch = "leptos_0.7", optional = true }
leptos_meta = { git = "https://github.com/leptos-rs/leptos", branch = "leptos_0.7" }
leptos_router = { git = "https://github.com/leptos-rs/leptos", branch = "leptos_0.7", features = [
    "nightly",
] }
leptos_router_macro = { git = "https://github.com/leptos-rs/leptos", branch = "leptos_0.7" }
serde = { version = "1.0", features = ["derive"] }
surrealdb = { version = "1.5.1", features = ["kv-speedb"], optional = true }
thiserror = "1"
tokio = { version = "1", features = [
    "macros",
    "rt-multi-thread",
], optional = true }
tracing = { version = "0.1", optional = true }
tower = { version = "0.4", optional = true }
tower-http = { version = "0.5", features = ["fs"], optional = true }
uuid = "1.6.1"
wasm-bindgen = "=0.2.92"

To Reproduce
Use <Title formatter=|text| format!("{text} - My website")/> in the main component, and update it in any page using <Title text="Page"/>. Load any page from server: get correct <title> (Page - My website). Navigate to any page: <title> is empty.
Expected behavior
<title> tag should be set whether loading from the server or navigating on the client.
Screenshots
None
Additional context
I'm tracking the leptos_0.7 branch, which is now at 81e7cd83293f809560e5545ef0398eacfaaf0b74.

I confirm that b814c5a solves this. Thanks, @gbj.


Error: Argument "data" is not a valid Document. Cannot use "undefined" as a Firestore value (found in field user.userRef).

Expected behavior
Make an normal import of the TimeStamp type.
Actual behavior
When trying to import a export made on 0.10.4 I get this error:
Error: Argument "data" is not a valid Document. Cannot use "undefined" as a Firestore value (found in field user.userRef).
Error: Argument "data" is not a valid Document. Cannot use "undefined" as a Firestore value (found in field user.userRef).
at Validator.(anonymous function).values [as isDocument] (C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\node_modules\firebase-admin\node_modules@google-cloud\firestore\build\src\validate.js:92:27)
at WriteBatch.set (C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\node_modules\firebase-admin\node_modules@google-cloud\firestore\build\src\write-batch.js:225:25)
at C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\dist\lib\import.js:66:19
at Array.map ()
at C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\dist\lib\import.js:55:22
at Array.map ()
at setDocuments (C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\dist\lib\import.js:53:32)
at Object.importData [as default] (C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\dist\lib\import.js:27:43)
at C:\Users\Pc\AppData\Roaming\npm\node_modules\node-firestore-import-export\dist\bin\firestore-import.js:96:28
at
PD: The field userRef that is mentioned in the error is of type reference, like this "userRef: users/oRVksmPWOsXPJNFrmbGP359t6J03"
Steps to reproduce the behavior
Make an export of the DB and then try to import it.

this is the part of the JSON that is referenced in the error:
"1XgUbUDfwue3FMpZLuqy": {
"service": 5,
"user": {
"userRef": {
"datatype": "documentReference",
"value": "users/WQuGJoMVf6d9HffF04g53G0mWif2"
},
"displayName": "Noel Farías"
},
"food": 5,
"speed": 5,
"collections": {}
},
@jloosli

+1

@jloosli I still have the exact same error of this issue on version 0.12.0

@pollo17385 Looking closer at https://github.com/jloosli/node-firestore-import-export/issues/36#issuecomment-441460805 it shows
"userRef": {
"datatype": "documentReference",
"value": "users/WQuGJoMVf6d9HffF04g53G0mWif2"
}

but datatype should have exported as datatype, like below:
"userRef": {
"__datatype__": "documentReference",
"value": "users/WQuGJoMVf6d9HffF04g53G0mWif2"
}

Is that just a copy/paste issue, or did the export not format it correctly?

@pollo17385 I'm so dumb...I published this without building it first. Update to the latest and try it and let me know if it works for you.

Jared, this things happen.
Now its working flawlessly. Thanks for your work and your time!!
Greetings Gonzalo.

Glad to hear it's working!


panicked at 'mismatched kinds in substitution'

Background
I use the VSCode rust-analyzer extension with version v0.3.992 Pre-Release. I tried switching to release version, this didn't fix my problem. You can find the code I am currently working with here: https://github.com/Felix-Droop/brute1000
I already found a similar and closed issue here: https://github.com/rust-analyzer/rust-analyzer/issues/11717
But I think my version is recent enough such that this should not be the exact same problem (not completely sure though).
rust-analyzer version: rust-analyzer version: bc08b8eff 2022-03-28 nightly
rustc version: rustc 1.59.0 (9d1b2106e 2022-02-23)
relevant settings: Should all be default^^
My problem
I get error messages from VSCode for some editing actions I do. The messages say the following:
Request textDocument/semanticTokens/full/delta failed.
Request textDocument/hover failed.
Request textDocument/signatureHelp failed.
One example of how I get the error is removing the comments here (inside VSCode using Ctrl+#): https://github.com/Felix-Droop/brute1000/blob/master/src/main.rs#L25-L35
As expected by the error messages, I get no code coloring, no hover help, etc. (for this block; for other parts of the code it works). In the following I will post the one examplary output from the VSCode Output field for the error messages:
Output
[Error - 15:24:06] Request textDocument/semanticTokens/full/delta failed.
  Message: server panicked: mismatched kinds in substitution
  Code: -32603
Panic context:
>
version: bc08b8eff 2022-03-28 nightly
request: textDocument/codeAction CodeActionParams {
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/.../brute1000/src/main.rs",
            query: None,
            fragment: None,
        },
    },
    range: Range {
        start: Position {
            line: 24,
            character: 0,
        },
        end: Position {
            line: 34,
            character: 5,
        },
    },
    context: CodeActionContext {
        diagnostics: [],
        only: None,
    },
    work_done_progress_params: WorkDoneProgressParams {
        work_done_token: None,
    },
    partial_result_params: PartialResultParams {
        partial_result_token: None,
    },
}

thread '<unnamed>' panicked at 'mismatched kinds in substitution', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\chalk-ir-0.81.0\src\fold\subst.rs:109:22
stack backtrace:
   0: std::panicking::begin_panic
   1: <chalk_ir::fold::subst::Subst<I> as chalk_ir::fold::Folder<I>>::fold_free_var_const
   2: <chalk_ir::Const<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   3: <chalk_ir::Ty<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   4: chalk_ir::_::<impl chalk_ir::fold::Fold<I> for chalk_ir::WhereClause<I>>::fold_with
   5: chalk_ir::fold::binder_impls::<impl chalk_ir::fold::Fold<I> for chalk_ir::Binders<T>>::fold_with
   6: chalk_ir::Binders<T>::substitute
   7: chalk_solve::clauses::builder::ClauseBuilder<I>::push_binders
   8: <chalk_solve::rust_ir::OpaqueTyDatum<I> as chalk_solve::clauses::program_clauses::ToProgramClauses<I>>::to_program_clauses
   9: chalk_solve::clauses::program_clauses_that_could_match
  10: chalk_recursive::solve::SolveIteration::solve_iteration
  11: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
  12: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_root_goal
  13: <hir_ty::db::TraitSolveQueryQuery as salsa::plumbing::QueryFunction>::execute
  14: salsa::runtime::Runtime::execute_query_implementation
  15: salsa::derived::slot::Slot<Q,MP>::read
  16: salsa::derived::slot::Slot<Q,MP>::read
  17: salsa::QueryTable<Q>::get
  18: <DB as hir_ty::db::HirDatabase>::trait_solve_query
  19: hir_ty::db::trait_solve_wait
  20: <DB as hir_ty::db::HirDatabase>::trait_solve
  21: hir_ty::infer::unify::InferenceTable::register_obligation_in_env
  22: hir_ty::infer::InferenceContext::insert_type_vars_shallow
  23: chalk_solve::display::state::WriterState<I,DB,P>::new
  24: chalk_solve::display::state::WriterState<I,DB,P>::new
  25: hir_def::intern::Interned<T>::new
  26: chalk_solve::display::state::WriterState<I,DB,P>::new
  27: chalk_solve::display::state::WriterState<I,DB,P>::new
  28: hir_ty::infer::infer_query
  29: salsa::runtime::Runtime::execute_query_implementation
  30: salsa::derived::slot::Slot<Q,MP>::read
  31: salsa::derived::slot::Slot<Q,MP>::read
  32: salsa::QueryTable<Q>::get
  33: <DB as hir_ty::db::HirDatabase>::infer_query
  34: hir_ty::db::infer_wait
  35: hir::DefWithBody::diagnostics
  36: hir::ModuleDef::diagnostics
  37: hir::Module::diagnostics
  38: ide_diagnostics::diagnostics
  39: std::panicking::try
  40: rust_analyzer::handlers::handle_code_action
  41: std::panicking::try
  42: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Panic context:
>
version: bc08b8eff 2022-03-28 nightly
request: experimental/inlayHints InlayHintsParams {
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/.../brute1000/src/main.rs",
            query: None,
            fragment: None,
        },
    },
    range: Some(
        Range {
            start: Position {
                line: 0,
                character: 0,
            },
            end: Position {
                line: 100,
                character: 1,
            },
        },
    ),
}

thread '<unnamed>' panicked at 'mismatched kinds in substitution', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\chalk-ir-0.81.0\src\fold\subst.rs:109:22
stack backtrace:
   0: std::panicking::begin_panic
   1: <chalk_ir::fold::subst::Subst<I> as chalk_ir::fold::Folder<I>>::fold_free_var_const
   2: <chalk_ir::Const<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   3: <chalk_ir::Ty<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   4: chalk_ir::_::<impl chalk_ir::fold::Fold<I> for chalk_ir::WhereClause<I>>::fold_with
   5: chalk_ir::fold::binder_impls::<impl chalk_ir::fold::Fold<I> for chalk_ir::Binders<T>>::fold_with
   6: chalk_ir::Binders<T>::substitute
   7: chalk_solve::clauses::builder::ClauseBuilder<I>::push_binders
   8: <chalk_solve::rust_ir::OpaqueTyDatum<I> as chalk_solve::clauses::program_clauses::ToProgramClauses<I>>::to_program_clauses
   9: chalk_solve::clauses::program_clauses_that_could_match
  10: chalk_recursive::solve::SolveIteration::solve_iteration
  11: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
  12: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_root_goal
  13: <hir_ty::db::TraitSolveQueryQuery as salsa::plumbing::QueryFunction>::execute
  14: salsa::runtime::Runtime::execute_query_implementation
  15: salsa::derived::slot::Slot<Q,MP>::read
  16: salsa::derived::slot::Slot<Q,MP>::read
  17: salsa::QueryTable<Q>::get
  18: <DB as hir_ty::db::HirDatabase>::trait_solve_query
  19: hir_ty::db::trait_solve_wait
  20: <DB as hir_ty::db::HirDatabase>::trait_solve
  21: hir_ty::infer::unify::InferenceTable::register_obligation_in_env
  22: hir_ty::infer::InferenceContext::insert_type_vars_shallow
  23: chalk_solve::display::state::WriterState<I,DB,P>::new
  24: chalk_solve::display::state::WriterState<I,DB,P>::new
  25: hir_def::intern::Interned<T>::new
  26: chalk_solve::display::state::WriterState<I,DB,P>::new
  27: chalk_solve::display::state::WriterState<I,DB,P>::new
  28: hir_ty::infer::infer_query
  29: salsa::runtime::Runtime::execute_query_implementation
  30: salsa::derived::slot::Slot<Q,MP>::read
  31: salsa::derived::slot::Slot<Q,MP>::read
  32: salsa::QueryTable<Q>::get
  33: <DB as hir_ty::db::HirDatabase>::infer_query
  34: hir_ty::db::infer_wait
  35: hir::source_analyzer::SourceAnalyzer::new_for_body
  36: hir::semantics::SemanticsImpl::analyze_impl
  37: ide::inlay_hints::hints
  38: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
  39: ide::inlay_hints::inlay_hints
  40: std::panicking::try
  41: ide::Analysis::inlay_hints
  42: rust_analyzer::handlers::handle_inlay_hints
  43: std::panicking::try
  44: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Panic context:
>
version: bc08b8eff 2022-03-28 nightly
request: experimental/inlayHints InlayHintsParams {
    text_document: TextDocumentIdentifier {
        uri: Url {
            scheme: "file",
            cannot_be_a_base: false,
            username: "",
            password: None,
            host: None,
            port: None,
            path: "/.../brute1000/src/main.rs",
            query: None,
            fragment: None,
        },
    },
    range: Some(
        Range {
            start: Position {
                line: 0,
                character: 0,
            },
            end: Position {
                line: 61,
                character: 13,
            },
        },
    ),
}

thread '<unnamed>' panicked at 'mismatched kinds in substitution', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\chalk-ir-0.81.0\src\fold\subst.rs:109:22
stack backtrace:
   0: std::panicking::begin_panic
   1: <chalk_ir::fold::subst::Subst<I> as chalk_ir::fold::Folder<I>>::fold_free_var_const
   2: <chalk_ir::Const<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   3: <chalk_ir::Ty<I> as chalk_ir::fold::SuperFold<I>>::super_fold_with
   4: chalk_ir::_::<impl chalk_ir::fold::Fold<I> for chalk_ir::WhereClause<I>>::fold_with
   5: chalk_ir::fold::binder_impls::<impl chalk_ir::fold::Fold<I> for chalk_ir::Binders<T>>::fold_with
   6: chalk_ir::Binders<T>::substitute
   7: chalk_solve::clauses::builder::ClauseBuilder<I>::push_binders
   8: <chalk_solve::rust_ir::OpaqueTyDatum<I> as chalk_solve::clauses::program_clauses::ToProgramClauses<I>>::to_program_clauses
   9: chalk_solve::clauses::program_clauses_that_could_match
  10: chalk_recursive::solve::SolveIteration::solve_iteration
  11: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_goal
  12: chalk_recursive::fixed_point::RecursiveContext<K,V>::solve_root_goal
  13: <hir_ty::db::TraitSolveQueryQuery as salsa::plumbing::QueryFunction>::execute
  14: salsa::runtime::Runtime::execute_query_implementation
  15: salsa::derived::slot::Slot<Q,MP>::read
  16: salsa::derived::slot::Slot<Q,MP>::read
  17: salsa::QueryTable<Q>::get
  18: <DB as hir_ty::db::HirDatabase>::trait_solve_query
  19: hir_ty::db::trait_solve_wait
  20: <DB as hir_ty::db::HirDatabase>::trait_solve
  21: hir_ty::infer::unify::InferenceTable::register_obligation_in_env
  22: hir_ty::infer::InferenceContext::insert_type_vars_shallow
  23: chalk_solve::display::state::WriterState<I,DB,P>::new
  24: chalk_solve::display::state::WriterState<I,DB,P>::new
  25: hir_def::intern::Interned<T>::new
  26: chalk_solve::display::state::WriterState<I,DB,P>::new
  27: chalk_solve::display::state::WriterState<I,DB,P>::new
  28: hir_ty::infer::infer_query
  29: salsa::runtime::Runtime::execute_query_implementation
  30: salsa::derived::slot::Slot<Q,MP>::read
  31: salsa::derived::slot::Slot<Q,MP>::read
  32: salsa::QueryTable<Q>::get
  33: <DB as hir_ty::db::HirDatabase>::infer_query
  34: hir_ty::db::infer_wait
  35: hir::source_analyzer::SourceAnalyzer::new_for_body
  36: hir::semantics::SemanticsImpl::analyze_impl
  37: ide::inlay_hints::hints
  38: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
  39: ide::inlay_hints::inlay_hints
  40: std::panicking::try
  41: ide::Analysis::inlay_hints
  42: rust_analyzer::handlers::handle_inlay_hints
  43: std::panicking::try
  44: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Thanks for the quick fix!
BTW, I think this software is amazing and makes for a great developing experience! It suddenly not working made me realize how much I rely upon it. ^^


CI: move lint job from Azure to GHA

As the title says. Things to ask the reviewer are:

[x] when should the job run? At the moment it's on pushes to maintenance and on PRs to main/maintenance.
[x] is the diff-against flag correct? The documentation for GITHUB_REF is at https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables.

Completes one of the jobs in https://github.com/scipy/scipy/issues/15814#issuecomment-1506516709.

This LGTM too, thanks! If the $GITHUB_REF bit is off (I have no experience with it) then we'll find out soon enough.


HEDA Idea: Primary Business Organization based on role (INVESTIGATION)

HEDA Idea: Primary Business Organization based on role
Created by: Elena Inurrategui (Proyecto Tribo)
Idea:
Someone can be related to a School or University as student or employee.
What is happening now:

A contact works at a School or University (the Account has the Educational Institution Record Type)
When I add an Affiliation to the University, SF will update the Primary Education Institution in the contact, instead of the Primary Business Organization, because the configuration is looking at the Account Record Type.

I would like something like this:
If I create an affiliation with the role = Employee and select it as primary, it updates the Primary Business Organization, regardless if the Account is a School, a University or a Business. If I create and affiliation with the role = Student, it updates the Primary Education Institution.

**lurch: add

Tracking W-022938

This Issue will be closed; follow this Idea in the Trailblazer Community for updates.


Fixed issue #9707

Issue Reference
Fixed issue #9707

Checked and Found that the issue has been fixed and working fine. Please check the screenshot for reference here


Fix naming conflict with ecto-rc.3

51

I've merged changes manually to resolve this. You can just remove the protocol implementations, since they now exist in ecto.


"Ensure that bitcoind is stopped" (kickstart)

counterparty-server kickstart fails if bitcoind isn't initially running.  Once bitcoind is running, you can start counterparty-server kickstart, but afterwards it instructs you to stop running bitcoind before proceeding. If bitcoind isn't running, you have to quickly turn it on and off which doesn't work very well in practice (bitcoin-cli stop launches a bitcoin-shutoff process which ended up doing nothing for several hours until I eventually pkill -6'd bitcoind).
Related logs:
2015-01-18-T10:51:32-0800 [INFO] Running v9.49.3 of counterpartyd.
2015-01-18-T10:51:32-0800 [INFO] Acquiring lock.
2015-01-18-T10:51:32-0800 [DEBUG] Lock acquired.
2015-01-18-T10:51:32-0800 [INFO] Connecting to database.
2015-01-18-T10:51:32-0800 [DEBUG] Creating connection to `counterparty.9.db`.
2015-01-18-T10:51:32-0800 [DEBUG] Checking database integrity.
2015-01-18-T10:51:32-0800 [INFO] Connecting to backend.
2015-01-18-T10:51:32-0800 [DEBUG] Could not connect to backend. (Try 1/12)
2015-01-18-T10:51:37-0800 [DEBUG] Could not connect to backend. (Try 2/12)
2015-01-18-T10:51:42-0800 [DEBUG] Could not connect to backend. (Try 3/12)
2015-01-18-T10:51:47-0800 [DEBUG] Could not connect to backend. (Try 4/12)
2015-01-18-T10:51:52-0800 [INFO] Received SIGINT.
2015-01-18-T10:51:52-0800 [INFO] Shutting down.

2015-01-18-T10:48:31-0800 [INFO] Running v9.49.3 of counterpartyd.
2015-01-18-T10:48:31-0800 [INFO] Acquiring lock.
2015-01-18-T10:48:31-0800 [INFO] Connecting to database.
2015-01-18-T10:48:31-0800 [INFO] Connecting to backend.
2015-01-18-T10:49:31-0800 [ERROR] Unhandled Exception
Traceback (most recent call last):
  File "/bin/counterparty-server", line 12, in <module>
    server.main()
  File "/usr/lib/python3.4/site-packages/counterpartycli/server.py", line 185, in main
    server.kickstart(db, bitcoind_dir=args.bitcoind_dir)
  File "/usr/lib/python3.4/site-packages/counterpartylib/server.py", line 344, in kickstart
    connect_to_backend()
  File "/usr/lib/python3.4/site-packages/counterpartylib/server.py", line 307, in connect_to_backend
    backend.getblockcount()
  File "/usr/lib/python3.4/site-packages/counterpartylib/lib/backend/__init__.py", line 32, in getblockcount
    return BACKEND().getblockcount()
  File "/usr/lib/python3.4/site-packages/counterpartylib/lib/backend/addrindex.py", line 118, in getblockcount
    return rpc('getblockcount', [])
  File "/usr/lib/python3.4/site-packages/counterpartylib/lib/backend/addrindex.py", line 52, in rpc
    raise BackendRPCError('Cannot communicate with backend. ({} is set to run on {}, is backend?)'.format(config.XCP_CLIENT, network))
counterpartylib.lib.backend.addrindex.BackendRPCError: Cannot communicate with backend. (counterpartyd is set to run on mainnet, is backend?)

As an aside, could the (y/N) prompt be worked around with something like:
parser_kickstart.add_argument('--noconfirm', help='do not prompt for any confirmation')

That would make it easier to run kickstart from system service files / configuration management frameworks.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Solved. Thanks!

Source
AUR

bitcoin-headless-addrindex
https://aur.archlinux.org/packages/bitcoin-headless-addrindex/

bitcoin-qt-addrindex
https://aur.archlinux.org/packages/bitcoin-qt-addrindex/

python-counterparty-lib
https://aur.archlinux.org/packages/python-counterparty-lib/

python-counterparty-lib-git
https://aur.archlinux.org/packages/python-counterparty-lib-git/

counterparty-cli
https://aur.archlinux.org/packages/counterparty-cli/

counterparty-cli-git
https://aur.archlinux.org/packages/counterparty-cli-git/

counterparty-gui
https://aur.archlinux.org/packages/counterparty-gui/

counterparty-gui-git
https://aur.archlinux.org/packages/counterparty-gui-git/

@atweiden, very cool!


Cleanup zap/repo/src-electron/generator/matter/app/zap-templates/templates

The goal is to eventually cleanup the matter specific zap code to not have any state for eg in ClustersHelper.js
During this cleanup we want to do the following:

Go through the matter directory in this issue. See if these helpers can have code pushed to the backend sql queries.
See if the helpers can use any of the existing helper logic and can remove code redundancy
Add unit tests for each of the helpers listed
Make sure to have a CHIP/Zigbee repo branch that points to your changes and passes the CI on both places
Also if you can fix anything new apart from what is listed then fix those issues as well.

Chip Repo PR: https://github.com/project-chip/connectedhomeip/pull/23410

Miscellaneous Stateful helper removal chip repo PR: https://github.com/project-chip/connectedhomeip/pull/25978


🐞🧑🚀  Ingestion Scan: File names including spaces not handled correctly by S3 Event Notifications

Describe the bug.
This bug was raised by @pricemg (thanks!).
Given two files.
file1.txt and file 2.txt

file1.txt - the scan etc performs as expected.
file 2.txt - is not picked up and scanned.

From Matthew:

Found out yesterday that s3 event notifications don't handle file names with spaces in and instead converts them to + 's which then I found was confusing my lambdas as they'd be trying to copy a file called e.g. my+file.txt based on the event notification being fed in, but the file in s3 is called my file.txt and so things we're getting stuck. Don't know if something you want/need to handle in your ap ingestion code
https://docs.aws.amazon.com/AmazonS3/latest/userguide/notification-content-structure.html

Initial attempts to solve this were reverted. We reverted them (and deleted the release we tested with) because files with spaces in them e.g. file 2.txt was scanned but was marked as infected when it was not.
To Reproduce
As part of briefly looking at this I (Gary) realised that there is currently no documented manner of testing the handler.py function in analytical-platform-integestion-scan.
If I recall when this was initially created we tested by creating release candidates and testing the full process, part of solving this bug should be to create a self-contained method in the analytical-platform-integestion-scan repository to test the handler.py function and document this in the README.
Expected Behaviour
Files with spaces are handled correctly.
Additional context
No response

We ought to discuss if this service is something we want to take advantage of and if so create a ticket and work on this.


Single Sign On pattern

Single sign on pattern should be implemented in patternfly-ng as specified on patternfly.org:
http://www.patternfly.org/pattern-library/application-framework/single-sign-on/

Closing due to inactivity.


Metal runtime segfault on close

Sometimes when ttrt finishes executing we segfault when using the metal backend.
./build/bin/ttmlir-opt --ttir-load-system-desc="path=n300.ttsys" --ttir-implicit-device --ttir-allocate --convert-ttir-to-ttmetal --ttmetal-serialize-to-binary="output=out.ttm" test/ttmlir/Silicon/TTMetal/to_layout.mlir

ttrt run --identity --atol 1e-02 out.ttm

Hmm that's not good, will take a look, thx for raising.

It's not a regression, it's been happening this way from day 1. I think there is a buffer that isn't be deallocated or something, at least it's crashing in buffer dealloc. Maybe the runtime map is hanging onto that shared ptr reference? Maybe we need to release the buffer during command queue exec dealloc? I only collected a back trace so I'm jumping to conclusions

TLDR; blocked on Metal fix.
Update - I looked at this issue, can reproduce, and I see what's going on.

A couple one-line improvements (for visual issues spotted) can be made on tt-mlir side (will put up PR)
but it doesn't solve this issue, and we do need a fix on tt-metal side (see https://github.com/tenstorrent/tt-metal/issues/12046 for details, will also put up PR)

Need the metal feature/bugfix to not allocate and deallocate metal Buffers that are created as views for TensorRefs for input/output tensors per program via createBufferFromTensorRef(device, tensorRef), otherwise Buffers that tt-mlir manages (allocating and deallocating) will mistakenly be deallocated by device teardown.
I made metal changes locally and confirmed it solves this segfault from looking at debug logs, and also from running test in loop 50x, previously would hit segfault 50% of the time.

Update here - TDLR; the "Metal runtimetime segfault on close" is ~worked-around now.

Merged a PR just now #529 to main which includes those couple one line fixes mentioned in prev comment, and another new tt-mlir hack which works around the original segfault reported here.  Also included is adding the TTMetal existing tests to CI for the first time.  This removes blocking dependency on tt-metal.
For the tt-metal changes (more proper fix for the segfault, to replace temporary hack), I haven't been able to get passing build inside tt-metal repo (some ttnn cryptic compile errors WIP), so haven't opened PR there quite yet.  Hope to get someone from Metal to look Tuesday if I don't figure it out by then.

Thinking I'll rename this ticket and keep open until proper fix comes.


Testing

Please test this locally because it changes a lot and the tests don't cover everything.
Coverage report
Name                          Stmts   Miss  Cover
-------------------------------------------------
harvest/__init__.py               0      0   100%
harvest/algo.py                 129     56    57%
harvest/broker/__init__.py        0      0   100%
harvest/broker/_base.py         176    117    34%
harvest/broker/dummy.py         226    121    46%
harvest/broker/robinhood.py     354    354     0%
harvest/load.py                  40     29    28%
harvest/plugin/__init__.py        1      1     0%
harvest/plugin/_base.py           2      2     0%
harvest/plugin/yahoo.py          17     17     0%
harvest/queue.py                 31      9    71%
harvest/trader/__init__.py        2      0   100%
harvest/trader/tester.py        121     81    33%
harvest/trader/trader.py        341    274    20%
-------------------------------------------------
TOTAL                          1440   1061    26%

Refactors harvest to following structure:
New

Was

I'm merging this now since it renames functions.


Remove temp code in LookupReferencesManager to support rolling upgrade in 0.11.0

The lookup service /druid/coordinator/v1/lookups/{tier} presently returns a list of lookup names for a specific tier. Once the PR #4758 is merged, this service will return a map of lookup names and LookupExtractorFactoryMapContainer objects based on a query parameter value. For supporting rolling updates, LookupReferencesManager would have a temporary fix that would handle this.
This issue is to track the removal of this temporary fix from getLookupListFromCoordinator() method in LookupReferencesManager.

@jihoonson  Yeah, this has been fixed in #5029 . Closing this issue.


Negative space in the coder sidebar

There's lots of negative space in the sidebar added by the extension. Could we perhaps list workspaces that match owner:me, refreshing every minute or something (with a refresh button to refresh now)? This would help avoid having to click "Open Workspace" if users are only using their own workspaces.

I'll start working on this tomorrow!

Notes
I started digging into this. I thought, "Ah this will be easy!!" but it turns out it's a little bit more complex. Currently, we use what's called "Welcome content".
This API allows us to contribute a viewWelcome and specify very basic contents as a string with support for links/buttons. We currently do this as so:
    "viewsWelcome": [
      {
        "view": "coderRemote",
        "contents": "You're logged in! \n[Open Workspace](command:coder.open)",
        "when": "coder.authenticated && coder.loaded"
      }
    ],

If we want to display more complex data - aka a list of workspaces - we'll need to contribute a view to this View Container.
I'm currently playing around with the tree-view-sample to figure out how to do that.
So that's the first step: if not logged in, display "login coder" as a viewWelcome, otherwise, display custom tree view.


Error while downloading

Looks like I'm having some internet problems. Is it possible to download the dataset ahead of time and load it locally, and if so is there an example for that ?

There is no support for this behavior within mteb. However, we use Huggingface's datasets for loading datasets with. I believe you can do:
task.load_data() # load dataset

# new sessions without internet
task.load_data() # loads datasets from cache

This is not a 100% consistent behaviour though as e.g. some of the datasets utilize a script when downloading. If you find that it works for some but not others, it might be worth looking into if it is possible to reformat the data to enable local caching.

As this is more on the datasets side, I'm closing this issue.


Store() function

Overview
This PR implements Store(<row_query>, <fieldname>=10). Currently, it's only supported on set fields. It's not clear to me yet how we would support this on mutex and bool fields. And I don't think it makes sense to store a row result into int or time fields (although I suppose if Store() took an optional timestamp, it could apply the row to all time quantums).
Also, the PQL function is Store(), but internally everything is SetRow() because it seemed like a complement to ClearRow().
Fixes #637 (at least the first phase of it)
TODO:

[x] Docs
[x] Decide if we want to support time fields.

Pull request checklist

[x] I have read the contributing guide.
[x] I have agreed to the Contributor License Agreement.
[x] I have updated the documentation.
[x] I have resolved any merge conflicts.
[x] I have included tests that cover my changes.
[x] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

I vote "no" on time fields - keep things simple for now.

I vote only set fields

Since we're only supporting set fields as the destination field, I'm taking this PR out of WIP.

This supports an arbitrary bitmap call, right? I would suggest adding a second docs example explicitly showing something simple like Store(Intersect(x, y), z), to demonstrate that you can sort of perform computations this way. Maybe a test that does something like that as well.
I agree on only supporting set fields for now, but some thoughts on future directions... Storing to mutex seems reasonable - doesn't it make sense (conceptually at least) to write some bits to one row of a mutex field, then clear any conflicting bits as necessary?
I can imagine performing arithmetic operations on int fields and storing the entire result into another int field. This is obviously far-future kind of work though, and its not clear if it would even make sense to use Pilosa for this.

@alanbernstein I added another example to the query docs.
I think that mutex support is do-able, but it will likely require that we handle the individual columns, checking for existing values on each.
I like the idea of storing arithmetic operations performed on int fields. That made me wonder about doing arithmetic operations on an int field in place. For example, add 7 to all columns in int field f. I think this would require us to do multiple passes and re-writing of rows, and I'm not even sure that's useful, but something we could likely do fairly easily.